4 Reference architecture for data collection and reporting

26.5313GPPData Collection and ReportingGeneral description and architectureRelease 17TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

4.1 General

Clause 6.2.8 of TS 23.288 [4] envisages a set of high-level procedures by which data is collected by a Network Data Analytics Function (NWDAF) from UE Application(s) via an intermediary Application Function. This clause defines a generic reference architecture for data collection and reporting that satisfies those procedures, including the logical functions involved and the logical reference points between them. The intermediary Application Function envisaged in [4] is here named the Data Collection AF.

It is intended that this reference architecture be instantiated in domain-specific ways to suit the needs of different features of the 5G System. The reference architecture may be instantiated separately in different slices of a network.

The services defined in the present document may be exposed to parties outside the trusted domain via the NEF, as defined in clause 4.7.1.

The Data Collection AF may support CAPIF [8] to provide APIs to other applications (i.e. API invokers), as defined in clause 4.7.2.

4.2 Functional entities for data collection and reporting

Figure 4.2‑1 below shows the reference architecture for data collection and reporting using reference point notation.

NOTE: The Data Collection AF may be deployed outside the trusted domain, in which case the services it exposes to API invokers are mediated by the NEF. The logical relationships denoted by the reference points are unaffected by such deployment choices.

Figure 4.2‑1: Reference architecture for data collection and reporting in reference point notation

The functional entities illustrated in the figure are described as follows:

1. Data collection and reporting functionality is provisioned at reference point R1 by a Provisioning AF of the Application Service Provider that may be deployed either inside or outside the trusted domain. The Ndcaf_DataReportingProvisioning service is provided by the Data Collection AF for this purpose.

NOTE 1: When provisioning is initiated from outside the trusted domain via the NEF, the Provisioning AF instead invokes the Nnef_DataReportingProvisioning service.

2. The Data Collection AF may be deployed inside or outside the trusted domain. It is responsible for managing the provisioning state for data collection and reporting. When its provisioning state changes, the Data Collection AF updates the set of available NF profile(s) in the NRF by invoking the Nnrf_NFManagement service defined in clause 5.2.7.2 of TS 23.502 [3] according to the usage defined in clause 6.2.8.2.2 of TS 23.288 [4] and specified in clause 6.1 of TS 29.510 [6].

NOTE 2: If the Data Collection AF is deployed outside the trusted domain, this registration occurs via the NEF, as described in clause 6.2.2.3 of TS 23.288 [4].

Depending on the provisioning information provided by the Application Service Provider (see clause 4.6.2), the Data Collection AF provides a data collection and reporting configuration to the Direct Data Collection Client at reference point R2, to the Indirect Data Collection Client at reference point R3 or to the Application Server (AS) instances at reference point R4, and receives data reports from them respectively at those same reference points.

The Data Collection AF processes received data reports according to processing instructions in its provisioning state. The processing activities include, but are not limited to, reporting format conversion, data normalisation, reporting domain-specific anonymisation of data and (dis)aggregation of data into reports to be exposed as events.

Finally, the Data Collection AF is responsible for exposing processed UE data to event notification subscribers both inside the trusted domain (such as the NWDAF) and outside it (such as the Event Consumer AF in the Application Service Provider). In this role, the Data Collection AF realises the Event Exposure Service as defined in clause 6.2.2.1 of TS 23.288 [4] and as specified in TS 29.517 [5]. Subscribers fulfil the role of NF consumers of this service in the service-based architecture [2, 3].

The set of UE data to be collected and exposed by the Data Collection AF is determined by the intersection^[1] between its provisioning state provided at R1 and the current set of subscriptions. This is reflected in the data collection and reporting configuration exposed at reference points R2, R3 and R4, and the subscription-driven event notifications sent to consumer entities such as the NWDAF or Event Consumer AF of an Application Service Provider over reference points R5 and R6. The Data Collection AF is responsible for ensuring that access to UE data is controlled according to the rules indicated in its provisioning state.

NOTE 3: When the Data Collection AF is deployed outside the trusted domain, the NWDAF uses the procedure defined in clause 5.2.6.2 of TS 23.502 [3] and further elaborated by clause 6.2.2.3 of TS 23.288 [4] to collect data from the externally deployed Data Collection AF via the NEF.

