Admission and Congestion Control (eRAN18.1 - 01)

eRAN
Admission and Congestion Control

Feature Parameter Description
Issue 01
Date 2022-03-08
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2022. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: https://www.huawei.com
Email: support@huawei.com
Issue 01 (2022-03-08) Copyright © Huawei Technologies Co., Ltd. i

eRAN
Admission and Congestion Control Feature
Parameter Description Contents
Contents
1 Change History.........................................................................................................................1
1.1 eRAN18.1 01 (2022-03-08)..................................................................................................................................................1
1.2 eRAN18.1 Draft A (2021-12-30)........................................................................................................................................ 1
2 About This Document.............................................................................................................3

2.1 General Statements................................................................................................................................................................ 3
2.2 Applicable RAT......................................................................................................................................................................... 3
2.3 Features in This Document.................................................................................................................................................. 3
3 Overview....................................................................................................................................5
4 Admission Control................................................................................................................... 6
4.1 Principles.................................................................................................................................................................................... 6
4.1.1 UE Admission Procedure................................................................................................................................................... 6
4.1.2 Service Admission Procedure........................................................................................................................................... 9
4.1.2.1 Non-GBR Service Admission.......................................................................................................................................11
4.1.2.2 GBR Service Admission................................................................................................................................................. 11
4.1.3 Redirection........................................................................................................................................................................... 19
4.2 Network Analysis.................................................................................................................................................................. 21
4.2.1 Benefits................................................................................................................................................................................. 21
4.2.2 Impacts.................................................................................................................................................................................. 21
4.3 Requirements......................................................................................................................................................................... 21
4.3.1 Licenses................................................................................................................................................................................. 22
4.3.2 Software................................................................................................................................................................................22
4.3.3 Hardware.............................................................................................................................................................................. 22
4.3.4 Networking.......................................................................................................................................................................... 22
4.3.5 Others.................................................................................................................................................................................... 22
4.4 Operation and Maintenance............................................................................................................................................. 23
4.4.1 Data Configuration........................................................................................................................................................... 23
4.4.1.1 Data Preparation............................................................................................................................................................ 23
4.4.1.2 Using MML Commands............................................................................................................................................... 25
4.4.1.3 Using the MAE-Deployment...................................................................................................................................... 26
4.4.2 Activation Verification..................................................................................................................................................... 26
4.4.3 Network Monitoring......................................................................................................................................................... 26
5 Enhanced Admission Control.............................................................................................. 29
Issue 01 (2022-03-08) Copyright © Huawei Technologies Co., Ltd. ii

eRAN
5.1 Principles.................................................................................................................................................................................. 29
5.1.1 UE Preemption................................................................................................................................................................... 29
5.1.2 Service Preemption........................................................................................................................................................... 32
5.2.1 Benefits................................................................................................................................................................................. 34
5.2.2 Impacts.................................................................................................................................................................................. 34
5.3 Requirements......................................................................................................................................................................... 35
5.3.1 Licenses................................................................................................................................................................................. 35
5.3.2 Software................................................................................................................................................................................35
5.3.3 Hardware.............................................................................................................................................................................. 36
5.3.4 Networking.......................................................................................................................................................................... 36
5.3.5 Others.................................................................................................................................................................................... 36
6 Congestion Control............................................................................................................... 44
6.1 Principles.................................................................................................................................................................................. 44
6.1.1 Congestion Control over GBR Services.......................................................................................................................44
6.1.1.1 Load Status Evaluation................................................................................................................................................ 45
6.1.1.2 Congestion Handling.................................................................................................................................................... 45
6.1.2 Congestion Control over Non-GBR Services.............................................................................................................46
6.1.2.1 Load Status Evaluation................................................................................................................................................ 46
6.1.2.2 Decrease in Priorities for Scheduling Cell Edge UEs.......................................................................................... 47
6.2.1 Benefits................................................................................................................................................................................. 47
6.2.2 Impacts.................................................................................................................................................................................. 47
6.3 Requirements......................................................................................................................................................................... 47
6.3.1 Licenses................................................................................................................................................................................. 48
6.3.2 Software................................................................................................................................................................................48
6.3.3 Hardware.............................................................................................................................................................................. 48
6.3.4 Networking.......................................................................................................................................................................... 48
6.3.5 Others.................................................................................................................................................................................... 48
Issue 01 (2022-03-08) Copyright © Huawei Technologies Co., Ltd. iii

eRAN
7 Parameters.............................................................................................................................. 53
8 Counters.................................................................................................................................. 54
9 Reference Documents...........................................................................................................55
Issue 01 (2022-03-08) Copyright © Huawei Technologies Co., Ltd. iv

eRAN
Parameter Description 1 Change History
1 Change History
This chapter describes changes not included in the "Parameters", "Counters",

"Glossary", and "Reference Documents" chapters. These changes include:
● Technical changes
Changes in functions and their corresponding parameters
● Editorial changes
Improvements or revisions to the documentation
1.1 eRAN18.1 01 (2022-03-08)

This issue includes the following changes.
Technical Changes
None
Editorial Changes
Revised descriptions in this document.
1.2 eRAN18.1 Draft A (2021-12-30)

This issue introduces the following changes to eRAN17.1 03 (2021-06-26).
Issue 01 (2022-03-08) Copyright © Huawei Technologies Co., Ltd. 1

eRAN
Parameter Description 1 Change History
Technical Changes
Change Parameter RAT Base Station
Description Change Model
Added an impact None FDD ● 3900 and 5900

relationship series base
between stations
enhanced ● DBS3900
admission control LampSite and
and Next DBS5900
Generation eCall LampSite
over LTE. For
details, see 5.2.2
Impacts.
Editorial Changes
Revised descriptions in this document.

eRAN
Parameter Description 2 About This Document
2 About This Document
2.1 General Statements

Purpose
This document is intended to acquaint readers with:
● The technical principles of features and their related parameters

● The scenarios where these features are used, the benefits they provide, and
the impact they have on networks and functions
● Requirements of the operating environment that must be met before feature
activation
● Parameter configuration required for feature activation, verification of feature
activation, and monitoring of feature performance
NOTE
This document only provides guidance for feature activation. Feature deployment and
feature gains depend on the specifics of the network scenario where the feature is
deployed. To achieve optimal gains, contact Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in this
document apply only to the corresponding software release. For future software
releases, refer to the corresponding updated product documentation.
2.2 Applicable RAT

This document applies to FDD.
2.3 Features in This Document

This document describes the following FDD features.

eRAN
Parameter Description 2 About This Document
Feature ID Feature Name Chapter/Section
LBFD-002023 Admission Control 4 Admission Control
LOFD-001029 Enhanced Admission 5 Enhanced Admission

Control Control
LOFD-00102901 Radio and

Transmission Resource
Pre-Emption
LBFD-002024 Congestion Control 6 Congestion Control

eRAN
Parameter Description 3 Overview
3 Overview
Admission and congestion control consists of admission control and congestion

control.
● Admission control involves UE admission and service admission.
– The eNodeB admits UEs based on the maximum permissible number of
UEs to ensure that the number of admitted UEs does not exceed the
system specifications.
– The eNodeB admits services based on the system resource load and QoS
satisfaction rates to ensure the QoS satisfaction rates of admitted UEs.
● Congestion control is a process in which the eNodeB controls system load to
ensure a high overall QoS satisfaction rate and stable system operation.
NOTE
Admission control consists of transport-resource-based and radio-resource-based admission

control. This document describes radio-resource-based admission control. For details about
transport-resource-based admission control, see Transmission Resource Management.
Enhanced admission control consists of radio resource preemption and transport resource
preemption. This document describes radio resource preemption including user-number-
based and service-based radio resource preemption. For details about transport resource
preemption, see Transmission Resource Management.

eRAN
Parameter Description 4 Admission Control
4 Admission Control
4.1 Principles
4.1.1 UE Admission Procedure

UE admission takes effect by default and is not controlled by switches.
When a new UE attempts to access a network, a UE admission procedure starts.
UEs can be classified into the following types:
● Privileged UEs: include high-priority UEs (with a "highPriorityAccess" cause
value in an RRC connection establishment request) and emergency UEs. For
the definition of emergency UE, see Emergency Call. The
CellRacThd.AcReservedUserNumber parameter specifies the number of UEs
reserved for privileged UEs.
● UEs involved in RRC connection reestablishment and necessary incoming
handovers. For details about necessary handovers, see Mobility Management
in Connected Mode. The CellRacThd.HoReservedUeNumber parameter
specifies the number of UEs reserved for such type of UEs.
● Common UEs
Figure 4-1 shows the UE admission procedure.

eRAN
Figure 4-1 UE admission procedure
The UE admission procedure is as follows:
1. The base station checks whether the CPU resources are limited. If the CPU
resources are limited, the base station rejects the access request. For details
about how to check whether CPU resources are limited, see Flow Control.

eRAN
2. The base station checks whether the sounding reference signal (SRS)
resources are successfully allocated. For details about the SRS resource
allocation principle, see Physical Channel Resource Management. This step
differs between the LBBPc and other types of BBPs.
In FDD:
– If the LBBPc is configured, the base station performs this step as follows:
▪ When SRS resources are configured for the cell, the cell supports
uplink timing measurement using only the SRS. Therefore, if SRS
resource allocation fails, the uplink timing of the UE may be
inaccurate and the eNodeB rejects the access request.
▪ When the SRS resources are not configured for the cell, the cell
supports uplink timing measurement using the demodulation
reference signal (DMRS). The eNodeB still allows UE access.
– Other types of BBPs support uplink timing measurement using the DMRS.
The uplink timing of the UE is accurate even if SRS resource allocation
fails. Therefore, the eNodeB still allows UE access.
3. The base station checks whether the PUCCH resources are successfully
allocated. If PUCCH resource allocation fails, the base station rejects the
access request. For details about the PUCCH resource allocation principle, see
Physical Channel Resource Management.
4. The eNodeB checks whether the number of UEs is limited. When one of the
following conditions is met, the eNodeB determines that the number of UEs is
limited and the admission of new UEs fails.
– Privileged UEs:
▪ The number of UEs in a cell has reached

