5.4 Unified Access Control information handling for 5G-NR

31.1213GPPRelease 16TSUICC-terminal interfaceUniversal Subscriber Identity Module (USIM) application test specification

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

5.4.1 Unified Access Control – Access identity 0, no access identities indicated by USIM

5.4.1.1 Definition and applicability

The purpose of Unified Access Control procedure is to perform access barring check for a 5GS access attempt associated with a given Access Category and one or more Access Identities upon request from upper layers or the RRC layer.

The 5G network shall be able to broadcast barring control information (i.e. a list of barring parameters associated with an Access Identity and an Access Category) in SIB1.

If no Access Identities are configured in EF_{UAC_AIC} and in EF_ACC, Access Identity 0 is applicable. The UE shall read EF_UAC-AICand EF_ACC as part of USIM Initialization procedure.

The UE shall be able to determine whether or not a particular new access attempt is allowed based on barring parameters that the UE receives from the broadcast barring control information and the configuration in the USIM.

When the NAS detects an access event, the NAS shall perform the mapping of the kind of request to one or more access identities and one access category and lower layers will perform access barring checks for that request based on the determined access identities and access category.

If RRC state is RRC_INACTIVE and the resumption of the RRC connection is triggered due to an RNA Update, RRC layer shall select Access Category as 8 and perform unified access control procedure in case there is no ongoing emergency service.

5.4.1.2 Conformance requirement

1. The Terminal shall read the access control value as part of the USIM-Terminal initialization procedure, and subsequently adopt this value.

Reference:

– 3GPP TS 31.102 [4], clause 5.1.1.2.

2. Access Identities are configured at the UE as listed in TS 22.261 [43] Table 6.22.2.2-1. Access Categories are defined by the combination of conditions related to UE and the type of access attempt as listed in TS 22.261 [43] Table 6.22.2.3-1. One or more Access Identities and only one Access Category are selected and tested for an access attempt.

Reference:

– 3GPP TS 22.261 [43], clause 6.22.2.

3. The UE shall be able to determine whether or not a particular new access attempt is allowed based on uac-BarringInfo broadcast in SIB1. Access Control check shall be performed as per the information received in uac-BarringInfoSetList.

Reference:

– 3GPP TS 38.331 [44], clauses 5.3.14.

4. If the resumption of the RRC connection is triggered due to an RNA update and there is no ongoing emergency service RRC shall select ‘8’ as the Access Category and perform the unified access control procedure.

Reference:

– 3GPP 38.331 [44], clauses 5.3.13.2.

5.4.1.3 Test purpose

1) To verify that the Terminal reads the access control value from EF_UAC-AICand EF_ACC as part of the USIM-Terminal initialisation procedure, and subsequently adopts this value.

2) To verify UE maps the kind of request to one or more access identities and one access category and lower layers performs access barring checks for that request based on the determined access identities and access category.

3) To verify UE performs unified access control procedure if RNA Update procedure is triggered.

5.4.1.4 Method of test

5.4.1.4.1 Initial conditions

The default 5G-NR UICC is used with the following exceptions:

EF_{UAC_AIC}and EF_ACC

No Access Identities configured in EF_{UAC_AIC}and no Access Classes configured in EF_ACC as also shown in table 5.4.1-1 and 5.4.1-2.

EF_IMSI(IMSI)

Logically: 246081357935793

Coding:	B1	B2	B3	B4	B5	B6	B7	B8	B9
Hex	08	29	64	80	31	75	39	75	39

EF_UST (USIM Service Table)

Logically:

User controlled PLMN selector available

Fixed dialling numbers available

The GSM Access available

The Group Identifier level 1 and level 2 not available

Service n 33 (Packed Switched Domain) shall be set to ‘1’

Enabled Services Table available

EPS Mobility Management Information available

Allowed CSG Lists and corresponding indications available

5GS Mobility Management Information available

5G Security Parameters available

Subscription identifier privacy support not available

SUCI calculation by USIM not available

UAC Access Identities support

Byte:	B1	B2	B3	B4	B5	B6	B7	B8
Binary:	xxxx xx1x	xxxx xxxx	xxxx 1×00	xxxx x1xx	xxxx xx11	xxxx xxxx	xxxx xxxx	xxxx xxxx
	B9	B10	B11		B16
	xxxx xxxx	xxxx xxxx	xx11 xxxx	…..	xx10 011x

NETWORK (NG-SS)

Cell A:

Transmits on the BCCH, with the following network parameters:

– TAI (MCC/MNC/TAC): MCC, MNC: see tables 5.4.1-1, TAC="000001".

– CellIdentity: "000000001"

If present in the REGISTRATION ACCEPT, the 5GS network feature support IE indicates Access identity 1 as not valid and Access identity 2 as not valid.

For Table 5.4.1-1:

uac-BarringInfo in SIB1 should be set as in the table:

– Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the table.

For Table 5.4.1-2:

No uac-BarringInfo in SIB1.

Cell B:

Transmits on the BCCH, with the following network parameters:

– TAI (MCC/MNC/TAC): MCC, MNC: see table 5.4.1-2, TAC="000001".

– CellIdentity: "000000002"

If present in the REGISTRATION ACCEPT, the 5GS network feature support IE indicates Access identity 1 as not valid and Access identity 2 as not valid.

For Table 5.4.1-2:

uac-BarringInfo in SIB1 should be set as in the table:

– Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the table.

5.4.1.4.2 Procedure

Steps for the Table 5.4.1-1

a) NG-SS activates Cell A and terminal is switched on and performs Registration if access is allowed according to the table.

b) Using the MMI or EMMI a MO Data call is attempted if required by the test.

c) The test is repeated for each set of values in the table.

Steps for the Table 5.4.1-2

a) NG-SS activates Cell A and terminal is switched on and performs successful Registration.

b) Using the MMI or EMMI set up a successful MO Data call.

c) NG-SS sends RRCRelease with suspendConfig in criticalExtensions (with the choice rrcRelease).

– ran-NotificationAreaInfo in suspendConfig contains the cellList with cellIdentity of Cell A

cellList {

plmn-Identity {mcc, mnc}, — see table 5.4.1-2 for mcc/mnc

ran-AreaCells 000000001’B

}

d) Deactivate Cell A and activate Cell B with uac-BarringInfo in SIB1 set as in the table:

– Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the table.

e) UE attempts to initiate RRCResumeRequest procedure with resumeCause set to rna-Update.

f) The test is repeated for each set of values in the table.

5.4.1.4.3 Acceptance criteria

For the Table 5.4.1-1

– After step a) the UE shall make a successful or not successful Registration to the network in accordance with the result indicated in the table.

– After step b) the UE shall make a successful or not successful MO Data call in accordance with the result indicated in the table if the step is applicable.

For the Table 5.4.1-2

– After step e) the UE shall make a successful or not successful RRC Resumption for RNA Update in accordance with the result indicated in the table.

Table 5.4.1-1

TC Seq#	Access Category	USIM		SIB1		REGISTRATION ACCEPT (5GS network feature support IE)		Result
TC Seq#	Access Category	EF_{UAC_AIC}	EF_ACC (Byte 1 b8-b4)	uac-BarringInfo	PLMN-Identity (MCC/MNC)	MPS indicator Bit	MCS indicator Bit	Registration successful?	MO Data call successful?
1.1	7	0x00 00 00 00	00000	Not Present	246 / 081	0	0	Yes	Yes
1.2	3	0x00 00 00 00	00000	UAC_BarringInfo_Common(3,0×0000000’B)	246 / 081	0	0	No	NA
1.3	3	0x00 00 00 00	00000	UAC_BarringInfo_PerPLMN(3,0×0000000’B)	246 / 081	0	0	No	NA
1.4	3	0x00 00 00 00	00000	UAC_BarringInfo_PerPLMN(3,0×1000000’B)	246 / 081	0	0	No	NA
1.5	7	0x00 00 00 00	00000	UAC_BarringInfo_Common(7,0×0000000’B)	246 / 081	0	0	Yes	No
1.6	7	0x00 00 00 00	00000	UAC_BarringInfo_PerPLMN(7,0×0000000’B)	246 / 081	0	0	Yes	No
1.7	3	0x00 00 00 00	00000	UAC_BarringInfo_Common2 ( 7,0×1000000’B, 3,0×0000000’B)	244 / 081	0	0	No	NA

Table 5.4.1-2

TC Seq#	Access Category	USIM		SIB1		REGISTRATION ACCEPT (5GS network feature support IE)		Result
TC Seq#	Access Category	EF_{UAC_AIC}	EF_ACC (Byte 1 b8-b4)	uac-BarringInfo	PLMN-Identity (MCC/MNC)	MPS indicator Bit	MCS indicator Bit	RRCResumeRequest with resumeCause set to rna-Update successful?
2.1	8	0x00 00 00 00	00000	Not Present	246 / 081	0	0	Yes
2.2	8	0x00 00 00 00	00000	UAC_BarringInfo_Common(8,0×0000000’B)	246 / 081	0	0	No
2.3	8	0x00 00 00 00	00000	UAC_BarringInfo_PerPLMN(8,0×0000000’B)	246 / 081	0	0	No
2.4	8	0x00 00 00 00	00000	UAC_BarringInfo_Common2 ( 7,0×1000000’B, 8,0×0000000’B)	244 / 081	0	0	No

5.4.2 Unified Access Control – Access Identity 1 – MPS indicated by USIM

5.4.2.1 Definition and applicability

The 5G network shall be able to broadcast barring control information (i.e. a list of barring parameters associated with an Access Identity and an Access Category) in SIB1.

The EF_UAC-AICin the USIM contains the configuration information pertaining to access identity 1 allocated for high priority services MPS.

If RRC state is RRC_INACTIVE and the resumption of the RRC connection is triggered due to an RNA Update RRC layer shall select Access Category as 8 and perform unified access control procedure in case there is no ongoing emergency service.

5.4.2.2 Conformance requirement

1. The Terminal shall read the access control value as part of the USIM-Terminal initialization procedure, and subsequently adopt this value.

Reference:

– 3GPP TS 31.102 [4], clause 5.1.1.2.

Reference:

– 3GPP TS 22.261 [43], clause 6.22.2

3. Access Identity 1 is valid if the RPLMN is the HPLMN, EHPLMN or visited PLMN of the home country.

Reference:

– 3GPP TS 24.501 [42], clause 4.5.2

4. The UE shall be able to determine whether or not a particular new access attempt is allowed based on uac-BarringInfo broadcast in SIB1. Access Control check shall be performed as per the information received in uac-BarringInfoSetList.

Reference:

– 3GPP TS 38.331 [44], clauses 5.3.14

5. If the resumption of the RRC connection is triggered due to an RNA update and there is no ongoing emergency service RRC shall select ‘8’ as the Access Category and perform the unified access control procedure.

Reference:

– 3GPP TS 38.331 [44], clauses 5.3.13.2

5.4.2.3 Test purpose

1) To verify that the Terminal reads the access control value from EF_UAC-AICand EF_ACC as part of the USIM-Terminal initialisation procedure, and subsequently adopts this value.

3) To verify the UE determines whether or not a particular access attempt is allowed based on uac-BarringInfo broadcast in SIB1 and if the RPLMN is the HPLMN, EHPLMN or visited PLMN of the home country.

4) To verify UE performs unified access control procedure if RNA Update procedure is triggered.

5.4.2.4 Method of test

5.4.2.4.1 Initial conditions

The default 5G-NR UICC is used with the following exceptions:

EF_{UAC_AIC}and EF_ACC

Access Identitity 1 (and in some test cases additional Access Identities) in EF_{UAC_AIC}is configured and no Access Classes are configured in EF_ACC as given in tables 5.4.2-1 and 5.4.2-2.

EF_IMSI(IMSI)

Logically: 246081357935793

Coding:	B1	B2	B3	B4	B5	B6	B7	B8	B9
Hex	08	29	64	80	31	75	39	75	39

EF_UST (USIM Service Table)

Logically:

User controlled PLMN selector available

Fixed dialling numbers available

The GSM Access available

The Group Identifier level 1 and level 2 not available

Service n 33 (Packed Switched Domain) shall be set to ‘1’

Enabled Services Table available

EPS Mobility Management Information available

Allowed CSG Lists and corresponding indications available

5GS Mobility Management Information available

5G Security Parameters available

Subscription identifier privacy support not available

SUCI calculation by USIM not available

UAC Access Identities support

Byte:	B1	B2	B3	B4	B5	B6	B7	B8
Binary:	xxxx xx1x	xxxx xxxx	xxxx 1×00	xxxx x1xx	xxxx xx11	xxxx xxxx	xxxx xxxx	xxxx xxxx
	B9	B10	B11		B16
	xxxx xxxx	xxxx xxxx	xx11 xxxx	…..	xx10 011x

NETWORK (NG-SS)

Cell A:

Transmits on the BCCH, with the following network parameters:

– TAI (MCC/MNC/TAC): MCC, MNC: see tables 5.4.2-1, TAC="000001".

– CellIdentity : "000000001"

For Table 5.4.2-1:

uac-BarringInfo in SIB1 should be set as in the table:

– Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the table.

For Table 5.4.2-2:

No uac-BarringInfo in SIB1.

Cell B:

Transmits on the BCCH, with the following network parameters:

– TAI (MCC/MNC/TAC): MCC, MNC: see table 5.4.2-2, TAC="000001".

– CellIdentity: "000000002"

For Table 5.4.2-2:

uac-BarringInfo in SIB1 should be set as in the table:

– Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the table.

5.4.2.4.2 Procedure

Steps for the Table 5.4.2-1

a) NG-SS activates Cell A and terminal is switched on and performs Registration if access is allowed according to the table.

b) Using the MMI or EMMI a MO Data call is attempted if required by the test.

c) The test is repeated for each set of values in the table.

Steps for the Table 5.4.2-2

NG-SS activates Cell A and terminal is switched on and performs successful Registration.

Using the MMI or EMMI set up a successful MO Data call.

NG-SS sends RRCRelease with suspendConfig in criticalExtensions (with the choice rrcRelease).

– ran-NotificationAreaInfo in suspendConfig contains the cellList with cellIdentity of Cell A

cellList {

plmn-Identity {mcc, mnc}, — see table 5.4.2-2 for mcc/mnc

ran-AreaCells 000000001’B

}

d) Deactivate Cell A and activate Cell B with uac-BarringInfo in SIB1 set as in the table:

– Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the table.

e) UE attempts to initiate RRCResumeRequest procedure with resumeCause set to rna-Update.