NOTE 4: The Data Collection AF is intended to be instantiated inside another Application Function in order to satisfy the domain-specific data collection and reporting requirements corresponding to particular features in the 5G System. As such, there may be several reoprting domain-specific Data Collection AF instances operating simultaneously in a particular 5G System, each one performing a different role. The definitions of these instantiations are beyond the scope of the present document.

3. The Direct Data Collection Client is responsible for collecting relevant data in the UE and for sending data reports to the Data Collection AF via reference point R2 using the Ndcaf_DataReporting service according to a data collection and reporting configuration that it has previously obtained from the Data Collection AF by invoking the same service at reference point R2.

NOTE 5: This method of reporting corresponds to the direct data collection procedure defined in clause 6.2.8 of TS 23.288 [4].

NOTE 6: In the case where the Data Collection AF is deployed in a different trust domain than the UE, the Direct Data Collection Client instead invokes the equivalent Nnef_DataReporting API via the NEF.

NOTE 7: The Direct Data Collection Client function is intended to be instantiated inside other UE functions in order to satisfy the domain-specific data collection and reporting requirements corresponding to particular features of the 5G System. As such, there may be several reporting domain-specific data collection client instances operating simultaneously on a given UE, each one performing a different role. One valid deployment option is to combine these instances in a common middleware component. Another option is to provide the Direct Data Collection Client as an integral part of each relevant UE Application. The definitions of these instantiations are beyond the scope of the present document. The realisation of these logical functions is implementation-dependent.

4. The UE Application is responsible for sharing relevant data with the Direct Data Collection Client via reference point R7. This may be achieved as a combination of application design, application configuration via R8 and/or application configuration via R7.

5. An Application Service Provider may also collect data from UE Applications via reference point R8 and employ an Indirect Data Collection Client subfunction to then send data reports to the Data Collection AF via reference point R3 by invoking the Ndcaf_DataReporting service according to a data collection and reporting configuration that it has previously obtained from the Data Collection AF by invoking the same service at reference point R3.

NOTE 8: This method of reporting corresponds to the indirect data collection procedure defined in clause 6.2.8 of TS 23.288 [4].

NOTE 9: In the case where the Application Service Provider server is deployed in a different trust domain than the Data Collection AF, the Indirect Data Collection Client instead invokes the equivalent Nnef_DataReporting API via the NEF at reference point R3.

NOTE 10: Collection of UE data via reference point R8 and processing by the Application Server Provider are outside 3GPP scope. The Indirect Data Collection Client may modify the collected UE data to satisfy the requirements of its data collection and reporting configuration.

6. Application Server instances (labelled AS) inside or outside the trusted domain may also collect data and report it to the Data Collection AF via reference point R4 by invoking the Ndcaf_DataReporting service, according to a data collection and reporting configuration previously obtained from the Data Collection AF by invoking the same service at reference point R4.

NOTE 11: In the case where the Application Server is deployed in a different trust domain than the Data Collection AF, the AS instead invokes the equivalent Nnef_DataReporting service via the NEF.

NOTE 12: The data collection and reporting requirements for such Application Servers are reporting domain-specific and therefore beyond the scope of the present document.

7. The NWDAF is the primary consumer of processed UE data. This is exposed to the NWDAF by the Data Collection AF in the form of data reporting event notifications via reference point R5 using the Naf_EventExposure service (as specified in TS 29.517 [5]) after any processing by the Data Collection AF has been performed according to its provisioned processing instructions.

NOTE 13: If the Data Collection AF is deployed outside the trusted domain, this interaction occurs instead by invoking the Nnef_EventExposure service via the NEF, as defined in clause 5.2.6.2 of TS 23.502 [3] and as further elaborated by clause 6.2.2.3 of TS 23.288 [4].

NOTE 14: The UE data of interest to the NWDAF at reference point R5, for example Observed Service Experience and Collective Behaviour, is governed by clause 6 of TS 23.288 [4].

8. By means of appropriate data collection and reporting provisioning, certain UE data may also be exposed in the form of data reporting events by the Data Collection AF to an Event Consumer AF residing in the Application Service Provider via reference point R6 using the Naf_EventExposure service defined in clause 5.2.19 of TS 23.502 [4] and specified in TS 29.517 [5].

NOTE 15: In the case where the Application Service Provider server is deployed outside the trusted domain, the Nnef_EventExposure service, as defined in clause 5.2.6.2 of TS 23.502 [3], is invoked instead.

4.3 Reference points for data collection and reporting

