Automatic Congestion Handling(ERAN8.1_03)

7/25/2019 Automatic Congestion Handling(ERAN8.1_03)

1/71

eRAN

Automatic Congestion Handling

Feature Parameter Description

Issue 03

Date 2015-11-03

HUAWEI TECHNOLOGIES CO., LTD.


2/71

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 thepurchase 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

Copyright Huawei Technologies Co., Ltd.

i
http://www.huawei.com/


3/71

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 Procedurefor Automatic Congestion Handling............................................................................................................. 8

3.2 Data Collection...............................................................................................................................................................9

3.3 Trigger Condition Judgment.........................................................................................................................................103.4 IntelligentOptimization 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 NetworkImpact........................................................................................................................... 18

5.1 LOFD-081205 Automatic Congestion Handling......................................................................................................... 18

6 Engineering Guidelines............................................................................................................. 21

6.1 When to Use Automatic Congestion Handling............................................................................................................ 226.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

eRAN

Automatic Congestion Handling Feature Parameter

Description Contents



ii


4/71

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

eRAN


Description Contents



iii


5/71

1About 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.

eNodeBType

Model

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 aretwo types of changes:

eRAN


Description 1 About This Document



1


6/71

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.

ChangeType

Change Description Parameter Change

AffectedEntity

Feature

change

Deleted the uplink synchronized user specifications

in a cell from 3.2 Data Collection. For details about

the relevant specifications, see 3900 Series Base

Station Technical Description.

None Macro,

micro,

and

LampSite

eNodeBs

Editorial

change

None None -

eRAN8.1 02 (2015-04-30)

This issue includes the following changes.

ChangeType

Change Description Parameter Change

AffectedEntity

Feature

change

Updated the maximum number of UL synchronized

users supported by different BBP types. For details,

see 3.2 Data Collection.

None Macro,

micro,

and

LampSite

eNodeBs

Editorial

change

None None -

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.

eRAN





2


7/71

1.4 Differences Between eNodeB Types

The features described in this document are implemented in the same way on macro, micro,

and LampSite eNodeBs.

eRAN





3


8/71

2OverviewLTE 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.

eRAN


Description 2 Overview



4


9/71

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-1shows the

architecture of Automatic Congestion Handling.

eRAN





5


10/71

Figure 2-1Architecture of Automatic Congestion Handling

eRAN





6


11/71

3Technical DescriptionThis chapter describes how LOFD-081205 Automatic Congestion Handling works. For

details about the engineering guidelines, see 6 Engineering Guidelines.

eRAN


Description 3 Technical Description



7


12/71

3.1 Procedure for Automatic Congestion Handling

Figure 3-1outlines the procedure for Automatic Congestion Handling.

Figure 3-1Procedure for Automatic Congestion Handling

NOTE

Each intelligent optimization function shown in Figure 3-1includes 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 thenext 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 currentperiod.

eRAN





8


13/71

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-1describes the required measurement

items and their calculation formulas.

Table 3-1Required measurement items and their calculation formulas

MeasurementItem

Definition Calculation Formula

User_Spec_Occ

upy_Rate

Average number of

UL synchronized

users in a cell/Maximum number of

UL synchronized

users in a cell

L.Traffic.User.Ulsync.Avg/Maximum number

of UL synchronized users in a cell

NOTE

l The uplink synchronized user capacity in a cell

varies with BBP types. For details about the

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_

Utilization_Rat

e

Number of used

CCEs/Total number

of available CCEs

