0

UE is not configured with any parameters from this table

1 (NOTE 1)

UE is configured for multimedia priority service (MPS).

2 (NOTE 2)

UE is configured for mission critical service (MCS).

3-10

Reserved for future use

11 (NOTE 3)

Access Class 11 is configured in the UE.

12 (NOTE 3)

Access Class 12 is configured in the UE.

13 (NOTE 3)

Access Class 13 is configured in the UE.

14 (NOTE 3)

Access Class 14 is configured in the UE.

15 (NOTE 3)

Access Class 15 is configured in the UE.

NOTE 1: Access identity 1 is valid when:
– the USIM file EFUAC_AIC indicates the UE is configured for access identity 1 and the RPLMN is the HPLMN (if the EHPLMN list is not present or is empty) or EHPLMN (if the EHPLMN list is present), or a visited PLMN of the home country (see the definition of home country in 3GPP TS 24.301 [15]); or
– the UE receives the 5GS network feature support IE with the MPS indicator bit set to "Access identity 1 valid in RPLMN or equivalent PLMN" from the RPLMN as described in subclause 5.5.1.2.4 and subclause 5.5.1.3.4.

NOTE 2: Access identity 2 is used by UEs configured for MCS and is valid when:
– the USIM file EFUAC_AIC indicates the UE is configured for access identity 2 and the RPLMN is the HPLMN (if the EHPLMN list is not present or is empty) or EHPLMN (if the EHPLMN list is present), or a visited PLMN of the home country (see 3GPP TS 23.122 [5]); or
– the UE receives the 5GS network feature support IE with the MCS indicator bit set to "Access identity 2 valid in RPLMN or equivalent PLMN" from the RPLMN as described in subclause 5.5.1.2.4 and subclause 5.5.1.3.4.

NOTE 3: Access identities 11 and 15 are valid in HPLMN (if the EHPLMN list is not present or is empty) or EHPLMN (if the EHPLMN list is present). Access Identities 12, 13 and 14 are valid in HPLMN and visited PLMNs of home country only (see the definition of home country in 3GPP TS 24.301 [15]).

1

Response to paging or NOTIFICATION over non-3GPP access;

5GMM connection management procedure initiated for the purpose of transporting an LPP message

Access attempt is for MT access

0 (= MT_acc)

2

Emergency

UE is attempting access for an emergency session (NOTE 1, NOTE 2)

2 (= emergency)

3

Access attempt for operator-defined access category

UE stores operator-defined access category definitions valid in the current PLMN as specified in subclause 4.5.3, and access attempt is matching criteria of an operator-defined access category definition

32-63
(= based on operator classification)

4

Access attempt for delay tolerant service

(a) UE is configured for NAS signalling low priority or UE supporting S1 mode is configured for EAB (see the "ExtendedAccessBarring" leaf of NAS configuration MO in 3GPP TS 24.368 [17] or 3GPP TS 31.102 [22]) where "EAB override" does not apply, and

(b). the UE received one of the categories a, b or c as part of the parameters for unified access control in the broadcast system information, and the UE is a member of the broadcasted category in the selected PLMN or RPLMN/equivalent PLMN

(NOTE 3, NOTE 5, NOTE 6, NOTE 7, NOTE 8)

1 (= delay tolerant)

5

MO MMTel voice call

Access attempt is for MO MMTel voice call

or for NAS signalling connection recovery during ongoing MO MMTel voice call (NOTE 2)

4 (= MO MMTel voice)

6

MO MMTel video call

Access attempt is for MO MMTel video call

or for NAS signalling connection recovery during ongoing MO MMTel video call (NOTE 2)

5 (= MO MMTel video)

7

MO SMS over NAS or MO SMSoIP

Access attempt is for MO SMS over NAS (NOTE 4) or MO SMS over SMSoIP transfer

or for NAS signalling connection recovery during ongoing MO SMS or SMSoIP transfer (NOTE 2)

6 (= MO SMS and SMSoIP)

8

UE NAS initiated 5GMM specific procedures

Access attempt is for MO signalling

3 (= MO_sig)

9

UE NAS initiated 5GMM connection management procedure or 5GMM NAS transport procedure

Access attempt is for MO data

7 (= MO_data)

