7.1.4 SDAP

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

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

7.1.4.1 SDAP Data Transfer and PDU Header Handling UL/DL

7.1.4.1.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state with multiple DRB’s established, each mapping more than one QoS flow }

ensure that {

when { UE receives an SDAP PDU with SDAP header }

then { UE SDAP entity retrieves the SDAP SDU from the SDAP PDU and delivers it to upper layer }

}

(2)

with { UE in RRC_CONNECTED state with multiple DRB’s established configured with UL SDAP header, each mapping more than one QoS flow configured by RRC }

ensure that {

when { UE has to transmit a SDAP PDU with header to be included }

then {UE builds an SDAP PDU from the SDAP SDU including the header, and maps it to the DRB as per stored DRB mapping rule for the QoS flow }

}

(3)

with { UE in RRC_CONNECTED state with multiple DRB’s and QoS flows established }

ensure that {

when { UE receives a SDAP PDU with SDAP header and RDI fields set to 1 }

then { UE stores the QoS flow to DRB mapping of the DL SDAP PDU as the QoS flow to DRB mapping rule for the UL and uses it for further UL SDAP PDU transmissions }

}

(4)

with { UE in RRC_CONNECTED state with multiple DRB’s and QoS flows established }

ensure that {

when { UE receives a SDAP PDU with SDAP header and RDI field set to 1 and the stored QoS flow to DRB mapping rule for the QoS flow is different from the QoS flow to DRB mapping of the DL SDAP data PDU }

then { UE stores the QoS flow to DRB mapping of the DL SDAP PDU as the QoS flow to DRB mapping rule for the UL, to be used for further UL SDAP PDU transmissions and transmits an end-marker control PDU for the QoS flow on the old DRB }

}

(5)

with { UE in RRC_CONNECTED state with multiple DRB’s and QoS flows established with QoS flow to DRB mapping }

ensure that {

when { UE receives a message which configures a new QoS flow to DRB mapping, different from the existing mapping }

then { UE stores the QoS flow to DRB mapping to be used for further UL SDAP PDU transmissions and transmits an end-marker control PDU for the QoS flow on the old DRB }

}

7.1.4.1.2 Conformance requirements

References: The conformance requirements covered in the present test case are specified in: TS 37.324, clauses 5.2.1, 5.2.2, 5.3.1, 5.3.2, 6.2.2.1, 6.2.2.2, 6.2.2.3, 6.2.3 and 6.3.4, TS 24.501 clause 6.2.5.1.3. Unless otherwise stated these are Rel-15 requirements.

[TS 37.324 clause 5.2.1]

At the reception of an SDAP SDU from upper layer for a QoS flow, the transmitting SDAP entity shall:

– if there is no stored QoS flow to DRB mapping rule for the QoS flow as specified in the subclause 5.3:

– map the SDAP SDU to the default DRB;

– else:

– map the SDAP SDU to the DRB according to the stored QoS flow to DRB mapping rule;

– if the DRB to which the SDAP SDU is mapped is configured by RRC (3GPP TS 38.331 [3]) with the presence of SDAP header,

– construct the UL SDAP data PDU as specified in the subclause 6.2.2.3;

– else:

– construct the UL SDAP data PDU as specified in the subclause 6.2.2.1;

– submit the constructed UL SDAP data PDU to the lower layers.

NOTE 1: UE behaviour is not defined if there is neither a default DRB nor a stored QoS flow to DRB mapping rule for the QoS flow.

NOTE 2: Default DRB is always configured with UL SDAP header (3GPP TS 38.331 [3]).

[TS 37.324 clause 5.2.2]

At the reception of an SDAP data PDU from lower layers for a QoS flow, the receiving SDAP entity shall:

– if the DRB from which this SDAP data PDU is received is configured by RRC (3GPP TS 38.331 [3]) with the presence of SDAP header:

– perform reflective QoS flow to DRB mapping as specified in the subclause 5.3.2;

– perform RQI handling as specified in the subclause 5.4;

