WSP

Web Service Provider

Services →
Introduced in Rel-2

WSP is an entity that provides web-based services, often location-based services, to end-users or other network entities within the 3GPP service architecture framework.

Category
Services
Introduced
Rel-2
Where
Services
Specifications
4 specs
WSP Description Purpose Related Specifications

Description

The Web Service Provider (WSP) is a logical role defined within the context of 3GPP specifications for service architectures, particularly those related to value-added services like Location Services (LCS) and Multimedia Messaging Service (MMS). As per specifications like TS 23.140 (Multimedia Messaging Service (MMS)) and TS 23.057 (Location Services (LCS)), the WSP is an application-level entity that hosts and delivers services, often via HTTP or other web protocols, to clients. It is a key component in the service layer, interacting with the core network to request network capabilities such as user location or messaging transport.

Architecturally, the WSP resides outside the trusted 3GPP network boundary but interfaces with it through standardized gateways and interfaces. For Location Services, a WSP would communicate with the Gateway Mobile Location Centre (GMLC) via the Le interface to request the location of a target user. For MMS, the WSP may interact with the MMSC (Multimedia Messaging Service Centre). The WSP implements the service logic, user interfaces, and application servers that consume network enablers. Its operation involves sending service requests (e.g., a location request), receiving responses from the network, and processing that data to deliver a final service to the end-user or a corporate client.

Key components in relation to a WSP include the 3GPP core network elements (like GMLC, HSS, MMSC), the standardized open interfaces (Le, Mm1), and the WSP's own application servers. Its role is to leverage standardized network capabilities to create marketable services, enabling a ecosystem where third-party providers can offer innovative applications. The security of interactions between the WSP and the 3GPP network is governed by specifications like TS 33.980, which details security requirements for location-based services.

Purpose & Motivation

The concept of the Web Service Provider was formalized to enable and regulate the provision of value-added services by entities external to the mobile network operator. This was driven by the industry's shift towards open service architectures in the early 2000s, where operators sought to expose network capabilities securely to third parties to spur innovation and create new revenue streams. Prior approaches often locked services within the operator's walled garden, limiting variety and growth.

The WSP role specifically addresses the problem of how to securely and reliably allow external application providers to access sensitive network functions, such as a subscriber's location. It solves this by defining a clear architectural role, standardized interfaces (like the Le interface for LCS), and associated security protocols. This created a business-to-business (B2B) model for services, motivating the creation of a vibrant ecosystem of location-based services, multimedia messaging applications, and later, broader IoT and API-driven services. It was a foundational step in the evolution from closed telecom networks to open platforms.

Evolution Across Releases

Rel-2 Initial

The concept was introduced in early releases within the context of Location Services (LCS) and other value-added services. The initial architecture defined the WSP as an external entity accessing network capabilities, like user location, through the Gateway Mobile Location Centre (GMLC), establishing the basic B2B service model.

Explore further

Broader topics and technologies where WSP plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 23.057 vj00 Mobile Execution Environment (MExE) Specification Rel-19
TS 23.140 v1600 MMS Non-Realtime Service Definition Rel-6
TR 33.980 vj00 GAA & Liberty Alliance Interworking Guidelines Rel-19