min(CellRacThd.AcUserNumber, maximum permissible number of
UEs that can access the cell due to the limitation of hardware
capabilities).
▪ The number of UEs served by a board that serves the cell has
reached its maximum permissible number due to the limitation of
hardware capabilities.
▪ The CellRacThd.AcReservedUserNumber parameter is set to 0 and

the number of UEs served by the eNodeB has reached the licensed
number of UEs served by the eNodeB.
Note: If this parameter is set to a non-zero value, the admission is
not limited by the licensed number of UEs.
– UEs involved in RRC connection reestablishment and necessary incoming
handovers:

capabilities) minus CellRacThd.AcReservedUserNumber.
hardware capabilities minus the product of

eRAN
CellRacThd.AcReservedUserNumber and the number of cells set up

on the board.
▪ The number of UEs served by the eNodeB has reached the licensed
– Common UEs

capabilities) minus the sum of CellRacThd.AcReservedUserNumber
and CellRacThd.HoReservedUeNumber.
hardware capabilities minus the product of the number of cells set
up on the board and the sum of
CellRacThd.AcReservedUserNumber and
CellRacThd.HoReservedUeNumber.
▪ The number of UEs served by the eNodeB has reached the licensed
5. If the UE's admission fails, the UE may initiate a UE preemption procedure.
For details, see 5.1.1 UE Preemption.
NOTE
The number of emergency UEs that can be admitted is only limited by the UE number
specification rather than the licensed UE number so that emergency UEs can preferentially
be admitted.
In the RAN sharing scenario, the licensed number of UEs varies depending on the operators.
As a result, the eNodeB temporarily allows UE access to obtain the PLMN ID when
determining whether the licensed number of UEs is limited. If the licensed number of UEs is
limited and the preemption based on the number of UEs fails, the eNodeB rejects the initial
context setup request of the temporarily accessed UE and releases the UE.
4.1.2 Service Admission Procedure

Figure 4-2 shows the service admission procedure.

eRAN
Figure 4-2 Service admission procedure
The EmcAdmitCongSwitch option of the CellAlgoSwitch.RacAlgoSwitch

parameter takes effect only when both the mission-critical push-to-talk (MCPTT)

eRAN
QoS management and congestion control for public safety are enabled. For details
about MCPTT QoS management and congestion control for public safety, see PTT.
● If the option is selected, the eNodeB does not perform special processing of
emergency calls. The eNodeB performs admission control over emergency
calls based on QoS satisfaction rates, and services with higher ARP priorities
than emergency calls can preempt emergency calls.
● If the option is deselected, emergency calls can be admitted directly and
cannot be preempted. For the definition of emergency call, see Emergency
Call.
This section describes the situation where the EmcAdmitCongSwitch option is
deselected.
4.1.2.1 Non-GBR Service Admission

Non-GBR service admission takes effect by default and is not controlled by
switches. Its procedure is as follows:
● If SRS or PUCCH resources fail to be allocated, service admission is rejected.
● If both the SRS and PUCCH resources are allocated successfully, the services
are directly admitted. The admission is neither affected by cell congestion nor
subject to QoS satisfaction.
NOTE
In FDD, if the LBBPc is installed and SRS resources are configured for a cell, the eNodeB
performs SRS resource allocation.
4.1.2.2 GBR Service Admission

GBR service admission is enabled if the DlSwitch and UlSwitch options of the
CellAlgoSwitch.RacAlgoSwitch parameter are selected.
For FDD, GBR services refer to services of QCIs 1 to 4, 65, and 66. For details about
admission of QCI-65 and QCI-66 services, see PTT.
To ensure QoS, the procedure for GBR service admission is as follows:
● If SRS or PUCCH resources fail to be allocated, service admission is rejected.
● If both the SRS and PUCCH resources are allocated successfully, emergency
call services are directly successfully admitted. The cell congestion check is
required for non-emergency call services. If the cell is not congested, the
eNodeB determines whether to admit such services based on the QoS
satisfaction rate.
NOTE
In FDD, if the LBBPc is installed and SRS resources are configured for a cell, the eNodeB
performs SRS resource allocation.
In a cell, the QoS satisfaction rate of GBR services indicates whether the QoS
requirements of admitted GBR services are fulfilled. This QoS satisfaction rate is
used for evaluating cell load and making admission decisions.
Figure 4-3 and Figure 4-4 show the downlink and uplink admission procedures
for GBR services based on QoS satisfaction rates, respectively.

eRAN
Figure 4-3 Downlink admission procedure for GBR services

eRAN
Figure 4-4 Uplink admission procedure for GBR services
● If the VOLTE_UNCONDITIONAL_ADMISSION option of the

CellRacThd.AdmissionControlPolicy parameter is selected, VoLTE services
can be admitted unconditionally.

eRAN
● If the MCPTT_UNCONDITIONAL_ADMISSION option of the

CellRacThd.AdmissionControlPolicy parameter is selected, MCPTT services
(QCI-65 and QCI-66 services) can be admitted unconditionally.
QoS Satisfaction Rate Evaluation

QCIs reflect QoS priorities, and QoS parameter settings vary with QCIs. For details,
see section 6.1.7 "Standardized QoS characteristics" in 3GPP TS 23.203 v10.7.0.
This protocol describes the characteristics of different services and the standards
for evaluating QoS satisfaction rates of these services in the LTE QoS mechanism.
If a UE does not support QoS parameter settings, the eNodeB modifies QoS
parameters based on the maximum UE capabilities.
When the UE initiates a new service request, the mobility management entity
(MME) sends the eNodeB an INITIAL CONTEXT SETUP REQUEST message over the
S1 interface containing the UE capability information and QoS parameter settings.
Based on the QoS parameters and UE capability, the eNodeB checks whether the
UE supports QoS parameter settings of a specific QCI. For details about UE
capabilities, see section 4.1 "ue-Category" in 3GPP TS 36.306 v10.6.0. The major
concern with the capability of a UE is whether the sum of GBRs of various services
exceeds the maximum UE capability, which is indicated by the maximum transport
block size supported by the UE. For details, see section 8.3.1 "Initial Context Setup"
in 3GPP TS 36.413 v10.6.0.
In the downlink, QoS satisfaction rates are evaluated based on the logical
channels corresponding to the QCIs.
In the uplink, however, QoS satisfaction rates are evaluated based on the logical
channel groups corresponding to the QCIs. The reason is that the eNodeB cannot
evaluate the amount of buffered data to be transmitted through each logical
channel on the UE side. This evaluation method helps reduce signaling overhead
and the number of buffer status reports (BSRs). A logical channel group is defined
as a group of radio bearers with similar QoS requirements. For details about
logical channel groups, see section 5.4.5 "Buffer Status Reporting" in 3GPP TS
36.321 v10.5.0.
The uplink and downlink QoS satisfaction rates of GBR services are calculated
based on QCIs, and a specific set of admission thresholds are set for each QCI.
That is, the differentiated admission by QCI is achieved by setting a specific set of
admission thresholds for each QCI.
Downlink QoS Satisfaction Rate Evaluation

For VoLTE services with a QCI of 1, the downlink QoS satisfaction rate is
represented by the ratio of the sum of the downlink QoS satisfaction rates of all
VoLTE services in a cell to the total number of VoLTE services in a cell.
The downlink QoS satisfaction rate of any VoLTE service is calculated by using the
following formula:
A VoLTE packet is satisfactory if it is buffered for a time less than 50 ms.

eRAN
For GBR services with QCI x (x ranges from 2 to 4), the downlink QoS satisfaction
rate is calculated by using the following formula:
For examples of the mapping between QCIs and service types, see section 6.1.7
"Standardized QoS characteristics" in 3GPP TS 23.203 v11.6.0. Huawei adheres to
the protocol to implement the mapping. For example, QCI 1 maps VoLTE services.
Uplink QoS Satisfaction Rate Evaluation

For VoLTE services with a QCI of 1, the uplink QoS satisfaction rate is represented
by the ratio of the sum of the uplink QoS satisfaction rates of all VoLTE services in
a cell to the total number of VoLTE services in a cell.
The uplink QoS satisfaction rate of any VoLTE service is calculated by using the
following formula:
The method of calculating the uplink QoS satisfaction rate of VoLTE services is
different from that of calculating the downlink QoS satisfaction rate of VoLTE
services. The difference is that the eNodeB cannot obtain the uplink buffering time
of VoLTE packets from the UE in the uplink. If an uplink VoLTE packet is buffered
on the UE for a time longer than the length of the timer for discarding Packet
Data Convergence Protocol (PDCP) PDUs, the VoLTE packet is discarded.
Therefore, the percentage of PDCP PDUs successfully received by the eNodeB is
used to determine whether there are timeout VoIP packets. For details, see section
5.4 "PDCP discard" in 3GPP 36.323 v8.6.0.
For uplink GBR services with a QCI ranging from 2 to 4, the uplink QoS
satisfaction rate is evaluated for each logical channel group. The QoS satisfaction
rate is represented by the ratio of the transmitted data to the total amount of
data to be transmitted. A higher ratio indicates a higher QoS satisfaction rate. The
uplink QoS satisfaction rate of GBR services is calculated by using the following
formula:
QCIs 1 to 4 can be mapped to logical channel groups. For details about the
mapping, see Scheduling. For example, if QCIs 2 to 4 are mapped to logical
channel group 2, the uplink QoS satisfaction rates for services with QCIs 2 to 4 are
represented by the satisfaction rate for logical channel group 2.

eRAN
Admission Decision-Making Based on QoS Satisfaction Rates

