ExpectedNumberOfNewPDUSessions

Usage: Parameter determining procedure sequence.

A value for this parameter shall be provided when the procedure is called.

Unless the test requires specific number of PDU sessions to be established the value should be either pc_noOf_PDUsSameConnection or pc_noOf_PDUsNewConnection ([23]).

Meaning: The number of PDU sessions which are expected to happen. Depends on the UE configuration and/or the context in which the procedure is used.

K

Usage: Parameter determining procedure sequence.

Meaning: The number of PDU SESSION ESTABLISHMENT REQUEST messages already processed including the one that is currently being processed.

L

Usage: Parameter determining procedure sequence.

Meaning: The number of PDU SESSION ESTABLISHMENT REQUEST messages being received so far.

N

Usage: Parameter determining procedure sequence.

The parameter is initialised with the value of ExpectedNumberOfNewPDUSessions

Meaning: Loop (step sequence repetition) control.

IMS_PDU

Usage: Condition determining specific message contents.

Meaning: PDU session establishment for IMS.
Whether a PDU session is for IMS is determined by the DNN/APN type of the entry in Table 4.8.4-1 which itself has been determined by the DNN IE in the UL NAS TRANSPORT message which carried the corresponding PDU SESSION ESTABLISHMENT REQUEST or by pc_APN_Default_Configuration if the DNN IE was not present

U – S

Message

0

Set K = 0, L = 0,

N = ExpectedNumberOfNewPDUSessions

–

–

–

1

The procedure specified in Table 4.5A.2.2.2-2 takes place.

–

–

–

2

Set K = K +1

–

–

–

–

EXCEPTION: In parallel to the events described in steps 3-6a1 below the events specified in Table 4.5A.2.2.2-2 may take place.

–

–

–

3

The SS transmits an RRCReconfiguration message and an PDU SESSION ESTABLISHMENT ACCEPT

<–

NR RRC: RRCReconfiguration

5GMM: DL NAS TRANSPORT

5GSM: PDU SESSION ESTABLISHMENT ACCEPT

–

4

The UE transmits an RRCReconfigurationComplete message.

–>

NR RRC: RRCReconfigurationComplete

–

–

EXCEPTION: Step 5a1 describes behaviour depending UE implementation; the "lower case letter" identifies a step sequence that take place if the UE performs a specific action.

–

–

–

5a1

IF the ‘IP address allocation’ for the DNN for which the PDU session is established is set to "Yes" in Table 4.8.4-1 THEN, the generic procedure for IP address allocation in the user plane, specified in subclause 4.5A.3, takes place performing IP address allocation in the user plane.

–

–

–

–

EXCEPTION: Step 6a1 describes behaviour depending UE implementation; the "lower case letter" identifies a step sequence that take place if the UE performs a specific action.

–

–

–

6a1

IF the ‘IMS registration’ for the DNN for which the PDU session is established is set to "Yes" in Table 4.8.4-1, THEN the generic procedure for IMS signalling in the U-plane specified in subclause 4.5A.4 takes place.

–

–

–

–

EXCEPTION: Steps 7a1 to 7b2 describe behaviour depending UE implementation; the "lower case letter" identifies a step sequence that take place if the UE performs a specific action.

–

–

–

7a1

IF L > K (NOTE 1) THEN repeat from step 2

–

–

–

7b1

ELSE IF K < N (NOTE 2) THEN repeat from step 1.

–

–

–

NOTE 1: One (or more) further PDU SESSION ESTABLISHMENT REQUEST message has been received in parallel.

NOTE 2: Less PDU SESSION ESTABLISHMENT REQUEST messages than expected have been received and processed so far -> further request are expected from the UE.

U – S

Message

1

Start Wait_Timer = 8 sec.

NOTE: 8s were chosen to cater for T3540 being set to 10s.

–

–

–

–

EXCEPTION: Steps 2a1 to 2b1 describe behaviour depending UE implementation; the "lower case letter" identifies a step sequence that take place if the UE performs a specific action.

–

–

–

2a1

The UE transmits an ULInformationTransfer message and a PDU SESSION ESTABLISHMENT REQUEST

–>

NR RRC: ULInformationTransfer

5GMM: UL NAS TRANSPORT

