Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Management

DCCF

Data Collection and Coordination Function

Management →

DCCF is the 5G network function that centrally manages the collection, storage, and policy-driven exposure of network analytics data between producers and consumers for AI/ML and optimization.

Introduced
Rel-17
Where
Core Network › 5G Core
Specifications
18 specs
DCCF Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Data Collection and Coordination Function (DCCF) is a critical management function within the 5G Service-Based Architecture (SBA), specifically designed to handle the lifecycle of data collection for network analytics and automation. Architecturally, it sits between data producers—such as Network Functions (NFs), Operations, Administration and Maintenance (OAM) systems, and User Equipment (UE)—and data consumers like the Network Data Analytics Function (NWDAF) or external Application Functions (AFs). The DCCF does not perform analytics itself but focuses on the orchestration of data flows: it receives data collection requests from consumers, translates them into actionable tasks for producers, aggregates the collected data, and stores it in a structured manner, often in coordination with a Data Storage Network Function (DSF).

Operationally, the DCCF works through a set of standardized interfaces (e.g., Ndcf_DataCollectionManagement) defined in 3GPP specifications. When an analytics consumer (e.g., an NWDAF instance training a model for load prediction) needs specific data, it sends a data collection request to the DCCF. This request includes parameters such as data type (e.g., UE mobility patterns, slice load metrics), collection granularity, frequency, and target data producers. The DCCF then evaluates this request against policies—which may define data access rights, privacy constraints, or network load considerations—and, if authorized, coordinates with the relevant producers to initiate data collection. It can handle both subscription-based (continuous) and request-response (one-time) data collection models.

Key components of the DCCF include its policy enforcement mechanism, data aggregation logic, and storage coordination capabilities. The policy enforcement component ensures that data collection complies with regulatory (e.g., GDPR), network (e.g., load balancing), and business (e.g., data sharing agreements) policies. The aggregation logic consolidates raw data from multiple sources—which might be heterogeneous in format or timing—into a unified, timestamped dataset suitable for analytics. Storage coordination involves managing the lifecycle of collected data in the DSF, including retention periods, indexing, and exposure to consumers. The DCCF also provides status notifications about data collection jobs (e.g., completion, failures) to consumers.

In the broader network ecosystem, the DCCF plays a foundational role in enabling data-driven automation and closed-loop operations in 5G and beyond. By decoupling data collection from analytics, it allows analytics functions to be more lightweight and focused on model execution, while the DCCF handles the heavy lifting of data sourcing and management. This separation of concerns improves scalability, as a single DCCF can serve multiple NWDAF instances or external AFs. Moreover, the DCCF facilitates network slicing by allowing slice-specific data collection policies—ensuring that data from one slice is not inadvertently exposed to analytics processes of another slice. Its integration with the 5G SBA ensures it can leverage existing service registration, discovery, and security mechanisms (e.g., via the NRF and SCP).

Purpose & Motivation

The DCCF was created to address the escalating complexity and volume of data required for AI/ML-driven network automation in 5G. Prior to Release 17, data collection for analytics was largely ad-hoc: each analytics function (like NWDAF) had to directly interface with data producers, leading to redundant data requests, inconsistent data formats, and inefficient network resource usage. For example, two NWDAF instances predicting congestion and optimizing handovers might separately request similar UE mobility data from the same AMF, doubling signaling overhead. There was also no centralized mechanism to enforce policies on data access or privacy across multiple analytics consumers, raising compliance risks.

Historically, network management relied on static OAM systems with periodic reporting, but 5G's dynamic nature—with features like network slicing, edge computing, and ultra-reliable low-latency communication (URLLC)—demands real-time, granular data for proactive optimization. The limitations of previous approaches became evident as operators deployed NWDAF for use cases like load balancing and anomaly detection; without a coordinator, the network faced scalability bottlenecks, especially with the proliferation of Internet of Things (IoT) devices and network slices generating terabytes of data daily.

The DCCF solves these problems by introducing a standardized, centralized data collection framework. It reduces signaling overhead by aggregating requests and distributing data efficiently, ensures policy compliance through a unified enforcement point, and provides a consistent data model (aligned with 3GPP specifications) that simplifies analytics development. Its creation was motivated by the industry's shift toward intent-based networking and autonomous operations, where reliable, high-quality data is the fuel for AI/ML models. By decoupling data collection from analytics, the DCCF future-proofs the network for emerging applications like digital twins, immersive services, and 6G research, which will require even more diverse and voluminous data sets.

What changed in its specifications

The latest release-to-release comparison of specifications that define DCCF. Each summary describes the whole specification, not only this term.