10

An uplink user data packet is to be sent for a PDU session with suspended user-plane resources

No further requirement is to be met

7 (= MO_data)

NOTE 1: This includes 5GMM specific procedures while the service is ongoing and 5GMM connection management procedures required to establish a PDU session with request type = "initial emergency request" or "existing emergency PDU session", or to re-establish user-plane resources for such a PDU session. This further includes the service request procedure initiated with a SERVICE REQUEST message with the Service type IE set to "emergency services fallback".<

NOTE 2: Access for the purpose of NAS signalling connection recovery during an ongoing service, or for the purpose of NAS signalling connection establishment following fallback indication from lower layers during an ongoing service, is mapped to the access category of the ongoing service in order to derive an RRC establishment cause, but barring checks will be skipped for this access attempt.

NOTE 3: If the UE selects a new PLMN, then the selected PLMN is used to check the membership; otherwise the UE uses the RLPMN or a PLMN equivalent to the RPLMN.

NOTE 4: This includes the 5GMM connection management procedures triggered by the UE-initiated NAS transport procedure for transporting the MO SMS.

NOTE 5: The UE configured for NAS signalling low priority is not supported in this release of specification. If a UE supporting both S1 mode and N1 mode is configured for NAS signalling low priority in S1 mode as specified in 3GPP TS 24.368 [17] or 3GPP TS 31.102 [22], the UE shall ignore the configuration for NAS signalling low priority when in N1 mode.

NOTE 6: If the access category applicable for the access attempt is 1, then the UE shall additionally determine a second access category from the range 3 to 7. If more than one access category matches, the access category of the lowest rule number shall be chosen. The UE shall use the second access category only to derive an RRC establishment cause for the access attempt.

NOTE 7: "EAB override" does not apply, if the UE is not configured to allow overriding EAB (see the "Override_ExtendedAccessBarring" leaf of NAS configuration MO in 3GPP TS 24.368 [17] or 3GPP TS 31.102 [22]), or if NAS has not received an indication from the upper layers to override EAB and the UE does not have a PDU session that was established with EAB override.

NOTE 8: For the definition of categories a, b and c associated with access category 1, see 3GPP TS 22.261 [3]. The categories associated with access category 1 are distinct from the categories a, b and c associated with EAB (see 3GPP TS 22.011 [1A]).

0

0 (= MT_acc)

mt-Access

1 (= delay tolerant)

Not applicable (NOTE 1)

2 (= emergency)

emergency

3 (= MO_sig)

mo-Signalling

4 (= MO MMTel voice)

mo-VoiceCall

5 (= MO MMTel video)

mo-VideoCall

6 (= MO SMS and SMSoIP)

mo-SMS

7 (= MO_data)

mo-Data

1

Any category

mps-PriorityAccess

2

Any category

mcs-PriorityAccess

11, 15

Any category

highPriorityAccess

12,13,14,

Any category

highPriorityAccess

NOTE 1: A UE using access category 1 for the access barring check will determine a second access category in the range 3 to 7 that is to be used for determination of the RRC establishment cause. See subclause 4.5.2, table 4.5.2.2, NOTE 6.

NOTE 2: See subclause 4.5.2, table 4.5.2.1 for use of the access identities of 0, 1, 2, and 11-15.

0

0 (= MT_acc)

mt-Access

1 (= delay tolerant)

Not applicable (NOTE 1)

2 (= emergency)

emergency

3 (= MO_sig)

mo-Signalling

4 (= MO MMTel voice)

mo-VoiceCall

5 (= MO MMTel video)

mo-VoiceCall

6 (= MO SMS and SMSoIP)

mo-Data

7 (= MO_data)

mo-Data

1

Any category

highPriorityAccess

2

Any category

highPriorityAccess

11, 15

Any category

highPriorityAccess

12,13,14,

Any category

highPriorityAccess

NOTE 1: A UE using access category 1 for the access barring check will determine a second access category in the range 3 to 7 that is to be used for determination of the RRC establishment cause. See subclause 4.5.2, table 4.5.2.2, NOTE 6.

NOTE 2: See subclause 4.5.2, table 4.5.2.1 for use of the access identities of 0, 1, 2, and 11-15.

NR Cell 1

