Tech-invite3GPPspaceIETF RFCsSIP

Content for  TS 29.509  Word version:  17.3.0

Top   Top   None   None   Next
1…   5…   6…   A…


1  ScopeWord‑p. 8

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

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.
TR 21.905: "Vocabulary for 3GPP Specifications".
TS 23.501: "System Architecture for the 5G System; Stage 2".
TS 23.502: "Procedures for the 5G System; Stage 2".
TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
RFC 7540:  "Hypertext Transfer Protocol Version 2 (HTTP/2)".
RFC 8259:  "The JavaScript Object Notation (JSON) Data Interchange Format".
TS 33.501: "Security Architecture and Procedures for 5G System".
RFC 5448:  "Improved Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA')".
TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
RFC 7807:  "Problem Details for HTTP APIs".
TS 29.503: "5G System; Unified Data Management Services; Stage 3".
RFC 6749:  "The OAuth 2.0 Authorization Framework".
TS 29.510: "Network Function Repository Services; Stage 3".
TS 31.102: "Characteristics of the Universal Subscriber Identity Module (USIM) application".
RFC 5216:  "The EAP-TLS Authentication Protocol".
draft-ietf-emu-rfc5448bis:  "Improved Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA')".
RFC 3748:  "Extensible Authentication Protocol (EAP)".
RFC 4648:  "The Base16, Base32 and Base64 Data Encodings".
TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
TR 21.900: "Technical Specification Group working methods".
TS 29.544: "5G System; SP-AF Services; Stage 3".
TS 23.316: " Wireless and wireline convergence access support for the 5G System (5GS); Release 16".
TS 29.524: "5G System; Cause codes mapping between 5GC interfaces; Stage 3".
OpenAPI Initiative, "OpenAPI Specification Version 3.0.0",

3  Definitions and abbreviationsWord‑p. 9

3.1  Definitions

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  Abbreviations

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.
Access and Mobility Management Function
Application Programming Interface
Authentication Server Function
Fixed Network RG
Message Authentication Code
Network Function
Residential Gateway
SEcurity Anchor Function
Steering of Roaming
Uniform Resource Identifier
UE Parameters Update
Wireline Access Gateway Function

4  OverviewWord‑p. 10

4.1  Introduction

The Network Function (NF) Authentication Server Function (AUSF) is the network entity in the 5G Core Network (5GC) supporting the following functionalities:
  • Authenticate the UE for the requester NF,
  • Provide keying material to the requester NF,
  • Protect the Steering Information List for the requester NF.
  • Protect the UE Parameter Update Data for the requester NF.
Figure 4-1 shows the reference architecture for the AUSF:
(not reproduced yet)
Figure 4-1: AUSF in 5G System architecture
This figure represents the AUSF architecture in the Service-based Architecture model. In the reference point model, the interface between the AMF and the AUSF is named N12. In this release, the SEAF function is collocated with the AMF. The AUSF may provide the service to the UDM.

Up   Top   ToC