4.5 Generic procedures

38.508-13GPP5GSPart 1: Common test environmentRelease 17TSUser Equipment (UE) conformance specification

4.5.1 General

The generic procedures are used by test cases to get UE under test into SWITCHED_OFF, RRC_IDLE/Ipsec SA not established, RRC_INACTIVE, RRC_CONNECTED/Ipsec SA or Out of Coverage established state.

A test case controls the SS by specifying the required RRC state and a set of generic procedure parameters applicable for the intended testing.

The connectivity values EN-DC and E-UTRA/EPC are both a UE connected to the EPC. The connectivity values E-UTRA/5GC, NR, NGEN-DC, NE-DC and NR-DC are all a UE connected to the 5GC.

Table 4.5.1-1: Generic procedure parameters

Parameter

Values

Description

Parameter condition

Connectivity

E-UTRA/5GC

E-UTRA connected to 5GC

Mandatory.

For value NR see note 1.

NR

NR connected to 5GC

EN-DC

E-UTRA-NR Dual Connectivity with E-UTRA connected to EPC

NGEN-DC

E-UTRA-NR Dual Connectivity with E-UTRA connected to 5GC

NE-DC

NR E-UTRA Dual Connectivity

NR-DC

NR-NR Dual Connectivity

WLAN

Un trusted non 3GPP access over WLAN

E-UTRA/EPC

E-UTRA connected to EPC

Bearers

MCG(s) and SCG

MCG and SCG

Mandatory when Connectivity is set to EN-DC, NGEN-DC, NE-DC and NR-DC and when the generic procedures are used by test cases to get UE under test into RRC_CONNECTED state.

s=1 if MULTI_PDN= FALSE and s=2 if MULTI_PDN=TRUE.

N/A otherwise.

MCG(s) and split

MCG and split

Test Mode

On

UE test mode active as specified in TS 38.509 [11], clause 5.2.2.

Optional

Test Loop Function

On

UE test mode active with one of the UE test loop modes activated as specified in TS 38.509 [11], clauses 5.2.2 and 5.3.2.

Optional

Connected without release

On

Enter RRC_Connected with Ipsec_SA_Established and without any release.

Optional

N/A for NR-DC.

Interworking without N26 interface supported

On

The NWK sets the REGISTRATION ACCEPT message, IE 5GS network feature support, IWK N26 (octet 3, bit 7) = 1

Optional,

Depends on test case scenario. Default message content for REGISTRATION ACCEPT is set to Interworking without N26 interface NOT supported

Unrestricted nr PDN

On

Allow unrestricted numbers of PDNs.

Optional for Connectivity E-UTRA/EPC.

N/A otherwise.

Sidelink

On

NR sidelink

Optional

Cast type

Unicast

To establish unicast sidelink and PC5-RRC connection.

Optional

GNSS Sync

On

To use GNSS as the synchronization reference source.

Optional

SL MIMO

On

To transmit PSSCH with 2 spatial layers, i.e. SL MIMO

Optional

Note 1: The TS 38.331 [6] abbreviation for NR connected to 5GC is NR/5GC.

Editor’s Note: The following values are not available to use in the current version of this specification because details are still FFS: Connectivity (E-UTRA/5GC and NGEN-DC).

4.5.2 RRC_IDLE

4.5.2.1 Initiation

The SS shall:

1> if connectivity is EN-DC:

2> use 1 E-UTRA cell and 1 NR cell, default parameters;

2> if connected without release is not present:

3> perform according to the table 4.5.2.2-1: E-UTRA RRC_IDLE;

1> if connectivity is E-UTRA/EPC:

2> use 1 E-UTRA cell, default parameters;

2> if unrestricted nr PDN is not present:

3> perform according to the table 4.5.2.2-1: E-UTRA RRC_IDLE;

2> else:

3> perform according to the table 4.5.2.2-5: E-UTRA RRC_IDLE Unrestricted nr PDN:

3> if pc_noOf_PDNsNewConnection > 0:

4> perform according to the table 4.5.2.2-6: E-UTRA RRC_IDLE Unrestricted nr PDN Extension;

1> if connectivity is NR:

2> use 1 NR cell, default parameters;

2> if sidelink is On

3> use 1 NR-SS-UE;

3> if GNSS Sync is On

4> use 1 GNSS simulator.

2> perform according to the table 4.5.2.2-2: NR RRC_IDLE;

2> if pc_noOf_PDUsNewConnection > 0

3> perform according to the table 4.5.2.2-4: NR RRC_IDLE Extension;

1> if connectivity is WLAN:

2> use 1 WLAN cell, default parameters;

2> if connected without release is not present:

3> perform according to the table 4.5.2.2-3: WLAN Ipsec_SA_Released;

2> else:

3> Not defined:

1> if connectivity is NR-DC:

2> use 2 NR cells, default parameters;

2> perform according to the table 4.5.2.2-2: NR RRC_IDLE.

1> if connectivity is NE-DC:

2> use 1 E-UTRA cell and 1 NR cell, default parameters;

2> perform according to the table 4.5.2.2-2: NR RRC_IDLE.

4.5.2.2 Procedures

Table 4.5.2.2-1: E-UTRA RRC_IDLE

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-9a2

Same as TS 36.508 [2] table 4.5.2.3-1, steps 1-9a2.

EXCEPTION: Steps 10a1 to 10b8 describe behaviour which depends on procedure parameters; the "lower case letter" identifies a step sequence that take place if a procedure parameter has a particular value.

