Add files using upload-large-folder tool

.gitattributes

@@ -58,3 +58,15 @@ saved_model/**/* filter=lfs diff=lfs merge=lfs -text
 # Video files - compressed
 *.mp4 filter=lfs diff=lfs merge=lfs -text
 *.webm filter=lfs diff=lfs merge=lfs -text
+original/38865-i00.docx filter=lfs diff=lfs merge=lfs -text
+original/23700-97-i10.docx filter=lfs diff=lfs merge=lfs -text
+original/23436-i20.docx filter=lfs diff=lfs merge=lfs -text
+original/33898-i01.docx filter=lfs diff=lfs merge=lfs -text
+original/36305-i00.docx filter=lfs diff=lfs merge=lfs -text
+original/36304-i00.docx filter=lfs diff=lfs merge=lfs -text
+original/22261-ic0.docx filter=lfs diff=lfs merge=lfs -text
+original/29558-i40.docx filter=lfs diff=lfs merge=lfs -text
+original/24257-i20.docx filter=lfs diff=lfs merge=lfs -text
+original/23288-i40.docx filter=lfs diff=lfs merge=lfs -text
+original/38101-5-i40.docx filter=lfs diff=lfs merge=lfs -text
+original/38741-i00.docx filter=lfs diff=lfs merge=lfs -text

gsma/29_series/29176/raw.md

