16/4/2020 FDD Congestion Control (LR18+)

FDD Congestion Control (LR18+)

Feature Guide

FDD Congestion Control (LR18+)

Version Date Author Reviewer Notes

No technical change
V1.0 2018-09-30 Mou Jun Zhang Fan
Update the Impact on Network

V1.1 2019-02-28 Mou Jun Zhang Fan No technical change

TABLE OF CONTENTS

1 Introduction
1.1 Related Feature List and License Control
1.2 Correlation with Other Features

2 Function Description

3 Technical Description
3.1 Definitions
3.2 Technical Details
3.2.1 Relationship between Congestion and Admission
3.2.2 Calculation of Released Resources
3.2.3 Congestion Control Procedure Based on Forced Release
3.2.4 Congestion Control Procedure Based on GBR Rate Downsizing

4 Engineering Guide
4.1 Requirements
4.1.1 Hardware Requirements
4.1.2 EPC Requirements
4.1.3 Frequency Band, Frequency and Bandwidth Requirements
4.1.4 UE Requirement
4.1.5 Transmission Bandwidth Requirements
4.2 Function Activation
4.2.1 Related parameters
4.2.2 Parameter Configuration Procedure
4.2.3 Disabling the Feature
4.2.4 Data Synchronization

5 Related Counters, KPI and Alarms

5.1 Related Counters
5.2 Related KPI
5.3 Related Alarms

6 Impact on Network
6.1 Gain Analysis
6.2 Impact Analysis

7 Abbreviations

8 References

FIGURES

Figure 2‑1 Congestion Control Flow

Figure 3‑1 Relationship between Admission and Congestion Control
Figure 3‑2 DL PRB Congestion Control Flow
Figure 3‑3 UL PRB Congestion Control Flow
Figure 4‑1 Configuring Switch for Congestion Control
Figure 4‑2 Configuring Maximum Number of GBR Service Be Preempted

127.0.0.1:8890/web/index.html#?pid=Lib20190202fdd37p&pv=R1_2 1/10
16/4/2020 FDD Congestion Control (LR18+)
Figure 4‑3 Configuring the First Rank of Pre-emption QCI and the Second Rank of Pre-emption QCI
Figure 4‑4 Configure the congestion control based on GBR Compression
Figure 4‑5 Close Switch for Congestion Control

TABLES
Table 1‑1 Related Feature List and License Control
Table 1‑2 Correlation with Other Features
Table 4‑1 Configuration Rule of Parameters
Table 5‑1 Congestion Control Related Counters

1 Introduction
This document provides the introduction, technical descriptions, parameter configuration, counters, alarms, and validation procedure of the LTE FDD congestion control
feature.

The parameters, alarms and counters in this document are the same as those of the latest software version when this document is released. To obtain the MO, parameters,
alarms, and KPIs of the existing software version, please refer to the product manuals of the existing software version.

This document is applicable to LTE FDD mode. "LTE" and "eNodeB" mentioned in this document respectively refer to "LTE FDD" and "LTE FDD-based eNodeB".

1.1 Related Feature List and License Control

Table 1‑1 Related Feature List and License Control

No Feature List No. Feature List Name License Control

or not
1 ZLF31-08-004 Congestion Control No

1.2 Correlation with Other Features

Table 1‑2 Correlation with Other Features

Feature ID Feature Name Required Mutually Impacted

Feature Exclusive Feature
Feature
ZLF31-08- Congestion ZLF31-08-001 None None
004 Control Radio
Admission
Control

Note:

This feature does not work only after radio admission control failed.

2 Function Description
If there are no sufficient downlink or uplink PRB resources to meet the requirements of new service requests, congestion occurs, and new services fail to be admitted.
These service requests include initial RRC connection establishment request, modification request of E-RAB, and handover request. The congestion control feature
ensures the access of high priority services by releasing resources of the services that can be preempted, or downsizing the GBR rate of low priority services.

The congestion control mechanism can increase the access success rate of high priority services and improve the experience of high priority users. Whether the
congestion control feature is enabled or which method is used for congestion control can be configured on the OMC.

The congestion control flow is shown in Figure 2-1.

Figure 2‑1 Congestion Control Flow

127.0.0.1:8890/web/index.html#?pid=Lib20190202fdd37p&pv=R1_2 2/10
16/4/2020 FDD Congestion Control (LR18+)
About LTE congestion control, this document focuses on the following key technologies:

l Relationship between congestion control and admission control;

l Congestion control procedure based on forced released

