name: DCCF
full_form: Data Collection Coordination Function
context: As depicted in Figure 4.2.16-1, the 5G System architecture allows user plane information exposure to some NFs via service-based interface in UPF. Figure 4.2.16-1: Architecture to support User Plane Information Exposure via a service-based interface NOTE 1: In this Release of the specification, only NWDAF/DCCF/MFAF, NEF/AF and TSNAF/TSCTSF are considered as the receiver of the UPF event notifications. NOTE 2: UPF information exposure is not restricted to SBI interface, i.e. reporting via PFCP over N4 to SMF is still applicable. Not all events can be subscribed to UPF directly. The details and constraints for the subscription to UPF event exposure service (i.e. direct vs. indirect) and the information exposed to certain NFs by UPF, as well as the information contained in the event notifications, are defined in clause 5.2.26.2 of TS 23.502[ Procedures for the 5G System (5GS) ]  [3] and clause 5.8.2.17.
description: The Data Collection Coordination Function (DCCF) is a network function within the 5G system architecture that plays a role in coordinating data collection, specifically in relation to user plane information exposure via service-based interfaces. It works alongside other network functions such as NWDAF and MFAF to receive event notifications from the User Plane Function (UPF), facilitating the management and utilization of user plane data within the 5G system.
explanation: DCCF is classified as a Network Function because it participates in the coordination and collection of data, integrating with other network functions like NWDAF and MFAF to support the exposure of user plane information. This aligns with the 3GPP's specifications for efficient data management within the 5G system architecture.
section_title: 4.2.16 Architecture to support User Plane Information Exposure via a service-based interface
biotag_Context: O,O,O,O,O,O,B-Technology,I-Technology,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,B-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,O,O,O,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,B-Interface,O,O,O,O,B-Protocol,O,B-Interface,O,B-Network Function,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,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,O,O,B-Technology,I-Technology,O,O,O,O,O,O
biotag_Description: O,B-Network Function,I-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,B-Technology,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,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,O,O,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O