4.30 QoS differentiation of traffic for non-3GPP device identifier

A 5GS can support QoS differentiation of traffic for non-3GPP devices connecting through the UE, as specified in 3GPP TS 23.501 [8]. The UE and the network may support QoS differentiation of traffic for non-3GPP devices.

The UE shall bind a non-3GPP device identifier to a non-3GPP device, for the traffic of the non-3GPP device that requires differentiated QoS (see 3GPP TS 23.501 [8] and 3GPP TS 23.316 [6D]). A non-3GPP device identifier shall be bound to no more than one non-3GPP device simultaneously. This binding enables the 5GS to distinguish between the traffic generated by different non-3GPP devices connected through the same UE.

NOTE 1: QoS differentiation of traffic for the non-3GPP device identifier also applies to the wireline access when a non-3GPP device is connecting to the 5G-RG.

NOTE 2: To support QoS differentiation of traffic for non-3GPP device(s) connecting through the UE, how the UE determines which PDU session to use for the non-3GPP device traffic and when to initiate the UE-requested PDU session modification procedure is up to UE implementation. Existing mechanisms (e.g. URSP rules if any or UE local configuration) can be used to determine which PDU session to use for the non-3GPP device traffic.

The UE requests QoS differentiation of traffic from one or more non-3GPP devices associated with non-3GPP device identifiers by providing each non-3GPP device identifier and the corresponding connection information to the SMF in the UE-requested PDU session modification procedure. The UE shall provide the non-3GPP device identifier and the corresponding connection information for each non-3GPP device depending on the PDU session type of the PDU session, as follows:

• for Ethernet PDU session type the UE shall include the non-3GPP device identifier and the Ethernet connection information;
• for IPv4 PDU session type the UE shall include the non-3GPP device identifier and the IPv4 connection information;
• for IPv6 PDU session type the UE shall include the non-3GPP device identifier and the IPv6 connection information; and
• for IPv4v6 PDU session type the UE shall include the non-3GPP device identifier and:
• the IPv4 connection information;
• the IPv6 connection information; or
• both 1) and 2).

NOTE 3: For an IPv4v6 PDU session type, it is up to UE implementation to decide whether to use IPv4 connection information, IPv6 connection information, or a combination of both. This decision can be based on the traffic associated with the non-3GPP device and the IP address allocation by the network for that PDU session.

The UE may request to suspend previously requested QoS differentiation for one or more non-3GPP device identifiers using the UE-requested PDU session modification procedure.

NOTE 4: How the UE determines to suspend previously requested QoS differentiation for a non-3GPP device identifier is implementation specific.