WiMAX Network Performance Management Activities V1.0

WiMAX Network Performance Management Activities V1.
INTERNAL
Contents
1 About This Document...................................................................6
1.1 Purposes..................................................................................................................................................................6 1.2 Intended Audience..................................................................................................................................................6 1.3 Content Organization..............................................................................................................................................6 1.4 Authors....................................................................................................................................................................7
2 Basic Concepts Related to Network Performance Management.......8

2.1 About This Chapter.................................................................................................................................................8 2.2 Basic Rules on WiMAX Network Performance Management...............................................................................8 2.3 Basic Contents of Network Performance Management........................................................................................10 2.4 Introduction to Network Performance Management Suite...................................................................................12 2.4.1 Tools and Templates.......................................................................................................................................12 2.4.2 Manuals and Guides.......................................................................................................................................13 2.5 Common Tools for Network Performance Management......................................................................................14 2.5.1 OMStar...........................................................................................................................................................14 2.5.2 APUS..............................................................................................................................................................16 2.5.3 WiMAX Automatic Evaluation Tool..............................................................................................................17 2.5.4 MAINEX........................................................................................................................................................18 2.6 Common Performance Data.................................................................................................................................21 2.6.1 Performance Measurement Data.....................................................................................................................21 2.6.2 CHR Data.......................................................................................................................................................25 2.6.3 Single User Signaling Tracing........................................................................................................................27 2.6.4 User Information Trace...................................................................................................................................29 2.6.5 CIT..................................................................................................................................................................32
3 Daily Performance Monitoring.....................................................35

3.1 About This Chapter...............................................................................................................................................35 3.2 Common KPIs......................................................................................................................................................36 3.2.1 Accessibility KPIs...........................................................................................................................................36 3.2.2 Retainability KPIs...........................................................................................................................................38 3.2.3 Mobility KPI...................................................................................................................................................39 3.2.4 User Experience KPI......................................................................................................................................40 3.2.5 Link Quality (Coding Efficiency) KPIs..........................................................................................................40 3.2.6 Link Quality (Coverage Evaluation) KPIs.....................................................................................................42
2013-7-9
Huawei Technologies Proprietary
Page 1 of 202
WiMAX Network Performance Management Activities V1.0
INTERNAL
3.2.7 Load Capacity KPIs........................................................................................................................................43 3.3 Generating Daily Performance Reports................................................................................................................44 3.3.1 Defining a Performance Measurement Template...........................................................................................44 3.3.2 Generating a Daily Report..............................................................................................................................44 3.3.3 Analyzing the Daily Report............................................................................................................................48 3.3.4 Common Problem Related to Daily Report Generation.................................................................................49 3.4 Generating a Performance Report........................................................................................................................50 3.5 Performance Alarm...............................................................................................................................................51 3.5.1 Purposes..........................................................................................................................................................51 3.5.2 Definition Modes of Performance Alarm.......................................................................................................51 3.5.3 Recommended Performance Alarms..............................................................................................................56 3.5.4 Querying Custom Alarms...............................................................................................................................56 3.5.5 Failure to Report Custom Alarms...................................................................................................................57 3.6 Unsolicited Customer Care...................................................................................................................................58 3.6.1 Users with Poor CINR....................................................................................................................................58 3.6.2 Users with Low Traffic Rate and Poor CINR.................................................................................................60 3.6.3 Users Occupying Many Resources.................................................................................................................60 3.6.4 High Traffic Users..........................................................................................................................................61
4 Routine Check on Network Performance......................................62

4.1 About This Chapter...............................................................................................................................................62 4.2 Parameter Check...................................................................................................................................................63 4.2.1 Prerequisites....................................................................................................................................................63 4.2.2 Parameter Check Procedure............................................................................................................................63 4.2.3 Parameter Check Period.................................................................................................................................67 4.2.4 Parameter Modification Process.....................................................................................................................67 4.2.5 Key Parameters...............................................................................................................................................68 4.2.6 Reference Documents.....................................................................................................................................71 4.3 Interference Check................................................................................................................................................72 4.3.1 TDD Interference Optimization......................................................................................................................72 4.3.2 External Interference Optimization................................................................................................................78 4.4 Service Experience Test........................................................................................................................................83 4.4.1 Rules for Selecting Test Sites.........................................................................................................................84 4.4.2 Test Operations...............................................................................................................................................85 4.4.3 Test Report Output and Tracing......................................................................................................................86
5 Accessibility Optimization...........................................................87
5.1 About This Chapter...............................................................................................................................................87 5.2 WiMAX Access Process.......................................................................................................................................88 5.2.1 WiMAX Network Entry Process....................................................................................................................88 5.2.2 Normal Network Entry Signaling Printed on M2000.....................................................................................89 5.3 Measurement Counters Related to WiMAX Access.............................................................................................91 5.3.1 Radio Access Success Ratio...........................................................................................................................91
2013-7-9
Page 2 of 202
INTERNAL
5.3.2 Initial Network Entry Radio Access Success Rate.........................................................................................94 5.3.3 Basic Capabilities Negotiation Success Rate.................................................................................................94 5.3.4 EAP Authentication Success Rate..................................................................................................................95 5.3.5 DSA Success Rate..........................................................................................................................................96 5.4 Further Analysis on Accessibility Counters..........................................................................................................97 5.4.1 Factors Affecting Accessibility Counters.......................................................................................................97 5.4.2 Major Features Improving Accessibility Counters.........................................................................................98 5.5 General Ideas of Access Success Rate Optimization..........................................................................................104 5.5.1 Access Success Rate Optimization Process..................................................................................................104 5.5.2 Entire Network Problem Analysis................................................................................................................105 5.5.3 Optimization of Top N Carriers....................................................................................................................107 5.6 Common Causes of Low Access Success Rate and Analysis Methods..............................................................107 5.6.1 Analysis........................................................................................................................................................107 5.6.2 Low Radio Access Success Rate..................................................................................................................109 5.6.3 Low Capability Negotiation Success Rate....................................................................................................111 5.6.4 Low Initial Authentication Success Rate......................................................................................................112 5.6.5 Other Failures in the Network Entry Procedure...........................................................................................113 5.7 Advanced Analysis Methods...............................................................................................................................113 5.7.1 Analysis of Network Entry Error Codes.......................................................................................................113 5.7.2 Analysis of Top N Users...............................................................................................................................115 5.7.3 Analysis of User Signal Quality....................................................................................................................117 5.8 Difficult Fault Handling.....................................................................................................................................120 5.8.1 Overview......................................................................................................................................................120 5.8.2 Method for Collecting Network Access Data from the DSP........................................................................120 5.8.3 Logs at the MS Side......................................................................................................................................121 5.9 Appendix.............................................................................................................................................................122 5.9.1 Cases.............................................................................................................................................................122 5.9.2 Reference Documents...................................................................................................................................124
6 Retainability Optimization.........................................................125
6.1 About This Chapter.............................................................................................................................................125 6.2 Retainability Evaluation Counters......................................................................................................................125 6.2.1 Network Disconnection Ratio......................................................................................................................125 6.2.2 Online Duration per Drop.............................................................................................................................126 6.2.3 Average Retain Duration of No Abnormal Interrupt....................................................................................126 6.3 Further Analysis on Retainability Counters........................................................................................................127 6.3.1 Influences of WiMAX User Behaviors on Retainability Counters..............................................................127 6.3.2 Features and Parameters Affecting Retainability Counters..........................................................................128 6.4 Common Fault Handling....................................................................................................................................133 6.4.1 Fault Locating Process..................................................................................................................................133 6.4.2 Cause Analysis..............................................................................................................................................137 6.5 Advanced Analysis Methods..............................................................................................................................140
2013-7-9
Page 3 of 202
INTERNAL
6.5.1 Analysis Tools...............................................................................................................................................140 6.5.2 Analyzing Network Drop Cause Values.......................................................................................................146 6.6 Difficult Fault Handling.....................................................................................................................................149 6.6.1 Exceptional User Trace.................................................................................................................................149 6.6.2 Onsite Test....................................................................................................................................................149 6.7 Appendix.............................................................................................................................................................150 6.7.1 Cases.............................................................................................................................................................150 6.7.2 Reference Document....................................................................................................................................152
7 Traffic Rate and Capacity Optimization......................................153

7.1 About This Chapter.............................................................................................................................................153 7.2 KPIs Related to Traffic Rate and Capacity.........................................................................................................153 7.2.1 Major Factors Affecting Capacity................................................................................................................153 7.2.2 KPIs Related to Traffic Rate and Capacity...................................................................................................155 7.2.3 KPIs Related to Coding Efficiency and Coverage.......................................................................................160 7.2.4 Capacity Expansion and Exception Thresholds...........................................................................................163 7.3 KPIs....................................................................................................................................................................164 7.3.1 Factors Affecting the KPIs............................................................................................................................164 7.3.2 Features and Parameters Affecting Traffic Rate and Capacity Counters......................................................165 7.3.3 Traffic Rate Measurement............................................................................................................................168 7.4 Common Performance Problem Analysis...........................................................................................................168 7.4.1 Analysis Overview........................................................................................................................................168 7.4.2 Analysis of DL User Experience..................................................................................................................172 7.4.3 Analysis of DL Coding Efficiency and Coverage.........................................................................................174 7.4.4 Analysis of DL Retransmission Rate............................................................................................................177 7.4.5 Analysis of UL User Experience..................................................................................................................178 7.4.6 Analysis of UL Coding Efficiency................................................................................................................180 7.4.7 Analysis of UL Retransmission Rate............................................................................................................183 7.4.8 Transmission Verification.............................................................................................................................185 7.5 Advanced Analysis Methods..............................................................................................................................185 7.5.1 Overview of Data Sources and Tools...........................................................................................................185 7.5.2 Traffic Rate Analysis....................................................................................................................................188 7.5.3 Abnormal User Handling..............................................................................................................................189 7.6 Difficult Fault Handling.....................................................................................................................................190 7.7 Appendix.............................................................................................................................................................190 7.7.1 Cases.............................................................................................................................................................190 7.7.2 Reference Documents...................................................................................................................................192
8 Capacity Management..............................................................193
8.1 About This Chapter.............................................................................................................................................193 8.2 Criteria for Capacity Expansion Based on Air Resource....................................................................................193 8.2.1 Capacity Expansion Criteria for V300R002C03..........................................................................................193 8.2.2 Capacity Expansion Parameter Optimization...............................................................................................195
2013-7-9
Page 4 of 202
INTERNAL
8.3 Air Interface Capacity Expansion Methods........................................................................................................196 8.3.1 Modifying the Networking Mode.................................................................................................................196 8.3.2 Adding Sites..................................................................................................................................................196 8.3.3 Using Multi-Carrier......................................................................................................................................196
9 Checklist on Basic Activities of Network Performance Management ................................................................................................... 200
2013-7-9
Page 5 of 202
INTERNAL
1
1.1 Purposes

About This Document
This manual describes the basic rules, methods, activities, and skills related to WiMAX network performance management. It guides field network planning and optimization engineers and project performance support personnel of Huawei HQ to complete performance optimization. This manual is applicable to the following scenarios: Onsite routine performance maintenance Network performance optimization Customer complaint handling
As a part of the WiMAX network performance management suite, this manual should be used with corresponding suite parts.
1.2 Intended Audience

This manual is intended for:

Network planning and optimization engineers Project performance support personnel of Huawei HQ
1.3 Content Organization

This manual contains 10 chapters. The contents are organized as follows:

About This Document Basic concepts related to network performance management (including basic rules, data, tools, templates, and guides) Routine network performance monitoring (daily report, weekly report, performance alarm, and user monitoring) Routine check on network performance (parameters, interferences, and active tests on service experience) Basic concepts and common fault handling related to network optimization
2013-7-9
Page 6 of 202
INTERNAL
(accessibility, retainability, traffic rate, and capacity)

Capacity management (capacity expansion standards and guides) Checklist on basic activities of network performance management
1.4 Authors
This manual is jointly written by WiMAX performance and research experts and NTS network planning and optimization experts. Chen Yayong is the general owner. The following table lists the authors of each chapter. Chapter Chapter 2Basic Concepts Related to Network Performance Management Chapter 3Daily Performance Monitoring Chapter 3Daily Performance Monitoring Chapter 3Daily Performance Monitoring Chapter 5Accessibility Optimization Chapter 6Retainability Optimization Chapter 8Capacity Management Chapter 8Capacity Management Author Chen Yayong He Shanshan, Zou Qing Yin Jiangping, Gu Wenxiang, Li Hongjing, Pu Song, Xu Nan Zou Qing, Xu Qiong Xie Shisheng, Li Hongjing Xu Nan Liu Tao Chen Yayong
2013-7-9
Page 7 of 202
INTERNAL
Basic Concepts Related to
Network Performance Management

2.1 About This Chapter
This chapter describes the basic rules and contents of network performance management, common performance data and tools, and contents of the WiMAX performance management suite.
2.2 Basic Rules on WiMAX Network Performance Management

Rule 1: The WiMAX network management means a series of basic activities that are effectively carried out on site. Someone thinks that network performance management is complex, involves mainly parameter adjustment, and relates to features, but they ignore the importance of onsite operations in the performance management process. Our experience tells us that onsite operations are critical to the performance of a network. Most network performance problems are caused by ineffective execution of basic activities. This manual is intended to describe how to effectively carry out the basic activities on site. For this purpose, this manual focuses on what activities can be carried out by field engineers and how to carry out these activities. Certainly, the performance of versions is the basis of excellent performance of the network. This task should be ensured by R&D engineers and is not the focus of this manual. Rule 2: The performance level of a network is determined by the network architecture (distance between sites + number of frequency channels). The continuous coverage in a cluster or whole network is recommended for network construction. The performance of a network is determined at its design stage. It has been found that a good network construction mode should ensure the proper distance between sites and the cluster fragmentation coverage, whereas the hot spot discrete coverage has great impacts on the growth of users and the subsequent network optimization and adjustment. Frequency channels determine the interference level of a network. When there are sufficient frequency channels, the loose frequency reuse mode with over three frequency channels is recommended.
2013-7-9
Page 8 of 202
INTERNAL
Rule 3: Network optimization should start immediately after one BS is deployed, instead of waiting until cluster optimization, especially when a new site is added in an existing area. For various reasons, many WiMAX networks are not optimized or cluster optimization is performed long after BSs provide services. The single-site verification is usually used to ensure the success of KPI acceptance but does not accomplish the functions of single-site acceptance. In the scenario of adding sites to existing areas, one BS is put into commercial use without any optimization. In this case, the new site does not function and even brings about negative impacts. Rule 4: Over-commitment on KPIs should be avoided through customer expected value management. Make KPI commitments with risks under control based on the actual situation of the network and the baseline capabilities of the products. When the value demanded by customers exceeds the baseline, report it to relevant departments at Huawei HQ for approval and file it according to the KPI commitment regulations. For details, see the WiMAX Network KPI Baseline V3.0.xls. Rule 5: MSs comply with Huawei MS feature specifications. Any MSs accessing the network must be strictly controlled. New MSs should pass Huawei IOT authentication. Additionally, MSs should support smooth upgrade, which is particularly important for WiMAX. You can understand the performance difference between MSs from the following aspects:
We suggest operators to use MSs that pass Huawei certification to support the key performance provided by Huawei systems and obtain optimal performance of the network. This does not mean Huawei uses only these MSs. In principle, Huawei systems are compatible with all MSs that comply with WiMAX protocol standards. There is an exception, that is, some MSs do not provide the supporting capability though they are claimed to support the feature. These MSs cannot be compatible with the system.
The WiMAX industry chain is under development, and protocol standards are to be improved. Therefore, WiMAX MSs should also support remote smooth upgrade. Rule 6: The network performance involves the whole system. High-quality engineering installation and normal operating of devices (including transmission devices) are the bases for excellent performance of a network. Therefore, the performance management team must closely cooperate with the engineering installation team and device maintenance team. This rule emphasizes the following two points:
Network performance involves the whole system, and each aspect is very important. Therefore, do not focus on only network planning optimization, performance features, and parameters. The problems of each aspect will finally come out as performance problems. Ensure information sharing and close cooperation in each aspect, for example, hold weekly routine meetings.
Rule 7: The correctness and stability of parameter configuration must be ensured for new BSs, BSs already in commercial use, and version upgrade. Many network performance problems are eventually found out as man-made parameter configuration problems, for example, some features are not enabled or parameters are not
2013-7-9
Page 9 of 202
INTERNAL
inherited after upgrade. One basic task of onsite performance work is to manage onsite parameter configurations:
The project parameter management cannot be remotely performed by R&D or technical support engineers at Huawei HQ. The owner of this task should be the field network planning and optimization team. R&D or technical support engineers should provide service guidance and support. Onsite parameter work does not aim to obtain the optimal network parameters through optimization, but to maintain the stability of parameters under the relatively suitable configuration so that the actual configuration of the network is consistent with that expected. The expected configuration may not be the optimal configuration.
For details on how to perform parameter management on site, see section 4.2"Parameter Check." Rule 8: Handle complaints of end users with great care because complaints mean users still want to accept our services and give us the last chance. In many projects, user complaints cannot be effectively closed due to different factors such as the large number of complaints or incomplete information. User complaint is a good way to show real user perception. Therefore, handle the complaints with great care:
Record and keep tracking of complaint handling and ensure the closing of complaints, especially those from VIP users. The core of complaint handling is not to solve the individual problems of users but to summarize the common problems from individual problems and solve them.
Rule 9: Discover interferences as early as possible, and urge relevant personnel to clear the discovered external interferences. Interferences commonly exist in the WiMAX network. Interferences should be discovered as early as possible in view of the influence and locating difficulty. Rule 10: Each problem must be tracked and solved; otherwise, small problems may cause big problems. The difficulty in onsite performance management work lies in the timely settlement of small problems. In the case of problem handling, record the problems and then trace them.
2.3 Basic Contents of Network Performance Management

The following table lists the basic activities for onsite routine performance management in combination with the capabilities of WiMAX systems.
2013-7-9
Page 10 of 202
INTERNAL
SN
Basic Activity
Executio n Frequenc y Weekly
Description
*1-1
Weekly routine maintenance meeting Daily monitoring report Weekly monitoring report Performance alarm Active user care
The network planning team and device maintenance team hold a routine meeting every week to share information, determine owners, and close problems. Use a template to generate a daily report to find out performance exceptions of the network, handle common problems, feed back difficult problems, and trace problem handling. Use a template to generate a weekly report to summarize the performance problem handling progress of the week and identify top problems. Define alarms triggered at performance faults through combined conditions to discover performance problems in time. Actively give early warning to high-risk users. The high-risk users include:
*1-2
Weekly/daily (if conditions permit) Monthly
*1-3
*1-4
Immediately
*1-5
Weekly
Users at low traffic rate and in poor wireless environment Users under suddenly poor coverage Users with a large data amount
*1-6
Parameter management and verification
Monthly
The parameters of sites already in commercial use should be stable. The parameters should be inherited after site upgrade. The parameters of new sites should be correct. Set up the baseline on site for parameter configuration of the project, periodically verify the existing network configuration, and correct the inconsistent configuration items. Analyze the faulty carriers and determine the interference types according to the network interference status monitored through daily reports. Select BSs according to certain rules for service experience tests. Check the contents of capacity expansion and compare the performance before and after capacity expansion.
*1-7
Interference check
Monthly
*1-8
Active test on service experience Capacity expansion of sites
Weekly
*1-9
Trigger
2013-7-9
Page 11 of 202
INTERNAL
SN
Basic Activity
Executio n Frequenc y Trigger
Description
*1-10
Return visit to users
Huawei engineers can carry out demo return visits at the early stage of network construction to sum up the common problems, and then fix down return visit as a routine task. Pay a return visit to users if user complaints cannot be solved remotely. Optimize the accessibility according to daily reports, and master the method of collecting data for handling difficult problems. Optimize the retainability according to daily reports, and master the method of collecting data for handling difficulties. Optimize the traffic rate and capacity according to daily reports, and master the method of collecting data for handling difficult problems.
*1-11
Basic optimization on accessibility Basic optimization on retainability Basic performance optimization on traffic rate and capacity User complaint handling
Trigger
*1-12
Trigger
*1-13
Trigger
*1-14
Trigger
Collect user complaints according to the template, trace the complaint problems, and ensure the closing of the problems.
2.4 Introduction to Network Performance Management Suite

2.4.1 Tools and Templates
Application Scenario Daily report analysis Performance measurement collection Weekly report analysis CHR analysis Initial network planning and network planning at capacity expansion stage Name WiMAX V32C03 Daily Report Template V2.0_2010-6-28.rar WiMAX V32C03 Daily Report Template_20106-21.xls WiMAX V32C03 Weekly Report Template V2.0_2010-6-21.rar OMStar Tool APUS Tool
2013-7-9
Page 12 of 202
INTERNAL
Application Scenario Risk evaluation of network planning Inspection, log analysis, data collection Routine check interference analysis Daily monitoring Daily report problem tracing Parameter modification Interference check Complaint handling Complaint handling
Name WiMAX Automatic Evaluation Tool MAINEX Tool (HCT, AAT, CT) C03 Spectrum Analyzor Active Customer Care Template.xls Philippines network performance issue tracking form20100512.xls Commercial network operations application.doc XX Project Interference Optimization Archive XXXX WiMAX Site Complaint Handling Template.xls XXXX WiMAX Site Complaint Information Collection Template.xls
2.4.2 Manuals and Guides

SN 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Name OMStar WiMAX Installation Guide OMSTAR-WiMAX User Manual WiMAX APUS 1.7.3 Operation Guide 20100506.doc WiMAX Automatic Evaluation Tool User Guide.doc CHR Configuration and Manual Collection Methods.doc How to Use the Third-Party Server to Collect CHR Data.doc OMATAR-Wi User Guide WiMAX Spectrum Analyzer User Guide V32C03.doc WiMAX Accessibility KPI Baseline Guide.doc WiMAX Retainability KPI Baseline Guide.doc DBS3900 V300R002C03 ARQ&HARQ Principles and Application Guide.doc DBS3900_V300R002C03 Guide to Principles and Applications for IRCMRC Adaptive Switchover.doc DBS3900 V300R002C03 Admission and Load Control Feature Principles and Application Guide.doc DBS3900 V300R002C03 Power Control and AMC Feature Principles and Application Guide.doc BS3900 V300R002C03 Multi-Antenna Feature Principle and Application Guide.doc
2013-7-9
Page 13 of 202
INTERNAL
16
DBS3900 V300R002C03 Access Feature Principles and Application Guide.doc
2.5 Common Tools for Network Performance Management

