ETSI TS 129 509 V15.5.1 (2019-10)

TECHNICAL SPECIFICATION
5G;
5G System;
Authentication Server Services;
Stage 3
(3GPP TS 29.509 version 15.5.1 Release 15)


3GPP TS 29.509 version 15.5.1 Release 15 1 ETSI TS 129 509 V15.5.1 (2019-10)

Reference
RTS/TSGC-0429509vf51
Keywords
5G
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2019.
All rights reserved.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3GPP TS 29.509 version 15.5.1 Release 15 2 ETSI TS 129 509 V15.5.1 (2019-10)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 29.509 version 15.5.1 Release 15 3 ETSI TS 129 509 V15.5.1 (2019-10)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 7
1 Scope . 8
2 References . 8
3 Definitions and abbreviations . 9
3.1 Definitions . 9
3.2 Abbreviations . 9
4 Overview . 9
4.1 Introduction . 9
5 Services offered by the AUSF . 10
5.1 Introduction . 10
5.2 Nausf_UEAuthentication Service . 10
5.2.1 Service Description . 10
5.2.2 Service Operations . 11
5.2.2.1 Introduction . 11
5.2.2.2 Authenticate . 11
5.2.2.2.1 General . 11
5.2.2.2.2 5G AKA . 11
5.2.2.2.3 EAP-based authentication method . 12
5.2.2.2.3.1 General . 12
5.2.2.2.3.2 EAP method: EAP-AKA' . 12
5.2.2.2.3.3 EAP method: EAP-TLS . 14
5.3 Nausf_SoRProtection Service . 14
5.3.1 Service Description . 14
5.3.2 Service Operations . 14
5.3.2.1 Introduction . 14
5.3.2.2 Protect . 14
5.3.2.2.1 General . 14
5.4 Nausf_UPUProtection Service . 15
5.4.1 Service Description . 15
5.4.2 Service Operations . 15
5.4.2.1 Introduction . 15
5.4.2.2 Protect . 15
5.4.2.2.1 General . 15
6 API Definitions . 16
6.1 Nausf_UEAuthentication Service API . 16
6.1.1 API URI . 16
6.1.2 Usage of HTTP . 16
6.1.2.1 General . 16
6.1.2.2 HTTP standard headers . 16
6.1.2.2.1 General . 16
6.1.2.2.2 Content type . 16
6.1.2.3 HTTP custom headers . 17
6.1.2.3.1 General . 17
6.1.3 Resources . 17
6.1.3.1 Overview . 17
6.1.3.2 Resource: List of ue-authentications . 18
6.1.3.2.1 Description . 18
6.1.3.2.2 Resource Definition . 18
6.1.3.2.3 Resource Standard Methods . 18
ETSI
3GPP TS 29.509 version 15.5.1 Release 15 4 ETSI TS 129 509 V15.5.1 (2019-10)
6.1.3.2.3.1 POST. 18
6.1.3.2.4 Resource Custom Operations . 19
6.1.3.2.4.1 Overview . 19
6.1.3.3 Resource: 5g-aka-confirmation (Document) . 19
6.1.3.3.1 Description . 19
6.1.3.3.2 Resource Definition . 19
6.1.3.3.3 Resource Standard Methods . 20
6.1.3.3.3.1 PUT . 20
6.1.3.4 Resource: eap-session (Document) . 20
6.1.3.4.1 Description . 20
6.1.3.4.2 Resource Definition . 20
6.1.3.4.3 Resource Standard Methods . 21
6.1.3.4.3.1 POST. 21
6.1.4 Custom Operations without associated resources . 21
6.1.4.1 Overview . 21
6.1.5 Notifications . 21
6.1.5.1 General . 21
6.1.6 Data Model . 22
6.1.6.1 General . 22
6.1.6.2 Structured data types . 22
6.1.6.2.1 Introduction . 22
6.1.6.2.2 Type: AuthenticationInfo . 22
6.1.6.2.3 Type: UEAuthenticationCtx . 23
6.1.6.2.4 Type: 5gAuthData . 23
6.1.6.2.5 Type: Av5gAka . 23
6.1.6.2.6 Type: ConfirmationData . 23
6.1.6.2.7 Type: EapSession . 24
6.1.6.2.8 Type: ConfirmationDataResponse. 24
6.1.6.3 Simple data types and enumerations . 24
6.1.6.3.1 Introduction . 24
6.1.6.3.2 Simple data types . 24
6.1.6.3.3 Enumeration: AuthType . 24
6.1.6.3.4 Enumeration: AuthResult . 25
6.1.6.3.5 Relation Types . 25
6.1.6.3.5.1 General . 25
6.1.6.3.5.2 The "5g-aka" Link relation . 25
6.1.6.3.5.3 The "eap-session" Link relation . 25
6.1.6.4 Binary data . 25
6.1.6.4.1 Introduction . 25
6.1.7 Error Handling . 25
6.1.7.1 General . 25
6.1.7.2 Protocol Errors . 25
6.1.7.3 Application Errors . 25
6.1.8 Security . 26
6.2 Nausf_SoRProtection Service API . 27
6.2.1 API URI . 27
6.2.2 Usage of HTTP . 27
6.2.2.1 General . 27
6.2.2.2 HTTP standard headers . 27
6.2.2.2.1 General . 27
6.2.2.2.2 Content type . 27
6.2.2.3 HTTP custom headers . 27
6.2.2.3.1 General . 27
6.2.3 Resources . 27
6.2.3.1 Overview . 27
6.2.3.2 Resource: ue-sor . 28
6.2.3.2.1 Description . 28
6.2.3.2.2 Resource Definition . 28
6.2.3.2.3 Resource Standard Methods . 28
6.2.3.2.4 Resource Custom Operations . 29
6.2.3.2.4.1 Overview . 29
6.2.3.2.4.2 Operation: generate-sor-data . 29
ETSI
3GPP TS 29.509 version 15.5.1 Release 15 5 ETSI TS 129 509 V15.5.1 (2019-10)
6.2.3.2.4.2.1 Description . 29
6.2.3.2.4.2.2 Operation Definition . 29
6.2.4 Custom Operations without associated resources . 29
6.2.4.1 Overview . 29
6.2.5 Notifications . 30
6.2.5.1 General . 30
6.2.6 Data Model . 30
6.2.6.1 General . 30
6.2.6.2 Structured data types . 30
6.2.6.2.1 Introduction . 30
6.2.6.2.2 Type: SorInfo . 31
6.2.6.2.3 Type: SorSecurityInfo . 31
6.2.6.2.4 Type: SteeringInfo . 31
6.2.6.2.5 Type: SteeringContainer . 31
6.2.6.3 Simple data types and enumerations . 32
6.2.6.3.1 Introduction . 32
6.2.6.3.2 Simple data types . 32
6.2.6.3.3 Enumeration: AccessTech . 32
6.2.7 Error Handling . 32
6.2.7.1 General . 32
6.2.7.2 Protocol Errors . 32
6.2.7.3 Application Errors . 32
6.2.8 Security . 33
6.3 Nausf_UPUProtection Service API . 33
6.3.1 API URI . 33
6.3.2 Usage of HTTP . 33
6.3.2.1 General . 33
6.3.2.2 HTTP standard headers . 33
6.3.2.2.1 General . 33
6.3.2.2.2 Content type . 33
6.3.2.3 HTTP custom headers . 34
6.3.2.3.1 General . 34
6.3.3 Resources . 34
6.3.3.1 Overview . 34
6.3.3.2 Resource: ue-upu . 34
6.3.3.2.1 Description . 34
6.3.3.2.2 Resource Definition . 34
6.3.3.2.3 Resource Standard Methods . 35
6.3.3.2.4 Resource Custom Operations . 35
6.3.3.2.4.1 Overview . 35
6.3.3.2.4.2 Operation: generate-upu-data . 35
6.3.3.2.4.2.1 Description . 35
6.3.3.2.4.2.2 Operation Definition . 35
6.3.4 Custom Operations without associated resources . 36
6.3.4.1 Overview . 36
6.3.5 Notifications . 36
6.3.5.1 General . 36
6.3.6 Data Model . 36
6.3.6.1 General . 36
6.3.6.2 Structured data types . 36
6.3.6.2.1 Introduction . 36
6.3.6.2.2 Type: UpuInfo . 37
6.3.6.2.3 Type: UpuSecurityInfo . 37
6.3.6.2.4 Type: UpuData . 37
6.3.6.3 Simple data types and enumerations . 37
6.3.6.3.1 Introduction . 37
6.3.6.3.2 Simple data types . 37
6.3.6.3.3 Enumeration: UpuDataType . 38
6.3.7 Error Handling . 38
6.3.7.1 General . 38
6.3.7.2 Protocol Errors . 38
6.3.7.3 Application Errors . 38
ETSI
3GPP TS 29.509 version 15.5.1 Release 15 6 ETSI TS 129 509 V15.5.1 (2019-10)
6.3.8 Security . 38
Annex A (normative): OpenAPI specification . 39
A.1 General . 39
A.2 Nausf_UEAuthentication API . 39
A.3 Nausf_SoRProtection API . 43
A.4 Nausf_UPUProtection API . 45
Annex B (Informative): Use of EAP-TLS . 47
B.1 General . 47
B.2 EAP method: EAP-TLS . 47
Annex C (informative): Withdrawn API versions . 49
C.1 General . 49
C.2 Nausf_SoRProtection API . 49
Annex D (informative): Change history . 50
History . 53