5GSM: PDU SESSION ESTABLISHMENT REQUEST

–

2a2

Stop Wait_Timer.

–

–

–

2a3

Set L = L +1.

–

–

–

2a4

Check: Does the L>N?

(NOTE 1)

–

–

F

2b1

Check: Does Wait_Timer expire?

(NOTE 2)

–

–

F

NOTE 1: The SS shall raise a fail verdict when there are more PDU SESSION ESTABLISHMENT REQUEST messages than expected and terminate the test. The reason for such a behaviour can be e.g. wrongly set IXIT with which the ExpectedNumberOfNewPDNConnections was initiated,

NOTE 2: Unless this is specified explicitly otherwise e.g. in a test procedure which calls the procedure specified in the present table, the SS shall raise a fail verdict when there are less PDN CONNECTIVITY REQUEST messages than expected received at this point and terminate the test. The reason for such a behaviour can be e.g. wrongly set PICS with which the ExpectedNumberOfNewPDUSessions was initiated.

Information Element

Value/remark

Comment

Condition

RRCReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

rrcReconfiguration ::= SEQUENCE {

radioBearerConfig

RadioBearerConfig with conditions SRB2 and DRB2

NOT IMS_PDU

nonCriticalExtension SEQUENCE {

masterCellGroup

CellGroupConfig with condition SRB2_DRB2

NOT IMS_PDU

dedicatedNAS-MessageList SEQUENCE (SIZE(1..maxDRB)) OF DedicatedNAS-Message {}

DedicatedNAS-Message

}

}

}

}

Information Element

Value/remark

Comment

Condition

RRCReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

rrcReconfiguration ::= SEQUENCE {

radioBearerConfig

RadioBearerConfig with condition DRBn

n is chosen as the next available number higher or equal to 2

RadioBearerConfig with condition DRB1

IMS_PDU

nonCriticalExtension SEQUENCE {

masterCellGroup

CellGroupConfig with condition DRBn

n is set to the same value as for the radioBearerConfig IE above

CellGroupConfig with condition DRB1

IMS_PDU

dedicatedNAS-MessageList SEQUENCE (SIZE(1..maxDRB)) OF DedicatedNAS-Message {}

DedicatedNAS-Message

}

}

}

}

U – S

Message

1

The UE transmits a PDU SESSION ESTABLISHMENT REQUEST

–>

5GMM: UL NAS TRANSPORT

5GSM: PDU SESSION ESTABLISHMENT REQUEST

2

The SS establishes an IPSec child security association according to the IKEv2 specification in RFC 7296 [34]

3

The SS transmits an PDU SESSION ESTABLISHMENT ACCEPT

<–

5GMM: DL NAS TRANSPORT

5GSM: PDU SESSION ESTABLISHMENT ACCEPT

ExpectedNumberOfNewPDNConnections

Usage: Parameter determining procedure sequence.

A value for this parameter shall be provided when the procedure is called.

Unless the test requires specific number of PDN connections to be established the value should be either pc_noOf_PDNsSameConnection or pc_noOf_PDNsNewConnection ([19]).

Meaning: The number of PDN connections which are expected to happen. Depends on the UE configuration and/or the context in which the procedure is used.

K

Usage: Parameter determining procedure sequence.

Meaning: The number of PDN CONNECTIVITY REQUEST messages already processed including the one that is currently being processed.

L

Usage: Parameter determining procedure sequence.

Meaning: The number of PDN CONNECTIVITY REQUEST messages being received so far.

N

Usage: Parameter determining procedure sequence.

The parameter is initialised with the value of ExpectedNumberOfNewPDNConnections

Meaning: Loop (step sequence repetition) control.

U – S

Message

0

Set K = 0, L = 0,

N = ExpectedNumberOfNewPDNConnections

–

–

–

1

The procedure specified in Table 4.5A.2B.2.2-2 takes place.

–

–

–

2

Set K = K +1.

–

–

–

–

EXCEPTION: In parallel to the events described in steps 3-6a1 below the events specified in Table 4.5A.2B.2.2-2 may take place.

–

–

–

3-4

Step 2-3 as defined in TS 36.508 [2], Table 4.5A.16.3-1, Generic Test Procedure to establish additional PDN connectivity take place.

