ZTE LR14 LTE FDD Congestion Control Feature Guide

ZTE LTE FDD Congestion
Control Feature Guide

LR14
ZTE LTE FDD Congestion Control Feature Guide
Version Date Author Reviewer Notes
Sun
Lianqiao
V1.0 2013/10/16 Li Nana First edition
Kang
Hongdan
Li Bo
Added the contents about GBR rate
Kang downsizing.
V2.0 2014/06/30 Li Nana
Hongdan
Added the chapter 5.
Li Shikai
Li Nana Add Chapter 7: Impact on Network
V3.0 2014-12-23 Li Bo
Bian Guangfeng Change some expressions
Parameter configuration interface update
Kang to eNodeB V3.20.50.20
V3.1 2015-01-22 Zhang Fan
Hongdan
Change the word template
2015 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used
without the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document is subjected to
change without notice.
ZTE Confidential Proprietary 2015 ZTE CORPORATION. All rights reserved. I

TABLE OF CONTENTS
1 Introduction........................................................................................................ 1
1.1 Scope ................................................................................................................... 1
1.2 Target Group ........................................................................................................ 1
1.3 Feature Attribute .................................................................................................. 1
1.4 Correlation with Other Features ........................................................................... 2
2 Definitions .......................................................................................................... 2
3 Technical Description ....................................................................................... 3

3.1 Feature Introduction ............................................................................................. 3
3.2 Technical Details .................................................................................................. 4
3.2.1 Relationship between Congestion and Admission ................................................ 4
3.2.2 Calculation of Released Resources...................................................................... 4
3.2.3 Congestion Control Procedure Based on Forced Release ................................... 6
3.2.4 Congestion Control Procedure Based on GBR Rate Downsizing ....................... 11
4 Parameter Configurations ............................................................................... 12

4.1 Parameters List .................................................................................................. 12
4.2 Parameter Configuration Rule ............................................................................ 12
4.3 Parameter Configuration Procedure ................................................................... 14
4.3.1 Enabling the Feature .......................................................................................... 14
4.3.2 Configuring the Other Related Parameters......................................................... 14
4.3.3 Disabling the Feature ......................................................................................... 16
4.3.4 Data Save and Synchronization ......................................................................... 16
5 Feature Validation............................................................................................ 17
5.1 Downlink PRB Congestion ................................................................................. 17
5.1.1 Topology ............................................................................................................ 17
5.1.2 Test Specification ............................................................................................... 18
5.1.3 Test Result ......................................................................................................... 20
5.2 Uplink PRB Congestion ...................................................................................... 24
5.2.1 Topology ............................................................................................................ 24
5.2.2 Test Specification ............................................................................................... 24
5.2.3 Test Result ......................................................................................................... 26
6 Related Counters, KPI, and Alarms ................................................................ 30

6.1 Related Counters ............................................................................................... 30
6.2 Related KPI ........................................................................................................ 30
6.3 Related Alarms................................................................................................... 30
7 Impact on Network........................................................................................... 30
8 Abbreviations................................................................................................... 31
FIGURES
Figure 3-1 Congestion Control Flow ..................................................................................... 3

Figure 3-2 Relationship between Admission and Congestion Control................................... 4
Figure 3-3 DL PRB Congestion Control Flow ....................................................................... 8
Figure 3-4 UL PRB Congestion Control Flow ..................................................................... 11
Figure 4-1 Configuring Switch for Congestion Control ........................................................ 14
Figure 4-2 Configuring Maximum Number of GBR Service Be Preempted ......................... 15
Figure 4-3 Configuring the First Rank of Pre-emption QCI and the Second Rank of
Pre-emption QCI................................................................................................................... 16
Figure 4-4 Data Synchronization Dialog Box ...................................................................... 17
Figure 5-1 Topology for PRB congestion feature testing .................................................... 18
Figure 5-2 Establish the dedicated bearers for UE2 ........................................................... 21
Figure 5-4 Dedicated bearer of UE1 was established unsuccessfully ................................. 22
Figure 5-5 Dedicated bearer of UE1 is established successfully ........................................ 23
Figure 5-6 The dedicated bearer of UE2 is released because reducing load ...................... 23
Figure 5-9 The dedicated bearer of UE1 was established unsuccessfully .......................... 28
Figure 5-10 The dedicated bearer of UE1 is established successfully ................................ 29
Figure 5-11 The dedicated bearer of UE2 is released because reducing load .................... 30
TABLES
Table 1-1 Correlation with Other Features ........................................................................... 2

