Admission and Congestion Control (ERAN3.0 - 03)

Admission and Congestion Control
eRAN3.0
Feature Parameter Description
Issue 03
Date 2012-12-29
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2013. 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 the 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
eRAN
Admission and Congestion Control Contents
Contents
1 Introduction ................................................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1
1.2 Intended Audience ........................................................................................................................ 1-1
1.3 Change History.............................................................................................................................. 1-1
2 Overview .....................................................................................................................................2-1
3 Load Monitoring ........................................................................................................................3-1
3.1 PRB Usage Monitoring .................................................................................................................. 3-1
3.2 GBR-Service QoS Satisfaction Rate Monitoring ........................................................................... 3-1
3.2.1 QoS Satisfaction Rate .......................................................................................................... 3-1
3.2.2 Downlink QoS Satisfaction Rate Evaluation ........................................................................ 3-2
3.2.3 Uplink QoS Satisfaction Rate Evaluation ............................................................................. 3-2
3.3 Resource Limitation Indications .................................................................................................... 3-2
4 Admission Control ....................................................................................................................4-1

4.1 Key Techniques ............................................................................................................................. 4-3
4.2 Service Attributes .......................................................................................................................... 4-3
4.3 UE Capability Decision .................................................................................................................. 4-4
4.4 Resource Limitation Decision ........................................................................................................ 4-4
4.5 Uplink and Downlink Admission .................................................................................................... 4-4
4.5.1 Non-GBR Service Admission ............................................................................................... 4-4
4.5.2 GBR Service Admission ....................................................................................................... 4-5
4.5.3 Preemption ........................................................................................................................... 4-8
4.5.4 Redirection ......................................................................................................................... 4-10
5 Congestion Control ..................................................................................................................5-1

5.1 Load Status Decision..................................................................................................................... 5-2
5.2 Release of Low-Priority GBR Services ......................................................................................... 5-2
6 Related Features .......................................................................................................................6-1

6.1 Admission Control ......................................................................................................................... 6-1
6.1.1 Required Features ................................................................................................................ 6-1
6.1.2 Mutually Exclusive Features ................................................................................................. 6-1
6.1.3 Affected Features ................................................................................................................. 6-1
6.2 Congestion Control ....................................................................................................................... 6-1
6.2.1 Required Features ................................................................................................................ 6-1
6.2.2 Mutually Exclusive Features ................................................................................................. 6-1
6.2.3 Affected Features ................................................................................................................. 6-1
7 Impact on the Network ............................................................................................................7-1

7.1 Admission Control ......................................................................................................................... 7-1
7.1.1 Impact on System Capacity .................................................................................................. 7-1
Issue 03 (2012-12-29) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
eRAN
Admission and Congestion Control Contents
7.1.2 Impact on Network Performance .......................................................................................... 7-1

7.2 Congestion Control ....................................................................................................................... 7-1
7.2.1 Impact on System Capacity .................................................................................................. 7-1
7.2.2 Impact on Network Performance .......................................................................................... 7-1
8 Engineering Guidelines...........................................................................................................8-1
8.1 When to Use Admission and Congestion Control ......................................................................... 8-1
8.1.1 Admission Control................................................................................................................. 8-1
8.1.2 Congestion Control ............................................................................................................... 8-1
8.2 Information to Be Collected ........................................................................................................... 8-2
8.2.1 Admission Control................................................................................................................. 8-2
8.2.2 Congestion Control ............................................................................................................... 8-2
8.3 Network Planning .......................................................................................................................... 8-2
8.3.1 RF Planning .......................................................................................................................... 8-2
8.3.2 Network Topology ................................................................................................................. 8-2
8.3.3 Hardware Planning ............................................................................................................... 8-2
8.4 Deploying Admission Control ........................................................................................................ 8-3
8.4.1 Deployment Requirements ................................................................................................... 8-3
8.4.2 Data Preparation .................................................................................................................. 8-3
8.4.3 Feature Activation ............................................................................................................... 8-10
8.4.4 Activation Observation ........................................................................................................ 8-12
8.4.5 Deactivation ........................................................................................................................ 8-16
8.5 Deploying Congestion Control .................................................................................................... 8-16
8.5.1 Deployment Requirements ................................................................................................. 8-16
8.5.2 Data Preparation ................................................................................................................ 8-16
8.5.3 Feature Activation ............................................................................................................... 8-19
8.5.4 Activation Observation ........................................................................................................ 8-20
8.5.5 Deactivation ........................................................................................................................ 8-21
8.6 Performance Optimization ........................................................................................................... 8-21
8.7 Troubleshooting ........................................................................................................................... 8-21
8.7.1 Admission Control............................................................................................................... 8-21
8.7.2 Congestion Control ............................................................................................................. 8-22
9 Parameters .................................................................................................................................9-1
10 Counters .................................................................................................................................10-1
11 Glossary ..................................................................................................................................11-1
12 Reference Documents .........................................................................................................12-1
Issue 03 (2012-12-29) Huawei Proprietary and Confidential ii

eRAN
Admission and Congestion Control 1 Introduction
1 Introduction
1.1 Scope
This document describes the admission and congestion control feature of the Long Term Evolution (LTE)
network. This feature is implemented through load monitoring, admission control, and congestion
control.
This document also describes the parameters and engineering guidelines related to admission and
congestion control.
Any managed objects (MOs), parameters, alarms, or counters described in this document correspond to
the software release delivered with this document. In the event of updates, the updates will be described
in the product documentation delivered with the latest software release.
1.2 Intended Audience

This document is intended for:
 Personnel who need to understand admission and congestion control
 Personnel who work with Huawei LTE products
1.3 Change History

This section provides information about the changes in different document versions.
There are two types of changes, which are defined as follows:
 Feature change: refers to a change in the admission and congestion control feature of a specific
product version.
 Editorial change: refers to a change in wording or the addition of information that was not described in
the earlier version.
Document Issues
The document issues are as follows:
 03 (2012-12-29)
 02 (2012-05-11)
 01 (2012-03-30)
 Draft A (2012-01-10)
03 (2012-12-29)
Compared with issue 02 (2012-05-11) of eRAN3.0, issue 03 (2012-12-29) of eRAN3.0 includes the
following changes.
Change Type Change Description Parameter Change

Feature change None None
Editorial change Added descriptions of None
redirection. For details, see
section 4.5.4 "Redirection."
Issue 03 (2012-12-29) Huawei Proprietary and Confidential 1-1

eRAN
02 (2012-05-11)
Compared with issue 01 (2012-03-30) of eRAN3.0, issue 02 (2012-05-11) of eRAN3.0 includes the
following changes.

Feature change Revised the VoIP service satisfaction rate None
evaluation method. For details, see section 3.2.2
"Downlink QoS Satisfaction Rate Evaluation" and
section 3.2.3 "Uplink QoS Satisfaction Rate
Evaluation."
Editorial Deleted descriptions of emergency calls. For None
change details about the feature, see Emergency Call
Feature Parameter Description.
01 (2012-03-30)
This is the first official release.
Compared with draft A (2012-01-10) of eRAN3.0, issue 01 (2012-03-30) of eRAN3.0 includes the
following changes.

Feature change Removed guaranteed bit rate Disabled the function of the option
(GBR) service rate downsizing RelDrbSwitch(LdcDrbRelSwitch) under the
from congestion control. CellAlgoSwitch.RacAlgoSwitch parameter
because this option will be deleted in later
versions.
Disabled the functions of the following
parameters because they will be deleted in
later versions:
 GoldGbrCongProportion
 SilverGbrCongProportion
 CopperGbrCongProportion
Editorial Revised chapter 8 "Engineering None
change Guidelines."
Draft A (2012-01-10)
This is a draft.
Compared with issue 02 (2012-12-24) of eRAN2.2, draft A (2012-01-10) of eRAN3.0 includes the
following changes.

eRAN

Feature change  Deleted descriptions on resource None
prediction–based admission.
 Added descriptions on procedures for
guaranteed bit rate (GBR) and non-GBR service
preemption. For details, see section 4.5.3
"Preemption."
Editorial  Added chapters 6 "Related Features" and 7 None
change "Impact on the Network."
 Split Load Control Feature Parameter Description
into Admission and Congestion Control Feature
Parameter Description and MLB Feature
Parameter Description.
For details about load balancing, see MLB

eRAN
Admission and Congestion Control 2 Overview
2 Overview
Load control aims to maintain system stability while maximizing resource usage by rejecting admission
requests or releasing some admitted services. Load control ensures the quality of admitted services by
controlling the cell load. In addition, load control provides the required quality of service (QoS)
mechanism for individual radio bearers to achieve maximal cell capacity.
Load control consists of four functions, which are load monitoring, admission control, load balancing,
and congestion control. Figure 2-1 shows the relationship between the four load control functions.
Figure 2-1 Relationship between load control functions
Admission control, load balancing, and congestion control are performed based on the results of load
monitoring. In addition, congestion control provides the overload indication and overload relief indication
for admission control. The related parameters include timers and thresholds (for example, admission
threshold, load balancing threshold, and congestion threshold) that are defined for admission control,
load balancing, and congestion control. For details about load balancing, see MLB Feature Parameter
Description.

eRAN
Admission and Congestion Control 3 Load Monitoring
3 Load Monitoring
Load monitoring provides the monitoring results, namely, physical resource block (PRB) usage, QoS
satisfaction rate of guaranteed bit rate (GBR) services, and resource limitation indication for the eNodeB
to determine whether to admit GBR services. Load monitoring also provides the PRB usage for the
eNodeB to determine whether to perform congestion control. Based on measurements, load monitoring
tracks the activation, modification, and release of each radio bearer in the cell, calculates the usage of
time and frequency resources, and checks the cell load status.
An eNodeB monitors the PRB usage and QoS satisfaction rate of GBR services to determine the cell
load status. Based on the cell load status, admission control and congestion control determine whether
to admit GBR services or release low-priority services. The resource allocation algorithms provide
resource limitation indications for the load monitoring.
When the user equipment (UE) receive (RX) capability is limited or the downlink transmit power is limited
due to poor downlink channel quality, the UEs may use only part of the time or frequency resources.
When only a small number of UEs camp on the cell, the QoS satisfaction rate of GBR services is
determined based on these UEs. As a result, new services will not be admitted although there are many
idle PRBs. To solve this problem, the monitoring of downlink PRB usage is introduced. When the
downlink PRB usage is low and the transmit power is not limited, new services are directly admitted.
When the downlink PRB usage is low and the transmit power is limited or when the downlink PRB usage
is high, admission decision must be made first according to the QoS satisfaction rate of GBR services
based on QoS class identifier (QCI).
3.1 PRB Usage Monitoring

