3GPP 23.501 v20.2.0 — the document's own text
5.52.2 Traffic identification
Taught in 27. Overload, energy, deployment and the rest (The 5G system architecture, in depth).
The UE may bind a Non-3GPP Device Identifier to a non-3GPP device for the traffic of the non-3GPP device that requires differentiated QoS. This binding enables the 5G System to distinguish between the traffic generated by and sent to different non-3GPP devices connected through the same UE.
NOTE 1: How the UE identifies the non-3GPP device and binds the Non-3GPP Device Identifier to a non-3GPP device is implementation specific. How the Non-3GPP Device Identifier(s) that are associated with the UE's SUPI in the 5GC are known to the UE is implementation specific.
NOTE 2: At any point in time, the Non-3GPP Device Identifier can be bound to at most one non-3GPP device.
Non-3GPP Device Identifier Information is stored in the UDR and includes a Non-3GPP Device Identifier and QoS information. The content of the Non-3GPP Device Identifier Information and how the AF may provision QoS information for the non-3GPP device(s) in the UDR (via the NEF) is further described in clause 4.15.6.15 of TS 23.502 [3].