Tech-
invite
3GPP
space
IETF
space
21
22
23
24
25
26
27
28
29
31
32
33
34
35
36
37
38
4‑5x
Content for
TR 33.839
Word version: 17.1.0
1…
4…
6…
4
Overview of Edge Computing (EC)
5
Key issues
4
Overview of Edge Computing (EC)
p. 11
5
Key issues
p. 12
5.0
General
p. 12
5.1
Key issue #1: Authentication and Authorization between EEC and EES
p. 12
5.1.1
Key Issue Details
p. 12
5.1.2
Security Threats
p. 12
5.1.3
Potential Security Requirements
p. 13
5.2
Key issue #2: Authentication and Authorization between EEC and ECS
p. 13
5.2.1
Key Issue Details
p. 13
5.2.2
Security Threats
p. 13
5.2.3
Potential Security Requirements
p. 14
5.3
Key issue #3: Authentication and Authorization between EES and ECS
p. 14
5.3.1
Key Issue Details
p. 14
5.3.2
Security Threats
p. 14
5.3.3
Potential Security Requirements
p. 14
5.4
Key Issue #4 Edge Data Network Authentication and Authorization
p. 15
5.4.1
Key issue detail
p. 15
5.4.2
Security threats
p. 15
5.4.3
Potential security requirements
p. 15
5.5
Key Issue #5 Edge Data Network User Identifier and Credential Protection
p. 15
5.5.1
Key issue detail
p. 15
5.5.2
Security threats
p. 15
5.5.3
Potential security requirements
p. 15
5.6
Key issue #6: Transport security for the EDGE-1-9 interfaces
p. 16
5.6.1
Key issue details
p. 16
5.6.2
Threats
p. 16
5.6.3
Potential security requirements
p. 17
5.7
Key Issue #7: Security of Network Information Provisioning to Local Applications with low latency procedure
p. 17
5.7.1
Key issue details
p. 17
5.7.2
Security threats
p. 18
5.7.3
Potential Security requirements
p. 18
5.8
Key Issue #8: authentication and authorization in EES capability exposure
p. 18
5.8.1
Key issue details
p. 18
5.8.2
Security threats
p. 18
5.8.3
Potential security requirements
p. 18
5.9
Key Issue #9: Security of EAS discovery procedure
p. 19
5.9.1
Key issue details
p. 19
5.9.2
Security threats
p. 19
5.9.3
Potential Security requirements
p. 19
5.10
Key issue #10: Authorization during Edge Data Network change
p. 19
5.10.1
Key issue details
p. 19
5.10.2
Security threats
p. 20
5.10.3
Potential security requirements
p. 20