10a1-10a10

IF Test Mode = On OR Test Loop Function = On THEN steps 10-19 as defined in TS 36.508 [2] table 4.5.2A.3-1, are performed.

The ACTIVATE TEST MODE is using the associated condition for the test loop.

10b1-10b8

ELSE steps 10-17 as defined in TS 36.508 [2], table 4.5.2.3-1 are performed.

Table 4.5.2.2-2: NR RRC_IDLE

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

<–

NR RRC: SYSTEM INFORMATION (BCCH)

2

The UE transmits an RRCSetupRequest message.

–>

NR RRC: RRCSetupRequest

3

The SS transmits an RRCSetup message.

<–

NR RRC: RRCSetup

4

The UE transmits an RRCSetupComplete message and a REGISTRATION REQUEST message.

–>

NR RRC: RRCSetupComplete

5GMM: REGISTRATION REQUEST

5

The SS transmits a DLInformationTransfer message and an AUTHENTICATION REQUEST message.

<–

NR RRC: DLInformationTransfer

5GMM: AUTHENTICATION REQUEST

6

The UE transmits an ULInformationTransfer message and an AUTHENTICATION RESPONSE message.

–>

NR RRC: ULInformationTransfer

5GMM: AUTHENTICATION RESPONSE

7

Void

8

The SS transmits a DLInformationTransfer message and a SECURITY MODE COMMAND message.

<–

NR RRC: DLInformationTransfer

5GMM: SECURITY MODE COMMAND

9

The UE transmits an ULInformationTransfer message and a SECURITY MODE COMPLETE message.

–>

NR RRC: ULInformationTransfer

5GMM: SECURITY MODE COMPLETE

EXCEPTION: Step 9Aa1 to 9Aa2 describes behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported and the procedure parameter Interworking without N26 interface supported is not present.

9Aa1

IF UE_S1_SUPPORTED the SS transmits a DLInformationTransfer message and a SECURITY MODE COMMAND message.

<–

NR RRC: DLInformationTransfer

5GMM: SECURITY MODE COMMAND

9Aa2

The UE transmits an ULInformationTransfer message and a SECURITY MODE COMPLETE message.

–>

NR RRC: ULInformationTransfer

5GMM: SECURITY MODE COMPLETE

EXCEPTION: Steps 9a1 to 9a2 describe the SS sequence depending on procedure parameters; the "lower case letter" identifies a step sequence that take place if a procedure parameter has a particular value

9a1

IF Test Mode = On OR Test Loop Function = On, the SS transmits an ACTIVATE TEST MODE message to activate UE radio bearer test mode procedure. The ACTIVATE TEST MODE message is using the associated condition for the test loop.

<–

RRC: DLInformationTransfer

TC: ACTIVATE TEST MODE

9a2

The UE transmits an ACTIVATE TEST MODE COMPLETE message.

–>

RRC: ULInformationTransfer

TC: ACTIVATE TEST MODE COMPLETE

10

The SS transmits a SecurityModeCommand message.

<–

NR RRC: SecurityModeCommand

11

The UE transmits a SecurityModeComplete message.

–>

NR RRC: SecurityModeComplete

12

The SS transmits a UECapabilityEnquiry message.

<–

NR RRC: UECapabilityEnquiry

13

The UE transmits a UECapabilityInformation message.

–>

NR RRC: UECapabilityInformation

14

The SS transmits a DLInformationTransfer message and a REGISTRATION ACCEPT message.

<–

NR RRC: DLInformationTransfer

5GMM: REGISTRATION ACCEPT

15

The UE transmits an ULInformationTransfer message and a REGISTRATION COMPLETE message.

–>

NR RRC: ULInformationTransfer

5GMM: REGISTRATION COMPLETE

16

Void

17

Void

18

Void

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

19a1

IF pc_noOf_PDUsSameConnection > 0 THEN the generic procedure for UE-requested PDU session establishment, specified in subclause 4.5A.2, takes place performing establishment of UE-requested PDU session(s) with ExpectedNumberOfNewPDUSessions = pc_noOf_PDUsSameConnection.

EXCEPTION: Steps 19Aa1 to 19Aa2 describe behaviour which depends on the SS sequence depending on procedure parameters; the "lower case letter" identifies a step sequence that take place if a procedure parameter has a particular value.

19Aa1

IF connected without release is On AND Test Loop Function=On AND pc_noOf_PDUsNewConnection=0 THEN the SS transmits a CLOSE UE TEST LOOP message to enter the UE test loop mode. The CLOSE UE TEST LOOP is using the associated condition for the test loop.

<–

NR RRC: DLInformationTransfer

TC: CLOSE UE TEST LOOP

19Aa2

The UE transmits a CLOSE UE TEST LOOP COMPLETE message to confirm that loopback entities for the radio bearer(s) have been created and loop back is activated.

–>

NR RRC: ULInformationTransfer

TC: CLOSE UE TEST LOOP COMPLETE

EXCEPTION: Step 20a1 depends on the SS sequence depending on procedure parameters; the "lower case letter" identifies a step sequence that take place if a procedure parameter has a particular value.

20a1

IF connected without release is not present THEN, the SS transmits an RRCRelease message.

<–

NR RRC: RRCRelease

EXCEPTION: Step 20Aa1 depends on the SS sequence depending on procedure parameters; the "lower case letter" identifies a step sequence that take place if a procedure parameter has a particular value.

20Aa1

IF GNSS Sync = On THEN trigger UE to reset or clear the current UTC time that has been calculated from GNSS.