The purposes of the reference points in the functional architecture defined in clause 4.2 above are as follows:

– R1 supports the following interactions between a Provisioning AF in the Application Service Provider and the Data Collection AF:

– Used by the Application Service Provider to provision data collection and reporting in a Data Collection AF instance by means of the Ndcaf_DataReportingProvisioning service defined in clause 4.4 of the present document (or else the equivalent service exposed by the NEF if the two functions are deployed in different trust domains). The provisioning information specifies what data is to be collected by data collection clients, how it is to be processed by the Data Collection AF and how it is to be exposed to event notification subscribers. A generic provisioning envelope for data collection and reporting is defined in clause 4.6 of the present document, but this is expected to be extended by individual reporting domains.

– R2 supports the following interactions between the Direct Data Collection Client in the UE and the Data Collection AF:

– Used by a Direct Data Collection Client instance to obtain its data collection and reporting configuration from the corresponding Data Collection AF instance by means of the Ndcaf_DataReporting service defined in clause 4.4 of the present document. A generic data collection and reporting configuration envelope is defined in clause 4.6.3 of the present document, but details of the configuration are specific to individual reporting domains and are specified elsewhere.

– Subsequently used by the Direct Data Collection Client to send reports to its Data Collection AF instance by means of the Ndcaf_DataReporting service defined in clause 4.4 of the present document. A generic data reporting envelope is defined in clause 4.6.4 of the present document, but details of the reporting format are specific to individual reporting domains and are specified elsewhere.

NOTE 1: This method of reporting corresponds to the direct data collection procedure defined in clause 6.2.8 of TS 23.288 [4].

– R3 supports the following interactions between the Indirect Data Collection Client in the Application Service Provider Server and the Data Collection AF.

– Used by an Indirect Data Collection Client instance to obtain its data collection and reporting configuration from the corresponding Data Collection AF instance by means of the Ndcaf_DataReporting service defined in clause 4.4 of the present document (or else the equivalent service exposed by the NEF if the two functions are deployed in different trust domains). A generic data collection and reporting configuration envelope is defined in clause 4.6.3 of the present document, but details of the configuration are specific to individual reporting domains and are specified elsewhere.

– Subsequently used by the Indirect Data Collection Client in the Application Service Provider server to send data reports to its Data Collection AF instance by means of the Ndcaf_DataReporting service defined in clause 4.4 of the present document (or else the equivalent service exposed by the NEF if the two functions are deployed in different trust domains). A generic data reporting envelope is defined in clause 4.6.4 of the present document, but details of the reporting format are specific to individual reporting domains and are specified elsewhere.

NOTE 2: This method of reporting corresponds to the indirect data collection procedure defined in clause 6.2.8 of TS 23.288 [4].

– R4 supports the following interactions between the Application Server (AS) and the Data Collection AF:

– Used by an AS instance to obtain its data collection and reporting configuration from the corresponding Data Collection AF instance by means of the Ndcaf_DataReporting service defined in clause 4.4 of the present document (or else the equivalent service exposed by the NEF if the two functions are deployed in different trust domains). A generic data collection and reporting configuration envelope is defined in clause 4.6.3 of the present document, but details of the configuration are specific to individual reporting domains and are specified elsewhere.

– Subsequently used by the AS instance to send data reports to its Data Collection AF instance by means of the Ndcaf_DataReporting service defined in clause 4.4 of the present document (or else the equivalent service exposed by the NEF if the two functions are deployed in different trust domains). A generic data reporting envelope is defined in clause 4.6.4 of the present document, but details of the reporting format are specific to individual reporting domains and are specified elsewhere.

NOTE 3: The AS plays the role of a Network Function when it invokes the Ndcaf_DataReporting service at reference point R4.

– R5 supports the following interactions between the NWDAF and the Data Collection AF:

– Used by an NWDAF instance to subscribe to data reporting events exposed by a Data Collection AF instance, according to the Naf_EventExposure_Subscribe procedure defined in clause 5.2.19.2.2 of TS 23.502 [3], as further elaborated in step 3a of clause 6.2.8.2.3 in TS 23.288 [4], and as specified in TS 29.517 [5] (or else the equivalent Nnef_EventExposure_Subscribe service exposed by the NEF if the two functions are deployed in different trust domains).

