5 API Definitions

29.5743GPP5G SystemData Collection Coordination ServicesRelease 18Stage 3TS

5.1 Ndccf_DataManagement Service API

5.1.1 Introduction

The Ndccf_DataManagement shall use the Ndccf_DataManagement API.

The API URI of the Ndccf_DataManagement API shall be:

{apiRoot}/<apiName>/<apiVersion>

The request URIs used in HTTP requests from the NF service consumer towards the NF service producer shall have the Resource URI structure defined in clause 4.4.1 of 3GPP TS 29.501 [5], i.e.:

{apiRoot}/<apiName>/<apiVersion>/<apiSpecificResourceUriPart>

with the following components:

– The {apiRoot} shall be set as described in 3GPP TS 29.501 [5].

– The <apiName> shall be "ndccf-datamanagement".

– The <apiVersion> shall be "v1".

– The <apiSpecificResourceUriPart> shall be set as described in clause 5.1.3.

5.1.2 Usage of HTTP

5.1.2.1 General

HTTP/2, IETF RFC 7540 [11], shall be used as specified in clause 5 of 3GPP TS 29.500 [4].

HTTP/2 shall be transported as specified in clause 5.3 of 3GPP TS 29.500 [4].

The OpenAPI [6] specification of HTTP messages and content bodies for the Ndccf_DataManagement API is contained in Annex A.

5.1.2.2 HTTP standard headers

5.1.2.2.1 General

See clause 5.2.2 of 3GPP TS 29.500 [4] for the usage of HTTP standard headers.

5.1.2.2.2 Content type

JSON, IETF RFC 8259 [12], shall be used as content type of the HTTP bodies specified in the present specification as specified in clause 5.4 of 3GPP TS 29.500 [4]. The use of the JSON format shall be signalled by the content type "application/json".

"Problem Details" JSON object shall be used to indicate additional details of the error in a HTTP response body and shall be signalled by the content type "application/problem+json", as defined in IETF RFC 7807 [13].

5.1.2.3 HTTP custom headers

The mandatory HTTP custom header fields specified in clause 5.2.3.2 of 3GPP TS 29.500 [4] shall be supported, and the optional HTTP custom header fields specified in clause 5.2.3.3 of 3GPP TS 29.500 [4] may be supported.

5.1.3 Resources

5.1.3.1 Overview

This clause describes the structure for the Resource URIs and the resources and methods used for the service.

Figure 5.1.3.1-1 depicts the resource URIs structure for the Ndccf_DataManagement API.

Figure 5.1.3.1-1: Resource URI structure of the Ndccf_DataManagement API

Table 5.1.3.1-1 provides an overview of the resources and applicable HTTP methods.

Table 5.1.3.1-1: Resources and methods overview

Resource name

Resource URI

HTTP method or custom operation

Description

DCCF Analytics Subscriptions

/analytics-subscriptions

POST

Creates a new Individual DCCF Analytics Subscription resource.

Individual DCCF Analytics Subscription

/analytics-subscriptions/{subscriptionId}

PUT

Modifies an existing Individual DCCF Analytics Subscription resource.

DELETE

Deletes an Individual DCCF Analytics Subscription identified by {subscriptionId}.

DCCF Data Subscriptions

/data-subscriptions

POST

Creates a new Individual DCCF Data Subscription resource.

Individual DCCF Data Subscription

/data-subscriptions/{subscriptionId}

PUT

Modifies an existing DCCF Data Subscription resource.

DELETE

Deletes an Individual DCCF Data Subscription identified by {subscriptionId}.

5.1.3.2 Resource: DCCF Analytics Subscriptions

5.1.3.2.1 Description

The DCCF Analytics Subscriptions resource represents all Analytics subscriptions to the Ndccf_DataManagement Service at a given DCCF. The resource allows an NF service consumer to create a new Individual DCCF Analytics Subscription resource.

5.1.3.2.2 Resource Definition

Resource URI: {apiRoot}/ndccf-datamanagement/<apiVersion>/analytics-subscriptions

This resource shall support the resource URI variables defined in table 5.1.3.2.2-1.

Table 5.1.3.2.2-1: Resource URI variables for this resource

Name

Data type

Definition

apiRoot

string

See clause 5.1.1

5.1.3.2.3 Resource Standard Methods
5.1.3.2.3.1 POST

This method shall support the URI query parameters specified in table 5.1.3.2.3.1-1.

Table 5.1.3.2.3.1-1: URI query parameters supported by the POST method on this resource

Name

Data type

P

Cardinality

Description

Applicability

n/a

This method shall support the request data structures specified in table 5.1.3.2.3.1-2 and the response data structures and response codes specified in table 5.1.3.2.3.1-3.

Table 5.1.3.2.3.1-2: Data structures supported by the POST Request Body on this resource

Data type

P

Cardinality

Description

NdccfAnalyticsSubscription

M

1

New Individual DCCF Analytics Subscription resource to be created.

Table 5.1.3.2.3.1-3: Data structures supported by the POST Response Body on this resource

Data type

P

Cardinality

Response

codes

Description

NdccfAnalyticsSubscription

M

1

201 Created

The creation of an Individual DCCF Analytics Subscription resource is confirmed and a representation of that resource is returned.

ProblemDetails

O

0..1

400 Bad Request

(NOTE 2)

ProblemDetails

O

0..1

403 Forbidden

(NOTE 2)

NOTE 1: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply.

NOTE 2: Failure cases are described in clause 5.1.7.

Table 5.1.3.2.3.1-4: Headers supported by the 201 response code on this resource

Name

Data type

P

Cardinality

Description

Location

string

M

1

Contains the URI of the newly created resource, according to the structure: {apiRoot}/ndccf-datamanagement/<apiVersion>/analytics-subscriptions/{subscriptionId}

5.1.3.2.4 Resource Custom Operations

None in this release of the specification.

5.1.3.3 Resource: Individual DCCF Analytics Subscription

5.1.3.3.1 Description

The Individual DCCF Analytics Subscription resource represents a single Analytics Subscription to the Ndccf_DataManagement Service at a given DCCF.

5.1.3.3.2 Resource Definition

Resource URI: {apiRoot}/ndccf-datamanagement/<apiVersion>/analytics-subscriptions/{subscriptionId}

This resource shall support the resource URI variables defined in table 5.1.3.3.2-1.

Table 5.1.3.3.2-1: Resource URI variables for this resource

Name

Data type

Definition

apiRoot

string

See clause 5.1.1

subscriptionId

string

Identifies an analytics subscription to the Ndccf_DataManagement Service

5.1.3.3.3 Resource Standard Methods
5.1.3.3.3.1 PUT

This method shall support the URI query parameters specified in table 5.1.3.3.3.1-1.

Table 5.1.3.3.3.1-1: URI query parameters supported by the PUT method on this resource

Name

Data type

P

Cardinality

Description

Applicability

n/a

This method shall support the request data structures specified in table 5.1.3.3.3.1-2 and the response data structures and response codes specified in table 5.1.3.3.3.1-3.

Table 5.1.3.3.3.1-2: Data structures supported by the PUT Request Body on this resource

Data type

P

Cardinality

Description

NdccfAnalyticsSubscription

M

1

Parameters to replace a subscription to DCCF Analytics Subscription resource.

Table 5.1.3.3.3.1-3: Data structures supported by the PUT Response Body on this resource

Data type

P

Cardinality

Response

codes

Description

NdccfAnalyticsSubscription

M

1

200 OK

The Individual DCCF Analytics Subscription resource was modified successfully and a representation of that resource is returned.

n/a

204 No Content

The Individual DCCF Analytics Subscription resource was modified successfully.

RedirectResponse

O

0..1

307 Temporary Redirect

Temporary redirection, during Individual DCCF Analytics Subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative DCCF (service) instance.

RedirectResponse

O

0..1

308 Permanent Redirect

Permanent redirection, during Individual DCCF Analytics Subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative DCCF (service) instance.

ProblemDetails

O

0..1

400 Bad Request

(NOTE 2)

ProblemDetails

O

0..1

403 Forbidden

(NOTE 2)

NOTE 1: The mandatory HTTP error status code for the PUT method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply.

NOTE 2: Failure cases are described in clause 5.1.7.

Table 5.1.3.3.3.1-4: Headers supported by the 307 Response Code on this resource

Name

Data type

P

Cardinality

Description

Location

string

M

1

An alternative URI of the resource located in an alternative DCCF (service) instance.

3gpp-Sbi-Target-Nf-Id

string

O

0..1

Identifier of the target NF (service) instance towards which the request is redirected.