By monitoring the PRB usage of GBR services, the eNodeB knows the usage of time-frequency
resources in the cell and evaluates the cell load on a preliminary basis. The Media Access Control (MAC)
layer calculates the PRB usage.
The formula for calculating the PRB usage is as follows:
The eNodeB compares the calculated PRB usage with the uplink and downlink PRB usage thresholds
CellRacThd.DlRbHighThd, CellRacThd.DlRbLowThd, CellRacThd.UlRbHighThd, and
CellRacThd.UlRbLowThd. In the downlink, for example, if the PRB usage is higher than
CellRacThd.DlRbHighThd, it indicates that the downlink PRB usage is high; if the PRB usage is lower
than CellRacThd.DlRbLowThd, it indicates that the downlink PRB usage is low. The purpose of using
both the upper threshold and the lower threshold is to prevent the possible ping-pong effect.
3.2 GBR-Service QoS Satisfaction Rate Monitoring

3.2.1 QoS Satisfaction Rate
The QoS satisfaction rate of GBR services reflects the QoS conditions of admitted GBR services in a cell.
It is used for evaluating the cell load.
The QCI of a service reflects the QoS requirements of the service, and each QCI has its own 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 the QoS satisfaction
rates of these services in the LTE QoS mechanism.

eRAN
For downlink, the QoS satisfaction rate is evaluated based on the QCI of the logical channel. For uplink,
however, the QoS satisfaction rate is evaluated based on the QCI of the logical channel group, which 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 is that the eNodeB cannot
estimate the amount of buffered data to be transmitted through each logical channel on the UE side. This
evaluation method helps reduce the signaling and the number of Buffer Status Reports (BSRs).
The uplink and downlink QoS satisfaction rates of GBR services are calculated based on QCIs, and the
admission thresholds are set for each QCI. That is, the admission differentiation between QCIs is
achieved through different admission thresholds.
3.2.2 Downlink QoS Satisfaction Rate Evaluation

The QoS satisfaction rate of QCI 1 is represented by the ratio of satisfied VoIP services in a cell to all
VoIP services in the cell. The QoS satisfaction rate of a VoIP service is represented by the proportion of
voice packets that meet the delay requirements to all voice packets. The higher the proportion, the
higher the satisfaction rate.
The QoS satisfaction rates of QCI x (x = 2–4) are represented by the QoS satisfaction rate of the GBR
service. The evaluation is based on the ratio of the scheduled data volume of these services to the total
data volume of these services to be transmitted. If the scheduled data volume is high or the data volume
in the buffer is low, it indicates that the QoS satisfaction rate is high.
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 is
used for VoIP services.
3.2.3 Uplink QoS Satisfaction Rate Evaluation

The QoS satisfaction rate of QCI 1 is represented by the ratio of satisfied VoIP services in a VoIP logical
channel group to all VoIP services in the logical channel group. The QoS satisfaction rate of a VoIP
service is represented by the proportion of successfully received voice packets to all voice packets. The
higher the proportion, the higher the satisfaction rate.
The uplink QoS satisfaction rate of GBR services is evaluated for each logical channel group. The QoS
satisfaction rate of a logical channel group is evaluated based on the transmitted data and the total
amount of data to be transmitted. If the transmitted data volume is high, it indicates that the QoS
satisfaction rate is high.
QCIs 1 to 4 can be mapped to logical channel groups. For details about the mapping rules, see
Scheduling Feature Parameter Description. If QCIs 2 to 4 are mapped to logical channel group 2, the
QoS satisfaction rates for services with QCIs 2 to 4 are represented by the satisfaction rate for logical
channel group 2.
3.3 Resource Limitation Indications

Load monitoring provides resource limitation indications required by admission control. The resource
limitation indications are described as follows:
 Downlink power limitation indication
A high downlink transmit power of the eNodeB may cause power limitation. The cell is not always
congested when a downlink power limitation indication is sent. In this case, the eNodeB does not
directly reject admission requests. Instead, it considers the QoS satisfaction rate and then makes a
decision.
The scheduling and power control algorithms determine whether the power is limited:

eRAN
− The
downlink power is limited if all downlink power is consumed and there are remaining RBs in the
downlink. This situation is possible when all UEs are at the cell edge.
− Thedownlink power is not limited if there is any (remaining) downlink power and there are no
remaining RBs in the downlink. This situation is possible when all UEs are at the cell center.
− The system has sufficient downlink resources if the power is not limited and the RB usage is low.
For details, see Scheduling Feature Parameter Description.
 PUCCH resource limitation indication
The physical uplink control channel (PUCCH) is allocated on the basis of the number of admitted
services and the QoS requirements of admitted services. When the existing PUCCH resource is
insufficient and no more resources are available, the PUCCH resource limitation indication is sent to
admission control, informing that no more admission requests can be accepted.
 Transport resource limitation indication
If congestion occurs when the transport resource (for example, the S1-interface bandwidth) is
insufficient, the eNodeB operates on the basis of preemption of transport resources. For details, see
Transport Resource Management Feature Parameter Description.
 Cell congestion indication
The cell congestion indication provided by congestion control indicates that the Uu interface resource
(PRBs or downlink transmit power) is insufficient. There are four types of indication: Uplink Congested
and Downlink Not Congested, Downlink Congested and Uplink Not Congested, Uplink and Downlink
Congested, and Uplink and Downlink Congestion Cleared.
− The eNodeB rejects the admission requests of GBR services (new services or handovers) if the
uplink or downlink is congested.
− The
eNodeB determines whether to admit a non-GBR service based on the rules of non-GBR service
admission. For details, see section 4.5.1 "Non-GBR Service Admission."
− If
preemption is enabled in the cell, new services can preempt other services. For details about
preemption, see section 4.5.3 "Preemption."

eRAN
Admission and Congestion Control 4 Admission Control
4 Admission Control
Admission control is categorized into radio-resource-based admission control and
transport-resource-based admission control. This document describes the former. For details about the
latter, see Transport Resource Management Feature Parameter Description.
Admission control described in this document determines whether to admit GBR services (new services
or handovers) based on the cell load conditions (PRB usage, QoS satisfaction rate of GBR services, and
resource limitation indications) provided by load monitoring.
Admission control determines whether to accept the requests for new services and handovers based on
the UE capability and the current resource usage under the precondition that the quality of services in
the whole cell is ensured. If the PUCCH resource is not limited, the requests for signaling radio bearers
(SRBs) are always accepted. SRBs are used, for example, to transmit location update and detach
requests. Figure 4-1 shows the process of admission control.

eRAN
Figure 4-1 Process of admission control
The process of admission control for all services (including new services or handovers) is described as
follows:
1. The eNodeB checks the UE capability. If the UE capability cannot meet the service requirements, it
will not be admitted. If the UE capability can meet the service requirements, the eNodeB proceeds to
the following step. For details, see section 4.3 "UE Capability Decision." The eNodeB does not check
the UE capability for new non-GBR service requests.
2. The eNodeB checks whether the required resources are limited. For details about resource limitation
indications, see section 3.3 "Resource Limitation Indications."

eRAN
− If
the PUCCH resource is limited, services will not be admitted. However, if the service is an
emergency call, the UE can preempt the PUCCH resource for other UEs.
− If
a congestion indication is received, the eNodeB makes a decision based on the status of a
preemption switch.
− If
all the preceding resources are not limited, the eNodeB proceeds to the following step. For details
about resource limitation indications, see section 3.3 "Resource Limitation Indications."
3. The eNodeB makes uplink admission decision and downlink admission decision based on the
service type (GBR or non-GBR services). Admission is successful when services can be admitted in
both the uplink and the downlink. For details about the uplink admission process and downlink
admission process, see section 4.5 "Uplink and Downlink Admission."
This admission control process does not apply to an emergency call because an emergency call has the
highest admission priority. For details about the admission of an emergency call, see Emergency Call
This chapter describes the basic feature LBFD-002023 Admission Control.
4.1 Key Techniques

The key techniques required in admission control are described as follows:
 The uplink and downlink non-GBR service admission is decided on the basis of the number of radio
bearers for non-GBR services in the cell, not the QoS satisfaction rate.
 The uplink and downlink GBR service admission can be based on QoS satisfaction rates and PRB
usage of GBR services.
− The admission based on QoS satisfaction rates checks whether to admit a GBR service (a new
service or handover) based on the QoS satisfaction rates of the admitted GBR services in the cell.
− Uplink/downlink
admission control limits the number of physical resource blocks (PRBs) used for
GBR services by checking the number of PRBs used by the admitted GBR services. For details, see
"Check on the Number of PRBs Used by GBR Services."
 If the cell resources are insufficient, new services will not be admitted. However, new services with
high priorities need to be admitted. In this case, service preemption enables high-priority services to
preempt the cell resources, improving the QoS satisfaction rates of these services. The minimum unit
that can be preempted is radio bearer. Radio resource preemption is an optional feature. For details,
see section 4.5.3 "Preemption."
Admission control presented by Huawei implements differentiated admissions based on service
attributes.
4.2 Service Attributes

The attributes of a service include service priority and service type.
 Service priority
When a radio bearer is set up, the Evolved Packet Core (EPC) determines the Allocation and
Retention Priority (ARP) of the radio bearer and sends the ARPs together with other QoS parameters
to the eNodeB.
The eNodeB categorizes services based on their ARP values. The ARP values are mapped onto 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 range of the preceding two ARP thresholds indicate bronze-level services. A small ARP
value indicates a high priority level. Table 4-1 shows a typical mapping between the ARP values and
the service priorities.

eRAN
Table 4-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 the ARP, see section 4.7.3 in 3GPP TS 23.401 V10.8.0 (2012-06).
 Service request type
The service request type can be a request for a new service or a handover. New services are
classified into gold-, silver-, and bronze-level services. The admission threshold for handovers is lower
than that for new services. For details about the admission thresholds, see "Admission Decision
Based on QoS Satisfaction Rates" in section 4.5.2 "GBR Service Admission."
4.3 UE Capability Decision

The UE reports its capability to the EPC each time the UE performs a network attachment. When the UE
needs to change its capability, it performs detachment and then re-attachment. If the eNodeB does not
know the UE capability, it initiates a UE Capability Inquiry procedure to request the UE to report its
capability 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 service request, the Mobility Management Entity (MME) sends an INITIAL
CONTEXT SETUP REQUEST message to the eNodeB over the S1 interface, indicating the UE
capability 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 relevant information and checks whether the UE supports specified bearers
based on the bearer parameters and UE capability. If the UE does not support the bearer parameters, it
cannot be admitted. The major concern about the UE capability 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).
4.4 Resource Limitation Decision

For details about how to check whether the resources are limited, see section 3.3 "Resource Limitation
Indications."
4.5 Uplink and Downlink Admission

Uplink and downlink admission decides whether the to-be-admitted service is a new service or a
handover, and then makes the admission decision based on the service type (GBR or non-GBR
services).
4.5.1 Non-GBR Service Admission

