Description
EDGEAPP (Edge Application) is a 3GPP term introduced in Release 19 and documented in specification 23.700, which covers study and technical reports on architecture enhancements. It refers to applications that are hosted at the edge of the mobile network — that is, in close proximity to the radio access network (RAN) — rather than in a centralized cloud or distant data center. Edge applications are a key enabler of edge computing in 5G and beyond, allowing services to benefit from reduced latency, lower backhaul traffic, and improved context awareness.
In the 3GPP architecture, edge computing is supported through the Edge Application Server (EAS) and Edge Enabler Server (EES) functions, as defined in specifications like TS 23.501 and TS 23.558. The EAS hosts the actual application logic, while the EES provides supporting capabilities such as service provisioning, registration, and discovery. The Edge Enabler Client (EEC) resides in the User Equipment (UE) and interacts with the EES to discover and connect to available edge applications. The network exposes edge computing capabilities via the Network Exposure Function (NEF) and the Unified Data Repository (UDR), enabling application functions to influence traffic routing and quality of service.
EDGEAPP in the context of 3GPP Release 19 likely refers to the study and specification work on edge applications within the 5G system, including aspects such as application mobility, service continuity, and integration with network slicing. The term may also encompass the broader ecosystem of edge applications that leverage 3GPP-defined enablers like the 5G Edge Computing (5GEC) framework. Key technical considerations include how the network selects an appropriate edge application server based on UE location, how session and service continuity is maintained when a UE moves between edge servers, and how QoS and charging are handled for edge-hosted services.
The architecture for edge applications involves multiple domains: the UE, the 5G RAN, the 5G Core (5GC), and the edge data network (EDN). The 5GC provides connectivity and policy control, while the EDN hosts the edge application servers. 3GPP specifies interfaces such as EDGE-1 (between EEC and EES), EDGE-2 (between EES and ECS), and EDGE-3 (between EES and 5GC) to standardize interactions. These interfaces enable the discovery of edge services, the establishment of user plane paths to edge servers, and the enforcement of policies such as traffic steering and QoS.
EDGEAPP is closely related to other 3GPP edge computing concepts such as the Edge Application Server (EAS), Edge Configuration Server (ECS), and the 5G Edge Computing enablers. It also intersects with network slicing, as edge applications may be deployed on specific network slices tailored to their requirements. For telecom engineers and students, understanding EDGEAPP is essential for designing and deploying low-latency, high-bandwidth services in 5G networks, including augmented reality, cloud gaming, industrial automation, and V2X communications.
Purpose & Motivation
EDGEAPP exists to enable applications to run at the edge of the mobile network, close to the user, thereby reducing latency and improving performance for latency-sensitive and bandwidth-intensive services. Traditional cloud applications are hosted in centralized data centers, which can be hundreds or thousands of kilometers away from the user, introducing significant transport latency. For applications like augmented reality, autonomous driving, and real-time industrial control, such latency is unacceptable. Edge computing solves this by moving compute and storage resources to the network edge, often co-located with the RAN or at a local breakout point.
3GPP's motivation for standardizing edge applications is to ensure interoperability and consistent behavior across different vendors and operators. Without standards, edge computing would be fragmented, with proprietary interfaces and limited scalability. The 3GPP edge computing architecture, including EDGEAPP, provides a standardized framework for discovering, selecting, and connecting to edge applications, as well as for managing their lifecycle and mobility. This enables operators to offer edge services as part of their 5G offerings, creating new revenue streams and differentiating their networks.
Furthermore, EDGEAPP supports the broader 5G vision of enabling vertical industries. By providing low-latency, high-reliability connectivity to edge applications, 3GPP networks can serve use cases in manufacturing, healthcare, transportation, and entertainment. The standardization of edge applications also facilitates multi-access edge computing (MEC) integration, allowing applications to be hosted across different access technologies and network domains.
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Initial introduction of the term EDGEAPP in 3GPP specifications, defined as Edge Application. This release marks the formal recognition and study of edge applications within the 3GPP architecture, building on earlier edge computing work in Releases 15-18. The definition is documented in specification 23.700, which covers study and technical reports.
Defining Specifications
3GPP specifications that define or reference EDGEAPP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 read |