Admission and Congestion Control (ERAN15.1 - 01)

eRAN
Admission and Congestion Control

Feature Parameter Description
Issue 01
Date 2019-06-06
HUAWEI TECHNOLOGIES CO., LTD.

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

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

eRAN
Admission and Congestion Control Feature Parameter
Description Contents
Contents
1 Change History.............................................................................................................................. 1
1.1 eRAN15.1 01 (2019-06-06)............................................................................................................................................1
1.2 eRAN15.1 Draft B (2019-01-10)....................................................................................................................................1
1.3 eRAN15.1 Draft A (2019-01-05)................................................................................................................................... 2
2 About This Document.................................................................................................................. 3

2.1 General Statements......................................................................................................................................................... 3
2.2 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.................................................................................................................................................................18
4.2 Network Analysis......................................................................................................................................................... 20
4.2.1 Benefits...................................................................................................................................................................... 20
4.2.2 Impacts.......................................................................................................................................................................20
4.3 Requirements................................................................................................................................................................ 20
4.3.1 Licenses..................................................................................................................................................................... 21
4.3.2 Software.....................................................................................................................................................................21
4.3.3 Hardware................................................................................................................................................................... 21
4.3.4 Networking................................................................................................................................................................ 21
4.3.5 Others.........................................................................................................................................................................21
4.4 Operation and Maintenance..........................................................................................................................................21
4.4.1 Data Configuration.................................................................................................................................................... 21
4.4.1.1 Data Preparation..................................................................................................................................................... 21
4.4.1.2 Using MML Commands......................................................................................................................................... 23
4.4.1.3 Using the CME....................................................................................................................................................... 24
4.4.2 Activation Verification.............................................................................................................................................. 24
4.4.3 Network Monitoring.................................................................................................................................................. 24
Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. ii

eRAN
5 Enhanced Admission Control................................................................................................... 27

5.1 Principles...................................................................................................................................................................... 27
5.1.1 UE Preemption.......................................................................................................................................................... 27
5.1.2 Service Preemption....................................................................................................................................................29
5.2.1 Benefits...................................................................................................................................................................... 31
5.2.2 Impacts.......................................................................................................................................................................31
5.3 Requirements................................................................................................................................................................ 31
5.3.1 Licenses..................................................................................................................................................................... 31
5.3.2 Software.....................................................................................................................................................................32
5.3.3 Hardware................................................................................................................................................................... 32
5.3.4 Networking................................................................................................................................................................ 32
5.3.5 Others.........................................................................................................................................................................33
5.4.1.3 Using the CME....................................................................................................................................................... 36
6 Congestion Control..................................................................................................................... 39
6.1 Principles...................................................................................................................................................................... 39
6.1.1 Congestion Control over GBR Services.................................................................................................................... 39
6.1.1.1 Load Status Evaluation........................................................................................................................................... 40
6.1.1.2 Congestion Handling.............................................................................................................................................. 40
6.1.2 Congestion Control over Non-GBR Services............................................................................................................41
6.1.2.1 Load Status Evaluation........................................................................................................................................... 41
6.1.2.2 Decrease in Priorities for Scheduling Cell Edge UEs............................................................................................ 41
6.2.1 Benefits...................................................................................................................................................................... 42
6.2.2 Impacts.......................................................................................................................................................................42
6.3 Requirements................................................................................................................................................................ 42
6.3.1 Licenses..................................................................................................................................................................... 42
6.3.2 Software.....................................................................................................................................................................42
6.3.3 Hardware................................................................................................................................................................... 43
6.3.4 Networking................................................................................................................................................................ 43
6.3.5 Others.........................................................................................................................................................................43
6.4.1.3 Using the CME....................................................................................................................................................... 45
Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. iii

eRAN

7 Parameters..................................................................................................................................... 48
8 Counters........................................................................................................................................ 49
9 Glossary......................................................................................................................................... 50
10 Reference Documents............................................................................................................... 51
Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. iv

eRAN
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:
l Technical changes
Changes in functions and their corresponding parameters
l Editorial changes
Improvements or revisions to the documentation
1.1 eRAN15.1 01 (2019-06-06)