Table 4-1 Parameters List .................................................................................................. 12
Table 4-2 Configuration Rule of Parameters ...................................................................... 12
Table 5-1 Test Equipment .................................................................................................. 18
Table 5-2 Downlink PRB Congestion Test ......................................................................... 18
Table 5-3 Uplink PRB Congestion ...................................................................................... 24
ZTE Confidential Proprietary 2015 ZTE CORPORATION. All rights reserved. III
1 Introduction
1.1 Scope
This document describes the congestion control technology (feature), including technical
description, algorithm flow, performance gain, application scenario, key parameters and
configuration, related counters, KPI statistics, alarms, and function verification.
1.2 Target Group
This document is intended for:
Personnel who need to understand FDD Congestion Control function
Personnel who work with ZTE products
1.3 Feature Attribute
For FDD single-mode eNodeB V3.20.50.20 series:
OMMB version: V12.13.58
EMS version: V12.13.58
For GUL multi-mode eNodeB V4.13.15 series:
OMMB version: V12.13.52
EMS version: V12.13.51
Note:
ZTE Confidential & Proprietary 1

FDD single-mode V3.20.50.20 corresponds to GUL multi-mode V4.13.15, and LTE

technology description and operation requirements in the corresponding versions are the
same.
Involved NEs:
UE eNodeB MME S-GW BSC/RNC SGSN P-GW HSS
- - - - -
Note:
*-: Not involved
*: involved
1.4 Correlation with Other Features
Table 1-1 Correlation with Other Features
Feature Feature Name Required Mutually Affected

ID Feature Exclusive Feature
Feature
ZLF31-08-004 Congestion Control None None None
2 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.
2 ZTE Confidential & Proprietary

3 Technical Description
3.1 Feature Introduction
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 background.
The congestion control flow is shown in Figure 3-1.
Figure 3-1 Congestion Control Flow
The Switch for Congestion Control (short name switchForConCtl) is used to enable or
disable the congestion control feature. The parameter switchForConCtl can be set to 0, 1,
2, or 3. If it is set to 0, the congestion control feature is disabled. If it is set to 1, 2, or 3,
the congestion control feature is enabled. The values 1 and 2 indicate forced release,
and 3 indicates downsizing the rate of GBR services.

3.2 Technical Details
3.2.1 Relationship between Congestion and Admission
As shown in Figure 3-2, 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.
Figure 3-2 Relationship between Admission and Congestion Control
Downlink PRB Admission Force downsizing the GBR

Failure rate of low priority Service
Output
High priority Uplink PRB Admission Force releasing low priority

Highrequest
Service priority Failure Service
Service request
3.2.2 Calculation of Released Resources
If the switch 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 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 Forced Release
If a service in the congestion queue fails to be admitted during E-RAB setup, the ABR of
a GBR service is equal to the GBR of the service, and the ABR of an NGBR service is
equal to the PBR of the service.