@@ -0,0 +1,1328 @@
+
+
+# 3GPP TS 29.176 V18.0.0 (2023-12)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; IP Multimedia Subsystems (IMS); Media Function (MF) Services; Stage 3 (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis
+
+Valbonne - FRANCE
+
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                            |    |
+|------------------------------------------------------------|----|
+| Foreword .....                                             | 5  |
+| 1 Scope.....                                               | 7  |
+| 2 References.....                                          | 7  |
+| 3 Definitions, symbols and abbreviations .....             | 8  |
+| 3.1 Definitions.....                                       | 8  |
+| 3.2 Symbols.....                                           | 8  |
+| 3.3 Abbreviations .....                                    | 8  |
+| 4 Overview.....                                            | 8  |
+| 5 Services offered by the MF.....                          | 9  |
+| 5.1 Introduction .....                                     | 9  |
+| 5.2 Nmf_MediaResourceManagement (MRM) Service .....        | 9  |
+| 5.2.1 Service Description .....                            | 9  |
+| 5.2.2 Service Operations.....                              | 9  |
+| 5.2.2.1 Introduction.....                                  | 9  |
+| 5.2.2.2 Nmf_MRM_Create Service Operation.....              | 9  |
+| 5.2.2.2.1 General .....                                    | 9  |
+| 5.2.2.2.2 Creation of a new media context.....             | 10 |
+| 5.2.2.3 Nmf_MRM_Update Service Operation.....              | 11 |
+| 5.2.2.3.1 General .....                                    | 11 |
+| 5.2.2.3.2 Updating an existing media context.....          | 11 |
+| 5.2.2.4 Nmf_MRM_Delete Service Operation.....              | 12 |
+| 5.2.2.4.1 General .....                                    | 12 |
+| 5.2.2.4.2 Deleting an existing media context.....          | 12 |
+| 6 API Definitions .....                                    | 13 |
+| 6.1 Nmf_MRM Service API .....                              | 13 |
+| 6.1.1 Introduction .....                                   | 13 |
+| 6.1.2 Usage of HTTP.....                                   | 13 |
+| 6.1.2.1 General.....                                       | 13 |
+| 6.1.2.2 HTTP standard headers.....                         | 13 |
+| 6.1.2.2.1 General .....                                    | 13 |
+| 6.1.2.2.2 Content type .....                               | 13 |
+| 6.1.2.3 HTTP custom headers.....                           | 13 |
+| 6.1.3 Resources.....                                       | 14 |
+| 6.1.3.1 Overview.....                                      | 14 |
+| 6.1.3.2 Resource: Contexts Collection.....                 | 14 |
+| 6.1.3.2.1 Description .....                                | 14 |
+| 6.1.3.2.2 Resource Definition.....                         | 14 |
+| 6.1.3.2.3 Resource Standard Methods.....                   | 15 |
+| 6.1.3.2.4 Resource Custom Operations.....                  | 16 |
+| 6.1.3.3 Resource: Individual Context .....                 | 16 |
+| 6.1.3.3.1 Description .....                                | 16 |
+| 6.1.3.3.2 Resource Definition.....                         | 16 |
+| 6.1.3.3.3 Resource Standard Methods.....                   | 16 |
+| 6.1.3.3.4 Resource Custom Operations.....                  | 18 |
+| 6.1.4 Custom Operations without associated resources ..... | 18 |
+| 6.1.5 Notifications .....                                  | 19 |
+| 6.1.6 Data Model .....                                     | 19 |
+| 6.1.6.1 General.....                                       | 19 |
+| 6.1.6.2 Structured data types.....                         | 19 |
+| 6.1.6.2.1 Introduction .....                               | 19 |
+| 6.1.6.2.2 Type: MediaContext.....                          | 20 |
+| 6.1.6.2.3 Type: TerminationInfo .....                      | 20 |
+| 6.1.6.2.4 Type: MediaInfo.....                             | 21 |
+
+|                               |                                         |           |
+|-------------------------------|-----------------------------------------|-----------|
+| 6.1.6.2.5                     | Type: DcMedia.....                      | 22        |
+| 6.1.6.2.6                     | Type: ArMedia.....                      | 24        |
+| 6.1.6.3                       | Simple data types and enumerations..... | 24        |
+| 6.1.6.3.1                     | Introduction .....                      | 24        |
+| 6.1.6.3.2                     | Simple data types .....                 | 24        |
+| 6.1.7                         | Error Handling .....                    | 24        |
+| 6.1.7.1                       | General .....                           | 24        |
+| 6.1.7.2                       | Protocol Errors .....                   | 24        |
+| 6.1.7.3                       | Application Errors.....                 | 25        |
+| 6.1.8                         | Feature negotiation .....               | 25        |
+| 6.1.9                         | Security .....                          | 25        |
+| 6.1.10                        | HTTP redirection.....                   | 25        |
+| <b>Annex A (normative):</b>   | <b>OpenAPI specification .....</b>      | <b>26</b> |
+| A.1                           | General.....                            | 26        |
+| A.2                           | Ndcmf_MRM API .....                     | 26        |
+| <b>Annex B (informative):</b> | <b>Change history.....</b>              | <b>31</b> |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# --- 1 Scope
+
+The present document specifies the stage 3 protocol and data model for the Nmf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the Media Function (MF).
+
+The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
+
+The IP Multimedia Subsystem (IMS) Data Channel (DC) architecture and procedures are specified in annex AC of 3GPP TS 23.228 [14].
+
+The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5].
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
+- [3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
+- [4] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
+- [5] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
+- [6] OpenAPI: "OpenAPI Specification Version 3.0.0", <https://spec.openapis.org/oas/v3.0.0>.
+- [7] 3GPP TR 21.900: "Technical Specification Group working methods".
+- [8] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
+- [9] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
+- [10] 3GPP TS 29.510: "5G System; Network Function Repository Services; Stage 3".
+- [11] IETF RFC 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2)".
+- [12] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
+- [13] IETF RFC 7807: "Problem Details for HTTP APIs".
+- [14] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
+- [15] IETF RFC 6902: " JavaScript Object Notation (JSON) Patch".
+- [16] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces Stage 3".
+
+# 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+*Definition format (Normal)*
+
+**<defined term>**: <definition>.
+
+**example:** text used to clarify abstract rules by applying them literally.
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|     |                                       |
+|-----|---------------------------------------|
+| DC2 | Reference point between MF and IMS AS |
+|-----|---------------------------------------|
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|        |                                            |
+|--------|--------------------------------------------|
+| AR     | Augmented Reality                          |
+| DC     | Data Channel                               |
+| MF     | Media Function                             |
+| IMS AS | IP Multimedia Subsystem Application Server |
+
+# 4 Overview
+
+Within the IMS DC architecture, the MF offers services to the IMS AS via the Nmf service based interface (see 3GPP TS 23.228 [14]).
+
+Figure 4.1-1 provides the reference model (in service-based interface representation and in reference point representation), with focus on the MF services.
+
+![Diagram of the reference model showing the IMS AS connected to the MF via the DC2 reference point and the Nmf service-based interface.](98a45dd7d474e067b7533cc966c11e95_img.jpg)
+
+The diagram illustrates the reference model for the Media Function (MF). On the left, a white rectangular box is labeled 'IMS AS'. A horizontal line connects this box to a green rectangular box on the right, which is labeled 'MF'. The connection line is labeled 'DC2' near the IMS AS and 'Nmf' near the MF. The 'Nmf' label is positioned next to a small circle on the left side of the MF box, indicating a service-based interface.
+
+Diagram of the reference model showing the IMS AS connected to the MF via the DC2 reference point and the Nmf service-based interface.
+
+**Figure 4.1-1: Reference model – MF**
+
+DC2 is the reference point between MF and IMS AS.
+
+# 5 Services offered by the MF
+
+## 5.1 Introduction
+
+The MF offers the following services via the Nmf interface:
+
+- Nmf\_MediaResourceManagement (MRM) 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 |
+|--------------|--------|---------------------------------------|----------------------------|---------|-------|
+| Nmf_MRM      | 6.1    | Nmf Media Resource Management Service | TS29176_Nmf_MRM.yaml       | nmf-mrm | A.2   |
+
+## 5.2 Nmf\_MediaResourceManagement (MRM) Service
+
+### 5.2.1 Service Description
+
+The Nmf\_MRM service as defined in 3GPP TS 23.228 [14] is provided by the Media Function (MF). This service enables the consumer to create, update and delete media resources. Data Channel (DC) and Augmented Reality (AR) are two capabilities supported by MF.
+
+The media resource represents a media context including one or multiple media terminations. A media termination includes media resources for one or multiple medias on the Mb interface. When a media pass through the MF, there is one termination for the input stream and one termination for the output stream.
+
+### 5.2.2 Service Operations
+
+#### 5.2.2.1 Introduction
+
+The Nmf\_MRM service supports the following service operation.
+
+**Table 5.2.2.1-1: Service operations supported by the Nmf\_MRM service**
+
+| Service Operations | Description                                                                          | Operation Semantics | Example Consumer(s) |
+|--------------------|--------------------------------------------------------------------------------------|---------------------|---------------------|
+| Create             | Create a new media context including one or multiple media terminations.             | Request/Response    | IMS AS              |
+| Update             | Update the one or multiple existing media resources within a specific media context. | Request/Response    | IMS AS              |
+| Delete             | Delete a specific media context including all the existing terminations and medias.  | Request/Response    | IMS AS              |
+
+#### 5.2.2.2 Nmf\_MRM\_Create Service Operation
+
+##### 5.2.2.2.1 General
+
+The Nmf\_MRM\_Create service operation is used by an NF service consumer to create a media context including one or multiple terminations and reserve media resources for anchoring one or multiple medias of Mb interface in each
+
+termination on MF. The consumer NF may also include application function (e.g. DCSF, DC AS) specification information requested by the application layer to be applied on the media by the MF.
+
+##### 5.2.2.2.2 Creation of a new media context
+
+The NF service consumer shall request a new context by using HTTP method POST with "{apiRoot}/nmf/<apiVersion>/contexts" as resource URI representing the "Contexts Collection", see clause 6.1.3.2.
+
+![Sequence diagram showing the creation of a media context. The NF Service Consumer sends a POST request to the MF. The MF responds with either a 201 Created (MediaContext) or a 4xx/5xx (ProblemDetails) or 3xx response.](053f1077d592e6622cd21dc4bb4cb366_img.jpg)
+
+```
+
+sequenceDiagram
+    participant NF Service Consumer
+    participant MF
+    Note left of NF Service Consumer: POST ../contexts (MediaContext)
+    NF Service Consumer->>MF: 1. POST ../contexts (MediaContext)
+    Note right of MF: -2a. 201 Created (MediaContext)
+    MF-->>NF Service Consumer: -2a. 201 Created (MediaContext)
+    Note right of MF: -2b. 4xx/5xx (ProblemDetails) or 3xx
+    MF-->>NF Service Consumer: -2b. 4xx/5xx (ProblemDetails) or 3xx
+  
+```
+
+Sequence diagram showing the creation of a media context. The NF Service Consumer sends a POST request to the MF. The MF responds with either a 201 Created (MediaContext) or a 4xx/5xx (ProblemDetails) or 3xx response.
+
+Figure 5.2.2.2.2-1 Creation of a media context
+
+1. The NF Service Consumer shall send a POST request to create an "Individual Context" resource in the MF. The payload body of the POST request shall contain a representation of the individual context resource to be created.
+
+The NF service consumer shall include list of termination descriptors in the HTTP message body. Each termination descriptor shall include list of media stream descriptors. Each media stream descriptor shall include:
+
+- Media ID, i.e. a unique identity of the media stream within the media context instance;
+- Remote Mb specifications, i.e. the media stream IP address and port allocated at the remote endpoint, i.e. remote UE, remote network.
+- Media resource description, which includes
+  - 1) Media resource type, e.g. DC, AR.
+  - 2) If media resource type is set to "DC", the DC media specification shall be included. The DC media specification shall include:
+    - a) Data Channel Mapping and Configuration information when originating/terminating data channel media flows on the Mb interface. It shall include the SCTP stream Id for the DC, and may include subprotocol, order, maxRetry, maxTime and priority may be included.
+    - b) Maximum Message Size, which represents the maximum size to be expected.
+    - c) Data Channel Port, which represents the port of SCTP port for the Data Channel.
+    - d) Security Setup, which identifies the security setup of the DTLS connection.
+    - e) Security Certificate Fingerprint, which identifies the security certificate fingerprint.
+    - f) Security Transport Identity, which identifies transport layer identity.
+
+For establishing bootstrap data channel or P2A/A2P application data channel, the following parameters shall be included:
+
+- a) media proxy configuration applicable to the media flow;
+- b) remote MDC1/MDC2 media specification information to be applied on the media by the MF;
+- c) Replacement HTTP URL for each streamId allocated by the application layer representing the application list (e.g. graphical user interface) offered to the IMS subscriber via the MDC1 interface.
+
+3) If media resource type is set to "AR", the AR media resource description shall be included, which includes:
+
+a) Media processing specification.
+
+2a. Upon the reception of the HTTP POST request, if the request is accepted and no error occur, the MF shall:
+
+- create a new media context;
+- assign a media contextId;
+- assign a terminationId for each termination descriptor; and
+- reserve media resources for each mediaId.
+
+The MF shall include a HTTP Location header to provide the location of a newly created resource (MediaContext) together with the status code 201 indicating the requested resource is created in the response message.
+
+2b. On failure, one of the HTTP status code listed in Table 6.1.3.2.3.1-3 shall be returned. For a 4xx/5xx response, the message body shall contain a ProblemDetails structure with the "cause" attribute set to one of the application errors listed in Table 6.1.3.2.3.1-3.
+
+On redirection, the MF shall include 3xx status code, which shall contain a Location header with an URI pointing to the endpoint to another MF (service) instance.
+
+#### 5.2.2.3 Nmf\_MRM\_Update Service Operation
+
+##### 5.2.2.3.1 General
+
+The Nmf\_MRM\_Update service operation is used by an NF service consumer to update one or multiple existing media resources within a specific media context on MF. Terminations and/or Medias can be added, modified, or deleted within an Update request.
+
+##### 5.2.2.3.2 Updating an existing media context
+
+The NF Service Consumer shall modify the context by using HTTP method PATCH with the URI "{apiRoot}/nmf/<apiVersion>/contexts/{contextId}" as resource URI representing the "Individual Context ", see clause 6.1.3.3.
+
+![Sequence diagram showing the interaction between an NF Service Consumer and an MF for updating a media context. The consumer sends a PATCH request to the MF. The MF responds with one of three options: 2a. 204 No Content, 2b. 200 OK (MediaContext), or 2c. 4xx/5xx (ProblemDetails) or 3xx.](ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg)
+
+```
+
+sequenceDiagram
+    participant NF Service Consumer
+    participant MF
+    Note left of NF Service Consumer: Update a media context
+    NF Service Consumer->>MF: 1. PATCH .../contexts/{contextId} (PatchData)
+    MF-->>NF Service Consumer: 2a. 204 No Content
+    MF-->>NF Service Consumer: 2b. 200 OK (MediaContext)
+    MF-->>NF Service Consumer: 2c. 4xx/5xx (ProblemDetails) or 3xx
+  
+```
+
+Sequence diagram showing the interaction between an NF Service Consumer and an MF for updating a media context. The consumer sends a PATCH request to the MF. The MF responds with one of three options: 2a. 204 No Content, 2b. 200 OK (MediaContext), or 2c. 4xx/5xx (ProblemDetails) or 3xx.
+
+Figure 5.2.2.3.2-1 Update a media context
+
+1. The NF Service Consumer shall send a PATCH request to modify a context resource in the MF. The modification may be for adding, updating or deleting terminations of the existing media context.
+
+For adding, removing or updating a termination in an existing MediaContext, the payload body of the PATCH request shall contain an "add", "remove" or "replace" PATCH operation respectively, with one item of the attribute "terminations" of the MediaContext.
+
+- 2a. On success, if the change is to delete the existing termination and MF accepts the request change, the MF shall return the status code 204 No Content.
+- 2b. On success, if the change is to add a new termination or to update the existing termination and DCMF accepts the request change, the MF shall return the status code 200 OK. The response shall contain the new resource representation of the resource Individual Context, which includes the added and modified resource or its sub-resource.
+- 2c On failure, one of the HTTP status code listed in Table 6.1.3.3.3.1-3 indicating the error shall be returned. For a 4xx/5xx response, the message body shall contain a ProblemDetails structure with the "cause" attribute set to one of the application errors listed in Table 6.1.3.3.3.1-3.
+
+On redirection, the MF shall return 3xx status code, which shall contain a Location header with an URI pointing to the endpoint to another MF (service) instance.
+
+#### 5.2.2.4 Nmf\_MRM\_Delete Service Operation
+
+##### 5.2.2.4.1 General
+
+The Nmf\_MRM\_Delete service operation is used by an NF service consumer to delete an existing media context including all existing terminations and medias on MF previously created by itself.
+
+##### 5.2.2.4.2 Deleting an existing media context
+
+The NF Service Consumer shall delete an existing context by using HTTP method DELETE with the URI "{apiRoot}/nmf/<apiVersion>/contexts/{contextId}" as resource URI representing the "Individual Context ", see clause 6.1.3.3.
+
+![Sequence diagram showing the interaction between an NF Service Consumer and an MF for deleting a media context. The consumer sends a DELETE request to the MF. The MF responds with either a 204 No Content (success) or a 4xx/5xx (ProblemDetails) or 3xx (redirection) response.](af6be343f0c0a8f155f965dcf337b8af_img.jpg)
+
+```
+
+sequenceDiagram
+    participant NF Service Consumer
+    participant MF
+    Note left of NF Service Consumer: 1. DELETE .../contexts/{contextId}
+    NF Service Consumer->>MF: 1. DELETE .../contexts/{contextId}
+    Note right of MF: -2a. 204 No Content
+    MF-->>NF Service Consumer: -2a. 204 No Content
+    Note right of MF: 2b. 4xx/5xx (ProblemDetails) or 3xx
+    MF-->>NF Service Consumer: 2b. 4xx/5xx (ProblemDetails) or 3xx
+  
+```
+
+Sequence diagram showing the interaction between an NF Service Consumer and an MF for deleting a media context. The consumer sends a DELETE request to the MF. The MF responds with either a 204 No Content (success) or a 4xx/5xx (ProblemDetails) or 3xx (redirection) response.
+
+Figure 5.2.2.4.2-1 Delete a media context
+
+- 1. The NF Service Consumer shall send a DELETE request to delete an existing context resource in the MF.
+- 2a. On success, the request is accepted, the MF shall reply with the status code 204 No Content indicating the resource identified by context ID is successfully deleted in the response message.
+- 2b. On failure, one of the HTTP status code listed in Table 6.1.3.3.3.2-3 indicating the error shall be returned. For a 4xx/5xx response, the message body shall contain a ProblemDetails structure with the "cause" attribute set to one of the application errors listed in Table 6.1.3.3.3.2-3.
+
+On redirection, the MF shall return 3xx status code, which shall contain a Location header with an URI pointing to the endpoint to another MF (service) instance.
+
+# 6 API Definitions
+
+## 6.1 Nmf\_MRM Service API
+
+### 6.1.1 Introduction
+
+The Nmf\_MRM service shall use the Ndcmf\_MRM API.
+
+The API URI of the Nmf\_MRM 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 " nmf\_mrm".
+- The <apiVersion> shall be "v1".
+- The <apiSpecificResourceUriPart> shall be set as described in clause 6.1.3.
+
+### 6.1.2 Usage of HTTP
+
+#### 6.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 Nmf\_MRM API is contained in Annex A.
+
+#### 6.1.2.2 HTTP standard headers
+
+##### 6.1.2.2.1 General
+
+See clause 5.2.2 of 3GPP TS 29.500 [4] for the usage of HTTP standard headers.
+
+##### 6.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].
+
+The use of JSON Patch (IETF RFC 6902 [15]) format in a HTTP request body shall be signaled by the content type "application/json-patch+json".
+
+#### 6.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.
+
+### 6.1.3 Resources
+
+#### 6.1.3.1 Overview
+
+This clause describes the structure for the Resource URIs and the resources and methods used for the service.
+
+Figure 6.1.3.1-1 depicts the resource URIs structure for the Nmf\_MRM API.
+
+![Diagram showing the resource URI structure for the Nmf_MRM API. The root is {apiRoot}/nmf-mrm/<apiVersion>. It branches to /contexts, which then branches to /{contextId}.](16c1175b5f05a4b55e6d396fc51b15b3_img.jpg)
+
+```
+
+graph TD
+    Root["{apiRoot}/nmf-mrm/<apiVersion>"] --> Contexts["/contexts"]
+    Contexts --> ContextId["/{contextId}"]
+  
+```
+
+Diagram showing the resource URI structure for the Nmf\_MRM API. The root is {apiRoot}/nmf-mrm/. It branches to /contexts, which then branches to /{contextId}.
+
+**Figure 6.1.3.1-1: Resource URI structure of the Nmf\_MRM API**
+
+Table 6.1.3.1-1 provides an overview of the resources and applicable HTTP methods.
+
+**Table 6.1.3.1-1: Resources and methods overview**
+
+| Resource purpose/name | Resource URI (relative path after API URI) | HTTP method or custom operation | Description (service operation)                                            |
+|-----------------------|--------------------------------------------|---------------------------------|----------------------------------------------------------------------------|
+| Contexts Collection   | /contexts                                  | POST                            | Creates a new Individual Context resource.                                 |
+| Individual Context    | /contexts/{contextId}                      | PATCH                           | Updates an existing Individual Context resource identified by {contextId}  |
+|                       |                                            | DELETE                          | Deletes an existing Individual Context resource identified by {contextId}. |
+
+#### 6.1.3.2 Resource: Contexts Collection
+
+##### 6.1.3.2.1 Description
+
+The Contexts Collection resource represents a collection of contexts created by NF service consumers of Nmf\_MRM service at a given MF. The resource is modelled as Collection resource archetype (see clause C.2 of 3GPP TS 29.501 [2]).
+
+##### 6.1.3.2.2 Resource Definition
+
+Resource URI: {apiRoot}/ nmf\_mrm/<apiVersion>/contexts
+
+This resource shall support the resource URI variables defined in table 6.1.3.2.2-1.
+
+**Table 6.1.3.2.2-1: Resource URI variables for this resource**
+
+| Name    | Data type | Definition       |
+|---------|-----------|------------------|
+| apiRoot | string    | See clause 6.1.1 |
+
+##### 6.1.3.2.3 Resource Standard Methods
+
+###### 6.1.3.2.3.1 POST
+
+This method shall support the URI query parameters specified in table 6.1.3.2.3.1-1.
+
+**Table 6.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 6.1.3.2.3.1-2 and the response data structures and response codes specified in table 6.1.3.2.3.1-3.
+
+**Table 6.1.3.2.3.1-2: Data structures supported by the POST Request Body on this resource**
+
+| Data type    | P | Cardinality | Description                               |
+|--------------|---|-------------|-------------------------------------------|
+| MediaContext | M | 1           | Creates a new Individual Context resource |
+
+**Table 6.1.3.2.3.1-3: Data structures supported by the POST Response Body on this resource**
+
+| Data type        | P | Cardinality | Response codes            | Description                                                                                                          |
+|------------------|---|-------------|---------------------------|----------------------------------------------------------------------------------------------------------------------|
+| MediaContext     | M | 1           | 201<br>Created            | The creation of an Individual Media Context resource is confirmed and a representation of that resource is returned. |
+| RedirectResponse | O | 0..1        | 307<br>Temporary Redirect | Temporary redirection. (NOTE 2)                                                                                      |
+| RedirectResponse | O | 0..1        | 308<br>Permanent Redirect | Permanent redirection. (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: RedirectResponse may be inserted by an SCP, see clause 6.10.9.1 of 3GPP TS 29.500 [4].
+
+**Table 6.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}/nfmf-mrm/<apiVersion>/contexts/{contextId}. |
+
+**Table 6.1.3.2.3.1-5: 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 on an alternative MF (service) instance.<br>Or the same URI, if a request is redirected to the same target resource via a different SCP. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target MF instance ID towards which the request is redirected.                                                                                                    |
+
+**Table 6.1.3.2.3.1-6: 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 on an alternative MF (service) instance.<br>Or the same URI, if a request is redirected to the same target resource via a different SCP. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target MF instance ID towards which the request is redirected.                                                                                                    |
+
+##### 6.1.3.2.4 Resource Custom Operations
+
+None in the release of this specification.
+
+#### 6.1.3.3 Resource: Individual Context
+
+##### 6.1.3.3.1 Description
+
+The Individual Context resource represents an individual context created by the NF service consumers of Nmf\_MRM service at a given MF. This resource is modelled as the Document resource archetype (see clause C.1 of 3GPP TS 29.501 [2]).
+
+##### 6.1.3.3.2 Resource Definition
+
+Resource URI: {apiRoot}/nmf\_mrm/<apiVersion>/contexts/{contextId}
+
+The <apiVersion> shall be set as described in clause 6.3.1.
+
+This resource shall support the resource URI variables defined in table 6.1.3.3.2-1.
+
+**Table 6.1.3.3.2-1: Resource URI variables for this resource**
+
+| Name      | Data type | Definition                                               |
+|-----------|-----------|----------------------------------------------------------|
+| apiRoot   | string    | See clause 6.1.1                                         |
+| contextId | string    | Identifies an individual context to the Nmf_MRM service. |
+
+##### 6.1.3.3.3 Resource Standard Methods
+
+###### 6.1.3.3.3.1 PATCH
+
+This method shall support the URI query parameters specified in table 6.1.3.3.3.1-1.
+
+**Table 6.1.3.3.3.1-1: URI query parameters supported by the PATCH method on this resource**
+
+| Name | Data type | P | Cardinality | Description | Applicability |
+|------|-----------|---|-------------|-------------|---------------|
+| n/a  |           |   |             |             |               |
+
+This method shall support the request data structures specified in table 6.1.3.3.3.1-2 and the response data structures and response codes specified in table 6.1.3.3.3.1-3.
+
+**Table 6.1.3.3.3.1-2: Data structures supported by the PATCH Request Body on this resource**
+
+| Data type        | P | Cardinality | Description                                                               |
+|------------------|---|-------------|---------------------------------------------------------------------------|
+| array(PatchItem) | M | 1..N        | Document describes the modification(s) to an Individual Context resource. |
+
+**Table 6.1.3.3.3.1-3: Data structures supported by the PATCH Response Body on this resource**
+
+| Data type        | P | Cardinality | Response codes         | Description                                                                                                                                                                                                                         |
+|------------------|---|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| MediaContext     | M | 1..N        | 200 OK                 | Represents a successful update on the media context.                                                                                                                                                                                |
+| n/a              |   |             | 204 No Content         |                                                                                                                                                                                                                                     |
+| RedirectResponse | O | 0..1        | 307 Temporary Redirect | Temporary redirection. (NOTE 2)                                                                                                                                                                                                     |
+| RedirectResponse | O | 0..1        | 308 Permanent Redirect | Permanent redirection. (NOTE 2)                                                                                                                                                                                                     |
+| ProblemDetails   | O | 0..1        | 403 Forbidden          | Indicates the modification of media context has failed due to application error.<br><br>The "cause" attribute may be used to indicate one of the following application errors:<br>- MEDIA_ID_CONFLICT<br>- MEDIA_CONNECTION_CHANGED |
+| ProblemDetails   | O | 0..1        | 404 Not Found          | Indicates the modification of media context has failed due to application error.<br><br>The "cause" attribute may be used to indicate one of the following application errors:<br>- CONTEXT_NOT_FOUND                               |
+
+NOTE 1: The mandatory HTTP error status code for the PATCH method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply.  
+NOTE 2: RedirectResponse may be inserted by an SCP, see clause 6.10.9.1 of 3GPP TS 29.500 [4].
+
+**Table 6.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 on an alternative MF (service) instance.<br>Or the same URI, if a request is redirected to the same target resource via a different SCP. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target MF instance ID towards which the request is redirected.                                                                                                    |
+
+**Table 6.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 on an alternative MF (service) instance.<br>Or the same URI, if a request is redirected to the same target resource via a different SCP. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target MF instance ID towards which the request is redirected.                                                                                                    |
+
+###### 6.1.3.3.3.2 DELETE
+
+This method shall support the URI query parameters specified in table 6.1.3.3.3.2-1.
+
+**Table 6.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 6.1.3.3.3.2-2 and the response data structures and response codes specified in table 6.1.3.3.3.2-3.
+
+**Table 6.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 6.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         |                                                                                                                                                                                                 |
+| RedirectResponse | O | 0..1        | 307 Temporary Redirect | Temporary redirection. (NOTE 2)                                                                                                                                                                 |
+| RedirectResponse | O | 0..1        | 308 Permanent Redirect | Permanent redirection. (NOTE 2)                                                                                                                                                                 |
+| Problem Details  | O | 0..1        | 404 Not Found          | Indicates the deletion of the context has failed due to application error.<br><br>The "cause" attribute may be used to indicate one of the following application errors:<br>- CONTEXT NOT FOUND |
+
+NOTE 1: 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.  
+NOTE 2: RedirectResponse may be inserted by an SCP, see clause 6.10.9.1 of 3GPP TS 29.500 [4].
+
+**Table 6.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 on an alternative MF (service) instance.<br>Or the same URI, if a request is redirected to the same target resource via a different SCP. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target MF instance ID towards which the request is redirected.                                                                                                    |
+
+**Table 6.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 on an alternative MF (service) instance.<br>Or the same URI, if a request is redirected to the same target resource via a different SCP. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target MF instance ID towards which the request is redirected.                                                                                                    |
+
+##### 6.1.3.3.4 Resource Custom Operations
+
+None in the release of specification.
+
+### 6.1.4 Custom Operations without associated resources
+
+None in this release of specification.
+
+### 6.1.5 Notifications
+
+None in this release of specification.
+
+### 6.1.6 Data Model
+
+#### 6.1.6.1 General
+
+This clause specifies the application data model supported by the API.
+
+Table 6.1.6.1-1 specifies the data types defined for the Nmf\_MRM service based interface protocol.
+
+**Table 6.1.6.1-1: Nmf\_MRM specific Data Types**
+
+| Data type       | Clause defined | Description                                      | Applicability |
+|-----------------|----------------|--------------------------------------------------|---------------|
+| MediaContext    | 6.1.6.2.2      | Represents an individual context resource on MF. |               |
+| TerminationInfo | 6.1.6.2.3      | Represents the termination information.          |               |
+| MediaInfo       | 6.1.6.2.4      | Represents the media Information.                |               |
+| DcMedia         | 6.1.6.2.5      | Represents the DC media descriptor.              |               |
+| ArMedia         | 6.1.6.2.6      | Represents the AR media descriptor.              |               |
+
+Table 6.1.6.1-2 specifies data types re-used by the Nmf\_MRM 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 Nmf\_MRM service based interface.
+
+**Table 6.1.6.1-2: Nmf\_MRM re-used Data Types**
+
+| Data type         | Reference           | Comments                                                  | Applicability |
+|-------------------|---------------------|-----------------------------------------------------------|---------------|
+| ProblemDetails    | 3GPP TS 29.571 [16] | Problem Details                                           |               |
+| MediaId           | 3GPP TS 29.571 [16] | Uniquely identifies one media flow within an IMS session. |               |
+| MaxMessageSize    | 3GPP TS 29.571 [16] | Max SCTP user message size.                               |               |
+| MediaResourceType | 3GPP TS 29.571 [16] | Media resource types.                                     |               |
+| MediaProxy        | 3GPP TS 29.571 [16] | Media proxy configuration applicable to the media flow    |               |
+| SecuritySetup     | 3GPP TS 29.571 [16] | Security setup of the DTLS association.                   |               |
+| DcEndpoint        | 3GPP TS 29.571 [16] | DC endpoint                                               |               |
+| DcStream          | 3GPP TS 29.571 [16] | Data channel stream information.                          |               |
+| ReplaceHttpUrl    | 3GPP TS 29.571 [16] | Replacement HTTP URL allocated by the application layer.  |               |
+| Uri               | 3GPP TS 29.571 [16] | Uri                                                       |               |
+| Endpoint          | 3GPP TS 29.571 [16] | Represents the IP endpoint.                               | Endpoint      |
+
+#### 6.1.6.2 Structured data types
+
+##### 6.1.6.2.1 Introduction
+
+This clause defines the structures to be used in resource representations.
+
+##### 6.1.6.2.2 Type: MediaContext
+
+Table 6.1.6.2.2-1: Definition of type MediaContext
+
+| Attribute name | Data type              | P | Cardinality | Description                                                                                                         | Applicability |
+|----------------|------------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------|---------------|
+| contextId      | string                 | C | 0..1        | Identifies a specific context. It is assigned by the MF when creating a new context, i.e. Nmf_MRM_Create operation. |               |
+| terminations   | array(TerminationInfo) | M | 1..N        | Represents the media terminations                                                                                   |               |
+
+##### 6.1.6.2.3 Type: TerminationInfo
+
+Table 6.1.6.2.3-1: Definition of type TerminationInfo
+
+| Attribute name | Data type        | P | Cardinality | Description                                                                                                                                                                                                                                                                      | Applicability |
+|----------------|------------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| terminationId  | string           | C | 0..1        | Identifies a specific media termination. It is assigned by the MF when creating a new termination. It shall be included in the response of adding a new media termination, i.e., the Nmf_MRM_Create operation and in the Nmf_MRM_Update operation with adding a new termination. |               |
+| medias         | array(MediaInfo) | M | 1..N        | Represent the list of media resources for one or multiple medias on the Mb interface.                                                                                                                                                                                            |               |
+
+##### 6.1.6.2.4 Type: MediaInfo
+
+Table 6.1.6.2.4-1: Definition of type MediaInfo
+
+| Attribute name     | Data type         | P | Cardinality | Description                                                                                                                                                                                                                                                                                                                                                                       | Applicability |
+|--------------------|-------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| mediaId            | string            | M | 1           | Identifies a media stream, e.g. data channel.                                                                                                                                                                                                                                                                                                                                     |               |
+| mediaResourceType  | MediaResourceType | M | 1           | Represents the media resource type, e.g. DC, AR.                                                                                                                                                                                                                                                                                                                                  |               |
+| localMbEndpoint    | Endpoint          | C | 0..1        | Represents the local IP address and port number of the local endpoint of MF on the Mb interface.<br>It will be allocated by MF.<br>It shall be contained in the response when creating a new media stream, i.e. Nmf_MRM_Create operation or Nmf_MRM_Update operation with adding a new termination or adding a media in an existing termination. (NOTE 1, NOTE 2)                 |               |
+| remoteMbEndpoint   | Endpoint          | C | 0..1        | Represents the IP address and port number of the remote endpoint on the Mb interface, e.g. remote UE.<br>It shall be contained in the request of creating a new media stream, i.e. Nmf_MRM_Create operation or Nmf_MRM_Update operation with adding a new termination or adding a media in an existing termination. It can be Null when originating a new media. (NOTE 1, NOTE 2) |               |
+| dcMedia            | DcMedia           | C | 0..1        | Represents the data channel media descriptors. It shall be contained if the mediaResourceType is set to "DC".                                                                                                                                                                                                                                                                     |               |
+| arMedia            | ArMedia           | C | 0..1        | Represents the AR media descriptors. It shall be contained if the mediaResourceType is set to "AR".                                                                                                                                                                                                                                                                               |               |
+| mediaProcessingURL | Uri               | C | 0..1        | The mediaProcessingURL indicates the address where MF receive service-related media instructions. It shall be contained in the response when creating a new media stream, i.e. Nmf_MRM_Create operation or Nmf_MRM_Update operation with adding a new termination or adding a media in an existing termination. (NOTE 1)                                                          |               |
+
+NOTE 1: The IE cannot be changed once the media has been established.
+
+NOTE 2: The attribute "transport" inside Endpoint data type shall be set to value only "UDP".
+
+##### 6.1.6.2.5 Type: DcMedia
+
+**Table 6.1.6.2.5-1: Definition of type DcMedia**
+
+| Attribute name     | Data type               | P | Cardinality | Description                                                                                                                                                                                                                                                                                                                                     | Applicability |
+|--------------------|-------------------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| mediaProxyConfig   | MediaProxy              | C | 0..1        | Represents the media proxy configuration. It shall be included if the mediald represents bootstrap or P2A/A2P application data channels.                                                                                                                                                                                                        |               |
+| replaceHttpUrl     | Map(ReplacementHttpUrl) | C | 0..1        | A map (list of key-value pairs where streamId is used as key of the map) of ReplacementHttpUrl.<br>Represents URL for the specific IMS subscriber when requesting the application list (e.g. graphical user interface) via the MDC1 interface. It shall be included if the mediald represents bootstrap data channel and streamId is 0 and 100. |               |
+| remoteMdc1Endpoint | Endpoint                | C | 0..1        | Represents the remote MDC1 media endpoint information, i.e. the IP address and port number of DCSF. It shall be included if the mediald represents a bootstrap data channel.                                                                                                                                                                    |               |
+| remoteMdc2Endpoint | Endpoint                | C | 0..1        | Represents the remote MDC2 media endpoint address, i.e. the IP address and port number of DC AS. It shall be included if the mediald represents a P2A/A2P application data channel and the mediaProxyConfig is set to "HTTP".                                                                                                                   |               |
+| localMdc1Endpoint  | Endpoint                | C | 0..1        | Represents the local MF MDC1 media endpoint information. It will be allocated by MF and contained in the response when the mediald represents a bootstrap data channel.                                                                                                                                                                         |               |
+| localMdc2Endpoint  | Endpoint                | C | 0..1        | Represents the local MF MDC2 media endpoint information. It will be allocated by MF and contained in the response when the mediald represents a P2A/A2P application data channel.                                                                                                                                                               |               |
+| mdc2Protocol       | string                  | O | 0..1        | Represents the transport layer protocols for MDC2 interface. It may be included when mediaProxyConfig is set "HTTP" and remoteMdc2Endpoint is present. This IE is formatted as the following pattern, for example:<br>'UDP/DTLS/SCTP'                                                                                                           |               |
+| streams            | map(DcStream)           | M | 1..N        | A map (list of key-value pairs where streamId is used as key of the map) of DcStream.<br>Represents the data channel mapping and configuration information when originating/terminating data channel media flows on the Mb interface.                                                                                                           |               |
+| maxMessageSize     | MaxMessageSize          | O | 0..1        | Represents the maximum size of to be expected.                                                                                                                                                                                                                                                                                                  |               |
+| localDcEndpoint    | DcEndpoint              | C | 0..1        | Represents the DC endpoint for the Data Channel.<br>It will be allocated by MF.<br>It shall be contained in the response when creating a new media stream, i.e. Nmf_MRM_Create operation or Nmf_MRM_Update operation with adding a new termination or adding a media in an existing termination. (NOTE)                                         |               |
+
+|                                                                     |               |   |      |                                                                                                                                                                                                                                                                                                                                              |  |
+|---------------------------------------------------------------------|---------------|---|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|
+| remoteDcEndpoint                                                    | DcEndpoint    | C | 0..1 | Represents the DC Endpoint for the Data Channel on the Mb interface. It shall be contained in the request of creating a new media stream, i.e. Nmf_MRM_Create operation or Nmf_MRM_Update operation with adding a new termination or adding a media in an existing termination. It can be NULL when originating a data channel media. (NOTE) |  |
+| securitySetup                                                       | SecuritySetup | O | 0..1 | Represents the security set up of the DTLS association.                                                                                                                                                                                                                                                                                      |  |
+| NOTE: The IE cannot be changed once the media has been established. |               |   |      |                                                                                                                                                                                                                                                                                                                                              |  |
+
+##### 6.1.6.2.6 Type: ArMedia
+
+**Table 6.1.6.2.6-1: Definition of type ArMedia**
+
+| Attribute name | Data type | P | Cardinality | Description | Applicability |
+|----------------|-----------|---|-------------|-------------|---------------|
+|                |           |   |             |             |               |
+
+Editor's note: The definition of ArMedia is FFS.
+
+#### 6.1.6.3 Simple data types and enumerations
+
+##### 6.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.
+
+##### 6.1.6.3.2 Simple data types
+
+The simple data types defined in table 6.1.6.3.2-1 shall be supported.
+
+**Table 6.1.6.3.2-1: Simple data types**
+
+| Type Name | Type Definition | Description | Applicability |
+|-----------|-----------------|-------------|---------------|
+|           |                 |             |               |
+
+### 6.1.7 Error Handling
+
+#### 6.1.7.1 General
+
+For the Nmf\_MRM 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 Nmf\_MRM API.
+
+#### 6.1.7.2 Protocol Errors
+
+No specific procedures for the Nmf\_MRM service are specified.
+
+#### 6.1.7.3 Application Errors
+
+The application errors defined for the Nmf\_MRM service are listed in Table 6.1.7.3-1.
+
+**Table 6.1.7.3-1: Application errors**
+
+| Application Error        | HTTP status code | Description                                                                                                                                                                                           |
+|--------------------------|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CONTEXT_NOT_FOUND        | 404 Not Found    | Indicates that the requested context is not found in the MF.                                                                                                                                          |
+| MEDIA_ID_CONFLICT        | 403 Forbidden    | Indicates that mediald which identifies the newly added media has existed within the specific termination.                                                                                            |
+| MEDIA_CONNECTION_CHANGED | 403 Forbidden    | Indicates that the connection information which has been marked that cannot be changed once the media has established is changed in the request. including the remoteMbEndpoint, localMbEndpoint etc. |
+
+### 6.1.8 Feature negotiation
+
+The optional features in table 6.1.8-1 are defined for the Nmf\_MRM API. They shall be negotiated using the extensibility mechanism defined in clause 6.6 of 3GPP TS 29.500 [4].
+
+**Table 6.1.8-1: Supported Features**
+
+| Feature number | Feature Name | Description |
+|----------------|--------------|-------------|
+|                |              |             |
+
+### 6.1.9 Security
+
+As indicated in 3GPP TS 33.501 [8] and 3GPP TS 29.500 [4], the access to the Nmf\_MRM 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 Nmf\_MRM 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 Nmf\_MRM service.
+
+The Nmf\_MRM API defines a single scope "nmf-mrm" for the entire service, and it does not define any additional scopes at resource or operation level.
+
+### 6.1.10 HTTP redirection
+
+An HTTP request may be redirected to a different MF service instance when using direct or indirect communications (see 3GPP TS 29.500 [4]).
+
+An SCP that reselects a different MF producer instance will return the NF Instance ID of the new MF producer instance in the 3gpp-Sbi-Producer-Id header, as specified in clause 6.10.3.4 of 3GPP TS 29.500 [4].
+
+If an MF redirects a service request to a different MF using an 307 Temporary Redirect or 308 Permanent Redirect status code, the identity of the new MF towards which the service request is redirected shall be indicated in the 3gpp-Sbi-Target-Nf-Id header of the 307 Temporary Redirect or 308 Permanent Redirect response as specified in clause 6.10.9.1 of 3GPP TS 29.500 [4].
+
+# Annex A (normative): OpenAPI specification
+
+## A.1 General
+
+This Annex specifies the formal definition of the API(s) defined in the present specification. It consists of OpenAPI specifications in YAML format.
+
+This Annex takes precedence when being discrepant to other parts of the specification with respect to the encoding of information elements and methods within the API(s).
+
+NOTE 1: The semantics and procedures, as well as conditions, e.g. for the applicability and allowed combinations of attributes or values, not expressed in the OpenAPI definitions but defined in other parts of the specification also apply.
+
+Informative copies of the OpenAPI specification files contained in this 3GPP Technical Specification are available on a Git-based repository that uses the GitLab software version control system (see clause 5.3.1 of 3GPP TS 29.501 [5] and clause 5B of 3GPP TR 21.900 [7]).
+
+## A.2 Ndcnf\_MRM API
+
+```
+openapi: 3.0.0
+
+info:
+  title: 'MF Media Resource Management (MRM) Service'
+  version: 1.0.0-alpha.1
+  description: |
+    MF Media Resource Management (MRM) Service.
+    © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+    All rights reserved.
+
+externalDocs:
+  description: >
+    3GPP TS 29.176 V18.0.0; IP Multimedia Subsystem (IMS); Media Function (MF) Services; Stage 3.
+  url: https://www.3gpp.org/ftp/Specs/archive/29_series/29.176/
+
+servers:
+  - url: '{apiRoot}/nmf-mrm/v1'
+    variables:
+      apiRoot:
+        default: https://example.com
+        description: apiRoot as defined in clause 4.4 of 3GPP TS 29.501
+
+security:
+  - {}
+  - oAuth2ClientCredentials:
+    - nmf-mrm
+
+paths:
+
+  /contexts:
+    post:
+      summary: Create a new media context.
+      operationId: CreateMediaContext
+      tags:
+        - MediaContext(Collection)
+      requestBody:
+        required: true
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/MediaContext'
+      responses:
+        '201':
+          description: Success
+          content:
+```
+
+```
+
+    application/json:
+      schema:
+        $ref: '#/components/schemas/MediaContext'
+  headers:
+    Location:
+      description: >
+        Contains the URI of the newly created resource, according to the structure:
+        {apiRoot}/nmf-mrm/<version>/contexts/{contextId}
+      required: true
+      schema:
+        type: string
+  '307':
+    description: Temporary Redirect
+    content:
+      application/json:
+        schema:
+          $ref: 'TS29571_CommonData.yaml#/components/schemas/RedirectResponse'
+    headers:
+      Location:
+        description: The URI pointing to the resource located on the redirect target MF.
+        required: true
+        schema:
+          type: string
+  '308':
+    description: Permanent Redirect
+    content:
+      application/json:
+        schema:
+          $ref: 'TS29571_CommonData.yaml#/components/schemas/RedirectResponse'
+    headers:
+      Location:
+        description: The URI pointing to the resource located on the redirect target MF.
+        required: true
+        schema:
+          type: string
+  '400':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/400'
+  '401':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/401'
+  '403':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/403'
+  '404':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/404'
+  '411':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/411'
+  '413':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/413'
+  '415':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/415'
+  '429':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/429'
+  '500':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/500'
+  '503':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/503'
+  default:
+    $ref: 'TS29571_CommonData.yaml#/components/responses/default'
+
+/contexts/{contextId}:
+
+  patch:
+    summary: Update Media Context
+    operationId: UpdateMediaContext
+    tags:
+      - Media Context ID (Document)
+    parameters:
+      - name: contextId
+        in: path
+        required: true
+        description: Unique ID of the Media Context to update.
+        schema:
+          type: string
+    requestBody:
+      content:
+        application/json-patch+json:
+          schema:
+            type: array
+            items:
+
+```
+
+```
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/PatchItem'
+      minItems: 1
+    required: true
+  responses:
+    '200':
+      description: Expected response to a valid request.
+      content:
+        application/json:
+          schema:
+            $ref: '#/components/schemas/MediaContext'
+    '204':
+      description: Expected response with empty body
+    '307':
+      description: Temporary Redirect
+      content:
+        application/json:
+          schema:
+            $ref: 'TS29571_CommonData.yaml#/components/schemas/RedirectResponse'
+      headers:
+        Location:
+          description: The URI pointing to the resource located on the redirect target MF.
+          required: true
+          schema:
+            type: string
+    '308':
+      description: Permanent Redirect
+      content:
+        application/json:
+          schema:
+            $ref: 'TS29571_CommonData.yaml#/components/schemas/RedirectResponse'
+      headers:
+        Location:
+          description: The URI pointing to the resource located on the redirect target MF.
+          required: true
+          schema:
+            type: string
+    '400':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/400'
+    '403':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/403'
+    '404':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/404'
+    '409':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/409'
+    '411':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/411'
+    '412':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/412'
+    '413':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/413'
+    '415':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/415'
+    '429':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/429'
+    '500':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/500'
+    '501':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/501'
+    '503':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/503'
+  default:
+    $ref: 'TS29571_CommonData.yaml#/components/responses/default'
+
+delete:
+  summary: Deletes a given Media Context
+  operationId: DeleteMediaContext
+  tags:
+    - Media Context ID (Document)
+  parameters:
+    - name: contextId
+      in: path
+      required: true
+      description: Unique ID of the Media Context to delete.
+      schema:
+        type: string
+  responses:
+    '204':
+      description: Expected response to a successful deletion.
+```
+
+```
+'307':
+  description: Temporary Redirect
+  content:
+    application/json:
+      schema:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/RedirectResponse'
+  headers:
+    Location:
+      description: The URI pointing to the resource located on the redirect target NRF.
+      required: true
+      schema:
+        type: string
+'308':
+  description: Permanent Redirect
+  content:
+    application/json:
+      schema:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/RedirectResponse'
+  headers:
+    Location:
+      description: The URI pointing to the resource located on the redirect target NRF.
+      required: true
+      schema:
+        type: string
+'400':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/400'
+'401':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/401'
+'403':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/403'
+'404':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/404'
+'411':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/411'
+'429':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/429'
+'500':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/500'
+'501':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/501'
+'503':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/503'
+default:
+  $ref: 'TS29571_CommonData.yaml#/components/responses/default'
+```
+
+### components:
+
+```
+securitySchemes:
+  oAuth2ClientCredentials:
+    type: oauth2
+    flows:
+      clientCredentials:
+        tokenUrl: '{nrfApiRoot}/oauth2/token'
+        scopes:
+          nmf-mrm: Access to the Nmf_MRM API.
+```
+
+### schemas:
+
+```
+MediaContext:
+  description: Information of a Media Context in a MF.
+  type: object
+  required:
+    - terminations
+  properties:
+    contextId:
+      type: string
+    terminations:
+      type: array
+      items:
+        $ref: '#/components/schemas/TerminationInfo'
+      minItems: 1
+
+TerminationInfo:
+  description: Represents the termination information.
+  type: object
+  required:
+    - medias
+  properties:
+```
+
+```
+    terminationId:
+      type: string
+    medias:
+      type: array
+      items:
+        $ref: '#/components/schemas/MediaInfo'
+      minItems: 1
+
+MediaInfo:
+  description: Represents the media information.
+  type: object
+  required:
+    - mediaId
+    - mediaResourceType
+  properties:
+    mediaId:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/MediaId'
+    mediaResourceType:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/MediaResourceType'
+    localMbEndpoint:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Endpoint'
+    remoteMbEndpoint:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Endpoint'
+    dcMedia:
+      $ref: '#/components/schemas/DcMedia'
+    mediaProcessingUri:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
+
+DcMedia:
+  description: Represents the DC media descriptor.
+  type: object
+  required:
+    - streams
+  properties:
+    mediaProxyConfig:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/MediaProxy'
+    replaceHttpUrl:
+      type: object
+      description: >
+        Contains a list of replacement HTTP URLs. The streamId attribute
+        within the ReplaceHttpUrl data type is the key of the map.
+      additionalProperties:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/ReplaceHttpUrl'
+      minProperties: 1
+    remoteMdc1Endpoint:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Endpoint'
+    remoteMdc2Endpoint:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Endpoint'
+    localMdc1Endpoint:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Endpoint'
+    localMdc2Endpoint:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Endpoint'
+    mdc2Protocol:
+      type: string
+    streams:
+      type: object
+      description: >
+        Contains a data channel mapping and configuration information. The streamId
+        attribute within the DcStream data type is the key of the map.
+      additionalProperties:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/DcStream'
+      minProperties: 1
+    maxMessageSize:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/MaxMessageSize'
+    localDcEndpoint:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/DcEndpoint'
+    remoteDcEndpoint:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/DcEndpoint'
+    securitySetup:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/SecuritySetup'
+```
+
+# Annex B (informative): Change history
+
+| Change history |              |           |    |     |     |                                                                       |  |             |
+|----------------|--------------|-----------|----|-----|-----|-----------------------------------------------------------------------|--|-------------|
+| Date           | Meeting      | TDoc      | CR | Rev | Cat | Subject/Comment                                                       |  | New version |
+| 2023-04        | CT4#115<br>e | C4-231552 |    |     |     | Version 0.1.0                                                         |  | 0.1.0       |
+| 2023-05        | CT4#116      | C4-232178 |    |     |     | Clause 4 Overview                                                     |  | 0.2.0       |
+| 2023-05        | CT4#116      | C4-232224 |    |     |     | Clause 5.1 Introduction of DCMF services                              |  | 0.2.0       |
+| 2023-05        | CT4#116      | C4-232506 |    |     |     | Service description and service operation introduction of MRM service |  | 0.2.0       |
+| 2023-05        | CT4#116      | C4-232607 |    |     |     | MRM API definition                                                    |  | 0.2.0       |
+| 2023-05        | CT4#116      | C4-232637 |    |     |     | MRM service operations                                                |  | 0.2.0       |
+| 2023-08        | CT4#117      | C4-233707 |    |     |     | Change DCMF to MF                                                     |  | 0.3.0       |
+| 2023-08        | CT4#117      | C4-233307 |    |     |     | Update the data channel related data types                            |  | 0.3.0       |
+| 2023-08        | CT4#117      | C4-233306 |    |     |     | Update MF service to support AR                                       |  | 0.3.0       |
+| 2023-10        | CT4#118      | C4-234539 |    |     |     | Update the scope                                                      |  | 0.4.0       |
+| 2023-10        | CT4#118      | C4-234540 |    |     |     | Support of Redirection                                                |  | 0.4.0       |
+| 2023-10        | CT4#118      | C4-234575 |    |     |     | Clarification on the DC media                                         |  | 0.4.0       |
+| 2023-10        | CT4#118      | C4-234543 |    |     |     | Editorial Corrections                                                 |  | 0.4.0       |
+| 2023-10        | CT4#118      | C4-234544 |    |     |     | Update the data model for AR remote cooperation                       |  | 0.4.0       |
+| 2023-10        | CT4#118      | C4-234341 |    |     |     | Usage of the apiVersion placeholder                                   |  | 0.4.0       |
+| 2023-11        | CT4#119      | C4-235576 |    |     |     | Move the Endpoint to Common Data                                      |  | 0.5.0       |
+| 2023-11        | CT4#119      | C4-235473 |    |     |     | OpenAPI of Nmf_MRM Service                                            |  | 0.5.0       |
+| 2023-12        | CT#102       | CP-233022 |    |     |     | Presented for information and approval                                |  | 1.0.0       |
+| 2023-12        | CT#102       | CP-233022 |    |     |     | Approved in TSC CT#102                                                |  | 18.0.0      |

