Description
In the 3GPP ecosystem, a Service Provider (SP) is a broad term for any organization that provides services to subscribers over a 3GPP-compliant mobile network. This includes the traditional Mobile Network Operator (MNO) that owns the radio access and core network infrastructure, as well as Mobile Virtual Network Operators (MVNOs) that lease network capacity from MNOs to offer their own branded services. The SP may also refer to entities providing specific value-added services (e.g., messaging, location-based services) or Internet of Things (IoT) connectivity management.
The SP's role involves several key areas: commercial and business aspects like customer acquisition, billing, and branding; technical service provisioning which includes managing subscriber profiles in the network's Home Subscriber Server (HSS) or Unified Data Management (UDM), defining service policies, and interfacing with the network operator's operational support systems (OSS/BSS). For an MVNO, this involves a business agreement with a host MNO, often requiring standardized interfaces (e.g., for provisioning) as defined in 3GPP specifications.
Architecturally, the SP interacts with the 3GPP network through reference points and interfaces specified for external entities. For example, an SP may host an Application Function (AF) that influences policy control via the N5 interface to the PCF. In IoT scenarios, the SP may operate a Service Capability Exposure Function (SCEF) or Network Exposure Function (NEF) to access network capabilities. The distinction between network operator and service provider can blur in vertically integrated MNOs, but the term SP explicitly focuses on the service offering and customer-facing functions.
Purpose & Motivation
The concept of a Service Provider was formalized in 3GPP to acknowledge and standardize the diverse business models emerging in the telecommunications industry beyond the traditional infrastructure-owning operator. It addresses the need for a clear architectural role for entities that deliver services without necessarily owning the underlying radio network.
This separation enables market flexibility, fostering competition and innovation. It allows MVNOs to enter the market, driving lower prices and niche services. For IoT, it enables specialized providers to offer connectivity management for vertical industries. Standardizing the SP role ensures that interfaces between network operators and service providers are interoperable, secure, and scalable, which is crucial for a healthy ecosystem. It reflects the evolution from monolithic telecom operators to an open ecosystem of service enablers.
What changed in its specifications
The latest release-to-release comparison of specifications that define SP. 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 →Rel-5 added MExE support for IP multimedia services and handling of individual media components in user profiles.
Full comparison in TS 22.057 →Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Introduced the Service Provider as a key architectural entity in the context of service frameworks and network management. It established the foundational distinction between network infrastructure ownership and service provision, particularly relevant for emerging data services and the initial concepts of virtual operators.
Defining Specifications
3GPP specifications that define or reference SP, 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.022 vj00 | ME Personalisation Features for GSM/3G | Rel-19 read |
| TS 22.057 vj00 | Mobile Execution Environment (MExE) Stage 1 | Rel-19 read |
| TS 22.801 vc00 | Study on Non-MTC Mobile Data Application Impacts | Rel-12 read |
| TR 22.907 v313 | UMTS IC Card and Terminal Concepts | R99 read |
| TS 23.171 v390 | LCS Stage 2 for UMTS | R99 read |
| TS 23.271 vj00 | LCS Stage 2 Specification | Rel-19 read |
| TS 25.222 vj00 | UTRA TDD Multiplexing & Channel Coding | Rel-19 read |
| TR 26.930 vj00 | WebRTC Enhancements for Immersive RTC over 5G | Rel-19 read |
| TR 26.996 vj10 | Immersive Audio for Split Rendering Performance | Rel-19 read |
| TS 28.390 vj00 | Solution Profiles for Interface IRPs | Rel-19 read |
| TS 28.667 vj00 | RPTA IRP Requirements | Rel-19 read |
| TS 28.668 vj00 | RPTA Integration Reference Point Requirements | Rel-19 read |
| TS 28.735 vj00 | STN Interface NRM IRP Information Service | Rel-19 read |
| TS 32.101 vj00 | PLMN Management Principles and Requirements | 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 32.742 vb00 | STN NRM for Configuration Management | Rel-11 read |
| TS 33.108 vj00 | LI Handover Interface Specification | Rel-19 read |
| TS 33.246 vj00 | MBMS Security Specification | Rel-19 read |
| TR 33.924 vj00 | GBA-OpenID Interworking Specification | Rel-19 read |
| TR 33.980 vj00 | GAA & Liberty Alliance Interworking Guidelines | Rel-19 read |
| TS 37.890 vj10 | Feasibility Study on 6 GHz for LTE/NR | Rel-19 read |