2.5.1 OMStar
Functions
OMStar is a CHR analysis tool. By processing CHR data, the OMStar can analyze user information according to a certain format. CHRs are classified into the network entry, network exit, handoff CHRs of source BS and target BS, and periodic CHRs. The OMStar can be used to analyze related data and further analyze the designated users according to specific MAC addresses. The OMStar uses the client/server structure and consists of the database, server, and clients.
1.
Database: stores data. The OMStar supports two kinds of databases, namely, free MSDE2000 and paid Microsoft SQL Server 2000. The MSDE2000 is a light desktop SQL Server database that can manage up to 2 GB data. Microsoft SQL Server 2000 provides more powerful data management capabilities but it must be purchased. Do not use SQL Server 2007 because it has many different features from SQL Server 2000. The OMStar supports SQL Server 2000 personal, professional, and enterprise editions. The SP4 patch should be installed.
2.
Server: The Transdata is the server program of the OMStar. It provides multiple functions such as project management, data import and deletion, and client access. A server supports concurrent connection of multiple clients.
2013-7-9
Page 14 of 202
INTERNAL
3.
Client: The OMStar serves as a client. The client connects to the database through the server to query data, process data, or export original data to an Excel file that can be identified. The client does not store any data but obtains data from the server and the database. Therefore, the client must connect to the OMStar server on the local PC or network. Though the OMStar does not restrict the connected clients, the number of clients querying data at the same time should not exceed 10 to ensure the concurrent query efficiency.
Usage Instructions
For the installation environment and system requirements of the OMStar, see the OMStar WiMAX Installation Guide on the support website (http://support.huawei.com). You do not need to enable the CHR in the whole network. Enable the CHR on only the BSs from which CHRs are collected. There is no requirement on disk space of the M2000 because CHRs are stored in BSs. The maximum size of CHRs saved in a BS is 10 MB. If the maximum size is exceeded, the earliest CHRs are overwritten. Therefore, you only need to run MML commands to enable the CHR on corresponding BSs without extra operations or software and hardware requirements. If the performance analysis platform (OMStar + server) is established, CHRs are periodically stored to the disk of the server through the M2000. The CHR data is detailed, thus occupying large disk space. After numbers are allocated on scale, the CHR data of five to seven days of 600 sites occupies about 60 GB disk space. The total disk space required exceeds 70 GB if the reserved import buffer and processing space are counted in. Therefore, process the CHR data in time when the disk space is limited:

Delete old data. Back up the database periodically. Export original data to Excel files, and then delete the old data.
For details on how to import, export, and delete the data, see the OMSTAR-WiMAX User Manual on the technical website (http://support.huawei.com).
Acquisition Modes
To obtain the installation programs, relevant documents and manuals of the OMStar and the MSDE2000, visit the support website (http://support.huawei.com), and then choose Software > Version Software > Wireless Product Line > WiMAX > WiMAX Tools > OMSTARWi.
2013-7-9
Page 15 of 202
INTERNAL
The OMStar requires a license. After the OMStar is installed successfully, choose Help > Show ESN Code to obtain the ESN, report the ESN, and apply for the license from after-sales network planning engineers.
2.5.2 APUS
Functions
The latest version of the WiMAX APUS tool is 1.7.3. This version is specific to the WiMAX network and integrated with the relatively independent functions of automatically planning the WiMAX frequency channels, preamble index, and neighboring cells. The functions of the WiMAX APUS tool are as follows: 1. Frequency planning The frequency planning is performed by the Frequency Plan module. After engineering parameters are imported, the frequency planning schemes can be implemented in the multi-frequency, single-frequency FFR, multi-frequency FFR, and FDD pre-planning scenarios. The multi-carrier scenario is not supported temporarily. Only the frequency planning results are displayed. In the FFR network, frequency planning and segment planning results are displayed, and a maximum of 18 frequency channels and six sectors are supported. The planning results can be directly exported to an EXCEL or KML file. 2. Preamble planning The preamble planning is performed by the Preamble Plan module. After engineering
2013-7-9
Page 16 of 202
INTERNAL
parameters are imported, the Preamble, ULPermbase, DLPermbase, and CDMAStart planning can be implemented in the single-frequency FFR, multi-frequency FFR, and multi-frequency PUSC with all SC networks. The preamble planning involves the segment and IDCELL influences. The preamble reuse planning also involves minimization of the segment and IDCELL interference. The planning results can be directly exported to an EXCEL or KML file. 3. Neighboring cell planning The neighboring cell planning is performed by the Neighbour Plan module. After engineering parameters are imported, the automatic planning of WiMAX neighboring cells can be implemented. With the forced preventive measure in the neighboring cell planning, the two cells with the same frequency and preamble cannot be neighboring cells of another cell at the same time.
Application Scenarios
The APUS tool is mainly used for initial planning of the WiMAX network and network planning at the mixed capacity expansion stage.
Usage Instructions
The APUS tool uses a unified engineering parameter table and is easy to operate. For details, see the WiMAX APUS 1.7.3 Operation Manual 20100506.doc.
Acquisition Modes
The latest version of the tool and relevant documents are released to WiMAX after-sales network planning personnel. You can obtain the latest version from after-sales network planning personnel. You can also obtain the latest version from the after-sales network planning server. The contact person is Jiang Bo (ID: 46652).
2.5.3 WiMAX Automatic Evaluation Tool

Functions
The WiMAX automatic evaluation tool is used for automatic evaluation of WiMAX network planning. This tool is integrated with functions such as WiMAX frequency planning evaluation, preamble planning evaluation, neighboring cell planning evaluation, paging group evaluation, and site distance statistics. The functional modules of the tool are independent of each other. The functions of the WiMAX APUS tool are as follows: 1. Frequency planning evaluation The tool supports two frequency planning evaluation modes, namely, engineering parameter-based evaluation and CHR-based evaluation. The engineering parameterbased evaluation is to find out the unreasonably planned cells at the engineering planning stage. This kind of evaluation supports the PUSC with all SC network, PUSC 1/3 network, and FFR network. The CHR-based evaluation is to find out the cells suffering severe shared-channel interference, and determine whether to review these cells (whether the frequency setting matches the engineering parameters and whether to re-plan these cells). 2. Preamble planning evaluation The preamble planning evaluation involves three evaluation modules: Preamble planning evaluation module: used to set the maximum number of measured layers and maximum valid distance, and measure the cells with the same frequency
2013-7-9
Page 17 of 202
INTERNAL
and preamble within the maximum number of measured layers and the valid distance, thus finding out the improperly planned cells. Preamble reuse statistics module: used to measure the number of use times of each cell with the same frequency and preamble. Nearest co-frequency cell statistics module: used to find out the nearest cell with the same frequency and preamble corresponding to each cell. 3. Neighboring cell planning The neighboring cell planning supports two evaluation modes, namely, engineering parameter-based evaluation and CHR-based evaluation. The engineering parameter-based evaluation is to find out the cells without the engineering parameter table, unidirectional neighboring cells, neighboring cells exceeding the maximum valid distance, and cells with more neighboring cells than specified. The CHR-based evaluation is to find out the cells where the available neighbor relationship is not configured and the neighboring cells without handovers for a long time. 4. Paging group evaluation The paging group evaluation is to check whether the paging capability of the gateway has reached or will soon reach the upper limit according to the performance measurement data, thus preparing for early warning. 5. Site distance evaluation The site distance evaluation is to measure the distance between sites, thus obtaining information about the network coverage.
This tool is used for risk evaluation related to the WiMAX network planning.
Usage Instructions
This tool is easy to use and can be used to evaluate the network planning risks quickly and effectively. For details, see the WiMAX Automatic Evaluation Tool User Guide.doc.
Acquisition Modes
The latest version of the tool is released to WiMAX after-sales network planning personnel. You can obtain the latest version from after-sales network planning personnel.
2.5.4 MAINEX
Functions
The MAINEX consists of the HCT, AAT, and CT tools. 1. HCT: Based on the CDMA MAINEX tool, the health check tool (HCT) inherits the highly automatic feature and multiple inspection modes of the original CDMA tool, adds the health check items for WiMAX devices, and also adds the function for upgrading the health knowledge library to deal with the longer development period of the tool. Add sites and check the health status of devices.
2013-7-9
Page 18 of 202
INTERNAL
Set the scheduled, hourly, daily, monthly, and yearly inspection tasks and automatically send inspection results. Upgrade office versions, check the configuration correctness, and check the typical configuration in offline mode. Trace and detect signal interference on the whole network, and perform RTWP measurement and analysis. Monitor network vulnerabilities and version technical problems, and check technical notification update in time. 2. AAT: The auxiliary analysis tool (AAT) is used for WiMAX device troubleshooting and analysis. This tool can be used to analyze and measure the run logs, alarm logs, and black box logs of WiMAX devices, helping engineers to locate device problems. The logs that can be analyzed by the AAT include call logs, operation logs, security logs, exception logs, and run logs. The alarms that can be analyzed by the AAT include history alarms and active alarms. The black box information that can be analyzed by the AAT includes last word and memory information. The AAT can also analyze RTWP logs. Call drop and network drop analysis, call failure cause analysis User coverage analysis: Analyze call logs to find out the users with poorest signals, and trace the user performance from multiple dimensions. User operation tracing: Analyze operation logs to measure the history operations, improper mining operations, and dangerous operations of users. BS running status tracing: Analyze run logs, security logs, and exception logs to trace the module running states of BSs. Information resetting: Trace last word and memory information to find out the real causes of BS reset. Alarm statistics and location: Measure and analyze active alarms and history alarms. 3. CT: The customization tool (CT) consists of the script collection tool and script preparation tool, and provides the script settings and RTWP data for logs, alarms, performance files, configuration files, black box files, and MML packets.
Usage Instructions
For details on the HCT, see the online help.
2013-7-9
Page 19 of 202
INTERNAL
For details on the AAT, see the online help.
For details on the CT, see the online help.
Acquisition Modes
You can obtain the MAINEX and related documents from the technical support website: http://support.huawei.com/support/pages/editionctrl/catalog/ShowVersionDetail.do? actionFlag=getDetail&node=000001474303&colID=ROOTENWEB|CO0000000174
2013-7-9
Page 20 of 202
INTERNAL
The HCT and the ATT are restricted by license. The user without a license is not authorized to analyze data. After the tool is installed, you can apply for a license as follows: choose Help > Display Equipment SN(D), obtain the ESN, and then return it to after-sales networking planning engineers to obtain the license.
2.6 Common Performance Data

2.6.1 Performance Measurement Data
Functions
Performance measurement is to measure carrier-level data. It periodically records the system data based on carriers for analysis and problem troubleshooting. Performance measurement is a mere data recording operation on the background. So long as relevant counters are
2013-7-9
Page 21 of 202
INTERNAL
subscribed to on the M2000, the BS automatically performs measurement and reporting. Even though the carriers are deactivated, the BS automatically restarts data recording when the carriers are reactivated. Performance measurement covers various aspects of the network, including the procedures (network entry, network exit, handover, and idle), capacity, rate, and interference evaluations. The V3R2C03 version already has more than 800 counters.
The performance measurement data collection and summarization are as follows: Each module of the BS automatically collects background data, and the performance measurement module summarizes the data. When the measurement period is reached, the M2000 delivers a collection instruction to the BS to obtain the performance measurement data of this period and save the data. Therefore, after the measurement period is reached, the performance measurement data is saved on the M2000 server. The history data query is not affected by version upgrade, reset, or failure of the BS. Under the current version (V3R2C03), the minimal performance measurement period is 30 minutes by default. The performance measurement period for Australia is specially customized to 15 minutes.
The performance measurement data is the data input from network analysis and preliminary problem isolation analysis. The common application scenarios are as follows:
Input data of daily monitoring The performance measurement data already includes all procedures and features of the network. Through the performance measurement data analysis, you can obtain the general running status of the network and use the performance measurement counters as KPIs to measure the network performance. As the input of the WiMAX V32C03 Daily Report Template V2.0, the performance measurement data can be displayed on daily reports to present the overall status of the network through certain calculation formulas. Through the result change trends, the network performance changes can be reflected, and thus the network health status can be
2013-7-9
Page 22 of 202
INTERNAL
monitored.
Problem isolation and troubleshooting. Performance measurement covers the whole network. Therefore, you can perform network analysis as a whole, and then use the performance measurement for problem isolation after problems are discovered and further located, thus finding the problem causes among the numerous data. For example, if you find that the network drop rate is low in certain sectors, check the relevant counters in network exit performance measurement to determine whether the problem is caused by more network exits or few sector users. If the number of network drop times is large and far beyond the average number of network drop times of the sectors with the same number of users, check the specific cause value. According to the following formula in the performance counter reference: Times of MS Disconnection from Network = Times of Deregistration due to Air Link Failure + Times of Deregistration due to Transmission Fault + Times of Deregistration due to Handover Failure + Times of Deregistration due to Other Causes + Re Auth Failure Times. Check the specific cause items in the performance measurement data to find out the highly possible failures and thus locate the specific cause through further analysis.
Usage Instructions
The performance measurement collection is performed through the M2000. The specific collection method is as follows: 1. 2. 3. On the main interface of the M2000, choose Performance > Query Result. Click NEW QUERY, and then select the query time range, counters, and sectors. For usual queries, you can save the query task as a template.
2013-7-9
Page 23 of 202
INTERNAL
4.
The query results can be saved as an Excel file. For the performance measurement collection, the most common problem is that the data collection fails or the data of certain time segments is lost. For common problem handling, see the following table.
Symptom (Determination Basis) The corresponding counter is not selected in Performance > Measure Management > Measurement Settings. The query time is too close to the current time.
Possible Cause
Action
The counter is not subscribed to.
Subscribe to the relevant counter.
The results of the previous measurement period can be output only after being summarized within several minutes. The M2000 supports collection of the counters of multiple measurement sets at a time. If certain counters are not subscribed to, however, all the collection results may be null.
Collect the data again 10 minutes later.
The counters collected at a time contain the contents of multiple measurement sets.
Check whether all the counters collected are subscribed to. Collect the counters by measurement set and check whether any data is collected.
2013-7-9
Page 24 of 202
INTERNAL
Symptom (Determination Basis) The data cannot be collected in busy hours.
Possible Cause
Action
There are more than 9 x 9, but the result bit length of the database is not expanded. The number of results is very large.
Obtain the database bit length check script from Huawei HQ, and run the script. Report relevant problems to Huawei HQ so that the problems can be solved in later versions.
There are 9 x 9 data results.
In the case of data loss or exceptions except those in the preceding table, ask relevant engineers at Huawei HQ to locate the problems.
2.6.2 CHR Data

Functions
CHRs are classified into event-triggered CHRs and periodically-triggered CHRs. The eventtriggered CHRs include network entry CHRs, network exit CHRs, source-BS CHRs, and target-BS CHRs. The periodically-triggered CHRs include mainly periodic CHRs. An event-triggered CHR is generated to record the operation time and operation of the user through fields when a user triggers a certain operation such as network entry, network exit, and handover. The event-triggered CHRs record the operations of all users and can be used to locate problems such as network entry failure, handover failure, and network drop. A periodically-triggered CHR records the data of a certain number of users at the specified time interval to reflect a status or change of the users and monitor the service and signal quality of the users.
CHRs are used to locate problems of the product. By default, the system does not generate CHRs. The system generates CHRs only after the function is enabled. For details, see "Usage Instructions." The application scenarios are as follows:
Network entry failure analysis It is used to locate the network entry failures of MSs. You can find out the cause of network entry failure based on the cause value. Through the failure cause measurement, you can analyze the key MSs and carriers for oriented problem troubleshooting.
Abnormal network exit analysis It is used to locate network drop of MSs. Similar to network entry analysis, you can preliminarily determine the network drop reason based on the cause value. Through summarization and filtering, you can find out the top N carriers and MSs for problem location.
User behavior analysis It is used to analysis the online duration and service duration of users. It objectively shows the traffic rates of users. By analyzing original data, you can obtain distribution of
2013-7-9
Page 25 of 202
INTERNAL
online durations and service durations, distribution of service activation rates, distribution of attachment rates, and analysis of uplink and downlink traffic.
User number growth analysis It is used to analyze the growth of user number. You can find out the users who are offline for a long time based on the recorded information.
Network entry delay analysis It is used to analyze the network access delay of MSs. For each user, you can analyze the delay at each stage. You can also analyze the average delay of each MS to further determine the stage at which the delay is high.
Traffic rate analysis It is used to analyze the traffic rate of MSs. By summarizing original data, you can obtain the distribution of user rates, and analyze the traffic rate of the MS for each user based on improper reporting measurement, signal quality, and coding efficiency.
User complaint analysis Users may not have professional knowledge, and their feedback problems may be ambiguous and broad. Therefore, you need to analyze the specific MSs from all preceding aspects to determine whether problems occur, and then analyze the specific problems.
Usage Instructions
The data of a CHR includes the basic information about NEs, NE configuration, CHR data, and engineering parameters. The CHR data is recorded by the BS. By default, the CHR function is disabled, that is, the CHR data is not recorded. Therefore, if you require CHR data, enable the CHR function first. To query the CHR function, run the command LST CCMCHRSWITCH. To enable the CHR function, run the command MOD CCMCHRSWITCH: CHRNWEFLG=ON, CHREXTNWFLG=ON, CHRSHOFLG=ON, CHRTHOFLG=ON, CHRPRIDFLG=ON; Currently, there are five types of common CHRs, corresponding to five switches. Additionally, there is a CHR customized for customers, namely, UBO CHR. This function should be disabled in normal cases.
Basic information about NEs The basic information about NEs includes the name, IP address, and version of the BS. The file is EAMInfo.xml.
NE configuration NE configuration includes the configuration information about the BS. Each BS has a configuration file, for example, GExport_ALAPAMQ_10.7.206.145_20100318151149.xml.
CHR data CHR data records the call history information about MSs and is saved in the BS. You need to operate on the BS. For details on how to collect the basic information about NEs, NE configuration, and CHR data, see the CHR Configuration and Manual Collection Methods.doc. For details on how to collect data from the third-party server, see the How to Use the Third-Party Server to Collect CHR Data.doc.
Engineering parameters
Huawei Technologies Proprietary Page 26 of 202
2013-7-9
INTERNAL
Engineering parameters are used to display and use the geographical information about the tool, including the basic sectors of the BS, carriers, latitude and longitude, and antenna downtilt. The engineering parameter file is Engineering Parameter Template.xls. This file can be obtained from field network planning engineers. The file must contain the following information. Sector Name Sector ID Site ID Longitude Latitude
The OMStar-WiMAX implements the network entry, network exit, service, and complaint analysis. For details, see the OMSTAR-Wi User Guide.
2.6.3 Single User Signaling Tracing

Functions
Signaling tracing records all the signaling messages of MSs since MSs access the network, including the R1 and R6 interface information. After signaling tracing is started, signaling messages are recorded until the task reaches the end time or is passively stopped. Data collection is performed through the M2000.
Procedure problem troubleshooting (network entry, network exit, handover, sleep, and idle) Single user signaling tracing is simple and easy-to-understand, and very important for locating procedure-related problems. Through procedure analysis, you can find out the specific process in which exceptions occur and preliminarily determine the faulty NEs. For example, if the exceptional procedure is initiated by the BS, you can obtain the specific problems recorded by the module based on the exception information (error cause) in the CHRs.
Monitoring of MS measurement reporting and BS delivery power adjustment After an MS accesses the network and keeps in stable state, if the Report message is used to report the downlink signal measurement result, you can monitor the measured value changes in real time through signaling monitoring. This is useful in the FFR network. The BS delivery power is sent to the MS through the RNG-RSP message. Through signaling tracing, the continuous power changes delivered by the BS can be obtained.
Usage Instructions
Signaling tracing is performed through the M2000. To start the signaling tracing module, choose Monitor > Signaling Trace on the M2000. To collect signaling tracing data, do as follows: 1. Create user signaling tracing. Select the NE where the MS resides, as shown in the following figure.
2013-7-9
Page 27 of 202
INTERNAL
2.
Enter the tracing type (R1 interface signaling, R6 interface signaling, or all signaling). Enter the MAC address of the MS to be traced. Ensure that the MAC address is set correctly; otherwise, messages cannot be traced.
3.
After starting the signaling tracing task, double-click it. The traced messages are displayed. The following figure shows the main interface.
2013-7-9
Page 28 of 202
INTERNAL
2.6.4 User Information Trace

Functions
Single user trace mainly includes user information trace (UIT). UIT displays the measurement items after the MS accesses the network in real time, for example, uplink/downlink signal quality, improper report measurement, and traffic measurement. After tracing is started, user information is recorded until the task reaches the end time or is passively stopped. Data collection is performed through the M2000.
After the MS accesses the network, UIT monitors the counters of the MS and analyzes whether the MS is in normal state. It is usually used to trace the uplink/downlink signal quality, uplink/downlink modulation coding method, outer loop adjustment, and continuous throughput.
Usage Instructions
To collect UIT data, do as follows: 1. To activate the signaling trace collection function, choose Signaling Trace Collection. The main interface is displayed, as shown in the following figure.
2013-7-9
Page 29 of 202
INTERNAL
2.
Double-click Subscriber Information Monitoring , enter the trace name, select the NE, and then set the start time and end time as required.
3.
Enter the MAC address of the MS to be traced, as shown in the following figure. Ensure that the MAC address is set correctly (that is, ensure that the MS resides under the NE selected in the preceding window); otherwise, no message can be traced.
2013-7-9
Page 30 of 202
INTERNAL
4.
After UIT is started, the counter results are displayed in real time (based on the report period), as shown in the following figure.
5.
To stop UIT, right-click the trace task and choose stop from the shortcut menu. After the task is stopped, you can export the saved file to the local computer. To do this, rightclick the trace task and choose export from the shortcut menu, as shown in the following figure.
2013-7-9
Page 31 of 202
INTERNAL
6.
The data can be exported to two file formats. The CSV format is recommended.
2.6.5 CIT
Functions
Carrier information trace (CIT) is also to measure carrier-level data and display carrier data. Different from performance measurement, the CIT supports more detailed time granularity and implements immediate and dynamic display.
Different location functions: Performance measurement is used to evaluate network performance and preliminarily analyze and isolate problems. Therefore, it aims to cover each feature of the product and monitor different aspects. UIT is a flexible and easy location tool that aims to display data quickly and reflect measurement result changes, thus implementing further problem analysis and location. Different time granularities: Due to different location directions, the performance measurement period cannot be too short and is fixedly set to 30 minutes, whereas the CIT display period is short and usually one to 10 seconds to reflect the changes of measurement items in a shorter time. Different function items: performance measurement is to evaluate network status;
2013-7-9
Page 32 of 202
INTERNAL
therefore, it involves many measurement counters (more than 900). The short report time of CIT, however, determines that only the critical and frequently changing measurement items are displayed. Therefore, UIT involves few measurement items and focuses only on the frequently changing counters such as traffic and RTWP. Particularly, UIT contains a great number of intermediate RF counters in consideration of problem location.
Different use modes: Performance measurement data is background data and automatically collected by the M2000 in most cases. Analysis engineers just need to collect and handle the results periodically. UIT data is dynamic GUI data. After the UIT function is enabled, the result changes are traced for problem analysis and location.
CIT provides data for problem analysis. Therefore, it should be used together with performance measurement. After the faulty sectors are located through macro analysis of performance measurement, start CIT for the faulty sectors. After the specific carriers are located, use UIT to observe the carrier data instantly, thus locating the problems. For example, if you find that the retransmission rate of a carrier is high through performance measurement, start CIT and check the HARQ per second, or check the RTWP of the carrier through the medium RF trace item to determine whether interference exists or check the interference changes. In brief, CIT is used to observe the problem details through dynamic update of carrier data for further location after the faulty carriers are discovered by using performance measurement or other methods.
Usage Instructions
To start CIT, do as follows: 1. 2. 3. 4. 5. Choose Monitor > Signaling Trace Collection on the main interface of the M2000. Click carrier Information Monitoring, set the trace name, BS, and start time. To perform continuous trace, you do not need to set the start time. Click Next. Set the IDs of the carriers to be traced and the report time (ranging from 1 to 10 seconds). After the setting is complete, click Finish. The trace starts. To repeat the trace, right-click the trace item and choose Copy from the shortcut menu.
2013-7-9
Page 33 of 202
INTERNAL
If CIT cannot be started, use one of the following methods:
Stop the trace items in Running state. The concurrent trace items supported by the M2000 are limited. Additionally, various tracing types (such as signaling, UIT, and CIT) are contained. Therefore, if the system prompts that there are too many trace items running currently, stop the unnecessary trace items, and then start a new CIT task again. Delete certain history trace items. Some system resources are occupied when the M2000 stores history trace tasks. If the current resources are lower than 20%, the trace task cannot be started. In this case, export the history trace data, delete the trace task, and then start a new CIT task. If trace cannot be started or other problems exist except the preceding cases, especially error codes are returned, contact relevant engineers at Huawei HQ to locate the problems.
2013-7-9
Page 34 of 202
INTERNAL
Daily Performance Monitoring

This chapter describes the start point of daily performance management, namely, some common performance monitoring methods such as daily performance report, weekly performance report, performance alarm, and unsolicited customer care. Field engineers should perform daily performance monitoring according to this chapter. The following table lists the major operations and requirements. Action Daily performance monitoring and analysis Requirement Mandatory. Performance data of at least one day of one week must be collected for monitoring. If conditions permit, it is recommended to perform daily monitoring. Operation and Output
Use the template to generate the WiMAX V32C03 Daily Report Template V2.0_2010-XX-XX.xls. Discover the network performance exceptions based on the daily report, create the XXX network performance issue tracking form.xls, handle common problems, report difficult problems to Huawei HQ, and trace the problem handling.
Weekly performance report
Mandatory. At least one weekly performance report is generated. If conditions permit, it is recommended to perform monitoring on a weekly basis. Optional. If conditions permit, it is recommended that unsolicited customer care be performed once every week. Optional. If conditions permit, urge customers to establish the platform.
Use the template to generate the WiMAX V32C03 Weekly Report Template V2.0_2010-XX-XX.xls.
Unsolicited customer care
Provide high-risk user pre-alert, create the Unsolicited Customer Care.xls, and submit the file to customers for unsolicited care. Collect and store CHR data for unsolicited customer care and highlevel problem analysis.
Establish the performance analysis platform (OMStar + server)
2013-7-9
Page 35 of 202
INTERNAL
3.2 Common KPIs

3.2.1 Accessibility KPIs
KPI Uni t % Calculation Formula Description User Norma l Range >80%
Radio Access Success Ratio
Network: Radio Access Success Ratio = (Basic capabilities negotiation request times + re-entry network success times from idle)/(initial network entry request times + re-entry network times from idle Number of Network Entry Failures due to Inter-Frequency Assignment Caused by No Access Permission)*100% Carrier: Radio Access Success Rate = (Basic capabilities negotiation request times + re-entry network success times from idle + HO complete times for HO in)/(initial network entry request times + re-entry network times from idle + ranging request times for ready HO in + ranging request times for unready HO in - Times of entry failure due to no access right and freq. assign)*100%
This KPI measures the success rate in the period starting from receiving of the RNG-REQ message to receiving of the SBC message. It involves only the success rate on the radio side and does not involve transmission and CN. By means of including the number of network re-entry times into the measurement, the denominator is effectively increased, and the impacts on the measurement caused by abnormal users can be reduced after the idle feature is enabled.
Customer
Initial Network Entry Radio Access Success Rate
Initial Network Entry Radio Access Success Rate = Basic capabilities negotiation request times/(initial network entry request times - Times of entry failure due to no access right and freq. assign)*100%
This KPI measures only the radio access success rate at initial network entry, without involving idle and handover. The major factors affecting this KPI include the air interface signaling quality and the admission control at RNG stage. This KPI can also be used to compare with the initial network entry success rate.
Customer
>80%
2013-7-9
Page 36 of 202
INTERNAL
KPI
Uni t %
Calculation Formula
Description
User
Norma l Range >40% (version earlier than V32C03 SPC300)
Initial Network Entry Success Rate
Initial Network Entry Success Rate = Registration success times/(initial network entry request times - network entry failure due to GW rejecting network entry failure times due to no getting for MS NAI network entry failure times due to no permitting)*100% Service Flow Establishment Success Rate = service flow setup success times/service flow setup request times*100%
The network entry success rate excludes the network entry failures caused by rejection of the network side. In terms of procedures, the service flow establishment procedure and the DHCP establishment procedure are not included. This KPI measures the probability of successful establishment of service flows. During establishment of service flows, admission determination is performed again to control user access based on the number of users, current load, and number of service flows. In this case, the service flows being established are included in the carrier load calculation.
Customer
Service % Flow Establish ment Success Rate
Customer
>90%
2013-7-9
Page 37 of 202
INTERNAL
3.2.2 Retainability KPIs

KPI Unit Calculation Formula Description User Norm al Rang e >180
Online Duration per Drop
min/tim e
Before SPC300: Online Duration per Drop = Carrier MS Online Duration/Times of MS Dropped from Network*60 After SPC300: Online Duration per Drop = Carrier MS Online Duration/Times of MS Dropped from Network*1000*60
For data services, it is recommended to use the online user drop rate. By measuring the online duration of users, you can convert the number of network drop times into the time interval of abnormal network exit, thus showing the retainability of users on the network. After the idle feature is enabled, MSs without services release resources and exit the network. In this case, the online user drop rate greatly decreases. Additionally, for versions earlier than C03SPC300, the unit total online duration of MSs is second; for C03SPC300 and later versions, however, the unit is millisecond. Therefore, for C03SPC300 and later versions, the result of this KPI must be divided by 1000.
Customer
2013-7-9
Page 38 of 202
INTERNAL
KPI
Unit
Calculation Formula
Description
User
Norm al Rang e <10%
Network Disconne ction Ratio
Before SPC500: Network Disconnection Ratio = The Times of MS Dropped from Network/(Online user number at the end of measurement period + The Times of MS Dropped from Network + Deregistration times due to MS + Deregistration times due to gateway + Deregistration times due to OM + Deregistration times from handoff source BS)*100% After SPC500: Network Disconnection Ratio = The Times of MS Dropped from Network/(Online user number at the end of measurement period + The Times of MS Dropped from Network + Deregistration times due to MS + Deregistration times due to gateway + Deregistration times due to OM + Deregistration times from handoff source BS + Times of Deregistration due to MS Power-Off)*100%
For data services, one user feature is that the connection is not released but stays in connection established state for a long time. In this case, the number of network entry times and the number of network exit times are relatively fewer. As a result, the measured retainability result is smaller than the actual one, and the real network status cannot be objectively reflected. It is recommended to use this KPI for reference.
Customer
3.2.3 Mobility KPI

KPI Unit Calculation Formula Handover Success Rate = Times of Completing Incoming Handover/ (Times of Handover Execution Triggered by MS + Number of Unready Incoming Handover Ranging Requests) Description User Norma l Range >85%
Handover Success Rate
The handover success rate is the proportion of successful handovers to the target carrier.
Customer
2013-7-9
Page 39 of 202
INTERNAL
3.2.4 User Experience KPI

KPI Uni t Calculation Formula Carrier DL BE Average Traffic Rate = DL BE Service Traffic * 8 / Carrier DL BE Traffic Duration Description This KPI indicates the actual rate experienced by all the BE users under one carrier during the downlink service time. It measures only the rate when the users are being served, thus excluding the impacts of no service time on the average rate. User Custome r Normal Range This KPI depends on the actual situation. For example, if the maximum rate for BE users in Philippine is 500 kbps, the average rate greater than 300 kbps is considered normal.
Carrier DL kbps BE Average Traffic Rate
It is similar for other service types and for uplink and downlink. Details are omitted.
3.2.5 Link Quality (Coding Efficiency) KPIs

KPI Uni t Calculation Formula Before SPC500: Carrier Average UL Slot Coding Efficiency = UL User Allocation Byte Number / (UL User Allocation Slot Number*6) After SPC500: Carrier Average UL Slot Coding Efficiency = UL User Allocation Byte Number / UL User Allocation Slot Number Description This KPI indicates the average value of all the users under one carrier when the MCS mode is used in the case of uplink services. This KPI measures the MCS mode during actual service of users and excludes the virtualhigh MCS mode when there is no uplink service. User Only for internal evaluatio n Normal Range >1.2
Carrier bpsc Average UL Slot Coding Efficiency
2013-7-9
Page 40 of 202
INTERNAL
KPI
Uni t
Calculation Formula Before SPC500: Carrier Average DL Slot Coding Efficiency = (DL All Zone MIMO-B User Allocation Byte Number + DL All Zone None MIMO-B User Allocation Byte Number + DL 1/3 Zone MIMO-B User Allocation Byte Number + DL 1/3 Zone None MIMO-B User Allocation Byte Number)/((DL All Zone MIMO-B User Allocation Slot Number + DL All Zone None MIMO-B User Allocation Slot Number + DL 1/3 Zone MIMO-B User Allocation Slot Number + DL 1/3 Zone None MIMO-B User Allocation Slot Number)*6) After SPC500: Carrier Average DL Slot Coding Efficiency = (DL All Zone MIMO-B User Allocation Byte Number + DL All Zone None MIMO-B User Allocation Byte Number + DL 1/3 Zone MIMO-B User Allocation Byte Number + DL 1/3 Zone None MIMO-B User Allocation Byte Number)/(DL All Zone MIMO-B User Allocation Slot Number + DL All Zone None MIMO-B User Allocation Slot Number + DL 1/3 Zone MIMO-B User Allocation Slot Number + DL 1/3 Zone None MIMO-B User Allocation Slot Number)
Description This KPI indicates the average value of all the users under one carrier when the MCS mode is used in the case of downlink services.
User Only for internal evaluatio n
Normal Range >2
Carrier bpsc Average DL Slot Coding Efficiency
2013-7-9
Page 41 of 202
INTERNAL
KPI DL Slot Occupied rate by DL MCS
Uni t %
Calculation Formula Slot Occupied rate by DL All Zone QPSK1/2 MIMO-B User = Slot Number Occupied by DL All Zone QPSK1/2 MIMO-B User/Total Slot Number Occupied by DL All Zone*100%
Description The service status of users is measured through the ratio of the slots occupied by each downlink order. This KPI measures the number of slots allocated to users, namely, distribution of slots occupied by service users. It is more accurate than mere calculation of MCS duration of all users at each order. The service status of users is measured through the ratio of the slots occupied by each uplink order. This KPI measures the number of slots allocated to users, namely, distribution of slots occupied by service users. It is more accurate than mere calculation of MCS duration of all users at each order.
User Only for internal evaluatio n
Normal Range <40%
UL Slot Occupied rate by UL MCS
Slot Number Occupied by UL All Zone QPSK1/2 MIMO-B User = Slot Number Occupied by UL All Zone QPSK1/2 MIMO-B User/Total Slot Number
Only for internal evaluatio n
<40%
3.2.6 Link Quality (Coverage Evaluation) KPIs

KPI Uni t Calculation Formula Downlink CINR less than 0 dB rate = downlink CINR less than 0 dB times/total downlink CINR times)*100% Downlink RSSI less than -90 dBm rate =downlink CINR less than -90 dBm times/total downlink CINR times)*100% Description Compared with the MCS mode, this KPI shows the precise downlink CINR distribution, which is reported by MSs and can be used to measure the downlink signal distribution of all users under one carrier. Downlink RSSI distribution is unrelated to MSs but depends only on channels and transmit power. It shows the downlink coverage status of the carrier. It can also compare with downlink CINR distribution measurement to preliminarily determine whether intra-frequency interference exists. User Only for internal evaluatio n Normal Range <40%
Downlink % CINR Distribution
Downlink % RSSI Distribution
Only for internal evaluatio n
<40%
2013-7-9
Page 42 of 202
INTERNAL
3.2.7 Load Capacity KPIs

KPI Uni t Calculation Formula Counter Description This KPI measures the uplink resource occupancy of the carrier when the number of users reaches a certain scale (namely, more than 30, which is configurable). It can be used to determine whether the system is congested. This KPI measures the downlink resource occupancy of the carrier when the number of users reaches a certain scale (namely, more than 30, which is configurable). It can be used to determine whether the system is congested. This KPI measures the average uplink throughput of the carrier when the number of users reaches a certain scale (namely, more than 50, which is configurable). It measures the actual throughput for uplink services of all the users under one carrier. This traffic measurement does not involve retransmission. This KPI should be customized or manually calculated on the M2000. This KPI measures the average downlink throughput of the carrier when the number of users reaches a certain scale (namely, more than 50, which is configurable). It measures the actual throughput for uplink services of all the users under one carrier. This traffic measurement does not involve retransmission. This KPI should be customized or manually calculated on the M2000. User Only for internal evaluation Normal Range <80%
UL % Average Resource Occupancy
DL % Average Resource Occupancy
Counter
Only for internal evaluation
<80%
UL average capacity
Mbps
UL average capacity = (uplink UGS traffic + uplink ERTPS traffic + uplink RTPS traffic + uplink nrtPS traffic + uplink BE traffic) / Stat. period*100%
This KPI should be determined with the resource occupancy and enabled functions. It does not have an absolute value.
DL average capacity
Mbps
DL average capacity = (downlink UGS traffic + downlink ERTPS traffic + downlink RTPS traffic + downlink nrtPS traffic + downlink BE traffic) / Stat. period*100%
This KPI should be determined with the resource occupancy and enabled functions. It does not have an absolute value.
2013-7-9
Page 43 of 202
INTERNAL
3.3 Generating Daily Performance Reports

Currently, the WiMAX V32C03 Daily Report Template V2.0_2010-6-21.xls is used to generate daily performance reports. This is a daily report generating tool in Excel format. This section describes how to use this tool.
3.3.1 Defining a Performance Measurement Template

For details on definition of the performance measurement template and the collection methods of performance measurement data, see section 2.6.1"Performance Measurement Data." When defining a performance measurement template, set counters and objects carefully.
Setting Counters
Due to loss of certain performance measurement data collected by the M2000, the data of different subjects is not completely parallel. As a result, the generated daily reports are incorrect. To ensure the correct calculation of the daily report generating tool, you should collect the associated counters concurrently based on the same performance measurement template and ensure that the counters required for calculation of each subject are saved in the same Excel file. Currently, there are 182 performance measurement counters required for the daily report template, among which 174 are carrier-level counters and eight are BTS-level counters (IP Path). A performance measurement collection template supports only 150 counters, and BTSlevel counters and carrier-level counters must be collected separately. Therefore, counters must be collected for three performance measurement templates. For details about the measurement counters added for the three templates, see the WiMAX V32C03 Daily Report Measurement Collection Template_2010-6-21.xls.
Classifying Objects by Area

The daily report generating tool can process only 65535 data records. The performance measurement period is 30 minutes. Each carrier has 48 records every day. In other words, when the number of carriers in the performance measurement template is greater than 1365, the exported performance measurement data will exceed the specification. If each BS has three sectors, a maximum of only 455 BSs are supported. If certain sites have multiple carriers, fewer BSs are supported. Therefore, you are advised to classify the BSs by area when many BSs are available (for example, classify 400 BSs to one area, which is not an absolute value and can be calculated according to the preceding specification), and then define performance measurement templates and generate daily reports by area. For example, you can define performance measurement templates 1, 2, and 3 for area 1 and templates 1, 2, and 3 for area 2. In these templates, counters are the same but BSs are different.
3.3.2 Generating a Daily Report

After collecting performance measurement data by the three templates from the M2000, start the daily report generating tool as follows: Start the macro of Excel, and then click Start on the Menu sheet. In the displayed window, select the BS version and counter name version, as shown in the following figure.
2013-7-9
Page 44 of 202
INTERNAL
The purpose of selecting the counter name version is to enable the counter names of the earlier BS version to the counter names of the later BS version after the M2000 is installed with the later mediation layer version of the BS. For example, if the version of the BS is C03SP205 but the M2000 upgrades the mediation layer to C03SPC500, the counter names of the C03SPC205 version change to those of the C03SPC500 version. Therefore, when selecting the version, you need to select the BS version to be analyzed first, and then select the counter name version of the M2000. Then, select the subjects to be analyzed according to the actual situation. For example, the handover feature is not enabled for Philippines, so you do not need to select Movability. Additionally, for IP path counter measurement, only Huawei GW of V3R3 version supports the IPPM function, and the IP path measurement is available only after this function is enabled. Therefore, if the IPPM function is not supported, you do not need to analyze the IP path.
2013-7-9
Page 45 of 202
INTERNAL
Then, import the performance measurement data collected from the M2000. For each subject, data is obtained from the three performance measurement templates respectively for analysis. The following figure shows the specific mapping. In other words, data can be exported from template 1 (instead of templates 2 and 3) to calculate the accessibility, retainability, movability, latency, and interference.
2013-7-9
Page 46 of 202
INTERNAL
Additionally, the filter conditions of the counter definition sheet in the daily report generating tool can be modified dynamically. After modification, the results in the daily report are filtered according to new filter conditions and marked in different colors.
2013-7-9
Page 47 of 202
INTERNAL
3.3.3 Analyzing the Daily Report

The daily report can show the basic status of the network. Different BSs require different daily report analysis periods. For important BSs, analysis must be performed every day; for common BSs, analysis can be performed once a week or month. Except for periodic analysis, daily report analysis must be performed before and after the BS version upgrade to compare
2013-7-9
Page 48 of 202
INTERNAL
the KPIs before and after upgrade and determine whether the upgrade improves the KPIs. Network optimization engineers need to discover and analyze problems according to the daily report and provide the solutions. For details about exceptions related to the daily report, see chapter 3"Daily Performance Monitoring", chapter 5"Accessibility Optimization", and chapter 6"Retainability Optimization." After daily report analysis, summarize the overall situation of the network, and record the discovered problems in the Philippines network performance issue tracking form20100512.xls to facilitate problem tracing and ensure the closing of problems.
3.3.4 Common Problem Related to Daily Report Generation

Performance measurement data may fail to be obtained from the M2000. The following prompt window is displayed.
The possible cause is that a certain BS does not subscribe to a certain performance measurement counter. Note that the BS needs to re-subscribe to all the performance measurement counters after being upgraded; otherwise, performance measurement data cannot be obtained. To re-subscribe to performance measurement counters, do as follows: Choose Performance > Measurement Management > Measurement Setting on the M2000, select the corresponding performance measurement template under the BS, and then select the BS name. If you need to apply the template to the whole network, select Network
2013-7-9
Page 49 of 202
INTERNAL
and All, select the required counters, and then click Apply.
3.4 Generating a Performance Report

The daily report uses the original performance measurement data obtained from the M2000 as inputs, whereas the weekly performance report uses the daily reports generated every day as inputs. Currently, the template WiMAX V32C03 Weekly Report Template V2.0_2010-6-21.xls is used to generate weekly performance reports. This weekly report template should be used with the daily report template WiMAX V32C03 Daily Report Template V2.0_2010-6-21.xls. Open the weekly report template, start the macro, and then click Start on the Home page.
2013-7-9
Page 50 of 202
INTERNAL
The following window is displayed.
As mentioned earlier, you need to classify BSs by area when defining the performance measurement template. When generating a weekly report, you need to select the number of areas, import the daily reports of one week of each area, and then click Start to generate weekly reports by area.
3.5 Performance Alarm

3.5.1 Purposes
When a group of predefined counters exceed the thresholds, the M2000 automatically generates an alarm so that problems can be found in time. Once an alarm is reported, relevant handling methods must be taken. Therefore, be cautious when defining performance alarms. Only alarms that clearly reflect problems can be defined. In normal cases, define only the recommended performance alarms.
3.5.2 Definition Modes of Performance Alarm

Step 1 Choose Performance > Threshold Management > Threshold Setting.
2013-7-9
Page 51 of 202
INTERNAL
Step 2 Select a desired NE type in the navigation tree, and then click Add.
Step 3 The following window is displayed. Select a measurement unit (BS for which you need to define the performance alarm) in the navigation tree. If you need to set the same performance alarm to all BSs, select All Available Object. Then, click the Basic Threshold Information tab, and then set the threshold name and alarm name.
2013-7-9
Page 52 of 202
INTERNAL
Step 4 Click the Extended Threshold Information tab. Performance alarms can be classified into simple performance alarms and combined performance alarms.
Simple performance alarms Simple performance alarms are classified into forward alarms and backward alarms. For the forward alarm, a threshold alarm can be generated only when the result value is equal to or greater than "threshold + offset". The greater the counter value, the higher level the alarm is. To clear the alarm, ensure that the result value is smaller than or equal to "threshold + offset". On the contrary, for the backward alarm, a threshold alarm is generated only when the result value is smaller than or equal to "threshold + offset". The smaller the counter value is, the higher the alarm severity is.
2013-7-9
Page 53 of 202
INTERNAL
Combined performance alarms The combined performance alarm indicates that an alarm is generated from two ore more performance counters. Click Combined, select the alarm severity to be defined, and then click set trigger condition.
In the displayed window, enter the trigger condition. Double-click the counter name, and the counter name is automatically displayed in Triggering conditions. Enclose the threshold of the counter in brackets when entering the value. Moreover, pay attention to the unit of the performance measurement counter when setting the threshold. Assume that the unit of the counter is %. If you need to set the threshold to 80%, enter only 80 in brackets.
2013-7-9
Page 54 of 202
INTERNAL
Step 5 Set the alarm clearing threshold. The procedure is similar to that for setting the trigger threshold. Click the Extended Threshold Information tab. Click set recover condition in the Recovering window. Set the alarm clearing condition in the displayed window. The alarm clearing condition is that the average number of users is greater than 2.
2013-7-9
Page 55 of 202
INTERNAL
3.5.3 Recommended Performance Alarms

"No Subscriber" Alarm
1. 2. 3. Trigger condition: number of access attempts > 1000 && average number of online users < 1 Clearing condition: average number of online users > 2 Handling method: If this alarm is generated, the BS may be faulty. Check the hardware and transmission status. Therefore, it is recommended to export data every day so that problems can be discovered and solved in time, for example, check whether carriers are available and whether transmission service links are interrupted. Supplementary description: This alarm is different from the "No Subscribers on a Carrier" alarm of the system. Before generating the "No Subscribers on a Carrier", the system does not check the number of access attempts, and the "No Subscribers" alarm may be generated because no users attempt to access the network. Therefore, the "No Subscribers on a Carrier" alarm cannot be used to determine whether the system is faulty or whether no users attempt to access the network.
4.
"Carrier Congestion" Alarm

5. Trigger condition: maximum number of online users > 80 or (DL average resource occupancy > 80% and DL BE user average traffic rate < 300 kbps) or (UL average resource occupancy > 80% and UL BE user average traffic rate < 100 kbps). For each site, proper thresholds can be defined according to the actual situation. Clearing condition: maximum number of online users < 80 and (DL average resource occupancy < 80% or DL BE user average traffic rate > 300 kbps) and (UL average resource occupancy < 80% or UL BE user average traffic rate > 100 kbps) Handling method: Export and analyze data every week. If the congestion alarms are frequently generated, the system needs to stop allocating numbers but expands the capacity by adding multiple carriers or BSs.
6.
7.
3.5.4 Querying Custom Alarms

The method of querying custom performance alarms is the same as that of querying system alarms. You can use the CTScriptMaker tool to prepare a script, log in to the M2000 through the Web interface, import the script to collect data, and then use the AAT tool to analyze the alarm logs. You can also directly click the alarm icon on the upper-right corner on the M2000, right-click any alarm, and then choose Save > Save All Records from the shortcut menu.
2013-7-9
Page 56 of 202
INTERNAL
3.5.5 Failure to Report Custom Alarms

After an alarm is customized, the alarm fails to be reported. Export the original data of relevant counters in the trigger conditions, but you can find that the alarm conditions are met. The possible cause is that one or more performance measurement counters in the multiple alarm conditions do not have values, and the M2000 regards that the alarm is invalid and does not check the other conditions. As a result, the alarm is not generated properly.
The possible causes that certain counters do not have values are as follows: 1. The performance measurement counter name is incorrect, for example, the counters of
2013-7-9
Page 57 of 202
INTERNAL
site C02 are named according to the counter names of site C03 or the counters of site C03 are named according to the counter names of site C02. In this case, the obtained counters do not have values. 2. Certain performance measurement counters are calculated by another two counters. For example, in the case that C = A/B, when B is 0, the M2000 regards that it is meaningless and C does not have a value. If individual sites do not subscribe to a certain performance measurement counter, the counter of the site does not have a value.
3.
When alarms cannot be generated properly, obtain the original data of relevant counters in the triggering conditions, and check whether the original data meets the alarm trigger conditions. If the conditions are met but alarms are not generated, handle the problem according to the preceding method.
3.6 Unsolicited Customer Care

The core idea of unsolicited customer care is that engineers should actively phone customers who have problems instead of passively waiting for customer complaints. Why is unsolicited care required? The reason is that traditional handling of user complaints is passive, and if users complain, problems have been serious. Moreover, most users directly quit without complaints if the problems are not solved within certain period. We recommend that operators use the unsolicited care mode if conditions permit. The recommended operation mode is that Huawei submit relevant problems to operators periodically, and operators carry out customer care activities. Use the OMStar to analyze CHR data to obtain the list of users requiring unsolicited care, fill the Unsolicited Customer Care Template.xls, and return it to the operator.
3.6.1 Users with Poor CINR

Data Sources
1. Use the OMStar to analyze the whole network user data of a certain period. It is recommended to analyze the data once every three days. Select user coverage analysis to export the Analysis of Single User Coverage table and compare the data with the previous analysis data. For the users whose DL CINR decreases by more than 10 dB, export the SBS information before and after DL CINR changes. In the OMStar, select User Complaint Analysis, choose Advanced > load from file, and import the list of MAC address in txt format. After the analysis is complete, export the Network Access Analysis table to obtain the BSIDs corresponding to these MAC addresses.
2.
2013-7-9
Page 58 of 202
INTERNAL
Handling Suggestion
3.
For a user with the CINR drop suddenly, check the previous service BSID, and check whether any operation is performed on the BS recently. If yes, analyze the operation results and the influences on the BS performance.
2013-7-9
Page 59 of 202
INTERNAL
4. 5. 6.
If no operation is performed recently, check whether the service BSID of the user changes. If the service BSID changes, check whether the original serving BS reports hardware/transmission alarms. If yes, check and rectify the hardware. If the original serving BS does not report any hardware alarm, check whether the original serving BS has admission restriction, which makes certain MSs fail to access this BS but access other BSs. If yes, the capacity or the number of users is restricted. In this case, field engineers should urge the customer to expand capacity. Otherwise, report the MAC address of the user to the operator and visit the user to find out the cause. If the serving BSID does not change, check whether the RSSI of the user becomes poor. If the RSSI of the user does not change, intra-frequency interference becomes more serious. In this case, check whether new sites are deployed around the original serving BS. If yes, optimize the coverage; if no, visit the user to find out the cause. If the service BSID of the user does not change but the RSSI becomes poor, check whether the RSSI of many users under the BS becomes poor. If yes, check the hardware, transmit power, and VSWR of the BS. If only some users have this problem, pay a return visit to these users.
7. 8.
9.
3.6.2 Users with Low Traffic Rate and Poor CINR

Data Sources
In the OMStar, select Traffic Rate Analysis, and export the Analysis of User Detail table to an Excel file. Filter the users whose DL BE rate is smaller than or equal to 300 kbps (this value varies with operators and relates mainly to the service rate configured for commercial users; usually, this value is set to 40% to 60% of the service rate) and DL CINR is smaller than or equal to 12 dB.
Handling Suggestion
Users with poor traffic rate most possibly quit, and unsolicited care is required. If the CINR is good but the traffic rate is low, it must be caused by congestion. Operators should visit the users with poor CINR.
3.6.3 Users Occupying Many Resources

Data Source
In the OMStar, select Traffic Rate Analysis and export the Analysis of User Detail table. DL BE Traffic(KB)/ Average DL Coding Efficiency indicates the relative DL resources occupied by the user; UL BE Traffic(KB)/ Average UL Coding Efficiency indicates the relative UL resources occupied by the user. If this value is large, air interface resources occupied by the user are many.
Handling Suggestion
Users occupying many DL/UL resources are low-value users. If these users occupy many resources, the possible causes are as follows: 1. 2. The traffic of the user is high. For handling suggestions, see section 3.6.4"High Traffic Users." The traffic of the user is not very high, but the slot efficiency is low and a great number
2013-7-9
Page 60 of 202
INTERNAL
of air interface resources are occupied due to the poor signal quality. Provide the list of these users to the operator and visit the users, to improve the signal quality and slot efficiency of these users, and reduce the occupied resources.
3.6.4 High Traffic Users

Data Source
In the OMStar, select Traffic Rate Analysis and export the Analysis of User Detail table. Perform sorting based on UL BE Traffic(KB)/ DL BE Traffic(KB). Users whose traffic is always high occupy a great number of resources.
Handling Suggestion
It is found that the daily download/upload traffic of some users is 6 GB. If these users are 512 kbps users, they download or upload the whole day at 512 kbps. These users may be Internet caf users, namely, low-value network users. In this case, provide the list of these users to the operator to restrict the traffic or rate of these users, thus avoiding congesting the entire carrier due to individual users.
2013-7-9
Page 61 of 202
INTERNAL
4
Action Parameter management
Routine Check on Network Performance

The routine network check is to eliminate the hidden danger affecting network performance, instead of analyzing the causes after problems are met. The contents of routine network check include parameter check, interference check, and active test on service experience. Onsite engineers should perform routine network check according to this chapter. The following table lists the major operations and requirements. Requirement Mandatory. Once per month Operation and Output
Set up and maintain the parameter configuration baseline of the project, and output the C03 KPI Template.MML. Check whether the actual configuration is consistent with the baseline and correct the inconsistent configuration items. Provide the Commercial network operations application.doc for the customer according to the actual situation of the site.
Interference check
Mandatory. Once per month
Monitor the interference status of the network according to the daily report, analyze the faulty carriers, determine the interference type, locate the problems, and prepare the Interference Optimization Archive for XXX Project of XXX Country.xls.
2013-7-9
Page 62 of 202
INTERNAL
Active test on service experience
Optional. If conditions permit, it is recommended that active test on service experience be performed once every week.
Select BSs based on certain rules, perform the onsite service experience test, and output the WiMAX user experience test report.xls.
4.2 Parameter Check

This section provides guidance for a quick check on parameter configuration in the entire network, involving the following operations: Step 1 Perform code planning and check the Network Engineering Parameters table. Step 2 Perform a configuration check at a typical site, complete the WiMAX Performance Parameter Configuration Rules for XX Project table and prepare the standard script C03 KPI Template.MML. Step 3 Perform a configuration check in the entire network using the Configuration Check Tool (CCT), and record the check results in the Template_CheckResult table. Modify the parameters by referring to the Template_CheckResult table and add modification records to the project configuration_ENG table.
4.2.1 Prerequisites
Ensure the following prerequisites are met before using the CCT:

Microsoft Office Excel 2003 or a later version is installed. The specified parameter configuration templates are available. References, templates and tools mentioned in this document can be obtained from the WiMAX Network Performance Management Activities folder.
1.
4.2.2 Parameter Check Procedure

Step 1 Perform code planning and check the Network Engineering Parameters table. 1. Get the following items ready: WiMAX Network Parameter Planning Guide V1.0 WiMAX APUS Tool WiMAX evaluation tool 2. Perform code planning using the WiMAX APUS Tool based on WiMAX Network Parameter Planning Guide V1.0. The Network Engineering Parameters table is generated as the code planning output. Check the Network Engineering Parameters table using the WiMAX evaluation tool.
If a code planning output table that has been checked by the evaluation tool is already provided, skip step 1.
3.
2013-7-9
Page 63 of 202
INTERNAL
Step 2 Perform a configuration check at a typical site, complete the WiMAX Performance Parameter Configuration Rules for XX Project table and prepare the standard script C03 KPI Template.MML. 1. Get the following items ready: WiMAX Performance Parameter Configuration Rules (V300R002C03)_V1.01 The parameter configuration script of the site to be checked. 2. Compare the parameters listed in the parameter configuration script of the site to be checked and those listed in the WiMAX Performance Parameter Configuration Rules (V300R002C03)_V1.01 table. Record the inconsistency in the Remarks column in the WiMAX Performance Parameter Configuration Rules (V300R002C03)_V1.01 table, and then save the table as WiMAX Performance Parameter Configuration Rules for XX Project.xls.
3.
Prepare the standard parameter configuration script by referring to the WiMAX Performance Parameter Configuration Rules (V300R002C03)_V1.01 , and save the standard script as C03 KPI Template.MML.
Step 3 Perform a configuration check in the entire network using the CCT, and record the check results in the Template_CheckResult table. 1. Get the following items ready: CCT and the Guide to Using the WiMAX Configuration Check Tool Standard parameter script C03 KPI Template.MML Parameter configuration scripts of the entire network to be checked
For details about how to obtain the parameter configuration scripts of the entire network, see the Guide to Using the WiMAX Configuration Check Tool.
2.
Open the project configuration_ENG table in the Template folder of the CCT installation directory.
3.
Fill the following information in the System Parameters sheet by referring to the Guide to Using the WiMAX Configuration Check Tool:
Huawei Technologies Proprietary Page 64 of 202
2013-7-9
INTERNAL
Site IDs, sector IDs, and carrier IDs of the BSs to be checked File name of the standard parameter configuration script, that is, C03 KPI Template.MML
If the standard script C03 KPI Template.MML is not saved in the Template folder, fill the absolute path saving the script instead of the file name.
4.
Fill the following information in the RNP Parameters sheet by referring to the Network Engineering Parameters table: Site IDs, sector IDs, and carrier IDs of the BSs to be checked Network engineering parameters to be checked
If any network engineering parameter to be check cannot be found in the RNP Parameters sheet, add a column in the sheet for the parameter.
5.
Start the CCT. Select the file project configuration_ENG.xls in the Select configuration para table area, and the parameter configuration scripts that are to be checked in the Select include configuration file folder area. Click Next to start the check in the entire network.
2013-7-9
Page 65 of 202
INTERNAL
6.
Save the check result in the Template_CheckResult table.
2013-7-9
Page 66 of 202
INTERNAL
Step 4 Modify the parameters by referring to the Template_CheckResult table and add modification records to the project configuration_ENG table. 1. 2. Modify parameters in the entire network by referring to Template_CheckResult table. Fill the modification records in the Modify Record columns in the two sheets of the project configuration_ENG table. For parameters that cannot be modified, record the reasons.
3.
Feed back the following files to Huawei headquarters: WiMAX Performance Parameter Configuration Rules for XX Project.xls Template_CheckResult.xls Project configuration_ENG.xls Parameter configuration scripts of the entire network before and after the modification
4.2.3 Parameter Check Period

The parameter check is performed once every two weeks. After the parameter configuration is relatively stable, the check can be performed once every month. Additionally, the parameter check can also be triggered by event, for example, parameters are checked after each version upgrade is performed.
4.2.4 Parameter Modification Process

Onsite network planning engineers maintain the parameter configuration baseline and check the parameters periodically. If incorrect parameters are found or parameters need to be modified for troubleshooting, network planning engineers should submit an application. After the application is approved by the WiMAX parameter committee at Huawei headquarters (whether to get approval from the customer should be determined by field engineers), TSD engineers modify the parameters (others cannot modify the existing network configuration) and feed back the results to network planning engineers after ensuring that parameters are modified successfully. Network planning parameters confirm and record the modified parameters and refresh the configuration baseline according to the actual situation. The process is as follows:
2013-7-9
Page 67 of 202
INTERNAL
The process documents are as follows: 1. 2. 3. Parameter modification application. Network planning engineers can submit an application according to the Commercial network operations application. Modification result feedback. Maintenance engineers and BS side engineers are responsible for reporting modification results. Parameter modification recording and archiving. Network planning engineers are responsible for recording modification results and modification time and recording the modifications in the parameter baseline table.
4.2.5 Key Parameters

Key parameters are classified into three categories: network planning parameters, feature parameters, and AMC threshold parameters. See the following table. Catego ry Network planning parameter Parameter ID CENTRALFREQUENCY DLZONETYPE segment DLPUSCSTCPERMBASE DLPUSCSTCPRBSID Categ ory Network planning paramete r Parameter ID SUBFRAMERATIO DLZONEIND preamble DLPUSCALLSTCPERMBASE DLPUSCAllSTCPRBSID
2013-7-9
Page 68 of 202
INTERNAL
Catego ry
Parameter ID ULPUSCPERMBASE DLZONENUM DL2NDZONESCHNUM CDMAGROUPSTART
Categ ory
Parameter ID ULPUSCALLPERMBASE DL2NDSTARTSYMBOL DLPUSCALLPERMBASE
Feature parameter
DEMODULATION MODULATION DLMIMOSWITCH DLAMSSWITCH DLZONEIND ULZONEIND ULOUTERLOOPPOWERS WITCH ULPWRCTRLMODE ULAMCSWITCH DLAMCSWITCH MIMOBAMCSWITCH LOADHOSWITCH SPARECAPSWITCH SFRATECTRLSWITCH ZONEHOSWITCH FCHRCI Software parameter P51 Software parameter P71 TRIGGERID TRIGGERFUNCTION TRIGGERVALUE
Feature paramete r
ARQSUPP MACMCSSCHSWITCH MOBFEATURESUPP DLOUTLOOPPWRCTR ULOUTERLOOPLOWTH ULOUTERLOOPUPTH ULOUTERLOOPPERHARQ DLOUTERLOOPLOWTH DLOUTERLOOPUPTH HARQDLOUTPERTARGET ULPUSCROTATION DLAMCMAXREPETIRION ULAMCMAXREPETIRION DLINITREPETITION ULCTRLSUPP MAPTYPE Software parameter P69 Software parameter P84 TRIGGERTYPE TRIGGERACTION TRIGGERAVERDURATION
AMC threshold parameter
DL 64QAM5/6 in threshold DL 64QAM5/6 out threshold DL 64QAM3/4 in threshold
AMC threshold paramete r
DL MIMO-A 64QAM5/6 out threshold DL MIMO-A 64QAM3/4 in threshold DL MIMO-A 64QAM3/4 out threshold
2013-7-9
Page 69 of 202
INTERNAL
Catego ry
Parameter ID DL 64QAM3/4 out threshold DL 64QAM2/3 in threshold DL 64QAM2/3 out threshold DL 64QAM1/2 in threshold DL 64QAM1/2 out threshold DL 16QAM3/4 in threshold DL 16QAM3/4 out threshold DL 16QAM1/2 in threshold DL 16QAM1/2 out threshold DL QPSK3/4 in threshold DL QPSK3/4 out threshold DL QPSK1/2 in threshold DL QPSK1/2 out threshold UL 16QAM3/4 in threshold UL 16QAM3/4 out threshold UL 16QAM1/2 in threshold UL 16QAM1/2 out threshold UL QPSK3/4 in threshold UL QPSK3/4 out threshold
Categ ory
Parameter ID DL MIMO-A 64QAM2/3 in threshold DL MIMO-A 64QAM2/3 out threshold DL MIMO-A 64QAM1/2 in threshold DL MIMO-A 64QAM1/2 out threshold DL MIMO-A 16QAM3/4 in threshold DL MIMO-A 16QAM3/4 out threshold DL MIMO-A 16QAM1/2 in threshold DL MIMO-A 16QAM1/2 out threshold DL MIMO-A QPSK3/4 in threshold DL MIMO-A QPSK1/2 in threshold DL MIMO-B 64QAM5/6 in threshold DL MIMO-B 64QAM5/6 out threshold DL MIMO-B 64QAM3/4 in threshold DL MIMO-B 64QAM3/4 out threshold DL MIMO-B 64QAM2/3 in threshold DL MIMO-B 64QAM2/3 out threshold DL MIMO-B 64QAM1/2 out threshold DL MIMO-B 16QAM3/4 in threshold DL MIMO-B 16QAM3/4 out threshold
2013-7-9
Page 70 of 202
INTERNAL
Catego ry
Parameter ID UL QPSK1/2 in threshold UL QPSK1/2 out threshold FECREPEATTWOTHSTEP FECREPEATFOURTHSTEP FECREPEATSIXTHSTEP DL MIMO-A 64QAM5/6 in threshold
Categ ory
Parameter ID DL MIMO-B 16QAM1/2 in threshold DL MIMO-B 16QAM1/2 out threshold DL MIMO-B QPSK3/4 in threshold DL MIMO-B QPSK3/4 out threshold DL MIMO-B QPSK1/2 in threshold DL MIMO-B QPSK1/2 out threshold
For details about the parameters, see the Description of Key Parameters.
D escri pt i on of Key Param et ers. doc
4.2.6 Reference Documents

Document Name XXX Project Parameter Configuration Baseline Form Usage Instructions on WiMAX Configuration Check Tool Commercial network operations application Description of Key Parameters WiMAX Preamble Planning and Configuration Guide Describes Whole network parameter baseline and recording of parameter modifications. Usage instructions for the CCT. Application Scenario Site parameter baseline maintenance Parameter check
Parameter modification application form provided for the customer. Meanings and functions of key parameters. Guidance for WiMAX preamble planning configuration.
Parameter modification application Parameter check Preamble planning
2013-7-9
Page 71 of 202
INTERNAL
4.3 Interference Check

Interference can be classified into uplink interference and downlink interference. Usually, external interference causes both uplink and downlink interference, and uplink interference is more serious. Therefore, you can determine whether external interference exists by checking uplink interference. Internal interference of the system also causes uplink and downlink interference. Downlink interference is mainly caused by frequency planning; therefore, the reasonability of frequency planning should be evaluated through the frequency planning module of the WiMAX automatic evaluation tool. Uplink interference is caused by GPS synchronization loss and TDD interference. Therefore, the interference check guide mainly describes how to check uplink interference.
4.3.1 TDD Interference Optimization

4.3.1.1 Symptom Identification
TDD interferences make the DL HARQ ACK channels in the UL common zones be interfered, causing missed detection of DL HARQ ACK. Thus, you can find that the DL HARQ retransmission rate is high through the performance report. It is recommended to locate the carriers with DL HARQ retransmission rate more than 30% during the routine performance report check.
4.3.1.2
Troubleshooting and Optimization

The collection scripts of the 8HP and 4HP boards and the silence inverse spectrum collection script of the 4HP board (the 8HP board does not support silence inverse spectrum collection) are as follows: Note that the BOARDNO parameter in the collection command should be set according to the actual situation. In the case of multi-carrier configuration, pay attention to the mapping between the carrier ID and the board No. The IP address, user name, and password of the FTP server in the upload connection should be set according to the actual situation. If there is no specialized FTP server onsite, use the M2000 as the FTP server to upload inverse frequency spectrum data. 1. Check whether the board type is 8HP or 4HP.
Step 1 Collecting inverse frequency spectrum
2013-7-9
Page 72 of 202
INTERNAL
Run the LST BRD command. If EXPANSIONBOARDTYPE in the return result is BBIa, the board type is 8HP; if EXPANSIONBOARDTYPE in the return result is BBIb, the board type is 4HP. As shown in the following figure, the board type is 4HP.
2.
MML commands for collecting inverse frequency spectrum data from the 8HP board Sector 0:
SET FPGATRANS: BOARDNO=3, TransCmdId=0, Para1=65548, Para2=1310976, Para3=0; SET FPGATRANS: BOARDNO=3, TransCmdId=1, Para1=1310976, Para2=2149580800, Para3=0; SET FPGATRANS: BOARDNO=3, TransCmdId=2, Para1=6, Para2=0, Para3=0; ULD FILE: SRCF="fpga_phy_a", CN=0, SRN=0, SN=3, DSTF="sec0_ant0", IP="10.4.1.213", USR="admin", PWD="admin";
Sector 1:
Sector 2:
3.
SET FPGATRANS: BOARDNO=3, TransCmdId=0, Para1=9, Para2=44142628, Para3=0; SET FPGATRANS: BOARDNO=3, TransCmdId=1, Para1=6147, Para2=100, Para3=0; SET FPGATRANS: BOARDNO=3, TransCmdId=2, Para1=8, Para2=0, Para3=0; ULD FILE: SRCF="fpga_phy_a", CN=0, SRN=0, SN=3, DSTF="sec0_ant0", IP="192.168.17.159", USR="mptc", PWD="mptc";
Sector 1:
SET FPGATRANS: BOARDNO=3, TransCmdId=0, Para1=9, Para2=44142637, Para3=0; SET FPGATRANS: BOARDNO=3, TransCmdId=1, Para1=6147, Para2=100, Para3=0; SET FPGATRANS: BOARDNO=3, TransCmdId=2, Para1=8, Para2=0, Para3=0;
2013-7-9
Page 73 of 202
INTERNAL
ULD FILE: SRCF="fpga_phy_a", CN=0, SRN=0, SN=0, DSTF="sec1_ant0", IP="192.168.17.159", USR="mptc", PWD="mptc";
Sector 2:
4.
MML commands for collecting inverse frequency spectrum data from the 4HP board in silence mode Start the collection.
STR SPECSCANPARA: SECTORID=0, CARRIERID=0, SCANDIRECTION=UPLINK, SILENCEFLAG=YES, SCANPERIOD=20SEC, SCANDURATION=10MIN, SCANPOINT=ADC;
Select UPLINK(UPLINK) from the Direction of Spectrum Scanning drop-down list box. Select ADC from the Data Collection Point of Spectrum Scan drop-down list box. If YES(YES) is selected from Silence Flag of Spectrum Scanning drop-down list box, the UL DSP spectrum scanning is enabled.
Stop the collection:

STP SPECSCANPARA;
This command can be used to stop the collection stops within the preset time.
Generate the silence inverse spectrum file of the DSP:

EXP DATAFILE: RACKNO=0, SUBRACKNO=0, BOARDNO=3, FILETYPE="dsp_spec";
This command is used to move the data in the DSP DDR memory to the high-end memory. The intermediate frame No. and slot No. should be set according to the actual situation of each site.
Upload data:
ULD FILE: SRCF=" dsp_spec ", CN=0, SRN=0, SN=3, DSTF=" dsp_spec ", IP="192.168.17.159", USR="mptc", PWD="mptc";
Step 2 Downloading inverse frequency spectrum data It is recommended to use the FTP tool such as FileZilla to download inverse frequency spectrum data. If the DOS command is used for downloading, the bin transfer mode must be used.
2013-7-9
Page 74 of 202
INTERNAL
Step 3 Analyzing the inverse frequency spectrum to determine whether TDD interferences exist Use the C03 spectrum analyzer to analyze the data. For details on how to use the tool, see the WiMAX Spectrum Analyzer User Guide V32C03.doc. Open the chart of average RSSI distribution of all symbols of the tool. This chart shows the average signal strength of each symbol in all collected UL sub-frames. As shown in the following figure, 345 symbols are collected, namely, 23 UL sub-frames (DL/UL subframe ratio is 31:15, 23 x 15 =345). The right chart shows that symbols 1, 16, 31, are burst at the interval of 15 symbols, that is, the first symbol of each UL sub-frame is interfered.
Normal Norma l
Inte Interfered rfer
First few symbols of each uplink subframe are interfered.
Note that when the time difference of GPS synchronization loss is small, the characteristics of the inverse frequency spectrum are similar to those of TDD interferences. The biggest difference is that GPS synchronization loss causes interferences on multiple peripheral cofrequency carriers. Then, the positions of the interfered symbols in the inverse frequency spectrum of these co-frequency carriers are different from those of the BSs out of GPS synchronization, whereas the TDD interferences must interfere with the first several symbols in each UL sub-frame. As shown in the following figure, for the BS out of GPS synchronization (DL/UL subframe ratio is 29:18, a total of three frames and 54 symbols), the first three symbols in each UL sub-frame are interfered; for peripheral co-frequency carriers, the last three symbols are interfered. Certainly, the GPS synchronization loss can be put ahead or postponed. That is, the BS with the first symbols interfered is unnecessarily the BS out of GPS synchronization. If the first three symbols of the carrier of only one BS are interfered, and the last three symbols of multiple carriers are interfered, the BS must be out of GPS synchronization, and the vice versa.
The first three symbols of each uplink subframe are interfered.
The last three symbols of each uplink subframe are interfered.
Usually, the BS out of GPS synchronization reports the following history alarms (that means
2013-7-9
Page 75 of 202
INTERNAL
GPS has been out of synchronization though the alarms are cleared). These alarms, however, are not the absolute criteria for determining the GPS synchronization loss. Currently, it is found the carriers still work properly though the alarms are reported or no alarms are reported though the GPS has been out of synchronization. Therefore, these alarms are used for reference only, and the direct proof is still the analysis result of the inverse frequency spectrum. The V3R2C03SPC300 has been integrated with the automatic detection and recovery mechanism. After the version is upgraded, the probability of this problem will be greatly reduced. Severi ty Name Alar m Sourc e WASEA05 58 WASEA05 58 WASEA05 58 WASEA05 58 WASEA05 58 WASEA05 58 WASEA05 58 WASEA05 58 WASEA02 47 WASEA02 47 Location Information Occurren ce Time(NT) 09/01/2010 04:32:21 09/01/2010 04:32:21 09/01/2010 04:32:21 09/01/2010 04:32:21 Alar m ID Clearan ce Time(N T) 09/01/2010 04:34:35 09/01/2010 04:34:35 09/01/2010 04:34:35 09/01/2010 04:34:35
Critical
Unavailable Carrier Resource Unavailable Carrier Resource Unavailable Carrier Resource Clock Exception on Main Control Board Unavailable Carrier Resource Unavailable Carrier Resource Unavailable Carrier Resource Clock Exception on Main Control Board Unavailable Carrier Resource Unavailable Carrier Resource
Sector No.=2,Carrier No.=0, Specific Problem=The clock is unavailable. Sector No.=1,Carrier No.=0, Specific Problem=The clock is unavailable. Sector No.=0,Carrier No.=0, Specific Problem=The clock is unavailable. Cabinet No.=0,Subrack No.=0,Slot No.=7, Specific Problem= Fail of the Clock Synchronization Sector No.=2,Carrier No.=0, Specific Problem=The clock is unavailable. Sector No.=1,Carrier No.=0, Specific Problem=The clock is unavailable. Sector No.=0,Carrier No.=0, Specific Problem=The clock is unavailable. Cabinet No.=0,Subrack No.=0,Slot No.=7, Specific Problem= Fail of the Clock Synchronization Sector No.=0,Carrier No.=0, Specific Problem=The clock is unavailable. Sector No.=1,Carrier No.=0, Specific Problem=The clock is unavailable.
10001
Critical
10001
Critical
10001
Critical
10040
Critical
10/01/2010 00:22:10 10/01/2010 00:22:10 10/01/2010 00:22:10 10/01/2010 00:22:10
10001
10/01/2010 00:24:24 10/01/2010 00:24:24 10/01/2010 00:24:24 10/01/2010 00:24:24
Critical
10001
Critical
10001
Critical
10040
Critical
10/01/2010 01:31:34 10/01/2010 01:31:34
10001
10/01/2010 01:33:47 10/01/2010 01:33:47
Critical
10001
2013-7-9
Page 76 of 202
INTERNAL
Severi ty
Name
Alar m Sourc e WASEA02 47 WASEA02 47 WASEA02 47 WASEA02 47 WASEA02 47
Location Information
Occurren ce Time(NT) 10/01/2010 01:31:34 10/01/2010 01:31:34 10/01/2010 01:31:34 10/01/2010 01:31:34 10/01/2010 01:31:34
Alar m ID
Clearan ce Time(N T) 10/01/2010 01:33:47 10/01/2010 01:33:47 10/01/2010 01:33:47 10/01/2010 01:33:47 10/01/2010 01:33:47
Critical
Unavailable Carrier Resource Unavailable Carrier Resource Unavailable Carrier Resource Unavailable Carrier Resource Clock Exception on Main Control Board
Sector No.=2,Carrier No.=0, Specific Problem=The clock is unavailable. Sector No.=0,Carrier No.=1, Specific Problem=The clock is unavailable. Sector No.=1,Carrier No.=1, Specific Problem=The clock is unavailable. Sector No.=2,Carrier No.=1, Specific Problem=The clock is unavailable. Cabinet No.=0,Subrack No.=0,Slot No.=7, Specific Problem= Fail of the Clock Synchronization
10001
Critical
10001
Critical
10001
Critical
10001
Critical
10040
If you determine that the GPS has been out of synchronization, run the RST SYS to restart the BS. If you can determine that the TDD interferences occur, go to the next step. Step 4 Adjusting the engineering parameters of the interfered site. Interference sources are usually multiple BSs. Therefore, first check the altitude, antenna height, and downtilt angle of the interfered site, and try to reduce the antenna height, increase the downtilt angle, and adjust frequencies without affecting the original coverage. If the problem persists, go to the next step. Step 5 Find out the possible interfering BSs. Determine the interference source distance based on the number of interfered symbols. One Symbol Interfered 29:18 31:15 31.7-62.6 km 62.6-93.4 km Two Symbols Interfered 62.6-93.4 km 93.4-124.3 km Three Symbols Interfered 93.4-124.3 km
Use the correlation search to find out the possible interfering BSs. For details on how to use the tool, see the WiMAX Spectrum Analyzer User Guide V32C03.doc. Match the found BSs according to the distances listed in the preceding table to further locate the interfering BSs. Then, reduce the power of these BSs one by one (if possible, deactivate the carriers), and then collect the inverse frequency spectrum data to check whether the interference power reduces. If so, you can determine that the corresponding BS is an interfering BS. The correlation search and power reduction operations should be performed repeatedly until all interfering BSs are located.
2013-7-9
Page 77 of 202
INTERNAL
Step 6 Adjusting the engineering parameters of the interfering BSs Try to reduce the antenna height, increase the downtilt angle, and adjust frequencies without affecting the original coverage. If still some BSs cannot be located, go to the next step. Step 7 Taking the emergency measures The emergency measures are used to prevent TDD interferences at the cost of other performances. Do not take these measures unless no other means are available. 1. Modify DL/UL subframe ratio from 29:18 to 31:15 on the whole network. Disadvantages: The UL rate is reduced. This measure is not applicable to sites having high requirements on the UL rate or UL/DL rate symmetry (for example, VoIP sites). If the SBC-REQ occupies one more sub-channel due to the reduction of UL sub-frame symbols, the MS network access performance will be degraded. Reduce the length of the DL sub-frame of the interfering BS. Disadvantages: The DL rate is reduced. Additionally, there are many interfering BSs. Disable CQICH reporting and use REP reporting instead. Disadvantages: The reporting frequency of DL measurement information is low. The air interface overhead is increased. Disable DL HARQ. Disadvantage: The DL HARQ gain is reduced.
2. 3.
4.
The emergency measures must be approved by Huawei HQ before implementation. Send the following information to Huawei HQ before submitting the emergency measures for reviewing. 5. 6. Network topology, in Mapinfo or Google Earth format. Engineering parameter table of the whole network. It must contain the information such as latitude, longitude, azimuth, site height, frequency, DLPUSCALLSTCPERMBASE, and DLPUSCALLSTCPRBSID. DLPUSCALLSTCPERMBASE and DLPUSCALLSTCPRBSID can be queried by running the LST CARRIERZONEINFO command. Interference optimization archive. It must contain the inverse frequency spectrum data before and after engineering parameter adjustment in Step 4 and Step 6, and the list of interfering BSs confirmed in Step 5.
1.
4.3.1.3
Interference Optimization Archive Setup

Archive the HARQ retransmission rate, engineering parameters, and inverse frequency spectrum data before and after adjustment. For the template, see the Interference Optimization Archive for XX Project.
4.3.2 External Interference Optimization

4.3.2.1 Symptom Identification
Usually, if external interferences exist, the NI density and NI intensity in the performance reports are higher. It is recommended to locate the carriers with NI intensity > -85 dBm or NI density > 10% during the routine performance report check.
2013-7-9
Page 78 of 202
INTERNAL
4.3.2.2
Analysis and Troubleshooting

The collection scripts of the 8HP and 4HP boards and the silence inverse spectrum collection script of the 4HP board (the 8HP board does not support silence inverse spectrum collection) are as follows: The BOARDNO parameter in the collection command should be set according to the actual situation. In the case of multi-carrier configuration, pay attention to the mapping between the carrier ID and the board No. The IP address, user name, and password of the FTP server in the upload connection should be set according to the actual situation. If there is no specialized FTP server onsite, use the M2000 as the FTP server to upload inverse frequency spectrum data. 1. Check whether the board type is 8HP or 4HP. Run the LST BRD command. If EXPANSIONBOARDTYPE in the return result is BBIa, the board type is 8HP; if EXPANSIONBOARDTYPE in the return result is BBIb, the board type is 4HP. As shown in the following figure, the board type is 4HP.
Step 1 Collecting inverse frequency spectrum
2.
SET FPGATRANS: BOARDNO=3, TransCmdId=0, Para1=65548, Para2=1310976, Para3=0; SET FPGATRANS: BOARDNO=3, TransCmdId=1, Para1=1310976, Para2=2149580800,
2013-7-9
Page 79 of 202
INTERNAL
Para3=0; SET FPGATRANS: BOARDNO=3, TransCmdId=2, Para1=6, Para2=0, Para3=0; ULD FILE: SRCF="fpga_phy_a", CN=0, SRN=0, SN=3, DSTF="sec0_ant0", IP="10.4.1.213", USR="admin", PWD="admin";
Sector 1:
Sector 2:
3.
Sector 1:
Sector 2:
4.
MML commands for collecting inverse frequency spectrum data from the 4HP board in silence mode Start the collection.
STR SPECSCANPARA: SECTORID=0, CARRIERID=0, SCANDIRECTION=UPLINK, SILENCEFLAG=YES, SCANPERIOD=20SEC, SCANDURATION=10MIN, SCANPOINT=ADC;
2013-7-9
Page 80 of 202
INTERNAL
Select UPLINK(UPLINK) from the Direction of Spectrum Scanning drop-down list box. Select ADC from the Data Collection Point of Spectrum Scan drop-down list box. If YES(YES) is selected from Silence Flag of Spectrum Scanning drop-down list box, the UL DSP spectrum scanning is enabled.
Stop the collection:

STP SPECSCANPARA;
This command can be used to stop the collection stops within the preset time.
Generate the silence inverse spectrum file of the DSP:

EXP DATAFILE: RACKNO=0, SUBRACKNO=0, BOARDNO=3, FILETYPE="dsp_spec";
This command is used to move the data in the DSP DDR memory to the high-end memory. The intermediate frame No. and slot No. should be set according to the actual situation of each site.
Upload data:
ULD FILE: SRCF=" dsp_spec ", CN=0, SRN=0, SN=3, DSTF=" dsp_spec ", IP="192.168.17.159", USR="mptc", PWD="mptc";
Step 2 Analyzing the inverse frequency spectrum Use the C03 spectrum analyzer to analyze the data. For details on how to use the tool, see the WiMAX Spectrum Analyzer User Guide V32C03. Check all the "The subcarrier power of xx frame xx symbol" charts through the tool. This chart presents the power of all sub-carriers of xx symbol of xx frame. The following figure shows the power of 1024 sub-carriers (10 MHz bandwidth). The normal OFDMA signal spectrum should be comb-shaped. If interferences exist, you can roughly determine the bandwidth and frequency channels of the interference signals through the spectrum.
2013-7-9
Page 81 of 202
INTERNAL
Normal
In-band narrowband interference
Interference without subscribers
Interference with subscribers
When the power control fails, the BTS background noise rises because the MS transmit power increases. In this case, the subcarrier power of the MS reaches -40 dBm.
Out-band interference source signals
Note that when the time difference of GPS synchronization loss is large or the TDD interference distance is long (that is, more symbols are interfered in addition to the first three ones), the NI is also increased. For the analysis and locating methods, see the locating method for GPS synchronization loss in the TDD Interference Optimization Guide. The following figure shows that nine symbols are out of GPS synchronization.
2013-7-9
Page 82 of 202
INTERNAL
The first few symbols of downlink subframe for other BTSs form preamble boosting.
The last few symbols of downlink subframe for other BTSs are displayed.
Step 3 Finding out the interference sources When external interferences exist, use the following method to find out the interference sources. 1. Analyze the interference source characters through the frequency spectrum and check whether these characteristics are consistent with those in peripheral communication systems. Analyze whether the interferences occur regularly or always exist. Display NI counters on a map and analyze whether the NI counters of peripheral sectors are abnormal. Collect the frequency spectrum from the peripheral sites to determine the approximate area of the interference source. Check whether the isolation distance of co-site BSs is enough and whether the combiner is damaged. Use the spectrum analyzer and the high-gain directional antenna to sweep the frequency channels in the area where interferences possibly exist, determine the specific direction of the interference source, and then find out the interference source.
2. 3. 4. 5. 6.
Step 4 Clearing interferences In the case of inband interferences, urge the customer to clear frequency channels. In the case of outband interferences, take engineering measures such as increasing the isolation distance and adjusting frequency channels to solve the problem. If the interference source is the WiMAX 16d system, communicate with Huawei RD and consider the synchronization solution.
4.3.2.3 Interference Optimization Archive Setup

Archive the NI density, NI intensity, interference type, and inverse frequency spectrum data before and after interference clearance. For the template, see the Interference Optimization Archive for XX Project of XX Country.
4.4 Service Experience Test

For the routine on site maintenance is a periodic activity to keep track of the network status. The test engineer represents a common user. Through actual service experience in important sectors or sectors where many users complain, the test engineer can know user feelings and
2013-7-9
Page 83 of 202
INTERNAL
discover problems. Tests should be arranged periodically according to the importance of the sites. Usually, two sites should be tested per day.
4.4.1 Rules for Selecting Test Sites

The sites for weekly service experience should be determined at the weekly routine meeting (complaint handling is not included). Onsite tests are conducted by network planning team. The purpose of service tests is to discover problems. Therefore, site selection should take user experience and problem probability into account and be random to some degree. Generally, site selection should comply with the following rules based on priority: 1. 2. 3. Sectors with a great number of access users: Sort the sites by the average number of users in busy hours, select those with many users, and perform service tests one by one. Sectors under which users complain: If many users under a certain sector complain, try to perform service tests on this sector in priority. VIP areas: Perform service tests in priority on sectors covering the important coverage areas selected by the customer, important number distribution areas, and areas where the construction personnel and relevant personnel of the customer reside, thus avoiding unnecessary complaints. Except for the preceding rules, other sites can be selected randomly. Try to perform service experience tests in each area of the network.
4.
Before testing, the testing personnel should know about the background and status of sites and get required information in advance. 5. 6. 7. Confirm the background status: Check whether BSs report alarms recently. Network planning parameters: including the heights, azimuths, and downtilt angles of sites, distance between sites, and location and heights of peripheral sites. Confirm the transmission status in priority: Check whether any transmission problems occur on sites through ping operations and transmission measurement in the daily report, and contact transmission engineers to know whether 2G/3G co-site exists. Interference scenario: Check whether an area has external interference. Select the handover bands in advance.
cmd setuser,su set wimax-log on cmd showver cmd showsf,1 cmd resetpacketfl cmd showsscaps cmd displaye cmd resetss (The preceding information is printed only once.) cmd showss cmd showssp cmd showphystats cmd showrftx cmd UPCS:cont cmd mss: cmd showpacketfl (The preceding information is displayed cyclically.)
8. 9.
10. Prepare relevant MS print scripts. See the following example:
2013-7-9
Page 84 of 202
INTERNAL
When the USB Dongle such as BM325 is used, the string "cmd" before commands can be omitted. This script is based on MSs using Sequans chip. It is inapplicable to MSs using Beceem chips, for example, BM328.
4.4.2 Test Operations

The recommended onsite test operations are as follows: 1. 2. If a site under which users complain, test the testing points similar to the radio environment of the complaining users in priority. Select scenarios with different signal quality for tests. Take downlink as an example. Select a test point where the downlink CINR is between 14 and 18 dB and a test point where the DL CINR is less than 12 dB. Normally, no test is required in areas where the downlink CINR is good (more than 20 dB). If problems are found in areas with the intermediate CINR, test the peripheral points. Before testing at each test point, run the print script on the MS. The test at each test point should include at least the following items: Network access: Try to access the network for 10 times. The network access succeeds if the IP address can be obtained. Download: Start intranet download through FTP for one minutes and internet download for two minutes (which is not limited to FTP mode, but the smooth download source should be selected). Use the DU meter to observe the transmission chart and open a stopwatch to record the average values. Upload: Start intranet and internet upload through FTP for two minutes respectively (other modes can also be used for internet upload). Use the DU meter to observe the transmission chart and open a stopwatch to record the average values. Ping: Ping the intranet server and the homepage of Google in the local country through ICMP ping for 20 times at two kinds of packet lengths (namely, 128 and 1500 bytes) Web page browse: Browse Web pages for three minutes. The target pages are not restricted. Online video: Open two or three video files at Youtube. Handover test (if the network disables handover, skip the test): Perform two handovers at handover bands while browsing Web pages. 5. The data that should be recorded is as follows: Latitude and longitude of test points Number of successful/unsuccessful network entry/handover times, number of abnormal drops during the test Outputs of MSs (including the network entry records of MSs) Transmission charts of the DU meter and snapshots of stopwatch for upload and download Log records of ping packets For user experience tests such as Web page browse and online video, use the DU meter and stopwatch to record transmission graphs and give brief descriptions. In the case of high speed and excellent experience, directly enter "ok". If Web pages cannot be opened or are opened slowly, describe the symptom briefly, for example, "Web pages are opened slowly", "server not found", or "video is not smooth". For each test item, restart the log function. Do not record the logs of the whole
3. 4.
2013-7-9
Page 85 of 202
INTERNAL
process in one file. If conditions permit, trace R1/R6 interface signaling and GW/AAA signaling, of users, corresponding users, and carriers.
4.4.3 Test Report Output and Tracing

After the test is complete, a test report should be provided. For the format and contents of the report, see the WiMAX User Experience Test Report.xls. Pay attention to the following points for writing the test report: 1. 2. Show the positions of sites and test points on a snapshot of Google Earth. During test, for example, in the process of upload, download, Web page browse, or online video playing, start the DU Meter and Stopwatch, capture transmission graphs, and attach the graphs to the report (one snapshot of each test point is required). In the case of network entry failure, copy only the last record before the failure occurs to the test report. No cause analysis is required. Fill the test report according to the test progress to improve the efficiency. Save the logs of the MS to a txt file and attach it to the test report.
3. 4. 5.
Specific problem location information is not included in the test report. If problems can be determined immediately during test, feed back to relevant NE engineers. If problems cannot be determined immediately, submit problem reports to Huawei headquarters for analysis and tracing (by maintenance engineers).
2013-7-9
Page 86 of 202
INTERNAL
5
1. 2. 3.
Accessibility Optimization

This chapter describes some features related to accessibility based on the understanding of accessibility counters. It focuses on how to handle the low network access success rate. After completing this chapter, field technical personnel should understand the accessibility KPIs, and reach the following requirements: Technical engineers are able to analyze and solve common accessibility problems. Some engineers with powerful technical skills are able to use the OMStar and AAT to analyze and solve high-level performance problems related to accessibility. WiMAX engineers are not required to solve difficult problems independently, but they must know how to collect relevant data. Technical engineers should be able to collect relevant data and return it to R&D engineers to analyze and locate problems.
2013-7-9
Page 87 of 202
INTERNAL
5.2 WiMAX Access Process

5.2.1 WiMAX Network Entry Process
2013-7-9
Page 88 of 202
INTERNAL
5.2.2 Normal Network Entry Signaling Printed on M2000

R1 interface:
R6 interface:
2013-7-9
Page 89 of 202
INTERNAL
R6 and R3 signaling printed by the GW:
2013-7-9
Page 90 of 202
INTERNAL
5.3 Measurement Counters Related to WiMAX Access

5.3.1 Radio Access Success Ratio
Counter Descriptio n This counter measures the success rate from RNG-REQ to REG-RSP (SUCCESS). Multiple service flows are established, and the number of service flows is uncertain. Therefore, the service flow establishment is not included when the formula of the counter is defined. During network entry, authentication may fail due to factors other than network quality problems (for example, incorrect user name or password). The C03 version also measures the number of network entry failures due to authentication rejection. Therefore, these factors are not involved for counter calculation. This counter is a KPI.
Measurem ent Descriptio n
During initial network entry, the number of initial network entry requests is increased by 1 each time when the system receives an RNGREQ message, as shown in A5. The number of successful initial entry registration times is increased by 1 each time when the system sends an REG-RSP message, as shown in B3. The BS receives a KEY_CHANGE_DIR message carrying the non-zero TLVAuth_Result from the GW, indicating that authentication is rejected. In this case, the number of network entry failures due to rejection of the network side is increased by 1, as shown in E of the figure in section 5.3.4"EAP Authentication Success Rate." Each time when the BS sends an RNG-RSP(Abort) message indicating network exit due to inter-frequency assignment, the number of interfrequency assignment times due to lack of access rights of the MS is increased by 1.
Calculatio n Formula
Radio Access Success Ratio = (Basic capabilities negotiation request times + re-entry network success times from idle)/(initial network entry request times + re-entry network times from idle - Number of Network Entry Failures due to Inter-Frequency Assignment Caused by No Access Permission)*100%
2013-7-9
Page 91 of 202
INTERNAL
The following figure shows the contents of the message in the case of authentication rejection.
2013-7-9
Page 92 of 202
INTERNAL
2013-7-9
Page 93 of 202
INTERNAL
5.3.2 Initial Network Entry Radio Access Success Rate

Counter Descriptio n This counter reflects the success rate of interactions between the MS and the BS (through the air interface) during the network entry process. The initial network entry process lasts from the RNG-REQ message to the SBC-REQ message, whereas the process of network re-entry in idle mode lasts from the RNG-REQ message to the RNG-RSP message. This counter excludes the factors related to the network side (for example, transmission and AAA failure) and reflects the performance of the BS. This counter is a KPI.
Measurem ent Point
During initial network entry, the number of initial network entry requests is increased by 1 each time when the system receives an RNGREQ message, as shown in A5. The number of capability negotiation requests is increased by 1 each time when the system receives an SBC-REQ message, as shown in A7.
Initial Network Entry Radio Access Success Rate = Basic capabilities negotiation request times/(initial network entry request times - Times of entry failure due to no access right and freq. assign)*100%
5.3.3 Basic Capabilities Negotiation Success Rate

Counter Descriptio n This counter reflects the success rate of message interactions between the BS and the GW during capability negotiation. It is not related to the quality of air interface signals. This counter is not a KPI but a counter customized for the daily report to analyze the initial network entry success rate.
Measurem ent Point
The number of capability negotiation requests is increased by 1 each time when the system receives an SBC-REQ message, as shown in A7. The number of successful capability negotiation times is increased by 1 each time when the system sends an SBC-REQ message, as shown in A9.
Basic capabilities negotiation success rate = Basic capabilities negotiation success times/Basic capabilities negotiation request times*100%
2013-7-9
Page 94 of 202
INTERNAL
5.3.4 EAP Authentication Success Rate

Counter Descriptio n This counter measures the successful authentication times starting from the negotiation result in the SBC-RSP message to the receiving of the authentication result delivered in the Key-change-Directive message. It excludes the authentication failures due to rejection by the GW. This counter is a KPI.
Measurem ent Point
During initial network entry of the MS, if the MS and the BS determine to enable authentication through negotiation at the SBC stage, the number of initial authentication times of the MS is increased by 1, as shown in A9. The number of the PKMv2 SA-TEK-Response messages sent by the BS is increased by 1 each time when the BS sends a PKM-RSP message carrying "code = 0x16", as shown in A. If the BS receives a KEY_CHANGE_DIR message carrying the nonzero TLV Auth_Result from the GW, authentication is rejected. In this case, the number of network entry rejections by the network side is increased by 1, as shown in E.
EAP Authentication Success Rate =PKMv2 SA-TEK-Response times sent by BS/(MS originated authentication times-network entry failure due to GW rejecting)*100%
2013-7-9
Page 95 of 202
INTERNAL
5.3.5 DSA Success Rate

Counter Description This KPI measures the probability of successful establishment of service flows. Admission determination is performed again after a DP is established but before the service flow is established. The admission determination at ranging stage is to determine whether the number of current users, number of service flows, and system load exceed thresholds. The admission determination at the service flow establishment stage also includes the load of service flows being established in the load calculation. The BS sends a DSA-REQ message to the MS only after admission is permitted. Therefore, the service flow establishment success rate reflects the success rate of air interface message interactions during service flow establishment, but does not relate to admission control. This counter is a KPI.
2013-7-9
Page 96 of 202
INTERNAL
Measureme nt Point
During initial network entry, the number of service flow establishment requests is increased by 1 each time when the BS sends a DSA-REQ message, as shown in B7. The number of successful service flow establishment times is increased by 1 each time when the BS receives a DSA-RSP message, as shown in B8.
Calculation Formula
DSA Success Rate = service flow setup success times/service flow setup request times*100%
5.4 Further Analysis on Accessibility Counters

5.4.1 Factors Affecting Accessibility Counters
1. Influences of MS Actions on Counter Measurement The WiMAX CPE MS makes call attempts continuously until the call is connected successfully or the MS is switched off. This action increases the failure times. For voice services, however, if a user does not try to set up a voice connection for a while after one or two call failures. As a result, for WiMAX, certain users with poor signal quality try to set up connections continuously, which degrades the entire counter. Additionally, WiMAX supports long online time. Once a user is online, the user does not try to access the network again. Certain users can keep online for seven hours. As a result, the number of successful network entry times decreases. As seen from the formula of this counter, the denominator is smaller. For voice services, however, the online time of users is short, and users with high signal quality can contribute to more successful access times, thus improving the counter. Based on the preceding two points, you can find that few MSs contribute to most failures by analyzing the WiMAX accessibility counters. In addition, if a user accesses the network alternatively between two or more BSs, the network entry success rate is also affected. When the user fails to access the network from BS1 due to authentication rejection, the user selects BS2 with the second highest signal quality to access the network. The signal quality under BS2 is poor, and the SBCREQ or PKM-REQ message may be restricted in the uplink. There is another possibility: When BS2 is still waiting for the SBC-REQ or PKM-REQ message from the MS, the MS already exits the network from BS2 and tries to access the network from BS1. After it fails, the user tries to access the network from BS2 again. In this case, BS2 receives the RNG-REQ message again.
2013-7-9
Page 97 of 202
INTERNAL
2.
Influences of BS Features on Counter Measurement The uplink slot limit function of the BS fragments uplink messages according to the signal quality, thus improving the transmit power of a single sub-carrier. The number of the PKM-REQ message fragments also directly affects the network entry success rate. The poorer the signal quality is, the more the fragments and the less possible the BS receives all the fragments. Loss of any fragment, however, may cause network entry failure. In other words, the probability of network entry success decreases as the number of message fragments increases. Moreover, in the calculation formula of the initial network entry success rate, the number of inter-frequency assignment times of the MS without access rights is removed from the denominator. If the system does not enable the inter-frequency assignment function but enables the admission restriction function, the network entry success rate is decreased. To sum up, the accessibility counters should be treated differently from 2G/3G counters, particularly when KPI commitment is made.
5.4.2 Major Features Improving Accessibility Counters

Feature Name Network access enhancement Configurable allocated bandwidth in CDMA_Allocation_IE Power control AMC timer configurable Uplink slot limit Description Uses MAP, DCD/UCD, and downlink signaling to improve the network entry success rate. Decreases the value of CDMA_Allocation_IE to the number of allocated slots in the initial RNG-REQ message to reduce the probability of the uplink RNG-REQ restriction. Postpones the power control AMC time so that all signaling messages are encoded in QPSK1/2 mode during network entry. Fragments uplink messages to increase the power of a single sub-carrier for signaling transmission and improve the signaling transmission success rate. Is specific to message loss caused by signal jitter. For example, at authentication stage, procedures are long, and PKM signaling messages are large in size and divided into many fragments. In this case, radio environment fluctuations easily cause fragment loss and network entry failure. The management connection HARQ has the feature of handling burst bit errors and can effectively avoid fragment loss. Its basic principle is that management connections use a lower MCS mode than service connections to ensure the reliability. Reduces influences of MSs frequently failing to access the network on the network entry success rate.
Management connection HARQ
Management connection MCS reduction Optimization of network entry success rate measurement
Network Access Enhancement

The network access enhancement feature ensures the reliability of downlink messages through the repetition mechanism, including MAP message repetition (DLMAP/ULMAP), broadcast
2013-7-9
Page 98 of 202
INTERNAL
message (DCD and UCD) repetition, and downlink signaling message repetition (RNG-RSP, SBC-RSP, and authentication messages) at initial network entry. The greater the repetition multiple is, the higher the reliability and the more resources that are consumed. Therefore, the reliability is improved at the cost of resource waste. Currently, the product supports repetition 2, repetition 4, or repetition 6. You can set it according to the actual situation. For example, if signals are weak but downlink resources are sufficient, use repetition 4 or repetition 6. MAP repetition: Currently, the product supports QPSK1/2 repetition 2, QPSK1/2 repetition 4, or QPSK1/2 repetition 6. You can set it according to the actual situation. For example, if signals are weak but downlink resources are sufficient, use MAP repetition 4 or MAP repetition 6. Note that MAP repetition cannot be used in the 5 MHz PUSC 1/3 network due to the limited resources, and should be used with caution in the FFR network. It is recommended to disable MAP repetition unless necessary. When setting the repetition times, you need to consider the network mode and the overhead. The overhead is high when repetition 4 is used. Therefore, MAP repetition should be disabled in normal cases. DCD/UCD repetition: The protocol specifies that the DCD and UCD messages are transmitted on fragmented broadcast connections and can be fragmented. Therefore, DCD and UCD repetition can be used to improve the transmission reliability. DCD/UCD fragmentation must be enabled before DCD/UCD repetition is enabled. By default, fragmentation is enabled but repetition is disabled. DCD/UCD repetition cannot be used in the 5 MHz PUSC 1/3 network. The repetition times should be set according to the actual situation. It is recommended to set repetition 4 at most. If repetition 6 is used, the overhead is very large. DL signaling repetition: It is the repetition mode of downlink signaling messages (such as RNG-RSP, SBC-RSP, PKM-RSP, and REG-RSP) within a certain period before the power control AMC timer expires at the network entry stage, thus enhancing the reliability of downlink signaling. DL signaling repetition cannot be used in the 5 MHz PUSC 1/3 network or FFR network. Repetition 2 can be set at most in the 10 MHz PUSC 1/3 network. The downlink RNG-RSP and SBC-RSP messages are large in length and cannot be fragmented. Therefore, these messages should be transmitted completely in one frame. Based on the available air interface resources, at most repetition 2 can be set in the 10 MHz PUSC 1/3 network; otherwise, the RNG-RSP and SBC-RSP messages cannot be sent completely. Note that the valid time of downlink signaling repetition for initial network entry is controlled by the power control AMC timer. That is, DL signaling repetition for initial network entry is valid only before the power control AMC timer expires. The timer duration is 10s by default. When the timer expires, the uplink/downlink MCS and repetition modes are automatically controlled by the power control AMC algorithm. The following table lists the recommended repetition times for network access enhancement. Networki ng Modes Recommended MAP Repetition Mode Recommended DCD/UCD Repetition Mode Recommended DL Signaling Repetition Mode During Network Entry No repetition No repetition Repetition 2 or no repetition No repetition
FFR 5 MHz 1/3 5 MHz with all 10 MHz 1/3
No repetition No repetition Repetition 2 or no repetition No repetition
No repetition No repetition Repetition 2 or no repetition No repetition
2013-7-9
Page 99 of 202
INTERNAL
Networki ng Modes
Recommended MAP Repetition Mode
Recommended DCD/UCD Repetition Mode
Recommended DL Signaling Repetition Mode During Network Entry No repetition, or repetition 2 or repetition 4, depending on service requirements
10M with all
No repetition, or repetition 2 or repetition 4, depending on service requirements
No repetition, or repetition 2 or repetition 4, depending on service requirements
Configurati MML Command on Description Set MAP repetition Repetition 2:

MOD CARRIERFRAMEINFO: SECTORID=0, CARRIERID=0, FCHRCI=REPETITION2;
Repetition 4:
Repetition 6:
Set DCD/UCD repetition
Enable DCD/UCD fragmentation:

MOD RRMSOFT: PARANO=66, VALUE=1;
No DCD/UCD repetition:
DCD/UCD repetition 2:
2013-7-9
Page 100 of 202
INTERNAL
Set DL signaling repetition
No DL signaling repetition:
MOD OFDMACFG: SECTORID=0, CARRIERID=0, DLINITREPETITION=NOREPETITION;
DL signaling repetition 2:
MOD OFDMACFG: SECTORID=0, CARRIERID=0, DLINITREPETITION=REPETITION-2;
Allocated Bandwidth in CDMA_Allocation_IE Configurable

After code adjustment succeeds, the BS uses CDMA_Allocation_IE to allocate bandwidth for an MS to send the RNG-REQ message. In the current version, CDMA_Allocation_IE indicates the bandwidth allocated for the RNG-REQ message (20 slots by default), mainly to achieve compatibility with old MSs. In fact, most MSs use less than 20 slots to send RNGREQ messages, and the extra slots are padded, resulting in a waste. If too many uplink slots are allocated, the sub-carrier transmit power of MSs becomes low. When MSs are under weak coverage, uplink RNG-REQ messages are restricted. Therefore, the number of slots allocated by CDMA_Allocation_IE can be reduced to improve the transmission success rate of the RNG-REQ messages sent by MSs. Theoretically, the less the slots allocated by CDMA_Allocation_IE, the higher the transmit power of the sub-carrier is. If the allocated bandwidth is insufficient, however, RNG-REQ messages cannot be sent. Additionally, in the case of network re-entry in idle mode, MSs can use IR code or HR code. Therefore, the design of the Slot parameter in CDMA_Allocation_IE should involve the size of the RNG-REQ message in the case of network re-entry in idle mode. The MS test results show that the RNG-REQ message at initial network entry consists of up to 59 bytes (10 slots). Therefore, the bandwidth allocated by CDMA_Allocation_IE can be set to 10 slots. You can set the parameter according to the DL/UL subframe ratio of each site based on the principle that sub-channels required by the RNG-REQ message should be occupied. For example, if the DL/UL subframe ratio is 29:18, change the value of the parameter to 10 slots; if the DL/UL subframe ratio is 31:15, change the value of the parameter to 12 slots. Configuration Description Set the bandwidth allocated by CDMA Allocation_IE. MML Command
Duration of the Power Control AMC Timer at Network Entry Stage

You can set the duration of the AMC validation timer (unit: ms) to ensure the reliability of
2013-7-9
Page 101 of 202
INTERNAL
signaling transmission at the network entry stage and enable all signaling messages including DHCP messages to use QPSK1/2 mode. This timer is started after the RNG-RSP message (it is a response to the RNG-REQ message and the status is "success") is sent. The uplink and downlink AMC does not function before the timer expires. This configuration affects the MCS mode used by the MS, that is, the MS uses the default MCS for initial network entry after the MS accesses the network and before the timer expires. If the value of this parameter is too large, resources are wasted; if the value of this parameter is too small, the network entry success rate is affected. In commercial application, this parameter should be set according to the maximum network entry duration of different MSs. The default value is 10s. It is recommended that you set this parameter according to the following performance counters. For example, if the network entry delay mostly ranges from 10 to 20s, set the timer duration to a little larger value; if the network entry delay of most MSs is within 10s, reduce the value properly. Configuration Description Set the power control AMC parameter at network entry stage. MML Command Set the duration of the power control AMC timer at network entry stage to 10s:
MOD PCAMCPARA: SECTORID=0, CARRIERID=0, AMCENABLETIMELEN=10000;
Uplink Slot Limit

During network entry, if the BS allocates too many uplink slots to the MS, the uplink subcarrier power is low due to restriction of the total power of the MS. As a result, the uplink signals are weak and uplink signaling messages cannot be sent successfully. Therefore, the slot limit algorithm can be used to fragment uplink signaling. The uplink slot limit algorithm calculates the maximum number of slots that can be allocated to an MS per frame dynamically according to the uplink signal quality, avoiding decreasing the sub-carrier power due to too many slots allocated to the MS. This algorithm is enabled by default. You need to set the minimum number of uplink slots before enabling this algorithm. This parameter avoids failure to send uplink data due to the too small number of slots calculated by the slot limit algorithm. Therefore, it is recommended that you set this parameter to the number of slots of two sub-channels, that is, set the value to 8 in the sub-frame proportion of 31:15 or 10 in the sub-frame proportion of 29:18. Set the slot limit algorithm. Enable the uplink slot limit algorithm:
MOD PCAMCPARA: SECTORID=0, CARRIERID=0, SLOTLIMITSWITCH=ON;
Set the minimum number of uplink slots (set it to 8 in the sub-frame proportion of 31:15; set it to 10 in the 29:18 sub-frame proportion, namely, two sub-channels):
MOD PCAMCPARA: SECTORID=0, CARRIERID=0, PCAMCMINSLOT=8;
Set the maximum number of uplink repetition times (up to repetition 2 can be set):
MOD OFDMACFG: SECTORID=0, CARRIERID=0, ULAMCMAXREPETIRION=REPETITION-2;
2013-7-9
Page 102 of 202
INTERNAL
Management Connection HARQ

This feature enhances the reliability of both uplink and downlink signaling. For management connection HARQ, parameters are negotiated at the SBC stage. Management connection HARQ becomes valid at the authentication stage. This feature can be used only when it is supported by the MS. Management Configure management connection HARQ: connection MOD RRMSOFT: PARANO=84, VALUE=201; HARQ
Management Connection MCS Reduction

This feature enhances the reliability of both uplink and downlink signaling. Its basic principle is that management connections use a lower MCS mode than service connections to ensure the reliability. If a frame contains the management message to be sent, the frame data is transmitted in management connection MCS mode; if a frame does not contain the management message to be sent, the frame data is transmitted in service connection MCS mode. Though the Management connection MCS reduction feature improves the reliability of management messages, the coding efficiency is decreased because the lower MCS mode is used. Currently, the product supports order 1 reduction or order 2 reduction. Order 1 reduction is recommended. Note that the Management connection MCS reduction feature is valid only after the power control AMC timer at network entry stage expires. If conditions permit, enable the management connection HARQ in priority. Usually, management connection MCS reduction and management connection HARQ should not be enabled at the same time. Management Configure Management connection MCS reduction: connection MOD RRMSOFT: PARANO=84, VALUE=202; MCS Set the number of reduced orders of the management connection (one order reduction reduced):
Optimization of Network Entry Success Rate Measurement

Based on the current counter measurement, exclude all the failures of illegal MSs (users rejected by the AAA server) from the counter measurement.
2013-7-9
Page 103 of 202
INTERNAL
5.5 General Ideas of Access Success Rate Optimization

5.5.1 Access Success Rate Optimization Process
2013-7-9
Page 104 of 202
INTERNAL
5.5.2 Entire Network Problem Analysis

1. Collect relevant data. Collect performance measurement data by referring to section 2.6.1"Performance Measurement Data." Generate daily performance reports by referring to section 3.3"Generating Daily Performance Reports." Set the M2000 to collect CHR data automatically. For details, see the How to Use the Third-Party to Collect CHR Data.doc. Use the OMStar to analyze user data. Collect other data such as alarms and call logs according to analysis requirements. 2. Analyze daily performance reports to find out top N carriers with low network entry success rate, and then locate the problems by referring to section 5.6"Common Causes of Low Access Success Rate and Analysis Methods." After daily reports are generated by area, check the network access counters on the Network KPI sheet of the daily report of each area to find out the area with the poorest network access counters and have an overall understanding of the network.
Check the success rate in each time segment on the Accessibility sheet of the daily report.
2013-7-9
Page 105 of 202
INTERNAL
Check the Carrier KPI sheet in the daily performance report of each area to analyze the network access rate in each area. Sort the initial network entry success rates in a descending order to obtain the top N carriers with the low network entry success rate, and focus on analyzing the carriers with a network entry success rate lower than 40% (which can be set according to the actual situation). Directly query the network access counters on the Carrier KPI sheet of the daily performance report, including the initial network entry radio access success rate, capability negotiation success rate, and authentication success rate, to check the counter or counters causing the low network entry success rate. Concentrate on analyzing the carriers whose initial network entry radio access success rate is lower than 80%, capability negotiation success rate is lower than 80%, and authentication success rate is lower than 40%. For details, see section 5.6"Common Causes of Low Access Success Rate and Analysis Methods." 3. If problems are not located after the handling operations described in section 5.6"Common Causes of Low Access Success Rate and Analysis Methods" are performed, use the advanced analysis method described in section 5.7"Advanced Analysis Methods" to locate the problems. You can use the advanced analysis method to locate the following problems: The radio access success rate is low, but no admission restriction or interference is found. The authentication success rate is low, but no interference is found. By using the advanced analysis method, you can find out the access failure causes, whether the failure is caused by individual users or all users, and whether the failure is caused by the poor signal quality or other factors. Visit the users whose access fail due to poor signal quality. 4. Use the method described in section 5.8"Difficult Fault Handling" to handle certain exceptions. Use the mentioned method to handle the following problems:
2013-7-9 Huawei Technologies Proprietary Page 106 of 202
INTERNAL
The capability negotiation success rate is low, but the configurations of the BS and the GW are correct without transmission alarms. After advanced analysis, it is found that the uplink SBC-REQ messages of the MSs with high signal quality are restricted, that is, the T9 timer expires. After advanced analysis, it is found that the uplink PKM-REQ messages of the MSs with high signal quality are restricted, that is, the T17 timer expires or the RNG-REQ message is received again during authentication.
5.5.3 Optimization of Top N Carriers

Generally, find out the top N carriers based on daily reports. If the problems cannot be located according to daily reports, use the OMStar to analyze CHR data and find out the top N users for analysis. For certain users (the signal quality is high, but the uplink SBC-REQ or PKMREQ messages are restricted. No transmission alarm is reported, but the GW with correct configuration does not respond to the capability negotiation message), collect data and feedback it to R&D engineers to locate the problems.
The determination conditions of the signal quality can be set according to the actual situation of sites. Usually, the DL CINR should be not less than 10 dB and the DL RSSI should be not less than -80 dBm.
5.6 Common Causes of Low Access Success Rate and Analysis Methods
5.6.1 Analysis
Common accessibility problems can be handled through simple confirmation and handling based on the fault phenomenon reflected in the daily report. See the following table.
2013-7-9
Page 107 of 202
INTERNAL
Phenomena The initial network entry radio access success rate is low. Admission limitation
Common Cause
Subsequent Method Expand the system capacity by adding sites or multiple carriers.
The number of users is limited. The number of service flows is limited. The load is limited.
The T9 timer expires. The SBCREQ receiving success rate is low.
The duration of the T9 timer is too short. The SBC-REQ message is too large. The NI is abnormal (NI density > 10%, NI intensity > -85). Interference exists.
Increase the duration of the T9 timer. Promote MS engineers to simplify the SBC-REQ message. Troubleshoot the failure.
Low capability negotiation success rate
The BS cannot receive the PreAttachment-REQ message returned by the GW.
The configuration of the BS or the GW is incorrect. For example, GWIP and GWID at the BS side are incorrect, BSID and BSIP are not configured at the GW side, or BSID and BTSIP configured at the GW side are incorrect. The service interface links are interrupted. The M2000 reports the IP PATH Disconnect, IP Path in fault, and Ethernet link fault alarms.
Modify the configuration at the BS and/or GW side.
Check whether transmission links are recovered.
The result code field in the Preattachment-RSP message returned by the GW is invalid.
The authentication capabilities of the MS and GW are inconsistent, causing capability negotiation failure. The most possible cause is that the authentication capability of the MS is incorrectly configured. The duration of the T17 timer is too short. The NI is abnormal (NI density > 10%, NI intensity > -85).
Modify the authentication capability at the MS side.
Low authentication success rate
Increase the duration of the T17 timer. Troubleshoot the failure.
2013-7-9
Page 108 of 202
INTERNAL
5.6.2 Low Radio Access Success Rate

Admission Limit
If the initial network entry radio access success rate is low, check whether admission is limited first. Admission limit is further classified into user number limit, service flow number limit, and load limit. Further determine the admission limit type by using the following method. The user number limit means that admission fails when the number of users under the carrier exceeds the upper limit. Run the command LST RRMSOFT: PARANO=85; to query the maximum number of supported users under the carrier. Then, view Maximum Number of Online Users(user)(busy time) and Average Number of Online Users(user)(busy time) on the Carrier KPI sheet of the daily report. Assume that the maximum number of supported users under a carrier is 130. If the preceding two counters are between 120 and 130, the most possible cause is the number of users is limited.
If you can confirm that the number of users is limited, and the maximum number of supported users is small (for example, 100), increase the value properly (for example, change the value to 130). The user number specification of the system varies with sites and is affected by factors such as the number of CQICHs and marketing strategy. If the maximum number of supported users is quite large, urge the customer to add sites or multiple carriers to enlarge the
2013-7-9
Page 109 of 202
INTERNAL
capacity. In factor, when the average number of users per carrier is more than 80, user experience may be not so good. In this case, capacity expansion should be considered. The service flow number limit means that admission fails when the number of service flows exceeds the upper limit. By default, the maximum number supported service flows is 1024 (sum of the uplink and downlink service flows, excluding management connections). The load limit means that admission fails when the current load on the carrier exceeds the threshold. Note that for a BE-only network, the load measured by the system is low, and usually admission failure due to load limit does not occur. For determination of admission limit based on service flow number and load, though MML commands are available to directly query the number of service flows and the load, only the current status of the system can be queried while the data of the previous day cannot be reflected. Therefore, if admission is not rejected due to user number limit, you need to check whether admission is rejected due to service flow number limit or load limit. In this case, you can collect admission and load performance measurement data to check whether initial network entry failure due to system overload or admission failure due to system specification limit occurs. You can also collect call logs for analysis. Call logs record the detailed admission failure causes. Despite the admission limit type, we need to urge the customer to add sites or multiple carriers to expand the capacity. Therefore, we only need to whether admission is limited. In addition to the preceding methods, you can also use the original performance measurement data at network entry to calculate the initial ranging success rate to determine whether admission is limited. Initial ranging success rate = initial ranging success times/ initial network entry request times. Generally, if the initial ranging success rate is less than 100%, admission may be limited. There are still exceptions. For example, the BS returns a RNG-RSP(abort) message after receiving the RNG-REQ message due to other factors. In this case, you can obtain the original performance measurement data related to admission or call logs for further confirmation. If the initial ranging success rate is 100%, there must be no admission limit. The only cause is that the uplink SBC-REQ message is limited. In this case, you do not need to perform admission limit determination but directly proceed according to the descriptions in "Uplink SBC-REQ Limit."
Uplink SBC-REQ Limit

If there is no admission limit, the initial network entry radio access success rate must be affected due to uplink SBC-REQ limit. In this case, for V3R2C03SC205 and later versions, run the command LST BSCFG; to check the value of T9Timeout and determine whether the T9 timer is too short. The default value of the T9 timer is 5000 ms. It takes about 90 ms for MSs to retransmit the SBC-REQ message. Certain MSs can retransmit the SBC-REQ messages for 16 times at most. Therefore, the T9 timer should not be less than 1500 ms so that MSs have enough time to retransmit the SBCREQ message. If the T9 timer is less than 1500 ms, it is recommended that you change the value to 1500 ms. If the T9 timer is normal, check the NI density and NI intensity of the carrier on the Carrier KPI sheet of the daily report. If the NI density is more than 10% and/or the NI intensity is more than -85 dB, the uplink SBC-REQ is limited due to interference and troubleshooting is required. If no interference exists, perform further analysis by using the advanced analysis method described in section 5.7"Advanced Analysis Methods."
2013-7-9
Page 110 of 202
INTERNAL
In addition, you can trace single user signaling to check the size of the SBC-REQ message and determine whether the overlarge SBC-REQ message occupies too many sub-channels and causes uplink limit. Generally, the size of the SBC-REQ should be controlled so that the message can be transmitted through two or three sub-channels. The number of sub-channels occupied by the SBC-REQ message can be calculated as follows: check the number of bytes of the SBC-REQ message through signaling trace. Assume that the number of bytes of the message is 54. Then, the total number of bytes is 64 (plus the 10 bytes of the MAC header and CRC). Each slot can carry 6 bytes. Then, a total of 11 slots are required to carry 64 bytes. If the sub-frame proportion is 31:15, there are 15 symbols in the uplink, that is, there are still 12 symbols in addition to the three symbols occupied by the uplink common zone. The number of slots on each sub-channel is 4. Then, three sub-channels are required for 11 slots. If more than three sub-channels are required for the SBC-REQ message, promote MS engineers to simplify the SBC-REQ message.
5.6.3 Low Capability Negotiation Success Rate

Incorrect Configuration of the BS or GW
When the capability negotiation success rate is 0, check first whether the configuration of the BS and the GW is correct. If the configuration is incorrect, the GW does not process the message. There was a case that the GW does not respond to the pre-attachment-REQ message sent by the BS because the BS configuration is not added at the GW side. In this case, run the MML command LST GWIP at the BS side to check whether GWIP and GWID configured at the BS side are correct. Alternatively, run the MML command LST LBS at the GW side to check whether the BS and BTSIP configured at the GW side are correct.
R5 Traffic Link Interruption

When the capability negotiation success rate is low or even 0, check transmission alarms to determine whether the IP PATH Disconnect, IP Path in fault, and Ethernet link fault alarms are reported. These alarms affect R6 interface service interactions, including the R6 interface message interaction during capability negotiation. If these alarms are reported, transmission failure causes the low capability negotiation success rate.
2013-7-9
Page 111 of 202
INTERNAL
In this case, you can run the Ping command at the GW side to check whether links are restored. Note that the traffic interface IP address (namely, the signaling interface IP address) instead of the maintenance interface IP address of the BS should be pinged. Pinging the IP address of the traffic interface can show whether the transmission links between the BS and the GW are normal. Pinging the IP address of the maintenance interface can show only whether the links between the BS and the M2000 are normal. You can run the command LST SIGCH to query the IP address of the traffic interface and run the command LST OMCH to query the IP address of the maintenance interface. If the links are not restored, ask transmission personnel to locate the problem. If the configuration of the BS and the GW is correct and no transmission alarms are reported, the possible cause is that transmission failure intermittently occurs but transmission alarms are not generated, or the BS or the GW is faulty. In this case, collect relevant data by referring to section 5.8"Difficult Fault Handling", and send the data to R&D engineers for problem locating.
5.6.4 Low Initial Authentication Success Rate

Interference
The authentication success rate is low usually because the uplink PKM-REQ message is lost due to the poor signal quality. Therefore, when the authentication success rate is low, you can check the NI density and NI intensity of the carrier in the daily report to determine whether interference exists. That is, check the NI density and NI intensity of the carrier on the Carrier KPI sheet of the daily report. If the NI density is more than 10% and/or the NI intensity is more than -85 dB, interference causes the low authentication success rate and troubleshooting is required.
Improper Setting of the T17 Timer

If the T17 timer is too short, authentication may fail. You can run the command LST CCMTIMER to check the No.4 timer in group 0. The default value of this timer is 5 minutes.
2013-7-9
Page 112 of 202
INTERNAL
If the value of this timer is too small, for example, 1 or 2 minutes, modify it to 5 minutes. If no interference is found, and the T17 time is set properly, perform further analysis by using the advanced analysis method described in section 5.7"Advanced Analysis Methods."
5.6.5 Other Failures in the Network Entry Procedure

The analysis focuses on the initial radio access, SBC, and authentication stages to locate the low access success rate. In fact, however, failures at other stages of the network entry procedure such as registration, service flow establishment, and DHCP may also cause access failure. The service flow establishment success rate can be viewed directly through the daily report. The registration success rate should be calculated according to the original performance measurement data at network entry. Currently, the DHCP cannot be measured because DHCP messages are sent as data instead of signaling. The product does not support measurement of DHCP messages. The registration success rate and service flow establishment success rate in fact reflect the air interface signal quality. Therefore, if these two counters are low, you can locate the problem by using the method for locating uplink SBC-REQ limit and uplink PKM-REQ limit. That is, query the NI density and NI intensity in the daily report to determine whether interference exists. If no interference exists, use the advanced analysis method, that is, use the OMStar to analyze CHRs to find out specific cause values and top N users and analyze the signal quality of these users.
5.7 Advanced Analysis Methods

You can find out the faulty carriers and solve most problems by using the methods described in section 5.6"Common Causes of Low Access Success Rate and Analysis Methods" based on daily performance reports. If the cause of the low network entry success rate cannot be located, use the OMStar to analyze CHRs or use the AAT to analyze call logs for further analysis. If the cause is located and you need to obtain the user-level information, you can use the advanced analysis methods described in this section to analyze the CHRs or call logs.
5.7.1 Analysis of Network Entry Error Codes

Start the OMStar, select Failed Network Access Analysis, select the objects to be analyzed, and then select the analysis granularity as required. You can perform analysis based on GW, site, sector, or carrier. After analysis, you can obtain the number of network access attempts, number of failed network access times, rate of failed network access, and number of failed network access error codes, as shown in the following figure.
2013-7-9
Page 113 of 202
INTERNAL
Right-click an error code. The corresponding cause value is automatically displayed.
The following figure shows the common network entry error codes and the counters that may affect the network entry success rate.
2013-7-9
Page 114 of 202
INTERNAL
The following describes error code 1612972047. In many scenarios, the BS may receive the RNG-REQ again. In this case, you should check the SubState parameter for the error code to determine at which stage the RNG-REQ message indicating that the MS re-enters the network is received. If SubState is 2, the MS exits the network and then enters the network again while the BS is waiting for the SBC-REQ message. If SubState is 3, the MS exits the network and then enters the network again when the GW does not respond to the PreAttachment-RSP message. If SubState is 4, the MS exits the network and then accesses the network again during authentication. Currently, however, the product does report the error code 1612972047 generated during network entry to the OMStar. Therefore, the OMStar does not provide the analysis results about this error code. Rectification is made in the C03SPC500 version. Currently, if you need to query the substate of the error code 2047, you can use only the AAT to analyze call logs and query the substate among the detailed data. See the following figure.
5.7.2 Analysis of Top N Users

Based on the preceding daily report analysis results, you can select the top N carriers and analyze them one by one to avoid increasing the difficulty in differentiating users due to the
2013-7-9
Page 115 of 202
INTERNAL
mixed data of multiple carriers. You can view the top N MSs with the low network entry success rate under the carrier on Analysis of User Detail, and thus determine whether the network entry failure is caused by continuous attempts of individual users or by most users. You can also determine the causes of network entry failure.
You can select an error code and then sort the MSs in a descending order. Then, you can obtain the top N MSs based on the error code.
2013-7-9
Page 116 of 202
INTERNAL
5.7.3 Analysis of User Signal Quality

Uplink SBC-REQ limit and uplink PKM-REQ limit are mainly related to the air interface signal quality, and the relevant error codes include 1612972087, 1612972181, and 1612972047. You should analyze the signal quality of the top N MSs with these error codes to determine whether network entry fails due to the poor signal quality or other factors. You can right-click the MAC address of a MS, and then select Detail Data from the shortcut menu to check the network entry details of the MS including the failure cause and signal quality.
2013-7-9
Page 117 of 202
INTERNAL
2013-7-9
Page 118 of 202
INTERNAL
As shown in the preceding figure, there is no corresponding valid signal quality next to the error codes 1612972087 and 1612972181. For fixed-line users, the signal quality should be similar. Therefore, you can refer to the signal quality of other error codes. When observing the signal quality, you also need to check the BSID to determine whether the signal quality decreases because the MS changes the BS. For mobile users, the signal quality may be always changing. If there is no signal quality corresponding to a certain error code, you cannot use the signal quality corresponding to other error codes as a reference. In this case, you cannot know about the signal quality when network entry fails. For signal quality, several cases exist. A user is at the edge of a cell and the signal quality is always quite poor. The signal quality of a user is usually good, but the CINR drops abruptly in the case of sudden interference, and the BS cannot receive the uplink messages sent by the MS. Or, after several failed attempts to access the network from a carrier (for example, because of authentication rejection), a user then tries to access the network from another carrier where the signal quality is poor, and the access fails again. Due to the unreasonable implementation of the product, the error code 2047 generated during network access is recorded into only call logs but not recorded into CHRs. Therefore, you need to collect call logs to analyze the top N carriers with the low initial network entry radio access success rate and low authentication success rate. You can also obtain the signal quality information about users by analyzing call logs. Note that the signal quality is recorded next to the error code 2047 in the call logs. Sometimes, however, you can find that the signal quality is recorded next to the error code 2047. This may be a bug of the product. Therefore, when analyzing the signal quality, do not use the signal quality recorded next to the error code 2047 as a reference. For users whose network entry success rate is low due to the poor signal quality, return visits
2013-7-9
Page 119 of 202
INTERNAL
can be paid and measures such as MS antenna adjustment can be taken to improve the signal quality, thus improving the network entry success rate. If the signal quality of most MSs under a carrier is poor, consider adding sites to optimize coverage. If the signal quality of the user is normal (downlink CINR > 10 dB, RSSI > -80dBm), but the error code 1612972047, 1612972087, or 1612972181 is still returned, exceptions may exist. Handle the exceptions according to the methods described in section 5.8"Difficult Fault Handling."
5.8 Difficult Fault Handling

5.8.1 Overview
The network access failure is quite complex and involves a large number of NEs. Therefore, you should collect various data completely and feed back it to R&D engineers for analysis and locating. 1. Find out the MSs that fail to access the network. The MSs failing to access the network are as follows: MSs that return the error code 1612972047, 1612972087, or 1612972181 though the signal quality is normal (downlink CINR > 10 dB, RSSI > -80dBm); MSs that return the error code 2140 though there are no transmission alarms or incorrect configuration; or MSs that are complained by users or are used for recurrence tests. 2. 3. 4. 5. 6. Perform single user signaling trace at the BS side and at the GW side. Collect network access data from the DSP at the BS side. For onsite tests, print the logs of the MS or the logs of the DT software at the MS side. After the fault recurs, collect the CHRs or call logs from the corresponding BS. Feed back the data collected in steps 2, 3, 4, and 5 to R&D engineers.
5.8.2 Method for Collecting Network Access Data from the DSP
To obtain the network access data from the DSP, do as follows: 1. Set the MS to collect data at the BS side. Query the maintenance interface IP address of the BS (by running LST OMCH). Start the Internet Explorer and enter the maintenance interface IP address in the address box to log in to the maintenance GUI of the BS. Then, run the command SET MSID and enter the MAC address of the MS to enable the function of capturing network entry data. After the setting is complete, you can run the command DSP MSID to check whether the MAC address of the MS is set correctly. 2. Export the data obtained from the DSP after network entry fails. Run the following command:
EXP DATAFILE:rackno=0,subrackno=0,boardno=3,filetype = "dsp_cap";
Then, start the FTP tool and set the user name, password, and path. The data obtained from the DSP is saved to the set path.
2013-7-9
Page 120 of 202
INTERNAL
Run the following command to obtain the data: ULD FILE: SRCF="dsp_cap", CN=0, SRN=0, SN=3, DSTF="data", IP="10.4.1.213", USR="admin", PWD="admin"; (Note: The last three items should be set according to the actual situation. These items indicate the IP address, user name, and password of the server and should be consistent with those set on the FTP server.) 3. Delete the MAC address of the MS. After the data is obtained, run the command DEL MSID to delete the setting of the MS. Note that all the preceding operations should be performed after login to the maintenance interface of the BS through the Internet Explorer. Verification results show that the commands directly executed on the M2000 do not take effect. In addition, data capture automatically stops after five unsuccessful network access attempts. Therefore, if you need to capture data after five failed attempts, you need to delete the MSID and perform the setting again according to the preceding method.
5.8.3 Logs at the MS Side

During onsite test, you can print the logs of the MS. The logs of the MS can be used to determine whether the MS receives the response message sent by the BS and whether the MS sends a request message after receiving the response message, thus determining whether the MS or the BS is faulty. For the GCT MS, directly enter q in the command window. The MS automatically saves the logs to the Temp folder in C:\. For the BM MS, run the following commands:
cmd cmd cmd cmd cmd cmd cmd cmd set cmd cmd cmd clearsniffer createsniffer,type=mac,mac=+PKM_REQ,dir=tx createsniffer,type=mac,mac=+PKM_RSP,dir=rx enablesniffer,100 filter,+RNGS filter,+UMSS filter,+UPCS filter,+SBCS wimax-log on startss dlmap mmd:detail
2013-7-9
Page 121 of 202
INTERNAL
cmd cmd cmd cmd cmd cmd cmd
mmt:detail showrftx showrftx dlmap showssp showss stopss
Certainly, the specific operations may change with the versions of MSs. For details, see the operation guides of specific MSs.
5.9 Appendix
5.9.1 Cases
Currently, most MSs support optimal frequency selection and automatic frequency selection. When an MS enters the network, it selects a frequency channel with high signal quality. Upon the network entry failure due to non-BS factors such as AAA rejection, the MS selects a frequency channel with poor signal quality, but it fails to enter the network. This procedure repeats and a large number of failures occur. Bangla Office: Problem Description: The network entry success rate cannot reach 90% due to non-BS factors or transmission and MS failure. As seen from logs, the signal quality is good without other problems, but a large number of network entry failures exist. Cause Analysis:
With the increase of authentication failures, more and more T9 timer timeout and authentication failures due to non-AAA authentication rejection occur and the overall network entry success rate drops. Log records show that more T9 timer timeout and non-AAA
2013-7-9
Page 122 of 202
INTERNAL
authentication failures (that is, the RNG-REQ messages are received again) occur after MSs fail to be authenticated under a carrier with good signal quality. Cause Description:
1. 2.
The MS selects sector A with strong signals to access the network, but authentication fails (due to defaulting or non-BS factors). The log records the signal quality of sector A. The MS tries to access the network from sector B with weak signals, which may cause T9 timer timeout. Because of the weak signals, the signal quality may fail to be reported and is not recorded into logs. If the T9 timer does not time out and the SBC succeeds, the authentication stage starts. At this stage, however, authentication messages are lost due to the poor quality of signals, large size of messages, and large number of fragments. The MS waits for the authentication timer (T17) timeout and BS exit. The MS accesses the network from sector A again, but authentication still fails (non-BS factors can be excluded through performance measurement). The log records the signal quality of sector A again. After authentication fails, the MS tries to access the network from sector B. In this case, the T17 timer does not time out, and the resources for previous network entry of the MS are retained. After receiving the RNG-REQ message, the BS considers that another RNG-REQ message is received, and the network entry fails (the cause is that the MS tries to access the network from sectors B, A, and then B again within only one minute). The signal quality fails to be reported and is not recorded into logs. The AAT records the average signal quality instead of the signal quality of specific carriers. Therefore, from the logs analyzed from the AAT, you can find that the radio
3.
4.
5.
6.
2013-7-9
Page 123 of 202
INTERNAL
environment is good but a large number of T9 timer timeouts occur and RNG-REQ messages are received again. To solve the problems, take the following measures: Optimize performance measurement counters. That is, delete all failures of illegal MSs (namely, the failed users rejected by AAA server) from the counter measurement. Optimize MSs. That is, enable the MSs not to select the secondary optimal frequency channel for network entry attempts in case of AAA rejection. Preventive measure for BS: Postpone network entry of the MSs with such problems. This function will be available in V3.3.

Document Name Content Application Scenario Common problem troubleshooting and configuration check
DBS3900 V300R002C03 Describes the principles, network Access Feature Principles and evaluation, relevant configuration, Application Guide.doc and test application of the access feature.
2013-7-9
Page 124 of 202
INTERNAL
6
1. 2. 3.
Retainability Optimization

This chapter briefly describes some features and parameters related to retainability based on the retainability counters. It focuses on how to discover and solve problems based on daily performance reports, and provides guidance for further analysis and handling of difficult problems. After completing this chapter, WiMAX engineers should be able to understand the retainability KPIs, and reach the following requirements: WiMAX engineers are able to analyze and solve common network drop problems independently. Some engineers with powerful technical skills are able to use the OMStar and AAT to analyze and solve high-level performance problems related to network drop. WiMAX engineers are not required to solve difficult problems independently, but they must know how to collect relevant data. Technical engineers should be able to collect relevant data and return it to R&D engineers to analyze and locate problems.
6.2 Retainability Evaluation Counters

6.2.1 Network Disconnection Ratio
Counter Name Formula Network Disconnection Ratio Before SPC500: Network Disconnection Ratio = The Times of MS Dropped from Network/(Online user number at the end of measurement period + The Times of MS Dropped from Network + Deregistration times due to MS + Deregistration times due to gateway + Deregistration times due to OM + Deregistration times from handoff source BS)*100% After SPC500: Network Disconnection Ratio = The Times of MS Dropped from Network/(Online user number at the end of measurement period + The Times of MS Dropped from Network + Deregistration times due to MS + Deregistration times due to gateway + Deregistration times due to OM + Deregistration times from handoff source BS + Times of Deregistration due to MS Power-Off)*100%
2013-7-9
Page 125 of 202
INTERNAL
Description Network Disconnection Ratio indicates the ratio of abnormal disconnections of MSs from the network. The normal network exit actively initiated by MSs is not calculated as network drop. The reason for differentiating abnormal drop and normal disconnection is that the real network quality cannot be reflected when MSs actively disconnect from the network, or MSs are disconnected from network through manual execution of commands or due to GW problems. Therefore, these cases are not included in abnormal disconnection measurement. Unit Reference Value % < 7%
6.2.2 Online Duration per Drop

Counter Name Formula Online Duration per Drop Before SPC300: Online Duration per Drop = Carrier MS Online Duration / The Times of MS Dropped from Network*60 After SPC300: Online Duration per Drop = Carrier MS Online Duration / The Times of MS Dropped from Network*1000*60 Descriptio n This counter defines the ratio of MS online duration to times of abnormal drop, namely, the interval of MS disconnection from network. Only the number of abnormal disconnection times is included in the measurement, while the number of active exit times of MSs is not included. The unit of the MS online duration is millisecond. Therefore, (1000 x 60) in the denominator is used to convert the result into minute. The online duration per drop can accurately represent the interval at which the MS disconnects from the network. This counter is more important for data services because a data service user may be online for a long time while a common voice service user is online during a call but hangs up after the call ends. In this sense, the call drop rate of the data service user is higher, but this problem can be avoided if the online duration pre drop is used. Unit Reference Value Minute > 250
6.2.3 Average Retain Duration of No Abnormal Interrupt

In addition to the preceding two retainability KPIs, a non-KPI counter, namely, Average Retain Duration of No Abnormal Interrupt, is defined for internal evaluation only. This counter is not provided for customers.
2013-7-9
Page 126 of 202
INTERNAL
Counter Name Formula
Average Retain Duration of No Abnormal Interrupt Before SPC300: Average Retain Duration of No Abnormal Interrupt = Carrier MS Online Duration / ((Times of MS Disconnection from Network - Times of Deregistration due to Handover Failure + (Times of Handover Execution Triggered by MS - Number of Ready Incoming Handover Ranging Requests) + (Number of Ready Incoming Handover Ranging Requests + Number of Unready Incoming Handover Ranging Requests - Times of Completing Incoming Handover)) * 60) After SPC300: Average Retain Duration of No Abnormal Interrupt = Carrier MS Online Duration / ((Times of MS Disconnection from Network - Times of Deregistration due to Handover Failure + (Times of Handover Execution Triggered by MS - Number of Ready Incoming Handover Ranging Requests) + (Number of Ready Incoming Handover Ranging Requests + Number of Unready Incoming Handover Ranging Requests - Times of Completing Incoming Handover)) * 1000 * 60)
Descriptio n
For mobility data services, MSs may drop from the network due to handovers. Disconnection in this scenario is treated as abnormal disconnection. This counter is similar to the online duration per drop but involves the disconnection caused by handovers. Minute > 250
Unit Reference Value
6.3 Further Analysis on Retainability Counters

6.3.1 Influences of WiMAX User Behaviors on Retainability Counters
Currently, the major services on the WiMAX network are data services. The biggest difference between the data service and the voice service is that data service users are online for a longer time than voice service users. That is, on the pure voice service network (for example, GSM or CDMA network), the process starting from number dialing to the end of the call is basically within the same measurement period. Though a limited number of calls across measurement periods, the network disconnection ratio is quite clear on this kind of networks. Moreover, on the pure voice service network, users hang up normally after calls end. In this case, the network can detect that MSs exit the network. For the WiMAX network, however, MSs are CPEs and USB dongle, and users usually exit the network by directly plugging, unplugging, or powering off MSs. MSs seldom exit network actively. In this scenario, the network side cannot detect the network exit behaviors of MSs, and thus calculate these behaviors as abnormal exits. As a result, most normal exits are treated as abnormal exits, which makes the network disconnection ratio worse. Due to the particularity of WiMAX services, it is not suitable to use the counters defined for the pure voice service network. Therefore, the WiMAX network disconnection ratio should involve not only the disconnection caused by various factors but also the number of users at the beginning or the end of the measurement period. Otherwise, the real network
INTERNAL
disconnection ratio cannot be obtained. With this counter, it can indicate the proportion of network drop of all network entry MSs within the measurement period. Another counter that presents the retainability of WiMAX services is the online duration per drop. This counter converts the number of disconnection times into the interval of abnormal exits and indicates the interval at which disconnection occurs, thus showing the retainability on the network more effectively. For details, see the WiMAX Retainability KPI Baseline Guide.
6.3.2 Features and Parameters Affecting Retainability Counters

Feature Name Network drop detection Description In versions earlier than V32C03SPC500, the network drop detection feature does not differentiate the MS plugging/unplugging and poweroff scenario from the abnormal disconnection scenario. Therefore, the measurement result of abnormal disconnection ratio is rather high. This feature improves the reliability of management connections.
Management connection HARQ enable or Management connection MCS reduction Uplink slot limit
This feature implements slot allocation adjustment based on radio channel changes, increasing the power of a single sub-carrier in data transmission. When ARQ is enabled, if the sliding windows at the transmitter and receiver ends are not synchronized, the BS initiates reset. When the number of unsuccessful resetting times reaches the threshold of CCMTHES No.8 (namely, the retransmission times threshold of T22, which is 30 by default), the BS enables the MS to exit the network. If HARQ and HARQ-based outer loop are enabled for service connections while HARQ or MCS reduction is not enabled for management connections, the reliability of management connections decreases and ARQ reset failures may be much more obvious. This feature improves the reliability of broadcast messages such as MAP, DCD, and UCD and accordingly reduces network drop of MSs due to loss of MAP messages. Online MSs need to be re-authenticated to verify their validity. The reauthentication period is delivered by AAA.
ARQ reset mechanism
MAP/DCD/UCD repetition Re-authentication
2013-7-9
Page 128 of 202
INTERNAL
Feature Name Idle feature
Description When there is no data transmission, the MS can enter idle mode, and the BS releases all the air interface resources of the MS. When there is data transmission, the MS can exit the idle mode, and service connections are resumed. The MS enters the idle mode, which is considered as a kind of normal network exit of the MS and is treated as the denominator of the calculation formula of the network disconnection ratio. Therefore, when the idle feature is enabled, the number of normal exits of the MS can be increased, thus decreasing the network disconnection ratio. When the MS detects a neighbor cell where signal quality meets the requirement, the MS hands over to the TBS. From the aspect of the SBS, the MS initiates a normal exit. The SBS releases the resources after the handover, which is considered as a kind of normal network exit of the MS and is treated as the denominator of the calculation formula of the network disconnection ratio. Therefore, when the HO feature is enabled, the number of normal exits of the MS can be increased, thus decreasing the network disconnection ratio.
HO feature
Network Drop Detection

The network drop detection mechanism has two major purposes. One purpose is that the BS requires a certain detection mechanism to adapt to use habits of WiMAX network users (that is, users directly plugging/unplugging or power off MSs) so that the BS can release system resources in time after the MSs exit the network. The other purpose is that the BS initiates the MS exit procedure in special scenarios (for example, the MS is in exceptional status) so that the MS can access the network again. The BS determines that the MS has disconnected from the network when the uplink error packet ratio of the MS is greater than the detection threshold (90% by default) within the detection period (60000 ms by default). Two parameters control the determination of network drop detection, namely, disconnection detection period and disconnection detection threshold. The longer the disconnection detection period is, the more accurate the determination is. In this case, however, system resources cannot be released in time, which may cause resource waste. If the disconnection detection period is shorter, system resources can be released in time, but the MS may be improperly determined as disconnected from the network due to burst error packets. The value of the disconnection detection threshold has similar effects as the value of the disconnection detection period. Generally, the disconnection detection threshold should be not less than 90% and the disconnection detection period should be not more than one minute. Commands for querying and modifying the disconnection detection period: Query command: LST RRMTIMER: TIMERNO=3 Modification command: MOD RRMTIMER: TIMERNO=3 Commands for querying and modifying the disconnection detection threshold: Query command: LST RRMSOFT: PARANO=17 Modification command: MOD RRMSOFT: PARANO=17
2013-7-9
Page 129 of 202
INTERNAL
The two parameters can take effect without the need to deactivate and then reactivate the sector.
Management Connection HARQ Enable or Management Connection MCS Reduction

Management connection HARQ and Management connection MCS reduction are used to improve the reliability of management connections but both have limitations. Management connection HARQ should be supported by MSs (currently, most MSs passing IOT tests support this feature except those earlier versions). For Management connection MCS reduction, however, the transmit power of the MS decreases after MCS reduction according to new protocol specifications. Though the BS performs power compensation after MCS reduction, the transmit power of the MS is further limited as more uplink resources are allocated. Therefore, the improvement of MCS reduction on the reliability of uplink management connections is not very obvious (MCS reduction can improve the reliability of only downlink management connections). This function is controlled by software parameter P84. P84 controls multiple performance algorithm switches. Bit 0 of P84 controls management connection HARQ. When bit 0 is set to 0, management connection HARQ is disabled; when bit 0 is set to 1, management connection HARQ is enabled. Bit 1 of P84 controls Management connection MCS reduction. When bit 1 is set to 0, Management connection MCS reduction is disabled; when bit 1 is set to 1, Management connection MCS reduction is enabled. Currently, the recommended value of P84 is the decimal number 201 that can be converted into the binary number 11001001, that is, management connection HARQ is enabled while Management connection MCS reduction is disabled (the least significant bit is bit 0). Query command: LST RRMSOFT:PARANO=84 Modification command: MOD RRMSOFT:PARANO=84 The modification can take effect without the need to activate or deactivate the sector (the MS needs to enter the network again to enable management connection HARQ).
Uplink Slot Limit

If too many uplink resources are allocated, the transmit power of MSs is limited, a large number of uplink error packets are generated, thus affecting service transmission and easily triggering the disconnection detection mechanism to make MSs exit. The uplink slot limit feature is used to avoid such problems. Uplink slot limit is controlled by the switch and enabled by default. As a basic function, uplink slot limit should not be disabled. Additionally, the AMC out threshold configured in each uplink MCS is used for calculating the allocated slots. Therefore, the uplink AMC threshold should use the default setting of the version in normal cases. To query the uplink slot limit switch, run the command LST PCAMCPARA. To modify the uplink slot limit switch, run the command MOD PCAMCPARA: SLOTLIMITSWITCH=ON; The parameter can take effect without the need to activate or deactivate the sector.
ARQ Reset Mechanism

If ARQ is enabled, the reset procedure should be initiated if the ARQ state machines of the receiver and transmitter are lost synchronously according to protocols. The reset procedure can be either initiated by the transmit end or the receive end, but both should receive the ACK
2013-7-9
Page 130 of 202
INTERNAL
message. T22 is a timer exclusively used to wait for the ACK message in the case of resetting. The maximum value of the T22 timer is 0.5s according to protocols. If resetting still fails after the maximum number of resetting times is reached, the system determines that the MS is faulty, and thus releases all the resources of the MS. Currently, the T22 timer duration (500 ms by default) and the maximum number of resetting times (the suggested value is 30) can be configured. Commands for querying and modifying the T22 timer duration: Query command: LST MSCFG; Modification command: MOD MSCFG: T22TIMEOUT=500 Commands for querying and modifying the maximum number of resetting times: Query command: LST CCMTHES: THRESHOLDTYPE=8 Modification command: MOD CCMTHES: THRESHOLDTYPE=8
MAP/DCD/UCD Repetition
Under weak coverage areas or on the network where downlink co-frequency interference exists, an MS may lose the broadcast messages such as MAP, DCD, and UCD and disconnect from the network due to message decoding failure. The MAP/DCD/UCD repetition is intended to improve the reliability of these broadcast messages through repetitive encoding. MAP repetition is indicated by the FCHRCI parameter. DCD/UCD repetition is indicated by software parameter P70. Repetition improves the reliability of messages but brings about greater resource overhead. Therefore, the parameter should be set flexibly according to the networking mode. Usually, in the 10 MHz PUSC with all SC networking mode, repetition 2 is enabled; in other networking modes, repetition is disabled. For details, see the DBS3900 V300R002C03 Access Feature Principles and Application Guide. Commands for querying and modifying MAP repetition: Query command: LST CARRIERFRAMEINFO; Modification command: MOD CARRIERFRAMEINFO:FCHRCI=REPETITION-2 Commands for querying and modifying DCD/UCD repetition: Query command: LST RRMSOFT:PARANO=70 Modification command: MOD RRMSOFT:PARANO=70 The parameter modification can take effect only after the sector is activated or deactivated.
Re-authentication
The CN side needs to re-authenticate online MSs to verify their validity. The re-authentication period is delivered by AAA. Due to multiple signaling interactions and certain large-size messages in the re-authentication procedure, messages may be easily lost and reauthentication may fail when the air interface signal quality is poor. As a result, the MS may disconnect from the network. Correspondingly, the shorter the re-authentication period is, the more times that the MS may disconnect from the network due to re-authentication failure, and the greater the network disconnection ratio is. If the re-authentication period is not limited, it is recommended to extend the period to 12
2013-7-9
Page 131 of 202
INTERNAL
hours or even disable re-authentication. This parameter is set at the AAA side.
Idle Feature
When there is no data transmission, the MS can enter idle mode, and the BS releases all the air interface resources of the MS. When there is data transmission, the MS can exit the idle mode, and service connections are resumed. According to the definition of the network disconnection ratio, this counter measures the percentage of the number of abnormal network drop times to the total number of network drop times. Due to the particularity of data services, there are few normal disconnections of WiMAX network users. After the idle feature is enabled, the BS can count it as normal disconnection when the MS enters the idle mode normally. In this case, the denominator in the calculation formula of the network disconnection ratio is increased, and thus the network disconnection ratio is decreased. For an MS without services, it releases the resources and disconnects from the network after the idle feature is enabled, thus reducing the total online duration of the MS and decreasing the online duration per drop. To enable the idle feature, you need to set the duration of the timer for entering idle mode initiated by the MS or the BS in addition to network planning parameters such as paging group and paging period. This parameter also has certain impacts on the network disconnection ratio. The shorter the idle duration initiated by the MS or BS is, the more frequently the MS enters the idle mode, the more normal disconnection times measured by the BS, and the smaller the network disconnection ratio is. If the idle duration is too short, however, service data may be transmitted before the MS enters the idle mode. In this case, the idle feature does not function. In addition, failure may occur and the MS may disconnect from the network if the MS enters or exits the idle mode too frequently. Therefore, the idle feature is enabled to reduce the usage of air interface resources, instead of reducing the network disconnection ratio. Relevant parameters should be determined according to the actual situation. The timer for entering the idle mode initiated by the MS is determined by the MS and cannot be controlled by the BS. The timer for entering the idle mode initiated by the BS is set by P55. The default value is 180s. Commands for querying and modifying the timer for entering the idle mode initiated by the BS: Query command: LST RRMSOFT:PARANO=55 Modification command: MOD RRMSOFT:PARANO=55
HO Feature
After the MS detects a neighbor cell meeting the signal quality condition, it initiates handover to the TBS. In this case, for the SBS, the MS initiates a handover and disconnects from the network normally. Therefore, the denominator in the calculation formula of the network disconnection ratio is increased, and the network disconnection ratio is thus reduced indirectly. Note that the HO feature is intended to enable MSs to be served under sectors with high signal quality, instead of reducing the network disconnection ratio. Relevant parameters should be determined according to the actual situation. This document describes only the influences on the network disconnection ratio after the HO feature is enabled. You are advised not to modify the parameters to make MSs initiate HOs frequently to increase the number of normal disconnection times.
2013-7-9
Page 132 of 202
INTERNAL
6.4 Common Fault Handling

This section describes the common scenarios of high disconnection ratio, how to analyze the possible causes through the daily performance report, and how to handle the problems. The number of network drop times is used as the numerator in the calculation formula of the network disconnection ratio, and used as the denominator in the calculation formula of the online duration per drop. In addition, the number of network drop times directly affects user experience. Therefore, the number of network drop times should be optimized for both network disconnection ratio and online duration per drop.
6.4.1 Fault Locating Process

After a daily report is generated with the daily report template, detailed analysis on the result data should be performed to find out the network problems and optimize the network counters. The following figure shows the general process for analyzing the daily performance report.
2013-7-9
Page 133 of 202
INTERNAL
1.
Analyze the entire network KPIs, including network disconnection ratio and online duration per drop on the daily performance report. If the network disconnection ratio is more than 10% or the online duration per drop is less than 180 minutes, it is recommended that you should check the BS and configuration, and then perform rectification or modify the configuration according to the check results.
Analyze the carrier KPIs, including network disconnection ratio and online duration per drop according to the daily performance report. Check the coverage or interference of the
2013-7-9
Page 134 of 202
INTERNAL
carrier where the network disconnection ratio is more than 10% or the online duration per drop is less than 180 minutes. For the coverage of the carrier, analyze the following KPIs: rate of UL/DL CINR < 12 dB, rate of UL RSSI < -80 dBm, and rate of DL RSSI < -80 dBm. For the interference of the carrier, analyze the following KPIs: interference density based on NI and interference intensity based on NI. If any of these KPIs exceeds the reference value, optimize the coverage or solve the interference problems of the corresponding carrier. Usually, the coverage is poor when the rate of DL RSSI < -80 dBm is more than 30%; the co-frequency interference is severe when the difference between the rate of DL RSSI < -80 dBm and the rate of DL CINR < 12 dB is more than 20%. If the average interference density based on NI is more than 5%, locate the interference problems of the BS.
2.
The Carrier sheet shows the comprehensive analysis results. You also need to perform detailed analysis of the KPIs on the Retainability and Coverage sheets. On the Retainability sheet, find out the carriers where the network drop rate is more than 10% or the online duration per drop is less than 180 minutes, and then select the top 50 sectors with the high network disconnection ratio for detailed analysis. Currently, the network drops are basically related to the radio environment, for example, poor coverage or strong interference. In the daily report, the Coverage sheet shows the coverage and co-frequency interference of a sector, and the Interference sheet shows the external interference of the network.
As shown in the preceding figure, the carrier with the highest network disconnection ratio is "FLORDBQ, CARRIERID=0, SECTORID=0". You can know the detailed
2013-7-9
Page 135 of 202
INTERNAL
coverage information about this carrier on the Coverage sheet (the following figure shows only a part of the contents).
You can know the detailed interference information about the sector on the Interference sheet (the following figure shows only a part of the contents).
According to the preceding analysis, you can know that the interference of the carrier is not large but the coverage is poor. 3. In the daily performance report template V2.0 (matching the BS C03SPC500), the network drop times due to different factors are measured separately. You can perform detailed analysis on the carriers with the most disconnection times caused by different factors, and take different measures based on the disconnection causes. For details, see section 6.4.2"Cause Analysis." The number of network drop times should be optimized for both network disconnection ratio and online duration per drop related to retainability.
2013-7-9
Page 136 of 202
INTERNAL
6.4.2 Cause Analysis

Fault Symptom Times of deregistration due to air link failure is high. Possible Cause 1. Uplink interference exists. Troubleshooting Method Check the NI measurement items in the daily performance report, and obtain the inverse frequency spectrum to determine whether interference exists. Check the distribution of RSSI and CINR of the sector to evaluate whether the coverage is normal. Solution If it is determined that external interference exists, urge the customer to perform frequency clearance by referring to chapter 5. Optimize the clusters.
2. The coverage is poor, and the downlink cofrequency interference is serious. 3. The uplink error packet rate is high.
1. Check the setting of the AMC threshold. 2. Check whether the uplink error packet rate (%) (in busy hours) and uplink HARQ retransmission rate (%) (in busy hours) are normal on the Error Packet sheet of the daily report.
2. Modify the setting to ensure the consistency. 2. Adjust the downtilt of the interference sector.
Times of deregistration due to handover failure is high.
1. The coverage is poor, and the downlink cofrequency interference is serious. 2. The parameters are configured improperly.
Check the distribution of RSSI and CINR to evaluate whether the coverage is normal.
Optimize the clusters.
1. Check the scan/handover trigger value. 2. Check the values of the handover-related timers. 3. Check whether any neighbor cell is not configured.
2. Modify the setting to ensure the consistency.
Times of deregistration due to transmission fault is high.
The counter is valid when the transmission failure detection is enabled. If the number of network drop times is too high, check the transmission monitoring records.
Rectify transmission faults.
2013-7-9
Page 137 of 202
INTERNAL
Fault Symptom Number of MSinitiated reauthorization failures is large.
Possible Cause 1. The account or the cipher key is invalid. 2. The coverage is poor, and the downlink cofrequency interference is serious. 3. The timer is improperly set.
Troubleshooting Method Check the call records of the AAA user. Check the distribution of RSSI and CINR to evaluate whether the coverage is normal.
Solution Visit the user after confirming that the account is invalid. Optimize the clusters.
1. Check whether the value of AK Active Lifetime configured on the AAA is too small. 2. Check the setting of the T17 timer at the BS side.
1. Change the value of AK Active Lifetime to 12 hours on the AAA. 2. Change the value of the T17 timer to the baseline value. Optimize the clusters.
Times of deregistration due to other causes is high.
1. The MS re-enters the network actively. 2. The MS fails to disconnect from the network due to other factors.
Check the coverage of the sector. Escalate the problem, collect relevant data, and return it to Huawei HQ for analysis.
Times of Deregistration due to Air Link Failure

This counter measures the number of times that the system determines that the MS has disconnected from the network and deletes the MS information when finding that the number of uplink PDUs does not increase or the number of uplink error packets exceeds the threshold within the detection period through network drop detection. The most common cause is that the BS does not detect the disconnection of the MS, but releases the resources of the MS to make the MS exit when finding that the number of uplink PDUs does not increase within continuous periods through network drop detection. Check the following possible causes:
Uplink interference: The measured NI counters of the sector are high (the interference density based on NI is more than 5% and the interference intensity based on NI is more than -90 dBm). Check the interference by referring to chapter 5. If it is determined that external interference exists, urge the customer to perform frequency clearance. Poor coverage and serious downlink co-frequency interference: Check the distribution of RSSI and CINR of the sector in WiMAX V32C03 Daily Report to evaluate the coverage. If the rate of DL RSSI < -80 dBm is more than 30% or the difference between the DL RSSI < -80 dBm and the DL CINR < 12 dB is more than 20% (which indicates that the co-frequency interference is serious), optimize the cluster. High uplink error packet rate: Check the uplink error packet rate (%) (in busy hours) and
2013-7-9
Page 138 of 202
INTERNAL
uplink HARQ retransmission rate (%) (in busy hours) on the Error Packet sheet of the daily report. If the uplink error packet rate is more than 3% or the uplink HARQ retransmission rate is more than 30%, check the BS configuration and ensure that the AMC threshold is consistent with the baseline.
Times of Deregistration due to Handover Failure

This counter is recorded on the SBS. It measures the number of handovers initiated by the MS at the source side without handover completion messages. The possible causes are as follows:
Poor coverage or serious interference: Due to discontinuous coverage, the MS fails to access the network on the TBS after initiating handover at the SBS. If the MS performs handover during the moving in particular, the signal quality drops as the MS moves, and finally the MS disconnects from the network due to handover failure. Check the distribution of RSSI and CINR of the sector in the performance measurement report to evaluate the coverage. If the rate of DL RSSI < -80 dBm is more than 30% or the difference between the DL RSSI < -80 dBm and the DL CINR < 12 dB is more than 20% (which indicates that the co-frequency interference is serious), optimize the cluster. Improper setting of parameters: Check the scan/handover trigger value, CCM timer, and neighbor cell configuration of the BS to ensure that the configuration is consistent with the baseline.
Times of Deregistration due to Transmission Fault

This item is measured only when the transmission detection mechanism is enabled. If transmission interruption is detected, the BS enables the MS to disconnect from the network through an RNG-RSP message. Check the transmission status when this measurement value is large. Currently, this function is disabled in most sites, and the measurement result is 0.
Number of MS-Initiated Re-Authorization Failures

This counter measures the number of network drop times due to direct rejection by the AAA server, three-way handshake failure, or AK timeout. The possible causes are as follows:
Invalid account or cipher key: Check the call records of the AAA user to determine whether the account expires or the user owes fees, and then visit the user. Poor coverage and serious downlink co-frequency interference: In this case, air interface signaling messages are lost, thus causing three-handshake failure or AK timeout. Check the distribution of RSSI and CINR of the sector in the performance measurement report to evaluate the coverage. If the rate of DL RSSI < -80 dBm is more than 30% or the difference between the DL RSSI < -80 dBm and the DL CINR < 12 dB is more than 20% (which indicates that the co-frequency interference is serious), optimize the cluster. Improper setting of the timer: Check the T17 timer of the BS and ensure that its value is consistent with the baseline value. Modify the re-authentication period to 12 hours at the AAA side except in a few sites where the re-authentication period is used as the minimal charging unit and should be set to a smaller value according to the actual situation.
Times of Deregistration due to Other Causes

The number of network drop times due to causes other than the preceding four causes is calculated in this counter. Currently, a known scenario is that the MS sends an RNG-REQ message to re-trigger initial network entry before the BS detects its exit. This cause can be checked through sector coverage analysis.
Poor coverage or serious interference: Due to discontinuous coverage, the MS fails to
2013-7-9
Page 139 of 202
INTERNAL
access the network on the TBS after initiating handover at the SBS. If the MS performs handover during the moving in particular, the signal quality drops as the MS moves, and finally the MS disconnects from the network due to handover failure. Check the distribution of RSSI and CINR of the sector in the performance measurement report to evaluate the coverage. If the rate of DL RSSI < -80 dBm is more than 30% or the difference between the DL RSSI < -80 dBm and the DL CINR < 12 dB is more than 20% (which indicates that the co-frequency interference is serious), optimize the cluster.
The MS initiates initial network entry again through an RNG-REQ message before the BS detects its exit: The possible cause is that the MS has disconnected from the network, for example, downlink out of synchronization, but the BS does not detect it, and the MS actively enters the network again. Alternatively, the timer of the MS times out and the MS enters the network again actively while the BS is waiting for the re-authentication message from the MS during re-authentication.
All the preceding problems are closely related to air interface signals. After excluding the coverage and interference causes, you are advised to collect CHRs or call logs to handle the problems.

Through performance measurement analysis, you can obtain the online duration per drop and network disconnection ratio of the entire network and each sector, find out the top N carriers, optimize the clusters of the poor coverage or interference carriers, and modify the incorrect parameter setting. If abnormal network drop persists under some carriers, you need to use the advanced data, namely, CHR data or call logs, for analysis.
6.5.1 Analysis Tools

The OMStar and AAT can be used for further analyze the abnormal network drop problems. The following sections describe how to use these tools for analysis.
Using the OMStar to Analyze Network Drop

By using the OMStar to analyze CHR data, you can obtain more detailed causes than the performance measurement data. You can obtain the following analysis information by setting the summary object (GW, BS, sector, or carrier).

Analysis of cause values Analysis of user details Analysis of carrier details
2013-7-9
Page 140 of 202
INTERNAL
Details are as follows: 1. Analysis of Cause Values You can obtain the error cause of each object from this sheet.
Click an object for secondary analysis. You can obtain the rank of users who disconnect from the network due to different factors, air interface resources, and MS types. From the rank of MSs based on disconnection cause value, you can know whether
2013-7-9
Page 141 of 202
INTERNAL
several MSs or all MSs disconnect from the network due to the specified cause. As shown in the following figure, two MSs, namely, 0025-6833-1CA5 and 0025-68ACFCBD, disconnect from the network due to the specified cause.
You can further analyze the signal quality of the MS disconnected due to the specified cause to determine whether the MS is under poor coverage or strong interference, and then perform the corresponding handling, for example, cluster optimization or user visit.
2.
Analysis of User Detail The same MS usually disconnects from the network due to different factors. You can obtain the network drop reason of each MS on the Analysis of User Detail sheet.
2013-7-9
Page 142 of 202
INTERNAL
Click an MS for secondary analysis. You can obtain the cause value and radio environment of the MS at each abnormal disconnection.
3.
Analysis of Carrier Detail You can obtain the network drop reason of each carrier on the Analysis of Carrier Detail sheet.
2013-7-9
Page 143 of 202
INTERNAL
Using the AAT to Analyze Network Drop

By using the AAT to analyze call logs, you can obtain the information similar to that from CHR data. The following section describes how to use the AAT to analyze the network drop reason. 4. Filter the network drop analysis information based on cause value "CallType = "DRCONN"".
2013-7-9
Page 144 of 202
INTERNAL
5.
After filtering, you can obtain the type and proportion of each cause value. Click a cause value. The detailed description, scenario, and handling suggestion of each cause are displayed.
6.
Set the summary object.
2013-7-9
Page 145 of 202
INTERNAL
7.
View the cause values and radio environments at all network drops on the Details tab page.
6.5.2 Analyzing Network Drop Cause Values

The CHRs or call logs record the number of all network drop scenarios. During analysis of the
2013-7-9
Page 146 of 202
INTERNAL
cause values, you need to know the cause values that result in MS disconnection from the network. For example, active exit initiated by the MS is a normal disconnection and not counted in the number of network drop times. Pay great attention to the cause values that result in MS disconnection from the network. The following table lists the common causes that result in MS disconnection. Error Code 7 Cause Description When the number of uplink error packets exceeds the threshold within the disconnection detection period, the BS actively releases the MS. Handling Suggestion Find out the top N MSs, and check the signal quality of these MSs at disconnection.
If the MS is under poor coverage (empiric value: DL RSSI -80 dBm) or in a downlink area with strong interference (empiric value: DL CINR DL RSSI 90), perform single user signaling trace and check the DL CINR and DL RSSI of the MS to determine its status: 1) If the MS is offline, record the MAC address of the MS. 2) If the MS is online and the current signal quality is good (DL RSSI -80 dBm or DL CINR 12 dB), the user may have adjusted the position of the MS. Record the MS information, indicating that the problem is solved. 3) If the MS is online, and the current signal quality is poor (DL RSSI -80 dBm or DL CINR 12 dB), record the MAC address of the MS or optimize the coverage of the MS. If the signal quality of the MS does not meet the preceding conditions, that is, the signal quality of the MS that frequently disconnects from the network is good, record it as a problem.
1612972047
The BS receives the RNGREQ from the MS again, indicating that the MS has disconnected from the network and connected to the network again without being detected by the BS. The BS releases the resources previously allocated to the MS.
Find out the top N MSs, and check the signal quality of these MSs at disconnection.
The most possible cause is that MAP messages are lost when the MS is under poor coverage or in an area with strong interference. Determine whether network coverage optimization is required. If the signal quality of the MS that frequently disconnects from the network due to this factor is good, record it as a problem.
2013-7-9
Page 147 of 202
INTERNAL
Error Code 1612977677
Cause Description The received KEY_CHANGE_DIREC message indicates authentication failure. Usually, the AAA returns the ACCESS-REJECT message.
Handling Suggestion Find out the top N MSs, and check the signal quality of these MSs at disconnection.
Ask engineers at the AAA side to check the authentication failure cause. If there are no AAA engineers on site, record it as a problem.
1612977699
After the MS is reauthenticated by the AAA, the BS and the MS perform threeway handshake. SA_TEK_CHALLENGE (sent from the BS to the MS) is the first signaling message for three-way handshake. The BS waits for the SA-TEKRequest response message from the MS. If the response message is not received, the BS resends the SA-TEKCHALLENGE message for three times. Usually, authentication fails if the SATEK-CHALLENGE message is lost on the air interface, or the MS determines that the message is invalid, or the SATEK-Request message sent by the MS is also lost. The BS enables the MS to disconnect from the network when the number of the SA_TEK_CHALLENGE message retransmission times exceeds the threshold during re-authentication.
Find out the top N MSs, and check the signal quality of these MSs at disconnection.
Exclude the re-authentication three-way handshake failure due to poor coverage or strong interference. If the signal quality of the MS that frequently disconnects from the network due to this factor is good, record it as a problem.
The following table lists the causes that are counted as the number of network drop times (namely, normal disconnection).
2013-7-9
Page 148 of 202
INTERNAL
Error Code 4
Cause Description The GW initiates the disconnection actively by sending a NetExit MS State Change Req message.
Handling Suggestion The disconnection initiated by the GW is not counted into the number of network drop times. For example, in certain scenarios, the MS enters the network from another carrier after it already enters the network. In this case, the GW detects that the MS is online, and thus actively enables the MS to exit. The disconnection actively initiated by the MS is not counted into the number of network drop times.
The MS actively requests deregistration.
One important purpose of CHR or call log data analysis is to find out the top N MSs that disconnect from the network due to various factors, and perform handling based on the cause values. Plan return visits to users in advance instead of passively waiting for complaints. If any cause cannot be handled, record it as a problem, collect relevant data, and return it to Huawei HQ for analysis.

