Canonical Atlas record

TS 33.535

Authentication and Key Management for Applications (AKMA) based on 3GPP credentials in the 5G System (5GS)

Responsible WGS3
StatusUnder change control
Initial releaseRel-16
Selected releaseRel-17
Latest indexed version19.0.0
Series33
TypeTS

Release evolution

Compare evidence between releases

Use indexed version, Work Item and Change Request evidence to see what changed around this specification. This is an evidence trail, not a clause-by-clause normative diff.

Release ledger

Version · WI · CR evidence by release

-no version indexed1 WI0 CRs
Rel-1616.2.01 WI66 CRs · 17 approved
Rel-1717.12.03 WI147 CRs · 45 approved
Rel-1818.8.07 WI83 CRs · 36 approved
Rel-1919.0.02 WI5 CRs

Rel-17 snapshot

Work affecting this release

147 indexed Change Requests · 3 connected Work Items.

Showing 12 CR records from the available cross-release sample. Browse release CR records (JSON) →

CR 0117 — Clarification on the NF consumer in 6.6.1

CR 0116 — Add function description about AAnF in 4.2.1

CR 0118 — Clarification on UDM manage AKMA subscription data in 4.2.5

CR 0115 — Add a Note about the Kaf refresh

CR 0114 — CR to 33.535: AKMA service support for roaming UE

CR 0115 rev.1 — Add a Note about the Kaf refresh

CR 0119 — Add description about error case in annex B

CR 0111 — AKMA roaming

CR 0110 — Correction to Deriving AKMA Application Key for a specific AF

CR 0112 — CR to 33.535: Refresh of KAKMA and KAF

CR 0108 — Sending UE ID to the AKMA AF

CR 0107 — No AKMA security context in AAnF

Version history

Indexed versions

Showing 34 of 34 indexed versions.

19.0.0Rel-19SA#1092025-10-15
18.8.0Rel-18SA#1082025-07-04
17.12.0Rel-17SA#1082025-07-04
18.7.0Rel-18SA#1072025-03-25
18.6.0Rel-18SA#1062025-01-09
18.5.0Rel-18SA#1052024-09-27
18.4.0Rel-18SA#1042024-07-08
18.3.0Rel-18SA#1032024-03-28
17.11.0Rel-17SA#1032024-03-28
18.2.0Rel-18SA#1022024-01-04
17.10.0Rel-17SA#1022024-01-04
18.1.0Rel-18SA#1012023-09-20
17.9.0Rel-17SA#1012023-09-20
18.0.0Rel-18SA#1002023-06-22
17.8.0Rel-17SA#992023-03-30
17.7.0Rel-17SA#97-e2022-09-22
17.6.0Rel-17SA#962022-06-17
17.5.0Rel-17SA#95-e2022-03-24
17.4.0Rel-17SA#94-e2021-12-23
17.3.0Rel-17SA#93-e2021-09-23
17.2.1Rel-17SA#92-e2021-07-02
17.2.0Rel-17SA#92-e2021-06-25
17.1.0Rel-17SA#91-e2021-04-06
17.0.0Rel-17SA#90-e2020-12-16
16.2.0Rel-16SA#90-e2020-12-16
16.1.0Rel-16SA#89-e2020-09-25
16.0.0Rel-16SA#88-e2020-07-08
1.0.0Rel-16 · pre-approvalSA#88-e2020-06-15
0.5.0Rel-16 · pre-approvalSA3#99-e2020-05-29
0.4.0Rel-16 · pre-approvalSA3#98-bis-e2020-04-28
0.3.0Rel-16 · pre-approvalSA3#98-e2020-03-27
0.2.0Rel-16 · pre-approvalSA3#972020-01-02
0.1.0Rel-16 · pre-approvalSA3-Ad-Hoc2019-10-30
0.0.1Rel-16 · pre-approvalSA3-Ad-Hoc2019-10-30

Atlas classifications

Meaning and provenance

No Atlas classifications have been attached yet.

Work Items

Standards work connected to TS 33.535

Limbo

Limbo: code to be used for not-approved CRs related to never-approved WIDs

-parsed
eV2XARC

Architecture enhancements for 3GPP support of advanced V2X services

Historical association · verification pending
Rel-16historical link
AKMA

SA3 aspects of AKMA

Rel-17official
AKMA

Authentication and key management for applications based on 3GPP credential in 5G

Rel-17parsed
TEI17

(Small) Technical Enhancements and Improvements for Rel-17

Rel-17parsed
AKMA_Disable

AKMA service disabling in roaming

Rel-18parsed
AKMA_GBA_DTLS

IETF DTLS protocol profile for AKMA and GBA

Rel-18parsed
AKMA_GBA_OSCORE

IETF OSCORE protocol profiles for GBA and AKMA

Rel-18parsed
AKMA_Ph2

AKMA phase 2

Rel-18parsed
HN_Auth

Security aspects of home network triggered primary authentication

Rel-18parsed
HN_Auth

Home network triggered primary authentication

Rel-18parsed
TEI18

(Small) Technical Enhancements and Improvements for Rel-18

Rel-18parsed
CryptoSP

3GPP profiles for cryptographic algorithms and security protocols

Rel-19parsed
TEI19

(Small) Technical Enhancements and Improvements for Rel-19

Rel-19parsed

Knowledge graph

Related standards

No graph edges indexed yet. The graph API is available at this JSON endpoint.