Table 5.1.3.3.3.1-5: Headers supported by the 308 Response Code on this resource

Name

Data type

P

Cardinality

Description

Location

string

M

1

An alternative URI of the resource located in an alternative DCCF (service) instance.

3gpp-Sbi-Target-Nf-Id

string

O

0..1

Identifier of the target NF (service) instance towards which the request is redirected.

5.1.3.3.3.2 DELETE

This method shall support the URI query parameters specified in table 5.1.3.3.3.2-1.

Table 5.1.3.3.3.2-1: URI query parameters supported by the DELETE method on this resource

Name

Data type

P

Cardinality

Description

Applicability

n/a

This method shall support the request data structures specified in table 5.1.3.3.3.2-2 and the response data structures and response codes specified in table 5.1.3.3.3.2-3.

Table 5.1.3.3.3.2-2: Data structures supported by the DELETE Request Body on this resource

Data type

P

Cardinality

Description

n/a

Table 5.1.3.3.3.2-3: Data structures supported by the DELETE Response Body on this resource

Data type

P

Cardinality

Response

codes

Description

n/a

204 No Content

The Individual DCCF Analytics Subscription resource was deleted successfully.

RedirectResponse

O

0..1

307 Temporary Redirect

Temporary redirection, during Individual DCCF Analytics Subscription deletion. The response shall include a Location header field containing an alternative URI of the resource located in an alternative DCCF (service) instance.

RedirectResponse

O

0..1

308 Permanent Redirect

Permanent redirection, during Individual DCCF Analytics Subscription deletion. The response shall include a Location header field containing an alternative URI of the resource located in an alternative DCCF (service) instance.

NOTE: The mandatory HTTP error status code for the DELETE method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply.

Table 5.1.3.3.3.2-4: Headers supported by the 307 Response Code on this resource

Name

Data type

P

Cardinality

Description

Location

string

M

1

An alternative URI of the resource located in an alternative DCCF (service) instance.

3gpp-Sbi-Target-Nf-Id

string

O

0..1

Identifier of the target NF (service) instance towards which the request is redirected.

Table 5.1.3.3.3.2-5: Headers supported by the 308 Response Code on this resource

Name

Data type

P

Cardinality

Description

Location

string

M

1

An alternative URI of the resource located in an alternative DCCF (service) instance.

3gpp-Sbi-Target-Nf-Id

string

O

0..1

Identifier of the target NF (service) instance towards which the request is redirected.

5.1.3.3.4 Resource Custom Operations

None in this release of the specification.

5.1.3.4 Resource: DCCF Data Subscriptions

5.1.3.4.1 Description

The DCCF Data Subscriptions resource represents all data subscriptions to the Ndccf_DataManagement Service at a given DCCF. The resource allows an NF service consumer to create a new Individual DCCF Data Subscription resource.

5.1.3.4.2 Resource Definition

Resource URI: {apiRoot}/ndccf-datamanagement/<apiVersion>/data-subscriptions

This resource shall support the resource URI variables defined in table 5.1.3.4.2-1.

Table 5.1.3.3.2-1: Resource URI variables for this resource

Name

Data type

Definition

apiRoot

string

See clause 5.1.1

5.1.3.4.3 Resource Standard Methods
5.1.3.4.3.1 POST

This method shall support the URI query parameters specified in table 5.1.3.4.3.1-1.

Table 5.1.3.4.3.1-1: URI query parameters supported by the POST method on this resource

Name

Data type

P

Cardinality

Description

Applicability

n/a

This method shall support the request data structures specified in table 5.1.3.4.3.1-2 and the response data structures and response codes specified in table 5.1.3.4.3.1-3.

Table 5.1.3.4.3.1-2: Data structures supported by the POST Request Body on this resource

Data type

P

Cardinality

Description

NdccfDataSubscription

M

1

Individual DCCF Data Subscription resource to be created.

Table 5.1.3.4.3.1-3: Data structures supported by the POST Response Body on this resource

Data type

P

Cardinality

Response

codes

Description

NdccfDataSubscription

M

1

201 Created

The creation of an Individual DCCF Data Subscription resource is confirmed and a representation of that resource is returned.

ProblemDetails

O

0..1

400 Bad Request

(NOTE 2)

ProblemDetails

O

0..1

403 Forbidden

(NOTE 2)

NOTE 1: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply.

NOTE 2: Failure cases are described in clause 5.1.7.

Table 5.1.3.4.3.1-4: Headers supported by the 201 response code on this resource

Name

Data type

P

Cardinality

Description

Location

string

M

1

Contains the URI of the newly created resource, according to the structure: {apiRoot}/ndccf-datamanagement/<apiVersion>/data-subscriptions/{subscriptionId}

5.1.3.4.4 Resource Custom Operations

None in this release of the specification.

5.1.3.5 Resource: Individual DCCF Data Subscription

5.1.3.5.1 Description

The Individual DCCF Data Subscription resource represents a single data subscription to the Ndccf_DataManagement Service at a given DCCF.

5.1.3.5.2 Resource Definition

Resource URI: {apiRoot}/ndccf-datamanagement/<apiVersion>/data-subscriptions/{subscriptionId}

This resource shall support the resource URI variables defined in table 5.1.3.5.2-1.

Table 5.1.3.5.2-1: Resource URI variables for this resource

Name

Data type

Definition

apiRoot

string

See clause 5.1.1

subscriptionId

string

Identifies a data subscription to the Ndccf_DataManagement Service

5.1.3.5.3 Resource Standard Methods
5.1.3.5.3.1 PUT

This method shall support the URI query parameters specified in table 5.1.3.5.3.1-1.

Table 5.1.3.5.3.1-1: URI query parameters supported by the PUT method on this resource

Name

Data type

P

Cardinality

Description

Applicability

n/a

This method shall support the request data structures specified in table 5.1.3.5.3.1-2 and the response data structures and response codes specified in table 5.1.3.5.3.1-3.

Table 5.1.3.5.3.1-2: Data structures supported by the PUT Request Body on this resource

Data type

P

Cardinality

Description

NdccfDataSubscription

M

1

Parameters to replace a subscription to DCCF Data Subscription resource.

Table 5.1.3.5.3.1-3: Data structures supported by the PUT Response Body on this resource

Data type

P

Cardinality

Response

codes

Description

NdccfDataSubscription

M

1

200 OK

The Individual DCCF Data Subscription resource was modified successfully and a representation of that resource is returned.

n/a

204 No Content

The Individual DCCF Data Subscription resource was modified successfully.

RedirectResponse

O

0..1

307 Temporary Redirect

Temporary redirection, during Individual DCCF Data Subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative DCCF (service) instance.

RedirectResponse

O

0..1

308 Permanent Redirect

Permanent redirection, during Individual DCCF Data Subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative DCCF (service) instance.

ProblemDetails

O

0..1

400 Bad Request

(NOTE 2)

ProblemDetails

O

0..1

403 Forbidden

(NOTE 2)

NOTE 1: The mandatory HTTP error status code for the PUT method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply.

NOTE 2: Failure cases are described in clause 5.1.7.

Table 5.1.3.5.3.1-4: Headers supported by the 307 Response Code on this resource

Name

Data type

P

Cardinality

Description

Location

string

M

1

An alternative URI of the resource located in an alternative DCCF (service) instance.

3gpp-Sbi-Target-Nf-Id

string

O

0..1

Identifier of the target NF (service) instance towards which the request is redirected.

Table 5.1.3.5.3.1-5: Headers supported by the 308 Response Code on this resource

Name

Data type

P

Cardinality

Description

Location

string

M

1

An alternative URI of the resource located in an alternative DCCF (service) instance.

3gpp-Sbi-Target-Nf-Id

string

O

0..1

Identifier of the target NF (service) instance towards which the request is redirected.

5.1.3.5.3.2 DELETE

This method shall support the URI query parameters specified in table 5.1.3.5.3.2-1.

Table 5.1.3.5.3.2-1: URI query parameters supported by the DELETE method on this resource

Name

Data type

P

Cardinality

Description

Applicability

n/a

This method shall support the request data structures specified in table 5.1.3.5.3.2-2 and the response data structures and response codes specified in table 5.1.3.5.3.2-3.

Table 5.1.3.5.3.2-2: Data structures supported by the DELETE Request Body on this resource

Data type

P

Cardinality

Description

n/a

Table 5.1.3.5.3.2-3: Data structures supported by the PUT Response Body on this resource

Data type

P

Cardinality

Response

codes

Description

n/a

204 No Content

The Individual DCCF Data Subscription resource was deleted successfully.

