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 EF_{UAC_AIC} indicates the UE is configured for access identity 1 and the selected PLMN, if a new PLMN is selected, or 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" 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 EF_{UAC_AIC} indicates the UE is configured for access identity 2 and the selected PLMN, if a new PLMN is selected, or 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" 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 without an ongoing 5GC-MO-LR procedure;

Access attempt to handover of ongoing MMTEL voice call, MMTEL video call or SMSoIP from non-3GPP access

Access attempt is for MT access, or handover of ongoing MMTEL voice call, MMTEL video call or SMSoIP from non-3GPP 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)

4.1

MO IMS registration related signalling

Access attempt is for MO IMS registration related signalling (e.g. IMS initial registration, re-registration, subscription refresh)

or for NAS signalling connection recovery during ongoing procedure for MO IMS registration related signalling (NOTE 2a)

9 (= MO IMS registration related signalling)

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)

8.1

Mobile originated location request

Access attempt is for mobile originated location request (NOTE 9)

3 (= MO_sig)

8.2

Mobile originated signalling transaction towards the PCF

Access attempt is for mobile originated signalling transaction towards the PCF (NOTE 10)

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 as defined in subclause 4.5.5, or for the purpose of NAS signalling connection establishment following fallback indication from lower layers during an ongoing service as defined in subclause 4.5.5, 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 2a: Access for the purpose of NAS signalling connection recovery during an ongoing procedure for MO IMS registration related signalling as defined in subclause 4.5.5, or for the purpose of NAS signalling connection establishment following fallback indication from lower layers during an ongoing procedure for MO IMS registration related signalling as defined in subclause 4.5.5, is mapped to the access category of the MO IMS registration related signalling 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]).

NOTE 9: This includes:
a) the UE-initiated NAS transport procedure for transporting a mobile originated location request;
b) the 5GMM connection management procedure triggered by a) above; and
c) NAS signalling connection recovery during an ongoing 5GC-MO-LR procedure.

NOTE 10: This includes:
a) the UE-initiated NAS transport procedure for transporting a mobile originated signalling
transaction towards the PCF;
b) the 5GMM connection management procedure triggered by a) above; and
c) NAS signalling connection recovery during an ongoing UE triggered V2X policy provisioning procedure.

NR Cell 1

PLMN1

001

01

U – S

Message

1

Make the UE attempt an emergency call dialling a number which is stored on the ME (e.g. 112 or 911). (NOTE 1)

–

–

–

–

2

Check: Does the UE transmit an RRCSetupRequest message with establishmentCause set to ’emergency’ within 30 s’?

–>

NR RRC: RRCSetupRequest

1

F

3

SS modifies NR Cell 1 SIB1 to remove Access barring for AC2 and sends short message. (NOTE 2, NOTE 3)

<–

Short Message

–

–

4

Wait for 2.1* modification period to allow the new system information to take effect

–

–

–

–

5

Start Timer = 84s (NOTE 2, NOTE 4)

–

–

–

–

5Aa2

Stop Timer = 84s

–

–

–

–

5Ab1

Timer = 84s expires

–

–

–

–

5Ab2

Make the UE attempt an emergency call dialling a number which is stored on the ME (e.g. 112 or 911). (NOTE 1)

–

–

–

–

5Ab3

UE transmits an RRCSetupRequest message with establishmentCause set to ‘highPriorityAccess’ to establish an emergency call.

–>

NR RRC: RRCSetupRequest

–

–

6

Void

–

–

–

–

7

The SS transmits an RRCSetup message.

<–

NR RRC: RRCSetup

–

–

–

EXCEPTION: Steps 8a1 to 8b2 describe behaviour that depends on the UE implementation; the "lower case letter" identifies a step sequence that take place if a particular implementation is under test.

–

–

–

–

8a1

The UE transmits an RRCSetupComplete message AND a SERVICE REQUEST message with ‘Service type’ set to ‘high priority access’.

–>

NR RRC: RRCSetupComplete

5GMM: SERVICE REQUEST

–

–

8a2

Steps 4-8 are performed from the generic test procedure as specified in TS 38.508-1 [4] subclause 4.9.11.

–

–

–

–

8b1

The UE transmits an RRCSetupComplete message AND a REGISTRATION REQUEST message with ‘registration type’ set to ‘emergency’. (Note 6)

–>

NR RRC: RRCSetupComplete

5GMM: REGISTRATION REQUEST

–

–

8b2

Steps 5-15 are performed from the generic test procedure as specified in TS 38.508-1 [4] subclause 4.5.2.2-2fv

.

–

–

–

–

9

Void

–

–

–

–

–

EXCEPTION: Steps 10a1 to 10b1 describe behaviour that depends on the UE implementation; the "lower case letter" identifies a step sequence that take place if a particular implementation is under test.

–

–

–

–

10a1

IF pc_SwitchOnOff THEN switch off UE, IF pc_USIM_Removal THEN remove the USIM.

–

–

–

–

10a2

SS starts timer1 = 5 sec to see if UE performs optional Step 10a3a1 (Note 5)

–

–

–

–

10a3a1

The UE transmits a DEREGISTRATION REQUEST message.

–>

NR RRC: ULInformationTransfer

5GMM: DEREGISTRATION REQUEST

10a3a2

The SS transmits an RRCRelease message IF step 10a3a1 was performed ELSE SS implicitly releases the RRC connection.

<–

NR RRC: RRCRelease

–

–

10b1

ELSE power off UE

–

–

–

–

NOTE 1: This could be done by e.g. MMI or AT command.

NOTE 2: Since barring is alleviated, UE may re-attempt an emergency call, triggered at step 1, automatically after T390 stop/expiry without manual intervention.

NOTE 3: Steps 3 to 9 are there to ensure that UE under test supports emergency call and is not initiating it at Step 2 due to access barring for AC2.

NOTE 4: T390 timer value is derived from 38.331[12] T390 = (0.7 + 0.6*rand)*uac-BarringTime where the uac-BarringTime value of 64s is provided in 38.523-1 Table 11.3.7.3.3-1 and where the value of rand is chosen to be 1 as to arrive at the maximum value for T390 of 83.2s rounded up to 84s.

Note 5: The UE may implicitly de-register upon disabling N1 mode capability due to ‘IMS voice not available’

Note 6: UE may try to find service to place the emergency call (step 1) on other RATs since emergency access is barred on NR Cell 1. In this case UE will send a REGISTRATION REQUEST instead of a SERVICE REQUEST.

NOTE 7: UE may perform domain selection and stop T390. If UE move back to the NR Cell 1 during 84s timer running, UE may initiate emergency call before 84s timer expire.

Information Element

Value/remark

Comment

Condition

SIB1 ::= SEQUENCE {

uac-BarringForCommon SEQUENCE {

UAC-BarringPerCatList ::= SEQUENCE (SIZE (1..maxAccessCat-1)) OF UAC-BarringPerCat {

1 entry

UAC-BarringPerCat[1] SEQUENCE {

entry 1

accessCategory

2

uac-barringInfoSetIndex

1

}

}

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

uac-BarringTime

s64

uac-BarringForAccessIdentity

‘0011111’B

}

uac-AccessCategory1-SelectionAssistanceInfo

Not Present

}

}

Information Element

Value/Remark

Comment

Condition

Service type

‘0101’B

High priority access

pc_noOf_PDUsNewConnections > 0

Information Element

Value/remark

Comment

Condition

RRCSetupRequest ::= SEQUENCE {

rrcSetupRequest SEQUENCE {

establishmentCause

highPriorityAccess

}

}