If the network drop causes of certain MSs cannot be located after performance measurement and CHR (including call logs) analysis, or the cause value recorded in the CHR is not a common one, record it as a problem, collect relevant data, and return it to Huawei HQ for analysis.
6.6.1 Exceptional User Trace

Analyze the CHRs of the sector to trace the top N MSs. The traced information includes the following:

R1/R6 interface signaling at the BS side Signaling at the GW side User information trace Carrier information trace
Send the trace data together with the call logs and CHRs to Huawei HQ for analysis.
6.6.2 Onsite Test

Select the sectors with abnormal online duration per drop, and obtain the radio environment information about the MSs that disconnect from the network abnormally from the CHRs. The radio environment and abnormally disconnected users during the onsite test should be consistent with those recorded in the CHRs, and only FTP download needs to be performed during onsite test. The data to be captured includes the following: 1. 2. 3. R1/R6 interface signaling at the BS side Signaling at the GW side (R6, R3 signaling, single user trace) User information trace
2013-7-9
Page 149 of 202
INTERNAL
4. 5.
Carrier information trace Logs at the MS side: For the MS that uses the Sequans chip, for example, BM625, Telnet to the MS and capture the MS data. The scripts are as follows:
Run the following commands first.

cmd cmd cmd cmd cmd cmd cmd set displaye setuser,su showsscaps showss showsf,1 upcs:conf filter,+UPCS+RNGS wimax-lon on
Use the tool to print the following information cyclically.