gsma/29_series/29255/raw.md

@@ -0,0 +1,1229 @@
+
+
+# 3GPP TS 29.255 V18.2.0 (2023-12)
+
+*Technical Specification*
+
+**3rd Generation Partnership Project;  
+Technical Specification Group Core Network and Terminals;  
+5G System;  
+Uncrewed Aerial System Service Supplier (USS) Services;  
+Stage 3  
+(Release 18)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 5G logo, consisting of the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green, curved lines representing signal waves.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the letters "3GPP" in a stylized, bold, black font. The "G" has a red signal wave icon below it. To the right of the "P" is a small "TM" symbol.
+
+3GPP logo
+
+A GLOBAL INITIATIVE
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+# --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                 |    |
+|---------------------------------------------------------------------------------|----|
+| Foreword .....                                                                  | 5  |
+| 1 Scope.....                                                                    | 7  |
+| 2 References.....                                                               | 7  |
+| 3 Definitions of terms, symbols and abbreviations.....                          | 8  |
+| 3.1 Terms.....                                                                  | 8  |
+| 3.2 Symbols.....                                                                | 8  |
+| 3.3 Abbreviations .....                                                         | 8  |
+| 4 Services offered by the USS .....                                             | 8  |
+| 4.1 Introduction .....                                                          | 8  |
+| 4.2 Naf_Authentication Service .....                                            | 8  |
+| 4.2.1 Service Description .....                                                 | 8  |
+| 4.2.1.1 Overview.....                                                           | 8  |
+| 4.2.1.2 Service Architecture .....                                              | 9  |
+| 4.2.1.3 Network Functions.....                                                  | 9  |
+| 4.2.1.3.1 Uncrewed Aerial System Service Supplier (USS) .....                   | 9  |
+| 4.2.1.3.2 NF Service Consumers.....                                             | 9  |
+| 4.2.2 Service Operations.....                                                   | 10 |
+| 4.2.2.1 Introduction.....                                                       | 10 |
+| 4.2.2.2 Naf_Authentication_AuthenticateAuthorize Service operation .....        | 10 |
+| 4.2.2.2.1 General .....                                                         | 10 |
+| 4.2.2.2.2 Authentication and Authorization of the UAV .....                     | 10 |
+| 4.2.2.3 Naf_Authentication_Notification Service operation .....                 | 11 |
+| 4.2.2.3.1 General .....                                                         | 11 |
+| 4.2.2.3.2 Notification for Reauthentication, Reauthorization or Revocation..... | 12 |
+| 5 API Definitions .....                                                         | 13 |
+| 5.1 Naf_Authentication Service API.....                                         | 13 |
+| 5.1.1 Introduction .....                                                        | 13 |
+| 5.1.2 Usage of HTTP.....                                                        | 13 |
+| 5.1.2.1 General.....                                                            | 13 |
+| 5.1.2.2 HTTP standard headers.....                                              | 13 |
+| 5.1.2.2.1 General .....                                                         | 13 |
+| 5.1.2.2.2 Content type .....                                                    | 13 |
+| 5.1.2.3 HTTP custom headers.....                                                | 13 |
+| 5.1.3 Resources.....                                                            | 14 |
+| 5.1.4 Custom Operations without associated resources .....                      | 14 |
+| 5.1.4.1 Overview.....                                                           | 14 |
+| 5.1.4.2 Operation: request-auth.....                                            | 14 |
+| 5.1.4.2.1 Description .....                                                     | 14 |
+| 5.1.4.2.2 Operation Definition .....                                            | 14 |
+| 5.1.5 Notifications .....                                                       | 15 |
+| 5.1.5.1 General.....                                                            | 15 |
+| 5.1.5.2 UAV Notification .....                                                  | 16 |
+| 5.1.5.2.1 Description .....                                                     | 16 |
+| 5.1.5.2.2 Target URI.....                                                       | 16 |
+| 5.1.5.2.3 Standard Methods.....                                                 | 16 |
+| 5.1.5.2.3.1 POST .....                                                          | 16 |
+| 5.1.6 Data Model .....                                                          | 17 |
+| 5.1.6.1 General.....                                                            | 17 |
+| 5.1.6.2 Structured data types.....                                              | 17 |
+| 5.1.6.2.1 Introduction .....                                                    | 17 |
+| 5.1.6.2.2 Type: UAVAuthInfo .....                                               | 18 |
+| 5.1.6.2.3 Type: ReauthRevokeNotify.....                                         | 19 |
+| 5.1.6.2.4 Type: UAVAuthResponse.....                                            | 20 |
+| 5.1.6.2.5 Type: AdditionInfoAuthenticateAuthorize .....                         | 20 |
+
+|                                                        |                                                                                  |           |
+|--------------------------------------------------------|----------------------------------------------------------------------------------|-----------|
+| 5.1.6.2.6                                              | Type: AuthContainer.....                                                         | 21        |
+| 5.1.6.3                                                | Simple data types and enumerations.....                                          | 21        |
+| 5.1.6.3.1                                              | Introduction .....                                                               | 21        |
+| 5.1.6.3.2                                              | Simple data types .....                                                          | 21        |
+| 5.1.6.3.3                                              | Enumeration: AuthResult.....                                                     | 21        |
+| 5.1.6.3.4                                              | Enumeration: NotifyType .....                                                    | 21        |
+| 5.1.6.3.5                                              | Void.....                                                                        | 22        |
+| 5.1.6.3.6                                              | Enumeration: AuthMsgType.....                                                    | 22        |
+| 5.1.6.4                                                | Data types describing alternative data types or combinations of data types ..... | 22        |
+| 5.1.6.4.1                                              | Type: ProblemDetailsAuthenticateAuthorize .....                                  | 22        |
+| 5.1.7                                                  | Error Handling .....                                                             | 22        |
+| 5.1.7.1                                                | General.....                                                                     | 22        |
+| 5.1.7.2                                                | Protocol Errors .....                                                            | 22        |
+| 5.1.7.3                                                | Application Errors.....                                                          | 22        |
+| 5.1.8                                                  | Feature negotiation .....                                                        | 22        |
+| 5.1.9                                                  | Security.....                                                                    | 23        |
+| <b>Annex A (normative): OpenAPI specification.....</b> |                                                                                  | <b>24</b> |
+| A.1                                                    | General.....                                                                     | 24        |
+| A.2                                                    | Naf_Authentication API .....                                                     | 24        |
+| <b>Annex B (informative): Change history .....</b>     |                                                                                  | <b>29</b> |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# --- 1 Scope
+
+The present document specifies the stage 3 protocol and data model for the UAS-specific Naf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the UAS-specific AF.
+
+The 5G System stage 2 architecture and procedures are specified in TS 23.501 [2], TS 23.502 [3], and TS 23.256 [14].
+
+The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in TS 29.500 [4], and TS 29.122 [16].
+
+The UAS Service Supplier (USS) provides the UAS-specific AF services to NF service consumers (e.g. NEF (UAS-NF)). The USS is functionality within the AF.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
+- [3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
+- [4] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
+- [5] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
+- [6] OpenAPI: "OpenAPI Specification Version 3.0.0", <https://spec.openapis.org/oas/v3.0.0>.
+- [7] 3GPP TR 21.900: "Technical Specification Group working methods".
+- [8] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
+- [9] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
+- [10] 3GPP TS 29.510: "5G System; Network Function Repository Services; Stage 3".
+- [11] IETF RFC 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2)".
+- [12] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
+- [13] IETF RFC 7807: "Problem Details for HTTP APIs".
+- [14] 3GPP TS 23.256: "Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2".
+- [15] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
+- [16] 3GPP TS 29.122: "T8 reference point for Northbound APIs".
+
+# 3 Definitions of terms, symbols and abbreviations
+
+## 3.1 Terms
+
+For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. For the purposes of the present document, the terms and definitions given in TS 23.256 [14] shall apply.
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
+
+|        |                                         |
+|--------|-----------------------------------------|
+| AA     | Authorization/Authentication            |
+| AF     | Application Function                    |
+| NEF    | Network Exposure Function               |
+| UAS    | Uncrewed Aerial System                  |
+| UAS-NF | Uncrewed Aerial System Network Function |
+| UAV    | Uncrewed Aerial Vehicle                 |
+| USS    | UAS Service Supplier                    |
+| UUAA   | USS UAV Authorization/Authentication    |
+
+# 4 Services offered by the USS
+
+## 4.1 Introduction
+
+Table 4.1-1 summarizes the corresponding APIs defined for this specification.
+
+**Table 4.1-1: API Descriptions**
+
+| Service Name       | Clause | Description                                  | OpenAPI Specification File      | apiName  | Annex |
+|--------------------|--------|----------------------------------------------|---------------------------------|----------|-------|
+| Naf_Authentication | 5.1    | USS Authentication and Authorization Service | TS29255_Naf_Authentication.yaml | naf-auth | A.2   |
+
+## 4.2 Naf\_Authentication Service
+
+### 4.2.1 Service Description
+
+#### 4.2.1.1 Overview
+
+The Naf\_Authentication service as defined in TS 23.256 [14] is provided by the USS via the Naf service-based interface (see TS 23.256 [14]).
+
+This service:
+
+- allows NF consumers to authentication and authorization of the UAV with the USS; and
+- notifies NF consumers about reauthentication, reauthorization and revocation.
+
+#### 4.2.1.2 Service Architecture
+
+The Application Function Authentication Service (Naf\_Authentication) is part of the Naf service-based interface exhibited by the Application Function (AF) which owns the functionality of USS.
+
+The known NF service consumers of the Naf\_Authentication are the Network Exposure Function (NEF) which owns the functionality of UAS-NF.
+
+Figures 4.2.1.2-1 and 4.2.1.2-2 provide the reference model (in service-based interface representation and in reference point representation), with focus on the USS and the scope of the present specification.
+
+![Figure 4.2.1.2-1: Reference architecture for Naf_Authentication service: SBI representation. The diagram shows an Application Function (AF) box containing a USS box and a Naf circle. Below the AF box is a UAS-NF box, which is inside a larger NEF box. A vertical line labeled 'Naf_Authentication' connects the Naf circle to the UAS-NF box.](a234352dfaccdc24745c88eef7724cc6_img.jpg)
+
+Figure 4.2.1.2-1: Reference architecture for Naf\_Authentication service: SBI representation. The diagram shows an Application Function (AF) box containing a USS box and a Naf circle. Below the AF box is a UAS-NF box, which is inside a larger NEF box. A vertical line labeled 'Naf\_Authentication' connects the Naf circle to the UAS-NF box.
+
+**Figure 4.2.1.2-1: Reference architecture for Naf\_Authentication service: SBI representation**
+
+![Figure 4.2.1.2-2: Reference architecture for Naf_Authentication service: reference point representation. The diagram shows a NEF box containing a UAS-NF box on the left, connected by a horizontal line labeled 'N33' to a box on the right. The right box contains a USS box and an AF box.](99bae07626f60f9ede10e2e387ef7051_img.jpg)
+
+Figure 4.2.1.2-2: Reference architecture for Naf\_Authentication service: reference point representation. The diagram shows a NEF box containing a UAS-NF box on the left, connected by a horizontal line labeled 'N33' to a box on the right. The right box contains a USS box and an AF box.
+
+**Figure 4.2.1.2-2: Reference architecture for Naf\_Authentication service: reference point representation**
+
+The functionalities supported by the USS are listed in clause 4.3.2 of TS 23.256 [14].
+
+#### 4.2.1.3 Network Functions
+
+##### 4.2.1.3.1 Uncrewed Aerial System Service Supplier (USS)
+
+The UAS service supplier (USS) application provides authentication and authorization for the UAV.
+
+The UAS service supplier (USS) allows NF consumers to exchange communication messages needed for authentication and authorization procedure. It also notifies NF consumers about reauthentication, reauthorization or revocation of the UAV.
+
+##### 4.2.1.3.2 NF Service Consumers
+
+The Uncrewed Aerial System network function (UAS NF):
+
+- supports authentication and authorization of the UAV with the USS;
+- supports subscription for notification of reauthentication, reauthorization and revocation of the UAV from the USS.
+
+### 4.2.2 Service Operations
+
+#### 4.2.2.1 Introduction
+
+#### 4.2.2.2 Naf\_Authentication\_AuthenticateAuthorize Service operation
+
+##### 4.2.2.2.1 General
+
+The Naf\_Authentication\_AuthenticateAuthorize service operation is used by the NF consumers during following procedure:
+
+- UUAA-MM and UUAA-SM procedures (see TS 23.256 [14], clause 5.2.2 and clause 5.2.3, respectively)
+- C2 authorization (see TS 23.256 [14], clause 5.2.5.2 and clause 5.4.3)
+
+##### 4.2.2.2.2 Authentication and Authorization of the UAV
+
+The Naf\_Authentication\_AuthenticateAuthorize service operation is invoked by an NF Service Consumer (e.g. an NEF (UAS-NF)) towards the USS, when UUAA-MM is done during 5GS registration, UUAA-SM is done during PDU session establishment, or for authorization for C2 communication over Uu interface or Direct C2 communication over PC5 interface (see TS 23.256 [14]).
+
+The NF Service Consumer (e.g. the NEF (UAS-NF)) shall send the authentication message to USS by sending the HTTP POST request towards the "request-auth" resource as shown in Figure 4.2.2.2.2-1.
+
+![Sequence diagram showing the AuthenticateAuthorize Service Operation between an NF Service Consumer and a USS. The NF Service Consumer sends a POST request to the USS. The USS responds with either a 200 OK or a 4xx/5xx or 3xx status code.](fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg)
+
+```
+
+sequenceDiagram
+    participant NF Service Consumer
+    participant USS
+    Note left of NF Service Consumer: 
+    NF Service Consumer->>USS: 1. POST.../request-auth
+    Note right of USS: 
+    USS-->>NF Service Consumer: 2a. 200 OK
+    Note right of USS: 
+    USS-->>NF Service Consumer: 2b. 4xx/5xx or 3xx
+  
+```
+
+Sequence diagram showing the AuthenticateAuthorize Service Operation between an NF Service Consumer and a USS. The NF Service Consumer sends a POST request to the USS. The USS responds with either a 200 OK or a 4xx/5xx or 3xx status code.
+
+**Figure 4.2.2.2.2-1: AuthenticateAuthorize Service Operation**
+
+1. The NF Service Consumer shall send a POST request to the resource with a UAVAuthInfo object in the request body. The UAVAuthInfo data type shall include:
+
+- "gpsi" attribute that carries the GPSI (in the format of External Identifier) of the UAV;
+- "serviceLevelId" attribute that carries the Service Level Device Identity of the UAV;
+
+The UAVAuthInfo data type may include
+
+- "uavLocInfo" attribute that provides the UAV location;
+- "notifyUri" attribute that provides the notification URI to receive notifications related to reauthentication, reauthorization or revocation triggered by the USS, which shall be present in the initial request;
+- "notifyCorrId" attribute that represents the notification correlation ID and this attribute shall be present when the "notifyUri" attribute is provided;
+- "authMsg" attribute that contains the authentication message based on the authentication method used, which is present in the intermediate round-trip messages and not in initial request. This attribute is deprecated; the attribute "authContainer" should be used instead.
+
+- "AuthContainer" data type that contains the AA related data provided by the UE (see TS 23.256 [14]). This attribute deprecates "authMsg" attribute and may contain:
+- "authMsgType" attribute that indicates the type of the AA message payload;
+- "authMsgPayload" attribute that carries the AA message payload;
+
+NOTE 1: The "authResult" attribute will not be present within the AuthContainer data type, when included within the request sent to USS.
+
+In case of UUAA-SM procedure, the UAVAuthInfo data type may also include:
+
+- "ipAddr" attribute that carries the IP Address associated with the PDU session; and
+- "pei" attribute that carries the PEI of the UAV.
+
+- 2a. If the HTTP request message from the NF service consumer is accepted, the USS shall respond with "200 OK" status code with the message body containing the UAVAuthResponse data type in the response body, which shall include "gpsi" attribute.
+
+If the USS triggers more intermediate round-trip messages, the UAVAuthResponse data shall include a "authMsg" attribute that contains the authentication message or authorization data.
+
+Otherwise, the UAVAuthResponse data type shall contain the "authResult" attribute. If the UAV is authenticated successfully, the USS shall set the "authResult" attribute to "AUTH\_SUCCESS". The "authMsg" and "authResult" attributes are deprecated; the "authContainer" attribute should be used instead. The UAVAuthResponse data type shall include the "authContainer" data type that may include:
+
+- AA message payload type within "authMsgType" attribute;
+- AA message payload containing the configuration information within "authMsgPayload" attribute;
+- AA result within "authResult" attribute, which is set to either "AUTH\_SUCCESS" in case of successful AA procedure or to "AUTH\_FAIL" in case of failed AA procedure in the final response of the AA procedure.
+
+NOTE 2: The absence of "authResult" attribute within "AuthContainer" data type indicates that the AA procedure is ongoing.
+
+- The "serviceLevelId" attribute containing a new Service Level Device Identity as the authorized Service Level Device Identity to the UAV.
+
+The UAVAuthResponse data type may also include:
+
+- the DN authorization profile index within the "authProfIndex" attribute;
+- the DN authorized Session-AMBR within the "authSessAmbr" attribute.
+
+- 2b. If the USS cannot successfully fulfil the received HTTP POST request due to an internal error or an error in the HTTP POST request, the USS shall send the HTTP error response as specified in clause 5.1.7.
+
+If the UAV authentication is failed, the USS shall reject the request with an HTTP "403 Forbidden" response message including the "cause" attribute of the ProblemDetailsAuthenticateAuthorize data structure set to "FAILED\_AUTH". The USS shall also include an indication of "uasResRelInd" attribute in the ProblemDetailsAuthenticateAuthorize data type to indicate if an UAS service related network resource can be released or not, during re-authentication failure, when the service operation is used during Re-authentication procedure.
+
+If the USS determines the received HTTP POST request needs to be redirected, the USS shall send an HTTP redirect response as specified in clause 5.2.10 of TS 29.122 [16].
+
+#### 4.2.2.3 Naf\_Authentication\_Notification Service operation
+
+##### 4.2.2.3.1 General
+
+The Naf\_Authentication\_Notification service operation is used by the NF consumers during the following procedure:
+
+- USS Initiated Re-authentication and Re-authorization (see TS 23.256 [14], clause 5.2.4)
+- USS Initiated Revocation (see TS 23.256 [14], clause 5.2.7)
+
+##### 4.2.2.3.2 Notification for Reauthentication, Reauthorization or Revocation
+
+The Naf\_Authentication\_Notification service operation is invoked by the USS to inform a NF Service Consumer (e.g. NEF (UAS-NF)), when USS triggers reauthentication, update authorization data or revoke authorization of the UAV.
+
+The USS shall send the request by sending the HTTP POST method towards the Notification URI as shown in Figure 4.2.2.3.2-1.
+
+![Sequence diagram showing the UAV Notification Service Operation between an NF Service Consumer and a USS. The USS sends a POST {notifyUri} request to the NF Service Consumer. The NF Service Consumer responds with either 2a. 204 No Content or 2b. 4xx/5xx or 3xx.](853f59c89931a666c07903b31d098277_img.jpg)
+
+```
+
+sequenceDiagram
+    participant NF Service Consumer
+    participant USS
+    Note left of NF Service Consumer: 
+    USS->>NF Service Consumer: 1. POST {notifyUri}
+    NF Service Consumer-->>USS: 2a. 204 No Content
+    NF Service Consumer-->>USS: 2b. 4xx/5xx or 3xx
+  
+```
+
+Sequence diagram showing the UAV Notification Service Operation between an NF Service Consumer and a USS. The USS sends a POST {notifyUri} request to the NF Service Consumer. The NF Service Consumer responds with either 2a. 204 No Content or 2b. 4xx/5xx or 3xx.
+
+Figure 4.2.2.3.2-1: UAV Notification Service Operation
+
+1. The USS shall send a POST request towards the Notification URI received in the Authenticate service operation request (See clause 4.2.2.1). The request body shall contain a ReauthRevokeNotify object containing the reauthentication information, update authorization information or revoke authorization indication. The ReauthRevokeNotify data type shall include:
+  - the "gpsi" attribute is set to the GPSI (in the format of External Identifier) of the given UAV required to be reauthenticated, reauthorized or revoked;
+  - the "serviceLevelId" attribute is set to the Service Level Device Identity of the UAV;
+  - the "notifyCorrId" attribute is set to the same value as the "notifyCorrId" attribute of UAVAuthInfo data type received in the request;
+  - the "notifyType" attribute is set to REAUTHENTICATE for reauthentication or set to REAUTHORIZE for authorization data update or set to REVOKE for revocation of authorization. In addition, if "notifyType" attribute is set to REAUTHORIZE, then attribute "authMsg" containing the authorization data shall be included. "authMsg" attribute is deprecated; the "authContainer" attribute should be used instead, which carries the authorization data.
+
+NOTE: The "authResult" attribute will not be present within the AuthContainer data type, when included within the Notification request sent by the USS.
+
+The ReauthRevokeNotify may also include:
+
+- the "ipAddr" attribute carries the IP Address associated with the PDU session;
+- 2a. On success, "204 No content" shall be returned without response body. If the "notifyType" attribute in the request indicated REVOKE, then UAS service related network resources are released.
+  - 2b. If the NF service consumer cannot successfully fulfil the received HTTP POST request due to an internal error or an error in the HTTP POST request, the NF service consumer shall send an HTTP error response as specified in clause 5.1.7.
+
+If the NF service consumer determines the received HTTP POST request needs to be redirected, the NF service consumer shall send an HTTP redirect response as specified in clause 5.2.10 of TS 29.122 [16].
+
+# 5 API Definitions
+
+## 5.1 Naf\_Authentication Service API
+
+### 5.1.1 Introduction
+
+The Naf\_Authentication shall use the Naf\_Authentication API.
+
+The API URI of the Naf\_Authentication 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 5.2.4 of TS 29.122 [16], i.e.:
+
+**{apiRoot}/<apiName>/<apiVersion>/<apiSpecificSuffixes>**
+
+with the following components:
+
+- The {apiRoot} shall be set as described in clause 5.2.4 in 3GPP TS 29.122 [16].
+- The <apiName> shall be "naf-auth".
+- The <apiVersion> shall be "v1".
+- The <apiSpecificSuffixes> 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 of TS 29.122 [16].
+
+HTTP/2 shall be transported as specified in TS 29.122 [16].
+
+The OpenAPI [6] specification of HTTP messages and content bodies for the Naf\_Authentication API is contained in Annex A.
+
+#### 5.1.2.2 HTTP standard headers
+
+##### 5.1.2.2.1 General
+
+See TS 29.122 [16] 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 TS 29.122 [16]. 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].
+
+NOTE: This release only supports the content type JSON.
+
+#### 5.1.2.3 HTTP custom headers
+
+The mandatory HTTP custom header fields specified in clause 5.2.3.2 of TS 29.500 [4] shall be supported, and the optional HTTP custom header fields specified in clause 5.2.3.3 of TS 29.500 [4] may be supported.
+
+### 5.1.3 Resources
+
+None
+
+### 5.1.4 Custom Operations without associated resources
+
+#### 5.1.4.1 Overview
+
+The structure of the custom operation URIs of the Naf\_Authentication service is shown in Figure 5.1.4.1-1.
+
+![Diagram showing the URI structure {apiRoot}/naf-auth/v1 with a callout pointing to /request-auth.](f6e8acf9f931452d01688d311b5c0364_img.jpg)
+
+The diagram shows the URI structure `{apiRoot}/naf-auth/v1`. A line extends from the bottom of the URI to a dashed rectangular box containing the text `/request-auth`, indicating that this path is appended to the base URI for the custom operation.
+
+Diagram showing the URI structure {apiRoot}/naf-auth/v1 with a callout pointing to /request-auth.
+
+**Figure 5.1.4.1-1: Custom operation URI structure of the Naf\_Authentication API**
+
+Table 5.1.4.1-1 provides an overview of the custom operations and applicable HTTP methods.
+
+**Table 5.1.4.1-1: Custom operations without associated resources**
+
+| Custom operation URI                                            | Mapped HTTP method | Description                                                                                      |
+|-----------------------------------------------------------------|--------------------|--------------------------------------------------------------------------------------------------|
+| <code>{apiRoot}/naf-auth/&lt;apiVersion&gt;/request-auth</code> | POST               | Request UAV authentication and authorization and subscribe to notifications triggered by the USS |
+
+#### 5.1.4.2 Operation: request-auth
+
+##### 5.1.4.2.1 Description
+
+The operation is used by the NF service consumer to request UAV authentication and authorization and subscribe to notifications triggered by the USS.
+
+##### 5.1.4.2.2 Operation Definition
+
+This operation shall support the response data structures and response codes specified in tables 5.1.4.2.2-1 and 5.1.4.2.2-2.
+
+**Table 5.1.4.2.2-1: Data structures supported by the POST Request Body on this resource**
+
+| Data type   | P | Cardinality | Description                                                             |
+|-------------|---|-------------|-------------------------------------------------------------------------|
+| UAVAuthInfo | M | 1           | Represents the data to be used for UAV authentication and authorization |
+
+**Table 5.1.4.2.2-2: Data structures supported by the POST Response Body on this resource**
+
+| Data type                           | P | Cardinality | Response codes         | Description                                                                                                                                                                                                                                                              |
+|-------------------------------------|---|-------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| UAVAuthResponse                     | M | 1           | 200 OK                 | Successful request of UAV authentication and authorization and subscription to notification of re-authentication and revocation triggered by the USS. If C2 authorization request is sent during UUAA-SM, the final response indicates that at least UUAA has succeeded. |
+| N/A                                 |   |             | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing a different URI. The URI shall be an alternative URI of the resource located on an alternative AF.                                                                                  |
+| N/A                                 |   |             | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing a different URI. The URI shall be an alternative URI of the resource located on an alternative AF.                                                                                  |
+| ProblemDetailsAuthenticateAuthorize | O | 0..1        | 403 Forbidden          | (NOTE 2)                                                                                                                                                                                                                                                                 |
+
+NOTE 1: The mandatory HTTP error status code for the POST method listed in Table 5.2.6-1 of TS 29.122 [16] also apply.
+
+NOTE 2: Failure cases are described in clause 5.1.7.3.
+
+**Table 5.1.4.2.2-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 AF. |
+
+**Table 5.1.4.2.2-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 AF. |
+
+### 5.1.5 Notifications
+
+#### 5.1.5.1 General
+
+This clause specifies the notifications provided by the Naf\_Authentication service.
+
+Notifications shall comply to clause 5.2.5 of 3GPP TS 29.122 [16].
+
+**Table 5.1.5.1-1: Notifications overview**
+
+| Notification     | Callback URI | HTTP method or custom operation | Description (service operation)                              |
+|------------------|--------------|---------------------------------|--------------------------------------------------------------|
+| UAV Notification | {notifyUri}  | notify (POST)                   | Reauthentication, Reauthorization or Revocation notification |
+
+#### 5.1.5.2 UAV Notification
+
+##### 5.1.5.2.1 Description
+
+The UAV Notification is used by the USS to trigger reauthentication, reauthorization or revocation notification to a NF service consumer that has subscribed to such notifications. The USS shall notify the NF Service Consumer when reauthentication is required.
+
+##### 5.1.5.2.2 Target URI
+
+The Callback URI "{notifyUri}" 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                                    |
+|-----------|-----------------------------------------------|
+| notifyUri | String formatted as URI with the Callback Uri |
+
+##### 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                                                               |
+|--------------------|---|-------------|---------------------------------------------------------------------------|
+| ReauthRevokeNotify | M | 1           | Contains the reauthentication, reauthorization or revocation information. |
+
+**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         | Successful notification of reauthentication or reauthorization or revocation.                                                                                                            |
+| N/A       |   |             | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing a different URI. The URI shall be an alternative URI of the resource located on an alternative NEF. |
+| N/A       |   |             | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing a different URI. The URI shall be an alternative URI of the resource located on an alternative NEF. |
+
+NOTE: The mandatory HTTP error status codes for the POST method listed in Table 5.2.6-1 of TS 29.122 [16] 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 NEF. |
+
+**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 NEF. |
+
+### 5.1.6 Data Model
+
+#### 5.1.6.1 General
+
+This clause specifies the application data model supported by the Naf\_Authentication API.
+
+Table 5.1.6.1-1 specifies the data types defined for the Naf\_Authentication service based interface protocol.
+
+**Table 5.1.6.1-1: Naf\_Authentication specific Data Types**
+
+| Data type                           | Clause defined | Description                                                                                            | Applicability |
+|-------------------------------------|----------------|--------------------------------------------------------------------------------------------------------|---------------|
+| UAVAuthInfo                         | 5.1.6.2.2      | Information within Authenticate Request                                                                |               |
+| UAVAuthResponse                     | 5.1.6.2.4      | Information within Authenticate Response                                                               |               |
+| AuthResult                          | 5.1.6.3.3      | Enumeration indicating authentication result                                                           |               |
+| ReauthRevokeNotify                  | 5.1.6.2.3      | Information within notification                                                                        |               |
+| NotifyType                          | 5.1.6.3.4      | Enumeration Notification type                                                                          |               |
+| ProblemDetailsAuthenticateAuthorize | 5.1.6.4.1      | Data type that extends ProblemDetails.                                                                 |               |
+| AdditionInfoAuthenticateAuthorize   | 5.1.6.2.5      | Contains more details (not only the ProblemDetails) in case an UAV authentication request is rejected. |               |
+| AuthContainer                       | 5.1.6.2.6      | Carries the AA related data                                                                            |               |
+
+Table 5.1.6.1-2 specifies data types re-used by the Naf\_Authentication 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 Naf\_Authentication service based interface.
+
+**Table 5.1.6.1-2: Naf\_Authentication re-used Data Types**
+
+| Data type         | Reference      | Comments                                                                               | Applicability |
+|-------------------|----------------|----------------------------------------------------------------------------------------|---------------|
+| BitRate           | TS 29.571 [15] | Bit Rate                                                                               |               |
+| Pei               | TS 29.571 [15] | Permanent Equipment Identifier                                                         |               |
+| Uri               | TS 29.571 [15] | Uri                                                                                    |               |
+| Gpsi              | TS 29.571 [15] | GPSI                                                                                   |               |
+| IpAddr            | TS 29.571 [15] | IP address                                                                             |               |
+| LocationArea5G    | TS 29.122 [16] | User location                                                                          |               |
+| ProblemDetails    | TS 29.122 [16] | Represents additional information and details on an error response.                    |               |
+| SupportedFeatures | TS 29.571 [15] | Used to negotiate the applicability of the optional features defined in table 5.1.8-1. |               |
+| RefToBinaryData   | TS 29.571 [15] | AA message payload data                                                                |               |
+
+#### 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: UAVAuthInfo
+
+Table 5.1.6.2.2-1: Definition of type UAVAuthInfo
+
+| Attribute name | Data type            | P | Cardinality | Description                                                                                                                                                                                                                                                                       | Applicability |
+|----------------|----------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| gpsi           | Gpsi                 | M | 1           | GPSI of the UAV                                                                                                                                                                                                                                                                   |               |
+| serviceLevelId | string               | M | 1           | Service Level Device Identity of the UAV                                                                                                                                                                                                                                          |               |
+| ipAddr         | IpAddr               | O | 0..1        | When present, this attribute indicates the IP address associated with the PDU session.                                                                                                                                                                                            |               |
+| authMsg        | string               | O | 0..1        | Contains the authentication message or authorization data (which is not present in the initial request) used in the subsequent request messages during multiple round trip message exchanges. This attribute is deprecated; the attribute "authContainer" should be used instead. |               |
+| authContainer  | array(AuthContainer) | O | 1..N        | Contains the AA related data without the "authResult" attribute. This attribute deprecates "authMsg" attribute.                                                                                                                                                                   |               |
+| pei            | Pei                  | O | 0..1        | PEI associated with the UAV.                                                                                                                                                                                                                                                      |               |
+| notifyUri      | Uri                  | C | 0..1        | This attribute shall be present in the initial authentication message.<br><br>It carries the notification URI to receive reauthentication, reauthorization or revocation related notifications                                                                                    |               |
+| notifyCorrId   | string               | C | 0..1        | Notification correlation ID assigned by the NF service consumer. Shall be present when the "notifyUri" attribute is provided.                                                                                                                                                     |               |
+| uavLocInfo     | LocationArea5G       | O | 0..1        | This attribute shall contain the UE location information if it is available.                                                                                                                                                                                                      |               |
+| suppFeat       | SupportedFeatures    | C | 0..1        | This IE shall be present during the initial authentication and authorization request if at least one optional feature defined in clause 5.1.8 is supported.                                                                                                                       |               |
+
+##### 5.1.6.2.3 Type: ReauthRevokeNotify
+
+Table 5.1.6.2.3-1: Definition of type ReauthRevokeNotify
+
+| Attribute name | Data type            | P | Cardinality | Description                                                                                                                                                                                                                                                       | Applicability |
+|----------------|----------------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| gpsi           | Gpsi                 | M | 1           | GPSI of the UAV                                                                                                                                                                                                                                                   |               |
+| serviceLevelId | string               | M | 1           | Service Level Device Identity of the UAV                                                                                                                                                                                                                          |               |
+| authMsg        | string               | C | 0..1        | Contains the authentication message or authorization data.<br>This attribute shall be present when "notifyType" attribute is set to REAUTHORIZE. This attribute is deprecated; the attribute "authContainer" should be used instead.                              |               |
+| authContainer  | array(AuthContainer) | C | 1..N        | Contains the AA related data. This attribute shall be present when "notifyType" attribute is set to REAUTHORIZE. This attribute deprecates "authMsg" attribute.                                                                                                   |               |
+| ipAddr         | IpAddr               | O | 0..1        | When present, this IE indicates the IP address associated with the PDU session.                                                                                                                                                                                   |               |
+| notifyCorrId   | string               | C | 0..1        | Notification correlation ID used to identify the request to which the notification relates.<br>It shall be present if the "notifyCorrId" attribute is provided in the request and set to the same value as the "notifyCorrId" attribute of UAVAuthInfo data type. |               |
+| notifyType     | NotifyType           | M | 1           | This attribute shall contain the notification type.                                                                                                                                                                                                               |               |
+
+##### 5.1.6.2.4 Type: UAVAuthResponse
+
+Table 5.1.6.2.4-1: Definition of type UAVAuthResponse
+
+| Attribute name | Data type            | P | Cardinality | Description                                                                                                                                                                                                              | Applicability |
+|----------------|----------------------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| gpsi           | Gpsi                 | C | 0..1        | GPSI of the UAV.<br>Shall be present except during PDU Session Modification for C2 Communication procedure.                                                                                                              |               |
+| authResult     | AuthResult           | C | 0..1        | Conveys the UAV authentication result (success) .<br>Shall be present if there is no intermediate round-trip messages. This attribute is deprecated; the attribute "authContainer" should be used instead.               |               |
+| authMsg        | string               | C | 0..1        | Contains the authentication message or authorization data.<br>Shall be present if the USS triggers intermediate round-trip messages. This attribute is deprecated; the attribute "authContainer" should be used instead. |               |
+| authContainer  | array(AuthContainer) | C | 1..N        | Contains the AA related data.                                                                                                                                                                                            |               |
+| serviceLevelId | string               | O | 0..1        | Contains a new Service Level Device Identity of the UAV                                                                                                                                                                  |               |
+| authSessAmbr   | BitRate              | O | 0..1        | The DN Authorized Session-AMBR.                                                                                                                                                                                          |               |
+| authProfIndex  | string               | O | 0..1        | DN authorization profile index.                                                                                                                                                                                          |               |
+| suppFeat       | SupportedFeatures    | C | 0..1        | This IE shall be present during the initial authentication and authorization response if at least one optional feature defined in clause 5.1.8 is supported.                                                             |               |
+
+##### 5.1.6.2.5 Type: AdditionInfoAuthenticateAuthorize
+
+Table 5.1.6.2.5-1: Definition of type AdditionInfoAuthenticateAuthorize
+
+| Attribute name | Data type | P | Cardinality | Description                                                                                                                                                                                                                                                                                                                                                                                                   | Applicability |
+|----------------|-----------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| uasResRelInd   | boolean   | C | 0..1        | This attribute is used to indicate if an UAS service related network resource can be released or not, during re-authentication failure.<br>It shall be included if the "cause" attribute within the ProblemDetails data type is set to "FAILED_AUTH".<br>When present, it shall be set as follows:<br>- true: UAS resource release is requested;<br>- false (default): UAS resource release is not requested. |               |
+
+##### 5.1.6.2.6 Type: AuthContainer
+
+Table 5.1.6.2.6-1: Definition of type AuthContainer
+
+| Attribute name | Data type       | P | Cardinality | Description                                                                                                  | Applicability |
+|----------------|-----------------|---|-------------|--------------------------------------------------------------------------------------------------------------|---------------|
+| authMsgType    | AuthMsgType     | C | 0..1        | Type of AA message.<br>Shall be present if more than one AuthContainer's are carried in the UAVAuthResponse. |               |
+| authMsgPayload | RefToBinaryData | O | 0..1        | AA message payload data.                                                                                     |               |
+| authResult     | AuthResult      | C | 0..1        | Shall be present for the final AA response conveying the AA result.                                          |               |
+
+#### 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 |
+|-----------|-----------------|-------------|---------------|
+|           |                 |             |               |
+
+##### 5.1.6.3.3 Enumeration: AuthResult
+
+The enumeration AuthResult represents the result of authentication and/or authorization. It shall comply with the provisions defined in table 5.1.6.3.3-1.
+
+Table 5.1.6.3.3-1: Enumeration AuthResult
+
+| Enumeration value | Description                                 | Applicability |
+|-------------------|---------------------------------------------|---------------|
+| AUTH_SUCCESS      | The UUAA or C2 authorization has succeeded. |               |
+| AUTH_FAIL         | The UUAA or C2 authorization has failed.    |               |
+
+##### 5.1.6.3.4 Enumeration: NotifyType
+
+The enumeration NotifyType represents the type of notification. It shall comply with the provisions defined in table 5.1.6.3.4-1.
+
+Table 5.1.6.3.4-1: Enumeration NotifyType
+
+| Enumeration value | Description                                    | Applicability |
+|-------------------|------------------------------------------------|---------------|
+| REAUTHENTICATE    | The UAV needs to be reauthenticated.           |               |
+| REAUTHORIZE       | Authorization data needs to be updated to UAV. |               |
+| REVOKE            | Revoke UAV authentication and authorization    |               |
+
+##### 5.1.6.3.5 Void
+
+##### 5.1.6.3.6 Enumeration: AuthMsgType
+
+The enumeration AuthMsgType represents the type of AA message. It shall comply with the provisions defined in table 5.1.6.3.6-1.
+
+**Table 5.1.6.3.6-1: Enumeration AuthMsgType**
+
+| Enumeration value | Description               | Applicability |
+|-------------------|---------------------------|---------------|
+| UUAA              | UUAA payload.             |               |
+| C2AUTH            | C2 authorization payload. |               |
+
+#### 5.1.6.4 Data types describing alternative data types or combinations of data types
+
+##### 5.1.6.4.1 Type: ProblemDetailsAuthenticateAuthorize
+
+**Table 5.1.6.4.1-1: Definition of type ProblemDetailsAuthenticateAuthorize as a list of to be combined data types**
+
+| Data type                           | Cardinality | Description                                                                                                                             | Applicability |
+|-------------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| ProblemDetails                      | 1           | Details of the problem as defined in TS 29.122 [16].                                                                                    |               |
+| AdditionalInfoAuthenticateAuthorize | 1           | Contains additional information to indicate the handling of the UAS service related network resource, during re-authentication failure. |               |
+
+### 5.1.7 Error Handling
+
+#### 5.1.7.1 General
+
+Response bodies for error handling, as described in 3GPP TS 29.122 [16], are applicable to the APIs in the present specification unless specified otherwise, with the following clarifications:
+
+- the SCEF is the AF; and
+- the SCS/AS is the NEF invoking an API.
+
+In addition, the requirements in the following clauses are applicable for the Naf\_Authentication API.
+
+#### 5.1.7.2 Protocol Errors
+
+No specific procedures for the Naf\_Authentication service are specified.
+
+#### 5.1.7.3 Application Errors
+
+The application errors defined for the Naf\_Authentication service are listed in Table 5.1.7.3-1.
+
+**Table 5.1.7.3-1: Application errors**
+
+| Application Error | HTTP status code | Description                                                                       |
+|-------------------|------------------|-----------------------------------------------------------------------------------|
+| FAILED_AUTH       | 403 Forbidden    | The HTTP request is rejected because the UAV authentication is failed by the USS. |
+
+### 5.1.8 Feature negotiation
+
+The optional features in table 5.1.8-1 are defined for the Naf\_Authentication API. They shall be negotiated using the extensibility mechanism defined in clause 6.6 of TS 29.122 [16].
+
+**Table 5.1.8-1: Supported Features**
+
+| Feature number | Feature Name | Description |
+|----------------|--------------|-------------|
+|                |              |             |
+
+### 5.1.9 Security
+
+TLS shall be used to support the security communication between the NEF and the AF over N33 interface. The access to the Naf\_Authentication API shall be authorized by means of OAuth2 protocol (see IETF RFC 6749 [9]), based on local configuration, using the "Client Credentials" authorization grant. If OAuth2 is used, a client, prior to consuming services offered by the Naf\_Authentication API, shall obtain a "token" from the authorization server.
+
+# Annex A (normative): OpenAPI specification
+
+## A.1 General
+
+This Annex specifies the formal definition of the API(s) defined in the present specification. It consists of OpenAPI specifications in YAML format.
+
+This Annex takes precedence when being discrepant to other parts of the specification with respect to the encoding of information elements and methods within the API(s).
+
+NOTE: The semantics and procedures, as well as conditions, e.g. for the applicability and allowed combinations of attributes or values, not expressed in the OpenAPI definitions but defined in other parts of the specification also apply.
+
+Informative copies of the OpenAPI specification files contained in this 3GPP Technical Specification are available on a Git-based repository that uses the GitLab software version control system (see TS 29.501 [5] clause 5.3.1 and TR 21.900 [7] clause 5B).
+
+## A.2 Naf\_Authentication API
+
+```
+openapi: 3.0.0
+
+info:
+  title: Naf_Authentication
+  version: 1.1.0-alpha.1
+  description: |
+    AF Authentication Service.
+    © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+    All rights reserved.
+
+externalDocs:
+  description: >
+    3GPP TS 29.255 V18.0.0; 5G System;Uncrewed Aerial System Service Supplier (USS) Services; Stage
+    3.
+  url: https://www.3gpp.org/ftp/Specs/archive/29_series/29.255/
+
+servers:
+  - url: '{apiRoot}/naf-auth/v1'
+    variables:
+      apiRoot:
+        default: https://example.com
+        description: apiRoot as defined in clause 5.2.4 of 3GPP TS 29.122
+
+security:
+  - {}
+  - oAuth2ClientCredentials: []
+
+paths:
+  /request-auth:
+    post:
+      operationId: UAVAuthRequest
+      summary: UAV authentication
+      tags:
+        - UAV authentication
+      requestBody:
+        description: UAV authentication
+        required: true
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/UAVAuthInfo'
+      responses:
+        '200':
+          description: UAV Auth response or message exchange
+          content:
+```
+
+```
+    application/json:
+      schema:
+        $ref: '#/components/schemas/UAVAuthResponse'
+  '307':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/307'
+  '308':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/308'
+  '400':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/400'
+  '401':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/401'
+  '403':
+    description: >
+      The request is rejected by the USS and more details (not only the ProblemDetails) are
+      returned.
+    content:
+      application/problem+json:
+        schema:
+          $ref: '#/components/schemas/ProblemDetailsAuthenticateAuthorize'
+  '404':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/404'
+  '411':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/411'
+  '413':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/413'
+  '415':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/415'
+  '429':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/429'
+  '500':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/500'
+  '503':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/503'
+  default:
+    $ref: 'TS29122_CommonData.yaml#/components/responses/default'
+callbacks:
+  reauthRevokeNotification:
+    '{request.body#/notifyUri}':
+      post:
+        requestBody:
+          required: true
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ReauthRevokeNotify'
+responses:
+  '204':
+    description: Successful Notification response
+  '307':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/307'
+  '308':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/308'
+  '400':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/400'
+  '401':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/401'
+  '403':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/403'
+  '404':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/404'
+  '411':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/411'
+  '413':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/413'
+  '415':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/415'
+  '429':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/429'
+  '500':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/500'
+  '503':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/503'
+  default:
+    $ref: 'TS29122_CommonData.yaml#/components/responses/default'
+
+components:
+
+securitySchemes:
+```
+
+```
+oAuth2ClientCredentials:
+  type: oauth2
+  flows:
+    clientCredentials:
+      tokenUrl: '{tokenUrl}'
+      scopes: {}
+
+schemas:
+
+#
+# STRUCTURED DATA TYPES
+#
+
+UAVAuthInfo:
+  description: UAV auth data
+  type: object
+  required:
+    - gpsi
+    - serviceLevelId
+  properties:
+    gpsi:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi'
+    serviceLevelId:
+      type: string
+    notifyUri:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
+    notifyCorrId:
+      type: string
+    ipAddr:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/IpAddr'
+    pei:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Pei'
+    authMsg:
+      type: string
+      deprecated: true
+    authContainer:
+      type: array
+      items:
+        $ref: '#/components/schemas/AuthContainer'
+      minItems: 1
+    uavLocInfo:
+      $ref: 'TS29122_CommonData.yaml#/components/schemas/LocationArea5G'
+    suppFeat:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures'
+
+UAVAuthResponse:
+  description: UAV auth response data
+  type: object
+  properties:
+    gpsi:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi'
+    authContainer:
+      type: array
+      items:
+        $ref: '#/components/schemas/AuthContainer'
+      minItems: 1
+    authMsg:
+      type: string
+      deprecated: true
+    authResult:
+      allOf:
+        - $ref: '#/components/schemas/AuthResult'
+        deprecated: true
+    serviceLevelId:
+      type: string
+    authSessAmbr:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRate'
+    authProfIndex:
+      type: string
+    suppFeat:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures'
+
+ReauthRevokeNotify:
+  description: UAV related notification
+  type: object
+```
+
+```
+required:
+  - gpsi
+  - serviceLevelId
+  - notifyType
+properties:
+  gpsi:
+    $ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi'
+  serviceLevelId:
+    type: string
+  notifyCorrId:
+    type: string
+  authContainer:
+    type: array
+    items:
+      $ref: '#/components/schemas/AuthContainer'
+    minItems: 1
+  authMsg:
+    type: string
+    deprecated: true
+  notifyType:
+    $ref: '#/components/schemas/NotifyType'
+  ipAddr:
+    $ref: 'TS29571_CommonData.yaml#/components/schemas/IpAddr'
+
+AuthContainer:
+  description: Authentication/Authorization data
+  type: object
+  properties:
+    authMsgType:
+      $ref: '#/components/schemas/AuthMsgType'
+    authMsgPayload:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/RefToBinaryData'
+    authResult:
+      $ref: '#/components/schemas/AuthResult'
+
+ProblemDetailsAuthenticateAuthorize:
+  description: Extends ProblemDetails to indicate more details during Authentication failure
+  allOf:
+    - $ref: 'TS29122_CommonData.yaml#/components/schemas/ProblemDetails'
+    - $ref: '#/components/schemas/AdditionInfoAuthenticateAuthorize'
+
+AdditionInfoAuthenticateAuthorize:
+  description: Indicates additional information during authentication failure
+  type: object
+  properties:
+    uasResRelInd:
+      type: boolean
+      description: >
+        Indicates to release the UAV resources during authentication failure, when set to
+        "true". Default is set to "false".
+```
+
+#
+
+# SIMPLE DATA TYPES
+
+#
+
+#
+
+# ENUMERATIONS
+
+#
+
+```
+AuthResult:
+  anyOf:
+    - type: string
+      enum:
+        - AUTH_SUCCESS
+        - AUTH_FAIL
+    - type: string
+      description: >
+        This string provides forward-compatibility with future extensions to the enumeration but
+        is not used to encode content defined in the present version of this API.
+  description: |
+    Represents the result of authentication and/or authorization.
+    Possible values are:
+    - AUTH_SUCCESS: The UUAA or C2 authorization has succeeded.
+    - AUTH_FAIL: The UUAA or C2 authorization has failed.
+```
+
+```
+NotifyType:
+  anyOf:
+    - type: string
+      enum:
+```
+
+- REAUTHENTICATE
+- REAUTHORIZE
+- REVOKE
+- type: string  
+description: >  
+This string provides forward-compatibility with future extensions to the enumeration but is not used to encode content defined in the present version of this API.
+
+description: |  
+Represents the type of notification.  
+Possible values are:
+
+- REAUTHENTICATE: The UAV needs to be reauthenticated.
+- REAUTHORIZE: Authorization data needs to be updated to UAV.
+- REVOKE: Revoke UAV authentication and authorization.
+
+AuthMsgType:  
+anyOf:
+
+- type: string  
+enum:  
+- UUAA  
+- C2AUTH
+- type: string  
+description: >  
+This string provides forward-compatibility with future extensions to the enumeration but is not used to encode content defined in the present version of this API.
+
+description: |  
+Represents the type of AA message.  
+Possible values are:
+
+- UUAA: Indicates that the type of the AA message is UUAA payload.
+- C2AUTH: Indicates that the type of the AA message is C2 authorization payload.
+
+# Annex B (informative): Change history
+
+| Change history |               |           |      |     |     |                                                                                                                                                |  |             |
+|----------------|---------------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------|--|-------------|
+| Date           | Meeting       | TDoc      | CR   | Rev | Cat | Subject/Comment                                                                                                                                |  | New version |
+| 2021-08        | CT3#117-e     | C3-214483 | -    | -   | -   | TS skeleton                                                                                                                                    |  | 0.0.0       |
+| 2021-08        | CT3#117-e     | C3-214588 |      |     |     | Added scope, introduction, references, and abbreviations.                                                                                      |  | 0.1.0       |
+| 2021-10        | CT3#118-e     | C3-215474 |      |     |     | Added service description, operations for Naf_Authentication Service and Naf_Authentication_ReauthNotify, also added resources and data model. |  | 0.2.0       |
+| 2021-11        | CT3#119-e     | C3-215474 |      |     |     | Added specification related to reauthentication and revocation. Removed resource and added custom operation.                                   |  | 0.3.0       |
+| 2021-12        | CT#94-e       | CP-213207 |      |     |     | Presented for information                                                                                                                      |  | 1.0.0       |
+| 2022-01        | CT3#119 bis-e | C3-220450 |      |     |     | Inclusion of C3-220494, C3-220265, C3-220362, C3-220340, C3-220268, C3-220279, and C3-220280                                                   |  | 1.1.0       |
+| 2022-02        | CT3#120       | C3-221513 |      |     |     | Inclusion of C3-221241, C3-221242, C3-221686, and C3-221302                                                                                    |  | 1.2.0       |
+| 2022-03        | CT#95e        | CP-220156 |      |     |     | Presentation to TSG CT for approval                                                                                                            |  | 2.0.0       |
+| 2022-03        | CT#95e        | CP-220156 |      |     |     | Approved by TSG CT                                                                                                                             |  | 17.0.0      |
+| 2022-06        | CT#96         | CP-221143 | 0001 |     |     | EN resolution                                                                                                                                  |  | 17.1.0      |
+| 2022-06        | CT#96         | CP-221143 | 0002 |     |     | Updates to Naf_Authentication_Notification                                                                                                     |  | 17.1.0      |
+| 2022-06        | CT#96         | CP-221143 | 0003 | 1   |     | Updates to Naf_Authentication_AuthenticateAuthorize service                                                                                    |  | 17.1.0      |
+| 2022-06        | CT#96         | CP-221143 | 0004 | 2   |     | Correction to remove revocation cause                                                                                                          |  | 17.1.0      |
+| 2022-06        | CT#96         | CP-221143 | 0005 | 1   |     | Corrections to open API                                                                                                                        |  | 17.1.0      |
+| 2022-06        | CT#96         | CP-221143 | 0007 |     |     | Update the data structures and OpenAPI for Naf_Authentication service                                                                          |  | 17.1.0      |
+| 2022-06        | CT#96         | CP-221143 | 0008 |     |     | Correction on data types for UAV Authentication and Authorization                                                                              |  | 17.1.0      |
+| 2022-06        | CT#96         | CP-221143 | 0009 |     |     | Correction on Security                                                                                                                         |  | 17.1.0      |
+| 2022-06        | CT#96         | CP-221143 | 0010 |     |     | Correction on status codes                                                                                                                     |  | 17.1.0      |
+| 2022-06        | CT#96         | CP-221151 | 0011 |     |     | Update of info and externalDocs fields                                                                                                         |  | 17.1.0      |
+| 2022-09        | CT#97e        | CP-222112 | 0013 | 2   |     | Application errors reference update in the tables defining methods on the resources for Naf_Authentication API                                 |  | 17.2.0      |
+| 2022-09        | CT#97e        | CP-222112 | 0014 | 1   |     | Incomplete implementation of CR #0007                                                                                                          |  | 17.2.0      |
+| 2022-09        | CT#97e        | CP-222112 | 0016 | 1   |     | Add CAA-Level UAV ID to the authorization response                                                                                             |  | 17.2.0      |
+| 2022-09        | CT#97e        | CP-222112 | 0017 | 1   |     | Missing description field for enumeration data types                                                                                           |  | 17.2.0      |
+| 2022-09        | CT#97e        | CP-222112 | 0018 | 1   |     | Operation identifier for Naf_Authentication API                                                                                                |  | 17.2.0      |
+| 2022-09        | CT#97e        | CP-222112 | 0019 | 1   |     | Update the presence condition of the attributes                                                                                                |  | 17.2.0      |
+| 2022-09        | CT#97e        | CP-222121 | 0020 |     |     | Update of info and externalDocs fields                                                                                                         |  | 17.2.0      |
+| 2022-12        | CT#98e        | CP-223180 | 0012 | 4   |     | Corrections for Auth message type                                                                                                              |  | 17.3.0      |
+| 2022-12        | CT#98e        | CP-223180 | 0021 | 1   |     | Adding missing attributes DN Authorization Profile Index and DN authorized Session AMBR                                                        |  | 17.3.0      |
+| 2022-12        | CT#98e        | CP-223188 | 0023 |     |     | Update of info and externalDocs fields                                                                                                         |  | 17.3.0      |
+| 2023-03        | CT#99         | CP-230156 | 0024 | 1   | F   | Correction of the description fields in enumerations                                                                                           |  | 18.0.0      |
+| 2023-03        | CT#99         | CP-230161 | 0026 |     | F   | Update of info and externalDocs fields                                                                                                         |  | 18.0.0      |
+| 2023-06        | CT#100        | CP-231156 | 0028 | 1   | B   | Support for A2X communications                                                                                                                 |  | 18.1.0      |
+| 2023-12        | CT#102        | CP-233279 | 0029 | 1   | B   | Include support for authorization of direct C2 communication over PC5                                                                          |  | 18.2.0      |

