5 Services offered by the SMF for NIDD

29.5423GPP5G SystemRelease 18Session management services for Non-IP Data Delivery (NIDD)Stage 3TS

5.1 Introduction

The SMF supports the following service(s) for NIDD.

Table 5.1-1: NF Service(s) provided by SMF for NIDD

Service Name	Description	Example Consumer
Nsmf_NIDD	This service allows the NF consumer NF to deliver NIDD MT data to PDU sessions.	NEF

5.2 Nsmf_NIDD Service

5.2.1 Service Description

The Nsmf_NIDD service operates on the PDU Sessions. The service operations exposed by this service allow an NF consumer (i.e. NEF) to deliver NEF anchored Mobile Terminated (MT) data for a given PDU session of a UE towards the SMF.

The Nsmf_NIDD service supports the following service operations:

Table 5.2.1-1: Service operations supported by the Nsmf_NIDD service

Service Operations	Description	Operation Semantics	Example Consumer(s)
Delivery	Deliver MT NIDD user data to the PDU session of the UE.	Request/Response	NEF

5.2.2 Service Operations

5.2.2.1 Introduction

See Table 5.2.1-1 for an overview of the service operations supported by the Nsmf_NIDD service.

5.2.2.2 Delivery

5.2.2.2.1 General

The Delivery service operation shall be used to transfer NEF anchored MT data for a given PDU session.

It is used in the following procedures:

– NEF anchored Mobile Terminated Data Transport (see clause 4.25.5 of 3GPP TS 23.502 [3]).

The NF Service Consumer (i.e. NEF) shall deliver MT data to the SMF by using the HTTP POST method ("deliver" custom operation) as shown in Figure 5.2.2.2.1-1.

Figure 5.2.2.2.1-1: Transfer MT Data

1. The NF Service Consumer shall send a POST request to the URI of "deliver" custom operation on an Individual PDU session resource in the SMF. The payload body of the POST request shall contain the MT data to be delivered.

NOTE: The URI of the individual PDU session resource is provided by SMF to the NEF during SMF-NEF connection creation (see clause 5.2.2.2.1 of 3GPP TS 29.541 [14]).

2a. On success, "204 No Content" shall be returned.

2b. On failure or redirection, one of the HTTP status code listed in Table 6.1.3.2.4.2.2-2 shall be returned. For a 4xx/5xx response, the message body may contain a DeliverError or ProblemDetails object, with the "cause" attribute indicating the cause of the failure. If Estimated Maximum Waiting Time is received from AMF, the SMF shall include it in the message body.