3GPP 24.501 v20.0.0 — the document's own text

9.11.4.13 QoS rules

Taught in 4. Inside TS 24.501, the document at the centre (CT1 — the group that writes what your phone says, overview).

The purpose of the QoS rules information element is to indicate a set of QoS rules to be used by the UE, where each QoS rule is a set of parameters as described in clause 6.2.5.1.1.2:

for classification and marking of uplink user traffic; and
for identification of a QoS flow which the network is to use for a particular downlink user traffic.

NOTE: The UE needs to be aware of a QoS flow which the network is to use for a particular downlink user traffic e.g. to determine whether a resource is available for downlink media of a media stream of an SDP media description provided by the UE in an IMS session.

The QoS rules may contain a set of packet filters consisting of zero or more packet filters for UL direction, zero or more packet filters for DL direction, zero or more packet filters for both UL and DL directions or any combinations of these. The set of packet filters determine the traffic mapping to QoS flows.

The QoS rules information element is a type 6 information element with a minimum length of 7 octets. The maximum length for the information element is 65538 octets.

The QoS rules information element is coded as shown in figure 9.11.4.13.1, figure 9.11.4.13.2, figure 9.11.4.13.3, figure 9.11.4.13.4, figure 9.11.4.13.5, figure 9.11.4.13.6, figure 9.11.4.13.7, figure 9.11.4.13.8 and table 9.11.4.13.1.

	8	7	6	5	4	3	2	1
	QoS rules IEI	octet 1
	Length of QoS rules IE	octet 2
		octet 3
	QoS rule 1	octet 4octet u
	QoS rule 2	octet u+1octet v
	…	octet v+1octet w
	QoS rule n	octet w+1octet x

Figure 9.11.4.13.1: QoS rules information element

8	7	6	5
QoS rule identifier	octet 4
Length of QoS rule	octet 5
	octet 6
Rule operation code	DQR bit	Number of packet filters	octet 7
Packet filter list	octet 8octet m
QoS rule precedence	octet m+1*
0Spare	Segregation	QoS flow identifier (QFI)	octet m+2*

Figure 9.11.4.13.2: QoS rule (u=m+2)

8	7	6	5	4	3
0	0	0	0	Packet filter identifier 1	octet 8
Spare
0	0	0	0	Packet filter identifier 2	octet 9
Spare
…
0	0	0	0	Packet filter identifier N	octet N+7
Spare

Figure 9.11.4.13.3: Packet filter list when the rule operation is "modify existing QoS rule and delete packet filters" (m=N+7)

8	7	6	5	4
0	0	Packet filter direction 1	Packet filter identifier 1	octet 8
Spare
Length of packet filter contents 1	octet 9
Packet filter contents 1	octet 10octet k
0	0	Packet filter direction 2	Packet filter identifier 2	octet k+1
Spare
Length of packet filter contents 2	octet k+2
Packet filter contents 2	octet k+3octet n
…	octet n+1octet y
0	0	Packet filter direction N	Packet filter identifier N	octet y+1
Spare
Length of packet filter contents N	octet y+2
Packet filter contents N	octet y+3octet m

Figure 9.11.4.13.4: Packet filter list when the rule operation is "create new QoS rule", or "modify existing QoS rule and add packet filters" or "modify existing QoS rule and replace all packet filters"

	8	7	6	5	4	3	2	1
	Number of (S)RTP multiplexed media identification information entries	octet 10
	(S)RTP multiplexed media identification information entry 1	octet 11octet h
	(S)RTP multiplexed media identification information entry 2	octet (h+1)octet i
	…	octet (i+1)octet j
	(S)RTP multiplexed media identification information entry n	octet (j+1)octet k

Figure 9.11.4.13.5: Value part of (S)RTP multiplexed media identification information component

8	7	6	5	4	3	2	1
Length of value part of (S)RTP multiplexed media identification information	octet 11
0	0	0	RPTPI	RSHEMPI	MITPI	PTPI	SSRCPI	octet 12
Spare	Spare	Spare
Synchronization Source (SSRC)	octet 13octet 16
Payload type	octet p*(see NOTE)
MID identification-tag	octet q(see NOTE)octet r
RTP SDES header extension id for MID	octet s* (see NOTE)octet t*
RTCP packet type	octet h*(see NOTE)

NOTE: The field is placed immediately after the last present preceding field.

Figure 9.11.4.13.6: (S)RTP multiplexed media identification information entry

8	7	6	5	4	3	2	1
0	0	PCP indicator	DEI indicator	PCP	DEI	octet 1
Spare	Spare

Figure 9.11.4.13.7: Value part of Extended 802.1Q C-TAG PCP/DEI type

8	7	6	5	4	3	2	1
0	0	PCP indicator	DEI indicator	PCP	DEI	octet 1
Spare	Spare

Figure 9.11.4.13.8: Value part of Extended 802.1Q S-TAG PCP/DEI type

Table 9.11.4.13.1: QoS rules information element