RedirectResponse

O

0..1

307 Temporary Redirect

Temporary redirection, during Individual DCCF Data Subscription deletion. The response shall include a Location header field containing an alternative URI of the resource located in an alternative DCCF (service) instance.

RedirectResponse

O

0..1

308 Permanent Redirect

Permanent redirection, during Individual DCCF Data Subscription deletion. The response shall include a Location header field containing an alternative URI of the resource located in an alternative DCCF (service) instance.

NOTE: The mandatory HTTP error status code for the DELETE method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply.

Table 5.1.3.5.3.2-4: Headers supported by the 307 Response Code on this resource

Name

Data type

P

Cardinality

Description

Location

string

M

1

An alternative URI of the resource located in an alternative DCCF (service) instance.

3gpp-Sbi-Target-Nf-Id

string

O

0..1

Identifier of the target NF (service) instance towards which the request is redirected.

Table 5.1.3.5.3.2-5: Headers supported by the 308 Response Code on this resource

Name

Data type

P

Cardinality

Description

Location

string

M

1

An alternative URI of the resource located in an alternative DCCF (service) instance.

3gpp-Sbi-Target-Nf-Id

string

O

0..1

Identifier of the target NF (service) instance towards which the request is redirected.

5.1.3.5.4 Resource Custom Operations

None in this release of the specification.

5.1.4 Custom Operations without associated resources

None in this release of the specification.

5.1.5 Notifications

5.1.5.1 General

Notifications shall comply to clause 6.2 of 3GPP TS 29.500 [4] and clause 4.6.2.3 of 3GPP TS 29.501 [5].

Table 5.1.5.1-1: Notifications overview

Notification

Callback URI

HTTP method or custom operation

Description

(service operation)

Analytics Event Notification

{anaNotifUri}

POST

Report one or several observed analytics events.

Data Event Notification

{dataNotifUri}

POST

Report one or several observed data collection events.

Fetch Notification

{fetchUri}

POST

Fetch one or several notified data or analytics.

5.1.5.2 Analytics Notification

5.1.5.2.1 Description

The Analytics Notification is used by the NF service producer to report one or several observed analytics events to an NF service consumer that has subscribed to such notifications.

5.1.5.2.2 Target URI

The Callback URI "{anaNotifUri}" shall be used with the callback URI variables defined in table 5.1.5.2.2-1.

Table 5.1.5.2.2-1: Callback URI variables

Name

Definition

anaNotifUri

String formatted as URI with the Callback Uri.

The Callback Uri is assigned within the Individual DCCF Analytics Subscription resource and described within the NdccfAnalyticsSubscription type (see table 5.1.6.2.2-1).

5.1.5.2.3 Standard Methods

5.1.5.2.3.1 POST

This method shall support the request data structures specified in table 5.1.5.2.3.1-1 and the response data structures and response codes specified in table 5.1.5.2.3.2-1.

Table 5.1.5.2.3.1-1: Data structures supported by the POST Request Body

Data type

P

Cardinality

Description

NdccfAnalyticsSubscriptionNotification

M

1

Provides information about observed analytics events

Table 5.1.5.2.3.1-2: Data structures supported by the POST Response Body

Data type

P

Cardinality

Response codes

Description

n/a

204 No Content

The receipt of the Notification is acknowledged.

RedirectResponse

O

0..1

307 Temporary Redirect

Temporary redirection, during the analytics event notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative NF consumer (service) instance where the notification should be sent.

RedirectResponse

O

0..1

308 Permanent Redirect

Permanent redirection, during the analytics event notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative NF consumer (service) instance where the notification should be sent.

NOTE: The mandatory HTTP error status codes for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply.

Table 5.1.5.2.3.1-3: Headers supported by the 307 Response Code on this resource

Name

Data type

P

Cardinality

Description

Location

string

M

1

An alternative URI representing the end point of an alternative NF consumer (service) instance towards which the notification should be redirected.

3gpp-Sbi-Target-Nf-Id

string

O

0..1

Identifier of the target NF (service) instance towards which the notification request is redirected.

Table 5.1.5.2.3.1-4: Headers supported by the 308 Response Code on this resource

Name

Data type

P

Cardinality

Description

Location

string

M

1

An alternative URI representing the end point of an alternative NF consumer (service) instance towards which the notification should be redirected.

3gpp-Sbi-Target-Nf-Id

string

O

0..1

Identifier of the target NF (service) instance towards which the notification request is redirected.

5.1.5.3 Data Notification

5.1.5.3.1 Description

The Data Notification is used by the NF service producer to report one or several observed data collection events to an NF service consumer that has subscribed to such notifications.

5.1.5.3.2 Target URI

The Callback URI "{dataNotifUri}" shall be used with the callback URI variables defined in table 5.1.5.3.2-1.

Table 5.1.5.3.2-1: Callback URI variables

Name

Definition

dataNotifUri

String formatted as URI with the Callback Uri.

The Callback Uri is assigned within the Individual DCCF Data Subscription resource and described within the NdccfDataSubscription type (see table 5.1.6.3.2-1).

5.1.5.3.3 Standard Methods
5.1.5.3.3.1 POST

This method shall support the request data structures specified in table 5.1.5.3.3.1-1 and the response data structures and response codes specified in table 5.1.5.3.3.1-2.

Table 5.1.5.3.3.1-1: Data structures supported by the POST Request Body

Data type

P

Cardinality

Description

NdccfDataSubscriptionNotification

M

1

Provides Information about observed data collection events.

Table 5.1.5.3.3.1-2: Data structures supported by the POST Response Body

Data type

P

Cardinality

Response codes

Description

n/a

204 No Content

The receipt of the notification is acknowledged.

RedirectResponse

O

0..1

307 Temporary Redirect

Temporary redirection, during the data event notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative NF consumer (service) instance where the notification should be sent.

RedirectResponse

O

0..1

308 Permanent Redirect

Permanent redirection, during the data event notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative NF consumer (service) instance where the notification should be sent.

NOTE: The mandatory HTTP error status codes for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply.

Table 5.1.5.3.3.1-3: Headers supported by the 307 Response Code on this resource

Name

Data type

P

Cardinality

Description

Location

string

M

1

An alternative URI representing the end point of an alternative NF consumer (service) instance towards which the notification should be redirected.

3gpp-Sbi-Target-Nf-Id

string

O

0..1

Identifier of the target NF (service) instance towards which the notification request is redirected.

Table 5.1.5.3.3.1-4: Headers supported by the 308 Response Code on this resource

Name

Data type

P

Cardinality

Description

Location

string

M

1

An alternative URI representing the end point of an alternative NF consumer (service) instance towards which the notification should be redirected.

3gpp-Sbi-Target-Nf-Id

string

O

0..1

Identifier of the target NF (service) instance towards which the notification request is redirected.

5.1.5.4 Fetch Notification

5.1.5.4.1 Description

The Fetch Notification is used by the NF service consumer to retrieve data or analytics from the DCCF.

5.1.5.4.2 Target URI

The Callback URI "{fetchUri}" shall be used with the callback URI variables defined in table 5.1.5.4.2-1.

Table 5.1.5.4.2-1: Callback URI variables

Name

Data type

Definition

fetchUri

Uri

Fetch Uri as assigned during the procedure of notification about the subscribed data or analytics within the FetchInstruction data type.

5.1.5.4.3 Standard Methods
5.1.5.4.3.1 POST

This method shall support the URI query parameters specified in table 5.1.5.4.3.1-1.

Table 5.1.5.4.3.1-1: URI query parameters supported by the POST method on this resource

Name

Data type

P

Cardinality

Description

Applicability

n/a

This method shall support the request data structures specified in table 5.1.5.4.3.1-2 and the response data structures and response codes specified in table 5.1.5.4.3.1-3.

Table 5.1.5.4.3.1-2: Data structures supported by the POST Request Body on this resource

Data type

P

Cardinality

Description

array(string)

M

1..N

Indicate the fetch correlation identifier(s).

Table 5.1.5.4.3.1-3: Data structures supported by the POST Response Body on this resource

Data type

P

Cardinality

Response

codes

Description

NdccfAnalyticsSubscriptionNotification

C

0..1

200 OK

The stored analytics related to the fetch correlation identifier(s).

(NOTE 2)

NdccfDataSubscriptionNotification

C

0..1

200 OK

The stored data related to the fetch correlation identifier(s).

(NOTE 2)

RedirectResponse

O

0..1

307 Temporary Redirect

Temporary redirection, during subscription retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative DCCF.

RedirectResponse

O

0..1