cmd cmd cmd cmd cmd cmd cmd upcs:cont showpacketfl showrftx mss: dlmap umss:clear umss:dump,0,1000
For the GCT or the MS using the Beceem chip, connect the DT software to save the logs at the MS side. Send the captured data together with the call logs and CHRs to Huawei HQ for analysis.
6.7 Appendix
6.7.1 Cases
Problem Description
The MS disconnects from the network. The cause value recorded in the call log is 1612972047. That means the BS receives the RNG-REQ message from the MS again (indicating that the MS has disconnected from the network and then reconnected to the network before being detected by the BS), and thus releases the resources previously allocated to the MS.
2013-7-9
Page 150 of 202
INTERNAL
Key Procedure and Root Cause Analysis
According to the traced signaling messages, the MS does not respond to the REP-REQ message sent by the BS before disconnecting from the network. The MS sends an RNG-REQ message (namely, the message numbered 100 in the preceding figure) again. After receiving the message numbered 102, the BS releases the previously established DP, and then responds to the RNG-REQ message. As seen from the REP-RSP message returned by the MS before disconnection from the network, the downlink CINR is 6 dB and the downlink RSSI is 71 dBm (the value in the signaling message is an encoded value which should be converted according to protocol definition) in the area where the MS resides. In other words, the downlink co-frequency interference is serious.
2013-7-9
Page 151 of 202
INTERNAL
Conclusion, Solution, and Effect

