Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 29.553  Word version:  18.3.0

Top   Top   None   None   Next
1…   5…

 

1  Scopep. 7

The present document specifies the stage 3 protocol and data model for the Npanf Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the 5G PAnF.
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.
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 33.503: "Security Aspects of Proximity based Services (ProSe) in the 5G System (5GS)".
[15]
TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
Up

3  Definitions 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.

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.
PAnF
Prose Anchor Function

4  Overviewp. 8

The Prose Anchor Function (PAnF) is the network entity in the 5G Core Network (5GC) supporting security procedure over Control Plane for the 5G ProSe UE-to-Network relay and 5G ProSe UE-to-UE Relay as specified in TS 33.503. Within the 5GC, the PAnF offers services to the AUSF and SMF via the Npanf service based interface.
Figure 4-1 provides the reference model (in service based interface representation and in reference point representation), with focus on the PAnF:
Reproduction of 3GPP TS 29.553, Fig. 4-1: Reference model - PAnF
Up
The PAnF supports the following functionalities:
  • Storage and retrieval of ProSe context information of the 5G ProSe Remote UE and ProSe context information of the 5G ProSe End UE;
  • Checking whether the 5G ProSe Remote UE is authorized to use the UE-to-Network Relay service and whether the End UE is authorized to use the UE-to-UE Relay service.
  • Resolving the ProSe Remote User ID to SUPI.

Up   Top   ToC