PLMN1

001

01

NR Cell 12

PLMN2

002

11

T0

SS/PBCH

SSS EPRE

dBm/SCS

-88

Off

The power level values are assigned to ensure UE registered on NR Cell 1.

T1

SS/PBCH

SSS EPRE

dBm/SCS

Off

-80

The power level values are assigned to ensure UE registered on NR Cell 12.

T2

SS/PBCH

SSS EPRE

dBm/SCS

-80

Off

The power level values are assigned to ensure UE registered on NR Cell 1.

T0

SS/PBCH

SSS EPRE

dBm/SCS

FFS

Off

The power level values are assigned to ensure UE registered on NR Cell 1.

T1

SS/PBCH

SSS EPRE

dBm/SCS

Off

FFS

The power level values are assigned to ensure UE registered on NR Cell 12.

T2

SS/PBCH

SSS EPRE

dBm/SCS

FFS

Off

The power level values are assigned to ensure UE registered on NR Cell 1.

U – S

Message

1

The SS adjusts the NR Cells power levels according to row "T1" in table 11.3.6.3.2-1/2.

–

–

–

–

1A

Void

–

–

–

–

1AA

Check: Does the UE transmit a RRCSetupRequest message on NR cell 12 including the establishmentCause which is any value except mcs-PriorityAccess?

–>

NR RRC: RRCSetupRequest

1

P

1AB-1AE

Steps 2 to 5 of the mobility registration updating procedure described in TS 38.508-1 [4] Table 4.9.5.2.2-1 are performed on NR Cell 12.

–

–

–

–

1AF-1AI

Steps 5 to 8 of the NR RRC_CONNECTED procedure in TS 38.508-1 Table 4.5.4.2-3 are performed.

–

–

–

–

1AJ

The SS transmits a CLOSE UE TEST LOOP message.

<–

NR RRC: DLInformationTransfer

TC: CLOSE UE TEST LOOP

–

–

1AK

The UE transmits a CLOSE UE TEST LOOP COMPLETE message.

–>

NR RRC: ULInformationTransfer

TC: CLOSE UE TEST LOOP COMPLETE

–

–

1AL

The SS transmits one IP PDU.

–

–

–

–

1AM

The SS transmits an RRCRelease message and move the UE to RRC_IDLE.

<–

NR RRC: RRCRelease

–

–

1AN

Check: Does the UE transmit an RRCSetupRequest message within 21s on NR Cell 12? (Note 4)

–>

NR RRC: RRCSetupRequest

1

F

1B

SS changes SIB1 of NR Cell 12 according to 38.508-1 [4] Table 4.6.1-28 and sends Short Message on PDCCH using P-RNTI.

–

–

–

–

1C

Start Timer=30 sec. (Note 3)

–

–

–

–

–

EXCEPTION: Steps 1Da1-1Db16 describe optional behaviour that depends on the UE implementation.

–

–

–

–

1Da1

Check: Does the UE transmit an RRCSetupRequest message and establishmentCause is set to mo-Data?

–>

NR RRC: RRCSetupRequest

1

P

1Da2

Stop Timer=30 sec

–

–

–

–

1Db1

Timer=30 sec expires

–

–

–

–

1Db2-1Db9

Steps 1-8 of the generic procedure for

NR RRC Connected specified in TS 38.508-1

Table 4.5.4.2-3 are performed.

–

–

–

–

1Db10

The SS transmits an OPEN UE TEST LOOP message.

<–

NR RRC: DLInformationTransfer

TC: OPEN UE TEST LOOP

–

–

1Db11

The UE transmits an OPEN UE TEST LOOP COMPLETE message.

–>

NR RRC: ULInformationTransfer

TC: OPEN UE TEST LOOP COMPLETE

–

–

1Db12

The SS transmits a CLOSE UE TEST LOOP message.

<–

NR RRC: DLInformationTransfer

TC: CLOSE UE TEST LOOP

–

–

1Db13

The UE transmits a CLOSE UE TEST LOOP COMPLETE message.

–>

NR RRC: ULInformationTransfer

TC: CLOSE UE TEST LOOP COMPLETE

–

–

1Db14

The SS transmits one IP PDU.

–

–

–

–

1Db15