– retrieve the SDAP SDU from the DL SDAP data PDU as specified in the subclause 6.2.2.2.

– else:

– retrieve the SDAP SDU from the DL SDAP data PDU as specified in the subclause 6.2.2.1;

– deliver the retrieved SDAP SDU to the upper layer.

[TS 37.324 clause 5.3.1]

When RRC (3GPP TS 38.331 [3]) configures an UL QoS flow to DRB mapping rule for a QoS flow, the SDAP entity shall:

– if the SDAP entity has already been established and there is no stored QoS flow to DRB mapping rule for the QoS flow and a default DRB is configured:

– construct an end-marker control PDU, as specified in the subclause 6.2.3, for the QoS flow;

– map the end-marker control PDU to the default DRB;

– submit the end-marker control PDU to the lower layers.

– if the stored UL QoS flow to DRB mapping rule is different from the configured QoS flow to DRB mapping rule for the QoS flow and the DRB according to the stored QoS flow to DRB mapping rule is configured by RRC (3GPP TS 38.331 [3]) with the presence of UL SDAP header:

– construct an end-marker control PDU, as specified in the subclause 6.2.3, for the QoS flow;

– map the end-marker control PDU to the DRB according to the stored QoS flow to DRB mapping rule;

– submit the end-marker control PDU to the lower layers.

– store the configured UL QoS flow to DRB mapping rule for the QoS flow.

When RRC (3GPP TS 38.331 [3]) releases an UL QoS flow to DRB mapping rule for a QoS flow, the SDAP entity shall:

– remove the UL QoS flow to DRB mapping rule for the QoS flow.

[TS 37.324 clause 5.3.2]

For each received DL SDAP dataPDU with RDI set to 1, the SDAP entity shall:

– process the QFI field in the SDAP header and determine the QoS flow;

– if there is no stored QoS flow to DRB mapping rule for the QoS flow and a default DRB is configured:

– construct an end-marker control PDU, as specified in the subclause 6.2.3, for the QoS flow;

– map the end-marker control PDU to the default DRB;

– submit the end-marker control PDU to the lower layers;

– if the stored QoS flow to DRB mapping rule for the QoS flow is different from the QoS flow to DRB mapping of the DL SDAP data PDU and the DRB according to the stored QoS flow to DRB mapping rule is configured by RRC (3GPP TS 38.331 [3]) with the presence of UL SDAP header:

– construct an end-marker control PDU, as specified in the subclause 6.2.3, for the QoS flow;

– map the end-marker control PDU to the DRB according to the stored QoS flow to DRB mapping rule;

– submit the end-marker control PDU to the lower layers;

– store the QoS flow to DRB mapping of the DL SDAP data PDU as the QoS flow to DRB mapping rule for the UL.

[TS 37.324 clause 6.2.2.1]

An SDAP PDU consists only of a data field and does not consist of any SDAP header, as described in Figure 6.2.2.1-1.

Figure 6.2.2.1-1: SDAP Data PDU format without SDAP header

[TS 37.324 clause 6.2.2.2]

Figure 6.2.2.2 – 1 shows the format of SDAP Data PDU of DL with SDAP header being configured.

Figure 6.2.2.2-1: DL SDAP Data PDU format with SDAP header

[TS 37.324 clause 6.2.2.3]

Figure 6.2.2.3 – 1 shows the format of SDAP Data PDU of UL with SDAP header being configured.

Figure 6.2.2.3-1: UL SDAP Data PDU format with SDAP header

[TS 37.324 clause 6.2.3]

Figure 6.2.3 – 1 shows the format of End-Marker Control PDU.

Figure 6.2.2.3-1: UL SDAP Data PDU format with SDAP header

[TS 37.324 clause 6.3.4]

Length: 6 bits

The QFI field indicates the ID of the QoS flow (3GPP TS 23.501 [4]) to which the SDAP PDU belongs.

[TS 24.501 clause 6.2.5.1.3]