NOTE: The UTC time can be reset or clear on the UE using AT command (+CUTCR).

EXCEPTION: Step 21a1 and 21b1 depend on the SS sequence depending on procedure parameters; the "lower case letter" identifies a step sequence that take place if a procedure parameter has a particular value.

21a1

IF Sidelink = On AND Cast type = Unicast AND UE initiated unicast mode NR sidelink comunication THEN generic procedure specified in subclause 4.9.22 is performed to establish unicast mode sidelink communication between the UE and the NR-SS-UE.

21b1

ELSE IF Sidelink = On AND Cast type = Unicast AND NR-SS-UE initiated unicast mode NR sidelink comunication THEN generic procedure specified in subclause 4.9.23 is performed to establish unicast mode sidelink communication between the UE and the NR-SS-UE.

22a1

Void

Table 4.5.2.2-3: WLAN Ipsec_SA_Released

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The UE associates with the WLAN AP and obtains the local IP address.

2

The UE performs a dynamic selection of N3IWF using DNS query

Exception: The UE establishes an IPsec tunnel in parallel to 5GC registration steps 3 to 7 as per the IKEv2 protocol as defined in TS 23.502 [33] clause 4.12.2.2 figure 4.12.2.2-1.

3

The UE transmits a REGISTRATION REQUEST message.

–>

5GMM: REGISTRATION REQUEST

4

The SS transmits an AUTHENTICATION REQUEST message including EAP-Request/AKA’-Challenge or 5G AKA Challenge.

<–

5GMM: AUTHENTICATION REQUEST

5

The UE transmits an AUTHENTICATION RESPONSE message including EAP-Response/AKA’-Challenge or 5G AKA Response.

–>

5GMM: AUTHENTICATION RESPONSE

6

The SS transmits a SECURITY MODE COMMAND message including EAP-Success if EAP-AKA’ used.

<–

5GMM: SECURITY MODE COMMAND

7

The UE transmits a SECURITY MODE COMPLETE message.

–>

5GMM: SECURITY MODE COMPLETE

8

The SS transmits a REGISTRATION ACCEPT message.

<–

5GMM: REGISTRATION ACCEPT

9

The UE transmits a REGISTRATION COMPLETE message.

–>

5GMM: REGISTRATION COMPLETE

10

The generic procedure for UE-requested PDU session establishment, specified in subclause 4.5A.2A, takes place performing establishment of UE-requested PDU session.

EXCEPTION: Step 11a1 depends on the SS sequence depending on procedure parameters; the "lower case letter" identifies a step sequence that take place if a procedure parameter has a particular value.

11a1

IF connected without release is not present THEN generic procedure for SS-requested IPsec Secure tunnel disconnection, specified in subclause 4.5A.5, takes place performing disconnection of security association.

Note: The current procedure assumes UE establishes a single PDU session over Non 3GPP Access.

Table 4.5.2.2-4: NR RRC_IDLE Extension

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

0

Wait for 10 sec to allow the UE to start PDU session establishment automatically.

IF it does THEN stop the 10 sec timer and continue with the steps from step 2 onwards.

IF it does not and the 10 sec timer expires THEN go to step 1.

EXCEPTION: Step 1a1 and 1b1 depends on the status of the UE; the "lower case letter" identifies a step sequence that take place if a PDU connection is already active.

1a1

IF there is no PDU connection already active THEN Trigger the UE to perform PDU session establishment via AT or MMI command.

NOTE: For the DNN name in the AT command, check the default PDU type from the value the ICS parameter pc_APN_Default_Configuration and take the value of the corresponding ICS parameter. If it is set to ‘none’ then use pc_APN_ID_Internet.

1b1

ELSE skip the steps 2-9a1

2-6

Steps 2-6 from Table 4.5.4.2-3 are performed.

7

The SS transmits a SERVICE ACCEPT message.

<–

NR RRC: DLInformationTransfer

5GMM: SERVICE ACCEPT

8

The generic procedure for UE-requested PDU session establishment, specified in subclause 4.5A.2, takes place performing establishment of UE-requested PDU session(s) with ExpectedNumberOfNewPDUSessions = pc_noOf_PDUsNewConnection.

EXCEPTION: Steps 8Aa1 to 8Aa2 describe behaviour which depends on the SS sequence depending on procedure parameters; the "lower case letter" identifies a step sequence that take place if a procedure parameter has a particular value.

8Aa1

IF connected without release is On AND Test Loop Function=On THEN the SS transmits a CLOSE UE TEST LOOP message to enter the UE test loop mode. The CLOSE UE TEST LOOP is using the associated condition for the test loop.

<–

NR RRC: DLInformationTransfer

TC: CLOSE UE TEST LOOP

8Aa2

The UE transmits a CLOSE UE TEST LOOP COMPLETE message to confirm that loopback entities for the radio bearer(s) have been created and loop back is activated.

–>

NR RRC: ULInformationTransfer

TC: CLOSE UE TEST LOOP COMPLETE

EXCEPTION: Step 9a1 depends on the SS sequence depending on procedure parameters; the "lower case letter" identifies a step sequence that take place if a procedure parameter has a particular value.

9a1

IF connected without release is not present THEN, the SS transmits an RRCRelease message.

<–

NR RRC: RRCRelease

Table 4.5.2.2-5: E-UTRA RRC_IDLE Unrestricted nr PDN

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-9a2

Steps 1 to 9a2 of the generic procedure for UE Registration (State 2) as specified in TS 36.508 [2], table 4.5.2.3-1 take place.