308 Permanent Redirect

Permanent redirection, during subscription retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative DCCF.

NOTE 1: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply.

NOTE 2: In case of a 200 OK response, one of NdccfAnalyticsSubscriptionNotification data structure and NdccfDataSubscriptionNotification data structure shall be included, depending on if the Fetch Notification included fetch correlation identifiers from an analytics notification or from a data notification.

Table 5.1.5.4.3.1-4: Headers supported by the by the 307 Response Code on this resource

Name

Data type

P

Cardinality

Description

Location

string

M

1

An alternative URI of the resource located in an alternative DCCF.

3gpp-Sbi-Target-Nf-Id

string

O

0..1

Identifier of the target NF (service) instance towards which the request is redirected.

Table 5.1.5.4.3.1-5: Headers supported by the 308 response code on this resource

Name

Data type

P

Cardinality

Description

Location

string

M

1

An alternative URI of the resource located in an alternative DCCF.

3gpp-Sbi-Target-Nf-Id

string

O

0..1

Identifier of the target NF (service) instance towards which the request is redirected.

5.1.6 Data Model

5.1.6.1 General

This clause specifies the application data model supported by the Ndccf_DataManagement API.

Table 5.1.6.1-1 specifies the data types defined for the Ndccf_DataManagement service based interface protocol.

Table 5.1.6.1-1: Ndccf_DataManagement specific Data Types

Data type

Clause defined

Description

Applicability

AggregationLevel

5.1.6.3.4

Contains an aggregation level for processing instructions (e.g. per UE, per Area of Interest).

DataCollectionPurpose

5.1.6.3.5

Represents the purpose for data collection.

DccfEvent

5.1.6.2.13

Represents the event type exposed by DCCF

EventParamReport

5.1.6.2.10

Represents a summarized report for one event parameter.

FormattingInstruction

5.1.6.2.6

Contains data or analytics formatting Instructions.

NdccfAnalyticsSubscription

5.1.6.2.2

Represents an Individual DCCF Analytics Subscription resource.

NdccfAnalyticsSubscriptionNotification

5.1.6.2.4

Represents a notification that corresponds with an Individual DCCF Analytics Subscription resource.

NdccfDataSubscription

5.1.6.2.3

Represents an Individual DCCF Data Subscription resource.

NdccfDataSubscriptionNotification

5.1.6.2.5

Represents a notification that corresponds with an Individual DCCF Data Subscription resource.

NotifSummaryReport

5.1.6.2.9

Represents summarized notifications based on processing instructions.

ParameterProcessingInstruction

5.1.6.2.8

Contains an event parameter name and the respective event parameter values and sets of attributes to be used in summarized reports.

ProcessingInstruction

5.1.6.2.7

Contains instructions related to the processing (e.g. clubbing) of notifications.

ReportingOptions

5.1.6.2.11

Represents reporting options for notifications that are processed.

SummarizationAttribute

5.1.6.3.3

Represents attribute in the summarized report.

Table 5.1.6.1-2 specifies data types re-used by the Ndccf_DataManagement service based interface protocol from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the Ndccf_DataManagement service based interface.

Table 5.1.6.1-2: Ndccf_DataManagement re-used Data Types

Data type

Reference

Comments

Applicability

AfEvent

3GPP TS 29.517 [21]

Represents an AF Event id

AmfEventType

3GPP TS 29.518 [19]

Represents an AMF Event id

DataSubscription

3GPP TS 29.575 [25]

Represents a data subscription to one of various possible data sources.

DataNotification

3GPP TS 29.575 [25]

Represents a data subscription notification of one of various possible data sources.

DateTime

3GPP TS 29.571 [17]

Identifies the time.

DurationSec

3GPP TS 29.571 [17]

Time in seconds.

EventType

3GPP TS 29.503 [20]

Represents an UDM Event id

FetchInstruction

3GPP TS 29.576 [26]

The fetch instruction indicates whether the data or analytics can be fetched by the consumer.

NefEvent

3GPP TS 29.591 [22]

Represents a NEF Event id

NetworkAreaInfo

3GPP TS 29.554 [28]

Identifies a network area.

NfInstanceId

3GPP TS 29.571 [17]

NF instance identifier.

NfSetId

3GPP TS 29.571 [17]

NF set identifier.

NnwdafEventsSubscription

3GPP TS 29.520 [15]

Represents a NWDAF analytics subscription.

NnwdafEventsSubscriptionNotification

3GPP TS 29.520 [15]

Represents a NWDAF analytics subscription notification.

NumberAverage

3GPP TS 29.520 [15]

Represents average and variance of a parameter value.

SACEvent

3GPP TS 29.536 [27]

Represents a NSAC Event id

SmfEvent

3GPP TS 29.508 [18]

Represents a SMF Event id

Supi

3GPP TS 29.571 [17]

Contains a SUPI.

SupportedFeatures

3GPP TS 29.571 [17]

Used to negotiate the applicability of the optional features defined in table 5.1.8-1.

TimeWindow

3GPP TS 29.122 [23]

Represents a time window.

Uinteger

3GPP TS 29.571 [17]

Unsigned Integer.

Uri

3GPP TS 29.571 [17]

URI.

5.1.6.2 Structured data types

5.1.6.2.1 Introduction

This clause defines the structures to be used in resource representations.

5.1.6.2.2 Type NdccfAnalyticsSubscription

Table 5.1.6.2.2-1: Definition of type NdccfAnalyticsSubscription

Attribute name

Data type

P

Cardinality

Description

Applicability

anaSub

NnwdafEventsSubscription

M

1

Subscribed analytics events. (NOTE 1)

anaNotifUri

Uri

M

1

Notification target address.

anaNotifCorrId

string

M

1

Notification correlation identifier.

formatInstruct

FormattingInstruction

O

0..1

Formatting instructions to be used for sending event notifications.

procInstructs

array(ProcessingInstruction)

O

1..N

Processing instructions to be used for sending event notifications.

targetNfId

NfInstanceId

O

0..1

NF instance identifier to which the DCCF shall create the requested subscription. (NOTE 3)

targetNfSetId

NfSetId

O

0..1

NF set identifier to which the DCCF shall create the requested subscription.

(NOTE 3)

adrfId

NfInstanceId

O

0..1

Identifier of the ADRF to be used by the DCCF.

If the subscription is for runtime analytics (i.e. the "timePeriod" attribute is either absent or contains a time window in the future) then the DCCF shall store the notifications in this ADRF.

If the subscription is for historical analytics (i.e. the "timePeriod" attribute contains a time window in the past) then the DCCF shall retrieve the data from this ADRF. (NOTE 3)

adrfSetId

NfSetId

O

0..1

Identifier of the ADRF Set to be used by the DCCF.

If the subscription is for runtime analytics (i.e. the "timePeriod" attribute is either absent or contains a time window in the future) then the DCCF shall store the notifications in this ADRF Set.

If the subscription is for historical analytics (i.e. the "timePeriod" attribute contains a time window in the past) then the DCCF shall retrieve the data from this ADRF Set. (NOTE 3)

suppFeat

SupportedFeatures

C

0..1

This IE represents a list of Supported features as described in clause 5.1.8.

It shall be present if at least one feature defined in clause 5.1.8 is supported.

timePeriod

TimeWindow

O

0..1

Represents a start time and a stop time during which the analytics was performed or is requested to be performed. If this attribute is provided, then the attribute "monDur" within the reporting information of the attribute "anaSub" shall not be provided.

(NOTE 2)

dataCollectPurposes

array(DataCollectionPurpose)

O

1..N

The purposes of data collection. This attribute may only be provided if user consent is required depending on local policy and regulations and the consumer has not checked user consent.

checkedConsentInd

boolean

O

0..1

If set to "true", it indicates that the NF service consumer has already checked the user consent. The default value is "false".

UserConsent

suppFeat

SupportedFeatures

C

0..1

This attribute represents a list of Supported features as described in clause 5.1.8.

It shall be present in the POST request if at least one feature defined in clause 5.1.8 is supported, and it shall be present in the POST response if the NF service consumer included the"suppFeat" attribute in the POST request.

NOTE 1: The "notificationURI" and "notifCorreId" attributes of NnwdafEventsSubscription data type shall be ignored by the DCCF. The DCCF will provide the notification target address and the notification correlation ID of the DCCF itself in the NnwdafEventsSubscription data type during the event subscription request to the NWDAF.

NOTE 2: It includes the time period either in the past or in the future (i.e., start time as past time and stop time as future time is not allowed).

NOTE 3: "targetNfId" and "targetNfSetId" are mutually exclusive. "adrfId" and "adrfSetId" are also mutually exclusive.

