5.4 Procedures for configuring data collection client

26.5313GPPData Collection and ReportingGeneral description and architectureRelease 17TS

At some later point, one or more of the three types of data collection client obtain their configuration from the Data Collection AF by invoking the Ndcaf_DataReporting service defined in the present document and specified in TS 26.532 [7]. The intersection between the above provisioning information and current event consumer subscriptions determines the contents of this configuration.

Figure 5.4‑1: High-level procedures for data collection client configuration phase

The steps are as follows:

9. If present in the instantiation, the UE Application creates a data collection and reporting context with the Direct Data Collection Client. As part of this context, the UE Application may indicate consent for a UE identifier to be included in data reports submitted on its behalf by the Direct Data Collection Client.

10. As a consequence of step 9 or (if the UE Application is not present) during its own initialisation, the Direct Data Collection Client acquires its data collection and reporting configuration from the Data Collection AF, if relevant.

If the UE Application is instantiated, the Direct Data Collection Client provides it with a data collection and reporting configuration derived from that just obtained from the Data Collection AF.

11. The Indirect Data Collection Client acquires its data collection and reporting configuration from the Data Collection AF, if relevant.

12. The AS acquires its data collection and reporting configuration from the Data Collection AF, if relevant.

Whenever the provisioning information changes, or the set of event exposure subscriptions changes, a new set of data collection and reporting configuration shall be made available to data collection clients by the Data Collection AF.