l Congestion control procedure based on GBR service downsizing

3 Technical Description

3.1 Definitions
Admission Bit Rate (ABR) refers to the service rate used for calculating required PRB resources for the service based on PRB admission.

Priority Bit Rate (PBR) is configured in the eNodeB to control the minimum guaranteed rate of NGBR service during dispatch. The PBR of the NGBR comes from the QoS
function.

3.2 Technical Details

3.2.1 Relationship between Congestion and Admission

As shown in figure below, if a service fails to be admitted due to insufficient uplink or downlink PRB resources after the admission module completes the processing, the
service joins the congestion queue. For services in the congestion queue, the congestion module releases resources of low priority services or downsizing their GBR rate
to ensure the admission of high priority services. For the details about the congestions during the admission control, refer to FDD Admission Control Feature Guide.

The value for congestion control switch AC.switchForConCtl can be {0, 1, 2, 3}.

“0” indicates the switch is “off” and congestion is not handled.

“1” and “2” indicate the switch is “on”, and congestion procedure based on forced release;

“3” indicates the switch is “on” and congestion procedure based on GBR rate downsizing.

Figure 3‑1 Relationship between Admission and Congestion Control

Note:

When the value of congestion control switch AC.switchForConCtl is “1”, first preempt the UE service. This function is not supported in this version.

3.2.2 Calculation of Released Resources

If the switch AC.switchForConCtl is set to 1 or 2, that means forced released. The congestion control module retrieves the services in the queue, calculates the rate to be
released, and releases services forcibly in accordance with the rate to be released.

If the switch AC.switchForConCtl is set to 3, that means downsizing the rate of GBR services, the congestion control module retrieves the services in the queue, calculates
the PRB resources to be released, and downsizing the rate of GBR services in accordance with the PRB resources to be released.

3.2.2.1 Calculation of Forced Release

If the downlink resources of the service are limited, the downlink service rate to be released = downlink ABR - downlink remaining rate resources of the air interface.

If the uplink resources of the service are limited, the uplink service rate to be released = uplink ABR - uplink remaining rate resources of the air interface.

The ABR represents the quantized bit rate value for the service admitted as a kind of resource. To the GBR service, the ABR value equals to the GBR value, and to the
NGBR service, the ABR value equals to the PBR value. The PBR is calculated based on the QCI and local configuration by the eNB. The cell uplink/downlink remaining
rate resources is calculated based on PRB resources and the Spectrum effectiveness by the eNB.

3.2.2.2 Calculation of GBR Rate Downsizing

If the downlink PRB resources of the service are limited, the downlink PRB resources to be released = required downlink PRB resources - downlink remaining PRB
resources of the air interface.

If the uplink PRB resources of the service are limited, the uplink PRB resources to be released = required uplink PRB resources - uplink remaining PRB resources of the air
interface.

The required uplink/downlink PRB resources are calculated based on the ABR of service and the Spectrum effectiveness by the eNB.

3.2.3 Congestion Control Procedure Based on Forced Release

Only the congestion services that have preemption capability but do not have an ARP of 15 can start the forced release procedure. The congestion service will choose the
established GBR service to release, and the number of GBR services that are released forcibly should not exceed the maximum number configured on the EMS.

Services can be released forcibly only when the following conditions are met:

127.0.0.1:8890/web/index.html#?pid=Lib20190202fdd37p&pv=R1_2 3/10
16/4/2020 FDD Congestion Control (LR18+)
1. NGBR services cannot be released forcibly.

2. The ARP of a service to be released forcibly should meet the condition that Pre-emption Vulnerability is pre-emptable, that means the service can be preempted.

3. The ARP of a service to be released forcibly should be lower than that of the congestion service.

4. Emergency services cannot be released forcibly.

If downlink and uplink resources are not enough for the congestion service at the same time, the downlink PRB congestion control procedure should be executed first.

3.2.3.1 Downlink PRB Congestion

For the denied services due to insufficient PRB resources, check whether the congestion service has an ARP of 15 or whether the service has no preemption capability. If
yes, the service is directly rejected. If no, go to downlink PRB congestion control procedure.

The downlink PRB congestion control procedure is as follows:

1. If the congestion switch is set to 1, select services of the local UE that can be released forcibly and add them into forcibly released candidate service list. If the
congestion switch is set to 2, select services of other UEs that can be released forcibly and add them into forcibly released candidate service list.

2. Calculate the resources needed for the service.