The admission threshold for handovers is looser than that for new services. The
CellQciPara.HandoverAdmissionThreshold parameter specifies the QCI-specific
admission threshold for handover services. Service differentiation can be achieved
by setting different admission offsets for new gold-, silver-, bronze-, and iron-level
services, based on the mapping between ARP values and service priorities. The
admission offsets are indicated by the following parameters.
● CellRacThd.NewGoldServiceOffset
● CellRacThd.NewSilverServiceOffset
● CellRacThd.NewCopperServiceOffset
● CellRacThd.NewIronServiceOffset
These offset values apply to both the uplink and downlink.
The eNodeB categorizes services based on their ARP values. The ARP values are
mapped to four service levels: gold, silver, bronze, and iron, as described in Table
4-1. The mapping can be adjusted by setting the following parameters:
● ARP threshold for gold-level services: CellRacThd.GoldServiceArpThd
● ARP threshold for silver-level services: CellRacThd.SilverServiceArpThd
● ARP threshold for bronze-level services: CellRacThd.CopperServiceArpThld
A service is defined as an iron-level service if its ARP value is out of the range
defined by the preceding parameters. A larger ARP value indicates a lower priority.
Table 4-1 Mapping between ARP values and service priorities

ARP Value Service
Priority
[1, CellRacThd.GoldServiceArpThd] Gold
(CellRacThd.GoldServiceArpThd, CellRacThd.SilverServiceArpThd] Silver
(CellRacThd.SilverServiceArpThd, Bronze
CellRacThd.CopperServiceArpThld]
(CellRacThd.CopperServiceArpThld, 15] Iron
For details about ARPs, see section 4.7.3 "Bearer level QoS parameters" in 3GPP TS
23.401 v10.8.0.
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:
● Admission thresholds for handover services
– The sum of CellQciPara.HandoverAdmissionThreshold and
CellRacThd.LoadHoAdmitOffset specifies the admission threshold for
handover services due to load causes.
– The CellQciPara.HandoverAdmissionThreshold parameter specifies the
admission threshold for handover services due to other causes.

eRAN
● Admission thresholds for new services

CellRacThd.NewGoldServiceOffset specifies the admission threshold for
new gold-level services.
CellRacThd.NewSilverServiceOffset specifies the admission threshold
for new silver-level services.
CellRacThd.NewCopperServiceOffset specifies the admission threshold
for new bronze-level services.
CellRacThd.NewIronServiceOffset specifies the admission threshold for
new iron-level services.
If voice service offloading is enabled (the VoIPOffloadSwitch option of the

CellAlgoSwitch.MlbAlgoSwitch parameter is selected), the voice service
admission threshold is the preceding admission threshold minus
CellRacThd.VoipOverAdmitOffset. In addition, service preemption is prohibited if
admission of handover services due to load causes fails. For details about voice
service offloading, see Intra-RAT Mobility Load Balancing.
For QCIs 1 to 4, the relationships between these thresholds are as follows:
● CellQciPara.HandoverAdmissionThreshold ≤
CellQciPara.HandoverAdmissionThreshold +
CellRacThd.NewGoldServiceOffset
● CellQciPara.HandoverAdmissionThreshold +
CellRacThd.NewGoldServiceOffset ≤
CellRacThd.NewSilverServiceOffset
CellRacThd.NewSilverServiceOffset ≤
CellRacThd.NewCopperServiceOffset
CellRacThd.NewCopperServiceOffset ≤
CellRacThd.NewIronServiceOffset
Downlink admission control rules are as follows:
● If the QoS satisfaction rate of services with each QCI is greater than or equal
to the admission threshold of non-load-based handovers with the
corresponding QCI:
– Non-load-based handovers with all QCIs can be admitted.
– The new gold-, silver-, bronze, and iron-level services with each QCI are
checked. If the QoS satisfaction rate of a certain level of services with a
QCI is greater than or equal to the corresponding admission threshold,
the services can be admitted.
– Load-based handovers for services with each QCI are checked. If the QoS
satisfaction rate of the services is greater than or equal to the

eRAN
corresponding admission threshold, the handovers for the services can be

admitted.
● If the QoS satisfaction rate of GBR services with a certain QCI is less than the
admission threshold of non-load-based handovers, then the non-load-based
handovers of the services with this QCI cannot be admitted, and neither the
new GBR services of all QCIs nor load-based handovers for GBR services of all
QCIs can be admitted.
NOTE
The QCIs of GBR services include 1 to 4, 65, and 66. The following takes the admission
of new QCI-65 services and load-based incoming handovers for QCI-65 services as an
example. During the admission, whether the QoS satisfaction rates of other GBR
services with QCIs 1 to 4, and 66 are higher than the corresponding admission
thresholds for non-load-based handovers is checked. If not, new QCI-65 services and
load-based incoming handovers for QCI-65 services cannot be admitted. This
mechanism ensures that non-load-based handovers take precedence over new services
and load-based incoming handovers during GBR service admission.
Uplink admission control rules are similar to those in the downlink. The difference
is that the eNodeB evaluates the QoS satisfaction rates of logical channel groups
when admitting GBR services in the uplink. For details, see Uplink QoS
Satisfaction Rate Evaluation.
System Resource Usage Evaluation

The eNodeB evaluates system resource usage as follows:
● When the CellRacThd.CceUsageThd parameter is set to 0:
– The eNodeB regards that the downlink system resource usage is high by
default.
– The eNodeB determines that the uplink system resource usage is high if
the uplink GBR PRB usage is high or the wait time for uplink scheduling
for VoLTE services is long.
● When the CellRacThd.CceUsageThd parameter is not set to 0:
– The eNodeB determines that the downlink system resource usage is high
if the downlink GBR PRB usage or GBR CCE usage is high.
– The eNodeB determines that the uplink system resource usage is high if
the uplink GBR PRB usage or GBR CCE usage is high.
The downlink and uplink GBR PRB usages, wait time for uplink scheduling for
VoLTE services, and GBR CCE usage are calculated as follows:
● Downlink GBR PRB usage
● Uplink GBR PRB usage

eRAN
After performing filtering on the obtained downlink or uplink GBR PRB usage,
the eNodeB compares the uplink or downlink PRB usage with the
CellRacThd.UlRbHighThd and CellRacThd.UlRbLowThd parameter values,
and then determines whether the downlink or uplink PRB usage is high.
● Waiting time for uplink scheduling of VoLTE services
The wait time starts when a VoLTE service requests uplink resources and stops
when the VoLTE service is allocated uplink resources. eNodeBs regard wait
time longer than 100 ms to be too long.
● GBR CCE usage
After performing filtering on the GBR CCE usage, the eNodeB compares the
GBR CCE usage with both the CellRacThd.CceUsageThd parameter value and
the value of CellRacThd.CceUsageThd minus 10%, and then determines
whether the CCE usage is high.
When the CCE usage is greater than CellRacThd.CceUsageThd, the eNodeB
determines that the CCE usage is high.
When the CCE usage is less than CellRacThd.CceUsageThd minus 10%, the
eNodeB determines that the CCE usage is low.
When the CCE usage is between CellRacThd.CceUsageThd and
CellRacThd.CceUsageThd minus 10%, the eNodeB determines that the CCE
usage is in the same state as that one second before the very moment when
the CCE usage increases or decreases to a value in this range.
4.1.3 Redirection
Redirection is a process where the eNodeB sends a UE an RRCConnectionRelease
message to release RRC connection. This message contains the target frequency
that the UE uses to re-access the network. The
ENodeBAlgoSwitch.RedirectSwitch parameter controls the redirection function
as follows:
● The LoadBasedSwitch option of this parameter specifies whether to enable
load-based redirection.
● The LoadRedirectFreqOptSwitch option controls the policy for selecting a
target frequency for redirection.
Figure 4-5 shows the redirection process.

eRAN
Figure 4-5 Redirection process
Descriptions of the redirection process shown in Figure 4-5 are as follows:
1. If the EPC assigns a UE the SPID when the UE accesses the network, the
eNodeB selects a target frequency for redirection based on the setting of the
LoadRedirectFreqOptSwitch option and the RATs and frequencies supported
by the UE among the frequencies corresponding to the SPID. For details about
SPID, see Flexible User Steering.
2. If the EPC does not assign the UE the SPID or frequency priorities are not set
in the SPID configuration for the UE, the operator-specific dedicated priority is
used. That is:
– The eNodeB selects a target frequency for redirection based on the
setting of the LoadRedirectFreqOptSwitch option among candidate
frequencies whose cell reselection priorities are specified by the Cell
reselection priority parameter in the MOs EutranNFreqRanShare,
UtranRanShare, and GeranRanShare.

eRAN
– Alternatively, the eNodeB selects a target frequency for redirection based

on the setting of the LoadRedirectFreqOptSwitch option among
candidate frequencies whose dedicated cell-reselection priorities are
configured in MOs EutranNFreqSCellOp, UtranNFreqSCellOp,
GeranNFGroupSCellOp, and Cdma2000BcSCellOp.
3. If the EPC does not assign the UE the SPID or frequency priorities are not set
in the SPID configuration for the UE, and if operator-specific dedicated
priorities are not specified, the common cell-reselection priorities are used. In
this case, the eNodeB selects a target frequency for redirection based on the
setting of the LoadRedirectFreqOptSwitch option and the RATs and
frequencies supported by the UE among the candidate frequencies whose cell
reselection common priorities are configured in MOs EutranInterNFreq,
UtranNFreq, and GeranNfreqGroup.
NOTE
If the admission fails for a UE requesting an incoming handover, redirection is supported for
the UE.
4.2 Network Analysis
4.2.1 Benefits
Admission control guarantees the QoS of admitted UEs by rejecting admission
requests of new UEs and services to maximize system capacity.
4.2.2 Impacts
Network Impacts
If network congestion results in limited system capacity, the implementation of
admission control algorithm decreases the access success rate and handover
success rate.
For admission control based on QoS satisfaction rates, if the admission threshold
is set to a smaller value, GBR services are easier to be admitted and the admission
success rate of GBR services increases. However, the service quality of admitted
GBR services becomes poorer.
When congestion occurs, the congestion control algorithm informs the admission
control algorithm. Then, the admission control algorithm starts to reject access
requests of new services.
Function Impacts
None
4.3 Requirements