The MS is out of synchronization in the downlink and disconnects form the network due to the serious downlink co-frequency interference. In this case, you need to find out the interference source and optimize the network coverage.
6.7.2 Reference Document

Document Name Content Application Scenario
2013-7-9
Page 152 of 202
INTERNAL
Traffic Rate and Capacity Optimization

This chapter describes how to discover problems related to traffic rate and capacity from service experience of users, perform preliminary analysis, and locate the problems, thus to improve the network capacity. It contains the following contents: Descriptions of KPIs Common problem analysis and handling Advanced analysis methods Difficult fault handling
After studying this chapter, WiMAX engineers should be able to understand the KPIs related to traffic rate and capacity optimization, and reach the following requirement: 1. 2. 3. WiMAX engineers are able to analyze and solve common traffic rate and capacity problems independently. Some engineers with powerful technical skills are able to use the OMStar and AAT to analyze and solve high-level performance problems related to traffic rate and capacity. WiMAX engineers are not required to solve difficult problems independently, but they must know how to collect relevant data. Technical engineers should be able to collect relevant data and return it to R&D engineers to analyze and locate problems.
7.2 KPIs Related to Traffic Rate and Capacity

7.2.1 Major Factors Affecting Capacity
The major factors that affect the throughput of a sector can be expressed in the following formula: Sector throughput = total number of slots x (1 - signaling overhead proportion)/(1 + retransmission rate) x slot coding efficiency
Signaling overhead proportion: indicates how many resources are used to transmit
2013-7-9
Page 153 of 202
INTERNAL
signaling, including MAP overhead, DCD/UCD broadcast overhead, and power control messages. It is usually determined by the number of users and the enabled functions. The lower the overhead is, the more resources can be used to transmit services.
Retransmission rate: indicates the retransmission consumption incurred after the HARQ feature is enabled. After HARQ is enabled, the demodulation threshold decreases, which improves the slot coding efficiency but brings about extra retransmission consumption. When the slot coding efficiency improvement exceeds the retransmission consumption, there is gain from enabling of the HARQ feature. Slot coding efficiency: indicates the adopted modulation code mode, depending on the AMC threshold, CINR of the MS, and features such as MIMO-A, MIMO-B, and CSM. All these factors can improve the slot coding efficiency.
The following table lists the major features related to traffic rate and capacity. Factor Affecting Throughput Signaling overhead proportion Performance Improvement Feature
Compressed MAP: After compressed MAP is used, DL-MAP and ULMAP can be packed together, thus saving certain overhead. The effect is much more obvious in the case of MAP repetition. Uplink common zone indicated by UCD: The fixedly allocated uplink areas, including Ranging, FFB, and HARQ Ack, are delivered through the UCD. In this way, the IEs of these three areas can be removed from UIL-MAP, thus reducing the length of UL-MAP. HARQ subburst combination: An IE can indicate the subbursts of multiple users instead of a single user. A frame uses only one or two IEs. CQICH: The downlink signal quality is reported through the uplink FFB, thus avoiding REP message interaction. The CQICH, however, cannot report the downlink RSSI. Packetized scheduling: When the QoS is met, multiple scheduling operations of a user are combined and performed at a time, reducing the overhead brought by map_IE. The V3R3C00 supports packetized scheduling of realtime and non-realtime services.
Retransmission rate
Uplink slot limit: The number of sub-carriers supported by a user is calculated on basis of the uplink signal quality and maximum transmit power of the user. Then, the number of slots allocated can be determined on basis of the calculated threshold, thus avoiding uplink error packets due to power limit. Outer loop power control: implements dynamic adjustment of the AMC threshold of a user. When the retransmission rate is higher than the target PER of outer loop power control, the AMC threshold of the user is increased to force the user to enter the MCS mode with lower demodulation threshold. Error packet MCS reduction: forcibly adjusts the MCS mode to reduce the retransmission rate. If the error packet rate of a user reaches a certain limit within a certain period, the MCS of the user is forcibly reduced. Uplink and downlink switches are available.
2013-7-9
Page 154 of 202
INTERNAL
Factor Affecting Throughput Slot coding efficiency
Performance Improvement Feature
AMC: adjusts the MCS mode according to the preset threshold and based on different signal quality levels. Outer loop power control: The AMC threshold of a user is dynamically adjusted according to the current retransmission rate of the user. If the retransmission is low, the AMC threshold is lowered, and the user can use a higher MCS mode. MIMO: improves the coding efficiency through diversity gain and power gain. The BS V3R3C00 supports uplink MIMO. Resource fair scheduling: indicates that users with good signal quality are allocated with as many slots as those allocated to the users with poor signal quality, thus improving the average coding efficiency of sectors.
7.2.2 KPIs Related to Traffic Rate and Capacity

