10.1.8

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

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

10.1.8.1 NSAC / PDU session establishment reject / Maximum number of PDU sessions reached / Back-off timer is neither zero nor deactivated

10.1.8.1.1 Test Purpose (TP)

(1)

with { UE is establishing UE-requested PDU session by sending PDU Session establishment Request message with S-NSSAI }

ensure that {

when { UE receives PDU SESSION ESTABLISHMENT REJECT with 5GSM cause value #69 "insufficient resources for specific slice" and Back-off timer value which is neither zero nor deactivated }

then { UE shall start timer T3585 and shall not send another PDU SESSION ESTABLISHMENT REQUEST message for the same S-NSSAI }

}

(2)

with { The timer T3585 associated with a S-NSSAI is running }

ensure that {

when { UE is switched off and switched on }

then { UE shall restart the timer T3585 if the time remaining for T3585 timeout at switch off is greater than the time elapsed between switch off and switch on }

}

(3)

with { UE in 5GMM-REGISTERED state }

ensure that {

when { The timer T3585 associated with the S-NSSAI expires }

then { UE could initiate PDU session establishment request with the S-NSSAI }

}

(4)

with { UE is establishing UE-requested PDU session by sending PDU Session establishment Request message with no S-NSSAI provided }

ensure that {

when { UE receives PDU SESSION ESTABLISHMENT REJECT with 5GSM cause value #69 "insufficient resources for specific slice" and Back-off timer value which is neither zero nor deactivated }

then { UE shall start timer T3585 and shall not send another PDU SESSION ESTABLISHMENT REQUEST message without an S-NSSAI }

}

10.1.8.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.501, clause 4.6.3.1, clause 6.4.1.4.2.Unless otherwise stated these are Rel-17 requirements.

[TS 24.501, clause 4.6.3.1]

A serving PLMN or the HPLMN, or SNPN can perform network slice admission control for the S-NSSAI(s) subject to NSAC to monitor and control the total number of established PDU sessions per network slice. The SMF performs network slice admission control on the S-NSSAI during the PDU session establishment procedure. If the maximum number of PDU sessions on a network slice associated with an S-NSSAI has been already reached, the SMF rejects the PDU session establishment request using S-NSSAI based congestion control as specifed in subclause 6.2.8 and 6.4.1.4.2.

The SMF performs network slice admission control on the S-NSSAI for a PDU session that is associated with the non-3GPP access, when the UE requests to transfer a session from the non-3GPP access to the 3GPP access with the Allowed PDU session status IE as described in subclause 5.6.1.4. If the maximum number of PDU sessions on a network slice associated with an S-NSSAI has been already reached, the SMF rejects the request to establish the user-plane resources (see 3GPP TS 29.502 [20A]).

Based on operator policy, the session management based network slice admission control is not applicable for the PDU session for emergency services, or the session management based network slice admission control result is ignored for the PDU session for emergency services.

Based on operator policy, the session management based network slice admission control is not applicable for the PDU session for priority services, or the session management based network slice admission control result is ignored for the PDU session for priority services.

NOTE: How the SMF determines that the PDU session is used for priority services is outside the scope of this release of the present document.

The session management based network slice admission control is not applicable to PDU session established for onboarding services in SNPN.

NOTE 1: For the MA PDU session during the PDU session establishment procedure, the SMF performs network slice admission control only when it is newly established over the associated access type.

NOTE 2: For a set of redundant PDU sessions, the SMF performs network slice admission control for each PDU session independently.

[TS 24.501, clause 6.4.1.4.2]

If:

– the 5GSM cause value #69 "insufficient resources for specific slice" and the Back-off timer value IE are included in the PDU SESSION ESTABLISHMENT REJECT message; or

– an indication that the 5GSM message was not forwarded due to S-NSSAI only based congestion control is received along a Back-off timer value and a PDU SESSION ESTABLISHMENT REQUEST message with the PDU session ID IE set to the PDU session ID of the PDU session;

the UE shall ignore the Re-attempt indicator IE provided by the network, if any, and take different actions depending on the timer value received for timer T3585 in the Back-off timer value IE or depending on the Back-off timer value received from the 5GMM sublayer (if the UE is a UE configured for high priority access in selected PLMN, exceptions are specified in subclause 6.2.8):

a) If the timer value indicates neither zero nor deactivated and an S-NSSAI was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3585 associated with the corresponding S-NSSAI, if it is running. If the timer value indicates neither zero nor deactivated and no S-NSSAI was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3585 associated with no S-NSSAI if it is running. The timer T3585 to be stopped includes the timer T3585 applied for all the PLMNs, if running, and the timer T3585 applied for the registered PLMN, if running. The UE shall then start timer T3585 with the value provided in the Back-off timer value IE or with the Back-off timer value received from the 5GMM sublayer and:

The UE shall not stop timer T3585 upon a PLMN change or inter-system change;

b) if the timer value indicates that this timer is deactivated and an S-NSSAI was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3585 associated with the corresponding S-NSSAI, if it is running. If the timer value indicates that this timer is deactivated and no S-NSSAI was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3585 associated with no S-NSSAI if it is running. The timer T3585 to be stopped includes the timer T3585 applied for all the PLMNs, if running, and the timer T3585 applied for the registered PLMN, if running. The UE:

1) shall not send another PDU SESSION ESTABLISHMENT REQUEST message with request type different from "initial emergency request" and different from "existing emergency PDU session", or another PDU SESSION MODIFICATION REQUEST with exception of those identified in subclause 6.4.2.1, for a non-emergency PDU session for the same S-NSSAI until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated if the UE does not support access to an SNPN using credentials from a credentials holder, or the selected entry of the "list of subscriber data" is updated if the UE supports access to an SNPN using credentials from a credentials holder, or the UE receives a PDU SESSION MODIFICATION COMMAND message for a non-emergency PDU session for the same S-NSSAI from the network, or a PDU SESSION AUTHENTICATION COMMAND message for a non-emergency PDU session for the same S-NSSAI from the network, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for the same S-NSSAI from the network; and

2) shall not send another PDU SESSION ESTABLISHMENT REQUEST message without an S-NSSAI and with request type different from "initial emergency request" and different from "existing emergency PDU session", or another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for a non-emergency PDU session established without an S-NSSAI provided by the UE, if no S-NSSAI was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated if the UE does not support access to an SNPN using credentials from a credentials holder, or the selected entry of the "list of subscriber data" is updated if the UE supports access to an SNPN using credentials from a credentials holder, or the UE receives a PDU SESSION MODIFICATION COMMAND message for a non-emergency PDU session established without an S-NSSAI provided by the UE, or a PDU SESSION AUTHENTICATION COMMAND message for a non-emergency PDU session established without an S-NSSAI provided by the UE, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for a non-emergency PDU session established without an S-NSSAI provided by the UE.

The timer T3585 remains deactivated upon a PLMN change or inter-system change; and

c) if the timer value indicates zero, the UE:

1) shall stop timer T3585 associated with the corresponding S-NSSAI (including the timer T3585 applied for all the PLMNs, if running, and the timer T3585 applied for the registered PLMN, if running), if running, and may send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the same S-NSSAI; and

2) if no S-NSSAI was provided during the PDU session establishment and the request type was different from "initial emergency request " and different from "existing emergency PDU session", the UE shall stop timer T3585 associated with no S-NSSAI, if running, and may send another PDU SESSION ESTABLISHMENT REQUEST message without an S-NSSAI (including the timer T3585 applied for all the PLMNs, if running, and the timer T3585 applied for the registered PLMN, if running), or another PDU SESSION MODIFICATION REQUEST message without an S-NSSAI provided by the UE.

