Beruflich Dokumente
Kultur Dokumente
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
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
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
7 Impact on Network........................................................................................... 30
8 Abbreviations................................................................................................... 31
FIGURES
TABLES
ZTE Confidential Proprietary 2015 ZTE CORPORATION. All rights reserved. III
ZTE LTE FDD Congestion Control Feature Guide
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.
Note:
Involved NEs:
UE eNodeB MME S-GW BSC/RNC SGSN P-GW HSS
- - - - -
Note:
*-: Not involved
*: involved
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.
3 Technical 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 background.
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.
Output
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.
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.
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.
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:
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.
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.
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.
The ARPs of selected services to be released forcibly must be lower than the
ARP of the congestion service.
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.
The ARPs of selected services to be released forcibly must be lower than the
ARP of the congestion service.
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.
Y
Downlink PRB Congestion is resolved?
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
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.
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.
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.
The ARPs of selected services to be released forcibly must be lower than the
ARP of the congestion service.
6. Check whether the 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.
The ARPs of selected services to be released forcibly must be lower than the
ARP of the congestion service.
8. Check whether the resources occupied by the selected GBR services can satisfy
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.
Y
N
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
SN Name Figure
1 Switch for Congestion Control Figure 4-1
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
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
To test the algorithm that determines the maximum number of allowable preempted
services, 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].
To test the algorithm that determines QCI rank of released services, 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 configure the first rank of pre-emption QCI and The second
3. Click .
Figure 4-3 Configuring the First Rank of Pre-emption QCI and the Second Rank of
Pre-emption QCI
2. Click , and then set Switch for congestion control to close [0].
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.
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.1 Topology
The topology for PRB congestion feature testing is shown in Figure 5-1.
eNB IP bone
PGW
MME / S-GW
SGW / DHCP Relay
PDN Server
1 eNodeB Number:1
2 UE Number:2
3 MME Number:1
4 PGW Number:1
Admission control
N/A
Switch for Congestion Control Close
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
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;
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
1. When the switch for congestion control is configured close[0], establish the
dedicated bearers for UE2, as shown in Figure 5-2.
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-6 The dedicated bearer of UE2 is released because reducing load
5.2.1 Topology
Admission control
N/A
Switch for Congestion Control Close
Preparations
Maximum Number of GBR N/A
2
Service be Preempted
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
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;
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
1. When the switch for congestion control is configured close[0], establish the
dedicated bearers for UE2, as shown in Figure 5-7.
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-11 The dedicated bearer of UE2 is released because reducing load
None
None
None
7 Impact on Network
Impact on Equipment Performance
None
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.
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.