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 23.700-98
Word version: 18.1.0
0…
4…
7…
8…
8
Deployment scenarios
9
Involved entities and relationships
10
Overall evaluation
11
Conclusions
A
ETSI MEC and EDGEAPP system comparison
B
Deployment and Evolution options of EDGEAPP and ETSI MEC platforms
$
Change history
8
Deployment scenarios
p. 213
9
Involved entities and relationships
p. 214
9.1
Federation and Roaming
p. 214
9.1.1
General
p. 214
10
Overall evaluation
p. 215
10.0
General
p. 215
10.1
Architecture enhancements
p. 215
10.1.1
Support for Terminal Equipment (TE)
p. 215
10.1.2
Roaming architecture
p. 215
10.1.3
Architecture for Federation and Roaming
p. 215
10.2
Key issue evaluations
p. 216
10.2.0
General
p. 216
10.2.1
Key issue #1: Enhanced notification service to the EEC
p. 220
10.2.2
Key issue #2: Enablement of Service APIs exposed by EAS
p. 221
10.2.3
Key issue #3: Enhancements to service continuity planning
p. 222
10.2.4
Key issue #4: EDGE-5
p. 222
10.2.5
Key issue #5: Alignment of EDGEAPP and ETSI MEC
p. 223
10.2.6
Key issue #6: Edge services support across ECSPs
p. 223
10.2.8
Key issue #8: EAS selection synchronization
p. 225
10.2.9
Key issue #9: Enhancement of dynamic EAS instantiation triggering
p. 225
10.2.10
Key issue #10: Support for Roaming UEs
p. 227
10.2.11
Key issue #11: ACR between EAS and Cloud Application Server
p. 229
10.2.12
Key issue #12: EEL service differentiation
p. 230
10.2.13
Key issue #13: Edge enabler layer support for EAS synchronization
p. 230
10.2.14
Key issue #14: Application traffic influence for initially selected EAS
p. 230
10.2.15
Key issue #15: Support of constrained devices for Edge
p. 231
10.2.16
Key issue #16: support of NAT deployed within the edge data network
p. 231
10.2.17
Key issue #17: Discovery of a common EAS
p. 231
10.2.18
Key issue #18: EAS bundles
p. 232
10.2.19
Key issue #19: ACR scenario combination
p. 232
10.2.20
Key issue #20: Supporting composite EASs
p. 233
10.2.21
Key issue #21: Simultaneously EAS connectivity in ACR
p. 233
10.2.22
Key issue #22: EAS discovery in Edge Node sharing scenario
p. 233
10.2.23
Key issue #23: Reliable Edge service
p. 234
10.2.24
Key issue #24: SEAL capability access for EEL support
p. 234
11
Conclusions
p. 235
11.1
General
p. 235
11.2
Conclusions for normative work
p. 235
11.2.1
General conclusions
p. 235
11.2.2
Architecture enhancement conclusions
p. 235
11.2.3
Solution conclusions
p. 236
A
ETSI MEC and EDGEAPP system comparison
p. 240
A.1
General
p. 240
A.2
Service consumer and service provider
p. 240
A.3
EAS/MEC application profile provisioning
p. 240
A.4
EAS registration and EAS discovery
p. 241
B
Deployment and Evolution options of EDGEAPP and ETSI MEC platforms
p. 242
B.1
General
p. 242
B.2
Deployment options
p. 243
B.2.1
Deployment Option-1: Collocated Platforms
p. 243
B.2.2
Deployment Option-2: Converged architecture
p. 243
B.2.2.1
General
p. 243
B.2.2.2
Evolution Options
p. 244
B.2.2.2.1
General
p. 244
B.2.2.2.2
Evolution Option #1- Enhancement of a deployed MEP to support the functionality of EES
p. 244
B.2.2.2.3
Evolution Option #2 Enhancement of a deployed EES to support the functionality of MEP
p. 245
B.2.3
Deployment Option-3: non-Collocated Platforms
p. 245
$
Change history
p. 246