– Subsequently used by the Data Collection AF to expose data reporting events to the NWDAF, according to the Naf_EventExposure_Notify procedure defined in clause 5.2.19.2.4 of TS 23.502 [3], as further elaborated in step 5a of clause 6.2.8.2.3 in TS 23.288 [4], and as specified in TS 29.517 [5] (or else the equivalent Nnef_EventExposure_Notify service exposed by the NEF if the two functions are deployed in different trust domains).

– R6 supports the following interactions between the Event Consumer AF in the Application Service Provider and the Data Collection AF:

– Used by an Event Consumer AF instance to subscribe to data reporting events exposed by the Data Collection AF, according to the Naf_EventExposure_Subscribe procedure defined in clause 5.2.19.2.2 of TS 23.502 [3] and specified in TS 29.517 [5] (or else the equivalent Nnef_EventExposure_Subscribe service exposed by the NEF if the two functions are deployed in different trust domains).

– Subsequently used by the Data Collection AF to expose data reporting events to the Event Consumer AF according to the Naf_EventExposure_Notify procedure defined in clause 5.2.19.2.4 of TS 23.502 [3] and specified in TS 29.517 [5] (or else the equivalent Nnef_EventExposure_Notify service exposed by the NEF if the two functions are deployed in different trust domains).

– R7 is a client API offered by the Direct Data Collection Client to the UE Application.

NOTE 4: When the Direct Data Collection Client is embedded in the UE Application, reference point R7 is not used.

– R8 supports data collection and reporting interactions between the UE Application and the Application Service Provider server.

NOTE 5: Interactions at reference point R8 are beyond the scope of 3GPP standardisation.

4.4 Service-based architecture for data collection and reporting

Figure 4.4‑1 below shows the reference architecture for data collection and reporting in service-based architecture notation. It depicts the case where the Data Collection AF is deployed inside the trusted domain, while the Application Service Provider and the AS may be deployed independently either inside or outside the trusted domain.

NOTE 1: In its role as an event exposure service provider Application Function, the Data Collection AF provides the (un)subscription operations of the Naf_EventExposure (or Nnef_EventExposure) service for use by Network Function service consumers. As Network Function service consumers, the NWDAF and the Event Consumer AF provide the event notification operation of the Naf_EventExposure (or Nnef_EventExposure) service for use by the Data Collection AF.

NOTE 2: The UE-based Direct Data Collection Client interacts with the Data Collection AF in the user plane, and so the interaction at reference point R2 does not traverse the service bus.

Figure 4.4‑1: Reference architecture for data collection and reporting in service‑based architecture notation when the Data Collection AF is deployed in the trusted domain

The following service-based APIs are used in connection with data collection and reporting:

1. The Ndcaf_DataReportingProvisioning service is provided by the Data Collection AF. It is defined by the present document and is specified in TS 26.532 [7]. This service is used by Provisioning AF instances to provision data collection and reporting in the Data Collection AF.

2. The Nnrf_NFManagement service is provided by the NRF. It is defined in clause 5.2.7.2 of TS 23.502 [3] and specified in clause 6.1 of TS 29.510 [6]. This service is used by the Data Collection AF to register an available NF profile with the NRF for each set of data collection and reporting provisioning information held by the former.

NOTE 1: As described in clause 6.2.8.2.2 of TS 23.288 [4] the NF profile in this case includes the External Application Identifier (used by clients when reporting data to the Data Collection AF), the Internal Application Identifier (used for event exposure to the NWDAF) and the Event ID. These NF profile parameters are in addition to those specified in clause 5.2.7.2 of TS 23.502 [3].

3. The Ndcaf_DataReporting service is provided by the Data Collection AF. It is defined by the present document and is specified in TS 26.532 [7].

a. This service is used by the Direct Data Collection Client, by the Indirect Data Collection Client in the Application Service Provider server and by AS instances to obtain their data collection and reporting configuration from the Data Collection AF.

b. Subsequently, this service is used by the Direct Data Collection Client, by the Indirect Data Collection Client and by AS instances to send data reports to the Data Collection AF.

NOTE 2: Trusted AS instances play the role of a Network Function when invoking the Ndcaf_DataReporting service (or equivalent) and are therefore depicted in figure 4.4‑1 as being directly attached to the service bus.

4. The Naf_EventExposure service is provided by the Data Collection AF. It is defined in clause 5.2.19.2 of TS 23.502 [3] and TS 23.288 [4], and is specified in TS 29.517 [5].

