Skip to main content
User Data Collection and Reporting

Architecture

TS 26.531 defines a generic reference architecture for data collection, reporting and exposure of UE data: the logical functions involved and the reference points between them. It is intended to be instantiated in domain-specific ways. TS 26.501 instantiates it for 5G Media Streaming.

At a glance
  • Reference points: R1 provisioning, R2 to R4 configuration and data reporting, R5 and R6 event exposure, R7 a client API on the UE.
  • Services and deployment: the Data Collection AF may sit inside or outside the trusted domain; outside it, the NEF exposes its events.
  • In 5GMS: the Data Collection AF sits in the 5GMS AF; provisioning moves to M1, and reports travel over M5.

The generic architecture​

Generic architecture
Reference architecture for data collection and reporting in reference point notationRedrawn from TS 26.531 V19.0.0, figure 4.2-1
In 5G Media Streaming
Data collection and reporting architecture instantiation for 5G Media StreamingRedrawn from TS 26.501 V20.0.0, figure 4.7.1-1

Click a figure to enlarge it. The data collection roles are shown in rose.

FunctionRole
Data Collection AFManages the provisioning state for data collection and reporting, processes collected UE data, and realises the Event Exposure Service (TS 26.531 V19.0.0 clause 4.2 (item 2)). When its provisioning state changes, it updates its NF profiles in the NRF.
Provisioning AFProvisions data collection and reporting at R1 (TS 26.531 V19.0.0 clause 4.2 (item 1)). It belongs to the Application Service Provider and may be deployed inside or outside the trusted domain.
Direct Data Collection ClientCollects relevant data in the UE and sends data reports at R2, according to a configuration it first obtains at R2 (TS 26.531 V19.0.0 clause 4.2 (item 3)) (TS 26.531 V19.0.0 clause 4.2 (item 3, NOTE 7)). It can be a common middleware component or part of each UE Application.
UE ApplicationShares relevant data with the Direct Data Collection Client at R7 (TS 26.531 V19.0.0 clause 4.2 (item 4)).
Indirect Data Collection ClientA subfunction of the Application Service Provider that sends data reports at R3, for data the provider collected from UE Applications at R8 (TS 26.531 V19.0.0 clause 4.2 (item 5)) (TS 26.531 V19.0.0 clause 4.2 (item 5, NOTE 10)). It may modify the collected data to meet its configuration.
Application Server (AS)Collects data and reports it at R4 (TS 26.531 V19.0.0 clause 4.2 (item 6) and clause 4.3, NOTE 3). It plays the role of a Network Function when it does so.
NWDAFThe primary consumer of processed UE data (R5) (TS 26.531 V19.0.0 clause 4.2 (item 7)).
Event Consumer AFReceives data reporting events at R6 (TS 26.531 V19.0.0 clause 4.2 (item 8)). It resides in the Application Service Provider.

Reference points​

Reference pointBetweenPurposeService
R1Provisioning AF and Data Collection AF (TS 26.531 V19.0.0 clause 4.3 (R1 bullet))What data is collected, how it is sampled and reported, how it is processed, and how it is exposed to event subscribers (TS 26.531 V19.0.0 clause 4.3 (R1 bullet))Ndcaf_DataReportingProvisioning
R2Direct Data Collection Client and Data Collection AFObtain the configuration, then send data reports (TS 26.531 V19.0.0 clause 4.3 (R2 bullet)) (TS 26.531 V19.0.0 clause 4.3 (R2 bullet) and clause 4.5.1). An encrypted data transfer protocol is required.Ndcaf_DataReporting
R3Indirect Data Collection Client and Data Collection AF (TS 26.531 V19.0.0 clause 4.3 (R3 bullet))Obtain the configuration, then send data reports (TS 26.531 V19.0.0 clause 4.3 (R3 bullet))Ndcaf_DataReporting
R4AS and Data Collection AF (TS 26.531 V19.0.0 clause 4.3 (R4 bullet))Obtain the configuration, then send data reports (TS 26.531 V19.0.0 clause 4.3 (R4 bullet))Ndcaf_DataReporting
R5NWDAF and Data Collection AF (TS 26.531 V19.0.0 clause 4.3 (R5 bullet))Subscribe to data reporting events and receive notifications (TS 26.531 V19.0.0 clause 4.3 (R5 bullets))Naf_EventExposure (or Nnef_EventExposure across trust domains) (TS 26.531 V19.0.0 clause 4.3 (R5 bullets) and clause 4.4 (item 4))
R6Event Consumer AF and Data Collection AF (TS 26.531 V19.0.0 clause 4.3 (R6 bullet))Subscribe to data reporting events and receive notifications (TS 26.531 V19.0.0 clause 4.3 (R6 bullets))Naf_EventExposure
R7UE Application and Direct Data Collection ClientA client API on the UE. Not used when the client is embedded in the UE Application.Specified in TS 26.532, clause 8
R8UE Application and Application Service Provider server (TS 26.531 V19.0.0 clause 4.3 (R8 bullet))Data collection between the application and its provider (TS 26.531 V19.0.0 clause 4.3 (R8 bullet))Beyond 3GPP standardisation

