Guidance of LTE FDD Inspection SOP Rules-R11.1.4

Guidance of LTE FDD Inspection SOP Rules Internal
Product Version Confidentiality

R11.1.4 INTERNAL
Huawei Technologies Co., Ltd. Product Name Page
Guidance of LTE FDD Inspection 375
SOP Rules
Guidance of LTE FDD Inspection SOP Rules
Prepared by: Chenlingxia WX322818, Date: 2016-03-07

Shaoxin WX333497
Reviewed by: Liaoling WX213117 Date: 2016-03-11
Approved by: Date:
Huawei Technologies Co., Ltd.

All Rights Reserved
Huawei Proprietary and Confidential Page 1 of 361

2020-6-23 Copyright © Huawei Technologies Co., Ltd.
Revise History
Date Version Description Author

2014-07-30 V3.1 Update the rule descriptions for all rules. Liaoling WX213117
2014-09-28 V3.2 Update the rule descriptions for optimized and new rules. Liaoling WX213117
2015-02-10 V3.4 Update the rule descriptions for optimized and new rules (Add 32 rules and Liaoling WX213117
delete 2 rules. Hierarchy adjustment).
2015-10-20 R11.0.1 Update the rule descriptions for optimized and new rules. Liaoling WX213117
2016-02-04 R11.1.1 Update the rule descriptions for optimized and new rules. Liaoling WX213117,
Chenlingxia WX322818
2016-03- R11.1.4 Update the rule descriptions for optimized and new rules. Liaoling WX213117,
Chenlingxia WX322818,
Shaoxin WX333497

1 Contents
Guidance of LTE FDD Inspection SOP Rules..................................................................................................................................................1
1Contents...........................................................................................................................................................................................................3
2Overview.......................................................................................................................................................................................................36
2.1 Details......................................................................................................................................................................................................36
2.2 Intended Audience..................................................................................................................................................................................36
2.3 Application Scope...................................................................................................................................................................................36
2.3.1 Update................................................................................................................................................................................................37
2.3.2 Revision compared with R11.0.1......................................................................................................................................................37
3Rule Description............................................................................................................................................................................................40
3.1 Network Health Indicator.....................................................................................................................................................................40

3.1.1 Location.............................................................................................................................................................................................40
3.1.2 Rules Description...............................................................................................................................................................................40
3.1.3 Principles............................................................................................................................................................................................41
3.1.4 Measures............................................................................................................................................................................................43
3.1.5 Reference...........................................................................................................................................................................................43
3.2 Basic Network Information...................................................................................................................................................................43
3.2.1 Location.............................................................................................................................................................................................43
3.2.3 Principles............................................................................................................................................................................................45
3.2.4 Measures............................................................................................................................................................................................46
3.2.5 Reference...........................................................................................................................................................................................47
3.3 Device Version Information..................................................................................................................................................................47
3.3.1 Location.............................................................................................................................................................................................47
3.3.3 Principles............................................................................................................................................................................................48
3.3.4 Measures............................................................................................................................................................................................48
3.3.5 Reference...........................................................................................................................................................................................48
3.4 Distribution of eNodeBs and Cells........................................................................................................................................................48
3.4.1 Location.............................................................................................................................................................................................48
3.4.3 Principles............................................................................................................................................................................................49

3.4.4 Measures............................................................................................................................................................................................50
3.4.5 Reference...........................................................................................................................................................................................50
3.5 Board Statistics.......................................................................................................................................................................................50
3.5.1 Location.............................................................................................................................................................................................50
3.5.3 Principles............................................................................................................................................................................................51
3.5.4 Measures............................................................................................................................................................................................52
3.5.5 Reference...........................................................................................................................................................................................52
3.6 RRU Configuration Information..........................................................................................................................................................52
3.6.1 Location.............................................................................................................................................................................................52
3.6.3 Principles............................................................................................................................................................................................53
3.6.4 Measures............................................................................................................................................................................................54
3.6.5 Reference...........................................................................................................................................................................................54
3.7 Sleeping Cell Check................................................................................................................................................................................54
3.7.1 Location.............................................................................................................................................................................................54
3.7.3 Principles............................................................................................................................................................................................55
3.7.4 Measures............................................................................................................................................................................................56
3.7.5 References..........................................................................................................................................................................................56
3.8 Unavailable Cell Check..........................................................................................................................................................................56
3.8.1 Location.............................................................................................................................................................................................56
3.8.3 Principles............................................................................................................................................................................................57
3.8.4 Measures............................................................................................................................................................................................58
3.8.5 Reference...........................................................................................................................................................................................58
3.9 Deactivated Cell Statistics.....................................................................................................................................................................58
3.9.1 Location.............................................................................................................................................................................................58
3.9.3 Principles............................................................................................................................................................................................58
3.9.4 Measures............................................................................................................................................................................................59
3.9.5 Reference...........................................................................................................................................................................................59
3.10 Hot Patch State Check.....................................................................................................................................................................59
3.10.1 Location.......................................................................................................................................................................................59
3.10.2 Rules Description........................................................................................................................................................................59
3.10.3 Principles.....................................................................................................................................................................................60
3.10.4 Measures......................................................................................................................................................................................60
3.10.5 Reference.....................................................................................................................................................................................60
3.11 Check of Cell Reserved State for Operator..................................................................................................................................60
3.11.1 Location.......................................................................................................................................................................................60
3.11.3 Principles.....................................................................................................................................................................................61
3.11.4 Measures......................................................................................................................................................................................61
3.11.5 Reference.....................................................................................................................................................................................61
3.12 Cell Barred State Check..................................................................................................................................................................61
3.12.1 Location.......................................................................................................................................................................................61
3.12.3 Principles.....................................................................................................................................................................................62
3.12.4 Measures......................................................................................................................................................................................62
3.12.5 Reference.....................................................................................................................................................................................62
3.13 Cell Capability Degraded Check....................................................................................................................................................62
3.13.1 Location.......................................................................................................................................................................................62
3.13.3 Principles.....................................................................................................................................................................................63
3.13.4 Measures......................................................................................................................................................................................63
3.13.5 Reference.....................................................................................................................................................................................63
3.14 Clock State Check............................................................................................................................................................................64
3.14.1 Location.......................................................................................................................................................................................64
3.14.3 Principles.....................................................................................................................................................................................64
3.14.4 Measures......................................................................................................................................................................................65
3.14.5 Reference.....................................................................................................................................................................................65
3.15 SCTP Link State Check (S1)..........................................................................................................................................................65
3.15.1 Location.......................................................................................................................................................................................65
3.15.3 Principles.....................................................................................................................................................................................66
3.15.4 Measures......................................................................................................................................................................................66
3.15.5 Reference.....................................................................................................................................................................................66
3.16 SCTP Link State Check (X2)..........................................................................................................................................................67
3.16.1 Location.......................................................................................................................................................................................67
3.16.3 Principles.....................................................................................................................................................................................68
3.16.4 Measures......................................................................................................................................................................................68
3.16.5 Reference.....................................................................................................................................................................................68
3.17 NE Project State Check...................................................................................................................................................................69
3.17.1 Location.......................................................................................................................................................................................69
3.17.3 Principles.....................................................................................................................................................................................69
3.17.4 Measures......................................................................................................................................................................................70
3.17.5 Reference.....................................................................................................................................................................................70
3.18 Active Alarm Analysis.....................................................................................................................................................................70
3.18.1 Location.......................................................................................................................................................................................70
3.18.3 Principles.....................................................................................................................................................................................71
3.18.4 Measures......................................................................................................................................................................................71
3.18.5 Reference.....................................................................................................................................................................................71
3.19 Historical Alarms Analysis.............................................................................................................................................................72
3.19.1 Location.......................................................................................................................................................................................72
3.19.3 Principles.....................................................................................................................................................................................73
3.19.4 Measures......................................................................................................................................................................................73
3.19.5 Reference.....................................................................................................................................................................................74
3.20 Abnormal Reset Event....................................................................................................................................................................74
3.20.1 Location.......................................................................................................................................................................................74
3.20.3 Principles.....................................................................................................................................................................................74
3.20.4 Measures......................................................................................................................................................................................75
3.20.5 Reference.....................................................................................................................................................................................75
3.21 Hardware Fault Alarm....................................................................................................................................................................75
3.21.1 Location.......................................................................................................................................................................................75
3.21.3 Principles.....................................................................................................................................................................................76
3.21.4 Measures......................................................................................................................................................................................76
3.21.5 Reference.....................................................................................................................................................................................76
3.22 RF Unit Channel Abnormal Alarm...............................................................................................................................................77
3.22.1 Location.......................................................................................................................................................................................77
3.22.3 Principles.....................................................................................................................................................................................77
3.22.4 Measures......................................................................................................................................................................................78
3.22.5 Reference.....................................................................................................................................................................................78
3.23 Entire System Alarm.......................................................................................................................................................................78
3.23.1 Location.......................................................................................................................................................................................78
3.23.3 Principles.....................................................................................................................................................................................79
3.23.4 Measures......................................................................................................................................................................................79
3.23.5 Reference.....................................................................................................................................................................................80
3.24 Board Temperature Monitor..........................................................................................................................................................80
3.24.1 Location.......................................................................................................................................................................................80
3.24.3 Principles.....................................................................................................................................................................................81
3.24.4 Measures......................................................................................................................................................................................82
3.24.5 Reference.....................................................................................................................................................................................82
3.25 Check of Transmit Channel Power Consistency..........................................................................................................................82
3.25.1 Location.......................................................................................................................................................................................82
3.25.3 Principles.....................................................................................................................................................................................83
3.25.4 Measures......................................................................................................................................................................................83
3.25.5 Reference.....................................................................................................................................................................................83
3.26 Check of Blind HO (redirection) Priority of Inter-RAT Neighboring Cell...............................................................................83
3.26.1 Location.......................................................................................................................................................................................83
3.26.3 Principles.....................................................................................................................................................................................84
3.26.4 Measures......................................................................................................................................................................................85
3.26.5 Reference.....................................................................................................................................................................................85
3.27 IPPATH Check................................................................................................................................................................................86
3.27.1 Location.......................................................................................................................................................................................86
3.27.3 Principles.....................................................................................................................................................................................86
3.27.4 Measures......................................................................................................................................................................................87
3.27.5 Reference.....................................................................................................................................................................................87
3.28 Clock Configuration Check............................................................................................................................................................87
3.28.1 Location.......................................................................................................................................................................................87
3.28.3 Principles.....................................................................................................................................................................................89
3.28.4 Measures......................................................................................................................................................................................89
3.28.5 Reference.....................................................................................................................................................................................90
3.29 IPRT Check......................................................................................................................................................................................90
3.29.1 Location.......................................................................................................................................................................................90
3.29.3 Principles.....................................................................................................................................................................................90
3.29.4 Measures......................................................................................................................................................................................91
3.29.5 Reference.....................................................................................................................................................................................91
3.30 Check of S1 Link State (Block)......................................................................................................................................................91
3.30.1 Location.......................................................................................................................................................................................91
3.30.3 Principles.....................................................................................................................................................................................91
3.30.4 Measures......................................................................................................................................................................................92
3.30.5 Reference.....................................................................................................................................................................................92
3.31 IPsec Configuration Check.............................................................................................................................................................92
3.31.1 Location.......................................................................................................................................................................................92
3.31.3 Principles.....................................................................................................................................................................................93
3.31.4 Measures......................................................................................................................................................................................93
3.31.5 Reference.....................................................................................................................................................................................93
3.32 Statistic of X2 Link SCTPHOST Port...........................................................................................................................................93
3.32.1 Location.......................................................................................................................................................................................93
3.32.3 Principles.....................................................................................................................................................................................94
3.32.4 Measures......................................................................................................................................................................................94
3.32.5 Reference.....................................................................................................................................................................................95
3.33 CSFB Feature Switch Check..........................................................................................................................................................95
3.33.1 Location.......................................................................................................................................................................................95
3.33.3 Principles.....................................................................................................................................................................................95
3.33.4 Measures......................................................................................................................................................................................96
3.33.5 Reference.....................................................................................................................................................................................96
3.34 Fast ANR Parameter Check...........................................................................................................................................................96
3.34.1 Location.......................................................................................................................................................................................96
3.34.3 Principles.....................................................................................................................................................................................97
3.34.4 Measures......................................................................................................................................................................................97
3.34.5 Reference.....................................................................................................................................................................................97
3.35 eUCellSectorEqm Configuration Check.......................................................................................................................................97
3.35.1 Location.......................................................................................................................................................................................97
3.35.3 Principles.....................................................................................................................................................................................98
3.35.4 Measures......................................................................................................................................................................................98
3.35.5 Reference.....................................................................................................................................................................................98
3.36 DRX Enter/Exit Threshold Check.................................................................................................................................................98
3.36.1 Location.......................................................................................................................................................................................98
3.36.3 Principles.....................................................................................................................................................................................99
3.36.4 Measures......................................................................................................................................................................................99
3.36.5 Reference.....................................................................................................................................................................................99
3.37 Excessive pRRUs Under Co-MPT..................................................................................................................................................99
3.37.1 Location.......................................................................................................................................................................................99
3.37.2 Rule Description..........................................................................................................................................................................99
3.37.3 Principles...................................................................................................................................................................................100
3.37.4 Measures....................................................................................................................................................................................100
3.37.5 Reference...................................................................................................................................................................................100
3.38 Check of Flash CSFB and RIM Configuration..........................................................................................................................100
3.38.1 Location.....................................................................................................................................................................................100
3.38.2 Rules Description......................................................................................................................................................................100
3.38.3 Principles...................................................................................................................................................................................101
3.38.4 Measures....................................................................................................................................................................................101
3.38.5 Reference...................................................................................................................................................................................101
3.39 2T4R Configuration Check...........................................................................................................................................................101
3.39.1 Location.....................................................................................................................................................................................101
3.39.3 Principles...................................................................................................................................................................................102
3.39.4 Measures....................................................................................................................................................................................102
3.39.5 Reference...................................................................................................................................................................................102
3.40 License Running State Check.......................................................................................................................................................103
3.40.1 Location.....................................................................................................................................................................................103
3.40.3 Principles...................................................................................................................................................................................103
3.40.4 Measures....................................................................................................................................................................................104
3.40.5 Reference...................................................................................................................................................................................104
3.41 License Item Consistency Check..................................................................................................................................................104
3.41.1 Location.....................................................................................................................................................................................104
3.41.3 Principles...................................................................................................................................................................................105
3.41.4 Measures....................................................................................................................................................................................105
3.41.5 Reference...................................................................................................................................................................................105
3.42 Check of LTE eRAN6.0&eRAN6.1 Life Cycle...........................................................................................................................105
3.42.1 Location.....................................................................................................................................................................................105
3.42.3 Principles...................................................................................................................................................................................106
3.42.4 Measures....................................................................................................................................................................................106
3.42.5 Reference...................................................................................................................................................................................106
3.43 CPU Load Evaluation....................................................................................................................................................................106
3.43.1 Location.....................................................................................................................................................................................106
3.43.3 Principles...................................................................................................................................................................................108
3.43.4 Measures....................................................................................................................................................................................108
3.43.5 Reference...................................................................................................................................................................................109
3.44 eNodeB Capacity Switch Check...................................................................................................................................................109
3.44.1 Location.....................................................................................................................................................................................109
3.44.3 Principles...................................................................................................................................................................................109
3.44.4 Measures....................................................................................................................................................................................110
3.44.5 Reference...................................................................................................................................................................................111
3.45 Check of Uu Interface Resource Congestion..............................................................................................................................111
3.45.1 Location.....................................................................................................................................................................................111
3.45.3 Principles...................................................................................................................................................................................112
3.45.4 Measures....................................................................................................................................................................................113
3.45.5 Reference...................................................................................................................................................................................113
3.46 User Plane Load Evaluation.........................................................................................................................................................113
3.46.1 Location.....................................................................................................................................................................................113
3.46.3 Principles...................................................................................................................................................................................114
3.46.4 Measures....................................................................................................................................................................................115
3.46.5 Reference...................................................................................................................................................................................116
3.47 Paging Performance Analysis.......................................................................................................................................................116
3.47.1 Location.....................................................................................................................................................................................116
3.47.3 Principles...................................................................................................................................................................................116
3.47.4 Measures....................................................................................................................................................................................117
3.47.5 Reference...................................................................................................................................................................................117
3.48 RRC Setup Success Rate...............................................................................................................................................................117
3.48.1 Location.....................................................................................................................................................................................117
3.48.3 Principles...................................................................................................................................................................................118
3.48.4 Measures....................................................................................................................................................................................120
3.48.5 Reference...................................................................................................................................................................................120
3.49 eRAB Setup Success Rate.............................................................................................................................................................120
3.49.1 Location.....................................................................................................................................................................................120
3.49.3 Principles...................................................................................................................................................................................121
3.49.4 Measures....................................................................................................................................................................................122
3.49.5 Reference...................................................................................................................................................................................123
3.50 Call Drop Rate...............................................................................................................................................................................123
3.50.1 Location.....................................................................................................................................................................................123
3.50.3 Principles...................................................................................................................................................................................124
3.50.4 Measures....................................................................................................................................................................................125
3.50.5 Reference...................................................................................................................................................................................125
3.51 Intra-eNB Handover Success Rate...............................................................................................................................................126
3.51.1 Location.....................................................................................................................................................................................126
3.51.3 Principles...................................................................................................................................................................................127
3.51.4 Measures....................................................................................................................................................................................128
3.51.5 Reference...................................................................................................................................................................................128
3.52 Inter-eNB Handover Success Rate...............................................................................................................................................129
3.52.1 Location.....................................................................................................................................................................................129
3.52.3 Principles...................................................................................................................................................................................130
3.52.4 Measures....................................................................................................................................................................................131
3.52.5 Reference...................................................................................................................................................................................131
3.53 Inter-RAT Handover Success Rate..............................................................................................................................................132
3.53.1 Location.....................................................................................................................................................................................132
3.53.3 Principles...................................................................................................................................................................................133
3.53.4 Measures....................................................................................................................................................................................134
3.53.5 Reference...................................................................................................................................................................................135
3.54 Intra-Freq Handover Success Rate..............................................................................................................................................135
3.54.1 Location.....................................................................................................................................................................................135
3.54.3 Principles...................................................................................................................................................................................136
3.54.4 Measures....................................................................................................................................................................................137
3.54.5 Reference...................................................................................................................................................................................137
3.55 Inter-Freq Handover Success Rate..............................................................................................................................................138
3.55.1 Location.....................................................................................................................................................................................138
3.55.3 Principles...................................................................................................................................................................................139
3.55.4 Measures....................................................................................................................................................................................140
3.55.5 Reference...................................................................................................................................................................................140
3.56 User Throughput Rate..................................................................................................................................................................141
3.56.1 Location.....................................................................................................................................................................................141
3.56.3 Principles...................................................................................................................................................................................142
3.56.4 Measures....................................................................................................................................................................................143
3.56.5 Reference...................................................................................................................................................................................143
3.57 User Number..................................................................................................................................................................................143
3.57.1 Location.....................................................................................................................................................................................143
3.57.3 Principles...................................................................................................................................................................................144
3.57.4 Measures....................................................................................................................................................................................146
3.57.5 Reference...................................................................................................................................................................................146
3.58 MOCN Performance Statistic from here....................................................................................................................................146
3.58.1 Location.....................................................................................................................................................................................146
3.58.3 Principles...................................................................................................................................................................................147
3.58.4 Measures....................................................................................................................................................................................147
3.58.5 Reference...................................................................................................................................................................................147
3.59 Network KPI Variation.................................................................................................................................................................148
3.59.1 Location.....................................................................................................................................................................................148
3.59.3 Principles...................................................................................................................................................................................148
3.59.4 Measures....................................................................................................................................................................................151
3.59.5 Reference...................................................................................................................................................................................151
3.60 Traffic Variation............................................................................................................................................................................151
3.60.1 Location.....................................................................................................................................................................................151
3.60.3 Principles...................................................................................................................................................................................152
3.60.4 Measures....................................................................................................................................................................................153
3.60.5 Reference...................................................................................................................................................................................153
3.61 Network KPI Variation (during specified time).........................................................................................................................153
3.61.1 Location.....................................................................................................................................................................................153
3.61.3 Principles...................................................................................................................................................................................154
3.61.4 Measures....................................................................................................................................................................................156
3.61.5 Reference...................................................................................................................................................................................156
3.62 Traffic Variation (during specific time)......................................................................................................................................156
3.62.1 Location.....................................................................................................................................................................................156
3.62.3 Principles...................................................................................................................................................................................157
3.62.4 Measures....................................................................................................................................................................................159
3.62.5 Reference...................................................................................................................................................................................159
3.63 TOP Risk Cells of KPI Degeneration..........................................................................................................................................159
3.63.1 Location.....................................................................................................................................................................................159
3.63.3 Principles...................................................................................................................................................................................160
3.63.4 Measures....................................................................................................................................................................................160
3.63.5 Reference...................................................................................................................................................................................160
3.64 TOP Risk Cells of KPI Degeneration (during specific time).....................................................................................................160
3.64.1 Location.....................................................................................................................................................................................160
3.64.3 Principles...................................................................................................................................................................................161
3.64.4 Measures....................................................................................................................................................................................161
3.64.5 Reference...................................................................................................................................................................................161
3.65 Parts of Support Precaution Notices Which Need Manual Check...........................................................................................161
3.65.1 Location.....................................................................................................................................................................................161
3.65.3 Principles...................................................................................................................................................................................162
3.65.4 Measures....................................................................................................................................................................................162
3.65.5 Reference...................................................................................................................................................................................162
3.66 Notice on Precaution for FDD eNodeBs – Network Access Failures after the IP Path Switchover Is Performed..............163
3.66.1 Location.....................................................................................................................................................................................163
3.66.3 Principles...................................................................................................................................................................................163
3.66.4 Measures....................................................................................................................................................................................164
3.66.5 Reference...................................................................................................................................................................................164
3.67 Precaution Bulletin on Service Impact Caused by ETH Interconnected Mode.....................................................................164
3.67.1 Location.....................................................................................................................................................................................164
3.67.3 Principles...................................................................................................................................................................................164
3.67.4 Measures....................................................................................................................................................................................165
3.67.5 Reference...................................................................................................................................................................................165
3.68 Notice on Precaution – Check of Abnormal RX Power of Optical Module (Only relates to China)....................................165
3.68.1 Location.....................................................................................................................................................................................165
3.68.3 Principles...................................................................................................................................................................................165
3.68.4 Measures....................................................................................................................................................................................165
3.68.5 Reference...................................................................................................................................................................................165
3.69 Notice on Precaution for Certificate Expiry Not Promptly Notified Because of Certificate Validity Check Disabling.....166
3.69.1 Location.....................................................................................................................................................................................166
3.69.3 Principles...................................................................................................................................................................................166
3.69.4 Measures....................................................................................................................................................................................166
3.69.5 Reference...................................................................................................................................................................................167
3.70 Notice on Precaution for Remote OMCH Reestablishment Failure Due to Self-Setup Disabling........................................167
3.70.1 Location.....................................................................................................................................................................................167
3.70.3 Principles...................................................................................................................................................................................168
3.70.4 Measures....................................................................................................................................................................................168
3.70.5 Reference...................................................................................................................................................................................168
3.71 Precaution Notice for LampSite - License Resources Become Insufficient Following Capability Improvements of the BBP (LBBPd or
UBBPd3, UBBPd4, UBBPd5, or UBBPd6)........................................................................................................................................168
3.71.1 Location.....................................................................................................................................................................................168
3.71.3 Principles...................................................................................................................................................................................169
3.71.4 Measures....................................................................................................................................................................................169
3.71.5 Reference...................................................................................................................................................................................170
3.72 Precaution Notice for Temperature Exception Alarm Reporting and Repeated Restart of LampSite RHUB Working in Low Temperature
170
3.72.1 Location.....................................................................................................................................................................................170
3.72.3 Principles...................................................................................................................................................................................170
3.72.4 Measures....................................................................................................................................................................................171
3.72.5 Reference...................................................................................................................................................................................171
3.73 Notice on Precaution for the Disconnection of LTE FDD eNodeBs.........................................................................................171
3.73.1 Location.....................................................................................................................................................................................171
3.73.3 Principles...................................................................................................................................................................................172
3.73.4 Measures....................................................................................................................................................................................172
3.73.5 Reference...................................................................................................................................................................................172
3.74 Notice on Precaution for Decrease in CA UE Handover Success Rate....................................................................................172
3.74.1 Location.....................................................................................................................................................................................172

3.74.3 Principles...................................................................................................................................................................................173
3.74.4 Measures....................................................................................................................................................................................174
3.74.5 Reference...................................................................................................................................................................................174
3.75 LTE FDD Precaution Notice - RRC Connection Reestablishment Rejected Due to a PCI Conflict....................................174
3.75.1 Location.....................................................................................................................................................................................174
3.75.3 Principles...................................................................................................................................................................................175
3.75.4 Measures....................................................................................................................................................................................175
3.75.5 Reference...................................................................................................................................................................................175
3.76 Notice on Precaution for Decreasing Handover Success Rate (Only relates to China).........................................................175
3.76.1 Location.....................................................................................................................................................................................175
3.76.3 Principles...................................................................................................................................................................................176
3.76.4 Measures....................................................................................................................................................................................176
3.76.5 Reference...................................................................................................................................................................................176
3.77 Notice on Precaution for FDD eNodeBs -Disconnected IPSec Tunnels...................................................................................176
3.77.1 Location.....................................................................................................................................................................................176
3.77.3 Principles...................................................................................................................................................................................177
3.77.4 Measures....................................................................................................................................................................................177
3.77.5 Reference...................................................................................................................................................................................177
3.78 Notice on Precaution for Instantaneous CPU Usage Increase Due to Automatic Removal of Neighboring Cells by Intra-RAT ANR in Full
Specification Scenarios........................................................................................................................................................................178
3.78.1 Location.....................................................................................................................................................................................178
3.78.3 Principles...................................................................................................................................................................................178
3.78.4 Measures....................................................................................................................................................................................179
3.78.5 Reference...................................................................................................................................................................................179
3.79 Notice on Precaution for Flash CSFB Failure Due to RSN Return to Zero After eNodeB Reset.........................................179
3.79.1 Location.....................................................................................................................................................................................179
3.79.3 Principles...................................................................................................................................................................................180
3.79.4 Measures....................................................................................................................................................................................181
3.79.5 Reference...................................................................................................................................................................................181
3.80 Notice on Precaution for FDD eNodeB- Deterioration of RRC Setup Success Rate and Other Counters Due to Disabled SRS
Configuration (Only relates to China)...............................................................................................................................................181
3.80.1 Location.....................................................................................................................................................................................181
3.80.3 Principles...................................................................................................................................................................................182
3.80.4 Measures....................................................................................................................................................................................182
3.80.5 Reference...................................................................................................................................................................................182
3.81 Notice on Precaution for Occasional UE Access Failure When IucsRrcRecfgMcCombSwitch Is Set to On......................182
3.81.1 Location.....................................................................................................................................................................................182
3.81.3 Principles...................................................................................................................................................................................183
3.81.4 Measures....................................................................................................................................................................................183
3.81.5 Reference...................................................................................................................................................................................183
3.82 Notice on Precaution for User Access Failures after the RF Link of a LampSite Base Station Recovers from an Intermittent
Disconnection........................................................................................................................................................................................183
3.82.1 Location.....................................................................................................................................................................................183
3.82.3 Principles...................................................................................................................................................................................184
3.82.4 Measures....................................................................................................................................................................................184
3.82.5 Reference...................................................................................................................................................................................184
3.83 Notice on Precaution for Service Interruption Due to a Negotiation Problem When the First Peer IP Address of a Dual-Homed SCTP
Link Is Not Configured at the Peer MME.........................................................................................................................................185
3.83.1 Location.....................................................................................................................................................................................185
3.83.3 Principles...................................................................................................................................................................................185
3.83.4 Measures....................................................................................................................................................................................186
3.83.5 Reference...................................................................................................................................................................................186
3.84 Precaution Notice for Lengthy Upgrades of Single-mode LampSite Base Station Where Each pRRU Connects to an RHUB over Two
Ethernet Cables....................................................................................................................................................................................186
3.84.1 Location.....................................................................................................................................................................................186
3.84.3 Principles...................................................................................................................................................................................187
3.84.4 Measures....................................................................................................................................................................................187
3.84.5 Reference...................................................................................................................................................................................187
3.85 Precaution Notice for Service Unavailability on a Co-MPT UMTS/LTE LampSite Base Station Using 9.8 Gbit/s Optical Modules 188
3.85.1 Location.....................................................................................................................................................................................188
3.85.3 Principles...................................................................................................................................................................................188
3.85.4 Measures....................................................................................................................................................................................189
3.85.5 Reference...................................................................................................................................................................................189
3.86 Precaution Notice for Failures in Reaching Peak Uplink Throughput on a LampSite LTE Base Station..........................189
3.86.1 Location.....................................................................................................................................................................................189
3.86.3 Principles...................................................................................................................................................................................190
3.86.4 Measures....................................................................................................................................................................................190
3.86.5 Reference...................................................................................................................................................................................190
3.87 Notice on Precaution for Failures of Cell Activation When Both 1R/2R and 4R Cells Are Setup on UBBPD6 Baseband (Only relates to
China)....................................................................................................................................................................................................191
3.87.1 Location.....................................................................................................................................................................................191

3.87.3 Principles...................................................................................................................................................................................191
3.87.4 Measures....................................................................................................................................................................................191
3.87.5 Reference...................................................................................................................................................................................191
3.88 Notice on Precaution for TOD Unusable Caused by USCU Baseband Resetting Which Used Clock Cascading Scenes (Only relates to
China)....................................................................................................................................................................................................192
3.88.1 Location.....................................................................................................................................................................................192
3.88.3 Principles...................................................................................................................................................................................192
3.88.4 Measures....................................................................................................................................................................................192
3.88.5 Reference...................................................................................................................................................................................192
3.89 Notice on Precaution for Occasional Unexpected eNodeB Restarts or Configuration Command Execution Failure upon Frequent X2 Self-
Setups.....................................................................................................................................................................................................192
3.89.1 Location.....................................................................................................................................................................................192
3.89.3 Principles...................................................................................................................................................................................193
3.89.4 Measures....................................................................................................................................................................................193
3.89.5 Reference...................................................................................................................................................................................194
3.90 Notice on Precaution for UE Access Failures or Releases in Inter-BBP Cells in Certain Scenarios....................................194
3.90.1 Location.....................................................................................................................................................................................194
3.90.3 Principles...................................................................................................................................................................................195
3.90.4 Measures....................................................................................................................................................................................195
3.90.5 Reference...................................................................................................................................................................................195
3.91 Notice on Precaution for Sleeping Cell by Using Time Synchronous Mode (Only relates to China)...................................196
3.91.1 Location.....................................................................................................................................................................................196
3.91.3 Principles...................................................................................................................................................................................196
3.91.4 Measures....................................................................................................................................................................................196
3.91.5 Measures....................................................................................................................................................................................196
3.91.6 Reference...................................................................................................................................................................................196
3.92 LTE FDD Precaution Notice – Resource Leakage for the RRC Connected User License Control Item.............................197
3.92.1 Location.....................................................................................................................................................................................197
3.92.3 Principles...................................................................................................................................................................................197
3.92.4 Measures....................................................................................................................................................................................198
3.92.5 Reference...................................................................................................................................................................................198
3.93 Notice on Precaution for Parts of eNodeB Resetting Upon Executing Function of Characteristic State Inquiring in CME (Only relates to
China)....................................................................................................................................................................................................198
3.93.1 Location.....................................................................................................................................................................................198
3.93.3 Principles...................................................................................................................................................................................199
3.93.4 Measures....................................................................................................................................................................................199
3.93.5 Reference...................................................................................................................................................................................199
3.94 Notice on Precaution for Failure in Automatically Removing Faulty X2 Interfaces.............................................................199
3.94.1 Location.....................................................................................................................................................................................199
3.94.3 Principles...................................................................................................................................................................................200
3.94.4 Measures....................................................................................................................................................................................200
3.94.5 Reference...................................................................................................................................................................................200
3.95 Notice on Precaution for Parts of Counters Deterioration Due to Enabled DRX (Only relates to China)..........................200
3.95.1 Location.....................................................................................................................................................................................200
3.95.3 Principles...................................................................................................................................................................................201
3.95.4 Measures....................................................................................................................................................................................201
3.95.5 Reference...................................................................................................................................................................................201
3.96 Precaution Notice for a Cell Establishment Failure Because Sector Equipment Is Not Added to a Sector Equipment Group of the Cell
201
3.96.1 Location.....................................................................................................................................................................................201
3.96.3 Principles...................................................................................................................................................................................202
3.96.4 Measures....................................................................................................................................................................................202
3.96.5 Reference...................................................................................................................................................................................202
3.97 Notice on Precaution - Resetting Main Control Board Affects GSM Service Due to LTE Transmission Interrupted over 45 minutes on
Dual-Mode Base Station of SingleRAN 3900 Series (Only relates to China).................................................................................203
3.97.1 Location.....................................................................................................................................................................................203
3.97.3 Principles...................................................................................................................................................................................203
3.97.4 Measures....................................................................................................................................................................................203
3.97.5 Reference...................................................................................................................................................................................203
3.98 Notice on Precaution for FDD eNodeB - Reduced Uplink Rate of Test User Due to Enabled Uplink Scheduler Ctrl Power Switch (Only
relates to China)....................................................................................................................................................................................203
3.98.1 Location.....................................................................................................................................................................................203
3.98.3 Principles...................................................................................................................................................................................204
3.98.4 Measures....................................................................................................................................................................................204
3.98.5 Reference...................................................................................................................................................................................204
3.99 Notice on Precaution for Frequently Deactivated Supplementary Carrier When SLTE_CA UE Executes CA Services (Only relates to
China)....................................................................................................................................................................................................204
3.99.1 Location.....................................................................................................................................................................................204
3.99.3 Principles...................................................................................................................................................................................205
3.99.4 Measures....................................................................................................................................................................................205
3.99.5 Reference...................................................................................................................................................................................205
3.100 Precaution Notice for Occasional Network Access Failure after Offline FFT Frequency Scan Ends.................................205
3.100.1 Location.....................................................................................................................................................................................205
3.100.3 Principles...................................................................................................................................................................................205
3.100.4 Measures....................................................................................................................................................................................206
3.100.5 Reference...................................................................................................................................................................................206
3.101 Precaution Notice for FDD eNodeB – Disable SysTimeCfgInd While Clock Synchronization Mode Is Set to FREQ (Only relates to China)
206
3.101.1 Location.....................................................................................................................................................................................206
3.101.3 Principles...................................................................................................................................................................................207
3.101.4 Measures....................................................................................................................................................................................207
3.101.5 Reference...................................................................................................................................................................................207
3.102 Precaution Notice for Abrupt Uplink Interference Increase on LampSite LTE Base Stations............................................207
3.102.1 Location.....................................................................................................................................................................................207
3.102.3 Principles...................................................................................................................................................................................208
3.102.4 Measures....................................................................................................................................................................................208
3.102.5 Reference...................................................................................................................................................................................208
3.103 Notice on Precaution for Invalid SYNCETH Clock When the Clock Working Mode Parameter Is Set to AUTO in a Base Station 209
3.103.1 Location.....................................................................................................................................................................................209
3.103.3 Principles...................................................................................................................................................................................209
3.103.4 Measures....................................................................................................................................................................................210
3.103.5 Reference...................................................................................................................................................................................210
3.104 Notice on Precaution for LTE FDD eNodeBs – MML Command Execution Failures After an eNodeB Reset or Configuration
Reactivation in Massive X2 Links Scenarios.....................................................................................................................................210
3.104.1 Location.....................................................................................................................................................................................210
3.104.3 Principles...................................................................................................................................................................................211
3.104.4 Measures....................................................................................................................................................................................211
3.104.5 Reference...................................................................................................................................................................................212
3.105 Notice on Precaution for Repeated BBP Restarts in FDD eNodeBs Due to Subscription to the PERIOD_CELL_L2_MR Message for Cell-
Level External CHR Tracing..............................................................................................................................................................212
3.105.1 Location.....................................................................................................................................................................................212
3.105.3 Principles...................................................................................................................................................................................212
3.105.4 Measures....................................................................................................................................................................................213
3.105.5 Reference...................................................................................................................................................................................213
3.106 Notice on Precaution for Switchback to the Faulty Primary IPsec Tunnel............................................................................213
3.106.1 Location.....................................................................................................................................................................................213
3.106.3 Principles...................................................................................................................................................................................214
3.106.4 Measures....................................................................................................................................................................................214
3.106.5 Reference...................................................................................................................................................................................214
3.107 Notice on Precaution for Exceptions Occurred after Synchronizing SON Logs of FDD eNodeBs on the U2000...............215
3.107.1 Location.....................................................................................................................................................................................215
3.107.3 Principles...................................................................................................................................................................................215
3.107.4 Measures....................................................................................................................................................................................216
3.107.5 Reference...................................................................................................................................................................................216
3.108 Notice on Precaution for Restart of FDD eNodeBs That Select Target Frequencies in a Round Robin Manner during Blind Redirections
for CSFB to UTRAN............................................................................................................................................................................216
3.108.1 Location.....................................................................................................................................................................................216
3.108.3 Principles...................................................................................................................................................................................217
3.108.4 Measures....................................................................................................................................................................................217
3.108.5 Reference...................................................................................................................................................................................218
3.109 Accident Recovery Information Statistic....................................................................................................................................218
3.109.1 Location.....................................................................................................................................................................................218
3.109.3 Principles...................................................................................................................................................................................219
3.109.4 Measures....................................................................................................................................................................................220
3.109.5 Reference...................................................................................................................................................................................220
3.110 X2 Interface Configuration Check...............................................................................................................................................220
3.110.1 Location.....................................................................................................................................................................................220
3.110.3 Principles...................................................................................................................................................................................221
3.110.4 Measures....................................................................................................................................................................................222
3.110.5 Reference...................................................................................................................................................................................222
3.111 Check of Transmission Link Fault Recovery Switch.................................................................................................................222
3.111.1 Location.....................................................................................................................................................................................222
3.111.3 Principles...................................................................................................................................................................................223
3.111.4 Measures....................................................................................................................................................................................223
3.111.5 Reference...................................................................................................................................................................................223
3.112 Check of Binding Route of Master/Slave OMCH......................................................................................................................224
3.112.1 Location.....................................................................................................................................................................................224
3.112.3 Principles...................................................................................................................................................................................224
3.112.4 Measures....................................................................................................................................................................................224
3.112.5 Reference...................................................................................................................................................................................224
3.113 DSTIP of IPRT Check...................................................................................................................................................................225
3.113.1 Location.....................................................................................................................................................................................225

3.113.3 Principles...................................................................................................................................................................................225
3.113.4 Measures....................................................................................................................................................................................225
3.113.5 Reference...................................................................................................................................................................................226
3.114 BFD Session Check........................................................................................................................................................................226
3.114.1 Location.....................................................................................................................................................................................226
3.114.3 Principles...................................................................................................................................................................................226
3.114.4 Measures....................................................................................................................................................................................227
3.114.5 Reference...................................................................................................................................................................................227
3.115 Signal Plane Config Check............................................................................................................................................................227
3.115.1 Location.....................................................................................................................................................................................227
3.115.3 Principles...................................................................................................................................................................................228
3.115.4 Measures....................................................................................................................................................................................228
3.115.5 Reference...................................................................................................................................................................................228
3.116 BOOTROM Version Check..........................................................................................................................................................228
3.116.1 Location.....................................................................................................................................................................................228
3.116.3 Principles...................................................................................................................................................................................229
3.116.4 Measures....................................................................................................................................................................................230
3.116.5 Reference...................................................................................................................................................................................230
3.117 Check of MAC Excessive Frame Error Rate..............................................................................................................................230
3.117.1 Location.....................................................................................................................................................................................230
3.117.3 Principles...................................................................................................................................................................................231
3.117.4 Measures....................................................................................................................................................................................231
3.117.5 Reference...................................................................................................................................................................................231
3.118 Check of the Number of Neighboring Utran Cells.....................................................................................................................231
3.118.1 Location.....................................................................................................................................................................................231
3.118.3 Principles...................................................................................................................................................................................232
3.118.4 Measures....................................................................................................................................................................................232
3.118.5 Reference...................................................................................................................................................................................232
3.119 Check of Abnormal User Number with QCI..............................................................................................................................232
3.119.1 Location.....................................................................................................................................................................................232
3.119.3 Principles...................................................................................................................................................................................233
3.119.4 Measures....................................................................................................................................................................................233
3.119.5 Reference...................................................................................................................................................................................233
3.120 NIC Collection State Analysis......................................................................................................................................................233
3.120.1 Location.....................................................................................................................................................................................233

3.120.3 Principles...................................................................................................................................................................................234
3.120.4 Measures....................................................................................................................................................................................234
3.120.5 Reference...................................................................................................................................................................................235
3.121 SRI Resource Adaptive Adjustment............................................................................................................................................235
3.121.1 Location.....................................................................................................................................................................................235
3.121.3 Principles...................................................................................................................................................................................235
3.121.4 Measures....................................................................................................................................................................................235
3.121.5 Reference...................................................................................................................................................................................236
3.122 PUCCH Resource Adjustment Algorithm..................................................................................................................................236
3.122.1 Location.....................................................................................................................................................................................236
3.122.3 Principles...................................................................................................................................................................................236
3.122.4 Measures....................................................................................................................................................................................237
3.122.5 Reference...................................................................................................................................................................................237
3.123 CQI Period Adaptive Adjustment...............................................................................................................................................237
3.123.1 Location.....................................................................................................................................................................................237
3.123.3 Principles...................................................................................................................................................................................237
3.123.4 Measures....................................................................................................................................................................................238
3.123.5 Reference...................................................................................................................................................................................238
3.124 SRS Period Adaptive Adjustment................................................................................................................................................238
3.124.1 Location.....................................................................................................................................................................................238
3.124.3 Principles...................................................................................................................................................................................239
3.124.4 Measures....................................................................................................................................................................................239
3.124.5 Reference...................................................................................................................................................................................239
3.125 SRS Subframe RECF Switch Adjustment..................................................................................................................................239
3.125.1 Location.....................................................................................................................................................................................239
3.125.3 Principles...................................................................................................................................................................................240
3.125.4 Measures....................................................................................................................................................................................240
3.125.5 Reference...................................................................................................................................................................................240
3.126 Recover SrsSubframeCfg to Default Value................................................................................................................................240
3.126.1 Location.....................................................................................................................................................................................240
3.126.3 Principles...................................................................................................................................................................................241
3.126.4 Measures....................................................................................................................................................................................241
3.126.5 Reference...................................................................................................................................................................................241
3.127 Extend T302 to 16s.........................................................................................................................................................................242
3.127.1 Location.....................................................................................................................................................................................242

3.127.3 Principles...................................................................................................................................................................................242
3.127.4 Measures....................................................................................................................................................................................242
3.127.5 Reference...................................................................................................................................................................................243
3.128 Disable FAST ANR........................................................................................................................................................................243
3.128.1 Location.....................................................................................................................................................................................243
3.128.3 Principles...................................................................................................................................................................................243
3.128.4 Measures....................................................................................................................................................................................244
3.128.5 Reference...................................................................................................................................................................................244
3.129 Disable DRX...................................................................................................................................................................................244
3.129.1 Location.....................................................................................................................................................................................244
3.129.3 Principles...................................................................................................................................................................................245
3.129.4 Measures....................................................................................................................................................................................245
3.129.5 Reference...................................................................................................................................................................................245
3.130 Increase Intra-Freq A3 Threshold to 5DB..................................................................................................................................245
3.130.1 Location.....................................................................................................................................................................................245
3.130.3 Principles...................................................................................................................................................................................246
3.130.4 Measures....................................................................................................................................................................................246
3.130.5 Reference...................................................................................................................................................................................246
3.131 Randomize UL Interference.........................................................................................................................................................246
3.131.1 Location.....................................................................................................................................................................................246
3.131.3 Principles...................................................................................................................................................................................247
3.131.4 Measures....................................................................................................................................................................................247
3.131.5 Reference...................................................................................................................................................................................247
3.132 PUCCH IRC Algorithm Switch...................................................................................................................................................248
3.132.1 Location.....................................................................................................................................................................................248
3.132.3 Principles...................................................................................................................................................................................248
3.132.4 Measures....................................................................................................................................................................................248
3.132.5 Reference...................................................................................................................................................................................249
3.133 Disable DL Frequency Selection..................................................................................................................................................249
3.133.1 Location.....................................................................................................................................................................................249
3.133.3 Principles...................................................................................................................................................................................249
3.133.4 Measures....................................................................................................................................................................................249
3.133.5 Reference...................................................................................................................................................................................250
3.134 Enable UL COMP..........................................................................................................................................................................250
3.134.1 Location.....................................................................................................................................................................................250

3.134.3 Principles...................................................................................................................................................................................250
3.134.4 Measures....................................................................................................................................................................................251
3.134.5 Reference...................................................................................................................................................................................251
3.135 Reduce Power Control Initial Value P0 of PUSCH and PUCCH............................................................................................251
3.135.1 Location.....................................................................................................................................................................................251
3.135.3 Principles...................................................................................................................................................................................252
3.135.4 Measures....................................................................................................................................................................................252
3.135.5 Reference...................................................................................................................................................................................252
3.136 Reduce PUSCH Power Control Initial Value P0........................................................................................................................253
3.136.1 Location.....................................................................................................................................................................................253
3.136.3 Principles...................................................................................................................................................................................253
3.136.4 Measures....................................................................................................................................................................................253
3.136.5 Reference...................................................................................................................................................................................254
3.137 Limit PUSCH RSRP Upper Threshold.......................................................................................................................................254
3.137.1 Location.....................................................................................................................................................................................254
3.137.3 Principles...................................................................................................................................................................................254
3.137.4 Measures....................................................................................................................................................................................254
3.137.5 Reference...................................................................................................................................................................................255
3.138 Shorten the Period of PUCCH Power Control...........................................................................................................................255
3.138.1 Location.....................................................................................................................................................................................255
3.138.3 Principles...................................................................................................................................................................................255
3.138.4 Measures....................................................................................................................................................................................256
3.138.5 Reference...................................................................................................................................................................................256
3.139 Uplift PucchPcTargetSinrOffset..................................................................................................................................................256
3.139.1 Location.....................................................................................................................................................................................256
3.139.3 Principles...................................................................................................................................................................................256
3.139.4 Measures....................................................................................................................................................................................257
3.139.5 Reference...................................................................................................................................................................................257
3.140 Enable PucchPcDtxSinrSwitch....................................................................................................................................................257
3.140.1 Location.....................................................................................................................................................................................257
3.140.3 Principles...................................................................................................................................................................................258
3.140.4 Measures....................................................................................................................................................................................258
3.140.5 Reference...................................................................................................................................................................................258
3.141 Optimization of P0 Nominal PUCCH..........................................................................................................................................258
3.141.1 Location.....................................................................................................................................................................................258

3.141.3 Principles...................................................................................................................................................................................259
3.141.4 Measures....................................................................................................................................................................................259
3.141.5 Reference...................................................................................................................................................................................259
3.142 PucchCloseLoopPcType and P0 Optimization...........................................................................................................................259
3.142.1 Location.....................................................................................................................................................................................259
3.142.3 Principles...................................................................................................................................................................................260
3.142.4 Measures....................................................................................................................................................................................260
3.142.5 Reference...................................................................................................................................................................................260
3.143 Increase PUCCH DeltaShift.........................................................................................................................................................261
3.143.1 Location.....................................................................................................................................................................................261
3.143.3 Principles...................................................................................................................................................................................261
3.143.4 Measures....................................................................................................................................................................................261
3.143.5 Reference...................................................................................................................................................................................262
3.144 Fixed Configuration of PUCCH Resource..................................................................................................................................262
3.144.1 Location.....................................................................................................................................................................................262
3.144.3 Principles...................................................................................................................................................................................264
3.144.4 Measures....................................................................................................................................................................................265
3.144.5 Reference...................................................................................................................................................................................265
3.145 Reset PDCP DiscardTimer to Default Value When Timeout...................................................................................................266
3.145.1 Location.....................................................................................................................................................................................266
3.145.3 Principles...................................................................................................................................................................................266
3.145.4 Measures....................................................................................................................................................................................267
3.145.5 Reference...................................................................................................................................................................................267
3.146 PUSCH DTX Supported Check...................................................................................................................................................267
3.146.1 Location.....................................................................................................................................................................................267
3.146.3 Principles...................................................................................................................................................................................268
3.146.4 Measures....................................................................................................................................................................................268
3.146.5 Reference...................................................................................................................................................................................268
3.147 Optimization of SR Rescheduling................................................................................................................................................268
3.147.1 Location.....................................................................................................................................................................................268
3.147.3 Principles...................................................................................................................................................................................269
3.147.4 Measures....................................................................................................................................................................................269
3.147.5 Reference...................................................................................................................................................................................269
3.148 Lower Retransmission Overhead of Special Signaling..............................................................................................................270
3.148.1 Location.....................................................................................................................................................................................270

3.148.3 Principles...................................................................................................................................................................................270
3.148.4 Measures....................................................................................................................................................................................271
3.148.5 Reference...................................................................................................................................................................................271
3.149 Solve UE Lost Scheduling Problems............................................................................................................................................271
3.149.1 Location.....................................................................................................................................................................................271
3.149.3 Principles...................................................................................................................................................................................272
3.149.4 Measures....................................................................................................................................................................................272
3.149.5 Reference...................................................................................................................................................................................272
3.150 DRB RLC Parameter Adaptive....................................................................................................................................................272
3.150.1 Location.....................................................................................................................................................................................272
3.150.3 Principles...................................................................................................................................................................................273
3.150.4 Measures....................................................................................................................................................................................273
3.150.5 Reference...................................................................................................................................................................................273
3.151 Round UP RBG..............................................................................................................................................................................274
3.151.1 Location.....................................................................................................................................................................................274
3.151.3 Principles...................................................................................................................................................................................274
3.151.4 Measures....................................................................................................................................................................................274
3.151.5 Reference...................................................................................................................................................................................275
3.152 Balanced Scheduling between PDCCH & PDSCH....................................................................................................................275
3.152.1 Location.....................................................................................................................................................................................275
3.152.3 Principles...................................................................................................................................................................................275
3.152.4 Measures....................................................................................................................................................................................276
3.152.5 Reference...................................................................................................................................................................................276
3.153 PDCCH Efficiency Improvement in Initial Stage......................................................................................................................276
3.153.1 Location.....................................................................................................................................................................................276
3.153.3 Principles...................................................................................................................................................................................277
3.153.4 Measures....................................................................................................................................................................................277
3.153.5 Reference...................................................................................................................................................................................277
3.154 Adaptive RBG................................................................................................................................................................................277
3.154.1 Location.....................................................................................................................................................................................277
3.154.3 Principles...................................................................................................................................................................................278
3.154.4 Measures....................................................................................................................................................................................278
3.154.5 Reference...................................................................................................................................................................................278
3.155 Increase Priority of Access Signaling Scheduling......................................................................................................................279
3.155.1 Location.....................................................................................................................................................................................279

3.155.3 Principles...................................................................................................................................................................................279
3.155.4 Measures....................................................................................................................................................................................279
3.155.5 Reference...................................................................................................................................................................................280
3.156 Avoid the Conflict of GAP Measurement and SR when DRX Is Disabled..............................................................................280
3.156.1 Location.....................................................................................................................................................................................280
3.156.3 Principles...................................................................................................................................................................................280
3.156.4 Measures....................................................................................................................................................................................281
3.156.5 Reference...................................................................................................................................................................................281
3.157 Avoid the Conflict of GAP Measurement and SR when DRX Is Enabled..............................................................................281
3.157.1 Location.....................................................................................................................................................................................281
3.157.3 Principles...................................................................................................................................................................................282
3.157.4 Measures....................................................................................................................................................................................282
3.157.5 Reference...................................................................................................................................................................................282
3.158 Non High-Speed Railway Scenario..............................................................................................................................................283
3.158.1 Location.....................................................................................................................................................................................283
3.158.3 Principles...................................................................................................................................................................................286
3.158.4 Measures....................................................................................................................................................................................288
3.158.5 Reference...................................................................................................................................................................................289
3.159 High-Speed Railway Scenario......................................................................................................................................................289
3.159.1 Location.....................................................................................................................................................................................289
3.159.3 Principles...................................................................................................................................................................................292
3.159.4 Measures....................................................................................................................................................................................293
3.159.5 Reference...................................................................................................................................................................................293
3.160 Enable SRS.....................................................................................................................................................................................293
3.160.1 Location.....................................................................................................................................................................................293
3.160.3 Principles...................................................................................................................................................................................294
3.160.4 Measures....................................................................................................................................................................................294
3.160.5 Reference...................................................................................................................................................................................294
3.161 QCI1 RLC/PDCP SN Size Optimization.....................................................................................................................................294
3.161.1 Location.....................................................................................................................................................................................294
3.161.3 Principles...................................................................................................................................................................................295
3.161.4 Measures....................................................................................................................................................................................295
3.161.5 Reference...................................................................................................................................................................................295
3.162 QCI5 PDCP Timer Optimization.................................................................................................................................................296
3.162.1 Location.....................................................................................................................................................................................296

3.162.3 Principles...................................................................................................................................................................................296
3.162.4 Measures....................................................................................................................................................................................296
3.162.5 Reference...................................................................................................................................................................................297
3.163 Uplink RLC Enhanced in Segments............................................................................................................................................297
3.163.1 Location.....................................................................................................................................................................................297
3.163.3 Principles...................................................................................................................................................................................297
3.163.4 Measures....................................................................................................................................................................................297
3.163.5 Reference...................................................................................................................................................................................298
3.164 Uplink Last Two Retransmission Schedule Optimization........................................................................................................298
3.164.1 Location.....................................................................................................................................................................................298
3.164.3 Principles...................................................................................................................................................................................298
3.164.4 Measures....................................................................................................................................................................................298
3.164.5 Reference...................................................................................................................................................................................299
3.165 Uplink Compensation Schedule...................................................................................................................................................299
3.165.1 Location.....................................................................................................................................................................................299
3.165.3 Principles...................................................................................................................................................................................299
3.165.4 Measures....................................................................................................................................................................................300
3.165.5 Reference...................................................................................................................................................................................300
3.166 Uplink Delay-based Dynamic Scheduling...................................................................................................................................300
3.166.1 Location.....................................................................................................................................................................................300
3.166.3 Principles...................................................................................................................................................................................300
3.166.4 Measures....................................................................................................................................................................................301
3.166.5 Reference...................................................................................................................................................................................301
3.167 Optimization of Uplink Data Size Estimation............................................................................................................................301
3.167.1 Location.....................................................................................................................................................................................301
3.167.3 Principles...................................................................................................................................................................................301
3.167.4 Measures....................................................................................................................................................................................302
3.167.5 Reference...................................................................................................................................................................................302
3.168 ROHC..............................................................................................................................................................................................302
3.168.1 Location.....................................................................................................................................................................................302
3.168.3 Principles...................................................................................................................................................................................302
3.168.4 Measures....................................................................................................................................................................................303
3.168.5 Reference...................................................................................................................................................................................303
3.169 TTI Bundling..................................................................................................................................................................................303
3.169.1 Location.....................................................................................................................................................................................303

3.169.3 Principles...................................................................................................................................................................................304
3.169.4 Measures....................................................................................................................................................................................304
3.169.5 Reference...................................................................................................................................................................................304
3.170 SPS...................................................................................................................................................................................................304
3.170.1 Location.....................................................................................................................................................................................304
3.170.3 Principles...................................................................................................................................................................................305
3.170.4 Measures....................................................................................................................................................................................305
3.170.5 Reference...................................................................................................................................................................................305
3.171 Downlink Last Two Retransmission Schedule Optimization....................................................................................................305
3.171.1 Location.....................................................................................................................................................................................305
3.171.3 Principles...................................................................................................................................................................................306
3.171.4 Measures....................................................................................................................................................................................306
3.171.5 Reference...................................................................................................................................................................................306
3.172 TBS-Based Scheduling for Downlink VoIP................................................................................................................................306
3.172.1 Location.....................................................................................................................................................................................306
3.172.3 Principles...................................................................................................................................................................................307
3.172.4 Measures....................................................................................................................................................................................307
3.172.5 Reference...................................................................................................................................................................................307
3.173 Preallocation & SmartPreallocation............................................................................................................................................307
3.173.1 Location.....................................................................................................................................................................................307
3.173.3 Principles...................................................................................................................................................................................308
3.173.4 Measures....................................................................................................................................................................................309
3.173.5 Reference...................................................................................................................................................................................309
3.174 Enhanced Preallocation for VOIP...............................................................................................................................................309
3.174.1 Location.....................................................................................................................................................................................309
3.174.3 Principles...................................................................................................................................................................................310
3.174.4 Measures....................................................................................................................................................................................310
3.174.5 Reference...................................................................................................................................................................................310
3.175 Debug Log Analysis.......................................................................................................................................................................310
3.175.1 Location.....................................................................................................................................................................................310
3.175.3 Principles...................................................................................................................................................................................311
3.175.4 Measures....................................................................................................................................................................................311
3.175.5 Reference...................................................................................................................................................................................311
3.176 FPGA Hard Failure Check...........................................................................................................................................................311
3.176.1 Location.....................................................................................................................................................................................311

3.176.3 Principles...................................................................................................................................................................................312
3.176.4 Measures....................................................................................................................................................................................313
3.176.5 Reference...................................................................................................................................................................................313
3.177 RRU Input Power Is Too High.....................................................................................................................................................313
3.177.1 Location.....................................................................................................................................................................................313
3.177.3 Principles...................................................................................................................................................................................314
3.177.4 Measures....................................................................................................................................................................................315
3.177.5 Reference...................................................................................................................................................................................315
3.178 Check of RF Unit Tx Channel Gain............................................................................................................................................315
3.178.1 Location.....................................................................................................................................................................................315
3.178.3 Principles...................................................................................................................................................................................316
3.178.4 Measures....................................................................................................................................................................................317
3.178.5 Reference...................................................................................................................................................................................317
3.179 Check of RF Unit PA Current......................................................................................................................................................317
3.179.1 Location.....................................................................................................................................................................................317
3.179.3 Principles...................................................................................................................................................................................318
3.179.4 Measures....................................................................................................................................................................................319
3.179.5 Reference...................................................................................................................................................................................319
3.180 RF Unit Clock Check.....................................................................................................................................................................319
3.180.1 Location.....................................................................................................................................................................................319
3.180.3 Principles...................................................................................................................................................................................320
3.180.4 Measures....................................................................................................................................................................................321
3.180.5 Reference...................................................................................................................................................................................321
3.181 RF Unit Hardware Check.............................................................................................................................................................321
3.181.1 Location.....................................................................................................................................................................................321
3.181.3 Principles...................................................................................................................................................................................322
3.181.4 Measures....................................................................................................................................................................................323
3.181.5 Reference...................................................................................................................................................................................323
3.182 Power Voltage of RF Unit Check.................................................................................................................................................323
3.182.1 Location.....................................................................................................................................................................................323
3.182.3 Principles...................................................................................................................................................................................324
3.182.4 Measures....................................................................................................................................................................................325
3.182.5 Reference...................................................................................................................................................................................325
3.183 CANBUS Communication Failure Check...................................................................................................................................325
3.183.1 Location.....................................................................................................................................................................................325

3.183.3 Principles...................................................................................................................................................................................326
3.183.4 Measures....................................................................................................................................................................................326
3.183.5 Reference...................................................................................................................................................................................326
3.184 SON Temporary File Check.........................................................................................................................................................326
3.184.1 Location.....................................................................................................................................................................................326
3.184.3 Principles...................................................................................................................................................................................327
3.184.4 Measures....................................................................................................................................................................................327
3.184.5 Reference...................................................................................................................................................................................327
3.185 DRX Inspection Rule.....................................................................................................................................................................327
3.185.1 Location.....................................................................................................................................................................................327
3.185.3 Principles...................................................................................................................................................................................328
3.185.4 Measures....................................................................................................................................................................................332
3.185.5 Reference...................................................................................................................................................................................332
3.186 Summary of Risky Parameter Verification................................................................................................................................332
3.186.1 Location.....................................................................................................................................................................................332
3.186.3 Principles...................................................................................................................................................................................333
3.186.4 Measures....................................................................................................................................................................................333
3.186.5 Reference...................................................................................................................................................................................333
3.187 PDCCH Algorithm Parameter.....................................................................................................................................................333
3.187.1 Location.....................................................................................................................................................................................333
3.187.3 Principles...................................................................................................................................................................................334
3.187.4 Measures....................................................................................................................................................................................334
3.187.5 Reference...................................................................................................................................................................................334
3.188 eNodeB Algorithm Switch.............................................................................................................................................................334
3.188.1 Location.....................................................................................................................................................................................334
3.188.3 Principles...................................................................................................................................................................................335
3.188.4 Measures....................................................................................................................................................................................335
3.188.5 Reference...................................................................................................................................................................................336
3.189 Global Procedure Switch..............................................................................................................................................................336
3.189.1 Location.....................................................................................................................................................................................336
3.189.3 Principles...................................................................................................................................................................................336
3.189.4 Measures....................................................................................................................................................................................336
3.189.5 Reference...................................................................................................................................................................................337
3.190 PCCH Configuration Information...............................................................................................................................................337
3.190.1 Location.....................................................................................................................................................................................337

3.190.3 Principles...................................................................................................................................................................................337
3.190.4 Measures....................................................................................................................................................................................337
3.190.5 Reference...................................................................................................................................................................................338
3.191 PUCCH Dynamic Configuration Information...........................................................................................................................338
3.191.1 Location.....................................................................................................................................................................................338
3.191.3 Principles...................................................................................................................................................................................338
3.191.4 Measures....................................................................................................................................................................................339
3.191.5 Reference...................................................................................................................................................................................339
3.192 RACH Dynamic Configuration Information..............................................................................................................................339
3.192.1 Location.....................................................................................................................................................................................339
3.192.3 Principles...................................................................................................................................................................................340
3.192.4 Measures....................................................................................................................................................................................340
3.192.5 Reference...................................................................................................................................................................................340
3.193 RLC and PDCP Parameter Group..............................................................................................................................................340
3.193.1 Location.....................................................................................................................................................................................340
3.193.3 Principles...................................................................................................................................................................................341
3.193.4 Measures....................................................................................................................................................................................341
3.193.5 Reference...................................................................................................................................................................................342
3.194 UE Controller Timer Configuration............................................................................................................................................342
3.194.1 Location.....................................................................................................................................................................................342
3.194.3 Principles...................................................................................................................................................................................342
3.194.4 Measures....................................................................................................................................................................................342
3.194.5 Reference...................................................................................................................................................................................343
3.195 Summary of Performance Optimized Parameter Verification.................................................................................................343
3.195.1 Location.....................................................................................................................................................................................343
3.195.3 Principles...................................................................................................................................................................................343
3.195.4 Measures....................................................................................................................................................................................343
3.195.5 Reference...................................................................................................................................................................................344
3.196 Cell Algorithm Switch...................................................................................................................................................................344
3.196.1 Location.....................................................................................................................................................................................344
3.196.3 Principles...................................................................................................................................................................................346
3.196.4 Measures....................................................................................................................................................................................347
3.196.5 Reference...................................................................................................................................................................................347
3.197 Cell CQI Adaptive Parameter Configuration.............................................................................................................................348
3.197.1 Location.....................................................................................................................................................................................348

3.197.3 Principles...................................................................................................................................................................................348
3.197.4 Measures....................................................................................................................................................................................349
3.197.5 Reference...................................................................................................................................................................................349
3.198 Cell Downlink Scheduling Parameter.........................................................................................................................................349
3.198.1 Location.....................................................................................................................................................................................349
3.198.3 Principles...................................................................................................................................................................................350
3.198.4 Measures....................................................................................................................................................................................350
3.198.5 Reference...................................................................................................................................................................................350
3.199 Cell Power Control Algorithm Parameter..................................................................................................................................350
3.199.1 Location.....................................................................................................................................................................................350
3.199.3 Principles...................................................................................................................................................................................351
3.199.4 Measures....................................................................................................................................................................................351
3.199.5 Reference...................................................................................................................................................................................351
3.200 PDCCH Algorithm Parameter.....................................................................................................................................................352
3.200.1 Location.....................................................................................................................................................................................352
3.200.3 Principles...................................................................................................................................................................................352
3.200.4 Measures....................................................................................................................................................................................352
3.200.5 Reference...................................................................................................................................................................................352
3.201 SRS Adaptive Parameter Configuration.....................................................................................................................................353
3.201.1 Location.....................................................................................................................................................................................353
3.201.3 Principles...................................................................................................................................................................................353
3.201.4 Measures....................................................................................................................................................................................354
3.201.5 Reference...................................................................................................................................................................................354
3.202 Cell Uplink Scheduling Parameter..............................................................................................................................................354
3.202.1 Location.....................................................................................................................................................................................354
3.202.3 Principles...................................................................................................................................................................................355
3.202.4 Measures....................................................................................................................................................................................355
3.202.5 Reference...................................................................................................................................................................................355
3.203 TimeAlignmentTimer....................................................................................................................................................................355
3.203.1 Location.....................................................................................................................................................................................355
3.203.3 Principles...................................................................................................................................................................................356
3.203.4 Measures....................................................................................................................................................................................356
3.203.5 Reference...................................................................................................................................................................................356
3.204 UE Timer & Constant Information.............................................................................................................................................357
3.204.1 Location.....................................................................................................................................................................................357

3.204.3 Principles...................................................................................................................................................................................357
3.204.4 Measures....................................................................................................................................................................................357
3.204.5 Reference...................................................................................................................................................................................358
3.205 Intra-frequency Cells Are Not in the Same BBP........................................................................................................................358
3.205.1 Location.....................................................................................................................................................................................358
3.205.3 Principles...................................................................................................................................................................................358
3.205.4 Measures....................................................................................................................................................................................359
3.205.5 Reference...................................................................................................................................................................................359
3.206 Inter-frequency Cells Are Under Same LBBPC........................................................................................................................359
3.206.1 Location.....................................................................................................................................................................................359
3.206.3 Principles...................................................................................................................................................................................359
3.206.4 Measures....................................................................................................................................................................................360
3.206.5 Reference...................................................................................................................................................................................360
3.207 Inter-frequency Cells’ LBBPd and UBBP Are Not in Slot 2/3.................................................................................................360
3.207.1 Location.....................................................................................................................................................................................360
3.207.3 Principles...................................................................................................................................................................................361
3.207.4 Measures....................................................................................................................................................................................361
3.207.5 Reference...................................................................................................................................................................................361
3.208 The RRU Platform of Inter-frequency Are Not Same Check...................................................................................................361
3.208.1 Location.....................................................................................................................................................................................361
3.208.3 Principles...................................................................................................................................................................................362
3.208.4 Measures....................................................................................................................................................................................362
3.208.5 Reference...................................................................................................................................................................................362
3.209 BasedSriGapOptSwitch Check....................................................................................................................................................363
3.209.1 Location.....................................................................................................................................................................................363
3.209.3 Principles...................................................................................................................................................................................363
3.209.4 Measures....................................................................................................................................................................................363
3.209.5 Reference...................................................................................................................................................................................364
3.210 DrxBasedSriGapOptSwitch Check..............................................................................................................................................364
3.210.1 Location.....................................................................................................................................................................................364
3.210.3 Principles...................................................................................................................................................................................364
3.210.4 Measures....................................................................................................................................................................................365
3.210.5 Reference...................................................................................................................................................................................365
3.211 MeasCycleSCell Check..................................................................................................................................................................365
3.211.1 Location.....................................................................................................................................................................................365

3.211.3 Principles...................................................................................................................................................................................366
3.211.4 Measures....................................................................................................................................................................................366
3.211.5 Reference...................................................................................................................................................................................366
3.212 ApCqiRptAbnormalCtrlSwitch Check.......................................................................................................................................366
3.212.1 Location.....................................................................................................................................................................................366
3.212.3 Principles...................................................................................................................................................................................367
3.212.4 Measures....................................................................................................................................................................................367
3.212.5 Reference...................................................................................................................................................................................367
3.213 DrxRcvDtxProSwitch Check........................................................................................................................................................368
3.213.1 Location.....................................................................................................................................................................................368
3.213.3 Principles...................................................................................................................................................................................368
3.213.4 Measures....................................................................................................................................................................................369
3.213.5 Reference...................................................................................................................................................................................369
3.214 CaGapMeasPriOffSwitch Check.................................................................................................................................................369
3.214.1 Location.....................................................................................................................................................................................369
3.214.3 Principles...................................................................................................................................................................................370
3.214.4 Measures....................................................................................................................................................................................370
3.214.5 Reference...................................................................................................................................................................................370
3.215 SCellModCaMeasRmvSwitch Check..........................................................................................................................................370
3.215.1 Location.....................................................................................................................................................................................370
3.215.3 Principles...................................................................................................................................................................................371
3.215.4 Measures....................................................................................................................................................................................371
3.215.5 Reference...................................................................................................................................................................................371
3.216 Check of CA UE Chose Mode......................................................................................................................................................372
3.216.1 Location.....................................................................................................................................................................................372
3.216.3 Principles...................................................................................................................................................................................372
3.216.4 Measures....................................................................................................................................................................................372
3.216.5 Reference...................................................................................................................................................................................372
3.217 CaCqiAndAckAbnCtrlSwitch Check..........................................................................................................................................373
3.217.1 Location.....................................................................................................................................................................................373
3.217.3 Principles...................................................................................................................................................................................373
3.217.4 Measures....................................................................................................................................................................................373
3.217.5 Reference...................................................................................................................................................................................373
3.218 SCC Quiet Time Check.................................................................................................................................................................374
3.218.1 Location.....................................................................................................................................................................................374

3.218.3 Principles...................................................................................................................................................................................374
3.218.4 Measures....................................................................................................................................................................................374
3.218.5 Reference...................................................................................................................................................................................374
3.219 Risky Parameter Verification.......................................................................................................................................................375
3.219.1 Location.....................................................................................................................................................................................375
3.219.3 Principles...................................................................................................................................................................................375
3.219.4 Measures....................................................................................................................................................................................375
3.219.5 Reference...................................................................................................................................................................................376
3.220 Performance Optimized Parameter Verification.......................................................................................................................376
3.220.1 Location.....................................................................................................................................................................................376
3.220.3 Principles...................................................................................................................................................................................377
3.220.4 Measures....................................................................................................................................................................................377
3.220.5 Reference...................................................................................................................................................................................377

2 Overview
1.1 Details
This guidance has introduced all LTE Inspection SOP rules (220 rules) and corresponding measures and suggestions can be found too. This
guidance can help the readers to understand the rules and inspection reports better, and increase the efficiency of analyzing problems.
The method of how to implement deploy MAINEX operation and maintenance tools (NIC and Standalone OMStar-E) to complete network
inspection automatically is not in this guidance. Please refer to the 《OMStar_E_V500R011_ Inspection SOP Guidance》published by OMStar to find the
details.
1.2 Intended Audience
It is applicable for L1 who are in charge of the routine SOP inspection, L2 who are in charge of SOP promotion and new L2 who are in charge of
development and maintenance.
1.3 Application Scope
 This guidance is applicable for the following NE versions.
SingleRAN versions eRAN versions

BTS/DBS3900 V100R008C00 BTS/DBS3900 eRAN 6.0
PICO BTS3911B V100R10C11

 PICO V100R010C11 is applicable for PICO BTS3911B inspection, which includes Active Alarm Analysis, Historical Alarm Analysis,
RRC Setup Success Rate and eRAB Setup Success Rate rules.
 This guidance is applicable for SOP R11.1.4 version.
 This guidance doesn’t contain the rules in the “Safety Check”.
 This guidance uses eRAN version number to show the version number.
 As far as the “Location”, same rules in different versions may in different locations. Since there are same and different rules in different
versions.
 Pay attention to the red part.
2.1.1 Update
This guidance is published with the SOP versions synchronously and it is updated by SOP maintenance group periodically.
2.1.2 Revision compared with R11.0.1
Parameter No. Name of Evaluation Item Description

1 Notice on Precaution for Invalid SYNCETH New Precaution.
Clock When the Clock Working Mode Parameter
New Is Set to AUTO in a Base Station

Features 2 Notice on Precaution for Repeated BBP Restarts New Precaution.
in FDD eNodeBs Due to Subscription to the
PERIOD_CELL_L2_MR Message for Cell-Level
External CHR Tracing

3 Notice on Precaution for LTE FDD eNodeBs – New Precaution.
MML Command Execution Failures After an
eNodeB Reset or Configuration Reactivation in
Massive X2 Links Scenarios

4 Notice on Precaution for Switchback to the New Precaution.
Faulty Primary IPsec Tunnel

5 Notice on Precaution for Exceptions Occurred New Precaution.
after Synchronizing SON Logs of FDD eNodeBs

on the U2000
6 Notice on Precaution for Restart of FDD New Precaution.
eNodeBs That Select Target Frequencies in a
Round Robin Manner during Blind Redirections
for CSFB to UTRAN
7 New manual precaution in
Notice on Precaution for LTE FDD eNodeBs – parts of support

Degenerate RRU Setup Success Rate Due to
“Extra-Low Load ” State for Long Time precaution notices which
need manual check.

8 New manual precaution in
Notice on Precaution for LTE FDD eNodeBs – parts of support

Ineffective MME Load Balance Due to Excessive
MMEC precaution notices which
need manual check.

9 Add “Subject Summary”
subject to count the
number of exceptions of
each rule under risky
Subject Summary
parameter verification
subject and performance
optimized parameter
verification subject.
10 “Big Traffic” Module Applicable for eRAN11.1.
11 “DRX” Module Applicable for eRAN11.1.
12 Update debug log error
Debug Log
rate in eRAN11.1.
13 1.Add the statistics of
abnormal times of each
CPU Load Evaluation board (MPT and BBP).
Optimize 2. Delete the statistics of
d abnormal WBBP boards.
Features 14 1. Delete tables of
normal configurations.
Clock Configuration Check
2. Add clock source check
(abnormal) table.
15 Historical Alarms Analysis Extend Top10 eNodeBs
to Top20.
16 Check of Blind HO (redirection) Priority of Inter- 1. Add the adjustment for
RAT Neighboring Cell CDMA neighboring

system.
2.Optimize the exception
output to distinguish the
abnormal configuration
of blind handover priority
and connected priority.
17 Add a judgment of the
BOOTROM version for
BOOTROM Version Check
different RRU boards and
output the exception.
18 Add a judgment based on
EP model and link model
IPPATH Check
in eRAN8.1 and its later
versions.
19 Optimize license
User Number
allocation algorithm.
20 Add the statistic of
Board Statistics
UNKOWN boards.
Deleted 21 Delete eRAN3.0 and
Delete eRAN3.0 and eRAN3.1 versions.
Versions eRAN3.1 related rules.
Adapted 22 Add inspection scenario
Add inspection scenario for PICO V100R010C11
Scenarios for PICO V100R010C11
version.
version.
23 Include VOLTE, DRX,
Add feature inspection scenario. Parameter Verification
and CA inspection.

3 Rule Description
3.1 Network Health Indicator
1.3.1 Location
Check Item Type Sub Item Item Name

01 Network Health Indicator 01 Network Health Indicator 01 Network Health Indicator
1.3.2 Rules Description
According to the number of exceptions and their severities, network health can be quantized to a specific score to reflect the overall condition of
the network directly. This rule is mainly used to collect network health’s related information.
1) Output health evaluation score in the entire network.
Network Health Evaluation

Category Check Item Score Recommendation Remark
Cell State 92.75 Please Keep It On 　
Equipment Configuration Check 66.67 Please Optimize It Immediately 　
State Check Equipment Running State 6.67 Please Solve It Immediately 　

Equipment Load 100.00 Please Keep It On 　
RRC Setup Success Rate 84.10 Please Keep Optimizing It 　
eRAB Setup Success Rate 96.92 Please Keep It On 　
KPI
Call Drop Rate 75.87 Please Optimize It Immediately 　
Handover Success Rate 82.35 Please Keep Optimizing It 　
Total Score 73.41 　　
2) According to the score of the network health evaluation, output TOP Problem List (If the problem number is less than 10, output all of them.)
TOP Problem List

No. Item Name Severity Cause Recommendation
1 01 Active Alarm Critical 1. Critical: 0 If this alarm occurs, solve it based on the
Analysis 2. Major: 92. Alarm Help.

3. The name of TOP3 is SCTP
link fault alarm(X2).

02 Inter-eNB Handover
2 Critical 98.89% Contact HUAWEI engineers.
Success Rate
05 Inter-freq Handover
3 Major 99.27% Contact HUAWEI engineers.
Success Rate
4 01 Drop Call Rate Major 0.84% Contact HUAWEI engineers.
02 Unavailable cell Try to activate the cell again. If it doesn’t

5 Major The number of unavailable cell is 2.
Check work, contact HUAWEI engineers.
1.3.3 Principles
1) “Network Health Evaluation” table: Set 8 items and give each item an initial score. The total score is 100. For each item, reduce its score
independently according to its issue until to 0. Add up the left score of the 8 items and get the final score. Score rate is the ratio of the actual
score to the initial score. If certain item participates into calculating but is not selected in this inspection, set the final score to its initial score.
Every item’s score is converted into actual score*100/initial score and then output. The principles of scoring are in the below table.
Item Sub Item Principle of Scoring
Unavailable Cell The initial score is 5. If the ratio of unavailable cell number to the total cell number increases 0.1%, reduce 0.5.
Seeping Cell The initial score is 5. The ratio of the sleeping cell number to the total cell number increases 0.1%, reduce 1.
Cell State
The initial score is 5. The ratio of the abnormal paging cell number to the total cell number increases 0.1%, reduce
Paging Performance
0.5.
Configuratio The initial score is 10. The actual score = initial score* (1-m/n). m stands for abnormal cell number and n stands for
Configuration Check
n Check total cell number.
Hot Patch State The initial score is 1. The actual score = initial score* (1-m/n). m stands for abnormal number of eNodeBs and n
Equipment
and License Running State stands for total number of eNodeBs.
Running
The initial score is 14. The ratio of the eNodeB number with major active alarms to the total eNodeB number rises
State Active Alarm
0.1%, reduce 0.14. Reduce 1 if 1 critical alarm occurs.
Uu Interface Resource The initial score is 5.The ratio of (Cell number whose L.RRC.SetupFail.ResFail is not 0 + Cell number whose L.E-
Congestion RAB.FailEst.NoRadioRes is not 0) to the entire network’s total cell number rises 0.1%, reduce 0.1.
Equipment
The initial score is 5. The actual score = 5-((the LMPT, UMPT number with average CPU usage between 50% ~
Load
CPU Load Evaluation 70%/ LMPT, UMPT number)* 0.05/0.001 + (LMPT, UMPT number with average CPU usage between 70% ~
100%/ LMPT, UMPT number)* 0.10/0.001 + (LBBP number with average CPU usage between 50% ~ 70%/LBBP

number)* 0.05/0.001 + (LBBP number with average CPU usage between 70% ~ 100%/LBBP number)
*0.10/0.001).
RRC Setup Success Rate Both of the initial score is 10. Add up the traffic measurement within the inspection period and get the total RRC /
eRAB setup success rate. From 100% on, reduce 0.5 when the ratio drops 0.1%. When it is lower than 98%, set the
eRAB Setup Success Rate
score to 0.
The initial score is 15.Add up the traffic measurement within the inspection period and get the total call drop rate.
Call Drop Rate
From 0% on, reduce 0.429 when the ratio rises 0.1%. When it is higher than 2 %, set the score to 0.
Intra-eNB Handover
Both of the initial score is 1.5. Add up the traffic measurement within the inspection period and get the total Intra-
Success Rate
Inter-eNB Handover eNB/Inter-eNB handover success rate. From 100% on, reduce 0.075 when the ratio drops 0.1%. When it is lower
KPI
Success Rate than 98%, set the score to 0.
Intra-Freq Handover
Handove
Both of the initial score is 3.5. Add up the traffic measurement within the inspection period and get the total Intra-
Success Rate
r Success
Inter-Freq Handover Freq/Inter-Freq handover success rate. From 100% on, reduce 0.175 when the ratio drops 0.1%. When it is lower
Rate
Success Rate than 98%, set the score to 0.
Inter-RAT
The initial score is 5. Add up the traffic measurement within the inspection period and get the total Inter-RAT
Handover Success
handover success rate. From 100% on, reduce 0.0625 when the ratio drops 0.10%.If it is lower than 98%, set the
Rate
score to 0.
Note:
Score Rate = (initial score-reduced score)/initial score
Suggestion: Based on the total score, output “Please Keep It On” when score rate >= 90%, “Please Keep Optimizing It” when it is between 80%
(contained)-90%, “Please Optimize It Immediately” when it is between 60% (contained)-80% and “Please Solve It Immediately” when it is lower than <
60%.
1) TOP Problem List：
 If score rate in Cell State, Configuration Check or eRAB Setup Success Rate items is lower than 50%, output Critical. If it is between
50%~90%, output Major.
 If score rate in the Equipment Load is lower than 80%, output Critical. If it is between 80%~90%, output Major.
 If score rate in RRC Setup Success Rate or Call Drop Rate is lower than 50%, output Critical. If it is between 50%~80%, output Major.
 If score rate in Handover Success Rate is lower than 50%, output Critical. If it is between 50%~70%, output Major.

1.3.4 Measures
If the score is relatively low, please find point-reducing items and solve the problem by corresponding measures.
1.3.5 Reference
None.
3.2 Basic Network Information
1.3.6 Location

02 Health check 01 Network Overview 01 Basic Network Information
Impact: If the speed of ETHPORT port is less than 100mbps, it will affect the peak rate. If MTU (Maximum Transmission Unit) is less than 1500
bytes, it would lead to packet loss or excessively fragmented data packets on transport network, resulting in a long delay, deteriorated performance or
damaged service quality.
This rule collects information of eNodeB ID, eNodeB Name, Operator Name, eNodeB Sharing Mode, DLEarfcn and Bandwidth Information and
Port Attribute, ETHPORT speed, MTU, whether IPSec is used or not, MME Release, Current Clock Synchronous Mode and eNodeB Clock Source
Configuration to know basic information of current internet and remind whether they are consistent with the recommended configurations.
1) Output every operator’s eNodeB Number and related information.
Basic Network Information Statistic

Operator Operator eNodeB Sharing eNodeB The Number of eNodeB
Name PLMN Mode Number Replications
Shared Frequency
PRIM:yi PRIM:42403 1 0
Sharing Mode
2) Output eNodeB number under different local speeds.
Local Speed Statistic

Local Speed eNodeB Number
1000M 17
1000M/100M 1

100M/1000M 1
3) Output eNodeB numbers under different clock synchronization modes.
Clock Synchronization Mode Statistic
Clock Synchronous Mode eNodeB Number
FREQ 18
TIME 3
4) Output each eNodeB’s eNodeB ID, eNodeB Name, Operator Name, eNodeB Sharing Mode, DLEarfcn and Bandwidth Information and Port
Attribute, ETHPORT Speed, Local Speed, MTU(byte), Encryption or Not, MME Release, Current Clock Synchronization Mode, eNodeB Clock
Source Configuration and so on.
Basic Network Information

VS. VS.F VS.F VS.F
ETHP FE EGE. EGE. EGE.
eNode DLEa Encr eNodeB
eNod Oper Oper ORT Current GE. TxM RxM RxM
eNod B rfcn Port ypti MME Clock
eB ator ator Speed Local MTU Clock Tx eanS axSp eanS
eB Sharin and Attrib on Releas Source
Nam Nam PLM Speed (byte) Synchroniza Max peed( eed(b peed(
ID g Band ute or e Configu
e e N tion Mode Spee bit/s) it/s) bit/s)
Mode width Not ration
d(bi
t/s)
5381 67.- PRI PRI Indepe [3700/ 0:Auto - 10M/1 1400/1 No Releas FREQ None 4029 2404. 79687 7338.
8 UMP M:tel M:50 ndent 10M] /0:Aut 0M 400 e R8 320 55 04 04
Ta2 us 204 Operat o
or
5383 GL_1 PRI PRI Indepe [1350/ 0:Copp - 100M 1500 No Releas FREQ IP Clock 3820 3700. 24557 15210
5 _3_L M:tel M:50 ndent 10M,1 er e R10 136 2 224 .22
us 204 Operat 350/20
or M]
Note: This principle does not apply to eNodeBs in RAN sharing with dedicated carrier mode.
5) Show the relationship between NE, data packet and eNodeB ID.
Relationship between NE, Data Packet and eNodeB ID

eNodeB ID eNodeB Name Data Packet Name NE Name
509 MNSU_B1_Pvt_4G_509 LTE_1_LUO_1_20130515143650 BTS3900LLTE_NE=3838
1.3.8 Principles
1) Find eNodeB ID and Name/eNodeB Function Name under eNodeB field from XML file.
2) Get the information of the Operator Name and Operator PLMN by CnOperator field.

3) Judge eNodeB Sharing Mode by ENODEBSHARINGMODE field. There are INDEPENDENT, SHARED_FREQ, and SEPARATED_FREQ
three modes.
4) Find out each cell’s DlEarfcn and DlBandWidth by Cell field.
5) Get current used port, local speed and MTU (byte) by MML’s DSP ETHPORT command.
a) Judge its attribute (Copper or Fiber) through ‘Port Attribute’. If Port Status = Up and Number of IPs is not 0, output its attribute.
b) Get ETHPORT’s speed mode by Local Speed. If it contains 10M or 100M, mark it red as an exception.
c) Get ETHPORT’s MTU by MTU (byte). If it is less than 1500 byte, mark it red as an exception.
6) Get ETHPORT speed from XML file.
a) If Port Status = Up and Number of IPs is not 0 by MML’s DSP ETHPORT command, record its port. If Port Status = Down or Number of
IPs is 0, output – and end.
b) Based on the port recorded in a), find and output its corresponding speed from XML file. (010M, 1100M, 21000M, 3---auto-
negotiation).
7) Check whether there is IPSECBIND field from XML file. If yes, it is considered that encryption is used.
8) Get MME release version from S1Interface’s MmeRelease.
9) Get clock synchronization mode and current clock source by MML’s DSP CLKSTAT command.
a) Get current clock synchronization mode by “Clock Synchronization Mode”.
b) Get current clock source by “Current Clock Source”.
10) Find and record CN/SRN/SN/SBT/PN under ethport from LMT.XML file.
11) Check the value of CN/SRN/SN/SBT/PN, which corresponds with traffic counters.
a) Check the value of fegeltekey from database.
b) Check the value of fegelteid from omstar_xxx_xsau.D_FEGELTE, which corresponds with fegeltekey (For example: "0:0:7:0:0" is the
value of CN/SRN/SN/SBT/PN. The detailed corresponding relationship is in the later passage).
c) Check the value of measunit from omstar_version_info.t_perf_item_enodebvxxxxxxxxxx, which corresponds with the traffic counters.
d) Check the value of measset from omstar_version_info.t_perf_measunit_xxxxxxxxxxx, which corresponds with the measunit.
e) Check the value of parameterenname from omstar_version_info.t_perf_measset_enodebxxxxxxxxxx, which corresponds with the measset
(The content of parameterenname indicates the order of fegelteid).
12) Select eNodeBs with same CN/SRN/SN/SBT/PN in step 11) and step 10), check and output VS.FEGE.TxMaxSpeed, VS.FEGE.TxMeanSpeed,
VS.FEGE.RxMaxSpeed and VS.FEGE.RxMeanSpeed.
 VS.FEGE.TxMaxSpeed is maximum transmit rate on the Ethernet port based on hour granularity in one day.
 VS.FEGE.TxMeanSpeed is average transmit rate on the Ethernet port based on hour granularity in one day.

 VS.FEGE.RxMaxSpeed is maximum receive rate on the Ethernet port based on hour granularity in one day.
 VS.FEGE.RxMeanSpeed is average receive rate on the Ethernet port based on hour granularity in one day.
13) Information of NE, data packet and eNodeB.
Output the information of the relationship between NE, data packet and the eNodeB.
1.3.9 Measures
1) Check whether the NE is consistent with the expectation or not.
2) Change the Local Speed to 1000M.
3) Change the MTU (byte) to 1500 bytes or above.
1.3.10 Reference
None.
3.3 Device Version Information
3.3.1 Location

02 Health Check 01 Network Overview 02 Device Version Information
This rule collects information of each eNodeB’s main area software version, MPT hardware version, MPT BootRom version, BBP hardware
version, BBP BootRom version, RRU software version, RRU hardware version, RRU BootRom Version and RRU serial number to understand the device
version information.
1) Count the eNodeB number under each main area software version in the entire network.
eNodeB Version Statistic

Main Area Software Version eNodeB Number
BTS3900 V100R008C00SPC240 4
2) Output RRU number.

RRU Number Statistic

BOM Encoding RRU Number
02310CJV 3
3) Output each eNodeB’s device version information.
Device Version Information

eNode eNodeB Main Area MPT Hardware MPT BootRom BBP Hardware BBP BootRom RRU Software RRU BootRom
LBBP Type RRU Hardware Version
B ID Name Software Version Version Version Version Version Version Version
BTS3900 1E.D0C.10.009 // MRRU.HWEI.x5A120000 // 1C.185.10.019 //

LBBPD // 33.001.01.035 //
112200 EHA200 V100R008C00SPC 2576 00.012.01.003 46337 // 46337 1E.D0C.10.009 // MRRU.HWEI.x5A120000 // 1C.185.10.019 //
LBBPC 04.001.01.23
240 1E.D0C.10.009 MRRU.HWEI.x5A120000 1C.185.10.019
Note: eRAN7.0 version adds three counters, which are RHUB software version, RHUB hardware version and RHUB BootRom version.
3.3.3 Principles
Get main area software version and site type’s information from XML file.
1) Get hot patch’s information by DSP PATCH command.
a) If the eNodeB has a hot patch and its state is active or running, use “site type + hot patch version” as eNodeB’s software version, such as
“DBS3900 LTE V100R003C00SPH436”.
b) If not, use “site type + main area software version” as eNodeB’s software version, such as “DBS3900 LTE V100R005C00SPC300”.
Note: When judging whether it has a hot patch, refer to the result of LMPT under Normal state.
2) Find out MPT hardware version, MPT BootRom version, LBBP hardware version, LBBP BootRom version, RRU software version, RRU
hardware version, RRU BootRom Version and RRU serial number by DSP BRDVER command.
3) Find out specific LBBP’s type based on its CN, SRN, and SN by DSP BRDMFRINFO command.
3.3.4 Measures
None.
3.3.5 Reference
None.

3.4 Distribution of eNodeBs and Cells
3.4.1 Location

02 Health Check 01 Network Overview 03 Distribution of eNodeBs and Cells
This rule is a statistical rule without exceptional examination. It is mainly used to collect each eNodeB and its cells’ related information to
understand the entire network better.
1) Output information of eNodeB Type, eNodeB Number and eNodeB Number (RRU concatenation) in the entire network.
eNodeB Number Statistic

eNodeB Type eNodeB Number eNodeB Number (RRU concatenation)
3 Cells in an eNodeB 249 0
Total 249 0
2) Output information of Cell Downlink earfcn, Cell Bandwidth, Cell Number and distribution of SFN cells in the entire network.
Cell Number Statistic

Cell Downlink earfcn Cell Bandwidth Cell Number SFN Cell
1875 15M 747 0
Total -- 747 0
3) Output distribution of eNodeBs and cells and other related information in the entire network.
Distribution of eNodeBs and Cells

eNo eNode Cell Produ Cell Downlink Reference Multi Multi
Tx Rx SFN RRU
deB B Numb ct Downlink bandwidt TAC Signal PB PA RRU Cell RRU Cell
Mode Cell Position
ID Name er Type earfcn h(MHz) Pwr Flag Mode
BTS3 41224 DB_3_P_A(-3 2R2T

1875 // 15M // 1 // SFN //
11 30 3 900_L // 182 // 182 dB) // DB_3_P_A(- NO // NO // - // - -
1875 15M 1 SFN
TE 41224 3 dB) 2R2T
3.4.3 Principles
1) Find out each eNodeB’s eNodeB ID, eNodeB Name, Cell Number, Product Type and each cell’s UtranDlArfcn, DlBandWidth, TAC,
ReferenceSignalPw, Pb, PaPcOff, MultiRruCellFlag, MultiRruCellMode and TxRxMode from XML file.

2) Check the value of MultiRruCellFlag and MultiRruCellMode under CELL from XML file to judge whether it is SFN cell. When
MultiRruCellFlag = BOOLEAN_TRUE and MultiRruCellMode = SFN, it is considered as a SFN Cell. (MultiRruCellFlag = 1 means
BOOLEAN_TRUE and MultiRruCellMode = 0 means SFN).
3) Check the value of PS under RRU from XML file to judge whether it is RRU concatenation. If any PS is non-zero, it is considered as
concatenated eNodeB and output its location and number.
4) Meaning of each parameter:
 UtranDlArfcn: Downlink Frequency;
 DlBandWidth: Downlink Bandwidth;
 TAC: Tracking Area Code;
 ReferenceSignalPwr: Reference Signal Power;
 Pb: PB;
 PaPcOff: PA;
 MultiRruCellFlag: Multi RUU Cell Flag;
 MultiRruCellMode: Multi RUU Cell Mode;
 TxRxMode：Cell’s Transfer and Receive Mode.
3.4.4 Measures
None.
3.4.5 Reference
None.
1.4 Board Statistics
1.4.1 Location

02 Health check 01 Network Overview 04 Board Statistics

This rule is used to summarize the board number in entire network and output each eNodeB’s board number.
1) Count board number in the entire network
Result of Board Statistics: Summary

UBB UTR USC MR LRR MR LRF PRRU( RH UNKNO
LMPT UMPT LBBP BRU
P P U RU U FU U MPMU) UB WN
LMP UNKNO UMPT UMPT UNKNO
TC WN a1 a2 WN
1 7 1 14 2 28 0 9 7 19 6 6 6 15 15 1 0
2) Output the information of BBP in the entire network.
Overview of BBP
BBP Number eNodeB Number
0 1
1 1
2 9
3 3
4 0
5 0
6 0
More than 6 0
3) Count board number under normal state to judge each eNodeB’s operating state.
Result of Board Statistic

LMPT UMPT L U
eNod eNodeB B UBB T USC MR LRR MR LRF PRRU(M RH UNKN
LMPT UNKN UMPT UMPT UNKN BRU
eB ID Name B P R U RU U FU U PMU) UB OWN
C OWN a1 a2 OWN
P P
62009 62009 1 1 1 1 2 0 0 1 0 0 0 0 0 0 1 1 0
4) Count board number used only for word extraction.
Result of Board Statistic (Only for Word)

LMP LRF BRU UNKNOWN
UMPT LBBP UTRP USCU MRRU LRRU MRFU
T U
8 17 28 0 9 7 19 6 6 6 0

1.4.3 Principles
1) Find out current eNodeB’s board configuration and count board number or module number ("LMPT", "UMPT", "LBBP", "UBBP", "UTRP",
"USCU", "MRRU", "LRRU", "MRFU", "LRFU", "MPMU", "PRRU", "RHUB", "BRU" and "UNKNON") in the entire network by MML’S
DSP BRD command.
2) Find more details for UMPT/LMPT/LBBP/UBBP by MML’s DSP BRDMFRINFO command. For example: If the result of Type under LBBP =
WD22LBBPC, delete WD22 and output LBBPC.
3) If both LBBP and UBBP have sub-boards, combine them as BBP column and list all sub-boards’ type and number. For example:
Both LBBP and UBBP have sub-boards:
LBBP or UBBP doesn’t have sub-boards (Take UBBP for example):
1.4.4 Measures
None.
1.4.5 Reference
None.
1.5 RRU Configuration Information
1.5.1 Location

02 Health Check 01 Network Overview 05 RRU Configuration Information
This rule is used to collect RRU configuration information in the entire network to understand it better.

1) Output VSWR alarm post-processing switch in the entire network.
Overview of VSWR Alarm Post-Processing Switch in the Entire Network
VSWR Alarm Post-Processing Switch RRU Number
Off 1
On 2
2) Output Topo Type in the entire network.
Overview of Topo Type in the Entire Network

Topo Type RRU Number
Chain 1
Ring 1
Load Balance 1
3) Output RF Unit Working Mode in the entire network.
Overview of RF Unit Working Mode in the Entire Network
RF Unit Working Mode RRU Number
GO(GSM_ONLY) 1
LO(LTE_FDD) 1
UO(UMTS_ONLY) 1
4) Output eNodeBs’ RRU configuration in the entire network.
RRU Config Information

VSWR Alarm
RRU VSWR Alarm VSWR Attenuation of the RX Ring/C
eNodeB eNodeB Post- Topo Backup RF Unit Working
CN/SRN/ Post-Processing Alarm channel of the RRU or hain
ID Name Processing Type Mode Mode
SN Threshold Threshold RFU(unit:db) (RCN)
Switch
6209 6209 0 / 60 / 0 On 2 1.5 0 1 Chain Cold LO(LTE_FDD)
6209 6209 0 / 61 / 0 On 2 1.5 0 2 Ring Cold GO(GSM_ONLY)
Load Cold
6209 6209 0 / 62 / 0 Off 2 1.5 0 2 UO(UMTS_ONLY)
Balance
1.5.3 Principles
Collect each eNodeB’s RRU configuration information in the entire network from XML file.
1) Check the value of ALMPROCSW under RRU (If ALMPROCSW = 0, it indicates VSWR alarm post-processing switch is on. If ALMPROCSW
= 1, it indicates VSWR alarm post-processing switch is off.).

2) Check the value of ALMPROCTHRHID under RRU (the value of VSWR alarm post-processing threshold is between 14~100 and the unit is 0.1,
so the actual value is between 1.4~10).
3) Check the value of ALMTHRHLD under RRU (the value of VSWR alarm post-processing threshold is between 14~30 and the unit is 0.1, so the
actual value is between 1.4~3).
4) Check the value of ATTEN under RXBRANCH (the value of Attenuation is between 0~60 and the unit is 0.5, so the actual value is between
0~30).
5) Find RCN Number under RRUCHAIN based on RCN Number under RRU and output Topo type (TT) and Backup mode (BM) (If TT = 0,
CHAIN state. If TT = 1, RING state. If TT = 2, LOADBALANCE state. If BM = 0, COLD backup mode. If BM = 1, HOT backup mode).
6) Check the value of RS (RF Unit Working Mode) under RRU and convert it into actual working mode. RS field is mainly used to identify whether
the eNodeB is single-mode or multi-mode.
1.5.4 Measures
None.
1.5.5 Reference
None.
3.5 Sleeping Cell Check
1.5.6 Location

02 Health check 02 Device State Check 01 Sleeping Cell Check
Users can’t access the cell if it is under sleeping state, which is out of service. This rule is mainly used to output suspected sleeping cells’ related
information.
1) Collect each cell’s traffic measurement to output suspected sleeping cell’s information by day.
Result of Sleeping Cell Check

eNodeB ID eNodeB Name Local Cell ID Cell Name Time(Day)

230013 230013 0 2300131 2012-12-14

2) Output the information of cells whose RRC Connection Request Number = 0 (latest consecutive 48 hours or above).
L.RRC.ConnReq.Att (latest consecutive 48 hours) = 0

eNodeB eNodeB Local Cell Period(L.RRC.C L.RA.GrpA. L.RA.GrpA.
Time(Day)
ID Name Cell ID Name onnReq.Att=0) Att Resp
2012-12-15
2313 2313 0 131 2012-12-15 01:00:00 - 2012- 7200 0
12-17 00:00:00
Note：
 The above two tables only list several counters: It also includes L.RA.GrpB.Att, L.RA.GrpB.Resp, L.RA.Dedicate.Att, L.RA.Dedicate_Resp,
L.RA.Dedicate.HO.Att, L.RA.Dedicate.HO.Resp, L.RRC.ConnReq.Att, L.Thrp.bits.UL, L.Thrp.bits.DL and L.Traffic.User.Avg. the failure of
power on restart
 If some counters in the cell weren’t activated in the first inspection report, traffic measurement can’t be collected.
1.5.8 Principles
1) “Result of Sleeping Cell Check” table:
a) Take each cell as granularity, summarize each cell’s Random Access preamble (msg1), Random Access Response (msg2) and RRC
connection request (msg3) during the evaluation period by day.
b) Calculate RA Rate of each cell by day. If the denominator is zero, set the result as null.
c) If the following three conditions are met, it is considered as suspected sleeping cell.
 The number of msg1> 250;
 RA Rate < 10%;
 The number of msg3 = 0.
d) Meantime, take each cell as granularity, summarize each cell’s L.Thrp.bits.UL, L.Thrp.bits.DL and L.Traffic.User.Avg during the
evaluation period by day.
2) “L.RRC.ConnReq.Att (latest consecutive 48 hours) = 0” table:
If these two conditions are met at the same time, output the cell’s information to the “L.RRC.ConnReq.Att (latest consecutive 48 hours) = 0”
table.
 The number of msg1>250;
 msg3, L.Thrp.bits.UL, L.Thrp.bits.DL and L.Traffic.User.Avg is 0 in the latest consecutive 48 hours or above.
Formula of each counter:

 The number of msg1 = (L.RA.GrpA.Att + L.RA.GrpB.Att + L.RA.Dedicate.Att + L.RA.Dedicate.HO.Att);
 The number of msg2 = (L.RA.GrpA.Resp + L.RA.GrpB.Resp + L.RA.Dedicate.Resp + L.RA.Dedicate.HO.Resp);
 The number of msg3 = L.RRC.ConnReq.Att;
 RA Rate = The number of msg2 /the number of msg1;
 Cell uplink throughput = L.Thrp.bits.UL;
 Cell downlink throughput = L.Thrp.bits.DL;
 L.Traffic.User.Avg = AVG{∑L.Traffic.User.Avg.1, … ,∑L.Traffic.User.Avg.i, … , ∑L.Traffic.User.Avg.24},I = 1, 2, …24(24hs).
1.5.9 Measures
Before recovering the cell, please collect the information of KPI data (sampled by hour) for more than one month, cell tracking and one-key log
data (BBP and MPT) and RRU log and send them to HUAWEI engineers for analysis.
1.5.10 References
It is inspected that 1 sleeping cell in August, 2012. After collecting one-key log and analyzed by LCEM, it is considered as known issue.
eRAN3.0 version has solved this problem.
3.6 Unavailable Cell Check
1.5.11 Location

02 Health Check 02 Device State Check 02 Unavailable Cell Check
When a cell is unavailable, cell establishment will fail, the services will be interrupted or cell establishment succeeds but the access will be
rejected, which would lower the internet’s performance. This rule is mainly used to output related information of unavailable and blocked cells.
1) Check a cell’s state by MML’s DSP CELL command. If it is not ‘normal’ and has been activated by ACT CELL command, it is considered that
some fault leads to the failure of cell establishment and output this cell’s related information.
Unavailable Cell List
eNod eNode Local Cell Cause of Cell Cell Latest Duration of Cell Duration of Cell Duration of Cell

B Cell Instanc Remove Unavailability Due Unavailability Due Unavailability Due to

eB ID Unavailable
Name ID e State Time to System Faults(S) to Human Factors(S) Energy Saving(S)
Uninstal Configuration 2014-01-27
5383 GL_L 1 146095 0 -
l activation fails. 09:56:41
2) Output related information of blocked cells.
Blocked Cell List

eNode Local Cell Time for Duration of Cell Duration of Cell Duration of Cell
eNod Cause for Cell
B Cell Instanc Cell Latest Unavailability Due Unavailability Due Unavailability Due
eB ID Unavailable
Name ID e State Deleting to System Faults(S) to Human Factors(S) to Energy Saving(S)
Uninstal Configuration 2014-01-27
5383 GL_L 1 146095 0 -
l activation fail 09:56:41
1.5.13 Principles
1) Check whether CellActive State under CELL from XML file is 1 or not. If yes, it indicates this cell has run ACT CELL before and go to next
step. If it is 0, it indicates this cell is never been activated and end.
2) Check all the cells’ state by MML’s DSP CELL command. If the result of ‘cell instant state’ is not ‘normal’, go to next step, or end.
3) Judge the unavailable reason from DSP CELL’s ‘Reason for latest state change’.
a) If it is “Cell Is Blocked”, the reason is blocked and output cell’s related information to the “Blocked Cell List”.
b) If it is “Cell setup successfully/Cell setup succeeded”, judge whether the value of CellAdminState under CELL from XML file is 1/2/3
(high/middle/low priority blocked). If it is, the reason is blocked and output cell’s related information to the “Blocked Cell List”. If not, the
reason is ‘others’ and output cell’s related information to the “Unavailable Cell List”.
c) If it is not a) or b), take the result itself as the reason for the failure of cell establishment and output cells’ related information to the
“Unavailable Cell List”.
1.5.14 Measures
1) Try to reactivate the cell and investigate the unavailable reason.
2) If this problem can’t be fixed up, contact HUAWEI engineers.

1.5.15 Reference
Please refer to 《LTE Maintenance Guide》:
http://support.huawei.com/carrier/docview!docview?nid=SE0000746720
3.7 Deactivated Cell Statistics
3.7.1 Location
02 Health check 02 Device State Check 03 Deactivated Cell Statistics
If a cell is under deactivated state, it couldn’t provide services. This rule is mainly used to collect related information of deactivated cells.
1) Output related information of deactivated cells.
Deactivated Cell List

eNodeB ID eNodeB Name Local Cell ID
230013 230013 0
230013 230013 2
3.7.3 Principles
1) Judge whether CellActiveState under CELL from XML file is 0 or not. If yes, it indicates this cell is deactivated manually or it is never been
activated before.
2) Output this cell’s information to the “Deactivated Cell List”.
3.7.4 Measures
1) If this service is necessary, use ACT CELL to activate the cell.
2) If the activation failed, please refer to 《LTE Maintenance Guide》:

3.7.5 Reference
None.
3.8 Hot Patch State Check
3.8.1 Location

02 Health Check 02 Device State Check 04 Hot Patch State Check
If eNodeBs have Deactive and Active hot patch, they couldn’t load new hot patch. If effective hot patch is under Active state, it will become
Deactive after eNodeBs reset. Therefore, Deactive and Active states are not recommended and need to confirm instead. This rule is mainly used to output
eNodeBs’ related information with Deactive or Active hot patch.
1) Output hot patch states and the corresponding eNodeBs’ information in the entire network.
Summary of Hot Patch State

Hot Patch State eNodeB Number Remark
Active 1 -
Deactive 1 -
Idle 1 -
2) Output eNodeBs’ related information with Deactive or Active hot patch.
Result of Abnormal Hot Patch Check in eNodeBs

eNodeB ID eNodeB Name Hot Patch ID Base Software Version Hot Patch State
49043 NEW_OM03 V100R011C00SPH001 V100R011C00SPC001 Active
49057 90_OM17 V100R011C00SPH001 V100R011C00SPC001 Deactive
3) Output eNodeBs’ related information with Idle or Running hot patch.
Result of Hot Patch Check in other eNodeBs

eNodeB ID eNodeB Name Hot Patch ID Base Software Version Hot Patch State
49157 190_OM17 V100R011C00SPH001 V100R011C00SPC001 Idle
3.8.3 Principles
1) Find MPT’s information by MML’s DSP BRD command. Get its cabinet No., subrack No. and slot No. if “Availability Status” is “Normal”,
“Standby Status” is “Active”and board type is *MPT.

2) There are IDLE, DEACTIVE, ACTIVE and RUNNING four states for a hot patch. Get all the boards’ hot patch information by MML’s DSP
PATCH command and find MPT’s hot patch information which satisfies 1) and take it as eNodeB’s hot patch state.
3.8.4 Measures
1) If this patch is not necessary, delete it by RMV PATCH command.
2) If this patch is necessary, put it into running state by ACT PATCH and CON PATCH command successively.
3.8.5 Reference
None.
3.9 Check of Cell Reserved State for Operator
3.9.1 Location

02 Health Check 02 Device State Check 05 Check of Cell Reserved State for Operator
If “CellReservedForOp” is set to CELL_RESERVED_FOR_OP, it indicates the cell is reserved for operator. UEs of AC11/ AC15 in their
HPLMN/EHPLMN will consider this cell as a candidate cell during cell selection or reselection. UEs of AC11/AC15 out their HPLMN/EHPLMN or UEs
of AC0-9/AC12-14 will consider this cell as a barred cell during cell selection or reselection. This rule is mainly used to collect information of cell reserved
state for operator.
1) Output cells which are reserved for operator and their related information.
Cell Reserved State for Operator

eNodeB ID eNodeB Name Local Cell ID Cell Reserved State for Operator
149530 149530_Marina 3 CELL_RESERVED
3.9.3 Principles
1) Check the value of “CellReservedForOp” under CELLOP in the XML file.
2) If CellReservedForOp = 0, which is CELL_RESERVED_FOR_OP state, it indicates this cell is reserved for operator.

3.9.4 Measures
Recommended value: CELL_NOT_RESERVED_FOR_OP (Not Reserved).
MML command: MOD CELLOP: CellReservedForOp = CELL_NOT_RESERVED_FOR_OP.
3.9.5 Reference
None.
3.10 Cell Barred State Check
3.10.1 Location

02 Health Check 02 Device State Check 06 Cell Barred State Check
If a cell is barred, the UE cannot stop at this cell. During cell selection and reselection, this cell will not be selected as a candidate cell. This rule is
mainly used to collect related information of barred cells.
1) Output related information of barred cells.
Cell Barred State Check

eNodeB
eNodeB Name Local Cell ID Cell Barred State
ID
62009 62009 3 CELL_BARRED
3.10.3 Principles
Check the value of “CellBarred” under CELLACCESS in the XML file and judge whether the cell is under barred state or not.
1) If the value is CELL_BARRED, it indicates this cell is barred and output its related information.
2) If the value is CELL_NOT_BARRED, it indicates this cell is not barred and don’t output.
3.10.4 Measures
Recommended value: CELL_NOT_BARRED.

MML command: MOD CELLACCESS: CellBarred=CELL_NOT_BARRED.
3.10.5 Reference
None.
3.11 Cell Capability Degraded Check
3.11.1 Location

02 Health Check 02 Device State Check 07 Cell Capability Degraded Check
If this alarm occurs, the coverage of the faulty local cell will decrease, the RTWP reported by some RRUs will be discarded, the features
configured on the local cell will not be supported, or certain demodulation capabilities of the uplink baseband equipment used by the local cell will be
unavailable. This rule is mainly used to collect related information of capability degraded cells.
1) Output cells’ related information with capability degraded alarm.
Cell Capability Degraded Check

eNodeB eNodeB Local Alarm Alarm Alarm Occurrence
Location
ID Name Cell ID ID Name Severity Time
cell capability Cabinet No.=0, Subrack No.=0, Slot
2014-02-06
27368 27368 1 29243 degraded Major No.=3, Port No.=0, Board Type=LBBP,
00:02:07
alarm Specific Problem=Receive No Signal
3.11.3 Principles
1) Filter alarm ID= 29243 (cell capability degraded alarm) from the active alarms (unrecovered).
2) Output detailed active alarm information.
3.11.4 Measures
1) Reestablish a cell (DEA CELL, ACT CELL) and check whether the alarm is cleared or not. (Please try to perform this operation during low-

traffic hours, for example, middle night.)
2) If not clear, collect log information and send them to HUAWEI engineers.
3.11.5 Reference
None.
3.12 Clock State Check
3.12.1 Location

02 Health Check 02 Device State Check 08 Clock State Check
If clock related active alarms occur (Alarm ID 26260~26265, 26267, 26278, 26106, 26538, 26120, 26266), it’s necessary to investigate this
eNodeB’s clock. This rule is mainly used to output eNodeBs’ related information with these alarms.
1) Output detailed information of clock related alarms.
eNodeB Clock State Check

eNode eNodeB PLL Alarm Alarm Occurrence
Alarm Name Location
B ID Name Status ID Severity Time
Free
External Clock 2013-01-20 Specific Problem=Excessive Frequency Difference
140310 140310 runnin 26262 Minor
Reference Problem 03:09:02 Between Clock Reference and Local Crystal Oscillator
g
2) Output TOP10 eNodeBs’ information with most alarms.
Top eNodeBs with Most Alarms

eNodeB ID eNodeB Name Alarm Times
630828 FH*** _630828 4
3) Output eNodeBs’ related information which alarms occur more than 3 times during inspection period.
Abnormal Alarm List (Alarm Times > 3)

eNodeB ID eNodeB Name Alarm ID Alarm Name Alarm Severity Alarm Times
Normal Normal Normal Normal Normal Normal

3.12.3 Principles
Check eNodeBs’ active alarms and find out whether there are 26260~26265, 26267, 26278, 26106, 26538, 26120, 26266 existed or not.
1) If there is, go to next step. Or end.
2) Find current PPL state by MML’s DSP CLKSTAT command and record the result.
3) Output eNodeB’s ID, PLL State and its alarm information.
3.12.4 Measures
Please refer to Alarm Help.
3.12.5 Reference
None.
1.6 SCTP Link State Check (S1)
1.6.1 Location

02 Health Check 02 Device State Check 09 SCTP Link State Check (S1)
If the link between an eNodeB and core network fails, it will affect S1’s handover. This rule is mainly used to check ALM-25888 SCTP link fault
(Judge it as S1 interface according to the description of the alarm) as well as collecting related information of SCTP link fault (S1).
1) Output the result of SCTP link state check (S1) according to alarm times.
The Result of SCTP Link State Check (S1)

Alarm Times eNodeB Number
1 0
2 0
3 0
4 0
5 0
6 0
>6 2

2) Output TOP20 eNodeBs’ information with most SCTP link fault alarms (S1).
Top20 eNodeBs with Most SCTP Link Fault Alarms (S1)

eNodeB eNodeB Port Alar Alarm Alarm Alarm
Location Occurrence Time
ID Name No. m ID Name Severity Times
Link No.=0,
SCTP link Description=NULL, Peer

225911 225911 0 25888 Major 1 2014-01-25 07:23:13
fault IP Address=195.195.30.5,
Service Type=S1-AP
1.6.3 Principles
Filter out Alarm ID=25888 from alarm table (alarm.csv) and get the key fields from locationinformation column.
1) If there is Service Type in key fields, judge whether it is S1 (contains S1) or not from its value. If not, go to next step.
2) Check whether there is SGW/MME under key field Description. If there is, consider it as S1. If it is blank, go to next step.
3) Check key field Peer IP Address and find IPPATH which has same address with Peer IP Address from XML file. Then check the value of its
corresponding ApplicationType. If it is 0, consider it as S1. If ApplicationType is not found, go to next step.
4) Check PathID of IPPATH from XML file, find corresponding Ippathid of eNodeBPath and check the value of apptype. If it is 0, consider it as S1.
5) Count SCTP link state in the entire network in segment according to alarm times.
1.6.4 Measures
1) Check whether eNodeB’s configuration is correct.
2) Use the ping detect method to check whether the transmission is normal.
1.6.5 Reference
None.
1.7 SCTP Link State Check (X2)
1.7.1 Location

02 Health Check 02 Device State Check 10 SCTP Link State Check (X2)
If eNodeBs’ X2 link fails, SCTP link can’t carry service signaling from X2 interface. Before the alarm is cleared, local eNodeBs are not allowed
to handover on these X2 interfaces. This rule is mainly used to check ALM-25888 SCTP link fault (Judge it as X2 interface according to the description of
the alarm) as well as collecting related information of SCTP link fault (X2).
1) Output the result of SCTP link state check (X2) according to the alarm times.
The Result of SCTP Link State Check (X2)

Alarm Times eNodeB Number
1 0
2 0
3 0
4 0
5 0
6 0
>6 2
2) Output TOP20 eNodeBs’ information with most SCTP link fault alarms (X2).
Top20 eNodeBs with Most SCTP Link Fault Alarms (X2)

eNode Alarm Intra- Frequency Inter-Frequency
eNode Port Alar Alarm Alarm Occurrence
B Severit Location X2 Hoout Execute X2 Hoout Execute
B ID No. m ID Name Times Time
Name y Success Rate Success Rate
Peer IP Address =
SCTP link 2014-11-25
414 4_414 - 25888 Major 1 40.40.40.15,Service Type=eX2- - -
fault alarm 00:16:08
AP
1.7.3 Principles
Filter out ID=25888 from alarm table (alarm.csv) and get the key fields from the locationinformation column.
1) If there is Service Type in key fields, judge whether it is X2(contains X2) from its value. If not, go to next step.
2) Check whether there is eNodeB or not under key field Description. If there is, consider it as X2. If it is blank, go to next step.
3) Check key field Peer IP Address and find IPPATH which has same address with Peer IP Address from XML file. Then check its corresponding
ApplicationType’s value. If it is 1, considered as X2. If ApplicationType is not founded, go to next step.
4) Check PathID of IPPATH from XML file, find corresponding Ippathid of eNodeBPath and check the value of apptype. If it is 1, consider it as X2.

5) Use original traffic measurement data from the first report to calculate L.HHO.X2.Intra-Freq.ExecSuccOut, L.HHO.X2.Inter-Freq.ExecSuccOut,
L.HHO.X2.Intra-Freq.ExecAttOut and L.HHO.X2.Inter-Freq.ExecAttOut of all cells under eNodeBs with this alarm during inspection time, and
then calculate Intra/Inter Frequency X2 Hoout Execute Success Rate during traffic measurement collecting period.
6) Count SCTP link state check (X2) in the entire network according to alarm times.
Formula of indexes:
 Number of executing X2 handover out between Intra Frequency eNodeBs successfully = L.HHO.X2.IntraFreq.ExecSuccOut
 Number of executing X2 handover out between Inter Frequency eNodeBs successfully = L.HHO.X2.InterFreq.ExecSuccOut
 Number of executing X2 handover out between Intra Frequency eNodeBs = L.HHO.X2.IntraFreq.ExecAttOut
 Number of executing X2 handover out between Inter Frequency eNodeBs = L.HHO.X2.InterFreq.ExecAttOut
 Intra Frequency X2 Hoout Execute Success Rate = L.HHO.X2.IntraFreq.ExecSuccOut / L.HHO.X2.IntraFreq.ExecAttOut
 Inter Frequency X2 Hoout Execute Success Rate = L.HHO.X2.InterFreq.ExecSuccOut / L.HHO.X2.InterFreq.ExecAttOut
1.7.4 Measures
1) Check and correct the blocked SCTP link by MML’s DSP SCTPLNK command.
2) If the alarm is not clear, check the bearer network, such as using the ping detect method to check whether the transmission is normal.
3) Contact the maintainers at the peer end to check whether the peer device is faulty or not.
1.7.5 Reference
None.
1.8 NE Project State Check
1.8.1 Location

02 Health Check 02 Device State Check 11 NE Project State Check
When the NE is in a special state (non-NOMARL), alarm reporting method will be changed, the accuracy of alarm detection will decrease and
data source of performance will be marked as unreliable. What’s more, it will continue its special state even after MPT restarts.

This rule is mainly used to collect eNodeBs’ related information with special state NE.
1) Output eNodeBs’ related information with special state NE.
NE Project State Check

eNodeB ID eNodeB Name NE State
230011 230011 INSTALL
230015 230015 EXPAND
230016 230016 UPGRADE
230017 230017 TESTING
230020 230020 ExpandStatus1
1.8.3 Principles
Check MNTMODE under EQUIPMENT field from LMT.XML file.
1) If it is 0, it indicates NE is under NORMAL state and end.
2) If it is not 0, it indicates NE is under non-NOMARL state and output this eNodeB’s information and mark it as abnormal.
Different value of MNTMODE indicates different NE state, as is shown in the below table.
Value of MNTMODE NE State

0 NOMARL
1 INSTALL
2 EXPAND
3 UPGRADE
4 TESTING
5 ExpandStatus1 ~ ExpandStatus10
1.8.4 Measures
If it is a commercial site, it is suggested to modify the project state to NORMAL mode by MML command: SET MNTMODE:
MNTMode=NORMAL~0.
1.8.5 Reference
None.

1.9 Active Alarm Analysis
1.9.1 Location

02 Health Check 03 Alarm Analysis 01 Active Alarm Analysis
This rule is mainly used to collect information of the distribution of active alarms in the entire network.
1) Collect information of all kinds of active alarms, alarm times and TOP20 eNodeBs’ information of each alarm.
Active Alarm Statistic (TOP20)

Alarm Tim
Alarm Name TOP1 TOP2 TOP3 TOP4 TOP5 TOP6 TOP7 TOP8 TOP9 TOP10
ID es
External eNB eNB ID:
eNB eNB ID: eNB ID: eNB ID: eNB ID:
Clock ID:1C-40- 1C-40- eNB ID: eNB ID: eNB ID:
ID:10.141. 1c 40 IOT LTE_NetC LTE_NetC LTE_NetCap
26261 Reference 12 eNB210- eNB211- CSPC104, CSPC105, CSPC106,
77.218, ENB222, apacity_53 apacity_53 acity_5315,
Not xuhuixu, xuhuixu, Once Once Once
Once Once 13, Once 14, Once Once
Configured Once Once
2) Output active alarms’ related information which occurs more than 5 times.
Active Alarms Frequently Occurred (>= 5 )

eNodeB ID eNodeB Name Alarm ID Alarm Name Alarm Severity Location Alarm Times
IP Path fault Peer
2070 EA_70 25886 Major 172
alarm Mode=GSM
3) Output the distribution of active alarms based on eNodeB ID.
Distribution of Active Alarms (by eNodeB ID)

eNodeB ID eNodeB Name Alarm Times
1259 EA_59 10
4) Output all active alarms and their related information.
Active Alarm List

Alarm ID Alarm Times Alarm Name Remark
25886 507 IP Path fault alarm -

1.9.3 Principles
1) Check all alarms in Alarm file.
2) If there is nothing in ClearanceTime column, it is considered as active alarm.
3) Output the active alarms and their eNodeBs’ information.
Note: alarm ID, alarm name and related information are listed in the below table.
Ala rm ID a nd
Ala rm N a m e .xls x
1.9.4 Measures
Refer to Alarm Help.
1.9.5 Reference
None.
1.10 Historical Alarms Analysis
1.10.1 Location

02 Health Check 03 Alarm Analysis 02 Historical Alarms Analysis
This rule is mainly used to collect information of the distribution of historical alarms in the entire network.
1) Output time range of occurred historical alarms.
Time Range of Occurred Historical Alarms
Occurrence Time of the First Alarm Occurrence Time of the Last Alarm
2012-12-13 10:05:05 2012-12-17 10:05:05
2) Collect TOP20 historical alarms (based on alarm times) and output their eNodeB ID and alarm times.

Historical Alarm Statistic (TOP20)

Alarm Alarm Alarm
TOP1 TOP2 TOP3 TOP4 TOP5 TOP6 TOP7 TOP8 TOP9 TOP10
ID Name Times
GPS eNB ID:
eNB ID: eNB ID: eNB ID: eNB ID: eNB ID: eNB ID:
Clock eNB ID: LTE_Net eNB ID: eNB ID:
LTE_NetC LTE_NetC TMO- TMO- TMO- 1C-40-
26120 Output 47 CSPC104, Capacity_ CSPC105 CSPC106,
apacity_53 apacity_53 5013, 6 5014, 6 5015, 6 ehuixu, 5
Unavailabl 6 times 5314, 6 , 6 times 6 times
15, 6 times 13, 6 times times times times times
e times
3) Output historical alarms’ related information which occurs more than 100 times.
Historical Alarms Frequently Occurred (>= 100)

eNodeB ID eNodeB Name Alarm ID Alarm Name Alarm Severity Location Alarm Times
Peer
2070 EA_70 25886 IP Path fault alarm Major 172
Mode=GSM
4) Output historical alarms’ related information which lasted for more than 8 hours (TOP50).
Historical Alarms Lasted for More than 8 hours

eNodeB eNodeB Alarm Alarm Alarm Occurren Clearance
Location Duration(S)
ID Name ID Name Severity ce Time Time
IP Path No.=22, Cabinet
IP Path No.=0, Subrack No.=0, Slot 2014-01-

2014-01-27
116053 116053 25886 fault Major No.=7, Description=NULL, 26 100846
18:04:00
alarm Peer IP 14:03:14
Address=172.26.193.98
5) Output the distribution of historical alarms based on eNodeB ID.
Distribution of Historical Alarms (by eNodeB ID)

eNodeB ID Alarm Times
1259 17
6) Output all historical alarms and their related information.
Historical Alarm List

Alarm ID Alarm Name Alarm Times Remark
25886 IP Path fault alarm 507 -
1.10.3 Principles
1) Check all alarms occurred in last month in Alarm file.

2) If there has information in ClearanceTime column, it is considered as historical alarm.
3) Output historical alarms and their eNodeBs’ related information.
Note: Related alarm ID, alarm name and other information are listed in the below table.
Ala rm ID a n d
Ala rm N a m e .xls x
1.10.4 Measures
Refer to Alarm Help and take immediate measures to the eNodeBs with frequently occurred alarms to prevent these alarms reoccurring.
1.10.5 Reference
None.
1.11 Abnormal Reset Event
1.11.1 Location

02 Health Check 03 Alarm Analysis 03 Abnormal Reset Event
If Event ID is 26212/26213 and the reset cause is abnormal reset, counted as abnormal reset event, which will lead to 2 minutes’ service cut-off.
If it can’t be solved, service cut-off will occur again. This rule is used to collect information of the distribution of abnormal reset events in the entire
network.
1) Output abnormal reset event’s eNodeB ID, eNodeB Name, event ID, event name, occurrence time, location and corresponding measures.
Abnormal Reset Events

eNodeB eNodeB Event Occurrence
Event Name Location Measures
ID Name ID Time
2014-06-30 Cabinet No.=0, Subrack No.=0, Analyze MPT and
53835 53835 26212 Board Startup
13:12:46 Slot No.=3, Board Type=LBBP, BBP’s one-click log

Reset Cause=Exceptional Reset
1.11.3 Principles
1) Find event log from Alarm file and count all abnormal startup events.
2) If there is Event ID = 26212 or 26213, go to next step, or end.
3) If Reset Cause = Exceptional Reset exits in the Location Information, counted as abnormal reset event.
4) If Alarm name is NE Startup, analyze MPT one-click log. If Alarm name is Board Startup, analyze MPT and BBP one-click log.
1.11.4 Measures
Check alarms occurred during the inspection time, collect corresponding board log and then feedback the issue to Huawei engineers for
troubleshooting.
1.11.5 Reference
None.
1.12 Hardware Fault Alarm
1.12.1 Location

02 Health Check 03Alarm Analysis 04 Hardware Fault Alarm
This rule is mainly used to collect information of the distribution of hardware fault alarm in the entire network.
1) Output board related alarm’s eNodeB ID, eNodeB Name, Alarm ID, Alarm Name, Severity, Location, Occurrence Time, Clearance Time and
Alarm Times.
Board Hardware Fault

eNodeB eNodeB Alarm Alarm Severit Occurren Clearance Alarm
Location
ID Name ID Name y ce Time Time Times
53835 53835 26200 Board Major Cabinet No.=0, 2014-06- 2014-06-30 2

Subrack No.=0, Slot

Hardware 30
No.=3, Board 13:23:07
Fault 13:10:24
Type=LBBP
2) Output RF Unit related alarm’s eNodeB ID, eNodeB Name, Alarm ID, Alarm Name, Severity, Location, Occurrence Time, Clearance Time and
Alarm Times.
RF Unit Hardware Fault

eNodeB eNodeB Alarm Alarm Occurrence Clearance Alarm
Severity Location
ID Name ID Name Time Time Times
Cabinet No.=0,
RF Unit
Subrack No.=60, 2014-01-25 2014-01-25
40211 40211 26532 Hardware Minor 1
Slot No.=0, Board 19:23:26 19:24:55
Fault
Type=MRRU
3) Output optical module related alarm’s eNodeB ID, eNodeB Name, Alarm ID, Alarm Name, Severity, Location, Occurrence Time, Clearance
Time and Alarm Times.
Optical Module Fault

eNodeB Alar Alarm Occurrence Clearance Alarm
eNodeB Name Alarm Name Location
ID m ID Severity Time Time Times
Optical Cabinet No.=0, Subrack No.=60, 2014-01-20 2014-01-20
40210 40210 26220 Minor 1
module Fault Slot No.=7,Board Type=MRRU 19:23:26 19:24:55
1.12.3 Principles
1) Take Alarm ID=26200, 26765, 26532, 26220, 26310, 26507, 26320, 26780, 26781, 26782, 26786’s information out from Alarm file.
 Board Hardware Fault :ALM-26200, ALM-26765;
 RF Unit Hardware Fault: ALM-26532;
 Optical module Fault: ALM-26220/ ALM-26310/ ALM-26507/ ALM-26320/ ALM-26780/ALM-26781/ALM-26782/ALM-26786.
1.12.4 Measures
If these alarms occur, refer to Alarm Help to solve them. Devices don’t allow active alarm existed.

1.12.5 Reference
None.
1.13 RF Unit Channel Abnormal Alarm
1.13.1 Location

02 Health Check 03 Alarm Analysis 05 RF Unit Channel Abnormal Alarm
This rule is mainly used to collect information of the distribution of RF unit channel abnormal alarms in the entire network. If Alarm ID = 26520,
26521, 26522, 26529, 26234, 26323 occurs on a board, it will lead to an excessive return loss at the antenna port, a decreasing sensitivity of RF unit, a
decreasing demodulation performance of a cell or a service cut-off carried on the RF unit in serious case.
1) Output eNodeBs’ eNodeB ID, eNodeB Name, Alarm ID, Alarm Name, Severity, Location, Occurrence Time, Clearance Time and Alarm Times
with this alarm.
RF Unit Channel Abnormal Alarm

eNode eNodeB Alar Alarm Occurrence Clearanc Alarm
Severity Location
B ID Name m ID Name Time e Time Times
RF Unit Cabinet No.=0, Subrack No.=60, Slot No.=0, TX
VSWR Channel No.=1, Board Type=LRRU, VSWR 2014-06-28

9043 9043 26529 Major - 1
Threshold Alarm Threshold (0.1)=30, VSWR(0.1)=74, 12:16:30
Crossed Output Power (0.1 dBm)=341
1.13.3 Principles
1) Take Alarm ID=26520, 26521, 26522, 26529, 26234, 26323’s information out from Alarm file.
 RF Unit TX Channel Gain Out of Range: Alarm ID = 26520;
 RF Unit RX Channel RTWP/RSSI too low: Alarm ID = 26521;
 RF Unit RX Channel RTWP/RSSI unbalanced: Alarm ID = 26522;
 RF Unit VSWR Threshold Crossed (Major):Alarm ID = 26529;

 BBU CPRI Interface Error: Alarm ID = 26234;
 BBU IR Optical Interface Performance Degraded: Alarm ID = 26323.
1.13.4 Measures
1) Perform a power-off reset on the board and check whether the alarm is clear or not. (Please perform it during low-traffic hours, for example, in
the middle night.)
2) Contact engineers onsite. If the alarm is not clear, collect log information on the faulty board to Huawei engineers for troubleshooting.
1.13.5 Reference
None.
1.14 Entire System Alarm
1.14.1 Location

02 Health Check 03 Alarm Analysis 06 Entire System Alarm
This rule is mainly used to collect information of the distribution of entire system alarms in the entire network.
with power alarms.
Power Module Problem

eNode eNode Alar Alarm Alarm Occurrence Clearance Alarm
Location
B ID B Name m ID Name Severity Time Time Times
Mains Cabinet No.=0, Subrack
60028 2562 Input No.=7, Slot No.=0, Board 2014-05-11 2014-05-22

600289 Major 4
9 2 Out of Type=PMU, Specific 01:37:15 21:32:58
Range Problem=AC Failure


with fan alarms.
Fan Module Problem

eNodeB eNodeB Alarm Alarm Occurrence Clearance
Alarm ID Location Alarm Times
ID Name Name Severity Time Time
Cabinet No.=0, Subrack No.=8, Slot
Fan Major 2012-12-14 2012-12-14
230145 230145 25673 No.=0, Fan No.=Inner air circulation 1
Stalled Alarm 18:31:01 18:31:31
fan, Board Type=TCU
with Monitoring alarms.
Monitoring Module Problem

eNodeB eNodeB Alarm Alarm Occurrence Clearance Alarm
Alarm Name Location
ID Name ID Severity Time Time Times
Monitoring Cabinet No.=0, Subrack
2012-12-11 2012-12-15
230005 230005 25601 Device Major No.=8, Slot No.=0, Board 7
06:07:23 21:37:48
Hardware Fault Type=TCU
1.14.3 Principles
1) Take Alarm ID=25621, 25622, 25624, 25625, 25626, 25630, 25631, 25632, 25633, 25634, 25654, 26107, 26112, 26113, 26774, 26776, 26115,
26108, 25652, 25655, 25656, 25673, 26104, 26110, 26111, 25600, 25601, 25602, 25620’s information out from Alarm file.
 Power Module Problem: 25621, 25622, 25624-25626, 25630-25634, 25654, 26107, 26112, 26113, 26774, 26776, 26115, 26108.
 Fan Module Problem: 25652, 25655, 25656, 25673, 26104, 26110, 26111.
 Monitoring Module Problem: 25600-25602, 25620.
1.14.4 Measures
If these alarms occur, refer to Alarm Help to solve them. Devices don’t allow active alarms existed.
1.14.5 Reference
None.

1.15 Board Temperature Monitor
1.15.1 Location

02 Health Check 03 Alarm Analysis 07 Board Temperature Monitor
If a board’s temperature is too high, the quality of services carried on the board will be affected seriously. If a board is under high temperature for
a long time, or under high temperature condition frequently, it will increase the risk of board fault. This rule is used to collect information of boards which
is/was under high temperature.
1) Output boards’ information which are under high temperature alarm.
Boards Are Under High Temperature

eNodeB ID eNodeB Name CN SRN SN Board Type Occurrence Time Alarm Type
230307 230307 0 7 0 PMU 2012-12-14 23:16:08 Battery Temperature Unacceptable
2) Output boards’ information (Alarm Times & Cumulative Duration) which were under high temperature during the inspection period.
Boards Were Under High Temperature

eNodeB eNodeB Board Alarm Alarm Cumulative Alarm
CN SRN SN Alarm Type
ID Name Type Occurrence Time Duration(Mins) Times
Battery
2012-12-13
230307 230307 0 7 0 PMU Temperature 4014.5 7
21:16:10
Unacceptable
3) Output the entire network’s boards and fans temperature information in segment according to the temperature.
Temperature Statistic
Temperature Statistic (℃) Temperature State Board Number Fan Number
Temperature
<-20 1 0
Exception
1.15.3 Temperature Principles
[-20, 0) 2 1
Normal
Temperature
1) [0, 35) 3 2 Get active alarms and historical alarms list in the entire
Normal
Temperature
[35, 50) 2 2 network from alarm file (alarm.csv) and filter out eNodeBs
Normal
Temperature with any of the below alarms.
[50, 80) 1 1
Exception
Temperature
[80, 100] 0 0
Exception Huawei Proprietary and Confidential Page 77 of 361
 Board Powered Off (Alarm ID = 26214) and Power off Cause = Temperature Too High;
 Board Temperature Unacceptable (Alarm ID = 26104) and Specific Problem = Temperature too High;
 RHUB Temperature Unacceptable (Alarm ID = 26771);
 Environment Temperature Unacceptable (Alarm ID = 25650);
 Cabinet Temperature Unacceptable (Alarm ID = 25652);
 Battery Temperature Unacceptable (Alarm ID = 25654);
 Cabinet Air Outlet Temperature Unacceptable (Alarm ID = 25655);
 Cabinet Air Intake Temperature Unacceptable (Alarm ID = 25656);
 RF Unit Temperature Unacceptable (Alarm ID = 26525);
2) If there is no information under ClearanceTime field, output related information to the ‘Boards are under high temperature’ table.
3) If there is information under ClearanceTime field, output related information to the ‘Boards were under high temperature’ table.
Note: Mark boards which are/were under high temperature as abnormal.
4) Check the entire network’s boards and fans temperature information by MML’s DSP BRDTEMP and DSP FAN command.
a) Run DSP BRDTEMP command to find Board Temperature (degree Celsius) to get all boards’ temperature.
b) Run DSP FAN command to find Temperature (degree Celsius) to get all fans’ temperature.
1.15.4 Measures
Solve it by alarm reference.
1.15.5 Reference
None.
1.16 Check of Transmit Channel Power Consistency
1.16.1 Location

02 Health Check 04 Data Configuration Check 01 Check of Transmit Channel Power Consistency

If maximum output powers on the TX channel are different, service speed will decrease and users’ perception will be affected. This rule is
mainly used to collect RF’s power locking information.
1) Output RRU number under inconsistent state of maximum output powers on the TX channel.
Result of Power Locking Check

Transmit Channel Locking State RRU Number
Inconsistent 0
2) Output each RF channel’s power locking state information (only output inconsistent and locked state).
Power Locking State

eNod eNodeB C SR S TX Channel RRU Hardware Maximum Output Maximum Output Power on
eB ID Name N N N No. Type Power on the TX Channel(10mW) the TX Channel(10mW)
60059 -xuhuixu 0 62 0 0 MRRU 4000 3500
1.16.3 Principles
1) Get RRU’s configuration information from configuration file, including CN, SRN, SN and RRU type.
2) Run DSP TXBRANCH command to get RRU’s hardware maximum output power and maximum output power on the TX channel based on the
result of CN, SRN and SN from 1).
3) Judge each TX channel’s locking state.
 If hardware maximum output power on the TX channel >= maximum output power on the TX channel, transmit power in the TX channel is
considered as locked.
 If not, transmit power in the TX channel is considered as unlocked.
4) Collect information of each RRU’s power locking state.
 If all of the channels in a RRU are locked, this RRU is considered as locked.
 If all of the channels in a RRU are unlocked, this RRU is considered as unlocked.
 If one of the channels in a RRU is unknown, this RRU is considered as unknown.
 If one of the channels in a RRU is locked and another channel is unlocked, this RRU is considered as inconsistent.
5) For locked and inconsistent RRU, judge their TxRxMode field. If TxRxMode=0 (1R1T mode), don’t output. Otherwise, output this eNodeB’s
information and count the number of RRUs as exceptional number.

1.16.4 Measures
Check whether the config of RS/PA/PB conforms to the plan or not. PA runs MOD CELLDLPCPDSCHPA, RS and Pb run MOD PDSCHCFG
to modify their values.
1.16.5 Reference
None.
1.17 Check of Blind HO (redirection) Priority of Inter-RAT Neighboring Cell
1.17.1 Location
02 Health Check 04 Data Configuration Check 02 Check of Blind HO (redirection) Priority of Inter-RAT Neighboring Cell
If frequency priority is set to 0 but this frequency isn’t selected as the target frequency for a blind handover, the call drop rate will increase. This
rule is mainly used to collect cells’ related information with abnormal blind HO (redirection) of inter-RAT neighboring cell. (Note: If blind HO switch is
enabled and only intra-RAT’s blind HO is involved, this check can be ignored.)
1) Output cells’ related information with abnormal blind HO (redirection) of inter-RAT neighbor cell.
Check Result of Blind HO (redirection) Priority of Inter-RAT Neighbor Cell

CDMA
BlindHo(re GERAN L2W L2G L2W HO L2G HO CSFB
eNod eNodeB Local UTRAN System System
direction)S System Redirection Redirection Success Success Executio
eB ID Name Cell ID Neighbor Cell Neighbor
witch Neighbor Cell Success Rate Success Rate Rate Rate n Rate
Cell
63087 -- 1 ON All UTRAN All GERAN - - - - -
4 blind HO blind HO
Not
priority and all priority and all
configured
connect connect
frequency frequency

priorities are 0 priorities are 0

All UTRAN All GERAN
blind HO blind HO
Not
63087 priority and all priority and all
- 2 ON 100% - - - 100%
configured
4 connect connect
frequency frequency
priorities are 0 priorities are 0
1.17.3 Principles
1) Check the value of HoModeSwitch under ENODEBALGOSWITCH from XML file to find whether BlindHoSwitch is turned on and list its state
into the last table.
2) Check all of the cells in this eNodeB’s UTRAN and GERAN system neighboring cell and judge whether each system’s blind handover switch
and frequency priority are 0 or not. Meantime, check whether CDMA system neighboring cell is configured.
a) Check all the cells in the eNodeB’s UTRAN system neighboring cell: Check the value of BlindHoPriority under UTRANNCELL and the
value of ConnFreqPriority under UTRANNFREQ.
 If both of BlindHoPriority and ConnFreqPriority are 0, mark it as abnormal.
 If both of BlindHoPriority and ConnFreqPriority are not configured or one of them are not configured, mark it as abnormal.
 If one of BlindHoPriority and ConnFreqPriority is not 0, considered as normal.
b) Check all the cells in the eNodeB’s GERAN system neighboring cell: Check the value of BlindHoPriority under GERANNCELL and the
value of ConnFreqPriority under GERANNFREQGROUP.
 If both of BlindHoPriority and ConnFreqPriority are 0, mark it as abnormal.
 If both of BlindHoPriority and ConnFreqPriority are not configured or one of them are not configured, mark it as abnormal.
 If one of BlindHoPriority and ConnFreqPriority is not 0, considered as normal.
c) Check whether CDMA system neighboring cell is configured: If Cdma20001XrttCellId under CDMA20001XRTTEXTCELL or
CDMA20001XRTTNCELL has value, it is considered as normal.
Note: If all of these three neighboring cells have exceptions, this cell is considered as abnormal and output its related information.
3) Use original traffic measurement data from the first report to get each cell’s L.RRCRedirection.E2W, L.RRCRedirection.E2W.PrepAtt,
L.RRCRedirection.E2G , L.RRCRedirection.E2G.PrepAtt, L.IRATHO.E2W.ExecSuccOut , L.IRATHO.E2W.ExecAttOut,
L.IRATHO.E2G.ExecSuccOut, L.IRATHO.E2G.ExecAttOut, L.CSFB.E2W, and L.CSFB.E2G, L.CSFB.E2T, L.CSFB.PrepSucc during the

inspection period and calculate each cell’s L2W redirection success rate, L2G redirection success rate, L2W handover success rate, L2G
handover success rate, and CSFB execution rate during the inspection period.
Each counter’s meaning and formula is listed below.
 L2W redirection success rate = L.RRCRedirection.E2W / L.RRCRedirection.E2W.PrepAtt;
 L2G redirection success rate = L.RRCRedirection.E2G / L.RRCRedirection.E2G.PrepAtt;
 L2W handover success rate = L.IRATHO.E2W.ExecSuccOut / L.IRATHO.E2W.ExecAttOut;
 L2G handover success rate = L.IRATHO.E2G.ExecSuccOut / L.IRATHO.E2G.ExecAttOut;
 CSFB execution rate (5C0X) = (L.CSFB.E2W + L.CSFB.E2G) / L.CSFB.PrepSucc;
 CSFB execution rate (other versions) = (L.CSFB.E2W + L.CSFB.E2G + L.CSFB.E2T) / L.CSFB.PrepSucc.
1.17.4 Measures
A larger frequency priority value indicates a higher priority. Modifying it by MML command can decrease the call drop rate.
MML command: MOD UTRANNFREQ. The parameter modification has no impact on the equipment.
1.17.5 Reference
None.
1.18 IPPATH Check
1.18.1 Location

02 Health Check 04 Data Configuration Check 03 IPPATH Check
If missing IP path occurs, corresponding services will be interrupted. If firewall of the transport network or peer core network forbids the
function of Ping when IPPATH channel detection switch is enabled, it will lead to detection failure and services may be affected. The abnormal result of
GTPU does not affect the usage of live network, but it is suggested to enable GTPU’s static detection switch (MOD GTPU: STATICCHK = ENABLE).
This rule is mainly used to collect eNodeBs’ related information with this risk.
1) Output eNodeB and its corresponding IP information with missing DSCP.

IPPATH Config Check(QOS) – DSCP Missing

eNodeB ID eNodeB Name Local IP Peer IP DSCP
62009 PanaromaUAQ2009 10.104.23.226 10.104.23.58 0
2) Output eNodeBs’ related information with disabled GTPU static detection switch to report IPPATH fault timely.
For versions before V100R010C10:
IPPATH Config Check –GTPU Static Detection Switch

eNodeB ID eNodeB Name Reason
Disabled GTPU static
62009 62009
detection switch
For V100R010C10 and its later versions:
IPPATH Config Check –GTPU Static Detection Switch

eNodeB ID eNodeB Name EP Model Link Model
103043 TPDHS_002_ Disabled GTPU static detection switch Disabled GTPU static detection switch
103060 KTSMS_003 - Disabled GTPU static detection switch
1.18.3 Principles
1) Missing DSCP check:
a) Collect all PRI values under UDTPARAGRP to make up group A.
b) Check the value of PATHTYPE under IPPATH field. When PATHTYPE = FIXED~0, take its corresponding DSCP value under IPPATH
to make up group B (When PATHTYPE is FIXED, DSCP is valid). Collect IP pairs (Local IP + Peer IP) these IPPATH used.
c) If there is a value exiting in group A but not in group B, it is considered as missing DSCP (missing IPPATH).
d) If there is a missing IPPATH, corresponding services will be interrupted.
e) Collect eNodeBs’ related information with this risk.
2) GTPU static detection switch:
For versions before V100R010C10:
a) Check the value of STATICCHK under GTPU from XML file. If STATICCHK = 0, it indicates that GTPU static detection switch is
disabled.
For V100R010C10 and its later versions:
b) EP model: Check the value of STATICCHK under USERPLANEPEER. If it is 0 (DISABLE), output this exception. If it is 1(ENABLE),
don’t output anything. If it is 2 (FOLLOW_GLOBAL), keep on judging STATICCHK under GTPU and mark it as abnormal if it is
DISABLE.

c) Link model: Check the value of STATICCHK under IPPATH. If it is 0 (DISABLE), output this exception. If it is 1(ENABLE), don’t output
anything. If it is 2 (FOLLOW_GLOBAL), keep on judging STATICCHK under GTPU and mark it as abnormal if it is DISABLE.
1.18.4 Measures
1) Increase priority of users’ data on IPPATH (DSCP).
2) MML command: ADD IPPATH: PATHID=0, JNRSCGRP=DISABLE, PATHTYPE=FIXED, DSCP=3.
3) It is suggested to enable GTPU static detection switch.
1.18.5 Reference
None.
1.19 Clock Configuration Check
1.19.1 Location

02 Health Check 04 Data Configuration Check 04 Clock Configuration Check
If the clock mode is time (phase) synchronization, check whether the clock source is IPCLK, GPS, or TOD. If not, it is considered as an incorrect
configuration. When the working mode of the clock source is free, it indicates the system clock works in free-running mode, that is, the system clock does
not trace any reference clock source. If the eNodeB is configured a TOD clock but without USCU board, it is also considered as incorrect configuration of
clock source. Check whether UMPTa board and ETH port transmission are used and whether UMPTa is configured SyncE (out). When clock source is
NTP but not configured NTPCP, it will lead to non-aligned time and unrealizable reported traffic measurement. This rule is mainly used to collect
information of these incorrect configurations of clock source.
1) Output eNodeBs’ information which are under time (phase) synchronization mode but without IPCLK, GPS, or TOD clock source.
Clock Synchronization Mode Check (Abnormal)

eNodeB ID eNodeB Name Clock ID Clock Source Cause
Reference clock doesn’t
900811 KPI1_eNB1_11 0 Peer Clock
support time synchronization.

2) Output eNodeBs’ information with a free clock source mode.
Clock Source Mode Check (Abnormal)

eNodeB ID eNodeB Name Cause
62085 62085 Working mode is Free.
3) Output eNodeBs’ information which refers to TOD clock but without USCU board.
TOD Clock Source Check (Abnormal)

eNodeB ID eNodeB Name Cause
62091 62091 No USCU board configured
4) Output eNodeBs’ related information which configured UMPTa board and SyncE (out) and used ETH port transmission.
Clock Output Check of SyncE (Abnormal)

C
eNodeB ID eNodeB Name SRN SN ETH0 Port State ETH1 Port State eNodeB Software Version
N
BTS3900
900812 KPI1_eNB2_12 0 0 19 - Up
V100R011C10SPC980B016
5) Output eNodeBs’ related information if they are not configured any clock source.
Clock Source Check (Abnormal)

eNodeB ID eNodeB Name Clock Source Cause
0 PL2_eNB2_24 0 Reference clock is not configured.
1.19.3 Principles
1) Check the clock synchronous mode: Check the value of CLKSYNCMODE field from XML file and run DSP CLKSRC to check eNodeB’s current
clock source configuration. If CLKSYNCMODE = 1, it indicates the synchronous mode is TIME (time or phase). In this case, the clock source must
be IPCLK, GPS or TOD. If not, mark it as abnormal.
2) Check the working mode of clock source: Check the value of CLKMODE field from XML file. If MODE = 2, it indicates free working mode and
mark it as fatal error.
3) Check of TOD clock source (Exception): Run DSP CLKSRC to check eNodeB’s clock source. If it is TOD, check whether USCU board is used by
DSP BRD. If not, mark it as an error.
4) Clock output check of SyncE (Exception):
a) Check the information of software version: Run LST SOFTWARE command, record the software version from “Main Area” and go to next
step.
b) Run DSP BRD command and check the content of “Config Type”. If there is “UMPT” board, record its CN, SRN and SN and go to next
step, or end.
c) Run DSP BRDMFRINFO command and check the content of “Type” to get the detail type of UMPT. If Type =

WD22UMPTa1/WD22UMPTa2/WD22UMPTa6, go to next step, or end.
d) Check whether Type=1 (OUT) is exited under SYNCETH from XML file. If yes, go to next step, or end.
e) Run DSP ETHPORT command to check whether “Port Status” of Port No. = 0 and Port No. = 1 of UMPTa board are “Up”. If one of them
is “Up”, output this eNodeB’s related information.
5) Check whether the value of TIMESRC under TIMESRC from XML file is 0 (NTP mode). If yes, check whether IP information is configured in
NTPCP. If not, print out the exception.
1.19.4 Measures
1) Check the configuration parameters of the reference clock source.
2) Add NTPC.
1.19.5 Reference
None.
1.20 IPRT Check
1.20.1 Location

02 Health Check 04 Data Configuration Check 05 IPRT Check
Lack of routes will lead to link disconnection and service interruption. This rule is mainly used to collect eNodeBs’ related information which
lack routes.
1) Check whether the peer IP addresses of the OM link, SCTP link, S1 link, clock link, and IKEPEER have been configured with corresponding
routes. If not, it is considered as lack of routes and output these eNodeBs’ related information.
Missed Router Check

eNodeB ID eNodeB Name Local IP Peer IP Service Type Cause
898989 898989 1.1.1.1 2.2.2.2 OM Lack of routes

1.20.3 Principles
1) Get local IP and peer IP address of OMCH, SCTPLINK, IPPATH, IPCLKLINK and IKEPEER from XML file.
2) Check these links’ local IP mask.
3) Do AND operation with the above local addresses and the masks from 2) to get Rst1. Do AND operation with the above peer addresses and the
masks from 2) to get Rst2. If Rst1= Rst2, end. If there are some links that Rst1! = Rst2, record these links’ peer addresses.
4) Check routing configuration table by IPRT from configuration file.
5) If there is a default route (a route to 0.0.0.0), it is considered as normal and end, or go to next step.
6) Do AND operation with all the destination IPs from 4) and its masks from routing table to get Rst11. Do AND operation with all the peer IPs
recorded from 3) and its masks from routing table to get Rst22.
7) Compare Rst11 and Rst22: If some address exists in Rst11 but not in Rst22, it indicates some link couldn’t find its corresponding route and
output this link’s information.
1.20.4 Measures
Lack of routes: Add corresponding route by ADD IPRT.
1.20.5 Reference
None.
1.21 Check of S1 Link State (Block)
1.21.1 Location

02 Health Check 04 Data Configuration Check 06 Check of S1 Link State (Block)
If UEs are in idle mode, new users cannot access the network after S1 interface is blocked. This rule is mainly used to collect eNodeBs’
information with blocked S1 interface.
1) Output eNodeBs’ information with blocked S1 interface.

eNodeBs’ Information with Blocked S1 Interface

S1 MME S1 S1 Mme Is Served S1 Link
eNod eNodeB Prio S1Interface Mme Served
Interfac Relea Interfaces Interfac Over Gumme Fault
eB ID Name rity UserNum Name Plmns
e ID se Block e State Load is Reason
mmesvc
62009 62009 0 0 TRUE 255 Normal FALSE 2 424-03 - NULL
dxb1
1.21.3 Principles
1) Check the value of S1InterfaceIsBlock under S1Interface field from XML file.
2) If S1InterfaceIsBlock=1, it indicates that S1 link is blocked and go to next step. Or end.
3) Output this eNodeB’s information and mark it as abnormal.
1.21.4 Measures
Run MML’s UBL S1INTERFACE command to unblock S1 link.
1.21.5 Reference
None.
1.22 IPsec Configuration Check
1.22.1 Location

02 Health Check 04 Data Configuration Check 07 IPsec Configuration Check
If IPsec certificate or pre-shared key is not configured, IPsec negotiation will fail. This rule is mainly used to collect eNodeBs’ information with
this risk.
1) Output IPsec configuration overview of the entire network.
IPSec Config Overview

Config Type Number of Configured eNodeBs Number of Not Configured eNodeBs
IPSec certificate 2 1
IPSec pre-shared key 2 1
2) Output eNodeBs’ related information without IPsec configuration.
eNodeBs without IPSec Certificate

eNodeB ID eNodeB Name
53835 GL_1_3_L
3) Output eNodeBs’ related information without IPsec pre-shared key.
eNodeBs without IPSec Pre-shared Key

50403 CLOUD 3
1.22.3 Principles
1) Check the value of AUTHMETH under IKEPROPOSAL field from XML file.
a) If AUTHMETH = 9, which indicate authentication method is IKE_RSA_SIG, go to step 2).
b) If AUTHMETH = 8, which indicates authentication method is PRE_SHARED_KEY, go to step 3).
2) Check whether IKE certificate is exited under APPCERT. If yes, the certificate must be found in CERTMK. If not, output its information into
‘eNodeBs without IPSec certificate’ table and mark it as abnormal.
3) Check whether IKEVERSION = 2 (IKE_V2 state) and PKEY="*****" are exited under IKEPEER. If not, output its information into ‘eNodeBs
without IPSec pre-shared key’ table and mark it as abnormal.
4) Collect the information of eNodeBs’ IPSec certificate and IPSec pre-shared key configuration in the entire network and output them into ‘IPsec
configuration overview’ table.
1.22.4 Measures
Run MML command:
1) When the certificate is not configured, run ADD APPCERT to add IKE certificate.
2) When Pre-shared key is not configured, run MOD IKEPEER to configure IKEVERSIO and PKEY, which need to correspond with the pre-
shared key authentication.
1.22.5 Reference
None.

1.23 Statistic of X2 Link SCTPHOST Port
1.23.1 Location

02 Health Check 04 Data Configuration Check 08 Statistic of X2 Link SCTPHOST Port
Since X2 son setup uses SCTPHOST’s corresponding port number by default, the ports of resource test and destination test must be consistent. If
not, it will lead to some invalid X2 links by son setup. For existing normal X2 link, unavailable access in short time such as intermittent disconnection,
eNodeB’s reset and so on will lead to adding one-way X2 link, where the alarms occur. For newly setup X2 link, except alarms, it will lead to unavailable
access and invalid X2 process. It will also affect the handover, MLB and so on. This rule is mainly used to collect eNodeBs’ related information with this
risk.
1) Output eNodeBs’ related information with this risk.
Statistic of X2 Link SCTPHOST Port
Port No. Number(sites using this port/total sites) eNodeB ID
3000 1/11 225911

36422 10/11 NA
1.23.3 Principles
1) Check X2SonSetupSwitch and X2SonLinkSetupType field from LMT.XML file. If X2SonSetupSwitch = 1 and X2SonLinkSetupType = 0, it
indicates son setup switch is enabled and son link setup type is OSS and go to next step. Or end.
2) Check the value of CpEpGroupId under X2 field.
3) Find corresponding EPGROUP based on the value of CpEpGroupId from step 2) (CpEpGroupId=EPGROUPID) to get corresponding
SCTPHOSTID.
4) Get the value of PN under corresponding SCTPHOST from step 3).
1.23.4 Measures
1) Filter the entire network’s SCTPHOST and find X2’s port number. Make a percentage list based on different ratios of port numbers.
2) If the percentage of an eNodeB is lower than 10%, it is considered as abnormal.

1.23.5 Reference
None.
1.24 CSFB Feature Switch Check
1.24.1 Location

02 Health Check 04 Data Configuration Check 09 CSFB Feature Switch Check
When CSFB feature algorithm switch is not configured properly, CSFB traffic measurement will become 0 and will lead to a failure of LTE voice
service. This rule outputs eNodeBs’ related information with improper configured CSFB feature algorithm switch.
1) Output eNodeBs’ related information with improper configured CSFB feature algorithm switch.
CSFB Feature Switch Check

eNode UTRAN GERAN UtranFl GeranF CDMA20001 CDMA2000 UTRAN GERAN
eNode
B CSFB CSFB ashCsfb lashCsf XRTT CSFB 1xRTT eCSFB CSFBSteer CSFBSteeri
B ID
Name switch switch Switch bSwitch Switch Switch ingSwitch ngSwitch
62009 62009 ON ON ON ON ON ON ON ON
Note: CDMA2000 1xRTT eCSFB switch, UtranCsfbSteeringSwitch and GeranCsfbSteeringSwitch are new counters in eRAN6.0 version.
1.24.3 Principles
1) When a UE initiates a CSFB request, the eNodeB cannot determine which network to feedback according to 3GPP Release 9 specifications.
Therefore, CDMA CSFB and GU CSFB cannot be enabled at the same time.
2) Check UtranCsfbSwitch, GeranCsfbSwitch, UtranFlashCsfbSwitch, GeranFlashCsfbSwitch, UtranCsfbSteeringSwitch,
GeranCsfbSteeringSwitch, Cdma1xRttCsfbSwitch and Cdma1XrttEcsfbSwitch from XML file.
3) Cdma1xRttCsfbSwitch/Cdma1XrttEcsfbSwitch can’t be enabled with other 6 switches at the same time. Do AND operation with
Cdma1xRttCsfbSwitch / Cdma1XrttEcsfbSwitch and other 6 switches, output related information and mark it as abnormal if the result is 1.

1.24.4 Measures
1) Please refer to the description of 4.1 and 4.2 in the feature document.
http://support.huawei.com/hedex/hdx.do?
lib=SC0000817918GZC0304J&v=05&tocLib=SC0000817918GZC0304J&tocV=05&id=GZC0304J_05_10000&tocURL=resources%252fzh%252dcn
%255fbookmap%255f0001792984%252ehtml&p=t&fe=1&ui=3&keyword=lofd&keyword=001090.
Note: CDMA CSFB and GU CSFB cannot be enabled at the same time. Please modify it based on actual business plan.
2) MML command: MOD ENODEBALGOSWITCH.
1.24.5 Reference
None.
Note: This rule is just for eRAN6.0 and eRAN6.1 version.
1.25 Fast ANR Parameter Check
1.25.1 Location

02 Health Check 04 Data Configuration Check 10 Fast ANR Parameter Check
If fast ANR is improperly configured and then initiated, the timer of UE reporting measurements will not be released when exiting network,
which will lead to a leakage of timer resource. After running in this state for a long time, application for timer resource will fail and a series of KPI
counters (RRC setup success rate, eRAB setup success rate, call drop rate and the average rate of a cell) will become abnormal. This rule is mainly used to
collect eNodeBs’ information with improper fast ANR configuration.
1) Output eNodeBs’ information with improper fast ANR configuration.
Fast ANR Parameter Check

FastAnrRprtAmoun
eNodeB ID eNodeB Name FastAnrRprtInterval
t
132620 0 64 5120ms

1.25.3 Principles
1) Check the value of FastAnrRprtInterval and FastAnrRprtAmount under ANR field from XML file.
2) If the value of FastAnrRprtInterval > 6, which indicates fast ANR PCI report interval is longer than 5120ms, go to next step or end.
3) If FastAnrRprtAmount ≥ 6, which indicates fast ANR PCI report amount is more than 64 times, output this exception.
1.25.4 Measures
Modify fast ANR’s configuration to default value. (Run MML command: MOD ANR: FastAnrRprtAmount=r64, FastAnrRprtInterval=5120m)
1.25.5 Reference
None.
Note: This rule is just for eRAN6.0 and eRAN6.1.
1.26 eUCellSectorEqm Configuration Check
1.26.1 Location

02 Health Check 04 Data Configuration Check 11 eUCellSectorEqm Configuration Check
When cell sector equipment is configured improperly, cell’s activation will fail if intra-frequency cells in an eNodeB use same sector equipment.
This rule is mainly used to collect cells’ related information with improper cell sector equipment configuration.
1) Output cells’ related information with improper cell sector equipment configuration.
Abnormal Cell
eNodeB ID eNodeB Name Local Cell ID SectorEqmId Downlink earfcn Description
22222 990362 1 1 3100 Improper SectorEqmId configuration
1.26.3 Principles
1) Check the value of LocalCellId and SectorEqmId under eUCellSectorEqm field from XML file.
2) Judge whether LocalCellId is same with SectorEqmId. If yes, go to next step. Or end.

3) Check whether the values of DlEarfcn, corresponding with LocalCellId, under Cell field are same or not. If yes, print it out and mark it as
abnormal. Or end.
1.26.4 Measures
Modify sector equipment to correspond with an intra-frequency cell. (MML command: MOD EUCELLSECTOREQM)
1.26.5 Reference
None.
3.13 DRX Enter/Exit Threshold Check
3.13.1 Location

02 Health Check 04 Data Configuration Check 11 Check of DRX Enter/Exit Threshold
In a big traffic cell (Max users are above 300), sending DRX parameters to UEs could reduce the amount of RRC reconfiguration signaling
generated from UEs since they frequently enter or exit DRX mode during the initial access without additional RRC connecting reconfiguration signaling.
This rule is mainly used to collect eNodeBs’ related information with this risk.
1) Output cells’ information which their FddEnterDrxThd or FddExitDrxThd are not configured to 1000.
Abnormal DRX Threshold List
eNodeB ID eNodeB Name Local Cell ID Cell Name FddEnterDrxThd FddExitDrxThd
1421 BTS3900L 0 Cell0 300 800
3.13.3 Principles
1) Judge whether DRX is enabled. If the following two conditions are met at the same time, it is considered that DRX is enabled.
a) Drx.DrxAlgSwitch =1 //enumerated value 1 means ON.
b) Check all of DrxParaGroup referenced by CELLSTANDARDQCI. If one of EnterDrxSwitch under corresponding DrxParaGroup is 1 //
enumerated value 1 means ON.

2) Check the value of FddEnterDrxThd and FddExitDrxThd for each cell under CellDrxPara field from LMT.XML file.
3) If some cell’s FddEnterDrxThd / FddExitDrxThd is not 1000, it is considered that main control board’s CPU has an overload risk and output this
cell’s related information to “Abnormal DRX Threshold List”.
3.13.4 Measures
In a big traffic cell (Max users are above 300), run MOD CELLDRXPARA command to set CellDrxPara.FddEnterDrxThd and
CellDrxPara.FddExitDrxThd to 1000.
3.13.5 Reference
None.
1.27 Excessive pRRUs Under Co-MPT
1.27.1 Location

02 Health Check 04 Data Configuration Check 12 Excessive pRRUs Under Co-MPT
1.27.2 Rule Description
The max number of pRRU configurations under co-MPT scenario is 48. If the number is more than that, it will lead to CPU overload, a longer
recovery time for cells or unavailable cells in serious cases. This rule is mainly used to collect eNodeBs’ information with excessive pRRUs.
1) Output eNodeBs’ information with excessive pRRUs.
Abnormal Data
eNodeB ID eNodeB Name Current Software Version Product Type pRRU Number
472114 923 BTS3900 V100R010C10 DBS3900_LTE 63
1.27.3 Principles
1） Check the value of SWVERSION under NE from XML file. If SWVERSION is any one of BTS3900 V100R009C00, BTS3900 V100R010C10
or BTS3900 V100R011C00, go to next step, or end.
2） Check the value of PRODUCTTYPE under NODE from XML file. If PRODUCTTYPE = 1 (DBS3900_LTE), 2 (BTS3900_LTE), 3

(BTS3900A_LTE), 4 (BTS3900L_LTE), 5 (BTS3900AL_LTE) or 7(DBS3900_LampSite_LTE), go to next step, or end.
3） Check the RT parameter under RRU from XML file to get the number of pRRU configurations. If RT = 783 (MPMU) and the number of pRRU
configurations is more than 48, mark it as abnormal and output its related information.
1.27.4 Measures
1) Recovery measures: According to the network planning, delete the extra pRRUs.
2) Solutions: Upgrade the base station to BTS3900 V100R011C10 or later.
1.27.5 Reference
None.
1.28 Check of Flash CSFB and RIM Configuration
3.13.6 Location

02 Health Check 04 Data Configuration Check 12 Check of Flash CSFB and RIM Configuration
When Flash CSFB and RIM are configured improperly, it will lead to abnormal triggering of CSFB process. This rule is used to collect
eNodeBs’ related information with improper Flash CSFB and RIM configuration.
1) Output eNodeBs’ related information with improper Flash CSFB and RIM configuration.
Abnormal Config
eNodeB eNodeB UtranFlashCsfb UTRAN RIM GeranFlashCsfb GERAN RIM
ID Name Switch SWITCH Switch SWITCH

132620 132620 ON OFF ON OFF
3.13.8 Principles
1) Check the value of UtranFlashCsfbSwitch, UTRAN RIM SWITCH, GeranFlashCsfbSwitch and GERAN RIM SWITCH from XML
configuration file.

2) If UtranFlashCsfbSwitch = 1, it means the switch is on, and then judge whether UTRAN RIM SWITCH is on. If UTRAN RIM SWITCH = 0,
which means the switch is off, output this eNodeB’s related information and mark it as abnormal.
3) Then check GSM side. If GeranFlashCsfbSwitch = 1, it means the switch is on, and then judge whether GERAN RIM SWITCH is on. If GERAN
RIM SWITCH = 0, which means the switch is off, output this eNodeB’s related information and mark it as abnormal.
3.13.9 Measures
Enable flash CSFB switch and RIM switch at the same time. (MML command: MOD ENODEBALGOSWITCH)
3.13.10 Reference
None.
3.14 2T4R Configuration Check
3.14.1 Location

02 Health Check 04 Data Configuration Check 12 2T4R Configuration Check
If it is a common 2T4R cell and its corresponding sector configuration is 4T4R receive/transmit mode by 2 RRUs, the cell will reconstruct when
there is no user and the measured counter L.Cell.Unavail.Dur.Sys is not 0. This rule is mainly used to collect cells’ related information which accord with
above configurations.
1) Output cells’ related information which accord with above configurations.
eNodeBs Accord with the Configurations

eNodeB ID eNodeB Name Local Cell ID Cell Name Cell Config RRU Rx/Tx Mode
CN: 0 SRN: 69 SN: 0 ANTN: 2 ANTTYPE: 3

70068 CSPC104 0 CSPC-0 2T4R
CN: 0 SRN: 69 SN: 0 ANTN:1 ANTTYPE:3

3.14.3 Principles
1) Check the value of MultiRruCellFlag and TxRxMode under Cell field from LMT.XML file. If MultiRruCellFlag = 0 and TxRxMode = 3, it
means a common 2T4R cell and go to next step. Or end.
2) Check the value of LocalCellId and SectorEqmId under EUCELLSECTOREQM field to confirm its sector equipment.
3) Find its corresponding sector from SECTOREQM field based on the value of SectorEqmId from step 2) and judge whether this sector
configuration is 4T4R mode by 2RRUs. The method is shown below.
a) Check all the CN, SRN and SN under SECTOREQMANTENNA field of this sector equipment.
b) Check all the CN, SRN and SN under eNodeB’s RRU.
c) If CN, SRN and SN from a) are any two of the RRU’s CN, SRN and SN and all the corresponding ANTTYPE forms a 4T4R mode, output
this cell’s related configuration information. Or end.
 ANTTYPE = 1, 2, 3 means RX_MODE, TX_MODE and RXTX_MODE separately.
3.14.4 Measures
Modify these cells’ sector configuration to 2T4R mode according to the investigating result.
3.14.5 Reference
None.
Note: This rule is for eRAN7.0 version.
3.15 License Running State Check
3.15.1 Location

02 Health Check 05 License State Check 01 License Running State Check
“Default state” indicates eNodeBs are running without license. “Keepalive state” indicates the license has expired but still in grace period. For
commercial LTE network, all eNodeBs’ license state must be commercial license and under normal state. This rule is mainly used to check each eNodeB’s

license state and output eNodeBs’ information with non-normal state and eNodeBs with normal state but their license will expire soon.
1) Output eNodeBs’ number under different license state.
Result of License State Statistic

License State eNodeB Number
Demo 1
Normal 1
2) Output eNodeBs’ information with non-normal license state.
Result of License State Check

eNodeB ID eNodeB Name LicenseState License Expiration Time
112172 EHA172 Demo 2015-10-08
112172 EHA172 Normal 2012-04-08
3.15.3 Principles
1) eRAN6.0 and eRAN6.1:
a) Get each eNodeB’s name, ID, State and Expire information by MML’s DSP LICENSE command. If LicenseState and Expire satisfy one of
the following conditions, it is considered as abnormal and output this eNodeB and its license information.
 Status ≠ Normal.
 Status = Normal, (Expire – the last day of traffic measurement）< 15.
2) Versions of eRAN7.0 and later:
a) At first, get each eNodeB’s name, ID, State and Expire Date by MML’s DSP LICINFO command. If there is no DSP LICINFO
command, run DSP LICENSE instead.
b) If LicenseState and Expire satisfy one of the following conditions, it is considered as abnormal and output this eNodeB and its license
information.
 Status ≠ Normal.
 Status = Normal, (Expiration Date – the last day of traffic statistic）< 15.
3.15.4 Measures
1) If an eNodeB’s license state is not ‘Normal’, run MML command (INS LICENSE) to install a commercial license.

3.15.5 Reference
None.
3.16 License Item Consistency Check
3.16.1 Location

02 Health Check 05 License State Check 02 License Item Consistency Check
If Allocated and Config of the license are not consistent, it will restrict the usage of features in the license, resulting in that feature services can’t
work normally in the end. This rule is used to check whether Config is larger than Allocated by DSP LICENSE. If yes, mark it as abnormal and print out
the result.
1） Output eNodeBs’ information if their Config are larger than Allocated.
License Config Larger Than Allocated

eNodeB ID eNodeB Name License Identifier License Item Allocated Config Actual Used Expiration Time
630828 -- LLT1EOAM01 Ethernet OAM(FDD) 0 1 0 NULL
Bidirectional Fault
630828 -- LLT1BFD01 0 2 0 2014-08-07
Detection (FDD)
3.16.3 Principles
1） Check license’s configuration information by MML’s DSP license command. Output eNodeBs’ related information if their Config are larger than
Allocated.
3.16.4 Measures
1) If Allocated is not enough, please add license. If Config is not reasonable, modify eNodeB’s configuration in time.
3.16.5 Reference
None.

3.17 Check of LTE eRAN6.0&eRAN6.1 Life Cycle
3.17.1 Location

02 Health Check 06 EOX Check 01Check of LTE eRAN6.0&eRAN6.1 Life Cycle
To help you better cope with challenges brought by market changes and technological innovations, Huawei hereby informs you of the milestones
in the life cycle of LTE FDD eRAN6.0 & eRAN6.1. Hopefully this information can give you a reference on making future network development plans.
The sales of LTE FDD eRAN6.0 & eRAN6.1 was stopped on June 30, 2015. Please note that you can no longer order LTE FDD eRAN6.0 & eRAN6.1
after the EOM date.
1) Output LTE eRAN6.0&eRAN6.1 life cycle’s milestone.
LTE eRAN6.0&eRAN6.1Life Cycle Information

Current Software eNodeB
EOM EOFS EOS Recommendation
Version Number
Use or upgrade to a new
LTE FDD V100R006C00 250 2015-06-30 2016-06-30 2016-12-31
version
3.17.3 Principles
Check the current time and compare it with EOM (2015-06-30). As long as the former is larger than the latter, output eNodeBs’ number.
3.17.4 Measures
Huawei suggests that you use new version or upgrade your eRAN6.0/eRAN6.1 to eRAN7.0/eRAN8.1, which has similar features and capabilities
but optimized functions compared with eRAN6.0/eRAN6.1. We will continue to provide high-level services for your new software version.
3.17.5 Reference
End of marketing Announcement for DBS3900/BTS3900/BTS3900A/BTS3900L/BTS3900AL LTE FDD eRAN6.0&eRAN6.1:
http://www1.huawei.com/en/ProductsLifecycle/RadioAccessProducts/LTE-Products/hw-419516.htm

3.18 CPU Load Evaluation
3.18.1 Location

03 Resource Load Analysis 01 Board Load Evaluation 01 CPU Load Evaluation
When CPU load of a board is too high, it may lead to site maintenance or a worse service quality. By monitoring average CPU usage of BBP per
hour in one day, take the greatest as the peak of average CPU usage in this day. If this peak is greater than 70%, it is considered as capacity risk. This rule
is mainly used to output boards’ related information with this risk.
1) Output actual times of average CPU usage of MPT board >= 70%.
Actual Times of Average CPU Usage of MPT Board >= 70%
eNodeB ID eNodeB Name CN SRN SN Board Type Actual Times
5014 TMO-5014 0 0 7 WD22UMPTa2 1

2) Output actual times of average CPU usage of BBP board >= 70%.
Actual Times of Average CPU Usage of BBP Board >= 70%
eNodeB ID eNodeB Name CN SRN SN Board Type Actual Times
5014 TMO-5014 0 0 3 - 1
3) Output average CPU usage of MPT boards and other related information.
Information of TOP MPT Boards with Highest Average CPU Usage

VS.BBUBo VS.BBUBo L.Traffic.B L.Traffic.Boar L.Traffi eNodeB eNodeB
eNode eNodeB SR Board Time(by
CN SN ard.CPULo ard.CPULo oard.CPUL d.UPlane.CPU c.User. Reset Reset
B ID Name N Type hour)
ad.Mean ad.Max oad.AVG Load.MAX Avg Time Type
2014-01-
WD22U
5014 T5014 0 0 7 71.00% 21.00% 6.00% 21.00% 10.21 24 - -
MPTa2
16:00:00
2014-01- 2014-01-
WD22U NE
5014 T5014 0 0 7 69.00% 19.00% 5.95 24 24
MPTa2 startup
17:00:00 17:10:00
5014 T5014 0 0 7 WD22U 69.00% 25.00% 8.4 - 2014-01- -

24
MPTa2
18:00:00
4) Output average CPU usage of BBP boards and other related information.
Information of TOP BBP Boards with Highest Average CPU Usage

VS.BBUBo VS.BBUBo L.Traffic.B L.Traffic.Boar L.Traffi eNodeB eNodeB
eNode eNodeB SR Board Time(by
CN SN ard.CPULo ard.CPULo oard.CPUL d.UPlane.CPU c.User. Reset Reset
B ID Name N Type hour)
ad.Mean ad.Max oad.AVG Load.MAX Avg Time Type
WD22 2014-01-
5014 T5014 0 0 3 LBBP 71.00% 24.00% 19.00% 4.49 10.21 24 - -
a2 16:00:00
2014-01- 2014-01-
NE
5014 T5014 0 0 3 -- 69.00% 19.00% 5.95 24 24
startup
17:00:00 17:10:00
2014-01-
5014 T5014 0 0 3 -- 69.00% 19.00% 5.95 - 24 -
18:00:00
3.18.3 Principles
1) Get traffic measurement data VS.BBUBoard.CPUload.Mean (Average Board CPU Usage) and VS.BBUBoard.CPUload.Max (Maximum Board
CPU Usage). Based on SN, judge whether it is a MPT board or BBP board. If SN is 1~5, it is BBP board. If SN= 6 or 7, it is MPT board.
2) For every single board, find its TOP1 average CPU usage as a sample point per day and record the occurrence time, then calculate the average
CPU usage of all the sample points during the whole inspection period and take this average data as final average CPU usage for this board.
3) Find boards with average CPU usage >=70% (except they don’t have any reset). If there are more than 10 pieces of board meet this condition,
output all of them. If there are less than 10 pieces, output TOP10 boards with highest average CPU usage. Based on these values, calculate actual
times which average CPU usage rate of each board > 70%.
4) Find specific time’s (recorded in step 2) maximum CPU usage rate, then calculate the average maximum CPU usage of all the sample points
during the whole inspection period and take this average data as final maximum CPU usage for this MPT/BBP board.
5) Find average number of users in all cells under MPT/BBP’s corresponding eNodeB (under specific time recorded in step 2), then add each cell’s
average number of users together and take it as average number of users in this eNodeB, which is MPT/BBP’s average number of users.
6) Find alarm’s occurrence time from Alarm file and set it as eNodeB’s reset time. If specific time recorded in step 2<= eNodeB’s reset time<=

specific time recorded in step 2+1hour, output the reset time.
7) Find alarm’s name from Alarm file and set it as eNodeB’s reset type. If step 6) is satisfied and alarm name is Board Startup or NE Startup, output
the name.
3.18.4 Measures
For the boards whose average CPU usage exceed 70%, please submit iCare for solution.
3.18.5 Reference
None.
3.19 eNodeB Capacity Switch Check
3.19.1 Location

03 Resource Load Analysis 02 eNodeB Capacity Check 01 eNodeB Capacity Switch Check
Basic capacity switches refer to public resource adaptive switches which are recommended to turn on during the operation of the network, in case
of a limited connected user number under some unknown and unexpected big traffic scenario. If some basic capacity switches are disabled, connected user
number will be less than the system specification. In big traffic scenario, it will lead to CPU overload or KPI deterioration if recommended configuration
are not executed. This rule outputs cells’ related information with this risk.
1) Output cells’ related information with this risk.
eNodeB Capacity Switch Check

Set
SriAda PucchA CqiPeri SrsPeri SrsSubfra
eNodeB eNodeB Local Cell Cell SrsSubframeCf PdcchSymNu PA and PB Config
ptiveSw lgoSwit odAdap odAdap meRecfSw
ID Name ID Name g to Default mSwitch (Pa,Pb)
itch ch tive tive itch
Value

cell0 // OFF // OFF // (-3 dB, 1) // (-3 dB,

5048 5048 0 // 1 OFF OFF OFF SC11 // SC10 ON// ON
cell1 OFF OFF 1)
3.19.3 Principles
eNodeB’s capacity switch check:
Check the following parameters’ recommended configuration from LMT.XML file and output eNodeBs’ information if their current network’s
configuration are inconsistent with the recommended value (satisfy any one of the following conditions).
Recommended Value Identification Method

SriAdaptiveSwitch is on. SriAdaptiveSwitch (under GLOBALPROCSWITCH) = 1, or mark it as abnormal.
PucchAlgoSwitch is on. Bit0 of PucchAlgoSwitch (under CellAlgoSwitch = 1, or mark it as abnormal.
CqiPeriodAdaptive is on. CqiPeriodAdaptive (under CqiAdaptiveCfg) =1, or mark it as abnormal.
SrsPeriodAdaptive is on. SrsPeriodAdaptive (under SriAdaptivecfg) =1, or mark it as abnormal.
SrsSubframeRecfSwitch is on. Bit0 of SrsAlgoSwitch (under CellAlgoSwitch) = 1, or mark it as abnormal.
SrsSubframeCfg is SC3. SrsSubframeCfg (under SRSCFG) = 3, or mark it as abnormal.
PdcchSymNumSwitch (High 1) If HighSpeedFlag (under CELL) = 0 (LOW_SPEED), it is considered as non-high speed cell. PdcchSymNumSwitch (under
speed cell is OFF and non-high CELLPDCCHALGO) = 2 in the LTE FDD V100R006C00 version and PdcchSymNumSwitch = 3 in other versions, or mark it as abnormal.
speed cell is 2) If HighSpeedFlag (under CELL) ≠ 0 (HIGH_SPEED~1, ULTRA_HIGH_SPEED~2, EXTRA_HIGH_SPEED~3), it is considered as high
ECFIADAPTIONON). speed cell. PdcchSymNumSwitch (under CELLPDCCHALGO) = 0, or mark it as abnormal.

The value of PA: PaPcOff (under CELLDLPCPDSCHPA) = 4, or mark it as abnormal.
Value of PA and PB is (0dB, 0).
The value of PB: Pb (under PDSCHCfg) 0, or mark it as abnormal.
3.19.4 Measures
Enable basic capacity switches to avoid that connected user number is less than the system specification.
 MOD GLOBALPROCSWITCH: SriAdaptiveSwitch=ON-1.
 MOD CELLALGOSWITCH: LocalCellId=x, PucchAlgoSwitch=PucchSwitch-1.
 MOD CQIADAPTIVECFG: CqiPeriodAdaptive=ON-1.
 MOD CELLALGOSWITCH: LocalCellId=x, SrsAlgoSwitch=SrsSubframeRecfSwitch-1.
 MOD SRSADAPTIVECFG：SrsPeriodAdaptive=ON-1.
 MOD SRSCFG：SrsSubframeCfg=3.
 Modify PDCCH switch under high speed cell: MOD CELLPDCCHALGO: PdcchSymNumSwitch =OFF-0.
 Modify PDCCH switch under high speed cell: MOD CELLPDCCHALGO: PdcchSymNumSwitch=1(ON) in LTE FDD V100R006C00 version
and PdcchSymNumSwitch=ECFIADAPTIONON~2 in other versions.

 The value of PA and PB: MOD CELLDLPCPDSCHPA: LocalCellId=x, PaPcOff=DB0_P_A (Modify the value of Pa), MOD PDSCHCFG:
LocalCellId=x, Pb = 0 (Modify the value of Pb).
3.19.5 Reference
None.
3.20 Check of Uu Interface Resource Congestion
3.20.1 Location

03 Resource Load Analysis 02 eNodeB Capacity Check 02 Check of Uu Interface Resource Congestion
If cell’s maximum or average user number is more than eNodeB’s specification or the limit of the license online users, it will lead to a failure of
radio resource allocation and new users can’t access the network. This rule is mainly used to remind RRC or eRAB setup failure caused by failed radio
resource allocation.
1) Output cells’ related information by hour if RRC congestion rate or eRAB congestion rate is greater than 0.2%.
Radio Resource Congestion Check

RRC
L.RRC. L.E-
eNode Time( L.RRC.C RRC L.E- ERAB L.Traff L.Traff Connected VS.Board
eNod Cell Cell SetupFa RAB.Fail
B by onnReq.A Congesti RAB.A Congestio ic.User. ic.User. User Num .CPUload.
eB ID ID Name il.ResFa Est.NoRa
Name hour) tt on Rate ttEst n Rate Avg Max License Max
il dioRes
Allocated
2014-
11320 EAF2 01-26

1 E1 21 1000 0.21% 21 10000 0.21% 16.73 25 10800 21
7 07 00:00:
00
11320 EAF2 1 E1 2014- 20 1000 0.20% 21 10000 0.21% 15.29 25 10800 19
7 07 01-26

01:00:
00
3.20.3 Principles
1) Get each cell’s L.RRC.SetupFail.ResFail, L.RRC.ConnReq.Att, L.E-RAB.FailEst.NoRadioRes and L.E-RAB.AttEst by hour from traffic
measurement file, and then calculate each cell’s RRC congestion rate and eRAB congestion rate.
 If RRC or eRAB congestion rate is greater than 0.2%, it is considered as radio resource congestion, mark it red and count as abnormal. List
all the abnormal related information and abnormal number is based on cell’s number.
 If RRC and eRAB congestion rate are less than 0.2%, output TOP20 cells’ information with highest RRC and eRAB congestion rate.
2) During the time period corresponding with the selected cells from step 1), check and output the following traffic measurement counters as related
data source:
 L.Traffic.User.Avg;
 L.Traffic.User.MAX;
 VS.Board.CPUload.Max (BBP).
From the result of “DSP cell”, find LocalCellId’s corresponding CN, SRN and SN of BBP board. They can identify which board the cell belongs
to uniquely.
 RRC Connected User License Allocated:
Get the corresponding Allocated value from the result of DSP license’s “RRC Connected User unit”. If there are more than one records, add them
together.
Note: If L.RRC.SetupFail.ResFail or L.E-RAB.FailEst.NoRadioRes >=50, list all the abnormal information. If they are less than 50, list TOP20
cells’ information with highest L.RRC.SetupFail.ResFail and L.E-RAB.FailEst.NoRadioRes.
3) Each counter’s formula:
 RRC congestion rate= L.RRC.SetupFail.ResFail / L.RRC.ConnReq.Att * 100%
 eRAB congestion rate = L.E-RAB.FailEst.NoRadioRes / L.E-RAB.AttEst * 100%
3.20.4 Measures
1) If cell’s maximum or average user number is more than eNodeB specification or the limit of license online users, expand the cell or the license
source.
2) If a cell does not have these two situations, collect MPT and BBP’s one-click log during corresponding time and send them to Huawei engineers

for analysis.
3.20.5 Reference
None.
3.21 User Plane Load Evaluation
3.21.1 Location

03 Resource Load Analysis 03 User Plane Load Evaluation 01 User Plane Load Evaluation
If data service is abnormal or there is capacity risk, it will affect user experience. This rule uses downlink RB usage rate and downlink average
user throughput to check whether this risk is exited.
1) Output threshold setting (Different bandwidth has different throughout rate threshold).
Threshold Setting
User Plane Load 5M Bandwidth DL 10M Bandwidth DL 20M Bandwidth DL User Plane Load PDCCH
Evaluate - DL Average User Average User Average User Evaluate - DL Spectral Resource
Average RB Usage Throughput(Mbps) Throughput(Mbps) Throughput(Mbps) Efficiency(bps/Hz) Usage
Rate Threshold Threshold Threshold Threshold Threshold Rate

70.00% 1 2 4 80.00% 70.00%
2) Output the number of cells having poor user experience or congestion area.
Result of User Plane Load Evaluate

Area Name Cell Number
Poor user experience 0
Congestion 0
3) Output detailed evaluation result and corresponding recommendation of cells with poor user experience or congestion area.
Detailed Evaluation Result of Cells with Poor User Experience or Congestion Area
eNod eNode Loc Cell Downlink DL DL DL DL Full Max L.ChM L.Traffi L.ChM Area Reco
eB ID B al Na Bandwidt Averag Average Spectral RB Traffi eas.PR c.User. eas.CC Partit mmen
Name Cell me h(MHz) e RB User Efficiency Through c User B.DL.U Avg E.Avail ion dation

Usage Throughpu put(Mbps

ID (bits/Hz) sed.Avg
Rate t(Mbps) )
GU
GUA
AN
39372 NGZ 36282 1232458 Norm
2 GZ 20 3.44% 17.19 0.84 16.82 3.44 18.79 None
2 HOU- 2.71 5295 al
HO
H
U-H
4) Output eNodeBs’ information if PDCCH resource usage rate > 70%.
PDCCH Resource Usage Rate > 70%

eNodeB eNodeB PDCCH Resource UL Average DL Average
Local Cell ID Cell Name
ID Name Usage Rate RB Usage Rate RB Usage Rate
5315 y_5315 1 cell1 77.15% 74.28% 80.87%
3.21.3 Principles
“Detailed evaluation result of cells with poor user experience or congestion area” table:
1) Calculate each cell’s DL average PRB usage rate during this inspection period: PRB_Usage_DL =
∑ ( L .ChMeas . PRB . DL . Used . Avg)/ N . N is the times L.ChMeas.PRB.DL.Used.Avg reported during this inspection period.
RB Number of cell' s full wideband
2) Calculate each cell’s DL average user throughout during this inspection period: User_Throughput_DL = sum (L.Thrp.bits.DL)/ sum
(L.Thrp.Time.DL) /1000.
3) Calculate each cell’s DL spectral efficiency during this inspection period: L.Thrp.bits.DL / (Report_Period * 60) / 1000000 /
(L.ChMeas.PRB.DL.Used.Avg / (DL_BANDWITH * 5)) / DL_BANDWITH.
4) Based on PRB_Usage_DL and User_Throughput_DL, place this cell into a certain area.
a) Normal: PRB_Usage_DL < RB usage rate threshold and User_Throughput_DL > User throughout threshold.
b) Overload: PRB_Usage_DL > RB usage rate threshold and User_Throughput_DL > User throughout threshold.
c) Poor user experience: PRB_Usage_DL < RB usage rate threshold & User_Throughput_DL < User throughout threshold and each cell’s
Max Traffic User per day >100 (Recommendation: Need further analysis. Please submit iCare).
d) Congestion: PRB_Usage_DL > RB usage rate threshold and User_Throughput_DL < User throughout threshold. Judge whether DL full RB

throughout rate =
∑ ( L .Thrp . bits . DL)∗RB Number of cell ' s full wideband is lower than full RB throughout
L. ChMeas . PRB . D L .Used . Avg∗Seconds of the whole inspection period
threshold. (If yes, need further analysis and please submit icare. If not, expand capacity）.
e) Unknown: one of PRB_Usage_DL and User_Throughput_DL or both of them are none (Recommendation: please confirm the integrity of
the original data).
5) Mark cells with poor user experience area or congestion area as abnormal and output their related information. Or output TOP10 cells’
information with highest DL average PRB usage rate.
“PDCCH resource usage rate > 70%” table:
1) If PDCCH resource usage rate > 70%, it is considered as abnormal, mark it red and output corresponding cells’ information.
PDCCH resource usage rate = (L.ChMeas.CCE.CommUsed + L.ChMeas.CCE.ULUsed + L.ChMeas.CCE.DLUsed) / L.ChMeas.CCE.Avail
*100%
Note: RB usage rate is 70% by default and it is configurable. 5M Bandwidth DL average user throughput (Mbps) Threshold is 1. 10M Bandwidth
DL average user throughput (Mbps) Threshold is 2. 20M Bandwidth DL average user throughput (Mbps) Threshold is 4. DL Spectral efficiency (bps/Hz)
Threshold is 80% by default and it is configurable. Formula of full RB throughput threshold: Spectral efficiency*Bandwidth of a cell (Spectral efficiency is
1 by default and it is configurable).
3.21.4 Measures
1) Recommendations for cells with poor user experience are 1) Check the number of users, MCS, interference and other KPI; 2) Drive test.
2) For congestion cells that downlink full RB throughput is lower than the threshold, submit icare. If it is larger than the threshold, expand capacity.
3.21.5 Reference
None.
3.22 Paging Performance Analysis
3.22.1 Location

03 Resource Load Analysis 05 Paging Performance Analysis 01 Paging Performance Analysis
It will affect paging service if there is a risk existed when processing paging message. If L.Paging.UU.Att/ L.Paging.S1.Rx <
PagingSentNum*0.85 for consecutive 6 hours or above in one cell, it is considered as abnormal paging performance. This rule is mainly used to collect
cells’ information with abnormal paging performance.
1) Output cells’ related information with abnormal paging performance.
Result of Paging Performance Analysis

eNode eNodeB Local L.Paging.UU. L.Paging. Ratio of L.Paging.UU.Att
Time(hour)
B ID Name Cell ID Att S1.Rx to L.Paging.S1.Rx
2012-01-12 Mall-
12584 1 10 30 0.33
12:00:00 Falcon
3.22.3 Principles
Monitor each cell’s paging performance data (L.Paging.UU.Att/ L.Paging.S1.Rx) by hour. If one cell’s L.Paging.UU.Att/ L.Paging.S1.Rx <
PagingSentNum*0.85 for consecutive 6 hours or above, it is considered as abnormal paging performance (L.Paging.UU.Att is Number of UEs contained in
paging messages transmitted over the Uu interface in a cell and L.Paging.S1.Rx is Number of received paging messages over the S1 interface in a cell).
Note: PagingSentNum is the number of paging message sent from the users and its value is between 1~3)
3.22.4 Measures
1) Specify symptoms of paging failures and confirm whether this problem occurs on the entire network or in top TALs/TACs.
2) Confirm paging scenario.
3) Confirm paging KPI trend.
3.22.5 Reference
None.

3.23 RRC Setup Success Rate
3.23.1 Location

04 KPI Performance Analysis 01 Access Performance 01 RRC Setup Success Rate
Abnormal RRC setup success rate will affect user’s experience. Collect the entire network’s RRC setup success rate information by day and
judge whether the exception is caused by TOP cell or not.
1) Output the entire network’s RRC setup success rate and related KPI by day.
RRC Setup Success Rate

Time(b RRC Setup L.RRC.Co Number of RRC RRC Setup Succ L.RRC.Conn RRC Setup Succ L.RRC.ConnReq.Att
y day) Succ Rate nnReq.Att Connection Setup Fails Rate (Emc) Req.Att.Emc Rate (HighPri) .HighPri
2012-
99.66% 5170489 17758 66.67% 3 - 0
12-14
2) Output TOPN cells’ information with lowest RRC setup success rate (<=85%).
TOPN Cells with Lowest RRC Setup Success Rate (<=85%)

Time(b eNode eNodeB Local Cell RRC Setup L.RRC.Co Number of RRC
y day) B ID Name Cell ID Name Succ Rate nnReq.Att Connection Setup Fails
2012- 23045 23045
230459 0 74.13% 5802 1501
12-14 9 91
3) Output TOP10 cells’ information with lowest RRC setup success rate (>85%) by day.
TOP10 Cells with Lowest RRC Setup Success Rate (>85%)

Time(b eNode eNodeB Local Cell RRC Setup L.RRC.Co Number of RRC
y day) B ID Name Cell ID Name Succ Rate nnReq.Att Connection Setup Fails
2012- 23045 23045
230459 0 89.43% 5837 617
12-16 9 91
4) Output TOP10 cells’ information with abnormal number of RRC connection setup fails by day.
TOP10 Cells with Abnormal Number of RRC Connection Setup Fails

Time(b eNodeB eNodeB Local Cell RRC Setup L.RRC.Co Number of RRC
y day) ID Name Cell ID Name Succ Rate nnReq.Att Connection Setup Fails

2012- 23019
230191 230191 4 78.10% 7243 1586
12-14 15
5) Output TOP10 cells’ information with lowest S1 interface setup success rate by day.
TOP10 Cells with Lowest S1 Interface Setup Success Rate

Time(b eNodeB eNodeB Local Cell S1 Interface RRC Setup L.RRC.Con
y day) ID Name Cell ID Name Setup Succ Rate Succ Rate nReq.Att
2014- EAJ1
116144 EAJ144 2 98.80% 100.00% 83
01-26 442
3.23.3 Principles
Use the original traffic measurement data from the first report to summarize each cell’s L.RRC.ConnReq.Att & L.RRC.ConnReq.Succ and then
calculate each cell’s RRC setup success rate during the inspection time.
1) RRC setup success rate (by day):
a) Get the entire network’s traffic measurement by adding the original data together.
b) Then calculate RRC setup success rate.
c) Output summarized traffic measurement data chronologically.
For TOP cells:
a) Don’t consider the data when L.RRC.ConnReq.Att is none or less than 100.
b) For the rest of cells, get RRC setup success rate by day.
2) TOPN cells with lowest RRC setup success rate by day (<= 85%):
a) Output TOPN cells’ information with lowest RRC setup success rate (<=85%) as an ascending order.
3) TOP10 cells with lowest RRC setup success rate by day (> 85%):
a) Find out TOP10 cells with lowest RRC setup success rate (>85%) as an ascending order.
b) Calculate the average RRC setup success rate of these TOP10 cells according to eNodeB ID separately (Total Number of RRC Connection
Setup Succeeds in a Cell/ Total Number of RRC Connection Setup Requests in a Cell).
c) Sort eNodeBs by its average RRC setup success rate as an ascending order. Cells under each eNodeB are sorted by their local cell ID.
d) Sort the data chronologically.
4) TOP10 cells with abnormal number of RRC connection setup fails by day:
a) Find out TOP10 cells with most number of RRC connection setup fails (RRC setup success rate <=98%) as a descending order.
b) Calculate the average number of RRC connection setup fails of these TOP10 cells according to eNodeB ID separately.

c) Sort eNodeBs by its average number of RRC connection setup fails as a descending order. Cells under each eNodeB are sorted by their local
cell ID.
5) TOP10 cells with lowest S1 interface setup success rate by day:
a) Calculate each cell’s S1 interface setup success rate during the inspection time by day.
b) Find out TOP10 cells with lowest RRC setup success rate as an ascending order.
c) Calculate the average RRC setup success rate of these TOP10 cells according to eNodeB ID separately (Total Number of RRC Connection
Setup Succeeds in a Cell/ Total Number of RRC Connection Setup Requests in a Cell).
d) Sort eNodeBs by its average RRC setup success rate as an ascending order. Cells under each eNodeB are sorted by their local cell ID.
e) Sort the data chronologically.
Note: If RRC setup success rate < THRESHOLD NOK RRC Setup Succ Rate, mark it red. The default threshold is 85% and configurable.
 RRC setup success rate = L.RRC.ConnReq.Succ / L.RRC.ConnReq.Att
 Number of RRC Connection Setup Fails = L.RRC.ConnReq.Att - L.RRC.ConnReq.Succ
 RRC setup success rate(Emc) = L.RRC.ConnReq.Succ.Emc / L.RRC.ConnReq.Att.Emc
 RRC setup success rate(HighPri) = L.RRC.ConnReq.Succ.HighPri / L.RRC.ConnReq.Att.HighPri
 RRC setup success rate(Mt) = L.RRC.ConnReq.Succ.Mt / L.RRC.ConnReq.Att.Mt
 RRC setup success rate(MoSig) = L.RRC.ConnReq.Succ.MoSig / L.RRC.ConnReq.Att.MoSig
 RRC setup success rate(MoData) = L.RRC.ConnReq.Succ.MoData / L.RRC.ConnReq.Att.MoData
 S1 interface setup success rate = S1Sig.ConnEst.Succ / S1Sig.ConnEst.Att
3.23.4 Measures
1) Identify whether this problem belongs to TOP cells or the entire network.
2) If it is under MOCN scenario, confirm whether this problem belongs to single operator or multi-operators by sub-operator's traffic measurement.
3) Analyze the major reasons of access failures and come up with priority actions.
4) Submit the sleeping cell problem to R&D directly.
3.23.5 Reference
None.

3.24 eRAB Setup Success Rate
3.24.1 Location

04 KPI Performance Analysis 01 Access Performance 02 eRAB Setup Success Rate
Abnormal eRAB setup success rate will affect the user experience seriously. Collect information of eRAB setup success rate in the entire
network by day and judge whether the exception is caused by TOP cells or not.
1) Output eRAB setup success rate and related KPI by day.
eRAB Setup Success Rate

L.E- L.E- L.E- L.E- L.E-
Time(by eRAB Setup Number of eRAB
RAB.Att RAB.FailEst. RAB.FailEst. RAB.FailEs RAB.FailEs
day) Succ Rate Setup Fails
Est NoReply MME t.TNL t.RNL
2014-01-
99.98% 36423154 7938 1 5155 1011 417
26
2) Output TOPN cells with lowest eRAB setup success rate by day (<=85%).
TOPN Cells with Lowest eRAB Setup Success Rate (<=85%)

Time(by eNodeB eNodeB Local Cell eRAB Setup L.E- Number of eRAB
day) ID Name Cell ID Name Succ Rate RAB.AttEst Setup Fails

2012-12- 23013
230135 230135 0 0.00% 2400 2400
14 51
3) Output TOP10 cells with lowest eRAB setup success rate (>85%).
TOP10 Cells with Lowest eRAB Setup Success Rate (>85%)

Time(by eNodeB eNodeB Local Cell eRAB Setup L.E- Number of eRAB
day) ID Name Cell ID Name Succ Rate RAB.AttEst Setup Fails

2012-12- 23013
230135 230135 5 86.00% 2400 336
14 56
4) Output TOP10 cells’ information with abnormal number of eRAB setup fails by day.
TOP10 Cells with Abnormal Number of eRAB Setup Fails

Time(by eNode eNodeB Local Cell eRAB Setup L.E- Number of eRAB

RAB.AttE
day) B ID Name Cell ID Name Succ Rate Setup Fails
st
2012-12- 230135
230135 230135 0 0.00% 2400 2400
14 1
Note: The above tables only list parts of the KPI counters.
1.46.3 Principles
Use the original traffic measurement date from the first report to summarize each cell’s L.E-RAB.AttEst & L.E-RAB.SuccEst and then calculate
each cell’s eRAB setup success rate during the inspection time.
1) eRAB setup success rate(by day):
b) Then calculate eRAB setup success rate by day.
c) Output summarized traffic statistic data chronologically.
For TOP cells:
a) Don’t consider the data when L.E-RAB.AttEst is none or less than 100.
b) For the rest of cells, get eRAB setup success rate by day.
2) TOPN cells with lowest eRAB setup success rate (<=85%):
a) Output TOPN cells’ information with lowest eRAB setup success rate (<=85%) as an ascending order.
3) TOP10 cells with lowest eRAB setup success rate (>85%) by day:
a) Find out TOP10 cells with lowest eRAB setup success rate (>85%) as an ascending order.
b) Calculate the average eRAB setup success rate of these TOP10 cells according to eNodeB ID separately (Total Number of eRAB
Connection Setup Succeeds in a Cell/ Total Number of eRAB Connection Setup Requests in a Cell).
c) Sort eNodeBs by its average eRAB setup success rate as an ascending order. Cells under each eNodeB are sorted by their local cell ID.
4) TOP10 cells with abnormal number of eRAB setup fails by day:
a) Find out TOP10 cells with most number of eRAB setup fails (eRAB setup success rate <=98%) as a descending order.
b) Calculate the average number of eRAB setup fails of these TOP10 cells according to eNodeB ID separately.
c) Sort eNodeBs by its average number of eRAB setup fails as a descending order. Cells under each eNodeB are sorted by their local cell ID.

 Number of eRAB Setup Fails = L.E-RAB.AttEst - L.E-RAB. SuccEst
 eRAB setup success rate = L.E-RAB. SuccEst / L.E-RAB.AttEst
Note: If eRAB setup success rate is lower than THRESHOLD NOK eRAB Setup Succ Rate, mark it red. The default value of the threshold is
85% and configurable.
1.46.4 Measures
1) Identify whether the handover problem is a common issue among multiple operators or just for one specific operator, and then analyze further.
2) If the problem is just for one specific operator, you need to filter the operator’s traffic measurement. In actual situations, confirm whether the
problem belongs to TOP cells or the entire network.
3) Preliminary analysis of handover failure based on traffic measurement.
1.46.5 Reference
None.
1.29 Call Drop Rate
1.29.1 Location

04 KPI Performance Analysis 02 Keep Ability 01 Call Drop Rate
Call drop rate is normal in the entire network and only small cells have serious call drop rate. High call drop rate in the TOPN cells caused by
eRAB abnormal release times due to handover failure will affect the user experience seriously. Collect information of the entire network’s call drop rate
and find out TOP10 cells with highest call drop rate by day.
1) Collect information of the entire network’s call drop rate by day, confirm whether the problem belongs to TOP cells or the entire network and
output call drop rate related KPI.
Call Drop Rate

Time(by Call Drop VOIP Call L.E- eRAB Total Actual Call L.E-
day) Rate Drop Rate RAB.Abno Release Times Drop Rate RAB.Abnorm

rmRel Rel.MME
2012/12/14 0.79% 50.00% 36123 4570896 0.80% 547
2) Output TOPN cells with highest call drop rate (>=3%).
TOPN Cells with Highest Call Drop Rate (>=3%)

L.E-
Time(by eNodeB eNodeB Local Cell Call Drop VOIP Call eRAB Total Actual Call
RAB.Abno
day) ID Name Cell ID Name Rate Drop Rate Release Times Drop Rate
rmRel
2012-12-16 230461 230461 1 2304612 8.76% 50.00% 46 525 8.76%
3) Output TOP10 cells with highest call drop rate (<3%).
TOP10 Cells with Highest Call Drop Rate (<3%)

L.E-
RAB.Abno
rmRel
2012-12-17 231122 231122 1 231122 2.95% - 12 407 2.95%
4) Output TOP10 cells with abnormal eRAB total release times by day.
TOP10 Cells with Abnormal eRAB Total Release Times

L.E-
RAB.Abno
rmRel
2012-12-16 230110 230110 1 230110 3.04% 50% 356 11712 3.04%
Note: The above tables only list parts of the counters.
1.29.3 Principles
Use the original traffic measurement data from the first report to get each cell’s L.E-RAB.AbnormRel & eRAB Total Release Times during the
inspection time.
1) Call drop rate (by day):
b) Then calculate call drop rate by day.
d) Calculate VOIP call drop rate by day.
For TOP cells:
a) Don’t consider the data when call drop rate is None, L.E-RAB.AbnormRel is less than 100 and (L.E-RAB.AbnormRel + L.E-

RAB.NormRel) <100.
b) For the rest of cells, get call drop rate, actual call drop rate and VOIP call drop rate by day.
2) TOPN cells with highest call drop rate (>=3%):
a) Output TOPN cells’ information with highest call drop rate (>=3%) as a descending order.
3) TOP10 cells with highest call drop rate (<3%):
a) Output TOP10 cells’ information with highest call drop rate (<3%) as a descending order.
b) Calculate the average call drop rate of these TOP10 cells according to eNodeB ID separately (L.E-RAB.AbnormRel / eRAB Total Release
Times).
c) Sort eNodeBs by its average call drop rate as a descending order. Cells under each eNodeB are sorted by their local cell ID.
4) TOP10 cells with highest abnormal L.E-RAB.AbnormRel:
a) Find out TOP10 cells with highest L.E-RAB.AbnormRel (Call drop rate > 2%) as a descending order.
b) Calculate the average L.E-RAB.AbnormRel of these TOP10 cells according to eNodeB ID separately.
c) Sort eNodeBs by its average L.E-RAB.AbnormRel as a descending order. Cells under each eNodeB are sorted by their local cell ID.
Note: If call drop rate > THRESHOLD NOK Call drop rate Setup Succ Rate, mark it red. The default threshold is 2% and configurable. For
TOP10 tables, the default value is 3% and configurable.
 eRAB Total Release Times = L.E-RAB.AbnormRel + L.E-RAB.NormRel
 Call drop rate = L.E-RAB. AbnormRel / (L.E-RAB.AbnormRel+L.E-RAB.NormRel)*100
 Actual call drop rate = [(L.E-RAB. AbnormRel+ L.E-RAB. AbnormRel.MME) / (L.E-RAB.AbnormRel+L.E-RAB.NormRel)]*100
 VOIP call drop rate = (L.E-RAB.AbnormRel.QCI.1) /(L.E-RAB.AbnormRel.QCI.1 + L.E-RAB.NormRel.QCI.1)*100
1.29.4 Measures
1) Check whether the eNodeB is lack of neighboring cells configuration or not.
2) Confirm whether the PCI value of the handover target cell is the same as the PCI Mod3 value of the serving cell or whether the PCI reuse
distance is too short.
3) If it is not cleared, collect the CHR log information from the eNodeB to Huawei engineer for troubleshooting.

1.29.5 Reference
None.
1.30 Intra-eNB Handover Success Rate
1.30.1 Location

04 KPI Performance Analysis 03 Handover Performance 01 Intra-eNB Handover Success Rate
Low handover success rate may cause call dropping, and affect users’ experience. Collect information of intra-eNB hoin success rate, find out
TOP10 cells with lowest intra-eNB hoin execute success rate and TOP10 cells with lowest intra-eNB hoin prepare success rate by day.
1) Output intra-eNB hoin success rate related information by day.
Intra-eNB Hoin Success Rate

Intra- L.HHO. L.HHO. Intra-
Time L.HHO.Int L.HHO.Pre L.HHO.Pre L.HHO.Pre L.HHO.P L.HHO.Prep. Data
eNB Hoin IntraeN IntraeN eNB Hoin
(by raeNB.Prep p.FailIn.Ad p.FailIn.H pAttIn.disc. rep.FailIn FailIn.Admit Comple
Execute B.Exec B.Exec Prepare
day) AttIn mitFail OCancel FlowCtrl .FlowCtrl Fail.Load teness
Succ Rate SuccIn AttIn Succ Rate
2014- 14
93.85% 351 374 100.00% 374 24 0 0 0 0
01-24 Hours
2014-
94.93% 6012 6333 100.00% 6333 44 1 0 0 0 All Day
01-25
2) Output TOP10 cells’ information with lowest intra-eNB hoin execute success rate by day.
TOP10 Cells with Lowest Intra-eNB Hoin Execute Success Rate

Intra- Intra-
L.HHO. L.HHO. L.HHO. L.HHO.P L.HHO. L.HHO.P
Time Local eNB Hoin eNB Hoin Data
eNode eNodeB Cell IntraeN Prep.Fa Prep.Fa repAttIn. Prep.Fa rep.FailIn
(by Cell Execute Execute Comple
B ID Name Name B.Exec ilIn.Ad ilIn.HO disc.Flow ilIn.Flo .AdmitFa
day) ID Success Fail teness
AttIn mitFail Cancel Ctrl wCtrl il.Load
Rate Times
2014- LTE_NetCa
5315 1 cell1 86.45% 155 21 0 0 0 0 0 2 Hours
01-24 pacity_5315
2014- LTE_NetCa 24
5315 1 cell1 94.18% 5499 320 18 1 0 0 0
01-25 pacity_5315 Hours
3) Output TOP10 cells’ information with lowest intra-eNB hoin prepare success rate by day.

TOP10 Cells with Lowest Intra-eNB Hoin Prepare Success Rate

Intra- L.HHO.
Intra- L.HHO. L.HHO. L.HHO. L.HHO.P L.HHO.
Local eNB Hoin Prep.Fa
Time(b eNode eNodeB Cell eNB Hoin IntraeN Prep.Fa Prep.Fa repAttIn. Prep.Fa Data
Cell Prepare ilIn.Ad
y day) B ID Name Name Prepare B.Prep ilIn.Ad ilIn.HO disc.Flow ilIn.Flo Completeness
ID Fail mitFail.
Succ Rate AttIn mitFail Cancel Ctrl wCtrl
Times Load
YLWHP_
001_WR_ YLW
2015- 33331 24
HoPuiVen 21 HPL2 99.61% 4602 18 0 0 0 0 0
10-31 7 Hours
tBdg_A_L 2
TE
YLWHP_
001_WR_ YLW
2015- 33331
HoPuiVen 21 HPL2 99.21% 4535 36 0 0 0 0 0 24Hours
10-30 7
tBdg_A_L 2
TE
1.30.3 Principles
Use the original traffic measurement data from the first report to get each cell’s L.HHO.IntraeNB.PrepAttIn, L.HHO.IntraeNB.ExecAttIn and
L.HHO.IntraeNB.ExecSuccIn during the inspection time.
1) Intra-eNB hoin execute success rate by day:
b) Then calculate intra-eNB hoin execute success rate and intra-eNB hoin prepare success rate by day.
For TOP cells:
a) Don’t consider the data when L.HHO.IntraeNB.ExecAttIn is 0 and TOP1% cells with lowest L.HHO.IntraeNB.ExecAttIn (If 1% of the
cell’s number is less than one, take this data into consideration).
b) For the rest of cells, get intra-eNB hoin execute success rate by day.
2) TOP10 cells with lowest intra-eNB hoin execute success rate :
a) Find out TOP10 cells with lowest intra-eNB hoin execute success rate as an ascending order.
b) Calculate the average intra-eNB hoin execute success rate of these TOP10 cells according to eNodeB ID separately (Total Success Times /
Total Execute Times).
c) Sort eNodeBs by its average intra-eNB hoin execute success rate as an ascending order. Cells under each eNodeB are sorted by their local
cell ID.

3) TOP10 cells with lowest intra-eNB hoin prepare success rate:
a) Output TOP10 cells with lowest intra-eNB hoin prepare success rate as an ascending order.
b) Calculate the average intra-eNB hoin prepare success rate of these TOP10 cells according to eNodeB ID separately (Total Execute Times /
Total Prepare Times).
c) Sort eNodeBs by its average intra-eNB hoin prepare success rate as an ascending order. Cells under each eNodeB are sorted by their local
cell ID.
Note: For these three tables, if intra-eNB hoin execute success rate and intra-eNB hoin prepare success rate < THRESHOLD NOK RRC Setup
Succ Rate, mark it red. The default threshold is 98% and configurable.
 Intra-eNB hoin execute fail times = L.HHO.IntraeNB.ExecAttIn – L.HHO.IntraeNB.ExecSuccIn
 Intra-eNB hoin prepare fail times = L.HHO.IntraeNB.PrepAttIn – L.HHO.IntraeNB.ExecAttIn
 Intra-eNB hoin execute success rate = L.HHO.IntraeNB.ExecSuccIn / L.HHO.IntraeNB.ExecAttIn
 Intra-eNB hoin prepare success rate = L.HHO.IntraeNB.ExecAttIn / L.HHO.IntraeNB.PrepAttIn
1.30.4 Measures
2) If the problem is just for one specific operator, it is necessary to filter the operator’s traffic measurement. In actual situations, confirm whether
the problem belongs to the TOP cells or the entire network.
1.30.5 Reference
None.
1.31 Inter-eNB Handover Success Rate
1.31.1 Location

04 KPI Performance Analysis 03 Handover Performance 02 Inter-eNB Handover Success Rate
Low handover success rate may cause call dropping, and affect users’ experience. Collect information of inter-eNB hoin success rate, find out
TOP10 cells with lowest inter-eNB hoin execute success rate and TOP10 cells with lowest inter-eNB hoin prepare success rate by day.
1) Output inter-eNB hoin success rate related information by day.
Inter-eNB Hoin Success Rate

Inter- L.HHO.I L.HHO. Inter-eNB L.HHO. L.HHO. L.HHO.P L.HHO.P L.HHO. L.HHO.P
Data
Time(b eNB Hoin ntereNB. IntereN Hoin IntereN Prep.Fa rep.FailIn repAttIn. Prep.Fa rep.FailIn
Comple
y day) Execute ExecSucc B.Exec Prepare B.Prep ilIn.Ad .HOCanc disc.Flow ilIn.Flo .AdmitFa
teness
Succ Rate In AttIn Succ Rate AttIn mitFail el Ctrl wCtrl il.Load
2014-
99.21% 37206 37502 99.87% 37549 44 1 0 0 0 All Day
01-25
2014-
85.27% 26623 31222 97.92% 31884 559 0 0 103 0 All Day
01-26
2014- 10
94.97% 7443 7837 99.96% 7840 3 0 0 0 0
01-27 Hours
2) Output TOP10 cells’ information with lowest inter-eNB hoin execute success rate by day.
TOP10 Cells with Lowest Inter-eNB Hoin Execute Success Rate

Lo
Inter-eNB
ca L.HHO. Inter-eNB L.HHO. L.HHO. L.HHO.P L.HHO. L.HHO.P
Hoin Data
Time(b eNode eNodeB l Cell IntereN Hoin Prep.Fa Prep.Fa repAttIn. Prep.Fa rep.FailIn
Execute Comple
y day) B ID Name Ce Name B.Exec Execute ilIn.Ad ilIn.HO disc.Flow ilIn.Flo .AdmitFa
Succ teness
ll AttIn Fail Times mitFail Cancel Ctrl wCtrl il.Load
Rate
ID
2014- LTE_NetCa 24
5315 1 cell1 89.00% 509 56 18 1 0 0 0
2014- LTE_NetCa cell80 24
5313 1 70.61% 7295 2144 127 0 0 0 0
01-26 pacity_5313 0 Hours
2014- LTE_NetCa 24
5314 1 1 73.52% 8640 2288 107 0 0 0 0
3) Output TOP10 cells’ information with lowest inter-eNB hoin prepare success rate by day.
TOP10 Cells with Lowest Inter-eNB Hoin Prepare Success Rate

Inter- L.HHO. Inter-eNB L.HHO.P L.HHO.P L.HHO.P L.HHO. L.HHO.P
Local Data
Time(b eNode eNodeB Cell eNB Hoin IntereN Hoin rep.FailIn rep.FailIn repAttIn. Prep.Fa rep.FailIn
Cell Comple
y day) B ID Name Name Prepare B.Prep Prepare .AdmitFa .HOCanc disc.Flow ilIn.Flo .AdmitFa
ID teness
Succ Rate AttIn Fail Times il el Ctrl wCtrl il.Load
2014- 5014 TMO- 0 KY50 91.79% 195 16 16 0 0 0 0 14

14_Bo
nn-
01-24 5014 Testan Hours
lage-
35
LTE_Ne
2014- 24
5315 tCapacit 1 cell1 96.22% 529 20 18 1 0 0 0
01-25 Hours
y_5315
1.31.3 Principles
Use the original traffic measurement data from the first report to get each cell’s .HHO.IntereNB.PrepAttIn, .HHO.IntereNB.ExecAttIn and
L.HHO.IntereNB.ExecSuccIn and then calculate each cell’s inter-eNB hoin execute success rate and inter-eNB hoin prepare success rate during the
inspection time.
1) Inter-eNB hoin execute success rate by day:
b) Then calculate inter-eNB hoin execute success rate and inter-eNB hoin prepare success rate by day.
For TOP cells:
a) Don’t consider the data when L.HHO.IntereNB.ExecAttIn is 0 and TOP1% cells with lowest L.HHO.IntereNB.ExecAttIn (If 1% of the
b) For the rest of cells, get inter-eNB hoin execute success rate by day.
2) TOP10 cells with lowest inter-eNB hoin execute success rate :
a) Find out TOP10 cells with lowest inter-eNB hoin execute success rate as an ascending order.
b) Calculate the average inter-eNB hoin execute success rate of these TOP10 cells according to eNodeB ID separately (Total Success Times /
c) Sort eNodeBs by its average inter-eNB hoin execute success rate as an ascending order. Cells under each eNodeB are sorted by their local
cell ID.
3) TOP10 cells with lowest inter-eNB hoin prepare success rate:
a) Output TOP10 cells with lowest inter-eNB hoin prepare success rate as an ascending order.
b) Calculate the average inter-eNB hoin prepare success rate of these TOP10 cells according to eNodeB ID separately (Total Execute Times /

c) Sort eNodeBs by its average inter-eNB hoin prepare success rate as an ascending order. Cells under each eNodeB are sorted by their local
cell ID.
Note: For these three tables, if inter-eNB hoin execute success rate and inter-eNB hoin prepare success rate < THRESHOLD NOK RRC Setup
Succ Rate, mark it red. The default threshold is 98% and configurable.
Each counter’s formula:
 Inter-eNB hoin execute fail times = L.HHO.IntereNB.ExecAttIn - L.HHO.IntereNB.ExecSuccIn
 Inter-eNB hoin prepare fail times = L.HHO.IntereNB.PrepAttIn - L.HHO.IntereNB.ExecAttIn
 Inter-eNB hoin execute success rate = L.HHO.IntereNB.ExecSuccIn / L.HHO.IntereNB.ExecAttIn
 Inter-eNB hoin prepare success rate = L.HHO.IntereNB.ExecAttIn / L.HHO.IntereNB.PrepAttIn
1.31.4 Measures
the problem belongs to TOP cells or the entire network.
1.31.5 Reference
None.
3.25 Inter-RAT Handover Success Rate
3.25.1 Location

04 KPI Performance Analysis 03 Handover Performance 03 Inter-RAT Handover Success Rate
Low inter-RAT handover success rate may cause call dropping, and affect users’ experience. Collect information of inter-RAT hoout success rate

and find out TOP10 cells with lowest E2W hoout execute success rate, lowest E2G hoout execute success rate and lowest E2C hoout execute success rate
by day.
1) Output inter-RAT hoout success rate related information by day.
Inter-RAT Hoout Success Rate

L.IRATHO. L.IRATHO. E2W Ho L.IRATHO L.IRATHO E2G Ho L.IRATHO L.IRATHO E2C Ho Data
Time(by
E2W.ExecSu E2W.ExecAtt Execute .E2G.ExecS .E2G.Exec Execute .E2C.ExecS .E2C.Exec Execute Comple
day)
ccOut Out Succ Rate uccOut AttOut Succ Rate uccOut AttOut Succ Rate teness
2014-01-26 0 0 - 0 0 - 0 0 - All Day
2) Output TOP10 cells’ information with lowest E2W hoout execute success rate by day.
TOP10 Cells with Lowest E2W Hoout Execute Success Rate

Time(by eNodeB eNodeB Local Cell E2W Ho Execute L.IRATHO.E2W L.IRATHO.E2 Data
day) ID Name Cell ID Name Succ Rate .ExecSuccOut W.ExecAttOut Completeness

2012-12-14 230013 230013 0 2300131 90.00% 21600 24000 24 Hours
3) Output TOP10 cells’ information with lowest E2G hoout execute success rate by day.
TOP10 Cells with Lowest E2G Hoout Execute Success Rate

Time(by eNode eNodeB Local Cell E2G Ho Execute L.IRATHO.E2G. L.IRATHO.E2 Data
day) B ID Name Cell ID Name Succ Rate ExecSuccOut G.ExecAttOut Completeness

2012-12-14 230013 230013 0 2300131 90.00% 21600 24000 24 Hours
4) Output TOP10 cells’ information with lowest E2C hoout execute success rate by day.
TOP10 Cells with Lowest E2C Hoout Execute Success Rate

Time(by eNode eNodeB Local Cell E2C Ho Execute L.IRATHO.E2C. L.IRATHO.E2C. Data
day) B ID Name Cell ID Name Succ Rate ExecSuccOut ExecAttOut Completeness

2012-12-14 230013 230013 0 2300131 90% 900 1000 24 Hours
3.25.3 Principles
Use the original traffic measurement data from the first report to get each cell’s L.IRATHO.E2W.ExecSuccOut, L.IRATHO.E2W.ExecAttOut,
L.IRATHO.E2G.ExecSuccOut, L.IRATHO.E2G.ExecAttOut, L.IRATHO.E2C.ExecSuccOut and L.IRATHO.E2C.ExecAttOut during the inspection time.
1) Inter-RAT hoout success rate (by day):
b) Calculate E2W hoout execute success rate, E2G hoout execute success rate and E2C hoout execute success rate by day.
2) TOP10 cells with lowest E2W hoout execute success rate by day.

a) Don’t consider the data when L.IRATHO.E2W.ExecAttOut is 0 and TOP1% cells with lowest L.IRATHO.E2W.ExecAttOut (If 1% of the
b) For the rest of cells, get E2W hoout execute success rate by day.
c) Find out TOP10 cells with lowest E2W hoout execute success rate as an ascending order.
d) Calculate the average E2W hoout execute success rate of these TOP10 cells according to eNodeB ID separately (Total Success Times /
e) Sort eNodeBs by its average E2W hoout execute success rate as an ascending order. Cells under each eNodeB are sorted by their local cell
ID.
f) Sort the data chronologically.
3) TOP10 cells with lowest E2G hoout execute success rate by day.
a) Don’t consider the data when L.IRATHO.E2G.ExecAttOut is 0 and TOP1% cells with lowest L.IRATHO.E2G.ExecAttOut (If 1% of the
b) For the rest of cells, get E2G hoout execute success rate by day.
c) Find out TOP10 cells with lowest E2G hoout execute success rate as an ascending order.
d) Calculate the average E2G hoout execute success rate of these TOP10 cells according to eNodeB ID separately (Total Success Times / Total
Execute Times).
e) Sort eNodeBs by its average E2G hoout execute success rate as an ascending order. Cells under each eNodeB are sorted by their local cell
ID.
4) TOP10 cells with lowest E2C hoout execute success rate by day.
a) Don’t consider the data when L.IRATHO.E2C.ExecAttOut is 0 and TOP1% cells with lowest L.IRATHO.E2C.ExecAttOut (If 1% of the
b) For the rest of cells, get E2C hoout execute success rate by day.
c) Find out TOP10 cells with lowest E2C hoout execute success rate as an ascending order.
d) Calculate the average E2C hoout execute success rate of these TOP10 cells according to eNodeB ID separately (Total Success Times / Total
Execute Times).
e) Sort eNodeBs by its average E2C hoout execute success rate as an ascending order. Cells under each eNodeB are sorted by their local cell
ID.

Note: For these four tables, if E2W/E2G/E2C hoout execute success rate < THRESHOLD NOK RRC Setup Succ Rate, mark it red. The default
threshold is 98% and configurable.
 E2W hoout execute success rate = L.IRATHO.E2W.ExecSuccOut/ L.IRATHO.E2W.ExecAttOut*100%
 E2G hoout execute success rate = L.IRATHO.E2G.ExecSuccOut/ L.IRATHO.E2G.ExecAttOut*100%
 E2C hoout execute success rate = L.IRATHO.E2C.ExecSuccOut/ L.IRATHO.E2C.ExecAttOut*100%
3.25.4 Measures
the problem belongs to TOP cells or the entire network.
3.25.5 Reference
None.
3.26 Intra-Freq Handover Success Rate
3.26.1 Location

04 KPI Performance Analysis 03 Handover Performance 04 Intra-Freq Handover Success Rate
If the handover success rate is lower than 98%, it will lead to call dropping when users are moving, which may affect users’ experience. Collect
information of intra-freq hoout success rate and find out TOP10 cells with lowest intra-freq hoout execute success rate and intra-freq hoout prepare
success rate separately by day.
1) Output intra-freq hoout success rate related information by day.
Intra-Freq Hoout Success Rate (by day)
Time(by Intra-Freq L.HHO.Int L.HHO.Int Intra-Freq L.HHO.Int Intra-Freq X2 Intra-Freq S1 Data

Hoout Execute raFreq.Exe raFreq.Exe Hoout Prepare raFreq.Pre Hoout Execute Hoout Execute Comple
day)
Succ Rate cSuccOut cAttOut Succ Rate pAttOut Succ Rate Succ Rate teness
2014-01-26 99.82% 9352557 9369383 99.97% 9372541 99.80% 100.00% All Day
2) Output TOP10 cells’ information with lowest intra-freq hoout execute success rate.
TOP10 Cells with Lowest Intra-Freq Hoout Execute Success Rate

Intra-Freq L.HHO.Intrae L.HHO.Intere L.HHO.Intrae L.HHO.Intere Data
Time(by eNode eNodeB Local Cell
Hoout Execute NB.IntraFreq. NB.IntraFreq. NB.IntraFreq. NB.IntraFreq. Comple
day) B ID Name Cell ID Name
Succ Rate ExecSuccOut ExecSuccOut ExecAttOut ExecAttOut teness
2014-01-24 5315 5315 2 cell2 92.42% 134 122 155 122 2 Hours
3) Output TOP10 cells’ information with lowest intra-freq hoout prepare success rate.
TOP10 Cells with Lowest Intra-Freq Hoout Prepare Success Rate

Local Intra-Freq L.HHO.Intrae L.HHO.Intere L.HHO.Intrae L.HHO.Intere Data
Time(by eNod eNodeB Cell
Cell Hoout Prepare NB.IntraFreq. NB.IntraFreq. NB.IntraFreq. NB.IntraFreq. Comple
day) eB ID Name Name
ID Succ Rate ExecAttOut ExecAttOut PrepAttOut PrepAttOut teness
14
2014-01-24 5013 5013 0 e-34 90.20% 0 221 0 245
Hours
3.26.3 Principles
Use the original traffic measurement data from the first report to get each cell’s L.HHO.Inter/Intra-eNB.IntraFreq.ExecSuccOut,
L.HHO.Inter/Intra-eNB.IntraFreq.ExecAttOut, L.HHO.Inter/Intra-eNB.IntraFreq.PrepAttOut, L.HHO.X2.IntraFreq.ExecSuccOut and
L.HHO.X2.IntraFreq.ExecAttOut during the inspection time.
1) Intra-freq hoout success rate (by day):
b) Calculate intra-freq hoout execute success rate, intra-freq hoout prepare success rate, intra-freq X2 hoout execute success rate and intra-freq
S1 hoout execute success rate by day.
2) TOP10 cells with lowest intra-freq hoout execute success rate by day.
a) Don’t consider the data when L.HHO.IntraFreq.ExecAttOut is 0, TOP1% cells have lowest L.HHO. IntraFreq.ExecAttOut and intrafreq
hoout fail times is less than or equal to 10 (If 1% of the cell’s number is less than one, take this data into consideration).
b) For the rest of cells, get intra-freq hoout execute success rate by day.

c) Find out TOP10 cells with lowest intra-freq hoout execute success rate as an ascending order.
d) Calculate the average intra-freq hoout execute success rate of these TOP10 cells according to eNodeB ID separately (Total Success Times /
e) Sort eNodeBs by its average intra-freq hoout execute success rate as an ascending order. Cells under each eNodeB are sorted by their local
cell ID.
3) TOP10 cells with lowest intra-freq hoout prepare success rate by day.
a) Don’t consider the data when L.HHO.IntraFreq.PrepAttOut is 0, TOP1% cells have lowest L.HHO. IntraFreq.PrepAttOut and intra-freq
hoout fail times is less than or equal to 10 (If 1% of the cell’s number is less than one, take this data into consideration).
b) For the rest of cells, get intra-freq hoout prepare success rate by day.
c) Find out TOP10 cells with lowest intra-freq hoout prepare success rate as an ascending order.
d) Calculate the average intra-freq hoout prepare success rate of these TOP10 cells according to eNodeB ID separately (Total Execute Times /
e) Sort eNodeBs by its average intra-freq hoout prepare success rate as an ascending order. Cells under each eNodeB are sorted by their local
cell ID.
Note: For these three tables, if intra-freq hoout execute success rate < THRESHOLD NOK RRC Setup Succ Rate, mark it red. The default
 L.HHO.IntraFreq.ExecSuccOut = (L.HHO.IntraeNB.IntraFreq.ExecSuccOut + L.HHO.IntereNB.IntraFreq.ExecSuccOut)
 L.HHO.IntraFreq.ExecAttOut = (L.HHO.IntraeNB.IntraFreq.ExecAttOut + L.HHO.IntereNB.IntraFreq.ExecAttOut)
 L.HHO.IntraFreq.PrepAttOut = (L.HHO.IntraeNB.IntraFreq.PrepAttOut + L.HHO.IntereNB.IntraFreq.PrepAttOut)
 Intra Frequency Hoout Fail Times = L.HHO.IntraFreq.ExecAttOut –L.HHO.IntraFreq.ExecSuccOut
 IntraFreq hoout execute success rate = (L.HHO.IntraFreq.ExecSuccOut / L.HHO.IntraFreq.ExecAttOut)*100%
 IntraFreq hoout prepare success rate = (L.HHO.IntraFreq.ExecAttOut / L.HHO.IntraFreq.PrepAttOut)*100%
 IntraFreq X2 hoout execute success rate =(L.HHO.X2.IntraFreq.ExecSuccOut / L.HHO.X2.IntraFreq.ExecAttOut)*100%
 IntraFreq S1 hoout execute success rate =[(L.HHO.IntereNB.IntraFreq.ExecSuccOut -
L.HHO.X2.IntraFreq.ExecSuccOut)/(L.HHO.IntereNB.IntraFreq.ExecAttOut - L.HHO.X2.IntraFreq.ExecAttOut)]*100%

3.26.4 Measures
1) Check the network planning and optimization: Handover switch, Cell radius, Neighboring cells, CellspecificOffset and frequency offset.
2) Check the interference and RF channels: If RF channels are normal, check whether there is uplink interference.
3) If it is not cleared, collect CHR log information from eNodeBs to Huawei engineers for troubleshooting.
3.26.5 Reference
None.
3.27 Inter-Freq Handover Success Rate
3.27.1 Location

04 KPI Performance Analysis 03 Handover Performance 05 Inter-Freq Handover Success Rate
If handover success rate is lower than 98%, it will lead to call dropping when users are moving, which may affect users’ experience. Collect
information of inter-freq hoout success rate and find out TOP10 cells with lowest inter-freq hoout execute success rate and inter-freq hoout prepare success
rate separately by day.
1) Output inter-freq hoout success rate related information by day.
Inter-Freq Hoout Success Rate

Inter-Freq L.HHO.Intere L.HHO.Intere Inter-Freq L.HHO.Int Inter-Freq X2 Inter-Freq S1 Data
Time(by
Hoout Execute NB.InterFreq. NB.InterFreq. Hoout Prepare erFreq.Pre Hoout Execute Hoout Execute Complete
day)
Succ Rate ExecSuccOut ExecAttOut Succ Rate pAttOut Succ Rate Succ Rate ness
2014-01-26 - 0 0 - 0 - - All Day
2) Output TOP10 cells’ information with lowest inter-freq hoout execute success rate.
TOP10 Cells with Lowest Inter-Freq Hoout Execute Success Rate

Inter-Freq L.HHO.Intrae L.HHO.Intere L.HHO.Intrae L.HHO.Intere Data
Time(by eNodeB eNodeB Local Cell
Hoout Execute NB.InterFreq. NB.InterFreq. NB.InterFreq. NB.InterFreq. Comple
day) ID Name Cell ID Name
Succ Rate ExecSuccOut ExecSuccOut ExecAttOut ExecAttOut teness
2014-01- 5315 5315 2 cell2 95.41% 5179 1468 5499 1468 All Day

25
3) Output TOP10 cells’ information with lowest inter-freq hoout prepare success rate.
TOP10 Cells with Lowest Inter-Freq Hoout Prepare Success Rate

Inter-Freq L.HHO.Intrae L.HHO.Intere L.HHO.Intrae L.HHO.Intere
Time(b eNodeB eNodeB Local Cell Data
Hoout Prepare NB.InterFreq. NB.InterFreq. NB.InterFreq. NB.InterFreq.
y day) ID Name Cell ID Name Completeness
Succ Rate ExecAttOut ExecAttOut PrepAttOut PrepAttOut
2014-
5314 5314 1 1 91.49% 0 9537 0 10424 All Day
01-26
3.27.3 Principles
Use the original traffic measurement data from the first report to get each cell’s L.HHO.Inter/Intra-eNB.InterFreq.ExecSuccOut,
L.HHO.Inter/Intra-eNB.InterFreq.ExecAttOut, L.HHO.Inter/Intra-eNB.InterFreq.PrepAttOut, L.HHO.X2.IntreFreq.ExecSuccOut and
L.HHO.X2.IntreFreq.ExecAttOut during the inspection time.
1） Inter-freq hoout success rate (by day):
b) Calculate inter-freq hoout execute success rate, inter-freq hoout prepare success rate, inter-freq X2 hoout execute success rate and inter-freq
S1 hoout execute success rate by day.
2） TOP10 cells with lowest inter-freq hoout execute success rate by day.
a) Don’t consider the data when L.HHO.InterFreq.ExecAttOut is 0 and TOP1% cells with lowest L.HHO. InterFreq.ExecAttOut (If 1% of the
b) For the rest of cells, get inter-freq hoout execute success rate by day.
c) Find out TOP10 cells with lowest inter-freq hoout execute success rate as an ascending order.
d) Calculate the average inter-freq hoout execute success rate of these TOP10 cells according to eNodeB ID separately (Total Success Times /
e) Sort eNodeBs by its average inter-freq hoout execute success rate as an ascending order. Cells under each eNodeB are sorted by their local
cell ID.
3） TOP10 cells with lowest inter-freq hoout prepare success rate by day.
a) Don’t consider the data when L.HHO.InterFreq.PrepAttOut is 0 and TOP1% cells with lowest L.HHO. InterFreq.PrepAttOut (If 1% of the

b) For the rest of cells, get inter-freq hoout prepare success rate by day.
c) Find out TOP10 cells with lowest inter-freq hoout prepare success rate as an ascending order.
d) Calculate the average inter-freq hoout prepare success rate of these TOP10 cells according to eNodeB ID separately (Total Execute Times /
e) Sort eNodeBs by its average inter-freq hoout prepare success rate as an ascending order. Cells under each eNodeB are sorted by their local
cell ID.
Note: For these three tables, if inter-freq hoout execute success rate < THRESHOLD NOK RRC Setup Succ Rate, mark it red. The default
 L.HHO.InterFreq.ExecSuccOut = (L.HHO.IntraeNB.IntraFreq.ExecSuccOut + L.HHO.IntereNB.IntraFreq.ExecSuccOut)
 L.HHO.InterFreq.ExecAttOut = (L.HHO.IntraeNB.IntraFreq.ExecAttOut + L.HHO.IntereNB.IntraFreq.ExecAttOut)
 L.HHO.InterFreq.PrepAttOut = (L.HHO.IntraeNB.IntraFreq.PrepAttOut + L.HHO.IntereNB.IntraFreq.PrepAttOut)
 Inter- Freq hoout fail times = L.HHO.InterFreq.ExecAttOut –L.HHO.InterFreq.ExecSuccOut
 Inter-Freq hoout execute success rate = (L.HHO.InterFreq.ExecSuccOut / L.HHO.InterFreq.ExecAttOut)*100%
 Inter-Freq hoout prepare success rate = (L.HHO.InterFreq.ExecAttOut / L.HHO.InterFreq.PrepAttOut)*100%
 Inter-Freq X2 hoout execute success rate =(L.HHO.X2.InterFreq.ExecSuccOut / L.HHO.X2.InterFreq.ExecAttOut)*100%
 Inter-Freq S1 hoout execute success rate =[(L.HHO.IntereNB.IntraFreq.ExecSuccOut -
L.HHO.X2.IntraFreq.ExecSuccOut)/(L.HHO.IntereNB.IntraFreq.ExecAttOut - L.HHO.X2.IntraFreq.ExecAttOut)]*100%
3.27.4 Measures
1) Check the network planning and optimization: Handover switch, Cell radius, Neighboring cells, CellspecificOffset and QoffsetFreq.
2) Check the interference and RF channels: If RF channels are normal, check whether there is uplink interference.
3) If it is not cleared, collect CHR log information from eNodeBs to Huawei engineers for troubleshooting.
3.27.5 Reference
None.

1.32 User Throughput Rate
1.32.1 Location

04 KPI Performance Analysis 04 Throughput 01 User Throughput Rate
This rule is mainly used to collect the user throughput rate in the entire network.
1) Output related information of user throughput rate in the entire network by day.
User Throughput Rate

DL User Total DL Traffic Total Transmit UL User Total UL Traffic Total Transmit
Data
Time(by Bearer Volume for Duration of DL Bearer Volume for Duration of UL
Complete
day) Throughp PDCP SDUs in a PDCP SDUs in a Throughput PDCP SDUs in a PDCP SDUs in a
ness
ut (kbps) cell (kbits) cell (s) (kbps) cell (kbits) cell (s)
2014-01-24 190464 190464 1 - 0 0 2 Hours
2014-01-25 190446.5 2228224 11.7 - 0 0 All Day
2014-01-26 190464 2285568 12 - 0 0 All Day
2014-01-27 190464 952320 5 - 0 0 10 Hours
2) TOP10 eNodeBs with highest traffic utilization.
Traffic Utilization (TOP10)

eNodeB ID Time(by day) Traffic Utilization
50224 2014-01-24 19.00%
50224 2014-01-25 19.00%
50224 2014-01-26 19.00%
50224 2014-01-27 19.00%
50221 2014-01-24 12.00%
50221 2014-01-25 12.00%
50221 2014-01-26 12.00%
50221 2014-01-27 12.00%
645 2014-01-24 10.00%
645 2014-01-25 10.00%

1.32.3 Principles
1) User bearer throughput (by day):
a) Use the original traffic measurement data from the first report to get each cell’s total downlink traffic volume for PDCP SDUs in a cell
(kbits), total transmit duration of downlink PDCP SDUs in a cell (s), total uplink traffic volume for PDCP SDUs in a cell (kbits) and total
transmit duration of uplink PDCP SDUs in a cell (s) during the inspection time.
b) Then calculate user’s downlink & uplink bearer throughput.
c) Output summarized traffic data chronologically (by day).
2) TOP10 eNodeBs with highest traffic utilization:
a) Use the original traffic measurement data from the first report to get each cell’s total downlink traffic volume for PDCP SDUs in a cell
(kbps) and total transmit duration of downlink PDCP SDUs in a cell (s) per hour.
b) Then calculate user’s downlink bearer throughput per hour in each cell.
c) Get the value of Allocated under License Identifier= LLT1THRUL01 by MML’s DSP license command to get eNodeB’s traffic (per Mbps).
d) Calculate traffic utilization, which is user’s downlink bearer throughput/ eNodeB’s traffic (per Mbps).
e) Output TOP10 cells’ information with highest traffic utilization as a descending order.
 DL User Bearer Throughput (kbps): L.Thrp.bits.DL/ L.Thrp.Time.DL
 Total downlink traffic volume for PDCP SDUs in a cell (kbits) = L.Thrp.bits.DL/1000
 Total transmit duration of downlink PDCP SDUs in a cell (s)= L.Thrp.Time.DL/1000
 Total uplink traffic volume for PDCP SDUs in a cell (kbits)= L.Thrp.bits.UL/ L.Thrp.Time.UL
 Total uplink traffic volume for PDCP SDUs in a cell (kbits) = L.Thrp.bits.UL/1000
 Total transmit duration of uplink PDCP SDUs in a cell (s) = L.Thrp.Time.UL/1000
 Traffic utilization =(L.Thrp.bits.DL/ L.Thrp.Time.DL)/ Allocated/ 1000 (Allocated is the value corresponding under License Identifier=
LLT1THRUL01）
1.32.4 Measures
None.

1.32.5 Reference
None.
1.33 User Number
1.33.1 Location

04 KPI Performance Analysis 05 Capacity and Load 01 User Number
User number can show network's capacity and load. This rule is mainly used to collect average user number and max user number to monitor
active user number.
1) Output the average user number and its related information in the entire network by day.
Average and Max User Number

Time(by day) Traffic.User.Avg Traffic.User.Max Data Completeness
2013-09-02 127.27 560 All Day
2) Output TOP20 cells’ information with largest Traffic.User.Ulsync.Avg.
TOP20 Cells with Largest Traffic.User.Ulsync.Avg

eNodeB eNodeB Local Cell Traffic.User. Occurrence Board Synchronized User
ID Name Cell ID Name Ulsync.Avg Time Type Capacity Usage in a Cell

EJR003 2014-01-27 WD22LB
119003 EJR003 3 142.36 35.59%
3 23:00:00 BPD2
EJR003 2014-01-28 WD22LB
119003 EJR003 3 135.41 33.85%
3 23:00:00 BPD2
3) Output TOP20 eNodeBs’ information with largest RRC connected users license capacity usage.
TOP20 eNodeBs with Largest RRC Connected Users License Capacity Usage
eNodeB eNodeB Sum of the Number of RRC Occurrence RRC Connected Users License
ID Name Connected Users in an eNodeB Time Capacity Usage in an eNodeB

2014-06-27
10071 LTE40 277.86 2.57%
03:00:00
10071 LTE40 277.84 2014-06-27 2.57%

05:00:00
4) Output the overview of user number in the entire network.
User Number in the Entire Network

Max User Number of a Cell Cell Number Proportion Remark
0 ~ 100 42 100.00% -
100 ~ 200 0 0.00% -
200 ~ 300 0 0.00% -
300 ~ 400 0 0.00% -
More than 40 0 0.00% 631438_3/631019_2
1.33.3 Principles
Use the original traffic measurement data from the database to calculate average user number during the traffic measurement collected period.
1) Average and max user number (by day):
a) Get original traffic measurement data L.Traffic.User.Max and L.Traffic.User.Avg and use max (L.Traffic.User.Max) and avg
(L.Traffic.User.Avg) to get average and max user number of each cell by day.
b) Add average/max user number of each cell together to get the average/max user number in the entire network per day.
2) TOP20 cells with largest Traffic.User.Avg:
a) Use 1)’s original traffic measurement data L.Traffic.User.Avg to calculate eNodeB’s average user number per day(accumulation of cells’
L.Traffic.User.Avg under this eNodeB ) and record the occurrence time. Set this data as eNodeB’s average user number during this
inspection period, sort eNodeBs by its average user number, select largest cells and output these cells’ related information.
b) Run MML’s DSP License command to get Allocated of License. At first, check whether License Identifier field contains LLT1ACTU01 or
LT1S0ACTUS00. If yes, find out its corresponding Allocated value (Allocated of License= Allocated value*Connected user number). If
not, check whether License Item contains RRC Connected User. If yes, find out its corresponding Allocated value (Allocated of License =
Allocated value*Connected user number)
c) Calculate the ratio of eNodeB’s average user number by day to Allocated of License. If it is more than 60%, mark it red and abnormal.
Note:
 Synchronized User Capacity Usage in a Cell = L.Traffic.User.Ulsync.Avg/ Synchronized User Capacity*100%. L.Traffic.User.Ulsync.Avg
is number of UL Synchronized Users in a Cell
 If max user number of a cell > = 300 or the ratio of user number to the license > = 0.6, output all of them. If there are less than 20 cells met
these conditions, output 20 cells’ information as a descending order.
 If the records of the data are less than 20, output all of them.

3) TOP20 eNodeBs with largest RRC connected users’ license capacity usage.
a) Use 2)’s method to get each cell’s original traffic measurement data L.Traffic.User.Max and Allocated of License.
b) Calculate the ratio of max user number to Allocated of License and select TOP20 cells with largest ratio. If the ratio is more than 60%, mark
it red and abnormal. Count abnormal eNodeBs by eNodeB ID.
Note:
 If max user number of a cell > = 300 or the ratio > = 0.6, output all of them. If there are less than 20 cells met these conditions, output 20
cells’ information as a descending order.
 If the records of the data are less than 20, output all of them.
If “TOP20 cells with largest Traffic.User.Avg” and “TOP20 eNodeBs with largest RRC connected users license capacity usage” have same
eNodeBs, count as one.
4) The overview of user number in the entire network.
a) Output summarized cell number under each max user number range.
b) Calculate the percentage of cell number under each max user number range to the entire cell number.
 Average user number = sum(L.Traffic.User.Avg) / 24
L.Traffic.User.Avg is average number of users in the entire network per hour and sum (L.Traffic.User.Avg) indicates the accumulation of 24
hours’ average number of users in the entire network.
 Max user number = max(L.Traffic.User.Max)
L.Traffic.User.Max is maximum number of users in the entire network per hour.
Note: If max number of a cell is >= 400, output the information of eNodeB and cell as A_cellX/B_cellX in the “Remark column”.
1.33.4 Measures
1) If the users’ number of a cell is over 400, please submit iCare to contact the heavy traffic owner, who will provide professional proposal for
expanding capacity.
2) If the ratio of user number to the license is larger than 90%, please apply the license again to expand license user resource.
1.33.5 Reference
None.

1.34 MOCN Performance Statistic from here
1.34.1 Location

04 KPI Performance Analysis 06 MOCN Performance 01 MOCN Performance Statistic
This rule is mainly used to monitor each operators’ call drop rate and user throughput rate to reflect their network performances.
1) Output operators’ performance statistic related information (by day).
MEGAFON Performance Statistic (by day)

L.E- L.E-
L.E- L.E- Call DL User
Time( Call L.E-RAB. RAB.Nor RAB.Abn L.E-RAB.
RAB.Nor RAB.Abno Drop Bearer
by Drop Rel.PLM mRel.PL ormRel.P Rel.PLM
mRel.PL rmRel.PL Rate Throughput
day) Rate N MN.QCI. LMN.QC N.QCI.1
MN MN (VOIP) (kbps)
1 I.1
2012- 0.68
131377 897 132274 - 0 0 0 10528.01
12-14 %
2) Output operators’ performance statistic related information (by hour).
MEGAFON Performance Statistic (by hour)

L.E- L.E- L.E- L.E-
Call L.E-RAB. Call Drop L.E-RAB. DL User Bearer
Time(by RAB.Nor RAB.Abno RAB.NormR RAB.Abnorm
Drop Rel.PLM Rate Rel.PLMN. Throughput
hour) mRel.PL rmRel.PL el.PLMN.QC Rel.PLMN.QC
Rate N (VOIP) QCI.1 (kbps)
MN MN I.1 I.1
2012-12-
14 1.05% 5832 62 5894 - 0 0 0 10612.68
00:00:00
1.34.3 Principles
1) Use CNOPERATOR’s fields from XML file to get CnOperatorName (operator’s name), MCC (mobile country code), and MNC (mobile network
code) separately. (Note: Avoid repeating. Take MEGAFON operator as an example)

2) Check CELLOPERATOR’s fields from XML file to get original traffic measurement data and output them into first report by hour.
3) Use the original traffic measurement data from the first report to calculate each operator’s call drop rate, call drop rate (VOIP), DL user bearer
throughput (kbps), QCI11 DL user bearer throughput (kbps), UL user bearer throughput (kbps), QCI11 UL user bearer throughput (kbps),
average user number, eRAB setup success rate and eRAB setup success rate (VOIP) by hour and by day separately, and then output them into
second report.
4) Output related traffic measurement data to the table MEGAFON performance statistic (by day & by hour) chronologically.
1.34.4 Measures
1) Analyze based on 《LTE PS Data Transmission X Action》: http://support.huawei.com/support/pages/kbcenter/view/product.do?
actionFlag=detailProductSimple&web_doc_id=SE0000716716&doc_type=123-2&doc_type=123-2&saveBrowserLoged=true
2) If unable to solve the problem, please submit iCare for help.
1.34.5 Reference
None.
1.35 Network KPI Variation
1.35.1 Location

04 KPI Performance Analysis 07 KPI Variation Risk Identify 01 Network KPI Variation
Serious degeneration of KPI counters mean serious degeneration of user experience. This rule is used to collect the information of most
degenerated TOP cells during the data collection period for 13 KPI counters which are listed in the table in Principles. These counters are separated into 3
groups, which are 1, 2 and 4. Counters in different groups have different algorithms.
1) Output TOP cells’ information with most degenerate L.RRC.SetupFail.NoReply.
TOP Cells with Most Degenerate L.RRC.SetupFail.NoReply

Absolute Relative
eNodeB eNodeB Cell L.RRC.SetupFail Latest N
Local Cell ID Time Range Degenerate Degenerate
ID Name Name .NoReply Day
Value Value

2012-12-14 VS
230457 230457 1 2304572 34.88 3100.00% 1.12->36.00 12-17: 36.00
2012-12-17
Note: This table only list parts of counters. N means 1~7 days. 1.12->36.00 indicates the data domain of corresponding counter during the time
period.
2) Output TOP cells’ information with most degenerate RRC setup success rate.
TOP Cells with Most Degenerate RRC Setup Succ Rate

Absolute Relative RRC
eNode eNodeB Local Cell Time Attempt Fail Latest N
Degenera Degenera Setup
B ID Name Cell ID Name Range Times Times Day
te Value te Value Succ Rate
2012-12-14 12-17:
23045 23045 99.75%- 10547.0(1101 9.0(27.0-
230457 1 VS 2012- -0.07 7.48% 92.29%(3
7 72 >92.29% 4.0->467.0) >36.0)
12-17 6.0/467.0)
Note: The other 11 counters’ output format are similar with table of TOP Cells with Most Degenerate RRC Setup Succ Rate, and only the
counter name and output data are different.
1.35.3 Principles
1) The classification of counters is listed in the below table.
Category Counter Name Classification

L.RRC.SetupFail.NoReply 1
RRC Setup Success Rate (%) 4
Abnormal ration of MSG4/MSG1 (%) 1
eRAB Setup Success Rate (%) 1
Call drop Rate (%) 2
Network Basic Reestablish rate (%) 1
Counter Intra-Freq hoout execute success rate (%) 1
Inter-Freq hoout execute success rate (%) 1
Intra-RAT hoout execute success rate (L2U) (%) 1
Intra-RAT hoout execute success rate (L2G) (%) 1
Intra-RAT hoout execute success rate (L2C) (%) 1
Hoin prepare success rate (%) 1
CSFB response success rate (%) 1
 Number of RRC connection setup failures due to no responses from the UE = L.RRC.SetupFail.NoReply.
 RRC setup success rate (%) = [L.RRC.ConnReq.Succ]/ [L.RRC.ConnReq.Att]*{100}.
 Abnormal ration of MSG4/MSG1 (%) = (L.RA.GrpA.ContResolution+L.RA.GrpB.ContResolution) / (L.RA.GrpA.Att+L.RA.GrpB.Att).
 eRAB setup success rate (%) = [L.E-RAB.SuccEst]/[L.E-RAB.AttEst]*{100}.

 Drop call rate (%) = [L.E-RAB.AbnormRel]/([L.E-RAB.AbnormRel]+[L.E-RAB.NormRel])*{100}；
 Reestablish rate (%) = L.RRC.ReEst.Succ/L.RRC.ReEst.Att.
 Intra-Freq hoout execute success rate (%) = ([L.HHO.IntraeNB.IntraFreq.ExecSuccOut] +
[L.HHO.IntereNB.IntraFreq.ExecSuccOut])/([L.HHO.IntraeNB.IntraFreq.ExecAttOut]+[L.HHO.IntereNB.IntraFreq.ExecAttOut])*{100}.
 Inter-Freq hoout execute success rate (%) = ([L.HHO.IntraeNB.InterFreq.ExecSuccOut] + [L.HHO.IntereNB.InterFreq.ExecSuccOut]) /
([L.HHO.IntraeNB.InterFreq.ExecAttOut] + [L.HHO.IntereNB.InterFreq.ExecAttOut])*{100}.
 Inter-RAT hoout execute success rate (L2U) (%) = [L.IRATHO.E2W.ExecSuccOut]/ [L.IRATHO.E2W.ExecAttOut]*{100}.
 Inter-RAT hoout execute success rate (L2G) (%) = [L.IRATHO.E2G.ExecSuccOut] / [L.IRATHO.E2G.ExecAttOut]*{100}.
 Inter-RAT hoout execute success rate (L2C) (%) = [L.IRATHO.E2C.ExecSuccOut] / [L.IRATHO.E2C.ExecAttOut)]*{100}.
 Hoin prepare success rate (%) = (L.HHO.IntraeNB.ExecAttIn+L.HHO.IntereNB.ExecAttIn) /
(L.HHO.IntraeNB.PrepAttIn+L.HHO.IntereNB.PrepAttIn).
 CSFB response success rate (%) = [L.CSFB.PrepSucc]/[L.CSFB.PrepAtt]*100.
 Absolute degenerate value = B-A.
 Relative degenerate value = {(B-A)/A}*100%.
Note: A indicates the counter value in the beginning of the time period and B indicates the counter value in the end of the time period.
2) Definitions of attempt times for each counter.
 For group 1 and group 2 counters, denominator is the attempt times.
 For group 4 counters, it is the absolute value itself.
3) Definitions of fail times for each counter.
 For group 1 counters, (denominator-numerator) is the fail times.
 For group 2 counters, numerator is the fail times.
 For group 4 counters, it is the absolute value itself.
Note: Classification and definition of counters are the same in Network KPI Variation and Network KPI Variation (during specific time) rules.
4) Obtain the busy hour by OMStar function, such as 6:00~24:00 and get each traffic measurement according to the original granularity.
5) Calculate each counter every day.
a) For group 1 and group 2 counters, summarize traffic measurement according to busy hour. Add denominator and numerator together
separately to get the counter value for each cell. Take group 1 counter RRC setup success rate (busy hour is 6:00~24:00) for example, add
these 18 hours’ L.RRC.ConnReq.Succ (numerator) and L.RRC.ConnReq.Att (denominator) together separately and then make a division to
get the RRC setup success rate every day.
b) For group 4 counters, get the traffic measurement under each original granularity and then make an arithmetic average of them to get the

counter value for each cell. Take group 4 counter L.RRC.SetupFail.NoReply (busy hour is 6:00~24:00 and original granularity is 30
minutes) for example, make an arithmetic average of these 36 pieces of traffic measurement.
6) Sort the cells based on the KPI recovery threshold. The methods are listed below.
a) Check whether the counter in latest day recovers or not. Put the unrecovered cells in the front.
b) Among the unrecovered cells, sort them based on their absolute degenerate values.
c) Among the recovered cells, sort them based on their absolute degenerate values.
d) Method of judging whether it is recovered: If counter in the latest day < initial value of degeneration+K*absolute degenerate value), it is
considered as recovered cell. K is the threshold and configurable. Its range is [0, 0.5] and the default value is 0.25.
7) Filter the data based on the filteration threshold of attempt times and output TOP cells with most degenerate KPI counters.
a) Don’t consider the cells if their attempt times is 0 or “-”.
b) Sort the cells as an ascending order and don’t consider the first 10% cells.
Note: Filteration threshold of attempt times is 10% by default and configurable.
1.35.4 Measures
1.35.5 Reference
None.
1.36 Traffic Variation
1.36.1 Location

04 KPI Performance Analysis 07 KPI Variation Risk Identify 02 Traffic Variation

degenerated TOP cells during the data collection period for 2 KPI counters which is listed in the table in Principles. These counters are separated into 3
1) Output TOP cells’ information with most degenerate downlink PRB usage.
TOP Cells with Most Degenerate DL PRB Usage (%)

Absolute Relative Average Max User
eNodeB eNodeB Local Cell DL PRB Latest N
Time Range Degenerate Degenera User Number
ID Name Cell ID Name Usage Day
Value te Value Number
2012-12-14 VS 12-17: 16->18 31->23
230457 230457 1 2 0.82 533.61% 0.15->0.97
2012-12-17 0.97
Note: This table only list parts of counters. N means 1~7 days. 0.15->0.97 indicates the data domain of corresponding counter during the time
period.
2) Output TOP cells’ information with most degenerate uplink PRB usage.
TOP Cells with Most Degenerate UL PRB Usage (%)

Absolute Relative Average Max User
eNodeB eNodeB Local Cell UL PRB Latest N
Time Range Degenerate Degenerate User Number
ID Name Cell ID Name Usage Day
Value Value Number
2012-12-14 VS 0.15- 12-17: 3->5 10->9
230117 230117 1 2 0.47 311.20%
2012-12-17 >0.62 0.62
1.36.3 Principles
1) The classification of counters is listed in the below table.
Category Counter Name Classification

Traffic DL PRB usage (%) 4
measurement UL PRB usage (%) 4
 DL PRB usage (%) = [L.ChMeas.PRB.DL.Used.Avg]/[Downlink System Bandwidth Corresponds to the Total Number of RB]*{100}.
 UL PRB usage (%) = [L.ChMeas.PRB.UL.Used.Avg]/[Uplink System Bandwidth Corresponds to the Total Number of RB]*{100}.
 Absolute degenerate value = B-A.
 Relative degenerate value = {(B-A)/A}*100%.
Note: A indicates the counter value in the beginning of the time period and B indicates the counter value in the end of the time period.
2) Definitions of attempt times for each counter.
 For group 1 and group 2 counters, denominator is the attempt times.
 For group 4 counters, it is the absolute value itself and it is taken as attempt times directly.
3) Definitions of fail times for each counter.

 For group 1 counters, (denominator-numerator) is the fail times.
 For group 2 counters, numerator is the fail times.
 For group 4 counters, it is the absolute value itself and it is taken as fail times directly.
Note: Classification and definition of counters are the same in Traffic Variation and Traffic Variation (during specific time) rules.
4) Obtain the busy hour by OMStar function, such as 6:00~24:00 and get each traffic measurement according to the original granularity.
5) Calculate each counter every day.
a) For group 4 counters, get the traffic measurement under each original granularity and then make an arithmetic average of them to get the
counter value for each cell. Take group 4 counter L.RRC.SetupFail.NoReply (busy hour is 6:00~24:00 and original granularity is 30
minutes) for example, make an arithmetic average of these 36 pieces of traffic measurement.
6) Sort the cells based on the KPI recovery threshold. The methods are listed below.
a) Check whether the counter in latest day recovers or not. Put the unrecovered cells in the front.
b) Among the unrecovered cells, sort them based on their absolute degenerate values.
c) Among the recovered cells, sort them based on their absolute degenerate values.
d) Method of judging whether it is recovered: If counter in the latest day < initial value of degeneration+K*absolute degenerate value, it is
considered as recovered cell. K is the threshold and configurable. Its range is [0, 0.5] and the default value is 0.25.
1.36.4 Measures
1.36.5 Reference
None.
1.37 Network KPI Variation (during specified time)
1.37.1 Location

04 KPI Performance Analysis 07 KPI Variation Risk Identify 03 Network KPI Variation (during specific time)

1) Output TOP cells’ information with most degenerate call drop rate before and after the specific time.
TOP Cells with Most Degenerate Call Drop Rate Before and After the Specific Time
Absolut Relati
Time Time Atte
eNode Local e ve Call Fail Latest Latest Latest Latest
eNod Cell Range Range mpt Rema
B Cell Degene Degen Drop Tim First Secon Third Fourth
eB ID Name Before After Tim rk
Name ID rate erate Rate es Day d Day Day Day
Upgrade Upgrade es
Value Value
145
2013-09- 2013-09- 73.0
29.0 9-4: 9-3:
02 03 0.06% (206 9-5: 9-2:
(13. 0.11% 0.12%
00:00:00 - 01:00:00 - 89.58 - 94.0 0.00% 0.06%(1
6 02 2 0602 0 0- (18.0/ (24.0/ 　
2013-09- 2013-09- % >0.12 - (0.0/5 3.0/206
>42. 15722 19994
03 05 % >35 59.0) 94.0)
0) .0) .0)
00:00:00 00:00:00 267.
0)
Note: The other 11 counters’ output format are similar with table of TOP Cells with Most Degenerate Call Drop Rate During Specific Time, and
only the counter name and output data are different.
1.37.3 Principles
Note: Classification and definition of counters are the same in Network KPI Variation and Network KPI Variation (during specific time) rules.
The details are in the rule Network KPI Variation.
1) Obtain the busy hour by OMStar function, such as 6:00~24:00 and get each traffic measurement according to the original granularity, starting
time of upgrade / operation and ending time of upgrade / operation.
2) Obtain the time range when importing the data.
a) If there are intersections among (time range before the specific time - N*7*24h), where N is 1, 2, 3 or 4, time range after the specific time
and the busy hour (The intersection can’t contain the upgrade/operation time range), it is suggested to compare data before and after the
intersections(scenarioⅠ). Or compare data based on the existing data (scenarioⅡ).

b) In both scenarios, the frontline designate a specific time and there are time ranges before and after the specific time. Also, the time range is
separated into weekend and weekday. Therefore, there are 4 time ranges: weekend before the specific time, weekday before the specific
time, weekend after the specific time and weekday after the specific time.
Note: For scenarioⅠ:
If there is longer time range before the specific time, such as there are two Mondays’ 6:00~24:00 and two Tuesdays’ 6: 00~12:00, make
arithmetic averages between these two Mondays and Tuesdays separately.
For scenarioⅡ:
The output absolute value need to do the arithmetic average based on days.
3) Calculate each counter during these four time ranges and make a statistic based on busy hour of these four time ranges.
a) For group 1 and group 2 counters, add the numerator and denominator together during the specific time and use the sum to calculate each
counter (cell level).
counter value for each cell during each time range.
4) Don’t consider the time range when there are small attempt times for each cell.
a) Don’t consider the cells if their attempt times are 0 or “-”.
b) Sort the cells as an ascending order and don’t consider the first 1% cells.
Note: Filteration threshold of attempt times is 1% by default and configurable.
5) Find TOP cells with most degenerate KPI counters before and after the specific time. For each cell:
a) If there are 4 time ranges (weekend before the specific time, weekday before the specific time, weekend after the specific time and weekday
after the specific time), calculate Δ(weekend after the specific time- weekend before the specific time), Δ(weekday after the specific time-
weekday before the specific time) and get the Δmax, corresponding A and B(such as Δmax=A-B) and their corresponding fail
times(Definitions are in the following explanation).
 If there are time ranges of weekend before the specific time, weekend after the specific time and weekday after the specific time, get the Δ
by weekend before the specific time and weekend after the specific time.
 If there are time ranges of weekday before the specific time, weekend after the specific time and weekday after the specific time, get the Δ
by weekday before the specific time and weekday after the specific time.
 If there are time ranges of weekend before the specific time, weekday before the specific time and weekend after the specific time, get the Δ
 If there are time ranges of weekend before the specific time, weekday before the specific time and weekday after the specific time, get the Δ

 If there are time ranges of (weekend before the specific time, weekday after the specific time) and (weekday before the specific time,
weekend after the specific time), get the Δ by these two time range directly and output “Unreliable Result” in the remark column..
Note: For group 1 counters, there is no need to take participate in the sort if Δ is positive and use their absolute values to take participate the sort
if Δ is negative. For group 2 and 4 counters, there is no need to take participate in the sort if Δ is negative.
b) After checking all of the cells, sort them as an ascending order based on Δmax (corresponding with Δfail times =fail times of A – fail times
of B) and don't consider the cells which theirΔfail times = 0 or falls into first TOP 1% cells.
c) For the rest of cells, output the number of cells as a descending order based on Δmax . If the fluctuated threshold is 0%, the number of cells
is MAX (1%* total cells, 20). If not, only consider cells which their Δmax is greater than the fluctuated threshold. If the number of cells are
more than MAX (1%* total cells, 20), set it to MAX (1%*total cells, 20).
Note:
 Time range: Time that corresponds with A and B (Δmax = A-B).
 Absolute fluctuated value: Δmax.
 Relative fluctuated value: Δmax/B. If B is 0, set it to “-”.
 For XX success rate, XX attempt times, XX fail times and other columns need to show the change of A and B, output the value of B before ‘->’
and the value of A after ‘->’.
 XXX Counter in latest N day: Fail times of XXX Counter in latest N day/ Attempt times of XXX Counter in latest N day.
1.37.4 Measures
1) Please check operation record and external interference first.
1.37.5 Reference
None.
1.38 Traffic Variation (during specific time)
1.38.1 Location

04 KPI Performance Analysis 07 KPI Variation Risk Identify 04 Traffic Variation(during specific time)
1) Output TOP cells’ information with most degenerate downlink PRB usage before and after the specific time.
TOP Cells with Most Degenerate Downlink PRB Usage Before and After the Specific Time
Absol Relati
eNod Time Time
eNo Local ute ve Downli Latest Latest Latest Latest Average
eB Cell Range Range Max User Rema
deB Cell Degen Degen nk PRB First Secon Third Fourt User
Nam Name Before After Number rk
ID ID erate erate Usage Day d Day Day h Day Number
e Upgrade Upgrade
Value Value
2013-09- 2013-09-
6256 SHJL 02 00:00 - 03 01:00 - 18.99 0.12- 9-5: 9-4: 9-3: 9-2:
2569 3 0.02 6->7 20->29 　
9 25693 2013-09- 2013-09- % >0.14 0.17 0.13 0.12 0.12
03 00:00 05 00:00
2) Output TOP cells’ information with most degenerate uplink PRB usage before and after the specific time.
TOP Cells with Most Degenerate Uplink PRB Usage Before and After the Specific Time
Absol Relati
eNod Time Time
eNo Local ute ve Uplink Latest Latest Latest Latest Average
eB Cell Range Range Max User Rema
deB Cell Degen Degen PRB First Second Third Fourt User
Nam Name Before After Number rk
ID ID erate erate Usage Day Day Day h Day Number
e Upgrade Upgrade
Value Value
Al-
2013-09- 2013-09-
Rams
6272 RAKL 02 00:00 - 03 01:00 - 26.68 0.06- 9-5: 9-4: 9-3: 9-2:
-1- 3 0.02 1->1 6->8 　
7 27273 2013-09- 2013-09- % >0.08 0.08 0.07 0.07 0.06
RAK
03 00:00 05 00:00
2727
1.38.3 Principles
Note: Classification and definition of counters are the same in Traffic Variation and Traffic Variation (during specific time) rules. The details are
in the rule Traffic Variation.
1) Obtain the busy hour by OMStar function, such as 6:00~24:00 and get each traffic measurement according to the original granularity, starting
time of upgrade / operation and ending time of upgrade / operation.

2) Obtain the time range when importing the data.
a) If there are intersections among time range before the specific time - N*7*24h (N is 1, 2, 3 and 4), time range after the specific time and the
busy hour (The intersection can’t contain the upgrade/operation time range), it is suggested to compare data before and after the
intersections(scenarioⅠ). Or compare data based on the existing data (scenarioⅡ).
b) In both scenarios, the frontline designate a specific time and there are time ranges before and after the specific time. Also, the time range is
separated into weekend and weekday. Therefore, there are 4 time ranges: weekend before the specific time, weekday before the specific
time, weekend after the specific time and weekday after the specific time.
Note: For scenarioⅠ:
If there is longer time range before the specific time, such as there are two Mondays’ 6:00~24:00 and two Tuesdays’ 6: 00~12:00, make
arithmetic averages between these two Mondays and Tuesdays separately.
For scenarioⅡ:
The output absolute value need to do the arithmetic average based on days.
3) Calculate each counter during these four time ranges and make a statistic based on busy hour of these four time ranges.
a) For group 1 and group 2 counters, add the numerator and denominator together during the specific time and use the sum to calculate each
counter (cell level).
counter value for each cell during each time range.
4) Find TOP cells with most degenerate KPI counters before and after the specific time. For each cell:
a) If there are 4 time ranges (weekend before the specific time, weekday before the specific time, weekend after the specific time and weekday
after the specific time), calculate Δ(weekend after the specific time- weekend before the specific time), Δ(weekday after the specific time-
weekday before the specific time) and get the Δmax, corresponding A and B(such as Δmax=A-B) and their corresponding fail
times(Definitions are in the following explanation).
 If there are time ranges of weekend before the specific time, weekend after the specific time and weekday after the specific time, get the Δ
 If there are time ranges of weekday before the specific time, weekend after the specific time and weekday after the specific time, get the Δ
 If there are time ranges of weekend before the specific time, weekday before the specific time and weekend after the specific time, get the Δ
 If there are time ranges of weekend before the specific time, weekday before the specific time and weekday after the specific time, get the Δ

 If there are time ranges of (weekend before the specific time, weekday after the specific time) and (weekday before the specific time,
weekend after the specific time), get the Δ by these two time ranges directly and output “Unreliable Result” in the remark column..
Note: For group 1 counters, there is no need to take participate in the sort if Δ is positive and use their absolute values to take participate the sort
if Δ is negative. For group 2 and 4 counters, there is no need to take participate in the sort if Δ is negative.
b) After checking all of the cells, sort them as an ascending order based on Δmax (corresponding with Δfail times =fail times of A – fail times
of B) and don't consider the cells which theirΔfail times = 0 or falls into first TOP 1%.
c) For the rest of cells, output the number of cells as a descending order based on Δmax . If the fluctuated threshold is 0%, the number of cells
is MAX (1%* total cells, 20). If not, only consider cells which their Δmax is greater than the fluctuated threshold. If the number of cells are
more than MAX (1%* total cells, 20), set it to MAX (1%*total cells, 20).
Note:
 Time range: Time that corresponds with A and B (Δmax = A-B).
 Absolute fluctuated value: Δmax.
 Relative fluctuated value: Δmax/B. If B is 0, set it to “-”.
 For XX success rate, XX attempt times, XX fail times and other columns need to show the change of A and B, output the value of B before ‘->’
and the value of A after ‘->’.
 XXX Counter in latest N day: Fail times of XXX Counter in latest N day/ Attempt times of XXX Counter in latest N day.
1.38.4 Measures
1.38.5 Reference
None.
1.39 TOP Risk Cells of KPI Degeneration
1.39.1 Location

04 KPI Performance Analysis 07 KPI Variation Risk Identify 05 TOP Risk Cells of KPI Degeneration
Serious degeneration of KPI counters mean serious degeneration of user experience. This rule is used to select cells with several degenerate KPI
counters, which can help the users to handle the top risks first.
1) Output TOP5 cells’ information with serious degenerate KPI counters.
TOP5 Risky Cells with Serious Degenerate KPI Counters
eNodeB eNodeB Local Cell Number of Degenerate 01 Network KPI 02 Traffic
ID Name Cell ID Name KPI Counters Variation Variation
Intra-Freq hoout execute Uplink PRB usage

230466 230466 3 2304664 2
success rate (%): -0.06% (%): 0.32%
1.39.3 Principles
1) Based on the result of Network KPI Variation and Traffic Variation rules, select cells with several degenerate KPI counters and output the
information of these counters and corresponding eNodeBs.
1.39.4 Measures
1.39.5 Reference
None.
1.40 TOP Risk Cells of KPI Degeneration (during specific time)
1.40.1 Location

04 KPI Performance Analysis 07 KPI Variation Risk Identify 06 TOP Risk Cells of KPI Degeneration (during specific time)

Serious degeneration of KPI counters mean serious degeneration of user experience. This rule is used to select cells with several degenerate KPI
counters, which can help the users to handle the top risks first.
1) Output TOP5 cells’ information with serious degenerate KPI counters (during specific time).
TOP5 Risky Cells with Serious Degenerate KPI Counters
eNodeB eNodeB Local Cell Number of Degenerate 01 Network KPI Variation 02 Traffic Variation (during
ID Name Cell ID Name KPI Counters (during specific time) specific time)
UL PRB usage (%): 0.01%,

53841 GUL_1_7_L 1 CELL_1 2 --
DL PRB usage (%): 0.00%
1.40.3 Principles
1) Based on the result of Network KPI Variation (during specific time) and Traffic Variation (during specific time) rules, select cells with several
degenerate KPI counters and output the information of these counters and corresponding eNodeBs.
1.40.4 Measures
1.40.5 Reference
None.
1.41 Parts of Support Precaution Notices Which Need Manual Check
1.41.1 Location

05 Precaution & Rectification Check 01 Precaution Check 01 Parts of Support Precaution Notices Which Need Manual Check

This rule is mainly used to list precautions which need manual check.
1) List precautions which need manual check.
Parts of Support Precaution Notices Which Need Manual Check

Notice ID Notice Name eNodeB Type NE Version Link Recommendation
http://support.huawei.co
m/carrier/navi#col=produ
Notice on Precaution for DBS3900
SRAN7.X, ct&path=PBI1-
LTE FDD-Parameter BTS3900
SRAN8.X and 7851894/PBI1-
SC0000857176 PresenceAntennaPort1 BTS3900A Check manually
SRAN9.X 7854240/PBI1-
configuration suggestion- BTS3900AL
versions 7854329/PBI1-
20140916-A-V1.1 BTS3900L
7923298/PBI1-
14065&resTab=BU
Support precaution notices list rules which need manual check. Please click the support link to get the details.
Each version’s corresponding precaution rules are listed in the below excel table.
Pa rts o f Sup p o rt
Pre ca utio n N o tice s Wh ich N e e d M a nua l Ch e ck.xls x
1.41.3 Principles
None.
1.41.4 Measures
None.
1.41.5 Reference
http://support.huawei.com/carrier/navi#col=product&path=PBI1-7851894/PBI1-7854240/PBI1-7854329/PBI1-7923298/PBI1-14065&resTab=BU

1.42 Notice on Precaution for FDD eNodeBs – Network Access Failures after the IP Path
Switchover Is Performed
1.42.1 Location

05 Precaution & Rectification Check 01 Precaution Check 06 Notice On Precaution-Network Access Failures after the IP Path Switchover Is Performed
When IP PATH switchovers abnormally, service admission fails, or UEs are abnormally released. The L.E-RAB.FailEst.TNL and L.E-
RAB.AbnormRel.TNL counters increase at the same time. This rule is mainly used to collect eNodeBs’ related information with this risk.
eNodeBs with Risk

eNodeB eNodeB Path RSCG RSCGRPULC RSCGRPDLC TRMDLOL TRMULOLC
Peer IP JNRSCGRP
ID Name ID RPID ACSWITCH ACSWITCH CSWITCH SWITCH
1 1 1 171.25.36.52 ENABLE 7 ON OFF OFF OFF
1.42.3 Principles
1) The value of Peer IP varies with IP paths in the LST IPPATH command output. If JNRSCGRP (Join Transmission Resource Group) is 0, which
is DISABLE state, end. If it is 1, which is ENABLE state, and RSCGRPID (Transmission Resource Group ID), Port Type, and Port No are not
exactly same, go to next step.
2) Check the ENDPOINTID under EP2RSCGRP from XML file. If there is no value or just one set, end. If there are two sets or more, go to next
step.
3) RSCGRPULCACSWITCH (Resource Group Uplink Admission Control Algorithm Switch) or RSCGRPDLCACSWITCH (Resource Group
Downlink Admission Control Algorithm Switch) is set to on in the LST TACALG command output.
4) RSCGRPULCACSWITCH and RSCGRPDLCACSWITCH are set to off in the LST TACALG command output. But TRMULOLCSWITCH
(Uplink OLC Algorithm Switch) or RSCGRPDLCACSWITCH (Downlink OLC Algorithm Switch) is set to on in the LST TOLCALG command
output.
 The fault occurs when 1)2)3) or 1)2)4) are met.

5) Output eNodeBs’ related information with this fault.
1.42.4 Measures
Precaution link:
1.42.5 Reference
None.
1.43 Precaution Bulletin on Service Impact Caused by ETH Interconnected Mode
1.43.1 Location

05 Precaution & Rectification Check 01 Precaution Check 03 Precaution Bulletion on Service Impact Caused by ETH Interconnected Mode
When a 3900 series base station is interconnected with Huawei's RTN through electrical ports, the base station links are intermittently interrupted
and the bit error rate (BER) increases after the RTN is powered off and then on. Services carried by the base station are affected.
eNodeBs with Risk

eNodeB eNodeB Port Port Local Local Peer PEERNEGO
ID Name No. Attribute Speed Duplex Speed MODE

1 1 1 Auto 10M Full duplex 10M AUTO
1.43.3 Principles
1) Check whether Port Attribute is Auto by MML’s DSP ETHPORT command. If no, end. If yes, go to next step.
2) From DSP ETHPORT command output, select Port Status = Up (activated), and then judge whether Local Duplex = Full Duplex and Local
Speed = 10M. If yes, mark it as abnormal.

1.43.4 Measures
1) Set electrical ports on both the RTN and base station to work in forced full-duplex mode at 100 Mbit/s.
2) Refer to precaution link:
1.43.5 Reference
None.
1.44 Notice on Precaution – Check of Abnormal RX Power of Optical Module (Only relates to
China)
1.44.1 Location

05 Precaution & Rectification Check 01 Precaution Check 04 Notice on Precaution – Check of Abnormal RX Power of Optical Module (Only relates to China)
None.
1.44.3 Principles
None.
1.44.4 Measures
None.
1.44.5 Reference
None.

1.45 Notice on Precaution for Certificate Expiry Not Promptly Notified Because of Certificate
Validity Check Disabling
1.45.1 Location

05 Precaution & Rectification Check 01 Precaution Check 05 Notice on Precaution for Certificate Expiry Not Promptly Notified Because of Certificate Validity Check Disabling
If certificate validity check is disabled, the eNodeB does not automatically update certificates, check certificate validity, or promptly give a
certification expiry notification. And the eNodeB may use an expired certificate for IKE or SSL negotiation and there is a risk of secure channel
renegotiation failure, which will interrupt services on the carried OM channels and service links. This rule is mainly used to collect eNodeBs’ related
information with this risk.
Certificate Validity Config Check
eNodeB ID eNodeB Name Certificate Validity Config Check Cause
The eNodeB using the certificate to confirm the safe

630828 -- Off
channel can’t prompt the certification is out of date.
1.45.3 Principles
1) Check the value of AUTHMETH under IKEPROPOSAL from XML file to confirm whether the eNodeB uses certificates for secure channel
authentication. If not, end. If yes, go to next step (AUTHMETH=IKE_RSA_SIG~9 means yes).
2) Check the value of ISENABLE under Certchktsk to confirm whether certificate validity check is enabled. If not, prompt a risk
(ISENABLE=DISABLE~0 means no).
1.45.4 Measures
If an eNodeB uses certificates for secure channel authentication, enable certificate validity check by running MML command: SET
CERTCHKTSK: ISENABLE=ENABLE~1.

Please refer to precaution link:
http://support.huawei.com/carrier/docview!docview?nid=SC2000001835&path=PBI1-7851894/PBI1-21433538/PBI1-7854329/PBI1-21465979/PBI1-
14065
1.45.5 Reference
None.
1.46 Notice on Precaution for Remote OMCH Reestablishment Failure Due to Self-Setup
Disabling
1.46.1 Location

05 Precaution & Rectification Check 01 Precaution Check 06 Notice on Precaution for Remote OMCH Reestablishment Failure Due to Self-Setup Disabling
When remote OMCH self-setup is disabled and eNodeB transmission is interrupted, current transmission configuration will be used to rectify it.
If it is caused by peer’s transmission reconfiguration or other reasons, the remote OMCH cannot be automatically reestablished. This rule is mainly used to
collect the state of eNodeBs’ remote OMCH auto-establishment switch.
1) Output eNodeBs’ number of disabled and enabled remote OMCH auto-establishment switch.
OMCH Auto-Establishment Switch (eNodeB Number)

OMCH Auto-Establishment OMCH Auto-Establishment
　
Switch(DISABLE) Switch(ENABLE)
eNodeB Number 1 250
2) Output eNodeBs’ related information with disabled remote OMCH auto-establishment switch.
OMCH Auto-Establishment Switch (DISABLE)
eNodeB ID eNodeB Name OMCH Auto-Establishment Switch
600071 TLWW1_RJ DISABLE

1.46.3 Principles
1) Check the value of SWITCH under DHCPSW from XML file. Count the number of ENABLE and DISABLE eNodeBs (SWITCH = 0 means
DISABLE state and SWITCH = 1 means ENABLE state).
2) Output eNodeBs’ related information with disabled SWITCH.
1.46.4 Measures
MML command: SET DHCPSW: SWITCH=ENABLE~1.
Precaution link: http://support.huawei.com/carrier/docview!docview?nid=SC2000002988&path=PBI1-7851894/PBI1-21433538/PBI1-
7854329/PBI1-21465979/PBI1-14065
1.46.5 Reference
None.
1.47 Precaution Notice for LampSite - License Resources Become Insufficient Following
Capability Improvements of the BBP (LBBPd or UBBPd3, UBBPd4, UBBPd5, or UBBPd6)
1.47.1 Location

05 Precaution & 07 Precaution Notice for LampSite-License Resources Become Insufficient Following
01 Precaution Check
Rectification Check Capacity Improvements of the BBP(LBPPd3 or UBBPd3, UBBPd4, UBBPd5 or UBBPd6)
By default, the intra-BBU Baseband Sharing (2T) license control item is free of charge for three sector equipment groups configured on the BBP
that connects to optical fibers. Extra sector equipment groups require paid licenses. If such a BBP has improved the capability to support six or more sector
equipment groups and is configured with more than four sector equipment groups, the license algorithm typically malfunctions, leading to license
insufficiency. In site deployment and capacity expansion scenarios, cells on the base station cannot be activated due to license insufficiency.

eNodeBs with Risk

Occurrence Sector Equipment Groups
eNodeB eNodeB SR Recommen
Current Software Version Time of CN SN Board Type Configured on the BBP that
ID Name N dation
ALM-26819 Connects to Optical Fibers
Refer to
BTS3900 2013-12-25 WD22UBBP
60059 eNB211 0 0 1 5 this
V100R009C00SPC100B061 11:02:00 D6
Precaution
1.47.3 Principles
1) Check active alarm of alarmid=26819 (Data Configuration Exceeding Licensed Limit) from Alarm.csv file and record its latest occurrence time.
2) Confirm the eNodeB has deactivated cells: CellActiveState = 0 under CELL from LMT.XML file.
3) Run MML’s DSP BRDMFRINFO to confirm the board type is LBBPd3 or UBBPd3/4/5/6 (For example, Type = WD2LBBPD3, WD2UBBPD3,
WD2UBBPD4, WD2UBBPD5 or WD2UBBPD6) and record boards’ CN, SRN and SN.
4) BBP connected to optical fibers: Check the value of HeadCabinetNo, HeadSubrackNo and HeadSlotNo (identify the location of the board that CPRI
port belongs to and they corresponds with 3)’s physical position) under RRUCHAIN from LMT.XML file. When both HeadCabinetNo and
HeadSubrackNo are 0, it indicates that BBP board is connected to optical fibers.
5) More than four sector equipment groups are configured: Check BaseBandEqmId and SectorEqmGroupId under EuSectorEqmGroup from LMT.
XML file to confirm the value of BaseBandEqmId is the same with last step’s SN and one BaseBandEqmId support more than 4 different
SectorEqmGroupId.
Note:
 BaseBandEqmId parameter indicates the ID of the baseband equipment serving a cell, corresponds with last step’s SN.
 SectorEqmGroupId parameter indicates the group ID of the sector devices that serve the cell and it uniquely identifies a group of sector devices within an eNodeB.
1.47.4 Measures
Obtain and use the commissioning license for the problem LampSite base stations.
1.47.5 Reference
Precaution link:

21117379
3.28 Precaution Notice for Temperature Exception Alarm Reporting and Repeated Restart of LampSite
RHUB Working in Low Temperature
3.28.1 Location

15 Precaution Notice for Temperature Exception Alarm Reporting and
05 Precaution & Rectification Check 01 Precaution Check
Repeated Restart of LampSite RHUB Working in Low Temperature
Due to inappropriate setting of the temperature threshold, the RHUB under the trigger conditions reports ALM-26771 RHUB Temperature
Unacceptable when it should not. The post-processing of the alarm causes the RHUB to restart. The RHUB restarts repeatedly, resulting in service
unavailability.
1) Output eNodeBs’ related information with this alarm.
Abnormal Data
eNodeB ID eNodeB Name eNodeB Version CN SRN SN Preventive Tool Is Used or Not Recommendation
BTS3900
Refer to the
393719 -393719-OF V100R010C10SPC18 0 60 0 No
precaution
0
3.28.3 Principles
1） Find SWVERSION under NE from LMT.XML file. If SWVERSION is BTS3900 V100R010C10SPC180 or BTS3900 V100R010C10SPC182,
go to next step, or end.
2） Check and record CN, SRN and SN under RHUB from LMT.XML file.
3） Run MML’s DSP BRDMFRINFO command to query corresponding hot patch’s vendor based on 2)’s CN, SRN and SN. If Vendor = HUAWEI,
it indicates hot patch has been activated. If Vendor = Huawei, mark it as abnormal and output related information.

3.28.4 Measures
Recovery measures:
Repair temperature threshold. Since the threshold didn’t open the interfaces publicly, it need “Preventive tool of RHUB3908 Temperature
Unacceptable” to repair. The details can be found in the below link:
http://support.huawei.com/carrier/navi#col=tool/3rdtool&path=CONTOOL-29-7/CONTOOL-000112255/CONTOOL-000125457
3.28.5 Reference
Precaution link: http://support.huawei.com/carrier/docview!docview?nid=SC2000003339
Note: This rule is just for eRAN8.1.
1.48 Notice on Precaution for the Disconnection of LTE FDD eNodeBs
1.48.1 Location

05 Precaution & Rectification Check 01 Precaution Check 08 Notice on Precaution for the Disconnection of LTE FDD eNodeBs
If transmission features are enabled in eNodeB configurations but their corresponding licenses are not applied, the transmission link will be
interrupted and the eNodeB will be disconnected from the M2000. This rule is mainly used to collect eNodeBs’ related information with this risk.
eNodeBs with Disconnection Risk

eNodeB ID eNodeB Name License Identifier Allocated Config Actual Used
62097 62097 LLT1BFD01 0 1 0
1.48.3 Principles
1) Check whether Allocated value of LLT1IPSEC01, LLT1PKI01, LLT1ACB01, LLT1IPIPVS01 or LLT1PPPOE01 is 0 but its corresponding
Configuration value is not 0 from DSP LICENSE. If yes, output its eNodeB ID, eNodeB Name, License Identifier, Allocated, Configuration and
Actual used value.

1.48.4 Measures
Please refer to the precaution link:
http://support.huawei.com/carrier/docview!docview?nid=SE0000676916&partNo=&path=PBI1-7851894/PBI1-21433538/PBI1-7854329/PBI1-
21465979
1.48.5 Reference
None.
Note: This rule is just for eRAN6.0 and eRAN 6.1.
3.29 Notice on Precaution for Decrease in CA UE Handover Success Rate
3.29.1 Location

05 Precaution & Rectification Check 01 Precaution Check 08 Notice on Precaution for Decrease in CA UE Handover Success Rate
During CA UE handover with SCC configuration, C-RNTI conflicted on the target side lead to an eNodeB software processing error, which
further leads to handover command delivery failures, handover failures and decreasing CA UE handover preparation success rate. This rule is mainly used
to collect cells’ related information with this risk.
Abnormal Data
SCC Deterioration Time of CA Deterioration Trend of
eNodeB eNodeB eNodeB Local CA Recommen
Cell Name Handover UE Handover CA UE Handover
ID Name Version Cell ID Switch dation
Switch Preparation Succ Rate Preparation Succ Rate
BTS3900
2014-01-24 10:00:00 -> Refer to the
5013 5013 V100R009C00 0 T-34 ON ON 90.00% -> 70.00%
2014-01-24 12:00:00 precaution
SPC010B022

3.29.3 Principles
1) Check whether CA is enabled from LMT.XML file (if a) or b) is met, it is considered as enabled):
a) Check CAGROUP parameter. If CAGROUP is configured with a value, it indicates a CA group is configured.
b) Check the value of CaAlgoSwitch under ENODEBALGOSWITCH and convert it into a binary number. If bit4 = 1, it indicates FCA is set
to ON.
2) Check whether HoWithSccCfgSwitch (handover with SCC configuration switch) is enabled: Check the value of CaAlgoSwitch and convert it
with a binary number (same with step b) and its bit7 = 1.
3) During the first 3 hours or longer of the traffic measurement collection period, CA UE handover preparation success rate keeps on decreasing.
a) From the original traffic data, get the number of PCC outgoing handover executions of CA UEs (L.HHO.ExecAttOut.CAUser.PCC) and the
number of PCC outgoing handover preparation attempts of CA UEs (L.HHO.PrepAttOut.CAUser.PCC).
b) Use the formula - CA UE handover preparation success rate = (L.HHO.ExecAttOut.CAUser.PCC / L.HHO.PrepAttOut.CAUser.PCC) to get
CA UE handover preparation success rate. In the initial 3 hours or longer of the inspection period, the value of CA UE handover preparation
success rate one hour ago is larger than the value one hour later.
 Number of PCC outgoing handover executions of CA UEs = L.HHO.ExecAttOut.CAUser.PCC;
 Number of PCC outgoing handover preparation attempts of CA UEs = L.HHO.PrepAttOut.CAUser.PCC;
 CA UE handover preparation succ rate = (L.HHO.ExecAttOut.CAUser.PCC/L.HHO.PrepAttOut.CAUser.PCC).
3.29.4 Measures
Disable HoWithSccCfgSwitch: MOD ENODEBALGOSWITCH: CaAlgoSwitch= HoWithSccCfgSwitch~0.
Refer to the precaution link: http://support.huawei.com/carrier/docview!docview?nid=SC2000001204&path=PBI1-7851894/PBI1-
21433538/PBI1-7854329/PBI1-21465979/PBI1-14065
3.29.5 Reference
None.
Note: This rule is just for eRAN7.0 (versions before eRAN7.0 SPC181).

3.30 LTE FDD Precaution Notice - RRC Connection Reestablishment Rejected Due to a PCI Conflict
3.30.1 Location

05 Precaution & Rectification Check 01 Precaution Check 07 LTE FDD Precaution Notice – RRC Connection Reestablishment Rejected Due to a PCI Conflict
If inter-frequency cells served by the same eNodeB are configured with the same PCI and shortMAC-I check is disabled, UEs' RRC connection
reestablishment requests may be rejected, and as a result, UEs intermittently receive signals and user experience is affected. This rule is mainly used to
collect cells’ related information with this risk.
Alarm Caused by Same PCI

eNodeB eNodeB Local Cell Current ShortMAC-I PCI
Recommendation
ID Name Cell ID Name Software Version Check Switch Conflict
LTE FDD Refer to this
5314 5314 0/1 0/1 Off 43
V100R007C00 precaution
3.30.3 Principles
1) Check the value of RsvdSwPara0 under ENBRSVDPARA from LMT.XML file and convert it into a binary number.
a) If bit31 = 1, ReservedSwitchParameter0_bit31 is enabled, which means shortMAC-I check switch is turned on and end.
b) If bit31 = 0, ReservedSwitchParameter0_bit31 is disabled, which means shortMAC-I check switch is turned off and go to step 3).
Note: eRAN6.0 and eRAN6.1 versions don’t need this step.
2) Check all the PhyCellId under CELL in the eNodeB.
a) If PhyCellId parameter is not set to the same values, end.
b) If PhyCellId parameter is set to the same values, it indicates there is a PCI conflict and go to step 3).
3) Counted as abnormal and output cells’ information with same PCI configuration.
3.30.4 Measures
1) For V100R009C00 version, run the following command to enable shortMAC-I check switch: MOD ENBRSVDPARA:
RsvdSwPara0=RsvdSwPara0_bit31-1.
2) For versions earlier than V100R009C00, upgrade the eNodeB to V100R009C00 first. If an eNodeB cannot be upgraded, change the PCIs.
Please refer to precaution link: http://support.huawei.com/carrier/docview!docview?nid=SC2000000885
3.30.5 Reference
None.
Note: This rule is just for eRAN6.0, eRAN6.1 and eRAN7.0.
3.31 Notice on Precaution for Decreasing Handover Success Rate (Only relates to China)
3.31.1 Location

09 Notice on Precaution for Decreasing in Handover Success Rate
(Only relates to China)
None.
3.31.3 Principles
None.
3.31.4 Measures
None.
3.31.5 Reference
None.

1.49 Notice on Precaution for FDD eNodeBs -Disconnected IPSec Tunnels
1.49.1 Location

05 Precaution & Rectification Check 01 Precaution Check 10 Notice on Precaution for FDD eNodeBs-Disconnected IPSEC Tunnels
In eRAN6.0 and eRAN6.1 problem versions (not LMPT), the services or OMCH on the IPSEC transmission channel, or both of them will
become disconnected if the IPSec tunnel cannot be used. This rule is mainly used to collect eNodeBs’ related information if their OMCH used IPSEC
tunnel.
1) Output eNodeBs’ related information (including the version information) if their OMCH used IPSEC tunnel.
eNodeB Information
OMCH
eNodeB eNodeB Check Whether IPSec Policy Negotiation
Using NE Version BTS3202E Version
ID Name Mode of Eudemon Is Template Mode
IPSEC
BTS3202E
62009 990362 Yes V100R010C00SPC200 Check manually
V100R008C00SPC02
1.49.3 Principles
Check whether OMCH uses IPSEC.
1) Check whether SIP has a value under ACLRULE from XML file. If not, print out “OMCH doesn’t use IPSEC”. If yes, go to next step.
2) Check whether there is same SIP address (more than 1 in most cases) under ACLRULE with the source IP address of OMCH. If yes, record its
ACLID and go to next step.
3) Check whether ACLID exits in IPSECPOLICY configuration. If yes, check whether it is the same with step 2)’s ACLID. If yes, it is considered
that OMCH used IPSEC and mark it as abnormal.
4) Collect the information of BTS3202E version: Check the value of SoftWareVersion under NE from XML file. If it contains BTS320E, it
indicates BTS3202E version information.
Note: If the version is not in the designated range, mark it red. The designated range is eRAN8.0 versions before eRAN8.0SPC270 (not
included), eRAN8.1 versions before eRAN8.1SPC290 (not included), eRAN8.0 version before BTS3202E eRAN8.0SPC270 (not included) and eRAN8.1
versions before BTS3202E eRAN8.1SPC200 (not included).

1.49.4 Measures
Set the IPSec policy negotiation mode of Eudemon to a template mode. For detailed operations, contact Huawei Symantec technical support.
Please refer to the precaution link:
http://support.huawei.com/support/pages/kbcenter/view/product.do?
actionFlag=detailManuscript&web_doc_id=SE0000719683&doc_type=TechPost&doc_type=TechPost
1.49.5 Reference
None.
Note: This rule is just for eRAN6.0 and eRAN 6.1.
3.32 Notice on Precaution for Instantaneous CPU Usage Increase Due to Automatic Removal of Neighboring
Cells by Intra-RAT ANR in Full Specification Scenarios
3.32.1 Location

09 Notice on Precaution for Instantaneous CPU Usage Increase Due to Automatic
Removal of Neighboring Cells by Intra-RAT ANR in Full Specification Scenarios
The intra-RAT automatic neighbor relation (ANR) algorithm switch is turned on, the automatic removal of intra-RAT neighboring cells is
enabled, and the number of intra-RAT neighboring cells configured for a local cell reaches the maximum permissible value 256. Under these conditions,
UE handovers trigger the addition of neighboring cells to this local cell and the automatic removal of neighboring cells from this local cell. As a result, the
CPU usage of the LMPT (not the UMPT) increases in a short period of time, which may affect ongoing services. This rule is mainly used to collect
eNodeBs’ information with this risk.
Abnormal Data
eNode eNodeB eNodeB Local Cell MPT IntraRatEve IntraRatAnrA Number of Intra-Freq Number of Inter-Freq Recommen

B ID Name Version Cell ID Name Type ntAnrSwitch utoDelSwitch Neighboring Cells Neighboring Cells dation
BTS3900
Refer to the
5047 5047 V100R009C00 1 Cell1 LMPT On On 2 259
precaution
SPC170
3.32.3 Principles
1) Check MPT’s CN, SRN and SN under DEVIP field from LMT.XML file.
2) Check the corresponding type under the MPT’s CN, SRN and SN. If type = 12289, it indicates that it is a LMPT type and go to next step.
3) Check the value of AnrSwitch under ENODEBALGOSWITCH and convert it into a binary number.
a) If bit0 = 1, IntraRatEventAnrSwitch is ON, which indicates the intra-RAT ANR algorithm switch is turned on.
b) If bit2 = 1, IntraRatAnrAutoDelSwitch is ON, which indicates the automatic removal of intra-RAT neighboring cells is enabled.
 If both a) and b) are met, go to next step, or end.
4) Check EUTRANINTERFREQNCELL and EUTRANINTRAFREQNCELL. If one LocalCellId has 256 different Cellids, which indicates a local
cell reaches the maximum permissible value, mark it as abnormal and output the related information.
3.32.4 Measures
1) To prevent this problem, you are advised to disable the automatic removal of intra-RAT neighboring cells by running the following command:
MOD ENODEBALGOSWITCH: AnrSwitch=IntraRatAnrAutoDelSwitch-0.
2) For V100R009C00SPC230 or later, you are advised to enable the automatic removal of intra-RAT neighboring cells.
Refer to the precaution link: http://support.huawei.com/carrier/docview!docview?nid=SC2000001925&path=PBI1-7851894/PBI1-
21433538/PBI1-7854329/PBI1-21465979/PBI1-14065
3.32.5 Reference
None.

3.33 Notice on Precaution for Flash CSFB Failure Due to RSN Return to Zero After eNodeB Reset
3.33.1 Location

05 Precaution & Rectification Check 01 Precaution Check 11 Notice on Precaution for Flash CSFB Failure Due to RSN Return to Zero after eNodeB Reset
The eNodeB initializes the RIM sequence number (RSN) to zero after being reset and sends a RIM request again. The peer RNC or BSC
considers this RSN to be abnormal and does not respond to the RIM request. As a result, flash CS fall back (CSFB) fails to take effect.
1. If Flash CSFB cannot take effect, CSFB delay increases by 500 ms to 700 ms, which is not perceivable.
2. Huawei RNCs and BSCs can automatically solve this problem 12 hours later. However, it is not clear how other vendors' RNCs and BSCs handle
this problem.
This rule is mainly used to collect cells’ related information with this risk.
1) Output cells' related information with this risk.
Abnormal Data Cause by Flash CSFB Failure

eNo Loc UTRAN GERAN Utran Geran Change
eNo Cell UTRA GERA MME Duration of Change of
deB al CSFB CSFB Neigh Neigh of Recomme
deB Na N RIM N RIM Release the L.FlashCS
Na Cell Steering Steering borin borin L.FlashC ndation
ID me Switch Switch Version Exception FB.E2W
me ID Switch Switch g Cell g Cell SFB.E2G
2014-01-26
Not Refer to
500 B21 Cell Confi Release 12:09:22-> 30.0 ->
0 ON ON config ON ON 2.0 -> 0.0 the
12 4 0 gured 10 2014-01-26 0.0
ured precaution
13:00:00
3.33.3 Principles
1) eNodeB Flash CSFB is enabled: Check the value of HoAlgoSwitch under ENODEBALGOSWITCH from LMT.XML file and convert it
into a binary number. If bit11 = 1, it indicates UtranFlashCsfbSwitch is ON (flash Cs fallback to Utran algorithm switch is turned on). If bit12 = 1, it
indicates GeranFlashCsfbSwitch is ON (flash Cs fallback to Geran algorithm switch is turned on).

2) RIM procedure is started and then the eNodeB is reset.
a) The RIM switch is turned on: Check the value of RimSwitch under ENODEBALGOSWITCH and convert it into a binary number. If
bit0 = 1, it indicates UTRAN_RIM_SWITCH is ON (UTRAN RIM switch is turned on). If bit1 = 1, it indicates GERAN_RIM_SWITCH is ON
(GERAN RIM switch is turned on).
b) External and neighboring UTRAN or GERAN cells are configured:
If Utrancellid under UTRANNCELL has the data, it indicates Utran neighboring cells are configured. If GeranCellId under GERANNCELL has
the data, it indicates Geran neighboring cells are configured.
c) The MME release number of the S1 interface is Release 9 or later: Check the value of MMERelease under S1INTERFACE.
 MMERelease = 1 means the MME release number of S1 interface is Release 9.
 MMERelease = 2 means the MME release number of S1 interface is Release 10.
3) The value of L.FlashCSFB.E2W or L.FlashCSFB.E2G is normal before eNodeB’s reset, but becomes zero after its reset.
a) Get all of alarmid=26213’s occurrence time from event.csv file and record them as the time of eNodeB’s reset.
b) Use the resetting time recorded in a) to check the corresponding value of L.FlashCSFB.E2W and L.FlashCSFB.E2G. There are
L.FlashCSFB.E2W and L.FlashCSFB.E2G > 0 before eNodeB resetting and L.FlashCSFB.E2W and L.FlashCSFB.E2G = 0 after eNodeB
resetting.
4) Output traffic measurement and cells’ related information during the exception occurs.
Note:
 If the cell has several pieces of abnormal data, output the latest one.
 Output related information if UTRAN or GERAN system has the exception.
3.33.4 Measures
1) On the RNC or BSC, initialize the RIM procedure and further initialize the RSN to zero by turning off the RIM switch and then turning it on.
2) On the eNodeB, enable it to send a RIM request again by turning off the RIM switch and then turning it on.
MOD ENODEBALGOSWITCH: RimSwitch = UTRAN_RIM_SWITCH-0&GERAN_RIM_SWITCH-0;
MOD ENODEBALGOSWITCH: RimSwitch = UTRAN_RIM_SWITCH-1&GERAN_RIM_SWITCH-1.
Please refer to precaution link: http://support.huawei.com/carrier/docview!docview?nid=SC2000001950&path=PBI1-7851894/PBI1-21433538/PBI1-
7854329/PBI1-21465979/PBI1-14065

3.33.5 Reference
None.
Note: This rule is just for eRAN6.0, eRAN6.1 and eRAN7.0 (versions before eRAN7.0 SPC230).
1.50 Notice on Precaution for FDD eNodeB- Deterioration of RRC Setup Success Rate and
Other Counters Due to Disabled SRS Configuration (Only relates to China)
1.50.1 Location

12 Notice on Precaution for FDD eNodeB-Deterioration of RRC Setup Success Rate
and Other Counters Due to Disabled SRS Configuration(Only relates to China)
None.
1.50.3 Principles
None.
1.50.4 Measures
None.
1.50.5 Reference
None.

1.51 Notice on Precaution for Occasional UE Access Failure When
IucsRrcRecfgMcCombSwitch Is Set to On
1.51.1 Location

11 Notice on Precaution for Occasional UE Access Failure
When IucsRrcRecfgMcCombSwitch Is Set to On
After the IucsRrcRecfgMcCombSwitch is set to on, an eNodeB determines that GAP information needs to be carried in the first reconfiguration
message, which is sent to a UE during the initial access. However, the eNodeB fails to encode RRC CONN RECFG messages due to internal processing
problems, causing the UE access failure and deterioration of eRAB setup success rate.
1) Output eNodeBs’ information with access failure precaution caused by IucsRrcRecfgMcCombSwitch.
Precaution Caused by IucsRrcRecfgMcCombSwitch

eNodeB eNodeB IucsRrcRecfgMc
Current Software Version Recommendation
ID Name CombSwitch
10.141.7 BTS3900 Continue to investigate signaling of access
30014 On
7.218 V100R009C00SPC150B061 failure UEs and eRAB setup success rate.
1.51.3 Principles
IucsRrcRecfgMcCombSwitch is set to On: Check the value of ProtocolMsgOptSwitch under GLOBALPROCSWITCH from LMT.XML file and
convert it into a binary number. If bit1 = 1, it indicates IucsRrcRecfgMcCombSwitch is set to on.
1.51.4 Measures
Set the IucsRrcRecfgMcCombSwitch to off by running the following command:
MOD GLOBALPROCSWITCH: ProtocolMsgOptSwitch=IucsRrcRecfgMcCombSwitch-0.

1.51.5 Reference
7854329/PBI1-21465979/PBI1-14065
1.52 Notice on Precaution for User Access Failures after the RF Link of a LampSite Base Station
Recovers from an Intermittent Disconnection
1.52.1 Location

13 Notice on Precaution for User Access Failures after the RF link of a
Lampsitebase Station Recovers from an Intermittent Disconnection
If the cell is functioning properly and the physical switch of the TX channel is turned off, users cannot access the LampSite base station after the
RF link of a LampSite base station recovers from an intermittent disconnection. This rule is mainly used to collect cells’ related information with this risk
before V100R008C00SPC300 and V100R009C00SPC150 versions.
1) Output cells’ information with this risk.
Information of Abnormal Cells

eNodeB eNodeB Local Physical Switch of the
Cell Name Cell State
ID Name Cell ID TX Channel
113109 EAF109 1 EAF1091 Normal Off
1.52.3 Principles
1) Run the DSP CELL command to check the cell state. If Cell instance state is Normal, it means the cell is functioning properly and go to next
step.
2) Run the DSP TXBRANCH command to check whether the physical switch of the TX channel on the pRRU to which users cannot access is
turned off.

3) If the cell is functioning properly and the switch is turned off, output this abnormal cell’s information.
1.52.4 Measures
1) Recovery measures: Run the following commands in sequence: DEA CELL (to deactivate the cell) and ACT CELL (to activate the cell).
2) Solutions: Upgrade the LampSite base station to V100R008C00SPC300 or later or upgrade the base station to V100R009C00SPC150 or later.
Precaution link: http://support.huawei.com/carrier/docview!docview?nid=SE0000752511&path=PBI1-7851894/PBI1-21433538/PBI1-
7854329/PBI1-21465979/PBI1-14065
1.52.5 Reference
None.
1.53 Notice on Precaution for Service Interruption Due to a Negotiation Problem When the First
Peer IP Address of a Dual-Homed SCTP Link Is Not Configured at the Peer MME
1.53.1 Location

14 Notice on Precaution for Service Interruption Due to a Negotiation Problem When the
First Peer IP Address of a Dual-Homed SCTP Link Is Not Configured at the Peer MME
When an eNodeB is configured with a dual-homed SCTP link whose first peer IP address is not configured as a local IP address of the link at the
peer MME, the SCTP link status in upper-layer applications is inconsistent with that in the protocol stack if the eNodeB does not receive the last chunk that
indicates successful negotiation within 1 second. As a result, the SCTP link is in the normal state but cannot transmit SCTP_DATA chunks. Services on the
link are then interrupted.
1) Output abnormal eNodeBs’ information.
Abnormal Data

eNodeB eNodeB eNodeB Dual-Homed First Local Second Local First Peer Second Occurrence Time of
Recommendation
ID Name Version Scenario IP IP IP Peer IP S1 Link Fault
BTS3900
173.73.73.8 125.120.12 Continue to
50226 217 V100R009C00 Configured 0.0.0.1 0.120.0.0 2014-01-06 20:12:08
2 0.1 investigate manually.
SPC010B022
1.53.3 Principles
1) The eNodeB is configured with a dual-homed SCTP link:
a) There are several SCTPLNK nodes in LMT.XML file. Take the nodes which their value of SCTPNO parameter are the same with
S1CpBearerId or S1SctpLinkId parameter under S1Interface node from the same LMT.XML file.
b) Check the value of LOCIP, SECLOCIP, PEERIP and SECPEERIP from the nodes selected from a) and all of them are not 0.0.0.0.
2) The eNodeB has active alarm of ALM29201 S1 interface fault: Check whether there is active alarm of Alarm ID = 29201 from alarm.csv
file.
1.53.4 Measures
1) Recovery measures:
Take one of the following measures:
a) Find the faulty SCTP link and reset it at the MME to trigger SCTP link negotiation again.
b) Restart the eNodeB to trigger SCTP link negotiation again.

2) Workarounds:
Take one of the following measures:
a) On the eNodeB, run the MML command MOD SCTPLNK to exchange the values of the first and second peer IP addresses. Alternatively,
run this command to remove the peer IP address that is not configured at the peer MME.
b) On the MME, configure the first peer IP address at the eNodeB as a local IP address of the SCTP link.
1.53.5 Reference
7854329/PBI1-21465979/PBI1-14065
Note: This rule is just for eRAN6.0 and eRAN7.0 (versions before eRAN6.0 SPC350 and eRAN7.0 SPC210).

1.54 Precaution Notice for Lengthy Upgrades of Single-mode LampSite Base Station Where
Each pRRU Connects to an RHUB over Two Ethernet Cables
1.54.1 Location

15 Precaution Notice for Lengthy Upgrades of Single-mode LampSite Base Station
Where Each pRRU Connects to an RHUB over Two Ethernet Cables
If the LampSite is configured as a single-mode base station, each pRRU connects to an RHUB over two Ethernet cables and multiple pRRUs
connect to the same BBU, multiple pRRUs simultaneously start to download the target software from the BBU after running ACT Software command. In
such a case, the downlink HDLC data flow may exceed the CPRI bandwidth limitation, causing packet loss. The BBU needs to wait until all pRRUs
download the software. As a result, the BBU takes a lengthy duration to activate the software (during which services are not interrupted). The pRRU
upgrade process is lengthy, prolonging the overall upgrade duration.
1) Output cells’ information with this risk.
Abnormal Data
eNodeB eNodeB pRRU Connects to the RHUB Single-mode Lampsite
eNodeB Version Recommendation
ID Name Over Two Ethernet Cables Base Station
BTS3900
5013 TMO-5013 YES YES Refer to the precaution
V100R009C00SPC010B022
1.54.3 Principles
1) Each pRRU connects to the RHUB over two Ethernet cables: TT = 2 under RRUCHAIN from LMT.XML file, which means load-sharing (pRRU
connects to the RHUB over two Ethernet cables).
2) The LampSite is configured as a single-mode base station: Peer Standard is NULL or ' ' in the DSP BSSTATUS command output.

1.54.4 Measures
Upgrade the base station to BTS3900 V100R009C00SPC235/BTS3900 V100R010C10SPC120 or its later version.
1.54.5 Reference
21430811/PBI1-21466567/PBI1-21117379
Note: This rule is just for eRAN6.0 and eRAN7.0 (versions before eRAN7.0 SPC235).
1.55 Precaution Notice for Service Unavailability on a Co-MPT UMTS/LTE LampSite Base
Station Using 9.8 Gbit/s Optical Modules
1.55.1 Location

16 Precaution Notice for Service Unavailability on a co-MPT UMTS/LTE
LampSite Base Station Using 9.8 Gbit/s Optical Modules
On a co-MPT UMTS/LTE LampSite base station, if both the baseband processing unit (either LBBPd or WBBPf) and RHUB are configured with
9.8 Gbit/s optical modules and CPRI(Common Public Radio Interface) rate negotiation adopts the default mode (auto-negotiation) or the CPRI rate is
manually set to 9.8 Gbit/s, UMTS and LTE services are unavailable because the WBBPf and LBBPd use a defective chip (SD6601) for allocating CPRI
resources and the chip cannot allocate sufficient resources to guarantee a CPRI rate of 9.8 Gbit/s in co-MPT UMTS/LTE scenarios.
1) Output eNodeBs’ information with this risk.
Result of Optical Modules Configuration Check under Co-MPT UMTS/LTE

eNodeB eNodeB Co-MPT BBP CPRI Bit Rate and Transmission
eNodeB Version BBP Type Recommendation
ID Name or Not Code Rate of RHUB Optical Module
BTS3900
Refer to the
70069 CSPC105 V100R009C00SP YES WD2WBBPF 9.8Gbps
precaution
C210B062

1.55.3 Principles
1) Co-MPT UMTS/LTE: Confirm co-MPT UMTS/LTE deployment is used by MML’s DSP APP command: Application Name has “U” and “L” at
the same time and both of Application State are “Available”.
2) The LBBPd or WBBPf functions as the baseband processing unit: Confirm the LBBPd or WBBPf functions as the baseband processing unit by
MML’s DSP BRDMFRINFO command: For example: Type = WD2LBBPD3 or WD2WBBPf3 and record board’s physical location (CN, SRN
and SN).
3) Baseband processing unit is configured with 9.8 Gbit/s optical modules: Confirm the board from 2)’s CPRI Bit Rate (bit/s) = 9.8G by MML’s
DSP CPRIPORT command.
4) RHUB is configured with 9.8 Gbit/s optical module.
a) Confirm the eNodeB has RHUB board by MML’s DSP BRD command: Config Type = RHUB and record board’s physical location (CN,
SRN and SN).
b) Confirm the board from a)’s optical module transmission code rate (100Mbit/s) = 98 by MML’s DSP SFP command.
1.55.4 Measures
1) If cells configured for a single optical fiber require a total CPRI rate of 4.9 Gbit/s or less, take the following measures:
a) Run the MOD RRUCHAIN command to change the CPRI rate to 4.9 Gbit/s manually. In this step, set Chain No. to the ID of the optical
chain from the baseband processing unit to the RHUB and CPRI Line Rate to 4.9(4.9).
b) Run the RST BRD command to restart the baseband processing unit that connects to fiber optic cables. In this step, set CN, SRN, and SN
based on actual conditions.
2) If cells configured for a single optical fiber require a total CPRI rate beyond 4.9 Gbit/s, distribute excess cells to other optical fibers and manually
change the CPRI link rate after negotiation to 4.9 Gbit/s. This is because a CPRI rate of 9.8 Gbit/s cannot be guaranteed in co-MPT UMTS/LTE
scenarios.
1.55.5 Reference
21430811/PBI1-21466567/PBI1-21117379

1.56 Precaution Notice for Failures in Reaching Peak Uplink Throughput on a LampSite LTE
Base Station
1.56.1 Location

17 Precaution Notice for Failures in Reaching Peak
Uplink Throughput on a LampSite LTE Base Station
In a 20 MHz LTE LampSite, some UEs (UEs using Hisilicon chips) have a limited capability of adjusting delays. If the CPRI_E compression
ratio of involved versions is 3:1 or 4:1, the system timing advance (TA) becomes abnormal, leading to uplink cyclic redundancy check (CRC) errors.
Consequently, the data rate cannot reach the peak uplink throughput. The result of peak throughput tests at the cell center shows that the uplink throughput
is 1 to 3 Mbit/s and 1 to 10 Mbit/s lower than the peak value in LTE TDD mode and LTE FDD mode, respectively.
Cells with Risk
eNodeB ID eNodeB Name Local Cell ID Cell Name Cell Bandwidth CPRI_E Compression Ratio Current Software Version Recommendation
BTS3900 Refer to the

5015 TMO-5015 1 KY5012 20M 3:1
V100R009C00SPC230B022 precaution
1.56.3 Principles
1) Cell downlink bandwidth is 20 MHz: Confirm DlBandWidth = 5 under CELL from LMT.XML file.
Note: 0~ CELL_BW_N6(1.4M), 1~ CELL_BW_N15(3M), 2~ CELL_BW_N25(5M), 3~ CELL_BW_N50(10M), 4~ CELL_BW_N75(15M), 5~ CELL_BW_N100(20M).
2) CPRI_E compression ratio is 3:1 or 4:1: Confirm CpriEthCompressionRatio = 1 or 2 under the same CELL.
Note: 0~ 2_TO_1 (2:1 compression), 1~ 3_TO_1 (3:1 compression), 2~ 4_TO_1 (4:1 compression).
1.56.4 Measures
Run the MOD CELL command to change the CPRI_E compression ratio to 2:1.
The following is an example:

MOD CELL: LocalCellId=0, UlBandWidth=CELL_BW_N100, DlBandWidth=CELL_BW_N100, MultiRruCellFlag=BOOLEAN_TRUE,

MultiRruCellMode=MPRU_AGGREGATION, CpriEthCompressionRatio=2_TO_1, CPRICompression=NORMAL_COMPRESSION.
Note:
If the CPRI_E compression ratio is set to 2:1, the total bandwidth of all networking modes cannot be reached in some networking scenarios.
1.56.5 Reference
21430811/PBI1-21466567/PBI1-21117379
Note: This rule is just for eRAN6.0 and eRAN7.0 (versions before eRAN7.0 SPC235).
1.57 Notice on Precaution for Failures of Cell Activation When Both 1R/2R and 4R Cells Are
Setup on UBBPD6 Baseband (Only relates to China)
1.57.1 Location

18 Notice on Precaution for Failures of Cell Activation When Both 1R/2R
and 4R cells Are Setup on UBBPD6 Baseband (Only relates to China)
None.
1.57.3 Principles
None.
1.57.4 Measures
None.

1.57.5 Reference
None.
1.58 Notice on Precaution for TOD Unusable Caused by USCU Baseband Resetting Which Used Clock
Cascading Scenes (Only relates to China)
1.58.1 Location

19 Notice on Precaution for TOD Unusable Caused by USCU Baseband
Resetting Which Used Clock Cascading Scenes (Only relates to China)
None.
1.58.3 Principles
None.
1.58.4 Measures
None.
1.58.5 Reference
None.

3.34 Notice on Precaution for Occasional Unexpected eNodeB Restarts or Configuration Command
Execution Failure upon Frequent X2 Self-Setups
3.34.1 Location

20 Notice on Precaution for Occasional Unexpected eNodeB Restarts or
Configuration Command Execution Failure upon Frequent X2 Self-Setups
Due to an eNodeB software defect, an error occurs in task scheduling within eNodeBs upon frequent X2 self-setups. As a result, the eNodeBs
restart unexpectedly or MML command execution fails.
The command execution failure has the following impact: eNodeB software cannot be upgraded. The symptom is that the software activation
progress stays at 99%. Operators cannot use MML commands or the CME to modify eNodeB configurations. The following self-organizing network
(SON) procedures fail: X2 self-setup, X2 automatic removal, neighboring cell addition by ANR, and neighboring cell removal by ANR.
1) Output information of abnormal restarts due to frequent X2 self-setups.
Information of Abnormal Restarts upon Frequent X2 Self-Setups

Number of X2 Self- Occurrence Time
eNodeB eNodeB eNodeB Number of User
SCPT Setup of Abnormal Recommendation
ID Name Version Plane Path Fault
Link Fault Switch Restart
BTS3900 Confirm the execution result of
2014-01-25
4210 B4210 V100R009C0 4 5 ON configuration modification
01:19:44
0SPC010B026 commands further.
3.34.3 Principles
1) The eNodeB has abnormal restart: There is Alarm ID = 26213 from event.csv file.
2) The X2 self-setup switch is turned on: Check the value of X2SonSetupSwitch under GlobalProcSwitch from LMT.XML file and
X2SonSetupSwitch = 1.

3) There are 5 alarms (ALM-25952 User Plane Path Fault or ALM-25888 SCTP Link Fault) related to X2 interfaces are active on the eNodeB
within 2 minutes: There is Alarm ID = 25952 or Alarm ID = 25888 from alarm.csv file.
3.34.4 Measures
1) In the case of command execution failure, run the MML command RST BRD to restart the main control board.
2) Clear ALM-25952 User Plane Path Fault and ALM-25888 SCTP Link Fault according to the alarm reference. If the alarms persist for transport
or other reasons, run the MML command ADD X2BLACKWHITELIST to blacklist the associated X2 interfaces, or run the following MML
command to disable X2 self-setup:
MOD GLOBALPROCSWITCH: X2SonSetupSwitch=OFF.
3.34.5 Reference
7854329/PBI1-21465979/PBI1-14065
3.35 Notice on Precaution for UE Access Failures or Releases in Inter-BBP Cells in Certain Scenarios
3.35.1 Location

05 Precaution & Rectification Check 01 Precaution Check 21 Notice on Precaution for UE Access Failure or Release in Inter-BBP Cells in Certain Scenarios
When only three physical cells are established on the secondary BBP of a single frequency network (SFN) cell or multi-MPRU cell, UEs
occasionally fail to access the cells or they are released unexpectedly. To be specific, the value of the counter L.RRC.SetupFail.ResFail.PUCCH, L.E-
RAB.AbnormRel.Radio.DRBReset, or L.E-RAB.AbnormRel.Radio.SRBReset increases unexpectedly.
Cells with Risk

eNodeB eNodeB Local Cell Multi-RRU Cell LBBPD Sector Equipment
Current Software Version Recommendation
ID Name Cell ID Name Mode 3 (group) ID

BTS3900
301 301 0 0 SFN cell 0-0-2 1//2//3 Refer to the precaution
V100R009C00SPC040B022
BTS3900
301 301 1 1 Multi-MPRU cell 0-0-2 3//4//5 Refer to the precaution
V100R009C00SPC040B022
3.35.3 Principles
1) The eNodeB’s BBP type is LBBPD3 and it has more than 2 LBBPD3 by MML’s DSP BRDMFRINFO command: For example: Type =
WD2LBBPD3 and record their physical locations (CN, SRN and SN).
2) The eNodeB has inter-BBP SFN cell or multi-MPRU cell: Check MultiRruCellFlag under CELL from LMT.XML file. If MultiRruCellFlag = 1,
it indicates the eNodeB supports multi-RRU cell. Keep on judging the value of MultiRruCellMode under CELL. If MultiRruCellMode = 0 (SFN
cell) or MultiRruCellMode = 5 (multi-MPRU cell), go to next step, or end.
3) Inter-BBP cell has more than 3 cell sector equipment:
 SFN cell has more than 3 cell sector equipment: SectorEqmId parameter under eUCellSectorEqm from LMT.XML file has more than 3
different values.
 Multi-MPRU cell has more than 3 cell sector equipment: SectorEqmGroupId parameter under eUCellSectorEqm from LMT.XML file has
more than 3 different values.
3.35.4 Measures
1) Deactivate all cells under the eNodeB.
2) Bind an SFN cell or multi-MPRU cell to a specific BBP without establishing such a cell across BBPs. If SFN or multi-MPRU cells have to be
established across BBPs, avoid binding three sector equipment sets or sector equipment groups to one BBP.
ADD BASEBANDEQM: BASEBANDEQMID=X, BASEBANDEQMTYPE=ULDL, UMTSDEMMODE=NULL, SN1=Y; MOD
EUCELLSECTOREQM: LocalCellId=Q, SectorEqmId=Z, BaseBandEqmId=X.
(The above command is applicable for already existed cell’s sector equipment. As far as new adding sector equipment, run ADD
EUCELLSECTOREQM: LocalCellId=Q, SectorEqmId=Z, BaseBandEqmId=X.)
3) Activate all of the cells and check whether risky scenarios exits.
3.35.5 Reference
Precaution link:

14065
3.36 Notice on Precaution for Sleeping Cell by Using Time Synchronous Mode (Only relates to China)
3.36.1 Location

22 Notice on Precaution for Sleeping Cell by Using Time Synchronous Mode
(Only relates to China)
None.
3.36.3 Principles
None.
3.36.4 Measures
None.
3.36.5 Measures
None.
3.36.6 Reference
None.

3.37 LTE FDD Precaution Notice – Resource Leakage for the RRC Connected User License Control Item
3.37.1 Location

23 LTE FDD Precaution Notice -Resource Leakage for the
RRC Connected User License Control Item
When a main control board is shared by LTE TDD and LTE FDD, after accessing an LTE TDD cell (for example, vice versa), a UE is handed
over or re-established to an intra-eNodeB LTE FDD cell (for example, vice versa) and then leaves the LTE FDD cell, resources of the license control item
applied when the UE access the network are not released, resulting in resource leakage. When the leaked resources increase to a certain level, the usage
value of the license control item reaches the upper limit. As a result, ALM-26812 System Dynamic Traffic Exceeding Licensed Limit is reported, and the
E-RAN setup success rate and incoming handover success rate decrease (Before the alarm reported, E-RAN setup success rate and handover success rate
will not be affected).
1) Output the information of abnormal eNodeBs.
Information of Abnormal eNodeBs

Actual Used for Actual Used for
eNode eNodeB S1 Interface
Current Software Version RRC Connected RRC Connected Recommendation
B ID Name User Number
User (FDD) User (TDD)
BTS3900 Check the problem that actual user number is

60222 NB222 300 255 50
V100R009C00SPC010B022 much more than the S1 Interface User Number.
3.37.3 Principles
1) The eNodeB has FDD and TDD cells at the same time, which indicates that there are FddTddInd = 0 and FddTddInd = 1 under CELL from
LMT.XML file.
Note: 0 means CELL_FDD (FDD) and 1 means CELL_TDD (TDD).
2) A is much higher than B:
a) Run the DSP LICINFO command to check the value of Actual Used for RRC Connected User (FDD) and RRC Connected User (TDD). The
sum of them is marked as A.

b) Run the DSP S1INTERFACE command to check the value of total S1 Interface User Number of the eNodeB and mark the value as B.
c) If A>>B (A is much larger than B, such as 10 times), this problem occurs.
3.37.4 Measures
If ALM-26812 System Dynamic Traffic Exceeding Licensed Limit is reported, run the RST BTSNODE command to reset the eNodeB.
If ALM-26812 System Dynamic Traffic Exceeding Licensed Limit is not reported, the fault will be rectified at 3:00 each morning and no
operation is needed.
2) Workarounds:
There is no workaround. You are advised to run the MOD EUTRANINTERFREQNCELL command to disable intra-eNodeB handovers between
LTE TDD cells and LTE FDD cells if the traffic is heavy.
3.37.5 Reference
7854329/PBI1-21465979/PBI1-14065
3.38 Notice on Precaution for Parts of eNodeB resetting Upon Executing Function of Characteristic State
Inquiring in CME (Only relates to China)
3.38.1 Location

24 Notice on Precaution for Parts of eNodeB Resetting Upon Executing
Function Characteristic State Inquiring in CME (Only relates to China)
None.

3.38.3 Principles
None.
3.38.4 Measures
None.
3.38.5 Reference
None.
3.39 Notice on Precaution for Failure in Automatically Removing Faulty X2 Interfaces
3.39.1 Location

05 Precaution & Rectification Check 01 Precaution Check 25 Notice on Precaution for Failure in Automatically Removing Faulty X2 Interfaces
The current automatic removal scheme requires the Neighbor eNodeB ID of the peer eNodeB. This ID can only be obtained from the X2 self-
setup procedure. If the X2 interface has never been successfully set up, the local eNodeB cannot obtain the peer eNodeB ID. As a result, the faulty X2
interface cannot be automatically removed and the alarm persists.
1) Output information of faulty X2 interfaces.
Information of Faulty X2 Interfaces

eNodeB eNodeB X2 SON Delete X2 SON Delete Neighbor Neighbor eNodeB
eNodeB Version X2 Interface ID Recommendation
ID Name Switch Time eNodeB ID PLMN ID
BTS3900
MCC:302
60058 eNB210 V100R009C00S 1 ON 3600 30010 Refer to the precaution
MNC:610
PC150B066

3.39.3 Principles
1) Judge whether X2 SON Delete Switch is turned on: Check the value of X2SonDeleteSwitch under GlobalProcSwitch, convert it into a binary
number and its bit0 = 1. Output the value of X2SonDeleteTimerforX2Fault at the same time.
2) Check whether there is alarmid=29204 (X2 Interface Fault alarm) from Alarm.csv file and record the value of X2 Interface ID in
Locationinformation.
3) Run the DSP X2INTERFACE command to query the values of Neighbor eNodeB ID and Neighbor eNodeB PLMN ID. If X2InterfaceId equals
X2 Interface ID from 2) and both Neighbor eNodeB ID and Neighbor eNodeB PLMN ID are NULL, this X2 interface cannot be automatically
removed. Mark it as abnormal and output its information.
3.39.4 Measures
Refer to the recovery measures in the below link to delete X2 interfaces manually.
3.39.5 Reference
7854329/PBI1-21465979/PBI1-14065
3.40 Notice on Precaution for Parts of Counters Deterioration Due to Enabled DRX (Only relates to China)
3.40.1 Location

26 Notice on Precaution for Parts of Counters Deterioration
Due to Enabled DRX (Only relates to China)
None.

3.40.3 Principles
None.
3.40.4 Measures
None.
3.40.5 Reference
None.
3.41 Precaution Notice for a Cell Establishment Failure Because Sector Equipment Is Not Added to a Sector
Equipment Group of the Cell
3.41.1 Location

27 Precaution Notice for a Cell Establishment Failure Because Sector
Equipment Is Not Added to a Sector Equipment Group of the Cell
A multi-MPRU-aggregation cell is configured with a set of sector equipment that is not added to any sector equipment group of the cell, which
will cause internal processing problems and establishment failure of multi-MPRU-aggregation cell (Upgrade scenarios: The cell cannot be activated after
the LampSite base station is upgraded to one of the versions involved in this precaution notice. New networks: The cell cannot be activated when the
LampSite base station of a version involved in this precaution notice is deployed.).
1) Output cells’ related information with this exception.
Abnormal Data
eNodeB Local Cell CpriEthComp Recommend
eNodeB ID eNodeB Version MultiRruCellMode SectorEqmId
Name Cell ID Name ressionRatio ation
53818 53818 0 cell0 BTS3900 multi-MPRU- 3:1 0 Refer to the
V100R009C00SPC010B02 aggregation cell precaution

3.41.3 Principles
Check whether the cell satisfies all of the following conditions from XML file.
1) The cell is a multi-MPRU-aggregation cell: Check the value of MultiRruCellMode under CELL and MultiRruCellMode = 5.
2) CpriEthCompressionRatio is 3:1 or 4:1: Check the value of CpriEthCompressionRatio under CELL and CpriEthCompressionRatio = 1 or 2.
3) The multi-MPRU-aggregation cell is configured with a set of sector equipment: Check the value of SectorEqmId under EUCELLSECTOREQM
and record the values to group A.
4) All sector equipment groups of the cell but excludes the sector equipment queried in 3): Check the value of SectorEqmId under
EUSECTOREQMGROUP and record the values to group B. Output the values that belong to group A but not in group B.
3.41.4 Measures
Recovery measures:
1) Deactivated the multi-MPRU-aggregation cell: DEA CELL: LocalCellId=X;
2) Remove the sector equipment configured for the multi-MPRU-aggregation cell, and then add this sector equipment to a sector equipment group
for the cell: RMV EUCELLSECTOREQM: LocalCellId=X, SectorEqmId=Y; ADD EUSECTOREQMID2GROUP: LocalCellId=X;
SectorEqmGroupId=Z, SectorEqmId=Y;
3) Activate the multi-MPRU-aggregation cell: ACT CELL: LocalCellId=X.
3.41.5 Reference
21430811/PBI1-21466567/PBI1-21117379
Note: This rule is just for eRAN7.0 (versions before eRAN7.0 SPC160) and eRAN8.1 (versions before and eRAN8.1 SPC250).

3.42 Notice on Precaution - Resetting Main Control Board Affects GSM Service Due to LTE Transmission
Interrupted over 45 minutes on Dual-Mode Base Station of SingleRAN 3900 Series (Only relates to
China)
3.42.1 Location

28 Notice on Precaution – Resetting Main Control Board Affects GSM Service Due to LTE Transmission
Interrupted over 45 minutes on Dual-mode Base Station of SingleRAN 3900 Series (Only relates to China)
None.
3.42.3 Principles
None.
3.42.4 Measures
None.
3.42.5 Reference
None.

3.43 Notice on Precaution for FDD eNodeB - Reduced Uplink Rate of Test User Due to Enabled Uplink
Scheduler Ctrl Power Switch (Only relates to China)
3.43.1 Location

29 Notice on Precaution for FDD eNodeB - Reduced Uplink Rate of Test User
Due to Enabled Uplink Scheduler Ctrl Power Switch (Only relates to China)
None.
3.43.3 Principles
None.
3.43.4 Measures
None.
3.43.5 Reference
None.
3.44 Notice on Precaution for Frequently Deactivated Supplementary Carrier When SLTE_CA UE Executes
CA Services (Only relates to China)
3.44.1 Location

05 Precaution & Rectification Check 01 Precaution Check 08 Notice on Precaution for Frequently Deactivated Supplementary Carrier

When SLTE_CA UE Executes CA Services (Only relates to China)
None.
3.44.3 Principles
None.
3.44.4 Measures
None.
3.44.5 Reference
None.
3.45 Precaution Notice for Occasional Network Access Failure after Offline FFT Frequency Scan Ends
3.45.1 Location

05 Precaution & Rectification Check 01 Precaution Check 09 Precaution Notice for Occasional Network Access Failure after Offline FFT Frequency Scan Ends
After offline FFT frequency scan ends, the pRRU, due to a software defect, occasionally indicates cell resource availability although cell
resources are not available yet. Consequently, the cell cannot provide services during the problem period. This rule is mainly used to collect information of
eNodeBs with this risk.
Abnormal Data
eNodeB ID eNodeB Name eNodeB Version Recommendation
300 2T8R BTS3900 Refer to the precaution
V100R010C00SPC000B07

3.45.3 Principles
Check SWVERSION under NE from LMT.XML file. If it is BTS3900 V100R010C00 versions (before BTS3900 V100R010C00SPC250) or
BTS3900 V100R010C10 versions (before BTS3900 V100R010C10SPC160), mark it as abnormal and output related eNodeBs’ information, or end.
3.45.4 Measures
1） Recovery measures:
Run MML commands to first deactivate the problem cell and then activate it by the following command.
LTE FDD: DEA CELL + ACT CELL
2） Workarounds
Disable offline FFT frequency scan, and then activate the concerned cell.
3） Solutions
Upgrade the base station to BTS3900 V100R009C00SPC250/BTS3900 V100R010C10SPC160 or later, which have solved this problem already.
3.45.5 Reference
21430811/PBI1-21466567/PBI1-21117379
3.46 Precaution Notice for FDD eNodeB – Disable SysTimeCfgInd While Clock Synchronization Mode Is Set
to FREQ (Only relates to China)
3.46.1 Location

20 Precaution Notice for FDD eNodeB – Disable SysTimeCfgInd While
Clock Synchronization Mode Is Set to FREQ (Only relates to China)

None.
3.46.3 Principles
None.
3.46.4 Measures
None.
3.46.5 Reference
None.
3.47 Precaution Notice for Abrupt Uplink Interference Increase on LampSite LTE Base Stations
3.47.1 Location

05 Precaution & Rectification Check 01 Precaution Check 31 Precaution Notice for Abrupt Uplink Interference Increase on LampSite LTE Base Stations
Due to uplink path loss changes or channel fading, certain UEs encounter uplink SINR deterioration and need to increase their transmit power
under closed-loop power control. If the power saturation protection mechanism fails, the pRRUs cannot control the maximum UE transmit power and their
received power occasionally exceeds the saturation power, causing abrupt increase in uplink interference, access exceptions and low RRC connection setup
success rate. This rule is mainly used to collect information of eNodeBs’ related information with this risk.
1) Output risky eNodeBs’ eNodeB ID, eNodeB name, eNodeB version, hardware version, PuschRsrpHighThdSwitch and so on.
Abnormal Data
eNodeB Local PuschRsrpHighT

eNodeB ID Cell Name CN SRN SN eNodeB Version Hardware Version
Name Cell ID hdSwitch
BTS3900 MPRU.HWEI.x701
60164 eNodeB26 1 CELL1 0 62 0 Off
V100R009C00SPC 20001

160B022
3.47.3 Principles
A LampSite base station that meets both the following conditions is subject to the problem.
1) Check pRRU’s hardware version on the LampSite base station by DSP BRDVER command: Check the Hardware Version field.
a) Current software version is V100R010C10SPCXXX and hardware version is one of MPRU.HWEI.x00120105, MPRU.HWEI.x00120200,
MPRU.HWEI.x60120000 or MPRU.HWEI.x70120001.
b) Current software version is V100R009C00SPCXXX and hardware version is one of MPRU.HWEI.x00120105, MPRU.HWEI.x00120200,
MPRU.HWEI.x40120000, MPRU.HWEI.x60120000 or MPRU.HWEI.x70120001.

2) Record pRRU’s CN, SRN and SN which meets the conditions described above.
a) Find SECTOREQMID under SECTOREQM from LMT.XML file and record them.
b) Check EuSectorEqmGroup field from LMT.XML file, which contains the SectorEqmId from a).
c) Check CELLALGOSWITCH from configuration file, find LocalCellId which is the same with b), and check PuschRsrpHighThdSwitch
under UlPcAlgoSwitch. If PuschRsrpHighThdSwitch is turned off, this problem will be triggered.
d) Output risky eNodeBs’ eNodeB ID, eNodeB name, eNodeB version, local cell ID, cell name, hardware version and
PuschRsrpHighThdSwitch.
3.47.4 Measures
1) Enable the high RSRP threshold: MOD CELLALGOSWITCH: LocalCellId=XXX, UlPcAlgoSwitch=PuschRsrpHighThdSwitch-1;
2) Configure the high RSRP threshold for PUSCH closed-loop power control. The configuration takes effect only when the
PuschRsrpHighThdSwitch is turned on: MOD CELLPCALGO: LocalCellId=XXX, PuschRsrpHighThd =-90.
3.47.5 Reference
http://support.huawei.com/carrier/docview!docview?nid=SC2000003758&path=PBI1-7851894/PBI1-21430741/PBI1-21430811/PBI1-
21466567/PBI1-21117379
Note: This rule is just for eRAN7.0 (versions before eRAN7.0SPC290) and eRAN8.1 (versions before eRAN8.1 SPC220).

3.48 Notice on Precaution for Invalid SYNCETH Clock When the Clock Working Mode Parameter Is Set to
AUTO in a Base Station
3.48.1 Location

19 Notice on Precaution for Invalid SYNCETH Clock When the Clock
Working Mode Parameter Is Set to AUTO in a Base Station
When the clock working mode parameter is set to AUTO in a base station and the main control board resets because the base station resets or is
upgraded, the SYNCETH clock selection will fail. Because after a main control board resets, its original configurations are restored but the configuration
status of the SYNCETH clock is not updated (that is, the SYNCETH clock is not configured). In this case, reference clock selection fails because only a
configured reference clock can be selected. Reference clock selection certainly fails on an UMPTb. There is a low probability that reference clock selection
fails on a WMPT, LMPT, or UMPTa. If a base station does not synchronize with the external reference clock for 90 days, ongoing services carried by the
base station will be affected and no alarm is reported. This rule is mainly used to output risky eNodeBs’ information.
1) Output risky eNodeBs’ related information.
Abnormal Data
eNodeB eNodeB Clock Source Clock Working Current Clock
eNodeB Version CN SRN SN
ID Name Type Mode Source
BTS3900 SyncEth
393684 -393684-OF 0 0 7 AUTO GPS Clock
V100R010C10SPC120 Clock
3.48.3 Principles
1） Check the SWVERSION parameter under NE from LMT.XML file. If SWVERSION = V100R010C10 versions before BTS3900
V100R010C10SPC190 (not included), go to next step, or end.
2） Check MODE parameter under TASM from LMT.XML file. If MODE = 0 (AUTO), go to next step, or end.
3） Check clock source type and clock source state by MML’s DSP CLKSRC command. If Clock Source Type = SyncEth clock and Clock Source
State = Available, mark it as abnormal and output this cell’s related information.

3.48.4 Measures
1） Workarounds:
Run the following command to set the Clock Working Mode parameter to MANUAL (Manual):
SET CLKMODE: MODE=MANUAL, CLKSRC=SYNCETH;
2） Solutions:
Upgrade the eNodeB to BTS3900 V100R010C10SPC190 or its later version.
3.48.5 Reference
7275801/PBI1-21465984/PBI1-13751
3.49 Notice on Precaution for LTE FDD eNodeBs – MML Command Execution Failures After an eNodeB
Reset or Configuration Reactivation in Massive X2 Links Scenarios
3.49.1 Location

20 Notice on Precaution for LTE FDD eNodeBs-MML Command Execution Failures
After an eNodeB Reset or Configuration Reactivation in Massive X2 Links Scenarios
When an eNodeB is configured with more than 220 X2 links, internal resources fail to be obtained during configuration synchronization due to
exceedingly large internal message overhead. This rule is mainly used to output eNodeBs’ information with this risk.
1) Output eNodeBs’ information if they may have MML command execution failures.
eNodeBs May Have MML Command Execution Failures

eNodeB eNodeB MPT BBP Number of Configured Did Configuration File
Recommendation
ID Name Type Type X2 Links Damaged Report or Not
eNodeBs may have
4G-
4503 UMPT UBBP 221 Yes MML command
4503
execution failures.

2) Output eNodeBs’ information which may have MML command execution failures after resetting.
eNodeBs May Have MML Command Execution Failures After Resetting

eNodeB MPT BBP Number of Did Configuration File
Recommendation
Name Type Type Configured X2 Links Damaged Report or not
eNodeBs may have MML command
4G_4400 UMPT UBBP 221 No
execution failures after resetting.
3.49.3 Principles
1) “eNodeBs may have MML command execution failures” table:
a) Running MML’s DSP BRDVER command to check whether the eNodeB is equipped with UMPT and UBBP board. If yes, go to next step,
or end.
b) Count the number of X2InterfaceId under X2INTERFACE from configuration file. If it is more than 220, go to next step, or end.
c) Check event.csv file to record last NE restarting time.
d) In alarm.csv file, check whether Alarm ID =26242 (Configuration File Damaged) occurs after the time recorded in c). If yes, output the
exception, or end.
2) “eNodeBs may have MML command execution failures after resetting” table:
a) According to step1)’s a) and b) to check and output eNodeBs’ information with more than 220 X2InterfaceId.
3.49.4 Measures
a) Run the RST APP command to reset the eNodeB.
b) Deliver the MOD ENODEBFUNCTION: UserLabel="test" command to the eNodeB when it works properly. If the execution is successful,
the problem is solved.
Note: After the command is executed successfully, restore the eNodeB configuration to the state before the command execution. Resetting the
eNodeB is not a recommended measure to solve the problem because the problem may be triggered again during an eNodeB reset.
2） Solutions:
Upgrade the eNodeB to V100R010C10SPC250 or later.

3.49.5 Reference
Precaution link:
14065
3.50 Notice on Precaution for Repeated BBP Restarts in FDD eNodeBs Due to Subscription to the
PERIOD_CELL_L2_MR Message for Cell-Level External CHR Tracing
3.50.1 Location

21 Notice on Precaution for Repeated BBP Restarts in FDD eNodeBs Due to Subscription
to the PERIOD_CELL_12_MR Message for Cell_Level External CHR Tracing
After the PERIOD_CELL_L2_MR message was subscribed to for cell-level external CHR tracing, an error occurred in internal message
processing when UEs were performing services. This resulted in the unexpected BBP restarts. This rule is mainly used to output eNodeBs’ information
with this risk.
Abnormal Data
eNodeB ID eNodeB Name eNodeB Version Recommendation
BTS3900 Check whether PERIOD_CELL_L2_MR message was
90964 0000_BWTWN203201
V100R010C10SPC160 subscribed to for cell-level external CHR tracing manually.
3.50.3 Principles
1) Check SWVERSION parameter under NE from LMT.XML. If SWVERSION is one of BTS3900 V100R010C10 SPC220 and its earlier
BTS3900 V100R010C10 versions or BTS3202E V100R010C10 SPC220 and its earlier BTS3202E V100R010C10 versions, go to next step, or
end.
2) Mark it as abnormal and output related information.

3.50.4 Measures
Unsubscribe from the PERIOD_CELL_L2_MR message for cell-level external CHR tracing.
2） Solutions:
a) For Macro & LampSite: Upgrade eNodeBs to BTS3900 V100R010C10SPC250 or later BTS3900 V100R010C10 versions.
b) For BTS3202E: Upgrade eNodeBs to BTS3202E V100R010C10SPC250 or later BTS3202E V100R010C10 versions.
3.50.5 Reference
Precaution link:
14065
3.51 Notice on Precaution for Switchback to the Faulty Primary IPsec Tunnel
3.51.1 Location

05 Precaution & Rectification Check 01 Precaution Check 22 Notice on Precaution for Switchback to the Faulty Primary IPsec Tunnel
If the eNodeB is enabled with the IPsec tunnel pair switchback function, the IPsec tunnel switches to the secondary tunnel when the primary
tunnel is faulty. When the primary tunnel is restored, the IPsec tunnel automatically switches back to the primary tunnel even if the primary tunnel becomes
faulty again during the time waiting for a switchback (120s by default), and cannot switch to the secondary tunnel again. As a result, services and OM
channel are affected. This rule is mainly used to output eNodeBs’ information with this risk.
1） Output eNodeBs’ information with this risk.
Abnormal Data
IPSec Dual Tunnel Recommend
eNodeB ID eNodeB Name eNodeB Version
Switch Back ation

0000_BWTWN2 BTS3900 Refer to the

90964 On
03201 V100R010C10SPC160 precaution.
3.51.3 Principles
1) Check SWVERSION parameter under NE from LMT.XML. If SWVERSION is one of BTS3900 V100R010C10SPC160, BTS3900
V100R010C10SPC180, BTS3900 V100R010C10SPC190, BTS3900 V100R010C10SPH195, BTS3900 V100R010C10SPH196, BTS3900
V100R010C10SPH197 or BTS3900 V100R010C10SPC220, go to next step, or end.
2) Check IPSECSWITCHBACK parameter under IPSECDTNL from LMT.XML. If IPSECSWITCHBACK = 1(ON), mark it as abnormal and
output related information.
3.51.4 Measures
Run the following command to disable the IPsec tunnel pair switchback function.
MOD IPSECDTNL: DUALID=0, IPSECSWITCHBACK=OFF.
2） Solutions:
a) If only services are interrupted, reset the eNodeB using the U2000.
b) If both services and the maintenance link are interrupted, and the transmission link fault rectification function is enabled, the eNodeB can
recover through a self-reset.
c) If only the maintenance link is interrupted, reset the eNodeB on the connected peer end.
d) Otherwise, reset the eNodeB locally.
3.51.5 Reference
Precaution link:
14065

3.52 Notice on Precaution for Exceptions Occurred after Synchronizing SON Logs of FDD eNodeBs on the
U2000
3.52.1 Location

05 Precaution & Rectification Check 01 Precaution Check 23 Notice on Precaution for Exceptions Occurred after Synchronizing SON Logs of FDD eNodeBs on the U2000
If this risk occurs,
 Some counters used for traffic measurement are occasionally abnormal, the actual values cannot be viewed, that is, the traffic statistics in the
abnormal period cannot be restored.
 The configuration file is occasionally corrupted, and eNodeB configurations are lost and ongoing services are interrupted after the eNodeB is
reset.
 Board reset occasionally occurs. As a result, eNodeB services are interrupted for a short period.
This rule is mainly used to output cells’ information with this risk.
1) Output cells’ related information with enabled neighboring cell classification management switch.
Check Result of Neighboring Cell Classification Management Switch

eNodeB Local Cell Neighboring Cell Classification
eNodeB Version Recommendation
Name Cell ID Name Management Switch
BTS3900 94738- Turn off neighboring cell classification management
94738-OF 1 ON
V100R010C10SPC120 1-OF switch, or disable the SON log synchronization function.
3.52.3 Principles
1） Check SWVERSION parameter under NE from LMT.XML. If SWVERSION is BTS3900 V100R010C10SPC250 or earlier BTS3900
V100R010C10 versions, go to next step, or end.
2） Check bit0 (INTRA_RAT_NCELL_CLASS_SW) of NCellClassMgtSw parameter under CELLALGOSWITCH from LMT.XML. If bit0 = 1, it
indicates INTRA_RAT_NCELL_CLASS_SW is turned on, mark it as abnormal and output related information.
3.52.4 Measures
Back up the eNodeB configuration file on the U2000 at first. After the configuration file passes the verification on the CME, download it to the
eNodeB and activate the configuration file again.
2) Workarounds:
(Recommended) Method 1:
Run the following command to disable the neighboring cell classification management switch on the eNodeB:
MOD CELLALGOSWITCH: LocalCellId=XXX, NCellClassMgtSw=INTRA_RAT_NCELL_CLASS_SW-0;

(Optional) Method 2:
In the OSMU management system of the U2000, disable the SON log synchronization function by setting LTE_SON_Log_Management to
Disable.
3) Solutions:
Upgrade the eNodeB to BTS3900 V100R010C10SPC255 or a later version.
3.52.5 Reference
7854329/PBI1-21465979/PBI1-14065
3.53 Notice on Precaution for Restart of FDD eNodeBs That Select Target Frequencies in a Round Robin
Manner during Blind Redirections for CSFB to UTRAN
3.53.1 Location

24 Notice on Precaution for Restart of FDD eNodeBs That Select Target Frequencies in
a Round Robin Manner during Blind Redirections for CSFB to UTRAN
On eNodeBs in which the function of selecting target frequencies in an RR manner during blind redirections for CSFB to UTRAN is enabled,
errors occur when the eNodeBs select neighboring UTRAN cells or frequencies in the event of CSFB protection timer expiration. In such a case, the slave-

core processes of the UMPT/UBBP and the eNodeB equipped with an LMPT restart and services are interrupted.
1） Output eNodeBs’ information with this risk.
Abnormal Data
CSFB to UTRAN Blind
eNodeB ID eNodeB Name eNodeB Version
Redirection RR Switch
BTS3900
393248 393248 ON
V100R010C10SPC120
3.53.3 Principles
Check the following parameters from LMT.XML file:
a) For V100R009C00 versions before BTS3900 V100R009C00SPC290: RsvdSwPara1_bit21 is turned on. Check the value of RsvdSwPara1 under
ENBQCIRSVDPARA, convert it into a binary number and bit21 = 1.
b) For V100R010C10 versions before BTS3900 V100R010C10SPC255: CSFB to UTRAN Blind Redirection RR Switch is turned on. Check the
value of UtranCsfbBlindRedirRrSw under CSFALLBACKBLINDHOCFG and UtranCsfbBlindRedirRrSw=1.
3.53.4 Measures
1） Workarounds:
a) For BTS3900 V100R009C00 version: Disable ENBRSVDPARA. RsvdSwPara1_bit21 by the following command.
MOD ENBRSVDPARA: RsvdSwPara1=RsvdSwPara1_bit21-0.
b) For BTS3900 V100R010C10 version: Disable CSFB to UTRAN Blind Redirection RR Switch by the following command.
MOD CSFALLBACKBLINDHOCFG: CnOperatorId = 0, UtranCsfbBlindRedirRrSw = OFF.
c) After disabling RsvdSwPara1_bit21 or CSFB to UTRAN Blind Redirection RR Switch, corresponding function can be replaced by the
following switch: Enable ENBRSVDPARA. RsvdSwPara1_bit23 instead by the command listed below for BTS3900 V100R009C00 and
BTS3900 V100R010C10.
MOD ENBRSVDPARA: RsvdSwPara1= RsvdSwPara1_bit21-0 & RsvdSwPara1_bit23-1.
2） Solutions:
Upgrade V100R009C00 version to V100R009C00SPC290 or later V100R009C00 version; Upgrade V100R010C10 version to
V100R010C10SPC255 or later V100R010C10 version.

3.53.5 Reference
http://support.huawei.com/carrier/docview!docview?nid=SC2000004236&path=PBI1-7851894/PBI1-21433538/PBI1-7854329/PBI1-
21465979/PBI1-14065
Note: This rule is just for eRAN7.0 (versions before eRAN7.0 SPC290) and eRAN8.1 (versions before eRAN8.1SPC255).
3.54 Accident Recovery Information Statistic
3.54.1 Location

06 Accident Inspection Scene 01 Accident Risk Check 01 Accident Recovery Information Statistic
This rule is mainly used to collect information of accident recovery. You can understand the accident recovery information in the entire network
through this rule.
1) Output the number of eNodeBs having accident recovery information.
Accident Recovery Information Statistic( eNodeB number)

SSL SSL SSL SSL SSL IKE AUTH IKE
PACKETFIL PACKETFIL OMC
Connectio Connectio Connection Authentica Authentica METH AUTHMETH
TERSWITCH TERSWITCH H(SLA
n Type n Type and Disabled tion Mode tion Mode (PRE_SHARED (IKE_RSA_SI
(DISABLE ) (ENABLE) VE)
(All) (SSL) ISENABLE (NONE) (PEER) _KEY) G)
0 2 1 1 1 0 4 2 0 0
Note: This table only list parts of counters. It also includes VLANMAP (NONE), VLANMAP (SINGLEVLAN), VLANMAP (SINGLEVLAN and
VLANGROUP), OMCH using IPSEC and Default Router is All Zero.
2) Output eNodeBs’ related information with accident recovery information.
Accident Recovery Information Statistic (All)

SSL SSL IKE PACKETFIL OMCH Default
eNode eNodeB ISENA APPC OMCH( VLAN
Connectio Authenticati AUTHM TERSWITC Using Router is
B ID Name BLE ERT SLAVE) MAP
n Type on Mode ETH H IPSEC All Zero
200 230 SSL ENAB NONE IKE_RS appcert DISABLE Master SINGLE No No

LE A_SIG .pem VLAN

DISAB IKE_RS appcert SINGLE
4210 B4210 SSL PRRE DISABLE Master No No
LE A_SIG .pem VLAN
3.54.3 Principles
Check whether there is corresponding configuration from XML file.
1) Collect the information of SSL connection type and SSL authentication mode:
a) Check the value of CONNTYPE (Connection type) under SSL from XML file and count the number of eNodeBs with different values
(CONNTYPE = 0 means ALL and CONNTYPE = 1 means only SSL).
b) Check the value of ISENABLE under CERTCHKTSK and count the number of eNodeBs with CONNTYPE = 1(only SSL connection) and
ISENABLE = 0 (The task of checking the certificate validity is disabled).
c) Check the value of AUTHMODE (Authentication Mode) under SSL from XML file and count the number of eNodeBs with different values
(AUTHMODE = 0 means NONE (Verify None) and AUTHMODE = 1 means PRRE (Verify Peer Certificate)).
2) Collect information of IKE authentication method.
a) Check the value of AUTHMETH (Authentication Method) under IKEPROPOSAL from XML and count the number of eNodeBs with
different values (AUTHMETH = 8 means PRE_SHARED_KEY and AUTHMETH = 9 means IKE_RSA_SIG).
3) Check whether PACKETFILTERSWITCH is configured.
a) Check the value of PACKETFILTERSWITCH and count the number of eNodeBs with different values (PACKETFILTERSWITCH = 0
means DISABLE and PACKETFILTERSWITCH = 1 means ENABLE).
4) Check whether active/standby OMCH is configured.
a) Check the value of FLAG (active/standby state) under OMCH from XML file and count the number of eNodeBs with different values
(FLAG = 0 means MASTER state and FLAG = 1 means SLAVE state).
5) Collect the information of the VLANMAP configuration.
a) Check the value of VLANMODE under VLANMAP from XML file and count the number of eNodeBs with different values (VLANMODE
= 0 means SINGLEVLAN and VLANMODE = 1 means VLANGROUP. If it is vacant, output “NONE”. If there are more than one
VRFIDX with different VLANMODEs, count it as “SINGLEVLAN and VLANGROUP”).
6) Check whether OMCH used IPSEC.
a) Check whether SIP has a value under ACLRULE from XML file. If not, print out that “OMCH didn’t use IPSEC”. If yes, go to next step.
b) Check whether SIP (more than one in most cases) under ACLRULE is the same with SRCIP of OMCH. If yes, record its ACLID and go to

next step.
c) Check whether there is ACLID under IPSECPOLICY. If yes, check whether it is the same with last step’s ACLID. If yes, it is considered
that OMCH used IPSEC.
7) Collect information of APPCERT.
a) Check the APPCERT (Appcert File Name) under CERTMK from XML file and output its content, which can be more than one value.
3.54.4 Measures
None.
3.54.5 Reference
None.
3.55 X2 Interface Configuration Check
1.58.6 Location

06 Accident Inspection Scene 01 Accident Risk Check 02 X2 Interface Configuration Check
For versions before V100R008C00SPC200, if there are more than 64 X2 interfaces, the cell will be out of service and the activation will fail after
eNodeB resetting. For all versions without X2 interface, they can’t reset the neighbor eNodeBs by X2 interface. This rule is mainly used to collect
eNodeBs’ related information with these exceptions.
1) Output the number of eNodeBs configured with X2 interface in the entire network.
X2 Interface Config Check (eNodeB Number)

Number of Used X2 Interface eNodeB Number (Total) eNodeB Number (Abnormal)
0 1 1
1-30 3 0
31-64 5 0
65-96 4 1
97-128 1 0

>128 0 0
Note: “eNodeB Number (Abnormal)” column is just for eRAN6.0 version and “eNodeB Number (Total)” column is named as “eNodeB Number”
in other versions.
2) Output eNodeBs’ related information without X2 interface.
No X2 Interface
eNodeB ID eNodeB Name Number of X2 Interfaces X2 Son Setup Switch
62201 62201 0 ON
3) Output TOP20 eNodeBs’ related information with most X2 interfaces.
X2 Interface Configuration Check (TOP20)

eNodeB ID eNodeB Name Number of X2 Interfaces X2 Son Setup Switch
62085 62085 99 ON
62009 62009 78 ON
Note: eRAN6.1 and later versions only output table 1 and 2 and will not mark it red or abnormal if the number of X2 interface is more than 64.
1.58.8 Principles
Check whether there is X2interface field from LMT.XML file. If yes, count their number to judge whether they are more than the threshold
configured by corresponding version.
1) Check whether there is X2interface field from LMT.XML file. If yes, go to next step, or end.
2) Count the number of X2interface under each eNodeB.
a) Count the number of eNodeBs with their X2InterfaceId between 0, [1, 30], [31, 64], [65, 96], [97, 128], (128,+∞) range, output the result to
the table “X2 Interface Configuration Check (eNodeB Number)” and set the number of eNodeBs without X2 interface as the number of
exceptions.
Note: For versions before eRAN6.0 SPC200, if the number of X2 interface is 0 or more than 64, mark it red and abnormal and count the number
of abnormal eNodeBs as the number of exceptions.
b) Output eNodeBs’ eNodeB ID, eNodeB name and the number of X2 interfaces to the “No X2 Interface” table if the eNodeB wasn’t
configured any X2 interfaces.
c) Based on the number of X2 interfaces, output TOP20 eNodeBs’ eNodeB ID, eNodeB name and the number of X2 interfaces with a
descending order.
3) For eNodeBs outputted into the tables, check their states of X2 son setup switch: Check X2SonSetupSwitch field from LMT.XML file. If
X2SonSetupSwitch = 0, it indicates the switch is turned off. If X2SonSetupSwitch = 1, it indicates the switch is turned on. Output the results into

the tables.
1.58.9 Measures
1) For versions before V100R008C00SPC200: When the number of X2Interface is more than 64, run “RMV X2INTERFACE: X2InterfaceId=XX”
manually to make sure the number of X2Interface is less than 64.
2) If the number of X2Interface is 0, run “ADD X2INTERFACE” command.
1.58.10 Reference
Please refer to the below link: http://3ms.huawei.com/hi/group/2030853/thread_4157813.html?
mapId=3325661&for_statistic_from=all_group_forum
3.56 Check of Transmission Link Fault Recovery Switch
1.58.11Location

06 Accident Inspection Scene 01 Accident Risk Check 04 Check of Transmission Link Fault Recovery Switch
If this switch is off, it can’t recover the transmission link fault after eNodeB is disconnected. This rule is mainly used to collect the entire
network’s transmission link fault recovery (TLFR) switch state.
1) Output the number of eNodeBs under different TLFR switch states in the entire network.
TLFR Switch (eNodeB Number)
　 TLFR Switch (Disable) TLFR Switch (Enable)
eNodeB Number 1 2
2) Output eNodeBs’ related information with disabled TLFR switch.
TLFR Switch (Disable)
eNodeB ID eNodeB Name TLFR Switch
600071 TLWW1_RJ Disable

1.58.13 Principles
1) Confirm the eNodeB is not under GL dual-mode: Check the value of RS under RRU from XML file and RS ≠ 72 (Only eRAN6.0 and eRAN7.0
have this judgment).
2) Check the value of TLFRSWITCH under TLFRSWITCH from XML file. Count the number of eNodeBs with different states. (TLFRSWITCH =
0 means DISABLE and LFRSWITCH = 1 means ENABLE).
3) If TLFRSWITCH is DISABLE, output this eNodeB’s related information.
1.58.14 Measures
MML command: SET TLFRSWITCH: TLFRSWITCH=ENABLE~1.
1.58.15 Reference
None.
3.57 Check of Binding Route of Master/Slave OMCH
1.58.16 Location

06 Accident Inspection Scene 01 Accident Risk Check 05 Check of Binding Route of Master/Slave OMCH
If an eNodeB is configured standby OMCH but doesn’t bind the route, the eNodeB couldn’t handover successfully when the current OMCH was
interrupted and U2000 switched its master/slave state, which will lead to the interruption of OMCH. This rule is mainly used to collect eNodeBs’ related
information which their OMCH didn’t bind the route.
1) Output eNodeBs’ related information which their OMCH didn’t bind the route.
eNodeBs Which Their OMCH didn’t Bind the Route

eNodeB ID eNodeB Name Configuration State
50160 So-MPT-UU-160 OMCH without binding route

1.58.18 Principles
1) Run MML’s LST OMCH command or check LMT.XML file to confirm the configuration of OMCH.
2) If there are two pieces of OMCH configuration information and their states are Master and SLAVE respectively, it indicates that the eNodeB is
configured with standby OMCH and go to step 3).
3) If both the MASTER and the SLAVE’s BRT are No, it is considered as a risk and output standby OMCH wasn’t configured the BRT, or end.
1.58.19 Measures
Bind the route for eNodeBs which have configured standby OMCH by the following command: MOD OMCH.
1.58.20 Reference
None.
3.58 DSTIP of IPRT Check
1.58.21 Location

06 Accident Inspection Scene 01 Accident Risk Check 06 DSTIP of IPRT Check
The route cannot be found and then station off under OMCH load sharing. This rule is mainly used to collect eNodeBs’ related information if the
DSTIP is 0.0.0.0, bear type of OMCH is ATM and BRT is No.
1) Output the number of eNodeBs with this risk.
The Number of eNodeBs with Disconnected Risk

The Number of eNodeBs with Disconnected Risk
1
2) Output the risky eNodeBs’ related information with details.
OMCH DSTIP of IPRT Check
eNodeB ID eNodeB Name BEAR DSTIP
53818 LBBPd2_liubin ATM 0.0.0.0

1.58.23 Principles
1) Run MML’s LST OMCH command or check LMT.XML file to confirm the configuration of OMCH.
2) If BEAR is “ATM”, go to step 3). If BEAR is “IPV4”, end.
3) If OMCH’s BRT is No, go to step 4), or end.
4) Run MML’s LST IPRT or check LMT.XML file to confirm the configuration of IPRT. If there is a default route with a 0.0.0.0 destination IP
address, output “ATM OMCH has a default route” to remind the risk.
1.58.24 Measures
Modify OMCH DSTIP to not all zero: MOD IPRT.
1.58.25 Reference
None.
3.59 BFD Session Check
1.58.26 Location

06 Accident Inspection Scene 01 Accident Risk Check 07 BFD Session Check
When active/standby route and equivalent route weren’t configured with BFD (Bidirectional Forwarding Detection) function, the trigger of
routes switching may fail. This rule is mainly used to collect the entire network’s BFD configuration information.
1) Output the number of eNodeBs under different BFD checking items in the entire network.
BFD Session Check (eNodeB Number)

Active/Standby Active/Standby Equivalent Route Equivalent BFD Function BFD Function
　
Route (Not Config) Route (Config) (Not Config) Route (Config) (Not Config) (Config)
eNodeB
250 0 250 0 250 0
Number
2) Output eNodeBs’ BFD configuration information in the entire network.

BFD Session Check

eNodeB ID eNodeB Name Active/Standby Routes Equivalent Routes BFD Function
230005 230005 Not configured Not configured Not configured
1.58.28 Principles
Check the configuration of eNodeBs’ active/standby route, equivalent route and BFD function by XML file.
1) Active/Standby route:
a) If DSTIPs are the same but NEXTHOPs and PREFs under their IPRT are different respectively, output “Configured”, or output “Not
configured”.
2) Equivalent route:
a) If DSTIPs, MASKs and REFs are the same but NEXTHOPs under their IPRT are different respectively, output “Configured”, or output “Not
configured”.
3) BFD function:
a) If SRCIP under BFDSESSION from XML file is vacant, output “Not configured”, or go to next step.
b) If the SRCIP is the same with the local IP of OMCH, output “Configured” and count the number of eNodeBs under different states. If they
are different, output “Not configured”.
Note: If the eNodeB is configured with equivalent route or active/Standby route, but without BFD session, mark it as abnormal.
1.58.29 Measures
MML command: ADD BFDSESSION.
1.58.30 Reference
None.
3.60 Signal Plane Config Check
1.58.31 Location

06 Accident Inspection Scene 01 Accident Risk Check 08 Signal Plane Config Check

In congestion scenario, it may lose the packet during the entire network transmission if DSCP of SIG is less than 46. If yes and it is less than other
transmission priority, it will lead to higher risk. This rule is mainly used collect eNodeBs’ related information with this risk.
1) Output eNodeBs’ related information if their DSCP of SIG are less than 46.
eNodeBs with DSCP of SIG <46

eNodeB eNodeB Signaling OM High OM Low
IPCLKPRI Recommendation
ID Name Priority Priority Priority
Low SIG priority will lead to a higher risk of losing
230080 230080 45 46 44 44
packet in congestion scenario. Modification is necessary.
If SIG priority is less than the default value, signaling will
230074 230074 45 44 44 44
loss the packet during transmission. Please modify it.
1.58.33 Principles
1) Check the value of PRIRULE under DIFPRI from XML file. If PRIRULE = 1, it indicates DSCP state, that is, differentiated services priority rule
is used, and go to next step, or end.
2) Judge the value of SIGPRI. If SIGPRI < 46 and under congestion scenario, packets may get lost. Output this eNodeB’s information.
3) For these risky eNodeBs, check the priority of OMHIGHPRI/ OMLOWPRI/ IPCLKPRI and output the result.
4) If the priority of OMHIGHPRI/ OMLOWPRI/ IPCLKPRI is larger than the value of SIGPRI, mark it red and judge it as abnormal.
Note: The risk only exists in congestion scenario.
1.58.34 Measures
Set the DSCP of SIG >= 46 by SET DIFPRI.
1.58.35 Reference
None.

3.61 BOOTROM Version Check
1.58.36 Location

06 Accident Inspection Scene 01 Accident Risk Check 09 BOOTROM Version Check
If RRU module enters a faulty BOOTROM version, RRU chain may break, it can’t work or upgrade and the base station may become
disconnected. This rule is mainly used to collect eNodeBs’ information with faulty BOOTROM version.
1) Output eNodeBs’ related information with faulty BOOTROM version.
BOOTROM Version Check
eNodeB ID eNodeB Name CN SRN SN RRU Hardware Version RRU BootRom Version
414 VoLTE414 0 60 0 MRRU.HWEI.x30140002 18.220.10.017
1.58.38 Principles
Check the information of RRU board and related BOOTROM version by MML command.
1) Run MML’s DSP BRDVER command to check the information of RRU hardware version and BootRom version.
2) For MRFUV2 850M RF module, mark it as abnormal if BOOTROM version is less than “18.232.10.017”.
Note: Comparing the module’s hardware version with MRFU.HWEI.x8A122502. If other characters are the same except the last two, it is
considered as MRFUV2 850M module.
3) For MRRU 1800M module, mark it as abnormal if BOOTROM version is less than “18.225.10.017”.
Note: Comparing the module’s hardware version with any one of MRRU.HWEI.x30140002, MRRU.HWEI.x30140001,
MRRU.HWEI.x30120002, MRRU.HWEI.x30120001, MRRU.HWEI.x30130001, or MRRU.HWEI.x31130002. If other characters are the same except the
last two, it is considered as MRRU 1800M module.
4) For MRRU (not 1800M) module, mark it as abnormal if BOOTROM version is less than “02.035.10.009”.
5) For MRFU V1 module, mark it as abnormal if BOOTROM version is less than “18.234.10.017”.
6) For V3 module, mark it as abnormal if BOOTROM version is less than “1C.178.10.019”.
7) For RRU3201/RRU3203/RRU3808/LRFU module, mark it as abnormal if BOOTROM version is less than “18.321.10.017”.
Note: Comparing the module’s hardware version with any one of LRRU.HWEI.x00130100, LRRU.HWEI.x00130002,

LRRU.HWEI.x00170000, LRRU.HWEI.x00170100, LRRU.HWEI.731170000, LRRU.HWEI.031170000 or LRFU.HWEI.x00170000. If other characters
are the same except the last two, it is considered as RRU3201/RRU3203/RRU3808/LRFU module.
8) For RRU3804/RRU3806/WRFU module, mark it as abnormal if BOOTROM’s version is less than “01.094.03.001”.
9) Judge whether it is MRRU (not 1800M) module, MRFU V1 module, V3 module, or RRU3804/3806/WRFU by RRU hardware version, which
are listed in the below excel table.
Ha rd wa re
Ve rs io n N u m b e r.xls x
1.58.39 Measures
Before upgrading the flash version, upgrade BOOTROM version first. It is recommended to upgrade the BOOTROM version to BTS3900
v100R010C10SPC190.
1.58.40 Reference
None.
3.62 Check of MAC Excessive Frame Error Rate
1.58.41 Location

06 Accident Inspection Scene 01 Accident Risk Check 08 Check of MAC Excessice Frame Error Rate
“MAC Excessive Frame Error Rate” is a minor alarm, but it indicates the local Ethernet port is inconsistent with the peer Ethernet port, which
will affect the transmission quality of the Ethernet link and the ongoing services may even be interrupted. This rule is mainly used to collect boards’
information with this alarm during the inspection period.
1) Output boards’ information which has this alarm.

The MAC Excessive Frame Error Rate (Current)

eNodeB eNodeB Current Occurrence
CN SRN SN PN
ID Name FER(per mill) Time
2012-12-13
230104 230104 1 63 0 1 10
08:39:38
2) Output boards’ information which had this alarm during the inspection period.
The MAC Excessive Frame Error Rate (Existed)

eNodeB eNodeB Current FER
CN SRN SN PT Occurrence Time Clearance Time
ID Name (per mill)
230104 230104 0 63 0 1 1000 2012-12-13 08:36:44 2012-12-13 08:37:28
230104 230104 0 63 0 1 10 2012-12-13 08:34:52 2012-12-13 08:36:36
1.58.43 Principles
Check the following fields from Alarm.csv file.
1) Check the information of Alarm ID=25881, find the location where the alarm occurs in the LocationInformation and count the number of alarm
occurrences as the number of exceptions.
2) Check whether there is data under ClearanceTime.
If no, it is considered as active alarm and output the related information to the “The MAC Excessive Frame Error Rate (Current)” table.
If yes, it is considered as historical alarm and output the related information to the “The MAC Excessive Frame Error Rate (Existed)” table.
1.58.44 Measures
Please solve it according to the alarm reference.
1.58.45 Reference
None.
3.63 Check of the Number of Neighboring Utran Cells
1.58.46 Location

06 Accident Inspection Scene 01 Accident Risk Check 10 Check of the Number of Neighboring Utran Cells

If excessive neighboring Utran cells are configured on the eNodeB, it may decrease the RRC setup success rate. This rule is mainly used to
collect eNodeBs’ related information with neighboring Utran cells.
1) Output eNodeBs’ related information with neighboring Utran cells and the number of neighboring Utran cells.
Result of the Number of Neighboring Utran Cells

eNodeB Number of Neighboring
eNodeB Name
ID Utran Cells
62368 62368 223
1.58.48 Principles
1) Check EutranExternalCell field from XML file.
2) Count and output the number of its configurations under EutranExternalCell.
3) If the number of EutranExternalCell is >= 3500, mark it as abnormal and count the number of abnormal eNodeBs as the number of exceptions.
Note: Only versions before eRAN6.0 SPC290, all eRAN6.1 versions and versions before eRAN7.0 SPC150 operate this check.
1.58.49 Measures
Delete UTRANNCELL’s configuration.
1.58.50 Reference
None.
3.64 Check of Abnormal User Number with QCI
1.58.51 Location

06 Accident Inspection Scene 01 Accident Risk Check 11 Check of Abnormal User Number with QCI

When the number of activated UEs with the QCI in the uplink & downlink buffer keeps increasing and has no periodic rules on time(no busy/idle
time), it may exceed the max user number of a cell, which would affect the network. This rule is mainly used to collect cells’ related information with this
risk.
Cells with Abnormal QCI User Number

eNodeB eNodeB Local Type of QCI with Increasing Type of QCI with Increasing
Time
ID Name Cell ID Activated UEs in Downlink Buffer Activated UEs in Uplink Buffer
2014-01-26-2014-01-
116009 EAJ009 1 QCI1/QCI9 QCI1/QCI9
28
1.58.53 Principles
1) Check whether L.Traffic.ActiveUser.DL.QCI.1 (Number of activated UEs with the QCI of 1 in the downlink buffer) and
L.Traffic.ActiveUser.UL.QCI.1 (Number of activated UEs with the QCI of 1 in the uplink buffer) are increasing at the same time. The method is
as follows:
a) Check all days’ traffic data between 0 AM to 6 AM during the inspection period. If the user number is larger than the last hour during 0AM
to 6AM, which lasts for several days, and uplink and downlink user number are increasing at the same time, it is considered as abnormal
and output the number of exceptions based on the number of abnormal eNodeBs.
2) Use the same way to check QCI2 to QCI9.
3) Collect the type of QCI of each cell if its uplink & downlink user number are increasing at the same time.
1.58.54 Measures
Adjust the handover threshold to a reasonable range to avoid excessive handovers due to wrong handover threshold and decrease the probability
of this problem.
1.58.55 Reference
None.
Note: This rule is just for eRAN6.0 (versions before eRAN6.0 SPC240) and eRAN6.1 (versions before eRAN6.1 SPC240).

3.65 NIC Collection State Analysis
1.58.56 Location

07 NIC Collection State Analysis 01 NIC Collection State Analysis 01 NIC Collection State Analysis
If the collection of NE data fails, it will affect the data analysis. This rule is mainly used to record different states of NE collection and other
related information after SOP analysis task finished.
1) Output NE information contained in the raw data in detail and each NE’s collection state.
Analysis of NE Collection States

NE Total Number of Number of Successfully Number of Unsuccessfully
NE ID NE Name
Type Collected NEs Collected NEs Collected NEs
230048 230048 DBS3900LTE 27 25 2
230049 230049 DBS3900LTE 27 27 0
2) Output NE’s related information if its NE collection failed.
Detailed Analysis of Unsuccessfully Collected NEs

NE Name of Collection Error
NE ID NE Name Collection Type
Type Collection Item State Description
Board Information Board Status

230053 230053 DBS3900LTE Failure --
and Software Version Query
Board Information Software

230053 230053 DBS3900LTE Failure --
and Software Version Version Query
Note: This rule is only applicable for single network mode and has no output for newly setup project mode.
1.58.58 Principles
1) Decompress NIC data package.
2) Read the content of index.html in the root directory of compressed package of collected report and output related information to “Analysis of NE
Collection State”.
3) If the number of unsuccessfully collection NEs is not 0 in index.html, read the content under NE file and output them into “Detailed Analysis of
Unsuccessfully Collected NEs” table.

1.58.59 Measures
None.
1.58.60 Reference
None.
3.66 SRI Resource Adaptive Adjustment
1.58.61 Location

09 Big Traffic Inspection 01 Adaptive CFG of Basic Resources 01 SRI Resource Adaptive Adjustment
If resources of SRI (Scheduling Request Indication) are limited, access of the internet may fail. While, enabled SRI adaptive switch can optimize
the resource usage. Therefore, it is recommended to turn it on. This rule is mainly used to collect information of eNodeBs with disabled SRI adaptive
switch.
1) Output eNodeBs’ related information with disabled SRI adaptive switch.
SRI Adaptive Switch

eNodeB ID eNodeB Name SRI Adaptive Switch
50405 CLOUD 5 MOD GLOBALPROCSWITCH: SriAdaptiveSwitch=ON;
1.58.63 Principles
1) Check the value of SriAdaptiveSwitch under GlobalProcSwitch from LMT.XML file.
a) If SriAdaptiveSwitch=1, it indicates SRI adaptive switch is turned on and end.
b) If SriAdaptiveSwitch=0, it indicates SRI adaptive switch is turned off and go to step 2).
2) Output this eNodeB’s related information and corresponding modifications.

1.58.64 Measures
MOD GLOBALPROCSWITCH：SriAdaptiveSwitch = ON.
Link of <LTE Heavy Traffic Precautions and Emergency Measures Guide-20150118-A-V4.0>:
http://support.huawei.com/carrier/docview!docview?nid=SE0000733418&path=PBI1-7851894/PBI1-21433538/PBI1-7854329/PBI1-
21465979/PBI1-6149576
1.58.65 Reference
None.
3.67 PUCCH Resource Adjustment Algorithm
1.58.66 Location

09 Big Traffic Inspection 01 Adaptive CFG of Basic Resources 02 PUCCH Resource Adjustment Algorithm
If resources of PUCCH are limited, access of the internet may fail. While, turning PUCCH switch on can optimize the resource usage. Therefore,
it is recommended to turn it on. This rule is mainly used to collect cells’ related information with disabled PUCCH resource adjustment switch.
1) Output cells’ related information with disabled PUCCH resource adjustment switch.
PUCCH Resource Adjustment Algorithm

eNodeB
eNodeB Name Local Cell ID PUCCH Resource Adjustment Algorithm
ID
MOD CELLALGOSWITCH : LocalCellId= 4,
5021 5C-21 4
PucchAlgoSwitch=PucchSwitch-1;
1.58.68 Principles
1) Check the value of PucchAlgoSwitch under CellAlgoSwitch from LMT.XML file.
2) Convert it into a binary number.
a) If bit0 = 1, it indicates PucchSwitch is turned on and end.

b) If bit0 = 0, it indicates PucchSwitch is turned off and go to step 3).
3) Output this cell’s related information and corresponding modifications.
1.58.69 Measures
MOD CELLALGOSWITCH: LocalCellId = x, PucchAlgoSwitch = PucchSwitch-1.
21465979/PBI1-6149576
1.58.70 Reference
None.
Note: This rule is just for eRAN6.0, eRAN6.1, eRAN7.0 and eRAN8.0.
3.68 CQI Period Adaptive Adjustment
1.58.71 Location

09 Big Traffic Inspection 01 Adaptive CFG of Basic Resources 03 CQI Period Adaptive Adjustment
If CQI resources are limited, access of the internet may fail. While, turning CQI period adaptive switch on can optimize the resource usage.
Therefore, it is recommended to turn it on. This rule is mainly used to collect information of eNodeBs with disabled CQI period adaptive switch.
1) Output eNodeBs’ related information with disabled CQI period adaptive switch.
CQI Period Adaptive Switch

eNodeB ID eNodeB Name CQI Period Adaptive Switch
60197 S_60197 MOD CQIADAPTIVECFG : CqiPeriodAdaptive = ON;
1.58.73 Principles
1) Check the value of CqiPeriodAdaptive under CqiAdaptiveCfg from LMT.XML file (For eRAN11.0 version, check the value of

CqiPeriodAdaptive under CELLCQIADAPTIVECFG).
a) If CqiPeriodAdaptive=1, it indicates CQI period adaptive switch is turned on and end.
b) If CqiPeriodAdaptive=0, it indicates CQI period adaptive switch is turned off and go to step 2).
1.58.74 Measures
MOD CQIADAPTIVECFG: CqiPeriodAdaptive = ON.
21465979/PBI1-6149576
1.58.75 Reference
None.
3.69 SRS Period Adaptive Adjustment
1.58.76 Location

09 Big Traffic Inspection 01 Adaptive CFG of Basic Resources 04 SRS Period Adaptive Adjustment
If SRS resources are limited, access of the internet may fail. While, turning SRS period adaptive switch on can optimize the resource usage.
Therefore, it is recommended to turn it on. This rule is mainly used to collect information of eNodeBs with disabled SRS period adaptive switch.
1) Output eNodeBs’ related information with disabled SRS period adaptive switch.
SRS Period Adaptive Switch

eNodeB ID eNodeB Name SRS Period Adaptive Switch
60199 S_60199 MOD SRSADAPTIVECFG : SrsPeriodAdaptive = ON;

1.58.78 Principles
1) SRS period adaptive switch is turned on (Just for eRAN8.1): Check the value of FddSrsCfgMode under SRSCFG from LMT.XML file and
FddSrsCfgMode = 1.
2) SRS period adaptive switch is turned off: Check the value of SrsPeriodAdaptive under SrsAdaptiveCfg from LMT.XML file and
SrsPeriodAdaptive = 0. Go to next step.
1.58.79 Measures
MOD SRSADAPTIVECFG: SrsPeriodAdaptive=ON.
21465979/PBI1-6149576
1.58.80 Reference
None.
3.70 SRS Subframe RECF Switch Adjustment
1.58.81 Location

09 Big Traffic Inspection 01 Adaptive CFG of Basic Resources 05 SRS Subframe RECF Switch Adjustment
If SRS subframe resources are limited, access of the internet may fail. While, turning SRS subframe RECF switch on can optimize the resource
usage. Therefore, it is recommended to turn it on. This rule is mainly used to collect information of cells with disabled SRS subframe RECF switch.
1) Output cells’ related information with disabled SRS subframe RECF switch.
SRS Subframe RECF Switch

eNodeB ID eNodeB Name Local Cell ID SRS Subframe RECF Switch

MOD CELLALGOSWITCH : LocalCellId = 0,

50222 enb192 0
SrsAlgoSwitch = SrsSubframeRecfSwitch-1;
1.58.83 Principles
1) SRS adaptive function is enabled (Just for eRAN8.1): Check the value of FddSrsCfgMode under SRSCFG from LMT.XML file. If
FddSrsCfgMode = 1, go to next step, or end.
2) SRS Subframe RECF Switch is turned off: Check the value of SrsAlgoSwitch under CellAlgoSwitch from LMT.XML file and convert it into a
binary number. If bit0 = 0, it indicates that SRS subframe RECF Switch is turned off. Go to next step, or end.
1.58.84 Measures
MOD CELLALGOSWITCH: SrsAlgoSwitch = SrsSubframeRecfSwitch-1.
21465979/PBI1-6149576
1.58.85 Reference
None.
3.71 Recover SrsSubframeCfg to Default Value
1.58.86 Location

09 Big Traffic Inspection 01 Adaptive CFG of Basic Resources 06 Recover SrsSubframeCfg to Default Value
If SRS subframe is not configured as the default value (SC3), the number of users will be limited. This rule is mainly used to collect cells’ related
information with this risk.

Recover SrsSubframeCfg to Default Value

eNodeB eNodeB
Local Cell ID Recover SrsSubframeCfg to Default Value
ID Name
50230 enb230 0 MOD SRSCFG : LocalCellId = 0, SrsSubframeCfg = SC3;
1.58.88 Principles
1) SRS adaptive function is enabled (Just for eRAN8.1): Check the value of FddSrsCfgMode under SRSCFG from LMT.XML file. If
FddSrsCfgMode = 1, go to next step, or end.
2) SRS subframe is not configured as the default value (SC3): Check the value of SrsSubframeCfg under SRSCfg from LMT.XML file. If
SrsSubframeCfg ≠ 3, go to next step, or end.
1.58.89 Measures
MOD SRSCFG: SrsSubframeCfg = SC3.
21465979/PBI1-6149576
1.58.90 Reference
None.
3.72 Extend T302 to 16s
1.58.91 Location

09 Big Traffic Inspection 02 Lower CPU Overhead 01 Extend T302 to16s

An eNodeB delivers RRC Reject signaling with T302 timer to UE and UE will launch the next RRC access after the timeout. Therefore, extending
the timer will relieve the signaling shock led by UE vindictive retry. However, extending T302 may increase user’ access delay. This rule is mainly used to
collect eNodeBs’ related information which its T302 ≠ 16.
1) Output eNodeBs’ related information if T302 ≠ 16.
Extend T302 to16s

eNodeB ID eNodeB Name Extend T302 to 16s
300 2T8R MOD RRCCONNSTATETIMER : T302 = 16;
1.58.93 Principles
1) Check the value of T302 under RrcConnStateTimer from LMT.XML file.
2) If T302 = 16, it indicates that T302 timer is set to 16s.
3) If T302 ≠ 16, output this eNodeB’s related information and corresponding modifications, or end.
1.58.94 Measures
MOD RRCCONNSTATETIMER: T302 = 16.
21465979/PBI1-6149576
1.58.95 Reference
None.
3.73 Disable FAST ANR
1.58.96 Location

09 Big Traffic Inspection 02 Lower CPU overhead 02 Disable FAST ANR

When FAST ANR algorithm switch is turned on, it will trigger excessive Uu interface measurement reports, which will impact the CPU usage of
main control board. It is suggested to turn it off during the assurance period. This rule is mainly used to collect eNodeBs’ related information with enabled
FAST ANR algorithm switch.
1) Output eNodeBs’ related information with enabled FAST ANR algorithm switch.
Disable FAST ANR

eNodeB ID eNodeB Name Close FAST ANR
MOD ENODEBALGOSWITCH:
5048 KPI02_48 AnrSwitch=IntraRatFastAnrSwitch-0&UtranFastAnrSwitch-
0&GeranFastAnrSwitch-0&CdmaFastAnrSwitch-0;
1.58.98 Principles
1) Check the value of AnrSwitch under ENodeBAlgoSwitch from LMT.XML file.
2) Convert the value into a binary number.
a) If bit1 = 1, it indicates that IntraRatFastAnrSwitch is turned on.
b) If bit5 = 1, it indicates that UtranFastAnrSwitch is turned on.
c) If bit6 = 1, it indicates that GeranFastAnrSwitch is turned on.
d) If bit7 = 1, it indicates that CdmaFastAnrSwitch is turned on.
3) If the value of AnrSwitch meets any one of the above conditions, output this eNodeB’s related information and corresponding modifications. Or
end.
1.58.99 Measures
MOD ENODEBALGOSWITCH: AnrSwitch=IntraRatFastAnrSwitch-0 & UtranFastAnrSwitch-0 & GeranFastAnrSwitch-0 &
CdmaFastAnrSwitch-0.
21465979/PBI1-6149576

1.58.100 Reference
None.
3.74 Disable DRX
1.58.101 Location
09 Big Traffic Inspection 02 Lower CPU overhead 03 Disable DRX
Excessive DRX users need to be maintained by a large number of timers and it will consume plenty of baseband board resources. It is suggested to
turn it off before the assurance. This rule is mainly used to collect eNodeBs’ related information with enabled DRX algorithm switch.
1) Output eNodeBs’ related information with enabled DRX algorithm switch.
Disable DRX
eNodeB ID eNodeB Name Disable DRX
6127 JJFAIOT_eNB127 MOD DRX : DrxAlgSwitch = OFF;
1.58.103 Principles
1) Check the value of DrxAlgSwitch under Drx from LMT.XML file.
a) If DrxAlgSwitch = 0, it indicated the switch is turned off and end.
b) If DrxAlgSwitch = 1, it indicates the switch is turned on and go to step 2).
1.58.104 Measures
MOD DRX: DrxAlgSwitch = OFF.
21465979/PBI1-6149576

1.58.105 Reference
None.
Note: This rule is just for eRAN6.0, eRAN6.1, eRAN7.0, eRAN8.0 and eRAN8.1.
3.75 Increase Intra-Freq A3 Threshold to 5DB
1.58.106 Location

09 Big Traffic Inspection 02 Lower CPU overhead 04 Increase Intra-Freq A3 Threshold to 5DB
Increasing the intra-frequency handover threshold will reduce the times of intra-frequency handover and the CPU overhead of main control board
due to reduced handover signaling. This rule is mainly used to collect cells’ related information which weren’t configured intra-frequency A3 threshold to
5DB.
1) Output cells’ related information which weren’t configured intra-frequency A3 threshold to 5DB.
Increase Intra-frequency A3 Threshold to 5DB

eNodeB eNodeB Local
Increase Intra-frequency A3 Threshold to 5DB
ID Name Cell ID
MOD INTRAFREQHOGROUP: LocalCellId = 0,

300 2T8R 0
IntraFreqHoA3Hyst = 4, IntraFreqHoA3Offset = 6.
1.58.108 Principles
1) Check IntraFreqHoA3Hyst and IntraFreqHoA3Offset corresponded with the cell under IntraFreqHoGroup from LMT.XML file.
a) If IntraFreqHoA3Hyst = 4, it indicates intra-frequency handover hysteresis is 4*0.5(DB).
b) If IntraFreqHoA3Offset = 6, it indicates intra-frequency handover offset is 6*0.5(DB).
2) If the values of these two parameters don’t meet any of conditions in 1), output this cell’s information and corresponding modifications, or end.

1.58.109 Measures
MOD INTRAFREQHOGROUP: LocalCellId = x, IntraFreqHoA3Hyst = 4, IntraFreqHoA3Offset = 6.
21465979/PBI1-6149576
1.58.110Reference
None.
Note: This rule is just for eRAN6.0, eRAN6.1, eRAN7.0, eRAN8.0 and eRAN8.1.
3.76 Randomize UL Interference
1.58.111Location
09 Big Traffic Inspection 03 Minimize UL Interference 01 Randomize UL Interference
1.58.112Rules Description
When the resources are allocated in the uplink scheduling, cells choose different distribution starting position according to the result of PCI mode
2. It may allocated from high frequency bands or low frequency bands, which could stagger the resource distribution of neighboring cells in a certain extent
to reduce the inter-cell interference and improve the user performance. This rule is mainly used to collect cells’ related information if their strategy for
allocating resource blocks (RBs) in the uplink of the cell is not Fs InRandom Strategy.
1) Output cells’ related information if their strategy for allocating resource blocks (RBs) in the uplink of the cell is not Fs InRandom Strategy.
Randomize UL Interference
eNodeB ID eNodeB Name Local Cell ID Randomize UL Interference
MOD CELLULSCHALGO : LocalCellId = 0,

5048 KPI02_48 0
UlRbAllocationStrategy = FS_INRANDOM_ADAPTIVE;

1.58.113 Principles
1) Check the value of UlRbAllocationStrategy under CellUlschAlgo from LMT.XML file.
2) If UlRbAllocationStrategy=1, it indicates the strategy for allocating RBs in the uplink of the cell is Fs InRandom Strategy.
3) If UlRbAllocationStrategy≠1, output this cell’s information and corresponding modifications, or end.
1.58.114Measures
MOD CELLULSCHALGO: LocalCellId = x, UlRbAllocationStrategy = FS_INRANDOM_ADAPTIVE.
21465979/PBI1-6149576
1.58.115Reference
None.
3.77 PUCCH IRC Algorithm Switch
1.58.116Location

09 Big Traffic Inspection 03 Minimize UL Interference 02 PUCCH IRC Algorithm Switch
IRC is a diversity combining technology and it can suppress the interference. Enabled PUCCH IRC switch can reduce PUCCH interference at a
certain extent and improve PUCCH’s demodulation performance. Therefore, it is recommended to turn it on. This rule is mainly used to collect cells’
related information with disabled PUCCH IRC algorithm switch.
1) Output cells’ related information with disabled PUCCH IRC algorithm switch.
PUCCH IRC Algorithm Switch

eNodeB ID eNodeB Name Local Cell ID PUCCH IRC Algorithm Switch

MOD CELLALGOSWITCH : LocalCellId =

300 2T8R 0
0, IrcSwitch = PucchIrcSwitch-1;
1.58.118Principles
1) Check eNodeBs’ Board Type by MML’s DSP BRDMFRINFO command. If Type = WD22LBBPC2, it indicates LBBPC board is supported and
end. If not, go to next step.
2) Check the value of IrcSwitch under CellAlgoSwitch from LMT.XML file and convert it into a binary number. If bit0 = 0, which indicates
PUCCH IRC algorithm switch is turned off, go to next step. Or end.
1.58.119Measures
MOD CELLALGOSWITCH: LocalCellId = x, IrcSwitch = PucchIrcSwitch-1.
21465979/PBI1-6149576
1.58.120 Reference
None.
3.78 Disable DL Frequency Selection
1.58.121 Location

09 Big Traffic Inspection 03 Minimize UL Interference 03 Disable DL Frequency Selection
If FreqSelSwitch of the DlSchSwitch is turned on, it will trigger the reporting of uplink CQI-ONLY, increase the uplink power and the
neighboring cell interference. This rule is mainly used to collect cells’ related information with enabled FreqSelSwitch.
1) Output cells’ related information with enabled FreqSelSwitch.

Disable DL Frequency Selection in Protection Area and Neighboring Cells

eNodeB ID eNodeB Name Local Cell ID FreqSelSwitch
5C-N-03-SON- MOD CELLALGOSWITCH : LocalCellId =

5023 1
tangwei23 1, DlSchSwitch = FreqSelSwitch-0;
1.58.123 Principles
1) Check the value of DlSchSwitch under CellAlgoSwitch from LMT.XML file.
a) If bit0 = 0, it indicates that FreqSelSwitch is turned off and end.
b) If bit0 = 1, it indicates that FreqSelSwitch is turned on and go to step 3).
1.58.124 Measures
MOD CELLALGOSWITCH: LocalCellId = x, DlSchSwitch = FreqSelSwitch-0.
21465979/PBI1-6149576
1.58.125 Reference
None.
3.79 Enable UL COMP
1.58.126 Location

09 Big Traffic Inspection 03 Minimize UL Interference 04 Enable UL COMP
UL CoMP function will choose the matching UE to joint receive multi-cell antennas. As a result, CoMP UE uses several times of antennas than

the non-CoMP UE, which will obtain interference suppression gain by IRC algorithm and increase the cell’s uplink throughput. This rule is mainly used to
collect cells’ related information with disabled uplink CoMP switch.
1) Output cells’ related information with disabled uplink CoMP switch.
Enable UL COMP
eNodeB eNodeB Local Cell
Enable UL COMP
ID Name ID
MOD CELLALGOSWITCH : UplinkCompSwitch = UlJointReceptionSwitch-1&
UlJointReceptionPhaseIISwitch-0 & UlCompRollbackSwitch-1;
300 2T8R 0 MOD CELLMCPARA :
LocalCellId = 0,ReportAmount = 1;
MOD CELLULCOMPALGO : LocalCellId = 0, UlCompA3Offset = -10;
1.58.128 Principles
1) Check the value of UplinkCompSwitch under CellAlgoSwitch from LMT.XML file and convert it into a binary number.
 If bit0 = 1, it indicates UlJointReceptionSwitch is turned on.
 If bit1 = 0, it indicates UlJointReceptionPhaseIISwitch is turned off.
 If bit2 = 1, it indicates that UlCompRollbackSwitch is turned on.
2) Check the value of ReportAmount under CellDLIcicMcPara.
 If ReportAmount = 0, it indicates the number of uplink ICIC measurement reports is 1.
3) Check the value of UlCompA3Offset under CellUlCompAlgo.
 If UlCompA3Offset = -10, it indicates the offset of intra-frequency handover is -10*0.5(DB). For eRAN8.1 version, UlCompA3Offset =
-20.
4) If one of the checked parameters don’t meet the above conditions, output this cell’s related information and corresponding modifications.
Note: For eRAN6.0 version, check the value of UlCompSwitch under CellAlgoSwitch in 1). If UlCompSwitch = 0, it indicates that uplink CoMP
algorithm switch is off and go to step 2) and 3).
1.58.129 Measures
1) MOD CELLALGOSWITCH: UplinkCompSwitch = UlJointReceptionSwitch-1 & UlJointReceptionPhaseIISwitch-0 & UlCompRollbackSwitch-
1(or MOD CELLALGOSWITCH: LocalCellId=0, UlCompSwitch=ENABLE).
2) MOD CELLMCPARA: LocalCellId = x, ReportAmount = 1.
3) MOD CELLULCOMPALGO: LocalCellId = x, UlCompA3Offset = -10. (eRAN8.1: UlCompA3Offset = -20)

21465979/PBI1-6149576
1.58.130 Reference
None.
3.80 Reduce Power Control Initial Value P0 of PUSCH and PUCCH
1.58.131 Location

09 Big Traffic Inspection 03 Minimize UL Interference 05 Reduce Power Control Initial Value P0 of PUSCH and PUCCH
Reducing the UE uplink transmit power during the access process would lower the interference to the neighboring cells. This rule is mainly used
to collect cells’ related information if their power control initial value P0 of PUSCH and PUCCH are not reduced.
1) Output cells’ related information if their power control initial value P0 of PUSCH and PUCCH are not reduced.
Reduce Power Control Initial Value P0 of PUSCH and PUCCH
eNodeB ID eNodeB Name Local Cell ID Reduce Power Control Initial Value P0 of PUSCH and PUCCH
MOD CELLULPCCOMM : LocalCellId = 0, PassLossCoeff = AL1,

300 2T8R 0
P0NominalPUCCH = -115, P0NominalPUSCH = -106;
1.58.133 Principles
1) Check the value of PassLossCoeff, P0NominalPUCCH and P0NominalPUSCH under CellUlpcComm from LMT.XML file.
a) If PassLossCoeff = 7, it indicates that the path loss coefficient is 1(AL1).
b) If P0NominalPUCCH = -115, it indicates that P0 nominal PUCCH is -115 (dBm).
c) If P0NominalPUSCH = -106, it indicates that P0 nominal PUSCH is -106 (dBm).
2) If one of the checked parameters don’t meet the above conditions, output this cell’s related information and corresponding modifications. Or end.

1.58.134 Measures
MOD CELLULPCCOMM: LocalCellId = 0, PassLossCoeff = AL1, P0NominalPUCCH = -115, P0NominalPUSCH = -106.
21465979/PBI1-6149576
1.58.135 Reference
None.
3.81 Reduce PUSCH Power Control Initial Value P0
1.58.136 Location

09 Big Traffic Inspection 03 Minimize UL Interference 05 Reduce PUSCH Power Control Initial Value P0
During the initial period of accessing, the transmit power of PUSCH equals to P0+a*PL, where a is PassLossCoeff and PL is uplink pass loss
estimated by the UE. Therefore, reducing P0 and enlarge a can lower uplink transmit power of users with small path loss and the interference to neighbor
cells. All cells in assurance areas and their intra-frequency neighbors should implement this optimization. This rule is mainly used to collect cells’ related
information if their PUSCH power control initial value P0 are not reduced.
1) Output cells’ related information if their PUSCH power control initial value P0 are not reduced.
Reduce PUSCH Power Control Initial Value P0

eNodeB ID eNodeB Name Local Cell ID Cell UL Power Control Configuration
CELLULPCCOMM:PassLossCoeff =
414 VoLTE414 0
AL07,P0NominalPUSCH = -67
1.58.138 Principles
1) Check the value of PassLossCoeff and P0NominalPUCCH under CellUlpcComm from LMT.XML file.

a) If PassLossCoeff = 7, it indicates that the Path loss coefficient is 1(AL1).
b) If P0NominalPUCCH = -115, it indicates that P0 nominal PUCCH is -115 (dBm).
c) If P0NominalPUSCH = -96, it indicates that P0 nominal PUSCH is -96 (dBm).
2) If one of the checked parameters don’t meet the above conditions, output this cell’s related information and corresponding modifications. Or end.
1.58.139 Measures
MOD CELLULPCCOMM: LocalCellId=0, PassLossCoeff=AL1, P0NominalPUSCH=-96.
21465979/PBI1-6149576
1.58.140 Reference
None.
3.82 Limit PUSCH RSRP Upper Threshold
1.58.141 Location

09 Big Traffic Inspection 03 Minimize UL Interference 06 Limit PUSCH RSRP Upper Threshold
With this optimization, uplink transmit power of near point UE will decrease while far point UE will not be affected. Therefore, interference to
neighbor cells will decrease and uplink volume of heavy traffic area will increase in the precondition of not damaging the uplink rate for far point UE. All
cells in assurance areas and their intra-frequency neighbors should implement this optimization.
1) Output cells’ related information which didn’t limit the PUSCH RSRP upper threshold.
PUSCH RSRP Upper Threshold

eNodeB ID eNodeB Name Local Cell ID PUSCH RSRP Upper Threshold
414 VoLTE414 0 CELLPCALGO:PuschRsrpHighThd = -82

1.58.143 Principles
1) Check the value of UlPcAlgoSwitch under CELLALGOSWITCH from LMT.XML file and convert it into a binary number. If bit11 = 1, it
indicates that PuschRsrpHighThdSwich is turned off, go to next step, or end.
2) Check the value of PuschRsrpHighThd under CELLPCALGO. If PuschRsrpHighThd ≠ -96, output this parameter’s value.
1.58.144 Measures
MOD CELLALGOSWITCH: LocalCellId=0, UlPcAlgoSwitch=PuschRsrpHighThdSwitch-1; MOD CELLPCALGO: LocalCellId=0,
PuschRsrpHighThd =-96.
21465979/PBI1-6149576
1.58.145 Reference
None.
3.83 Shorten the Period of PUCCH Power Control
1.58.146 Location

09 Big Traffic Inspection 04 Enhance the Reliability of PUCCH 01 Shorten the Period of PUCCH Power Control
A smaller value of this parameter results in faster adjustments for power control of PUCCH under interference, making PUCCH SINR to reach
the target more rapidly.
1) Output cells’ related information if its PUCCH power control period is not 1(20ms).
Shorten the Period of PUCCH Power Control

eNodeB ID eNodeB Name Local Cell ID PUCCH Power Control Period

414 VoLTE414 0 CELLPCALGO: PucchPcPeriod=10;
1.58.148 Principles
Check the value of PucchPcPeriod under CELLPCALGO from LMT.XML file. If PuschRsrpHighThd ≠ 1, mark it as abnormal and output this
cell’s related information.
1.58.149 Measures
MOD CELLPCALGO: LocalCellId=0, PucchPcPeriod=1;
21465979/PBI1-6149576
1.58.150 Reference
None.
3.84 Uplift PucchPcTargetSinrOffset
1.58.151 Location

09 Big Traffic Inspection 04 Enhance Reliability of PUCCH 02 Uplift PucchPcTargetSinrOffset
With higher PUCCH power control target SINR under interference scenario, it can gain better demodulation performance for PUCCH, which
indicates signaling performance of PUCCH will increase when increasing UE’s PUCCH power, but it will increase the interference to other UEs or
neighboring cells at the same time.
1) Output cells’ related information if their PucchPcTargetSinrOffset ≠ 10.
Uplift PucchPcTargetSinrOffset

eNodeB ID eNodeB Name Local Cell ID PucchPcTargetSinrOffset
414 VoLTE414 0 CELLPCALGO : PucchPcTargetSinrOffset = 0
1.58.153 Principles
Check the value of PucchPcTargetSinrOffset under CELLPCALGO from LMT.XML file. If PucchPcTargetSinrOffset ≠ 10, mark it as abnormal
and output this cell’s related information.
1.58.154 Measures
MOD CELLPCALGO: LocalCellId=0, PucchPcTargetSinrOffset=10.
21465979/PBI1-6149576
1.58.155 Reference
None.
3.85 Enable PucchPcDtxSinrSwitch
1.58.156 Location

09 Big Traffic Inspection 04 Enhance Reliability of PUCCH 03 Enable PucchPcDtxSinrSwitch
If this option is deselected, the eNodeB will discard the measured SINR for the PUCCH HARQ (hybrid automatic repeat request)-ACK feedback
that are detected in the DTX state. If there are excessive DTX existed due to the interference or other reasons under this mechanism, PUCCH power control
can’t increase the transmit power and therefore demodulation performance deteriorates.
If this option is selected, the eNodeB will process the measured uplink SINR even when PUCCH DTX is detected, generates power control

commands based on the SINR, and delivers the power control commands to UEs.
1） Output cells’ related information with disabled PucchPcDtxSinrSwitch.
Enable PucchPcDtxSinrSwitch
eNodeB ID eNodeB Name Local Cell ID PucchPcDtxSinrSwitch
CELLALGOSWITCH:
414 VoLTE414 0
UlPcAlgoSwitch=PucchPcDtxSinrSwitch-0.
1.58.158 Principles
Check the value of UlPcAlgoSwitch under CELLALGOSWITCH from LMT.XML file and convert it into a binary number. If bit7 = 0, mark it as
abnormal and output this cell’s related information.
1.58.159 Measures
MOD CELLALGOSWITCH: LocalCellId=x, UlPcAlgoSwitch=PucchPcDtxSinrSwitch-1.
21465979/PBI1-6149576
1.58.160 Reference
None.
3.86 Optimization of P0 Nominal PUCCH
1.58.161 Location

09 Big Traffic Inspection 04 Enhance Reliability of PUCCH 04 Optimization of P0 Nominal PUCCH
Reduce P0 Nominal PUCCH will lower PUCCH transmit power during the initial accessing period and the interference to the neighbor cells. It is

applicable for scenarios without interference from outside system. If uplink average interference of PUCCH in idle time (period of lowest traffic during a
whole day) is lower than -110dBm, it is considered as no interference from outside system.
1) Output cells’ related information if their P0NominalPUCCH ≠ -115(dBm).
Optimization of P0 Nominal PUCCH

eNodeB ID eNodeB Name Local Cell ID P0 nominal PUCCH
414 VoLTE414 0 CELLULPCCOMM:P0NominalPUCCH = -105
1.58.163 Principles
Check the value of P0NominalPUCCH under CELLULPCCOMM from LMT.XML file. If P0NominalPUCCH ≠ -115, mark it as abnormal and
output this cell’s related information.
1.58.164 Measures
MOD CELLULPCCOMM: LocalCellId=0, P0NominalPUCCH=-115.
21465979/PBI1-6149576
1.58.165 Reference
None.
3.87 PucchCloseLoopPcType and P0 Optimization
1.58.166 Location

09 Big Traffic Inspection 04 Enhance Reliability of PUCCH 05 PucchCloseLoopPcType and P0 Optimization

Increasing P0 Nominal PUCCH under the interference will enhance PUCCH demodulation performance during the initial accessing period. It is
applicable for scenarios under interference from outside system. If uplink average interference of PUCCH in idle time (period of lowest traffic during a
whole day) is higher than -110dBm, it is considered as having interference from outside system.
1) Output cells’ related information if their P0NominalPUCCH ≠-105(dbm) or PucchCloseLoopPcType is NOT_USE_P0NOMINALPUCCH.
Uplift P0NominalPUCCH and Modify PucchCloseLoopPcType

Value of P0NominalPUCCH and
eNodeB ID eNodeB Name Local Cell ID
PucchCloseLoopPcType
CELLPCALGO: PucchCloseLoopPcType =
414 VoLTE414 0
NOT_USE_P0NOMINALPUCCH.
1.58.168 Principles
1) Check the value of P0NominalPUCCH under CELLULPCCOMM from LMT.XML file. If P0NominalPUCCH ≠ -105 (Recommended), output
the value of this parameter.
2) Check the value of PucchCloseLoopPcType under CELLPCALGO. If PucchCloseLoopPcType= 0, it indicates PUCCH close loop power control
type is NOT_USE_P0NOMINALPUCCH, output the value of this parameter.
1.58.169 Measures
MOD CELLULPCCOMM: LocalCellId=0, P0NominalPUCCH=-105; MOD CELLPCALGO: LocalCellId=0, PucchCloseLoopPcType =
USE_P0NOMINALPUCCH.
21465979/PBI1-6149576
1.58.170 Reference
None.

3.88 Increase PUCCH DeltaShift
1.58.171 Location

09 Big Traffic Inspection 04 Enhance Reliability of PUCCH 06 Increase PUCCH DeltaShift
A larger value of this parameter leads to a longer interval between cyclic shifts used for the PUCCH, less UEs supporting code division
multiplexing in the same subcarrier, less interference between these UEs, and better demodulation performance. It is applicable for scenarios such as there
is spare uplink PUSCH resources or downlink volume must be reserved. Meanwhile, this parameter limits its MaxSyncUserNumPerBbi to less than 1200.
Therefore, the DeltaShift must be DS1_DELTA_SHIFT when MaxSyncUserNumPerBbi>1200.
1) Output cells’ related information if their DeltaShift is not DS2_DELTA_SHIFT.
Increase PUCCH DeltaShift

eNodeB eNodeB Local
MAX_SYNC_USER DeltaShift
ID Name Cell ID
GLOBALPROCSWITCH:MaxSyncUserN PUCCHCFG:DeltaShift =
414 VoLTE414 0
umPerBbi = MAX_SYNC_USER_1200 DS1_DELTA_SHIFT
1.58.173 Principles
1) Check the value of MaxSyncUserNumPerBbi under GLOBALPROCSWITCH from LMT.XML file. If MaxSyncUserNumPerBbi = 0, it
indicates that Maximum Sync-User Number Per BBI is 1200 (MAX_SYNC_USER_1200), go to next step, or end.
2) Check the value of DeltaShift under PUCCHCFG. If DeltaShift ≠ 1 (DS2_DELTA_SHIFT), output this cell’s related information as an
exception.
1.58.174 Measures
MOD PUCCHCFG: LocalCellId=0, DeltaShift=DS2_DELTA_SHIFT.

21465979/PBI1-6149576
1.58.175 Reference
None.
Note: This rule is just for eRAN8.1 and eRAN11.0 and eRAN11.1.
3.89 Fixed Configuration of PUCCH Resource
1.58.176 Location

09 Big Traffic Inspection 04 Enhance Reliability of PUCCH 07 Fixed Configuration of PUCCH Resource
Fixed configuration of PUCCH resource could avoid the PUCCH frequency domain resource overlapping with its intra-frequency neighboring
cells, which could lower the interference from the PUSCH of neighboring cells to PUCCH of local cells and demodulation performance of PUCCH will
increase. However, it will add the overhead of PUCCH resource and uplink volume will be affected at the same time.
1) Output eNodeBs’ related information if its current network configuration is inconsistent with the recommended value.
Current Network Configuration Check

eNodeB eNodeB Local Cell Cell CA or DL SPS
Cell Name DeltaShift Current Network Configuration
ID Name ID Bandwidth Scenario
CELLALGOSWITCH: PucchAlgoSwitch=PucchSwitch-
DS1_DELTA no-CA & no- 1;

414 VoLTE414 1 cell1 10M
_SHIFT DLSPS PUCCHCFG: CqiRbNum = 1, NaSriChNum = 6;
RACHCFG: PrachFreqOffset = 6;
2) Output the relationship between PUCCH resource (CQI RB Number, NaSriChNum, PUCCH RB Number) and “Cell Bandwidth, DeltaShift, CA
or DL SPS scenario”.
Fixed Configuration of PUCCH Resource

Cell CA or DL SPS CqiRb NaSriCh PUCCH
DeltaShift
Bandwidth Scenario Num Num RB
5M DS1_DELTA_SHIFT CA & DLSPS 3 77 8

5M DS1_DELTA_SHIFT CA Only 3 57 8
5M DS1_DELTA_SHIFT DLSPS Only 3 45 8
no-CA & no-

5M DS1_DELTA_SHIFT 3 25 6
DLSPS
no-CA & no-

DLSPS
no-CA & no-

DLSPS
no-CA & no-

DLSPS
no-CA & no-

DLSPS
no-CA & no-

DLSPS

no-CA & no-

DLSPS
no-CA & no-

DLSPS
Note: Preconditions mean “Cell Bandwidth, DeltaShift, CA or DL SPS scenario” and recommended value means “Number of CQI RB,
NaSriChNum, PUCCH RB” indicators.
1.58.178 Principles
1) Check whether “Cell Bandwidth, DeltaShift, CA or DL SPS scenario” meet the preconditions in the “Fixed Configuration of PUCCH Resource”
table. If yes, go to next step, or end.
 Cell Bandwidth: Check the value of DlBandWidth under Cell. If DlBandWidth= 2, it indicates that cell bandwidth is 5M. If DlBandWidth =
3, it indicates that cell bandwidth is 10M. If DlBandWidth = 4, it indicates cell bandwidth is 15M. If DlBandWidth = 5, it indicates cell
bandwidth is 20M.
 DeltaShift: Check the value of DeltaShift under PUCCHCFG. If DeltaShift=0, it indicates DeltaShif is DS1_DELTA_SHIFT (ds1). If
DeltaShift=1, it indicates DeltaShif is DS2_DELTA_SHIFT (ds2).
 CA or DL SPS scenario:
CA scenario: If a) or b) is met, it is considered as CA scenario.
a) Check the value of CaAlgoSwitch under ENODEBALGOSWITCH and its bit4 (freqcfgswitch) = 1 and PccDlEarfcn under
SCCFREQCFG has a value.
b) localcellid under CAGROUPSCELLCFG has a value.
DL SPS scenario: Check the value of DlSchSwitch under CELLALGOSWITCH, convert it into a binary number and its bit2 = 1.
2) Check whether “Number of CQI RB, NaSriChNum, PUCCH RB” meet the recommended value in the “Fixed Configuration of PUCCH
Resource” table. If no, output related information, or end.

 CQI RB Number: Check the value of CqiRbNum under PUCCHCFG.
 NaSriChNum: Check the value of NaSriChNum under PUCCHCFG.
 PUCCH RB Number: Check the value of PrachFreqOffset under RACHCFG.
1.58.179 Measures
MOD CELLALGOSWITCH: LocalCellId=x, PucchAlgoSwitch=PucchSwitch-0;
MOD PUCCHCFG: LocalCellId=x, NaSriChNum=X, CqiRbNum=X. (The values of NaSriChNum and CqiRbNum are related with the
bandwidth, Fmt1x DS and other factors. Please find the details in the above table)
MOD RACHCFG: PrachFreqOffset=X; (Find the details in the above table).
21465979/PBI1-6149576
1.58.180 Reference
None.
3.90 Reset PDCP DiscardTimer to Default Value When Timeout
1.58.181 Location

09 Big Traffic Inspection 04 Lower Retransmission Overhead of Uu Interface 01 Reset PDCP DiscardTimer to Default Value When Timeout
When PDCP entry receives a packet, it begins to record the time. If it isn’t scheduled by mac when the time exceeds the length of Pdcp Discard
Timer, the packet will be discard. In big traffic scenario, some users can't be scheduled in a long time due to too many users, which will lead to packet loss,
retransmission and additional consumption to the Uu interface resource.
Check the RLCPDCPPARAGROUP only when QCI = 6, 8 and 9. This rule is mainly used to collect eNodeBs’ related information with this risk.

Reset PDCP DiscardTimer to Default Value When Timeout

QCI Reset PDCP DiscardTimer to
Default Value When Timeout
QCI6 // QCI8 //
MOD RLCPDCPPARAGROUP:
115325 EAA325
QCI9
DiscardTimer = DiscardTimer_100.
1.58.183 Principles
From LMT.XML file:
1) Check the value of QCI under STANDARDQCI and record the value of RlcPdcpParaGroupId when QCI = 6, 8 and 9.
2) Find the value of DiscardTimer under RlcPdcpParaGroup, which corresponds with same RlcPdcpParaGroupId from 1). If DiscardTimer = 7, it
indicates that the length of the PDCP discard timer is infinity.
3) If DiscardTimer ≠ 7, output this eNodeBs’ related information and corresponding modifications.
1.58.184 Measures
MOD RLCPDCPPARAGROUP: DiscardTimer = DiscardTimer_Infinity. (Pay attention to the parameter’s reference relationship: Set the value
of DiscardTimer under RLCPDCPPARAGROUP and refer the corresponding RLCPDCPPARAGROUP under STANDARDQCI).
21465979/PBI1-6149576
1.58.185 Reference
None.
3.91 PUSCH DTX Supported Check
1.58.186 Location

09 Big Traffic Inspection 04 Lower Retransmission Overhead of Uu Interface 02 PUSCH DTX Supported Check

If missing detection of DCI0 by UE or SR false alarm in DRX state occur, it will lead to repeated uplink retransmission, wasted uplink PUSCH
resource and greatly increased uplink error code rate if this optimization item doesn’t turn on. After turning on this optimization item, the next schedule of
HARQ makes initially transmission scheduling when the eNodeB inspects the uplink DTX. It redelivers uplink schedule authorization, instead of starting
HARQ retransmission. If the authorization has been delivered twice and it still can detect DTX, stop this SR schedule to avoid the missing detection of
DCI0 by UE or uplink retransmission consumption caused by SR false alarm in DRX state. Both C and D board should support this optimization item.
Positive gain: Suppress retransmission overhead caused by SR false alarm and improve the uplink & downlink cell and the user throughput rate.
This rule is mainly used to collect cells’ related information with disabled PUSCH DTX switch.
1) Output cells’ related information with disabled PUSCH DTX switch.
PUSCH DTX Supported Check

eNodeB ID eNodeB Name Local Cell ID PUSCH DTX Supported Check
MOD CELLALGOSWITCH : LocalCellId =

5048 KPI02_48 0
0, UlSchSwitch = PuschDtxSwitch-1;
1.58.188 Principles
1) Check the value of UlSchSwitch under CellAlgoSwitch from LMT.XML file.
a) If bit7 = 1, it indicates that PUSCH DTX switch is enabled and end.
b) If bit7 = 0, it indicates that PUSCH DTX switch is disabled and go to step 3).
1.58.189 Measures
MOD CELLALGOSWITCH: LocalCellId = x, UlSchSwitch = PuschDtxSwitch-1.
21465979/PBI1-6149576

1.58.190 Reference
None.
3.92 Optimization of SR Rescheduling
1.58.191 Location

09 Big Traffic Inspection 04 Lower Retransmission Overhead of Uu Interface 03 Optimization of SR Rescheduling
If SR scheduling detection is PUSCH DTX, it will stop rescheduling the subsequent SR. If SR scheduling detection is NACK and the number of
HARQ retransmissions for a SR reaches the maximum value but the scheduling still fails but still can’t transmit successfully, the later twice SR scheduling
will be made during the On Duration timer for the DRX long cycle starts when DRX is turned on. This rule is mainly used to collect cell’s related
information with disabled UlEnhancedSrSchSwitch.
1) Output cells’ related information with disabled UlEnhancedSrSchSwitch.
Optimization of SR Rescheduling
eNodeB
eNodeB ID Local Cell ID Optimization of SR Rescheduling
Name

300 2T8R 0
UlSchSwitch = UlEnhancedSrSchSwitch-1;
1.58.193 Principles
1) Check the value of DrxAlgSwitch under DRX from LMT.XML file. If DrxAlgSwitch = 1, it indicates DRX algorithm switch is enabled. Go to
step 2), or end.
2) Check the value of UlSchSwitch under CellAlgoSwitch.
a) If bit10 = 1, it indicates that UlEnhancedSrSchSwitch is enabled and end.
b) If bit10 = 0, it indicates that UlEnhancedSrSchSwitch is disabled and go to step 4).

1.58.194 Measures
MOD CELLALGOSWITCH: LocalCellId = x, UlSchSwitch = UlEnhancedSrSchSwitch -1.
21465979/PBI1-6149576
1.58.195 Reference
None.
3.93 Lower Retransmission Overhead of Special Signaling
1.58.196 Location

09 Big Traffic Inspection 04 Lower Retransmission Overhead of Uu Interface 04 Lower Retransmission Overhead of Special Signaling
After certain terminals received inter-RAT handover command, they don’t reply the handover RLC state report to the eNodeB, but access the
target directly. Therefore, the eNodeB will retransmit the state report repeatedly, wasting the Uu interface resource. After this optimization is enabled, it
will reduce RLC retransmission times of inter-RAT handover command to 2, which reduces the retransmission consumption, saves the Uu interface
resource and increases downlink cell and users’ throughput rate. However, handover success rate of inter-RAT might decrease slightly. This rule is mainly
used to collect eNodeBs’ related information with disabled SPECSIGRETRANSOPTSWITCH.
1) Output eNodeBs’ related information with disabled SPECSIGRETRANSOPTSWITCH.
Lower Retransmission Overhead of Special Signaling

eNodeB ID eNodeB Name Lower Retransmission Overhead of Special Signaling
MOD ENODEBALGOSWITCH : HighLoadNetOptSwitch =

300 2T8R
SPECSIGRETRANSOPTSWITCH-1;
1.58.198 Principles
1) Check the value of HighLoadNetOptSwitch under ENodeBAlgoSwitch from LMT.XML file.

a) If bit0 = 1, it indicates SPECSIGRETRANSOPTSWITCH is enabled and end.
b) If bit0 = 0, it indicates SPECSIGRETRANSOPTSWITCH is disabled and go to step 3).
Note: For eRAN6.0 version, step 1) is checking the value of RsvdSwPara0 under eNBRsvdPara. If RsvdSwPara0_bit27 = 0, output this
eNodeB’s related information.
1.58.199 Measures
eRAN6.0: MOD ENBRSVDPARA: RsvdSwPara0=RsvdSwPara0_bit27-1.
eRAN7.0, eRAN8.0, eRAN8.1, eRAN11.0: MOD ENODEBALGOSWITCH：HighLoadNetOptSwitch = SPECSIGRETRANSOPTSWITCH-1.
21465979/PBI1-6149576
1.58.200 Reference
None.
Note: This rule is just for eRAN6.0 (eRAN6.0 SPC272 and its later version), eRAN7.0 (eRAN7.0SPC150 and its later version), eRAN8.0, eRAN8.1 and eRAN11.0.
3.94 Solve UE Lost Scheduling Problems
1.58.201 Location

09 Big Traffic Inspection 04 Lower Retransmission Overhead of Uu Interface 05 Solve UE Lost Scheduling Problems
During the service, the RBLER will become relatively high if the link become abnormal suddenly (the user removes the card or enters the weak
coverage area) because the eNodeB doesn't have the mechanism of identifying whether the link is abnormal and it will not stop scheduling this user. When
AbnUeSchSwitch is enabled, it will increase a mechanism counting the abnormal uplink and downlink. When it detects the UE is abnormal, it will stop
scheduling. When it detects the link is recovered, it will recover the scheduling. This optimization will save Uu interface resource overhead caused by
abnormal terminal scheduling repeatedly. However, Uu interface transmission delay may increase for weak coverage users. This rule is mainly used to
collect cells’ related information with disabled AbnUeSchSwitch.
1) Output cells’ related information with disabled AbnUeSchSwitch.
Solve UE Lost Scheduling Problems

eNodeB ID eNodeB Name Local Cell ID Solve UE Lost Scheduling Problems
300 2T8R 0
CellSchStrategySwitch = AbnUeSchSwitch-1;
1.58.203 Principles
1) Check the value of CellSchStrategySwitch under CellAlgoSwitch from LMT.XML file.
a) If bit0 = 1, it indicates that AbnUeSchSwitch is enabled and end.
b) If bit0 = 0, it indicates that AbnUeSchSwitch is disabled and go to step 3).
1.58.204 Measures
MOD CELLALGOSWITCH: LocalCellId = x, CellSchStrategySwitch = AbnUeSchSwitch-1.
21465979/PBI1-6149576
1.58.205 Reference
None.
Note: This rule is just for eRAN7.0 (eRAN7.0SPC040 and its later version), eRAN8.0 and eRAN11.0.
3.95 DRB RLC Parameter Adaptive
1.58.206 Location

09 Big Traffic Inspection 05 Lower Overhead of RLC State Report 01 DRB RLC Parameter Adaptive
In big traffic scenario, the Uu interface will become congested with increasing traffic volume and the delay of RLC state report and scheduling of
Polling packet will increase, which may exceed the barred timer of RLC state report and Polling retransmission timer, leading to unnecessary
retransmission of state report and Polling packet and wasted Uu interface resource. If RLC mode selection is AM and RlcParaAdaptSwitch is enabled,
barred timer of RCL state report and Polling retransmission timer can be elongated automatically based on the number of online users to reduce the
overhead of Uu interface resource. This rule is mainly used to collect cells’ related information with disabled RlcParaAdaptSwitch.
1) Output eNodeBs’ related information with disabled RlcParaAdaptSwitch.
DRB RLC Parameter Adaptive

eNodeB ID eNodeB Name DRB RLC Parameter Adaptive
MOD RLCPDCPPARAGROUP: RlcPdcpParaGroupId = 0,

300 2T8R
RlcMode = RlcMode_AM, RlcParaAdaptSwitch = ON.
1.58.208 Principles
1) Check the value of RlcMode and RlcParaAdaptSwitch under RlcPdcpParaGroup from LMT.XML file.
a) If RlcMode=1, it indicates that RLC mode selection is AM.
b) If RlcParaAdaptSwitch=1, it indicates RLC parameter adaptive switch is on.
2) If the values of these parameters don’t meet any conditions in 1), output this eNodeB’s information and corresponding modifications. Or end.
1.58.209 Measures
MOD RLCPDCPPARAGROUP: RlcMode = RlcMode_AM, RlcParaAdaptSwitch = ON.
21465979/PBI1-6149576
1.58.210 Reference
None.
Note: This rule is just for eRAN7.0 (eRAN7.0SPC150 and its later version), eRAN8.0, eRAN8.1, eRAN11.0 and eRAN11.1.

3.96 Round UP RBG
1.58.211Location

09 Big Traffic Inspection 06 PDCCH Efficiency Improvement 01 Round Up RBG
In the downlink scheduling, the current TTI will allocate N+1 RBG for the user to assure the data can be scheduled at one time if the RB number
which the user needed is between N and N+1. This rule is mainly used to collect cells’ related information which its RBG Resource Allocation Strategy is
not round up.
1) Output cells’ related information which its RBG Resource Allocation Strategy is not round up.
Round UP RBG
eNodeB ID eNodeB Name Local Cell ID Round UP RBG
MOD CELLDLSCHALGO : LocalCellId =
300 2T8R 0
0, RbgAllocStrategy = ROUND_UP;
1.58.213 Principles
1) Check the value of RbgAllocStrategy under CellDlschAlgo from LMT.XML file.
2) If RbgAllocStrategy=1, it indicates that Resource Allocation Strategy is round up.
3) If RbgAllocStrategy≠ 1, output this cell’s related information and corresponding modifications. Or end.
1.58.214 Measures
MOD CELLDLSCHALGO: LocalCellId = x, RBGALLOCSTRATEGY = ROUND_UP.
21465979/PBI1-6149576
1.58.215 Reference
None.

3.97 Balanced Scheduling between PDCCH & PDSCH
1.58.216 Location

09 Big Traffic Inspection 06 PDCCH Efficiency Improvement 02 Balanced Scheduling between PDCCH & PDSCH
In the big traffic scenario, the downlink schedule will choose one large packet user randomly and reserves PDCCH resource for it. When it
comes to the last user, downlink schedule distributes PDSCH resource for the chosen user to avoid that PDCCH is exhausted before PDSCH for scenarios
which small packets account for high percentage. This rule is mainly used to collect cells’ related information which their balanced PDCCH & PDSCH is
inconsistent with the recommended value.
1) Output cells’ related information which their balanced PDCCH & PDSCH is inconsistent with the recommended configuration.
Balanced Scheduling between PDCCH & PDSCH

eNodeB Balanced Scheduling between PDCCH &
eNodeB Name Local Cell ID
ID PDSCH
MOD ENBCELLRSVDPARA : LocalCellId = 0,

300 2T8R 0 DataThdInPdcchPdschBal = 17000,
UeNumThdInPdcchPdschBal = 100;
1.58.218 Principles
1) Check the value of DataThdInPdcchPdschBal and UeNumThdInPdcchPdschBal from LMT.XML file.
a) If DataThdInPdcchPdschBal = 17000, it indicates that data threshold in PDCCH and PDSCH Balance is 17000.
b) If UeNumThdInPdcchPdschBal = 100, it indicates that UE Num threshold in PDCCH and PDSCH Balance is 100.
2) If the above two parameters don’t meet the condition in 1), output this cell’s related information and corresponding modifications. Or end.
Note: For eRAN6.0SPC260 and its later eRAN6.0 versions, step 1) is checking the value of RsvdPara3 and RsvdPara12 under
eNBCellRsvdPara.
1.58.219 Measures
MOD CELLDLSCHALGO: LocalCellId = x, DataThdInPdcchPdschBal = 17000, UeNumThdInPdcchPdschBal = 100
For eRAN6.0SPC260 version: MOD ENBCELLRSVDPARA: LocalCellId=x, RsvdPara3 =17000, MOD ENBCELLRSVDPARA:

LocalCellId=x, RsvdPara12 =100.
21465979/PBI1-6149576
1.58.220 Reference
None.
Note: This rule is just for eRAN6.0 (eRAN6.0 SPC260 and its later version), eRAN7.0 and eRAN8.0.
3.98 PDCCH Efficiency Improvement in Initial Stage
1.58.221 Location
09 Big Traffic Inspection 06 PDCCH Efficiency Improvement 03 PDCCH Efficiency Improvement in Initial Stage
After turning PDCCH capacity improve switch on, it can increase PDCCH resource usage during setting up data radio bear in the initial access
period and optimize PDCCH distribution algorithm. If a UE fails to be allocated with CCEs, the eNodeB reallocates CCEs to the UE by increasing the
PDCCH power to decrease the PDCCH aggregation level for the UE, which will increase the total PDCCH resource usage. This rule is mainly used to
collect cells’ related information with disabled PDCCH capacity improve switch.
1) Output cells’ related information with disabled PDCCH capacity improve switch.
PDCCH Efficiency Improvement in Initial Stage

eNodeB ID eNodeB Name Local Cell ID PDCCH Efficiency Improvement in Initial Stage
MOD ENBCELLRSVDPARA : LocalCellId = 0,
300 2T8R 0
PdcchCapacityImproveSwitch = OFF;
1.58.223 Principles
1) Check the value of PdcchCapacityImproveSwitch under CellPdcchAlgo from LMT.XML file.
a) If PdcchCapacityImproveSwitch=1, it indicates that PDCCH capacity improve switch is enabled and end.

b) If PdcchCapacityImproveSwitch=0, it indicates that PDCCH capacity improve switch is disabled and go to step 2).
Note: For eRAN6.0SPC272 and its later versions, check the value of RsvdSwPara0 under eNBRsvdPara. If RsvdSwPara0_bit18 ≠ 1, output this
For eRAN8.1, eRAN11.0 and eRAN11.1, the name of this rule has been changed into PDCCH Capacity Improvement.
1.58.224 Measures
MOD CELLPDCCHALGO: LocalCellId = 0, PdcchCapacityImproveSwitch = ON (or MOD ENBCELLRSVDPARA:
LocalCellId=0，RsvdSwPara0=RsvdSwPara0_bit18-1).
21465979/PBI1-6149576
1.58.225 Reference
None.
Note: This rule is just for eRAN6.0 (eRAN6.0 SPC272 and its later version), eRAN7.0 (eRAN7.0SPC150 and its later version) and eRAN8.0.
3.99 Adaptive RBG
1.58.226 Location

09 Big Traffic Inspection 06 PDCCH Efficiency Improvement 04 Adaptive RBG
When resource allocation strategy is adaptive, downlink scheduling will increase. By reducing fragment scheduling, it can reduce CCE overhead,
increase downlink PRB usage and shorten the delay to increase downlink throughput. While, spectral efficiency will slightly decrease. This rule is mainly
used to collect cells’ related information if resource allocation strategy is not “adaptive”.
1) Output cells’ related information if resource allocation strategy is not “adaptive”.
Adaptive RBG

eNodeB ID eNodeB Name Local Cell ID Adaptive RBG
MOD CELLDLSCHALGO : LocalCellId

300 2T8R 0
= 0, RbgAllocStrategy = ADAPTIVE;
1.58.228 Principles
1) Check the value of RbgAllocStrategy under CellDlschAlgo from LMT.XML file.
2) If RbgAllocStrategy = 2, it indicates resource allocation strategy is “Adaptive”.
3) If RbgAllocStrategy ≠ 2, output this cell’s related information and corresponding modifications. Or end.
1.58.229 Measures
MOD CELLDLSCHALGO: LocalCellId = x, RbgAllocStrategy = ADAPTIVE.
21465979/PBI1-6149576
1.58.230 Reference
None.
Note: This rule is just for eRAN7.0 (eRAN7.0SPC040 and its later version), eRAN8.0, eRAN11.0 and eRAN11.1.
3.100 Increase Priority of Access Signaling Scheduling
1.58.231 Location

09 Big Traffic Inspection 07 Ensure Basic KPI in Congestion Scenario 01 Increase Priority of Access Signaling Scheduling
When UlRaUserSchOptSw is enabled, it could identify the Uu interface signaling of access flow (including RRC and ERAB setup period),
improve the scheduling priority and increase the access success rate in the congested Uu interface scenario. However, the uplink & downlink cell and the
user experience rate may drop because the access signaling will preempt the resource. This rule is mainly used to collect cells’ related information with

disabled UlRaUserSchOptSw.
1) Output cells’ related information with disabled UlRaUserSchOptSw.
Increase Priority of Access Signaling Scheduling
eNodeB ID eNodeB Name Local Cell ID Increase Priority of Access Signaling Scheduling

300 2T8R 0
UlSchSwitch = UlRaUserSchOptSw-1;
1.58.233 Principles
1) Check the value of UlSchSwitch under CellAlgoSwitch from LMT.XML file.
a) If bit18 = 1, it indicates that UlRaUserSchOptSw is enabled and end.
b) If bit18 = 0, it indicates that UlRaUserSchOptSw is disabled and go to step 3).
3) Output this cell’s related information and corresponding modifications
1.58.234 Measures
MOD CELLALGOSWITCH: LocalCellId = x, UlSchSwitch = UlRaUserSchOptSw-1.
21465979/PBI1-6149576
1.58.235 Reference
None.
Note: This rule is just for eRAN7.0 (eRAN7.0SPC150 and its later version) and eRAN8.0.
3.101 Avoid the Conflict of GAP Measurement and SR when DRX Is Disabled
1.58.236 Location

09 Big Traffic Inspection 07 Ensure Basic KPI in Congestion Scenario 02 Avoid the Conflict of GAP Measurement and SR when DRX Is Disabled

With the increasing traffic volume, SR period fits the adjustment automatically. Some users' SR period may overlap with GAP period, which
indicates the reporting time of SR is in GAP period, resulting in a failure of data transmission which triggers this SR because SR can’t be reported. If it is
triggered by RLC state report, numbers of RLC retransmission will reach the maximum value and call drop will occur. This optimization will avoid this
problem when DRX is disabled. This rule is mainly used to collect cells’ related information with disabled BasedSriGapOptSwitch.
1) Output cells’ related information with disabled BasedSriGapOptSwitch.
Avoid the Conflict of GAP Measurement and SR when DRX Is Disabled
eNodeB ID eNodeB Name Avoid the Conflict of GAP Measurement and SR when DRX Is Disabled
MOD ENODEBALGOSWITCH : HoCommOptSwitch = BasedSriGapOptSwitch-

5021 SON-tangwei21
1;
1.58.238 Principles
1) Check the value of DrxAlgSwitch under DRX from LMT.XML file. If DrxAlgSwitch = 0, it indicates DRX algorithm switch is disabled, go to
step 2), or end.
2) Check the value of HoCommOptSwitch under ENodeBAlgoSwitch from LMT.XML file.
a) If bit0 = 1, it indicates that BasedSriGapOptSwitch is enabled and end.
b) If bit0 = 0, it indicates that BasedSriGapOptSwitch is disabled and go to step 4).
Note: For eRAN6.0 and 6.1 version, check the value of RsvdSwPara0 under eNBRsvdPara in the step 1). If RsvdSwPara0_bit19 ≠ 1, output this
1.58.239 Measures
MOD ENODEBALGOSWITCH: HoCommOptSwitch = BasedSriGapOptSwitch-1(Or MOD ENBRSVDPARA：RsvdSwPara0 =
RsvdSwPara0_bit19-1).
21465979/PBI1-6149576

1.58.240 Reference
None.
3.102 Avoid the Conflict of GAP Measurement and SR when DRX Is Enabled
1.58.241 Location

09 Big Traffic Inspection 07 Ensure Basic KPI in Congestion Scenario 03 Avoid the Conflict of GAP Measurement and SR when DRX Is Enabled
With the increasing traffic volume, SR period fits the adjustment automatically. Some users' SR period may overlap with GAP period, which
indicates the reporting time of SR is in GAP period, resulting in a failure of data transmission which triggers this SR because SR can’t be reported. If it is
triggered by RLC state report, numbers of RLC retransmission will reach the maximum value and call drop will occur. This optimization will avoid this
problem when DRX is enabled. This rule is mainly used to collect cells’ related information with disabled DrxBasedSriGapOptSwitch.
1) Output cells’ related information with disabled DrxBasedSriGapOptSwitch.
Avoid the Conflict of GAP Measurement and SR when DRX Is Enabled

eNodeB eNodeB Avoid the Conflict of GAP Measurement and SR
ID Name when DRX Is Enabled

MOD ENODEBALGOSWITCH :
300 2T8R
HoCommOptSwitch = DrxBasedSriGapOptSwitch-1;
1.58.243 Principles
1) Check the value of DrxAlgSwitch under DRX from LMT.XML file. If DrxAlgSwitch = 1, it indicates DRX algorithm switch is enabled, go to
step 2), or end.
2) Check the value of HoCommOptSwitch under ENodeBAlgoSwitch from LMT.XML file.
a) If bit2 = 1, it indicates that DrxBasedSriGapOptSwitch is enabled and end.
b) If bit2 = 0, it indicates that DrxBasedSriGapOptSwitch is disabled and go to step 4).

4) Output this cell’s related information and corresponding modifications
1.58.244 Measures
MOD ENODEBALGOSWITCH: HoCommOptSwitch = DrxBasedSriGapOptSwitch-1(eRAN8.0, eRAN8.1, eRAN11.0).
MOD ENBRSVDPARA: RsvdSwPara1 = RsvdSwPara1_bit17-1(eRAN7.0).
21465979/PBI1-6149576
1.58.245 Reference
None.
Note: This rule is just for eRAN7.0 (eRAN7.0SPC160 and its later version), eRAN8.0, eRAN11.0 and eRAN11.1.
3.103 Non High-Speed Railway Scenario
1.58.246 Location

09 Big Traffic Inspection 08 Scheduled Optimization Strategy 01 Non High-Speed Railway Scenario
This rule is used to check whether cells configured as non-high-speed railway mode implement scheduled optimization strategy, which can
ensure the timing performance and minimize Uu interface overhead of timing. Therefore, it is recommended to implement it. Different collocations of
software versions and BBP types need different optimizations. This rule is mainly used to collect non high-speed railway cells’ related information without
scheduled optimization strategy.
eRAN6.0 version:
1) Output cells’ related information which meet the condition of sub scenario one (versions before eRAN6.0SPC272 or sub-BBP is LBBPC).
Sub Scenario One

eNodeB ID eNodeB Name Local Cell ID Enable SRS
62727 K2727 3 MOD SRSCFG : LocalCellId = 3, SrsCfgInd = BOOLEAN_TRUE;
2) Output cells’ related information which meet the condition of sub scenario two (versions between eRAN6.0SPC272 (contained) and

eRAN6.0SPC290 and sub-BBP is not LBBPC).
Sub Scenario Two

eNodeB eNodeB Local Timing Advance Command
Set TATimer to Infinity Adaptive SRS Allocation
ID Name Cell ID Optimization
MOD TATIMER : MOD SRSCFG : LocalCellId = 1, MOD TATIMER :
LocalCellId = 1, SrsCfgInd = BOOLEAN_TRUE; MOD LocalCellId = 1,

62085 J2085 1
TimeAlignmentTimer = ENBCELLRSVDPARA : LocalCellId = 1, TimingAdvCmdOptSwitch =
INFINITY; RsvdSwPara0 = RsvdSwPara0_bit19-1; ON;

3) Output cells’ related information which meet the condition of sub scenario three (eRAN6.0SPC290 and its later versions and sub-BBP is not
LBBPC).
Sub Scenario Three

eNod eNodeB Local Timing Resource
Adaptive SRS Allocation Set TATimer to Infinity
eB ID Name Cell ID Optimization
MOD SRSCFG : LocalCellId = 3,

MOD ENBCELLRSVDPARA : MOD TATIMER : LocalCellId
SrsCfgInd = BOOLEAN_TRUE; MOD
62097 H2097 3 LocalCellId = 3 , RsvdSwPara0 = 3, TimeAlignmentTimer =
ENBCELLRSVDPARA : LocalCellId = 3,
= RsvdSwPara0_bit20-1; INFINITY;
RsvdSwPara0 = RsvdSwPara0_bit19-1;
4) Output cells’ related information which their version or board information is missing (No information of sub version).
Cells without Matching Sub Scenarios

eNodeB ID eNodeB Name Local Cell ID Missing Information
50017 T157 0 Board
eRAN7.0 version:
Sub Scenario One

Enable SRS Set TATimer to SF10240
MOD TATIMER : MOD TATIMER :
MOD SRSCFG : LocalCellId
LocalCellId = 0, LocalCellId = 0,
60164 eNodeB26 0 = 0, SrsCfgInd =
TimeAlignmentTimer = TimingAdvCmdOptSwitch =
BOOLEAN_TRUE;
SF10240; ON;

2) Output cells’ related information which meet the condition of sub scenario two (eRAN7.0SPC150 and its later versions and sub-BBP is not
LBBPC).
Sub Scenario Two

eNodeB eNodeB Local Timing Resource Set TATimer to
Adaptive SRS Allocation
ID Name Cell ID Optimization Infinity
MOD MOD
ENBCELLRSVDPARA : TATIMER :
TMO- SrsCfgInd = BOOLEAN_TRUE; MOD
5015 0 LocalCellId = 0 , LocalCellId = 0,
5015 ENBCELLRSVDPARA : LocalCellId = 0,
RsvdSwPara0 = TimeAlignmentTi
RsvdSwPara0 = RsvdSwPara0_bit19-1;
RsvdSwPara0_bit20-1; mer = INFINITY;

5047 B47 10 Board
eRAN8.0 version:
Sub Scenario One

Enable SRS Set TATimer to SF10240
MOD SRSCFG :
300 2T8R 1 LocalCellId = 1, SrsCfgInd
TimeAlignmentTimer = TimingAdvCmdOptSwitch =
= BOOLEAN_TRUE;
SF10240; ON;
2) Output cells’ related information which meet the condition of sub scenario two (eRAN8.0SPC030 and its later versions and sub-BBP is not
LBBPC).
Sub Scenario Two

eNodeB eNodeB Local Timing Resource
Adaptive SRS Allocation Set TATimer to Infinity


6127 B127 0 SrsCfgInd = BOOLEAN_TRUE,
TimingResOptSwitch TimeAlignmentTimer =
FddSrsCfgMode = ADAPTIVEMODE;
= ON; INFINITY;

5049 KPI02_49 0 Board
Note: Details of each sub scenario are in the below table.
1.58.248 Principles
1) Check the value of SWVERSION under NE from LMT.XML file.
2) Check whether there is LBBPC under Type in dsp_brdmfrinfo.txt file. If yes, it indicates that sub-BBP is LBBPC.
3) Check corresponding cell’s ID in dsp_cell.txt file.
4) Check the value of parameters required by different scheduled optimization strategies and different versions of corresponding cells from
LMT.XML file.
Condition-based determination of each version is listed in the below table.
NE Version Ne Sub Version Conditions Table Details of Parameter

eRAN6.0 Sub Scenario One  Sub-BBP is LBBPC.
&
(Enable SRS)  The value of SrsCfgInd
Versions before Sub Scenario One

of the corresponding cell

eRAN6.0SPC272 (Enable SRS)
under SRSCFG ≠ 1.
eRAN6.0SPC272 Sub Scenario Two
 The value of
~  but not  (Set TA Timer
TimeAlignmentTimer of
eRAN6.0 Versions before to infinity)
the corresponding cell
Sub Scenario Two
eRAN6.0SPC290
 or  but
under TATIMER ≠ 7.
(Adaptive SRS
not   Bit19 of the value of
Allocation)
Sub Scenario Two RsvdSwPara0 under
 but not  (Timing advance ENBCELLRSVDPARA ≠
command 1.

optimization) 
Sub Scenario
 or  but TimingAdvCmdOptSwitch
eRAN6.0SPC290 Three (Adaptive
not  ≠ 1 under TATIMER.
and its later SRS Allocation)
 Bit20 of the value of
Sub Scenario
versions
RsvdSwPara0 under
Three (Timing
 but not  ENBCELLRSVDPARA ≠
resource
1.
optimization)
 The value of
Sub Scenario
TimeAlignmentTimer of
 but not  Three (Set TA
the corresponding cell
Timer to infinity)
eRAN7.0 eRAN7.0 Sub Scenario One under TATIMER ≠ 6.
&
eRAN8.0 eRAN8.0 (Enable SRS)  The value of
Versions before
FddSrsCfgMode of the
eRAN7.0SPC150, Sub Scenario One

corresponding cell under

Versions before (Enable SRS)
SRSCFG ≠ 1.
eRAN8.0SPC030
TimingResOptSwitch ≠ 1
eRAN7.0 Sub Scenario One
under TATIMER.
eRAN8.0 & (Set TATimer to
SF10240)
Versions before
Sub Scenario One
eRAN7.0SPC150,
 (Set TATimer to
Versions before
SF10240)
eRAN8.0SPC030
eRAN7.0 Sub Scenario One
eRAN8.0 (Timing advance

&
command
optimization)
Versions before  Sub Scenario One
eRAN7.0SPC150, (Timing advance
Versions before command

eRAN8.0SPC030 optimization)
eRAN7.0SPC150 Sub Scenario Two
 or  but
and its later (Adaptive SRS
not 
versions, Allocation)
Sub Scenario Two
eRAN8.0SPC030
 but not  (Timing resource

and its later
optimization)
versions
Sub Scenario Two
 but not  (Set TATimer to
infinity)
eRAN6.0 Cells without
eRAN7.0 Information of Ne sub-version or matching sub
eRAN8.0 sub-BBP is missing. scenario
1.58.249 Measures
1) Find the command descriptions in the above tables or executed MML commands in the overview of each sub scenario table. Detailed MML
commands are as follows:
 Enable SRS: MOD SRSCFG: LocalCellId = x, SrsCfgInd = BOOLEAN_TRUE~1.
 Set TATimer to infinity: MOD TATIMER: LocalCellId =x, TimeAlignmentTimer = INFINITY~7.
 Adaptive SRS Allocation: MOD SRSCFG : LocalCellId = x, SrsCfgInd = BOOLEAN_TRUE~1, or MOD ENBCELLRSVDPARA :
LocalCellId = 0, RsvdSwPara0 = RsvdSwPara0_bit19~1(eRAN6.0); MOD SRSCFG : LocalCellId = X, FddSrsCfgMode =
ADAPTIVEMODE~1(eRAN7.0, eRAN8.0)
 Timing advance command optimization: MOD TATIMER : LocalCellId = x, TimingAdvCmdOptSwitch = ON~1
 Timing resource optimization: MOD ENBCELLRSVDPARA: LocalCellId = 0, RsvdSwPara0 = RsvdSwPara0_bit20~1(eRAN6.0); MOD
TATIMER: LocalCellId = 0, TimingResOptSwitch = ON~1(eRAN7.0, eRAN8.0).
2) Refer to <LTE Heavy Traffic Precautions and Emergency Measures Guide-20150118-A-V4.0> which published on support:
21465979/PBI1-6149576

1.58.250 Reference
None.
Note: This rule is just for eRAN6.0, eRAN7.0, eRAN8.0, eRAN8.1, eRAN11.0 and eRAN11.1.
3.104 High-Speed Railway Scenario
3.104.1 Location

09 Big Traffic Inspection 08 Scheduled Optimization Strategy 02 High-Speed Railway Scenario
This rule is used to check whether cells configured as high-speed railway mode implement scheduled optimization strategy, which can ensure the
timing performance and minimize Uu interface overhead of timing. Therefore, it is recommended to implement it. Different collocations of software
versions and BBP types need different optimizations. This rule is mainly used to collect high-speed railway cells’ related information without scheduled
optimization strategy.
eRAN6.0 version:
1) Output high-speed railway cells’ related information.
High-Speed Railway Scenario

eNodeB
eNodeB ID Local Cell ID Enable SRS
Name
MOD SRSCFG : LocalCellId = 3, SrsCfgInd

62727 AK2727 3
= BOOLEAN_TRUE;
2) Output the overview of high-speed railway scenario, including the command name, principle, precaution, executed MML command and so on.
Overview of High-Speed Railway Scenario

Rollback MML (The command
Executed provided here is just for reference.
Command Imported Prio
Principle Precaution Level MML Parameters should rollback based License
Name Version rity
Command on the configuration of the
network)
In big traffic MOD

Enable SRS volume with Null ALL Cell High SRSCFG : Null
SrsCfgInd = X;
excessive users LocalCellId

scenario,
enabled SRS = 0,
could reduce SrsCfgInd =
the scheduling BOOLEAN
overhead of _TRUE
DMRS TA.
eRAN7.0 version:
High-Speed Railway Scenario

eNodeB eNodeB Local Set TA Timer to
Enable SRS Timing Advance Command Optimization
ID Name Cell ID SF10240
MOD SRSCFG : MOD TATIMER :
LocalCellId = 1, LocalCellId = 1, MOD TATIMER : LocalCellId = 1,
50012 eB214 1
SrsCfgInd = TimeAlignmentTimer TimingAdvCmdOptSwitch = ON;
BOOLEAN_TRUE; = SF10240;

Rollback MML (The
command provided
here is just for
Command Precautio Imported Executed MML reference.
Principle Level Priority Licenses
Name n Version Command Parameters should
rollback based on
the configuration of
the network)
In big traffic
volume with
excessive users MOD SRSCFG :
MOD SRSCFG :
scenario, opening LocalCellId = 0,
Enable SRS Null ALL Cell High LocalCellId = 1, Null
SRS could reduce SrsCfgInd =
SrsCfgInd = X;
the scheduling BOOLEAN_TRUE
overhead of
DMRS TA.
Set The overhead of Null ALL Cell High MOD TATIMER : MOD TATIMER : Null
TATimer to Uu interface LocalCellId = 0, LocalCellId = 1,
SF10240 reduces as the TimeAlignmentTim TimeAlignmentTimer
reduced numbers er = SF10240; = X;
of TA adjustment
command

delivered.
Optimize the
method of TA
adjustment
Timing commend
advance delivered to
command reduce the Null ALL Cell High Null
TimingAdvCmdOpt TimingAdvCmdOptS
optimizatio overhead of Uu
Switch = ON; witch = X;
n interface as
reduced numbers
of command
delivered.
eRAN8.0 version:
High Speed-Railway Scenario

eNodeB Set TATimer to Timing Advance
eNodeB ID Local Cell ID Enable SRS
Name SF10240 Command Optimization
MOD SRSCFG : MOD TATIMER : MOD TATIMER :
LocalCellId = 0, LocalCellId = 0, LocalCellId = 0,
50400 CLOUD 1 0
SrsCfgInd = TimeAlignmentTimer = TimingAdvCmdOptSwitch
BOOLEAN_TRUE; SF10240; = ON;

Rollback MML (The
command provided here
Executed is just for reference.
Command Precautio Imported
Principle Level Priority MML Parameters should Licenses
Name n Version
Command rollback based on the
configuration of the
network)
In big traffic
volume with MOD
excessive users SRSCFG :
MOD SRSCFG :
scenario, opening LocalCellId =
Enable SRS Null ALL Cell High LocalCellId = 1, Null
SRS could reduce 0, SrsCfgInd =
SrsCfgInd = X;
the scheduling BOOLEAN_T
overhead of DMRS RUE
TA.
Set The overhead of Null ALL Cell High MOD MOD TATIMER : Null

Uu interface TATIMER :
reduces as the LocalCellId =
LocalCellId = 1,
TATimer to reduced numbers of 0,
TimeAlignmentTimer =
SF10240 TA adjustment TimeAlignme
X;
command ntTimer =
delivered. SF10240;
Optimize the
method of TA
MOD
adjustment
Timing TATIMER :
commend delivered MOD TATIMER :
advance LocalCellId =
to reduce the LocalCellId = 1,
command Null ALL Cell High 0, Null
overhead of Uu TimingAdvCmdOptSwitc
optimizatio TimingAdvC
interface as h = X;
n mdOptSwitch
reduced numbers of
= ON;
command
delivered.
3.104.3 Principles
1) Check the value of SWVERSION under NE from LMT.XML file.
2) Check the value of parameters required by different scheduled optimization strategies and different versions of corresponding cells from
LMT.XML file.
Condition-based determination of each version is listed in the below table.
NE Version Condition Table Details of Parameter

High-speed railway  The value of SrsCfgInd of the
eRAN6.0 
scenario (Enable SRS)
corresponding cell under SRSCFG ≠ 1.
High-speed railway
  The value of TimeAlignmentTimer of the
scenario (Enable SRS)
High speed railway corresponding cell under TATIMER ≠ 6.
 scenario (Set TATimer  The value of TimingAdvCmdOptSwitch

eRAN7.0
eRAN8.0 to SF10240)
under TATIMER ≠ 1.
High speed railway
scenario (Timing

advance command
optimization)

3.104.4 Measures
1) Find the command descriptions in the above tables or executed MML commands in the overview of each sub scenario table. Detailed MML
commands are as follows:
 Enable SRS: MOD SRSCFG: LocalCellId = x, SrsCfgInd = BOOLEAN_TRUE~1.
 Set TATimer to SF10240: MOD TATIMER : LocalCellId =x, TimeAlignmentTimer = SF10240~6
 Timing advance command optimization: MOD TATIMER : LocalCellId = x, TimingAdvCmdOptSwitch = ON~1
2) Refer to <LTE Heavy Traffic Precautions and Emergency Measures Guide-20150118-A-V4.0> which published on support:
21465979/PBI1-6149576
3.104.5 Reference
None.
Note: This rule is just for eRAN6.0, eRAN7.0, eRAN8.0, eRAN8.1, eRAN11.0 and eRAN11.1.
3.105 Enable SRS
3.105.1 Location

09 Big Traffic Inspection 06 Scheduled Optimization Strategy 01 Enable SRS
In big traffic volume with excessive users scenario, enabled SRS could reduce the scheduling overhead of DMRS TA. This rule is mainly used to
collect cells’ related information if SRS configuration indicator is not “BOOLEAN_TURE”
1) Output cells’ related information if SRS configuration indicator is not “BOOLEAN_TURE”.
Enable SRS
eNodeB ID eNodeB Name Local Cell ID Enable SRS

630820 ----- 2
SrsCfgInd = BOOLEAN_TRUE;

3.105.3 Principles
1) Check the value of SrsCfgInd under SRSCfg from LMT.XML file.
2) If SrsCfgInd=1, it indicates that SRS configuration indicator is “BOOLEAN_TURE”.
3) If SrsCfgInd ≠ 1, output this cell’s related information and corresponding modifications. Or end.
3.105.4 Measures
MML command: MOD SRSCFG: LocalCellId = X, SrsCfgInd = BOOLEAN_TRUE~1.
21465979/PBI1-6149576
3.105.5 Reference
None.
3.106 QCI1 RLC/PDCP SN Size Optimization
3.106.1 Location

10 VOLTE Inspection 01 Optimize PDCP/RLC 01 QCI1 RLC/PDCP SN Size Optimization
Enlarging SN size of PDCP/RLC could reduce the chances of HFN number being changed, which would reduce continuous packet loss and
single pass due to mismatched HFN number in both sides. However, the entire network’s configuration must be consistent with the recommended value, or
it will have deteriorated packet loss rate and single pass when eNodeBs handover between two different SN sizes.
1) Output eNodeBs’ related information which their RlcMode, PdcpSnSize, UlRlcSnSize and DlRlcSnSize are inconsistent with the recommended
value.
Abnormal Data

eNodeB eNodeB RlcPdcpPa RLC Mode UM PDCP-SN Uplink RLC-SN Downlink RLC-SN
ID Name raGroupId Selection Size Size Size
301 301 0 RlcMode_UM PdcpSnsize_7bits RlcSnSize_size5 RlcSnSize_size5
3.106.3 Principles
From LMT.XML file:
1) Check the value of RlcPdcpParaGroupId corresponded with QCI1 under STANDARDQCI: Check the value of RlcPdcpParaGroupId under
STANDARDQCI corresponded with QCI = 1.
2) Check 4 parameters corresponded with RlcPdcpParaGroupId of QCI1 under RLCPDCPPARAGROUP: Check the value of RlcMode,
PdcpSnSize, UlRlcSnSize and DlRlcSnSize under RLCPDCPPARAGROUP with the same RlcPdcpParaGroupId from the step 1).
3) Output eNodeBs’ related information which their RlcMode, PdcpSnSize, UlRlcSnSize and DlRlcSnSize are inconsistent with the recommended
value.
Note: The recommended value of these four parameters are RlcMode = RlcMode_UM~2, PdcpSnSize = PdcpSnsize_12bits~1, UlRlcSnSize = RlcSnSize_size10~1 and
DlRlcSnSize = RlcSnSize_size10~1 respectively.
3.106.4 Measures
Set related parameters to recommended value: MOD RLCPDCPPARAGROUP: RlcPdcpParaGroupId=n, RlcMode=RlcMode_UM,
PdcpSnSize=PdcpSnsize_12bits, UlRlcSnSize=RlcSnSize_size10, DlRlcSnSize=RlcSnSize_size10.
3.106.5 Reference
None.
3.107 QCI5 PDCP Timer Optimization
3.107.1 Location

10 VOLTE Inspection 01 Optimize PDCP/RLC 02 QCI5 PDCP Timer Optimization

In order to ensure VOLTE users’ experience, DiscardTimer of QCI1 is set to 100ms. However, it should set to infinity for QCI5. In that way, SIP
signaling of QCI5 won’t be discarded due to the expiration of the PDCP DiscardTimer, poor quality channel and user experience can be improved and low
transmission power of terminals and fragmented SIP signaling packet problems can be solved.
1) Output eNodeBs’ related information if their DiscardTimer is not configured as DiscardTimer_Infinity.
Abnormal Data
QCI5 RLC PDCP
eNodeB ID eNodeB Name DiscardTimer
ParaGroupID
301 301 0 300
3.107.3 Principles
From LMT.XML file:
1) Check the value of RlcPdcpParaGroupId corresponded with QCI5 under STANDARDQCI: Check the value of RlcPdcpParaGroupId under
STANDARDQCI corresponded with QCI = 5.
2) Check the value of DiscardTimer corresponded with RlcPdcpParaGroupId of QCI5 under RLCPDCPPARAGROUP: Check the value of
DiscardTimer under RLCPDCPPARAGROUP with same RlcPdcpParaGroupId from the step 1).
3) Output eNodeBs’ related information if their DiscardTimer are not configured as DiscardTimer_Infinity.
Note: DiscardTimer = DiscardTimer_Infinity~7
3.107.4 Measures
Set related parameter to recommended value: MOD RLCPDCPPARAGROUP: RlcPdcpParaGroupId=m, DiscardTimer = DiscardTimer_Infinity.
3.107.5 Reference
None.

3.108 Uplink RLC Enhanced in Segments
3.108.1 Location

10 VOLTE Inspection 02 VOLTE Uplink Optimization Strategy 01 Uplink RLC Enhanced in Segments
The period of VOLTE packet transmission is 20ms. If the chosen TBS is less than the voice data packet due to the limit of UE’s uplink
transmission power in the edge of cells, segmented data packets will occur. Without limitation, the number of UL RLC segments for VOLTE users may be
larger than 20, which will block the transmission of next data packet, resulting in packet loss after the timeout. Therefore, the number of UL RLC segments
should be controlled. By controlling the number of segments, it can reduce the packet loss due to the expiration of the PDCP DiscardTimer and poor
quality channel.
1) Output eNodeBs’ related information if their UlVoipRlcMaxSegNum are not 20.
Abnormal Data
Local Cell
eNodeB ID eNodeB Name Cell Name UlVoipRlcMaxSegNum
ID
301 301 0 Cell0 10
3.108.3 Principles
1) Check the value of UlVoipRlcMaxSegNum under CELLULSCHALGO from LMT.XML file.
2) Output eNodeBs’ related information if their UlVoipRlcMaxSegNum are not 20.
3.108.4 Measures
Set related parameter to recommended value:
MOD CELLULSCHALGO: LocalCellId=x, UlVoipRlcMaxSegNum=20.
3.108.5 Reference
None.

3.109 Uplink Last Two Retransmission Schedule Optimization
3.109.1 Location

10 VOLTE Inspection 02 VOLTE Uplink Optimization Strategy 02 Uplink Last Two Retransmission Schedule Optimization
It will lead to small RBLER due to untimely adjusted AMC even in places with good signal and packet loss. If uplink last two retransmission
schedule optimization is enabled, retransmission success rate will increase and uplink RBLER will decrease, which will reduce the packet loss rate.
1) Output eNodeBs’ related information with disabled UlLast2RetransSchOptSwitch.
Abnormal Data
eNodeB Local Cell

eNodeB ID UlLast2RetransSchOptSwitch
Name Cell ID Name
301 301 0 Cell0 OFF
3.109.3 Principles
Find out eNodeBs with disabled UlLast2RetransSchOptSwitch from LMT.XML file.
eRAN7.0version: Check the value of RsvdSwPara1 under ENBCELLRSVDPARA, convert it into a binary number and bit6 = 0.
eRAN8.1version: Check the value of UlSchSwitch under CELLALGOSWITCH, convert it into a binary number and bit5 = 0.
3.109.4 Measures
Set related parameters to recommended value:
eRAN7.0version: MOD ENBCELLRSVDPARA: LocalCellId=x, RsvdSwPara1=RsvdSwPara1_bit6-1;
eRAN8.1version: MOD CELLALGOSWITCH: LocalCellId=x, UlSchSwitch=UlLast2RetransSchOptSwitch-1;
3.109.5 Reference
None.

3.110 Uplink Compensation Schedule
3.110.1Location

10 VOLTE Inspection 02 VOLTE Uplink Optimization Strategy 03 Uplink Compensation Schedule
The eNodeB will judge whether it is under silent period or talk spurt, and then schedule as each state’s minimal scheduling interval. If uplink
VoIP schedule optimization switch is selected, an uplink dynamic scheduling is triggered for VOLTE UEs adopting uplink dynamic scheduling when the
scheduling interval is greater than the uplink scheduling interval threshold. This ensures timely uplink scheduling on VOLTE UEs even when SR missing
detections occur, thereby avoiding packet loss caused by the expiration of the PDCP packet discarding timer. Therefore, it is recommended to enable it.
1) Output eNodeBs’ related information with disabled UlVoipSchOptSwitch.
Abnormal Data
eNodeB Cell
eNodeB ID Local Cell ID UlVoipSchOptSwitch
Name Name
301 301 0 Cell0 OFF
3.110.3Principles
Find out eNodeBs with disabled UlVoipSchOptSwitch from LMT.XML file.
eRAN7.0version: Check the value of RsvdSwPara1 under ENBCELLRSVDPARA, convert it into a binary number and bit20 = 0.
eRAN8.1version: Check the value of UlEnhencedVoipSchSw under CELLULSCHALGO, convert it into a binary number and bit3 = 0.
3.110.4Measures
eRAN8.1version: MOD CELLULSCHALGO: LocalCellId=x, UlEnhencedVoipSchSw = UlVoipSchOptSwitch-1;
3.110.5Reference
None.

3.111 Uplink Delay-based Dynamic Scheduling
3.111.1Location

10 VOLTE Inspection 02 VOLTE Uplink Optimization Strategy 04 Uplink Delay-based Dynamic Scheduling
When uplink delay-based dynamic scheduling is enabled, scheduling priorities are dynamically adjusted based on VoIP packet delays. Longer
waiting time indicates higher priority. In big traffic volume, cell reloading, higher SR missing detection rate or DRX scenarios, this optimization could
reduce packet loss rate (Under Beta test, nor recommended now).
1） Output cells’ related information if their UlDelaySchStrategy is not VOIP_DELAYSCH.
Abnormal Data
eNodeB ID eNodeB Name Local Cell ID Cell Name UlDelaySchStrategy
414 VoLTE414 0 cell0 NO_DELAYSCH
3.111.3Principles
1) Check the value of UlDelaySchStrategy under CELLULSCHALGO from LMT.XML file.
2) If UlDelaySchStrategy = 1, it indicates VOIP_DELAYSCH is enabled. Output cells’ related information if their UlDelaySchStrategy ≠ 1.
3.111.4Measures
Set related parameters to recommended value: MOD CELLULSCHALGO: LocalCellId=x, UlDelaySchStrategy=VOIP_DELAYSCH;
3.111.5Reference
None.

3.112 Optimization of Uplink Data Size Estimation
3.112.1Location

10 VOLTE Inspection 02 VOLTE Uplink Optimization Strategy 05 Optimization of Uplink Data Size Estimation
If this option is selected, the eNodeB estimates the uplink traffic volume more accurate that is dynamically scheduled for VOLTE services, which
shortens the VOLTE packet delay, reduces the packet loss rate, and improves the voice service quality under cell reloading, higher SR missing detection
rate and DRX scenarios (Under Beta test, nor recommended now).
1) Output eNodeBs’ related information with disabled UlVoLTEDataSizeEstSwitch.
Abnormal Data
eNodeB ID eNodeB Name Local Cell ID Cell Name UlVoLTEDataSizeEstSwitch
301 301 0 Cell0 OFF
3.112.3Principles
Find out disabled UlVoLTEDataSizeEstSwitch from LMT.XML file: Check the value of UlEnhencedVoipSchSw under CELLULSCHALGO,
convert it into a binary number and bit4 = 0.
3.112.4Measures
Set related parameters to recommended value: MOD CELLULSCHALGO: LocalCellId=x, UlEnhencedVoipSchSw =
UlVoLTEDataSizeEstSwitch-1;
3.112.5Reference
None.

3.113 ROHC
3.113.1Location

10 VOLTE Inspection 03 VOLTE Enhancement 01 ROHC
ROHC, enhanced feature of VOLTE, can increase coverage area and capacity. First commercial characteristic, active opening is not
recommended.
1) Output current network configuration data which is inconsistent with the recommended value.
Abnormal Data
eNodeB eNodeB RohcS Profile0x Profile0x Profile0x Profile0x
HighestMode
ID Name witch 0001 0002 0003 0004
O_MODE (Bi-
301 301 ON directional Enable Enable Disable Disable
Optimistic Mode)
3.113.3Principles
1) Check the value of RohcSwitch, HighestMode and Profiles from LMT.XML file.
 RohcSwitch =1, which indicates that ROHC function is enabled.
 HighestMode = 2, which indicates that the operating mode of ROHC is O_MODE (Bi-directional Optimistic Mode).
 Convert the value of Profiles into a binary number and its bit0&bit1 = 1 and bit2&bit3 = 0, which indicates that Profile0x0001 and
Profile0x0002 are enabled and Profile0x0003 and Profile0x0004 are disabled.
2) Mark it as abnormal and output this eNodeB’s related information if any conditions in 1) are not met.
3.113.4Measures
Set related parameters to recommended value: MOD PDCPROHCPARA: RohcSwitch=OFF, HighestMode = O_MODE, Profiles =
Profile0x0001-1&Profile0x0002-1&Profile0x0003-0&Profile0x0004-0.

3.113.5Reference
None.
3.114 TTI Bundling
3.114.1Location

10 VOLTE Inspection 03 VOLTE Enhancement 02 TTI Bundling
TTI bundling, enhanced feature of VOLTE, can increase coverage area and capacity. TTI bundling enables a data block to be transmitted in four
consecutive TTIs, which are bound together and treated as the same resource. Different HARQ redundancy versions of the same data block are transmitted
in different TTIs. TTI bundling makes full use of HARQ combining gains and reduces the number of retransmissions and time of RTT transmission. First
commercial characteristic, active opening is not recommended.
Output cells’ related information with enabled TTIBundlingSwitch.
Abnormal Data
eNodeB ID eNodeB Name Local Cell ID Cell Name TTI BundlingSwitch
301 301 0 Cell0 ON
3.114.3Principles
1) Check the value of UlSchSwitch under CELLALGOSWITCH from LMT.XML file and convert it into a binary number.
a) If bit4 = 0, it indicates TtiBundlingSwitch is off and end.
b) If bit4 = 1, it indicates TtiBundlingSwitch is on and go to step 2).
2) Count it as exception and output this eNodeB’s information.
3.114.4Measures
Set related parameters to recommended value: MOD CELLALGOSWITCH: LocalCellId=x, UlSchSwitch=TtiBundlingSwitch-0.

3.114.5Reference
None.
3.115 SPS
3.115.1Location

10 VOLTE Inspection 03 VOLTE Enhancement 03 SPS
SPS, enhanced feature of VOLTE, can increase coverage area and capacity. First commercial characteristic, active opening is not recommended.
1) Output cells’ related information if one of SpsSchSwitch (UlSchSwitch), SpsSchSwitch (DlSchSwitch), CloseLoopSpsSwitch or
PdschSpsPcSwitch is enabled.
Abnormal Data
eNode eNodeB Local Cell SpsSchSwitch SpsSchSwitch( CloseLoop PdschSps

B ID Name Cell ID Name (UlSchSwitch) DlSchSwitch) SpsSwitch PcSwitch
301 301 0 Cell0 ON ON ON ON
3.115.3Principles
1) Check the following parameters’ configuration from LMT.XML file and output them if they are inconsistent with the recommended value.
 Check the value of UlSchSwitch under CELLALGOSWITCH, convert it into a binary number and bit0 = 0, which indicates SpsSchSwitch
(UlSchSwitch) is off.
 Check the value of DlSchSwitch under CELLALGOSWITCH, convert it into a binary number and bit2 = 0, which indicates SpsSchSwitch
(DlSchSwitch) is off.
 Check the value of UlPcAlgoSwitch under CELLALGOSWITCH, convert it into a binary number and bit0 = 0, which indicates
CloseLoopSpsSwitch is off.
 Check the value of DlPcAlgoSwitch under CELLALGOSWITCH, convert it into a binary number and bit0 = 0, which indicates that
PdschSpsPcSwitch is off.

1) Mark it as abnormal and output this cell’s related information if any conditions in 1) are not met.
3.115.4Measures
Set related parameters to recommended value: MOD CELLALGOSWITCH: LocalCellId=x, UlSchSwitch = SpsSchSwitch-0, DlSchSwitch =
SpsSchSwitch-0, UlPcAlgoSwitch = CloseLoopSpsSwitch-0, DlPcAlgoSwitch = PdschSpsPcSwitch-0.
3.115.5Reference
None.
3.116 Downlink Last Two Retransmission Schedule Optimization
3.116.1Location

10 VOLTE Inspection 04 VOLTE Downlink Optimization Strategy 01 Downlink Last Two Retransmission Schedule Optimization
Enabled DlRetxTbsIndexAdjOptSwitch can increase retransmission success rate and reduce downlink RBLER, which could reduce the voice
packet loss rate, through last two retransmission schedule optimization.
1) Output eNodeBs’ related information with disabled DlRetxTbsIndexAdjOptSwitch.
Abnormal Data
eNodeB Local Cell Cell DlRetxTbsIndexA
eNodeB ID
Name ID Name djOptSwitch
301 301 0 Cell0 OFF
3.116.3Principles
Find out disabled DlRetxTbsIndexAdjOptSwitch from LMT.XML file.
eRAN7.0 version: Check the value of RsvdSwPara1 under ENBCELLRSVDPARA, convert it into a binary number and bit27 = 0.
eRAN8.1 version: Check the value of CqiAdjAlgoSwitch under CELLULSCHALGO, convert it into a binary number and bit8 = 0.

3.116.4Measures
eRAN8.1version: MOD CELLALGOSWITCH: LocalCellId=x, CqiAdjAlgoSwitch = DlRetxTbsIndexAdjOptSwitch-1.
3.116.5Reference
None.
3.117 TBS-Based Scheduling for Downlink VoIP
3.117.1Location

10 VOLTE Inspection 04 VOLTE Downlink Optimization Strategy 02 TBS-Based Scheduling for Downlink VoIP
When VoipTbsBasedMcsSelSwitch is selected, HARQ retransmission can be reduced in VoIP service and delay performance for users in
middle/near point will improved. Positive gain: Reduce IBLER.
1) Output eNodeBs’ related information with disabled VoipTbsBasedMcsSelSwitch.
Abnormal Data
eNodeB Local Cell
eNodeB ID VoipTbsBasedMcsSelSwitch
Name Cell ID Name
301 301 0 Cell0 OFF
3.117.3Principles
VoipTbsBasedMcsSelSwitch is off: Check the value of DlSchSwitch under CELLALGOSWITCH from LMT.XML file, convert it into a binary
number and its bit11 = 0.

3.117.4Measures
Set related parameters to recommended value: MOD CELLALGOSWITCH: LocalCellId=x, DlSchSwitch = VoipTbsBasedMcsSelSwitch-1.
3.117.5Reference
None.
3.118 Preallocation & SmartPreallocation
3.118.1Location

10 VOLTE Inspection 02 VOLTE Uplink Optimization Strategy 03 Preallocation & SmartPreallocation
Based on the live network analysis, voice quality was mainly affected by packets loss rate in uplink which caused by SRI detection failure on
PUCCH channel. If voice packets cannot be delivered on uplink successfully within 100ms due to SRI detection failure, the packets will be deleted on
PDCP layer on UE side (this is the QOS requirement for QCI1). Preallocation is an optimized scheduling method to avoid uplink voice data packets loss
caused by SRI detection failure, but preallocation cannot distinguish different QCI type, and cannot take effect in DRX scenarios, so Huawei introduces
smart preallocation function since eRAN7.0 to allow QCI1 user perform preallocation scheduling in DRX scenario(eRAN6.0 version only supports user
level’s smart preallocation). Positive gain: Avoid uplink voice data packets loss caused by SRI detection failure. Negative gain: Consume extra scheduling
resources.
1) Output cells’ related information with abnormal configured parameters.
Abnormal Data
SmartPreAll Preallo Preallo Preal SmartPr
Local Cell PreAllocatio PreAllocationS SmartPreAllocat
eNode eNodeB eNodeB ocationSwitc cationP cation locati eallocati
Cell Na nSwitch(Cell witch(CellPreA ionSwitch(CellP
B ID Name Version h(CellAlgoS araGro MinPer onSiz onDurat
ID me AlgoSwitch) llocGroup) reAllocGroup)
witch) upId iod e ion
50226 217 BTS390 1 cell2 ON OFF 2 ON ON 20 120 160
0 172
V100R0

09C00SP
C160B0
22
3.118.3Principles
1) QCI parameter is QCI1: Check the value of QCI under CELLSTANDARDQCI from LMT.XML file and QCI = 1. Record corresponding
LocalCellId and PreallocationParaGroupId.
2) Check the value of UlSchSwitch under CELLALGOSWITCH, corresponding with 1)’s LocalCellId, and convert it into a binary number.
 If bit2 = 1, it indicates PreallocationSwitch is enabled.
 If bit6 = 1, it indicates SmartPreAllocationSwitch is enabled.
3) Check the value of PreallocationSwitch, SmartPreAllocationSwitch, PreallocationMinPeriod, PreallocationSize and
SmartPreallocationDurationparameter under CELLPREALLOCGROUP, corresponding with 1)’s PreallocationParaGroupId.
 PreallocationSwitch = 1, which indicates that preallocation switch is enabled for a bearer with a specified preallocation parameter group ID.
 SmartPreAllocationSwitch = 1, which indicates that smart preallocation switch is enabled for a bearer with a specified preallocation
parameter group ID.
 PreallocationMinPeriod = 20, which indicates that minimal period of preallocation is 20ms.
 PreallocationSize = 120, which indicates data size of preallocation is 120 bytes.
 SmartPreallocationDuration=160, which indicates smart preallocation duration is 160ms.
4) Mark it as abnormal and output this cell’s related information if checked parameters don’t meet the conditions in 2) or 3).
3.118.4Measures
Set related parameters to recommended value: MOD CELLALGOSWITCH: LocalCellId=x, UlSchSwitch = PreAllocationSwitch-1 &
SmartPreAllocationSwitch-1; MOD CELLPREALLOCGROUP: LocalCellId=x, PreallocationParaGroupId=n, PreallocationSwitch=ON,
SmartPreallocationSwitch=ON, PreallocationMinPeriod=20, PreallocationSize=120, SmartPreallocationDuration=160.
3.118.5Reference
None.
Note: This rule is just for eRAN6.0 and eRAN7.0 (versions before eRAN7.0SPC180).

3.119 Enhanced Preallocation for VOIP
3.119.1Location

10 VOLTE Inspection 02 VOLTE Uplink Optimization Strategy 04 Enhanced Preallocation for VOIP
Preallocation (smart preallocation is included) will limit the online user number (if RRC Connected User is more than 50, preallocation will not
take effect). However, the function of preallocation is unreplaceable for VOIP users. Therefore, voice preallocation is implemented. This parameter is
designed to allow QCI1 users to use preallocation when RRC Connected User is more than 50 to reduce uplink data packet loss.
1) Output cells’ related information with disabled Enhanced Preallocation Switch for VOIP.
Abnormal Data
eNodeB eNodeB Local Cell Enhanced Preallocation
eNodeB Version
ID Name Cell ID Name Switch for VOIP
BTS3900
5047 5G-S-03 0 Cell0 OFF
V100R009C00SPC170
3.119.3Principles
1) Enhanced Preallocation Switch for VOIP is disabled: Check the value of RsvdSwPara0 under ENBCELLRSVDPARA from LMT.XML file,
convert it into a binary number and its bit30 = 0.
2) Output abnormal cells’ related information.
3.119.4Measures
Set related parameters to recommended value: MOD ENBCELLRSVDPARA: LocalCellId=x, RsvdSwPara0=RsvdSwPara0_bit30-1.
3.119.5Reference
None.
Note: This rule is just for eRAN7.0 (versions between eRAN7.0SPC128 and eRAN7.0SPC180).

3.120 Debug Log Analysis
3.120.1 Location

09 Log Inspection 01 Debug Log Analysis 01 Debug Log Analysis
Please analyze all error codes from debug log based on one click log on main control board. This rule is mainly used to collect error codes’
information every day if its occurrence times is more than the threshold.
1) Output error codes’ information in detail if its occurrence times every day is more than the threshold.
Abnormal Data of Error Code

Log Error Code Value of Error Max Times Occurred Every
eNodeB Name Date Actual Times
Type Name Code Day in a Single eNodeB
10.141.77.218_ L2_ERR_M
- DEBUG 5259937 1 1
30014 AC_02A1
10.141.77.218_ L2_ERR_M
- DEBUG 5260484 1000 2139
30014 AC_04E0
3.120.3 Principles
1) The log collected by OMStar will be added into the database after summarizing and processing.
2) From the interface provided by OMStar, get corresponding error code’s occurrence time based on its ID and compare it with the threshold. If it is
more than the threshold, mark it as abnormal and output it into “Abnormal Data of Error Code” table.
3.120.4 Measures
Collect one click log on main control board and deliver it to HUAWEI engineers.
3.120.5 Reference
None.
Note: This rule is just for eRAN8.0 and its later versions.

3.121 FPGA Hard Failure Check
3.121.1 Location

09 Log Inspection 02 Platform Log Analysis 01 FPGA Hard Failure Check
Fault RRU hardware will lead to RRU link disconnection, hardware fault, and abnormal service and so on after updating. This rule is mainly used
to collect the location and fault information on eNodeBs with FPGA hard failure.
1) Output the information of Location, Fault Name, Fault ID, Occurrence Time, and Current State and so on with FPGA hard failure.
FPGA Hard Failure Table

Fault Fault Fault Occurr
Occurrence
eNo Occurs Occurs Occurs ence
S Ala Ti Curre /Recovery Date Of
eNod deB C S Fault Again Again Again In 3 Time of BO Electro
R rm m nt Time of the Manufa
eB ID Nam N N Name After After Mins After the M nic Lab
N ID es State Last Fault cture
e Warm Power-off Power-off First
Occur
Reset Reset Reset Fault
309
2014- 2102310
8- FPGA 2014-08-07 023
Fault 08-06 VNE10 2014-
414 414 0 60 0 >09- Hard 5 No Yes Yes 04:32:29(48 10V
Occur 04:24:3 E20000 02-16
>4- Failure 0) NE
0(480) 86
>10
2014-
98- FPGA 023 2102315
Fault 06-24 2014-06-24 2009-
414 414 1 60 0 >9- Hard 2 No Yes Yes 155 528D09
Occur 06:58:2 11:16:23 03-21
>5 Failure 28 3058784
4
3.121.3 Principles
For center fault log and RRU fault log, the methods of judging FPGA hard failure fault are different. The details are listed below.
1) Center fault log:
a) Get the fault information if its fltid=3098 and byte4 of lctinfo is 09 from CFLT file, and then get other analyzing information from
spcproblem, byte5 of lctinfo (Faults with same name and analyzing information are considered as one fault) and fault occurred location
(CN, SRN and SN) from reptbrd.

b) Get the latest state under occurtime. If flttype=UnCleared, go to next step, or end.
c) If this fault occurs before power-off reset and occurs again in 3 minutes after power-off reset, go to step d), or end. The details are as
follows:
 Get the fault information of fltid=2558/3026. If its byte3 of dctinfo is 00, it indicates power-off reset and go to next step, or end.
 Get all the occurrence time of fltid=3098. Confirm the fault occurs before the power-off rest and occurs again in 3 minutes after power-
off reset, or end.
d) Check the Serial Number and Date of Manufacture under the fault occurred location(CN,SRN and SN) from MML’s dsp_brdmfrinfo.txt file
to get Electronic Lab, Date Of Manufacture and BOM (bit 3 to bit10 of Electronic Lab is BOM code), and then output related information
of this center fault.
2) RRU fault log:
a) Get the fault information if its almcode=98/100 and subparam0 = 9 from RRU file, and then get other analyzing information from
sunparam1 (Faults with same name and analyzing information are considered as one fault) and the fault occurred location (CN, SRN and
SN) from filename.
b) Get the latest state under occurtime. If almstate = 1, go to next step, or end.
c) If this fault occurs before power-off reset and occurs again in 3 minutes after power-off reset, go to step d), or end. The details are as
follows:
 Get the fault information of almcode=26. If byte1 of its corresponding parameter is 00, it indicates power-off reset and go to next step, or
end.
 Get all the occurrence time of almcode=98/100. Confirm the fault occurs before the power-off rest and occurs again in 3 minutes after
power-off reset, or end.
d) Check the Serial Number and Date of Manufacture under the fault occurred location (CN,SRN and SN) from MML’s dsp_brdmfrinfo.txt file
to get Electronic Lab, Date Of Manufacture and BOM (bit 3 to bit10 of Electronic Lab is BOM code), and then output related information
of this RRU fault.
Note: The format of center fault alarm ID is 3098->9->*->* and RRU fault alarm ID is 98->9->* or 100->9->*.
3.121.4 Measures
Replace RRU.

3.121.5 Reference
None.
3.122 RRU Input Power Is Too High
3.122.1 Location

09 Log Inspection 02 Platform Log Analysis 02 RRU Input Power Is Too High
If RRU’s input power is continuously too high, RRU may be damaged and power services of a cell may be affected and so on. This rule is mainly
used to collect the location and fault information on eNodeBs with high RRU input power.
1) Output the information of the Location, Fault Name, Fault ID, Occurrence Time, and Current State and so on with high RRU input power.
RRU Input Power Is Too High

Occurr
Fault Fault Fault Occur
ence/Re Date
Occurs Occurs Occurs rence
eNode S Curre covery Electr Of
eNod C S Alar Fault Again Again Again In 3 Time
B R Times nt Time of BOM onic Manu
eB ID N N m ID Name After After Mins After of the
Name N State the Last Lab factur
Warm Power-off Power-off First
Fault e
Reset Reset Reset Fault
Time
RRU 2014- 21023
3183- 2014-
Input 07-24 10VN
VoLT >09- Fault 08-07 02310 2014-
414 0 60 0 Power 3 No Yes No 04:24: E10E2
E414 >4- Occur 04:33:2 VNE 02-16
Is Too 30(48 00008
>10 8(480)
High 0) 6
RRU
2005- 2005- 21023
Input
VoLT 183- Fault No 07-02 07-15 02315 15528 2009-
414 1 60 0 Power 1 No No
E414 >1->6 Occur 00:00: 00:00:0 528 D0930 03-21
Is Too
00 0 58784
High

3.122.3 Principles
For center fault log and RRU fault log, the methods of judging RRU’s high input power fault are different. The details are listed below.
a) Get the fault information if its fltid=3183 from CFLT file, and then get other analyzing information from byte4 and byte5 of lctinfo,
spcproblem (Faults with same name and analyzing information are considered as one fault) and fault occurred location (CN, SRN and SN)
from reptbrd. If one of the conditions below is met, go to step b).
 Check the latest state under occurtime and flttype=UnCleared.
 Check its latest state in the last 14 days and times of flttype=UnCleared is more than 3.
b) Check the Serial Number and Date of Manufacture under the fault occurred location(CN,SRN and SN) from MML’s dsp_brdmfrinfo.txt file
to get Electronic Lab, Date Of Manufacture and BOM(bit 3 to bit10 of Electronic Lab is BOM code), and then output related information of
this center fault.
2) RRU fault log:
a) Get the fault information if its almcode=183 from RRU file, and then get other analyzing information from sunparam0, sunparam1 (Faults
with same name and analyzing information are considered as one fault), and fault occurred location (CN, SRN and SN) from filename. If
one of the conditions below is met, go to step b).
 Check the latest state under almtime and almstate=1.
 Check its latest state in the last 14 days and times of almstate=1 is more than 3.
this RRU fault.
Note: The format of center fault alarm ID is 3183->*->*->* and RRU fault alarm ID is 183->*->*.
3.122.4 Measures
Send one click log of eNodeB and RRU to researchers for analysis.
3.122.5 Reference
None.

3.123 Check of RF Unit Tx Channel Gain
3.123.1 Location

09 Log Inspection 02 Platform Log Analysis 03 Check of RF Unit Tx Channel Gain
When the gain of transmit channel is too large, it will lead to a large downlink coverage, which may cause overshoot interference to other cells.
When the gain of transmit channel is too small, it will lead to a small downlink coverage, which may cause coverage void, or service interruption loaded on
RF unit in serious cases. This rule is mainly used to collect the location and fault information on eNodeBs with abnormal gain of RF unit Tx channel.
1） Output the information of Location, Fault Name, Fault ID, Occurrence Time, and Current State and so on with abnormal gain of RF unit Tx
channel.
Check of RF Unit Tx Channel Gain

Fault Fault
Fault Occur Occurr
Occurs Occurs
Occurs rence ence/Re
eNode S Ti Curre Again Again In Date Of
eNod C S Alar Fault Again Time covery Electro
B R m nt After 3 Mins BOM Manufa
eB ID N N m ID Name After of the Time of nic Lab
Name N es State Power- After cture
Warm First the Last
off Power-off
Reset Fault Fault
Reset Reset
Abnor
mal
2014-
3180- Gain 2014- 2102310
07-24 0231
VoLT >01- of RF Fault 08-07 VNE10 2014-
414 0 60 0 3 No Yes No 04:24: 0VN
E414 >1- Unit Occur 04:33:2 E20000 02-16
30(48 E
>aa Tx 8(480) 86
0)
Chann
el
414 VoLT 1 60 0 180- Abnor 1 Fault No No No 2005- 2005- 0231 2102315 2009-
E414 >1->1 mal Occur 07-02 07-15 5528 528D09 03-21
Gain 00:00: 00:00:0 3058784
of RF 00 0
Unit

Tx
Chann
el
3.123.3 Principles
For center fault log and RRU fault log, the methods of judging abnormal RF unit Tx channel gain are different. The details are listed below.
spcproblem (Faults with same name and analyzing information are considered as one fault), and fault occurred location (CN, SRN and SN)
b) Check the Serial Number and Date of Manufacture under the fault occurred location( CN,SRN and SN) from MML’s dsp_brdmfrinfo.txt file
this center fault.
2) RRU fault log:
this RRU fault.
3.123.4 Measures
When this fault occurs, try to repair RF unit remotely. Please send one click log of eNodeB and RRU to researchers for analysis.

3.123.5 Reference
None.
3.124 Check of RF Unit PA Current
3.124.1 Location

09 Log Inspection 02 Platform Log Analysis 04 Check of RF Unit PA Current
Continuous overcurrent of power amplifier will result in that some parts in RF unit work abnormally, or service loaded on RF unit is interrupted
in serious cases. This rule is mainly used to collect the location and fault information on eNodeBs with overcurrent of RF unit power amplifier.
1） Output the information of Location, Fault Name, Fault ID, Occurrence Time, and Current State and so on with overcurrent of RF unit power
amplifier.
Check of RF Unit PA Current

Fault Fault Fault Occur Occurr
Occurs Occurs Occurs rence ence/Re
eNode S Ti Curre Date Of
eNod C S Alar Fault Again Again Again In 3 Time covery BO Electro
B R me nt Manufact
eB ID N N m ID Name After After Mins After of the Time of M nic Lab
Name N s State ure
Warm Power- Power-off First the Last
Reset off Reset Reset Fault Fault
Overc
urrent 2014-
3181- 2014- 2102310
of RF 07-24 023
VoLT >01- Fault 08-07 VNE10 2014-02-
414 0 60 0 Unit 3 No Yes No 04:24: 10V
E414 >1- Occur 04:33:2 E20000 16
Power 30(48 NE
>aa 8(480) 86
Ampli 0)
fier
414 VoLT 1 60 0 183- Overc 1 Fault No No 2005- 2005- 023 2102315 2009-03-
E414 >1->1 urrent Occur 07-02 07-15 155 528D09 21
No
of RF 00:00: 00:00:0 28 3058784
Unit 00 0
Power

Ampli
fier
3.124.3 Principles
For center fault log and RRU fault log, the methods of judging overcurrent of RF unit power amplifier are different. The details are listed below.
1） Center fault log:
this center fault.
2） RRU fault log:
this RRU fault.
3.124.4 Measures

3.124.5 Reference
None.
3.125 RF Unit Clock Check
3.125.1 Location

09 Log Inspection 02 Platform Log Analysis 05 Clock of RF Unit Check
If clock related fault on RF unit occurs, some parts in RF unit will work abnormally, or service loaded on RF unit will be interrupted in serious
cases. This rule is mainly used to collect the location and fault information on eNodeBs with RF unit clock fault.
1） Output the information of Location, Fault Name, Fault ID, Occurrence Time, and Current State and so on with RF unit clock fault.
RF Unit Clock Check 　

Fault Fault Fault Occurr Occurren
Cur Occurs Occurs Occurs ence ce/Recove
eNode S Ti Electr Date Of
eNod C S Alar Fault rent Again Again Again In 3 Time of ry Time
B R me BOM onic Manufa
eB ID N N m ID Name Stat After After Mins After the of the
Name N s Lab cture
e Warm Power- Power-off First Last
Reset off Reset Reset Fault Fault
21023
3148- Check Faul 2014- 2014-08-
10VN
VoLT >01- of RF t 07-24 07 02310 2014-
414 0 60 0 3 No Yes No E10E2
E414 >1- Unit Occ 04:24:3 04:33:28( VNE 02-16
00008
>aa Clock ur 0(480) 480)
6
Check Faul 2005- 21023
2005-07-
VoLT 148- of RF t 07-02 02315 15528 2009-
414 1 60 0 1 No No No 15
E414 >1->1 Unit Occ 00:00:0 528 D0930 03-21
00:00:00
Clock ur 0 58784

3.125.3 Principles
For center fault log and RRU fault log, the methods of judging RF unit clock fault are different. The details are listed below.
a) Get the fault information if its fltid=3148/3149/3152 from CFLT file, and then get other analyzing information from byte4 and byte5 of
lctinfo, spcproblem (Faults with same name and analyzing information are considered as one fault), and fault occurred location (CN, SRN
and SN) from reptbrd. For fltid=3148, go to step b) if flttype=UnCleared. For fltid=3149/3152, go to step b) if one of the conditions below
is met.
this center fault.
2） RRU fault log:
a) Get the fault information if its almcode=148/149/152 from RRU file, and then get other analyzing information from sunparam0, sunparam1
(Faults with same name and analyzing information are considered as one fault), and fault occurred location (CN, SRN and SN) from
filename. If one of the conditions below is met, go to step b).
 Check its state in the last 30 days and times of almstate=1 is more than 3.
this RRU fault.
Note: The format of center fault alarm ID is 3148->*->*->* and RRUF fault alarm ID is 148->*->*.
3.125.4 Measures
If there is "ALM-26538 RF unit clock problem" reported, solve it based on the corresponding measurement. If ALM-26538 is not reported, send
one click log of eNodeB and RRU to researchers for analysis.

3.125.5 Reference
None.
3.126 RF Unit Hardware Check
3.126.1 Location

09 Log Inspection 02 Platform Log Analysis 06 RF Unit Hardware Check
If RF unit hardware fault occurs, RF unit or some functions on RF unit may not work normally, service loaded on it will be interrupted or service
quality on it will become worse. This rule is mainly used to collect the location and fault information on eNodeBs with RF unit hardware fault.
1) Output the information of Location, Fault Name, Fault ID, Occurrence Time, and Current State and so on with RF unit hardware fault.
RF Unit Hardware Check

Fault
Fault Fault Occur Occurr
Occurs
Occurs Occurs rence ence/Re
eNode S Ti Curre Again In Date Of
eNod C S Alar Fault Again Again Time covery Electro
B R m nt 3 Mins BOM Manufactu
eB ID N N m ID Name After After of the Time of nic Lab
Name N es State After re
Warm Power- First the Last
Power-off
Reset off Reset Fault Fault
Reset
RF 2014-
3015- 2014- 2102310
Unit 07-24
VoLT >01- Fault 08-07 02310 VNE10
414 0 60 0 Hardw 3 No Yes No 04:24: 2014-02-16
E414 >1- Occur 04:33:2 VNE E20000
are 30(48
>aa 8(480) 86
Fault 0)
414 VoLT 1 60 0 15->1- RF 1 Fault No No No 2005- 2005- 02315 2102315 2009-03-21
E414 >1 Unit Occur 07-02 07-15 528 528D09
Hardw 00:00: 00:00:0 3058784

are
00 0
Fault
3.126.3 Principles
For center fault log and RRU fault log, the methods of judging RF unit hardware fault are different. The details are listed below (Take one of the
faults as an example).
this center fault.
2） RRU fault log:
with same name and analyzing information are considered as one fault), and fault occurred location (CN, SRN and SN) from filename
finally. If one of the conditions below is met, go to step b).
this RRU fault.
3.126.4 Measures
If there is "ALM-26532 RF unit hardware fault" reported, solve it based on the corresponding alarm measurement. If ALM-26532 is not reported,
send one click log of eNodeB and RRU to researchers for analysis.

3.126.5 Reference
None.
3.127 Power Voltage of RF Unit Check
3.127.1 Location

09 Log Inspection 02 Platform Log Analysis 07 Power Voltage of RF Unit Check
If there is continuous carrier voltage fault, some parts in RF unit may work abnormally, or service loaded on RF unit will be interrupted in
serious cases. This rule is mainly used to collect the location and fault information on eNodeBs with carrier voltage fault.
1） Output the information of Location, Fault Name, Fault ID, Occurrence Time, and Current State and so on with carrier voltage fault.
Check of RF Unit Power Voltage

Fault Fault Fault Time of
Time
Cur Occurs Occurs Occurs the Last
eNode S Ti of the B Electr Date Of
eNod C S Alar Fault rent Again Again Again In 3 Fault
B R m First O onic Manufa
eB ID N N m ID Name Stat After After Mins After Occur or
Name N es Fault M Lab cture
e Warm Power- Power-off Recovery
Occur
Reset off Reset Reset Time
RF 02
2014- 21023
Unit Faul 2014-08- 31
3134- 07-24 10VN
VoLT Power t 07 0 2014-
414 0 60 0 >1- 3 No Yes No 04:24: E10E2
E414 Voltag Occ 04:33:28( V 02-16
>aa 30(48 00008
e ur 480) N
0) 6
Fault E
414 VoLT 1 60 0 134- RF 1 Faul No No No 2005- 2005-07- 02 21023 2009-
E414 >1->1 Unit t 07-02 15 31 15528 03-21
Power Occ 00:00: 00:00:00 55 D0930
Voltag ur 00 28 58784

e
Fault
3.127.3 Principles
For center fault log and RRU fault log, the methods of judging RF unit power voltage fault are different. The details are listed below.
b) Check the Serial Number and Date of Manufacture under the fault occurred location (CN,SRN and SN) from MML’s dsp_brdmfrinfo.txt file
this center fault.
2） RRU fault log:
b) Check the Serial Number and Date of Manufacture under the fault occurred location (CN,SRN and SN) from MML’s dsp_brdmfrinfo.txt file
this RRU fault.
3.127.4 Measures

3.127.5 Reference
None.
Note: This rule is just for versions eRAN7.0 and its later versions.
3.128 CANBUS Communication Failure Check
3.128.1 Location

09 Log Inspection 02 Platform Log Analysis 05 CANBUS Communication Failure Check
If “Inter-Board CANBUS Communication Failure” occurs,
1. Updating the cpld version will fail when updating NE.
2. Obtainning the BBU ESN will fail, so the LICENSE will work abnormally.
3. Monitoring the site’s environment may be affected.
This rule is mainly used to collect eNodeBs’ related information with this alarm.
1) Output eNodeBs’ eNodeB ID, eNodeB Name, CN, SRN and SN information with this alarm.
eNodeBs with Inter-Board CANBUS Communication Failure

eNodeB ID eNodeB Name CN SRN SN
900806 XN-103.103.1.156 0 12 2
900807 XN-103.103.1.157 0 12 2
3.128.3 Principles
1) Get the information of fltid=2003(Link Disconnected Between SMS and CANBUS Node Fault) from CFLT file, and then get this fault’s other
analyzing information (Faults with same name and analyzing information are considered as one fault) from byte4 and byte5 of lctinfo,
spcproblem, fault occurred location (CN, SRN and SN) from reptbrd and the occurrence time of this fault from occurtime.
2) Get the information of alarmid=26101(Inter-Board CANBUS Communication Failure) from Alarm file.
3) If ALM-26101 Inter-Board CANBUS Communication Failure occurred within one minute after FLT-2003 Link Disconnected between SMS and
CANBUS Node Fault, it is considered as CANBUS communication failure and output this eNodeB’s information.

3.128.4 Measures
Please refer to the guidance to confirm the faulty reason.
http://3ms.huawei.com/hi/group/6639/wiki_3547005.html
3.128.5 Reference
None.
3.129 SON Temporary File Check
3.129.1 Location

09 Log Inspection 03 BSP Log Analysis 01 SON Temporary File Check
If junk file of NE isn’t cleared, the flash files of log, traffic and so on can't be generated.
1) Output eNodeBs’ information if the number of SON temporary files is more than 5.
Abnormal Data
eNodeB ID eNodeB Name Number of SON Temporary Files
900806 XN-103.103.1.156 6
3.129.3 Principles
1) Check the number of records started as “Tffs1:/log/exp/son” under aucfilename field from bsp file.
2) If the number of SON temporary files is more than 5, mark it as abnormal and output corresponding eNodeBs’ information.
3.129.4 Measures
If junk file of NE isn’t cleared, the flash files of log, traffic and so on can't be generated. Therefore, it is suggested to reset the NE.

3.129.5 Reference
None.
3.130 DRX Inspection Rule
3.130.1 Location

14 DRX Inspection 01 DRX Inspection 01 DRX Inspection Rule
If DRX is enabled, it will affect the data transmission delay, measurement accuracy, resulting in packet loss because of its inherent
characteristics. Therefore, enabling it is not recommended. However, if asked to do so, it is suggested to configure it with the recommended value. If not,
parts of the KPI may become worse and the terminal cannot reach the power saving effect.
1) Output cells’ related information if their configurations are inconsistent or consistent with the recommended value (QCI1).
Recommended Configurations for VOIP Service (QCI1)

Recommended Recommended
DRXPara eNode eNodeB Local MML
QCI Output Result Configuration Configuration (By
GroupId B ID Name Cell ID Command
(Power Saving First) Apple)
11 // 12
OnDurationTimer = 7, OnDurationTimer = 3,
// 13 // Different from
MOD DrxInactivityTimer = DrxInactivityTimer =
0000_B 21 // 22 both of the
1 4 90964 DRXPARA 13, DrxReTxTimer = 3, DrxReTxTimer = 4,
W // 23 // recommended
GROUP 4, SupportShortDrx = SupportShortDrx = 0,
31 // 32 configurations.
0, LongDrxCycle = 3 LongDrxCycle = 3
// 33
OnDurationTimer = 7, OnDurationTimer = 3,
11 // 12 Different from
MOD DrxInactivityTimer = DrxInactivityTimer =
10301 // 13 // both of the
1 4 CWPAP DRXPARA 13, DrxReTxTimer = 3, DrxReTxTimer = 4,
3 21 // 22 recommended
GROUP 4, SupportShortDrx = SupportShortDrx = 0,
// 23 configurations.
0, LongDrxCycle = 3 LongDrxCycle = 3
2) Output cells’ related information if their configurations are inconsistent or consistent with the recommended value (QCI5/6/8/9).
Recommended Configurations for Data Service (QCI5/6/8/9)
QCI DRXPara eNodeB eNodeB Local Cell ID Output Result MML Recommended Recommended

Configuration( Perform Configuration(Power

GroupId ID Name Command
ance First) Saving First)
Different from
11 // 12 // 13 //
0000_BWTW both of the MOD
5 6 90964 21 // 22 // 23 // SrsCfgInd >= 3 SrsCfgInd >= 6
N203201 recommended TATIMER
31 // 32 // 33
configurations.
Different from LongDrxCycle = 3, LongDrxCycle = 9,
11 // 12 // 13 // MOD
0000_BWTW both of the OnDurationTimer = 1, OnDurationTimer = 7,
5 6 90964 21 // 22 // 23 // DRXPARA
N203201 recommended DrxInactivityTimer = 13, DrxInactivityTimer =
31 // 32 // 33 GROUP
configurations. DrxReTxTimer = 4 14, DrxReTxTimer = 4
3.130.3 Principles
“Recommended Configuration for VOIP Service (QCI1)” table:
1) Check the value of QCI under CELLSTANDARDQCI. If QCI = 1, record its corresponding LocalCellId.
2) Check whether the parameters are consistent with the “Recommended Configuration (Power Saving First)” or “Recommended Configuration (By
Apple)”.
 Check whether the parameters corresponding with same LocalCellId with 1) are consistent with “Recommended Configuration (Power
Saving First)”.
 Bears of corresponding parameter group ID support DRX: Check the value of EnterDRXSwitch under DrxParaGroup and
EnterDRXSwitch = 1.
Note: If EnterDRXSwitch = 0, it indicates that the bearers do not support DRX and end.
 Length of Long DRX Cycle:
Note: If a) or b) is met, it indicates that the length of Long DRX Cycle is consistent with the recommended value. If not, it indicates that the length of Long
DRX Cycle is inconsistent with the recommended value.
a) When downlink and uplink SpsSchSwitch are disabled, length of Long DRX Cycle is 40 subframes: Check the value of DlSchSwitch
and UlSchSwitch under CELLALGOSWITCH and convert them into binary numbers. If bit2 of DlSchSwitch and bit0 of
UlSchSwitch = 0, check the value of LongDrxCycle under DrxParaGroup and LongDrxCycle = 3.
b) When downlink or uplink SpsSchSwitch is enabled, length of Long DRX Cycle is 20 subframes: Check the value of DlSchSwitch
and UlSchSwitch under CELLALGOSWITCH and convert them into binary numbers. If bit2 of DlSchSwitch or bit0 of UlSchSwitch
= 1, check the value of LongDrxCycle under DrxParaGroup and LongDrxCycle = 1.
 On Duration Timer is 10 PDCCH subframes: Check the value of OnDurationTimer under DRXPARAGROUP and OnDurationTimer =
7.

 DRX Inactivity Timer is 80 PDCCH subframes: Check the value of DrxInactivityTimer under DRXPARAGROUP and
DrxInactivityTimer = 13.
 DRX Retransmission Timer is 8 PDCCH subframes: Check the value of DRXReTxTimer under DRXPARAGROUP and
DRXReTxTimer = 4.
 Can’t support short-cycle DRX: Check the value of SupportShortDrx under DrxParaGroup and SupportShortDrx = 0.
 Check whether the parameters corresponding with same LocalCellId with 1) are consistent with “Recommended Configuration (By
Apple)”.
EnterDRXSwitch = 1.
 Long DRX Cycle is 40 subframes: Check the value of LongDrxCycle under DrxParaGroup and LongDrxCycle = 3.
 On Duration Timer is 4 PDCCH subframes: Check the value of OnDurationTimer under DRXPARAGROUP and OnDurationTimer = 3.
DRXReTxTimer = 4.
 Can’t support short-cycle DRX: Check the value of SupportShortDrx under DrxParaGroup and SupportShortDrx = 0.
Note: If the parameters are consistent with “Recommended Configuration (Power Saving First)”, output “consistent with Recommended Configuration (Power Saving
First)” in the “Output Result” column and output “-” in last three columns. If the parameters are consistent with “Recommended Configuration (By Apple)”, output
“consistent with Recommended Configuration (By Apple)” in the “Output Result” column and output “-” in last three columns. If the parameters are inconsistent with
neither of the recommended configurations, output “Different from both of the recommended configurations” in the “Output Result” column, corresponding MML
command and Recommended Configuration in the last three columns.
“Recommended Configurations for Data Service (QCI5/6/8/9)” table:
1) Check the value of QCI under CELLSTANDARDQCI. If QCI =5/6/8/9, record its corresponding LocalCellId and DRXParaGroupId.
2) Check whether the parameters are consistent with the “Recommended Configuration (Performance First)” or “Recommended Configuration
(Power Saving First)”.
 Check whether the parameters corresponding with same LocalCellId with 1) are consistent with “Recommended Configuration
(Performance First)”.

EnterDRXSwitch = 1.
 Length of Long DRX Cycle is 40 subframes: Check the value of LongDrxCycle under DrxParaGroup and LongDrxCycle = 3.
 On Duration Timer is 2 PDCCH subframes: Check the value of OnDurationTimer under DRXPARAGROUP and OnDurationTimer = 1.
DRXReTxTimer = 4.
 FDD Enter DRX Threshold is 1000: Check the value of FddEnterDrxThd under CELLDRXPARA and FddEnterDrxThd = 1000.
 FDD Exit DRX Threshold is 1000: Check the value of FddExitDrxThd under CELLDRXPARA and FddExitDrxThd = 1000.
 Uplink Time Alignment Timer:
Note: If a) or b) is met, it indicates that the length of uplink time alignment timer is consistent with the recommended value. If not, it indicates that the length
of uplink time alignment timer is inconsistent with the recommended value.
a) When SRS Configuration Indicator is BOOLEAN_TRUE and uplink time alignment timer needs to set to 1920 subframes: Check the
value of SrsCfgInd under SRSCfg and SrsCfgInd = 1. Check the value of TimeAlignmentTimer under TimeAlignmentTimer and
TimeAlignmentTimer = 3.
b) When SRS Configuration Indicator is BOOLEAN_FALSE and uplink time alignment timer needs to set to infinity: Check the value
of SrsCfgInd under SRSCfg and SrsCfgInd = 0. Check the value of TimeAlignmentTimer under TimeAlignmentTimer and
 Check whether the parameters corresponding with same LocalCellId with 1) are consistent with “Recommended Configuration (Power
Saving First)”.
EnterDRXSwitch = 1.
 Length of Long DRX Cycle is 320 subframes: Check the value of LongDrxCycle under DrxParaGroup and LongDrxCycle = 9.
 On Duration Timer is 10 PDCCH subframes: Check the value of OnDurationTimer under DRXPARAGROUP and OnDurationTimer =
7.

DRXReTxTimer = 4.
 FDD Enter DRX Threshold is 1000: Check the value of FddEnterDrxThd under CELLDRXPARA and FddEnterDrxThd = 1000.
 FDD Exit DRX Threshold is 1000: Check the value of FddExitDrxThd under CELLDRXPARA and FddExitDrxThd = 1000.
 Uplink time alignment timer:
Note: If a) or b) is met, it indicates that the length of uplink time alignment timer is consistent with the recommended value. If not, it indicates that the length
of uplink time alignment timer is inconsistent with the recommended value.
a) When SRS Configuration Indicator is BOOLEAN_TRUE and uplink time alignment timer needs to set to 10240 subframes: Check
the value of SrsCfgInd under SRSCfg and SrsCfgInd = 1. Check the value of TimeAlignmentTimer under TimeAlignmentTimer and
b) When SRS Configuration Indicator is BOOLEAN_FALSE and uplink time alignment timer needs to set to infinity: Check the value
of SrsCfgInd under SRSCfg and SrsCfgInd = 0. Check the value of TimeAlignmentTimer under TimeAlignmentTimer and
Note: If the parameters are consistent with “Recommended Configuration (Performance First)”, output “consistent with Recommended Configuration (Performance
First)” in the “Output Result” column and output “-” in last three columns. If the parameters are consistent with “Recommended Configuration (Power Saving First)”,
output “consistent with Recommended Configuration (Power Saving First)” in the “Output Result” column and output “-” in last three columns. If the parameters are
inconsistent with neither of the recommended configurations, output “Different from both of the recommended configurations” in the “Output Result” column,
corresponding MML command and Recommended Configuration in the last three columns.
3.130.4 Measures
1) VOIP service (QCI1): If the verification results are inconsistent with both of the recommended configurations, modify them based on the
Recommended Configuration (By Apple) if the customer requires. Otherwise, modify them based on Recommended Configuration (Power
Saving First).
2) Data services (QCI5/6/8/9): If the verification results are inconsistent with both of the recommended configurations, modify them based on the
Recommended Configuration (Performance First) if the customer requires. Otherwise, modify them based on Recommended Configuration
(Power Saving First).
3) The entire network’s configuration must be consistent with one set of the recommended configurations.

3.130.5 Reference
None.
3.131 Summary of Risky Parameter Verification
3.131.1 Location

13 Parameter Verification Inspection 01 Risky Parameter Verification 01 Summary of Risky Parameter Verification
If parameter’s configuration is inconsistent with the recommended value, it may lead to online problems.
1) Output the current network configuration which is inconsistent with the recommended value.
Abnormal Data
Number of Abnormal
Parameter Recommended Current Network
Parameter Subject MML Object Parameter ID Parameters(must Remark
Name Value Configuration
modify)
Must disable it.
Hysteresis for
PS data CELLPDCC HysForCfiBased Enabling this parameter
CFI increase 0 1(1) 1
transmission HALGO PreSch will lead to negative
based on PreSch
gain.
3.131.3 Principles
Risky parameter verification has 8 inspection rules and 10 MML objects. Output current network configuration which is inconsistent with the
recommended value based on parameter ID to this rule (Please refer to the below 8 inspection rules to get the details).
3.131.4 Measures
For parameters which their configurations are inconsistent with the recommended value, it is suggested to compare them with parameters’
baseline and modify them according to different eNodeBs. (Modifying parameters is risky. Please operate it carefully.)

3.131.5 Reference
None.
Note: This rule is just for eRAN8.1 versions.
3.132 PDCCH Algorithm Parameter
3.132.1 Location

13 Parameter Verification Inspection 01 Risky Parameter Verification 02 PDCCH Algorithm Parameter
If parameter’s configuration is inconsistent with the recommended value, it may lead to online problems. Enabling hysteresis for CFI increase
based on PreSch will lead to negative gain.
Abnormal Data
eNodeB eNodeB Local Current Network Recommended
Cell Name MML Object Parameter ID Parameter Name
ID Name Cell ID Configuration value
HysForCfiBas Hysteresis for CFI increase
414 VoLTE414 0 cell0 CELLPDCCHALGO 1 0
edPreSch based on PreSch
3.132.3 Principles
Check the parameter’s configuration below from LMT.XML file and output the current network configuration which is inconsistent with the
recommended value.
 Hysteresis for CFI increase based on PreSch: Check the value of HoCommOptSwitch under ENodeBAlgoSwitch field and convert it into a binary
data. If bit0 = 1, end. Or output this cell’s information.
3.132.4 Measures
baseline and modify them according to different eNodeBs (Modifying parameters is risky. Please operate it carefully.)

Hysteresis for CFI increase based on PreSch: MOD CELLPDCCHALGO: LocalCellId=X, HysForCfiBasedPreSch=0.
3.132.5 Reference
None.
3.133 eNodeB Algorithm Switch
3.133.1 Location

13 Parameter Verification Inspection 01 Risky Parameter Verification 03 eNodeB Algorithm Switch
1. BasedSriGapOptSwitch: If this switch is enabled and not in the discontinuous reception (DRX) state, it will consider transmission of scheduling
request indicators (SRIs) when configuring measurement gaps for a UE, which will decrease the risk of call dropping. If this switch is
disabled, the transmission of SRIs is not considered and abnormal UEs do not send SRIs occasionally on the live network, the problem of
decreased eRAB setup success rate increases significantly since SRI period reconfiguration is reduced.
2. DrxBasedSriGapOptSwitch: If this switch is enabled in DRX state, it will consider transmission of scheduling request indicators (SRIs) when
configuring measurement gaps for a UE. If this switch is disabled, the transmission of SRIs is not considered and not all SRIs fall into
measurement gaps, which will lead to call dropping. It is suggested to turn it on to avoid this problem.
1） Output the current network configuration which is inconsistent with the recommended value.
Abnormal Data
eNodeB Current Network Recommended
eNodeB ID MML Object Parameter ID Parameter Name
Name Configuration value
ENODEBALGO BasedSriGapOptSwitch@
414 VoLTE414 BasedSriGapOptSwitch 0 1
SWITCH HoCommOptSwitch
ENODEBALGO DrxBasedSriGapOptSwitc
414 VoLTE414 DrxBasedSriGapOptSwitch 0 1
SWITCH h@HoCommOptSwitch

3.133.3 Principles
recommended value.
 BasedSriGapOptSwitch: Check the value of HoCommOptSwitch under ENodeBAlgoSwitch field and convert it into a binary data. If bit0 =1,
end. Or output this eNodeB’s information.
 DrxBasedSriGapOptSwitch: Check the value of HoCommOptSwitch under ENodeBAlgoSwitch field and convert it into a binary data. If bit1=1,
end. Or output this eNodeB’s information.
3.133.4 Measures
BasedSriGapOptSwitch: MOD ENODEBALGOSWITCH: HoAlgoSwitch = BasedSriGapOptSwitch-1; DrxBasedSriGapOptSwitch: MOD
ENODEBALGOSWITCH: HoAlgoSwitch=DrxBasedSriGapOptSwitch-1.
3.133.5 Reference
None.
3.134 Global Procedure Switch
3.134.1 Location

13 Parameter Verification Inspection 01 Risky Parameter Verification 04 Global Procedure Switch
If parameter’s configuration is inconsistent with the recommended value, it may lead to online problems. When EnhancedPhrRptCtrlSw is
disabled, the eNodeB will continue scheduling 3RB for a while after handover. Enabled EnhancedPhrRptCtrlSw can avoid this problem.

Abnormal Data
eNodeB Parameter Current network Recommended
eNodeB ID MML object Parameter ID
Name Name configuration value
GLOBALPRO EnhancedPhrRpt EnhancedPhrRp
414 VoLTE414 0 1
CSWITCH CtrlSw tCtrlSw
3.134.3 Principles
recommended value.
 EnhancedPhrRptCtrlSw: Check the value of EnhancedPhrRptCtrlSw under GLOBALPROCSWITCH field. If EnhancedPhrRptCtrlSw = 1, end.
Or output this eNodeB’s information.
3.134.4 Measures
EnhancedPhrRptCtrlSw: MOD GLOBALPROCSWITCH: EnhancedPhrRptCtrlSw=ON.
3.134.5 Reference
None.
3.135 PCCH Configuration Information
3.135.1 Location

13 Parameter verification inspection 01 Risky Parameter Verification 05 PCCH Configuration Information
Some terminals will response re-paging in connected state, which will lead to call dropping.

Abnormal Data
Local Cell Current Network Recommended
eNodeB ID eNodeB Name MML Object Parameter ID Parameter Name
Cell ID Name Configuration Value
414 VoLTE414 0 cell0 PCCHCFG PagingSentNum Paging sent number 1 2
3.135.3 Principles
Check the parameter’s configuration below from LMT.XML file and output the current network configuration data which is inconsistent with the
recommended value.
 Paging sent number: Check the value of PagingSentNum under PCCHCFG field. If PagingSentNum = 0, end. If not, output this cell’s related
information.
3.135.4 Measures
Paging sent number: MOD PCCHCFG: LocalCellId=x, PagingSentNum=1.
3.135.5 Reference
None.
3.136 PUCCH Dynamic Configuration Information
3.136.1 Location

13 Parameter Verification Inspection 01 Risky Parameter Verification 06 PUCCH Dynamic Configuration Information
If parameter’s configuration is inconsistent with the recommended value, it may lead to online problems. There are some abnormal UEs which

they do not send SRIs occasionally on the live network. Therefore, the problem of decreased eRAB setup success rate increases significantly since SRI
period reconfiguration is reduced.
Abnormal Data
eNodeB eNodeB Local Current Network Recommende
ID Name Cell ID Configuration d Value
SriPeriodAdapti SRI Period NOQCIADAP
414 VoLTE414 0 cell0 PUCCHCFG QCIADAPTIVE
ve Adaptive Switch TIVE
3.136.3 Principles
recommended value.
 SRI Period Adaptive Switch: Check the value of SriPeriodAdaptive under PUCCHCFG field. If SriPeriodAdaptive = 2, end. Or output this cell’s
related information.
3.136.4 Measures
SRI Period Adaptive Switch: MOD PUCCHCFG: LocalCellId=0, SriPeriodAdaptive=NOQCIADAPTIVE.
3.136.5 Reference
None.
3.137 RACH Dynamic Configuration Information
3.137.1 Location

13 Parameter Verification Inspection 01 Risky Parameter Verification 07 RACH Dynamic Configuration Information

Timer for contention resolution is configured as SF64_MAC_RESOLUTION_TIMER (64) subframes, which is the product baseline and
modifying is not recommended. A smaller value leads to RRC setup success rate deterioration. Maximum number of Msg3 HARQ transmissions is
configured as 5, which is the product baseline and modifying is not recommended. A smaller value leads to RRC setup success rate deterioration.
Abnormal Data
eNodeB eNodeB Local Current Network Recommended
ID Name Cell ID Configuration Value
ContentionReso Timer for contention SF64_MAC_RESO
393704 393704 2 393704-2 RACHCFG 4
lutionTimer resolution LUTION_TIMER
Maximum number
MaxHarqMsg3
393730 393730 2 393730-2 RACHCFG of Msg3 HARQ 4 5
Tx
transmissions
3.137.3 Principles
recommended value.
 Timer for contention resolution: Check the value of ContentionResolutionTimer under RACHCFG field. If ContentionResolutionTimer = 7, end.
Or output this eNodeB’s related information.
 Maximum number of Msg3 HARQ transmissions: Check the value of MaxHarqMsg3Tx under RACHCFG field. If MaxHarqMsg3Tx = 5, end. Or
output this eNodeB’s related information.
3.137.4 Measures
Timer for contention resolution: MOD RACHCFG: LocalCellId=0, ContentionResolutionTimer=SF64_MAC_RESOLUTION_TIMER;
Maximum number of Msg3 HARQ transmissions: MOD RACHCFG: LocalCellId=0, MaxHarqMsg3Tx=5.

3.137.5 Reference
None.
3.138 RLC and PDCP Parameter Group
3.138.1 Location

13 Parameter Verification Inspection 01 Risky Parameter Verification 08 RLC and PDCP Parameter Group
Some terminals don’t support UM mode in RLC when QCI7, which will lead to eRAB setup success rate deterioration.
Abnormal Data
eNodeB
eNodeB ID MML Object Parameter ID Parameter Name Current Network Configuration Recommended Value
Name
RLCPDCPPARAGRO
393248 393248-SF RlcMode RLC mode QCI2_RlcMode_AM QCI2_RlcMode_UM
UP
3.138.3 Principles
recommended value.
 RLC mode:
a) Check the value of RlcPdcpParaGroupId corresponding with Qci=1~9 under StandardQci field.
b) Check the value of RlcMode corresponding with same RlcPdcpParaGroupId from 1) under RLCPDCPPARAGROUP field. If following
conditions are met, end. Or mark it as abnormal and output this eNodeB’s related information.
(RLCPDCPPARAGROUP: QCI=1)== 2;

3.138.4 Measures
RLC mode: MOD RLCPDCPPARAGROUP: RlcPdcpParaGroupId=X, RlcMode =RlcMode_UM/RlcMode_AM; RLCPDCPPARAGROUP
(QCI1~3, 7): (RlcMode_UM), RLCPDCPPARAGROUP (QCI4~6, 8, 9): (RlcMode_AM).
3.138.5 Reference
None.
3.139 UE Controller Timer Configuration
3.139.1 Location

13 Parameter Verification Inspection 01 Risky Parameter Verification 09 UE Controller Timer Configuration
Filter repeated RRCConnReq Timer is configured as 2s, which is the product baseline and modifying is not recommended. A smaller value leads
to an increasing times of RRC.Att and deteriorated RRC setup success rate (retransmission is not included).
Abnormal Data

eNodeB eNodeB Current Network Recommended

MML Object Parameter ID Parameter Name
ID Name Configuration Value
RRCCONNST FilterReptRrcCon Filter Repeated

393740 393740-OF 3 2
ATETIMER nReqTimer RRCConnReq Timer
3.139.3 Principles
recommended value.
 Filter repeated RRCConnReq Timer: check the value of FilterReptRrcConnReqTimer under RRCCONNSTATETIMER field. If
FilterReptRrcConnReqTimer = 2, end. Or mark it as abnormal and output this eNodeB’s information.
3.139.4 Measures
Filter Repeated RRCConnReq Timer: MOD RRCCONNSTATETIMER: FilterReptRrcConnReqTimer=2.
3.139.5 Reference
None.
3.140 Summary of Performance Optimized Parameter Verification
3.140.1 Location

13 Parameter Verification Inspection 02 Performance Optimization Parameter Verification 01 Summary of Performance Optimized Parameter Verification
1） Output the current network configuration which is inconsistent and consistent with the recommended value.

Abnormal Data
Current Number of Abnormal
Parameter Parameter Parameter Recommended
MML Object Network Parameters (must be Remark
Subject ID Name Value
Configuration modified)
Hysteresis for Must disable it. Enabling
PS data CELLPDCCH HysForCfiBas
CFI increase 0 1(1) 1 this parameter will lead
transmission ALGO edPreSch
based on PreSch to negative gain.
3.140.3 Principles
Performance optimized parameter verification has 9 inspection rules and 25 MML objects. Output current network configuration which is
inconsistent and consistent with the recommended value based on parameter ID to this rule (Please refer to the below 9 inspection rules to get the details).
3.140.4 Measures
For parameters which didn’t pass the verification, it is suggested to compare them with parameters’ baseline and modify them according to
different eNodeBs. (Modifying parameters is risky. Please operate it carefully.)
3.140.5 Reference
None.
3.141 Cell Algorithm Switch
3.141.1 Location

13 Parameter Verification Inspection 02 Performance Optimization Parameter Verification 02 Cell Algorithm Switch
1. DlCqiAdjDeltaOptSwitch: If this switch is disabled when many users are on the network, CQI will report slowly, which will lead to untimely

adjustment of MCS. Enabling this switch can quicken the adjustment speed and it has no effect for few users scenario.
2. DlEnVarIblerTargetSwitch: Suggest to disable this switch because of arithmetic bug and enable this switch after eRAN8.0.
3. PucchIrcSwitch: This para enhances PUCCH demodulation, and PucchIRCEnhance must be enabled at the same time.
4. PucchIRCEnhance: Under interference scenario, PUCCH IRC gains less than MRC. This switch can adjust in two methods and it must be
associate with PucchIrcSwitch.
5. PucchPcDtxSinrSwitch: After PucchPcPeriod=20ms and PucchPcDtxSinrSwitch=ON were put into practice at Beta Area in K, PUCCH RSRP,
UL QCI1 packet loss rate and PUCCH interference decreased and .DL BLER and DTX rate had no obvious change (The astringency of PUCCH POWER
CONTROL in Fmt 1a/1b is better than Fmt1. When PUCCH interference decreased, Fmt1 gains more.).
6. PuschDtxSwitch: If this parameter is enabled, it could separate NACK and DTX, and eNodeB can schedule HARQ retransmission based on
DTX.
7. SinrAdjustSwitch: When this switch is disabled, UL MCS could not adjust according to ACK and NACK, which will lead to IBLER
deteriorating and bring negative gain.
8. UlJointReceptionSwitch: It enhances UL demodulation and there is no negative gain. A majority of sites use this para.
9. CqiAdjAlgoSwitch: When this switch disabled, MCS could not adjust according to ACK and NACK, which will bring negative gain.
10. PdcchPcSwitch: It is the default power control way. Other methods will bring negative gain.
11. MrcIrcAdptSwitch: It enhances UL demodulation and there is no negative gain. A majority of sites use this para.
12. InnerLoopPucchSwitch: It is the default power control way. Other methods will bring negative gain.
13. SchedulerCtrlPowerSwitch: When this switch is disabled, users on middle and edge point cannot schedule on full power, which will lead to
deficient schedule.
14. EnAperiodicCqiRptSwitch: Aperiodic CQI is more accurate than periodic CQI, which is in favor of MCS adjusting. If some terminals don’t
report aperiodic CQI all the time, this parameter will inform UE to report once. When this switch disabled, MCS adjusting will be inaccurate and lead to
negative gain.
Abnormal Data
eNodeB eNodeB Local Cell Cell MML Current Network Recommende
Parameter ID Parameter Name
ID Name ID Name Object Configuration d Value
DlCqiAdjDeltaOp
CELLALG
414 VoLTE414 0 cell0 tSwitch@CqiAdj DlCqiAdjDeltaOptSwitch 0 1
OSWITCH
AlgoSwitch
DlEnVarIblerTarg
CELLALG
414 VoLTE414 0 cell0 etSwitch@CqiAdj DlEnVarIblerTargetSwitch 0 1
OSWITCH
AlgoSwitch

CELLALG PucchIrcSwitch@
414 VoLTE414 0 cell0 PucchIrcSwitch 0 1
OSWITCH IrcSwitch
CELLALG PucchIRCEnhanc
414 VoLTE414 0 cell0 PucchIRCEnhance OFF ON
OSWITCH e
PucchPcDtxSinrS
CELLALG
414 VoLTE414 0 cell0 witch@UlPcAlgo PucchPcDtxSinrSwitch 0 1
OSWITCH
Switch
CELLALG PuschDtxSwitch
414 VoLTE414 0 cell0 PuschDtxSwitch 0 1
OSWITCH @UlSchSwitch
CELLALG SinrAdjustSwitch
414 VoLTE414 0 cell0 SinrAdjustSwitch 0 1
OSWITCH @UlSchSwitch
UlJointReception
CELLALG
414 VoLTE414 0 cell0 Switch@UplinkC UlJointReceptionSwitch 0 1
OSWITCH
ompSwitch
CqiAdjAlgoSwitc
CELLALG
414 VoLTE414 1 cell1 h@CqiAdjAlgoS CqiAdjAlgoSwitch 0 1
OSWITCH
witch
CELLALG PdcchPcSwitch@
414 VoLTE414 1 cell1 PdcchPcSwitch 0 1
OSWITCH DlPcAlgoSwitch
MrcIrcAdptSwitc
CELLALG
414 VoLTE414 1 cell1 h@PuschIrcAlgo MrcIrcAdptSwitch 0 1
OSWITCH
Switch
InnerLoopPucchS
CELLALG
414 VoLTE414 1 cell1 witch@UlPcAlgo InnerLoopPucchSwitch 0 1
OSWITCH
Switch
SchedulerCtrlPow
CELLALG
414 VoLTE414 1 cell1 erSwitch@UlSch SchedulerCtrlPowerSwitch 0 1
OSWITCH
Switch
EnAperiodicCqiR
CELLALG
414 VoLTE414 1 cell1 ptSwitch@DlSch EnAperiodicCqiRptSwitch 0 1
OSWITCH
Switch
3.141.3 Principles
recommended value.

PucchPcDtxSinrSwitch is enabled. Bit7 of UlPcAlgoSwitch (under CELLALGOSWITCH) = 1, or mark it as abnormal.
CqiAdjAlgoSwitch is enabled. Bit0 of CqiAdjAlgoSwitch (under CELLALGOSWITCH) = 1, or mark it as abnormal.

EnAperiodicCqiRptSwitch is enabled. Bit5 of DlSchSwitch (under CELLALGOSWITCH) = 1, or mark it as abnormal.

InnerLoopPucchSwitch is enabled. Bit3 of UlPcAlgoSwitch (under CELLALGOSWITCH) = 1, or mark it as abnormal.
PdcchPcSwitch is enabled. Bit2 of DlPcAlgoSwitch (under CELLALGOSWITCH) = 1, or mark it as abnormal.
PucchIrcSwitch is enabled. Bit0 of IrcSwitch (under CELLALGOSWITCH) = 1, or mark it as abnormal.
PuschDtxSwitch is enabled. Bit7 of UlSchSwitch (under CELLALGOSWITCH) =1, or mark it as abnormal.
SchedulerCtrlPowerSwitch is enabled. Bit11 of UlSchSwitch (under CELLALGOSWITCH) =1, or mark it as abnormal.
SinrAdjustSwitch is enabled. Bit1 of UlSchSwitch (under CELLALGOSWITCH) =1, or mark it as abnormal.
PucchIRCEnhance is enabled. PucchIRCEnhance (under CELLALGOSWITCH) = 1, or mark it as abnormal.
DlCqiAdjDeltaOptSwitch is enabled. Bit6 of CqiAdjAlgoSwitch (under CELLALGOSWITCH) =1, or mark it as abnormal.
DlEnVarIblerTargetSwitch is enabled. Bit7 of CqiAdjAlgoSwitch (under CELLALGOSWITCH) =1, or mark it as abnormal.
MrcIrcAdptSwitch is enabled. Bit0 of PuschIrcAlgoSwitch (under CELLALGOSWITCH) =1, or mark it as abnormal.
UlJointReceptionSwitch is enabled. Bit0 of UplinkCompSwitch (under CELLALGOSWITCH) =1, or mark it as abnormal.
3.141.4 Measures
baseline and modify them according to different eNodeBs (Modifying parameters is risky. Please operate it carefully).
 PucchIRCEnhance: MOD CELLALGOSWITCH:LocalCellId=x, PucchIRCEnhance=ON;
 PucchPcDtxSinrSwitch: MOD CELLALGOSWITCH:LocalCellId=x, UlPcAlgoSwitc =PucchPcDtxSinrSwitch-1;
 InnerLoopPucchSwitch: MOD CELLALGOSWITCH:LocalCellId=x, UlPcAlgoSwitc=InnerLoopPucchSwitch-1;
 CqiAdjAlgoSwitch: MOD CELLALGOSWITCH:LocalCellId=x, CqiAdjAlgoSwitch=CqiAdjAlgoSwitch-1;
 DlCqiAdjDeltaOptSwitch: MOD CELLALGOSWITCH:LocalCellId=x, CqiAdjAlgoSwitch =DlCqiAdjDeltaOptSwitch-1;
 DlEnVarIblerTargetSwitch: MOD ELLALGOSWITCH:LocalCellId=x,CqiAdjAlgoSwitch=DlEnVarIblerTargetSwitch-1;
 EnAperiodicCqiRptSwitch: MOD CELLALGOSWITCH:LocalCellId=x, DlSchSwitch =EnAperiodicCqiRptSwitch-1;
 PdcchPcSwitch: MOD CELLALGOSWITCH:LocalCellId=x, DlPcAlgoSwitch =PdcchPcSwitch-1;
 PucchIrcSwitch: MOD CELLALGOSWITCH:LocalCellId=x, IrcSwitch =PucchIrcSwitch-1;
 PuschDtxSwitch : MOD CELLALGOSWITCH:LocalCellId=x, UlSchSwitch=PuschDtxSwitch-1;
 SchedulerCtrlPowerSwitch: MOD CELLALGOSWITCH:LocalCellId=x, UlSchSwitch =SchedulerCtrlPowerSwitch-1;
 SinrAdjustSwitch: MOD CELLALGOSWITCH:LocalCellId=x, UlSchSwitch=SinrAdjustSwitch-1;
 MrcIrcAdptSwitch: MOD CELLALGOSWITCH:LocalCellId=x, PuschIrcAlgoSwitch =MrcIrcAdptSwitch-1;
 UlJointReceptionSwitch: MOD CELLALGOSWITCH: LocalCellId =x, UplinkCompSwitch =UlJointReceptionSwitch-1.

3.141.5 Reference
None.
3.142 Cell CQI Adaptive Parameter Configuration
3.142.1 Location

13 Parameter Verification Inspection 02 Performance Optimization Parameter Verification 03 Cell CQI Adaptive Parameter Configuration
When CQI period adaptive switch is enabled: The CQI reporting period adaptively changes based on the Uu interface load of the cell. This
adjustment achieves better balance between timely CQI report and PUCCH resource reduction. Enabled handover aperiodic CQI config switch benefits
MCS after the handover, which cooperates with HoStaticMcsTimer to increase the throughput. This para is test on N network and the throughput increased
by 8% within 1s after the handover.
Abnormal Data
eNodeB eNodeB Local Cell Cell Current Network Recommended
MML Object Parameter ID Parameter Name
ID Name ID Name Configuration Value
CELLCQIAD CqiPeriodAdaptiv CQI period
414 VoLTE414 0 cell0 OFF ON
APTIVECFG e adaptive switch
Handover
CELLCQIAD HoAperiodicCqiC
414 VoLTE414 0 cell0 aperiodic CQI OFF ON
APTIVECFG fgSwitch
config switch
3.142.3 Principles
recommended value.

Handover aperiodic CQI config switch is enabled. HoAperiodicCqiCfgSwitc (under CELLCQIADAPTIVECFG) = 1, or mark it as abnormal.
CQI period adaptive switch is enabled. CqiPeriodAdaptive (under CELLCQIADAPTIVECFG) = 1, or mark it as abnormal.
3.142.4 Measures
CQI period adaptive switch: MOD CELLCQIADAPTIVECFG: LocalCellId=x, CqiPeriodAdaptive =ON;
Handover aperiodic CQI config switch: MOD CELLCQIADAPTIVECFG: LocalCellId=x, HoAperiodicCqiCfgSwitch=ON.
3.142.5 Reference
None.
3.143 Cell Downlink Scheduling Parameter
3.143.1 Location

13 Parameter Verification Inspection 02 Performance Optimized Parameter Verification 04 Cell Downlink Scheduling Parameter
eNodeB Interference Randomize Modular: Adopt MOD3 by default. This way is effective in more scenarios than big modular. Handover UE
Static MCS Scheduling Timer: This benefits MCS after handover, which cooperates with HoAperiodicCqiCfgSwitch to increase the throughput. This para
is test on N network and the throughput increased by 8% within 1s after the handover.
Abnormal Data
eNodeB Local Cell Cell Current Network Recommended
eNodeB ID MML Object Parameter ID Parameter Name
Name ID Name Configuration Value
414 VoLTE414 0 cell0 CELLDLSCH EnbInterfRandM eNodeB MOD6 MOD3

Interference
ALGO od Randomize
Modular
Handover UE
CELLDLSCH HoStaticMcsTim
414 VoLTE414 0 cell0 Static MCS 60 10
ALGO er
Scheduling Timer
3.143.3 Principles
recommended value.
Handover UE Static MCS Scheduling Timer is 10 (ms). HoStaticMcsTimer (under CellDlschAlgo) = 10, or mark it as abnormal.
eNodeB Interference Randomize Modular is MOD3 (3). EnbInterfRandMod (under CellDlschAlgo) f = 0, or mark it as abnormal.
3.143.4 Measures
eNodeB Interference Randomize Modular: MOD CELLDLSCHALGO: LocalCellId=x, EnbInterfRandMod=MOD3;
Handover UE Static MCS Scheduling Timer: MOD CELLDLSCHALGO: LocalCellId=x, HoStaticMcsTimer=10.
3.143.5 Reference
None.
3.144 Cell Power Control Algorithm Parameter
3.144.1 Location

13 Parameter Verification Inspection 02 Performance Optimized Parameter Verification 05 Cell Power Control Algorithm Parameter

After PucchPcPeriod=20ms and PucchPcDtxSinrSwitch=ON put into practice at Beta Area in K, PUCCH RSRP, UL QCI1 packet loss rate and
PUCCH interference decreased and. DL BLER and DTX rate had no obvious change (The astringency of PUCCH POWER CONTROL in Fmt 1a/1b is
better than Fmt1. When PUCCH interference decrease, Fmt1 gains more).
Abnormal Data
eNodeB Local Cell Current Network Recommended
eNodeB Name Cell Name MML Object Parameter ID Parameter Name
ID ID Configuration Value
Pucch Power Control
414 VoLTE414 0 cell0 CELLPCALGO PucchPcPeriod 10 1
Period
3.144.3 Principles
recommended value.

Pucch Power Control Period is 1 (20ms). PucchPcPeriod (under CELLPCALGO) = 1, or mark it as abnormal
3.144.4 Measures
Pucch Power Control Period: MOD CELLPCALGO: LocalCellId=x, PucchPcPeriod=1.
3.144.5 Reference
None.

3.145 PDCCH Algorithm Parameter
3.145.1 Location

13 Parameter Verification Inspection 02 Performance Optimized Parameter Verification 06 PDCCH Algorithm Parameter
Korea network verifies that downlink throughput increases by 2% after modifying this parameter.
Abnormal Data
eNodeB Local Cell Cell MML Parameter Current Network Recommended
eNodeB ID Parameter ID
Name ID Name Object Name Configuration Value
CELLPDCC PDCCH Max
414 VoLTE414 0 cell0 PdcchMaxCodeRate 75 95
HALGO Code Rate
3.145.3 Principles
recommended value.

PdcchMaxCodeRate (under CELLPDCCHALGO) = 95, or mark it as
PDCCH Max Code Rate is 0.95.
abnormal.
3.145.4 Measures
PDCCH Max Code Rate: MOD CELLPDCCHALGO: LocalCellId=x, PdcchMaxCodeRate=95.
3.145.5 Reference
None.

3.146 SRS Adaptive Parameter Configuration
3.146.1 Location

13 Parameter Verification Inspection 02 Performance Optimized Parameter Verification 07 SRS Adaptive Parameter Configuration
SrsSubframeRecfSwitch and SrsPeriodAdaptive must be enabled at the same time to make sure that the number of SRS supported users reaches
max capacity.
Note: Since eRAN7.0, SrsSubframeCfg can be set to SC3/SC4/SC5/SC6 on the precondition of SrsSubframeRecfSwitch and SrsPeriodAdaptive
are enabled at the same time. However, it is recommended to set to SC3 to be consistent with MML help file. This recommended value is the product
baseline since eRAN6.0.
Abnormal Data
eNodeB eNodeB Local Cell Parameter Current Network Recommended
Cell Name MML Object Parameter Name
ID Name ID ID Configuration Value
CELLSRSAD SrsPeriodAda SRS period adaptive
414 VoLTE414 0 cell0 OFF ON
APTIVECFG ptive switch
3.146.3 Principles
recommended value.
SRS period adaptive switch is enabled. SrsPeriodAdaptive (under CELLSRSADAPTIVECFG) = 1, or mark it as abnormal.
3.146.4 Measures
SRS period adaptive switch: MOD CELLSRSADAPTIVECFG: LocalCellId=x, SrsPeriodAdaptive = ON.
3.146.5 Reference
None.
3.147 Cell Uplink Scheduling Parameter
3.147.1 Location

13 Parameter Verification Inspection 02 Performance Optimized Parameter Verification 08 Cell Uplink Scheduling Parameter
Fs InRandom strategy in middle/low load situation enables neighboring cells using different uplink PRB, reduces uplink interference, and
enhances user’s performance. What’s more, EPF uplink scheduling strategy is the best allocation strategy and it is used by default.
Abnormal Data
eNodeB eNodeB Local Cell Cell Parameter Current Network Recommended
MML Object Parameter Name
ID Name ID Name ID Configuration Value
CELLULSCH UlRbAllocati Uplink Resource Block FS_INRANDO
414 VoLTE414 0 cell0 FS_NONFS_ADAPTIVE
ALGO onStrategy Allocation Strategy M_ADAPTIVE
CELLULSCH Uplink Scheduling ULSCH_STRATEGY_M ULSCH_STRA
414 VoLTE414 1 cell1 UlschStrategy
ALGO Strategy AX_CI TEGY_EPF
3.147.3 Principles
recommended value.

Uplink Resource Block Allocation Strategy is Fs InRandom Strategy. UlRbAllocationStrategy (under CellUlschAlgo) = 1, or mark it as abnormal.
Uplink Scheduling Strategy is ULSCH_STRATEGY_EPF (EPF). UlschStrategy (under CellUlschAlgo) = 0, or mark it as abnormal.
3.147.4 Measures
Uplink Resource Block Allocation Strategy: MOD CELLULSCHALGO: LocalCellId=x, UlRbAllocationStrategy =
FS_INRANDOM_ADAPTIVE;
Uplink Scheduling Strategy: MOD CELLULSCHALGO: LocalCellId=x, UlschStrategy=ULSCH_STRATEGY_EPF.
3.147.5 Reference
None.
3.148 TimeAlignmentTimer
3.148.1 Location

13 Parameter Verification Inspection 02 Performance Optimized Parameter Verification 09 TimeAlignmentTimer
If parameter’s configuration is inconsistent with the recommended value, it may lead to online problems. This rule optimizes uplink timer
performance when configured TimeAlignmentTimer is too long and decreases numbers of sending unnecessary uplink time alignment command to
motionless or low speed users, saving Uu interface resource and help UE under DRX state to save electricity while not affect uplink time alignment
performance.
Abnormal Data
eNodeB eNodeB Local Cell Cell Parameter Current Network Recommendation
MML Object Parameter ID
ID Name ID Name Name Configuration Value

Uplink time
TIMEALIGN TimingAdvCm
414 VoLTE414 0 cell0 alignment OFF ON
MENTTIMER dOptSwitch
timer
3.148.3 Principles
recommended value.

TimingAdvCmdOptSwitch (under TimeAlignmentTimer) = 1, or mark it as
TimingAdvCmdOptSwitch is enabled.
abnormal.
3.148.4 Measures
For parameters which their configurations are different from the recommendation value, it is suggested to compare them with parameters’
baseline and modify them according to different eNodeBs. (Modifying network’s parameters is risky. Please operate it carefully.)
Uplink time alignment timer: MOD TATIMER: LocalCellId=x, TimingAdvCmdOptSwitch=ON.
3.148.5 Reference
None.
3.149 UE Timer & Constant Information
3.149.1 Location

13 Parameter Verification Inspection 02 Performance Optimized Parameter Verification 10 UE Timer & Constant Information
If parameter’s configuration is inconsistent with the recommended value, it may lead to online problems. RRC Setup success rate improved
significantly after T300 revised from 200ms to 1000ms. Operators1 increases from 99.5% to 99.9%, Operators2 increases from 99.7% to 99.95% and

Operators3 increases from 99.45% to 99.95%. This recommended value is the product baseline since eRAN9.0.
Abnormal Data
Local Cell Parameter Current Network Recommended
eNodeB ID eNodeB Name Cell Name MML Object Parameter Name
ID ID Configuration Value
414 VoLTE414 0 cell0 UETIMERCONST T300 Time 300 MS200_T300 MS1000_T300
3.149.3 Principles
recommended value.

Time 300 = MS1000_T300 (1000 ms). T300 (under UETIMERCONST) = 5, or mark it as abnormal.
3.149.4 Measures
For parameters which their configurations are different from the recommendation value, it is suggested to compare them with parameters’
baseline and modify them according to different eNodeBs. (Modifying network’s parameters is risky. Please operate it carefully.)
Time 300: MOD UETIMERCONST: LocalCellId=x, T300=MS1000_T300.
3.149.5 Reference
None.
3.150 Intra-frequency Cells Are Not in the Same BBP
3.150.1 Location

11 CA Inspection 01 CA Provisioning Hardware Check 01 Intra-frequency Cells Are Not in the Same BBP

If CoMP and SFN features are activated at the same time, it may lead to a shortage of backplane bandwidth, which will affect these features’
provisioning.
1) If different cells under same eNodeB have same DLEarfcn but different primary BBP’s CN, SRN and SN, mark it as abnormal and output their
related information.
Abnormal Intra-Freq Cells

eNodeB ID eNodeB Name Local Cell ID Cell Name DLEarfcn CN SRN SN Device No
414 VoLTE414 0 cell0 37900 0 0 1 255
414 VoLTE414 1 cell1 37900 0 0 4 255
3.150.3 Principles
1) Find out intra-freq cells: Check the value of DLEarfcn under Cell field from LMT.XML file, gather cells with same DLEarfcn together and go to
next step.
2) Judge whether intra-freq cells are under the same board or not: Check cells’ primary BBP information with same DLEarfcn by MML’s dsp cell
command. If their CN, SRN and SN are not the same, it indicates they are not in the same board and output the exception, or end.
3.150.4 Measures
If changes are necessary, please submit service request to GTAC and HO will support it.
3.150.5 Reference
None.
3.151 Inter-frequency Cells Are Under Same LBBPC
3.151.1 Location

11 CA Inspection 01 CA Provisioning Hardware Check 02 Inter-frequency Cells Are Under Same LBBPC

If all inter-freq cells are under the C board, it couldn’t proceed to CA.
1) If cells with different DLEarfcn under the same eNodeB have same board type (LBPPC), output this exception.
Inter-freq Cells Are Under Same LBBPC

Group eNodeB eNodeB Local Cell Cell Frequency DLEarf S Board RRU Device
CN SRN BBU Type
No ID Name ID Name Band cn N Type Version No
1 414 VoLTE41 0 cell0 38 37900 0 0 1 BBU 3900 LBBPC LRRU V1 255
1 414 VoLTE41 1 cell1 38 36900 0 0 2 BBU 3900 LBBPC LRRU V2 255
3.151.3 Principles
1) Find out inter-freq cells: Check the value of DLEarfcn under Cell field from LMT.XML file, make groups with two different DLEarfcn and go to
next step.
2) Judge whether they are BBU3900 type: Check the Description by MML’s DSP brdmfrinfo command. For example, if Description =
Manufactured Board, BBU3900, WD22LBBPD2, LTE Baseband Processing Unit D (3 cell, 4T4R), 1*1, it indicates this board is BBU3900 type
since there is “BBU3900” field. If both of them are BBU3900, go to next step, or end.
3) Judge whether both of them are under C board: Check the Type by MML’s DSP brdmfrinfo command. If “Type = WD22LBBPC1”, it indicates
C type since there is “LBBPC”. If both of them are on C board, output cells’ related information, or end.
3.151.4 Measures
3.151.5 Reference
None.

3.152 Inter-frequency Cells’ LBBPd and UBBP Are Not in Slot 2/3
3.152.1 Location

11 CA inspection 01 CA Provisioning Hardware Check 03 Inter-frequency Cells’ LBBPd and UBBP Are Not in Slot 2/3
If all the D or U boards are not in slot 2/3, it may lead to a shortage of backplane bandwidth, which will affect these features provisioning.
1) If cells with different DLEarfcn under the same eNodeB have different CN, SRN and SN, not all the board type are LBBPC and there is no slot 2
or 3, output this exception.
All the D or U boards Are Not in Slot 2/3

Group eNode eNodeB Local Cell Frequency DLEar SR BBU Board RRU Device
CN SN
No B ID Name cell ID Name band fcn N type Type version No
VoLTE4 BBU LRRU
1 414 0 cell0 38 37900 0 0 1 LBBPC 255
1 3900 V1
VoLTE4 BBU LRRU
1 414 1 cell1 38 36900 0 0 2 LBBPC 255
1 3900 V2
3.152.3 Principles
1) Find out inter-freq cells: Check the value of DLEarfcn under Cell field from LMT.XML file, make groups with two different DLEarfcn and go to
next step.
2) Judge whether they are BBU3900 type: Check the Description by MML’s DSP brdmfrinfo command. For example, if Description =
Manufactured Board, BBU3900, WD22LBBPD2, LTE Baseband Processing Unit D (3 cell, 4T4R), 1*1, it indicates this board is BBU3900 type
since there is “BBU3900” field. If both of them are BBU3900, go to next step, or end.
3) If BBP’s CN, SRN and SN are not exactly same (Run MML’s DSP cell command to check the CN, SRN and SN based on primary BBP
information), not all Baseboard Type (Whether DSP brdmfrinfo’s “type” contains “LBBPC”) are LBBPC, and there is no slot 2/3, output the
exception.

3.152.4 Measures
3.152.5 Reference
None.
3.153 The RRU Platform of Inter-frequency Are Not Same Check
3.153.1 Location

11 CA inspection 01 CA Provisioning Hardware Check 04 The RRU Platform of Inter-frequency Are Not Same Check
In order to achieve synchronous delay, it needs two-carrier RRU or two RRUs with same type to support CA, or CA performance can’t be
guaranteed.
1) If cells under same eNodeB have same FreqBand but different RRU versions, output it as abnormal.
Inter-Freq Cells with Different RRU Versions

eNodeB ID eNodeB Name Local cell ID Cell Name Band Downlink Frequency RRU Version Device No
414 VoLTE414 0 cell0 38 37900 LRRU V1 255
414 VoLTE414 1 cell1 38 37900 LRRU V2 255
3.153.3 Principles
1) Find cells’ information with same FREQBAND: Check the value of FREQBAND under Cell field from LMT.XML file, gather cells with same
FREQBAND together and go to next step.
2) Check the value of SectorEqmId under eUCellSectorEqm field based on 1)’s LocalCellId and record the value.
3) Check the value of CN, SRN and SN under SECTOREQM field based on 2)’s SectorEqmId and record the value.
4) Check board description based on 3)’s CN, SRN and SN by MML’s DSP brdmfrinfo command. If RRU versions (such as: LRRU V1) are
different, output it as abnormal. (Method of judging different RRU versions: If the Description is RRU3221, WD5MLRUB870, LRRU V1, LTE

Single-mode Multi-carriers Remote Radio Unit (TX2620-2690MHz/RX2500-2570MHz,-48VDC, 5G, 2T2R, With Installation Kit). Compare the
red part.)
3.153.4 Measures
3.153.5 Reference
None.
3.154 BasedSriGapOptSwitch Check
3.154.1 Location

11 CA Inspection 02 Compatibility Parameter Check 01 BasedSriGapOptSwitch Check
When this switch is enabled, it will consider transmission of scheduling request indicators (SRIs) when configuring measurement gaps for a UE
not in the discontinuous reception (DRX) state, which will decrease the risk of call dropping. When this switch is disabled, it will result in the opposite
effect.
1) Output eNodeBs’ related information with disabled BasedSriGapOptSwitch under non-DRX state.
Abnormal Data
eNodeB ID eNodeB Name ENodeB Version BasedSriGapOptSwitch
5047 eNODEB47 BTS3900 V100R009C00SPC170 Off
3.154.3 Principles
1) Check the value of HoCommOptSwitch under ENODEBALGOSWITCH field from LMT.XML file.
2) Convert it into a binary value.
a) If bit0 is 1, it means this switch is enabled and end.

b) If bit0 is 0, it means this switch is disabled and go to step 3).
3) Mark it as abnormal and output this eNodeB’s information.
3.154.4 Measures
Run MML command to enable the switch: MOD ENODEBALGOSWITCH: HoCommOptSwitch = BasedSriGapOptSwitch-1.
3.154.5 Reference
None.
3.155 DrxBasedSriGapOptSwitch Check
3.155.1 Location

11 CA Inspection 02 Compatibility Parameter Check 02 DrxBasedSriGapOptSwitch Check
When this switch is enabled, it will consider transmission of scheduling request indicators (SRIs) when configuring measurement gaps for a UE
in the discontinuous reception (DRX) state, which will decrease the risk of call dropping. When this switch is disabled, it will result in the opposite effect.
1) Output eNodeBs’ related information with disabled RsvdSwPara1-bit17 (V100R009C00 version).
Abnormal Data
eNodeB ID eNodeB Name eNodeB Version RsvdSwPara1-bit17
5014 TMO-5014 BTS3900 V100R009C00SPC234B022 Off
2) Output eNodeBs’ related information with disabled DrxBasedSriGapOptSwitch (V100R010C10 version).
Abnormal Data
eNodeB ID eNodeB Name eNodeB Version DrxBasedSriGapOptSwitch
414 VoLTE414 BTS3900 V100R010C10SPC110B304 Off
3.155.3 Principles
1) For V100R009C00SPC160 and its later versions: Check the value of RsvdSwPara1 under ENBRSVDPARA field from LMT.XML file and

convert it into a binary value. If bit17 = 0, mark it as abnormal and output this eNodeB’s related information, or end.
2) For V100R010C10 version: Check the value of HoCommOptSwitch under ENODEBALGOSWITCH field from LMT.XML file and convert it
into a binary value. If bit2 = 0, mark it as abnormal and output this eNodeB’s related information, or end.
3.155.4 Measures
1) V100R009C00SPC160 and its later versions: Run MML command to enable the switch: MOD ENBRSVDPARA: RsvdSwPara1
=RsvdSwPara1_bit17-1;
2) V100R010C10 version: Run MML command to enable the switch: MOD ENODEBALGOSWITCH: HoCommOptSwitch =
DrxBasedSriGapOptSwitch-1.
3.155.5 Reference
None.
Note: This rule is just for eRAN7.0 (eRAN7.0 SPC160 and its later version) and eRAN8.1 version.
3.156 MeasCycleSCell Check
3.156.1 Location

11 CA Inspection 02 Compatibility Parameter Check 03 MeasCycleSCell Check
A smaller value of this parameter indicates a shorter sampling period and therefore results in that the CA UE measures the radio resources of the
SCell more frequently. However, this also increases the UE power consumption. A larger value of this parameter results in the opposite effect. If the
sampling period is not configured and no compatibility protection mechanism is adopted for the CA UE, the CA UE's activity is unpredictable when the
eNodeB configures a SCell for the CA UE, which will increase the risk of call dropping.
1) Output eNodeBs’ related information if RsvdPara21 is not 3 (eRAN7.0 version).
Abnormal Data
eNodeB ID eNodeB Name eNodeB Version RsvdPara21
4210 B4210 BTS3900 V100R009C00SPC040B026 0

2) Output cells’ related information if MeasCycleSCell is not 320ms (eRAN8.1 version).
Abnormal Data
Local Cell
eNodeB ID eNodeB Name eNodeB Version Cell Name MeasCycleSCell
ID
414 VoLTE414 BTS3900 V100R010C10SPC110B304 0 cell0 Not configured
3.156.3 Principles
1) eRAN7.0 version: Check the value of RsvdPara21 under ENBRSVDPARA field from LMT.XML file. If it is not 3, mark it as abnormal and
output this eNodeB’s related information, or end.
2) eRAN8.1 version: Check the value of MeasCycleSCell under CAMGTCFG field from LMT.XML file. If it is not 320ms, mark it as abnormal
and output this cell’s related information, or end.
3.156.4 Measures
1) eRAN7.0 version: Run MML command to set it to recommended value: MOD ENBRSVDPARA:RsvdPara21 = 3;
2) eRAN8.1 version: Run MML command to set it to recommended value: MOD CAMGTCFG: LocalCellId=X, MeasCycleSCell = 320ms.
3.156.5 Reference
None.
3.157 ApCqiRptAbnormalCtrlSwitch Check
3.157.1 Location

11 CA Inspection 02 Compatibility Parameter Check 04 ApCqiRptAbnormalCtrlSwitch Check
This switch indicates whether to apply a compatibility solution to abnormal aperiodic CQI reporting. If it is enabled, when the RRC reconfig
periodic CQI, the aperiodic CQI information is added. If it is disabled, when the RRC reconfig periodic CQI, the aperiodic CQI information is not added if

the aperiodic CQI setting isn't changed, which will increase the risk of call dropping.
Abnormal Data
2) Output eNodeBs’ related information with disabled ApCqiRptAbnormalCtrlSwitch (V100R010C10 version).
Abnormal Data
eNodeB ID eNodeB Name eNodeB Version ApCqiRptAbnormalCtrlSwitch
414 VoLTE414 BTS3900 V100R010C10SPC110B304 Off
3.157.3 Principles
1) V100R009C00 version: Check the value of RsvdSwPara1 under ENBRSVDPARA field from LMT.XML file and convert it into a binary
number. If bit11 = 0, mark it as abnormal and output this eNodeB’s related information, or end.
2) V100R010C10 version: Check the value of CompatibilityCtrlSwitch under ENODEBALGOSWITCH field from LMT.XML file and convert it
into a binary number. If bit1 = 0, mark it as abnormal and output this eNodeB’s related information, or end.
3.157.4 Measures
1) V100R009C00 version: Run MML command to enable the switch: MOD ENBRSVDPARA:RsvdSwPara1=RsvdSwPara1_bit11-1;
2) V100R010C10 version: Run MML command to enable the switch: MOD ENODEBALGOSWITCH: CompatibilityCtrlSwitch =
ApCqiRptAbnormalCtrlSwitch-1.
3.157.5 Reference
None.
3.158 DrxRcvDtxProSwitch Check
3.158.1 Location

11 CA Inspection 02 Compatibility Parameter Check 05 DrxRcvDtxProSwitch Check

If this switch is on in carrier aggregation (CA) scenarios, the eNodeB determines whether two consecutive DTXs occur based on HARQ
feedbacks on both the primary component carrier (PCC) and the secondary component carrier (SCC). If two consecutive DTXs occur, the eNodeB
determines whether the UE enters the DRX sleep time based on conditions in common scenarios. In CA scenarios, the setting of this parameter in the PCell
and the SCell must be the same, or it will increase the risk of call dropping.
1) Output cells’ related information with disabled RsvdSwPara1-bit7 (V100R009C00 version).
Abnormal Data
Local
eNodeB ID eNodeB Name eNodeB Version Cell Name RsvdSwPara1-bit7
Cell ID
BTS3900
5014 TMO-5014 0 Cell0 Off
V100R009C00SPC234B022
2) Output cells’ related information with disabled DrxRcvDtxProSwitch (V100R010C10 version).
Abnormal Data
eNodeB ID eNodeB Name eNodeB Version Local Cell ID Cell Name DrxRcvDtxProSwitch
BTS3900
414 VoLTE414 0 cell0 Off
V100R010C10SPC110B304
3.158.3 Principles
1) For V100R009C00 version: Check the value of RsvdSwPara1 under ENBCELLRSVDPARA field from LMT.XML file, and convert it into a
binary number. If bit7 = 0, mark it as abnormal and output this cell’s related information. Or end.
2) For V100R010C10 version: Check the value of DrxRcvDtxProSwitch under CELLDRXPARA field from LMT.XML file. If
DrxRcvDtxProSwitch = 0, mark it as abnormal and output this cell’s related information. Or end.
3.158.4 Measures
1) For V100R009C00 version: Run MML command to enable the switch: MOD ENBCELLRSVDPARA:LocalCellId=X, RsvdSwPara1 =
RsvdSwPara1_bit7-1;
2) For V100R010C10 version: Run MML command to enable the switch: MOD CELLDRXPARA: LocalCellId=X, DrxRcvDtxProSwitch=ON.

3.158.5 Reference
None.
3.159 CaGapMeasPriOffSwitch Check
3.159.1 Location

11 CA Inspection 02 Compatibility Parameters Check 06 CaGapMeasPriOffSwitch Check
This option specifies whether the eNodeB preferentially deletes the inter-frequency measurement configuration after a UE reports event A4 for
configuring a SCell. If this option is selected, the eNodeB preferentially sends an A4-related measurement configuration deletion message. If this option is
deselected, the eNodeB sends the SCell configuration message to the UE before sending an A4-related measurement configuration deletion message to the
UE, which will increase the risk of call dropping.
1) Output eNodeBs’ related information with disabled CaGapMeasPriOffSwitch.
Abnormal Data
eNodeB ID eNodeB Name eNodeB Version CaGapMeasPriOffSwitch
BTS3900
5047 5G-S Off
V100R009C00SPC170
3.159.3 Principles
Check the value of ProtocolCompatibilitySw under GLOBALPROCSWITCH field from LMT.XML file and convert it into a binary number. If
bit0 = 0, mark it as abnormal and output this cell’s related information. Or end.
3.159.4 Measures
Run MML command to enable the switch: MOD GLOBALPROCSWITCH: ProtocolCompatibilitySw=CaGapMeasPriOffSwitch-1.

3.159.5 Reference
None.
3.160 SCellModCaMeasRmvSwitch Check
3.160.1 Location

11 CA Inspection 02 Compatibility Parameter Check 07 SCellModCaMeasRmvSwitch Check
This option controls whether to delete the A2 and A6 measurement configuration for SCC (Secondary Component Carrier) of the UE before
changing the SCell of the UE. If this option is selected, upon receiving an A6/A2 measurement report from a UE, the eNodeB sends an A2- and A6-related
measurement configuration deletion message to the UE before changing the SCell of the UE. If this option is deselected, upon receiving an A6/A2
measurement report from a UE, the eNodeB does not send an A2- and A6-related measurement configuration deletion message to the UE before changing
the SCell of the UE, which will increase the risk of call dropping.
Abnormal Data
2) Output eNodeBs’ related information with disabled SCellModCaMeasRmvSwitch (V100R010C10 version).
Abnormal Data
eNodeB ID eNodeB Name eNodeB Version SCellModCaMeasRmvSwitch
BTS3900
414 VoLTE414 Off
V100R010C10SPC110B304
3.160.3 Principles
1) For V100R009C00 version: Check the value of RsvdSwPara1 under ENBRSVDPARA field from LMT.XML file, and convert it into a binary
number. If bit20 = 0, mark it as abnormal and output this cell’s related information. Or end.
2) For V100R010C10 version: Check the value of ProtocolCompatibilitySw under GLOBALPROCSWITCH field from LMT.XML file, and

convert it into a binary number. If bit6 = 0, mark it as abnormal and output this cell’s related information. Or end.
3.160.4 Measures
1) For V100R009C00 version: Run MML command to enable the switch: MOD ENBRSVDPARA:RsvdSwPara1= RsvdSwPara 1_bit20-1;
2) For V100R010C10 version: Run MML command to enable the switch: MOD GLOBALPROCSWITCH: ProtocolCompatibilitySw =
SCellModCaMeasRmvSwitch-1.
3.160.5 Reference
None.
3.161 Check of CA UE Chose Mode
3.161.1 Location

11 CA Inspection 02 Compatibility Parameter Check 08 Check of CA UE Chose Mode
If this parameter is set to ANR_UE_CAP (ANR UE Capability) and the neighboring cell is an unknown cell or the PCI confusion occurs, the
ANR algorithm instructs CA UEs which are capable to perform CGI reading to get new neighboring in time or handover into correct cells to avoid call
dropping. If it is not ANR_UE_CAP, it will increase the risk of call dropping.
1) Output eNodeBs’ related information with disabled CaGapMeasPriOffSwitch.
Abnormal Data
eNodeB ID eNodeB Name eNodeB Version CA UE Chose Mode
5047 5G-S BTS3900 V100R009C00SPC170 CA UE CAP
3.161.3 Principles
Check the value of CaUeChoseMode under ANR field from LMT.XML file. If CaUeChoseMode = 2, it indicates ANR UE CAP. If not, mark it
as abnormal and output this eNodeB’s related information.

3.161.4 Measures
Run MML command to set the data to recommended value: MOD ANR: CaUeChoseMode=ANR_UE_CAP.
3.161.5 Reference
None.
3.162 CaCqiAndAckAbnCtrlSwitch Check
3.162.1 Location

11 CA Inspection 02 Compatibility Parameter Check 09 CaCqiAndAckAbnCtrlSwitch Check
If this option is selected, the SimulAckNackAndCqiSwitc is set to False for CA UEs. If this option is deselected, the
SimulAckNackAndCqiSwitc is set based on the original algorithms.
1) Output eNodeBs’ related information with disabled CaCqiAndAckAbnCtrlSwitch.
Abnormal Data
eNodeB ID eNodeB Name eNodeB Version CaCqiAndAckAbnCtrlSwitch
BTS3900
414 VoLTE414 V100R010C10SPC110B30 Off
3.162.3 Principles
Check the value of CompatibilityCtrlSwitch under ENODEBALGOSWITCH field from LMT.XML file and convert it into a binary number. If
bit6 = 0, mark it as abnormal and output its corresponding eNodeB’s information. Or end.

3.162.4 Measures
Run MML command to enable the switch: MOD ENODEBALGOSWITCH: CompatibilityCtrlSwitch=CaCqiAndAckAbnCtrlSwitch-1.
3.162.5 Reference
None.
Note: This rule is just for eRAN8.1 version.
3.163 SCC Quiet Time Check
3.163.1 Location

11 CA Inspection 02 Compatibility Parameter Check 10 SCC Quiet Time Check
SCC quiet time indicates the SCC unavailability duration. Some multi-mode UEs (for example, SRLTE/SLTE UEs) periodically do not receive
signals of the SCell but detect signals of another RAT in CA scenarios. This causes an increase in the number of residual erroneous blocks in the SCell,
triggering SCell deactivation and an increased call drop rate. This rule is applicable for all V100R008C10 versions.
1) Output cells’ related information with RsvdPara31 ≠ 200.
Abnormal Data
eNodeB ID eNodeB Name eNodeB Version Local Cell ID Cell Name RsvdPara31
414 VoLTE414 BTS3900 V100R010C10SPC110B304 0 cell0 230
3.163.3 Principles
Check the value of RsvdPara31 under ENBCELLRSVDPARA field from LMT.XML file. If RsvdPara31 ≠ 200, mark it as abnormal and output
this cell’s related information, or end.
3.163.4 Measures
Run MML command to open the switch: MOD ENBCELLRSVDPARA: RsvdPara31 = 200.

3.163.5 Reference
None.
Note: This rule is just for eRAN8.1 version.
3.164 Risky Parameter Verification
3.164.1 Location

15 Subject Summary 01 Parameter Verification Inspection 01 Risky Parameter Verification
1) Output the number of exceptions of each rule under risky parameter verification subject.
Summary
Rule Name Number of Exceptions
01 Summary of Risky Parameter Verification 5
02 PDCCH Algorithm Parameter 1
03 eNodeB Algorithm Switch 2
04 Global Procedure Switch 1
05 PCCH Configuration Information 0
06 PUCCH Dynamic Configuration

1
Information
07 RACH Dynamic Configuration Information 0
08 RLC and PDCP Parameter Group 0
09 UE Controller Timer Configuration 0
3.164.3 Principles
Summarize the number of exceptions of each rule under risky parameter verification subject.

3.164.4 Measures
If detailed report is desired, please check “Risky Parameter Verification” rule to generate it on OMStar-E tool again.
3.164.5 Reference
None.
3.165 Performance Optimized Parameter Verification
3.165.1 Location

15 Subject Summary 01 Parameter Verification Inspection 02 Performance Optimized Parameter Verification
If parameter’s configuration is inconsistent with the recommended value, it would lead to degenerate network performance.
1) Output the number of exceptions of each rule under performance optimized parameter verification subject.
Summary
Rule Name Number of Exceptions
01 Summary of Performance Optimized
17
Parameter Verification
02 Cell Algorithm Switch 9
03 Cell CQI Adaptive Parameter
1
Configuration
04 Cell Downlink Scheduling Parameter 2
05 Cell Power Control Algorithm
1
Parameter
06 PDCCH Algorithm Parameter 1
07 SRS Adaptive Parameter
0
Configuration
08 Cell Uplink Scheduling Parameter 1

09 TimeAlignmentTimer 1
10 UE Timer & Constant Information 1
3.165.3 Principles
Summarize the number of exceptions of each rule under performance optimized parameter verification subject.
3.165.4 Measures
If detailed report is desired, please check “Performance Optimized Parameter Verification” rule to generate it on OMStar-E tool again.
3.165.5 Reference
None.


Guidance of LTE FDD Inspection SOP Rules-R11.1.4

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Guidance of LTE FDD Inspection SOP Rules-R11.1.4

Caricato da

Copyright:

Formati disponibili

Guidance of LTE FDD Inspection SOP Rules Internal

Product Version Confidentiality

Guidance of LTE FDD Inspection SOP Rules

Prepared by: Chenlingxia WX322818, Date: 2016-03-07

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Page 1 of 361

Date Version Description Author

Huawei Proprietary and Confidential Page 2 of 361

Guidance of LTE FDD Inspection SOP Rules..................................................................................................................................................1

3.1 Network Health Indicator.....................................................................................................................................................................40

Huawei Proprietary and Confidential Page 3 of 361

3.74.2 Rules Description......................................................................................................................................................................172

3.87.2 Rules Description......................................................................................................................................................................191

3.113.2 Rules Description......................................................................................................................................................................225

3.120.2 Rules Description......................................................................................................................................................................234

3.127.2 Rules Description......................................................................................................................................................................242

3.134.2 Rules Description......................................................................................................................................................................250

3.141.2 Rules Description......................................................................................................................................................................258

3.148.2 Rules Description......................................................................................................................................................................270

3.155.2 Rules Description......................................................................................................................................................................279

3.162.2 Rules Description......................................................................................................................................................................296

3.169.2 Rules Description......................................................................................................................................................................303

3.176.2 Rules Description......................................................................................................................................................................311

3.183.2 Rules Description......................................................................................................................................................................325

3.190.2 Rules Description......................................................................................................................................................................337

3.197.2 Rules Description......................................................................................................................................................................348

3.204.2 Rules Description......................................................................................................................................................................357

3.211.2 Rules Description......................................................................................................................................................................365

3.218.2 Rules Description......................................................................................................................................................................374

Huawei Proprietary and Confidential Page 35 of 361

1.2 Intended Audience

development and maintenance.

1.3 Application Scope

 This guidance is applicable for the following NE versions.

SingleRAN versions eRAN versions

Huawei Proprietary and Confidential Page 36 of 361

 This guidance is applicable for SOP R11.1.4 version.

 This guidance doesn’t contain the rules in the “Safety Check”.

 Pay attention to the red part.

2.1.2 Revision compared with R11.0.1

Parameter No. Name of Evaluation Item Description

Clock When the Clock Working Mode Parameter

New Is Set to AUTO in a Base Station

in FDD eNodeBs Due to Subscription to the

PERIOD_CELL_L2_MR Message for Cell-Level

External CHR Tracing

MML Command Execution Failures After an

eNodeB Reset or Configuration Reactivation in

Massive X2 Links Scenarios

Faulty Primary IPsec Tunnel

after Synchronizing SON Logs of FDD eNodeBs

Huawei Proprietary and Confidential Page 37 of 361

Notice on Precaution for LTE FDD eNodeBs – parts of support

need manual check.

Notice on Precaution for LTE FDD eNodeBs – parts of support

need manual check.

Huawei Proprietary and Confidential Page 38 of 361

Huawei Proprietary and Confidential Page 39 of 361

3.1 Network Health Indicator

Check Item Type Sub Item Item Name

1.3.2 Rules Description

1) Output health evaluation score in the entire network.

Network Health Evaluation

State Check Equipment Running State 6.67 Please Solve It Immediately 　