5.1.6.2.3 Type NdccfDataSubscription

Table 5.1.6.2.3-1: Definition of type NdccfDataSubscription

Attribute name

Data type

P

Cardinality

Description

Applicability

dataSub

DataSubscription

M

1

Represents the requested events subscription.

(NOTE 1)

dataNotifUri

Uri

M

1

Notification target address.

dataNotifCorrId

string

M

1

Notification correlation identifier.

formatInstruct

FormattingInstruction

O

0..1

Formatting instructions to be used for sending event notifications.

procInstructs

array(ProcessingInstruction)

O

1..N

Processing instructions to be used for sending event notifications.

targetNfId

NfInstanceId

O

0..1

Data Producer NF instance identifier to which the DCCF shall create the requested subscription. (NOTE 3)

targetNfSetId

NfSetId

O

0..1

Data Producer NF set identifier to which the DCCF shall create the requested subscription. (NOTE 3)

adrfId

NfInstanceId

O

0..1

Identifier of the ADRF to be used by the DCCF.

If the subscription is for runtime data (i.e. the "timePeriod" attribute is either absent or contains a time window in the future) then the DCCF shall store the notifications in this ADRF.

If the subscription is for historical data (i.e. the "timePeriod" attribute contains a time window in the past) then the DCCF shall retrieve the data from this ADRF. (NOTE 3)

adrfSetId

NfSetId

O

0..1

Identifier of the ADRF Set to be used by the DCCF.

If the subscription is for runtime data (i.e. the "timePeriod" attribute is either absent or contains a time window in the future) then the DCCF shall store the notifications in this ADRF Set.

If the subscription is for historical data (i.e. the "timePeriod" attribute contains a time window in the past) then the DCCF shall retrieve the data from this ADRF Set. (NOTE 3)

suppFeat

SupportedFeatures

C

0..1

This IE represents a list of Supported features as described in clause 5.1.8.

It shall be present if at least one feature defined in clause 5.1.8 is supported.

timePeriod

TimeWindow

O

0..1

Represents a start time and a stop time during which data was collected or is requested to be collected. If this attribute is included, then the internal attributes of the data subscription that indicate a subscription duration (e.g. the "targetPeriod" attribute of an "eventSubs" attribute of an "smfDataSub" attribute, or the "monDur" attribute of the ReportingInformation data type) shall not be provided.

(NOTE 2)

dataCollectPurposes

array(DataCollectionPurpose)

O

1..N

The purposes of data collection. This attribute may only be provided if user consent is required depending on local policy and regulations and the consumer has not checked user consent.

checkedConsentInd

boolean

O

0..1

If set to "true", it indicates that the NF service consumer has already checked the user consent. The default value is "false".

UserConsent

suppFeat

SupportedFeatures

C

0..1

This attribute represents a list of Supported features as described in clause 5.1.8.

It shall be present in the POST request if at least one feature defined in clause 5.1.8 is supported, and it shall be present in the POST response if the NF service consumer included the"suppFeat" attribute in the POST request.

NOTE 1: The notification target address contained in the subscription attribute that is provided within the "dataSub" attribute (i.e. "eventNotifyUri" of "amfDataSub", "notifUri" of "smfDataSub", "callbackReference" of "udmDataSub", "notifUri" of "nefDataSub", "notifUri" of "afDataSub", "nfStatusNotificationUri" of "nrfDataSub", or "eventNotifyUri" of "nsacfDataSub") and the notification correlation ID contained in the subscription attribute that is provided within the "dataSub" attribute (i.e. the "notifyCorrelationId" of "amfDataSub", "notifId" of "smfDataSub", "notifyCorrelationId" of "udmDataSub", "notifId" of "nefDataSub", "notifId" of "afDataSub", or "notifyCorrelationId" of "nsacfDataSub") shall be ignored by the DCCF. The DCCF will provide the notification target address and the notification correlation ID of the DCCF itself in the data type during the event subscription request to each NF.

NOTE 2: It includes the time period either in the past or in the future (i.e., start time as past time and stop time as future time is not allowed).

NOTE 3: "targetNfId" and "targetNfSetId" are mutually exclusive. "adrfId" and "adrfSetId" are also mutually exclusive.

5.1.6.2.4 Type NdccfAnalyticsSubscriptionNotification

Table 5.1.6.2.4-1: Definition of type NdccfAnalyticsSubscriptionNotification

Attribute name

Data type

P

Cardinality

Description

Applicability

anaNotifications

array(NnwdafEventsSubscriptionNotification)

C

1..N

List of analytics subscription notifications. (NOTE 1, NOTE 3)

anaReports

array(NotifSummaryReport)

C

1..N

List of reports with summarized data from multiple analytics notifications that the DCCF has received from NWDAF. (NOTE 1)

fetchInstruct

FetchInstruction

C

0..1

Instructions for the NF service consumer to fetch the notifications itself. (NOTE 1, NOTE 2)

anaNotifCorrId

string

M

1

Notification correlation identifier.

terminationReq

boolean

O

0..1

If provided and set to "true", it indicates that the subscription is requested to be terminated, i.e. no further notifications related to this subscription will be provided. The default value is "false".

timeStamp

DateTime

M

1

It represents the time when DCCF completed preparation of the requested analytics. (NOTE 3)

NOTE 1: Exactly one of these attributes shall be provided.

NOTE 2: The "fetchInstruct" attribute shall not be included in Ndccf_DataManagement_Fetch response body.

NOTE 3: If the DCCF has received the notifications from another source without a timestamp, then the DCCF adds itself a timestamp based on the time it received the notification in "timeStampGen" attribute contained in "dataNotification" attribute within the EventNotification data type in the NnwdafEventsSubscriptionNotification data type.

5.1.6.2.5 Type NdccfDataSubscriptionNotification

Table 5.1.6.2.5-1: Definition of type NdccfDataSubscriptionNotification

Attribute name

Data type

P

Cardinality

Description

Applicability

dataNotif

DataNotification

C

0..1

Data subscription notification. (NOTE 1, NOTE 3)

dataReports

array(NotifSummaryReport)

C

1..N

List of reports with summarized data from multiple notifications received from data producer. (NOTE 1)

fetchInstruct

FetchInstruction

C

0..1

Instructions for the NF service consumer to fetch the notifications itself. (NOTE 1, NOTE 2)

dataNotifCorrId

string

M

1

Notification correlation identifier.

terminationReq

boolean

O

0..1

If provided and set to "true", it indicates that the subscription is requested to be terminated, i.e. no further notifications related to this subscription will be provided. The default value is "false".

timeStamp

DateTime

M

1

It represents the time when DCCF completed preparation of the requested analytics. (NOTE 3)

NOTE 1: Exactly one of these attributes shall be provided.

NOTE 2: The "fetchInstruct" attribute shall not be included in the response body of a Fetch operation.

NOTE 3: If the DCCF has received the notifications from another source without a timestamp, then the DCCF adds itself a timestamp based on the time it received the notification in the "timeStamp" attribute within the DataNotification data type.

5.1.6.2.6 Type FormattingInstruction

Table 5.1.6.2.6-1: Definition of type FormattingInstruction

Attribute name

Data type

P

Cardinality

Description

Applicability

consTrigNotif

boolean

O

0..1

If provided and set to "true", it indicates that notifications shall be buffered (sending only fetch instructions to the NF service consumer) until the NF service consumer requests their delivery using Ndccf_DataManagement or Nmfaf_3caDataManagement Service.

The default value is "false".

reportingOptions

ReportingOptions

O

0..1

This attribute is provided if the NF service consumer requires clubbing of notifications and its contents describe how the notifications shall be clubbed, i.e. when they should be sent.

5.1.6.2.7 Type ProcessingInstruction

Table 5.1.6.2.7-1: Definition of type ProcessingInstruction

Attribute name

Data type

P

Cardinality

Description

Applicability

eventId

DccfEvent

M

1

Identifies the (event exposure or analytics) event that the processing instructions apply to.

procInterval

DurationSec

M

1

Indicates the interval (in seconds) over which the processing of data for inclusion in each notification sent to consumers shall occur.

paramProcInstructs

array(ParameterProcessingInstruction)

O

1..N

List of event parameter name(s), and for each event parameter name, respective event parameter values and sets of the attributes to be used in the summarized reports.

5.1.6.2.8 Type ParameterProcessingInstruction

Table 5.1.6.2.8-1: Definition of type ParameterProcessingInstruction

Attribute name

Data type

P

Cardinality

Description

Applicability

name

string

M

1

