TR 33.835
Study on Authentication and Key Management
for Applications based on 3GPP Credential in 5G

3GPP‑Page fToC_↓ Partial Content _→

V16.1.0 (Wzip) 2020/06 83 p.

Rapporteur:: Miss Huang, Xiaoting
China Mobile Com. Corporation

full Table of Contents for TR 33.835 Word version: 16.1.0

each clause number in 'red' refers to the equivalent title in the Partial Content

Scope p. 10

References p. 10

Definitions of terms, symbols and abbreviations p. 11

3.1	Terms p. 11
3.2	Symbols p. 11
3.3	Abbreviations p. 11

Key Issues p. 12

4.1

Key Issue#1: Security Anchor p. 12

4.1.1	Issue detail p. 12
4.1.2	Security Threat p. 14
4.1.3	Potential architectural requirement p. 14

4.2

Key Issue #2: Transport independent procedure definition p. 14

4.2.1	Issue details p. 14
4.2.2	Security Threats p. 15
4.2.3	Potential architecture requirements p. 15

4.3

Key Issue #3: Mutual authentication between UE and anchor function p. 15

4.3.1	Issue details p. 15
4.3.2	Security Threats p. 15
4.3.3	Potential security requirements p. 15

4.4

Key Issue #4: Authentication framework p. 16

4.4.1	Issue details p. 16
4.4.2	Security Threats p. 16
4.4.3	Potential security requirements p. 16

4.5

Key Issue #5: User privacy p. 16

4.5.1	Issue details p. 16
4.5.2	Security Threats p. 16
4.5.3	Potential security requirements p. 17

4.6

Key Issue #6: Secure communication between UE and application server p. 17

4.6.1	Issue details p. 17
4.6.2	Security threats p. 17
4.6.3	Potential security requirements p. 17

4.7

Key Issue #7: Protecting subscriber's personal information in control and data traffic p. 17

4.7.1	Issue details p. 17
4.7.2	Security Threats p. 18
4.7.3	Potential security requirements p. 18

4.8

Key Issue #8: Protection of AKMA architecture interfaces p. 18

4.8.1	Issue details p. 18
4.8.2	Security Threats p. 18
4.8.3	Potential security requirements p. 18

4.9

Key Issue #9: Key separation for AKMA AFs p. 18

4.9.1	Issue details p. 18
4.9.2	Security Threats p. 18
4.9.3	Potential security requirements p. 18

4.10

Key Issue #10: Compliance with local rules and regulations p. 19

4.10.1	Issue details p. 19
4.10.2	Security Threats p. 19
4.10.3	Potential security requirements p. 19

4.11

Key Issue #11: Generic battery efficient end-to-end security p. 19

4.11.1	Issue details p. 19
4.11.2	Security threats p. 19
4.11.3	Potential security requirements p. 19

4.12

Key Issue #12: Key lifetimes p. 19

4.12.1	Issue details p. 19
4.12.2	Security Threats p. 19
4.12.3	Potential security requirements p. 20

4.13

Key Issue #13: API for AKMA keys in UE p. 20

4.13.1	Issue details p. 20
4.13.2	Security Threats p. 21
4.13.3	Potential security requirements p. 21

4.14

Key Issue #14: Key revocation p. 21

4.14.1	Issue details p. 21
4.14.2	Security Threats p. 21
4.14.3	Potential security requirements p. 21

4.15

Key Issue #15: Synchronization of keys when using established keys p. 21

4.15.1	Issue details p. 21
4.15.2	Security Threats p. 22
4.15.3	Potential security requirements p. 22

4.16

Key Issue #16: Application key freshness of AKMA p. 22

4.16.1	Issue details p. 22
4.16.2	Security Threats p. 22
4.16.3	Potential security requirements p. 22

4.17

Key Issue #17: AKMA push p. 22

4.17.1	Issue details p. 22
4.17.2	Security Threats p. 23
4.17.3	Potential security requirements p. 23

Candidate Solutions p. 23

5.1

Solution #1: Introducing third party key to AKMA p. 23

5.1.1	Introduction p. 23
5.1.2	Solution details p. 23
5.1.3	Evaluation p. 24

5.2

