Progressive Access Barring

Feature Description

337/221 04-LZA 701 6014/1 Uen BH

Copyright

© Ericsson AB 2017–2022. All rights reserved. No part of this document may be

reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use of this
document.

Trademark List

All trademarks mentioned herein are the property of their respective owners.
These are shown in the document Trademark Information.

337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13

 Contents

Contents

1 Overview 1

2 Dependencies 3
2.1 Compatibility of Load Balancing and Automatic Access
Barring 5

3 Feature Operation 7
3.1 Access Class Barring Functionalities 13

4 Network Impact 22

5 Parameters 23

6 Performance 26

7 Activate 27

8 Deactivate 28

9 Engineering Guidelines 29

337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13

Progressive Access Barring

337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13

1 Progressive Access Barring Overview

The feature introduces priority levels for calculating barring factors and
mapping traffic classes.

Access Type: LTE

Feature Identity: FAJ 121 4746
Value Package Name: High Load Handling
Value Package Identity: FAJ 801 0415
Node Type: Baseband Radio Node
Licensing: Licensed feature. One license for each
node.

Summary
The Progressive Access Barring feature introduces three different priority levels
for the calculation of barring factors used for access class barring signaled in
SIB2. It also introduces the possibility to map the following five different traffic
classes to any of the priority levels:
— Mobile Originating Data

— Mobile Originating Signaling

— CSFB

— MMTEL Voice

— MMTEL Video

It is also possible to configure a traffic class to never be barred, so there is an

implicit fourth priority level. In addition to the five traffic classes above, the
following traffic classes can be configured to never be barred, which means that
they are given higher priority than any traffic class that is mapped to the first
three priority levels:

— SMS

— Access class 10-15, each can be individually configured to always be barred

or never barred

Additional Information
For information on the preferred state and parameter settings of this feature, see
RAN Parameter Recommendations Lists.

337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13 1

 Progressive Access Barring

For more information about this feature and related topics, see 3GPP TS 24.173.

2 337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13

2 Dependencies of Progressive Access Barring

The feature has dependencies with other features related to access barring,
idle mode support, and load control.

Features

Table 1 Feature Dependencies

Feature Relationship Description
Load-Based Access Barring Prerequisite Load-Based Access Barring is a prerequisite to
(FAJ 121 3093) Progressive Access Barring. If Progressive Access
Barring is activated, Load-Based Access Barring is
replaced by it to avoid further congestion. As
opposed to Load-Based Access Barring, in
Progressive Access Barring it is possible to set
different priority levels of traffic classes and
configure different maximum barring probability.
Idle Mode Support (Part of Related The Idle Mode Support feature makes manual access
LTE Basic) class barring possible both for the common and the
PLMN-specific access class barring parameters
without any license.
The following configurations exist for the presence
attribute for each access class barring parameter in
the AcBarringPresence struct:

— OFF

— MANUAL

— AUTO

If the presence of an access attempt type is set to

MANUAL, manual access class barring is applied. If the
presence is set to AUTO, automatic access class
barring functionality is started automatically when
the system becomes congested. The barring factor is
recalculated periodically and sent to the UEs in the
SIB2 message until the system is not congested.
Then the automatic access class barring mechanism
is stopped.
Inter-Frequency Load Related When the Inter-Frequency Load Balancing feature is
Balancing (FAJ 121 3009) used together with automatic access class barring,
the cell stops broadcasting its load status to other
cells. It is removed from the list of candidates for
inter-frequency load balancing. This is to avoid
handover to an already overloaded cell. The load
measurement is ongoing to enable the outgoing
handover to other cells, and to decrease the load
faster. If load balancing during access class barring is
disabled, all inter-frequency load balancing
processes are disabled in the cell.
MME Overload Control (FAJ Related MME Overload Control increases the number of
121 3097) rejected UEs while MMEs are in overload state. This
can trigger automatic access barring, and activate
the presence of access class barring parameters in
SIB2 due to increased ratio of RRC Connection
Rejects.
PLMN-Specific Access Barring Related The Progressive Access Barring feature is required
(FAJ 121 4916) for the following functions of the PLMN-Specific
Access Barring feature:

— PLMN Progressive Access Barring

337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13 3

 Progressive Access Barring

Feature Relationship Description

— Prioritized PLMN Progressive Access Barring
Progressive Barring for Related The Progressive Access Barring feature is a
Special Access Classes (FAJ prerequisite feature of Progressive Barring for
121 4917) Special Access Classes feature. If Progressive Access
Barring feature is deactivated, Progressive Barring
for Special Access Classes feature is unable to
operate. This feature introduces the possibility to
automatically bar Special Access Classes. The
following two new priority levels for the five traffic
classes:

— PRIORITY3

— PRIORITY4

introduces possibility to automatically bar special

Access Classes (AC 10..15) in those priority levels.
Inter-Frequency Offload (FAJ Conflicting Subscription ratio measurements are disabled when
121 3061) automatic access class barring is triggered. In case of
no subscription ratio measurements, outgoing Inter-
Frequency Offload is disabled.

Hardware
No specific hardware requirements.

Limitations
No known limitations.

Other Network Elements

This feature requires UEs to support the following IEs introduced in Release 12
RRC 36.331:
— ac-BarringSkipForMMTelVoice-r12

— ac-BarringSkipForMMTelVideo-r12

Release 9/10/11 UEs only support SSAC but not above IEs used for skipping.
These UEs pass the barring procedure twice, the IMS/MMTel and RRC layer,
before trying the RRC connection request. This means that voice and video
accessibility can be degraded for Release 9/10/11 UEs when Progressive Access
Barring is activated in severe overload situations. Release 8 UEs ignore both
SSAC and Access Class Barring skip and use MoData barring for voice and video.
For more information, see Release 9/10/11/12 3GPP TS 36.331.

4 337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13

2.1 Compatibility of Load Balancing and Automatic Access
Barring
During ongoing automatic access class barring calculation mechanism,
inter-frequency load balancing for incoming handover is disabled in the cell.

When automatic access class barring is used together with Inter-Frequency Load
Balancing, the incoming handover to an overloaded cell is disabled.

Inter-frequency load balancing is enabled in the cell when the barring probability
reaches 0.

If load balancing during access class barring is enabled, that is

[Link] or [Link] is set to
true, the following events occur:

— The subscription ratio measurements are still ongoing in the cell when the
automatic access class barring calculation mechanism is triggered.

— The function enables the cell for outgoing load balancing handover, and a
faster recovery from overload.

— Triggering of the access class barring calculation mechanism does not

disable subscription ratio evaluation and Inter-Frequency Load Balancing.

If the Preferential Traffic Management solution is enabled, by setting the

[Link] attribute to true, and the cell is configured as priority
cell, triggering of the access class barring calculation mechanism does not disable
the following events:

— Subscription ratio evaluation

— Inter-Frequency Load Balancing

— Inter-Frequency Offload

A cell is configured as priority cell if the following is true:

— [Link] is set to PRIORITY.

— The [Link] or the

[Link] reference to a cell profile is set as
priority.

337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13 5

 Progressive Access Barring

Example 1 Automatic Access Class Barring Disables Load Balancing

Barring
Probability

100%

Ceiling of barring probability

= 100% – minimum barring factor

lbabPeriod

lbabIncr
lbabDecr
Minimum
barring
probability

t0 t1 t2 t3 t4 t5 t6 t7
Time

A enabled A enabled
B enabled B disabled
A disabled A disabled A enabled
B disabled B disabled B enabled

A: Inter-Frequency Load Balancing

B: Inter-Frequency Offload
L0002155B

Figure 1 Inter-Frequency Load Management Disabled by Automatic Access

Barring

The following events occur during the access class barring calculation
mechanism:

1. Before t1, inter-frequency load balancing can be enabled.

2. At t1, these load balancing functions are disabled, and automatic access
class barring calculation is enabled.

3. Between t1 and t4, until the automatic access class barring calculation is
enabled, the load balancing functions remain disabled.

4. At t4, the barring probability reaches its minimum value, that is 0. Inter-
frequency load balancing can be enabled again.

5. Between t5 and t6, inter-frequency load balancing is disabled again.

6. Between t6 and t7, outgoing inter-frequency load balancing is enabled only

if [Link] or [Link] is
set to true.

7. At t7, the barring probability reaches its minimum value again. Inter-
frequency load balancing and inter-frequency offload are enabled again.

6 337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13

3 Feature Operation of Progressive Access
Barring

The feature introduces the possibility to prioritize traffic classes for access
class barring in severe overload situations. The feature extends the
operation of the Load-Based Access Barring feature.

Automatic Access Class Barring Operation

Automatic access class barring monitors the ratio between RRC Connection
Rejects and RRC Connection Attempts and activates or deactivates access
class barring parameters in SIB2 messages. Automatic access class barring uses
barring information from SIB2 broadcast messages to inform UEs about the
congestion level in the system.

Access class barring starts to operate when the access class barring calculation
mechanism is triggered by the following conditions being true:
— The ratio between RRC Connection Rejects and RRC Connection
Attempts is above [Link] or
[Link] for a time interval
[Link] or
[Link].

— The intensity of the RRC Connection Requests is higher than the minimum
intensity.

