You are on page 1of 1804

Radio and Performance

Radio and Performance


Contents
3.2 Radio and Performance
3.2.1 800M Self-interference Cancellation
3.2.2 Access Class Control
3.2.3 Admission and Congestion Control
3.2.4 AQM
3.2.5 Carrier Aggregation
3.2.6 Cell Management
3.2.7 Compact Bandwidth
3.2.8 Connection Management
3.2.9 CSPC
3.2.10 DRX and Signaling Control
3.2.11 DSCP-based Service Experience Guarantee
3.2.12 Extended Cell Range
3.2.13 Extended CP
3.2.14 Flexible User Steering
3.2.15 High Speed Mobility
3.2.16 ICIC
3.2.17 Idle Mode Management
3.2.18 Inter-RAT Mobility Load Balancing
3.2.19 Inter-RAT Mobility Management in Connected Mode
3.2.20 Intra-RAT Mobility Load Balancing
3.2.21 Intra-RAT Mobility Management in Connected Mode
3.2.22 LTE-CDMA2000 PS Service Interworking
3.2.23 MIMO
3.2.24 Multiple Frequency Band Indicator
3.2.25 Overview of Mobility Management in Connected Mode
3.2.26 Physical Channel Resource Management
3.2.27 Power Control
3.2.28 QoS Management
3.2.29 Receiver Technologies
3.2.30 Scheduling
3.2.31 SCTP Congestion Control
3.2.32 TDM eICIC
3.2.33 Terminal Awareness Differentiation
3.2.34 TPE
3.2.35 UL CoMP
3.2.36 Uplink Timing Control

2 Radio and Performance


It describes features related to radio and performance.

Parent topic: Description

eRAN

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

800M Self-interference Cancellation Feature Parameter Description


Issue 01

Date 2015-03-23

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: support@huawei.com

2.1 Contents
1 About This Document
1.1 Scope
1.2 Intended Audience
1.3 Change History
1.4 Differences Between eNodeB Types
2 Overview
3 Technical Description
4 Related Features
5 Network Impact
6 Engineering Guidelines
6.1 When to Use 800 MHz Self-interference Cancellation
6.2 Required Information
6.3 Planning
6.4 Deployment
6.4.1 Requirements
6.4.2 Data Preparation
6.4.3 Precautions
6.4.4 Activation
6.4.5 Activation Observation
6.4.6 Reconfiguration
6.4.7 Deactivation
6.5 Performance Monitoring

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

6.6 Parameter Optimization


6.7 Troubleshooting
7 Parameters
8 Counters
9 Glossary
10 Reference Documents

1 About This Document

1 Scope
This document describes LOFD-001067 800M Self-interference Cancellation, including its technical principles, related features, network impact, and engineering guidelines.
This document applies to the following types of eNodeBs.

eNodeB Type Model

Macro 3900 series eNodeB

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.

2 Intended Audience
This document is intended for personnel who:

Need to understand the features described herein


Work with Huawei products

3 Change History
This section provides information about the changes in different document versions. There are two types of changes:

Feature change
Changes in features and parameters of a specified version as well as the affected entities
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.

RAN8.1 01 (2015-03-23)

This issue does not include any changes.

RAN8.1 Draft A (2015-01-15)

Compared with Issue 01 (2014-04-26) of eRAN7.0, Draft A (2015-01-15) of eRAN8.1 includes the following changes.

Change Type Change Description Parameter Change

Feature change Added the mutual exclusion with LOFD-070205 Adaptive SFN/SDMA in 4 Related Features. None

Editorial change None None

4 Differences Between eNodeB Types


The features described in this document apply only to macro eNodeBs.

2 Overview

This document describes the optional feature LOFD-001067 800M Self-interference Cancellation, which only applies to 3900 series base stations in frequency division duplex (FDD) mode.

NOTE:
This feature does not apply to the LampSite solution.

A cell that operates in the 800 MHz frequency band (band 20) has an 11 MHz duplex frequency separation, as shown in Figure 2-1. Therefore, when a UE simultaneously transmits and receives data, the uplink causes interference to the downlink and the interference leads to deterioration in the downlink receiver sensitivity.
The degrees of interference and deterioration depend on the UE's duplex frequency separation, transmit power, and positions of uplink and downlink physical resource blocks (PRBs). The degrees also depend on the UE's transmit power and radio frequency (RF) component specifications.
Figure 2-1 shows the 800 MHz frequency band.
Figure 2-1 800 MHz frequency band

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

The 800 MHz self-interference cancellation feature applies to the following scenario:

UEs perform uplink and downlink services at the same time.


UEs have low specifications.
UEs' uplink signals cause intolerant interference to their downlink signals.

This feature does not apply to scenarios where there is no self-interference.

3 Technical Description

800 MHz self-interference is the interference that a UE's signal transmission induces on the UE's signal reception (that is, uplink-to-downlink interference) in a cell that operates in the 800 MHz frequency band. Self-interference is restricted by the RF component specifications of the UE and the narrow duplex frequency
separation of the 800 MHz frequency band. Self-interference mainly consists of intermodulation (IM) interference, including IM2, IM3, IM5, and IM7, which correspond to IM orders. The strength of self-interference is determined by the UE's transmit power and intermediate frequency (IF) performance, mainly referring to the
duplex frequency separation and non-linear power amplifier.

NOTE:
IM interference occurs when two or more interfering signals reach a UE's receiver at the same time. The frequency combination of these interfering signals is close or even identical to the frequency of a wanted signal because the power amplifier of the UE is non-linear. As a result, the UE cannot filter out these
interfering signals, and these signals interfere with wanted signals. Different frequency combinations cause different IM interference.
Downlink-to-uplink interference is due to the eNodeB and can be mitigated by selecting RF components with good performance, which is usually done before network construction. By contrast, uplink-to-downlink interference is due to UEs, but the UEs' types, models, and RF component specifications are
uncontrollable. Therefore, the eNodeB needs to use some algorithms to reduce uplink-to-downlink interference.
In this document, self-interference refers to uplink-to-downlink interference on the UE side.

The impact of 800 MHz self-interference varies according to the bandwidth:

A cell with a 5 MHz bandwidth has a wide frequency separation, and therefore the impact of self-interference caused by a narrow duplex frequency separation is small enough to ignore.
A cell with a 10 MHz, 15 MHz, or 20 MHz bandwidth has a narrow frequency separation and therefore self-interference exists. Downlink PRBs at any positions in the spectrum may experience interference from the uplink. When the UE is not tolerant of the interference, 800 MHz self-interference cancellation is
required.

NOTE:
A cell operating in the 800 MHz frequency band (band 20) does not support a 1.4 MHz or 3 MHz bandwidth, according to 3GPP specifications.

Assume that a UE in a cell with a bandwidth of 20 MHz is allocated 50 PRBs for uplink transmission. In this case, the start position of uplink PRBs is at 836.5 MHz (831 MHz + 25 x 180 kHz = 836.5 MHz). Then, the red curve in Figure 3-1 represents self-interference.
Figure 3-1 Self-interference in the 800 MHz frequency band

NOTE:
Figure 3-1 is only a schematic diagram because the result is obtained without the duplexer's suppression.

800 MHz self-interference cancellation is controlled by ImIcSwitch(ImIcSwitch) under CellAlgoSwitch.UlSchSwitch. If ImIcSwitch(ImIcSwitch) is selected, the eNodeB mitigates self-interference and increases downlink capacity by limiting the number of allocated uplink PRBs. For details, see 6 Engineering Guidelines.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

4 Related Features

erequisite Features

The 800 MHz self-interference cancellation feature depends on the feature LBFD-002025 Basic Scheduling.

utually Exclusive Features

This feature is mutually exclusive with the following feature:


LOFD-070205 Adaptive SFN/SDMA

pacted Features

This feature has impacts on LBFD-002025 Basic Scheduling. To mitigate self-interference, the eNodeB limits the number of uplink PRBs to be allocated. When this feature is effective, the uplink throughput decreases. The decreased uplink throughput is directly proportional to the reduced PRBs.

5 Network Impact

stem Capacity

The 800 MHz self-interference cancellation feature limits the number of allocated uplink PRBs to mitigate self-interference and to increase downlink capacity. However, this method has a negative impact on uplink capacity. The reduction degree of uplink capacity has a positive correlation with the reduction degree of uplink
PRBs.

etwork Performance

When the conditions for deploying the 800 MHz self-interference cancellation feature are fulfilled, this feature prevents a decrease in downlink throughput caused by self-interference but leads to a reduction in uplink throughput. The reduction degree of uplink throughput has a positive correlation with the reduction degree of
uplink PRBs.

6 Engineering Guidelines

1 When to Use 800 MHz Self-interference Cancellation


Operators can use the 800 MHz self-interference cancellation feature to increase downlink throughput in the following scenario:

The 800 MHz frequency band (band 20) is deployed to provide a bandwidth of 10 MHz, 15 MHz, or 20 MHz.
There are not more than one, two, or three UEs in a cell with the bandwidth of 10 MHz, 15 MHz, or 20 MHz, respectively.
UEs perform uplink and downlink services at the same time, and the uplink causes interference to the downlink.
A decrease in uplink throughput is acceptable.

2 Required Information
Before deploying the 800 MHz self-interference cancellation feature, collect the following information:

UE transmit power
The transmit power of UEs can be obtained usually from section 6.2.2 in 3GPP TS 36.101 V10.6.0.
UE performance, including the duplex frequency separation, modulator performance, and non-linear power amplifier performance
The performance of UEs can be obtained by analyzing and taking statistics on the performance indicators and specifications of the RF components that cause self-interference.

3 Planning
This feature does not require special network planning. Perform network planning for cells operating in the 800 MHz frequency band in the same way as you do for other cells. That is, perform network planning based on information such as the inter-site spacing, eNodeB transmit power, UE transmit power, and throughput
of CEUs.

4 Deployment

6.4.1 Requirements
The operator has purchased and activated the license for the feature listed in the following table.

Feature ID Feature Name Model License Control Item NE Sales Unit

LOFD-001067 800 MHz Self-interference Cancellation LT1S800MSC00 800M Self-interference Cancellation(FDD) eNodeB Per cell

Required information has been collected before deployment. The evaluation result shows that there is a risk of uplink-to-downlink intermodulation interference in 800 MHz cells.

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.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

There are three types of data sources:

Network plan (negotiation required): parameter values planned by the operator and negotiated with the evolved packet core (EPC) or peer transmission equipment
Network plan (negotiation not required): parameter values planned and set by the operator
User-defined: parameter values set by users.

equired Data

The following table describes the parameter that must be set in the CellAlgoSwitch MO.

Parameter Name Parameter ID Data Source Setting Notes

Uplink schedule switch CellAlgoSwitch.UlSchSwitch Network plan (negotiation not required) This parameter specifies the switch ImIcSwitch for the 800 MHz self-
interference cancellation feature.
If ImIcSwitch is turned on, the feature is enabled. If ImIcSwitch is
turned off, the feature is disabled.

enario-specific Data

None

6.4.3 Precautions
When this feature is in effect, the GBR may not be ensured for uplink services.

6.4.4 Activation
sing the CME to Perform Batch Configuration for Newly Deployed eNodeBs

Enter the values of the parameters listed in Table 6-1 in a summary data file, which also contains other data for the new eNodeBs to be deployed. Then, import the summary data file into the Configuration Management Express (CME) for batch configuration. For detailed instructions, see section "Creating eNodeBs in
Batches" in the initial configuration guide for the eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized file, depending on the following conditions:

The managed objects (MOs) in Table 6-1 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.
Some MOs in Table 6-1 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-1 Parameters related to 800 MHz self-interference cancellation

MO Sheet in the Summary Data File Parameter Group Remarks

CellAlgoSwitch User-defined sheet LocalCellID, CellAlgoSwitch None

sing the CME to Perform Batch Configuration for Existing eNodeBs

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:

1. Choose CME > Advanced > Customize Summary Data File (U2000 client mode), or choose Advanced > Customize Summary Data File (CME client mode), to customize a summary data file for batch reconfiguration.

NOTE:
For context-sensitive help on a current task in the client, press F1.

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.
3. In the summary data file, set the parameters in the MOs listed in Table 6-1 and close the file.
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.
5. 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.

sing the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB. The procedure is as follows:

1. In the planned data area, click Base Station in the upper left corner of the configuration window.
2. In area 1 shown in Figure 6-1, select the eNodeB to which the MOs belong.
Figure 6-1 MO search and configuration window

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

3. On the Search tab page in area 2, enter an MO name, for example, CELL.
4. In area 3, double-click the MO in the Object Name column. All parameters in this MO are displayed in area 4.
5. Set the parameters in area 4 or 5.
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.

sing MML Commands

Run the MOD CELLALGOSWITCH command with the ImIcSwitch check box selected under the CellAlgoSwitch.UlSchSwitch parameter.

ML Command Examples

MOD CELLALGOSWITCH: LocalCellId=0, UlSchSwitch=ImIcSwitch-1;

6.4.5 Activation Observation


This section describes how to verify the activation when the UEs in the cell center or on the cell edge are experiencing high traffic in both the uplink and downlink.
The observation procedure is as follows:

Starting cell performance monitoring on the U2000 client

1. Choose Monitoring > Signaling Trace > Signaling Trace Management.


2. In the navigation tree on the left of the Signaling Trace Management window, choose Cell Performance Monitoring > General Throughput Monitoring and click New.
This task measures the downlink data throughput at the RLC layer, which is indicated by Cell Downlink RLC Throughput(bps).
3. Compare the measurement results before and after deploying 800 MHz self-interference cancellation.
If the counter value increases, the feature is successfully activated.

Starting UE performance monitoring on the U2000 client

1. Choose Monitoring > Signaling Trace > Signaling Trace Management.


2. In the navigation tree on the left of the Signaling Trace Management window, choose User Performance Monitoring > Throughput Monitoring and click New.
This task measures the downlink data throughput at the RLC layer, which is indicated by Downlink RLC Throughput(bps).
3. Compare the measurement results before and after deploying 800 MHz self-interference cancellation.
If the counter value increases, the feature is successfully activated.

6.4.6 Reconfiguration
None

6.4.7 Deactivation
sing 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 Using the CME to
Perform Batch Configuration for Existing eNodeBs. In the procedure, modify parameters according to Table 6-2.

Table 6-2 Parameters related to 800 MHz self-interference cancellation

MO Sheet in the Summary Data File Parameter Group Setting Notes

CellAlgoSwitch User-defined sheet LocalCellIDCellAlgoSwitch Turn off ImIcSwitch.

sing the CME to Perform Single Configuration

On the CME, set parameters according to Table 6-2. For detailed instructions, see Using the CME to Perform Single Configuration for feature activation.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

sing MML Commands

Run the MOD CELLALGOSWITCH command with the ImIcSwitch check box cleared under the CellAlgoSwitch.UlSchSwitch parameter.

ML Command Examples

MOD CELLALGOSWITCH: LocalCellId=0, UlSchSwitch=ImIcSwitch-0;

5 Performance Monitoring
None

6 Parameter Optimization
N/A

7 Troubleshooting
If this feature cannot work correctly, perform the following steps for troubleshooting:

1. Check that the license is correct and does not exceed the validity period.
2. Check that the conditions for using this feature are met. For details, see When to Use 800 MHz Self-interference Cancellation.
3. Check that the deployment requirements are fulfilled. For details, see 6.4.1 Requirements.
4. Check that the feature is activated successfully. For details, see 6.4.5 Activation Observation.
5. If this feature still fails to work after the preceding checks, contact Huawei technical support.

7 Parameters

Table 7-1 Parameters

MO Parameter ID MML Command Feature ID Feature Name Description

CellAlgoSwitch UlSchSwitch MOD CELLALGOSWITCH LOFD-001016 / TDLOFD- VoIP Semi-persistent Meaning:


LST CELLALGOSWITCH 001016 Scheduling This parameter indicates the switches related to uplink (UL) scheduling in the cell. The switches are used to enable or disable specific UL
LOFD-001048 / TDLOFD- TTI Bundling scheduling functions.
001048 Dynamic Scheduling SpsSchSwitch: Indicates the switch used to enable or disable semi-persistent scheduling during talk spurts of VoIP services. If this switch is
LOFD-00101502 / Basic SchedulingTDLOFD- on, semi-persistent scheduling is applied during talk spurts of VoIP services. If this switch is off, dynamic scheduling is applied during talk
TDLOFD-00101502 070224:Scheduling Based spurts of VoIP services.
TDLBFD-002025 on Max Bit Rate SinrAdjustSwitch: Indicates whether to adjust the measured signal to interference plus noise ratio (SINR) based on ACK/NACK in UL hybrid
LBFD-070102 / TDLBFD- MBR>GBR Configuration automatic repeat request (HARQ) processes.
070102 UL 2x2 MU-MIMO PreAllocationSwitch: Indicates whether to enable preallocation in the uplink. When this switch is on: (1) If SmartPreAllocationSwitch is off and
LOFD-001002 UL 2x4 MU-MIMO a UE is in the discontinuous reception (DRX) state, preallocation is disabled for the UE in the uplink; (2) If SmartPreAllocationSwitch is off
LOFD-001058 AMC and the UE is not in the DRX state, preallocation is enabled for the UE in the uplink; (3) If SmartPreAllocationSwitch is on and the
LBFD-001006 SmartPreAllocationDuration parameter value is greater than 0, smart preallocation is enabled for the UE in the uplink; (4) If
SmartPreAllocationSwitch is on and the SmartPreAllocationDuration parameter value is 0, preallocation is disabled for the UE in the uplink. If
this switch is off, preallocation is disabled for the UE in the uplink. If bearer-level preallocation or bearer-level smart preallocation is enabled
for a UE with a QCI class, cell-level preallocation and cell-level smart preallocation do not apply to UEs with the QCI.
UlVmimoSwitch: Indicates whether to enable multi-user MIMO (MU-MIMO) in the UL. If this switch is on, the eNodeB performs MU-MIMO
pairing among UEs based on related principles. UEs forming a pair transmit data using the same time-frequency resources, which improves
system throughput and spectral efficiency.
TtiBundlingSwitch: Indicates whether to enable transmission time interval (TTI) bundling. If TTI bundling is enabled, more transmission
opportunities are available to UEs within the delay budget for VoIP services on the Uu interface, thereby improving uplink coverage.
ImIcSwitch: Indicates whether to enable the intermodulation interference (IM) cancellation for UEs. When data is transmitted in both uplink
and downlink, two IM components are generated symmetrically beside the Direct Current (DC) subcarrier on the downlink receive channel
due to interference from uplink radio signals. If this switch is on, IM component elimination is performed on UEs. If this switch is off, IM
component elimination is not performed on UEs. This switch applies only to FDD cells working in frequency band 20.
SmartPreAllocationSwitch: Indicates whether to enable uplink smart preallocation when preallocation is enabled (by turning on
PreAllocationSwitch). If both PreAllocationSwitch and SmartPreAllocationSwitch are on and SmartPreAllocationDuration is set to a value
greater than 0, uplink smart preallocation is enabled; otherwise, uplink smart preallocation is disabled.
PuschDtxSwitch: Indicates whether the eNodeB uses the physical uplink shared channel (PUSCH) discontinuous transmission (DTX)
detection result during UL scheduling. In an LTE FDD cell, if this switch is on, based on the PUSCH DTX detection result, the eNodeB
determines whether to perform adaptive retransmission during UL scheduling and also adjusts the control channel element (CCE)
aggregation level of the physical downlink control channel (PDCCH) carrying downlink control information (DCI) format 0. If an FDD cell is
established on an LBBPc, this switch takes effect only when the cell uses less than four RX antennas and normal cyclic prefix (CP) in the
uplink and the SrsCfgInd parameter in the SRSCfg MO is set to BOOLEAN_TRUE. Note that the LBBPc does not support PUSCH DTX
detection for UEs with MU-MIMO applied. In an LTE TDD cell, this switch takes effect only when the cell is configured with subframe
configuration 2 or 5. After this switch takes effect, the eNodeB adjusts the CCE aggregation level based on the PUSCH DTX detection
results. Note that LTE TDD cells established on LBBPc boards do not support PUSCH DTX detection.
UlIblerAdjustSwitch: Indicates whether to enable the uplink initial block error rate (IBLER) adjustment algorithm. If this switch is on, IBLER
convergence target is adjusted to increase the cell edge throughput. When this switch is on, the recommended configuration of parameter
DopMeasLevel in MO CellUlschAlgo is CLASS_1.
UlEnhancedFssSwitch: Indicates whether to enable uplink load-based enhanced frequency selection. This switch applies only to FDD cells.
UlIicsAlgoSwitch: Indicates whether to enable the UL IICS algorithm. If this switch is on, interference can be reduced based on accurate

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

detection of user attributes and resource scheduling coordination, thereby increasing the cell edge throughput.
UlEnhancedSrSchSwitch: Indicates whether uplink re-scheduling is performed only when the On Duration timer for the DRX long cycle starts.
Uplink re-scheduling is required if the number of HARQ retransmissions for a scheduling request (SR) reaches the maximum value but the
scheduling still fails. If this switch is on, uplink re-scheduling is performed only when the On Duration timer for the DRX long cycle starts. If
this switch is off, uplink re-scheduling is performed immediately when the number of HARQ retransmissions for SR reaches the maximum
value but the scheduling still fails. It is recommended that the switch be turned on in live networks.
SchedulerCtrlPowerSwitch: Indicates whether the uplink scheduler performs scheduling without considering power control restrictions. If this
switch is on, the uplink scheduler performs scheduling without considering power control restrictions, which ensures full utilization of the
transmit power for all UEs. If this switch is off, the uplink scheduler considers power control restrictions while performing scheduling, which
prevents full utilization of the transmit power for UEs at far or medium distances from the cell center.
UlMinGbrSwitch: Indicates whether to enable uplink minimum guaranteed bit rate (GBR). If this switch is on, the minimum GBR of non-GBR
services is ensured by increasing the scheduling priority of UEs whose non-GBR service rates are lower than the minimum GBR of GBR
services.
UlMbrCtrlSwitch: Indicates whether to enable uplink 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 uplink scheduling on GBR bearers based on the MBR and GBR. If this switch is off,
the eNodeB performs uplink scheduling on GBR bearers based only on the GBR.
MbrUlSchSwitch: Indicates whether the eNodeB performs uplink scheduling based on MBR. If this switch is on, the eNodeB prioritizes UEs
based on the MBRs during uplink scheduling. This parameter applies only to LTE TDD cells.
UeAmbrUlSchSwitch: Indicates whether the eNodeB performs uplink scheduling based on the aggregate maximum bit rate (AMBR) of UEs. If
this switch is on, the eNodeB prioritizes UEs based on the AMBRs during uplink scheduling. This parameter applies only to LTE TDD cells.
UlEnhancedDopplerSwitch: Indicates whether to enable enhanced uplink scheduling based on mobility speed. If this switch is on, enhanced
uplink scheduling based on mobility speed is enabled. If this switch is on, the eNodeB determines whether a UE is a low-mobility UE based
on the Doppler measurement in the physical layer, and then improves uplink frequency selective scheduling performance for low-mobility
UEs. If this switch is off, enhanced uplink scheduling based on mobility speed is disabled. This switch takes effect only when the
UlEnhancedDopplerSwitch parameter is set to CLASS_1. This switch does not take effect on cells established on an LBBPc.
UlRaUserSchOptSw: Indicates whether the eNodeB raises the scheduling priority of UEs sending uplink access signaling, including MSG5
and the RRC Connection Reconfiguration Complete message. If this switch is on, the eNodeB raises the scheduling priority of UEs sending
uplink access signaling. If this switch is off, the eNodeB does not raise the scheduling priority of UEs sending uplink access signaling.
UlLast2RetransSchOptSwitch: Indicates whether to enable optimization on the scheduling policy for the last two retransmissions. If this
switch is on, optimization on the scheduling policy for the last two retransmissions is enabled. If the UE transmit power is not limited, adaptive
retransmission is used and the number of RBs increases in the last two retransmissions to increase the receive success rate of the last two
retransmissions and decrease uplink RBLER. If this switch is off, optimization on the scheduling policy for the last two retransmissions is
disabled. This switch does not apply to LTE TDD cells.
UlInterfFssSwitch: Indicates whether to enable interference-based uplink frequency-selective scheduling.
UlSmallRBSpectralEffOptSw: Indicates whether to enable spectral efficiency optimization on uplink small RBs. If this switch is on, the
optimization is enabled, thereby ensuring that the transmission block size calculated based on optimized spectral efficiency is not less than
the traffic volume needs to be scheduled. If this switch is off, the optimization is disabled.
PuschUsePucchRbSwitch: Indicates whether PUCCH RBs can be occupied by the PUSCH. In scenarios with a single user, if this switch is
on, PUCCH RBs can be occupied by the PUSCH. If this switch is off, PUCCH RBs cannot be occupied by the PUSCH. In scenarios with
multiple users, PUCCH RBs cannot be occupied by the PUSCH no matter whether this switch is on or off.
PuschDtxSchOptSwitch: If this switch is on, the eNodeB determines whether to perform adaptive retransmission during UL scheduling based
on the PUSCH DTX detection result. This switch takes effect only when subframe configuration 2 or 5 is used. If a TDD cell is established on
an LBBPc, PUSCH DTX detection is not supported. This switch applies only to LTE TDD cells.
PrachRbReuseSwitch:If this switch is on, the PUSCH and PRACH transmissions can use the same resource.
If this switch is off, the PUSCH and PRACH transmissions cannot use the same resource. This switch applies only to LTE TDD cells.
ULFSSAlgoswitch:If this switch is off, uplink frequency-selective scheduling is disabled. If this switch is on, uplink frequency-selective
scheduling is enabled. This switch is invalid if the HighSpeedFlag parameter in the Cell MO is set to HIGH_SPEED(High speed cell flag) or
ULTRA_HIGH_SPEED(Ultra high speed cell flag), that is, uplink frequency-selective scheduling is disabled in high speed and ultra high
speed mobility conditions. This switch applies only to LTE TDD cells.
SrSchDataAdptSw: Indicates whether to enable data volume adaption in SR scheduling. Data volume adaption in SR scheduling is enabled
only when this option is selected.
UlFssUserThdStSwitch: UlFssUserThdStSwitch: Indicates whether to enable the optimization policy on the UE number threshold for
frequency selective scheduling. The optimization policy is enabled only when this option is selected.
GUI Value Range: SpsSchSwitch(SpsSchSwitch), SinrAdjustSwitch(SinrAdjustSwitch), PreAllocationSwitch(PreAllocationSwitch),
UlVmimoSwitch(UlVmimoSwitch), TtiBundlingSwitch(TtiBundlingSwitch), ImIcSwitch(ImIcSwitch),
SmartPreAllocationSwitch(SmartPreAllocationSwitch), PuschDtxSwitch(PuschDtxSwitch), UlIblerAdjustSwitch(UlIblerAdjustSwitch),
UlEnhancedFssSwitch(UlEnhancedFssSwitch), UlEnhancedSrSchSwitch(UlEnhancedSrSchSwitch),
SchedulerCtrlPowerSwitch(SchedulerCtrlPowerSwitch), UlIicsAlgoSwitch(UlIicsAlgoSwitch), UlMinGbrSwitch(UlMinGbrSwitch),
UlMbrCtrlSwitch(UlMbrCtrlSwitch), MbrUlSchSwitch(MbrUlSchSwitch), UeAmbrUlSchSwitch(UeAmbrUlSchSwitch),
UlEnhancedDopplerSwitch(UlEnhancedDopplerSwitch), UlRaUserSchOptSw(UlRaUserSchOptSw),
UlLast2RetransSchOptSwitch(UlLast2RetransSchOptSwitch), UlInterfFssSwitch(UlInterfFssSwitch),
UlSmallRBSpectralEffOptSw(UlSmallRBSpectralEfficiencyOptSw), PuschUsePucchRbSwitch(PuschUsePucchRbSwitch),
PuschDtxSchOptSwitch(PuschDtxSchOptSwitch), ULFSSAlgoSwitch(ULFSSAlgoSwitch), PrachRbReuseSwitch(PrachRbReuseSwitch),
SrSchDataAdptSw(SrSchDataAdptSw), UlFssUserThdStSwitch(UlFssUserThdStSwitch)
Unit: None
Actual Value Range: SpsSchSwitch, SinrAdjustSwitch, PreAllocationSwitch, UlVmimoSwitch, TtiBundlingSwitch, ImIcSwitch,
SmartPreAllocationSwitch, PuschDtxSwitch, UlIblerAdjustSwitch, UlEnhancedFssSwitch, UlEnhancedSrSchSwitch,
SchedulerCtrlPowerSwitch, UlIicsAlgoSwitch, UlMinGbrSwitch, UlMbrCtrlSwitch, MbrUlSchSwitch, UeAmbrUlSchSwitch,
UlEnhancedDopplerSwitch, UlRaUserSchOptSw, UlLast2RetransSchOptSwitch, UlInterfFssSwitch, UlSmallRBSpectralEffOptSw,
PuschUsePucchRbSwitch, PuschDtxSchOptSwitch, ULFSSAlgoSwitch, PrachRbReuseSwitch, SrSchDataAdptSw, UlFssUserThdStSwitch
Default Value: SpsSchSwitch:Off, SinrAdjustSwitch:On, PreAllocationSwitch:On, UlVmimoSwitch:Off, TtiBundlingSwitch:Off, ImIcSwitch:Off,
SmartPreAllocationSwitch:Off, PuschDtxSwitch:On, UlIblerAdjustSwitch:Off, UlEnhancedFssSwitch:On, UlEnhancedSrSchSwitch:Off,
SchedulerCtrlPowerSwitch:Off, UlIicsAlgoSwitch:Off, UlMinGbrSwitch:Off, UlMbrCtrlSwitch:Off, MbrUlSchSwitch:Off,
UeAmbrUlSchSwitch:Off, UlEnhancedDopplerSwitch:Off, UlRaUserSchOptSw:Off, UlLast2RetransSchOptSwitch:Off, UlInterfFssSwitch:Off,
UlSmallRBSpectralEffOptSw:Off, PuschUsePucchRbSwitch:Off, PuschDtxSchOptSwitch:Off, ULFSSAlgoSwitch:On,

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

PrachRbReuseSwitch:Off, SrSchDataAdptSw:On, UlFssUserThdStSwitch:Off

8 Counters

There are no specific counters associated with this feature.

9 Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

10 Reference Documents

1. 3GPP TS 36.101, "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception"

eRAN
Access Class Control Feature Parameter Description
Issue 01

Date 2015-03-23

HUAWEI TECHNOLOGIES CO., LTD.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

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: support@huawei.com

2.2 Contents
1 About This Document
1.1 Scope
1.2 Intended Audience
1.3 Change History
1.4 Differences Between eNodeB Types
2 Overview
2.1 Introduction
2.2 Benefits
2.3 Architecture
3 Concepts
3.1 Access Types
3.2 AC Control Parameters
4 Static AC Control
4.1 Static AC control Procedure
4.2 Access Decision Procedure
5 Intelligent AC Control
5.1 Intelligent AC Control Procedure
5.2 Implementation Principles
5.3 Access Probability Factor Adjustment
6 Dynamic SSAC
6.1 Dynamic SSAC Procedure
6.2 Implementation Principles
6.3 Access Probability Factor Adjustment
7 Related Features
7.1 Features Related to LOFD-070207 Intelligent Access Class Control
7.2 Features Related to LOFD-008002 Dynamic Service-specific Access Control
8 Network Impact
8.1 LOFD-070207 Intelligent Access Class Control
8.2 LOFD-008002 Dynamic Service-specific Access Control
9 Engineering Guidelines
9.1 When to Use Access Class Control
9.2 Required Information
9.3 Planning
9.3.1 RF Planning
9.3.2 Network Planning
9.3.3 Hardware Planning
9.4 Deployment
9.4.1 Requirements

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

9.4.2 Data Preparation


9.4.3 Initial Configuration
9.4.4 Activation Observation
9.4.5 Reconfiguration
9.4.6 Deactivation
9.5 Performance Monitoring
9.6 Parameter Optimization
9.7 Troubleshooting
10 Parameters
11 Counters
12 Glossary
13 Reference Documents

1 About This Document

1 Scope
This document describes access class (AC) control, including its technical principles, related features, network impact, and engineering guidelines.
This document covers the following features:

LOFD-070207 Intelligent Access Class Control


LOFD-008002 Dynamic Service-specific Access Control

This document applies to the following types of eNodeBs.

eNodeB Type Model

Macro 3900 series eNodeB

Micro BTS3202E

LampSite DBS3900

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.

2 Intended Audience
This document is intended for personnel who:

Need to understand Access Class Control


Work with Huawei products

3 Change History
This section provides information about the changes in different document versions. There are two types of changes:

Feature change
Changes in features and parameters of a specified version as well as the affected entities
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.

RAN8.1 01 (2015-03-23)

This issue does not include any changes.

RAN8.1 Draft A (2015-01-15)

Compared with Issue 01 (2014-04-26) of eRAN7.0, Draft A (2015-01-15) of eRAN8.1 includes the following changes.

Change Type Change Description Parameter Change Affected Entity

Feature change Added LOFD-008002 Dynamic Service-specific Access Control. For details Added the following parameters: Macro/Micro/LampSite
about this feature, see 6 Dynamic SSAC and 9 Engineering Guidelines. CellAlgoSwitch.AcBarAlgoforDynSwitch
CellDynAcBarAlgoPara.DisasterReferenceInd
CellDynAcBarAlgoPara.DisasterDuration
CellDynAcBarAlgoPara.SsacTriggerCondSatiPeriods
CellDynAcBarAlgoPara.SsacCancelCondSatiPeriods

Optimized the mechanisms for triggering and canceling intelligent AC control. Added the following parameters: Macro/Micro/LampSite
For details, see 5 Intelligent AC Control and 9 Engineering Guidelines. CellDynAcBarAlgoPara.MoTriggerCondSatiPeriods
CellDynAcBarAlgoPara.MoCancelCondSatiPeriods

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

Added the policy options for determining whether a cell is congested. For Added the following parameters: Macro/Micro/LampSite
details, see 5.2 Implementation Principles and 6.2 Implementation Principles. EnodebFlowCtrlPara.DynAcBarPolicyMode
EnodebFlowCtrlPara.CpuLoadThd

Editorial change Revised the description in this document. None   

4 Differences Between eNodeB Types


ature Support by Macro, Micro, and LampSite eNodeBs

Feature ID Feature Name Supported by Macro eNodeBs Supported by Micro eNodeBs Supported by LampSite eNodeBs

LOFD-070207 Intelligent Access Class Control Y Y Y

LOFD-008002 Dynamic Service-specific Access Control Y Y Y

nction Implementation in Macro, Micro, and LampSite eNodeBs

Function Difference

Triggering of flow control in intelligent AC control For macro eNodeBs, flow control is triggered by a large amount of RRC signaling or RACH signaling. For micro eNodeBs, flow control is triggered only by a large amount of RACH signaling. For details, see 5.2
Implementation Principles.

2 Overview

1 Introduction
As defined in 3GPP TS 36.331, access class (AC) control is a method used to manage UE access to the network. With AC control, the eNodeB broadcasts AC control parameters to all UEs in a cell through System Information Block 2 (SIB2) messages. UEs determine whether they can access the cell based on this
information.
Huawei provides three AC control methods: static AC control, intelligent AC control, and dynamic service-specific access control (SSAC):

Static AC control: After AC control parameters are configured on the Operating Support System (OSS) by an operator, the eNodeB broadcasts parameters to UEs through system information (SI), without considering the current network load.
Intelligent AC control: The eNodeB determines whether to adjust and deliver AC control parameters for mobile originated (MO) data and MO signaling in a cell based on the cell congestion state.
Dynamic SSAC: The eNodeB determines whether to adjust and deliver AC control parameters for multimedia telephony voice and multimedia telephony video in a cell based on whether the cell is congested and whether the area where the cell is located is in a disaster.

According to section 5.3.3 "RRC connection establishment" in 3GPP TS 36.331 V11.2.0, only mobile originating UEs perform access decision after receiving AC control parameters from the eNodeB. UEs handed over from other cells or mobile terminating UEs do not perform access decision.
When a UE transits from the idle mode to the connected mode, it sends an RRC Connection Request message to the eNodeB. The UE determines whether its access is allowed based on access barring information broadcast in system information and the cause of RRC connection setup or the cause of UE access. The
CellAcBar.AcBarringInfoCfgInd parameter specifies whether access barring information is broadcast.

NOTE:
When selecting a cell to camp on, a UE does not consider access barring information, which means that a UE of a specific access class still camps on a cell though access to that cell is not allowed for that access class. In addition, the UE does not perform cell reselection when the indicated access barring information
changes.

2 Benefits
Static AC control enables operators to perform AC control by configuring parameters if a large number of UEs access the network simultaneously. This method, however, requires operators to set the AC control switch based on real-time network conditions because the network load changes dynamically.
Compared with static AC control, intelligent AC control offers the following benefits:

Controls the access of UEs initiating MO data or MO signaling to prevent a sharp increase in signaling load.
Performs AC control based on the cell congestion state without manual intervention.
Relieves cell congestion.

Compared with static AC control, dynamic SSAC offers the following benefits:

Controls the access of UEs initiating multimedia telephony voice or multimedia telephony video to prevent network congestion and ensure that UEs initiating data services can timely access the disaster bulletin information on the network.
Performs AC control based on the disaster state and cell congestion state without manual intervention.

3 Architecture
atic AC Control

Figure 2-1 shows the network architecture for static AC control. The access of UEs is controlled even when the network load is light.
Figure 2-1 Network architecture for static AC control

1. AC control parameters configured on the OSS are sent to the eNodeB.


2. The eNodeB broadcasts parameters to UEs through SIB2 message update.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

3. UEs decide whether to initiate an access procedure to this cell.

elligent AC Control

Figure 2-2 shows the network architecture for intelligent AC control.


Figure 2-2 Network architecture for intelligent AC control

1. AC control parameters configured on the OSS are sent to the eNodeB.


2. The eNodeB determines whether to trigger AC control based on the cell congestion state.
3. The eNodeB broadcasts parameters to UEs in the cell if the AC control triggering condition is met.
4. The eNodeB periodically checks whether cell congestion is relieved. If no, it adjusts access probability factors to expand the control range until the cell congestion is relieved.
5. The eNodeB broadcasts adjusted parameters to UEs through SIB2 messages.
6. UEs decide whether to initiate an access procedure to this cell.

ynamic SSAC

Figure 2-3 shows the network architecture for dynamic SSAC.

Figure 2-3 Network architecture for dynamic SSAC

1. AC control parameters configured on the OSS are sent to the eNodeB.


2. The eNodeB determines whether to trigger dynamic SSAC based on the cell congestion state and disaster state.
3. The eNodeB broadcasts parameters to UEs in the cell if the condition for triggering dynamic SSAC is met.
4. The eNodeB periodically checks whether the cell congestion is relieved or the disaster state is ended. If no, it adjusts access probability factors to expand the control range or maintains the access probability factors until the cell congestion is relieved or the disaster state is ended.
5. The eNodeB broadcasts adjusted parameters to UEs through SIB2 messages.
6. UEs decide whether to initiate an access procedure to this cell.

3 Concepts

1 Access Types
Based on the access cause and service type, SIB2 messages can contain the following access types in the ac-BarringInfo IE:

Emergency call
Mobile originating data (MO data)
Mobile originating signaling (MO signaling)
Multimedia telephony voice
Multimedia telephony video
CS fallback (CSFB)

2 AC Control Parameters
For emergency calls, an AC control parameter is defined to specify whether to perform AC control.
For other access types, the following parameters are defined in 3GPP specifications:

ac-BarringFactor
A random number (rand) is generated by the UE after it initiates an access request. If the value of rand is less than that of ac-BarringFactor, the UE proceeds with the access procedure. If the value of rand is greater than or equal to that of ac-BarringFactor, the UE stops the access procedure.
ac-BarringTime
Together with rand, this parameter determines the duration for barring this access request as follows: Access barring duration = (0.7 + 0.6 x rand) x ac-BarringTime After the duration ends, the UE generates a rand and compares it with ac-BarringFactor again.
ac-BarringForSpecialAC
This parameter determines whether UEs of AC 11 to AC 15 can access the cell.

According to 3GPP specifications, ac-BarringFactor can be set only to P00(0%) when any of the bits of ac-BarringForSpecialAC is set to 1. For details, see section 6.3.1 "System information blocks" in 3GPP TS 36.331 V11.2.0.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

4 Static AC Control

1 Static AC control Procedure


Static AC control applies to the following access types:

Emergency call, MO data, and MO signaling, which are introduced in 3GPP Release 8
SSAC Multimedia telephony voice and multimedia telephony video, which are introduced in 3GPP Release 9
CSFB, which is introduced in 3GPP Release 10

NOTE:
SSAC is performed specifically for multimedia telephony voice and multimedia telephony video.

A UE checks whether to start cell access based on its access type and AC control parameters from the eNodeB:

For emergency calls, MO signaling, MO data, and CSFB, the UE checks at the access stratum (AS) whether to start cell access.
For multimedia telephony voice and multimedia telephony video, the UE checks at the non-access stratum (NAS) whether to start cell access. If the check is passed and AC control parameters for MO data are available, the UE then checks again at the AS whether to start cell access.

Figure 4-1 shows the general process of static AC control.

Figure 4-1 General process of static AC control

AC barring for different access types is controlled by the following parameters:

CellAcBar.AcBarringForEmergency for emergency calls (AC 10)


CellAcBar.AcBarringForMoDataCfgInd for MO data
CellAcBar.AcBarringForMoSigCfgInd for MO signaling
CellAcBar.AcBarForMVoiceCfgInd for multimedia telephony voice
CellAcBar.AcBarForMVideoCfgInd for multimedia telephony video
CellAcBar.AcBarForCsfbCfgInd for CSFB

After the eNodeB delivers AC control parameters, UEs perform access decision based on these parameters.

NOTE:
For details about the list of barred ACs and how a UE determines its AC, see chapter 4 "Access control" in 3GPP TS 22.011 V10.0.0 and section 3.4 "Access control" in 3GPP TS 23.122 V10.0.0.

When CellAlgoSwitch.AcBarAlgoSwitch is set to ACBAR_SWITCH_STATIC(static configuration), static AC control is used. The eNodeB determines whether to perform AC control on an access type based on the settings of parameters in the CellAcBar MO.
When CellAlgoSwitch.AcBarAlgoSwitch is set to ACBAR_SWITCH_DISABLE(Disable), AC control is disabled.

2 Access Decision Procedure


This section describes the access decision procedures that UEs perform after receiving AC control parameters.

mergency Calls

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

Figure 4-2 shows the access decision procedure for emergency calls.
Figure 4-2 Access decision procedure for emergency calls

O Data

Figure 4-3 shows the access decision procedure for MO data.

Figure 4-3 Access decision procedure for MO data

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

The access barring timer for MO data is started by the UE originating the call. The timer length is calculated based on the value of the CellAcBar.AcBarTimeForCall parameter. For details, see section 5.3.3.11 "Access barring check" in 3GPP TS 36.331 V11.2.0.
The AC control for MO data is specified by the following parameters:

CellAcBar.AcBarringFactorForCall: specifies the access probability factor for MO data.


CellAcBar.AcBarTimeForCall: specifies the access barring duration for MO data.
CellAcBar.AC11BarforCall: specifies the access barring indicator for MO data on UEs of AC 11.
CellAcBar.AC12BarforCall: specifies the access barring indicator for MO data on UEs of AC 12.
CellAcBar.AC13BarforCall: specifies the access barring indicator for MO data on UEs of AC 13.
CellAcBar.AC14BarforCall: specifies the access barring indicator for MO data on UEs of AC 14.
CellAcBar.AC15BarforCall: specifies the access barring indicator for MO data on UEs of AC 15.

The CellAcBar.AcBarringFactorForCall parameter can be set only to P00(0%) when any of the parameters CellAcBar.AC11BarforCall to CellAcBar.AC15BarforCall is set to BOOLEAN_TRUE(true).

O Signaling

Figure 4-4 shows the access decision procedure for MO signaling.

Figure 4-4 Access decision procedure for MO signaling

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

The access barring timer for MO signaling is started by the UE originating the signaling. The timer length is calculated based on the value of the CellAcBar.AcBarTimeForSig parameter. For details, see section 5.3.3.11 "Access barring check" in 3GPP TS 36.331 V11.2.0.
The AC control for MO signaling is specified by the following parameters:

CellAcBar.AcBarringFactorForSig: specifies the access probability factor for MO signaling.


CellAcBar.AcBarTimeForSig: specifies the access barring duration for MO signaling.
CellAcBar.AC11BarForSig: specifies the access barring indicator for MO signaling on UEs of AC 11.
CellAcBar.AC12BarForSig: specifies the access barring indicator for MO signaling on UEs of AC 12.
CellAcBar.AC13BarForSig: specifies the access barring indicator for MO signaling on UEs of AC 13.
CellAcBar.AC14BarForSig: specifies the access barring indicator for MO signaling on UEs of AC 14.
CellAcBar.AC15BarForSig: specifies the access barring indicator for MO signaling on UEs of AC 15.

The CellAcBar.AcBarringFactorForSig parameter can be set only to P00(0%) when any of the parameters CellAcBar.AC11BarForSig to CellAcBar.AC15BarForSig is set to BOOLEAN_TRUE(true).

ultimedia Telephony Voice

Figure 4-5 shows the access decision procedure for multimedia telephony voice.

Figure 4-5 Access decision procedure for multimedia telephony voice

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

The access barring timer for multimedia telephony voice is started by the UE originating the multimedia telephony voice. The timer length is calculated based on the value of the CellAcBar.AcBarTimeForMVoice parameter. For details, see section 5.3.3.11 "Access barring check" in 3GPP TS 36.331 V11.2.0.
The AC control for multimedia telephony voice is specified by the following parameters:

CellAcBar.AcBarFactorForMVoice: specifies the access probability factor for multimedia telephony voice.
CellAcBar.AcBarTimeForMVoice: specifies the access barring duration for multimedia telephony voice.
CellAcBar.SpecialACBarForMVoice: specifies the access barring indicators for multimedia telephony voice on UEs of ACs 11 to 15.

The access barring indicators for multimedia telephony voice on UEs of ACs 11 to 15 are specified by bits of the CellAcBar.SpecialACBarForMVoice parameter.
The CellAcBar.AcBarFactorForMVoice parameter can be set only to P00(0%) when any option under the CellAcBar.SpecialACBarForMVoice parameter is selected.

ultimedia Telephony Video

Figure 4-5 shows the access decision procedure for multimedia telephony video.

Figure 4-6 Access decision procedure for multimedia telephony video

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

The access barring timer for multimedia telephony video is started by the UE originating the multimedia telephony video. The timer length is calculated based on the value of the CellAcBar.AcBarTimeForMVideo parameter. For details, see section 5.3.3.11 "Access barring check" in 3GPP TS 36.331 V11.2.0.
The AC control for multimedia telephony video is specified by the following parameters:

CellAcBar.AcBarFactorForMVideo: specifies the access probability factor for multimedia telephony video.
CellAcBar.AcBarTimeForMVideo: specifies the access barring duration for multimedia telephony video.
CellAcBar.SpecialACBarForMVideo: specifies the access barring indicators for multimedia telephony video on UEs of ACs 11 to 15.

The access barring indicators for multimedia telephony video on UEs of ACs 11 to 15 are specified by bits of the CellAcBar.SpecialACBarForMVideo parameter.
The CellAcBar.AcBarFactorForMVideo parameter can be set only to P00(0%) when any option under the CellAcBar.SpecialACBarForMVideo parameter is selected.

SFB

The AC control for CSFB is performed based on the following rules:

If AC control parameters from the eNodeB contain CSFB-related parameters, these parameters are used.
If AC control parameters from the eNodeB do not contain CSFB-related parameters, AC control parameters for MO data are used.

Figure 4-7 shows the access decision procedure for CSFB.


Figure 4-7 Access decision procedure for CSFB

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

The access barring timer for CSFB is started by the UE initiating the CSFB. The timer length is calculated based on the value of the CellAcBar.AcBarTimeForCsfb parameter. For details, see section 5.3.3.11 "Access barring check" in 3GPP TS 36.331 V11.2.0.
The AC control for CSFB is specified by the following parameters:

CellAcBar.AcBarFactorForCsfb: specifies the access probability factor for CSFB.


CellAcBar.AcBarTimeForCsfb: specifies the access barring duration for CSFB.
CellAcBar.SpecialACBarForCsfb: specifies the access barring indicators for CSFB on UEs of ACs 11 to 15.

The access barring indicators for CSFB on UEs of ACs 11 to 15 are specified by bits of the CellAcBar.SpecialACBarForCsfb parameter.
The CellAcBar.AcBarFactorForCsfb parameter can be set only to P00(0%) when any option under the CellAcBar.SpecialACBarForCsfb parameter is selected.
If access to an E-UTRAN cell is barred, the UE selects a GERAN or UTRAN cell through the cell reselection procedure to ensure improved user experience. For details, see section 5.6.1.6 "Abnormal cases in the UE" in 3GPP TS 24.301 V10.0.0.

5 Intelligent AC Control

1 Intelligent AC Control Procedure


Intelligent AC control is used when the CellAlgoSwitch.AcBarAlgoSwitch parameter is set to ACBAR_SWITCH_DYNAMIC(dynamic configuration) and the DYNAMIC_FOR_MO(DYNAMIC_FOR_MO) option under the CellAlgoSwitch.AcBarAlgoforDynSwitch parameter is selected.
Intelligent AC control is applied to MO data and MO signaling. If static AC control is configured, static AC control is applied to other access types.
Figure 5-1 shows the procedure for intelligent AC control.

Figure 5-1 Procedure for intelligent AC control

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

The conditions for triggering and canceling intelligent AC control are determined by the following parameters:

CellDynAcBarAlgoPara.MoTriggerCondSatiPeriods
This parameter specifies the number of consecutive cell congestion periods for triggering intelligent AC control.
CellDynAcBarAlgoPara.MoCancelCondSatiPeriods
This parameter specifies the number of consecutive cell congestion relief periods for canceling intelligent AC control.

2 Implementation Principles
Intelligent AC control is a supplement to static AC control. Based on the cell load state, intelligent AC control automatically triggers or cancels AC control on MO data and MO signaling.
After intelligent AC control is enabled, the eNodeB periodically checks the cell state based on the setting of the CellDynAcBarAlgoPara.DynAcBarStatPeriod parameter. The policy of determining cell congestion is specified by the EnodebFlowCtrlParaDynAcBarPolicyMode parameter.

EnodebFlowCtrlPara.DynAcBarPolicyMode being set to FLOWCONTROL(FLOWCONTROL)


If the ratio of the flow control duration to the measurement duration is greater than or equal to the value of the CellDynAcBarAlgoPara.DynAcBarTriggerThd parameter, the eNodeB determines that the cell is congested. For details about flow control, see Flow Control Feature Parameter Description.

NOTE:
For macro eNodeBs, flow control is triggered by a large amount of RRC signaling or RACH signaling. The cells on the same board have the same flow control state because flow control is performed at the board level. If the CellDynAcBarAlgoPara.DynAcBarTriggerThd parameter is set to the same value for
the cells on a board, the congestion states of the cells are the same. It is recommended that the same AC control parameters be configured for cells on the same board.
For micro eNodeBs, flow control is triggered only by a large amount of RACH signaling.

EnodebFlowCtrlPara.DynAcBarPolicyMode being set to CPULOAD(CPULOAD)


The eNodeB calculates the proportion of time during which the CPU usage of the main control board or baseband processing unit for a cell is greater than or equal to the value of the EnodebFlowCtrlPara.CpuLoadThd parameter. If the calculation result is greater than or equal to the value of the
CellDynAcBarAlgoPara.DynAcBarTriggerThd parameter, the eNodeB determines that the cell is congested.

NOTE:
When the EnodebFlowCtrlPara.DynAcBarPolicyMode parameter is set to CPULOAD(CPULOAD), if the EnodebFlowCtrlPara.CpuLoadThd parameter is set to a value less than 80% (for example, 50%), the access of a large number of UEs is barred although the CPU resource is sufficient. In this case, user
experience is affected and the specified busy hour call attempts (BHCA) of the eNodeB may fail to be reached.

If the EnodebFlowCtrlPara.DynAcBarPolicyMode parameter is modified during the measurement period specified by the CellDynAcBarAlgoPara.DynAcBarStatPeriod parameter, the eNodeB determines whether the cell is congested based on the cell states determined using both policies.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

For example, the measurement period is 20s, the eNodeB determines the cell state each second, the flow control policy is used in the first 10s, and the CPU usage policy is used in the second 10s. That is, the first 10 states are determined based on the flow control state, and the second 10 states are determined based
on the CPU usage. Based on the 20 cell states, the eNodeB calculates the proportion of time during which the cell is in the congestion state to determine whether the cell is congested during the measurement period.
The eNodeB calculates the proportion of time during which the cell is in the flow control state or the proportion of time during which the CPU usage of the main control board or baseband processing unit for the cell is greater than or equal to the EnodebFlowCtrlPara.CpuLoadThd parameter value within the measurement
period specified by the CellDynAcBarAlgoPara.DynAcBarStatPeriod parameter. If the calculation result is lower than or equal to the CellDynAcBarAlgoPara.DynAcBarCancelThd parameter value, the eNodeB determines that the cell congestion is relived.

ggering of Intelligent AC Control

According to 5.1 Intelligent AC Control Procedure, after intelligent AC control is enabled, the eNodeB periodically checks whether a cell is congested and counts the number of consecutive periods during which the cell is congested.
If the number of consecutive periods during which the cell is congested reaches the value of the CellDynAcBarAlgoPara.MoTriggerCondSatiPeriods parameter, the eNodeB triggers intelligent AC control. The eNodeB sends AC control parameters through SIB2 messages to dynamically adjust the access probability factor
CellAcBar.AcBarringFactorForSig or CellAcBar.AcBarringFactorForCall.

andling After Intelligent AC Control Is Triggered

If intelligent AC control triggered in the last period is not canceled in the current period, the eNodeB checks whether the cell is congested in the current period.

If the cell is congested, AC control cannot be canceled, and the eNodeB gradually decreases the access probability factor value to expand the access control range. The access barring duration is not adjusted.
If the cell congestion is relieved, the eNodeB further checks the number of consecutive periods during which the cell congestion is relieved.
If the number of consecutive periods during which the cell congestion is relieved is less than the value of the CellDynAcBarAlgoPara.MoCancelCondSatiPeriods parameter, the eNodeB maintains the broadcast access probability factor for MO data or MO signaling.
If the number of consecutive periods during which the cell congestion is relieved reaches the value of the CellDynAcBarAlgoPara.MoCancelCondSatiPeriods parameter, the eNodeB sends SIB2 messages that do not contain MO data or MO signaling access control configurations to UEs to cancel
access control on MO signaling or MO data.

AC control on other access types is not canceled. The value of the CellDynAcBarAlgoPara.DynAcBarCancelThd parameter must be less than the value of the CellDynAcBarAlgoPara.DynAcBarTriggerThd parameter.

3 Access Probability Factor Adjustment


Access probability factors are defined in section 6.3.1 "System information blocks" in 3GPP TS 36.331 V11.2.0. After intelligent AC control is enabled, the access probability factors are selected in descending order until cell congestion is relieved. The AC barring duration is the same as the duration configured in static AC
barring. Figure 5-2 shows the detailed access probability factor adjustment procedure.
Figure 5-2 Detailed access probability factor adjustment procedure

To ensure that some UEs can access the cell, the minimum access probability factor is P05(5%). If cell congestion is not immediately relieved even with an access probability factor of P05(5%), then P05(5%) is maintained until cell congestion is eventually relieved.
If the cell is congested again, the access probability factor is selected in descending order from P95(95%).

6 Dynamic SSAC

1 Dynamic SSAC Procedure


When the CellAlgoSwitch.AcBarAlgoSwitch parameter is set to ACBAR_SWITCH_DYNAMIC(dynamic configuration) and the DYNAMIC_FOR_SSAC(DYNAMIC_FOR_SSAC) option under the CellAlgoSwitch.AcBarAlgoforDynSwitch parameter is selected, dynamic SSAC is used.
Dynamic SSAC is applied to multimedia telephony voice and multimedia telephony video. If static AC control is configured, static AC control is applied to other access types.
Figure 6-1 shows the procedure for dynamic SSAC.

Figure 6-1 Procedure for dynamic SSAC

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

The conditions for triggering and canceling dynamic SSAC are determined by the following parameters:

CellDynAcBarAlgoPara.DisasterReferenceInd
This parameter specifies whether a type of disaster message is referenced for determining whether a cell is in a disaster state. If the eNodeB does not reference any disaster message, the disaster state of the cell does not need to be determined.
CellDynAcBarAlgoPara.DisasterDuration
This parameter specifies the duration that the cell is in the disaster state. The duration starts when the eNodeB determines that the cell is in a disaster state. The cell is out of the disaster state after the duration specified by this parameter ends.
The timer corresponding to this parameter is independent of the CellDynAcBarAlgoPara.DisasterReferenceInd parameter and starts when the eNodeB receives a disaster message for a cell.
CellDynAcBarAlgoPara.SsacTriggerCondSatiPeriods
This parameter specifies the number of consecutive periods, during which a cell is both in a disaster state and in a congestion state, for triggering dynamic SSAC.
CellDynAcBarAlgoPara.SsacCancelCondSatiPeriods
This parameter specifies the number of consecutive periods, during which the cell congestion is relieved or the cell is out of the disaster state, for canceling dynamic SSAC.

2 Implementation Principles
Dynamic SSAC is a supplement to static AC control. Based on the cell load state and disaster state, dynamic SSAC automatically triggers or cancels AC control on multimedia telephony voice and multimedia telephony video.
After dynamic SSAC is enabled, the eNodeB periodically checks the cell congestion state and disaster state based on the setting of the CellDynAcBarAlgoPara.DynAcBarStatPeriod paramter.

The eNodeB determines that a cell is in a disaster state if the eNodeB receives an earthquake and tsunami warning system (ETWS) primary notification (PN) or commercial mobile alert system (CMAS) message for the cell.
The type of message received by the eNodeB is specified by the CellDynAcBarAlgoPara.DisasterReferenceInd parameter. The policy of determining cell congestion is specified by the EnodebFlowCtrlPara.DynAcBarPolicyMode parameter.
EnodebFlowCtrlPara.DynAcBarPolicyMode being set to FLOWCONTROL(FLOWCONTROL)
If the ratio of the flow control duration to the measurement duration is greater than or equal to the value of the CellDynAcBarAlgoPara.DynAcBarTriggerThd parameter, the eNodeB determines that the cell is congested. For details about flow control, see Flow Control Feature Parameter Description.

NOTE:
For macro eNodeBs, flow control is triggered by a large amount of RRC signaling or RACH signaling. The cells on the same board have the same flow control state because flow control is performed at the board level. If the CellDynAcBarAlgoPara.DynAcBarTriggerThd parameter is set to the
same value for the cells on a board, the congestion states of the cells are the same. It is recommended that the same AC control parameters be configured for cells on the same board.
For micro eNodeBs, flow control is triggered only by a large amount of RACH signaling.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

EnodebFlowCtrlPara.DynAcBarPolicyMode being set to CPULOAD(CPULOAD)


The eNodeB calculates the proportion of time during which the CPU usage of the main control board or baseband processing unit for a cell is greater than or equal to the value of the EnodebFlowCtrlPara.CpuLoadThd parameter.

NOTE:
When the EnodebFlowCtrlPara.DynAcBarPolicyMode parameter is set to CPULOAD(CPULOAD), if the EnodebFlowCtrlPara.CpuLoadThd parameter is set to a value less than 80% (for example, 50%), the access of a large number of UEs is barred although the CPU resource is sufficient. In this
case, user experience is affected and the specified busy hour call attempts (BHCA) of the eNodeB may fail to be reached.

In this case, user experience is affected and the specified BHCA of the eNodeB may fail to be reached. If the EnodebFlowCtrlPara.DynAcBarPolicyMode paramter is modified during the measurement period specified by the CellDynAcBarAlgoPara.DynAcBarStatPeriod paramter, the eNodeB determines whether the
cell is congested in the same way as it does in intelligent AC control. For details, see 5.2 Implementation Principles.
After dynamic SSAC is triggered for a cell, the eNodeB determines that the cell is out of the congestion state and disaster state when the following conditions are met:

The eNodeB calculates the proportion of time during which the cell is in the flow control state or the proportion of time during which the CPU usage of the main control board or baseband processing unit for the cell is greater than or equal to the EnodebFlowCtrlPara.CpuLoadThd parameter value within the
measurement period specified by the CellDynAcBarAlgoPara.DynAcBarStatPeriod parameter. If the calculation result is lower than or equal to the CellDynAcBarAlgoPara.DynAcBarCancelThd parameter value, the eNodeB determines that the cell congestion is relived.
The disaster duration is specified by the CellDynAcBarAlgoPara.DisasterDuration parameter. After the duration ends, the cell is out of the disaster state.

ggering of SSAC

According to 6.1 Dynamic SSAC Procedure, after dynamic SSAC is enabled, the eNodeB periodically checks whether a cell is congested and is in a disaster state and counts the number of consecutive periods during which the cell is congested and is in a disaster state.
When the number of consecutive periods during which a cell is congested and is in a disaster state reaches the value of CellDynAcBarAlgoPara.SsacTriggerCondSatiPeriods, the eNodeB triggers dynamic SSAC for the cell. The eNodeB sends AC control parameters through SIB2 messages to dynamically adjust the
access probability factor CellAcBar.AcBarFactorForMVoice or CellAcBar.AcBarFactorForMVideo.

andling After Dynamic SSAC Is Triggered

If dynamic SSAC triggered in the last period is not canceled in the current period, the eNodeB checks whether the cell is congested and is in a disaster state in the current period.

If the cell is congested and is in a disaster state, AC control cannot be canceled, and the eNodeB gradually decreases the access probability factor value for the cell to expand the access control range. The access barring duration is not adjusted.
If the cell is not congested or is not in a disaster state, the eNodeB further checks the number of consecutive periods during which the cell is out of the congestion or disaster state.
If the number of consecutive periods during which the cell is out of the congestion or disaster state is less than the value of the CellDynAcBarAlgoPara.SsacCancelCondSatiPeriods parameter, the eNodeB maintains the broadcast access probability factor for multimedia telephony voice or
multimedia telephony video.
If the number of consecutive periods during which the cell is out of the congestion or disaster state reaches the value of the CellDynAcBarAlgoPara.SsacCancelCondSatiPeriods parameter, the eNodeB sends SIB2 messages that do not contain multimedia telephony voice or multimedia telephony
video access control configurations to UEs to cancel access control on multimedia telephony voice or multimedia telephony video.

AC control on other access types is not canceled. The value of the CellDynAcBarAlgoPara.DynAcBarCancelThd parameter must be less than the value of the CellDynAcBarAlgoPara.DynAcBarTriggerThd parameter.

3 Access Probability Factor Adjustment


After dynamic SSAC is started, the eNodeB adjusts the access probability factors until the cell congestion is relieved or the cell disaster state is ended. The adjustment mechanism is the same as that described in "5.3 Access Probability Factor Adjustment."

7 Related Features

1 Features Related to LOFD-070207 Intelligent Access Class Control


erequisite Features

Intelligent access control depends on the feature LBFD-002009 Broadcast of system information because AC control parameters are broadcast through SIB2 messages.

utually Exclusive Features

None

pacted Features

None

2 Features Related to LOFD-008002 Dynamic Service-specific Access Control


erequisite Features

Dynamic SSAC depends on the feature LBFD-002009 Broadcast of system information because AC control parameters are broadcast through SIB2 messages.
Dynamic SSAC depends on the feature LBFD-002029 Earthquake and Tsunami Warning System (ETWS) when the CellDynAcBarAlgoPara.DisasterReferenceInd parameter is set to ETWS_PN(ETWS_PN) or ETWS_PN_TEST(ETWS_PN_TEST).
Dynamic SSAC depends on the feature LOFD-001092 CMAS Support when the CellDynAcBarAlgoPara.DisasterReferenceInd parameter is set to CMAS(CMAS).

utually Exclusive Features

None

pacted Features

None

8 Network Impact

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

1 LOFD-070207 Intelligent Access Class Control


stem Capacity

When the EnodebFlowCtrlPara.DynAcBarPolicyMode parameter is set to CPULOAD(CPULOAD), if the EnodebFlowCtrlPara.CpuLoadThd parameter is set to a value less than 80% (for example, 50%), the access of a large number of UEs is barred although the CPU resource is sufficient. In this case, user experience
is affected and the specified BHCA of the eNodeB may fail to be reached.

etwork Performance

The highest frequency for access probability factor adjustment is once every 20 seconds during intelligent AC control. This has no influence on network performance.
If the RRC connection setup success rate decreases because of flow control on the main control board or baseband processing units and intelligent AC control is enabled, the access of some UEs is barred and cell congestion will be relieved. The RRC connection setup success rate will also increase. The degree in the
increase depends on the cell congestion status, AC control parameter settings, and the proportion of UEs that support AC control in the network. If UE access is barred, users' access experience is affected.

2 LOFD-008002 Dynamic Service-specific Access Control


stem Capacity

When the EnodebFlowCtrlPara.DynAcBarPolicyMode parameter is set to CPULOAD(CPULOAD), if the EnodebFlowCtrlPara.CpuLoadThd parameter is set to a value less than 80% (for example, 50%), the access of a large number of UEs is barred although the CPU resource is sufficient. In this case, user experience
is affected and the specified BHCA of the eNodeB may fail to be reached.

etwork Performance

The highest frequency for access probability factor adjustment is once every 20 seconds during dynamic SSAC. This has no influence on network performance.
If the RRC connection setup success rate decreases because of flow control on the main control board or baseband processing units and dynamic SSAC is enabled, the access of some UEs is barred and cell congestion will be relieved. The RRC connection setup success rate will also increase. The degree in the increase
depends on the cell congestion status, AC control parameter settings, and the proportion of UEs that support AC control in the network. If UE access is barred, users' access experience is affected.

9 Engineering Guidelines

1 When to Use Access Class Control


Static AC control, intelligent AC control, and dynamic SSAC have an impact on user access experience. That is, if UE access is barred, the UE's perceived access delay increases. AC control should therefore only be enabled when a large number of UEs in a cell will simultaneously access the network, as in the case for
special events such as holidays, concerts, and sporting events or for disasters such as earthquakes and tsunamis.

This guideline is particularly important for static AC control.


If intelligent AC control and dynamic SSAC are enabled in a congested cell, new UEs may not be able to access the network and user experience may be affected. If this impact is acceptable, intelligent AC control and dynamic SSAC can be always enabled to relieve cell congestion, even for unpredictable
congestion.
Dynamic SSAC can also be enabled in scenarios where a large number of UEs will simultaneously initiate multimedia telephony voice or multimedia telephony video in addition to scenarios such as earthquakes, tsunamis, and hurricanes.

2 Required Information
The information to be collected is as follows:

Whether UEs support ACs defined in 3GPP Release 8 and later


Operators can obtain the distribution of various types of UEs and the capability of these UEs to support AC control from evolved packet core (EPC) information.
Whether heavy traffic causes signaling shock to a network when a large number of UEs in a cell simultaneously access the network

3 Planning

9.3.1 RF Planning
N/A

9.3.2 Network Planning


N/A

9.3.3 Hardware Planning


N/A

4 Deployment

9.4.1 Requirements
her NEs

Emergency calls, MO data, and MO signaling require that UEs support the AC control mechanism defined in 3GPP Release 8.
Multimedia telephony voice and multimedia telephony video require that UEs support the AC control mechanism defined in 3GPP Release 9.
CSFB requires that UEs support the AC control mechanism defined in 3GPP Release 10.

cense

The operator has purchased and activated the license for intelligent AC control listed in the following table.

Feature ID Feature Name Model License Control Item NE Sales Unit

LOFD-070207 Intelligent Access Class Control LT1S00IACC00 Intelligent Access Class Control (FDD) eNodeB Per cell

The operator has purchased and activated the license for dynamic SSAC listed in the following table.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

Feature ID Feature Name Model License Control Item NE Sales Unit

LOFD-008002 Dynamic Service-specific Access Control LT1S0DSSAC00 Dynamic Service-specific Access Control (FDD) eNodeB Per Cell

9.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:

Network plan (negotiation not required): parameter values planned and set by the operator
Network plan (negotiation required): parameter values planned by the operator and negotiated with the evolved packet core (EPC) or peer transmission equipment
User-defined: parameter values set by users

equired Data

The following table describes the parameters that must be set in the CellAlgoSwitch MO to configure the AC control switch.

Parameter Name Parameter ID Data Source Setting Notes

Local cell ID CellAlgoSwitch.LocalCellId Network plan This parameter specifies the local ID of a cell. It uniquely identifies a cell within the coverage of an eNodeB.
(negotiation not required)

AcBar algorithms switch CellAlgoSwitch.AcBarAlgoSwitch Network plan This parameter specifies an AC control algorithm. If this parameter is set to ACBAR_SWITCH_DYNAMIC(dynamic configuration), dynamic
(negotiation not required) AC control is enabled. In this situation, the CellAlgoSwitch.AcBarAlgoforDynSwitch parameter determines whether to enable intelligent AC
control on MO signaling and MO data or SSAC on multimedia telephony voice and multimedia telephony video. If this parameter is set to
ACBAR_SWITCH_STATIC(static configuration), static AC control is enabled. In this situation, the access probability factors and average
access barring duration are set in the CellAcBar MO. When this parameter is set to ACBAR_SWITCH_DISABLE(Disable), AC barring is
disabled.

Ac Bar Algorithm Switch for Dynamic CellAlgoSwitch.AcBarAlgoforDynSwitch Network plan This parameter determines whether to enable intelligent AC control on MO signaling and MO data or SSAC on multimedia telephony voice
(negotiation not required) and multimedia telephony video. This parameter is valid only when CellAlgoSwitch.AcBarAlgoSwitch is set to
ACBAR_SWITCH_DYNAMIC(dynamic configuration).

The following table describes the parameters that must be set in the CellAcBar MO to configure AC control information.

Parameter Name Parameter ID Data Source Setting Notes

Local cell ID CellAcBar.LocalCellId Network plan (negotiation not required) This parameter specifies the local ID of a cell. It uniquely identifies a cell within the coverage of an eNodeB.

AC barring information configure indicator CellAcBar.AcBarringInfoCfgInd Network plan (negotiation not required) This parameter specifies whether to configure AC control information.

Emergency call barring state CellAcBar.AcBarringForEmergency Network plan (negotiation not required) This parameter specifies whether UEs of AC 10 can initiate access for emergency calls.
If this parameter is set to BOOLEAN_TRUE(True), UEs of AC 0 to AC 9 or those without IMSIs cannot initiate access for
emergency calls. If this parameter is set to BOOLEAN_FALSE(False), such UEs can initiate access for emergency calls.
UEs of AC N (ranging from 11 to 15) cannot initiate access for emergency calls if both AC N and AC 10 are barred. Otherwise, such
UEs call initiate access for emergency calls.

AC barring for mobile data configure indicator CellAcBar.AcBarringForMoDataCfgInd Network plan (negotiation not required) This parameter specifies whether to configure AC control information for MO data.

Access probability factor for originating call CellAcBar.AcBarringFactorForCall Network plan (negotiation not required) This parameter specifies an access probability factor for MO data. If the random number generated by a UE is less than this access
probability factor, the UE can initiate access for MO data. Otherwise, the UE cannot initiate access for MO data.
This parameter must be set to P00(0%) if any of AC 11 to AC 15 is barred for MO data.

Mean access barring time for originating call CellAcBar.AcBarTimeForCall Network plan (negotiation not required) This parameter specifies the average access barring duration for MO data.

AC11 barring state for originating call CellAcBar.AC11BarforCall Network plan (negotiation not required) This parameter specifies whether UEs of AC 11 can initiate access for MO data.

AC12 barring state for originating call CellAcBar.AC12BarforCall Network plan (negotiation not required) This parameter specifies whether UEs of AC 12 can initiate access for MO data.

AC13 barring state for originating call CellAcBar.AC13BarforCall Network plan (negotiation not required) This parameter specifies whether UEs of AC 13 can initiate access for MO data.

AC14 barring state for originating call CellAcBar.AC14BarforCall Network plan (negotiation not required) This parameter specifies whether UEs of AC 14 can initiate access for MO data.

AC15 barring state for originating call CellAcBar.AC15BarforCall Network plan (negotiation not required) This parameter specifies whether UEs of AC 15 can initiate access for MO data.

AC barring for mobile signal configure indicator CellAcBar.AcBarringForMoSigCfgInd Network plan (negotiation not required) This parameter specifies whether to configure AC control information for MO signaling.

Access probability factor for signaling CellAcBar.AcBarringFactorForSig Network plan (negotiation not required) This parameter specifies an access probability factor for MO signaling. If the random number generated by a UE is less than this
access probability factor, the UE can initiate access for MO signaling.
Otherwise, the UE cannot initiate access for MO signaling. This parameter must be set to P00(0%) if any of AC 11 to AC 15 is
barred for MO signaling.

Mean access barring time for signaling CellAcBar.AcBarTimeForSig Network plan (negotiation not required) This parameter specifies the average access barring duration for MO signaling.

AC11 barring state for signaling CellAcBar.AC11BarForSig Network plan (negotiation not required) This parameter specifies whether UEs of AC 11 can initiate access for MO signaling.

AC12 barring state for signaling CellAcBar.AC12BarForSig Network plan (negotiation not required) This parameter specifies whether UEs of AC 12 can initiate access for MO signaling.

AC13 barring state for signaling CellAcBar.AC13BarForSig Network plan (negotiation not required) This parameter specifies whether UEs of AC 13 can initiate access for MO signaling.

AC14 barring state for signaling CellAcBar.AC14BarForSig Network plan (negotiation not required) This parameter specifies whether UEs of AC 14 can initiate access for MO signaling.

AC15 barring state for signaling CellAcBar.AC15BarForSig Network plan (negotiation not required) This parameter specifies whether UEs of AC 15 can initiate access for MO signaling.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

AC barring for MMTEL voice configure indicator CellAcBar.AcBarForMVoiceCfgInd Network plan (negotiation not required) This parameter specifies whether to configure AC control information for multimedia telephony voice.

Access probability factor for MMTEL voice CellAcBar.AcBarFactorForMVoice Network plan (negotiation not required) This parameter specifies an access probability factor for multimedia telephony voice. If the random number generated by a UE is
less than this access probability factor, the UE can initiate access for multimedia telephony voice. Otherwise, the UE cannot initiate
access for multimedia telephony voice.
This parameter must be set to P00(0%) if any of AC 11 to AC 15 is barred for multimedia telephony voice.

Mean access barring time for MMTEL voice CellAcBar.AcBarTimeForMVoice Network plan (negotiation not required) This parameter specifies the average access barring duration for multimedia telephony voice.

AC 11-15 barring state for MMTEL voice CellAcBar.SpecialACBarForMVoice Network plan (negotiation not required) This parameter specifies whether UEs of AC 11 to AC 15 can initiate access for multimedia telephony voice.

AC barring for MMTEL video configure indicator CellAcBar.AcBarForMVideoCfgInd Network plan (negotiation not required) This parameter specifies whether to configure AC control information for multimedia telephony video.

Access probability factor for MMTEL video CellAcBar.AcBarFactorForMVideo Network plan (negotiation not required) This parameter specifies an access probability factor for multimedia telephony video. If the random number generated by a UE is
less than this access probability factor, the UE can initiate access for multimedia telephony video. Otherwise, the UE cannot initiate
access for multimedia telephony video.
This parameter must be set to P00(0%) if any of AC 11 to AC 15 is barred for multimedia telephony video.

Mean access barring time for MMTEL video CellAcBar.AcBarTimeForMVideo Network plan (negotiation not required) This parameter specifies the average access barring duration for multimedia telephony video.

AC 11-15 barring state for MMTEL video CellAcBar.SpecialACBarForMVideo Network plan (negotiation not required) This parameter specifies whether UEs of AC 11 to AC 15 can initiate access for multimedia telephony video.

AC barring for CSFB configure indicator CellAcBar.AcBarForCsfbCfgInd Network plan (negotiation not required) This parameter specifies whether to configure AC control information for CSFB.

Access probability factor for CSFB CellAcBar.AcBarFactorForCsfb Network plan (negotiation not required) This parameter specifies an access probability factor for CSFB. If the random number generated by a UE is less than this access
probability factor, the UE can initiate access for CSFB. Otherwise, the UE cannot initiate access for CSFB.
This parameter must be set to P00(0%) if any of AC 11 to AC 15 is barred for CSFB.

Mean access barring time for CSFB CellAcBar.AcBarTimeForCsfb Network plan (negotiation not required) This parameter specifies the average access barring duration for CSFB.

AC 11-15 barring state for CSFB CellAcBar.SpecialACBarForCsfb Network plan (negotiation not required) This parameter specifies whether UEs of AC 11 to AC 15 can initiate access for CSFB.

enario-specific Data

The following table describes the parameters that must be set in the CellDynAcBarAlgoPara MO to configure intelligent AC control information.

Parameter Name Parameter ID Data Source Setting Notes

Local cell ID CellDynAcBarAlgoPara.LocalCellId Network plan (negotiation not This parameter specifies the local ID of a cell. It uniquely identifies a cell within the coverage of an eNodeB.
required)

Dynamic AC Barring Control Statistic Period CellDynAcBarAlgoPara.DynAcBarStatPeriod Network plan (negotiation not This parameter specifies a period for measuring the proportion of cell congestion duration.
required)

Dynamic AC Barring Control Trigger Threshold CellDynAcBarAlgoPara.DynAcBarTriggerThd Network plan (negotiation not This parameter specifies a threshold for triggering intelligent AC control. This threshold is denoted by a proportion of cell congestion
required) duration. If the proportion of cell congestion duration in a statistic period (CellDynAcBarAlgoPara.DynAcBarStatPeriod) is greater than
or equal to this threshold, the condition for triggering intelligent AC control is met.

Dynamic AC Barring Control Cancel Threshold CellDynAcBarAlgoPara.DynAcBarCancelThd Network plan (negotiation not This parameter specifies a threshold for canceling intelligent AC control. This threshold is denoted by a proportion of cell congestion
required) duration. If the proportion of cell congestion duration in a statistic period (CellDynAcBarAlgoPara.DynAcBarStatPeriod) is less than or
equal to this threshold, the condition for canceling intelligent AC control is met.

MO Trigger Condition Satisfied Periods CellDynAcBarAlgoPara.MoTriggerCondSatiPeriods Network plan (negotiation not This parameter specifies the number of consecutive periods during which the condition for triggering intelligent AC control on MO data or
required) MO signaling is met. Intelligent AC control on MO data or MO signaling is triggered only when the number of consecutive periods during
which the condition for triggering intelligent AC control on MO data or MO signaling is met reaches the value of this parameter.

MO Cancel Condition Satisfied Periods CellDynAcBarAlgoPara.MoCancelCondSatiPeriods Network plan (negotiation not This parameter specifies the number of consecutive periods during which the condition for canceling intelligent AC control on MO data or
required) MO signaling is met. Intelligent AC control on MO data or MO signaling is canceled only when the number of consecutive periods during
which the condition for canceling intelligent AC control on MO data or MO signaling is met reaches the value of this parameter.

The following table describes the parameters that must be set in the CellDynAcBarAlgoPara MO to configure dynamic SSAC information.

Parameter Name Parameter ID Data Source Setting Notes

Local cell ID CellDynAcBarAlgoPara.LocalCellId Network plan (negotiation not This parameter specifies the local ID of a cell. It uniquely identifies a cell within the coverage of an eNodeB.
required)

Dynamic AC Barring Control Statistic Period CellDynAcBarAlgoPara.DynAcBarStatPeriod Network plan (negotiation not This parameter specifies a period for measuring the proportion of cell congestion duration.
required)

Dynamic AC Barring Control Trigger Threshold CellDynAcBarAlgoPara.DynAcBarTriggerThd Network plan (negotiation not This parameter specifies a threshold for triggering intelligent AC control. This threshold is denoted by a proportion of cell congestion
required) duration. If the proportion of cell congestion duration in a statistic period (CellDynAcBarAlgoPara.DynAcBarStatPeriod) is greater than
or equal to this threshold, the condition for triggering intelligent AC control is met.

Dynamic AC Barring Control Cancel Threshold CellDynAcBarAlgoPara.DynAcBarCancelThd Network plan (negotiation not This parameter specifies a threshold for canceling dynamic SSAC. This threshold is denoted by a proportion of cell congestion duration. If
required) the proportion of cell congestion duration in a statistic period (CellDynAcBarAlgoPara.DynAcBarStatPeriod) is less than or equal to this
threshold, the condition for canceling dynamic SSAC is met.

Disaster Reference Indication CellDynAcBarAlgoPara.DisasterReferenceInd Network plan (negotiation not This parameter specifies the disaster reference indications used for determining whether a cell is in the disaster state. This parameter
required) applies only to dynamic SSAC.

Disaster Duration CellDynAcBarAlgoPara.DisasterDuration Network plan (negotiation not This parameter specifies the duration that the cell is in a disaster state. The duration starts after the cell enters the disaster state. The cell
required) is out of the disaster state after the duration specified by this parameter ends. This parameter applies only to dynamic SSAC.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

Ssac Trigger Condition Satisfied Periods CellDynAcBarAlgoPara.SsacTriggerCondSatiPeriods Network plan (negotiation not This parameter specifies the number of consecutive periods during which the condition for triggering dynamic SSAC is met. Dynamic
required) SSAC can be triggered only when the number of consecutive periods during which the condition for triggering dynamic SSAC is met
reaches the value of this parameter.

Ssac Cancel Condition Satisfied Periods CellDynAcBarAlgoPara.SsacCancelCondSatiPeriods Network plan (negotiation not This parameter specifies the number of consecutive periods during which the condition for canceling dynamic SSAC is met. Dynamic
required) SSAC can be canceled only when the number of consecutive periods during which the condition for canceling dynamic SSAC is met
reaches the value of this parameter.

The following table describes the parameters that must be set in the EnodebFlowCtrlPara MO to configure the congestion determination policy for intelligent AC control and dynamic SSAC.

Parameter Name Parameter ID Data Source Setting Notes

Dynamic AC Barring Policy Mode EnodebFlowCtrlPara.DynAcBarPolicyMode Network plan (negotiation not required) This parameter specifies the policy of determining cell congestion for intelligent AC control and dynamic SSAC.
When this paramter is set to FLOWCONTROL(FLOWCONTROL), the eNodeB determines that a cell is congested when the cell is
under flow control.
When this paramter is set to CPULOAD(CPULOAD), the eNodeB determines cell congestion based on the configured CPU load
threshold. If the CPU load of a main control board or baseband processing unit serving the cells is greater than or equal to the
configured CPU load threshold, the cells are congested. The CPU load threshold is specified by the
EnodebFlowCtrlPara.CpuLoadThd parameter.

CPU Load Threshold EnodebFlowCtrlPara.CpuLoadThd Network plan (negotiation not required) This parameter specifies the CPU load threshold for determining cell congestion. This parameter takes effect only when
EnodebFlowCtrlPara.DynAcBarPolicyMode is set to CPULOAD(CPULOAD). If the CPU load of a main control board or baseband processing
unit serving the cells is greater than or equal to this parameter value, the cells are congested. If the CPU load is less than this parameter value,
the cells are not congested.

9.4.3 Initial Configuration


sing the CME to Perform Batch Configuration for Newly Deployed eNodeBs

Enter the values of the parameters listed in Table 9-1, Table 9-2 and Table 9-3 in a summary data file, which also contains other data for the new eNodeBs to be deployed.
Then, import the summary data file 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:
The MOs in Table 9-1, Table 9-2 and Table 9-3 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.
Some MOs in Table 9-1, Table 9-2 and Table 9-3 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.

Static AC Control

Table 9-1 Static AC control parameters

MO Sheet in the Summary Data File Parameter Group Remarks

CellAlgoSwitch CellAlgoSwitch AcBarAlgoSwitch User-defined Pattern sheet

CellAcBar CellAcBar LocalCellId, AcBarringInfoCfgInd, AcBarringForEmergency, AcBarringForMoDataCfgInd, AcBarringFactorForCall, User-defined List sheet
AcBarTimeForCall, AC11BarforCall, AC12BarforCall, AC13BarforCall, AC14BarforCall, AC15BarforCall,
AcBarringForMoSigCfgInd, AcBarringFactorForSig, AcBarTimeForSig, AC11BarForSig, AC12BarForSig,
AC13BarForSig, AC14BarForSig, AC15BarForSig, AcBarForMVoiceCfgInd, AcBarFactorForMVoice,
AcBarTimeForMVoice, SpecialACBarForMVoice, AcBarForMVideoCfgInd, AcBarFactorForMVideo,
AcBarTimeForMVideo, SpecialACBarForMVideo, AcBarForCsfbCfgInd, AcBarFactorForCsfb, AcBarTimeForCsfb,
SpecialACBarForCsfb

Intelligent AC Control
In addition to the preceding parameters in the CellAcBar MO, intelligent AC control requires the parameters in the following table.

Table 9-2 Intelligent AC control parameters

MO Sheet in the Summary Data File Parameter Group Remarks

CellAlgoSwitch CellAlgoSwitch AcBarAlgoSwitch, AcBarAlgoforDynSwitch User-defined Pattern sheet

CellDynAcBarAlgoPara CellDynAcBarAlgoPara LocalCellId, DynAcBarStatPeriod, DynAcBarTriggerThd, DynAcBarCancelThd, MoTriggerCondSatiPeriods, User-defined List sheet
MoCancelCondSatiPeriods

EnodebFlowCtrlPara EnodebFlowCtrlPara DynAcBarPolicyMode, CpuLoadThd User-defined List sheet

Dynamic SSAC
In addition to the preceding parameters in the CellAcBar MO, dynamic SSAC requires the parameters in the following table.

Table 9-3 Dynamic SSAC parameters

MO Sheet in the Summary Data File Parameter Group Remarks

CellAlgoSwitch CellAlgoSwitch AcBarAlgoSwitch, AcBarAlgoforDynSwitch User-defined Pattern sheet

CellDynAcBarAlgoPara CellDynAcBarAlgoPara LocalCellId, DynAcBarStatPeriod, DynAcBarTriggerThd, DynAcBarCancelThd, SsacTriggerCondSatiPeriods, User-defined List sheet
SsacCancelCondSatiPeriods, DisasterReferenceInd, DisasterDuration

EnodebFlowCtrlPara EnodebFlowCtrlPara DynAcBarPolicyMode, CpuLoadThd User-defined List sheet

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

sing the CME to Perform Batch Configuration for Existing eNodeBs

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.

1. The procedure is as follows: 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.
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.
3. In the summary data file, set the parameters in the MOs according to the setting notes provided in section "Data Preparation" and close the file.
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.
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.

sing the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB. The procedure is as follows:

1. In the planned data area, click Base Station in the upper left corner of the configuration window.
2. In area 1 shown in Figure 9-1, select the eNodeB to which the MOs belong.
Figure 9-1 MO search and configuration window

3. On the Search tab page in area 2, enter an MO name, for example, CELL.
4. In area 3, double-click the MO in the Object Name column.
5. All parameters in this MO are displayed in area 4.
6. Set the parameters in area 4 or 5. 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.

sing MML Commands

Static AC Control
To configure static AC control, perform the following steps:

1. Run the MOD CELLACBAR command to set AC control parameters. The access type can be emergency calls, MO data, MO signaling, multimedia telephony voice, multimedia telephony video, or CSFB.
2. Run the MOD CELLALGOSWITCH command to set the AC control mode to static AC control.

Intelligent AC Control
To configure intelligent AC control, perform the following steps:

1. Run the MOD CELLDYNACBARALGOPARA command to set intelligent AC control parameters, including the statistic period, triggering threshold, canceling threshold, number of periods in which the triggering condition is met, and number of periods in which the canceling condition is met.
2. Run the MOD CELLACBAR command to set other AC control parameters. The access type can be emergency calls, MO data, MO signaling, multimedia telephony voice, multimedia telephony video, or CSFB.
3. Run the MOD CELLALGOSWITCH command to set the AC control mode to intelligent AC control.
4. Run the MOD ENODEBFLOWCTRLPARA command to set the policy of determining whether a cell is congested to flow control.

Dynamic SSAC
To configure dynamic SSAC, perform the following steps:

1. Run the MOD CELLDYNACBARALGOPARA command to set dynamic SSAC parameters, including the statistic period, triggering condition, canceling threshold, number of periods in which the triggering condition is met, number of periods in which the canceling condition is met, disaster reference indication,
and disaster duration.
2. Run the MOD CELLACBAR command to set other AC control parameters. The access type can be emergency calls, MO data, MO signaling, multimedia telephony voice, multimedia telephony video, or CSFB.
3. Run the MOD CELLALGOSWITCH command to set the AC control mode to dynamic SSAC.
4. Run the MOD ENODEBFLOWCTRLPARA command to set the policy of determining whether a cell is congested to flow control.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

ML Command Examples

Static AC Control
MOD CELLACBAR: LocalCellId=0, AcBarringInfoCfgInd=CFG, AcBarringForMoDataCfgInd=CFG, AcBarringFactorForCall=P95, AcBarTimeForCall= ACCESS_BARRING_TIME_S4;
MOD CELLALGOSWITCH: LocalCellId=0, AcBarAlgoSwitch= ACBAR_SWITCH_STATIC;
Intelligent AC Control
MOD CELLDYNACBARALGOPARA: LocalCellId=0, DynAcBarTriggerThd =100, DynAcBarCancelThd =80, DynAcBarStatPeriod=20, MoTriggerCondSatiPeriods=2, MoCancelCondSatiPeriods=1;
MOD CELLACBAR: LocalCellId=0, AcBarringInfoCfgInd=CFG, AcBarringForMoDataCfgInd=CFG, AcBarringFactorForCall=P95, AcBarTimeForCall= ACCESS_BARRING_TIME_S4;
MOD CELLALGOSWITCH: LocalCellId=0, AcBarAlgoSwitch= ACBAR_SWITCH_DYNAMIC, AcBarAlgoforDynSwitch= DYNAMIC_FOR_MO-1;
MOD ENODEBFLOWCTRLPARA: DynAcBarPolicyMode=FLOWCONTROL;
Dynamic SSAC
MOD CELLDYNACBARALGOPARA: LocalCellId=0, DynAcBarTriggerThd =100, DynAcBarCancelThd =80, DynAcBarStatPeriod=20, SsacTriggerCondSatiPeriods=2, SsacCancelCondSatiPeriods=1, DisasterReferenceInd=ETWS_PN-1, DisasterDuration=60;
MOD CELLACBAR: LocalCellId=0, AcBarringInfoCfgInd=CFG, AcBarForMVoiceCfgInd=CFG, AcBarFactorForMVoice=P95, AcBarTimeForMVoice= ACCESS_BARRING_TIME_S4;
MOD CELLALGOSWITCH: LocalCellId=0, AcBarAlgoSwitch= ACBAR_SWITCH_DYNAMIC, AcBarAlgoforDynSwitch= DYNAMIC_FOR_SSAC-1;
MOD ENODEBFLOWCTRLPARA: DynAcBarPolicyMode=FLOWCONTROL;

9.4.4 Activation Observation


atic AC Control

If Uu tracing results show that delivered SIB2 contains AC control parameters, static AC control has been activated. The activation observation procedure is as follows:

1. On the U2000 client, choose Monitor > Signaling Trace > Signaling Trace Management.
2. In the navigation tree of the Signaling Trace Management window, choose Trace Type > LTE > Application Layer > Uu Interface Trace, and double-click Uu Interface Trace.
3. In the Uu Interface Trace dialog box, configure the Uu interface tracing task and click Finish to start the task in the current cell.
4. On the task list of the Signaling Trace Management window, double-click the Uu Interface Trace task. A monitoring window for Uu interface tracing is displayed.
5. Set AC control parameters in the CellAcBar MO, for example, for MO signaling. Then, check the monitoring window for SIB2 in RRC_SYS_INFO. If SIB2 contains the AC control parameters, as shown in Figure 9-2, static AC control has been activated.

Figure 9-2 Uu tracing result (SIB2)

elligent AC Control

If the value of any of the following counters is not zero, intelligent AC control has been activated:

L.Dyn.ACBar.Trigger.Num: indicates the number of times intelligent AC control is triggered.


L.Dyn.ACBar.Cancel.Num: indicates the number of times intelligent AC control is canceled.

NOTE:
If the AC control switch is adjusted after intelligent AC control is triggered and before it is cancelled, the values of the preceding counters will be slightly different from those in scenarios without switch adjustment. Here is an example for switch adjustment: ACBAR_SWITCH_DYNAMIC(dynamic configuration) is changed
to ACBAR_SWITCH_STATIC(static configuration) or ACBAR_SWITCH_DISABLE(Disable).

ynamic SSAC

If the value of any of the following counters is not zero, dynamic SSAC has been activated:

L.SSAC.Dyn.ACBar.Trigger.Num: indicates the number of times dynamic SSAC is triggered.


L.SSAC.Dyn.ACBar.Cancel.Num: indicates the number of times dynamic SSAC is canceled.

NOTE:
If the AC control switch is adjusted after dynamic SSAC is triggered and before it is cancelled, the values of the preceding counters will be slightly different from those in scenarios without switch adjustment. Here is an example for switch adjustment: ACBAR_SWITCH_DYNAMIC(dynamic configuration) is changed to
ACBAR_SWITCH_STATIC(static configuration) or ACBAR_SWITCH_DISABLE(Disable).

9.4.5 Reconfiguration

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

Run the MOD CELLALGOSWITCH command to switch between static AC control, intelligent AC control, and dynamic SSAC.

9.4.6 Deactivation
sing 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 Using the CME to
Perform Batch Configuration for Existing eNodeBs. In the procedure, modify parameters according to Table 9-4.

Table 9-4 Static AC Control, intelligent AC control, and dynamic SSAC parameters

MO Sheet in the Summary Data File Parameter Group Setting Notes

CellAlgoSwitch CellAlgoSwitch AcBarAlgoSwitch ACBAR_SWITCH_DISABLE(Disable)

sing the CME to Perform Single Configuration

On the CME, set parameters according to Table 9-4. For detailed instructions, see Using the CME to Perform Single Configuration described for feature activation.

sing MML Commands

Run the MOD CELLALGOSWITCH command to deactivate static AC control, intelligent AC control, or dynamic SSAC.

ML Command Examples

MOD CELLALGOSWITCH: LocalCellId=0, AcBarAlgoSwitch= ACBAR_SWITCH_DISABLE;

5 Performance Monitoring
elligent AC Control

The performance monitoring methods for intelligent AC control are as follows:

Monitor the L.Dyn.ACBar.Trigger.Num and L.Dyn.ACBar.Cancel.Num counters for MO data and MO signaling. If the values of these counters are always zero, intelligent AC control has not been triggered. In this case, adjust the triggering threshold.
If intelligent AC control has been triggered, monitor the L.RRC.ConnReq.Msg.disc.FlowCtrl and L.RRC.SetupFail.Rej.FlowCtrl counters. If the number of RRC connection request discards or rejections due to flow control decreases, intelligent AC control has taken effect.

The decreased number of RRC connection request discards or rejections depends on the proportion of UEs that support AC control, the access probability factor, and the access barring duration. If a cell is seriously congested and the proportion of UEs that support AC control is high, intelligent AC control can achieve high
gains.

ynamic SSAC

The performance monitoring methods for dynamic SSAC are as follows:

Monitor the L.SSAC.Dyn.ACBar.Trigger.Num and L.SSAC.Dyn.ACBar.Cancel.Num counters for multimedia telephony voice and multimedia telephony video. If the values of these counters are always zero, dynamic SSAC has not been triggered. In this case, adjust the triggering threshold.
If dynamic SSAC has been triggered, monitor the L.RRC.ConnReq.Msg.disc.FlowCtrl and L.RRC.SetupFail.Rej.FlowCtrl counters. If the number of RRC connection request discards or rejections due to flow control decreases, dynamic SSAC has taken effect.

The decreased number of RRC connection request discards or rejections depends on the proportion of UEs that support SSAC, the access probability factor, and the access barring duration. If a cell is seriously congested because a large number of UEs simultaneously initiate access for multimedia telephony voice and
multimedia telephony video and the proportion of UEs that support SSAC is high, dynamic SSAC can achieve high gains.

6 Parameter Optimization
atic AC Control

When a large number of UEs in a cell simultaneously access the network, the cell may be congested (for example, the CPU usage exceeds the flow control threshold). In this case, determine the ACs to be controlled based on the following counters:

L.RRC.ConnReq.Att.MoData
L.RRC.ConnReq.Att.MoSig
L.RRC.ConnReq.Att.Emc
L.CSFB.PrepAtt

Then, set AC control parameters for the identified ACs. These parameters will be broadcast to UEs.
If the congestion is not relieved, adjust access probability factors such as CellAcBar.AcBarringFactorForCall to expand the AC control scope, or adjust access barring durations such as CellAcBar.AcBarTimeForCall to control the access frequencies.

elligent AC Control

Monitor the L.Dyn.ACBar.Trigger.Num and L.Dyn.ACBar.Cancel.Num counters for MO data and MO signaling. If the values of these counters are always zero, intelligent AC control has not been triggered. In this case, adjust the CellDynAcBarAlgoPara.DynAcBarTriggerThd,
CellDynAcBarAlgoPara.DynAcBarCancelThd, CellDynAcBarAlgoPara.MoTriggerCondSatiPeriods, and CellDynAcBarAlgoPara.MoCancelCondSatiPeriods parameters.

ynamic SSAC

Monitor the L.SSAC.Dyn.ACBar.Trigger.Num and L.SSAC.Dyn.ACBar.Cancel.Num counters for multimedia telephony voice and multimedia telephony video. If the values of these counters are always zero, dynamic SSAC has not been triggered. In this case, adjust the CellDynAcBarAlgoPara.DynAcBarTriggerThd,
CellDynAcBarAlgoPara.DynAcBarCancelThd, CellDynAcBarAlgoPara.SsacTriggerCondSatiPeriods, and CellDynAcBarAlgoPara.SsacCancelCondSatiPeriods parameters.

7 Troubleshooting
elligent AC Control

Fault Description
The values of L.Dyn.ACBar.Trigger.Num and L.Dyn.ACBar.Cancel.Num are always zero. This indicates that intelligent AC control has not been triggered.
The CPU usage (VS.BBUBoard.CPULoad.Mean) of the main control board or a baseband processing unit exceeds the flow control threshold (for example, 80%) for a long period (for example, 15 minutes). In addition, the values of L.RRC.ConnReq.Msg.disc.FlowCtrl and L.RRC.SetupFail.Rej.FlowCtrl show that RRC
connection setup requests are discarded or rejected due to flow control. In this case, it is deduced that a large number of random access requests or RRC connection setup requests lead to long-term flow control and serious cell congestion.
Fault Handling
The fault handling procedure is as follows:

1. Run the LST CELLALGOSWITCH command to check whether intelligent AC control is enabled. If it is disabled, turn on the intelligent AC control switch.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

2. Run the LST CELLDYNACBARALGOPARA command to check the settings of CellDynAcBarAlgoPara.DynAcBarStatPeriod, CellDynAcBarAlgoPara.DynAcBarTriggerThd, CellDynAcBarAlgoPara.DynAcBarCancelThd, CellDynAcBarAlgoPara.MoTriggerCondSatiPeriods, and
CellDynAcBarAlgoPara.MoCancelCondSatiPeriods. That is, check whether the settings meet the operator's requirements, for example, whether the trigger threshold is greater than the proportion of time during which the eNodeB is under flow control. If the settings are not appropriate, run the MOD
CELLDYNACBARALGOPARA command to adjust these parameters.
3. If intelligent AC control is still not triggered, run the MOD CELLDYNACBARALGOPARA command to set the preceding parameters to smaller values.
4. If intelligent AC control is still not triggered, contact Huawei technical support.

ynamic SSAC

Fault Description
The values of L.SSAC.Dyn.ACBar.Trigger.Num and L.SSAC.Dyn.ACBar.Cancel.Num are always zero. This indicates that dynamic SSAC has not been triggered.
The CPU usage (VS.BBUBoard.CPULoad.Mean) of the main control board or a baseband processing unit exceeds the flow control threshold (for example, 80%) for a long period (for example, 15 minutes). In addition, the values of L.RRC.ConnReq.Msg.disc.FlowCtrl and L.RRC.SetupFail.Rej.FlowCtrl show that RRC
connection setup requests are discarded or rejected due to flow control. In this case, it is deduced that a large number of random access requests or RRC connection setup requests lead to long-term flow control and serious cell congestion.
Fault Handling
The fault handling procedure is as follows:

1. Run the LST CELLALGOSWITCH command to check whether dynamic SSAC is enabled. If it is disabled, turn on the dynamic SSAC switch.
2. Run the LST CELLDYNACBARALGOPARA command to check whether the settings of CellDynAcBarAlgoPara.DisasterReferenceInd and CellDynAcBarAlgoPara.DisasterDuration meet the operator's requirements. If CellDynAcBarAlgoPara.DisasterReferenceInd is set, check whether the eNodeB has
received a disaster message from the MME for the current cell.
3. Run the LST CELLDYNACBARALGOPARA command to check the settings of CellDynAcBarAlgoPara.DynAcBarStatPeriod, CellDynAcBarAlgoPara.DynAcBarTriggerThd, CellDynAcBarAlgoPara.DynAcBarCancelThd, CellDynAcBarAlgoPara.SsacTriggerCondSatiPeriods, and
CellDynAcBarAlgoPara.SsacCancelCondSatiPeriods. That is, check whether the settings meet the operator's requirements, for example, whether the triggering threshold is greater than the proportion of time during which the eNodeB is under flow control or the number of periods in which the triggering
condition is met is large.
4. If dynamic SSAC is still not triggered, run the MOD CELLDYNACBARALGOPARA command to set the preceding parameters to smaller values.
5. If intelligent AC control is still not triggered, contact Huawei technical support.

10 Parameters

Table 10-1 Parameters

MO Parameter ID MML Command Feature ID Feature Name Description

CellAlgoSwitch AcBarAlgoforDynSwitch MOD CELLALGOSWITCH LOFD-008002 / TDLOFD- Dynamic Service Specific Meaning:
LST CELLALGOSWITCH 080202 Access Control Indicates whether to enable intelligent access barring algorithms. This parameter controls whether to enable intelligent access barring on
LOFD-070207 / TDLOFD- Intelligent Access Class mobile-originated (MO) signaling, MO data, service specific access control (SSAC) for multimedia telephony (MMTEL) voice services, or
081222 Control SSAC for MMTEL video services. This parameter takes effect only when the AcBarAlgoSwitch parameter in the CellAlgoSwitch MO is set
to ACBAR_SWITCH_DYNAMIC.
DYNAMIC_FOR_MO: Indicates whether to enable intelligent access barring on UEs running MO signaling or MO data.
If this switch is on, intelligent access barring applies to UEs running MO signaling or MO data.
If this switch is off, intelligent access barring does not apply to UEs running MO signaling or MO data.
DYNAMIC_FOR_SSAC: Indicates whether to enable intelligent access barring on UEs running MMTEL voices services or MMTEL video
services.
If this switch is on, intelligent access barring applies to UEs running MMTEL voices services or MMTEL video services.
If this switch is off, intelligent access barring does not apply to UEs running MMTEL voices services or MMTEL video services.
GUI Value Range: DYNAMIC_FOR_MO(DYNAMIC_FOR_MO), DYNAMIC_FOR_SSAC(DYNAMIC_FOR_SSAC)
Unit: None
Actual Value Range: DYNAMIC_FOR_MO, DYNAMIC_FOR_SSAC
Default Value: DYNAMIC_FOR_MO:On, DYNAMIC_FOR_SSAC:Off

CellDynAcBarAlgoPara DisasterReferenceInd MOD LOFD-008002 / TDLOFD- Dynamic Service Specific Meaning:


CELLDYNACBARALGOPARA 008002 Access Control Indicates the disaster reference indications used for determining whether a cell is in the disaster state. If all switches included in this
LST parameter are off, the disaster state of the cell does not need to be determined.
CELLDYNACBARALGOPARA ETWS_PN: Indicates whether Primary notifications (PNs) in the earthquake and tsunami warning system (ETWS) is used in the disaster
state determination. The PNs for ETWS do not include PNs used for ETWS tests.
If this switch is on, PNs in ETWS are used in the disaster state determination.
If this switch is off, PNs in ETWS are not used in the disaster state determination.
ETWS_PN_TEST: Indicates whether PNs for ETWS tests are used in the disaster state determination.
If this switch is on, PNs in ETWS tests are used in the disaster state determination.
If this switch is off, PNs in ETWS tests are not used in the disaster state determination.
CMAS: Indicates whether commercial mobile alert system (CMAS) warning notifications are used in the disaster state determination.
If this switch is on, CMAS warning notifications are used in the disaster state determination.
If this switch is off, CMAS warning notifications are not used in the disaster state determination.
GUI Value Range: ETWS_PN(ETWS PN), ETWS_PN_TEST(ETWS PN FOR TEST), CMAS(CMAS)
Unit: None
Actual Value Range: ETWS_PN, ETWS_PN_TEST, CMAS
Default Value: ETWS_PN:On, ETWS_PN_TEST:Off, CMAS:Off

CellDynAcBarAlgoPara DisasterDuration MOD LOFD-008002 / TDLOFD- Dynamic Service Specific Meaning: Indicates the duration that the cell is in the disaster state. The cell is out of the disaster state after the duration specified by this
CELLDYNACBARALGOPARA 008002 Access Control parameter ends.
LST GUI Value Range: 1~10080

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

CELLDYNACBARALGOPARA Unit: min


Actual Value Range: 1~10080
Default Value: 60

CellDynAcBarAlgoPara SsacTriggerCondSatiPeriods MOD LOFD-008002 / TDLOFD- Dynamic Service Specific Meaning: Indicates the number of periods for triggering intelligent access barring on specific services. If related triggering conditions are
CELLDYNACBARALGOPARA 008002 Access Control met in consecutive periods specified by this parameter, intelligent access barring on specific services is triggered.
LST GUI Value Range: 1~1000
CELLDYNACBARALGOPARA Unit: None
Actual Value Range: 1~1000
Default Value: 2

CellDynAcBarAlgoPara SsacCancelCondSatiPeriods MOD LOFD-008002 / TDLOFD- Dynamic Service Specific Meaning: Indicates the number of periods for canceling intelligent access barring on specific services. If related cancellation conditions
CELLDYNACBARALGOPARA 008002 Access Control are met in consecutive periods specified by this parameter, intelligent access barring on specific services is canceled.
LST GUI Value Range: 1~1000
CELLDYNACBARALGOPARA Unit: None
Actual Value Range: 1~1000
Default Value: 1

CellDynAcBarAlgoPara MoTriggerCondSatiPeriods MOD LOFD-070207 / TDLOFD- Intelligent Access Class Meaning: Indicates the number of consecutive periods for triggering intelligent access class control on mobile-originated (MO) calls or
CELLDYNACBARALGOPARA 070207 Control signaling if related triggering conditions are met.
LST GUI Value Range: 1~1000
CELLDYNACBARALGOPARA Unit: None
Actual Value Range: 1~1000
Default Value: 2

CellDynAcBarAlgoPara MoCancelCondSatiPeriods MOD LOFD-070207 / TDLOFD- Intelligent Access Class Meaning: Indicates the number of consecutive periods for canceling intelligent access class control on mobile-originated (MO) calls or
CELLDYNACBARALGOPARA 070207 Control signaling if related cancellation conditions are met.
LST GUI Value Range: 1~1000
CELLDYNACBARALGOPARA Unit: None
Actual Value Range: 1~1000
Default Value: 1

eNodeBFlowCtrlPara DynAcBarPolicyMode MOD LOFD-070207 / TDLOFD- Intelligent Access Class Meaning:


ENODEBFLOWCTRLPARA 070207 Control Indicates the policy for determining whether cells are congested in intelligent access control or service-based dynamic access control.
LST LOFD-008002 / TDLOFD- Dynamic Service Specific If this parameter is set to FLOWCONTROL(FLOWCONTROL), cell congestion is determined based on the flow control state.
ENODEBFLOWCTRLPARA 008002 Access Control(SSAC) If this parameter is set to CPULOAD(CPULOAD), cell congestion is determined based on the configured CPU load threshold. If the CPU
load of a main control board or baseband processing unit serving the cells is greater than or equal to the configured CPU load threshold,
the cells are congested. The CPU load threshold is specified by the CpuLoadThd parameter.
GUI Value Range: FLOWCONTROL(FLOWCONTROL), CPULOAD(CPULOAD)
Unit: None
Actual Value Range: FLOWCONTROL, CPULOAD
Default Value: FLOWCONTROL(FLOWCONTROL)

eNodeBFlowCtrlPara CpuLoadThd MOD LOFD-070207 / TDLOFD- Intelligent Access Class Meaning: Indicates the CPU load threshold of a board. If the CPU load of a main control board or baseband processing unit serving the
ENODEBFLOWCTRLPARA 070207 Control cells is greater than or equal to this parameter value, the cells are congested. If the CPU load is less than this parameter value, the cells
LST LOFD-008002 / TDLOFD- Dynamic Service Specific are not congested. This parameter takes effect only when the DynAcBarPolicyMode parameter is set to CPULOAD(CPULOAD).
ENODEBFLOWCTRLPARA 008002 Access Control(SSAC) GUI Value Range: 50~100
Unit: %
Actual Value Range: 50~100
Default Value: 80

CellAcBar AcBarringInfoCfgInd MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning: Indicates whether to configure the access barring information.
LST CELLACBAR 002009 information GUI Value Range: NOT_CFG(Not configure), CFG(Configure)
Unit: None
Actual Value Range: NOT_CFG, CFG
Default Value: NOT_CFG(Not configure)

CellAcBar AcBarringForEmergency MOD CELLACBAR LBFD-002028 / TDLBFD- Emergency Call Meaning:


LST CELLACBAR 002028 Indicates the emergency call barring status of access class 10, indicating whether UEs of access class 10 can initiate emergency calls.
If this parameter is set to BOOLEAN_TRUE, UEs of access classes 0 to 9 or those without IMSIs cannot initiate emergency calls. If this
parameter is set to BOOLEAN_FALSE, UEs of access classes 0 to 9 and those without IMSIs can initiate emergency calls.
A UE in access classes 11 to 15 cannot initiate emergency calls only when its access class and access class 10 are both barred. If its
access class or access class 10 is not barred, emergency calls initiated by the UE are granted access.
GUI Value Range: BOOLEAN_FALSE(False), BOOLEAN_TRUE(True)
Unit: None
Actual Value Range: BOOLEAN_FALSE, BOOLEAN_TRUE
Default Value: BOOLEAN_FALSE(False)

CellAcBar AcBarringForMoDataCfgInd MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning: Indicates whether to configure the access barring information for mobile-originated calls.
LST CELLACBAR 002009 information GUI Value Range: NOT_CFG(Not configure), CFG(Configure)
Unit: None
Actual Value Range: NOT_CFG, CFG
Default Value: NOT_CFG(Not configure)

CellAcBar AcBarringForMoSigCfgInd MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning: Indicates whether to configure the access barring information for signaling.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

LST CELLACBAR 002009 information GUI Value Range: NOT_CFG(Not configure), CFG(Configure)
Unit: None
Actual Value Range: NOT_CFG, CFG
Default Value: NOT_CFG(Not configure)

CellAcBar AcBarForMVoiceCfgInd MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning: Indicates whether to configure the access barring information for multimedia telephony (MMTEL) voice services.
LST CELLACBAR 002009 information GUI Value Range: NOT_CFG(Not configure), CFG(Configure)
Unit: None
Actual Value Range: NOT_CFG, CFG
Default Value: NOT_CFG(Not configure)

CellAcBar AcBarForMVideoCfgInd MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning: Indicates whether to configure the access barring information for multimedia telephony (MMTEL) video services.
LST CELLACBAR 002009 information GUI Value Range: NOT_CFG(Not configure), CFG(Configure)
Unit: None
Actual Value Range: NOT_CFG, CFG
Default Value: NOT_CFG(Not configure)

CellAcBar AcBarForCsfbCfgInd MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning: Indicates whether to configure the access barring information for CS fallback (CSFB) services.
LST CELLACBAR 002009 information GUI Value Range: NOT_CFG(Not configure), CFG(Configure)
Unit: None
Actual Value Range: NOT_CFG, CFG
Default Value: NOT_CFG(Not configure)

CellAlgoSwitch AcBarAlgoSwitch MOD CELLALGOSWITCH LBFD-002009 / TDLBFD- Broadcast of system Meaning: Indicates the switch for the access barring algorithm. If this parameter is set to ACBAR_SWITCH_DYNAMIC, intelligent access
LST CELLALGOSWITCH 002009 information barring is enabled. In this situation, the access probability factors for mobile-originated data and mobile-originated signaling are
LOFD-0700206 / TLOFD- Dynamic AC Barring dynamically adjusted based on the cell load. If this parameter is set to ACBAR_SWITCH_STATIC, static access barring is enabled. In
0700206 this situation, the access probability factors and average access barring durations are configured in the access barring information. If this
parameter is set to ACBAR_SWITCH_DISABLE, access barring is disabled.
GUI Value Range: ACBAR_SWITCH_DYNAMIC(dynamic configuration), ACBAR_SWITCH_STATIC(static configuration),
ACBAR_SWITCH_DISABLE(Disable)
Unit: None
Actual Value Range: ACBAR_SWITCH_DYNAMIC, ACBAR_SWITCH_STATIC, ACBAR_SWITCH_DISABLE
Default Value: ACBAR_SWITCH_STATIC(static configuration)

CellAcBar AcBarTimeForCall MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning: Indicates the average access barring duration for mobile-originated calls.
LST CELLACBAR 002009 information GUI Value Range: ACCESS_BARRING_TIME_S4(4s), ACCESS_BARRING_TIME_S8(8s), ACCESS_BARRING_TIME_S16(16s),
ACCESS_BARRING_TIME_S32(32s), ACCESS_BARRING_TIME_S64(64s), ACCESS_BARRING_TIME_S128(128s),
ACCESS_BARRING_TIME_S256(256s), ACCESS_BARRING_TIME_S512(512s)
Unit: s
Actual Value Range: ACCESS_BARRING_TIME_S4, ACCESS_BARRING_TIME_S8, ACCESS_BARRING_TIME_S16,
ACCESS_BARRING_TIME_S32, ACCESS_BARRING_TIME_S64, ACCESS_BARRING_TIME_S128, ACCESS_BARRING_TIME_S256,
ACCESS_BARRING_TIME_S512
Default Value: ACCESS_BARRING_TIME_S4(4s)

CellAcBar AcBarringFactorForCall MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning: Indicates the access probability factor for mobile-originated calls. A mobile-originated call is granted access if the random
LST CELLACBAR 002009 information number generated by the UE is less than this access probability factor; otherwise, the access request is rejected. According to 3GPP TS
36.331, if any of the parameters AC11BarforCall, AC12BarforCall, AC13BarforCall, AC14BarforCall, and AC15BarforCall is set to
BOOLEAN_TRUE, the eNodeB sends UEs P00 as the access probability factor for mobile-originated calls in the system information block
type 2 (SIB2), regardless of the actual setting of the AcBarringFactorForCall parameter.
GUI Value Range: P00(0%), P05(5%), P10(10%), P15(15%), P20(20%), P25(25%), P30(30%), P40(40%), P50(50%), P60(60%),
P70(70%), P75(75%), P80(80%), P85(85%), P90(90%), P95(95%)
Unit: %
Actual Value Range: P00, P05, P10, P15, P20, P25, P30, P40, P50, P60, P70, P75, P80, P85, P90, P95
Default Value: P95(95%)

CellAcBar AC11BarforCall MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning:


LST CELLACBAR 002009 information Indicates the mobile-originated call barring status of access class 11, indicating whether UEs of access class 11 can initiate mobile-
originated calls.
If this parameter is set to BOOLEAN_TRUE, UEs of access class 11 cannot initiate mobile-originated calls. If this parameter is set to
BOOLEAN_FALSE, UEs of access class 11 can initiate mobile-originated calls.
GUI Value Range: BOOLEAN_FALSE(False), BOOLEAN_TRUE(True)
Unit: None
Actual Value Range: BOOLEAN_FALSE, BOOLEAN_TRUE
Default Value: BOOLEAN_FALSE(False)

CellAcBar AC12BarforCall MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning:


LST CELLACBAR 002009 information Indicates the mobile-originated call barring status of access class 12, indicating whether UEs of access class 12 can initiate mobile-
originated calls.
If this parameter is set to BOOLEAN_TRUE, UEs of access class 12 cannot initiate mobile-originated calls. If this parameter is set to
BOOLEAN_FALSE, UEs of access class 12 can initiate mobile-originated calls.
GUI Value Range: BOOLEAN_FALSE(False), BOOLEAN_TRUE(True)
Unit: None
Actual Value Range: BOOLEAN_FALSE, BOOLEAN_TRUE
Default Value: BOOLEAN_FALSE(False)

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

CellAcBar AC13BarforCall MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning:


LST CELLACBAR 002009 information Indicates the mobile-originated call barring status of access class 13, indicating whether UEs of access class 13 can initiate mobile-
originated calls.
If this parameter is set to BOOLEAN_TRUE, UEs of access class 13 cannot initiate mobile-originated calls. If this parameter is set to
BOOLEAN_FALSE, UEs of access class 13 can initiate mobile-originated calls.
GUI Value Range: BOOLEAN_FALSE(False), BOOLEAN_TRUE(True)
Unit: None
Actual Value Range: BOOLEAN_FALSE, BOOLEAN_TRUE
Default Value: BOOLEAN_FALSE(False)

CellAcBar AC14BarforCall MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning:


LST CELLACBAR 002009 information Indicates the mobile-originated call barring status of access class 14, indicating whether UEs of access class 14 can initiate mobile-
originated calls.
If this parameter is set to BOOLEAN_TRUE, UEs of access class 14 cannot initiate mobile-originated calls. If this parameter is set to
BOOLEAN_FALSE, UEs of access class 14 can initiate mobile-originated calls.
GUI Value Range: BOOLEAN_FALSE(False), BOOLEAN_TRUE(True)
Unit: None
Actual Value Range: BOOLEAN_FALSE, BOOLEAN_TRUE
Default Value: BOOLEAN_FALSE(False)

CellAcBar AC15BarforCall MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning:


LST CELLACBAR 002009 information Indicates the mobile-originated call barring status of access class 15, indicating whether UEs of access class 15 can initiate mobile-
originated calls.
If this parameter is set to BOOLEAN_TRUE, UEs of access class 15 cannot initiate mobile-originated calls. If this parameter is set to
BOOLEAN_FALSE, UEs of access class 15 can initiate mobile-originated calls.
GUI Value Range: BOOLEAN_FALSE(False), BOOLEAN_TRUE(True)
Unit: None
Actual Value Range: BOOLEAN_FALSE, BOOLEAN_TRUE
Default Value: BOOLEAN_FALSE(False)

CellAcBar AcBarTimeForSig MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning: Indicates the average access barring duration for signaling.
LST CELLACBAR 002009 information GUI Value Range: ACCESS_BARRING_TIME_S4(4s), ACCESS_BARRING_TIME_S8(8s), ACCESS_BARRING_TIME_S16(16s),
ACCESS_BARRING_TIME_S32(32s), ACCESS_BARRING_TIME_S64(64s), ACCESS_BARRING_TIME_S128(128s),
ACCESS_BARRING_TIME_S256(256s), ACCESS_BARRING_TIME_S512(512s)
Unit: s
Actual Value Range: ACCESS_BARRING_TIME_S4, ACCESS_BARRING_TIME_S8, ACCESS_BARRING_TIME_S16,
ACCESS_BARRING_TIME_S32, ACCESS_BARRING_TIME_S64, ACCESS_BARRING_TIME_S128, ACCESS_BARRING_TIME_S256,
ACCESS_BARRING_TIME_S512
Default Value: ACCESS_BARRING_TIME_S4(4s)

CellAcBar AcBarringFactorForSig MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning: Indicates the access probability factor for signaling. Signaling from a UE is granted access if the random number generated by
LST CELLACBAR 002009 information the UE is less than this access probability factor; otherwise, the access request is rejected. According to 3GPP TS 36.331, if any of the
parameters AC11BarForSig, AC12BarForSig, AC13BarForSig, AC14BarForSig, and AC15BarForSig is set to BOOLEAN_TRUE, the
eNodeB sends UEs P00 as the access probability factor for signaling in the system information block type 2 (SIB2), regardless of the
actual setting of the AcBarringFactorForSig parameter.
GUI Value Range: P00(0%), P05(5%), P10(10%), P15(15%), P20(20%), P25(25%), P30(30%), P40(40%), P50(50%), P60(60%),
P70(70%), P75(75%), P80(80%), P85(85%), P90(90%), P95(95%)
Unit: %
Actual Value Range: P00, P05, P10, P15, P20, P25, P30, P40, P50, P60, P70, P75, P80, P85, P90, P95
Default Value: P95(95%)

CellAcBar AC11BarForSig MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning:


LST CELLACBAR 002009 information Indicates the signaling barring status of access class 11, indicating whether UEs of access class 11 can initiate signaling access.
If this parameter is set to BOOLEAN_TRUE, UEs of access class 11 cannot initiate signaling access. If this parameter is set to
BOOLEAN_FALSE, UEs of access class 11 can initiate signaling access.
GUI Value Range: BOOLEAN_FALSE(False), BOOLEAN_TRUE(True)
Unit: None
Actual Value Range: BOOLEAN_FALSE, BOOLEAN_TRUE
Default Value: BOOLEAN_FALSE(False)

CellAcBar AC12BarForSig MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning:


LST CELLACBAR 002009 information Indicates the signaling barring status of access class 12, indicating whether UEs of access class 12 can initiate signaling access.
If this parameter is set to BOOLEAN_TRUE, UEs of access class 12 cannot initiate signaling access. If this parameter is set to
BOOLEAN_FALSE, UEs of access class 12 can initiate signaling access.
GUI Value Range: BOOLEAN_FALSE(False), BOOLEAN_TRUE(True)
Unit: None
Actual Value Range: BOOLEAN_FALSE, BOOLEAN_TRUE
Default Value: BOOLEAN_FALSE(False)

CellAcBar AC13BarForSig MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning:


LST CELLACBAR 002009 information Indicates the signaling barring status of access class 13, indicating whether UEs of access class 13 can initiate signaling access.
If this parameter is set to BOOLEAN_TRUE, UEs of access class 13 cannot initiate signaling access. If this parameter is set to
BOOLEAN_FALSE, UEs of access class 13 can initiate signaling access.
GUI Value Range: BOOLEAN_FALSE(False), BOOLEAN_TRUE(True)

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

Unit: None
Actual Value Range: BOOLEAN_FALSE, BOOLEAN_TRUE
Default Value: BOOLEAN_FALSE(False)

CellAcBar AC14BarForSig MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning:


LST CELLACBAR 002009 information Indicates the signaling barring status of access class 14, indicating whether UEs of access class 14 can initiate signaling access.
If this parameter is set to BOOLEAN_TRUE, UEs of access class 14 cannot initiate signaling access. If this parameter is set to
BOOLEAN_FALSE, UEs of access class 14 can initiate signaling access.
GUI Value Range: BOOLEAN_FALSE(False), BOOLEAN_TRUE(True)
Unit: None
Actual Value Range: BOOLEAN_FALSE, BOOLEAN_TRUE
Default Value: BOOLEAN_FALSE(False)

CellAcBar AC15BarForSig MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning:


LST CELLACBAR 002009 information Indicates the signaling barring status of access class 15, indicating whether UEs of access class 15 can initiate signaling access.
If this parameter is set to BOOLEAN_TRUE, UEs of access class 15 cannot initiate signaling access. If this parameter is set to
BOOLEAN_FALSE, UEs of access class 15 can initiate signaling access.
GUI Value Range: BOOLEAN_FALSE(False), BOOLEAN_TRUE(True)
Unit: None
Actual Value Range: BOOLEAN_FALSE, BOOLEAN_TRUE
Default Value: BOOLEAN_FALSE(False)

CellAcBar AcBarTimeForMVoice MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning: Indicates the average access barring time of multimedia telephony (MMTEL) voice services.
LST CELLACBAR 002009 information GUI Value Range: ACCESS_BARRING_TIME_S4(4s), ACCESS_BARRING_TIME_S8(8s), ACCESS_BARRING_TIME_S16(16s),
ACCESS_BARRING_TIME_S32(32s), ACCESS_BARRING_TIME_S64(64s), ACCESS_BARRING_TIME_S128(128s),
ACCESS_BARRING_TIME_S256(256s), ACCESS_BARRING_TIME_S512(512s)
Unit: s
Actual Value Range: ACCESS_BARRING_TIME_S4, ACCESS_BARRING_TIME_S8, ACCESS_BARRING_TIME_S16,
ACCESS_BARRING_TIME_S32, ACCESS_BARRING_TIME_S64, ACCESS_BARRING_TIME_S128, ACCESS_BARRING_TIME_S256,
ACCESS_BARRING_TIME_S512
Default Value: ACCESS_BARRING_TIME_S4(4s)

CellAcBar AcBarFactorForMVoice MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning: Indicates the access probability factor for multimedia telephony (MMTEL) voice services. An MMTEL voice service is granted
LST CELLACBAR 002009 information access if the random number generated by the UE is less than this access probability factor; otherwise, the access request is barred.
GUI Value Range: P00(0%), P05(5%), P10(10%), P15(15%), P20(20%), P25(25%), P30(30%), P40(40%), P50(50%), P60(60%),
P70(70%), P75(75%), P80(80%), P85(85%), P90(90%), P95(95%)
Unit: %
Actual Value Range: P00, P05, P10, P15, P20, P25, P30, P40, P50, P60, P70, P75, P80, P85, P90, P95
Default Value: P95(95%)

CellAcBar SpecialACBarForMVoice MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning:


LST CELLACBAR 002009 information Indicates whether multimedia telephony (MMTEL) voice services initiated by UEs of AC 11 to AC 15 are granted access.
AC11BARSTATE: If this option is selected, the MMTEL voice services initiated by UEs of AC 11 in idle mode are barred.
AC12BARSTATE: If this option is selected, the MMTEL voice services initiated by UEs of AC 12 in idle mode are barred.
AC13BARSTATE: If this option is selected, the MMTEL voice services initiated by UEs of AC 13 in idle mode are barred.
AC14BARSTATE: If this option is selected, the MMTEL voice services initiated by UEs of AC 14 in idle mode are barred.
AC15BARSTATE: If this option is selected, the MMTEL voice services initiated by UEs of AC 15 in idle mode are barred.
GUI Value Range: AC11BARSTATE(AC11BARSTATE), AC12BARSTATE(AC12BARSTATE), AC13BARSTATE(AC13BARSTATE),
AC14BARSTATE(AC14BARSTATE), AC15BARSTATE(AC15BARSTATE)
Unit: None
Actual Value Range: AC11BARSTATE, AC12BARSTATE, AC13BARSTATE, AC14BARSTATE, AC15BARSTATE
Default Value: AC11BARSTATE:Permit, AC12BARSTATE:Permit, AC13BARSTATE:Permit, AC14BARSTATE:Permit,
AC15BARSTATE:Permit

CellAcBar AcBarTimeForMVideo MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning: Indicates the average access barring time of multimedia telephony (MMTEL) video services.
LST CELLACBAR 002009 information GUI Value Range: ACCESS_BARRING_TIME_S4(4s), ACCESS_BARRING_TIME_S8(8s), ACCESS_BARRING_TIME_S16(16s),
ACCESS_BARRING_TIME_S32(32s), ACCESS_BARRING_TIME_S64(64s), ACCESS_BARRING_TIME_S128(128s),
ACCESS_BARRING_TIME_S256(256s), ACCESS_BARRING_TIME_S512(512s)
Unit: s
Actual Value Range: ACCESS_BARRING_TIME_S4, ACCESS_BARRING_TIME_S8, ACCESS_BARRING_TIME_S16,
ACCESS_BARRING_TIME_S32, ACCESS_BARRING_TIME_S64, ACCESS_BARRING_TIME_S128, ACCESS_BARRING_TIME_S256,
ACCESS_BARRING_TIME_S512
Default Value: ACCESS_BARRING_TIME_S4(4s)

CellAcBar AcBarFactorForMVideo MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning: Indicates the access probability factor for multimedia telephony (MMTEL) video services. An MMTEL video service is granted
LST CELLACBAR 002009 information access if the random number generated by the UE is less than this access probability factor; otherwise, the access request is barred.
GUI Value Range: P00(0%), P05(5%), P10(10%), P15(15%), P20(20%), P25(25%), P30(30%), P40(40%), P50(50%), P60(60%),
P70(70%), P75(75%), P80(80%), P85(85%), P90(90%), P95(95%)
Unit: %
Actual Value Range: P00, P05, P10, P15, P20, P25, P30, P40, P50, P60, P70, P75, P80, P85, P90, P95
Default Value: P95(95%)

CellAcBar SpecialACBarForMVideo MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning:


LST CELLACBAR 002009 information Indicates whether multimedia telephony (MMTEL) video services initiated by UEs of AC 11 to AC 15 are granted access.
AC11BARSTATE: If this option is selected, the MMTEL video services initiated by UEs of AC 11 in idle mode are barred.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

AC12BARSTATE: If this option is selected, the MMTEL video services initiated by UEs of AC 12 in idle mode are barred.
AC13BARSTATE: If this option is selected, the MMTEL video services initiated by UEs of AC 13 in idle mode are barred.
AC14BARSTATE: If this option is selected, the MMTEL video services initiated by UEs of AC 14 in idle mode are barred.
AC15BARSTATE: If this option is selected, the MMTEL video services initiated by UEs of AC 15 in idle mode are barred.
GUI Value Range: AC11BARSTATE(AC11BARSTATE), AC12BARSTATE(AC12BARSTATE), AC13BARSTATE(AC13BARSTATE),
AC14BARSTATE(AC14BARSTATE), AC15BARSTATE(AC15BARSTATE)
Unit: None
Actual Value Range: AC11BARSTATE, AC12BARSTATE, AC13BARSTATE, AC14BARSTATE, AC15BARSTATE
Default Value: AC11BARSTATE:Permit, AC12BARSTATE:Permit, AC13BARSTATE:Permit, AC14BARSTATE:Permit,
AC15BARSTATE:Permit

CellAcBar AcBarTimeForCsfb MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning: Indicates the average access barring time of CS fallback (CSFB) services.
LST CELLACBAR 002009 information GUI Value Range: ACCESS_BARRING_TIME_S4(4s), ACCESS_BARRING_TIME_S8(8s), ACCESS_BARRING_TIME_S16(16s),
ACCESS_BARRING_TIME_S32(32s), ACCESS_BARRING_TIME_S64(64s), ACCESS_BARRING_TIME_S128(128s),
ACCESS_BARRING_TIME_S256(256s), ACCESS_BARRING_TIME_S512(512s)
Unit: s
Actual Value Range: ACCESS_BARRING_TIME_S4, ACCESS_BARRING_TIME_S8, ACCESS_BARRING_TIME_S16,
ACCESS_BARRING_TIME_S32, ACCESS_BARRING_TIME_S64, ACCESS_BARRING_TIME_S128, ACCESS_BARRING_TIME_S256,
ACCESS_BARRING_TIME_S512
Default Value: ACCESS_BARRING_TIME_S4(4s)

CellAcBar AcBarFactorForCsfb MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning: Indicates the access probability factor for CS fallback (CSFB) services. If the random number generated by a UE is less than
LST CELLACBAR 002009 information the parameter value, the eNodeB accepts the CSFB service access request; otherwise, the eNodeB rejects the access request.
GUI Value Range: P00(0%), P05(5%), P10(10%), P15(15%), P20(20%), P25(25%), P30(30%), P40(40%), P50(50%), P60(60%),
P70(70%), P75(75%), P80(80%), P85(85%), P90(90%), P95(95%)
Unit: %
Actual Value Range: P00, P05, P10, P15, P20, P25, P30, P40, P50, P60, P70, P75, P80, P85, P90, P95
Default Value: P95(95%)

CellAcBar SpecialACBarForCsfb MOD CELLACBAR LBFD-002009 / TDLBFD- Broadcast of system Meaning:


LST CELLACBAR 002009 information Indicates whether CS fallback (CSFB) services initiated by UEs of AC 11 to AC 15 are granted access.
AC11BARSTATE: If this option is selected, the CSFB services initiated by UEs of AC 11 in idle mode are barred.
AC12BARSTATE: If this option is selected, the CSFB services initiated by UEs of AC 12 in idle mode are barred.
AC13BARSTATE: If this option is selected, the CSFB services initiated by UEs of AC 13 in idle mode are barred.
AC14BARSTATE: If this option is selected, the CSFB services initiated by UEs of AC 14 in idle mode are barred.
AC15BARSTATE: If this option is selected, the CSFB services initiated by UEs of AC 15 in idle mode are barred.
GUI Value Range: AC11BARSTATE(AC11BARSTATE), AC12BARSTATE(AC12BARSTATE), AC13BARSTATE(AC13BARSTATE),
AC14BARSTATE(AC14BARSTATE), AC15BARSTATE(AC15BARSTATE)
Unit: None
Actual Value Range: AC11BARSTATE, AC12BARSTATE, AC13BARSTATE, AC14BARSTATE, AC15BARSTATE
Default Value: AC11BARSTATE:Permit, AC12BARSTATE:Permit, AC13BARSTATE:Permit, AC14BARSTATE:Permit,
AC15BARSTATE:Permit

CellDynAcBarAlgoPara DynAcBarStatPeriod MOD LOFD-070207 / TDLOFD- Intelligent Access Class Meaning: Indicates the statistic period of dynamic access class (AC) barring in a cell, during which the proportion of time that the cell is in
CELLDYNACBARALGOPARA 070207 Control the congestion state is exported.
LST GUI Value Range: 10~60
CELLDYNACBARALGOPARA Unit: s
Actual Value Range: 10~60
Default Value: 20

CellDynAcBarAlgoPara DynAcBarTriggerThd MOD LOFD-070207 / TDLOFD- Intelligent Access Class Meaning: Indicates the threshold for triggering dynamic access class (AC) barring in the cell. This threshold specifies the proportion of
CELLDYNACBARALGOPARA 070207 Control time that the cell is in the congestion state. If the proportion of time that the cell is in the congestion state is greater than or equal to this
LST parameter value within a statistic period (specified by the DynAcBarStatPeriod parameter), the conditions for triggering dynamic AC
CELLDYNACBARALGOPARA barring are met.
GUI Value Range: 0~100
Unit: %
Actual Value Range: 0~100
Default Value: 100

CellDynAcBarAlgoPara DynAcBarCancelThd MOD LOFD-070207 / TDLOFD- Intelligent Access Class Meaning: Indicates the threshold for canceling dynamic access class (AC) barring in the cell. This threshold specifies the proportion of
CELLDYNACBARALGOPARA 070207 Control time that the cell is in the congestion state. If the proportion of time that the cell is in the congestion state is less than or equal to this
LST parameter value within a statistic period (specified by the DynAcBarStatPeriod parameter), the conditions for canceling dynamic AC
CELLDYNACBARALGOPARA barring are met.
GUI Value Range: 0~100
Unit: %
Actual Value Range: 0~100
Default Value: 80

CellAlgoSwitch LocalCellId DSP None None Meaning: Indicates the local ID of the cell. It uniquely identifies a cell within a BS.
CELLULCAMCCLUSTER GUI Value Range: 0~255
LST CELLALGOSWITCH Unit: None
MOD CELLALGOSWITCH Actual Value Range: 0~255
Default Value: None

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

CellAcBar LocalCellId LST CELLACBAR None None Meaning: Indicates the local ID of the cell. It uniquely identifies a cell within a BS.
MOD CELLACBAR GUI Value Range: 0~255
Unit: None
Actual Value Range: 0~255
Default Value: None

CellDynAcBarAlgoPara LocalCellId LST None None Meaning: Indicates the local cell ID. It uniquely identifies a cell within an eNodeB.
CELLDYNACBARALGOPARA GUI Value Range: 0~255
MOD Unit: None
CELLDYNACBARALGOPARA Actual Value Range: 0~255
Default Value: None

11 Counters

Table 11-1 Counters

Counter ID Counter Name Counter Description Feature ID Feature Name

1526728217 L.RRC.ConnReq.Att.Emc Number of RRC connection setup attempts with a Multi-mode: None RRC Connection Management
cause value of emergency GSM: None RRC Connection Management
UMTS: None
LTE: LBFD-002007
TDLBFD-002007

1526728220 L.RRC.ConnReq.Att.MoSig Number of RRC connection setup attempts with a Multi-mode: None RRC Connection Management
cause value of mo-Signalling GSM: None RRC Connection Management
UMTS: None
LTE: LBFD-002007
TDLBFD-002007

1526728221 L.RRC.ConnReq.Att.MoData Number of RRC connection setup attempts with a Multi-mode: None RRC Connection Management
cause value of mo-Data GSM: None RRC Connection Management
UMTS: None
LTE: LBFD-002007
TDLBFD-002007

1526728321 L.CSFB.PrepAtt Number of CSFB indicators received by the eNodeB Multi-mode: None CS Fallback to UTRAN
GSM: None CS Fallback to UTRAN
UMTS: None CS Fallback to GERAN
LTE: LOFD-001033 CS Fallback to GERAN
TDLOFD-001033 CS Fallback to CDMA2000 1xRTT
LOFD-001034 CS Fallback to CDMA2000 1xRTT
TDLOFD-001034
LOFD-001035
TDLOFD-001035

1526728489 L.RRC.ConnReq.Msg.disc.FlowCtrl Number of times the RRC Connection Request Multi-mode: None RRC Connection Management
message is discarded due to flow control GSM: None RRC Connection Management
UMTS: None
LTE: LBFD-002007
TDLBFD-002007

1526728490 L.RRC.SetupFail.Rej.FlowCtrl Number of times the eNodeB sends an RRC Multi-mode: None RRC Connection Management
Connection Reject message to the UE due to flow GSM: None RRC Connection Management
control UMTS: None
LTE: LBFD-002007
TDLBFD-002007

1526729499 L.Dyn.ACBar.Trigger.Num Number of times that dynamic AC Barring is triggered Multi-mode: None Intelligent Access Class Control
GSM: None Intelligent Access Class Control
UMTS: None
LTE: LOFD-070207
TDLOFD-080202

1526729500 L.Dyn.ACBar.Cancel.Num Number of times that dynamic AC Barring is cancelled Multi-mode: None Intelligent Access Class Control
GSM: None Intelligent Access Class Control
UMTS: None
LTE: LOFD-070207
TDLOFD-080202

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

1526729501 L.Dyn.ACBar.Adjust.Num Number of times that parameters related to dynamic Multi-mode: None Intelligent Access Class Control
AC Barring are adjusted GSM: None Intelligent Access Class Control
UMTS: None
LTE: LOFD-070207
TDLOFD-080202

1526729502 L.Dyn.ACBar.Control.Dur Control duration of dynamic AC Barring Multi-mode: None Intelligent Access Class Control
GSM: None Intelligent Access Class Control
UMTS: None
LTE: LOFD-070207
TDLOFD-080202

1526736656 L.SSAC.Dyn.ACBar.Trigger.Num Number of times dynamic SSAC is triggered Multi-mode: None Broadcast of system information
GSM: None Broadcast of system information
UMTS: None Dynamic Service-Specific Access Control
LTE: LBFD-002009 Dynamic Service-specific Acccess Control
TDLBFD-002009 Intelligent Access Class Control
LOFD-008002
TDLOFD-081222
LOFD-070207

1526736657 L.SSAC.Dyn.ACBar.Adjust.Num Number of times parameters related to dynamic SSAC Multi-mode: None Broadcast of system information
are adjusted GSM: None Broadcast of system information
UMTS: None Dynamic Service-Specific Access Control
LTE: LBFD-002009 Dynamic Service-specific Acccess Control
TDLBFD-002009 Intelligent Access Class Control
LOFD-008002
TDLOFD-081222
LOFD-070207

1526736658 L.SSAC.Dyn.ACBar.Cancel.Num Number of times dynamic SSAC is canceled Multi-mode: None Broadcast of system information
GSM: None Broadcast of system information
UMTS: None Dynamic Service-Specific Access Control
LTE: LBFD-002009 Dynamic Service-specific Acccess Control
TDLBFD-002009 Intelligent Access Class Control
LOFD-008002
TDLOFD-081222
LOFD-070207

1526736659 L.SSAC.Dyn.ACBar.Control.Dur Duration of dynamic SSAC Multi-mode: None Broadcast of system information
GSM: None Broadcast of system information
UMTS: None Dynamic Service-Specific Access Control
LTE: LBFD-002009 Dynamic Service-specific Acccess Control
TDLBFD-002009 Intelligent Access Class Control
LOFD-008002
TDLOFD-081222
LOFD-070207

12 Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

13 Reference Documents

1. 3GPP TS 36.331, " Radio Resource Control (RRC)"


2. 3GPP TS 24.301, "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3"
3. 3GPP TS 22.011, "Service accessibility"
4. 3GPP TS 23.122, "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode"

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

eRAN
Admission and Congestion Control Feature Parameter Description
Issue 01

Date 2015-03-23

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: support@huawei.com

2.3 Contents
1 About This Document
1.1 Scope
1.2 Intended Audience

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

1.3 Change History


1.4 Differences Between eNodeB Types
2 Overview
3 Admission Control
3.1 User Admission
3.2 Service Admission
3.2.1 Non-GBR Service Admission
3.2.2 GBR Service Admission
3.2.2.1 UE Capability Evaluation
3.2.2.2 Cell Congestion Indication
3.2.2.3 Admission Based on QoS Satisfaction Rates
3.3 Preemption
3.3.1 User Preemption
3.3.2 Service Preemption
3.4 Redirection
4 Congestion Control
4.1 Load Status Evaluation
4.2 Release of Low-Priority GBR Services
5 Related Features
5.1 Features Related to LBFD-002023 Admission Control
5.2 Features Related to LOFD-00102901 Radio/transport Resource Pre-emption
5.3 Features Related to LBFD-002024 Congestion Control
6 Network Impact
6.1 LBFD-002023 Admission Control
6.2 LOFD-00102901 Radio/transport resource pre-emption
6.3 LBFD-002024 Congestion Control
7 Engineering Guidelines
7.1 When to Use Admission and Congestion Control
7.2 Required Information
7.3 Planning
7.3.1 RF Planning
7.3.2 Network Planning
7.3.3 Hardware Planning
7.4 Deployment of Admission Control
7.4.1 Requirements
7.4.2 Data Preparation
7.4.3 Activation
7.4.4 Activation Observation
7.4.5 Deactivation
7.5 Deployment of Congestion Control
7.5.1 Deployment Requirements
7.5.2 Data Preparation
7.5.3 Activation
7.5.4 Activation Observation
7.5.5 Deactivation
7.6 Performance Monitoring
7.7 Parameter Optimization
7.8 Troubleshooting
7.8.1 Admission Control
7.8.2 Congestion Control
8 Parameters
9 Counters
10 Glossary
11 Reference Documents

1 About This Document

1 Scope
This document describes admission and congestion control, including its technical principles, related features, network impact, and engineering guidelines.
This document covers the following features:

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

LBFD-002023 Admission Control


LOFD-001029 Enhanced Admission Control
LOFD-00102901 Radio/transport Resource Preemption
LBFD-002024 Congestion Control

This document applies to the following types of eNodeBs.

eNodeB Type Model

Macro 3900 series eNodeBs

Micro BTS3202E

LampSite DBS3900

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.

2 Intended Audience
This document is intended for personnel who:

Need to understand the features described herein


Work with Huawei products

3 Change History
This section provides information about the changes in different document versions. There are two types of changes:

Feature change
Changes in features and parameters of a specified version as well as the affected entities.
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.

RAN8.1 01 (2015-03-23)

This issue does not include any changes.

RAN8.1 Draft A (2015-01-15)

Compared with Issue 01 (2014-04-26) of eRAN7.0, Draft A (2015-01-15) of eRAN8.1 includes the following changes.

Change Type Change Description Parameter Change Affected Entity

Feature change Added performance counters related to admission control and preemption. For details, see 7.6 None Macro/Micro/LampSite
Performance Monitoring.

Editorial change Revised the description in 2 Overview. None -

4 Differences Between eNodeB Types


The features described in this document are implemented in the same way on macro, micro, and LampSite eNodeBs.

2 Overview

roduction

During admission control, an eNodeB decides whether to accept a guaranteed bit rate (GBR) service request (either new service or handover) based on the physical resource block (PRB) usage and the quality of service (QoS) satisfaction rate of GBR services. During congestion control, the eNodeB controls system load to
ensure a high overall QoS satisfaction rate and stable system operation.

enefits

Load control maintains system stability by rejecting certain admission requests or releasing some admitted services, while maximizing resource usage. Load control ensures the quality of admitted services by controlling the cell load. It also provides the required QoS for individual radio bearers and maximizes cell capacity.

3 Admission Control

This chapter describes the basic feature LBFD-002023 Admission Control.


Admission control is categorized into radio-resource-based admission control and transport-resource-based admission control. This document describes radio-resource-based admission control. For details about transport-resource-based admission control, see Transport Resource Management Feature Parameter
Description. For details about how to configure this feature, see 7 Engineering Guidelines.
Radio-resource-based admission control is categorized into user admission and service admission.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

When a piece of user equipment (UE) requests access to a network, that is, when a UE requests setup of a radio resource control (RRC) connection or requests an incoming handover, the E-UTRAN NodeB (eNodeB) performs the user admission procedure.
When a UE that has accessed a cell requests a new service, that is, when a UE requests establishment of an E-UTRAN radio access bearer (E-RAB) or requests an incoming handover, the eNodeB performs the service admission procedure.

1 User Admission
When a UE requests to access a network, that is, when a UE requests setup of an RRC connection or requests an incoming handover, the eNodeB performs the user admission procedure. Figure 3-1 shows the user admission procedure.
Figure 3-1 User admission procedure

The user admission procedure is as follows:

1. The eNodeB checks whether the CPU resource is limited. If the CPU resource is limited, the eNodeB rejects the access request. For details about how the eNodeB checks whether the CPU resource is limited, see Flow Control Feature Parameter Description.
2. The eNodeB checks whether the sounding reference signal (SRS) resource is successfully allocated. For details about the SRS resource allocation principle, see Physical Channel Resource Management Feature Parameter Description. The eNodeB performs this step differently based on whether LBBPc or BBP
of another type is configured.

If the LBBPc is configured, the eNodeB performs this step as follows:


If the SRS resource is configured for the cell, the cell supports uplink timing measurement using only the SRS. Therefore, if the SRS resource allocation fails, the uplink timing of the UE may not be accurate and the eNodeB rejects the access request.
If the SRS resource is not configured for the cell, the cell supports uplink timing measurement using the demodulation reference signal (DMRS). Even if the SRS resource is not allocated, the eNodeB accepts the access request.

Other types of BBPs support uplink timing measurement using the DMRS. Even if the SRS resource allocation fails, the uplink timing of the UE is accurate and the eNodeB does not reject the access request.

NOTE:
LampSite eNodeBs do not support the LBBPc.

3. The eNodeB checks whether the PUCCH resource is successfully allocated. If the PUCCH resource allocation fails, the eNodeB rejects the access request. For details about the PUCCH resource allocation principle, see Physical Channel Resource Management Feature Parameter Description.
4. The eNodeB checks whether the number of users is limited. If the number of admitted users has reached the maximum or the licensed user number, the eNodeB determines that the number of users is limited and the admission fails.
5. For the user that is admitted by the eNodeB, if the UE requests a service (that is, to establish an E-RAB), the eNodeB performs the service admission procedure. For details, see 3.2 Service Admission.
6. If the UE's access request is rejected by the eNodeB, the UE can initiate a user preemption procedure. For details, see 3.3.1 User Preemption.

NOTE:

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

The number of emergency UEs that can be admitted is restricted only by the maximum number of UEs supported by the cell rather than by the licensed number of UEs so that emergency UEs can preferentially be admitted.
In the RAN sharing scenario, the licensed user number varies depending on operators. Therefore, the eNodeB temporarily allows the access to obtain the PLMN ID to determine whether the licensed user number is limited. If the licensed user number is limited and the preemption based on user number fails, the eNodeB
rejects the initial context setup request of the temporarily accessed user and releases the user.

In user admission, UE numbers are reserved for privileged UEs to increase their admission success rates. Privileged UEs include emergency UEs and high-priority UEs with a "highPriorityAccess" cause value in an RRC connection establishment request. Other UEs are common UEs.
The prioritized access to services of privileged UEs can be achieved based on user preemption. However, user preemption is not allowed in some areas according to local regulations. Therefore, UE numbers are reserved for privileged UEs to ensure the admission of these UEs.
The UE numbers reserved for privileged UEs are controlled by the CellRacThd.AcReservedUserNumber parameter.

When the CellRacThd.AcReservedUserNumber parameter is set to 0, user-number-reservation-based admission control is disabled. In this case, the eNodeB rejects the access requests of high-priority UEs when the number of admitted users has reached the licensed user number. The eNodeB rejects the
access requests of both privileged UEs and common UEs when the number of admitted users has reached the maximum number.
If the CellRacThd.AcReservedUserNumber parameter is set to a non-zero value, UE numbers are reserved for privileged UEs. In this case, the eNodeB accepts the access requests of high-priority UEs even when the number of admitted users has reached the licensed user number. The eNodeB admits
privileged UEs and common UEs based on different UE number requirements.
The number of privileged UEs that can be admitted is based on the maximum number of UEs supported by the cell.
The number of common UEs that can be admitted is the difference between the maximum number of UEs supported by the cell and the CellRacThd.AcReservedUserNumber parameter value. The CellRacThd.AcReservedUserNumber parameter specifies the UE numbers reserved for privileged
UEs.

If the CellRacThd.AcReservedUserNumber parameter is set to a non-zero value, it is recommended that SRS resources and PUCCH resources be set to default values. In this case, neither SRS resources nor PUCCH resources will directly cause user admission failures. It is recommended that the ARP values of the
bearers for UEs whose cause value for an RRC connection establishment request is "highPriorityAccess" and that for emergency UEs be set to the same. This ensures the GBR services of these high-priority UEs are directly admitted successfully.

2 Service Admission
When a UE that has accessed a cell requests setup of a new service, that is, when a UE requests to establish an E-RAB or requests a handover to the cell, the eNodeB performs the service admission procedure. Figure 3-2 shows the service admission procedure.

Figure 3-2 Service admission procedure

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

3.2.1 Non-GBR Service Admission


For a non-GBR service, the admission procedure is as follows:

If the SRS or PUCCH resource allocation fails, the eNodeB rejects the access request.
If both the SRS resource allocation and the PUCCH resource allocation are successful, the eNodeB accepts the request. In the admission procedure, the eNodeB does not check the UE capabilities or whether the cell is congested, or make the admission decision based on the QoS satisfaction rates.

NOTE:
SRS resource allocation is required only if the SRS resource is configured for the LBBPc.

3.2.2 GBR Service Admission


For a GBR service, its QoS has to be guaranteed. The admission procedure is as follows:

If the SRS or PUCCH resource allocation fails, the eNodeB rejects the access request.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

If both the SRS resource allocation and the PUCCH resource allocation are successful, the eNodeB makes the admission decision as follows:
For an emergency call, the eNodeB accepts the request.
For a non-emergency call, the eNodeB checks the UE capabilities and whether the cell is congested, and then makes the decision based on the QoS satisfaction rates.

NOTE:
SRS resource allocation is required only if the SRS resource is configured for the LBBPc.

3.2.2.1 UE Capability Evaluation


The UE reports its capabilities to the evolved packet core (EPC) each time the UE attaches to the network. When the UE needs to update its capabilities, it performs detach and then attach procedures to report the new capabilities to the EPC. If the eNodeB does not know the UE capabilities, it initiates a UE capability
transfer procedure to request the UE to report its capabilities to the eNodeB and the EPC. For details, see section 5.6.3 in 3GPP TS 36.331 V10.6.0 (2012-06).
When the UE initiates a new service request, the Mobility Management Entity (MME) sends an INITIAL CONTEXT SETUP REQUEST message to the eNodeB over the S1 interface, indicating the UE capabilities and bearer parameters. For details about UE capabilities, see section 4.1 in 3GPP TS 36.306 V10.6.0 (2012-
06).
The eNodeB stores the information and checks whether the UE supports the specified bearer. If the UE does not support the bearer parameters, the eNodeB rejects the access request. The major concern about the UE capabilities is whether the total rate of various services exceeds the maximum UE capability, indicated
by the maximum transport block size for the UE. For details, see section 8.3.1 in 3GPP TS 36.413 V10.6.0 (2012-06).

3.2.2.2 Cell Congestion Indication


Cell congestion indications are provided by congestion control to indicate that the Uu interface resources are insufficient. There are four types of indications:

Uplink Congested and Downlink Not Congested


Downlink Congested and Uplink Not Congested
Uplink and Downlink Congested
Uplink and Downlink Congestion Cleared

If a GBR service access request arrives, the eNodeB rejects the access request (either new services or handovers) regardless of whether congestion occurs in the downlink or uplink.

3.2.2.3 Admission Based on QoS Satisfaction Rates


The QoS satisfaction rate of GBR services in a cell reflects the QoS conditions of admitted GBR services in the cell. It is used for evaluating cell load and making admission decisions.
In the downlink, radio resources such as physical resource blocks (PRBs) and power are shared by all UEs in a cell. Decreases in the downlink QoS satisfaction rates indicate limited radio resources. The eNodeB performs downlink admission control based only on QoS satisfaction rates.
In the uplink, radio resources may not be fully used because of a limitation on uplink power. The eNodeB performs uplink admission control based on the PRB usage, wait time for uplink scheduling of voice over IP (VoIP) services, and QoS satisfaction rates.
Figure 3-3 and Figure 3-4 show the downlink and uplink admission procedures for GBR services based on QoS satisfaction rates, respectively.

Figure 3-3 Downlink admission procedure for GBR services

Figure 3-4 Uplink admission procedure for GBR services

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

RB Usage Monitoring

By monitoring the PRB usage of services with high scheduling priorities in the uplink, the eNodeB learns about the usage of uplink time-frequency resources in the cell and preliminarily evaluates the cell load. In the uplink, services with high scheduling priorities include GBR services and the signaling and services whose
scheduling priorities are higher than GBR services, such as retransmissions, signaling radio bearers (SRBs), and scheduling requests (SRs). The Media Access Control (MAC) layer calculates the PRB usage using the following formula:

After filtering, the eNodeB compares the calculated PRB usage with the uplink PRB usage thresholds CellRacThd.UlRbHighThd and CellRacThd.UlRbLowThd and then determines the PRB usage status. Using both the upper and lower thresholds prevents a possible ping-pong effect.

aluation of the Wait Time for Uplink Scheduling of VoIP Services

The wait time starts when a VoIP service requests uplink resources and stops when the VoIP service is allocated uplink resources. eNodeBs regard wait time longer than 100 ms to be too long.

aluation of QoS Satisfaction Rates

The QoS class identifier (QCI) of a service reflects the QoS requirements of that service, and each QCI corresponds to a unique set of QoS parameters. For details, see section 6.1.7 in 3GPP TS 23.203 V10.7.0 (2012-06). This protocol describes the characteristics of different services and the standards for evaluating their
QoS satisfaction rates in the LTE QoS mechanism.
In the downlink, QoS satisfaction rates are evaluated based on the logical channels corresponding to the QCIs. In the uplink, however, QoS satisfaction rates are evaluated based on logical channel groups. A logical channel group is defined as a group of radio bearers with similar QoS requirements. For details about logical
channel groups, see section 5.4.5 in 3GPP TS 36.321 V10.5.0 (2012-03). The reason for the difference between the uplink and the downlink is that the eNodeB cannot estimate the amount of buffered data to be transmitted through each logical channel on the UE side. The evaluation method for the uplink helps reduce
signaling load and the number of Buffer Status Reports (BSRs).
The uplink and downlink QoS satisfaction rates of GBR services are calculated per QCI, and admission thresholds are also set per QCI to achieve admission differentiation between QCIs.

aluation of Downlink QoS Satisfaction Rates

Services with QCI 1 are VoIP services. Their downlink QoS satisfaction rate is represented by the average downlink satisfaction rate of VoIP services in a cell, that is, the ratio of the sum of the downlink satisfaction rates of all VoIP services in a cell to the total number of VoIP services in a cell.
The downlink QoS satisfaction rate of a single VoIP service is calculated by using the following formula:

A voice packet is satisfactory if it is buffered for a time less than 50 ms.


Services with QCIs 2 to 4 are GBR services. The downlink QoS satisfaction rate of GBR services with QCI 2, 3, or 4 is calculated by using the following formula:

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

where
i = 2, 3, or 4

NOTE:
Section 6.1.7 in 3GPP TS 23.203 V11.6.0 (2012-06) provides an example mapping between QCIs and service types but does not provide definitions of the mapping. Huawei implements the mapping according to the examples, where QCI 1 represents VoIP services.

aluation of Uplink QoS Satisfaction Rates

Services with QCI 1 are VoIP services. Their uplink QoS satisfaction rate is represented by the average uplink satisfaction rate of VoIP services in a cell, that is, the ratio of the sum of the uplink satisfaction rates of all VoIP services in a cell to the total number of VoIP services in a cell.
The uplink QoS satisfaction rate of a single VoIP service is calculated by using the following formula:

NOTE:
The uplink QoS satisfaction rate of a VoIP service is calculated differently from the downlink QoS satisfaction rate of a VoIP service. In the uplink, the eNodeB cannot obtain the time for which voice packets are buffered on the UE. However, if an uplink voice packet is buffered on the UE for a time longer than the length of
the timer for discarding Packet Data Convergence Protocol (PDCP) PDUs, the voice packet is discarded. Therefore, the percentage of PDCP PDUs successfully received by the eNodeB is used to determine whether there are timeout voice packets. For details, see section 5.4 "PDCP discard" in 3GPP 36.323 V8.6.0.

Services with QCIs 2 to 4 are GBR services. Their uplink QoS satisfaction rate is evaluated for each logical channel group. The QoS satisfaction rate is represented by the ratio of the transmitted data to the total amount of data to be transmitted. A higher ratio indicates a higher QoS satisfaction rate. The uplink QoS
satisfaction rate of GBR services with QCIs 2 to 4 is calculated by using the following formula:

QCIs 1 to 4 can be mapped to logical channel groups. For details about the mapping, see Scheduling Feature Parameter Description. If QCIs 2 to 4 are mapped to logical channel group 2, the uplink QoS satisfaction rates for services with QCIs 2 to 4 are represented by the satisfaction rate for logical channel group 2.

dmission Decision Based on QoS Satisfaction Rates

The admission threshold for handovers is lower than that for new services. The eNodeB defines four handover thresholds QcixHoThd (x = 1–4) for the QCIs. Based on the handover thresholds, service differentiation can be achieved by setting admission offsets for new gold-, silver-, and bronze-level services, based on the
mapping between ARP values and service priorities. The admission offsets are CellRacThd.NewGoldServiceOffset, CellRacThd.NewSilverServiceOffset, and CellRacThd.NewCopperServiceOffset. These offset values apply to both the uplink and downlink.
The eNodeB categorizes services based on their ARP values. The ARP values are mapped to three service priorities: gold, silver, and bronze. The mapping can be adjusted by setting CellRacThd.GoldServiceArpThd (the ARP threshold for gold-level services) or CellRacThd.SilverServiceArpThd (the ARP threshold for
silver-level services). The ARP values beyond the ranges defined by these two parameters correspond to bronze-level services. A small ARP value indicates a high priority level. Table 3-1 shows a typical mapping between the ARP values and the service priorities.

Table 3-1 Typical mapping between the ARP values and the service priorities

ARP Value Service Priority

1–5 Gold

6–10 Silver

11–15 Bronze

For details about ARPs, see section 4.7.3 in 3GPP TS 23.401 V10.8.0 (2012-06).
For GBR services whose QCIs range from 1 to 4, the admission thresholds for handovers and new services corresponding to a QCI are as follows:

The admission threshold for handovers is QcixHoThd.


The admission threshold for new gold-level services is QcixHoThd plus CellRacThd.NewGoldServiceOffset.
The admission threshold for new silver-level services is QcixHoThd plus CellRacThd.NewSilverServiceOffset.
The admission threshold for new bronze-level services is QcixHoThd plus CellRacThd.NewCopperServiceOffset.

The relationship between these thresholds is as follows:


QcixHoThd ≤ QcixHoThd + CellRacThd.NewGoldServiceOffset ≤ QcixHoThd + CellRacThd.NewSilverServiceOffset ≤ QcixHoThd + CellRacThd.NewCopperServiceOffset ≤ 100%
Assume that SQCI = x (x = 1–4) represents the QoS satisfaction rate for QCI x. The following rules apply to downlink admission evaluation:

For SQCI = x ≥ QcixHoThd + CellRacThd.NewCopperServiceOffset


If the QoS satisfaction rates of all QCIs except QCI x are higher than the corresponding handover admission thresholds, then the eNodeB accepts requests for new gold-, silver-, and bronze-level services and handovers with QCI x.
If the QoS satisfaction rate of any QCI is lower than the corresponding handover admission threshold, then the eNodeB rejects requests for new gold-, silver-, and bronze-level services with QCI x but accepts requests for incoming handovers with QCI x.
For QcixHoThd + CellRacThd.NewCopperServiceOffset > SQCI = x ≥ QcixHoThd + CellRacThd.NewSilverServiceOffset
If the QoS satisfaction rates of all QCIs except QCI x are higher than the corresponding handover admission thresholds, then the eNodeB accepts requests for new gold- and silver-level services and handovers with QCI x but rejects requests for new bronze-level services with QCI x.
If the QoS satisfaction rate of any QCI is lower than the corresponding handover admission threshold, then the eNodeB rejects requests for new gold-, silver-, and bronze-level services with QCI x but accepts requests for incoming handovers with QCI x.
For QcixHoThd + CellRacThd.NewSilverServiceOffset > SQCI = x ≥ QcixHoThd + CellRacThd.NewGoldServiceOffset
If the QoS satisfaction rates of all QCIs except QCI x are higher than the corresponding handover admission thresholds, then the eNodeB accepts requests for new gold-level services and handovers with QCI x but rejects requests for new silver- and bronze-level services with QCI x.
If the QoS satisfaction rate of any QCI is lower than the corresponding handover admission threshold, then the eNodeB rejects requests for new gold-, silver-, and bronze-level services with QCI x but accepts requests for incoming handovers with QCI x.
For QcixHoThd + CellRacThd.NewGoldServiceOffset > SQCI = x ≥ QcixHoThd
The eNodeB rejects requests for new gold-, silver-, bronze-level services with QCI x but accepts requests for handovers with QCI x.
For QcixHoThd > SQCI = x

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

The eNodeB rejects requests for new services and handovers with QCI x.

The rules for uplink admission evaluation are similar to the rules for downlink admission evaluation. The difference is that the eNodeB evaluates the QoS satisfaction rates of logical channel groups when admitting GBR services in the uplink. For details, see Evaluation of Uplink QoS Satisfaction Rates.

3 Preemption
This section describes radio resource preemption in the optional feature LOFD-00102901 Radio/transport Resource Pre-emption.
For details about transport resource preemption, see Transport Resource Management Feature Parameter Description.

3.3.1 User Preemption


When an emergency UE accesses the network and fails to be allocated SRS or PUCCH resources, the UE preempts the resources of the common UE in the synchronization state and with the lowest ARP in the same cell. If the common UE has multiple services with different ARPs, the highest ARP is considered as the
ARP of the UE.
When a UE with a high ARP or an emergency UE requests access to the network, the eNodeB rejects the access request because the number of users is limited. If the IntraOpUeNumPreemptSwitch(IntraOpUeNumPreemptSwitch) option of the ENodeBAlgoSwitch.UeNumPreemptSwitch parameter is selected, this
UE preempts the resources of common UEs with low ARPs.

NOTE:
In the user-number-based preemption, the eNodeB establishes a temporary RRC connection for any UE requesting access to the eNodeB in order to obtain the UE's ARP attributes.

In the user-number-based preemption, the resources for the following types of low-ARP UEs are preempted in descending order of priority:

Low-ARP UEs in the out-of-synchronization state performing non-GBR services


Low-ARP UEs in the out-of-synchronization state performing GBR services
Low-ARP UEs in the synchronized state performing non-GBR services
Low-ARP UEs in the synchronized state performing GBR services

If the preemption succeeds and redirection is enabled, the eNodeB performs a redirection for the UE whose resource is preempted. If the preemption request is rejected and redirection is enabled, the eNodeB performs a redirection for the UE that requests a preemption. For details about redirection procedure, see 3.4
Redirection.
The ARP value of a bearer of a UE is generally allocated by the EPC. If a UE initiates a CSFB procedure, the EPC allocates a lower ARP value for the bearer of the UE. When the licensed number of UEs is limited, such a UE fails to preempt resources and then experiences an admission failure.
UEs initiating CSFB procedures can be classified as emergency UEs initiating CSFB procedures and common UEs initiating CSFB procedures. If the value of the IE CS Fallback Indicator in the INITIAL CONTEXT SETUP REQUEST message sent from the EPC to the eNodeB is CS Fallback High Priority, the UE is an
emergency UE initiating a CSFB procedure; otherwise, the UE is a common UE initiating a CSFB procedure.
You can set the CsFallbackPolicyCfg.CsfbUserArpCfgSwitch parameter to increase the ARP values of bearers for emergency UEs initiating CSFB procedures. The IEs contained in the ARP values of default bearers for emergency UEs initiating CSFB procedures are configured as follows:

Pre-emption Capability
The value of this IE for emergency UEs initiating CSFB procedures is may trigger pre-emption, indicating that the UEs can preempt resources of other low-priority UEs.
Pre-emption Vulnerability
The value of this IE for emergency UEs initiating CSFB procedures is not pre-emptable, indicating that resources of the UEs cannot be preempted by other UEs.
Priority Level
The value of this IE for emergency UEs initiating CSFB procedures is 1.
The ARP IE priority level for common UEs initiating CSFB procedures can be specified by the CsFallbackPolicyCfg.NormalCsfbUserArp parameter.

To ensure that common UEs initiating CSFB procedures are capable of preempting users when the number of UEs allowed to be admitted is limited, it is recommended that the bearers of common UEs initiating CSFB procedures be configured with high ARP priorities.

3.3.2 Service Preemption


When a new emergency service requests preemption and fails to be allocated SRS or PUCCH resources, the service preempts the resources of the common UE in the synchronization state and with the lowest ARP in the same cell. If the common UE has multiple services with different ARPs, the highest ARP is
considered as the ARP of the UE.
When a GBR service with a high ARP requests service preemption, it preempts GBR services with low ARPs if the request is rejected because the cell is congested or the admission based on the QoS satisfaction rates fails. Service preemption is triggered if one of the conditions shown in Figure 3-3 or Figure 3-4 is met.
Service preemption is enabled by selecting the PreemptionSwitch(PreemptionSwitch) option of the CellAlgoSwitch.RacAlgoSwitch parameter. Note that SRBs, IP multimedia subsystem (IMS) signaling, and emergency calls cannot be preempted.
A service can preempt other services only if its ARP information element (IE) "pre-emption capability" is "may trigger pre-emption". If a service is not capable of preemption, it cannot be admitted. If service A is capable of preemption, it can preempt a service B that meets all of the following conditions:

Only non-emergency GBR services can be preempted.


The value of the ARP IE "pre-emption vulnerability" of service B is "pre-emptable".
The value of the ARP IE "priority level" of service B is greater than that of service A.
If service B is a GBR service, the resources allocated to it are greater than or equal to the resources required by GBR service A.

Preemption fails if any one of the preceding conditions is not met. If none of the GBR services of a UE is admitted or preemption for all GBR services of a UE fails, the UE is redirected if redirection is enabled. For details about operations related to redirection, see 3.4 Redirection.

NOTE:
A service whose ARP value is 15 can neither preempt other services nor be preempted by other services. For details, see section 9.2.1.60 in 3GPP TS 36.413 V10.6.0 (2012-06).

During the preemption procedure, the eNodeB first groups GBR services with low priorities and then selects services that can be preempted from this group. The procedure is as follows:

1. The eNodeB groups the GBR services with low priorities.


The eNodeB first selects releasable GBR services and then groups the services with the lowest priorities among them. A releasable GBR service must meet the following conditions:
The value of the ARP IE "pre-emption vulnerability" of the service is "pre-emptable".
The service is not an emergency call.
The service rate is not 0.
The eNodeB sorts these GBR services based on the following rule: The service with the largest value of the ARP IE "priority level" has the lowest priority and ranks first. If two services have the same "priority level" value, the service that occupies more PRBs ranks ahead of the other.

2. The eNodeB selects services to be preempted.


The eNodeB estimates the number of PRBs required by a preempting service based on the average spectral efficiency of the cell. The eNodeB calculates the number of PRBs released from the group of GBR services with low priorities. The calculation stops after the number of released PRBs meets the
requirements of the preempting service. The preemption fails if no service can be preempted or the number of PRBs released from ten preempted services does not meet the requirements of the preempting service.
If the GBR service to be preempted is the only GBR service on a UE, the UE can be redirected when redirection is enabled. For details about redirection, see 3.4 Redirection.

4 Redirection

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

During a redirection, the eNodeB sends the UE an RRCConnectionRelease message that includes the target frequency information for the redirection. Redirection is enabled if LoadBasedSwitch under the ENodeBAlgoSwitch.RedirectSwitch parameter is on.
The eNodeB selects the target frequency as follows:

If a subscriber profile ID (SPID) has been specified for the UE, the eNodeB determines the UE-supported RATs and frequency bands and checks for the mapping between frequencies and priorities in the associated SPID configuration. The eNodeB then selects the highest-priority frequency except the serving
frequency as the target frequency. For details about SPIDs, see Flexible User Steering Feature Parameter Description.
If an SPID is not specified for the UE or frequency priorities are not set in the SPID configuration for the UE, the eNodeB considers the operator-specific dedicated cell-reselection priorities for frequencies. Among the UE-supported frequency bands, the eNodeB selects the highest-priority frequency except the
serving frequency as the target frequency. The priorities are specified in the EutranNFreqRanShare, UtranRanShare, and GeranRanShare MOs or in the EutranNFreqSCellOp, UtranNFreqSCellOp, GeranNFGroupSCellOp, and Cdma2000BcSCellOp MOs.
If an SPID is not specified for the UE or frequency priorities are not set in the SPID configuration for the UE, and if operator-specific dedicated cell-reselection priorities are not specified, the eNodeB considers common cell-reselection priorities. Among the UE-supported frequency bands, the eNodeB selects the
highest-priority frequency except the serving frequency as the target frequency. The priorities are specified in the EutranInterNFreq, UtranNFreq, and GeranNfreqGroup MOs.

NOTE:
If the admission fails for a UE requesting a handover, the UE cannot be redirected to another cell.

4 Congestion Control

This chapter describes the basic feature LBFD-002024 Congestion Control.


Congestion control reduces congestion caused by an insufficiency of radio resources or transport resources. This document describes only the former. For details about the latter, see Transport Resource Management Feature Parameter Description.
Congestion can be prevented in most cases if admission control is performed. However, congestion may occur in the following cases:

The services are diverse and the data rates of certain services vary significantly. Variations in the data volume inevitably affect the cell load.
The radio conditions vary because of user mobility. The same service at the same data rate may require different radio resources on different occasions.

In these two cases, the cell load varies and the quality of admitted services gets affected, even if the number of users in the cell does not change. The congestion control algorithm is required to handle possible congestion.
Figure 4-1 shows the congestion control process. Congestion control is enabled if the DlLdcSwitch(dlLdcSwitch) or UlLdcSwitch(ulLdcSwitch) check box under the CellAlgoSwitch.RacAlgoSwitch parameter is selected.

Figure 4-1 Congestion control process

When the cell is congested, congestion control releases the GBR services with low priorities first to make some resources available. The release reduces system load and helps ensure the quality of other admitted services.
To ensure continuity and stability of emergency calls, the eNodeB does not release emergency calls.
For details about how to configure this feature, see 7 Engineering Guidelines.

1 Load Status Evaluation


The eNodeB checks the load status by monitoring the PRB usage and QoS satisfaction rate. The cell status can be either of the following:

Congested state
A cell is regarded as congested in the downlink if the downlink QoS satisfaction rate of one or more QCIs is lower than the relevant congestion threshold.
A cell is regarded as congested in the uplink if the uplink QoS satisfaction rate of one or more QCIs is lower than the relevant congestion threshold and the uplink PRB usage is high, or if the uplink QoS satisfaction rate of one or more QCIs is lower than the relevant congestion threshold and the wait time for
uplink scheduling of VoIP services is too long.
When the cell is congested, the congestion control algorithm instructs the admission control algorithm to reject all access requests and, in addition, takes actions to reduce cell load. When the QoS satisfaction rates of QCIs 1, 2, 3, and 4 all become higher than the sum of the related congestion threshold and
CellRacThd.CongRelOffset, the cell returns to the normal state. The congestion thresholds are specified by QcixCongThd (x = 1–4), that is, by the CellRacThd.Qci1CongThd, CellRacThd.Qci2CongThd, CellRacThd.Qci3CongThd, and CellRacThd.Qci4CongThd parameters.
For each QCI, the sum of QcixCongThd (x = 1–4) and CellRacThd.CongRelOffset must be lower than the corresponding QcixHoThd (x = 1–4).
Normal state
The cell is regarded as normal if the QoS satisfaction rates of QCIs 1, 2, 3, and 4 are all higher than the corresponding QcixCongThd (x = 1–4).

2 Release of Low-Priority GBR Services


f a cell is congested, congestion control selects a service that ranks the first in the group of admitted low-priority GBR services and releases the selected service.
If the only GBR service on the selected UE is released and redirection is enabled, the eNodeB redirects the UE to another frequency or RAT, increasing the access success rate of the UE. For details about redirection, see 3.4 Redirection.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

After the GBR service is released, the eNodeB checks whether the QoS satisfaction rates of GBR services are restored. If the QoS satisfaction rates of GBR services are not restored, the eNodeB performs the GBR service release procedure again until the congestion is relieved.

5 Related Features

1 Features Related to LBFD-002023 Admission Control


erequisite Features

None

utually Exclusive Features

None

pacted Features

None

2 Features Related to LOFD-00102901 Radio/transport Resource Pre-emption


erequisite Features

LOFD-00102901 Radio/transport Resource Pre-emption is dependent on LBFD-002023 Admission Control. Preemption can be triggered only if admission fails.

utually Exclusive Features

None

pacted Features

LBFD-002028 Emergency Call has an impact on LOFD-00102901 Radio/transport Resource Pre-emption. Emergency calls are assigned the highest priority. If the admission of an emergency call fails, preemption is performed for the emergency call.

3 Features Related to LBFD-002024 Congestion Control


erequisite Features

None

utually Exclusive Features

None

pacted Features

None

6 Network Impact

1 LBFD-002023 Admission Control


stem Capacity

The admission control algorithm maximizes system capacity while satisfying the QoS requirements of admitted services. For example, if the QoS satisfaction rate of GBR services is low, new services cannot be admitted and preemption will be triggered. System capacity can be maximized on condition that the QoS
requirements are satisfied.

etwork Performance

If network congestion results in limited system capacity, the implementation of admission control algorithm decreases the admission and handover success rates. For admission control based on QoS satisfaction rates, if the admission threshold is set to a smaller value, GBR services are easier to be admitted and the
admission success rate of GBR services increases. However, the service quality of admitted GBR services becomes poorer.

2 LOFD-00102901 Radio/transport resource pre-emption


stem Capacity

No impact.

etwork Performance

Preemption increases the access success rate for users with high ARPs. However, users with low ARPs are forcibly released and their service drop rate increases.
The way the eNodeB performs user-number-based preemption will increase the amount of radio signaling because of the following three actions:

The eNodeB establishes a temporary RRC connection for any UE requesting access to the eNodeB in order to obtain its ARP attributes.
The eNodeB releases temporary RRC connections for those UEs that eventually encounter preemption failures.
The eNodeB releases RRC connections for preempted UEs.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

3 LBFD-002024 Congestion Control


stem Capacity

The congestion control algorithm maximizes system capacity while preferentially satisfying the QoS requirements of users with high ARPs. When congestion occurs, the congestion control algorithm informs the admission control algorithm. Then, the admission control algorithm starts to reject access requests.

etwork Performance

The congestion control algorithm increases the service drop rate because the congestion-control-triggered releases of users are regarded as service drops. Counters are provided to indicate congestion-triggered service drops. For details about the counters, see 9 Counters.

7 Engineering Guidelines

1 When to Use Admission and Congestion Control


When a network becomes congested with an increasing number of users and higher QoS requirements, eNodeBs need to perform radio resource management so that QoS requirements of ongoing services can be fulfilled and differentiated services can be provided.
When radio resource congestion occurs (for example, QoS requirements cannot be fulfilled or radio bearers cannot be set up), activate admission control to relieve congestion and provide service-priority-based access services.
When congestion increases so that QoS requirements still cannot be fulfilled, activate congestion control to enable low-priority service release.

2 Required Information
For both admission control and congestion control, collect the QoS satisfaction rates and uplink PRB usage of cells.

3 Planning

7.3.1 RF Planning
N/A

7.3.2 Network Planning


Network planning is required for redirection. Redirection can transfer loads to inter-frequency or inter-RAT cells if admission fails or a low-priority service needs to be released.
During network planning, operators can coordinate resources of the GERAN, UTRAN, and E-UTRAN in a hierarchical structure to increase return on investment, better utilize existing resources, and achieve service steering.

7.3.3 Hardware Planning


N/A

4 Deployment of Admission Control

7.4.1 Requirements
ature

For details, see 5.1 Features Related to LBFD-002023 Admission Control in the section "Impacted Features".

ardware

None

cense

The required licenses for the Enhanced Admission Control feature must be activated before service preemption is enabled.
The operator must purchase and activate the licenses of the features listed in the following table.

Feature ID Feature Name Model License Control Item NE Sales Unit

LOFD-001029 Enhanced Admission Control LT1S000EAC00 Enhanced Admission Control (FDD) Macro eNodeB/LampSite eNodeB/BTS3202E per RRC Connected User

her Requirements

As required by congestion control,


the preemption capability and vulnerability must be specified in the EPC for services with different priorities.

7.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:

Network plan (negotiation required): parameter values planned by the operator and negotiated with the EPC or peer transmission equipment
Network plan (negotiation not required): parameter values planned and set by the operator
User-defined: parameter values set by users

equired Data

N/A

enario-specific Data

Scenario 1: Admission Based on QoS Satisfaction Rates


The following table describes the parameters that must be set in CellAlgoSwitch MOs to enable admission based on QoS satisfaction rates.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

Parameter Name Parameter ID Data Source Setting Notes

Local cell ID CellAlgoSwitch.LocalCellId Network plan (negotiation not required) This parameter specifies the local ID of a cell. It uniquely identifies a
cell within an eNodeB.
Set this parameter based on the network plan.

RAC algorithm switch CellAlgoSwitch.RacAlgoSwitch Network plan (negotiation not required) To enable downlink admission based on QoS satisfaction
rates, select the DlSwitch(dlCacSwitch) check box.
To disable downlink admission based on QoS satisfaction
rates, clear the DlSwitch(dlCacSwitch) check box.

To enable uplink admission based on QoS satisfaction


rates, select the UlSwitch(ulCacSwitch) check box.
To disable uplink admission based on QoS satisfaction
rates, clear the UlSwitch(ulCacSwitch) check box.

The following table describes the parameters that must be set in CellRacThd MOs to configure admission based on QoS satisfaction rates.

Parameter Name Parameter ID Data Source Setting Notes

Local cell ID CellRacThd.LocalCellId Network plan (negotiation not required) This parameter specifies the local ID of a cell. It uniquely identifies a
cell within an eNodeB.
Set this parameter based on the network plan.

Gold service arp threshold CellRacThd.GoldServiceArpThd Network plan (negotiation not required) This parameter specifies the ARP threshold for gold-level services. A
service is defined as a gold-level service if its ARP value is less than
or equal to this parameter value. A smaller ARP value indicates a
higher priority.
The value 5 is recommended.

Silver service arp threshold CellRacThd.SilverServiceArpThd Network plan (negotiation not required) This parameter specifies the ARP threshold for silver-level services.
A service is defined as a silver-level service if its ARP value is less
than or equal to this parameter value and greater than the value of
CellRacThd.GoldServiceArpThd.
The value 10 is recommended.
A service is defined as a bronze-level service if its ARP value is
greater than CellRacThd.SilverServiceArpThd.
A smaller ARP value indicates a higher priority.

QCI1 handover admission threshold CellRacThd.Qci1HoThd Network plan (negotiation not required) This parameter specifies the handover admission threshold for QCI 1.
The parameter applies to both uplink and downlink.
If the QoS satisfaction rate of services with a QCI of 1 in
the cell is higher than or equal to this threshold, handover
services with a QCI of 1 are admitted.
If the QoS satisfaction rate of these services is lower than
this threshold, handover services with a QCI of 1 are not
admitted.
The value 90 is recommended.

QCI2 handover admission threshold CellRacThd.Qci2HoThd Network plan (negotiation not required) This parameter specifies the handover admission threshold for QCI 2.
The parameter applies to both uplink and downlink.
If the QoS satisfaction rate of services with a QCI of 2 in
the cell is higher than or equal to this threshold, handover
services with a QCI of 2 are admitted.
If the QoS satisfaction rate of these services is lower than
this threshold, handover services with a QCI of 2 are not
admitted.
The value 90 is recommended.

QCI3 handover admission threshold CellRacThd.Qci3HoThd Network plan (negotiation not required) This parameter specifies the handover admission threshold for QCI 3.
The parameter applies to both uplink and downlink.
If the QoS satisfaction rate of services with a QCI of 3 in
the cell is higher than or equal to this threshold, handover
services with a QCI of 3 are admitted.
If the QoS satisfaction rate of these services is lower than
this threshold, handover services with a QCI of 3 are not
admitted.
The value 90 is recommended.

QCI4 handover admission threshold CellRacThd.Qci4HoThd Network plan (negotiation not required) This parameter specifies the handover admission threshold for QCI 4.
The parameter applies to both uplink and downlink.
If the QoS satisfaction rate of services with a QCI of 4 in
the cell is higher than or equal to this threshold, handover
services with a QCI of 4 are admitted.
If the QoS satisfaction rate of these services is lower than

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

this threshold, handover services with a QCI of 4 are not


admitted.
The value 90 is recommended.

Gold new service admission threshold offset CellRacThd.NewGoldServiceOffset Network plan (negotiation not required) This parameter specifies admission offset for new gold-level services.
The parameter applies to both uplink and downlink.
New gold-level services and handover services with a
specific QCI are admitted if the following conditions are
both met:
The QoS satisfaction rate of services with this QCI is
higher than or equal to the sum of this offset and the
admission threshold for handover services with this QCI.
The QoS satisfaction rates of all other QCIs are higher
than the corresponding handover admission thresholds.
New services are not admitted if the QoS satisfaction rate
of any QCI is lower than the corresponding handover
admission threshold.
The value 5 is recommended.

Silver new service admission threshold offset CellRacThd.NewSilverServiceOffset Network plan (negotiation not required) This parameter specifies admission offset for new silver-level
services. The parameter applies to both uplink and downlink.
New silver-level services and handover services with a
specific QCI are admitted if the following conditions are
both met:
The QoS satisfaction rate of services with this QCI is
higher than or equal to the sum of this offset and the
admission threshold for handover services with this QCI.
The QoS satisfaction rates of all other QCIs are higher
than the corresponding handover admission thresholds.
New services with a specific QCI are not admitted if the
QoS satisfaction rate of any QCI is lower than the
corresponding handover admission threshold.
The value 5 is recommended.

Bronze new service admission threshold offset CellRacThd.NewCopperServiceOffset Network plan (negotiation not required) This parameter specifies admission offset for new bronze-level
services. The parameter applies to both uplink and downlink.
New bronze-level services and handover services with a
specific QCI are admitted if the following conditions are
both met:
The QoS satisfaction rate of services with this QCI is
higher than or equal to the sum of this offset and the
admission threshold for handover services with this QCI.
The QoS satisfaction rates of all other QCIs are higher
than the corresponding handover admission thresholds.
New services with a specific QCI are not admitted if the
QoS satisfaction rate of any QCI is lower than the
corresponding handover admission threshold.
The value 5 is recommended.

Uplink RB used ratio high threshold CellRacThd.UlRbHighThd Network plan (negotiation not required) This parameter specifies the threshold for deciding whether the uplink
resource block (RB) usage is high. If the MAC layer reports that the
uplink RB usage is greater than this parameter value, the uplink RB
usage is regarded to be high. This threshold is used in uplink
admission decisions.
The value 95 is recommended.

Uplink RB used ratio low threshold CellRacThd.UlRbLowThd Network plan (negotiation not required) This parameter specifies the threshold for deciding whether the uplink
RB usage is low. If the MAC layer reports that the uplink RB usage is
less than this parameter value, the uplink RB usage is regarded to be
low. This threshold is used in uplink admission decisions.
The value 90 is recommended.

Scenario 2: Service Preemption


This section describes data preparation for radio resource preemption. For details about data preparation for transport resource preemption, see Transport Resource Management Feature Parameter Description.
Before collecting the parameters for enabling and configuring service preemption, collect the parameters in CellAlgoSwitch MOs for enabling admission based on QoS satisfaction rates. For the parameters for enabling admission based on QoS satisfaction rates, see scenario 1 in "Scenario-specific Data."
The following table describes the parameters that must be set in CellAlgoSwitch MOs to enable service preemption.

Parameter Name Parameter ID Data Source Setting Notes

Local cell ID CellAlgoSwitch.LocalCellId Network plan (negotiation not required) This parameter specifies the local ID of a cell. It uniquely identifies a
cell within an eNodeB.
Set this parameter based on the network plan.

RAC algorithm switch CellAlgoSwitch.RacAlgoSwitch Network plan (negotiation not required) PreemptionSwitch(PreemptionSwitch) under this parameter
specifies whether to enable service preemption.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

If the PreemptionSwitch(PreemptionSwitch) check box is


selected, new higher-priority services that have failed to be
admitted can preempt the admitted lower-priority services
in the cell.
If the PreemptionSwitch(PreemptionSwitch) check box is
cleared, only emergency calls can be admitted to the cell.

Scenario 3: Intra-operator User-Number-based Preemption


The following table describes the parameter that must be set in the EnodeBAlgoSwitch MO to enable intra-operator user-number-based preemption.

Parameter Name Parameter ID Data Source Setting Notes

UE number preemption switch ENodeBAlgoSwitch.UeNumPreemptSwitch Network plan (negotiation not required) This parameter specifies whether to enable or disable user-number-based preemption.
If the IntraOpUeNumPreemptSwitch option is selected, when a user cannot access the network because of the
user number restriction, the user can preempt resources of other lower-priority users served by the same
operator. If this option is not selected, preemption is not allowed.

Scenario 4: User-Number-Reservation-based Admission Control of Privileged UEs


The following table describes the parameter that must be set in the CellRacThd MO to enable user-number-reservation-based admission control of privileged UEs.

Parameter Name Parameter ID Data Source Setting Notes

Admission Control Reserved User Number CellRacThd.AcReservedUserNumber Network plan (negotiation not required) This parameter specifies the UE numbers reserved for privileged UEs. If this parameter is set to 0, no UE
numbers are reserved for privileged UEs. A non-zero value of this parameter indicates the maximum UE
numbers reserved for privileged UEs. A larger value of this parameter indicates a larger UE number reserved for
privileged UEs and a smaller UE number available for common UEs. The parameter value 0 is recommended.

Scenario 5: ARP Configuration for Common UEs Initiating CSFB Procedures


The following table describes the parameters that must be set in the CSFallBackPolicyCfg MO to configure ARPs for common UEs initiating CSFB procedures.

Parameter Name Parameter ID Data Source Setting Notes

Csfb User Arp Configuration Switch CSFallBackPolicyCfg.CsfbUserArpCfgSwitch Network plan (negotiation not required) This parameter specifies whether the ARPs for common UEs initiating CSFB procedures can be configured.
The parameter value OFF(Off) is recommended.

Normal Csfb User Arp CSFallBackPolicyCfg.NormalCsfbUserArp Network plan (negotiation not required) This parameter specifies the ARP for common UEs initiating CSFB procedures. If this parameter is set to 1, the
ARP for these UEs is the same as that for emergency UEs initiating CSFB procedures. The parameter value 2
is recommended.

7.4.3 Activation
sing the CME to Perform Batch Configuration for Newly Deployed eNodeBs

When using a summary data file to configure feature data and the data for new eNodeBs to be deployed, see "Creating eNodeBs in Batches" in the relevant eNodeB initial configuration guide, which is available in the eNodeB product documentation.
Enter the values of the parameters listed in Table 7-1, Table 7-2, Table 7-3, Table 7-4, and Table 7-5 in a summary data file, which also contains other data for new eNodeBs to be deployed. Then, import the summary data file into the Configuration Management Express (CME) for batch configuration.
The summary data file may be a scenario-specific file provided by the CME or a customized file, depending on the following conditions:

The managed objects (MOs) in Table 7-1, Table 7-2, Table 7-3, Table 7-4, or Table 7-5 are contained in a scenario-specific summary data file. In this situation, set the parameters in the MOs, and then verify the parameter settings and save the file.
Some MOs in Table 7-1, Table 7-2, Table 7-3, Table 7-4, or Table 7-5 are not contained in a scenario-specific summary data file. In this situation, customize a summary data file to include the MOs before setting the parameters.

Table 7-1 Parameters for admission based on QoS satisfaction rates

MO Sheet in the Summary Data File Parameter Group Remarks

CellAlgoSwitch CellAlgoSwitch Local cell ID, RAC algorithm switch User-defined template

CellRacThd CellRacThd Local cell ID, Gold service arp threshold, Silver service arp threshold, QCI1 handover admission threshold (%), User-defined template
QCI2 handover admission threshold (%), QCI3 handover admission threshold (%), QCI4 handover admission
threshold (%), Gold new service admission threshold offset (%), Silver new service admission threshold offset (%),
Copper new service admission threshold offset (%), Uplink RB used ratio high threshold(%), Uplink RB used ratio
low threshold (%)

Table 7-2 Parameters for service preemption

MO Sheet in the Summary Data File Parameter Group Remarks

CellAlgoSwitch CellAlgoSwitch Local cell ID, RAC algorithm switch User-defined template

CellRacThd CellRacThd Local cell ID, Gold service arp threshold, Silver service arp threshold, QCI1 User-defined template
handover admission threshold (%), QCI2 handover admission threshold (%),
QCI3 handover admission threshold(%), QCI4 handover admission
threshold(%), Gold new service admission threshold offset(%), Silver new
service admission threshold offset(%), Copper new service admission
threshold offset(%), Uplink RB used ratio high threshold(%), Uplink RB used
ratio low threshold(%)

Table 7-3 Parameters for intra-operator preemption based on the number of UEs

MO Sheet in the Summary Data File Parameter Group Remarks

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

ENodeBAlgoSwitch ENodeBAlgoSwitch UE number preemption switch User-defined template

Table 7-4 Parameters for admission control of privileged UEs based on reserved resources

MO Sheet in the Summary Data File Parameter Group Remarks

CellRacThd CellRacThd Admission Control Reserved User Numbers User-defined template

Table 7-5 Parameters for ARP configuration for common UEs initiating CSFB procedures when the number of UEs to be admitted is limited

MO Sheet in the Summary Data File Parameter Group Remarks

CsFallbackPolicyCfg CsFallbackPolicyCfg Csfb User Arp Configure Switch, Normal Csfb User Arp User-defined template

sing the CME to Perform Batch Configuration for Existing eNodeBs

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.

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 choose Managing the CME > CME Guidelines > LTE Application Management >
eNodeB Related Operations > Customizing a Summary Data File for Batch eNodeB Configuration.
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 eNodeB data stored on the CME into a customized summary data
file.
3. In the summary data file, set the parameters in the MOs according to the setting notes provided in section "Data Preparation" and close the file.
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 verifying data.
5. 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.

sing the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB. The procedure is as follows:

1. In the planned data area, click Base Station in the upper left corner of the configuration window.
2. In area 1 shown in Figure 7-1, select the eNodeB to which the MOs belong.
Figure 7-1 MO search and configuration window

3. On the Search tab page in area 2, enter an MO name, for example, CELL.
4. In area 3, double-click the MO in the Object Name column. All parameters in this MO are displayed in area 4.
5. Set the parameters in area 4 or 5.
6. In the planned data area, choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts.

sing MML Commands

Scenario 1: Admission Based on QoS Satisfaction Rates

1. Run the MOD CELLALGOSWITCH command to enable uplink and downlink admission control based on QoS satisfaction rates.
2. Run the MOD CELLRACTHD command to configure admission control.

Scenario 2: Service Preemption

1. Run the MOD CELLALGOSWITCH command to enable uplink and downlink admission control based on QoS satisfaction rates, and then to enable service preemption.
2. Run the MOD CELLRACTHD command to configure admission control.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

Scenario 3: Intra-operator Preemption Based on the Number of UEs


Run the MOD ENODEBALGOSWITCH command to enable intra-operator user-number-based preemption.
Scenario 4: Admission Control of Privileged UEs Based on Reserved Resources
Run the MOD CELLRACTHD command to set the number of UEs reserved for admission control.
Scenario 5: ARP Configuration for Common UEs Initiating CSFB Procedures When the Number of UEs to Be Admitted Is Limited
Run the MOD CSFALLBACKPOLICYCFG command to turn on the switch for configuring ARP for common UEs initiating CSFB procedures and to configure the ARPs for common UEs initiating CSFB procedures.

ML Command Examples

Enabling Admission Control Based on QoS Satisfaction Rates


MOD CELLALGOSWITCH: LocalCellId=0, RacAlgoSwitch=DlSwitch-1&UlSwitch-1;

Enabling Service Preemption


MOD CELLALGOSWITCH: LocalCellId=0, RacAlgoSwitch=PreemptionSwitch-1;
Configuring Admission Control
MOD CELLRACTHD: LocalCellId=0, GoldServiceArpThd=5, SilverServiceArpThd=10, Qci1HoThd=80, Qci2HoThd=80, Qci3HoThd=80, Qci4HoThd=80, NewGoldServiceOffset=5, NewSilverServiceOffset=5, NewCopperServiceOffset=5, UlRbHighThd=90,
UlRbLowThd=80;

Enabling Intra-operator Preemption Based on the Number of UEs


MOD ENODEBALGOSWITCH:UeNumPreemptSwitch=IntraOpUeNumPreemptSwitch-1;
Enabling Admission Control of Privileged UEs Based on Reserved Resources
MOD CELLRACTHD:LocalCellId=0,AcReservedUserNumber=15;
Enabling ARP Configuration for Common UEs Initiating CSFB Procedures When the Number of UEs to Be Admitted Is Limited
MOD CSFALLBACKPOLICYCFG:CSFBUSERARPCFGSWITCH=ON,NORMALCSFBUSERARP=2;

7.4.4 Activation Observation


enario 1: Admission Based on QoS Satisfaction Rates

The verification procedure is as follows:

1. On the U2000 client, start S1 interface tracing and start monitoring on the following items: QoS satisfaction rate, RB usage, and the number of services.

a. Choose Monitor > Signaling Trace > Signaling Trace Management.


b. In the navigation tree on the left of the Signaling Trace Management window:

Choose LTE > Application Layer > S1 Interface Trace to create an S1 interface tracing task.
Choose LTE > Cell Performance Monitoring > Satisfaction of Service Monitoring to create a task for monitoring QoS satisfaction rates.
Choose LTE > Cell Performance Monitoring > Usage of RB Monitoring to create a task for monitoring RB usage.
Choose LTE > Cell Performance Monitoring > Service Statistic Monitoring to create a task for monitoring the number of services.

2. Use UEs to access a cell, and perform GBR services with a QCI in the range of 2 to 4 on the UEs. Move some UEs to the cell center and increase the GBR traffic volume on these UEs until the MAC layer reports that the uplink RB usage is higher than CellRacThd.UlRbHighThd. (The PRB usage of GBR
services can be deduced from the results of RB usage monitoring.) Then, move some other UEs to the cell edge until the QoS satisfaction rate of the GBR services on these UEs falls below the admission threshold for this QCI.
3. Initiate new GBR services with a QCI in the range of 2 to 4.
4. Check the S1AP_ERAB_SETUP_REQ and S1AP_ERAB_SETUP_RSP messages in the S1 interface tracing result.
If the cause value for E-RAB setup failures is "radioNetwork: radio-resources-not-available" in the S1AP_ERAB_SETUP_RSP messages, as shown in Figure 7-2, or if the number of services does not increase with the S1AP_ERAB_SETUP_REQ messages, the new GBR service requests have been rejected.

Figure 7-2 S1AP_ERAB_SETUP_RSP message that indicates failed admission based on satisfaction rates

enario 2: Service Preemption

In this scenario, two GBR services (A and B) are involved. GBR service A has a QCI of 3 and an ARP value of 7, and GBR service B has a QCI of 4 and an ARP value greater than 7. The GBR service with a larger ARP value has a lower priority. Both GBR services can preempt other services and can be preempted.
To check whether a service can preempt other services or can be preempted, observe the S1AP_ERAB_SETUP_REQ message in the S1 interface tracing result. In this message for GBR service A, as shown in Figure 7-3, the value 1 (may-trigger-pre-emption) of the IE pre-emptionCapability indicates that the service
can preempt other services and the value 1 (pre-emptable) of the IE pre-emptionVulnerability indicates that the service can be preempted. The value 0 indicates the opposite.

Figure 7-3 S1AP_ERAB_SETUP_REQ message that includes the ARP value and the preemption attributes

The verification procedure is as follows:

1. On the U2000 client, start S1 interface tracing and start monitoring on the following items: QoS satisfaction rate, RB usage, and the number of services.

a. Choose Monitor > Signaling Trace > Signaling Trace Management.


b. In the navigation tree on the left of the Signaling Trace Management window:

Choose LTE > Application Layer > S1 Interface Trace to create an S1 interface tracing task.
Choose LTE > Cell Performance Monitoring > Satisfaction of Service Monitoring to create a task for monitoring QoS satisfaction rates.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

Choose LTE > Cell Performance Monitoring > Usage of RB Monitoring to create a task for monitoring RB usage.
Choose LTE > Cell Performance Monitoring > Service Statistic Monitoring to create a task for monitoring the number of services.

2. Use UEs to access a cell, and perform GBR service B on some UEs.
3. Perform GBR service A on some other UEs. Follow the operation in 2 for scenario 1 in 7.4.4 Activation Observation so that requests for GBR service A are first rejected due to admission based on QoS satisfaction rates.
4. Monitor S1 signaling to verify that GBR service A preempts GBR service B. GBR service B is released, as shown in Figure 7-4. Follow the operation in 4 for scenario 1 in 7.4.4 Activation Observation to verify that GBR service A has been successfully admitted to the cell.

Figure 7-4 S1AP_ERAB_REL_IND message that indicates successful preemption

enario 3: Intra-operator User-Number-based Preemption

If intra-operator user-number-based preemption is enabled and all users can both be preempted and preempt other users, users with high ARPs can preempt users with low ARPs to access the cell when the number of users has reached the licensed value.
The verification procedure is as follows:

1. On the U2000 client, choose Monitor > Signaling Trace > Signaling Trace Management.
2. In the navigation tree on the left of the Signaling Trace Management window, choose LTE > Application Layer > S1 Interface Trace to create an S1 interface tracing task.
3. Apply for a license in which the number of RRC_CONNECTED users is 6, and select the IntraOpUeNumPreemptSwitch(IntraOpUeNumPreemptSwitch) check box under the EnodeBAlgoSwitch.UeNumPreemptSwitch parameter.
4. Enable a UE that meets the following requirements to access the network:
The ARP value for the default bearer is 7.
The ARP IE "pre-emption vulnerability" is set to "pre-emptable" for the default bearer.

5. Enable five UEs that meet the following requirements to access the network:
The UEs and the previous UE are served by the same operator.
The ARP value for the default bearer is 6.
The ARP IE "pre-emption vulnerability" is set to "pre-emptable" for the default bearer.

6. Enable another UE that meets the following requirements to access the network:
The UE and the previous UEs are served by the same operator.
The ARP value for the default bearer is 1.
The ARP IE "pre-emption capability" is set to "may trigger pre-emption" for the default bearer.

7. Monitor S1 signaling to verify that the second UE successfully preempts the resources allocated to the first UE. The first UE is released, as shown in Figure 7-5.
Figure 7-5 S1AP_UE_ CONTEXT_REL_REQ message that indicates successful preemption

7.4.5 Deactivation
sing 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 Using the CME to
Perform Batch Configuration for Existing eNodeBs. In the procedure, modify parameters according to Table 7-6, Table 7-7, Table 7-8, Table 7-9, and Table 7-10.

Table 7-6 Parameters for admission based on QoS satisfaction rates

MO Sheet in the Summary Data File Parameter Group Setting Notes

CellAlgoSwitch CellAlgoSwitch Local cell ID, RAC algorithm switch Turn off the switches that control admission control based on
satisfaction rates.

Table 7-7 Parameters for service preemption

MO Sheet in the Summary Data File Parameter Group Setting Notes

CellAlgoSwitch CellAlgoSwitch Local cell ID, RAC algorithm switch Turn off the service preemption switch.

Table 7-8 Parameters for intra-operator user-number-based preemption

MO Sheet in the Summary Data File Parameter Group Setting Notes

ENodeBAlgoSwitch EnodeBAlgoSwitch UE number preemption switch Turn off the switch that controls user-number-based preemption.

Table 7-9 Parameters for user-number-reservation-based admission control of privileged UEs

MO Sheet in the Summary Data File Parameter Group Setting Notes

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

CellRacThd CellRacThd Admission Control Reserved User Numbers Disable user-number-reservation-based admission control of privileged UEs by setting this parameter to 0.

Table 7-10 Parameters for ARP configuration for common UEs initiating CSFB procedures in scenarios where the number of UEs allowed to be admitted is limited

MO Sheet in the Summary Data File Parameter Group Setting Notes

CsFallbackPolicyCfg CsFallbackPolicyCfg Csfb User Arp Configure Switch Disable ARP configuration for common UEs initiating CSFB procedures in scenarios where
the number of UEs allowed to be admitted is limited.

sing the CME to Perform Single Configuration

On the CME, set parameters according to Table 7-6, Table 7-7, Table 7-8, Table 7-9, and Table 7-10. For detailed instructions, see Using the CME to Perform Single Configuration described for feature activation.

sing MML Commands

Scenario 1: Admission Based on QoS Satisfaction Rates


Run the MOD CELLALGOSWITCH command to disable uplink and downlink admission control based on QoS satisfaction rates.
Scenario 2: Service Preemption

1. Run the MOD CELLALGOSWITCH command to disable uplink and downlink admission control based on QoS satisfaction rates.
2. Run the MOD CELLALGOSWITCH command to disable service preemption.

Scenario 3: Intra-operator User-Number-based Preemption


Run the MOD ENODEBALGOSWITCH command to disable intra-operator user-number-based preemption.
Scenario 4: User-Number-Reservation-based Admission Control of Privileged UEs
Run the MOD CELLRACTHD command to disable user-number-reservation-based admission control of privileged UEs.
Scenario 5: ARP Configuration for Common UEs Initiating CSFB Procedures in Scenarios Where the Number of Users Allowed to Be Admitted Is Limited
Run the MOD CSFALLBACKPOLICYCFG command to disable ARP configuration for common UEs initiating CSFB procedures.

ML Command Examples

Disabling Admission Control Based on QoS Satisfaction Rates


MOD CELLALGOSWITCH: LocalCellId=0, RacAlgoSwitch=DlSwitch-0&UlSwitch-0;

Disabling Service Preemption


MOD CELLALGOSWITCH: LocalCellId=0, RacAlgoSwitch=PreemptionSwitch-0;

Disabling Intra-operator User-Number-based Preemption


MOD ENODEBALGOSWITCH: UeNumPreemptSwitch=IntraOpUeNumPreemptSwitch-0;

Disabling User-Number-Reservation-based Admission Control of Privileged UEs


MOD CELLRACTHD: LocalCellId=0, AcReservedUserNumber=0;
Disabling ARP Configuration for Common UEs Initiating CSFB Procedures in Scenarios Where the Number of Users Allowed to Be Admitted Is Limited
MOD CSFALLBACKPOLICYCFG: CsfbUserArpCfgSwitch=0;

5 Deployment of Congestion Control

7.5.1 Deployment Requirements


ature

For details, see 5.3 Features Related to LBFD-002024 Congestion Control in the section "Impacted Features".

ardware

None

cense

Congestion control does not have requirements for the operating environment, transmission networking, and licenses.

her Requirements

As required by congestion control for the EPC,


only the services whose ARP-related IE pre-emptionVulnerability is "pre-emptable" can be released if the switch specified by DlLdcSwitch(dlLdcSwitch) or UlLdcSwitch(ulLdcSwitch) is turned on. Therefore, the IE pre-emptionVulnerability must be set to "pre-emptable" in the EPC.

7.5.2 Data Preparation


equired Data

The following table describes the parameters that must be set in CellAlgoSwitch MOs to enable the congestion control algorithms.

Parameter Name Parameter ID Data Source Setting Notes

Local cell ID CellAlgoSwitch.LocalCellId Network plan (negotiation not required) This parameter specifies the local ID of a cell. It uniquely identifies a
cell within an eNodeB.
Set this parameter based on the network plan.

RAC algorithm switch CellAlgoSwitch.RacAlgoSwitch Network plan (negotiation not required) To enable downlink congestion detection, select the
DlLdcSwitch(dlLdcSwitch) check box. If congestion is
detected, congestion relief actions are taken.
To disable downlink congestion detection, clear the

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

DlLdcSwitch(dlLdcSwitch) check box. Then, downlink


congestion in the cell, if any, cannot be relieved.
To enable uplink congestion detection, select the
UlLdcSwitch(ulLdcSwitch) check box. If congestion is
detected, congestion relief actions are taken.
To disable uplink congestion detection, clear the
UlLdcSwitch(ulLdcSwitch) check box. Then, uplink
congestion in the cell, if any, cannot be relieved.

enario-specific Data

The following table describes the parameters that must be set in CellRacThd MOs to configure the congestion control algorithms.

Parameter Name Parameter ID Data Source Setting Notes

Local cell ID CellRacThd.LocalCellId Network plan (negotiation not required) This parameter specifies the local ID of a cell. It uniquely identifies a
cell within an eNodeB.
Set this parameter based on the network plan.

QCI1 congest threshold CellRacThd.Qci1CongThd Network plan (negotiation not required) This parameter specifies the congestion threshold for services with a
QCI of 1. It applies to both uplink and downlink.
If the QoS satisfaction rate of services with a QCI of 1 in
the cell is lower than this threshold, these services enter
the congested state.
If the QoS satisfaction rate of these services is higher than
the sum of this threshold and CellRacThd.CongRelOffset,
these services exit the congested state.
The value 65 is recommended.

QCI2 congest threshold CellRacThd.Qci2CongThd Network plan (negotiation not required) This parameter specifies the congestion threshold for services with a
QCI of 2. It applies to both uplink and downlink.
If the QoS satisfaction rate of services with a QCI of 2 in
the cell is lower than this threshold, these services enter
the congested state.
If the QoS satisfaction rate of these services is higher than
the sum of this threshold and CellRacThd.CongRelOffset,
these services exit the congested state.
The value 65 is recommended.

QCI3 congest threshold CellRacThd.Qci3CongThd Network plan (negotiation not required) This parameter specifies the congestion threshold for services with a
QCI of 3. It applies to both uplink and downlink.
If the QoS satisfaction rate of services with a QCI of 3 in
the cell is lower than this threshold, these services enter
the congested state.
If the QoS satisfaction rate of these services is higher than
the sum of this threshold and CellRacThd.CongRelOffset,
these services exit the congested state.
The value 65 is recommended.

QCI4 congest threshold CellRacThd.Qci4CongThd Network plan (negotiation not required) This parameter specifies the congestion threshold for services with a
QCI of 4. It applies to both uplink and downlink.
If the QoS satisfaction rate of services with a QCI of 4 in
the cell is lower than this threshold, these services enter
the congested state.
If the QoS satisfaction rate of these services is higher than
the sum of this threshold and CellRacThd.CongRelOffset,
these services exit the congested state.
The value 65 is recommended.

Offset for service congest relieving CellRacThd.CongRelOffset Network plan (negotiation not required) This parameter specifies the congestion relief offset.
If the QoS satisfaction rate of services with a specific QCI
in the cell is higher than the sum of this offset and the
congestion threshold for that QCI, these services exit the
congested state.
If the QoS satisfaction rate of these services is lower than
the sum of this offset and the congestion threshold for that
QCI, these services remain in the congested state.
The value 20 is recommended.

Uplink RB used ratio high threshold CellRacThd.UlRbHighThd Network plan (negotiation not required) This parameter specifies the threshold for deciding whether the uplink
RB usage is high. If the MAC layer reports that the uplink RB usage is
greater than this parameter value, the uplink RB usage is regarded to
be high. This threshold is used in uplink admission decisions.
The value 95 is recommended.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

Uplink RB used ratio low threshold CellRacThd.UlRbLowThd Network plan (negotiation not required) This parameter specifies the threshold for deciding whether the uplink
RB usage is low. If the MAC layer reports that the uplink RB usage is
less than this parameter value, the uplink RB usage is regarded to be
low. This threshold is used in uplink admission decisions.
The value 90 is recommended.

7.5.3 Activation
sing the CME to Perform Batch Configuration for Newly Deployed eNodeBs

Enter the values of the parameters listed in Table 7-11 in a summary data file, which also contains other data for the new eNodeBs to be deployed. Then, import the summary data file 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:
The summary data file may be a scenario-specific file provided by the CME or a customized file, depending on the following conditions:

The MOs in Table 7-11 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.
Some MOs in Table 7-11 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 7-11 Parameters for congestion control

MO Sheet in the Summary Data File Parameter Group Remarks

CellAlgoSwitch CellAlgoSwitch Local cell ID, RAC algorithm switch User-defined template

CellRacThd CellRacThd Local cell ID, QCI1 congest threshold(%), QCI2 congest threshold(%), QCI3 congest threshold(%), QCI4 User-defined template
congest threshold(%), Offset for service congest relieving(%), Uplink RB used ratio high threshold(%),
Uplink RB used ratio low threshold(%)

sing the CME to Perform Batch Configuration for Existing eNodeBs

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.

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.
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.
3. In the summary data file, set the parameters in the MOs according to the setting notes provided in section "Data Preparation" and close the file.
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.
5. 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.

sing the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB. The procedure is as follows:

1. In the planned data area, click Base Station in the upper left corner of the configuration window.
2. In area 1 shown in Figure 7-6, select the eNodeB to which the MOs belong.
Figure 7-6 MO search and configuration window

3. On the Search tab page in area 2, enter an MO name, for example, CELL.
4. In area 3, double-click the MO in the Object Name column. All parameters in this MO are displayed in area 4.
5. Set the parameters in area 4 or 5.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

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.

sing MML Commands

1. Run the MOD CELLALGOSWITCH command to enable uplink and downlink congestion control.
2. Run the MOD CELLRACTHD command to configure congestion control.

ML Command Examples

MOD CELLALGOSWITCH: LocalCellId=0, RacAlgoSwitch=DlLdcSwitch-1&UlLdcSwitch-1;


MOD CELLRACTHD: LocalCellId=0, Qci1CongThd=65, Qci2CongThd=65, Qci3CongThd=65, Qci4CongThd=65, UlRbHighThd=95, UlRbLowThd=90;

7.5.4 Activation Observation


The verification procedure is as follows:

1. On the U2000 client, start S1 interface tracing and start monitoring on the following items: QoS satisfaction rate, RB usage, and the number of services.

a. Choose Monitor > Signaling Trace > Signaling Trace Management.


b. In the navigation tree on the left of the Signaling Trace Management window:

Choose LTE > Application Layer > S1 Interface Trace to create an S1 interface tracing task.
Choose LTE > Cell Performance Monitoring > Satisfaction of Service Monitoring to create a task for monitoring QoS satisfaction rates.
Choose LTE > Cell Performance Monitoring > Usage of RB Monitoring to create a task for monitoring RB usage.
Choose LTE > Cell Performance Monitoring > Service Statistic Monitoring to create a task for monitoring the number of services.

2. Use UEs to access a cell, and perform GBR services with a QCI in the range of 2 to 4 on the UEs. Move some UEs to the cell center and increase the GBR traffic volume on these UEs until the MAC layer reports that the uplink RB usage is higher than CellRacThd.UlRbHighThd. (The PRB usage of GBR
services can be deduced from the results of RB usage monitoring.) Then, move some other UEs to the cell edge until the QoS satisfaction rate of the GBR services on these UEs falls below the congestion threshold for this QCI.
3. Check the S1 interface tracing result for the S1AP_ERAB_REL_IND message.
If the release cause value is "radioNetwork: reduce-load-in-serving-cell" in the S1AP_ERAB_REL_IND message, as shown in Figure 7-7, the indicated low-priority service has been released as expected.

Figure 7-7 S1AP_ERAB_REL_IND message that indicates the release of a low-priority service

7.5.5 Deactivation
sing 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 Using the CME to
Perform Batch Configuration for Existing eNodeBs. In the procedure, modify parameters according to Table 7-12.

Table 7-12 Parameters for congestion control

MO Sheet in the Summary Data File Parameter Group Setting Notes

CellAlgoSwitch CellAlgoSwitch Local cell ID, RAC algorithm switch Turn off the switches that control uplink and downlink congestion
control.

sing the CME to Perform Single Configuration

On the CME, set parameters according to Table 7-12. For detailed instructions, see Using the CME to Perform Single Configuration described for feature activation.

sing MML Commands

Run the MOD CELLALGOSWITCH command to disable uplink and downlink congestion control.

ML Command Examples

MOD CELLALGOSWITCH: LocalCellId=0, RacAlgoSwitch=DlLdcSwitch-0&UlLdcSwitch-0;

6 Performance Monitoring
Admission and congestion control involves RRC connection management and bearer management.

dmission Control

If the licensed UE numbers, UE number specifications, or PUCCH resources are limited, the eNodeB does not allow new UEs to access the cell or UEs to be handed over to the cell, and the RRC connections for these UEs fail to be established. The RRC connection congestion rate increases.
If resources in the cell are insufficient, the eNodeB may reject the access requests of new bearers and incoming handover bearers, and E-RABs fail to be set up. The E-RAB congestion rate increases. The initial E-RAB congestion rate monitors new bearers that fail to be admitted. Table 7-13 lists the methods for
calculating the three measurement indicators.

Table 7-13 Congestion rate calculation

Measurement Indicator Formula

RRC congestion rate 1 - (L.RRC.ConnReq.Succ - L.Cell.UserSpec.PrepEmp.PrepAtt.Num - L.Cell.UserLic.Limit.Num)/L.RRC.ConnReq.Msg

E-RAB congestion rate 1 - L.E-RAB.SuccEst/L.E-RAB.AttEst

Initial E-RAB congestion rate 1-L.E-RAB.InitSuccEst/L.E-RAB.InitAttEst

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

NOTE:
Counters in RRC.SetupFail.Cell monitor reasons of RRC connection setup failures.
Counters in E-RAB.EstFail.Cell monitor reasons of E-RAB setup failures.
The L.Cell.UserLic.Limit.Num.PLMN counter monitors the number of times that the licensed number of UEs is limited for a specific operator.

eemption

After preemption is activated, UEs establish RRC connections first, and then trigger preemption. If a UE fails the preemption, the RRC connection for this UE is released. If the preemption is successful, the RRC connection for the UE whose resources are preempted is released. The
L.Cell.UserSpec.PrepEmp.PrepAtt.Num counter measures the number of released RRC connections.
The following counters measure the number of RRC connections of UEs that successfully preempt resources of other UEs:

L.Cell.UserLimit.PreEmp.Num
L.Cell.UserLic.PrepEmp.Succ.Num
L.Cell.UserLic.PrepEmp.Succ.Num.PLMN

The L.E-RAB.AbnormRel.Cong counter measures the number of bearers abnormally released in the case of congestion, including bearers released due to preemption and bearers released due to congestion control.

ongestion Control

During congestion control, the L.LC.ULCong.Dur.Cell and L.LC.DLCong.Dur.Cell counters measure the uplink congestion time and downlink congestion time, respectively. The L.LC.ULCong.Num.Cell and L.LC.DLCong.Num.Cell counters measure the number of times uplink congestion and downlink congestion occur in a
cell, respectively. The L.LC.User.Rel counter measures the number of bearers released due to congestion control.
If redirection is performed, the L.RRCRedirection.IntraLTE counter measures the number of redirections.

7 Parameter Optimization
The L.Traffic.Privilege.User.max and L.Traffic.Privilege.User.avg counters measure the maximum number and the average number of privileged UEs in a cell, respectively. In scenarios where user-number-reservation-based admission control of privileged UEs is enabled, if the CellRacThd.AcReservedUserNumber
parameter is set to an extremely large value, the number of common UEs that can access the cell is small; if the CellRacThd.AcReservedUserNumber parameter value is set to an extremely small value, the user number resources reserved for privileged UEs may be insufficient. Therefore, the
CellRacThd.AcReservedUserNumber parameter settings must be adjusted based on the values of the L.Traffic.Privilege.User.max and L.Traffic.Privilege.User.avg counters.

8 Troubleshooting

7.8.1 Admission Control


ult Description

High-priority services fail to preempt low-priority services.

ult Handling

1. Check whether the IE priorityLevel in the S1AP_ERAB_SETUP_REQ message, as shown in Figure 7-8, of the service to be preempted is greater than that of the preempting service.
If yes, go to 2.
If no, change the values accordingly at the EPC.

Figure 7-8 Checking the ARP value

2. Check the same message to observe whether: (1) The value of the IE pre-emptionCapability is 1 for the preempting service; (2) The value of the IE pre-emptionVulnerability is 1 for the service to be preempted.
If either of the two values is 0, change the service attributes accordingly at the EPC.
If both values are 1, contact Huawei technical support for further troubleshooting.

7.8.2 Congestion Control


None

8 Parameters

Table 8-1 Parameters

MO Parameter ID MML Command Feature ID Feature Name Description

CellRacThd AcReservedUserNumber MOD CELLRACTHD LBFD-002023 / TDLBFD- Admission Control Meaning: Indicates the UE numbers reserved for UEs initiating emergency calls and high-priority UEs. If this parameter is set to 0, no UE
LST CELLRACTHD 002023 number is reserved for UEs initiating emergency calls and high-priority UEs. A non-zero value of this parameter represents the maximum UE
number reserved for UEs initiating emergency calls and high-priority UEs.
GUI Value Range: 0~30
Unit: None
Actual Value Range: 0~30
Default Value: 0

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

CellRacThd NewGoldServiceOffset MOD CELLRACTHD LBFD-002023 / TDLBFD- Admission Control Meaning: Indicates the offset for admission of new gold-level services. This parameter applies to both downlink and uplink. New gold-level
LST CELLRACTHD 002023 services and handed-over services with QCI N are admitted if both the following conditions are met: (1) The satisfaction rate of services with
QCI N is higher than or equal to the sum of this offset and the admission threshold for the handed-over services with QCI N. (2) The
satisfaction rate of services with any other QCI is higher than or equal to the corresponding admission threshold for the handed-over
services with that QCI.
GUI Value Range: 0~90
Unit: %
Actual Value Range: 0~90
Default Value: 5

CellRacThd NewSilverServiceOffset MOD CELLRACTHD LBFD-002023 / TDLBFD- Admission Control Meaning: Indicates the offset for admission of new silver-level services. This parameter applies to both downlink and uplink. New silver-level
LST CELLRACTHD 002023 services and handed-over services with QCI N are admitted if both the following conditions are met: (1) The satisfaction rate of services with
QCI N is higher than or equal to the sum of this offset and the admission threshold for the handed-over services with QCI N. (2) The
satisfaction rate of services with any other QCI is higher than or equal to the corresponding admission threshold for the handed-over
services with that QCI.
GUI Value Range: 0~90
Unit: %
Actual Value Range: 0~90
Default Value: 5

CellRacThd NewCopperServiceOffset MOD CELLRACTHD LBFD-002023 / TDLBFD- Admission Control Meaning: Indicates the offset for admission of new bronze-level services. This parameter applies to both downlink and uplink. New bronze-
LST CELLRACTHD 002023 level services and handed-over services with QCI N are admitted if both the following conditions are met: (1) The satisfaction rate of services
with QCI N is higher than or equal to the sum of this offset and the admission threshold for the handed-over services with QCI N. (2) The
satisfaction rate of services with any other QCI is higher than or equal to the corresponding admission threshold for the handed-over
services with that QCI.
GUI Value Range: 0~90
Unit: %
Actual Value Range: 0~90
Default Value: 5

CellRacThd GoldServiceArpThd MOD CELLRACTHD LBFD-002023 / TDLBFD- Admission Control Meaning: Indicates the Allocation and Retention Priority (ARP) threshold for the Golden-level services. A service is defined as a Golden-level
LST CELLRACTHD 002023 service if its ARP value is smaller than or equal to this threshold. The service priority has a negative correlation with the ARP value.
GUI Value Range: 1~15
Unit: None
Actual Value Range: 1~15
Default Value: 5

CellRacThd SilverServiceArpThd MOD CELLRACTHD LBFD-002023 / TDLBFD- Admission Control Meaning: Indicates the Allocation and Retention Priority (ARP) threshold for the Silver-level services. A service is defined as a Silver-level
LST CELLRACTHD 002023 service if its ARP value is smaller than or equal to the value of this parameter and is larger than the value of GoldServiceArpThd. A service is
defined as a Bronze-level service if its ARP value is larger than the value of this parameter. The service priority has a negative correlation
with the ARP value.
GUI Value Range: 1~15
Unit: None
Actual Value Range: 1~15
Default Value: 10

ENodeBAlgoSwitch UeNumPreemptSwitch MOD LOFD-00102901 / Radio/transport resource Meaning: Indicates the switch used to enable or disable the preemption based on the number of users. IntraOpUeNumPreemptSwitch: This
ENODEBALGOSWITCH TDLOFD-00102901 pre-emption parameter indicates the switch used to enable or disable the intra-operator preemption based on the number of users. If this switch is on,
LST when a user cannot access the network because of the user number restriction, the user can preempt resources of other lower-priority users
ENODEBALGOSWITCH served by the same operator. If this switch is off, preemption is not allowed. InterOpUeNumPreemptSwitch: This parameter indicates the
switch used to enable or disable the inter-operator preemption based on the number of users. If this switch is on, the inter-operator
preemption based on the number of users is allowed. If this switch is off, the inter-operator preemption based on the number of users is not
allowed.
GUI Value Range: IntraOpUeNumPreemptSwitch(IntraOpUeNumPreemptSwitch),
InterOpUeNumPreemptSwitch(InterOpUeNumPreemptSwitch)
Unit: None
Actual Value Range: IntraOpUeNumPreemptSwitch, InterOpUeNumPreemptSwitch
Default Value: IntraOpUeNumPreemptSwitch:Off, InterOpUeNumPreemptSwitch:Off

CSFallBackPolicyCfg CsfbUserArpCfgSwitch MOD LBFD-002023 /TDLBFD- Admission Control Meaning: Indicates whether allocation/retention priorities (ARPs) can be configured for CSFB services triggered by common calls. For details
CSFALLBACKPOLICYCFG 002023 about ARPs, see 3GPP TS 23.401.
LST GUI Value Range: OFF(Off), ON(On)
CSFALLBACKPOLICYCFG Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)

CSFallBackPolicyCfg NormalCsfbUserArp MOD LBFD-002023 /TDLBFD- Admission Control Meaning: Indicates the allocation/retention priority (ARP) of a CSFB service triggered by a common call. When this parameter is set to 1, the
CSFALLBACKPOLICYCFG 002023 service priority is the same as that of an emergency call. For details about the ARP, see 3GPP TS 23.401.
LST GUI Value Range: 1~15
CSFALLBACKPOLICYCFG Unit: None
Actual Value Range: 1~15
Default Value: 2

CellAlgoSwitch RacAlgoSwitch MOD CELLALGOSWITCH LBFD-002023 / TDLBFD- Admission Control Meaning:


LST CELLALGOSWITCH 002023 Congestion Control Indicates whether to enable the admission and load control algorithms.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

LBFD-002024 / TDLBFD- Radio/transport resource DlSwitch: Indicates whether to enable the algorithm of downlink admission control based on the satisfaction rate. If this switch is on, the
002024 pre-emption algorithm is enabled. If this switch is off, the algorithm is disabled. During the calculation of the QoS satisfaction rate of services with different
LOFD-00102901 QCIs, the satisfaction estimation method used dedicatedly for VoIP services is implemented on services with the QCI of 1. If a service with
the QCI of 1 is not a VoIP service, the satisfaction rate calculated using this method is lower than the actual value, which affects the
admission of GBR services. Therefore, if not all the services with the QCI of 1 are VoIP services, it is recommended that this switch be off.
UlSwitch: Indicates whether to enable the algorithm of uplink admission control based on the satisfaction rate. If this switch is on, the
algorithm is enabled. If this switch is off, the algorithm is disabled. During the calculation of the QoS satisfaction rate of services with different
QCIs, the satisfaction estimation method used dedicated for VoIP services is implemented on services with the QCI of 1. If a service with the
QCI of 1 is not a VoIP service, the satisfaction rate calculated using this method is lower than the actual value, which affects the admission
of GBR services. Therefore, if not all the services with the QCI of 1 are VoIP services, it is recommended that this switch be off.
DlPredictSwitch: Indicates whether to enable the algorithm of downlink admission control based on prediction. If this switch is on, the
algorithm is enabled. If this switch is off, the algorithm is disabled.
UlPredictSwitch: Indicates whether to enable the algorithm of uplink admission control based on prediction. If this switch is on, the algorithm
is enabled. If this switch is off, the algorithm is disabled.
GbrUsageSwitch: Indicates whether to enable the check on the number of PRBs used by GBR services. If this switch is on, the number of
PRBs used by existing GBR services is checked before a new GBR service can be admitted. If this switch is off, the number of PRBs used
by existing GBR services is not checked during admission evaluation of new GBR services
DlLdcSwitch: Indicates whether to implement load control in the downlink of a cell. If this switch is on, the system checks for congestion in
the downlink of the cell. If the downlink is congested, load control is performed. If this switch is off, the system does not check for congestion
in the downlink of the cell and the congestion cannot be relieved. During the calculation of the QoS satisfaction rate of services with different
QCIs, the satisfaction estimation method used dedicated for VoIP services is implemented on services with the QCI of 1. If a service with the
QCI of 1 is not a VoIP service, the satisfaction rate calculated using this method is lower than the actual value, which affects the cell load
control. Therefore, if not all the services with the QCI of 1 are VoIP services, it is recommended that this switch be off.
UlLdcSwitch: Indicates whether to implement load control in the uplink of a cell. If this switch is on, the system checks for congestion in the
uplink of the cell. If the uplink is congested, load control is performed. If this switch is off, the system does not check for congestion in the
uplink of the cell and the congestion cannot be relieved. During the calculation of the QoS satisfaction rate of services with different QCIs,
the satisfaction estimation method used dedicated for VoIP services is implemented on services with the QCI of 1. If a service with the QCI
of 1 is not a VoIP service, the satisfaction rate calculated using this method is lower than the actual value, which affects the cell load control.
Therefore, if not all the services with the QCI of 1 are VoIP services, it is recommended that this switch be off.
RelDrbSwitch: Indicates whether low-priority services can be released in the case of congestion. If this switch is on, low-priority services can
be released. If this switch is off, low-priority services cannot be released.
PreemptionSwitch: Indicates whether to enable the preemption control algorithm. If this switch is on, preemption can be used when the
admission of high-priority services fails. If this switch is off, only emergency calls can be admitted to the system when resources are
insufficient.
GUI Value Range: DlSwitch(dlCacSwitch), UlSwitch(ulCacSwitch), DlPredictSwitch(dlCacPredictSwitch),
UlPredictSwitch(ulCacPredictSwitch), GbrUsageSwitch(GbrUsedPRbCheckSwitch), DlLdcSwitch(dlLdcSwitch), UlLdcSwitch(ulLdcSwitch),
RelDrbSwitch(LdcDrbRelSwitch), PreemptionSwitch(PreemptionSwitch)
Unit: None
Actual Value Range: DlSwitch, UlSwitch, DlPredictSwitch, UlPredictSwitch, GbrUsageSwitch, DlLdcSwitch, UlLdcSwitch, RelDrbSwitch,
PreemptionSwitch
Default Value: DlSwitch:Off, UlSwitch:Off, DlPredictSwitch:Off, UlPredictSwitch:Off, GbrUsageSwitch:Off, DlLdcSwitch:Off, UlLdcSwitch:Off,
RelDrbSwitch:Off, PreemptionSwitch:Off

ENodeBAlgoSwitch RedirectSwitch MOD LBFD-002023 / TDLBFD- Admission Control Meaning:


ENODEBALGOSWITCH 002023 Congestion Control Indicates the switch used to enable or disable the redirection algorithm. This switch does not control redirection or fast redirection for CSFB.
LST LBFD-002024 / TDLBFD- Radio/transport resource GeranFlashRedirectSwitch: If this switch and GeranRedirectSwitch are on, fast redirection to GERAN can be performed.
ENODEBALGOSWITCH 002024 pre-emption UranFlashRedirectSwitch: If this switch and UtranRedirectSwitch are on, fast redirection to UTRAN can be performed.
LOFD-00102901 / PS Inter-RAT Mobility LoadBasedSwitch: If this switch is on, load based redirection can be performed.
TDLOFD-00102901 between E-UTRAN and GUI Value Range: LoadBasedSwitch, GeranFlashRedirectSwitch, UranFlashRedirectSwitch
LOFD-001019 / TDLOFD- UTRAN Unit: None
001019 PS Inter-RAT Mobility Actual Value Range: LoadBasedSwitch, GeranFlashRedirectSwitch, UranFlashRedirectSwitch
LOFD-001020 / TDLOFD- between E-UTRAN and
Default Value: LoadBasedSwitch:Off, GeranFlashRedirectSwitch:Off, UranFlashRedirectSwitch:Off
001020 GERAN
LOFD-001021 / TDLOFD- PS Inter-RAT Mobility
001021 between E-UTRAN and
CDMA2000

CellRacThd CongRelOffset MOD CELLRACTHD LBFD-002024 / TDLBFD- Congestion Control Meaning: Indicates the congestion release offset. The service of a specific QCI exits the congestion state if the satisfaction rate of the service
LST CELLRACTHD 002024 exceeds the sum of this congestion release offset and the congestion threshold for the QCI. The service retains the congestion state if the
satisfaction rate is below or equal to the sum of this congestion release offset and the congestion threshold for the QCI.
GUI Value Range: 0~50
Unit: %
Actual Value Range: 0~50
Default Value: 20

CellRacThd Qci1CongThd MOD CELLRACTHD LBFD-002024 / TDLBFD- Congestion Control Meaning:


LST CELLRACTHD 002024 Indicates the congestion threshold for services with QCI of 1. This threshold applies to both UL and DL.
If the satisfaction rate of services with QCI of 1 in the cell becomes lower than this threshold, the services with QCI of 1 enter the congested
state.
If the satisfaction rate of services with QCI of 1 in the cell becomes higher than the sum of this threshold and the congestion relief offset, the
services with QCI of 1 leave the congested state.
GUI Value Range: 0~99
Unit: %
Actual Value Range: 0~99
Default Value: 65

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

CellRacThd Qci2CongThd MOD CELLRACTHD LBFD-002024 / TDLBFD- Congestion Control Meaning:


LST CELLRACTHD 002024 Indicates the congestion threshold for services with QCI of 2. This threshold applies to both UL and DL.
If the satisfaction rate of services with QCI of 2 in the cell becomes lower than this threshold, the services with QCI of 2 enter the congested
state.
If the satisfaction rate of services with QCI of 2 in the cell becomes higher than the sum of this threshold and the congestion relief offset, the
services with QCI of 2 leave the congested state.
GUI Value Range: 0~99
Unit: %
Actual Value Range: 0~99
Default Value: 65

CellRacThd Qci3CongThd MOD CELLRACTHD LBFD-002024 / TDLBFD- Congestion Control Meaning:


LST CELLRACTHD 002024 Indicates the congestion threshold for services with QCI of 3. This threshold applies to both UL and DL.
If the satisfaction rate of the services with QCI of 3 in the cell becomes lower than this threshold, the services with QCI of 3 enter the
congested state.
If the satisfaction rate of services with QCI of 3 in the cell becomes higher than the sum of this threshold and the congestion relief offset, the
services with QCI of 3 leave the congested state.
GUI Value Range: 0~99
Unit: %
Actual Value Range: 0~99
Default Value: 65

CellRacThd Qci4CongThd MOD CELLRACTHD LBFD-002024 / TDLBFD- Congestion Control Meaning:


LST CELLRACTHD 002024 Indicates the congestion threshold for services with QCI of 4. This threshold applies to both UL and DL.
If the satisfaction rate of services with QCI of 4 in the cell becomes lower than this threshold, the services with QCI of 4 enter the congested
state.
If the satisfaction rate of services with QCI of 4 in the cell becomes higher than the sum of this threshold and the congestion relief offset, the
services with QCI of 4 leave the congested state.
GUI Value Range: 0~99
Unit: %
Actual Value Range: 0~99
Default Value: 65

CellAlgoSwitch LocalCellId DSP None None Meaning: Indicates the local ID of the cell. It uniquely identifies a cell within a BS.
CELLULCAMCCLUSTER GUI Value Range: 0~255
LST CELLALGOSWITCH Unit: None
MOD CELLALGOSWITCH Actual Value Range: 0~255
Default Value: None

CellRacThd LocalCellId LST CELLRACTHD None None Meaning: Indicates the local cell ID. It uniquely identifies a cell within a BS.
MOD CELLRACTHD GUI Value Range: 0~255
Unit: None
Actual Value Range: 0~255
Default Value: None

CellRacThd Qci1HoThd MOD CELLRACTHD LBFD-002023 / TDLBFD- Admission Control Meaning:


LST CELLRACTHD 002023 Indicates the admission threshold for the handed-over service with QCI of 1. This threshold applies to both UL and DL.
If the satisfaction rate of services with QCI of 1 is above or equal to this threshold, the handed-over service with QCI of 1 can be admitted.
If the satisfaction rate of services with QCI of 1 is below this threshold, the handed-over service with QCI of 1 cannot be admitted.
GUI Value Range: 10~99
Unit: %
Actual Value Range: 10~99
Default Value: 90

CellRacThd Qci2HoThd MOD CELLRACTHD LBFD-002023 / TDLBFD- Admission Control Meaning:


LST CELLRACTHD 002023 Indicates the admission threshold for the handed-over service with QCI of 2. This threshold applies to both UL and DL.
If the satisfaction rate of services with QCI of 2 is above or equal to this threshold, the handed-over service with QCI of 2 can be admitted.
If the satisfaction rate of services with QCI of 2 is below this threshold, the handed-over service with QCI of 2 cannot be admitted.
GUI Value Range: 10~99
Unit: %
Actual Value Range: 10~99
Default Value: 90

CellRacThd Qci3HoThd MOD CELLRACTHD LBFD-002023 / TDLBFD- Admission Control Meaning:


LST CELLRACTHD 002023 Indicates the admission threshold for the handed-over service with QCI of 3. This threshold applies to both UL and DL.
If the satisfaction rate of services with QCI of 3 is above or equal to this threshold, the handed-over service with QCI of 3 can be admitted.
If the satisfaction rate of services with QCI of 3 is below this threshold, the handed-over service with QCI of 3 cannot be admitted.
GUI Value Range: 10~99
Unit: %
Actual Value Range: 10~99
Default Value: 90

CellRacThd Qci4HoThd MOD CELLRACTHD LBFD-002023 / TDLBFD- Admission Control Meaning:

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

LST CELLRACTHD 002023 Indicates the admission threshold for the handed-over service with QCI of 4. This threshold applies to both UL and DL.
If the satisfaction rate of services with QCI of 4 is above or equal to this threshold, the handed-over service with QCI of 4 can be admitted.
If the satisfaction rate of services with QCI of 4 is below this threshold, the handed-over service with QCI of 4 cannot be admitted.
GUI Value Range: 10~99
Unit: %
Actual Value Range: 10~99
Default Value: 90

CellRacThd UlRbHighThd MOD CELLRACTHD LBFD-002023 / TDLBFD- Admission Control Meaning: Indicates the threshold for deciding on whether the UL RB usage is high. This threshold applies to UL admission decision. If the UL
LST CELLRACTHD 002023 Congestion Control RB usage reported by the MAC layer is above this threshold, the UL RB usage is assumed to be high.
LBFD-002024 / TDLBFD- GUI Value Range: 10~100
002024 Unit: %
Actual Value Range: 10~100
Default Value: 95

CellRacThd UlRbLowThd MOD CELLRACTHD LBFD-002023 / TDLBFD- Admission Control Meaning: Indicates the threshold for deciding on whether the UL RB usage is low. It applies to UL admission decision. If the UL RB usage
LST CELLRACTHD 002023 Congestion Control reported by the MAC layer is below this threshold, the UL RB usage is assumed to be low.
LBFD-002024 / TDLBFD- GUI Value Range: 10~100
002024 Unit: %
Actual Value Range: 10~100
Default Value: 90

9 Counters

Table 9-1 Counters

Counter ID Counter Name Counter Description Feature ID Feature Name

1526726657 L.RRC.ConnReq.Msg Number of RRC connection setup requests Multi-mode: None RRC Connection Management
(retransmission included) GSM: None RRC Connection Management
UMTS: None
LTE: LBFD-002007
TDLBFD-002007

1526726659 L.RRC.ConnReq.Succ Number of RRC connection setup completion times Multi-mode: None RRC Connection Management
GSM: None RRC Connection Management
UMTS: None
LTE: LBFD-002007
TDLBFD-002007

1526726760 L.LC.ULCong.Num.Cell Number of times uplink congestion occurs in a cell Multi-mode: None Congestion Control
GSM: None Congestion Control
UMTS: None
LTE: LBFD-002024
TDLBFD-002024

1526726761 L.LC.ULCong.Dur.Cell Duration of uplink congestion in a cell Multi-mode: None Congestion Control
GSM: None Congestion Control
UMTS: None
LTE: LBFD-002024
TDLBFD-002024

1526726762 L.LC.DLCong.Num.Cell Number of times downlink congestion occurs in a cell Multi-mode: None Congestion Control
GSM: None Congestion Control
UMTS: None
LTE: LBFD-002024
TDLBFD-002024

1526726763 L.LC.DLCong.Dur.Cell Duration of downlink congestion in a cell Multi-mode: None Congestion Control
GSM: None Congestion Control
UMTS: None
LTE: LBFD-002024
TDLBFD-002024

1526726764 L.LC.User.Rel Number of service releases due to congestion Multi-mode: None Congestion Control
GSM: None Congestion Control
UMTS: None
LTE: LBFD-002024
TDLBFD-002024

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

1526727544 L.E-RAB.SuccEst Total number of successful E-RAB setups initiated by Multi-mode: None Radio Bearer Management
UEs in a cell GSM: None Radio Bearer Management
UMTS: None
LTE: LBFD-002008
TDLBFD-002008

1526727545 L.E-RAB.AttEst Total number of E-RAB setup attempts initiated by UEs Multi-mode: None Radio Bearer Management
in a cell GSM: None Radio Bearer Management
UMTS: None
LTE: LBFD-002008
TDLBFD-002008

1526728274 L.E-RAB.InitAttEst Total number of initial E-RAB setup attempts initiated Multi-mode: None Radio Bearer Management
by UEs in a cell GSM: None Radio Bearer Management
UMTS: None
LTE: LBFD-002008
TDLBFD-002008

1526728275 L.E-RAB.InitSuccEst Total number of successful initial E-RAB setups Multi-mode: None Radio Bearer Management
initiated by UEs in a cell GSM: None Radio Bearer Management
UMTS: None
LTE: LBFD-002008
TDLBFD-002008

1526728278 L.E-RAB.FailEst.RNL Number of E-RAB setup failures due to faults at the Multi-mode: None Radio Bearer Management
radio network layer GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008
LBFD-002023
TDLBFD-002023

1526728279 L.E-RAB.FailEst.NoRadioRes Number of E-RAB setup failures due to insufficient Multi-mode: None Radio Bearer Management
radio resources GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008
LBFD-002023
TDLBFD-002023

1526728284 L.E-RAB.AbnormRel.Cong Number of abnormal releases of activated E-RABs due Multi-mode: None Radio Bearer Management
to network congestion GSM: None Radio Bearer Management
UMTS: None Congestion Control
LTE: LBFD-002008 Congestion Control
TDLBFD-002008 Radio/transport resource pre-emption
LBFD-002024 Radio/transport resource pre-emption
TDLBFD-002024
LOFD-00102901
TDLOFD-00102901

1526728325 L.RRCRedirection.IntraLTE Number of intra-RAT intra-duplex-mode redirections Multi-mode: None Admission Control
GSM: None Admission Control
UMTS: None Coverage Based Inter-frequency Handover
LTE: LBFD-002023 Coverage Based Inter-frequency Handover
TDLBFD-002023 Distance Based Inter-frequency Handover
LBFD-00201802
TDLBFD-00201802
LBFD-00201804

1526728444 L.Cell.UserLimit.PreEmp.Num Number of successful preemptions triggered due to Multi-mode: None Radio/transport resource pre-emption
user limitation GSM: None Radio/transport resource pre-emption
UMTS: None
LTE: LOFD-00102901
TDLOFD-00102901

1526729495 L.E-RAB.AbnormRel.Cong.PLMN Number of abnormal releases of activated E-RABs Multi-mode: None Radio Bearer Management
because of network congestion for a specific operator GSM: None Radio Bearer Management
UMTS: None Congestion Control
LTE: LBFD-002008 Congestion Control
TDLBFD-002008 Radio/transport resource pre-emption
LBFD-002024 Radio/transport resource pre-emption
TDLBFD-002024 RAN Sharing with Common Carrier
LOFD-00102901 RAN Sharing with Dedicated Carrier

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

TDLOFD-00102901 RAN Sharing with Common Carrier


LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037 Hybrid RAN Sharing
TDLOFD-001036
TDLOFD-001037
LOFD-070206

1526729545 L.E-RAB.FailEst.NoRadioRes.SRS Number of E-RAB setup failures due to insufficient Multi-mode: None Radio Bearer Management
SRS resources GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008
LBFD-002023
TDLBFD-002023

1526729546 L.E-RAB.FailEst.NoRadioRes.PUCCH Number of E-RAB setup failures due to insufficient Multi-mode: None Radio Bearer Management
PUCCH resources GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008
LBFD-002023
TDLBFD-002023

1526729631 L.RRCRedirection.InterFddTdd Number of intra-RAT inter-duplex-mode redirections Multi-mode: None Admission Control
GSM: None Admission Control
UMTS: None Coverage Based Inter-frequency Handover
LTE: LBFD-002023 Coverage Based Inter-frequency Handover
TDLBFD-002023 Distance Based Inter-frequency Handover
LBFD-00201802
TDLBFD-00201802
LBFD-00201804

1526729912 L.E-RAB.AbnormRel.Cong.PreEmp Number of abnormal releases of activated E-RABs Multi-mode: None Radio Bearer Management
because of radio resource preemption GSM: None Radio Bearer Management
UMTS: None Congestion Control
LTE: LBFD-002008 Congestion Control
TDLBFD-002008 Radio/transport resource pre-emption
LBFD-002024 Radio/transport resource pre-emption
TDLBFD-002024
LOFD-00102901
TDLOFD-00102901

1526729913 L.E-RAB.AbnormRel.Cong.Load Number of abnormal releases of activated E-RABs Multi-mode: None Radio Bearer Management
because of radio resource overload GSM: None Radio Bearer Management
UMTS: None Congestion Control
LTE: LBFD-002008 Congestion Control
TDLBFD-002008
LBFD-002024
TDLBFD-002024

1526729923 L.E-RAB.AbnormRel.Cong.VoIP Number of abnormal releases of activated E-RABs for Multi-mode: None Radio Bearer Management
voice services because of radio network congestion GSM: None Radio Bearer Management
UMTS: None Congestion Control
LTE: LBFD-002008 Congestion Control
TDLBFD-002008 Radio/transport resource pre-emption
LBFD-002024 Radio/transport resource pre-emption
TDLBFD-002024
LOFD-00102901
TDLOFD-00102901

1526729926 L.E-RAB.AbnormRel.Cong.PreEmp.VoIP Number of abnormal releases of activated E-RABs for Multi-mode: None Radio Bearer Management
voice services because of radio resource preemption GSM: None Radio Bearer Management
UMTS: None Congestion Control
LTE: LBFD-002008 Congestion Control
TDLBFD-002008 Radio/transport resource pre-emption
LBFD-002024 Radio/transport resource pre-emption
TDLBFD-002024
LOFD-00102901
TDLOFD-00102901

1526729927 L.E-RAB.AbnormRel.Cong.Load.VoIP Number of abnormal releases of activated E-RABs for Multi-mode: None Radio Bearer Management
voice services because of radio resource overload GSM: None Radio Bearer Management
UMTS: None Congestion Control

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

LTE: LBFD-002008 Congestion Control


TDLBFD-002008
LBFD-002024
TDLBFD-002024

1526729931 L.E-RAB.AbnormRel.Cong.PreEmp.PLMN Number of abnormal releases of activated E-RABs Multi-mode: None Radio Bearer Management
because of radio resource preemption for a specific GSM: None Radio Bearer Management
operator UMTS: None RAN Sharing with Common Carrier
LTE: LBFD-002008 RAN Sharing with Dedicated Carrier
TDLBFD-002008 RAN Sharing with Common Carrier
LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037 Hybrid RAN Sharing
TDLOFD-001036 Congestion Control
TDLOFD-001037 Congestion Control
LOFD-070206 Radio/transport resource pre-emption
LBFD-002024 Radio/transport resource pre-emption
TDLBFD-002024
LOFD-00102901
TDLOFD-00102901

1526729932 L.E-RAB.AbnormRel.Cong.Load.PLMN Number of abnormal releases of activated E-RABs Multi-mode: None Radio Bearer Management
because of radio resource overload for a specific GSM: None Radio Bearer Management
operator UMTS: None RAN Sharing with Common Carrier
LTE: LBFD-002008 RAN Sharing with Dedicated Carrier
TDLBFD-002008 RAN Sharing with Common Carrier
LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037 Hybrid RAN Sharing
TDLOFD-001036 Congestion Control
TDLOFD-001037 Congestion Control
LOFD-070206
LBFD-002024
TDLBFD-002024

1526729942 L.E-RAB.AbnormRel.Cong.VoIP.PLMN Number of abnormal releases of activated E-RABs for Multi-mode: None Radio Bearer Management
voice services because of radio network congestion for GSM: None Radio Bearer Management
a specific operator UMTS: None RAN Sharing with Common Carrier
LTE: LBFD-002008 RAN Sharing with Dedicated Carrier
TDLBFD-002008 RAN Sharing with Common Carrier
LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037 Hybrid RAN Sharing
TDLOFD-001036 Congestion Control
TDLOFD-001037 Congestion Control
LOFD-070206 Radio/transport resource pre-emption
LBFD-002024 Radio/transport resource pre-emption
TDLBFD-002024
LOFD-00102901
TDLOFD-00102901

1526729947 L.E-RAB.AbnormRel.Cong.PreEmp.VoIP.PLMN Number of abnormal releases of activated E-RABs for Multi-mode: None Radio Bearer Management
voice services because of radio resource preemption GSM: None Radio Bearer Management
for a specific operator UMTS: None RAN Sharing with Common Carrier
LTE: LBFD-002008 RAN Sharing with Dedicated Carrier
TDLBFD-002008 RAN Sharing with Common Carrier
LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037 Hybrid RAN Sharing
TDLOFD-001036 Congestion Control
TDLOFD-001037 Congestion Control
LOFD-070206 Radio/transport resource pre-emption
LBFD-002024 Radio/transport resource pre-emption
TDLBFD-002024
LOFD-00102901
TDLOFD-00102901

1526729948 L.E-RAB.AbnormRel.Cong.Load.VoIP.PLMN Number of abnormal releases of activated E-RABs for Multi-mode: None Radio Bearer Management
voice services because of radio resource overload for a GSM: None Radio Bearer Management
specific operator UMTS: None RAN Sharing with Common Carrier
LTE: LBFD-002008 RAN Sharing with Dedicated Carrier
TDLBFD-002008 RAN Sharing with Common Carrier
LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037 Hybrid RAN Sharing
TDLOFD-001036 Congestion Control
TDLOFD-001037 Congestion Control

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

LOFD-070206
LBFD-002024
TDLBFD-002024

1526729951 L.E-RAB.FailEst.TNL.DLRes Number of E-RAB setup failures because of insufficient Multi-mode: None Radio Bearer Management
downlink transport resources GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008
LBFD-002023
TDLBFD-002023

1526729952 L.E-RAB.FailEst.TNL.ULRes Number of E-RAB setup failures because of insufficient Multi-mode: None Radio Bearer Management
uplink transport resources GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008
LBFD-002023
TDLBFD-002023

1526729953 L.E-RAB.FailEst.NoRadioRes.DLThrpLic Number of E-RAB setup failures because of insufficient Multi-mode: None Radio Bearer Management
licensed downlink traffic volume GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008
LBFD-002023
TDLBFD-002023

1526729954 L.E-RAB.FailEst.NoRadioRes.ULThrpLic Number of E-RAB setup failures because of insufficient Multi-mode: None Radio Bearer Management
licensed uplink traffic volume GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008
LBFD-002023
TDLBFD-002023

1526729955 L.E-RAB.FailEst.NoRadioRes.DLSatis Number of E-RAB setup failures because of a low Multi-mode: None Radio Bearer Management
downlink satisfaction rate GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008
LBFD-002023
TDLBFD-002023

1526729956 L.E-RAB.FailEst.NoRadioRes.ULSatis Number of E-RAB setup failures because of a low Multi-mode: None Radio Bearer Management
uplink satisfaction rate GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008
LBFD-002023
TDLBFD-002023

1526729961 L.E-RAB.FailEst.NoRadioRes.VoIP Number of setup failures of E-RABs for voice services Multi-mode: None Radio Bearer Management
because of insufficient radio resources GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008
LBFD-002023
TDLBFD-002023

1526729964 L.E-RAB.FailEst.NoRadioRes.SRS.VoIP Number of setup failures of E-RABs for voice services Multi-mode: None Radio Bearer Management
because of insufficient SRS resources GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008
LBFD-002023
TDLBFD-002023

1526729965 L.E-RAB.FailEst.NoRadioRes.PUCCH.VoIP Number of setup failures of E-RABs for voice services Multi-mode: None Radio Bearer Management
because of insufficient PUCCH resources GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

LBFD-002023
TDLBFD-002023

1526729966 L.E-RAB.FailEst.NoRadioRes.DLThrpLic.VoIP Number of setup failures of E-RABs for voice services Multi-mode: None Radio Bearer Management
because of insufficient licensed downlink traffic volume GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008
LBFD-002023
TDLBFD-002023

1526729967 L.E-RAB.FailEst.NoRadioRes.ULThrpLic.VoIP Number of setup failures of E-RABs for voice services Multi-mode: None Radio Bearer Management
because of insufficient licensed uplink traffic volume GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008
LBFD-002023
TDLBFD-002023

1526729968 L.E-RAB.FailEst.NoRadioRes.DLSatis.VoIP Number of setup failures of E-RABs for voice services Multi-mode: None Radio Bearer Management
because of a low downlink satisfaction rate GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008
LBFD-002023
TDLBFD-002023

1526729969 L.E-RAB.FailEst.NoRadioRes.ULSatis.VoIP Number of setup failures of E-RABs for voice services Multi-mode: None Radio Bearer Management
because of a low uplink satisfaction rate GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008
LBFD-002023
TDLBFD-002023

1526729970 L.E-RAB.FailEst.TNL.DLRes.VoIP Number of setup failures of E-RABs for voice services Multi-mode: None Radio Bearer Management
because of insufficient downlink transport resources GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008
LBFD-002023
TDLBFD-002023

1526729971 L.E-RAB.FailEst.TNL.ULRes.VoIP Number of setup failures of E-RABs for voice services Multi-mode: None Radio Bearer Management
because of insufficient uplink transport resources GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008
LBFD-002023
TDLBFD-002023

1526729973 L.E-RAB.FailEst.TNL.DLRes.PLMN Number of E-RAB setup failures because of insufficient Multi-mode: None Radio Bearer Management
downlink transport resources for a specific operator GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008 RAN Sharing with Common Carrier
LBFD-002023 RAN Sharing with Dedicated Carrier
TDLBFD-002023 RAN Sharing with Common Carrier
LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037 Hybrid RAN Sharing
TDLOFD-001036
TDLOFD-001037
LOFD-070206

1526729974 L.E-RAB.FailEst.TNL.ULRes.PLMN Number of E-RAB setup failures because of insufficient Multi-mode: None Radio Bearer Management
uplink transport resources for a specific operator GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008 RAN Sharing with Common Carrier
LBFD-002023 RAN Sharing with Dedicated Carrier
TDLBFD-002023 RAN Sharing with Common Carrier
LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037 Hybrid RAN Sharing

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

TDLOFD-001036
TDLOFD-001037
LOFD-070206

1526729975 L.E-RAB.FailEst.NoRadioRes.DLThrpLic.PLMN Number of E-RAB setup failures because of insufficient Multi-mode: None Radio Bearer Management
downlink licensed traffic volume for a specific operator GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008 RAN Sharing with Common Carrier
LBFD-002023 RAN Sharing with Dedicated Carrier
TDLBFD-002023 RAN Sharing with Common Carrier
LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037 Hybrid RAN Sharing
TDLOFD-001036
TDLOFD-001037
LOFD-070206

1526729976 L.E-RAB.FailEst.NoRadioRes.ULThrpLic.PLMN Number of E-RAB setup failures because of insufficient Multi-mode: None Radio Bearer Management
uplink licensed traffic volume for a specific operator GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008 RAN Sharing with Common Carrier
LBFD-002023 RAN Sharing with Dedicated Carrier
TDLBFD-002023 RAN Sharing with Common Carrier
LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037 Hybrid RAN Sharing
TDLOFD-001036
TDLOFD-001037
LOFD-070206

1526729977 L.E-RAB.FailEst.NoRadioRes.DLSatis.PLMN Number of E-RAB setup failures because of a low Multi-mode: None Radio Bearer Management
downlink satisfaction rate for a specific operator GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008 RAN Sharing with Common Carrier
LBFD-002023 RAN Sharing with Dedicated Carrier
TDLBFD-002023 RAN Sharing with Common Carrier
LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037 Hybrid RAN Sharing
TDLOFD-001036
TDLOFD-001037
LOFD-070206

1526729978 L.E-RAB.FailEst.NoRadioRes.ULSatis.PLMN Number of E-RAB setup failures because of a low Multi-mode: None Radio Bearer Management
uplink satisfaction rate for a specific operator GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008 RAN Sharing with Common Carrier
LBFD-002023 RAN Sharing with Dedicated Carrier
TDLBFD-002023 RAN Sharing with Common Carrier
LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037 Hybrid RAN Sharing
TDLOFD-001036
TDLOFD-001037
LOFD-070206

1526729983 L.E-RAB.FailEst.NoRadioRes.VoIP.PLMN Number of setup failures of E-RABs for voice services Multi-mode: None Radio Bearer Management
because of insufficient radio resources for a specific GSM: None Radio Bearer Management
operator UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008 RAN Sharing with Common Carrier
LBFD-002023 RAN Sharing with Dedicated Carrier
TDLBFD-002023 RAN Sharing with Common Carrier
LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037 Hybrid RAN Sharing
TDLOFD-001036
TDLOFD-001037
LOFD-070206

1526729986 L.E-RAB.FailEst.NoRadioRes.SRS.VoIP.PLMN Number of setup failures of E-RABs for voice services Multi-mode: None Radio Bearer Management
because of insufficient SRS resources for a specific GSM: None Radio Bearer Management
operator UMTS: None Admission Control

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

LTE: LBFD-002008 Admission Control


TDLBFD-002008 RAN Sharing with Common Carrier
LBFD-002023 RAN Sharing with Dedicated Carrier
TDLBFD-002023 RAN Sharing with Common Carrier
LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037 Hybrid RAN Sharing
TDLOFD-001036
TDLOFD-001037
LOFD-070206

1526729987 L.E-RAB.FailEst.NoRadioRes.PUCCH.VoIP.PLMN Number of setup failures of E-RABs for voice services Multi-mode: None Radio Bearer Management
because of insufficient PUCCH resources for a specific GSM: None Radio Bearer Management
operator UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008 RAN Sharing with Common Carrier
LBFD-002023 RAN Sharing with Dedicated Carrier
TDLBFD-002023 RAN Sharing with Common Carrier
LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037 Hybrid RAN Sharing
TDLOFD-001036
TDLOFD-001037
LOFD-070206

1526729988 L.E-RAB.FailEst.NoRadioRes.DLThrpLic.VoIP.PLMN Number of setup failures of E-RABs for voice services Multi-mode: None Radio Bearer Management
because of insufficient licensed downlink traffic volume GSM: None Radio Bearer Management
for a specific operator UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008 RAN Sharing with Common Carrier
LBFD-002023 RAN Sharing with Dedicated Carrier
TDLBFD-002023 RAN Sharing with Common Carrier
LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037 Hybrid RAN Sharing
TDLOFD-001036
TDLOFD-001037
LOFD-070206

1526729989 L.E-RAB.FailEst.NoRadioRes.ULThrpLic.VoIP.PLMN Number of setup failures of E-RABs for voice services Multi-mode: None Radio Bearer Management
because of insufficient licensed uplink traffic volume for GSM: None Radio Bearer Management
a specific operator UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008 RAN Sharing with Common Carrier
LBFD-002023 RAN Sharing with Dedicated Carrier
TDLBFD-002023 RAN Sharing with Common Carrier
LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037 Hybrid RAN Sharing
TDLOFD-001036
TDLOFD-001037
LOFD-070206

1526729990 L.E-RAB.FailEst.NoRadioRes.DLSatis.VoIP.PLMN Number of setup failures of E-RABs for voice services Multi-mode: None Radio Bearer Management
because of a low downlink satisfaction rate for a GSM: None Radio Bearer Management
specific operator UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008 RAN Sharing with Common Carrier
LBFD-002023 RAN Sharing with Dedicated Carrier
TDLBFD-002023 RAN Sharing with Common Carrier
LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037 Hybrid RAN Sharing
TDLOFD-001036
TDLOFD-001037
LOFD-070206

1526729991 L.E-RAB.FailEst.NoRadioRes.ULSatis.VoIP.PLMN Number of setup failures of E-RABs for voice services Multi-mode: None Radio Bearer Management
because of a low uplink satisfaction rate for a specific GSM: None Radio Bearer Management
operator UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008 RAN Sharing with Common Carrier
LBFD-002023 RAN Sharing with Dedicated Carrier
TDLBFD-002023 RAN Sharing with Common Carrier
LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037 Hybrid RAN Sharing
TDLOFD-001036

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

TDLOFD-001037
LOFD-070206

1526729992 L.E-RAB.FailEst.TNL.DLRes.VoIP.PLMN Number of setup failures of E-RABs for voice services Multi-mode: None Radio Bearer Management
because of insufficient downlink transport resources for GSM: None Radio Bearer Management
a specific operator UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008 RAN Sharing with Common Carrier
LBFD-002023 RAN Sharing with Dedicated Carrier
TDLBFD-002023 RAN Sharing with Common Carrier
LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037 Hybrid RAN Sharing
TDLOFD-001036
TDLOFD-001037
LOFD-070206

1526729993 L.E-RAB.FailEst.TNL.ULRes.VoIP.PLMN Number of setup failures of E-RABs for voice services Multi-mode: None Radio Bearer Management
because of insufficient uplink transport resources for a GSM: None Radio Bearer Management
specific operator UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008 RAN Sharing with Common Carrier
LBFD-002023 RAN Sharing with Dedicated Carrier
TDLBFD-002023 RAN Sharing with Common Carrier
LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037 Hybrid RAN Sharing
TDLOFD-001036
TDLOFD-001037
LOFD-070206

1526730100 L.Traffic.Privilege.User.avg Average number of privileged UEs in a cell Multi-mode: None Admission Control
GSM: None Admission Control
UMTS: None Emergency Call
LTE: LBFD-002023 Emergency call
TDLBFD-002023
LBFD-002028
TDLBFD-002028

1526730101 L.Traffic.Privilege.User.max Maximum number of privileged UEs in a cell Multi-mode: None Admission Control
GSM: None Admission Control
UMTS: None Emergency Call
LTE: LBFD-002023 Emergency call
TDLBFD-002023
LBFD-002028
TDLBFD-002028

1526730830 L.E-RAB.FailEst.RNL.eNodeB.NormRel Number of E-RAB setup failures due to normal release Multi-mode: None Radio Bearer Management
initiated by eNodeB GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008
LBFD-002023
TDLBFD-002023

1526730831 L.E-RAB.FailEst.RNL.eNodeB.AbnormRel Number of E-RAB setup failures due to abnormal Multi-mode: None Radio Bearer Management
release initiated by eNodeB GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008
LBFD-002023
TDLBFD-002023

1526736694 L.E-RAB.FailEst.NoRadioRes.DLSatis.QCI2 Number of setup failures of E-RABs with a QCI of 2 Multi-mode: None Radio Bearer Management
because of a low downlink satisfaction rate GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008
TDLBFD-002023
LBFD-002023

1526736695 L.E-RAB.FailEst.NoRadioRes.DLSatis.QCI3 Number of setup failures of E-RABs with a QCI of 3 Multi-mode: None Radio Bearer Management
because of a low downlink satisfaction rate GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

TDLBFD-002008
TDLBFD-002023
LBFD-002023

1526736696 L.E-RAB.FailEst.NoRadioRes.DLSatis.QCI4 Number of setup failures of E-RABs with a QCI of 4 Multi-mode: None Radio Bearer Management
because of a low downlink satisfaction rate GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008
TDLBFD-002023
LBFD-002023

1526736697 L.E-RAB.FailEst.NoRadioRes.ULSatis.QCI2 Number of setup failures of E-RABs with a QCI of 2 Multi-mode: None Radio Bearer Management
because of a low uplink satisfaction rate GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008
TDLBFD-002023
LBFD-002023

1526736698 L.E-RAB.FailEst.NoRadioRes.ULSatis.QCI3 Number of setup failures of E-RABs with a QCI of 3 Multi-mode: None Radio Bearer Management
because of a low uplink satisfaction rate GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008
TDLBFD-002023
LBFD-002023

1526736699 L.E-RAB.FailEst.NoRadioRes.ULSatis.QCI4 Number of setup failures of E-RABs with a QCI of 4 Multi-mode: None Radio Bearer Management
because of a low uplink satisfaction rate GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008
TDLBFD-002023
LBFD-002023

1526736700 L.E-RAB.FailEst.NoRadioRes.DLSatis.QCI2.PLMN Number of setup failures of E-RABs with a QCI of 2 Multi-mode: None Radio Bearer Management
because of a low downlink satisfaction rate for a GSM: None Radio Bearer Management
specific operator UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008 RAN Sharing with Common Carrier
LBFD-002023 RAN Sharing with Dedicated Carrier
TDLBFD-002023 RAN Sharing with Common Carrier
LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037 Hybrid RAN Sharing
TDLOFD-001036
TDLOFD-001037
LOFD-070206

1526736701 L.E-RAB.FailEst.NoRadioRes.DLSatis.QCI3.PLMN Number of setup failures of E-RABs with a QCI of 3 Multi-mode: None Radio Bearer Management
because of a low downlink satisfaction rate for a GSM: None Radio Bearer Management
specific operator UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008 RAN Sharing with Common Carrier
LBFD-002023 RAN Sharing with Dedicated Carrier
TDLBFD-002023 RAN Sharing with Common Carrier
LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037
TDLOFD-001036
TDLOFD-001037

1526736702 L.E-RAB.FailEst.NoRadioRes.DLSatis.QCI4.PLMN Number of setup failures of E-RABs with a QCI of 4 Multi-mode: None Radio Bearer Management
because of a low downlink satisfaction rate for a GSM: None Radio Bearer Management
specific operator UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008 RAN Sharing with Common Carrier
LBFD-002023 RAN Sharing with Dedicated Carrier
TDLBFD-002023 RAN Sharing with Common Carrier
LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037
TDLOFD-001036
TDLOFD-001037

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

1526736703 L.E-RAB.FailEst.NoRadioRes.ULSatis.QCI2.PLMN Number of setup failures of E-RABs with a QCI of 2 Multi-mode: None Radio Bearer Management
because of a low uplink satisfaction rate for a specific GSM: None Radio Bearer Management
operator UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008 RAN Sharing with Common Carrier
LBFD-002023 RAN Sharing with Dedicated Carrier
TDLBFD-002023 RAN Sharing with Common Carrier
LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037
TDLOFD-001036
TDLOFD-001037

1526736704 L.E-RAB.FailEst.NoRadioRes.ULSatis.QCI3.PLMN Number of setup failures of E-RABs with a QCI of 3 Multi-mode: None Radio Bearer Management
because of a low uplink satisfaction rate for a specific GSM: None Radio Bearer Management
operator UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008 RAN Sharing with Common Carrier
LBFD-002023 RAN Sharing with Dedicated Carrier
TDLBFD-002023 RAN Sharing with Common Carrier
LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037
TDLOFD-001036
TDLOFD-001037

1526736705 L.E-RAB.FailEst.NoRadioRes.ULSatis.QCI4.PLMN Number of setup failures of E-RABs with a QCI of 4 Multi-mode: None Radio Bearer Management
because of a low uplink satisfaction rate for a specific GSM: None Radio Bearer Management
operator UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008 RAN Sharing with Common Carrier
LBFD-002023 RAN Sharing with Dedicated Carrier
TDLBFD-002023 RAN Sharing with Common Carrier
LOFD-001036 RAN Sharing with Dedicated Carrier
LOFD-001037
TDLOFD-001036
TDLOFD-001037

1526736856 L.E-RAB.FailEst.NoRadioRes.DLSatis.PTT Number of E-RAB setup failures for PTT services Multi-mode: None Radio Bearer Management
because of a low downlink satisfaction rate GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008 Enhanced Extended QCI
LBFD-002023 Enhanced Extended QCI
TDLBFD-002023
LOFD-081218
TDLOFD-081215

1526736857 L.E-RAB.FailEst.NoRadioRes.ULSatis.PTT Number of setup failures of E-RABs for PTT services Multi-mode: None Radio Bearer Management
because of a low uplink satisfaction rate GSM: None Radio Bearer Management
UMTS: None Admission Control
LTE: LBFD-002008 Admission Control
TDLBFD-002008 Enhanced Extended QCI
LBFD-002023 Enhanced Extended QCI
TDLBFD-002023
LOFD-081218
TDLOFD-081215

1526736866 L.Cell.UserSpec.PrepEmp.PrepAtt.Num Number of times preemptions are triggered by the Multi-mode: None Admission Control
limitation of the UE number specification GSM: None Admission Control
UMTS: None Radio/transport resource pre-emption
LTE: LBFD-002023 Radio/transport resource pre-emption
TDLBFD-002023
LOFD-00102901
TDLOFD-00102901

1526736867 L.Cell.UserLic.Limit.Num.PLMN Number of times the licensed number of UEs is limited Multi-mode: None Admission Control
for a specific operator GSM: None Admission Control
UMTS: None Radio/transport resource pre-emption
LTE: LBFD-002023 Radio/transport resource pre-emption
TDLBFD-002023 RAN Sharing with Common Carrier
LOFD-00102901 Hybrid RAN Sharing
TDLOFD-00102901 RAN Sharing with Common Carrier
LOFD-001036

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

LOFD-070206
TDLOFD-001036

1526736868 L.Cell.UserLic.PrepEmp.Succ.Num.PLMN Number of successful preemptions triggered by the Multi-mode: None Admission Control
limitation of the licensed number of UEs for a specific GSM: None Admission Control
operator UMTS: None Radio/transport resource pre-emption
LTE: LBFD-002023 Radio/transport resource pre-emption
TDLBFD-002023 RAN Sharing with Common Carrier
LOFD-00102901 Hybrid RAN Sharing
TDLOFD-00102901 RAN Sharing with Common Carrier
LOFD-001036
LOFD-070206
TDLOFD-001036

1526736869 L.Cell.UserLic.Limit.Num Number of times the licensed number of UEs is limited Multi-mode: None Admission Control
GSM: None Admission Control
UMTS: None Radio/transport resource pre-emption
LTE: LBFD-002023 Radio/transport resource pre-emption
TDLBFD-002023
LOFD-00102901
TDLOFD-00102901

1526736870 L.Cell.UserLic.PrepEmp.Succ.Num Number of successful preemptions triggered by the Multi-mode: None Admission Control
limitation of the licensed number of UEs GSM: None Admission Control
UMTS: None Radio/transport resource pre-emption
LTE: LBFD-002023 Radio/transport resource pre-emption
TDLBFD-002023
LOFD-00102901
TDLOFD-00102901

10 Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

11 Reference Documents

1. 3GPP TS 23.203, "Policy and charging control architecture"


2. 3GPP TS 23.401, "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access"
3. 3GPP TS 36.306, "User Equipment (UE) radio access capabilities"
4. 3GPP TS 36.321, "Medium Access Control(MAC) protocol specification"
5. 3GPP TS 36.331, "Radio Resource Control (RRC)"
6. 3GPP TS 36.413, "S1 Application Protocol (S1AP)"
7. Scheduling Feature Parameter Description
8. Transport Resource Management Feature Parameter Description
9. Flow Control Feature Parameter Description
10. Flexible User Steering Feature Parameter Description
11. Physical Channel Resource Management Feature Parameter Description

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

eRAN
AQM Feature Parameter Description
Issue 01

Date 2015-03-23

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: support@huawei.com

2.4 Contents
1 About This Document
1.1 Scope
1.2 Intended Audience
1.3 Change History

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

1.4 Differences Between eNodeB Types


2 Overview
3 Technical Description
4 Network Impact
4.1 LOFD-001027 Active Queue Management (AQM)
5 Related Features
5.1 LOFD-001027 Active Queue Management (AQM)
6 Engineering Guidelines
6.1 When to Use AQM
6.2 Required Information
6.3 Planning
6.4 Deployment
6.4.1 Requirements
6.4.2 Data Preparation
6.4.3 Activation
6.4.4 Activation Observation
6.4.5 Reconfiguration
6.4.6 Deactivation
6.5 Performance Monitoring
6.6 Parameter Optimization
6.7 Troubleshooting
7 Parameters
8 Counters
9 Glossary
10 Reference Documents

1 About This Document

1 Scope
This document describes LOFD-001027 Active Queue Management (AQM), including its technical principles, related features, network impact, and engineering guidelines.
This document applies to the following types of eNodeBs.

eNodeB Type Model

Macro 3900 series eNodeB

Micro BTS3202E

LampSite DBS3900 LampSite

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 FDD eNodeB.

2 Intended Audience
This document is intended for personnel who:

Need to understand the features described herein


Work with Huawei products

3 Change History
This section provides information about the changes in different document versions. There are two types of changes:

Feature change
Changes in features and parameters of a specified version as well as the affected entities
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

RAN 8.1 01 (2015-03-23)

This issue does not include any changes.

RAN8.1 Draft A (2015-01-15)

Compared with Issue 02 (2014-05-30) of eRAN7.0, Draft A (2015-01-15) of eRAN8.1 includes the following changes.

Change Type Change Description Parameter Change Affected Entity

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

Feature change None None -

Editorial change Modified the description in 6.7 Troubleshooting. None Macro, micro, and LampSite eNodeBs

4 Differences Between eNodeB Types


The features described in this document are implemented in the same way on macro, micro, and LampSite eNodeBs.

2 Overview

A radio link has a lower bandwidth than a wired link and the bandwidth of a radio link fluctuates. A large amount of data buffered on the eNodeB may congest the air interface during downlink data transmission. Therefore, AQM is introduced, which actively controls the buffer queue length to prevent congestion deterioration.
When air interface resources are insufficient, AQM estimates the buffer queue length and selectively discards Transmission Control Protocol (TCP) packets in case of congestion. Congestion control at the sender is triggered as early as possible to prevent congestion deterioration. As a result, the transmission delay of
interactive services (such as web browsing) decreases, and user experience is therefore improved. The feature also ensures the fair scheduling of different services.
AQM has the following benefits:

Detects congestion in the buffer queue as early as possible and minimizes the probability of congestion deterioration by discarding packets.
Maintains a relatively short queue to reach a tradeoff between the data throughput and transmission delay.
Avoids global synchronization caused by simultaneous overflow of multiple data streams.

NOTE:
Packets often burst when they arrive at a buffer queue. When the queue is full or nearly full, a large number of packets are lost. Upon detection of lost packets, multiple TCP senders sharply decrease the send window by reducing the amount of data to transmit. Then, the packet arrival rate declines quickly and the network
is no longer congested. The TCP senders start to increase the transmission rate after detecting that the network is not congested, which again results in network congestion. This problem occurs repeatedly, which is called global synchronization.

Huawei AQM applies to non-GBR (GBR is short for guaranteed bit rate) services.
AQM is controlled by the CellAlgoSwitch.AqmAlgoSwitch parameter. For details about the configuration, see  6 Engineering Guidelines.

3 Technical Description

Due to the limitation of resource capacity and processing capability of networks, congestion can become a bottleneck in network development. End-to-end congestion control technologies in TCP have been the main methods used to control IP network congestion. However, UEs at the network edge may not obtain accurate
information about the network status in time. Therefore, these TCP congestion control technologies cannot solve all problems in networks. To address this problem, node-based congestion control technologies are developed. AQM is one such node-based congestion control technology.
As an IP network node, an eNodeB uses AQM to detect buffer queues. If AQM detects that the number of packets in a buffer queue (that is, the queue length) exceeds a specified threshold, it discards TCP packets selectively based on TCP port numbers. As a result, the amount of data is reduced, the delay of interactive
services is reduced, and fair scheduling among data streams is improved.
The working area of AQM is divided into normal, congestion avoidance, and congestion control areas based on the minimum and maximum congestion thresholds. Figure 3-1 shows the AQM working areas. In this figure, Max represents the maximum packet loss rate of a non-GBR service in the congestion avoidance area,
and the red lines denote the packet discard rate.
Figure 3-1 AQM working areas

AQM calculates the average queue length and compares it with the minimum and maximum congestion thresholds. AQM then performs different operations under each of the following conditions:

Average queue length ≤ Minimum congestion threshold


In the normal area, AQM does not discard any packets because the queue is not congested.

Minimum congestion threshold < Average queue length < Maximum congestion threshold
In the congestion avoidance area, AQM discards some packets because the queue is congested. The number of discarded packets increases along with the amount of data successfully sent to the eNodeB.

Average queue length ≥ Maximum congestion threshold


In the congestion control area, AQM discards every newly arrived packet because the queue is severely congested.

The minimum congestion threshold is automatically calculated by the eNodeB based on the real-time data rate over the air interface and requires no manual setting. The maximum congestion threshold is the minimum congestion threshold multiplied by eight.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

4 Network Impact

1 LOFD-001027 Active Queue Management (AQM)


stem Capacity

When AQM is enabled, the processing delay of downlink packets carried by non-GBR bearers decreases. Therefore, the delay of delay-sensitive services, such as HTTP services and small file downloads, decreases. The processing delay can be monitored by dividing the value of the L.Traffic.DL.PktDelay.Time.QCI.x
counter by the value of the L.Traffic.DL.PktDelay.Num.QCI.x counter. However, when AQM is enabled, the cell throughput decreases, some UEs' throughput fluctuates, or the throughput for non-GBR services decreases. If GRB and non-GBR services coexist in a cell, and the actual GBR service rate is smaller than the
subscribed GBR service rate, the scheduling opportunities for GBR services increase because the throughput for non-GBR services decreases. Therefore, the throughput for GRB services increases.

etwork Performance

The network key performance indicators (KPIs) related to the system throughput fluctuate as follows:

If a cell has both cell edge users (CEUs) and cell center users (CCUs), AQM will decrease the throughput of CEUs because services of CEUs are easily congested. There is a low probability that services of CCUs are congested, and therefore AQM will increase the throughput of CCUs and the increased
throughput is larger than the decreased throughput for CEUs. In this case, the cell throughput increases.
If a cell has only CEUs, the cell throughput will decrease because AQM decreases the throughput of CEUs.
If a cell has only CCUs, the impacts of AQM on the cell throughput can be ignored.

5 Related Features

1 LOFD-001027 Active Queue Management (AQM)


erequisite Features

None

utually Exclusive Features

None

pacted Features

None

6 Engineering Guidelines

1 When to Use AQM


AQM is used for queue management of user plane data in LTE networks.
AQM applies to downlink hybrid-service scenarios where multiple TCP services are running on one bearer. In such scenarios, the TCP services with a larger traffic volume occupy air interface resources for a long time. The air interface resources for the TCP services with a smaller traffic volume are insufficient, and a large
amount of data is buffered in the eNodeB. As a result, the latency of services that require a quick response (real-time services such as web browsing or small-file download) is prolonged, and user experience deteriorates sharply.
Huawei AQM applies only to non-GBR services.
Enable AQM in the following scenarios:

The congestion probability and packet loss rate in specific cells are abnormally high, user experience with interactive services deteriorates, and you have determined that the problem occurs due to a large amount of downlink data. If the problem is not caused by a large amount of downlink data, enabling AQM
may cause further deterioration of the service quality.
Multiple TCP-based bit torrent (BT) services are running or large files are being downloaded while lots of interactive services are running on the network.

In the following scenarios, AQM brings no gain or could even have slightly negative effects:

When there are both TCP and User Datagram Protocol (UDP) services on a bearer, discarding TCP and UDP packets in this scenario can reduce the TCP traffic but not the UDP traffic.

Packets are randomly discarded by AQM during network congestion. If packets of interactive services are discarded, user experience with these services deteriorates.
The data rate of CEUs fluctuates due to interference. In this scenario, the eNodeB is not congested and AQM brings little gain.
Discarding packets can cause throughput fluctuations, especially when there are only a small number (for example, one or two) of TCP connections.
The downlink throughput on a bearer exceeds 30 Mbit/s. In this scenario, non-GBR services are not congested and AQM brings little gain.

2 Required Information
The values of the following counters must be collected before AQM is deployed.

Counter ID Counter Name Description

1526727922 L.Traffic.DL.PktDelay.Time.QCI.6 Processing delay of downlink PDCP SDUs for DRB services with the QCI of 6 in a cell

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

1526727925 L.Traffic.DL.PktDelay.Time.QCI.7 Processing delay of downlink PDCP SDUs for DRB services with the QCI of 7 in a cell

526727928 L.Traffic.DL.PktDelay.Time.QCI.8 Processing delay of downlink PDCP SDUs for DRB services with the QCI of 8 in a cell

1526727931 L.Traffic.DL.PktDelay.Time.QCI.9 Processing delay of downlink PDCP SDUs for DRB services with the QCI of 9 in a cell

1526727923 L.Traffic.DL.PktDelay.Num.QCI.6 Number of successfully transmitted downlink PDCP SDUs for DRB services with the QCI of 6 in a cell

1526727926 L.Traffic.DL.PktDelay.Num.QCI.7 Number of successfully transmitted downlink PDCP SDUs for DRB services with the QCI of 7 in a cell

1526727929 L.Traffic.DL.PktDelay.Num.QCI.8 Number of successfully transmitted downlink PDCP SDUs for DRB services with the QCI of 8 in a cell

1526727932 L.Traffic.DL.PktDelay.Num.QCI.9 Number of successfully transmitted downlink PDCP SDUs for DRB services with the QCI of 9 in a cell

Assume that the value of L.Traffic.DL.PktDelay.Time.QCI.x/L.Traffic.DL.PktDelay.Num.QCI.x (x indicates the QCI of a service) is A. If A is larger than 500 ms/packet for a non-GBR service with the QCI of x and the value of the Discard timer(ms) parameter for the QCI of x is larger than 500 ms, it is recommended that
AQM be enabled. The Discard timer(ms) parameter value can be queried by running the LST RLCPDCPPARAGROUP command.

3 Planning
None

4 Deployment

6.4.1 Requirements
This feature has no requirements for the operating environment or transmission networking. This feature does not depend on and is not mutually exclusive with other features.
The operator has purchased and activated the license for the feature listed in Table 6-1.

Table 6-1 License information for AQM

Feature ID Feature Name Model License Control Item NE Sales Unit

LOFD-001027 Active Queue Management(AQM) LT1S000AQM00 Active Queue Management(AQM)(FDD) eNodeB per RRC Connected User

6.4.2 Data Preparation


This section describes the data that you need to collect for setting parameters. Mandatory 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:

Network plan (negotiation required): parameter values planned by the operator and negotiated with the EPC or peer transmission equipment
Network plan (negotiation not required): parameter values planned and set by the operator
User-defined: parameter values set by users.

andatory Data

The following table describes the parameters that must be set in the CellAlgoSwitch managed object (MO) to configure the AQM algorithm switch.

Parameter Name Parameter ID Data Source Setting Notes

Local cell ID CellAlgoSwitch.LocalCellId Network plan (negotiation not required) Set this parameter to the local ID of the cell where the AQM algorithm
will be enabled.

AQM algorithm switch CellAlgoSwitch.AqmAlgoSwitch Network plan (negotiation not required) Set this parameter based on the network plan.

enario-specific Data

None

6.4.3 Activation
sing 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 into the Configuration Management Express (CME) for batch configuration. For detailed instructions, see section "Creating eNodeBs in
Batches" in the initial configuration guide for the eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized file, depending on the following conditions:

If the MOs in Table 6-2 are contained in a scenario-specific summary data file, set the parameters in the MOs, and then verify the parameters and save the file.
If some MOs in Table 6-2 are not contained in a scenario-specific summary data file, customize a summary data file to include the MOs before you can set the parameters.

Table 6-2 Parameters for activating AQM

MO Sheet in the Summary Data File Parameter Group Remarks

CellAlgoSwitch CellAlgoSwitch Local Cell ID, AQM algorithm switch None

sing the CME to Perform Batch Configuration for Existing eNodeBs

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:

1. Choose CME > Advanced > Customize Summary Data File (U2000 client mode), or choose Advanced > Customize Summary Data File (CME client mode), to customize a summary data file for batch reconfiguration.

NOTE:
For context-sensitive help on a current task in the client, press F1.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

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.
3. In the summary data file, set the parameters in the MOs listed in Table 6-2 and close the file.
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.
5. 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.

sing the CME to Perform Single Configuration

On the CME, set the parameters listed in section "Data Preparation" for a single eNodeB. The procedure is as follows:

1. In the planned data area, click Base Station in the upper left corner of the configuration window.
2. In area 1 shown in Figure 6-1, select the eNodeB to which the MOs belong.
Figure 6-1 MO search and configuration window

3. On the Search tab page in area 2, enter an MO name, for example, CELL.
4. In area 3, double-click the MO in the Object Name column. All parameters in this MO are displayed in area 4.
5. Set the parameters in area 4 or 5.
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.

sing MML Commands

To enable AQM, run the MOD CELLALGOSWITCH command with the AqmAlgoSwitch check box selected under the CellAlgoSwitch.AqmAlgoSwitch parameter.

ML Command Examples

MOD CELLALGOSWITCH:LOCALCELLID=0,AQMALGOSWITCH=AqmAlgoSwitch-1;

6.4.4 Activation Observation


Before the observation, ensure that:

The downlink throughput of the user's computer is lower than 10 Mbit/s. The downlink throughput can be controlled by decreasing the cell bandwidth or increasing the number of UEs in the cell.
The operator's computer can normally access the network, connect to the download server, and run FTP download services.
Multiple large files whose sizes are larger than 1 GB and multiple small files are available on the server for the download.

NOTE:
Whether a file is a small file depends on the downlink throughput of the user's computer. If the latency of downloading a file while downloading one or multiple large files is within 10 seconds, the file is a small file.

The observation procedure is as follows:

1. Run the MOD CELLALGOSWITCH command with the AqmAlgoSwitch check box selected under the AQM algorithm switch parameter. Then, enable the computer to access the network.
MML Command Example:
MOD CELLALGOSWITCH:LOCALCELLID=0,AQMALGOSWITCH=AqmAlgoSwitch-1;
2. Download one or more large files and a small file simultaneously. Then, record the small file download latency. Repeat the test and average the recorded values as the small file download latency with AQM enabled.
3. Run the MOD CELLALGOSWITCH command with the AqmAlgoSwitch check box cleared under the AQM algorithm switch parameter. Then, enable the computer to reaccess the network.
MML Command Example:
MOD CELLALGOSWITCH:LOCALCELLID=0,AQMALGOSWITCH=AqmAlgoSwitch-0;
4. Download one or more large files and a small file simultaneously. Then, record the small file download latency. Repeat the test and average the recorded values as the small file download latency with AQM disabled.
5. Compare the two average values and verify that the time of small file download is shortened when AQM is enabled.

6.4.5 Reconfiguration

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

None

6.4.6 Deactivation
sing 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 Using the CME to
Perform Batch Configuration for Existing eNodeBs. In the deactivation procedure, modify parameters according to Table 6-3.

Table 6-3 Parameters for deactivating AQM

MO Sheet in the Summary Data File Parameter Group Remarks

CellAlgoSwitch CellAlgoSwitch AQMalgorithm switch Set the AqmAlgoSwitch parameter to 0.

sing the CME to Perform Single Configuration

On the CME, set parameters according to Table 6-3. For detailed instructions, see Using the CME to Perform Single Configuration for feature deactivation.

sing MML Commands

To disable AQM, run the MOD CELLALGOSWITCH command with the AqmAlgoSwitch check box cleared under the CellAlgoSwitch.AqmAlgoSwitch parameter.

ML Command Examples

MOD CELLALGOSWITCH:LOCALCELLID=0,AQMALGOSWITCH=AqmAlgoSwitch-0;

5 Performance Monitoring
The following counters are used to monitor the AQM performance.

Counter ID Counter Name Description

1526727922 L.Traffic.DL.PktDelay.Time.QCI.6 Processing delay of downlink PDCP SDUs for DRB services with the QCI of 6 in a cell

1526727925 L.Traffic.DL.PktDelay.Time.QCI.7 Processing delay of downlink PDCP SDUs for DRB services with the QCI of 7 in a cell

1526727928 L.Traffic.DL.PktDelay.Time.QCI.8 Processing delay of downlink PDCP SDUs for DRB services with the QCI of 8 in a cell

1526727931 L.Traffic.DL.PktDelay.Time.QCI.9 Processing delay of downlink PDCP SDUs for DRB services with the QCI of 9 in a cell

1526727923 L.Traffic.DL.PktDelay.Num.QCI.6 Number of successfully transmitted downlink PDCP SDUs for DRB services with the QCI of 6 in a cell

1526727926 L.Traffic.DL.PktDelay.Num.QCI.7 Number of successfully transmitted downlink PDCP SDUs for DRB services with the QCI of 7 in a cell

1526727929 L.Traffic.DL.PktDelay.Num.QCI.8 Number of successfully transmitted downlink PDCP SDUs for DRB services with the QCI of 8 in a cell

1526727932 L.Traffic.DL.PktDelay.Num.QCI.9 Number of successfully transmitted downlink PDCP SDUs for DRB services with the QCI of 9 in a cell

1526726863 L.PDCP.Tx.Disc.Trf.SDU.QCI.6 Number of downlink traffic SDUs discarded by the PDCP layer for services with the QCI of 6 in a cell

1526726869 L.PDCP.Tx.Disc.Trf.SDU.QCI.7 Number of downlink traffic SDUs discarded by the PDCP layer for services with the QCI of 7 in a cell

1526726875 L.PDCP.Tx.Disc.Trf.SDU.QCI.8 Number of downlink traffic SDUs discarded by the PDCP layer for services with the QCI of 8 in a cell

1526726881 L.PDCP.Tx.Disc.Trf.SDU.QCI.9 Number of downlink traffic SDUs discarded by the PDCP layer for services with the QCI of 9 in a cell

After AQM is enabled, the average processing delay of downlink PDCP SDUs for DRB services will decrease slightly and the number of downlink traffic SDUs discarded by the PDCP layer will increase slightly.

NOTE:
Average processing delay of downlink PDCP SDUs for a DRB service = Value of the counter L.Traffic.DL.PktDelay.Time.QCI.x/Value of the counter L.Traffic.DL.PktDelay.Num.QCI.x. x indicates the QCI of the service.

6 Parameter Optimization
None

7 Troubleshooting
ult Description

AQM is enabled but brings no gains to the system.

ult Handling

1. Run the LST CELLALGOSWITCH command to check that the AQM switch has been turned on.
MML Command example:
LST CELLALGOSWITCH:LOCALCELLID=0;
2. Download one or more large files, and perform ping operations simultaneously. Maintain the test for at least 2 minutes, and monitor the ping delay changes. If the delay is shorter than 500 ms, add more downloading threads. When the delay reaches 500 ms, start downloading a small file. If the test result still
indicates no gains from AQM, contact Huawei technical support.

NOTE:
When the delay reaches 500 ms, AQM discards some packets. You can perform ping operations to check whether AQM brings gains. If AQM brings gains, the end-to-end ping delay is reduced to 500 ms regardless of the number of TCP threads (delay caused by the EPC is not considered).

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

7 Parameters

Table 7-1 Parameters

MO Parameter ID MML Command Feature ID Feature Name Description

CellAlgoSwitch AqmAlgoSwitch MOD CELLALGOSWITCH LOFD-001027 / TDLOFD- Active Queue Meaning: Indicates the switch that is used to enable and disable the Active Queue Management (AQM) algorithm. If this switch is set to ON,
LST CELLALGOSWITCH 001027 Management (AQM) the AQM function is enabled to prevent or control congestion. The length of the PDCP packet queue is maintained at a relatively small value
to help achieve an appropriate trade-off between throughput and time latency. If this switch is set to OFF, the AQM function is disabled.
GUI Value Range: AqmAlgoSwitch
Unit: None
Actual Value Range: AqmAlgoSwitch
Default Value: AqmAlgoSwitch:Off

CellAlgoSwitch LocalCellId DSP None None Meaning: Indicates the local ID of the cell. It uniquely identifies a cell within a BS.
CELLULCAMCCLUSTER GUI Value Range: 0~255
LST CELLALGOSWITCH Unit: None
MOD CELLALGOSWITCH Actual Value Range: 0~255
Default Value: None

8 Counters

Table 8-1 Counters

Counter ID Counter Name Counter Description Feature ID Feature Name

1526726863 L.PDCP.Tx.Disc.Trf.SDU.QCI.6 Number of downlink PDCP SDUs discarded for Multi-mode: None Radio Bearer Management
services carried on DRBs with a QCI of 6 in a cell GSM: None Radio Bearer Management
UMTS: None Basic Scheduling
LTE: LBFD-002008 Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025

1526726869 L.PDCP.Tx.Disc.Trf.SDU.QCI.7 Number of downlink PDCP SDUs discarded for Multi-mode: None Radio Bearer Management
services carried on DRBs with a QCI of 7 in a cell GSM: None Radio Bearer Management
UMTS: None Basic Scheduling
LTE: LBFD-002008 Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025

1526726875 L.PDCP.Tx.Disc.Trf.SDU.QCI.8 Number of downlink PDCP SDUs discarded for Multi-mode: None Radio Bearer Management
services carried on DRBs with a QCI of 8 in a cell GSM: None Radio Bearer Management
UMTS: None Basic Scheduling
LTE: LBFD-002008 Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025

1526726881 L.PDCP.Tx.Disc.Trf.SDU.QCI.9 Number of downlink PDCP SDUs discarded for Multi-mode: None Radio Bearer Management
services carried on DRBs with a QCI of 9 in a cell GSM: None Radio Bearer Management
UMTS: None Basic Scheduling
LTE: LBFD-002008 Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025

1526727922 L.Traffic.DL.PktDelay.Time.QCI.6 Total processing delay of downlink PDCP SDUs for Multi-mode: None Radio Bearer Management
DRB services with the QCI of 6 in a cell GSM: None Radio Bearer Management
UMTS: None Basic Scheduling
LTE: LBFD-002008 Basic Scheduling
TDLBFD-002008
LBFD-002025

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

TDLBFD-002025

1526727923 L.Traffic.DL.PktDelay.Num.QCI.6 Number of successfully transmitted downlink PDCP Multi-mode: None Radio Bearer Management
SDUs for DRB services with the QCI of 6 in a cell GSM: None Radio Bearer Management
UMTS: None Basic Scheduling
LTE: LBFD-002008 Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025

1526727925 L.Traffic.DL.PktDelay.Time.QCI.7 Total processing delay of downlink PDCP SDUs for Multi-mode: None Radio Bearer Management
DRB services with the QCI of 7 in a cell GSM: None Radio Bearer Management
UMTS: None Basic Scheduling
LTE: LBFD-002008 Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025

1526727926 L.Traffic.DL.PktDelay.Num.QCI.7 Number of successfully transmitted downlink PDCP Multi-mode: None Radio Bearer Management
SDUs for DRB services with the QCI of 7 in a cell GSM: None Radio Bearer Management
UMTS: None Basic Scheduling
LTE: LBFD-002008 Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025

1526727928 L.Traffic.DL.PktDelay.Time.QCI.8 Total processing delay of downlink PDCP SDUs for Multi-mode: None Radio Bearer Management
DRB services with the QCI of 8 in a cell GSM: None Radio Bearer Management
UMTS: None Basic Scheduling
LTE: LBFD-002008 Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025

1526727929 L.Traffic.DL.PktDelay.Num.QCI.8 Number of successfully transmitted downlink PDCP Multi-mode: None Radio Bearer Management
SDUs for DRB services with the QCI of 8 in a cell GSM: None Radio Bearer Management
UMTS: None Basic Scheduling
LTE: LBFD-002008 Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025

1526727931 L.Traffic.DL.PktDelay.Time.QCI.9 Total processing delay of downlink PDCP SDUs for Multi-mode: None Radio Bearer Management
DRB services with the QCI of 9 in a cell GSM: None Radio Bearer Management
UMTS: None Basic Scheduling
LTE: LBFD-002008 Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025

1526727932 L.Traffic.DL.PktDelay.Num.QCI.9 Number of successfully transmitted downlink PDCP Multi-mode: None Radio Bearer Management
SDUs for DRB services with the QCI of 9 in a cell GSM: None Radio Bearer Management
UMTS: None Basic Scheduling
LTE: LBFD-002008 Basic Scheduling
TDLBFD-002008
LBFD-002025
TDLBFD-002025

1526729466 L.RLC.FirstPacketDelay.NonGBR.Index0 Number of times delay of the first RLC SDU for a non- Multi-mode: None Active Queue Management (AQM)
GBR bearer ranges within index 0 GSM: None LTE-A Introduction
UMTS: None
LTE: LOFD-001027
LAOFD-001001

1526729467 L.RLC.FirstPacketDelay.NonGBR.Index1 Number of times delay of the first RLC SDU for a non- Multi-mode: None Active Queue Management (AQM)
GBR bearer ranges within index 1 GSM: None LTE-A Introduction
UMTS: None
LTE: LOFD-001027
LAOFD-001001

1526729468 L.RLC.FirstPacketDelay.NonGBR.Index2 Number of times delay of the first RLC SDU for a non- Multi-mode: None Active Queue Management (AQM)
GBR bearer ranges within index 2 GSM: None LTE-A Introduction
UMTS: None
LTE: LOFD-001027

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

LAOFD-001001

1526729469 L.RLC.FirstPacketDelay.NonGBR.Index3 Number of times delay of the first RLC SDU for a non- Multi-mode: None Active Queue Management (AQM)
GBR bearer ranges within index 3 GSM: None LTE-A Introduction
UMTS: None
LTE: LOFD-001027
LAOFD-001001

1526729470 L.RLC.FirstPacketDelay.NonGBR.Index4 Number of times delay of the first RLC SDU for a non- Multi-mode: None Active Queue Management (AQM)
GBR bearer ranges within index 4 GSM: None LTE-A Introduction
UMTS: None
LTE: LOFD-001027
LAOFD-001001

1526729471 L.AQM.PacketDropNum.QCI.6 Number of packets discarded by AQM for services with Multi-mode: None Active Queue Management (AQM)
QCI of 6 GSM: None
UMTS: None
LTE: LOFD-001027

1526729472 L.AQM.PacketDropNum.QCI.7 Number of packets discarded by AQM for services with Multi-mode: None Active Queue Management (AQM)
QCI of 7 GSM: None
UMTS: None
LTE: LOFD-001027

1526729473 L.AQM.PacketDropNum.QCI.8 Number of packets discarded by AQM for services with Multi-mode: None Active Queue Management (AQM)
QCI of 8 GSM: None
UMTS: None
LTE: LOFD-001027

1526729474 L.AQM.PacketDropNum.QCI.9 Number of packets discarded by AQM for services with Multi-mode: None Active Queue Management (AQM)
QCI of 9 GSM: None
UMTS: None
LTE: LOFD-001027

9 Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

10 Reference Documents

None

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

eRAN
Carrier Aggregation Feature Parameter Description
Issue 02

Date 2015-04-30

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: support@huawei.com

2.5 Contents
1 About This Document
1.1 Scope
1.2 Intended Audience
1.3 Change History

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

1.4 Differences Between eNodeB Types


2 Overview
2.1 Introduction
2.2 Benefits
2.3 Architecture
3 Technical Description
3.1 Function Overview
3.1.1 Related Concepts
3.1.2 Usage Scenarios
3.1.2.1 Typical Scenarios
3.1.2.2 Atypical Scenarios
3.1.3 CA Features
3.1.3.1 LAOFD-001001 LTE-A Introduction
3.1.3.2 LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz
3.1.3.3 LAOFD-070201 Flexible CA from Multiple Carriers
3.1.3.4 LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU
3.1.3.5 LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul
3.1.3.6 LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial]
3.1.3.7 LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz
3.1.3.8 LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz
3.1.3.9 LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial]
3.1.3.10 MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial]
3.1.4 Band Combinations
3.2 Carrier Management
3.2.1 Overview
3.2.2 PCC Anchoring (at Initial Access)
3.2.2.1 CA-Group-based PCC Anchoring
3.2.2.2 Frequency-based or Adaptive PCC Anchoring
3.2.3 SCell Configuration
3.2.3.1 CA-Group-based SCell Configuration
3.2.3.2 Frequency-based SCell Configuration
3.2.3.3 Adaptive SCell Configuration
3.2.3.4 Load-based SCell Configuration
3.2.4 SCell Change
3.2.5 SCell Activation
3.2.6 SCell Deactivation
3.2.7 SCell Removal
3.2.8 PCC Anchoring (at RRC Connection Releases)
3.3 Other Key Techniques Under CA
3.3.1 Connection Management Under CA
3.3.2 Mobility Management Under CA
3.3.3 Admission and Congestion Control Under CA
3.3.4 Scheduling Under CA
3.3.5 MIMO Under CA
3.3.6 DRX Control Under CA
3.3.7 RAN Sharing Under CA
3.3.8 Power Backoff Under CA
3.3.9 MTA Under CA
4 Related Features
4.1 Features Related to LAOFD-001001 LTE-A Introduction
4.2 Features Related to LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz
4.3 Features Related to LAOFD-070201 Flexible CA from Multiple Carriers
4.4 Features Related to LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU
4.5 Features Related to LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul
4.6 Features Related to LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial]
4.7 Features Related to LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz
4.8 Features Related to LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz
4.9 Features Related to LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial]
4.10 Features Related to MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial]
5 Network Impact
5.1 LAOFD-001001 LTE-A Introduction
5.2 LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz
5.3 LAOFD-070201 Flexible CA from Multiple Carriers
5.4 LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU
5.5 LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

5.6 LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial]


5.7 LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz
5.8 LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz
5.9 LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial]
5.10 MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial]
6 Engineering Guidelines for LAOFD-001001 LTE-A Introduction and LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz
6.1 When to Use LAOFD-001001 and LAOFD-001002
6.2 Required Information
6.3 Planning
6.4 Deployment
6.4.1 Requirements
6.4.2 Data Preparation
6.4.3 Precautions
6.4.4 Hardware Adjustment
6.4.5 Activation
6.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
6.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs
6.4.5.3 Using the CME to Perform Single Configuration
6.4.5.4 Using Feature Operation and Maintenance on the CME
6.4.5.5 Using MML Commands
6.4.6 Activation Observation
6.4.7 Deactivation
6.4.7.1 Using the CME to Perform Batch Configuration
6.4.7.2 Using the CME to Perform Single Configuration
6.4.7.3 Using MML Commands
6.5 Performance Monitoring
6.6 Parameter Optimization
6.7 Troubleshooting
7 Engineering Guidelines for LAOFD-070201 Flexible CA from Multiple Carriers
7.1 When to Use LAOFD-070201
7.2 Required Information
7.3 Planning
7.4 Deployment
7.4.1 Requirements
7.4.2 Data Preparation
7.4.3 Precautions
7.4.4 Hardware Adjustment
7.4.5 Activation
7.4.6 Activation Observation
7.4.7 Deactivation
7.5 Performance Monitoring
7.6 Parameter Optimization
7.7 Troubleshooting
8 Engineering Guidelines for LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU
8.1 When to Use LAOFD-070202
8.2 Required Information
8.3 Planning
8.4 Deployment
8.4.1 Requirements
8.4.2 Data Preparation
8.4.3 Precautions
8.4.4 Hardware Adjustment
8.4.5 Activation
8.4.6 Activation Observation
8.4.7 Deactivation
8.5 Performance Monitoring
8.6 Parameter Optimization
8.7 Troubleshooting
9 Engineering Guidelines for LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul
9.1 When to Use LAOFD-080201
9.2 Required Information
9.3 Planning
9.4 Deployment
9.4.1 Requirements
9.4.2 Data Preparation

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

9.4.3 Precautions
9.4.4 Hardware Adjustment
9.4.5 Activation
9.4.6 Activation Observation
9.4.7 Deactivation
9.5 Performance Monitoring
9.6 Parameter Optimization
9.7 Troubleshooting
10 Engineering Guidelines for LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial]
10.1 When to Use LAOFD-080202
10.2 Required Information
10.3 Planning
10.4 Deployment
10.4.1 Requirements
10.4.2 Data Preparation
10.4.3 Precautions
10.4.4 Hardware Adjustment
10.4.5 Activation
10.4.6 Activation Observation
10.4.7 Deactivation
10.5 Performance Monitoring
10.6 Parameter Optimization
10.7 Troubleshooting
11 Engineering Guidelines for LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz and LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz
11.1 When to Use LAOFD-080207 and LAOFD-080208
11.2 Required Information
11.3 Planning
11.4 Deployment
11.4.1 Requirements
11.4.2 Data Preparation
11.4.3 Precautions
11.4.4 Hardware Adjustment
11.4.5 Activation
11.4.6 Activation Observation
11.4.7 Deactivation
11.5 Performance Monitoring
11.6 Parameter Optimization
11.7 Troubleshooting
12 Engineering Guidelines for LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial]
12.1 When to Use LAOFD-081237
12.2 Required Information
12.3 Planning
12.4 Deployment
12.4.1 Requirements
12.4.2 Data Preparation
12.4.3 Precautions
12.4.4 Hardware Adjustment
12.4.5 Activation
12.4.6 Activation Observation
12.4.7 Deactivation
12.5 Performance Monitoring
12.6 Parameter Optimization
12.7 Troubleshooting
13 Engineering Guidelines for MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial]
13.1 When to Use MRFD-101222
13.2 Required Information
13.3 Planning
13.4 Deployment
13.4.1 Requirements
13.4.2 Data Preparation
13.4.3 Precautions
13.4.4 Hardware Adjustment
13.4.5 Activation
13.4.6 Activation Observation
13.4.7 Deactivation

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

13.5 Performance Monitoring


13.6 Parameter Optimization
13.7 Troubleshooting
14 Parameters
15 Counters
16 Glossary
17 Reference Documents

1 About This Document

1 Scope
This document describes carrier aggregation (CA), including its technical principles, related features, network impact, and engineering guidelines. This document covers the following features:

LAOFD-001001 LTE-A Introduction


LAOFD-00100101 Intra-Band Carrier Aggregation for Downlink 2CC in 20MHz
LAOFD-00100102 Inter-Band Carrier Aggregation for Downlink 2CC in 20MHz
LAOFD-00100103 Support of UE Category 6
LAOFD-00100104 Support of UE Category 7
LAOFD-00100105 Support of UE Category 9
LAOFD-00100106 Support of UE Category 10

LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz


LAOFD-070201 Flexible CA from Multiple Carriers
LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU
LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul
LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial]
LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz
LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz
LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial]
MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial]

A trial feature is a feature that customers can use without paying for the license fee in the current version. In a later version, a trial feature may be deleted or become an optional feature. The license fee is required for optional features.
Before using a trial feature, customers need to sign a memorandum of understanding (MoU) with Huawei.
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 Type Model

Macro 3900 series eNodeB

Micro BTS3202E

LampSite DBS3900 LampSite

2 Intended Audience
This document is intended for personnel who:

Need to understand the features described herein


Work with Huawei products

3 Change History
This section provides information about the changes in different document versions. There are two types of changes:

Feature change
Changes in features and parameters of a specified version as well as the affected entities
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.

RAN8.1 02 (2015-04-30)

This issue includes the following changes.

Change Type Change Description Parameter Change Affected Entity

Feature change None None N/A

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

Editorial change Revised the description of the functional architecture. For details, see 2.3 Architecture. None N/A

Revised the description of typical scenario 5. For details, see 3.1.2.1 Typical Scenarios. None N/A

Modified the total bandwidth descriptions. For details, see 3.1.3 CA Features. None N/A

Revised the description of CA in networks that support downlink 4x4 MIMO. For details, see 3.1.3.9 LAOFD-081237 None N/A
Carrier Aggregation with DL 4x4 MIMO [Trial].

Modified band combinations. For details, see 3.1.4 Band Combinations. None N/A

Revised the description of adaptive configuration. For details, see 3.2.3.3 Adaptive SCell Configuration. None N/A

Revised the description of load-based SCell configuration. For details, see 3.2.3.4 Load-based SCell Configuration. None N/A

Modified the impacted features of LTE-A Introduction. For details, see 4.1 Features Related to LAOFD-001001 LTE-A None N/A
Introduction.

Modified the impacted features of Carrier Aggregation for Uplink 2CC. For details, see 4.6 Features Related to LAOFD- None N/A
080202 Carrier Aggregation for Uplink 2CC [Trial].

Revised the description of hardware planning. For details, see 6.3 Planning. None N/A

Modified the precautions for frequency-based configuration mode. For details, see 6.4.3 Precautions. None N/A

Revised the description of hardware adjustment. For details, see 6.4.4 Hardware Adjustment. None N/A

Modified the precautions for Inter-eNodeB CA based on Coordinated BBU. For details, see 8.4.3 Precautions. None N/A

Modified the transmission networking requirements and precautions for Inter-eNodeB CA based on Relaxed backhaul. None N/A
For details, see 9.4.1 Requirements and 9.4.3 Precautions.

Modified the procedure for deactivating Carrier Aggregation for Uplink 2CC. For details, see 10.4.7 Deactivation. None N/A

Modified the license requirement of downlink 3CC aggregation. For details, see 11.4.1 Requirements. None N/A

RAN8.1 01 (2015-03-23)

This issue includes the following changes.

Change Type Change Description Parameter Change Affected Entity

Feature change None None N/A

Editorial change Revised the descriptions of UE categories in 3.1.3.1 LAOFD-001001 LTE-A Introduction. None N/A

Revised the descriptions of Inter-eNodeB CA based on Coordinated BBU. For details, see: None N/A
3.1.3.4 LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU (feature description)
5.4 LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU (network impact)
8.4.5 Activation
8.4.7 Deactivation

Modified band combinations. For details, see 3.1.4 Band Combinations. None N/A

Modified the impact of LTE-A Introduction. For details, see 5.1 LAOFD-001001 LTE-A Introduction. None N/A

Modified precautions in 6.4.3 Precautions. None N/A

Revised the descriptions of the CME-based batch configuration procedure and the MML-based configuration None N/A
procedures. For details, see 6.4.5 Activation.

Revised the description of hardware planning for FDD+TDD CA in 13.3 Planning. None N/A

RAN8.1 Draft A (2015-01-15)

Compared with Issue 06 (2014-12-30) of eRAN7.0, Draft A (2015-01-15) of eRAN8.1 includes the following changes.

Change Type Change Description Parameter Change Affected Entity

Feature change Added CA in distributed multi-BBU interconnection scenarios. For details, see 3.1.3.4 LAOFD-070202 Inter-eNodeB CA None Macro eNodeBs
based on Coordinated BBU.

Added relaxed-backhaul-based inter-eNodeB CA. For details, see: Added the option RelaxedBackhaulCaSwitch to the parameter Macro and micro eNodeBs
3.1.3.5 LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul (feature description) ENodeBAlgoSwitch.CaAlgoSwitch.
4.5 Features Related to LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul
5.5 LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul (network impact)
9 Engineering Guidelines for LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul

Added uplink 2CC aggregation. For details, see: Added the option CaUl2CCSwitch to the parameter Macro eNodeBs
3.1.3.6 LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial] (feature description) CaMgtCfg.CellCaAlgoSwitch.
4.6 Features Related to LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial]
5.6 LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial] (network impact)

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

10 Engineering Guidelines for LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial]

Added downlink 3CC aggregation. For details, see: Added the option CaDl3CCSwitch to the parameter Macro eNodeBs
3.1.3.7 LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz (feature description) CaMgtCfg.CellCaAlgoSwitch.
3.1.3.8 LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz (feature description)
4.7 Features Related to LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz
4.8 Features Related to LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz
5.7 LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz (network impact)
5.8 LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz (network impact)
11 Engineering Guidelines for LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz and LAOFD-
080208 Carrier Aggregation for Downlink 3CC in 60MHz

Added AMBR-based control over the number of UEs configured with SCells. For details, see 3.2.3 SCell Configuration. Added the following parameters: Macro, micro, and LampSite eNodeBs
CaMgtCfg.CellMaxPccNumber
CaMgtCfg.CaAmbrThd

Added CA in DL 4x4 MIMO scenarios. For details, see: None Macro eNodeBs
3.1.3.9 LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial] (feature description)
4.9 Features Related to LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial]
5.9 LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial] (network impact)
12 Engineering Guidelines for LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial]

Added FDD+TDD CA. For details, see: Added the following options to the parameter Macro eNodeBs
3.1.3.10 MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial] (feature description) ENodeBAlgoSwitch.CaAlgoSwitch:
4.10 Features Related to MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial] InterFddTddCaSwitch
5.10 MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial] (network impact) CaDl4CCSwitch
13 Engineering Guidelines for MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial] Added the following parameters:
ENodeBFrameOffset.FddFrameOffset
ENodeBFrameOffset.TddFrameOffset
CellFrameOffset.LocalCellId
CellFrameOffset.FrameOffsetMode
CellFrameOffset.FrameOffset
Added the option FDDTDD to the parameter
CaGroup.CaGroupTypeInd.

Added implementation of features in CA scenarios. For details, see: None Macro, micro, and LampSite eNodeBs
3.3.8 Power Backoff Under CA
3.3.9 MTA Under CA

Added adaptive configuration mode. For details, see: Added the option AdpCaSwitch to the Macro, micro, and LampSite eNodeBs
3.2.1 Overview ENodeBAlgoSwitch.CaAlgoSwitch parameter.
3.2.2.2 Frequency-based or Adaptive PCC Anchoring
3.2.3.3 Adaptive SCell Configuration
6.4.2 Data Preparation
6.4.3 Precautions
6.4.5.5 Using MML Commands
6.4.7.3 Using MML Commands
6.6 Parameter Optimization

Added the following sub-features to LAOFD-001001 LTE-A Introduction, as described in 1.1 Scope and 3.1.3 CA None Macro, micro, and LampSite eNodeBs
Features:
LAOFD-00100103 Support of UE Category 6
LAOFD-00100104 Support of UE Category 7
LAOFD-00100105 Support of UE Category 9
LAOFD-00100106 Support of UE Category 10

Deleted the following sub-features from LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz (see 1.1 None Macro, micro, and LampSite eNodeBs
Scope and 3.1.3 CA Features):
LAOFD-00100201 Carrier Aggregation for Downlink 2CC in 40MHz
LAOFD-00100202 Support of UE Category 6

Added band combinations. For details, see 3.1.4 Band Combinations. None Macro, micro, and LampSite eNodeBs

Changed the name of LAOFD-070201 from "CA for Downlink 2CC From Multiple Carriers" to "Flexible CA from Multiple None Macro, micro, and LampSite eNodeBs
Carriers". For details, see:
3.1.3.3 LAOFD-070201 Flexible CA from Multiple Carriers (feature description)
4.3 Features Related to LAOFD-070201 Flexible CA from Multiple Carriers
5.3 LAOFD-070201 Flexible CA from Multiple Carriers (network impact)
7 Engineering Guidelines for LAOFD-070201 Flexible CA from Multiple Carriers

Added load-based SCell configuration. For details, see 3.2.3.4 Load-based SCell Configuration. Added the option SccSmartCfgSwitch to the parameter Macro, micro, and LampSite eNodeBs

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

ENodeBAlgoSwitch.CaAlgoSwitch.

Added PCC anchoring at RRC connection releases. For details, see 3.2.8 PCC Anchoring (at RRC Connection Added the option IdleModePccAnchorSwitch to the parameter Macro, micro, and LampSite eNodeBs
Releases). ENodeBAlgoSwitch.CaAlgoSwitch.

Editorial change None None N/A

4 Differences Between eNodeB Types


ature Support by Macro, Micro, and LampSite eNodeBs

Feature ID Feature Name Supported by Macro eNodeBs Supported by Micro eNodeBs Supported by LampSite eNodeBs

LAOFD-001001 LTE-A Introduction Yes Yes Yes

LAOFD-00100101 Intra-Band Carrier Aggregation for Downlink 2CC in 20MHz Yes Yes Yes

LAOFD-00100102 Inter-Band Carrier Aggregation for Downlink 2CC in 20MHz Yes Yes Yes

LAOFD-00100103 Support of UE Category 6 Yes Yes Yes

LAOFD-00100104 Support of UE Category 7 Yes Yes Yes

LAOFD-00100105 Support of UE Category 9 Yes Yes Yes

LAOFD-00100106 Support of UE Category 10 Yes Yes Yes

LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz Yes Yes Yes

LAOFD-070201 Flexible CA from Multiple Carriers Yes Yes Yes

LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU Yes No Yes

LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul Yes Yes No

LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial] Yes No Yes

LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz Yes No Yes

LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz Yes No Yes

LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial] Yes No No

MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial] Yes No No

nction Implementation in Macro, Micro, and LampSite eNodeBs

None

2 Overview

1 Introduction
3rd Generation Partnership Project (3GPP) requires LTE-Advanced networks to provide a downlink peak data rate of 1 Gbit/s. However, radio spectrum resources are so scarce that in most cases an operator owns only non-adjacent chunks of the spectrum. Due to the limited bandwidth of a single chunk of the spectrum,
the 1 Gbit/s data rate requirement is hard to meet.
To deal with this situation, 3GPP TR 36.913 of Release 10 introduced carrier aggregation (CA) to LTE-Advanced networks, allowing aggregation of contiguous or non-contiguous carriers. CA achieves wider bandwidths (a maximum of 100 MHz) and higher spectral efficiency (especially in spectrum refarming scenarios).
During CA, upper-layer data streams are mapped to individual component carriers (CCs) at the Media Access Control (MAC) layer in LTE-Advanced networks. An eNodeB constructs one or more (two or more in the case of spatial multiplexing) transport blocks (TBs) in each transmission time interval (TTI) for each CC.
Each CC uses its own hybrid automatic repeat request (HARQ) entities and link adaptation mechanism. Therefore, the LTE-Advanced system can inherit single-carrier-based physical layer designs for the LTE system.
Huawei eNodeBs allow three configuration modes: CA-group-based, frequency-based, and adaptive CA. Unless otherwise stated, the descriptions in this document apply to all three modes.

2 Benefits
aximized Resource Utilization

A CA-capable UE (referred to as CA UE in this document) can use idle resource blocks (RBs) on up to five CCs to maximize utilization of resources.

ficient Utilization of Non-contiguous Spectrum Chunks

With CA, an operator's non-contiguous spectrum chunks can be aggregated for efficient utilization.

etter User Experience

With CA enabled, a single UE can reach higher uplink and downlink peak data rates. On a network that serves a number of UEs, CA UEs with activated secondary serving cells (SCells) can use idle resources in their SCells and achieve increased throughput if the network is not overloaded.

3 Architecture
nctional Architecture

The functional architecture for CA includes primary component carrier (PCC) anchoring, SCell configuration, and transitions between SCell states. For details, see 3.2 Carrier Management. This architecture also includes special implementation of other features under CA, as described in 3.3 Other Key Techniques Under CA.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

Huawei CA operates in accordance with the following constraints, which are stipulated in 3GPP TS 36.300 of Release 10:

In the uplink or downlink, a CA UE supports the aggregation of up to five CCs, each with a maximum bandwidth of 20 MHz. Currently, Huawei eNodeBs support the aggregation of no more than three FDD CCs or a combination of four FDD and TDD CCs, each with a maximum bandwidth of 20 MHz.
CA UEs support asymmetric CA. A UE may use different numbers of CCs in the uplink and downlink. However, the number of CCs in the downlink must always be greater than or equal to the number of CCs in the uplink. In addition, the uplink CCs must be included in the set of downlink CCs. Currently, Huawei
eNodeBs support the aggregation of two CCs in the uplink and the aggregation of two CCs, three CCs, or a combination of four FDD and TDD CCs in the downlink.
Each CC uses the same frame structure as 3GPP Release 8 carriers to support backward compatibility.
3GPP Release 8 or 9 UEs are allowed to transmit and receive data on Release 10 CCs.

otocol Stack Architecture

The uplink and downlink air-interface protocol stack with CA enabled has the following characteristics:

A single radio bearer has only one Packet Data Convergence Protocol (PDCP) entity and one Radio Link Control (RLC) entity. In addition, the number of CCs at the physical layer is invisible to the RLC layer.
User-plane data scheduling at the MAC layer is performed separately for individual CCs.
Each CC has an independent set of transport channels and separate HARQ entities and retransmission processes.

Figure 2-1 shows the uplink and downlink air-interface protocol stack with CA enabled.

Figure 2-1 Uplink and downlink air-interface protocol stack with CA enabled

ARQ: automatic repeat request


ROHC: robust header compression

3 Technical Description

1 Function Overview

3.1.1 Related Concepts


Cell

A primary serving cell (PCell) is the cell on which a CA UE camps. In the PCell, the CA UE works in the same way as it does in a 3GPP Release 8 or Release 9 cell. The physical uplink control channel (PUCCH) of the UE exists only in the PCell.
For more details, see 3.3.1 Connection Management Under CA.

Cell

A secondary serving cell (SCell) is a cell that works at a different frequency from the PCell. The eNodeB configures an SCell for a CA UE through an RRC Connection Reconfiguration message. An SCell provides the CA UE with more radio resources. The CA UE can have only downlink SCells or both downlink and uplink
SCells.

Component carriers (CCs) are the carriers that are aggregated for a CA UE.

CC

The primary component carrier (PCC) is the carrier of the PCell.

CC

A secondary component carrier (SCC) is the carrier of an SCell.

CC Anchoring

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

During PCC anchoring, the eNodeB selects a high-priority cell as the PCell for the UE.

elated Events

Event A2
Event A2 indicates that the signal quality of the serving cell becomes lower than a specific threshold. For details, see Intra-RAT Mobility Management in Connected Mode.
Event A3
Event A3 indicates that the signal quality of the PCell's neighboring cell becomes higher than that of the PCell. For details, see Intra-RAT Mobility Management in Connected Mode.
Event A4
Event A4 indicates that the signal quality of a neighboring cell becomes higher than a specific threshold. For details, see Intra-RAT Mobility Management in Connected Mode.
Event A5
Event A5 indicates that the signal quality of the PCell becomes lower than a specific threshold and the signal quality of a neighboring cell becomes higher than another specific threshold. For details, see Intra-RAT Mobility Management in Connected Mode.
Event A6
Event A6 indicates that the signal quality of an SCell's intra-frequency neighboring cell becomes higher than that of the SCell. If the eNodeB receives an event A6 report, it changes the SCell while keeping the PCell unchanged. For details about this event, see section 5.5.4.6a "Event A6 (Neighbour becomes
offset better than SCell)" in 3GPP TS 36.331 V10.12.0.

3.1.2 Usage Scenarios

3.1.2.1 Typical Scenarios


Annex J in 3GPP TS 36.300 of Release 10 defines five typical scenarios for using CA. It stipulates that the two carriers are intra-eNodeB carriers in these scenarios. Table 3-1 lists the typical scenarios and whether Huawei eNodeBs support the scenarios. The following features apply to the typical scenarios:

LAOFD-001001 LTE-A Introduction


LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz
LAOFD-070201 Flexible CA from Multiple Carriers
LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial]
LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz
LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz
LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial]
MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial]

Table 3-1 Typical scenarios for using CA and Huawei eNodeBs' support

Typical Scenario Supported by Huawei eNodeBs Remarks

Scenario 1: intra-eNodeB co-coverage carriers Yes None

Scenario 2: intra-eNodeB different-coverage carriers Yes None

Scenario 3: intra-eNodeB carriers (one for macro coverage; another for Yes eNodeBs support this scenario in frequency-based and adaptive configuration modes but not in CA-group-based
edge coverage) configuration mode.

NOTE:
For details about the configuration modes, see 3.2.1 Overview.

Scenario 4: intra-eNodeB carriers (one provided by the site; another Yes In frequency-based or adaptive configuration mode, eNodeBs support this scenario when the ratio of
provided by remote radio heads [RRHs]) macro cells to RRHs is 1:N (N ≥ 1).
In CA-group-based configuration mode, eNodeBs support this scenario when the ratio of macro cells to
RRHs is 1:1.

Scenario 5: intra-eNodeB carriers (one provided only by the site; another Yes None
provided by the site and a repeater)

The following figures show the typical scenarios. In the figures, F1 and F2 denote two carrier frequencies.

Figure 3-1 Intra-eNodeB co-coverage carriers

Figure 3-2 Intra-eNodeB different-coverage carriers

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

Figure 3-3 Intra-eNodeB carriers (one for macro coverage; another for edge coverage)

Figure 3-4 Intra-eNodeB carriers (one provided by the site; another provided by RRHs)

Figure 3-5 Intra-eNodeB carriers (one provided only by the site; another provided by the site and a repeater)

3.1.2.2 Atypical Scenarios


In addition to protocol-defined typical scenarios, Huawei CA applies to the following atypical scenarios:

Multi-BBU interconnection
The CA feature involved is LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU. This feature implements CA between cells served by different baseband units (BBUs). For details, see 3.1.3.4 LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU.
Relaxed backhaul
The CA feature involved is LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul. This feature implements CA between inter-eNodeB cells in scenarios with relaxed backhaul requirements for delay. For details, see 3.1.3.5 LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul.

3.1.3 CA Features
CA enables a UE to simultaneously access more than one carrier and transmit uplink (UL) data and receive downlink (DL) data over all carriers, greatly increasing the data rate of the UE.
Table 3-2 provides an overview of the CA features.

Table 3-2 CA features

Feature Max. No. of UL CCs Max. No. of DL CCs Max. Total BW Description

LAOFD-001001 LTE-A Introduction 1 2 20 MHz This feature allows aggregation of two downlink CCs (referred to as downlink
(CA not supported) (2CC aggregation supported) 2CC aggregation in this document) to a maximum bandwidth of 20 MHz.

LAOFD-001002 Carrier Aggregation for Downlink 2CC in 1 2 40 MHz This feature allows downlink 2CC aggregation to a maximum bandwidth of 40
40MHz MHz.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

LAOFD-070201 Flexible CA from Multiple Carriers 1 4 80 MHz This feature enables an eNodeB to select the two, three, or four most suitable
downlink carriers for CA.

LAOFD-070202 Inter-eNodeB CA based on Coordinated 1 4 80 MHz This feature allows downlink CA between inter-eNodeB cells in multi-BBU
BBU interconnection scenarios.

LAOFD-080201 Inter-eNodeB CA based on Relaxed 1 2 40 MHz This feature allows downlink 2CC aggregation between inter-eNodeB cells in
backhaul scenarios with relaxed backhaul requirements.

LAOFD-080202 Carrier Aggregation for Uplink 2CC 2 2 40 MHz This feature allows aggregation of two uplink CCs (referred to as uplink 2CC
[Trial] aggregation in this document) to a maximum bandwidth of 40 MHz.

LAOFD-080207 Carrier Aggregation for Downlink 3CC in 1 3 40 MHz This feature allows aggregation of three downlink CCs (referred to as
40MHz downlink 3CC aggregation in this document) to a maximum bandwidth of 40
MHz.

LAOFD-080208 Carrier Aggregation for Downlink 3CC in 1 3 60 MHz This feature allows downlink 3CC aggregation to a maximum bandwidth of 60
60MHz MHz.

LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO 1 4 80 MHz This feature allows downlink CA to a maximum bandwidth of 40 MHz on
[Trial] networks that support 4T MIMO.

MRFD-101222 FDD+TDD Carrier Aggregation(LTE 1 4 80 MHz This feature allows aggregation of at most four downlink FDD and TDD CCs
FDD) [Trial] to a maximum bandwidth of 80 MHz.

3.1.3.1 LAOFD-001001 LTE-A Introduction


This feature includes six sub-features:

LAOFD-00100101 Intra-Band Carrier Aggregation for Downlink 2CC in 20MHz


Intra-band CA aggregates two carriers in a single frequency band for downlink data transmission to one CA UE. Intra-band CA is further classified into contiguous CA and non-contiguous CA, as shown in scenarios A and B in Figure 3-6.
The time alignment error between two intra-band contiguous or non-contiguous CCs must be less than 130 ns or 260 ns, respectively.
This sub-feature allows aggregation of carriers in the bands listed in 3.1.4 Band Combinations to a maximum of 20 MHz for a CA UE.
LAOFD-00100102 Inter-Band Carrier Aggregation for Downlink 2CC in 20MHz
Inter-band CA aggregates two carriers from different frequency bands for downlink data transmission to one CA UE. Scenario C in Figure 3-6 shows inter-band CA.
The time alignment error between two inter-band CCs must be less than 260 ns.
This sub-feature allows aggregation of carriers in the bands listed in 3.1.4 Band Combinations to a maximum of 20 MHz for a CA UE.

Figure 3-6 Intra-band and inter-band CA

LAOFD-00100103 Support of UE Category 6


This sub-feature enables CA for UEs of category 6, which is defined in 3GPP TS 36.306 V10.0.0.
With this sub-feature, a UE of category 6 can reach a peak data rate of 300 Mbit/s in the downlink and 50 Mbit/s in the uplink.
LAOFD-00100104 Support of UE Category 7
This sub-feature enables CA for UEs of category 7, which is defined in 3GPP TS 36.306 V12.0.0.
With this sub-feature, a UE of category 7 can reach a peak data rate of 300 Mbit/s in the downlink and 100 Mbit/s in the uplink.
LAOFD-00100105 Support of UE Category 9
This sub-feature enables CA for UEs of category 9, which is defined in 3GPP TS 36.306 V12.0.0.
With this sub-feature, a UE of category 9 can reach a peak data rate of 450 Mbit/s in the downlink and 50 Mbit/s in the uplink.

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

LAOFD-00100106 Support of UE Category 10


This sub-feature enables CA for UEs of category 10, which is defined in 3GPP TS 36.306 V12.0.0.
With this sub-feature, a UE of category 10 can reach a peak data rate of 450 Mbit/s in the downlink and 100 Mbit/s in the uplink.

3.1.3.2 LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz


This feature allows a maximum of 40 MHz downlink bandwidth for a CA UE. By aggregating two contiguous or non-contiguous carriers, operators can provide higher bandwidths and improve service quality for UEs. Scenarios A and B in Figure 3-6 illustrate intra-band contiguous and non-contiguous carriers, respectively.
This feature allows aggregation of carriers in the bands listed in 3.1.4 Band Combinations to a maximum of 40 MHz for a CA UE.

3.1.3.3 LAOFD-070201 Flexible CA from Multiple Carriers


This feature allows an eNodeB to select several of the most suitable carriers for CA. The selections are based on the CA capability reported by the CA UE and carrier management principles.
During initial access, during an incoming handover, or during an RRC connection re-establishment, a CA UE reports its CA capability to the eNodeB after setting up an RRC connection with the PCell. The eNodeB selects a suitable carrier as an SCC for the CA UE based on the carrier deployment and the carrier
management principles described in 3.2 Carrier Management.
From FDD carriers, an eNodeB can currently select either two or three carriers for CA. From TDD carriers, an eNodeB can currently select two, three, or four carriers for FDD+TDD CA. This feature maximizes carrier utilization. It uses mobility load balancing (MLB) to achieve efficient multi-carrier management.

3.1.3.4 LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU


This feature allows CA between inter-eNodeB cells in multi-BBU interconnection scenarios. In eRAN6.0, only intra-BBU cells can be aggregated. Currently, CA also works between inter-BBU cells in multi-BBU interconnection scenarios.

eRAN7.0 supports centralized multi-BBU interconnection, in which case the peak downlink data rate reaches 300 Mbit/s if 2x2 MIMO and downlink 2CC aggregation are enabled.
The BBUs exchange signaling messages and transmit service data through one or two levels of universal switching units (USUs). For details about centralized multi-BBU interconnection, see USU3910-based Multi-BBU Interconnection.
In addition to centralized multi-BBU interconnection, eRAN8.1 supports distributed multi-BBU interconnection, in which case the effect of CA varies depending on the round trip time for inter-eNodeB transmission with 2x2 MIMO enabled:
If the round trip time is less than 32 μs, downlink 2CC aggregation and downlink 3CC aggregation help achieve a peak downlink data rate of 300 Mbit/s and 450 Mbit/s, respectively.
If the round trip time is between 32 μs (including 32 μs) and 260 μs, downlink 2CC aggregation and downlink 3CC aggregation help achieve a peak downlink data rate of 270 Mbit/s and 400 Mbit/s, respectively.
If the round trip time is greater than or equal to 260 μs, CA does not work.

Distributed multi-BBU interconnection requires that a Universal inter-Connection Combo Unit (UCCU) board be installed in each BBU and connected to a USU through an optical cable for signaling exchange and data transmission between the BBUs. For details about distributed multi-BBU interconnection, see
USU3910-based Multi-BBU Interconnection.

NOTE:
In multi-BBU interconnection scenarios, each pair of BBUs are inter-eNodeB BBUs.

Inter-eNodeB CA in multi-BBU interconnection scenarios employs the same procedures as intra-eNodeB CA for PCC anchoring, SCell configuration, SCell change, SCell activation, SCell deactivation, and SCell removal. For details about these procedures, see 3.2 Carrier Management.

3.1.3.5 LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul


Since eRAN8.1, CA has also applied to inter-eNodeB cells in relaxed backhaul scenarios, as shown in Figure 3-7. The cells can be macro cells or a combination of macro and micro cells. In relaxed backhaul scenarios, eNodeBs are interconnected with a one-way delay less than or equal to 4 ms and round trip time less
than or equal to 8 ms.

Figure 3-7 Inter-eNodeB CA based on relaxed backhaul

On live networks with relaxed backhaul requirements, if UEs and the EPC comply with 3GPP Release 10, inter-eNodeB CA can be deployed without requiring network reconstruction.
During CA between macro cells, the cells exchange signaling messages and data through eX2 interfaces between the main control boards (LMPT or UMPT) of eNodeBs. During CA between macro and micro cells, the cells exchange signaling messages and data through eX2 interfaces between the main control board
(LMPT or UMPT) of the macro eNodeB and the transport module of the micro eNodeB. When one-way delay and round trip time between eNodeBs are not greater than 4 ms and 8 ms, respectively, downlink 2CC aggregation increases the downlink average data rate of a CA UE by 40%–80% and peak data rate by more
than 80%, compared with the data rates of a non-CA UE. The data rate reaches the peak value when the CA UE is the only UE in the cell and is located in the cell center.

NOTE:
After CA is enabled, the transmission delay for CA-group-based configuration mode can be queried by running the DSP CAGROUPCELL command, and that for frequency-based or adaptive configuration mode can be queried by running the DSP PCCSCELLLIST command. Frequency-based or adaptive
configuration mode is recommended for inter-eNodeB CA based on relaxed backhaul (also referred to as relaxed-backhaul-based inter-eNodeB CA in this document for clarity).
For details about eX2 interfaces between eNodeBs, see eX2 Self-Management.

The CA procedure is as follows:

1. During initial access, during an incoming handover, or during an RRC connection re-establishment, a CA UE reports its downlink CA capability to the eNodeB after setting up an RRC connection with the PCell.
2. The eNodeB checks the related switch settings, the status of the eX2 interface to a peer eNodeB, and inter-eNodeB transmission delay. If all the conditions meet certain requirements, the local eNodeB selects a carrier of the peer eNodeB as an SCC for the CA UE. The switch setting requirements depend on
the types of eNodeBs:
If the pair of eNodeBs are both macro eNodeBs, RelaxedBackhaulCaSwitch under the ENodeBAlgoSwitch.CaAlgoSwitch parameter must be on for both eNodeBs.
If the eNodeBs are a pair of macro and micro eNodeBs, RelaxedBackhaulCaSwitch under the ENodeBAlgoSwitch.CaAlgoSwitch parameter must be on for both eNodeBs. In addition, HetNetCaSwitch under this parameter must also be on for the micro eNodeB.

3. After activating the SCell, the eNodeB that serves the PCell will divert RLC traffic of the CA UE from the PCell to the SCell. When inter-eNodeB transmission quality deteriorates (for example, the transmission delay does not meet requirements or transmission is interrupted), the eNodeB removes the SCell to
exit CA. CA restarts when transmission quality recovers.

3GPP Release 10 specifications stipulate that downlink-data demodulation results (ACK or NACK) must be reported over the PCC of each CA UE. In a relaxed backhaul scenario, the eNodeB that provides the SCC for a CA UE estimates the CQI, NACK, and scheduling priority to determine the scheduling occasion and
resources for the UE in advance without affecting the scheduling priority policy and fairness among UEs. This prevents inter-eNodeB CA failures caused by transmission delay.
Inter-eNodeB CA based on relaxed backhaul requires that a GPS or IEEE1588 V2 clock source be deployed with a time synchronization accuracy of ±1.5 μs. It also requires that the jitter and packet loss rate meet the requirements described in S1/X2 Self-Management.
Inter-eNodeB CA based on relaxed backhaul employs the same procedures as intra-eNodeB CA for PCC anchoring, SCell activation, SCell change, and SCell deactivation, as described in 3.2 Carrier Management. This type of inter-eNodeB CA implements SCell configuration and SCell removal as described in both the
current section and 3.2 Carrier Management.

3.1.3.6 LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial]

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

This feature allows a maximum of 40 MHz uplink bandwidth for a CA UE. By aggregating two intra- or inter-band carriers, operators can provide higher bandwidths and improve service quality for UEs. Figure 3-6 illustrates intra- and inter-band carrier aggregation. 3.1.4 Band Combinations lists the combinations of bands
that support carrier aggregation.
This feature is dependent on the uplink CA capabilities of UEs and the setting of CaUl2CCSwitch under the CaMgtCfg.CellCaAlgoSwitch parameter. It requires LAOFD-001001 LTE-A Introduction to be activated. Therefore, after LAOFD-080202 is enabled, two carriers can be aggregated for both uplink and downlink
transmission.
LAOFD-080202 works in typical scenarios and multi-BBU interconnection scenarios but does not work between eNodeBs in relaxed backhaul scenarios.

3.1.3.7 LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz


This feature allows a maximum of 40 MHz downlink bandwidth for a CA UE. By aggregating three intra- or inter-band carriers, operators can provide higher bandwidths and improve service quality for UEs. Figure 3-6 illustrates intra- and inter-band carrier aggregation. 3.1.4 Band Combinations lists the combinations of
bands that support carrier aggregation.
This feature is dependent on the downlink CA capabilities of UEs and the setting of CaDl3CCSwitch under the CaMgtCfg.CellCaAlgoSwitch parameter.
To meet the transmission requirements of acknowledgments (ACKs) and negative ACKs (NACKs) for three carriers, PUCCH format 3 is introduced. For details about PUCCH format 3, see section 10.1.1 "PUCCH format information" in 3GPP TS 36.213 V11.4.0.
This feature works in typical scenarios and multi-BBU interconnection scenarios but does not work between eNodeBs in relaxed backhaul scenarios.

3.1.3.8 LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz


This feature allows a maximum of 60 MHz downlink bandwidth for a CA UE. By aggregating three intra- or inter-band carriers, operators can provide higher bandwidths and improve service quality for UEs. Figure 3-6 illustrates intra- and inter-band carrier aggregation. 3.1.4 Band Combinations lists the combinations of
bands that support carrier aggregation.
This feature is dependent on the downlink CA capabilities of UEs and the setting of CaDl3CCSwitch under the CaMgtCfg.CellCaAlgoSwitch parameter.
To meet the transmission requirements of ACKs and NACKs for three carriers, PUCCH format 3 is introduced. For details about PUCCH format 3, see section 10.1.1 "PUCCH format information" in 3GPP TS 36.213 V11.4.0.
This feature works in typical scenarios and multi-BBU interconnection scenarios but does not work between eNodeBs in relaxed backhaul scenarios.

3.1.3.9 LAOFD-081237 Carrier Aggregation with DL 4x4 MIMO [Trial]


This feature allows CA in networks that support 4T MIMO.

When transmission mode (TM) 3 or 4 is used on the network, downlink CA works in DL 4x2 MIMO or in DL 4x4 MIMO with rank 2 scenarios, depending on the reception capabilities of the CA UEs. If a CA UE supports 2R, downlink CA works in DL 4x2 MIMO scenarios. If a CA UE supports 4R, downlink CA
works in DL 4x4 MIMO scenarios with a maximum rank of 2, regardless of whether the UE supports rank 4. The reason is that CA UEs (except those of category 8) can use only rank 2 in TM3 or TM4 cells, according to section 4.1 "ue-Category" in 3GPP 36.306 V12.0.0.
The theoretical peak downlink data rate of a CA UE on this network increases in proportion to the number of CCs aggregated. For example, downlink 2CC aggregation achieves 300 Mbit/s, and downlink 3CC aggregation achieves 450 Mbit/s.
When TM9 is used on the network, CA works in DL 4x2 MIMO or in DL 4x4 MIMO with rank 4 scenarios, depending on the reception capabilities of the CA UEs. If a CA UE supports 2R, CA works in DL 4x2 MIMO scenarios. If a CA UE supports 4R and rank 4, CA works in DL 4x4 MIMO scenarios with a
maximum rank of 4.
Aggregation of two downlink 20 MHz carriers for a CA UE on this network can theoretically achieve a peak downlink data rate of 600 Mbit/s. However, TM9 introduces system overheads, which limit the rate to no more than 500 Mbit/s. In addition, the data rate depends on the UE category. In the same scenario,
downlink 2CC aggregation can achieve a peak downlink data rate of 300 Mbit/s for a category 6 or 7 CA UE and 450 Mbit/s for a category 9 or 10 CA UE. Under CA with other numbers of CCs, the theoretical and actual peak data rates can be deduced based on the fact that the rates are proportional to the
number of CCs aggregated.

NOTE:
3GPP Release 10 introduces TM9 into LTE. TM9 supports single-user MIMO with a maximum of eight layers and multi-user MIMO with a maximum of four data blocks (at most two layers for each UE). For details about TM9, see MIMO.

This feature supports 2CC aggregation and 3CC aggregation. It works between intra-eNodeB cells in typical scenarios, between inter-eNodeB cells in multi-BBU interconnection scenarios, and between inter-eNodeB cells in relaxed backhaul scenarios.

3.1.3.10 MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial]


This feature allows aggregation of downlink FDD and TDD CCs. With this feature, up to four CCs can be aggregated to a maximum bandwidth of 80 MHz. This feature deals with spectrum shortages by utilizing both FDD and TDD spectral resources, addresses mobile broadband service competitions, and improves service
quality.
In this feature, only FDD carriers can be PCCs of CA UEs. TDD cells must use uplink-downlink configuration 1 or 2. There is no subframe configuration requirement for FDD cells. If a frame offset is configured for a TDD cell, the same frame offset must be specified for the FDD cells involved in CA.
This feature is dependent on the downlink CA capabilities of UEs and the setting of InterFddTddCaSwitch under the CaMgtCfg.CellCaAlgoSwitch parameter.
This feature works in typical scenarios and between eNodeBs in relaxed backhaul scenarios. In typical scenarios, downlink 2CC, 3CC, or 4CC aggregation works. However, in relaxed backhaul scenarios, only downlink 2CC aggregation between macro cells works.

3.1.4 Band Combinations


GPP-defined Band Combinations

eNodeBs support CA in the combinations of 3GPP-defined bands listed in Table 3-3. The following are the rules for using CA features in different band combinations:

If the total bandwidth is less than or equal to 20 MHz, the feature LAOFD-001001 LTE-A Introduction must be activated. In addition, the following features can be activated when required: LAOFD-070201 Flexible CA from Multiple Carriers, LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU, LAOFD-
080201 Inter-eNodeB CA based on Relaxed backhaul, LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial], and MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial].
If the total bandwidth is greater than 20 MHz but is less than or equal to 40 MHz, the features LAOFD-001001 LTE-A Introduction and LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz must be activated. In addition, the following features can be activated when required: LAOFD-070201 Flexible
CA from Multiple Carriers, LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU, LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul, LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial], LAOFD-080207 Carrier Aggregation for Downlink 3CC in 40MHz, and MRFD-101222 FDD+TDD
Carrier Aggregation(LTE FDD) [Trial].
If the total bandwidth is greater than 40 MHz but is less than or equal to 60 MHz, the following features must be activated: LAOFD-001001 LTE-A Introduction, LAOFD-001002 Carrier Aggregation for Downlink 2CC in 40MHz, LAOFD-070201 Flexible CA from Multiple Carriers, LAOFD-080207 Carrier
Aggregation for Downlink 3CC in 40MHz, and LAOFD-080208 Carrier Aggregation for Downlink 3CC in 60MHz. In addition, the following features can be activated when required: LAOFD-070202 Inter-eNodeB CA based on Coordinated BBU, LAOFD-080201 Inter-eNodeB CA based on Relaxed backhaul,
LAOFD-080202 Carrier Aggregation for Uplink 2CC [Trial], and MRFD-101222 FDD+TDD Carrier Aggregation(LTE FDD) [Trial].

NOTE:
If carriers with the bandwidths listed in the BW (MHz) column of the following table are aggregated, the total bandwidth cannot exceed the bandwidth listed in the Max. Total BW (MHz) column.

Table 3-3 CA band combinations supported by Huawei eNodeBs

Band Combination BW (MHz) Applicable Entity Version Max. Total BW (MHz)

Band 7 (2.6 GHz), contiguous 15+15 Macro eNodeBs eRAN8.1 or later 40


10+20
15+20
20+20

Band 3 (1.8 GHz), contiguous 5+20 Macro eNodeBs eRAN8.1 or later 40


10+20
15+20
20+20

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

Band 7 (2.6 GHz) + band 3 (1.8 GHz) Band 7: {10, 15, 20} Macro, micro, and LampSite eNodeBs eRAN6.0 or later 40
Band 3: {5, 10, 15, 20}

Band 7 (2.6 GHz) + band 20 (800 MHz) Band 7: {10, 15, 20} Macro eNodeBs eRAN6.0 or later 30
Band 20: {5, 10}

Band 3 (1.8 GHz) + band 20 (800 MHz) Band 3: {5, 10, 15, 20} Macro eNodeBs eRAN6.0 or later 30
Band 20: {5, 10}

Band 1 (2.1 GHz) + band 3 (1.8 GHz) Band 1: {5, 10, 15, 20} Macro, micro, and LampSite eNodeBs eRAN6.0 or later 40
Band 3: {5, 10, 15, 20}

Band 4 (advanced wireless service [AWS]) + band 17 Band 4: {5, 10} Macro eNodeBs eRAN6.0 or later 20
(700 MHz) Band 17: {5, 10}

Band 4 (AWS) + band 13 (700 MHz) Band 4: {5, 10} Macro eNodeBs
Band 13: {10}

Band 4 (AWS) + band 12 (low frequency band of 700 Band 4: {5, 10} Macro eNodeBs
MHz) Band 12: {5, 10}

Band 4 (AWS), non-contiguous Band 4: {5, 10} Macro eNodeBs eRAN7.0 or later 20

Band 4 (AWS) + band 7 (2.6 GHz) Band 4: {10, 15} Macro eNodeBs eRAN7.0 or later 35
Band 7: {10, 15, 20}

Band 3 (1.8 GHz) + band 28 (APT700) Band 3: {5, 10, 15, 20} Macro eNodeBs eRAN7.0 or later 40
Band 28: {5, 10, 15, 20}

Band 4 (AWS) + band 2 (Personal Communication Band 4: {5, 10, 15, 20} Macro and LampSite eNodeBs eRAN7.0 or later 40
Service [PCS]) Band 2: {5, 10, 15, 20}

Band 2 (PCS) + band 7 (2.6 GHz) Band 2: {5, 10, 15, 20} Macro eNodeBs eRAN7.0 or later 40
Band 7: {5, 10, 15, 20}

Band 7 (2.6 GHz) + band 12 (low frequency band of Band 7: {5, 10, 15, 20} Macro eNodeBs eRAN7.0 or later 30
700 MHz) Band 12: {5, 10}

Band 7 (2.6 GHz) + band 13 (700 MHz) Band 7: {5, 10, 15, 20} Macro eNodeBs eRAN7.0 or later 30
Band 13: {5, 10}

Band 7 (2.6 GHz) + band 17 (700 MHz) Band 7: {5, 10, 15, 20} Macro eNodeBs eRAN7.0 or later 30
Band 17: {5, 10}

Band 7 (2.6 GHz) + band 28 (APT700) Band 7: {5, 10, 15, 20} Macro eNodeBs eRAN7.0 or later 40
Band 28: {5, 10, 15, 20}

Band 1 (2.1 GHz) + band 5 (850 MHz) Band 1: {10} Macro and micro eNodeBs eRAN7.0 or later 20
Band 5: {10}

Band 1 (2.1 GHz) + band 7 (2.6 GHz) Band 1: {5, 10, 15, 20} Macro and LampSite eNodeBs eRAN7.0 or later 40
Band 7: {5, 10, 15, 20}

Band 1 (2.1 GHz) + band 28 (APT700) Band 1: {5, 10, 15, 20} Macro eNodeBs eRAN7.0 or later 40
Band 28: {5, 10, 15, 20}

Band 5 (850 MHz) + band 7 (2.6 GHz) Band 5: {5, 10, 15, 20} Macro eNodeBs eRAN7.0 or later 40
Band 7: {5, 10, 15, 20}

Band 5 (850 MHz) + band 28 (APT700) Band 5: {5, 10, 15, 20} Macro eNodeBs eRAN7.0 or later 40
Band 28: {5, 10, 15, 20}

Band 28 (APT700), contiguous 10+20 Macro eNodeBs eRAN7.0 or later 40


15+15
15+20
20+20

Band 28 (APT700), non-contiguous Band 28: {5, 10, 15, 20} Macro eNodeBs eRAN7.0 or later 40

Band 3 (1.8 GHz) + band 28 (APT700) Band 3: {5, 10, 15, 20} Macro eNodeBs eRAN7.0 or later 40
Band 28: {5, 10, 15, 20}

Band 20 (800 MHz) + band 8 (900 MHz) Band 20: {10} Macro eNodeBs eRAN7.0 or later 20

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

Band 8: {10}

Band 3 (1.8 GHz) + band 5 (850 MHz) Band 3: {10, 20} Macro eNodeBs eRAN7.0 or later 30
Band 5: {10}

Band 2 (PCS) + band 29 (700 MHz) Band 2: {5, 10} Macro eNodeBs eRAN7.0 or later 20
Band 29: {5, 10}

Band 4 (AWS) + band 29 (700 MHz) Band 4: {5, 10} Macro eNodeBs eRAN7.0 or later 20
Band 29: {5, 10}

Band 7 (2.6 GHz) + band 8 (900 MHz) Band 7: {5, 10, 15, 20} Macro eNodeBs eRAN7.0 or later 40
Band 8: {5, 10, 15, 20}

Band 3 (1.8 GHz) + band 8 (900 MHz) Band 3: {5, 10, 15, 20} Macro eNodeBs eRAN8.1 or later 40
Band 8: {5, 10, 15, 20}

Band 2 (1.9 GHz), non-contiguous Band 2: {5, 10, 15, 20} Macro eNodeBs eRAN8.1 or later 40

Band 3 (1.8 GHz), non-contiguous Band 3: {5, 10, 15, 20} Macro eNodeBs eRAN8.1 or later 40

Band 4 (2.1 GHz), non-contiguous Band 4: {5, 10, 15, 20} Macro eNodeBs eRAN8.1 or later 40

Band 7 (2.6 GHz), non-contiguous 5+15 Macro eNodeBs eRAN8.1 or later 40


10+10
10+15
15+15
15+20
20+20

Band 2 (1.9 GHz) + band 12 (700 MHz) Band 2: {5, 10, 15, 20} Macro eNodeBs eRAN8.1 or later 30
Band 12: {10}

Band 2 (1.9 GHz) + band 13 (700 MHz) Band 2: {5, 10, 15, 20} Macro eNodeBs eRAN8.1 or later 30
Band 13: {10}

Band 2 (1.9 GHz) + band 17 (700 MHz) Band 2: {5, 10} Macro eNodeBs eRAN8.1 or later 20
Band 17: {5, 10}

Band 5 (850 MHz) + band 12 (700 MHz) Band 5: {5, 10} Macro eNodeBs eRAN8.1 or later 20
Band 12: {5, 10}

Band 4 (AWS) + band 12 (700 MHz) Band 4: {15} Macro and micro eNodeBs eRAN8.1 or later 25
Band 12: {10}

Band 4 (AWS) + band 13 (700 MHz) Band 4: {15} Macro and micro eNodeBs eRAN8.1 or later 25
Band 13: {10}

Band 1 (2.1 GHz) + band 5 (850 MHz) + band 7 (2.6 Band 1: {10} Macro eNodeBs eRAN8.1 or later 40
GHz) Band 5: {10}
(3CC) Band 7: {5, 10, 15, 20}

Band 1 (2.1 GHz) + band 3 (1.8 MHz) + band 8 (900 Band 1: {5, 10, 15, 20} Macro eNodeBs eRAN8.1 or later 50
MHz) Band 3: {5, 10, 15, 20}
(3CC) Band 8: {5, 10}

Band 3 (1.8 GHz) + band 7 (2.6 GHz) + band 20 (800 Band 3: {5, 10, 15, 20} Macro eNodeBs eRAN8.1 or later 50
MHz) Band 7: {10, 15, 20}
(3CC) Band 20: {5, 10}

Band 3 (1.8 GHz) + band 7 (2.6 GHz) + band 7 (2.6 Band 3: {5, 10, 15, 20} Macro and LampSite eNodeBs eRAN8.1 or later 60
GHz) Band 7: {10, 15, 20}
(3CC) Band 7: {10, 15, 20}

Band 3 (1.8 GHz) + band 3 (1.8 GHz) + band 7 (2.6 Band 3: {5, 10, 15, 20} Macro and LampSite eNodeBs eRAN8.1 or later 60
GHz) Band 3: {5, 10, 15, 20}
(3CC) Band 7: {10, 15, 20}

Band 3 (1.8 GHz) + band 3 (1.8 GHz) + band 20 (800 Band 3: {5, 10, 15, 20} Macro eNodeBs eRAN8.1 or later 50
MHz) Band 3: {5, 10, 15, 20}
(3CC) Band 20: {5, 10}

Band 2 (1.9 GHz) + band 4 (2.1 GHz) + band 29 (700 Band 2: {5, 10, 15, 20} Macro eNodeBs eRAN8.1 or later 45
MHz)

file:///C|/Users/erafrsu/Documents/BI/Huawei/CPI/eRAN8.1/Stefan/eRAN8 Radio and Performance.html[2015-07-01 12:50:49]


Radio and Performance

Band 4: {5, 10, 15}


(3CC) Band 29: {5, 10}

Band 2 (1.9 GHz) + band 5 (850 MHz) + band 29 Band 2: {5, 10, 15, 20} Macro eNodeBs eRAN8.1 or later 40
(700 MHz) Band 5: {5, 10}
(3CC) Band 29: {5, 10}

Band 4 (2.1 GHz) + band 7 (2.6 GHz) + band 12 (700 Band 4: {5, 10, 15} Macro eNodeBs eRAN8.1 or later 45
MHz) Band 7: {5, 10, 15, 20}
(3CC) Band 12: {5, 10}

Band 3 (1.8 GHz) + band 40 (2.3 GHz) Band 3 (FDD): {5} Macro eNodeBs eRAN8.1 or later 25
(FDD+TDD 2CC) Band 40 (TDD): {20}

Band 20 (800 MHz) + band 38 (2.6 GHz) + band 38 Band 20 (FDD): {10} Macro eNodeBs eRAN8.1 or later 50
(2.6 GHz) Band 38 (TDD): {20}
(FDD+TDD 3CC) Band 38 (TDD): {20}

Band 3 (1.8 GHz) + band 7 (2.6 GHz) + band 40 (2.3 Band 3 (FDD): {10, 15} Macro eNodeBs eRAN8.1 or later 60
GHz) + band 40 (2.3 GHz) Band 7 (FDD): {20}
(FDD+TDD 4CC) Band 40 (TDD): {10, 20}
Band 40 (TDD): {20}

Band 3 (1.8 GHz) + band 7 (2.6 GHz) + band 38 (2.6 Band 3 (FDD): {15} Macro eNodeBs eRAN8.1 or later 75
GHz) + band 38 (2.6 GHz) Band 7 (FDD): {20}
(FDD+TDD 4CC) Band 38 (TDD): {20}
Band 38 (TDD): {20}

Band 3 (1.8 GHz) + band 8 (900 MHz) + band 41 (2.6 Band 3 (FDD): {10, 15, 20} Macro eNodeBs eRAN8.1 or later 80
GHz) + band 41 (2.6 GHz) Band 8 (FDD): {10, 15, 20}
(FDD+TDD 4CC) Band 41 (TDD): {20}
Band 41 (TDD): {20}

Band 7 (2.6 GHz) + band 20 (800 MHz) + band 38 Band 7 (FDD): {10} Macro eNodeBs eRAN8.1 or later 60
(2.6 GHz) + band 38 (2.6 GHz) Band 20 (FDD): {10}
(FDD+TDD 4CC) Band 38 (TDD): {20}
Band 38 (TDD): {20}

Band 8 (900 MHz) + band 39 (1.9 GHz) + band 41 Band 8 (FDD): {10, 15, 20} Macro eNodeBs eRAN8.1 or later 80
(2.6 GHz) + band 41 (2.6 GHz) Band 39 (FDD): {20}
(FDD+TDD 4CC) Band 41 (TDD): {20}
Band 41 (TDD): {20}

Band 1 (2.1 GHz) + band 5 (850 MHz)+ band 7 (2.6 Band 1 (FDD): {10} Macro eNodeBs eRAN8.1 or later 60
GHz) + band 40 (2.3 GHz) Band 5 (FDD): {10}
(FDD+TDD 4CC) Band 7 (FDD): {20}
Band 40 (TDD): {20}

Band 3 (1.8 GHz) + band 7 (2.6 GHz) + band 20 (800 Band 3 (FDD): {10}