f) The test is repeated for each set of values in the table.

5.4.2.4.3 Acceptance criteria

For the Table 5.4.2-1

– After step a) the UE shall make a successful or not successful Registration to the network in accordance with the result indicated in the table.

– After step b) the UE shall make a successful or not successful MO Data call in accordance with the result indicated in the table if the step is applicable.

For the Table 5.4.2-2

– After step e) the UE shall make a successful or not successful RRC Resumption for RNA Update in accordance with the result indicated in the table.

Table 5.4.2-1

TC Seq#	Access Category	USIM		SIB1		REGISTRATION ACCEPT (5GS network feature support IE)		Result
TC Seq#	Access Category	EF_{UAC_AIC}	EF_ACC (Byte 1 b8-b4)	uac-BarringInfo	PLMN-Identity (MCC/MNC)	MPS indicator Bit	MCS indicator Bit	Registration successful?	MO Data call successful?
1.1	7	0x01 00 00 00	00000	Not Present	246 / 081	0	0	Yes	Yes
1.2	3	0x01 00 00 00	00000	UAC_BarringInfo_Common( 3,0×1000000’B)	246 / 081	0	0	No	NA
1.3	3	0x01 00 00 00	00000	UAC_BarringInfo_PerPLMN( 3,0×1000000’B)	246 / 081	0	0	No	NA
1.4	3	0x01 00 00 00	00000	UAC_BarringInfo_Common( 3,0×1000000’B)	246 / 082	0	0	No	NA
1.5	3	0x01 00 00 00	00000	UAC_BarringInfo_Common( 3,0×0100000’B)	246 / 081	0	0	Yes	Yes
1.6	3	0x03 00 00 00	00000	UAC_BarringInfo_Common( 3,0×0100000’B)	246 / 081	0	0	Yes	Yes
1.7	7	0x01 00 00 00	00000	UAC_BarringInfo_Common( 7,0×0000000’B)	246 / 081	0	0	Yes	Yes
1.8	3	0x01 00 00 00	00000	UAC_BarringInfo_Common( 3,0×0000000’B)	244 / 081	0	0	No	NA
1.9	7	0x01 00 00 00	00000	UAC_BarringInfo_Common( 7,0×1000000’B)	246 / 081	0	0	Yes	No
1.10	7	0x01 00 00 00	00000	UAC_BarringInfo_PerPLMN( 7,0×1000000’B)	246 / 081	0	0	Yes	No
1.11	7	0x01 00 00 00	00000	UAC_BarringInfo_Common( 7,0×1000000’B)	246 / 082	0	0	Yes	No
1.12	7	0x01 00 00 00	00000	UAC_BarringInfo_Common( 7,0×0000000’B)	244 / 081	0	0	Yes	No
1.13	7	0x01 00 00 00	00000	UAC_BarringInfo_Common( 7,0×01000000’B)	244 / 081	1	0	Yes	Yes
1.14	7	0x02 00 00 00	00000	UAC_BarringInfo_Common( 7,0×01000000’B)	244 / 081	1	0	Yes	Yes
1.15	7	0x01 00 00 00	00000	UAC_BarringInfo_Common2( 3,0×0100000’B, 7,0×1000000’B )	246 / 081	0	0	Yes	No
1.16	3	0x01 00 00 00	00000	UAC_BarringInfo_Common2( 7,0×1000000’B, 3,0×0000000’B )	244 / 081	0	0	No	NA

Table 5.4.2-2

TC Seq#	Access Category	USIM		SIB1		REGISTRATION ACCEPT (5GS network feature support IE)		Result
TC Seq#	Access Category	EF_{UAC_AIC}	EF_ACC (Byte 1 b8-b4)	uac-BarringInfo	PLMN-Identity (MCC/MNC)	MPS indicator Bit	MCS indicator Bit	RRCResumeRequest with resumeCause set to rna-Update successful?
2.1	8	0x01 00 00 00	00000	Not Present	246 / 081	0	0	Yes
2.2	8	0x01 00 00 00	00000	UAC_BarringInfo_Common( 8,0×1000000’B)	246 / 081	0	0	No
2.3	8	0x01 00 00 00	00000	UAC_BarringInfo_PerPLMN( 8,0×0000000’B)	246 / 081	0	0	Yes
2.4	8	0x01 00 00 00	00000	UAC_BarringInfo_Common( 8,0×1000000’B)	244 / 081	1	0	No
2.5	8	0x01 00 00 00	00000	UAC_BarringInfo_Common2 ( 7,0×1000000’B, 8,0×0000000’B )	244 / 081	0	0	No
2.6	8	0x01 00 00 00	00000	UAC_BarringInfo_Common( 8,0×0000000’B)	246 / 081	0	0	Yes
2.7	8	0x01 00 00 00	00000	UAC_BarringInfo_PerPLMN( 8,0×1000000’B)	246 / 081	0	0	No

5.4.3 Unified Access Control – Access Identity 1 – no MPS indication by USIM and SUPI not changed

5.4.3.1 Definition and applicability

The 5G network shall be able to broadcast barring control information (i.e. a list of barring parameters associated with an Access Identity and an Access Category) in SIB1.

When the UE is in the country of its HPLMN or in an EHPLMN (if the EHPLMN list is present), and the USIM file EF_{UAC_AIC}does not indicate the UE is configured for access identity 1, the UE uses the MPS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message to determine if access identity 1 is valid.

The UE shall not consider access identity 1 to be valid when the UE is not in the country of its HPLMN prior to receiving the MPS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message being set to "Access identity 1 valid in RPLMN or equivalent PLMN".

5.4.3.2 Conformance requirement

1. The USIM file EF_{UAC_AIC} does not indicate the UE is configured for access identity 1, the UE uses the MPS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message to determine if access identity 1 is valid.

Reference:

– 3GPP TS 24.501 [42], clause 4.5.2.

2. The UE shall not consider access identity 1 to be valid when the UE is not in the country of its HPLMN prior to receiving the MPS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message being set to "Access identity 1 valid in RPLMN or equivalent PLMN".

Reference:

– 3GPP TS 24.501 [42], clause 4.5.2.

3. The MPS indicator is stored together with a PLMN identity of the PLMN that provided it, and is valid in that RPLMN or equivalent PLMN. The MPS indicator can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME, else the UE shall delete the MPS indicator.

Reference:

– 3GPP TS 24.501 [42], Annex C.

4. Access Identity 1 is valid if the RPLMN is the HPLMN, EHPLMN or visited PLMN of the home country.

Reference:

– 3GPP TS 24.501 [42], clause 4.5.2

5. Upon receiving a REGISTRATION ACCEPT message with the MPS indicator bit set to "Access identity 1 valid", the UE shall act as a UE with access identity 1 configured for MPS in all NG-RAN of the registered PLMN and its equivalent PLMNs. The MPS indicator bit in the 5GS network feature support IE provided in the REGISTRATION ACCEPT message is valid until the UE receives a REGISTRATION ACCEPT message with the MPS indicator bit set to "Access identity 1 not valid" or until the UE selects a non-equivalent PLMN. Access identity 1 is only applicable while the UE is in N1 mode.

Reference:

– 3GPP TS 24.501 [42], clause 5.5.1.3.4

6. The UE shall be able to determine whether or not a particular new access attempt is allowed based on uac‑BarringInfo broadcast in SIB1. Access Control check shall be performed as per the information received in uac‑BarringInfoSetList.

Reference:

– 3GPP TS 38.331 [44], clauses 5.3.14

5.4.3.3 Test purpose

1) To verify if the RPLMN is the HPLMN, EHPLMN or visited PLMN of the home country and the USIM file EF_{UAC_AIC} does not indicate the UE is configured for access identity 1 and the MPS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message is received, UE considers access identity as 1 for access barring.

2) To verify the MPS indicator is stored together with a PLMN identity of the PLMN that provided it, and the MPS indicator can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME,

3) To verify that the UE maps the kind of request to one or more access identities and one access category and lower layers performs access barring checks for that request based on the determined access identities and access category.

4) To verify that the UE determines whether or not a particular access attempt is allowed based on uac‑BarringInfo broadcast in SIB1 and if the RPLMN is the HPLMN, EHPLMN or visited PLMN of the home country.

5) To verify that a UE operated with a USIM where the file EF_{UAC_AIC}does not indicate access identity 1, after a change of the REGISTRATION ACCEPT message with the MPS indicator bit set to "Access identity 1 not valid", or when the UE has selected a non-equivalent PLMN, the UE is acting as if it is configured for access identity 0.

5.4.3.4 Method of test

5.4.3.4.1 Initial conditions

The default 5G-NR UICC is used with the following exceptions:

EF_{UAC_AIC}and EF_ACC

No Access Identity is configured in EF_{UAC_AIC} and no Access Classes are configured in EF_ACC as given in table 5.4.3-1.

EF_IMSI(IMSI)

Logically: 246081357935793

Coding:	B1	B2	B3	B4	B5	B6	B7	B8	B9
Hex	08	29	64	80	31	75	39	75	39

EF_UST (USIM Service Table)

Logically:

User controlled PLMN selector available

Fixed dialling numbers available

The GSM Access available

The Group Identifier level 1 and level 2 not available

Service n 33 (Packed Switched Domain) shall be set to ‘1’

Enabled Services Table available

EPS Mobility Management Information available

Allowed CSG Lists and corresponding indications available

5GS Mobility Management Information available

5G Security Parameters available

Subscription identifier privacy support not available

SUCI calculation by USIM not available

UAC Access Identities support

Byte:	B1	B2	B3	B4	B5	B6	B7	B8
Binary:	xxxx xx1x	xxxx xxxx	xxxx 1×00	xxxx x1xx	xxxx xx11	xxxx xxxx	xxxx xxxx	xxxx xxxx
	B9	B10	B11		B16
	xxxx xxxx	xxxx xxxx	xx11 xxxx	…..	xx10 011x

NETWORK (NG-SS)

Cell A:

Transmits on the BCCH, with the following network parameters:

– TAI (MCC/MNC/TAC): 246/081/000001.

– CellIdentity: "000000001"

For Table 5.4.3-1:

After turning on the cell for the 2^nd time, uac‑BarringInfo in SIB1 should be set as in the table:

– Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the table.

Cell B:

Transmits on the BCCH, with the following network parameters:

TAI (MCC/MNC/TAC): MCC, MNC: see table 5.4.3-1, TAC: "000002".

CellIdentity: "000000002"

For Table 5.4.3-1:

uac-BarringInfo in SIB1 should be set as in the table:

– Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the table.

5.4.3.4.2 Procedure

Steps for the Table 5.4.3-1

a) The NG-SS activates Cell A without uac‑BarringInfo in SIB1, the ME is switched on (1^st time) and sends a REGISTRATION REQUEST to Cell A.

b) Cell A responds with a REGISTRATION ACCEPT message with the MPS indicator bit set to "Access identity 1 valid".

c) The ME is switched off, the NG-SS deactivates Cell A.

d) The NG-SS activates Cell A or B with SIB1 as specified in the table.

e) The ME is switched on again (2^nd time) using the same USIM and sends a REGISTRATION REQUEST to the cell activated in step d).

f) The cell activated in step d) responds with a REGISTRATION ACCEPT message without 5GS network feature support IE.

g) Using the MMI or EMMI a MO Data call is attempted if required by the test.

h) The test is repeated for each set of values in the table.

5.4.3.4.3 Acceptance criteria

For the Table 5.4.3-1

– After step e) the UE shall make a successful or not successful Registration to the network in accordance with the result indicated in the table.

– After step g) the UE shall make a successful or not successful MO data call in accordance with the result indicated in the table.

Table 5.4.3-1

TC Seq#)	Access Category	USIM		SIB1 of Cell A or B after the 2^nd power up of the ME			REGISTRATION ACCEPT (5GS network feature support IE) on Cell A at 1^st power up of the ME		Result
TC Seq#)	Access Category	EF_{UAC_AIC}	EF_ACC (Byte 1 b8-b4)	Cell A or B	uac-BarringInfo	PLMN-Identity (MCC/MNC)	MPS indicator Bit	MCS indicator Bit	Registration successful?	MO Data call successful?
1.1	3	0x00 00 00 00	00000	Cell A	Not Present	246 / 081	1	0	Yes	Yes
1.2	3	0x00 00 00 00	00000	Cell A	UAC_BarringInfo_Common (3,0×1000000’B)	246 / 081	1	0	No	N/A
1.3	7	0x00 00 00 00	00000	Cell A	UAC_BarringInfo_Common (7,0×0100000’B)	246 / 081	1	0	Yes	No
1.4	3	0x00 00 00 00	00000	Cell A	UAC_BarringInfo_Common (3,0×0100000’B)	246 / 081	1	0	Yes	Yes
1.5	3	0x00 00 00 00	00000	Cell B	UAC_BarringInfo_PerPLMN (3,0×0100000’B)	246 / 082	1	0	No	N/A
1.6	3	0x00 00 00 00	00000	Cell B	UAC_BarringInfo_Common (3,0×0000000’B)	244 / 081	1	0	No	N/A
1.7	7	0x00 00 00 00	00000	Cell B	UAC_BarringInfo_Common (7,0×0100000’B)	244 / 081	1	0	Yes	No
1.8	7	0x00 00 00 00	00000	Cell B	UAC_BarringInfo_Common (7,0×0100000’B)	244 / 081	1	1	Yes	No

5.4.4 Unified Access Control – Access Identity 1 – no MPS indication by USIM and SUPI is changed

5.4.4.1 Definition and applicability

The 5G network shall be able to broadcast barring control information (i.e. a list of barring parameters associated with an Access Identity and an Access Category) in SIB1.

When the UE is in the country of its HPLMN or in an EHPLMN (if the EHPLMN list is present), and the USIM file EF_{UAC_AIC} does not indicate the UE is configured for access identity 1, the UE uses the MPS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message to determine if access identity 1 is valid.

The MPS indicator is stored together with a PLMN identity of the PLMN that provided it and is valid in that RPLMN or equivalent PLMN. The MPS indicator can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME, else the UE shall delete the MPS indicator.

5.4.4.2 Conformance requirement

1. When the UE is in the country of its HPLMN, and the USIM file EF_{UAC_AIC} does not indicate the UE is configured for access identity 1, the UE uses the MPS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message to determine if access identity 1 is valid.

Reference:

– 3GPP TS 24.501 [42], clause 4.5.2.

Reference:

– 3GPP TS 24.501 [42], clause 4.5.2.