Counter Name Formula Descriptio n Carrier DL BE Average Traffic Rate Carrier DL BE Average Traffic Rate = DL BE Service Traffic * 8 / Carrier DL BE Traffic Duration This KPI indicates the actual average rate experienced by all the BE users under one carrier during the downlink service time within the measurement period (the minimum unit is 30 minutes). It measures only the rate when the users are being served, thus excluding the impacts of no service time on the average rate. Retransmission is also not included. WiMAX is mostly used as a bandwidth application. It is a network mode featuring one-time access and long-time online. Therefore, when the traffic is fixed, if the online time is longer, the average rate of the user is decreased, and the traffic rate experienced by the user cannot be really reflected. In comparison, the traffic rate can better present the actual service level of the BS provided for a single user. For example, when a user browses a Web page, the service duration is measured from startup of the browser up to completion of refreshing the Web page. If the user does not perform any other click operation, the service duration is not increased. The traffic rate measures the average rate perceived by the user within this period. The time unit for resource allocation of the BS is frame, while the time unit for QoS rate is second. Therefore, if resources that meet maximum QoS rate for the user within one second, the traffic rate may exceed the QoS. In fact, the average traffic rate should be higher than QoS rate when the system is not busy and service experience is good. In V300R002C03 and later versions, the BS supports the traffic rate and traffic duration measurement for five kinds of downlink service flows. Unit Kbps
2013-7-9
Page 155 of 202
INTERNAL
Carrier UL BE Average Traffic Rate Carrier UL BE Average Traffic Rate = UL BE Service Traffic * 8 / Carrier UL BE Traffic Duration
Description This KPI indicates the actual average rate experienced by all the BE users under one carrier during the uplink service time within the measurement period (the minimum unit is 30 minutes). Similar to the downlink traffic rate, the uplink traffic rate also measures the average rate perceived by users during actual service time. Relatively, the measurement result may also exceed the maximum QoS rate. Due to the limitation of the product, the traffic duration is not measured for uplink UGS and ertPS. The uplink traffic duration and traffic rate are measured for rtPS, nrtPS, and BE. Unit Kbps
DL carrier average Throughput For versions earlier than V3R2C03SPC500: DL carrier average Throughput = (DL Unicast Traffic on Carrier + DL Broadcast Traffic)/measurement period For V3R2C03SPC500 and V3R3: DL carrier average Throughput = DL Unicast Traffic on Carrier /measurement period
Description This KPI measures the downlink average traffic rate per carrier within the measurement period. This KPI is a compound counter that indicates the overall throughput of the carrier. It can be directly obtained from performance measurement data. In V3R2C03SPC500 and later versions, this KPI measures only the traffic allocated to the user. The downlink broadcast messages such as DCD/UCD and MAP are not measured. Unit Kbps
UL carrier average Throughput UL carrier average Throughput = UL Unicast Traffic on Carrier/measurement period
2013-7-9
Page 156 of 202
INTERNAL
Descriptio n
This KPI measures the uplink average traffic rate per carrier. This KPI is a compound counter that indicates the overall throughput of the carrier. It can be directly obtained from performance measurement data. Kbps
Unit
Carrier DL Slot Occupancy Rate DL All Zone Occupancy Rate = Total Number of Slots Occupied on DL All Zone/Total Number of Slots in DL All Zone x 100% or DL Partial Zone Occupancy Rate = Total Number of Slots Occupied on DL Partial Zone/Total Number of Slots in DL Partial Zone x 100%
Description This KPI indicates the usage of downlink resources and shows the service experience effect. It is an important counter for optimization measures such as capacity expansion and site addition. This KPI measures the overall resource consumption level of the carrier, involving the FCH, MAP message, and traffic channels occupied by the user. It can best explain the pressure of the sector. By default, 10% of the BS resources are reserved. Therefore, if the measurement result is more than 80%, the sector downlink is nearly congested. Note that in versions earlier than V3R2C03SPC300, the HARQ retransmission is not involved in the occupancy calculation. Therefore, in the SPC205 version, you need to include the retransmission rate in calculating the resource occupancy of the sector; otherwise, a sector where the retransmission rate is high but resource occupancy is low may have been congested, affecting the service experience of users. In C03SPC300 and later versions, the occupancy calculation includes the retransmission rate, and thus the resource usage of the sector can be directly presented. In the FFR network, the occupancies of the two zones are measured separately and should be included in calculating of the carrier load. Unit %
Carrier UL Slot Occupancy Rate UL All Zone Occupancy Rate = Total Number of Slots Occupied on UL All Zone/Total Number of Slots in UL All Zone x 100% or UL Partial Zone Occupancy Rate = Total Number of Slots Occupied on UL Partial Zone/Total Number of Slots in UL Partial Zone x 100%
2013-7-9
Page 157 of 202
INTERNAL
Description This KPI indicates the usage of uplink resources and shows the service experience effect. It is an important counter for optimization measures such as capacity expansion and site addition. This KPI measures the overall resource consumption level of the carrier, involving the uplink common zones and traffic channels occupied by the user. It can best explain the pressure of the sector. By default, no uplink resources are reserved but certain resources are reserved in common zones. Therefore, if the measurement result is more than 85%, the sector is nearly congested in the uplink. The uplink resource occupancy calculation includes the retransmission rate, and thus the resource usage of the sector can be directly presented. In FFR mode, the occupancies of the two zones are measured separately and should be included in calculating of the carrier load. Unit %
DL Channel Overhead Occupancy Ratio DL Channel Overhead Occupancy Ratio = Number of Slots Occupied by DL Common Regions/ (Total Number of Slots in DL All Zone + Total Number of Slots in DL Partial Zone)*100%
Description This KPI measures the proportion of the downlink resources occupied by the downlink common zones (FCH and MAP messages) to all downlink air interface resources. It can be used to evaluate the influences of downlink common zones on the system capacity. If the proportion of the resources occupied for system overhead is too large, the number of slots that can be allocated to users for service transmission decreases. As a result, the throughput of the system in full load decreases. Unit %
Average Number of Online Users It is measured by the BS and output as performance measurement data.
Description This KPI indicates the average number of concurrent online users under a carrier within the measurement period. It shows the user scale of the network. The measurement of average user number provides references for network planning, such as capacity expansion and carrier addition. It is equivalent to the number of users keeping online under average effects. It shows the network usage status of users. Unit /
Counter Name
Maximum Number of Online Users
2013-7-9
Page 158 of 202
INTERNAL
Formula
When a user changes from online state to offline state, the number of online users is reduced by 1. When a user accesses the network successfully, the number of online users is increased by 1. The maximum value within the measurement period should be used.
Description This KPI indicates the maximum number of concurrent online users under a carrier within the measurement period. It shows the user scale of the network. The measurement of maximum user number provides references for network planning, such as capacity expansion and carrier addition. For example, the number of users in a certain region and the maximum number of concurrent online users per BS indicate the state of the BS (idle or busy), and are used to determine whether to expand the system capacity. Unit /
DL HARQ re-transmission rate DL HARQ re-transmission rate = (1st Retransmission DL HARQ Subburst of Receiving Success*1 + 2nd Retransmission DL HARQ Subburst of Receiving Success*2 + 3rd Retransmission DL HARQ Subburst of Receiving Success*3 + 4th Retransmission DL HARQ Subburst of Receiving Success*4 + DL HARQ Subburst Number of Receiving Failure*3) / (DL HARQ Subburst Number of Receiving Success in One Time+ 1st Retransmission DL HARQ Subburst of Receiving Success + 2nd Retransmission DL HARQ Subburst of Receiving Success + 3rd Retransmission DL HARQ Subburst of Receiving Success + 4th Retransmission DL HARQ Subburst of Receiving Success + DL HARQ Subburst Number of Receiving Failure)*100%
Description This KPI measures the proportion of the subbursts transmitted due to retransmission to the HARQ subbursts to be transmitted. This proportion shows the influences of retransmission on normal service transmission and can be used to evaluate whether the outer loop algorithm is reasonable. The calculation formula of this KPI is related to the maximum number of HARQ retransmission times. The preceding formula is used to calculate the DL retransmission rate when the maximum number of retransmission times is 3 (default value of the product). This KPI is not directly output as the performance measurement data but is automatically generated by the daily performance report. Unit %
Counter Name
UL HARQ re-transmission rate
2013-7-9
Page 159 of 202
INTERNAL
Formula
UL HARQ re-transmission rate =(1st Retransmission UL HARQ Subburst of Receiving Success*1 + 2nd Retransmission UL HARQ Subburst of Receiving Success*2 + 3rd Retransmission UL HARQ Subburst of Receiving Success*3 + 4th Retransmission UL HARQ Subburst of Receiving Success*4 + UL HARQ Subburst Number of Receiving Failure*3) / (UL HARQ Subburst Number of Receiving Success in One Time+ 1st Retransmission UL HARQ Subburst of Receiving Success + 2nd Retransmission UL HARQ Subburst of Receiving Success + 3rd Retransmission UL HARQ Subburst of Receiving Success + 4th Retransmission UL HARQ Subburst of Receiving Success + UL HARQ Subburst Number of Receiving Failure)*100%
Description This KPI measures the proportion of the subbursts transmitted due to retransmission to the HARQ subbursts to be transmitted. This proportion shows the influences of retransmission on normal service transmission and can be used to evaluate whether the outer loop algorithm is reasonable. The calculation formula of this KPI is related to the maximum number of HARQ retransmission times. The preceding formula is used to calculate the UL retransmission rate when the maximum number of retransmission times is 3 (default value of the product). This KPI is not directly output as the performance measurement data but is automatically generated by the daily performance report. Unit %
7.2.3 KPIs Related to Coding Efficiency and Coverage

