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

Glossary term · Services

VHE

Virtual Home Environment

Services →

VHE is a service architecture concept enabling mobile users to consistently access their personalized services and interface settings as if in their home network, regardless of their location or terminal.

Introduced
R99
Where
Services › IMS
Specifications
23 specs
Also in
Management, Security, Core Network
VHE Description Purpose What changed Neighbours Specifications

Description

The Virtual Home Environment (VHE) is a comprehensive service framework defined in 3GPP that aims to provide users with a consistent set of services, personalized features, and user interface characteristics, as if they were in their home network, irrespective of their physical location or the terminal device they are using. The concept is rooted in the idea of service portability and personalization, which are critical for enhancing user experience in mobile communications. VHE is not a single network element but rather an architectural concept and a set of capabilities distributed across the network, including the home network, visited networks, and the user equipment (UE). It relies on standardized interfaces and service capabilities to ensure that service logic and user preferences can be transferred and executed in visited networks, enabling a seamless experience similar to that in the home environment.

Architecturally, VHE involves several key components and mechanisms. The Home Environment (HE) is responsible for storing the user's service profile, which includes preferences, subscribed services, and user interface settings. This profile is accessed by the Visited Network (VN) when the user roams. The VHE concept leverages the capabilities of the Intelligent Network (IN) and the Customized Applications for Mobile network Enhanced Logic (CAMEL) for service control, as well as the Open Service Architecture (OSA) and the Service Capability Server (SCS) for service exposure and execution. The execution of VHE services in a visited network requires the support of service brokers, which mediate between the home and visited networks to ensure that service logic is correctly interpreted and applied, taking into account the capabilities of the visited network and the terminal.

The operation of VHE involves the dynamic adaptation of services based on the user's context, which includes location, terminal capabilities, and network conditions. When a user roams into a visited network, the VHE system retrieves the user's service profile from the home network. This profile is then used to configure the services available in the visited network to match the user's home environment as closely as possible. This may involve adapting the user interface, enabling specific service features, or even downloading necessary applications or data. The VHE framework supports various service types, including voice, data, and multimedia services, and it is designed to be extensible to accommodate new services as they emerge. The role of VHE in the network is to bridge the gap between different network operators and technologies, providing a unified service experience that fosters user loyalty and enables innovative service offerings.

Purpose & Motivation

The Virtual Home Environment was created to address the challenges of service portability and personalization in mobile networks, particularly in the context of roaming. Before VHE, when users moved between different networks, especially while roaming internationally, they often faced a fragmented experience where services available in their home network were not accessible, or the user interface and service behavior differed significantly. This limitation hindered the adoption of advanced mobile services and reduced user satisfaction. The primary motivation for VHE was to enable service providers to offer a consistent and personalized service experience across network boundaries, thereby enhancing the value proposition of mobile services and encouraging user mobility.

Historically, the development of VHE began in 3GPP Release 99, aligning with the rollout of 3G networks and the increasing emphasis on data services and multimedia applications. The concept was driven by the need to support innovative services that required a high degree of personalization and context-awareness, such as location-based services, multimedia messaging, and mobile commerce. VHE aimed to leverage the capabilities of intelligent networks and open service architectures to decouple service logic from network infrastructure, allowing services to be executed in various network environments. This approach addressed the limitations of earlier systems where services were tightly coupled to specific network elements or operators, making them difficult to port or adapt.

Furthermore, VHE was designed to solve the problem of service interoperability between different operators and technologies. By standardizing the mechanisms for service profile management, service execution, and user interface adaptation, VHE facilitated collaboration between home and visited networks, enabling them to offer a seamless experience to roaming users. This not only improved user convenience but also opened up new business opportunities for operators by allowing them to offer value-added services to visiting subscribers. The evolution of VHE over subsequent 3GPP releases reflects its adaptation to new network architectures, such as IP Multimedia Subsystem (IMS), and its integration with emerging service paradigms, ensuring its relevance in the context of 4G and 5G networks.

What changed in its specifications

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

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 22.101Rel-16 → Rel-17

Rel-17 added support for Multi-USIM devices, emergency call handling, and definitions for MUSIM UEs.

Full comparison in TS 22.101 →

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

R99 Initial

Introduced the initial VHE concept as part of the 3G service architecture, focusing on enabling consistent personal service environment across network boundaries. It defined basic principles for service portability, user profile management, and the use of CAMEL and IN capabilities to support VHE services in roaming scenarios.

Enhanced VHE with support for multimedia services and improved service personalization mechanisms. Introduced better integration with the IP Multimedia Subsystem (IMS) framework, allowing VHE to leverage IMS capabilities for session-based services and richer multimedia applications.

Further aligned VHE with IMS architecture, enabling more advanced service scenarios through the use of SIP-based signaling and service enablers. Added support for presence and group management features, expanding the scope of VHE to include collaborative and context-aware services.

Refined VHE specifications to improve interoperability and performance. Introduced enhancements for service discovery and execution in visited networks, including better mechanisms for adapting services to terminal capabilities and network conditions.

Continued evolution with a focus on service continuity and mobility management. Added support for VHE in the context of fixed-mobile convergence (FMC), enabling seamless service experience across fixed and mobile networks.

Adapted VHE concepts to the evolving network architecture, including support for LTE/EPC. Emphasized the role of VHE in enabling personalized services in all-IP networks, with enhancements for policy control and charging integration.

Defining Specifications

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

SpecificationTitleRelease
TS 21.133 v410 3G Security: Threat Analysis & Requirements Rel-4 read
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 22.100 v370 UMTS Service Requirements for Release '99 R99 read
TS 22.101 vl00 3GPP Service Principles for PLMNs Rel-21 read
TS 22.121 v531 Virtual Home Environment Service Requirements Rel-5 read
TS 22.127 v900 Open Service Access (OSA) Stage 1 Requirements Rel-9 read
TS 22.141 vj00 Presence Service Requirements Rel-19 read
TS 22.228 vl00 IMS Service Requirements Rel-21 read
TS 22.240 vj00 3GPP Generic User Profile Requirements Rel-19 read
TR 22.970 v301 Virtual Home Environment (VHE) Concept and Requirements R99 read
TR 22.975 v310 UMTS Numbering and Addressing Requirements R99 read
TS 23.050 3GPP TS 23.050 R99 read
TS 23.127 v610 Virtual Home Environment Stage 2 Specification Rel-6 read
TS 23.171 v390 LCS Stage 2 for UMTS R99 read
TS 23.221 vj00 3GPP System Architectural Requirements Rel-19 read
TS 23.271 vj00 LCS Stage 2 Specification Rel-19 read
TR 23.923 v300 Mobile IP+ Feasibility Study for UMTS/GPRS R99 read
TS 29.198 v340 OSA R99 API Stage 3 Specification R99 read
TS 32.101 vj00 PLMN Management Principles and Requirements Rel-19 read
TS 32.102 vj00 Telecom Management Physical Architecture Framework Rel-19 read
TS 32.140 vj00 Subscription Management (SuM) requirements Rel-19 read
TS 32.141 vj00 Subscription Management (SuM) Architecture Rel-19 read
TS 33.106 vj00 Lawful Interception Requirements (Pre-Rel-15) Rel-19 read