3. Upon receiving a REGISTRATION ACCEPT message with the MPS indicator bit set to "Access identity 1 valid" in RPLMN or equivalent PLMN, the UE shall act as a UE with access identity 1 configured for MPS in all NG-RAN of the registered PLMN and its equivalent PLMNs. The MPS indicator bit in the 5GS network feature support IE provided in the REGISTRATION ACCEPT message is valid until the UE receives a REGISTRATION ACCEPT message with the MPS indicator bit set to "Access identity 1 not valid in RPLMN or equivalent PLMN" or until the UE selects a non-equivalent PLMN. Access identity 1 is only applicable while the UE is in N1 mode.

Reference:

– 3GPP TS 24.501 [42], clause 5.5.1.2.4.

4- The MPS indicator is stored together with a PLMN identity of the PLMN that provided it, and is valid in that RPLMN or equivalent PLMN. The MPS indicator can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME, else the UE shall delete the MPS indicator.

Reference:

– 3GPP TS 24.501 [42], Annex C.

5. The UE shall be able to determine whether or not a particular new access attempt is allowed based on uac BarringInfo broadcast in SIB1. Access Control check shall be performed as per the information received in uac BarringInfoSetList.

Reference:

– 3GPP TS 38.331 [44], clauses 5.3.14

5.4.4.3 Test purpose

2) To verify that the MPS indicator bit in the 5GS network feature support IE provided in the REGISTRATION ACCEPT message is valid until the UE receives a REGISTRATION ACCEPT message with the MPS indicator bit set to "Access identity 1 not valid" or until the UE selects a non-equivalent PLMN.

3) To verify the MPS indicator is stored together with a PLMN identity of the PLMN that provided it, and the MPS indicator can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME.

4) To verify that the UE maps the kind of request to one or more access identities and one access category and lower layers performs access barring checks for that request based on the determined access identities and access category.

5.4.4.4 Method of test

5.4.4.4.1 Initial conditions

The default 5G-NR UICC is used with the following exceptions:

EF_{UAC_AIC}and EF_ACC

No Access Identity is configured in EF_{UAC_AIC}and no Access Classes are configured in EF_ACC as given in table 5.4.4-1.

EF_IMSI(IMSI)

Logically: 246081357935793

Coding:	B1	B2	B3	B4	B5	B6	B7	B8	B9
Hex	08	29	64	80	31	75	39	75	39

EF_UST (USIM Service Table)

Logically:

User controlled PLMN selector available

Fixed dialling numbers available

The GSM Access available

The Group Identifier level 1 and level 2 not available

Service n 33 (Packed Switched Domain) shall be set to ‘1’

Enabled Services Table available

EPS Mobility Management Information available

Allowed CSG Lists and corresponding indications available

5GS Mobility Management Information available

5G Security Parameters available

Subscription identifier privacy support not available

SUCI calculation by USIM not available

UAC Access Identities support

Byte:	B1	B2	B3	B4	B5	B6	B7	B8
Binary:	xxxx xx1x	xxxx xxxx	xxxx 1×00	xxxx x1xx	xxxx xx11	xxxx xxxx	xxxx xxxx	xxxx xxxx

	B9	B10	B11		B16
	xxxx xxxx	xxxx xxxx	xx11 xxxx	…..	xx10 011x

NETWORK (NG-SS)

Cell A:

Transmits on the BCCH, with the following network parameters:

– TAI (MCC/MNC/TAC): 246/081/000001.

– CellIdentity: "000000001"

For Table 5.4.4-1:

After turning on the cell for the 2^nd time, uac‑BarringInfo in SIB1 should be set as in the table:

– Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the table.

Cell B:

Transmits on the BCCH, with the following network parameters:

– TAI (MCC/MNC/TAC): MCC, MNC: see table 5.4.4-1, TAC="000002".

– CellIdentity: "000000002"

For Table 5.4.4-1:

uac-BarringInfo in SIB1 should be set as in the table:

– Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the table.

5.4.4.4.2 Procedure

Steps for the Table 5.4.4-1

a) NG-SS activates Cell A without uac‑BarringInfo in SIB1, the ME is switched on (1^st time) and sends a REGISTRATION REQUEST to Cell A.

b) Cell A responds with a REGISTRATION ACCEPT message with the MPS indicator bit set to "Access identity 1 valid".

c) The ME is switched off, The NG-SS deactivates Cell A.

d) The NG-SS activates Cell A or B with SIB1 as specified in the table.

e) The ME is switched on again (2^nd time) with a different USIM (e.g.: IMSI set to 24681685533963) and sends a REGISTRATION REQUEST to the Cell in step d).

f) Cell A or B (as specified in the table) responds with a REGISTRATION ACCEPT message without 5GS network feature support IE.

g) Using the MMI or EMMI a MO Data call is attempted if required by the test.

h) The test is repeated for each set of values in the table.

5.4.4.4.3 Acceptance criteria

For the Table 5.4.4-1

– After step e) the UE shall make a successful or not successful Registration to the network in accordance with the result indicated in the table.

– After step g) the UE shall make a successful or not successful MO data call in accordance with the result indicated in the table

Table 5.4.4-1

TC Seq#)	Access Category	USIM		SIB1 of Cell A or B after the 2^nd power up of the ME			REGISTRATION ACCEPT (5GS network feature support IE) on Cell A at 1^st power up of the ME		Result
TC Seq#)	Access Category	EF_{UAC_AIC}	EF_ACC (Byte 1 b8-b4)	Cell A or B	uac-BarringInfo	PLMN-Identity (MCC/MNC)	MPS indicator Bit	MCS indicator Bit	Registration successful?	MO Data call successful?
1.1	3	0x00 00 00 00	00000	Cell A	Not Present	246 / 081	1	0	Yes	Yes
1.2	3	0x00 00 00 00	00000	Cell A	UAC_BarringInfo_Common( 3,0×0100000’B)	246 / 081	1	0	No	NA
1.3	7	0x00 00 00 00	00000	Cell A	UAC_BarringInfo_Common( 7,0×0100000’B)	246 / 081	1	0	Yes	No
1.4	3	0x00 00 00 00	00000	Cell A	UAC_BarringInfo_Common( 3,0×0000000’B)	246 / 081	1	0	No	NA
1.5	3	0x00 00 00 00	00000	Cell B	UAC_BarringInfo_Common( 3,0×0100000’B)	246 / 082	1	0	No	NA
1.6	3	0x00 00 00 00	00000	Cell B	UAC_BarringInfo_PerPLMN( 3,0×01000001’B)	244 / 081	1	0	No	NA
1.7	7	0x00 00 00 00	00000	Cell B	UAC_BarringInfo_Common( 7,0×0000000’B)	244 / 081	1	0	Yes	No

5.4.5 Unified Access Control – Access Identity 2 – MCS indicated by USIM

5.4.5.1 Definition and applicability

The 5G network shall be able to broadcast barring control information (i.e. a list of barring parameters associated with an Access Identity and an Access Category) in SIB1.

The EF_UAC-AICin the USIM contains the configuration information pertaining to access identity 2 allocated for high priority services MCS.

5.4.5.2 Conformance requirement

1. The Terminal shall read the access control value as part of the USIM-Terminal initialization procedure, and subsequently adopt this value.

Reference:

– 3GPP TS 31.102 [4], clause 5.1.1.2.

2. Access Identities are configured at the UE as listed in 3GPP TS 22.261 [43] Table 6.22.2.2-1. Access Categories are defined by the combination of conditions related to UE and the type of access attempt as listed in 3GPP TS 22.261 [43] Table 6.22.2.3-1. One or more Access Identities and only one Access Category are selected and tested for an access attempt.

Reference:

– 3GPP TS 22.261 [43], clause 6.22.2

3. Access Identity 2 is valid if the RPLMN is the HPLMN, EHPLMN or visited PLMN of the home country.

Reference:

– 3GPP TS 24.501 [42], clause 4.5.2

Reference:

– 3GPP TS 38.331 [44], clauses 5.3.14

Reference:

– 3GPP TS 38.331 [44], clauses 5.3.13.2

5.4.5.3 Test purpose

1) To verify that the Terminal reads the access control value from EF_UAC-AICand EF_ACC as part of the USIM-Terminal initialisation procedure, and subsequently adopts this value.

4) To verify UE performs unified access control procedure if RNA Update procedure is triggered.

5.4.5.4 Method of test

5.4.5.4.1 Initial conditions

The default 5G-NR UICC is used with the following exceptions:

EF_{UAC_AIC}and EF_ACC

Access Identity 2 (and in some test cases additional Access Identities) in EF_{UAC_AIC}is configured and no Access Classes are configured in EF_ACC as given in tables 5.4.5-1 and 5.4.5-2.

EF_IMSI(IMSI)

Logically: 246081357935793

Coding:	B1	B2	B3	B4	B5	B6	B7	B8	B9
Hex	08	29	64	80	31	75	39	75	39

EF_UST (USIM Service Table)

Logically:

User controlled PLMN selector available

Fixed dialling numbers available

The GSM Access available

The Group Identifier level 1 and level 2 not available

Service n 33 (Packed Switched Domain) shall be set to ‘1’

Enabled Services Table available

EPS Mobility Management Information available

Allowed CSG Lists and corresponding indications available

5GS Mobility Management Information available

5G Security Parameters available

Subscription identifier privacy support not available

SUCI calculation by USIM not available

UAC Access Identities support

Byte:	B1	B2	B3	B4	B5	B6	B7	B8
Binary:	xxxx xx1x	xxxx xxxx	xxxx 1×00	xxxx x1xx	xxxx xx11	xxxx xxxx	xxxx xxxx	xxxx xxxx
	B9	B10	B11		B16
	xxxx xxxx	xxxx xxxx	xx11 xxxx	…..	xx10 011x

NETWORK (NG-SS)

Cell A:

Transmits on the BCCH, with the following network parameters:

– TAI (MCC/MNC/TAC): MCC, MNC: see tables 5.4.5-x, TAC="000001".

– CellIdentity : "000000001"

For Table 5.4.5-1:

uac-BarringInfo in SIB1 should be set as in the table:

– Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the table.

For Table 5.4.5-2:

No uac-BarringInfo in SIB1.

Cell B:

Transmits on the BCCH, with the following network parameters:

– TAI (MCC/MNC/TAC): MCC, MNC: see table 5.4.5-2, TAC="000001".

– CellIdentity: "000000002"

For Table 5.4.5-2:

uac-BarringInfo in SIB1 should be set as in the table:

– Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the table.

5.4.5.4.2 Procedure

Steps for the Table 5.4.5-1

a) NG-SS activates Cell A and terminal is switched on and performs Registration if access is allowed according to the table.

b) Using the MMI or EMMI a MO Data call is attempted if required by the test.

c) The test is repeated for each set of values in the table.

Steps for the Table 5.4.5-2

a) NG-SS activates Cell A and terminal is switched on and performs successful Registration.

b) Using the MMI or EMMI set up a successful MO Data call.

c) NG-SS sends RRCRelease with suspendConfig in criticalExtensions (with the choice rrcRelease).

– ran-NotificationAreaInfo in suspendConfig contains the cellList with cellIdentity of Cell A

cellList {

plmn-Identity {mcc, mnc}, — see table 5.4.5-2 for mcc/mnc

ran-AreaCells 000000001’B

}

d) Deactivate Cell A and activate Cell B with uac-BarringInfo in SIB1 set as in the table:

– Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the table.

e) UE attempts to initiate RRCResumeRequest procedure with resumeCause set to rna-Update.

f) The test is repeated for each set of values in the table.

5.4.5.4.3 Acceptance criteria

For the Table 5.4.5-1

– After step a) the UE shall make a successful or not successful Registration to the network in accordance with the result indicated in the table.

– After step b) the UE shall make a successful or not successful MO Data call in accordance with the result indicated in the table if the step is applicable.

For the Table 5.4.5-2

– After step e) the UE shall make a successful or not successful RRC Resumption for RNA Update in accordance with the result indicated in the table.

Table 5.4.5-1

TC Seq#	Access Category	USIM		SIB1		REGISTRATION ACCEPT (5GS network feature support IE)		Result
TC Seq#	Access Category	EF_{UAC_AIC}	EF_ACC (Byte 1 b8-b4)	uac-BarringInfo	PLMN-Identity (MCC/MNC)	MPS indicator Bit	MCS indicator Bit	Registration successful?	MO Data call successful?
1.1	7	0x02 00 00 00	00000	Not Present	246 / 081	0	0	Yes	Yes
1.2	3	0x02 00 00 00	00000	UAC_BarringInfo_Common( 3,0×0100000’B)	246 / 081	0	0	No	NA
1.3	3	0x02 00 00 00	00000	UAC_BarringInfo_PerPLMN( 3,0×0100000’B)	246 / 081	0	0	No	NA
1.4	3	0x02 00 00 00	00000	UAC_BarringInfo_Common( 3,0×0100000’B)	246 / 082	0	0	No	NA
1.5	3	0x02 00 00 00	00000	UAC_BarringInfo_Common( 3,0×1000000’B)	246 / 081	0	0	Yes	Yes
1.6	3	0x03 00 00 00	00000	UAC_BarringInfo_Common( 3,0×1000000’B)	246 / 081	0	0	Yes	Yes
1.7	7	0x02 00 00 00	00000	UAC_BarringInfo_Common( 7,0×0000000’B)	246 / 081	0	0	Yes	Yes
1.8	3	0x02 00 00 00	00000	UAC_BarringInfo_Common( 3,0×0000000’B)	244 / 081	0	0	No	NA
1.9	7	0x02 00 00 00	00000	UAC_BarringInfo_Common( 7,0×0100000’B)	246 / 081	0	0	Yes	No
1.10	7	0x02 00 00 00	00000	UAC_BarringInfo_PerPLMN( 7,0×0100000’B)	246 / 081	0	0	Yes	No
1.11	7	0x02 00 00 00	00000	UAC_BarringInfo_Common( 7,0×0100000’B)	246 / 082	0	0	Yes	No
1.12	7	0x02 00 00 00	00000	UAC_BarringInfo_Common( 7,0×0000000’B)	244 / 081	0	0	Yes	No
1.13	7	0x02 00 00 00	00000	UAC_BarringInfo_Common( 7,0×10000000’B)	244 / 081	0	1	Yes	Yes
1.14	7	0x01 00 00 00	00000	UAC_BarringInfo_Common( 7,0×10000000’B)	244 / 081	0	1	Yes	Yes
1.15	7	0x02 00 00 00	00000	UAC_BarringInfo_Common2( 3,0×1000000’B, 7,0×0100000’B)	246 / 081	0	0	Yes	No
1.16	3	0x02 00 00 00	00000	UAC_BarringInfo_Common2( 7,0×0100000’B, 3,0×0000000’B)	244 / 081	0	0	No	NA