EXCEPTION: Steps 10a1 to 10b8 describe behaviour which depends on procedure parameters; the "lower case letter" identifies a step sequence that take place if a procedure parameter has a particular value.

10a1-10a8

IF Test Mode = On OR Test Loop Function = On THEN steps 10-17 of the generic procedure for UE Registration, UE Test Mode Activated (State 2A) as specified in TS 36.508 [2] table 4.5.2A.3-1, take place.

The ACTIVATE TEST MODE is using the associated condition for the test loop.

10b1-10b6

ELSE steps 10-15 as defined in TS 36.508 [2], table 4.5.2.3-1 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 10A 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 10A below the relevant generic procedure for IMS signalling in the U-plane specified in Table 4.8.4-1 takes place.

10A

This message includes the ATTACH COMPLETE message. The ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message is piggybacked in ATTACH COMPLETE.

–>

RRC: ULInformationTransfer

NAS: ATTACH COMPLETE

NAS: ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT

11

The Generic Test Procedure to establish multiple additional PDN connections as specified in subclause 4.5A.2B takes place, ExpectedNumberOfNewPDNConnections=pc_noOf_PDNsSameConnection.

EXCEPTION: Steps 11Aa1 to 11Aa2 describe behaviour which depends on the SS sequence depending on procedure parameters; the "lower case letter" identifies a step sequence that take place if a procedure parameter has a particular value.

11Aa1

IF connected without release is On AND Test Loop Function=On AND pc_noOf_PDUsNewConnection =0 THEN the SS transmits a CLOSE UE TEST LOOP message to enter the UE test loop mode. The CLOSE UE TEST LOOP is using the associated condition for the test loop.

<–

RRC: DLInformationTransfer

TC: CLOSE UE TEST LOOP

11Aa2

The UE transmits a CLOSE UE TEST LOOP COMPLETE message to confirm that loopback entities for the radio bearer(s) have been created and loop back is activated.

–>

RRC: ULInformationTransfer

TC: CLOSE UE TEST LOOP COMPLETE

EXCEPTION: Step 12a1 depends on procedure parameters; the "lower case letter" identifies a step sequence that take place if a procedure parameter has a particular value.

12a1

IF connected without release is not present THEN, the SS transmits an RRCConnectionRelease message to release RRC connection and move to E-UTRA RRC_IDLE (State 2).

<–

RRC: RRCConnectionRelease

Table 4.5.2.2-6: E-UTRA RRC_IDLE Unrestricted nr PDN Extension

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

0

Wait for 10 sec to allow the UE to start PDN connection establishment automatically.

IF it does THEN stop the 10 sec timer and continue with the steps from step 2 onwards.

IF it does not and the 10 sec timer expires THEN go to step 1.

EXCEPTION: Step 1a1 and 1b1 depends on the status of the UE; the "lower case letter" identifies a step sequence that take place if a PDU connection is already active.

1a1

IF there is no PDN connection already active THEN Trigger the UE to perform PDN connection establishment via AT or MMI command.

NOTE: For the DNN name in the AT command, check the default PDU type from the value the ICS parameter pc_APN_Default_Configuration and take the value of the corresponding ICS parameter. If it is set to ‘none’ then use pc_APN_ID_Internet.

1b1

ELSE skip the steps 2-8a1

2-6

Steps 3 to 7 of the generic procedure specified in TS 36.508 [2], table 4.5.3.3-1 take place.

7

The Generic Test Procedure to establish multiple additional PDN connections as specified in subclause 4.5A.2B takes place, ExpectedNumberOfNewPDNConnections=pc_noOf_PDNsNewConnection.

EXCEPTION: Steps 7Aa1 to 7Aa2 describe behaviour which depends on the SS sequence depending on procedure parameters; the "lower case letter" identifies a step sequence that take place if a procedure parameter has a particular value.

7Aa1

IF connected without release is On AND Test Loop Function=On THEN the SS transmits a CLOSE UE TEST LOOP message to enter the UE test loop mode. The CLOSE UE TEST LOOP is using the associated condition for the test loop.

<–

RRC: DLInformationTransfer

TC: CLOSE UE TEST LOOP

7Aa2

The UE transmits a CLOSE UE TEST LOOP COMPLETE message to confirm that loopback entities for the radio bearer(s) have been created and loop back is activated.

–>

RRC: ULInformationTransfer

TC: CLOSE UE TEST LOOP COMPLETE

EXCEPTION: Step 18a1 depends on procedure parameters; the "lower case letter" identifies a step sequence that take place if a procedure parameter has a particular value.

8a1

IF connected without release is not present THEN, the SS transmits an RRCConnectionRelease message to release RRC connection and move to E-UTRA RRC_IDLE (State 2).

<–

RRC: RRCConnectionRelease

4.5.2.3 Specific message contents

All specific message contents shall be according clause 4.6 and 4.7 and TS 36.508 [2] clause 4.6 and 4.7 with the following exception(s).

Table 4.5.2.3-1: SECURITY MODE COMMAND (Step 9Aa1, Table 4.5.2.2-2)

Derivation path: Table 4.7.1-25 with condition UE_S1_SUPPORTED

Table 4.5.2.3-2: SERVICE REQUEST (Step 4, Table 4.5.2.2-4)

Derivation Path: Table 4.7.1-16.

Information Element

Value/remark

Comment

Condition

Service type

‘0000’B

signalling

