Admission and Congestion Control in HW ERAN8.1

eRAN
Admission and Congestion Control

Feature Parameter Description
Issue 03
Date 2015-11-03
HUAWEI TECHNOLOGIES CO., LTD.

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

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 03 (2015-11-03) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
eRAN
Admission and Congestion Control Feature Parameter
Description Contents
Contents
1 About This Document.................................................................................................................. 1

1.1 Scope.............................................................................................................................................................................. 1
1.2 Intended Audience.......................................................................................................................................................... 1
1.3 Change History............................................................................................................................................................... 2
1.4 Differences Between eNodeB Types.............................................................................................................................. 3
2 Overview......................................................................................................................................... 4
3 LBFD-002023 Admission Control/LOFD-001029 Enhanced Admission Control.............. 5
3.1 User Admission.............................................................................................................................................................. 6
3.2 Service Admission.......................................................................................................................................................... 9
3.2.1 Non-GBR Service Admission....................................................................................................................................11
3.2.2 GBR Service Admission............................................................................................................................................11
3.2.2.1 UE Capability Evaluation....................................................................................................................................... 11
3.2.2.2 Cell Congestion Indication..................................................................................................................................... 11
3.2.2.3 Admission Based on QoS Satisfaction Rates......................................................................................................... 12
3.3 LOFD-00102901 Radio/transport Resource Pre-emption............................................................................................ 17
3.3.1 User Preemption........................................................................................................................................................ 17
3.3.2 Service Preemption....................................................................................................................................................19
3.4 Redirection....................................................................................................................................................................20
4 LBFD-002024 Congestion Control............................................................................................ 21

4.1 Load Status Evaluation................................................................................................................................................. 23
4.2 Release of Low-Priority GBR Services........................................................................................................................23
5 Related Features...........................................................................................................................24
5.1 Features Related to LBFD-002023 Admission Control............................................................................................... 24
5.2 Features Related to LOFD-00102901 Radio/transport Resource Pre-emption............................................................ 24
5.3 Features Related to LBFD-002024 Congestion Control.............................................................................................. 25
6 Network Impact........................................................................................................................... 26
6.1 LBFD-002023 Admission Control............................................................................................................................... 26
6.2 LOFD-00102901 Radio/transport resource pre-emption............................................................................................. 26
6.3 LBFD-002024 Congestion Control.............................................................................................................................. 27
7 Engineering Guidelines............................................................................................................. 28
7.1 When to Use Admission and Congestion Control........................................................................................................28
Issue 03 (2015-11-03) Huawei Proprietary and Confidential ii

eRAN
Description Contents
7.2 Required Information................................................................................................................................................... 28

7.3 Planning........................................................................................................................................................................ 28
7.3.1 RF Planning............................................................................................................................................................... 28
7.3.2 Network Planning...................................................................................................................................................... 28
7.3.3 Hardware Planning.................................................................................................................................................... 29
7.4 Deployment of Admission Control...............................................................................................................................29
7.4.1 Requirements............................................................................................................................................................. 29
7.4.2 Data Preparation........................................................................................................................................................ 29
7.4.3 Activation.................................................................................................................................................................. 36
7.4.4 Activation Observation..............................................................................................................................................41
7.4.5 Deactivation...............................................................................................................................................................44
7.5 Deployment of Congestion Control..............................................................................................................................46
7.5.1 Deployment Requirements........................................................................................................................................ 46
7.5.2 Data Preparation........................................................................................................................................................ 47
7.5.3 Activation.................................................................................................................................................................. 54
7.5.4 Activation Observation..............................................................................................................................................57
7.5.5 Deactivation...............................................................................................................................................................57
7.6 Performance Monitoring...............................................................................................................................................58
7.7 Parameter Optimization................................................................................................................................................ 59
7.8 Troubleshooting............................................................................................................................................................ 60
7.8.1 Admission Control.....................................................................................................................................................60
7.8.2 Congestion Control....................................................................................................................................................60
8 Parameters..................................................................................................................................... 61
9 Counters........................................................................................................................................ 79
10 Glossary..................................................................................................................................... 107
11 Reference Documents............................................................................................................. 108
Issue 03 (2015-11-03) Huawei Proprietary and Confidential iii

eRAN
Description 1 About This Document
1 About This Document
1.1 Scope
This document describes admission and congestion control, including its technical principles,
related features, network impact, and engineering guidelines.
This document covers the following features:
l LBFD-002023 Admission Control

l LOFD-001029 Enhanced Admission Control
l LOFD-00102901 Radio/transport Resource Preemption
l LBFD-002024 Congestion Control
Any managed objects (MOs), parameters, alarms, or counters described herein correspond to
the software release delivered with this document. Any future updates will be described in the
product documentation delivered with future software releases.
This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD,
and "eNodeB" refers to LTE FDD eNodeB.
This document applies to the following types of eNodeBs.
eNodeB Type Model
Macro 3900 series eNodeBs
Micro BTS3202E
LampSite DBS3900 LampSite
1.2 Intended Audience

This document is intended for personnel who:
l Need to understand the features described herein
Issue 03 (2015-11-03) Huawei Proprietary and Confidential 1

eRAN
l Work with Huawei products
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes:
l Feature change
Changes in features and parameters of a specified version as well as the affected entities
l Editorial change
Changes in wording or addition of information and any related parameters affected by
editorial changes. Editorial change does not specify the affected entities.
eRAN8.1 03 (2015-11-03)
This issue includes the following changes.
Change Change Description Parameter Change Affected

Type Entity
Feature None None N/A

change
Editorial Modified monitoring methods None -

change of admission and congestion
control observation. For
details, see the following
sections:
l 7.4.4 Activation
Observation
l 7.5.4 Activation
Observation
eRAN8.1 02 (2015-06-30)
This issue includes the following changes.

Type Entity
Feature None None Macro/

change Micro/
LampSite

eRAN

Type Entity
Editorial Revised descriptions of user- Added the Macro/

change number-based preemption. InterOpUeNumPreemptS- Micro/
For details, see the following witch(InterOpUeNumPree LampSite
sections: mptSwitch) option of the
l 3.3.1 User Preemption ENodeBAlgoSwitch.UeNu
mPreemptSwitch parameter.
l 7.4.2 Data Preparation
l 7.4.3 Activation
l 7.4.5 Deactivation
eRAN8.1 01 (2015-03-23)
This issue does not include any changes.
eRAN8.1 Draft A (2015-01-15)

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

Type r Change
Feature Added performance counters None Macro/Micro/LampSite

change related to admission control and
preemption. For details, see 7.6
Performance Monitoring.
Editorial Revised the description in 2 None -

change Overview.
1.4 Differences Between eNodeB Types

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

eRAN
Description 2 Overview
2 Overview
Introduction
During admission control, an eNodeB decides whether to accept a guaranteed bit rate (GBR)
service request (either new service or handover) based on the physical resource block (PRB)
usage and the quality of service (QoS) satisfaction rate of GBR services. During congestion
control, the eNodeB controls system load to ensure a high overall QoS satisfaction rate and
stable system operation.
Benefits
Load control maintains system stability by rejecting certain admission requests or releasing
some admitted services, while maximizing resource usage. Load control ensures the quality of
admitted services by controlling the cell load. It also provides the required QoS for individual
radio bearers and maximizes cell capacity.

eRAN
Admission and Congestion Control Feature Parameter 3 LBFD-002023 Admission Control/LOFD-001029
Description Enhanced Admission Control
3 LBFD-002023 Admission Control/

LOFD-001029 Enhanced Admission Control
Admission control is categorized into radio-resource-based admission control and transport-

resource-based admission control. This document describes radio-resource-based admission
control. For details about transport-resource-based admission control, see Transport Resource
Management Feature Parameter Description. For details about how to configure this feature,
see 7 Engineering Guidelines.
Radio-resource-based admission control is categorized into user admission and service
admission.
l When a piece of user equipment (UE) requests access to a network, that is, when a UE
requests setup of a radio resource control (RRC) connection or requests an incoming
handover, the E-UTRAN NodeB (eNodeB) performs the user admission procedure.
l When a UE that has accessed a cell requests a new service, that is, when a UE requests
establishment of an E-UTRAN radio access bearer (E-RAB) or requests an incoming
handover, the eNodeB performs the service admission procedure.

eRAN
3.1 User Admission

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

eRAN
Figure 3-1 User admission procedure

eRAN
The user admission procedure is as follows:
1. The eNodeB checks whether the CPU resource is limited. If the CPU resource is limited,
the eNodeB rejects the access request. For details about how the eNodeB checks whether
the CPU resource is limited, see Flow Control Feature Parameter Description.
2. The eNodeB checks whether the sounding reference signal (SRS) resource is
successfully allocated. For details about the SRS resource allocation principle, see
Physical Channel Resource Management Feature Parameter Description. The eNodeB
performs this step differently based on whether LBBPc or BBP of another type is
configured.
l If the LBBPc is configured, the eNodeB performs this step as follows:
– If the SRS resource is configured for the cell, the cell supports uplink timing
measurement using only the SRS. Therefore, if the SRS resource allocation fails,
the uplink timing of the UE may not be accurate and the eNodeB rejects the access
request.
– If the SRS resource is not configured for the cell, the cell supports uplink timing
measurement using the demodulation reference signal (DMRS). Even if the SRS
resource is not allocated, the eNodeB accepts the access request.
l Other types of BBPs support uplink timing measurement using the DMRS. Even if the
SRS resource allocation fails, the uplink timing of the UE is accurate and the eNodeB
does not reject the access request.
NOTE
LampSite eNodeBs do not support the LBBPc.
3. The eNodeB checks whether the PUCCH resource is successfully allocated. If the
PUCCH resource allocation fails, the eNodeB rejects the access request. For details
about the PUCCH resource allocation principle, see Physical Channel Resource
Management Feature Parameter Description.
4. The eNodeB checks whether the number of users is limited. If the number of admitted
users has reached the maximum or the licensed user number, the eNodeB determines that
the number of users is limited and the admission fails.
5. For the user that is admitted by the eNodeB, if the UE requests a service (that is, to
establish an E-RAB), the eNodeB performs the service admission procedure. For details,
see 3.2 Service Admission.
6. If the UE's access request is rejected by the eNodeB, the UE can initiate a user
preemption procedure. For details, see 3.3.1 User Preemption.
NOTE
The number of emergency UEs that can be admitted is restricted only by the maximum number of UEs
supported by the cell rather than by the licensed number of UEs so that emergency UEs can
preferentially be admitted.
In the RAN sharing scenario, the licensed user number varies depending on operators. Therefore, the
eNodeB temporarily allows the access to obtain the PLMN ID to determine whether the licensed user
number is limited. If the licensed user number is limited and the preemption based on user number fails,
the eNodeB rejects the initial context setup request of the temporarily accessed user and releases the
user.
In user admission, UE numbers are reserved for privileged UEs to increase their admission
success rates. Privileged UEs include emergency UEs and high-priority UEs with a
"highPriorityAccess" cause value in an RRC connection establishment request. Other UEs are
common UEs.

eRAN
Privileged UEs are defined because resource preemption is not allowed for operators in some
countries and areas by local regulations but high-priority UEs of these operators need to be
preferentially admitted. The eNodeB determines whether to admit privileged UEs based only
on the maximum number of UEs that can be supported by the cell instead of the licensed user
number. Therefore, user-number-reservation-based admission control can be enabled to
reserve resources for privileged UEs to ensure the preferential admission of privileged UEs.
The UE numbers reserved for privileged UEs are controlled by the
CellRacThd.AcReservedUserNumber parameter.
l If the CellRacThd.AcReservedUserNumber parameter is set to 0, user-number-
reservation-based admission control is disabled. In this case, the eNodeB rejects the
access requests of high-priority UEs and common UEs when the number of admitted
users has reached the licensed user number. The eNodeB rejects the access requests of
both privileged UEs and common UEs when the number of admitted users has reached
the maximum number.
l If the CellRacThd.AcReservedUserNumber parameter is set to a non-zero value, UE
numbers are reserved for privileged UEs. In this case, the eNodeB accepts the access
requests of high-priority UEs but rejects the access requests of common UEs when the
number of admitted users has reached the licensed user number. The eNodeB admits
privileged UEs and common UEs based on different UE number requirements.
– The number of privileged UEs that can be admitted is based on the maximum
number of UEs supported by the cell.
– The number of common UEs that can be admitted is the difference between the
maximum number of UEs supported by the cell and the
CellRacThd.AcReservedUserNumber parameter value. The
CellRacThd.AcReservedUserNumber parameter specifies the UE numbers
reserved for privileged UEs.
If the CellRacThd.AcReservedUserNumber parameter is set to a non-zero value, it is
recommended that SRS resources and PUCCH resources be set to default values. In this case,
neither SRS resources nor PUCCH resources will directly cause user admission failures. It is
recommended that the ARP values of the bearers for UEs whose cause value for an RRC
connection establishment request is "highPriorityAccess" and that for emergency UEs be set
to the same. This ensures the GBR services of these high-priority UEs are directly admitted
successfully.
3.2 Service Admission

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

eRAN
Figure 3-2 Service admission procedure

eRAN
3.2.1 Non-GBR Service Admission

