10.1.4 UE-requested PDU session establishment

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

10.1.4.1 UE-requested PDU session establishment / Abnormal / T3580

10.1.4.1.1 Test Purpose (TP)

(1)

with { the UE in 5GMM-REGISTERED state and at least one PDU session has been established. the SS sends PDU SESSION RELEASE COMMAND with #39 "reactivation requested", and the UE has sent a PDU SESSION ESTABLISHMENT REQUEST message }

ensure that {

when { On the 1st, 2nd, 3rd, 4th expiry of timer T3580 }

then { the UE retransmits PDU SESSION ESTABLISHMENT REQUEST message and the PDU session information which was transported together with the initial transmission of the PDU SESSION ESTABLISHMENT REQUEST message }

}

(2)

with { the UE in 5GMM-REGISTERED state and has sent a PDU SESSION ESTABLISHMENT REQUEST message }

ensure that {

when { on the maximum 5th expiry of timer T3580 }

then { the UE aborts the procedure }

}

10.1.4.1.2 Conformance requirements

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

[TS 24.501, clause 6.4.1.6]

The following abnormal cases can be identified:

a) Expiry of timer T3580

The UE shall, on the first expiry of the timer T3580, retransmit the PDU SESSION ESTABLISHMENT REQUEST message and the PDU session information which was transported together with the initial transmission of the PDU SESSION ESTABLISHMENT REQUEST message and shall reset and start timer T3580, if still needed. This retransmission can be repeated up to four times, i.e. on the fifth expiry of timer T3580, the UE shall abort the procedure, release the allocated PTI and enter the state PROCEDURE TRANSACTION INACTIVE.

10.1.4.1.3 Test description

10.1.4.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 with at least one PDU session X (1 <= X <= 15) active according to 38.508-1 [4].

10.1.4.1.3.2 Test procedure sequence

Table 10.1.4.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

0A

Cause the UE to request establishment of PDU session Y to the DN. (Note 3)

–

–

–

–

0B

The PDU session establishment procedure as specified in TS 38.508-1 [4] subclause 4.5A.2 takes place

–

–

–

–

1

The generic test procedure in TS 38.508-1 clause 4.9.21 for PDU Session Release is performed with PDU SESSION RELEASE COMMAND message includes 5GSM cause #39 "reactivation requested" to release PDU session X.

–

–

–

–

2-15

Void.

–

–

–

–

16

The UE transmits a PDU SESSION ESTABLISHMENT REQUEST message and the S-NSSAI and DNN in UL NAS TRANSPORT message are the same values as released (Note 2).

–>

5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST

–

–

17

The SS waits 16 seconds (T3580).

–

–

–

–

18

Check: Does the UE re-transmit the PDU SESSION ESTABLISHMENT REQUEST message and the S-NSSAI and DNN in UL NAS TRANSPORT message are the same values as sent in step 16?

–>

5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST

1

P

19

The SS waits 16 seconds (2nd expiry of T3580).

–

–

–

–

20

Check: Does the UE re-transmit the PDU SESSION ESTABLISHMENT REQUEST message and the S-NSSAI and DNN in UL NAS TRANSPORT message are the same values as sent in step 16?

–>

5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST

1

P

21

The SS waits 16 seconds (3rd expiry of T3580).

–

–

–

–

22

Check: Does the UE re-transmit the PDU SESSION ESTABLISHMENT REQUEST message and the S-NSSAI and DNN in UL NAS TRANSPORT message are the same values as sent in step 16?

–>

5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST

1

P

23

The SS waits 16 seconds (4th expiry of T3580).

–

–

–

–

24

Check: Does the UE re-transmit the PDU SESSION ESTABLISHMENT REQUEST message and the S-NSSAI and DNN in UL NAS TRANSPORT message are the same values as sent in step 16?

–>

5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST

1

P

25

The SS waits 16 seconds (5th expiry of T3580).

–

–

–

–

26

Check: Does the UE re-transmit the PDU SESSION ESTABLISHMENT REQUEST message and the S-NSSAI and DNN in UL NAS TRANSPORT message are the same values as sent in step 16 in the next 20 seconds? (Note 1)

–>

5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST

2

F

Note 1: The 20 seconds is chosen randomly as long as it is greater than T3580 = 16 seconds.

Note 2 : At step 16 the SS waits for 1s for the UE to transmit the PDU Session Establishment REQ. Upon expiry of 1s, the PDU Session Establishment may be performed by MMI or AT command.

Note 3: The request of connectivity to an additional PDU session may be performed by MMI or AT command.

10.1.4.1.3.3 Specific message contents

Table 10.1.4.1.3.3-0: PDU SESSION ESTABLISHMENT ACCEPT (preamble; step 3, Table 4.5A.2.2.2-1, TS 38.508-1 [4])

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#n in TS 38.508-1[4],Table 4.8.4-1

‘n’ in QoS rule#n corresponds to the default PDU session type as set in the PICS pc_APN_Default_Configuration

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 during (preamble; step 2a1, Table 4.5A.2.2.2-2, TS 38.508-1 [4])

Table 10.1.4.1.3.3-1: PDU SESSION RELEASE COMMAND (Step 1, Table 10.1.4.1.3.2-1; step 1, TS 38.508-1 [4] Table 4.9.21.2.2-1)

Derivation path: TS 38.508-1 [4], table 4.7.2-14

Information Element

Value/Remark

Comment

Condition

PDU session ID

X

ID of the active PDU session in preamble

5GSM cause

‘0010 0111’B

Reactivation requested

Table 10.1.4.1.3.3-2: UL NAS TRANSPORT (Step 16, 18, 20, 22, 24 Table 10.1.4.1.3.2-1)

Derivation path: TS 38.508-1 [4], table 4.7.1-10

Information Element

Value/Remark

Comment

Condition

S-NSSAI

Same as the S-NSSAI of PDU session X in the Preamble

"OMIT" can be a value for S-NSSAI

DNN

Same as the DNN of PDU session X in the Preamble

"OMIT" can be a value for DNN

Table 10.1.4.1.3.3-3: UL NAS TRANSPORT (Preamble, step 2a1, Table 4.5A.2.2.2-2, TS 38.508-1 [4])

Derivation Path: TS 38.508-1 [4] Table 4.7.1-10

Information Element

Value/remark

Comment

Condition

S-NSSAI

Record value if present, otherwise record as "OMIT"

TTCN recorded the value to compare with value of same IE in step 16,18, 20, 22, 24

DNN

Record value if present, otherwise record as "OMIT"

TTCN recorded the value to compare with value of same IE in step 16,18, 20, 22, 24