eRAN
4.3.1 Licenses
None
4.3.2 Software
Prerequisite Functions
None
Mutually Exclusive Functions

None
4.3.3 Hardware
Base Station Models
FDD:
● 3900 and 5900 series base stations
● DBS3900 LampSite and DBS5900 LampSite
● BTS3912E
● BTS3911E
● BTS3203E
● BTS3202E
NOTE
The BTS3912E does not support unconditional admission of MCPTT voice services.
The BTS3911E does not support unconditional admission of MCPTT voice services.
The BTS3203E does not support UE number resource reservation for UEs involved in
incoming necessary handovers or unconditional admission of voice services.
The BTS3202E does not support UE number resource reservation for UEs involved in
incoming necessary handovers or unconditional admission of voice services.
Boards
No requirements
RF Modules
No requirements
4.3.4 Networking
None
4.3.5 Others
In FDD, there are no requirements.

eRAN
4.4 Operation and Maintenance
4.4.1 Data Configuration
4.4.1.1 Data Preparation
UE Admission
This function is enabled by default and does not need activation. Table 4-2
describes the parameters used for function optimization.
Table 4-2 Parameters used for optimization
Parameter Parameter ID Setting Notes

Name
Admission CellRacThd.AcUserNumber None

Control User
Number
Admission CellRacThd.AcReservedUserNum None

Control ber
Reserved User
Number
UE Number CellRacThd.HoReservedUeNum- None

Reserved for ber
Handover
QoS-Satisfaction-Rate-based Admission Control

Table 4-3 and Table 4-4 describe the parameters used for function activation and
optimization, respectively.
Table 4-3 Parameters used for activation
Parameter Parameter ID Option Setting Notes

Name
RAC algorithm CellAlgoSwitch. DlSwitch and None

switch RacAlgoSwitch UlSwitch
CCE Usage CellRacThd.Cce None The value 80 is

Threshold UsageThd recommended.

eRAN

Name
Gold service CellRacThd.GoldServiceArpThd Use the recommended

arp threshold value.
Silver service CellRacThd.SilverServiceArpThd Use the recommended

arp threshold value.
Copper Service CellRacThd.CopperServiceArpThl Use the recommended

ARP Threshold d value.
Gold new CellRacThd.NewGoldServiceOff- Use the recommended

service set value.
admission
threshold offset
Silver new CellRacThd.NewSilverServiceOff- Use the recommended

service set value.
admission
threshold offset
Bronze new CellRacThd.NewCopperServiceOf Use the recommended

service fset value.
admission
threshold offset
Iron New CellRacThd.NewIronServiceOff- Use the recommended

Service set value.
Admission
Threshold
Offset
Load-based CellRacThd.LoadHoAdmitOffset Use the recommended

Handover value.
Admission
Offset
High RB Usage CellRacThd.UlRbHighThd Use the recommended

Thld value.
Low RB Usage CellRacThd.UlRbLowThd Use the recommended

Thld value.
Handover CellQciPara.HandoverAdmission- Use the recommended

Admission Threshold value.
Threshold
Admission CellRacThd.AdmissionControlPo- Use the recommended

Control Policy licy value.

eRAN
Redirection
Table 4-5 describes the parameters used for function activation. No parameter is
involved in function optimization.

Name
Redirection ENodeBAlgoSwi LoadBasedSwit You are advised to retain

switch tch.RedirectSwi ch the default value.
tch LoadRedirectFr
eqOptSwitch
4.4.1.2 Using MML Commands
Activation Command Examples (FDD)

Before using MML commands, refer to 4.2.2 Impacts and 4.3.2 Software and
complete the parameter configurations for related functions based on the impact,
dependency, and mutually exclusive relationships between the functions, as well
as the actual network scenario.
//Activating QoS-satisfaction-rate-based admission control
MOD CELLALGOSWITCH: LocalCellId=0, RacAlgoSwitch=DlSwitch-1&UlSwitch-1;
MOD CELLRACTHD: LocalCellId=0, CceUsageThd=80;
//Activating redirection
MOD ENODEBALGOSWITCH:RedirectSwitch=LoadBasedSwitch-1&LoadRedirectFreqOptSwitch-1;
Optimization Command Examples

//Optimizing UE admission (when no UE number resources are reserved for privileged UEs)
MOD CELLRACTHD: LocalCellId=0, AcReservedUserNumber=0, HoReservedUeNumber=0,
AcUserNumber=65535;
//Optimizing QoS-satisfaction-rate-based admission control

MOD CELLRACTHD: LocalCellId=0, CceUsageThd=80;
MOD CELLRACTHD: LocalCellId=0, GoldServiceArpThd=5, SilverServiceArpThd=10, NewGoldServiceOffset=5,
NewSilverServiceOffset=5, NewCopperServiceOffset=5, UlRbHighThd=95, UlRbLowThd=90,
LoadHoAdmitOffset=0, CopperServiceArpThld=15, NewIronServiceOffset=5,
AdmissionControlPolicy=VOLTE_UNCONDITIONAL_ADMISSION-0;
MOD CELLQCIPARA: LocalCellId=0, Qci=2, HandoverAdmissionThreshold=90;
Deactivation Command Examples (FDD)

The following provides only deactivation command examples. You can determine
whether to restore the settings of other parameters based on actual network
conditions.
//Deactivating UE-number-reservation-based admission control of privileged UEs
MOD CELLRACTHD: LocalCellId=0, AcReservedUserNumber=0;
//Deactivating QoS-satisfaction-rate-based admission control

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

eRAN
4.4.1.3 Using the MAE-Deployment

For detailed operations, see Feature Configuration Using the MAE-Deployment.
4.4.2 Activation Verification

Check whether QoS-satisfaction-rate-based admission control has taken effect by
performing the following steps:
Step 1 On the MAE-Access, start S1 interface tracing and start monitoring on the
following items: Satisfaction of Service Monitoring and Usage of RB
Monitoring.
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. Increase the traffic volume of GBR services on these UEs. Move
some UEs towards the cell edge until the cell is congested, as indicated by
Congestion State in the monitoring results.
Step 3 Initiate new GBR services with the same QCI. QoS-satisfaction-rate-based
admission control rejects these new GBR service requests.
Step 4 Check the S1AP_ERAB_SETUP_REQ and S1AP_ERAB_SETUP_RSP messages in the

S1 interface tracing result. If the cause value for E-RAB setup failures is
"radioNetwork: radio-resources-not-available" in the S1AP_ERAB_SETUP_RSP
messages, as shown in Figure 4-6, or if the number of services does not increase
with the S1AP_ERAB_SETUP_REQ messages, the new GBR service requests have
been rejected.
Figure 4-6 S1AP_ERAB_SETUP_RSP message that indicates failed admission based

on satisfaction rates
----End
4.4.3 Network Monitoring

Admission control involves RRC connection management and bearer management.
If the licensed UE number, UE number specification, or PUCCH resources is limited,

the eNodeB does not allow new UEs to access the cell or UEs to be handed over
to the cell, and the RRC connections for these UEs fail to be set up. The RRC
congestion rate increases.
If resources in the cell are limited the eNodeB may reject the access requests of
new bearers and incoming handover bearers, and E-RABs fail to be set up. The E-
RAB congestion rate increases. Table 4-6 lists the methods for calculating the
measurement indicators.

eRAN
Table 4-6 Congestion rate calculation
Measurement Formula
Indicator
RRC congestion 1 – (L.RRC.ConnReq.Succ –

rate L.Cell.UserSpec.PrepEmp.PrepAtt.Num –
L.Cell.UserLic.Limit.Num)/L.RRC.ConnReq.Msg
E-RAB congestion L.E-RAB.FailEst.NoRadioRes/L.E-RAB.AttEst

rate
NOTE
Causes of RRC connection setup failures can be viewed from the counters in the "RRC Setup
Failure Measurement" function subset.
Causes of E-RAB setup failures can be viewed from the counters in the "E-RAB Setup Failure
Measurement" function subset.
The number of times the number of UEs to be admitted is limited by the licensed number
of UEs for a specific operator can be viewed from the L.Cell.UserLic.Limit.Num.PLMN
counter.
E-RAB setup failures caused by admission rejection based on QoS satisfaction rates
can be monitored using the counters listed in Table 4-7.
Table 4-7 Counters related to E-RAB setup failures
Counter ID Counter Name
1526729955 L.E-RAB.FailEst.NoRadioRes.DLSatis
1526729956 L.E-RAB.FailEst.NoRadioRes.ULSatis
1526729968 L.E-RAB.FailEst.NoRadioRes.DLSatis.VoIP
1526729969 L.E-RAB.FailEst.NoRadioRes.ULSatis.VoIP
1526736694 L.E-RAB.FailEst.NoRadioRes.DLSatis.QCI2
1526736697 L.E-RAB.FailEst.NoRadioRes.ULSatis.QCI2

eRAN
Counter ID Counter Name
1526748818 L.E-
RAB.FailEst.NoRadioRes.CCELimited.DLSatis.VoIP
1526748817 L.E-
RAB.FailEst.NoRadioRes.CCELimited.ULSatis.VoIP
1526748820 L.E-
RAB.FailEst.NoRadioRes.CCELimited.DLSatis.QCI6
5
1526748819 L.E-
RAB.FailEst.NoRadioRes.CCELimited.ULSatis.QCI6
5
1526748822 L.E-
RAB.FailEst.NoRadioRes.CCELimited.DLSatis.QCI6
6
1526748821 L.E-
RAB.FailEst.NoRadioRes.CCELimited.ULSatis.QCI6
6