For a non-GBR service, the admission procedure is as follows:
l If the SRS or PUCCH resource allocation fails, the eNodeB rejects the access request.
l If both the SRS resource allocation and the PUCCH resource allocation are successful,
the eNodeB accepts the request. In the admission procedure, the eNodeB does not check
the UE capabilities or whether the cell is congested, or make the admission decision
based on the QoS satisfaction rates.
NOTE
SRS resource allocation is required only if the SRS resource is configured for the LBBPc.
3.2.2 GBR Service Admission

For a GBR service, its QoS has to be guaranteed. The admission procedure is as follows:
l If the SRS or PUCCH resource allocation fails, the eNodeB rejects the access request.
l If both the SRS resource allocation and the PUCCH resource allocation are successful,
the eNodeB makes the admission decision as follows:
– For an emergency call, the eNodeB accepts the request.
– For a non-emergency call, the eNodeB checks the UE capabilities and whether the
cell is congested, and then makes the decision based on the QoS satisfaction rates.
NOTE
SRS resource allocation is required only if the SRS resource is configured for the LBBPc.
3.2.2.1 UE Capability Evaluation

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

Cell congestion indications are provided by congestion control to indicate that the Uu
interface resources are insufficient. There are four types of indications:
l Uplink Congested and Downlink Not Congested

eRAN
l Downlink Congested and Uplink Not Congested

l Uplink and Downlink Congested
l Uplink and Downlink Congestion Cleared
If a GBR service access request arrives, the eNodeB rejects the access request (either new
services or handovers) regardless of whether congestion occurs in the downlink or uplink.
3.2.2.3 Admission Based on QoS Satisfaction Rates

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

eRAN
Figure 3-4 Uplink admission procedure for GBR services
PRB Usage Monitoring

By monitoring the PRB usage of services with high scheduling priorities in the uplink, the
eNodeB learns about the usage of uplink time-frequency resources in the cell and
preliminarily evaluates the cell load. In the uplink, services with high scheduling priorities

eRAN
include GBR services and the signaling and services whose scheduling priorities are higher
than GBR services, such as retransmissions, signaling radio bearers (SRBs), and scheduling
requests (SRs). The Media Access Control (MAC) layer calculates the PRB usage using the
following formula:
After filtering, the eNodeB compares the calculated PRB usage with the uplink PRB usage
thresholds CellRacThd.UlRbHighThd and CellRacThd.UlRbLowThd and then determines the
PRB usage status. Using both the upper and lower thresholds prevents a possible ping-pong
effect.
Evaluation of the Wait Time for Uplink Scheduling of VoIP Services

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

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

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

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

Services with QCIs 2 to 4 are GBR services. The downlink QoS satisfaction rate of GBR
services with QCI 2, 3, or 4 is calculated by using the following formula:
where
i = 2, 3, or 4
NOTE
Section 6.1.7 in 3GPP TS 23.203 V11.6.0 (2012-06) provides an example mapping between QCIs and
service types but does not provide definitions of the mapping. Huawei implements the mapping
according to the examples, where QCI 1 represents VoIP services.
Evaluation of Uplink QoS Satisfaction Rates

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

eRAN
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 Based on QoS Satisfaction Rates

The admission threshold for handovers is lower than that for new services. The eNodeB
defines four handover thresholds QcixHoThd (x = 1–4) for the QCIs. Based on the handover
thresholds, service differentiation can be achieved by setting admission offsets for new gold-,
silver-, and bronze-level services, based on the mapping between ARP values and service
priorities. The admission offsets are CellRacThd.NewGoldServiceOffset,
CellRacThd.NewSilverServiceOffset, and CellRacThd.NewCopperServiceOffset. These
offset values apply to both the uplink and downlink.
The eNodeB categorizes services based on their ARP values. The ARP values are mapped to
three service priorities: gold, silver, and bronze. The mapping can be adjusted by setting
CellRacThd.GoldServiceArpThd (the ARP threshold for gold-level services) or
CellRacThd.SilverServiceArpThd (the ARP threshold for silver-level services). The ARP
values beyond the ranges defined by these two parameters correspond to bronze-level
services. A small ARP value indicates a high priority level. Table 3-1 shows a typical
mapping between the ARP values and the service priorities.
Table 3-1 Typical mapping between the ARP values and the service priorities
ARP Value Service Priority
1–5 Gold
6–10 Silver
11–15 Bronze
For details about ARPs, see section 4.7.3 in 3GPP TS 23.401 V10.8.0 (2012-06).
For GBR services whose QCIs range from 1 to 4, the admission thresholds for handovers and
new services corresponding to a QCI are as follows:
l The admission threshold for handovers is QcixHoThd.

l The admission threshold for new gold-level services is QcixHoThd plus
CellRacThd.NewGoldServiceOffset.
l The admission threshold for new silver-level services is QcixHoThd plus
CellRacThd.NewSilverServiceOffset.
l The admission threshold for new bronze-level services is QcixHoThd plus
CellRacThd.NewCopperServiceOffset.
The relationship between these thresholds is as follows:
QcixHoThd ≤ QcixHoThd + CellRacThd.NewGoldServiceOffset ≤ QcixHoThd +

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

eRAN
l For SQCI = x ≥ QcixHoThd + CellRacThd.NewCopperServiceOffset

If the QoS satisfaction rates of all QCIs except QCI x are higher than the corresponding
handover admission thresholds, then the eNodeB accepts requests for new gold-, silver-,
and bronze-level services and handovers with QCI x.
If the QoS satisfaction rate of any QCI is lower than the corresponding handover
admission threshold, then the eNodeB rejects requests for new gold-, silver-, and bronze-
level services with QCI x but accepts requests for incoming handovers with QCI x.
l For QcixHoThd + CellRacThd.NewCopperServiceOffset > SQCI = x ≥ QcixHoThd +
CellRacThd.NewSilverServiceOffset
handover admission thresholds, then the eNodeB accepts requests for new gold- and
silver-level services and handovers with QCI x but rejects requests for new bronze-level
services with QCI x.
l For QcixHoThd + CellRacThd.NewSilverServiceOffset > SQCI = x ≥ QcixHoThd +
CellRacThd.NewGoldServiceOffset
handover admission thresholds, then the eNodeB accepts requests for new gold-level
services and handovers with QCI x but rejects requests for new silver- and bronze-level
services with QCI x.
l For QcixHoThd + CellRacThd.NewGoldServiceOffset > SQCI = x ≥ QcixHoThd
The eNodeB rejects requests for new gold-, silver-, bronze-level services with QCI x but
accepts requests for handovers with QCI x.
l For QcixHoThd > SQCI = x
The eNodeB rejects requests for new services and handovers with QCI x.
The rules for uplink admission evaluation are similar to the rules for downlink admission
evaluation. The difference is that the eNodeB evaluates the QoS satisfaction rates of logical
channel groups when admitting GBR services in the uplink. For details, see Evaluation of
Uplink QoS Satisfaction Rates.
3.3 LOFD-00102901 Radio/transport Resource Pre-emption

For details about transport resource preemption, see Transport Resource Management Feature
Parameter Description.
3.3.1 User Preemption

When an emergency UE accesses the network and fails to be allocated SRS or PUCCH
resources, the UE preempts the resources of the common UE in the synchronization state and
with the lowest ARP in the same cell. If the common UE has multiple services with different
ARPs, the highest ARP is considered as the ARP of the UE.

eRAN
When a UE with a high ARP or an emergency UE attempts to access to the network and the
eNodeB rejects the access attempt due to the limited number of UEs:
l If the IntraOpUeNumPreemptSwitch(IntraOpUeNumPreemptSwitch) option of the

ENodeBAlgoSwitch.UeNumPreemptSwitch parameter is selected, this UE preempts the
resources of common UEs with low ARPs served by the same operator. The preemption
is not allowed if this option is deselected.
l If the InterOpUeNumPreemptSwitch(InterOpUeNumPreemptSwitch) option of the
ENodeBAlgoSwitch.UeNumPreemptSwitch parameter is selected, this UE preempts the
resources of common UEs with low ARPs served by different operators. The preemption
is not allowed if this option is deselected.
NOTE
In the user-number-based preemption, the eNodeB establishes a temporary RRC connection for any UE
requesting access to the eNodeB in order to obtain the UE's ARP attributes.
In the user-number-based preemption, the resources for the following types of low-ARP UEs
are preempted in descending order of priority:
l Low-ARP UEs in the out-of-synchronization state performing non-GBR services

l Low-ARP UEs in the out-of-synchronization state performing GBR services
l Low-ARP UEs in the synchronized state performing non-GBR services
l Low-ARP UEs in the synchronized state performing GBR services
If the preemption succeeds and redirection is enabled, the eNodeB performs a redirection for
the UE whose resource is preempted. If the preemption request is rejected and redirection is
enabled, the eNodeB performs a redirection for the UE that requests preemption. For details
about redirection procedure, see 3.4 Redirection.
The ARP value of a bearer of a UE is generally allocated by the EPC. The EPC allocates a
low ARP value for the bearer of a CSFB UE. When the licensed number of UEs is limited,
such a UE fails to preempt resources and then experiences an admission failure.
CSFB UEs can be classified as 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.
You can set the CsFallbackPolicyCfg.CsfbUserArpCfgSwitch parameter to increase the ARP

values of bearers for CSFB UEs. The IEs contained in the ARP values of default bearers for
CSFB UEs are configured as follows:
l Pre-emption Capability
– The value of this IE for CSFB UEs is may trigger pre-emption, indicating that the
UEs can preempt resources of other low-priority UEs.
l Pre-emption Vulnerability
– The value of this IE for CSFB UEs is not pre-emptable, indicating that resources
of the UEs cannot be preempted by other UEs.
l Priority Level
– The value of this IE for emergency CSFB UEs is 1.
– The ARP IE priority level for common CSFB UEs can be specified by the
CsFallbackPolicyCfg.NormalCsfbUserArp parameter.

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

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

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 If service B is a GBR service, the resources allocated to it are greater than or equal to the
resources required by GBR service A.
Preemption fails if any one of the preceding conditions is not met. If none of the GBR
services of a UE is admitted or preemption for all GBR services of a UE fails, the UE is
redirected if redirection is enabled. For details about operations related to redirection, see 3.4
Redirection.
NOTE
A service whose ARP value is 15 can neither preempt other services nor be preempted by other services.
For details, see section 9.2.1.60 in 3GPP TS 36.413 V10.6.0 (2012-06).
During the preemption procedure, the eNodeB first groups GBR services with low priorities
and then selects services that can be preempted from this group. The procedure is as follows:
1. The eNodeB groups the GBR services with low priorities.
The eNodeB first selects releasable GBR services and then groups the services with the
lowest priorities among them. A releasable GBR service must meet the following
conditions:
– The value of the ARP IE "pre-emption vulnerability" of the service is "pre-
emptable".
– The service is not an emergency call.
– The service rate is not 0.
The eNodeB sorts these GBR services based on the following rule: The service with
the largest value of the ARP IE "priority level" has the lowest priority and ranks

eRAN
first. If two services have the same "priority level" value, the service that occupies
more PRBs ranks ahead of the other.
2. The eNodeB selects services to be preempted.
The eNodeB estimates the number of PRBs required by a preempting service based on
the average spectral efficiency of the cell. The eNodeB calculates the number of PRBs
released from the group of GBR services with low priorities. The calculation stops after
the number of released PRBs meets the requirements of the preempting service. The
preemption fails if no service can be preempted or the number of PRBs released from ten
preempted services does not meet the requirements of the preempting service.
If the GBR service to be preempted is the only GBR service on a UE, the UE can be
redirected when redirection is enabled. For details about redirection, see 3.4
Redirection.
3.4 Redirection
During a redirection, the eNodeB sends the UE an RRCConnectionRelease message that
includes the target frequency information for the redirection. Redirection is enabled if
LoadBasedSwitch under the ENodeBAlgoSwitch.RedirectSwitch parameter is on.
The eNodeB selects the target frequency as follows:
l If a subscriber profile ID (SPID) has been specified for the UE, the eNodeB determines
the UE-supported RATs and frequency bands and checks for the mapping between
frequencies and priorities in the associated SPID configuration. The eNodeB then selects
the highest-priority frequency except the serving frequency as the target frequency. For
details about SPIDs, see Flexible User Steering Feature Parameter Description.
l If an SPID is not specified for the UE or frequency priorities are not set in the SPID
configuration for the UE, the eNodeB considers the operator-specific dedicated cell-
reselection priorities for frequencies. Among the UE-supported frequency bands, the
eNodeB selects the highest-priority frequency except the serving frequency as the target
frequency. The priorities are specified in the EutranNFreqRanShare, UtranRanShare,
and GeranRanShare MOs or in the EutranNFreqSCellOp, UtranNFreqSCellOp,
GeranNFGroupSCellOp, and Cdma2000BcSCellOp MOs.
l If an SPID is not specified for the UE or frequency priorities are not set in the SPID
configuration for the UE, and if operator-specific dedicated cell-reselection priorities are
not specified, the eNodeB considers common cell-reselection priorities. Among the UE-
supported frequency bands, the eNodeB selects the highest-priority frequency except the
serving frequency as the target frequency. The priorities are specified in the
EutranInterNFreq, UtranNFreq, and GeranNfreqGroup MOs.
NOTE
If the admission fails for a UE requesting a handover, the UE cannot be redirected to another cell.

eRAN
Description 4 LBFD-002024 Congestion Control
4 LBFD-002024 Congestion Control
Congestion control reduces congestion caused by an insufficiency of radio resources or