If a service fails to be admitted during E-RAB modification, the ABR of a GBR service is
equal to GBR, and the ABR of an NGBR service is equal to PBR. is the difference
between rates before and after the E-RAB modification.
The remaining rate resources of the air interface of the cell are calculated in accordance
with the spectral efficiency and remaining PRB resources maintained by the admission
control feature.
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.
3.2.2.2 GBR Rate Downsizing
If a service fails to be admitted during E-RAB setup, its ABR is equal to the GBR or PBR.
The PRB resources needed for the service are calculated in accordance with the service
type and QCI.
If a service fails to be admitted during E-RAB modification, its ABRs before and after
modification are equal to GBR or PBR respectively. The PRB resources to be occupied
by the service before and after modification are calculated in accordance with the service
type and QCI. The difference is PRB, which is the PRB resources needed for the
service.
The remaining PRB resources of the air interface of the cell are maintained by the
admission control feature.
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.

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:
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 congestion control procedure should be execut first.
3.2.3.1 Downlink PRB Congestion
The downlink PRB congestion control procedure is as follows:
1. 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 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. Select GBR services to be forcibly released in accordance with the following

conditions. The number of GBR services to be released cannot exceed
preemMaxNumOfGBR (Parameter name Maximum Number of GBR Service be
Preempted).
The ARPs of selected services to be released forcibly must be lower than the
ARP of the congestion service.
The services to be released forcibly can be preempted.
The QCIs of the services to be released forcibly are in PremptQciRank1

(Parameter name The First Rank of Pre-Emption QCI).
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.
5. Check whether the resources occupied by the selected GBR services can satisfy
the congestion services request. If yes, add the GBR services into orcibly released
candidate service list and go to step 8. If no, go to the next step.

preemMaxNumOfGBR.
The QCIs of the services to be released forcibly are in

PremptQciRank2(Parameter name The Second Rank of Pre-Emption QCI).

efficiency.

7. Check whether the rate resources occupied by the selected GBR services can
satisfy the congestion services request. If yes, go to the next step. If no, the new
service is refused.
8. Check whether uplink PRB resources are limited for the new service. If yes, perform
an uplink PRB congestion control procedure. If no, the selected GBR services in
forcibly released candidate service list will be released and the new service is
admitted.
Figure 3-3 DL PRB Congestion Control Flow
Admission refusal service

for DL PRB resource limited
According to the ucConSwitch to generate the candidate

service queue
Select break GBR satisfing Forced releasing Condition and

QCI in aucPremptQciRank1[4] and output releasing
candidate Erab list.
Y
Downlink PRB Congestion is resolved?
Select break GBR of other UE satisfing Forced releasing

Condition and QCI in aucPremptQciRank2[4] and output
releasing candidate Erab list.
Y
Downlink PRB Congestion is resolved?
N
The Admission service is rejected
by UL PRB resource limited?
Y
N
Output breaking
selected GBR services Break selected GBR
and execut UL PRB The service will be
services and access
congestion process rejected.
the service

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. If only the uplink resources are not enough for the congestion
service, directly execute the uplink congestion control procedure.
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 and go to step 8. If no, go to the next step.

preemMaxNumOfGBR.
The QCIs of the services to be released forcibly are in PremptQciRank1.

efficiency.

the congestion service. If yes, add the selected GBR services into forcibly
released candidate service list and go to step 8.. If no, go to the next step.

preemMaxNumOfGBR.
The QCIs of the services to be released forcibly are in PremptQciRank2.

efficiency.
the congestion service (the total number of services forcibly released must be less
than or equal to preemMaxNumOfGBR). If yes, the selected GBR services in
forcibly released candidate service list will be released and the new service is
admitted. If no, the new service is refused.

Figure 3-4 UL PRB Congestion Control Flow
Admission refusal service

for uplink prb limited
According to the ucConswitch to generate candidate

the service queue.
Evaluate needed uplink releasing resource for

admission refusal service.
Break GBR service list for uplink PRB Congestion is null?
Uplink resource of the break GBR service list

can fulfill needed uplink resource of service?
Y
N
Select break GBR erab of other UE satisfing forced

releasing Condition and QCI in PremptQciRank1 and output
releasing candidate erab list.
Uplink PRB Congestion is resolved?

Y
N
Select break GBR of other UE satisfing Forced

