Description
The Enterprise Application Server (EAS) is a key architectural component introduced in 3GPP Release 15 as part of the 5G system's support for vertical industries and enterprise services. It is essentially a server or a platform that resides within an enterprise's premises or at the network edge, hosting application logic and services tailored to specific business needs. The EAS interacts with the 5G core network via standardized interfaces, allowing it to utilize network capabilities such as Quality of Service (QoS), location services, and network status information. Its architecture is designed to be flexible, supporting deployment in private 5G networks, public network slices, or hybrid models.
How the EAS works involves several key components and procedures. The EAS registers itself with the 5G core network, specifically with the Network Exposure Function (NEF) and the Network Repository Function (NRF), making its services discoverable to authorized User Equipment (UE) and other network functions. When a UE needs to access an enterprise application, the 5G core can route traffic to the appropriate EAS based on policies, user subscription, and application requirements. The EAS can also request network capabilities through the NEF, for example, to trigger QoS changes or obtain UE location information, enabling context-aware applications. The communication between the UE and EAS can be optimized for low latency by deploying the EAS at the edge of the network, close to the end-users.
The role of the EAS in the network is to bridge the gap between generic cellular connectivity and specialized enterprise applications. It allows enterprises to move beyond simple connectivity to offer integrated services that leverage the intrinsic features of the 5G system. For instance, in a factory setting, an EAS might host a real-time machine control application that requires ultra-reliable low-latency communication (URLLC) and access to sensor data from the shop floor. The EAS can interact with the network to ensure the necessary QoS is provided for the control traffic. It also enables service continuity and mobility, as the UE can maintain a session with the EAS even when moving across different radio access points within the enterprise domain.
Purpose & Motivation
The Enterprise Application Server was created to address the growing demand from industries for customized, high-performance applications that leverage 5G network capabilities. Prior to its introduction, enterprise services over cellular networks were often limited to basic connectivity or relied on over-the-top (OTT) applications that had no direct integration with the network. This approach lacked the ability to guarantee performance, leverage network intelligence, or offer seamless mobility within enterprise environments. The rise of Industry 4.0, smart factories, and private networks highlighted the need for a standardized way to host enterprise-specific applications within the network architecture.
The primary problems EAS solves include enabling low-latency edge computing for enterprise applications, providing secure and isolated service environments, and allowing enterprises to control and manage their own services. By hosting applications closer to the end-users (at the edge), EAS reduces latency and backhaul traffic, which is critical for real-time applications like augmented reality, industrial automation, and autonomous vehicles. It also addresses the limitation of one-size-fits-all network services by allowing vertical industries to deploy tailored applications that can interact directly with 5G network functions through exposed APIs.
Historically, the motivation for EAS stems from 3GPP's work on network slicing and edge computing, which laid the groundwork for customized network services. EAS provides the application hosting element that completes the vision of end-to-end network slices for enterprises. It allows operators to offer not just connectivity slices but also value-added application platforms as a service. This creates new business models, enabling enterprises to deploy their own digital transformation initiatives on a reliable, high-performance 5G foundation without building everything from scratch.
Key Features
- Hosts enterprise-specific application logic and services within the 5G network
- Integrates with 5G core via NEF and NRF for service discovery and capability exposure
- Supports deployment at the network edge for low-latency application access
- Can request network capabilities like QoS enforcement and location services
- Enables service continuity and mobility within enterprise domains
- Facilitates private network and network slicing scenarios for vertical industries
Evolution Across Releases
Introduced as part of 5G system architecture for vertical support. Defined basic architecture for EAS registration, discovery, and interaction with 5G core network functions like NEF and NRF. Focused on enabling edge computing and enterprise application hosting.
Enhanced integration with edge computing (EDGEAPP) and service-based architecture. Introduced improved procedures for EAS discovery, selection, and traffic routing based on UE location and application requirements. Added support for enhanced URLLC and industrial IoT scenarios.
Further refined EAS capabilities with the introduction of the Edge Application Server Discovery Function (EASDF). Strengthened support for application mobility and session continuity. Expanded APIs for network capability exposure to EAS.
Enhanced support for AI/ML-driven applications and network automation. Improved scalability and management of multiple EAS instances in large enterprise deployments. Further integration with network slicing for dedicated enterprise slices.
Continued evolution for advanced enterprise use cases, including extended reality (XR) and digital twins. Enhanced security and isolation mechanisms for multi-tenant EAS deployments.
Ongoing enhancements for 5G-Advanced, focusing on convergence with cloud-native principles and further API standardization. Aimed at seamless integration of EAS with AI and compute resources across the network.
Defining Specifications
| Specification | Title |
|---|---|
| TS 23.255 | 3GPP TS 23.255 |
| TS 23.433 | 3GPP TS 23.433 |
| TS 23.436 | 3GPP TS 23.436 |
| TS 23.548 | 3GPP TS 23.548 |
| TS 23.558 | 3GPP TS 23.558 |
| TS 23.700 | 3GPP TS 23.700 |
| TS 23.748 | 3GPP TS 23.748 |
| TS 23.758 | 3GPP TS 23.758 |
| TS 23.958 | 3GPP TS 23.958 |
| TS 24.501 | 3GPP TS 24.501 |
| TS 24.543 | 3GPP TS 24.543 |
| TS 24.558 | 3GPP TS 24.558 |
| TS 26.506 | 3GPP TS 26.506 |
| TS 26.510 | 3GPP TS 26.510 |
| TS 26.512 | 3GPP TS 26.512 |
| TS 26.804 | 3GPP TS 26.804 |
| TS 26.812 | 3GPP TS 26.812 |
| TS 26.998 | 3GPP TS 26.998 |
| TS 28.538 | 3GPP TS 28.538 |
| TS 28.815 | 3GPP TS 28.815 |
| TS 28.843 | 3GPP TS 28.843 |
| TS 28.844 | 3GPP TS 28.844 |
| TS 28.879 | 3GPP TS 28.879 |
| TS 29.508 | 3GPP TS 29.508 |
| TS 29.512 | 3GPP TS 29.512 |
| TS 29.514 | 3GPP TS 29.514 |
| TS 29.519 | 3GPP TS 29.519 |
| TS 29.522 | 3GPP TS 29.522 |
| TS 29.549 | 3GPP TS 29.549 |
| TS 29.558 | 3GPP TS 29.558 |
| TS 29.591 | 3GPP TS 29.591 |
| TS 32.257 | 3GPP TR 32.257 |
| TS 32.972 | 3GPP TR 32.972 |
| TS 33.127 | 3GPP TR 33.127 |
| TS 33.163 | 3GPP TR 33.163 |
| TS 33.739 | 3GPP TR 33.739 |
| TS 33.749 | 3GPP TR 33.749 |
| TS 33.839 | 3GPP TR 33.839 |