eRAN
Parameter Description 5 Enhanced Admission Control
5 Enhanced Admission Control
5.1 Principles
5.1.1 UE Preemption
SRS or PUCCH Resource Allocation Failure
When a new emergency UE fails to be allocated SRS or PUCCH resources and the
CellRacThd.AcReservedUserNumber parameter is set to 0, the UE preempts the
resources of a non-emergency UE in the synchronized state and with the lowest
ARP priority in the same cell. If the preempted UE has multiple services with
different ARP priorities, the highest ARP priority is used as the ARP priority of the
UE.
UE Number Limitation
When the UE number specification of the system is limited, there are UEs that
treat a local cell as their SCell, and the local cell and the UEs' PCells are intra-
eNodeB cells, a UE for which the admission procedure fails in the local cell is
allowed to preempt UE number specification resources occupied by the UEs' SCell.
This function takes effect by default and is not controlled by switches.
When the UE number specification of the system is limited and no UE in the local
cell treats the local cell as their SCell, or the licensed number of UEs is limited, the
eNodeB performs as follows:
When a UE with a high ARP priority attempts to access the network and the
eNodeB rejects the access attempt due to limitation on the number of UEs:
● If the IntraOpUeNumPreemptSwitch option of the
ENodeBAlgoSwitch.UeNumPreemptSwitch parameter is selected, this UE
preempts the resources of non-emergency UEs with low ARP priorities served
by the same operator. The preemption is not allowed if this option is
deselected.
● If the InterOpUeNumPreemptSwitch option of the
ENodeBAlgoSwitch.UeNumPreemptSwitch parameter is selected, this UE

eRAN
preempts the resources of non-emergency UEs with low ARP priorities served
by different operators. The preemption is not allowed if this option is
deselected.
NOTE
For details about SCell and PCell, see Carrier Aggregation.
In the UE-number-based preemption, the eNodeB sets up a temporary RRC

connection for any UE requesting access to the eNodeB in order to obtain the UE's
ARP attributes. Based on the ARP attributes, the eNodeB determines whether to
allow the UE's preemption.
● If the preemption fails, the UE immediately releases the temporary RRC

connection.
● If the preemption succeeds, the temporary RRC connection is changed to a
formal one.
The number of temporary RRC connections in a cell depends on the setting of the
UeNumPreemptCapbEnhSwitch option of the
ENodeBAlgoSwitch.UeNumPreemptSwitch parameter.
● When this option is deselected, the number of temporary RRC connections
allowed in a cell is small and is limited by hardware capabilities.
● When this option is selected, the number of temporary RRC connections
allowed in a cell is calculated as follows: Number of temporary RRC
connections due to the limitation of hardware capabilities + [maximum
permissible number of RRC connections in a cell due to the limitation of
hardware capabilities – min(CellRacThd.AcUserNumber, maximum
permissible number of RRC connections in a cell due to the limitation of
hardware capabilities)]
When the number of RRC connections reaches the number of temporary RRC
connections allowed in a cell, new access requests of UEs will be rejected during
RRC connection setup procedures and therefore preemption cannot be triggered.
A low-ARP-priority UE can be preempted when the IE Pre-emption Vulnerability is

set to pre-emptable for ARPs corresponding to all bearers of the UE. Such UEs are
preempted in the following order:
1. Low-ARP-priority UEs in the out-of-synchronization state performing non-GBR

services
2. Low-ARP-priority UEs in the out-of-synchronization state performing GBR
services
3. Low-ARP-priority UEs in the synchronized state performing non-GBR services
4. Low-ARP-priority UEs in the synchronized state performing GBR services
If the preemption succeeds and redirection is enabled, the eNodeB performs a

redirection for the UE whose resource is preempted. If the preemption request is
rejected and redirection is enabled, the eNodeB performs a redirection for the UE
that requests preemption. For details about the redirection procedure, see 4.1.3
Redirection.
The ARP priority of a UE is generally allocated by the EPC. The eNodeB supports
ARP configurations in the following scenarios:

eRAN
● CS fallback (CSFB) UEs

The EPC allocates a low ARP priority for a CSFB UE. When the number of UEs
is limited, such a UE can hardly preempt resources of other low-ARP-priority
UEs and then experiences a preemption failure, resulting in an admission
failure. CSFB UEs can be classified into emergency CSFB UEs and common
CSFB UEs. If the value of the IE CS Fallback Indicator in the INITIAL CONTEXT
SETUP REQUEST message sent from the EPC to the eNodeB is CS Fallback
High Priority, the UE is an emergency CSFB UE; otherwise, the UE is a
common CSFB UE.
To increase the ARP priority for a CSFB UE, the
CSFallBackPolicyCfg.CsfbUserArpCfgSwitch parameter can be set to ON. In
this case, the ARP configurations for the default bearer of the CSFB UE are as
follows:
– Pre-emption Capability
▪ The value of this IE is may trigger pre-emption, indicating that the

UEs can preempt resources of other low-ARP-priority UEs.
– Pre-emption Vulnerability
▪ The value of this IE is not pre-emptable, indicating that resources of

the UEs cannot be preempted by other UEs.
– Priority Level
▪ The value of this IE for emergency CSFB UEs is 1.
▪ The value of this IE for common CSFB UEs can be specified by the
CSFallBackPolicyCfg.NormalCsfbUserArp parameter.
To ensure that common CSFB UEs are capable of preempting UEs when the
number of UEs is limited, it is recommended that common CSFB UEs be
configured with high ARP priorities.
● UEs whose RRCConnectionRequest messages contain the cause value of mo-
Signalling
If the cause value is mo-Signalling in the RRCConnectionRequest message
received from a UE, the eNodeB can configure the ARP priority for the UE.
The CellRacThd.MoSigArpOverride parameter controls this function. If this
parameter is set to a non-zero value, then this function is enabled, and the
eNodeB provides the following ARP configurations for the default bearers of
such UEs:


– Priority Level
▪ If the value of this IE for the default bearer is greater than the
CellRacThd.MoSigArpOverride parameter value, the value of this IE
is changed to the parameter value.

eRAN
● NSA-DC-capable UEs
This function is controlled by the CellRacThd.NsaArpOverride parameter. If
this parameter is set to a non-zero value for a cell with NSA DC enabled, then
this function is enabled, and the eNodeB provides the following ARP
configurations for the default bearers of such UEs:


– Priority Level
▪ If the CellRacThd.NsaArpOverride parameter is set to a value in the

range from 1 to 15 and the value of this IE for the default bearers is
greater than the CellRacThd.NsaArpOverride parameter value, the
value of this IE is changed to the CellRacThd.NsaArpOverride
parameter value.
▪ If the CellRacThd.NsaArpOverride parameter is set to a value in the

range from 16 to 30 and the value of this IE for the default bearers is
greater than the CellRacThd.NsaArpOverride parameter value
minus 15, the value of this IE is changed to the
CellRacThd.NsaArpOverride parameter value minus 15. When the
NSA DC UE initiates preemption, the value of the Pre-emption
Vulnerability IE of other UEs is considered as pre-emptable.
5.1.2 Service Preemption

As illustrated in Figure 4-2, when admission and congestion control over
emergency calls, MCPTT QoS management, and congestion control for public
safety are enabled, emergency calls can be preempted based on the ARP priorities
in the same way as common GBR services. If one of the three functions is disabled,
emergency calls cannot be preempted.
When a new emergency call requests preemption and fails to be allocated SRS or
PUCCH resources, the service preempts the resources of the common UE in the
synchronization state and with the lowest ARP priority in the same cell. If the
common UE has multiple services with different ARP priorities, the highest ARP
priority is used as the ARP priority of the UE.
When a GBR service request with a high ARP priority is rejected because the cell is
congested or the admission based on the QoS satisfaction rates fails, the GBR
service will attempt to preempt GBR services with low ARP priorities to access the
cell. Service preemption can be triggered based on conditions described in Figure
4-3 or Figure 4-4.
Service preemption is enabled by selecting the PreemptionSwitch option of the

CellAlgoSwitch.RacAlgoSwitch parameter.
A service can preempt other services only if its ARP IE Pre-emption Capability is
may trigger pre-emption. If a service is not capable of preemption, it cannot be

eRAN
admitted. If service A is capable of preemption, it can preempt a service B that

meets all of the following conditions:
● Service B is a non-emergency GBR service.
● The value of the ARP IE Pre-emption Vulnerability of service B is pre-
emptable.
● The value of the ARP IE Priority Level of service B is greater than that of
service A.
● Resources allocated to service B ≥ Resources required by service A x
CellRacThd.PreResNeedTuningFactor
Preemption fails if any one of the preceding conditions is not met. If none of the
GBR services of a UE is admitted or preemption for all GBR services of the UE fails,
the UE is redirected if redirection is enabled. For details about the redirection
procedure, see 4.1.3 Redirection.
NOTE
A service whose ARP value is 15 can neither preempt other services nor be preempted by
other services. For details, see section 9.2.1.60 in 3GPP TS 36.413 v10.6.0.
During the preemption procedure, the eNodeB first groups GBR services with low
priorities and then selects services that can be preempted from this group. The
procedure is as follows:
1. The eNodeB groups the GBR services with low priorities.
– The eNodeB first selects releasable GBR services and then groups the
services with the lowest priorities among them. A releasable GBR service
must meet the following conditions:
▪ The value of the ARP IE Pre-emption Vulnerability of the service is

pre-emptable.
▪ The service is not an emergency call.
▪ The GBR service rate is not 0.