This attribute contains a JSON pointer value (as defined in IETF RFC 6901 [24]) that references an attribute, i.e. a target location, within the notification object (e.g. of NefEventExposureNotif, AfEventExposureNotif, AmfEventNotification, NsmfEventExposureNotification, MonitoringReport, NotificationData, or SACEventReport data type) to which the processing instruction is applied.

values

array(Any type)

M

1..N

A list of values for the attribute identified by the "name" attribute, which shall be matched with values contained in the notifications received and summarized by the DCCF.

The data type of the elements of the list shall be the same as the type of the attribute identified by the "name" attribute.

sumAttrs

array(SummarizationAttribute)

M

1..N

Attributes requested to be used in the summarized reports.

aggrLevel

AggregationLevel

O

0..1

Indicates the aggregation level to which the processing instructions shall apply.

supis

array(Supi)

O

1..N

Indicates the UEs for which processed reports are requested. It may be provided only if "aggrLevel" is provided and is set to the value "UE".

areas

array(NetworkAreaInfo)

C

1..N

Indicates the Areas of Interest for which processed reports are requested. It shall be provided only if "aggrLevel" is provided and is set to the value "AOI".

5.1.6.2.9 Type NotifSummaryReport

Table 5.1.6.2.9-1: Definition of type NotifSummaryReport

Attribute name

Data type

P

Cardinality

Description

Applicability

eventId

DccfEvent

M

1

Identifies the (event exposure or analytics) event that this report applies to.

procInterval

DurationSec

M

1

Indicates the interval (in seconds) over which the processing of data for inclusion in this report occurred.

eventReports

array(EventParamReport)

M

1..N

List of event parameter reports.

5.1.6.2.10 Type EventParamReport

Table 5.1.6.2.10-1: Definition of type EventParamReport

Attribute name

Data type

P

Cardinality

Description

Applicability

name

string

M

1

The name of the reported parameter.

values

array(Any type)

M

1..N

The list of values of the reported parameter.

supi

Supi

C

0..1

Indicates the UE that this report is for. It shall be provided if the "aggrLevel" of the instructions had the value "UE".

area

NetworkAreaInfo

C

0..1

Indicates the Area of Interest that this report is for. It shall be provided if the "aggrLevel" of the instructions had the value "AOI".

spacing

NumberAverage

C

0..1

Contains the average and variance of the time interval separating two consecutive occurrences of the same event and parameter value. It shall be provided if available and the "SPACING" value was contained in the "paramProcInstructs" attribute of the instructions.

duration

NumberAverage

C

0..1

Contains the average and variance of time for which the parameter value applies. It shall be provided if available and the "DURATION" value was contained in the "paramProcInstructs" attribute of the instructions.

count

Uinteger

C

0..1

Represents the number of countable occurrences for the parameter. It shall be provided if available and the "OCCURRENCES" value was contained in the "paramProcInstructs" attribute of the instructions.

avgAndVar

NumberAverage

C

0..1

Contains the average and variance of the parameter value. It shall be provided if available and the "AVG_VAR" value was contained in the "paramProcInstructs" attribute of the instructions.

mostFreqVal

Any type

C

0..1

Contains the most frequent value among the elements of the reported "values" attribute. It shall be provided if available and the "FREQ_VAL" value was contained in the "paramProcInstructs" attribute of the instructions.

leastFreqVal

Any type

C

0..1

Contains the least frequent value among the elements of the reported "values" attribute. It shall be provided if available and the "FREQ_VAL" value was contained in the "paramProcInstructs" attribute of the instructions.

minValue

string

C

0..1

Identifies the minimum value of the parameter. It shall be provided if available and the "MIN_MAX" value was contained in the "paramProcInstructs" attribute of the instructions.

maxValue

string

C

0..1

Identifies the maximum value of the parameter. It shall be provided if available and the "MIN_MAX" value was contained in the "paramProcInstructs" attribute of the instructions.

5.1.6.2.11 Type ReportingOptions

Table 5.1.6.2.11-1: Definition of type ReportingOptions

Attribute name

Data type

P

Cardinality

Description

Applicability

notifyWindow

TimeWindow

C

0..1

Represents a start time and a stop time during which notifications shall be sent. (NOTE)

notifyPeriod

DurationSec

C

0..1

Indicates the period (in seconds) with which notifications are sent to the consumer, irrespective of whether the event occurs (e.g. every 30 minutes). (NOTE)

notifyPeriodInc

DurationSec

C

0..1

Indicates the time interval (in seconds) between the first two notifications (where the first one is sent upon event occurrence), and that the time interval between subsequent notifications shall be increased each time by the value of this attribute. (NOTE)

depEventSubId

string

C

0..1

Notifications for the present subscription are sent only upon occurrence of events of the subscription with identifier that matches this attribute. (NOTE)

minClubbedNotif

Uinteger

O

0..1

Indicates the minimum number of clubbed notifications.

maxClubbedNotif

Uinteger

O

0..1

Indicates the maximum number of clubbed notifications.

NOTE: Exactly one of these attributes shall be provided.

5.1.6.2.12 Void
5.1.6.2.13 DccfEvent

Table 5.1.6.2.13-1: Definition of type DccfEvent

Attribute name

Data type

P

Cardinality

Description

Applicability

nwdafEvent

NwdafEvent

C

0..1

Identifies the (event exposure or analytics) NWDAF event ID that the processing instructions apply to. (NOTE)

smfEvent

SmfEvent

C

0..1

Identifies the (event exposure or analytics) SMF event ID that the processing instructions apply to. (NOTE)

amfEvent

AmfEventType

C

0..1

Identifies the (event exposure or analytics) AMF event ID that the processing instructions apply to. (NOTE)

nefEvent

NefEvent

C

0..1

Identifies the (event exposure or analytics) NEF event ID that the processing instructions apply to. (NOTE)

udmEvent

EventType

C

0..1

Identifies the (event exposure or analytics) UDM event ID that the processing instructions apply to. (NOTE)

afEvent

AfEvent

C

0..1

Identifies the (event exposure or analytics) AF event ID that the processing instructions apply to. (NOTE)

sacEvent

SACEvent

C

0..1

Identifies the (event exposure or analytics) NSACF event ID that the processing instructions apply to. (NOTE)

nrfEvent

NotificationEventType

C

0..1

Identifies the (event exposure or analytics) NRF event ID that the processing instructions apply to. (NOTE)

NOTE: Exactly one of these attributes shall be provided.

5.1.6.3 Simple data types and enumerations

5.1.6.3.1 Introduction

This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses.

5.1.6.3.2 Simple data types

The simple data types defined in table 5.1.6.3.2-1 shall be supported.

Table 5.1.6.3.2-1: Simple data types

Type Name

Type Definition

Description

Applicability

n/a

5.1.6.3.3 Enumeration: SummarizationAttribute

Table 5.1.6.3.3-1: Enumeration SummarizationAttribute

Enumeration value

Description

Applicability

SPACING

Average and variance of the time interval separating two consecutive occurrences of the same event and parameter value, or periodicity for periodic reporting.

DURATION

Average and variance of the time for which the parameter value applies.

OCCURRENCES

Number of countable occurrences for the parameter.

AVG_VAR

Average and variance of the parameter.

FREQ_VAL

Most and least frequent values.

MIN_MAX

Maximum and minimum parameter values.

5.1.6.3.4 Enumeration: AggregationLevel

Table 5.1.6.3.4-1: Enumeration AggregationLevel

Enumeration value

Description

Applicability

UE

Indicates that the summarized reports shall be provided per UE.

AOI

Indicates that the summarized reports shall be provided per Area of Interest.

5.1.6.3.5 Enumeration: DataCollectionPurpose

Table 5.1.6.3.5-1: Enumeration DataCollectionPurpose

Enumeration value

Description

Applicability

ANALYTICS_GENERATION

The data is collected for generating the analytics.

MODEL_TRAINING

The data is collected for ML model training.

5.1.6.4 Data types describing alternative data types or combinations of data types

None in this release of the specification.

5.1.6.5 Binary data

None in this release of the specification.

5.1.7 Error Handling

5.1.7.1 General

For the Ndccf_DataManagement API, HTTP error responses shall be supported as specified in clause 4.8 of 3GPP TS 29.501 [5]. Protocol errors and application errors specified in table 5.2.7.2-1 of 3GPP TS 29.500 [4] shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in table 5.2.7.1-1 of 3GPP TS 29.500 [4].

In addition, the requirements in the following clauses are applicable for the Ndccf_DataManagement API.

5.1.7.2 Protocol Errors