R2 runs in the user plane, so it does not traverse the 5G System service bus (TS 26.531 V19.0.0 clause 4.4, NOTE 2).

Where the Data Collection AF is deployed​

TS 26.531 documents five collaboration scenarios. Reference point R2 traverses the data plane in all of them.

ScenarioDeployment
AAll functions inside the trusted domain (TS 26.531 V19.0.0 clause A.2).
BThe Application Service Provider functions outside the trusted domain; their interactions with the Data Collection AF are mediated by the NEF (TS 26.531 V19.0.0 clause A.3).
CAs B, with the AS also outside the trusted domain (TS 26.531 V19.0.0 clause A.4).
DThe Data Collection AF itself outside the trusted domain; it registers with the NRF via the NEF, and the NWDAF uses Nnef_EventExposure to subscribe to its events (TS 26.531 V19.0.0 clause A.5).
EThe Direct Data Collection Client deployed as a subfunction of the UE Application (TS 26.531 V19.0.0 clause A.6). It can be combined with any of the other scenarios.

When a function is outside the trusted domain, the NEF exposes the services under its own names: Nnef_DataReportingProvisioning to Provisioning AFs, Nnef_DataReporting to Indirect Data Collection Clients and Application Servers, and Nnef_EventExposure to Event Consumer AFs (TS 26.531 V19.0.0 clause 4.7.1). When the Data Collection AF itself is outside the trusted domain, the interactions at R1′, R3′, R4′ and R6′ are outside the scope of 3GPP and are expected to be functionally equivalent to those at R1, R3, R4 and R6 (TS 26.531 V19.0.0 clause A.5 and clause 4.4).

In 5G Media Streaming​

TS 26.501 maps the abstract roles onto 5GMS functions.

Role in TS 26.531In 5GMS
Application Service ProviderThe 5GMS Application Provider
Data Collection AFInstantiated in the 5GMS AF
Direct Data Collection ClientInstantiated in the Media Session Handler. It takes logical responsibility for the Metrics Collection & Reporting and Consumption Collection & Reporting subfunctions, and for logging ANBR-based Network Assistance invocations.
ASThe 5GMS AS, deployed as a trusted AS within the 5G System or externally
Event Consumer AFInstantiated in the 5GMS Application Provider
Provisioning AFNot instantiated; data collection is provisioned with the 5GMS procedures
Indirect Data Collection ClientNot instantiated; indirect reporting is outside the scope of 5G Media Streaming
Reference pointIn 5GMS
M1Provisioning of data collection and reporting in the Data Collection AF (R1 is not instantiated)
M5Direct data reporting of QoE metrics and consumption, via the Media Session Handler and the 5GMS AF
R2Direct data reporting of ANBR-based Network Assistance invocations to the Data Collection AF
R4Media streaming access reporting by the 5GMS AS
R5Event exposure to subscribing NWDAF instances
R6Event exposure to subscribing Event Consumer AF instances in the 5GMS Application Provider
M6Configuration of 5GMS-related data reporting by the 5GMS-Aware Application
R3, R7, R8Not instantiated

Release differences​

  • TS 26.531: the figures are the same in Release 17, 18 and 19.
  • TS 26.501, Release 17: R2 is not instantiated; all direct reporting is logically realised through M5. Figure 4.7.1-1 has no Network Assistance subfunction and no R2 line.
  • TS 26.501, from Release 18: R2 carries ANBR-based Network Assistance invocations, and the Media Session Handler takes responsibility for logging them.
Sources for this page
  • The generic architecture: TS 26.531 V19.0.0, clause 4.1 and clause 4.2, items 1 to 8, NOTE 7 and NOTE 10.
  • Reference points: TS 26.531 V19.0.0, clause 4.3 (R1 to R8, NOTE 3, NOTE 4, NOTE 5), clause 4.4 (services, NOTE 2) and clause 4.5.1.
  • Where the Data Collection AF is deployed: TS 26.531 V19.0.0, annex A, clauses A.1 to A.6, and clauses 4.4 and 4.7.1.
  • In 5G Media Streaming: TS 26.501 V20.0.0, clause 4.7.1 (role list and reference point definitions).
  • Figures: redrawn from TS 26.531 V19.0.0, figure 4.2-1, and TS 26.501 V20.0.0, figure 4.7.1-1.
  • Release differences: image files compared in TS 26.531 V17.3.0, V18.2.0 and V19.0.0; TS 26.501 V17.10.0 and V19.4.0, clause 4.7.1 and figure 4.7.1-1.