QoS rule identifier (octet 4)The QoS rule identifier field is used to identify the QoS rule.Bits8 7 6 5 4 3 2 10 0 0 0 0 0 0 0 no QoS rule identifier assigned0 0 0 0 0 0 0 1 QRI 1 to1 1 1 1 1 1 1 1 QRI 255The network shall not set the QRI value to 0.QoS rule precedence (octet m+1)The QoS rule precedence field is used to specify the precedence of the QoS rule among all QoS rules (both the signalled QoS rules as described in clause 6.2.5.1.1.2 and the derived QoS rules as described in clause 6.2.5.1.1.3) associated with the PDU session of the QoS flow. This field includes the binary coded value of the QoS rule precedence in the range from 0 to 255 (decimal). The higher the value of the QoS rule precedence field, the lower the precedence of that QoS rule is. For the "delete existing QoS rule" operation, the QoS rule precedence value field shall not be included. For the "create new QoS rule" operation, the QoS rule precedence value field shall be included.The value 80 (decimal) is reserved.Segregation bit (bit 7 of octet m+2) (see NOTE 1)In the UE to network direction the segregation bit indicates whether the UE is requesting the network to bind service data flows described by the QoS rule to a dedicated QoS Flow and it is encoded as follows. In the network to UE direction this bit is spare.Bit70 Segregation not requested1 Segregation requestedQoS flow identifier (QFI) (bits 6 to 1 of octet m+2) (see NOTE 1)The QoS flow identifier (QFI) field contains the QoS flow identifier.Bits6 5 4 3 2 10 0 0 0 0 0 no QoS flow identifier assigned0 0 0 0 0 1 QFI 1 to1 1 1 1 1 1 QFI 63The network shall not set the QFI value to 0.For the "delete existing QoS rule" operation, the QoS flow identifier value field shall not be included. For the "create new QoS rule" operation, the QoS flow identifier value field shall be included.DQR bit (bit 5 of octet 7)The DQR bit indicates whether the QoS rule is the default QoS rule and it is encoded as follows:Bit50 the QoS rule is not the default QoS rule.1 the QoS rule is the default QoS rule.Rule operation code (bits 8 to 6 of octet 7)Bits8 7 60 0 0 Reserved0 0 1 Create new QoS rule0 1 0 Delete existing QoS rule0 1 1 Modify existing QoS rule and add packet filters1 0 0 Modify existing QoS rule and replace all packet filters1 0 1 Modify existing QoS rule and delete packet filters1 1 0 Modify existing QoS rule without modifying packet filters1 1 1 ReservedNumber of packet filters (bits 4 to 1 of octet 7)The number of packet filters contains the binary coding for the number of packet filters in the packet filter list. The number of packet filters field is encoded in bits 4 through 1 of octet 7 where bit 4 is the most significant and bit 1 is the least significant bit. For the "delete existing QoS rule" operation and for the "modify existing QoS rule without modifying packet filters" operation, the number of packet filters shall be coded as 0. For the "create new QoS rule" operation and the "modify existing QoS rule and replace all packet filters" operation, the number of packet filters shall be greater than or equal to 0 and less than or equal to 15. For all other operations, the number of packet filters shall be greater than 0 and less than or equal to 15.Packet filter list (octets 8 to m)The packet filter list contains a variable number of packet filters.For the "delete existing QoS rule" operation, the length of QoS rule field is set to one.For the "delete existing QoS rule" operation and the "modify existing QoS rule without modifying packet filters" operation, the packet filter list shall be empty.For the "modify existing QoS rule and delete packet filters" operation, the packet filter list shall contain a variable number of packet filter identifiers. This number shall be derived from the coding of the number of packet filters field in octet 7.For the "create new QoS rule" operation and for the "modify existing QoS rule and replace all packet filters" operation, the packet filter list shall contain 0 or a variable number of packet filters. This number shall be derived from the coding of the number of packet filters field in octet 7.For the "modify existing QoS rule and add packet filters" operation, the packet filter list shall contain a variable number of packet filters. This number shall be derived from the coding of the number of packet filters field in octet 7.Each packet filter is of variable length and consists of- a packet filter direction (2 bits); - a packet filter identifier (4 bits); - the length of the packet filter contents (1 octet); and- the packet filter contents itself (variable amount of octets).The packet filter direction field is used to indicate for what traffic direction the filter applies.Bits6 50 0 reserved0 1 downlink only (see NOTE 2)1 0 uplink only1 1 bidirectionalThe packet filter identifier field is used to identify each packet filter in a QoS rule. The least significant 4 bits are used. When the UE requests to "create new QoS rule", "modify existing QoS rule and replace all packet filters" or "modify existing QoS rule and add packet filters", the packet filter identifier values shall be set to 0.The length of the packet filter contents field contains the binary coded representation of the length of the packet filter contents field of a packet filter. The first bit in transmission order is the most significant bit.The packet filter contents field is of variable size and contains a variable number (at least one) of packet filter components. Each packet filter component shall be encoded as a sequence of a one octet packet filter component type identifier and a packet filter component value field. Furthermore, for all packet filter component type identifier values except for "(S)RTP multiplexed media identification information type", each of the other packet filter component value field has a fixed length. The packet filter component type identifier shall be transmitted first.In each packet filter, there shall not be more than one occurrence of each packet filter component type. Among the "IPv4 remote address type" and "IPv6 remote address/prefix length type" packet filter components, only one shall be present in one packet filter. Among the "IPv4 local address type" and "IPv6 local address/prefix length type" packet filter components, only one shall be present in one packet filter. Among the "single local port type" and "local port range type" packet filter components, only one shall be present in one packet filter. Among the "single remote port type" and "remote port range type" packet filter components, only one shall be present in one packet filter. Among the "destination MAC address type" and "destination MAC address range type" packet filter components, only one shall be present in one packet filter. Among the "source MAC address type" and "source MAC address range type" packet filter components, only one shall be present in one packet filter. If the "match-all type" packet filter component is present in the packet filter, no other packet filter component shall be present in the packet filter and the length of the packet filter contents field shall be set to one. If the "Ethertype type" packet filter component is present in the packet filter and the "Ethertype type" packet filter component value is neither "0800H" (for IPv4) nor "86DDH" (for IPv6), no IP packet filter component shall be present in the packet filter.The term "IP packet filter component" refers to "IPv4 remote address type", "IPv4 local address type", "IPv6 remote address/prefix length type", "IPv6 local address/prefix length type", "Protocol identifier/Next header type", "Single local port type", "Local port range type", "Single remote port type", "Remote port range type", "Security parameter index type", "Type of service/Traffic class type" and "Flow label type".The "(S)RTP multiplexed media identification information type" packet filter component can not be present in the packet filter with no "IP packet filter component".The term local refers to the UE and the term remote refers to an external network entity.Packet filter component type identifierBits8 7 6 5 4 3 2 10 0 0 0 0 0 0 1 Match-all type (see NOTE 2)0 0 0 1 0 0 0 0 IPv4 remote address type0 0 0 1 0 0 0 1 IPv4 local address type 0 0 1 0 0 0 0 1 IPv6 remote address/prefix length type0 0 1 0 0 0 1 1 IPv6 local address/prefix length type0 0 1 1 0 0 0 0 Protocol identifier/Next header type0 1 0 0 0 0 0 0 Single local port type0 1 0 0 0 0 0 1 Local port range type0 1 0 1 0 0 0 0 Single remote port type 0 1 0 1 0 0 0 1 Remote port range type0 1 1 0 0 0 0 0 Security parameter index type0 1 1 1 0 0 0 0 Type of service/Traffic class type1 0 0 0 0 0 0 0 Flow label type1 0 0 0 0 0 0 1 Destination MAC address type1 0 0 0 0 0 1 0 Source MAC address type1 0 0 0 0 0 1 1 802.1Q C-TAG VID type1 0 0 0 0 1 0 0 802.1Q S-TAG VID type1 0 0 0 0 1 0 1 802.1Q C-TAG PCP/DEI type1 0 0 0 1 0 1 0 Extended 802.1Q C-TAG PCP/DEI type1 0 0 0 0 1 1 0 802.1Q S-TAG PCP/DEI type1 0 0 0 1 0 1 1 Extended 802.1Q S-TAG PCP/DEI type1 0 0 0 0 1 1 1 Ethertype type1 0 0 0 1 0 0 0 Destination MAC address range type1 0 0 0 1 0 0 1 Source MAC address range type1 0 0 1 0 0 0 1 (S)RTP multiplexed media identification information type (see NOTE 3, NOTE 4)All other values are reserved.The description and valid combinations of packet filter component type identifiers in a packet filter are defined in 3GPP TS 23.501 [8].For "match-all type", the packet filter component shall not include the packet filter component value field.For "IPv4 remote address type", the packet filter component value field shall be encoded as a sequence of a four octet IPv4 address field and a four octet IPv4 address mask field. The IPv4 address field shall be transmitted first.For "IPv4 local address type", the packet filter component value field shall be encoded as defined for "IPv4 remote address type".For "IPv6 remote address/prefix length type", the packet filter component value field shall be encoded as a sequence of a sixteen octet IPv6 address field and one octet prefix length field. The IPv6 address field shall be transmitted first.For "IPv6 local address/prefix length type", the packet filter component value field shall be encoded as defined for "IPv6 remote address /prefix length".For "protocol identifier/Next header type", the packet filter component value field shall be encoded as one octet which specifies the IPv4 protocol identifier or Ipv6 next header.For "single local port type" and "single remote port type", the packet filter component value field shall be encoded as two octets which specify a port number.For "local port range type" and "remote port range type", the packet filter component value field shall be encoded as a sequence of a two octet port range low limit field and a two octet port range high limit field. The port range low limit field shall be transmitted first.For "security parameter index", the packet filter component value field shall be encoded as four octets which specify the IPSec security parameter index.For "type of service/traffic class type", the packet filter component value field shall be encoded as a sequence of a one octet type-of-service/traffic class field and a one octet type-of-service/traffic class mask field. The type-of-service/traffic class field shall be transmitted first.For "flow label type", the packet filter component value field shall be encoded as three octets which specify the IPv6 flow label. The bits 8 through 5 of the first octet shall be spare whereas the remaining 20 bits shall contain the IPv6 flow label.For "destination MAC address type" and "source MAC address type", the packet filter component value field shall be encoded as 6 octets which specify a MAC address. When the packet filter direction field indicates "bidirectional", the destination MAC address is the remote MAC address and the source MAC address is the local MAC address.For "802.1Q C-TAG VID type", the packet filter component value field shall be encoded as two octets which specify the VID of the customer-VLAN tag (C-TAG). The bits 8 through 5 of the first octet shall be spare whereas the remaining 12 bits shall contain the VID. If there are more than one C-TAG in the Ethernet frame header, the outermost C-TAG is evaluated.For "802.1Q S-TAG VID type", the packet filter component value field shall be encoded as two octets which specify the VID of the service-VLAN tag (S-TAG). The bits 8 through 5 of the first octet shall be spare whereas the remaining 12 bits shall contain the VID. If there are more than one S-TAG in the Ethernet frame header, the outermost S-TAG is evaluated.For "802.1Q C-TAG PCP/DEI type", the packet filter component value field shall be encoded as one octet which specifies the 802.1Q C-TAG PCP and DEI. The bits 8 through 5 of the octet shall be spare, the bits 4 through 2 contain the PCP and bit 1 contains the DEI. If there are more than one C-TAG in the Ethernet frame header, the outermost C-TAG is evaluated.For "extended 802.1Q C-TAG PCP/DEI type", the packet filter component value field shall be encoded as one octet which specifies the 802.1Q C-TAG PCP and DEI as shown in figure 9.11.4.13.7. The bits 8 and 7 of the octet shall be spare and set to 0. The bit 6 indicates the presence of the PCP field, when bit 6 is set to 1, the bits 4 through 2 contain the PCP. When the bit 6 is set to 0, the bits 4 through 2 are spare and not used. The bit 5 indicates the presence of the EDI field, when bit 5 is set to 1, bit 1 contains the DEI. When the bit 5 is set to 0, the bit 1 is spare and not used. If there are more than one C-TAG in the Ethernet frame header, the outermost C-TAG is evaluated.For "802.1Q S-TAG PCP/DEI type", the packet filter component value field shall be encoded as one octet which specifies the 802.1Q S-TAG PCP and DEI. The bits 8 through 5 of the octet shall be spare, the bits 4 through 2 contain the PCP and bit 1 contains the DEI. If there are more than one S-TAG in the Ethernet frame header, the outermost S-TAG is evaluated.For "extended 802.1Q S-TAG PCP/DEI type", the packet filter component value field shall be encoded as one octet which specifies the 802.1Q S-TAG PCP and DEI as shown in figure 9.11.4.13.8. The bits 8 and 7 of the octet shall be spare and set to 0. The bit 6 indicates the presence of the PCP field, when bit 6 is set to 1, the bits 4 through 2 contain the PCP. When the bit 6 is set to 0, the bits 4 through 2 are spare and not used. The bit 5 indicates the presence of the EDI field, when bit 5 is set to 1, bit 1 contains the DEI. When the bit 5 is set to 0, the bit 1 is spare and not used. If there are more than one S-TAG in the Ethernet frame header, the outermost S-TAG is evaluated.For "ethertype type", the packet filter component value field shall be encoded as two octets which specify an ethertype.For "destination MAC address range type", the packet filter component value field shall be encoded as a sequence of a 6 octet destination MAC address range low limit field and a 6 octet destination MAC address range high limit field. The destination MAC address range low limit field shall be transmitted first. When the packet filter direction field indicates "bidirectional", the destination MAC address range is the remote MAC address range.For "source MAC address range type", the packet filter component value field shall be encoded as a sequence of a 6 octet source MAC address range low limit field and a 6 octet source MAC address range high limit field. The source MAC address range low limit field shall be transmitted first. When the packet filter direction field indicates "bidirectional", the source MAC address is the local MAC address range.For "(S)RTP multiplexed media identification information type", the packet filter component value field shall be encoded as figure 9.11.4.13.5 and figure 9.11.4.13.6.An (S)RTP multiplexed media identification information entry for (s)RTCP shall contain the RTCP packet type field and at least one of the SSRC field and MID identification-tag field.An (S)RTP multiplexed media identification information entry for (s)RTP shall contain payload type field, additionally, it may contain:a) SSRC field;b) MID identification-tag field and RTP SDES header extension id for MID; orc) both a) and b).An (S)RTP multiplexed media identification information entry for (s)RTP and (s)RTCP shall contain:a) SSRC field;b) MID identification-tag field and RTP SDES header extension id for MID field; orc) both a) and b).SSRC presence indicator (SSRCPI) (bit 1 of octet 12)The SSRCPI field indicates whether the SSRC field is included or not.Bit10 SSRC not included1 SSRC includedPayload type presence indicator (PTPI) (bit 2 of octet 12)The PTPI field indicates whether the payload type field is included or not.Bit20 Payload type not included1 Payload type includedMID identification-tag presence indicator (MITPI) (bit 3 of octet 12)The MITPI field indicates whether the MID identification-tag field is included or not.Bit30 MID identification-tag not included1 MID identification-tag includedRTP SDES header extension id for MID presence indicator (RSHEMPI) (bit 4 of octet 12)The RSHEMPI field indicates whether the RTP SDES header extension id for MID field is included or not.Bit40 RTP SDES header extension id for MID not included1 RTP SDES header extension id for MID includedRTCP packet type presence indicator (RPTPI) (bit 5 of octet 12)The RPTPI field indicates whether the RTCP packet type field is included or not.Bit50 RTCP packet type not included1 RTCP packet type includedThe synchronization source (SSRC) field shall be encoded as 4 octet SSRC field which specify the synchronization source identifier in the RTP header as specified in IETF RFC 3550 [71].The payload type field shall be encoded as octet payload type field which contains the binary representation of an integer between 0(inclusive) and 127(inclusive) as specified in IETF RFC 3550 [71] (see NOTE 5). The other values are spare. If a spare value is received, the UE shall ignore the corresponding (S)RTP multiplexed media identification information entry.The MID identification-tag field shall be encoded as length of the MID identification-tag which is one octet and followed by value of the MID identification-tag which is with a maximum length of 255 octets as specified in IETF RFC 9143 [72].The RTP SDES header extension id for MID field contains the RTP SDES header extension id for MID, it shall be coded as the RTP SDES header extension id of the RTP SDES header extension for MID as specified in IETF RFC 9143 [72].The RTCP packet type field shall be encoded as one octet and contains the binary representation of an unsigned integer in the range 0 to 255 inclusive as specified in IETF RFC 3550 [71] (see NOTE 5).
NOTE 1: Octet m+2 shall not be included without octet m+1.NOTE 2: The "Match-all type" packet filter component type identifier shall not be used with packet filter direction "downlink only".NOTE 3: When the "(S)RTP multiplexed media identification information type" packet filter component type identifier is present in an uplink packet filter, if an UL user data packet matches any (S)RTP multiplexed media identification information entry, the UL user data packet is considered to match the (S)RTP multiplexed media identification information component of the UL packet filter. How to determine an UL user data packet matches the (S)RTP multiplexed media identification information entry is left to implementation.NOTE 4: At least one of the SSRCPI, PTPI, MITPI, RSHEMPI, and RPTPI shall be set to 1 in the (S)RTP multiplexed media identification information entry.NOTE 5: As specified in clause 4 of IETF RFC 5761 [73], the RTP payload type values and RTCP packet type values in the multiplexed media shall not collide. The RTP payload type values plus 128 and RTCP packet type values in the multiplexed media shall not collide.

