Add files using upload-large-folder tool

marked/Rel-18/29_series/29013/raw.md

@@ -0,0 +1,770 @@
+
+
+# 3GPP TS 29.013 V18.0.0 (2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Signalling interworking between ISDN supplementary services; Application Service Element (ASE) and Mobile Application Part (MAP) protocols (Release 18)**
+
+![GSMA logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+**GLOBAL SYSTEM FOR  
+MOBILE COMMUNICATIONS**
+
+GSMA logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+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.
+
+© 2024, 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.....                                                              | 4         |
+| 2 References.....                                                         | 4         |
+| 3 Definitions and abbreviations .....                                     | 5         |
+| 3.1 Definitions.....                                                      | 5         |
+| 3.2 Abbreviations .....                                                   | 5         |
+| 4 General.....                                                            | 6         |
+| 4.1 GSM CCBS Architecture Overview .....                                  | 6         |
+| 4.2 GSM CCBS - ISDN CCBS ASE Interworking Overview .....                  | 7         |
+| 4.3 Overview on the use of CCBS procedures and parameters values .....    | 8         |
+| 4.4 Mapping between MAP and SSAP application layer messages .....         | 8         |
+| 4.4.1 MAP D-interface to SSAP interface mapping in HLR A.....             | 8         |
+| 4.4.2 SSAP interface to MAP D-interface interface mapping in HLR A.....   | 8         |
+| 5 Mapping between MAP message parameters and SSAP message parameters..... | 9         |
+| 5.1 CCBS Request Invocation.....                                          | 9         |
+| 5.1.1 Encoding of called party subaddress information .....               | 11        |
+| 5.2 CCBS Request Result.....                                              | 11        |
+| 5.3 CCBS Request Error .....                                              | 12        |
+| 6 Dialogue handling on the SSAP interface.....                            | 13        |
+| 6.1 Dialogue Beginning.....                                               | 13        |
+| 6.1.1 CCBS Request Invocation.....                                        | 13        |
+| 6.2 Dialogue Continuation .....                                           | 13        |
+| 6.2.1 CCBS Request Result.....                                            | 13        |
+| 6.2.2 CCBS Remote User Free Invocation.....                               | 14        |
+| 6.2.3 CCBS Suspend Invocation .....                                       | 14        |
+| 6.2.4 CCBS Resume Invocation.....                                         | 15        |
+| 6.3 Dialogue End.....                                                     | 15        |
+| 6.3.1 Normal dialogue end .....                                           | 15        |
+| 6.3.2 CCBS Cancel Invocation (from A-side).....                           | 16        |
+| 6.3.3 CCBS Cancel Invocation (from B-side).....                           | 16        |
+| 6.3.4 CCBS Request Error.....                                             | 17        |
+| 7 Addressing of SCCP layer messages on the SSAP interface.....            | 17        |
+| 7.1 Use of SCCP.....                                                      | 17        |
+| 7.2 Addressing of messages at the originating PLMN.....                   | 17        |
+| 7.2.1 TC-BEGIN message from the originating network HLR.....              | 17        |
+| 7.2.2 TC-CONTINUE, TC-END messages from the originating network HLR ..... | 18        |
+| 7.3 Addressing of messages at the destination PLMN.....                   | 18        |
+| 7.3.1 TC-CONTINUE, TC-END messages from the destination network HLR ..... | 18        |
+| 7.4 Number formats of the SCCP address parameters.....                    | 19        |
+| 7.4.1 Originating PLMN.....                                               | 19        |
+| 7.4.2 Destination PLMN.....                                               | 19        |
+| <b>Annex A (informative): Change history.....</b>                         | <b>20</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3GPP.
+
+This TS provides a detailed specification for interworking between the ISDN Supplementary Services ASE protocol and the Mobile Application Part (MAP) D interface protocol for handling of supplementary services within the 3GPP system.
+
+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 this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version 3.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 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 specification;
+
+# --- 1 Scope
+
+The scope of the present document is to provide a specification for interworking between the ISDN Application Service Element (ASE) protocol for supplementary services and the Mobile Application Part (MAP) protocol on MAP D-interface protocol for handling of supplementary services within the digital cellular telecommunications system (Phase 2+). This version of the specification includes the interworking for the Call Completion to Busy Subscriber (CCBS) service between the ISDN CCBS-ASE and MAP.
+
+The MAP protocol for CCBS service is specified in GSM 09.02. The ISDN CCBS-ASE protocol is specified in ETS 300 356-18. The ISDN CCBS-ASE protocol is also commonly referred to as the SSAP protocol in GSM 03.93. This specification clarifies the interworking within the HLR between these protocols for the Call Completion to Busy Subscriber (CCBS) service.
+
+Clause 4 describes the mapping between MAP application layer messages and SSAP application layer messages.
+
+Clause 5 describes the mapping between MAP message parameters and SSAP message parameters.
+
+Clause 6 describes the dialogue handling on the SSAP interface.
+
+Clause 7 describes the SCCP layer addressing for messages on the SSAP interface.
+
+# --- 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.
+- [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
+- [2] GSM 02.93: "Digital cellular telecommunications system (Phase 2+); Completion of calls to busy subscriber (CCBS) supplementary services - Stage 1".
+- [3] GSM 03.93: "Digital cellular telecommunications system (Phase 2+); Technical Realisation of Completion of Calls to Busy Subscriber (CCBS); Stage 2".
+- [4] GSM 04.80: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification Formats and coding".
+- [5] GSM 04.93: "Digital cellular telecommunications system (Phase 2+); Technical Realisation of Completion of Calls to Busy Subscriber (CCBS); Stage 3".
+- [6] GSM 09.02 "Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification".
+- [7] GSM 09.07 : "Digital cellular telecommunications system (Phase 2+); General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)".
+- [8] ETS 300 102-1 (1990): "Integrated Services Digital Network (ISDN); User-network interface layer 3 specifications for basic call control".
+- [9] ETS 300 356-18: "ISDN User Part (ISUP) version 2 for the international interface: Part 18: Completion of Calls to Busy Subscriber (CCBS) supplementary service".
+- [10] ETS 300 358: "Integrated Services Digital Network (ISDN); Completion of Calls to Busy Subscriber (CCBS) supplementary service; Functional capabilities and information flows".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of this specification, the following definitions apply:
+
+**SSAP:** Supplementary Service Application Part. SSAP is the protocol used for CCBS procedures on the interface between the originating and destination network. Communication across this interface is performed using SCCP Connectionless Signalling (Refer to ETS 300 358). The terms CCBS-ASE defined in ETS 300 356-18 for the ISDN CCBS service and SSAP defined in GSM 03.93 are the same and are used interchangeably in this specification. The SSAP interface is between the originating network entities (HLR A, OLE) and the destination network entities (HLR B, DLE).
+
+## 3.2 Abbreviations
+
+Abbreviations used in this specification are listed in GSM 01.04.
+
+For the purposes of this specification, the following abbreviations apply:
+
+|      |                                        |
+|------|----------------------------------------|
+| ASE  | Application Service Element            |
+| CCBS | Call Completion to Busy Subscriber     |
+| DLE  | Destination Local Exchange             |
+| ISDN | Integrated Services Digital Network    |
+| MAP  | Mobile Application Part                |
+| OLE  | Originating Local Exchange             |
+| SCCP | Signalling Connection Control Part     |
+| SSAP | Supplementary Service Application Part |
+| TC   | Transaction Capabilities               |
+
+# 4 General
+
+## 4.1 GSM CCBS Architecture Overview
+
+The stage 1 of the CCBS service is defined in GSM 02.93.
+
+The network architecture to support the CCBS service in GSM networks is defined in GSM 03.93. For convenience, the architecture is shown again in this specification. Figure 4.1.1 is an architectural overview of the CCBS service when interworking between the originating and the destination networks involved. The originating network may be a mobile network or a fixed network and the destination network may also be a mobile network or a fixed network.
+
+The call related signalling (see ETS 300 356-18) for CCBS is performed on ISUP links on the following interfaces:
+
+VMSC A - GMSC B;
+
+VMSC A - DLE;
+
+OLE - GMSC B;
+
+whereas the specific CCBS procedures (see ETS 300 356-18) are performed via the SSAP protocol, which is signalled on the following interfaces:
+
+HLR A - HLR B;
+
+HLR A - DLE;
+
+OLE - HLR B.
+
+This specification only describes the MAP - SSAP protocol interworking.
+
+![Figure 4.1: Architectural overview showing common point of interworking. The diagram shows an Originating Network on the left and a Destination Network on the right, both connected to a central TRANSIT NETWORK(S). In the Originating Network, a Fixed Network (OLE) and a Mobile Network (VMSC A) are connected to the transit network via ISUP and SSAP links. The Mobile Network also includes HLR A and VLR A. In the Destination Network, a Fixed Network (DLE) and a Mobile Network (VMSC B) are connected to the transit network via ISUP and SSAP links. The Mobile Network also includes HLR B, VLR B, and GMSC B. SSAP links connect OLE to DLE, HLR A to HLR B, and HLR A to DLE. MAP links connect HLR A to HLR B and HLR A to GMSC B. ISUP links connect VMSC A to GMSC B and VMSC A to DLE.](28d250125d6a79bb23a8a3d459f54cb6_img.jpg)
+
+```
+graph LR
+    subgraph Originating_Network [Originating Network]
+        subgraph Fixed_Network_A [Fixed Network]
+            OLE[OLE]
+        end
+        subgraph Mobile_Network_A [Mobile Network]
+            HLR_A[HLR A]
+            VLR_A[VLR A]
+            VMSC_A[VMSC A]
+        end
+    end
+    subgraph Destination_Network [Destination Network]
+        subgraph Fixed_Network_B [Fixed Network]
+            DLE[DLE]
+        end
+        subgraph Mobile_Network_B [Mobile Network]
+            HLR_B[HLR B]
+            VLR_B[VLR B]
+            VMSC_B[VMSC B]
+            GMSC_B[GMSC B]
+        end
+    end
+    TRANSIT((TRANSIT NETWORK(S)))
+    OLE -- ISUP --> TRANSIT
+    OLE -- SSAP --> TRANSIT
+    VMSC_A -- ISUP --> TRANSIT
+    HLR_A -- SSAP --> TRANSIT
+    HLR_A -- SSAP --> DLE
+    HLR_A -- MAP --> HLR_B
+    HLR_A -- MAP --> GMSC_B
+    TRANSIT -- ISUP --> DLE
+    TRANSIT -- SSAP --> DLE
+    TRANSIT -- ISUP --> GMSC_B
+    TRANSIT -- SSAP --> HLR_B
+    GMSC_B -- ISUP --> VMSC_B
+```
+
+Figure 4.1: Architectural overview showing common point of interworking. The diagram shows an Originating Network on the left and a Destination Network on the right, both connected to a central TRANSIT NETWORK(S). In the Originating Network, a Fixed Network (OLE) and a Mobile Network (VMSC A) are connected to the transit network via ISUP and SSAP links. The Mobile Network also includes HLR A and VLR A. In the Destination Network, a Fixed Network (DLE) and a Mobile Network (VMSC B) are connected to the transit network via ISUP and SSAP links. The Mobile Network also includes HLR B, VLR B, and GMSC B. SSAP links connect OLE to DLE, HLR A to HLR B, and HLR A to DLE. MAP links connect HLR A to HLR B and HLR A to GMSC B. ISUP links connect VMSC A to GMSC B and VMSC A to DLE.
+
+Figure 4.1: Architectural overview showing common point of interworking
+
+## 4.2 GSM CCBS - ISDN CCBS ASE Interworking Overview
+
+The non-call related signalling procedures for CCBS between the originating network and the destination network are defined in ETS 300 356-18 as the ISDN CCBS-ASE. The GSM network also uses these signalling procedures for CCBS without any changes. The ISDN CCBS ASE protocol is supported in GSM networks in the HLR A (originating network) and HLR B (destination network). Therefore no protocol interworking for ISDN CCBS-ASE is needed for the CCBS service between GSM networks and ISDN networks.
+
+In GSM networks, the CCBS functionality is distributed across several network entities (see GSM 03.93) including the HLR, VLR, MSC and the MS. The HLR shall provide any necessary signalling interworking between the MAP protocol for call completion services on the MAP D-interface (between the VLR and the HLR) and ISDN CCBS-ASE protocol between the originating and destination networks.
+
+The MAP protocol for CCBS service is specified in GSM 09.02. The ISDN CCBS-ASE protocol is specified in ETS 300 356-18. This specification clarifies the interworking within the HLR between these protocols.
+
+## 4.3 Overview on the use of CCBS procedures and parameters values
+
+A GSM subscriber can roam while there is an active CCBS request. The called party address (MSISDN) information is used to initiate a dialogue with the destination network on the SSAP interface. The dialogue on the SSAP interface is opened and maintained while there is an active CCBS request (see ETS 300 356-18). However, the dialogues on the MAP D interface can be closed and reopened as necessary (see GSM 09.02 and GSM 03.93) and use the IMSI information for addressing.
+
+## 4.4 Mapping between MAP and SSAP application layer messages
+
+The mapping of MAP messages on the D interface and SSAP messages between the originating and destination networks is described. The precise coding of these messages is given in GSM 09.02 and ETS 300 356-18.
+
+### 4.4.1 MAP D-interface to SSAP interface mapping in HLR A
+
+**Table 4.1: Mapping of GSM 09.02 (MAP) operations to ETS 300 356-18 (SSAP) operations**
+
+| MAP OPERATIONS                                                                                                                                                                                                                                                                                                                                                   | SSAP OPERATIONS |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|
+| RegisterCCEntry                                                                                                                                                                                                                                                                                                                                                  | CcbsRequest     |
+| EraseCCEntry/ A GSM 03.93 Event (note 1)                                                                                                                                                                                                                                                                                                                         | CcbsCancel      |
+| RemoteUserFree Result/<br>RemoteUserFree Error/<br>A GSM 03.93 Event (note 2)                                                                                                                                                                                                                                                                                    | CcbsSuspend     |
+| StatusReport/<br>A GSM 03.93 Event (note 3)                                                                                                                                                                                                                                                                                                                      | CcbsResume      |
+| NOTE 1 This event may be local to HLR A. See GSM 03.93 for a dynamic description of possible events in HLR A leading to a CCBS request being cancelled. The SSAP CcbsCancel operation can include a cause code parameter; this shall be set to the appropriate value corresponding to the actual dynamic event by HLR A (e.g. cCBS-T3-Timeout, cCBS-T4-Timeout). |                 |
+| NOTE 2 This event may be local to HLR A. See GSM 03.93 for a dynamic description of possible events in HLR A leading to a CCBS request being suspended.                                                                                                                                                                                                          |                 |
+| NOTE 3 This event may be local to HLR A. See GSM 03.93 for a dynamic description of possible events in HLR A leading to a CCBS request being resumed.                                                                                                                                                                                                            |                 |
+
+### 4.4.2 SSAP interface to MAP D-interface interface mapping in HLR A
+
+| SSAP OPERATIONS                                                                                                                                                                                                                                                      | MAP OPERATIONS                               |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|
+| CcbsRequest Result                                                                                                                                                                                                                                                   | RegisterCCEntry Result                       |
+| CcbsRequest Error                                                                                                                                                                                                                                                    | RegisterCCEntry Error                        |
+| RemoteUserFree                                                                                                                                                                                                                                                       | RemoteUserFree                               |
+| CcbsCancel                                                                                                                                                                                                                                                           | SetReportingState/A GSM 03.93 Event (note 1) |
+| NOTE 1 This event may be local to HLR A. See GSM 03.93 for a dynamic description of possible events in HLR A resulting from a CCBS request being cancelled. The SSAP CcbsCancel operation can include a cause code parameter(e.g. cCBS-T7-Timeout, cCBS-T9-Timeout). |                                              |
+
+# 5 Mapping between MAP message parameters and SSAP message parameters
+
+The mapping between MAP message parameters and SSAP message parameters is described. The precise coding of these messages is given in GSM 09.02 and ETS 300 356-18.
+
+The following messages on the SSAP interface do not contain any parameters:
+
+- RemoteUserFree;
+- Suspend;
+- Resume.
+
+## 5.1 CCBS Request Invocation
+
+![Signalling flow for CCBS Request Invocation diagram](a234352dfaccdc24745c88eef7724cc6_img.jpg)
+
+```
+sequenceDiagram
+    participant VLRA
+    participant HLRA
+    participant DN as DESTINATION NETWORK B
+    Note left of VLRA: +--+\n      | |\n      +--+\n    VLRA->>HLRA: RegisterCCEntry\n    Note right of VLRA: TC-BEGIN\n    Note left of HLRA: +--+\n      | |\n      +--+\n    HLRA->>DN: CcbsRequest\n    Note right of HLRA: TC-BEGIN\n    Note left of DN: +--+\n      | |\n      +--+\n
+```
+
+The diagram illustrates the signalling flow for CCBS Request Invocation. It involves three entities: VLRA, HLRA, and DESTINATION NETWORK B. The sequence of messages is as follows: VLRA sends a RegisterCCEntry message to HLRA, accompanied by a TC-BEGIN message. HLRA then sends a CcbsRequest message to DESTINATION NETWORK B, also accompanied by a TC-BEGIN message. Each entity is represented by a vertical dashed line with a '+' at the top and bottom, indicating the start and end of the interaction period.
+
+Signalling flow for CCBS Request Invocation diagram
+
+Figure 5.1: Signalling flow for CCBS Request Invocation
+
+Table 5.1: Mapping of CCBS Request Invocation parameters
+
+| RegisterCCEntry PARAMETERS                                                                                                                                                                                                                                                                                                                                                                                                            | CcbsRequest PARAMETERS            |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|
+| ss-Code                                                                                                                                                                                                                                                                                                                                                                                                                               | not present                       |
+| ccbs-Feature<br>- b-subscriberSubaddress (note 1)                                                                                                                                                                                                                                                                                                                                                                                     | accessTransportParameter (note 2) |
+| translatedB-Number                                                                                                                                                                                                                                                                                                                                                                                                                    | calledPartyNumber (note 3)        |
+| serviceIndicator                                                                                                                                                                                                                                                                                                                                                                                                                      | not present                       |
+| callInfo                                                                                                                                                                                                                                                                                                                                                                                                                              | not present                       |
+| networkSignallInfo<br>- ISDN BC Tag, Length, Content (note 4)                                                                                                                                                                                                                                                                                                                                                                         | userServiceInf                    |
+| networkSignallInfo<br>- HLC Tag, Length, Content (note 5)                                                                                                                                                                                                                                                                                                                                                                             | accessTransportParameter (note 2) |
+| networkSignallInfo<br>- LLC Tag, Length, Content (note 6)                                                                                                                                                                                                                                                                                                                                                                             | accessTransportParameter (note 2) |
+| not present                                                                                                                                                                                                                                                                                                                                                                                                                           | retainSupported (note 7)          |
+| not present                                                                                                                                                                                                                                                                                                                                                                                                                           | callingPartyNumber (note 8)       |
+| not present                                                                                                                                                                                                                                                                                                                                                                                                                           | userServiceInfPrime (note 9)      |
+| NOTE 1 CCBS-Feature contains the b-subscriberSubaddress parameter which is the called party subaddress. The GSM HLR A shall map the called party subaddress into the accessTransportParameter if received from the VLR. The entire called party subaddress information (i.e. called party subaddress IEI, LENGTH and CONTENT) is mapped into the accessTransportParameter. See subclause 5.1.1. for details of the required encoding. |                                   |
+| NOTE 2 The CcbsRequest contains only one accessTransportParameter. This parameter contains information on the ISDN HLC, LLC and Subaddress.                                                                                                                                                                                                                                                                                           |                                   |
+| NOTE 3 The calledParty Number shall be in the international E.164 format.                                                                                                                                                                                                                                                                                                                                                             |                                   |
+| NOTE 4 The networkSignallInfo contains three information elements ISDN BC, HLC, LLC. The structure of this is defined in GSM 09.02 and the content in GSM 09.07. The ISDN BC information element CONTENT (i.e. without ISDN BC TAG, LENGTH) is mapped into the userServiceInf parameter.                                                                                                                                              |                                   |
+| NOTE 5 The networkSignallInfo contains three information elements ISDN BC, HLC, LLC. The structure of this is defined in GSM 09.02 and the content in GSM 09.07. The entire ISDN HLC information element (i.e. ISDN HLC TAG, LENGTH and CONTENT) is mapped into the accessTransportParameter.                                                                                                                                         |                                   |
+| NOTE 6 The networkSignallInfo contains three information elements ISDN BC, HLC, LLC. The structure of this is defined in GSM 09.02 and the content in GSM 09.07. The entire ISDN LLC information element (i.e. ISDN LLC TAG, LENGTH and CONTENT) is mapped into the accessTransportParameter.                                                                                                                                         |                                   |
+| NOTE 7 This information is local to the HLR A. This information element shall be coded by HLR A to reflect whether it supports CCBS Retention capability.                                                                                                                                                                                                                                                                             |                                   |
+| NOTE 8 This information is local to HLR A. The HLR A provides callingPartyNumber if CLIR was not invoked (See the serviceIndicator parameter in GSM 09.02 and GSM 03.93). If sent, the A subscriber's identity shall be the Basic MSISDN (i.e. the main MSISDN) and shall be in the international E.164 format.                                                                                                                       |                                   |
+| NOTE 9 The GSM HLR A shall not send the userServiceInfPrime                                                                                                                                                                                                                                                                                                                                                                           |                                   |
+
+### 5.1.1 Encoding of called party subaddress information
+
+The CCBS-Feature parameter is received from the VLR and it may include the b-subscriberSubaddress parameter as defined in GSM 09.02. The Called Party Subaddress information requires additional processing in HLR to ensure correct encoding of this information on the SSAP interface. The HLR shall add two octets to the ISDN-SubaddressString received from the VLR as indicated in figure 5.2.
+
+![](7e670a2b556b53ea9002dfff3a420e08_img.jpg)
+
+|                                                                          |
+|--------------------------------------------------------------------------|
+| Called Party Subaddress IEI<br>(See ETS 300 102-1)<br>0111 0001 (note 1) |
+| Length of the called party address<br>contents (note 2)                  |
+| ISDN-SubaddressString<br>(See GSM 09.02)<br><br>(note 3)                 |
+
+NOTE 1 Called Party Subaddress Information Element Identifier (IEI) is defined by ETS 300 102-1. Its value is "01110001". This information is not sent from the VLR and has to be derived locally in the HLR for interworking purposes.
+
+NOTE 2 This information has to be derived locally in the HLR for interworking purposes.
+
+NOTE 3 This information is sent by the VLR. The ISDN-SubaddressString contents is defined in GSM 09.02.
+
+**Figure 5.2: Encoding of Called Party Subaddress information**
+
+## 5.2 CCBS Request Result
+
+![Signalling flow diagram for CCBS Request Result showing interactions between VLRA, HLRA, and DESTINATION NETWORK B.](b3c108e7145f2017957569d06ea359cb_img.jpg)
+
+```
+
+sequenceDiagram
+    participant VLRA
+    participant HLRA
+    participant DN as DESTINATION NETWORK B
+    Note right of DN: CcbsRequest-Result  
+TC-CONTINUE
+    DN-->HLRA: 
+    Note right of HLRA: RegisterCCEntry-Result  
+TC-END
+    HLRA-->VLRA: 
+  
+```
+
+The diagram illustrates the signalling flow for the CCBS Request Result. It involves three entities: VLRA, HLRA, and DESTINATION NETWORK B. The flow starts with a message from DESTINATION NETWORK B to HLRA labeled 'CcbsRequest-Result' and 'TC-CONTINUE'. HLRA then sends a response back to DESTINATION NETWORK B. Next, HLRA sends a message to VLRA labeled 'RegisterCCEntry-Result' and 'TC-END'.
+
+Signalling flow diagram for CCBS Request Result showing interactions between VLRA, HLRA, and DESTINATION NETWORK B.
+
+**Figure 5.3: Signalling flow for CCBS Request Result**
+
+Table 5.2: Mapping of CCBS Request Result parameters
+
+| CcbsRequest_ Result PARAMETERS                                                                                                                                                                                       | RegisterCCEntry_ Result PARAMETERS |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|
+| retainSupported (note 1)                                                                                                                                                                                             | not present                        |
+| not present                                                                                                                                                                                                          | ccbs-Feature (note 2)              |
+| NOTE 1 This information is associated with each CCBS Request and indicates whether CCBS Retention is supported by the destination B network (see GSM 03.93).                                                         |                                    |
+| NOTE 2 This information is local to the HLR A. Some of information contained in ccbs-Feature (e.g. ccbs-index) is allocated by the HLR A. The ccbs-Feature information is sent to the MS (see GSM 03.93, GSM 04.93). |                                    |
+
+## 5.3 CCBS Request Error
+
+![Signalling flow for CCBS Request Error diagram showing three vertical lifelines: VLRA, HLRA, and DESTINATION NETWORK B. The flow starts with a message from DESTINATION NETWORK B to HLRA labeled 'CcbsRequest-Error' and 'TC-END'. HLRA then sends a message back to VLRA labeled 'RegisterCCEntry-Error' and 'TC-END'.](08441fa90c5fd11994626f662ac13f19_img.jpg)
+
+```
+
+sequenceDiagram
+    participant VLRA
+    participant HLRA
+    participant DESTINATION_NETWORK_B as DESTINATION NETWORK B
+    Note right of DESTINATION_NETWORK_B: +--+\n      | | |\n    Note left of HLRA: +--+\n      | | |\n    Note left of VLRA: +--+\n      | | |\n    DESTINATION_NETWORK_B->>HLRA: CcbsRequest-Error\n    Note right of HLRA: TC-END\n    HLRA-->>VLRA: RegisterCCEntry-Error\n    Note left of VLRA: TC-END
+  
+```
+
+Signalling flow for CCBS Request Error diagram showing three vertical lifelines: VLRA, HLRA, and DESTINATION NETWORK B. The flow starts with a message from DESTINATION NETWORK B to HLRA labeled 'CcbsRequest-Error' and 'TC-END'. HLRA then sends a message back to VLRA labeled 'RegisterCCEntry-Error' and 'TC-END'.
+
+Figure 5.4: Signalling flow for CCBS Request Error
+
+Table 5.3: Mapping of CCBS Request Error parameters
+
+| CcbsRequest_ Error PARAMETERS                                                                                        | RegisterCCEntry_ Error PARAMETERS        |
+|----------------------------------------------------------------------------------------------------------------------|------------------------------------------|
+| shortTermDenial/ longTermDenial (note 1)                                                                             | shortTermDenial/ longTermDenial (note 2) |
+| NOTE 1 For coding of these User Errors see ETS 300 356-18.                                                           |                                          |
+| NOTE 2 For coding of these User Errors see GSM 09.02. This information is sent to the MS (see GSM 04.93, GSM 04.80). |                                          |
+
+# 6 Dialogue handling on the SSAP interface
+
+The dialogue handling on the SSAP interface and the mapping between the corresponding TC transaction sublayer messages on the MAP D and SSAP interfaces is described. The diagrams show the general principle of dialogue handling. Specific message flows depend on the dynamics of the application in the network elements, see GSM 03.93 and GSM 09.02.
+
+## 6.1 Dialogue Beginning
+
+### 6.1.1 CCBS Request Invocation
+
+![Signalling flow for CCBS REQUEST INVOCATION](3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg)
+
+```
+sequenceDiagram
+    participant VLRA
+    participant HLRA
+    participant DN as DESTINATION NETWORK B
+    Note left of VLRA: +--+\n    VLRA->>HLRA: RegisterCCEntry\n    Note right of HLRA: TC-BEGIN\n    HLRA->>DN: CcbsRequest\n    Note right of HLRA: TC-BEGIN SCCP
+```
+
+The diagram illustrates the signalling flow for CCBS REQUEST INVOCATION. It involves three entities: VLRA, HLRA, and DESTINATION NETWORK B. The sequence of messages is as follows: VLRA sends a RegisterCCEntry message to HLRA, which is mapped to TC-BEGIN. HLRA then sends a CcbsRequest message to DESTINATION NETWORK B, which is mapped to TC-BEGIN SCCP.
+
+Signalling flow for CCBS REQUEST INVOCATION
+
+Figure 6.1: Signalling flow for CCBS REQUEST INVOCATION
+
+The CCBS Request invocation is carried by TC-BEGIN. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.1.
+
+## 6.2 Dialogue Continuation
+
+### 6.2.1 CCBS Request Result
+
+![Signalling flow for CCBS Request Result](5dfc130b129ace4df375839020a5700d_img.jpg)
+
+```
+sequenceDiagram
+    participant VLRA
+    participant HLRA
+    participant DN as DESTINATION NETWORK B
+    Note left of VLRA: +--+\n    DN->>HLRA: CcbsRequest-Result\n    Note right of HLRA: TC-CONTINUE SCCP\n    HLRA->>VLRA: RegisterCCEntry-Result\n    Note right of VLRA: TC-END
+```
+
+The diagram illustrates the signalling flow for CCBS Request Result. It involves three entities: VLRA, HLRA, and DESTINATION NETWORK B. The sequence of messages is as follows: DESTINATION NETWORK B sends a CcbsRequest-Result message to HLRA, which is mapped to TC-CONTINUE SCCP. HLRA then sends a RegisterCCEntry-Result message to VLRA, which is mapped to TC-END.
+
+Signalling flow for CCBS Request Result
+
+Figure 6.2: Signalling flow for CCBS Request Result
+
+The CCBS Request Result is carried by TC-CONTINUE. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.3.
+
+### 6.2.2 CCBS Remote User Free Invocation
+
+![Sequence diagram for CCBS Remote User Free Invocation showing signaling flow between VLRA, HLRA, and DESTINATION NETWORK B.](bd671b21db63e6fdb2196e9b18502aac_img.jpg)
+
+```
+
+sequenceDiagram
+    participant VLRA
+    participant HLRA
+    participant DNB as DESTINATION NETWORK B
+    Note right of HLRA: RemoteUserFree
+    HLRA->>DNB: TC-CONTINUE SCCP
+    Note left of HLRA: RemoteUserFree
+    HLRA->>VLRA: TC-BEGIN
+  
+```
+
+The diagram illustrates the signaling flow for CCBS Remote User Free Invocation. It involves three entities: VLRA, HLRA, and DESTINATION NETWORK B. The sequence starts with a message 'RemoteUserFree' being processed at the HLRA. A 'TC-CONTINUE SCCP' message is sent from the HLRA to the DESTINATION NETWORK B. Simultaneously, another 'RemoteUserFree' message is processed at the HLRA, and a 'TC-BEGIN' message is sent from the HLRA to the VLRA.
+
+Sequence diagram for CCBS Remote User Free Invocation showing signaling flow between VLRA, HLRA, and DESTINATION NETWORK B.
+
+**Figure 6.3: Signalling flow for Remote User Free Invocation**
+
+The CCBS Remote User Free Invocation is carried by TC-CONTINUE. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.3.
+
+### 6.2.3 CCBS Suspend Invocation
+
+![Sequence diagram for CCBS Suspend Invocation (RemoteUserFree_Result) showing signaling flow between VLRA, HLRA, and DESTINATION NETWORK B.](f6e8acf9f931452d01688d311b5c0364_img.jpg)
+
+```
+
+sequenceDiagram
+    participant VLRA
+    participant HLRA
+    participant DNB as DESTINATION NETWORK B
+    Note left of HLRA: RemoteUserFree-Result
+    VLRA->>HLRA: TC-END
+    Note right of HLRA: CcbsSuspend (note 1)
+    HLRA->>DNB: TC-CONTINUE SCCP
+  
+```
+
+The diagram illustrates the signaling flow for CCBS Suspend Invocation (RemoteUserFree\_Result). It involves three entities: VLRA, HLRA, and DESTINATION NETWORK B. The sequence starts with a message 'RemoteUserFree-Result' being processed at the VLRA. A 'TC-END' message is sent from the VLRA to the HLRA. Simultaneously, a 'CcbsSuspend (note 1)' message is processed at the HLRA, and a 'TC-CONTINUE SCCP' message is sent from the HLRA to the DESTINATION NETWORK B.
+
+Sequence diagram for CCBS Suspend Invocation (RemoteUserFree\_Result) showing signaling flow between VLRA, HLRA, and DESTINATION NETWORK B.
+
+NOTE 1 For conditions leading to a request being suspended, see GSM 03.93
+
+**Figure 6.4: Signalling flow for CCBS Suspend Invocation (RemoteUserFree\_Result)**
+
+![Sequence diagram for CCBS Suspend Invocation (RemoteUserFree_Error) showing signaling flow between VLRA, HLRA, and DESTINATION NETWORK B.](704082cc3e11776bda29595c76411362_img.jpg)
+
+```
+
+sequenceDiagram
+    participant VLRA
+    participant HLRA
+    participant DNB as DESTINATION NETWORK B
+    Note left of HLRA: RemoteUserFree-Error
+    VLRA->>HLRA: TC-END
+    Note right of HLRA: CcbsSuspend (note 1)
+    HLRA->>DNB: TC-CONTINUE SCCP
+  
+```
+
+The diagram illustrates the signaling flow for CCBS Suspend Invocation (RemoteUserFree\_Error). It involves three entities: VLRA, HLRA, and DESTINATION NETWORK B. The sequence starts with a message 'RemoteUserFree-Error' being processed at the VLRA. A 'TC-END' message is sent from the VLRA to the HLRA. Simultaneously, a 'CcbsSuspend (note 1)' message is processed at the HLRA, and a 'TC-CONTINUE SCCP' message is sent from the HLRA to the DESTINATION NETWORK B.
+
+Sequence diagram for CCBS Suspend Invocation (RemoteUserFree\_Error) showing signaling flow between VLRA, HLRA, and DESTINATION NETWORK B.
+
+NOTE 1 For conditions leading to a request being suspended, see GSM 03.93
+
+**Figure 6.5: Signalling flow for CCBS Suspend Invocation (RemoteUserFree\_Error)**
+
+The CCBS Suspend Invocation is carried by TC-CONTINUE. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.2
+
+### 6.2.4 CCBS Resume Invocation
+
+![Signalling flow for CCBS Resume Invocation diagram](9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg)
+
+```
+
+sequenceDiagram
+    participant VLRA
+    participant HLRA
+    participant DN as DESTINATION NETWORK B
+    Note left of VLRA: StatusReport
+    VLRA->>HLRA: TC-BEGIN
+    HLRA->>DN: CcbsResume (note 1)  
+TC-CONTINUE  
+SCCP
+  
+```
+
+The diagram illustrates the signalling flow for CCBS Resume Invocation. It involves three entities: VLRA, HLRA, and DESTINATION NETWORK B. The sequence starts with a 'StatusReport' message from VLRA to HLRA. VLRA then sends a 'TC-BEGIN' message to HLRA. HLRA sends a 'CcbsResume (note 1)' message to DESTINATION NETWORK B, which includes 'TC-CONTINUE' and 'SCCP' components.
+
+Signalling flow for CCBS Resume Invocation diagram
+
+NOTE 1 For conditions leading to a request being resumed, see GSM 03.93
+
+**Figure 6.6: Signalling flow for CCBS Resume Invocation**
+
+The CCBS Resume Invocation is carried by TC-CONTINUE. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.2.
+
+## 6.3 Dialogue End
+
+### 6.3.1 Normal dialogue end
+
+![Signalling flow for normal dialogue end diagram](3f1987804d7d78bc3b3bc560e974280a_img.jpg)
+
+```
+
+sequenceDiagram
+    participant VLRA
+    participant HLRA
+    participant DN as DESTINATION NETWORK B
+    Note right of DN: No component primitive
+    DN->>HLRA: TC-END  
+SCCP
+    HLRA->>VLRA: SetReportingState (note 1)  
+TC-BEGIN
+  
+```
+
+The diagram illustrates the signalling flow for normal dialogue end. It involves three entities: VLRA, HLRA, and DESTINATION NETWORK B. The sequence starts with a 'No component primitive' message from DESTINATION NETWORK B to HLRA. DESTINATION NETWORK B then sends a 'TC-END' message to HLRA, which includes 'SCCP' components. HLRA sends a 'SetReportingState (note 1)' message to VLRA, which includes 'TC-BEGIN' components.
+
+Signalling flow for normal dialogue end diagram
+
+NOTE 1 If the monitoring function is active in VLR A and all outstanding CCBS Requests have been deactivated, the HLR A sends SetReportingState to deactivate the monitoring function (see GSM 03.93).
+
+**Figure 6.7: Signalling flow for normal dialogue end**
+
+The normal ending of CCBS dialogue from the B-side is carried by TC-END. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.3.
+
+### 6.3.2 CCBS Cancel Invocation (from A-side)
+
+![Signalling flow for CCBS Cancel Invocation (from A-side)](16152cf1d84aea10848758f51a91ff6a_img.jpg)
+
+```
+
+sequenceDiagram
+    participant VLRA
+    participant HLRA
+    participant DN as DESTINATION NETWORK B
+    Note left of VLRA: (note 1)
+    VLRA->>HLRA: EraseCCEntry
+    Note right of HLRA: TC-BEGIN
+    HLRA->>DN: CcbsCancel
+    Note right of DN: TC-END (note 1)  
+SCCP
+  
+```
+
+The diagram illustrates the signalling flow for CCBS Cancel Invocation from the A-side. It involves three entities: VLRA, HLRA, and DESTINATION NETWORK B. The sequence starts with VLRA sending an 'EraseCCEntry' message to HLRA, with a note indicating this is note 1. HLRA responds with 'TC-BEGIN'. HLRA then sends a 'CcbsCancel' message to DESTINATION NETWORK B, with a note indicating this is TC-END (note 1) and SCCP.
+
+Signalling flow for CCBS Cancel Invocation (from A-side)
+
+NOTE 1 Where all outstanding CCBS Requests have been deactivated, CCBS Cancel is sent to each corresponding Destination Network B with the appropriate Destination Network B E.164 Called Party Address (see GSM 03.93, GSM 04.93).
+
+**Figure 6.8: Signalling flow for CCBS Cancel Invocation (from A-side)**
+
+The CCBS Cancel Invocation from the A-side is carried by TC-END. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.2.
+
+### 6.3.3 CCBS Cancel Invocation (from B-side)
+
+![Signalling flow for CCBS Cancel Invocation (from B-side)](6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg)
+
+```
+
+sequenceDiagram
+    participant VLRA
+    participant HLRA
+    participant DN as DESTINATION NETWORK B
+    Note left of DN: (note 1)
+    DN->>HLRA: CcbsCancel
+    Note right of HLRA: TC-END  
+SCCP
+    HLRA->>VLRA: SetReportingState
+    Note left of VLRA: TC-BEGIN
+  
+```
+
+The diagram illustrates the signalling flow for CCBS Cancel Invocation from the B-side. It involves three entities: VLRA, HLRA, and DESTINATION NETWORK B. The sequence starts with DESTINATION NETWORK B sending a 'CcbsCancel' message to HLRA, with a note indicating this is note 1. HLRA responds with 'TC-END' and 'SCCP'. HLRA then sends a 'SetReportingState' message to VLRA, with a note indicating this is TC-BEGIN.
+
+Signalling flow for CCBS Cancel Invocation (from B-side)
+
+NOTE 1: If the monitoring function is active in VLR A and all outstanding CCBS Requests have been deactivated, the HLR A sends SetReportingState to deactivate the monitoring function (see GSM 03.93).
+
+**Figure 6.9: Signalling flow for CCBS Cancel Invocation (from B-side)**
+
+The CCBS Cancel Invocation from the B-side is carried by TC-END. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.3.
+
+### 6.3.4 CCBS Request Error
+
+![Sequence diagram showing the signalling flow for CCBS Request Error between VLRA, HLRA, and DESTINATION NETWORK B.](df82d77a0d2637cbf2da9ea920a554fa_img.jpg)
+
+```
+sequenceDiagram
+    participant VLRA
+    participant HLRA
+    participant DN as DESTINATION NETWORK B
+    Note right of DN: CcbsRequest-Error
+    DN-->HLRA: TC-END SCCP
+    Note right of HLRA: RegisterCCEntry-Error
+    HLRA-->VLRA: TC-END
+```
+
+The diagram illustrates the signalling flow for a CCBS Request Error. It involves three entities: VLRA, HLRA, and DESTINATION NETWORK B. The sequence of messages is as follows: 1. A message labeled 'CcbsRequest-Error' is sent from DESTINATION NETWORK B to HLRA. 2. Below this, a message labeled 'TC-END SCCP' is sent from DESTINATION NETWORK B to HLRA. 3. Next, a message labeled 'RegisterCCEntry-Error' is sent from HLRA to VLRA. 4. Finally, a message labeled 'TC-END' is sent from HLRA to VLRA.
+
+Sequence diagram showing the signalling flow for CCBS Request Error between VLRA, HLRA, and DESTINATION NETWORK B.
+
+**Figure 6.10: Signalling flow for CCBS Request Error**
+
+The CCBS Request Error is carried by TC-END. The SCCP addressing parameters on the SSAP interface shall be as shown in table 7.3.
+
+# 7 Addressing of SCCP layer messages on the SSAP interface
+
+The SCCP layer addressing for messages on the SSAP interface is described.
+
+## 7.1 Use of SCCP
+
+Clarifications and restrictions on the use and coding of the main SCCP parameters impacted by CCBS on the SSAP interface are indicated. See ETS 300 356-18 and the associated references for the full specification on the use of SCCP on the SSAP interface. The SCCP routeing on the SSAP interface shall be based on the Global Title (GT) translation mechanism as for routeing on the international interface. GT addressing shall be used for inter and intra PLMN signalling. This allows any impact of other network features e.g. Mobile Number Portability to be minimised.
+
+## 7.2 Addressing of messages at the originating PLMN
+
+### 7.2.1 TC-BEGIN message from the originating network HLR
+
+The relevant SCCP parameters in the first message from the HLR A transporting TC-BEGIN are shown in table 7.1. All other SCCP parameters shall be as indicated in ETS 300 356-18.
+
+**Table 7.1: SCCP parameters used by HLR A for TC-BEGIN**
+
+| <b>SCCP PARAMETERS for the message transporting TC-BEGIN</b> | <b>PARAMETER VALUE</b>                                                                                                                                                                                                                                           |
+|--------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CdPA-Called Party Address                                    | E.164 number of the Called Party. This may be in either international or national E.164 format, see subclause 7.4.1. It is derived from the translatedB-Number parameter which is available from the CCBS application in HLRA, see RegisterCCEntry in GSM 09.02. |
+| CgPA-Calling Party Address                                   | E.164 number of HLR A. This may be in either international or national E.164 format, see subclause 7.4.1.                                                                                                                                                        |
+| SSN- Subsystem Number                                        | 0000 1011<br>(See ETS 300 356-18)                                                                                                                                                                                                                                |
+| TT- Translation Type                                         | 0001 0001<br>(See ETS 300 356-18)                                                                                                                                                                                                                                |
+| Other SCCP Parameters                                        | See ETS 300 356-18                                                                                                                                                                                                                                               |
+
+### 7.2.2 TC-CONTINUE, TC-END messages from the originating network HLR
+
+The relevant SCCP parameters in the subsequent messages from the HLR A transporting TC-CONTINUE and TC-END are shown in table 7.2. All other SCCP parameters shall be as indicated in ETS 300 356-18.
+
+**Table 7.2: SCCP parameters used by HLR A for TC-CONTINUE, TC-END**
+
+| <b>SCCP PARAMETERS for the message transporting TC-CONTINUE, TC-END</b> | <b>PARAMETER VALUE</b>                                                                                                                                                                |
+|-------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CdPA-Called Party Address                                               | The Called Party Address is the E.164 address of the calling entity in the destination network that was received in the first response message from the destination network (note 1). |
+| CgPA-Calling Party Address                                              | E.164 number of HLR A. This may be in either international or national E.164 format as used in the message transporting TC-BEGIN, see subclause 7.4.1.                                |
+| SSN- Subsystem Number                                                   | 0000 1011<br>(See ETS 300 356-18)                                                                                                                                                     |
+| TT- Translation Type                                                    | 0001 0001<br>(See ETS 300 356-18)                                                                                                                                                     |
+| Other SCCP Parameters                                                   | See ETS 300 356-18                                                                                                                                                                    |
+| NOTE 1                                                                  | If the destination network is a GSM PLMN, this is E.164 number of HLR B.                                                                                                              |
+
+## 7.3 Addressing of messages at the destination PLMN
+
+### 7.3.1 TC-CONTINUE, TC-END messages from the destination network HLR
+
+The relevant SCCP parameters in the first and subsequent messages from the HLR B transporting TC-CONTINUE and TC-END are shown in table 7.3. All other SCCP parameters shall be as indicated in ETS 300 356-18.
+
+**Table 7.3: SCCP parameters for TC-CONTINUE, TC-END used by HLR B**
+
+| SCCP PARAMETERS for the message transporting TC-CONTINUE, TC-END | PARAMETER VALUE                                                                                                                                                                                    |
+|------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CdPA-Called Party Address                                        | The Called Party Address is the E.164 address of the calling entity in the originating network that was received in the first message transporting TC-BEGIN from the originating network (note 1). |
+| CgPA-Calling Party Address                                       | E.164 number of HLR B. This may be in either international or national E.164 format, see subclause 7.4.2 (note 2)                                                                                  |
+| SSN- Subsystem Number                                            | 0000 1011<br>(See ETS 300 356-18)                                                                                                                                                                  |
+| TT- Translation Type                                             | 0001 0001<br>(See ETS 300 356-18)                                                                                                                                                                  |
+| Other SCCP Parameters                                            | See ETS 300 356-18                                                                                                                                                                                 |
+| NOTE 1                                                           | If the originating network is a GSM PLMN, this is E.164 number of HLR A.                                                                                                                           |
+| NOTE 2                                                           | The E.164 number of HLRB is used as this allows any impact of other network features to be minimised.                                                                                              |
+
+## 7.4 Number formats of the SCCP address parameters
+
+The Called and Calling Party Address information in SCCP should be in international E.164 format. Optionally national format E.164 addresses may be used in SCCP for routing of national traffic. For this, the HLR has to modify the addresses which are in international E.164 format to a national E.164 format. If a national format E.164 option is used, all involved network nodes in a given country (i.e. the originating network, any transit networks and the destination network) need support that option. As negotiation is not possible, the option selected by the originating network shall determine the addressing used for all messages which are a part of a single dialogue.
+
+### 7.4.1 Originating PLMN
+
+The Called and Calling Party Address information in SCCP should be in international E.164 format.
+
+The originating network HLR A may use the SCCP Called Party Address in national E.164 format if the called destination (as indicated by the translatedB-number) is in the same country as HLR A.
+
+The originating network HLR A may use the SCCP Calling Party Address in national E.164 format if the called destination (as indicated by the translatedB-number) is in the same country as HLR A.
+
+The originating network HLR A shall ensure that the SCCP Called and Calling Party Addresses are either both in international format or national format.
+
+### 7.4.2 Destination PLMN
+
+The Called and Calling Party Address information in SCCP should be in international E.164 format.
+
+The destination network HLR B may use the SCCP Called Party Address in national E.164 format if the originating network is in the same country as HLR B.
+
+The destination network HLR B may use the SCCP Calling Party Address in national E.164 format if the originating network is in the same country as HLR B.
+
+The destination network HLR B shall ensure that the SCCP Called and Calling Party Addresses are either both in international format or national format.

marked/Rel-18/29_series/29119/raw.md

@@ -0,0 +1,296 @@
+
+
+# 3GPP TS 29.119 V18.0.0 (2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; GPRS Tunnelling Protocol (GTP) specification for Gateway Location Register (GLR) (Release 18)**
+
+![LTE Advanced Pro logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for LTE Advanced Pro, featuring the letters 'lte' in a bold, lowercase font. Above the 't' is a green signal icon with three bars. To the right of the 't' are the words 'Advanced' and 'Pro' in a smaller font, with 'Pro' in red.
+
+LTE Advanced Pro logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized, bold font. Below the 'P' is a red signal icon with three bars. Below 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.
+
+© 2024, 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         |
+| 1.1 References.....                                         | 5         |
+| 2 Definitions and abbreviations .....                       | 5         |
+| 2.1 Definitions.....                                        | 5         |
+| 2.2 Abbreviations .....                                     | 6         |
+| 3 General.....                                              | 6         |
+| 4 Transmission order and bit definitions.....               | 7         |
+| 5 GTP header .....                                          | 7         |
+| 6 GTP Message and Message Formats .....                     | 7         |
+| 6.1 Signalling Message Formats .....                        | 7         |
+| 6.2 Path Management messages.....                           | 8         |
+| 6.3 Tunnel Management messages.....                         | 8         |
+| 6.4 Location Management message .....                       | 9         |
+| 6.5 Mobility Management messages.....                       | 9         |
+| 6.6 Reliable delivery of signalling messages .....          | 9         |
+| 6.7 Information element .....                               | 10        |
+| 7 Signalling Plane (GTP-C) .....                            | 10        |
+| 8 GTP-U .....                                               | 10        |
+| 9 Path Protocol.....                                        | 10        |
+| 10 Error handling .....                                     | 10        |
+| 11 Inter-PLMN GTP communication over the Gp Interface ..... | 10        |
+| 12 IP, the networking technology used by GTP .....          | 10        |
+| 13 GTP parameters.....                                      | 10        |
+| <b>Annex A (informative): Change history.....</b>           | <b>11</b> |
+
+# --- Foreword
+
+The present document has been produced by the 3<sup>rd</sup> 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.
+
+# 1 Scope
+
+The present document describes the signalling requirements and procedures used at network elements related to the GLR for GTP within the 3GPP system at the application level.
+
+The present document gives the description of the systems needed only in the network utilising GLR as the delta document against 3GPP TS 29.060.
+
+## 1.1 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 TS 23.060: "General Packet Radio Service (GPRS); Service description Stage2".
+- [2] 3GPP TS 23.119: "Gateway Location Register (GLR) – stage2".
+- [3] 3GPP TS 24.008: "Mobile radio interface layer 3 specification, Core Network Protocols – Stage 3".
+- [4] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
+- [5] 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface".
+
+# 2 Definitions and abbreviations
+
+## 2.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply.
+
+**Gateway Location Register:** this entity handles location management of roaming subscriber in visited network without involving HLR
+
+**Intermediate GSN:** this entity is used as serving GSN towards home network and relay some PDU notification messages between serving GSN and Gateway GSN
+
+**MM context:** information sets held in MS and GSNs for a GPRS subscriber related to mobility management (MM)
+
+**MM Context ID:** IMSI or equivalent for use in conjunction with Anonymous Access (please refer to section GTP Header)
+
+**Path:** UDP/IP path and TCP/IP path are examples of paths that may be used to multiplex GTP tunnels
+
+**Path Protocol:** path Protocol is the protocol(s) used as a bearer of GTP between GSNs
+
+**PDP:** packet Data Protocol (PDP) is a network protocol used by an external packet data network interfacing to GPRS
+
+- PDP Context:** information sets held in MS and GSNs for a PDP address
+- Signalling message:** GTP signalling messages are exchanged between GSN pairs in a path. The signalling messages are used to transfer GSN capability information between GSN pairs and to create, update and delete GTP tunnels
+- T-PDU:** original packet, for example an IP datagram, from an MS or a network node in an external packet data network. A T-PDU is the payload that is tunnelled in the GTP tunnel
+- Tunnel Endpoint Identifier (TEID):** this field unambiguously identifies a tunnel endpoint in the receiving GTP-U or GTP-C protocol entity. The receiving end side of a GTP tunnel locally assigns the TEID value the transmitting side has to use. The TEID values are exchanged between tunnel endpoints using GTP-C messages
+
+## 2.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|        |                              |
+|--------|------------------------------|
+| GGSN   | Gateway GPRS support node    |
+| GLR    | Gateway Location Register    |
+| GPRS   | General Packet Radio Service |
+| GTP    | GPRS Tunnelling Protocol     |
+| IM_GSN | Intermediate GSN             |
+| IP     | Internet Protocol            |
+| GLR    | Gateway Location Register    |
+| SGSN   | Serving GPRS support node    |
+| TEID   | Tunnel Endpoint Identifier   |
+| UDP    | User Datagram Protocol       |
+
+# --- 3 General
+
+The present document defines the GPRS Tunnelling Protocol (GTP) specific to the network with the GLR, i.e. the protocol between IM\_GSN and other nodes (i.e. GGSN, SGSN and GTP-MAP protocol converting GSN). It includes only the GTP signalling but not data transfer procedures.
+
+The interface between IM\_GSM and GGSN is either intra-PLMN interface or inter-PLMN interface.
+
+![Figure 1: Logical Architecture for PS domain in the network with GLR. The diagram shows a hierarchy of network elements. At the top are GLR and HLR connected by a dotted line (Signalling Interface). Below GLR is a GTP-MAP Protocol Converting GSN, which is connected to GLR by a dotted line and to an IM_GSN by a dotted line. Below HLR is another GTP-MAP Protocol Converting GSN, which is connected to HLR by a dotted line and to a GGSN by a dotted line. The IM_GSN is connected to the GTP-MAP Protocol Converting GSN under GLR by a dotted line, to an SGSN by a solid line (Signalling and Data Transfer Interface), and to the GGSN by a dotted line. The SGSN is connected to the GGSN by a solid line. A legend at the bottom indicates that dotted lines represent Signalling Interfaces and solid lines represent Signalling and Data Transfer Interfaces.](997233d405f0d4b89ddeb7683e047f66_img.jpg)
+
+Figure 1: Logical Architecture for PS domain in the network with GLR. The diagram shows a hierarchy of network elements. At the top are GLR and HLR connected by a dotted line (Signalling Interface). Below GLR is a GTP-MAP Protocol Converting GSN, which is connected to GLR by a dotted line and to an IM\_GSN by a dotted line. Below HLR is another GTP-MAP Protocol Converting GSN, which is connected to HLR by a dotted line and to a GGSN by a dotted line. The IM\_GSN is connected to the GTP-MAP Protocol Converting GSN under GLR by a dotted line, to an SGSN by a solid line (Signalling and Data Transfer Interface), and to the GGSN by a dotted line. The SGSN is connected to the GGSN by a solid line. A legend at the bottom indicates that dotted lines represent Signalling Interfaces and solid lines represent Signalling and Data Transfer Interfaces.
+
+**Figure 1: Logical Architecture for PS domain in the network with GLR**
+
+The GTP protocol is implemented only by IM\_GSNs, SGSNs and GGSNs. No other systems need to be aware of GTP. GPRS MSs are connected to a SGSN without being aware of GTP.
+
+It is assumed that there will be a many-to-many relationship between IM\_GSNs, SGSNs and GGSNs. An IM\_GSN may provide service to many GGSNs. A SGSN may provide service to many IM\_GSNs and GGSNs.
+
+# 4 Transmission order and bit definitions
+
+Transmission order and bit definitions on the interface between the IM\_GSN and other nodes in the network with GLR are the same as that used in the network without the GLR, see 3GPP TS 29.060.
+
+# 5 GTP header
+
+The GTP header used on interface between the IM\_GSN and other nodes in the network with GLR is the same as that used in the network without the GLR, see 3GPP TS 29.060.
+
+# 6 GTP Message and Message Formats
+
+The only signalling plane exists between the IM\_GSN and other nodes (i.e. GGSN, SGSN and GTP-MAP protocol converting GSN).
+
+## 6.1 Signalling Message Formats
+
+GTP defines a set of signalling messages between two associated GSNs. The signalling messages to be used between the IM\_GSN and other nodes are defined in the table below. For the GTP signalling messages to be used on other interfaces see 3GPP TS 29.060.
+
+Table 1: Signalling messages
+
+| Message Type value (Decimal) | Signalling message                          | Reference                |
+|------------------------------|---------------------------------------------|--------------------------|
+| 3                            | Version Not Supported                       | 7.4.3 in 3GPP TS 29.060  |
+| 27                           | PDU Notification Request                    | 7.5.12 in 3GPP TS 29.060 |
+| 28                           | PDU Notification Response                   | 7.5.13 in 3GPP TS 29.060 |
+| 29                           | PDU Notification Reject Request             | 7.5.14 in 3GPP TS 29.060 |
+| 30                           | PDU Notification Reject Response            | 7.5.15 in 3GPP TS 29.060 |
+| 32                           | Send Routeing Information for GPRS Request  | 7.6.1 in 3GPP TS 29.060  |
+| 33                           | Send Routeing Information for GPRS Response | 7.6.2 in 3GPP TS 29.060  |
+| 34                           | Failure Report Request                      | 7.6.3 in 3GPP TS 29.060  |
+| 35                           | Failure Report Response                     | 7.6.4 in 3GPP TS 29.060  |
+
+## 6.2 Path Management messages
+
+The messages, which are listed in following table, are used on the interface between the IM\_GSN and other nodes. For the definitions of these messages and other messages used on the other interfaces refer to the corresponding sections in 3GPP TS 29.060.
+
+| Messages              | Sending node | Receiving node |
+|-----------------------|--------------|----------------|
+| Version Not Supported | IM_GSN       | GGSN, SGSN     |
+|                       | GGSN, SGSN   | IM_GSN         |
+
+## 6.3 Tunnel Management messages
+
+In following table, only the messages used between the IM\_GSN and GGSN and between the IM\_GSN and SGSN are listed. For the definitions of these messages and other messages used on the other interfaces refer to the corresponding sections in 3GPP TS 29.060.
+
+| Messages                         | Sending node | Receiving node |
+|----------------------------------|--------------|----------------|
+| PDU Notification Request         | GGSN         | IM_GSN         |
+|                                  | IM_GSN       | SGSN           |
+| PDU Notification Response        | SGSN         | IM_GSN         |
+|                                  | IM_GSN       | GGSN           |
+| PDU Notification Reject Request  | SGSN         | IM_GSN         |
+|                                  | IM_GSN       | GGSN           |
+| PDU Notification Reject Response | GGSN         | IM_GSN         |
+|                                  | IM_GSN       | SGSN           |
+
+## 6.4 Location Management message
+
+In the network with the GLR, The optional Location Management messages are defined to support the case when Network-Requested PDP Context Activation procedures are used and an IM\_GSN does not have a SS7 MAP interface. GTP is then used to transfer signalling messages between the IM\_GSN and a GTP-MAP protocol-converting GSN in the GPRS backbone network. The GTP-MAP protocol-converting GSN converts the signalling messages described in this section between GTP and MAP. The MAP messages are sent to and received from the GLR. The GTP-MAP protocol-converting function is described in 3GPP TS 23.060. The MAP protocol describing the corresponding procedures and messages is described in 3GPP TS 29.002. This alternative method is illustrated in Figure 2.
+
+![Diagram illustrating the GTP-MAP Interworking between IM_GSN, GSN, and GLR. The diagram shows three protocol stacks. The IM_GSN stack has layers GTP, UDP, IP, L2, and L1. The GSN stack has layers GTP, UDP, IP, L2, and L1, with a 'GTP-MAP Interworking' block above the GTP layer. This block contains two sub-stacks: one with GTP, MAP, TCAP, SCCP, MTP3, MTP2, and L1; the other with MAP, TCAP, SCCP, MTP3, MTP2, and L1. The GLR stack has layers MAP, TCAP, SCCP, MTP3, MTP2, and L1. Vertical dashed lines separate the three stacks, and horizontal lines connect corresponding layers across them.](367926125450c2bc3f4bdca9d59a62ba_img.jpg)
+
+Diagram illustrating the GTP-MAP Interworking between IM\_GSN, GSN, and GLR. The diagram shows three protocol stacks. The IM\_GSN stack has layers GTP, UDP, IP, L2, and L1. The GSN stack has layers GTP, UDP, IP, L2, and L1, with a 'GTP-MAP Interworking' block above the GTP layer. This block contains two sub-stacks: one with GTP, MAP, TCAP, SCCP, MTP3, MTP2, and L1; the other with MAP, TCAP, SCCP, MTP3, MTP2, and L1. The GLR stack has layers MAP, TCAP, SCCP, MTP3, MTP2, and L1. Vertical dashed lines separate the three stacks, and horizontal lines connect corresponding layers across them.
+
+Figure 2: IM\_GSN - GLR Signalling via a GTP-MAP protocol-converter in a GSN
+
+In following table, only the messages used between the IM\_GSN and The GTP-MAP protocol-converting GSN are listed. For the definitions of these messages and other messages used on the other interfaces refer to the corresponding sections in 3GPP TS 29.060.
+
+| Messages                                    | Sending node                | Receiving node              |
+|---------------------------------------------|-----------------------------|-----------------------------|
+| Send Routeing Information for GPRS Request  | IM_GSN                      | GTP-MAP protocol-converting |
+| Send Routeing Information for GPRS Response | GTP-MAP protocol-converting | IM_GSN                      |
+| Failure Report Request                      | IM_GSN                      | GTP-MAP protocol-converting |
+| Failure Report Response                     | GTP-MAP protocol-converting | IM_GSN                      |
+
+## 6.5 Mobility Management messages
+
+The messages belonging to the mobility management messages are not used on the interface between the IM\_GSN and other nodes in the network with the GLR.
+
+## 6.6 Reliable delivery of signalling messages
+
+For the Reliability mechanism in the IM\_GSN, see section 7.8 in 3GPP TS 29.060.
+
+## 6.7 Information element
+
+The format of information elements in the message used on the interface between the IM\_GSN and other nodes in the network with GLR is the same as that in the network without the GLR. See 3GPP TS 29.060.
+
+# --- 7 Signalling Plane (GTP-C)
+
+The definition of signalling plane used in the network with the GLR is the same as that used in the network without the GLR, see in 3GPP TS 29.060.
+
+# --- 8 GTP-U
+
+GTP-U is not used on the interface between the IM\_GSN and other nodes. For the definition of GTP-U on the other interfaces, see in 3GPP TS 29.060.
+
+# --- 9 Path Protocol
+
+The Path Protocol on the interface between the IM\_GSN and other nodes in the network with the GLR is the same as that used in the network without the GLR. See 3GPP TS 29.060.
+
+# --- 10 Error handling
+
+The error handling on the interface between the IM\_GSN and other nodes is the same as that in the network without the GLR. See 3GPP TS 29.060. One exception is that the IM\_GSN doesn't have a Restart Counter because the IM\_GSM stores no PDP and MM context and therefore the synchronisation of the status of these with other GSNs is not needed.
+
+# --- 11 Inter-PLMN GTP communication over the Gp Interface
+
+Refer to the corresponding section in 3GPP TS 29.060.
+
+# --- 12 IP, the networking technology used by GTP
+
+Refer to the corresponding section in 3GPP TS 29.060.
+
+# --- 13 GTP parameters
+
+The definitions and directions for use of the parameters in GTP (inc. timer values or counter values and so on) on the interface between the IM\_GSN and other nodes is the same as that used in the network without the GLR. See 3GPP TS 29.060.

marked/Rel-18/29_series/29173/raw.md

@@ -0,0 +1,643 @@
+
+
+# 3GPP TS 29.173 V18.0.0 (2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Location Services (LCS); Diameter-based SLh interface for Control Plane LCS (Release 18)**
+
+![LTE logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The LTE logo, featuring the letters 'lte' in a bold, lowercase font. Above the 'l' is a red signal strength icon consisting of four curved lines. A small 'TM' trademark symbol is located to the right of the 'e'.
+
+LTE logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the letters '3GPP' in a stylized, bold, black font. The '3' is larger and positioned to the left of the 'G', 'P', and 'P'. A small red signal strength icon is located below the 'P'. A small 'TM' trademark symbol is located to the top right of the 'P'.
+
+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.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM 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 Definitions.....                                                | 7  |
+| 3.2 Abbreviations .....                                             | 7  |
+| 4 General Description .....                                         | 7  |
+| 4.1 Introduction .....                                              | 7  |
+| 4.2 Architecture Overview .....                                     | 7  |
+| 4.3 Functional Requirements of SLh Interface .....                  | 8  |
+| 5 Diameter-based SLh Interface .....                                | 8  |
+| 5.1 Introduction .....                                              | 8  |
+| 5.2 Procedure Descriptions .....                                    | 8  |
+| 5.2.1 Send Routing Information for LCS .....                        | 8  |
+| 5.2.1.1 General.....                                                | 8  |
+| 5.2.1.2 Detailed Behaviour of the HSS.....                          | 10 |
+| 5.2.1.3 Detailed Behaviour of the GLMC .....                        | 10 |
+| 6 Protocol Specification and Implementations .....                  | 11 |
+| 6.1 Introduction .....                                              | 11 |
+| 6.1.1 Use of Diameter Base Protocol .....                           | 11 |
+| 6.1.2 Securing Diameter Messages .....                              | 11 |
+| 6.1.3 Accounting Functionality .....                                | 11 |
+| 6.1.4 Use of Sessions.....                                          | 11 |
+| 6.1.5 Transport Protocol .....                                      | 11 |
+| 6.1.6 Routing Considerations .....                                  | 11 |
+| 6.1.7 Advertising Application Support.....                          | 11 |
+| 6.1.8 Diameter Application Identifier.....                          | 12 |
+| 6.1.9 User Identity to HSS resolution.....                          | 12 |
+| 6.2 Commands.....                                                   | 12 |
+| 6.2.1 Introduction .....                                            | 12 |
+| 6.2.2 Command-Code values .....                                     | 12 |
+| 6.2.3 LCS-Routing-Info-Request (RIR) Command .....                  | 13 |
+| 6.2.4 LCS-Routing-Info-Answer (RIA) Command.....                    | 13 |
+| 6.3 Result-Code AVP and Experimental-Result AVP Values .....        | 14 |
+| 6.3.1 General .....                                                 | 14 |
+| 6.3.2 Success .....                                                 | 14 |
+| 6.3.3 Permanent Failures .....                                      | 14 |
+| 6.3.3.1 DIAMETER_ERROR_USER_UNKNOWN (5001) .....                    | 14 |
+| 6.3.3.2 DIAMETER_ERROR_UNAUTHORIZED_REQUESTING_NETWORK (5490) ..... | 15 |
+| 6.3.4 Transient Failures .....                                      | 15 |
+| 6.3.4.1 DIAMETER_ERROR_ABSENT_USER (4201) .....                     | 15 |
+| 6.4 AVPs .....                                                      | 15 |
+| 6.4.1 General .....                                                 | 15 |
+| 6.4.2 LMSI.....                                                     | 16 |
+| 6.4.3 Serving-Node.....                                             | 16 |
+| 6.4.4 MME-Name.....                                                 | 16 |
+| 6.4.5 MSC-Number .....                                              | 16 |
+| 6.4.6 LCS-Capabilities-Sets .....                                   | 17 |
+| 6.4.7 GMLC-Address .....                                            | 17 |
+| 6.4.8 Additional-Serving-Node .....                                 | 17 |
+| 6.4.9 PPR-Address.....                                              | 17 |
+| 6.4.10 Feature-List-ID AVP .....                                    | 17 |
+| 6.4.11 Feature-List AVP.....                                        | 17 |
+
+6.4.12 MME-Realm..... 18  
+6.4.13 SGSN-Name ..... 18  
+6.4.14 SGSN-Realm ..... 18  
+**Annex A (informative): Change history..... 19**
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> 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.
+
+# 1 Scope
+
+The present document describes the Diameter-based SLh interface between the GMLC and the HSS defined for the Control Plane LCS in EPC.
+
+LCS procedures over the SLh interface are defined in the 3GPP TS 23.271 [2].
+
+This specification defines the Diameter application for the GMLC-HSS, SLh reference point. The interactions between the HSS and the GMLC are specified, including the signalling flows. As LCS procedures over the Diameter-based SLh interface are identical to the MAP-based Lh interface, the descriptions of the Lh MAP operations defined in the 3GPP TS 29.002 [3] are mapped into the descriptions of the SLh Diameter commands.
+
+# 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.271: "Functional stage 2 description of Location Services (LCS)".
+- [3] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
+- [4] 3GPP TS 29.228: "IP multimedia (IM) Subsystem Cx Interface; Signalling flows and Message Elements".
+- [5] Void.
+- [6] 3GPP TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security".
+- [7] IETF RFC 4960: "Stream Control Transport Protocol".
+- [8] 3GPP TS 29.229: "Cx and Dx Interfaces based on the Diameter protocol; protocol details".
+- [9] 3GPP TS 29.329: "Sh Interface based on the Diameter protocol; protocol details".
+- [10] 3GPP TS 23.003: "Numbering, addressing and identification ".
+- [11] 3GPP TS 23.012: "Location Management Procedures".
+- [12] 3GPP TS 29.272: "Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol".
+- [13] IETF RFC 2234: "Augmented BNF for syntax specifications".
+- [14] Void
+- [15] ITU-T Recommendation E.164: "The international public telecommunication numbering plan".
+- [16] 3GPP TS 29.273: "Evolved Packet System (EPS); 3GPP EPS AAA interfaces".
+- [17] IETF RFC 6733: "Diameter Base Protocol".
+
+# --- 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], 3GPP TS 23.271 [2] 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].
+
+## 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].
+
+|        |                                           |
+|--------|-------------------------------------------|
+| ABNF   | Augmented Backus-Naur form                |
+| AVP    | Attribute Value Pair                      |
+| H-GMLC | Home-Gateway Mobile Location Centre       |
+| IANA   | Internet Assigned Numbers Authority       |
+| PMD    | Pseudonym mediation device functionality  |
+| PPR    | Privacy Profile Register                  |
+| R-GMLC | Requesting-Gateway Mobile Location Centre |
+| RFC    | Request For Comments                      |
+| V-GMLC | Visited-Gateway Mobile Location Centre    |
+
+# --- 4 General Description
+
+## 4.1 Introduction
+
+The SLh reference point between the GMLC and the HSS is defined in the 3GPP TS 23.271 [2].
+
+This document describes the Diameter-based SLh interface related procedures, message parameters and protocol specifications.
+
+## 4.2 Architecture Overview
+
+The architecture for support of Location Services in GSM, UMTS and EPS has been defined in 3GPP TS 23.271 [2] and the relevant network elements and interfaces are shown in the figure 4.2-1.
+
+![Figure 4.2-1: Overview of the LCS Functional Architecture. The diagram shows a central GMLC connected to an HSS via the SLh interface. The GMLC is also connected to seven other entities via various interfaces: Le (External LCS Client), SLg (MME), Lg (SGSN), Lg (MSC/ MSC Server), Lpp (PPR), Lid (PMD), and La (AAA Server).](d0abac95583b52a3b35f74a215567334_img.jpg)
+
+```
+
+graph TD
+    HSS[HSS] -- SLh --> GMLC[GMLC]
+    GMLC -- Le --> ELCS[External LCS Client]
+    GMLC -- SLg --> MME[MME]
+    GMLC -- Lg --> SGSN[SGSN]
+    GMLC -- Lg --> MSC[MSC/ MSC Server]
+    GMLC -- Lpp --> PPR[PPR]
+    GMLC -- Lid --> PMD[PMD]
+    GMLC -- La --> AAA[AAA Server]
+  
+```
+
+Figure 4.2-1: Overview of the LCS Functional Architecture. The diagram shows a central GMLC connected to an HSS via the SLh interface. The GMLC is also connected to seven other entities via various interfaces: Le (External LCS Client), SLg (MME), Lg (SGSN), Lg (MSC/ MSC Server), Lpp (PPR), Lid (PMD), and La (AAA Server).
+
+**Figure 4.2-1: Overview of the LCS Functional Architecture**
+
+In this architecture, the SLh interface is defined between the Gateway Mobile Location Center (GMLC) and the Home Subscriber Server (HSS) to allow the GMLC to request routing information from the HLR or HSS.
+
+## 4.3 Functional Requirements of SLh Interface
+
+The requirements for SLh interface are defined in 3GPP TS 23.271 [2].
+
+The SLh interface is used by the GMLC to request routing information from the HSS i.e. the address of the H-GMLC, and/or the address of the visited MSC/MSC server, SGSN, 3GPP AAA server or MME for a particular target UE whose location has been requested.
+
+# 5 Diameter-based SLh Interface
+
+## 5.1 Introduction
+
+This section describes the Diameter-based SLh interface related procedures and Information elements exchanged between functional entities.
+
+In the tables that describe the Information Elements transported by each Diameter command, each Information Element is marked as (M) Mandatory, (C) Conditional or (O) Optional in the "Cat." column. For the correct handling of the Information Element according to the category type, see the description detailed in section 6 of the 3GPP TS 29.228 [4].
+
+## 5.2 Procedure Descriptions
+
+### 5.2.1 Send Routing Information for LCS
+
+#### 5.2.1.1 General
+
+This procedure is used between the GMLC and the HSS. The procedure is invoked by the GMLC and is used:
+
+- To retrieve routing information for LCS for a specified user from the HSS.
+
+This procedure is mapped to the commands LCS-Routing-Info-Request/Answer in the Diameter application specified in chapter 6. Tables 5.2.1.1/1 and 5.2.1.1/2 detail the involved information elements.
+
+**Table 5.2.1.1/1: Send Routing Information for LCS (SLh-LCS-SRI)**
+
+| Information element name                    | Mapping to Diameter AVP | Cat. | Description                                                                                                             |
+|---------------------------------------------|-------------------------|------|-------------------------------------------------------------------------------------------------------------------------|
+| IMSI                                        | User-Name               | C    | This information element shall contain the IMSI of the targeted user. This IE shall be present if the MSISDN is absent. |
+| MSISDN                                      | MSISDN                  | C    | This information element shall contain the MSISDN of the targeted user. This IE shall be present if the IMSI is absent. |
+| GMLC Number                                 | GMLC-Number             | O    | This information element shall contain the ISDN (E.164) number of the requesting GMLC.                                  |
+| Supported Features (See 3GPP TS 29.229 [8]) | Supported-Features      | O    | If present, this information element shall contain the list of features supported by the origin host.                   |
+
+**Table 5.2.1.1/2: Send Routing Information for LCS (SLh-LCS-SRI) Resp**
+
+| Information element name                    | Mapping to Diameter AVP           | Cat. | Description                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------------------------|-----------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Result (See 5.3.5)                          | Result-Code / Experimental-Result | M    | Result of the request.<br>Result-Code AVP shall be used for errors defined in the Diameter base protocol (see IETF RFC 6733 [17]).<br>Experimental-Result AVP shall be used for SLh errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.                                                                                                |
+| IMSI                                        | User-Name                         | C    | This information element shall contain the IMSI of the targeted user. This IE shall be present if Result-Code is DIAMETER_SUCCESS and the MSISDN is absent.                                                                                                                                                                                                                                                                      |
+| MSISDN                                      | MSISDN                            | C    | This information element shall contain the MSISDN of the targeted user. This IE shall be present if Result-Code is DIAMETER_SUCCESS and the IMSI is absent.                                                                                                                                                                                                                                                                      |
+| LMSI                                        | LMSI                              | C    | This information element shall contain the LMSI allocated by the VLR. This IE should be present if Result-Code is DIAMETER_SUCCESS and LMSI is available in the HSS and MSC-Number is included in the Serving-Node AVP or in an Additional-Serving-Node AVP.                                                                                                                                                                     |
+| Serving Node                                | Serving-Node                      | C    | This information element shall contain the information about the network node serving the targeted user i.e. the name/number of the serving node (MME, SGSN, 3GPP AAA server or MSC/MSC server), the LCS capabilities sets supported by the serving node and the IP address of the visited GMLC associated with the serving node. This IE shall be present if the Result-Code is DIAMETER_SUCCESS; otherwise it shall be absent. |
+| Additional Serving Node                     | Additional-Serving-Node           | C    | This information element shall contain the information about another network node serving the targeted user. This IE may be present if Result-Code is DIAMETER_SUCCESS; otherwise it shall be absent. There may be multiple instances of this IE in the response provided by the HSS.                                                                                                                                            |
+| Home GMLC Address                           | GMLC-Address                      | C    | This information element shall contain the IP address of the H-GMLC. This IE should be present if the Result-Code is DIAMETER_SUCCESS; otherwise it shall be absent.                                                                                                                                                                                                                                                             |
+| PPR Address                                 | PPR-Address                       | C    | This information element shall contain the IP address of the Privacy Profile Register (PPR). This IE should be present if available in the HSS and the Result-Code is DIAMETER_SUCCESS; otherwise it shall be absent.                                                                                                                                                                                                            |
+| RIA Flags                                   | RIA-Flags                         | O    | This Information Element contains a bit mask. See 6.4.15 for the meaning of the bits.                                                                                                                                                                                                                                                                                                                                            |
+| Supported Features (See 3GPP TS 29.229 [8]) | Supported-Features                | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                                                                                                                                                                                            |
+
+#### 5.2.1.2 Detailed Behaviour of the HSS
+
+Upon reception of the Send Routing Info for LCS request, the HSS shall, in the following order:
+
+1. Check whether the requesting GMLC belongs to a network authorized to request UE location information. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_UNAUTHORIZED\_REQUESTING\_NETWORK in the Send Routing Information for LCS Response.
+2. Check that the User Identity for whom data is asked exists in HSS. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN in the Send Routing Information for LCS Response.
+- 2a. If both IMSI and MSISDN are present in the request, check whether they identify the same User. If not, the HSS Result-Code shall be set to DIAMETER\_CONTRADICTING\_AVPS in the Send Routing Information for LCS Response.
+3. Check that there is at least one serving node associated with the targeted user. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_ABSENT\_USER in the Send Routing Information for LCS Response.
+
+If there is an error in any of the above steps then the HSS shall stop processing and shall return the error code specified in the respective step (see 3GPP TS 29.329 [9] and 3GPP TS 29.229 [8] for an explanation of the error codes).
+
+If the HSS cannot fulfil the received request for reasons not stated in the above steps, e.g. due to a database error or empty mandatory data elements, it shall stop processing the request and set Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY.
+
+Otherwise, the requested operation shall take place and the HSS shall return the Result-Code AVP set to DIAMETER\_SUCCESS. The HSS returns one or several of the network addresses of the current MME, SGSN, 3GPP AAA server and/or VMSC/MSC server, the LCS capabilities of the serving nodes if available, the V-GMLC address associated with the serving nodes, if available, and whichever of the IMSI and MSISDN that was not provided in the Send Routing Info for LCS request. If MSISDN was not provided in the Send Routing Info for LCS request and the subscription is MSISDN-less, the HSS shall return the dummy MSISDN value (see 3GPP TS 23.003 [10]). If both MSISDN and IMSI were provided in the Send Routing Info for LCS request, the HSS returns either MSISDN or IMSI or both. The HSS returns the address of the H-GMLC. The HSS also provides the address of the PPR, if available.
+
+The HSS shall include the Diameter Identity of the SGSN (i.e. SGSN-Name and SGSN-Realm), within the Serving-Node AVP or within an Additional-Serving-Node AVP, if and only if the HSS has received an indication that the Lgd interface is supported by the SGSN (see 3GPP TS 29.272 [12]).
+
+The HSS shall include the SGSN Number, within the Serving-Node AVP or Additional Serving-Node AVP, except if the HSS has received an indication that the Lg interface is not supported by the SGSN (see 3GPP TS 29.272 [12]).
+
+If the UE is served by the MME and SGSN parts of the same combined MME/SGSN (see 3GPP TS 29.272 [12] subclause 5.2.2.1.1 for how the HSS determines if the UE is served by the combined MME/SGSN) and if this combined MME/SGSN has indicated the support for optimized LCS procedure (via the Supported-Feature AVP as defined in 3GPP TS 29.272 [12] subclause 7.3.10) and if HSS supports this optimized LCS procedure, then the HSS shall set the "Combined-MME/SGSN-Supporting-Optimized-LCS-Proc" bit of the RIA-Flags.
+
+Regarding the LCS capabilities of the serving nodes, if the HSS registered an SGSN via the S6d reference point (i.e., the registered serving node is an S4-SGSN), the HSS shall set the LCS-Capabilities-Set value to indicate support of Capability Set 5 (i.e., LCS release 7 or later version). If the HSS registered an MME, the HSS shall not indicate any LCS capability value to the GMLC (i.e., the LCS-Capabilities-Set AVP shall be absent over SLh when the serving node is an MME); in this case, the GMLC shall assume that the MME supports LCS Capability Set 5.
+
+#### 5.2.1.3 Detailed Behaviour of the GLMC
+
+If there are a serving node as well as additional serving nodes in a successful Send Routing Info for LCS response, the receiving shall use the serving node in preference to the additional serving nodes.
+
+# 6 Protocol Specification and Implementations
+
+## 6.1 Introduction
+
+### 6.1.1 Use of Diameter Base Protocol
+
+The Diameter base protocol as specified in IETF RFC 6733 [17] shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and error codes as specified in this specification. Unless otherwise specified, the procedures (including error handling and unrecognised information handling) shall be used unmodified.
+
+### 6.1.2 Securing Diameter Messages
+
+For secure transport of Diameter messages, see 3GPP TS 33.210 [6].
+
+### 6.1.3 Accounting Functionality
+
+Accounting functionality (Accounting Session State Machine, related command codes and AVPs) shall not be used on the SLh interface.
+
+### 6.1.4 Use of Sessions
+
+Between the GMLC and the HSS, Diameter sessions shall be implicitly terminated. An implicitly terminated session is one for which the server does not maintain state information. The client shall not send any re-authorization or session termination requests to the server.
+
+The Diameter base protocol as specified in IETF RFC 6733 [17] includes the Auth-Session-State AVP as the mechanism for the implementation of implicitly terminated sessions.
+
+The client (server) shall include in its requests (responses) the Auth-Session-State AVP set to the value NO\_STATE\_MAINTAINED (1), as described in IETF RFC 6733 [17]. As a consequence, the server shall not maintain any state information about this session and the client shall not send any session termination request. Neither the Authorization-Lifetime AVP nor the Session-Timeout AVP shall be present in requests or responses.
+
+### 6.1.5 Transport Protocol
+
+Diameter messages over the SLh interface shall make use of SCTP IETF RFC 4960 [7] as transport protocol.
+
+### 6.1.6 Routing Considerations
+
+This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host.
+
+If GMLC knows the address/name of the HSS for a certain user, both the Destination-Realm AVP and the Destination-Host AVP shall be present in the request. Otherwise, only the Destination-Realm AVP shall be present and the command shall be routed to the next Diameter node. Consequently, the Destination-Host AVP is declared as optional in the ABNF for all requests initiated by a GMLC.
+
+Destination-Realm AVP is declared as mandatory in the ABNF for all requests.
+
+If the Vendor-Specific-Application-ID AVP is received in any of the commands defined in this specification, it shall be ignored by the receiving node, and it shall not be used for routing purposes.
+
+### 6.1.7 Advertising Application Support
+
+The HSS and GMLC shall advertise support of the Diameter SLh Application by including the value of the application identifier in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands.
+
+The vendor identifier value of 3GPP (10415) shall be included in the Supported-Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands, and in the Vendor-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands.
+
+The Vendor-Id AVP included in Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands that is not included in the Vendor-Specific-Application-Id AVPs as described above shall indicate the manufacturer of the Diameter node as per IETF RFC 6733 [17].
+
+### 6.1.8 Diameter Application Identifier
+
+The SLh interface protocol shall be defined as an IETF vendor specific Diameter application, where the vendor is 3GPP. The vendor identifier assigned by IANA to 3GPP (<http://www.iana.org/assignments/enterprise-numbers>) is 10415.
+
+The Diameter application identifier assigned to the SLh interface application is 16777291 (allocated by IANA).
+
+### 6.1.9 User Identity to HSS resolution
+
+The User identity to HSS resolution mechanism enables the GMLC (for non-roaming case) or Diameter Relay/proxy agents in the home network (for roaming case) to find the identity of the HSS that holds the LCS subscription data and routing information for the target user when multiple and separately addressable HSSs have been deployed in the home network. The resolution mechanism is not required in networks that utilise a single HSS.
+
+This User identity to HSS resolution mechanism may rely on routing capabilities provided by Diameter and be implemented in the home operator network within dedicated Diameter Agents (Redirect Agents or Proxy Agents) responsible for determining the HSS identity based on the provided user identity. If this Diameter based implementation is selected by the Home network operator, the principles described in the 3GPP TS 29.272 [12] shall apply.
+
+NOTE: Alternatives to the user identity to HSS resolution Diameter based implementation are outside the scope of this specification.
+
+## 6.2 Commands
+
+### 6.2.1 Introduction
+
+This section defines the Command code values and related ABNF for each command described in this specification.
+
+### 6.2.2 Command-Code values
+
+This section defines Command-Code values for the SLh interface application as allocated by IANA.
+
+Every command is defined by means of the ABNF syntax IETF RFC 2234 [13], according to the Command Code Format (CCF) specification defined in IETF RFC 6733 [17]. In the case, the definition and use of an AVP is not specified in this document, the guidelines in IETF RFC 6733 [17] shall apply.
+
+The Vendor-Specific-Application-Id AVP shall not be included in any command sent by Diameter nodes supporting applications defined in this specification. If the Vendor-Specific-Application-Id AVP is received in any of the commands defined in this specification, it shall be ignored by the receiving node.
+
+NOTE: The Vendor-Specific-Application-Id AVP is included as an optional AVP in all Command Code Format specifications defined in this specification in order to overcome potential interoperability issues with intermediate Diameter agents non-compliant with IETF RFC 6733 [17].
+
+The following Command Codes are defined in this specification:
+
+**Table 6.2.2/1: Command-Code values for SLh**
+
+| <b>Command-Name</b>      | <b>Abbreviation</b> | <b>Code</b> | <b>Section</b> |
+|--------------------------|---------------------|-------------|----------------|
+| LCS-Routing-Info-Request | RIR                 | 8388622     | 6.2.3          |
+| LCS-Routing-Info-Answer  | RIA                 | 8388622     | 6.2.4          |
+
+For these commands, the Application-ID field shall be set to 16777291 (application identifier of the SLh interface application, allocated by IANA).
+
+### 6.2.3 LCS-Routing-Info-Request (RIR) Command
+
+The LCS-Routing-Info-Request (RIR) command, indicated by the Command-Code field set to 8388622 and the "R" bit set in the Command Flags field, is sent from GMLC to HSS.
+
+Message Format
+
+```
+< LCS-Routing-Info-Request > ::= < Diameter Header: 8388622, REQ, PXY, 16777291 >
+
+< Session-Id >
+
+[ Vendor-Specific-Application-Id ]
+
+{ Auth-Session-State }
+
+{ Origin-Host }
+
+{ Origin-Realm }
+
+[ Destination-Host ]
+
+{ Destination-Realm }
+
+[ User-Name ]
+
+[ MSISDN ]
+
+[ GMLC-Number ]
+
+*[ Supported-Features ]
+
+*[ Proxy-Info ]
+
+*[ Route-Record ]
+
+*[ AVP ]
+```
+
+### 6.2.4 LCS-Routing-Info-Answer (RIA) Command
+
+The LCS-Routing-Info-Answer (RIA) command, indicated by the Command-Code field set to 8388622 and the 'R' bit cleared in the Command Flags field, is sent from HSS to GMLC.
+
+Message Format
+
+```
+< LCS-Routing-Info-Answer > ::= < Diameter Header: 8388622, PXY, 16777291 >
+
+< Session-Id >
+
+[ Vendor-Specific-Application-Id ]
+
+[ Result-Code ]
+```
+
+```
+
+[ Experimental-Result ]
+{ Auth-Session-State }
+{ Origin-Host }
+{ Origin-Realm }
+*[ Supported-Features ]
+[ User-Name ]
+[ MSISDN ]
+[ LMSI ]
+[ Serving-Node ]
+*[ Additional-Serving-Node ]
+[ GMLC-Address ]
+[ PPR-Address ]
+[ RIA-Flags ]
+*[ AVP ]
+[ Failed-AVP ]
+*[ Proxy-Info ]
+*[ Route-Record ]
+
+```
+
+## 6.3 Result-Code AVP and Experimental-Result AVP Values
+
+### 6.3.1 General
+
+This section defines result code values that shall be supported by all Diameter implementations that conform to this specification.
+
+### 6.3.2 Success
+
+Result codes that fall within the Success category shall be used to inform a peer that a request has been successfully completed. The Result-Code AVP values defined in the Diameter base protocol specified in IETF RFC 6733 [17] shall be applied.
+
+### 6.3.3 Permanent Failures
+
+Errors that fall within the Permanent Failures category shall be used to inform the peer that the request has failed, and should not be attempted again. The Result-Code AVP values defined in the Diameter base protocol specified in IETF RFC 6733 [17] shall be applied. When one of the result codes defined here is included in a response, it shall be inside an Experimental-Result AVP and the Result-Code AVP shall be absent.
+
+#### 6.3.3.1 DIAMETER\_ERROR\_USER\_UNKNOWN (5001)
+
+This result code shall be sent by the HSS to indicate that the user identified by the IMSI or the MSISDN is unknown. This error code is defined in 3GPP TS 29.229 [8]
+
+#### 6.3.3.2 DIAMETER\_ERROR\_UNAUTHORIZED\_REQUESTING\_NETWORK (5490)
+
+This result code shall be sent by the HSS to indicate that the requesting GMLC's network is not authorized to request UE location information.
+
+### 6.3.4 Transient Failures
+
+Errors that fall within the transient failures category are those used to inform a peer that the request could not be satisfied at the time that it was received. The request may be able to be satisfied in the future.
+
+#### 6.3.4.1 DIAMETER\_ERROR\_ABSENT\_USER (4201)
+
+This result code shall be sent by the HSS to indicate that the location of the targeted user is not known at this time to satisfy the requested operation.
+
+## 6.4 AVPs
+
+### 6.4.1 General
+
+The following table specifies the Diameter AVPs defined for the SLh interface protocol, their AVP Code values, types, possible flag values and whether or not the AVP may be encrypted. The Vendor-ID header of all AVPs defined in this specification shall be set to 3GPP (10415).
+
+For all AVPs which contain bit masks and are of the type Unsigned32, bit 0 shall be the least significant bit. For example, to get the value of bit 0, a bit mask of 0x00000001 should be used.
+
+**Table 6.4.1/1: SLh specific Diameter AVPs**
+
+| Attribute Name          | AVP Code | Section defined | Value Type       | AVP Flag rules |     |            |          |  | May Encr. |
+|-------------------------|----------|-----------------|------------------|----------------|-----|------------|----------|--|-----------|
+|                         |          |                 |                  | Must           | May | Should not | Must not |  |           |
+| LMSI                    | 2400     | 6.4.2           | OctetString      | M, V           |     |            |          |  | No        |
+| Serving-Node            | 2401     | 6.4.3           | Grouped          | M, V           |     |            |          |  | No        |
+| MME-Name                | 2402     | 6.4.4           | DiameterIdentity | M, V           |     |            |          |  | No        |
+| MSC-Number              | 2403     | 6.4.5           | OctetString      | M, V           |     |            |          |  | No        |
+| LCS-Capabilities-Sets   | 2404     | 6.4.6           | Unsigned32       | M, V           |     |            |          |  | No        |
+| GMLC-Address            | 2405     | 6.4.7           | Address          | M, V           |     |            |          |  | No        |
+| Additional-Serving-Node | 2406     | 6.4.8           | Grouped          | M, V           |     |            |          |  | No        |
+| PPR-Address             | 2407     | 6.4.9           | Address          | M, V           |     |            |          |  | No        |
+| MME-Realm               | 2408     | 6.4.12          | DiameterIdentity | V              |     |            | M        |  | No        |
+| SGSN-Name               | 2409     | 6.4.13          | DiameterIdentity | V              |     |            | M        |  | No        |
+| SGSN-Realm              | 2410     | 6.4.14          | DiameterIdentity | V              |     |            | M        |  | No        |
+| RIA-Flags               | 2411     | 6.4.15          | Unsigned32       | V              |     |            | M        |  | No        |
+
+NOTE 1: The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header bit denoted as "V", indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see IETF RFC 6733 [17].
+
+The following table specifies the Diameter AVPs re-used by the SLh interface protocol from existing Diameter Applications, including a reference to their respective specifications and when needed, a short description of their use within SLh.
+
+Any other AVPs from existing Diameter Applications, except for the AVPs from the Diameter base protocol as specified in IETF RFC 6733 [17], do not need to be supported. The AVPs from the Diameter base protocol as specified in IETF RFC 6733 [17] are not included in table 6.4.1/2, but they may be re-used for the SLh protocol.
+
+Table 6.4.1/2: SLh re-used Diameter AVPs
+
+| Attribute Name       | Reference           | Comments           |
+|----------------------|---------------------|--------------------|
+| MSISDN               | 3GPP TS 29.329 [9]  |                    |
+| SGSN-Number          | 3GPP TS 29.272 [12] |                    |
+| Supported-Features   | 3GPP TS 29.229 [8]  |                    |
+| Feature-List-ID      | 3GPP TS 29.229 [8]  | See section 6.4.10 |
+| Feature-List         | 3GPP TS 29.229 [8]  | See section 6.4.11 |
+| GMLC-Number          | 3GPP TS 29.272 [12] |                    |
+| 3GPP-AAA-Server-Name | 3GPP TS 29.273 [16] |                    |
+
+### 6.4.2 LMSI
+
+The LMSI AVP is of type OctetString and it shall contain the Local Mobile Station Identity (LMSI) allocated by the VLR, as defined in 3GPP TS 23.003 [10]. For further details on the encoding of this AVP, see 3GPP TS 23.003[10].
+
+### 6.4.3 Serving-Node
+
+The Serving-Node AVP is of type Grouped. This AVP shall contain the information about the network node serving the targeted user.
+
+AVP format
+
+```
+Serving-Node ::= <AVP header: 2401 10415>
+                [ SGSN-Number ]
+                [ SGSN-Name ]
+                [ SGSN-Realm ]
+                [ MME-Name ]
+                [ MME-Realm ]
+                [ MSC-Number ]
+                [ 3GPP-AAA-Server-Name ]
+                [ LCS-Capabilities-Sets ]
+                [ GMLC-Address ]
+                *[AVP]
+```
+
+The GMLC-Address AVP included in the Serving-Node grouped AVP shall contain, if present, the IPv4 or IPv6 address of the GMLC associated with the serving node (i.e., either the home GMLC or the visited GMLC, depending on the location of the serving node).
+
+### 6.4.4 MME-Name
+
+The MME-Name AVP is of type DiameterIdentity and it shall contain the Diameter identity of the serving MME. For further details on the encoding of this AVP, see IETF RFC 6733 [17].
+
+### 6.4.5 MSC-Number
+
+The MSC-Number AVP is of type OctetString and it shall contain the ISDN number of the serving MSC or MSC server in international number format as described in ITU-T Rec E.164 [15] and shall be encoded as a TBCD-string. See 3GPP TS 29.002 [3] for encoding of TBCD-strings.
+
+### 6.4.6 LCS-Capabilities-Sets
+
+The LCS-Capabilities-Sets AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in 3GPP 29.002 [3].
+
+### 6.4.7 GMLC-Address
+
+The GMLC-Address AVP is of type Address and shall contain the IPv4 or IPv6 address of H-GMLC or the V-GMLC associated with the serving node.
+
+### 6.4.8 Additional-Serving-Node
+
+The Additional-Serving-Node AVP is of type Grouped. This AVP shall contain the information about the network node serving the targeted user.
+
+AVP format
+
+```
+Additional-Serving-Node ::= <AVP header: 2406 10415>
+                        [ SGSN-Number ]
+                        [ MME-Name ]
+                        [ SGSN-Name ]
+                        [ SGSN-Realm ]
+                        [ MME-Realm ]
+                        [ MSC-Number ]
+                        [ 3GPP-AAA-Server-Name ]
+                        [ LCS-Capabilities-Sets ]
+                        [ GMLC-Address ]
+                        *[AVP]
+```
+
+The GMLC-Address AVP included in the Additional-Serving-Node grouped AVP shall contain, if present, the IPv4 or IPv6 address of the GMLC associated with the serving node (i.e., either the home GMLC or the visited GMLC, depending on the location of the serving node).
+
+### 6.4.9 PPR-Address
+
+The PPR-Address AVP is of type Address and contains the IPv4 or IPv6 address of the Privacy Profile Register for the targeted user.
+
+### 6.4.10 Feature-List-ID AVP
+
+The syntax of this AVP is defined in 3GPP TS 29.229 [8]. For this release, the Feature-List-ID AVP value shall be set to 1.
+
+### 6.4.11 Feature-List AVP
+
+The syntax of this AVP is defined in 3GPP TS 29.229 [8]. A null value indicates that there is no feature used by the application.
+
+NOTE: There is no feature defined for this release.
+
+### 6.4.12 MME-Realm
+
+The MME-Realm AVP is of type DiameterIdentity and it shall contain the Diameter Realm Identity of the serving MME. For further details on the encoding of this AVP, see IETF RFC 6733 [17].
+
+### 6.4.13 SGSN-Name
+
+The SGSN-Name AVP is of type DiameterIdentity and it shall contain the Diameter identity of the serving SGSN. For further details on the encoding of this AVP, see IETF RFC 6733 [17].
+
+### 6.4.14 SGSN-Realm
+
+The SGSN-Realm AVP is of type DiameterIdentity and it shall contain the Diameter Realm Identity of the serving SGSN. For further details on the encoding of this AVP, see IETF RFC 6733 [17].
+
+### 6.4.15 RIA-Flags
+
+The RIA-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 6.4.15/1:
+
+**Table 6.4.15/1: RIA-Flags**
+
+| Bit                                                                                                            | Name                                            | Description                                                                                                                                                                      |
+|----------------------------------------------------------------------------------------------------------------|-------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 0                                                                                                              | Combined-MME/SGSN-Supporting-Optimized-LCS-Proc | This bit, when set, indicates that the UE is served by the MME and the SGSN parts of the same combined MME/SGSN and this combined MME/SGSN supports the optimized LCS procedure. |
+| NOTE1: Bits not defined in this table shall be cleared by the sending HSS and discarded by the receiving GMLC. |                                                 |                                                                                                                                                                                  |

marked/Rel-18/29_series/29205/raw.md

@@ -0,0 +1,953 @@
+
+
+# 3GPP TS 29.205 V18.0.0 (2024-03)
+
+Technical Specification
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Application of Q.1900 series to bearer independent Circuit Switched (CS) core network architecture; Stage 3 (Release 18)**
+
+![3GPP logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 3GPP logo, featuring the letters '3GPP' in a stylized font. The '3' is large and bold, with a red signal icon below it. The 'G' and 'P' are also bold, with the 'P' having a small 'TM' symbol above it.
+
+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.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM 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 Definitions.....                                                     | 7         |
+| 3.2 Symbols.....                                                         | 7         |
+| 3.3 Abbreviations .....                                                  | 7         |
+| 4 Protocols.....                                                         | 8         |
+| 4.1 Call control protocol (Nc interface) .....                           | 8         |
+| 4.2 Interworking with other protocols.....                               | 8         |
+| 4.3 Resource control protocol (G)MSC and MGW (Mc Interface) .....        | 8         |
+| 4.4 Bearer control protocol between MGWs (Nb interface).....             | 9         |
+| 4.5 Signalling Transport.....                                            | 9         |
+| 4.5.1 Call Control protocols .....                                       | 9         |
+| 4.5.2 Resource control protocol (G)MSC and MGW (Mc Interface) .....      | 9         |
+| 4.5.3 Bearer control protocol between MGWs (Nb interface) .....          | 9         |
+| <b>Annex A: Void.....</b>                                                | <b>9</b>  |
+| <b>Annex B (normative): Transparent Support of Mobile Services .....</b> | <b>9</b>  |
+| B.1 Introduction.....                                                    | 9         |
+| B.2 Mobile Service Transport (MST) – Format and Codes .....              | 10        |
+| B.2.1 Encapsulated Application Information.....                          | 10        |
+| B.2.1.1 General Layout .....                                             | 10        |
+| B.2.1.2 List of Identifiers .....                                        | 12        |
+| B.2.1.3 Mobile Equipment Identifier .....                                | 12        |
+| B.2.1.4 LCLS Negotiation Request.....                                    | 13        |
+| B.2.1.5 LCLS Negotiation Response .....                                  | 13        |
+| B.2.1.6 LCLS Status.....                                                 | 14        |
+| B.2.1.7 LCLS Status Change .....                                         | 14        |
+| B.2.1.8 LCLS Status Result .....                                         | 14        |
+| B.2.1.9 LCLS Global Call Reference.....                                  | 15        |
+| B.2.1.10 LCLS Configuration Preference.....                              | 16        |
+| B.2.1.11 LCLS Configuration Change Request.....                          | 17        |
+| B.2.1.12 LCLS Configuration Change Result .....                          | 17        |
+| B.2.2 Application Transport Instruction Indicators .....                 | 18        |
+| <b>Annex C (normative): LCLS Service Application .....</b>               | <b>18</b> |
+| C.1 Use of MST ASE .....                                                 | 18        |
+| C.2 Procedures.....                                                      | 18        |
+| C.2.1 Indication of LCLS Capability .....                                | 18        |
+| C.2.1.1 LCLS Service Capability Indication .....                         | 18        |
+| C.2.1.2 Actions at Originating Serving Node .....                        | 19        |
+| C.2.1.3 Actions at Intermediate Serving Node .....                       | 19        |
+| C.2.1.4 Actions at Destination Serving Node .....                        | 19        |
+| C.2.2 Backward LCLS Negotiation during Call Setup.....                   | 20        |
+| C.2.2.1 Introduction .....                                               | 20        |
+| C.2.2.2 Actions at Destination Serving Node .....                        | 20        |
+| C.2.2.3 Actions at Intermediate Serving Node .....                       | 20        |
+| C.2.2.4 Actions at Originating Serving Node .....                        | 20        |
+| C.2.3 Answer message.....                                                | 21        |
+| C.2.3.1 Introduction .....                                               | 21        |
+
+- C.2.3.2 Actions at Destination Serving Node ..... 21
+- C.2.3.3 Actions at Intermediate Serving Node ..... 21
+- C.2.3.4 Actions at Originating Serving Node ..... 21
+- C.2.4 LCLS Configuration Change Request..... 21
+  - C.2.4.1 Introduction ..... 21
+  - C.2.4.2 Actions at Initiating Serving Node ..... 22
+  - C.2.4.3 Actions at Intermediate Serving Node ..... 22
+  - C.2.4.4 Actions at Terminating Serving Node..... 22
+- C.2.5 LCLS Status Update..... 22
+  - C.2.5.1 Introduction ..... 22
+  - C.2.5.2 Actions at Initiating Serving Node ..... 23
+  - C.2.5.3 Actions at Intermediate Serving Node ..... 23
+  - C.2.5.4 Actions at Terminating Serving Node..... 23
+- C.2.6 LCLS Status Change Request ..... 23
+  - C.2.6.1 Introduction ..... 23
+  - C.2.6.2 Actions at Initiating Serving Node ..... 23
+  - C.2.6.3 Actions at Intermediate Serving Node ..... 24
+  - C.2.6.4 Actions at Terminating Serving Node..... 24
+
+**Annex D (informative): Change history ..... 25**
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> 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.
+
+# 1 Scope
+
+The present document describes the protocols to be used when ITU-T Q.1902 "Bearer Independent Call Control" is used as call control protocol in a 3GPP Bearer Independent CS core network 3GPP TS 23.205 [1]. The Q.1902 operates between (G)MSC servers. The BICC architecture as described in ITU-T Q.1902 [6]-[10] consists of a number of protocols. The following types of protocols are described: call control protocol, bearer control protocols and a resource control protocol for this architecture. The architecture complies with the requirements imposed by 3GPP TS 23.205 [1] and TS 23.153 [2].
+
+The present document is valid for a 3<sup>rd</sup> generation PLMN (UMTS) complying with Release 4 and later.
+
+Note: Q.1902 can be used in other network architectures than the one defined in 3GPP TS 23.205 [1]
+
+# 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 TS 23.205: "Bearer Independent CS Core Network – Stage 2".
+- [2] 3GPP TS 23.153: "Out of Band Transcoder Control - Stage 2".
+- [3] 3GPP TS 29.232: "Media Gateway Controller (MGC) – Media Gateway (MGW) Interface; Stage 3".
+- [4] 3GPP TS 29.414: "Core Network Nb Data Transport and Signalling Transport".
+- [5] ITU-T Recommendation Q.765.5 (06/2000): "Application Transport Mechanism".
+- [6] ITU-T Recommendation Q.1902.1 (07/2001): "Bearer Independent Call Control CS2 Functional Description". Inclusive Amendment 3: "Support for the Customized Alerting Tone (CAT) service".
+- [7] ITU-T Recommendation Q.1902.2 (07/2001): "Bearer Independent Call Control CS2 General functions of messages and parameters". Inclusive Amendment 5: "Support for the Customized Alerting Tone (CAT) service".
+- [8] ITU-T Q.1902.3 (07/2001): "Bearer Independent Call Control CS2 Formats and Codes". Inclusive Amendment 5: "Support for the Customized Alerting Tone (CAT) service".
+- [9] ITU-T Recommendation Q.1902.4 (07/2001): "Bearer Independent Call Control CS2 Basic Call Procedures".
+- [10] ITU-T Recommendation Q.1902.5 (07/2001): "Exceptions to the Application Transport Mechanism in the Context of Bearer Independent Call Control".
+- [11] ITU-T Recommendation Q.1902.6 (07/2001): "Generic Signalling Procedures for the support of the ISDN User Part Supplementary Services and for bearer redirection".
+- [12] ITU-T Recommendation Q.1950 (07/2001): "Call Bearer Control Protocol".
+- [13] ITU-T Recommendations Q.2630.1 (12/1999), Q.2630.2 (12/2000): "AAL type 2 signalling protocol".
+
+- [14] ITU-T Recommendation Q.1990 (07/2001): "BICC Bearer Control tunnelling protocol".
+- [15] ITU-T Recommendation Q.1970 (07/2001): "BICC IP Bearer Control protocol".
+- [16] ITU-T Recommendation Q.1912.1 (07/2001): "Interworking between Signalling System No. 7 ISDN user part and the Bearer Independent Call Control protocol".
+- [17] ITU-T Recommendation Q.1912.2 (07/2001): "Interworking between selected Signalling System (PSTN Access DSS1, C5, R1, R2, TUP) and the Bearer Independent Call Control Protocol".
+- [18] ITU-T Recommendation Q.2150.0 (05/2001): "Generic Signalling Transport Service".
+- [19] ITU-T Recommendation Q.2150.1 (05/2001): "Signalling Transport Converter on MTP3 and MTP3b".
+- [20] ITU-T Recommendation Q.2150.3 (12/2002): "Signalling Transport Converter on SCTP".
+- [21] ITU-T Recommendation H.248.4 (11/2000): "Gateway Control Protocol: Transport over SCTP".
+- [22] 3GPP TS 29.202: "SS7 signalling transport in core network".
+- [23] ITU-T Recommendation H.248.5 (11/2000): "Gateway control protocol: Transport over ATM".
+- [24] ITU-T Q.765 (06/2000): "Signalling system No. 7 – Application transport mechanism".
+- [25] 3GPP TS 23.003: "Numbering, addressing and identification".
+- [26] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2".
+- [27] 3GPP TS 23.237: "IP Multimedia subsystem (IMS) Service Continuity; Stage 2".
+- [28] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [29] 3GPP TS 23.284: "Local Call Local Switch; Stage 2".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|    |                                                     |
+|----|-----------------------------------------------------|
+| Nc | Interface between the (G)MSC servers.               |
+| Mc | Interface between the server and the media gateway. |
+| Nb | Interface between media gateways (MGW).             |
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations as defined in 3GPP TR 21.905 [28] 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 [28].
+
+|      |                                  |
+|------|----------------------------------|
+| APM  | Application Transport Mechanism  |
+|      | Application Transport Message    |
+| APP  | Application Transport Parameter  |
+| BAT  | Bearer Association Transport     |
+| BICC | Bearer Independent Call Control  |
+| C5   | CCITT signalling system number 5 |
+| GCR  | Global Call Reference            |
+
+|      |                                      |
+|------|--------------------------------------|
+| LCLS | Local Call Local Switch              |
+| M3UA | MTP3 – User Adaptation Layer         |
+| MGC  | Media Gateway Controller             |
+| MST  | Mobile Service Transport             |
+| R1   | Regional Signalling System 1         |
+| R2   | Regional Signalling System 2         |
+| SCTP | Stream Control Transmission Protocol |
+| SN   | Serving Node                         |
+| TUP  | Telephony User Part                  |
+
+# 4 Protocols
+
+Implementations providing any of the interfaces or protocols identified in the subclauses below shall implement the requirements of the specifications identified in those subclauses.
+
+## 4.1 Call control protocol (Nc interface)
+
+|          |                                                                                                                                                                                                                                           |
+|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Q.1902.1 | BICC PROTOCOL (CS2) FUNCTIONAL DESCRIPTION [6]                                                                                                                                                                                            |
+| Q.1902.2 | BICC PROTOCOL (CS2) AND SIGNALLING SYSTEM NO 7 ISUP<br>GENERAL FUNCTIONS OF MESSAGES AND PARAMETERS [7]                                                                                                                                   |
+| Q.1902.3 | BICC PROTOCOL (CS2) AND SIGNALLING SYSTEM NO 7 ISUP<br>FORMATS AND CODES [8] (NOTE)                                                                                                                                                       |
+| Q.1902.4 | BICC (CS2) BASIC CALL PROCEDURES [9]                                                                                                                                                                                                      |
+| Q.1902.5 | EXCEPTIONS TO THE APM IN THE CONTEXT OF BICC [10]<br>AMENDMENT TO ITU-T RECOMMENDATION Q.765.5 FOR BICC CS2 [5]                                                                                                                           |
+| Q.1902.6 | GENERIC SIGNALLING PROCEDURES AND SUPPORT OF THE ISDN USER PART SUPPLEMENTARY<br>SERVICES WITH THE BEARER INDEPENDENT CALL CONTROL PROTOCOL [11]                                                                                          |
+| NOTE:    | The "Backward CAT indicators" parameter shall be encoded as an optional 3-octet parameter in the ACM, CPG and SEG messages rather than as a 1-octet parameter as incorrectly defined in Amendment 5 of ITU-T Recommendation Q.1902.3 [8]. |
+
+## 4.2 Interworking with other protocols
+
+|          |                                                                                                                                           |
+|----------|-------------------------------------------------------------------------------------------------------------------------------------------|
+| Q.1912.1 | ISUP-BICC INTERWORKING [16]                                                                                                               |
+| Q.1912.2 | INTERWORKING BETWEEN SELECTED SIGNALLING SYSTEMS (PSTN ACCESS DSS1 C5 R1 R2 TUP)<br>AND THE BEARER INDEPENDENT CALL CONTROL PROTOCOL [17] |
+
+## 4.3 Resource control protocol (G)MSC and MGW (Mc Interface)
+
+|                |                                                                              |
+|----------------|------------------------------------------------------------------------------|
+| 3GPP TS 29.232 | "Media Gateway Controller (MGC) – Media Gateway (MGW) Interface;Stage 3" [3] |
+|----------------|------------------------------------------------------------------------------|
+
+## 4.4 Bearer control protocol between MGWs (Nb interface)
+
+|                |                                                                                                                                                                                                                                                                                     |
+|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 3GPP TS 29.414 | "Core Network Nb Data Transport and Signalling Transport" [4] including ITU-T Recommendation Q.1970 "IP bearer control protocol" [15] , ITU-T Recommendation Q.1990 "BICC tunneling control protocol" [14] , ITU-T Recommendation Q.2630.1-2 "AAL type 2 signalling protocol" [13]. |
+|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+## 4.5 Signalling Transport
+
+### 4.5.1 Call Control protocols
+
+|                |                                                                                            |
+|----------------|--------------------------------------------------------------------------------------------|
+| Q.2150.0       | "Generic Signalling Transport Service" [18]                                                |
+| Q.2150.1       | "Signalling Transport Converter on MTP3 and MTP3b" [19]                                    |
+| Q.2150.3       | "Signalling Transport Converter on SCTP" [20]                                              |
+| 3GPP TS 29.202 | "SS7 signalling transport in core network" [22] Annex A: The use of M3UA in 3GPP networks. |
+
+### 4.5.2 Resource control protocol (G)MSC and MGW (Mc Interface)
+
+|                |                                                                                                                                                                                                                                                                                                                        |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 3GPP TS 29.232 | "Media Gateway Controller (MGC) – Media Gateway (MGW) Interface; Stage 3" [3] including ITU-T Recommendation H.248.4 "Transport over SCTP" [21], ITU-T Recommendation H.248.5 "Transport over ATM" [23], and 3GPP TS 29.202 "SS7 signalling transport in core network" [22] Annex A: The use of M3UA in 3GPP networks. |
+|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+### 4.5.3 Bearer control protocol between MGWs (Nb interface)
+
+|                |                                                                                                                                                                                                                   |
+|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 3GPP TS 29.414 | "Core Network Nb Data Transport and signalling transport" [4] including ITU-T Recommendation Q.2630.1-2: "AAL type 2 signalling protocol" [13] and the tunnel-up and tunnel-down procedure in 3GPP TS 29.232 [31] |
+|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+# --- Annex A: Void
+
+# Annex B (normative): Transparent Support of Mobile Services
+
+## B.1 Introduction
+
+This Annex specifies a new mobile APM usage "Transparent support of mobile services".
+
+In ITU-T Recommendation Q.1902.3 [8], for the Application Transport Parameter (APP), the following codepoint is defined to refer to this application context identifier (ACI):
+
+0 0 0 0 1 1 1 MST <as defined in ETSI TS 129.205>
+
+The text in ITU-T Recommendation Q.1902.5 [10] shall be followed when implementing this application with the following clarification:
+
+- where the text refers to BAT ASE this shall be interpreted to mean Mobile Service Transport (MST) service.
+
+The MST service shall use implicit addressing; see ITU-T Recommendation Q.765 [24].
+
+## B.2 Mobile Service Transport (MST) – Format and Codes
+
+### B.2.1 Encapsulated Application Information
+
+#### B.2.1.1 General Layout
+
+The general layout of the Encapsulated Application Information field of the Application Transport parameter as defined in ITU-T Recommendation Q.1902.3 [8] is shown in Table B.2.1.1.1.
+
+**Table B.2.1.1.1: Encapsulated application information field**
+
+| MSB                         |   |   |   |   |   |   |   | LSB |  | Octet |
+|-----------------------------|---|---|---|---|---|---|---|-----|--|-------|
+| 8                           | 7 | 6 | 5 | 4 | 3 | 2 | 1 |     |  |       |
+| Identifier 1                |   |   |   |   |   |   |   |     |  | 1     |
+| Length indicator 1          |   |   |   |   |   |   |   |     |  | 2     |
+| Compatibility information 1 |   |   |   |   |   |   |   |     |  | 3     |
+| Contents 1                  |   |   |   |   |   |   |   |     |  | 4     |
+|                             |   |   |   |   |   |   |   |     |  |       |
+| Identifier n                |   |   |   |   |   |   |   |     |  | m     |
+| Length indicator n          |   |   |   |   |   |   |   |     |  |       |
+| Compatibility information n |   |   |   |   |   |   |   |     |  |       |
+| Contents n                  |   |   |   |   |   |   |   |     |  | p     |
+
+Each information element within the Encapsulated Application Information field has the same structure. An information element consists of four fields which always appear in the following order: Identifier (one octet), Length indicator, Compatibility information, Contents.
+
+The Identifier distinguishes one type from another one and governs the interpretation of the contents. There are two types of Identifiers: type "constructor" and type "simple", for which the contents are defined as follows:
+
+- For a "constructor" type, the Contents field shall again consist of one or more information elements, each of which is structured as described above, i.e., Identifier, Length indicator, Compatibility information, Contents.
+- For a "simple" type, the Contents field contains one value only.
+
+When passing on an information element of type "constructor", the order of the information elements within this "constructor" shall be maintained.
+
+The Length indicator specifies the length (i.e., integral number of octets in pure binary representation) of the Compatibility information and Contents. The length does not include the Identifier nor the Length indicator.
+
+The format of the Length indicator is shown in Table B.2.1.1.2. Bit 8 is defined as Extension indicator and indicates whether or not the information on the length continues through the next octet. Value "0" of the Extension indicator means "*information continues through the next octet*", while value "1" means "*last octet*". The Length indicator itself has a maximum length of 2 octets, i.e., if octet 1a is needed, the Extension indicator of octet 1a is always set to value "1".
+
+**Table B.2.1.1.2: Length indicator**
+
+|        | 8 | 7 | 6 | 5   | 4 | 3 | 2 | 1   | Octet |
+|--------|---|---|---|-----|---|---|---|-----|-------|
+| ext.   |   |   |   |     |   |   |   | LSB | 1     |
+| ext. 1 | 0 | 0 | 0 | MSB |   |   |   |     | 1a    |
+
+The Compatibility information contains corresponding instructions for the case that the received information element is unrecognised. The format of this field is shown in Table B.2.1.1.3.
+
+**Table B.2.1.1.3: Compatibility information**
+
+| 8    | 7                           | 6                     | 5              | 4                           | 3                     | 2 | 1 | Octet |
+|------|-----------------------------|-----------------------|----------------|-----------------------------|-----------------------|---|---|-------|
+| ext. | pass-on not possible        |                       | general action |                             |                       |   |   | 1     |
+|      | send notification indicator | instruction indicator | reserved       | send notification indicator | instruction indicator |   |   |       |
+
+The following codes are used in the subfields of the Compatibility information field.
+
+Bits 2 1 *Instruction indicator for general action*
+
+0 0 Pass on information element
+
+0 1 Discard information element
+
+1 0 Discard MST data
+
+1 1 Release call
+
+Bit 3 *Send notification indicator for general action*
+
+0 Do not send notification
+
+1 Send notification
+
+Bit 4 reserved
+
+Bits 6 5 *Instruction indicator for pass-on not possible*
+
+0 0 Release call
+
+0 1 Discard information element
+
+1 0 Discard MST data
+
+1 1 reserved (interpreted as 00)
+
+Bit 7 *Send notification indicator for pass-on not possible*
+
+0 Do not send notification
+
+1 Send notification
+
+Bit 8 *Extension indicator*
+
+- 0 Information continues through the next octet
+- 1 Last octet
+
+The Contents field is the substance of the element and contains the information the element is intended to convey.
+
+#### B.2.1.2 List of Identifiers
+
+Table B.2.1.2.1 contains the list of Identifiers.
+
+**Table B.2.1.2.1: List of identifiers**
+
+| Value                        | Information element name          | Type   | Reference |
+|------------------------------|-----------------------------------|--------|-----------|
+| 0000 0000                    | spare                             | -      |           |
+| 0000 0001                    | Mobile Equipment Identifier       | simple | B.2.1.3   |
+| 0000 0010                    | LCLS Negotiation Request          | simple | B.2.1.4   |
+| 0000 0011                    | LCLS Negotiation Response         | simple | B.2.1.5   |
+| 0000 0100                    | LCLS Status                       | simple | B.2.1.6   |
+| 0000 0101                    | LCLS Status Change                | simple | B.2.1.7   |
+| 0000 0110                    | LCLS Status Result                | simple | B.2.1.8   |
+| 0000 0111                    | LCLS Global Call Reference        | simple | B.2.1.9   |
+| 0000 1000                    | LCLS Configuration Preference     | simple | B.2.1.10  |
+| 0000 1001                    | LCLS Configuration Change Request | simple | B.2.1.11  |
+| 0000 1010                    | LCLS Configuration Change Result  | simple | B.2.1.12  |
+| 0000 1011<br>to<br>1101 1111 | reserved for 3GPP use             | -      |           |
+| 1110 0000<br>to<br>1111 1111 | reserved for national use         | -      |           |
+
+#### B.2.1.3 Mobile Equipment Identifier
+
+The format of the Mobile Equipment Identifier is shown in Table B.2.1.3.1.
+
+**Table B.2.1.3.1: Mobile Equipment Identifier**
+
+| MSB                         |   |   |   |   |   |   |   | LSB |   |   |   |   |   |   |   | Octet |
+|-----------------------------|---|---|---|---|---|---|---|-----|---|---|---|---|---|---|---|-------|
+| 8                           | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8   | 7 | 6 | 5 | 4 | 3 | 2 | 1 |       |
+| Mobile Equipment Identifier |   |   |   |   |   |   |   |     |   |   |   |   |   |   |   | 1     |
+|                             |   |   |   |   |   |   |   |     |   |   |   |   |   |   |   | ...   |
+|                             |   |   |   |   |   |   |   |     |   |   |   |   |   |   |   | x     |
+
+The MEI contains either the International Mobile station Equipment Identity (IMEI) or the International Mobile station Equipment Identity and Software Version Number (IMEISV) as defined in subclause 6.2 of 3GPP TS 23.003 [25].
+
+Both IMEI and IMEISV are TBCD encoded where IMEI is 15 digits and IMEISV is 16 digits. Bits 5 to 8 of octet n+1 (where n represents the octet of the IMEI(SV) being encoded) encodes digit 2n, bits 1 to 4 of octet n+1 encodes digit 2n-1 (i.e. the order of digits is swapped in each octet compared to the digit order defined in 3GPP TS 23.003 [25]). For IMEI, bits 5 to 8 of the last octet shall be filled with an end mark coded as '1111'.
+
+For the use of the Mobile Equipment Identifier (MEI) see 3GPP TS 23.216 [26] and 3GPP TS 23.237 [27].
+
+#### B.2.1.4 LCLS Negotiation Request
+
+The format of the LCLS Negotiation Request is shown in Table B.2.1.4.1.
+
+**Table B.2.1.4.1: LCLS Negotiation Request**
+
+| MSB                 |       |   |   |   |   |                      | LSB |  |         |
+|---------------------|-------|---|---|---|---|----------------------|-----|--|---------|
+| 8                   | 7     | 6 | 5 | 4 | 3 | 2                    | 1   |  |         |
+| Extension Indicator | Spare |   |   |   |   | Permission Indicator |     |  | Octet 1 |
+
+The LCLS Negotiation Request is sent in the forward direction to indicate LCLS usage permission.
+
+##### Bit 1 2        **Permission Indicator**
+
+|         |                         |
+|---------|-------------------------|
+| 00      | LCLS is allowed         |
+| 01      | LCLS is not allowed     |
+| 10 – 11 | Reserved for future use |
+
+Bit 3 - 7        Spare
+
+##### Bit 8            **Extension Indicator**
+
+|   |                                     |
+|---|-------------------------------------|
+| 0 | information continues in next octet |
+| 1 | last octet                          |
+
+For the use of the LCLS Negotiation Request IE see Annex C.2.1 and 3GPP TS 23.284 [29].
+
+#### B.2.1.5 LCLS Negotiation Response
+
+The format of the LCLS Negotiation Response is shown in Table B.2.1.5.1.
+
+**Table B.2.1.5.1: LCLS Negotiation Response**
+
+| MSB   |   |   |   |   |                      |   | LSB |  |         |
+|-------|---|---|---|---|----------------------|---|-----|--|---------|
+| 8     | 7 | 6 | 5 | 4 | 3                    | 2 | 1   |  |         |
+| Spare |   |   |   |   | Permission Indicator |   |     |  | Octet 1 |
+
+The LCLS Negotiation Response contains information sent in the backwards direction to indicate result of the LCLS Negotiation Request. The LCLS Negotiation Response is coded as follows:
+
+##### Bits 1 2        **Permission Indicator**
+
+|    |                                            |
+|----|--------------------------------------------|
+| 00 | LCLS is allowed                            |
+| 01 | LCLS is not allowed                        |
+| 10 | LCLS is not supported by a subsequent node |
+| 11 | spare                                      |
+
+Bits 3 - 8 Spare
+
+For the use of the LCLS Negotiation Response IE see Annex C.2.2 and 3GPP TS 23.284 [29].
+
+#### B.2.1.6 LCLS Status
+
+The format of the LCLS Status is shown in Table B.2.1.6.1.
+
+**Table B.2.1.6.1: LCLS Status**
+
+| • MSB       |   |   |   |   |   |   |   | • LSB | Octet |
+|-------------|---|---|---|---|---|---|---|-------|-------|
+| 8           | 7 | 6 | 5 | 4 | 3 | 2 | 1 |       |       |
+| LCLS Status |   |   |   |   |   |   |   |       | 1     |
+
+The LCLS Status contains information sent in forward and backward directions to indicate LCLS connection status. The LCLS Status is coded as follows:
+
+| Value     | Meaning                                |
+|-----------|----------------------------------------|
+| 0000 0000 | no indication                          |
+| 0000 0001 | LCLS is feasible but not yet connected |
+| 0000 0010 | LCLS not connected                     |
+| 0000 0011 | LCLS connected                         |
+
+All other values are reserved.
+
+For the use of the LCLS Status IE see Annex C.2.3, C.2.5 and 3GPP TS 23.284 [29].
+
+#### B.2.1.7 LCLS Status Change
+
+The format of the LCLS Status Change is shown in Table B.2.1.7.1.
+
+**Table B.2.1.7.1: LCLS Status Change**
+
+| MSB                |   |   |   |   |   |   |   | LSB | Octet |
+|--------------------|---|---|---|---|---|---|---|-----|-------|
+| 8                  | 7 | 6 | 5 | 4 | 3 | 2 | 1 |     |       |
+| LCLS Status Change |   |   |   |   |   |   |   |     | 1     |
+
+The LCLS Status Change Identifier contains information sent in forward and backward directions to indicate requested change of LCLS connection status. The LCLS Status Change Identifier is coded as follows:
+
+| Value     | Meaning                                     |
+|-----------|---------------------------------------------|
+| 0000 0000 | LCLS connection preparation                 |
+| 0000 0001 | LCLS disconnection preparation              |
+| 0000 0010 | LCLS disconnection preparation for Handover |
+
+All other values are reserved.
+
+For the use of the LCLS Status Change IE see Annex C.2.6 and 3GPP TS 23.284 [29].
+
+#### B.2.1.8 LCLS Status Result
+
+The format of the LCLS Status Result is shown in Table B.2.1.8.1.
+
+**Table B.2.1.8.1: LCLS Status Result**
+
+| MSB   |   |   | LSB                 |   |   |                      |   | Octet |
+|-------|---|---|---------------------|---|---|----------------------|---|-------|
+| 8     | 7 | 6 | 5                   | 4 | 3 | 2                    | 1 |       |
+| Spare |   |   | Rejection Indicator |   |   | Acceptance Indicator |   | 1     |
+
+The LCLS Status Result contains information sent in forward and backward directions to indicate result of the LCLS Status Change Request. The LCLS Status Result is coded as follows:
+
+##### **Bit 1 Acceptance Indicator**
+
+|   |                                     |
+|---|-------------------------------------|
+| 0 | LCLS Status Change request accepted |
+| 1 | LCLS Status Change request rejected |
+
+##### **Bits 2 3 4 5 Rejection Indicator**
+
+|             |                               |
+|-------------|-------------------------------|
+| 0000        | No indication                 |
+| 0001        | Ongoing supplementary service |
+| 0010 – 1111 | Reserved for future use       |
+
+Bits 6 - 8 Spare
+
+For the use of the LCLS Status Result IE see Annex C.2.6 and 3GPP TS 23.284 [29].
+
+#### B.2.1.9 LCLS Global Call Reference
+
+The format of the LCLS Global Call Reference (GCR) is shown in Table B.2.1.9.1.
+
+**Table B.2.1.9.1: LCLS Global Call Reference**
+
+| MSB                                |   |   | LSB |   |   |   |   | Octet         |
+|------------------------------------|---|---|-----|---|---|---|---|---------------|
+| 8                                  | 7 | 6 | 5   | 4 | 3 | 2 | 1 |               |
+| Network ID length indicator        |   |   |     |   |   |   |   | 1             |
+| Network ID                         |   |   |     |   |   |   |   | 2             |
+| (variable length 3 – 5 octets)     |   |   |     |   |   |   |   | 4+m (m=0,1,2) |
+| Node ID length indicator           |   |   |     |   |   |   |   | 5+m           |
+| Node ID                            |   |   |     |   |   |   |   | 6+m           |
+| (fixed length: 2 octets)           |   |   |     |   |   |   |   | 7+m           |
+| Call Reference ID length indicator |   |   |     |   |   |   |   | 8+m           |
+|                                    |   |   |     |   |   |   |   | 9+m           |
+| Call Reference ID                  |   |   |     |   |   |   |   |               |
+| (fixed length: 5 octets)           |   |   |     |   |   |   |   | 13+m          |
+
+The LCLS GCR is information sent in forward direction to uniquely identify a call and correlate activities associated with that call. The LCLS GCR is coded as follows:
+
+- Network ID length indicator  
+Binary coded information indicating the number of octets in the Network ID field.
+- Network ID  
+Information identifying a network. The Network ID field is specified in ITU-T Recommendation Q.1902.3 [8].
+- Node ID length Indicator  
+Binary coded information indicating the number of octets in the Node ID field.
+
+- Node ID  
+A binary number that uniquely identifies within the network the node which generates the call reference.
+- Call Reference ID length indicator  
+Binary coded information indicating the number of octets in the Call Reference ID field.
+- Call Reference ID  
+A binary number used for the call reference of the call. It is generated by the originating serving node for each call.
+
+NOTE: If the originating serving radio access is GERAN the format of the Call Reference ID subfield is shown in Table B.2.1.9.2. The originating BSS ID is an integer that uniquely identifies the Base Station Subsystem (BSS) Node within an operator's network.
+
+**Table B.2.1.9.2: Call Reference ID**
+
+| MSB                                            |   |   |   |   |   |   |   | LSB |   |   |   |   |   |   |   | Octet |
+|------------------------------------------------|---|---|---|---|---|---|---|-----|---|---|---|---|---|---|---|-------|
+| 8                                              | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 8   | 7 | 6 | 5 | 4 | 3 | 2 | 1 |       |
+| Call Identifier<br>(fixed length: 3 octets)    |   |   |   |   |   |   |   |     |   |   |   |   |   |   |   | 1     |
+|                                                |   |   |   |   |   |   |   |     |   |   |   |   |   |   |   | 2     |
+|                                                |   |   |   |   |   |   |   |     |   |   |   |   |   |   |   | 3     |
+| Originating BSS ID<br>(fixed length: 2 octets) |   |   |   |   |   |   |   |     |   |   |   |   |   |   |   | 4     |
+|                                                |   |   |   |   |   |   |   |     |   |   |   |   |   |   |   | 5     |
+
+For the use of the LCLS GCR IE see Annex C.2.1 and 3GPP TS 23.284 [29].
+
+#### B.2.1.10 LCLS Configuration Preference
+
+The format of the LCLS Configuration Preference is shown in Table B.2.1.10.1.
+
+**Table B.2.1.10.1: LCLS Configuration Preference**
+
+| MSB                 |       |   |   | LSB                               |                                  |                                 |                                | Octet |
+|---------------------|-------|---|---|-----------------------------------|----------------------------------|---------------------------------|--------------------------------|-------|
+| 8                   | 7     | 6 | 5 | 4                                 | 3                                | 2                               | 1                              |       |
+| Extension Indicator | Spare |   |   | Backward Data Reception Indicator | Forward Data Reception Indicator | Backward Data Sending Indicator | Forward Data Sending Indicator | 1     |
+
+The LCLS Configuration Preference contains information sent in forward and backward directions to indicate negotiated LCLS configuration preference.
+
+##### Bit 1 Forward Data Sending Indicator
+
+0 not required  
+1 required
+
+##### Bit 2 Backward Data Sending Indicator
+
+0 not required  
+1 required
+
+##### Bit 3 Forward Data Reception Indicator
+
+0 not required  
+1 required
+
+##### Bit 4 Backward Data Reception Indicator
+
+0 not required  
+1 required
+
+Bits 5 - 7 Spare
+
+**Bit 8 Extension Indicator**  
+0 information continues in next octet  
+1 last octet
+
+For the use of the LCLS Configuration Preference IE see Annex C.2.1, C.2.2, C.2.4 and 3GPP TS 23.284 [29].
+
+#### B.2.1.11 LCLS Configuration Change Request
+
+The format of the LCLS Configuration Change Request is shown in Table B.2.1.11.1.
+
+**Table B.2.1.11.1: LCLS Configuration Change Request**
+
+| MSB                 | LSB   |   |   |   |   |   |      | Octet |
+|---------------------|-------|---|---|---|---|---|------|-------|
+| 8                   | 7     | 6 | 5 | 4 | 3 | 2 | 1    |       |
+| Extension Indicator | Spare |   |   |   |   |   | Type | 1     |
+
+The LCLS Configuration Change Request contains information sent in the forward and backward directions to indicate type of LCLS Configuration Change Request.
+
+**Bit 1 2 Type**  
+00 LCLS Configuration Preference Modification Request  
+01 - 11 Spare
+
+Bit 3 - 7 Spare
+
+**Bit 8 Extension Indicator**  
+0 information continues in next octet  
+1 last octet
+
+For the use of the LCLS Configuration Change Request IE see Annex C.2.4 and 3GPP TS 23.284 [29].
+
+#### B.2.1.12 LCLS Configuration Change Result
+
+The format of the LCLS Configuration Change Result is shown in Table B.2.1.12.1.
+
+**Table B.2.1.12.1: LCLS Configuration Change Result**
+
+| MSB   |   |                     |   |   |   |   | LSB                  | Octet |
+|-------|---|---------------------|---|---|---|---|----------------------|-------|
+| 8     | 7 | 6                   | 5 | 4 | 3 | 2 | 1                    |       |
+| Spare |   | Rejection Indicator |   |   |   |   | Acceptance Indicator | 1     |
+
+The LCLS Configuration Change Result contains information sent in the backward direction to indicate result of the LCLS Configuration Change Request. The LCLS Configuration Change Result is coded as follows:
+
+**Bit 1 Acceptance Indicator**  
+0 LCLS Configuration Change request accepted  
+1 LCLS Configuration Change request rejected (if set then Rejection Indicator provides further details)
+
+**Bits 2 3 4 5 Rejection Indicator**
+
+|             |                                            |
+|-------------|--------------------------------------------|
+| 0000        | No indication                              |
+| 0001        | Requested LCLS configuration not supported |
+| 0010        | Ongoing supplementary service              |
+| 0011 – 1111 | Reserved for future use                    |
+| Bits 6 - 8  | Spare                                      |
+
+For the use of the LCLS Configuration Change Result IE see Annex C.2.4 and 3GPP TS 23.284 [29].
+
+### B.2.2 Application Transport Instruction Indicators
+
+For the MST service the Application Transport Instruction Indicators (ATII) shall be set as follows:
+
+|      |   |                                          |
+|------|---|------------------------------------------|
+| Bits | 1 | <i>Release call indicator (RCI)</i>      |
+|      | 0 | do not release call                      |
+| Bit  | 2 | <i>Send notification indicator (SNI)</i> |
+|      | 0 | do not send notification                 |
+
+# --- Annex C (normative): LCLS Service Application
+
+LCLS Service is defined in 3GPP TS 23.284 [29] and is dependent on the following identifiers being included in BICC/ISUP messaging. The following sections describe the detailed protocol behaviour when these identifiers are included.
+
+## --- C.1 Use of MST ASE
+
+LCLS service makes use of the services of the MST ASE described in Annex B. The services of the MST ASE are accessed by means of primitives (such as "MST\_data") which are the same as BAT ASE primitives defined in ITU-T Recommendation Q.765.5 [5].
+
+## --- C.2 Procedures
+
+### C.2.1 Indication of LCLS Capability
+
+#### C.2.1.1 LCLS Service Capability Indication
+
+LCLS service shall be used for a call if MST\_data primitive associated with an IAM includes LCLS Information Elements: a LCLS GCR, a LCLS Negotiation Request and a LCLS Configuration Preference. The absence of the LCLS Negotiation, the LCLS Configuration Preference and the LCLS GCR Information Elements in the IAM specifies that the LCLS service shall not be used.
+
+The compatibility information of the LCLS Negotiation Request, the LCLS Configuration Preference and the LCLS GCR Information Elements shall be set so as to cause the Information Element to be discarded by nodes that do not support LCLS service.
+
+The procedures for call establishment using the LCLS service are described in 3GPP TS 23.284 [29].
+
+#### C.2.1.2 Actions at Originating Serving Node
+
+An originating Serving Node (SN) that supports the LCLS service shall indicate this within the IAM message of the mobile originating call by including the LCLS Negotiation Request, the LCLS Configuration Preference and the LCLS GCR Information Elements within the MST Application Transport Parameter (APP) within the IAM.
+
+When the LCLS service is allowed to be used the IAM is sent to the succeeding node with the Permission Indicator of the LCLS Negotiation Request Information Element set to "LCLS is allowed".
+
+Depending on network requirements the originating SN may additionally indicate required configurations for user plane connectivity towards originating or terminating UE within the LCLS Configuration Preference Information Element. If the originating MSC server needs to:
+
+- send data towards the terminating UE it shall set Forward Data Sending Indicator to "required";
+- send data towards the originating UE it shall set Backward Data Sending Indicator to "required";
+- receive data from the originating UE it shall set Forward Data Reception Indicator to "required";
+- receive data from the terminating UE it shall set Backward Data Reception Indicator to "required".
+
+The originating SN shall perform the setting of LCLS Configuration Preference Information Element according to rules specified in sub-clause 4.2 of 3GPP TS 23.284 [29] or it may determine that LCLS is not allowed and indicate this by setting the value of Permission Indicator of the LCLS Negotiation Request Information Element to "LCLS is not allowed".
+
+#### C.2.1.3 Actions at Intermediate Serving Node
+
+For the intermediate Serving Node (SN), LCLS service indication (i.e. LCLS GCR, LCLS Negotiation Request and LCLS Configuration Preference Information Elements) shall be included only if received from the preceding node and if the node itself supports the LCLS service.
+
+The intermediate SN shall not change the LCLS GCR Information Element. If the intermediate SN receives Permission Indicator of the LCLS Negotiation Request Information Element set to "LCLS is not allowed" it shall not change it.
+
+Depending on network requirements the intermediate SN may additionally indicate required configurations for user plane connectivity towards originating or terminating UE by changing the received LCLS Configuration Preference Information Element. If the intermediate SN needs to:
+
+- send data towards the terminating UE it shall set Forward Data Sending Indicator to "required";
+- send data towards the originating UE it shall set Backward Data Sending Indicator to "required";
+- receive data from the originating UE it shall set Forward Data Reception Indicator to "required";
+- receive data from the terminating UE it shall set Backward Data Reception Indicator to "required".
+
+If the intermediate SN receives any of these indicators set to "required" it shall not change them.
+
+#### C.2.1.4 Actions at Destination Serving Node
+
+For the destination Serving Node (SN), LCLS service shall be supported only if the IAM with the LCLS Negotiation Request, LCLS Configuration Preference and LCLS GCR Information Elements within the MST Application Transport Parameter (APP) is received from the preceding node and if the node itself supports the LCLS service.
+
+Depending on network requirements the destination SN may additionally modify received configurations for user plane connectivity towards originating or terminating UE, by changing the settings of the LCLS Configuration Preference Information Element. If the destination SN needs to:
+
+- send data towards the terminating UE it shall set Forward Data Sending Indicator to "required";
+- send data towards the originating UE it shall set Backward Data Sending Indicator to "required";
+- receive data from the originating UE it shall set Forward Data Reception Indicator to "required";
+
+- receive data from the terminating UE it shall set Backward Data Reception Indicator to "required".
+
+If the destination SN receives any of these indicators set to "required" it shall not change them.
+
+The destination SN shall perform modification of LCLS Configuration Preference Information Element according to rules specified in sub-clause 4.2 of 3GPP TS 23.284 [29] or it may determine that LCLS is not allowed and shall indicate this by setting the value of Permission Indicator of the LCLS Negotiation Response Information Element to "LCLS is not allowed".
+
+### C.2.2 Backward LCLS Negotiation during Call Setup
+
+#### C.2.2.1 Introduction
+
+LCLS service shall be used for a call if MST\_data primitive associated with first backward (APM or ACM) message includes a LCLS Negotiation Response and a LCLS Configuration Preference Information Elements. The absence of the LCLS Negotiation Response and the LCLS Configuration Preference Information Elements in the first backward message specifies that the LCLS service shall not be used.
+
+The compatibility information of the LCLS Negotiation Response and the LCLS Configuration Preference Information Elements shall be set so as to cause the Information Element to be discarded by nodes that do not support LCLS service.
+
+#### C.2.2.2 Actions at Destination Serving Node
+
+If LCLS service is supported according to conditions specified in sub-clause C.2.1.4 a destination SN shall include in the first backward message (APM or ACM) the LCLS Negotiation Response and the LCLS Configuration Preference Information Elements in the MST\_Data request primitive.
+
+#### C.2.2.3 Actions at Intermediate Serving Node
+
+If LCLS service is supported according to conditions specified in sub-clause C.2.1.3 but a succeeding node does not return LCLS Negotiation Response Information Element in the first backward message, an Intermediate SN shall include the LCLS Negotiation Response Information Element. The Permission Indicator of the LCLS Negotiation Response Information Element shall be set to "LCLS is not supported by a subsequent node".
+
+On receipt of a backward message (APM, ACM or CPG) with the LCLS Negotiation Response and the LCLS Configuration Preference Information Elements the Intermediate SN shall store the LCLS configuration settings from the LCLS Configuration Preference Information Element and shall forward the LCLS Negotiation Response and the LCLS Configuration Preference Information Elements unchanged.
+
+#### C.2.2.4 Actions at Originating Serving Node
+
+If the first backward message does not contain the LCLS Negotiation Response and the LCLS Configuration Preference Information Elements the originating SN shall assume that LCLS is not supported by succeeding node and LCLS shall not be performed for that call; no further LCLS signalling shall take place for that call.
+
+If the first backward message contains the LCLS Negotiation Response Information Element but the Permission Indicator is set to "LCLS Not Allowed" or "LCLS is not supported by a subsequent node" then the originating SN shall not request establishment of the LCLS connection at this time.
+
+NOTE: A subsequent LCLS Negotiation Response Information Element can be received from succeeding nodes, e.g. in the event of a call forwarding on no reply.
+
+### C.2.3 Answer message
+
+#### C.2.3.1 Introduction
+
+LCLS connection may be established for a call if MST\_data primitive associated with an ANM includes a LCLS Status Identifier Information Element. The absence of the LCLS Status Identifier Information Element in the ANM specifies that the LCLS connection shall not be requested.
+
+The compatibility information of the LCLS Status Identifier shall be set so as to cause the Information Element to be discarded by nodes that do not support LCLS service.
+
+#### C.2.3.2 Actions at Destination Serving Node
+
+If a destination SN determines that LCLS service is feasible according to the conditions specified in sub-clause 6.2.1.3.4 of 3GPP TS 23.284 [29] it shall include the LCLS Status Identifier Information Element set to "LCLS feasible but not yet connected" within the MST Application Transport Parameter (APP) within the ANM.
+
+#### C.2.3.3 Actions at Intermediate Serving Node
+
+An Intermediate SN shall pass the LCLS Status Identifier within the ANM unchanged.
+
+#### C.2.3.4 Actions at Originating Serving Node
+
+When an originating SN receives an ANM with the LCLS Status Identifier indicating the LCLS service is feasible it shall request LCLS connection.
+
+### C.2.4 LCLS Configuration Change Request
+
+#### C.2.4.1 Introduction
+
+Modification of a LCLS configuration can only occur after the LCLS negotiation has been performed during the call set-up phase according to the procedures described in sub-clauses C.2.1 and C.2.2. A SN involved in a LCLS Configuration Change procedure must not initiate a new LCLS Configuration Change Request until the existing LCLS Configuration Change procedure has been completed.
+
+A LCLS Configuration Change Request message may be sent in either direction and at any time during the active phase of a call, after the LCLS negotiation has been performed during the call establishment. A LCLS Configuration Change Request and a LCLS Configuration Preference Information Elements indicating the requested change of the LCLS configuration shall be included in a MST\_data primitive, corresponding to an APM message.
+
+A MST\_Data primitive, corresponding to the APM message shall be issued in response, including the LCLS Configuration Preference and the LCLS Configuration Change Result Information Elements indicating if the requested change of LCLS configuration has been accepted and if it has not been accepted the reason for rejection.
+
+The compatibility information of the LCLS Configuration Preference, the LCLS Configuration Change Request and LCLS Configuration Change Result Information Elements shall be set so as to cause the Information Element to be discarded and send notification by nodes that do not support LCLS service.
+
+NOTE: The term "initiating" SN in the following clauses refers to a SN which initiates the LCLS Configuration Change Request. The term "terminating" SN in the following clauses refers to a SN which terminates the LCLS Configuration Change Request.
+
+#### C.2.4.2 Actions at Initiating Serving Node
+
+If a SN determines that LCLS configuration needs to be changed it may send an APM message which includes a LCLS Configuration Change Request and the LCLS Configuration Preference Information Elements to its succeeding and/or preceding node. The initiating SN shall set the desired configurations as described in sub-clause C.2.1.2.
+
+The LCLS Configuration Change Request may only be initiated if LCLS Negotiation was performed during call establishment.
+
+NOTE: this does not require that LCLS was permitted during the call establishment.
+
+On receipt of an APM message containing the LCLS Configuration Preference and the LCLS Configuration Change Result Information Elements, if the result indicates "accepted" the modification of the LCLS Configuration settings has been successful. If the LCLS Configuration Change Result Information Element indicates "rejected" the initiating SN shall resume the LCLS connection with the LCLS configuration unchanged.
+
+#### C.2.4.3 Actions at Intermediate Serving Node
+
+When an intermediate SN receives an APM message with the LCLS Configuration Change Request and the LCLS Configuration Preference Information Elements requesting a certain LCLS Configuration Change the intermediate SN shall check if it can support the requested LCLS configuration. If the intermediate SN can support the proposed LCLS configuration it shall forward the LCLS Configuration Preference and the LCLS Configuration Change Request Information Elements to its succeeding or preceding node. If the intermediate SN cannot support/permit the proposed LCLS configuration it shall respond with a LCLS Configuration Change Result Information Element set to "LCLS Configuration Change request rejected" along with the Rejection Indicator detailing the reason for rejection.
+
+On receipt of an APM message with the LCLS Configuration Change Result and LCLS Configuration Preference Information Elements from its succeeding/preceding node if the LCLS Configuration Change Result Information Element indicates "accepted" the intermediate SN shall store the LCLS configuration settings from the LCLS Configuration Preference Information Element and shall forward the APM message to its preceding/succeeding node.
+
+If the LCLS Configuration Change Result Information Element indicates "rejected" the intermediate SN shall resume the LCLS connection with the LCLS configuration unchanged and the intermediate SN shall forward the APM message to its preceding/succeeding node.
+
+#### C.2.4.4 Actions at Terminating Serving Node
+
+When an SN which is a terminating SN with respect to a LCLS Configuration Change Request receives an APM message with the LCLS Configuration Change Request and LCLS Configuration Preference Information Elements requesting a certain LCLS Configuration Change the terminating SN shall check if it can support the requested LCLS configuration.
+
+If the terminating SN can support the proposed LCLS configuration change it shall return the LCLS Configuration Preference Information Element and the LCLS Configuration Change Result Information Element indicating acceptance of the LCLS Configuration Change to its succeeding or preceding node. If the terminating SN cannot support/permit the proposed LCLS configuration it shall respond with a LCLS Configuration Change Result Information Element set to "LCLS Configuration Change request rejected" along with the Rejection Indicator detailing the reason for rejection.
+
+### C.2.5 LCLS Status Update
+
+#### C.2.5.1 Introduction
+
+A LCLS Status Update message may be sent in either direction to indicate that a LCLS connection status has been changed. A LCLS Status Identifier Information Element indicating the new LCLS connection status value shall be included in a MST\_data primitive, corresponding to an APM message.
+
+The compatibility information of the LCLS Status Identifier shall be set so as to cause the Information Element to be discarded and send notification by nodes that do not support LCLS service.
+
+NOTE: The term "initiating" SN in the following clauses refers to an originating SN or a destination SN that may initiate the LCLS Status Update message. The term "terminating" SN in the following clauses refers to an originating SN or a destination SN that may receive the LCLS Status Update message.
+
+#### C.2.5.2 Actions at Initiating Serving Node
+
+If a SN determines that the LCLS connection status has been changed it shall send the new LCLS connection status value to an adjacent SN. An initiating SN shall send the LCLS Status Identifier Information Element within the MST Application Transport Parameter (APP) within the APM message.
+
+#### C.2.5.3 Actions at Intermediate Serving Node
+
+When an intermediate SN receives the APM message with the LCLS Status Identifier Information Element from the preceding/succeeding SN and if the same LCLS connection status value has not been already received from the succeeding/preceding SN, the intermediate SN shall store the new LCLS Connection status value and shall pass the LCLS Status Identifier Information Element within the APM message unchanged to its succeeding/preceding SN.
+
+#### C.2.5.4 Actions at Terminating Serving Node
+
+When a terminating SN receives the APM message with the LCLS Status Identifier Information Element from the adjacent SN, it shall update its LCLS connection status value.
+
+### C.2.6 LCLS Status Change Request
+
+#### C.2.6.1 Introduction
+
+A LCLS Status Change Request message may be sent in either direction and at any time during the active phase of a call, after the LCLS has been initially established. A LCLS Status Change Identifier Information Element indicating the requested change of the LCLS connection status shall be included in a MST\_data primitive, corresponding to an APM message.
+
+An MST\_Data primitive, corresponding to the APM message shall be issued in response, including the LCLS Status Change Identifier Information Element and a LCLS Status Result Identifier Information Element indicating if the requested change of LCLS connection status has been accepted and if it has not been accepted the reason for rejection.
+
+The compatibility information of the LCLS Status Change Identifier and the LCLS Status Result Identifier shall be set so as to cause the Information Element to be discarded and send notification by nodes that do not support LCLS service.
+
+NOTE: The term "initiating" SN in the following clauses refers to a SN which initiates the LCLS Status Change. The term "terminating" SN in the following clauses refers to a SN which terminates the LCLS Status Change.
+
+#### C.2.6.2 Actions at Initiating Serving Node
+
+When a SN determines that the LCLS connection status needs to be changed, it shall request the change of the LCLS connection status from its preceding and/or succeeding SN. An initiating SN shall send the LCLS Status Change Identifier Information Element within the MST Application Transport Parameter (APP) within an APM message.
+
+An APM message containing the LCLS Status Change Identifier Information Element and a LCLS Status Result Identifier Information Element will be received in response from the succeeding and/or preceding SN.
+
+If initiating SN is an SN serving a Radio Network (originating SN or destination SN), upon reception of the LCLS Status Result Identifier Information Element indicating the acceptance of the requested LCLS connection status change, the initiating SN shall change the LCLS connection status.
+
+NOTE: This change of LCLS connection status can be deferred until signalling interaction with the served Radio Network Controller, which is outside of the scope of this specification.
+
+#### C.2.6.3 Actions at Intermediate Serving Node
+
+When an intermediate SN receives from a preceding/succeeding SN an APM message that includes a LCLS Status Change Identifier Information Element within the MST Application Transport Parameter (APP) it shall check if it can support the required change of the LCLS connection status.
+
+If the intermediate SN cannot support the requested change of the LCLS connection status it shall respond to the preceding/succeeding SN with the APM message containing the LCLS Status Change Identifier Information Element and a LCLS Status Result Identifier Information Element with an Acceptance indicator set to "LCLS Status Change request rejected" along with a Rejection Indicator detailing the reason for rejection.
+
+If the intermediate SN can support the required change of the LCLS connection status it shall pass the LCLS Status Change Identifier Information Element within the APM message unchanged to its succeeding/preceding SN. An APM message will be received in response, including the LCLS Status Change Identifier Information Element and a LCLS Status Result Identifier Information Element from its succeeding/preceding SN. The intermediate SN shall pass the LCLS Status Change Identifier Information Element and the LCLS Status Result Identifier Information Element within the APM message unchanged to its succeeding/preceding SN.
+
+#### C.2.6.4 Actions at Terminating Serving Node
+
+Upon reception of an APM message that includes a LCLS Status Change Identifier Information Element, from the adjacent SN, a terminating SN shall check if it can support the required change of the LCLS connection status.
+
+If the terminating SN can support the required change, it shall change the LCLS connection status. If the result of the LCLS connection status change is successful the terminating SN shall send to the adjacent SN the APM message with the LCLS Status Change Identifier Information Element and a LCLS Status Result Identifier Information Element indicating the acceptance of the requested LCLS connection status change.
+
+NOTE: If the terminating SN is an SN serving a Radio Network (originating SN or destination SN), there can be additional signalling with the served Radio Network Controller, prior to responding to the LCLS Status Change Request; this is, however, outside of the scope of this specification.
+
+If the result of the LCLS connection status change is unsuccessful or if the terminating SN cannot support the required change it shall respond to the adjacent SN with the APM message containing the LCLS Status Change Identifier Information Element and a LCLS Status Result Identifier Information Element with an Acceptance indicator set to "LCLS Status Change request rejected" along with a Rejection Indicator detailing the reason for rejection.

marked/Rel-18/29_series/29217/raw.md

@@ -0,0 +1,938 @@
+
+
+# 3GPP TS 29.217 V18.0.0 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Policy and Charging Control (PCC); Congestion reporting over Np reference point (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 3<sup>rd</sup> 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.
+
+## --- **Keywords**
+
+LTE, Policy
+
+### **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.
+
+© 2024, 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 and abbreviations .....                                          | 7  |
+| 3.1 Definitions.....                                                           | 7  |
+| 3.2 Abbreviations .....                                                        | 7  |
+| 4 Np reference point.....                                                      | 7  |
+| 4.1 Overview .....                                                             | 7  |
+| 4.2 Np reference model .....                                                   | 8  |
+| 4.3 Functional elements.....                                                   | 8  |
+| 4.3.1 RCAF.....                                                                | 8  |
+| 4.3.2 PCRF .....                                                               | 9  |
+| 4.3.3 H-PCRF .....                                                             | 9  |
+| 4.3.4 V-PCRF .....                                                             | 9  |
+| 4.4 Procedures over Np reference point.....                                    | 9  |
+| 4.4.1 RUCI Report.....                                                         | 9  |
+| 4.4.1.1 General.....                                                           | 9  |
+| 4.4.1.2 Non-aggregated RUCI report.....                                        | 10 |
+| 4.4.1.3 Aggregated RUCI report.....                                            | 10 |
+| 4.4.2 Reporting Restriction Provisioning .....                                 | 10 |
+| 4.4.3 UE mobility between RCAFs.....                                           | 11 |
+| 4.4.4 Removal of UE context .....                                              | 11 |
+| 4.4.5 Race condition handling .....                                            | 12 |
+| 5 Np protocol .....                                                            | 12 |
+| 5.1 Protocol support .....                                                     | 12 |
+| 5.2 Initialization, maintenance and termination of connection and session..... | 12 |
+| 5.3 Np specific AVPs.....                                                      | 13 |
+| 5.3.1 General .....                                                            | 13 |
+| 5.3.2 Aggregated-Congestion-Info AVP .....                                     | 13 |
+| 5.3.3 Aggregated-RUCI-Report AVP .....                                         | 13 |
+| 5.3.4 Congestion-Level-Definition AVP.....                                     | 14 |
+| 5.3.5 Congestion-Level-Range AVP.....                                          | 14 |
+| 5.3.6 Congestion-Level-Set-Id AVP .....                                        | 14 |
+| 5.3.7 Congestion-Level-Value AVP.....                                          | 14 |
+| 5.3.8 Congestion-Location-Id AVP.....                                          | 15 |
+| 5.3.9 Conditional-Restriction AVP .....                                        | 15 |
+| 5.3.10 eNodeB-Id AVP .....                                                     | 15 |
+| 5.3.11 IMSI-List AVP .....                                                     | 15 |
+| 5.3.12 RCAF-Id AVP .....                                                       | 16 |
+| 5.3.13 Reporting-Restriction AVP .....                                         | 16 |
+| 5.3.14 RUCI-Action AVP .....                                                   | 16 |
+| 5.3.15 Extended-eNodeB-Id AVP .....                                            | 17 |
+| 5.4 Np re-used AVPs.....                                                       | 17 |
+| 5.4.1 General .....                                                            | 17 |
+| 5.4.2 Use of the Supported-Features AVP on the Np reference point.....         | 18 |
+| 5.5 Np specific Experimental-Result-Code AVP values .....                      | 19 |
+| 5.5.1 General .....                                                            | 19 |
+| 5.5.2 Success .....                                                            | 19 |
+| 5.5.3 Permanent Failures .....                                                 | 19 |
+| 5.5.4 Transient Failures .....                                                 | 19 |
+| 5.6 Np messages.....                                                           | 19 |
+| 5.6.0 Command-Code Values.....                                                 | 19 |
+| 5.6.1 Non-Aggregated-RUCI-Report-Request (NRR) command .....                   | 20 |
+| 5.6.2 Non-Aggregated-RUCI-Report-Answer (NRA) command.....                     | 20 |
+
+5.6.3 Aggregated-RUCI-Report-Request (ARR) command ..... 21  
+5.6.4 Aggregated-RUCI-Report-Answer (ARA) command..... 21  
+5.6.5 Modify-Uecontext-Request (MUR) command..... 21  
+5.6.6 Modify-Uecontext-Answer (MUA) command..... 22  
+**Annex A (informative): Change history..... 23**
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> 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.
+
+# 1 Scope
+
+The present document provides the stage 3 specification of the Np reference point. The functional requirements and the stage 2 specifications of the Np reference point are contained in 3GPP TS 23.203 [2]. The Np reference point lies between the RAN Congestion Awareness Function (RCAF) and the Policy and Charging Rules Function (PCRF) for the non-roaming case, between the RCAF and the H-PCRF for the home-routed scenario and between the RCAF and the V-PCRF for the visited access scenario.
+
+NOTE: If not specified explicitly, the PCRF also means H-PCRF for the home-routed scenario or V-PCRF in the visited access scenario in the specification.
+
+# 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.203: "Policy and charging control architecture".
+- [3] 3GPP TS 29.213: "Policy and Charging Control signalling flows and QoS parameter mapping".
+- [4] IETF RFC 4005: "Diameter Network Access Server Application".
+- [5] IETF RFC 4006: "Diameter Credit Control Application".
+- [6] 3GPP TS 29.229: "Cx and Dx interfaces based on Diameter protocol; Protocol details".
+- [7] IETF RFC 3588: "Diameter Base Protocol".
+- [8] 3GPP TS 23.401: "GPRS enhancements for E-UTRAN access".
+- [9] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
+- [10] 3GPP TS 29.215: "Policy and Charging Control (PCC) over S9 reference point; Stage 3".
+- [11] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)".
+- [12] 3GPP TS 29.274: "3GPP Evolved Packet System. Evolved GPRS Tunnelling Protocol for EPS (GTPv2)".
+- [13] ITU-T Recommendation E.212: "The international identification plan for mobile terminals and mobile users".
+- [14] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points".
+- [15] IETF RFC 7683: "Diameter Overload Indication Conveyance".
+- [16] IETF RFC 7944: "Diameter Routing Message Priority".
+- [17] IETF RFC 8583: "Diameter Load Information Conveyance".
+- [18] IETF RFC 6733: "Diameter Base Protocol".
+
+- [19] IETF RFC 5719: "Updated IANA Considerations for Diameter Command Code Allocations".
+- [20] IETF RFC 2234: "Augmented BNF for syntax specifications".
+
+# --- 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].
+
+**Home Routed Access:** Roaming scenario where the PCEF is located in the HPLMN. In a Home Routed roaming scenario, the UE obtains access to the packet data network from the HPLMN.
+
+**RAN user plane congestion:** RAN user plane congestion occurs when the demand for RAN resources exceeds the available RAN capacity to deliver the user data for a prolonged period of time.
+
+NOTE: Short-duration traffic bursts is a normal condition at any traffic load level, and is not considered to be RAN user plane congestion. Likewise, a high-level of utilization of RAN resources (based on operator configuration) is considered a normal mode of operation and might not be RAN user plane congestion.
+
+**Visited Access (also known as local breakout):** Roaming scenario where the PCEF is located in the VPLMN. In a Visited Access Roaming scenario, the UE obtains access to the packet data network from the VPLMN.
+
+## 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].
+
+|        |                                       |
+|--------|---------------------------------------|
+| AF     | Application Function                  |
+| ARR    | Aggregated RUCI Report Request        |
+| ARA    | Aggregated RUCI Report Answer         |
+| DRMP   | Diameter Routing Message Priority     |
+| H-PCRF | Home PCRF                             |
+| MUR    | Modify Uecontext Request              |
+| MUA    | Modify Uecontext Answer               |
+| NRR    | Non-Aggregated RUCI Report Request    |
+| NRA    | Non-Aggregated RUCI Report Answer     |
+| PCC    | Policy and Charging Control           |
+| PCRF   | Policy and Charging Rule Function     |
+| RCAF   | RAN Congestion Awareness Function     |
+| RUCI   | RAN User Plane Congestion Information |
+| V-PCRF | Visited PCRF                          |
+
+# --- 4 Np reference point
+
+## 4.1 Overview
+
+The Np reference point is located between the RCAF and the PCRF for the non-roaming scenario, between the RCAF and the H-PCRF for the home-routed scenario and between the RCAF and the V-PCRF for the visited access scenario. The Np reference point is used for:
+
+- Reporting the RUCI from the RCAF to the PCRF;
+- Provisioning the Reporting Restriction from the PCRF to the RCAF;
+
+- The User Equipment (UE) mobility between RCAF;
+- The removal of the UE context in the RCAF.
+
+The stage 2 level requirements for the Np reference point are defined in 3GPP TS 23.203 [2].
+
+Signalling flows related to Np interface are specified in 3GPP TS 29.213 [3].
+
+Refer to Annex G of 3GPP TS 29.213 [3] for Diameter overload control procedures over the Np interface.
+
+Refer to Annex J of 3GPP TS 29.213 [3] for Diameter message priority mechanism procedures over the Np interface.
+
+Refer to Annex K of 3GPP TS 29.213 [3] for Diameter load control procedures over the Np interface.
+
+## 4.2 Np reference model
+
+The relationships between the involved functional entities are depicted in figure 4.2.1. The overall PCC architecture is depicted in clause 3a of 3GPP TS 29.213 [3] .
+
+![Diagram of the Np reference model showing RCAF and PCRF connected via the Np interface.](1c94fd3cebf58af136144f14160d128e_img.jpg)
+
+The diagram shows two green rectangular boxes, labeled 'RCAF' on the left and 'PCRF' on the right, connected by a horizontal line. Above the line, the label 'Np' is centered. There is a small vertical tick mark on the line between the two boxes.
+
+Diagram of the Np reference model showing RCAF and PCRF connected via the Np interface.
+
+**Figure 4.2.1: Np reference model**
+
+NOTE: For the home-routed access scenario, the RCAF interacts with the H-PCRF. For the visited access scenario, the RCAF interacts with the V-PCRF.
+
+**Figure 4.2.2: Void**
+
+**Figure 4.2.3: Void**
+
+## 4.3 Functional elements
+
+### 4.3.1 RCAF
+
+The RCAF is a functional element which reports RAN User Plane Congestion Information (RUCI) via the Np interface to the PCRF to enable the PCRF to take the RAN user plane congestion status into account for policy decisions. RUCI includes the following information:
+
+- The user id (e.g. IMSI) identifying the UE impacted by congestion;
+- PDN ID for which congestion information is reported;
+- Congestion level information (either congestion level value or congestion level set id) of the UE impacted by congestion;
+- eNodeB identifier, ECGI or SAI identifying the eNodeB, E-UTRAN cell or Service Area respectively, serving the UE if a conditional restriction to restrict location reporting is not enabled.
+
+NOTE 1: In case of E-UTRAN, whether the eNodeB identifier or the ECGI are included in the RUCI is up to operator configuration in the RCAF.
+
+The RCAF sends the RUCI to the PCRFs serving the UEs' PDN connections as follows:
+
+- For a PDN connection in a non-roaming scenario the RCAF reports the RUCI to the PCRF;
+- For a PDN connection in a local breakout scenario, based on operator configuration, the RCAF reports the RUCI to the V-PCRF;
+
+- For a PDN connection in a home routed scenario, based on the roaming agreement with the HPLMN and operator configuration, the RCAF reports the RUCI to the H-PCRF
+
+NOTE 2: Reporting of congestion information to the HPLMN may be used e.g. in case of a group of PLMNs which belong to a single business entity.
+
+The RCAF determines whether a given PDN connection is served in a local breakout or a home routed roaming scenario based on the APN operator identifier received as part of the APN information from the MME or the SGSN as documented in 3GPP TS 23.401 [8] and 3GPP TS 23.060 [9], respectively.
+
+NOTE 3: Operator configuration can be used to limit RUCI reporting on the Np interface to certain APNs only.
+
+The RCAF maintains a context per user id and APN. The context is identified by the IMSI and the APN. It contains the following information:
+
+- The previously reported congestion level over the Np reference point;
+- The reporting restrictions received from the PCRF. The reporting restrictions are stored by the RCAF until the PCRF explicitly signals to remove the reporting restrictions.
+- The logical PCRF id received from the PCRF to identify the PCRF that is the Np destination for the RCAF when sending aggregate messages.
+
+### 4.3.2 PCRF
+
+The PCRF is a functional element that encompasses policy control decision and flow based charging control functionalities.
+
+The PCRF may receive RUCI from the RCAF as input for policy decisions of congestion mitigation. The PCRF may provide, update or remove the reporting restrictions of RUCI, or stop or enable RUCI reporting for a given user id and PDN ID. The PCRF may enable or disable the reporting of congestion location identifier as part of RUCI. The PCRF may also remove the context at the RCAF for a given user id and PDN ID.
+
+NOTE: Depending on the RUCI reporting interval configured in the RCAF, a UE can move outside the area indicated without the RCAF immediately notifying the PCRF. In case the PCRF receives information about the cell currently serving a UE via Np and Gx when the location change reporting is enabled, then the information received via Gx is expected to take precedence.
+
+### 4.3.3 H-PCRF
+
+Functionality defined in clause 4.3.2 shall apply if UE is roaming with home-routed access scenario.
+
+NOTE: Reporting of congestion information to the HPLMN can be used e.g. in case of a group of PLMNs which belong to a single business entity.
+
+### 4.3.4 V-PCRF
+
+Functionality defined in clause 4.3.2 shall apply if UE is roaming with visited access scenario.
+
+## 4.4 Procedures over Np reference point
+
+### 4.4.1 RUCI Report
+
+#### 4.4.1.1 General
+
+The RCAF shall perform the RUCI reporting to the PCRF when at least one of the following conditions applies:
+
+- the RCAF detects a UE in the congestion area for the first time;
+- a reporting restriction is enabled and the congestion level set id is changed;
+
+- a reporting restriction is not enabled and the congestion level value is changed;
+- a conditional restriction to restrict location reporting is not enabled and the UE is in a congested area and the location is changed; or
+- the RCAF detects that the UE is no longer experiencing congestion (i.e. the UE is no longer detected in any of the congested cells that the RCAF is monitoring).
+
+The RCAF shall report the RUCI to the PCRF unless the RUCI reporting is disabled for the PDN ID or for the user id and the PDN ID.
+
+Two types of RUCI reports may be used on Np for transfer of congestion information from RCAF to PCRF: Non-aggregated RUCI report and Aggregated RUCI report. If the RCAF does not know the destination PCRF for the user id and PDN ID, the Non-aggregated RUCI report shall be used; otherwise the RCAF may use either the Non-aggregate RUCI report or Aggregated RUCI report for the user id and PDN ID.
+
+#### 4.4.1.2 Non-aggregated RUCI report
+
+For a Non-aggregated RUCI report, the RCAF shall send an NRR command to the PCRF by including the user id within the Subscription-Id AVP, PDN ID within the Called-Station-Id AVP and a congestion level set id within the Congestion-Level-Set-Id AVP if the reporting restriction was provided earlier or a congestion level value within the Congestion-Level-Value AVP if the reporting restriction was not provided earlier at the command level. The RCAF may also provide congestion location identifier of the UE within the Congestion-Location-Id AVP in the NRR command. The RCAF shall also include the RCAF Identity within the RCAF-Id AVP in every NRR command for a specific user id and PDN ID.
+
+Once the PCRF receives the NRR command, the PCRF shall store the related info and respond with an NRA command including the PCRF id within the PCRF-Address AVP. The PCRF may use the RUCI received from the RCAF as input for policy decisions. When the RCAF receives the NRA command, the RCAF may store the PCRF id in the UE context for this specific user id together with PDN ID for further aggregated RUCI report.
+
+If the ReportRestriction feature is supported by both the RCAF and the PCRF, the PCRF may provide reporting restrictions in the NRA command according to clause 4.4.2.
+
+#### 4.4.1.3 Aggregated RUCI report
+
+For an Aggregated RUCI report, the RCAF shall aggregate the RUCIs of different user ids and PDN IDs that have the same destination PCRF. The RCAF shall send an ARR command to the destination PCRF by including the PCRF id within the Destination-Host AVP, one or more Aggregated-RUCI-Report AVP with a congestion level set id within the Congestion-Level-Set-Id AVP if the reporting restriction was provided earlier or a congestion level value within the Congestion-Level-Value AVP if the reporting restriction was not provided earlier, the PDN ID within the Called-Station-ID AVP and a list of aggregated congestion information within the Aggregated-Congestion-Info AVP.
+
+NOTE 1: Each instance of Aggregated-RUCI-Report AVP aggregates the user id list of the subscribers that share the same level of congestion or share the same congestion level set id.
+
+NOTE 2: When the RCAF assembles a Diameter ARR command, if the message length of ARR command has exceeded the maximum length of Diameter message which can be configurable, the RCAF can divide the original ARR command into multiple aggregated RUCI messages for the delivery over Np reference point.
+
+Once the PCRF receives the ARR command, the PCRF shall store the related info and respond with an ARA command. The PCRF may use the RUCI received from the RCAF as input for policy decisions.
+
+### 4.4.2 Reporting Restriction Provisioning
+
+If the ReportRestriction feature is supported by both the RCAF and the PCRF, the PCRF may provide the reporting restrictions for a specific user id and PDN ID in the initial NRA command. The PCRF may also provide, modify or disable restrictions for RUCI reporting or stop or enable RUCI reporting for the specific user id and PDN ID at any later time. The PCRF may also use this procedure to enable or disable the reporting of congestion location identifier as part of RUCI.
+
+In order to initially provide the reporting restrictions, the PCRF shall send a Modify-Uecontext-Request (MUR) command including the targeted Subscription-Id AVP indicating the user id, the Called-Station-Id AVP indicating the targeted PDN ID and one or more Congestion-Level-Definition AVP(s) including the defined congestion level set within the Congestion-Level-Set-Id AVP and corresponding congestion level(s) within the Congestion-Level-Range AVP or reply with an NRA command including one or more Congestion-Level-Definition AVP(s) including the defined congestion level set within the Congestion-Level-Set-Id AVP and corresponding congestion level(s) within the Congestion-Level-Range AVP . The PCRF may also include the Reporting-Restriction AVP and Conditional-Restriction AVP to indicate when conditional reporting restrictions apply.
+
+The PCRF may modify already provided reporting restrictions. To do so the PCRF shall provide the complete list of congestion level sets and corresponding congestion levels to be used in the same manner as when initially providing reporting restrictions. This complete list shall replace any previously provided list. The absence of Reporting-Restriction AVP and Conditional-Restriction AVP indicates that previous state of reporting restrictions remains valid.
+
+If reporting restrictions has been provided for a specific user id and PDN ID, the PCRF may remove the reporting restrictions by, in the MUR command, including the Reporting-Restriction AVP set to 0 (No reporting restriction), together with Subscription-Id AVP indicating the user id and the Called-Station-Id AVP indicating the targeted PDN ID or reply with an NRA command including the Reporting-Restriction AVP set to 0 (No reporting restriction).
+
+The PCRF may disable RUCI reporting by, in the MUR command, including the RUCI-Action AVP set to 0 (Disable RUCI Reporting), together with Subscription-Id AVP indicating the user id and the Called-Station-Id AVP indicating the targeted PDN ID or reply with an NRA command including the RUCI-Action AVP set to 0 (Disable RUCI Reporting).
+
+To enable RUCI Reporting if previously disabled, the PCRF in the MUR command shall include the RUCI-Action AVP set to 1 (Enable RUCI Reporting), together with Subscription-Id AVP indicating the user id and the Called-Station-Id AVP indicating the targeted PDN ID or reply with an NRA command including the RUCI-Action AVP set to 1 (Enable RUCI Reporting).
+
+If reporting restrictions also applies, the PCRF shall include one or more Congestion-Level-Definition AVP(s) including the defined congestion level set with the Congestion-Level-Set-Id AVP and corresponding congestion level(s) within the Congestion-Level-Range AVP, within the same command.
+
+To provision the reporting restriction which disables the reporting of congestion location identifier of the UE as part of RUCI, the PCRF shall include Reporting-Restriction AVP set to 1 (Conditional reporting restriction) and Conditional-Restriction AVP with the bit 0 be set. To enable a previously disabled reporting of the congestion location identifier of the UE as part of RUCI, the PCRF shall include Reporting-Restriction AVP set to 2 (Unconditional reporting restriction).
+
+The PCRF shall include the value of the RCAF-Id AVP received in the NRR command for the specific user id and PDN ID in the Destination-Host AVP of the MUR command.
+
+The RCAF acknowledges the received MUR command by sending a Modify-Uecontext-Answer (MUA) command in all cases above.
+
+### 4.4.3 UE mobility between RCAFs
+
+If RUCI reporting is used for a specific user id and PDN ID and the PCRF receives a new non-aggregated RUCI report for the same user id and PDN ID but with a different RCAF id included in the RCAF-Id AVP, the PCRF shall update the related information and respond with an NRA command according to clause 4.4.1.1.
+
+The PCRF shall also initiate a removal of the UE context to the old RCAF according to clause 4.4.4.
+
+### 4.4.4 Removal of UE context
+
+This procedure is initiated when the PCRF needs to remove a UE context from the RCAF, e.g. at UE mobility between RCAFs.
+
+If the PCRF due to an event determines that a UE context needs to be removed from the RCAF, the PCRF shall send an MUR command to the targeted RCAF to explicitly release the context related to the user id and PDN ID by including the Subscription-Id AVP indicating the user id, the Called-Station-Id AVP indicating the PDN ID, the Destination-Host AVP indicating the targeted RCAF id and the RUCI-Action AVP set to 2 (Release Context).
+
+The RCAF when receiving the MUR command from the PCRF shall release the context related to the user id and PDN ID. If this is the last PDN ID stored for this user id the RCAF shall release the complete context.
+
+The RCAF shall acknowledge the received MUR command by sending an MUA command.
+
+### 4.4.5 Race condition handling
+
+If the RCAF receives an MUR command to remove a context for a specific user id and PDN ID, the request shall be handled immediately, regardless of whether there are any ongoing RUCI report transactions for that user id and PDN ID.
+
+If the PCRF receives an NRR command for a specific user id and PDN ID, and if there is an ongoing MUR command to remove the context for that user id and PDN ID, the PCRF shall reject the incoming request with a Diameter experimental result code of DIAMETER\_PENDING\_TRANSACTION.
+
+If the PCRF receives an ARR command for specific user id and PDN ID combinations for which there is at least one ongoing MUR command to remove the context, the PCRF shall accept the request and only update the context(s) that are not in the process of being removed.
+
+# --- 5 Np protocol
+
+## 5.1 Protocol support
+
+The Np application is defined as a vendor specific Diameter application, where the vendor is 3GPP and the Application-ID for the Np Application in the present release is 16777342. The vendor identifier assigned by IANA to 3GPP (<http://www.iana.org/assignments/enterprise-numbers>) is 10415.
+
+NOTE: A route entry can have a different destination based on the application identification AVP of the message. Therefore, Diameter agents (relay, proxy, redirection, translation agents) must be configured appropriately to identify the 3GPP Np application within the Auth-Application-Id AVP in order to create suitable routeing tables.
+
+With regard to the Diameter protocol defined over the Np interface, the PCRF acts as a Diameter server, in the sense that it is the network element that handles the RUCI reporting for a particular realm. The RCAF acts as the Diameter client, in the sense that it is the network element reporting the RUCI.
+
+## 5.2 Initialization, maintenance and termination of connection and session
+
+The initialization and maintenance of the connection between the RCAF and PCRF are defined by the underlying protocol. Establishment and maintenance of connections between Diameter nodes are described in IETF RFC 6733 [18].
+
+After establishing the transport connection, the RCAF and the PCRF shall advertise the support of the Np specific Application by including the value of the application identifier in the Auth-Application-Id AVP and the value of the 3GPP (10415) in the Vendor-Id AVP of the Vendor-Specific-Application-Id AVP contained in the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. The Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands are specified in the Diameter Base Protocol (IETF RFC 6733 [18]).
+
+The Np Diameter session shall be terminated after each request and answer pair interaction.
+
+In order to indicate that the session state is not to be maintained, the Diameter client and server shall include the Auth-Session-State AVP with the value set to NO\_STATE\_MAINTAINED (1), in the request and in the answer messages (see IETF RFC 6733 [18]).
+
+## 5.3 Np specific AVPs
+
+### 5.3.1 General
+
+Table 5.3.1.1 describes the Diameter AVPs defined for the Np reference point, their AVP Code values, types, possible flag values, whether or not the AVP may be encrypted and which supported features the AVP is applicable to. The Vendor-Id header of all AVPs defined in the present document shall be set to 3GPP (10415).
+
+**Table 5.3.1.1: Np specific Diameter AVPs**
+
+| Attribute Name              | AVP Code | Clause defined | Value Type (NOTE 2) | AVP Flag rules (NOTE 1) |     |            |          | May Encr. | Applicability (NOTE 3) |
+|-----------------------------|----------|----------------|---------------------|-------------------------|-----|------------|----------|-----------|------------------------|
+|                             |          |                |                     | Mus t                   | May | Should not | Must not |           |                        |
+| Aggregated-Congestion-Info  | 4000     | 5.3.2          | Grouped             | V, M                    | P   |            |          | Y         |                        |
+| Aggregated-RUCI-Report      | 4001     | 5.3.3          | Grouped             | V, M                    | P   |            |          | Y         |                        |
+| Congestion-Level-Definition | 4002     | 5.3.4          | Grouped             | V                       | P   |            | M        | Y         | ReportRestriction      |
+| Congestion-Level-Range      | 4003     | 5.3.5          | Unsigned32          | V                       | P   |            | M        | Y         | ReportRestriction      |
+| Congestion-Level-Set-Id     | 4004     | 5.3.6          | Unsigned32          | V                       | P   |            | M        | Y         | ReportRestriction      |
+| Congestion-Level-Value      | 4005     | 5.3.7          | Unsigned32          | V, M                    | P   |            |          | Y         |                        |
+| Congestion-Location-Id      | 4006     | 5.3.8          | Grouped             | V                       | P   |            | M        | Y         | ReportRestriction      |
+| Conditional-Restriction     | 4007     | 5.3.9          | Unsigned32          | V                       | P   |            | M        | Y         | ReportRestriction      |
+| eNodeB-Id                   | 4008     | 5.3.10         | OctetString         | V, M                    | P   |            |          | Y         |                        |
+| IMSI-List                   | 4009     | 5.3.11         | OctetString         | V, M                    | P   |            |          | Y         |                        |
+| RCAF-Id                     | 4010     | 5.3.12         | DiameterIdentity    | V, M                    | P   |            |          | Y         |                        |
+| Reporting-Restriction       | 4011     | 5.3.13         | Unsigned32          | V                       | P   |            | M        | Y         | ReportRestriction      |
+| RUCI-Action                 | 4012     | 5.3.14         | Unsigned32          | V                       | P   |            | M        | Y         | ReportRestriction      |
+| Extended-eNodeB-Id          | 4013     | 5.3.15         | OctetString         | V, M                    | P   |            | M        | Y         |                        |
+
+NOTE 1: The AVP header bit denoted as 'M', indicates whether support of the AVP is required. The AVP header bit denoted as 'V', indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see IETF RFC 6733 [18].
+
+NOTE 2: The value types are defined in IETF RFC 6733 [18].
+
+NOTE 3: AVPs marked with a supported feature (e.g. "ReportRestriction") are applicable as described in clause 5.4.2.
+
+### 5.3.2 Aggregated-Congestion-Info AVP
+
+The Aggregated-Congestion-Info AVP (AVP code 4000) is of type Grouped. It contains a list of user ids identified by IMSI and optionally the congestion location id in which the list of user ids are located.
+
+```
+Aggregated-Congestion-Info ::= < AVP Header: 4000 >
+    [ Congestion-Location-Id ]
+    [ IMSI-List ]
+    *[ AVP ]
+```
+
+### 5.3.3 Aggregated-RUCI-Report AVP
+
+The Aggregated-RUCI-Report AVP (AVP code 4001) is of type Grouped, and it is used to contain the congestion level value or congestion level set id for a set of users which have the same PCRF for the same PDN ID.
+
+The congestion-Level-Value AVP contains the congestion level value if the PCRF did not provide the reporting restriction earlier for the user id and PDN ID.
+
+The Congestion-Level-Set-Id AVP contains the congestion level set identifier between the PCRF and the RCAF if the PCRF provided the reporting restriction earlier for the user id and PDN ID.
+
+The Called-Station-Id AVP contains the PDN ID.
+
+The Aggregated-Congestion-Info AVP shall indicate the list of users included in the IMSI-List AVP and the congested location included in the Congestion-Location-Id AVP (if applicable), where a congestion level included in the Congestion-Level-Value AVP or congestion level set included in the Congestion-Level-Set-Id AVP shall apply.
+
+```
+Aggregated-RUCI-Report ::= < AVP Header: 4001 >
+  1*{ Aggregated-Congestion-Info }
+    [ Called-Station-Id ]
+    [ Congestion-Level-Value ]
+    [ Congestion-Level-Set-Id ]
+    *[ AVP ]
+```
+
+### 5.3.4 Congestion-Level-Definition AVP
+
+The Congestion-Level-Definition AVP (AVP code 4002) is of type Grouped, and it is used to define a congestion level set and corresponding congestion level(s) to be used by the RCAF for a specific user id and PDN ID at congestion reporting. When this AVP is present in the MUR command reporting restrictions apply, when this AVP is absent there are no reporting restriction for the specific user id and PDN ID.
+
+```
+Congestion-Level-Definition ::= < AVP Header: 4002 >
+  { Congestion-Level-Set-Id }
+  { Congestion-Level-Range }
+  *[ AVP ]
+```
+
+### 5.3.5 Congestion-Level-Range AVP
+
+The Congestion-Level-Range AVP (AVP code 4003) is of type Unsigned32, and it is used to indicate the list of congestion level(s) bound to a certain congestion level set, between the PCRF and the RCAF. The Congestion-Level-Range AVP shall contain a bit mask. The bit 0 shall be the least significant bit. For example, to get the value of bit 0, a bit mask of 0x0001 should be used. The meaning of the bits shall be as defined below:
+
+**Table 5.3.5.1: Congestion Level Range**
+
+| Bit | Name                 | Description                                                                                                                                                                           |
+|-----|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 0   | No congestion        | This bit, when set, indicates that the RCAF shall report the corresponding congestion level set id to the PCRF when there is no congestion for a certain user id and PDN ID.          |
+| 1   | Congestion level 1   | This bit, when set, indicates that the RCAF shall report the corresponding congestion level set id to the PCRF when congestion level 1 is reached for a certain user id and PDN ID.   |
+| 1+n | Congestion level 1+n | This bit, when set, indicates that the RCAF shall report the corresponding congestion level set id to the PCRF when congestion level 1+n is reached for a certain user id and PDN ID. |
+
+### 5.3.6 Congestion-Level-Set-Id AVP
+
+The Congestion-Level-Set-Id AVP (AVP code 4004) is of type Unsigned32, and it is used to indicate the congestion level set identifier between the PCRF and the RCAF.
+
+### 5.3.7 Congestion-Level-Value AVP
+
+The Congestion-Level-Value AVP (AVP code 4005) is of type Unsigned32, and it is used to indicate the congestion level associated with the user id and PDN ID.
+
+The following values are defined:
+
+0 (No congestion):
+
+This value indicates that there is no congestion.
+
+N (Congestion level n):
+
+These values indicate that there is congestion. The value n is an integer between 1 and 31 and indicates a congestion level. The value 1 is the lowest congestion level and value 31 is the highest congestion level.
+
+### 5.3.8 Congestion-Location-Id AVP
+
+The Congestion-Location -Id AVP (AVP code 4006) is of type Grouped, and it indicates the identifier of a congested location in which the UE is currently located. The congested location is one of the following: the eNodeB, E-UTRAN cell or Service Area serving the UE. If ECGI is included in the 3GPP-User-Location-Info AVP within Congestion-Location-Id AVP, then the eNodeB identifier within eNodeB-Id AVP or Extended-eNodeB-Id AVP shall not be included in this AVP. This AVP is provided in the RUCI per user id and APN. If the eNodeB identifier has a length of 18 or 21 bits it shall be provided in the Extended-eNodeB-Id AVP and otherwise in the eNodeB-Id AVP.
+
+AVP Format:
+
+```
+Congestion-Location-Id ::= < AVP Header: 4006 >
+                        [ 3GPP-User-Location-Info ]
+                        [ eNodeB-Id ]
+                        [ Extended-eNodeB-Id ]
+                        *[ AVP ]
+```
+
+### 5.3.9 Conditional-Restriction AVP
+
+The Conditional-Restriction AVP (AVP code 4007) is of type Unsigned32 and it shall contain a bit mask, and indicates what conditional reporting restrictions apply. Conditional reporting restrictions shall apply when this AVP is provided. The bit 0 shall be the least significant bit. For example, to get the value of bit 0, a bit mask of 0x0001 should be used. The meaning of the bits shall be as defined below:
+
+**Table 5.3.9.1: Conditional-Restriction over Np**
+
+| Bit | Name                                  | Description                                                                                                        |
+|-----|---------------------------------------|--------------------------------------------------------------------------------------------------------------------|
+| 0   | UE location info not included in RUCI | This bit, when set, indicates that the location information of the UE shall not be included in RUCI for reporting. |
+
+### 5.3.10 eNodeB-Id AVP
+
+The eNodeB-Id AVP (AVP code 4008) is of type OctetString, and indicates the eNodeB in which the UE is currently located. The AVP shall be coded as in clause 8.51 of 3GPP TS 29.274 [12].
+
+### 5.3.11 IMSI-List AVP
+
+The IMSI-List AVP (AVP code 4009) is of type OctetString, and it contains a list of user ids identified by IMSI. Each IMSI shall be encoded as TBCD digits as defined in ITU-T Recommendation E.212 [13], i.e. digits from 0 through 9 are encoded "0000" to "1001". Each IMSI shall be encoded as 8 octets. If the length of the IMSI is 14, then the last octet shall be encoded as "1111 1111". If the length of the IMSI is 15, bits 5 to 8 of the last octet shall be encoded with the filler "1111". The maximum number of digits is 15. An example of the encoding of the IMSI List as the data part of the OctetString AVP is given below in Figure 5.3.11-1. Octet 1 given below is the first octet of the data part of the IMSI-List AVP.
+
+| Octets    | Bits                      |   |   |   |                           |   |   |   |
+|-----------|---------------------------|---|---|---|---------------------------|---|---|---|
+|           | 8                         | 7 | 6 | 5 | 4                         | 3 | 2 | 1 |
+| 1         | Number digit 2 of IMSI-1  |   |   |   | Number digit 1 of IMSI-1  |   |   |   |
+| 2         | Number digit 4 of IMSI-1  |   |   |   | Number digit 3 of IMSI-1  |   |   |   |
+| ...       | ...                       |   |   |   | ...                       |   |   |   |
+| 8         | 1111                      |   |   |   | Number digit 15 of IMSI-1 |   |   |   |
+| 9         | Number digit 2 of IMSI-2  |   |   |   | Number digit 1 of IMSI-2  |   |   |   |
+| 10        | Number digit 4 of IMSI-2  |   |   |   | Number digit 3 of IMSI-2  |   |   |   |
+| ...       | ...                       |   |   |   | ...                       |   |   |   |
+| 15        | Number digit 14 of IMSI-2 |   |   |   | Number digit 13 of IMSI-2 |   |   |   |
+| 16        | 1111                      |   |   |   | 1111                      |   |   |   |
+| 17        | Number digit 2 of IMSI-3  |   |   |   | Number digit 1 of IMSI-3  |   |   |   |
+| 18        | Number digit 4 of IMSI-3  |   |   |   | Number digit 3 of IMSI-3  |   |   |   |
+| ...       | ...                       |   |   |   | ...                       |   |   |   |
+| 23        | Number digit 14 of IMSI-3 |   |   |   | Number digit 13 of IMSI-3 |   |   |   |
+| 24        | 1111                      |   |   |   | 1111                      |   |   |   |
+| ...       | ...                       |   |   |   | ...                       |   |   |   |
+| (n-1)*8+1 | Number digit 2 of IMSI-n  |   |   |   | Number digit 1 of IMSI-n  |   |   |   |
+| (n-1)*8+2 | Number digit 4 of IMSI-n  |   |   |   | Number digit 3 of IMSI-n  |   |   |   |
+| ...       | ...                       |   |   |   | ...                       |   |   |   |
+| (n-1)*8+8 | 1111                      |   |   |   | Number digit 15 of IMSI-n |   |   |   |
+
+NOTE: In the above figure showing an example of encoding, it is assumed that n IMSIs are included in the IMSI-List AVP. The digit length of IMSI-1, IMSI-2, IMSI-3 and IMSI-n are 15, 14, 14, 15 respectively.
+
+**Figure 5.3.11-1: Encoding of IMSI-List AVP**
+
+### 5.3.12 RCAF-Id AVP
+
+The RCAF-Id AVP (AVP code 4010) is of type DiameterIdentity, and it is used to contain the RCAF identity.
+
+### 5.3.13 Reporting-Restriction AVP
+
+The Reporting-Restriction AVP (AVP code 4011) is of type Unsigned32, and it is used to indicate the applicable reporting restrictions between the PCRF and RCAF. If this AVP is not provided during the initial reporting restriction provisioning, it shall be understood as unconditional reporting restrictions apply.
+
+The following values are defined:
+
+0 (No reporting restriction):
+
+This value shall be used by the PCRF to indicate to the RCAF that there are no restrictions on congestion reporting for a specific user id and PDN ID. This value shall not be used if congestion level definitions are included in the same command.
+
+1 (Conditional reporting restriction):
+
+This value shall be used by the PCRF to indicate to the RCAF that there are conditional restrictions on congestion reporting for a specific user id and PDN ID.
+
+2 (Unconditional reporting restriction):
+
+This value shall be used by the PCRF to indicate to the RCAF that there are unconditional restrictions on congestion reporting for a specific user id and PDN ID.
+
+### 5.3.14 RUCI-Action AVP
+
+The RUCI-Action AVP (AVP code 4012) is of type Unsigned32, and it is used to disable or enable RUCI reporting between the PCRF and RCAF or to release the context for a specific user id and PDN ID.
+
+The following values are defined:
+
+0 (Disable RUCI reporting):
+
+This value shall be used by the PCRF to indicate to the RCAF that RUCI reporting shall not be performed for a specific user id and PDN ID.
+
+1 (Enable RUCI reporting):
+
+This value shall be used by the PCRF to indicate to the RCAF that RUCI reporting shall be performed for a specific user id and PDN ID.
+
+2 (Release Context):
+
+This value shall be used by the PCRF to indicate to the RCAF that the context shall be released for a specific user id and PDN ID.
+
+### 5.3.15 Extended-eNodeB-Id AVP
+
+The Extended-eNodeB-Id AVP (AVP code 4013) is of type OctetString, and indicates the eNodeB in which the UE is currently located. The AVP shall be coded as in clause 8.51 of 3GPP TS 29.274 [12] for Type Extended Macro eNodeB.
+
+## 5.4 Np re-used AVPs
+
+### 5.4.1 General
+
+Table 5.4.1.1 lists the Diameter AVPs re-used by the Np reference point from other existing Diameter Applications, reference to their respective specifications, short description of their usage within the Np reference point and which supported features the AVP is applicable to. AVPs from existing Diameter Applications, except for the AVPs from Diameter base protocol, do not need to be supported. The AVPs from Diameter base protocol are not included in table 5.4.1.1, but they are re-used for the Np reference point. Unless otherwise stated, re-used AVPs shall maintain their 'M', 'P' and 'V' flag settings. Where RADIUS VSAs are re-used, unless otherwise stated, they shall be translated to Diameter AVPs as described in RFC 4005 [4] with the exception that the 'M' flag shall be set and the 'P' flag may be set.
+
+Table 5.4.1.1: Np re-used Diameter AVPs
+
+| Attribute Name                                                                          | Reference                        | Description                                                                                                                                                                         | Applicability (NOTE) |
+|-----------------------------------------------------------------------------------------|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|
+| Called-Station-Id                                                                       | IETF RFC 4005 [4]                | The address the user is connected to (i.e. the PDN identifier).                                                                                                                     |                      |
+| DRMP                                                                                    | IETF RFC 7944 [16]               | Allows Diameter endpoints to indicate the relative priority of Diameter transactions.                                                                                               |                      |
+| Load                                                                                    | IETF RFC 8583 [17]               | The AVP used to convey load information between Diameter nodes.<br>This AVP and all AVPs within this grouped AVP shall have the 'M' bit cleared.                                    |                      |
+| OC-OLR                                                                                  | IETF RFC 7683 [15]               | Contains the necessary information to convey an overload report.                                                                                                                    |                      |
+| OC-Supported-Features                                                                   | IETF RFC 7683 [15]               | Defines the support for the Diameter overload indication conveyance by the sending node.                                                                                            |                      |
+| PCRF-Address                                                                            | TS 29.215 [10]                   | The identity, which indicates the destination PCRF.                                                                                                                                 |                      |
+| Subscription-Id                                                                         | IETF RFC 4006 [5]                | The identification of the subscription (i.e. IMSI)                                                                                                                                  |                      |
+| Supported-Features                                                                      | TS 29.229 [6]                    | If present, this AVP informs the destination host about the features that the origin host requires to successfully complete this command exchange                                   |                      |
+| 3GPP-User-Location-Info                                                                 | TS 29.061 [11], clause 16.4.7.2. | Indicates details of where the UE is currently located. Only SAI (Geographic Location Type set to 1) or ECGI (Geographic Location Type set to 129) is included in this information. |                      |
+| NOTE: AVPs marked with a supported feature are applicable as described in clause 5.4.2. |                                  |                                                                                                                                                                                     |                      |
+
+### 5.4.2 Use of the Supported-Features AVP on the Np reference point
+
+When new functionality is introduced on the Np reference point, it should be defined as optional. If backwards incompatible changes cannot be avoided, the new functionality shall be introduced as a new feature and support advertised with the Supported-Features AVP. Unless otherwise stated, the use of the Supported-Features AVP on the Np reference point shall be compliant to the usage of the Supported-Features AVP on the Cx reference point and consistent with the procedures for the dynamic discovery of supported features as defined in clause 7.2 of 3GPP TS 29.229 [6].
+
+When extending the application by adding new AVPs for a feature, the new AVPs shall have the M bit cleared and the AVP shall not be defined mandatory in the command ABNF.
+
+As defined in 3GPP TS 29.229 [6], the Supported-Features AVP is of type grouped and contains the Vendor-Id, Feature-List-ID and Feature-List AVPs. On the all reference points as specified in this specification, the Supported-Features AVP is used to identify features that have been defined by 3GPP and hence, for features defined in this document, the Vendor-Id AVP shall contain the vendor ID of 3GPP (10415). If there are multiple feature lists defined for the reference point, the Feature-List-ID AVP shall differentiate those lists from one another.
+
+The Supported-Features AVP shall be included in every NRR and NRA command if supported by the RCAF and PCRF respectively.
+
+The table below defines the features applicable to the Np interface for the feature list with a Feature-List-ID of 1.
+
+Table 5.4.2.1: Features of Feature-List-ID 1 used in Np
+
+| Feature bit                                                                                                                         | Feature           | M/O | Description                                                 |
+|-------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----|-------------------------------------------------------------|
+| 0                                                                                                                                   | ReportRestriction | O   | This feature indicates the support of reporting restriction |
+| <b>Feature bit:</b> The order number of the bit within the Feature-List AVP where the least significant bit is assigned number "0". |                   |     |                                                             |
+| <b>Feature:</b> A short name that can be used to refer to the bit and to the feature, e.g. "EPS".                                   |                   |     |                                                             |
+| <b>M/O:</b> Defines if the implementation of the feature is mandatory ("M") or optional ("O") in this 3GPP Release.                 |                   |     |                                                             |
+| <b>Description:</b> A clear textual description of the feature.                                                                     |                   |     |                                                             |
+
+## 5.5 Np specific Experimental-Result-Code AVP values
+
+### 5.5.1 General
+
+This clause defines result code values that shall be supported by Diameter implementations that conform to this specification.
+
+### 5.5.2 Success
+
+Result Codes that fall into the Success category are used to inform a peer that a request has been successfully completed. The Result-Code AVP values defined in Diameter BASE IETF RFC 6733 [18] are applied.
+
+### 5.5.3 Permanent Failures
+
+Errors that fall into the Permanent Failures category shall be used to inform the peer that the request has failed. The Result-Code AVP values defined in Diameter Base Protocol IETF RFC 6733 [18] are applied. As an addition the following Result-Code AVP value defined in IETF RFC 4006 [5] is applicable:
+
+DIAMETER\_USER\_UNKNOWN (5030):
+
+This error shall be used by the PCRF to indicate to the RCAF that the end user specified in the request is unknown to the PCRF, or it shall be used by the RCAF to indicate to the PCRF that the end user specified in the request is unknown to the RCAF. This result code does not apply for aggregated RUCI report.
+
+### 5.5.4 Transient Failures
+
+Errors that fall within the Transient Failures category are used to inform a peer that the request could not be satisfied at the time it was received, but may be able to satisfy the request in the future.
+
+The Result-Code AVP values defined in Diameter Base IETF RFC 6733 [18] are applicable. As an addition the following Experimental-Result-Code value defined in 3GPP TS 29.212 [14] is applicable:
+
+DIAMETER\_PENDING\_TRANSACTION (4144):
+
+This error shall be used when a node receives an incoming request for a specific user id and PDN ID while it has an ongoing transaction for the same user id and PDN ID and cannot handle the request as described in clause 4.4.5.
+
+## 5.6 Np messages
+
+### 5.6.0 Command-Code Values
+
+This clause defines the Command-Code values for the Np interface application as allocated by IANA from the vendor-specific namespace defined in IETF RFC 5719 [x]. Every command is defined by means of the ABNF syntax in IETF RFC 2234 [y], and according to the rules in IETF RFC 6733 [18].
+
+NOTE: As the commands in the present specification have originally been defined based on the former specification of the Diameter Base Protocol (IETF RFC 3588 [7]), the Vendor-Specific-Application-Id AVP is still assumed as a required AVP (an AVP indicated as {AVP}) in the command code format to avoid backward compatibility issues, even if the use of this AVP has been deprecated in the new specification of the Diameter Base Protocol (IETF RFC 6733 [18]).
+
+The Np application identifier shall be included in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP contained in the commands defined in this specification.
+
+The following Command Codes are defined in this specification:
+
+Table 5.6.0.1: Command-Code values for Np
+
+| Command-Name                       | Abbreviation | Code    | Section |
+|------------------------------------|--------------|---------|---------|
+| Non-Aggregated-RUCI-Report-Request | NRR          | 8388720 | 5.6.1   |
+| Non-Aggregated-RUCI-Report-Answer  | NRA          | 8388720 | 5.6.2   |
+| Aggregated-RUCI-Report-Request     | ARR          | 8388721 | 5.6.3   |
+| Aggregated-RUCI-Report-Answer      | ARA          | 8388721 | 5.6.4   |
+| Modify-Uecontext-Request           | MUR          | 8388722 | 5.6.5   |
+| Modify-Uecontext-Answer            | MUA          | 8388722 | 5.6.6   |
+
+#### 5.6.1 Non-Aggregated-RUCI-Report-Request (NRR) command
+
+The NRR command, indicated by the Command-Code field set to 8388720 and the 'R' bit set in the Command Flags field, is sent by the RCAF to the PCRF as part of the Non-aggregated RUCI report procedure.
+
+Message Format:
+
+```
+<NR-Request> ::= <Diameter Header: 8388720, REQ, PXY >
+                < Session-Id >
+                [ DRMP ]
+                { Vendor-Specific-Application-Id }
+                { Auth-Session-State }
+                { Origin-Host }
+                { Origin-Realm }
+                { Destination-Realm }
+                [ Destination-Host ]
+                [ Origin-State-Id ]
+                [ Subscription-Id ]
+                [ Called-Station-Id ]
+                [ Congestion-Level-Value ]
+                [ Congestion-Level-Set-Id ]
+                [ Congestion-Location-Id ]
+                [ OC-Supported-Features ]
+                [ RCAF-Id ]
+                *[ Proxy-Info ]
+                *[ Route-Record ]
+                *[ Supported-Features ]
+                *[ AVP ]
+```
+
+#### 5.6.2 Non-Aggregated-RUCI-Report-Answer (NRA) command
+
+The NRA command, indicated by the Command-Code field set to 8388720 and the 'R' bit cleared in the Command Flags field, is sent by the PCRF to the RCAF as part of the Non-aggregated RUCI report procedure.
+
+Message Format:
+
+```
+<NR-Answer> ::= < Diameter Header: 8388720, PXY >
+                < Session-Id >
+                [ DRMP ]
+                { Vendor-Specific-Application-Id }
+                { Auth-Session-State }
+                { Origin-Host }
+                { Origin-Realm }
+                [ Result-Code ]
+                [ Experimental-Result ]
+                [ Error-Message ]
+                [ Error-Reporting-Host ]
+                [ Failed-AVP ]
+                [ OC-Supported-Features ]
+                [ OC-OLR ]
+                [ Reporting-Restriction ]
+                [ Conditional-Restriction ]
+                [ RUCI-Action ]
+                *[ Congestion-Level-Definition ]
+                [ PCRF-Address ]
+                [ Origin-State-Id ]
+                *[ Redirect-Host ]
+                [ Redirect-Host-Usage ]
+                [ Redirect-Max-Cache-Time ]
+                *[ Proxy-Info ]
+                *[ Supported-Features ]
+```
+
+```
+
+*[ Load ]
+*[ AVP ]
+
+```
+
+### 5.6.3 Aggregated-RUCI-Report-Request (ARR) command
+
+The ARR command, indicated by the Command-Code field set to 8388721 and the 'R' bit set in the Command Flags field, is sent by the RCAF to the PCRF as part of the Aggregated RUCI report procedure.
+
+Message Format:
+
+```
+
+<AR-Request> ::= <Diameter Header: 8388721, REQ, PXY >
+                < Session-Id >
+                [ DRMP ]
+                { Vendor-Specific-Application-Id }
+                { Auth-Session-State }
+                { Origin-Host }
+                { Origin-Realm }
+                { Destination-Realm }
+                [ Destination-Host ]
+                [ Origin-State-Id ]
+                *[ Aggregated-RUCI-Report ]
+                [ OC-Supported-Features ]
+                *[ Proxy-Info ]
+                *[ Route-Record ]
+                *[ Supported-Features ]
+                *[ AVP ]
+
+```
+
+### 5.6.4 Aggregated-RUCI-Report-Answer (ARA) command
+
+The ARA command, indicated by the Command-Code field set to 8388721 and the 'R' bit cleared in the Command Flags field, is sent by the PCRF to the RCAF as part of the Aggregated RUCI report procedure.
+
+Message Format:
+
+```
+
+<AR-Answer> ::= < Diameter Header: 8388721, PXY >
+                < Session-Id >
+                [ DRMP ]
+                { Vendor-Specific-Application-Id }
+                { Auth-Session-State }
+                { Origin-Host }
+                { Origin-Realm }
+                [ Result-Code ]
+                [ Experimental-Result ]
+                [ Error-Message ]
+                [ Error-Reporting-Host ]
+                [ Failed-AVP ]
+                [ Origin-State-Id ]
+                [ OC-Supported-Features ]
+                [ OC-OLR ]
+                *[ Redirect-Host ]
+                [ Redirect-Host-Usage ]
+                [ Redirect-Max-Cache-Time ]
+                *[ Proxy-Info ]
+                *[ Supported-Features ]
+                *[ Load ]
+                *[ AVP ]
+
+```
+
+### 5.6.5 Modify-Uecontext-Request (MUR) command
+
+The MUR command, indicated by the Command-Code field set to 8388722 and the 'R' bit set in the Command Flags field, is sent by the PCRF to the RCAF in order to request congestion reporting restrictions or remove the context for a specific user id and PDN ID.
+
+Message Format:
+
+```
+
+< Modify-Uecontext-Request > ::= < Diameter Header: 8388722, REQ, PXY >
+                                < Session-Id >
+                                [ DRMP ]
+                                { Vendor-Specific-Application-Id }
+                                { Auth-Session-State }
+                                { Origin-Host }
+
+```
+
+```
+{ Origin-Realm }
+{ Destination-Realm }
+{ Destination-Host }
+[ Origin-State-Id ]
+[ Subscription-Id ]
+[ Called-Station-Id ]
+[ OC-Supported-Features ]
+[ Reporting-Restriction ]
+[ Conditional-Restriction ]
+[ RUCI-Action ]
+*[ Congestion-Level-Definition ]
+*[ Proxy-Info ]
+*[ Route-Record ]
+*[ AVP ]
+```
+
+### 5.6.6 Modify-Uecontext-Answer (MUA) command
+
+The MUA command, indicated by the Command-Code field set to 8388722 and the 'R' bit set in the Command Flags field, is sent by the RCAF to the PCRF as a response to the request for congestion reporting restrictions to or remove the context a specific user id and PDN ID.
+
+Message Format:
+
+```
+< Modify-Uecontext-Answer > ::= < Diameter Header: 8388722, PXY >
+< Session-Id >
+[ DRMP ]
+{ Vendor-Specific-Application-Id }
+{ Auth-Session-State }
+{ Origin-Host }
+{ Origin-Realm }
+[ Result-Code ]
+[ Experimental-Result ]
+[ Failed-AVP ]
+[ Origin-State-Id ]
+[ OC-Supported-Features ]
+[ OC-OLR ]
+*[ Redirect-Host ]
+[ Redirect-Host-Usage ]
+[ Redirect-Max-Cache-Time ]
+*[ Proxy-Info ]
+*[ AVP ]
+```
+
+# Annex A (informative): Change history
+
+| <b>Change history</b> |              |                 |           |            |                                                                                |                                                                              |            |
+|-----------------------|--------------|-----------------|-----------|------------|--------------------------------------------------------------------------------|------------------------------------------------------------------------------|------------|
+| <b>Date</b>           | <b>TSG #</b> | <b>TSG Doc.</b> | <b>CR</b> | <b>Rev</b> | <b>Subject/Comment</b>                                                         | <b>Old</b>                                                                   | <b>New</b> |
+| 2015-06               | CT#68        | CP-150367       |           |            | Cleaned-up by MCC, based on the version sent by e-mail on June 5th and agreed. | 2.1.0                                                                        | 2.2.0      |
+| 2015-06               | -            | -               | -         | -          | MCC Editorial update after approval by TSG CT#68                               | 2.2.0                                                                        | 13.0.0     |
+| 2015-09               | CP-69        | CP-150477       | 0003      | 2          | Alignment of RUCI reporting restrictions' basis for UPCON                      | 13.0.0                                                                       | 13.1.0     |
+| 2015-09               | CP-69        | CP-150477       | 0005      | 2          | Correction to the PCRF functionality                                           | 13.0.0                                                                       | 13.1.0     |
+| 2015-09               | CP-69        | CP-150477       | 0006      | 1          | Correction to the RCAF functionality                                           | 13.0.0                                                                       | 13.1.0     |
+| 2015-09               | CP-69        | CP-150477       | 0008      | 1          | Corrections to the wrong implementation of C3-150441                           | 13.0.0                                                                       | 13.1.0     |
+| 2015-09               | CP-69        | CP-150477       | 0009      | 1          | Fixing Ambiguous Flag Rules for AVPs reused from TS 29.061                     | 13.0.0                                                                       | 13.1.0     |
+| 2015-12               | CP-70        | CP-150672       | 0010      | 1          | Some corrections to 29.217                                                     | 13.1.0                                                                       | 13.2.0     |
+| 2015-12               | CP-70        | CP-150797       | 0011      | 1          | Update the PCC architecture figures in 29.217                                  | 13.1.0                                                                       | 13.2.0     |
+| 2015-12               | CP-70        | CP-150630       | 0012      | 1          | Update draft-ietf-dime-ovli reference to RFC 7683                              | 13.1.0                                                                       | 13.2.0     |
+| 2015-12               | CP-70        | CP-150672       | 0013      | 1          | Vendor Specific Application ID over Np interface                               | 13.1.0                                                                       | 13.2.0     |
+| 2015-12               | CP-70        | CP-150672       | 0016      | 2          | Race condition handling for aggregated RUCI report                             | 13.1.0                                                                       | 13.2.0     |
+| 2015-12               | CP-70        | CP-150730       | 0018      | 1          | Diameter Message Priority over Np                                              | 13.1.0                                                                       | 13.2.0     |
+| <b>Change history</b> |              |                 |           |            |                                                                                |                                                                              |            |
+| <b>Date</b>           | <b>TSG #</b> | <b>TSG Doc.</b> | <b>CR</b> | <b>Rev</b> | <b>Cat</b>                                                                     | <b>Subject/Comment</b>                                                       | <b>New</b> |
+| 2016-03               | CT#71        | CP-160094       | 0022      | 1          | F                                                                              | Congestion Level for the specific user id                                    | 13.3.0     |
+| 2016-03               | CT#71        | CP-160094       | 0023      | 1          | F                                                                              | Add command codes and AVP numbers for Np protocol                            | 13.3.0     |
+| 2016-03               | CT#71        | CP-160093       | 0024      | -          | F                                                                              | Reference of the Diameter message priority mechanism procedure               | 13.3.0     |
+| 2016-03               | CT#71        | CP-160094       | 0025      | 1          | F                                                                              | Add missing abbreviations                                                    | 13.3.0     |
+| 2016-06               | CT#72        | CP-160276       | 0026      | 2          | F                                                                              | Correct Modify-Uecontext-Answer command definition and some editorial errors | 13.4.0     |
+| 2016-09               | CT#73        | CP-160442       | 0027      | -          | F                                                                              | Correction of IETF drmp draft version                                        | 13.5.0     |
+| 2016-09               | CT#73        | CP-160453       | 0028      | 1          | F                                                                              | Correction to the Np reused Diameter AVPs table                              | 13.5.0     |
+| 2016-12               | CT#74        | CP-160614       | 0029      | -          | F                                                                              | Correction to change IETF drmp draft version to official RFC 7944            | 13.6.0     |
+| 2016-12               | CT#74        | CP-160615       | 0030      | 2          | B                                                                              | Diameter Load Control Mechanism                                              | 14.0.0     |
+| 2016-12               | CT#74        | CP-160616       | 0031      | 1          | F                                                                              | Diameter base protocol specification update                                  | 14.0.0     |
+| 2017-03               | CT#75        | CP-170086       | 0033      | 2          | F                                                                              | Support of long and short Macro eNodeB IDs                                   | 14.1.0     |
+| 2017-03               | CT#75        | CP-170076       | 0034      | -          | F                                                                              | Update instance number for the Failed-AVP in answer commands                 | 14.1.0     |
+| 2017-06               | CT#76        | CP-171119       | 0035      | 1          | F                                                                              | Reference update for draft-ietf-dime-load                                    | 14.2.0     |
+| 2017-06               | CT#76        | CP-171133       | 0040      | 1          | F                                                                              | Vendor-Specific-Application-Id AVP handling                                  | 14.2.0     |
+| 2018-06               | CT#80        |                 |           |            |                                                                                | Automatic upgrade from previous Release                                      | 15.0.0     |
+| 2019-09               | CT#85        | CP-192154       | 0042      | 1          | A                                                                              | draft-ietf-dime-load published as RFC 8583                                   | 15.1.0     |
+| 2020-07               | SA#88e       | -               | -         | -          |                                                                                | Update to Rel-16 version (MCC)                                               | 16.0.0     |
+| 2022-03               | SA#95e       | -               | -         | -          |                                                                                | Update to Rel-17 version (MCC)                                               | 17.0.0     |
+| 2024-03               | SA#103       | -               | -         | -          |                                                                                | Update to Rel-18 version (MCC)                                               | 18.0.0     |

marked/Rel-18/29_series/29219/raw.md

@@ -0,0 +1,862 @@
+
+
+# 3GPP TS 29.219 V18.0.0 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Policy and Charging Control: Spending Limit Reporting over Sy reference point (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
+
+## --- **Keywords**
+
+UMTS, LTE, QoS, Charging, Policy
+
+## **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.
+
+© 2024, 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 and abbreviations .....                              | 7  |
+| 3.1 Definitions.....                                               | 7  |
+| 3.2 Abbreviations .....                                            | 7  |
+| 4 Sy reference point .....                                         | 8  |
+| 4.1 Overview .....                                                 | 8  |
+| 4.2 Sy Reference model .....                                       | 8  |
+| 4.3 Subscriber Spending Limits .....                               | 8  |
+| 4.4 Functional elements.....                                       | 9  |
+| 4.4.1 PCRF .....                                                   | 9  |
+| 4.4.2 OCS .....                                                    | 9  |
+| 4.5 Spending Limits procedures over Sy reference point .....       | 9  |
+| 4.5.1 Initial/Intermediate Spending Limit Report Request.....      | 9  |
+| 4.5.1.1 General.....                                               | 9  |
+| 4.5.1.2 Detailed behaviour of the PCRF .....                       | 10 |
+| 4.5.1.3 The behaviour of the OCS .....                             | 10 |
+| 4.5.2 Spending Limit Report .....                                  | 11 |
+| 4.5.2.1 General.....                                               | 11 |
+| 4.5.2.2 The behaviour of the OCS .....                             | 12 |
+| 4.5.2.3 Detailed behaviour of the PCRF.....                        | 12 |
+| 4.5.3 Final Spending Limit Report Request .....                    | 12 |
+| 4.5.3.1 General.....                                               | 12 |
+| 4.5.3.2 Detailed behaviour of the PCRF .....                       | 13 |
+| 4.5.3.3 The behaviour of the OCS .....                             | 13 |
+| 4.5.4 Sy Session Termination by the OCS .....                      | 13 |
+| 5 Sy protocol.....                                                 | 13 |
+| 5.1 Protocol support .....                                         | 13 |
+| 5.1.1 Use of Diameter base protocol .....                          | 13 |
+| 5.1.2 Void .....                                                   | 14 |
+| 5.1.3 Accounting functionality .....                               | 14 |
+| 5.1.4 Transport protocol .....                                     | 14 |
+| 5.1.5 Advertising Application Support.....                         | 14 |
+| 5.1.6 Use of the Supported-Features AVP .....                      | 14 |
+| 5.2 Initialization and maintenance of connection and session ..... | 15 |
+| 5.3 Sy specific AVPs.....                                          | 15 |
+| 5.3.0 General .....                                                | 15 |
+| 5.3.1 Policy-Counter-Identifier AVP .....                          | 16 |
+| 5.3.2 Policy-Counter-Status AVP.....                               | 16 |
+| 5.3.3 Policy-Counter-Status-Report AVP .....                       | 16 |
+| 5.3.4 SL-Request-Type AVP.....                                     | 16 |
+| 5.3.5 Pending-Policy-Counter-Information AVP .....                 | 16 |
+| 5.3.6 Pending-Policy-Counter-Change-Time AVP .....                 | 17 |
+| 5.3.7 SN-Request-Type AVP .....                                    | 17 |
+| 5.4 Sy re-used AVPs .....                                          | 17 |
+| 5.5 Sy specific Experimental-Result-Code AVP values .....          | 18 |
+| 5.5.1 General .....                                                | 18 |
+| 5.5.2 Permanent Failures .....                                     | 18 |
+| 5.5.3 Transient Failures .....                                     | 19 |
+| 5.6 Sy Messages .....                                              | 19 |
+| 5.6.1 Command-Code Values.....                                     | 19 |
+| 5.6.2 Spending-Limit-Request (SLR) command.....                    | 19 |
+| 5.6.3 Spending-Limit-Answer (SLA) command .....                    | 20 |
+
+5.6.4 Spending-Status-Notification-Request (SNR) command..... 20  
+5.6.5 Spending-Status-Notification-Answer (SNA) command ..... 20  
+5.6.6 Session-Termination-Request (STR) command..... 21  
+5.6.7 Session-Termination-Answer (STA) command ..... 21  
+**Annex A (normative): User Identity for Fixed Broadband Access network convergence..... 22**  
+**Annex B (informative): Change history..... 23**
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> 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.
+
+# --- 1 Scope
+
+The present document provides the stage 3 specification of the Sy reference point for the present release. The functional requirements and the stage 2 specifications of the Sy reference point are contained in TS 23.203 [2]. The Sy reference point lies between the Policy and Charging Rule Function (PCRF) and the Online Charging System (OCS). The internal OCS functionality for policy counter provision management pertaining to Sy is specified in TS 32.296 [16].
+
+# --- 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.203: "Policy Control and Charging architecture".
+- [3] Void.
+- [4] IETF RFC 4005: "Diameter Network Access Server Application"
+- [5] IETF RFC 4006: "Diameter Credit Control Application".
+- [6] IETF RFC 5719: "Updated IANA Considerations for Diameter Command Code Allocations"
+- [7] IETF RFC 2234: "Augmented BNF for syntax specifications".
+- [8] 3GPP TS 29.213: "Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping".
+- [9] Void.
+- [10] Void.
+- [11] Void.
+- [12] Void.
+- [13] IETF RFC 791: "Transmission Control Protocol".
+- [14] IETF RFC 4960: "Stream Control Transmission Protocol".
+- [15] 3GPP TS 29.229: "Cx and Dx interfaces based on the Diameter protocol".
+- [16] 3GPP TS 32.296: "Telecommunication management; charging management; Online Charging System (OCS) applications and interfaces".
+- [17] ETSI TS 283 034 v2.2.0: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Network Attachment Sub-System (NASS); e4 interface based on the DIAMETER protocol".
+- [18] IETF RFC 3046: "DHCP Relay Agent Information Option".
+- [19] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points".
+
+- [20] IETF RFC 7683: "Diameter Overload Indication Conveyance".
+- [21] IETF RFC 7944: "Diameter Routing Message Priority".
+- [22] IETF RFC 8583: "Diameter Load Information Conveyance".
+- [23] IETF RFC 6733: "Diameter Base Protocol".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions 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].
+
+**policy counter:** A mechanism within the OCS to track spending applicable for a subscriber.
+
+**policy counter identifier:** A reference to a policy counter in the OCS for a subscriber.
+
+**policy counter status:** A label whose values are not standardized and that is associated with a policy counter's value relative to the spending limit(s) (the number of possible policy counter status values for a policy counter is one greater than the number of thresholds associated with that policy counter, i.e policy counter status values describe the status around the thresholds). This is used to convey information relating to subscriber spending from OCS to PCRF. Specific labels are configured jointly in OCS and PCRF.
+
+**spending limit:** A spending limit is the usage limit of a policy counter (e.g. monetary, volume, duration) that a subscriber is allowed to consume.
+
+**spending limit report:** a notification, containing the current policy counter status generated from the OCS to the PCRF via the Sy reference point.
+
+## 3.2 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].
+
+|      |                                                    |
+|------|----------------------------------------------------|
+| DRMP | Diameter Routing Message Priority                  |
+| OCS  | Online charging system                             |
+| OFCS | Offline charging system                            |
+| PCEF | Policy and Charging Enforcement Function           |
+| PCRF | Policy and Charging Rule Function                  |
+| RCAF | RAN Congestion Awareness Function                  |
+| SLA  | Spending-Limit-Answer (SL-Answer)                  |
+| SLR  | Spending-Limit-Request (SL- Request)               |
+| SNA  | Spending-Status-Notification-Answer (SN-Answer)    |
+| SNR  | Spending-Status-Notification-Request (SN- Request) |
+| STA  | Session-Termination-Answer (ST-Answer)             |
+| STR  | Session-Termination-Request (ST- Request)          |
+
+# --- 4 Sy reference point
+
+## 4.1 Overview
+
+The Sy reference point is located between the Policy and Charging Rules Function (PCRF) and the Online Charging System (OCS). The Sy reference point enables transfer of policy counter status information relating to subscriber spending from OCS to PCRF and supports the following functions:
+
+- Request of policy counter status reporting from PCRF to OCS and subscribe to or unsubscribe from spending limit reports (i.e. notifications of policy counter status changes).
+- Notification of spending limit reports from OCS to PCRF.
+- Cancellation of spending limit reporting from PCRF to OCS.
+
+Since the Sy reference point resides between the PCRF and OCS in the HPLMN, roaming with home routed or visited access as well as non-roaming scenarios are supported in the same manner.
+
+The stage 2 level requirements for the Sy reference point are defined in 3GPP TS 23.203 [2].
+
+Signalling flows related to the Sy interface are specified in 3GPP TS 29.213 [8].
+
+Refer to Annex G of 3GPP TS 29.213 [8] for Diameter overload control procedures over the Sy interface.
+
+Refer to Annex J of 3GPP TS 29.213 [8] for Diameter message priority mechanism procedures over the Sy interface.
+
+Refer to Annex K of 3GPP TS 29.213 [8] for Diameter load control procedures over the Sy interface.
+
+## 4.2 Sy Reference model
+
+The Sy reference point is defined between the PCRF and the OCS. The relationships between the involved functional entities are depicted in figure 4.2.1. The overall PCC architecture is depicted in clause 3a of 3GPP TS 29.213 [8]
+
+![Diagram of the Sy reference model showing PCRF and OCS connected by the Sy interface.](3b621c21b0af3a504a28d2547e87138f_img.jpg)
+
+The diagram shows two rectangular boxes, one on the left labeled 'PCRF' and one on the right labeled 'OCS'. A horizontal line connects the two boxes. Above the line, centered between the boxes, is the label 'Sy'. There is a small vertical tick mark on the line directly below the 'Sy' label.
+
+Diagram of the Sy reference model showing PCRF and OCS connected by the Sy interface.
+
+Figure 4.2.1: Sy reference model
+
+.Figure 4.2.2: Void
+
+## 4.3 Subscriber Spending Limits
+
+Policy decisions based on spending limits is a function that allows the PCRF to make policy decisions based on the status of policy counters that are maintained in the OCS. The PCRF uses the policy counter statuses received from the OCS as input to its policy decisions, e.g. downgrade the QoS (e.g. APN-AMBR) or modify the PCC/QoS/ADC Rules.
+
+When the status of policy counters is first required to make a policy decision for a subscriber, the PCRF uses the Initial Spending Limit Report Request procedure. The PCRF may request specific or all policy counter statuses to be reported by the OCS for the user. The OCS provides the status to the PCRF of the requested policy counters, and will notify the PCRF of any changes in the status of those policy counters. Optionally, the OCS can provide one or more pending statuses for a requested policy counter with the times that have to be applied. The pending status of a policy counter shall autonomously become the current status of a policy counter at the PCRF when the indicated corresponding time is reached. Subsequently, the provided information for pending statuses of a policy counter shall overwrite the previously received information.
+
+NOTE 1: The mechanism for provisioning the policy counters in the OCS is out of scope of this document.
+
+NOTE 2: A policy counter in the OCS can represent the spending for one or more services, one or more devices, one or more subscribers, etc. The representation is operator dependent. There is no explicit relationship between Charging-Key and policy counter.
+
+The PCRF may request reporting for specific policy counter(s) that it is not currently subscribed and/or cancel reporting for specific policy counter status(es) using the Intermediate Spending Limit Report Request. The PCRF may cancel spending limit reporting for all policy counter(s) using the Final Spending Limit Report Request.
+
+The updated subscriber profile may also trigger the PCRF sending the Initial/Intermediate/Final Spending Limit Report Request to the OCS to subscribe and/or cancel reporting for policy counter status(es). If spending limit reporting for a policy counter is enabled, the OCS shall notify the PCRF of changes in the status of this policy counter (e.g. daily spending limit of \$2 reached) and optionally pending statuses of this policy counter with the activation time (e.g. due to a billing period that will expire at midnight).
+
+## 4.4 Functional elements
+
+### 4.4.1 PCRF
+
+The Policy Control and Charging Rules Function (PCRF) is a functional element that encompasses policy control decision and flow based charging control functionalities.
+
+The PCRF may take information on the subscriber's spending status into account in its policy decisions. The PCRF may request spending limit reporting for policy counters from the OCS using the Initial or Intermediate Spending Limit Report Request procedure as specified in clause 4.5.1. The PCRF may cancel spending limit reporting for specific policy counter(s) using the Intermediate Spending Limit Report Request procedure, or for all policy counter(s) using the Final Spending Limit Report Request procedure as specified in clause 4.5.3.
+
+The PCRF shall have at least one active IP-CAN session to be able to initiate an Sy session to be used when required for spending limit reporting for that subscriber. The PCRF shall terminate the Sy session when the last IP-CAN session for that subscriber is terminated or no IP-CAN session for the same user depends on the spending status information provided over Sy reference point.
+
+The PCRF may use the status of each relevant policy counter as input to its policy decision as required by the decision logic.
+
+### 4.4.2 OCS
+
+The Online Charging System (OCS), for the purpose of policy decisions based on the subscriber's spending, shall:
+
+- maintain the policy counter statuses applicable for a subscriber.
+- report the policy counter status values for the subscriber when requested to the PCRF.
+- when a policy counter status changes, report the change to the PCRF.
+
+## 4.5 Spending Limits procedures over Sy reference point
+
+### 4.5.1 Initial/Intermediate Spending Limit Report Request
+
+#### 4.5.1.1 General
+
+This procedure shall be used by the PCRF to request the status of policy counters available at the OCS, and to subscribe or unsubscribe to updates of policy counters by the OCS.
+
+This procedure is mapped to the Spending-Limit-Request/Answer commands specified in clause 5.6.
+
+**Table 4.5.1.1/1: Initial/Intermediate Spending Limit Report Request**
+
+| Information element name                  | Mapping to Diameter AVP                                             | Cat. | Description                                                                                                                                                                                                                                                                                                                                                   |
+|-------------------------------------------|---------------------------------------------------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| User Identity                             | Subscription-Id, Logical-Access-ID AVP, Physical-Access-ID (NOTE 1) | C    | This IE shall contain the identity of the user. It shall be present in the initial request when the SL-Request-Type=INITIAL_REQUEST.                                                                                                                                                                                                                          |
+| Request Type                              | SL-Request-Type                                                     | M    | This IE shall indicate whether this is the initial or a subsequent request for the user.                                                                                                                                                                                                                                                                      |
+| Subscribed Policy Counter Identifier List | Policy-Counter-Identifier                                           | O    | This IE shall indicate the list of policy counter identifiers to be subscribed to. In the intermediate spending limit report request procedure, this list overrides a previously provisioned list. If omitted in either the Initial or Intermediate Spending Limit Report Request procedures the PCRF requests subscription to all available policy counters. |
+
+NOTE 1: The Logical-Access-ID AVP and Physical-Access-ID AVP are only applicable to Fixed Broadband Access network convergence as defined in annex A.
+
+**Table 4.5.1.1/2: Initial/Intermediate Spending Limit Report Response**
+
+| Information element name     | Mapping to Diameter AVP            | Cat. | Description                                                                                                                                                                           |
+|------------------------------|------------------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Policy Counter Status Report | Policy-Counter-Status-Report       | O    | If present, this information element shall contain a policy counter identifier, the current status value and if applicable pending policy counter statuses with the activation times. |
+| Result                       | Result-Code or Experimental-Result | M    | This IE shall contain the result of the operation.                                                                                                                                    |
+
+#### 4.5.1.2 Detailed behaviour of the PCRF
+
+The PCRF shall make use of this procedure when it determines for a subscriber that
+
+- The status of policy counter(s) to which the PCRF does not have an existing subscription for status change notifications is/are required.
+- The status of one or more, but not all, policy counter(s) to which the PCRF has an existing subscription for status change notifications are no longer required.
+
+NOTE: The Final Spending Limit Request procedure in clause 4.5.3 is used to remove all subscriptions.
+
+In the initial request, i.e. when the request is sent for the first time for the Subscriber, the PCRF shall set the SL-Request-Type AVP to the value INITIAL\_REQUEST (0). For subsequent requests for the same Subscriber, the PCRF shall set the SL-Request-Type AVP to INTERMEDIATE\_REQUEST (1).
+
+For each policy counter that the PCRF requires the current status and notifications of future status changes, the PCRF shall indicate the concerned policy counter identifiers in the request. Alternatively, the policy counter identifiers may be omitted if the PCRF requires the current status and notifications of future status changes of all available policy counters.
+
+#### 4.5.1.3 The behaviour of the OCS
+
+Upon reception of the request from the PCRF, the OCS shall check if there is an ongoing Sy session associated with the received Session-Id AVP. If there is no Sy session and the SL-Request-Type AVP is set to INITIAL\_REQUEST (0), an Sy session is created on the OCS. If there is an Sy session and the SL-Request-Type AVP is not set to INTERMEDIATE\_REQUEST (1), the OCS shall return a response with the Result-Code set to DIAMETER\_INVALID\_AVP\_VALUE and with the Failed-AVP AVP containing the SL-Request-Type AVP. If there is no Sy session and the SL-Request-Type AVP is not set to INITIAL\_REQUEST (0), the OCS shall return a response with the Result-Code AVP set to DIAMETER\_UNKNOWN\_SESSION\_ID.
+
+Upon reception of the request from the PCRF provided with explicit Policy Counter Identifier(s):
+
+If all the policy counter identifiers are known to the OCS, the OCS shall be able to subsequently notify the PCRF of any policy counter state changes and/or additions, removal or changes of pending policy counter statuses along with their activation time.
+
+If a policy counter identifier is known by the OCS, but is not applicable to the subscriber (e.g. not provisioned), the OCS may use an operator configured policy counter status to indicate this to the PCRF.
+
+If the OCS is configured to accept the request provided with unknown policy counter identifier(s), and if the OCS determines that one or more policy counter identifiers are unknown, an operator configured policy counter status may be used to indicate the policy counter identifier(s) determined as unknown by OCS. The status of known policy counter identifier(s) shall be returned to the PCRF in the same procedure in this case.
+
+Alternatively, if the OCS is configured to reject the request provided with unknown policy counter identifier(s), and if the OCS determines that one or more policy counter identifiers are unknown, the OCS shall return a response with the Experimental-Result-Code AVP set to DIAMETER\_ERROR\_UNKNOWN\_POLICY\_COUNTERS and with the Failed-AVP AVP indicating the unknown policy counter identifiers. When this failure occurs, if the SL-Request-Type AVP is set to:
+
+- INITIAL\_REQUEST (0), then the Sy session is not created.
+- INTERMEDIATE\_REQUEST (1), then none of the changes in the request take effect but the Sy session is maintained.
+
+NOTE 1: In order to avoid misbehaviors due to the policy counters maintained in the Sy session, the PCRF can terminate the Sy session invoking the Final Spending Limit Request procedure in clause 4.5.3.
+
+When the PCRF provides a new subscribed policy counter identifier list, the OCS shall remove any policy counter identifiers no longer in the list from association with the Sy session such that the OCS will no longer notify the PCRF of those policy counter state changes.
+
+If an initial or intermediate request contains no policy counter identifiers, the OCS shall subsequently notify the PCRF of all available policy counter state changes and optionally the pending policy counter statuses with the activation times. If the OCS has no available policy counters for that subscriber during the Initial Spending Limit Report Request procedure, it sets the Experimental-Result-Code to DIAMETER\_ERROR\_NO\_AVAILABLE\_POLICY\_COUNTERS. When this failure occurs, if the SL-Request-Type AVP is set to:
+
+- INITIAL\_REQUEST (0), then the Sy session is not created.
+- INTERMEDIATE\_REQUEST (1), then none of the changes in the request take effect but the Sy session is maintained.
+
+NOTE 2: The PCRF can terminate the Sy session invoking the Final Spending Limit Request procedure in clause 4.5.3, or maintain the Sy session assuming that further available policy counters will be notified.
+
+If the user identified in an initial request is not known to the OCS, the OCS shall reject the Spending Limit Report Request by including the result code of DIAMETER\_USER\_UNKNOWN in the Spending Limit Report Answer. In this case, the Sy session is not created.
+
+Upon successful creation of an Sy session, the OCS shall include the current status of all subscribed policy counters (if any) in the response and set the Result-Code to DIAMETER\_SUCCESS.
+
+### 4.5.2 Spending Limit Report
+
+#### 4.5.2.1 General
+
+This procedure shall be used by the OCS to notify the PCRF of changes in the status of subscribed policy counter(s).
+
+This procedure is mapped to the Spending-Status-Notification-Request /Answer commands specified commands specified in clause 5.6.
+
+**Table 4.5.2.1/1: Spending Limit Report Request**
+
+| Information element name     | Mapping to Diameter AVP      | Cat. | Description                                                                                                                                                                           |
+|------------------------------|------------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Policy Counter Status Report | Policy-Counter-Status-Report | M    | If present, this information element shall contain a policy counter identifier, the current status value and if applicable pending policy counter statuses with the activation times. |
+
+**Table 4.5.2.1/2: Spending Limit Report Response**
+
+| Information element name | Mapping to Diameter AVP            | Cat. | Description                                        |
+|--------------------------|------------------------------------|------|----------------------------------------------------|
+| Result                   | Result-Code or Experimental-Result | M    | This IE shall contain the result of the operation. |
+
+#### 4.5.2.2 The behaviour of the OCS
+
+When the status of a specific policy counter changes or when pending statuses associated with the policy counter are added, removed or changed, the OCS shall determine the Sy sessions impacted by the change (i.e. those Sy sessions that have subscribed to status change notifications for the changed policy counter) and send a Spending-Status-Notification-Request command including the current policy counter status, and if applicable pending policy counter statuses with the activation times to the PCRF associated with each affected Sy session. The OCS shall not send the policy counter status for the same policy counter until it received the response of the previous status report of the policy counter.
+
+If several policy counters change status at the same time, the OCS may group the status change notifications into a single Spending-Status-Notification-Request command to the PCRF by sending multiple Policy-Counter-Status-Report AVPs in the request.
+
+#### 4.5.2.3 Detailed behaviour of the PCRF
+
+The PCRF shall acknowledge the request by sending a response with a Result-Code AVP set to DIAMETER\_SUCCESS and use the status of the received policy counter(s) as input to its policy decision to apply operator defined actions, e.g. downgrade the QoS.
+
+NOTE: The values related to the status of a policy counter (e.g. valid, invalid or any other status) are not specified. The interpretation and actions related to the values are out of scope of 3GPP.
+
+The PCRF shall ignore an unknown policy counter status report for all unknown policy counter identifiers in an SLA or in an SNR from the OCS.
+
+If the PCRF receives an SNR command while it has an ongoing SLR transaction with the OCS, the PCRF shall update the policy counter information based on the SNR command. When the corresponding SLA command for the ongoing SLR transaction is eventually received, the PCRF shall only update policy counter information for counters that were not provided in the previously received SNR command.
+
+If the PCRF receives a Policy-Counter-Status-Report with one or more Pending-Policy-Counter-Information AVPs, then at the time defined by the Pending-Policy-Counter-Change-Time AVP, the pending Policy-Counter-Status shall autonomously become the current status of a policy counter. Subsequently provided information for pending statuses of a policy counter shall overwrite the previously received information. If the pending policy counter statuses are applicable to a policy counter identifier but the Pending-Policy-Counter-Information AVPs are omitted in the new policy counter status report, the PCRF shall remove all the pending policy counter statuses.
+
+### 4.5.3 Final Spending Limit Report Request
+
+#### 4.5.3.1 General
+
+This procedure shall be used by the PCRF to unsubscribe to any future updates of policy counters for a given subscriber by the OCS.
+
+This procedure is mapped to the Session-Termination-Request/Answer commands specified in IETF RFC 6733 [23].
+
+**Table 4.5.3.1/1: Final Spending Limit Report Request**
+
+| Information element name | Mapping to Diameter AVP | Cat. | Description                                                                                            |
+|--------------------------|-------------------------|------|--------------------------------------------------------------------------------------------------------|
+| Termination Cause        | Termination-Cause       | M    | This IE shall contain the reason why the session was terminated. It shall be set to "DIAMETER_LOGOUT". |
+
+**Table 4.5.3.1/2: Final Spending Limit Report Response**
+
+| Information element name | Mapping to Diameter AVP | Cat. | Description                                        |
+|--------------------------|-------------------------|------|----------------------------------------------------|
+| Result                   | Result-Code             | M    | This IE shall contain the result of the operation. |
+
+#### 4.5.3.2 Detailed behaviour of the PCRF
+
+When the PCRF decides that policy decisions for a given user no longer depend on policy counter(s) to which the PCRF has existing subscriptions for status change notifications, the PCRF shall send the Final Spending Limit Report Request to the OCS.
+
+#### 4.5.3.3 The behaviour of the OCS
+
+Upon reception of the request from the PCRF, the OCS shall check that there is an ongoing Sy session associated with the received Session-Id AVP. If there is no Sy session, the OCS shall return a response with the Result-Code AVP set to DIAMETER\_UNKNOWN\_SESSION\_ID.
+
+The OCS shall remove all policy counter subscriptions associated with the Sy session such that the OCS will no longer notify the PCRF of policy counter state changes and close the session by returning a response with the Result-Code AVP set to DIAMETER\_SUCCESS.
+
+### 4.5.4 Sy Session Termination by the OCS
+
+If the ASR feature is supported, and the OCS decides that the Sy session for a subscriber needs to be terminated (e.g. because subscriber is removed from an OCS system), the OCS shall send the Spending-Status-Notification-Request (SNR) containing the SN-Request-Type AVP with bit 1 (Abort Session Request) set to the PCRF.
+
+Upon receipt of the SNR containing the SN-Request-Type AVP with bit 1 set, the PCRF shall acknowledge the receipt of the SNR by sending the Spending-Status-Notification-Answer (SNA) and shall then send a Final Spending Limit Report Request as specified in clause 4.5.3.
+
+NOTE: The termination of the Sy session causes the H-PCRF to make the applicable policy decision and act accordingly, i.e. sessions on other interfaces such as the Rx or Gx interface will remain established, unless the policy decision causes their termination.
+
+# 5 Sy protocol
+
+## 5.1 Protocol support
+
+### 5.1.1 Use of Diameter base protocol
+
+The Diameter Base Protocol as specified in IETF RFC 6733 [23] shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and error codes as specified in this specification. Unless otherwise specified, the procedures (including error handling and unrecognised information handling) shall be used unmodified.
+
+With regard to the Diameter protocol defined over the Sy interface, the OCS acts as a Diameter server, in the sense that it is the network element that handles policy counter status requests for a particular realm. The PCRF acts as the Diameter client, in the sense that it is the network element requesting policy counter status to the OCS.
+
+A Diameter routing table entry can have a different destination based on the application identifier of the command. The application identifier stored in the command header must match the value of any application identifier AVPs in the command body. Diameter agents (relay, proxy, redirection, translation agents) should use the application identifier in the command header to route to a suitable destination.
+
+### 5.1.2 Void
+
+### 5.1.3 Accounting functionality
+
+Accounting functionality (Accounting Session State Machine, related command codes and AVPs) shall not be used on the Sy interface.
+
+### 5.1.4 Transport protocol
+
+Diameter messages over the Sy interface shall make use of TCP IETF RFC 791 [13] or SCTP IETF RFC 4960 [14].
+
+### 5.1.5 Advertising Application Support
+
+The Diameter application identifier assigned to the Sy interface application is 16777302.
+
+The PCRF and OCS shall advertise support of the Diameter Sy Application by including the value of the Sy application identifier in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands.
+
+The vendor identifier value of 3GPP (10415) shall be included in the Supported-Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands, and in the Vendor-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands.
+
+The Vendor-Id AVP included in Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands that is not included in the Vendor-Specific-Application-Id AVPs as described above shall indicate the manufacturer of the Diameter node as per IETF RFC 6733 [23].
+
+### 5.1.6 Use of the Supported-Features AVP
+
+The Supported-Features AVP is used during session establishment to inform the destination host about the required and optional features that the origin host supports. The client shall, in the first request in a Diameter session indicate the set of supported features. The server shall, in the first answer within the Diameter session indicate the set of features that it has in common with the client and that the server shall support within the same Diameter session. Any further command messages shall always be compliant with the list of supported features indicated in the Supported-Features AVPs during session establishment. Features that are not advertised as supported shall not be used to construct the command messages for that Diameter session. Unless otherwise stated, the use of the Supported-Features AVP on the Sy reference point shall be compliant with the requirements for dynamic discovery of supported features and associated error handling on the Cx reference point as defined in clause 7.2.1 of TS 29.229 [15].
+
+The base functionality for the Sy reference point is the 3GPP Rel-11 standard and a feature is an extension to that functionality. If the origin host does not support any features beyond the base functionality, the Supported-Features AVP may be absent from the Sy commands. As defined in clause 7.1.1 of TS 29.229 [15], when extending the application by adding new AVPs for a feature, the new AVPs shall have the M bit cleared and the AVP shall not be defined mandatory in the command ABNF.
+
+As defined in TS 29.229 [15], the Supported-Features AVP is of type grouped and contains the Vendor-Id, Feature-List-ID and Feature-List AVPs. On the Sy reference point, the Supported-Features AVP is used to identify features that have been defined by 3GPP and hence, for features defined in this document, the Vendor-Id AVP shall contain the vendor ID of 3GPP (10415). If there are multiple feature lists defined for the Sy reference point, the Feature-List-ID AVP shall differentiate those lists from one another.
+
+On receiving an initial request application message, the destination host shall act as defined in clause 7.2.1 of TS 29.229 [15]. The following exceptions apply to the initial SLR/SLA command pair:
+
+- If the PCRF supports any supported features defined for Sy, the SLR shall include the features supported by the PCRF within Supported-Features AVP(s) with the 'M' bit cleared.
+
+NOTE 2: One instance of Supported-Features AVP is needed per Feature-List-ID.
+
+- If the SLR command does not contain any Supported-Features AVP(s) and the OCS supports no supported features defined for Sy functionality, the OCS shall not include the Supported-Features AVP in the SLA command. In this case, both PCRF and OCS shall not use any supported features defined for Sy.
+
+Once the PCRF and OCS have negotiated the set of supported features during session establishment, the set of common features shall be used during the lifetime of the Diameter session.
+
+The table below defines the features applicable to the Sy interface for the feature list with a Feature-List-ID of 1.
+
+**Table 5.1.6-1: Features of Feature-List-ID 1 used on the Sy interface**
+
+| Feature bit                                                                                                                                                                                                                                                                                                                                                                       | Feature | M/O | Description                                                    |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-----|----------------------------------------------------------------|
+| 0                                                                                                                                                                                                                                                                                                                                                                                 | ASR     | O   | Sy Session Termination by the OCS as specified in clause 4.5.4 |
+| Feature bit: The order number of the bit within the Feature-List AVP where the least significant bit is assigned number "0".<br>Feature: A short name that can be used to refer to the bit and to the feature, e.g. "EPS".<br>M/O: Defines if the implementation of the feature is mandatory ("M") or optional ("O").<br>Description: A clear textual description of the feature. |         |     |                                                                |
+
+## 5.2 Initialization and maintenance of connection and session
+
+The Diameter protocol between the PCRF and the OCS, shall always keep the session state, and use the same Session-Id parameter for the lifetime of each Diameter session.
+
+Each Diameter session shall identify a Sy session for a given user. In order to indicate that the session state is to be maintained, the Diameter client and server shall not include the Auth-Session-State AVP, either in the request or in the response messages (see IETF RFC 6733 [23]).
+
+The PCRF shall link the Gx session(s) or S9 session with the Sy session at Sy session initialization and maintain that until the IP-CAN session(s) for that subscriber are terminated or no IP-CAN session for the same user depends on the spending status information provided over Sy reference point.
+
+## 5.3 Sy specific AVPs
+
+### 5.3.0 General
+
+Table 5.3.0.1 describes the Diameter AVPs defined for the Sy reference point, their AVP Code values, types and possible flag values. The Vendor-Id header of all AVPs defined in the present document shall be set to 3GPP (10415).
+
+**Table 5.3.0.1: Sy specific Diameter AVPs**
+
+| Attribute Name                                                                                                                                                                                                                                            | AVP Code | Clause defined | Value Type | AVP Flag rules (Note 1) |     |            |          | Applicability (Note 2) |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------------|------------|-------------------------|-----|------------|----------|------------------------|
+|                                                                                                                                                                                                                                                           |          |                |            | Must                    | May | Should not | Must not |                        |
+| Pending-Policy-Counter-Information                                                                                                                                                                                                                        | 2905     | 5.3.5          | Grouped    | M,V                     | P   |            |          |                        |
+| Pending-Policy-Counter-Change-Time                                                                                                                                                                                                                        | 2906     | 5.3.6          | Time       | M,V                     | P   |            |          |                        |
+| Policy-Counter-Identifier                                                                                                                                                                                                                                 | 2901     | 5.3.1          | UTF8String | M,V                     | P   |            |          |                        |
+| Policy-Counter-Status                                                                                                                                                                                                                                     | 2902     | 5.3.2          | UTF8String | M,V                     | P   |            |          |                        |
+| Policy-Counter-Status-Report                                                                                                                                                                                                                              | 2903     | 5.3.3          | Grouped    | M,V                     | P   |            |          |                        |
+| SL-Request-Type                                                                                                                                                                                                                                           | 2904     | 5.3.4          | Enumerated | M,V                     | P   |            |          |                        |
+| SN-Request-Type                                                                                                                                                                                                                                           | 2907     | 5.3.7          | Unsigned32 | V                       | P   |            | M        | ASR                    |
+| NOTE 1: The AVP header bit denoted as 'M', indicates whether support of the AVP is required. The AVP header bit denoted as 'V', indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see IETF RFC 6733 [23]. |          |                |            |                         |     |            |          |                        |
+| NOTE 2: AVPs marked with a supported feature are applicable as described in clause 5.1.6.                                                                                                                                                                 |          |                |            |                         |     |            |          |                        |
+
+### 5.3.1 Policy-Counter-Identifier AVP
+
+The Policy-Counter-Identifier AVP (AVP code 2901) is of type UTF8String, and it uniquely identifies a policy counter that is maintained per subscriber within the OCS.
+
+### 5.3.2 Policy-Counter-Status AVP
+
+The Policy-Counter-Status AVP (AVP code 2902) is of type UTF8String, and identifies the policy counter status applicable for a specific policy counter and subscriber.
+
+NOTE: The valid values for the Policy-Counter-Status AVP are specific for each Policy-Counter-Identifier value.
+
+The values (e.g. valid, invalid or any other status) are not specified. The interpretation and actions related to the defined values are out of scope of 3GPP.
+
+### 5.3.3 Policy-Counter-Status-Report AVP
+
+The Policy-Counter-Status-Report AVP (AVP code 2903) is of type Grouped. It is used by the OCS to report the status of a specific policy counter.
+
+Associated pending policy counter statuses shall always be provided within Pending-Policy-Counter-Information AVPs if the pending policy counter statuses are applicable to the policy counter identifier. If there are no Pending-Policy-Counter-Information AVPs provided within the Policy-Counter-Status-Report AVP, previously provided pending counter statuses are removed. In addition, newly provided pending policy counter statuses overwrite previously provided ones.
+
+AVP Format:
+
+```
+Policy-Counter-Status-Report ::= < AVP Header: 2903 >
+    { Policy-Counter-Identifier }
+    { Policy-Counter-Status }
+    *[ Pending-Policy-Counter-Information ]
+    *[ AVP ]
+```
+
+### 5.3.4 SL-Request-Type AVP
+
+The SL-Request-Type AVP (AVP code 2904) is of type Enumerated, and informs the OCS whether the SLR command is being sent as part of the initial or intermediate spending limit report request procedure.
+
+The following values are defined:
+
+INITIAL\_REQUEST (0)
+
+This value indicates that this is the first request in the Diameter session.
+
+INTERMEDIATE\_REQUEST (1)
+
+This value indicates that this is the second or subsequent request in the Diameter session.
+
+### 5.3.5 Pending-Policy-Counter-Information AVP
+
+The Pending-Policy-Counter-Information AVP (AVP code 2905) is of type Grouped, which contains the pending policy counter status and the active time. If multiple pending policy counter AVPs are included, they shall be sorted in order of change time.
+
+AVP Format:
+
+```
+Pending-Policy-Counter-Information ::= < AVP Header: 2905 >
+    { Policy-Counter-Status }
+    { Pending-Policy-Counter-Change-Time }
+    *[ AVP ]
+```
+
+NOTE: The valid values for the Pending-Policy-Counter-Information AVP are specific for each Policy-Counter-Identifier value.
+
+### 5.3.6 Pending-Policy-Counter-Change-Time AVP
+
+The Pending-Policy-Counter-Change-Time AVP (AVP code 2906) is of type Time. This value indicates the NTP time at which the pending policy counter status becomes the current status of a policy counter.
+
+### 5.3.7 SN-Request-Type AVP
+
+The SN-Request-Type AVP (AVP code 2907) shall be of type Unsigned32 and shall contain a bit mask, and informs the PCRF about the type of the Spending-Status-Notification-Request (SNR). The bit 0 shall be the least significant bit. For example, to get the value of bit 0, a bit mask of 0x0001 should be used.
+
+The following values are defined, and multiple bits may be set in combination:
+
+**Table 5.3.7-1: SN-Request-Type AVP**
+
+| Bit | Name                  | Description                                                                                                                                                                                                                 |
+|-----|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 0   | Normal Request        | This bit, when set, indicates that the SNR is used only to convey a spending limit report as detailed in clause 4.5.2. This shall be the default value that applies when the SN-Request-Type AVP is not included in an SNR. |
+| 1   | Abort Session Request | This bit, when set, indicates that the SNR is used to request the termination of the Sy session as detailed in clause 4.5.4                                                                                                 |
+
+## 5.4 Sy re-used AVPs
+
+Table 5.4 lists the Diameter AVPs re-used by the Sy reference point from existing Diameter Applications, reference to their respective specifications and a short description of their usage within the Sy reference point. Other AVPs from existing Diameter Applications, except for the AVPs from Diameter base protocol, do not need to be supported. The AVPs from Diameter base protocol are not included in table 5.4, but they are re-used for the Sy reference point. Unless otherwise stated, re-used AVPs shall maintain their 'M', 'P' and 'V' flag settings. Where 3GPP Radius VSAs are re-used, unless otherwise stated, they shall be translated to Diameter AVPs as described in RFC 4005 [4] with the exception that the 'M' flag shall be set and the 'P' flag may be set.
+
+**Table 5.4: Sy re-used Diameter AVPs**
+
+| Attribute Name        | Reference            | Description                                                                                                                                                                                                                                                                                                         |
+|-----------------------|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| DRMP                  | IETF RFC 7944 [21]   | Allows Diameter endpoints to indicate the relative priority of Diameter transactions.                                                                                                                                                                                                                               |
+| Subscription-Id       | IETF RFC 4006 [5]    | The identification of the subscription (IMSI, MSISDN, etc)                                                                                                                                                                                                                                                          |
+| Load                  | IETF RFC 8583 [22]   | The AVP used to convey load information between Diameter nodes.<br>This AVP and all AVPs within this grouped AVP shall have the 'M' bit cleared.                                                                                                                                                                    |
+| Logical-Access-ID     | ETSI TS 283 034 [17] | Contains a Circuit-ID (as defined in IETF RFC 3046 [18]). The Logical Access ID may explicitly contain the identity of the Virtual Path and Virtual Channel carrying the traffic. Applicable only for Fixed Broadband Access network convergence as defined in annex A.<br>This AVP shall have the 'M' bit cleared. |
+| OC-OLR                | IETF 7683 [20]       | Contains the necessary information to convey an overload report.                                                                                                                                                                                                                                                    |
+| OC-Supported-Features | IETF 7683 [20]       | Defines the support for the Diameter overload indication conveyance by the sending node.                                                                                                                                                                                                                            |
+| Physical-Access-ID    | ETSI TS 283 034 [17] | Identifies the physical access to which the user equipment is connected. Includes a port identifier and the identity of the access node where the port resides. Applicable only for Fixed Broadband Access network convergence as defined in annex A.<br>This AVP shall have the 'M' bit cleared.                   |
+| Supported-Features    | 3GPP TS 29.229 [15]  | If present in a request, this AVP informs the destination host about the features that the origin host supports. If present in an answer, this AVP informs the destination host about common features with the origin host.                                                                                         |
+
+## 5.5 Sy specific Experimental-Result-Code AVP values
+
+### 5.5.1 General
+
+IETF RFC 6733 [23] specifies the Experimental-Result AVP containing Vendor-ID AVP and Experimental-Result-Code AVP. The Experimental-Result-Code AVP (AVP Code 298) is of type Unsigned32 and contains a vendor-assigned value representing the result of processing a request. The Vendor-ID AVP shall be set to 3GPP (10415).
+
+### 5.5.2 Permanent Failures
+
+Errors that fall within the Permanent Failures category shall be used to inform the peer that the request failed, and the request should not be attempted again.
+
+The Result-Code AVP values defined in Diameter base protocol IETF RFC 6733 [23] are applicable. Also, the following Result-Code AVP value defined in IETF RFC 4006 [5] is applicable:
+
+DIAMETER\_USER\_UNKNOWN (5030)
+
+This error shall be used by the OCS to indicate to the PCRF that the end user specified in the request is unknown to the OCS and that the Sy session cannot be created.
+
+The following specific Sy Experimental-Result-Code value is defined for permanent failures:
+
+DIAMETER\_ERROR\_UNKNOWN\_POLICY\_COUNTERS (5570)
+
+This error shall be used by the OCS to indicate to the PCRF that the OCS does not recognize one or more Policy Counters specified in the request, when the OCS is configured to reject the request provided with unknown policy counter identifier(s).
+
+### 5.5.3 Transient Failures
+
+Errors that fall within the transient failures category are used to inform a peer that the request could not be satisfied at the time it was received, but may be able to satisfy the request in the future.
+
+The Result-Code AVP values defined in Diameter base protocol IETF RFC 6733 [23] are applicable. Also the following specific Sy Experimental-Result-Code value is defined for transient failures:
+
+DIAMETER\_ERROR\_NO\_AVAILABLE\_POLICY\_COUNTERS (4241)
+
+This error shall be used by the OCS to indicate to the PCRF that the OCS has no available policy counters for the subscriber.
+
+The PCRF may retry the request based on local configuration or operator policy on receipt of a transient failure.
+
+## 5.6 Sy Messages
+
+### 5.6.1 Command-Code Values
+
+This clause defines the Command-Code values for the Sy interface application as allocated by IANA from the vendor-specific namespace defined in IETF RFC 5719 [6]. Every command is defined by means of the ABNF syntax IETF RFC 2234 [7], according to the rules in IETF RFC 6733 [23].
+
+The following Command Codes are defined in this specification:
+
+**Table 5.6.1: Command-Code values for Sy**
+
+| Command-Name                         | Abbreviation | Code    | Section |
+|--------------------------------------|--------------|---------|---------|
+| Spending-Limit-Request               | SLR          | 8388635 | 5.6.2   |
+| Spending-Limit-Answer                | SLA          | 8388635 | 5.6.3   |
+| Spending-Status-Notification-Request | SNR          | 8388636 | 5.6.4   |
+| Spending-Status-Notification-Answer  | SNA          | 8388636 | 5.6.5   |
+
+In addition, the Session-Termination-Request and Session-Termination-Answer commands are reused from IETF RFC 6733 [23].
+
+For the commands defined in this specification and reused commands, the Application-ID field shall be set to 16777302.
+
+### 5.6.2 Spending-Limit-Request (SLR) command
+
+The SLR command, indicated by the Command-Code field set to 8388635 and the 'R' bit set in the Command Flags field, is sent by the PCRF to the OCS as part of the Initial or Intermediate Spending Limit Report Request procedure.
+
+Message Format:
+
+```
+<SL-Request> ::= <Diameter Header: 8388635, REQ, PXY >
+                < Session-Id >
+                [ DRMP ]
+                { Auth-Application-Id }
+                { Origin-Host }
+                { Origin-Realm }
+                { Destination-Realm }
+                [ Destination-Host ]
+                [ Origin-State-Id ]
+                [ OC-Supported-Features ]
+                * [ Supported-Features ]
+                { SL-Request-Type }
+                * [ Subscription-Id ]
+                * [ Policy-Counter-Identifier ]
+                [ Logical-Access-ID ]
+                [ Physical-Access-ID ]
+                * [ Proxy-Info ]
+                * [ Route-Record ]
+                * [ AVP ]
+```
+
+NOTE: Multiple instances of the Subscription-Id AVP in the SLR command correspond to multiple types of identifier for the same subscriber, for example IMSI and MSISDN.
+
+### 5.6.3 Spending-Limit-Answer (SLA) command
+
+The SLA command, indicated by the Command-Code field set to 8388635 and the 'R' bit cleared in the Command Flags field, is sent by the OCS to the PCRF as part of the Initial or Intermediate Spending Limit Report Request procedure.
+
+Message Format:
+
+```
+<SL-Answer> ::= < Diameter Header: 8388635, PXY >
+                < Session-Id >
+                [ DRMP ]
+                { Auth-Application-Id }
+                { Origin-Host }
+                { Origin-Realm }
+                [ Result-Code ]
+                [ Experimental-Result ]
+                [ OC-Supported-Features ]
+                [ OC-OLR ]
+                * [ Supported-Features ]
+                * [ Policy-Counter-Status-Report ]
+                [ Error-Message ]
+                [ Error-Reporting-Host ]
+                [ Failed-AVP ]
+                [ Origin-State-Id ]
+                * [ Redirect-Host ]
+                [ Redirect-Host-Usage ]
+                [ Redirect-Max-Cache-Time ]
+                * [ Proxy-Info ]
+                * [ Load ]
+                * [ AVP ]
+```
+
+### 5.6.4 Spending-Status-Notification-Request (SNR) command
+
+The SNR command, indicated by the Command-Code field set to 8388636 and the 'R' bit set in the Command Flags field, is sent by the OCS to the PCRF as part of the Spending Limit Report procedure.
+
+Message Format:
+
+```
+<SN-Request> ::= < Diameter Header: 8388636, REQ, PXY >
+                < Session-Id >
+                [ DRMP ]
+                { Origin-Host }
+                { Origin-Realm }
+                { Destination-Realm }
+                { Destination-Host }
+                { Auth-Application-Id }
+                [ Origin-State-Id ]
+                [ OC-Supported-Features ]
+                * [ Policy-Counter-Status-Report ]
+                [ SN-Request-Type ]
+                * [ Proxy-Info ]
+                * [ Route-Record ]
+                * [ AVP ]
+```
+
+### 5.6.5 Spending-Status-Notification-Answer (SNA) command
+
+The SNA command, indicated by the Command-Code field set to 8388636 and the 'R' bit cleared in the Command Flags field, is sent by the PCRF to the OCS as part of the Spending Limit Report procedure.
+
+Message Format:
+
+```
+<SN-Answer> ::= < Diameter Header: 8388636, PXY >
+                < Session-Id >
+                [ DRMP ]
+                { Origin-Host }
+                { Origin-Realm }
+                [ Result-Code ]
+                [ Experimental-Result ]
+```
+
+```
+[ Origin-State-Id ]  
+[ OC-Supported-Features ]  
+[ OC-OLR ]  
+[ Error-Message ]  
+[ Error-Reporting-Host ]  
+*[ Redirect-Host ]  
+[ Redirect-Host-Usage ]  
+[ Redirect-Max-Cache-Time ]  
+[ Failed-AVP ]  
+*[ Proxy-Info ]  
+*[ AVP ]
+```
+
+### 5.6.6 Session-Termination-Request (STR) command
+
+The STR command, indicated by the Command-Code field set to 275 and the 'R' bit set in the Command Flags field, is sent by the PCRF to the OCS as part of the Final Spending Limit Report Request procedure.
+
+Message Format:
+
+```
+<ST-Request> ::= < Diameter Header: 275, REQ, PXY >  
+                < Session-Id >  
+                [ DRMP ]  
+                { Origin-Host }  
+                { Origin-Realm }  
+                { Destination-Realm }  
+                { Auth-Application-Id }  
+                { Termination-Cause }  
+                [ Destination-Host ]  
+                [ OC-Supported-Features ]  
+                [ Origin-State-Id ]  
+                *[ Proxy-Info ]  
+                *[ Route-Record ]  
+                *[ AVP ]
+```
+
+### 5.6.7 Session-Termination-Answer (STA) command
+
+The STA command, indicated by the Command-Code field set to 275 and the 'R' bit cleared in the Command Flags field, is sent by the OCS to the PCRF as part of the Final Spending Limit Report Request procedure.
+
+Message Format:
+
+```
+<ST-Answer> ::= < Diameter Header: 275, PXY >  
+                < Session-Id >  
+                [ DRMP ]  
+                { Origin-Host }  
+                { Origin-Realm }  
+                [ Result-Code ]  
+                [ Error-Message ]  
+                [ Error-Reporting-Host ]  
+                [ Failed-AVP ]  
+                [ Origin-State-Id ]  
+                [ OC-Supported-Features ]  
+                [ OC-OLR ]  
+                *[ Redirect-Host ]  
+                [ Redirect-Host-Usage ]  
+                [ Redirect-Max-Cache-Time ]  
+                *[ Proxy-Info ]  
+                *[ Load ]  
+                *[ AVP ]
+```
+
+# --- Annex A (normative): User Identity for Fixed Broadband Access network convergence
+
+In the Fixed Broadband Access network convergence scenario, the User Identity refers to the Subscriber Identifier as defined in TS 29.212 [19] Annex G.5.1.6.
+
+If the User Identity is the Access Line Identifier, the Logical-Access-ID AVP and Physical-Access-ID AVP are included in the SLR command instead of the Subscription-Id AVP.
+
+# Annex B (informative): Change history
+
+| Change history |        |           |      |     |                                                                                                                 |                                                                         |        |
+|----------------|--------|-----------|------|-----|-----------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------|--------|
+| Date           | TSG #  | TSG Doc.  | CR   | Rev | Subject/Comment                                                                                                 | Old                                                                     | New    |
+| 2014-12        | TSG#66 | CP-140922 | 020  | 2   | Update PCC architecture diagrams to include Np reference point                                                  | 12.2.0                                                                  | 13.0.0 |
+| 2015-06        | TSG#68 | CP-150342 | 0023 | 1   | Notify a pending policy counter status change                                                                   | 13.0.0                                                                  | 13.1.0 |
+| 2015-06        | TSG#68 | CP-150342 | 0026 | 1   | Correction to pending policy counters status report                                                             | 13.0.0                                                                  | 13.1.0 |
+| 2015-06        | TSG#68 | CP-150342 | 0029 | 5   | Including the Supported-Features AVP                                                                            | 13.0.0                                                                  | 13.1.0 |
+| 2015-06        | TSG#68 | CP-150348 | 0031 | 1   | Usage of AVPs related to user identity for convergence scenario                                                 | 13.0.0                                                                  | 13.1.0 |
+| 2015-06        | TSG#68 | CP-150360 | 0032 | 1   | Diameter overload control over Sy                                                                               | 13.0.0                                                                  | 13.1.0 |
+| 2015-06        | TSG#68 | CP-150363 | 0034 | 1   | Correcting Hanging Paragraphs                                                                                   | 13.0.0                                                                  | 13.1.0 |
+| 2015-12        | TSG#70 | CP-150797 | 0040 | 1   | Update the PCC architecture figures in 29.219                                                                   | 13.1.0                                                                  | 13.2.0 |
+| 2015-12        | TSG#70 | CP-150630 | 0041 | 1   | Update draft-ietf-dime-ovli reference to RFC 7683                                                               | 13.1.0                                                                  | 13.2.0 |
+| 2015-12        | TSG#70 | CP-150788 | 0042 | 3   | Sy interface impacts for Race condition handling                                                                | 13.1.0                                                                  | 13.2.0 |
+| 2015-12        | TSG#70 | CP-150788 | 0046 | 2   | Correction text for the use of the Spending-Status-Notification-Request (SNR) command on the Sy reference point | 13.1.0                                                                  | 13.2.0 |
+| Change history |        |           |      |     |                                                                                                                 |                                                                         |        |
+| Date           | TSG #  | TSG Doc.  | CR   | Rev | Cat                                                                                                             | Subject/Comment                                                         | New    |
+| 2016-03        | TSG#71 | CP-160093 | 0047 | 2   | B                                                                                                               | Diameter Message Priority over Sy interface                             | 13.3.0 |
+| 2016-12        | TSG#74 | CP-160614 | 0052 | -   | F                                                                                                               | Change IETF drmp draft version to official RFC 7944                     | 13.4.0 |
+| 2016-12        | TSG#74 | CP-160615 | 0051 | 2   | B                                                                                                               | Diameter Load Control Mechanism                                         | 14.0.0 |
+| 2016-12        | TSG#74 | CP-160616 | 0053 | 1   | F                                                                                                               | Diameter base protocol specification update                             | 14.0.0 |
+| 2017-03        | TSG#75 | CP-170076 | 0055 | 1   | F                                                                                                               | Update instance number for the Failed-AVP in answer commands            | 14.1.0 |
+| 2017-06        | TSG#76 | CP-171119 | 0057 | 1   | F                                                                                                               | Reference update for draft-ietf-dime-load                               | 14.2.0 |
+| 2017-09        | TSG#77 | CP-172054 | 0062 | 2   | B                                                                                                               | Enhancement on Sy reference point                                       | 15.0.0 |
+| 2018-03        | TSG#79 | CP-180049 | 0063 | 2   | F                                                                                                               | Supported-Features AVP missing in SLR/SLA's ABNF                        | 15.1.0 |
+| 2019-06        | TSG#84 | CP-191093 | 0073 | 1   | A                                                                                                               | Correction of OCS behaviour for unknown and unavailable Policy Counters | 15.2.0 |
+| 2019-09        | TSG#85 | CP-192154 | 0075 | 1   | A                                                                                                               | draft-ietf-dime-load published as RFC 8583                              | 15.3.0 |
+| 2020-07        | SA#88e | -         | -    | -   |                                                                                                                 | Update to Rel-16 version (MCC)                                          | 16.0.0 |
+| 2022-03        | SA#95e | -         | -    | -   |                                                                                                                 | Update to Rel-17 version (MCC)                                          | 17.0.0 |
+| 2024-03        | SA#103 | -         | -    | -   |                                                                                                                 | Update to Rel-18 version (MCC)                                          | 18.0.0 |

marked/Rel-18/29_series/29250/raw.md

@@ -0,0 +1,1157 @@
+
+
+# 3GPP TS 29.250 V18.0.0 (2024-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Nu reference point between SCEF and PFDF for sponsored data connectivity (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 stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' in smaller letters below the logo.
+
+3GPP logo
+
+## --- **Keywords**
+
+<keyword[, keyword, ...]>
+
+## **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.
+
+© 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM 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 and abbreviations .....                    | 7  |
+| 3.1 Definitions.....                                     | 7  |
+| 3.2 Abbreviations .....                                  | 7  |
+| 4 Nu reference point.....                                | 7  |
+| 4.1 Overview .....                                       | 7  |
+| 4.2 Nu reference model .....                             | 7  |
+| 4.3 Functional elements.....                             | 8  |
+| 4.3.1 PFDF.....                                          | 8  |
+| 4.3.2 SCEF.....                                          | 8  |
+| 4.4 Procedures over Nu reference point.....              | 8  |
+| 4.4.1 Management of PFD.....                             | 8  |
+| 4.4.2 PFD management notification .....                  | 9  |
+| 5 Nu protocol .....                                      | 9  |
+| 5.1 Introduction .....                                   | 9  |
+| 5.2 Transport layer .....                                | 10 |
+| 5.3 Application delivery layer.....                      | 10 |
+| 5.3.1 General .....                                      | 10 |
+| 5.3.2 HTTP status codes.....                             | 10 |
+| 5.3.3 Methods .....                                      | 10 |
+| 5.3.4 Resources and URI design.....                      | 11 |
+| 5.3.5 HTTP request/response formats .....                | 11 |
+| 5.3.5.1 General.....                                     | 11 |
+| 5.3.5.2 POST /nuapplication/provisioning .....           | 12 |
+| 5.3.5.3 POST /nuapplication/notification .....           | 14 |
+| 5.3.6 Feature negotiation .....                          | 15 |
+| 5.3.6.1 General.....                                     | 15 |
+| 5.3.6.2 HTTP custom headers.....                         | 16 |
+| 5.3.6.2.1 3gpp-Optional-Features.....                    | 16 |
+| 5.3.6.2.2 3gpp-Required-Features .....                   | 16 |
+| 5.3.6.2.3 3gpp-Accepted-Features.....                    | 16 |
+| 5.4 Specific application communication .....             | 17 |
+| 5.4.1 General .....                                      | 17 |
+| 5.4.2 Content type.....                                  | 17 |
+| 5.4.3 JSON provisioning fields .....                     | 17 |
+| 5.4.3.1 General.....                                     | 17 |
+| 5.4.3.2 scef-notification-uri .....                      | 17 |
+| 5.4.4 Void.....                                          | 18 |
+| 5.4.5 JSON errors and informational response fields..... | 18 |
+| 5.4.5.1 General.....                                     | 18 |
+| 5.4.6 JSON report fields .....                           | 18 |
+| 5.4.6.1 General.....                                     | 18 |
+| 5.4.6.2 pfd-reports.....                                 | 18 |
+| 5.4.6.3 application-ids.....                             | 19 |
+| 5.4.7 JSON notification fields .....                     | 19 |
+| 5.4.7.1 General.....                                     | 19 |
+| 5.4.7.2 notification-pfd-reports.....                    | 19 |
+| 5.4.7.3 user-plane-location-area.....                    | 20 |
+| 5.4.7.4 cell-ids.....                                    | 20 |
+| 5.4.7.5 enodeb-ids.....                                  | 20 |
+| 5.4.7.6 extended-enodeb-ids .....                        | 20 |
+| 5.4.7.7 routing-area-ids .....                           | 20 |
+
+|                               |                                               |           |
+|-------------------------------|-----------------------------------------------|-----------|
+| 5.4.7.8                       | tracking-area-ids .....                       | 21        |
+| 5.5                           | PFDF discovery .....                          | 21        |
+| 5.6                           | SCEF discovery .....                          | 21        |
+| 6                             | Secure communication .....                    | 21        |
+| <b>Annex A (informative):</b> | <b>JSON Schema .....</b>                      | <b>21</b> |
+| A.1                           | Provisioning schema .....                     | 21        |
+| A.2                           | Error and Informational response schema ..... | 23        |
+| A.3                           | PFD management notification schema .....      | 25        |
+| <b>Annex B (informative):</b> | <b>Call Flows .....</b>                       | <b>28</b> |
+| B.1                           | General .....                                 | 28        |
+| B.2                           | Provisioning of PFDs .....                    | 28        |
+| <b>Annex C (informative):</b> | <b>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.
+
+# 1 Scope
+
+The present document provides the stage 3 specification of the Nu reference point. The functional requirements and the stage 2 specifications of the Nu reference point are specified in 3GPP TS 23.682 [2]. The Nu reference point lies between the Packet Flow Description Function (PFDF) and the Service Capability Exposure Function (SCEF).
+
+# 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.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
+- [3] 3GPP TS 23.203: "Policy and charging control architecture".
+- [4] 3GPP TS 29.213: "Policy and Charging Control signalling flows and QoS parameter mapping".
+- [5] 3GPP TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security".
+- [6] IETF RFC 2818: "HTTP Over TLS".
+- [7] IETF RFC 793: "Transmission Control Protocol".
+- [8] Void.
+- [9] 3GPP TS 29.251: "Gw and Gwn reference points for sponsored data connectivity".
+- [10] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax".
+- [11] IETF RFC 7159: "The JavaScript Object Notation (JSON) Data Interchange Format".
+- [12] IETF draft-newton-json-content-rules-09: "A Language for Rules Describing JSON Content".
+
+NOTE: This individual draft will not further progress in IETF. It is available from the following link:  
+<https://www.ietf.org/archive/id/draft-newton-json-content-rules-09.txt>.
+
+- [13] IETF RFC 7230: "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing".
+- [14] IETF RFC 7231: "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content".
+- [15] IETF RFC 7232: "Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests".
+- [16] IETF RFC 7233: "Hypertext Transfer Protocol (HTTP/1.1): Range Requests".
+- [17] IETF RFC 7234: "Hypertext Transfer Protocol (HTTP/1.1): Caching".
+- [18] IETF RFC 7235: "Hypertext Transfer Protocol (HTTP/1.1): Authentication".
+- [19] 3GPP TS 29.274: "Evolved GPRS Tunnelling Protocol for EPS (GTPv2)".
+
+# 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].
+
+**Packet Flow Description (PFD):** A set of information enabling the detection of application traffic provided by a 3<sup>rd</sup> party service provider (from 3GPP TS 23.203 [3]).
+
+## 3.2 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 3GPP TR 21.905 [1].
+
+|      |                                          |
+|------|------------------------------------------|
+| JSON | JavaScript Object Notation               |
+| PCEF | Policy and Charging Enforcement Function |
+| PFD  | Packet Flow Description                  |
+| PFDF | Packet Flow Description Function         |
+| SCEF | Service Capability Exposure Function     |
+| TDF  | Traffic Detection Function               |
+
+# 4 Nu reference point
+
+## 4.1 Overview
+
+The Nu reference point is located between the Packet Flow Description Function (PFDF) and the Service Capability Exposure Function (SCEF). The Nu reference point is used for provisioning of PFDs from the SCEF to the PFDF and reporting the result of the PFD Management from the PFDF to the SCEF.
+
+The stage 2 level requirements for the Nu reference point are defined in 3GPP TS 23.682 [2].
+
+## 4.2 Nu reference model
+
+The Nu reference point is defined between the SCEF and the PFDF. The relationships between the different functional entities involved are depicted in figure 4.2.1. The overall PCC architecture is depicted in clause 3a of 3GPP TS 29.213 [4].
+
+![Diagram of the Nu reference model showing the PFDF and SCEF connected via the Nu reference point.](ba9d6e1a75eb6672d04e61a86e1b8a61_img.jpg)
+
+The diagram illustrates the Nu reference model. It consists of two light green rectangular boxes, labeled 'PFDF' on the left and 'SCEF' on the right. A horizontal line connects the two boxes. Above this line, centered between the boxes, is the label 'Nu'. A small vertical tick mark is positioned on the horizontal line directly below the 'Nu' label.
+
+Diagram of the Nu reference model showing the PFDF and SCEF connected via the Nu reference point.
+
+Figure 4.2.1: Nu reference model
+
+## 4.3 Functional elements
+
+### 4.3.1 PFDF
+
+The PFDF (Packet Flow Description Function) is a functional element which receives and manages the PFDs associated to application identifier (s) from the SCEF via the Nu reference point.
+
+The PFDF provisions PFDs for the corresponding application identifier (s) to the PCEF/TDF as defined in 3GPP TS 23.203 [3] and 3GPP TS 29.251 [9].
+
+### 4.3.2 SCEF
+
+The SCEF (Service Capability Exposure Function) is a functional element which provides means to securely expose the services and capabilities provided by the 3GPP network interfaces.
+
+The SCEF shall support the management of PFDs provided by the 3<sup>rd</sup> party SCS/AS. The SCEF may provision the PFDs to the PFDF via the Nu reference point.
+
+## 4.4 Procedures over Nu reference point
+
+### 4.4.1 Management of PFD
+
+The PFDs associated with application identifier (s) may be created, updated or removed in the PFDF by the third party SCS/AS via the SCEF as defined in 3GPP TS 23.682 [2].
+
+If the SCEF receives one or more sets of PFDs for external application identifier (s) provisioned by the third party SCS/AS, which is authorized to perform the management of PFDs based on operator policies, the SCEF shall:
+
+- If the external application identifier(s) is different from the application identifier(s) known at the PFDF, translate the external application identifier(s) to the application identifier(s) known at the PFDF; and
+- may check if the allowed delay satisfies the required SLA against the minimum allowed delay as defined in 3GPP TS 23.682 [2]; and
+- send an HTTP POST message to the PFDF including the provisioned PFD changes for the the application identifier (s) within the body of the HTTP POST as described in clause 5.3.5.2.
+
+NOTE 1: It is up to operator configuration whether to use different external application identifiers that require a mapping to application identifiers known at the PFDF. The external application identifier can be the same as the application identifier known at the PFDF.
+
+Upon receipt of the HTTP request for the provisioning operation from the SCEF, the PFDF shall perform the following steps:
+
+- If an allowed delay is received for an application identifier, for Pull mode as defined in 3GPP TS 29.251 [9], the PFDF shall compare the allowed delay with the configured caching time which is:
+  - a caching time value configured for that application identifier; or
+  - the default caching time value if no caching time value is configured for that application identifier.
+- Then if the PFDF cannot ensure the PCEF/TDF will pull the PFDs in time (i.e. allowed delay is shorter than the caching time), the PFDF shall within the HTTP response send a failure reason and that caching time value used in the comparison and may still store (create/update/remove) the PFDs for this application identifier.
+
+NOTE 2: In the Combination mode as defined in 3GPP TS 29.251 [9], the PFDF can check the received allowed delay against the caching time but will always store (create/update/remove) the PFDs.
+
+- In the Pull mode as defined in 3GPP TS 29.251 [9], for the application identifier(s) without the need to send failure reason; or in the Push or Combination mode as defined in 3GPP TS 29.251 [9], for received application identifier(s), the PFDF shall:
+
+- delete all the PFD(s) for the application identifier(s) where the removal-flag is also provided and set to true;
+- update the existing PFD(s) if a new PFD(s) with the same PFD identifier(s) is received , add new PFD(s) if the new PFD(s) with a new PFD identifier(s) is received, and/or delete an existing PFD(s) if the same PFD identifier(s) without any content is received, where the partial-flag is also provided and set to true;
+- remove existing PFD(s) (if available) and install the new PFD(s) for the corresponding PFD identifier(s) where no flag is provided;
+- acknowledge the HTTP POST message by sending a corresponding HTTP response with the appropriate status code as defined in clause 5.3.2. If the POST operation was successful for at least one application identifier, the PFDF shall respond with an HTTP 200 OK status code.
+
+### 4.4.2 PFD management notification
+
+In the Push mode or Combination mode as defined in 3GPP TS 29.251 [9], if the PFDs are provisioned to at least one of the known PCEFs/TDFs (but not all) within the allowed delay (i.e. the provisioned PFDs can not be enforced successfully in some PCEF/TDFs known on the PFDF), the PFDF may notify the SCEF about the failed PFD provisioning with the HTTP POST message using the failure reason "PARTIAL\_FAILURE" as defined in Table 5.4.7.1-1. In this case, the PFDF may include location area(s) of the PCEF/TDF(s) which can not enforce the provisioned PFD(s) within the field "user-plane-location-area" of the corresponding instance of the PFD report(s). If the PFDs are provisioned to none of the known PCEFs/TDFs within the allowed delay, the PFDF shall notify the SCEF about the failed PFD provisioning with the HTTP POST message using appropriate failure reason as defined in clause 6.4.6.3 of 3GPP TS 29.251 [9].
+
+When receiving the HTTP POST message, the SCEF shall respond with an HTTP response message.
+
+# --- 5 Nu protocol
+
+## 5.1 Introduction
+
+The following layers of the protocol stack for the Nu reference point between the SCEF and the PFDF are described in clauses:
+
+- IETF RFC 793 [7] provides the communication service at the transport layer.
+- An optional communication security layer can be added between the transport and the application delivery layer (see clause 6).
+- The application delivery layer provides the transport of the specific application communication data using IETF RFC 7230 [13], IETF RFC 7231 [14], IETF RFC 7232 [15], IETF RFC 7233 [16], IETF RFC 7234 [17] and IETF RFC 7235 [18].
+- The specific application communication layer constitutes the transport of the JSON content type.
+
+Figure 5.1.1 illustrates the protocol stack of the RESTful Nu reference point.
+
+![Figure 5.1.1: Protocol stack of the RESTful Nu reference point. The diagram shows two protocol stacks, SCEF and PFDF, connected by a REST-Nu interface. The SCEF stack has layers: JSON (Specific application communication), HTTP (Application delivery), TCP (Transport layer), IP (Network layer), L2 (Data link layer), and L1 (Physical layer). The PFDF stack has the same layers: JSON, HTTP, TCP, IP, L2, and L1. The REST-Nu interface is shown as a vertical line between the two stacks.](e6df2733626a85205c1db682e6259c46_img.jpg)
+
+|                                    |      |         |      |
+|------------------------------------|------|---------|------|
+| Specific application communication | JSON |         | JSON |
+| Application delivery               | HTTP |         | HTTP |
+| Transport layer                    | TCP  |         | TCP  |
+| Network layer                      | IP   |         | IP   |
+| Data link layer                    | L2   |         | L2   |
+| Physical layer                     | L1   |         | L1   |
+|                                    | SCEF | REST-Nu | PFDF |
+
+Figure 5.1.1: Protocol stack of the RESTful Nu reference point. The diagram shows two protocol stacks, SCEF and PFDF, connected by a REST-Nu interface. The SCEF stack has layers: JSON (Specific application communication), HTTP (Application delivery), TCP (Transport layer), IP (Network layer), L2 (Data link layer), and L1 (Physical layer). The PFDF stack has the same layers: JSON, HTTP, TCP, IP, L2, and L1. The REST-Nu interface is shown as a vertical line between the two stacks.
+
+**Figure 5.1.1: Protocol stack of the RESTful Nu reference point**
+
+## 5.2 Transport layer
+
+HTTP is layered over TCP, which provides a reliable transport.
+
+For provisioning of PFDs from the SCEF to the PFDF, the SCEF acts as an HTTP client and the PFDF acts as an HTTP server. As a result, the SCEF shall initiate a TCP connection with the PFDF.
+
+## 5.3 Application delivery layer
+
+### 5.3.1 General
+
+The application delivery layer shall use RESTful HTTP.
+
+The application delivery layer provides provisioning of the PFDs by the SCEF.
+
+If the SCEF needs to provision PFDs for a set of application identifier(s) (creation/update/deletion) to the PFDF, the SCEF shall send an HTTP POST message.
+
+### 5.3.2 HTTP status codes
+
+The HTTP status codes for the REST-based Nu interface are specified in the IETF RFC 7231 [14].
+
+### 5.3.3 Methods
+
+Methods indicate to the server what action has to be performed. Every HTTP request message has a method.
+
+The HTTP POST method is used by the SCEF to provision PFDs for a set of application identifiers. The request URI defines the address responsible for the management of the PFDs provisioning as a controller resource.
+
+The HTTP POST method is also used by the PFDF to inform the SCEF for PFD management notification.
+
+Every HTTP request results in a response message that comes back with a status code and further information in its body, if required. The HTTP request initiator waits for this response before initiating a further request.
+
+### 5.3.4 Resources and URI design
+
+The URI design shall be based on the structure defined in IETF RFC 3986 [10]:
+
+```
+scheme ":" hier-part [ "?" query ] [ "#" fragment ]  
+hier-part = "//" authority path-abempty  
+/ path-absolute  
+/ path-rootless  
+/ path-empty
+```
+
+The scheme may be HTTP or HTTPS for the Nu interface. Within a scheme the definition of names shall follow the rules of HTTP URIs. Host and port are the main parts of the authority. The path element identifies the resources.
+
+For the Nu interface, the following required parts of the URI shall be used as follows:
+
+scheme: The application delivery layer protocol "http" or "https".
+
+authority: It includes the server address and optionally a port as follows: host [":" port]
+
+path-absolute: The path-absolute should have the following ABNF: "/" mainapp "/" mainresource. In this release:
+
+"mainapp" is "nuapplication".
+
+"mainresource" is "provisioning".
+
+The PFDs management (associating/disassociating PFDs with application identifiers) in PFDF is a controller resource that is responsible for processing requests that provisioning a set of changes for more than one set of PFDs for corresponding application identifiers atomically.
+
+An example of the URI to identify the controller resource is <http://pfdserver.example.com/nuapplication/provisioning>.
+
+NOTE: A different path can be used when the Resource URI is preconfigured in the SCEF.
+
+### 5.3.5 HTTP request/response formats
+
+#### 5.3.5.1 General
+
+The PFDs provisioning procedure is performed through HTTP transactions consisting of a request initiated by the SCEF and answered by the PFDF.
+
+Table 5.3.5.1-1 summarizes the content of the requests and responses. More detailed information is specified in the corresponding clauses as indicated in the table.
+
+**Table 5.3.5.1-1: Nu requests/response summary table**
+
+| Method | Resource URI's path                                                   | Clause Defined | Request body                                                                                                                                         | Initiator | Response body                                                                                        |
+|--------|-----------------------------------------------------------------------|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|------------------------------------------------------------------------------------------------------|
+| POST   | /nuapplication/provisioning (NOTE 1)                                  | 5.3.5.2        | Content-Type: application/json<br>The SCEF shall include PFDs content associated with application identifier(s) using the schema defined in Annex A. | SCEF      | Successful response: The PFDF may include informational data in the body of the response in Annex A. |
+| POST   | {sceF-notification-uri}<br>or<br>/nuapplication/notification (NOTE 2) | 5.3.5.3        | Content-Type: application/json<br>The PFDF shall include notification result and application identifier(s) using the schema defined in Annex A.      | PFDF      |                                                                                                      |
+
+NOTE 1: A different path from /nuapplication/provisioning may be used when it is configured in the SCEF. In that case the "path" part set in the different methods should use the configured one.
+
+NOTE 2: A different path from /nuapplication/notification may be used when it is configured in the PFDF and no sceF-notification-uri is received in the provisioning POST. In that case the "path" part set in the different methods should use the configured one.
+
+#### 5.3.5.2 POST /nuapplication/provisioning
+
+The provisioning of the PFDs shall be performed by the SCEF by using the POST method as follows:
+
+- The request URI formatted as defined in clause 5.3.4 with the "path" part set to: /nuapplication/provisioning.
+- The Content-Type header field set to "application/json"
+- The body of the message encoded in JSON format as defined in Annex A. The body shall include
+  - for the PFD(s) creation for a new application identifier, a new application identifier and its full list of PFD(s) to be created;
+  - for the PFD(s) full update for an existing application identifier, the existing application identifier and its new full list of PFD(s)
+  - for the PFD(s) partial update for an existing application identifier, the existing application identifier, partial update indication and
+    - new PFD(s) with new PFD identifier(s) to add new PFD(s),
+    - new PFD(s) with existing PFD identifier(s) to update existing PFD(s), and/or
+    - the existing PFD identifier(s) without any content to remove the existing PFD(s);
+  - for the PFD(s) removal for an existing application identifier, the existing application identifier and the removal indication.
+
+Upon receipt of the HTTP POST request, the PFDF shall respond to the SCEF indicating whether the provisioning was successful or not using one of the HTTP status codes as defined in clause 5.3.2. If the provisioning was accepted, the PFDF shall respond with an HTTP 200 OK status code if no resource is created, or an HTTP 201 Created status code if one or more resources are created. If the allowed delay is too short according to the criteria in clause 4.4.1, the PFDF shall respond with an HTTP 200 OK status code and additional information in the body of the response indicating failure reason "too short allowed delay" and the value of caching time as defined in Annex A. If the provisioning was rejected, the PFDF shall indicate the reason using an appropriate HTTP status code as defined in clause 5.3.2 and optionally additional information in the body of the response as defined in Annex A.
+
+Below is an example of an HTTP POST and a corresponding successful response:
+
+POST /nuapplication/provisioning HTTP/1.1  
+Host: pfdserver.example.com  
+Content-Type: application/json  
+Content-Length: ...
+
+```
+[  
+  {  
+    "application-identifier":"test-application-1",  
+    "removal-flag":true  
+  },  
+  {  
+    "application-identifier":"test-application-2",  
+    "allowed-delay":600,  
+    "pfds":[  
+      {  
+        "pfd-identifier":"pfd1",  
+        "flow-descriptions":[  
+          "permit in ip from 10.68.28.39 80 to any"  
+        ]  
+      },  
+      {  
+        "pfd-identifier":"pfd2",  
+        "urls":[  
+          "^http://test.example.com(/\\S*)?$"  
+        ]  
+      }  
+    ]  
+  },  
+  {  
+    "application-identifier":"test-application-3",  
+    "partial-flag":true,  
+    "pfds":[  
+      {  
+        "pfd-identifier":"pfd3",  
+        "urls":[  
+          "^http://test.example2.net(/\\S*)?$"  
+        ]  
+      }  
+    ]  
+  }  
+]
+```
+
+```
+    ]  
+  },  
+  {  
+    "pfd-identifier":"pfd4"  
+  }  
+]  
+}  
+]
+```
+
+Here is an example of a successful response:
+
+HTTP/1.1 200 OK
+
+Date: Mon, 7 May 2012 16:00:00 GMT
+
+Server: pfdserver.example.com
+
+Content-Type: application/json
+
+```
+{  
+  "success-message": "Notification was processed successfully.",  
+}
+```
+
+#### 5.3.5.3 POST /nuapplication/notification
+
+The notification of the PFD management shall be performed by the PFDF by using the POST method as follows:
+
+- The request URI formatted as defined in clause 5.3.4 with the "path" part set to: /nuapplication/notification.
+- The Content-Type header field set to "application/json".
+- The body of the message encoded in JSON format as defined in Annex A. The body shall include the pfd-report.
+
+Upon receipt of the HTTP POST request, the SCEF shall respond to the PFDF with HTTP 200 OK status code.
+
+Below is an example of an HTTP POST and a corresponding response:
+
+POST /nuapplication/notification HTTP/1.1
+
+Host: scefservers.example.com
+
+Content-Type: application/json
+
+Content-Length: ...
+
+```
+{  
+  "notification-pfd-reports": [  
+    {  
+      "application-ids": ["test-application-1", "test-application-2", "test-application-3"],  
+      "pfd-failure-code": "PARTIAL_FAILURE",  
+      "user-plane-location-area": {  
+        "cell-ids" : ["46000045BD6007", "46000045BD6008"],  
+      }  
+    }  
+  ]  
+}
+```
+
+```
+        "tracking-area-ids" : ["46000063F8", "46000063F9"]  
+    }  
+}  
+]  
+}
+```
+
+Here is an example of a response:
+
+HTTP/1.1 200 OK
+
+Date: Mon, 7 May 2018 16:00:00 GMT
+
+Server: scefservers.example.com
+
+Content-Type: application/json
+
+### 5.3.6 Feature negotiation
+
+#### 5.3.6.1 General
+
+The REST based Nu interface needs to provide a mechanism to advertise required and optional features supported by both the SCEF and PFDF for interoperability reasons as the functionality of the REST Nu based interface is augmented.
+
+Feature negotiation shall take place during the first interaction (i.e. HTTP POST in provisioning) between the PFDF and the SCEF. The client shall include in the HTTP request the set of supported features as follows:
+
+- if a feature is required for the proper operation of the application, it shall be included within the 3gpp-Required-Features header;
+- if a feature is optional for the proper operation of the application, it shall be included within the 3gpp-Optional-Features header.
+
+The server shall include, within the 3gpp-Accepted-Features header in the HTTP response, the set of features it supports in common with the client.
+
+If the server does not support any of the required features advertised by the client within the 3gpp-Required-Features header, the server shall reject the HTTP request with an HTTP 412 Precondition Failed status code and shall include the commonly supported features with the client within the 3gpp-Accepted-Features.
+
+If the server requires certain features to be supported that are not advertised by the client, the server shall reject the HTTP request with an HTTP 412 Precondition Failed status code and shall include the commonly supported features with the client within the 3gpp-Accepted-Features and the required features in the 3gpp-required-features.
+
+If the SCEF and the PFDF successfully negotiate supported features, the list of commonly supported features shall be applicable for the lifetime of the application. Features that are not advertised as supported shall not be used.
+
+The sender may send information that is related to the supported features. Any unrecognized information shall be ignored by the receiver.
+
+The table below defines the features applicable to the Nu interface.
+
+**Table 5.3.6.1-1: Features used in Nu Interface**
+
+| Feature                                                                                                                 | M/O | Description                                                                                       |
+|-------------------------------------------------------------------------------------------------------------------------|-----|---------------------------------------------------------------------------------------------------|
+| DomainNameProtocol                                                                                                      | O   | This feature supports the additional protocol matching condition for the domain name in PFD data. |
+| PfdMgmtNotification                                                                                                     | O   | This feature supports the PFD management notification.                                            |
+| Feature: A short name for the feature to which the M/O and description pertain.                                         |     |                                                                                                   |
+| M/O: Indication on whether the implementation of the feature is mandatory ("M") or optional ("O") in this 3GPP Release. |     |                                                                                                   |
+| Description: Textual description of the feature.                                                                        |     |                                                                                                   |
+
+NOTE: The base functionality for the Nu interface is defined in the Release-14 version of this specification and a feature is an extension of that functionality. The negotiation of supported features allows interworking between the endpoints of the Nu interface whereby each entity may support all, some, or none of the features that the Nu application can support defined in this specification. Features are defined so that they are independent of each other. Any introduced feature is explicitly defined in this specification.
+
+Since a post Release-16 version of SCEF does not send any supported feature information, the interworking PFDF supporting Release-16 version does not need to send any information related to supported feature and both sides shall behave as specified in the Release-14 version of this specification.
+
+A post Release-16 version of PFDF may receive supported feature information from a Release-16 version of SCEF, those information will be ignored by the PFDF and both sides shall behave as specified in the Release-14 version of this specification.
+
+#### 5.3.6.2 HTTP custom headers
+
+This clause defines any new HTTP custom headers introduced by this specification.
+
+##### 5.3.6.2.1 3gpp-Optional-Features
+
+This header is used by the client to advertise the optional features that are supported by the client.
+
+The encoding of the header follows the ABNF as defined in IETF RFC 7230 [13].
+
+`3gpp-Optional-Features = "3gpp-Optional-Features" ":" 1#token`
+
+An example is: `3gpp-Optional-Features: feature1, feature2`
+
+##### 5.3.6.2.2 3gpp-Required-Features
+
+This header is used by the client to announce the mandatory features that must be supported in the server.
+
+This header is also used by the server to indicate the missing features that must be supported in the client.
+
+The encoding of the header follows the ABNF as defined in IETF RFC 7230 [13].
+
+`3gpp-Required-Features = "3gpp-Required-Features" ":" 1#token`
+
+An example is: `3gpp-Required-Features: feature1, feature2`
+
+##### 5.3.6.2.3 3gpp-Accepted-Features
+
+The header is used by the server to confirm the commonly supported set of features with the client.
+
+The encoding of the header follows the ABNF as defined in IETF RFC 7230 [13].
+
+`3gpp-Accepted-Features = "3gpp-Accepted-Features" ":" 1#token`
+
+An example is: `3gpp-Accepted-Features: feature1, feature2`
+
+## 5.4 Specific application communication
+
+### 5.4.1 General
+
+Specific application communication represents the presentation of application data structures by transforming data into the form that the application accepts. It establishes the context between application-layer entities.
+
+NOTE: This release only supports the content type JSON.
+
+### 5.4.2 Content type
+
+The body of HTTP messages shall be in JSON format. The content of the JSON text is defined in clause 5.4.3 and Annex A.
+
+The MIME media type that shall be used within the Content-Type header field is "application/json" as defined in IETF RFC 7159 [11].
+
+### 5.4.3 JSON provisioning fields
+
+#### 5.4.3.1 General
+
+Table 5.4.3.1-1 describes the JSON provisioning fields used within the body of the HTTP messages representing the PFDs information associated with an application identifier. The table includes the information about the name of the field and the type of the fields.
+
+**Table 5.4.3.1-1: Nu Provisioning JSON fields**
+
+| Field Name             | Clause defined     | JSON Value Type<br>(NOTE 1) | JCR Type<br>(NOTE 2) | Applicability<br>(NOTE 4) |
+|------------------------|--------------------|-----------------------------|----------------------|---------------------------|
+| application-identifier | 3GPP TS 29.251 [9] | string                      | string               |                           |
+| allowed-delay          | 3GPP TS 29.251 [9] | number                      | uint64               |                           |
+| pfdids                 | 3GPP TS 29.251 [9] | array                       | array                |                           |
+| pfd-identifier         | 3GPP TS 29.251 [9] | string                      | string               |                           |
+| flow-descriptions      | 3GPP TS 29.251 [9] | array                       | array                |                           |
+| urls                   | 3GPP TS 29.251 [9] | array                       | array                |                           |
+| domain-names           | 3GPP TS 29.251 [9] | array                       | array                |                           |
+| removal-flag (NOTE 3)  | 3GPP TS 29.251 [9] | boolean                     | boolean              |                           |
+| partial-flag (NOTE 3)  | 3GPP TS 29.251 [9] | boolean                     | boolean              |                           |
+| dn-protocol            | 3GPP TS 29.251 [9] | string                      | string               | DomainNameProtocol        |
+| scef-notification-uri  | 5.4.3.2            | string                      | string               | PfdMgmtNotification       |
+
+NOTE 1: The basic JSON value types are defined in IETF RFC 7159 [11].  
+NOTE 2: The JCR types are defined in IETF draft-newton-json-content-rules [12].  
+NOTE 3: Only one of the removal-flag and the partial-flag for the application identifier shall be set to true.  
+NOTE 4: Fields marked with a supported feature are applicable as described in clause 5.3.6.
+
+#### 5.4.3.2 scef-notification-uri
+
+The scef-notification-uri is of type string indicating the SCEF sent URI for receiving notifications.
+
+### 5.4.4 Void
+
+### 5.4.5 JSON errors and informational response fields
+
+#### 5.4.5.1 General
+
+Table 5.4.4.1-1 describes the JSON fields defined for the errors and informational responses including their types and the field names.
+
+**Table 5.4.5.1-1: JSON fields for errors and informational response**
+
+| Field Name                                                                                  | Clause defined              | JSON Value Type (NOTE 1) | JCR Type (NOTE 2)                                               | Applicability (NOTE 5) |
+|---------------------------------------------------------------------------------------------|-----------------------------|--------------------------|-----------------------------------------------------------------|------------------------|
+| errors                                                                                      | 3GPP TS 29.251 [9] (NOTE 4) | array                    | array                                                           |                        |
+| error-type                                                                                  | 3GPP TS 29.251 [9] (NOTE 4) | string                   | "application"<br>"interface"<br>"server"<br>"other"<br>(NOTE 3) |                        |
+| error-message                                                                               | 3GPP TS 29.251 [9]          | string                   | string                                                          |                        |
+| error-tag                                                                                   | 3GPP TS 29.251 [9]          | string                   | string                                                          |                        |
+| error-path                                                                                  | 3GPP TS 29.251 [9]          | string                   | string                                                          |                        |
+| error-info                                                                                  | 3GPP TS 29.251 [9]          | object                   | object                                                          |                        |
+| success-message                                                                             | 3GPP TS 29.251 [9]          | string                   | string                                                          |                        |
+| success-path                                                                                | 3GPP TS 29.251 [9]          | string                   | string                                                          |                        |
+| success-info                                                                                | 3GPP TS 29.251 [9]          | object                   | object                                                          |                        |
+| NOTE 1: The basic JSON value types are defined in IETF RFC 7159 [11].                       |                             |                          |                                                                 |                        |
+| NOTE 2: The JCR types are defined in IETF draft-newton-json-content-rules [12].             |                             |                          |                                                                 |                        |
+| NOTE 3: The quoted strings for a string type.                                               |                             |                          |                                                                 |                        |
+| NOTE 4: The error is sent from the PFDF to the SCEF.                                        |                             |                          |                                                                 |                        |
+| NOTE 5: Fields marked with a supported feature are applicable as described in clause 5.3.6. |                             |                          |                                                                 |                        |
+
+### 5.4.6 JSON report fields
+
+#### 5.4.6.1 General
+
+Table 5.4.6.1-1 describes the JSON fields defined for the report information objects which are included in the error-info field.
+
+**Table 5.4.6.1-1: JSON fields for Report from the PFDF**
+
+| Field Name                                                                                  | Clause defined              | JSON Value Type (NOTE 1) | JCR Type (NOTE 2) | Applicability (NOTE 4) |
+|---------------------------------------------------------------------------------------------|-----------------------------|--------------------------|-------------------|------------------------|
+| pfd-reports                                                                                 | 5.4.6.2                     | array                    | array             |                        |
+| application-ids                                                                             | 5.4.6.3                     | array                    | array             |                        |
+| pfd-failure-code                                                                            | 3GPP TS 29.251 [9] (NOTE 3) | string                   | string            |                        |
+| caching-time                                                                                | 3GPP TS 29.251 [9]          | number                   | uint64            |                        |
+| NOTE 1: The basic JSON value types are defined in IETF RFC 7159 [11].                       |                             |                          |                   |                        |
+| NOTE 2: The JCR types are defined in IETF draft-newton-json-content-rules [12].             |                             |                          |                   |                        |
+| NOTE 3: The additional failure reasons for Nu are "TOO_SHORT_ALLOWED_DELAY".                |                             |                          |                   |                        |
+| NOTE 4: Fields marked with a supported feature are applicable as described in clause 5.3.6. |                             |                          |                   |                        |
+
+#### 5.4.6.2 pfd-reports
+
+The pfd-reports field is of type array and it contains a list of pfd reports.
+
+The pfd-reports field can be used in an HTTP response to report failures in the installation/modification of PFDs. In this case, it shall be provided as a sub field of the error-info field.
+
+Multiple pfd report instances shall be provided within the pfd-reports field if different pfd-failure-code values are applicable within the same HTTP response.
+
+caching-time field is included if the pfd-failure-code is set to the value "TOO\_SHORT\_ALLOWED\_DELAY".
+
+A report instance shall contain application-ids and pfd-failure-code fields.
+
+The JCR format for the pfd-reports is:
+
+```
+$pfd-reports = "pfd-reports" : [
+  { $application-ids,
+    $pfd-failure-code,
+    $caching-time,
+  } +
+]
+```
+
+#### 5.4.6.3 application-ids
+
+The application-ids field is of type array of string, and contains one or more application identifiers to which the PFDs belong.
+
+### 5.4.7 JSON notification fields
+
+#### 5.4.7.1 General
+
+Table 5.4.7.1-1 describes the JSON notification fields used within the body of the HTTP messages. The table includes the information about the name of the field and the type of the fields.
+
+**Table 5.4.7.1-1: Nu Notification JSON fields**
+
+| Field Name               | Clause defined                  | JSON Value Type<br>(NOTE 1) | JCR Type<br>(NOTE 2) | Applicability<br>(NOTE 3) |
+|--------------------------|---------------------------------|-----------------------------|----------------------|---------------------------|
+| notification-pfd-reports | 5.4.7.2                         | array                       | array                | PfdMgmtNotification       |
+| application-ids          | 5.4.6.3                         | array                       | array                | PfdMgmtNotification       |
+| pfd-failure-code         | 3GPP TS 29.251 [9] (<br>NOTE 4) | string                      | string               | PfdMgmtNotification       |
+| user-plane-location-area | 5.4.7.3                         | object                      | object               | PfdMgmtNotification       |
+| cell-ids                 | 5.4.7.4                         | array                       | array                | PfdMgmtNotification       |
+| enodeb-ids               | 5.4.7.5                         | array                       | array                | PfdMgmtNotification       |
+| extended-enodeb-ids      | 5.4.7.6                         | array                       | array                | PfdMgmtNotification       |
+| routing-area-ids         | 5.4.7.7                         | array                       | array                | PfdMgmtNotification       |
+| tracking-area-ids        | 5.4.7.8                         | array                       | array                | PfdMgmtNotification       |
+
+NOTE 1: The basic JSON value types are defined in IETF RFC 7159 [11].  
+NOTE 2: The JCR types are defined in IETF draft-newton-json-content-rules [12].  
+NOTE 3: Fields marked with a supported feature are applicable as described in clause 5.3.6.  
+NOTE 4: The additional failure reasons for Nu are "PARTIAL\_FAILURE".
+
+#### 5.4.7.2 notification-pfd-reports
+
+The notification-pfd-reports field is of type array and it contains a list of pfd reports.
+
+The notification-pfd-reports field can be used in an HTTP POST to notify the failures in the installation/modification of PFDs. In this case, it shall be included in the body of the message.
+
+Multiple pfd report instances shall be provided within the notification-pfd-reports field if different pfd-failure-code values are applicable within the same HTTP response.
+
+user-plane-location-area field is included if the pfd-failure-code is set to the value "PARTIAL\_FAILURE".
+
+A report instance shall contain application-ids and pfd-failure-code fields.
+
+The JCR format for the notification-pfd-reports is:
+
+```
+$notification-pfd-reports = "notification-pfd-reports" : [  
+  { $application-ids,  
+    $pfd-failure-code,  
+    $user-plane-location-area ?  
+  } +  
+]
+```
+
+#### 5.4.7.3 user-plane-location-area
+
+The user-plane-location-areas field is of type object and it contains location areas of the user plane(s) which can not enforce the PFD(s) successfully.
+
+The JCR format for the user-plane-location-area is:
+
+```
+$user-plane-location-area = // : {  
+  $cell-ids ?,  
+  $enodeb-ids ?,  
+  $extended-enodeb-ids ?,  
+  $routing-area-ids ?,  
+  $tracking-area-id ?  
+}
+```
+
+#### 5.4.7.4 cell-ids
+
+The cell-ids is of type string array and it contains a list of Cell Global Identities served by the user plane(s) which can not enforce the PFD(s) successfully. The content of the string has the same encoding as defined in clause 8.21.1 of 3GPP TS 29.274 [19].
+
+#### 5.4.7.5 enodeb-ids
+
+The enodeb-ids is of type string array and it contains a list of eNodeB identities served by the user plane(s) which can not enforce the PFD(s) successfully. The content of the string has the same encoding as defined in clause 8.21.7 of 3GPP TS 29.274 [19].
+
+#### 5.4.7.6 extended-enodeb-ids
+
+The enodeb-ids is of type string array and it contains a list of eNodeB identities served by the user plane(s) which can not enforce the PFD(s) successfully. The content of the string has the same encoding as defined in clause 8.21.8 of 3GPP TS 29.274 [19].
+
+#### 5.4.7.7 routing-area-ids
+
+The routing-area-ids is of type string array and it contains a list of Routing Area Identities served by the user plane(s) which can not enforce the PFD(s) successfully. The content of the string has the same encoding as defined in clause 8.21.3 of 3GPP TS 29.274 [19].
+
+#### 5.4.7.8 tracking-area-ids
+
+The tracking-area-ids is of type string array and it contains a list of Tracking Area Identities served by the user plane(s) which can not enforce the PFD(s) successfully. The content of the string has the same encoding as defined in clause 8.21.4 of 3GPP TS 29.274 [19].
+
+## 5.5 PFDF discovery
+
+The PFDF URI may be pre-configured on the SCEF.
+
+The SCEF may select the PFDF by this configuration.
+
+## 5.6 SCEF discovery
+
+The SCEF notification URI may be pre-configured on the PFDF.
+
+The SCEF notification URI may also be sent to the PFDF in the PFD provisioning.
+
+The PFDF may select the SCEF by the pre-configuration or use the notification URI received in the PFD provisioning.
+
+# --- 6 Secure communication
+
+Either the NDS/IP network layer security defined in 3GPP TS 33.210 [5] or HTTP over TLS as defined in IETF RFC 2818 [6] should be used to secure communication over the REST based Nu interface.
+
+# --- Annex A (informative): JSON Schema
+
+## A.1 Provisioning schema
+
+This clause defines the JSON schema for the body of HTTP request providing the provisioned PFDs. The schema is based on IETF draft-newton-json-content-rules [12] and is defined below:
+
+```
+# jcr-version 0.7
+```
+
+```
+# ruleset-id 3gpp.nuapplication.provisioning
+```
+
+```
+# import 3gpp.gwapplication.pfds as pfds
+```
+
+```
+; JCR representing the PFDs provisioning data
+```
+
+```
+$provisioning-root = @{root} {
+```
+
+```
+  $application-identifier,
+```
+
+```
+  $removal-flag ?,
+```
+
+```
+  $partial-flag ?,
+```
+
+```
+  $allowed-delay ?,
+```
+
+```
+  $pfds ?,
+```
+
+```
+  $scefn-notification-uri ?
+```
+
+```
+}  
+  
+; An array list of the PFDs for multiple application identifiers  
+$pfd-array-root = @{root} [ $provisioning-root * ]  
+  
+; The detected application traffic identifier for the PFDs  
+$application-identifier = "application-identifier" : string  
+  
+; The allowed delay time for the PFDs deployment  
+$allowed-delay = "allowed-delay" : uint64  
+  
+; The PFDs associated with the same application identifier  
+$pfd = "pfd" : [ $pfd * ]  
+; The PFD content  
+$pfd = {  
+    $pfd-identifier,  
+    ( $flow-descriptions | $urls | $domain-names | // : any ) ?,  
+    $pfd.dn-protocol ?  
+}  
+  
+; The PFD identifier  
+$pfd-identifier = "pfd-identifier" : string  
+  
+; The flow descriptions  
+$flow-descriptions = "flow-descriptions" : [ string + ]  
+  
+; The url matching expressions  
+$urls = "urls" : [ string + ]  
+  
+; The domain name match criteria  
+$domain-names = "domain-names" : [ string + ]  
+  
+; A flag indicates whether this is a removal or not  
+$removal-flag = "removal-flag" : boolean
+```
+
+; A flag indicates whether this is a partial update or not  
+\$partial-flag = "partial-flag" : boolean
+
+; The URI in the SCEF for receiving notifications from the PFDF  
+\$sceff-notification-uri = "sceff-notification-uri" : string
+
+## --- A.2 Error and Informational response schema
+
+This clause defines the JSON schema for the body of HTTP responses in case of errors or success. The schema is based on IETF draft-newton-json-content-rules [12] and is defined below:
+
+# jcr-version 0.7
+
+# ruleset-id 3gpp.nuapplication.info
+
+; A JCR for the error/successful response body
+
+; Errors information
+
+\$errors-root = @{root} { \$errors }
+
+; Success information
+
+```
+$success-root = @{root} {  
+    $success-message,  
+    $success-path ?,  
+    $success-info ?  
+}
+```
+
+; Resource fields definitions
+
+; The list of errors returned in responses sent by the PCEF/TDF
+
+```
+$errors = "errors" : [  
+{  
+    $error-type,  
+    $error-message,  
+    $error-tag ?,  
+    $error-path ?,  
+    $error-info ?  
+} +  
+]
+```
+
+; The error type for an error. It can be one of 'application', 'interface', 'server' and 'other'.
+
+\$error-type = "error-type" : ( "application" | "interface" | "server" | "other" )
+
+; The error text message
+
+\$error-message = "error-message" : string
+
+; The error tag for a specific error
+
+\$error-tag = "error-tag" : string
+
+; A JSON pointer path to the error resource
+
+\$error-path = "error-path" : string
+
+; Any additional information for the error
+
+\$error-info = "error-info" : {
+
+\$pfd-reports ?,
+
+// : any \*
+
+}
+
+; Report fields definitions
+
+; The list of pfd reports sent to the SCEF
+
+\$pfd-reports = "pfd-reports" : [
+
+{
+
+\$application-ids,
+
+\$pfd-failure-code,
+
+\$caching-time
+
+} +
+
+]
+
+; The application identifiers for the PFDs
+
+\$application-ids = "application-ids" : [string+]
+
+; The string format for the pfd failure code
+
+\$pfd-failure-code =: (
+
+"MALFUNCTION" |
+
+"RESOURCES\_LIMITATION" |
+
+"TOO\_SHORT\_ALLOWED\_DELAY" |
+
+```
+"PARTIAL_FAILURE" |  
+"OTHER_REASON"  
+)  
+  
+; The caching time for the PFDs  
+$caching-time = "caching-time" : uint64  
+  
+; The successful text message  
+$success-message = "success-message" : string  
+  
+; A JSON pointer path to the success resource  
+$success-path = "success-path" : string  
+  
+; Any additional information for the success.  
+$success-info = "success-info" : { // : any * }
+```
+
+## --- A.3 PFD management notification schema
+
+This clause defines the JSON schema for the body of HTTP request providing the notification of PFD management. The schema is based on IETF draft-newton-json-content-rules [12] and is defined below:
+
+```
+# jcr-version 0.7  
+  
+# ruleset-id 3gpp.nuapplication.notification  
+  
+; A JCR for the notification body  
+$notification-root = @{root} {  
+    $notification-pfd-reports  
+}  
+  
+; Report fields definitions  
+  
+; The list of pfd reports sent to the SCEF  
+$notification-pfd-reports = "notification- pfd-reports" : [  
+{  
+    $application-ids,  
+    $pfd-failure-code,  
+    $user-plane-location-area ?  
+} +  
+]
+```
+
+; The application identifiers for the PFDs
+
+\$application-ids = "application-ids" : [string+]
+
+; The string format for the pfd failure code
+
+\$pfd-failure-code =: (  
+"MALFUNCTION" |  
+"RESOURCES\_LIMITATION" |  
+"PARTIAL\_FAILURE" |  
+"OTHER\_REASON"  
+)
+
+; The location area of user planes which can not enforce the PFDs successfully
+
+\$user-plane-location-area = {  
+\$cell-ids ?,  
+\$enodeb-ids ?,  
+\$extended-enodeb-ids ?,  
+\$routing-area-ids ?,  
+\$tracking-area-ids ?  
+}
+
+; The cell IDs served by the user planes which can not enforce the PFDs successfully
+
+\$cell-ids = "cell-ids" : [ string + ]
+
+; The eNodeB IDs served by the user planes which can not enforce the PFDs successfully
+
+\$enodeb-ids = "enodeb-ids" : [ string + ]
+
+; The extended eNodeB IDs served by the user planes which can not enforce the PFDs successfully
+
+\$extended-enodeb-ids = "extended-enodeb-ids" : [ string + ]
+
+; The Routing Area IDs served by the user planes which can not enforce the PFDs successfully
+
+\$routing-area-ids = "routing-area-ids" : [ string + ]
+
+; The Tracking Area IDs served by the user planes which can not enforce the PFDs successfully
+
+\$tracking-area-ids = "tracking-area-ids" : [ string + ]
+
+
+
+# --- Annex B (informative): Call Flows
+
+## B.1 General
+
+This annex describes the procedures for the interactions between the PFDF and the SCEF.
+
+## --- B.2 Provisioning of PFDs
+
+This clause describes the signalling flow for the Provisioning of PFDs.
+
+![Sequence diagram showing the provisioning of PFDs between SCEF and PFDF.](4af57aad638888edf2062306f8a54a6c_img.jpg)
+
+```
+sequenceDiagram
+    participant SCEF
+    participant PFDF
+    Note right of SCEF: 1. HTTP POST
+    SCEF->>PFDF: 1. HTTP POST
+    Note left of PFDF: 2. HTTP 200 OK
+    PFDF-->>SCEF: 2. HTTP 200 OK
+```
+
+The diagram is a sequence diagram illustrating the interaction between the SCEF (Service Capability Exposure Function) and the PFDF (PDN Gateway Selection Function) for provisioning PFDs. It consists of two vertical lifelines. The first message is an arrow from the SCEF lifeline to the PFDF lifeline, labeled '1. HTTP POST'. The second message is an arrow from the PFDF lifeline back to the SCEF lifeline, labeled '2. HTTP 200 OK'.
+
+Sequence diagram showing the provisioning of PFDs between SCEF and PFDF.
+
+**Figure B.2.1: Provisioning of PFDs**
+
+1. The SCEF sends the HTTP POST to the PFDF to indicate the creation, modification or deletion of PFDs for one or more application identifier(s) including the parameters defined in clause 5.3.5.2.
+2. The PFDF sends the HTTP 200 OK response to the SCEF including the parameters defined in clause 5.3.5.2.
+
+# Annex C (informative): Change history
+
+| Date    | TSG #  | TSG Doc.  | CR   | Rev | Cat | Subject/Comment                                                                               | New    |
+|---------|--------|-----------|------|-----|-----|-----------------------------------------------------------------------------------------------|--------|
+| 2016-10 |        |           |      |     |     | TS skeleton of Nu reference point stage 3.                                                    | 0.0.0  |
+| 2016-10 |        |           |      |     |     | Inclusion of C3-163247, C3-163248, C3-163322 and editorial change from Rapporteur.            | 0.1.0  |
+| 2016-12 |        |           |      |     |     | Inclusion of C3-164069, C3-164227 and editorial change from Rapporteur.                       | 0.2.0  |
+| 2017-01 |        |           |      |     |     | Inclusion of C3-170053, C3-17 0054, C3-170056 and editorial change from Rapporteur.           | 0.3.0  |
+| 2017-02 |        |           |      |     |     | Inclusion of C3-171187, C3-171324, and editorial change from Rapporteur.                      | 0.4.0  |
+| 2017-04 |        |           |      |     |     | Inclusion of C3-172121, C3-172193, C3-172278, and editorial change from Rapporteur.           | 0.5.0  |
+| 2017-05 |        |           |      |     |     | Inclusion of C3-173200, C3-173202, C3-173332, C3-173333 and editorial change from Rapporteur. | 0.6.0  |
+| 2017-06 | CT#76  | CP-171145 |      |     |     | TS sent to plenary for information and approval                                               | 1.0.0  |
+| 2017-06 | CT#76  | CP-171145 |      |     |     | TS approved at plenary                                                                        | 14.0.0 |
+| 2017-09 | CT#77  | CP-172047 | 0001 | 2   | F   | Caching time over the Nu interface                                                            | 14.1.0 |
+| 2017-09 | CT#77  | CP-172047 | 0002 | 2   | F   | Clarification of partial update                                                               | 14.1.0 |
+| 2017-09 | CT#77  | CP-172047 | 0003 | 1   | F   | Correct the example of the PFD provisioning                                                   | 14.1.0 |
+| 2017-09 | CT#77  | CP-172047 | 0004 | 1   | F   | Update the reference of HTTP 1.1                                                              | 14.1.0 |
+| 2017-09 | CT#77  | CP-172047 | 0007 | -   | F   | PFD handling for Push or Combination mode in PFDF                                             | 14.1.0 |
+| 2017-12 | CT#78  | CP-173100 | 0008 | -   | F   | JSON example correction                                                                       | 14.2.0 |
+| 2018-06 | CT#80  |           |      |     |     | Automatic upgrade from previous Release                                                       | 15.0.0 |
+| 2019-03 | CT#83  | CP-190131 | 0010 | 2   | B   | Supported feature negotiation                                                                 | 16.0.0 |
+| 2019-03 | CT#83  | CP-190133 | 0012 | 2   | B   | PFD extension                                                                                 | 16.0.0 |
+| 2019-06 | CT#84  | CP-191097 | 0015 | -   | A   | Reference update: draft-newton-json-content-rules                                             | 16.1.0 |
+| 2019-06 | CT#84  | CP-191100 | 0016 | -   | F   | Encoding of custom header fields                                                              | 16.1.0 |
+| 2019-06 | CT#84  | CP-191102 | 0018 | 1   | B   | PFD management notification                                                                   | 16.1.0 |
+| 2019-12 | CT#86  | CP-193220 | 0019 | 3   | B   | PFD partial failure notification                                                              | 16.2.0 |
+| 2022-03 | SA#95e | -         | -    | -   |     | Update to Rel-17 version (MCC)                                                                | 17.0.0 |
+| 2024-03 | SA#103 | -         | -    | -   |     | Update to Rel-18 version (MCC)                                                                | 18.0.0 |

marked/Rel-18/29_series/29256/raw.md

@@ -0,0 +1,1155 @@
+
+
+# 3GPP TS 29.256 V18.3.0 (2023-12)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Uncrewed Aerial Systems Network Function (UAS-NF); Aerial Management 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 small capital 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 small capital letters.
+
+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 of terms, symbols and abbreviations..... | 8  |
+| 3.1 Terms.....                                         | 8  |
+| 3.2 Symbols.....                                       | 8  |
+| 3.3 Abbreviations .....                                | 8  |
+| 4 Overview.....                                        | 8  |
+| 4.1 Introduction .....                                 | 8  |
+| 5 Services offered by the NEF (UAS-NF).....            | 9  |
+| 5.1 Introduction .....                                 | 9  |
+| 5.2 Nnef_Authentication Service .....                  | 9  |
+| 5.2.1 Service Description .....                        | 9  |
+| 5.2.2 Service Operations.....                          | 9  |
+| 5.2.2.1 Introduction.....                              | 9  |
+| 5.2.2.2 AuthenticateAuthorize Service Operation .....  | 10 |
+| 5.2.2.2.1 General .....                                | 10 |
+| 5.2.2.3 AuthNotify Service Operation .....             | 11 |
+| 5.2.2.3.1 General .....                                | 11 |
+| 6 API Definitions .....                                | 12 |
+| 6.1 Nnef_Authentication Service API.....               | 12 |
+| 6.1.1 Introduction .....                               | 12 |
+| 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.....                                   | 13 |
+| 6.1.3.1 Overview.....                                  | 13 |
+| 6.1.3.2 Resource: uav-authentications .....            | 14 |
+| 6.1.3.2.1 Description .....                            | 14 |
+| 6.1.3.2.2 Resource Definition.....                     | 14 |
+| 6.1.3.2.3 Resource Standard Methods.....               | 14 |
+| 6.1.3.2.4 Resource Custom Operations.....              | 15 |
+| 6.1.5 Notifications .....                              | 15 |
+| 6.1.5.1 General.....                                   | 15 |
+| 6.1.5.2 Authentication Notification .....              | 16 |
+| 6.1.5.2.1 Description .....                            | 16 |
+| 6.1.5.2.2 Target URI.....                              | 16 |
+| 6.1.5.2.3 Standard Methods.....                        | 16 |
+| 6.1.6 Data Model .....                                 | 17 |
+| 6.1.6.1 General.....                                   | 17 |
+| 6.1.6.2 Structured data types.....                     | 17 |
+| 6.1.6.2.1 Introduction .....                           | 17 |
+| 6.1.6.2.2 Type: UAVAuthInfo .....                      | 18 |
+| 6.1.6.2.3 Type: AuthNotification .....                 | 19 |
+| 6.1.6.2.4 Type: UAVAuthResponse.....                   | 20 |
+| 6.1.6.2.5 Type: UAVAuthFailure.....                    | 21 |
+| 6.1.6.2.6 Type: AuthContainer.....                     | 21 |
+| 6.1.6.3 Simple data types and enumerations.....        | 21 |
+| 6.1.6.3.1 Introduction .....                           | 21 |
+| 6.1.6.3.2 Simple data types .....                      | 22 |
+
+- 6.1.6.3.3 Enumeration: AuthResult..... 22
+- 6.1.6.3.4 Enumeration: NotifType ..... 22
+- 6.1.7 Error Handling..... 22
+  - 6.1.7.1 General..... 22
+  - 6.1.7.2 Protocol Errors ..... 22
+  - 6.1.7.3 Application Errors..... 22
+- 6.1.8 Feature negotiation ..... 23
+- 6.1.9 Security ..... 23
+- 6.1.10 HTTP redirection..... 23
+
+A.1 General..... 23  
+A.2 Nnef\_Authentication API ..... 24
+
+# --- 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-NF functionality of the Nnef Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the NEF (UAS-NF).
+
+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].
+
+The Uncrewed Aerial System Network Function (UAS-NF) provides the UAS-specific NEF services to NF service consumers (e.g. AMF, SMF). The UAS-NF is functionality within the NEF.
+
+# --- 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] 3GPP TS 23.256: "Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2".
+- [7] 3GPP TR 21.900: "Technical Specification Group working methods".
+- [8] IETF RFC 9113: "HTTP/2".
+- [9] OpenAPI Initiative, "OpenAPI 3.0.0 Specification", <https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md>.
+- [10] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
+- [11] IETF RFC 9457: "Problem Details for HTTP APIs".
+- [12] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
+- [13] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
+- [14] 3GPP TS 29.510: "Network Function Repository Services; Stage 3".
+- [15] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
+- [16] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
+
+# --- 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].
+
+For the purposes of the present document, the terms and definitions given in 3GPP TS 23.256 [6] 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 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].
+
+|       |                                           |
+|-------|-------------------------------------------|
+| AA    | Authorization/Authentication              |
+| BRID  | Broadcast Remote Identification           |
+| BVLOS | Beyond Visual Line of Sight               |
+| C2    | Command and Control                       |
+| NRID  | Networked Remote Identification           |
+| PEI   | Permanent Equipment Identifier            |
+| RID   | Remote Identification                     |
+| TPAE  | Third Party Authorized Entity             |
+| UAS   | Uncrewed Aerial System                    |
+| UAV   | Uncrewed Aerial Vehicle                   |
+| USS   | UAS Service Supplier                      |
+| UTM   | Uncrewed Aerial System Traffic Management |
+| UUAA  | USS UAV AA                                |
+| UUID  | Universal Unique Identifier               |
+
+# --- 4 Overview
+
+## 4.1 Introduction
+
+Within the 5GC, the NEF (UAS-NF) offers services to the AMF, SMF, and PCF via the Nnef service based interface, and the NEF (UAS-NF) offers services to the SMF+PGW-C via the Nnef service based interface for UUAA-SM and C2 procedure supported in EPS (see 3GPP TS 23.256 [6]).
+
+Figure 4.1-1 provides the reference model (in service based interface representation and in reference point representation), with focus on the NEF (UAS-NF) and the scope of the present specification.
+
+![Figure 4.1-1: Reference model – NEF (UAS-NF). The diagram shows four network functions (AMF, SMF, PCF, and AF) on the left connected to a central NEF (UAS-NF) on the right. The connections are labeled N51 (AMF to NEF), N29 (SMF to NEF), N30 (PCF to NEF), and N33 (AF to NEF). The NEF (UAS-NF) is represented by a large green rectangle containing a smaller green rectangle labeled UAS-NF. The label 'Nnef' is placed between the central connection point and the NEF (UAS-NF) block.](e6df2733626a85205c1db682e6259c46_img.jpg)
+
+Figure 4.1-1: Reference model – NEF (UAS-NF). The diagram shows four network functions (AMF, SMF, PCF, and AF) on the left connected to a central NEF (UAS-NF) on the right. The connections are labeled N51 (AMF to NEF), N29 (SMF to NEF), N30 (PCF to NEF), and N33 (AF to NEF). The NEF (UAS-NF) is represented by a large green rectangle containing a smaller green rectangle labeled UAS-NF. The label 'Nnef' is placed between the central connection point and the NEF (UAS-NF) block.
+
+Figure 4.1-1: Reference model – NEF (UAS-NF)
+
+The functionalities supported by the NEF (UAS-NF) are listed in clause 4.3.2 of 3GPP TS 23.256 [6].
+
+# 5 Services offered by the NEF (UAS-NF)
+
+## 5.1 Introduction
+
+The table 5.1-1 shows the NEF (UAS-NF) Services and Service Operations:
+
+Table 5.1-1 List of NEF (UAS-NF) Services
+
+| Service Name        | Service Operations    | Operation Semantics | Example Consumer(s) | Mapped Service Operation                  |
+|---------------------|-----------------------|---------------------|---------------------|-------------------------------------------|
+| Nnef_Authentication | AuthenticateAuthorize | Request/Response    | AMF, SMF, SMF+PGW-C | Nnef_Authentication_AuthenticateAuthorize |
+|                     | Notification          | Subscribe/Notify    | AMF, SMF, SMF+PGW-C | Nnef_Authentication_Notification          |
+
+## 5.2 Nnef\_Authentication Service
+
+### 5.2.1 Service Description
+
+The service allows communication of authentication and authorization messages between AMF/SMF and external AF (USS). An NF as service consumer (e.g. AMF, SMF, SMF+PGW-C) can authenticate or subscribe to receive notifications from NEF (UAS-NF) related to reauthentication, update authorization data or revoke authorization of the UAV.
+
+### 5.2.2 Service Operations
+
+#### 5.2.2.1 Introduction
+
+The Nnef\_Authentication service supports following service operations:
+
+- AuthenticateAuthorize
+- Notification
+
+#### 5.2.2.2 AuthenticateAuthorize Service Operation
+
+##### 5.2.2.2.1 General
+
+The AuthenticateAuthorize service operation is used during the following procedure:
+
+- UUAA-MM and UUAA-SM procedures (see 3GPP TS 23.256 [6], clause 5.2.2 and clause 5.2.3, respectively)
+- C2 authorization (see 3GPP TS 23.256 [6], clause 5.2.5 and clause 5.4)
+
+The AuthenticateAuthorize service operation is invoked by an NF Service Consumer (e.g. an AMF, SMF, SMF+PGW-C) towards the NEF (UAS-NF), when UUAA-MM is done at 5GS registration, UUAA-SM is done at PDU session establishment, or for Authorization for C2 in 5GS or EPS.
+
+The NF Service Consumer (e.g. the AMF or the SMF or the SMF+PGW-C) shall send the authentication message to NEF (UAS-NF) by sending the HTTP POST request towards the UAV Authentications resource as shown in Figure 5.2.2.2.1-1.
+
+![Sequence diagram showing the AuthenticateAuthorize Service Operation. An NF Service Consumer sends a POST request to the NEF (UAS-NF). The NEF responds with either a 200 OK (UAVAuthResponse) or a 4xx/5xx (ProblemDetails) or 3xx status.](7c6d9bfe9c31ce872722d60b73d20df1_img.jpg)
+
+```
+
+sequenceDiagram
+    participant NF Service Consumer
+    participant NEF (UAS-NF)
+    Note left of NF Service Consumer: 1. POST .../uav-authentications (UAVAuthInfo)
+    NF Service Consumer->>NEF (UAS-NF): Request
+    Note right of NEF (UAS-NF): 2a. 200 OK (UAVAuthResponse)
+    NEF (UAS-NF)-->>NF Service Consumer: Response
+    Note right of NEF (UAS-NF): 2b. 4xx/5xx (ProblemDetails) or 3xx
+    NEF (UAS-NF)-->>NF Service Consumer: Error/Redirect
+  
+```
+
+Sequence diagram showing the AuthenticateAuthorize Service Operation. An NF Service Consumer sends a POST request to the NEF (UAS-NF). The NEF responds with either a 200 OK (UAVAuthResponse) or a 4xx/5xx (ProblemDetails) or 3xx status.
+
+**Figure 5.2.2.2.1-1: AuthenticateAuthorize Service Operation**
+
+- The NF Service Consumer shall send a POST request to the resource representing the UAV Authentications resource of the NEF (UAS-NF) with a "UAVAuthInfo" object in the request body, including:
+  - gsi IE set to GPSI (in the format of External Identifier) of the UAV;
+  - serviceLevelId IE set to Service Level Device Identity;
+  - authMsg IE contains the service-level AA message
+    - . This IE is deprecated; the "authContainer" IE should be used instead.
+  - "authContainer" IE that contains one or more authentication message(s) in the AA container provided by the UE (see 3GPP TS 23.256 [6]). This IE deprecates the "authMsg" IE.
+  - authNotificationURI IE provides the notification URI to receive notifications related to authentication;
+  - authServerAddress IE provides the Authorization Server Address, e.g. Authorization Server FQDN. This IE is not included for intermediate round-trip authentication messages;
+  - nfType IE carries the NF type of the NF service consumer (e.g. AMF or SMF or SMF+PGW-C); and
+  - userLocInfo IE provides the user location information (e.g. cell Id).
+
+If the NF Service Consumer is SMF or SMF+PGW-C, the "UAVAuthInfo" also may include:
+
+- ipAddr IE carries the IP Address associated with the PDU session;
+- pei IE carries the PEI;
+
+If the NF Service Consumer is SMF or SMF+PGW-C, for UUAA-MM and UUAA-SM procedures the "UAVAuthInfo" also may include:
+
+- dnn IE carries the DNN which can be used by NEF (UAS-NF) later on to create a subscription at SMF; and
+- sNssai IE carries the S-NSSAI which can be used by NEF (UAS-NF) later on to create a subscription at SMF.
+
+2a. On success, the NEF (UAS-NF) shall store the result and return "200 OK".
+
+For intermediate round-trip messages, the content (i.e. UAVAuthResponse) shall contain the GPSI of the UAV and Service Level Device Identity. The content optionally includes "authContainer", see 3GPP TS 23.256 [6] for further details.
+
+For the final NEF (UAS-NF) to NF service consumer message, the content (i.e. UAVAuthResponse) shall contain the GPSI of the UAV, notifyCorrId attribute and "authResult" attribute. If the UAV is authenticated successfully, the NEF (UAS-NF) shall set the "authResult" attribute to "AUTH\_SUCCESS". "authMsg" and "authResult" attributes are deprecated; the attribute "authContainer" should be used instead. The content shall contain the authorized Service Level Device Identity and "authContainer" content delivering the AA result, configuration information to the UAV. The AMF forwards the message transparently to UE over NAS MM.
+
+2b. On failure or redirection, one of the HTTP status codes listed in Table 6.1.7.3-1 shall be returned. For a 4xx/5xx response, the message body containing a ProblemDetails structure with the "cause" attribute set to one of the application errors listed in Table 6.1.7.3-1.
+
+If the NEF (UAS-NF) cannot successfully fulfil the received HTTP POST request due to an internal error or an error in the HTTP POST request, the NEF (UAS-NF) shall send the HTTP error response as specified in clause 6.1.7.
+
+If the UAV authentication is failed, the NEF (UAS-NF) shall reject the request with an HTTP "403 Forbidden" response message including the "cause" attribute of the ProblemDetails data structure set to "AUTHENTICATION\_FAILURE". NEF (UAS-NF) shall also include an indication of uasResourceRelease received from the USS to indicate if the PDU sessions associated with the "DNN(s) subject to aerial services" can be released or not, during re-authentication failure, when the service operation is used during Re-authentication procedure.
+
+In above steps, while there is no expected response from the USS in the case of time out, the NEF(UAS-NF) shall return HTTP status code "504 Gateway Timeout", with the message body containing a ProblemDetails structure with the "cause" attribute set to "PEER\_NOT\_RESPONDING".
+
+#### 5.2.2.3 AuthNotify Service Operation
+
+##### 5.2.2.3.1 General
+
+The AuthNotify service operation is used during the following procedure:
+
+- USS Initiated reauthentication (see 3GPP TS 23.256 [6], clause 5.2.4)
+- USS Initiated update authorization data or revoke authorization of the UAV
+
+The AuthNotify service operation is invoked by the NEF (UAS-NF) to inform a NF Service Consumer (e.g. AMF, SMF, SMF+PGW-C), when USS triggers reauthentication, update authorization data or revoke authorization of the UAV. NEF (UAS-NF) shall determine the NF service consumer based on the previously stored UUAA context during the successful UUAA procedure as defined in clause 5.2.2.2.
+
+The NEF (UAS-NF) shall send the AuthNotify request by sending the HTTP POST method towards the Notification URI as shown in Figure 5.2.2.3.1-1.
+
+![Sequence diagram for AuthNotify Service Operation. The diagram shows two lifelines: 'NF Service Consumer' on the left and 'NEF(UAS-NF)' on the right. The sequence of messages is: 1. A solid arrow points from NEF(UAS-NF) to NF Service Consumer with the text '1. POST {notificationUri} (AuthNotification)'. 2a. A dashed arrow points from NF Service Consumer to NEF(UAS-NF) with the text '2a. 204 No content'. 2b. A dashed arrow points from NF Service Consumer to NEF(UAS-NF) with the text '2b. 4xx/5xx (ProblemDetails) or 3xx'.](e787e02d9214556476d95941bda1d350_img.jpg)
+
+```
+
+sequenceDiagram
+    participant NEF as NEF(UAS-NF)
+    participant Consumer as NF Service Consumer
+    Note left of Consumer: 
+    Note right of NEF: 
+    NEF->>Consumer: 1. POST {notificationUri} (AuthNotification)
+    Consumer-->>NEF: 2a. 204 No content
+    Consumer-->>NEF: 2b. 4xx/5xx (ProblemDetails) or 3xx
+  
+```
+
+Sequence diagram for AuthNotify Service Operation. The diagram shows two lifelines: 'NF Service Consumer' on the left and 'NEF(UAS-NF)' on the right. The sequence of messages is: 1. A solid arrow points from NEF(UAS-NF) to NF Service Consumer with the text '1. POST {notificationUri} (AuthNotification)'. 2a. A dashed arrow points from NF Service Consumer to NEF(UAS-NF) with the text '2a. 204 No content'. 2b. A dashed arrow points from NF Service Consumer to NEF(UAS-NF) with the text '2b. 4xx/5xx (ProblemDetails) or 3xx'.
+
+Figure 5.2.2.3.1-1: AuthNotify Service Operation
+
+1. The NEF (UAS-NF) shall send a POST request towards the Notification URI received in the Authenticate service operation request (See clause 5.2.2.2.1). If the AMF for UUAA-MM has changed, the NEF (UAS-NF)
+
+should discover the Notification URI of the new AMF via NRF (in the default notification subscription with the "UUAA\_MM\_AUTH\_NOTIFICATION" notification type). The NEF (UAS-NF) shall be able to determine the NF type of the NF service consumer by nfType IE received in the Authenticate service operation request. The request body shall contain an "AuthNotification" object containing the reauthentication information or update authorization information or revoke authorization indication.
+
+When the procedure is used for reauthentication or reauthorization/update authorization information, the AuthNotification object includes:
+
+- the gpsi IE set to the GPSI (in the format of External Identifier) of the given UAV required to be reauthenticated;
+- serviceLevelId IE set to the Service Level Device Identity of the UAV;
+- authMsg IE contains the service-level AA message. This IE is deprecated; the "authContainer" IE should be used instead.
+- "authContainer" IE that contains AA related data provided by the UE (see 3GPP TS 23.256 [6]). This IE deprecates the "authMsg" IE.
+- notifyType IE set to REAUTH used for reauthentication and/or notifyType IE set to UPDATEAUTH used for update authorization data; and
+- notifyCorrId IE set to the notification correlation ID;
+
+When the procedure is used for authorization revocation, the AuthNotification object includes:
+
+- the gpsi IE set to the GPSI (in the format of External Identifier) of the given UAV;
+- serviceLevelId IE set to the Service Level Device Identity of the UAV;
+- notifyType IE set to REVOKE; and
+- notifyCorrId IE set to the notification correlation ID;
+
+2a. On success, "204 No content" shall be returned without response body. If the NF Service consumer remove the successful UUAA result during UUAA Revocation procedure, the NEF (UAS-NF) shall remove the UUAA context (see clause 5.2.7 of 3GPP TS 23.256 [6]).
+
+2b. On failure or redirection, one of the HTTP status code listed in Table 6.1.5.2.3.1-3 shall be returned. For a 4xx/5xx response, the response body should contain a "ProblemDetails" object.
+
+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 6.1.7.
+
+# --- 6 API Definitions
+
+## 6.1 Nnef\_Authentication Service API
+
+### 6.1.1 Introduction
+
+The Nnef\_Authentication shall use the Nnef\_Authentication API.
+
+The API URI of the Nnef\_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 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 "nnef-authentication".
+- 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 [8], 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 [9] specification of HTTP messages and content bodies for the Nnef\_Authentication 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 [10], 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 [11].
+
+#### 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 applicable.
+
+### 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 Nnef\_Authentication API.
+
+![Diagram showing the resource URI structure for the Nnef_Authentication API. The root path is {apiRoot}/nnef-authentication/<apiVersion>. A line branches from this root to a box containing the resource URI part /uav-authentications.](c52116487ab4b76a2415714183c9a14a_img.jpg)
+
+```
+graph TD; Root["{apiRoot}/nnef-authentication/<apiVersion>"] --> Box["/uav-authentications"];
+```
+
+Diagram showing the resource URI structure for the Nnef\_Authentication API. The root path is {apiRoot}/nnef-authentication/. A line branches from this root to a box containing the resource URI part /uav-authentications.
+
+**Figure 6.1.3.1-1: Resource URI structure of the Nnef\_Authentication 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 name       | Resource URI         | HTTP method or custom operation | Description          |
+|---------------------|----------------------|---------------------------------|----------------------|
+| uav-authentications | /uav-authentications | POST                            | A UAV authentication |
+
+#### 6.1.3.2 Resource: uav-authentications
+
+The resource represents UAV Authentications to be done with the NEF (UAS-NF).
+
+##### 6.1.3.2.1 Description
+
+##### 6.1.3.2.2 Resource Definition
+
+Resource URI: {apiRoot}/nnef-authentication/<apiVersion>/uav-authentications
+
+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 performs UAV authentication.
+
+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                                           |
+|-------------|---|-------------|-------------------------------------------------------|
+| UAVAuthInfo | M | 1           | Represents the data to be used for UAV authentication |
+
+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                                                                                                                                                                                                                                                                        |
+|------------------|---|-------------|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| UAVAuthResponse  | M | 1           | 200 OK                    | Successful request of UAV authentication and authorization. If C2 authorization request is sent during UUAA-SM, the final response indicates that at least UUAA has succeeded.                                                                                                     |
+| RedirectResponse | O | 0..1        | 307<br>Temporary Redirect | Temporary redirection.<br>(NOTE 2)                                                                                                                                                                                                                                                 |
+| RedirectResponse | O | 0..1        | 308<br>Permanent Redirect | Permanent redirection.<br>(NOTE 2)                                                                                                                                                                                                                                                 |
+| UAVAuthFailure   | O | 0..1        | 403<br>Forbidden          | This represents that the UAV authentication is failed, the "cause" attribute of the ProblemDetails data structure set to one of the following application errors:<br>- AUTHENTICATION_FAILURE<br>- SERVICE_NOT_ALLOWED<br>See table 6.1.7.3-1 for the description of these errors. |
+| ProblemDetails   | O | 0..1        | 504<br>Gateway Timeout    | The "cause" attribute may be used to indicate the following application error:<br>- PEER_NOT_RESPONDING<br>See table 6.1.7.3-1 for the description of the error.                                                                                                                   |
+
+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 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 NEF (UAS-NF) or NEF (UAS-NF) (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.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 service instance within the same NEF (UAS-NF) or UAS-NF/NEF (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.3.2.4 Resource Custom Operations
+
+None
+
+### 6.1.5 Notifications
+
+#### 6.1.5.1 General
+
+This clause specifies the notifications provided by the Nnef\_Authentication service.
+
+Notifications shall comply to clause 6.2 of 3GPP TS 29.500 [4] and clause 4.6.2.3 of 3GPP TS 29.501 [5].
+
+#### 6.1.5.2 Authentication Notification
+
+##### 6.1.5.2.1 Description
+
+The NF Service Consumer (e.g. the AMF or SMF or SMF+PGW-C) provides the Notification URI for getting notified about reauthentication requested by the USS. The NEF (UAS-NF) shall notify the NF Service Consumer when reauthentication is requested by the USS.
+
+##### 6.1.5.2.2 Target URI
+
+The Notification URI "{notifUri}" shall be used with the callback URI variables defined in table 6.1.5.2.2-1.
+
+**Table 6.1.5.2.2-1: Callback URI variables**
+
+| Name            | Definition                                    |
+|-----------------|-----------------------------------------------|
+| notificationUri | String formatted as URI with the Callback Uri |
+
+##### 6.1.5.2.3 Standard Methods
+
+###### 6.1.5.2.3.1 POST
+
+This method shall support the request data structures specified in table 6.1.5.2.3.1-1 and the response data structures and response codes specified in table 6.1.5.2.3.1-2.
+
+**Table 6.1.5.2.3.1-1: Data structures supported by the POST Request Body**
+
+| Data type        | P | Cardinality | Description                                |
+|------------------|---|-------------|--------------------------------------------|
+| AuthNotification | M | 1           | Contains the reauthentication information. |
+
+**Table 6.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 |
+| RedirectResponse | O | 0..1        | 307 Temporary Redirect | Temporary redirection.<br>(NOTE 2)          |
+| RedirectResponse | O | 0..1        | 308 Permanent Redirect | Permanent redirection.<br>(NOTE 2)          |
+
+NOTE 1: The mandatory HTTP error status codes for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply, with response body containing an object of ProblemDetails data type (see clause 5.2.7 of 3GPP TS 29.500 [4]).
+
+NOTE 2: RedirectResponse may be inserted by an SCP, see clause 6.10.9.1 of 3GPP TS 29.500 [4].
+
+**Table 6.1.5.2.3.1-4: Headers supported by the 307 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                                                                                                                                                            |
+|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | A URI pointing to the endpoint of NF service consumer to which the notification should be sent. 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 notification is redirected.                                                                                                                                        |
+
+**Table 6.1.5.2.3.1-5: Headers supported by the 308 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                                                                                                                                                            |
+|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | A URI pointing to the endpoint of NF service consumer to which the notification should be sent. 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 notification is redirected.                                                                                                                                        |
+
+### 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 Nnef\_Authentication service based interface protocol.
+
+**Table 6.1.6.1-1: Nnef\_Authentication specific Data Types**
+
+| Data type        | Clause defined | Description                                  | Applicability |
+|------------------|----------------|----------------------------------------------|---------------|
+| UAVAuthInfo      | 6.1.6.2.2      | Information within Authenticate Request      |               |
+| AuthNotification | 6.1.6.2.3      | Information within notification              |               |
+| UAVAuthResponse  | 6.1.6.2.4      | Information within Authenticate Response     |               |
+| UAVAuthFailure   | 6.1.6.2.5      | Information within Authenticate Response     |               |
+| AuthResult       | 6.1.6.3.3      | Enumeration indicating authentication result |               |
+| NotifyType       | 6.1.6.3.4      | Enumeration Notification type                |               |
+| AuthContainer    | 6.1.6.2.6      | Carries the AA related data                  |               |
+
+Table 6.1.6.1-2 specifies data types re-used by the Nnef\_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 Nnef\_Authentication service based interface.
+
+**Table 6.1.6.1-2: Nnef\_Authentication re-used Data Types**
+
+| Data type        | Reference           | Comments                                         | Applicability |
+|------------------|---------------------|--------------------------------------------------|---------------|
+| IpAddr           | 3GPP TS 29.571 [15] | IP address                                       |               |
+| Pei              | 3GPP TS 29.571 [15] | Permanent Equipment Identifier                   |               |
+| Uri              | 3GPP TS 29.571 [15] | Uri                                              |               |
+| Gpsi             | 3GPP TS 29.571 [15] | GPSI                                             |               |
+| ExtSnssai        | 3GPP TS 29.571 [15] | Ext Snssai                                       |               |
+| Dnn              | 3GPP TS 29.571 [15] | DNN information                                  |               |
+| UserLocation     | 3GPP TS 29.571 [15] | User location                                    |               |
+| RedirectResponse | 3GPP TS 29.571 [15] | Contains redirection related information         |               |
+| NFType           | 3GPP TS 29.510 [14] | NF Type                                          |               |
+| ReftoBinaryData  | 3GPP TS 29.571 [15] | authMsg data, AA message payload data            |               |
+| Bytes            | 3GPP TS 29.571 [15] | Binary data encoded as a base64 character string |               |
+
+#### 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: UAVAuthInfo
+
+Table 6.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        | This IE may be present if the NF Service Consumer is the SMF or SMF+PGW-C.<br><br>When present, this IE indicates the IP address associated with the PDU session.                      |               |
+| authMsg             | RefToBinaryData      | O | 0..1        | Contains the service-level AA message. 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        | This IE may be present if the NF Service Consumer is the SMF or SMF+PGW-C.<br><br>When present, PEI associated with the UAV.                                                           |               |
+| authServerAddress   | string               | O | 0..1        | Provides the Authorization Server Address, e.g. Authorization Server FQDN.                                                                                                             |               |
+| authNotificationURI | Uri                  | C | 0..1        | This IE shall be present in the initial authentication message.<br><br>It carries the notification URI to receive authentication related notifications                                 |               |
+| dnn                 | Dnn                  | C | 0..1        | This IE shall be present if the NF Service Consumer is the SMF or SMF+PGW-C.<br><br>When present, this IE indicates DNN associated with the PDU session.                               |               |
+| sNssai              | ExtSnsai             | C | 0..1        | This IE shall be present if the NF Service Consumer is the SMF.<br><br>When present, this IE indicates the S-NSSAI associated with the PDU session.                                    |               |
+| ueLocInfo           | UserLocation         | O | 0..1        | This IE shall contain the UE location information if it is available.                                                                                                                  |               |
+| nfType              | NFType               | M | 1           | NFType of the NF service consumer.<br>Possible NFType values supported in this release of the specification are <ul style="list-style-type: none"> <li>- AMF</li> <li>- SMF</li> </ul> |               |
+
+##### 6.1.6.2.3 Type: AuthNotification
+
+Table 6.1.6.2.3-1: Definition of type AuthNotification
+
+| 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        | RefToBinaryData      | C | 0..1        | Contains the service-level AA message.<br>This IE may be present if the notifType is set to "UPDATEAUTH". This attribute is deprecated; the attribute "authContainer" should be used instead.   |               |
+| authContainer  | array(AuthContainer) | C | 1..N        | Contains the AA related data, including optionally the "authResult" attribute. This IE shall be present if the notifType is set to "UPDATEAUTH". This attribute deprecates "authMsg" attribute. |               |
+| notifType      | NotifType            | M | 1           | This IE shall contain the notification type.                                                                                                                                                    |               |
+| notifyCorrId   | string               | M | 1           | This IE shall contain the Notification Correlation Id.                                                                                                                                          |               |
+
+##### 6.1.6.2.4 Type: UAVAuthResponse
+
+Table 6.1.6.2.4-1: Definition of type UAVAuthResponse
+
+| Attribute name | Data type            | P | Cardinality | Description                                                                                                                                                                                                           | Applicability |
+|----------------|----------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| gpsi           | Gpsi                 | M | 1           | GPSI of the UAV                                                                                                                                                                                                       |               |
+| authResult     | AuthResult           | C | 0..1        | This IE shall be present for the final NEF (UAS-NF) to NF service consumer message.<br><br>Conveys the UAV authentication result. This attribute is deprecated; the attribute "authContainer" should be used instead. |               |
+| authMsg        | RefToBinaryData      | O | 0..1        | Contains the service-level AA message. This attribute is deprecated; the attribute "authContainer" should be used instead.                                                                                            |               |
+| authContainer  | array(AuthContainer) | C | 1..N        | Contains the AA related data, including the "authResult" attribute in the final AA response. This attribute shall be present for the final AA response message. This attribute deprecates "authMsg" attribute.        |               |
+| serviceLevelId | string               | O | 0..1        | This IE contains the authorized Service Level Device Identity                                                                                                                                                         |               |
+| notifyCorrId   | string               | O | 0..1        | When present, this IE shall contain the Notification Correlation Id.                                                                                                                                                  |               |
+
+##### 6.1.6.2.5 Type: UAVAuthFailure
+
+Table 6.1.6.2.5-1: Definition of type UAVAuthFailure
+
+| Attribute name     | Data type      | P | Cardinality | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Applicability |
+|--------------------|----------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| error              | ProblemDetails | M | 1           | Represents the application error information. The application level error cause shall be encoded in the "cause" attribute.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |               |
+| uasResourceRelease | boolean        | C | 0..1        | <p>This IE shall be present and used to indicate if the PDU sessions associated with the "DNN(s) subject to aerial services" can be released or not, during re-authentication failure.</p> <p>It shall be included if the "cause" attribute of the ProblemDetails data structure set to "AUTHENTICATION_FAILURE".</p> <p>When present, it shall be set as follows:<br/> - true: the PDU sessions associated with the "DNN(s) subject to aerial services" release is requested;<br/> - false (default): the PDU sessions associated with the "DNN(s) subject to aerial services" release is not requested.</p> |               |
+
+##### 6.1.6.2.6 Type: AuthContainer
+
+Table 6.1.6.2.6-1: Definition of type AuthContainer
+
+| Attribute name | Data type       | P | Cardinality | Description                                                                                                            | Applicability |
+|----------------|-----------------|---|-------------|------------------------------------------------------------------------------------------------------------------------|---------------|
+| authMsgType    | Bytes           | O | 0..1        | This IE, when present, carries the Service-level-AA payload type specified in clause 9.11.2.15 of 3GPP TS 24.501 [16]. |               |
+| 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.                                                    |               |
+
+#### 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.3.3 Enumeration: AuthResult
+
+The enumeration AuthResult represents the result of authentication and/or authorization. It shall comply with the provisions defined in table 6.1.5.3.3-1.
+
+**Table 6.1.6.3.3-1: Enumeration AuthResult**
+
+| Enumeration value | Description                                               | Applicability |
+|-------------------|-----------------------------------------------------------|---------------|
+| "AUTH_SUCCESS"    | The UAV authentication or C2 Authorization has succeeded. |               |
+| "AUTH_FAIL"       | The UAV authentication or C2 Authorization has failed.    |               |
+
+##### 6.1.6.3.4 Enumeration: NotifType
+
+The enumeration NotifType represents the type of notification. It shall comply with the provisions defined in table 6.1.6.3.4-1.
+
+**Table 6.1.6.3.4-1: Enumeration NotifType**
+
+| Enumeration value | Description                                    | Applicability |
+|-------------------|------------------------------------------------|---------------|
+| "REAUTH"          | The UAV needs to be reauthenticated.           |               |
+| "UPDATEAUTH"      | Authorization data needs to be updated to UAV. |               |
+| "REVOKE"          | Revoke UAV authentication and authorization    |               |
+
+### 6.1.7 Error Handling
+
+#### 6.1.7.1 General
+
+For the Nnef\_Authentication 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 Nnef\_Authentication API.
+
+#### 6.1.7.2 Protocol Errors
+
+No specific procedures for the Nnef\_Authentication service are specified.
+
+#### 6.1.7.3 Application Errors
+
+The application errors defined for the Nnef\_Authentication service are listed in Table 6.1.7.3-1.
+
+**Table 6.1.7.3-1: Application errors**
+
+| Application Error      | HTTP status code    | Description                                                            |
+|------------------------|---------------------|------------------------------------------------------------------------|
+| AUTHENTICATION_FAILURE | 403 Forbidden       | The UAV authentication is failed                                       |
+| SERVICE_NOT_ALLOWED    | 403 Forbidden       | UAS services not allowed                                               |
+| PEER_NOT_RESPONDING    | 504 Gateway Timeout | No response is received from the remote peer (i.e. USS) when time out. |
+
+### 6.1.8 Feature negotiation
+
+The optional features in table 6.1.8-1 are defined for the Nnef\_Authentication 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 [12] and 3GPP TS 29.500 [4], the access to the Nnef\_Authentication API may be authorized by means of the OAuth2 protocol (see IETF RFC 6749 [13]), based on local configuration, using the "Client Credentials" authorization grant, where the NRF (see 3GPP TS 29.510 [14]) plays the role of the authorization server.
+
+If OAuth2 is used, an NF Service Consumer, prior to consuming services offered by the Nnef\_Authentication API, shall obtain a "token" from the authorization server, by invoking the Access Token Request service, as described in 3GPP TS 29.510 [14], 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 Nnef\_Authentication service.
+
+The Nnef\_Authentication API defines a single scope "nnef-authentication" 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 Nnef\_Authentication service instance when using direct or indirect communications (see 3GPP TS 29.500 [4]).
+
+An SCP that reselects a different NEF (UAS-NF) producer instance will return the NF Instance ID of the new NEF (UAS-NF) 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 NEF (UAS-NF) redirects a service request to a different NEF (UAS-NF) using an 307 Temporary Redirect or 308 Permanent Redirect status code, the identity of the new NEF (UAS-NF) 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 3.0.0 specifications in YAML format, following guidelines in 3GPP TS 29.501 [5].
+
+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 Nnef\_Authentication API
+
+```
+openapi: 3.0.0
+
+info:
+  title: Nnef_Authentication
+  version: '1.0.2'
+  description: |
+    NEF Auth Service.
+    © 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+    All rights reserved.
+
+externalDocs:
+  description: >
+    3GPP TS 29.256 V17.3.0; 5G System;Uncrewed Aerial Systems Network Function (UAS-NF);
+    Aerial Management Services; Stage 3
+  url: https://www.3gpp.org/ftp/Specs/archive/29_series/29.256/
+
+servers:
+  - url: '{apiRoot}/nnef-authentication/v1'
+    variables:
+      apiRoot:
+        default: https://example.com
+        description: apiRoot as defined in clause 4.4 of 3GPP TS 29.501
+
+security:
+  - {}
+  - oAuth2ClientCredentials:
+    - nnef-authentication
+
+paths:
+  /uav-authentications:
+    post:
+      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: 'TS29571_CommonData.yaml#/components/responses/307'
+        '308':
+          $ref: 'TS29571_CommonData.yaml#/components/responses/308'
+        '400':
+          $ref: 'TS29571_CommonData.yaml#/components/responses/400'
+        '403':
+          description: UAV authentication failure
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/UAVAuthFailure'
+```
+
+```
+'504':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/504'
+default:
+  $ref: 'TS29571_CommonData.yaml#/components/responses/default'
+callbacks:
+  authNotification:
+    '{request.body#/authNotification }':
+      post:
+        requestBody:
+          required: true
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/AuthNotification'
+        responses:
+          '204':
+            description: Successful Notification response
+          '307':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/307'
+          '308':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/308'
+          '400':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/400'
+          default:
+            $ref: 'TS29571_CommonData.yaml#/components/responses/default'
+
+components:
+  securitySchemes:
+    oAuth2ClientCredentials:
+      type: oauth2
+      flows:
+        clientCredentials:
+          tokenUrl: '{nrfApiRoot}/oauth2/token'
+          scopes:
+            nnef-authentication: Access to the Nnef_authentication API
+
+schemas:
+#
+# STRUCTURED DATA TYPES
+#
+  UAVAuthInfo:
+    description: UAV auth data
+    type: object
+    required:
+      - gps
+      - serviceLevelId
+      - nfType
+    properties:
+      gps:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/Gps'
+      serviceLevelId:
+        type: string
+      authNotificationURI:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
+      ipAddr:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/IpAddr'
+      pei:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/Pei'
+      authServerAddress:
+        type: string
+      authMsg:
+        allOf:
+          - $ref: 'TS29571_CommonData.yaml#/components/schemas/RefToBinaryData'
+            deprecated: true
+      authContainer:
+        type: array
+        items:
+          $ref: '#/components/schemas/AuthContainer'
+        minItems: 1
+      ueLocInfo:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/UserLocation'
+      dnn:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/Dnn'
+      sNssai:
+```
+
+```
+$ref: 'TS29571_CommonData.yaml#/components/schemas/ExtSnssai'
+nfType:
+$ref: 'TS29510_Nnrf_NFManagement.yaml#/components/schemas/NFType'
+
+UAVAuthResponse:
+  description: UAV auth response data
+  type: object
+  required:
+    - gpsi
+  properties:
+    gpsi:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi'
+    serviceLevelId:
+      type: string
+    authMsg:
+      allOf:
+        - $ref: 'TS29571_CommonData.yaml#/components/schemas/RefToBinaryData'
+      deprecated: true
+    authContainer:
+      type: array
+      items:
+        $ref: '#/components/schemas/AuthContainer'
+      minItems: 1
+    authResult:
+      allOf:
+        - $ref: '#/components/schemas/AuthResult'
+      deprecated: true
+    notifyCorrId:
+      type: string
+
+AuthNotification:
+  description: UAV related notification
+  type: object
+  required:
+    - gpsi
+    - serviceLevelId
+    - notifyType
+    - notifyCorrId
+  properties:
+    gpsi:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi'
+    serviceLevelId:
+      type: string
+    notifyCorrId:
+      type: string
+    authMsg:
+      allOf:
+        - $ref: 'TS29571_CommonData.yaml#/components/schemas/RefToBinaryData'
+      deprecated: true
+    authContainer:
+      type: array
+      items:
+        $ref: '#/components/schemas/AuthContainer'
+      minItems: 1
+    notifyType:
+      $ref: '#/components/schemas/NotifyType'
+
+UAVAuthFailure:
+  description: UAV auth failure
+  type: object
+  required:
+    - error
+  properties:
+    error:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/ProblemDetails'
+    uasResourceRelease:
+      type: boolean
+      default: false
+
+AuthContainer:
+  description: Authentication/Authorization data
+  type: object
+  properties:
+    authMsgType:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Bytes'
+    authMsgPayload:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/RefToBinaryData'
+    authResult:
+```
+
+```
+$ref: '#/components/schemas/AuthResult'
+```
+
+```
+#
+```
+
+```
+# SIMPLE DATA TYPES
+```
+
+```
+#
+```
+
+```
+#
+```
+
+```
+# ENUMERATIONS
+```
+
+```
+#
+```
+
+```
+AuthResult:  
+  description: Enumeration representing the result of authentication and/or authorization.  
+  anyOf:  
+  - type: string  
+    enum:  
+    - AUTH_SUCCESS  
+    - AUTH_FAIL  
+  - type: string  
+NotifyType:  
+  description: Enumeration representing the type of notification.  
+  anyOf:  
+  - type: string  
+    enum:  
+    - REAUTH  
+    - UPDATEAUTH  
+    - REVOKE  
+  - type: string
+```
+
+# Annex B (informative): Change history
+
+| Change history |              |           |      |     |     |                                                                                                                                        |             |
+|----------------|--------------|-----------|------|-----|-----|----------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date           | Meeting      | TDoc      | CR   | Rev | Cat | Subject/Comment                                                                                                                        | New version |
+| 2021-04        | CT4#103-e    | C4-212292 |      |     |     | Initial TS skeleton.                                                                                                                   | 0.0.0       |
+| 2021-04        | CT4#103-e    | C4-212598 |      |     |     | Added scope, introduction, references, and abbreviations.                                                                              | 0.1.0       |
+| 2021-05        | CT4#104-e    | C4-213529 |      |     |     | Aligned introduction terminology. Added, updated references.                                                                           | 0.2.0       |
+| 2021-08        | CT4#105-e    | C4-214758 |      |     |     | Aligned interfaces, added Nnef_Auth service.                                                                                           | 0.3.0       |
+| 2021-10        | CT4#106-e    | C4-215522 |      |     |     | Several alignments with stage-2, clean-up, added OpenAPI for Nnef_Auth.                                                                | 0.4.0       |
+| 2021-11        | CT4#107-e    | C4-216474 |      |     |     | Several further alignments with stage-2: aligned API and operation names, terminology. Further clean-up done.                          | 0.5.0       |
+| 2021-12        | CT#94        | CP-213160 |      |     |     | V1.0.0 presented for information                                                                                                       | 1.0.0       |
+| 2022-01        | CT4#107bis-e | C4-220456 |      |     |     | Several consistency issues addressed. Implemented pCRs C4-220121, C4-220122, C4-220285, C4-220291, C4-220292, C4-220293, and C4-220387 | 1.1.0       |
+| 2022-02        | CT4#108-e    | C4-221594 |      |     |     | Further consistency issues addressed. Implemented pCRs C4-221324, C4-221494, C4-221519, and C4-221340.                                 | 1.2.0       |
+| 2022-03        | CT#95e       | CP-220109 |      |     |     | TS presented for approval                                                                                                              | 2.0.0       |
+| 2022-03        | CT#95e       |           |      |     |     | TS approved                                                                                                                            | 17.0.0      |
+| 2022-06        | CT#96e       | CP-221044 | 0001 | 1   |     | Add Notification Correlation id                                                                                                        | 17.1.0      |
+| 2022-06        | CT#96e       | CP-221044 | 0002 | 1   |     | Indication of UAS service release                                                                                                      | 17.1.0      |
+| 2022-06        | CT#96e       | CP-221044 | 0004 |     |     | Removal of revoke cause                                                                                                                | 17.1.0      |
+| 2022-06        | CT#96e       | CP-221028 | 0005 |     |     | Remove the apiVersion placeholder from the resource URI variables table                                                                | 17.1.0      |
+| 2022-06        | CT#96e       | CP-221282 | 0007 | 1   |     | 29.256 Rel-17 API version and External doc update                                                                                      | 17.1.0      |
+| 2022-09        | CT#97e       | CP-222036 | 0009 |     |     | Fix for formatting of OpenAPI description field                                                                                        | 17.2.0      |
+| 2022-09        | CT#97e       | CP-222058 | 0010 |     |     | 29.256 Rel-17 API version and External doc update                                                                                      | 17.2.0      |
+| 2022-12        | CT#98e       | CP-223056 | 0008 | 2   |     | Corrections for Auth message type                                                                                                      | 17.3.0      |
+| 2022-12        | CT#98e       | CP-223066 | 0011 |     |     | 29.256 Rel-17 API version and External doc update                                                                                      | 17.3.0      |
+| 2023-03        | CT#99        | CP-230082 | 0012 | 1   |     | Rejecting PDN connection for C2 communication when UAS service is not allowed                                                          | 17.4.0      |
+| 2023-03        | CT#99        | CP-230068 | 0014 |     |     | Miscellaneous corrections                                                                                                              | 18.0.0      |
+| 2023-06        | CT#100       | CP-231027 | 0013 | 5   | F   | Location header and missing Redirection clause                                                                                         | 18.1.0      |
+| 2023-09        | CT#101       | CP-232047 | 0018 | 1   | A   | Authorization Notification Callbackfor UUAA-MM after AMF Change                                                                        | 18.2.0      |
+| 2023-09        | CT#101       | CP-232046 | 0017 | -   | B   | Clarification on Direct C2 authorization procedure                                                                                     | 18.2.0      |
+| 2023-12        | CT#102       | CP-233027 | 0020 | -   | F   | HTTP RFCs obsoleted by IETF RFC 9113                                                                                                   | 18.3.0      |
+| 2023-12        | CT#102       | CP-233030 | 0021 | -   | F   | ProblemDetails RFC 7807 obsoleted by 9457                                                                                              | 18.3.0      |

marked/Rel-18/29_series/29542/raw.md

@@ -0,0 +1,849 @@
+
+
+# 3GPP TS 29.542 V18.3.0 (2023-12)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Session Management Services for Non-IP Data Delivery (NIDD); 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 letters is a red signal wave icon, and below that, the text 'A GLOBAL INITIATIVE' 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.
+
+UMTSTM 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 Terms.....                                                                           | 7  |
+| 3.2 Symbols.....                                                                         | 7  |
+| 3.3 Abbreviations .....                                                                  | 7  |
+| 4 Overview.....                                                                          | 7  |
+| 4.1 Introduction .....                                                                   | 7  |
+| 5 Services offered by the SMF for NIDD .....                                             | 8  |
+| 5.1 Introduction .....                                                                   | 8  |
+| 5.2 Nsmf_NIDD Service .....                                                              | 8  |
+| 5.2.1 Service Description .....                                                          | 8  |
+| 5.2.2 Service Operations.....                                                            | 8  |
+| 5.2.2.1 Introduction.....                                                                | 8  |
+| 5.2.2.2 Delivery .....                                                                   | 8  |
+| 5.2.2.2.1 General .....                                                                  | 8  |
+| 6 API Definitions .....                                                                  | 9  |
+| 6.1 Nsmf_NIDD Service API.....                                                           | 9  |
+| 6.1.1 Introduction .....                                                                 | 9  |
+| 6.1.2 Usage of HTTP.....                                                                 | 9  |
+| 6.1.2.1 General.....                                                                     | 9  |
+| 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.....                                                         | 10 |
+| 6.1.3 Resources.....                                                                     | 10 |
+| 6.1.3.1 Overview.....                                                                    | 10 |
+| 6.1.3.2 Resource: Individual PDU session .....                                           | 11 |
+| 6.1.3.2.1 Description .....                                                              | 11 |
+| 6.1.3.2.2 Resource Definition.....                                                       | 11 |
+| 6.1.3.2.3 Resource Standard Methods.....                                                 | 11 |
+| 6.1.3.2.4 Resource Custom Operations.....                                                | 12 |
+| 6.1.3.2.4.2.1 Description.....                                                           | 12 |
+| 6.1.3.2.4.2.2 Operation Definition .....                                                 | 12 |
+| 6.1.4 Custom Operations without associated resources .....                               | 13 |
+| 6.1.5 Notifications .....                                                                | 13 |
+| 6.1.6 Data Model .....                                                                   | 13 |
+| 6.1.6.1 General.....                                                                     | 13 |
+| 6.1.6.2 Structured data types.....                                                       | 14 |
+| 6.1.6.2.1 Introduction .....                                                             | 14 |
+| 6.1.6.2.2 Type: DeliverReqData.....                                                      | 14 |
+| 6.1.6.2.3 Type: DeliverAddInfo.....                                                      | 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 ..... | 14 |
+| 6.1.6.4.1 Type: DeliverError .....                                                       | 14 |
+| 6.1.6.5 Binary data.....                                                                 | 15 |
+| 6.1.6.5.1 Mobile Terminated 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        |
+| 6.1.10                        | HTTP redirection.....              | 16        |
+| <b>Annex A (normative):</b>   | <b>OpenAPI specification .....</b> | <b>17</b> |
+| A.1                           | General.....                       | 17        |
+| A.2                           | Nsmf_NIDD API .....                | 17        |
+| <b>Annex B (informative):</b> | <b>Change history .....</b>        | <b>20</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 Nsmf Service Based Interfaces for Non-IP Data Delivery (NIDD). It provides stage 3 protocol definitions and message flows, and specifies the API for the service offered by the SMF.
+
+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].
+
+# --- 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: "Hypertext Transfer Protocol Version 2 (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 29.541: "5G System (5GS); Network Exposure (NE) function services for Non-IP Data Delivery (NIDD) and Short Message Services (SMS); Stage 3".
+- [15] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
+
+# 3 Definitions, symbols and abbreviations
+
+## 3.1 Terms
+
+Void.
+
+## 3.2 Symbols
+
+Void.
+
+## 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].
+
+|       |                                         |
+|-------|-----------------------------------------|
+| 5GC   | 5G Core Network                         |
+| AMF   | Access and Mobility Management Function |
+| H-SMF | Home SMF                                |
+| I-SMF | Intermediate SMF                        |
+| NEF   | Network Exposure Function               |
+| NIDD  | Non-IP Data Delivery                    |
+| MT    | Mobile Terminated                       |
+| SMF   | Session Management Function             |
+| V-SMF | Visited SMF                             |
+
+# 4 Overview
+
+## 4.1 Introduction
+
+Within the 5GC, the SMF offers services to the NF service consumers via the Nsmf service based interface (see 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3]).
+
+Figure 4.1-1 provides the reference model (in service based interface representation and in reference point representation), with focus on the services specified within the present specification.
+
+![Reference model diagram showing the NEF connected to the SMF via the N29 reference point.](06da11ab76cacc38bbcd714e437797ea_img.jpg)
+
+The diagram illustrates the reference model for the SMF. It features two main components: a Network Exposure Function (NEF) on the left and a Session Management Function (SMF) on the right. The NEF is represented by a light green rectangle. The SMF is represented by a larger light green rectangle with a semi-circular interface on its left side. A horizontal line connects the NEF to the SMF's interface. This line is labeled with 'N29' near the NEF and 'Nsmf' near the SMF's interface, indicating the reference point and service based interface respectively.
+
+Reference model diagram showing the NEF connected to the SMF via the N29 reference point.
+
+Figure 4.1-1: Reference model – SMF
+
+N29 is the reference point between the (H-)SMF and the NEF.
+
+The functionalities supported by the SMF are listed in clause 6.2.2 of 3GPP TS 23.501 [2].
+
+# 5 Services offered by the SMF for NIDD
+
+## 5.1 Introduction
+
+The SMF supports the following service(s) for NIDD.
+
+**Table 5.1-1: NF Service(s) provided by SMF for NIDD**
+
+| Service Name | Description                                                                     | Example Consumer |
+|--------------|---------------------------------------------------------------------------------|------------------|
+| Nsmf_NIDD    | This service allows the NF consumer NF to deliver NIDD MT data to PDU sessions. | NEF              |
+
+## 5.2 Nsmf\_NIDD Service
+
+### 5.2.1 Service Description
+
+The Nsmf\_NIDD service operates on the PDU Sessions. The service operations exposed by this service allow an NF consumer (i.e. NEF) to deliver NEF anchored Mobile Terminated (MT) data for a given PDU session of a UE towards the SMF.
+
+The Nsmf\_NIDD service supports the following service operations:
+
+**Table 5.2.1-1: Service operations supported by the Nsmf\_NIDD service**
+
+| Service Operations | Description                                             | Operation Semantics | Example Consumer(s) |
+|--------------------|---------------------------------------------------------|---------------------|---------------------|
+| Delivery           | Deliver MT NIDD user data to the PDU session of the UE. | Request/Response    | NEF                 |
+
+### 5.2.2 Service Operations
+
+#### 5.2.2.1 Introduction
+
+See Table 5.2.1-1 for an overview of the service operations supported by the Nsmf\_NIDD service.
+
+#### 5.2.2.2 Delivery
+
+##### 5.2.2.2.1 General
+
+The Delivery service operation shall be used to transfer NEF anchored MT data for a given PDU session.
+
+It is used in the following procedures:
+
+- NEF anchored Mobile Terminated Data Transport (see clause 4.25.5 of 3GPP TS 23.502 [3]).
+
+The NF Service Consumer (i.e. NEF) shall deliver MT data to the SMF by using the HTTP POST method ("deliver" custom operation) as shown in Figure 5.2.2.2.1-1.
+
+![Sequence diagram showing the transfer of MT data from an NF Service Consumer to an SMF. The consumer sends a POST request to the URI '.../pdu-sessions/{pduSessionRef}/deliver' with 'DeliverReqData'. The SMF responds with either a 204 No Content (2a) or an error status code (2b) such as 4xx/5xx (DeliverError/ProblemDetails) or 3xx.](562f471e8153729557e6a4ee6343c32c_img.jpg)
+
+```
+
+sequenceDiagram
+    participant NF Service Consumer
+    participant SMF
+    Note right of NF Service Consumer: 1. POST .../pdu-sessions/{pduSessionRef}/deliver (DeliverReqData)
+    NF Service Consumer->>SMF: Request
+    Note left of SMF: 2a. 204 No Content
+    SMF-->>NF Service Consumer: Response 2a
+    Note left of SMF: 2b. 4xx/5xx (DeliverError/ProblemDetails) or 3xx
+    SMF-->>NF Service Consumer: Response 2b
+  
+```
+
+Sequence diagram showing the transfer of MT data from an NF Service Consumer to an SMF. The consumer sends a POST request to the URI '.../pdu-sessions/{pduSessionRef}/deliver' with 'DeliverReqData'. The SMF responds with either a 204 No Content (2a) or an error status code (2b) such as 4xx/5xx (DeliverError/ProblemDetails) or 3xx.
+
+**Figure 5.2.2.2.1-1: Transfer MT Data**
+
+1. The NF Service Consumer shall send a POST request to the URI of "deliver" custom operation on an Individual PDU session resource in the SMF. The content of the POST request shall contain the MT data to be delivered.
+
+NOTE: The URI of the individual PDU session resource is provided by SMF to the NEF during SMF-NEF connection creation (see clause 5.2.2.2.1 of 3GPP TS 29.541 [14]).
+
+- 2a. On success, "204 No Content" shall be returned.
+
+- 2b. On failure or redirection, one of the HTTP status code listed in Table 6.1.3.2.4.2.2-2 shall be returned. For a 4xx/5xx response, the message body may contain a DeliverError or ProblemDetails object, with the "cause" attribute indicating the cause of the failure. If Estimated Maximum Waiting Time is received from AMF, the SMF shall include it in the message body.
+
+# 6 API Definitions
+
+## 6.1 Nsmf\_NIDD Service API
+
+### 6.1.1 Introduction
+
+The Nsmf\_NIDD service shall use the Nsmf\_NIDD API.
+
+The API URI of the Nsmf\_NIDD API shall be:
+
+**{apiRoot}/<apiName>/<apiVersion>/**
+
+The request URI used in HTTP request 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 "nsmf-nidd".
+- 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 Nsmf\_NIDD API is contained in Annex A.
+
+#### 6.1.2.2 HTTP standard headers
+
+##### 6.1.2.2.1 General
+
+The usage of HTTP standard headers shall be supported as specified in clause 5.2.2 of 3GPP TS 29.500 [4].
+
+##### 6.1.2.2.2 Content type
+
+The following content types shall be supported:
+
+- the JSON format (IETF RFC 8259 [12]). The use of the JSON format shall be signalled by the content type "application/json". See also clause 5.4 of 3GPP TS 29.500 [4].
+- the Problem Details JSON Object (IETF RFC 9457 [13]). The use of the Problem Details JSON object in a HTTP response body shall be signalled by the content type "application/problem+json".
+
+NOTE: "application/json" is used in a response that includes a payload body containing an application-specific data structure, see clause 4.8 of 3GPP TS 29.501 [5].
+
+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 or two binary body parts 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.5gnas  | Binary encoded payload, encoding a 5GS NAS message or 5G NAS IEs, as specified in 3GPP TS 24.501 [7]. |
+
+See clause 6.1.6.5 for the binary payloads supported in the binary body part of multipart messages.
+
+#### 6.1.2.3 HTTP custom headers
+
+In this release of the specification, no specific custom headers are defined for the Nsmf\_NIDD service.
+
+For 3GPP specific HTTP custom headers used across all service based interfaces, see clause 5.2.3 of 3GPP TS 29.500 [4].
+
+### 6.1.3 Resources
+
+#### 6.1.3.1 Overview
+
+Figure 6.1.3.1-1 describes the resource URI structure of the Nsmf\_NIDD API.
+
+![Figure 6.1.3.1-1: Resource URI structure of the Nsmf_NIDD API. The diagram shows a hierarchical tree structure of URI paths. The root is {apiRoot}/nsmf-nidd/<apiVersion>. It branches to /pdu-sessions, which branches to /{pduSessionRef}, which finally branches to /deliver. The /deliver path is enclosed in a dashed box.](e9314c83043183351ed74908e9bf2f90_img.jpg)
+
+```
+
+    {apiRoot}/nsmf-nidd/<apiVersion>
+    |
+    +-- /pdu-sessions
+    |
+    +-- /{pduSessionRef}
+    |
+    +-- /deliver
+  
+```
+
+Figure 6.1.3.1-1: Resource URI structure of the Nsmf\_NIDD API. The diagram shows a hierarchical tree structure of URI paths. The root is {apiRoot}/nsmf-nidd/. It branches to /pdu-sessions, which branches to /{pduSessionRef}, which finally branches to /deliver. The /deliver path is enclosed in a dashed box.
+
+**Figure 6.1.3.1-1: Resource URI structure of the Nsmf\_NIDD 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 name          | Resource URI                          | HTTP method or custom operation | Description                |
+|------------------------|---------------------------------------|---------------------------------|----------------------------|
+| Individual PDU session | /pdu-sessions/{pduSessionRef}/deliver | deliver (POST)                  | Delivery Service Operation |
+
+#### 6.1.3.2 Resource: Individual PDU session
+
+##### 6.1.3.2.1 Description
+
+This resource represents an individual PDU session created in SMF for NIDD.
+
+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}/nsmf-nidd/<apiVersion>/pdu-sessions/{pduSessionRef}
+
+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          | Definition                                                                    |
+|---------------|-------------------------------------------------------------------------------|
+| apiRoot       | See clause 6.1.1                                                              |
+| apiVersion    | See clause 6.1.1                                                              |
+| pduSessionRef | PDU session reference assigned by the SMF during SMF-NEF Connection creation. |
+
+##### 6.1.3.2.3 Resource Standard Methods
+
+None.
+
+##### 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**
+
+| Custom operation URI  | Mapped HTTP method | Description                 |
+|-----------------------|--------------------|-----------------------------|
+| {resourceUri}/deliver | POST               | Delivery service operation. |
+
+###### 6.1.3.2.4.2 Operation: deliver
+
+###### 6.1.3.2.4.2.1 Description
+
+This custom operation enables to deliver NEF anchored MT data for a given PDU session towards the SMF.
+
+###### 6.1.3.2.4.2.2 Operation Definition
+
+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                                        |
+|----------------|---|-------------|----------------------------------------------------|
+| DeliverReqData | M | 1           | Representation of the payload of a Deliver Request |
+
+**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                                                                                                                                                                                                                                                                                                |
+|------------------|---|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| n/a              |   |             | 204 No Content         | Successful delivery of MT data.                                                                                                                                                                                                                                                                            |
+| RedirectResponse | O | 0..1        | 307 Temporary Redirect | Temporary redirection.<br>(NOTE 2)                                                                                                                                                                                                                                                                         |
+| RedirectResponse | O | 0..1        | 308 Permanent Redirect | Permanent redirection.<br>(NOTE 2)                                                                                                                                                                                                                                                                         |
+| DeliverError     | O | 0..1        | 504 Gateway Timeout    | The "cause" attribute may be used to indicate the following application errors:<br>- UE_NOT_REACHABLE, if the UE is not reachable to deliver the mobile terminated data; if Estimated Maximum Waiting Time shall be included if available;<br><br>See table 6.1.7.3-1 for the description of these errors. |
+
+NOTE 1: The mandatory HTTP error status codes for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] other than those specified in the table above also apply, with a ProblemDetails data type when needed (see clause 5.2.7 of 3GPP TS 29.500 [4]).
+
+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.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 SMF or SMF (service) set. 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 SMF or SMF (service) set. 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
+
+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 Nsmf\_NIDD service based interface protocol.
+
+**Table 6.1.6.1-1: Nsmf\_NIDD specific Data Types**
+
+| Data type      | Clause defined | Description                                   | Applicability |
+|----------------|----------------|-----------------------------------------------|---------------|
+| DeliverReqData | 6.1.6.2.2      | Information within Deliver Request            |               |
+| DeliverAddInfo | 6.1.6.2.3      | Deliver Error Response Additional Information |               |
+| DeliverError   | 6.1.6.4.1      | Deliver Error Response                        |               |
+
+Table 6.1.6.1-2 specifies data types re-used by the N<sub><NF></sub> 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 N<sub><NF></sub> service based interface.
+
+**Table 6.1.6.1-2: Nsmf\_NIDD re-used Data Types**
+
+| Data type        | Reference           | Comments                                                                                       | Applicability |
+|------------------|---------------------|------------------------------------------------------------------------------------------------|---------------|
+| RefToBinaryData  | 3GPP TS 29.571 [15] | Cross-Reference to binary data encoded within a binary body part in an HTTP multipart message. |               |
+| ProblemDetails   | 3GPP TS 29.571 [15] | Error description                                                                              |               |
+| DurationSec      | 3GPP TS 29.571 [15] | Duration in units of seconds                                                                   |               |
+| RedirectResponse | 3GPP TS 29.571 [15] | Redirect Response                                                                              |               |
+
+#### 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: DeliverReqData
+
+**Table 6.1.6.2.2-1: Definition of type DeliverReqData**
+
+| Attribute name | Data type       | P | Cardinality | Description                                                                | Applicability |
+|----------------|-----------------|---|-------------|----------------------------------------------------------------------------|---------------|
+| mtData         | RefToBinaryData | M | 1           | This IE shall reference the Mobile Terminated Data (see clause 6.1.6.5.1). |               |
+
+##### 6.1.6.2.3 Type: DeliverAddInfo
+
+**Table 6.1.6.2.3-1: Definition of type DeliverAddInfo**
+
+| Attribute name | Data type   | P | Cardinality | Description                                                                                   | Applicability |
+|----------------|-------------|---|-------------|-----------------------------------------------------------------------------------------------|---------------|
+| maxWaitingTime | DurationSec | C | 0..1        | This IE shall contain the estimated maximum wait time (see clause 4.25.5 of 3GPP 23.502 [3]). |               |
+
+#### 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
+
+##### 6.1.6.4.1 Type: DeliverError
+
+**Table 6.1.6.4.1-1: Definition of type DeliverError as a list of "to be combined data types"**
+
+| Data type      | Cardinality | Description                                              | Applicability |
+|----------------|-------------|----------------------------------------------------------|---------------|
+| ProblemDetails | 1           | Detail information of the problem                        |               |
+| DeliverAddInfo | 1           | Additional information to be returned in error response. |               |
+
+#### 6.1.6.5 Binary data
+
+##### 6.1.6.5.1 Mobile Terminated Data
+
+Mobile Terminated Data shall encode the Data Contents of the Payload Container specified in 3GPP TS 24.501 [7], using the vnd.3gpp.5gnas content-type, as summarized in Table 6.1.6.5.1-1.
+
+**Table 6.1.6.5.1-1: Mobile Terminated Data**
+
+| Mobile Terminated Data                      | Reference<br>(3GPP TS 24.501 [7]) | Related NAS SM message |
+|---------------------------------------------|-----------------------------------|------------------------|
+| Payload container contents in octets 4 to n | 9.11.3.39                         | DL NAS Transport       |
+
+### 6.1.7 Error Handling
+
+#### 6.1.7.1 General
+
+For the Nsmf\_NIDD 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 Nsmf\_NIDD API.
+
+#### 6.1.7.2 Protocol Errors
+
+No specific procedures for the Nsmf\_NIDD service are specified.
+
+#### 6.1.7.3 Application Errors
+
+The common application errors defined in Table 5.2.7.2-1 of 3GPP TS 29.500 [4] may be used for the Nsmf\_NIDD service.
+
+The application errors defined for the Nsmf\_NIDD service are listed in Table 6.1.7.3-1.
+
+**Table 6.1.7.3-1: Application errors**
+
+| Application Error | HTTP status code    | Description                              |
+|-------------------|---------------------|------------------------------------------|
+| UE_NOT_REACHABLE  | 504 Gateway Timeout | The UE is not reachable for the service. |
+
+### 6.1.8 Feature negotiation
+
+The optional features in table 6.1.8-1 are defined for the Nsmf\_NIDD 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 Nsmf\_NIDD 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 Nsmf\_NIDD 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 Nsmf\_NIDD service.
+
+The Nsmf\_NIDD API defines scopes for OAuth2 authorization as specified in 3GPP TS 33.501 [15]; it defines a single scope consisting on the name of the service (i.e., "nsmf-nidd"), 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 SMF service instance, within the same SMF or a different SMF of an SMF set, e.g. when an SMF service instance is part of an SMF (service) set or when using indirect communications (see 3GPP TS 29.500 [4]).
+
+An SCP that reselects a different SMF producer instance will return the NF Instance ID of the new SMF 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 SMF within an SMF set redirects a service request to a different SMF of the set using an 307 Temporary Redirect or 308 Permanent Redirect status code, the identity of the new SMF 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 Nsmf\_NIDD Service API. It consists of OpenAPI 3.0.0 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 3GPP TS 29.501 [5] clause 5.3.1 and 3GPP TR 21.900 [7] clause 5B).
+
+## --- A.2 Nsmf\_NIDD API
+
+```
+openapi: 3.0.0
+
+info:
+  version: '1.2.0-alpha.1'
+  title: 'Nsmf_NIDD'
+  description: |
+    SMF NIDD Service.
+    © 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+    All rights reserved.
+
+externalDocs:
+  description: 3GPP TS 29.542 V18.0.0; 5G System; Session Management Services for Non-IP Data
+    Delivery (NIDD); Stage 3
+  url: https://www.3gpp.org/ftp/Specs/archive/29_series/29.542/
+
+servers:
+  - url: '{apiRoot}/nsmf-nidd/v1'
+    variables:
+      apiRoot:
+        default: https://example.com
+        description: apiRoot as defined in clause 4.4 of 3GPP TS 29.501.
+
+security:
+  - {}
+  - oAuth2ClientCredentials:
+    - nsmf-nidd
+
+paths:
+  '/pdu-sessions/{pduSessionRef}/deliver':
+    post:
+      summary: Delivery Service Operation
+      tags:
+        - Individual PDU session
+      operationId: Deliver
+      parameters:
+        - name: pduSessionRef
+          in: path
+          description: PDU session reference
+          required: true
+          schema:
+            type: string
+      requestBody:
+        description: representation of the payload of Deliver Request
+        required: true
+        content:
+```
+
+```
+
+    multipart/related: # message with a binary body part
+      schema:
+        type: object
+        properties:
+          jsonData:
+            $ref: '#/components/schemas/DeliverReqData'
+          binaryMtData:
+            type: string
+            format: binary
+          encoding:
+            jsonData:
+              contentType: application/json
+            binaryMtData:
+              contentType: application/vnd.3gpp.5gnas
+          headers:
+            Content-Id:
+              schema:
+                type: string
+  responses:
+    '204':
+      description: successful transfering of Delivery
+    '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'
+    '503':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/503'
+    '504':
+      description: unsuccessful delivery of mobile terminated data - gateway timeout
+      content:
+        application/json:
+          schema:
+            $ref: '#/components/schemas/DeliverError'
+  default:
+    $ref: 'TS29571_CommonData.yaml#/components/responses/default'
+
+components:
+  securitySchemes:
+    oAuth2ClientCredentials:
+      type: oauth2
+      flows:
+        clientCredentials:
+          tokenUrl: '{nrfApiRoot}/oauth2/token'
+          scopes:
+            nsmf-nidd: Access to the nsmf-nidd API
+
+schemas:
+#
+# STRUCTURED DATA TYPES
+#
+
+DeliverReqData:
+  description: Representation of the payload of a Deliver Request.
+  type: object
+  properties:
+    mtData:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/RefToBinaryData'
+  required:
+
+```
+
+- mtData
+
+DeliverAddInfo:  
+description: Additional information in an error response to a Deliver Request.  
+type: object  
+properties:  
+ maxWaitingTime:  
+ \$ref: 'TS29571\_CommonData.yaml#/components/schemas/DurationSec'
+
+#
+
+# DATA TYPES DESCRIBING ALTERNATIVE OR COMBINATION OF DATA TYPES
+
+#
+
+DeliverError:  
+description: Representation of the payload in an error response to a Deliver Request.  
+allOf:  
+ - \$ref: 'TS29571\_CommonData.yaml#/components/schemas/ProblemDetails'  
+ - \$ref: '#/components/schemas/DeliverAddInfo'
+
+# Annex B (informative): Change history
+
+| Change history |          |           |      |     |     |                                                     |  |             |
+|----------------|----------|-----------|------|-----|-----|-----------------------------------------------------|--|-------------|
+| Date           | Meeting  | TDoc      | CR   | Rev | Cat | Subject/Comment                                     |  | New version |
+| 2020-03        | CT4#96-e | C4-201267 |      |     |     | Initial Draft.                                      |  | 0.1.0       |
+| 2020-03        | CT#87e   | CP-200093 |      |     |     | Presented for information and approval              |  | 1.0.0       |
+| 2020-03        | CT#87e   |           |      |     |     | Approved at CT#87e                                  |  | 16.0.0      |
+| 2020-06        | CT#88e   | CP-201071 | 0001 | 2   | F   | Storage of YAML files in ETSI Forge                 |  | 16.1.0      |
+| 2020-06        | CT#88e   | CP-201046 | 0003 |     | F   | Miscellaneous Corrections                           |  | 16.1.0      |
+| 2020-06        | CT#88e   | CP-201073 | 0004 |     | F   | 29.542 Rel-16 API version and External doc update   |  | 16.1.0      |
+| 2020-09        | CT#89e   | CP-202105 | 0005 |     | F   | Optionality of DeliverError                         |  | 16.2.0      |
+| 2020-12        | CT#90e   | CP-203032 | 0007 |     | F   | YAML files in 3GPP Forge                            |  | 16.3.0      |
+| 2021-03        | CT#91e   | CP-210037 | 0010 | 1   | F   | HTTP 3xx redirection                                |  | 17.0.0      |
+| 2021-03        | CT#91e   | CP-210034 | 0011 | 1   | F   | OpenAPI Reference                                   |  | 17.0.0      |
+| 2021-03        | CT#91e   | CP-210054 | 0013 | -   | F   | 29.542 Rel-16 API version and External doc update   |  | 17.0.0      |
+| 2021-06        | CT#92e   | CP-210050 | 0014 | 1   | F   | Resolving Warning in Nsmf_NIDD API                  |  | 17.1.0      |
+| 2021-06        | CT#92e   | CP-210050 | 0017 | 1   | A   | Redirect Response                                   |  | 17.1.0      |
+| 2021-06        | CT#92e   | CP-210050 | 0018 |     | F   | 29.542 Rel-17 API version and External doc update   |  | 17.1.0      |
+| 2021-09        | CT#93e   | CP-212060 | 0021 | -   | A   | 3xx description correction for SCP                  |  | 17.2.0      |
+| 2022-03        | CT#95e   | CP-220025 | 0025 | 1   | F   | SMF reference model update                          |  | 17.3.0      |
+| 2022-06        | CT#96    | CP-221051 | 0027 |     | F   | 29.542 Rel-17 API version and External doc update   |  | 17.4.0      |
+| 2022-12        | CT#98    | CP-223028 | 0029 | 1   | F   | Missing Mandatory Status Codes in OpenAPI           |  | 18.0.0      |
+| 2022-12        | CT#98    | CP-223033 | 0030 |     | F   | 29.542 Rel-18 API version and External doc update   |  | 18.0.0      |
+| 2023-06        | CT#100   | CP-231028 | 0031 | 3   | F   | Location header description                         |  | 18.1.0      |
+| 2023-09        | CT#101   | CP-232063 | 0035 | 1   | F   | Update on the references                            |  | 18.2.0      |
+| 2023-12        | CT#102   | CP-233029 | 0036 | 1   | F   | HTTP RFCs obsoleted by IETF RFC 9110, 9111 and 9113 |  | 18.3.0      |
+| 2023-12        | CT#102   | CP-233030 | 0037 |     | F   | ProblemDetails RFC 7807 obsoleted by 9457           |  | 18.3.0      |

marked/Rel-18/29_series/29544/raw.md

@@ -0,0 +1,767 @@
+
+
+# 3GPP TS 29.544 V18.1.0 (2023-12)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Secured Packet Application Function (SP-AF) 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 Terms.....                                             | 8  |
+| 3.2 Symbols.....                                           | 8  |
+| 3.3 Abbreviations .....                                    | 8  |
+| 4 Overview.....                                            | 8  |
+| 4.1 Introduction .....                                     | 8  |
+| 5 Services offered by the SP-AF.....                       | 9  |
+| 5.1 Introduction .....                                     | 9  |
+| 5.2 Nspaf_SecuredPacket Service.....                       | 9  |
+| 5.2.1 Service Description .....                            | 9  |
+| 5.2.2 Service Operations.....                              | 9  |
+| 5.2.2.1 Introduction.....                                  | 9  |
+| 5.2.2.2 Provide .....                                      | 9  |
+| 5.2.2.2.1 General .....                                    | 9  |
+| 5.2.2.2.2 Secured Packet Retrieval.....                    | 9  |
+| 6 API Definitions .....                                    | 10 |
+| 6.1 Nspaf_SecuredPacket 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.....                         | 11 |
+| 6.1.2.2.1 General .....                                    | 11 |
+| 6.1.2.2.2 Content type .....                               | 11 |
+| 6.1.2.3 HTTP custom headers.....                           | 11 |
+| 6.1.3 Resources.....                                       | 11 |
+| 6.1.3.1 Overview.....                                      | 11 |
+| 6.1.3.2 Resource: SecuredPacket.....                       | 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.....                  | 12 |
+| 6.1.3.2.4.2.1 Description.....                             | 12 |
+| 6.1.3.2.4.2.2 Operation Definition .....                   | 12 |
+| 6.1.4 Custom Operations without associated resources ..... | 13 |
+| 6.1.5 Notifications .....                                  | 13 |
+| 6.1.6 Data Model .....                                     | 13 |
+| 6.1.6.1 General.....                                       | 13 |
+| 6.1.6.2 Structured data types.....                         | 13 |
+| 6.1.6.2.1 Introduction .....                               | 13 |
+| 6.1.6.2.2 Type: UiccConfigurationParameter .....           | 14 |
+| 6.1.6.2.3 Type: ExtendedSteeringContainer .....            | 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.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 Nspaf\_SecuredPacket API..... 16  
+**Annex B (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 Nspaf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the SP-AF.
+
+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].
+
+# --- 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 29.503: "Unified Data Management Services"; Stage 3.
+- [15] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces Stage 3".
+- [16] 3GPP TS 31.115: "Secured packet structure for (Universal) Subscriber Identity Module (U)SIM Toolkit applications".
+- [17] 3GPP TS 29.509: "Authentication Server Services; Stage 3".
+- [18] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)"
+- [19] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
+
+# 3 Definitions, symbols and abbreviations
+
+## 3.1 Terms
+
+Void.
+
+## 3.2 Symbols
+
+Void.
+
+## 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].
+
+|        |                                          |
+|--------|------------------------------------------|
+| OTA    | Over The Air                             |
+| SOR-AF | Steering Of Roaming Application Function |
+| SP-AF  | Secured Packet Application Function      |
+| UDM    | Unified Data Management                  |
+
+# 4 Overview
+
+## 4.1 Introduction
+
+Within the 5GC, the SP-AF offers services to the UDM and to the SOR-AF via the Nspaf service based interface.
+
+The UDM or SOR-AF shall make use of the SP-AF services when it needs to protect UE parameters for which the final consumer is the USIM (see 3GPP TS 33.501 [8] clause 6.15.2.1).
+
+Figure 4.1-1 provides the reference model with focus on the SP-AF.
+
+NOTE: The generation of the secured packet and the definition of the storage and handling of OTA keys or other sensitive data are out of scope of this document. For more details, refer to 3GPP TS 23.040 [18] and 3GPP TS 31.115 [16].
+
+![Reference model diagram showing UDM and SOR-AF connected to SP-AF via the Nspaf interface.](6078636a87fbe0e699aab4a6fddd15d7_img.jpg)
+
+The diagram illustrates the reference model for the SP-AF. On the left, there are two rectangular boxes labeled 'UDM' and 'SOR-AF'. Lines from both boxes converge to a single point labeled 'Nspaf'. From this point, a line connects to a large green rectangular box on the right labeled 'SP-AF'.
+
+Reference model diagram showing UDM and SOR-AF connected to SP-AF via the Nspaf interface.
+
+Figure 4.1-1: Reference model – SP-AF
+
+# 5 Services offered by the SP-AF
+
+## 5.1 Introduction
+
+The SP-AF offers the following services via the Nspaf interface:
+
+- Nspaf\_SecuredPacket 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 |
+|---------------------|--------|------------------------------|-----------------------------------|----------------------|-------|
+| Nspaf_SecuredPacket | 6.1    | Nspaf Secured Packet Service | TS29544_Nspaf_SecuredPacket .yaml | nspaf-secured-packet | A.2   |
+
+## 5.2 Nspaf\_SecuredPacket Service
+
+### 5.2.1 Service Description
+
+The Nspaf\_SecuredPacket Service may be consumed by the NF consumer (e.g. UDM or SOR-AF) when it has detected that a UICC configuration parameter (e.g. Routing ID data or Steering of Roaming information) needs to be updated, and the new value is not available in secured packet format.
+
+For the list of service operations see clause 5.2.2.1
+
+### 5.2.2 Service Operations
+
+#### 5.2.2.1 Introduction
+
+For the Nspaf\_SecuredPacket service the following service operations are defined:
+
+- Provide
+
+The Nspaf\_SecuredPacket Service is used by Consumer NFs (e.g. UDM or SOR-AF) to request the SP-AF to provide a secured packet that contains an UICC configuration parameter as sent in the request by means of the Provide service operation
+
+#### 5.2.2.2 Provide
+
+##### 5.2.2.2.1 General
+
+This service operation is used by the NF Service Consumer (e.g. UDM or SOR-AF) to request construction of a secured packet that contains the provided UICC configuration information (e.g. Routing Indicator or Steering of Roaming information).
+
+The following procedures using the Provide service operation are supported:
+
+- Secured Packet Retrieval
+
+##### 5.2.2.2.2 Secured Packet Retrieval
+
+Figure 5.2.2.2.2-1 shows a scenario where the NF consumer (e.g. UDM or SOR-AF) sends a request to the SP-AF to provide a secured packet.
+
+The request contains the UE's identity (/{supi}) and the UICC configuration parameter.
+
+![Sequence diagram showing the interaction between an NF-consumer and an SP-AF. The NF-consumer sends a POST request to the SP-AF. The SP-AF responds with either a 200 OK (SecuredPacket) or a 404 Not Found.](e6df2733626a85205c1db682e6259c46_img.jpg)
+
+```
+
+sequenceDiagram
+    participant NF-consumer
+    participant SP-AF
+    Note right of NF-consumer: 1. POST.../{supi}/provide-secured-packet (UiccConfigurationParameter)
+    NF-consumer->>SP-AF: Request
+    Note left of SP-AF: 2a. 200 OK (SecuredPacket)
+    SP-AF-->>NF-consumer: Response 2a
+    Note left of SP-AF: 2b. 404 Not Found
+    SP-AF-->>NF-consumer: Response 2b
+  
+```
+
+Sequence diagram showing the interaction between an NF-consumer and an SP-AF. The NF-consumer sends a POST request to the SP-AF. The SP-AF responds with either a 200 OK (SecuredPacket) or a 404 Not Found.
+
+**Figure 5.2.2.2.2-1: NF consumer requests the SP-AF to provide a secured packet**
+
+1. The NF consumer sends a POST request (custom method: provide-secured-packet) to the resource representing the SUPI.
+- 2a. On success, the SP-AF responds with "200 OK", containing the requested SecuredPacket.
+- 2b. If the resource does not exist (the supi is unknown in the SP-AF), the SP-AF returns the HTTP status code "404 Not Found", and additional error information should be included in the response body (in "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 POST response body.
+
+# 6 API Definitions
+
+## 6.1 Nspaf\_SecuredPacket Service API
+
+### 6.1.1 Introduction
+
+The Nspaf\_SecuredPacket service shall use the Nspaf\_SecuredPacket API.
+
+The request URI used in HTTP request from the NF service consumer towards the NF service producer shall have the 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 "nspaf-secured-packet".
+- 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 Nspaf\_SecuredPacket 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 applicable.
+
+### 6.1.3 Resources
+
+#### 6.1.3.1 Overview
+
+![Diagram showing the hierarchical structure of the nspaf-secured-packet API URI. The root is {apiRoot}/nspaf-secured-packet/<apiVersion>. It branches to /{supi}, which in turn branches to /provide-secured-packet (indicated by a dashed box).](ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg)
+
+```
+
+graph TD
+    Root["{apiRoot}/nspaf-secured-packet/<apiVersion>"] --> Supi["/{supi}"]
+    Supi --> Packet["/provide-secured-packet"]
+    style Packet stroke-dasharray: 5 5
+  
+```
+
+Diagram showing the hierarchical structure of the nspaf-secured-packet API URI. The root is {apiRoot}/nspaf-secured-packet/. It branches to /{supi}, which in turn branches to /provide-secured-packet (indicated by a dashed box).
+
+**Figure 6.1.3.1-1: Resource URI structure of the nspaf-secured-packet 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 name                    | Resource URI                   | HTTP method or custom operation | Description                                                                                |
+|----------------------------------|--------------------------------|---------------------------------|--------------------------------------------------------------------------------------------|
+| SecuredPacket (Custom operation) | /{supi}/provide-secured-packet | Provide-secured-packet (POST)   | The SP-AF generates a secured packet containing the presented UICC configuration parameter |
+
+#### 6.1.3.2 Resource: SecuredPacket
+
+##### 6.1.3.2.1 Description
+
+This resource represents the information that is needed to construct secured packets for the SUPI.
+
+##### 6.1.3.2.2 Resource Definition
+
+Resource URI: {apiRoot}/nspaf-secured-packet/v1/{supi}/provide-secured-packet
+
+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    | Definition                                                                                                                           |
+|---------|--------------------------------------------------------------------------------------------------------------------------------------|
+| apiRoot | See clause 6.1.1                                                                                                                     |
+| supi    | Represents the Subscription Permanent Identifier (see 3GPP TS 23.501 [2] clause 5.9.2)<br>pattern: "^(imsi-[0-9]{5,15} nai-.[+.]\$)" |
+
+##### 6.1.3.2.3 Resource Standard Methods
+
+No Standard Methods are supported for this 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**
+
+| Custom operation URI    | Mapped HTTP method | Description                                                                                                 |
+|-------------------------|--------------------|-------------------------------------------------------------------------------------------------------------|
+| /provide-secured-packet | POST               | The SP-AF generates a secured packet for the SUPI that contains the presented UICC configuration parameter. |
+
+###### 6.1.3.2.4.2 Operation: provide-secured-packet
+
+###### 6.1.3.2.4.2.1 Description
+
+This custom operation is used by the NF service consumer (e.g. UDM) to request a secured packet for the SUPI containing the presented UICC configuration parameter. The returned secured packet shall be constructed as an SMS-Deliver as specified in 3GPP TS 23.040 [18] and protected as specified in 3GPP TS 31.115 [16].
+
+###### 6.1.3.2.4.2.2 Operation Definition
+
+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                                              |
+|-----------------------------|---|-------------|----------------------------------------------------------|
+| UiccConfiguration Parameter | M | 1           | Contains the parameter that is to be updated in the UICC |
+
+**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                                                                                      |
+|----------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|--------------------------------------------------------------------------------------------------|
+| SecuredPacket                                                                                                              | M | 1           | 200 OK         | Upon success, a response body containing the generated secured packet shall be returned.         |
+| ProblemDetails                                                                                                             | O | 0..1        | 404 Not Found  | The "cause" attribute may be used to convey the following application error:<br>- USER NOT FOUND |
+| 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. |   |             |                |                                                                                                  |
+
+### 6.1.4 Custom Operations without associated resources
+
+In this release of this specification, no custom operations without associated resources are defined for the Nspaf\_SecuredPacket Service.
+
+### 6.1.5 Notifications
+
+In this release of this specification, no notifications are defined for the Nspaf\_SecuredPacket Service.
+
+### 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 Nspaf service based interface protocol.
+
+**Table 6.1.6.1-1: Nspaf specific Data Types**
+
+| Data type                  | Clause defined | Description                                                                             | Applicability |
+|----------------------------|----------------|-----------------------------------------------------------------------------------------|---------------|
+| UiccConfigurationParameter | 6.1.6.2.2      | UICC Configuration Parameters                                                           |               |
+| RoutingId                  | 6.1.6.3.2      | Routing ID                                                                              |               |
+| ExtendedSteeringContainer  | 6.1.6.2.3      | Extended Steering Container (including the contents of Steering Container and SOR-CMCI) |               |
+
+Table 6.1.6.1-2 specifies data types re-used by the Nspaf 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 Nspaf service based interface.
+
+**Table 6.1.6.1-2: Nspaf re-used Data Types**
+
+| Data type      | Reference           | Comments                                            | Applicability |
+|----------------|---------------------|-----------------------------------------------------|---------------|
+| SecuredPacket  | 3GPP TS 29.503 [14] | Secured Packet                                      |               |
+| ProblemDetails | 3GPP TS 29.571 [15] |                                                     |               |
+| SteeringInfo   | 3GPP TS 29.509 [17] | Steering Information                                |               |
+| SorCmci        | 3GPP TS 29.503 [14] | Contains SOR-CMCI as defined in 3GPP TS 24.501 [19] |               |
+
+#### 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: UiccConfigurationParameter
+
+Table 6.1.6.2.2-1: Definition of type UiccConfigurationParameter
+
+| Attribute name            | Data type                 | P | Cardinality | Description                                                                                                                                  | Applicability |
+|---------------------------|---------------------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| routingId                 | RoutingId                 | C | 0..1        | The Routing Id that needs to be updated in the USIM.                                                                                         |               |
+| steeringContainer         | array(SteeringInfo)       | C | 1..N        | List of PLMN/AccessTechnologies combinations that need to be updated in the USIM.                                                            |               |
+| extendedSteeringContainer | ExtendedSteeringContainer | C | 0..1        | Extended Steering Container that includes list of PLMN/AccessTechnologies combinations with the SOR-CMCI that need to be updated in the USIM |               |
+
+Note: Exactly one attribute shall be present
+
+##### 6.1.6.2.3 Type: ExtendedSteeringContainer
+
+Table 6.1.6.2.3-1: Definition of type ExtendedSteeringContainer
+
+| Attribute name    | Data type           | P | Cardinality | Description                                                                                                                                                                                                                                                                                                        | Applicability |
+|-------------------|---------------------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| steeringContainer | array(SteeringInfo) | C | 1..N        | List of PLMN/AccessTechnologies combinations that need to be updated in the USIM.                                                                                                                                                                                                                                  |               |
+| sorCmci           | SorCmci             | C | 0..1        | When present, provides the SOR-CMCI values as defined in 3GPP TS 24.501 [19]                                                                                                                                                                                                                                       |               |
+| storeSorCmciInMe  | boolean             | C | 0..1        | When present, indicates "Store the SOR-CMCI in the ME", i.e. whether to instruct UE to store SOR-CMCI in the ME as defined in 3GPP TS 23.122 [14] and 3GPP TS 24.501 [27].<br><br>- True: Indicates to store the SOR-CMCI in the ME<br>- False or absent: Indicates storing the SOR-CMCI in the ME is not required |               |
+
+NOTE: At least one attribute shall be present. If no additional attributes than steeringContainer is included, then use of steeringContainer can be considered instead of using ExtendedSteeringContainer.
+
+#### 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 |
+|-----------|-----------------|-------------------------|---------------|
+| RoutingId | string          | Pattern: "[0-9]{1,4}\$" |               |
+
+### 6.1.7 Error Handling
+
+#### 6.1.7.1 General
+
+For the Nspaf\_SecuredPacket 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 Nspaf\_SecuredPacket API.
+
+#### 6.1.7.2 Protocol Errors
+
+No specific procedures for the Nspaf\_SecuredPacket service are specified.
+
+#### 6.1.7.3 Application Errors
+
+The application errors defined for the Nspaf\_SecuredPacket service are listed in Table 6.1.7.3-1.
+
+**Table 6.1.7.3-1: Application errors**
+
+| Application Error | HTTP status code | Description             |
+|-------------------|------------------|-------------------------|
+| USER_NOT_FOUND    | 404 Not Found    | The user does not exist |
+
+### 6.1.8 Feature negotiation
+
+The optional features in table 6.1.8-1 are defined for the Nspaf\_SecuredPacket 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 Nspaf\_SecuredPacket 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 Nspaf\_SecuredPacket 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 Nspaf\_SecuredPacket service.
+
+The Nspaf\_SecuredPacket API defines a single scope "nspaf-secured-packet" 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 3.0.0 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 3GPP TS 29.501 [5] clause 5.3.1 and 3GPP TR 21.900 [7] clause 5B).
+
+## A.2 Nspaf\_SecuredPacket API
+
+```
+openapi: 3.0.0
+info:
+  title: 'Nspaf_SecuredPacket'
+  version: '1.2.0-alpha.1'
+  description: |
+    Nspaf Secured Packet Service.
+    © 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+    All rights reserved.
+externalDocs:
+  description: 3GPP TS 29.544, SP-AF Services, version V18.0.0
+  url: https://www.3gpp.org/ftp/Specs/archive/29_series/29.544/
+servers:
+  - url: '{apiRoot}/nspaf-secured-packet/v1'
+    variables:
+      apiRoot:
+        default: https://example.com
+        description: apiRoot as defined in clause 4.4 of 3GPP TS 29.501
+security:
+  - {}
+  - oAuth2ClientCredentials:
+    - nspaf-secured-packet
+paths:
+  /{supi}/provide-secured-packet:
+    post:
+      summary: request generation of a secured packet
+      operationId: ProvideSecuredPacket
+      tags:
+        - SecuredPacket Generation (Custom Operation)
+      parameters:
+        - name: supi
+          in: path
+          description: SUPI of the user
+          required: true
+          schema:
+            $ref: 'TS29571_CommonData.yaml#/components/schemas/Supi'
+      requestBody:
+        required: true
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/UiccConfigurationParameter'
+      responses:
+        '200':
+          description: Success
+          content:
+```
+
+```
+
+    application/json:
+      schema:
+        $ref: 'TS29503_Nudm_SDM.yaml#/components/schemas/SecuredPacket'
+  '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'
+  '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:
+            nspaf-secured-packet: Access to the nspaf-secured-packet API
+  schemas:
+
+# COMPLEX TYPES:
+
+UiccConfigurationParameter:
+  description: Represents UICC Configuration Parameters.
+  type: object
+  oneOf:
+    - required: [routingId ]
+    - required: [steeringContainer ]
+    - required: [extendedSteeringContainer ]
+  properties:
+    routingId:
+      $ref: '#/components/schemas/RoutingId'
+    steeringContainer:
+      type: array
+      items:
+        $ref: 'TS29509_Nausf_SoRProtection.yaml#/components/schemas/SteeringInfo'
+      minItems: 1
+    extendedSteeringContainer:
+      $ref: '#/components/schemas/ExtendedSteeringContainer'
+
+ExtendedSteeringContainer:
+  description: Represents Extended Steering Containers.
+  type: object
+  properties:
+    steeringContainer:
+      type: array
+      items:
+        $ref: 'TS29509_Nausf_SoRProtection.yaml#/components/schemas/SteeringInfo'
+      minItems: 1
+    sorCmci:
+      $ref: 'TS29503_Nudm_SDM.yaml#/components/schemas/SorCmci'
+    storeSorCmciInMe:
+      type: boolean
+
+# SIMPLE TYPES:
+
+RoutingId:
+  description: Represents a routing indicator.
+  type: string
+
+```
+
+pattern: '^[0-9]{1,4}\$'
+
+# ENUMS:
+
+# Annex B (informative): Change history
+
+| Change history |         |           |      |     |     |                                                                                                                               |             |
+|----------------|---------|-----------|------|-----|-----|-------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date           | Meeting | TDoc      | CR   | Rev | Cat | Subject/Comment                                                                                                               | New version |
+| 2019-10        | CT4#94  | C4-194013 |      |     |     | Initial Draft.                                                                                                                | 0.1.0       |
+| 2019-10        | CT4#94  | C4-194367 |      |     |     | Notaf Overview                                                                                                                | 0.2.0       |
+| 2019-10        | CT4#94  | C4-194488 |      |     |     | Notaf_SecuredPacket-Provide service operation                                                                                 | 0.2.0       |
+| 2019-10        | CT4#94  | C4-194492 |      |     |     | Resources                                                                                                                     | 0.2.0       |
+| 2019-10        | CT4#94  | C4-194516 |      |     |     | Data Model                                                                                                                    | 0.2.0       |
+| 2019-10        | CT4#94  | C4-194490 |      |     |     | OpenAPI Specification                                                                                                         | 0.2.0       |
+| 2019-11        | CT4#95  | C4-195481 |      |     |     | Clean Up                                                                                                                      | 0.3.0       |
+| 2019-12        | CT#86   | CP-193071 |      |     |     | TS presented for information                                                                                                  | 1.0.0       |
+| 2019-12        | CT#86   | CP-193285 |      |     |     | A title updated                                                                                                               | 1.0.1       |
+| 2020-03        | CT4#96e | C4-201119 |      |     |     | Pseudo-CR on SOR                                                                                                              | 1.1.0       |
+| 2020-03        | CT4#96e | C4-201123 |      |     |     | Pseudo-CR on Clean Up                                                                                                         | 1.1.0       |
+| 2020-03        | CT4#96e | C4-201217 |      |     |     | Pseudo-CR on the necessary modifications to change OTAF NF name to SP-AF                                                      | 1.1.0       |
+| 2020-03        | CT4#96e | C4-201314 |      |     |     | Pseudo-CR on API descriptions table in clause 5.1                                                                             | 1.1.0       |
+| 2020-03        | CT#87e  | CP-200062 |      |     |     | TS presented for approval                                                                                                     | 2.0.0       |
+| 2020-03        | CT#87e  |           |      |     |     | Approved at CT#87e                                                                                                            | 16.0.0      |
+| 2020-07        | CT#88e  | CP-201040 | 0001 | 1   | C   | Clarification on Secured Packet format provided by SP-AF                                                                      | 16.1.0      |
+| 2020-07        | CT#88e  | CP-201040 | 0002 |     | F   | Storage of YAML files in ETSI Forge                                                                                           | 16.1.0      |
+| 2020-07        | CT#88e  | CP-201040 | 0003 | 1   | F   | Miscellaneous Corrections                                                                                                     | 16.1.0      |
+| 2020-07        | CT#88e  | CP-201073 | 0005 |     | F   | 3GPP TS 29.544 API Version and External doc Update                                                                            | 16.1.0      |
+| 2020-09        | CT#89e  | CP-202110 | 0006 | 1   | F   | Miscellaneous corrections                                                                                                     | 16.2.0      |
+| 2020-09        | CT#89e  | CP-202096 | 0007 |     | F   | API version and External doc update                                                                                           | 16.2.0      |
+| 2020-12        | CT#90e  | CP-203048 | 0008 |     | F   | Storage of yaml files                                                                                                         | 16.3.0      |
+| 2021-06        | CT#92e  | CP-211051 | 0011 |     | F   | OpenAPI Reference                                                                                                             | 17.0.0      |
+| 2021-06        | CT#92e  | CP-211028 | 0012 | 1   | F   | Adding some missing description fields to data type definitions in OpenAPI specification files of the Nspaf_SecuredPacket API | 17.0.0      |
+| 2021-06        | CT#92e  | CP-211050 | 0013 |     | F   | 29.544 Rel-17 API version and External doc update                                                                             | 17.0.0      |
+| 2021-12        | CT#94e  | CP-213197 | 0014 | 2   | B   | SOR-CMCI support                                                                                                              | 17.1.0      |
+| 2021-12        | CT#94e  | CP-213121 | 0015 |     | F   | 29.544 Rel-17 API version and External doc update                                                                             | 17.1.0      |
+| 2022-03        | CT#95e  | CP-220041 | 0016 |     | B   | Addition of SOR-CMCI related attribute as input to SP-AF                                                                      | 17.2.0      |
+| 2022-03        | CT#95e  | CP-220066 | 0017 |     | F   | API version and External doc update                                                                                           | 17.2.0      |
+| 2022-06        | CT#96   | CP-221300 | 0018 | 1   | F   | API version and External doc update                                                                                           | 17.3.0      |
+| 2022-12        | CT#98e  | CP-223027 | 0020 | 1   | F   | Missing Mandatory Status Codes in OpenAPI                                                                                     | 18.0.0      |
+| 2022-12        | CT#98e  | CP-223033 | 0021 |     | F   | 29.544 Rel-18 API version and External doc update                                                                             | 18.0.0      |
+| 2023-12        | CT#102  | CP-233028 | 0022 | 1   | F   | HTTP RFCs obsoleted by IETF RFC 9110, 9111 and 9113                                                                           | 18.1.0      |
+| 2023-12        | CT#102  | CP-233029 | 0023 |     | F   | ProblemDetails RFC 7807 obsoleted by 9457                                                                                     | 18.1.0      |