Admission control decides whether to admit a non-GBR service based on the number of radio bearers
used for non-GBR services in the cell, rather than the evaluated QoS satisfaction rate. The
CellRacThd.MaxNonGBRBearerNum parameter indicates the maximum number of radio bearers used
for non-GBR services in the cell. If the number of radio bearers used for non-GBR services after the
admission of a non-GBR service is smaller than CellRacThd.MaxNonGBRBearerNum, the non-GBR
services can be admitted in the cell.

eRAN
IMS services are directly admitted without evaluation on the QoS satisfaction rate. In addition, IMS
service admission is not restricted by CellRacThd.MaxNonGBRBearerNum.
Extended QCIs can be set according to the requirements of a specific operator. Their mapping services
are non-GBR services, and therefore the admission of these services is also restricted by
CellRacThd.MaxNonGBRBearerNum. If an extended QCI maps to QCI 5, the admission of the
services with the extended QCI is not restricted by CellRacThd.MaxNonGBRBearerNum.
When the value of CellRacThd.MaxNonGBRBearerNum is reached and preemption is enabled, a new
non-GBR service can preempt an admitted non-GBR service with a low priority. For details about
preemption, see section 4.5.3 "Preemption."
4.5.2 GBR Service Admission

This section takes the downlink admission process of GBR services as an example. Figure 4-2 shows
the downlink admission process of GBR services.

eRAN
Figure 4-2 Downlink admission process of GBR services
Check on the Number of PRBs Used by GBR Services

If the GbrUsageSwitch(GbrUsedPRbCheckSwitch) check box under the
CellAlgoSwitch.RacAlgoSwitch parameter is selected, the eNodeB determines whether to admit new
GBR services based on the number of PRBs used by the admitted GBR services. For handovers,
however, the eNodeB does not make such decisions. By limiting the number of PRBs used by GBR
services, the eNodeB prevents GBR services from occupying too many resources. If GBR services
occupy many resources, non-GBR services cannot obtain resources. As a result, the service rate for
non-GBR services may be 0.
When the proportion of PRBs used by the admitted GBR services is higher than
CellRacThd.GbrRbUsedHighThd, the eNodeB rejects the requests for new GBR services. If
preemption is enabled in the cell, a new GBR service can preempt an admitted GBR service. When the

eRAN
proportion is lower than CellRacThd.GbrRbUsedLowThd, the eNodeB admits GBR services to prevent
the ping-pong effect.
Decision on the PRB Usage and Transmit Power

The MAC layer periodically measures the PRB usage, which is filtered and then compared with the
upper and lower thresholds in the downlink and uplink:
In the downlink:
 If the PRB usage is low and the transmit power is not limited, the new service or handover is admitted.
 If the PRB usage is high or the transmit power is limited, the eNodeB checks whether to use the
admission method based on QoS satisfaction rates depending on setting of the
CellAlgoSwitch.RacAlgoSwitch parameter.
In the uplink, admission control does not need to check whether the transmit power is limited.
QoS Satisfaction Rate Evaluation

For details, see section 3.2.2 "Downlink QoS Satisfaction Rate Evaluation" and section 3.2.3 "Uplink
QoS Satisfaction Rate Evaluation."
Admission 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, the service
differentiation can be achieved by setting the admission offsets for new gold-, silver-, and bronze-level
services, depending 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 uplink and downlink.
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. Then, the rules of downlink
admission decision are as follows:
 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 new gold-, silver-, and bronze-level services and handovers corresponding
to QCI x are admitted.
If the QoS satisfaction rate of a QCI is lower than the corresponding handover admission threshold,
then new gold-, silver-, and bronze-level services corresponding to QCI x are rejected but handovers
corresponding to QCI x are admitted.

eRAN
 For QcixHoThd + CellRacThd.NewCopperServiceOffset > SQCI = x ≥ QcixHoThd +

CellRacThd.NewSilverServiceOffset
If the QoS satisfaction rates corresponding to all QCIs except QCI x are higher than the corresponding
handover admission thresholds, then new gold- and silver-level services and handovers
corresponding to QCI x are admitted but new bronze-level services are rejected.
 For QcixHoThd + CellRacThd.NewSilverServiceOffset > SQCI = x ≥ QcixHoThd +
CellRacThd.NewGoldServiceOffset
If the QoS satisfaction rates corresponding to all QCIs except QCI x are higher than the corresponding
handover admission thresholds, then new gold-level services and handovers corresponding to QCI x
are admitted but new silver- and bronze-level services are rejected.
 For QcixHoThd + CellRacThd.NewGoldServiceOffset > SQCI = x ≥ QcixHoThd
New gold-, silver-, bronze-level services corresponding to QCI x are rejected but handovers for QCI x
are admitted.
 For QcixHoThd > SQCI = x
Both new service and handovers corresponding to QCI x are rejected.
The rules of uplink admission decision are similar to the rules of downlink admission decision. The
difference is that the QoS satisfaction rate of logical channel group is evaluated for GBR services in the
uplink. For details, see section 3.2.3 "Uplink QoS Satisfaction Rate Evaluation."
4.5.3 Preemption
This section describes the radio resource preemption in the optional feature LOFD-00102901
Radio/transport Resource Pre-emption.
For details about the transport resource preemption, see Transport Resource Management Feature
If new services with high priorities cannot be admitted, they can preempt the admitted services with low
priorities in the cell. Preemption is triggered if one of the conditions as shown in Figure 4-1 is met.
Preemption can also be triggered in the case that the required resources are limited or the cell is
congested.
Preemption is enabled by selecting the PreemptionSwitch(PreemptionSwitch) check box under the
CellAlgoSwitch.RacAlgoSwitch parameter. Note that the SRBs, 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 does not have the preemption capability, it cannot be admitted. If a
service has the preemption capability, it can preempt a service that meets all of the following conditions:
 The to-be-preempted service is a GBR service if the preempting service is a GBR service, or the
to-be-preempted service is a non-GBR service if the preempting service is a non-GBR service.
 The value of the ARP IE "pre-emption vulnerability" of the to-be-preempted service is "pre-emptable".
 The value of the ARP IE "priority level" of the to-be-preempted service is greater than that of the
preempting service.

eRAN
 If the to-be-preempted service is a GBR service, the resources allocated to it are more than or equal to
the resources required by the preempting GBR service.
The preemption cannot be successful if any one of the preceding conditions is not met. If a new service
fails to preempt other services during initial access, the UE is redirected when redirection is enabled. For
details about operations related to redirection, see section 4.5.4 "Redirection."
If a handover service fails to preempt other services, relevant operations are performed based on the
actual situations. For detailed operations, see Mobility Management in Connected Mode Feature
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).
Procedure for Preempting a GBR Service

The eNodeB first groups GBR services with low priorities and then selects services that can be
preempted from the group. The procedure is as follows:
1. The eNodeB selects GBR services with low priorities and forms a group.
 The eNodeB first selects release-allowable GBR services, and then groups 10 services with the lowest
priorities among them. A release-allowable 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 service.
− The service rate is not 0.
 The eNodeB sorts the 10 GBR services based on the following rule: A service with the largest ARP IE
"priority level" value has the lowest priority and ranks first. If two services have the same ARP IE
"priority level" value, the service that occupies more RBs ranks ahead of the other.
2. The eNodeB selects services to be preempted.
 The eNodeB estimates the number of RBs required by a preempting service based on the average
spectral efficiency of the cell.
 The eNodeB calculates the number of RBs released from the group of GBR services with low priorities.
The release stops after the number of released RBs meets the requirements of the preempting service.
The preemption fails if no service can be preempted or the number of RBs of the preempted services
cannot meet the requirements of the preempting service.
 If the GBR service to be preempted is the only GBR service of a user, the user can be redirected when
redirection is enabled. For details about the redirection procedure, see section 4.5.4 "Redirection."
Procedure for Preempting a Non-GBR Service

If the preempting service is a non-GBR service, this service can preempt only non-GBR services. The
procedure for preempting a non-GBR service is as follows:
1. The eNodeB selects non-GBR services whose ARP IE "pre-emption vulnerability" is "pre-emptable".
2. The eNodeB excludes IMS signaling and emergency call services.
3. The eNodeB further selects the services whose ARP IE "priority level" value is greater than that of
the preempting service. The eNodeB then sorts the selected services based on the following rule: A
service with a larger ARP IE "priority level" value ranks ahead of a service with a smaller ARP IE
"priority level" value.
4. The service that ranks first is preempted first.
5. The preemption fails if no service can be preempted.

eRAN
4.5.4 Redirection
A UE that fails to access a cell can be redirected to another cell, even to an inter-RAT cell. This section
describes the eNodeB operations related to redirection.
When the eNodeB releases a UE, the eNodeB sends an RRC Connection Release message to the UE.
This message includes the redirection target frequency information for the UE to access a cell on the
target frequency. The redirection is controlled by LoadBasedSwitch under the
EnodeBAlgoSwitch.RedirectSwitch parameter.
 If a subscriber profile ID (SPID) has been specified for the UE, the eNodeB performs the following
steps regarding target frequency selection:
1. Determines the UE-capable RATs and frequency bands.
2. Checks for the mapping between frequencies and priorities in the associated SPID configuration.
3. Filters the frequencies defined in the SPID configuration according to the UE capabilities and
delivers them in descending order of priority.
For details about dedicated priorities and SPID, see Idle Mode Management Feature Parameter
Description and Flexible User Steering Feature Parameter Description, respectively.
 If the SPID has not been specified for the UE, the eNodeB performs the following steps regarding
target frequency selection:
2. Selects the UE-capable inter-RAT neighboring frequency with the highest reselection priority
specified by the UTRANRANSHARE.CellReselPriority parameter and delivers it to the UE.
 If the reselection priority of no neighboring frequency is specified by the
UTRANRANSHARE.CellReselPriority parameter, the eNodeB performs the following steps
regarding target frequency selection:
2. Selects the UE-capable inter-RAT neighboring frequency with the highest reselection priority
specified by the UTRANNFREQ.CellReselPriority parameter and delivers it to the UE.

eRAN
Admission and Congestion Control 5 Congestion Control
5 Congestion Control
Congestion control handles the congestion due to 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. In this case,
variations in the data volume inevitably affect the cell load.
 The radio conditions vary because of user mobility. In this case, the same service at the same data