If the 5GSM congestion re-attempt indicator IE with the ABO bit set to "The back-off timer is applied in all PLMNs" is included in the PDU SESSION ESTABLISHMENT REJECT message with the 5GSM cause value #69 "insufficient resources for specific slice", then the UE shall apply the timer T3585 for all the PLMNs. Otherwise, the UE shall apply the timer T3585 for the registered PLMN. Additionally, if the 5GSM congestion re-attempt indicator IE with the CATBO bit set to "The back-off timer is applied in the current access type" is included in the PDU SESSION ESTABLISHMENT REJECT message with the 5GSM cause value #69 "insufficient resources for specific slice", then the UE shall apply the timer T3585 for the current access type. Otherwise, the UE shall apply the timer T3585 for both 3GPP access type and non-3GPP access type.

If the Back-off timer value IE is not included or no Back-off timer value is received from the 5GMM sublayer, then the UE may send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the same S-NSSAI or without an S-NSSAI.

When the timer T3585 is running or the timer is deactivated, the UE is allowed to initiate a PDU session establishment procedure for emergency services.

If the timer T3585 is running when the UE enters state 5GMM-DEREGISTERED, the UE remains switched on, and the USIM in the UE (if any) remains the same and the entry in the "list of subscriber data" to which timer T3585 is associated (if any) is not updated, then timer T3585 is kept running until it expires or it is stopped.

If the UE is switched off when the timer T3585 is running, and if the USIM in the UE (if any) remains the same and the entry in the "list of subscriber data" to which timer T3585 is associated (if any) is not updated when the UE is switched on, the UE shall behave as follows:

let t1 be the time remaining for T3585 timeout at switch off and let t be the time elapsed between switch off and switch on. If t1 is greater than t, then the timer shall be restarted with the value t1 – t. If t1 is equal to or less than t, then the timer need not be restarted. If the UE is not capable of determining t, then the UE shall restart the timer with the value t1.

NOTE: As described in this subclause, upon PLMN change or inter-system change, the UE does not stop the timer T3584 or T3585. This means the timer T3584 or T3585 can still be running or be deactivated for the given 5GSM procedure, the PLMN, the S-NSSAI and optionally the DNN combination when the UE returns to the PLMN or when it performs inter-system change back from S1 mode to N1 mode. Thus the UE can still be prevented from sending another PDU SESSION ESTABLISHMENT REQUEST or PDU SESSION MODIFICATION REQUEST message in the PLMN for the same S-NSSAI and optionally the same DNN.

Upon PLMN change, if T3584 is running or is deactivated for an S-NSSAI, a DNN, and old PLMN, but T3584 is not running and is not deactivated for the S-NSSAI, the DNN, and new PLMN, then the UE is allowed to send a PDU SESSION ESTABLISHMENT REQUEST message for the same S-NSSAI and the same DNN in the new PLMN.

Upon PLMN change, if T3585 is running or is deactivated for an S-NSSAI and old PLMN, but T3585 is not running and is not deactivated for the S-NSSAI and new PLMN, then the UE is allowed to send a PDU SESSION ESTABLISHMENT REQUEST message for the same S-NSSAI in the new PLMN.

10.1.8.1.3 Test description

10.1.8.1.3.1 Pre-test conditions

System Simulator:

– NGC Cell A.

UE:

– None.

Preamble:

– The UE is in state 3N-A on NGC Cell A according to TS 38.508-1 [4].

10.1.8.1.3.2 Test procedure sequence

