5 Services offered by the MNPF

29.5783GPP5G SystemMobile Number Portability ServicesRelease 18Stage 3TS

5.1 Introduction

The MNPF offers the following services via the Nmnpf interface:

– Nmnpf_NPStatus Service

Table 5.1-1 summarizes the corresponding APIs defined for this specification.

Table 5.1-1: API Descriptions

Service Name	Clause	Description	OpenAPI Specification File	apiName	Annex
Nmnpf_NPStatus	6.1	MNPF Number portability Status Service	TS29578_Nmnpf_NPStatus.yaml	nmnpf-npstatus	A.2

5.2 Nmnpf_NPStatus Service

5.2.1 Service Description

See 3GPP TS 23.540 [14] clause 6.7.1.

5.2.2 Service Operations

5.2.2.1 Introduction

For the Nmnpf_NPStatus service the following service operations are defined:

– Get

The Nmnpf_NPStatus Service is used by Consumer NFs (SMS-GMSC, NRF, SCP) to retrieve the UE’s subscription network by means of the Get service operation.

5.2.2.2 Get

5.2.2.2.1 General

This clause provides a general description of the Get service operation.

5.2.2.2.2 MNPF Status information retrieval

Figure 5.2.2.2.2-1 shows a scenario where the NF service consumer (e.g. SMS-GMSC, NRF, SCP) sends a request to the MNPF to receive the UE’s Subscription Network (see also clause 5.1.7.2, clause 5.1.7.3 and clause 5.1.7.4 of 3GPP TS 23.540 [14]. The request contains the UE’s identity (/{gpsi}).

Figure 5.2.2.2.2-1: Requesting a UE’s NP statusI

1. The NF service consumer (e.g. SMS-GMSC, NRF, SCP) sends a GET request to the resource representing the UE’s number portability status.

2a. On success, the MNPF responds with "200 OK" with the message body containing the UE’s Number Portability Status Information.

2b. If there is no valid information for the UE, HTTP status code "404 Not Found" shall be returned including additional error information in the response body (in the "ProblemDetails" element).

On failure, the appropriate HTTP status code indicating the error shall be returned and appropriate additional error information should be returned in the GET response body.