Table 5.4.5-2

TC Seq#	Access Category	USIM		SIB1		REGISTRATION ACCEPT (5GS network feature support IE)		Result
TC Seq#	Access Category	EF_{UAC_AIC}	EF_ACC (Byte 1 b8-b4)	uac-BarringInfo	PLMN-Identity (MCC/MNC)	MPS indicator Bit	MCS indicator Bit	RRCResumeRequest with resumeCause set to rna-Update successful?
2.1	8	0x02 00 00 00	00000	Not Present	246 / 081	0	0	Yes
2.2	8	0x02 00 00 00	00000	UAC_BarringInfo_Common( 8,0×0100000’B)	246 / 081	0	0	No
2.3	8	0x02 00 00 00	00000	UAC_BarringInfo_PerPLMN( 8,0×0000000’B)	246 / 081	0	0	Yes
2.4	8	0x02 00 00 00	00000	UAC_BarringInfo_Common( 8,0×0100000’B)	244 / 081	0	1	No
2.5	8	0x02 00 00 00	00000	UAC_BarringInfo_Common2( 7,0×0100000’B, 8,0×0000000’B)	244 / 081	0	0	No

5.4.6 Unified Access Control – Access Identity 2 – no MCS indication by USIM and SUPI is not changed

5.4.6.1 Definition and applicability

The 5G network shall be able to broadcast barring control information (i.e. a list of barring parameters associated with an Access Identity and an Access Category) in SIB1.

When the UE is in the country of its HPLMN or in an EHPLMN (if the EHPLMN list is present), and the USIM file EF_{UAC_AIC}does not indicate the UE is configured for access identity 2, the UE uses the MCS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message to determine if access identity 2 is valid.

The UE shall not consider access identity 2 to be valid when the UE is not in the country of its HPLMN prior to receiving the MCS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message being set to "Access identity 2 valid in RPLMN or equivalent PLMN".

5.4.6.2 Conformance requirement

1. The USIM file EF_{UAC_AIC} does not indicate the UE is configured for access identity 2, the UE uses the MCS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message to determine if access identity 2 is valid.

Reference:

– 3GPP TS 24.501 [42], clause 4.5.2.

2. The UE shall not consider access identity 2 to be valid when the UE is not in the country of its HPLMN prior to receiving the MCS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message being set to "Access identity 2 valid in RPLMN or equivalent PLMN".

Reference:

– 3GPP TS 24.501 [42], clause 4.5.2.

3. The MCS indicator is stored together with a PLMN identity of the PLMN that provided it, and is valid in that RPLMN or equivalent PLMN. The MCS indicator can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME, else the UE shall delete the MCS indicator.

Reference:

– 3GPP TS 24.501 [42], Annex C.

4. Access Identity 2 is valid if the RPLMN is the HPLMN, EHPLMN or visited PLMN of the home country.

Reference:

– 3GPP TS 24.501 [42], clause 4.5.2

6. Upon receiving a REGISTRATION ACCEPT message with the MCS indicator bit set to "Access identity 2 valid", the UE shall act as a UE with access identity 2 configured for MCS in all NG-RAN of the registered PLMN and its equivalent PLMNs. The MCS indicator bit in the 5GS network feature support IE provided in the REGISTRATION ACCEPT message is valid until the UE receives a REGISTRATION ACCEPT message with the MCS indicator bit set to "Access identity 2 not valid" or until the UE selects a non-equivalent PLMN. Access identity 2 is only applicable while the UE is in N1 mode.

Reference:

– 3GPP TS 24.501 [42], clause 5.5.1.3.4

Reference:

– 3GPP TS 38.331 [44], clauses 5.3.14

5.4.6.3 Test purpose

1) To verify if the RPLMN is the HPLMN, EHPLMN or visited PLMN of the home country and the USIM file EF_{UAC_AIC} does not indicate the UE is configured for access identity 2 and the MCS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message is received, UE considers access identity as 2 for access barring.

2) To verify the MCS indicator is stored together with a PLMN identity of the PLMN that provided it, and the MCS indicator can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME,

5) To verify that a UE operated with a USIM where the file EF_{UAC_AIC}does not indicate access identity 2, after a change of the REGISTRATION ACCEPT message with the MCS indicator bit set to "Access identity 2 not valid", or when the UE has selected a non-equivalent PLMN, the UE is acting as if it is configured for access identity 0.

5.4.6.4 Method of test

5.4.6.4.1 Initial conditions

The default 5G-NR UICC is used with the following exceptions:

EF_{UAC_AIC}and EF_ACC

No Access Identity is configured in EF_{UAC_AIC}and no Access Classes are configured in EF_ACC as given in tables 5.4.6-1.

EF_IMSI(IMSI)

Logically: 246081357935793

Coding:	B1	B2	B3	B4	B5	B6	B7	B8	B9
Hex	08	29	64	80	31	75	39	75	39

EF_UST (USIM Service Table)

Logically:

User controlled PLMN selector available

Fixed dialling numbers available

The GSM Access available

The Group Identifier level 1 and level 2 not available

Service n 33 (Packed Switched Domain) shall be set to ‘1’

Enabled Services Table available

EPS Mobility Management Information available

Allowed CSG Lists and corresponding indications available

5GS Mobility Management Information available

5G Security Parameters available

Subscription identifier privacy support not available

SUCI calculation by USIM not available

UAC Access Identities support

Byte:	B1	B2	B3	B4	B5	B6	B7	B8
Binary:	xxxx xx1x	xxxx xxxx	xxxx 1×00	xxxx x1xx	xxxx xx11	xxxx xxxx	xxxx xxxx	xxxx xxxx
	B9	B10	B11		B16
	xxxx xxxx	xxxx xxxx	xx11 xxxx	…..	xx10 011x

NETWORK (NG-SS)

Cell A:

Transmits on the BCCH, with the following network parameters:

– MCC, MNC: 246/081

– TAC: ="000001".

– CellIdentity: "000000001"

For Table 5.4.6-1:

After turning on the cell for the 2^nd time, uac‑BarringInfo in SIB1 should be set as in the table:

Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the table.

Cell B:

Transmits on the BCCH, with the following network parameters:

– TAI (MCC/MNC/TAC): MCC, MNC: see table 5.4.6-1, TAC="000002".

– CellIdentity: "000000002"

For Table 5.4.6-1:

uac-BarringInfo in SIB1 should be set as in the table:

Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the table.

5.4.6.4.2 Procedure

Steps for the Table 5.4.6-1

a) NG-SS activates Cell A without uac‑BarringInfo in SIB1, the ME is switched on (1^st time) and sends a REGISTRATION REQUEST to Cell A.

b) Cell A responds with a REGISTRATION ACCEPT message with the MCS indicator bit set to "Access identity 2 valid".

c) The ME is switched off and turned off Cell A.

d) Turn on Cell A or B with SIB1 as specified in the table.

e) The ME is switched on again (2^nd time) using the same USIM and sends a REGISTRATION REQUEST to the Cell in step d).

f) Cell A or B (as specified in the table) responds with a REGISTRATION ACCEPT message without 5GS network feature support IE.

g) Using the MMI or EMMI a MO Data call is attempted if required by the test.

h) The test is repeated for each set of values in the table.

5.4.6.4.3 Acceptance criteria

For the Table 5.4.6-1

– After step e) the UE shall make a successful or not successful Registration to the network in accordance with the result indicated in the table.

– After step g) the UE shall make a successful or not successful MO data call in accordance with the result indicated in the table.

Table 5.4.6-1

TC Seq#)	Access Category	USIM		SIB1 of Cell A or B after the 2^nd power up of the ME			REGISTRATION ACCEPT (5GS network feature support IE) on Cell A at 1^st power up of the ME		Result
TC Seq#)	Access Category	EF_{UAC_AIC}	EF_ACC (Byte 1 b8-b4)	Cell A or B	uac-BarringInfo	PLMN-Identity (MCC/MNC)	MPS indicator Bit	MCS indicator Bit	Registration successful?	MO Data call successful?
1.1	3	0x00 00 00 00	00000	Cell A	Not Present	246 / 081	1	0	Yes	Yes
1.2	3	0x00 00 00 00	00000	Cell A	UAC_BarringInfo_Common( 3,0×0100000’B)	246 / 081	0	1	No	NA
1.3	7	0x00 00 00 00	00000	Cell A	UAC_BarringInfo_Common( 7,0×1000000’B)	246 / 081	0	1	Yes	No
1.4	3	0x00 00 00 00	00000	Cell A	UAC_BarringInfo_Common( 3,0×1000000’B)	246 / 081	0	1	Yes	Yes
1.5	3	0x00 00 00 00	00000	Cell B	UAC_BarringInfo_Common( 3,0×1000000’B)	246 / 082	0	1	No	NA
1.6	3	0x00 00 00 00	00000	Cell B	UAC_BarringInfo_PerPLMN( 3,0×1000000’B)	244 / 081	0	1	No	NA
1.7	7	0x00 00 00 00	00000	Cell B	UAC_BarringInfo_Common( 7,0×0000000’B)	244 / 081	0	1	Yes	No

5.4.7 Unified Access Control – Access Identity 2 – no MCS indication by USIM and SUPI is changed

5.4.7.1 Definition and applicability

The 5G network shall be able to broadcast barring control information (i.e. a list of barring parameters associated with an Access Identity and an Access Category) in SIB1.

When the USIM file EF_{UAC_AIC}does not indicate the UE is configured for access identity 2, the UE uses the MCS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message to determine if access identity 2 is valid.

The MCS indicator is stored together with a PLMN identity of the PLMN that provided it, and is valid in that RPLMN or equivalent PLMN. The MCS indicator can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME, else the UE shall delete the MCS indicator.

5.4.7.2 Conformance requirement

1. When the UE is in the country of its HPLMN, and the USIM file EF_{UAC_AIC} does not indicate the UE is configured for access identity 2, the UE uses the MCS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message to determine if access identity 2 is valid.

Reference:

– 3GPP TS 24.501 [42], clause 4.5.2.

Reference:

– 3GPP TS 24.501 [42], clause 4.5.2.

3. The UE shall consider access identity 2 to be valid when the network informs the UE that the use of access identity 2 is valid in the RPLMN or equivalent PLMN by setting the MCS indicator bit of the 5GS network feature support IE to "Access identity 2 valid", in the REGISTRATION ACCEPT message, the UE shall act as a UE with access identity 2 configured for MCS in all NG-RAN of the registered PLMN and its equivalent PLMNs, until the UE receives a REGISTRATION ACCEPT message with the MCS indicator bit set to "Access identity 2 not valid" or until the UE selects a non-equivalent PLMN. Access identity 2 is only applicable while the UE is in N1 mode.

Reference:

– 3GPP TS 24.501 [42], clause 5.5.1.2.4.

4. The MCS indicator is stored together with a PLMN identity of the PLMN that provided it, and is valid in that RPLMN or equivalent PLMN. The MCS indicator can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME, else the UE shall delete the MCS indicator.

Reference:

– 3GPP TS 24.501 [42], Annex C.

5. The UE shall be able to determine whether or not a particular new access attempt is allowed based on uac‑BarringInfo broadcast in SIB1. Access Control check shall be performed as per the information received in uac‑BarringInfoSetList.

Reference:

– 3GPP TS 38.331 [44], clauses 5.3.14

5.4.7.3 Test purpose

1) To verify if the RPLMN is the HPLMN, EHPLMN or visited PLMN of the home country and the USIM file EF_{UAC_AIC}does not indicate the UE is configured for access identity 2 and the MCS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message is received, UE considers access identity as 2 for access barring.

2) To verify that the MCS indicator bit in the 5GS network feature support IE provided in the REGISTRATION ACCEPT message is valid until the UE receives a REGISTRATION ACCEPT message with the MCS indicator bit set to "Access identity 2 not valid" or until the UE selects a non-equivalent PLMN.

3) To verify the MCS indicator is stored together with a PLMN identity of the PLMN that provided it, and the MCS indicator can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME.

5.4.7.4 Method of test

5.4.7.4.1 Initial conditions

The default 5G-NR UICC is used with the following exceptions:

EF_{UAC_AIC}and EF_ACC

No Access Identity is configured in EF_{UAC_AIC}and no Access Classes are configured in EF_ACC as given in table 5.4.7-1.

EF_IMSI(IMSI)

Logically: 246081357935793

Coding:	B1	B2	B3	B4	B5	B6	B7	B8	B9
Hex	08	29	64	80	31	75	39	75	39

EF_UST (USIM Service Table)

Logically:

User controlled PLMN selector available

Fixed dialling numbers available

The GSM Access available

The Group Identifier level 1 and level 2 not available

Service n 33 (Packed Switched Domain) shall be set to ‘1’

Enabled Services Table available

EPS Mobility Management Information available

Allowed CSG Lists and corresponding indications available

5GS Mobility Management Information available

5G Security Parameters available

Subscription identifier privacy support not available

SUCI calculation by USIM not available

UAC Access Identities support

Byte:	B1	B2	B3	B4	B5	B6	B7	B8
Binary:	xxxx xx1x	xxxx xxxx	xxxx 1×00	xxxx x1xx	xxxx xx11	xxxx xxxx	xxxx xxxx	xxxx xxxx

	B9	B10	B11		B16
	xxxx xxxx	xxxx xxxx	xx11 xxxx	…..	xx10 011x

NETWORK (NG-SS)

Cell A:

Transmits on the BCCH, with the following network parameters:

– TAI (MCC/MNC/TAC): 246/081/000001

– CellIdentity: "000000001"

For Table 5.4.7-1:

After turning on the cell for the 2^nd time, uac‑BarringInfo in SIB1 should be set as in the table:

– Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the table.

Cell B:

Transmits on the BCCH, with the following network parameters:

– TAI (MCC/MNC/TAC): MCC, MNC: see table 5.4.7-1, TAC="000002".

– CellIdentity: "000000002"

For Table 5.4.7-1:

uac-BarringInfo in SIB1 should be set as in the table:

– Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the table.

5.4.7.4.2 Procedure

Steps for the Table 5.4.7-1

