Description
OWSER, formally known as the OMA Web Services Enabler Release, is a 3GPP technical specification (TS 23.222) that establishes a framework for incorporating Open Mobile Alliance service enablers into the 3GPP ecosystem. Its primary function is to define the architectural principles, interfaces, and procedures that allow 3GPP network entities to interact with OMA-defined web service capabilities in a standardized manner. This integration is crucial for enabling service providers to offer advanced, converged services that leverage both telecommunication network features and internet-based application logic.
The architecture specified by OWSER involves defining reference points between 3GPP network functions, such as the IP Multimedia Subsystem (IMS) or the Home Subscriber Server (HSS), and OMA Service Enablers. These enablers are essentially reusable software components that provide common functions like presence, messaging, or device management. OWSER specifies how these enablers are discovered, how they authenticate and authorize requests from network functions, and how the actual service logic is invoked using web services protocols, primarily SOAP/XML over HTTP. It details the necessary adaptations, including security mechanisms and data mapping, to ensure seamless interoperability between the 3GPP and OMA domains.
The specification covers several key aspects: the overall architectural model showing the relationship between 3GPP and OMA domains; the definition of the OWSER Gateway or Adaptation Function, which acts as a mediator translating between 3GPP-specific protocols (like Diameter) and OMA web service interfaces; and the detailed procedures for service invocation, subscription, and notification. By providing this blueprint, OWSER allows network operators to expose network capabilities (like user location or subscription status) to authorized OMA applications securely, enabling the development of rich, context-aware services without requiring application developers to understand the intricacies of the underlying 3GPP signaling protocols.
Purpose & Motivation
OWSER was created to address the growing need for convergence between traditional telecommunications networks and internet-based web services. Prior to its specification, integrating OMA service enablers (which were designed with a web-centric, RESTful or SOAP-based philosophy) with 3GPP networks (which relied on telecom-specific protocols like MAP and Diameter) was a complex, proprietary, and non-interoperable task for vendors and operators. This fragmentation hindered the rapid deployment of innovative blended services that could combine network intelligence with application-layer logic.
The primary motivation was to leverage the rich ecosystem of OMA service enablers—such as those for Presence, Push-to-talk over Cellular (PoC), and Device Management—within the controlled and secure environment of a 3GPP operator's network. OWSER provides the standardized 'glue' that solves this integration problem. It defines a clear, agreed-upon method for service exposure, allowing operators to monetize their network assets by making them available to third-party application providers in a controlled fashion, while also enabling the creation of operator-managed services that are richer and more feature-complete. Its introduction in Release 15 aligned with the broader industry shift towards network openness, API-driven architectures, and the seamless blending of telco and IT capabilities, which are foundational concepts for 5G service-based architectures.
Key Features
- Standardized architecture for integrating OMA web service enablers with 3GPP networks
- Definition of adaptation functions (OWSER Gateway) for protocol translation between telecom and web service domains
- Specification of secure discovery, authentication, and authorization mechanisms for service enablers
- Support for service invocation, subscription, and notification procedures using web services protocols
- Enables exposure of 3GPP network capabilities (e.g., user status, location) to authorized OMA applications
- Facilitates the development of converged, context-aware services by blending network and application logic
Evolution Across Releases
Initial introduction of OWSER in 3GPP. The specification TS 23.222 defined the foundational architecture, principles, and procedures for integrating OMA Web Service Enablers. It established the concept of an adaptation layer between 3GPP network functions and OMA service enablers, detailing the reference points, security model, and basic service invocation mechanisms.
Defining Specifications
| Specification | Title |
|---|---|
| TS 23.222 | 3GPP TS 23.222 |