This issue does not include any changes.
1.2 eRAN15.1 Draft B (2019-01-10)

This issue includes the following changes.
Technical Changes
Change Description Parameter Change RAT Base Station
Model
Added UE number resource Added the following FDD l 3900 and 5900
reservation for UEs involved parameters: series base
in incoming necessary l CellRacThd.HoRese stations
handovers (for example, rvedUeNumber l DBS3900
coverage-based handover) LampSite and
and unconditional admission l CellRacThd.Admissi
onControlPolicy DBS5900
control switch for voice LampSite
services. For details, see 4.1.1
UE Admission Procedure l BTS3912E
and 4.1.2.2 GBR Service l BTS3911E
Admission.
Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 1

eRAN
Description 1 Change History
Editorial Changes
Revised descriptions in this document.
1.3 eRAN15.1 Draft A (2019-01-05)

This issue introduces the following changes to eRAN13.1 01 (2018-04-10).
Technical Changes
Change Description Parameter Change RAT Base Station
Model
Added counters related to E- None FDD l 3900 and 5900

RAB setup failures. For series base
details, see 4.4.3 Network stations
Monitoring. l DBS3900
LampSite and
DBS5900
LampSite
l BTS3912E
l BTS3911E
Editorial Changes
Revised descriptions in this document.

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

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

l The scenarios where these features are used, the benefits they provide, and the impact
they have on networks and functions
l Requirements of the operating environment that must be met before feature activation
l 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
the desired 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 RAT
This document applies to FDD.
2.3 Features in This Document

This document describes the following FDD features.

eRAN
Description 2 About This Document
Feature ID Feature Name 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
Description 3 Overview
3 Overview
Admission and congestion control consists of admission control and congestion control.
l During admission control, an eNodeB decides whether to accept a guaranteed bit rate
(GBR) service request (either a new service or handover) based on the physical resource
block (PRB) usage and the quality of service (QoS) satisfaction rate of GBR services.
l During congestion control, 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
Description 4 Admission Control
4 Admission Control
4.1 Principles
Admission control is enabled if the DlSwitch and UlSwitch options of the
CellAlgoSwitch.RacAlgoSwitch parameter are selected.
4.1.1 UE Admission Procedure

When a new UE attempts to access a network, a UE admission procedure starts. UEs can be
classified into the following types:
l 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.
l 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.
l 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 eNodeB checks whether the CPU resources are limited. If the CPU resources are
limited, the eNodeB rejects the access request. For details about how to check whether
CPU resources are limited, see Flow Control.

eRAN
2. The eNodeB checks whether the sounding reference signal (SRS) resources are
successfully allocated. For details about the SRS resource allocation principle, see
Physical Channel Resource Management. The eNodeB performs this step depending on
the baseband processing unit (BBP) type.
In FDD:
– If the LBBPc is configured, the eNodeB performs this step as follows:
n 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.
n 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 eNodeB checks whether the PUCCH resources are successfully allocated. If
PUCCH resource allocation fails, the eNodeB 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:
n The number of UEs in a cell has reached min(CellRacThd.AcUserNumber,
maximum number of UEs that can access the cell due to the limitation of
hardware capabilities).
n The number of UEs served by a board that serves the cell has reached its
maximum number due to the limitation of hardware capabilities.
n 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:
hardware capabilities) minus CellRacThd.AcReservedUserNumber.
maximum number due to the limitation of hardware capabilities minus the
product of CellRacThd.AcReservedUserNumber and the number of cells set
up on the board.
n The number of UEs served by the eNodeB has reached the licensed number of
UEs served by the eNodeB.
– Common UEs

eRAN
hardware capabilities) minus the sum of

CellRacThd.AcReservedUserNumber and
CellRacThd.HoReservedUeNumber.
maximum number due to the limitation of hardware capabilities minus the
product of the number of cells set up on the board and the sum of
CellRacThd.AcReservedUserNumber and
CellRacThd.HoReservedUeNumber.
n The number of UEs served by the eNodeB has reached the licensed number of
UEs served by the eNodeB.
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) QoS management and