During ongoing access class barring calculation mechanism, the following applies
to all access attempt types the presence of which is set to AUTO:
— The barring factor (1 – barring probability) for the common or the PLMN-
specific access class barring parameter for the access attempt type is
included in the next SIB2 broadcast message.

— Barring probability for the access attempt type is changed periodically, based
on the measured load in the cell and the MOM configuration.

— If a UE attempts to connect to the cell and it can be barred based on its

access class and access attempt type, access class barring is applied to the
UE. UEs are informed about access class barring parameters in SIB2
broadcast messages.

— Inter-Frequency Load Balancing and subscription ratio measurements are

disabled for the cell if the following criteria is fulfilled:

• Preferential Traffic Management is disabled, or the cell is not configured

as a priority cell.

337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13 7

 Progressive Access Barring

• Load balancing during access class barring is disabled.

Automatic access class barring calculation is continued until no congestion is

detected.

Admission
UE ACB Load Control
Control

RRC Connection Reject

RRC Connection Request

Progressive Access Barring

Access
Barring in SIB2 Calculate Measure
RRC Conn. Rejection ratio
Barring Factor
RRC Conn. Request intensity

L0001738B

Figure 2 Feature Interaction Overview of Automatic Access Class Barring

Progressive Access Barring Operation

The functionality can be applied for the following traffic classes:
— CSFB

— Mobile originating data

— Mobile originating signaling

— MMTel Video

— MMTel Voice

8 337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13

 The functionality is enabled when the access barring configuration is configured
for at least one of the traffic classes.

If the presence of a traffic class in SIB2 message is set to AUTO, barring factors
are updated for the traffic class in the common access class barring parameters.

In Progressive Access Barring, five traffic priority levels can be used. The operator
can assign each traffic class to any priority level.

Barring
Probability

Maximum barring probability

for traffic priority level 1

Maximum barring probability

for traffic priority level 2 lbabDecr

Maximum barring probability

for traffic priority level 0

lbablncr

lbabPeriod

t0 t1 t2 t3 t4 t5 t6 t7 t8 Time

Priority Priority Priority Priority Priority

level 0 level 1 level 2 level 1 level 0

L0002176A

Figure 3 Barring Factor Change by Progressive Access Barring

Access class barring starts at the lowest priority level, traffic priority level 0.

When the barring probability reaches its maximum in a priority level, barring
probability starts to be changed in the next higher priority level.

While the barring probability is changed in a priority level, the barring probability
stays at its maximum value in each lower priority level.

When the barring probability reaches 0 in a priority level, barring probability

starts to be changed in the next lower priority level.

When the barring probability reaches 0 in priority level 0, access class barring
stops.

337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13 9

 Progressive Access Barring

Note: If the parameters are changed in an overload situation, it can have an

impact on access barring regarding RRC Connection Attempts.

When the access class barring calculation mechanism is triggered, barring

probability is increased by [Link] or
[Link] at traffic priority level 0.

During the ongoing access class barring calculation mechanism, barring

probability is changed every [Link] or
[Link] depending on the relation between the traffic load
and LBAB thresholds, and the barring trend.

Table 2 Barring Factor Change

Traffic Load Situation Barring Trend Barring Probability
Change
— The ratio between N/A Barring probability is
RRC Connection increased by
Rejects and RRC [Link]
Connection cr or
Attempts is above [Link]
[Link] cr.
bThreshRejectRate
High or
[Link]
bThreshRejectRate
High for a time
interval
[Link]
bThreshTimeHigh or
[Link]
bThreshTimeHigh.

— The intensity of the

RRC Connection
Requests is higher
than the minimum
intensity.
The ratio between RRC The previous barring Barring probability is
Connection Rejects probability change was increased by
and RRC Connection increase. [Link]
Attempts stays between cr or
threshold [Link]
[Link] cr.
reshRejectRateHigh or
[Link] The previous barring Barring probability is
reshRejectRateHigh probability change was decreased by
and threshold decrease. [Link]
[Link] cr or
reshRejectRateLow or

10 337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13

 Traffic Load Situation Barring Trend Barring Probability
Change
[Link] [Link]
reshRejectRateLow.(1) cr.
If either of the following N/A Barring probability is
conditions is true: decreased by
[Link]
— The ratio between cr or
RRC Connection [Link]
Rejects and RRC cr.
Connection
Attempts is below
[Link]
bThreshRejectRate
Low or
[Link]
bThreshRejectRate
Low for a time
interval
[Link]
bThreshTimeLow or
[Link]
bThreshTimeLow.

— The intensity of the

RRC Connection
Requests is lower
than the minimum
intensity for at least
the duration of
[Link]
bPeriod or
[Link]
bPeriod.

(1) Timers [Link] or [Link] and