releasing Condition and QCI in PremptQciRank2
Y and output releasing candidate Erab list.
Y Uplink PRB Congestion is resolved?
Break selected GBR

The service will be
services and access
rejected.
the service
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 ZTE LTE FDD
GBR Rate Downsizing Feature Guide.
4 Parameter Configurations
4.1 Parameters List
Table 4-1 Parameters List
SN Name Figure
1 Switch for Congestion Control Figure 4-1
2 Maximum Number of GBR Service be Preempted Figure 4-2
3 The First Rank of Pre-Emption QCI Figure 4-3
4 The Second Rank of Pre-Emption QCI Figure 4-3
4.2 Parameter Configuration Rule
Table 4-2 Configuration Rule of Parameters
S MO Default
Name Description Value Range
N Name Value

1 This parameter
determines
whether the
algorithm is valid
0:Close,1:Congestion
or not. Admission
Process of
denied dont
Switch for Pre-Empting Own
execute
Congesti Service
AC congestion Close[0]
on Prior,2:Congestion
process when this
Control Process of not
switch is close;
Pre-Empting Own
Admission denied
Service
execute
congestion
process when this
switch is open.
2 Maximum
number This parameter
of GBR indicates
AC Service maximum number [13] 2
be of GBR Service
preempte be preempted
d
3 The first rank of

Pre-emption QCI.
The first GBR E-RABs QCI2[2];
rank of which QCI in 0:None,1:QCI1,2:QCI2 QCI3[3];
AC
pre-empti Rank1 will be ,3:QCI3,4:QCI4 QCI4[4];
on QCI preempted first in None[0]
congestion
control.
4 The second rank

of Pre-emption
The
QCI. GBR QCI1[1];
second
E-RABs which 0:None,1:QCI1,2:QCI2 None[0];
AC rank of
QCI in Rank1 will ,3:QCI3,4:QCI4 None[0];
pre-empti
be preempted first None[0]
on QCI
in congestion
control.

4.3 Parameter Configuration Procedure
4.3.1 Enabling the Feature
To test the congestion control algorithm, perform the following steps:
1. In the Configuration Management window of the EMS, select [Modify Area-> Radio
Parameter -> LTE FDD -> E-UTRAN FDD Cell -> Admission Control].
2. Click , and then set Switch for congestion control to Congestion process of not
Pre-empting Own Service [2], as shown in Figure 4-1.
3. Click on the toolbar.
Figure 4-1 Configuring Switch for Congestion Control
4.3.2 Configuring the Other Related Parameters
To test the algorithm that determines the maximum number of allowable preempted
services, perform the following steps:

2. Click , and then configure Maximum number of GBR service be preempted,
as shown in Figure 4-2.
Figure 4-2 Configuring Maximum Number of GBR Service Be Preempted
To test the algorithm that determines QCI rank of released services, perform the
following steps:
2. Click , and then configure the first rank of pre-emption QCI and The second
rank of pre-emption QCI, as shown in Figure 4-3.
3. Click .

Figure 4-3 Configuring the First Rank of Pre-emption QCI and the Second Rank of
Pre-emption QCI
4.3.3 Disabling the Feature
To disable the congestion control feature, perform the following steps:
1. In the Configuration Management window of the EMS, select [Modify Area->

Radio Parameter -> LTE FDD -> E-UTRAN FDD Cell -> Admission Control].
2. Click , and then set Switch for congestion control to close [0].
4.3.4 Data Save and Synchronization
1. After modified the parameters, click to save all the data.
2. In the NE Management tab, select the eNodeB agent node. Then click the
Configuration Management button on the upper left of the Configuration
Management tab, and select Data Synchronization from the drop-down list. The
Data Synchronization dialog box is displayed, see Figure 4-4.

Figure 4-4 Data Synchronization Dialog Box
3. Select the NE to which the configuration data is to be distributed, which is eNodeB