transport resources. This document describes only the former. For details about the latter, see
Transport Resource Management Feature Parameter Description.
Congestion can be prevented in most cases if admission control is performed. However,
congestion may occur in the following cases:
l The services are diverse and the data rates of certain services vary significantly.
Variations in the data volume inevitably affect the cell load.
l The radio conditions vary because of user mobility. The same service at the same data
rate may require different radio resources on different occasions.
In these two cases, the cell load varies and the quality of admitted services gets affected, even
if the number of users in the cell does not change. The congestion control algorithm is
required to handle possible congestion.
Figure 4-1 shows the congestion control process. Congestion control is enabled if the
DlLdcSwitch(dlLdcSwitch) or UlLdcSwitch(ulLdcSwitch) check box under the
CellAlgoSwitch.RacAlgoSwitch parameter is selected.

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

eRAN
4.1 Load Status Evaluation

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

f a cell is congested, congestion control selects a service that ranks the first in the group of
admitted low-priority GBR services and releases the selected service.
If the only GBR service on the selected UE is released and redirection is enabled, the eNodeB
redirects the UE to another frequency or RAT, increasing the access success rate of the UE.
For details about redirection, see 3.4 Redirection.
After the GBR service is released, the eNodeB checks whether the QoS satisfaction rates of
GBR services are restored. If the QoS satisfaction rates of GBR services are not restored, the
eNodeB performs the GBR service release procedure again until the congestion is relieved.

eRAN
Description 5 Related Features
5 Related Features
5.1 Features Related to LBFD-002023 Admission Control

Prerequisite Features
None
Mutually Exclusive Features

None
Impacted Features
None
5.2 Features Related to LOFD-00102901 Radio/transport

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

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

eRAN
Description 5 Related Features
5.3 Features Related to LBFD-002024 Congestion Control

None

None
Impacted Features
None

eRAN
Description 6 Network Impact
6 Network Impact
6.1 LBFD-002023 Admission Control

System Capacity
The admission control algorithm maximizes system capacity while satisfying the QoS
requirements of admitted services. For example, if the QoS satisfaction rate of GBR services
is low, new services cannot be admitted and preemption will be triggered. System capacity
can be maximized on condition that the QoS requirements are satisfied.
Network Performance
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.
6.2 LOFD-00102901 Radio/transport resource pre-emption

System Capacity
No impact.
Network Performance
Preemption increases the access success rate for users with high ARPs. However, users with
low ARPs are forcibly released and their service drop rate increases.
The way the eNodeB performs user-number-based preemption will increase the amount of
radio signaling because of the following three actions:
l The eNodeB establishes a temporary RRC connection for any UE requesting access to
the eNodeB in order to obtain its ARP attributes.

eRAN
Description 6 Network Impact
l The eNodeB releases temporary RRC connections for those UEs that eventually
encounter preemption failures.
l The eNodeB releases RRC connections for preempted UEs.
6.3 LBFD-002024 Congestion Control

System Capacity
The congestion control algorithm maximizes system capacity while preferentially satisfying
the QoS requirements of users with high ARPs. When congestion occurs, the congestion
control algorithm informs the admission control algorithm. Then, the admission control
algorithm starts to reject access requests.
Network Performance
The congestion control algorithm increases the service drop rate because the congestion-
control-triggered releases of users are regarded as service drops. Counters are provided to
indicate congestion-triggered service drops. For details about the counters, see 9 Counters.

eRAN
Description 7 Engineering Guidelines
7 Engineering Guidelines
7.1 When to Use Admission and Congestion Control

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

For both admission control and congestion control, collect the QoS satisfaction rates and
uplink PRB usage of cells.
7.3 Planning
7.3.1 RF Planning
N/A
7.3.2 Network Planning

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

eRAN
7.3.3 Hardware Planning

N/A
7.4 Deployment of Admission Control
7.4.1 Requirements
Feature
For details, see 5.1 Features Related to LBFD-002023 Admission Control in the section
"Impacted Features".
Hardware
None
License
The required licenses for the Enhanced Admission Control feature must be activated before
service preemption is enabled.
The operator must purchase and activate the licenses of the features listed in the following
table.
Feature ID Feature Model License NE Sales Unit

Name Control Item
LOFD-00102 Enhanced LT1S000 Enhanced Macro per RRC

9 Admission EAC00 Admission eNodeB/ Connected
Control Control (FDD) LampSite User
eNodeB/
BTS3202E
Other Requirements
As required by congestion control, the preemption capability and vulnerability must be
specified in the EPC for services with different priorities.
7.4.2 Data Preparation

This section describes the data that you need to collect for setting parameters. Required data is
data that you must collect for all scenarios. Collect scenario-specific data when necessary for
a specific feature deployment scenario.
There are three types of data sources:
l Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment

eRAN
l Network plan (negotiation not required): parameter values planned and set by the
operator
l User-defined: parameter values set by users
Required Data
N/A
Scenario-specific Data
Scenario 1: Admission Based on QoS Satisfaction Rates
The following table describes the parameters that must be set in the CellAlgoSwitch MO to
enable admission based on QoS satisfaction rates.
Parameter Paramet Data Setting Notes

Name er ID Source
Local cell CellAlgo Network This parameter specifies the local ID of a cell. It
ID Switch.L plan uniquely identifies a cell within an eNodeB. Set
ocalCellI (negotiation this parameter based on the network plan.
d not
required)
RAC CellAlgo Network l To enable downlink admission based on QoS

algorithm Switch.R plan satisfaction rates, select the
switch acAlgoS (negotiation DlSwitch(dlCacSwitch) option.
witch not l To disable downlink admission based on QoS
required) satisfaction rates, deselect the
DlSwitch(dlCacSwitch) option.
Network l To enable uplink admission based on QoS

plan satisfaction rates, select the
(negotiation UlSwitch(ulCacSwitch) option.
not l To disable uplink admission based on QoS
required) satisfaction rates, deselect the
UlSwitch(ulCacSwitch) option.
The following table describes the parameters that must be set in the CellRacThd MO to
configure admission based on QoS satisfaction rates.

Name er ID Source
Local cell CellRac Network This parameter specifies the local ID of a cell. It
ID Thd.Loc plan uniquely identifies a cell within an eNodeB. Set
alCellId (negotiation this parameter based on the network plan.
not
required)

eRAN

Name er ID Source
Gold CellRac Network This parameter specifies the ARP threshold for
service arp Thd.Gol plan gold-level services. A service is defined as a
threshold dService (negotiation gold-level service if its ARP value is less than or
ArpThd not equal to this parameter value.
required) A smaller ARP value indicates a higher priority.
The value 5 is recommended.
Silver CellRac Network This parameter specifies the ARP threshold for
service arp Thd.Silv plan silver-level services. A service is defined as a
threshold erService (negotiation silver-level service if its ARP value is less than or
ArpThd not equal to this parameter value and greater than the
required) value of CellRacThd.GoldServiceArpThd.
A service is defined as a bronze-level service if
its ARP value is greater than the value of
CellRacThd.SilverServiceArpThd. A smaller
ARP value indicates a higher priority.
QCI1 CellRac Network This parameter specifies the handover admission

handover Thd.Qci plan threshold for QCI 1. The parameter applies to
admission 1HoThd (negotiation both uplink and downlink.
threshold not l If the QoS satisfaction rate of services with a
required) QCI of 1 in the cell is higher than or equal to
this threshold, handover services with a QCI
of 1 are admitted.
l If the QoS satisfaction rate of these services is
lower than this threshold, handover services
with a QCI of 1 are not admitted.

of 2 are admitted.

eRAN

Name er ID Source

of 3 are admitted.

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

eRAN

Name er ID Source
Silver new CellRac Network This parameter specifies admission offset for new
service Thd.New plan silver-level services. The parameter applies to
admission SilverSer (negotiation both uplink and downlink.
threshold viceOffse not l New silver-level services and handover
offset t required) services with a specific QCI are admitted if
thresholds.
l New services with a specific QCI are not
admitted if the QoS satisfaction rate of any
QCI is lower than the corresponding handover
admission threshold.
Bronze new CellRac Network This parameter specifies admission offset for new
service Thd.New plan bronze-level services. The parameter applies to
admission CopperS (negotiation both uplink and downlink.
threshold erviceOff not l New bronze-level services and handover
offset set required) services with a specific QCI are admitted if
thresholds.
l New services with a specific QCI are not
admitted if the QoS satisfaction rate of any
QCI is lower than the corresponding handover
admission threshold.
Uplink RB CellRac Network This parameter specifies the threshold for

used ratio Thd.UlR plan deciding whether the uplink RB usage is high.
high bHighTh (negotiation This threshold is used in uplink admission
threshold d not decisions. If the MAC layer reports that the
required) uplink RB usage is greater than this parameter
value, the uplink RB usage is regarded to be
high.

eRAN

Name er ID Source
Uplink RB CellRac Network This parameter specifies the threshold for

used ratio Thd.UlR plan deciding whether the uplink RB usage is low.
low bLowThd (negotiation This threshold is used in uplink admission
threshold not decisions. If the MAC layer reports that the
required) uplink RB usage is less than this parameter value,
the uplink RB usage is regarded to be low.
Scenario 2: Service Preemption
This section describes data preparation for radio resource preemption. For details about data
preparation for transport resource preemption, see Transport Resource Management Feature
Parameter Description.
Before collecting the parameters for enabling and configuring service preemption, collect the
parameters in the CellAlgoSwitch MO for enabling admission based on QoS satisfaction
rates. For the parameters for enabling admission based on QoS satisfaction rates, see scenario
1.
The following table describes the parameters that must be set in the CellAlgoSwitch MO to
enable service preemption.
Parameter Parame Data Setting Notes

Name ter ID Source
Local cell ID CellAlg Network This parameter specifies the local ID of a cell. It
oSwitch plan uniquely identifies a cell within an eNodeB. Set
.LocalC (negotiation this parameter based on the network plan.
ellId not
required)
RAC CellAlg Network PreemptionSwitch(PreemptionSwitch) of this

algorithm oSwitch plan parameter specifies whether to enable service
switch .RacAlg (negotiation preemption.
oSwitch not l If the
required) PreemptionSwitch(PreemptionSwitch)
option is selected, new higher-priority
services that have failed to be admitted can
preempt the admitted lower-priority services
in the cell.
l If the
PreemptionSwitch(PreemptionSwitch)
option is deselected, only emergency calls
can be admitted to the cell.
Scenario 3: User-Number-based Preemption

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

Name er ID Source
UE number EnodeB Network This parameter specifies whether to enable user-

preemption AlgoSwit plan number-based preemption.
switch ch.UeNu (negotiatio l IntraOpUeNumPreemptSwitch: This option
mPreemp n not specifies whether to enable intra-operator user-
tSwitch required) number-based preemption. If the
IntraOpUeNumPreemptSwitch option is
selected, when a user cannot access the
network because of the user number
restriction, the user can preempt resources of
other lower-priority users served by the same
operator. If this option is deselected,
preemption is not allowed.
l InterOpUeNumPreemptSwitch: This option
specifies whether to enable inter-operator user-
number-based preemption. If the
InterOpUeNumPreemptSwitch option is
selected, when a user cannot access the
network because of the user number
restriction, the user can preempt resources of
other lower-priority users served by different
operators. If this option is deselected,
preemption is not allowed.
Scenario 4: User-Number-Reservation-based Admission Control of Privileged UEs
The following table describes the parameter that must be set in the CellRacThd MO to enable
user-number-reservation-based admission control of privileged UEs.

Name er ID Source
Admission CellRac Network This parameter specifies the UE numbers reserved

Control Thd.AcR plan for privileged UEs. If this parameter is set to 0, no
Reserved eservedU (negotiatio UE numbers are reserved for privileged UEs. A
User serNumb n not non-zero value of this parameter indicates the
Number er required) maximum UE numbers reserved for privileged
UEs. A larger value of this parameter indicates a
larger UE number reserved for privileged UEs and
a smaller UE number available for common UEs.
Scenario 5: ARP Configuration for Common UEs Initiating CSFB Procedures

eRAN
The following table describes the parameters that must be set in the CSFallBackPolicyCfg
MO to configure ARPs for common UEs initiating CSFB procedures.
Parameter Parameter ID Data Source Setting Notes

Name
Csfb User CSFallBackPolic Network plan This parameter specifies whether

Arp yCfg.CsfbUserAr (negotiation not the ARPs for common UEs
Configurati pCfgSwitch required) initiating CSFB procedures can be
on Switch configured.
The value OFF(Off) is
recommended.
Normal CSFallBackPolic Network plan This parameter specifies the ARP

Csfb User yCfg.NormalCsfb (negotiation not for common UEs initiating CSFB
Arp UserArp required) procedures. If this parameter is set
to 1, the ARP for these UEs is the
same as that for emergency UEs
initiating CSFB procedures.
7.4.3 Activation
Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
Enter the values of the parameters listed in Table 7-1, Table 7-2, Table 7-3, Table 7-4, or
Table 7-5 in a summary data file, which also contains other data for the new eNodeBs to be
deployed. Then, import the summary data file into the Configuration Management Express
(CME) for batch configuration. For detailed instructions, see "Creating eNodeBs in Batches"
in the initial configuration guide for the eNodeB, which is available in the eNodeB product
documentation.
The summary data file may be a scenario-specific file provided by the CME or a customized
file, depending on the following conditions:
l The managed objects (MOs) in Table 7-1, Table 7-2, Table 7-3, Table 7-4, or Table 7-5
are contained in a scenario-specific summary data file. In this situation, set the
parameters in the MOs, and then verify the parameter settings and save the file.
l Some MOs in Table 7-1, Table 7-2, Table 7-3, Table 7-4, or Table 7-5 are not contained
in a scenario-specific summary data file. In this situation, customize a summary data file
to include the MOs before setting the parameters.
Table 7-1 Parameters for admission based on QoS satisfaction rates
MO Sheet in the Parameter Group Remarks