a) NG-SS activates Cell A without uac‑BarringInfo in SIB1, the UE is switched on (1^st time) and sends a REGISTRATION REQUEST to Cell A.

b) Cell A responds with a REGISTRATION ACCEPT message with the MCS indicator bit set to "Access identity 2 valid".

c) The UE is switched off and Cell A is turned off.

d) Turn on Cell A or B with SIB1 as specified in the table.

e) The UE is switched on again (2^nd time) with a different USIM (e.g.: IMSI set to 24681685533963) and sends a REGISTRATION REQUEST to the Cell in step d).

f) Cell A or B (as specified in the table) responds with a REGISTRATION ACCEPT message without 5GS network feature support IE.

g) Using the MMI or EMMI a MO Data call is attempted if required by the test.

h) The test is repeated for each set of values in the table.

5.4.7.4.3 Acceptance criteria

For the Table 5.4.7-1

– After step e) the UE shall make a successful or not successful Registration to the network in accordance with the result indicated in the table.

– After step g) the UE shall make a successful or not successful MO data call in accordance with the result indicated in the table.

Table 5.4.7-1

TC Seq#)	Access Category	USIM		SIB1 of Cell A or B after the 2^nd power up of the ME			REGISTRATION ACCEPT (5GS network feature support IE) on Cell A at 1^st power up of the ME		Result (after 2^nd power up)
TC Seq#)	Access Category	EF_{UAC_AIC}	EF_ACC (Byte 1 b8-b4)	Cell A or B	uac-BarringInfo	PLMN-Identity (MCC/MNC)	MPS indicator Bit	MCS indicator Bit	Registration successful?	MO Data call successful?
1.1	3	0x00 00 00 00	00000	Cell A	Not Present	246 / 081	0	1	Yes	Yes
1.2	3	0x00 00 00 00	00000	Cell A	UAC_BarringInfo_Common( 3,0×1000000’B)	246 / 081	0	1	No	NA
1.3	7	0x00 00 00 00	00000	Cell A	UAC_BarringInfo_Common( 7,0×1000000’B)	246 / 081	0	1	Yes	No
1.4	3	0x00 00 00 00	00000	Cell A	UAC_BarringInfo_Common( 3,0×0000000’B)	246 / 081	0	1	No	NA
1.5	3	0x00 00 00 00	00000	Cell B	UAC_BarringInfo_Common( 3,0×1000000’B)	246 / 082	0	1	No	NA
1.6	3	0x00 00 00 00	00000	Cell B	UAC_BarringInfo_PerPLMN( 3,0×1000000’B)	244 / 081	0	1	No	NA
1.7	7	0x00 00 00 00	00000	Cell B	UAC_BarringInfo_Common( 7,0×0000000’B)	244 / 081	0	1	Yes	No

5.4.8 Unified Access Control – Access Identities 11 and 15 indicated by USIM

5.4.8.1 Definition and applicability

The 5G network shall be able to broadcast barring control information (i.e. a list of barring parameters associated with an Access Identity and an Access Category) in SIB1.

The EF_ACCin the USIM contains the configuration information pertaining to access identities 11 and 15.

5.4.8.2 Conformance requirement

1. The Terminal shall read the access control value as part of the USIM-Terminal initialization procedure, and subsequently adopt this value.

Reference:

– 3GPP TS 31.102 [4], clause 5.1.1.2.

Reference:

– 3GPP TS 22.261 [43], clause 6.22.2.

3. Access Identity 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).

Reference:

– 3GPP TS 24.501 [42], clause 4.5.2.

Reference:

– 3GPP TS 38.331 [44], clauses 5.3.14.

Reference:

– 3GPP TS 38.331 [44], clauses 5.3.13.2.

5.4.8.3 Test purpose

1) To verify that the Terminal reads the access control value from EF_UAC-AICand EF_ACC as part of the USIM-Terminal initialisation procedure, and subsequently adopts this value.

4) To verify UE performs unified access control procedure if RNA Update procedure is triggered.

5.4.8.4 Method of test

5.4.8.4.1 Initial conditions

The default 5G-NR UICC is used with the following exceptions:

EF_{UAC_AIC}and EF_ACC

Access Identities 11 and 15 are configured in EF_ACCand no Access Identities are configured in EF_{UAC_AIC} as given in tables 5.4.8-1 and 5.4.8-2.

EF_IMSI(IMSI)

Logically: 246081357935793

Coding:	B1	B2	B3	B4	B5	B6	B7	B8	B9
Hex	08	29	64	80	31	75	39	75	39

EF_UST (USIM Service Table)

Logically:

User controlled PLMN selector available

Fixed dialling numbers available

The GSM Access available

The Group Identifier level 1 and level 2 not available

Service n 33 (Packed Switched Domain) shall be set to ‘1’

Enabled Services Table available

EPS Mobility Management Information available

Allowed CSG Lists and corresponding indications available

5GS Mobility Management Information available

5G Security Parameters available

Subscription identifier privacy support not available

SUCI calculation by USIM not available

UAC Access Identities support

Byte:	B1	B2	B3	B4	B5	B6	B7	B8
Binary:	xxxx xx1x	xxxx xxxx	xxxx 1×00	xxxx x1xx	xxxx xx11	xxxx xxxx	xxxx xxxx	xxxx xxxx
	B9	B10	B11		B16
	xxxx xxxx	xxxx xxxx	xx11 xxxx	…..	xx10 011x

NETWORK (NG-SS)

Cell A:

Transmits on the BCCH, with the following network parameters:

– TAI (MCC/MNC/TAC): MCC, MNC: see tables 5.4.8-x, TAC="000001".

– CellIdentity: "000000001"

For Table 5.4.8-1:

uac-BarringInfo in SIB1 should be set as in the table:

– Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the table.

For Table 5.4.8-2:

No uac-BarringInfo in SIB1.

Cell B:

Transmits on the BCCH, with the following network parameters:

– TAI (MCC/MNC/TAC): MCC, MNC: see table 5.4.8-2, TAC="000001".

– CellIdentity: "000000002"

For Table 5.4.8-2:

uac-BarringInfo in SIB1 should be set as in the table:

– Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the table.

5.4.8.4.2 Procedure

Steps for the Table 5.4.8-1

a) NG-SS activates Cell A and terminal is switched on and performs Registration if access is allowed according to the table.

b) Using the MMI or EMMI a MO Data call is attempted if required by the test.

c) The test is repeated for each set of values in the table.

Steps for the Table 5.4.8-2

a) NG-SS activates Cell A and terminal is switched on and performs successful Registration.

b) Using the MMI or EMMI set up a successful MO Data call.

c) NG-SS sends RRCRelease with suspendConfig in criticalExtensions (with the choice rrcRelease).

– ran-NotificationAreaInfo in suspendConfig contains the cellList with cellIdentity of Cell A

cellList {

plmn-Identity {mcc, mnc}, — see table 5.4.8-2 for mcc/mnc

ran-AreaCells 000000001’B

}

d) Deactivate Cell A and activate Cell B with uac-BarringInfo in SIB1 set as in the table:

– Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the table.

e) UE attempts to initiate RRCResumeRequest procedure with resumeCause set to rna-Update.

f) The test is repeated for each set of values in the table.

5.4.8.4.3 Acceptance criteria

For the Table 5.4.8-1

– After step a) the UE shall make a successful or not successful Registration to the network in accordance with the result indicated in the table.

– After step b) the UE shall make a successful or not successful MO Data call in accordance with the result indicated in the table if the step is applicable.

For the Table 5.4.8-2

– After step e) the UE shall make a successful or not successful RRC Resumption for RNA Update in accordance with the result indicated in the table.

Table 5.4.8-1

TC Seq#	Access Category	USIM			SIB1		Result
TC Seq#	Access Category	EF_{UAC_AIC}	EF_ACC (Byte 1 b8-b4)	Access Identies	uac-BarringInfo	PLMN-Identity (MCC/MNC)	Registration successful?	MO Data call successful?
1.1	7	0x00 00 00 00	00001	11	Not Present	246 / 081	Yes	Yes
1.2	3	0x00 00 00 00	00001	11	UAC_BarringInfo_Common( 3,0×0010000’B)	246 / 081	No	NA
1.3	3	0x00 00 00 00	00001	11	UAC_BarringInfo_PerPLMN( 3,0×0010000’B)	246 / 081	No	NA
1.4	3	0x00 00 00 00	00001	11	UAC_BarringInfo_Common( 3,0×0000000’B)	246 / 082	No	NA
1.5	3	0x00 00 00 00	00001	11	UAC_BarringInfo_Common( 3,0×0001000’B)	246 / 081	Yes	Yes
1.6	3	0x00 00 00 00	10001	11, 15	UAC_BarringInfo_Common( 3,0×0000001’B)	246 / 081	Yes	Yes
1.7	7	0x00 00 00 00	00001	11	UAC_BarringInfo_Common( 7,0×0010000’B)	246 / 081	Yes	No
1.8	7	0x00 00 00 00	00001	11	UAC_BarringInfo_Common( 7,0×0000000’B)	246 / 082	Yes	No
1.9	7	0x00 00 00 00	00001	11	UAC_BarringInfo_Common( 7,0×0000000’B)	244 / 081	Yes	No
1.10	7	0x00 00 00 00	00001	11	UAC_BarringInfo_Common2( 3,0×0001000’B, 7,0×0010000’B)	246 / 081	Yes	No
1.11	3	0x00 00 00 00	10000	15	UAC_BarringInfo_Common( 3,0×0000001’B)	246 / 081	No	NA
1.12	3	0x00 00 00 00	10000	15	UAC_BarringInfo_PerPLMN( 3,0×0000001’B)	246 / 081	No	NA
1.13	3	0x00 00 00 00	10000	15	UAC_BarringInfo_Common( 3,0×0000000’B)	246 / 082	No	NA
1.14	3	0x00 00 00 00	10000	15	UAC_BarringInfo_Common( 3,0×0010000’B)	246 / 081	Yes	Yes
1.15	7	0x00 00 00 00	10000	15	UAC_BarringInfo_Common( 7,0×0000001’B)	246 / 081	Yes	No
1.16	7	0x00 00 00 00	10000	15	UAC_BarringInfo_Common( 7,0×0000000’B)	246 / 082	Yes	No
1.17	7	0x00 00 00 00	10000	15	UAC_BarringInfo_Common( 7,0×0000000’B)	244 / 081	Yes	No
1.18	7	0x00 00 00 00	10000	15	UAC_BarringInfo_Common2( 3,0×0001000’B, 7,0×0000001’B)	246 / 081	Yes	No

Table 5.4.8-2

TC Seq#	Access Category	USIM			SIB1		Result
TC Seq#	Access Category	EF_{UAC_AIC}	EF_ACC (Byte 1 b8-b4)	Access identity	uac-BarringInfo	PLMN-Identity (MCC/MNC)	RRCResumeRequest with resumeCause set to rna-Update successful?
2.1	8	0x00 00 00 00	00001	11	Not Present	246 / 081	Yes
2.2	8	0x00 00 00 00	00001	11	UAC_BarringInfo_Common( 8,0×0010000’B)	246 / 081	No
2.3	8	0x00 00 00 00	00001	11	UAC_BarringInfo_PerPLMN( 8,0×0000000’B)	246 / 081	Yes
2.4	8	0x00 00 00 00	00001	11	UAC_BarringInfo_Common( 8,0×0000000’B)	246 / 082	No
2.5	8	0x00 00 00 00	00001	11	UAC_BarringInfo_Common2( 7,0×0000001’B, 8,0×0000000’B)	244 / 081	No
2.6	8	0x00 00 00 00	10000	15	UAC_BarringInfo_Common( 8,0×0000001’B)	246 / 081	No
2.7	8	0x00 00 00 00	10000	15	UAC_BarringInfo_PerPLMN( 8,0×0000000’B)	246 / 081	Yes
2.8	8	0x00 00 00 00	10000	15	UAC_BarringInfo_Common( 8,0×0000000’B)	246 / 082	No
2.9	8	0x00 00 00 00	10000	15	UAC_BarringInfo_Common2( 7,0×0000001’B, 8,0×0000000’B )	244 / 081	No

5.4.9 Unified Access Control – Access Identities 12, 13 and 14 indicated by USIM

5.4.9.1 Definition and applicability

The 5G network shall be able to broadcast barring control information (i.e. a list of barring parameters associated with an Access Identity and an Access Category) in SIB1.

The EF_ACCin the USIM contains the configuration information pertaining to access identities 12, 13 and 14.

5.4.9.2 Conformance requirement

1. The Terminal shall read the access control value as part of the USIM-Terminal initialization procedure, and subsequently adopt this value.

Reference:

– 3GPP TS 31.102 [4], clause 5.1.1.2.

Reference:

– 3GPP TS 22.261 [43], clause 6.22.2.

3. Access Identities 12, 13 and 14 are valid in HPLMN and visited PLMNs of home country only.

Reference:

– 3GPP TS 24.501 [42], clause 4.5.2.

Reference:

– 3GPP TS 38.331 [44], clauses 5.3.14.

Reference:

– 3GPP TS 38.331 [44], clauses 5.3.13.2.

5.4.9.3 Test purpose

1) To verify that the Terminal reads the access control value from EF_UAC-AICand EF_ACC as part of the USIM-Terminal initialisation procedure, and subsequently adopts this value.

4) To verify UE performs unified access control procedure if RNA Update procedure is triggered.

5.4.9.4 Method of test

5.4.9.4.1 Initial conditions

The default 5G-NR UICC is used with the following exceptions:

EF_{UAC_AIC}and EF_ACC

Access Identities 12, 13 and 14 are configured in EF_ACCand no Access Identities are configured in EF_{UAC_AIC} as given in tables 5.4.9-1 and 5.4.9-2.

EF_IMSI(IMSI)

Logically: 246081357935793

Coding:	B1	B2	B3	B4	B5	B6	B7	B8	B9
Hex	08	29	64	80	31	75	39	75	39

EF_UST (USIM Service Table)

Logically:

User controlled PLMN selector available

Fixed dialling numbers available

The GSM Access available

The Group Identifier level 1 and level 2 not available

Service n 33 (Packed Switched Domain) shall be set to ‘1’

Enabled Services Table available

EPS Mobility Management Information available

Allowed CSG Lists and corresponding indications available

5GS Mobility Management Information available

5G Security Parameters available

Subscription identifier privacy support not available

SUCI calculation by USIM not available

UAC Access Identities support

