Content for TS 23.436 Word version: 19.2.0
0…
5…
6…
8…
8.3…
8.4…
8.5…
8.6…
8.7…
8.8…
8.9…
8.10…
8.11…
8.12…
8.13…
8.14…
8.15…
8.16…
9…
9.3…
9.4…
A…
8.12 Procedure for supporting data collection to A-DCCF
8.12.1 General
8.12.2 Procedure
8.12.3 Information flows
...
...
8.12 Procedure for supporting data collection to A-DCCF |R19| p. 70
8.12.1 General p. 70
This clause describes two procedures (covering both subscribe-notify and request-response models in clause 8.12.2.1 and 8.12.2.2 respectively) for supporting data collection at A-DCCF.
8.12.2 Procedure p. 71
8.12.2.1 Subscribe-notify model p. 71
Figure 8.12.2.1-1 illustrates the procedure for consumer to request A-DCCF to initiate subscription for data or analytics collection. The procedure may be utilized by the consumer to update the subscription for data or analytics collection.
Pre-conditions:
- Consumer (ADAE server) collects data or analytics via A-DCCF from data producer.
Step 1.
The consumer (ADAE server) sends a data collection subscription request to A-DCCF for collecting data/analytics. The request message includes identifier of the consumer (ADAE server ID), Data Collection Event ID, and Data Collection Requirements. The request message may include the identifier of Data Producer, Analytics ID, target data producer profile criteria, process requirements, Area of Interest, Time validity, storage requirements, and notification endpoints. The consumer decides to go via A-DCCF based on internal configuration.
Step 2.
If the data producer is not identified by the consumer, the A-DCCF determines the data procedure that can provide data/analytics. If the consumer requested storage of data/analytics in an A-ADRF but the A-ADRF ID is not provided by the consumer, or the collected data/analytics is to be stored in an A-ADRF according to configuration on the A-DCCF, the A-DCCF selects an A-ADRF to store the collected data/analytics.
Step 3.
The A-DCCF determines whether the data/analytics requested in step 1 are already being collected. If the requested data/analytics are already being collected by a consumer, the A-DCCF adds the new consumer to the list of consumers that are subscribed for these data/analytics.
Step 4.
If the data/analytics subscribed in step 1 is not being collected by the A-DCCF, the A-DCCF subscribes to the data producer for data/analytics.
If the data/analytics subscribed in step 1 partially matches the data/analytics that is already being collected by the A-DCCF, a modification of this subscription to the data producer would satisfy both the existing data/analytics subscriptions as well as the newly requested data/analytics, the A-DCCF requests an update of the previous subscription to the data producer. The A-DCCF adds the consumer to the list of consumers that are subscribed for these data/analytics.
Step 5.
Upon received the data/analytics subscription request from the A-DCCF, the data producer determines whether the required data/analytics can be provided and sends data/analytics subscription response to the A-DCCF.
Step 6.
The A-DCCF sends data/analytics subscription response to the consumer.
Step 7.
When the required data/analytics are available, the data producer notifies the data/analytics to the A-DCCF.
Step 8.
The A-DCCF notifies the data/analytics to all notification endpoints indicated in step 1. Data/analytics sent to notification endpoints may be processed by the DCCF upon to the request in step 1. The DCCF may store the data/analytics in the A-ADRF if requested by the consumer or if required by A-DCCF configuration.
8.12.2.2 Request-response model p. 72
Figure 8.12.2.2-1 illustrates the procedure for the consumer to request A-DCCF for data or analytics collection.
Step 1.
The consumer (ADAE server) sends a Get data/analytics request to A-DCCF for data/analytics collection. The request message includes identifier of the consumer (ADAE server ID), and Data/Analytics Requirements. The request message may include the identifier of Data Producer, Analytics ID, target data producer profile criteria, process requirements, storage requirements, and notification endpoints. The consumer decides to go via A-DCCF based on internal configuration.
Step 2.
The A-DCCF determines whether the data/analytics requested in step 1 are already being collected. If the requested data/analytics are already being collected by a consumer, the A-DCCF adds the new consumer to the list of consumers that are subscribed for these data/analytics.
Step 3.
If the data/analytics requested in step 1 is not being collected by the A-DCCF, and the data producer is not identified by the consumer, the A-DCCF determines the data procedure that can provide data/analytics. If the consumer requested storage of data/analytics in an A-ADRF but the A-ADRF ID is not provided by the consumer, or the collected data/analytics is to be stored in an A-ADRF according to configuration on the A-DCCF, the A-DCCF selects an A-ADRF to store the collected data/analytics.
Step 4.
The A-DCCF sends Get data/analytics request to the data producer for data/analytics.
Step 5.
Upon received the data/analytics request from the A-DCCF, the data producer determines whether the required data/analytics can be provided and sends data/analytics response to the A-DCCF. The required data/analytics may be contained in the response if they are available at the data producer.
Step 6.
The A-DCCF sends data/analytics response to the consumer. The required data/analytics may be contained in the response if get from the data producer.
8.12.3 Information flows p. 73
8.12.3.1 General p. 73
The following information flows are specified for data collection based on clause 8.12.2.
8.12.3.2 Data collection subscription request p. 73
Table 8.12.3.2-1 describes information elements for the data collection subscription request from the consumer (ADAE server) to the A-DCCF.
| Information element | Status | Description |
|---|---|---|
| Consumer ID | M | The identifier of the consumer (ADAE server ID). |
| Data Collection Event ID | M | The identifier of the data collection event. |
| Data Collection requirements | M | The requirements for data collection, including the format of data, frequency of reporting, level of abstraction of data, level of accuracy of data. |
| Analytics ID | O | The identifier of the analytics event, for which the data collection is needed. |
| List of Data Producer IDs | O | The list of Data Producer IDs. |
| Target data producer profile criteria | O | Characteristics of the data producers to be used. |
| Area of Interest | O | The geographical or service area for which the requirement request applies. |
| Time validity | O | The time validity of the request. |
| Process requirements | O | Requirements on processing the collected data/analytics. |
| Storage requirements | O | Requirements on storage of the collected data/analytics. |
| > A-ADRF ID | O | The identifier of A-ADRF for store the collected data/analytics. |
| Notification endpoints ID or address | O | The identifier or address of the notification endpoints. |
8.12.3.3 Data collection subscription response p. 73
Table 8.12.3.3-1 describes information elements for the data collection subscription response from the A-DCCF to the consumer (ADAE server).
| Information element | Status | Description |
|---|---|---|
| Result | M | The result of the data collection subscription request (positive or negative acknowledgement). |
8.12.3.4 Data collection notification p. 73
Table 8.12.3.4-1 describes information elements for the data collection notification from the A-DCCF to the consumer (ADAE server).
| Information element | Status | Description |
|---|---|---|
| Data Collection Event ID | M | The identifier of the data collection event. |
| Analytics ID | O | The identifier of the analytics event. |
| Analytics Type | O | The type of reported analytics, which can be statistics, prediction, etc. |
| Data Type | O | The type of reported data samples, which can be UE data, network data, application data, edge data, or different granularities/abstraction of data (e.g. real time, non-real time). |
| Data Output | M | The reported data/analytics, which can be inform of measurements or offline/historical data/analytics based on subscription. |
| Process information | O | Information of the processing of the collected data/analytics. |
| Storage information | O | Information of the storage of the collected data/analytics. |
| > A-ADRF ID | O | The identifier of A-ADRF for store the collected data/analytics. |
8.12.3.5 Get Data/Analytics request p. 74
Table 8.12.3.5-1 describes information elements for the Get data/analytics request from the consumer (ADAE server) to the A-DCCF.
| Information element | Status | Description |
|---|---|---|
| Consumer ID | M | The identifier of the consumer (ADAE server ID). |
| Data/Analytics requirements | M | The requirements for data/analytics collection, including the format of data, level of abstraction of data, level of accuracy of data. |
| Analytics ID | O | The identifier of the analytics event for the required analytics. |
| List of Data Producer IDs | O | The list of Data Producer IDs. |
| Target data producer profile criteria | O | Characteristics of the data producers to be used. |
| Area of Interest | O | The geographical or service area for which the requirement request applies. |
| Time validity | O | The time validity of the request. |
| Process requirements | O | Requirements on processing the collected data/analytics. |
| Storage requirements | O | Requirements on storage of the collected data/analytics. |
| > A-ADRF ID | O | The identifier of A-ADRF for store the collected data/analytics. |
| Notification endpoints ID or address | O | The identifier or address of the notification endpoints. |
8.12.3.6 Data collection response p. 74
Table 8.12.3.6-1 describes information elements for the data collection response from the A-DCCF to the consumer (ADAE server).
| Information element | Status | Description |
|---|---|---|
| Result | M | The result of the analytics data request (positive or negative acknowledgement). |
| Analytics ID | O | The identifier of the analytics event. |
| Analytics Type | O | The type of reported analytics, which can be statistics, prediction, etc. |
| Data Type | O | The type of reported data samples, which can be UE data, network data, application data, edge data, or different granularities/abstraction of data (e.g. real time, non-real time). |
| Data Output | M | The reported data/analytics, which can be inform of measurements or offline/historical data/analytics based on subscription. |
| Process information | O | Information of the processing of the collected data/analytics. |
| Storage information | O | Information of the storage of the collected data/analytics. |
| > A-ADRF ID | O | The identifier of A-ADRF for store the collected data/analytics. |
8.12.3.7 Data producer profile p. 75
The data producer profile IE includes information about the data generation/production capability of the data producer to support data collection for data analytics service and the availability/accessibility of the generated/produced data, as defined in Table 8.12.3.7-1.
| Information element | Status | Description |
|---|---|---|
| Data Producer ID | M | ID of the data producer. |
| Data producer type (NOTE) | M | Specifies the type of the data producer, e.g., ADAEC, A-DCCF, A-ADRF, VAL server, SEAL server, SEAL client, EES, EAS. |
| Data type (NOTE) | M | Type of information that can be provided by the data producer, e.g., performance indicators, reproducer usage data, server load data, application performance, edge load. |
| Data producer role (NOTE) | O | Role of the data producer, e.g., generating entity, original producer, repository. |
| Original producer ID (NOTE) | O | If the data producer role is not "original producer" or "generating entity", specifies the Producer ID of the original data producer for the data provided by this data producer. If the data producer type is A-DCCF, this is a list of Data Producer IDs. |
| Data freshness (NOTE) | O | If the data producer role is not "original producer" or "generating entity", length of time elapsed after the data is generated until is available at the data producer. Alternatively, the data collection rate supported by the producer is provided. |
| Data producer capability (NOTE) | O | Indicates data producer capabilities for this data type, e.g. how long the data can be stored, support for anonymization, data generation rate and schedule. |
|
NOTE:
When the Data producer profile IE is used for Target data producer profile criteria (e.g. Table 8.12.3.2-1 and Table 8.12.3.5-1), this IE may be a list of values.
|
||