Table 4.5.2.3-3: Message PDN CONNECTIVITY REQUEST (step 4, Table 4.5.2.2-5)

Derivation path: TS 36.508 [2], Table 4.7.3-20.

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.

Table 4.5.2.3-4: Message ESM INFORMATION RESPONSE (step 9a2, Table 4.5.2.2-5)

Derivation path: TS 36.508 [2], Table 4.7.3-14.

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.

Table 4.5.2.3-5: Message ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (Steps 10a5, 10b7, Table 4.5.2.2-5)

Derivation path: TS 36.508 [2], Table 4.7.3-6 with CONDITION Interworking_with_5GS.

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)

4.5.3 RRC_INACTIVE

4.5.3.1 Initiation

The SS shall:

1> if connectivity is NR

2> use 1 NR cell, default parameters;

2> perform according to the table 4.5.3.2-1: NR RRC_INACTIVE;

4.5.3.2 Procedures

Table 4.5.3.2-1: NR RRC_INACTIVE

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-19a1

Same as table 4.5.2.2-2, steps 1-19a1.

EXCEPTION: Steps 19Aa1-19Ab9 describes behaviour depending UE implementation; the "lower case letter" identifies a step sequence that take place if the UE performs a specific action.

19Aa1

IF pc_noOf_PDUsNewConnection = 0 AND Test Loop Function=On, table 4.5.2.2-2 steps 19Aa1-19Aa2 take place.

19 Ab1

IF pc_noOf_PDUsNewConnection > 0 THEN the SS transmits an RRCRelease message

<–

NR RRC: RRCRelease

19 Ab2-Ab9

Steps 1-8 of the NR RRC_IDLE extension procedure specified in table 4.5.2.2-4, take place.

20

The SS transmits an RRCRelease message with suspend.

<–

NR RRC: RRCRelease

4.5.4 RRC_CONNECTED

4.5.4.1 Initiation

The SS shall:

1> perform according to clause 4.5.2 RRC_IDLE;

1> if connectivity is EN-DC:

2> use 1 E-UTRA cell and 1 NR cell, default parameters;

2> if connected without release is On:

3> perform according to the table 4.5.4.2-2: RF E-UTRA RRC_CONNECTED;

2> else:

3> perform according to the table 4.5.4.2-1: E-UTRA RRC_CONNECTED;

1> if connectivity is E-UTRA/EPC:

2> use 1 E-UTRA cell, default parameters;

2> perform according to the table 4.5.4.2-1: E-UTRA RRC_CONNECTED;

1> if connectivity is NR:

2> use 1 NR cell, default parameters;

2> if sidelink is On

3> use 1 NR-SS-UE;

3> if GNSS Sync is On

4> use 1 GNSS simulator.

2> if connected without release is not present:

3> perform according to the table 4.5.4.2-3: NR RRC_CONNECTED;

1> if connectivity is WLAN:

2> use 1 WLAN cell, default parameters;

2> if connected without release is not present:

3> perform according to the table 4.5.4.2-4: WLAN IPsec_SA_Established;

2> else:

3> Not defined;

1> if connectivity is NR-DC:

2> use 2 NR cells, default parameters;

2> perform according to the table 4.5.4.2-5: NR-DC RRC_CONNECTED;

1> if connectivity is NE-DC:

2> use 1 E-UTRA cell and 1 NR cell, default parameters;

2> perform according to the table 4.5.4.2-6: NE-DC RRC_CONNECTED;

4.5.4.2 Procedures

Table 4.5.4.2-1: E-UTRA RRC_CONNECTED

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-6

Same as TS 36.508 [2] table 4.5.3.3-1, steps 2-7.

7

Same as TS 36.508 [2] table 4.5.3.3-1, step 8.

The RRCConnectionReconfiguration is using condition EN-DC_SRB2-DRB for connectivity EN-DC and bearers MCG(s) and SCG or connectivity E-UTRA/EPC. The RRCConnectionReconfiguration is using an associated condition MCG_and_SCG for bearers MCG(s) and SCG or condition MCG_and_split for bearers MCG(s) and split. For connectivity E-UTRA/EPC there’s no associated condition.

<–

RRC: RRCConnectionReconfiguration

NAS:

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

EXCEPTION: IF MCG(s) and SCG or MCG(s) and split. In parallel to steps 8-9 the UE performs a C-RNTI based Contention Based Random Access (CBRA) procedure on the NR cell.

8-9

Same as TS 36.508 [2] table 4.5.3.3-1, steps 9-10a1

10a1-10a2

IF Test Loop Function=On, same as TS 36.508 [2] table 4.5.4.3-1, steps 1-2.

The CLOSE UE TEST LOOP is using the associated condition for the test loop.

Table 4.5.4.2-2: RF E-UTRA RRC_CONNECTED

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-9

Same as table 4.5.2.2-1, steps 1-9.

10a1-10a2

IF Test Mode = On OR Test Loop Function = On THEN same as TS 36.508 [2] table 4.5.2A.3-1, steps 10-11.

The ACTIVATE TEST MODE is using the associated condition for the test loop.

EXCEPTION: Steps 11a1 to 11b8 describe the SS sequence depending on procedure parameters; the "lower case letter" identifies a step sequence that take place if a procedure parameter has a particular value.

11a1-11a8

IF Test Mode = On OR Test Loop Function = On THEN same as TS 36.508 [2] table 4.5.2A.3-1, steps 12-18.

11b1-11b8

ELSE, same as TS 36.508 [2] table 4.5.2.3-1, steps 10-16.