Byte:	B1	B2	B3	B4	B5	B6	B7	B8
Binary:	xxxx xx1x	xxxx xxxx	xxxx 1×00	xxxx x1xx	xxxx xx11	xxxx xxxx	xxxx xxxx	xxxx xxxx
	B9	B10	B11		B16
	xxxx xxxx	xxxx xxxx	xx11 xxxx	…..	xx10 011x

NETWORK (NG-SS)

Cell A:

Transmits on the BCCH, with the following network parameters:

– TAI (MCC/MNC/TAC): MCC, MNC: see tables 5.4.9-x, TAC="000001".

– CellIdentity : "000000001"

For Table 5.4.9-1:

uac-BarringInfo in SIB1 should be set as in the table:

– Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the table.

For Table 5.4.9-2:

No uac-BarringInfo in SIB1.

Cell B:

Transmits on the BCCH, with the following network parameters:

– TAI (MCC/MNC/TAC): MCC, MNC: see table 5.4.9-2, TAC="000001".

– CellIdentity: "000000002"

For Table 5.4.9-2:

uac-BarringInfo in SIB1 should be set as in the table:

– Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the table.

5.4.9.4.2 Procedure

Steps for the Table 5.4.9-1

a) NG-SS activates Cell A and terminal is switched on and performs Registration if access is allowed according to the table.

b) Using the MMI or EMMI a MO Data call is attempted if required by the test.

c) The test is repeated for each set of values in the table.

Steps for the Table 5.4.9-2

a) NG-SS activates Cell A and terminal is switched on and performs successful Registration.

b) Using the MMI or EMMI set up a successful MO Data call.

c) NG-SS sends RRCRelease with suspendConfig in criticalExtensions (with the choice rrcRelease).

– ran-NotificationAreaInfo in suspendConfig contains the cellList with cellIdentity of Cell A

cellList {

plmn-Identity {mcc, mnc}, — see table 5.4.9-2 for mcc/mnc

ran-AreaCells 000000001’B

}

d) Deactivate Cell A and activate Cell B with uac-BarringInfo in SIB1 set as in the table:

– Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the table.

e) UE attempts to initiate RRCResumeRequest procedure with resumeCause set to rna-Update.

f) The test is repeated for each set of values in the table.

5.4.9.4.3 Acceptance criteria

For the Table 5.4.9-1

– After step a) the UE shall make a successful or not successful Registration to the network in accordance with the result indicated in the table.

– After step b) the UE shall make a successful or not successful MO Data call in accordance with the result indicated in the table if the step is applicable.

For the Table 5.4.9-2

– After step e) the UE shall make a successful or not successful RRC Resumption for RNA Update in accordance with the result indicated in the table.

Table 5.4.9-1

TC Seq#	Access Category	USIM			SIB1		Result
TC Seq#	Access Category	EF_{UAC_AIC}	EF_ACC (Byte 1 b8-b4)	Access Identity	uac-BarringInfo	PLMN-Identity (MCC/MNC)	Registration successful?	MO Data call successful?
1.1	7	0x00 00 00 00	00010	12	Not Present	246 / 081	Yes	Yes
1.2	3	0x00 00 00 00	00010	12	UAC_BarringInfo_Common( 3,0×0001000’B)	246 / 081	No	NA
1.3	3	0x00 00 00 00	00010	12	UAC_BarringInfo_PerPLMN( 3,0×0001000’B)	246 / 081	No	NA
1.4	3	0x00 00 00 00	00010	12	UAC_BarringInfo_Common( 3,0×0000000’B)	246 / 082	Yes	Yes
1.5	3	0x00 00 00 00	00010	12	UAC_BarringInfo_Common( 3,0×0001000’B)	246 / 082	No	NA
1.6	3	0x00 00 00 00	00010	12	UAC_BarringInfo_Common( 3,0×0000000’B)	244 / 081	No	NA
1.7	3	0x00 00 00 00	00010	12	UAC_BarringInfo_Common( 3,0×0000100’B)	246 / 081	Yes	Yes
1.8	3	0x00 00 00 00	01110	12,13,14	UAC_BarringInfo_Common( 3,0×0000110’B)	246 / 081	Yes	Yes
1.9	7	0x00 00 00 00	00010	12	UAC_BarringInfo_Common( 7,0×0001000’B)	246 / 081	Yes	No
1.10	7	0x00 00 00 00	00010	12	UAC_BarringInfo_Common( 7,0×0000000’B)	246 / 082	Yes	Yes
1.11	7	0x00 00 00 00	00010	12	UAC_BarringInfo_Common( 7,0×0000000’B)	244 / 081	Yes	No
1.12	7	0x00 00 00 00	00010	12	UAC_BarringInfo_Common2 ( 3,0×0000100’B, 7,0×0001000’B )	246 / 081	Yes	No
1.13	3	0x00 00 00 00	00100	13	UAC_BarringInfo_Common( 3,0×0000100’B)	246 / 081	No	NA
1.14	3	0x00 00 00 00	00100	13	UAC_BarringInfo_PerPLMN( 3,0×0000100’B)	246 / 081	No	NA
1.15	3	0x00 00 00 00	00100	13	UAC_BarringInfo_Common( 3,0×0000000’B)	246 / 082	Yes	Yes
1.16	3	0x00 00 00 00	00100	13	UAC_BarringInfo_Common( 3,0×0000100’B)	246 / 082	No	NA
1.17	3	0x00 00 00 00	00100	13	UAC_BarringInfo_Common( 3,0×0000010’B)	246 / 082	Yes	Yes
1.18	7	0x00 00 00 00	00100	13	UAC_BarringInfo_Common( 7,0×0000100’B)	246 / 081	Yes	No
1.19	7	0x00 00 00 00	00100	13	UAC_BarringInfo_Common( 7,0×0000000’B)	244 / 081	Yes	No
1.20	7	0x00 00 00 00	00100	13	UAC_BarringInfo_Common2( 3,0×0000010’B, 7,0×0000100’B)	246 / 081	Yes	No
1.21	3	0x00 00 00 00	01000	14	UAC_BarringInfo_Common( 3,0×0000010’B)	246 / 081	No	NA
1.22	3	0x00 00 00 00	01000	14	UAC_BarringInfo_PerPLMN( 3,0×0000010’B)	246 / 081	No	NA
1.23	3	0x00 00 00 00	01000	14	UAC_BarringInfo_Common( 3,0×0000000’B)	246 / 082	Yes	Yes
1.24	3	0x00 00 00 00	01000	14	UAC_BarringInfo_Common( 3,0×0000010’B)	246 / 082	No	NA
1.25	3	0x00 00 00 00	01000	14	UAC_BarringInfo_Common( 3,0×0001100’B)	246 / 082	Yes	Yes
1.26	7	0x00 00 00 00	01000	14	UAC_BarringInfo_Common( 7,0×0000010’B)	246 / 081	Yes	No
1.27	7	0x00 00 00 00	01000	14	UAC_BarringInfo_Common( 7,0×0000000’B)	244 / 081	Yes	No
1.28	7	0x00 00 00 00	01000	14	UAC_BarringInfo_Common2( 3,0×0000100’B, 7,0×0000010’B)	246 / 081	Yes	No

Table 5.4.9-2

TC Seq#	Access Category	USIM			SIB1		Result
TC Seq#	Access Category	EF_{UAC_AIC}	EF_ACC (Byte 1 b8-b4)	Access Identity	uac-BarringInfo	PLMN-Identity (MCC/MNC)	RRCResumeRequest with resumeCause set to rna-Update successful?
2.1	8	0x00 00 00 00	00010	12	Not Present	246 / 081	Yes
2.2	8	0x00 00 00 00	00010	12	UAC_BarringInfo_Common( 8,0×0001000’B)	246 / 081	No
2.3	8	0x00 00 00 00	00010	12	UAC_BarringInfo_PerPLMN( 8,0×0000000’B)	246 / 081	Yes
2.4	8	0x00 00 00 00	00010	12	UAC_BarringInfo_Common( 8,0×0010000’B)	246 / 082	Yes
2.5	8	0x00 00 00 00	00010	12	UAC_BarringInfo_Common2 ( 7,0×0010000’B, 8,0×0000000’B)	244 / 081	No
2.6	8	0x00 00 00 00	00100	13	UAC_BarringInfo_Common( 8,0×0000100’B)	246 / 081	No
2.7	8	0x00 00 00 00	00100	13	UAC_BarringInfo_PerPLMN( 8,0×0000000’B)	246 / 081	Yes
2.8	8	0x00 00 00 00	00100	13	UAC_BarringInfo_Common( 8,0×0000100’B)	246 / 082	No
2.9	8	0x00 00 00 00	00100	13	UAC_BarringInfo_Common2 ( 7,0×0001000’B, 8,0×0000000’B)	244 / 081	No
2.10	8	0x00 00 00 00	01000	14	UAC_BarringInfo_Common( 8,0×0000010’B)	246 / 081	No
2.11	8	0x00 00 00 00	01000	14	UAC_BarringInfo_PerPLMN( 8,0×0000000’B)	246 / 081	Yes
2.12	8	0x00 00 00 00	01000	14	UAC_BarringInfo_Common( 8,0×0000010’B)	246 / 082	No
2.13	8	0x00 00 00 00	01000	14	UAC_BarringInfo_Common2 ( 7,0×0000100’B, 8,0×0000000’B)	244 / 081	No

5.4.10 Unified Access Control – Operator-Defined Access Category

5.4.10.1 Definition and applicability

The 5G network shall be able to broadcast barring control information a list of barring parameters associated with an Access Identity and an Access Category in SIB1. Access category numbers in the 32-63 range are used for operator-defined Access Categories.

The EF_{UAC_AIC}in the USIM contains the configuration information pertaining to access identities allocated for high priority services that can be used by the subscriber.

Operator-defined access category definitions can be signaled to the UE using NAS signaling. Each operator-defined access category definition consists of the parameters a precedence value, an operator-defined access category number, one or more access category criteria type and optionally, a standardized access category.

When the UE needs to initiate an access attempt that triggers access barring check, the UE shall determine one or more access identities from the set of standardized access identities, and one access category from the set of standardized access categories and operator-defined access categories, to be associated with that access attempt.

In order to determine the access category applicable for the access attempt, the NAS shall check the Access category mapping rules, and use the access category of the lowest rule number for which there is a match for barring check. In the case of operator-defined access categories, the UE shall select the access category from the operator-defined access category definition with the lowest precedence value.

5.4.10.2 Conformance requirement

1. The Terminal shall read the access control value as part of the USIM initialization procedure, and subsequently adopt this value.

Reference:

– 3GPP TS 31.102 [4], clause 5.1.1.2.

2. Access Identities are configured at the UE as listed in Table 6.22.2.2-1. Access Categories are defined by the combination of conditions related to UE and the type of access attempt as listed in Table 6.22.2.3-1.

Reference:

– 3GPP TS 22.261 [43], clause 6.22.2

3. Operator may provide one or more PLMN-specific Operator-defined access category definitions to the UE using NAS signaling (Operator-defined access category definitions information element), and the UE handles the Operator-defined access category definitions stored for the Registered PLMN, as specified in TS 24.501.

References:

– 3GPP TS 23.501 [49], clause 5.2.5

– 3GPP TS 24.501 [42] clause 9.11.3.38

4. When the UE needs to initiate an access attempt in one of the events listed in clause 4.5.1, the UE shall determine one or more access identities from the set of standardized access identities, and one access category from the set of standardized access categories and operator-defined access categories, to be associated with that access attempt.

Reference:

– 3GPP TS 24.501 [42], clause 4.5.2

5. An access attempt matches the criteria of an operator-defined access category definition, if the access attempt matches all access category criteria types included in the criteria with any of the associated access criteria type values.

Reference:

– 3GPP TS 24.501 [42], clause 4.5.3

6. In order to determine the access category applicable for the access attempt, the NAS shall check the rules in table 4.5.2.2, and use the access category for which there is a match for barring check. If the access attempt matches more than one rule, the access category of the lowest rule number shall be selected. If the access attempt matches more than one operator-defined access category definition, the UE shall select the access category from the operator-defined access category definition with the lowest precedence value (see clause 4.5.3).

Reference:

– 3GPP TS 24.501 [42], clause 4.5.2

7. If the UE receives Operator-defined access category definitions IE in the REGISTRATION ACCEPT message and the Operator-defined access category definitions IE contains one or more operator-defined access category definitions, the UE shall delete any operator-defined access category definitions stored for the RPLMN and shall store the received operator-defined access category definitions for the RPLMN. If the UE receives the Operator-defined access category definitions IE in the REGISTRATION ACCEPT message and the Operator-defined access category definitions IE contains no operator-defined access category definitions, the UE shall delete any operator-defined access category definitions stored for the RPLMN. If the REGISTRATION ACCEPT message does not contain the Operator-defined access category definitions IE, the UE shall not delete the operator-defined access category definitions stored for the RPLMN.

Reference:

– 3GPP TS 24.501 [42], clause 5.5.1.2.4

8. The UE shall be able to determine whether or not a particular new access attempt is allowed based on uac-BarringInfo broadcast in SIB1. Access Control check shall be performed as per the information received in uac-BarringInfoSetList.

Reference:

– 3GPP TS 38.331 [44], clauses 5.3.14

5.4.10.3 Test purpose

1) To verify that the Terminal reads the access control value from EF_{UAC_AIC}and EF_ACC as part of the USIM initialisation procedure, and subsequently adopts this value.

2) To verify if UE uses operator-defined access categories received within Operator-defined access category definitions information element in the REGISTRATION ACCEPT.

3) To verify the UE checks the access category applicable for the access attempt, as per the Access category mapping rules and chooses the matching lowest rule.

4) To verify the UE checks operator-defined access category parameters precedence value, operator-defined access category number and access category criteria type associated with the Operator-defined Access Category when determining the Access Category for the access attempt.

5) To verify UE stops using the operator-defined access category definitions stored for the previously selected PLMN.

6) To verify UE maps the kind of request to one or more access identities and one access category and lower layers performs access barring checks for that request based on the determined access identities and access category.

7) To verify the UE determines whether or not a particular access attempt is allowed based on uac-BarringInfo broadcast in SIB1 and if the RPLMN is the HPLMN, EHPLMN or visited PLMN of the home country.

5.4.10.4 Method of test

5.4.10.4.1 Initial conditions

The default 5G-NR UICC is used with the following exceptions:

EF_{UAC_AIC}and EF_ACC