rate may require different radio resources (such as PRBs and power) at different time points.
In the preceding 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. Therefore, the congestion control algorithm is required
to handle possible congestion.
The changes in radio channel conditions, UE locations, and packet switched (PS) services may result in
the changes in the occupied resources and cell load. When the cell load increases to a certain extent,
the cell gets congested. To solve this problem, congestion control is introduced to control the cell load,
ensuring the overall QoS satisfaction rate and system stability.
Figure 5-1 shows the congestion control process. Congestion control is enabled or disabled by selecting
or clearing the DlLdcSwitch(dlLdcSwitch) or UlLdcSwitch(ulLdcSwitch) check box under the
CellAlgoSwitch.RacAlgoSwitch parameter. Congestion control can function only after the
DlLdcSwitch(dlLdcSwitch) or UlLdcSwitch(ulLdcSwitch) check box is selected.
Figure 5-1 Congestion control process
When the cell is congested, congestion control releases the GBR services with low priorities first to
make some resources available. In this way, the quality of other admitted services can be ensured.
The release of low-priority GBR services reduces the resource load effectively. The eNodeB does not
release emergency calls so that the continuity and stability of emergency calls are ensured.

eRAN
Admission and Congestion Control 5 Congestion Control
This chapter describes the basic feature LBFD-002024 Congestion Control.
5.1 Load Status Decision

The eNodeB checks load status by monitoring the PRB usage, QoS satisfaction rate, and downlink
transmit power. The cell status can be either congested or normal.
 Congested state
The cell is regarded as congested if the QoS satisfaction rate corresponding to one or more QCIs is
lower than the relevant congestion threshold and the uplink or downlink PRB usage is high, or if the
downlink QoS satisfaction rate is lower than the relevant congestion threshold and the downlink
transmit power is limited.
When the cell is congested, all service requests are rejected and congestion control is triggered to
mitigate the congestion status in the uplink or downlink. When the QoS satisfaction rates of QCIs 1, 2,
3, and 4 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 higher than the
corresponding QcixCongThd (x = 1–4).
5.2 Release of Low-Priority GBR Services

If 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
operations related to redirection, see section 4.5.4 "Redirection."
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.

eRAN
Admission and Congestion Control 6 Related Features
6 Related Features
6.1 Admission Control
6.1.1 Required Features
Admission control depends on load monitoring and the following features:
 LBFD-002024 Congestion Control
 LBFD-002016 Dynamic Downlink Power Allocation
 LOFD-001015 Enhanced Scheduling
6.1.2 Mutually Exclusive Features

None
6.1.3 Affected Features

LBFD-002028 Emergency Call
This is an independent feature with the highest priority. If the admission of an emergency call fails,
preemption is enabled for the emergency call to preempt resources of other services.
6.2 Congestion Control

6.2.1 Required Features
Congestion control depends on load monitoring.
6.2.2 Mutually Exclusive Features

None
6.2.3 Affected Features

None

eRAN
Admission and Congestion Control 7 Impact on the Network
7 Impact on the Network

7.1 Admission Control
7.1.1 Impact on System 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 cannot be confirmed,
admission of new services fail and preemption will be triggered. The system capacity can be maximized
only after the QoS requirements are satisfied.
7.1.2 Impact on Network Performance

The admission control algorithm affects the admission success and handover success rates. This
algorithm sets different admission thresholds for users. For example, the thresholds for handovers and
admitting gold-level services are lower than the thresholds for admitting other types of services, which
means handovers and gold-level services are easier to be admitted. This ensures the handover and
admission success rates, and user experience for gold users.
7.2 Congestion Control

7.2.1 Impact on System Capacity
The congestion control algorithm maximizes system capacity while satisfying the QoS requirements of
admitted services. Before a system is congested, the load balancing algorithm moves some loads of the
system to inter-frequency and inter-RAT cells with light loads to maximize system capacity. After the
congestion threshold is reached, the congestion control algorithm informs the admission control
algorithm of the congestion. Then, the admission control algorithm starts to deny the admission of new
users.
7.2.2 Impact on Network Performance

The congestion control algorithm increases the service drop rate because it can trigger the release of
GBR bearers. These releases are counted as service drops and increases the service drop rate. There
are counters that indicate congestion-triggered service drops. For details about the counters, see
chapter 10 "Counters."

eRAN
Admission and Congestion Control 8 Engineering Guidelines
8 Engineering Guidelines
8.1 When to Use Admission and Congestion Control
8.1.1 Admission Control
Admission control applies to the following scenarios:
 Radio resources are insufficient, for example, during large-scale sports events or conference
rebroadcast.
Admission control should be performed when UEs in idle mode or new users initiate service requests
in the local cell. In handover scenarios where the target cell provides better signal quality than the
source cell, the target cell determines whether to accept admission requests from UEs based on the
system resource status (for example, the PRB usage and the QoS satisfaction rates of admitted
services).
 A UE initiates an emergency call or sets up a signaling radio bearer (SRB).
Emergency calls and SRBs take precedence over other services. They are admitted without the need
for admission evaluation.
 Operators share radio resources in radio access network (RAN) sharing scenarios.
The operators have purchased different proportions of radio resources and maintain their respective
QoS satisfaction rates. Based on the QoS satisfaction rates, the operators determine whether to admit
more services.
Admission control configurations vary depending on the service type, GBR or non-GBR. Set admission
control parameters in the following ways:
 The traffic volume in a cell increases, and the PRB usage by GBR services reaches the threshold for
determining that the PRB usage is high. In this scenario:
− Turn on admission control algorithm switches to enable admission control of requests for new
services or handovers based on resource usage. To enable admission control based on QoS
satisfaction rates of admitted services, turn on the satisfaction-rate-based admission control
algorithm switches.
− Toreserve resources for non-GBR services, turn on the switch specified by
GbrUsageSwitch(GbrUsedPRbCheckSwitch) under CellAlgoSwitch.RacAlgoSwitch. This
ensures that PRBs are not used up by GBR services and non-GBR services retain normal QoS
satisfaction rates and user experience.
− Toenable high-priority services to preempt low-priority services when resources are insufficient, turn
on the preemption switch.
− The emergency call service is subject to the operator's policy. If the operator provides the emergency
call service, turn on the emergency call switch and ensure that the settings on the E-UTRAN and
EPC are consistent to prioritize emergency calls. If the operator provides the emergency call service
for UEs in limited service mode, turn on the switch for emergency calls in limited service mode.
 The network is providing only non-GBR services.
In this scenario, set the CellRacThd.MaxNonGBRBearerNum parameter for admission control. This
parameter specifies the maximum number of bearers for non-GBR services that can be admitted to a
cell. By default, the parameter setting takes effect when an eNodeB uses the default configurations.
There is no switch for controlling the availability of this parameter.
8.1.2 Congestion Control

Radio and transmission resource management becomes increasingly important if the network becomes
congested with an increasing number of users and higher QoS requirement. Congestion control reduces

eRAN
the network load and maintains system stability while increasing the QoS satisfaction rate. The
congestion control algorithm brings little benefit when there is a small number of users on a network.
Congestion control applies to the following scenarios:
 When only GBR services are running on a network, the amount of data to be transmitted increases
due to service bursts, and the RB requirement increases because of deterioration in radio channel
conditions for some UEs. Therefore, the limited RBs cannot meet the QoS requirements of all services,
and UEs with unfavorable channel conditions retain low QoS satisfaction rates.
 When GBR and non-GBR services are running on a network, GBRs cannot be ensured when
congestion occurs.
In this situation, congestion control releases low-priority services. This may increase the service drop
rate. Therefore, the key performance indicator (KPI) measurement on the service drop rate in the
congested state must be distinguished from the service drop rates in other states.
8.2 Information to Be Collected

Collect the PRB usage and QoS satisfaction rates of cells.
The PRB usage and QoS satisfaction rates of cells are an important basis for evaluating the network
load. Based on scenarios and load conditions, admission control policies for different service types are
set during data planning. In addition, the admission threshold is adjusted if the access success rate is
low and the service drop rate is high due to a high network load. The purpose is to maximize resource
usage and maintain quality of admitted services.

Collect the PRB usage and QoS satisfaction rates of cells.
The PRB usage and QoS satisfaction rates of cells are provided by the admission control algorithm.
Congestion control is triggered based on the QoS satisfaction rates. If the QoS satisfaction rate of
services with QCI x (x = 1 to 4) falls below the congestion threshold for that QCI and the PRB usage is
high, the services with QCI x enter the congested state and the eNodeB performs overload evaluation.
8.3 Network Planning

8.3.1 RF Planning
N/A
8.3.2 Network Topology

Network topology 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 topology planning, operators 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.
8.3.3 Hardware Planning

N/A

eRAN
8.4 Deploying Admission Control

8.4.1 Deployment Requirements
Admission control has no requirements for the operating environment and transmission networking.
Requirements for the Core Network

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

To use preemption in admission control, operators must purchase and activate the following license.
Feature License Control Item Name

LOFD-001029 Enhanced Admission Control
8.4.2 Data Preparation

This section describes generic data and scenario-specific data to be collected. Generic data is
necessary for all scenarios and must always be collected. Scenario-specific data is collected only when
necessary for a specific scenario.
There are three types of data sources:
 Network plan (negotiation required): Parameters are planned by operators and negotiated with the
EPC or peer transmission equipment.
 Network plan (negotiation not required): Parameters are planned and set by operators.
 User-defined: Parameters are set as required by users.
Generic Data
N/A
Scenario-specific Data
Scenario 1: Check on the Number of PRBs Used by GBR Services
The following table describes the parameters that must be set in CellAlgoSwitch managed objects
(MOs) to enable the check on the number of PRBs used by GBR services.
Parameter Parameter ID Source Setting Description

Name
Local cell CellAlgoSwitch. Network plan This parameter specifies the local ID of a cell. It
ID LocalCellId (negotiation uniquely identifies a cell within an eNodeB.
not required) The actual value range for this parameter is 0 to 17.

eRAN

Name
RAC CellAlgoSwitch. Network plan  To enable the check on the number of PRBs used
algorithm RacAlgoSwitch (negotiation by GBR services, select the
switch not required) GbrUsageSwitch(GbrUsedPRbCheckSwitch)
check box.
 To disable this check, clear the
GbrUsageSwitch(GbrUsedPRbCheckSwitch)
check box.
The following table describes the parameters that must be set in CellRacThd MOs to configure the
check on the number of PRBs used by GBR services.
Parameter Parameter ID
Source Setting Description
Name
Local cell CellRacThd.Loc Network plan This parameter specifies the local ID of a cell. It
ID alCellId (negotiation uniquely identifies a cell within an eNodeB.
not required) The actual value range for this parameter is 0 to
17.
GBR used CellRacThd.Gbr Network plan This parameter specifies the threshold for deciding
resource RbUsedHighTh (negotiation whether the PRB usage by GBR services is high.
high d not required) The parameter applies to both uplink and downlink.
proportion If the MAC layer reports that the PRB usage by
threshold GBR services is greater than this parameter value,
the PRB usage is assumed to be high. Then, new
GBR services are not admitted if the check on the
number of PRBs used by GBR services is enabled.
The value 95 is recommended.
GBR used CellRacThd.Gbr Network plan This parameter specifies the threshold for deciding
resource RbUsedLowThd (negotiation whether the PRB usage by GBR services is low.
low not required) The parameter applies to both uplink and downlink.
proportion If the MAC layer reports that the PRB usage by
threshold GBR services is less than this parameter value, the
PRB usage is assumed to be low.
Scenario 2: 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.