For PDU session of IPv4, IPv6, IPv4v6 or Ethernet PDU session type, upon receiving an UL user data packet from the upper layers for transmission via a PDU session, the UE shall attempt to associate the UL user data packet with:

a) the QFI of a signalled QoS rule associated with the PDU session which has a set of packet filters containing a packet filter for UL direction matching the UL user data packet or containing a packet filter for both UL and DL directions matching the UL user data packet; or

b) the QFI of a derived QoS rule associated with the PDU session which has the packet filter for UL direction matching the UL user data packet;

by evaluating the QoS rules in increasing order of their precedence values until the UL user data packet is associated with a QFI or all QoS rules are evaluated.

For PDU session of unstructured PDU session type, upon receiving an UL user data packet from the upper layers for transmission via a PDU session, the UE shall associate the UL user data packet with the QFI of the default QoS rule associated with the PDU session.

If the UL user data packet is associated with a QFI, the UE shall pass the QFI along the UL user data packet to the lower layers for transmission.

NOTE: Marking of the UL user data packet with the QFI is performed by the lower layers.

If all QoS rules are evaluated and the UL user data packet is not associated with a QFI, the UE shall discard the UL user data packet.

7.1.4.1.3 Test description

7.1.4.1.3.1 Pre-test conditions

System Simulator:

– NR Cell 1

UE:

– None.

Preamble:

– The UE is in 5GS state 3N-A with one PDU session active according to TS 38.508-1 [4], clause 4.4A.3, Table 4.4A.3-1 and using the message condition UE TEST LOOP MODE B active with IP PDU delay = 1 second, to return one SDAP SDU per DL SDAP SDU. 2 DRBs are configured where DRB j is defined as default DRB. The NAS QoS rules for the QoS flows with QFI=1, QFI=2, QFI=5 and QFI=6 are configured. QoS flows with QFI=5 and QFI=6 are mapped to DRB j, QoS flows with QFI=1 and QFI=2 are mapped to DRB k.

7.1.4.1.3.2 Test procedure sequence

Table 7.1.4.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS sends the SDAP Data PDU with SDAP header on DRB k and the following content to the UE: RDI=0. RQI=0, QFI=2.	<–	SDAP DL Data PDU	–	–
2	Check: Does the UE re-transmit SDAP Data PDU on DRB k with SDAP header as per the stored DRB mapping flow with QFI=2?	–>	SDAP UL Data PDU	1,2	P
2A	The SS transmits an OPEN UE TEST LOOP message.	<–	OPEN UE TEST LOOP	–	–
2B	The UE transmits an OPEN UE TEST LOOP COMPLETE message.	–>	OPEN UE TEST LOOP COMPLETE	–	–
2C	The SS transmits a CLOSE UE TEST LOOP Message with IP PDU delay = 1 second.	<–	CLOSE UE TEST LOOP	–	–
2D	The UE transmits a CLOSE UE TEST LOOP COMPLETE message.	–>	CLOSE UE TEST LOOP COMPLETE	–	–
3	The SS sends the SDAP Data PDU with SDAP header on DRB k and the following content to the UE: RDI=1, RQI=0, QFI=5.	<–	SDAP DL Data PDU	–	–
–	EXCEPTION: In parallel to the event described in step 4 the events specified in Table 7.1.4.1.3.2-2 shall take place.	–	–	–	–
4	Check: Does the UE re-transmit SDAP Data PDU on DRB k with SDAP header as per the stored DRB mapping Flow with QFI=5?	–>	SDAP UL Data PDU	3	P
4A	The SS transmits an OPEN UE TEST LOOP message.	<–	OPEN UE TEST LOOP	–	–
4B	The UE transmits an OPEN UE TEST LOOP COMPLETE message.	–>	OPEN UE TEST LOOP COMPLETE	–	–
4C	The SS transmits a CLOSE UE TEST LOOP Message with IP PDU delay = 1 second.	<–	CLOSE UE TEST LOOP	–	–
4D	The UE transmits a CLOSE UE TEST LOOP COMPLETE message.	–>	CLOSE UE TEST LOOP COMPLETE	–	–
5	The SS transmits an RRCReconfiguration message including a PDU SESSION MODIFICATION COMMAND	<–	RRCReconfiguration (PDU SESSION MODIFICATION COMMAND)	–	–
–	EXCEPTION: In parallel to the event described in step 6 the events specified in Tables 7.1.4.1.3.2-3 and 7.1.4.1.3.2-4 shall take place.	–	–	–	–
6	The UE transmits an RRCReconfigurationComplete message.	–>	RRCReconfigurationComplete	–	–
7	The SS sends the SDAP Data PDU with SDAP header on DRB k and the following content to the UE: RDI=0. RQI=0, QFI=4.	<–	SDAP DL Data PDU	–	–
8	Check: Does the UE re-transmit SDAP Data PDU on DRB k with SDAP header as per the stored DRB mapping Flow with QFI=4?	–>	SDAP UL Data PDU	5	P