Access Identities are configured in EF_{UAC_AIC}and Access Classes are configured in EF_ACC as given in Table 5.4.10-1.

EF_IMSI(IMSI)

Logically: 246081357935793

Coding:	B1	B2	B3	B4	B5	B6	B7	B8	B9
Hex	08	29	64	80	31	75	39	75	39

EF_UST (USIM Service Table)

Logically:

User controlled PLMN selector available

Fixed dialling numbers available

The GSM Access available

The Group Identifier level 1 and level 2 not available

Service n 33 (Packed Switched Domain) shall be set to ‘1’

Enabled Services Table available

EPS Mobility Management Information available

Allowed CSG Lists and corresponding indications available

5GS Mobility Management Information available

5G Security Parameters available

Subscription identifier privacy support not available

SUCI calculation by USIM not available

UAC Access Identities support available

Support for URSP by USIM not available

Coding:

Byte:	B1	B2	B3	B4	B5	B6	B7	B8
Binary:	xxxx xx1x	xxxx xxxx	xxxx 1×00	xxxx x1xx	xxxx xx11	xxxx xxxx	xxxx xxxx	xxxx xxxx
	B9	B10	B11		B16	B17
	xxxx xxxx	xxxx xxxx	xx11 xxxx	…..	xx10 011x	xxxx 0xxx

ME shall be configured with following URSP rules:

Rule Precedence = 1

Traffic Descriptor:

DNN=TestGp.rs1

Route Selection Descriptor:

Precedence = 1

Network Slice Selection, S-NSSAI: ′01 01 01 01′ (ST: MBB, SD: ′010101′)

SSC Mode Selection: SSC Mode 1

Access Type preference: 3GPP access

Rule Precedence = 2

Traffic Descriptor:

DNN = TestGp.rs2

Route Selection Descriptor:

Precedence = 1

Network Slice Selection, S-NSSAI: ′01 01 01 02′ (ST: MBB, SD: ′010102′)

SSC Mode Selection: SSC Mode 1

Rule Precedence = 3

Traffic Descriptor:

DNN = TestGp.rs3

Route Selection Descriptor:

Precedence = 1

Network Slice Selection, S-NSSAI: ′01 01 01 02′ (ST: MBB, SD: ′010102′)

SSC Mode Selection: SSC Mode 1

NETWORK (NG-SS)

Cell A:

Transmits on the BCCH, with the following network parameters:

– MCC, MNC: 246/081

– TAC: "000001".

– CellIdentity: "000000001"

For Table 5.4.10-1:

After turning on the cell for the 2^nd time, uac‑BarringInfo in SIB1 should be set as in the table:

– Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the table.

REGISTRATION ACCEPT IEIs.

– Operator-Defined Access Category Definitions IEI is configured as defined in Table 5.4.10-1

– Refer to Annex A tables A4-A5 for Methods ODAC_definitions1() and ODAC_definitions2().

– For HPLMN Cells:Allowed S-NSSAI IEI is configured to include S-NSSAIs ′01 01 01 01′, ′01 01 01 02′ and ′01 01 01 03′.

For VPLMN Cells:

– Allowed S-NSSAI IEI is configured to include S-NSSAIs (’01 01 01 01’, ’01 01 01 01’), (’01 01 01 02’, ’01 01 01 02’), and (’01 01 01 03’, ’01 01 01 03’).

5.4.10.4.2 Procedure

Steps for the Table 5.4.10-1

a) NG-SS activates Cell A with uac‑BarringInfo in SIB1 as in the table, the ME is switched on with the UICC and sends a REGISTRATION REQUEST to Cell A.

b) Cell A responds with a REGISTRATION ACCEPT message with the Operator-Defined Access Category Definitions IEI as defined in the Table.

c) Attempt 1^st MO Data call to DNN TestGp.rs1/S-NSSAI ’01 01 01 01′ using the MMI or EMMI.

d) For sequences 1.1 – 1.14:

Attempt 2^nd MO Data call to DNN TestGp.rs2/S-NSSAI ’01 01 01 02′ using the MMI or EMMI.

For sequences 1.15 – 1.17:

Attempt 2^nd MO Data call to DNN TestGp.rs3/S-NSSAI ’01 01 01 02′ using the MMI or EMMI

e) The test is repeated for each set of values in the table.

5.4.10.5 Acceptance criteria

For the Table 5.4.10-1

– The UE shall make a successful or not successful 1^st MO data call in accordance with the result indicated in the table.

– The UE shall make a successful or not successful 2^nd MO data call in accordance with the result indicated in the table.

able 5.4.10-1

TC Seq#	Access Category for Call 1&2	USIM		SIB1 of Cell A		REGISTRATION ACCEPT	Result
TC Seq#	Access Category for Call 1&2	EF_{UAC_AIC}	EF_ACC (Byte 1 b8-b4)	uac-BarringInfo	PLMN-Identity (MCC/MNC)	(Operator-defined access category definitions IE)	MO Data call 1 successful?	MO Data call 2 successful?
1.1	32,7	0x00 00 00 00	00000	Not Present	246 / 081	ODAC_definitions1(0)	Yes	Yes
1.2	32,7	0x00 00 00 00	00000	UAC_BarringInfo_Common ( 32,0×0000000’B)	246 / 081	ODAC_definitions1(0)	No	Yes
1.3	50,7	0x00 00 00 00	00000	UAC_BarringInfo_Common ( 50,0×0100000’B)	246 / 081	ODAC_definitions1(18)	No	Yes
1.4	63,7	0x01 00 00 00	00000	UAC_BarringInfo_Common ( 7,0×1000000’B)	246 / 082	ODAC_definitions1(31)	Yes	No
1.5	63,7	0x02 00 00 00	00000	UAC_BarringInfo_Common ( 63,0×0100000’B)	246 / 081	ODAC_definitions1(31)	No	Yes
1.6	48,7	0x01 00 00 00	00000	UAC_BarringInfo_Common2 ( 7,0×1000000’B, 48,0×1000000’B)	246 / 082	ODAC_definitions1(16)	No	No
1.7	48,7	0x02 00 00 00	00000	UAC_BarringInfo_Common ( 48,0×1000000’B)	246 / 082	ODAC_definitions1(16)	Yes	Yes
1.8	50,7	0x02 00 00 00	00000	UAC_BarringInfo_PerPLMN ( 50,0×1100000’B)	244 / 081	ODAC_definitions1(18)	No	Yes
1.9	50,7	0x00 00 00 00	00001	UAC_BarringInfo_Common ( 50,0×0001000’B)	244 / 081	ODAC_definitions1(18)	No	Yes
1.10	33,7	0x02 00 00 00	00000	UAC_BarringInfo_Common2 ( 33,0×0100000’B, 7,0×1000000’B)	246 / 082	ODAC_definitions1(1)	No	Yes
1.11	34,7	0x01 00 00 00	00000	UAC_BarringInfo_Common2 ( 7,0×1000000’B, 34,0×0100000’B)	246 / 082	ODAC_definitions1(2)	Yes	No
1.12	7,34	0x01 00 00 00	00000	UAC_BarringInfo_Common2 ( 32,0×1000000’B, 34,0×0100000’B)	246 / 081	ODAC_definitions2(2,0)	Yes	Yes
1.13	7,32	0x00 00 00 00	01000	UAC_BarringInfo_Common2 ( 32,0×0000000’B, 34,0×0000010’B)	246 / 082	ODAC_definitions2(0,2)	Yes	Yes
1.14	7,48	0x00 00 00 00	00100	UAC_BarringInfo_Common2 ( 48,0×0100000’B, 7,0×0000100’B)	246 / 082	ODAC_definitions2(16,31)	No	Yes
1.15	7,32	0x01 00 00 00	00000	UAC_BarringInfo_Common2 ( 32,0×1000000’B, 34,0×0100000’B)	246 / 081	ODAC_definitions2(2,0)	Yes	No
1.16	7,34	0x00 00 00 00	01000	UAC_BarringInfo_Common2 ( 32,0×0000000’B, 34,0×0000010’B)	246 / 082	ODAC_definitions2(0,2)	Yes	No
1.17	7,63	0x00 00 00 00	00100	UAC_BarringInfo_Common2 ( 48,0×0100000’B, 7,0×0000100’B)	246 / 082	ODAC_definitions2(16,31)	No	Yes

5.4.11 Unified Access Control – Operator-Defined Access Categories, no change in SUPI

5.4.11.1 Definition and applicability

The EF_UAC-AICin the USIM contains the configuration information pertaining to access identities allocated for high priority services that can be used by the subscriber.

Operator-defined access category definitions can be signalled to the UE using NAS signalling. Each operator-defined access category definition consists of the parameters: a precedence value, an operator-defined access category number, one or more access category criteria type and optionally, a standardized access category.

Operator-defined access category definitions are stored together with a PLMN identity of the PLMN that provided them, and is valid in that PLMN or equivalent PLMN. The operator-defined access category definitions can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME, else the UE shall delete the operator-defined access category definitions.

5.4.11.2 Conformance requirement

1. The Terminal shall read the access control value as part of the USIM initialization procedure, and subsequently adopt this value.

Reference:

– 3GPP TS 31.102 [4], clause 5.1.1.2.

Reference:

– 3GPP TS 22.261 [43], clause 6.22.2

3. Operator may provide one or more PLMN-specific Operator-defined access category definitions to the UE using NAS signalling (Operator-defined access category definitions information element), and the UE handles the Operator-defined access category definitions stored for the Registered PLMN, as specified in 3GPP TS 24.501.

References:

– 3GPP TS 23.501 [49], clause 5.2.5

– 3GPP TS 24.501 [42] clause 9.11.3.38

4. Operator-defined access category definitions are stored together with a PLMN identity of the PLMN that provided them, and is valid in that PLMN or equivalent PLMN. The operator-defined access category definitions can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME, else the UE shall delete the operator-defined access category definitions.

Reference:

– 3GPP TS 24.501 [42], Annex C

5. In order to determine the access category applicable for the access attempt, the NAS shall check the rules in 3GPP TS 24.501 [42] Table 4.5.2.2, and use the access category for which there is a match for barring check. If the access attempt matches more than one rule, the access category of the lowest rule number shall be selected. If the access attempt matches more than one operator-defined access category definition, the UE shall select the access category from the operator-defined access category definition with the lowest precedence value (see 3GPP TS 24.501 [42] clause 4.5.3).

Reference:

– 3GPP TS 24.501 [42], clause 4.5.2

6. If the UE receives Operator-defined access category definitions IE in the REGISTRATION ACCEPT message and the Operator-defined access category definitions IE contains one or more operator-defined access category definitions, the UE shall delete any operator-defined access category definitions stored for the RPLMN and shall store the received operator-defined access category definitions for the RPLMN. If the UE receives the Operator-defined access category definitions IE in the REGISTRATION ACCEPT message and the Operator-defined access category definitions IE contains no operator-defined access category definitions, the UE shall delete any operator-defined access category definitions stored for the RPLMN. If the REGISTRATION ACCEPT message does not contain the Operator-defined access category definitions IE, the UE shall not delete the operator-defined access category definitions stored for the RPLMN.

Reference:

– 3GPP TS 24.501 [42], clause 5.5.1.2.4

7. The UE shall be able to determine whether or not a particular new access attempt is allowed based on uac-BarringInfo broadcast in SIB1. Access Control check shall be performed as per the information received in uac-BarringInfoSetList.

Reference:

– 3GPP TS 38.331 [44], clauses 5.3.14

5.4.11.3 Test purpose

1) To verify that the Terminal reads the access control value from EF_UAC-AICand EF_ACC as part of the USIM-Terminal initialisation procedure, and subsequently adopts this value.

2) To verify if UE uses operator-defined access categories received within Operator-defined access category definitions information element in the REGISTRATION ACCEPT.

3) To verify the UE checks the access category applicable for the access attempt, as per the Access category mapping rules and chooses the matching lowest rule.

5) To verify the Operator-defined access category definitions are stored together with a PLMN identity of the PLMN that provided them, and is valid in that PLMN or equivalent PLMN.

6) To verify the Operator-defined access category definitions can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME, else the UE shall delete the operator-defined access category definitions.

7) To verify UE maps the kind of request to one or more access identities and one access category and lower layers performs access barring checks for that request based on the determined access identities and access category.

8) To verify the UE determines whether or not a particular access attempt is allowed based on uac-BarringInfo broadcast in SIB1 and if the RPLMN is the HPLMN, EHPLMN or visited PLMN of the home country.

5.4.11.4 Method of test

5.4.11.4.1 Initial conditions

The default 5G-NR UICC is used with the following exceptions:

EF_{UAC_AIC}and EF_ACC

Access Identity is configured in EF_{UAC_AIC}and no Access Classes are configured in EF_ACC as given in Table 5.4.11-1.

EF_IMSI(IMSI)

Logically: 246081357935793

Coding:	B1	B2	B3	B4	B5	B6	B7	B8	B9
Hex	08	29	64	80	31	75	39	75	39

EF_UST (USIM Service Table)

Logically:

User controlled PLMN selector available

Fixed dialling numbers available

The GSM Access available

The Group Identifier level 1 and level 2 not available

Service n 33 (Packed Switched Domain) shall be set to ‘1’

Enabled Services Table available

EPS Mobility Management Information available

Allowed CSG Lists and corresponding indications available

5GS Mobility Management Information available

5G Security Parameters available

Subscription identifier privacy support not available

SUCI calculation by USIM not available

UAC Access Identities support available

Support for URSP by USIM not available

Byte:	B1	B2	B3	B4	B5	B6	B7	B8
Binary:	xxxx xx1x	xxxx xxxx	xxxx 1×00	xxxx x1xx	xxxx xx11	xxxx xxxx	xxxx xxxx	xxxx xxxx
	B9	B10	B11		B16	B17
	xxxx xxxx	xxxx xxxx	xx11 xxxx	…..	xx10 011x	xxxx 0xxx

ME shall be configured with following URSP rules.

Rule Precedence =1

Traffic Descriptor:

DNN=TestGp.rs1

Route Selection Descriptor:

Precedence=1

Network Slice Selection, S-NSSAI: ’01 01 01 01’ (ST: MBB, SD: ‘010101’)

SSC Mode Selection: SSC Mode 1

Access Type preference: 3GPP access

Rule Precedence = 2

Traffic Descriptor:

DNN=TestGp.rs2

Route Selection Descriptor:

Precedence =1

Network Slice Selection, S-NSSAI: 01 01 01 02 (ST: MBB, SD: 010102)

