5.52.3 Session management enhancement

For the traffic of non-3GPP devices requiring differentiated QoS, the Non-3GPP Device Connection Information may be signalled by the UE as defined in TS 24.501 [47]. When a non-3GPP device is connected to the UE, the UE may request QoS differentiation for a Non-3GPP Device Identifier by providing the Non-3GPP Device Connection Information in PDU Session Modification Request to the SMF. The Non-3GPP Device Connection Information may include information of more than one non-3GPP device. The SMF forwards the Non-3GPP Device Connection Information to the PCF for policy control.

NOTE 1: To support QoS differentiation of traffic for Non-3GPP Device Identifier, how the UE determines which PDU Session to use for the non-3GPP device's traffic is not specified; the existing mechanisms (e.g. URSP) can be used to determine which PDU Session to use. It is up to UE implementation to determine when to initiate the PDU Session Modification procedure for updating the Non-3GPP Device Connection Information.

NOTE 2: Combination(s) of DNN and S-NSSAI are configured in the UE by the operator for the QoS differentiation of traffic for Non-3GPP Device Identifiers feature using existing mechanisms (e.g. URSP) and can be used to select an SMF and PCF that support handling of non-3GPP device identifiers. All of the SMFs and the PCFs serving this DNN and S-NSSAI in the network need to support Non-3GPP Device Identifiers.

For an Ethernet PDU Session, the Non-3GPP Device Connection Information includes the following information for each non-3GPP device if the UE is requesting QoS differentiation for a Non-3GPP Device Identifier:

• Non-3GPP Device Identifier;
• MAC address of the non-3GPP device used in PDU Session;
• Optionally, VLAN tag ID that is associated with the non-3GPP device used in PDU Session.

If the VLAN tag ID is present in the Non-3GPP Device Connection Information and if any received VLAN Tag ID from the UE is not within the allowed VLAN tags for the UE (as described in clause 5.6.10.2), the SMF rejects the PDU Session Modification Request, without sending SM Policy Association Modification request to PCF as specified in the clause 5.52.4.

For an IPv4 or IPv4v6 PDU Session, the Non-3GPP Device Connection Information includes the following information for each non-3GPP device if the UE is requesting QoS differentiation for a Non-3GPP Device Identifier:

• Non-3GPP Device Identifier;
• IPv4 Address associated with the non-3GPP device used in PDU Session;
• Optionally, port range(s) associated with the non-3GPP device used in PDU Session.

NOTE 3: IPv4 Address refers to the IP Address of the PDU Session or an IP Address in the range of a Framed Route that is associated with the PDU Session.

For an IPv6 or IPv4v6 PDU Session, the Non-3GPP Device Connection Information includes the following information for each non-3GPP device if the UE is requesting QoS differentiation for a Non-3GPP Device Identifier:

• Non-3GPP Device Identifier;
• IPv6 Address/prefix(sub) associated with the non-3GPP device used in PDU Session;
• Optionally, port range(s) associated with the non-3GPP device used in PDU Session.

NOTE 4: If the PDU Session type is IPv4v6, it is up to UE implementation to determine to use IPv4 or IPv6 or both Address/prefix(sub) based on the associated traffic of the non-3GPP device and the IPv4 address and an IPv6 prefix that are allocated by the network to the PDU Session.

If the UE wants to suspend previously requested QoS differentiation for a Non-3GPP Device Identifier, the UE may send the Non-3GPP Device Connection Information in a PDU Session Modification Request to the SMF without providing user plane address information in the Non-3GPP Device Connection Information. The Non-3GPP Device Connection Information may include information of more than one non-3GPP device.

NOTE 5: How the UE decides that it wants to suspend previously requested QoS differentiation for a Non-3GPP Device Identifier is implementation specific. For example, when a device disconnects, QoS differentiation for the associated Non-3GPP Device Identifier can be suspended.

If the PCF indicates to the SMF, by rejecting the SM Policy Association Modification, that any of the corresponding Non-3GPP Device Identifier(s) in the Non-3GPP Device Connection Information are not available in the UDR for the UE as specified in clause 6.1.3.31 of TS 23.503 [45], the SMF rejects the PDU Session Modification with a cause code to notify the UE that the Non-3GPP Device Identifier(s) are not available for the UE.

NOTE 6: Since the inclusion of Non-3GPP Device Identifier(s) not available in the UDR for the UE leads to rejection of PDU Session Modification Request, it is recommended that UE does not include parameters that are not related to Non-3GPP Device Connection Information in a PDU Session Modification Request that request differentiated QoS for a non-3GPP device.