Access Class Barring

There are several different ways for Access Control, but in terms of overall logic we can
think of two different mechanisms as listed below.
 Type 1) Accept initial request from UE but Network send Reject message
 Type 2) Prevent UE from trying initial access itself. (This type is called 'Barring')
o Case 1 : Bar every UE from any type of access even for emergency call
(Configured by SIB1)
o Case 2 : Bar only specific UE (with specific marking in USIM) from a
specific services (Configured by SIB2)

Access Control by SIB2 : ac-Barring

You may easily guess the Access Control Mechanism by SIB2. You would see several
different copies of the following structure. Just by looking at the name of the
parameters, you may guess 'this is to allowing (or barring) a certain UE group (Access
Class) to a certain service with only a certain probability'.

ac-BarringForXXXXXX
ac-BarringFactor: pXY (0)
ac-BarringTime: sA (0)
ac-BarringForSpecialAC: ABCDE (bitmap)

 XXXXX here represents the name of the service (application).

 ac-BarringFactor represents the probability of allowance of the access.
 ac-BarringForSpecialAC represents Access Class for UEs. A = 11, B = 12, C = 13,
D = 14, E = 15

For example,
Let's assume that pXY is set to be p50 and ac-BarringForSpecialAC is set to be 01000.
This bitmap indicates the status of each Access Class as follows.
AC 11 = Not Barring
AC 12 = Barring
AC 13 = Not Barring
AC 14 = Not Barring
AC 15 = Not Barring
Therefore, this barring applies only to the UE that has Access Class 12 is set to be '1' in
its USIM.
With this SIB settings, If a UE belonging to Access Class 12 sees this SIB parameter, it
generate a random number between 0 and 1. If the number is lower than 0.5 (p50), it is
allowed to get access. If the number is higher than 0.5, it should not get access. UE can
retry this with the everage interval of A seconds set in ac-BarringTime when it is
necessary.

What is the use of these Access Categories ?

In Idle mode , based on the AC a user will be treated differently when it comes to

 Emergency Call

 Mobile Originated (MO) Signaling Setup

 MO Data Session
 Voice Call (MMTEL Voice)

 Video Call (MMTEL Video)

 CS Fall back

Access Class Barring for Emergency Call

Access class barring for emergency calls determines whether or not UE with AC 0 to 9
should treat the cell as barred for emergency calls. The same rule is applicable to UE
without a USIM.

UEs with Access class 11 to 15 are able to make emergency calls unless

 the cell is AC class barred for emergency calls and

 the cell is AC barred for mobile originating data calls

Access Class Barring for Mobile Originated (MO) signaling (General Procedure)
Access class barring for Mobile Originated signaling determines whether or not UE should
treat the cell as barred when initiating an MO signaling connection.

How to Determine if a Cell is Barred ?

UEs with Access class 0 to 9 generate a random number between 0 and 1. If it is less than
the Barring factor then the cell is treated as not barred.

UE with AC 11 to 15 check the Barring for special Access Classes parameter to determine
whether or not it is necessary to generate a random number with which to compare against
the Barring Factor.

What if a cell is barred for MO Signaling ?

If a cell is to be treated as barred for MO signaling connection , then the Barring Time is
used to define a penalty time during which the UE is not allowed to re-attempt access . The
penalty time for MO Signaling is T305. The way timer T305 value is computed is as follows.

Cell Barring time for MO Signalling

T305=(0.7+0.6*RAND)*Barring time
What if a cell is barred for MO Data ?
In case if the cell is to treated as barred for MO data connections. In this case, the penalty
time is T303. The way timer T303 is computed is as follows

T303=(0.7+0.6*RAND)*Barring time