QoS rule identifier (octet 4)The QoS rule identifier field is used to identify the QoS rule.Bits8 7 6 5 4 3 2 10 0 0 0 0 0 0 0 no QoS rule identifier assigned0 0 0 0 0 0 0 1 QRI 1 to1 1 1 1 1 1 1 1 QRI 255The network shall not set the QRI value to 0.QoS rule precedence (octet m+1)The QoS rule precedence field is used to specify the precedence of the QoS rule among all QoS rules (both the signalled QoS rules as described in clause 6.2.5.1.1.2 and the derived QoS rules as described in clause 6.2.5.1.1.3) associated with the PDU session of the QoS flow. This field includes the binary coded value of the QoS rule precedence in the range from 0 to 255 (decimal). The higher the value of the QoS rule precedence field, the lower the precedence of that QoS rule is. For the "delete existing QoS rule" operation, the QoS rule precedence value field shall not be included. For the "create new QoS rule" operation, the QoS rule precedence value field shall be included.The value 80 (decimal) is reserved.Segregation bit (bit 7 of octet m+2) (see NOTE 1)In the UE to network direction the segregation bit indicates whether the UE is requesting the network to bind service data flows described by the QoS rule to a dedicated QoS Flow and it is encoded as follows. In the network to UE direction this bit is spare.Bit70 Segregation not requested1 Segregation requestedQoS flow identifier (QFI) (bits 6 to 1 of octet m+2) (see NOTE 1)The QoS flow identifier (QFI) field contains the QoS flow identifier.Bits6 5 4 3 2 10 0 0 0 0 0 no QoS flow identifier assigned0 0 0 0 0 1 QFI 1 to1 1 1 1 1 1 QFI 63The network shall not set the QFI value to 0.For the "delete existing QoS rule" operation, the QoS flow identifier value field shall not be included. For the "create new QoS rule" operation, the QoS flow identifier value field shall be included.DQR bit (bit 5 of octet 7)The DQR bit indicates whether the QoS rule is the default QoS rule and it is encoded as follows:Bit50 the QoS rule is not the default QoS rule.1 the QoS rule is the default QoS rule.Rule operation code (bits 8 to 6 of octet 7)Bits8 7 60 0 0 Reserved0 0 1 Create new QoS rule0 1 0 Delete existing QoS rule0 1 1 Modify existing QoS rule and add packet filters1 0 0 Modify existing QoS rule and replace all packet filters1 0 1 Modify existing QoS rule and delete packet filters1 1 0 Modify existing QoS rule without modifying packet filters1 1 1 ReservedNumber of packet filters (bits 4 to 1 of octet 7)The number of packet filters contains the binary coding for the number of packet filters in the packet filter list. The number of packet filters field is encoded in bits 4 through 1 of octet 7 where bit 4 is the most significant and bit 1 is the least significant bit. For the "delete existing QoS rule" operation and for the "modify existing QoS rule without modifying packet filters" operation, the number of packet filters shall be coded as 0. For the "create new QoS rule" operation and the "modify existing QoS rule and replace all packet filters" operation, the number of packet filters shall be greater than or equal to 0 and less than or equal to 15. For all other operations, the number of packet filters shall be greater than 0 and less than or equal to 15.Packet filter list (octets 8 to m)The packet filter list contains a variable number of packet filters.For the "delete existing QoS rule" operation, the length of QoS rule field is set to one.For the "delete existing QoS rule" operation and the "modify existing QoS rule without modifying packet filters" operation, the packet filter list shall be empty.For the "modify existing QoS rule and delete packet filters" operation, the packet filter list shall contain a variable number of packet filter identifiers. This number shall be derived from the coding of the number of packet filters field in octet 7.For the "create new QoS rule" operation and for the "modify existing QoS rule and replace all packet filters" operation, the packet filter list shall contain 0 or a variable number of packet filters. This number shall be derived from the coding of the number of packet filters field in octet 7.For the "modify existing QoS rule and add packet filters" operation, the packet filter list shall contain a variable number of packet filters. This number shall be derived from the coding of the number of packet filters field in octet 7.Each packet filter is of variable length and consists of- a packet filter direction (2 bits); - a packet filter identifier (4 bits); - the length of the packet filter contents (1 octet); and- the packet filter contents itself (variable amount of octets).The packet filter direction field is used to indicate for what traffic direction the filter applies.Bits6 50 0 reserved0 1 downlink only (see NOTE 2)1 0 uplink only1 1 bidirectionalThe packet filter identifier field is used to identify each packet filter in a QoS rule. The least significant 4 bits are used. When the UE requests to "create new QoS rule", "modify existing QoS rule and replace all packet filters" or "modify existing QoS rule and add packet filters", the packet filter identifier values shall be set to 0.The length of the packet filter contents field contains the binary coded representation of the length of the packet filter contents field of a packet filter. The first bit in transmission order is the most significant bit.The packet filter contents field is of variable size and contains a variable number (at least one) of packet filter components. Each packet filter component shall be encoded as a sequence of a one octet packet filter component type identifier and a packet filter component value field. Furthermore, for all packet filter component type identifier values except for "(S)RTP multiplexed media identification information type", each of the other packet filter component value field has a fixed length. The packet filter component type identifier shall be transmitted first.In each packet filter, there shall not be more than one occurrence of each packet filter component type. Among the "IPv4 remote address type" and "IPv6 remote address/prefix length type" packet filter components, only one shall be present in one packet filter. Among the "IPv4 local address type" and "IPv6 local address/prefix length type" packet filter components, only one shall be present in one packet filter. Among the "single local port type" and "local port range type" packet filter components, only one shall be present in one packet filter. Among the "single remote port type" and "remote port range type" packet filter components, only one shall be present in one packet filter. Among the "destination MAC address type" and "destination MAC address range type" packet filter components, only one shall be present in one packet filter. Among the "source MAC address type" and "source MAC address range type" packet filter components, only one shall be present in one packet filter. If the "match-all type" packet filter component is present in the packet filter, no other packet filter component shall be present in the packet filter and the length of the packet filter contents field shall be set to one. If the "Ethertype type" packet filter component is present in the packet filter and the "Ethertype type" packet filter component value is neither "0800H" (for IPv4) nor "86DDH" (for IPv6), no IP packet filter component shall be present in the packet filter.The term "IP packet filter component" refers to "IPv4 remote address type", "IPv4 local address type", "IPv6 remote address/prefix length type", "IPv6 local address/prefix length type", "Protocol identifier/Next header type", "Single local port type", "Local port range type", "Single remote port type", "Remote port range type", "Security parameter index type", "Type of service/Traffic class type" and "Flow label type".The "(S)RTP multiplexed media identification information type" packet filter component can not be present in the packet filter with no "IP packet filter component".The term local refers to the UE and the term remote refers to an external network entity.Packet filter component type identifierBits8 7 6 5 4 3 2 10 0 0 0 0 0 0 1 Match-all type (see NOTE 2)0 0 0 1 0 0 0 0 IPv4 remote address type0 0 0 1 0 0 0 1 IPv4 local address type 0 0 1 0 0 0 0 1 IPv6 remote address/prefix length type0 0 1 0 0 0 1 1 IPv6 local address/prefix length type0 0 1 1 0 0 0 0 Protocol identifier/Next header type0 1 0 0 0 0 0 0 Single local port type0 1 0 0 0 0 0 1 Local port range type0 1 0 1 0 0 0 0 Single remote port type 0 1 0 1 0 0 0 1 Remote port range type0 1 1 0 0 0 0 0 Security parameter index type0 1 1 1 0 0 0 0 Type of service/Traffic class type1 0 0 0 0 0 0 0 Flow label type1 0 0 0 0 0 0 1 Destination MAC address type1 0 0 0 0 0 1 0 Source MAC address type1 0 0 0 0 0 1 1 802.1Q C-TAG VID type1 0 0 0 0 1 0 0 802.1Q S-TAG VID type1 0 0 0 0 1 0 1 802.1Q C-TAG PCP/DEI type1 0 0 0 1 0 1 0 Extended 802.1Q C-TAG PCP/DEI type1 0 0 0 0 1 1 0 802.1Q S-TAG PCP/DEI type1 0 0 0 1 0 1 1 Extended 802.1Q S-TAG PCP/DEI type1 0 0 0 0 1 1 1 Ethertype type1 0 0 0 1 0 0 0 Destination MAC address range type1 0 0 0 1 0 0 1 Source MAC address range type1 0 0 1 0 0 0 1 (S)RTP multiplexed media identification information type (see NOTE 3, NOTE 4)All other values are reserved.The description and valid combinations of packet filter component type identifiers in a packet filter are defined in 3GPP TS 23.501 [8].For "match-all type", the packet filter component shall not include the packet filter component value field.For "IPv4 remote address type", the packet filter component value field shall be encoded as a sequence of a four octet IPv4 address field and a four octet IPv4 address mask field. The IPv4 address field shall be transmitted first.For "IPv4 local address type", the packet filter component value field shall be encoded as defined for "IPv4 remote address type".For "IPv6 remote address/prefix length type", the packet filter component value field shall be encoded as a sequence of a sixteen octet IPv6 address field and one octet prefix length field. The IPv6 address field shall be transmitted first.For "IPv6 local address/prefix length type", the packet filter component value field shall be encoded as defined for "IPv6 remote address /prefix length".For "protocol identifier/Next header type", the packet filter component value field shall be encoded as one octet which specifies the IPv4 protocol identifier or Ipv6 next header.For "single local port type" and "single remote port type", the packet filter component value field shall be encoded as two octets which specify a port number.For "local port range type" and "remote port range type", the packet filter component value field shall be encoded as a sequence of a two octet port range low limit field and a two octet port range high limit field. The port range low limit field shall be transmitted first.For "security parameter index", the packet filter component value field shall be encoded as four octets which specify the IPSec security parameter index.For "type of service/traffic class type", the packet filter component value field shall be encoded as a sequence of a one octet type-of-service/traffic class field and a one octet type-of-service/traffic class mask field. The type-of-service/traffic class field shall be transmitted first.For "flow label type", the packet filter component value field shall be encoded as three octets which specify the IPv6 flow label. The bits 8 through 5 of the first octet shall be spare whereas the remaining 20 bits shall contain the IPv6 flow label.For "destination MAC address type" and "source MAC address type", the packet filter component value field shall be encoded as 6 octets which specify a MAC address. When the packet filter direction field indicates "bidirectional", the destination MAC address is the remote MAC address and the source MAC address is the local MAC address.For "802.1Q C-TAG VID type", the packet filter component value field shall be encoded as two octets which specify the VID of the customer-VLAN tag (C-TAG). The bits 8 through 5 of the first octet shall be spare whereas the remaining 12 bits shall contain the VID. If there are more than one C-TAG in the Ethernet frame header, the outermost C-TAG is evaluated.For "802.1Q S-TAG VID type", the packet filter component value field shall be encoded as two octets which specify the VID of the service-VLAN tag (S-TAG). The bits 8 through 5 of the first octet shall be spare whereas the remaining 12 bits shall contain the VID. If there are more than one S-TAG in the Ethernet frame header, the outermost S-TAG is evaluated.For "802.1Q C-TAG PCP/DEI type", the packet filter component value field shall be encoded as one octet which specifies the 802.1Q C-TAG PCP and DEI. The bits 8 through 5 of the octet shall be spare, the bits 4 through 2 contain the PCP and bit 1 contains the DEI. If there are more than one C-TAG in the Ethernet frame header, the outermost C-TAG is evaluated.For "extended 802.1Q C-TAG PCP/DEI type", the packet filter component value field shall be encoded as one octet which specifies the 802.1Q C-TAG PCP and DEI as shown in figure 9.11.4.13.7. The bits 8 and 7 of the octet shall be spare and set to 0. The bit 6 indicates the presence of the PCP field, when bit 6 is set to 1, the bits 4 through 2 contain the PCP. When the bit 6 is set to 0, the bits 4 through 2 are spare and not used. The bit 5 indicates the presence of the EDI field, when bit 5 is set to 1, bit 1 contains the DEI. When the bit 5 is set to 0, the bit 1 is spare and not used. If there are more than one C-TAG in the Ethernet frame header, the outermost C-TAG is evaluated.For "802.1Q S-TAG PCP/DEI type", the packet filter component value field shall be encoded as one octet which specifies the 802.1Q S-TAG PCP and DEI. The bits 8 through 5 of the octet shall be spare, the bits 4 through 2 contain the PCP and bit 1 contains the DEI. If there are more than one S-TAG in the Ethernet frame header, the outermost S-TAG is evaluated.For "extended 802.1Q S-TAG PCP/DEI type", the packet filter component value field shall be encoded as one octet which specifies the 802.1Q S-TAG PCP and DEI as shown in figure 9.11.4.13.8. The bits 8 and 7 of the octet shall be spare and set to 0. The bit 6 indicates the presence of the PCP field, when bit 6 is set to 1, the bits 4 through 2 contain the PCP. When the bit 6 is set to 0, the bits 4 through 2 are spare and not used. The bit 5 indicates the presence of the EDI field, when bit 5 is set to 1, bit 1 contains the DEI. When the bit 5 is set to 0, the bit 1 is spare and not used. If there are more than one S-TAG in the Ethernet frame header, the outermost S-TAG is evaluated.For "ethertype type", the packet filter component value field shall be encoded as two octets which specify an ethertype.For "destination MAC address range type", the packet filter component value field shall be encoded as a sequence of a 6 octet destination MAC address range low limit field and a 6 octet destination MAC address range high limit field. The destination MAC address range low limit field shall be transmitted first. When the packet filter direction field indicates "bidirectional", the destination MAC address range is the remote MAC address range.For "source MAC address range type", the packet filter component value field shall be encoded as a sequence of a 6 octet source MAC address range low limit field and a 6 octet source MAC address range high limit field. The source MAC address range low limit field shall be transmitted first. When the packet filter direction field indicates "bidirectional", the source MAC address is the local MAC address range.For "(S)RTP multiplexed media identification information type", the packet filter component value field shall be encoded as figure 9.11.4.13.5 and figure 9.11.4.13.6.An (S)RTP multiplexed media identification information entry for (s)RTCP shall contain the RTCP packet type field and at least one of the SSRC field and MID identification-tag field.An (S)RTP multiplexed media identification information entry for (s)RTP shall contain payload type field, additionally, it may contain:a) SSRC field;b) MID identification-tag field and RTP SDES header extension id for MID; orc) both a) and b).An (S)RTP multiplexed media identification information entry for (s)RTP and (s)RTCP shall contain:a) SSRC field;b) MID identification-tag field and RTP SDES header extension id for MID field; orc) both a) and b).SSRC presence indicator (SSRCPI) (bit 1 of octet 12)The SSRCPI field indicates whether the SSRC field is included or not.Bit10 SSRC not included1 SSRC includedPayload type presence indicator (PTPI) (bit 2 of octet 12)The PTPI field indicates whether the payload type field is included or not.Bit20 Payload type not included1 Payload type includedMID identification-tag presence indicator (MITPI) (bit 3 of octet 12)The MITPI field indicates whether the MID identification-tag field is included or not.Bit30 MID identification-tag not included1 MID identification-tag includedRTP SDES header extension id for MID presence indicator (RSHEMPI) (bit 4 of octet 12)The RSHEMPI field indicates whether the RTP SDES header extension id for MID field is included or not.Bit40 RTP SDES header extension id for MID not included1 RTP SDES header extension id for MID includedRTCP packet type presence indicator (RPTPI) (bit 5 of octet 12)The RPTPI field indicates whether the RTCP packet type field is included or not.Bit50 RTCP packet type not included1 RTCP packet type includedThe synchronization source (SSRC) field shall be encoded as 4 octet SSRC field which specify the synchronization source identifier in the RTP header as specified in IETF RFC 3550 [71].The payload type field shall be encoded as octet payload type field which contains the binary representation of an integer between 0(inclusive) and 127(inclusive) as specified in IETF RFC 3550 [71] (see NOTE 5). The other values are spare. If a spare value is received, the UE shall ignore the corresponding (S)RTP multiplexed media identification information entry.The MID identification-tag field shall be encoded as length of the MID identification-tag which is one octet and followed by value of the MID identification-tag which is with a maximum length of 255 octets as specified in IETF RFC 9143 [72].The RTP SDES header extension id for MID field contains the RTP SDES header extension id for MID, it shall be coded as the RTP SDES header extension id of the RTP SDES header extension for MID as specified in IETF RFC 9143 [72].The RTCP packet type field shall be encoded as one octet and contains the binary representation of an unsigned integer in the range 0 to 255 inclusive as specified in IETF RFC 3550 [71] (see NOTE 5).

NOTE 1: Octet m+2 shall not be included without octet m+1.NOTE 2: The "Match-all type" packet filter component type identifier shall not be used with packet filter direction "downlink only".NOTE 3: When the "(S)RTP multiplexed media identification information type" packet filter component type identifier is present in an uplink packet filter, if an UL user data packet matches any (S)RTP multiplexed media identification information entry, the UL user data packet is considered to match the (S)RTP multiplexed media identification information component of the UL packet filter. How to determine an UL user data packet matches the (S)RTP multiplexed media identification information entry is left to implementation.NOTE 4: At least one of the SSRCPI, PTPI, MITPI, RSHEMPI, and RPTPI shall be set to 1 in the (S)RTP multiplexed media identification information entry.NOTE 5: As specified in clause 4 of IETF RFC 5761 [73], the RTP payload type values and RTCP packet type values in the multiplexed media shall not collide. The RTP payload type values plus 128 and RTCP packet type values in the multiplexed media shall not collide.