5.3 Nnwdaf_DataManagement Service API

29.5203GPP5G SystemNetwork Data Analytics ServicesRelease 17Stage 3TS

5.3.1 Introduction

The Nnwdaf_DataManagement Service shall use the Nnwdaf_DataManagement API.

The API URI of the Nnwdaf_DataManagement API shall be:

{apiRoot}/<apiName>/<apiVersion>

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

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

with the following components:

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

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

– The <apiVersion> shall be "v1".

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

5.3.2 Usage of HTTP

5.3.2.1 General

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

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

The OpenAPI [11] specification of HTTP messages and content bodies for the Nnwdaf_DataManagement is contained in Annex A.

5.3.2.2 HTTP standard headers

5.3.2.2.1 General

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

5.3.2.2.2 Content type

JSON, IETF RFC 8259 [10], shall be used as content type of the HTTP bodies specified in the present specification as specified in subclause 5.4 of 3GPP TS 29.500 [6]. 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 [15].

5.3.2.3 HTTP custom headers

The Nnwdaf_DataManagement Service API shall support mandatory HTTP custom header fields specified in subclause 5.2.3.2 of 3GPP TS 29.500 [6] and may support HTTP custom header fields specified in subclause 5.2.3.3 of 3GPP TS 29.500 [6].

In this release of the specification, no specific custom headers are defined for the Nnwdaf_DataManagement Service API.

5.3.3 Resources

5.3.3.1 Resource Structure

Figure 5.3.3.1-1: Resource URI structure of the Nnwdaf_DataManagement API

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

Table 5.3.3.1-1: Resources and methods overview

Resource name

Resource URI

HTTP method or custom operation

Description

NWDAF Data Management Subscriptions

/subscriptions

POST

Creates a new Individual NWDAF Data Management Subscription resource.

Individual NWDAF Data Management Subscription

/subscriptions/{subscriptionId}

DELETE

Deletes an Individual NWDAF Data Management Subscription identified by subresource {subscriptionId}.

PUT

Modifies an existing Individual NWDAF Data Management Subscription identified by subresource {subscriptionId}.

5.3.3.2 Resource: NWDAF Data Management Subscriptions

5.3.3.3 Resource: Individual NWDAF Data Management Subscription

5.3.4 Custom Operations without associated resources

5.3.5 Notifications

5.3.6 Data Model

5.3.7 Error handling

5.3.8 Feature negotiation

The optional features in table 5.3.8-1 are defined for the Nnwdaf_DataManagement API. They shall be negotiated using the extensibility mechanism defined in subclause 6.6 of 3GPP TS 29.500 [6].

Table 5.3.8-1: Supported Features

Feature number

Feature Name

Description

5.3.9 Security