Table 10.1.8.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Cause the UE to request establishment of PDU session with S-NSSAI. Note: This step is triggered by MMI or AT command.	–	–	–	–
2	The UE transmits an ULInformationTransfer message and a PDU SESSION ESTABLISHMENT REQUEST message with S-NSSAI.	–>	NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST	–	–
3	The SS transmits PDU SESSION ESTABLISHMENT REJECT message with 5GSM cause value #69 and Back-off timer value which is neither zero nor deactivated	<–	PDU SESSION ESTABLISHMENT REJECT	–	–
4	Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST message with S-NSSAI within 60 seconds?	–>	NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST	1	F
5	The SS transmits an RRCRelease message.	<–	NR RRC: RRCRelease	–	–
6	The UE is switched off by executing generic procedure in Table 4.9.6.1-1 in TS 38.508-1 [4]	–	–	–	–
7	The UE is switched on	–	–	–	–
8	The general procedure is completed by executing of the UE registration procedure in TS 38.508-1 [4] table 4.5.2.2-2 , ‘connected without release’.	–	–	–	–
9	Cause the UE to request establishment of PDU session with the same S-NSSAI as step 1. Note: This step is triggered by MMI or AT command.	–	–	–	–
10	Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST message with S-NSSAI within 60 seconds?	–>	NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST	2	F
11	Cause the UE to request establishment of PDU session with the same S-NSSAI as step 1 after 1 minute since step 10. Note: This step is triggered by MMI or AT command.	–	–	–	–
12	Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST message with S-NSSAI within 60 seconds?	–>	5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST	2,3	P
13	The SS transmits a PDU SESSION ESTABLISHMENT ACCEPT message.	<–	5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT ACCEPT	–	–
14	Cause the UE to request establishment of PDU session without S-NSSAI. Note: This step is triggered by MMI or AT command.	–	–	–	–
15	The UE transmits an ULInformationTransfer message and a PDU SESSION ESTABLISHMENT REQUEST message without S-NSSAI.	–>	NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST	–	–
16	The SS transmits PDU SESSION ESTABLISHMENT REJECT message with 5GSM cause value #69 and Back-off timer value which is neither zero nor deactivated	<–	PDU SESSION ESTABLISHMENT REJECT	–	–
17	Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST message without S-NSSAI within 60 seconds?	–>	NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST	4	F
18	The SS transmits an RRCRelease message.	<–	NR RRC: RRCRelease	–	–

10.1.8.1.3.3 Specific message contents

Table 10.1.8.1.3.3-1: UL NAS TRANSPORT (step 2, step 12, Table 10.1.8.1.3.2-1)

Derivation Path: TS 38.508-1 [4] table 4.7.1-10, condition INITIAL_PDU_REQUEST.
Information Element	Value/remark	Comment	Condition
S-NSSAI	present

