Glossary term · Management

Subscriber profile

Subscriber Profile

Management →

Subscriber profile is the set of data managed by Subscription Management that defines a subscriber's service entitlements, restrictions, and usage limits.

Introduced
Rel-8
Where
Management
Specifications
3 specs

3GPP QuarterlyThe next issue by email, at most eight a year.

Category
Management
Introduced
Rel-8
Where
Management
Specifications
3 specs
Subscriber profile Description Purpose Related Specifications

Description

A subscriber profile is the set of data managed and stored by Subscription Management (SuM) for a subscriber for the management of associated users and subscribed services and the limits relative to their use. It is a fundamental concept in 3GPP network management, representing the collection of parameters, policies, and entitlements that define what services a subscriber can access, under what conditions, and with what restrictions. The profile is maintained by the network operator and is used by various network functions to enforce service policies, charging, and quality of service.

The subscriber profile typically includes information such as the subscriber's identity (IMSI, MSISDN), subscribed services (voice, data, SMS, supplementary services), QoS parameters (maximum bit rate, guaranteed bit rate), roaming restrictions, and charging characteristics. It may also include details about associated users, such as family members or enterprise employees, who share the subscription. The profile is stored in a central repository, often the Home Subscriber Server (HSS) or a Subscription Management (SuM) entity, and is accessed by network elements like the Mobility Management Entity (MME), Serving GPRS Support Node (SGSN), and Policy and Charging Rules Function (PCRF) to make decisions about service provisioning.

The management of subscriber profiles involves operations such as creation, modification, deletion, and querying. These operations are performed through standardized interfaces, such as the Sh interface between the HSS and application servers, or the SuM interfaces defined in 3GPP TS 32.140 and TS 32.172. The profile data is structured according to a schema that allows for extensibility and interoperability. For example, the Subscription Management (SuM) concept, introduced in Rel-8, provides a unified way to manage subscription data across different domains, including CS, PS, and IMS.

The subscriber profile is closely linked to the concept of a subscription, which describes the commercial relationship between the subscriber and the service provider. The profile is the technical representation of that relationship, translating business agreements into network parameters. It enables the network to personalize services, apply differentiated charging, and enforce policies. For instance, a subscriber with a premium profile might have higher QoS limits and access to additional services compared to a basic subscriber.

In 5G, the subscriber profile is managed by the Unified Data Management (UDM) function, which stores subscription data and generates authentication vectors. The profile is used by the Access and Mobility Management Function (AMF) and Session Management Function (SMF) to control access and session establishment. The 5G profile includes new parameters for network slicing, such as allowed S-NSSAIs, and for edge computing. The evolution of the subscriber profile reflects the increasing complexity and flexibility of mobile networks, supporting a wide range of services and business models.

Purpose & Motivation

The subscriber profile exists to provide a centralized, standardized representation of a subscriber's service entitlements and restrictions, enabling the network to deliver personalized services and enforce policies consistently. Before its formalization, subscriber data was scattered across different network elements, leading to inconsistencies and operational complexity. The profile consolidates this data, making it easier to manage and query.

It solves the problem of service differentiation and policy enforcement in multi-service networks. By defining what a subscriber can do and under what conditions, the profile allows operators to offer tiered services, apply fair usage policies, and prevent abuse. It also supports regulatory requirements, such as lawful interception and emergency services, by providing the necessary subscriber information.

The motivation for creating the subscriber profile concept came from the need to manage increasingly complex subscriptions, especially with the introduction of IMS and the convergence of fixed and mobile networks. The Subscription Management (SuM) system was developed to provide a unified view of subscription data, and the subscriber profile is its core data structure. Over time, the profile has evolved to include new parameters for 4G and 5G, such as those for network slicing and IoT, reflecting the growing diversity of services and devices.

Release Timeline

Evolution Across Releases

Rel-8 Initial

Initial definition: The set of data managed and stored by Subscription Management (SuM) for a subscriber for the management of associated users and subscribed services and the limits relative to their use. This release introduced the Subscription Management (SuM) concept, providing a unified way to manage subscription data across different domains.

The definition remained unchanged from Rel-8, carrying over the same wording. The SuM architecture continued to be refined, but the core definition of subscriber profile stayed the same.

The definition remained unchanged from Rel-8, carrying over the same wording. No changes to the definition were made in this release.

The definition remained unchanged from Rel-8, carrying over the same wording. The term continued to be used in the context of evolved packet core and IMS.

The definition remained unchanged from Rel-8, carrying over the same wording. No changes to the definition were made in this release.

The definition remained unchanged from Rel-8, carrying over the same wording. The term continued to be applied in new scenarios such as machine-type communication.

The definition remained unchanged from Rel-8, carrying over the same wording. No changes to the definition were made in this release.

The definition remained unchanged from Rel-8, carrying over the same wording. The term was used in 5G specifications, but the definition itself did not change.

The definition remained unchanged from Rel-8, carrying over the same wording. No changes to the definition were made in this release.

The definition remained unchanged from Rel-8, carrying over the same wording. The term continued to be used in the context of 5G and beyond.

The definition remained unchanged from Rel-8, carrying over the same wording. No changes to the definition were made in this release.

The definition remained unchanged from Rel-8, carrying over the same wording. The term continues to be relevant for future network management.

Defining Specifications

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

SpecificationTitleRelease
TS 28.752 vj00 SuM NRM IRP Information Service Rel-19
TS 32.140 vj00 Subscription Management (SuM) requirements Rel-19
TS 32.172 vb00 SuM NRM IRP: Information Service Rel-11