[Link] or [Link] are used to
check the RRC Connection Reject ratio whenever an automatic access class barring
functionality runs.

When the barring probability reached its maximum—the configured minimum

barring factor—the barring factor is not changed until the conditions for
decreasing it are fulfilled.

The barring factor (1 – barring probability) is updated in SIB2, and the updated
barring factor is included in the next SIB2 broadcast message.

337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13 11

 Progressive Access Barring

Example 2 Traffic Class Priorities in Progressive Access Barring

Data
VoLTE
Signaling
CSFB
ViLTE ViLTE
Data
Priority level 2
CSFB
Signaling
VoLTE Priority level 1

Priority level 0
Traffic classes

Figure 4 Traffic Class Priorities for Access Class Barring

In the example, three priority levels are configured.

Each traffic class can be assigned to one priority level. One priority level can
contain any number of traffic classes.

Access class barring starts at traffic priority level 0, with UEs that have the traffic
types configured for priority level 0: mobile originating data and mobile
originating signaling.

When the barring probability reaches its maximum on priority level 0, access
class barring starts at traffic priority level 1, for ViLTE.

Information Elements for Access Class Barring

Each traffic class has its own IEs for access class barring in SIB2 and RRC
messages.

Table 3 Information Elements in SIB2 and RRC Messages for Access Class
Barring
Traffic Class IEs in SIB2
Mobile originating data acBarringForMOData
Mobile originating signaling acBarringForMOSignalling
CSFB acBarringForCSFB-r10
MMTel Voice ssacBarringForMMTelVoice-r9
MMTel Video ssacBarringForMMTelVideo-r9

12 337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13

 SSAC was introduced in 3GPP Release 9 to provide the IMS/MMTel access class
barring for voice and video. If SIB2 includes ssacBarringForMMTelVoice-r9 or
ssacBarringForMMTelVideo-r9, the RRC layer delivers this access class barring
information to the higher layer and SSAC for voice and video works at IMS/
MMTel layer on the UE side. For more information, see 3GPP TS 24.173.

3.1 Access Class Barring Functionalities

A variety of access class barring functionalities are available using different
configurations depending on the license states and the values of MOM
attributes.

Table 4 Access Class Barring Functionalities

License for License for License for License for Attribute Functionality
Load-Based Progressive Progressive PLMN- EUtranCellF
Access Access Barring for Specific [Link]
Barring Barring Special Access Access gPlmnPabEna
Classes Barring bled or
EUtranCellT
[Link]
gPlmnPabEna
bled
Deactivated N/A N/A N/A N/A Manual
Access Class
Barring on
page 14
Activated Deactivated N/A Deactivated N/A Load-Based
Access
Barring on
page 15
Activated Deactivated N/A Activated N/A PLMN Load-
Based Access
Barring on
page 15
Activated Activated Deactivated Deactivated N/A Progressive
Access
Barring on
page 16
Activated Activated Deactivated Activated False PLMN
Progressive
Access

337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13 13

 Progressive Access Barring

License for License for License for License for Attribute Functionality
Load-Based Progressive Progressive PLMN- EUtranCellF
Access Access Barring for Specific [Link]
Barring Barring Special Access Access gPlmnPabEna
Classes Barring bled or
EUtranCellT
[Link]
gPlmnPabEna
bled
Barring on
page 16
Activated Activated Deactivated Activated True Prioritized
PLMN
Progressive
Access
Barring on
page 17
Activated Activated Activated Deactivated N/A Progressive
Barring for
Special Access
Classes on
page 18
Activated Activated Activated Activated False PLMN
Progressive
Barring for
Special Access
Classes on
page 19
Activated Activated Activated Activated True Prioritized
PLMN
Progressive
Barring for
Special Access
Classes on
page 20

3.1.1 Manual Access Class Barring

Manual Access Class Barring is the basic access class barring functionality.
The operation of this functionality depends only on MOM configuration, and
it is independent of the traffic load situation.

The Manual Access Class Barring functionality does not require any licensed
feature.

14 337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13

 When this access class barring functionality is used, the barring factors are
determined for each traffic class based on the values of the corresponding MOM
attributes.

Barring factors specified in MOM are broadcast in SIB2 messages only if the
presence of each traffic class in SIB2 is set to MANUAL. If the presence of a traffic
class in SIB2 is set to any other value—OFF or AUTO—the AC-BarringConfig
element for that traffic class is not present in SIB2.

Note: The presence of a traffic class in SIB2 message can be set differently for
the common access barring parameters and the PLMN-specific access
barring parameters.

3.1.2 Load-Based Access Barring

Load-Based Access Barring is the basic automatic access class barring

functionality. The operation of this functionality depends on the traffic load
situation.

