Content for TS 23.501 Word version: 18.5.0

1… 3… 4.2.3 4.2.4 4.2.5… 4.2.8… 4.2.8.2.2 4.2.8.2.3… 4.2.8.4… 4.2.9… 4.2.15… 4.3… 4.3.3 4.3.4 4.3.5 4.4… 4.4.6… 4.4.8… 5… 5.3… 5.3.3… 5.4… 5.5… 5.6… 5.6.7… 5.7… 5.7.2… 5.7.3… 5.7.4 5.7.5… 5.8… 5.8.2.11… 5.9… 5.10… 5.11… 5.15… 5.15.11… 5.16… 5.17… 5.18… 5.19… 5.21… 5.22… 5.27… 5.28… 5.29… 5.30… 5.31… 5.32… 5.32.6… 5.33… 5.34… 5.35… 5.38… 5.43… 6… 6.3… 6.3.8… 7… 7.2… 8… 8.2.4 8.2.5… 8.3… A… D… E… F G… G.3 G.4… H… J K… M… N… O… P…

4.2.8.2.3 Home-routed Roaming Architecture 4.2.8.3 Reference Points for Non-3GPP Access 4.2.8.3.1 Overview 4.2.8.3.2 Requirements on Ta
...

4.2.8.2.3 Home-routed Roaming Architecture p. 62

Reproduction of 3GPP TS 23.501, Fig. 4.2.8.2.3-1: Home-routed Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in the same VPLMN as 3GPP access

Figure 4.2.8.2.3-1: Home-routed Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in the same VPLMN as 3GPP access

Reproduction of 3GPP TS 23.501, Fig. 4.2.8.2.3-2: Home-routed Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in a different VPLMN than 3GPP access

Figure 4.2.8.2.3-2: Home-routed Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in a different VPLMN than 3GPP access

Reproduction of 3GPP TS 23.501, Fig. 4.2.8.2.3-3: Home-routed Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in HPLMN

Figure 4.2.8.2.3-3: Home-routed Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in HPLMN

Reproduction of 3GPP TS 23.501, Fig. 4.2.8.2.3-4: Home-routed Roaming architecture for 5G Core Network with trusted non-3GPP access using the same VPLMN as 3GPP access

Figure 4.2.8.2.3-4: Home-routed Roaming architecture for 5G Core Network with trusted non-3GPP access using the same VPLMN as 3GPP access

4.2.8.3 Reference Points for Non-3GPP Access p. 64

4.2.8.3.1 Overview |R16| p. 64

The description of the reference points specific for the non-3GPP access:

N2, N3, N4, N6:

these are defined in clause 4.2.

Reference point between the UE and the untrusted non-3GPP access (e.g. WLAN). This depends on the non-3GPP access technology and is outside the scope of 3GPP.

Reference point between the untrusted non-3GPP access and the N3IWF for the transport of NWu traffic.

Reference point between the 5G-RG and the W-AGF which transports the user plane traffic and the N1 NAS protocol. The definition of this interface is outside the scope of 3GPP.

Reference point between the FN-RG and the W-AGF. The definition of this interface is outside the scope of 3GPP.

Reference point between the UE and the TNAP. See e.g. Figure 4.2.8.2.1-2.

Yt'

Reference point between the N5CW devices and the TWAP. It is defined in clause 4.2.8.5.

NWu

Reference point between the UE and N3IWF for establishing secure tunnel(s) between the UE and N3IWF so that control-plane and user-plane exchanged between the UE and the 5G Core Network is transferred securely over untrusted non-3GPP access.

NWt

Reference point between the UE and the TNGF. A secure NWt connection is established over this reference point, as specified in clause 4.12a.2.2 of TS 23.502. NAS messages between the UE and the AMF are transferred via this NWt connection.

A reference point between the TNAP and the TNGF, which is used to support an AAA interface. Ta requirements are documented in clause 4.2.8.3.2.

A reference point between two TNGFs, which is used to facilitate UE mobility between different TNGFs (inter-TNGF mobility).

Tn and inter-TNGF mobility are not specified in this Release of the specification.

4.2.8.3.2 Requirements on Ta |R16| p. 64

Ta shall be able to

Carry EAP-5G traffic and user location information before the NWt connection is established between the UE and the TNGF.
Allow the UE and the TNGF to exchange IP traffic.

In deployments where the TNAP does not allocate the local IP addresses to UE(s), Ta shall be able to:

Allow the UE to request and receive IP configuration from the TNAN (including a local IP address), e.g. with DHCP. This is to allow the UE to use an IP stack to establish a NWt connection between the UE and the TNGF.

In this Release of the specification, Ta is not specified.