3. Select GBR services to be forcibly released according to the rules as follows, output candidate service list. The number of GBR services to be released cannot exceed
AC.preemMaxNumOfGBR.

l The ARPs of selected services to be released forcibly must be lower than the ARP of the congestion service.

l The services to be released forcibly can be preempted.

l The QCIs of the services to be released forcibly are in AC.premptQciRank1

l Preferred low ARP services as the services to be forcibly released, if several services have the same ARP, select the one which has poor spectral efficiency.

4. Take out the GBR service in the candidate service list output by step 3 sequentially, and add into the forcibly release service list, until all services in the forcibly release
service list could satisfy the congestion service’s downlink request. If all services in the forcibly release service list could satisfy the congestion service’s request, then
go to step 7; else, go to step 5.

5. Select GBR services to be forcibly released according to the rules as follows, output candidate service list. The number of GBR services to be released cannot exceed
AC.preemMaxNumOfGBR

l The ARPs of selected services to be released forcibly must be lower than the ARP of the congestion service.

l The services to be released forcibly can be preempted.

l The QCIs of the services to be released forcibly are in AC.premptQciRank2

l Preferred low ARP services as the services to be forcibly released, if several services have the same ARP, selecting the one which has poor spectral efficiency.

6. Take out the GBR service in the candidate service list output by step 5 sequentially, and add into the forcibly release service list, until all services in the forcibly release
service list could satisfy the congestion service’s request. If all services in the forcibly release service list could satisfy the congestion service’s downlink request, and
the size of forcibly release service list is not bigger than AC.preemMaxNumOfGBR, then go to step 7; else, the congestion service is admission rejected, and the
congestion control procedure is end.

7. If all services in the forcibly release service list could satisfy the congestion service’s uplink request, release all the services in the forcibly release service list, the
congestion service is admission success, and the congestion control procedure is end, else, perform an uplink PRB congestion control procedure.

Figure 3‑2 DL PRB Congestion Control Flow

127.0.0.1:8890/web/index.html#?pid=Lib20190202fdd37p&pv=R1_2 4/10
16/4/2020 FDD Congestion Control (LR18+)

3.2.3.2 Uplink PRB Congestion

If neither downlink nor uplink resources are enough for the congestion service, after the downlink congestion control procedure is finished, the uplink congestion control
procedure is executed.

The uplink PRB congestion control procedure is as follows:

1. Check whether the service rejected during admission has an ARP of 15 or whether the service has no preemption capability. If yes, the service is directly rejected. If
no, go to the next step.

2. If the congestion switch is set to 1, select services of the local UE that can be released forcibly and add them into forcibly released candidate service list. If the
congestion switch is set to 2, select services of other UEs that can be released forcibly and add them into forcibly released candidate service list.

3. Calculate the resources needed for the service.

4. If the congestion service has executed the downlink congestion procedure, check whether the uplink resources occupied by the selected GBR services can satisfy the
congestion service. If yes, add the selected GBR services into forcibly released candidate service list. If no, go to the next step.

5. Select GBR services to be forcibly released according to the rules as follows, output the candidate service list. The number of GBR services to be released cannot
exceed AC.preemMaxNumOfGBR.

l The ARPs of selected services to be released forcibly must be lower than the ARP of the congestion service.

l The services to be released forcibly can be preempted.

l The QCIs of the services to be released forcibly are in AC.premptQciRank1.

l Preferred low ARP services as the services to be forcibly released, if several services have the same ARP, selecting the one which has poor spectral efficiency.

6. Take out the GBR service in the candidate service list output by step 3 sequentially, and add into the forcibly release service list, until all services in the forcibly release
service list could satisfy the congestion service’s uplink request. If all services in the forcibly release service list could satisfy the congestion service’s uplink request,
and the size of forcibly release service list is not bigger than AC.preemMaxNumOfGBR, then go to step 9; else, the congestion service is admission rejected, and the
congestion control procedure is end.

7. Select GBR services to be forcibly released according to the rules as follows, output the candidate services to be forcibly released. The number of GBR services to be
released cannot exceed AC.preemMaxNumOfGBR.

l The ARPs of selected services to be released forcibly must be lower than the ARP of the congestion service.

l The services to be released forcibly can be preempted.

l The QCIs of the services to be released forcibly are in AC.premptQciRank2.

l Preferred low ARP services as the services to be forcibly released, if several services have the same ARP, selecting the one which has poor spectral efficiency.