The Load-Based Access Barring functionality requires that the Load-Based

Access Barring licensed feature is activated.

When this access class barring functionality is used, the barring factors are
updated for all traffic classes based on the traffic load situation.

If the presence of a traffic class in SIB2 is set to AUTO, the following applies:

— In the common access class barring parameters, barring factors are updated
for the traffic class.

— In the PLMN-specific access class barring parameters, barring factors are not
updated for the traffic class.

Barring factors in PLMN-specific access class barring parameters are broadcast

in SIB2 messages only if the presence of the traffic class in SIB2 is set to MANUAL.

3.1.3 PLMN Load-Based Access Barring

PLMN Load-Based Access Barring is an automatic access class barring

functionality that extends the Load-Based Access Barring feature. The
operation of this functionality depends on both the traffic load situation and
the PLMN-specific access barring configuration.

The PLMN Load-Based Access Barring functionality requires that the following
licensed features are activated:

— Load-Based Access Barring

337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13 15

 Progressive Access Barring

— PLMN-Specific Access Barring

When this access class barring functionality is used, the barring factors are
updated for all traffic classes based on the traffic load situation and the PLMN-
specific access barring configuration.

If the presence of a traffic class in SIB2 message is set to AUTO, barring factors
are updated for the traffic class both in the common access barring parameters
and in the PLMN-specific access barring parameters.

Note: The presence of a traffic class in SIB2 message can be set differently for
the common access barring parameters and the PLMN-specific access
barring parameters.

3.1.4 Progressive Access Barring

Progressive Access Barring is an automatic access class barring

functionality that extends the Load-Based Access Barring feature. This
functionality prioritizes the traffic classes for access class barring.

The Progressive Access Barring functionality requires that the following licensed
features are activated:
— Load-Based Access Barring

— Progressive Access Barring

Access class barring in the common access class barring parameters starts for the
traffic classes assigned to the lowest traffic priority level. When the barring factor
reaches the minimum barring factor for a traffic priority level access class barring
is continued on the next higher priority level.

If the presence of a traffic class in SIB2 is set to AUTO, the following applies:

— In the common access class barring parameters, barring factors are updated
for the traffic class.

— In the PLMN-specific access class barring parameters, barring factors are not
updated for the traffic class.

Barring factors in PLMN-specific access class barring parameters are broadcast

in SIB2 messages only if the presence of the traffic class in SIB2 is set to MANUAL.

3.1.5 PLMN Progressive Access Barring

PLMN Progressive Access Barring is an automatic access class barring

functionality that extends the Progressive Access Barring feature. This

16 337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13

 functionality takes the PLMN-specific access barring configuration into
account when prioritizing the traffic classes for access class barring.

The PLMN Progressive Access Barring functionality requires that the following
licensed features are activated:
— Load-Based Access Barring

— PLMN-Specific Access Barring

— Progressive Access Barring

When this access class barring functionality is used, the following applies:
— The common and the PLMN-specific access barring parameters share the
same priority relations among traffic classes.

— The barring factors and the priority level are updated by applying the
progressive access barring algorithms so that the traffic classes in the PLMN-
specific access barring parameters are also taken into account.

If the presence of a traffic class in SIB2 message is set to AUTO, barring factors
are updated for the traffic class both in the common access barring parameters
and in the PLMN-specific access barring parameters.

Note: The presence of a traffic class in SIB2 message can be set differently for
the common access barring parameters and the PLMN-specific access
barring parameters.

3.1.6 Prioritized PLMN Progressive Access Barring

Prioritized PLMN Progressive Access Barring is an automatic access class

barring functionality that extends the Progressive Access Barring feature.
This functionality prioritizes the PLMNs for access class barring in addition
to prioritizing the traffic classes.

The Prioritized PLMN Progressive Access Barring functionality requires that the
following licensed features are activated:
— Load-Based Access Barring

— PLMN-Specific Access Barring

— Progressive Access Barring

The functionality is enabled if attribute

[Link] or
[Link] is set to true.

337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13 17

 Progressive Access Barring

When this access class barring functionality is used, the following applies:
— The common and the PLMN-specific access barring parameters share the
same priority relations among traffic classes.

— Access class barring starts at the lowest PLMN priority level for the traffic
classes assigned to the lowest traffic priority level. If no PLMN is allocated to
a PLMN priority level, the level is skipped.

— The barring factors and the priority level are updated by applying the
progressive access barring algorithms within each PLMN priority level. When
the barring factor reaches the minimum barring factor for the highest traffic
priority level on a PLMN priority level, access class barring is continued on
the next higher PLMN priority level.

If the presence of a traffic class in SIB2 is set to AUTO, the following applies:
— In the common access class barring parameters, barring factors are set the
same value for the traffic class as the barring factors for the traffic class on
the lowest PLMN priority level.