eRAN
congestion control for public safety are enabled. For details about MCPTT QoS management
and congestion control for public safety, see PTT.
l 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.
l 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

The procedure for non-GBR service admission is as follows:
l If SRS or PUCCH resources fail to be allocated, service admission is rejected.
l If both the SRS and PUCCH resources are allocated successfully, non-GBR 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

To ensure QoS, the procedure for GBR service admission is as follows:
l If SRS or PUCCH resources fail to be allocated, service admission is rejected.
l 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, voice 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

eRAN
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 VoIP 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 VoIP services in a cell to the
total number of VoIP services in a cell.
The downlink QoS satisfaction rate of any VoIP service is calculated by using the following
formula:
A VoIP packet is satisfactory if it is buffered for a time less than 50 ms.
For a GBR service with QCI x (x ranges from 2 to 4), its downlink QoS satisfaction rate is
calculated by using the following formula:

eRAN
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 VoIP services.
Uplink QoS Satisfaction Rate Evaluation

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

eRAN
l 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:
l ARP threshold for gold-level services: CellRacThd.GoldServiceArpThd

l ARP threshold for silver-level services: CellRacThd.SilverServiceArpThd
l ARP threshold for bronze-level services: CellRacThd.CopperServiceArpThld
A service is defined as an iron-level service if its ARP value is greater than

CellRacThd.CopperServiceArpThld. 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, CellRacThd.CopperServiceArpThld] Bronze
(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:
l 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.
l 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.

eRAN

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:
l CellQciPara.HandoverAdmissionThreshold ≤
CellQciPara.HandoverAdmissionThreshold + CellRacThd.NewGoldServiceOffset
l CellQciPara.HandoverAdmissionThreshold + CellRacThd.NewGoldServiceOffset ≤
CellQciPara.HandoverAdmissionThreshold + CellRacThd.NewSilverServiceOffset
l CellQciPara.HandoverAdmissionThreshold + CellRacThd.NewSilverServiceOffset ≤
CellQciPara.HandoverAdmissionThreshold + CellRacThd.NewCopperServiceOffset
l CellQciPara.HandoverAdmissionThreshold + CellRacThd.NewCopperServiceOffset
≤ CellQciPara.HandoverAdmissionThreshold + CellRacThd.NewIronServiceOffset
Downlink admission control rules are as follows:
l 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 handover services with each QCI are checked. If the QoS satisfaction
rate of the services is greater than or equal to the corresponding admission
threshold, the services can be admitted.
l If the QoS satisfaction rate of services with a certain QCI is less than the admission
threshold of non-load-based handovers, the non-load-based handovers of the services
with this QCI cannot be admitted, and neither the new services nor load-based handover
services with all QCIs can be admitted.
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:
l 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 VoIP services is
long.
l 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.

eRAN
– 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 usage, wait time for uplink scheduling for VoIP services,
and GBR CCE usage are calculated as follows:
l Downlink GBR PRB usage
l Uplink GBR PRB usage
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.
l Waiting time for uplink scheduling of VoIP services
The wait time starts when a VoIP service requests uplink resources and stops when the
VoIP service is allocated uplink resources. eNodeBs regard wait time longer than 100 ms
to be too long.
l 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:

eRAN
l The LoadBasedSwitch option of this parameter controls whether to enable load-based

redirection.
l The LoadRedirectFreqOptSwitch option controls the policy for selecting a target
frequency for redirection.
Figure 4-5 shows the redirection process.
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:

eRAN
– 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.
– 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
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.
Prerequisite Functions
None
Mutually Exclusive Functions

None
4.3.3 Hardware
Base Station Models
No requirements
Boards
No requirements
RF Modules
No requirements
4.3.4 Networking
None
4.3.5 Others
In FDD, there are no requirements.
4.4 Operation and Maintenance
4.4.1 Data Configuration
4.4.1.1 Data Preparation
UE-Number-based Admission Control

This function is enabled by default and does not need activation. Table 4-2 describes the
parameters used for function optimization.

eRAN
Table 4-2 Parameters used for optimization

Parameter Parameter ID Setting Notes
Name
Admission CellRacThd.AcUserNumber None

Control User
Number
Admission CellRacThd.AcReservedUserNumber None

Control Reserved
User Number
UE Number CellRacThd.HoReservedUeNumber None

Reserved for
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.R DlSwitch and None

switch acAlgoSwitch UlSwitch
CCE Usage CellRacThd.Cce N/A The value 80 is

Threshold UsageThd recommended.

Name
Gold service arp CellRacThd.GoldServiceArpThd Set this parameter to its

threshold recommended value.
Silver service arp CellRacThd.SilverServiceArpThd Set this parameter to its

threshold recommended value.
Copper Service CellRacThd.CopperServiceArpThld Set this parameter to its

ARP Threshold recommended value.
Gold new service CellRacThd.NewGoldServiceOffset Set this parameter to its

admission recommended value.
threshold offset

eRAN

Name
Silver new CellRacThd.NewSilverServiceOffset Set this parameter to its

service admission recommended value.
threshold offset
Bronze new CellRacThd.NewCopperServiceOffset Set this parameter to its

service admission recommended value.
threshold offset
Iron New Service CellRacThd.NewIronServiceOffset Set this parameter to its

Admission recommended value.
Threshold Offset
Uplink RB used CellRacThd.UlRbHighThd Set this parameter to its

ratio high recommended value.
threshold
Uplink RB used CellRacThd.UlRbLowThd Set this parameter to its

ratio low recommended value.
threshold
Handover CellQciPara.HandoverAdmission- Set this parameter to its

Admission Threshold recommended value.
Threshold
Admission CellRacThd.AdmissionControlPolicy Set this parameter to its

Control Policy recommended value.
4.4.1.2 Using MML Commands
Activation Command Examples (FDD)

//QoS-satisfaction-rate-based admission control
MOD CELLALGOSWITCH: LocalCellId=0, RacAlgoSwitch=DlSwitch-1&UlSwitch-1;
MOD CELLRACTHD: LocalCellId=0, CceUsageThd=80;
Optimization Command Examples

//UE-number-based admission control (when no UE number resources are reserved for
privileged UEs)
MOD CELLRACTHD: LocalCellId=0, AcReservedUserNumber=0, HoReservedUeNumber=0,
AcUserNumber=65535;
//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, CopperServiceArpThld=15, NewIronServiceOffset=5,
AdmissionControlPolicy=VOLTE_UNCONDITIONAL_ADMISSION-0;
MOD CELLQCIPARA: LocalCellId=0, Qci=2, HandoverAdmissionThreshold=90;
Deactivation Command Examples (FDD)