3056 in this example. Set the synchronization parameters, and then click
Synchronize.
The Confirm dialog box is displayed, prompting for the verification code.
4. Enter the verification code, and click OK. The system starts to synchronize all
parameters to eNodeB. When 100% is displayed in the Progress column, it
indicates that the synchronization is completed.
5 Feature Validation
5.1 Downlink PRB Congestion
5.1.1 Topology
The topology for PRB congestion feature testing is shown in Figure 5-1.

Figure 5-1 Topology for PRB congestion feature testing
eNB IP bone
PGW
MME / S-GW
SGW / DHCP Relay
PDN Server
Test equipment is shown in Table 5-1.
Table 5-1 Test Equipment
SN Test Equipment Requirement
1 eNodeB Number:1
2 UE Number:2
3 MME Number:1
4 PGW Number:1
5 PDN server Number:1
5.1.2 Test Specification
Table 5-2 Downlink PRB Congestion Test
Test Item Downlink PRB congestion test
To verify the function of Downlink Congestion Control can be

Test Purpose
support by system.
EUTRAN works normally;

EPC works normally;
Application server runs normally;
Preparations
OMC works normally;
UEs are prepared and work normally;
Test tools of eNodeB side and UE side are available;

Main parameter is listed as follow:
Parameter Name Value Remark
Admission control
N/A
Switch for Congestion Control Close
Maximum Number of GBR N/A

2
Service be Preempted
The First Rank of Pre-Emption N/A

2;3;4;0
QCI
The Second Rank of N/A

1;0;0;0
Pre-Emption QCI
E-UTRAN FDD Cell
Downlink System Bandwidth 10(50RB)[3] N/A
Uplink System Bandwidth 10(50RB)[3] N/A
Others Default value N/A
The QoS parameters are as follows:
UE1 UE2
QCI 1 2
ARP 2 12
DL GBR 40 40
UL GBR 10 10
DL MBR 40 40
UL MBR 10 10
pre-emption vulnerability 1 0
pre-emption capability 0 1
Test Step Expected Result
1 Place 2 UEs to the cell center. None
Start test tool of eNodeB and UE

2 Test tools work normally;
side to record the test log.
Power on UEs and make sure that Cell ID of serving cell can be seen at UE
3
the UEs camp on the serving cell. side;

Initiate Attach operation from UEs

4 UE access FDD cell successfully;
side;
Establish the dedicated bearers for Dedicated bearers setup successfully for
UE2 as GBR service based on the UE2;
5
parameters above table. Check QoS information in E-RAB Setup
Request
Generate UDP downlink service

6 The downlink throughput are 40Mbps.
with IPERF tool, 40 Mbps for UE2.
Establish a dedicated bearer for

The dedicated bearer for UE1 setup
7 UE1 as GBR service based on the
unsuccessfully.
parameters table in precondition 8.
Observe and record the throughput

of the dedicated bearer, record
8 signaling between UE side and None
eNodeB side, record the screen
capture
Delete dedicated bearers of UE1,

The dedicated bearers are deleted
9 UE2 which established above
successfully.
steps
Configure Switch for Congestion

10 Control as Congestion Process of The parameter is configured successfully.
not Pre-Empting Own Service[2].
The dedicated bearer setup successfully

for UE1;
11 Repeat the step 5 to 8
The dedicated bearer release
successfully for UE2.
After congestion control is set as open, when system resource is

Anticipative
congestion, the bearer with lower priority ARP will be released, and
Result
meanwhile the bearer with higher priority ARP will be setup.
5.1.3 Test Result
1. When the switch for congestion control is configured close[0], establish the
dedicated bearers for UE2, as shown in Figure 5-2.

Figure 5-2 Establish the dedicated bearers for UE2
2. Establish the dedicated bearers for UE1, as shown in Figure 5-2.

3. The dedicated bearer of UE1 is established unsuccessfully because radio resource

