11.3.9 UAC / Access Identity 0 / ODAC / PLMN / RPLMN / not EPLMN

38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification

11.3.9.1 Test Purpose (TP)

(1)

with { UE not configured for special AIs (1,2,11-15) having received Operator Defined Access Category ""x"" in the range 32..63 with access category criteria type set to ""DNN"" valid in the selected PLMN or RPLMN as part of Registration Procedure }

ensure that {

when { SIB1 message indicates no barring for Access category 7 but 0% accessibility for Access Category ""x" }

then { UE does not initiate PDU Session Establishment for the "DNN" }

}

(2)

with { UE not configured for special AIs (1,2,11-15) having received Operator Defined Access Category ""x"" in the range 32..63 with access category criteria type set to ""DNN"" valid in the selected PLMN or RPLMN as part of Registration Procedure , SIB1 message indicates no barring for Access category 7 but 0% accessibility for Access Category ""x" }

ensure that {

when { UE moves to another cell belonging to a different PLMN not equivalent to the previous PLMN }

then { UE is able to initiate PDU Session Establishment for "DNN" in the new PLMN }

}

11.3.9.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in TS 24.501: clause 4.5.3 and TS 38.331: clause 5.3.14.1, 5.3.14.2, 5.3.14.4 and 5.3.14.5. Unless otherwise stated these are Rel-15 requirements.

[TS 24.501, clause 4.5.3]

Operator-defined access category definitions can be signalled to the UE using NAS signalling. Each operator-defined access category definition consists of the following parameters:

a) a precedence value which indicates in which order the UE shall evaluate the operator-defined category definition for a match;

b) an operator-defined access category number, i.e. access category number in the 32-63 range that uniquely identifies the access category in the PLMN in which the access categories are being sent to the UE;

c) criteria consisting of one or more access category criteria type and associated access category criteria type values. The access category criteria type can be set to one of the following:

1) DNN;

2) OS Id + OS App Id of application triggering the access attempt; or

3) S-NSSAI; and

NOTE 1: An access category criteria type can be associated with more than one access category criteria values.

d) optionally, a standardized access category. This standardized access category is used in combination with the access identities of the UE to determine the RRC establishment cause as specified in subclause 4.5.6.

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.

Each operator-defined access category definition has a different precedence value.

Several operator-defined access category definitions can have the same operator-defined access category number.

If:

– an access category in bullet d) is not provided;

– an access category in bullet d) is provided and is not a standardized access category; or

– an access category in bullet d) is provided, is a standardized access category and is not recognized by the UE;

the UE shall use instead:

– access category 3 (MO_sig) if the access attempt is triggered by uplink signalling; or

– access category 7 (MO_data) if the access attempt is triggered by uplink data

in combination with the access identities of the UE to determine the RRC establishment cause as specified in subclause 4.5.6.

The operator-defined access category definitions are valid in the PLMN which provided them and in a PLMN equivalent to the PLMN which provided them, as specified in annex C.

If the UE stores operator-defined access category definitions valid in the selected PLMN or the RPLMN, then access control in 5GMM-IDLE mode will only be performed for the event a) defined in subclause 4.5.1. If the transition from 5GMM-IDLE mode over 3GPP access to 5GMM-CONNECTED mode is due to a UE NAS initiated 5GMM specific procedure, then this access attempt shall be mapped to one of the standardized access categories in the range < 32, see subclause 4.5.2. I.e. for this case the UE shall skip the checking of operator-defined access category definitions.

If the UE is stores operator-defined access category definitions valid in the selected PLMN or the RPLMN, then access control in 5GMM-CONNECTED mode and in 5GMM-CONNECTED mode with RRC inactive indication will only be performed for the events 1) to 6) defined in subclause 4.5.1.

The UE shall handle the operator-defined access category definitions stored for the RPLMN as specified in subclause 5.4.4.3, subclause 5.5.1.2.4, and subclause 5.5.1.3.4.

When the UE is switched off, the UE shall keep the operator-defined access category definitions so that the operator-defined access category definitions can be used after switch on.