TS 23.501Rel-18 → Rel-19

Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.

Full comparison in TS 23.501 →
TS 23.503Rel-18 → Rel-19

Rel-19 TS 23.503 adds Network Slice Replacement and Energy Saving Indicator reporting, Application Function influence on payload header handling, and Local Offloading Management Policy for edge computing. It also adds ATSSS Phase 4 multi-access steering (MPQUIC-E, ATSSS-LL), spending-limit policy for roaming, and PCF use of network analytics.

Full comparison in TS 23.503 →

Technology family

Network exposure and analytics · Core Network

  1. Rel-11 SCS/AS
  2. Rel-13 IWK-SCEF, SCEF
  3. Rel-15 CAPIF, NEF, NWDAF
  4. Rel-16 SCEF+NEF
  5. Rel-17 ADRF, AnLF, DCCF, L-NEF, MDAF, MFAF, MTLF
  6. Rel-18 RE-NWDAF
  • DCCF used together with ADRF
    “Based on the NF request or configuration on the DCCF, the DCCF may determine the ADRF and interact directly or indirectly with the ADRF to request or store data or analytics.” TS 23.288
  • DCCF used together with MFAF
    “The MFAF selection function is supported by the DCCF. The DCCF shall utilize the NRF to discover MFAF instance(s) unless MFAF information is available by other means, e.g. locally configured on the DCCF.” TS 23.501
  • DCCF used together with NWDAF
    “The functionalities provided by DCCF and/or ADRF can also be hosted by an NWDAF.” TS 23.501

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 3 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-17 introduced

Rel-17 defines the DCCF as a new network function, with its architecture, Ndccf data management services, discovery, and data collection and analytics subscription procedures.

  • “The Data Collection Coordination Function (DCCF) supports the following functionality:” TS 23.501 v17.15.0
  • “When the DCCF receives a request for data, it determines the status of data collection from the Data Source.” TS 23.288 v17.12.0
  • DCCF services definition TS 23.288CR0308
Rel-18 1 CR

Rel-18 adds DCCF relocation, transferring UE data subscriptions from source to target DCCF, plus user consent checking, event muting, immediate reporting and storage handling in DCCF data management.

  • “the DCCF supports requesting the transfer of a UE data subscription from source DCCF to target DCCF.” TS 29.574 v18.12.0
  • “the DCCF shall mute the event notification and store the available events until the NF service consumer requests to retrieve them” TS 29.574 v18.12.0
  • eNA_Ph3 DCCF relocation in TS 23.288 TS 23.288CR0630
Rel-19 specification text

DCCF APIs and behaviour were corrected and extended: the DCCF data subscription gained stored-event return on deletion and new notification attributes, Fetch changed to HTTP POST, and the N117 SCP-DCCF reference point was added.

  • “The Individual DCCF Data Subscription resource matching the subscriptionId was deleted and including the stored unsent data events in the response.” TS 29.574 v19.7.0
  • “The Data Consumer invokes the Ndccf_DataManagement_Fetch service operation by sending an HTTP POST request message” TS 29.552 v19.7.0
  • “N117: Reference point between SCP and DCCF.” TS 23.501 v19.9.0

Defining Specifications

3GPP specifications that define or reference DCCF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.501 vk30 5G System Architecture Rel-20 read
TS 23.503 vk30 5G Policy and Charging Control Framework Rel-20 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TS 29.503 vk10 UDM Service Based Interface Rel-20 read
TS 29.508 vk10 Session Management Event Exposure Service Rel-20 read
TS 29.514 vk10 Policy Authorization Service Rel-20 read
TS 29.517 vk10 AF Event Exposure Service Rel-20 read
TS 29.518 vk10 AMF Service Based Interface Rel-20 read
TS 29.520 vk10 5G NWDAF Services Rel-20 read
TS 29.536 vk10 Nnsacf Network Slice Admission Control Rel-20 read
TS 29.552 vk10 5G Network Data Analytics Procedures Rel-20 read
TS 29.564 vk10 Nupf Service Based Interface Rel-20 read
TS 29.574 vk10 DCCF Service Based Interface Rel-20 read
TS 29.575 vk10 ADRF Service Based Interface Rel-20 read
TS 29.576 vk10 MFAF Service Based Interface Rel-20 read
TS 29.591 vk10 NEF Southbound Services Rel-20 read
TS 29.889 vj10 Study on UPF data collection for AI/ML Rel-19 read
TS 33.794 vj10 Study on Zero Trust Security Enablers for 5G Rel-19 read