8. Take out the GBR service in the candidate service list output by step 7 sequentially, and add into the forcibly release service list, until all services in the forcibly release
service list could satisfy the congestion service’s uplink request. If all services in the forcibly release service list could satisfy the congestion service’s uplink request,
and the size of forcibly release service list is not bigger than AC.preemMaxNumOfGBR, then go to step 9; else, the congestion service is admission rejected, and the
congestion control procedure is end.

127.0.0.1:8890/web/index.html#?pid=Lib20190202fdd37p&pv=R1_2 5/10
16/4/2020 FDD Congestion Control (LR18+)
9. Release all the services in the forcibly release service list, the congestion service is admission success, and the congestion control procedure is end.

Figure 3‑3 UL PRB Congestion Control Flow

3.2.4 Congestion Control Procedure Based on GBR Rate Downsizing

In GBR rate downsizing procedure, the congestion service will choose the established GBR service to downsizing GBR rate, and the number of GBR services by
downsizing GBR rate cannot exceed the maximum permit number.

For the congestion control process of GBR rate downsizing, refer to the FDD GBR Service Downsizing Feature Guide.

4 Engineering Guide

4.1 Requirements

4.1.1 Hardware Requirements

The cell is normal.

4.1.2 EPC Requirements

No special requirements

4.1.3 Frequency Band, Frequency and Bandwidth Requirements

No special requirements

4.1.4 UE Requirement

No special requirements.

4.1.5 Transmission Bandwidth Requirements

No special requirements.

4.2 Function Activation

4.2.1 Related parameters

Table 4‑1 Configuration Rule of Parameters

127.0.0.1:8890/web/index.html#?pid=Lib20190202fdd37p&pv=R1_2 6/10
16/4/2020 FDD Congestion Control (LR18+)
Parameter Parameter Default
SN Parameter Range value
name explanation value
This parameter
determines
whether the
algorithm is 0:Close,
valid or not. 1:Congestion
Admission Process of
denied does Pre-Empting
not execute Own Service
Switch for congestion Prior,
1 AC.switchForConCtl Congestion process when 2:Congestion 0:close
Control this switch is Process of
close; not Pre-
Admission Empting Own
denied then to Service;
execute 3: GBR
congestion Compression
process when
this switch is
open.
This parameter
Maximum
indicates
Number of
maximum
2 AC.preemMaxNumOfGBR GBR Service [1…3] 2
number of GBR
be
Service be
Preempted
preempted
The first rank of
Pre-emption
QCI. GBR E- 0:None,
The First RABs which 1:QCI1, [QCI2,
3 AC.premptQciRank1 Rank of Pre- QCI in Rank1 2:QCI2, QCI3,
Emption QCI will be 3:QCI3, QCI4,None]
preempted first 4:QCI4
in congestion
control.
The second
rank of Pre-
emption QCI. 0:None,
1:QCI1, [QCI1,
The Second GBR E-RABs
None,
4 AC.premptQciRank2 Rank of Pre- which QCI in 2:QCI2,
None,
Emption QCI Rank1 will be 3:QCI3, None]
preempted first 4:QCI4
in congestion
control.

4.2.2 Parameter Configuration Procedure

4.2.2.1 Configure Switch for Congestion Control

1. Select [Modify Area-> Radio Parameter -> LTE FDD -> E-UTRAN FDD Cell -> Admission Control], click and set Switch for Congestion Control to
Congestion Process of not Pre-Empting Own Service [2], see the figure below. Click to save configuration.

Figure 4‑1 Configuring Switch for Congestion Control

4.2.2.2 Configure Maximum Number of GBR Service Be Preempted

1. Select [Modify Area-> Radio Parameter -> LTE FDD -> E-UTRAN FDD Cell -> Admission Control], click and set Maximum Number of GBR Service Be
Preempted, see the figure below. Click to save configuration.

Figure 4‑2 Configuring Maximum Number of GBR Service Be Preempted

127.0.0.1:8890/web/index.html#?pid=Lib20190202fdd37p&pv=R1_2 7/10
16/4/2020 FDD Congestion Control (LR18+)

4.2.2.3 Configure the First andSecond Ranks of Pre-emption QCI

1. Select Modify Area-> Radio Parameter -> LTE FDD -> E-UTRAN FDD Cell -> Admission Control, click and set The First Rank of Pre-Emption QCI and The
Second Rank of Pre-Emption QCI, see the figure below. Click to save configuration.

Figure 4‑3 Configuring the First Rank of Pre-emption QCI and the Second Rank of Pre-emption QCI