a. Used by the NWDAF to subscribe to data reporting events exposed by the Data Collection AF and subsequently used by the Data Collection AF to notify these events to the NWDAF, as described in clause 6.2.2.2 or 6.2.2.3 (as appropriate) of TS 23.288 [4].

b. Used by an Event Consumer AF in the Application Service Provider server to subscribe to data reporting events exposed by the Data Collection AF and subsequently used by the Data Collection AF to notify these events to the Application Service Provider server, as described in clause 6.2.2.2 or clause 6.2.2.3 (as appropriate) of TS 23.288 [4].

Figure 4.4‑2 depicts the case where the Data Collection AF is instead deployed outside the trusted domain, along with the Application Service Provider and the (external) AS. In this case, the subfunctions of the Application Service Provider and the (external) AS do not interact with the Data Collection AF via the 5G System service bus. The Ndcaf service is therefore not required in such deployments. The interactions at the relevant reference points are outside the scope of 3GPP and are depicted as R1′, R3′, R4′ and R6′ to reflect this.

Figure 4.4‑2: Reference architecture for data collection and reporting in service‑based architecture notation when the Data Collection AF is deployed outside the trusted domain

4.5 Information security model

4.5.1 Transport security

An encrypted data transfer protocol shall be employed at reference point R2 to protect the secrecy and integrity of collected UE data in transit between the Direct Data Collection Client and the Data Collection AF.

4.5.2 Data exposure restriction model

The Provisioning AF restricts the exposure of UE data over reference points R5 and R6 by configuring a set of Data Access Profiles for each Event ID to be exposed. A Data Access Profile specifies a set of data processing operations that need to be performed by the Data Collection AF on the collected UE data in order to synthesize the event data that will be exposed to the NWDAF and/or Event Consumer AF.

When subscribing to event exposure notifications for a particular Event ID, an NWDAF or Event Consumer AF goes through an authorisation procedure (see clause 5.8) with an Authorisation AS that determines the level of access the event subscriber is allowed to have by selecting one of the provisioned Data Access Profiles for the Event ID in question. If successful, the Authorisation AS supplies an access token to the subscriber which is presented to and validated by the Data Collection AF as part of the event subscription procedure.

NOTE: The procedure for selecting an appropriate Data Access Profile is not specified in the present document.

Figure 4.5.2-1 depicts the static data model for the data collection provisioning with Data Access Profiles to restrict data exposure access.

Figure 4.5.2-1: Data exposure restriction domain model

The Data Access Profile defines restrictions along the time, user, and location dimensions:

– Restrictions along the time dimension determine the granularity of access to UE data along the time axis. The finest granularity allows access to events as they take place in time. The coarsest level of access aggregates all event data along the time axis to produce a single aggregated value.

– Restrictions along the user dimension allow the Provisioning AF to restrict access to UE data related events based on groups. The finest granularity allows the event consumer to access events related to single users. Coarse granularity access exposes aggregated collected event data based on user groups. The coarsest granularity access exposes the data being aggregated for all users.

– Restrictions along the location dimension allow the Provisioning AF to restrict access to UE data related events based on the geographical location of the data collection client during the event. The finest granularity allows the event consumer to access events individually, irrespective of the location. Coarse granularity access exposes aggregated collected event data based on a geographical area. The coarsest level of access aggregates all event data along the location axis to produce a single aggregated value for all locations.

The baseline set of aggregation functions is listed in table 4.5.2‑1:

Table 4.5.2‑1: Baseline aggregation functions

Aggregation function	Description
None	No aggregation is applied, and all reported data records are exposed as individual events.
Count	The number of reported data records is exposed to event consumers.
Mean	The mean average of the values in reported data records is exposed to event consumers.
Maximum	The maximal observed value in reported data records is exposed to event consumers.
Minimum	The minimal observed value in reported data records is exposed to event consumers.
Sum	The sum of the values in reported data records is exposed to event consumers.

The authorization URL, if present in the data exposure restrictions, is used to redirect subscription requests without a valid access token to an authorization server, which will perform the authorization for the requested Data Access Profile.

Upon successful authorization, the consumer entity obtains an access token, which contains an identifier of the Data Access Profile that is allowed for the event consumer. Upon successful subscription, the Data Collection AF shall apply the indicated aggregation functions of the corresponding Data Access Profile along the time and user dimensions on the collected data prior to exposing it to the event consumer.