Table 7.1.4.1.3.2-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Check: Does the UE transmit End-Marker Control PDU on DRB j for QFI=5?	–>	SDAP UL Control PDU	4	P

Table 7.1.4.1.3.2-3: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Check: Does the UE transmit End-Marker Control PDU on DRB j for QFI=4?	–>	SDAP UL Control PDU	5	P

Table 7.1.4.1.3.2-4: Parallel behaviour

Procedure

Message Sequence

Verdict

U – S

Message

The UE Transmits PDU SESSION MODIFICATION COMPLETE

–>

ULInformationTransfer

(PDU SESSION MODIFICATION COMPLETE)

–

7.1.4.1.3.3 Specific message contents

Table 7.1.4.1.3.3-1: RadioBearerConfig-DRB (Preamble)

Derivation Path: TS 38.508-1 [4], table 4.6.3-132 and condition NR
Information Element	Value/remark	Comment	Condition
RadioBearerConfig ::= SEQUENCE {
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) OF DRB-ToAddMod {	2 entries
DRB-ToAddMod[1] SEQUENCE {		entry 1
cnAssociation CHOICE {
sdap-Config SEQUENCE {
pdu-Session	The same as the PDU session ID in PDU SESSION ESTABLISHMENT REQUEST
sdap-HeaderDL	present
sdap-HeaderUL	present
defaultDRB	false
mappedQoS-FlowsToAdd SEQUENCE {
QFI	1
QFI	2
}
}
}
drb-Identity	k	k is allocated according to internal TTCN mapping
}
DRB-ToAddMod[2] SEQUENCE {		entry 2
cnAssociation CHOICE {
sdap-Config SEQUENCE {
pdu-Session	The same as the PDU session ID in PDU SESSION ESTABLISHMENT REQUEST
sdap-HeaderDL	present
sdap-HeaderUL	present
defaultDRB	true
mappedQoS-FlowsToAdd SEQUENCE {
QFI	5
QFI	6
}
}
}
}
drb-Identity	j	j is allocated according to internal TTCN mapping
}
}
}

Table 7.1.4.1.3.3-2: RadioBearerConfig-DRB (step 5, Table 7.1.4.1.3.2-1)

Derivation Path: TS 38.508-1 [4], table 4.6.3-132 and condition NR
Information Element	Value/remark	Comment	Condition
RadioBearerConfig ::= SEQUENCE {	–	–
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) OF DRB-ToAddMod {	1 entry	BID is the total number of established DRBs in the UE, before applying the contents of this IE
DRB-ToAddMod[1] SEQUENCE {		entry 1
cnAssociation CHOICE {
sdap-Config SEQUENCE {
pdu-Session	The same as the PDU session ID in PDU SESSION ESTABLISHMENT REQUEST
sdap-HeaderDL	present
sdap-HeaderUL	present
defaultDRB	false
mappedQoS-FlowsToAdd SEQUENCE {
QFI	4
}
}
drb-Identity	k	k is allocated according to internal TTCN mapping
}
}
}
}