–

–

–

–

EXCEPTION: IF the ‘IP address allocation’ for the APN for which the PDN connection is established is set to "Yes" in Table 4.8.4-1 THEN, in parallel to the event described in step 5 below the generic procedure for IP address allocation in the U-plane specified in TS 36.508 [2], subclause 4.5A.1 takes place performing IP address allocation in the U-plane if requested by the UE.

–

–

–

–

EXCEPTION: IF the ‘IMS registration’ for the APN for which the PDN connection is established is set to "Yes" in Table 4.8.4-1, THEN in parallel to the event described in step 5 below the relevant generic procedure for IMS signalling in the U-plane specified in Table 4.8.4-1 takes place.

–

–

–

5

Step 4 as defined in TS 36.508 [2], Table 4.5A.16.3-1, Generic Test Procedure to establish additional PDN connectivity takes place.

–

–

–

–

EXCEPTION: Steps 6a1 to 6b1 describe behaviour depending UE implementation; the "lower case letter" identifies a step sequence that take place if the UE performs a specific action.

–

–

–

6a1

IF L > K (NOTE 1) THEN repeat from step 2.

–

–

–

6b1

ELSE IF K < N (NOTE 2) THEN repeat from step 1.

–

–

–

NOTE 1: One (or more) further PDN CONNECTIVITY REQUEST message has been received in parallel.

NOTE 2: Less PDN CONNECTIVITY REQUEST messages than expected have been received and processed so far and consequently further requests are expected from the UE.

U – S

Message

1

Start Wait_Timer = 10 sec.

NOTE: 10 sec is an arbitrary value.

–

–

–

–

EXCEPTION: Steps 2a1 to 2b1 describe behaviour depending UE implementation; the "lower case letter" identifies a step sequence that take place if the UE performs a specific action.

–

–

–

2a1

Step 1 as defined in Table 4.5A.16.3-1, specified in TS 36.508 [2], subclause 4.5A.16 Generic Test Procedure to establish additional PDN connectivity takes place.

The UE transmits a PDN CONNECTIVITY REQUEST message to request an additional PDN.

–>

PDN CONNECTIVITY REQUEST

–

2a2

Stop Wait_Timer.

–

–

–

2a3

Set L = L +1.

–

–

–

2a4

Check: Does the L>N?

(NOTE 1)

–

–

F

2b1

Check: Does Wait_Timer expire?

(NOTE 2)

–

–

F

NOTE 1: The SS shall raise a fail verdict when there are more PDN CONNECTIVITY REQUEST messages received than expected (L>N) and terminate the test. The reason for such a behaviour can be e.g. wrongly set PICS with which the ExpectedNumberOfNewPDNConnections was initiated,

NOTE 2: Unless this is specified explicitly otherwise, e.g. in a test procedure which calls the procedure specified in the present table, the SS shall raise a fail verdict when there are less PDN CONNECTIVITY REQUEST messages than expected received at this point (note that when this procedure is called from the main behaviour K < N). The reason for such a behaviour can be e.g. wrongly set PICS with which the ExpectedNumberOfNewPDNConnections was initiated.

Information Element

Value/Remark

Comment

Condition

Access point name

Not present or One of the provided APN(s) in the Table 4.8.4-1

If present, the SS shall initialise the APN_Default=False

If not present NOTE 2

NOTE 1: Unless explicitly specified otherwise, the SS uses the Access point name value to address the entry of Table 4.8.4-1 to be used for the subsequent signalling of the PDN connectivity establishment and verifying specific UE behaviour e.g. depending on the type of the APN the UE may perform some actions.

NOTE 2: The SS uses pc_APN_Default_Configuration to address the entry of Table 4.8.4-1 to be used for the subsequent signalling of the PDN connectivity establishment.

Information Element

Value/Remark

Comment

Condition

EPS QoS

The EPC default bearer context of the entry in Table 4.8.4-1 which has been determined at step 1

Access point name

IF the UE provided an Access point name in step 1 THEN the SS returns this name;

OTHERWISE the SS includes the DNN/APN ID value of the entry in Table 4.8.4-1 which has been determined at step 1.

Container ID n+3