//Disabling UE-number-reservation-based admission control of privileged UEs
MOD CELLRACTHD: LocalCellId=0, AcReservedUserNumber=0;

eRAN
//Disabling QoS-satisfaction-rate-based admission control

MOD CELLALGOSWITCH: LocalCellId=0, RacAlgoSwitch=DlSwitch-0&UlSwitch-0;
4.4.1.3 Using the CME

For detailed operations, see CME-based Feature Configuration.
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 U2020 client, 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-5 lists the methods for calculating the measurement indicators.

eRAN
Table 4-5 Congestion rate calculation

Measurement Formula
Indicator
RRC congestion rate 1 – (L.RRC.ConnReq.Succ –

L.Cell.UserSpec.PrepEmp.PrepAtt.Num –
L.Cell.UserLic.Limit.Num)/L.RRC.ConnReq.Msg
E-RAB congestion 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-6.
Table 4-6 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
1526736856 L.E-RAB.FailEst.NoRadioRes.DLSatis.PTT
1526736857 L.E-RAB.FailEst.NoRadioRes.ULSatis.PTT

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.QCI65
1526748819 L.E-
RAB.FailEst.NoRadioRes.CCELimited.ULSatis.QCI65
1526748822 L.E-
RAB.FailEst.NoRadioRes.CCELimited.DLSatis.QCI66
1526748821 L.E-
RAB.FailEst.NoRadioRes.CCELimited.ULSatis.QCI66

