name: TDF
full_form: Traffic Detection Function
context: TDF collects charging information per user per TDF session. TDF session charging allows the TDF to collect charging information related to data volumes sent to and received by the UE/MS for the timeframe since the establishment till the termination of TDF session. The user can be identified by MSISDN and/or IMSI, while the TDF session can be determined by a unique identifier generated by the P-GW (an "EPS default bearer Charging Identifier" for GTP based connectivity or an "unique Charging Id" for PMIP based connectivity when establishing TDF session. TDF session specific offline charging in TDF is achieved by ABC offline charging, with a vendor specific rating group/service identifier associated with the TDF session.The main collected information items are duration of the TDF session and data volume transferred during the lifetime of the TDF session. When Charging per TDF session is active, the following chargeable events are defined: - Start of TDF session. Upon encountering this
description: The Traffic Detection Function (TDF) is a network component responsible for collecting charging information related to data volumes sent to and received by the User Equipment (UE)/Mobile Station (MS) during a TDF session. It plays a crucial role in enabling per-session charging, allowing for the collection of specific charging information for each user's data transmission.
explanation: TDF is classified as a Network Function because it operates within the network to collect and manage charging information on a per-user, per-session basis. The context highlights its involvement in charging processes, session management, and interaction with other network elements like the P-GW.
section_title: 5.2.1.9.2Charging per TDF session
biotag_Context: B-Network Function,O,O,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,B-Network Function,O,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,O,O,O,O,O,O,B-Parameter,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,O,B-Network Function,O,O,O,B-Service,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O
biotag_Description: O,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,I-Device,O,B-Parameter,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O