SSC Mode Selection: SSC Mode 1

NETWORK (NG-SS)

Cell A:

Transmits on the BCCH, with the following network parameters:

– MCC, MNC: 246/081

– TAC: "000001"

– CellIdentity: "000000001"

For Table 5.4.11-1:

uac‑BarringInfo in SIB1 should be set as in the table:

– Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the tables A1-A3.

Cell B:

NOTE: This cell is not required for the sequences in Table 5.4.11-1.

Transmits on the BCCH, with the following network parameters:

– TAI (MCC/MNC/TAC): MCC, MNC: see Table 5.4.11-1, TAC="000002".

– CellIdentity: "000000002"

For Table 5.4.11-1:

uac-BarringInfo in SIB1 should be set as in the table:

– Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the tables A1-A3.

REGISTRATION ACCEPT IEIs.

– Operator-Defined Access Category Definitions IEI is configured as defined in Table 5.4.11-1.

– Refer to Annex A tables A4-A5 for Methods ODAC_definitions1() and ODAC_definitions2()

For HPLMN Cells:

– Allowed S-NSSAI IEI is configured to include S-NSSAIs ’01 01 01 01’, ’01 01 01 02’and ’01 01 01 03’.

For VPLMN Cells:

– Allowed S-NSSAI IEI is configured to include S-NSSAIs (’01 01 01 01’, ’01 01 01 01’), (’01 01 01 02’, ’01 01 01 02’), and (’01 01 01 03’, ’01 01 01 03’).

5.4.11.4.2 Procedure

For the Table 5.4.11-1

a) NG-SS activates Cell A with uac‑BarringInfo in SIB1 as in the table, the ME is switched on with the UICC and sends the 1^st REGISTRATION REQUEST to Cell A.

b) Cell A responds with a REGISTRATION ACCEPT message with the Operator-Defined Access Category Definitions IEI as defined in the Table.

If the Cell 2 in the table is Cell A,

c) Remove the UICC.

d) Reinsert the same UICC.

e) ME sends the 2^nd REGISTRATION REQUEST to Cell A and NG-SS sends the 2^nd REGISTRATION ACCEPT.

If the Cell 2 in the table is Cell B,

c) Remove the UICC and deactivate the Cell A.

d) Re-insert the same UICC and activate Cell B.

e) ME sends the 2^nd REGISTRATION REQUEST to Cell B and NG-SS sends the 2^nd REGISTRATION ACCEPT.

f) Attempt 1^st MO Data call to DNN TestGp.rs1/S-NSSAI ’01 01 01 01′ using the MMI or EMMI.

g) Attempt 2^nd MO Data call to DNN TestGp.rs2/S-NSSAI ’01 01 01 02′ using the MMI or EMMI.

5.4.11.4.3 Acceptance criteria

For the Table 5.4.11-1

– The UE shall make a successful or not successful 1^st MO data call in accordance with the result indicated in the table.

– The UE shall make a successful or not successful 2^nd MO data call in accordance with the result indicated in the table.

Table 5.4.11-1

TC Seq#	Access Category for Call 1&2	USIM		Cell 2		SIB 1: uac-BarringInfo (for all the Cells)	Operator-defined access category definitions IEI in	Result
TC Seq#	Access Category for Call 1&2	EF_{UAC_AIC}	EF_ACC (Byte 1 b8-b4)	Cell Id of	PLMN-Identity (MCC/MNC)	SIB 1: uac-BarringInfo (for all the Cells)	1^st :REGISTRATION ACCEPT 2^nd :REGISTRATION ACCEPT	MO Data call 1 successful?	MO Data call 2 successful?
1.1	7,33	0x00 00 00 00	00000	Cell A	246 / 081	Not Present	ODAC_definitions1(0) ODAC_definitions2(1,16)	Yes	Yes
1.2	7,33	0x00 00 00 00	00000	Cell A	246 / 081	UAC_BarringInfo_Common( 33,0×0000000’B)	ODAC_definitions1(0) ODAC_definitions2(1,16)	Yes	No
1.3	34,7	0x01 00 00 00	00000	Cell A	246 / 081	UAC_BarringInfo_Common2 ( 34,0×1000000’B, 50,0×1000000’B )	ODAC_definitions2(18,1) ODAC_definitions1(2)	No	Yes
1.4	7,63	0x01 00 00 00	00000	Cell B	244 / 081	UAC_BarringInfo_Common2 ( 63,0×0000000’B, 7,0×0100000’B )	ODAC_definitions1(3) ODAC_definitions2(31,18)	No	No
1.5	63,7	0x02 00 00 00	00000	Cell A	246 / 081	UAC_BarringInfo_Common( 63,0×0100000’B)	ODAC_definitions1(31) ODAC – Not present	No	Yes
1.6	7,7	0x00 00 00 00	10000	Cell B	246 / 082	UAC_BarringInfo_Common( 48,0×0010000’B)	ODAC_definitions1(16) ODAC – Not present	Yes	Yes
1.7	7,7	0x00 00 00 00	00100	Cell B	246 / 082	UAC_BarringInfo_Common2 ( 32,0×0000100’B, 34,0×0000100’B )	ODAC_definitions2(0,2) ODAC – Empty	Yes	Yes

5.4.12 Unified Access Control – Operator-Defined Access Categories, SUPI change

5.4.12.1 Definition and applicability

The EF_UAC-AICin the USIM contains the configuration information pertaining to access identities allocated for high priority services that can be used by the subscriber.

5.4.12.2 Conformance requirement

1. The Terminal shall read the access control value as part of the USIM initialization procedure, and subsequently adopt this value.

Reference:

– 3GPP TS 31.102 [4], clause 5.1.1.2.

Reference:

– 3GPP TS 22.261 [43], clause 6.22.2

References:

– 3GPP TS 23.501 [49], clause 5.2.5

– 3GPP TS 24.501 [42] clause 9.11.3.38

Reference:

– 3GPP TS 24.501 [42], Annex C

Reference:

– 3GPP TS 24.501 [42], clause 4.5.2

Reference:

– 3GPP TS 24.501 [42], clause 5.5.1.2.4

Reference:

– 3GPP TS 38.331 [44], clauses 5.3.14

5.4.12.3 Test purpose

1) To verify that the Terminal reads the access control value from EF_UAC-AICand EF_ACC as part of the USIM-Terminal initialisation procedure, and subsequently adopts this value.

2) To verify if UE uses operator-defined access categories received within Operator-defined access category definitions information element in the REGISTRATION ACCEPT.

3) To verify the UE checks the access category applicable for the access attempt, as per the Access category mapping rules and chooses the matching lowest rule.

5) To verify the Operator-defined access category definitions are stored together with a PLMN identity of the PLMN that provided them, and is valid in that PLMN or equivalent PLMN.

5.4.12.4 Method of test

5.4.12.4.1 Initial conditions

Both UICC 1 and UICC 2 are configured as the default 5G-NR UICC with the following exceptions:

EF_IMSI(IMSI)

UICC 1:

Logically: 246081357935793

Coding:	B1	B2	B3	B4	B5	B6	B7	B8	B9
Hex	08	29	64	80	31	75	39	75	39

UICC 2:

Logically: 246081357935799

Coding:	B1	B2	B3	B4	B5	B6	B7	B8	B9
Hex	08	29	64	80	31	75	39	75	99

EF_{UAC_AIC}and EF_ACC

Access Identity is configured in _{EFUAC_AIC} and no Access Classes are configured in EF_ACC as given in Table 5.4.12-1.

EF_UST (USIM Service Table)

Logically:

User controlled PLMN selector available

Fixed dialling numbers available

The GSM Access available

The Group Identifier level 1 and level 2 not available

Service n 33 (Packed Switched Domain) shall be set to ‘1’

Enabled Services Table available

EPS Mobility Management Information available

Allowed CSG Lists and corresponding indications available

5GS Mobility Management Information available

5G Security Parameters available

Subscription identifier privacy support not available

SUCI calculation by USIM not available

UAC Access Identities support available

Support for URSP by USIM not available

Byte:	B1	B2	B3	B4	B5	B6	B7	B8
Binary:	xxxx xx1x	xxxx xxxx	xxxx 1×00	xxxx x1xx	xxxx xx11	xxxx xxxx	xxxx xxxx	xxxx xxxx
	B9	B10	B11		B16	B17
	xxxx xxxx	xxxx xxxx	xx11 xxxx	…..	xx10 011x	xxxx 0xxx

ME shall be configured with following URSP rules.

Rule Precedence =1

Traffic Descriptor:

DNN=TestGp.rs1

Route Selection Descriptor:

Precedence=1

Network Slice Selection, S-NSSAI: ’01 01 01 01’ (ST: MBB, SD: ‘010101’)

SSC Mode Selection: SSC Mode 1

Access Type preference: 3GPP access

Rule Precedence = 2

Traffic Descriptor:

DNN=TestGp.rs2

Route Selection Descriptor:

Precedence =1

Network Slice Selection, S-NSSAI: ’01 01 01 02’ (ST: MBB, SD: ‘010102’)

SSC Mode Selection: SSC Mode 1

NETWORK (NG-SS)

Cell A:

Transmits on the BCCH, with the following network parameters:

– MCC, MNC: 246/081

– TAC: "000001"

– CellIdentity: "000000001"

For Table 5.4.12-1:

uac‑BarringInfo in SIB1 should be set as in the table:

– Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the tables A1-A3.

Cell B:

This cell is required for some sequences as in the Table 5.4.12-1.

Transmits on the BCCH, with the following network parameters:

– TAI (MCC/MNC/TAC): MCC, MNC: see Table 5.4.12-1, TAC="000002".

– CellIdentity: "000000002"

For Table 5.4.12-1:

uac-BarringInfo in SIB1 should be set as in the table:

– Refer to Annex A for the Methods UAC_BarringInfo_xxxxxx() in the tables A1-A3.

REGISTRATION ACCEPT IEIs.

– Operator-Defined Access Category Definitions IEI is configured as defined in Table 5.4.12-1.

– Refer to Annex A tables A4-A5 for Methods ODAC_definitions1() and ODAC_definitions2().

For HPLMN Cells:

– Allowed S-NSSAI IEI is configured to include S-NSSAIs ’01 01 01 01’, ’01 01 01 02’and ’01 01 01 03’.

For VPLMN Cells:

– Allowed S-NSSAI IEI is configured to include S-NSSAIs (’01 01 01 01’, ’01 01 01 01’), (’01 01 01 02’, ’01 01 01 02’), and (’01 01 01 03’, ’01 01 01 03’).

5.4.12.4.2 Procedure

For the Table 5.4.12-1

a) NG-SS activates Cell A with uac‑BarringInfo in SIB1 as in the table, the ME is switched on with the UICC 1 and sends the 1^st REGISTRATION REQUEST to Cell A.

b) Cell A responds with a REGISTRATION ACCEPT message with the Operator-Defined Access Category Definitions IEI as defined in the Table.

If the Cell 2 in the table is Cell A,

c) Remove the UICC 1 from the ME.

d) Insert the UICC 2.

e) ME sends the 2^nd REGISTRATION REQUEST to Cell A and NG-SS sends the 2^nd REGISTRATION ACCEPT.

If the Cell 2 in the table is Cell B,

c) Remove the UICC 1 from the ME and deactivate the Cell A.

d) Insert the UICC 2 and activate Cell B.

e) ME sends the 2^nd REGISTRATION REQUEST to Cell B and NG-SS sends the 2^nd REGISTRATION ACCEPT.

f) Attempt 1^st MO Data call to DNN TestGp.rs1/S-NSSAI ’01 01 01 01’’ using the MMI or EMMI.

g) Attempt 2^nd MO Data call to DNN TestGp.rs2/S-NSSAI ’01 01 01 02′ using the MMI or EMMI.

5.4.12.4.3 Acceptance criteria

For the Table 5.4.12-1

– The UE shall make a successful or not successful 1^st MO data call in accordance with the result indicated in the table.

– The UE shall make a successful or not successful 2^nd MO data call in accordance with the result indicated in the table.

Table 5.4.12-1

TC Seq#	Access Category for Call 1 & 2	USIM		Cell 2		SIB 1: uac-BarringInfo (for all the Cells)	Operator-defined access category definitions IEI in	Result
TC Seq#	Access Category for Call 1 & 2	EF_{UAC_AIC}	EF_ACC (Byte 1 b8-b4)	Cell Id of	PLMN-Identity (MCC/MNC)	SIB 1: uac-BarringInfo (for all the Cells)	1^st: REGISTRATION ACCEPT 2^nd: REGISTRATION ACCEPT	MO Data call 1 successful?	MO Data call 2 successful?
1.1	7,33	0x00 00 00 00	00000	Cell A	246 / 081	Not Present	ODAC_definitions1(0) ODAC_definitions2(1,16)	Yes	Yes
1.2	7,33	0x00 00 00 00	00000	Cell A	246 / 081	UAC_BarringInfo_Common( 33,0×0000000’B)	ODAC_definitions1(0) ODAC_definitions2(1,16)	Yes	No
1.3	34,7	0x01 00 00 00	00000	Cell A	246 / 081	UAC_BarringInfo_Common2 ( 34,0×1000000’B, 50,0×1000000’B )	ODAC_definitions2(18,1) ODAC_definitions1(2)	No	Yes
1.4	7,63	0x01 00 00 00	00000	Cell B	244 / 081	UAC_BarringInfo_Common2 ( 63,0×0000000’B, 7,0×0100000’B )	ODAC_definitions1(3) ODAC_definitions2(31,18)	No	No
1.5	7,7	0x02 00 00 00	00000	Cell A	246 / 081	UAC_BarringInfo_Common( 63,0×0100000’B)	ODAC_definitions1(31) ODAC – Not present	Yes	Yes
1.6	7,7	0x00 00 00 00	10000	Cell B	246 / 082	UAC_BarringInfo_Common( 48,0×0010000’B)	ODAC_definitions1(16) ODAC – Not present	Yes	Yes
1.7	7,7	0x00 00 00 00	00100	Cell B	246 / 082	UAC_BarringInfo_Common2 ( 32,0×0000100’B, 34,0×0000100’B )	ODAC_definitions2(0,2) ODAC – Empty	Yes	Yes
1.8	7,7	0x00 00 00 00	00100	Cell B	246 / 082	UAC_BarringInfo_Common2 ( 50,0×0000100’B, 33,0×0000100’B )	ODAC_definitions2(18,1) ODAC – Not present	Yes	Yes