Table 7.1.4.1.3.3-3: PDU SESSION MODIFICATION COMMAND (step 5, Table 7.1.4.1.3.2-1)

Derivation Path: TS 38.508-1 [4], 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
Authorized QoS rules	1 entry
QoS rule [1]	Reference QoS rule #4a as defined in TS 38.508-1 [4], Table 4.8.2.1-4a.	QFI=4
Authorized QoS flow descriptions	1 entry
QoS flow [1]	Reference QoS flow #2a as defined in TS 38.508-1 [4], Table 4.8.2.3-2a.	QFI=4

Table 7.1.4.1.3.3-4: PDU SESSION ESTABLISHMENT ACCEPT (Preamble)

Derivation Path: TS 38.508-1 [4], table 4.7.2-2
Information Element	Value/remark	Comment	Condition
PDU session ID	The same as the PDU session ID in PDU SESSION ESTABLISHMENT REQUEST
Authorized QoS rules	4 entries
QoS rule [1]	Reference QoS rule #1 as defined in TS 38.508-1 [4], Table 4.8.2.1-1	QFI=1
QoS rule [2]	Reference QoS rule #4 as defined in Table 7.1.4.1.3.3-7	QFI=2
QoS rule [3]	Reference QoS rule #5 as defined in TS 38.508-1 [4], Table 4.8.2.1-5	QFI=5
QoS rule [4]	Reference QoS rule #6 as defined in TS 38.508-1 [4], Table 4.8.2.1-6	QFI=6
Mapped EPS Bearer contexts	Not Present
Authorized QoS flow descriptions	4 entries
QoS flow [1]	Reference QoS flow #1 as defined in Table 7.1.4.1.3.3-5	QFI=1
QoS flow [2]	Reference QoS flow #2 as defined in Table 7.1.4.1.3.3-6	QFI=2
QoS flow [3]	Reference QoS flow #3 as defined in TS 38.508-1 [4], Table 4.8.2.3-3	QFI=5
QoS flow [4]	Reference QoS flow #4 as defined in TS 38.508-1 [4], Table 4.8.2.3-4	QFI=6

Table 7.1.4.1.3.3-5: Reference QoS flow #1 (Preamble)

Derivation Path: TS 38.508-1 [4], table 4.8.2.3-1
Information Element	Value/remark	Comment	Condition
QoS flow descriptions
QoS flow description	1 entry
QFI	‘00 0001’B	QFI 1
Operation code	‘001’B	Create new QoS flow description
E bit	‘1’B	Parameters list is included
Number of parameters	’00 0001’B	1 parameter
5QI	‘0000 1001’B	5QI 9

Table 7.1.4.1.3.3-6: Reference QoS flow #2 (Preamble)

Derivation Path: TS 38.508-1 [4], table 4.8.2.3-2
Information Element	Value/remark	Comment	Condition
QoS flow descriptions
QoS flow description	1 entry
QFI	‘00 0010’B	QFI 2
Operation code	‘001’B	Create new QoS flow description
E bit	‘1’B	Parameters list is included
Number of parameters	’00 0001’B	1 parameter
5QI	‘0000 0101’B	5QI 5

Table 7.1.4.1.3.3-7: Reference QoS rule #4

Derivation Path: TS 38.508-1[4], table 4.8.2.1-4
Information Element	Value/remark	Comment	Condition
QoS rules
QoS rule
DQR bit	‘0’B

7.1.4.2 SDAP Data Transfer handling without Header UL/DL

7.1.4.2.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state with multiple DRB’s established. SDAP configured without header and no stored QoS flow mapping }

ensure that {

when { UE receives a SDAP SDU from upper layers }

then { UE SDAP entity transmits the SDAP PDU with header on default DRB }

}

(2)

with { UE in RRC_CONNECTED state with multiple DRB’s established. SDAP configured without header and no stored QoS flow mapping }

ensure that {

when { UE SDAP recieves from RRC new Qos Flow mapping }

then { UE SDAP entity transmits an end-marker control PDU for the QoS flow on default DRB }

}

