Description
The Visited Edge Configuration Server (V-ECS) is a service capability introduced in 5G to support edge computing for roaming users. It is a network function located within the Visited Public Land Mobile Network (VPLMN) that acts as a configuration and discovery server for Edge Computing Service (ECS) information. When a User Equipment (UE) roams into a visited network, the V-ECS provides it with the necessary configuration data to access local edge computing resources, such as Edge Application Server (EAS) instances or local data networks (LDNs). This enables the UE to utilize low-latency services hosted at the network edge of the visited operator.
Architecturally, the V-ECS interacts with the Home Edge Configuration Server (H-ECS) in the user's home network. The H-ECS may provide the UE with initial edge service profiles or policies. When the UE moves to a visited network, it can contact the V-ECS (discovered via mechanisms like DNS or local configuration) to obtain visited-network-specific edge configuration. The V-ECS communicates with local edge service providers and network functions to gather up-to-date information about available edge services, their capabilities, and access points. It typically exposes a service-based interface, likely based on HTTP/2 or similar protocols, as defined in 3GPP service-based architecture.
How it works: The UE sends a request to the V-ECS, possibly authenticated and authorized via the home network. The V-ECS processes this request, potentially consulting local policy or the H-ECS for subscriber-specific allowances. It then returns a configuration response containing details such as Fully Qualified Domain Names (FQDNs) or IP addresses of local EASs, connectivity parameters for edge data networks, and service-level agreements. The UE uses this information to establish a PDU session or connection towards the local edge resources, bypassing longer paths to the home network. The V-ECS plays a crucial role in the Edge Computing Enabler Layer, bridging the gap between roaming mobility and edge service accessibility.
Purpose & Motivation
The V-ECS was created to extend the benefits of edge computing—ultra-low latency and localized data processing—to roaming subscribers. Prior to its introduction, edge services were largely accessible only in the home network, meaning a roaming user would have to connect back to their home region for edge applications, negating the latency advantages. This was a significant limitation for use cases like industrial IoT, autonomous driving, and augmented reality, which require consistent low-latency performance regardless of location.
Introduced in 3GPP Release 18 as part of the enhanced edge computing framework, the V-ECS addresses this problem by allowing visited operators to expose their local edge infrastructure to roaming users in a controlled manner. It solves the service discovery and configuration challenge in a roaming context, enabling seamless access to local edge services. Its development was motivated by the industry push for global edge service interoperability and the need to support new business models where operators can offer edge computing as a service to each other's customers. The V-ECS facilitates these roaming agreements by providing a standardized way to configure UEs for local edge access.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (8 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 17, the V-ECS (Visited Edge Configuration Server) function was introduced to support UEs that are roaming, enabling the EEC in the UE to obtain edge enabler layer services from the V-ECS and a V-EES. This was defined within roaming architectures, utilizing the EDGE-10 reference point between the H-ECS and V-ECS for exchanging ECS profile and EDN configuration information. The release also included updates and corrections to the ECS configuration information.
In Release 18, the V-ECS function was enhanced to support the provisioning of ECS configuration information together with the PLMN ID to the 5GC, enabling more integrated network-aware edge configuration. The release also introduced the use of an ECS profile as a more structured alternative to raw configuration information and defined specific authentication methods for securing the ECS configuration process. These updates built upon the existing EDGE-10 reference point used for exchanging ECS profiles and EDN configuration information between ECSs, particularly in roaming scenarios where the EEC obtains services from the V-ECS.
- Provision ECS configuration information together with PLMN ID to 5GC TS 23.558CR0361
- Use of ECS profile instead of ECS configuration information TS 23.558CR0370
- Authentication methods in ECS configuration TS 23.558CR0429
- Correction for bundle in EDN configuration information TS 23.558CR0452
- Corrections to ECS configuration information TS 23.558CR0213
In Release 19, the new capability for the Visited Edge Configuration Server (V-ECS) is the instigation of an Application Context Transfer (ACR) at the Edge Enabler Server (EES). This enhancement enables the V-ECS, which provides edge enabler layer services to a roaming UE's EEC, to trigger the transfer of Application Context data between Edge Application Servers as part of service continuity procedures. This allows the V-ECS to more actively manage application state for UEs accessing edge services in a visited network.
- Instigating ACR at the edge enabler server (EES) TS 23.558CR0561
Explore further
Broader topics and technologies where V-ECS plays a role.
Defining Specifications
3GPP specifications that define or reference V-ECS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.558 vk00 | Architecture for Edge Applications | Rel-20 |
| TR 33.739 vi10 | Study on security enhancement of support for | Rel-18 |