was not available, as shown in Figure 5-4.
Figure 5-4 Dedicated bearer of UE1 was established unsuccessfully
4. When the switch for congestion control is configured Congestion Process of not
Pre-Empting Own Service[2], the dedicated bearer of UE1 is established
successfully, as shown in Figure 5-5.

Figure 5-5 Dedicated bearer of UE1 is established successfully
5. The dedicated bearer of UE2 is released because reducing load, as shown in

Figure 5-6.
Figure 5-6 The dedicated bearer of UE2 is released because reducing load

5.2 Uplink PRB Congestion
5.2.1 Topology
Please refer to section 5.1.1 Topology.
5.2.2 Test Specification
Table 5-3 Uplink PRB Congestion
Test Item Uplink PRB congestion test
To verify the function of Uplink Congestion Control can be support

Test Purpose
by system.
EUTRAN works normally;

EPC works normally;
Application server runs normally;
OMC works normally;
UEs are prepared and work normally;
Test tools of eNodeB side and UE side are available;
Main parameter is listed as follow:
Parameter Name Value Remark
Admission control
N/A
Switch for Congestion Control Close
Preparations
Maximum Number of GBR N/A
2
Service be Preempted
The First Rank of Pre-Emption N/A

2;3;4;0
QCI
The Second Rank of N/A

1;0;0;0
Pre-Emption QCI
E-UTRAN FDD Cell
Downlink System Bandwidth 10(50RB)[3] N/A
Uplink System Bandwidth 10(50RB)[3] N/A

Others Default value N/A
The QoS parameters are as follows:
UE1 UE2
QCI 1 2
ARP 2 12
DL GBR 10 10
UL GBR 20 20
DL MBR 10 10
UL MBR 20 20
pre-emption vulnerability 0 0
pre-emption capability 1 1
Test Step Expected Result
1 Place 2 UEs to the cell center. None
Start test tool of eNodeB and UE

2 Test tools work normally;
side to record the test log.
Power on UEs and make sure that Cell ID of serving cell can be seen at UE
3
the UEs camp on the serving cell. side;
Initiate Attach operation from UEs

4 UE access FDD cell successfully;
side;
Establish the dedicated bearers for Dedicated bearers setup successfully for
UE2 as GBR service based on the UE2;
5
parameters above table. Check QoS information in E-RAB Setup
Request
Generate UDP uplink service with

6 The uplink throughput are 20Mbps.
IPERF tool, 20 Mbps for UE2.
Establish a dedicated bearer for

The dedicated bearer for UE1 setup
7 UE1 as GBR service based on the
unsuccessfully.
parameters table in precondition 8.
Observe and record the throughput

of the dedicated bearer, record
8 signaling between UE side and None
eNodeB side, record the screen
capture

Delete dedicated bearers of UE1,

The dedicated bearers are deleted
9 UE2 which established above
successfully.
steps
Configure Switch for Congestion

10 Control as Congestion Process of The parameter is configured successfully.
not Pre-Empting Own Service[2].
The dedicated bearer setup successfully

for UE1;
11 Repeat the step 5 to 8
The dedicated bearer release
successfully for UE2.
After congestion control is set as open, when system resource is

Anticipative
congestion, the bearer with lower priority ARP will be released, and
Result
meanwhile the bearer with higher priority ARP will be setup.
5.2.3 Test Result
1. When the switch for congestion control is configured close[0], establish the
dedicated bearers for UE2, as shown in Figure 5-7.

2. Establish the dedicated bearers for UE1, as shown in Figure 5-8.

3. The dedicated bearer of UE1 is established unsuccessfully because radio resource

was not available, as shown in Figure 5-9.
Figure 5-9 The dedicated bearer of UE1 was established unsuccessfully

4. When the switch for congestion control is configured Congestion Process of not
Pre-Empting Own Service[2], the dedicated bearer of UE1 is established
successfully, as shown in Figure 5-10.
Figure 5-10 The dedicated bearer of UE1 is established successfully
5. The dedicated bearer of UE2 is released because reducing load, as shown in