eRAN
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 their 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.
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:
l 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.
l If the InterOpUeNumPreemptSwitch option of the
ENodeBAlgoSwitch.UeNumPreemptSwitch parameter is selected, this UE 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.

eRAN
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.
l If the preemption fails, the UE immediately releases the temporary RRC connection.
l 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.
l When this option is deselected, the number of temporary RRC connections allowed in a
cell is small and is limited by hardware capabilities.
l 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 number of RRC connections in a cell
under the limitation of hardware capabilities – min(CellRacThd.AcUserNumber,
maximum 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:
l 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:

eRAN
– Pre-emption Capability
n 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
n The value of this IE is not pre-emptable, indicating that resources of the UEs
cannot be preempted by other UEs.
– Priority Level
n The value of this IE for emergency CSFB UEs is 1.
n 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.
l 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, this function is enabled, and the eNodeB provides the following
ARP configurations for the default bearers of such UEs:
– Pre-emption Capability
n 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
n The value of this IE is not pre-emptable, indicating that resources of the UEs
cannot be preempted by other UEs.
– Priority Level
n 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.
5.1.2 Service Preemption

As illustrated in 4.1.2 Service Admission Procedure, 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.

eRAN
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 admitted. If
service A is capable of preemption, it can preempt a service B that meets all of the following
conditions:
l Service B is a non-emergency GBR service.
l The value of the ARP IE Pre-emption Vulnerability of service B is pre-emptable.
l The value of the ARP IE Priority Level of service B is greater than that of service A.
l 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:
n The value of the ARP IE Pre-emption Vulnerability of the service is pre-
emptable.
n The service is not an emergency call.
n 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:
l The CellRacThd.AcUserNumber parameter value for a cell is less than the maximum
number of UEs that the cell supports.
l The maximum CPU usages of the main control board and the BBP are less than 60%.
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.
The way the eNodeB performs UE-number-based preemption will increase the amount of
radio signaling because of the following three actions:
l The eNodeB sets up a temporary RRC connection for any UE requesting access to the
eNodeB in order to obtain its ARP attributes.
l The eNodeB releases temporary RRC connections for those UEs that eventually
encounter preemption failures.
l The eNodeB releases RRC connections for UEs which are preempted.
Function Impacts
RAT Function Function Reference Description
Name Switch
FDD Emergency None Emergency Emergency calls are assigned the

call Call highest priority. If the admission
of an emergency call fails,
preemption is performed for the
emergency call.
5.3 Requirements
5.3.1 Licenses
The following are FDD license requirements.

eRAN
RAT Feature ID Feature Name Model Sales Unit
FDD LOFD-001029 Enhanced LT1S000EAC00 per RRC

Admission Control Connected User
5.3.2 Software
feature documents.
RAT Function Name Function Switch Reference
FDD Radio-resource-based UlSwitch and DlSwitch options of Admission and

admission control the Congestion
CellAlgoSwitch.RacAlgoSwitch Control
parameter

None
5.3.3 Hardware
Base Station Models

Enhanced admission control applies to all base station models, except that the following
function does not apply to micro base stations.
When the number of UEs is limited during UE preemption, the eNodeB attempts to set up
temporary RRC connections for UEs that request to access the eNodeB. The number of
temporary RRC connections is increased to give high-priority UEs an opportunity to perform
UE preemption. For details about this function, see 5.1.1 UE Preemption.
Boards
No requirements
RF Modules
No requirements
5.3.4 Networking
None

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

Name
RAC algorithm CellAlgoSwitch.R PreemptionSwit Retain the default value.

switch acAlgoSwitch ch

Name
Preempt CellRacThd.PreResNeedTuningFac- Set this parameter to its

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

eRAN

Name
UE number ENodeBAlgoSwit IntraOpUeNum Retain the default value.

preemption ch.UeNumPreemp PreemptSwitch
switch tSwitch

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

Configuration gSwitch recommended value.
Switch
Normal Csfb CSFallBackPolicyCfg.NormalCsfbUs Set this parameter to its

User Arp erArp recommended value.
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.
Preemption-triggered Redirection
Table 5-5 describes the parameters used for function activation. No parameter is involved in
function optimization.

eRAN

Name
Redirection ENodeBAlgoSwit LoadBasedSwitc In a multi-RAT multi-

switch ch.RedirectSwitch h frequency network, if
LoadRedirectFr preemption is enabled, it is
eqOptSwitch 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
LoadRedirectFreqOptS-
witch 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&InterOpUeNumPreemp
tSwitch-1;
//Preemption-triggered redirection
MOD ENODEBALGOSWITCH:REDIRECTSWITCH=LoadBasedSwitch-1&LoadRedirectFreqOptSwitch-1;

//ARP priority configuration when the number of UEs is limited
MOD CSFALLBACKPOLICYCFG:CsfbUserArpCfgSwitch=ON,NormalCsfbUserArp=2;
//ARP priority configuration for UEs whose RRC connection requests contain the
cause value of mo-Signalling
MOD CELLRACTHD:LocalCellId=0,MoSigArpOverride=2;
//Setting the Preempt Resource Need Tuning Factor parameter
MOD CELLRACTHD:LocalCellId=0,PreResNeedTuningFactor=100;

eRAN
Deactivation Command Examples

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

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

MOD CSFALLBACKPOLICYCFG: CsfbUserArpCfgSwitch=0;
MOD CELLRACTHD: LocalCellId=0, MoSigArpOverride=0;
//Disabling 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 S1AP_ERAB_SETUP_REQ message that includes the ARP priority level and the
preemption attributes
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

eRAN
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 ARP priorities can preempt UEs with low ARP priorities to access
the cell when the number of UEs has reached the licensed value. The verification procedure is
as follows:
Step 1 On the U2020 client, create and start an S1 interface tracing task.
Step 2 Apply for a license in which the number of RRC_CONNECTED UEs is 6, and select the
IntraOpUeNumPreemptSwitch option of the ENodeBAlgoSwitch.UeNumPreemptSwitch
parameter.
Step 3 Use a UE that meets the following requirements to access the network:
l The ARP value for the default bearer is 7.
l The ARP IE Pre-emption Vulnerability is set to pre-emptable for the default bearer.
Step 4 Use another five UEs that meet the following requirements and are served by the same
operator to access the network:
l The ARP IE Pre-emption Vulnerability is set to pre-emptable for the default bearer.
Step 5 Use another UE that meets the following requirements and is served by the same operator to
access the network:
l The IE Pre-emption Capability is set to may trigger pre-emption for the default bearer.
Step 6 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.

eRAN
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 U2020 client, 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 L.Cell.UserLimit.PreEmp.Num
l L.Cell.UserLic.PrepEmp.Succ.Num
l L.Cell.UserLic.PrepEmp.Succ.Num.PLMN
The number of E-RABs that are preempted and then released is counted in the L.E-
RAB.AbnormRel.Cong.PreEmp counter.

eRAN
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:
l 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.
l 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.
l The number of RBs used is not 0.
l 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.
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.

eRAN
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 the user experience deteriorates because of cell congestion, the eNodeB lowers the
scheduling priorities of non-GBR services and decreases the probability of scheduling UEs
with poor signal quality 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:
l Uplink congested
l Downlink congested
l Uplink and downlink congested
l 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:
l 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).
l 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.
– 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 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 such services.