No specific procedures for the Ndccf_DataManagement service are specified.

5.1.7.3 Application Errors

The application errors defined for the Ndccf_DataManagement service are listed in Table 5.1.7.3-1.

Table 5.1.7.3-1: Application errors

Application Error

HTTP status code

Description

SUBSCRIPTION_CANNOT_BE_SERVED

400 Bad Request

Indicates that the DCCF cannot use the contents of the request to either a) determine whether the subscription can already be served or interactions with the NWDAF and/or ADRF are required or b) determine what interactions with the NWDAF and/or ADRF are required (if it has determined that they are required).

USER_CONSENT_NOT_GRANTED

403 Forbidden

Indicates that the request shall be rejected because an impacted user consent is not granted.

5.1.8 Feature negotiation

The optional features in table 5.1.8-1 are defined for the Ndccf_DataManagement API. They shall be negotiated using the extensibility mechanism defined in clause 6.6 of 3GPP TS 29.500 [4].

Table 5.1.8-1: Supported Features

Feature number

Feature Name

Description

1

UserConsent

Indicates the support of detailed handling of user consent, e.g. indications that user consent has been checked and error responses related to the user consent is not granted.

5.1.9 Security

As indicated in 3GPP TS 33.501 [8] and 3GPP TS 29.500 [4], the access to the Ndccf_DataManagement API may be authorized by means of the OAuth2 protocol (see IETF RFC 6749 [9]), based on local configuration, using the "Client Credentials" authorization grant, where the NRF (see 3GPP TS 29.510 [10]) plays the role of the authorization server.

If OAuth2 is used, an NF Service Consumer, prior to consuming services offered by the Ndccf_DataManagement API, shall obtain a "token" from the authorization server, by invoking the Access Token Request service, as described in 3GPP TS 29.510 [10], clause 5.4.2.2.

NOTE: When multiple NRFs are deployed in a network, the NRF used as authorization server is the same NRF that the NF Service Consumer used for discovering the Ndccf_DataManagement service.

The Ndccf_DataManagement API defines a single scope "ndccf-datamanagement" for the entire service, and it does not define any additional scopes at resource or operation level.

5.2 Ndccf_ContextManagement Service API

5.2.1 Introduction

The Ndccf_ContextManagement shall use the Ndccf_ContextManagement API.

The API URI of the Ndccf_ContextManagement API shall be:

{apiRoot}/<apiName>/<apiVersion>

The request URIs used in HTTP requests from the NF service consumer towards the NF service producer shall have the Resource URI structure defined in clause 4.4.1 of 3GPP TS 29.501 [5], i.e.:

{apiRoot}/<apiName>/<apiVersion>/<apiSpecificResourceUriPart>

with the following components:

– The {apiRoot} shall be set as described in 3GPP TS 29.501 [5].

– The <apiName> shall be "ndccf-contextmanagement".

– The <apiVersion> shall be "v1".

– The <apiSpecificResourceUriPart> shall be set as described in clause 5.2.3.

5.2.2 Usage of HTTP

5.2.2.1 General

HTTP/2, IETF RFC 7540 [11], shall be used as specified in clause 5 of 3GPP TS 29.500 [4].

HTTP/2 shall be transported as specified in clause 5.3 of 3GPP TS 29.500 [4].

The OpenAPI [6] specification of HTTP messages and content bodies for the Ndccf_ContextManagement API is contained in Annex A.

5.2.2.2 HTTP standard headers

5.2.2.2.1 General

See clause 5.2.2 of 3GPP TS 29.500 [4] for the usage of HTTP standard headers.

5.2.2.2.2 Content type

JSON, IETF RFC 8259 [12], shall be used as content type of the HTTP bodies specified in the present specification as specified in clause 5.4 of 3GPP TS 29.500 [4]. The use of the JSON format shall be signalled by the content type "application/json".

"Problem Details" JSON object shall be used to indicate additional details of the error in a HTTP response body and shall be signalled by the content type "application/problem+json", as defined in IETF RFC 7807 [13].

5.2.2.3 HTTP custom headers

The mandatory HTTP custom header fields specified in clause 5.2.3.2 of 3GPP TS 29.500 [4] shall be supported, and the optional HTTP custom header fields specified in clause 5.2.3.3 of 3GPP TS 29.500 [4] may be supported.

5.2.3 Resources

5.2.3.1 Overview

This clause describes the structure for the Resource URIs and the resources and methods used for the service.

Figure 5.2.3.1-1 depicts the resource URIs structure for the Ndccf_ContextManagement API.

Figure 5.2.3.1-1: Resource URI structure of the Ndccf_ContextManagement API

Table 5.2.3.1-1 provides an overview of the resources and applicable HTTP methods.

Table 5.2.3.1-1: Resources and methods overview

Resource name

Resource URI

HTTP method or custom operation

Description

DCCF Data Collection Profiles

/data-collection-profiles

POST

Creates a new Individual DCCF Data Collection Profile resource.

Individual DCCF Data Collection Profile

/data-collection-profiles/{profileId}

PUT

Modifies an existing Individual DCCF Data Collection Profile resource.

DELETE

Deletes an Individual DCCF Data Collection Profile identified by {profileId}.

5.2.3.2 Resource: DCCF Data Collection Profiles

5.2.3.2.1 Description

The DCCF Data Collection Profiles resource represents all data collection profiles that exist in the Ndccf_ContextManagement service at a given DCCF.

5.2.3.2.2 Resource Definition

Resource URI: {apiRoot}/ndccf-contextmanagement/v<apiVersion>/data-collection-profiles

This resource shall support the resource URI variables defined in table 5.2.3.2.2-1.

Table 5.2.3.2.2-1: Resource URI variables for this resource

Name

Data type

Definition

apiRoot

string

See clause 5.2.1

5.2.3.2.3 Resource Standard Methods

5.2.3.2.3.1 POST

This method shall support the URI query parameters specified in table 5.2.3.2.3.1-1.

Table 5.2.3.2.3.1-1: URI query parameters supported by the POST method on this resource

Name

Data type

P

Cardinality

Description

Applicability

n/a

This method shall support the request data structures specified in table 5.2.3.2.3.1-2 and the response data structures and response codes specified in table 5.2.3.2.3.1-3.

Table 5.2.3.2.3.1-2: Data structures supported by the POST Request Body on this resource

Data type

P

Cardinality

Description

NdccfDataCollectionProfile

M

1

New Individual DCCF Data Collection Profile resource to be created

Table 5.2.3.2.3.1-3: Data structures supported by the POST Response Body on this resource

Data type

P

Cardinality

Response

codes

Description

NdccfDataCollectionProfile

M

1

201 Created

The creation of an Individual DCCF Data Collection Profile resource is confirmed and a representation of that resource is returned.

NOTE: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply.

Table 5.2.3.2.3.1-4: Headers supported by the 201 response code on this resource

Name

Data type

P

Cardinality

Description

Location

string

M

1

Contains the URI of the newly created resource, according to the structure: {apiRoot}/ndccf-contextmanagement/<apiVersion>/data-collection-profiles/{profileId}

5.2.3.2.4 Resource Custom Operations

None in this release of the specification.

5.2.3.3 Resource: Individual DCCF Data Collection Profile

5.2.3.3.1 Description

The Individual DCCF Data Collection Profile resource represents a single data collection profile to the Ndccf_ContextManagement service at a given DCCF.

5.2.3.3.2 Resource Definition

Resource URI: {apiRoot}/ndccf-contextmanagement/<apiVersion>/data-collection-profiles/{profileId}

This resource shall support the resource URI variables defined in table 5.2.3.3.2-1.

Table 5.2.3.3.2-1: Resource URI variables for this resource

Name

Data type

Definition

apiRoot

string

See clause 5.1.1

profileId

string

Identifies a data collection profile to the Ndccf_ContextManagement Service

5.2.3.3.3 Resource Standard Methods
5.2.3.3.3.1 PUT

This method shall support the URI query parameters specified in table 5.2.3.3.3.1-1.

Table 5.2.3.3.3.1-1: URI query parameters supported by the PUT method on this resource

Name

Data type

P

Cardinality

Description

Applicability

n/a

This method shall support the request data structures specified in table 5.2.3.3.3.1-2 and the response data structures and response codes specified in table 5.2.3.3.3.1-3.

Table 5.2.3.3.3.1-2: Data structures supported by the PUT Request Body on this resource

Data type

P

Cardinality

Description

NdccfDataCollectionProfile

M

1

Parameters to replace Individual DCCF Data Collection Profile resource.

Table 5.2.3.3.3.1-3: Data structures supported by the PUT Response Body on this resource

