Content for TS 29.598 Word version: 18.4.0
1 Scope
2 References
3 Definitions of terms, symbols and abbreviations
3.1 Terms
3.2 Symbols
3.3 Abbreviations
4 Overview
...
...
1 Scope p. 9
The present document specifies the stage 3 protocol and data model for the Nudsf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the UDSF.
The 5G System stage 2 architecture and procedures are specified in TS 23.501 and TS 23.502.
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in TS 29.500 and TS 29.501.
2 References p. 9
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]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 23.501: "System Architecture for the 5G System; Stage 2".
[3]
TS 23.502: "Procedures for the 5G System; Stage 2".
[4]
TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[5]
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]
TR 21.900: "Technical Specification Group working methods".
[8]
TS 33.501: "Security architecture and procedures for 5G system".
[9]
RFC 6749: "The OAuth 2.0 Authorization Framework".
[10]
TS 29.510: "5G System; Network Function Repository Services; Stage 3".
[11]
RFC 9113: " HTTP/2".
[12]
RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
[13]
RFC 9457: "Problem Details for HTTP APIs".
[14]
RFC 6902: "JavaScript Object Notation (JSON) Patch".
[15]
RFC 9110: "HTTP Semantics".
[16] Void.
[17]
RFC 9111: " HTTP Caching".
[18]
ISO/IEC 14977: "Information technology - Syntactic metalanguage - Extended BNF".
[19]
TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
[20]
RFC 2045: "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies".
[21]
RFC 2046: "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types".
[22]
RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax".
3 Definitions of terms, symbols and abbreviations p. 10
3.1 Terms p. 10
void
3.2 Symbols p. 10
void
3.3 Abbreviations p. 10
For the purposes of the present document, the abbreviations given in TR 21.905 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.
5GC
5G Core Network
BNF
Backus-Naur Form
EBNF
Extended BNF
CP
Control Plane
MIME
Multipurpose Internet Mail Extensions
NF
Network Function
UDSF
Unstructured Data Storage Function
4 Overview p. 10
The UDSF, as depicted in Figure 4.1-1 below, is described in clause 4.2.5 of TS 23.501. Any of the 5GS NFs can make use of the UDSF to store and retrieve unstructured data, i.e., data that is not defined in 3GPP specifications, and can make use of the UDSF to run timers and get notified on timer expiry. The UDSF is deployed in the same network where the CP NF is located and the same UDSF may be shared by all the NFs in the PLMN to store/retrieve their respective data or an NF may have its own UDSF depending on operator configuration.