(3)

with { UE in RRC_CONNECTED state with multiple DRB’s established. SDAP configured without header and stored QoS flow mapping configured by RRC }

ensure that {

when { UE receives a SDAP SDU from upper layers }

then { UE SDAP entity transmits the SDAP PDU without header on non default DRB as per configured QoS flow mapping }

}

7.1.4.2.2 Conformance requirements

References: The conformance requirements covered in the present test case are specified in: TS 37.324, clauses 5.2.1, 5.2.2, 5.3.1, 6.2.2.1 and 6.2.3, TS 24.501 clause 6.2.5.1.3. Unless otherwise stated these are Rel-15 requirements.

[TS 37.324 clause 5.2.1]

At the reception of an SDAP SDU from upper layer for a QoS flow, the transmitting SDAP entity shall:

– if there is no stored QoS flow to DRB mapping rule for the QoS flow as specified in the subclause 5.3:

– map the SDAP SDU to the default DRB;

– else:

– map the SDAP SDU to the DRB according to the stored QoS flow to DRB mapping rule;

– if the DRB to which the SDAP SDU is mapped is configured by RRC (3GPP TS 38.331 [3]) with the presence of SDAP header,

– construct the UL SDAP data PDU as specified in the subclause 6.2.2.3;

– else:

– construct the UL SDAP data PDU as specified in the subclause 6.2.2.1;

– submit the constructed UL SDAP data PDU to the lower layers.

NOTE 1: UE behaviour is not defined if there is neither a default DRB nor a stored QoS flow to DRB mapping rule for the QoS flow.

NOTE 2: Default DRB is always configured with UL SDAP header (3GPP TS 38.331 [3]).

[TS 37.324 clause 5.2.2]

At the reception of an SDAP data PDU from lower layers for a QoS flow, the receiving SDAP entity shall:

– if the DRB from which this SDAP data PDU is received is configured by RRC (3GPP TS 38.331 [3]) with the presence of SDAP header:

– perform reflective QoS flow to DRB mapping as specified in the subclause 5.3.2;

– perform RQI handling as specified in the subclause 5.4;

– retrieve the SDAP SDU from the DL SDAP data PDU as specified in the subclause 6.2.2.2.

– else:

– retrieve the SDAP SDU from the DL SDAP data PDU as specified in the subclause 6.2.2.1;

– deliver the retrieved SDAP SDU to the upper layer.

[TS 37.324 clause 5.3.1]

When RRC (3GPP TS 38.331 [3]) configures an UL QoS flow to DRB mapping rule for a QoS flow, the SDAP entity shall:

– if the SDAP entity has already been established and there is no stored QoS flow to DRB mapping rule for the QoS flow and a default DRB is configured:

– construct an end-marker control PDU, as specified in the subclause 6.2.3, for the QoS flow;

– map the end-marker control PDU to the default DRB;

– submit the end-marker control PDU to the lower layers.

– construct an end-marker control PDU, as specified in the subclause 6.2.3, for the QoS flow;

– map the end-marker control PDU to the DRB according to the stored QoS flow to DRB mapping rule;

– submit the end-marker control PDU to the lower layers.

– store the configured UL QoS flow to DRB mapping rule for the QoS flow.

When RRC (3GPP TS 38.331 [3]) releases an UL QoS flow to DRB mapping rule for a QoS flow, the SDAP entity shall:

– remove the UL QoS flow to DRB mapping rule for the QoS flow.

[TS 37.324 clause 6.2.2.1]

An SDAP PDU consists only of a data field and does not consist of any SDAP header, as described in Figure 6.2.2.1-1.

Figure 6.2.2.1-1: SDAP Data PDU format without SDAP header

[TS 37.324 clause 6.2.3]

Figure 6.2.3 – 1 shows the format of End-Marker Control PDU.

Figure 6.2.3-1: End-Marker Control PDU

[TS 24.501 clause 6.2.5.1.3]