gsma/29_series/29524/raw.md

@@ -0,0 +1,555 @@
+
+
+# 3GPP TS 29.524 V18.0.0 (2023-12)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Cause codes mapping between 5GC interfaces; Stage3 (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller text to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a small red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                                   |    |
+|---------------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                                    | 5  |
+| 1 Scope.....                                                                                      | 6  |
+| 2 References.....                                                                                 | 6  |
+| 3 Definitions, symbols and abbreviations .....                                                    | 7  |
+| 3.1 Abbreviations .....                                                                           | 7  |
+| 4 Mapping between 5GC interfaces causes and 5GMM Cause Codes by AMF .....                         | 7  |
+| 4.1 General .....                                                                                 | 7  |
+| 4.2 Mapping between Nausf services causes and 5GMM causes .....                                   | 7  |
+| 4.2.1 General .....                                                                               | 7  |
+| 4.2.2 Mapping between Nausf_UEAuthentication service causes on N12 and 5GMM causes .....          | 8  |
+| 4.2.2.1 General .....                                                                             | 8  |
+| 4.2.2.2 Mapping from HTTP to 5GMM causes values – Request rejected by AUSF.....                   | 8  |
+| 4.2.2.3 Mapping from HTTP to 5GMM cause values – Request accepted by AUSF .....                   | 8  |
+| 4.3 Mapping between Nsmf services causes and 5GMM causes.....                                     | 9  |
+| 4.3.1 General .....                                                                               | 9  |
+| 4.3.2 Mapping between Nsmf_PDUSession service causes on N11 and 5GMM causes .....                 | 9  |
+| 4.3.2.1 General .....                                                                             | 9  |
+| 4.3.2.2 Mapping from HTTP to 5GMM Cause Values .....                                              | 9  |
+| 4.4 Mapping between Nudm services causes and 5GMM causes.....                                     | 11 |
+| 4.4.1 General .....                                                                               | 11 |
+| 4.4.2 Mapping between Nudm_UEContextManagement service causes on N8 and 5GMM causes.....          | 11 |
+| 4.4.2.1 General .....                                                                             | 11 |
+| 4.4.2.1 Mapping from HTTP to NAS cause values – Request rejected by UDM.....                      | 11 |
+| 4.4.3 Mapping between Nudm_SubscriberDataManagement service causes on N8 and 5GMM causes .....    | 11 |
+| 4.4.3.1 General .....                                                                             | 11 |
+| 4.4.3.2 Mapping from HTTP to NAS cause values – Request rejected by UDM due to N8 failure .....   | 12 |
+| 4.5 Mapping between Neir services causes and 5GMM causes .....                                    | 12 |
+| 4.5.1 General .....                                                                               | 12 |
+| 4.5.2 Mapping between N5g-eir_EquipmentIdentityCheck Service causes on N17 and 5GMM causes .....  | 12 |
+| 4.5.2.1 General .....                                                                             | 12 |
+| 4.5.2.2 Mapping from HTTP to NAS cause values – Request accepted by EIR.....                      | 12 |
+| 4.6 Mapping between Nnssf services causes and 5GMM causes .....                                   | 12 |
+| 4.6.1 General .....                                                                               | 12 |
+| 4.6.2 Mapping between Nnssf_NSSelection service causes on N22 and 5GMM causes .....               | 12 |
+| 4.6.2.1 General .....                                                                             | 12 |
+| 4.6.2.2 Mapping from HTTP to 5GMM Cause Values .....                                              | 13 |
+| 5 Mapping between 5GC interfaces causes and 5GSM Cause Codes by SMF .....                         | 13 |
+| 5.1 General .....                                                                                 | 13 |
+| 5.2 Mapping between Npcf service causes on N7 and 5GSM causes.....                                | 13 |
+| 5.2.1 General .....                                                                               | 13 |
+| 5.2.2 Mapping between Npcf_SMSPolicyControl Service causes on N7 and 5GSM causes .....            | 13 |
+| 5.2.2.1 General .....                                                                             | 13 |
+| 5.2.2.2 Mapping from HTTP to 5GSM cause values – Request rejected by PCF.....                     | 14 |
+| 5.3 Mapping between Nudm service causes on N10 and 5GSM causes.....                               | 14 |
+| 5.3.1 General .....                                                                               | 14 |
+| 5.3.2 Mapping between Nudm_UEContextManagement service causes on N10 and 5GSM causes .....        | 14 |
+| 5.3.2.1 General .....                                                                             | 14 |
+| 5.3.2.2 Mapping from HTTP to 5GSM cause values – Request rejected by UDM due to N10 failures..... | 14 |
+| 5.3.3 Mapping between Nudm_SubscriberDataManagement service causes on N10 and 5GSM causes .....   | 15 |
+| 5.3.3.1 General .....                                                                             | 15 |
+| 5.3.3.2 Mapping from HTTP to 5GSM cause values – Request rejected by UDM due to N10 failures..... | 15 |
+| 5.4 Mapping between N4 causes and 5GSM causes.....                                                | 15 |
+| 5.4.1 General .....                                                                               | 15 |
+| 5.4.2 Mapping from N4 to 5GSM cause values .....                                                  | 16 |
+
+5.5 Mapping between Nnsacf services causes and 5GSM causes..... 17  
+5.5.1 General ..... 17  
+5.5.2 Mapping between Nnsacf\_NSAC service causes on N81 and 5GSM causes..... 17  
+5.5.2.1 General..... 17  
+5.5.2.2 Mapping from HTTP to 5GSM Cause Values..... 17  
+**Annex A (informative): Change history..... 18**
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# --- 1 Scope
+
+The present document specifies the mapping:
+
+- performed by the AMF between HTTP responses (Status Codes and Protocol or Application Errors) returned by 5GC NFs to the AMF and 5GMM Cause values sent to UEs;
+- performed by the SMF between HTTP responses (Status Codes and Protocol or Application Errors) returned by 5GC NFs to SMF and 5GSM Cause values sent to UEs;
+- performed by the SMF between N4 errors returned by the UPF and 5GSM Cause values sent to UEs.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 29.244: "Interface between the Control Plane and the User Plane Nodes".
+- [3] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
+- [4] 3GPP TS 29.531: "5G System; Network Slice Selection Services; Stage 3".
+- [5] 3GPP TS 29.503: "5G System; Unified Data Management Services; Stage 3".
+- [6] 3GPP TS 29.512: "5G System; Session Management Policy Control Service; Stage 3".
+- [7] 3GPP TS 29.509: "5G System; Authentication Server Services; Stage 3".
+- [8] 3GPP TS 29.502: "5G System; Session Management Services; Stage 3".
+- [9] 3GPP TS 29.508: "5G System, Session Management Event Exposure Service; Stage 3".
+- [10] 3GPP TS 29.540: "5G System; SMS Services; Stage3 ".
+- [11] 3GPP TS 29.511: "5G System; Equipment Identity Register Services; Stage 3".
+- [12] 3GPP TS 29.507: "5G System; Access and Mobility Policy Control Service; Stage 3".
+- [13] 3GPP TS 29.525: "5G System; UE Policy Control Service; Stage 3".
+
+[xx] 3GPP TS 29.536: "5G System; Network Slice Admission Control Services; Stage 3".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|      |                                         |
+|------|-----------------------------------------|
+| 5GC  | 5G Core Network                         |
+| AMF  | Access and Mobility Management Function |
+| HTTP | Hypertext Transfer Protocol             |
+| NF   | Network Function                        |
+| NSSF | Network Slice Selection Function        |
+| PCF  | Policy Control Function                 |
+| SMF  | Session Management Function             |
+| UDM  | Unified Data Management                 |
+
+# --- 4 Mapping between 5GC interfaces causes and 5GMM Cause Codes by AMF
+
+## 4.1 General
+
+This clause defines the mapping performed by the AMF between HTTP responses (status codes and Protocol or Application Errors) returned by NF services contacted by the AMF and the 5GMM cause values sent to UEs.
+
+No mapping is required for:
+
+- the Nsmf\_SMService\_Activate, Nsmf\_SMService\_Deactivate and Nsmf\_SMService\_UplinkSMS operations described in 3GPP TS 29.540 [10].
+- the Npcf\_AMPolicyControl service operations described in 3GPP TS 29.507 [12].
+- the Npcf\_UEPolicyControl service operations described in 3GPP TS 29.525 [13].
+
+## 4.2 Mapping between Nausf services causes and 5GMM causes
+
+### 4.2.1 General
+
+This clause defines the mapping performed by the AMF between HTTP responses (status codes and Protocol or Application Errors) returned by AUSF services to the AMF and the 5GMM cause values sent to UEs.
+
+### 4.2.2 Mapping between Nausf\_UEAuthentication service causes on N12 and 5GMM causes
+
+#### 4.2.2.1 General
+
+This clause defines the mapping for the Nausf\_UEAuthentication service (see 3GPP TS 29.509 [7]). It also contains the mapping in case of a 200 OK is returned but the Authentication has failed.
+
+#### 4.2.2.2 Mapping from HTTP to 5GMM causes values – Request rejected by AUSF
+
+**Table .4.2.2-1: Mapping from HTTP to 5GMM cause values – Request rejected by AUSF**
+
+| HTTP status code on N12   | Protocol or Application Error    | 5GMM cause to UE                                                                                                                                                                 |
+|---------------------------|----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 403 Forbidden             | SERVING_NETWORK_NOT_AUTHORIZED   | Cause #11 – PLMN not allowed<br>Cause #73 – Serving network not authorized<br>Cause #12 – Tracking area not allowed<br>Cause #15 – No suitable cells in tracking area<br>(NOTE1) |
+|                           | AUTHENTICATION_REJECTED          | N/A (NOTE 2)                                                                                                                                                                     |
+|                           | INVALID_HN_PUBLIC_KEY_IDENTIFIER | N/A (NOTE 2)                                                                                                                                                                     |
+|                           | INVALID_HN_PUBLIC_KEY_IDENTIFIER | N/A (NOTE 2)                                                                                                                                                                     |
+| 404 Not Found             | CONTEXT_NOT_FOUND                | N/A (NOTE 2)                                                                                                                                                                     |
+|                           | USER_NOT_FOUND                   |                                                                                                                                                                                  |
+| 504 Gateway Timeout       | UPSTREAM_SERVER_ERROR            | N/A (NOTE 2)                                                                                                                                                                     |
+|                           | NETWORK_FAILURE                  | N/A (NOTE 2)                                                                                                                                                                     |
+| 500 Internal Server Error | AV_GENERATION_PROBLEM            | N/A (NOTE 2)                                                                                                                                                                     |
+| 501 Not Implemented       | UNSUPPORTED_PROTECTION_SCHEME    | N/A (NOTE 2)                                                                                                                                                                     |
+
+NOTE 1: One of these 5GMM causes may be used.  
+NOTE 2: There is no corresponding mapping since the Authentication is rejected and the Authentication Reject message does not have a 5GMM cause.
+
+#### 4.2.2.3 Mapping from HTTP to 5GMM cause values – Request accepted by AUSF
+
+**Table .4.2.2.3-1: Mapping from HTTP to 5GMM cause values – Request accepted by AUSF**
+
+| HTTP status code on N12 | Protocol or Application Error                                                                                                   | 5GMM cause to UE      |
+|-------------------------|---------------------------------------------------------------------------------------------------------------------------------|-----------------------|
+| 200 OK                  | The "authResult" in "ConfirmationDataResponse" is set to "AUTHENTICATION_FAILURE" (see clause 6.1.6.2.8 of 3GPP TS 29.509 [7]). | Cause #3 – Illegal UE |
+|                         | The "authResult" in "EapSession" is set to "AUTHENTICATION_FAILURE" (see clause 6.1.6.2.8 of 3GPP TS 29.509 [7]).               | Cause #3 – Illegal UE |
+
+## 4.3 Mapping between Nsmf services causes and 5GMM causes
+
+### 4.3.1 General
+
+This clause defines the mapping performed by the AMF between HTTP responses (status codes and Protocol or Application Errors) returned by SMF services to the AMF and the 5GMM cause values sent to UEs.
+
+The AMF may invoke SMF service operations upon receipt of:
+
+- 5GSM messages (e.g. PDU Session establishment request) piggybacked in 5GMM UL NAS TRANSPORT message;
+- 5GMM Service Request or Registration Request messages, to establish the user-plane resources of a PDU session.
+
+A 5GMM cause is defined in:
+
+- the DL NAS TRANSPORT message;
+- the PDU session reactivation result error cause IE of a REGISTRATION ACCEPT or SERVICE ACCEPT message;
+- the REGISTRATION REJECT or SERVICE REJECT message.
+
+The AMF shall support mapping the status code and/or Protocol or Application Error received from the SMF to a 5GMM cause code, where 3GPP TS 24.501 [3] requires a 5GMM Cause to be included in the 5GMM message sent to the UE.
+
+NOTE: REGISTRATION REJECT and SERVICE REJECT messages are rejected only due to 5GMM-specific reasons, i.e. not for problems specific to session management.
+
+### 4.3.2 Mapping between Nsmf\_PDUSession service causes on N11 and 5GMM causes
+
+#### 4.3.2.1 General
+
+This clause defines the mapping for the Nsmf\_PDUSession service (see 3GPP TS 29.502 [8]).
+
+#### 4.3.2.2 Mapping from HTTP to 5GMM Cause Values
+
+Table 4.3.2.2-1: Mapping from HTTP to 5GMM cause values – Request rejected by SMF
+
+| HTTP status code on N11 | Protocol or Application Error                                                                                                                       | 5GMM cause to UE                                            |
+|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|
+| 200 OK                  | The upCnxState IE is set to DEACTIVATED and the Cause IE set to "INSUFFICIENT_UP_RESOURCES" (see clause 5.2.2.3.2.2 of 3GPP TS 29.502 [8]) (NOTE 2) | #92 - Insufficient user-plane resources for the PDU session |
+| 403 Forbidden           | OUT_OF_LADN_SERVICE_AREA                                                                                                                            | #43 - LADN not available                                    |
+| 403 Forbidden           | PRIORITIZED_SERVICES_ONLY                                                                                                                           | #28 - Restricted service area                               |
+| 404 Not Found           | CONTEXT_NOT_FOUND                                                                                                                                   | N/A (NOTE 1)                                                |
+|                         |                                                                                                                                                     |                                                             |
+|                         |                                                                                                                                                     |                                                             |
+|                         |                                                                                                                                                     |                                                             |
+| 504 Gateway Timeout     | NETWORK_FAILURE                                                                                                                                     | N/A (NOTE 1)                                                |
+
+NOTE 1: An N1 SM cause is included by the SMF in the HTTP error response in this case.
+
+NOTE 2: This corresponds to the scenario where NG-RAN cannot establish user plane resources during the activation of the User Plane connection of a PDU session.
+
+## 4.4 Mapping between Nudm services causes and 5GMM causes
+
+### 4.4.1 General
+
+This clause defines the mapping performed by the AMF between HTTP responses (status codes and Protocol or Application Errors) returned by UDM services to AMF and the 5GMM cause values sent to UEs.
+
+### 4.4.2 Mapping between Nudm\_UEContextManagement service causes on N8 and 5GMM causes
+
+#### 4.4.2.1 General
+
+This clause defines the mapping for the Nudm\_UEContextManagement service is described in 3GPP TS 29.503 [5]).
+
+#### 4.4.2.1 Mapping from HTTP to NAS cause values – Request rejected by UDM
+
+**Table 4.4.2.1-1: Mapping from HTTP to 5GMM cause values – Request rejected by UDM**
+
+| HTTP status code on N8                                                                          | Protocol or Application Error | 5GMM cause to UE                                                                                                                              |
+|-------------------------------------------------------------------------------------------------|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|
+| 403 Forbidden                                                                                   | UNKNOWN_5GS_SUBSCRIPTION      | #27 – N1 mode not allowed                                                                                                                     |
+|                                                                                                 | ACCESS_NOT_ALLOWED            | #15 "No suitable cells in tracking area", or<br>#12 "Tracking area not allowed"<br>or<br>#72 – Non-3GPP access to 5GCN not allowed (NOTE)     |
+|                                                                                                 | RAT_NOT_ALLOWED               | #15 "No suitable cells in tracking area", or<br>#13 "Roaming not allowed in this tracking area", or<br>#12 "Tracking area not allowed" (NOTE) |
+|                                                                                                 | NO_PS_SUBSCRIPTION            | #7 – 5GS services not allowed                                                                                                                 |
+|                                                                                                 | ROAMING_NOT_ALLOWED           | #11 "PLMN not allowed" or<br>#13 "Roaming not allowed in this tracking area", (NOTE)                                                          |
+| 404 Not Found                                                                                   | CONTEXT_NOT_FOUND             | #9 "UE identity cannot be derived by the network"                                                                                             |
+| 404 Not Found                                                                                   | USER_NOT_FOUND                | #3 "Illegal UE"                                                                                                                               |
+| 422 Unprocessable Entity                                                                        | UNPROCESSABLE_REQUEST         | #111 protocol error unspecified                                                                                                               |
+| NOTE: Any of those NAS Cause Code values may be sent to the UE, depending on operator's choice. |                               |                                                                                                                                               |
+
+### 4.4.3 Mapping between Nudm\_SubscriberDataManagement service causes on N8 and 5GMM causes
+
+#### 4.4.3.1 General
+
+This clause defines the mapping for the Nudm\_SubscriberDataManagement service is described in 3GPP TS 29.503 [5]).
+
+#### 4.4.3.2 Mapping from HTTP to NAS cause values – Request rejected by UDM due to N8 failure
+
+**Table 4.4.x.2-1: Mapping from HTTP to 5GMM cause values – Request rejected by UDM due to N8 failures when consuming Nudm\_SubscriberDataManagement service**
+
+| HTTP status code on N8                                                                          | Protocol or Application Error    | 5GMM cause to UE                             |
+|-------------------------------------------------------------------------------------------------|----------------------------------|----------------------------------------------|
+| 404 Not Found                                                                                   | USER_NOT_FOUND<br>DATA_NOT_FOUND | #3 "Illegal UE"<br>#27 "N1 mode not allowed" |
+| NOTE: Any of those NAS Cause Code values may be sent to the UE, depending on operator's choice. |                                  |                                              |
+
+## 4.5 Mapping between Neir services causes and 5GMM causes
+
+### 4.5.1 General
+
+This clause defines the mapping performed by the AMF between HTTP responses (status code and Protocol or Application Errors) returned by the EIR to the AMF and the 5GMM cause values sent to UEs.
+
+### 4.5.2 Mapping between N5g-eir\_EquipmentIdentityCheck Service causes on N17 and 5GMM causes
+
+#### 4.5.2.1 General
+
+This clause defines the mapping for the N5g-eir\_EquipmentIdentityCheck service (see 3GPP TS 29.511 [11]).
+
+#### 4.5.2.2 Mapping from HTTP to NAS cause values – Request accepted by EIR
+
+**Table 4.5.2.2-1: Mapping from HTTP to 5GMM cause values – Request accepted by EIR**
+
+| HTTP Status on N17 | Protocol or Application information                                                                     | 5GMM cause to UE |
+|--------------------|---------------------------------------------------------------------------------------------------------|------------------|
+| 200 OK             | Equipment Status is set to "BLACKLISTED", which indicates that the equipment is in the prohibited list. | #6 "Illegal ME"  |
+
+## 4.6 Mapping between Nnssf services causes and 5GMM causes
+
+### 4.6.1 General
+
+This clause defines the mapping performed by the AMF between HTTP responses (Status Code and Protocol or Application Errors) returned by the NSSF to the AMF and the 5GMM cause values sent to UEs.
+
+### 4.6.2 Mapping between Nnssf\_NSSelection service causes on N22 and 5GMM causes
+
+#### 4.6.2.1 General
+
+This clause defines the mapping for the Nnssf\_NSSelection service (see 3GPP TS 29.531 [4]).
+
+#### 4.6.2.2 Mapping from HTTP to 5GMM Cause Values
+
+**Table 4.6.2.2-1: Mapping from HTTP to 5GMM cause values – Request rejected by NSSF**
+
+| HTTP status code on N22 | Protocol or Application Error | 5GMM cause to UE                  |
+|-------------------------|-------------------------------|-----------------------------------|
+| 403 Forbidden           | SNSSAI NOT SUPPORTED          | #62 – No Network Slices available |
+
+# --- 5 Mapping between 5GC interfaces causes and 5GSM Cause Codes by SMF
+
+## 5.1 General
+
+This clause describes the mapping performed by the SMF between HTTP responses (status Code and Protocol or Application Errors) returned by NF services contacted by the SMF and the corresponding 5GSM cause values sent to UEs (in5GSMmessages).
+
+No mapping is required for the Nsmf\_PDUSession service over N11 since the SMF includes the 5GSM cause in 5GSM messages sent in N1 SM Information (see 3GPP TS 29.502 [5]).
+
+No mapping is required for the Nsmf\_PDUSession service over N16 since the 5GSM cause is generated at the H-SMF and provided to the V-SMF in N1 SM Information (see 3GPP TS 29.502 [9]).
+
+No mapping is required for the Nsmf\_EventExposure service specified in 3GPP TS 29.508 [9]
+
+## 5.2 Mapping between Npcf service causes on N7 and 5GSM causes
+
+### 5.2.1 General
+
+This clause defines the mapping performed by the SMF between HTTP responses (status code and Protocol or Application Errors) returned by the PCF to the SMF and the 5GSM causes sent to UEs.
+
+### 5.2.2 Mapping between Npcf\_SMPolicyControl Service causes on N7 and 5GSM causes
+
+#### 5.2.2.1 General
+
+This clause defines the mapping for the Npcf\_SMPolicyControl service (see 3GPPTS 29.512 [6]).
+
+#### 5.2.2.2 Mapping from HTTP to 5GSM cause values – Request rejected by PCF
+
+**Table 5.2.2.2-1: Mapping from HTTP to 5GSM cause values – Request rejected by PCF**
+
+| HTTP status code on N7 | Protocol or Application Error       | 5GSM cause to UE                                               |
+|------------------------|-------------------------------------|----------------------------------------------------------------|
+| 400 Bad Request        | USER_UNKNOWN                        | Cause #29 - User authentication or authorization failed        |
+|                        | ERROR_INITIAL_PARAMETERS            | Cause #31 - Request rejected, unspecified                      |
+|                        | ERROR_TRIGGER_EVENT                 | Cause #31 - Request rejected, unspecified                      |
+| 403 Forbidden          | ERROR_TRAFFIC_MAPPING_INFO_REJECTED | Cause #29 - User authentication or authorization failed        |
+|                        | POLICY_CONTEXT_DENIED               | Cause #29 - User authentication or authorization failed (NOTE) |
+|                        | VALIDATION_CONDITION_NOT_MET        | Cause #29 - User authentication or authorization failed        |
+|                        | EXCEEDED_UE_SLICE_DATA_RATE         | Cause #69 - Insufficient resources for specific slice          |
+|                        | EXCEEDED_SLICE_DATA_RATE            | Cause #69 - Insufficient resources for specific slice          |
+|                        | EXCEEDED_GROUP_DATA_RATE            | Cause #69 - Insufficient resources for specific slice          |
+
+NOTE: Upon receiving the cause POLICY CONTEXT DENIED, the SMF may reject the request, or it may accept the request based on the local policy.
+
+## 5.3 Mapping between Nudm service causes on N10 and 5GSM causes
+
+### 5.3.1 General
+
+This clause defines the mapping performed by the SMF between HTTP responses (status codes and Protocol or Application Errors) returned by the UDM to the SMF and the 5GSM causes sent to UEs.
+
+### 5.3.2 Mapping between Nudm\_UEContextManagement service causes on N10 and 5GSM causes
+
+#### 5.3.2.1 General
+
+This clause defines the mapping for the Nudm\_UEContextManagement service (see 3GPP TS 29.503 [5]).
+
+#### 5.3.2.2 Mapping from HTTP to 5GSM cause values – Request rejected by UDM due to N10 failures
+
+**Table 5.3.2.2-1: Mapping from HTTP to 5GSM cause values – Request rejected by UDM due to N10 failures**
+
+| HTTP status code on N10 | Protocol or Application Error | 5GSM cause to UE                                                                                                                                |
+|-------------------------|-------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|
+| 403 Forbidden           | ROAMING_NOT_ALLOWED           | #29 "User authentication or authorization failed"                                                                                               |
+|                         | DNN_NOT_ALLOWED               | #27 "Missing or unknown DNN" or<br>#67 "Insufficient resources for specific slice and DNN"<br>#70 "Missing or unknown DNN in a slice"<br>(NOTE) |
+| 404 Not Found           | USER NOT FOUND                | #29 "User authentication or authorization failed"                                                                                               |
+
+NOTE: Any of those NAS Cause Code values may be sent to the UE, depending on operator's choice.
+
+### 5.3.3 Mapping between Nudm\_SubscriberDataManagement service causes on N10 and 5GSM causes
+
+#### 5.3.3.1 General
+
+This clause defines the mapping for the Nudm\_SubscriberDataManagement service (see 3GPP TS 29.503 [5]).
+
+#### 5.3.3.2 Mapping from HTTP to 5GSM cause values – Request rejected by UDM due to N10 failures
+
+**Table 5.3.3.2-1: Mapping from HTTP to 5GSM cause values – Request rejected by UDM due to N10 failures when consuming Nudm\_SubscriberDataManagement service**
+
+| HTTP status code on N10 | Protocol or Application Error    | 5GSM cause to UE                                                                                   |
+|-------------------------|----------------------------------|----------------------------------------------------------------------------------------------------|
+| 404 Not Found           | USER NOT FOUND<br>DATA_NOT_FOUND | #29 "User authentication or authorization failed"<br>#33 "Requested service option not subscribed" |
+
+NOTE: Any of those NAS Cause Code values may be sent to the UE, depending on operator's choice.
+
+## 5.4 Mapping between N4 causes and 5GSM causes
+
+### 5.4.1 General
+
+N4 error handling and cause codes are defined in 3GPP TS 29.244 [2].
+
+The receipt of an N4 error may trigger error handling in SMF. This clause defines the mapping performed by the SMF between when an error received on N4 interface cannot be resolved by SMF and results in the SMF sending a 5GSM message to the UE.
+
+### 5.4.2 Mapping from N4 to 5GSM cause values
+
+**Table 5.4.2-1: Mapping from N4 to 5GSM cause values – Request rejected by SMF due to N4 failures**
+
+| <b>N4 Cause Code</b>   |                                               | <b>5GSM cause to UE</b>  |                                                                                                                                                      |
+|------------------------|-----------------------------------------------|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Cause value<br>Decimal | Error description                             | Cause value              | Error description                                                                                                                                    |
+| 64                     | Request rejected<br>(reason not<br>specified) | #31                      | Request rejected,<br>unspecified                                                                                                                     |
+| 74                     | PFCP entity in<br>congestion                  | #26<br>#38<br>#69<br>#67 | Insufficient resources<br>Network Failure<br>Insufficient resources<br>for specific slice<br>Insufficient resources<br>for specific slice and<br>DNN |
+| 77                     | System failure                                | #31                      | Request rejected,<br>unspecified                                                                                                                     |
+
+## 5.5 Mapping between Nnsacf services causes and 5GSM causes
+
+### 5.5.1 General
+
+This clause defines the mapping performed by the SMF between HTTP responses (Status Code and Protocol or Application Errors) returned by the NSACF to the SMF and the 5GSM cause values sent to UEs.
+
+### 5.5.2 Mapping between Nnsacf\_NSAC service causes on N81 and 5GSM causes
+
+#### 5.5.2.1 General
+
+This clause defines the mapping for the Nnsacf\_NSAC service (see 3GPP TS 29.536 [14]).
+
+#### 5.5.2.2 Mapping from HTTP to 5GSM Cause Values
+
+**Table 5.X.2.2-1: Mapping from HTTP to 5GSM cause values – Request rejected by NSACF**
+
+| HTTP status code on N81 | Protocol or Application Error | 5GSM cause to UE                               |
+|-------------------------|-------------------------------|------------------------------------------------|
+| 403 Forbidden           | ALL_SLICE_FAILED              | #69 –Insufficient resources for specific slice |
+
+# Annex A (informative): Change history
+
+| Change history |           |           |      |     |     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |             |
+|----------------|-----------|-----------|------|-----|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date           | Meeting   | TDoc      | CR   | Rev | Cat | Subject/Comment                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | New version |
+| 2018-10        | CT4#86Bis |           |      |     |     | First version of this new TS including:<br>C4-187375 (Skeleton)<br>C4-187378 (N11 – 5GMM)<br>C4-187391 (N8 – 5GMM – Request rejected)<br>C4-187589 (Scope)<br>C4-187390 (N4 – 5GMM)                                                                                                                                                                                                                                                                                                             | 0.1.0       |
+| 2018-12        | CT4#87    |           |      |     |     | The following agreed documents are included:<br>C4-188418 (NSSF)<br>C4-188484 (Nsmf_PDUSession N11 and N16)<br>C4-188486 (Cause 5GMM)<br>C4-188609 (N4)<br>C4-188637 (N8 and 5GMM)<br>C4-188638 (EIR)<br>C4-188640 (N10 and 5GSM)<br>C4-188641 (N7)<br>C4-188642 (Nausf)<br>C4-188643 (N11 5GMM)<br>C4-188647 (Clean-up) (Conclusion from C4-188384 was wrongly reported to be included in 5GSM General Clause while it applied to 5GMM – corrected by Rapporteur).<br>C4-188648 (General 5GSM) | 0.2.0       |
+| 2018-12        | CT#82     | CP-183104 |      |     |     | Sent for information and approval                                                                                                                                                                                                                                                                                                                                                                                                                                                               | 1.0.0       |
+| 2018-12        | CT#82     | CP-183104 |      |     |     | Approved in CT#82                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | 15.0.0      |
+| 2019-03        | CT#83     | CP-190031 | 0001 | 2   | F   | Corrections on cause mapping in clause 4                                                                                                                                                                                                                                                                                                                                                                                                                                                        | 15.1.0      |
+| 2019-03        | CT#83     | CP-190031 | 003  | 1   | F   | Mapping between N11 causes and 5GMM causes                                                                                                                                                                                                                                                                                                                                                                                                                                                      | 15.1.0      |
+| 2019-03        | CT#83     | CP-190031 | 0008 | 1   | F   | Remove EN's in 5.2.2.2                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | 15.1.0      |
+| 2019-03        | CT#83     | CP-190031 | 0004 | 2   | F   | Corrections to 5GMM and 5GSM causes mappings                                                                                                                                                                                                                                                                                                                                                                                                                                                    | 15.1.0      |
+| 2019-06        | CT#84     | CP-191037 | 0012 | -   | F   | Cause mapping updates                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | 15.2.0      |
+| 2019-06        | CT#84     | CP-191037 | 0013 | 1   | F   | Correction on cause mapping regarding no subscription                                                                                                                                                                                                                                                                                                                                                                                                                                           | 15.2.0      |
+| 2019-06        | CT#84     | CP-191037 | 0014 | 2   | F   | Essential Correction on Error mapping for NSSF Services                                                                                                                                                                                                                                                                                                                                                                                                                                         | 15.2.0      |
+| 2019-06        | CT#84     | CP-191037 | 0015 | 1   | F   | Essential Correction on mapping for N4 to SBI                                                                                                                                                                                                                                                                                                                                                                                                                                                   | 15.2.0      |
+| 2019-06        | CT#84     | CP-191037 | 0016 | 1   | F   | Cause mapping corrections                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | 15.2.0      |
+| 2019-06        | CT#84     | CP-191037 | 0017 | 1   | F   | Add a mapping for N10                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | 15.2.0      |
+| 2019-12        | CT#86     | CP-193036 | 0019 | 2   | F   | Add new mapping towards Cause #62 (No Network Slices available)                                                                                                                                                                                                                                                                                                                                                                                                                                 | 16.0.0      |
+| 2020-06        | CT#88e    | CP-201034 | 0020 | 1   | F   | Correction of the mapping between PCF service causes and 5GSM causes                                                                                                                                                                                                                                                                                                                                                                                                                            | 16.1.0      |
+| 2021-03        | CT#91e    | CP-210027 | 0022 | 1   | D   | Use of inclusive terminology                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | 17.0.0      |
+| 2021-03        | CT#91e    | CP-210028 | 0023 | 1   | F   | ERROR CONFLICTING REQUEST                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | 17.0.0      |
+| 2021-06        | CT#92e    | CP-211146 | 0024 |     | F   | Editorial Correction                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | 17.1.0      |
+| 2021-09        | CT#93e    | CP-212230 | 0025 | 1   | B   | Cause Mapping for NSAC                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | 17.2.0      |
+| 2021-12        | CT#94e    | CP-213086 | 0026 | -   | F   | Mapping for the cause from Nudm_SubscriberDataManagement                                                                                                                                                                                                                                                                                                                                                                                                                                        | 17.3.0      |
+| 2023-12        | CT#102    | CP-233064 | 0028 | 1   | F   | Cause mapping for EXCEEDED_UE_SLICE_DATA_RATE and EXCEEDED_SLICE_DATA_RATE                                                                                                                                                                                                                                                                                                                                                                                                                      | 17.4.0      |
+| 2023-12        | CT#102    | CP-233047 | 0027 | -   | B   | Cause mapping for EXCEEDED_GROUP_DATA_RATE                                                                                                                                                                                                                                                                                                                                                                                                                                                      | 18.0.0      |

