Edge Hosting Environment

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.

Key Features

• Standardized application lifecycle management (onboarding, instantiation, termination)
• Traffic steering capabilities to direct user plane data to edge applications
• Secure exposure of network status and user information via APIs
• Integration with core network functions like NEF and UPF
• Support for application context transfer and service continuity
• Policy enforcement for resource usage and access control

Evolution Across Releases

Defining Specifications