When the UE selects a new PLMN which is not equivalent to the previously selected PLMN, the UE shall stop using the operator-defined access category definitions stored for the previously selected PLMN and should keep the operator-defined access category definitions stored for the previously selected PLMN.

NOTE 2: When the UE selects a new PLMN which is not equivalent to the previously selected PLMN, the UE can delete the operator-defined access category definitions stored for the previously selected PLMN e.g. if there is no storage space in the UE.

[TS 38.331, clause 5.3.14.1]

The purpose of this procedure is to perform access barring check for an access attempt associated with a given Access Category and one or more Access Identities upon request from upper layers according to TS 24.501 [23] or the RRC layer.

After a PCell change in RRC_CONNECTED the UE shall defer access barring checks until it has obtained SIB1 (as specified in 5.2.2.2) from the target cell.

[TS 38.331, clause 5.3.14.2]

Upon initiation of the procedure, the UE shall:

1> if timer T390 is running for the Access Category:

2> consider the access attempt as barred;

1> else if timer T302 is running and the Access Category is neither ‘2’ nor ‘0’:

2> consider the access attempt as barred;

1> else:

2> if the Access Category is ‘0’:

3> consider the access attempt as allowed;

2> else:

3> if SIB1 includes uac-BarringPerPLMN-List and the uac-BarringPerPLMN-List contains an UAC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to the PLMN selected by upper layers (see TS 24.501 [23]):

4> select the UAC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to the PLMN selected by upper layers;

4> in the remainder of this procedure, use the selected UAC-BarringPerPLMN entry (i.e. presence or absence of access barring parameters in this entry) irrespective of the uac-BarringForCommon included in SIB1;

3> else if SIB1 includes uac-BarringForCommon:

4> in the remainder of this procedure use the uac-BarringForCommon (i.e. presence or absence of these parameters) included in SIB1;

3> else:

4> consider the access attempt as allowed;

3> if uac-BarringForCommon is applicable or the uac-ACBarringListType indicates that uac-ExplicitACBarringList is used:

4> if the corresponding UAC-BarringPerCatList contains a UAC-BarringPerCat entry corresponding to the Access Category:

5> select the UAC-BarringPerCat entry;

5> if the uac-BarringInfoSetList contains a UAC-BarringInfoSet entry corresponding to the selected uac-barringInfoSetIndex in the UAC-BarringPerCat:

6> select the UAC-BarringInfoSet entry;

6> perform access barring check for the Access Category as specified in 5.3.14.5, using the selected UAC-BarringInfoSet as "UAC barring parameter";

5> else:

6> consider the access attempt as allowed;

4> else:

5> consider the access attempt as allowed;

3> else if the uac-ACBarringListType indicates that uac-ImplicitACBarringList is used:

4> select the uac-BarringInfoSetIndex corresponding to the Access Category in the uac-ImplicitACBarringList;

4> if the uac-BarringInfoSetList contains the UAC-BarringInfoSet entry corresponding to the selected uac-BarringInfoSetIndex:

5> select the UAC-BarringInfoSet entry;

5> perform access barring check for the Access Category as specified in 5.3.14.5, using the selected UAC-BarringInfoSet as "UAC barring parameter";

4> else:

5> consider the access attempt as allowed;

3> else:

4> consider the access attempt as allowed;

1> if the access barring check was requested by upper layers:

2> if the access attempt is considered as barred:

3> if timer T302 is running:

4> if timer T390 is running for Access Category ‘2’:

5> inform the upper layer that access barring is applicable for all access categories except categories ‘0’, upon which the procedure ends;

4> else

5> inform the upper layer that access barring is applicable for all access categories except categories ‘0’ and ‘2’, upon which the procedure ends;

3> else:

4> inform upper layers that the access attempt for the Access Category is barred, upon which the procedure ends;

2> else:

3> inform upper layers that the access attempt for the Access Category is allowed, upon which the procedure ends;

1> else:

2> the procedure ends.

[TS 38.331, clause 5.3.14.4]

The UE shall:

1> if timer T302 expires or is stopped:

2> for each Access Category for which T390 is not running:

3> consider the barring for this Access Category to be alleviated:

1> else if timer T390 corresponding to an Access Category other than ‘2’ expires or is stopped, and if timer T302 is not running:

2> consider the barring for this Access Category to be alleviated;

1> else if timer T390 corresponding to the Access Category ‘2’ expires or is stopped:

2> consider the barring for this Access Category to be alleviated;

1> when barring for an Access Category is considered being alleviated:

2> if the Access Category was informed to upper layers as barred:

3> inform upper layers about barring alleviation for the Access Category.

2> if barring is alleviated for Access Category ‘8’:

3> perform actions specified in 5.3.13.8;

[TS 38.331, clause 5.3.14.5]

The UE shall:

1> if one or more Access Identities are indicated according to TS 24.501 [23], and

1> if for at least one of these Access Identities the corresponding bit in the uac-BarringForAccessIdentity contained in "UAC barring parameter" is set to zero:

2> consider the access attempt as allowed;

1> else:

2> draw a random number ‘rand’ uniformly distributed in the range: 0 ≤ rand < 1;

2> if ‘rand’ is lower than the value indicated by uac-BarringFactor included in "UAC barring parameter":

3> consider the access attempt as allowed;

2> else:

3> consider the access attempt as barred;

1> if the access attempt is considered as barred:

2> draw a random number ‘rand’ that is uniformly distributed in the range 0 ≤ rand < 1;

2> start timer T390 for the Access Category with the timer value calculated as follows, using the uac-BarringTime included in "AC barring parameter":

T390 = (0.7+ 0.6 * rand) * uac-BarringTime.

11.3.9.3 Test description

11.3.9.3.1 Pre-test conditions

System Simulator:

– 2 NR cells: NR Cell 1 and 12 as specified in TS 38.508-1 [4] table 4.4.2-3.

– System information combination NR-1 as defined in TS 38.508-1 [4] Table 4.4.3.1.2-1 is used in NR cells.

UE:

– None.

Preamble:

– The UE is registered on PLMN1 (NR Cell 1) and in state 3N-A on NR Cell 1(serving cell) by using the procedure described in TS 38.508-1 [4] clause 4.5.2.2 with “connected without release” except that the REGISTRATION ACCEPT message indicates Operator Defined Access Category ""33"" as described in Table 11.3.9.3.3-1.

11.3.9.3.2 Test procedure sequence

Table 11.3.9.3.2-1 for FR1 and Table 11.3.9.3.2-2 for FR2 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions in preamble, while the column marked "T1" is to be applied subsequently in the Main behaviour. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 11.3.9.3.2-1: Time instances of cell power level and parameter changes for FR1

Parameter

Unit

NR Cell 1

NR Cell 12

Remarks

T0

SS/PBCH

SSS EPRE

dBm/SCS

-88

Off

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

T1

SS/PBCH

SSS EPRE

dBm/SCS

Off

-88

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

Note 1: Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.1-3.

Table 11.3.9.3.2-2: Time instances of cell power level and parameter changes for FR2

Parameter

Unit

NR Cell 1

NR Cell 12

Remarks

T0

SS/PBCH

SSS EPRE

dBm/SCS

-82

Off

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

T1

SS/PBCH

SSS EPRE

dBm/SCS

Off

-82

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

Note 1: Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.2-2.

Table 11.3.9.3.2-3: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-2

Void

–

–

–

–

3

Make the UE attempt to establish a PDU session for the DNN defined in Table 11.3.9.3.3-1. This can be done by an AT/MMI command.

–

–

–

–

4

Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST and the DNN in UL NAS TRANSPORT message is the same value in UL NAS TRANSPORT message in preamble within 11.2s?

–>

5GMM: UL NAS TRANSPORT

5GSM: PDU SESSION ESTABLISHMENT REQUEST

1

F

5

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

–

–

–

–

6

The mobility registration updating procedure described in TS 38.508-1 [4] Table 4.9.5.2.2-1 is performed on NR Cell 12 and release RRC connection. (Note 1)