gsma/29_series/29578/raw.md

@@ -0,0 +1,702 @@
+
+
+# 3GPP TS 29.578 V18.1.0 (2023-12)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Mobile Number Portability Services; Stage 3 (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller text to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' underneath.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                          |    |
+|------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                           | 6  |
+| 1 Scope.....                                                                             | 8  |
+| 2 References.....                                                                        | 8  |
+| 3 Definitions, symbols and abbreviations .....                                           | 9  |
+| 3.1 Definitions.....                                                                     | 9  |
+| 3.2 Symbols.....                                                                         | 9  |
+| 3.3 Abbreviations .....                                                                  | 9  |
+| 4 Overview.....                                                                          | 9  |
+| 4.1 Introduction .....                                                                   | 9  |
+| 5 Services offered by the MNPF.....                                                      | 10 |
+| 5.1 Introduction .....                                                                   | 10 |
+| 5.2 Nmpf_NPStatus Service.....                                                           | 10 |
+| 5.2.1 Service Description .....                                                          | 10 |
+| 5.2.2 Service Operations.....                                                            | 10 |
+| 5.2.2.1 Introduction.....                                                                | 10 |
+| 5.2.2.2 Get.....                                                                         | 10 |
+| 5.2.2.2.1 General .....                                                                  | 10 |
+| 5.2.2.2.2 MNPF Status information retrieval .....                                        | 10 |
+| 6 API Definitions .....                                                                  | 11 |
+| 6.1 Nmpf_NPStatus Service API .....                                                      | 11 |
+| 6.1.1 Introduction .....                                                                 | 11 |
+| 6.1.2 Usage of HTTP.....                                                                 | 11 |
+| 6.1.2.1 General.....                                                                     | 11 |
+| 6.1.2.2 HTTP standard headers.....                                                       | 12 |
+| 6.1.2.2.1 General .....                                                                  | 12 |
+| 6.1.2.2.2 Content type .....                                                             | 12 |
+| 6.1.2.3 HTTP custom headers.....                                                         | 12 |
+| 6.1.3 Resources.....                                                                     | 12 |
+| 6.1.3.1 Overview.....                                                                    | 12 |
+| 6.1.3.2 Resource: NPstatus .....                                                         | 13 |
+| 6.1.3.2.1 Description .....                                                              | 13 |
+| 6.1.3.2.2 Resource Definition.....                                                       | 13 |
+| 6.1.3.2.3 Resource Standard Methods.....                                                 | 13 |
+| 6.1.4 Custom Operations without associated resources .....                               | 13 |
+| 6.1.5 Notifications .....                                                                | 13 |
+| 6.1.6 Data Model .....                                                                   | 14 |
+| 6.1.6.1 General.....                                                                     | 14 |
+| 6.1.6.2 Structured data types.....                                                       | 14 |
+| 6.1.6.2.1 Introduction .....                                                             | 14 |
+| 6.1.6.2.2 Type: NpStatusInfo .....                                                       | 14 |
+| 6.1.6.3 Simple data types and enumerations.....                                          | 14 |
+| 6.1.6.3.1 Introduction .....                                                             | 14 |
+| 6.1.6.3.2 Simple data types .....                                                        | 14 |
+| 6.1.6.4 Data types describing alternative data types or combinations of data types ..... | 15 |
+| 6.1.6.5 Binary data.....                                                                 | 15 |
+| 6.1.7 Error Handling.....                                                                | 15 |
+| 6.1.7.1 General.....                                                                     | 15 |
+| 6.1.7.2 Protocol Errors.....                                                             | 15 |
+| 6.1.7.3 Application Errors.....                                                          | 15 |
+| 6.1.8 Feature negotiation .....                                                          | 15 |
+| 6.1.9 Security.....                                                                      | 15 |
+
+**Annex A (normative): OpenAPI specification ..... 16**  
+A.1 General..... 16  
+A.2 Nmnpf\_NPStatus API..... 16  
+**Annex B (informative): Withdrawn API versions ..... 17**  
+B.1 General..... 17  
+B.2 Nmnpf\_NPstatus API..... 17  
+**Annex C (informative): Change history..... 19**
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# --- 1 Scope
+
+The present document specifies the stage 3 protocol and data model for the Nnmpf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the MNPF.
+
+The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
+
+The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5].
+
+Stage 2 requirements for the Nnmpf services are specified in 3GPP TS 23.540 [14].
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
+- [3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
+- [4] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
+- [5] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
+- [6] OpenAPI: "OpenAPI Specification Version 3.0.0", <https://spec.openapis.org/oas/v3.0.0>.
+- [7] 3GPP TR 21.900: "Technical Specification Group working methods".
+- [8] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
+- [9] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
+- [10] 3GPP TS 29.510: "5G System; Network Function Repository Services; Stage 3".
+- [11] IETF RFC 9113: "HTTP/2".
+- [12] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
+- [13] IETF RFC 9457: "Problem Details for HTTP APIs".
+- [14] 3GPP TS 23.540: " Technical realization of Service Based Short Message Service; Stage 2".
+- [15] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces Stage 3".
+
+# 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**Nmnpf:** Service-based interface exhibited by the MNPF server
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+<symbol>            <Explanation>
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|      |                                    |
+|------|------------------------------------|
+| MNPF | Mobile Number Portability Function |
+|------|------------------------------------|
+
+# 4 Overview
+
+## 4.1 Introduction
+
+Within the 5GC, the MNPF offers services to the SMS-GMSC, NRF and SCP via the Nmnpf service based interface (see 3GPP TS 23.501 [2], 3GPP TS 23.502 [3], and 3GPP TS 23.540 [14]).
+
+Figure 4.1-1 provides the reference model (in service based interface representation and in reference point representation), with focus on the MNPF.
+
+![Reference model diagram for MNPF showing NRF, SMS-GMSC, and SCP connected to the MNPF via the Nmnpf interface.](2a0f333f04f8e672bebf288c511c1db5_img.jpg)
+
+The diagram illustrates the reference model for the MNPF. On the left, three functional blocks are shown: NRF, SMS-GMSC, and SCP. Each block is connected to a central interface point labeled 'Nmnpf' via a line representing a service based interface. The connections are labeled SM14 (NRF to Nmnpf), SM12 (SMS-GMSC to Nmnpf), and SM13 (SCP to Nmnpf). The 'Nmnpf' interface is represented by a circle on the left side of a large green rectangular block labeled 'MNPF'.
+
+Reference model diagram for MNPF showing NRF, SMS-GMSC, and SCP connected to the MNPF via the Nmnpf interface.
+
+**Figure 4.1-1: Reference model – MNPF**
+
+The functionalities supported by the MNPF are listed in clause 6.7 of 3GPP TS 23.540 [14].
+
+# 5 Services offered by the MNPF
+
+## 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{}).
+
+![Sequence diagram showing the interaction between an NF service consumer and an MNPF to request a UE's NP status. The consumer sends a GET request to the MNPF. The MNPF responds with either a 200 OK (NpStatusInfo) or a 404 Not Found.](5a4e62bead259c258d069fd3663ea670_img.jpg)
+
+```
+
+sequenceDiagram
+    participant NF service consumer
+    participant MNPF
+    Note left of NF service consumer: Requesting a UE's NP status
+    NF service consumer->>MNPF: 1. GET .../{gpsi}
+    MNPF-->>NF service consumer: 2a. 200 OK (NpStatusInfo)
+    MNPF-->>NF service consumer: 2b. 404 Not Found
+  
+```
+
+Sequence diagram showing the interaction between an NF service consumer and an MNPF to request a UE's NP status. The consumer sends a GET request to the MNPF. The MNPF responds with either a 200 OK (NpStatusInfo) or a 404 Not Found.
+
+**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.
+
+# 6 API Definitions
+
+## 6.1 Nmnpf\_NPStatus Service API
+
+### 6.1.1 Introduction
+
+The Nmnpf\_NPStatus service shall use the Nmnpf\_NPStatus API.
+
+The API URI of the Nmnpf\_NPStatus 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 "nmnpf-npstatus".
+- The <apiVersion> shall be "v1".
+- The <apiSpecificResourceUriPart> shall be set as described in clause 6.1.3.
+
+### 6.1.2 Usage of HTTP
+
+#### 6.1.2.1 General
+
+HTTP/2, IETF RFC 9113 [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 Nmnpf\_NPStatus API is contained in Annex A.
+
+#### 6.1.2.2 HTTP standard headers
+
+##### 6.1.2.2.1 General
+
+See clause 5.2.2 of 3GPP TS 29.500 [4] for the usage of HTTP standard headers.
+
+##### 6.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 9457 [13].
+
+#### 6.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.
+
+### 6.1.3 Resources
+
+#### 6.1.3.1 Overview
+
+This clause describes the structure for the Resource URIs and the resources and methods used for the service.
+
+Figure 6.1.3.1-1 depicts the resource URIs structure for the Nmnpf\_NPStatus API.
+
+![Diagram showing the resource URI structure for the Nmnpf_NPStatus API. The root path is {apiRoot}/nmnpf_npstatus/{apiVersion}. A line branches from this root to a box containing the relative path /{gpsi}.](e787e02d9214556476d95941bda1d350_img.jpg)
+
+```
+
+    {apiRoot}/nmnpf_npstatus/{apiVersion}
+    |
+    +--> /{gpsi}
+  
+```
+
+Diagram showing the resource URI structure for the Nmnpf\_NPStatus API. The root path is {apiRoot}/nmnpf\_npstatus/{apiVersion}. A line branches from this root to a box containing the relative path /{gpsi}.
+
+**Figure 6.1.3.1-1: Resource URI structure of the Nmnpf\_NPStatus API**
+
+Table 6.1.3.1-1 provides an overview of the resources and applicable HTTP methods.
+
+**Table 6.1.3.1-1: Resources and methods overview**
+
+| Resource purpose/name | Resource URI (relative path after API URI) | HTTP method or custom operation | Description (service operation)    |
+|-----------------------|--------------------------------------------|---------------------------------|------------------------------------|
+| NPstatus              | /{gpsi}                                    | GET                             | Retrieve the NP status of the GPSI |
+|                       |                                            |                                 |                                    |
+
+#### 6.1.3.2 Resource: NPstatus
+
+##### 6.1.3.2.1 Description
+
+This resource represents the Number Portability status for a GPSI.
+
+##### 6.1.3.2.2 Resource Definition
+
+Resource URI: {apiRoot}/nmnpf-npstatus/<apiVersion>/{gpsI}
+
+This resource shall support the resource URI variables defined in table 6.1.3.2.2-1.
+
+**Table 6.1.3.2.2-1: Resource URI variables for this resource**
+
+| Name    | Data type | Definition                                               |
+|---------|-----------|----------------------------------------------------------|
+| apiRoot | string    | See clause 6.1.1                                         |
+| gpsI    | Gpsi      | See 3GPP TS 29.571 [15]; the only valid format is MSISDN |
+
+##### 6.1.3.2.3 Resource Standard Methods
+
+###### 6.1.3.2.3.1 GET
+
+This method shall support the URI query parameters specified in table 6.1.3.2.3.1-1.
+
+**Table 6.1.3.2.3.1-1: URI query parameters supported by the GET method on this resource**
+
+| Name | Data type | P | Cardinality | Description | Applicability |
+|------|-----------|---|-------------|-------------|---------------|
+| n/a  |           |   |             |             |               |
+
+This method shall support the request data structures specified in table 6.1.3.2.3.1-2 and the response data structures and response codes specified in table 6.1.3.2.3.1-3.
+
+**Table 6.1.3.2.3.1-2: Data structures supported by the GET Request Body on this resource**
+
+| Data type | P | Cardinality | Description |
+|-----------|---|-------------|-------------|
+| n/a       |   |             |             |
+
+**Table 6.1.3.2.3.1-3: Data structures supported by the GET Response Body on this resource**
+
+| Data type                                                                                                                 | P | Cardinality | Response codes | Description                                                                                                |
+|---------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|------------------------------------------------------------------------------------------------------------|
+| NpStatusInfo                                                                                                              | M | 1           | 200 OK         | Upon success, the response body contains the Number Portability Status information.                        |
+| ProblemDetails                                                                                                            | O | 0..1        | 404 Not Found  | The "cause" attribute may be used to indicate one of the following application errors:<br>- GPSI NOT_FOUND |
+| NOTE: The mandatory HTTP error status code for the GET method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply. |   |             |                |                                                                                                            |
+
+### 6.1.4 Custom Operations without associated resources
+
+None.
+
+### 6.1.5 Notifications
+
+None.
+
+### 6.1.6 Data Model
+
+#### 6.1.6.1 General
+
+This clause specifies the application data model supported by the API.
+
+Table 6.1.6.1-1 specifies the data types defined for the Nmnpf\_NPStatus service based interface protocol.
+
+**Table 6.1.6.1-1: Nmnpf\_NPStatus specific Data Types**
+
+| Data type    | Clause defined | Description                           | Applicability |
+|--------------|----------------|---------------------------------------|---------------|
+| NpStatusInfo | 6.1.6.2.2      | Number Portability Status Information |               |
+
+Table 6.1.6.1-2 specifies data types re-used by the Nmnpf\_NPStatus 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 Nmnpf\_NPStatus service based interface.
+
+**Table 6.1.6.1-2: Nmnpf\_NPStatus re-used Data Types**
+
+| Data type      | Reference           | Comments                               | Applicability |
+|----------------|---------------------|----------------------------------------|---------------|
+| Gpsi           | 3GPP TS 29.571 [15] | General Public Subscription Identifier |               |
+| ProblemDetails | 3GPP TS 29.571 [15] | Error description                      |               |
+| PlmnId         | 3GPP TS 29.571 [15] | PLMN Identity                          |               |
+
+#### 6.1.6.2 Structured data types
+
+##### 6.1.6.2.1 Introduction
+
+This clause defines the structures to be used in resource representations.
+
+##### 6.1.6.2.2 Type: NpStatusInfo
+
+**Table 6.1.6.2.2-1: Definition of type NpStatusInfo**
+
+| Attribute name      | Data type | P | Cardinality | Description                               | Applicability |
+|---------------------|-----------|---|-------------|-------------------------------------------|---------------|
+| subscriptionNetwork | PlmnId    | M | 1           | Identifies the GPSI's subscriptionNetwork |               |
+| tbc                 |           |   |             |                                           |               |
+
+#### 6.1.6.3 Simple data types and enumerations
+
+##### 6.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.
+
+##### 6.1.6.3.2 Simple data types
+
+The simple data types defined in table 6.1.6.3.2-1 shall be supported.
+
+**Table 6.1.6.3.2-1: Simple data types**
+
+| Type Name | Type Definition | Description | Applicability |
+|-----------|-----------------|-------------|---------------|
+|           |                 |             |               |
+
+#### 6.1.6.4 Data types describing alternative data types or combinations of data types
+
+None.
+
+#### 6.1.6.5 Binary data
+
+None.
+
+### 6.1.7 Error Handling
+
+#### 6.1.7.1 General
+
+For the Nnmpf\_NPStatus 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 Nnmpf\_NPStatus API.
+
+#### 6.1.7.2 Protocol Errors
+
+Protocol errors handling shall be supported as specified in clause 5.2.7 of 3GPP TS 29.500 [4].
+
+#### 6.1.7.3 Application Errors
+
+The application errors defined for the Nnmpf\_NPStatus service are listed in Table 6.1.7.3-1.
+
+**Table 6.1.7.3-1: Application errors**
+
+| Application Error | HTTP status code | Description |
+|-------------------|------------------|-------------|
+|                   |                  |             |
+
+### 6.1.8 Feature negotiation
+
+The optional features in table 6.1.8-1 are defined for the Nnmpf\_NPStatus API. They shall be negotiated using the extensibility mechanism defined in clause 6.6 of 3GPP TS 29.500 [4].
+
+**Table 6.1.8-1: Supported Features**
+
+| Feature number | Feature Name | Description |
+|----------------|--------------|-------------|
+|                |              |             |
+
+### 6.1.9 Security
+
+As indicated in 3GPP TS 33.501 [8] and 3GPP TS 29.500 [4], the access to the Nnmpf\_NPStatus 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 Nnmpf\_NPStatus 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 Nnmpf\_NPStatus service.
+
+The Nnmpf\_NPStatus API defines a single scope "nnmpf-npstatus" for the entire service, and it does not define any additional scopes at resource or operation level.
+
+# Annex A (normative): OpenAPI specification
+
+## A.1 General
+
+This Annex specifies the formal definition of the API(s) defined in the present specification. It consists of OpenAPI specifications in YAML format.
+
+This Annex takes precedence when being discrepant to other parts of the specification with respect to the encoding of information elements and methods within the API(s).
+
+NOTE 1: The semantics and procedures, as well as conditions, e.g. for the applicability and allowed combinations of attributes or values, not expressed in the OpenAPI definitions but defined in other parts of the specification also apply.
+
+Informative copies of the OpenAPI specification files contained in this 3GPP Technical Specification are available on a Git-based repository that uses the GitLab software version control system (see clause 5.3.1 of 3GPP TS 29.501 [5] and clause 5B of 3GPP TR 21.900 [7]).
+
+## A.2 Nmnpf\_NPStatus API
+
+```
+openapi: 3.0.0
+info:
+  title: 'Nmnpf_NPStatus'
+  version: '1.1.0-alpha.1'
+  description: |
+    Nmnpf Number Portability Status Service.
+    © 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+    All rights reserved.
+externalDocs:
+  description: 3GPP TS 29.578 V18.0.0; Mobile Number Portability Services.
+  url: https://www.3gpp.org/ftp/Specs/archive/29_series/29.578/
+servers:
+  - url: '{apiRoot}/nmnpf-npstatus/v1'
+    variables:
+      apiRoot:
+        default: https://example.com
+        description: apiRoot as defined in clause 4.4 of 3GPP TS 29.501
+security:
+  - {}
+  - oAuth2ClientCredentials:
+    - nmnpf-npstatus
+paths:
+  /{gpsi}:
+    get:
+      summary: Retrieves the Number Portability status of the UE
+      operationId: GetNumberPortabilityStatus
+      tags:
+        - Number Portability Status (Document)
+      parameters:
+        - name: gpsi
+          in: path
+          description: GPSI of the UE
+          required: true
+          schema:
+            $ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi'
+      responses:
+        '200':
+          description: Expected response to a valid request
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/NpStatusInfo'
+        '400':
+          $ref: 'TS29571_CommonData.yaml#/components/responses/400'
+```
+
+```
+'401':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/401'
+'403':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/403'
+'404':
+  description: GPSI Not Found
+  content:
+    application/problem+json:
+      schema:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/ProblemDetails'
+'406':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/406'
+'429':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/429'
+'500':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/500'
+'502':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/502'
+'503':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/503'
+default:
+  description: Unexpected error
+
+components:
+  securitySchemes:
+    oAuth2ClientCredentials:
+      type: oauth2
+      flows:
+        clientCredentials:
+          tokenUrl: '{nrfApiRoot}/oauth2/token'
+          scopes:
+            nmnpf-npstatus: Access to the nmnpf-npstatus API
+  schemas:
+
+# COMPLEX TYPES:
+
+  NpStatusInfo:
+    description: Contains the Subscription Network
+    type: object
+    required:
+      - subscriptionNetwork
+    properties:
+      subscriptionNetwork:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/PlmnId'
+
+# SIMPLE TYPES:
+
+# ENUMS:
+```
+
+# --- Annex B (informative): Withdrawn API versions
+
+## B.1 General
+
+This Annex lists withdrawn API versions of the APIs defined in the present specification. 3GPP TS 29.501 [5] clause 4.3.1.6 describes the withdrawal of API versions.
+
+## --- B.2 Nmnpf\_NPstatus API
+
+The API versions listed in table B.2-1 are withdrawn for the Nmnpf\_NPStatus API.
+
+**Table B.2-1: Withdrawn API versions of the Nmnpf\_NPStatus service**
+
+| API version number | Remarks |
+|--------------------|---------|
+|                    |         |
+
+# Annex C (informative): Change history
+
+| Change history |          |           |      |      |     |                                                                                      |             |
+|----------------|----------|-----------|------|------|-----|--------------------------------------------------------------------------------------|-------------|
+| Date           | Meeting  | TDoc      | CR   | Re v | Cat | Subject/Comment                                                                      | New version |
+| 2022-02        | CT4#108e | C4-221536 |      |      |     | Initial draft                                                                        | 0.1.0       |
+| 2022-04        | CT4#109e | C4-222270 |      |      |     | Pseudo-CR on SCP and NRF supported                                                   | 0.2.0       |
+| 2022-05        | CT4#110e | C4-223092 |      |      |     | Pseudo-CR on MNPF name                                                               | 0.3.0       |
+| 2022-05        | CT4#110e | C4-223093 |      |      |     | Pseudo-CR on Document Clean Up                                                       | 0.3.0       |
+| 2022-05        | CT4#110e | C4-223354 |      |      |     | Pseudo-CR on Remove the apiVersion placeholder from the resource URI variables table | 0.3.0       |
+| 2022-06        | CT#96    | CP-221079 |      |      |     | TS presented for information and approval                                            | 1.0.0       |
+| 2022-06        | CT#96    | CP-221079 |      |      |     | TS approved at CT#95                                                                 | 17.0.0      |
+| 2022-09        | CT#97e   | CP-222027 | 0003 |      | F   | Alignment on the service name used with template                                     | 17.1.0      |
+| 2022-09        | CT#97e   | CP-222027 | 0004 | 1    | F   | Update the reference model                                                           | 17.1.0      |
+| 2022-12        | CT#98e   | CP-223027 | 0006 | 1    | F   | Missing Mandatory Status Codes in OpenAPI                                            | 18.0.0      |
+| 2022-12        | CT#98e   | CP-223033 | 0007 |      | F   | 29.578 Rel-18 API version and External doc update                                    | 18.0.0      |
+| 2023-12        | CT#102   | CP-233028 | 0008 | 1    | F   | HTTP RFCs obsoleted by IETF RFC 9110, 9111 and 9113                                  | 18.1.0      |
+| 2023-12        | CT#102   | CP-233029 | 0009 |      | F   | ProblemDetails RFC 7807 obsoleted by 9457                                            | 18.1.0      |

gsma/29_series/29579/raw.md

@@ -0,0 +1,878 @@
+
+
+# 3GPP TS 29.579 V18.3.0 (2023-12)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Interworking MSC For Short Message Services; Stage 3 (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'G' has a red signal wave icon below it.
+
+3GPP logo
+
+A GLOBAL INITIATIVE
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                          |    |
+|------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                           | 5  |
+| 1 Scope.....                                                                             | 7  |
+| 2 References.....                                                                        | 7  |
+| 3 Definitions and abbreviations .....                                                    | 8  |
+| 3.1 Definitions.....                                                                     | 8  |
+| 3.2 Abbreviations .....                                                                  | 8  |
+| 4 Overview.....                                                                          | 8  |
+| 4.1 Introduction .....                                                                   | 8  |
+| 5 Services offered by the SMS-IWMSC.....                                                 | 8  |
+| 5.1 Introduction .....                                                                   | 8  |
+| 5.2 Niwmsc_SMService Service.....                                                        | 9  |
+| 5.2.1 Service Description .....                                                          | 9  |
+| 5.2.2 Service Operations.....                                                            | 9  |
+| 5.2.2.1 Introduction.....                                                                | 9  |
+| 5.2.2.2 MoForwardSm .....                                                                | 9  |
+| 5.2.2.2.1 General .....                                                                  | 9  |
+| 5.2.2.2.2 SBI-based MO SM transfer.....                                                  | 9  |
+| 6 API Definitions .....                                                                  | 10 |
+| 6.1 Niwmsc_SMService Service API .....                                                   | 10 |
+| 6.1.1 Introduction .....                                                                 | 10 |
+| 6.1.2 Usage of HTTP.....                                                                 | 10 |
+| 6.1.2.1 General.....                                                                     | 10 |
+| 6.1.2.2 HTTP standard headers.....                                                       | 10 |
+| 6.1.2.2.1 General .....                                                                  | 10 |
+| 6.1.2.2.2 Content type .....                                                             | 10 |
+| 6.1.2.3 HTTP custom headers.....                                                         | 11 |
+| 6.1.2.4 HTTP multipart messages.....                                                     | 11 |
+| 6.1.3 Resources.....                                                                     | 11 |
+| 6.1.3.1 Overview.....                                                                    | 11 |
+| 6.1.3.2 Resource: MoSmInfo.....                                                          | 12 |
+| 6.1.3.2.1 Description .....                                                              | 12 |
+| 6.1.3.2.2 Resource Definition.....                                                       | 12 |
+| 6.1.3.2.3 Resource Standard Methods.....                                                 | 12 |
+| 6.1.3.2.4 Resource Custom Operations.....                                                | 13 |
+| 6.1.4 Custom Operations without associated resources .....                               | 15 |
+| 6.1.5 Notifications .....                                                                | 15 |
+| 6.1.6 Data Model .....                                                                   | 15 |
+| 6.1.6.1 General.....                                                                     | 15 |
+| 6.1.6.2 Structured data types.....                                                       | 15 |
+| 6.1.6.3 Simple data types and enumerations.....                                          | 16 |
+| 6.1.6.3.1 Introduction .....                                                             | 16 |
+| 6.1.6.3.2 Simple data types .....                                                        | 16 |
+| 6.1.6.4 Data types describing alternative data types or combinations of data types ..... | 16 |
+| 6.1.6.5 Binary data.....                                                                 | 16 |
+| 6.1.6.5.1 Binary Data Types.....                                                         | 16 |
+| 6.1.6.5.2 SMS Payload Information.....                                                   | 16 |
+| 6.1.7 Error Handling.....                                                                | 16 |
+| 6.1.7.1 General.....                                                                     | 16 |
+| 6.1.7.2 Protocol Errors .....                                                            | 16 |
+| 6.1.7.3 Application Errors.....                                                          | 16 |
+| 6.1.8 Feature negotiation .....                                                          | 17 |
+| 6.1.9 Security.....                                                                      | 17 |
+| 6.1.10 HTTP redirection.....                                                             | 17 |
+
+**Annex A (normative): OpenAPI specification ..... 18**  
+A.1 General..... 18  
+A.2 Niwmsc\_SMService API..... 18  
+**Annex B (informative): Withdrawn API versions ..... 20**  
+B.1 General..... 20  
+B.2 Niwmsc\_SMService API..... 20  
+**Annex C (informative): Change history..... 21**
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# 1 Scope
+
+The present document specifies the stage 3 protocol and data model for the Niwmsc Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the SMS-IWMSC.
+
+The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
+
+The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5].
+
+Stage 2 requirements for the Niwmsc services are specified in 3GPP TS 23.540 [14].
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
+- [3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
+- [4] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
+- [5] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
+- [6] OpenAPI: "OpenAPI Specification Version 3.0.0", <https://spec.openapis.org/oas/v3.0.0>.
+- [7] 3GPP TR 21.900: "Technical Specification Group working methods".
+- [8] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
+- [9] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
+- [10] 3GPP TS 29.510: "5G System; Network Function Repository Services; Stage 3".
+- [11] IETF RFC 9113: "HTTP/2".
+- [12] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
+- [13] IETF RFC 9457: "Problem Details for HTTP APIs".
+- [14] 3GPP TS 23.540: "Technical realization of Service Based Short Message Service; Stage 2".
+- [15] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces Stage 3".
+- [16] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)".
+- [17] 3GPP TS 29.577: "5G System; IP Short Message Gateway and SMS Router For Short Message Service; Stage 3".
+- [18] 3GPP TS 24.011: " Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface".
+
+# 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**Niwmsc:** Service-based interface exhibited by the SMS-IWMSC
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|       |                                 |
+|-------|---------------------------------|
+| SM MO | Short Message Mobile Originated |
+|-------|---------------------------------|
+
+# 4 Overview
+
+## 4.1 Introduction
+
+The SMS-IWMSC offers services to the SMSF via the Niwmsc service based interface (see 3GPP TS 23.501 [2], 3GPP TS 23.502 [3], and 3GPP TS 23.540 [14]).
+
+Figure 4.1-1 provides the reference model (in service based interface representation and in reference point representation), with focus on the SMS-IWMSC.
+
+![Reference model diagram showing SMSF connected to SMS-IWMSC via SM10 interface and Niwmsc service-based interface.](18f841ac4f2ef28f34a026f1bdc5af9a_img.jpg)
+
+The diagram illustrates the reference model for the SMS-IWMSC. On the left, a white rectangular box is labeled 'SMSF'. A horizontal line, representing the SM10 interface, connects this box to a green rectangular box on the right labeled 'SMS-IWMSC'. The connection point on the SMS-IWMSC side is marked with a small circle and labeled 'Niwmsc', indicating the service-based interface.
+
+Reference model diagram showing SMSF connected to SMS-IWMSC via SM10 interface and Niwmsc service-based interface.
+
+**Figure 4.1-1: Reference model – SMS-IWMSC**
+
+The functionalities supported by the SMS-IWMSC are listed in clause 6.3 of 3GPP TS 23.540 [14].
+
+# 5 Services offered by the SMS-IWMSC
+
+## 5.1 Introduction
+
+The SMS-IWMSC offers the following services via the Niwmsc interface:
+
+- Niwmsc\_SMService 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 |
+|------------------|--------|---------------------------------|-------------------------------|-------------------|-------|
+| Niwmsc_SMService | 6.1    | SMS-IWMSC short message service | TS29579_Niwmsc_SMService.yaml | niwmsc-smbservice | A.2   |
+
+## 5.2 Niwmsc\_SMService Service
+
+### 5.2.1 Service Description
+
+See 3GPP TS 23.540 [14] clause 6.3.1
+
+### 5.2.2 Service Operations
+
+#### 5.2.2.1 Introduction
+
+For the Niwmsc\_SMService service the following service operations are defined:
+
+- MoForwardSm
+
+The Niwmsc\_SMService Service is used by Consumer NFs (SMSF) to transfer MO short message by means of the MoForwardSm service operation.
+
+#### 5.2.2.2 MoForwardSm
+
+##### 5.2.2.2.1 General
+
+This clause provides a general description of the MoForwardSm service operation.
+
+##### 5.2.2.2.2 SBI-based MO SM transfer
+
+The MoForwardSm service operation shall be used to transmit uplink SMS message via SMS-IWMSC.
+
+It is used in the following procedures:
+
+- Successful Mobile Originated short message transfer via SMS-IWMSC (see clause 5.2.2 of 3GPP TS 23.540 [14]).
+- Unsuccessful Mobile Originated short message transfer via SMS-IWMSC (see clause 5.2.3 of 3GPP TS 23.540 [14]).
+
+The NF Service Consumer (e.g. SMSF) shall transmit uplink SMS message to the SMS-IWMSC by using the HTTP POST method as shown in Figure 5.2.2.2.1-1.
+
+![Sequence diagram showing SBI-based MO SM transfer between NF Service Consumer and SMS-IWMSC.](97a08abb8a43f3f8c6ce347199cd909a_img.jpg)
+
+```
+
+sequenceDiagram
+    participant NF Service Consumer
+    participant SMS-IWMSC
+    Note right of NF Service Consumer: (SMS Data)
+    NF Service Consumer->>SMS-IWMSC: 1. POST ../mo-sm-info/{supi}/sendsms
+    SMS-IWMSC-->>NF Service Consumer: 2a. 200 OK (Delivery Report)
+    SMS-IWMSC-->>NF Service Consumer: 2b. 4xx/5xx (ProblemDetails) or 3xx
+  
+```
+
+The diagram illustrates the interaction between an NF Service Consumer and an SMS-IWMSC. The consumer sends a POST request (step 1) to the SMS-IWMSC, including SMS data. The SMS-IWMSC responds with either a 200 OK (Delivery Report) (step 2a) or a 4xx/5xx (ProblemDetails) or 3xx (step 2b).
+
+Sequence diagram showing SBI-based MO SM transfer between NF Service Consumer and SMS-IWMSC.
+
+**Figure 5.2.2.2.2.1-1: SBI-based MO SM transfer**
+
+1. The NF Service Consumer shall send a POST request to the resource representing the UE's Mobile Originated Short Message Information resource (i.e. .../mo-sm-info/{supi}/sendsmss) of the SMS-IWMSC. The content of the POST request shall contain the SMS message to be sent.
+- 2a. On success, "200 OK" shall be returned with "SmsDeliveryData" object contains the MO SMS Delivery Report in the response body.
+- 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.
+
+# --- 6 API Definitions
+
+## 6.1 Niwmsc\_SMService Service API
+
+### 6.1.1 Introduction
+
+The Niwmsc\_SMService shall use the Niwmsc\_SMService API.
+
+The API URI of the Niwmsc\_SMService 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 "niwmsc-smbservice".
+- The <apiVersion> shall be "v1".
+- The <apiSpecificResourceUriPart> shall be set as described in clause 6.1.3.
+
+### 6.1.2 Usage of HTTP
+
+#### 6.1.2.1 General
+
+HTTP/2, IETF RFC 9113 [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 Niwmsc\_SMService API is contained in Annex A.
+
+#### 6.1.2.2 HTTP standard headers
+
+##### 6.1.2.2.1 General
+
+See clause 5.2.2 of 3GPP TS 29.500 [4] for the usage of HTTP standard headers.
+
+##### 6.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 9457 [13].
+
+Multipart messages shall also be supported (see clause 6.1.2.4) using the content type "multipart/related", comprising:
+
+- one JSON body part with the "application/json" content type; and
+- one binary body part with 3gpp vendor specific content subtypes.
+
+The 3gpp vendor specific content subtypes defined in Table 6.1.2.2.2-1 shall be supported.
+
+**Table 6.1.2.2.2-1: 3GPP vendor specific content subtypes**
+
+| content subtype | Description                                                                                                                                                       |
+|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| vnd.3gpp.sms    | Binary encoded payload, encoding SMS payload, as specified in 3GPP TS 23.040 [16] and 3GPP TS 24.011 [17].                                                        |
+| NOTE:           | Using 3GPP vendor content subtypes allows to describe the nature of the opaque payload (e.g. SMS payload) without having to rely on metadata in the JSON content. |
+
+See clause 6.1.2.4 for the binary payloads supported in the binary body part of multipart messages.
+
+#### 6.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.
+
+#### 6.1.2.4 HTTP multipart messages
+
+HTTP multipart messages shall be supported, to transfer opaque SMS payload (e.g. SMS message, CP Ack, etc.), in the following service operations (and HTTP messages):
+
+- MoForwardSm service operation;
+
+HTTP multipart messages shall include one JSON body part and one binary body part comprising content of SMS payload content (see clause 6.1.6.5).
+
+The JSON body part shall be the "root" body part of the multipart message. It shall be encoded as the first body part of the multipart message. The "Start" parameter does not need to be included.
+
+The multipart message shall include a "type" parameter (see IETF RFC 2387 [18]) specifying the media type of the root body part, i.e. "application/json".
+
+NOTE: The "root" body part (or "root" object) is the first body part the application processes when receiving a multipart/related message, see IETF RFC 2387 [18]. The default root is the first body within the multipart/related message. The "Start" parameter indicates the root body part, e.g. when this is not the first body part in the message.
+
+A binary body part shall include a Content-ID header (see IETF RFC 2045 [19]), and the JSON body part shall make a reference to the binary body part using the Content-ID header field.
+
+Examples of multipart/related messages can be found in Annex B.
+
+### 6.1.3 Resources
+
+#### 6.1.3.1 Overview
+
+This clause describes the structure for the Resource URIs and the resources and methods used for the service.
+
+Figure 6.1.3.1-1 depicts the resource URIs structure for the Niwmse\_SMSService API.
+
+![Diagram showing the hierarchical structure of the Niwmsc_SMSService API URI. The root is {apiRoot}/niwmsc_smbservice/<apiVersion>. It branches to /mo-sm-info, which branches to /{supi}, which branches to /send sms (dashed box).](27b06ec9f42b5d727a2630f61a5f1861_img.jpg)
+
+{apiRoot}/niwmsc\_smbservice/<apiVersion>
+
+```
+
+graph TD
+    Root["{apiRoot}/niwmsc_smbservice/<apiVersion>"] --> MoSmInfo["/mo-sm-info"]
+    MoSmInfo --> Supi["/{supi}"]
+    Supi --> SendSms["/send sms"]
+    style SendSms stroke-dasharray: 5 5
+  
+```
+
+Diagram showing the hierarchical structure of the Niwmsc\_SMSService API URI. The root is {apiRoot}/niwmsc\_smbservice/. It branches to /mo-sm-info, which branches to /{supi}, which branches to /send sms (dashed box).
+
+**Figure 6.1.3.1-1: Resource URI structure of the Niwmsc\_SMSService API**
+
+Table 6.1.3.1-1 provides an overview of the resources and applicable HTTP methods.
+
+**Table 6.1.3.1-1: Resources and methods overview**
+
+| Resource purpose/name | Resource URI (relative path after API URI) | HTTP method or custom operation | Description (service operation) |
+|-----------------------|--------------------------------------------|---------------------------------|---------------------------------|
+| SMSService            | /mo-sm-info/{supi}/send sms                | send sms (POST)                 | MO short message transfer       |
+|                       |                                            |                                 |                                 |
+|                       |                                            |                                 |                                 |
+|                       |                                            |                                 |                                 |
+|                       |                                            |                                 |                                 |
+
+#### 6.1.3.2 Resource: MoSmInfo
+
+##### 6.1.3.2.1 Description
+
+This resource represents the collection of Mobile Originated Short Message Information in SMS-IWMSC.
+
+This resource is modelled with the Document resource archetype (see clause C.1 of 3GPP TS 29.501 [5]).
+
+##### 6.1.3.2.2 Resource Definition
+
+Resource URI: {apiRoot}/<apiName>/<apiVersion>/mo-sm-info{supi}
+
+This resource shall support the resource URI variables defined in table 6.1.3.2.2-1.
+
+**Table 6.1.3.2.2-1: Resource URI variables for this resource**
+
+| Name    | Data type | Definition                                                                                                                                         |
+|---------|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------|
+| apiRoot | string    | See clause 6.1.1                                                                                                                                   |
+| supi    | Supi      | Represents the Subscription Permanent Identifier (see 3GPP TS 23.501 [2] clause 5.9.2)<br>pattern: See pattern of type Supi in 3GPP TS 29.571 [15] |
+
+##### 6.1.3.2.3 Resource Standard Methods
+
+No HTTP method has been defined for the Mobile Originated Short Message Information collection resource.
+
+##### 6.1.3.2.4 Resource Custom Operations
+
+###### 6.1.3.2.4.1 Overview
+
+**Table 6.1.3.2.4.1-1: Custom operations**
+
+| Operation name | Custom operation URI        | Mapped HTTP method | Description                                         |
+|----------------|-----------------------------|--------------------|-----------------------------------------------------|
+| sendsms        | /mo-sm-infos/{supi}/sendsms | POST               | Send MO SMS message or the related Delivery Report. |
+
+###### 6.1.3.2.4.2 Operation: sendsms
+
+###### 6.1.3.2.4.2.1 Description
+
+This custom operation is used for NF Service Consumers to send SMS message in uplink direction.
+
+###### 6.1.3.2.4.2.2 Operation Definition
+
+This custom operation is used to send a SMS payload to an UE's Mobile Originated Short Message Information resource in the SMS-IWMSC.
+
+This operation shall support the request data structures specified in table 6.1.3.2.4.2.2-1 and the response data structure and response codes specified in table 6.1.3.2.4.2.2-2.
+
+**Table 6.1.3.2.4.2.2-1: Data structures supported by the POST Request Body on this resource**
+
+| Data type | P | Cardinality | Description                                      |
+|-----------|---|-------------|--------------------------------------------------|
+| SmsData   | M | 1           | Representation of the MO SMS message to be sent. |
+
+**Table 6.1.3.2.4.2.2-2: Data structures supported by the POST Response Body on this resource**
+
+| Data type        | P | Cardinality | Response codes         | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|------------------|---|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| SmsDeliveryData  | M | 1           | 200 OK                 | This case represents the successful of sending SMS message in uplink direction, with necessary response data on the received delivery report.                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| RedirectResponse | O | 0..1        | 307 Temporary Redirect | Temporary redirection. (NOTE 2)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| RedirectResponse | O | 0..1        | 308 Permanent Redirect | Permanent redirection. (NOTE 2)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| ProblemDetails   | O | 0..1        | 400 Bad Request        | This case represents an unsuccessful delivery of SMS message.<br>The "cause" attribute may be used to indicate one of the following application errors: <ul style="list-style-type: none"> <li>- SMS_PAYLOAD_MISSING, if the expected SMS payload content is missing;</li> <li>- SMS_PAYLOAD_ERROR, if error exists in the SMS payload content.</li> </ul>                                                                                                                                                                                                    |
+| ProblemDetails   | O | 0..1        | 403 Forbidden          | This case represents an unsuccessful delivery of SMS message.<br>The "cause" attribute may be used to indicate one of the following application errors: <ul style="list-style-type: none"> <li>- UNKNOWN_SERVICE_CENTRE_ADDRESS, if the SMS-SC was unknown;</li> <li>- SERVICE_CENTRE_CONGESTION, if the SMS-SC was in congestion;</li> <li>- USER_NOT_SERVICE_CENTER, if the user didn't belongs to the SMS-SC;</li> <li>- FACILITY_NOT_SUPPORTED, if the facility not supported;</li> <li>- INVALID_SME_ADDRESS, if the SME address is invalid..</li> </ul> |
+| ProblemDetails   | O | 0..1        | 504 Gateway Timeout    | This case represents an unsuccessful delivery of SMS message.<br>The "cause" attribute may be used to indicate one of the following application errors: <ul style="list-style-type: none"> <li>- UNREACHABLE_SMS_SC, if the response is timeout.</li> </ul>                                                                                                                                                                                                                                                                                                   |
+
+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 6.1.3.2.4.2.2-3: 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 on an alternative service instance within the same SMS-IWMSC or SMS-IWMSC (service) set.<br>For the case, when a request is redirected to the same target resource via a different SCP, see clause 6.10.9.1 in 3GPP TS 29.500 [4]. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance ID towards which the request is redirected                                                                                                                                                                                     |
+
+**Table 6.1.3.2.4.2.2-4: 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 on an alternative service instance within the same SMS-IWMSC or SMS-IWMSC (service) set.<br>For the case, when a request is redirected to the same target resource via a different SCP, see clause 6.10.9.1 in 3GPP TS 29.500 [4]. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance ID towards which the request is redirected                                                                                                                                                                                     |
+
+### 6.1.4 Custom Operations without associated resources
+
+In this release of this specification, no custom operations without associated resources are defined.
+
+### 6.1.5 Notifications
+
+In this release of this specification, no notification procedures are defined.
+
+### 6.1.6 Data Model
+
+#### 6.1.6.1 General
+
+This clause specifies the application data model supported by the API.
+
+Table 6.1.6.1-1 specifies the data types defined for the Niwmsc\_SMSService service based interface protocol.
+
+**Table 6.1.6.1-1: Niwmsc\_SMSService specific Data Types**
+
+| Data type | Clause defined | Description | Applicability |
+|-----------|----------------|-------------|---------------|
+| N/A       |                |             |               |
+
+Table 6.1.6.1-2 specifies data types re-used by the Niwmsc\_SMSService 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 Niwmsc\_SMSService service based interface.
+
+**Table 6.1.6.1-2: Niwmsc\_SMSService re-used Data Types**
+
+| Data type         | Reference           | Comments                                                                                                           | Applicability |
+|-------------------|---------------------|--------------------------------------------------------------------------------------------------------------------|---------------|
+| ProblemDetails    | 3GPP TS 29.571 [15] | Common Data Type used in response bodies                                                                           |               |
+| RedirectResponse  | 3GPP TS 29.571 [15] | Redirect Response                                                                                                  |               |
+| Supi              | 3GPP TS 29.571 [15] | Subscription Permanent Identifier                                                                                  |               |
+| RefToBinaryData   | 3GPP TS 29.571 [15] | Information for indicating the binary content of SMS payload.                                                      |               |
+| Ipv4Addr          | 3GPP TS 29.571 [15] | IPv4 address                                                                                                       |               |
+| Ipv6Addr          | 3GPP TS 29.571 [15] | IPv6 address                                                                                                       |               |
+| SupportedFeatures | 3GPP TS 29.571 [15] | Supported Features                                                                                                 |               |
+| SmsData           | 3GPP TS 29.577 [17] | Information within request message invoking MoForwardSm service operation, for delivering MO SMS.                  |               |
+| SmsDeliveryData   | 3GPP TS 29.571 [17] | Information within response message invoking MoForwardSm service operation, for delivering MO SMS Delivery Report. |               |
+
+#### 6.1.6.2 Structured data types
+
+In this release of this specification, no structure to be used in resource representations is defined.
+
+#### 6.1.6.3 Simple data types and enumerations
+
+##### 6.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.
+
+##### 6.1.6.3.2 Simple data types
+
+The simple data types defined in table 6.1.6.3.2-1 shall be supported.
+
+**Table 6.1.6.3.2-1: Simple data types**
+
+| Type Name | Type Definition | Description | Applicability |
+|-----------|-----------------|-------------|---------------|
+| N/A       |                 |             |               |
+
+#### 6.1.6.4 Data types describing alternative data types or combinations of data types
+
+None.
+
+#### 6.1.6.5 Binary data
+
+##### 6.1.6.5.1 Binary Data Types
+
+**Table 6.1.6.5.1-1: Binary Data Types**
+
+| Name                    | Clause defined | Content type |
+|-------------------------|----------------|--------------|
+| SMS Payload Information | 6.1.6.4.2      | vnd.3gpp.sms |
+
+##### 6.1.6.5.2 SMS Payload Information
+
+SMS Payload Information shall encode a SMS payload as specified in 3GPP TS 23.040 [16] and 3GPP TS 24.011 [18], using the vnd.3gpp.sms content-type.
+
+SMS Payload Information may encode e.g. the following content:
+
+- CP-DATA, CP-ACK, CP-ERROR as specified in 3GPP TS 23.040 [16] and 3GPP TS 24.011 [18].
+
+### 6.1.7 Error Handling
+
+#### 6.1.7.1 General
+
+For the Niwmsc\_SMService 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 Niwmsc\_SMService API.
+
+#### 6.1.7.2 Protocol Errors
+
+No specific procedures for the Niwmsc\_SMService service are specified.
+
+#### 6.1.7.3 Application Errors
+
+The application errors defined for the Niwmsc\_SMService service are listed in Table 6.1.7.3-1.
+
+**Table 6.1.7.3-1: Application errors**
+
+| Application Error         | HTTP status code    | Description                                                                             |
+|---------------------------|---------------------|-----------------------------------------------------------------------------------------|
+| SMS_PAYLOAD_MISSING       | 400 Bad Request     | The expected SMS payload content is missing.                                            |
+| SMS_PAYLOAD_ERROR         | 400 Bad Request     | Errors exist in the format of SMS payload.                                              |
+| SERVICE_CENTRE_CONGESTION | 403 Forbidden       | The delivery of the MO short message failed because SMS-SC was in congestion.           |
+| USER_NOT_SERVICE_CENTER   | 403 Forbidden       | The delivery of the short message failed because the user didn't belongs to the SMS-SC. |
+| FACILITY_NOT_SUPPORTED    | 403 Forbidden       | The delivery of the MO short message failed because of facility not supported.          |
+| INVALID_SME_ADDRESS       | 403 Forbidden       | The delivery of the MO short message failed because the SME address is invalid.         |
+| UNREACHABLE_SMS_SC        | 504 Gateway Timeout | The delivery of the MO short message failed because the response is timeout.            |
+
+### 6.1.8 Feature negotiation
+
+The optional features in table 6.1.8-1 are defined for the Niwmsc\_SMService API. They shall be negotiated using the extensibility mechanism defined in clause 6.6 of 3GPP TS 29.500 [4].
+
+**Table 6.1.8-1: Supported Features**
+
+| Feature number | Feature Name | Description |
+|----------------|--------------|-------------|
+| N/A            |              |             |
+
+### 6.1.9 Security
+
+As indicated in 3GPP TS 33.501 [8] and 3GPP TS 29.500 [4], the access to the Niwmsc\_SMService 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 Niwmsc\_SMService 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 Niwmsc\_SMService service.
+
+The Niwmsc\_SMService API defines a single scope "niwmsc-smbservice" for the entire service, and it does not define any additional scopes at resource or operation level.
+
+### 6.1.10 HTTP redirection
+
+An HTTP request may be redirected to a different SMS-IWMSC service instance, within the same SMS-IWMSC or a different SMS-IWMSC of an SMS-IWMSC set, e.g. when an SMS-IWMSC service instance is part of an SMS-IWMSC (service) set or when using indirect communications (see 3GPP TS 29.500 [4]).
+
+An SCP that reselects a different SMS-IWMSC producer instance will return the NF Instance ID of the new SMS-IWMSC producer instance in the 3gpp-Sbi-Producer-Id header, as specified in clause 6.10.3.4 of 3GPP TS 29.500 [4].
+
+If an SMS-IWMSC within an SMS-IWMSC set redirects a service request to a different SMS-IWMSC of the set using a 307 Temporary Redirect or 308 Permanent Redirect status code, the identity of the new SMS-IWMSC towards which the service request is redirected shall be indicated in the 3gpp-Sbi-Target-Nf-Id header of the 307 Temporary Redirect or 308 Permanent Redirect response as specified in clause 6.10.9.1 of 3GPP TS 29.500 [4].
+
+# Annex A (normative): OpenAPI specification
+
+## A.1 General
+
+This Annex specifies the formal definition of the API(s) defined in the present specification. It consists of OpenAPI specifications in YAML format.
+
+This Annex takes precedence when being discrepant to other parts of the specification with respect to the encoding of information elements and methods within the API(s).
+
+NOTE 1: The semantics and procedures, as well as conditions, e.g. for the applicability and allowed combinations of attributes or values, not expressed in the OpenAPI definitions but defined in other parts of the specification also apply.
+
+Informative copies of the OpenAPI specification files contained in this 3GPP Technical Specification are available on a Git-based repository that uses the GitLab software version control system (see clause 5.3.1 of 3GPP TS 29.501 [5] and clause 5B of 3GPP TR 21.900 [7]).
+
+## A.2 Niwmsc\_SMService API
+
+```
+openapi: 3.0.0
+info:
+  title: 'Niwmsc_SMService'
+  version: '1.1.0-alpha.2'
+  description: |
+    SMS-IWMSC Short Message Service.
+    © 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+    All rights reserved.
+
+externalDocs:
+  description: 3GPP TS 29.579 V18.1.0; 5G System; SMS Services; Stage 3.
+  url: https://www.3gpp.org/ftp/Specs/archive/29_series/29.579/
+
+servers:
+  - url: '{apiRoot}/niwmsc-smsservice/v1'
+    variables:
+      apiRoot:
+        default: https://example.com
+        description: apiRoot as defined in clause 4.4 of 3GPP TS 29.501
+
+security:
+  - oAuth2ClientCredentials:
+    - niwmsc-smsservice
+  - {}
+
+paths:
+  /mo-sm-infos/{supi}/sendsms:
+    post:
+      summary: Send SMS payload for a given UE
+      operationId: SendSMS
+      tags:
+        - Send MO SMS message and the delivery report
+      parameters:
+        - name: supi
+          in: path
+          required: true
+          description: Subscription Permanent Identifier (SUPI)
+          schema:
+            type: string
+      requestBody:
+        content:
+          multipart/related: # message with a binary body part
+            schema:
+              type: object
+              properties:
+                jsonData:
+                  $ref: '#/components/schemas/SmsData'
+                binaryPayload:
+```
+
+```
+        type: string
+        format: binary
+    encoding:
+      jsonData:
+        contentType: application/json
+      binaryPayload:
+        contentType: application/vnd.3gpp.sms
+      headers:
+        Content-Id:
+          schema:
+            type: string
+    required: true
+  responses:
+    '200':
+      description: sending delivery report
+      content:
+        multipart/related: # message with a binary body part
+          schema:
+            type: object
+            properties:
+              jsonData:
+                $ref: '#/components/schemas/SmsDeliveryData'
+              binaryPayload:
+                type: string
+                format: binary
+            encoding:
+              jsonData:
+                contentType: application/json
+              binaryPayload:
+                contentType: application/vnd.3gpp.sms
+              headers:
+                Content-Id:
+                  schema:
+                    type: string
+    '307':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/307'
+    '308':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/308'
+    '400':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/400'
+    '401':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/401'
+    '403':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/403'
+    '404':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/404'
+    '411':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/411'
+    '413':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/413'
+    '415':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/415'
+    '429':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/429'
+    '500':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/500'
+    '502':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/502'
+    '504':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/504'
+    default:
+      $ref: 'TS29571_CommonData.yaml#/components/responses/default'
+
+components:
+
+  securitySchemes:
+    oAuth2ClientCredentials:
+      type: oauth2
+      flows:
+        clientCredentials:
+          tokenUrl: '{nrfApiRoot}/oauth2/token'
+          scopes:
+            niwmsc-smbservice: Access to the niwmsc-smbservice API
+
+schemas:
+
+  SmsData:
+    description: >
+```
+
+```
+
+    Information within request message invoking MoForwardSm service operation,
+    for delivering MO SMS.
+type: object
+required:
+  - smsPayload
+properties:
+  smsPayload:
+    $ref: 'TS29571_CommonData.yaml#/components/schemas/RefToBinaryData'
+
+SmsDeliveryData:
+  description: >
+    Information within response message invoking MoForwardSm service operation,
+    for delivering MO SMS Delivery Report.
+  type: object
+  required:
+    - smsPayload
+  properties:
+    smsPayload:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/RefToBinaryData'
+
+# COMPLEX TYPES:
+
+# SIMPLE TYPES:
+
+# ENUMS:
+
+```
+
+# --- Annex B (informative): Withdrawn API versions
+
+## B.1 General
+
+This Annex lists withdrawn API versions of the APIs defined in the present specification. 3GPP TS 29.501 [5] clause 4.3.1.6 describes the withdrawal of API versions.
+
+## --- B.2 Niwmsc\_SMService API
+
+The API versions listed in table B.2-1 are withdrawn for the Niwmsc\_SMService API.
+
+**Table B.2-1: Withdrawn API versions of the Niwmsc\_SMService service**
+
+| API version number | Remarks |
+|--------------------|---------|
+|                    |         |
+
+# Annex C (informative): Change history
+
+| Change history |          |           |      |     |     |                                                       |             |
+|----------------|----------|-----------|------|-----|-----|-------------------------------------------------------|-------------|
+| Date           | Meeting  | TDoc      | CR   | Rev | Cat | Subject/Comment                                       | New version |
+| 2022-04        | CT4#109e | C4-222331 |      |     |     | C4-222331 as basis                                    | 0.1.0       |
+| 2022-04        | CT4#109e | C4-222343 |      |     |     | Implementation of C4-222343 in CT4#109e               | 0.2.0       |
+| 2022-05        | CT4#110e | C4-223452 |      |     |     | Implementation of C4-223219 and C4-223224 in CT4#110e | 0.3.0       |
+| 2022-06        | CT#96    | CP-221080 |      |     |     | TS presented for information and approval             | 1.0.0       |
+| 2022-06        | CT#96    | CP-221080 |      |     |     | TS approved at CT#95                                  | 17.0.0      |
+| 2022-09        | CT#97e   | CP-222027 | 0002 | -   | B   | Add 3xx for the service operation                     | 17.1.0      |
+| 2022-09        | CT#97e   | CP-222027 | 0003 | -   | F   | Alignment on the service name used with template      | 17.1.0      |
+| 2022-09        | CT#97e   | CP-222027 | 0004 | -   | F   | Corrections on the table name and NOTE                | 17.1.0      |
+| 2022-09        | CT#97e   | CP-222027 | 0005 | -   | F   | Update on the content type for OpenAPI                | 17.1.0      |
+| 2022-09        | CT#97e   | CP-222027 | 0006 | 1   | F   | Update on the reference model                         | 17.1.0      |
+| 2022-09        | CT#97e   | CP-222058 | 0007 | -   | F   | 29.579 Rel-17 API version and External doc update     | 17.1.0      |
+| 2022-12        | CT#98e   | CP-223028 | 0008 | 1   | F   | Missing Mandatory Status Codes in OpenAPI             | 18.0.0      |
+| 2022-12        | CT#98e   | CP-223033 | 0009 | -   | F   | 29.579 Rel-18 API version and External doc update     | 18.0.0      |
+| 2023-03        | CT#99e   | CP-230073 | 0012 | -   | A   | Rel-18 Niwmsc SMService API HTTP code correction      | 18.0.1      |
+| 2023-03        | CT#99e   | CP-230071 | 0014 | -   | F   | 29.579 Rel-18 API version and External doc update     | 18.0.1      |
+| 2023-03        | CT#99e   | CP-230321 | 0015 | -   | F   | 29.579 Rel-18 API version and External doc update     | 18.1.0      |
+| 2023-06        | CT#99e   | CP-231026 | 0013 | 3   | F   | Location header description                           | 18.2.0      |
+| 2023-12        | CT#102   | CP-233027 | 0017 | -   | F   | HTTP RFCs obsoleted by IETF RFC 9113                  | 18.3.0      |
+| 2023-12        | CT#102   | CP-233028 | 0016 | 1   | F   | HTTP RFCs update in TS 29.579                         | 18.3.0      |
+| 2023-12        | CT#102   | CP-233030 | 0018 | -   | F   | ProblemDetails RFC 7807 obsoleted by 9457             | 18.3.0      |

gsma/29_series/29641/raw.md

@@ -0,0 +1,204 @@
+
+
+# 3GPP TS 29.641 V18.1.0 (2023-06)
+
+*Technical Report*
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 3GPP registry for Service Names and Port Numbers (Release 18)**
+
+![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller text to the right.
+
+5G Advanced logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                                              |          |
+|------------------------------------------------------------------------------|----------|
+| Foreword .....                                                               | 4        |
+| 1 Scope.....                                                                 | 5        |
+| 2 References.....                                                            | 5        |
+| 3 Definitions of terms, symbols and abbreviations.....                       | 5        |
+| 3.1 Terms.....                                                               | 5        |
+| 3.2 Void.....                                                                | 6        |
+| 3.3 Void.....                                                                | 6        |
+| 4 3GPP procedures for Service Name and Port Number registry management ..... | 6        |
+| 4.1 General Principles .....                                                 | 6        |
+| 4.2 3GPP allocated Service Name and Port Number registry.....                | 6        |
+| 5 Port Number Database .....                                                 | 6        |
+| <b>Annex A (informative): Change history.....</b>                            | <b>7</b> |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# --- 1 Scope
+
+The present document defines 3GPP procedures for Service Name and Port Number registry management. These procedures should be followed by 3GPP WGs when requesting new port numbers for the 3GPP allocated port number solution#6, which is specified in clause 4.4 of the 3GPP TR 29.941 [2].
+
+The present document also maintains a database of the 3GPP allocated port numbers.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+
+[2] 3GPP TR 29.941: "Study on Port Number Allocation Alternatives for New 3GPP Interfaces".
+
+# --- 3 Definitions of terms, symbols and abbreviations
+
+## 3.1 Terms
+
+For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+3.2 Void
+
+3.3 Void
+
+# --- 4 3GPP procedures for Service Name and Port Number registry management
+
+## 4.1 General Principles
+
+3GPP CT4 is responsible for the management and maintenance of service name and port number registry from the sub-range of 101 ports from 65400 to 65500. This sub-range belongs to the Dynamic/Private Port range [49152 - 65535] and IANA does not assign port numbers from this range.
+
+Clause 4.4 in 3GPP TR 29.941 [2] specifies solution#6 for 3GPP allocated port numbers. Solution#6 requires 3GPP CT4 to maintain the 3GPP allocated port number repository.
+
+## 4.2 3GPP allocated Service Name and Port Number registry
+
+This clause specifies 3GPP procedure for the port number allocation based on the solution#6 (see clause 4.4 in 3GPP TR 29.941 [2]).
+
+1. If a 3GPP working group decides to utilize 3GPP allocated port number solution#6, the working group shall send an LS request to 3GPP CT4. CT4 accepts the request if it addresses the following matters (checklist):
+  - a. The request should be for a protocol, which is supported by intra-domain interface(s).
+  - b. The request should indicate that the request cannot meet IANA/IETF requirements for the port number allocation (see Annex C in 3GPP TR 29.941 [2]).
+  - c. The request should indicate that solution#6 is preferable and selected after evaluating other solutions specified in 3GPP TR 29.941 [2].
+2. LS request to 3GPP CT4 shall also contain the following information:
+  - a. The service name, e.g. x2-ctrl.
+  - b. Applicable transport protocol(s).
+  - c. Short description, e.g. X2-CP.
+  - d. A statement that the new port number will be used across intra-domain interface <name> between nodes <name> and <name>.
+  - e. Work Item Code (WIC) used by the request sender (both the abbreviation and the numerical value).
+3. 3GPP CT4 shall inform the 3GPP WG that has requested new port number allocation and also may inform other, relevant 3GPP WGs about the decision. 3GPP CT4 creates respective CR. If CT plenary approves the CR, then the assigned port number will be added to the Table 5-1 (see clause 5).
+
+# --- 5 Port Number Database
+
+Table 5-1 represents 3GPP allocated service name and port number registry of 101 ports from 65400 to 65500. 3GPP CT4 maintains the repository.
+
+Table 5-1: Service Name/port number assigned by 3GPP
+
+| Service Name | Port Number | Transport Protocol | Description  | Inter/Intra interface between entities             | Requesting WG | Registration Date |
+|--------------|-------------|--------------------|--------------|----------------------------------------------------|---------------|-------------------|
+| SLMP         | 65400       | UDP                | SLM-C-CP     | Inter SLM-C hosted UEs                             | CT1           | 2023-06 (CT#100)  |
+| MSGin5GMD    | 65401       | UDP                | MSGin5GMD-UP | Inter MSGin5G Client to MSGin5G Server (MSGin5G-1) | CT1           | 2023-06 (CT#100)  |
+
+# Annex A (informative): Change history
+
+| Change history |              |           |      |     |     |                                                                      |             |
+|----------------|--------------|-----------|------|-----|-----|----------------------------------------------------------------------|-------------|
+| Date           | Meeting      | TDoc      | CR   | Rev | Cat | Subject/Comment                                                      | New version |
+| 2022-01        | CT4#107e-bis | C4-220265 |      |     |     | Skeleton                                                             | 0.0.0       |
+| 2022-01        | CT4#107e-bis | C4-220458 |      |     |     | Following tdocs are implemented: C4-220287, C4-220288 and C4-220289. | 0.1.0       |
+| 2022-02        | CT4#108e     | C4-221587 |      |     |     | Spec number was assigned.                                            | 0.2.0       |
+| 2022-03        | CT#95e       | CP-220103 |      |     |     | TS presented for information and approval                            | 1.0.0       |
+| 2022-03        | CT#95e       |           |      |     |     | TS approved                                                          | 17.0.0      |
+| 2022-06        | CT#96        | CP-221026 | 0001 | -   | D   | Editorial corrections                                                | 17.1.0      |
+| 2022-09        | CT#97e       | CP-222033 | 0002 | -   | F   | Correcting references                                                | 17.2.0      |
+| 2023-03        | CT#99        | CP-230058 | 0003 | 1   | B   | Allocating new port number                                           | 18.0.0      |
+| 2023-06        | CT#100       | CP-231062 | 0004 | -   | B   | New UDP port number for the SLMP                                     | 18.1.0      |
+| 2023-06        | CT#100       | CP-231062 | 0005 | 3   | B   | New port number for MSGin5G service                                  | 18.1.0      |