Data type

P

Cardinality

Response

codes

Description

NdccfDataCollectionProfile

M

1

200 OK

The Individual DCCF Data Collection Profile resource was modified successfully, and a representation of that resource is returned.

n/a

204 No Content

The Individual DCCF Data Collection Profile resource was modified successfully.

RedirectResponse

O

0..1

307 Temporary Redirect

Temporary redirection, during Individual DCCF Data Collection Profile modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative DCCF (service) instance.

RedirectResponse

O

0..1

308 Permanent Redirect

Permanent redirection, during Individual DCCF Data Collection Profile modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative DCCF (service) instance.

NOTE: The mandatory HTTP error status code for the PUT method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply.

Table 5.2.3.3.3.1-4: Headers supported by the 307 Response Code on this resource

Name

Data type

P

Cardinality

Description

Location

string

M

1

An alternative URI of the resource located in an alternative DCCF (service) instance.

3gpp-Sbi-Target-Nf-Id

string

O

0..1

Identifier of the target NF (service) instance towards which the request is redirected.

Table 5.2.3.3.3.1-5: Headers supported by the 308 Response Code on this resource

Name

Data type

P

Cardinality

Description

Location

string

M

1

An alternative URI of the resource located in an alternative DCCF (service) instance.

3gpp-Sbi-Target-Nf-Id

string

O

0..1

Identifier of the target NF (service) instance towards which the request is redirected.

5.2.3.3.3.2 DELETE

This method shall support the URI query parameters specified in table 5.2.3.3.3.2-1.

Table 5.2.3.3.3.2-1: URI query parameters supported by the DELETE method on this resource

Name

Data type

P

Cardinality

Description

Applicability

n/a

This method shall support the request data structures specified in table 5.2.3.3.3.2-2 and the response data structures and response codes specified in table 5.2.3.3.3.2-3.

Table 5.2.3.3.3.2-2: Data structures supported by the DELETE Request Body on this resource

Data type

P

Cardinality

Description

n/a

Table 5.2.3.3.3.2-3: Data structures supported by the DELETE Response Body on this resource

Data type

P

Cardinality

Response

codes

Description

n/a

204 No Content

The Individual DCCF Data Collection Profile resource was deleted successfully.

RedirectResponse

O

0..1

307 Temporary Redirect

Temporary redirection, during Individual DCCF Data Collection Profile deletion. The response shall include a Location header field containing an alternative URI of the resource located in an alternative DCCF (service) instance.

RedirectResponse

O

0..1

308 Permanent Redirect

Permanent redirection, during Individual DCCF Data Collection Profile deletion. The response shall include a Location header field containing an alternative URI of the resource located in an alternative DCCF (service) instance.

NOTE: The mandatory HTTP error status code for the DELETE method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply.

Table 5.2.3.3.3.2-4: Headers supported by the 307 Response Code on this resource

Name

Data type

P

Cardinality

Description

Location

string

M

1

An alternative URI of the resource located in an alternative DCCF (service) instance.

3gpp-Sbi-Target-Nf-Id

string

O

0..1

Identifier of the target NF (service) instance towards which the request is redirected.

Table 5.2.3.3.3.2-5: Headers supported by the 308 Response Code on this resource

Name

Data type

P

Cardinality

Description

Location

string

M

1

An alternative URI of the resource located in an alternative DCCF (service) instance.

3gpp-Sbi-Target-Nf-Id

string

O

0..1

Identifier of the target NF (service) instance towards which the request is redirected.

5.2.3.3.4 Resource Custom Operations

None in this release of the specification.

5.2.4 Custom Operations without associated resources

None in this release of the specification.

5.2.5 Notifications

None in this release of the specification.

5.2.6 Data Model

5.2.6.1 General

This clause specifies the application data model supported by the Ndccf_ContextManagement API.

Table 5.2.6.1-1 specifies the data types defined for the Ndccf_ContextManagement service based interface protocol.

Table 5.2.6.1-1: Ndccf_ContextManagement specific Data Types

Data type

Clause defined

Description

Applicability

NdccfDataCollectionProfile

5.2.6.2.2

Represents an Individual DCCF Data Collection Profile resource.

Table 5.2.6.1-2 specifies data types re-used by the Ndccf_ContextManagement service based interface protocol from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the Ndccf_ContextManagement service based interface.

Table 5.2.6.1-2: Ndccf_ContextManagement re-used Data Types

Data type

Reference

Comments

Applicability

DataSubscription

3GPP TS 29.575 [25]

Represents a data subscription to one of various possible data sources.

NfInstanceId

3GPP TS 29.571 [17]

NF instance identifier.

NfSetId

3GPP TS 29.571 [17]

NF Set identifier.

NnwdafEventsSubscription

3GPP TS 29.520 [15]

Represents an NWDAF analytics subscription.

5.2.6.2 Structured data types

5.2.6.2.1 Introduction

This clause defines the structures to be used in resource representations.

5.2.6.2.2 Type: NdccfDataCollectionProfile

Table 5.2.6.2.2-1: Definition of type NdccfDataCollectionProfile

Attribute name

Data type

P

Cardinality

Description

Applicability

anaSub

NnwdafEventsSubscription

C

0..1

Representation of the analytics events subscription that is used to collect analytics.

(NOTE 1)

dataSub

DataSubscription

C

0..1

Representation of the data subscription that is used to collect data.

(NOTE 1)

nwdafId

NfInstanceId

C

0..1

NF instance identifier of the NWDAF that this data collection profile belongs to. (NOTE 2)

adrfId

NfInstanceId

C

0..1

NF instance identifier of the ADRF that this data collection profile belongs to. (NOTE 2)

nwdafSetId

NfSetId

C

0..1

Identifier of the set of the NWDAF that this data collection profile belongs to. (NOTE 2)

adrfSetId

NfSetId

C

0..1

Identifier of the set of the ADRF that this data collection profile belongs to. (NOTE 2)

NOTE 1: Only one of these attributes shall be provided.

NOTE 2: Only one of these attributes shall be provided.

5.2.6.3 Simple data types and enumerations

5.2.6.3.1 Introduction

This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses.

5.2.6.3.2 Simple data types

The simple data types defined in table 5.2.6.3.2-1 shall be supported.

Table 5.2.6.3.2-1: Simple data types

Type Name

Type Definition

Description

Applicability

5.2.6.4 Data types describing alternative data types or combinations of data types

None in this release of the specification.

5.2.6.5 Binary data

None in this release of the specification.

5.2.7 Error Handling

5.2.7.1 General

For the Ndccf_ContextManagement API, HTTP error responses shall be supported as specified in clause 4.8 of 3GPP TS 29.501 [5]. Protocol errors and application errors specified in table 5.2.7.2-1 of 3GPP TS 29.500 [4] shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in table 5.2.7.1-1 of 3GPP TS 29.500 [4].

In addition, the requirements in the following clauses are applicable for the Ndccf_ContextManagement API.

5.2.7.2 Protocol Errors

No specific procedures for the Ndccf_ContextManagement service are specified.

5.2.7.3 Application Errors

The application errors defined for the Ndccf_ContextManagement service are listed in Table 5.2.7.3-1.

Table 5.2.7.3-1: Application errors

Application Error

HTTP status code

Description

5.2.8 Feature negotiation

The optional features in table 5.2.8-1 are defined for the Ndccf_ContextManagement API. They shall be negotiated using the extensibility mechanism defined in clause 6.6 of 3GPP TS 29.500 [4].

Table 5.2.8-1: Supported Features

Feature number

Feature Name

Description

5.2.9 Security

As indicated in 3GPP TS 33.501 [8] and 3GPP TS 29.500 [4], the access to the Ndccf_ContextManagement API may be authorized by means of the OAuth2 protocol (see IETF RFC 6749 [9]), based on local configuration, using the "Client Credentials" authorization grant, where the NRF (see 3GPP TS 29.510 [10]) plays the role of the authorization server.

If OAuth2 is used, an NF Service Consumer, prior to consuming services offered by the Ndccf_ContextManagement API, shall obtain a "token" from the authorization server, by invoking the Access Token Request service, as described in 3GPP TS 29.510 [10], clause 5.4.2.2.

NOTE: When multiple NRFs are deployed in a network, the NRF used as authorization server is the same NRF that the NF Service Consumer used for discovering the Ndccf_ContextManagement service.

The Ndccf_ContextManagement API defines a single scope "ndccf-contextmanagement" for the entire service, and it does not define any additional scopes at resource or operation level.

Annex A (normative):
OpenAPI specification