(L.ChMeas.CCE.CommUsed +

L.ChMeas.CCE.ULUsed+

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 Switchparameter

(parameter ID:

CellPdcchAlgo.PdcchSymNumSwitch) is set to

ON(On)or ECFIADAPTIONON(EnhancedCFI Adaption On), or when the PDCCH

Symbol Number Adjust Switchparameter is set

to OFF(Off)and the PDCCH Initial Symbol

Numberparameter (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.

eRAN





9


14/71

MeasurementItem

Definition Calculation Formula

DL_PRB_Utili

zation_Rate

Number of used

downlink PRBs/Total

number of downlink

PRBs

L.ChMeas.PRB.DL.Used.Avg/

L.ChMeas.PRB.DL.Avail

UL_PRB_Utili

zation_Rate

Number of used

uplink PRBs/Total

number of uplink

PRBs

L.ChMeas.PRB.UL.Used.Avg/

L.ChMeas.PRB.UL.Avail

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.PhichResourceis equivalent to Ngin 3GPP TS 36.211. The parameter value

can be 1/6, 1/2, 1, and 2. Table 3-2lists the corresponding number of available CCEs per TTI.

Automatic Congestion Handling uses the number of available CCEs that correspond to Ng=

1.

Table 3-2Number of available CCEs when the maximum number of fixed PDCCH symbols

is adopted

System

Bandwidth(MHz)

PHICHCFG.P

hichResource= 1/6

PHICHCFG.P

hichResource= 1/2

PHICHCFG.P

hichResource= 1

PHICHCFG.P

hichResource= 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 Collectionmeets the trigger condition for an

intelligent optimization function described in 3.4 Intelligent Optimization Functions and

Parameter Adjustmentsand 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.

eRAN





10


15/71

3.4 Intelligent Optimization Functions and ParameterAdjustments

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 LIOPTATOMRULEcommand 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 increasesl 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 LIOPTRULEcommand 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 adjustmentsspecified by the intelligent optimization rules.

eRAN





11


16/71

Rule ID Trigger Condition Parameter Adjustment

7 User_Spec_Occupy_Rate >

50%

andDL_PRB_Utilization_Rate

< 90%

The MOD CELLDLSCHALGOcommand is

executed with the RBG Resource Allocation

Strategyparameter set to

ADAPTIVE(Adaptive) .

8 User_Spec_Occupy_Rate 95%

The original parameter value is restored.

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 >

50%

and

UL_PRB_Utilization_Rate

> 20%

The MOD CELLULSCHALGOcommand is

executed with the Uplink Resource Block

Allocation Strategyparameter set to

FS_INRANDOM_ADAPTIVE(Fs InRandom

Strategy).

12 User_Spec_Occupy_Rate

50%

and

PDCCH_CCE_Utilization_

Rate > 60%

The MOD TATIMERcommand is executed

with Timing Resource Optimization Switch

set to ON(On)and Uplink time alignment

timerset to INFINITY(Infinity). The

optimized TA function is enabled.


50%

andPDCCH_CCE_Utilization_

Rate > 60%

The MOD CELLALGOSWITCHcommand is

executed with

AbnUeSchSwitch(AbnUeSchSwitch) selected

under Cell Schedule Strategy Switch. The

function of detection and scheduling for

abnormal UEs is enabled.


50%

and


Rate > 60%

The MOD CELLPDCCHALGOcommand is

executed with PDCCH Capacity Improve

Switchset to ON(On). PDCCH CCE capacity

improvement is enabled.


50%

and


Rate > 60%

The MOD CELLALGOSWITCHcommand is

executed with FreqSelSwitch(FreqSelSwitch)

cleared under DL schedule switch. Downlink

frequency selective scheduling is disabled.

6 User_Spec_Occupy_Rate 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 BulkConfiguration 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 theparametersin the MOs according to the setting notesprovided in 6.4.2 Data Preparationand close the file.

Step 4 Choose CME> LTE Application> Import Data> Import Base Station BulkConfiguration 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 IncrementalScripts(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 Areain 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 Preparationfor a single eNodeB. The

procedure is as follows:

Step 1 In the planned data area, click Base Stationin the upper left corner of the configurationwindow.

Step 2 In area 1 shown in Figure 6-1, select the eNodeB to which the MOs belong.

eRAN


Description 6 Engineering Guidelines



31


36/71

Figure 6-1MO search and configuration window

Step 3 On the Searchtab page in area 2, enter an MO name, for example, CELL.

Step 4 In area 3, double-click the MO in the Object Namecolumn. All parameters in this MO aredisplayed 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), orchoose 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 ENODEBALGOSWITCHcommand with ACHSwitch(ACHSwitch)selected under the Intelligent Optimization Algorithm Switchparameter.

----End

l (Optional) Special scenarios: Deactivating an intelligent optimization rule after ACH is

enabled

Step 1 Run the LST LIOPTRULEcommand to query the intelligent optimization rule that isassociated with an operation.

Step 2 Run the DEA LIOPTRULEcommand 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

eRAN





32


37/71

l (Optional) Special scenarios: Disabling an atom rule of an intelligent optimization rule

after ACH is enabled


Step 2 Run the LST LIOPTRULEMEMBERcommand to query the ID of the atom rule that isassociated with the intelligent optimization rule.

Step 3 Run the MOD LIOPTRULEMEMBERcommand to disable the atom rule of intelligentoptimization 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 ruleafter ACH is enabled


Step 2 Run the LST LIOPTRULEMEMBERcommand to query the ID of the atom rule that isassociated with the intelligent optimization rule.

Step 3 Run the LST LIOPTATOMRULEcommand to query the trigger condition for the atom rule.

Step 4 Run the MOD LIOPTATOMRULEcommand to modify the trigger condition for the atomrule.

----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 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 LIOPTRULEMEMBER: AtomRuleID=1, RuleID=1;

LST LIOPTATOMRULE: AtomRuleID=1;MOD LIOPTATOMRULE: AtomRuleID=1, ThresholdforNumPara=30;

eRAN





33


38/71

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 Logtab and then click Synchronizein the lower right corner of theQuery SON Logtab. 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-definedConditionsarea in the left pane.

l Set Log Categoryto LTE Automatic Congestion Handling Log.

l In the Event Namearea, select Set Automatic Congestion Handling Switch, Modify

Cell-level Runtime Parameters, Recover Cell-level Runtime Parameters, ModifyeNodeB-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 rightpane.

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 byrunning correlated LST commands and perform the following step to query the running

values:

Step 1 Run the DSP LIOPTRULEcommand to view the values of Action Type, Action, LocalCell ID, and Executive Status.

Expected result: The value of Action Typefor some intelligent optimization rules is

MODIFY.

l If the value of Executive Statusfor a parameter is UN-EXECUTEDor 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 Statusfor a parameter is EXECUTED, the parameter has been

modified by Automatic Congestion Handling. In this situation, view the target value in

the Actionfield, which is the running value of the parameter.

eRAN





34


39/71

NOTE

The following are descriptions of fields in the command output of DSP LIOPTRULE.

Action Type: The value can be either MODIFYor 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 configuredvalues.

Action: Indicates which and how parameters are modified when an intelligent optimization

rule applies. This field does not take effect if Action Typeis 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-EXECUTEDindicates that the intelligent optimization rule has not been executed.

EXECUTINGindicates 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-3Parameter related to Automatic Congestion Handling

MO Sheet in theSummary Data File

Parameter Group Setting Notes

ENodeBAlgoSwit

ch

User-defined sheet,

such as eNodeB

Algorithm Switch.

Intelligent

Optimization

Algorithm Switch

Set ACHSwitchto 0.

This parameter group

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 Configurationdescribed for feature activation.

Using MML Commands

Step 1 Run the MOD ENODEBALGOSWITCHcommand with ACHSwitch(ACHSwitch)cleared under the Intelligent Optimization Algorithm Switchparameter.

MOD ENODEBALGOSWITCH: IOptAlgoSwitch=ACHSwitch-0;

----End

eRAN





35


40/71

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-4KPIs 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

utilization

(L.ChMeas.CCE.CommUsed+ L.ChMeas.CCE.ULUsed

+ 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-5lists the counters used for calculating the KPIs in Table 6-4.

Table 6-5Counters 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

eRAN





36


41/71

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 forPDCP 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

ecision

Total duration of downlink data

transmission in a cell (with the

precision of 1 ms)

1526728998 L.Thrp.Time.Cell.UL.HighPr

ecision

Total duration of uplink data

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

I

Data transmit duration except the last

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

allPkt

Uplink data transmission duration

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-6for improvement in network performance.

eRAN





37


42/71

Table 6-6Parameter that can be adjusted to improve network performance

Parameter Name

ParameterID

Adjustment Notes MMLCommand

Thresholdfor

Numerical

Parameter

LIOptAtomRule.Thresh

oldforNumP

ara

Indicates the threshold for selecting ameasurement object with a numerical value

in an atom rule of 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 30indicates 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 triggercondition 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 LIOPTRULEMEMBERcommand

to view the associated intelligentoptimization rule, and then run the LST

LIOPTRULEcommand 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/

MODLIOPTATO

MRULE

eRAN





38


43/71

Parameter Name

ParameterID

Adjustment Notes MMLCommand

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.

eRAN





39


44/71

7ParametersTable 7-1Parameters

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

CellPdc

chAlgo

PdcchSy

mNumS

witch

MOD

CELLP

DCCHA

LGO

LST

CELLP

DCCHA

LGO

LBFD-0

02003 /

TDLBF

D-00200

3

Physical

Channel

Manage

ment

Meaning: Indicates the switch used to enable or

disable dynamic adjustment on the number of

orthogonal frequency division multiplexing (OFDM)

symbols occupied by the physical downlink control

channel (PDCCH). If this parameter is set to OFF, the

number of OFDM symbols occupied by the PDCCH

is fixed and cannot be dynamically adjusted. If this

parameter is set to ON, the number of OFDM symbolsoccupied 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: NoneActual Value Range: OFF, ON, ECFIADAPTIONON

Default Value: ON(On)

eRAN


Description 7 Parameters



40


45/71

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

CellPdc

chAlgo

InitPdcc

hSymNu

m

MOD

CELLP

DCCHA

LGO

LST

CELLP

DCCHA

LGO

LBFD-0

02003 /

TDLBF

D-00200

3

Physical

Channel

Manage

ment

Meaning: Indicates the number of OFDM symbols

initially occupied by the PDCCH. If the switch for

dynamic adjustment of the number of OFDM symbols

occupied by the PDCCH is turned off, this parameter

indicates the number of OFDM symbols that are

always occupied by the PDCCH. For LTE TDD cells,

this parameter indicates the number of OFDM

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 PDCCHoccupies 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

Cfg

PhichRe

source

MOD

PHICH

CFG

LST

PHICH

CFG

LBFD-0

02003 /

TDLBF

D-00200

3

LOFD-0

01051

LBFD-0

02009 /

TDLBF

D-00200

9

Physical

Channel

Manage

ment

Compac

t

Bandwi

dth

Broadca

st of

system

informat

ion

Meaning:

Indicates a coefficient that is used to calculate the

resources used by the PHICH for the cell. It

corresponds to the Ng parameter in the protocol.

For details on the usage of the Ng parameter, see

3GPP TS 36.211.

GUI Value Range: ONE_SIXTH, HALF, ONE, TWO

Unit: None

Actual Value Range: ONE_SIXTH, HALF, ONE,

TWO

Default Value: ONE

eRAN





41


46/71

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

LIOptR

ule

Penalty

Time

MOD

LIOPTR

ULE

DSP

LIOPTR

ULE

LST

LIOPTR

ULE

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

on

Handlin

g

Automat

ic

Congesti

on

Handlin

g(TDD)

Meaning: Indicates the penalty duration of intelligent

optimization rules under an intelligent optimization

function. If related conditions for an intelligent

optimization rule under an intelligent optimization

function are met and related adjustment measures are

taken, the penalty duration starts. During the penalty

duration, parameter adjustment cannot be triggered

even if conditions for an intelligent optimization rule

under this intelligent optimization function are met. If

this parameter is set to 0, no penalty is imposed on

intelligent optimization rules under an intelligent

optimization function.


Unit: s


Default Value: 300

TimeAli

gnment

Timer

TimeAli

gnment

Timer

MOD

TATIM

ER

LST

TATIM

ER

None None Meaning: Indicates the length of the uplink time

alignment timer for UEs in the cell. A UE is

considered not time-aligned in the uplink if the timer

expires.

GUI Value Range: SF500(500 subframes), SF750(750

subframes), SF1280(1280 subframes), SF1920(1920

subframes), SF2560(2560 subframes), SF5120(5120subframes), SF10240(10240 subframes),

INFINITY(Infinity)

Unit: None

Actual Value Range: SF500, SF750, SF1280, SF1920,

SF2560, SF5120, SF10240, INFINITY

Default Value: INFINITY(Infinity)

ENodeB

AlgoSwi

tch

IOptAlg

oSwitch

MOD

ENODE

BALGO

SWITCH

LST

ENODE

BALGO

SWITC

H

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

onHandlin

g

Automat

ic

Congesti

on

Handlin

g(TDD)

Meaning: Indicates whether to enable intelligent

optimization algorithms. This parameter includes the

following switches: ACHSwitch: If this switch is on,

the eNodeB periodically determines whether to adjustparameters based on the predefined adaptive

parameter adjustment rules and adjusts parameters if

the predefined adaptive parameter adjustment rules

are met. Therefore, network performance reaches the

optimum in congestion scenarios.

GUI Value Range: ACHSwitch(ACHSwitch)

Unit: None

Actual Value Range: ACHSwitch

Default Value: ACHSwitch:Off

eRAN





42


47/71

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

LIOptFe

ature

IOptFeat

ureID

LST

LIOPTF

EATUR

E

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

on

Handlin

g

Automat

ic

Congesti

on

Handlin

g(TDD)

Meaning: Indicates the ID of the intelligent

optimization feature.


Unit: None


Default Value: None

LIOptFe

ature

IOptFeat

ureNam

e

LST

LIOPTF

EATUR

E

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

on

Handlin

g

Automat

ic

Congesti

on

Handlin

g(TDD)

Meaning: Indicates the name of the intelligent


GUI Value Range: 0~64 characters

Unit: None


Default Value: NULL(empty string)

LIOptFu

nction

IOptFeat

ureID

DSP

LIOPTF

UNCTI

ON

LST

LIOPTF

UNCTI

ON

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

on

Handlin

g

Automat

ic

Congesti

on

Handlin

g(TDD)




Unit: None


Default Value: 1

eRAN





43


48/71

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

LIOptFu

nction

IOptFun

ctionID

DSP

LIOPTF

UNCTI

ON

LST

LIOPTF

UNCTI

ON

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

on

Handlin

g

Automat

ic

Congesti

on

Handlin

g(TDD)




Unit: None


Default Value: None

LIOptFu

nction

IOptFun

ctionNa

me

DSP

LIOPTF

UNCTI

ON

LST

LIOPTF

UNCTI

ON

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

on

Handlin

g

Automat

ic

Congesti

on

Handlin

g(TDD)

Meaning: Indicates the name of the intelligent



Unit: None



LIOptFu

nction

LocalCe

llId

DSP

LIOPTF

UNCTI

ON

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

on

Handlin

g

Automat

ic

Congesti

on

Handlin

g(TDD)

Meaning: Indicates the ID of the cell with which

intelligent optimization atom rules are applied. This

parameter can only be queried by running the DSP

LIOPTFUNCTION command. Information displayed

in the DSP LIOPTFUNCTION command output is

specific to the cell. This parameter setting does not

take effect when the MeasureObjType parameter is set

to eNodeB.


Unit: NoneActual Value Range: 0~255

Default Value: None

eRAN





44


49/71

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

LIOptFu

nction

Status DSP

LIOPTF

UNCTI

ON

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

on

Handlin

g

Automat

ic

Congesti

on

Handlin

g(TDD)

Meaning: Indicates the status of intelligent

optimization atom rules. This parameter can only be

queried by running the DSP LIOPTFUNCTION

command. If this parameter value is NORMAL, the

intelligent optimization is in the normal state. If this

parameter value is PENALTY, the intelligent

optimization is under penalty, and all related

intelligent optimization measures cannot be taken.

GUI Value Range: NORMAL(Normal),

PENALTY(Penalty)

Unit: None

Actual Value Range: NORMAL, PENALTYDefault Value: None

LIOptFu

nction

Measure

ObjType

LST

LIOPTF

UNCTI

ON

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

on

Handlin

g

Automat

ic

Congesti

onHandlin

g(TDD)

Meaning: Indicates the measurement object type in

intelligent optimization atom rules. If this parameter is

set to Cell, the measurement objects are cell-level

atom rules. If this parameter is set to eNodeB, the

measurement objects are eNodeB-level atom rules.

GUI Value Range: Cell(Cell), eNodeB(eNodeB)

Unit: None

Actual Value Range: Cell, eNodeB

Default Value: Cell(Cell)

LIOptR

ule

Action DSP

LIOPTR

ULE

LST

LIOPTR

ULE

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

on

Handlin

g

Automat

ic

Congesti

on

Handlin

g(TDD)

Meaning:

Indicates the action that must be taken according to an

intelligent optimization rule.

Note: When the network exits the heavy load status,

the value of this parameter does not need to be

specified and the actual value restores to the value

configured before optimization. In this case, the value

of the ActionType parameter in the LIOptRule MO isRESUME(RESUME) and the value of the Action

parameter is NULL(empty string).


Unit: None



eRAN





45


50/71

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

LIOptR

ule

ActionT

ype

DSP

LIOPTR

ULE

LST

LIOPTR

ULE

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

on

Handlin

g

Automat

ic

Congesti

on

Handlin

g(TDD)

Meaning: Indicates the type of relationships between

atom rules under an intelligent optimization rule. If

this parameter is set to AND, optimization actions

corresponding to the intelligent optimization rule are

triggered only when all atom rules under this

intelligent optimization rule meet related

requirements. If this parameter is set to OR,

optimization actions corresponding to the intelligent

optimization rule are triggered when any atom rule

under this intelligent optimization rule meets related

requirements.

GUI Value Range: MODIFY(MODIFY),

RESUME(RESUME)

Unit: None

Actual Value Range: MODIFY, RESUME

Default Value: MODIFY(MODIFY)

LIOptR

ule

ActiveSt

atus

DSP

LIOPTR

ULE

LST

LIOPTR

ULE

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

on

Handlin

g

Automatic

Congesti

on

Handlin

g(TDD)

Meaning: Indicates whether an intelligent

optimization rule is activated. If the parameter value is

set to ACTIVATED, the intelligent optimization rule is

activated. If the parameter value is set to

DEACTIVATED, the intelligent optimization rule is

deactivated and does not take effect.

GUI Value Range: ACTIVATED(ACTIVATED),DEACTIVATED(DEACTIVATED)

Unit: None

Actual Value Range: ACTIVATED, DEACTIVATED

Default Value: ACTIVATED(ACTIVATED)

LIOptR

ule

Adaptiv

eRAT

MOD

LIOPTR

ULE

DSP

LIOPTR

ULE

LST

LIOPTR

ULE

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

on

Handlin

g

Automat

ic

Congesti

on

Handlin

g(TDD)

Meaning: Indicates the duplex mode to which an

intelligent optimization rule applies. If this parameter

is set to FDD, the intelligent optimization rule applies

to FDD. If this parameter is set to TDD, the intelligent

optimization rule applies to TDD. If this parameter is

set to BOTH, the intelligent optimization rule appliesto both FDD and TDD.

GUI Value Range: BOTH(BOTH), FDD(FDD),

TDD(TDD)

Unit: None

Actual Value Range: BOTH, FDD, TDD

Default Value: BOTH(BOTH)

eRAN





46


51/71

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

LIOptR

ule

AtomRu

leRelati

onType

DSP

LIOPTR

ULE

LST

LIOPTR

ULE

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

on

Handlin

g

Automat

ic

Congesti

on

Handlin

g(TDD)

Meaning: Indicates the type of relationships between

atom rules under an intelligent optimization rule. If

this parameter is set to AND, optimization actions

corresponding to the intelligent optimization rule are

triggered only when all atom rules under this

intelligent optimization rule meet related

requirements. If this parameter is set to OR,

optimization actions corresponding to the intelligent

optimization rule are triggered when any atom rule

under this intelligent optimization rule meets related

requirements.

GUI Value Range: AND(AND), OR(OR)

Unit: None

Actual Value Range: AND, OR

Default Value: AND(AND)

LIOptR

ule

LocalCe

llId

DSP

LIOPTR

ULE

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

on

Handler

Automat

ic

Congestion

Handler(

TDD)

Meaning: Indicates the ID of the cell to which

intelligent optimization atom rules are applied. This


LIOPTRULE command. Information displayed in the

DSP LIOPTRULE command output is specific to the

cell. This parameter setting does not take effect when

the MeasureObjType parameter is set to eNodeB.


Unit: None


Default Value: None

LIOptR

ule

Executiv

eStatus

DSP

LIOPTR

ULE

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

on

Handlin

g

Automat

ic

Congesti

on

Handlin

g(TDD)

Meaning: Indicates the state of parameter adjustment

corresponding to an intelligent optimization rule. This


LIOPTRULE command. If this parameter value is

UN-EXECUTED, parameter adjustment is not

performed. If this parameter value is EXECUTING,

parameter adjustment is being performed. If thisparameter is EXECUTED, parameter adjustment has

been performed.

GUI Value Range: UN-EXECUTED(UN-

EXECUTED), EXECUTING(EXECUTING),

EXECUTED(EXECUTED)

Unit: None

Actual Value Range: UN-EXECUTED,

EXECUTING, EXECUTED

Default Value: None

eRAN





47


52/71

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

LIOptR

ule

IOptFun

ctionID

DSP

LIOPTR

ULE

LST

LIOPTR

ULE

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

on

Handlin

g

Automat

ic

Congesti

on

Handlin

g(TDD)




Unit: None


Default Value: 1

LIOptR

ule

Period MOD

LIOPTR

ULE

DSP

LIOPTR

ULE

LST

LIOPTR

ULE

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

on

Handlin

g

Automat

ic

Congesti

on

Handlin

g(TDD)

Meaning: Indicates the evaluation period of an

intelligent optimization rule.


Unit: s


Default Value: 300

LIOptR

ule

RuleID ACT

LIOPTR

ULE

DEA

LIOPTR

ULE

DSP

LIOPTR

ULE

LSTLIOPTR

ULE

MOD

LIOPTR

ULE

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

on

Handlin

g

Automat

ic

Congesti

on

Handlin

g(TDD)

Meaning: Indicates the ID of an intelligent

optimization rule.


Unit: None


Default Value: None

eRAN





48


53/71

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

LIOptAt

omRule

AtomRu

leID

LST

LIOPTA

TOMR

ULE

MOD

LIOPTA

TOMR

ULE

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

on

Handlin

g

Automat

ic

Congesti

on

Handlin

g(TDD)

Meaning: Indicates the ID of an intelligent

optimization atom rule.


Unit: None


Default Value: None

LIOptAt

omRule

Conditio

nType

LST

LIOPTA

TOMR

ULE

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

on

Handlin

g

Automat

ic

Congesti

on

Handlin

g(TDD)

Meaning: Indicates the relationship between

measurement objects and thresholds in intelligent

optimization atom rules. The parameter values

BIGGERTHAN, EQUALTO, SMALLERTHAN,

SMALLERTHANOREQUALTO,

BIGGERTHANOREQUALTO, and NOTEQUALTO

indicate the conditions of greater than, equal to,

smaller than, smaller than and equal to, greater than

and equal to, and not equal to, respectively.

GUI Value Range: BIGGERTHAN(BIGGERTHAN),

EQUALTO(EQUALTO),

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)

eRAN





49


54/71

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

LIOptAt

omRule

Measure

Object

LST

LIOPTA

TOMR

ULE

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

on

Handlin

g

Automat

ic

Congesti

on

Handlin

g(TDD)

Meaning: Indicates the measurement object in


set to USER_SPEC_OCCUPY_RATE, the

measurement object is the ratio of uplink

synchronized UEs to the total UEs. If this parameter is

set to UL_PRB_UTILIZATION_RATE, the

measurement object is uplink physical resource block

(PRB) usage. If this parameter is set to

DL_PRB_UTILIZATION_RATE, the measurement

object is the downlink PRB usage. If this parameter is

set to PDCCH_CCE_UTILIZATION_RATE, the

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

omRule

Measure

ObjType

LST

LIOPTA

TOMR

ULE

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

on

Handling

Automat

ic

Congesti

on

Handlin

g(TDD)

Meaning: Indicates the measurement object type in


set to Cell, the measurement objects are cell-level

atom rules. If this parameter is set to eNodeB, the

measurement objects are eNodeB-level atom rules.

GUI Value Range: Cell(Cell), eNodeB(eNodeB)

Unit: None

Actual Value Range: Cell, eNodeB

Default Value: Cell(Cell)

eRAN





50


55/71

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

LIOptAt

omRule

Threshol

dforNu

mPara

MOD

LIOPTA

TOMR

ULE

LST

LIOPTA

TOMR

ULE

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

on

Handlin

g

Automat

ic

Congesti

on

Handlin

g(TDD)

Meaning: Indicates the threshold for selecting

measurement objects with numerical values in

intelligent optimization atom rules.

GUI Value Range: -2147483647~2147483647

Unit: None

Actual Value Range: -2147483647~2147483647

Default Value: 0

LIOptR

uleMem

ber

ActiveSt

atus

MOD

LIOPTR

ULEME

MBER

LST

LIOPTR

ULEME

MBER

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

on

Handlin

g

Automat

ic

Congesti

on

Handlin

g(TDD)

Meaning: Indicates whether an intelligent

optimization rule member is activated. If this

parameter is set to ACTIVATED, the intelligent

optimization atom rules apply to the evaluation of the

associated intelligent optimization rule. If this

parameter is set to DEACTIVATED, the intelligent

optimization atom rules do not apply to the evaluation

of the associated intelligent optimization rule.

GUI Value Range: ACTIVATED(ACTIVATED),

DEACTIVATED(DEACTIVATED)

Unit: None

Actual Value Range: ACTIVATED, DEACTIVATED

Default Value: ACTIVATED(ACTIVATED)

LIOptR

uleMem

ber

RuleID LST

LIOPTR

ULEME

MBER

MOD

LIOPTR

ULEME

MBER

LOFD-0

81205

TDLOF

D-08120

9

Automat

ic

Congesti

on

Handlin

g

Automat

ic

Congesti

on

Handlin

g(TDD)


optimization rule to which the intelligent optimization

rule members associated.


Unit: None


Default Value: None

eRAN





51


56/71

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

CellDlsc

hAlgo

RbgAllo

cStrateg

y

MOD

CELLD

LSCHA

LGO

LST

CELLD

LSCHA

LGO

LBFD-0

02025/

TDLBF

D-00202

5

LOFD-0

0101502

/

TDLOF

D-00101

502

Basic

Scheduli

ng

Dynami

c

Scheduli

ng

Meaning: For services whose QoS class identifier

(QCI) is not 1: When this parameter is set to

ROUND_DOWN: (1) If the number of required

resource block groups (RBGs) is less than 1, the

actual number of RBs are allocated to UEs at the

current transmission time interval (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

RBGs are allocated to UEs in the current TTI and the

other required RBs are allocated to UEs in the next

TTI. Setting this parameter to ROUND_DOWN

ensures full utilization of RBs, but increases

scheduling times and decreases downlink data rate. Ifthis 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 inthe 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 areallocated 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

eRAN





52


57/71

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

Actual Value Range: ROUND_DOWN, ROUND_UP,

ADAPTIVE

Default Value: ROUND_DOWN(Round Down)

CellUlsc

hAlgo

UlRbAll

ocationS

trategy

MOD

CELLU

LSCHA

LGO

LST

CELLU

LSCHA

LGO

LOFD-0

0101502

/

TDLOF

D-00101

502

Dynami

c

Scheduli

ng

Meaning: Indicates the strategy for allocating resource

blocks (RBs) in the uplink of the cell. If this parameter

is set to FS_NONFS_ADAPTIVE, this strategy

adaptively switches between frequency selective

scheduling and non-frequency selective scheduling. If

this parameter is set to

FS_INRANDOM_ADAPTIVE, this strategy

adaptively switches between frequency selective

scheduling and interference-randomization-basedscheduling.

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)

TimeAlignment

Timer

TimingResOptS

witch

MODTATIM

ER

LST

TATIM

ER

None None Meaning: Indicates whether to enable the mechanismof optimized resource scheduling for uplink timing.If

this parameter is set to OFF, the eNodeB adopts the

existing resource scheduling policy for uplink timing,

which consumes a large amount of resources used for

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 valueON 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


eRAN





53


58/71

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

TimeAli

gnment

Timer

Timing

AdvCm

dOptSwi

tch

MOD

TATIM

ER

LST

TATIM

ER

None None Meaning:

Indicates whether optimization of the mechanism for

delivering the uplink time alignment command takes

effect. If the optimization takes effect, the number of

unnecessary uplink time alignment commands

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 thatthe 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


eRAN





54


59/71

MO Parameter ID

MMLCommand

FeatureID

FeatureName

Description

TimeAli

gnment

Timer

Timing

MeasMo

de

MOD

TATIM

ER

Automatic Congestion Handling(ERAN8.1_03)

Documents

Transcript of Automatic Congestion Handling(ERAN8.1_03)