12

The SS transmits an RRCConnectionReconfiguration for connectivity EN-DC and bearers MCG(s) and SCG. The RRCConnectionReconfiguration is using an associated condition MCG_and_SCG for bearers MCG(s) and SCG or condition MCG_and_split for bearers MCG(s) and split.

<–

RRC: RRCConnectionReconfiguration

NAS:

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

EXCEPTION: In parallel to steps 13-14 the UE performs a C-RNTI based Contention Based Random Access (CBRA) procedure on the NR cell.

EXCEPTION: the steps 13 and 14 happen in any order.

13

The UE transmits an RRCConnectionReconfigurationComplete

–>

RRC: RRCConnectionReconfigurationComplete

14

The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message

–>

RRC: ULInformationTransfer

NAS: ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

15a1-15a2

IF Test Loop Function=On, same as TS 36.508 [2] table 4.5.4.3-1, steps 1-2.

The CLOSE UE TEST LOOP is using the associated condition for the test loop.

Table 4.5.4.2-3: NR RRC_CONNECTED

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits a Paging message.

<–

NR RRC: Paging

2

The UE transmits an RRCSetupRequest message.

–>

NR RRC: RRCSetupRequest

3

The SS transmits an RRCSetup message.

<–

NR RRC: RRCSetup

4

The UE transmits an RRCSetupComplete message and a SERVICE REQUEST message.

–>

NR RRC: RRCSetupComplete

5GMM: SERVICE REQUEST

5

The SS transmits a SecurityModeCommand message.

<–

NR RRC: SecurityModeCommand

6

The UE transmits a SecurityModeComplete message.

–>

NR RRC: SecurityModeComplete

7

The SS transmits an RRCReconfiguration message and a SERVICE ACCEPT message to establish SRB2 and DRB(s).

The RRCReconfiguration message is configured using RRCReconfiguration-SRB2-DRB(n, m) where n and m are the number of DRB(s) configured with RLC-AM and RLC-UM respectively.

<–

NR RRC: RRCReconfiguration

5GMM: SERVICE ACCEPT

8

The UE transmits an RRCReconfigurationComplete message.

–>

NR RRC: RRCReconfigurationComplete

EXCEPTION: Steps 9a1 to 9a2 describe behaviour which depends on the SS sequence depending on procedure parameters; the "lower case letter" identifies a step sequence that take place if a procedure parameter has a particular value.

9a1

IF Test Loop Function=On, the SS transmits a CLOSE UE TEST LOOP message to enter the UE test loop mode. The CLOSE UE TEST LOOP is using the associated condition for the test loop.

<–

NR RRC: DLInformationTransfer

TC: CLOSE UE TEST LOOP

9a2

The UE transmits a CLOSE UE TEST LOOP COMPLETE message to confirm that loopback entities for the radio bearer(s) have been created and loop back is activated.

–>

NR RRC: ULInformationTransfer

TC: CLOSE UE TEST LOOP COMPLETE

Table 4.5.4.2-4: WLAN IPsec_SA_Established

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Trigger UE to initiate IPSec SA.

2

The generic procedure for UE-requested IPsec Secure tunnel establishment, specified in subclause 4.5A.64, takes place performing establishment of security association and one child security association.

Table 4.5.4.2-5: NR-DC RRC_CONNECTED

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-8

Same as table 4.5.4.2-3, steps 1-8.

8A

The SS transmits an RRCReconfiguration message and a PDU SESSION MODIFICATION COMMAND to add a new SCG DRB or a new split DRB

<–

NR RRC: RRCReconfiguration
5GMM: DL NAS TRANSPORT
5GSM: PDU SESSION MODIFICATION COMMAND

EXCEPTION: In parallel to steps 8B and 8C the UE performs a C-RNTI based Contention Based Random Access (CBRA) procedure on the PSCell.

EXCEPTION: Depending upon UE implementation, step 8B and 8C can occur in any order

8B

The UE transmits an RRCReconfigurationComplete message including nr-SCG-Response.

–>

NR RRC: RRCReconfigurationComplete

8C

The UE transmits a ULInformationTransfer message and an PDU SESSION MODIFICATION COMPLETE message.

–>

NR RRC: ULInformationTransfer

5GMM: UL NAS TRANSPORT

5GSM: PDU SESSION MODIFICATION COMPLETE

EXCEPTION: Steps 9a1 to 9a2 describe behaviour which depends on the SS sequence depending on procedure parameters; the "lower case letter" identifies a step sequence that take place if a procedure parameter has a particular value.

9a1

IF Test Loop Function=On, the SS transmits a CLOSE UE TEST LOOP message to enter the UE test loop mode. The CLOSE UE TEST LOOP is using the associated condition for the test loop.

<–

NR RRC: DLInformationTransfer

TC: CLOSE UE TEST LOOP

9a2

The UE transmits a CLOSE UE TEST LOOP COMPLETE message to confirm that loopback entities for the radio bearer(s) have been created and loop back is activated.

–>

NR RRC: ULInformationTransfer

TC: CLOSE UE TEST LOOP COMPLETE

Table 4.5.4.2-6: NE-DC RRC_CONNECTED

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-8

Same as table 4.5.4.2-3, steps 1-8.

8A

The SS transmits an RRCReconfiguration message and a PDU SESSION MODIFICATION COMMAND to add a new SCG DRB or a new split DRB

<–

NR RRC: RRCReconfiguration
5GMM: DL NAS TRANSPORT
5GSM: PDU SESSION MODIFICATION COMMAND

