name: TNGF
full_form: Trusted Non-3GPP Gateway Function
context: non-3GPP access, with the following modifications: - The N3IWF in Figure 5.2.2.13.2.1 should be substituted with a TNGF and the Untrusted non-3GPP access should be substituted with a Trusted non-3GPP Access Point (TNAP). - Charging Data Request [Initial/Update] contains RAT type and user location specifics to trusted non-3GPP. - The TNGF may send a TNGF Identities parameter to AMF inside an N2 Uplink NAS Transport message. The TNGF Identities parameter contains a list of identifiers (i.e. FQDNs or IP addresses) of N3 terminations supported by the TNGF. If received by the AMF, it shall forward it to the SMF, which may use it as input to UPF selection.
description: The Trusted Non-3GPP Gateway Function (TNGF) is a network component that facilitates communication between trusted non-3GPP access networks and the 5G core network. It plays a crucial role in PDU session establishment, charging data collection, and UPF selection.
explanation: TNGF is classified as a Network Function based on its role in managing communication between trusted non-3GPP access networks and the 5G core network, as described in the context from 3GPP TS 32.255.
section_title: 5.2.2.13.2PDU session establishment
biotag_Context: O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,I-Network Function,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Network Function,O,O,O,B-Network Function,O,O,B-Interface,B-Connection,B-Protocol,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,B-Interface,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O
biotag_Description: O,B-Network Function,I-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,B-Network Function,O