— In the PLMN-specific access class barring parameters, barring factors are

updated for the traffic class.

Note: The presence of a traffic class in SIB2 message can be set differently for
the common access barring parameters and the PLMN-specific access
barring parameters.

3.1.7 Progressive Barring for Special Access Classes

Progressive Barring for Special Access Classes is an automatic access class

barring functionality that extends the Progressive Access Barring feature.
This functionality prioritizes the special access class in traffic classes in
addition to prioritizing the standard access classes.

With this functionality, the barring factors and the priority level are updated by
applying the progressive barring for special access classes algorithms. If the
priority level of a special access class is equal to the current priority level and the
barring factor is equal to the minimum barring factor of the priority level, then the
barring information of a special access class is set to true.

If the presence of a traffic class of a special access class in SIB2 is set to AUTO, the
following applies:

— In the common access class barring parameters, barring factors are updated
for the traffic class.

— In the PLMN-specific access class barring parameters, barring factors are not
updated for the traffic class.

18 337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13

 Barring factors in PLMN-specific access class barring parameters are broadcast
in SIB2 messages only if the presence of the traffic class in SIB2 is set to MANUAL.

Note: The presence of a traffic class in SIB2 message can be set differently for
the common access barring parameters and the PLMN-specific access
barring parameters.

3.1.8 PLMN Progressive Barring for Special Access Classes

PLMN Progressive Barring for Special Access Classes is an automatic access

class barring functionality that extends the Progressive Barring for Special
Access Classes feature. This functionality takes the PLMN-specific access
barring configuration into account when prioritizing the special access
classes for access class barring.

The Prioritized PLMN Progressive Access Barring functionality requires that the
following licensed features are activated:
— Load-Based Access Barring

— PLMN-Specific Access Barring

— Progressive Access Barring

— Progressive Barring for Special Access Classes

With this functionality, the barring factors and the priority level are updated by
applying the progressive barring for special access classes algorithms. If the
priority level of a special access class is equal to the current priority level and the
barring factor is equal to the minimum barring factor of the priority level, then the
barring information of a special access class is set to true.

The common and the PLMN-specific access barring parameters share the same
priority relations among standard and special access classes of traffic classes.

There is no priority relation between PLMNs.

If the presence of a traffic class in SIB2 is set to AUTO, barring factors are updated
for the special access class both in the common access class barring parameters
and in the PLMN-specific access class barring parameters.

Note: The presence of a traffic class in SIB2 message can be set differently for
the common access barring parameters and the PLMN-specific access
barring parameters.

337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13 19

 Progressive Access Barring

3.1.9 Prioritized PLMN Progressive Barring for Special Access Classes

Prioritized PLMN Progressive Barring for Special Access Classes is an

automatic access class barring functionality that extends the Progressive
Barring for Special Access Classes feature. This functionality prioritizes the
PLMNs for access class barring in addition to prioritizing the special access
classes.

The Prioritized PLMN Progressive Access Barring functionality requires that the
following licensed features are activated:
— Load-Based Access Barring

— PLMN-Specific Access Barring

— Progressive Access Barring

— Progressive Barring for Special Access Classes

The functionality is enabled if attribute

[Link] or
[Link] is set to true.

If the PLMN priority is lower than the current PLMN priority, the barring
information of the special access class is set to barred.

If the PLMN priority is higher than the current PLMN priority, the barring
information of the special access class is set to not barred.

If the PLMN priority is equal to the current PLMN priority, the barring information
of the special access class is set as follows:

— If the priority level of a special access class is lower than current priority
level, the barring information of the special access class is set to barred.

— If the priority level of a special access class is equal to current priority level
and barring factor is equal to the minimum barring factor of the priority level,
then barring information of the special access class is set to barred.

— Otherwise, barring information of a special access class is set to not barred.

The common and the PLMN-specific access barring parameters share the same
priority relations among standard and special access classes of traffic classes.

Hence, the priority relations among standard and special access classes of traffic
classes are the same within each PLMN priority level. The priority relations
among standard and special access classes of traffic classes are defined by the
Progressive Barring for Special Access Classes configuration.

20 337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13

 If the presence of a traffic class in SIB2 is set to AUTO, barring factors are updated
for the special access class both in the common access class barring parameters
and in the PLMN-specific access class barring parameters.

Note: The presence of a traffic class in SIB2 message can be set differently for
the common access barring parameters and the PLMN-specific access
barring parameters.

337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13 21

 Progressive Access Barring

4 Network Impact of Progressive Access

Barring

The feature does not impact any network elements.

Capacity and Performance

No impact.

Interfaces
No impact.

Other Network Elements