Solution #2: Access independent architecture solution for AKMA p. 25

5.2.1

Introduction p. 25

5.2.2

Solution details p. 25

5.2.2.1

Architecture and reference points p. 25

5.2.2.2

Procedures p. 26

5.2.2.2.1	Initiation p. 26
5.2.2.2.2	Authentication p. 26
5.2.2.2.3	Usage p. 27

5.2.3

Evaluation p. 27

5.3

Solution #3: Architecture solution for AKMA with standalone anchor p. 28

5.3.1

Introduction p. 28

5.3.2

Solution details p. 28

5.3.2.1

Architecture and reference points p. 28

5.3.2.2

Procedures p. 29

5.3.2.2.1	Initiation p. 29
5.3.2.2.2	Authentication p. 29
5.3.2.2.3	Usage p. 30

5.3.3

Evaluation p. 31

5.4

Solution #4: Bootstrapping authentication of AKMA p. 31

5.4.1

Introduction p. 31

5.4.2

Solution details p. 31

5.4.2.0	General p. 31
5.4.2.1	Potential Authentication procedure for 5G AKA p. 31
5.4.2.2	Potential Authentication procedure for EAP-AKA' p. 34

5.4.3

Evaluation p. 35

5.5

Solution #5: Transport independent procedure using existing protocols by applying OneM2M protocol binding mechanism p. 35

5.5.1	Introduction p. 35
5.5.2	Solution details p. 35
5.5.3	Evaluation p. 36

5.6

Solution #6: Transport independent procedure using existing protocols by introducing a protocol transfer gateway p. 36

5.6.1

Introduction p. 36

5.6.2

Solution details p. 37

5.6.2.1

Architecture reference model p. 37

5.6.2.1.1	Entities p. 37
5.6.2.1.2	Service based interfaces p. 37

5.6.2.2

Procedures p. 38

5.6.3

Evaluation p. 39

5.7

Solution #7: UE implementation scheme- AKMA framework and application on modem p. 39

5.7.1	Introduction p. 39
5.7.2	Solution details p. 39
5.7.3	Evaluation p. 39

5.8

Solution #8: UE implementation scheme- AKMA framework on UICC and application on modem p. 40

5.8.1	Introduction p. 40
5.8.2	Solution details p. 40
5.8.3	Evaluation p. 40

5.9

Solution #9: UE implementation scheme- Application Processor (AP) scheme with AKMA framework on modem p. 40

5.9.1	Introduction p. 40
5.9.2	Solution details p. 40
5.9.3	Evaluation p. 41

5.10

Solution #10: UE implementation scheme- Application Processor (AP) scheme with AKMA framework on UICC p. 41

5.10.1	Introduction p. 41
5.10.2	Solution details p. 41
5.10.3	Evaluation p. 42

5.11

Solution #11: UE implementation scheme- AKMA framework implemented on Secure Element (SE) p. 42

5.11.1	Introduction p. 42
5.11.2	Solution details p. 42
5.11.3	Evaluation p. 42

5.12

Solution #12: UE implementation scheme- AKMA framework implemented on application processor's OS p. 42

5.12.1	Introduction p. 42
5.12.2	Solution details p. 43
5.12.3	Evaluation p. 43

5.13

Solution #13: AKMA authentication via the control plane p. 43

5.13.1

Introduction p. 43

5.13.2

Solution details p. 44

5.13.2.1

Architecture and reference points p. 44

5.13.2.2

Procedures p. 44

5.13.2.2.1	Initiation p. 44
5.13.2.2.2	AKMA authentication with EAP-AKA' p. 45
5.13.2.2.3	AKMA authentication with 5G AKA p. 46
5.13.2.2.4	Usage p. 47

5.13.3

Evaluation p. 47

5.14

Solution #14: Key revocation p. 48

5.14.1

Introduction p. 48

5.14.2

Solution details p. 48

5.14.2.1	Revocation in Application function p. 48
5.14.2.2	Revocation in UE p. 48

5.15

Solution #15: Implicit bootstrapping p. 49

5.15.1

Introduction p. 49

5.15.2

Solution details p. 51

