Content for TR 23.758 Word version: 17.0.0
5 Architectural requirements
6 Application architecture for enabling edge applications
7 Solutions
8 Identities and commonly used values
9 Deployment scenarios
10 Involved business relationships
11 Overall evaluation
12 Conclusions
A Analysis of edge computing standards
B EEC decomposition
$ Change History
5 Architectural requirements p. 17
5.1 General requirements p. 17
5.1.1 General p. 17
5.1.2 Requirements p. 17
5.2 Edge Data Network configuration data p. 17
5.2.1 General p. 17
5.2.2 Requirements p. 17
5.3 Edge Enabler Client registration p. 18
5.3.1 General p. 18
5.3.2 Requirements p. 18
5.4 Edge Application Server enablement p. 18
5.4.1 General p. 18
5.4.2 Requirements p. 18
5.5 Edge Application Server discovery p. 18
5.5.1 General p. 18
5.5.2 Requirements p. 18
5.6 Capability exposure to Edge Application Servers p. 19
5.6.1 General p. 19
5.6.2 Requirements p. 19
5.7 Security p. 19
5.7.1 General p. 19
5.7.2 Requirements p. 19
6 Application architecture for enabling edge applications p. 19
6.1 General p. 19
6.2 Application architecture p. 19
6.3 Functional elements p. 20
6.3.1 General p. 20
6.3.2 Edge Enabler Server p. 20
6.3.3 Edge Enabler Client p. 21
6.3.4 Edge Data Network Configuration Server p. 21
6.4 Reference Points p. 21
6.4.1 General p. 21
6.4.2 EDGE-1 p. 21
6.4.3 EDGE-2 p. 21
6.4.4 EDGE-3 p. 22
6.4.5 EDGE-4 p. 22
6.4.6 EDGE-5 p. 22
6.4.7 EDGE-6 p. 22
6.4.8 EDGE-7 p. 22
6.4.9 EDGE-8 p. 23
7 Solutions p. 23
7.1 Solution #1: Edge Application Server Discovery p. 23
7.1.1 Solution description p. 23
7.1.2 Solution evaluation p. 25
7.2 Solution #2: Provisioning of Edge Data Network configuration p. 25
7.2.1 Solution description p. 25
7.2.1.1 General p. 25
7.2.1.2 Procedure for provisioning Edge Data Network configuration p. 26
7.2.1.3 Procedure for initial provisioning and connecting to the Edge Enabler Server p. 28
7.2.1.4 Derivation of EDNCS address from the serving network domain name p. 29
7.2.2 Solution evaluation p. 29
7.3 Solution #3: Edge Data Network using LADN p. 29
7.3.1 Solution description p. 29
7.3.2 Solution evaluation p. 30
7.4 Solution #4: Location Reporting API p. 30
7.4.1 Solution description p. 30
7.4.1.1 General p. 30
7.4.1.2 Procedure p. 30
7.4.1.2.1 Request-Response model p. 30
7.4.1.2.2 Subscribe-Notify model p. 31
7.4.1.2.3 Detection of UE location from the 3GPP system p. 33
7.4.1.3 Service Operations p. 33
7.4.2 Solution evaluation p. 34
7.5 Solution #5: UE Identifier API p. 35
7.5.1 Solution description p. 35
7.5.2 Solution evaluation p. 37
7.6 Solution #6: Service Authorization for Edge Computing service p. 37
7.6.1 Solution description p. 37
7.6.2 Solution evaluation p. 39
7.7 Solution #7: Dynamic availability of Edge Application Servers p. 39
7.7.1 Solution description p. 39
7.7.2 Solution evaluation p. 40
7.8 Solution #8: Registering Edge Enabler Client on Edge Enabler Server p. 40
7.8.1 Solution description p. 40
7.8.2 Solution evaluation p. 42
7.9 Solution #9: Relocation of application context p. 43
7.9.1 Solution description p. 43
7.9.1.1 Procedure p. 43
7.9.1.2 API description p. 44
7.9.2 Solution evaluation p. 45
7.10 Solution #10: Network capability exposure to Edge Application Server using CAPIF p. 46
7.10.1 Solution description p. 46
7.10.1.1 General p. 46
7.10.1.2 Distributed CAPIF p. 46
7.10.1.3 Centralized CAPIF p. 47
7.10.1.4 EES and EAS direct interaction with 3GPP core network(s) p. 49
7.10.2 Solution evaluation p. 50
7.11 Solution #11: QoS Management for 5G Edge Applications p. 50
7.12 Solution #12: Edge Application Server Enablement p. 51
7.12.1 Solution description p. 51
7.12.1.1 General p. 51
7.12.1.2 Edge Application Server Registration p. 52
7.12.1.3 EAS-initiated Edge Application Server De-registration p. 53
7.12.1.4 EES-initiated Edge Application Server De-registration p. 54
7.12.1.5 Edge Application Server Subscription and Notification p. 55
7.12.1.6 Edge Application Server Registration using CAPIF p. 57
7.12.1.7 Edge Application Server De-registration using CAPIF p. 58
7.12.2 Solution evaluation p. 58
7.13 Solution #13: Discovery of Edge Data Network and Edge Application Server p. 59
7.13.1 Solution description p. 59
7.13.1.1 General p. 59
7.13.1.2 Procedure for Edge Data Network Selection p. 59
7.13.1.3 Procedure for Edge Application Server Discovery p. 60
7.13.1.4 Edge Application Server Discovery with EDNCS p. 61
7.13.2 Solution evaluation p. 63
7.14 Solution #14: User plane management event API p. 63
7.14.1 Solution description p. 63
7.14.1.1 General p. 63
7.14.1.2 User plane management event API - Request-Response model p. 64
7.14.1.3 User plane management event API - Subscribe-Notify model p. 64
7.14.1.4 API description p. 66
7.14.2 Solution evaluation p. 67
7.15 Solution #15: Edge Application Server's service APIs publish and discovery using CAPIF p. 67
7.15.1 Solution description p. 67
7.15.1.1 Distributed CAPIF p. 67
7.15.1.2 Centralized CAPIF p. 69
7.15.2 Solution evaluation p. 70
7.16 Solution #16: Edge Enabler Server initiated application context relocation p. 71
7.17 Solution #17: Registering Edge Enabler Server on Edge Data Network Configuration Server p. 73
7.18 Solution #18: Fetch target edge Application Server API p. 74
7.18.1 Solution description p. 74
7.18.2 Solution evaluation p. 76
7.19 Solution #19: Fetching target Edge Enabler Server information from EDNCS p. 76
7.20 Solution #20: Application Client initiated relocation of application context p. 77
7.21 Solution #21: Edge Enabler Client triggered application context relocation p. 79
7.21.1 Solution description p. 80
7.21.1.1 Edge Enabler Client triggered and source EES determined Application Context Relocation p. 80
7.21.2 Solution evaluation p. 81
7.22 Solution #22: Distributing Edge Application Server information p. 82
7.23 Solution #23: EAS discovery without registration to EES p. 83
7.23.1 Solution description p. 83
7.23.1.1 Edge Data network service execution p. 83
7.23.1.2 Example Discovery methods p. 84
7.23.1.2.1 HTTPS based protocol p. 85
7.23.1.2.2 Using DNS p. 85
7.23.2 Solution evaluation p. 85
7.24 Solution #24: Edge Application Server Discovery using DNS p. 85
7.25 Solution #25: Client Information API p. 87
7.26 Solution #26: Enhancements to CAPIF with serving area information p. 90
7.27 Solution #27: Relocation of application context considering analytics p. 90
7.28 Solution #28: EEC subscription for EDNCS events p. 92
7.28.1 Solution description p. 92
7.28.1.1 General p. 92
7.28.1.2 Subscription for notification p. 93
7.28.1.2.1 Procedure p. 93
7.28.1.3 Subscription update/cancellation p. 94
7.28.1.3.1 Procedure p. 94
7.28.1.4 Notifications from the Edge Data Network Configuration Server p. 94
7.28.1.4.1 Procedure p. 94
7.28.2 Solution evaluation p. 95
7.29 Solution #29: Lifecycle management assistance p. 95
8 Identities and commonly used values p. 96
8.1 General p. 96
8.2 Edge Enabler Client ID p. 96
8.3 Edge Enabler Server ID p. 96
8.4 Edge Application Server ID p. 96
8.5 Edge Application Server Instance ID p. 97
8.6 Application Client ID p. 97
8.7 Application Client Instance ID p. 97
8.8 UE ID p. 97
8.9 UE Location p. 97
9 Deployment scenarios p. 97
10 Involved business relationships p. 99
11 Overall evaluation p. 100
11.1 General p. 100
11.2 Architecture evaluation p. 100
11.3 Solution evaluations p. 101
11.3.1 General p. 101
11.3.2 Key Issue 2 solutions p. 103
11.3.3 Key Issue 3 solutions p. 103
11.3.4 Key Issue 4 Solutions p. 104
11.3.5 Key Issue 7 Solutions p. 104
11.3.6 Key Issue 9 Solutions p. 105
12 Conclusions p. 106
A Analysis of edge computing standards p. 109
A.1 Edge computing support in 3GPP 5GS p. 109
A.1.1 Description p. 109
A.1.2 Analysis of terminologies p. 109
A.2 Analysis of ETSI MEC p. 109
A.2.1 Introduction p. 109
A.2.2 MEC framework and architecture p. 109
A.2.2.1 Reference architecture p. 109
A.2.2.2 MEC application enablement p. 110
A.2.2.3 MEC services p. 110
A.2.2.4 Application lifecycle and package management p. 110
A.2.2.5 Device application interface p. 110
A.2.2.6 ETSI ISG MEC version of Edge Application Server registration p. 110
A.2.3 Mapping of ETSI MEC and EDGEAPP architecture p. 112
B EEC decomposition p. 112
$ Change History p. 113