Table 10.1.8.1.3.3-2: PDU SESSION ESTABLISHMENT REJECT (step 3, step 16, Table 10.1.8.1.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.2-3
Information Element	Value/remark	Comment	Condition
5GSM cause	‘0100 0101’	insufficient resources for specific slice
Back-off timer value	‘1010 0011’B	3 minutes

Table 10.1.8.1.3.3-3: PDU SESSION ESTABLISHMENT ACCEPT (step 13, Table 10.1.8.1.3.2-1)

Derivation path: TS 38.508-1 clause 4.7.2-2
Information Element	Value/remark	Comment	Condition
S-NSSAI	The same S-NSSAI as the S-NSSAI of the PDU session which UE request at step 11

Table 10.1.8.1.3.3-4: UL NAS TRANSPORT (step 15, Table 10.1.8.1.3.2-1)

Derivation Path: TS 38.508-1 [4] table 4.7.1-10, condition INITIAL_PDU_REQUEST.

10.1.8.2 NSAC / PDU session establishment reject / Maximum number of PDU sessions reached / Back-off timer is deactivated

10.1.8.2.1 Test Purpose (TP)

(1)

with { UE is establishing UE-requested PDU session by sending PDU Session establishment Request message with S-NSSAI }

ensure that {

when { UE receives PDU SESSION ESTABLISHMENT REJECT with 5GSM cause value #69 "insufficient resources for specific slice" and Back-off timer value which is deactivated }

then { UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for the same S-NSSAI until UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated if the UE does not support access to an SNPN using credentials from a credentials holder }

}

(2)

with { UE is establishing UE-requested PDU session by sending PDU Session establishment Request message with S-NSSAI }

ensure that {

when { UE receives PDU SESSION ESTABLISHMENT REJECT with 5GSM cause value #69 "insufficient resources for specific slice" and Back-off timer value which is deactivated }

then { UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for the same S-NSSAI until UE receives a PDU SESSION MODIFICATION COMMAND message for the same S-NSSAI }

}

(3)

with { UE is establishing UE-requested PDU session by sending PDU Session establishment Request message with S-NSSAI }

ensure that {

when { UE receives PDU SESSION ESTABLISHMENT REJECT with 5GSM cause value #69 "insufficient resources for specific slice" and Back-off timer value which is deactivated }

then { UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for the same S-NSSAI until UE receives a PDU SESSION AUTHENTICATION COMMAND message for the same S-NSSAI }

}

(4)

with { UE is establishing UE-requested PDU session by sending PDU Session establishment Request message with S-NSSAI }

ensure that {

when { UE receives PDU SESSION ESTABLISHMENT REJECT with 5GSM cause value #69 "insufficient resources for specific slice" and Back-off timer value which is deactivated }

then { UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for the same S-NSSAI until UE receives a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for the same S-NSSAI }

}

10.1.8.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.501, clause 4.6.3.1, clause 6.4.1.4.2.Unless otherwise stated these are Rel-17 requirements.

[TS 24.501, clause 4.6.3.1]

NOTE: How the SMF determines that the PDU session is used for priority services is outside the scope of this release of the present document.

The session management based network slice admission control is not applicable to PDU session established for onboarding services in SNPN.

NOTE 1: For the MA PDU session during the PDU session establishment procedure, the SMF performs network slice admission control only when it is newly established over the associated access type.

NOTE 2: For a set of redundant PDU sessions, the SMF performs network slice admission control for each PDU session independently.

[TS 24.501, clause 6.4.1.4.2]

If:

– the 5GSM cause value #69 "insufficient resources for specific slice" and the Back-off timer value IE are included in the PDU SESSION ESTABLISHMENT REJECT message; or

The UE shall not stop timer T3585 upon a PLMN change or inter-system change;

The timer T3585 remains deactivated upon a PLMN change or inter-system change; and

c) if the timer value indicates zero, the UE:

When the timer T3585 is running or the timer is deactivated, the UE is allowed to initiate a PDU session establishment procedure for emergency services.

10.1.8.2.3 Test description

10.1.8.2.3.1 Pre-test conditions

System Simulator:

– NGC Cell A.

UE:

– None.

Preamble:

– The UE is in state 3N-A on NGC Cell A according to TS 38.508-1 [4].

10.1.8.2.3.2 Test procedure sequence

Table 10.1.8.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Cause the UE to request establishment of PDU session with S-NSSAI. Note: This step is triggered by MMI or AT command.	–	–	–	–
2	The UE transmits an ULInformationTransfer message and a PDU SESSION ESTABLISHMENT REQUEST message with S-NSSAI.	–>	NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST	–	–
3	The SS transmits PDU SESSION ESTABLISHMENT REJECT message with 5GSM cause value #69 and Back-off timer value which is deactivated	<–	PDU SESSION ESTABLISHMENT REJECT	–	–
4	Cause the UE to request establishment of PDU session with the same S-NSSAI as step 1. Note: This step is triggered by MMI or AT command.	–	–	–	–
5	Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST message with S-NSSAI within 60 seconds?	–>	NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST	1,2,3,4	F
6	The SS transmits an RRCRelease message.	<–	NR RRC: RRCRelease	–	–
7	The UE is switched off by executing generic procedure in Table 4.9.6.1-1 in TS 38.508-1 [4]	–	–	–	–
8	The UE is switched on	–	–	–	–
9	The general procedure is completed by executing of the UE registration procedure in TS 38.508-1 [4] table 4.5.2.2-2 , ‘connected without release’.	–	–	–	–
10	Cause the UE to request establishment of PDU session with the same S-NSSAI as step 1. Note: This step is triggered by MMI or AT command.	–	–	–	–
11	Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST message with S-NSSAI within 60 seconds?	–>	NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST	1	P
12	The SS transmits PDU SESSION ESTABLISHMENT REJECT message with 5GSM cause value #69 and Back-off timer value which is deactivated	<–	PDU SESSION ESTABLISHMENT REJECT	–	–
13	The SS transmits a PDU SESSION MODIFICATION COMMAND message.	<–	PDU SESSION MODIFICATION COMMAND	–	–
14	The UE transmits a PDU SESSION MODIFICATION COMPLETE message.	–>	PDU SESSION MODIFICATION COMPLETE	–	–
15	Cause the UE to request establishment of PDU session with the same S-NSSAI as step 1. Note: This step is triggered by MMI or AT command.	–	–	–	–
16	Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST message with S-NSSAI within 60 seconds?	–>	NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST	2	P
17	The SS transmits PDU SESSION ESTABLISHMENT REJECT message with 5GSM cause value #69 and Back-off timer value which is deactivated	<–	PDU SESSION ESTABLISHMENT REJECT
18	The SS transmits PDU SESSION AUTHENTICATION COMMAND including an EAP-Request message.	<–	PDU SESSION AUTHENTICATION COMMAND	–	–
19	The UE transmits a PDU SESSION AUTHENTICATION COMPLETE containing EAP-Response message.	–>	PDU SESSION AUTHENTICATION COMPLETE	–	–
20	The SS transmits PDU SESSION AUTHENTICATION RESULT message containing an EAP-Success message.	<–	PDU SESSION AUTHENTICATION RESULT	–	–
21	Cause the UE to request establishment of PDU session with the same S-NSSAI as step 1. Note: This step is triggered by MMI or AT command.	–	–
22	Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST message with S-NSSAI within 60 seconds?	–>	NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST	3	P
23	The SS transmits PDU SESSION ESTABLISHMENT REJECT message with 5GSM cause value #69 and Back-off timer value which is deactivated	<–	PDU SESSION ESTABLISHMENT REJECT	–	–
24	The SS transmits a PDU SESSION RELEASE COMMAND without Back-off timer value IE for the same S-NSSAI as step 1.	<–	5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION RELEASE COMMAND	–	–
25	The UE transmits a PDU SESSION RELEASE COMPLETE message	–>	5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION RELEASE COMPLETE	–	–
26	Cause the UE to request establishment of PDU session with the same S-NSSAI as step 1. Note: This step is triggered by MMI or AT command.	–	–	–	–
27	Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST message with S-NSSAI within 60 seconds?	–>	NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST	4	P
28	The SS transmits a PDU SESSION ESTABLISHMENT ACCEPT message.	<–	5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT ACCEPT	–	–

10.1.8.2.3.3 Specific message contents

Table 10.1.8.2.3.3-1: UL NAS TRANSPORT (step 2, step 11, step 16, step 22, step 27,Table 10.1.8.2.3.2-1)

Derivation Path: TS 38.508-1 [4] table 4.7.1-10, condition INITIAL_PDU_REQUEST.
Information Element	Value/remark	Comment	Condition
S-NSSAI	present

Table 10.1.8.2.3.3-2: PDU SESSION ESTABLISHMENT REJECT (step 3, step 12, step 17, step 23 ,Table 10.1.8.2.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.2-3
Information Element	Value/remark	Comment	Condition

5GSM cause	‘0100 0101’	insufficient resources for specific slice
Back-off timer value	‘1110 0000’B	deactivated

Table 10.1.8.2.3.3-3: PDU SESSION ESTABLISHMENT ACCEPT (step 28, Table 10.1.8.2.3.2-1)

Derivation path: TS 38.508-1 clause 4.7.2-2
Information Element	Value/remark	Comment	Condition
S-NSSAI	The same S-NSSAI as the S-NSSAI of the PDU session which UE request at step 10

Table 10.1.8.2.3.3-4: PDU SESSION AUTHENTICATION RESULT (step 20, Table 10.1.8.2.3.2-1)

Derivation Path: TS 38.508-1 table 4.7.2-6
Information Element	Value/remark	Comment	Condition
EAP message	EAP-success	See TS 24.501 [25] subclause 9.11.2.2

10.1.8.3 NSAC / PDU session establishment reject / Maximum number of PDU sessions reached / Back-off timer is zero or not included

10.1.8.3.1 Test Purpose (TP)

(1)

with { UE is establishing UE-requested PDU session by sending PDU Session establishment Request message with S-NSSAI }

ensure that {

when { UE receives PDU SESSION ESTABLISHMENT REJECT with 5GSM cause value #69 "insufficient resources for specific slice" and Back-off timer value set to zero }

then { UE could send another PDU SESSION ESTABLISHMENT REQUEST message for the same S-NSSAI }

}

(2)

with { UE is establishing UE-requested PDU session by sending PDU Session establishment Request message with no S-NSSAI provided }

ensure that {

when { UE receives PDU SESSION ESTABLISHMENT REJECT with 5GSM cause value #69 "insufficient resources for specific slice" and Back-off timer value set to zero }

then { UE could send another PDU SESSION ESTABLISHMENT REQUEST message without an S-NSSAI }

}

(3)

with { UE is establishing UE-requested PDU session by sending PDU Session establishment Request message with S-NSSAI }

ensure that {

when { UE receives PDU SESSION ESTABLISHMENT REJECT with 5GSM cause value #69 "insufficient resources for specific slice" and Back-off timer value IE is not included }

then { UE could send another PDU SESSION ESTABLISHMENT REQUEST message for the same S-NSSAI }

10.1.8.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.501, clause 4.6.3.1, clause 6.4.1.4.2.Unless otherwise stated these are Rel-17 requirements.

[TS 24.501, clause 4.6.3.1]

NOTE: How the SMF determines that the PDU session is used for priority services is outside the scope of this release of the present document.

The session management based network slice admission control is not applicable to PDU session established for onboarding services in SNPN.

NOTE 1: For the MA PDU session during the PDU session establishment procedure, the SMF performs network slice admission control only when it is newly established over the associated access type.

NOTE 2: For a set of redundant PDU sessions, the SMF performs network slice admission control for each PDU session independently.

[TS 24.501, clause 6.4.1.4.2]

If:

– the 5GSM cause value #69 "insufficient resources for specific slice" and the Back-off timer value IE are included in the PDU SESSION ESTABLISHMENT REJECT message; or

The UE shall not stop timer T3585 upon a PLMN change or inter-system change;

The timer T3585 remains deactivated upon a PLMN change or inter-system change; and

c) if the timer value indicates zero, the UE:

When the timer T3585 is running or the timer is deactivated, the UE is allowed to initiate a PDU session establishment procedure for emergency services.

10.1.8.3.3 Test description

10.1.8.3.3.1 Pre-test conditions

System Simulator:

– NGC Cell A.

UE:

– None.

Preamble:

– The UE is in state 3N-A on NGC Cell A according to TS 38.508-1 [4].

10.1.8.3.3.2 Test procedure sequence

Table 10.1.8.3.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Cause the UE to request establishment of PDU session with S-NSSAI. Note: This step is triggered by MMI or AT command.	–	–	–	–
2	The UE transmits an ULInformationTransfer message and a PDU SESSION ESTABLISHMENT REQUEST message with S-NSSAI.	–>	NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST	–	–
3	The SS transmits PDU SESSION ESTABLISHMENT REJECT message with 5GSM cause value #69 and Back-off timer value which is set to zero.	<–	PDU SESSION ESTABLISHMENT REJECT	–	–
4	Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST message with S-NSSAI within 60 seconds?	–>	NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST	1	P
5	The SS transmits a PDU SESSION ESTABLISHMENT ACCEPT message.	<–	5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT ACCEPT	–	–
6	The generic test procedure in TS 38.508-1 Table 4.9.21.2.2-1 of Procedure for PDU Session Release is performed.	–	–	–	–
7	Cause the UE to request establishment of PDU session without S-NSSAI. Note: This step is triggered by MMI or AT command.	–	–	–	–
8	The UE transmits an ULInformationTransfer message and a PDU SESSION ESTABLISHMENT REQUEST message without S-NSSAI.	–>	NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST	–	–
9	The SS transmits PDU SESSION ESTABLISHMENT REJECT message with 5GSM cause value #69 and Back-off timer value which is set to zero.	<–	PDU SESSION ESTABLISHMENT REJECT	–	–
10	Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST message without S-NSSAI within 60 seconds?	–>	NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST	2	P
11	The SS transmits a PDU SESSION ESTABLISHMENT ACCEPT message.	<–	5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT ACCEPT	–	–
12	The generic test procedure in TS 38.508-1 Table 4.9.21.2.2-1 of Procedure for PDU Session Release is performed.	–	–	–	–
13	Cause the UE to request establishment of PDU session with S-NSSAI. Note: This step is triggered by MMI or AT command.	–	–	–	–
14	The UE transmits an ULInformationTransfer message and a PDU SESSION ESTABLISHMENT REQUEST message with S-NSSAI.	–>	NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST	–	–
15	The SS transmits PDU SESSION ESTABLISHMENT REJECT message with 5GSM cause value #69 and and Back-off timer value IE is not included.	<–	PDU SESSION ESTABLISHMENT REJECT	–	–
16	Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST message with S-NSSAI within 60 seconds?	–>	NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST	3	P
17	The SS transmits a PDU SESSION ESTABLISHMENT ACCEPT message.	<–	5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT ACCEPT	–	–

10.1.8.3.3.3 Specific message contents

Table 10.1.8.3.3.3-1: UL NAS TRANSPORT (step 2, step 4, step 14, step 16, Table 10.1.8.3.3.2-1)

Derivation Path: TS 38.508-1 [4] table 4.7.1-10, condition INITIAL_PDU_REQUEST.
Information Element	Value/remark	Comment	Condition
S-NSSAI	present

Table 10.1.8.1.3.3-2: PDU SESSION ESTABLISHMENT REJECT (step 3, step 9, Table 10.1.8.3.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.2-3
Information Element	Value/remark	Comment	Condition

5GSM cause	‘0100 0101’	insufficient resources for specific slice
Back-off timer value	‘1010 0000’B	0 minutes

Table 10.1.8.1.3.3-3: PDU SESSION ESTABLISHMENT ACCEPT (step 5, step 17, Table 10.1.8.3.3.2-1)

Derivation path: TS 38.508-1 clause 4.7.2-2
Information Element	Value/remark	Comment	Condition
S-NSSAI	The same S-NSSAI as the S-NSSAI of the PDU session which UE request at step 1

Table 10.1.8.1.3.3-4: PDU SESSION ESTABLISHMENT REJECT (step 15, Table 10.1.8.3.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.2-3
Information Element	Value/remark	Comment	Condition

5GSM cause	‘0100 0101’	insufficient resources for specific slice
Back-off timer value	Not present

Table 10.1.8.3.3.3-5: UL NAS TRANSPORT (step 8, step 10, Table 10.1.8.3.3.2-1)

Derivation Path: TS 38.508-1 [4] table 4.7.1-10, condition INITIAL_PDU_REQUEST.