No impact.

22 337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13

5 Parameters for Progressive Access Barring

This feature affects the parameters related to RRC and barring factor.

Table 5 Parameters
Parameter Type Description
[Link] Affected See MOM description.
ingPresence The attribute references
the AcBarringPresence
struct. The struct has the
following members:
— acBarringForMoDat
aPresence

— acBarringForMoSig
nPresence

— acBarringForCSFBP
resence

— acBarringForMmtel
VoicePresence

— acBarringForMmtel
VideoPresence

— acBarringPriority
MoData

— acBarringPriority
MoSignaling

— acBarringPriority
CSFB

— acBarringPriority
MmtelVoice

— acBarringPriority
MmtelVideo
[Link] Affected See MOM description.
cr
[Link] Affected See MOM description.
cr

337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13 23

 Progressive Access Barring

Parameter Type Description

[Link] Affected See MOM description.
nBarringFactor
[Link] Affected See MOM description.
nBarringFactorPrio1
[Link] Affected See MOM description.
nBarringFactorPrio2
[Link] Affected See MOM description.
nBarringFactorPrio3
[Link] Affected See MOM description.
nBarringFactorPrio4
[Link] Affected See MOM description.
riod
[Link] Affected See MOM description.
reshRejectRateHigh
[Link] Affected See MOM description.
reshRejectRateLow
[Link] Affected See MOM description.
reshTimeHigh
[Link] Affected See MOM description.
reshTimeLow
[Link] Affected See MOM description.
ingPresence The attribute references
the AcBarringPresence
struct. The struct has the
following members:
— acBarringForMoDat
aPresence

— acBarringForMoSig
nPresence

— acBarringForCSFBP
resence

— acBarringForMmtel
VoicePresence

— acBarringForMmtel
VideoPresence

— acBarringPriority
MoData

— acBarringPriority
MoSignaling

24 337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13

 Parameter Type Description
— acBarringPriority
CSFB

— acBarringPriority
MmtelVoice

— acBarringPriority
MmtelVideo
[Link] Affected See MOM description.
cr
[Link] Affected See MOM description.
cr
[Link] Affected See MOM description.
nBarringFactor
[Link] Affected See MOM description.
nBarringFactorPrio1
[Link] Affected See MOM description.
nBarringFactorPrio2
[Link] Affected See MOM description.
nBarringFactorPrio3
[Link] Affected See MOM description.
nBarringFactorPrio4
[Link] Affected See MOM description.
riod
[Link] Affected See MOM description.
reshRejectRateHigh
[Link] Affected See MOM description.
reshRejectRateLow
[Link] Affected See MOM description.
reshTimeHigh
[Link] Affected See MOM description.
reshTimeLow

337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13 25

 Progressive Access Barring

6 Performance of Progressive Access Barring

The feature has associated performance management entities related to

accessibility, retainability, and throughput.

KPIs
This feature has no associated KPIs.

Counters
— [Link]

— [Link]

— [Link]

— [Link]

— [Link]

— [Link]

— [Link]

— [Link]

— [Link]

— [Link]

Events
This feature has no associated events.

26 337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13

7 Activate Progressive Access Barring

To use the feature, it must be activated following the usual feature

activation procedure.

Prerequisites
— The license key is installed in the node.

— Continuous Cell Trace Recording (CCTR) is activated for at least one week.
This ensures there is troubleshooting data available if something goes
wrong.

— Load-Based Access Barring (FAJ 121 3093) is activated.

— At least one of the following members of the AcBarringPresence struct is

set to AUTO:
— acBarringForCsfbPresence

— acBarringForMoDataPresence

— acBarringForMoSignPresence

— acBarringForMMTELVideoPresence

— acBarringForMMTELVoicePresence

Steps

1. Set the [Link] attribute to ACTIVATED in the

FeatureState=CXC4012120 MO instance.

After This Task

Keep CCTR active for at least one week after this procedure for continued
collection of troubleshooting data.

337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13 27

 Progressive Access Barring

8 Deactivate Progressive Access Barring

If the feature is no longer needed, it can be deactivated following the usual

feature deactivation procedure. It must also be deactivated before the
activation of any conflicting feature.

Prerequisites
Continuous Cell Trace Recording (CCTR) is activated for at least one week. This
ensures there is troubleshooting data available if something goes wrong.

Steps

1. Set the [Link] attribute to DEACTIVATED in the

FeatureState=CXC4012120 MO instance.

After This Task

Keep CCTR active for at least one week after this procedure for continued
collection of troubleshooting data.

28 337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13

9 Engineering Guidelines for Progressive
Access Barring

The feature has configurations related to traffic and user equipment.

BarringFactor at IEs of SIB2