eRAN
The eNodeB determines that a UE is a cell edge UE if the UE reports a CQI value less than
CellRacThd.CqiFarThd after UE filtering or the uplink SINR of the UE 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 8 Counters.
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 cell congestion persists, UEs with poor signal quality
cannot be scheduled, increasing RRC connection setup delay and service drop rate.
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
6.3 Requirements
6.3.1 Licenses
None
6.3.2 Software
feature documents.
None

eRAN

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.

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

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

recommended that this
option be selected.

eRAN

Name
UeExpBasedCon For non-GBR services, it is

gCtrlSw recommended that this
option be selected.
CCE Usage CellRacThd.Cce N/A 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 N/A Set this parameter to its

Threshold gestionThreshold recommended value.
Offset for service CellRacThd.Cong N/A Set this parameter to its

congest relieving RelOffset recommended value.
Uplink RB used CellRacThd.UlRb N/A Set this parameter to its

ratio high HighThd recommended value.
threshold
Uplink RB used CellRacThd.UlRb N/A Set this parameter to its

ratio low LowThd recommended value.
threshold
Redirection ENodeBAlgoSwit LoadBasedSwitc If congestion control is

switch ch.RedirectSwitch h enabled, it is recommended
that this option be selected
to redirect UEs whose RRC
connections are released
due to congestion control to
other frequencies,
preventing these UEs from
experiencing re-access
failures.
LoadRedirectFr If congestion control is