–

–

–

–

6A

Start Timer=5 sec.

–

–

–

–

EXCEPTION: Steps 6Ba1-6Bb3 describes optional behaviour that depends on the UE implementation.

6Ba1

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

–>

NR RRC: RRCSetupRequest

2

P

6Ba2

Stop Timer=5 sec.

–

–

–

–

6Bb1

Timer=5 sec expires

–

–

–

–

6Bb2

Make the UE attempt to establish a PDU session for the DNN defined in Table 11.3.9.3.3-1. This can be done by an AT/MMI command.

–

–

–

–

6Bb3

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

–>

NR RRC: RRCSetupRequest

2

P

9-14

Steps 3-8 of the generic procedure for

NR RRC_Connected specified in TS 38.508-1

Table 4.5.4.2-3 are performed.

–

–

–

–

15

Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST and the DNN value in UL NAS TRANSPORT message is the same as the DNN value of Operator-defined access category definitions defined in Table 11.3.9.3.3-1

–>

5GMM: UL NAS TRANSPORT

5GSM: PDU SESSION ESTABLISHMENT REQUEST

2

P

16

The SS transmits RRCReconfiguration message containing PDU SESSION ESTABLISHMENT ACCEPT message.

<–

NR RRC：RRCReconfiguration

5GMM: DL NAS TRANSPORT

5GSM: PDU SESSION ESTABLISHMENT ACCEPT

–

–

17

The UE transmits RRCReconfigurationComplete message to confirm the establishment of DRB.

–>

NR RRC：RRCReconfigurationComplete

–

–

18

Void

–

–

–

–

Note 1: SS ignore the PDU SESSION ESTABLISHMENT REQUEST sent before SS release RRC connection.

11.3.9.3.3 Specific message contents

Table 11.3.9.3.3-1: REGISTRATION ACCEPT (preamble)

Derivation path: TS 38.508 [4] Table 4.7.1-7

Information Element

Value/remark

Comment

Condition

Operator-defined access category definitions

Precedence value

‘0000 0000’B

PSAC

‘1’B

Value 1 means that standardized access category is present.

Operator-defined access category number

‘00001’B

33

Criteria

Criteria type

‘0000 0000’B

DNN type

Criteria value

DNN length-value pair count

‘0000 0001’B

DNN length-value pair

DNN value length

Set to the length in octets of the DNN value field.

DNN value

‘ABCD‘

Standardized access category

‘00111’B

Access category number 7

Table 11.3.9.3.3-2: SIB1 of NR Cell 1 and NR Cell 12 (preamble and all steps, Table 11.3.9.3.2-3)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-28

Information Element

Value/remark

Comment

Condition

SIB1 ::= SEQUENCE {

uac-BarringInfo SEQUENCE {

NR cell 1

NR cell 12

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

1 entry

UAC-BarringPerCat[1] SEQUENCE {

entry 1

accessCategory

33

uac-barringInfoSetIndex

1

Value 1 corresponds to the first entry in uac-BarringInfoSetList

}

}

uac-BarringPerPLMN-List

Not present

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

1 entry

UAC-BarringInfoSet[1] SEQUENCE {

entry 1

uac-BarringFactor

p00

0% access probability

uac-BarringTime

s16

16 s

uac-BarringForAccessIdentity

‘1111111’B

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

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

}

}

uac-AccessCategory1-SelectionAssistanceInfo

Not Present

}

}

Table 11.3.9.3.3-3: PDU SESSION ESTABLISHMENT ACCEPT (step 16, Table 11.3.9.3.2-3)

Derivation path: TS 38.508-1 [4], Table 4.7.2-2

Information Element

Value/remark

Comment

Condition

Authorized QoS rules

5GC QoS rule of the Config#1 in Table 4.8.4-1

Mapped EPS bearer contexts

Mapped EPS bearer context

Mapped EPS QoS parameters

EPC default bearer context of the Config#1 in Table 4.8.4-1

DNN

The same DNN value as sent in the UL NAS TRANSPORT message at step 15