4.5.3 Authentication of data collection clients by the Data Collection AF

To satisfy the requirements in clause 6.2.8.1 of TS 23.288 [4], a data collection client shall supply authentication information to the Data Collection AF:

1. When the data collection client requests its data collection and reporting configuration from the Data Collection AF; and

2. When the data collection client reports UE data to the Data Collection AF.

For reasons of efficiency, the authentication information may be provided once at the start of a long-lived UE data reporting session.

NOTE: In the case of direct reporting, the requirement to supply authentication information may require the UE Application to first obtain this from the Application Service Provider via reference point R8 and then pass it to the Direct Data Collection Client via R7 (or, in the case of Collaboration E depicted in clause A.6, via an internal interface) before it can be presented to the Data Collection AF at reference point R2.

4.6 Domain model

4.6.1 General

Figure 4.6.1‑1 depicts the static data model for the data collection and reporting domain. It is further described below.

Figure 4.6.1‑1: Static domain model

The Provisioning AF provisions zero or more sets of provisioning information in the Data Collection AF at reference point R1. The baseline set of information provisioned is described in clause 4.6.2. Each set of provisioning information pertains to one application, identified by its external application identifier, and one type of exposed event, uniquely identified in the 5G System by its Event ID, as defined in clause 4.15.1 of TS 23.502 [3]. There may be more than one set of provisioning information for a particular external application identifier, but the combination of the external application identifier and Event ID shall be unique for a given Data Collection AF instance.

The data processing instructions and data exposure restrictions are expressed as a set of Data Access Profiles (see clause 4.5.2). The data exposure restrictions limit the types of event consumer that are authorised to subscribe to the Event ID provisioned for the application and the data processing instructions specify aggregation functions that are applied to UE data prior to exposure to those event consumers.

Each set of provisioning information is manifested as a data collection client configuration that the Data Collection AF makes available to Direct Data Collection Client instances at reference point R2, to Indirect Data Collection Client instances at R3 and to AS instances at R4.

Once configured, these data collection clients then send data reports to the Data Collection AF associated with the data collection client configuration. Each data report provides the external application identifier associated with the UE Application and also includes a non-empty list of data reporting records containing the parameters collected by the data collection client. These parameters typically include a sampling timestamp.

NOTE 1: It is the responsibility of the data collection client to discover its external application identifier by means outside the scope of the present document.

An event consumer (the NWDAF and/or Event Consumer AF) subscribes to a type of event exposed by the Data Collection AF using the procedures defined in clause 6.2.8.2.3 of TS 23.288 [4]. The event consumer may additionally specify user-, location- and/or application-based filters in its subscription request in order to further limit the events exposed to a subset of those permitted by the relevant provisioned data exposure restriction(s). Attempts by an event consumer to subscribe to event types that are not provisioned at the Data Collection AF instance are permitted, but will yield no event notifications until such event types have been successfully provisioned.

NOTE 2: It is the responsibility of the event consumer to discover the relevant application identifier of interest by means outside the scope of the present document.

Depending on the data processing instructions provisioned in the Data Collection AF, a data reporting record contributes to zero or more events exposed to subscribers at reference points R5 and/or R6. Conversely, an exposed event arises from one or more data reporting records. In the case of events synthesised by the Data Collection AF from multiple data reporting records, the timestamp of the event shall indicate when it was synthesised. Otherwise, the timestamp of the event shall be identical to the timestamp of the data reporting record from which it arose.

The Data Collection AF exposes a batch of recent events to consumers (the NWDAF and/or Event Consumer AF) as an event exposure notification.

4.6.2 Provisioning information for data collection and reporting

A separate set of provisioning information shall be provided to the Data Collection AF at reference point R1 for each Event ID it is to expose. This provisioning information embodies the Service Level Agreement between the network operator and the Application Service Provider envisaged in clause 6.2.8.1 of TS 23.288 [4]. The provisioning information shall include at least the parameters defined in table 4.6.2‑1 below:

Table 4.6.2‑1: Baseline provisioning information for data collection and reporting

