Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

EAS

Enterprise Application Server

Services →

EAS is a network function that hosts and executes enterprise-specific applications within a 5G system to enable custom services close to users.

Introduced
Rel-15
Where
Services › Codecs
Specifications
38 specs
Also in
Core Network, Management, Security
EAS Description Purpose What changed Neighbours Detected Changes Specifications

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.

What changed in its specifications

The latest release-to-release comparison of specifications that define EAS. Each summary describes the whole specification, not only this term.

TS 23.255Rel-18 → Rel-19

Rel-19 added real-time flight path reporting, QoS-based flight route selection, no-transmit zone management, and supporting APIs/procedures for UAS applications.

Full comparison in TS 23.255 →
TS 23.433Rel-18 → Rel-19

Rel-19 added SEALDD procedures for connection status, policy, background data, ACR events, multi-modal service, bandwidth, and delay-tolerant satellite transmission, plus SEALDD-enabled XR data transmission APIs.

Full comparison in TS 23.433 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (306 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-15, normative work from Rel-16.

Rel-16 1 change
  • Corrections to EAS and IMSI TLVs in 33163 TS 33.163CR0013
Rel-17 50 changes
  • EAS rediscovery TS 24.501CR3386
  • Adding EAS IP replacement information in AppRelocationInfo TS 29.508CR0149
  • Support of Network Exposure to EAS via Local NEF TS 29.512CR0782
  • Adding EAS IP replacement information in PCC rules TS 29.512CR0862
  • Support of AF triggered EAS rediscovery TS 29.512CR0883
  • Support of Network Exposure to EAS via Local NEF. TS 29.514CR0314

+ 44 more changes

Rel-18 180 changes
  • Support of influencing UPF and EAS (re)location for collections of UEs TS 23.548CR0070
  • KI#4 common EAS enforcement for set of UEs TS 23.548CR0075
  • Influencing UPF and EAS (re)location for collections of UEs TS 23.548CR0082
  • EAS Re-discovery Procedure with EASDF in HR roaming scenario TS 23.548CR0073
  • KI#4: AF traffic influence for common EAS, DNAI selection TS 23.548CR0087
  • The EAS discovery procedure with V-EASDF using IP replacement mechanism for supporting HR-SBO TS 23.548CR0088

+ 174 more changes

Rel-19 73 changes
  • KI#1 EAS rediscovery for PDU session with local SMF TS 23.548CR0242
  • Addition of N6 delay measurement based EAS (re-)discovery enhancement TS 23.548CR0248
  • Common EAS bundle with repository TS 23.558CR0501
  • Update ECS functionality to support Common EAS bundle TS 23.558CR0510
  • Common EAS in partner ECSP TS 23.558CR0528
  • Common EAS procedures – putting together TS 23.558CR0566

+ 67 more changes

Rel-20 2 changes
  • EAS discovery with energy related information TS 23.558CR0752
  • Align the service operation with procedure for EAS deployment information creation and update TS 29.522CR1917

Defining Specifications

3GPP specifications that define or reference EAS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.255 vk10 UAS Application Enabler Architecture Rel-20 read
TS 23.433 vk40 SEAL Data Delivery Architecture Rel-20 read
TS 23.436 vk20 Application Data Analytics Enablement Rel-20 read
TS 23.548 vk00 5G Edge Computing Stage 2 Architecture Rel-20 read
TS 23.558 vk30 Enabling Edge Applications Rel-20 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TR 23.748 vh00 Edge Computing Enhancement Study for 5GC Rel-17 read
TR 23.758 vh00 Study on Edge Application Architecture Rel-17 read
TR 23.958 vj00 EDGEAPP alignment with ETSI MEC and GSMA OP Rel-19 read
TS 24.501 vk10 5GS NAS Protocol Specification Rel-20 read
TS 24.543 vk10 SEAL Data Delivery Management Protocol Rel-20 read
TS 24.558 vk00 Edge Application Enabler Server APIs Stage 3 Rel-20 read
TS 26.506 vk00 5G Real-Time Media Communication Architecture Rel-20 read
TS 26.510 vj20 5G Media Streaming and Real-Time Communication APIs Rel-19 read
TS 26.512 vj30 5G Media Streaming Protocols and APIs Rel-19 read
TS 26.804 vk10 5G Media Delivery Architecture Extensions Rel-20 read
TR 26.812 vi10 Technical Report Rel-18 read
TR 26.998 vj00 5G AR/MR Glasses Integration Study Rel-19 read
TS 28.538 vj50 Management and orchestration for edge computing Rel-19 read
TR 28.815 vh00 Charging Study for Edge Computing Rel-17 read
TR 28.843 vi10 Technical Report on Charging Aspects for Vertical Scenarios Rel-18 read
TR 28.844 vi00 Technical Report on Charging Aspects of Satellite in 5GS Rel-18 read
TS 28.879 vj10 OAM for Service Management Exposure Study Rel-19 read
TS 29.508 vk10 Session Management Event Exposure Service Rel-20 read
TS 29.512 vk10 Session Management Policy Control Service Stage 3 Rel-20 read
TS 29.514 vk10 Policy Authorization Service Rel-20 read
TS 29.519 vk10 5G UDR Policy and Application Data Services Rel-20 read
TS 29.522 vk10 NEF Northbound Interface Rel-20 read
TS 29.549 vk10 SEAL Service APIs Rel-20 read
TS 29.558 vk00 Edge Application Enablement APIs Rel-20 read
TS 29.591 vk10 NEF Southbound Services Rel-20 read
TS 32.257 vj00 Edge Computing Charging Management Rel-19 read
TR 32.972 vj00 Energy Efficiency Study for 5G Networks Rel-19 read
TS 33.127 vj80 Lawful Interception Architecture Rel-19 read
TS 33.163 vj00 Battery Efficient Security for Low Throughput MTC Rel-19 read
TR 33.739 vi10 Study on security enhancement of support for Rel-18 read
TS 33.749 vj00 Study on security aspects of edge computing enhancement Rel-19 read
TR 33.839 vh10 Edge Computing Security Study for 5G Core Rel-17 read