Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.316  Word version:  18.6.0

Top   Top   Up   Prev   None
1…   4…   4.5…   4.7…   4.10…   4.10b…   4.11…   5…   6…   7…   7.2.2…   7.2.3…   7.2.4…   7.3…   7.6…   7.7…   8…   9…   9.5…   10…   A… 
A UE behind RG using untrusted Non-3GPP access procedures  B Support for differentiated charging and QoS for UEs behind RG  $ Change history 

 

A  UE behind RG using untrusted Non-3GPP access procedures  p. 90

This Annex describes how untrusted Non-3GPP access to 5GC can be provided to a UE via a 5G-RG and FN-RG connected to 5GC.
Reproduction of 3GPP TS 23.316, Fig. A-1: Non-roaming architecture for UE behind 5G-RG using untrusted N3GPP access
Figure A-1: Non-roaming architecture for UE behind 5G-RG using untrusted N3GPP access
Up
The 5G-RG can be connected to 5GC via W-5GAN, NG-RAN or via both accesses. The UE can be connected to 5GC via untrusted non-3GPP access (via 5G-RG), NG-RAN or via both accesses.
Reproduction of 3GPP TS 23.316, Fig. A-2: Non-roaming architecture for UE behind FN-RG using untrusted N3GPP access
Figure A-2: Non-roaming architecture for UE behind FN-RG using untrusted N3GPP access
Up
The FN-RG can be connected to 5GC via W-5GAN The UE can be connected to 5GC via untrusted non-3GPP access (via FN-RG), NG-RAN or via both accesses.
Up

B  Support for differentiated charging and QoS for UEs behind RG |R18|  p. 92

For the traffic of UEs behind a RG, QoS differentiation in the RG's PDU Session can be provided on a per UE's IPsec Child Security Association basis. The UE's N3IWF/TNGF determines the IPsec child SAs as defined in clauses 4.12 and 4.12a of TS 23.502 as well as the DSCP value used in the outer IP header of that IPsec child SA. It is assumed that the same set of DSCP values and corresponding QoS are applicable independent of whether UE-requested or network-initiated QoS is used.
To support QoS differentiation for the UE's traffic, QoS mapping rules between the RG's 5GC and the UE's 5GC are governed by an SLA (or network configuration in case of single operator), which includes the mapping between the DSCP marking for the IPsec child SAs and the corresponding QoS parameters and also the N3IWF/TNGF IP address(es). The non-alteration of the DSCP field on NWu/NWt is also governed by the SLA and by transport-level arrangements that are outside of 3GPP scope. The SLA also governs the RG PDU session IP addresses.
The RG's PCF and SMF may provide PCC rules and QoS rules for the available mappings as determined by the SLA. The packet detection filters in the RG's UPF can be based on the N3IWF/TNGF IP address and the DSCP markings on NWu/NWt.
UE's SMF/PCF may use the UE's local IP address, which is the N6 address of the RG's PDU session, to enable differentiated QoS and charging when the UE is accessing N3IWF/TNGF via a W-5GAN.
Differentiated charging is enabled by the awareness of N3IWG/TNGF and RG PDU Session IP addresses and also the mapping between DSCP marking and QoS parameters included in the SLA.
Up

$  Change history  p. 93

Up   Top