11.3.5 UAC / Access Identity 1 / New cell not in the country of its HPLMN/EHPLMN 0% access probability / MPS indicator / HPLMN/0%/100% accessibility AC5 / MMTEL-Video call

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

11.3.5.1 Test Purpose (TP)

(1)

with { UE configured for Access Identity 1 }

ensure that {

when { UE moves to a new cell which is not in the country of its HPLMN or in an EHPLMN (if the EHPLMN list is present) having received SIB1 message including UAC set to 0% accessibility for Access Category 7 and Access Identity 1 is exempted from the access barring check }

then { UE does not consider Access Identity 1 as valid and does not initiate RRC connection since Access Identity 0 is not exempted from the access barring check until barring for Access Category 7 is removed }

}

(2)

with { UE configured for Access Identity 1 }

ensure that {

when { UE moves to a new cell which is not in the country of its HPLMN or in an EHPLMN (if the EHPLMN list is present) but receives the MPS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message being set to ""Access identity 1 valid"" }

then { UE does consider Access Identity 1 as valid }

}

(3)

with { UE configured for Access Identity 1 having received SIB1 containing UAC Barring Info indicating 0% accessibility for Access Category 5 in NR RRC_IDLE state on HPLMN }

ensure that {

when { User initiates MMTEL-Video call }

then { UE does not attempt to initiate connection on the NR Cell }

}

(4)

with { UE configured for Access Identity 1 having received SIB1 containing UAC Info indicating 100% accessibility for Access Category 5 while camped on HPLMN in NR RRC_IDLE state }

ensure that {

when { User initiates MMTEL-Video call and Access Barring check indicates Barring is alleviated }

then { UE initiates RRC Connection Setup procedure with establishmentCause set to mps-PriorityAccess }

}

11.3.5.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in TS 24.501: clause 4.5.2, 4.5.4.1 and 4.5.6 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.2]

When the UE needs to initiate an access attempt in one of the events listed in subclause 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.

The set of the access identities applicable for the request is determined by the UE in the following way:

a) for each of the access identities 1, 2, 11, 12, 13, 14 and 15 in table 4.5.2.1, the UE shall check whether the access identity is applicable in the selected PLMN, if a new PLMN is selected, or otherwise if it is applicable in the RPLMN or equivalent PLMN; and

b) if none of the above access identities is applicable, then access identity 0 is applicable.

Table 4.5.2.1: Access identities

Access Identity number

UE configuration

0

UE is not configured with any parameters from this table

1 (NOTE 1)

UE is configured for multimedia priority service (MPS).

2 (NOTE 2)

UE is configured for mission critical service (MCS).

3-10

Reserved for future use

11 (NOTE 3)

Access Class 11 is configured in the UE.

12 (NOTE 3)

Access Class 12 is configured in the UE.

13 (NOTE 3)

Access Class 13 is configured in the UE.

14 (NOTE 3)

Access Class 14 is configured in the UE.

15 (NOTE 3)

Access Class 15 is configured in the UE.

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

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

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

The UE uses the MPS indicator bit of the 5GS network feature support IE to determine if access identity 1 is valid. Processing of the MPS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message is described in subclause 5.5.1.2.4 and subclause 5.5.1.3.4. 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".

When the UE is in the country of its HPLMN, the contents of the USIM files EFUAC_AIC and EFACC as specified in 3GPP TS 31.102 [22] and the rules specified in table 4.5.2.1 are used to determine the applicability of access identity 1 and access classes 11 – 15. When the UE is in the country of its HPLMN, and the USIM file EFUAC_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. When the UE is in the country of its HPLMN, and the USIM file EFUAC_AIC indicates the UE is configured for access identity 1, the MPS indicator bit of the 5GS network feature support IE is not applicable. When the UE is not in the country of its HPLMN, the contents of the USIM files EFUAC_AIC and EFACC are not applicable.

The UE uses the MCS indicator bit of the 5GS network feature support IE to determine if access identity 2 is valid. Processing of the MCS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message is described in subclause 5.5.1.2.4 and subclause 5.5.1.3.4. 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".

When the UE is in the country of its HPLMN, the contents of the USIM files EFUAC_AIC and EFACC as specified in 3GPP TS 31.102 [22] and the rules specified in table 4.5.2.1 are used to determine the applicability of access identity 2 and access classes 11 – 15. When the UE is in the country of its HPLMN, and the USIM file EFUAC_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. When the UE is in the country of its HPLMN, and the USIM file EFUAC_AIC indicates the UE is configured for access identity 2, the MCS indicator bit of the 5GS network feature support IE is not applicable. When the UE is not in the country of its HPLMN, the contents of the USIM files EFUAC_AIC and EFACC are not applicable.

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 subclause 4.5.3).