Summary Data
File
CellAlgoS CellAlgoSwitch Local cell ID, RAC algorithm User-defined

witch switch template

eRAN

Summary Data
File
CellRacTh CellRacThd Local cell ID, Gold service arp User-defined

d threshold, Silver service arp template
threshold, QCI1 handover
admission threshold (%), QCI2
handover admission threshold (%),
QCI3 handover admission
threshold (%), QCI4 handover
admission threshold (%), Gold new
service admission threshold offset
(%), Silver new service admission
threshold offset (%), Copper new
service admission threshold offset
(%), Uplink RB used ratio high
threshold(%), Uplink RB used ratio
low threshold (%)
Table 7-2 Parameters for service preemption

Summary Data
File
CellAlgoSwitch CellAlgoSwitch Local cell ID, RAC User-defined

algorithm switch template

eRAN

Summary Data
File
CellRacThd CellRacThd Local cell ID, Gold User-defined

service arp threshold, template
Silver service arp
threshold, QCI1
handover admission
threshold (%), QCI2
handover admission
threshold (%), QCI3
handover admission
threshold(%), QCI4
handover admission
threshold(%), Gold
new service admission
threshold offset(%),
Silver new service
admission threshold
offset(%), Copper new
service admission
threshold offset(%),
Uplink RB used ratio
high threshold(%),
Uplink RB used ratio
low threshold(%)
Table 7-3 Parameters for UE-number-based preemption

Summary Data
File
EnodeBAlgoSwitc ENodeBAlgoSwitch UE number preemption User-defined

h switch template
Table 7-4 Parameters for admission control of privileged UEs based on reserved resources
Summary Data
File
CellRacThd CellRacThd Admission Control User-defined

Reserved User template
Numbers

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

Summary Data
File
CsFallbackPolicyC CsFallbackPolicyCf Csfb User Arp User-defined

fg g Configure Switch, template
Normal Csfb User Arp
Using the CME to Perform Batch Configuration for Existing eNodeBs

Batch reconfiguration using the CME is the recommended method to activate a feature on
existing eNodeBs. This method reconfigures all data, except neighbor relationships, for
multiple eNodeBs in a single procedure. The procedure is as follows:
Step 1 Customize a summary data file with the MOs and parameters listed in section "Using the
CME to Perform Batch Configuration for Newly Deployed eNodeBs". For online help, press
F1 when a CME window is active, and choose Managing the CME > CME Guidelines >
LTE Application Management > eNodeB Related Operations > Customizing a Summary
Data File for Batch eNodeB Configuration.
Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk
Configuration Data (U2000 client mode), or choose LTE Application > Export Data >
Export Base Station Bulk Configuration Data (CME client mode), to export eNodeB data
stored on the CME into a customized summary data file.
Step 3 In the summary data file, set the parameters in the MOs according to the setting notes
provided in section "Data Preparation" and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk
Configuration Data (U2000 client mode), or choose LTE Application > Import Data >
Import Base Station Bulk Configuration Data (CME client mode), to import the summary
data file into the CME, and then start the data verification.
Step 5 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or
choose Area Management > Planned Area > Export Incremental Scripts (CME client
mode), to export and activate the incremental scripts. For detailed operations, see Managing
the CME > CME Guidelines > Script File Management > Exporting Incremental Scripts
from a Planned Data Area in the CME online help.
----End
Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB.
The procedure is as follows:
Step 1 In the planned data area, click Base Station in the upper left corner of the configuration
window.
Step 2 In area 1 shown in Figure 7-1, select the eNodeB to which the MOs belong.

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

Step 1 Run the MOD CELLALGOSWITCH command to enable uplink and downlink admission
control based on QoS satisfaction rates.
Step 2 Run the MOD CELLRACTHD command to configure admission control.
----End
Step 1 Run the MOD CELLALGOSWITCH command to enable uplink and downlink admission
control based on QoS satisfaction rates, and then to enable service preemption.
Step 2 Run the MOD CELLRACTHD command to configure admission control.
----End
Scenario 3: User-Number-based Preemption

eRAN
Run the MOD ENODEBALGOSWITCH command to enable user-number-based

preemption.
Scenario 4: Admission Control of Privileged UEs Based on Reserved Resources
Run the MOD CELLRACTHD command to set the number of UEs reserved for admission
control.
Scenario 5: ARP Configuration for Common UEs Initiating CSFB Procedures When the
Number of UEs to Be Admitted Is Limited
Run the MOD CSFALLBACKPOLICYCFG command to turn on the switch for

configuring ARP for common UEs initiating CSFB procedures and to configure the ARPs for
common UEs initiating CSFB procedures.
MML Command Examples

l Enabling Admission Control Based on QoS Satisfaction Rates
MOD CELLALGOSWITCH: LocalCellId=0, RacAlgoSwitch=DlSwitch-1&UlSwitch-1;
l Enabling Service Preemption

MOD CELLALGOSWITCH: LocalCellId=0, RacAlgoSwitch=PreemptionSwitch-1;
l Configuring Admission Control

MOD CELLRACTHD: LocalCellId=0, GoldServiceArpThd=5, SilverServiceArpThd=10,
Qci1HoThd=80, Qci2HoThd=80, Qci3HoThd=80, Qci4HoThd=80,
NewGoldServiceOffset=5, NewSilverServiceOffset=5, NewCopperServiceOffset=5,
UlRbHighThd=90, UlRbLowThd=80;
l Enabling User-Number-based Preemption

MOD
ENODEBALGOSWITCH:UeNumPreemptSwitch=IntraOpUeNumPreemptSwitch-1&InterOpUeNumPr
eemptSwitch-1;
l Enabling Admission Control of Privileged UEs Based on Reserved Resources

MOD CELLRACTHD:LocalCellId=0,AcReservedUserNumber=15;
l Enabling ARP Configuration for Common UEs Initiating CSFB Procedures When
the Number of UEs to Be Admitted Is Limited
MOD CSFALLBACKPOLICYCFG:CSFBUSERARPCFGSWITCH=ON,NORMALCSFBUSERARP=2;
7.4.4 Activation Observation

Step 1 On the U2000 client, start S1 interface tracing and start monitoring on the following items:
QoS satisfaction rate, RB usage, and the number of services.
1. Choose Monitor > Signaling Trace > Signaling Trace Management.
2. In the navigation tree on the left of the Signaling Trace Management window:
– Choose LTE > Application Layer > S1 Interface Trace to create an S1 interface
tracing task.
– Choose LTE > Cell Performance Monitoring > Satisfaction of Service
Monitoring to create a task for monitoring QoS satisfaction rates.
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, which can be
monitored based on Congestion State in the monitoring results.

eRAN
Step 3 Initiate new GBR services with a QCI in the range of 2 to 4. These new GBR service requests
are rejected in admission based on QoS satisfaction rates.
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
7-2, or if the number of services does not increase with the S1AP_ERAB_SETUP_REQ
messages, the new GBR service requests have been rejected.
Figure 7-2 S1AP_ERAB_SETUP_RSP message that indicates failed admission based on

satisfaction rates
----End

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

eRAN
tracing task.
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
for scenario 1 in this section so that requests for GBR service A are first rejected due to
admission based on QoS satisfaction rates. Initiate new GBR service A. Preemption principles
specify that high-priority services can be admitted based on the preemption of low-priority
services, so that 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, as shown in Figure 7-4. GBR service A is successfully set up.
Figure 7-4 S1AP_ERAB_REL_IND message that indicates successful preemption
----End
Scenario 3: Intra-Operator User-Number-based Preemption

If user-number-based preemption is enabled and all users can both be preempted and preempt
other users, users with high ARPs can preempt users with low ARPs to access the cell when
the number of users has reached the licensed value. The verification procedure is as follows:
Step 1 On the U2000 client, choose Monitor > Signaling Trace > Signaling Trace Management.
Step 2 In the navigation tree on the left of the Signaling Trace Management window, choose LTE
> Application Layer > S1 Interface Trace to create an S1 interface tracing task.
Step 3 Apply for a license in which the number of RRC_CONNECTED users is 6, and select the
IntraOpUeNumPreemptSwitch(IntraOpUeNumPreemptSwitch) option.
Step 4 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 5 Use another five UEs that meet the following requirements to access the network:
l The UEs and the previous UE are served by the same operator.
l The ARP IE "pre-emption vulnerability" is set to pre-emptable for the default bearer.
Step 6 Enable another UE that meets the following requirements to access the network:
l The UE and the previous UEs are served by the same operator.
l The ARP IE "pre-emption capability" is set to may trigger pre-emption for the default
bearer.

eRAN
Step 7 Monitor S1 signaling to verify that the resources allocated to the first UE are preempted and
the first UE is released, as shown in Figure 7-5.
Figure 7-5 S1AP_UE_ CONTEXT_REL_REQ message that indicates successful preemption
----End
7.4.5 Deactivation
Using the CME to Perform Batch Configuration
Batch reconfiguration using the CME is the recommended method to deactivate a feature on
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for
feature activation described in Using the CME to Perform Batch Configuration for
Existing eNodeBs. In the procedure, modify parameters according to Table 7-6, Table 7-7,
Table 7-8, Table 7-9, and Table 7-10.
Table 7-6 Parameters for admission based on QoS satisfaction rates

MO Sheet in the Parameter Setting Notes
Summary Data File Group
CellAlgoSwitch CellAlgoSwitch Local cell Turn off the switches that

ID, RAC control admission control
algorithm based on satisfaction rates.
switch
Table 7-7 Parameters for service preemption

MO Sheet in the Summary Parameter Group Setting Notes
Data File
CellAlgoSwitch CellAlgoSwitch Local cell ID, RAC Turn off the

algorithm switch service preemption
switch.

eRAN
Table 7-8 Parameters for User-number-based preemption

MO Sheet in the Summary Parameter Setting Notes
Data File Group
ENodeBAlgoSwit EnodeBAlgoSwitch UE number Turn off the switch

ch preemption switch that controls user-
number-based
preemption.
Table 7-9 Parameters for user-number-reservation-based admission control of privileged UEs

MO Sheet in the Parameter Group Setting Notes
Summary Data
File
CellRacThd CellRacThd Admission Control Reserved Disable user-number-

User Numbers reservation-based
admission control of
privileged UEs by
setting this parameter
to 0.
Table 7-10 Parameters for ARP configuration for common UEs initiating CSFB procedures in
scenarios where the number of UEs allowed to be admitted is limited
MO Sheet in the Parameter Setting Notes
Summary Data File Group
CsFallbackPoli CsFallbackPolicyCfg Csfb User Arp Disable ARP configuration

cyCfg Configure for common UEs initiating
Switch CSFB procedures in
scenarios where the number
of UEs allowed to be
admitted is limited.

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

Run the MOD CELLALGOSWITCH command to disable uplink and downlink admission

eRAN
Step 1 Run the MOD CELLALGOSWITCH command to disable uplink and downlink admission
Step 2 Run the MOD CELLALGOSWITCH command to disable service preemption.
----End
Scenario 3: Intra-Operator User-Number-based Preemption
Run the MOD ENODEBALGOSWITCH command to disable user-number-based
preemption.
Scenario 4: User-Number-Reservation-based Admission Control of Privileged UEs
Run the MOD CELLRACTHD command to disable user-number-reservation-based
admission control of privileged UEs.
Scenario 5: ARP Configuration for Common UEs Initiating CSFB Procedures When the
Number of UEs to Be Admitted Is Limited
Run the MOD CSFALLBACKPOLICYCFG command to disable ARP configuration for
common UEs initiating CSFB procedures.

l Disabling Admission Control Based on QoS Satisfaction Rates
MOD CELLALGOSWITCH: LocalCellId=0, RacAlgoSwitch=DlSwitch-0&UlSwitch-0;
l Disabling Service Preemption

MOD CELLALGOSWITCH: LocalCellId=0, RacAlgoSwitch=PreemptionSwitch-0;
l Disabling User-Number-based Preemption

MOD ENODEBALGOSWITCH:
UeNumPreemptSwitch=IntraOpUeNumPreemptSwitch-0&InterOpUeNumPreemptSwitch-0;
l Disabling User-Number-Reservation-based Admission Control of Privileged UEs

MOD CELLRACTHD: LocalCellId=0, AcReservedUserNumber=0;
l Disabling ARP Configuration for Common UEs Initiating CSFB Procedures in

Scenarios Where the Number of Users Allowed to Be Admitted Is Limited
MOD CSFALLBACKPOLICYCFG: CsfbUserArpCfgSwitch=0;
7.5 Deployment of Congestion Control
7.5.1 Deployment Requirements

Feature
For details, see 5.3 Features Related to LBFD-002024 Congestion Control in the section
"Impacted Features".
Hardware
None
License
Congestion control does not have requirements for the operating environment, transmission
networking, and licenses.

