Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

Subscriber

Subscriber

Services →

Subscriber is an entity that holds a subscription with a service provider to manage service access, authorize users, and set usage limits for billing in a 3GPP network.

Introduced
Rel-4
Where
Services › IMS
Specifications
20 specs
Also in
Management, Core Network
Subscriber Description Purpose What changed Neighbours Detected Changes Specifications

Description

In 3GPP terminology, a Subscriber is a fundamental business and technical concept representing an entity—typically a person or organization—that has entered into a Subscription agreement with a service provider. This entity may be associated with one or more users who actually consume the services. The subscriber holds the contractual relationship, is responsible for payment, and has the authority to subscribe or unsubscribe services, register users authorized to use those services, and define usage limits for those users. This separation of subscriber (payer/manager) from user (consumer) is crucial for flexible service models in mobile networks.

The subscriber concept is central to the architecture of the IP Multimedia Subsystem (IMS) and other 3GPP service enablers. In IMS, the subscriber is identified by an IP Multimedia Private Identity (IMPI) and may have one or more IP Multimedia Public Identities (IMPUs). The Home Subscriber Server (HSS) stores subscription-related information, including service profiles, authentication vectors, and authorization data. When a user attempts to access a service, the network authenticates the subscriber and checks whether the requested service is allowed based on the subscription profile. This ensures that only authorized entities can use services and that billing can be correctly applied.

The subscriber also plays a key role in policy and charging control (PCC). The Policy and Charging Rules Function (PCRF) or, in 5G, the Policy Control Function (PCF) retrieves subscriber-specific policies from the Subscription Profile Repository (SPR) or Unified Data Repository (UDR). These policies determine quality of service (QoS) levels, charging rules, and bandwidth limitations. For example, a subscriber may have a premium subscription that allows higher data rates or access to specific services like VoLTE. The network enforces these policies dynamically based on the subscriber's profile and current network conditions.

In the context of supplementary services, such as Explicit Call Transfer (ECT), the subscriber is the entity that subscribes to the service and can invoke it. The term "Subscriber A" is used in specifications like 22.072 and 22.091 to denote the served mobile subscriber who invokes the ECT service. This highlights the subscriber's active role in managing and using services, beyond just being a passive account holder.

From a management perspective, subscriber data is maintained in various network elements: the HSS in IMS and EPS, the UDR in 5G, and the Equipment Identity Register (EIR) for device-related information. Operations such as subscription management, authentication, and authorization rely on accurate subscriber data. The 3GPP specifications (e.g., 21.905, 22.101, 23.228) define the subscriber concept and its interactions with network functions, ensuring interoperability across vendors and operators. As networks evolve towards 5G and beyond, the subscriber concept remains foundational, adapting to new service models like network slicing, where a subscriber may have slice-specific subscriptions.

Purpose & Motivation

The Subscriber concept exists to clearly separate the entity that holds the contractual relationship with the service provider from the users who actually consume the services. This separation is essential for flexible business models, allowing a single subscriber (e.g., a corporation) to manage multiple users (employees) and control their access and usage. It also enables accurate billing and policy enforcement, as the network can apply rules based on the subscription rather than individual users.

Historically, early mobile networks (2G) had a simpler model where the subscriber and user were often the same person, identified by the SIM card. However, as services became more diverse and complex, especially with the introduction of IMS in 3GPP Release 5, the need for a more sophisticated subscriber model emerged. The subscriber entity allows for multiple users under one subscription, each with potentially different service permissions and limits. This is particularly important for enterprise customers, machine-to-machine (M2M) communications, and multi-device scenarios.

The subscriber concept also solves the problem of authentication and authorization in a multi-service environment. By centralizing subscription data in the HSS/UDR, the network can authenticate the subscriber once and then authorize access to various services based on the subscription profile. This avoids the need for separate credentials for each service and simplifies the user experience. Furthermore, it enables operators to offer personalized services and charging plans, driving revenue and customer loyalty.

What changed in its specifications

The latest release-to-release comparison of specifications that define Subscriber. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

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 →
TS 22.057Rel-4 → Rel-5

Rel-5 added MExE support for IP multimedia services and handling of individual media components in user profiles.

Full comparison in TS 22.057 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (3 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-19 2 changes
  • KI#1: Cancel procedure for subscriber specific IMS Events TS 23.228CR1655
  • IMS AS discovery for non subscriber specific event TS 23.228CR1737
Rel-20 1 change
  • Procedures for non-subscriber specific DCSF events TS 23.228CR1759

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 22.057 vj00 Mobile Execution Environment (MExE) Stage 1 Rel-19 read
TS 22.101 vl00 3GPP Service Principles for PLMNs Rel-21 read
TS 23.228 vk10 IP Multimedia Core Network Subsystem Rel-20 read
TS 24.173 vj00 Multimedia Telephony Service and Supplementary Services in IMS Rel-19 read
TS 24.406 v810 Message Waiting Indication (MWI) Protocol Rel-8 read
TS 24.606 vj00 MWI Service Protocol Description Rel-19 read
TS 29.222 vk10 CAPIF Northbound API Protocol Rel-20 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.240 vk10 3GPP Charging Architecture and Principles Rel-20 read
TS 32.251 vj00 PS Domain Charging Management Rel-19 read
TS 32.270 vj00 MMS Charging Management Specification Rel-19 read
TS 32.272 vj00 Charging for Push-to-Talk over Cellular (PoC) Rel-19 read
TS 32.273 vj00 MBMS Charging Management Rel-19 read
TS 32.277 vj20 Charging Management for Proximity Services (ProSe) Rel-19 read
TS 32.278 vj00 Monitoring Events Offline Charging Specification Rel-19 read
TS 32.295 vj00 3GPP Charging: CDR Transfer via GTP' Protocol Rel-19 read
TS 32.296 vj00 Online Charging System (OCS) Architecture Rel-19 read
TS 32.825 va00 Rc Reference Point Study for ABMF Rel-10 read