5.15.2.1	Authentication using EAP-AKA' p. 51
5.15.2.2	Authentication using 5G AKA p. 52
5.15.2.3	AKMA key refresh p. 52

5.15.3

Evaluation p. 53

5.16

Solution #16: Use of KSEAF as root key for KAKMA p. 54

5.16.1

Introduction p. 54

5.16.2

Solution details p. 54

5.16.2.1

AKMA Key Repository Service p. 54

5.16.2.1.1	AKMA Key Repository Service Serving Network Architecture Option p. 54
5.16.2.1.2	AKMA Key Repository Service Home Network Architecture Option p. 55

5.16.2.2

AKMA Established Key Use Procedure p. 56

5.16.2.2.1

Procedure p. 56

5.16.3

Evaluation p. 57

5.17

Solution #17: Efficient key derivation for end-to-end security p. 58

5.17.1

Introduction p. 58

5.17.2

Solution details p. 58

5.17.2.1

Architecture p. 58

5.17.2.2

Potential Procedures p. 59

5.17.2.2.1	Information flow p. 59
5.17.2.2.2	Key hierarchy p. 64

5.17.3

Evaluation p. 65

5.18

Solution #18: Key separation for AKMA AFs using counters p. 65

5.18.1	Introduction p. 65
5.18.2	Solution details p. 66
5.18.3	Evaluation p. 66

5.19

Solution #19: Reusing KAUSF for AKMA p. 67

5.19.1	Introduction p. 67
5.19.2	Solution details p. 67
5.19.3	Evaluation p. 68

5.20

Solution #20: Key identification when implicit bootstrapping is used p. 68

5.20.1

Introduction p. 68

5.20.2

Solution details p. 68

5.20.2.1	Option 1 - Key Identifier calculated from the keys p. 68
5.20.2.2	Option 2 - Reuse of ngKSI p. 68

5.20.3

Evaluation p. 69

5.21

Solution #21: Combining implicit bootstrapping solutions for usage of KAUSF or KSEAF as AKMA root key p. 70

5.21.1

Introduction p. 70

5.21.2

Solution details p. 70

5.21.2.1	Generic procedure p. 70
5.21.2.2	Home Network Option p. 71
5.21.2.3	Serving Network Option p. 71
5.21.2.4	Combined Option p. 72

5.21.3

Evaluation p. 72

5.22

Solution #22: Key freshness in AKMA p. 72

5.22.1	Introduction p. 72
5.22.2	Solution details p. 72
5.22.3	Evaluation p. 73

5.23

Solution #23: Implicit bootstrapping using NEF as the AKMA Anchor Functions p. 74

5.23.1

Introduction p. 74

5.23.2

Solution details p. 74

5.23.2.1	Architecture p. 74
5.23.2.2	Procedures p. 75

5.23.3

Evaluation p. 76

5.24

Solution #24: AKMA push p. 76

5.24.1

Introduction p. 76

5.24.2

Solution details p. 76

5.24.2.1

Architecture and reference points p. 76

5.24.2.2

Potential Procedures p. 77

5.24.2.2.1

Initiation p. 77

5.24.3

Evaluation p. 79

5.25

Solution #25: Key lifetimes p. 79

5.25.1

Introduction p. 79

5.25.2

Solution details p. 79

5.25.2.1	KAKMA lifetime p. 79
5.25.2.2	Application key lifetime p. 80

5.25.3

Evaluation p. 81

Evaluation and conclusion p. 81

6.1

Evaluation and conclusion on architecture and authentication procedures p. 81

6.2

Evaluation and conclusion on key management p. 81

6.2.1	Evaluation and conclusion on Key lifetimes (Key issue #12) p. 81
6.2.2	Evaluation and conclusion on Secure communication between UE and application server (Key issue #6) p. 82

6.3

Evaluation and conclusion on interfaces and protocols p. 82

6.4

Evaluation and conclusion on privacy p. 82

6.5

Evaluation and conclusion on API of AKMA in the UE p. 82

Change history p. 83

TR 33.835 Study on Authentication and Key Management for Applications based on 3GPP Credential in 5G

full Table of Contents for TR 33.835 Word version: 16.1.0

TR 33.835
Study on Authentication and Key Management
for Applications based on 3GPP Credential in 5G