b) the QFI of a derived QoS rule associated with the PDU session which has the packet filter for UL direction matching the UL user data packet;

by evaluating the QoS rules in increasing order of their precedence values until the UL user data packet is associated with a QFI or all QoS rules are evaluated.

If the UL user data packet is associated with a QFI, the UE shall pass the QFI along the UL user data packet to the lower layers for transmission.

NOTE: Marking of the UL user data packet with the QFI is performed by the lower layers.

If all QoS rules are evaluated and the UL user data packet is not associated with a QFI, the UE shall discard the UL user data packet.

7.1.4.2.3 Test description

7.1.4.2.3.1 Pre-test conditions

System Simulator:

– NR Cell 1

UE:

– None.

Preamble:

– The UE is in 5GS state 3N-A with one PDU session active according to TS 38.508-1 [4], clause 4.4A.3, Table 4.4A.3-1 and using the message condition UE TEST LOOP MODE B active to return one UL SDAP SDU per DL SDAP SDU. 2 DRBs are configured where DRBj is defined as default DRB. The NAS QoS rules for QoS flows QFI = 5 and QFI = 2 are configured. The ‘mappedQoS-Flows’ is empty for both DRB’s for SDAP layer.

7.1.4.2.3.2 Test procedure sequence

Table 7.1.4.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS sends the SDAP Data PDU without SDAP header on DRB k for QFI =2.	<–	SDAP DL Data PDU	–	–
2	Check: Does the UE transmit SDAP Data PDU on DRB j, which is default DRB, with SDAP header including QFI=2?	–>	SDAP UL Data PDU	1	P
3	The SS sends the SDAP Data PDU without SDAP header on DRB j for QFI 5.	<–	SDAP DL Data PDU	–	–
4	Check: Does the UE transmit SDAP Data PDU on DRB j, which is default DRB, with SDAP header including QFI=5?	–>	SDAP UL Data PDU	1	P
5	The SS transmits an NR RRCReconfiguration message to configure QoS Flow rules	<–	(RRCReconfiguration)	–	–
–	EXCEPTION: In parallel to the event described in step 6 the events specified in Table 7.1.4.2.3.2-2 shall take place.	–	–	–	–
6	The UE transmit an NR RRCReconfigurationComplete message.	–>	(RRCReconfigurationComplete)	–	–
7	The SS sends the SDAP Data PDU without SDAP header on DRB k for QFI =2.	<–	SDAP DL Data PDU	–	–
8	Check: Does the UE transmit SDAP Data PDU on DRB k?	–>	SDAP UL Data PDU	3	P
9	The SS sends the SDAP Data PDU without SDAP header on DRB j for QFI 5.	<–	SDAP DL Data PDU	–	–
10	Check: Does the UE transmit SDAP Data PDU on DRB j, with SDAP header including QFI=5?	–>	SDAP UL Data PDU	3	P

Table 7.1.4.2.3.2-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Check: Does the UE transmit End-Marker Control PDU on DRBj for QFI=2?	–>	SDAP UL Control PDU	2	P

Table 7.1.4.2.3.2-3: Void

7.1.4.2.3.3 Specific message contents

Table 7.1.4.2.3.3-1: RadioBearerConfig-DRB (Preamble)

Derivation Path: TS 38.508-1 [4], table 4.6.3-132 and condition NR
Information Element	Value/remark	Comment	Condition
RadioBearerConfig ::= SEQUENCE {
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) OF SEQUENCE {	2 entries
DRB-ToAddMod[1] SEQUENCE {		entry 1
cnAssociation CHOICE {
sdap-Config SEQUENCE {
pdu-Session	The same as the PDU session ID in PDU SESSION ESTABLISHMENT REQUEST
sdap-HeaderDL	absent
sdap-HeaderUL	absent
defaultDRB	false
}
}
drb-Identity	k	k is allocated according to internal TTCN mapping
}
DRB-ToAddMod[2] SEQUENCE {		entry 2
cnAssociation CHOICE {
sdap-Config SEQUENCE {
pdu-Session	The same as the PDU session ID in PDU SESSION ESTABLISHMENT REQUEST
sdap-HeaderDL	absent
sdap-HeaderUL	present
defaultDRB	true
}
}
drb-Identity	j	j is allocated according to internal TTCN mapping
}
}
}

