Tech-invite  3GPPspecsRELsGlossariesSIP
21222324252627282931323334353637384‑5x

Top   in Index   Prev   Next

TR 23.758SA6
Study on Application Architecture
for enabling Edge Applications

use "3GPP‑Page" to get the Word version
for a better overview, the Table of Contents (ToC) is reproduced
V17.0.0 (Wzip)2019/12  113 p.

WI Acronym:  FS_EDGEAPP
Rapporteur:  Mr. Gupta, NishantSamsung Electronics Co., Ltd

Edge Computing is a network architecture concept that enables cloud computing capabilities and service environments to be deployed at the edge of the cellular network. It promises several benefits such as lower latency, higher bandwidth, reduced backhaul traffic and prospects for several new services. This technical report identifies the key issues and corresponding application architecture and related solutions with recommendations for the normative work.
The aspects of the study include identifying architecture requirements (e.g. discovery of edge services, authentication of the clients), supporting application layer functional model and corresponding solutions to enable the deployment of applications on the edge of 3GPP networks, with no impact to edge-unaware applications on the UE and minimal impact to edge-aware applications on the UE.

full Table of Contents for  TR 23.758  Word version:   17.0.0

Here   Top
1  ScopeWord-p. 9
2  References
3  Definitions, symbols and abbreviationsWord-p. 10
4  Key issuesWord-p. 12
5  Architectural requirementsWord-p. 17
6  Application architecture for enabling edge applications
7  SolutionsUp
7.1  Solution #1: Edge Application Server Discovery
7.2  Solution #2: Provisioning of Edge Data Network configuration
7.3  Solution #3: Edge Data Network using LADN
7.4  Solution #4: Location Reporting API
7.5  Solution #5: UE Identifier APIWord-p. 35
7.6  Solution #6: Service Authorization for Edge Computing service
7.7  Solution #7: Dynamic availability of Edge Application Servers
7.8  Solution #8: Registering Edge Enabler Client on Edge Enabler Server
7.9  Solution #9: Relocation of application contextWord-p. 43
7.10  Solution #10: Network capability exposure to Edge Application Server using CAPIFWord-p. 46
7.11  Solution #11: QoS Management for 5G Edge ApplicationsUp
7.12  Solution #12: Edge Application Server Enablement
7.13  Solution #13: Discovery of Edge Data Network and Edge Application ServerWord-p. 59
7.14  Solution #14: User plane management event APIUp
7.15  Solution #15: Edge Application Server's service APIs publish and discovery using CAPIF
7.16  Solution #16: Edge Enabler Server initiated application context relocationWord-p. 71
7.17  Solution #17: Registering Edge Enabler Server on Edge Data Network Configuration Server
7.18  Solution #18: Fetch target edge Application Server API
7.19  Solution #19: Fetching target Edge Enabler Server information from EDNCSUp
7.20  Solution #20: Application Client initiated relocation of application contextWord-p. 77
7.21  Solution #21: Edge Enabler Client triggered application context relocation
7.22  Solution #22: Distributing Edge Application Server informationWord-p. 82
7.23  Solution #23: EAS discovery without registration to EES
7.24  Solution #24: Edge Application Server Discovery using DNSUp
7.25  Solution #25: Client Information API
7.26  Solution #26: Enhancements to CAPIF with serving area informationWord-p. 90
7.27  Solution #27: Relocation of application context considering analytics
7.28  Solution #28: EEC subscription for EDNCS events
7.29  Solution #29: Lifecycle management assistance
8  Identities and commonly used values
9  Deployment scenarios
10  Involved business relationships
11  Overall evaluationWord-p. 100
12  ConclusionsWord-p. 106
A  Analysis of edge computing standardsWord-p. 109
B  EEC decomposition
C  Change historyWord-p. 113

Up   Top