If the UE has access classes corresponding to Access Class Barring parameters in
SIB2, the UE draws a random number uniformly distributed in the range: 0 ≤ rand
< 1. If 'rand' is lower than the value indicated by ac-BarringFactor, it considers
access to the cell as not barred. Access Class Barring is introduced in SIB2. For
more information, see 3GPP TS 36.331.

There are five traffic class types:

— MO Data

— MO Signaling

— CSFB

— MMTel voice

— MMTel video

Each traffic class has its own IEs for access class barring in SIB2. Legacy LBAB
feature supports three traffic classes: MO Data, MO signaling, and CSFB.
Progressive Access Barring also supports two additional traffic classes: MMTel
voice and MMTel video. MMTel voice and MMTel video use two IEs unlike the
other three traffic types. SSAC was introduced in 3GPP Release 9 to provide the
IMS/MMTel access class barring for voice and video. If SIB2 includes
ssacBarringForMMTel-Voice-r9 or ssacBarringForMMTel-Video-r9, the RRC
layer delivers this Access Class Barring information to the higher layer and SSAC
for voice and video works at IMS/MMTel layer on the UE side. Access Class
Barring skip was introduced in 3GPP Release 12. If SIB2 includes
acBarringSkipForMMTelVoice or acBarringSkipForMMTelVideo, mobile
originating MMTel voice or video bypasses the RRC level Access Class Barring.
This means that if the UE establishes the RRC connection for mobile originating
MMTel service, the UE considers access to the cell as not barred.

337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13 29

 Progressive Access Barring

Figure 5 IE of SIB2

MOM Attributes
After feature activation, loadBasedBarringFactor
([Link] or
[Link]) and lbabBarringPriorityLevel
([Link] or
[Link]) can help monitor any Access
Barring functionality.

The following attributes can be configured for each priority level:

— [Link]

— [Link]

— EUtranCellFDD.lbabMinBarringFactorPrio1

— EUtranCellTDD.lbabMinBarringFactorPrio1

— EUtranCellFDD.lbabMinBarringFactorPrio2

— EUtranCellTDD.lbabMinBarringFactorPrio2

— EUtranCellFDD.lbabMinBarringFactorPrio3

— EUtranCellTDD.lbabMinBarringFactorPrio3

— EUtranCellFDD.lbabMinBarringFactorPrio4

— EUtranCellTDD.lbabMinBarringFactorPrio4

Note: lbabMinBarringFactor is used for priority level 0.

lbabMinBarringFactorPrio1 is used for priority level 1 and
lbabMinBarringFactorPrio2 is used for priority level 2.

30 337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13

 The following members of the [Link] and
[Link] struct are used to configure priority level
for each traffic class:

— acBarringPriorityCsfb

— acBarringPriorityMoData

— acBarringPriorityMoSignaling

— acBarringPriorityMmtelVoice

— acBarringPriorityMmtelVideo

Configuration of Progressive Access Barring

This feature is activated when specific configurations are satisfied as shown in
Figure 6. The configuration is similar to the configuration of Load-Based Access
Barring. It is necessary to set at least one of the following attributes to AUTO:
— acBarringForCsfbPresence

— acBarringForMoDataPresence

— acBarringForMoSignPresence

— acBarringForMMTELVideoPresence

— acBarringForMMTELVoicePresence

LBAB PAB AcBarringMode AcBarringMode Load-Based Progressive

License License Setting or Setting for Access Barring Access Barring
Setting Setting MO-Signalling MmTelVoice (LBAB) Activated (PAB) Activated
or MO-Data or or MmTelVideo
CSFB

OFF NO NO
OFF MANUAL NO NO
AUTO NO YES
OFF NO NO
ON ON MANUAL MANUAL NO NO
AUTO NO YES
OFF NO YES
AUTO MANUAL NO YES
AUTO NO YES

L0001734B

Figure 6 Configuration of Progressive Access Barring

For more information about the configuration of LBAB, see Load-Based Access
Barring. For more detailed information on the handling of LBAB license, see
Activate Load-Based Access Barring and Deactivate Load-Based Access Barring.

337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13 31

 Progressive Access Barring

Observability
The following counters can be used to check if Progressive Access Barring works
correctly and which traffic types are barred by the feature:

— [Link]

— [Link]

— [Link]

— [Link]

— [Link]

— [Link]

— [Link]

— [Link]

— [Link]

— [Link]

In addition to the above counters for Access Class Barring, the total number of
RRC connection request attempts, [Link] or
[Link], and the total number of successful RRC
connection establishments, [Link] or
[Link], can also be used to monitor the impact
of Progressive Access Barring on the eNodeB.

32 337/221 04-LZA 701 6014/1 Uen BH | 2022-07-13