‘001C’H

Length of container ID n+3 contents

Container ID n+3 contents

5GC QoS rule of the entry in Table 4.8.4-1 which has been determined at step 1

Container ID n+4

‘001F’H

Length of container ID n+4 contents

Container ID n+4 contents

As per the relevant QoS rule (Container ID n+3)

ExpectedNumberOfPDUSessionModifications

Usage: Parameter determining procedure sequence.

A value for this parameter shall be provided when the procedure is called.

Unless the test requires specific number of PDU modifications to take place the value should be set to pc_noOf_PDNsSameConnection + pc_noOf_PDNsNewConnection +1 ([19]).

Meaning: The number of PDU sessions which are expected to happen. Depends on the UE configuration and/or the context in which the procedure is used.

K

Usage: Parameter determining procedure sequence.

Meaning: The number of PDN SESSION MODIFICATION REQUEST messages already processed including the one that is currently being processed.

L

Usage: Parameter determining procedure sequence.

Meaning: The number of PDN SESSION MODIFICATION REQUEST being received so far.

N

Usage: Parameter determining procedure sequence.

The parameter is initialised with the value of ExpectedNumberOfPDUSessionModifications

Meaning: Loop (step sequence repetition) control.

U – S

Message

0

Set K = 0, L = 0,

N = (ExpectedNumberOfPDUSessionModifications).

–

–

–

1

The procedure specified in Table 4.5A.2C.2.2-2 takes place.

–

–

–

2

Set K = K +1.

–

–

–

–

EXCEPTION: In parallel to the events described in steps 3-5a1 below the events specified in Table 4.5A.2C.2.2-2 may take place.

–

–

–

3

The SS transmits a RRCReconfiguration message and a PDU SESSION MODIFICATION COMMAND.

<–

NR RRC: RRCReconfiguration

5GMM: DL NAS TRANSPORT

5GSM: PDU SESSION MODIFICATION COMMAND

–

–

EXCEPTION: Depending upon UE implementation, step 4 and 4A can occur in any order

–

–

–

4

The UE transmits a RRCReconfigurationComplete message.

–>

NR RRC: RRCReconfigurationComplete

–

4A

The UE transmits a PDU SESSION MODIFICATION COMPLETE message.

–>

5GMM: UL NAS TRANSPORT

5GSM: PDU SESSION MODIFICATION COMPLETE

–

EXCEPTION: Steps 5a1 to 5b1 describe behaviour depending UE implementation; the "lower case letter" identifies a step sequence that take place if the UE performs a specific action.

–

–

–

5a1

IF L > K (NOTE 1) THEN repeat from step 2.

–

–

–

5b1

ELSE IF K < N (NOTE 2) THEN repeat from step 1.

–

–

–

NOTE 1: One (or more) further PDU SESSION MODIFICATION REQUEST message has been received in parallel.

NOTE 2: Less PDU SESSION MODIFICATION REQUEST messages than expected have been received and processed so far -> Further request are expected from the UE.

U – S

Message

1

Start Wait_Timer = 8 sec.

NOTE: 8s were chosen to cater for T3540 being set to 10s.

–

–

–

–

EXCEPTION: Steps 2a1 to 2b1 describe behaviour depending UE implementation; the "lower case letter" identifies a step sequence that take place if the UE performs a specific action.

–

–

–

2a1

The UE transmits an ULInformationTransfer message and a PDU SESSION MODIFICATION REQUEST with PDU session ID which has been associated with a default EPS bearer set up during the UE operation in S1.

–>

NR RRC: ULInformationTransfer

5GSM: PDU SESSION MODIFICATION REQUEST

–

2a2

Stop Wait_Timer.

–

–

–

2a3

Set L = L +1.

–

–

–

2a4

Check: Does the L>N?

(NOTE 1)

–

–

F

2b1

Check: Does Wait_Timer expire?

(NOTE 2)

–

–

F

NOTE 1: The SS shall raise a fail verdict when there are more PDU SESSION MODIFICATION REQUEST messages received than expected and terminate the test. The reason for such a behaviour can be e.g. wrongly set PICS with which the ExpectedNumberOfNewPDNConnections was initiated.

