Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 29.556  Word version:  18.6.0

Top   Top   None   None   Next
1…   5…

 

1  Scopep. 7

The present document specifies the stage 3 protocol and data model for the Neasdf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the EASDF.
The 5G System stage 2 architecture and procedures are specified in TS 23.501, TS 23.502 and TS 23.548.
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.
Up

2  Referencesp. 7

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]
TS 23.548: "5G System Enhancements for Edge Computing; Stage 2".
[15]
RFC 6902:  "JavaScript Object Notation (JSON) Patch".
[16]
TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
[17]  Void.
[18]
RFC 7871:  "Client Subnet in DNS Queries".
[19]
TS 23.003: "Numbering, addressing and identification".
[20]
TS 29.502: "5G System; Session Management Services; Stage 3".
Up

3  Definitions, symbols and abbreviationsp. 8

3.1  Definitionsp. 8

For the purposes of the present document, the terms and definitions given in TR 21.905 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.
One-Time DNS Rule:
A DNS Rule that applies only once to a specific DNS message earlier buffered in the EASDF and reported to the SMF (see clause 5.2.3.2.4).

3.2  Abbreviationsp. 8

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 TR 21.905.
BD AIT
Baseline DNS Action Information Template
BD MDT
Baseline DNS Message Detection Template
EASDF
Edge Application Server Discovery Function
ECS
EDNS Client Subnet
EDNS
Extension mechanisms for DNS
HR-SBO
Home Routed Session BreakOut
MDT
(DNS Query or DNS Response) Message Detection Template
Up

4  Overviewp. 8

4.1  Introductionp. 8

Within the 5GC, the EASDF offers services to the SMF via the Neasdf service based interface (see TS 23.548, TS 23.501 and TS 23.502).
Figure 4.1-1 provides the reference model (in service based interface representation and in reference point representation), with focus on the EASDF and the scope of the present specification.
Reproduction of 3GPP TS 29.556, Fig. 4.1-1: Reference model - EASDF
Up
The functionalities supported by the EASDF are listed in clause 5.1.1 of TS 23.548.

Up   Top   ToC