eqOptSwitch enabled, it is recommended
that this option be selected
to prevent UEs from
experiencing ping-pong
redirection among multiple
frequencies.

eRAN
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, UlRbHighThd=95, CceUsageThd=80;
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

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

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


eRAN
Scenario 1: Congestion Control over GBR 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. 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.
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.
During congestion control, the L.LC.ULCong.Dur.Cell and L.LC.DLCong.Dur.Cell

counters measure the uplink congestion duration and downlink congestion duration,
respectively. 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.

eRAN
When congestion control has taken effect, the L.RRCRedirection.IntraLTE counter value
includes the number of redirections if redirections are triggered.

eRAN
Description 7 Parameters
7 Parameters
The following hyperlinked EXCEL files of parameter reference match the software version
with which this document is released.
l Node Parameter Reference: contains device and transport parameters.
l eNodeBFunction Parameter Reference: contains all parameters 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 parameter reference for the software version used on the live network
from the product documentation delivered with that version.
FAQ: 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

eRAN
Description 8 Counters
8 Counters
The following hyperlinked EXCEL files of performance counter reference match the software
version with which this document is released.
l Node Performance Counter Summary: contains device and transport counters.
l 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
Description 9 Glossary
9 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

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

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

Admission and Congestion Control (ERAN15.1 - 01)

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Admission and Congestion Control (ERAN15.1 - 01)

Caricato da

Copyright:

Formati disponibili

eRAN

Admission and Congestion Control

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. i

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

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. ii

5 Enhanced Admission Control................................................................................................... 27

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. iii

6.4.2 Activation Verification.............................................................................................................................................. 46

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. iv

1.1 eRAN15.1 01 (2019-06-06)

1.2 eRAN15.1 Draft B (2019-01-10)

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 1

1.3 eRAN15.1 Draft A (2019-01-05)

Added counters related to E- None FDD l 3900 and 5900

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 2

2 About This Document

2.1 General Statements

l The technical principles of features and their related parameters

2.3 Features in This Document

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 3

Feature ID Feature Name Section

LBFD-002023 Admission Control 4 Admission Control

LOFD-001029 Enhanced Admission 5 Enhanced Admission Control

LOFD-00102901 Radio and Transmission

LBFD-002024 Congestion Control 6 Congestion Control

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 4

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

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 5

4.1.1 UE Admission Procedure

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 6

Figure 4-1 UE admission procedure

The UE admission procedure is as follows:

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 7

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 8

hardware capabilities) minus the sum of

4.1.2 Service Admission Procedure

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 9

Figure 4-2 Service admission procedure

The EmcAdmitCongSwitch option of the CellAlgoSwitch.RacAlgoSwitch parameter takes

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 10

4.1.2.1 Non-GBR Service Admission

4.1.2.2 GBR Service Admission

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 11

Figure 4-3 Downlink admission procedure for GBR services

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 12

Figure 4-4 Uplink admission procedure for GBR services

If the VOLTE_UNCONDITIONAL_ADMISSION option of the

QoS Satisfaction Rate Evaluation

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 13

Downlink QoS Satisfaction Rate Evaluation

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

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 14

Uplink QoS Satisfaction Rate Evaluation

Admission Decision-Making Based on QoS Satisfaction Rates

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 15

These offset values apply to both the uplink and downlink.

l ARP threshold for gold-level services: CellRacThd.GoldServiceArpThd

A service is defined as an iron-level service if its ARP value is greater than

Table 4-1 Mapping between ARP values and service priorities

ARP Value Service