Figure 5-11.

Figure 5-11 The dedicated bearer of UE2 is released because reducing load
6 Related Counters, KPI, and Alarms
6.1 Related Counters
None
6.2 Related KPI
None
6.3 Related Alarms
None
7 Impact on Network
Impact on Equipment Performance

None
Impact on Network KPIs
Advantages of this feature:
If access is not permitted due to congestion, this feature allows the system to release
some resources for the new service. This feature can increase the service access ratio,
improve user experience of new subscribers who has high priority.
Disadvantages of this feature:
User experience of subscribers with lower priorities degrades due to forcible release or
rate downgrade in case of congestion.
8 Abbreviations
For the acronyms and abbreviations, see LTE Glossary.

ZTE LR14 LTE FDD Congestion Control Feature Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ZTE LR14 LTE FDD Congestion Control Feature Guide

Uploaded by

Copyright:

Available Formats

ZTE LTE FDD Congestion

Control Feature Guide

2015 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary 2015 ZTE CORPORATION. All rights reserved. I

3 Technical Description ....................................................................................... 3

4 Parameter Configurations ............................................................................... 12

6 Related Counters, KPI, and Alarms ................................................................ 30

Figure 3-1 Congestion Control Flow ..................................................................................... 3

Table 1-1 Correlation with Other Features ........................................................................... 2

1.2 Target Group

This document is intended for:

Personnel who need to understand FDD Congestion Control function

Personnel who work with ZTE products

1.3 Feature Attribute

For FDD single-mode eNodeB V3.20.50.20 series:

OMMB version: V12.13.58

EMS version: V12.13.58

For GUL multi-mode eNodeB V4.13.15 series:

OMMB version: V12.13.52

EMS version: V12.13.51

ZTE Confidential & Proprietary 1

FDD single-mode V3.20.50.20 corresponds to GUL multi-mode V4.13.15, and LTE

1.4 Correlation with Other Features

Table 1-1 Correlation with Other Features

Feature Feature Name Required Mutually Affected

ZLF31-08-004 Congestion Control None None None

2 ZTE Confidential & Proprietary

3.1 Feature Introduction

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

Figure 3-1 Congestion Control Flow

ZTE Confidential & Proprietary 3

3.2 Technical Details

3.2.1 Relationship between Congestion and Admission

As shown in Figure 3-2, if a service fails to be admitted due to insufficient uplink or

Figure 3-2 Relationship between Admission and Congestion Control

Downlink PRB Admission Force downsizing the GBR

High priority Uplink PRB Admission Force releasing low priority

3.2.2 Calculation of Released Resources

3.2.2.1 Forced Release

4 ZTE Confidential & Proprietary

3.2.2.2 GBR Rate Downsizing

ZTE Confidential & Proprietary 5

3.2.3 Congestion Control Procedure Based on Forced Release

1. NGBR services cannot be released forcibly.

4. Emergency services cannot be released forcibly.

3.2.3.1 Downlink PRB Congestion

The downlink PRB congestion control procedure is as follows:

3. Calculate the resources needed for the service.

6 ZTE Confidential & Proprietary

4. Select GBR services to be forcibly released in accordance with the following

The services to be released forcibly can be preempted.

The QCIs of the services to be released forcibly are in PremptQciRank1

Preferred low ARP services as the services to be forcibly released, if several

6. Select GBR services to be forcibly released in accordance with the following

The services to be released forcibly can be preempted.

The QCIs of the services to be released forcibly are in

Preferred low ARP services as the services to be forcibly released, if several

ZTE Confidential & Proprietary 7

Figure 3-3 DL PRB Congestion Control Flow

Admission refusal service

According to the ucConSwitch to generate the candidate

Select break GBR satisfing Forced releasing Condition and

Select break GBR of other UE satisfing Forced releasing

8 ZTE Confidential & Proprietary