eRAN
Other Requirements
As required by congestion control for the EPC, only the services whose ARP-related IE pre-
emptionVulnerability is "pre-emptable" can be released if the switch specified by
DlLdcSwitch(dlLdcSwitch) or UlLdcSwitch(ulLdcSwitch) is turned on. Therefore, the IE
pre-emptionVulnerability must be set to "pre-emptable" in the EPC.
7.5.2 Data Preparation

Required Data
The following table describes the parameters that must be set in CellAlgoSwitch MOs to
enable the congestion control algorithms.
Parameter Name Parameter ID Data Source Setting Notes
Local cell ID CellAlgoSwitch.Loc Network plan This parameter

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

eRAN
RAC algorithm CellAlgoSwitch.Ra Network plan l To enable

switch cAlgoSwitch (negotiation not downlink
required) congestion
detection, select
the
DlLdcSwitch(dl
LdcSwitch)
check box. If
congestion is
detected,
congestion relief
actions are taken.
l To disable
downlink
congestion
detection, clear
the
DlLdcSwitch(dl
LdcSwitch)
check box. Then,
downlink
congestion in the
cell, if any,
cannot be
relieved.
l To enable uplink
congestion
detection, select
the
UlLdcSwitch(ul
LdcSwitch)
check box. If
congestion is
detected,
congestion relief
actions are taken.
l To disable uplink
congestion
detection, clear
the
UlLdcSwitch(ul
LdcSwitch)
check box. Then,
uplink
congestion in the
cell, if any,
cannot be
relieved.

eRAN
Scenario-specific Data
The following table describes the parameters that must be set in CellRacThd MOs to
configure the congestion control algorithms.
Local cell ID CellRacThd.LocalC Network plan This parameter

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

threshold ongThd (negotiation not specifies the
required) congestion threshold
for services with a
QCI of 1. It applies
to both uplink and
downlink.
l If the QoS
satisfaction rate
of services with a
QCI of 1 in the
cell is lower than
this threshold,
these services
enter the
congested state.
l If the QoS
satisfaction rate
of these services
is higher than the
sum of this
threshold and
CellRacThd.Co
ngRelOffset,
these services
exit the
congested state.
The value 65 is
recommended.

eRAN

for services with a
to both uplink and
downlink.
l If the QoS
satisfaction rate
of services with a
QCI of 2 in the
cell is lower than
this threshold,
these services
enter the
congested state.
l If the QoS
satisfaction rate
of these services
is higher than the
sum of this
threshold and
CellRacThd.Co
ngRelOffset,
these services
exit the
congested state.
The value 65 is
recommended.

eRAN

for services with a
to both uplink and
downlink.
l If the QoS
satisfaction rate
of services with a
QCI of 3 in the
cell is lower than
this threshold,
these services
enter the
congested state.
l If the QoS
satisfaction rate
of these services
is higher than the
sum of this
threshold and
CellRacThd.Co
ngRelOffset,
these services
exit the
congested state.
The value 65 is
recommended.

eRAN

for services with a
to both uplink and
downlink.
l If the QoS
satisfaction rate
of services with a
QCI of 4 in the
cell is lower than
this threshold,
these services
enter the
congested state.
l If the QoS
satisfaction rate
of these services
is higher than the
sum of this
threshold and
CellRacThd.Co
ngRelOffset,
these services
exit the
congested state.
The value 65 is
recommended.

eRAN
Offset for service CellRacThd.CongR Network plan This parameter

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

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

eRAN
Uplink RB used CellRacThd.UlRbL Network plan This parameter

ratio low threshold owThd (negotiation not specifies the
required) threshold for
deciding whether the
uplink RB usage is
low. If the MAC
layer reports that the
uplink RB usage is
less than this
parameter value, the
uplink RB usage is
regarded to be low.
This threshold is
used in uplink
admission decisions.
The value 90 is
recommended.
7.5.3 Activation
Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
Enter the values of the parameters listed in Table 7-11 in a summary data file, which also
contains other data for the new eNodeBs to be deployed. Then, import the summary data file
into the Configuration Management Express (CME) for batch configuration. For detailed
instructions, see "Creating eNodeBs in Batches" in the initial configuration guide for the
eNodeB, which is available in the eNodeB product documentation.
l The MOs in Table 7-11 are contained in a scenario-specific summary data file. In this
situation, set the parameters in the MOs, and then verify and save the file.
l Some MOs in Table 7-11 are not contained in a scenario-specific summary data file. In
this situation, customize a summary data file to include the MOs before you can set the
parameters.
Table 7-11 Parameters for congestion control

Summary Data
File
CellAlgoSwitc CellAlgoSwitch Local cell ID, RAC algorithm User-defined

h switch template

eRAN

Summary Data
File
CellRacThd CellRacThd Local cell ID, QCI1 congest User-defined

threshold(%), QCI2 congest template
threshold(%), QCI3 congest
threshold(%), QCI4 congest
threshold(%), Offset for service
congest relieving(%), Uplink RB
used ratio high threshold(%),
Uplink RB used ratio low
threshold(%)
Using the CME to Perform Batch Configuration for Existing eNodeBs

Batch reconfiguration using the CME is the recommended method to activate a feature on
existing eNodeBs. This method reconfigures all data, except neighbor relationships, for
multiple eNodeBs in a single procedure.
Step 1 Customize a summary data file with the MOs and parameters listed in section "Using the
CME to Perform Batch Configuration for Newly Deployed eNodeBs". For online help, press
F1 when a CME window is active, and select Managing the CME > CME Guidelines >
LTE Application Management > eNodeB Related Operations > Customizing a Summary
Data File for Batch eNodeB Configuration.
Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk
Configuration Data (U2000 client mode), or choose LTE Application > Export Data >
Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeB
data stored on the CME into the customized summary data file.
Step 3 In the summary data file, set the parameters in the MOs according to the setting notes
provided in section "Data Preparation" and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk
Configuration Data (U2000 client mode), or choose LTE Application > Import Data >
Import Base Station Bulk Configuration Data (CME client mode), to import the summary
data file into the CME, and then start the data verification.
mode), to export and activate the incremental scripts. For detailed operations, see Managing
the CME > CME Guidelines > Script File Management > Exporting Incremental Scripts
from a Planned Data Area in the CME online help.
----End

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB.
The procedure is as follows:
Step 1 In the planned data area, click Base Station in the upper left corner of the configuration
window.

eRAN
Step 2 In area 1 shown in Figure 7-6, select the eNodeB to which the MOs belong.
Figure 7-6 MO search and configuration window
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.
Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
Step 5 Set the parameters in area 4 or 5.
mode), to export and activate the incremental scripts.
----End
Using MML Commands

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

MOD CELLALGOSWITCH: LocalCellId=0, RacAlgoSwitch=DlLdcSwitch-1&UlLdcSwitch-1;
MOD CELLRACTHD: LocalCellId=0, Qci1CongThd=65, Qci2CongThd=65, Qci3CongThd=65,
Qci4CongThd=65, UlRbHighThd=95, UlRbLowThd=90;

eRAN
7.5.4 Activation Observation

tracing task.
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, which can be
monitored based on 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 S1AP_ERAB_REL_IND
message, as shown in Figure 7-7, the indicated low-priority service has been released as
expected.
Figure 7-7 S1AP_ERAB_REL_IND message that indicates the release of a low-priority

service
----End
7.5.5 Deactivation
Using the CME to Perform Batch Configuration
Batch reconfiguration using the CME is the recommended method to deactivate a feature on
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for
feature activation described in Using the CME to Perform Batch Configuration for
Existing eNodeBs. In the procedure, modify parameters according to Table 7-12.

eRAN
Table 7-12 Parameters for congestion control
MO Sheet in the Parameter Group Setting Notes

Summary Data
File
CellAlgoSwitch CellAlgoSwitch Local cell ID, RAC Turn off the

algorithm switch switches that control
uplink and downlink
congestion control.

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

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

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

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

eRAN
Measurement Formula
Indicator
E-RAB congestion 1 - L.E-RAB.SuccEst/L.E-RAB.AttEst

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

congestion rate
NOTE
Counters in RRC.SetupFail.Cell monitor reasons of RRC connection setup failures.

Counters in E-RAB.EstFail.Cell monitor reasons of E-RAB setup failures.
The L.Cell.UserLic.Limit.Num.PLMN counter monitors the number of times that the licensed number
of UEs is limited for a specific operator.
Preemption
After preemption is activated, UEs establish RRC connections first, and then trigger
preemption. If a UE fails the preemption, the RRC connection for this UE is released. If the
preemption is successful, the RRC connection for the UE whose resources are preempted is
released. The L.Cell.UserSpec.PrepEmp.PrepAtt.Num counter measures the number of
released RRC connections.
The following counters measure the number of RRC connections of UEs that successfully
preempt resources of other UEs:
l L.Cell.UserLimit.PreEmp.Num
l L.Cell.UserLic.PrepEmp.Succ.Num
l L.Cell.UserLic.PrepEmp.Succ.Num.PLMN
The L.E-RAB.AbnormRel.Cong counter measures the number of bearers abnormally
released in the case of congestion, including bearers released due to preemption and bearers
released due to congestion control.
Congestion Control
During congestion control, the L.LC.ULCong.Dur.Cell and L.LC.DLCong.Dur.Cell
counters measure the uplink congestion time and downlink congestion time, respectively. The
L.LC.ULCong.Num.Cell and L.LC.DLCong.Num.Cell counters measure the number of
times uplink congestion and downlink congestion occur in a cell, respectively. The
L.LC.User.Rel counter measures the number of bearers released due to congestion control.
If redirection is performed, the L.RRCRedirection.IntraLTE counter measures the number
of redirections.
7.7 Parameter Optimization

The L.Traffic.Privilege.User.max and L.Traffic.Privilege.User.avg counters measure the
maximum number and the average number of privileged UEs in a cell, respectively. In
scenarios where user-number-reservation-based admission control of privileged UEs is
enabled, if the CellRacThd.AcReservedUserNumber parameter is set to an extremely large

eRAN
value, the number of common UEs that can access the cell is small; if the
CellRacThd.AcReservedUserNumber parameter value is set to an extremely small value, the
user number resources reserved for privileged UEs may be insufficient. Therefore, the
CellRacThd.AcReservedUserNumber parameter settings must be adjusted based on the
values of the L.Traffic.Privilege.User.max and L.Traffic.Privilege.User.avg counters.
7.8 Troubleshooting
7.8.1 Admission Control

Fault Description
High-priority services fail to preempt low-priority services.
Fault Handling
Step 1 Check whether the IE priorityLevel in the S1AP_ERAB_SETUP_REQ message, as shown in
Figure 7-8, of the service to be preempted is greater than that of the preempting service.
l If yes, go to Step 2.
l If no, change the values accordingly at the EPC.
Figure 7-8 Checking the ARP value
Step 2 Check the same message to observe whether: (1) The value of the IE pre-emptionCapability is
1 for the preempting service; (2) The value of the IE pre-emptionVulnerability is 1 for the
service to be preempted.
l If either of the two values is 0, change the service attributes accordingly at the EPC.
l If both values are 1, contact Huawei technical support for further troubleshooting.
----End
7.8.2 Congestion Control

None

eRAN
Description 8 Parameters
8 Parameters
Table 8-1 Parameters

MO Parame MML Feature Feature Description
ter ID Comma ID Name
nd
ENodeB UeNum MOD LOFD-0 Radio/ Meaning: Indicates the switch used to enable or
AlgoSwi Preempt ENODE 0102901 transport disable the preemption based on the number of users.
tch Switch BALGO / resource IntraOpUeNumPreemptSwitch: This parameter
SWITC TDLOF pre- indicates the switch used to enable or disable the intra-
H D-00102 emption operator preemption based on the number of users. If
LST 901 this switch is on, when a user cannot access the
ENODE network because of the user number restriction, the
BALGO user can preempt resources of other lower-priority
SWITC users served by the same operator. If this switch is off,
H preemption is not allowed. InterOpUeNumPreemptS-
witch: This parameter indicates the switch used to
enable or disable the inter-operator preemption based
on the number of users. If this switch is on, the inter-
operator preemption based on the number of users is
allowed. If this switch is off, the inter-operator
preemption based on the number of users is not
allowed.
GUI Value Range: IntraOpUeNumPreemptS-
witch(IntraOpUeNumPreemptSwitch),
InterOpUeNumPreemptS-
witch(InterOpUeNumPreemptSwitch)
Unit: None
Actual Value Range: IntraOpUeNumPreemptSwitch,
InterOpUeNumPreemptSwitch
Default Value: IntraOpUeNumPreemptSwitch:Off,
InterOpUeNumPreemptSwitch:Off

eRAN