Counter Name Formula Carrier DL Average Slot Coding Efficiency Before SPC500: Carrier DL Average Slot Coding Efficiency = (DL All Zone MIMO-B User Allocation Byte Number + DL All Zone None MIMO-B User Allocation Byte Number + DL 1/3 Zone MIMO-B User Allocation Byte Number + DL 1/3 Zone None MIMO-B User Allocation Byte Number)/((DL All Zone MIMO-B User Allocation Slot Number + DL All Zone None MIMO-B User Allocation Slot Number + DL 1/3 Zone MIMO-B User Allocation Slot Number + DL 1/3 Zone None MIMO-B User Allocation Slot Number)*6)
2013-7-9
Page 160 of 202
INTERNAL
Description This KPI indicates the average number of bits that can be carried over each DL sub-carrier, thus obtaining the approximate DL average MCS. It involves all the users under a carrier and reflects the average signal quality of the users under the sector. Without regard to HARQ retransmission, the average coding efficiency is independently used to represent the approximate average MCS mode of the user group being served. Relatively, if the coding efficiency of a sector is high but the throughput cannot reach the expected level, it usually indicates that the retransmission rate of the sector is high. This KPI reflects the overall status of a sector. The similar counters are as follows: DL All Zone Average Slot Coding Efficiency DL All Zone MIMO-B User Average Slot Coding Efficiency DL All Zone None MIMO-B User Average Slot Coding Efficiency DL Partial Zone Average Slot Coding Efficiency DL Partial Zone MIMO-B User Average Slot Coding Efficiency DL Partial Zone None MIMO-B User Average Slot Coding Efficiency Unit Bpsc
Carrier UL Average Slot Coding Efficiency Before SPC500: Carrier UL Average Slot Coding Efficiency = UL User Allocation Byte Number / (UL User Allocation Slot Number*6) After SPC500: Carrier UL Average Slot Coding Efficiency = UL User Allocation Byte Number / UL User Allocation Slot Number
Description This KPI indicates the average number of bits that can be carried over each UL sub-carrier, thus obtaining the approximate UL average MCS. It involves all the users under a carrier and reflects the average signal quality of the users under the sector. Similar to the DL average coding efficiency, the average coding efficiency, without regard to HARQ retransmission, is independently used to represent the approximate average MCS mode of the user group being served. Unit Bpsc
downlink CINR less than 12 dB rate downlink CINR less than 12 dB rate = (Times When DL CINR Is Lower Than 0 dB+Times When DL CINR Ranges from 1 dB to 4 dB+Times When DL CINR Ranges from 5 dB to 8 dB+Times When DL CINR Ranges from 9 dB to 12 dB)/Times When DL CINR Ranges from X dB to X dB *100%
2013-7-9
Page 161 of 202
INTERNAL
Description CINR directly measures the signal quality of users. Through this KPI, you can analyze the overall signal quality of the users under a sector. This KPI is not directly output as the performance measurement data but is automatically generated by the daily performance report. Unit %
Downlink RSSI less than -80 dBm rate Downlink RSSI less than -80 dBm rate = (Times When DL RSSI Is Not Higher Than -90 dBm+Times When DL RSSI Ranges from -89 dBm to -80 dBm)/Times When DL RSSI Ranges from -X dBm to -XdBm*100%
Description RSSI is not affected by interference and can be used to measure coverage. This KPI directly shows the proportion of poor-coverage users under the current sector, thus promoting optimization and site addition. Compared with the proportion of CINR, it can also be used to measure whether co-frequency interference exists. This KPI is not directly output as the performance measurement data but is automatically generated by the daily performance report. Unit %
Uplink CINR less than 12 dB rate Uplink CINR less than 12 dB rate = (Times When UL CINR Is Lower Than 0 dB+Times When UL CINR Ranges from 1 dB to 4 dB+Times When UL CINR Ranges from 5 dB to 8 dB+Times When UL CINR Ranges from 9 dB to 12 dB)/Times When UL CINR Ranges from X dB to X dB *100%
Description CINR directly measures the signal quality of users. Through this KPI, you can analyze the overall signal quality of the users under a sector. Unlink the DL CINR which is periodically reported, the UL CINR is measured by the BS and is proportional to the frequency of services, that is, if the user triggers services more frequently, the proportion of the CINR is higher. Therefore, this measurement can reflect the instant signal status of a user being served, but does not show the signal quality of all users under a sector. The most accurate and direct way to observe signal distribution is to check the DL RSSI. This KPI is not directly output as the performance measurement data but is automatically generated by the daily performance report. Unit %
2013-7-9
Page 162 of 202
INTERNAL
Uplink RSSI less than -80 dBm rate Uplink RSSI less than -80 dBm rate = (Times When UL RSSI Is Not Higher Than -90 dBm+Times When UL RSSI Ranges from -89 dBm to -80 dBm)/Times When UL RSSI Ranges from -X dBm to -XdBm*100%
Description This KPI shows the overall UL signal quality of the users being served. Similar to the UL CINR, the UL RSSI is also measured by the BS and is related to the service frequency of users. This KPI is not directly output as the performance measurement data but is automatically generated by the daily performance report. Unit %
7.2.4 Capacity Expansion and Exception Thresholds

Based on the early warning principle, a sector should be expanded before it is congested. The sector expansion should comply with the following rules: 1. The number of users is the absolute determination condition. If the number of users reaches the expansion threshold (namely, 80), carriers should be added irrespective of the throughput or occupancy level. It is considered that the capacity approaches to the limit when the DL traffic rate is less than 300 kbps, the DL slot occupancy is more than 75%, and the retransmission rate is less than 15% in busy hours. In this case, carriers should be added. It is considered that the capacity approaches to the limit when the UL traffic rate is less than 100 kbps, the UL slot occupancy is more than 80%, and the retransmission rate is less than 10% in busy hours. In this case, carriers should be added. If the occupancy exceeds the preceding thresholds but the traffic rate is still higher than the standard value (DL: 300 kbps, UL: 100 kbps), a sector can still allocate numbers without having to expand the capacity. The preceding thresholds for capacity expansion are determined based on Philippine Globe (10M with all, MIMO-B disabled, number allocation rates/l 512 kbps and 1 Mbps). For specific sites, adjustments can be made according to the enabled features. Determination Criteria The average DL traffic rate in busy hours is less than 300 kbps. The average UL traffic rate in busy hours is less than 100 kbps (standard value for number allocation). Congestion The DL slot occupancy of a sector in busy hours is more than 75%. The UL slot occupancy of a sector in busy hours is more than 80%. The average number of online users in busy hours is more than 80. If any of the preceding conditions is met, the sector is congested or nearly congested, and capacity expansion is required.
2.
3.
4.
5.
Problem Low traffic rate
2013-7-9
Page 163 of 202
INTERNAL
Problem Low DL coding efficiency Low UL coding efficiency Poor coverage Co-channel interference
Determination Criteria The average DL coding efficiency during busy hours is less than 2. (Philippine criteria. When MIMO-B is enabled, the lower limit for coding efficiency should be increased.) The average UL coding efficiency during busy hours is less than 1.5. (Philippine criteria. When MIMO is enabled, the lower limit for coding efficiency should be increased.) The rate of DL CINR <= 12 dB is more than 20%, or the rate of DL RSSI <= -80 dBm is more than 20%. (rate of DL CINR <= 12 dB) (rate of DL RSSI <= -80 dBm) 20%
7.3 KPIs
7.3.1 Factors Affecting the KPIs
Traffic rate and capacity are correlated. When other conditions are the same, if the number of concurrent service users is greater, the system capacity is limited, and the traffic rate of a single user decreases. Similarly, if the number of active users decreases, the system capacity pressure is lowered, and a single user can obtain more system resources and better service experience. There are another two related KPIs.
Coding efficiency: It shows the coverage status of users, namely, the average MCS mode of all users under a carrier. Because the air interface resources are definite, the higher MCS mode can be used as the signal quality improves. When the allocated bandwidth is the same, fewer slots are occupied and the carrier can serve more users, thus obtaining a higher average throughput. Retransmission rate: The retransmission rate is measured only after HARQ is enabled. HARQ brings about combination gain and decreases the demodulation threshold, but certain resources are occupied for retransmission. Therefore, the retransmission rate is used to indicate the HARQ transmission status and the proportion of resources occupied for retransmission. Generally, the retransmission rate should be adjusted through outer loop power control.
For the network, coverage and interference are the major impacts on the coding efficiency and retransmission rate. Coverage determines the average coding efficiency, while the interference influences are reflected through the retransmission rate. If the proportion of the poor-coverage users to all services being served under the current sector, the average coding efficiency is low. If interference (co-frequency interference or external interference) exists, the retransmission rate of users is high and even exceeds the target PER of the outer loop. Reversely, if the retransmission rate is high, the outer loop increases the AMC threshold to enable users to use a lower MCS mode to lower the demodulation threshold. In this case, the coding efficiency also decreases. Particularly, the system configuration also affects the traffic rate and capacity. For example, if
2013-7-9
Page 164 of 202
INTERNAL
the AMC threshold switch is off, the threshold setting is improper, or the outer loop parameters are unreasonable, the system capacity and user service experience are affected.
7.3.2 Features and Parameters Affecting Traffic Rate and Capacity Counters
Feature Name Fair scheduling MIMO CSM MAP/DCD/UCD repetition Compressed MAP HARQ subburst combination AMC Outer loop power control HARQ Uplink slot limit Description Resources are evenly scheduled for users using different MCS modes based on slots or traffic rate. The diversity gain can be obtained. The throughput is improved through uplink user pairing. The reliability of broadcast messages such as MAP, DCD, and UCD is improved. The length of the MAP message is reduced. The length of map_IE of HARQ is reduced. Different modulation code modes are used on the basis of user signal quality. The MCS threshold is dynamically adjusted according to the retransmission rate of users. The throughput is improved through retransmission, thus lowering the demodulation threshold. The allocation of slots is adjusted based on radio channel changes, increasing the power of a single sub-carrier in data transmission.
Fair Scheduling
There are two scheduling modes: resource-fair mode and rate-fair mode. Resource-fair scheduling means that the same number of slots is allocated to users using different MCS modes under the same conditions. Rate-fair scheduling means that the same number of bytes is allocated to users using different MCS modes. Rate-fair scheduling enables lower-order users to occupy a large number of slots, thus decreasing the coding efficiency of the sector. Resource-fair scheduling ensures the average MCS of the sector, thus achieving a high average throughput. Query command: LST MACCAPABILITY:; Modification command: MOD MACCAPABILITY: SECTORID=0, CARRIERID=0, MACALPHAVALUE=120, MACMCSSCHSWITCH=ON; The parameter modification can take effect without the need to activate or deactivate the sector.
MIMO
MIMO is a special space division technology. Through multiple Tx/Rx channels, MIMO
2013-7-9
Page 165 of 202
INTERNAL
brings about diversity gain and improves the throughput. MIMO is classified into two categories: MIMO-A and MIMO-B. MIMO-A increases the CINR. MIMO-B increases the coding efficiency by two times. Query command: Modification command: The parameter modification can take effect only after the sector is activated or deactivated.
CSM
CSM is a technology similar to MIMO.
MAP/DCD/UCD Repetition
MAP and broadcast signaling repetition can improve the accessibility counters, lower the demodulation threshold, improve the network entry success rate of MSs, and reduces MS disconnection due to loss of MAP and broadcast messages. The repetition, however, is at the cost of doubled slots occupied, and repetition 2/4/6 brings about a high system overhead. Query command: LST CARRIERFRAMEINFO:; Modification command (modify the switch to repetition 2): MOD CARRIERFRAMEINFO: SECTORID=0, CARRIERID=0, FCHRCI=REPETITION-2; The parameter modification can take effect only after the sector is activated or deactivated.
Compressed MAP
Compressed MAP is used to pack DL-MAP and UL-MAP together to save certain fixed overhead. More resources can be saved when MAP repetition is enabled. Query command: LST CARRIERFRAMEINFO:; Modification command: MOD CARRIERFRAMEINFO: SECTORID=0, CARRIERID=0, MAPTYPE=COMPRESS; The parameter modification can take effect only after the sector is activated or deactivated.
HARQ
HARQ is a physical-layer retransmission technology. Through HARQ retransmission, the demodulation threshold can be lowered and the PER can be reduced. HARQ retransmission also brings about certain overhead. Therefore, the current air interface PER is controlled through outer loop to dynamically adjust the HARQ retransmission rate. Query command: LST OFDMACAPABILITY:; Modification command: MOD OFDMACAPABILITY: SECTORID=0,CARRIERID=0,DEMODULATION=37,MODULATION=20,ULCTRLSUPP =4,OFDMAMAPCAP=2; MOD ULCHANPARA:SECTORID=0,CARRIERID=0,HARQDELAYFORDLBURST=1,ULHAR QMAXRETRAN=3; MOD DLCHANPARA:SECTORID=0,CARRIERID=0,HARQACKDELAYFORULBURST=1,DL MAXHARQRETRAN=3; MOD MACCAPABILITY:SECTORID=0,CARRIERID=0,MAXBURINHARQ=49,PDUEXTFOR
2013-7-9
Page 166 of 202
INTERNAL
HARQ=0,HEADERTYPESUPP=524287,HARQCHASEBUFCAP=5142,EXTCAP=7; The parameter modification can take effect only after the sector is activated or deactivated.
HARQ subburst_IE Combination

When HARQ is enabled, a burst of a single user is split into multiple subbursts. Each subburst is indicated in map_IE, thus bringing about a large amount of MAP overhead. With the subburst_IE combination feature, multiple subbursts of different users can be indicated in an IE structure, thus saving the system overhead. Query command: LST RRMSOFT: PARANO=82; Modification command: MOD RRMSOFT: PARANO=82, VALUE=3; The parameter modification can take effect without the need to activate or deactivate the sector.
Outer Loop Power Control

Outer loop power control is an algorithm used to adjust the AMC threshold for each user based on the retransmission rate. If the retransmission rate is not higher than the target PER, the transmission status is good, and the AMC threshold on each order for the current user is actively lowered. If the retransmission rate is higher than the target PER, the AMC threshold is increased to make the user enter the lower MCS mode, thus lowering the demodulation threshold and ensuring that the retransmission rate is lower than the target PER. The outer loop states of different users are different, thus implementing user-based AMC thresholds. The threshold increasing and lowering have a limit. Query command: LST PCAMCPARA:; Modification command: MOD PCAMCPARA: SECTORID=0, CARRIERID=0, ULOUTERLOOPUPTH=5, ULOUTERLOOPLOWTH=-3, HARQDLOUTPERTARGET=100, DLOUTERLOOPLOWTH=-3, DLOUTERLOOPUPTH=5, ULOUTERLOOPPERHARQ=100; The parameter modification can take effect without the need to activate or deactivate the sector.
Uplink Slot Limit

If too many uplink resources are allocated, the transmit power of MSs is limited, a large number of uplink error packets are generated, thus affecting service transmission and easily triggering the disconnection detection mechanism to make MSs exit. The uplink slot limit feature is used to avoid such problems. Uplink slot limit is controlled by the switch and enabled by default. As a basic function, uplink slot limit should not be disabled. Additionally, the AMC out threshold configured in each uplink order is used for calculating the allocated slots. Therefore, the uplink AMC threshold should use the default setting of the version, and the dynamic change of thresholds is implemented through outer loop. Query command: LST PCAMCPARA Modification command: MOD PCAMCPARA: SLOTLIMITSWITCH=ON; The parameter modification can take effect without the need to activate or deactivate the sector.
2013-7-9
Page 167 of 202
INTERNAL
7.3.3 Traffic Rate Measurement

Traffic rate is a counter used to measure user service experience. It measures the traffic rate perceived by users during only the service time, and thus reflects the real feeling of users. From the aspect of performance measurement analysis, performance measurement is used to display and analyze the access states of all users on the network within a certain period and obtain the KPIs to reflect the actual running status and network bearer status, thus providing guidance for business operations of operators and measuring the network health. Huawei WiMAX network users are mostly broadband service users. Unlike continuous services (for example, FTP), the common user behaviors of the broadband service such as website browsing and email sending are discontinuous. If the online duration is used to calculate the user rate, the actual traffic rate perceived by users during the service time cannot be reflected, and thus the measurement result has certain deviation. Therefore, to ensure that the performance measurement is closer to user behaviors and reflects the actual service experience of users more accurately, the actual traffic rate should be described on the basis of accurate measurement. The carrier-level service duration measurement is added for this purpose. The service duration consists of the following parts: 1. 2. Duration of user data being scheduled Waiting time of the user data in queues before scheduling
See the following example: If the 1st data frame enters a queue, the 5th frame is scheduled, and the 10th frame exits the network, the online duration is 50 ms and the service duration is 25 ms. Assume that the user traffic within the period is 10 KB, the traffic rate is 400 kbps (= 10/0.025) and the average rate is 200 kbps (= 10/0.05). If the calculation method mentioned earlier is used, the result obtained is only half of the actual value, and the performance analysis and service evaluation must be affected. The time unit for resource allocation of the BS is frame, while the time unit for QoS rate is second. Therefore, if resources that meet maximum QoS rate for the user within one second, the traffic rate may exceed the QoS. In fact, the average traffic rate should be higher than QoS rate when the system is not busy and service experience is good.
7.4 Common Performance Problem Analysis

This section describes the common problems related to network capacity and traffic rate, possible causes, and handling methods. You can complete the general handling of the performance problems related to traffic rate and capacity according to the contents of this section.
7.4.1 Analysis Overview

Before starting the carrier-level traffic rate and capacity analysis, note the following issues: The number of users is the absolute determination condition. If the number of users reaches the expansion threshold (namely, 80), carriers should be added irrespective of the throughput or occupancy level. The criterion for measuring the downlink service experience of users is the traffic rate. In the
INTERNAL
case of downlink service scheduling, the system load directly affects the service experience of users. If the traffic rate is low but the system load is high, it can be considered that the sector is nearly congested, degrading the average service experience of users. To check the service experience, check whether the DL average traffic rate during busy hours has reached the preset value on the Carrier KPI sheet of the daily report. Like downlink service scheduling, the criterion for measuring the downlink service experience of users is the traffic rate. In the case of downlink service scheduling, whether the sector has residual resources directly determines whether to allocate resources. In the case of uplink service scheduling, however, the uplink power of the user should also be considered, and the maximum number of sub-carriers that can be supported should be calculated through slot limit. Therefore, if the traffic rate is low but the resource occupancy is high, it can be considered that the sector is nearly congested, degrading the average service experience of users. If the traffic rate is low but the uplink resource occupancy does not reach the congestion level, check whether uplink limit is enabled in combination with uplink and downlink signal quality of the user. Particularly, when WiMAX is used for radio broadband access, the common services used by users are asymmetric services such as Web page browsing, online video playing, and file download. Downlink data transmission proposes a large demand for bandwidth. There are only application feedbacks or few background traffics in the uplink, and thus there is a smaller requirement on bandwidth. For uplink and downlink symmetric services such as VoIP, the bandwidth of less than 100 kbps can meet the requirement. Therefore, the uplink traffic rate should be determined properly in combination with the commercial mode and user behaviors of the network. Take Philippine Globe as an example. The rates configured by the user are 512 kbps and 1 Mbps, and the used services are website browsing and VoIP (G.729 and G.711) services. Therefore, it is determined that the service experience is poor if the downlink traffic rate is less than 300 kbps or the uplink traffic rate is less than 100 kbps during busy hours. Through the network daily performance report, you can find out the sites where the traffic rate is low and user experience is bad. Perform preliminary determination on the measurement results of daily reports by referring to section 7.2.4"Capacity Expansion and Exception Thresholds." The following tables list the major problems that affect the network capacity and rate. Downlink: Symptom (Determination Basis) The average number of users in busy hours is more than 80. The traffic rate is low and the occupancy is high. Possible Cause The sector is congested. The traffic flow rate is too low. The sector is nearly congested. The coding efficiency is low. Handling Method Add carriers. Check the traffic flow configuration. Add carriers. Check co-frequency interference or coverage.
2013-7-9
Page 169 of 202
INTERNAL
The retransmission rate is high.
Check whether the error packet rate is high or the Ack messages are lost. Load the standard configuration for commercial application. Optimize the RF and adjust the downtilt and direction angle.
The coding efficiency is low.
The AMC is disabled.
The downlink AMC is disabled.
The difference between the rate of DL CINR < 12 dB and the rate of RSSI < -80 dBm is more than 20%. The difference between the rate of DL CINR < 12 dB and the rate of RSSI < -80 dBm is more than 30%. The CINR of a single user varies greatly.
The co-frequency interference exists.
The coverage is poor.
Add sites.
The MS reports the DL CINR exception value.
Feed back to MS engineers to locate the fault. Upgrade the version. Troubleshoot the fault. Configure PERMBASEID.
The The HARQ Ack loss is retransmission serious. rate is high. The retransmission rate drops after the measurement method is changed. The parameters are configured improperly.
The ultra wide coverage of the BS causes TDD interference. The DL CINR reported by the MS is virtual-high because PERMBASEID is not configured. The AMC threshold is too low. The target PER of the outer loop is too higher. The upper and lower thresholds of the outer loop are set improperly.
Set a higher AMC threshold. Adjust outer loop parameters.
The retransmission rate of all users is high.
The external interference exists (which cannot be suppressed even though the outer loop parameters are set to the upper limits).
Troubleshoot the fault.
2013-7-9
Page 170 of 202
INTERNAL
The retransmission rate of only users with poor signal quality is high.
The coverage is poor, causing MAP loss.
Add sites.
Uplink: Symptom (Determination Basis) The average number of users in busy hours is more than 80. Low traffic rate The uplink occupancy rate is high. Possible Cause The sector is congested. The sector is congested. The traffic flow rate is too low. The coding efficiency is low. The retransmission rate is high. Handling Method Add carriers. Add carriers. Check the traffic flow configuration. Check co-frequency interference or coverage. Check whether the configuration is incorrect or the signal quality is poor. Add sites and optimize the coverage. Enable open loop power control. Perform service experience tests on site. Load the standard configuration for commercial application. Add sites.
The uplink occupancy rate is low.
The user power is converged and slots are limited to maintain the higher order, which limits the actual rate. There are few application requirements.
The coding efficiency is low.
The AMC is disabled.
The uplink AMC is disabled.
The difference between the rate of DL CINR < 12 dB and the rate of RSSI < -80 dBm is more than 20%. There are few users, and the coding efficiency of some users is low.
The coverage is poor, and users are far away from BSs, or the path loss is large, thus causing uplink limit. There are few users under a sector, and some abnormal users cause the sector measurement deviation.
Visit abnormal users.
2013-7-9
Page 171 of 202
INTERNAL
Symptom (Determination Basis) The parameters are configured improperly.
Possible Cause The configured maximum power of the MS is less than the MS capability. The AMC threshold is too low. The target PER of the outer loop is too higher. The upper and lower thresholds of the outer loop are set improperly.
Handling Method Set MSTXPWRLMTLV L to the value of (maximum Tx power of the MS - 1). Set a higher AMC threshold. Adjust outer loop parameters.
The The parameters are retransmission configured improperly. rate is high.
The difference between the rate of DL CINR < 12 dB and the rate of RSSI < -80 dBm is more than 20%. The difference between the rate of DL CINR < 12 dB and the rate of RSSI < -80 dBm is more than 30%. The uplink slot limit is disabled.
The co-frequency interference degrades the DL CINR. The low CINR causes loss of MAP messages, thus resulting in retransmission. The poor coverage and the low CINR cause loss of MAP messages, thus resulting in retransmission. The uplink slot limit is disabled, which causes insufficient power of the MS. External interference exists. The coverage is poor, causing loss of MAP messages.
Optimize the RF and adjust the downtilt and direction angle.
Add sites.
Enable the slot limit.
The retransmission rate of all users is high. The retransmission rate of only users with poor signal quality is high.
Troubleshoot the fault. Add sites.
7.4.2 Analysis of DL User Experience

The criterion for measuring the downlink service experience of users is the traffic rate. To check the service experience, check whether the DL average traffic rate during busy hours has reached the preset value on the Carrier KPI sheet of the daily report. In the case of downlink service scheduling, the system load directly affects the service experience of users. If the traffic rate is low but the system load is high, it can be considered that the sector is nearly congested, degrading the average service experience of users.
2013-7-9
Page 172 of 202
INTERNAL
For the congested sites, check whether the capacity reaches the requirement by checking whether the UL/DL average throughput during busy hours reaches the preset value on the Carrier KPI sheet of the daily report.
If the UL/DL rate and throughput of the sector reaches the preset values of the network (the preset values are determined separately according to the actual situation of each site), the sector works properly, and the congestion is caused by the limited capacity or user capacity. In this case, capacity expansion is required. If the average throughput is low and does not reach the preset value, check whether the occupancy rate is high. If the occupancy rate is high but the average throughput is low, perform further troubleshooting on the site. For FFR sites, the same method can be used for analysis except that the two zones should be analyzed separately. In versions earlier than V3R2C03SPC300, the resource consumption caused by HARQ retransmission is not calculated in the DL occupancy rate. Therefore, in versions such as SPC103 and SPC205, the DL occupancy rate should be calculated according to the formula described in section 7.2.1"Major Factors Affecting Capacity." The possible causes for sector congestion or low traffic rate are as follows: 1. The traffic flow configuration or the CN configuration is improper. Check the traffic rate configured on the AAA and whether the rate-limited NEs exist in the system. A case ever happened in Philippines: one 1 Mbps (downlink) user gets only about 500 kbps. The troubleshooting results show that a forwarding server on the CN limits the rate based on the MAC address of the user. 2. The system overhead is high and many resources are occupied. The overhead indicates the resources occupied by the system. If the system overhead is lowered, more slots are available for users. Through the measurement entity DL common zone resource occupancy rate, check the DL overhead. Generally, in the case of repetition 2 in the 10 MHz PUSC with all SC network, the MAP resource occupancy rate is about 7 to 13% during busy hours, which is reasonable. Check whether HARQ subburst combination and UL common zone indication by UCD are enabled when the MS permits.
2013-7-9
Page 173 of 202
INTERNAL
Check whether relevant features such as compressed MAP and HARQ are enabled. Check whether the REP message is used to request reporting of DL signal quality. In addition to the resources occupied, the REP message is added with the map IE during delivery. Therefore, it can be reported through the CQICH to save resources. The related commands are as follows: LST RRMSOFT: PARANO=82; (subburst combination, if it is set to 3, it indicates both UL and DL subbursts are combined) LST RRMSOFT: PARANO=78; (UL common zone indication by UCD, the value 1 indicates that UL common zone is indicated by UCD) LST RRMSOFT: PARANO=27; (REP message, the value 0 indicates that REP message is disabled) LST CARRIERFRAMEINFO: SECTORID=0, CARRIERID=0; (whether MAPTYPE is set to COMPRESS) The HARQ parameters may be adjusted according to the actual situation of each site. Obtain the HARQ parameters from Huawei HQ. 3. The average coding efficiency is low. The average coding efficiency is related to features. For Philippine Globe project, the enabled features include MIMO-A, HARQ, IRC, and network access enhancement. According to the current feature configuration, if the DL average coding efficiency is less than 2, it indicates the DL coding of the sector is inefficient, and the average value is low. The criterion is related to features, and can be set according to the actual situation of each site. 4. The retransmission rate is high. When the retransmission rate is higher than the target PER of DL outer loop, the retransmission rate is high. When the residual error packet rate of the sector is more than 1%, the error packet rate is high even though the retransmission rate is low. The related command is as follows: LST PCAMCPARA: SECTORID=0, CARRIERID=0; (DLOUTLOOPPWRCTRL indicates the DL outer loop switch; HARQDLOUTPERTARGET indicates the target PER of DL outer loop; DLOUTERLOOPLOWTH indicates the lower limit of DL outer loop; DLOUTERLOOPUPTH indicates the upper limit of outer loop; ULOUTERLOOPPERHARQ indicates the target PER of UL outer loop; ULOUTERLOOPLOWTH indicates the adjustment lower limit; ULOUTERLOOPUPTH indicates the adjustment upper limit) 5. The system resources are not fully utilized. The DL resource reservation rate is 10% by default. If the DL resource reservation rate is too high, the system resources are not repeatedly used. Check whether P54 is set to 10. The command is as follows: LST RRMSOFT: PARANO=54; (resource reservation = 10)
7.4.3 Analysis of DL Coding Efficiency and Coverage

As mentioned in section 7.2.2"KPIs Related to Traffic Rate and Capacity", the average coding efficiency, without regard to HARQ retransmission, is independently used to represent the approximate average MCS mode of the user group being served. The average coding efficiency measures the actual coding efficiency allocated to users. It really reflects the overall MCS status after slots are allocated during the service time. Therefore, the average coding
2013-7-9
Page 174 of 202
INTERNAL
efficiency should be observed together with the retransmission rate. The abnormal sectors are as follows: 1. 2. Sectors with low average coding efficiency among the congested sites. Sectors with low average coding efficiency identified through the daily report, namely, the sectors whose DL coding efficiency is less than 2 on the Carrier KPI sheet of the daily report (if the MIMO is enabled in the UL and DL, the lower threshold of the coding efficiency should be raised, which can be set according to the actual situation of each site).
To locate the low coding efficiency problem, check the following causes: 3. The AMC is not enabled. If the DL AMC switch is not enabled, the coding efficiency is only 1. This can easily be found from the daily report. If the number of users is more than 10 but the coding efficiency is 1, the most possible cause is that AMC is not enabled. The command is as follows: LST RRMSWITCH: SECTORID=0, CARRIERID=0; (whether DLAMCSWITCH is enabled) 4. The AMC order number is not configured or the threshold is improperly set. If the order number is not configured or the threshold is improperly set, the average coding efficiency of the sector is abnormal. In this case, check whether the order number and the threshold are configured according to the commercial configuration of the network or the recommended values. The modification and maintenance of the threshold should be reviewed and recorded by the parameter committee at Huawei HQ. The maximum number of DL repetition times should be the same as the number of MAP repetition times. If the number of MAP repetition times is 2, repetition 4 and repetition 6 should be disabled. The commands are as follows: LST DCDBURSTPROFILE: SECTORID=0, CARRIERID=0; (whether the DL order number is set correctly) LST DLAMCTHRESH: SECTORID=0, CARRIERID=0; (whether the DL threshold is set correctly)
2013-7-9
Page 175 of 202
INTERNAL
5.
The signal quality is poor. On the Carrier KPI sheet of the daily performance report, Link Quality lists the proportional relationship of weak-coverage users, as shown in the following figure.
For DL coverage, check rate of DL CINR<= 12dB or rate of DL RSSI<=-80dBm. If the rate of DL RSSI<=-80dBm is high, the coverage is weak, thus causing the low coding efficiency. The recommended value of rate of DL RSSI<=-80dBm is 30%. If the difference between rate of DL CINR<= 12dB and rate of DL RSSI<=-80dBm is equal to or greater than 20%, many users under the sector have good RSSI but poor CINR. The possible cause of the low coding efficiency is the co-frequency interference. 6. The network topology structure is unreasonable. Check the following factors: Site height Direction angles and downtilt of the antenna Frequency planning Distance between sites For specific network planning rules. If the network topology causes capacity problems, re-planning is required. 7. The scheduling algorithm of the BS is improper. The resource-fair algorithm should be set to improve the average coding efficiency. If the rate-fair algorithm is set, the average coding efficiency is degraded by weakcoverage users. When the resource-fair algorithm is set, the filter factor should be set to 120. The command is as follows: LST MACCAPABILITY: SECTORID=0, CARRIERID=0; (whether MACALPHAVALUE is set to 120 and the resource-fair algorithm switch MACMCSSCHSWITCH is set to ON) 8. The maximum DL Tx power is not set. Check whether the maximum Tx power of the sector is set. The command is as follows:
2013-7-9
Page 176 of 202
INTERNAL
LST CARRIERBASICINFO: SECTORID=0, CARRIERID=0; (whether EIRP is set to 400) Analyze the abnormal results according to the actual onsite situation. For example, if only repetition 2 is supported in the DL, users with low CINR cannot be accessed. Then, the ratio of CINR < 0 or DL CINR ranging between 1 and 4 dB to the DL CINR distribution should be small; otherwise, exceptions may exist and should be located based on user-level data such as CHRs.
7.4.4 Analysis of DL Retransmission Rate

The high retransmission rate is the important factor that results in poor service experience and throughput degradation. If a large number of resources are consumed for retransmission, the service experience of users degrades. On the Carrier KPI sheet of the daily performance report, Link Quality lists the sites with high retransmission rate. For retransmission, both retransmission rate and error packet rate should be concerned. The retransmission rate reflects the overall trend. It measures the rough retransmission rate of all MSs under the sector, which is similar to the average value. The error packet rate indicates the rate of retransmission failures that cause application-layer retransmission. Though the result is small, the user experience is greatly affected.
Therefore, both counters should be concerned, and the requirement on the error packet rate should be stricter. To decrease the retransmission rate of the sector, analyze the following aspects: 1. The current parameter settings are too high. The parameters should be set according to the review conclusions of HQ to ensure that the parameters are suitable for the network. The AMC threshold is too low. The too low threshold causes a high retransmission rate, and the outer loop cannot provide protection. The target PER of the outer loop is too high. The default target PER is 10%. If the target PER is too high, the retransmission rate is high. The upper and lower thresholds of the outer loop are too low. When the retransmission rate is high, error bits cannot be suppressed even though the outer loop is set to the threshold. The parameter settings should be consistent with the review results of the baseline
INTERNAL
committee at Huawei HQ. If the parameter settings are not reviewed by the baseline committee, the parameter settings should be consistent with the onsite configuration baseline. The commands are as follows: LST DLAMCTHRESH: SECTORID=0, CARRIERID=0; (whether the DL threshold is too low) LST PCAMCPARA: SECTORID=0, CARRIERID=0; (DLOUTLOOPPWRCTRL indicates the DL outer loop switch; HARQDLOUTPERTARGET indicates the target PER of the DL outer loop; DLOUTERLOOPLOWTH indicates the lower threshold of DL outer loop; DLOUTERLOOPUPTH indicates the upper threshold of DL outer loop) 2. PERMBASEID is not configured, making the DL measurement results virtual-high. If PERMBASEID is not configured, the pilot measurement of the MS may be virtual-high. If the CINR for reporting pilot is set, the BS sets the MCS mode to a larger value, but the actual signal quality cannot support it, thus causing the higher retransmission rate. To solve this problem, set PERMBASEID according to the network planning. The temporary prevention method is to modify P51. P51 controls the measurement mode. It can be changed to 1 to request the MS to report the CINR of the preamble. The command is as follows: MOD RRMSOFT: PARANO=51, VALUE=1; (set to preamble measurement) 3. The ultra wide coverage of the BS causes TDD interference. In multiple sites in America, Australia, and Philippine, TDD interference occurs. As a result, the UL common zones are interfered, and Ack messages are lost, thus causing a high retransmission rate. In versions later than C03SPC300, check the measurement entity "Times of DL HARQ ACK Message Check Missing". If the value is large, UL common zone interference exists under the sector. To handle the UL common zone interference, see section 4.3"Interference Check." 4. The coverage is poor. If the retransmission rate of the sector is unrelated to the signal quality, that is, the retransmission rate of the MS with good signal quality is also high, check whether UL common zone interference exists and Ack messages are lost. For the sector where the retransmission rate is high, check the coverage status. If the coverage is poor, the rate of DL CINR < 12 dB is high, MAP messages are lost, and the MS with poor signal quality cannot receive its subbursts. As a result, the retransmission rate becomes higher. For the relevant criteria, see section 8.2.1"Capacity Expansion Criteria for V300R002C03." 5. External interference exists. Check the NI intensity and density of the sector from the daily performance report. If the measurement results of these two items are high, it indicates external interference frequently occurs.
7.4.5 Analysis of UL User Experience

