2 References

29.1223GPPRelease 18T8 reference point for Northbound APIsTS

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.032: "Universal Geographical Area Description (GAD)".

[4] Void.

[5] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".

[6] Hypertext Transfer Protocol (HTTP) Status Code Registry at IANA, http://www.iana.org/assignments/http-status-codes.

[7] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax".

[8] IETF RFC 7807: "Problem Details for HTTP APIs".

[9] 3GPP TS 29.154: "Service capability exposure functionality over Nt reference point".

[10] 3GPP TS 29.214: "Policy and Charging Control over Rx reference point".

[11] 3GPP TS 29.336: "Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications".

[12] 3GPP TS 29.128: "Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) interfaces for interworking with packet data networks and applications".

[13] 3GPP TS 29.201: "Representational State Transfer (REST) reference point between Application Function (AF) and Protocol Converter (PC)".

[14] 3GPP TS 23.003: "Numbering, addressing and identification".

[15] IETF RFC 3339: "Date and Time on the Internet: Timestamps".

[16] IETF RFC 7230: "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing".

[17] IETF RFC 7231: "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content".

[18] IETF RFC 7232: "Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests".

[19] IETF RFC 7233: "Hypertext Transfer Protocol (HTTP/1.1): Range Requests".

[20] IETF RFC 7234: "Hypertext Transfer Protocol (HTTP/1.1): Caching".

[21] IETF RFC 7235: "Hypertext Transfer Protocol (HTTP/1.1): Authentication".

[22] IETF RFC 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2)".

[23] 3GPP TS 29.155: "Traffic steering control; Representational state transfer (REST) over St reference point".

[24] 3GPP TS 29.368: "Tsp interface protocol between the MTC Interworking Function (MTC-IWF) and Service Capability Server (SCS)".

[25] 3GPP TS 29.337: "Diameter-based T4 interface for communications with packet data networks and applications".

[26] 3GPP TS 29.250: "Nu reference point between SCEF and PFDF for sponsored data connectivity".

[27] Open API: "OpenAPI Specification Version 3.0.0", https://spec.openapis.org/oas/v3.0.0.

[28] IETF RFC 1166: "Internet Numbers".

[29] IETF RFC 5952: "A recommendation for Ipv6 address text representation".

[30] 3GPP TS 29.153: "Service capability exposure functionality over Ns reference point".

[31] 3GPP TS 24.250: "Protocol for Reliable Data Service; Stage 3".

[32] IETF RFC 6455: "The Websocket Protocol".

[33] 3GPP TS 29.272: "Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol".

[34] 3GPP TS 29.338: "Diameter based protocols to support Short Message Service (SMS) capable Mobile Management Entities (MMEs)".

[35] 3GPP TS 33.187: "Security aspects of Machine-Type Communications (MTC) and other mobile data applications communications enhancements".

[36] 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE);MB2 Reference Point;Stage 3".

[37] 3GPP TS 29.116: "Presentational state transfer over xMB reference point between Content Provider and BM-SC".

[38] IETF RFC 5789: "PATCH method for HTTP".

[39] IETF RFC 7396: "JSON Merge Patch".

[40] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".

[41] YAML (10/2009): "YAML Ain’t Markup Language (YAML™) Version 1.2", http://www.yaml.org/spec/1.2/spec.html.

[42] 3GPP TS 29.572: "5G System; Location Management Services; Stage 3".

[43] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)".

[44] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".

[45] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces Stage 3".

[46] IETF RFC 6733: "Diameter Base Protocol".

[47] 3GPP TS 23.222: "Common API Framework for 3GPP Northbound APIs; Stage 2".

[48] 3GPP TS 29.222: "Common API Framework for 3GPP Northbound APIs; Stage 3".

[49] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".

[50] 3GPP TS 29.554: "5G System; Background Data Transfer Policy Control Service; Stage 3".

[51] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".

[52] 3GPP TS 29.514: "5G System; Policy Authorization Service; Stage 3".

[53] 3GPP TS 33.122: "Security Aspects of Common API Framework for 3GPP Northbound APIs".

[54] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)".

[55] 3GPP TS 23.468: "Group Communication System Enablers for LTE (GCSE_LTE); stage 2".

[56] 3GPP TS 26.348, "Northbound Application Programming Interface (API) for Multimedia Broadcast/Multicast Service (MBMS) at the xMB reference point".

[57] 3GPP TS 29.508: "5G System; Session Management Event Exposure Service; Stage 3".

[58] 3GPP TR 21.900: "Technical Specification Group working methods".

[59] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC); Protocol Specification".

[60] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification".

[61] 3GPP TS 29.675: "User Equipment (UE) radio capability provisioning service; Stage 3".

[62] 3GPP TS 29.522: "5G System; Network Exposure Function Northbound APIs; Stage 3".

[63] 3GPP TS 29.503: "5G System; Unified Data Management Services; Stage 3".

[64] 3GPP TS 24.526: "User Equipment (UE) policies for 5G System (5GS); Stage 3".

[65] 3GPP TS 29.515: "5G System; Gateway Mobile Location Services; Stage 3".

[66] IETF RFC 5322: "Internet Message Format".

[67] IETF RFC 6902: "JavaScript Object Notation (JSON) Patch".

[68] 3GPP TS 33.558: "Security aspects of enhancement of support for enabling edge applications; Stage 2".

[69] IETF RFC 5234: "Augmented BNF for Syntax Specifications: ABNF".