EHE

Edge Hosting Environment

Services →
Introduced in Rel-17 Also in: Services

EHE is a standardized 3GPP framework for deploying and managing applications at the network edge to enable low-latency services and provide a consistent hosting environment across operator networks.

Category
Services
Introduced
Rel-17
Where
Core Network › 5G Core
Also touches
1 segments
Specifications
5 specs
EHE Description Purpose Related Classification Detected Changes Specifications

Description

The Edge Hosting Environment (EHE) is a 3GPP architectural framework and set of capabilities defined to support the deployment, execution, and management of applications and network functions at the edge of the operator's network. It is part of the broader edge computing ecosystem in 5G, often associated with Multi-access Edge Computing (MEC). The EHE provides a standardized environment that abstracts underlying network and hardware resources, allowing application providers to deploy their services in a consistent manner across different operator networks. Architecturally, the EHE is typically realized within an Edge Application Server or Edge Enabler Server, which hosts the environment and interacts with core network functions like the Network Exposure Function (NEF) and the User Plane Function (UPF).

The EHE works by offering a set of services and APIs to edge applications. These include lifecycle management (onboarding, instantiation, termination), traffic steering rules to route relevant user plane data to the application, access to network and user status information (with proper authorization), and connectivity to other network functions. Key components include the EHE Platform, which provides the runtime environment, and the EHE Management System, which handles orchestration and policy enforcement. The environment ensures applications can leverage network capabilities like location services, bandwidth management, and quality of service (QoS) enforcement dynamically.

Its role in the network is to bridge the gap between telco infrastructure and third-party application developers. By providing a standardized hosting environment at the edge, it enables ultra-low latency applications, reduces backhaul traffic, and allows for context-aware service delivery. The EHE is integral to realizing the full potential of 5G for use cases like augmented reality, industrial automation, and real-time video analytics, where processing must occur geographically close to the end-user or data source to meet performance requirements.

Purpose & Motivation

The EHE was created to address the fragmentation and complexity in deploying edge applications across diverse telecom operator networks. Before standardization, edge computing initiatives like ETSI MEC provided frameworks, but full integration with 3GPP mobile core networks required proprietary solutions. This made it difficult for application developers to create services that could run seamlessly on any operator's edge infrastructure. The EHE standardizes the interface between applications and the network edge, solving the problem of vendor lock-in and enabling scalable edge service ecosystems.

Introduced in 3GPP Release 17 as part of the enablers for edge computing, the EHE's motivation stems from the need to expose network capabilities securely and efficiently to authorized applications. It allows operators to monetize their edge real estate by offering a platform for third-party services while maintaining control over network resources and user privacy. The EHE addresses limitations of previous ad-hoc approaches by defining clear architectural roles, reference points, and procedures for application lifecycle management, traffic influence, and network information exposure, thereby accelerating the adoption of edge computing in 5G.

Classification

Part ofMEC
Related approachesNEF

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-17 1 change

In Release 17, corrections and clarifications were made to the Edge Hosting Environment (EHE) within the Edge Computing architecture. The enhancements specifically addressed the procedure for BaselineDNSPattern management in the EASDF to support EAS discovery. Furthermore, the release detailed the operational scenarios for accessing an EHE in a Visited PLMN, including the Home-Routed traffic with Session Breakout (HR-SBO) roaming case.

  • Correction related EHE in EC architecture TS 23.548CR0046

Explore further

Broader topics and technologies where EHE plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.548 vj50 5G System Edge Computing Enhancements Rel-19
TS 23.700 vk00 XR Services Application Enablement Layer Rel-20
TS 29.558 vj40 Enabling Edge Applications Rel-19
TS 29.591 vj40 5G NEF Southbound Services Stage 3 Rel-19
TR 33.739 vi10 Study on security enhancement of support for Rel-18
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.