The criterion for measuring the downlink service experience of users is the traffic rate. The standard traffic rate is 100 kbps. For the congested sites, check whether the capacity reaches the requirement by checking
2013-7-9
Page 178 of 202
INTERNAL
whether the UL/DL average throughput during busy hours reaches the preset value on the Carrier KPI sheet of the daily report. If the UL/DL rate and throughput of the sector reaches the preset values of the network (the preset values are determined separately according to the actual situation of each site), the sector works properly, and congestion occurs because the capacity limit of the sector is reached. In this case, capacity expansion is required.
If the average throughput does not reach the preset value, check whether the UL occupancy rate is high. If the occupancy rate is high but the average throughput is low, perform further troubleshooting on the site. Different from the DL occupancy rate measurement, the UL occupancy rate measurement includes the HARQ transmission. Therefore, the occupancy rate displayed on the network daily performance report is the actual occupancy rate of the sector, and no conversion is required. The UL public overhead (UL common zone) is fixed. Under the normal configuration, the first three symbols (six symbols in the FFR) are occupied and do not change with the number of users. Therefore, the system overhead affects only the DL throughput but does not change the UL throughput. The possible causes for sector congestion are as follows: 1. The average coding efficiency is low. The average coding efficiency is related to coverage. For the Philippine Globe project, the enabled features that are related to the UL coding efficiency include HARQ and error packet MCS reduction. According to the current feature configuration, if the UL average coding efficiency is less than 1.5, it indicates the coding efficiency of the sector is abnormal, and the average value is low. The criterion is related to features, and can be set according to the actual situation of each site. 2. The retransmission rate is high. When the retransmission rate is higher than the target PER of DL outer loop, the retransmission rate is high. When the residual error packet rate of the sector is more than 1%, the error packet
2013-7-9
Page 179 of 202
INTERNAL
rate is high even though the retransmission rate is low. The command is as follows: LST PCAMCPARA: SECTORID=0, CARRIERID=0; (ULOUTERLOOPPERHARQ indicates the target PER of UL outer loop); ULOUTERLOOPLOWTH indicates the lower limit; ULOUTERLOOPUPTH indicates the upper limit) If the resource occupancy rate is far below the congestion threshold but the traffic rate is still low, the possible causes are as follows: 1. UL limit is enabled. For UL services, the BS estimates the number of sub-carriers supported by the MS through the slot limit, and thus allocates the corresponding number of slots. If the UL signals are weak, few sub-carriers can be supported. As a result, the BS has residual resources but does not allocate them to the MS. Accordingly, the traffic rate cannot be improved. There is a special scenario of UL limit: When the power is converged when there is no UL service, the UL CINR is good, and thus the higher MCS mode is used. When the service is triggered, the number of slots calculated by the BS is small to keep the current MCS mode without generating error packets. According to the phenomenon, the UL MCS mode of the MS has more orders, the retransmission rate does not exceed the PER of outer loop, but the traffic rate is low. For UL limited users, the root cause is the poor coverage. In addition, add sites to optimize the (UL) signal quality of users. In addition, try to use the open loop power control. In this case, the MS automatically calculates the path loss and performs compensation, thus improving the service experience of users to some degree. The DL RSSI is the absolute criterion for measuring the coverage degree. If the DL coverage is poor, UL limit may occur due to the Tx power limit of the MS. The evaluation criterion is that the rate of DL RSSI < -80 dBm is more than 30%. 2. There are few traffic requirements. As described in section 8.3.1"Modifying the Networking Mode", WiMAX has few traffic requirements in the UL as a broadband application. If the measurement result is low because there are few services, the result is meaningless. Such a case should be identified through sector information. For example: The number of users under the sector is small, the UL throughput and DL throughput are low, and the UL occupancy rate does not exceed 30% (the occupancy rate of the UL common zone is 20% in the 10 MHz PUSC with all SC network). In this case, the traffic rate cannot be used for reference to determine that the service experience is poor. The most direct and accurate way to determine the traffic requirements of users is to perform onsite service experience tests.
7.4.6 Analysis of UL Coding Efficiency

As mentioned in section 7.2.2"KPIs Related to Traffic Rate and Capacity", the average coding efficiency, without regard to HARQ retransmission, is independently used to represent the approximate average MCS mode of the user group being served. The average coding efficiency measures the actual coding efficiency allocated to users. It really reflects the overall MCS status after slots are allocated during the service time. Therefore, the average coding efficiency should be observed together with the retransmission rate. The abnormal sectors are as follows: 1. Sectors with low average coding efficiency among the congested sites.
2013-7-9
Page 180 of 202
INTERNAL
2.
Sectors with low average coding efficiency identified through the daily report, namely, the sectors whose UL coding efficiency is less than 1.5 on the Carrier KPI sheet of the daily report (V3R3 supports UL MIMO; if this feature is enabled, the lower threshold of the coding efficiency should be raised, which can be set according to the actual situation of each site).
To locate the low coding efficiency, check the following causes: 1. The AMC is not enabled. If the DL AMC switch is not enabled, the coding efficiency is only 1. This can be easily found from the daily report. If the number of users is more than 10 but the coding efficiency is 1, the most possible cause is that AMC is not enabled. The command is as follows: LST RRMSWITCH: SECTORID=0, CARRIERID=0; (whether ULAMCSWITCH, DLAMCSWITCH, ULPWRCTRLMODE, and ULOUTERLOOPPOWERSWITCH are set to ON) 2. The AMC order number is not configured or the threshold is improperly set. If the order number is not configured or the threshold is improperly set, the average coding efficiency of the sector is abnormal. In this case, check whether the order number and the threshold are configured according to the commercial configuration of the network or the recommended values. The modification and maintenance of the threshold should be reviewed and recorded by the parameter committee at Huawei HQ. The command is as follows: LST UCDBURSTPROFILE: SECTORID=0, CARRIERID=0; (whether the UL order number is set correctly) LST ULAMCTHRESH: SECTORID=0, CARRIERID=0; (whether the UL threshold is set correctly) 3. The signal quality is poor. On the Carrier KPI sheet of the daily performance report, Link Quality lists the proportional relationship of weak-coverage users, as shown in the following figure.
2013-7-9
Page 181 of 202
INTERNAL
The AMC is determined according to the UL CINR. If the rate of UL CINR < 12 dB or the rate of UL RSSI < -85 dBm is high, the UL signal quality is poor, thus causing the low coding efficiency. In this case, sites should be added. The recommended value is 20%. 4. The network topology structure is unreasonable. Check the following factors: Site height Direction angles and downtilt of the antenna Frequency planning Distance between sites For specific network planning rules. If the network topology causes capacity problems, re-planning is required. 5. The scheduling algorithm of the BS is improper. The resource-fair algorithm should be set to improve the average coding efficiency. If the rate-fair algorithm is set, the average coding efficiency is degraded by weakcoverage users. When the resource-fair algorithm is set, the filter factor should be set to 120. The command is as follows: LST MACCAPABILITY: SECTORID=0, CARRIERID=0; (whether MACALPHAVALUE is set to 120 and the resource-fair algorithm switch MACMCSSCHSWITCH is set to ON) 6. The maximum Tx power is not set. MSTXPWRLMTLVL in ULCHANPARA is treated as the maximum Tx power of the MS by the BS. If the value of this parameter is too small, the power control and slot limit results are smaller, and the MS cannot work at the maximum Tx power. Check whether the value is suitable for the MS. Set it to the value of (maximum Tx power of the MS - 1). The command is as follows: LST ULCHANPARA: SECTORID=0, CARRIERID=0; (check the value of MSTXPWRLMTLVL) During the analysis of the coding efficiency and coverage, the UL analysis cannot follow
2013-7-9
Page 182 of 202
INTERNAL
the DL analysis rules completely. Due to the particularity of UL services, the Tx power of the MS is far lower than that of the BS. During scheduling, to avoid too many error packets, the BS calculates the power required for each sub-carrier based on the MCS for limiting the slots. The coding efficiency is high, which does not mean that the signal quality is good. When there is no service, the power is converged, and the higher MCS mode is used. When there is a service, slots are limited to keep the current MCS mode, and thus the number of allocated slots may be fewer. In this scenario, the maximum throughput and the number of supported users under the sector can be guaranteed, but the coding efficiency is high and the average traffic rate is low due to the power limit. Therefore, the UL signal quality cannot directly show the coverage of users. The DL RSSI should also be checked to determine the distance between the MS and the BS and the coverage. 7. Few abnormal MSs affect the measurement results of the sector. When there are few users under the sector, few abnormal users may have a great effect on the measurement results of the entire sector with regard to the frequency of UL services. When there are less than 10 users under the sector, perform analysis based on CHRs to determine whether the coding efficiencies of all MSs are low or few MSs with very low coding efficiency affect the average level of the entire sector.
7.4.7 Analysis of UL Retransmission Rate

The high retransmission rate is the important factor that results in poor service experience and throughput degradation. If a large number of resources are consumed for retransmission, the service experience of users degrades. On the Carrier KPI sheet of the daily performance report, Link Quality lists the sites with high retransmission rate. For retransmission, both retransmission rate and error packet rate should be concerned. The retransmission rate reflects the overall trend. It measures the rough retransmission rate of all MSs under the sector, which is similar to the average value. The error packet rate indicates the rate of retransmission failures that cause application-layer retransmission. Though the result is small, the user experience is greatly affected.
Therefore, both counters should be concerned, and the requirement on the error packet rate should be stricter.
2013-7-9
Page 183 of 202
INTERNAL
To decrease the retransmission rate of the sector, analyze the following aspects: 1. The current parameter settings are too high. The parameters should be set according to the review conclusions of HQ to ensure that the parameters are suitable for the network. The AMC threshold is too low: The too low threshold causes a high retransmission rate, and the outer loop cannot provide protection. The target PER of the outer loop is too high. The default target PER is 10%. If the target PER is too high, the retransmission rate is high. The upper and lower thresholds of the outer loop are too low. When the retransmission rate is high, error bits cannot be suppressed even though the outer loop is set to the threshold. The command is as follows: LST ULAMCTHRESH: SECTORID=0, CARRIERID=0; (whether the UL order number is too small) LST PCAMCPARA: SECTORID=0, CARRIERID=0; (ULOUTERLOOPPERHARQ indicates the target PER of UL outer loop); ULOUTERLOOPLOWTH indicates the lower limit; ULOUTERLOOPUPTH indicates the upper limit) 2. Slot limit is not enabled. In the case of slot limit, the UL resources are allocated according to the maximum number of supported sub-carriers when the UL CINR of the MS reaches the demodulation threshold, thus avoiding error bits due to insufficient power of the MS. If slot limit is disabled, the maximum Tx power is not concerned for UL resource allocation. In this case, if the number of allocated slots is beyond the capability of the MS, the UL power of the MS is insufficient, and error bits are generated. The command is as follows: LST PCAMCPARA: SECTORID=0, CARRIERID=0; (the UL slot limit switch SLOTLIMITSWITCH should be set to ON) 3. The coverage is poor. If the coverage of the sector is poor or co-frequency interference exists, the probability that the rate of DL CINR < 12 dB is high, and the MAP messages are lost becomes higher. As a result, the MS with poor signal quality cannot receive its subbursts, and the retransmission rate is higher. In the sector with few users, if the coverage of certain users is poor, the retransmission rate becomes particularly high, thus lowering the measurement result of the entire sector. Therefore, for a sector with less than 10 users, the CHRs should be analyzed to determine whether the high retransmission rate is caused by all or certain users under the sector. For the sector with poor coverage, add sites to solve this problem. Correspondingly, this operation also improves the service experience of DL users. 4. Interference exists. The BS has interference suppression measures such as outer loop and error packet MCS reduction. If the radio environment is poor, frequent changes occur, or the interference is too serious to be suppressed even when the outer loop is adjusted to the maximum value, the retransmission rate cannot be reduced below the target PER of outer loop. For the sector with high retransmission rate, you can check the NI intensity and density of the sector from the daily performance report. If the measurement values are high, obvious interference exists, and further troubleshooting is required.
2013-7-9
Page 184 of 202
INTERNAL
7.4.8 Transmission Verification

After the preceding analysis, it can be found that 80% of the sectors require capacity and traffic rate optimizations, but it is difficult to find out the external interference and transmission influences through only the daily report. For details on how to handle interference problems, see section 4.3"Interference Check." The following describes only how to handle transmission problems. Except frequent link interruption, it is difficult to identify transmission problems, especially intermittent interruption. Generally, you can identify transmission problems as follows: 1. 2. Analyze the transmission measurement in the daily performance report to determine the transmission status. Ping the BS through the GW on the M2000 and check the transmission packet loss. The GW command is as follows: PING: IP="signaling IP of the BS", NUM=50, PKTLEN=1500; 3. 4. Query history alarms to check whether the transmission problems occur. Contact transmission engineers to know about the transmission type, routing mode, and whether 2G/3G co-site is available.

This section describes advanced analysis methods and how to use the OMStar to locate traffic rate and capacity related problems. After finishing this section, you can analyze and handle traffic rate and capacity related problems.
7.5.1 Overview of Data Sources and Tools

Relevant Fields in CHR
The periodic CHR is the user-level performance measurement and records the traffic, throughput, number of slots occupied by each order, retransmission rate, error packet rate, and signal quality of users. The biggest advantage of the CHR is that the CHR allows user-level performance analysis and performance analysis, and the differences between MSs can be obviously analyzed to find out the abnormal MSs. The following table lists the key fields related to user services and traffic rate. CHR Counter Traffic of DL connection Throughput of the DL connection Service duration of DL connection Description Traffic of DL connection. Throughput of a single service connection. Service duration of the DL service CID.
2013-7-9
Page 185 of 202
INTERNAL
CHR Counter Number of slots occupied on each DL MCS DL RSSI Distribution DL CINR Distribution DL HARQ Air Interface PER DL HARQ Remnant PER Traffic of DL CID Traffic of UL connection Service duration of UL connection Number of slots occupied by each UL MCS UL RSSI Distribution UL CINR Distribution UL HARQ Air Interface PER UL HARQ Remnant PER
Description Number of slots occupied on each DL order, with MIMO-A and MIMO-B differentiated. Distribution of DL RSSI zones of a user. The measurement samples are reported by the MS. Distribution of DL CINRs of a user, at an accurate step of 1 dB. The measurement samples are reported by the MS. Rate of error packets over DL air interface of the MS. It is measured before HARQ retransmission. Residual error packet rate of the MS, namely, the proportion of error packets after HARQ retransmission. Traffic rate of the UL CID. Throughput of a single service connection. Service duration of the UL service CID. Number of slots occupied on each UL order, with MIMO-A and MIMO-B differentiated. Distribution of UL RSSI zones of a user. The samples are measured by the BS. Distribution of UL CINRs of a user, at an accurate step of 1 dB. The samples are measured by the BS. Rate of error packets over UL air interface of the MS. It is measured before HARQ retransmission. Residual error packet rate of the MS, namely, the proportion of error packets after HARQ retransmission.
Functions of the OMStar

The OMStar is a CHR analysis tool. With this tool, you can summarize the information about users on the network, analyze and discover problems, and locate problems from the perspective of users. The analysis items related to user rate include User Coverage Analysis and Traffic Rate Analysis.
User Coverage Analysis: contains three sheets, namely, User Distribution Analysis, Link Quality and Air Interface Resource Analysis, and Analysis of Single-User Coverage. User Distribution Analysis lists the number of abnormal users under NEs and basic information about users (including signal quality, error packet rate, and coding efficiency) based on the summarization time. Link Quality and Air Interface Resource Analysis categorizes user signal quality and lists the number of UL/DL CINRs, and the number of UL/DL RSSIs. It provides the most detailed information about the signal quality of users under sectors. Analysis of Single-User Coverage is the most direct summary of each user, including the UL/DL signal quality, error packet rate, average UL/DL coding efficiency,
2013-7-9
Page 186 of 202
INTERNAL
number of occupied UL/DL slots, and distribution of slot occupancy in each MCS mode.
Traffic Rate Analysis: contains three sheets, including Analysis of service speed statistic, Analysis of User Detail, and Analysis of Carrier Detail. Analysis of service speed statistic collects the number of users at different traffic rates by interval distribution. Analysis of User Detail provides user-level measurement and lists the traffic rate of each user and corresponding information. It can be used to analyze the causes of good or poor service experience. Analysis of Carrier Detail is a summary of carriers and lists the average signal quality, coding efficiency, average error packet, and traffic rate of all users under each carrier. You can directly determine whether the traffic rate of the carrier meets requirements on this sheet.
2013-7-9
Page 187 of 202
INTERNAL
For details on how to use the OMStar, see the OMATAR-Wi User Guide.
7.5.2 Traffic Rate Analysis

The preceding sections tell you how to find the measures to optimize the carrier traffic rate or capacity. Through CHRs, you can perform further analysis and detail the preceding analysis results at the user level. 1. Differences Caused by User Differentiation: Through CHRs, you can determine whether the discovered problem occurs to all users under the sector or is caused by certain users. If the performance of a sector varies greatly in different time segments of a day, you can analyze the users and their status in different time segments to locate the user(s) causing the obvious performance changes of the sector. Through CHRs, you can identify the status of all users under a sector at low coding efficiency and determine whether the problems happen to all users or are caused by various factors (such as co-frequency interference and poor coverage). If the retransmission rate of the sector is high, you can check the signal quality of the users at high retransmission rate through CHRs. If the signal quality of most users at high retransmission rate is poor, MAP messages are lost due to the poor coverage. If the retransmission rate of users at good signal quality is also high, the possible cause is that the UL common zones suffer interferences. 2. Select the typical users. Users under a sector can be categorized through CHR to select the typical users for tracing, optimization, and visit. For users with weak signals, large traffics, and many slots, the user experience may be still acceptable at the cost of a large number of system resources. These users can be identified through CHRs, and then visits and optimizations can be conducted. Similarly, users at high retransmission rate may have poor service experience. These
2013-7-9
Page 188 of 202
INTERNAL
users can also be identified through CHR, and then active care can be conducted.
7.5.3 Abnormal User Handling

For abnormal users discovered, perform the handling as follows: 1. CHR analysis A detailed analysis on a single user can be performed through CHRs. You can select User Complaint Analysis to trace and analyze each service and process of users.
User complaint analysis is a horizontal analysis based on users. It can be used to analyze the service status and information about a user at network entry based on the specified MAC address. The contents of user complaint analysis include Overview, Network Access Analysis, Network Exit Analysis, User Rate Analysis, User Quality Analysis, Source Side Handover Analysis, and Destination Side Handover Analysis. Through user complaint analysis, you can view the different states of the specified user in different time segments, thus finding the time segment or user state when exceptions occur. After the MS state or time segment when exceptions occur, you can enable user trace. By using the more detailed "recorder" method, you can obtain the MS states and perform a deeper analysis. 2. User trace User trace includes signaling trace and user trace. Through the traced user information, you can discover exceptions. Through the traced signaling, you can find out the step at which the process stops, thus locating and analyzing the problems. Some exceptions do not necessarily occur. You need to enable the trace task for a long time and wait until the exceptions occur before performing further analysis. Except the typical MSs, you can also trace several normal users and discover problems through information comparison.
2013-7-9
Page 189 of 202
INTERNAL

After the handling described in this chapter is complete, you can locate and solve 80% of the network capacity and rate problems. For the problems that are not solved, field engineers should feed back information to Huawei HQ for handling. For abnormal sectors and users, collect the basic data first. 1. 2. 3. Performance measurement of one week CHRs of the latest three days Carrier trace during busy hours. For carrier-level problems, if specific users cannot be located, select three users with different signal quality levels randomly for user trace and R1 signaling trace. If the abnormal MSs can be located, enable user trace and R1 signaling trace during busy hours or in time segments when exceptions occur. Additionally, select three other users randomly for user trace and R1 signaling trace. History alarms of the recent two weeks For user problems, provide the types and versions of abnormal MSs.
4.
5. 6.
Further analysis and BS data collect should be performed under the guidance of Huawei HQ. When reporting problems, describe the following contents: 1. 2. 3. 4. 5. Position, network planning parameters, and transmission mode of the site Whether known interferences or transmission problems exist Onsite analysis and location procedures and results Whether peripheral sites are normal or whether the same or other problems exist The problem descriptions should not be ambiguous. For example, use "the sector throughput is xx Mbps" instead of "the sector throughput is low"; use "the sector retransmission rate is xx%" instead of "the sector retransmission rate is high".
7.7 Appendix
7.7.1 Cases
In Philippine Globe, the DL throughput of the PANTOKQ site in full load is low and cannot reach the preset value 8 Mbps. The locating procedure is as follows: 1. 2. 3. Cause: The DL rate of the sector is low. Check the configuration: The power control AMC is enabled, outer loop is enabled, and scheduling mode is rate-fair. Analyze the congestion degree of the sector: If the DL occupancy rate of the sector mostly exceeds 80%, there are no residual resources, but the throughput is still low during busy hours, the problem is not caused by the insufficient occupancy rate. Check the retransmission rate: If the configuration is correct, there is no obvious problem about outer loop adjustment, and the retransmission rate of the sector is about 11% (which is similar to the target PER of DL outer loop), the problem is not caused by the retransmission rate. Check the coding efficiency: The coding efficiency of the three sectors of the site is only about 2 (exceptions are found).
4.
5.
2013-7-9
Page 190 of 202
INTERNAL
6. 7.
Check the DL CINR measurement. It is found that the values of Number of DL CINR<0 are large (exceptions are found). Through analysis, you may find that the major cause is the poor coverage or cofrequency interference. After analyzing the CHRs, however, you can find that the number of CINR > 20 and the number of CINR < 0 of certain MSs are large, which is unreasonable.
8.
Select the typical MSs for user trace and R1 signaling trace. It is found that MSs suddenly report "DL CINR = -3" (problem located).
Filter such users and select the typical MSs for locating. It is found that certain MSs continuously report "DL CINR = -3". The conclusions are as follows: The MS abnormally reports "DL CINR = -3". Based on this, the BS performs AMC determination and enables the MS to enter DL repetition 6. When the MS uses services in the lower MCS mode, the BS allocates a lot of slots to the user to ensure rate fair, thus degrading the coding efficiency of the sector. The solutions are as follows:
2013-7-9
Page 191 of 202
INTERNAL
The abnormal value reporting problem should be located and solved by MS engineers. Modify the configuration of the BS to disable DL repetition 4 and repetition 6. Change the scheduling mode to resource-fair mode. Replace the MSs of users who encounter serious abnormal value reporting problems.

Document Name DBS3900 V300R002C03 ARQ&HARQ Principles and Application Guide.doc DBS3900_V300R002C03 Guide to Principles and Applications for IRCMRC Adaptive Switchover.doc BS3900 V300R002C03 MultiAntenna Feature Principle and Application Guide.doc Content Describes the principles, network evaluation, relevant configuration, and test application of ARQ&HARQ. Describes the principles, network evaluation, relevant configuration, and test application of IRCMRC. Describes the principles, network evaluation, relevant configuration, and test application of multi-antenna features (MIMO-A, MIMO-B, and CSM). Describes the principles, network evaluation, relevant configuration, and test application of the power control and AMC feature. Describes the principles, network evaluation, relevant configuration, and test application of the admission and load control features. Application Scenario Common problem troubleshooting and configuration check Common problem troubleshooting and configuration check Common problem troubleshooting and configuration check Common problem troubleshooting and configuration check Common problem troubleshooting and configuration check
DBS3900 V300R002C03 Power Control and AMC Feature Principles and Application Guide.doc DBS3900 V300R002C03 Admission and Load Control Feature Principles and Application Guide.doc
2013-7-9
Page 192 of 202
INTERNAL
Capacity Management

After the WiMAX network is running for a certain period, the network traffic gets closer to the network design capacity and network resources are used up gradually, in service hot spots particularly, with the increase of usage. During network monitoring, field engineers can propose capacity expansion as soon as possible according to the actual network situation to avoid the network quality degradation and affect the network usage. This chapter tells field engineers how to monitor capacity counters and capacity expansion methods. The criteria are formulated on the basis of V32C03 and will be updated with the improvement of product capabilities.
8.2 Criteria for Capacity Expansion Based on Air Resource

8.2.1 Capacity Expansion Criteria for V300R002C03
The capacity criteria are based on carrier to facilitate comparison because the monitoring unit in the performance measurement is carrier. When measuring capacity counters, select the data of a busy time segment instead of the whole day. For the C03 version, monitor the following counters for one or two weeks. Capacity expansion is required when the UL or DL counters during busy hours of one week meet the following criteria for three or more times. 1. Capacity expansion criteria for C03 Criteria UL 1. Maximum Number Of Online Users > 80% of total users supported by the product (or the planned active users) 2. Uplink slot occupancy ratio > 70% Measur e Expand the capacity.
2013-7-9
Page 193 of 202
INTERNAL
Criteria 3. UL single BE user average traffic rate < minimum expected rate DL 1. Maximum Number of Online Users > 80% of total users supported by the product (or the planned active users) 2. Downlink slot occupancy ratio > 70% 3. DL single BE user average traffic rate < minimum expected rate
Measur e
Expand the capacity.
Only the average traffic rate of the BE service is used because the priority of the BE service is the lowest. Whether the carrier is congested can be reflected through the BE service when only the BE service or hybrid service is available. If no BE service flows are configured on the live network (for example, VoIP-only service), only the slot occupancy ratio and the number of active users need to be used. The minimum expected rate does not have an empiric value. The updated value can be obtained from the customer or user for each site. For example, in Philippine project, the customer requires the DL minimum rate of 300 kbps and the UL minimum rate of 100 kbps (when MIMO-B is disabled). Measurement Entities in the C03 Daily Performance Report The UL slot occupancy rate and DL slot occupancy rate can be obtained from uplink slot occupancy ratio(%)(busy time) and uplink slot occupancy ratio(%)(busy time) under Load Capacity of the C03 daily performance report.
2.
The maximum number of online users can be obtained from Maximum Number of Online Users(user)(busy time) under Load Capacity of the C03 performance measurement daily report.
2013-7-9
Page 194 of 202
INTERNAL
The UL and DL single user average traffic rate can be obtained from Carrier UL BE Average Traffic Rate(kbps)(busy time) and Carrier DL BE Average Traffic Rate(kbps)(busy time) under Traffic Speed of the C03 performance measurement daily report.
8.2.2 Capacity Expansion Parameter Optimization

Before hardware capacity expansion, optimize parameters by using performance measures (enabling features and checking parameter settings). 1. Enabling features Enable the outer loop power control. Enable the HARQ feature. Enable MIMO-B, IRC, and CSM. Check whether the network access enhancement feature is enabled and whether the repetition times are reasonable: In the PUSC with all SC network, enable the network access enhancement feature and use repetition 2; in the PUSC 1/3 network or FFR network, do not enable the network access enhancement feature. Scheduling type: The scheduling type varies with requirements. It is recommended to use the resource-fair scheduling mode to utilize resources reasonably and improve the throughput of the sector. 2. Checking parameter settings (ensure that the configuration of the congested sector is consistent with the commercial application configuration) Check whether the MCS mode is configured. For example, after Philippine Globe site was upgraded, the MCS modes DL 640QAM 1/2 and UL 16QAM 3/4 were lost. Check whether resource reservation is reasonable. Check that the threshold has been optimized and is not the default setting. Check whether the outer loop threshold is reasonable.
2013-7-9
Page 195 of 202
INTERNAL
8.3 Air Interface Capacity Expansion Methods

The air interface capacity expansion methods are as follows:

Modify the networking mode. Add sites. Use multiple carriers.
8.3.1 Modifying the Networking Mode

The methods of modifying the networking mode to improve the capacity are as follows: 1. 10 MHz PUSC with 1/3 1x3x1>10 MHz FFR 1x3x1 Capacity: The capacity is increased by about 30%. Risk: Pay attention to whether the MS supports the FFR function. 2. 10 MHz PUSC with 1/3 1x3x1>10 MHz PUSC with all 1x3x3 Capacity: The capacity is doubled. Risk: The operator should have enough frequency spectrum resources. 3. 5 MHz PUSC with all 1x3x3>10 MHz PUSC with all 1x3x3 Capacity: The capacity is doubled. Risk: The operator should have enough frequency spectrum resources. Consider whether the MSs adapt to 5 MHz and 10 MHz networking modes. If not, evaluate and modify the configuration risks of MSs.
8.3.2 Adding Sites

The methods of adding sites are as follows: 1. 2. Use small BSs in hot spot areas to increase the capacity, raise the signal strength, and improve service experience of users. Build macro sites, and reduce the power and downtilt of the original sites and new sites to make the original coverage area to be covered by two sites and increase the capacity and signal strength. When the capacity is insufficient, use the DAS or indoor Pico in buildings to expand the capacity.
3.
8.3.3 Using Multi-Carrier

When expanding the capacity by using multi-carrier, pay attention to the BS configuration. Currently, the RRU of the V32C02 version supports two-carrier 4T4R. The following figure shows the networking of the V32C02 version. Each BBU can be configured with up to four BBI boards, and each BBI board supports only three carriers. Each RRU has two CPRI ports. For a single BS, when there is only one carrier under each sector, only one BBI board is required; when there are two carriers under each sector, two BBI boards are required; and so on. When a certain sector needs to be expanded from a single carrier to multiple carriers, one BBI board needs to be added. The following describes the configurations of the BS in the two-carrier, three-carrier, and four-carrier networking.
2013-7-9
Page 196 of 202
INTERNAL
Figure 1.1 Appearances of the BBU3900 and the RRU3702
Configuration of the BS with Two Carriers

When the three sectors of a single BS are configured to two-carrier, the configuration of the BS is as follows: Configurati on Type Numbe r of BBI Boards 2 Numbe r of BMPT Boards 1 Numbe r of UPEU Boards 1 Numb er of RRUs 3 Number of Required CPRI Optical Modules (pair) 6
S(2/2/2) 4T4R
Note the following points: 2. Because a single sector uses two carriers, the power of each channel is evenly shared by carriers. In the case of two carriers per sector, the power of each carrier is only half of that under the full power/channel mode. For FDD bands, consider use the RRU filters on the same band for the same sector to save RRU filters. (30M product limitation)
3.
2013-7-9
Page 197 of 202
INTERNAL
Figure 3.1 Appearance of two carriers under general configuration
Configuration of the BS with Three Carriers

Currently, a single RRU of the V32C02 version supports only two carriers. The following table lists the BS configuration in the three-carrier networking. Configuration Numb Type er of BBI Boards S(3/3/3) 4T4R 3 Numbe r of BMPT Boards 1 Number of UPEU Boards Number of RRUs Number of Required CPRI Optical Modules (pair) 9
Note the following points: 4. The RRU of the current version supports only two carriers. Therefore, when a single sector supports three or more carriers, to support 4T4R/three carriers, two RRUs should be configured with external combiners. In this way, the combination loss is introduced. Usually, the loss of the cavity combiner is 1 dB. Because a single RRU has two carriers, the power of each channel is evenly shared by carriers. In the case of three carriers, one RRU is configured with two carriers, and one RRU is configured with the third carrier. The power of the RRU with two carriers is reduced by 3 dB. Therefore, the power of the RRU with the third carrier is also reduced by 3 dB to reach the coverage consistency of a single sector at the network planning stage. For the FDD bands, when there are more than three carriers under the same sector, external combiners (together with 4T4R) should be added for combination. Usually, the combiner requires large bandwidth. Therefore, under one sector, two carriers use the RRU filters on the same band and the third carrier can use a filter on another band (so long as the combiner supports these two bands).
5.
6.
2013-7-9
Page 198 of 202
INTERNAL
Configuration of the BS with Four Carriers

The following table lists the configuration of the BS with four carriers for the V32C02 version. Configuration Numb Type er of BBI Boards S(4/4/4) 4T4R 4 Numbe r of BMPT Boards 1 Number of UPEU Boards Number of RRUs Number of Required CPRI Optical Modules (pair) 12
Note the following points: 7. Similar to three-carrier networking, to support four carriers/sector and 4T4R at the same time, the external combiner should be configured (the loss of the cavity combiner is 1 dB). Because a single RRU has two carriers, the power of each channel is evenly shared by carriers. In the case of four carriers, the power of each carrier is half of the Tx power under full power/channel. Similar to three-carrier networking, for the FDD bands, under one sector, the first and second carriers use the RRU filters on the same band, whereas the third and fourth carriers can use the filters on another band (so long as the combiner supports these two bands).
8.
9.
2013-7-9
Page 199 of 202
INTERNAL
9
Project ID Reviewer Item Comment No. 1 Checklist
Checklist on Basic Activities of
Network Performance Management

(REPCHK01 V1.0 / for internal use only) Owner Date
Status
Comment
Do you set up and maintain network performance archives Yes [ ] (including the parameter configuration baseline, daily No [ ] performance report, weekly performance report, analysis report, network optimization report, interference optimization archive, NA [ ] and project engineering parameter table)? Do you read the WiMAX network performance management manuals completely? Yes [ ] No [ ] NA [ ] Yes [ ] No [ ] NA [ ] Yes [ ] No [ ] NA [ ] Yes [ ] No [ ] NA [ ]
Is a maintenance routine meeting held with relevant departments (for example, equipment department) every week?
Is there regular communication with customers (operators) to obtain network performance evaluations of customers?
Do you know about the progress about peripheral modules, for example, the running status and problem handling status of the BS?
2013-7-9
Page 200 of 202
INTERNAL
Is the network daily performance report output and analyzed every day to analyze the discovered network performance problems?
Yes [ ] No [ ] NA [ ]
Is the network weekly performance report output every week to Yes [ ] report the top N problems? No [ ] NA [ ] Are network performance problems recorded and traced according to the template? Does the problem closing rate exceed 50%? Yes [ ] No [ ] NA [ ]
Are users with problems reported to the operator periodically so Yes [ ] active care tests can be performed? No [ ] NA [ ] Are the definitions of network KPIs compliant with Huawei baseline? Are there any special indexes not included in the baseline? Yes [ ] No [ ] NA [ ]
10
11
Is there any network KPI commitment beyond the baseline? Are Yes [ ] relevant departments at Huawei HQ given early warnings? No [ ] NA [ ] Is the project parameter configuration baseline maintained regularly? Is the consistency between actual configuration and configuration baseline checked periodically? Is the network checked periodically for interference? Yes [ ] No [ ] NA [ ] Yes [ ] No [ ] NA [ ]
12
13
14
Are the interference optimization archives set up for interfered sites for problem tracing and closing?
Yes [ ] No [ ] NA [ ] Yes [ ] No [ ] NA [ ] Yes [ ] No [ ] NA [ ] Yes [ ] No [ ] NA [ ]
15
Is a service experience test conducted every week as required? Is a test report output according to the template?
16
Are there any MSs that do not pass Huawei IOT used on the network?
17
Are the complaints of end users effectively collected and delivered to Huawei?
2013-7-9
Page 201 of 202
INTERNAL
18
Are the complaints of end users recorded? Are the problems solved?
Yes [ ] No [ ] NA [ ] Yes [ ] No [ ] NA [ ]
19
Is confirmation with the users whose complaint problems are solved conducted by phone?
20
Is the network structure normalized and compliant with network Yes [ ] design specifications? No [ ] NA [ ] Is any incompliance produced due to external factor limitations (such as site acquisition and marketing competition strategy)? Are early warnings given? Is the single-frequency networking or two-frequency networking used? Do you seek help from technical support engineers at Huawei HQ? Is frequency clearance performed during network design? Are the network interferences traced? Yes [ ] No [ ] NA [ ] Yes [ ] No [ ] NA [ ] Yes [ ] No [ ] NA [ ] Yes [ ] No [ ] NA [ ]
21
22
23
24
Do you know about the network transmission status?
25
Are there any devices of other manufacturers used on the network?
Yes [ ] No [ ] NA [ ] Yes [ ] No [ ] NA [ ]
26
Is the RF optimization performed? Is any optimization report output?
2013-7-9
Page 202 of 202

WiMAX Network Performance Management Activities V1.0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WiMAX Network Performance Management Activities V1.0

Uploaded by

Copyright:

Available Formats

WiMAX Network Performance Management Activities V1.

2 Basic Concepts Related to Network Performance Management.......8

3 Daily Performance Monitoring.....................................................35

Huawei Technologies Proprietary