Content for TR 23.700-98 Word version: 18.1.0
4 Key issues p. 17
4.1 Key issue #1: Enhanced notification service to the EEC p. 17
4.2 Key issue #2: Enablement of Service APIs exposed by EAS p. 18
4.3 Key issue #3: Enhancements to service continuity planning p. 18
4.4 Key issue #4: EDGE-5 p. 19
4.5 Key issue #5: Alignment of EDGEAPP and ETSI MEC p. 20
4.6 Key issue #6: Edge services support across ECSPs p. 20
4.7 Key issue #7: Application traffic filter exposure p. 21
4.8 Key issue #8: EAS selection synchronization p. 22
4.9 Key issue #9: Enhancement of dynamic EAS instantiation triggering p. 23
4.10 Key issue #10: Support for roaming UEs p. 23
4.11 Key issue #11: ACR between EAS and Cloud Application Server p. 24
4.12 Key issue #12: EEL service differentiation p. 24
4.13 Key issue #13: Edge enabler layer support for EAS synchronization p. 24
4.14 Key issue #14: Application traffic influence for initially selected EAS p. 25
4.15 Key issue #15: Support of constrained devices for Edge p. 26
4.16 Key issue #16: support of NAT deployed within the edge data network p. 26
4.17 Key issue #17: Discovery of a common EAS p. 26
4.18 Key issue #18: EAS bundles p. 27
4.19 Key issue #19: ACR scenario combination p. 28
4.20 Key issue #20: Supporting composite EASs p. 28
4.21 Key issue #21: Simultaneously EAS connectivity in ACR p. 28
4.22 Key issue #22: EAS discovery in Edge Node sharing scenario p. 30
4.23 Key issue #23: Reliable Edge service p. 30
4.24 Key issue #24: SEAL capability access for EEL support p. 31
5 Architectural requirements p. 31
5.1 General requirements p. 31
5.1.1 General p. 31
5.2 Enablement of Service APIs exposed by EAS p. 31
5.2.1 General p. 31
5.2.2 Requirements p. 31
5.3 ECS discovery p. 32
5.3.1 General p. 32
5.3.2 Requirements p. 32
5.4 Alignment of EDGEAPP and ETSI MEC p. 32
5.4.1 General p. 32
5.4.2 Requirements p. 32
5.5 Common EAS p. 33
5.5.1 General p. 33
5.5.2 Requirements p. 33
6 Enhanced Application Architecture p. 33
6.1 Option #1: Roaming architecture p. 33
6.1.1 Architecture enhancements p. 33
6.1.1.1 Local breakout roaming architecture: Local breakout to access H-ECS p. 33
6.1.1.2 Home-routed EDGE-4 access to H-ECS p. 34
6.1.2 Identities p. 35
6.1.3 Cardinality rules p. 35
6.2 Option #2: Non-roaming architecture p. 35
6.3 Option #3: Edge Notification Server architecture p. 35
6.4 Option #4: Constrained devices with limited capabilities p. 37
6.4.1 Architecture enhancements p. 37
6.4.1.1 General p. 37
6.4.1.2 Architecture p. 37
6.4.2 Identities p. 38
6.4.3 Cardinality rules p. 38
6.5 Option #5: Architecture for ACR between EAS and CAS without CES p. 38
6.6 Option #6: Architecture for ACR between EAS and CAS with CES p. 40
6.7 Option #7: Architecture for Common EAS selection with central binding server p. 41
6.8 Option #8: Architecture for ACR update in service continuity planning p. 41
6.9 Option #9: EEL utilization of SEAL services deployed in EDN p. 42
6.10 Option #10: EDGEAPP architecture in edge node sharing p. 43
6.11 Option #11: EDGEAPP architecture enhanced with Central AC Association Repository p. 44
6.12 Option #12: Architecture for Federation and Roaming p. 45
