Description
The Home Environment Value Added Service Provider (HE-VASP) is a role defined in 3GPP specifications that represents an external service provider which has a formal agreement with the Home Environment (HE) of a mobile subscriber. The Home Environment is the entity that manages the subscriber's profile and services, typically the Home Public Land Mobile Network (HPLMN) or an equivalent service provider. The HE-VASP collaborates with the Home Environment to deliver value-added services (VAS) to the user. These services can range from multimedia content, location-based services, messaging, to enterprise applications. The key characteristic is that the Home Environment manages the delivery of these services in a controlled manner, ensuring that the user experience is seamless and that the services are integrated into the user's subscription.
Architecturally, the HE-VASP does not directly interact with the user's device; instead, it interfaces with the Home Environment through standardized or proprietary interfaces. The Home Environment acts as a broker or gateway, aggregating services from multiple HE-VASPs and presenting them to the user as part of their home service package. This abstraction allows the user to access services without needing to manage multiple provider relationships. The HE-VASP may provide one or more services, and the same service could be offered by multiple HE-VASPs, giving the Home Environment flexibility in sourcing services. The specifications 22.121 and 22.127 define the service aspects, while 23.127 and 23.198 cover the technical realization, including the OSA/Parlay architecture that enables third-party service providers to access network capabilities.
The operation of HE-VASP relies on service capability servers (SCS) and service capability features (SCF) as defined in the Open Service Access (OSA) framework. The Home Environment exposes network capabilities such as call control, location, and messaging through standardized APIs. The HE-VASP uses these APIs to build services. For example, a HE-VASP could offer a location-based advertising service by querying the user's location through the OSA location API. The Home Environment enforces policies, authentication, and authorization, ensuring that only authorized HE-VASPs can access user data and that privacy is maintained. The user is typically unaware of which HE-VASP provides a particular service; the Home Environment handles the selection and orchestration.
Key components involved include the OSA Gateway, which provides the secure interface between the Home Environment and HE-VASPs, and the Service Capability Servers, which implement the actual network capabilities. The HE-VASP may also interact with the Home Environment's subscriber database to personalize services. The specifications 29.198 define the OSA API, which is a set of CORBA-based interfaces that allow applications to access network functions. This architecture enables rapid service creation and deployment without requiring the HE-VASP to have deep knowledge of the underlying network protocols.
In summary, HE-VASP is a fundamental concept in 3GPP's service architecture, enabling a vibrant ecosystem of third-party service providers while maintaining the Home Environment's control over the user experience. It allows operators to offer differentiated services and monetize network assets through partnerships, while ensuring security, privacy, and seamless integration. The concept has evolved from R99 to Rel-19, with the core definition remaining stable, reflecting its enduring relevance in mobile service delivery.
Purpose & Motivation
The HE-VASP concept was introduced to address the need for a structured framework that allows external service providers to offer value-added services to mobile subscribers without requiring direct integration with each operator's network. Before this, service delivery was largely operator-centric, with limited ability for third parties to access network capabilities. The HE-VASP model solves this by defining a clear business and technical relationship between the Home Environment and the service provider, mediated by standardized interfaces such as OSA/Parlay. This enables operators to leverage their network assets and offer a wider range of services, while third parties can reach a large subscriber base with minimal integration effort.
The motivation also included the desire to create a competitive marketplace for services, where multiple HE-VASPs can offer similar services, and the Home Environment can select the best offerings. This fosters innovation and reduces time-to-market for new services. The transparency to the user is a key goal: users should not need to know which provider delivers a service, as long as it works seamlessly within their subscription. This requires the Home Environment to manage service orchestration, authentication, and billing, which are complex tasks that the HE-VASP model abstracts away from the user.
Historically, the HE-VASP concept emerged in R99 as part of the early efforts to open up mobile networks to third-party applications. It was refined in Rel-5 with additional wording to clarify the managed and transparent nature of service delivery. The concept has remained largely unchanged since then, indicating its stability and continued applicability. It laid the groundwork for later service architectures such as IMS and the Service Capability Exposure Function (SCEF) in 4G and 5G, which further evolved the idea of exposing network capabilities to external providers.
What changed in its specifications
The latest release-to-release comparison of specifications that define HE-VASP. Each summary describes the whole specification, not only this term.
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 →Topology hiding, policy management, service subscription, API accounting, identity management, and content management are the main additions in OSA Rel-8.
Full comparison in TS 22.127 →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.
Wording changed to add: 'The Home Environment provides services to the user in a managed way, possibly by collaborating with HE-VASPs, but this is transparent to the user. The same service could be provided by more than one HE-VASP and each HE-VASP can provide more than one service.' This expanded the definition to clarify the managed and transparent nature of service delivery and the multiplicity of providers.
Defining Specifications
3GPP specifications that define or reference HE-VASP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 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 23.127 v610 | Virtual Home Environment Stage 2 Specification | Rel-6 read |
| TS 23.198 v900 | Open Service Access (OSA) Stage 2 | Rel-9 read |
| TS 29.198 v340 | OSA R99 API Stage 3 Specification | R99 read |