EXCEPTION: In parallel to steps 8B and 8C the UE performs a C-RNTI based Contention Free Random Access (CFRA) procedure on the PSCell.

8B

The UE transmits an RRCReconfigurationComplete message including eutra-SCG-Response.

–>

NR RRC: RRCReconfigurationComplete

8C

The UE transmits a ULInformationTransfer message and an PDU SESSION MODIFICATION COMPLETE message.

–>

NR RRC: ULInformationTransfer

5GMM: UL NAS TRANSPORT

5GSM: PDU SESSION MODIFICATION COMPLETE

EXCEPTION: Steps 9a1 to 9a2 describe behaviour which depends on the SS sequence depending on procedure parameters; the "lower case letter" identifies a step sequence that take place if a procedure parameter has a particular value.

9a1

IF Test Loop Function=On, the SS transmits a CLOSE UE TEST LOOP message to enter the UE test loop mode. The CLOSE UE TEST LOOP is using the associated condition for the test loop.

<–

NR RRC: DLInformationTransfer

TC: CLOSE UE TEST LOOP

9a2

The UE transmits a CLOSE UE TEST LOOP COMPLETE message to confirm that loopback entities for the radio bearer(s) have been created and loop back is activated.

–>

NR RRC: ULInformationTransfer

TC: CLOSE UE TEST LOOP COMPLETE

4.5.4.3 Specific message contents

All specific message contents shall be according clause 4.6 and 4.7 and TS 36.508 [2] clause 4.6 and 4.7 with the exceptions below.

Table 4.5.4.3-0: RRCConnectionReconfiguration (step 7, Table 4.5.4.2-1)

Derivation Path: 36.508 table 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReconfiguration-r8 SEQUENCE {

dedicatedInfoNASList

Not present

no NAS message

dedicatedInfoNASList SEQUENCE (SIZE(1..maxDRB)) OF

1 entry

MCG_and_SCG OR MCG_and_split

dedicatedInfoNAS [1]

OCTET STRING including ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

according to table 4.5.4.3-1

}

}

}

}

Table 4.5.4.3-1: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST (step 7, Table 4.5.4.2-1)

Derivation path: TS 36.508 [2] Table 4.7.3-3

Information Element

Value/Remark

Comment

Condition

Linked EPS bearer identity

12

EPS QoS

According to reference dedicated EPS bearer context #6 – in TS 36.508 [2] table 6.6.2-1A

TFT

According to reference dedicated EPS bearer context #6 – in TS 36.508 [2] table 6.6.2-1A

Negotiated QoS

According to reference dedicated EPS bearer context #6 – in TS 36.508 [2] table 6.6.2-1A

Negotiated LLC SAPI

According to reference dedicated EPS bearer context #6 – in TS 36.508 [2] table 6.6.2-1A

Radio priority

According to reference dedicated EPS bearer context #6 – in TS 36.508 [2] table 6.6.2-1A

Protocol configuration options

According to reference dedicated EPS bearer context #6 – in TS 36.508 [2] table 6.6.2-1A

Extended protocol configuration options

According to reference dedicated EPS bearer context #6 – in TS 36.508 [2] table 6.6.2-1A

Table 4.5.4.3-1A: RRCConnectionReconfiguration (step 12, Table 4.5.4.2-2)

Derivation Path: 36.508 table 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReconfiguration-r8 SEQUENCE {

dedicatedInfoNASList SEQUENCE (SIZE(1..maxDRB)) OF

1 entry

dedicatedInfoNAS [1]

OCTET STRING including ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

according to table 4.5.4.3-1B

}

}

}

}

Table 4.5.4.3-1B: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST (step 12, Table 4.5.4.2-2)

Derivation path: TS 36.508 [2] Table 4.7.3-3

Information Element

Value/Remark

Comment

Condition

Linked EPS bearer identity

5

EPS QoS

According to reference dedicated EPS bearer context #6 – in TS 36.508 [2] table 6.6.2-1A

TFT

According to reference dedicated EPS bearer context #6 – in TS 36.508 [2] table 6.6.2-1A

Negotiated QoS

According to reference dedicated EPS bearer context #6 – in TS 36.508 [2] table 6.6.2-1A

Negotiated LLC SAPI

According to reference dedicated EPS bearer context #6 – in TS 36.508 [2] table 6.6.2-1A

Radio priority

According to reference dedicated EPS bearer context #6 – in TS 36.508 [2] table 6.6.2-1A

Protocol configuration options

According to reference dedicated EPS bearer context #6 – in TS 36.508 [2] table 6.6.2-1A

Extended protocol configuration options

According to reference dedicated EPS bearer context #6 – in TS 36.508 [2] table 6.6.2-1A

Table 4.5.4.3-2: RRCReconfiguration (step 7, Table 4.5.4.2-3)

Derivation Path: TS 38.508-1, table 4.8.1-1B

Table 4.5.4.3-3: Void

Table 4.5.4.3-4: PDU SESSION MODIFICATION COMMAND (step 8A, Table 4.5.4.2-5 and Table 4.5.4.2-6)

Derivation Path: Table 4.7.2-9.

Information Element

Value/remark

Comment

Condition

PDU session ID

The same as the PDU session ID in PDU SESSION ESTABLISHMENT REQUEST associated with the Internet PDU session if available or with the first PDU session

Authorized QoS rules

One entry

QoS rule [1]

Reference QoS rule #5 as defined in Table 4.8.2.1-5.

QFI=5