NOTE 2: Unless this is specified explicitly otherwise e.g. in a test procedure which calls the procedure specified in the present table, the SS shall raise a fail verdict when there are less PDU SESSION MODIFICATION REQUEST messages than expected received at this point and terminate the test. The reason for such a behaviour can be e.g. wrongly set PICS with which the ExpectedNumberOfNewPDUSessions was initiated,

Information Element

Value/remark

Comment

Condition

Request type

‘101’B

"modification request"

Information Element

Value/remark

Comment

Condition

PDU session ID

The PDU session ID associated with the default EPS bearer of the PDN connection which is being transferred into PDU session and for which the UE needs to indicate its capabilities via the modification procedure.

(NOTE 1)

5GSM capability

Present. Contents not checked.

Integrity protection maximum data rate

Present. Contents not checked.

NOTE 1: The PDU session ID was provided in the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT when the UE attached in S1. If the UE provides here an unknown PDU session ID then the SS shall set an Inconclusive verdict.

Information Element

Value/remark

Comment

Condition

RRCReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

rrcReconfiguration ::= SEQUENCE {

radioBearerConfig

RadioBearerConfig with conditions SRB2 and DRB2

NOT IMS_PDU

nonCriticalExtension SEQUENCE {

masterCellGroup

CellGroupConfig with condition SRB2_DRB2

NOT IMS_PDU

}

}

}

}

Information Element

Value/remark

Comment

Condition

RRCReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

rrcReconfiguration ::= SEQUENCE {

radioBearerConfig

RadioBearerConfig with condition DRBn

n is chosen as the next available number higher or equal to 2

RadioBearerConfig with condition DRB1

IMS_PDU

nonCriticalExtension SEQUENCE {

masterCellGroup

CellGroupConfig with condition DRBn

n is set to the same value as for the radioBearerConfig IE above

CellGroupConfig with condition DRB1

IMS_PDU

}

}

}

}

U – S

Message

–

EXCEPTION: Step 1 below and Step 1 in Table 4.5A.3.2.2-2 describe behaviour that depends on the contents of the latest PDU SESSION ESTABLISHMENT REQUEST message sent by the UE prior to this procedure.

–

–

–

EXCEPTION: In parallel to the event described in step 1 below the step specified in Table 4.5A.3.2.2-2 may take place.

–

–

1

If the "PDU session type" in the latest PDU SESSION ESTABLISHMENT REQUEST message prior to this procedure was ‘IPv4’ or ‘IPv4v6’ then, IPv4 address allocation by DHCPv4 may occur on the user plane bearer established for the QoS flow of the default QoS rule.

–

–

U – S

Message

1

If the "PDU session type" in the latest PDU SESSION ESTABLISHMENT REQUEST message prior to this procedure was ‘IPv6’ or ‘IPv4v6’ then stateless address auto configuration occurs on the user plane bearer established for the QoS flow of the default QoS rule.

–

–

U – S

Message

–

EXCEPTION: Steps 1a1 to 1a2b1 describe a transaction that depends on the UE capability

–

–

1a1

IF pc_IMS_5GS then the SS starts timer Timer_1 = 10 s (Note 1)

–

–

–

EXCEPTION: Steps 1a2a1 to 1a2b1 describe a transaction that depends on the UE implementation

–

–

1a2a1-1a2a8

Registration procedure according TS 34.229-5 [47] subclause A.2 (steps 1-8).

Note: SS cancels timer Timer_1 at step 1a2a1

–

–

1a2b1

Timer_1 expires

–

–

U – S

Message

1

The SS initiated disconnection from the existing IPsec tunnel as defined in TS 24.502 [35] clause 7.4.2

–

–

NOTE: It is assumed that the WLAN AP association remains throughout the procedure.

U – S

Message

–

Exception: In parallel to steps 1 to 2, the UE initiates an IPsec security association and one child security association as defined in TS 24.502 [35] clause 7.3.2

–

–

1

The UE transmits a SERVICE REQUEST message.

–>

5GMM: SERVICE REQUEST

2

The SS transmits a SERVICE Accept message.

<–

5GMM: SERVICE ACCEPT

Information Element

Value/remark

Comment

Condition

Service type

Service type value

‘0000’B

signalling