The SS transmits an RRCRelease message and move the UE to RRC_IDLE.

<–

NR RRC: RRCRelease

–

–

1Db16

Check: Does the UE transmit an RRCSetupRequest message and establishmentCause is set to mo-Data?

–>

NR RRC: RRCSetupRequest

1

P

1E-1I

Steps 3-7 of the generic procedure for

NR RRC Connected specified in TS 38.508-1

Table 4.5.4.2-3 are performed.

–

–

–

–

–

EXCEPTION: Steps 1J and 1K can occur in any order.

–

–

–

–

1J

The UE transmits an RRCReconfigurationComplete message.

–>

NR RRC: RRCReconfigurationComplete

–

–

1K

The UE loops back the IP PDU

–

–

–

–

1L

The UE is switched off by executing generic procedure in Table 4.9.6.3-1 in TS 38.508-1 [4]

–

–

–

–

1M

The SS adjusts the NR Cells power levels according to row "T2" in table 11.3.6.3.2-1/2.

–

–

–

–

1N

The UE is Switched ON. The generic test procedure in TS 38.508-1 [4] Table 4.5.2.2-2 indicate that the UE performs registration on NR Cell 1 with condition Test Mode = On.

–

–

–

–

–

EXCEPTION: Step 1O is performed in p pc_noOf_PDUsNewConnection > 0.

–

–

–

–

1O

The generic procedure in TS 38.508-1 [4] Table 4.5.2.2-4 for UE-requested PDU session establishment performs registration on NR Cell 1 and then release the RRC Connection.

–

–

–

–

1P

The SS adjusts the NR Cells power levels according to row "T1" in table 11.3.6.3.2-1/2.

–

–

–

–

2

Check: Does the UE transmit an RRCSetupRequest message on NR cell 12 including the establishmentCause which is any value except mcs-PriorityAccess.

–>

NR RRC: RRCSetupRequest

1

P

3-6

Steps 2 to 5 of the mobility registration updating procedure described in TS 38.508-1 [4] Table 4.9.5.2.2-1 are performed on NR Cell 12. (Note 1)

–

–

–

–

6A-6D

Steps 5 to 8 of the NR RRC_CONNECTED procedure in TS 38.508-1 Table 4.5.4.2-3 are performed.

–

–

–

–

6E

The SS transmits a CLOSE UE TEST LOOP message.

<–

NR RRC: DLInformationTransfer

TC: CLOSE UE TEST LOOP

–

–

6F

The UE transmits a CLOSE UE TEST LOOP COMPLETE message.

–>

NR RRC: ULInformationTransfer

TC: CLOSE UE TEST LOOP COMPLETE

–

–

7

The SS transmits one IP PDU.

–

–

–

–

8

The SS transmits an RRCRelease message and move the UE to RRC_IDLE.

<–

NR RRC: RRCRelease

–

–

9

Check: Does the UE transmit an RRCSetupRequest message including establishmentCause of mcs-PriorityAccess within 10 s?

–>

NR RRC: RRCSetupRequest

2

P

10

SS transmit an RRCSetup message.

<–

NR RRC: RRCSetup

–

–

11

The UE transmits an RRCSetupComplete message to confirm the successful completion of the connection establishment.

–>

NR RRC: RRCSetupComplete

5GMM: SERVICE REQUEST

–

–

11A-11C

Steps 5 to 7 of the NR RRC_CONNECTED procedure in TS 38.508-1 Table 4.5.4.2-3 are performed.

–

–

–

–

–

EXCEPTION: Steps 11D and 12 can occur in any order.

–

–

–

–

11D

The UE transmits an RRCReconfigurationComplete message.

–>

NR RRC: RRCReconfigurationComplete

–

–

12

The UE loops back the IP PDU.

–

–

–

–

13

Void

–

–

–

–

–

EXCEPTION: Steps 14a1A1-14a19 describe behaviour that depends on UE configuration; the "lower case letter" identifies a step sequence that takes place if inactiveState is configured

–

–

–

–

14a1A1

IF pc_inactiveState THEN the SS transmits an RRCRelease message to release RRC connection and move the UE to RRC_IDLE.

<–

NR RRC: RRCRelease

–

–

14a1A2