– The eNodeB sorts these GBR services based on the following rule: The
service with the largest value of the ARP IE Priority Level has the lowest
priority and ranks first. If two services have the same value of the IE
Priority Level, the service that occupies more PRBs ranks ahead of the
other.
2. The eNodeB selects services to be preempted.
– The eNodeB estimates the number of PRBs required by a preempting
service based on the average spectral efficiency of the cell and the QoS
parameter settings of the service.
– The eNodeB calculates the number of PRBs to be released from the group
of GBR services with low priorities. The calculation stops when the
number of to-be-released PRBs meets the requirements of the
preempting service. The preemption fails if no service can be preempted
or the number of PRBs released from 10 to-be-preempted services does
not meet the requirements of the preempting service.
– If the GBR service to be preempted is the only GBR service on a UE, the
UE can be redirected when redirection is enabled. For details about the
redirection procedure, see 4.1.3 Redirection.

eRAN
5.2.1 Benefits
High-priority UEs preempt resources of low-priority UEs or resources are reserved
for high-priority UEs to ensure experience of high-priority UEs.
High-priority services preempt resources of low-priority services to ensure
experience of high-priority services.
This function is recommended when both of the following conditions are met:
● The CellRacThd.AcUserNumber parameter value for a cell is less than the
maximum number of UEs that the cell supports.
● The maximum CPU usages of the main control board and the BBP are less
than 60%.
If this function is enabled when either of the conditions is not met, the function
still takes effect, but the CPU usage increases.
5.2.2 Impacts
Network Impacts
Preemption increases the access success rate for UEs with high ARP priorities.
However, UEs with low ARP priorities are forcibly released, and their service drop
rate increases. In addition, the air interface signaling overhead increases.
Function Impacts
RAT Function Function Reference Description
Name Switch
FDD CSFB- None Emergency Emergency calls are assigned

based Call the highest priority. If the
emergenc admission of an emergency
y call call fails, preemption is
performed for the emergency
FDD IMS- None Emergency call.
based Call
emergenc
y call

eRAN
RAT Function Function Reference Description

Name Switch
FDD Next NG_ECAL Emergency

Generatio L_SW Call
n eCall option of
over LTE the
Emc.Eme
rgCallOp
timizatio
nSw
paramete
r
5.3 Requirements
5.3.1 Licenses
The following are FDD license requirements.
RAT Feature ID Feature Name Model Sales Unit
FDD LOFD-001029 Enhanced LT1S000EAC00 per RRC

Admission Connected User
Control
5.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated. For detailed
operations, see the relevant feature documents.
RAT Function Name Function Switch Reference
FDD Radio-resource- UlSwitch and DlSwitch Admission and

based admission options of the Congestion
control CellAlgoSwitch.RacAlgoSwitc Control
h parameter

None

eRAN
5.3.3 Hardware
Base Station Models
FDD:
● 3900 and 5900 series base stations
● DBS3900 LampSite and DBS5900 LampSite
● BTS3912E
● BTS3911E
● BTS3203E
● BTS3202E
NOTE
The BTS3203E does not support ARP modification for NSA-DC-capable UEs.
The BTS3202E does not support ARP modification for NSA-DC-capable UEs.
Boards
No requirements
RF Modules
No requirements
5.3.4 Networking
None
5.3.5 Others
The preemption capability and vulnerability must be specified in the EPC for
services with different priorities.
Service Preemption
QoS-satisfaction-rate-based admission control must be configured ahead of
service preemption. For details, see QoS-Satisfaction-Rate-based Admission
Control.

eRAN

Name
RAC algorithm CellAlgoSwitch. PreemptionSw Retain the default value.

switch RacAlgoSwitch itch

Name
Preempt CellRacThd.PreResNeedTuning- Set this parameter to its

Resource Need Factor recommended value.
Tuning Factor
UE-Number-based Preemption

Name
UE number ENodeBAlgoSwi IntraOpUeNu Retain the default value.

preemption tch.UeNumPree mPreemptSwit
switch mptSwitch ch

Name
Csfb User Arp CSFallBackPolicyCfg.CsfbUserArp Set this parameter to its

Configuration CfgSwitch recommended value.
Switch
Normal Csfb CSFallBackPolicyCfg.NormalCsfb Set this parameter to its

User Arp UserArp recommended value.

eRAN

Name
MO Signaling CellRacThd.MoSigArpOverride Configure the ARP

ARP Override priorities for UEs whose
RRC connection requests
contain the cause value
of mo-Signalling. If
signaling ARP
modification is enabled,
set this parameter by
referring to the ARP
values configured in the
EPC.
NSA User ARP CellRacThd.NsaArpOverride Set this parameter based

Override on the network plan.
Preemption-triggered Redirection
Table 5-5 describes the parameters used for function activation. No parameter is
involved in function optimization.

eRAN

Name
Redirection ENodeBAlgoSwi LoadBasedSwit In a multi-RAT multi-

switch tch.RedirectSwi ch frequency network, if
tch LoadRedirectFr preemption is enabled, it
eqOptSwitch is recommended that
the LoadBasedSwitch
option be selected to
redirect UEs whose RRC
connections are released
after they are preempted
or fail to preempt other
UEs, to other
frequencies. This
prevents these UEs from
accessing the current
frequency again and
experiencing access
failures.
If preemption is enabled,
it is recommended that
the LoadRedirectFre-
qOptSwitch option be
selected to prevent UEs
from experiencing ping-
pong redirection among
multiple frequencies.
Activation Command Examples

//Service preemption
MOD CELLALGOSWITCH: LocalCellId=0, RacAlgoSwitch=PreemptionSwitch-1;
//UE-number-based preemption
MOD
ENODEBALGOSWITCH:UeNumPreemptSwitch=IntraOpUeNumPreemptSwitch-1&InterOpUeNumPreemptSwi
tch-1;
//Preemption-triggered redirection

//Setting the ARP priority when the number of UEs is limited
MOD CSFALLBACKPOLICYCFG:CsfbUserArpCfgSwitch=ON,NormalCsfbUserArp=2;

eRAN
//Setting the ARP priority for UEs whose RRC connection requests contain the cause value of mo-Signalling
MOD CELLRACTHD:LocalCellId=0,MoSigArpOverride=2;
//Setting the NSA User ARP Override parameter
MOD CELLRACTHD:LocalCellId=0,NsaArpOverride=2;
//Setting the Preempt Resource Need Tuning Factor parameter
MOD CELLRACTHD:LocalCellId=0,PreResNeedTuningFactor=100;
Deactivation Command Examples

conditions.
//Deactivating service preemption
MOD CELLALGOSWITCH: LocalCellId=0, RacAlgoSwitch=PreemptionSwitch-0;
//Deactivating UE-number-based preemption

MOD ENODEBALGOSWITCH:
UeNumPreemptSwitch=IntraOpUeNumPreemptSwitch-0&InterOpUeNumPreemptSwitch-0;
//Deactivating ARP priority configuration when the number of UEs is limited

MOD CSFALLBACKPOLICYCFG: CsfbUserArpCfgSwitch=OFF;
MOD CELLRACTHD: LocalCellId=0, MoSigArpOverride=0;
//Deactivating preemption-triggered redirection



Scenario 1: Service Preemption
In this scenario, two GBR services (A and B) are initiated. 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 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 5-1, 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 5-1 Checking the ARP priority level and the preemption attributes of the
QCI

eRAN
Monitoring.
Step 2 Use UEs to access a cell, and perform GBR service B (with a QCI of 4) on some
UEs.
Step 3 Perform GBR service A (with a QCI of 3) on some other UEs. Follow operations in
step 2 described in 4.4.2 Activation Verification to simulate a scenario where
requests for GBR service A are rejected based on QoS satisfaction rates. Initiate
new GBR service A. Based on preemption principles, high-priority services can be
admitted by preempting low-priority services. Therefore, GBR service A can
preempt GBR service B.
Step 4 Monitor S1 signaling to verify that GBR service A preempts GBR service B. GBR
service B is released, and the S1AP_ERAB_REL_IND message includes the release
cause value radioNetwork:reduce-load-in-serving-cell, as shown in Figure 5-2.
GBR service A is successfully set up.
Figure 5-2 S1AP_ERAB_REL_IND message that indicates successful preemption
----End
Scenario 2: Intra-Operator UE-Number-based Preemption

If UE-number-based preemption is enabled and all UEs can both be preempted
and preempt other UEs, UEs with high priorities can preempt UEs with low
priorities to access the cell when the number of UEs has reached the maximum
permissible number of UEs. The verification procedure is as follows:
Step 1 On the MAE-Access, create and start an S1 interface tracing task.
Step 2 Select the IntraOpUeNumPreemptSwitch option of the

ENodeBAlgoSwitch.UeNumPreemptSwitch parameter, and set the
CellRacThd.AcUserNumber parameter to 1.
Step 3 Use a UE that meets the following requirements to access the network:
● The ARP value for the default bearer is 7.
● The ARP IE Pre-emption Vulnerability is set to pre-emptable for the default
bearer.
Step 4 Use another UE that meets the following requirements and is served by the same
operator to access the network:
● The ARP value for the default bearer is 1.
● The IE Pre-emption Capability is set to may trigger pre-emption for the
default bearer.

eRAN
Step 5 Monitor S1 signaling to verify that the UE having a default bearer with the ARP
value of 7 is preempted. The S1AP_UE_CONTEXT_REL_REQ message includes the
release cause value radioNetwork:reduce-load-in-serving-cell, as shown in Figure
5-3. The new UE successfully accesses the network.
Figure 5-3 S1AP_UE_CONTEXT_REL_REQ message that indicates successful

preemption
----End
Scenario 3: Preemption-triggered Redirection

If the preemption function is successfully verified, perform the following steps to
verify the function of preemption-triggered redirection.
Step 1 On the MAE-Access, create and start a Uu interface tracing task.
Step 2 Monitor Uu signaling to verify that the RRC_CONN_REL message including the IE
redirectedCarrierInfo appears, as shown in Figure 5-4.
Figure 5-4 RRC_CONN_REL message that indicates a UE is preempted and then

redirected
----End