NOTE: The case when an access attempt matches more than one rule includes the case when multiple events trigger an access attempt at the same time.

Table 4.5.2.2: Mapping table for access categories

Rule #

Type of access attempt

Requirements to be met

Access Category

1

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

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

Access attempt is for MT access

0 (= MT_acc)

2

Emergency

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

2 (= emergency)

3

Access attempt for operator-defined access category

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

32-63
(= based on operator classification)

4

Access attempt for delay tolerant service

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

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

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

1 (= delay tolerant)

5

MO MMTel voice call

Access attempt is for MO MMTel voice call

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

4 (= MO MMTel voice)

6

MO MMTel video call

Access attempt is for MO MMTel video call

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

5 (= MO MMTel video)

7

MO SMS over NAS or MO SMSoIP

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

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

6 (= MO SMS and SMSoIP)

8

UE NAS initiated 5GMM specific procedures

Access attempt is for MO signalling

3 (= MO_sig)

9

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

Access attempt is for MO data

7 (= MO_data)

10

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

No further requirement is to be met

7 (= MO_data)

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

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

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

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

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

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

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

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

[TS 24.501, clause 4.5.4.1]

When the UE is in 5GMM-IDLE mode, upon receiving a request from the upper layers for an access attempt, the NAS shall categorize the access attempt into access identities and an access category following subclause 4.5.2, table 4.5.2.1 and table 4.5.2.2, and subclause 4.5.3, and provide the applicable access identities and the access category to the lower layers for the purpose of access control checking. In this request to the lower layer the NAS can also provide to the lower layer the RRC establishment cause determined as specified in subclause 4.5.6 of this specification.

NOTE 1: The access barring check is performed by the lower layers.

NOTE 2: As an implementation option, the NAS can provide the RRC establishment cause to the lower layers after being informed by the lower layers that the access attempt is allowed.

If the UE has uplink user data pending for one or more PDU sessions when it builds a REGISTRATION REQUEST or SERVICE REQUEST message as initial NAS message, the UE shall indicate the respective PDU sessions in the Uplink data status IE as specified in subclause 5.5.1.3.2 and 5.6.1.2, regardless of the access category for which the access barring check is performed.

NOTE 3: The UE indicates pending user data for all the respective PDU sessions, even if barring timers are running for some of the corresponding access categories.

If the lower layers indicate that the access attempt is allowed, the NAS shall initiate the procedure to send the initial NAS message for the access attempt.

If the lower layers indicate that the access attempt is barred, the NAS shall not initiate the procedure to send the initial NAS message for the access attempt. Additionally:

a) if the event which triggered the access attempt was an MO-MMTEL-voice-call-started indication or an MO-MMTEL-video-call-started indication:

1) if the UE is operating in the single-registration mode and the UE’s usage setting is "voice centric", the UE may attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC, it then proceeds with the appropriate EMM specific procedures and, if necessary, ESM procedures to make a PDN connection providing access to IMS available; see subclause 4.8.2 and 3GPP TS 24.301 [15];

2) if the UE is operating in the dual-registration mode, the UE may proceed in S1 mode with the appropriate EMM specific procedures and ESM procedures to make a PDN connection providing access to IMS available; see subclause 4.8.3 and 3GPP TS 24.301 [15];

3) otherwise, the NAS shall notify the upper layers that the access attempt is barred. In this case, upon receiving an indication from the lower layers that the barring is alleviated for the access category with which the access attempt was associated, the NAS shall notify the upper layers that the barring is alleviated for the access category and may initiate the procedure to send the initial NAS message, if still needed; and

b) if the event which triggered the access attempt was an MO-SMSoIP-attempt-started indication:

1) if the UE is operating in the single-registration mode, the UE may attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC, it then proceeds with the appropriate EMM specific procedures and, if necessary, ESM procedures to make a PDN connection providing access to IMS available; see subclause 4.8.2 and 3GPP TS 24.301 [15];

2) if the UE is operating in the dual-registration mode, the UE may proceed in S1 mode with the appropriate EMM specific procedures and ESM procedures to make a PDN connection providing access to IMS available; see subclause 4.8.3 and 3GPP TS 24.301 [15];