ETSI
3GPP TS 29.509 version 15.5.1 Release 15 7 ETSI TS 129 509 V15.5.1 (2019-10)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
ETSI
3GPP TS 29.509 version 15.5.1 Release 15 8 ETSI TS 129 509 V15.5.1 (2019-10)
1 Scope
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 3GPP TS 23.501 [2], 3GPP TS 23.502 [3] and
3GPP TS 33.501 [8].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition
are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5].
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.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[4] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[5] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[6] IETF RFC 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2)".
[7] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
[8] 3GPP TS 33.501: "Security Architecture and Procedures for 5G System".
rd
[9] IETF RFC 5448: "Improved Extensible Authentication Protocol Method for 3 Generation
Authentication and Key Agreement (EAP-AKA')".
Editor's Note: This reference may be removed and references to it updated when the IETF publishes the
corresponding update version.
[10] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
[11] IETF RFC 7807: "Problem Details for HTTP APIs".
[12] 3GPP TS 29.503: "5G System; Unified Data Management Services; Stage 3".
[13] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
[14] 3GPP TS 29.510: "Network Function Repository Services; Stage 3".
[15] 3GPP TS 31.102: "Characteristics of the Universal Subscriber Identity Module (USIM)
application".
[16] IETF RFC 5216: "The EAP-TLS Authentication Protocol".
[17] Internet draft draft-ietf-emu-rfc5448bis: "Improved Extensible Authentication Protocol Method for
3rd Generation Authentication and Key Agreement (EAP-AKA')".
ETSI
3GPP TS 29.509 version 15.5.1 Release 15 9 ETSI TS 129 509 V15.5.1 (2019-10)
[18] IETF RFC 3748: "Extensible Authentication Protocol (EAP)".
[19] IETF RFC 4648: "The Base16, Base32 and Base64 Data Encodings".
[20] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[21] 3GPP TR 21.900: "Technical Specification Group working methods".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following
apply. A term defined in the present document takes precedence over the definition of the same term, if any, in
3GPP TR 21.905 [1].
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] 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 [1].
AMF Access and Mobility Management Function
API Application Programming Interface
AUSF Authentication Server Function
MAC Message Authentication Code
NF Network Function
SEAF SEcurity Anchor Function
SoR Steering of Roaming
URI Uniform Resource Identifier
UPU UE Parameters Update
4 Overview
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.
Figure 4-1 shows the reference architecture for the AUSF:
ETSI
3GPP TS 29.509 version 15.5.1 Release 15 10 ETSI TS 129 509 V15.5.1 (2019-10)

AUSF
Nausf
AMF/ AMF/
UDM
SEAF SEAF
HPLMN VPLMN
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.
5 Services offered by the AUSF
5.1 Introduction
The AUSF offers to NF Service Consumers (e.g. AMF) the following services:
- Nausf_UEAuthentication
- Nausf_SoRProtection
- Nausf_UPUProtection
5.2 Nausf_UEAuthentication Service
5.2.1 Service Description
The AUSF is acting as NF Service Producer. It provides UE authentication service to the requester NF. The NF Service
Consumer is the AMF.
For this service, the following service operations are defined:
- Authenticate
This service permits to authenticate the UE and to provide one or more master keys which are used by the AMF to
derived subsequent keys.
ETSI
3GPP TS 29.509 version 15.5.1 Release 15 11 ETSI TS 129 509 V15.5.1 (2019-10)
5.2.2 Service Operations
5.2.2.1 Introduction
The service operation defined for the Nausf_UEAuthentication is as follows:
- Authenticate: It allows the AMF to authenticate the UE.
5.2.2.2 Authenticate
5.2.2.2.1 General
The service operation "Authenticate" permits the requester NF to initiate the Authentication of the UE by providing the
following information to the AUSF:
- UE id (e.g. SUPI)
- Serving Network Name
The AUSF retrieves the UE's subscribed authentication method from the UDM and depending on the information
provided by the UDM, the AUSF enters in one of the following procedures:
- 5G-AKA
- EAP-based authentication'
For those two different procedures a new resource is generated by the AUSF. The content of the resource will depend
on the procedure and will be returned to the AMF.
5.2.2.2.2 5G AKA
In this procedure, the NF Service Consumer (AMF) requests the authentication of the UE by providing UE related
information and the serving network name and the 5G AKA is selected. The NF Service Consumer (AMF) shall then
return to the AUSF the result received from the UE:

Figure 5.2.2.2.2-1: 5G AKA
1. The NF Service Consumer (AMF) shall send a POST request to the AUSF. The payload of the body shall
contain at least the UE Id and the Serving Network Name.
2a. On success, "201 Created" shall be returned. The payload body shall contain the representation of the resource
created and the "Location" header shall contain the URI of the created resource (e.g.
ETSI
3GPP TS 29.509 version 15.5.1 Release 15 12 ETSI TS 129 509 V15.5.1 (2019-10)
.../v1/ue_authentications/{authCtxId}). The AUSF generates a sub-resource "5g-aka-confirmation". The AUSF
shall provide an hypermedia link towards this sub-resource in the payload to indicate to the AMF where it shall
send a PUT for the confirmation.
2b. On failure, one of the HTTP status code listed in table 6.1.7.3-1 shall be returned with the message body
containing a ProblemDetails structure with the "cause" attribute set to one of the application error listed in Table
6.1.7.3-1. If the serving network is not authorized, the AUSF shall use the
SERVING_NETWORK_NOT_AUTHORIZED "cause".
3. Based on the relation type, the NF Service Consumer (AMF) deduces that it shall send a PUT containing the
"RES*" provided by the UE to the URI provided by the AUSF or derived by itself. The NF Service Consumer
(AMF) shall also send a PUT containing null value in the RES* to indicate the failure to the AUSF for the
following cases:
- if the UE is not reached, and
...