Enhanced admission control involves RRC connection management and bearer
management.
After preemption is activated, the eNodeB sets up RRC connections first for a UE,
and then triggers preemption. If a UE fails the preemption, the RRC connection for
this UE is released. If the preemption is successful, the RRC connection for the
preempted UE is released. The L.Cell.UserSpec.PrepEmp.PrepAtt.Num counter
measures the number of released RRC connections.
The following counters measure the number of RRC connections of UEs that
successfully preempt resources of other UEs:
● L.Cell.UserLimit.PreEmp.Num
● L.Cell.UserLic.PrepEmp.Succ.Num
● L.Cell.UserLic.PrepEmp.Succ.Num.PLMN

eRAN
The number of E-RABs that are preempted and then released is counted in the
L.E-RAB.AbnormRel.Cong.PreEmp counter.

eRAN
Parameter Description 6 Congestion Control
6 Congestion Control
6.1 Principles
6.1.1 Congestion Control over GBR Services

Figure 6-1 shows the congestion control process of GBR services. Congestion
control is enabled if the DlLdcSwitch and UlLdcSwitch option of the
CellAlgoSwitch.RacAlgoSwitch parameter are selected.
Figure 6-1 Congestion control process

eRAN
When a cell is congested, congestion control preferentially releases the GBR

services with low priorities to mitigate the congestion degree and free some
resources. The release reduces system load and helps ensure the QoS of other
admitted services. To ensure continuity and stability of emergency calls, the
eNodeB does not release emergency calls.
6.1.1.1 Load Status Evaluation

The eNodeB evaluates the load status by monitoring the PRB usage and QoS
satisfaction rate. The cell status can be either of the following:
● Congested state
A cell is regarded as congested in the downlink if the downlink QoS
satisfaction rate of services with one or more QCIs is less than
CellQciPara.CongestionThreshold and the downlink system resource usage is
high.
A cell is regarded as congested in the uplink if the uplink QoS satisfaction rate
of services with one or more QCIs is less than
CellQciPara.CongestionThreshold and the uplink system resource usage is
high.
For details about how to determine system resource usage status, see 4.1.2.2
GBR Service Admission.
When the cell is congested, the congestion control algorithm instructs the
admission control algorithm to reject all access requests and, in addition,
takes actions to reduce cell load. When the QoS satisfaction rates of services
with QCIs 1 to 4 all become higher than the sum of
CellQciPara.CongestionThreshold and CellRacThd.CongRelOffset, the cell
returns to the normal state.
For each QCI, the sum of CellQciPara.CongestionThreshold and
CellRacThd.CongRelOffset must be less than
CellQciPara.HandoverAdmissionThreshold.
● Normal state
The cell is regarded as normal if the QoS satisfaction rates of services with all
QCIs are all greater than CellQciPara.CongestionThreshold.
6.1.1.2 Congestion Handling

When a cell is congested in the uplink or downlink, the eNodeB releases the
highest-ranking one of the GBR services that meet both of the following
conditions and restricts admission of GBR services.
● The number of RBs used is not 0.
● The value of the ARP IE Pre-emption Vulnerability of the service is pre-
emptable and the ARP value is not 15.
For details about the ranking of GBR services, see 5.1.2 Service Preemption.
When the ARP values of all GBR services are the same in the cell, the eNodeB
releases UEs that occupy the most PRBs.
Emergency calls can be released by congestion control only when admission and
congestion control over emergency calls, MCPTT QoS management, and
congestion control for public safety are all enabled.

eRAN
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 the redirection procedure, see 4.1.3
Redirection.
After the GBR service is released, the eNodeB checks whether the QoS satisfaction
rates of GBR services are restored. If they are not restored, the eNodeB performs
the GBR service release procedure again until the congestion is cleared.
6.1.2 Congestion Control over Non-GBR Services

When user experience deteriorates because of cell congestion, the eNodeB lowers
the scheduling priorities of non-GBR services for UEs with poor signal quality and
decreases the probability of scheduling these UEs in the uplink and downlink.
Congestion control over non-GBR services is enabled if the

UeExpBasedCongCtrlSw option of the CellAlgoSwitch.RacAlgoSwitch parameter
is selected.
6.1.2.1 Load Status Evaluation

UE-experience-based congestion states include:
● Uplink congested
● Downlink congested
● Uplink and downlink congested
● Congestion cleared
A cell is in the UE-experienced-based congestion state if any of the preceding

situations occurs. The eNodeB determines the congestion status as follows:
● Uplink congested
When the uplink UE-perceived data rate is lower than
CellRacThd.UlExperienceThd and the uplink resource is congested, the cell is
uplink congested.
– The uplink cell resource is congested when the uplink PRB usage of the
cell is greater than or equal to CellRacThd.RbCongHighThd or the CCE
allocation failure rate of the cell is greater than or equal to
CellRacThd.CceAlFailHighThd.
– The uplink cell resource is not congested when the uplink PRB usage is
less than max(CellRacThd.RbCongHighThd – 10%, 0) and the CCE
allocation failure rate of the cell is less than
max(CellRacThd.CceAlFailHighThd – 10%, 0).
● Downlink congested
When the downlink UE-perceived data rate is lower than
CellRacThd.DlExperienceThd and the downlink resource is congested, the
cell is downlink congested.
– The downlink cell resource is congested when the downlink PRB usage of
the cell is greater than or equal to CellRacThd.RbCongHighThd or the
CCE allocation failure rate of the cell is greater than or equal to
CellRacThd.CceAlFailHighThd.

eRAN
– The downlink cell resource is not congested when the downlink PRB
usage is less than max(CellRacThd.RbCongHighThd – 10%, 0) and the
CCE allocation failure rate of the cell is less than
max(CellRacThd.CceAlFailHighThd – 10%, 0).
6.1.2.2 Decrease in Priorities for Scheduling Cell Edge UEs

When a cell is congested, the eNodeB decreases the uplink and downlink dynamic
scheduling priorities for non-GBR services of some cell edge UEs in the cell. When
the cell congestion is cleared (neither the uplink nor the downlink is congested),
the eNodeB restores the priorities for non-GBR services of the cell edge UEs.
The eNodeB determines that a UE is a cell edge UE if the filtered CQI value less
than CellRacThd.CqiFarThd or the uplink SINR is less than –1 dB.
6.2.1 Benefits
When a cell is overloaded, the eNodeB releases some UEs or lowers the scheduling
priorities for some UEs to ensure the QoS of other UEs in the cell.
Congestion control over GBR services maximizes system capacity while
preferentially satisfying the QoS requirements of UEs with high ARP priorities.
6.2.2 Impacts
Network Impacts
Congestion control over GBR services increases the service drop rate. This is
because the congestion-control-triggered releases of bearers are regarded as
service drops. Counters are provided to indicate congestion-triggered service drops.
For details, see 6.4.3 Network Monitoring. Congestion control over GBR services
rejects admission of new services in the GBR congestion state, which affects the E-
RAB setup success rate.
When user experience is poor due to loads, congestion control over non-GBR
services lowers the priorities for scheduling UEs with poor signal quality in the
uplink and downlink. This reduces the extent to which user experience of other
UEs is suppressed and therefore increases overall cell capacity. If the number of
UEs is large, the increase in the cell traffic volume is small and UEs with poor
signal quality cannot be scheduled. This is because the scheduling priorities are
decreased for only a few UEs. As a result, the average UE throughput decreases,
and the average RRC connection setup duration and the service drop rate increase.
Function Impacts
None
6.3 Requirements

eRAN
6.3.1 Licenses
None
6.3.2 Software
None

None
6.3.3 Hardware
Base Station Models

No requirements
Boards
No requirements
RF Modules
No requirements
6.3.4 Networking
None
6.3.5 Others
As required by congestion control for the EPC, only the services whose ARP IE Pre-
emption Vulnerability is pre-emptable can be released if the DlLdcSwitch or
UlLdcSwitch option of the CellAlgoSwitch.RacAlgoSwitch parameter is selected.
Therefore, the IE Pre-emption Vulnerability must be set to pre-emptable in the
EPC.

Table 6-1 describes the parameters used for function activation. Table 6-2 and
Table 6-3 describe the parameters used for function optimization.

eRAN

Name
RAC algorithm CellAlgoSwitch. DlLdcSwitch For GBR services, it is

switch RacAlgoSwitch recommended that this
option be selected.
UlLdcSwitch For GBR services, it is

recommended that this
option be selected.
UeExpBasedCo For non-GBR services, it

ngCtrlSw is recommended that
this option be selected.
CCE Usage CellRacThd.Cce None Set this parameter to its

Threshold UsageThd recommended value.
Table 6-2 Parameters used for optimization (congestion control over GBR
services)
Name
Congestion CellQciPara.Con None Set this parameter to its

Threshold gestionThresho recommended value.
ld
Offset for CellRacThd.Con None Set this parameter to its
service congest gRelOffset recommended value.
relieving
High RB Usage CellRacThd.UlR None Set this parameter to its

Thld bHighThd recommended value.
Low RB Usage CellRacThd.UlR None Set this parameter to its

Thld bLowThd recommended value.
Redirection ENodeBAlgoSwi LoadBasedSwit If congestion control is

switch tch.RedirectSwi ch enabled, it is
tch recommended that this
redirect UEs whose RRC
connections are released
due to congestion
control to other
frequencies, preventing
these UEs from
experiencing re-access
failures.

eRAN

Name
LoadRedirectFr If congestion control is

eqOptSwitch enabled, it is
recommended that this
prevent UEs from
experiencing ping-pong
redirection among
multiple frequencies.
Table 6-3 Parameters used for optimization (congestion control over non-GBR
services)
Name
CCE Allocation CellRacThd.CceAlFailHighThd Set this parameter to its

Failure High recommended value.
Threshold
RB Congestion CellRacThd.RbCongHighThd Set this parameter to its

High Threshold recommended value.
CQI Threshold CellRacThd.CqiFarThd Set this parameter to its