nd
CellRac AcReser MOD LBFD-0 Admissi Meaning: Indicates the UE numbers reserved for UEs
Thd vedUser CELLR 02023 / on initiating emergency calls and high-priority UEs. If
Number ACTHD TDLBF Control this parameter is set to 0, no UE number is reserved
LST D-00202 for UEs initiating emergency calls and high-priority
CELLR 3 UEs. A non-zero value of this parameter represents
ACTHD the maximum UE number reserved for UEs initiating
emergency calls and high-priority UEs.
GUI Value Range: 0~30
Unit: None
Actual Value Range: 0~30
Default Value: 0
CellRac NewGol MOD LBFD-0 Admissi Meaning: Indicates the offset for admission of new
Thd dService CELLR 02023 / on gold-level services. This parameter applies to both
Offset ACTHD TDLBF Control downlink and uplink. New gold-level services and
LST D-00202 handed-over services with QCI N are admitted if both
CELLR 3 the following conditions are met: (1) The satisfaction
ACTHD rate of services with QCI N is higher than or equal to
the sum of this offset and the admission threshold for
the handed-over services with QCI N. (2) The
satisfaction rate of services with any other QCI is
higher than or equal to the corresponding admission
threshold for the handed-over services with that QCI.
Unit: %
Default Value: 5
CellRac NewSilv MOD LBFD-0 Admissi Meaning: Indicates the offset for admission of new
Thd erServic CELLR 02023 / on silver-level services. This parameter applies to both
eOffset ACTHD TDLBF Control downlink and uplink. New silver-level services and
Unit: %
Default Value: 5

eRAN

nd
CellRac NewCop MOD LBFD-0 Admissi Meaning: Indicates the offset for admission of new
Thd perServi CELLR 02023 / on bronze-level services. This parameter applies to both
ceOffset ACTHD TDLBF Control downlink and uplink. New bronze-level services and
Unit: %
Default Value: 5
CellRac GoldSer MOD LBFD-0 Admissi Meaning: Indicates the Allocation and Retention
Thd viceArp CELLR 02023 / on Priority (ARP) threshold for the Golden-level
Thd ACTHD TDLBF Control services. A service is defined as a Golden-level
LST D-00202 service if its ARP value is smaller than or equal to this
CELLR 3 threshold. The service priority has a negative
ACTHD correlation with the ARP value.
Unit: None
Default Value: 5
CellRac SilverSe MOD LBFD-0 Admissi Meaning: Indicates the Allocation and Retention
Thd rviceArp CELLR 02023 / on Priority (ARP) threshold for the Silver-level services.
Thd ACTHD TDLBF Control A service is defined as a Silver-level service if its
LST D-00202 ARP value is smaller than or equal to the value of this
CELLR 3 parameter and is larger than the value of
ACTHD GoldServiceArpThd. A service is defined as a Bronze-
level service if its ARP value is larger than the value
of this parameter. The service priority has a negative
correlation with the ARP value.
Unit: None
Default Value: 10

eRAN

nd
eNBCell RsvdSw MOD None None Meaning:

RsvdPar Para3 ENBCE Indicates reserved 32-bit switch parameter 3 that is
a LLRSV reserved for future requirements.
DPARA
LST Note on parameter replacement: Reserved parameters
ENBCE are temporarily used in patch versions and will be
LLRSV replaced with new parameters. For example, the ID of
DPARA a new parameter can signify the parameter function.
Therefore, avoid using this parameter.
GUI Value Range:
RsvdSwPara3_bit1(ReservedSwitchParameter3_bit1),
RsvdSwPara3_bit10(ReservedSwitchParame-
ter3_bit10),
ter3_bit11),
ter3_bit12),
ter3_bit13),
ter3_bit14),
ter3_bit15),
ter3_bit16),
ter3_bit17),
ter3_bit18),
ter3_bit19),
ter3_bit20),
ter3_bit21),
ter3_bit22),
ter3_bit23),

eRAN

nd
ter3_bit24),
ter3_bit25),
ter3_bit26),
ter3_bit27),
ter3_bit28),
ter3_bit29),
ter3_bit30),
ter3_bit31),
ter3_bit32)
Unit: None
Actual Value Range: RsvdSwPara3_bit1,
RsvdSwPara3_bit2, RsvdSwPara3_bit3,
RsvdSwPara3_bit32
Default Value: RsvdSwPara3_bit1:Off,
RsvdSwPara3_bit2:Off, RsvdSwPara3_bit3:Off,

eRAN

nd
RsvdSwPara3_bit32:Off
eNBCell RsvdU8 MOD None None Meaning: Indicates reserved U8 parameter 10 that is
RsvdPar Para10 ENBCE reserved for future requirements. Note on parameter
a LLRSV replacement: Reserved parameters are temporarily
DPARA used in patch versions and will be replaced with new
LST parameters. For example, the ID of a new parameter
ENBCE can signify the parameter function. Therefore, avoid
LLRSV using this parameter.
DPARA GUI Value Range: 0~255
Unit: None
Default Value: 0
Unit: None
Default Value: 0
Unit: None
Default Value: 0

eRAN

nd
Unit: None
Default Value: 0
Unit: None
Default Value: 0
Unit: None
Default Value: 0

eRAN

nd
Unit: None
Default Value: 0
CSFallB CsfbUse MOD LBFD-0 Admissi Meaning: Indicates whether allocation/retention

ackPolic rArpCfg CSFAL 02023 / on priorities (ARPs) can be configured for CSFB services
yCfg Switch LBACK TDLBF Control triggered by common calls. For details about ARPs,
POLIC D-00202 see 3GPP TS 23.401.
YCFG 3 GUI Value Range: OFF(Off), ON(On)
LST Unit: None
CSFAL
LBACK Actual Value Range: OFF, ON
POLIC Default Value: OFF(Off)
YCFG
CSFallB Normal MOD LBFD-0 Admissi Meaning: Indicates the allocation/retention priority
ackPolic CsfbUse CSFAL 02023 / on (ARP) of a CSFB service triggered by a common call.
yCfg rArp LBACK TDLBF Control When this parameter is set to 1, the service priority is
POLIC D-00202 the same as that of an emergency call. For details
YCFG 3 about the ARP, see 3GPP TS 23.401.
LST GUI Value Range: 1~15
CSFAL Unit: None
LBACK
POLIC Actual Value Range: 1~15
YCFG Default Value: 2

eRAN

nd
CellAlg RacAlgo MOD LBFD-0 Admissi Meaning:

oSwitch Switch CELLA 02023 / on Indicates whether to enable the admission and load
LGOSW TDLBF Control control algorithms.
ITCH D-00202 Congesti
LST 3 on DlSwitch: Indicates whether to enable the algorithm
CELLA LBFD-0 Control of downlink admission control based on the
LGOSW 02024 / satisfaction rate. If this switch is on, the algorithm is
Radio/ enabled. If this switch is off, the algorithm is disabled.
ITCH TDLBF transport
D-00202 During the calculation of the QoS satisfaction rate of
resource services with different QCIs, the satisfaction
4 pre- estimation method used dedicatedly for VoIP services
LOFD-0 emption is implemented on services with the QCI of 1. If a
0102901 service with the QCI of 1 is not a VoIP service, the
satisfaction rate calculated using this method is lower
than the actual value, which affects the admission of
GBR services. Therefore, if not all the services with
the QCI of 1 are VoIP services, it is recommended that
this switch be off.
UlSwitch: Indicates whether to enable the algorithm
of uplink admission control based on the satisfaction
rate. If this switch is on, the algorithm is enabled. If
this switch is off, the algorithm is disabled. During the
calculation of the QoS satisfaction rate of services
with different QCIs, the satisfaction estimation
method used dedicated for VoIP services is
implemented on services with the QCI of 1. If a
service with the QCI of 1 is not a VoIP service, the
than the actual value, which affects the admission of
GBR services. Therefore, if not all the services with
the QCI of 1 are VoIP services, it is recommended that
this switch be off.
DlPredictSwitch: Indicates whether to enable the
algorithm of downlink admission control based on
prediction. If this switch is on, the algorithm is
enabled. If this switch is off, the algorithm is disabled.
UlPredictSwitch: Indicates whether to enable the
algorithm of uplink admission control based on
prediction. If this switch is on, the algorithm is
enabled. If this switch is off, the algorithm is disabled.
GbrUsageSwitch: Indicates whether to enable the
check on the number of PRBs used by GBR services.
If this switch is on, the number of PRBs used by
existing GBR services is checked before a new GBR
service can be admitted. If this switch is off, the
number of PRBs used by existing GBR services is not

eRAN

nd
checked during admission evaluation of new GBR

services
DlLdcSwitch: Indicates whether to implement load
control in the downlink of a cell. If this switch is on,
the system checks for congestion in the downlink of
the cell. If the downlink is congested, load control is
performed. If this switch is off, the system does not
check for congestion in the downlink of the cell and
the congestion cannot be relieved. During the
calculation of the QoS satisfaction rate of services
with different QCIs, the satisfaction estimation
method used dedicated for VoIP services is
implemented on services with the QCI of 1. If a
service with the QCI of 1 is not a VoIP service, the
than the actual value, which affects the cell load
control. Therefore, if not all the services with the QCI
of 1 are VoIP services, it is recommended that this
switch be off.
UlLdcSwitch: Indicates whether to implement load
control in the uplink of a cell. If this switch is on, the
system checks for congestion in the uplink of the cell.
If the uplink is congested, load control is performed. If
this switch is off, the system does not check for
congestion in the uplink of the cell and the congestion
cannot be relieved. During the calculation of the QoS
satisfaction rate of services with different QCIs, the
satisfaction estimation method used dedicated for
VoIP services is implemented on services with the
QCI of 1. If a service with the QCI of 1 is not a VoIP
service, the satisfaction rate calculated using this
method is lower than the actual value, which affects
the cell load control. Therefore, if not all the services
with the QCI of 1 are VoIP services, it is
recommended that this switch be off.
RelDrbSwitch: Indicates whether low-priority services
can be released in the case of congestion. If this
switch is on, low-priority services can be released. If
this switch is off, low-priority services cannot be
released.
PreemptionSwitch: Indicates whether to enable the
preemption control algorithm. If this switch is on,
preemption can be used when the admission of high-
priority services fails. If this switch is off, only
emergency calls can be admitted to the system when
resources are insufficient.

eRAN

nd
GUI Value Range: DlSwitch(dlCacSwitch),

UlSwitch(ulCacSwitch),
DlPredictSwitch(dlCacPredictSwitch),
UlPredictSwitch(ulCacPredictSwitch),
GbrUsageSwitch(GbrUsedPRbCheckSwitch),
DlLdcSwitch(dlLdcSwitch),
UlLdcSwitch(ulLdcSwitch),
RelDrbSwitch(LdcDrbRelSwitch),
PreemptionSwitch(PreemptionSwitch)
Unit: None
Actual Value Range: DlSwitch, UlSwitch,
DlPredictSwitch, UlPredictSwitch, GbrUsageSwitch,
DlLdcSwitch, UlLdcSwitch, RelDrbSwitch,
PreemptionSwitch
Default Value: DlSwitch:Off, UlSwitch:Off,
DlPredictSwitch:Off, UlPredictSwitch:Off,
GbrUsageSwitch:Off, DlLdcSwitch:Off,
UlLdcSwitch:Off, RelDrbSwitch:Off,
PreemptionSwitch:Off

eRAN

nd
ENodeB Redirect MOD LBFD-0 Admissi Meaning:

AlgoSwi Switch ENODE 02023 / on Indicates the switch used to enable or disable the
tch BALGO TDLBF Control redirection algorithm. This switch does not control
SWITC D-00202 Congesti redirection or fast redirection for CSFB.
H 3 on
LST LBFD-0 Control GeranFlashRedirectSwitch: If this switch and
ENODE 02024 / GeranRedirectSwitch are on, fast redirection to
Radio/ GERAN can be performed.
BALGO TDLBF transport
SWITC D-00202 resource UtranFlashRedirectSwitch: If this switch and
H 4 pre- UtranRedirectSwitch are on, fast redirection to
LOFD-0 emption UTRAN can be performed.
0102901 PS Inter-
/ LoadBasedSwitch: If this switch is on, load based
RAT redirection can be performed.
TDLOF Mobility
D-00102 between GUI Value Range: LoadBasedSwitch,
901 E- GeranFlashRedirectSwitch, UtranFlashRedirectSwitch
LOFD-0 UTRAN Unit: None
01019 / and Actual Value Range: LoadBasedSwitch,
TDLOF UTRAN GeranFlashRedirectSwitch, UtranFlashRedirectSwitch
D-00101 PS Inter- Default Value: LoadBasedSwitch:Off,
9 RAT GeranFlashRedirectSwitch:Off, UtranFlashRedirectS-
LOFD-0 Mobility witch:Off
01020 / between
TDLOF E-
D-00102 UTRAN
0 and
LOFD-0 GERAN
01021 / PS Inter-
TDLOF RAT
D-00102 Mobility
1 between
E-
UTRAN
and
CDMA2
000

eRAN

nd
Unit: None
Default Value: 0
CellRac CongRel MOD LBFD-0 Congesti Meaning: Indicates the congestion release offset. The
Thd Offset CELLR 02024 / on service of a specific QCI exits the congestion state if
ACTHD TDLBF Control the satisfaction rate of the service exceeds the sum of
LST D-00202 this congestion release offset and the congestion
CELLR 4 threshold for the QCI. The service retains the
ACTHD congestion state if the satisfaction rate is below or
equal to the sum of this congestion release offset and
the congestion threshold for the QCI.
Unit: %
Default Value: 20
CellRac Qci1Co MOD LBFD-0 Congesti Meaning:

Thd ngThd CELLR 02024 / on Indicates the congestion threshold for services with
ACTHD TDLBF Control QCI of 1. This threshold applies to both UL and DL.
LST D-00202
CELLR 4 If the satisfaction rate of services with QCI of 1 in the
ACTHD cell becomes lower than this threshold, the services
with QCI of 1 enter the congested state.
If the satisfaction rate of services with QCI of 1 in the
cell becomes higher than the sum of this threshold and
the congestion relief offset, the services with QCI of 1
leave the congested state.
Unit: %
Default Value: 65

eRAN

nd

LST D-00202
Unit: %
Default Value: 65

LST D-00202
CELLR 4 If the satisfaction rate of the services with QCI of 3 in
ACTHD the cell becomes lower than this threshold, the
services with QCI of 3 enter the congested state.
Unit: %
Default Value: 65

eRAN

nd

LST D-00202
Unit: %
Default Value: 65
CellAlg LocalCe DSP None None Meaning: Indicates the local ID of the cell. It uniquely
oSwitch llId CELLU identifies a cell within a BS.
LCAMC GUI Value Range: 0~255
CLUST
ER Unit: None
LST Actual Value Range: 0~255

CELLA Default Value: None
LGOSW
ITCH
MOD
CELLA
LGOSW
ITCH
CellRac LocalCe LST None None Meaning: Indicates the local cell ID. It uniquely
Thd llId CELLR identifies a cell within a BS.
ACTHD GUI Value Range: 0~255
MOD Unit: None
CELLR
ACTHD Actual Value Range: 0~255
Default Value: None

eRAN

nd
CellRac Qci1Ho MOD LBFD-0 Admissi Meaning:

Thd Thd CELLR 02023 / on Indicates the admission threshold for the handed-over
ACTHD TDLBF Control service with QCI of 1. This threshold applies to both
LST D-00202 UL and DL.
CELLR 3
ACTHD If the satisfaction rate of services with QCI of 1 is
above or equal to this threshold, the handed-over
service with QCI of 1 can be admitted.
If the satisfaction rate of services with QCI of 1 is
below this threshold, the handed-over service with
QCI of 1 cannot be admitted.
Unit: %
Default Value: 90

CELLR 3
Unit: %
Default Value: 90

eRAN

nd

CELLR 3
Unit: %
Default Value: 90

CELLR 3
Unit: %
Default Value: 90
CellRac UlRbHi MOD LBFD-0 Admissi Meaning: Indicates the threshold for deciding on
Thd ghThd CELLR 02023 / on whether the UL RB usage is high. This threshold
ACTHD TDLBF Control applies to UL admission decision. If the UL RB usage
LST D-00202 Congesti reported by the MAC layer is above this threshold, the
CELLR 3 on UL RB usage is assumed to be high.
ACTHD LBFD-0 Control GUI Value Range: 10~100
02024 / Unit: %
TDLBF
D-00202 Actual Value Range: 10~100
4 Default Value: 95

eRAN

nd
CellRac UlRbLo MOD LBFD-0 Admissi Meaning: Indicates the threshold for deciding on
Thd wThd CELLR 02023 / on whether the UL RB usage is low. It applies to UL
ACTHD TDLBF Control admission decision. If the UL RB usage reported by
LST D-00202 Congesti the MAC layer is below this threshold, the UL RB
CELLR 3 on usage is assumed to be low.
ACTHD LBFD-0 Control GUI Value Range: 10~100
02024 / Unit: %
TDLBF
D-00202 Actual Value Range: 10~100
4 Default Value: 90

eRAN
Description 9 Counters
9 Counters
Table 9-1 Counters

Counter ID Counter Name Counter Feature ID Feature Name
Description
1526726657 L.RRC.ConnReq.M Number of RRC Multi-mode: None RRC Connection

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

ucc connection setup GSM: None Management
completion times RRC Connection
UMTS: None
Management
LTE:
LBFD-002007
TDLBFD-002007
1526726760 L.LC.ULCong.Num Number of times Multi-mode: None Congestion Control

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

Cell congestion in a cell GSM: None Congestion Control
UMTS: None
LTE:
LBFD-002024
TDLBFD-002024

eRAN

Description
1526726762 L.LC.DLCong.Num Number of times Multi-mode: None Congestion Control

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

Cell downlink GSM: None Congestion Control
congestion in a cell
UMTS: None
LTE:
LBFD-002024
TDLBFD-002024
1526726764 L.LC.User.Rel Number of service Multi-mode: None Congestion Control

releases due to GSM: None Congestion Control
congestion
UMTS: None
LTE:
LBFD-002024
TDLBFD-002024
1526727544 L.E-RAB.SuccEst Total number of Multi-mode: None Radio Bearer

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

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

initial E-RAB setup GSM: None Management
attempts initiated Radio Bearer
by UEs in a cell UMTS: None
Management
LTE:
LBFD-002008
TDLBFD-002008

eRAN

Description
1526728275 L.E- Total number of Multi-mode: None Radio Bearer

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

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

RAB.FailEst.NoRa setup failures due to GSM: None Management
dioRes insufficient radio Radio Bearer
resources UMTS: None
Management
LTE:
LBFD-002023
TDLBFD-002023
1526728284 L.E- Number of Multi-mode: None Radio Bearer

RAB.AbnormRel.C abnormal releases GSM: None Management
ong of activated E- Radio Bearer
RABs due to UMTS: None
Management
network congestion LTE:
LBFD-002008 Congestion Control
TDLBFD-002008 Congestion Control
LBFD-002024 Radio/transport
resource pre-
TDLBFD-002024 emption
LOFD-00102901 Radio/transport
TDLOFD-0010290 resource pre-
1 emption

eRAN

Description
1526728325 L.RRCRedirection.I Number of intra- Multi-mode: None Admission Control

ntraLTE RAT intra-duplex- GSM: None Admission Control
mode redirections
UMTS: None Coverage Based
LTE: Inter-frequency
LBFD-002023 Handover
TDLBFD-002023 Coverage Based
Inter-frequency
TDLBFD-0020180 Distance Based
2 Inter-frequency
1526728444 L.Cell.UserLimit.Pr Number of Multi-mode: None Radio/transport

eEmp.Num successful GSM: None resource pre-
preemptions emption
triggered due to UMTS: None
Radio/transport
user limitation LTE: resource pre-
LOFD-00102901 emption
TDLOFD-0010290
1

ong.PLMN of activated E- Radio Bearer
RABs because of UMTS: None
Management
network congestion LTE:
for a specific LBFD-002008 Congestion Control
operator TDLBFD-002008 Congestion Control
resource pre-
1 emption
LOFD-001036 RAN Sharing with
LOFD-001037 Common Carrier
TDLOFD-001036 RAN Sharing with
Dedicated Carrier
TDLOFD-001037
RAN Sharing with
LOFD-070206 Common Carrier
RAN Sharing with
Dedicated Carrier
Hybrid RAN
Sharing

eRAN

Description

dioRes.SRS insufficient SRS Radio Bearer
Management
LTE:
LBFD-002023
TDLBFD-002023

dioRes.PUCCH insufficient PUCCH Radio Bearer
Management
LTE:
LBFD-002023
TDLBFD-002023
1526729631 L.RRCRedirection.I Number of intra- Multi-mode: None Admission Control

nterFddTdd RAT inter-duplex- GSM: None Admission Control
mode redirections
UMTS: None Coverage Based
LTE: Inter-frequency
TDLBFD-002023 Coverage Based
Inter-frequency
TDLBFD-0020180 Distance Based
2 Inter-frequency

ong.PreEmp of activated E- Radio Bearer
Management
radio resource LTE:
preemption LBFD-002008 Congestion Control
resource pre-
1 emption

eRAN

Description

ong.Load of activated E- Radio Bearer
Management
radio resource LTE:
overload LBFD-002008 Congestion Control
LBFD-002024
TDLBFD-002024

ong.VoIP of activated E- Radio Bearer
RABs for voice UMTS: None
Management
services because of LTE:
radio network LBFD-002008 Congestion Control
congestion TDLBFD-002008 Congestion Control
resource pre-
1 emption

ong.PreEmp.VoIP of activated E- Radio Bearer
Management
radio resource LBFD-002008 Congestion Control
preemption TDLBFD-002008 Congestion Control
resource pre-
1 emption

ong.Load.VoIP of activated E- Radio Bearer
Management
radio resource LBFD-002008 Congestion Control
overload TDLBFD-002008 Congestion Control
LBFD-002024
TDLBFD-002024

eRAN

Description

ong.PreEmp.PLMN of activated E- Radio Bearer
Management
radio resource LTE:
preemption for a LBFD-002008 RAN Sharing with
specific operator Common Carrier
TDLBFD-002008
RAN Sharing with
LOFD-001036 Dedicated Carrier
TDLOFD-001036 Common Carrier
LBFD-002024 Hybrid RAN
Sharing
TDLBFD-002024
Congestion Control
LOFD-00102901
Congestion Control
TDLOFD-0010290
1 Radio/transport
resource pre-
emption
Radio/transport
resource pre-
emption

ong.Load.PLMN of activated E- Radio Bearer
Management
radio resource LTE:
overload for a LBFD-002008 RAN Sharing with
specific operator Common Carrier
TDLBFD-002008
RAN Sharing with
Sharing
TDLBFD-002024
Congestion Control
Congestion Control

eRAN

Description

ong.VoIP.PLMN of activated E- Radio Bearer
Management
radio network LBFD-002008 RAN Sharing with
congestion for a Common Carrier
TDLBFD-002008
specific operator RAN Sharing with
Sharing
TDLBFD-002024
Congestion Control
LOFD-00102901
Congestion Control
TDLOFD-0010290
1 Radio/transport
resource pre-
emption
Radio/transport
resource pre-
emption

eRAN

Description

ong.PreEmp.VoIP.P of activated E- Radio Bearer
LMN RABs for voice UMTS: None
Management
radio resource LBFD-002008 RAN Sharing with
preemption for a Common Carrier
TDLBFD-002008
Sharing
TDLBFD-002024
Congestion Control
LOFD-00102901
Congestion Control
TDLOFD-0010290
1 Radio/transport
resource pre-
emption
Radio/transport
resource pre-
emption

ong.Load.VoIP.PL of activated E- Radio Bearer
MN RABs for voice UMTS: None
Management
radio resource LBFD-002008 RAN Sharing with
overload for a Common Carrier
TDLBFD-002008
Sharing
TDLBFD-002024
Congestion Control
Congestion Control

eRAN

Description

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

ULRes because of Radio Bearer
insufficient uplink UMTS: None
Management
transport resources LTE:
LBFD-002023
TDLBFD-002023

RAB.FailEst.NoRa setup failures GSM: None Management
dioRes.DLThrpLic because of Radio Bearer
insufficient licensed UMTS: None
Management
downlink traffic LTE:
volume LBFD-002008 Admission Control
LBFD-002023
TDLBFD-002023

dioRes.ULThrpLic because of Radio Bearer
insufficient licensed UMTS: None
Management
uplink traffic LTE:
volume LBFD-002008 Admission Control
LBFD-002023
TDLBFD-002023

eRAN

Description

dioRes.DLSatis because of a low Radio Bearer
downlink UMTS: None
Management
satisfaction rate LTE:
LBFD-002023
TDLBFD-002023

dioRes.ULSatis because of a low Radio Bearer
uplink satisfaction UMTS: None
Management
rate LTE:
LBFD-002023
TDLBFD-002023
1526729961 L.E- Number of setup Multi-mode: None Radio Bearer

RAB.FailEst.NoRa failures of E-RABs GSM: None Management
dioRes.VoIP for voice services Radio Bearer
because of UMTS: None
Management
insufficient radio LTE:
LBFD-002023
TDLBFD-002023

dioRes.SRS.VoIP for voice services Radio Bearer
Management
insufficient SRS LTE:
LBFD-002023
TDLBFD-002023

eRAN

Description

dioRes.PUCCH.VoI for voice services Radio Bearer
P because of UMTS: None
Management
insufficient PUCCH LTE:
LBFD-002023
TDLBFD-002023

dioRes.DLThrpLic. for voice services Radio Bearer
VoIP because of UMTS: None
Management
insufficient licensed LTE:
downlink traffic LBFD-002008 Admission Control
volume TDLBFD-002008 Admission Control
LBFD-002023
TDLBFD-002023

dioRes.ULThrpLic. for voice services Radio Bearer
VoIP because of UMTS: None
Management
uplink traffic LBFD-002008 Admission Control
volume TDLBFD-002008 Admission Control
LBFD-002023
TDLBFD-002023

dioRes.DLSatis.VoI for voice services Radio Bearer
P because of a low UMTS: None
Management
downlink LTE:
satisfaction rate LBFD-002008 Admission Control
LBFD-002023
TDLBFD-002023

eRAN

Description

dioRes.ULSatis.VoI for voice services Radio Bearer
P because of a low UMTS: None
Management
uplink satisfaction LTE:
rate LBFD-002008 Admission Control
LBFD-002023
TDLBFD-002023

RAB.FailEst.TNL. failures of E-RABs GSM: None Management
DLRes.VoIP for voice services Radio Bearer
Management
insufficient LTE:
downlink transport LBFD-002008 Admission Control
resources TDLBFD-002008 Admission Control
LBFD-002023
TDLBFD-002023

ULRes.VoIP for voice services Radio Bearer
Management
insufficient uplink LTE:
transport resources LBFD-002008 Admission Control
LBFD-002023
TDLBFD-002023

eRAN

Description