Table 7.1.4.2.3.3-2: RadioBearerConfig-DRB (step 5, Table 7.1.4.2.3.2-1)

Derivation Path: TS 38.508-1 [4], table 4.6.3-132 and condition NR
Information Element	Value/remark	Comment	Condition
RadioBearerConfig ::= SEQUENCE {
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) OF SEQUENCE {	2 entries
DRB-ToAddMod[1] SEQUENCE {		entry 1
cnAssociation CHOICE {
sdap-Config SEQUENCE {
pdu-Session	The same as the PDU session ID in PDU SESSION ESTABLISHMENT REQUEST
sdap-HeaderDL	absent
sdap-HeaderUL	absent
defaultDRB	false
mappedQoS-FlowsToAdd SEQUENCE {
QFI	2
}
}
}
drb-Identity	k	k is allocated according to internal TTCN mapping
}
DRB-ToAddMod[2] SEQUENCE {		entry 2
cnAssociation CHOICE {
sdap-Config SEQUENCE {
pdu-Session	The same as the PDU session ID in PDU SESSION ESTABLISHMENT REQUEST
sdap-HeaderDL	absent
sdap-HeaderUL	present
defaultDRB	true
mappedQoS-FlowsToAdd	Not present	The ‘mappedQoS-Flows’ is empty for the DRB.
}
}
drb-Identity	j	j is allocated according to internal TTCN mapping
}
}
}

Table 7.1.4.2.3.3-3: PDU SESSION ESTABLISHMENT ACCEPT (Preamble)

Derivation Path: TS 38.508-1 [4], table 4.7.2-2
Information Element	Value/remark	Comment	Condition
PDU session ID	The same as the PDU session ID in PDU SESSION ESTABLISHMENT REQUEST
Authorized QoS rules	3 entries
QoS rule [1]	Reference QoS rule #1 as defined in Table 4.8.2.1-1	QFI=1
QoS rule [2]	Reference QoS rule #4 as defined in Table 4.8.2.1-4 except DQR bit set to ‘0’	QFI=2
QoS rule [3]	Reference QoS rule #5 as defined in Table 4.8.2.1-5	QFI=5
Mapped EPS bearer contexts	Not Present
Authorized QoS flow descriptions	3 entries
QoS flow [1]	Reference QoS flow #1 as defined in Table 7.1.4.2.3.3-4	QFI=1
QoS flow [2]	Reference QoS flow #2 as defined in Table 7.1.4.2.3.3-5	QFI=2
QoS flow [3]	Reference QoS flow #3 as defined in Table 4.8.2.3-3	QFI=5

Table 7.1.4.2.3.3-4: Reference QoS flow #1 (Preamble)

Derivation Path: TS 38.508-1 [4], table 4.8.2.3-1
Information Element	Value/remark	Comment	Condition
QoS flow descriptions
QoS flow description	1 entry
QFI	‘00 0001’B	QFI 1
Operation code	‘001’B	Create new QoS flow description
E bit	‘1’B	Parameters list is included
Number of parameters	’00 0001’B	1 parameter
5QI	‘0000 1001’B	5QI 9

Table 7.1.4.2.3.3-5: Reference QoS flow #2 (Preamble)

Derivation Path: TS 38.508-1 [4], table 4.8.2.3-2
Information Element	Value/remark	Comment	Condition
QoS flow descriptions
QoS flow description	1 entry
QFI	‘00 0010’B	QFI 2
Operation code	‘001’B	Create new QoS flow description
E bit	‘1’B	Parameters list is included
Number of parameters	’00 0001’B	1 parameter
5QI	‘0000 0101’B	5QI 5