for Far Users recommended value.
DL Experience CellRacThd.DlExperienceThd Set this parameter to its

Rate Threshold recommended value.
UL Experience CellRacThd.UlExperienceThd Set this parameter to its

Rate Threshold recommended value.
Activation Command Examples

//Congestion control over GBR services
MOD CELLALGOSWITCH: LocalCellId=0, RacAlgoSwitch=DlLdcSwitch-1&UlLdcSwitch-1;
//Congestion control over non-GBR services

MOD CELLALGOSWITCH: LocalCellId=0, RacAlgoSwitch=UeExpBasedCongCtrlSw-1;

//Congestion control over GBR services
MOD CELLRACTHD: LocalCellId=0, CongRelOffset=20, UlRbHighThd=95, UlRbLowThd=90, CceUsageThd=80;

eRAN
MOD ENODEBALGOSWITCH: RedirectSwitch=LoadBasedSwitch-1&LoadRedirectFreqOptSwitch-1;

MOD CELLQCIPARA: LocalCellId=0, Qci=1, CongestionThreshold=65;
//Congestion control over non-GBR services

MOD CELLRACTHD: LocalCellId=0, CceAlFailHighThd=10, CqiFarThd=5, DlExperienceThd=200,
RbCongHighThd=95, UlExperienceThd=16;
Deactivation Command Examples

conditions.
//Deactivating congestion control over GBR services
MOD CELLALGOSWITCH: LocalCellId=0, RacAlgoSwitch=DlLdcSwitch-0&UlLdcSwitch-0;
//Deactivating congestion control over non-GBR services

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


Scenario 1: Congestion Control over GBR Services
Monitoring.
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. Move some UEs towards the cell center and increase the traffic
volume of GBR services on these UEs. Move some UEs towards the cell edge until
the cell is congested, as indicated by Congestion State in the monitoring results.
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 message,
as shown in Figure 6-2, the indicated low-priority service has been released as
expected.
Figure 6-2 S1AP_ERAB_REL_IND message that indicates the release of a low-

priority service
----End
If the function of congestion-control-based redirection is activated, trace messages
over the Uu interface by referring to the operations in Scenario 3: Preemption-
triggered Redirection in 5.4.2 Activation Verification to verify that this function
has taken effect.

eRAN
Scenario 2: Congestion Control over Non-GBR Services

Use UEs to access a cell and perform non-GBR services. Move some UEs towards
the cell edge until the cell is in the user-experience-based congestion state.
Check whether the traffic volume in a cell increases after congestion control over
non-GBR services is enabled. The traffic volume in the cell can be calculated by
using the following formula:
Traffic volume in a cell = L.Thrp.bits.DL + L.Thrp.bits.UL

Congestion control involves RRC connection management and bearer
management.
● When congestion control over GBR services has taken effect, the
L.LC.ULCong.Dur.Cell and L.LC.DLCong.Dur.Cell counters measure the uplink
congestion duration and downlink congestion duration, respectively, during
congestion control. The L.LC.ULCong.Num.Cell and L.LC.DLCong.Num.Cell
counters measure the numbers of times uplink congestion and downlink
congestion occur in a cell, respectively. The L.LC.User.Rel counter measures
the number of bearers released due to congestion control.
● When congestion control over GBR services has taken effect, the
L.RRCRedirection.IntraLTE counter value includes the number of redirections
after redirections are triggered.

eRAN
Parameter Description 7 Parameters
7 Parameters
The following hyperlinked EXCEL files of parameter documents match the

software version with which this document is released.
● Node Parameter Reference: contains device and transport parameters.

● eNodeBFunction Parameter Reference: contains all parameters related to
radio access functions, including air interface management, access control,
mobility control, and radio resource management.
● eNodeBFunction Used Reserved Parameter List: contains the reserved
parameters that are in use and those that have been disused.
NOTE
You can find the EXCEL files of parameter reference and used reserved parameter list for
the software version used on the live network from the product documentation delivered
with that version.
FAQ 1: How do I find the parameters related to a certain feature from

parameter reference?
Step 1 Open the EXCEL file of parameter reference.
Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, LOFD-001016 or
TDLOFD-001016.
Step 3 Click OK. All parameters related to the feature are displayed.
----End
FAQ 2: How do I find the information about a certain reserved parameter

from the used reserved parameter list?
Step 1 Open the EXCEL file of the used reserved parameter list.
Step 2 On the Used Reserved Parameter List sheet, use the MO, Parameter ID, and BIT
columns to locate the reserved parameter, which may be only a bit of a parameter.
View its information, including the meaning, values, impacts, and product version
in which it is activated for use.
----End

eRAN
Parameter Description 8 Counters
8 Counters
The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
● Node Performance Counter Summary: contains device and transport counters.
● eNodeBFunction Performance Counter Summary: contains all counters related
to radio access functions, including air interface management, access control,
mobility control, and radio resource management.
NOTE
You can find the EXCEL files of performance counter reference for the software version used
on the live network from the product documentation delivered with that version.
FAQ: How do I find the counters related to a certain feature from

performance counter reference?
Step 1 Open the EXCEL file of performance counter reference.

Step 2 On the Counter Summary(En) sheet, filter the Feature ID column. Click Text
Filters and choose Contains. Enter the feature ID, for example, LOFD-001016 or
TDLOFD-001016.
Step 3 Click OK. All counters related to the feature are displayed.
----End

eRAN
Parameter Description 9 Reference Documents
9 Reference Documents
1. 3GPP TS 23.203, "Policy and charging control architecture"

2. 3GPP TS 23.401, "General Packet Radio Service (GPRS) enhancements for
Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access"
3. 3GPP TS 36.306, "User Equipment (UE) radio access capabilities"
4. 3GPP TS 36.321, "Medium Access Control (MAC) protocol specification"
5. 3GPP TS 36.413, "S1 Application Protocol (S1AP)"
6. Transmission Resource Management
7. Scheduling
8. Flexible User Steering
9. Flow Control
10. Physical Channel Resource Management
11. PTT
12. Intra-RAT Mobility Load Balancing
13. Carrier Aggregation
14. Emergency Call
15. Mobility Management in Connected Mode

Admission and Congestion Control (eRAN18.1 - 01)

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 (eRAN18.1 - 01)

Uploaded by

Copyright:

Available Formats

eRAN

Admission and Congestion Control

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2022-03-08) Copyright © Huawei Technologies Co., Ltd. i

2 About This Document.............................................................................................................3

5 Enhanced Admission Control.............................................................................................. 29

Issue 01 (2022-03-08) Copyright © Huawei Technologies Co., Ltd. ii

Issue 01 (2022-03-08) Copyright © Huawei Technologies Co., Ltd. iii

6.4.3 Network Monitoring......................................................................................................................................................... 52

Issue 01 (2022-03-08) Copyright © Huawei Technologies Co., Ltd. iv

This chapter describes changes not included in the "Parameters", "Counters",

1.1 eRAN18.1 01 (2022-03-08)

1.2 eRAN18.1 Draft A (2021-12-30)

Issue 01 (2022-03-08) Copyright © Huawei Technologies Co., Ltd. 1

Added an impact None FDD ● 3900 and 5900

Issue 01 (2022-03-08) Copyright © Huawei Technologies Co., Ltd. 2

2 About This Document

2.1 General Statements

● The technical principles of features and their related parameters

2.2 Applicable RAT

2.3 Features in This Document

Issue 01 (2022-03-08) Copyright © Huawei Technologies Co., Ltd. 3

Feature ID Feature Name Chapter/Section

LBFD-002023 Admission Control 4 Admission Control

LOFD-001029 Enhanced Admission 5 Enhanced Admission

LOFD-00102901 Radio and

LBFD-002024 Congestion Control 6 Congestion Control

Issue 01 (2022-03-08) Copyright © Huawei Technologies Co., Ltd. 4

Admission and congestion control consists of admission control and congestion

Admission control consists of transport-resource-based and radio-resource-based admission

Issue 01 (2022-03-08) Copyright © Huawei Technologies Co., Ltd. 5

4.1.1 UE Admission Procedure

Issue 01 (2022-03-08) Copyright © Huawei Technologies Co., Ltd. 6

Figure 4-1 UE admission procedure

The UE admission procedure is as follows:

Issue 01 (2022-03-08) Copyright © Huawei Technologies Co., Ltd. 7

▪ The number of UEs in a cell has reached

▪ The CellRacThd.AcReservedUserNumber parameter is set to 0 and

▪ The number of UEs in a cell has reached

Issue 01 (2022-03-08) Copyright © Huawei Technologies Co., Ltd. 8

CellRacThd.AcReservedUserNumber and the number of cells set up

▪ The number of UEs in a cell has reached

4.1.2 Service Admission Procedure

Issue 01 (2022-03-08) Copyright © Huawei Technologies Co., Ltd. 9

Figure 4-2 Service admission procedure

The EmcAdmitCongSwitch option of the CellAlgoSwitch.RacAlgoSwitch

Issue 01 (2022-03-08) Copyright © Huawei Technologies Co., Ltd. 10

4.1.2.1 Non-GBR Service Admission

4.1.2.2 GBR Service Admission

Issue 01 (2022-03-08) Copyright © Huawei Technologies Co., Ltd. 11

Figure 4-3 Downlink admission procedure for GBR services

Issue 01 (2022-03-08) Copyright © Huawei Technologies Co., Ltd. 12

Figure 4-4 Uplink admission procedure for GBR services

● If the VOLTE_UNCONDITIONAL_ADMISSION option of the

Issue 01 (2022-03-08) Copyright © Huawei Technologies Co., Ltd. 13

● If the MCPTT_UNCONDITIONAL_ADMISSION option of the

QoS Satisfaction Rate Evaluation

Downlink QoS Satisfaction Rate Evaluation

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

Issue 01 (2022-03-08) Copyright © Huawei Technologies Co., Ltd. 14

Uplink QoS Satisfaction Rate Evaluation