DLRes.PLMN because of Radio Bearer
insufficient UMTS: None
Management
downlink transport LTE:
resources for a LBFD-002008 Admission Control
specific operator TDLBFD-002008 Admission Control
LBFD-002023 RAN Sharing with
Common Carrier
TDLBFD-002023
RAN Sharing with
Hybrid RAN
Sharing

ULRes.PLMN because of Radio Bearer
insufficient uplink UMTS: None
Management
transport resources LTE:
for a specific LBFD-002008 Admission Control
operator TDLBFD-002008 Admission Control
Common Carrier
TDLBFD-002023
RAN Sharing with
Hybrid RAN
Sharing

eRAN

Description

dioRes.DLThrpLic. because of Radio Bearer
PLMN insufficient UMTS: None
Management
downlink licensed LTE:
traffic volume for a LBFD-002008 Admission Control
Common Carrier
TDLBFD-002023
RAN Sharing with
Hybrid RAN
Sharing

dioRes.ULThrpLic. because of Radio Bearer
PLMN insufficient uplink UMTS: None
Management
licensed traffic LTE:
volume for a LBFD-002008 Admission Control
Common Carrier
TDLBFD-002023
RAN Sharing with
Hybrid RAN
Sharing

eRAN

Description

dioRes.DLSatis.PL because of a low Radio Bearer
MN downlink UMTS: None
Management
satisfaction rate for LTE:
a specific operator LBFD-002008 Admission Control
Common Carrier
TDLBFD-002023
RAN Sharing with
Hybrid RAN
Sharing

dioRes.ULSatis.PL because of a low Radio Bearer
MN uplink satisfaction UMTS: None
Management
rate for a specific LTE:
operator LBFD-002008 Admission Control
Common Carrier
TDLBFD-002023
RAN Sharing with
Hybrid RAN
Sharing

eRAN

Description

dioRes.VoIP.PLMN for voice services Radio Bearer
Management
insufficient radio LTE:
Common Carrier
TDLBFD-002023
RAN Sharing with
Hybrid RAN
Sharing

dioRes.SRS.VoIP.P for voice services Radio Bearer
LMN because of UMTS: None
Management
insufficient SRS LTE:
Common Carrier
TDLBFD-002023
RAN Sharing with
Hybrid RAN
Sharing

eRAN

Description

dioRes.PUCCH.VoI for voice services Radio Bearer
P.PLMN because of UMTS: None
Management
insufficient PUCCH LTE:
Common Carrier
TDLBFD-002023
RAN Sharing with
Hybrid RAN
Sharing

dioRes.DLThrpLic. for voice services Radio Bearer
VoIP.PLMN because of UMTS: None
Management
downlink traffic LBFD-002008 Admission Control
volume for a TDLBFD-002008 Admission Control
LBFD-002023
Common Carrier
TDLBFD-002023
RAN Sharing with
Hybrid RAN
Sharing

eRAN

Description

dioRes.ULThrpLic. for voice services Radio Bearer
VoIP.PLMN because of UMTS: None
Management
uplink traffic LBFD-002008 Admission Control
volume for a TDLBFD-002008 Admission Control
LBFD-002023
Common Carrier
TDLBFD-002023
RAN Sharing with
Hybrid RAN
Sharing

dioRes.DLSatis.VoI for voice services Radio Bearer
P.PLMN because of a low UMTS: None
Management
downlink LTE:
satisfaction rate for LBFD-002008 Admission Control
a specific operator TDLBFD-002008 Admission Control
Common Carrier
TDLBFD-002023
RAN Sharing with
Hybrid RAN
Sharing

eRAN

Description

dioRes.ULSatis.VoI for voice services Radio Bearer
P.PLMN because of a low UMTS: None
Management
rate for a specific LBFD-002008 Admission Control
operator TDLBFD-002008 Admission Control
Common Carrier
TDLBFD-002023
RAN Sharing with
Hybrid RAN
Sharing

DLRes.VoIP.PLMN for voice services Radio Bearer
Management
insufficient LTE:
downlink transport LBFD-002008 Admission Control
resources for a TDLBFD-002008 Admission Control
LBFD-002023
Common Carrier
TDLBFD-002023
RAN Sharing with
Hybrid RAN
Sharing

eRAN

Description

ULRes.VoIP.PLMN for voice services Radio Bearer
Management
insufficient uplink LTE:
transport resources LBFD-002008 Admission Control
for a specific TDLBFD-002008 Admission Control
operator RAN Sharing with
LBFD-002023
Common Carrier
TDLBFD-002023
RAN Sharing with
Hybrid RAN
Sharing
1526730100 L.Traffic.Privilege. Average number of Multi-mode: None Admission Control

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

User.max of privileged UEs in GSM: None Admission Control
a cell
UMTS: None Emergency Call
LTE: Emergency call
LBFD-002023
TDLBFD-002023
LBFD-002028
TDLBFD-002028

eRAN

Description

RAB.FailEst.RNL.e setup failures due to GSM: None Management
NodeB.NormRel normal release Radio Bearer
initiated by eNodeB UMTS: None
Management
LTE:
LBFD-002023
TDLBFD-002023

RAB.FailEst.RNL.e setup failures due to GSM: None Management
NodeB.AbnormRel abnormal release Radio Bearer
initiated by eNodeB UMTS: None
Management
LTE:
LBFD-002023
TDLBFD-002023

dioRes.DLSatis.QC with a QCI of 2 Radio Bearer
I2 because of a low UMTS: None
Management
downlink LTE:
TDLBFD-002023
LBFD-002023

Management
downlink LTE:
TDLBFD-002023
LBFD-002023

eRAN

Description

Management
downlink LTE:
TDLBFD-002023
LBFD-002023

dioRes.ULSatis.QC with a QCI of 2 Radio Bearer
Management
TDLBFD-002023
LBFD-002023

Management
TDLBFD-002023
LBFD-002023

Management
TDLBFD-002023
LBFD-002023

eRAN

Description

I2.PLMN because of a low UMTS: None
Management
downlink LTE:
satisfaction rate for LBFD-002008 Admission Control
a specific operator TDLBFD-002008 Admission Control
Common Carrier
TDLBFD-002023
RAN Sharing with
Hybrid RAN
Sharing

Management
downlink LTE:
satisfaction rate for Admission Control
LBFD-002008
a specific operator Admission Control
TDLBFD-002008
RAN Sharing with
LBFD-002023 Common Carrier
TDLBFD-002023 RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with
TDLOFD-001037 Dedicated Carrier

eRAN

Description

Management
downlink LTE:
satisfaction rate for Admission Control
LBFD-002008
a specific operator Admission Control
TDLBFD-002008
RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with

Management
rate for a specific Admission Control
LBFD-002008
operator Admission Control
TDLBFD-002008
RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with

eRAN

Description

Management
LBFD-002008
TDLBFD-002008
RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with

Management
LBFD-002008
TDLBFD-002008
RAN Sharing with
Common Carrier
TDLOFD-001036
RAN Sharing with

RAB.FailEst.NoRa setup failures for GSM: None Management
dioRes.DLSatis.PT PTT services Radio Bearer
T because of a low UMTS: None
Management
downlink LTE:
LBFD-002023 Enhanced Extended
QCI
TDLBFD-002023
Enhanced Extended
LOFD-081218 QCI
TDLOFD-081215

eRAN

Description

dioRes.ULSatis.PT for PTT services Radio Bearer
T because of a low UMTS: None
Management
LBFD-002023 Enhanced Extended
QCI
TDLBFD-002023
Enhanced Extended
LOFD-081218 QCI
TDLOFD-081215
1526736866 L.Cell.UserSpec.Pr Number of times Multi-mode: None Admission Control

epEmp.PrepAtt.Nu preemptions are GSM: None Admission Control
m triggered by the
limitation of the UE UMTS: None Radio/transport
number LTE: resource pre-
specification LBFD-002023 emption
TDLBFD-002023 Radio/transport
resource pre-
TDLOFD-0010290
1
1526736867 L.Cell.UserLic.Lim Number of times Multi-mode: None Admission Control

it.Num.PLMN the licensed number GSM: None Admission Control
of UEs is limited
for a specific UMTS: None Radio/transport
operator resource pre-
LTE:
emption
LBFD-002023
Radio/transport
TDLBFD-002023 resource pre-
1 Common Carrier
LOFD-001036 Hybrid RAN
Sharing
LOFD-070206
RAN Sharing with

eRAN

Description
1526736868 L.Cell.UserLic.Prep Number of Multi-mode: None Admission Control

Emp.Succ.Num.PL successful GSM: None Admission Control
MN preemptions
triggered by the UMTS: None Radio/transport
limitation of the resource pre-
LTE:
licensed number of emption
LBFD-002023
UEs for a specific Radio/transport
operator TDLBFD-002023 resource pre-
1 Common Carrier
LOFD-001036 Hybrid RAN
Sharing
LOFD-070206
RAN Sharing with
1526736869 L.Cell.UserLic.Lim Number of times Multi-mode: None Admission Control

it.Num the licensed number GSM: None Admission Control
of UEs is limited
UMTS: None Radio/transport
LTE: resource pre-
LBFD-002023 emption
TDLBFD-002023 Radio/transport
resource pre-
TDLOFD-0010290
1
1526736870 L.Cell.UserLic.Prep Number of Multi-mode: None Admission Control

Emp.Succ.Num successful GSM: None Admission Control
preemptions
triggered by the UMTS: None Radio/transport
limitation of the LTE: resource pre-
licensed number of LBFD-002023 emption
UEs TDLBFD-002023 Radio/transport
resource pre-
TDLOFD-0010290
1

eRAN
Description 10 Glossary
10 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

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

2. 3GPP TS 23.401, "General Packet Radio Service (GPRS) enhancements for Evolved
Universal Terrestrial Radio Access Network (E-UTRAN) access"
3. 3GPP TS 36.306, "User Equipment (UE) radio access capabilities"
4. 3GPP TS 36.321, "Medium Access Control(MAC) protocol specification"
5. 3GPP TS 36.331, "Radio Resource Control (RRC)"
6. 3GPP TS 36.413, "S1 Application Protocol (S1AP)"
7. Scheduling Feature Parameter Description
8. Transport Resource Management Feature Parameter Description
9. Flow Control Feature Parameter Description
10. Flexible User Steering Feature Parameter Description
11. Physical Channel Resource Management Feature Parameter Description


Admission and Congestion Control in HW ERAN8.1

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Admission and Congestion Control in HW ERAN8.1

Transféré par

Droits d'auteur :

Formats disponibles

eRAN

Admission and Congestion Control

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 03 (2015-11-03) Huawei Proprietary and Confidential i

1 About This Document.................................................................................................................. 1

4 LBFD-002024 Congestion Control............................................................................................ 21

Issue 03 (2015-11-03) Huawei Proprietary and Confidential ii

7.2 Required Information................................................................................................................................................... 28

Issue 03 (2015-11-03) Huawei Proprietary and Confidential iii

1 About This Document

This document covers the following features:

l LBFD-002023 Admission Control

This document applies to the following types of eNodeBs.

eNodeB Type Model

Macro 3900 series eNodeBs

LampSite DBS3900 LampSite

1.2 Intended Audience

l Need to understand the features described herein

Issue 03 (2015-11-03) Huawei Proprietary and Confidential 1

l Work with Huawei products

1.3 Change History

Change Change Description Parameter Change Affected

Feature None None N/A

Editorial Modified monitoring methods None -

Change Change Description Parameter Change Affected

Feature None None Macro/

Issue 03 (2015-11-03) Huawei Proprietary and Confidential 2

Change Change Description Parameter Change Affected

Editorial Revised descriptions of user- Added the Macro/

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

Change Change Description Paramete Affected Entity

Feature Added performance counters None Macro/Micro/LampSite

Editorial Revised the description in 2 None -

1.4 Differences Between eNodeB Types

Issue 03 (2015-11-03) Huawei Proprietary and Confidential 3

Issue 03 (2015-11-03) Huawei Proprietary and Confidential 4

3 LBFD-002023 Admission Control/

Admission control is categorized into radio-resource-based admission control and transport-

Issue 03 (2015-11-03) Huawei Proprietary and Confidential 5

3.1 User Admission

Issue 03 (2015-11-03) Huawei Proprietary and Confidential 6

Figure 3-1 User admission procedure

Issue 03 (2015-11-03) Huawei Proprietary and Confidential 7

The user admission procedure is as follows:

LampSite eNodeBs do not support the LBBPc.

Issue 03 (2015-11-03) Huawei Proprietary and Confidential 8

3.2 Service Admission

Issue 03 (2015-11-03) Huawei Proprietary and Confidential 9

Figure 3-2 Service admission procedure

Issue 03 (2015-11-03) Huawei Proprietary and Confidential 10

3.2.1 Non-GBR Service Admission

3.2.2 GBR Service Admission

3.2.2.1 UE Capability Evaluation

3.2.2.2 Cell Congestion Indication

l Uplink Congested and Downlink Not Congested

Issue 03 (2015-11-03) Huawei Proprietary and Confidential 11

l Downlink Congested and Uplink Not Congested

3.2.2.3 Admission Based on QoS Satisfaction Rates

Figure 3-3 Downlink admission procedure for GBR services

Issue 03 (2015-11-03) Huawei Proprietary and Confidential 12

Figure 3-4 Uplink admission procedure for GBR services

PRB Usage Monitoring