Authorized QoS flow descriptions

One entry

QoS flow [1]

Reference QoS flow #5 as defined in Table 4.8.2.3-5.

QFI=5

Table 4.5.4.3-5: RRCReconfiguration (step 8A, Table 4.5.4.2-5)

Derivation Path: TS 38.508-1, table 4.8.1-1CA

Table 4.5.4.3-6: RRCReconfigurationComplete (step 8B, Table 4.5.4.2-5)

Derivation Path: TS 38.508-1, table 4.6.1-14 with condition NR-DC

Table 4.5.4.3-7: RRCReconfiguration (step 8A, Table 4.5.4.2-6)

Derivation Path: TS 38.508-1, table 4.8.1-1CB

Table 4.5.4.3-8: RRCReconfigurationComplete (step 8B, Table 4.5.4.2-6)

Derivation Path: TS 38.508-1, table 4.6.1-14 with condition NE-DC

4.5.5 SWITCHED_OFF

4.5.5.1 Initiation

The SS shall:

1> if Test State ID=0-A:

2> Do nothing;

1> else if Test State ID=0N-B:

2> use 1 NR cell, default parameters;

2> perform the procedure according to the table 4.5.5.2-1: NR SWITCHED_OFF_0_B;

1> else if Test State ID=0E-B:

2> FFS

NOTE: The procedure for State 0N-B is used as default.

4.5.5.2 Procedures

Table 4.5.5.2-1: NR SWITCHED_OFF_0N_B

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-20

Same as table 4.5.2.2-2, steps 1-20.

21-26

Same as table 4.9.6.1-1, steps 1a1-1b1

4.5.5.3 Specific message contents

All specific message contents shall be according clause 4.6 and 4.7.

NOTE: The procedure refers to default messages content. If a test case requires specific parameters to be set during the procedure e.g. list with ePLMNs or/and TAIs is stored, new or not 5G-GUTI, etc. then, this needs to be specified in the test case, which uses the procedure.

4.5.6 Void

4.5.7 Out of Coverage

4.5.7.1 Initiation

The SS shall:

1> If sidelink is On

2> use neither NR cell nor E-UTRA cell;

2> use 1 GNSS simulator;

2> use 1 NR-SS-UE;

2> perform the procedure according to the table 4.5.7.2-1: Out of Coverage (NR sidelink).

4.5.7.2 Procedures

Table 4.5.7.2-1: Out of Coverage (NR sidelink)

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: Steps 1a1 describe the SS sequence depending on procedure parameters; the "lower case letter" identifies a step sequence that take place if a procedure parameter has a particular value.

1a1

IF Test Mode = On OR Test Loop Function = On THEN the SS triggers UE to activate UE test mode E.

NOTE: The activation of UE test mode may be performed by MMI or AT command (+CATM).

1A

Trigger UE to reset or clear the current UTC time that has been calculated from GNSS.

NOTE: The UTC time can be reset or clear on the UE using AT command (+CUTCR).

EXCEPTION: Steps 2a1 and 2b1 describe the SS sequence depending on procedure parameters; the "lower case letter" identifies a step sequence that take place if a procedure parameter has a particular value.

2a1

IF Cast type = Unicast AND UE initiated unicast mode NR sidelink comunication THEN generic procedure specified in subclause 4.9.22 is performed to establish unicast mode sidelink communication between the UE and the NR-SS-UE.

2b1

ELSE IF Cast type = Unicast AND NR-SS-UE initiated unicast mode NR sidelink comunication THEN generic procedure specified in subclause 4.9.23 is performed to establish unicast mode sidelink communication between the UE and the NR-SS-UE.

EXCEPTION: Steps 3a1 and 3b1 describe the SS sequence depending on procedure parameters; the "lower case letter" identifies a step sequence that take place if a procedure parameter has a particular value.

3a1

IF Test Loop Function = On AND the NR-SS-UE is configured as transmitting UE THEN the SS triggers UE to close UE test loop mode E (Receive Mode).

NOTE: Closing of UE test loop mode E may be performed by MMI or AT command (+CCUTLE).

3b1

IF Test Loop Function = On AND NR-SS-UE is configured as receiving UE AND SL MIMO ≠ On THEN the SS triggers UE to close UE test loop mode E (Transmit Mode).

NOTE: Closing of UE test loop mode E may be performed by MMI or AT command (+CCUTLE).

3c1

IF Test Loop Function = On AND NR-SS-UE is configured as receiving UE AND SL MIMO = On THEN the SS triggers UE to close UE test loop mode E (Transmit Mode with SL-MIMO).

NOTE: Closing of UE test loop mode E may be performed by MMI or AT command (+CCUTLE).

4

Void

4.5.7.3 Specific message contents

All specific message contents shall be according subclause 4.7B with the exceptions below.

Table 4.5.7.3-1: +CATM (Table 4.5.7.2-1, Step 1a1)

Derivation Path: +CATM specified in subclause 4.7B with condition Activation

Table 4.5.7.3-2: +CCUTLE (Table 4.5.7.2-1, Step 3a1)

Derivation Path: Table 4.7B-1 with condition Close and Receive

Table 4.5.7.3-3: +CCUTLE (Table 4.5.7.2-1, Step 3b1)

Derivation Path: Table 4.7B-1 with condition Close and Transmit

Table 4.5.7.3-4: +CCUTLE (Table 4.5.7.2-1, Step 3c1)

Derivation Path: Table 4.7B-1 with condition Close, Transmit and SL_MIMO