The SS changes the SIB1 of NR Cell 1 according to Table 11.3.6.3.3-4 to set the uac-BarringInfo and adjusts the NR Cells power levels according to row "T2" in table 11.3.6.3.2-1/2.

–

–

–

–

14a2-14a6

Steps 1 to 5 of the mobility registration updating procedure described in TS 38.508-1 [4] Table 4.9.5.2.2-1 are performed on NR Cell 1. (Note 2)

–

–

–

–

14a7-14a10

Steps 5 to 8 of the NR RRC_CONNECTED procedure in TS 38.508-1 Table 4.5.4.2-3 are performed.

–

–

–

–

14a10A

The SS transmits an OPEN UE TEST LOOP message.

<–

NR RRC: DLInformationTransfer

TC: OPEN UE TEST LOOP

–

–

14a10B

The UE transmits an OPEN UE TEST LOOP COMPLETE message.

–>

NR RRC: ULInformationTransfer

TC: OPEN UE TEST LOOP COMPLETE

–

–

14a10C

The SS transmits a CLOSE UE TEST LOOP message.

<–

NR RRC: DLInformationTransfer

TC: CLOSE UE TEST LOOP

–

–

14a10D

The UE transmits a CLOSE UE TEST LOOP COMPLETE message.

–>

NR RRC: ULInformationTransfer

TC: CLOSE UE TEST LOOP COMPLETE

–

–

14a11

The SS transmits one IP PDU.

–

–

–

–

14a12

The SS transmits an RRCRelease message with suspend configuration and move the UE to RRC_INACTIVE.

<–

NR RRC: RRCRelease

–

–

14a13

Check: Does the UE transmit an RRCResumeRequest message including resumeCause of mcs-PriorityAccess within 21 s? (Note 4)

–>

NR RRC: RRCResumeRequest

3

F

14a14

SS changes SIB1 according to Table 11.3.6.3.3-6 and the SS notifies the UE of change of System Information on NR Cell 1 by send Short Message on PDCCH using P-RNTI.

<–

NR RRC: Paging

–

–

14a15

Start Timer=30 sec. (Note 3)

NOTE: This is an arbitrary value to wait for UE initiated RRC resume procedure.

–

–

–

–

–

EXCEPTION: Steps 14a15a1-14a15b8 describes optional behaviour that depends on the UE implementation.

–

–

–

–

14a15a1

Check: Does the UE transmit an RRCResumeRequest message including resumeCause of mcs-PriorityAccess?

–>

NR RRC: RRCResumeRequest

4

P

14a15a2

Stop Timer=30.

–

–

–

–

14a15b1

Timer=30 sec expires

–

–

–

–

14a15b2

The SS transmits a Paging message including a matched identity (correct fullI-RNTI).

<–

NR RRC: Paging

–

–

14a15b3

The UE transmit an RRCResumeRequest message.

–>

NR RRC: RRCResumeRequest

14a15b4

The SS transmits an RRCResume message.

<–

NR RRC: RRCResume

–

–

14a15b5

The UE transmits an RRCResumeComplete message.

–>

NR RRC: RRCResumeComplete

–

–

14a15b5A

The SS transmits an OPEN UE TEST LOOP message.

<–

NR RRC: DLInformationTransfer

TC: OPEN UE TEST LOOP

–

–

14a15b5B

The UE transmits an OPEN UE TEST LOOP COMPLETE message.

–>

NR RRC: ULInformationTransfer

TC: OPEN UE TEST LOOP COMPLETE

–

–

14a15b5C

The SS transmits a CLOSE UE TEST LOOP message.

<–

NR RRC: DLInformationTransfer

TC: CLOSE UE TEST LOOP

–

–

14a15b5D

The UE transmits a CLOSE UE TEST LOOP COMPLETE message.

–>

NR RRC: ULInformationTransfer

TC: CLOSE UE TEST LOOP COMPLETE

–

–

14a15b6

The SS transmits one IP PDU.

–

–

–

–

14a15b7

The SS transmits an RRCRelease message with suspendConfig IE and move the UE to RRC_Inactive state.

<–

NR RRC: RRCRelease

–

–

14a15b8

Check: Does the UE transmit an RRCResumeRequest message including resumeCause of mcs-PriorityAccess?

