Value Added Services

Description

Value Added Services (VAS) in 3GPP is not a single technology but a comprehensive framework and set of specifications for enabling, deploying, and managing enhanced services. These services leverage the core network capabilities to offer functionality that is not part of the standard telephony or packet data bearer service. The VAS architecture is distributed and involves several specialized network nodes interacting with the core network. Key architectural components include the VAS platforms themselves (e.g., SMS Center, MMS Center, Location Server, Streaming Server), gateways (e.g., WAP Gateway, Parlay Gateway), and critical support systems like the Charging System (OCS, OFCS) and the Home Location Register (HLR) or Home Subscriber Server (HSS) for subscriber data.

How VAS works depends on the specific service. For a content download VAS, a user's request from their handset is routed via the packet data network to a VAS platform (e.g., a content portal). The platform authenticates the user, often by querying the HSS, processes the request, and delivers the content. Crucially, the entire transaction is tracked for charging. The network's Charging Trigger Function (CTF) generates charging events based on service usage, which are sent to the Online Charging System (OCS) for prepaid or hybrid customers or to the Offline Charging System (OFCS) for postpaid billing. For a network-initiated VAS like a location-based alert, an application server uses a standardized interface (like OSA/Parlay or SCP) to query the network for a user's location and then sends a targeted message.

The role of the VAS framework is to provide the standardized 'plumbing' that allows these diverse services to be integrated securely, reliably, and in a billable manner into the mobile operator's network. It defines the protocols, data formats, and procedures for service invocation, subscriber privacy, quality of service handling, and, most importantly, detailed charging correlation. This enables operators to create complex service bundles and partnerships with third-party content providers while maintaining control over authentication, policy, and revenue collection.

Purpose & Motivation

The concept of VAS exists to monetize the mobile network beyond simple connectivity. The core purpose is to generate additional Average Revenue Per User (ARPU) by offering services that customers perceive as valuable enhancements. From a technical standpoint, the 3GPP VAS specifications were created to solve the problems of chaos and incompatibility. In the early days, vendors and operators developed proprietary platforms, leading to vendor lock-in, inability to mix services from different providers, and complex integration challenges. Standardization was motivated by the need for interoperability, scalability, and the facilitation of a global ecosystem of application and content providers.

It addressed key limitations of ad-hoc service deployment: lack of standardized charging mechanisms made billing difficult; absence of common subscriber data interfaces hindered personalization; and no uniform service management frameworks made operations costly. The 3GPP VAS architecture, particularly as it evolved with the IP Multimedia Subsystem (IMS), provided a structured way to introduce new services. It separated the service layer from the transport layer, allowing services to be developed independently of the underlying access technology (GSM, UMTS, LTE). This framework is what enabled the explosive growth of mobile messaging, mobile internet, app stores, and countless other services by providing a reliable, billable, and manageable platform upon which to build.

Key Features

• Framework for service creation, deployment, and lifecycle management
• Standardized interfaces for third-party service provider access (e.g., OSA/Parlay)
• Integrated, detailed charging mechanisms for service usage (e.g., Diameter Ro/Rf)
• Reliance on core network subscriber data and authentication (HLR/HSS)
• Support for diverse service types: messaging, content, location, presence
• Separation of service logic from transport/connectivity layers

Evolution Across Releases

Defining Specifications