Parameter	Cardinality	Description
External Application Identifier	1..1	The identifier to be used in reports sent to the Data Collection AF by data collection clients. (This needs to be mapped to the Internal Application Identifier when exposing events to the NWDAF.)
Internal Application Identifier	1..1	The identifier to be used by event consumers (including the NWDAF and the Event Consumer AF) when subscribing to events in the Data Collection AF.
Event ID	1..1	The identifier of an AF event that will be exposed to event consumers as a result of the provisioning.
Data collection client type	1..1	The type of data collection client that will submit data reports to the Data Collection AF.
Valid targets	1..1	A parameter to control whether event consumers are permitted to filter events by External UE identifier or External Group Identifier when subscribing, instead of receiving events relating to all UEs.
Parameters to be reported	1..*	The subset of domain-specific parameters associated with the specified Event ID to be reported to the Data Collection AF (subject to user consent).
Data processing instructions	1..*	A set of operations to be performed by the Data Collection AF on the parameters reported according to clause 4.6.4 prior to exposure as an event at a particular access level. The set of supported operations shall include at least those listed in table 4.5.2‑1.
Data exposure restrictions	1..*	A set of restrictions on the exposure of the collected data after any data processing, each corresponding to a different access level.

4.6.3 Configuration information for data collection clients

All clients of the Data Collection AF wishing to report data shall first obtain a data collection and reporting configuration from the Data Collection AF at reference point R2, R3 or R4 (as appropriate). For each Event ID, the data collection and reporting configuration shall include at least the parameters defined in table 4.6.3‑1 below:

Table 4.6.3‑1: Baseline information for data collection and reporting configuration

Parameter

Cardinality

Description

External Application Identifier

1..1

Identifies the UE Application to which this data collection and reporting configuration pertains.

Quoted in reports sent to the Data Collection AF.

Parameters to be collected

1..*

The subset of domain-specific parameters associated with the specified Event ID to be collected by the Data Collection AF (subject to user consent).

4.6.4 Information included in data reports to the Data Collection AF

For each Event ID, the data report shall include at least the parameters as defined in table 4.6.4-1 below:

Table 4.6.4‑1: Baseline information for data reporting

Parameter	Cardinality	Description
External Application Identifier	1..1	Identifies the UE Application to which this data report pertains.
Collected parameters	1..*	The set of parameters collected by the data collection and reporting client.

4.7 Service exposure

4.7.1 Service exposure via Network Exposure Function (NEF)

The following services provided by a Data Collection AF deployed inside the trusted domain shall be exposed northbound by the NEF to an Application Service Provider outside the trusted domain, as depicted in clauses A.3 and A.4:

– The Ndcaf_DataReportingProvisioning service shall be exposed to Provisioning AF instances deployed outside the trusted domain as Nnef_DataReportingProvisioning. See clause 6 of TS 26.532 [7] and clause 5.24 of TS 29.522 [10].

– The Ndcaf_DataReporting service shall be exposed to Indirect Data Collection Clients and Application Servers deployed outside the trusted domain as Nnef_DataReporting. See clause 7 of TS 26.532 [7] and clause 5.23 of TS 29.522 [10].

– The Naf_EventExposure service shall be exposed to Event Consumer AF instances deployed outside the trusted domain as Nnef_EventExposure. See TS 29.517 [5] and TS 29.522 [10].

The following services provided by an externally deployed Data Collection AF shall be exposed southbound by the NEF to Network Functions deployed inside the trusted domain, as depicted in clauses A.5:

– The Naf_EventExposure service shall be exposed to Event Consumer AF instances deployed inside the trusted domain as Nnef_EventExposure. See TS 29.517 [5] and TS 29.591 [11].

4.7.2 Service exposure via Common API Framework (CAPIF) for Northbound APIs

When CAPIF is supported, then:

– the Data Collection AF shall support the CAPIF API provider domain functions as part of a distributed CAPIF deployment, i.e. Ndcaf and Naf via CAPIF‑2/2e; and CAPIF‑3, CAPIF‑4 and CAPIF‑5, as specified in clause 7.3 of TS 23.222 [8];

– the Data Collection AF shall support the CAPIF Core Function and API provider domain functions as part of a centralised CAPIF deployment, i.e. Ndcaf and Naf via CAPIF‑2/2e, as specified in clause 7.2 of TS 23.222 [8].

The CAPIF and associated API provider domain functions are specified in TS 23.222 [8].

4.7.3 Service exposure via Service Enabler Architecture Layer (SEAL) for Verticals

The use of the SEAL framework for exposure of the Ndcaf_DataReportingProvisioning, Ndcaf_DataReporting and Naf_EventExposure services is for future study.