4.2.2.4 Configure the congestion control based on GBR Compression

1. Select Modify Area-> Radio Parameter -> LTE FDD -> E-UTRAN FDD Cell -> Admission Control, click and set Switch for Congestion Control to GBR
Compression[3], see the figure below. Click to save configuration.

Figure 4‑4 Configure the congestion control based on GBR Compression

4.2.3 Disabling the Feature

1. Select Modify Area-> Radio Parameter -> LTE FDD -> E-UTRAN FDD Cell -> Admission Control, click and set Switch for Congestion Control to Close[0],
see the figure below. Click to save configuration.

Figure 4‑5 Close Switch for Congestion Control

127.0.0.1:8890/web/index.html#?pid=Lib20190202fdd37p&pv=R1_2 8/10
16/4/2020 FDD Congestion Control (LR18+)

4.2.4 Data Synchronization

Check the configuration and click Data Synchronization button.

5 Related Counters, KPI and Alarms

5.1 Related Counters

Table 5‑1 Congestion Control Related Counters

SN Counter Num Counter Name

1 Number of QCI1 E-RAB Release by ENB
C373210412 Through E-RAB Release Procedure due to
Cell Congestion
2 Number of QCI2 E-RAB Release by ENB
C373210413 Through E-RAB Release Procedure due to
Cell Congestion
3 Number of QCI3 E-RAB Release by ENB
C373210414 Through E-RAB Release Procedure due to
Cell Congestion
4 Number of QCI4 E-RAB Release by ENB
C373210415 Through E-RAB Release Procedure due to
Cell Congestion
5 Number of QCI5 E-RAB Release by ENB
C373210416 Through E-RAB Release Procedure due to
Cell Congestion
6 Number of QCI6 E-RAB Release by ENB
C373210417 Through E-RAB Release Procedure due to
Cell Congestion
7 Number of QCI7 E-RAB Release by ENB
C373210418 Through E-RAB Release Procedure due to
Cell Congestion
8 Number of QCI8 E-RAB Release by ENB
C373210419 Through E-RAB Release Procedure due to
Cell Congestion
9 Number of QCI9 E-RAB Release by ENB
C373210420 Through E-RAB Release Procedure due to
Cell Congestion
10 Number of E-RAB Release by ENB
C373210421 Through E-RAB Release Procedure due to
Cell Congestion
11 Number of Successful Triggered Cell DL
C373404450
Congestion
12 Number of Triggered Cell DL Congestion
C373404451
Failure
13 Number of Successful Triggered Cell UL
C373404466
Congestion
14 Number of Triggered Cell UL Congestion
C373404467
Failure

5.2 Related KPI

None

5.3 Related Alarms

None

127.0.0.1:8890/web/index.html#?pid=Lib20190202fdd37p&pv=R1_2 9/10
16/4/2020 FDD Congestion Control (LR18+)

6 Impact on Network

6.1 Gain Analysis

When this function is enabled, the services with low priority will be forcibly released to ensure the services with high priority when the system resources are limited. With
GBR service downsizing technology, the system capacity can be maximized, which may affect online uses experience to some extent.

The services with low priority are forcibly released, which leads to E-RAB calldrop rate increases.

6.2 Impact Analysis

When system resource of the cell is limited and congestion occurs, to ensure the services with high priority, E-RAB call drop may increase, the services with low priority are
forcibly released, which leads to E-RAB call drop rate increases.

When system resource of the cell is limited and congestion occurs, to ensure the services with high priority, the forcibly released resources and GBR service downsizing
lead to the decrease of the preempted user rate, resulting in PRB usage decrease.

7 Abbreviations
For the acronyms and abbreviations, see LTE Glossary.

8 References
1. 3GPP TS 23.203, "Policy and charging control architecture"
2. 3GPP TS 23.401, "General Packet Radio Service (GPRS) enhancements for Evolved
3. Universal Terrestrial Radio Access Network (E-UTRAN) access"
4. 3GPP TS 36.306, "User Equipment (UE) radio access capabilities"
5. 3GPP TS 36.321, "Medium Access Control(MAC) protocol specification"
6. 3GPP TS 36.331, "Radio Resource Control (RRC)"
7. 3GPP TS 36.413, "S1 Application Protocol (S1AP)"
8. FDD Admission Control Feature Guide.
9. FDD GBR Service Downsizing Feature Guide.

127.0.0.1:8890/web/index.html#?pid=Lib20190202fdd37p&pv=R1_2 10/10