eRANAutomatic Congestion Handling Feature Parameter Description Issue 03 Date 2015-11-03 HUAWEI TECHNOLOGIES CO., LTD. Copyright © Huawei Technologies Co., Ltd. 2015. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd. Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders. Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied. Huawei Technologies Co., Ltd. Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China Website: http://www.huawei.com Email:
[email protected] Issue 03 (2015-11-03) Huawei Proprietary and Confidential i Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description Contents Contents 1 About This Document.................................................................................................................. 1 1.1 Scope.............................................................................................................................................................................. 1 1.2 Intended Audience.......................................................................................................................................................... 1 1.3 Change History............................................................................................................................................................... 1 1.4 Differences Between eNodeB Types.............................................................................................................................. 3 2 Overview......................................................................................................................................... 4 2.1 Introduction.................................................................................................................................................................... 5 2.2 Benefits........................................................................................................................................................................... 5 2.3 Architecture.................................................................................................................................................................... 5 3 Technical Description...................................................................................................................7 3.1 Procedure for Automatic Congestion Handling............................................................................................................. 8 3.2 Data Collection............................................................................................................................................................... 9 3.3 Trigger Condition Judgment.........................................................................................................................................10 3.4 Intelligent Optimization Functions and Parameter Adjustments..................................................................................11 3.5 Customization of Intelligent Optimization Rules......................................................................................................... 15 4 Related Features...........................................................................................................................17 4.1 Features Related to LOFD-081205 Automatic Congestion Handling..........................................................................17 5 Network Impact........................................................................................................................... 18 5.1 LOFD-081205 Automatic Congestion Handling......................................................................................................... 18 6 Engineering Guidelines............................................................................................................. 21 6.1 When to Use Automatic Congestion Handling............................................................................................................ 22 6.2 Required Information................................................................................................................................................... 22 6.3 Planning........................................................................................................................................................................ 23 6.4 Deployment.................................................................................................................................................................. 24 6.4.1 Requirements............................................................................................................................................................. 24 6.4.2 Data Preparation........................................................................................................................................................ 24 6.4.3 Precautions.................................................................................................................................................................29 6.4.4 Hardware Adjustment................................................................................................................................................29 6.4.5 Initial Configuration.................................................................................................................................................. 29 6.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs..................................................29 6.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs............................................................... 31 Issue 03 (2015-11-03) Huawei Proprietary and Confidential ii Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description Contents 6.4.5.3 Using the CME to Perform Single Configuration.................................................................................................. 31 6.4.5.4 Using MML Commands......................................................................................................................................... 32 6.4.5.5 MML Command Examples.................................................................................................................................... 33 6.4.6 Activation Observation..............................................................................................................................................34 6.4.7 Deactivation...............................................................................................................................................................35 6.5 Performance Monitoring...............................................................................................................................................36 6.6 Parameter Optimization................................................................................................................................................ 37 6.7 Troubleshooting............................................................................................................................................................ 39 7 Parameters..................................................................................................................................... 40 8 Counters........................................................................................................................................ 62 9 Glossary......................................................................................................................................... 66 10 Reference Documents............................................................................................................... 67 Issue 03 (2015-11-03) Huawei Proprietary and Confidential iii Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 1 About This Document 1 About This Document 1.1 Scope This document describes LOFD-081205 Automatic Congestion Handling, including its technical principles, related features, network impact, and engineering guidelines. Any managed objects (MOs), parameters, alarms, or counters described herein correspond to the software release delivered with this document. Any future updates will be described in the product documentation delivered with future software releases. This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD, and "eNodeB" refers to LTE FDD eNodeB. This document applies to the following types of eNodeBs. eNodeB Model Type Macro 3900 series eNodeB Micro BTS3202E LampSite DBS3900 LampSite 1.2 Intended Audience This document is intended for personnel who: l Need to understand the features described herein l Work with Huawei products 1.3 Change History This section provides information about the changes in different document versions. There are two types of changes: Issue 03 (2015-11-03) Huawei Proprietary and Confidential 1 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 1 About This Document l Feature change Changes in features and parameters of a specified version as well as the affected entities l Editorial change Changes in wording or addition of information and any related parameters affected by editorial changes. Editorial change does not specify the affected entities. eRAN8.1 03 (2015-11-03) This issue includes the following changes. Change Change Description Paramete Affected Type r Change Entity Feature Deleted the uplink synchronized user specifications None Macro, change in a cell from 3.2 Data Collection. For details about micro, the relevant specifications, see 3900 Series Base and Station Technical Description. LampSite eNodeBs Editorial None None - change eRAN8.1 02 (2015-04-30) This issue includes the following changes. Change Change Description Paramete Affected Type r Change Entity Feature Updated the maximum number of UL synchronized None Macro, change users supported by different BBP types. For details, micro, see 3.2 Data Collection. and LampSite eNodeBs Editorial None None - change eRAN8.1 01 (2015-03-23) This issue does not include any changes. eRAN8.1 Draft A (2015-01-15) This document is created for eRAN8.1. Issue 03 (2015-11-03) Huawei Proprietary and Confidential 2 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 1 About This Document 1.4 Differences Between eNodeB Types The features described in this document are implemented in the same way on macro, micro, and LampSite eNodeBs. Issue 03 (2015-11-03) Huawei Proprietary and Confidential 3 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 2 Overview 2 Overview LTE network load increases significantly at major events, such as sporting events, congregations, and parades. In severe scenarios, network congestion may occur, causing network performance and user experience to deteriorate. Network congestion occurs in the following scenarios: l Expected heavy-traffic scenarios, such as daily peak hours and sporting events l Unexpected heavy-traffic scenarios, such as parades If network congestion occurs, operators need to adjust network parameter settings to optimize network performance and improve user experience. When network congestion is mitigated, operators need to restore the original parameter settings. Modifying parameter settings is a demanding task because it involves a large number of NEs and parameters. Automatic Congestion Handling is designed to address network congestion under these circumstances. Automatic Congestion Handling enables the eNodeB to adaptively handle network congestion, modifying parameter settings in a timely manner and reducing maintenance costs. Issue 03 (2015-11-03) Huawei Proprietary and Confidential 4 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 2 Overview 2.1 Introduction Automatic Congestion Handling enables the eNodeB to periodically measure cell congestion status. The eNodeB adjusts parameter settings based on congestion conditions to mitigate cell congestion, improving network performance and user experience. An increasing number of users cause resource (mainly PRBs and PDCCH CCEs) congestion on an LTE network, and resource congestion results in degraded network performance and user experience. When the proportion of users with small-packet transmission (such as SRBs, TA packets, and heartbeat packets) increases in scheduling, PDCCH CCEs are very likely to become a resource bottleneck. That is, PDCCH CCEs are nearly exhausted but PRBs are still sufficient. This is because, in scheduling, users with small-packet transmission assigned high scheduling priorities consume the same number of PDCCH CCEs but fewer PRBs than users with large-packet transmission do. Automatic Congestion Handling is designed to reduce the consumed PDCCH CCEs and increase the utilization of PDCCH CCEs and PRBs, thereby improving network performance and user experience. 2.2 Benefits Automatic Congestion Handling provides the following benefits: l Adjusts the parameter settings based on the predefined intelligent optimization functions in event of network congestion to improve network performance and user experience. l Simplifies service guarantee and reduces manpower costs in heavy traffic scenarios. NOTE Intelligent optimization functions cannot eliminate hardware resource bottlenecks. 2.3 Architecture Automatic Congestion Handling is implemented on the eNodeB. Intelligent optimization functions have been predefined on the eNodeB. These functions specify when and how to adjust parameter settings to mitigate network congestion. The trigger conditions for parameter adjustment can be customized. The eNodeB periodically judges the trigger conditions specified by intelligent optimization functions on a one by one basis. If a trigger condition applies, the eNodeB implements the specified parameter adjustment. Figure 2-1 shows the architecture of Automatic Congestion Handling. Issue 03 (2015-11-03) Huawei Proprietary and Confidential 5 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 2 Overview Figure 2-1 Architecture of Automatic Congestion Handling Issue 03 (2015-11-03) Huawei Proprietary and Confidential 6 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 3 Technical Description 3 Technical Description This chapter describes how LOFD-081205 Automatic Congestion Handling works. For details about the engineering guidelines, see 6 Engineering Guidelines. Issue 03 (2015-11-03) Huawei Proprietary and Confidential 7 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 3 Technical Description 3.1 Procedure for Automatic Congestion Handling Figure 3-1 outlines the procedure for Automatic Congestion Handling. Figure 3-1 Procedure for Automatic Congestion Handling NOTE Each intelligent optimization function shown in Figure 3-1 includes two intelligent optimization rules: parameter adjustment and parameter restoration. For details, see 3.4 Intelligent Optimization Functions and Parameter Adjustments. The eNodeB monitors usage of specified resources, such as the number of admitted users, physical resource blocks (PRBs), and PDCCH control channel elements (CCEs). Based on the monitoring results and predefined trigger conditions, the eNodeB decides whether to trigger intelligent optimization functions. The procedure consists of the following three steps: 1. Data collection The eNodeB periodically collects data required for intelligent optimization functions. 2. Trigger condition judgment The eNodeB judges the trigger conditions for each intelligent optimization rule of an intelligent optimization function based on the collected data in a period. If a trigger condition applies, the eNodeB implements the specified parameter adjustment. If none of the trigger conditions apply, the current procedure ends and a new procedure starts in the next period. 3. Parameter adjustments according to intelligent optimization functions The eNodeB adjusts the parameters specified by the triggered intelligent optimization functions. The preceding procedure runs periodically. In this way, the eNodeB monitors the network load status and adaptively adjusts parameters, thereby maximizing network performance. NOTE If a parameter value has been changed to the target value in the previous period, the eNodeB will not change the parameter value again specified by a triggered intelligent optimization function in the current period. Issue 03 (2015-11-03) Huawei Proprietary and Confidential 8 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 3 Technical Description 3.2 Data Collection The eNodeB uses counters to periodically monitor the usage of specified resources, such as the number of admitted users, PDCCH CCEs, and PRBs. Based on the measurements of the counters, the eNodeB determines whether to trigger adaptive parameter adjustment. The measurement period is 5 minutes by default. Table 3-1 describes the required measurement items and their calculation formulas. Table 3-1 Required measurement items and their calculation formulas Measurement Definition Calculation Formula Item User_Spec_Occ Average number of L.Traffic.User.Ulsync.Avg/Maximum number upy_Rate UL synchronized of UL synchronized users in a cell users in a cell/ NOTE Maximum number of l The uplink synchronized user capacity in a cell UL synchronized varies with BBP types. For details about the users in a cell relevant specifications, see 3900 Series Base Station Technical Description. l If a board type changes, the eNodeB automatically calculates the user specification based on the new board type. l Micro eNodeBs support only the 5, 10, 15, and 20 MHz system bandwidths. The maximum number of UL synchronized users per cell for each system bandwidth is 200. PDCCH_CCE_ Number of used (L.ChMeas.CCE.CommUsed + Utilization_Rat CCEs/Total number L.ChMeas.CCE.ULUsed + e of available CCEs L.ChMeas.CCE.DLUsed)/(Number of CCEs per TTI when the maximum number of fixed PDCCH symbols is adopted x Number of TTIs in a measurement period) NOTE l This formula applies only when the PDCCH Symbol Number Adjust Switch parameter (parameter ID: CellPdcchAlgo.PdcchSymNumSwitch) is set to ON(On) or ECFIADAPTIONON(Enhanced CFI Adaption On), or when the PDCCH Symbol Number Adjust Switch parameter is set to OFF(Off) and the PDCCH Initial Symbol Number parameter (parameter ID: CellPdcchAlgo.InitPdcchSymNum) is set to the maximum number of symbols allowed by the eNodeB. l When the system bandwidth is 1.4 MHz, the maximum number of symbols is 4. For other system bandwidths, the maximum number of symbols is 3. Issue 03 (2015-11-03) Huawei Proprietary and Confidential 9 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 3 Technical Description Measurement Definition Calculation Formula Item DL_PRB_Utili Number of used L.ChMeas.PRB.DL.Used.Avg/ zation_Rate downlink PRBs/Total L.ChMeas.PRB.DL.Avail number of downlink PRBs UL_PRB_Utili Number of used L.ChMeas.PRB.UL.Used.Avg/ zation_Rate uplink PRBs/Total L.ChMeas.PRB.UL.Avail number of uplink PRBs The number of available CCEs when the maximum number of fixed PDCCH symbols is adopted depends on the system bandwidth and the value of PHICHCFG.PhichResource. When the system bandwidth is 1.4 MHz, the maximum number of fixed PDCCH symbols is 4. For other system bandwidths, the maximum number of fixed PDCCH symbols is 3. PHICHCFG.PhichResource is equivalent to Ng in 3GPP TS 36.211. The parameter value can be 1/6, 1/2, 1, and 2. Table 3-2 lists the corresponding number of available CCEs per TTI. Automatic Congestion Handling uses the number of available CCEs that correspond to Ng = 1. Table 3-2 Number of available CCEs when the maximum number of fixed PDCCH symbols is adopted System PHICHCFG.P PHICHCFG.P PHICHCFG.P PHICHCFG.P Bandwidth hichResource hichResource hichResource hichResource (MHz) = 1/6 = 1/2 =1 =2 20 87 86 84 80 15 65 64 62 59 10 43 42 41 39 5 21 21 20 19 3 12 12 12 11 1.4 6 6 6 6 3.3 Trigger Condition Judgment If the collected data described in 3.2 Data Collection meets the trigger condition for an intelligent optimization function described in 3.4 Intelligent Optimization Functions and Parameter Adjustments and the penalty time (specified by LIOptRule.PenaltyTime) has elapsed, the parameter adjustment specified by the intelligent optimization function is implemented. For details about the functions and parameter adjustments, see 3.4 Intelligent Optimization Functions and Parameter Adjustments. Issue 03 (2015-11-03) Huawei Proprietary and Confidential 10 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 3 Technical Description 3.4 Intelligent Optimization Functions and Parameter Adjustments The intelligent optimization functions of automatic congestion handling are predefined on the eNodeB. Each intelligent optimization function has two optimization rules, adjustment and restoration. Trigger conditions and parameter adjustment operations are configured in each intelligent optimization rule. Trigger conditions involve the measurement items listed in Table 3-1. You can run the MOD LIOPTATOMRULE command to configure the thresholds of trigger conditions. For details, see 6.4.5.4 Using MML Commands. Automatic Congestion Handling mitigates the impact of heavy traffic and restores the original network configurations when the traffic load becomes light. Therefore, an intelligent optimization function includes two rules: l Parameter adjustment when the traffic load increases l Parameter restoration when the traffic load decreases Parameter adjustment and restoration must be implemented based on the same measurement items but with different trigger conditions, preventing a parameter from being adjusted and restored at the same time. In addition, it is a good practice to retain a hysteresis for the trigger thresholds for parameter adjustment and restoration. The hysteresis prevents a parameter from being adjusted or restored repeatedly. You can run the LST LIOPTRULE command to list the intelligent optimization functions supported by Automatic Congestion Handling in the current release. The following sections describe the intelligent optimization functions supported by Automatic Congestion Handling in LTE TDD. The trigger conditions use default settings and are configurable. For details about how to modify a trigger condition, see 6.4.5.4 Using MML Commands. NOTE It is recommended that operators not manually adjust parameters through MML commands specified by intelligent optimization functions while intelligent optimization functions are taking effect. If a parameter is manually adjusted by operators and adaptively adjusted by an intelligent optimization function, the latest adjustment will take effect. If operators have to manually adjust a parameter, deactivate the corresponding intelligent optimization function first and then manually adjust the parameter. Function 2: Adaptive RBG Allocation In heavy traffic scenarios, the eNodeB adaptively allocates the resource block groups (RBGs) to reduce the consumed PDCCH CCEs and increase the downlink cell capacity. The eNodeB adaptively allocates the RBGs to meet data transmission requirements. If more than one RBG is required, the eNodeB rounds up the required number. For example, if the eNodeB calculates that 1.5 RBGs are required, it allocates two RBGs. If fewer than one RBG is required, the eNodeB allocates the required PRBs. For example, if two PRBs are required and they are not enough to compose an RBG, the eNodeB allocates two PRBs. Adaptive RBG allocation allows the eNodeB to schedule user data with minimum scheduling occurrences at the cost of a few PRBs. This function reduces the total number of scheduling occurrences on the network and lowers the consumed PDCCH CCEs. The following table describes the trigger conditions and corresponding parameter adjustments specified by the intelligent optimization rules. Issue 03 (2015-11-03) Huawei Proprietary and Confidential 11 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 3 Technical Description Rule ID Trigger Condition Parameter Adjustment 7 User_Spec_Occupy_Rate > The MOD CELLDLSCHALGO command is 50% executed with the RBG Resource Allocation and Strategy parameter set to ADAPTIVE(Adaptive). DL_PRB_Utilization_Rate < 90% 8 User_Spec_Occupy_Rate < The original parameter value is restored. 40% or DL_PRB_Utilization_Rate > 95% Function 3: Optimized Uplink PRB Allocation Policy Before the uplink PRB allocation policy is optimized, the uplink PRBs between neighboring cells overlap with each other, causing significant uplink interference. The optimized uplink PRB allocation policy randomizes the positions of uplink PRBs, reducing uplink interference and increasing uplink cell capacity. The following table describes the trigger conditions and corresponding parameter adjustments specified by the intelligent optimization rules. Rule ID Trigger Condition Parameter Adjustment 11 User_Spec_Occupy_Rate > The MOD CELLULSCHALGO command is 50% executed with the Uplink Resource Block and Allocation Strategy parameter set to FS_INRANDOM_ADAPTIVE(Fs InRandom UL_PRB_Utilization_Rate Strategy). > 20% 12 User_Spec_Occupy_Rate < The original parameter value is restored. 40% or UL_PRB_Utilization_Rate < 10% Function 4: Optimized TA The eNodeB maintains uplink timing for each UE so that the signals sent by all UEs can reach the eNodeB at the same time. Maintaining uplink timing is two-part: A UE sends the eNodeB uplink signals for timing advance (TA) measurement, and the eNodeB sends the UE a TA adjustment instruction. If a UE does not send the eNodeB uplink signals for TA measurement within a certain period, the eNodeB performs uplink scheduling for the UE so that the eNodeB can determine the TA for the UE through the demodulation reference signal (DMRS). Such uplink scheduling Issue 03 (2015-11-03) Huawei Proprietary and Confidential 12 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 3 Technical Description consumes PDCCH resources and uplink PRBs. In addition, the eNodeB periodically sends TA adjustment instructions to UEs to maintain uplink synchronization. This procedure also consumes PDCCH resources and downlink PRBs. If the traffic load is light, the eNodeB will have sufficient channel resources to maintain uplink timing for UEs, ensuring TA accuracy and service quality. If network congestion occurs, it is a good practice to enable the optimized TA function. This function reduces the uplink scheduling resources used for TA measurement through DMRS and lowers the transmission frequency of TA adjustment instructions, thereby reducing the consumed PDCCH CCEs and PRBs and increasing the cell capacity. If the transmission frequency of TA adjustment instructions decreases, UEs may enter the out- of-synchronization state. To avoid this situation, set TimeAlignmentTimer.TimeAlignmentTimer to INFINITY(Infinity) when you enable the optimized TA function. The following table describes the trigger conditions and corresponding parameter adjustments specified by the intelligent optimization rules. Rule ID Trigger Condition Parameter Adjustment 1 User_Spec_Occupy_Rate > The MOD TATIMER command is executed 50% with Timing Resource Optimization Switch and set to ON(On) and Uplink time alignment timer set to INFINITY(Infinity). The PDCCH_CCE_Utilization_ optimized TA function is enabled. Rate > 60% 2 User_Spec_Occupy_Rate < The original parameter value is restored. 40% or PDCCH_CCE_Utilization_ Rate < 25% Function 5: Detection and Scheduling for Abnormal UEs In the uplink, if the eNodeB detects 16 consecutive uplink CRC errors on a UE, the eNodeB stops uplink scheduling for the UE and resumes uplink scheduling when it receives a scheduling request (SR) from the UE. In the downlink, if the eNodeB detects 16 consecutive uplink discontinuous transmissions (DTXs) on a UE, the eNodeB stops downlink scheduling for the UE and resumes it when the uplink CRC result is correct or when periodic CQI reporting becomes normal on the PUCCH. This function enables the eNodeB to detect abnormal UEs and stop scheduling for them, preventing PRBs and PDCCH CCEs from being wasted by abnormal UEs. With this function, the eNodeB can schedule more services in heavy traffic scenarios, improving cell capacity. However, there is a low probability that the eNodeB incorrectly identifies abnormal UEs. If a UE is incorrectly identified as an abnormal UE, it will experience prolonged transmission delay, degraded user experience, and an increased probability of call drops. The following table describes the trigger conditions and corresponding parameter adjustments specified by the intelligent optimization rules. Issue 03 (2015-11-03) Huawei Proprietary and Confidential 13 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 3 Technical Description Rule ID Trigger Condition Parameter Adjustment 3 User_Spec_Occupy_Rate > The MOD CELLALGOSWITCH command is 50% executed with and AbnUeSchSwitch(AbnUeSchSwitch) selected under Cell Schedule Strategy Switch. The PDCCH_CCE_Utilization_ function of detection and scheduling for Rate > 60% abnormal UEs is enabled. 4 User_Spec_Occupy_Rate < The original parameter value is restored. 40% or PDCCH_CCE_Utilization_ Rate < 25% Function 6: PDCCH CCE Capacity Improvement The CCE aggregation level varies with UE channel conditions in scheduling. If the remaining consecutive CCEs cannot meet the aggregation level requirements, the eNodeB cannot schedule the corresponding UE. In this situation, CCE fragments are left and PDCCH CCEs cannot be fully utilized. PDCCH CCE capacity improvement enables the eNodeB to reallocate CCEs, in event of a CCE allocation failure for scheduling, by aggregating CCEs at a low level and increasing the transmit power. This processing mechanism has the same effect as high-level CCE aggregation. PDCCH CCE capacity improvement increases the CCE allocation success rate, improving the PDCCH CCE utilization and cell capacity. The following table describes the trigger conditions and corresponding parameter adjustments specified by the intelligent optimization rules. Rule ID Trigger Condition Parameter Adjustment 13 User_Spec_Occupy_Rate > The MOD CELLPDCCHALGO command is 50% executed with PDCCH Capacity Improve and Switch set to ON(On). PDCCH CCE capacity improvement is enabled. PDCCH_CCE_Utilization_ Rate > 60% 14 User_Spec_Occupy_Rate < The original parameter value is restored. 40% or PDCCH_CCE_Utilization_ Rate < 25% Function 7: Smart Control for Downlink Frequency Selective Scheduling Downlink frequency selective scheduling triggers large-scale aperiodic CQI reporting, consuming many uplink PRBs and CCEs and increasing uplink interference. In event of Issue 03 (2015-11-03) Huawei Proprietary and Confidential 14 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 3 Technical Description network congestion, disabling downlink frequency selective scheduling helps reduce the interference and increase the uplink cell capacity. However, disabling downlink frequency selective scheduling slightly decreases downlink cell throughput. The following table describes the trigger conditions and corresponding parameter adjustments specified by the intelligent optimization rules. Rule ID Trigger Condition Parameter Adjustment 5 User_Spec_Occupy_Rate > The MOD CELLALGOSWITCH command is 50% executed with FreqSelSwitch(FreqSelSwitch) and cleared under DL schedule switch. Downlink frequency selective scheduling is disabled. PDCCH_CCE_Utilization_ Rate > 60% 6 User_Spec_Occupy_Rate < The original parameter value is restored. 40% or PDCCH_CCE_Utilization_ Rate < 25% 3.5 Customization of Intelligent Optimization Rules Automatic Congestion Handling in the current release supports customization of intelligent optimization rules as follows: l Deactivating an intelligent optimization rule It is a good practice to deactivate an intelligent optimization rule if the parameter settings on the live network are the same as those specified by the intelligent optimization rule. This is to ensure that the active intelligent optimization rules are effective after Automatic Congestion Handling is enabled. You can run the ACT LIOPTRULE command to activate an intelligent optimization rule or DEA LIOPTRULE to deactivate an intelligent optimization rule. For details, see 6.4.5.4 Using MML Commands. l Disabling a trigger condition (referred to as an atom rule) for an intelligent optimization rule If a default atom rule for an intelligent optimization rule is too strict, the intelligent optimization rule will be difficult to apply. In this situation, you can disable the trigger condition to make the intelligent optimization rule be easily applied, thereby improving feature performance. NOTE If all of the atom rules of an intelligent optimization rule are disabled, the intelligent optimization rule is deactivated. l Modifying a trigger condition (referred to as an atom rule) for an intelligent optimization rule If a default atom rule for an intelligent optimization rule is too strict, you can modify the threshold of the atom rule, in addition to disabling it, to make the intelligent optimization rule be easily applied. Issue 03 (2015-11-03) Huawei Proprietary and Confidential 15 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 3 Technical Description If an atom rule for an intelligent optimization rule is too loose, the intelligent optimization rule will be applied too frequently, adversely affecting feature performance. In this situation, you can increase the value of the threshold for the atom rule. For details about how to customize the intelligent optimization rules, see 6.4.5 Initial Configuration. Issue 03 (2015-11-03) Huawei Proprietary and Confidential 16 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 4 Related Features 4 Related Features 4.1 Features Related to LOFD-081205 Automatic Congestion Handling Prerequisite Features None Mutually Exclusive Features None Impacted Features None Issue 03 (2015-11-03) Huawei Proprietary and Confidential 17 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 5 Network Impact 5 Network Impact 5.1 LOFD-081205 Automatic Congestion Handling System Capacity If the network is congested, insufficient PDCCH CCEs become a resource bottleneck. If PDCCH CCEs are exhausted, PRBs cannot be used for scheduling. Automatic Congestion Handling enables adaptive parameter adjustment in event of network congestion to reduce resource consumption, improving CCE utilization and increasing system capacity. The following are impacts of the intelligent optimization functions on system capacity in event of network congestion: l Adaptive RBG allocation This function enables the eNodeB to adaptively allocate the number of RBGs to meet the data transmission requirements. The eNodeB can schedule user data with a minimum number of scheduling occurrences at the cost of a few PRBs. This function reduces the total number of scheduling occurrences, lowers the number of consumed CCEs, and increases downlink cell capacity. l Optimized uplink PRB allocation policy This function enables the eNodeB to randomize the positions of allocated uplink PRBs, reducing the interference among neighboring cells and increasing uplink cell capacity. l Optimized TA This function enables the eNodeB to reduce the resources used for TA measurement and lower the transmission frequency of TA adjustment instructions, thereby reducing the consumed PDCCH CCEs and PRBs and increasing cell capacity. l Detection and scheduling for abnormal UEs This function enables the eNodeB to detect abnormal UEs and stop scheduling for abnormal UEs, preventing PRBs and CCEs from being wasted by abnormal UEs. The eNodeB can schedule more services in heavy traffic scenarios, increasing cell capacity. l PDCCH CCE capacity improvement This function enables the eNodeB to reallocate CCEs, in event of a CCE allocation failure for scheduling, by aggregating CCEs at a low level and increasing the transmit power. This function improves the PDCCH CCE utilization and increases cell capacity. Issue 03 (2015-11-03) Huawei Proprietary and Confidential 18 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 5 Network Impact l Smart control for downlink frequency selective scheduling This function enables the eNodeB to reduce aperiodic CQI reporting, thereby decreasing the consumed CCEs and uplink PRBs. This function helps reduce the uplink interference and increase uplink cell capacity. Network Performance The following are impacts of the intelligent optimization functions on network performance in event of network congestion: l Adaptive RBG allocation This function enables the eNodeB to schedule user data with a minimum number of scheduling occurrences at the cost of a few PRBs. In this way, this function improves downlink PRB utilization and increases downlink cell capacity. However, this function reduces the period of time for user data in the buffer and lowers the number of active users in a cell. In addition, this function may slightly decrease the average scheduled users number per TTI (SUNPT) in the downlink. l Optimized uplink PRB allocation policy This function reduces uplink interference among neighboring cells and increases uplink cell capacity. l Optimized TA This function enables the eNodeB to reduce the resources used for TA measurement and lower the transmission frequency of TA adjustment instructions, thereby reducing the consumed PDCCH CCEs and PRBs and increasing cell capacity. When this function applies, the average SUNPT in the cell may slightly decrease. This function also slightly decreases the TA accuracy of UEs, adversely affecting high-speed UE throughput. If the eNodeB cannot measure the TA through the sounding reference signal (SRS), PUCCH, or uplink data transmission when the transmission period for a TA adjustment instruction arrives, the eNodeB performs uplink scheduling for the UE to measure the TA through DMRS. In this situation, uplink interference may increase and RACH false alarms may occur, reducing the RACH access success rate. If the channel quality for the UE is too bad, uplink scheduling will cause uplink block errors, increasing the uplink block error rate (BLER). l Detection and scheduling for abnormal UEs This function helps increase the cell capacity. However, there is a low probability that the eNodeB incorrectly detects and schedules abnormal UEs. If a UE is incorrectly identified as an abnormal UE, it will experience prolonged transmission delay, degraded user experience, and an increased probability of call drops. l PDCCH CCE capacity improvement This function improves the PDCCH CCE utilization and cell capacity. However, the increase in the transmit power for CCEs may increase the interference against the corresponding symbols in neighboring cells, adversely affecting downlink throughput. l Smart control for downlink frequency selective scheduling This function helps reduce the uplink interference and increase the uplink cell capacity but decreases downlink cell capacity. The preceding intelligent optimization functions aim to reduce the consumed PDCCH CCEs and enable the eNodeB to meet the scheduling requirements of more users in event of PDCCH CCE insufficiency, thereby increasing PRB utilization and cell capacity. The scheduling requirements come from the users who have camped on the cell and the RRC Issue 03 (2015-11-03) Huawei Proprietary and Confidential 19 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 5 Network Impact connection setup requests from new users. If the PRB utilization increases in a cell, the interference against its neighboring cells increases and network performance may slightly fluctuate, such as the call drop rate, delay, and RACH access success rate. If an RRC connection setup request is rejected in a cell, subsequent RRC connection setup requests will also be rejected in the cell. Therefore, the rejected RRC connection setup requests increase. Issue 03 (2015-11-03) Huawei Proprietary and Confidential 20 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 6 Engineering Guidelines 6 Engineering Guidelines This chapter provides engineering guidelines for LOFD-081205 Automatic Congestion Handling. Issue 03 (2015-11-03) Huawei Proprietary and Confidential 21 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 6 Engineering Guidelines 6.1 When to Use Automatic Congestion Handling It is recommended that Automatic Congestion Handling be enabled in either of the following scenarios: l Unexpected network congestion, such as air interface resource congestion caused by a surge in the number of users l Expected network congestion caused by heavy traffic data For details about how to determine network congestion, see 6.2 Required Information. 6.2 Required Information Collect the following information before feature deployment: l Utilization of PDCCH CCEs and downlink PRBs in peak hours Evaluate the air interface resource load conditions. It is a good practice to activate the feature if PDCCH CCEs are insufficient and PRB usage is low. NOTE If PDCCH CCE usage is greater than 60% and downlink PRB usage is less than 90%, you can determine that PDCCH CCEs are insufficient and PRB usage is low. This is the recommended standard. For details about the calculation formula of measurement items, see 3.2 Data Collection. l Parameter settings on the live network Check parameter settings on the live network. Evaluate the feature performance and judge whether it is necessary to deactivate intelligent optimization functions. Table 6-1 describes when to deactivate intelligent optimization functions. Table 6-1 When to deactivate intelligent optimization functions Intelligent Deactivation Prerequisites MML Command to Optimization View Parameter Function ID Settings Adaptive RBG The CellDlschAlgo.RbgAllocStrategy LST allocation parameter has been set to CELLDLSCHALGO ADAPTIVE(Adaptive) before the feature is deployed. Optimized uplink The LST PRB allocation CellUlschAlgo.UlRbAllocationStrategy CELLULSCHALGO policy parameter has been set to FS_INRANDOM_ADAPTIVE(Fs InRandom Strategy) before the feature is deployed. Issue 03 (2015-11-03) Huawei Proprietary and Confidential 22 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 6 Engineering Guidelines Intelligent Deactivation Prerequisites MML Command to Optimization View Parameter Function ID Settings Optimized TA The TimeAlignmentTim- LST TATIMER er.TimingResOptSwitch parameter has been set to ON(On) and the TimeAlignmentTim- er.TimeAlignmentTimer parameter has been set to INFINITY(Infinity) before the feature is deployed. OR TimeAlignmentTim- er.TimingAdvCmdOptSwitch, TimeAlignmentTim- er.TimeAlignmentTimer, or TimeAlignmentTim- er.TimingMeasMode does not use the default settings. Detection and AbnUeSchSwitch(AbnUeSchSwitch) LST scheduling for has been selected under the CELLALGOSWITCH abnormal UEs CellAlgoSwitch.CellSchStrategySwitch parameter before the feature is deployed. PDCCH CCE The CellPdcchAlgo.PdcchCapacityIm- LST capacity proveSwitch parameter has been set to CELLPDCCHALGO improvement ON(On) before the feature is deployed. Smart control for FreqSelSwitch(FreqSelSwitch) has LST downlink been cleared under the CELLALGOSWITCH frequency CellAlgoSwitch.DlSchSwitch parameter selective before the feature is deployed. scheduling NOTE If an intelligent optimization function is implemented but does not have any effect, an event "Modify Cell-level Runtime Parameters" is still recorded in the SON logs. In this situation, it is a good practice to run the DEA LIOPTRULE command to deactivate the corresponding intelligent optimization rule. 6.3 Planning RF Planning N/A Network Planning N/A Issue 03 (2015-11-03) Huawei Proprietary and Confidential 23 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 6 Engineering Guidelines Hardware Planning N/A 6.4 Deployment 6.4.1 Requirements Operating Environment N/A Transmission Networking N/A License The operator has purchased and activated the license for the feature listed in the following table. Feature Feature Model License NE Sales Unit ID Name Control Item LOFD-08 Automatic LT1S000ACH Automatic eNodeB per eNodeB 1205 Congestion 00 Congestion Handling Handling (FDD) Other Requirements N/A 6.4.2 Data Preparation This section describes the data that you need to collect for setting parameters. Required data is data that you must collect for all scenarios. Collect scenario-specific data when necessary for a specific feature deployment scenario. There are three types of data sources: l Network plan (negotiation required): parameter values planned by the operator and negotiated with the evolved packet core (EPC) or peer transmission equipment l Network plan (negotiation not required): parameter values planned and set by the operator l User-defined: parameter values set by users Issue 03 (2015-11-03) Huawei Proprietary and Confidential 24 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 6 Engineering Guidelines Required Data NOTE A set of intelligent optimization rules for Automatic Congestion Handling has been predefined on the eNodeB. You only need to activate the feature license and set the feature switch. The following table describes the key parameter that must be set in the ENodeBAlgoSwitch managed object (MO) to configure the switch controlling Automatic Congestion Handling. Parameter Parameter ID Data Source Setting Notes Name Intelligent ENodeBAlgoSwitc Network plan It is a good practice to set this Optimizatio h.IOptAlgoSwitch (negotiation parameter to n not required) ACHSwitch(ACHSwitch) for sites Algorithm where network congestion is easy to Switch occur. Scenario-specific Data NOTE Use the following parameters to customize intelligent optimization rules. For details about customization scenarios, see 3.5 Customization of Intelligent Optimization Rules. The following table describes the parameters that must be set in the LIOptFunction MO to configure the name of an intelligent optimization function. Parameter Parameter ID Data Source Setting Notes Name Intelligent LIOptFunction.IO Network plan Indicates the ID of an intelligent Optimizatio ptFunctionID (negotiation optimization function. n Function not required) ID Intelligent LIOptFunction.IO User-defined Indicates the name of an intelligent Optimizatio ptFunctionName optimization function. All of the n Function names of intelligent optimization Name functions supported by the eNodeB have been pre-defined. You are advised to retain the default parameter value. The following table describes the parameters that must be set in the LIOptRule MO to configure an intelligent optimization rule. Issue 03 (2015-11-03) Huawei Proprietary and Confidential 25 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 6 Engineering Guidelines Parameter Parameter ID Data Source Setting Notes Name Rule ID LIOptRule.RuleID Network plan Indicates the ID of an intelligent (negotiation optimization rule. not required) Period LIOptRule.Period User-defined Indicates the evaluation period for an intelligent optimization rule. Both the default value and the recommended value are 300s. Currently, the conditions for determining whether to trigger an intelligent optimization rule is based on the traffic statistics measured at an interval of 5 minutes on the eNodeB. The rule cannot take effect quickly even though the value of this parameter is less than 300s. Therefore, it is recommended that the parameter be set to a value not less than 300s. Penalty LIOptRule.Penalty User-defined Indicates the penalty duration for an Time Time intelligent optimization rule. The penalty duration starts when the trigger conditions for an intelligent optimization rule are met and the eNodeB adjusts the parameters specified by the intelligent optimization rule. The penalty duration applies to all atom rules of the intelligent optimization rule. During the penalty period, the eNodeB does not adjust those parameters again even if the trigger condition for an atom rule of the intelligent optimization rule is met. If the parameter value is 0, no penalty is imposed on intelligent optimization rule. It is a good practice to retain the default value 300s. Issue 03 (2015-11-03) Huawei Proprietary and Confidential 26 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 6 Engineering Guidelines Parameter Parameter ID Data Source Setting Notes Name Adaptive LIOptRule.Adapti User-defined Indicates the radio access technology RAT veRAT to which an intelligent optimization rule applies. l If the parameter value is FDD, the intelligent optimization rule applies to FDD. l If the parameter value is TDD, the intelligent optimization rule applies to TDD. l If the parameter value is BOTH, the intelligent optimization rule applies to both FDD and TDD. The value of this parameter has been set for each predefined intelligent optimization rule on the eNodeB. If you want to apply a rule to only FDD or TDD when the default value is BOTH, the value can be changed to FDD or TDD. If the default value is FDD or TDD, the value does not need to be changed. The reason is that an intelligent optimization rule does not take effect even through its parameter value is changed. If this parameter value has been modified for an intelligent optimization rule, this parameter value for all the other intelligent optimization rules of the same intelligent optimization function must also be modified to the same value. The following table describes the parameters that must be set in the LIOptAtomRule MO to configure the atom rules of an intelligent optimization rule. Parameter Parameter ID Data Source Setting Notes Name Atom Rule LIOptAtomRule. Network plan Indicates the ID of an atom rule in ID AtomRuleID (negotiation an intelligent optimization rule. not required) Issue 03 (2015-11-03) Huawei Proprietary and Confidential 27 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 6 Engineering Guidelines Parameter Parameter ID Data Source Setting Notes Name Threshold LIOptAtomRule. User-defined Indicates the threshold for selecting for ThresholdforNum- a measurement object with a Numerical Para numerical value in an atom rule of Parameter an intelligent optimization rule. l If the measurement object is a percentage type, users only need to enter a number. For example, a parameter value of 30 indicates 30%. l If the measurement object is one of other types, the entered value is the actual value. An atom rule can be used as a trigger condition for more than one intelligent optimization rule. An intelligent optimization function includes two rules: parameter adjustment and parameter restoration. These two rules are mutually exclusive and therefore must have no overlapping trigger conditions. That way, a parameter will not be adjusted and restored at the same time. The allowed range of the parameter value is not specified because this parameter is used for different measurement objects. Understand the meaning of the specific measurement object when setting a value for this parameter. For example, if you set a negative value or a number greater than 100 for a percentage-type measurement object, the eNodeB will regard it invalid. You are advised not to modify this parameter. If you have to modify it, run the LST LIOPTRULEMEMBER command to view the intelligent optimization rules to be affected by modification. The following table describes the parameters that must be set in the LIOptRuleMember MO to configure the members of an intelligent optimization rule. Issue 03 (2015-11-03) Huawei Proprietary and Confidential 28 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 6 Engineering Guidelines Parameter Parameter ID Data Source Setting Notes Name Rule ID LIOptRuleMemb Network plan Indicates the ID of an intelligent er.RuleID (negotiation optimization rule corresponding to not required) an intelligent optimization rule member. Atom Rule LIOptRuleMemb Network plan Indicates the ID of an atom rule ID er.AtomRuleID (negotiation corresponding to an intelligent not required) optimization rule member. Active LIOptRuleMemb User-defined Indicates whether an intelligent Status er.ActiveStatus optimization rule member is activated. l If the parameter value is ACTIVATED, the atom rule is used as a trigger condition for the associated intelligent optimization rule. l If the parameter value is DEACTIVATED, the atom rule is not used as a trigger condition for the associated intelligent optimization rule. It is a good practice to retain the default value ACTIVATED. To make an atom rule not be used as a trigger condition for the associated intelligent optimization rule, run the MOD LIOPTRULEMEMBER command to modify the parameter value for the atom rule. 6.4.3 Precautions None 6.4.4 Hardware Adjustment N/A 6.4.5 Initial Configuration 6.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs Enter the values of the parameters listed in Table 6-2 in a summary data file, which also contains other data for the new eNodeBs to be deployed. Then, import the summary data file Issue 03 (2015-11-03) Huawei Proprietary and Confidential 29 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 6 Engineering Guidelines into the Configuration Management Express (CME) for batch configuration. For detailed instructions, see "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB, which is available in the eNodeB product documentation. The summary data file may be a scenario-specific file provided by the CME or a customized file, depending on the following conditions: l The managed objects (MOs) in Table 6-2 are contained in a scenario-specific summary data file. In this situation, set the parameters in the MOs, and then verify and save the file. l Some MOs in Table 6-2 are not contained in a scenario-specific summary data file. In this situation, customize a summary data file to include the MOs before you can set the parameters. Table 6-2 Parameter related to Automatic Congestion Handling MO Sheet in the Parameter Group Remarks Summary Data File ENodeBAlgoSwi User-defined sheet, Intelligent Set ACHSwitch to 1. tch such as eNodeB Optimization This parameter group Algorithm Switch. Algorithm Switch must be customized on a pattern-type sheet, whose name is user-defined. LIOptFunction User-defined sheet, Intelligent This parameter group such as Intelligent Optimization must be customized Optimization Function ID, on a pattern-type Function. Intelligent sheet, whose name is Optimization user-defined. Function Name LIOptRule User-defined sheet, Rule ID, Period, This parameter group such as Intelligent Penalty Time, must be customized Optimization Rule. Adaptive RAT, on a pattern-type Active Status sheet, whose name is user-defined. LIOptAtomRule User-defined sheet, Atom Rule ID, This parameter group such as Intelligent Threshold for must be customized Optimization Atom Numerical on a pattern-type Rule. Parameter sheet, whose name is user-defined. LIOptRuleMemb User-defined sheet, Rule ID, Atom Rule This parameter group er such as Intelligent ID, Active Status must be customized Optimization Rule on a pattern-type Member. sheet, whose name is user-defined. Issue 03 (2015-11-03) Huawei Proprietary and Confidential 30 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 6 Engineering Guidelines 6.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs Batch Reconfiguration Batch reconfiguration using the CME is the recommended method to activate a feature on existing eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure is as follows: Step 1 Customize a summary data file with the MOs and parameters listed in section "Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs." For online help, press F1 when a CME window is active, and select Managing the CME > CME Guidelines > LTE Application Management > eNodeB Related Operations > Customizing a Summary Data File for Batch eNodeB Configuration. Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME into the customized summary data file. Step 3 In the summary data file, set the parameters in the MOs according to the setting notes provided in 6.4.2 Data Preparation and close the file. Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station Bulk Configuration Data (CME client mode), to import the summary data file into the CME, and then start the data verification. Step 5 After data verification is complete, choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. For detailed operations, see Managing the CME > CME Guidelines > Script File Management > Exporting Incremental Scripts from a Planned Data Area in the CME online help. ----End 6.4.5.3 Using the CME to Perform Single Configuration On the CME, set the parameters listed in 6.4.2 Data Preparation for a single eNodeB. The procedure is as follows: Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window. Step 2 In area 1 shown in Figure 6-1, select the eNodeB to which the MOs belong. Issue 03 (2015-11-03) Huawei Proprietary and Confidential 31 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 6 Engineering Guidelines Figure 6-1 MO search and configuration window Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL. Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are displayed in area 4. Step 5 Set the parameters in area 4 or 5. Step 6 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. ----End 6.4.5.4 Using MML Commands l Common scenarios: Enabling ACH Step 1 Run the MOD ENODEBALGOSWITCH command with ACHSwitch(ACHSwitch) selected under the Intelligent Optimization Algorithm Switch parameter. ----End l (Optional) Special scenarios: Deactivating an intelligent optimization rule after ACH is enabled Step 1 Run the LST LIOPTRULE command to query the intelligent optimization rule that is associated with an operation. Step 2 Run the DEA LIOPTRULE command to deactivate the intelligent optimization rule. NOTE When deactivating an intelligent optimization rule, you are advised to deactivate another intelligent optimization rule with the same Intelligent Optimization Function ID. ----End Issue 03 (2015-11-03) Huawei Proprietary and Confidential 32 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 6 Engineering Guidelines l (Optional) Special scenarios: Disabling an atom rule of an intelligent optimization rule after ACH is enabled Step 1 Run the LST LIOPTRULE command to query the intelligent optimization rule that is associated with an operation. Step 2 Run the LST LIOPTRULEMEMBER command to query the ID of the atom rule that is associated with the intelligent optimization rule. Step 3 Run the MOD LIOPTRULEMEMBER command to disable the atom rule of intelligent optimization rule. NOTE If all of the atom rules of an intelligent optimization rule are disabled, the intelligent optimization rule is deactivated. ----End l (Optional) Special scenarios: Modifying an atom rule of an intelligent optimization rule after ACH is enabled Step 1 Run the LST LIOPTRULE command to query the intelligent optimization rule that is associated with an operation. Step 2 Run the LST LIOPTRULEMEMBER command to query the ID of the atom rule that is associated with the intelligent optimization rule. Step 3 Run the LST LIOPTATOMRULE command to query the trigger condition for the atom rule. Step 4 Run the MOD LIOPTATOMRULE command to modify the trigger condition for the atom rule. ----End 6.4.5.5 MML Command Examples //Common scenarios: Setting the ACHSwitch bit to 1 to enable ACH MOD ENODEBALGOSWITCH: IOptAlgoSwitch=ACHSwitch-1; // (Optional) Special scenarios: Deactivating an intelligent optimization rule after ACH is enabled LST LIOPTRULE: RuleID=3; DEA LIOPTRULE: RuleID=3; // (Optional) Special scenarios: Disabling an atom rule of an intelligent optimization rule after ACH is enabled LST LIOPTRULE: RuleID=1; LST LIOPTRULEMEMBER: AtomRuleID=1, RuleID=1; MOD LIOPTRULEMEMBER: RuleID=1, AtomRuleID=1, ActiveStatus=DEACTIVATED; // (Optional) Special scenarios: Modifying an atom rule of an intelligent optimization rule after ACH is enabled LST LIOPTRULE: RuleID=1; LST LIOPTRULEMEMBER: AtomRuleID=1, RuleID=1; LST LIOPTATOMRULE: AtomRuleID=1; MOD LIOPTATOMRULE: AtomRuleID=1, ThresholdforNumPara=30; Issue 03 (2015-11-03) Huawei Proprietary and Confidential 33 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 6 Engineering Guidelines 6.4.6 Activation Observation l Method 1: Viewing the SON logs on the U2000 client To use SON logs to verify whether Automatic Congestion Handling has been activated, perform the following steps: Step 1 On the U2000 client, choose SON > SON Log. Step 2 Click the Query SON Log tab and then click Synchronize in the lower right corner of the Query SON Log tab. In the displayed dialog box, select NEs and confirm. The logs start to be synchronized and a dialog box is displayed indicating the status of the synchronization. Step 3 After the synchronization is complete, set the log query criteria in the User-defined Conditions area in the left pane. l Set Log Category to LTE Automatic Congestion Handling Log. l In the Event Name area, select Set Automatic Congestion Handling Switch, Modify Cell-level Runtime Parameters, Recover Cell-level Runtime Parameters, Modify eNodeB-level Runtime Parameters, or Recover eNodeB-level Runtime Parameters. Step 4 Click Query. The logs that meet the query conditions are displayed on the log list in the right pane. Step 5 Double-click a record on the log list to view the details of the log in the displayed dialog box. ----End l Method 2: Running the MML commands to view the running values of parameters Automatic Congestion Handling modifies the running values of parameters, instead of the configured values in the database. In this situation, the running values may differ from the configured values. You can query the configured values of the parameters by running correlated LST commands and perform the following step to query the running values: Step 1 Run the DSP LIOPTRULE command to view the values of Action Type, Action, Local Cell ID, and Executive Status. Expected result: The value of Action Type for some intelligent optimization rules is MODIFY. l If the value of Executive Status for a parameter is UN-EXECUTED or EXECUTING, the running value of the parameter is the same as the configured value. In this situation, run a correlated LST command to query the configured value, which is also the running value of the parameter. l If the value of Executive Status for a parameter is EXECUTED, the parameter has been modified by Automatic Congestion Handling. In this situation, view the target value in the Action field, which is the running value of the parameter. Issue 03 (2015-11-03) Huawei Proprietary and Confidential 34 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 6 Engineering Guidelines NOTE The following are descriptions of fields in the command output of DSP LIOPTRULE. – Action Type: The value can be either MODIFY or RESUME. If it is MODIFY, the intelligent optimization rule is used to modify parameter values. If it is RESUME, the intelligent optimization rule is used to restore parameter values to the originally configured values. – Action: Indicates which and how parameters are modified when an intelligent optimization rule applies. This field does not take effect if Action Type is set to RESUME. – Local Cell ID: Indicates the ID of the cell to which intelligent optimization rules are applied. This field does not take effect for eNodeB-level intelligent optimization rules. – Executive Status: The value can be UN-EXECUTED, EXECUTING, and EXECUTED. UN-EXECUTED indicates that the intelligent optimization rule has not been executed. EXECUTING indicates that the intelligent optimization rule is being executed. EXECUTED indicates that the intelligent optimization rule has been executed. ----End 6.4.7 Deactivation Using the CME to Perform Batch Configuration Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for feature activation described in 6.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs. In the procedure, modify the parameter according to Table 6-3. Table 6-3 Parameter related to Automatic Congestion Handling MO Sheet in the Parameter Group Setting Notes Summary Data File ENodeBAlgoSwit User-defined sheet, Intelligent Set ACHSwitch to 0. ch such as eNodeB Optimization This parameter group Algorithm Switch. Algorithm Switch must be customized on a pattern-type sheet, whose name is user- defined. Using the CME to Perform Single Configuration On the CME, set parameters according to Table 6-3. For detailed instructions, see 6.4.5.3 Using the CME to Perform Single Configuration described for feature activation. Using MML Commands Step 1 Run the MOD ENODEBALGOSWITCH command with ACHSwitch(ACHSwitch) cleared under the Intelligent Optimization Algorithm Switch parameter. MOD ENODEBALGOSWITCH: IOptAlgoSwitch=ACHSwitch-0; ----End Issue 03 (2015-11-03) Huawei Proprietary and Confidential 35 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 6 Engineering Guidelines 6.5 Performance Monitoring After the feature is activated, monitor the feature performance and view the automatic operations as specified by intelligent optimization functions. The feature performance can be monitored through key performance indicators (KPIs), such as PRB utilization, PDCCH CCE utilization, uplink/ downlink cell throughput, and uplink/ downlink user throughput. The automatic operations can be viewed in SON logs. l Monitoring KPIs Table 6-4 KPIs used in performance monitoring KPI Calculation Formula DL PRB utilization L.ChMeas.PRB.DL.Used.Avg/L.ChMeas.PRB.DL.Avail UL PRB utilization L.ChMeas.PRB.UL.Used.Avg/L.ChMeas.PRB.UL.Avail PDCCH CCE (L.ChMeas.CCE.CommUsed + L.ChMeas.CCE.ULUsed utilization + L.ChMeas.CCE.DLUsed)/(Number of CCEs per TTI when the maximum number of fixed PDCCH symbols is adopted x Number of TTIs in a measurement period) DL cell throughput L.Thrp.bits.DL/L.Thrp.Time.Cell.DL.HighPrecision UL cell throughput L.Thrp.bits.UL/L.Thrp.Time.Cell.UL.HighPrecision DL user throughput (L.Thrp.bits.DL - L.Thrp.bits.DL.LastTTI)/ L.Thrp.Time.DL.RmvLastTTI UL user throughput (L.Thrp.bits.UL - L.Thrp.bits.UE.UL.SmallPkt)/ L.Thrp.Time.UE.UL.RmvSmallPkt Table 6-5 lists the counters used for calculating the KPIs in Table 6-4. Table 6-5 Counters used in KPI calculation Counter ID Counter Name Description 1526726737 L.ChMeas.PRB.UL.Used.Avg Average number of used uplink PRBs 1526726740 L.ChMeas.PRB.DL.Used.Avg Average number of used PDSCH PRBs 1526728434 L.ChMeas.PRB.UL.Avail Number of available uplink PRBs 1526728433 L.ChMeas.PRB.DL.Avail Number of available downlink PRBs 1526728303 L.ChMeas.CCE.CommUsed Number of PDCCH CCEs used for common DCI 1526728304 L.ChMeas.CCE.ULUsed Number of PDCCH CCEs used for uplink DCI Issue 03 (2015-11-03) Huawei Proprietary and Confidential 36 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 6 Engineering Guidelines Counter ID Counter Name Description 1526728305 L.ChMeas.CCE.DLUsed Number of PDCCH CCEs used for downlink DCI 1526728261 L.Thrp.bits.DL Total downlink traffic volume for PDCP SDUs in a cell 1526728259 L.Thrp.bits.UL Total uplink traffic volume for PDCP PDUs in a cell 1526728997 L.Thrp.Time.Cell.DL.HighPr Total duration of downlink data ecision transmission in a cell (with the precision of 1 ms) 1526728998 L.Thrp.Time.Cell.UL.HighPr Total duration of uplink data ecision transmission in a cell (with the precision of 1 ms) 1526729005 L.Thrp.bits.DL.LastTTI Downlink traffic volume sent in the last TTI for PDCP SDUs before the buffer is empty 1526729015 L.Thrp.Time.DL.RmvLastTT Data transmit duration except the last I TTI before the downlink buffer is empty 1526729415 L.Thrp.bits.UE.UL.SmallPkt Uplink traffic volume of PDCP PDUs scheduled for small packets 1526729416 L.Thrp.Time.UE.UL.RmvSm Uplink data transmission duration allPkt except that for small packets l Using the SON logs For detailed operations, see 6.4.6 Activation Observation. 6.6 Parameter Optimization After the feature is activated, you are advised to observe network performance and adjust the parameter listed in Table 6-6 for improvement in network performance. Issue 03 (2015-11-03) Huawei Proprietary and Confidential 37 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 6 Engineering Guidelines Table 6-6 Parameter that can be adjusted to improve network performance Paramete Parameter Adjustment Notes MML r Name ID Command Threshold LIOptAtom Indicates the threshold for selecting a MOD for Rule.Thresh measurement object with a numerical value LIOPTATO Numerical oldforNumP in an atom rule of an intelligent MRULE Parameter ara optimization rule. l If the measurement object is a percentage type, users only need to enter a number. For example, a parameter value of 30 indicates 30%. l If the measurement object is one of other types, the entered value is the actual value. An atom rule can be used as a trigger condition for more than one intelligent optimization rule. An intelligent optimization function includes two rules, one is for parameter adjustment and the other is for parameter restoration. These two rules are mutually exclusive and therefore must have no intersection on the trigger conditions, preventing a parameter from being adjusted and restored at the same time. The allowed range of the parameter value is not specified because this parameter is used for different measurement objects. Understand the meaning of the specific measurement object when setting a value for this parameter. For example, if you set a negative value or a number greater than 100 for a percentage-type measurement object, the eNodeB will regard it invalid. You are advised not to modify this parameter. If you have to modify it, run the LST LIOPTRULEMEMBER command to view the associated intelligent optimization rule, and then run the LST LIOPTRULE command to view the operation specified by the intelligent optimization rule. If the modification of this parameter causes parameter adjustment to be triggered when PDCCH CCEs are still sufficient, feature gains will become insignificant and the values of counters, such as the call drop rate, RACH success rate, and uplink/ Issue 03 (2015-11-03) Huawei Proprietary and Confidential 38 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 6 Engineering Guidelines Paramete Parameter Adjustment Notes MML r Name ID Command downlink cell throughput, may be adversely affected. 6.7 Troubleshooting In the current release, the eNodeB judges the atom rules for intelligent optimization rules based on the measurements of counters collected during each measurement period (5 minutes). If the measurements of counters in a measurement period are unreliable, the eNodeB discards the measurements, does not judge the atom rules in the measurement period, and waits for the measurements in the next measurement period. If the measurements are always unreliable, intelligent optimization functions will fail to take effect. In this situation, identify the reason why the measurements are unreliable and fix the problem. Issue 03 (2015-11-03) Huawei Proprietary and Confidential 39 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 7 Parameters 7 Parameters Table 7-1 Parameters MO Parame MML Feature Feature Description ter ID Comma ID Name nd CellPdc PdcchSy MOD LBFD-0 Physical Meaning: Indicates the switch used to enable or chAlgo mNumS CELLP 02003 / Channel disable dynamic adjustment on the number of witch DCCHA TDLBF Manage orthogonal frequency division multiplexing (OFDM) LGO D-00200 ment symbols occupied by the physical downlink control LST 3 channel (PDCCH). If this parameter is set to OFF, the CELLP number of OFDM symbols occupied by the PDCCH DCCHA is fixed and cannot be dynamically adjusted. If this LGO parameter is set to ON, the number of OFDM symbols occupied by the PDCCH is dynamically adjusted based on the required number of PDCCH control channel elements (CCEs). If this parameter is set to ECFIADAPTIONON, the number of OFDM symbols occupied by the PDCCH is dynamically adjusted based on the cell downlink throughput, and the adjustment performance is the best among the three methods. GUI Value Range: OFF(Off), ON(On), ECFIADAPTIONON(Enhanced CFI Adaption On) Unit: None Actual Value Range: OFF, ON, ECFIADAPTIONON Default Value: ON(On) Issue 03 (2015-11-03) Huawei Proprietary and Confidential 40 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 7 Parameters MO Parame MML Feature Feature Description ter ID Comma ID Name nd CellPdc InitPdcc MOD LBFD-0 Physical Meaning: Indicates the number of OFDM symbols chAlgo hSymNu CELLP 02003 / Channel initially occupied by the PDCCH. If the switch for m DCCHA TDLBF Manage dynamic adjustment of the number of OFDM symbols LGO D-00200 ment occupied by the PDCCH is turned off, this parameter LST 3 indicates the number of OFDM symbols that are CELLP always occupied by the PDCCH. For LTE TDD cells, DCCHA this parameter indicates the number of OFDM LGO symbols initially occupied by PDCCH where only the downlink scheduling and controlling information is transmitted in downlink subframes. If the switch for dynamic adjustment of the number of OFDM symbols occupied by the PDCCH is turned on and the bandwidth is 1.4 MHz or 3 MHz, the PDCCH occupies 4 or 3 OFDM symbols, respectively, and this parameter is invalid. If the switch is turned on and the bandwidth is 5 MHz, 10 MHz, 15 MHz, or 20 MHz, the eNodeB adjusts the number of OFDM symbols in the range of 1, 2, and 3 when this parameter is set to the default value 1, or in the range of 2 and 3 when this parameter is set to 2 or 3. For LTE TDD cells, if the switch is turned on and the bandwidth is 5 MHz, the eNodeB adjusts the number of OFDM symbols in the range of 2 and 3 by default, and this parameter is invalid. GUI Value Range: 1~4 Unit: None Actual Value Range: 1~4 Default Value: 1 PHICH PhichRe MOD LBFD-0 Physical Meaning: Cfg source PHICH 02003 / Channel Indicates a coefficient that is used to calculate the CFG TDLBF Manage resources used by the PHICH for the cell. It LST D-00200 ment corresponds to the Ng parameter in the protocol. PHICH 3 Compac CFG LOFD-0 t For details on the usage of the Ng parameter, see 01051 Bandwi 3GPP TS 36.211. LBFD-0 dth GUI Value Range: ONE_SIXTH, HALF, ONE, TWO 02009 / Broadca Unit: None TDLBF st of D-00200 system Actual Value Range: ONE_SIXTH, HALF, ONE, 9 informat TWO ion Default Value: ONE Issue 03 (2015-11-03) Huawei Proprietary and Confidential 41 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 7 Parameters MO Parame MML Feature Feature Description ter ID Comma ID Name nd LIOptR Penalty MOD LOFD-0 Automat Meaning: Indicates the penalty duration of intelligent ule Time LIOPTR 81205 ic optimization rules under an intelligent optimization ULE TDLOF Congesti function. If related conditions for an intelligent DSP D-08120 on optimization rule under an intelligent optimization LIOPTR 9 Handlin function are met and related adjustment measures are ULE g taken, the penalty duration starts. During the penalty Automat duration, parameter adjustment cannot be triggered LST even if conditions for an intelligent optimization rule LIOPTR ic Congesti under this intelligent optimization function are met. If ULE this parameter is set to 0, no penalty is imposed on on Handlin intelligent optimization rules under an intelligent g(TDD) optimization function. GUI Value Range: 0~65535 Unit: s Actual Value Range: 0~65535 Default Value: 300 TimeAli TimeAli MOD None None Meaning: Indicates the length of the uplink time gnment gnment TATIM alignment timer for UEs in the cell. A UE is Timer Timer ER considered not time-aligned in the uplink if the timer LST expires. TATIM GUI Value Range: SF500(500 subframes), SF750(750 ER subframes), SF1280(1280 subframes), SF1920(1920 subframes), SF2560(2560 subframes), SF5120(5120 subframes), SF10240(10240 subframes), INFINITY(Infinity) Unit: None Actual Value Range: SF500, SF750, SF1280, SF1920, SF2560, SF5120, SF10240, INFINITY Default Value: INFINITY(Infinity) ENodeB IOptAlg MOD LOFD-0 Automat Meaning: Indicates whether to enable intelligent AlgoSwi oSwitch ENODE 81205 ic optimization algorithms. This parameter includes the tch BALGO TDLOF Congesti following switches: ACHSwitch: If this switch is on, SWITC D-08120 on the eNodeB periodically determines whether to adjust H 9 Handlin parameters based on the predefined adaptive LST g parameter adjustment rules and adjusts parameters if ENODE Automat the predefined adaptive parameter adjustment rules BALGO ic are met. Therefore, network performance reaches the SWITC Congesti optimum in congestion scenarios. H on GUI Value Range: ACHSwitch(ACHSwitch) Handlin Unit: None g(TDD) Actual Value Range: ACHSwitch Default Value: ACHSwitch:Off Issue 03 (2015-11-03) Huawei Proprietary and Confidential 42 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 7 Parameters MO Parame MML Feature Feature Description ter ID Comma ID Name nd LIOptFe IOptFeat LST LOFD-0 Automat Meaning: Indicates the ID of the intelligent ature ureID LIOPTF 81205 ic optimization feature. EATUR TDLOF Congesti GUI Value Range: 0~65535 E D-08120 on Handlin Unit: None 9 g Actual Value Range: 0~65535 Automat Default Value: None ic Congesti on Handlin g(TDD) LIOptFe IOptFeat LST LOFD-0 Automat Meaning: Indicates the name of the intelligent ature ureNam LIOPTF 81205 ic optimization feature. e EATUR TDLOF Congesti GUI Value Range: 0~64 characters E D-08120 on Handlin Unit: None 9 g Actual Value Range: 0~64 Automat Default Value: NULL(empty string) ic Congesti on Handlin g(TDD) LIOptFu IOptFeat DSP LOFD-0 Automat Meaning: Indicates the ID of the intelligent nction ureID LIOPTF 81205 ic optimization feature. UNCTI TDLOF Congesti GUI Value Range: 0~65535 ON D-08120 on Handlin Unit: None LST 9 LIOPTF g Actual Value Range: 0~65535 UNCTI Automat Default Value: 1 ON ic Congesti on Handlin g(TDD) Issue 03 (2015-11-03) Huawei Proprietary and Confidential 43 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 7 Parameters MO Parame MML Feature Feature Description ter ID Comma ID Name nd LIOptFu IOptFun DSP LOFD-0 Automat Meaning: Indicates the ID of the intelligent nction ctionID LIOPTF 81205 ic optimization function. UNCTI TDLOF Congesti GUI Value Range: 0~65535 ON D-08120 on Handlin Unit: None LST 9 LIOPTF g Actual Value Range: 0~65535 UNCTI Automat Default Value: None ON ic Congesti on Handlin g(TDD) LIOptFu IOptFun DSP LOFD-0 Automat Meaning: Indicates the name of the intelligent nction ctionNa LIOPTF 81205 ic optimization function. me UNCTI TDLOF Congesti GUI Value Range: 0~64 characters ON D-08120 on Handlin Unit: None LST 9 LIOPTF g Actual Value Range: 0~64 UNCTI Automat Default Value: NULL(empty string) ON ic Congesti on Handlin g(TDD) LIOptFu LocalCe DSP LOFD-0 Automat Meaning: Indicates the ID of the cell with which nction llId LIOPTF 81205 ic intelligent optimization atom rules are applied. This UNCTI TDLOF Congesti parameter can only be queried by running the DSP ON D-08120 on LIOPTFUNCTION command. Information displayed 9 Handlin in the DSP LIOPTFUNCTION command output is g specific to the cell. This parameter setting does not Automat take effect when the MeasureObjType parameter is set ic to eNodeB. Congesti GUI Value Range: 0~255 on Unit: None Handlin g(TDD) Actual Value Range: 0~255 Default Value: None Issue 03 (2015-11-03) Huawei Proprietary and Confidential 44 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 7 Parameters MO Parame MML Feature Feature Description ter ID Comma ID Name nd LIOptFu Status DSP LOFD-0 Automat Meaning: Indicates the status of intelligent nction LIOPTF 81205 ic optimization atom rules. This parameter can only be UNCTI TDLOF Congesti queried by running the DSP LIOPTFUNCTION ON D-08120 on command. If this parameter value is NORMAL, the 9 Handlin intelligent optimization is in the normal state. If this g parameter value is PENALTY, the intelligent Automat optimization is under penalty, and all related ic intelligent optimization measures cannot be taken. Congesti GUI Value Range: NORMAL(Normal), on PENALTY(Penalty) Handlin Unit: None g(TDD) Actual Value Range: NORMAL, PENALTY Default Value: None LIOptFu Measure LST LOFD-0 Automat Meaning: Indicates the measurement object type in nction ObjType LIOPTF 81205 ic intelligent optimization atom rules. If this parameter is UNCTI TDLOF Congesti set to Cell, the measurement objects are cell-level ON D-08120 on atom rules. If this parameter is set to eNodeB, the 9 Handlin measurement objects are eNodeB-level atom rules. g GUI Value Range: Cell(Cell), eNodeB(eNodeB) Automat Unit: None ic Congesti Actual Value Range: Cell, eNodeB on Default Value: Cell(Cell) Handlin g(TDD) LIOptR Action DSP LOFD-0 Automat Meaning: ule LIOPTR 81205 ic Indicates the action that must be taken according to an ULE TDLOF Congesti intelligent optimization rule. LST D-08120 on LIOPTR 9 Handlin Note: When the network exits the heavy load status, ULE g the value of this parameter does not need to be Automat specified and the actual value restores to the value ic configured before optimization. In this case, the value Congesti of the ActionType parameter in the LIOptRule MO is on RESUME(RESUME) and the value of the Action Handlin parameter is NULL(empty string). g(TDD) GUI Value Range: 1~500 characters Unit: None Actual Value Range: 1~500 Default Value: NULL(empty string) Issue 03 (2015-11-03) Huawei Proprietary and Confidential 45 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 7 Parameters MO Parame MML Feature Feature Description ter ID Comma ID Name nd LIOptR ActionT DSP LOFD-0 Automat Meaning: Indicates the type of parameter adjustment ule ype LIOPTR 81205 ic when the trigger conditions in an intelligent ULE TDLOF Congesti optimization rule are met. If this parameter is set to LST D-08120 on MODIFY, the intelligent optimization rule is used to LIOPTR 9 Handlin modify parameters. If this parameter is set to ULE g RESUME, the intelligent optimization rule is used to Automat restore parameters to the initial settings. ic GUI Value Range: MODIFY(MODIFY), Congesti RESUME(RESUME) on Unit: None Handlin g(TDD) Actual Value Range: MODIFY, RESUME Default Value: MODIFY(MODIFY) LIOptR ActiveSt DSP LOFD-0 Automat Meaning: Indicates whether an intelligent ule atus LIOPTR 81205 ic optimization rule is activated. If the parameter value is ULE TDLOF Congesti set to ACTIVATED, the intelligent optimization rule is LST D-08120 on activated. If the parameter value is set to LIOPTR 9 Handlin DEACTIVATED, the intelligent optimization rule is ULE g deactivated and does not take effect. Automat GUI Value Range: ACTIVATED(ACTIVATED), ic DEACTIVATED(DEACTIVATED) Congesti Unit: None on Handlin Actual Value Range: ACTIVATED, DEACTIVATED g(TDD) Default Value: ACTIVATED(ACTIVATED) LIOptR Adaptiv MOD LOFD-0 Automat Meaning: Indicates the duplex mode to which an ule eRAT LIOPTR 81205 ic intelligent optimization rule applies. If this parameter ULE TDLOF Congesti is set to FDD, the intelligent optimization rule applies DSP D-08120 on to FDD. If this parameter is set to TDD, the intelligent LIOPTR 9 Handlin optimization rule applies to TDD. If this parameter is ULE g set to BOTH, the intelligent optimization rule applies Automat to both FDD and TDD. LST LIOPTR ic GUI Value Range: BOTH(BOTH), FDD(FDD), ULE Congesti TDD(TDD) on Unit: None Handlin g(TDD) Actual Value Range: BOTH, FDD, TDD Default Value: BOTH(BOTH) Issue 03 (2015-11-03) Huawei Proprietary and Confidential 46 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 7 Parameters MO Parame MML Feature Feature Description ter ID Comma ID Name nd LIOptR AtomRu DSP LOFD-0 Automat Meaning: Indicates the type of relationships between ule leRelati LIOPTR 81205 ic atom rules under an intelligent optimization rule. If onType ULE TDLOF Congesti this parameter is set to AND, optimization actions LST D-08120 on corresponding to the intelligent optimization rule are LIOPTR 9 Handlin triggered only when all atom rules under this ULE g intelligent optimization rule meet related Automat requirements. If this parameter is set to OR, ic optimization actions corresponding to the intelligent Congesti optimization rule are triggered when any atom rule on under this intelligent optimization rule meets related Handlin requirements. g(TDD) GUI Value Range: AND(AND), OR(OR) Unit: None Actual Value Range: AND, OR Default Value: AND(AND) LIOptR LocalCe DSP LOFD-0 Automat Meaning: Indicates the ID of the cell to which ule llId LIOPTR 81205 ic intelligent optimization atom rules are applied. This ULE TDLOF Congesti parameter can only be queried by running the DSP D-08120 on LIOPTRULE command. Information displayed in the 9 Handler DSP LIOPTRULE command output is specific to the Automat cell. This parameter setting does not take effect when ic the MeasureObjType parameter is set to eNodeB. Congesti GUI Value Range: 0~255 on Unit: None Handler( TDD) Actual Value Range: 0~255 Default Value: None LIOptR Executiv DSP LOFD-0 Automat Meaning: Indicates the state of parameter adjustment ule eStatus LIOPTR 81205 ic corresponding to an intelligent optimization rule. This ULE TDLOF Congesti parameter can only be queried by running the DSP D-08120 on LIOPTRULE command. If this parameter value is 9 Handlin UN-EXECUTED, parameter adjustment is not g performed. If this parameter value is EXECUTING, Automat parameter adjustment is being performed. If this ic parameter is EXECUTED, parameter adjustment has Congesti been performed. on GUI Value Range: UN-EXECUTED(UN- Handlin EXECUTED), EXECUTING(EXECUTING), g(TDD) EXECUTED(EXECUTED) Unit: None Actual Value Range: UN-EXECUTED, EXECUTING, EXECUTED Default Value: None Issue 03 (2015-11-03) Huawei Proprietary and Confidential 47 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 7 Parameters MO Parame MML Feature Feature Description ter ID Comma ID Name nd LIOptR IOptFun DSP LOFD-0 Automat Meaning: Indicates the ID of the intelligent ule ctionID LIOPTR 81205 ic optimization function. ULE TDLOF Congesti GUI Value Range: 0~65535 LST D-08120 on Handlin Unit: None LIOPTR 9 ULE g Actual Value Range: 0~65535 Automat Default Value: 1 ic Congesti on Handlin g(TDD) LIOptR Period MOD LOFD-0 Automat Meaning: Indicates the evaluation period of an ule LIOPTR 81205 ic intelligent optimization rule. ULE TDLOF Congesti GUI Value Range: 0~65535 DSP D-08120 on Handlin Unit: s LIOPTR 9 ULE g Actual Value Range: 0~65535 LST Automat Default Value: 300 LIOPTR ic ULE Congesti on Handlin g(TDD) LIOptR RuleID ACT LOFD-0 Automat Meaning: Indicates the ID of an intelligent ule LIOPTR 81205 ic optimization rule. ULE TDLOF Congesti GUI Value Range: 0~65535 DEA D-08120 on Handlin Unit: None LIOPTR 9 ULE g Actual Value Range: 0~65535 DSP Automat Default Value: None LIOPTR ic ULE Congesti on LST Handlin LIOPTR g(TDD) ULE MOD LIOPTR ULE Issue 03 (2015-11-03) Huawei Proprietary and Confidential 48 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 7 Parameters MO Parame MML Feature Feature Description ter ID Comma ID Name nd LIOptAt AtomRu LST LOFD-0 Automat Meaning: Indicates the ID of an intelligent omRule leID LIOPTA 81205 ic optimization atom rule. TOMR TDLOF Congesti GUI Value Range: 0~65535 ULE D-08120 on Handlin Unit: None MOD 9 LIOPTA g Actual Value Range: 0~65535 TOMR Automat Default Value: None ULE ic Congesti on Handlin g(TDD) LIOptAt Conditio LST LOFD-0 Automat Meaning: Indicates the relationship between omRule nType LIOPTA 81205 ic measurement objects and thresholds in intelligent TOMR TDLOF Congesti optimization atom rules. The parameter values ULE D-08120 on BIGGERTHAN, EQUALTO, SMALLERTHAN, 9 Handlin SMALLERTHANOREQUALTO, g BIGGERTHANOREQUALTO, and NOTEQUALTO Automat indicate the conditions of greater than, equal to, ic smaller than, smaller than and equal to, greater than Congesti and equal to, and not equal to, respectively. on GUI Value Range: BIGGERTHAN(BIGGERTHAN), Handlin EQUALTO(EQUALTO), g(TDD) SMALLERTHAN(SMALLERTHAN), SMALLERTHANOREQUAL- TO(SMALLERTHANOREQUALTO), BIGGERTHANOREQUAL- TO(BIGGERTHANOREQUALTO), NOTEQUALTO(NOTEQUALTO) Unit: None Actual Value Range: BIGGERTHAN, EQUALTO, SMALLERTHAN, SMALLERTHANOREQUALTO, BIGGERTHANOREQUALTO, NOTEQUALTO Default Value: BIGGERTHAN(BIGGERTHAN) Issue 03 (2015-11-03) Huawei Proprietary and Confidential 49 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 7 Parameters MO Parame MML Feature Feature Description ter ID Comma ID Name nd LIOptAt Measure LST LOFD-0 Automat Meaning: Indicates the measurement object in omRule Object LIOPTA 81205 ic intelligent optimization atom rules. If this parameter is TOMR TDLOF Congesti set to USER_SPEC_OCCUPY_RATE, the ULE D-08120 on measurement object is the ratio of uplink 9 Handlin synchronized UEs to the total UEs. If this parameter is g set to UL_PRB_UTILIZATION_RATE, the Automat measurement object is uplink physical resource block ic (PRB) usage. If this parameter is set to Congesti DL_PRB_UTILIZATION_RATE, the measurement on object is the downlink PRB usage. If this parameter is Handlin set to PDCCH_CCE_UTILIZATION_RATE, the g(TDD) measurement object is the control channel element (CCE) usage on the PDCCH. GUI Value Range: USER_SPEC_OCCUPY_RATE(USER_SPEC_OCC UPY_RATE), UL_PRB_UTILIZATION_RATE(UL_PRB_UTILIZ ATION_RATE), DL_PRB_UTILIZATION_RATE(DL_PRB_UTILIZ ATION_RATE), PDCCH_CCE_UTILIZATION_RATE(PDCCH_CCE _UTILIZATION_RATE) Unit: None Actual Value Range: USER_SPEC_OCCUPY_RATE, UL_PRB_UTILIZATION_RATE, DL_PRB_UTILIZATION_RATE, PDCCH_CCE_UTILIZATION_RATE Default Value: USER_SPEC_OCCUPY_RATE(USER_SPEC_OCC UPY_RATE) LIOptAt Measure LST LOFD-0 Automat Meaning: Indicates the measurement object type in omRule ObjType LIOPTA 81205 ic intelligent optimization atom rules. If this parameter is TOMR TDLOF Congesti set to Cell, the measurement objects are cell-level ULE D-08120 on atom rules. If this parameter is set to eNodeB, the 9 Handlin measurement objects are eNodeB-level atom rules. g GUI Value Range: Cell(Cell), eNodeB(eNodeB) Automat Unit: None ic Congesti Actual Value Range: Cell, eNodeB on Default Value: Cell(Cell) Handlin g(TDD) Issue 03 (2015-11-03) Huawei Proprietary and Confidential 50 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 7 Parameters MO Parame MML Feature Feature Description ter ID Comma ID Name nd LIOptAt Threshol MOD LOFD-0 Automat Meaning: Indicates the threshold for selecting omRule dforNu LIOPTA 81205 ic measurement objects with numerical values in mPara TOMR TDLOF Congesti intelligent optimization atom rules. ULE D-08120 on GUI Value Range: -2147483647~2147483647 LST 9 Handlin g Unit: None LIOPTA TOMR Automat Actual Value Range: -2147483647~2147483647 ULE ic Default Value: 0 Congesti on Handlin g(TDD) LIOptR ActiveSt MOD LOFD-0 Automat Meaning: Indicates whether an intelligent uleMem atus LIOPTR 81205 ic optimization rule member is activated. If this ber ULEME TDLOF Congesti parameter is set to ACTIVATED, the intelligent MBER D-08120 on optimization atom rules apply to the evaluation of the LST 9 Handlin associated intelligent optimization rule. If this LIOPTR g parameter is set to DEACTIVATED, the intelligent ULEME Automat optimization atom rules do not apply to the evaluation MBER ic of the associated intelligent optimization rule. Congesti GUI Value Range: ACTIVATED(ACTIVATED), on DEACTIVATED(DEACTIVATED) Handlin Unit: None g(TDD) Actual Value Range: ACTIVATED, DEACTIVATED Default Value: ACTIVATED(ACTIVATED) LIOptR RuleID LST LOFD-0 Automat Meaning: Indicates the ID of the intelligent uleMem LIOPTR 81205 ic optimization rule to which the intelligent optimization ber ULEME TDLOF Congesti rule members associated. MBER D-08120 on GUI Value Range: 0~65535 MOD 9 Handlin g Unit: None LIOPTR ULEME Automat Actual Value Range: 0~65535 MBER ic Default Value: None Congesti on Handlin g(TDD) Issue 03 (2015-11-03) Huawei Proprietary and Confidential 51 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 7 Parameters MO Parame MML Feature Feature Description ter ID Comma ID Name nd CellDlsc RbgAllo MOD LBFD-0 Basic Meaning: For services whose QoS class identifier hAlgo cStrateg CELLD 02025/ Scheduli (QCI) is not 1: When this parameter is set to y LSCHA TDLBF ng ROUND_DOWN: (1) If the number of required LGO D-00202 Dynami resource block groups (RBGs) is less than 1, the LST 5 c actual number of RBs are allocated to UEs at the CELLD LOFD-0 Scheduli current transmission time interval (TTI); (2) If the LSCHA 0101502 ng number of required RBGs is greater than N but less LGO / than N+1 (N is greater than or equal to 1), RBs of N TDLOF RBGs are allocated to UEs in the current TTI and the D-00101 other required RBs are allocated to UEs in the next 502 TTI. Setting this parameter to ROUND_DOWN ensures full utilization of RBs, but increases scheduling times and decreases downlink data rate. If this parameter is set to ROUND_UP and the number of required RBGs is greater than N but less than N+1 (N is greater than or equal to 0), RBs of N+1 RBGs are allocated to UEs in the current TTI. Setting this parameter to ROUND_UP wastes a few RBs, but decreases scheduling times and increases downlink data rate. When this parameter is set to ADAPTIVE: (1) If the number of required RBGs is less than 1, the actual number of RBs are allocated to UEs at the current TTI; (2) If the number of required RBGs is greater than N but less than N+1 (N is greater than or equal to 1), RBs of N+1 RBGs are allocated to UEs in the current TTI. Compared with setting this parameter to ROUND_UP, setting this parameter to ADAPTIVE does not waste RBs when the number of required RBGs is less than 1. For services whose QCI is 1 (such as VoIP services): When this parameter is set to ROUND_DOWN: (1) If the number of required RBGs is less than 1, the actual number of RBs are allocated to UEs at the current TTI; (2) If the number of required RBGs is greater than N but less than N+1 (N is greater than or equal to 1), RBs of N+1 RBGs are allocated to UEs in the current TTI. If this parameter is set to ROUND_UP or ADAPTIVE, RBs are allocated to UEs in the same way that they are allocated when this parameter is set to ROUND_UP or ADAPTIVE for services whose QCI is not 1, respectively. For ping services: If the number of required RBGs is greater than N but less than N+1 (N is greater than or equal to 0), RBs of N+1 RBGs are allocated to UEs in the current TTI regardless of the actual parameter setting. GUI Value Range: ROUND_DOWN(Round Down), ROUND_UP(Round Up), ADAPTIVE(Adaptive) Unit: None Issue 03 (2015-11-03) Huawei Proprietary and Confidential 52 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 7 Parameters MO Parame MML Feature Feature Description ter ID Comma ID Name nd Actual Value Range: ROUND_DOWN, ROUND_UP, ADAPTIVE Default Value: ROUND_DOWN(Round Down) CellUlsc UlRbAll MOD LOFD-0 Dynami Meaning: Indicates the strategy for allocating resource hAlgo ocationS CELLU 0101502 c blocks (RBs) in the uplink of the cell. If this parameter trategy LSCHA / Scheduli is set to FS_NONFS_ADAPTIVE, this strategy LGO TDLOF ng adaptively switches between frequency selective LST D-00101 scheduling and non-frequency selective scheduling. If CELLU 502 this parameter is set to LSCHA FS_INRANDOM_ADAPTIVE, this strategy LGO adaptively switches between frequency selective scheduling and interference-randomization-based scheduling. GUI Value Range: FS_NONFS_ADAPTIVE(Fs nonFs Strategy), FS_INRANDOM_ADAPTIVE(Fs InRandom Strategy) Unit: None Actual Value Range: FS_NONFS_ADAPTIVE, FS_INRANDOM_ADAPTIVE Default Value: FS_INRANDOM_ADAPTIVE(Fs InRandom Strategy) TimeAli Timing MOD None None Meaning: Indicates whether to enable the mechanism gnment ResOptS TATIM of optimized resource scheduling for uplink timing.If Timer witch ER this parameter is set to OFF, the eNodeB adopts the LST existing resource scheduling policy for uplink timing, TATIM which consumes a large amount of resources used for ER delivering Timing Advance Commands in large traffic scenarios.If this parameter is set to ON, the eNodeB adopts the mechanism of optimized resource scheduling for uplink timing, which reduces the number of unnecessary Timing Advance Commands to be delivered and reduces resources allocated for uplink timing in large traffic scenarios.This parameter applies only to LTE FDD cells. The parameter value ON is recommended in heavily loaded cells where there is a large number of UEs. GUI Value Range: OFF(Off), ON(On) Unit: None Actual Value Range: OFF, ON Default Value: ON(On) Issue 03 (2015-11-03) Huawei Proprietary and Confidential 53 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 7 Parameters MO Parame MML Feature Feature Description ter ID Comma ID Name nd TimeAli Timing MOD None None Meaning: gnment AdvCm TATIM Indicates whether optimization of the mechanism for Timer dOptSwi ER delivering the uplink time alignment command takes tch LST effect. If the optimization takes effect, the number of TATIM unnecessary uplink time alignment commands ER delivered to motionless or low-mobility UEs can be reduced to save air interface resources and reduce power consumption of UEs in DRX mode. This ensures the uplink time alignment performance if the length of the uplink time alignment timer is set to a large value. If this parameter is set to ON, it is recommended that the TimeAlignmentTimer parameter be set to SF10240. A smaller value of the TimeAlignmentTim- er parameter, such as SF5120, leads to a higher probability of becoming out-of-synchronization in the uplink for UEs in DRX mode. If this parameter is set to ON, it is recommended that the LongDrxCycle parameter be smaller than or equal to SF320. Otherwise, the uplink time alignment performance of UEs in DRX mode is affected. GUI Value Range: OFF(Off), ON(On) Unit: None Actual Value Range: OFF, ON Default Value: ON(On) Issue 03 (2015-11-03) Huawei Proprietary and Confidential 54 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 7 Parameters MO Parame MML Feature Feature Description ter ID Comma ID Name nd TimeAli Timing MOD LBFD-0 Uplink Meaning: Indicates the method of measuring uplink gnment MeasMo TATIM 70101 Timing timing offsets. If this parameter is set to INVALID, Timer de ER Based uplink timing offsets are measured based on the LST on demodulation reference signal (DMRS) for PUSCH or TATIM PUCCH sounding reference signal (SRS). If this parameter is ER set to ALLMEASMODE, uplink timing offsets are measured based on the DMRS for PUSCH and SRS or based on the DMRS for PUSCH and channel quality indicator (CQI) in PUCCH. In addition, the value ON of the TimingAdvCmdOptSwitch parameter takes effect regardless of the actual parameter setting. That is, the eNodeB always sends the Timing Advance Command to UEs. In this case, it is recommended that the TimeAlignmentTimer parameter be set to SF10240. The value ALLMEASMODE applies only to LTE FDD cells. The parameter value INVALID takes effect in a cell regardless of the actual parameter setting in any of the following scenarios: (1) The cell is established on an LBBPc. (2) The UlCyclicPrefix parameter is set to EXTENDED_CP. (3) The HighSpeedFlag parameter is set to HIGH_SPEED, ULTRA_HIGH_SPEED, or EXTRA_HIGH_SPEED. (4) The TX/RX mode of the cell is 2T8R. GUI Value Range: INVALID(Invalid Timing Measurement Mode), ALLMEASMODE(All Timing Measurement Mode) Unit: None Actual Value Range: INVALID, ALLMEASMODE Default Value: INVALID(Invalid Timing Measurement Mode) CellAlg CellSch MOD LOFD-0 Enhance Meaning: oSwitch Strategy CELLA 0101502 d Indicates whether to enable a specific scheduling Switch LGOSW / Scheduli policy in the uplink and downlink. ITCH TDLOF ng LST D-00101 Basic AbnUeSchSwitch: Indicates whether to disable CELLA 502 Scheduli scheduling of abnormal UEs. If this switch is on, LGOSW LBFD-0 ng abnormal UEs are not scheduled. If this switch is off, ITCH 02025 / abnormal UEs are scheduled. TDLBF GUI Value Range: D-00202 AbnUeSchSwitch(AbnUeSchSwitch) 5 Unit: None Actual Value Range: AbnUeSchSwitch Default Value: AbnUeSchSwitch:Off Issue 03 (2015-11-03) Huawei Proprietary and Confidential 55 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 7 Parameters MO Parame MML Feature Feature Description ter ID Comma ID Name nd CellPdc PdcchCa MOD LBFD-0 Physical Meaning: chAlgo pacityIm CELLP 02003 Channel Indicates whether to optimize PDCCH capacity proveSw DCCHA Manage expansion. itch LGO ment LST For LTE FDD networks, if this parameter is set to CELLP ON(On), (1) the initial value for closed-loop DCCHA adjustment on PDCCH aggregation level applies only LGO to SRBs; (2) if a UE fails to be allocated with CCEs, the eNodeB reallocates CCEs to the UE by increasing the PDCCH power and decreasing the PDCCH aggregation level for the UE. If this parameter is set to OFF(Off), (1) the initial value for closed-loop adjustment on PDCCH aggregation level applies to both SRBs and DRBs; (2) if a UE fails to be allocated with CCEs, the eNodeB does not reallocate CCEs to the UE by increasing the PDCCH power and decreasing the PDCCH aggregation level for the UE. For LTE TDD networks, if this parameter is set to ON(On), the eNodeB reallocates CCEs to a UE, if the UE fails to be allocated with CCEs, by increasing the PDCCH transmit power and decreasing the PDCCH aggregation level for the UE. If this parameter is set to OFF(Off), the eNodeB does not reallocate CCEs to a UE, if the UE fails to be allocated with CCEs, by increasing the PDCCH power and decreasing the PDCCH aggregation level for the UE. GUI Value Range: OFF(Off), ON(On) Unit: None Actual Value Range: OFF, ON Default Value: OFF(Off) Issue 03 (2015-11-03) Huawei Proprietary and Confidential 56 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 7 Parameters MO Parame MML Feature Feature Description ter ID Comma ID Name nd CellAlg DlSchS MOD LOFD-0 VoIP Meaning: oSwitch witch CELLA 01016 / Semi- Indicates the switches related to downlink scheduling LGOSW TDLOF persisten in the cell. ITCH D-00101 t LST 6 Scheduli FreqSelSwitch: Indicates whether to enable frequency CELLA LOFD-0 ng selective scheduling. If this switch is on, data is LGOSW 0101502 Dynami transmitted on the frequency band in good signal ITCH / c quality. TDLOF Scheduli ServiceDiffSwitch: Indicates whether to enable D-00101 ng service differentiation. If this switch is on, service 502 DL differentiation is applied. If this switch is off, service LOFD-0 Non- differentiation is not applied. 01109 / GBR TDLOF Packet SpsSchSwitch: Indicates whether to enable semi- D-00110 Bundlin persistent scheduling during talk spurts of VoIP 9 g services. If this switch is on, semi-persistent scheduling is applied during talk spurts of VoIP LOFD-0 Symbol services. If this switch is off, dynamic scheduling is 01070 / Power applied during talk spurts of VoIP services. TDLOF Saving D-00107 Scheduli MBSFNShutDownSwitch: Indicates whether to 0 ng enable Multimedia Broadcast multicast service Single TDLOF Based Frequency Network (MBSFN) subframe shutdown. If D-07022 on Max this switch is on, MBSFN subframe shutdown is 4 Bit Rate applied. If this switch is off, MBSFN subframe shutdown is not applied. This switch is valid only LBFD-0 Basic when SymbolShutdownSwitch is on. If the MBSFN 02025 / Scheduli shutdown switch is on, the setting of the switch for TDLBF ng mapping SIBs to SI messages becomes invalid. The D-00202 Support latter can be specified by the SiMapSwitch parameter 5 of in the CellSiMap MO. If the MBSFN subframe LBFD-0 aperiodi shutdown switch is off, the setting of the switch for 02031 / c CQI mapping SIBs to SI messages becomes valid. MBSFN TDLBF reports subframe shutdown applies only to LTE-only base D-00203 MBR>G stations. 1 BR NonGbrBundlingSwitch: Indicates whether to enable LBFD-0 Configu downlink non-GBR packet bundling. If this switch is 70102 / ration on, delay of non-GBR services can be controlled in TDLBF Enhance non-congestion scenarios. If this switch is off, delay of D-07010 d DL non-GBR services cannot be controlled. 2 Frequen LBFD-0 cy EnAperiodicCqiRptSwitch: Indicates whether to 60202 Selectiv enable enhanced aperiodic channel quality indicator e (CQI) reporting. If this switch is on, the eNodeB triggers aperiodic CQI reporting for a UE based on downlink services of the UE and the interval at which the UE sends periodic CQI reports. If this switch is off, UEs under non-frequency selective scheduling do not trigger aperiodic CQI reporting based on downlink Issue 03 (2015-11-03) Huawei Proprietary and Confidential 57 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 7 Parameters MO Parame MML Feature Feature Description ter ID Comma ID Name nd services and triggers an aperiodic CQI reporting if no valid periodic CQI reports are sent in eight consecutive periodic CQI reporting periods. DlMbrCtrlSwitch: Indicates whether to enable downlink scheduling based on the maximum bit rate (MBR) and guaranteed bit rate (GBR) on the GBR bearer. If this switch is on, the eNodeB performs downlink scheduling on GBR bearers based on the MBR and GBR. If this switch is off, the eNodeB performs downlink scheduling on GBR bearers based on the GBR only. MbrDlSchSwitch: Indicates whether the eNodeB performs downlink scheduling based on MBR. If this switch is on, the eNodeB determines priorities of UEs based on the MBR in downlink scheduling. This parameter applies only to LTE TDD cells. UeAmbrDlSchSwitch: Indicates whether the eNodeB performs downlink scheduling based on the aggregate maximum bit rate (AMBR) of UEs. If this switch is on, the eNodeB determines priorities of UEs based on the AMBR of UEs in downlink scheduling. This parameter applies only to LTE TDD cells. EpfEnhancedSwitch: Indicates whether to enable enhanced proportional fair (EPF) for downlink scheduling. EPF for downlink scheduling is enabled only when this switch is on. AperiodicCqiTrigOptSwitch: Indicates whether to trigger aperiodic CQI optimization. If this switch is on, a UE performing initial access triggers aperiodic CQI reporting based on related triggering conditions after the DLMAC instance has been established for 200 ms and the eNodeB receives MSG5. Consider that aperiodic CQI reporting is triggered by invalid CQI reports in eight consecutive CQI reporting periods. If cyclic redundancy check (CRC) on aperiodic CQI reports fails, aperiodic CQI reporting is not repeatedly triggered when DRX is enabled; or aperiodic CQI reporting is triggered after eight TTIs when DRX is disabled. If this switch is off, a UE performing initial access triggers aperiodic CQI reporting based on related triggering conditions after the DLMAC instance has been established for 200 ms. Consider that aperiodic CQI reporting is triggered by invalid CQI reports in eight consecutive CQI reporting periods. If CRC on aperiodic CQI reports fails, Issue 03 (2015-11-03) Huawei Proprietary and Confidential 58 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 7 Parameters MO Parame MML Feature Feature Description ter ID Comma ID Name nd aperiodic CQI reporting is triggered after eight TTIs regardless of the DRX status. VoipTbsBasedMcsSelSwitch: Indicates whether the modulation and coding scheme (MCS) index is selected based on the transport block size (TBS) in downlink scheduling for VoIP services. If this switch is on, the MCS index is selected based on the TBS in downlink scheduling for VoIP services. If this switch is off, the MCS index is not selected based on the TBS in downlink scheduling for VoIP services. UeSigMcsEnhanceSwitch: Indicates whether to enable or disable the optimized MCS algorithm for UE signaling. The optimized MCS algorithm for UE signaling takes effect after this switch is on. This parameter applies only to LTE TDD cells. PagingInterfRandSwitch: Indicates whether to enable or disable interference randomizing for paging messages. If this switch is on, interference randomizing is enabled for paging messages. This switch is valid only in TDD mode. DlSingleUsrMcsOptSwitch: Indicates conditions for lowering the modulation and coding scheme (MCS) for a single UE. When this switch is on, the MCS can be lowered for a UE if the UE is the only UE to be scheduled in a transmission time interval (TTI). When this switch is off, the MCS can be lowered for a UE if there are only 10 percent of TTIs having UEs to schedule in each sparse packet determination period and the UE is the only UE to be scheduled in each TTI. SubframeSchDiffSwitch: Indicates whether subframes 3 and 8 perform scheduling based on increased number of uplink scheduling UEs when subframe configuration type 2 is used. If this switch is on, subframes 3 and 8 perform scheduling based on increased number of uplink scheduling UEs when subframe configuration type 2 is used. If this switch is off, subframes 3 and 8 perform scheduling based on the policy that other downlink subframes adopt when subframe configuration type 2 is used. This switch is dedicated to LTE TDD cells. TailPackagePriSchSwitch: Indicates the switch that controls the scheduling of downlink connected tail packages in the bearer. If this switch is on, the connected tail package is scheduled preferentially in Issue 03 (2015-11-03) Huawei Proprietary and Confidential 59 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 7 Parameters MO Parame MML Feature Feature Description ter ID Comma ID Name nd the next TTI, which reduces the delay and increases the transmission rate. If this switch is off, the scheduling strategy of the connected tail package is the same as other downlink subframes. This switch is dedicated to LTE TDD cells. FreqSelJudgeIgnorDopplerSwitch: Indicates whether Doppler determination conditions are considered during channel frequency selective scheduling determination. Doppler determination conditions are considered only when this option is deselected. This option applies only to LTE FDD. SIB1InterfRandSwitch: Indicates whether to enable SIB1 interference randomizing. If this switch is on, interference randomizing is enabled for SIB1. This switch applies only to LTE TDD cells. GUI Value Range: FreqSelSwitch(FreqSelSwitch), ServiceDiffSwitch(ServiceDiffSwitch), SpsSchSwitch(SpsSchSwitch), MBSFNShutDownSwitch(MBSFNShutDownSwitch), NonGbrBundlingSwitch(NonGbrBundlingSwitch), EnAperiodicCqiRptSwitch(EnAperiodicCqiRptS- witch), DlMbrCtrlSwitch(DlMbrCtrlSwitch), MbrDlSchSwitch(MbrDlSchSwitch), UeAmbrDlSchSwitch(UeAmbrDlSchSwitch), EpfEnhancedSwitch(EpfEnhancedSwitch), AperiodicCqiTrigOptSwitch(AperiodicCqiTrigOptS- witch), VoipTbsBasedMcsSelS- witch(VoipTbsBasedMcsSelSwitch), PagingInterfRandSwitch(PagingInterfRandSwitch), DlSingleUsrMcsOptSwitch(DlSingleUsrMcsOptS- witch), SubframeSchDiffSwitch(SubframeSchDiffS- witch), TailPackagePriSchS- witch(TailPackagePriSchSwitch), UeSigMcsEnhanceSwitch(UeSigMcsEnhanceSwitch), FreqSelJudgeIgnorDopplerSwitch(FreqSelJudgeIgnor- DopplerSwitch), SIB1InterfRandSwitch(SIB1InterfRandSwitch) Unit: None Actual Value Range: FreqSelSwitch, ServiceDiffSwitch, SpsSchSwitch, MBSFNShutDownSwitch, NonGbrBundlingSwitch, EnAperiodicCqiRptSwitch, DlMbrCtrlSwitch, MbrDlSchSwitch, UeAmbrDlSchSwitch, EpfEnhancedSwitch, AperiodicCqiTrigOptSwitch, VoipTbsBasedMcsSelSwitch, PagingInterfRand- Switch, DlSingleUsrMcsOptSwitch, SubframeSchDiffSwitch, TailPackagePriSchSwitch, Issue 03 (2015-11-03) Huawei Proprietary and Confidential 60 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 7 Parameters MO Parame MML Feature Feature Description ter ID Comma ID Name nd UeSigMcsEnhanceSwitch, FreqSelJudgeIgnorDop- plerSwitch, SIB1InterfRandSwitch Default Value: FreqSelSwitch:Off, ServiceDiffSwitch:Off, SpsSchSwitch:Off, MBSFNShutDownSwitch:Off, NonGbrBundlingS- witch:Off, EnAperiodicCqiRptSwitch:Off, DlMbrCtrlSwitch:Off, MbrDlSchSwitch:Off, UeAmbrDlSchSwitch:Off, EpfEnhancedSwitch:Off, AperiodicCqiTrigOptSwitch:Off, VoipTbsBasedMcs- SelSwitch:Off, PagingInterfRandSwitch:Off, DlSingleUsrMcsOptSwitch:Off, SubframeSchDiffS- witch:Off, TailPackagePriSchSwitch:Off, UeSigMcsEnhanceSwitch:Off, FreqSelJudgeIgnor- DopplerSwitch:Off, SIB1InterfRandSwitch:On LIOptR AtomRu LST LOFD-0 Automat Meaning: Indicates the ID of the intelligent uleMem leID LIOPTR 81205 ic optimization atom rule to which the intelligent ber ULEME TDLOF Congesti optimization rule members associated. MBER D-08120 on GUI Value Range: 0~65535 MOD 9 Handlin g Unit: None LIOPTR ULEME Automat Actual Value Range: 0~65535 MBER ic Default Value: None Congesti on Handlin g(TDD) Issue 03 (2015-11-03) Huawei Proprietary and Confidential 61 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 8 Counters 8 Counters Table 8-1 Counters Counter ID Counter Name Counter Feature ID Feature Name Description 1526726737 L.ChMeas.PRB.UL Average number of Multi-mode: None Basic Scheduling .Used.Avg used uplink PRBs GSM: None Basic Scheduling UMTS: None Adaptive SFN/ LTE: SDMA LBFD-002025 TDLBFD-002025 LOFD-070205 1526726740 L.ChMeas.PRB.DL Average number of Multi-mode: None Basic Scheduling .Used.Avg used PDSCH PRBs GSM: None Basic Scheduling UMTS: None Adaptive SFN/ LTE: SDMA LBFD-002025 TDLBFD-002025 LOFD-070205 1526728259 L.Thrp.bits.UL Total uplink traffic Multi-mode: None Radio Bearer volume for PDCP GSM: None Management PDUs in a cell Radio Bearer UMTS: None Management LTE: LBFD-002008 Basic Scheduling TDLBFD-002008 Basic Scheduling LBFD-002025 TDLBFD-002025 Issue 03 (2015-11-03) Huawei Proprietary and Confidential 62 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 8 Counters Counter ID Counter Name Counter Feature ID Feature Name Description 1526728261 L.Thrp.bits.DL Total downlink Multi-mode: None Radio Bearer traffic volume for GSM: None Management PDCP SDUs in a Radio Bearer cell UMTS: None Management LTE: LBFD-002008 Basic Scheduling TDLBFD-002008 Basic Scheduling LBFD-002025 TDLBFD-002025 1526728303 L.ChMeas.CCE.Co Number of PDCCH Multi-mode: None Physical Channel mmUsed CCEs used for GSM: None Management common DCI Physical Channel UMTS: None Management LTE: LBFD-002003 TDLBFD-002003 1526728304 L.ChMeas.CCE.UL Number of PDCCH Multi-mode: None Physical Channel Used CCEs used for GSM: None Management uplink DCI in a Physical Channel measurement period UMTS: None Management LTE: LBFD-002003 TDLBFD-002003 1526728305 L.ChMeas.CCE.DL Number of PDCCH Multi-mode: None Physical Channel Used CCEs used for GSM: None Management downlink DCI in a Physical Channel measurement period UMTS: None Management LTE: LBFD-002003 TDLBFD-002003 1526728333 L.Traffic.User.Ulsy Average number of Multi-mode: None RRC Connection nc.Avg UL synchronized GSM: None Management users in a cell RRC Connection UMTS: None Management LTE: LBFD-002007 TDLBFD-002007 Issue 03 (2015-11-03) Huawei Proprietary and Confidential 63 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 8 Counters Counter ID Counter Name Counter Feature ID Feature Name Description 1526728433 L.ChMeas.PRB.DL Number of Multi-mode: GSM and LTE FDD .Avail available downlink MRFD-090202 Dynamic Spectrum PRBs GSM: None Sharing(LTE FDD) UMTS: None LTE-A Introduction LTE: Carrier Aggregation LAOFD-001001 for Downlink 2CC LAOFD-001002 in 40MHz LOFD-070205 Adaptive SFN/ TDLOFD-001075 SDMA SFN 1526728434 L.ChMeas.PRB.UL Number of Multi-mode: GSM and LTE FDD .Avail available uplink MRFD-090202 Dynamic Spectrum PRBs GSM: None Sharing(LTE FDD) UMTS: None LTE-A Introduction LTE: Carrier Aggregation LAOFD-001001 for Downlink 2CC LAOFD-001002 in 40MHz LOFD-070205 Adaptive SFN/ TDLOFD-001075 SDMA SFN 1526728997 L.Thrp.Time.Cell.D Total duration of Multi-mode: None Radio Bearer L.HighPrecision downlink data GSM: None Management transmission in a Radio Bearer cell (with the UMTS: None Management precision of 1 ms) LTE: LBFD-002008 Basic Scheduling TDLBFD-002008 Basic Scheduling LBFD-002025 TDLBFD-002025 1526728998 L.Thrp.Time.Cell.U Total duration of Multi-mode: None Radio Bearer L.HighPrecision uplink data GSM: None Management transmission in a Radio Bearer cell (with the UMTS: None Management precision of 1 ms) LTE: LBFD-002008 Basic Scheduling TDLBFD-002008 Basic Scheduling LBFD-002025 TDLBFD-002025 Issue 03 (2015-11-03) Huawei Proprietary and Confidential 64 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 8 Counters Counter ID Counter Name Counter Feature ID Feature Name Description 1526729005 L.Thrp.bits.DL.Last Downlink traffic Multi-mode: None Radio Bearer TTI volume sent in the GSM: None Management last TTI for PDCP Radio Bearer SDUs before the UMTS: None Management buffer is empty LTE: LBFD-002008 Basic Scheduling TDLBFD-002008 Basic Scheduling LBFD-002025 TDLBFD-002025 1526729015 L.Thrp.Time.DL.R Data transmit Multi-mode: None Radio Bearer mvLastTTI duration except the GSM: None Management last TTI before the Radio Bearer downlink buffer is UMTS: None Management empty LTE: LBFD-002008 Basic Scheduling TDLBFD-002008 Basic Scheduling LBFD-002025 TDLBFD-002025 1526729415 L.Thrp.bits.UE.UL. Uplink traffic Multi-mode: None Radio Bearer SmallPkt volume of PDCP GSM: None Management PDUs scheduled for Radio Bearer small packets UMTS: None Management LTE: LBFD-002008 Basic Scheduling TDLBFD-002008 Basic Scheduling LBFD-002025 TDLBFD-002025 1526729416 L.Thrp.Time.UE.U Uplink data Multi-mode: None Radio Bearer L.RmvSmallPkt transmission GSM: None Management duration except that Radio Bearer for small packets UMTS: None Management LTE: LBFD-002008 Basic Scheduling TDLBFD-002008 Basic Scheduling LBFD-002025 TDLBFD-002025 Issue 03 (2015-11-03) Huawei Proprietary and Confidential 65 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 9 Glossary 9 Glossary For the acronyms, abbreviations, terms, and definitions, see Glossary. Issue 03 (2015-11-03) Huawei Proprietary and Confidential 66 Copyright © Huawei Technologies Co., Ltd. eRAN Automatic Congestion Handling Feature Parameter Description 10 Reference Documents 10 Reference Documents 1. Scheduling Feature Parameter Description Issue 03 (2015-11-03) Huawei Proprietary and Confidential 67 Copyright © Huawei Technologies Co., Ltd.