Skip to main content
User Data Collection and Reporting

Implementation Detail

In short
  • Which specification the code follows: the Release 18 API definitions of TS 26.532 as published by 3GPP at its TSG meeting 105, which is the default of the build. The audit judges every statement of TS 26.531 and TS 26.532 valid in Releases 17 to 19 (no Release 20 change is known).
  • Generic framework: a Data Collection AF library and a standalone AF serve R1, R2 to R4, R5 and R6. No data collection client is provided.
  • In 5G Media Streaming: the Data Collection AF library is designed to be embedded in the 5GMS Application Function. That integration is not yet part of the main branch of the 5GMS Application Function, so no 5GMS data is collected or exposed yet.
  • Source of this page: an audit of the main branch of the Data Collection AF repository on 2026-10-20: each requirement split into the cases its clause defines, each case read against the code by one reader and then independently by a second, with a third reading where they disagreed. Cases that depend on the Open5GS framework layer, which is not part of the repository, are not shown.

For what the specifications define, see the Technology page. For how to run the tools, see the Tutorials. The Standards are on the Data Collection standards page.

Architecture​

The generic architecture and its 5G Media Streaming instantiation, with the parts the Reference Tools provide and the status of each reference point.

Generic architecture
Data collection reference architecture, with Reference ToolsBased on TS 26.531 V19.0.0, figure 4.2-1
In 5G Media Streaming
Data collection in 5G Media Streaming (Release 17), with Reference ToolsBased on TS 26.501 V17.10.0, figure 4.7.1-1, the release the 5GMS AF is built against

Click a figure to enlarge it.

Generic framework​

Each feature, split into its requirements and each requirement into the cases its clause defines: what works, what does not, and why. Open a feature, then a requirement.

  • UE Data Collection, Reporting and Event Exposure.
  • DCAF (Data Collection AF (library and standalone application)): rt-data-collection-application-function.
  • DC client (Data Collection Client (none exists; the repository's test scripts exercise the APIs)): .
  • Source: code read against every statement of the specifications on the project page; statements a component cannot meet by construction marked absent by group, 2026-10-20.
  • Not shown: 16 further cases (a specification or code outside the audit that could not be read).
3GPP release
300 of 532 implemented · 51 differ · 181 absentcases, over 164 requirements

✓ Implemented≠ Differs from the specification– Absent? Specification inconsistent: its text and its OpenAPI or tables disagreei Noted: observed, not a verdict against a clause

Provisioning104 of 162 implemented · 21 differ · 37 absent
Data Access Profiles5 of 7 implemented · 1 differs · 1 absent
Sampling and reporting rules48 of 65 implemented · 8 differ · 9 absent
Event exposure9 of 13 implemented · 1 differs · 3 absent
Data reports and data domains113 of 185 implemented · 12 differ · 60 absent
Client configuration and reporting sessions9 of 42 implemented · 2 differ · 31 absent
The features3 of 17 implemented · 4 differ · 10 absent
General7 of 19 implemented · 2 differ · 10 absent

Integration with 5G Media Streaming​

The Data Collection AF library is designed to be embedded in the 5GMS Application Function; that integration is not yet merged into the main branch of the 5GMS Application Function. See the Media Streaming and Advanced Media Delivery: Implementation status page for the 5GMS side.

Full audit for members

This page summarises a requirement-by-requirement audit of the code. The full audit (each requirement with its clause quoted, the code that meets or misses it, and the findings) is available to 5G-MAG members through Developer Tools (the Standards2Deployments repository).

Become a member · Request access

Implementation status​

The Data Collection AF (repository cards are on the project page).

  • Implemented: creating, reading and deleting Provisioning Sessions, Data Reporting Configurations and Data Reporting Sessions; communication reports; time-window aggregation; context identifiers on rules and conditions; event subscription and notification at R5 and R6; registration of an AF profile with the NRF at start-up.
  • Needs fix: replacing a Data Reporting Configuration does not store it; the code returns 201 (Created) when a session or configuration is read, where the specification gives 200 (OK); the aggregation function names MAXIMUM and MINIMUM of the specification are not accepted (the code expects MIN and MAX), and COUNT is not accepted for communication records; an empty list of event consumer types matches no consumer; the event time stamp is the time of the notification, not of the record; default values for omitted sampling and reporting rules are not applied; a few property names differ from the specification (location, downlinkThrougput).
  • Not implemented: PATCH, user and location restrictions, record types other than communication (a report with another type is accepted and not stored), redirects, the CORS headers, updating the NRF profile when provisioning changes, and a Direct, Indirect or AS data collection client.

Used with other projects​

The Data Collection AF library is designed to be used by the Media Streaming and Advanced Media Delivery Application Function; see the 5G Media Streaming section above for the state of that integration.