eRAN
Name
Local cell CellAlgoSwitch. Network plan This parameter specifies the local ID of a cell. It
ID LocalCellId (negotiation uniquely identifies a cell within an eNodeB.
17.
RAC CellAlgoSwitch. Network plan  To enable downlink admission based on QoS
algorithm RacAlgoSwitch (negotiation satisfaction rates, select the
switch not required) 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
Name
Local cell CellRacThd.Loc Network plan This parameter specifies the local ID of a cell. It
ID alCellId (negotiation uniquely identifies a cell within an eNodeB.
17.
Gold CellRacThd.Gol Network plan This parameter specifies the ARP threshold for
service arp dServiceArpThd (negotiation gold-level services. A service is defined as a
threshold not required) gold-level service if its ARP value is less than or
equal to this parameter value. A smaller ARP value
indicates a higher priority.
Silver CellRacThd.Silv Network plan This parameter specifies the ARP threshold for
service arp erServiceArpTh (negotiation silver-level services. A service is defined as a
threshold d not required) silver-level service if its ARP value is less than or
equal to this parameter value and greater than the
value of CellRacThd.GoldServiceArpThd.
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.

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

eRAN
Name
Gold new CellRacThd.Ne Network plan This parameter specifies admission offset for new
service wGoldServiceOf (negotiation gold-level services. The parameter applies to both
admission fset not required) uplink and downlink.
threshold  New gold-level services and handed-over
offset 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
handed-over services with this QCI.
− TheQoS 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.
Silver new CellRacThd.Ne Network plan This parameter specifies admission offset for new
service wSilverService (negotiation silver-level services. The parameter applies to both
admission Offset not required) uplink and downlink.
threshold  New silver-level services and handed-over
offset services with a specific QCI are admitted if the
following conditions are both met:
 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.

eRAN
Name
Copper CellRacThd.Ne Network plan This parameter specifies admission offset for new
new wCopperServic (negotiation bronze-level services. The parameter applies to
service eOffset not required) both uplink and downlink.
admission  New bronze-level services and handed-over
threshold services with a specific QCI are admitted if the
offset following conditions are both met:
 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.
Uplink RB CellRacThd.UlR Network plan This parameter specifies the threshold for deciding
used ratio bHighThd (negotiation whether the uplink resource block (RB) usage is
high not required) high. If the MAC layer reports that the uplink RB
threshold usage is greater than this parameter value, the
uplink RB usage is assumed to be high. This
threshold is used in uplink admission decisions.
Downlink CellRacThd.DlR Network plan This parameter specifies the threshold for deciding
RB used bHighThd (negotiation whether the downlink RB usage is high. If the MAC
ratio high not required) layer reports that the downlink RB usage is greater
threshold than this parameter value, the downlink RB usage
is assumed to be high. This threshold is used in
downlink admission decisions.
Uplink RB CellRacThd.UlR Network plan This parameter specifies the threshold for deciding
used ratio bLowThd (negotiation whether the uplink RB usage is low. If the MAC
low not required) layer reports that the uplink RB usage is less than
threshold this parameter value, the uplink RB usage is
assumed to be low. This threshold is used in uplink
admission decisions.
Downlink CellRacThd.DlR Network plan This parameter specifies the threshold for deciding
RB used bLowThd (negotiation whether the downlink RB usage is low. If the MAC
ratio low not required) layer reports that the downlink RB usage is less
is assumed to be low. This threshold is used in

eRAN
Scenario 3: 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 preparing the parameters for enabling and configuring service preemption, prepare 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 2 in "Scenario-specific
Data."
The following table describes the parameters that must be set in CellAlgoSwitch MOs to enable service
preemption.

Name
Local cell ID CellAlgoSwitch.L Network plan This parameter specifies the local ID of a
ocalCellId (negotiation cell. It uniquely identifies a cell within an
not required) eNodeB.
The actual value range for this parameter is
0 to 17.
RAC algorithm CellAlgoSwitch.R Network plan PreemptionSwitch(PreemptionSwitch)
switch acAlgoSwitch (negotiation under this parameter specifies whether to
not required) enable service preemption.
 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 4: Non-GBR Service Admission

The following table describes the parameters that must be set in CellRacThd MOs to configure
non-GBR service admission.

Name
Local cell CellRacThd.Loc Network plan This parameter specifies the local ID of a cell.
ID alCellId (negotiation not It uniquely identifies a cell within an eNodeB.
required) The actual value range for this parameter is 0
to 17.

eRAN

Name
Non-GBR CellRacThd.Max Network plan This parameter specifies the maximum
max bearer NonGbrBearerN (negotiation not number of radio bearers used for non-GBR
number um required) services in the cell, excluding IP Multimedia
Subsystem (IMS) services. The parameter
applies to both uplink and downlink.
Set the parameter based on actual service
requirements.
8.4.3 Feature Activation

Configuring a Single eNodeB Using the GUI
Configure a single eNodeB using the Configuration Management Express (CME) graphical user
interface (GUI) based on the collected data described in section 8.4.2 "Data Preparation." For details,
see the procedure for configuring a single eNodeB on the CME GUI described in eNodeB Initial
Configuration Guide.
Configuring eNodeBs in Batches

To configure eNodeBs in batches, perform the following steps:
Step 1 On the GUI, set the parameters listed in the table for a specific scenario in this section, and save
the parameter settings as a user-defined template.
The parameters are the same as those described in section 8.4.2 "Data Preparation.
Step 2 Fill in the summary data file with the name of the user-defined template.
The parameter settings in the user-defined template will be applied to the eNodeBs after you import
the summary data file into the CME.
----End
For descriptions of the user-defined template and summary data file and also the detailed procedure for
configuring eNodeBs in batches, see eNodeB Initial Configuration Guide.
MO Parameter Group Name Parameter

CellAlgoSwitch CellAlgoSwitch Local cell ID, RAC algorithm switch
CellRacThd CellRacThd Local cell ID, GBR used resource high proportion
threshold (%), GBR used resource low proportion
threshold (%)

eRAN

CellRacThd CellRacThd Local cell ID, Gold service arp threshold, Silver
service arp threshold, QCI1 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(%), Downlink RB used ratio high
threshold(%), Uplink RB used ratio low threshold(%),
Downlink RB used ratio low threshold(%)

CellRacThd CellAlgoSwitch Local cell ID, RAC algorithm switch
CellRacThd CellRacThd Local cell ID, Gold service arp threshold, Silver service
arp threshold, QCI1 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(%),
Downlink RB used ratio high threshold(%), Uplink RB
used ratio low threshold(%), Downlink RB used ratio low
threshold(%)

CellRacThd CellRacThd Local cell ID, Non-GBR max bearer number
Configuring a Single eNodeB Using MML Commands

The activation procedure is as follows:
Step 1 Run the MOD CELLALGOSWITCH command to enable the check on the number of PRBs used
by GBR services.
Step 2 Run the MOD CELLRACTHD command to configure this check.
----End

eRAN

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

Step 1 Run the MOD CELLALGOSWITCH command to enable uplink and downlink admission based
on QoS satisfaction rates and enable service preemption.
Step 2 Run the MOD CELLRACTHD command to configure service preemption.
----End

Run the MOD CELLRACTHD command to set the maximum number of radio bearers for non-GBR
services in each cell.
8.4.4 Activation Observation

The verification procedure is as follows:
Step 1 On the M2000 client, start S1 interface tracing and start monitoring on the RB usage and number
of services.
1. 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.
− Choose Cell Performance Monitoring > Usage of RB Monitoring to create a task of
monitoring on the RB usage.
− Choose Cell Performance Monitoring > Service Statistics Monitoring to create a task of
monitoring on the number of services.
Step 2 Use UEs to access a cell, and perform GBR services with a QCI in the range of 2 to 4 on the UEs.
Ensure that the proportion of PRBs used by the GBR services is lower than the
CellRacThd.GbrRbUsedHighThd value. (The PRB usage by GBR services can be deduced
from the results of RB usage monitoring.)
Step 3 Check the S1AP_ERAB_SETUP_REQ and S1AP_ERAB_SETUP_RSP messages in the S1
interface tracing result.
If the S1AP_ERAB_SETUP_RSP message does not include the cause value for E-UTRAN radio
access bearer (E-RAB) setup failures, as shown in Figure 8-1, or if the number of services increases

eRAN
with the S1AP_ERAB_SETUP_REQ messages, then new GBR services have been successfully
admitted.
Figure 8-1 S1AP_ERAB_SETUP_RSP message indicating successful admission based on the check on
the PRB usage by GBR services
Step 4 Move some UEs to the cell center and increase the GBR traffic volume on these UEs until the
proportion of PRBs used by GBR services exceeds the CellRacThd.GbrRbUsedHighThd
value.
Step 5 Initiate a new GBR service with a QCI in the range of 2 to 4.
Step 6 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 8-2, or if the number of services does not
increase with the S1AP_ERAB_SETUP_REQ messages, then the new GBR service requests have
been rejected.
Figure 8-2 S1AP_ERAB_SETUP_RSP message indicating failed admission based on the check on the
PRB usage by GBR services
----End

Step 1 On the M2000 client, start S1 interface tracing and start monitoring on the following items: QoS
satisfaction rate, RB usage, and the number of services.
task.
− Choose Cell Performance Monitoring > Satisfaction of Service Monitoring to create a
task of monitoring on QoS satisfaction rates.

eRAN
Move some UEs to the cell center and increase the GBR traffic volume on these UEs until the
MAC layer reports that the uplink or downlink RB usage is higher than
CellRacThd.UlRbHighThd or CellRacThd.DlRbHighThd, respectively. (The PRB usage of
GBR services can be deduced from the results of RB usage monitoring.) In addition, 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.
Step 3 Initiate a new GBR service with this QCI.
Step 4 Follow the operation in Step 6 for scenario 1 in section 8.4.4 "Activation Observation" to verify
that the new GBR service fails to be admitted.
----End

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 8-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 8-3 S1AP_ERAB_SETUP_REQ message including the ARP value and the preemption attributes

task.

eRAN

Step 2 Use UEs to access a cell, and perform GBR service B on some UEs.
Step 3 Perform GBR service A on some other UEs. Follow the operation in Step 2 for scenario 2 in
section 8.4.4 "Activation Observation" so that requests for GBR service A are first rejected due to
Step 4 Monitor S1 signaling to verify that GBR service A preempts GBR service B. GBR service B is
released, as shown in Figure 8-4. Follow the operation in Step 3 for scenario 1 in section 8.4.4
"Activation Observation" to verify that GBR service A has been successfully admitted to the cell.
Figure 8-4 S1AP_ERAB_REL_IND message indicating successful preemption
----End

Step 1 On the M2000 client, start S1 interface tracing and start monitoring on the number of services.
task.
Step 2 Use UEs to access a cell until the number of non-GBR services in the cell reaches the
CellRacThd.MaxNonGBRBearerNum value.
Step 3 Use some other UEs to attempt to access the cell.
Step 4 Monitor S1 signaling, as shown in Figure 8-5, to verify that the default non-GBR E-RABs fail to
be set up for these UEs.
Figure 8-5 S1AP_INITIAL_CONTEXT_SETUP_FAIL message indicating a failure to set up the default
non-GBR E-RAB

eRAN
----End
8.4.5 Deactivation
Run the MOD CELLALGOSWITCH command to disable the check on the number of PRBs used by
GBR services.

Run the MOD CELLALGOSWITCH command to disable the algorithms for uplink and downlink

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

Non-GBR service admission is enabled by default. No switch is available for enabling or disabling
non-GBR service admission. To restore the test environment for non-GBR service admission, run the
MOD CELLRACTHD command with the CellRacThd.MaxNonGBRBearerNum parameter changed to
its default value.
8.5 Deploying Congestion Control

8.5.1 Deployment Requirements
Congestion control has the following requirement for the EPC:
According to 3GPP TS 23.401, only the services whose ARP-related IE Pre-emption Vulnerability is
"pre-emptable" can be released if the switch specified by DlLdcSwitch(dlLdcSwitch) or
UlLdcSwitch(ulLdcSwitch) is turned on. Therefore, the IE Pre-emption Vulnerability must be set to
"pre-emptable" in the EPC.
Congestion control has no requirements for the operating environment, transmission networking, and
licenses.
8.5.2 Data Preparation

Generic Data
The following table describes the parameters that must be set in CellAlgoSwitch MOs to enable the
congestion control algorithms.
Parameter Parameter Source Setting Description

Name ID
Local cell ID CellAlgoS Network plan This parameter specifies the local ID of a cell. It
witch.Loca (negotiation uniquely identifies a cell within an eNodeB.
lCellId not required) The actual value range for this parameter is 0 to 17.

eRAN
Parameter Parameter Source Setting Description

Name ID
RAC CellAlgoS Network plan  To enable downlink congestion detection, select the
algorithm witch.RacA (negotiation DlLdcSwitch(dlLdcSwitch) check box. If congestion
switch lgoSwitch not required) is detected, congestion relief actions are taken.
 To disable downlink congestion detection, clear the
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.
Scenario-specific Data
The following table describes the parameters that must be set in CellRacThd MOs to configure the
congestion control algorithms.

Name
Local cell CellRacThd.Lo Network plan This parameter specifies the local ID of a cell. It
ID calCellId (negotiation not uniquely identifies a cell within an eNodeB.
required) The actual value range for this parameter is 0 to
17.
QCI1 CellRacThd.Q Network plan This parameter specifies the congestion threshold
congest ci1CongThd (negotiation not for services with a QCI of 1. It applies to both uplink
threshold required) 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.
higher than the sum of this threshold and
CellRacThd.CongRelOffset, these services exit
the congested state.

eRAN

Name
Offset for CellRacThd.C Network plan This parameter specifies the congestion relief
service ongRelOffset (negotiation not offset.
congest required)  If the QoS satisfaction rate of services with a
relieving 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.
lower than the sum of this offset and the
congestion threshold for that QCI, these services
remain in the congested state.

eRAN

Name
Uplink RB CellRacThd.Ul Network plan This parameter specifies the threshold for deciding
used ratio RbHighThd (negotiation not whether the uplink RB usage is high. If the MAC
high required) layer reports that the uplink RB usage is greater
threshold than this parameter value, the uplink RB usage is
assumed to be high. This threshold is used in
uplink admission decisions.
Downlink CellRacThd.Dl Network plan This parameter specifies the threshold for deciding
RB used RbHighThd (negotiation not whether the downlink RB usage is high. If the MAC
ratio high required) layer reports that the downlink RB usage is greater
is assumed to be high. This threshold is used in
Uplink RB CellRacThd.Ul Network plan This parameter specifies the threshold for deciding
used ratio RbLowThd (negotiation not whether the uplink RB usage is low. If the MAC
low required) layer reports that the uplink RB usage is less than
threshold this parameter value, the uplink RB usage is
assumed to be low. This threshold is used in uplink
admission decisions.
Downlink CellRacThd.Dl Network plan This parameter specifies the threshold for deciding
RB used RbLowThd (negotiation not whether the downlink RB usage is low. If the MAC
ratio low required) layer reports that the downlink RB usage is less
is assumed to be low. This threshold is used in
8.5.3 Feature Activation

Configuring a Single eNodeB Using the GUI
Configure a single eNodeB using the CME GUI based on the collected data described in section 8.5.2
"Data Preparation." For details, see the procedure for configuring a single eNodeB on the CME GUI
described in eNodeB Initial Configuration Guide.
Configuring eNodeBs in Batches

To configure eNodeBs in batches, perform the following steps:
Step 1 On the GUI, set the parameters listed in the table provided in this section, and save the
parameter settings as a user-defined template.
The parameters are the same as those described in section 8.5.2 "Data Preparation.
Step 2 Fill in the summary data file with the name of the user-defined template.

eRAN
The parameter settings in the user-defined template will be applied to the eNodeBs after you import
the summary data file into the CME.
----End
For descriptions of the user-defined template and summary data file and also the detailed procedure for
configuring eNodeBs in batches, see eNodeB Initial Configuration Guide.

CellRacThd CellRacThd Local cell ID, QCI1 congest threshold(%), QCI2 congest
threshold(%), QCI3 congest threshold(%), QCI4
congest threshold(%), Offset for service congest
relieving(%), Uplink RB used ratio high threshold(%),
Downlink RB used ratio high threshold(%), Uplink RB
used ratio low threshold(%), Downlink RB used ratio
low threshold(%)
Configuring a Single eNodeB Using MML Commands

Step 1 Run the MOD CELLALGOSWITCH command to enable the uplink and downlink congestion
control algorithms.
Step 2 Run the MOD CELLRACTHD command to configure the congestion control algorithms.
----End
8.5.4 Activation Observation

task.
Move some UEs to the cell center and increase the GBR traffic volume on these UEs until the
MAC layer reports that the uplink or downlink RB usage is higher than
CellRacThd.UlRbHighThd or CellRacThd.DlRbHighThd, respectively. (The PRB usage of

eRAN
GBR services can be deduced from the results of RB usage monitoring.) In addition, 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.
Step 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 8-6, the indicated low-priority service has
been released as expected. Note that the eNodeB stops releasing services when there are two or
fewer services in the cell, preventing excessive release.
Figure 8-6 S1AP_ERAB_REL_IND message indicating the release of a low-priority service
----End
8.5.5 Deactivation
Run the MOD CELLALGOSWITCH command to disable the uplink and downlink congestion control
algorithms.
8.6 Performance Optimization

None
8.7 Troubleshooting
Fault Description
High-priority services fail to preempt low-priority services.
Fault Handling
Step 1 Check whether the IE priorityLevel in the S1AP_ERAB_SETUP_REQ message, as shown in
Figure 8-7, of the service to be preempted is greater than that of the preempting service.
 If yes, go to Step 2.
 If no, change the values accordingly at the EPC.

eRAN
Figure 8-7 Checking the ARP value
Step 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.
----End

None

eRAN
Admission and Congestion Control 9 Parameters
9 Parameters
Table 9-1 Parameter description
MO Parameter ID MML Command Feature ID Feature Description
Name
UtranRanSh CellReselPriority ADD LBFD-00201 Cell Meaning:Indicates the cell

are UTRANRANSH 803 / Selection reselection priority of the
ARE TDLBFD-002 and operator that shares the
01803 Reselectio neighboring UTRAN frequency.
MOD n / Cell If the related SPID
UTRANRANSH Selection configuration is specified, set
ARE and this priority to the one specified
LST Re-selecti in the SPID configuration. If no
UTRANRANSH on related SPID configuration is
ARE specified but this parameter is
set, the eNodeB delivers the
cell reselection priorities of all
PLMNs supported by a UE by
using the IE
idleModeMobilityControlInfo in
an RRC Connection Release
message to the UE. If no
related SPID configuration is
specified and this parameter is
not set, a UE uses the cell
reselection priority of the
neighboring UTRAN frequency,
which is broadcast in the
system information.
GUI Value Range:0~7
Unit:None
Actual Value Range:0~7
Default Value:0
UtranNFreq CellReselPriority ADD LBFD-00201 Cell Meaning:The UE decides

UTRANNFREQ 803 / Selection whether to reselect a
TDLBFD-002 and neighboring cell on the UTRAN
MOD 01803 Reselectio frequency based on the value
UTRANNFREQ n of this parameter and the
LBFD-00200 absolute priority of the serving
LST 9/ Broadcast cell.
UTRANNFREQ TDLBFD-002 of System
009 Informatio If the value of this parameter is
n larger than the absolute priority
of the serving cell, the UE
starts measurements on
neighboring cells on the
UTRAN frequency; then if the
signal quality of some
neighboring cells meets the

eRAN

Name
related conditions, the UE
starts cell reselection.
If the value of this parameter is
smaller than the absolute
priority of the serving cell, the
UE starts the measurements
only when the signal quality of
the serving cell is poor; then if
the signal quality of some
neighboring cells meets the
related conditions, the UE
starts cell reselection.
Frequencies used for different
RATs must be assigned
different cell reselection
priorities. For details, see
3GPP TS 36.331.
GUI Value Range:0~7
Unit:None
Default Value:1
CellRacThd CongRelOffset MOD LBFD-00100 3GPP R8 Meaning:Indicates the

CELLRACTHD 1 / Specificati congestion release offset. The
TDLBFD-001 ons service of a specific QCI exits
LST 001 the congestion state if the
CELLRACTHD Congestio satisfaction rate of the service
LBFD-00202 n Control exceeds the sum of this
4/ congestion release offset and
TDLBFD-002 the congestion threshold for
024 the QCI. The service retains
the congestion state if the
satisfaction rate is below the
sum of this congestion release
offset and the congestion
threshold for the QCI.
GUI Value Range:0~50
Unit:%
Default Value:20
CellRacThd DlRbHighThd MOD LBFD-00100 3GPP R8 Meaning:Indicates the

CELLRACTHD 1 / Specificati threshold for deciding on
TDLBFD-001 ons whether the DL resource block
LST 001 (RB) usage is high. This
Admission threshold applies to DL

eRAN

Name
CELLRACTHD LBFD-00202 Control admission decision. If the
3/ usage of the DL RB reported
TDLBFD-002 Congestio by the MAC layer is above this
023 n Control threshold, the DL RB usage is
assumed to be high.
LBFD-00202
4/ GUI Value Range:10~100
TDLBFD-002
024 Unit:%
Default Value:95
CellRacThd DlRbLowThd MOD LBFD-00100 3GPP R8 Meaning:Indicates the

TDLBFD-001 ons whether the DL resource block
LST 001 (RB) usage is low. This
CELLRACTHD Admission threshold applies to DL
LBFD-00202 Control admission decision. If the
3/ usage of the DL RB reported
TDLBFD-002 Congestio by the MAC layer is below this
023 n Control
threshold, the usage of the DL
LBFD-00202 RB is assumed to be low.
TDLBFD-002
024 Unit:%
Default Value:90
CellRacThd GbrRbUsedHigh MOD LBFD-00100 3GPP R8 Meaning:Indicates the

Thd CELLRACTHD 1 / Specificati threshold for high PRB usage
TDLBFD-001 ons by GBR services. The value of
LST 001 this parameter is expressed in
CELLRACTHD Admission percentage and applies to both
LBFD-00202 Control UL and DL. If the MAC layer
3/ detects that the PRB usage by
TDLBFD-002 GBR services exceeds the
023 threshold, the usage is high. In
this situation, new GBR
services are not admitted if
GbrUsageSwitch under the
RacAlgoSwitch parameter is
turned on.
Unit:%
Default Value:95

eRAN

Name
CellRacThd GbrRbUsedLow MOD LBFD-00100 3GPP R8 Meaning:Indicates the

Thd CELLRACTHD 1 / Specificati threshold for low PRB usage
TDLBFD-001 ons by GBR services. The value of
LST 001 this parameter is expressed in
CELLRACTHD Admission percentage and applies to both
LBFD-00202 Control UL and DL. If the MAC layer
3/ detects that the PRB usage by
TDLBFD-002 GBR services falls below the
023 threshold, the usage is
considered to be low.
Unit:%
Default Value:90
CellRacThd GoldServiceArpT MOD LBFD-00202 Admission Meaning:Indicates the

hd CELLRACTHD 3 / Control Allocation and Retention
TDLBFD-002 Priority (ARP) threshold for the
LST 023 Congestio Golden-level services. A
CELLRACTHD n Control service is defined as a
LBFD-00202
4/ Basic Qos Golden-level service if its ARP
value is smaller than or equal
TDLBFD-002 Managem to this threshold. The service
024 ent
priority has a negative
LBFD-00300 correlation with the ARP value.
TDLBFD-003
002 Unit:None
Default Value:5
CellRacThd LocalCellId LST LBFD-00100 3GPP R8 Meaning:Indicates the local

CELLRACTHD 1 / Specificati cell ID. It uniquely identifies a
TDLBFD-001 ons cell within a BS.
MOD 001
CELLRACTHD GUI Value Range:0~17
Unit:None
Default Value:None
CellAlgoSwit LocalCellId LST None None Meaning:Indicates the local ID

ch CELLALGOSWI of the cell. It uniquely identifies
TCH a cell within a BS.
MOD

eRAN

Name
CELLALGOSWI GUI Value Range:0~17
TCH
Unit:None
Default Value:None
CellRacThd MaxNonGbrBear MOD LBFD-00100 3GPP R8 Meaning:Indicates the

erNum CELLRACTHD 1 / Specificati maximum number of non-GBR
TDLBFD-001 ons services (excluding IP
LST 001 Multimedia Subsystem [IMS]
CELLRACTHD Admission services) that can be provided
LBFD-00202 Control by a cell. The value of this
3/ parameter is applied to both UL
TDLBFD-002 and DL.
023
Unit:None
Default Value:3000
CellRacThd NewCopperServi MOD LBFD-00100 3GPP R8 Meaning:Indicates the offset

ceOffset CELLRACTHD 1 / Specificati for admission of new
TDLBFD-001 ons Bronze-level services. The
LST 001 value of this parameter applies
CELLRACTHD Admission in both UL and DL. New
LBFD-00202 Control Bronze-level services with QCI
3/ N can be admitted if both the
TDLBFD-002 following conditions are met:
023 (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
services with that QCI.
Unit:%
Default Value:5

eRAN

Name
CellRacThd NewGoldService MOD LBFD-00100 3GPP R8 Meaning:Indicates the offset

Offset CELLRACTHD 1 / Specificati for admission of new
TDLBFD-001 ons Gold-level services. The value
LST 001 of this parameter applies in
CELLRACTHD Admission both UL and DL. New
LBFD-00202 Control Gold-level services with QCI N
3/ can be admitted if both the
Unit:%
Default Value:5
CellRacThd NewSilverServic MOD LBFD-00100 3GPP R8 Meaning:Indicates the offset

eOffset CELLRACTHD 1 / Specificati for admission of new
TDLBFD-001 ons Silver-level services. The value
LST 001 of this parameter applies in
CELLRACTHD Admission both UL and DL. New
LBFD-00202 Control Silver-level services with QCI
3/ N can be admitted if both the
Unit:%

eRAN

Name
Default Value:5
CellRacThd Qci1CongThd MOD LBFD-00100 3GPP R8 Meaning:Indicates the

CELLRACTHD 1 / Specificati congestion threshold for
TDLBFD-001 ons services with QCI of 1. This
LST 001 threshold applies to both UL
CELLRACTHD Congestio and DL.
LBFD-00202 n Control
4/ If the satisfaction rate of
TDLBFD-002 services with QCI of 1 in the
024 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
Unit:%
Default Value:65
CellRacThd Qci1HoThd MOD LBFD-00100 3GPP R8 Meaning:Indicates the

CELLRACTHD 1 / Specificati admission threshold for the
TDLBFD-001 ons handed-over service with QCI
LST 001 of 1. This threshold applies to
CELLRACTHD Admission both UL and DL.
LBFD-00202 Control
TDLBFD-002 services with QCI of 1 is above
023 or equal to this threshold, the
handed-over service with QCI
of 1 can be admitted.
services with QCI of 1 is below
this threshold, the handed-over
service with QCI of 1 cannot be
admitted.
Unit:%

eRAN

Name
Default Value:90

state.
Unit:%
Default Value:65

LBFD-00202 Control
admitted.
Unit:%

eRAN

Name
Default Value:90

4/ If the satisfaction rate of the
state.
Unit:%
Default Value:65

LBFD-00202 Control
admitted.
Unit:%

eRAN

Name
Default Value:90

state.
Unit:%
Default Value:65

LBFD-00202 Control
admitted.
Unit:%

eRAN

Name
Default Value:90
CellAlgoSwit RacAlgoSwitch MOD LBFD-00100 3GPP R8 Meaning:Indicates the

ch CELLALGOSWI 1 / Specificati switches used to enable or
TCH TDLBFD-001 ons disable the admission and load
001 control algorithms.
LST Admission
CELLALGOSWI LBFD-00202 Control DlSwitch: Indicates whether to
TCH 3/ enable or disable the
TDLBFD-002 Congestio satisfaction rate-based
023 n Control admission control algorithm in
the downlink. If this switch is
LBFD-00202 Radio/tran turned on, the algorithm is
4/ sport
enabled. If this switch is turned
TDLBFD-002 Resource off, the algorithm is
024 Pre-empti
on disabled.During the calculation
LOFD-00102 of the QoS satisfaction rate for
901 / services with different QCIs,
TDLOFD-00 the dedicated VoIP service
102901 satisfication estimation method
is used for the services with
QCI 1. If services with QCI 1
are not all VoIP services, the
satisfication 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 QCI 1 are
VoIP services, this switch is
advised to be turned off.
UlSwitch: Indicates whether to
enable or disable the
satisfaction rate-based
admission control algorithm in
the uplink. If this switch is
turned on, the algorithm is
off, the algorithm is
disabled.During the calculation
of the QoS satisfaction rate for
services with different QCIs,
the dedicated VoIP service
satisfication estimation method

eRAN

Name
the admission of GBR
services. Therefore, if not all
the services with QCI 1 are
VoIP services, this switch is
advised to be turned off.
DlPredictSwitch: Indicates
whether to enable or disable
the prediction-based
the downlink. If this switch is
off, the algorithm is disabled.
This switch will be removed in
the later versions. In this
version, the setting of this
switch is still synchronized
between the M2000 and the
eNodeB, but it is no longer
used internally. Therefore,
avoid using this switch.
UlPredictSwitch: Indicates
the prediction-based
the uplink. If this switch is
off, the algorithm is disabled.
This switch will be removed in
the later versions. In this
version, the setting of this
switch is still synchronized
between the M2000 and the
eNodeB, but it is no longer
used internally. Therefore,
avoid using this switch.
GbrUsageSwitch: Indicates
the check on the number of
PRBs used by GBR services. If
this switch is turned on, a
check is performed on whether
the number of PRBs used by
admitted GBR services
exceeds the related threshold
during the admission
evaluation of a new GBR
service. If this switch is turned
off, the check is not performed

eRAN

Name
during the admission
evaluation of a new GBR
service.
DlLdcSwitch: Indicates
the downlink load control
algorithm. If this switch is
turned on, downlink congestion
checks are performed and if
the cell is congested,
corresponding actions can be
taken to relieve the congestion.
If this switch is turned off,
downlink congestion checks
are not performed; therefore,
downlink congestion, if any,
cannot be relieved. During the
calculation of the QoS
satisfaction rate for services
with different QCIs, the
dedicated VoIP service
the load control of the cell.
Therefore, if not all the
services with QCI 1 are VoIP
services, this switch is advised
to be turned off.
UlLdcSwitch: Indicates
the uplink load control
algorithm. If this switch is
turned on, uplink congestion
checks are performed and if
the cell is congested,
corresponding actions can be
taken to relieve the congestion.
If this switch is turned off,
uplink congestion checks are
not performed; therefore,
uplink congestion, if any,
cannot be relieved. During the
calculation of the QoS
satisfaction rate for services
with different QCIs, the
dedicated VoIP service

eRAN

Name
the load control of the cell.
Therefore, if not all the
services with QCI 1 are VoIP
services, this switch is advised
to be turned off.
RelDrbSwitch: Indicates
the algorithm of releasing
low-priority services in the
case of congestion. If this
switch is turned on, release of
such services is allowed in the
case of congestion. If this
switch is turned off, release of
such services is prohibited in
the case of congestion.This
switch will be removed in the
later versions. In this version,
the setting of this switch is still
synchronized between the
M2000 and the eNodeB, but it
is no longer used internally.
Therefore, avoid using this
switch.
PreemptionSwitch: Indicates
the preemption algorithm. If
this switch is turned on, some
high-priority services can
access the system by means
of preemption if their
admission requests are
rejected. If this switch is turned
off, only emergency calls can
access the system when
resources are insufficient.
GUI Value
Range:DlSwitch(dlCacSwitch),
UlSwitch(ulCacSwitch),
DlPredictSwitch(dlCacPredictS
witch),
UlPredictSwitch(ulCacPredictS
witch),

eRAN

Name
GbrUsageSwitch(GbrUsedPR
bCheckSwitch),
DlLdcSwitch(dlLdcSwitch),
UlLdcSwitch(ulLdcSwitch),
RelDrbSwitch(LdcDrbRelSwitc
h),
PreemptionSwitch(Preemption
Switch)
Unit:None
Actual Value Range:DlSwitch,
UlSwitch, DlPredictSwitch,
UlPredictSwitch,
GbrUsageSwitch,
DlLdcSwitch, UlLdcSwitch,
RelDrbSwitch,
PreemptionSwitch
Default Value:dlCacSwitch:Off,
ulCacSwitch:Off,
dlCacPredictSwitch:Off,
ulCacPredictSwitch:Off,
GbrUsedPRbCheckSwitch:Off,
dlLdcSwitch:Off,
ulLdcSwitch:Off,
LdcDrbRelSwitch:Off,
PreemptionSwitch:Off
ENodeBAlgo RedirectSwitch MOD LOFD-00101 PS Meaning:Indicates the switch

Switch ENODEBALGO 9 / Inter-RAT used to enable or disable the
SWITCH TDLOFD-00 Mobility redirection algorithm. This
1019 between switch does not control
LST E-UTRAa redirection for CS fallback or
ENODEBALGO LOFD-00102 nd flash CS fallback.
SWITCH 0/ UTRAN
TDLOFD-00 GeranFlashRedirectSwitch: If
1020 PS both this switch and the switch
Inter-RAT for redirection to GERAN are
LBFD-00201 Mobility turned on, fast redirection to
803 / between GERAN is enabled.
TDLBFD-002 E-UTRAa
01803 nd UranFlashRedirectSwitch: If
GERAN both this switch and the switch
for redirection to UTRAN are
Cell turned on, fast redirection to
Selection UTRAN is enabled.
and
Re-selecti GUI Value
on Range:LoadBasedSwitch,
GeranFlashRedirectSwitch,
UranFlashRedirectSwitch
Unit:None

eRAN

Name
Actual Value
Range:LoadBasedSwitch,
GeranFlashRedirectSwitch,
UranFlashRedirectSwitch
Default
Value:LoadBasedSwitch:Off,
GeranFlashRedirectSwitch:Off,
UranFlashRedirectSwitch:Off
CellRacThd SilverServiceArp MOD LBFD-00202 Admission Meaning:Indicates the

Thd CELLRACTHD 3 / Control Allocation and Retention
TDLBFD-002 Priority (ARP) threshold for the
LST 023 Congestio Silver-level services. A service
CELLRACTHD n Control is defined as a Silver-level
LBFD-00202
4/ Basic Qos service if its ARP value is
smaller than or equal to the
TDLBFD-002 Managem value of this parameter and is
024 ent
larger than the value of
LBFD-00300 GoldServiceArpThd. A service
2/ is defined as a Bronze-level
TDLBFD-003 service if its ARP value is
002 larger than the value of this
parameter. The service priority
has a negative correlation with
the ARP value.
Unit:None
Default Value:10
CellRacThd UlRbHighThd MOD LBFD-00100 3GPP R8 Meaning:Indicates the

TDLBFD-001 ons whether the UL RB usage is
LST 001 high. This threshold applies to
CELLRACTHD Admission UL admission decision. If the
LBFD-00202 Control UL RB usage reported by the
3/ MAC layer is above this
TDLBFD-002 Congestio threshold, the UL RB usage is
023 n Control
assumed to be high.
LBFD-00202 GUI Value Range:10~100
4/
TDLBFD-002 Unit:%
024
Default Value:95
CellRacThd UlRbLowThd MOD LBFD-00100 3GPP R8 Meaning:Indicates the

eRAN

Name
TDLBFD-001 ons whether the UL RB usage is
LST 001 low. It applies to UL admission
CELLRACTHD Admission decision. If the UL RB usage
LBFD-00202 Control reported by the MAC layer is
3/ below this threshold, the UL
TDLBFD-002 Congestio RB usage is assumed to be
023 n Control
low.
LBFD-00202 GUI Value Range:10~100
4/
TDLBFD-002 Unit:%
024
Default Value:90

eRAN
Admission and Congestion Control 10 Counters
10 Counters
Table 10-1 Counter description
Counter ID Counter Name Counter Feature ID Feature Name
Description
1526726760 L.LC.ULCong.Num.Cell Number of times LBFD-002024 Congestion

uplink congestion Control
occurs in a cell TDLBFD-002024
Congestion
Control
1526726761 L.LC.ULCong.Dur.Cell Duration of uplink LBFD-002024 Congestion

congestion in a Control
cell TDLBFD-002024
Congestion
Control
1526726762 L.LC.DLCong.Num.Cell Number of times LBFD-002024 Congestion

downlink Control
congestion occurs TDLBFD-002024
in a cell Congestion
Control
1526726763 L.LC.DLCong.Dur.Cell Duration of LBFD-002024 Congestion

downlink Control
congestion in a TDLBFD-002024
cell Congestion
Control
1526726764 L.LC.User.Rel Number of GBR LBFD-002024 Congestion

service releases Control
due to congestion TDLBFD-002024
in a cell Congestion
Control
1526728279 L.E-RAB.FailEst.NoRadioRes Number of E-RAB LBFD-002008 Radio Bearer

setup failures due Management
to insufficient TDLBFD-002008
radio resources LBFD-002023 Radio Bearer
Management
TDLBFD-002023 Admission
Control
Admission
Control
1526728325 L.RRCRedirection.IntraLTE Number of LBFD-002023 Admission

redirections in the Control
E-UTRAN TDLBFD-002023
Admission
LBFD-00201802 Control
Coverage Based

eRAN
Admission and Congestion Control 10 Counters
Counter ID Counter Name Counter Feature ID Feature Name

Description
TDLBFD-00201802 Inter-frequency
Handover
LBFD-00201804
Coverage Based
Inter-frequency
Handover
Distance Based
Inter-frequency
Handover

eRAN
Admission and Congestion Control 11 Glossary
11 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
Admission and Congestion Control 12 Reference Documents
12 Reference Documents
This chapter lists the reference documents related to admission and congestion control:
[1] 3GPP TS 23.203, "Policy and charging control architecture"
[2] 3GPP TS 36.306, "User Equipment (UE) radio access capabilities"
[3] 3GPP TS 36.300, "E-UTRAN Overall description"
[4] 3GPP TS 36.413, "S1 Application Protocol (S1AP)"
[5] 3GPP TS 36.423, "X2 Application Protocol (X2AP)"
[6] 3GPP TS 36.331, "Radio Resource Control (RRC)"
[7] 3GPP TS 23.401, "General Packet Radio Service (GPRS) enhancements for Evolved Universal
Terrestrial Radio Access Network (E-UTRAN) access"
[8] eNodeB Performance Counter Reference
[9] eNodeB MO Reference
[10] Transport Resource Management Feature Parameter Description
[11] Idle Mode Management Feature Parameter Description
[12] Mobility Management in Connected Mode Feature Parameter Description
[13] Scheduling Feature Parameter Description
[14] eNodeB Initial Configuration Guide
[15] Emergency Call Feature Parameter Description
[16] MLB Feature Parameter Description


Admission and Congestion Control (ERAN3.0 - 03)

Uploaded by

Copyright:

Available Formats

You might also like

Admission and Congestion Control (ERAN3.0 - 03)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Admission and Congestion Control (ERAN3.0 - 03)

Uploaded by

Copyright:

Available Formats

Admission and Congestion Control

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

4 Admission Control ....................................................................................................................4-1

5 Congestion Control ..................................................................................................................5-1

6 Related Features .......................................................................................................................6-1

7 Impact on the Network ............................................................................................................7-1

Issue 03 (2012-12-29) Huawei Proprietary and Confidential i

7.1.2 Impact on Network Performance .......................................................................................... 7-1

Issue 03 (2012-12-29) Huawei Proprietary and Confidential ii

1.2 Intended Audience

1.3 Change History

Change Type Change Description Parameter Change

Issue 03 (2012-12-29) Huawei Proprietary and Confidential 1-1

Change Type Change Description Parameter Change

Change Type Change Description Parameter Change

Issue 03 (2012-12-29) Huawei Proprietary and Confidential 1-2

Change Type Change Description Parameter Change

Issue 03 (2012-12-29) Huawei Proprietary and Confidential 1-3

Issue 03 (2012-12-29) Huawei Proprietary and Confidential 2-1

3.1 PRB Usage Monitoring

3.2 GBR-Service QoS Satisfaction Rate Monitoring

Issue 03 (2012-12-29) Huawei Proprietary and Confidential 3-1

3.2.2 Downlink QoS Satisfaction Rate Evaluation

3.2.3 Uplink QoS Satisfaction Rate Evaluation

3.3 Resource Limitation Indications

Issue 03 (2012-12-29) Huawei Proprietary and Confidential 3-2

Issue 03 (2012-12-29) Huawei Proprietary and Confidential 3-3

Issue 03 (2012-12-29) Huawei Proprietary and Confidential 4-1

Figure 4-1 Process of admission control

Issue 03 (2012-12-29) Huawei Proprietary and Confidential 4-2

4.1 Key Techniques

4.2 Service Attributes

Issue 03 (2012-12-29) Huawei Proprietary and Confidential 4-3

4.3 UE Capability Decision

4.4 Resource Limitation Decision

4.5 Uplink and Downlink Admission

4.5.1 Non-GBR Service Admission

Issue 03 (2012-12-29) Huawei Proprietary and Confidential 4-4

4.5.2 GBR Service Admission

Issue 03 (2012-12-29) Huawei Proprietary and Confidential 4-5

Figure 4-2 Downlink admission process of GBR services

Check on the Number of PRBs Used by GBR Services

Issue 03 (2012-12-29) Huawei Proprietary and Confidential 4-6

Decision on the PRB Usage and Transmit Power

QoS Satisfaction Rate Evaluation

Admission Decision Based on QoS Satisfaction Rates

Issue 03 (2012-12-29) Huawei Proprietary and Confidential 4-7

 For QcixHoThd + CellRacThd.NewCopperServiceOffset > SQCI = x ≥ QcixHoThd +

Issue 03 (2012-12-29) Huawei Proprietary and Confidential 4-8

Procedure for Preempting a GBR Service

Procedure for Preempting a Non-GBR Service

Issue 03 (2012-12-29) Huawei Proprietary and Confidential 4-9

Issue 03 (2012-12-29) Huawei Proprietary and Confidential 4-10

Issue 03 (2012-12-29) Huawei Proprietary and Confidential 5-1

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

5.1 Load Status Decision