3) otherwise, the NAS layer shall notify the upper layers that the access attempt is barred. In this case, upon receiving an indication from the lower layers that the barring is alleviated for the access category with which the access attempt was associated, the NAS shall notify the upper layers that the barring is alleviated for the access category and may initiate the procedure to send the initial NAS message, if still needed.

NOTE 4: Barring timers, on a per access category basis, are run by the lower layers. At expiry of barring timers, the indication of alleviation of access barring is indicated to the NAS on a per access category basis.

[TS 24.501, clause 4.5.6]

When 5GMM requests the establishment of a NAS-signalling connection, the RRC establishment cause used by the UE shall be selected according to one or more access identities (see subclause 4.5.2) and the determined access category as specified in table 4.5.6.1 and table 4.5.6.2. If the determined access category is an operator-defined access category, then the RRC establishment cause used by the UE shall be selected according to table 4.5.6.1 and table 4.5.6.2 based on one or more access identities (see subclause 4.5.2) and the standardized access category determined for the operator-defined access category as described in subclause 4.5.3.

Table 4.5.6.1: Mapping table for access identities/access categories and RRC establishment cause when establishing N1 NAS signalling connection via NR connected to 5GCN

Access identities

Access categories

RRC establishment cause is set to

0

0 (= MT_acc)

mt-Access

1 (= delay tolerant)

Not applicable (NOTE 1)

2 (= emergency)

emergency

3 (= MO_sig)

mo-Signalling

4 (= MO MMTel voice)

mo-VoiceCall

5 (= MO MMTel video)

mo-VideoCall

6 (= MO SMS and SMSoIP)

mo-SMS

7 (= MO_data)

mo-Data

1

Any category

mps-PriorityAccess

2

Any category

mcs-PriorityAccess

11, 15

Any category

highPriorityAccess

12,13,14,

Any category

highPriorityAccess

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

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

Table 4.5.6.2: Mapping table for access identities/access categories and RRC establishment cause when establishing N1 NAS signalling connection via E-UTRA connected to 5GCN

Access identities

Access categories

RRC establishment cause is set to

0

0 (= MT_acc)

mt-Access

1 (= delay tolerant)

Not applicable (NOTE 1)

2 (= emergency)

emergency

3 (= MO_sig)

mo-Signalling

4 (= MO MMTel voice)

mo-VoiceCall

5 (= MO MMTel video)

mo-VoiceCall

6 (= MO SMS and SMSoIP)

mo-Data

7 (= MO_data)

mo-Data

1

Any category

highPriorityAccess

2

Any category

highPriorityAccess

11, 15

Any category

highPriorityAccess

12,13,14,

Any category

highPriorityAccess

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

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