–>

NR RRC: RRCResumeRequest

4

P

14a16

SS transmit an RRCResume message.

<–

NR RRC: RRCResume

–

–

–

EXCEPTION: Steps 14a17 and 14a18 can occur in any order.

–

–

–

–

14a17

The UE transmits an RRCResumeComplete message to confirm the successful completion of the connection establishment.

–>

NR RRC: RRCResumeComplete

–

–

14a18

The UE loops back the IP PDU.

–

–

–

–

14a19

Void

–

–

–

–

15-28

Void

–

–

–

–

Information Element

Value/remark

Comment

Condition

SIB1 ::= SEQUENCE {

uac-BarringInfo SEQUENCE {

uac-BarringForCommon SEQUENCE (SIZE (1..maxAccessCat-1)) OF UAC-BarringPerCat {

1 entry

UAC-BarringPerCat[1] SEQUENCE {

entry 1

accessCategory

7

(= MO_data)

uac-barringInfoSetIndex

1

Value 1 corresponds to the first entry in uac-BarringInfoSetList

}

}

uac-BarringPerPLMN-List

Not present

uac-BarringInfoSetList SEQUENCE (SIZE(1..maxBarringInfoSet)) OF UAC-BarringInfoSet {

1 entry

UAC-BarringInfoSet[1] SEQUENCE {

entry 1

uac-BarringFactor

p00

0% access probability

uac-BarringTime

s16

16 s

uac-BarringForAccessIdentity

‘1011111’B

Value 1 means that access attempt is not allowed for the corresponding access identity.

The leftmost bit, bit 0 in the bit string corresponds to Access Identity 1.

}

}

uac-AccessCategory1-SelectionAssistanceInfo

Not present

}

}

Information Element

Value/remark

Comment

Condition

RRCSetupRequest ::= SEQUENCE {

rrcSetupRequest SEQUENCE {

establishmentCause

Any allowed value other than mcs-PriorityAccess

Step 2, Step 1AA

mcs-PriorityAccess

Step 9

}

}

Information Element

Value/remark

Comment

Condition

5GS network feature support

‘0000 0001 0000 0010’B

Access identity 2 valid in RPLMN or equivalent PLMN.

IMS voice over PS session supported over 3GPP access.

All other features set to "not supported" including the

‘Interworking without N26 interface not supported’.

Information Element

Value/remark

Comment

Condition

RRCReconfiguration ::= SEQUENCE {

dedicatedNAS-MessageList

Not present

}

Information Element

Value/Remark

Comment

Condition

Service type

‘0101’B

high priority access

Information Element

Value/remark

Comment

Condition

UE test loop mode B LB setup

IP PDU delay

‘0000 0010’B

2 seconds

Information Element

Value/remark

Comment

Condition

SIB1 ::= SEQUENCE {

uac-BarringInfo SEQUENCE {

uac-BarringForCommon SEQUENCE (SIZE (1..maxAccessCat-1)) OF UAC-BarringPerCat {

1 entry

UAC-BarringPerCat[1] SEQUENCE {

entry 1

accessCategory

7

(= MO_data)

uac-barringInfoSetIndex

1

Value 1 corresponds to the first entry in uac-BarringInfoSetList

}

}

uac-BarringPerPLMN-List

Not present

uac-BarringInfoSetList SEQUENCE (SIZE(1..maxBarringInfoSet)) OF SEQUENCE {

1 entry

UAC-BarringInfoSet[1] SEQUENCE {

entry 1

uac-BarringFactor

P00

0% access probability

uac-BarringTime

s16

16 s

uac-BarringForAccessIdentity

1111111

Value 1 means that access attempt is not allowed for the corresponding access identity.

The leftmost bit, bit 0 in the bit string corresponds to Access Identity 1.

}

}

uac-AccessCategory1-SelectionAssistanceInfo

Not present

}

}

Information Element

Value/remark

Comment

Condition

RRCResumeRequest ::= SEQUENCE {

rrcResumeRequest SEQUENCE {

resumeCause

mcs-PriorityAccess

}

}

Information Element

Value/remark

Comment

Condition

SIB1 ::= SEQUENCE {

uac-BarringInfo

Not present

}