[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 handover resulting in change of PCell in RRC_CONNECTED the UE shall defer access barring checks until it has obtained valid UAC information (from SIB1) 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> 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, and if timer T390 corresponding to an Access Category is not running; or

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

1> 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.5.3 Test description

11.3.5.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 are configured as shown in Table 11.3.5.3.1–1. PLMN settings are defined in TS 36.523-1 [13] table 6.0.1-1.

Table 11.3.5.3.1–1: PLMN identifiers

NR Cell

PLMN names

NR Cell 1

PLMN1

NR Cell 12

PLMN2

– 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:

– The UE is equipped with USIM configuration 18 as defined in TS 38.508-1 [4] Table 6.4.1-18.

Preamble:

– The UE is in state 1N-A, RRC_IDLE Connectivity (NR), in accordance with the procedure described in TS 38.508-1 [4], clause 4.5.2.

11.3.5.3.2 Test procedure sequence

Table 11.3.5.3.2-1 for FR1 and Table 11.3.5.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 columns marked "T1", "T2" and "T3" are 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.5.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

-80

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

T2

SS/PBCH

SSS EPRE

dBm/SCS

-80

Off

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

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

Table 11.3.5.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

FFS

Off

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

T1

SS/PBCH

SSS EPRE

dBm/SCS

Off

FFS

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

T2

SS/PBCH

SSS EPRE

dBm/SCS

FFS

Off

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

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

Table 11.3.5.3.2-3: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

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

–

–

–

–

1A

Void

–

–

–

–

1B

Void

–

–

–

–

2

The UE transmits RRCSetupRequest message on NR cell 12.

Check: Does the RRCSetupRequest message includes the establishmentCause which is any value except mps-PriorityAccess?

–>

NR RRC: RRCSetupRequest

1

P

2A-2B

Steps 3-4 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed on NR Cell 12. (Note 2)

–

–

–

–

–

EXCEPTION: Steps 2Ca1 to 2Cb3a1 describe behaviour that depends on events happening prior to their execution; the "lower case letter" identifies a step sequence that take place if a specific prior event takes place.

–

–

–

–

2Ca1-2Ca15

IF 5GS registration type is set as Initial Registration in step 2B, THEN Steps 5 to 19 of the generic test procedure in TS 38.508-1 Table 4.5.2.2-2 are performed without RRC release on NR Cell 12.

–

–

–

–

2Cb1-2Cb2

IF 5GS registration type is set as Mobility Registration in step 2B, THEN Steps 4 to 5 of the generic test procedure in TS 38.508-1 Table 4.9.5.2.2-1 are performed without RRC release on NR Cell 12.

–

–

–

–

3-10

Void

–

–

–

–

10A

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

<–

NR RRC: RRCRelease

–

–

10B

Make the UE attempt to establish a PDU session. This can be done by an AT/MMI command.

–

–

–

–

10C

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

–>

NR RRC: RRCSetupRequest

1

F

10D

SS changes SIB1 of NR Cell 12 according to Table 11.3.5.3.3-2 and sends Short Message on PDCCH using P-RNTI.

–

–

–

–

10E

Start Timer=28 sec. (Note4)

–

–

–

–

–

EXCEPTION: Steps 10Ea1-10Eb3 describes optional behaviour that depends on the UE implementation.

–

–

–

–

10Ea1

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

–>

NR RRC: RRCSetupRequest

1

P

10Ea2

Stop Timer=28 sec.

–

–

–

–

10eb1

Timer=28 sec expires

–

–

–

–

10Eb2

Make the UE attempt to establish a PDU session. This can be done by an AT/MMI command.

–

–

–

–

10Eb3

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

–>

NR RRC: RRCSetupRequest

1

P

10Fa1-10Fa8

Steps 3-8 of the generic procedure for

NR RRC_Connected specified in TS 38.508-1

Table 4.5.2.2-4 are performed without RRC release.

–

–

–

–

10H

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

–

–

–

–

11

Void

–

–

–

–

11A

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

–

–

–

–

11B

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

–

–

–

–

11C

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

–

–

–

–

11D-11F

Steps 2-4 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed on NR Cell 12. (Note 2)

–

–

–

–

–

EXCEPTION: Steps 11Fa1 to 11Fb3a1 describe behaviour that depends on events happening prior to their execution; the "lower case letter" identifies a step sequence that take place if a specific prior event takes place.

–

–

–

–

11Fa1-11Fa16a1

IF 5GS registration type is set as Initial Registration in step 11F, THEN Steps 5 to 20a1of the generic test procedure in TS 38.508-1 Table 4.5.2.2-2 are performed on NR Cell 12.

–

–

–

–

11Fb1-11Fb3a1

IF 5GS registration type is set as Mobility Registration in step 211F, THEN Steps 4 to 6a1 of the generic test procedure in TS 38.508-1 Table 4.9.5.2.2-1 are performed on NR Cell 12.

–

–

–

–

12

The SS transmits a Paging message.

<–

NR RRC: Paging

–

–

13

Void

–

–

–

–

14

Check: Does the UE transmit a RRCSetupRequest message including establishmentCause equal to mps–PriorityAccess within 10 s?

–>

NR RRC: RRCSetupRequest

2

P

15-20

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

–

–

–

–

21-23

Void

–

–

–

–

24

The SS transmits an RRCRelease message to release RRC connection and moves the UE to RRC_IDLE.

<–

NR RRC: RRCRelease

–

–

25

SS changes SIB1 of NR cell 1 according to Table 11.3.5.3.3-1.

–

–

–

–

26

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

–

–

–

–

26A-26C

Steps 2-4 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed. (Note 2)

–

–

–

–

–

EXCEPTION: Steps 26Da1 to 26Db3a1 describe behaviour that depends on events happening prior to their execution; the "lower case letter" identifies a step sequence that take place if a specific prior event takes place.

–

–

–

–

26Da1-26Da16a1

IF 5GS registration type is set as Initial Registration in step 26C, THEN Steps 5 to 20a1of the generic test procedure in TS 38.508-1 Table 4.5.2.2-2 are performed on NR Cell 1.

–

–

–

–

26Db1-26Db3a1

IF 5GS registration type is set as Mobility Registration in step 26C, THEN Steps 4 to 6a1 of the generic test procedure in TS 38.508-1 Table 4.9.5.2.2-1 are performed on NR Cell 1.

–

–

–

–

27-32a1

Void

–

–

–

–

33

AT command to make the UE attempt MMTEL-Video call.

–

–

–

–

34

Check: Does the UE transmit an RRCSetupRequest message including establishmentCause equal to mps-PriorityAccess within 6 s?

–>

NR RRC: RRCSetupRequest

3

F

35

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

<–

PDCCH (DCI 1_0): Short Message

–

–

35A

SS starts timer T_Delay=26 sec.

–

–

–

–

–

EXCEPTION: Steps 35Aa1 to 35Ab3 describe behaviour that depends on the UE implementation; the "lower case letter" identifies a step sequence that take place depending on the UE implementation.

–

–

–

–

35Aa1

Check: Does the UE transmit an RRCSetupRequest message including establishmentCause equal to mps-PriorityAccess?

–>

NR RRC: RRCSetupRequest

4

P

35Aa2

SS stops timer T_Delay=26 sec.

–

–

–

–

35Ab1

timer T_Delay=26 sec expires.

–

–

–

–

35Ab2

Make the UE attempt another MMTEL-Video call.

–

–

–

–

35Ab3

Check: Does the UE transmit an RRCSetupRequest message including establishmentCause equal to mps-PriorityAccess within 10 s?

–>

NR RRC: RRCSetupRequest

4

P

36-38

Void

–

–

–

–

39-49b3

Steps 3-13b3 of generic test procedure for IMS MO Video call establishment in 5GC as specified in 38.508-1 [4] Table 4.9.24.2.2-1 are performed.

–

–

–

–

50

The generic test procedure for IMS MT call release in 5GC as specified in TS 38.508-1 [4] Table 4.9.18.2.2-1 takes place.

–

–

–

–

Note 1: The SS includes a 5GS network feature support IE in the REGISTRATION ACCEPT message configured as Table 11.3.5.3.3-3.

Note 2: The 5GS registration type shall be only set as Mobility Registration for R16 UEs according to TS 24.501 subclause 5.2.3.2.5 specified in Release 16. The EXCEPTION description applies only to R15 UEs.

Note 3: The wait time 21s is selected to be more than T390 maximum = (0.7 + 0.6 * rand) * uac-BarringTime(16s) = 20.7s when ‘rand’ takes the maximum value of 0.99.

Note 4: The wait time 28s is selected to cover 20.7s ((0.7 + 0.6 * rand) * uac-BarringTime(16s)) + 5.12s (modification period) + 2s (extra wait timer for UE to trigger RRCSetupRequest) = 27.82s rounded up to 28s when ‘rand’ takes the maximum value of 0.99.

11.3.5.3.3 Specific message contents

Table 11.3.5.3.3-1: SIB1 of NR Cell 1 (step 25 and step 35, Table 11.3.5.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 {

step 25

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

1 entry

UAC-BarringPerCat[1] SEQUENCE {

entry 1

accessCategory

5

(= MO MMTel video)

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

}

uac-BarringInfo

Not present

Step 35

}

Table 11.3.5.3.3-2: SIB1 of NR Cell 12 (Step 1 and step 10D, Table 11.3.5.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 {

Step 1

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

1 entry

UAC-BarringPerCat[1] SEQUENCE {

entry 1

accessCategory

7

(= MO_data)

uac-barringInfoSetIndex

1

Value 1 corresponds to the first entry in uac-BarringInfoSetList

}

}

uac-BarringPerPLMN-List

Not present

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

1 entry

UAC-BarringInfoSet[1] SEQUENCE {

entry 1

uac-BarringFactor

p00

0% access probability

uac-BarringTime

s16

16 s

uac-BarringForAccessIdentity

0111111’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

}

uac-BarringInfo

Not present

Step 10D

}

Table 11.3.5.3.3-3: REGISTRATION ACCEPT (step 11Fa10 and step 11Fb2, Table 11.3.5.3.2-3)

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

Information Element

Value/remark

Comment

Condition

5GS network feature support

‘1000 0001 0000 0000 0000 0000’B

Access identity 1 valid in RPLMN or equivalent PLMN.

IMS voice over PS session supported over 3GPP access.

All other features set to "not supported" including the

‘Interworking without N26 interface not supported’.