Subscription Profile

Description

The Subscription Profile is a fundamental concept in 3GPP networks, representing the collection of data that defines the services, features, and permissions associated with a subscriber. It is stored and managed by various network domains and subsystems, such as the Home Subscriber Server (HSS), Unified Data Management (UDM), and other entities, depending on the network architecture. The profile includes information such as subscriber identities (IMSI, MSISDN), authentication credentials, service subscriptions (e.g., voice, data, SMS), QoS parameters, roaming restrictions, and supplementary services. This data is essential for the network to authenticate the subscriber, authorize access to services, and enforce policies.

The Subscription Profile is not a monolithic entity; it can be decomposed into multiple components that may be stored in different network elements or domains. For example, in a 4G network, the HSS stores the subscription data for EPS, while the IMS HSS stores data for IMS services. In 5G, the UDM stores subscription data, and the Unified Data Repository (UDR) may hold additional data. The profile is typically structured according to standardized information models, such as those defined in 3GPP TS 23.008, which specifies the format and semantics of subscription data. This ensures interoperability between different vendors' equipment and allows for consistent behavior across the network.

The management of the Subscription Profile involves provisioning, updating, and deleting data as subscribers change their services or as the operator introduces new offerings. This is often done through Subscription Management (SuM) capabilities, which provide standardized interfaces for operators and service providers to interact with the profile. The profile is also used by network functions during procedures such as attach, registration, and service request, where the network retrieves the relevant data to authenticate the user and establish the requested services. For example, during an LTE attach procedure, the MME retrieves the subscription profile from the HSS to determine the allowed APNs, QoS parameters, and other policies.

Security is a critical aspect of the Subscription Profile, as it contains sensitive information that must be protected from unauthorized access. 3GPP specifications define security mechanisms for the storage, transmission, and access of subscription data, including encryption, integrity protection, and access control. The profile is also subject to privacy regulations, and operators must ensure compliance with legal requirements regarding data protection.

With the advent of 5G and network slicing, the Subscription Profile has become more dynamic and granular. Subscribers may have multiple profiles associated with different network slices, each with its own set of requirements. The profile may also include slice-specific parameters, such as allowed S-NSSAIs and slice-specific QoS. This evolution reflects the increasing complexity of services and the need for flexible, personalized subscription management. In summary, the Subscription Profile is a comprehensive data set that enables the network to deliver services to subscribers in a controlled and secure manner.

Purpose & Motivation

The Subscription Profile exists to provide a centralized, standardized repository of subscriber-specific data that network functions can rely on to deliver services. Before the introduction of standardized profiles, each network element might have maintained its own subscriber data, leading to inconsistencies, duplication, and operational inefficiencies. For example, if a subscriber changed their service plan, multiple systems would need to be updated, increasing the risk of errors and delays. The lack of a common data model also made it difficult to introduce new services or to interoperate between different vendors' equipment.

The 3GPP introduced the concept of the Subscription Profile in early releases (R99) to address these issues. Initially, the definition focused on privacy classes, reflecting the early emphasis on privacy in location services. However, as networks evolved, the definition was broadened in Release 8 to encompass all data managed and stored by network domains and subsystems for the operation and execution of services. This change recognized that the profile is not just about privacy but about all aspects of service delivery, including authentication, authorization, and policy control.

The Subscription Profile solves several problems. It provides a single source of truth for subscriber data, ensuring consistency across the network. It enables interoperability by defining standardized formats and semantics, allowing different vendors' equipment to exchange and interpret subscription data correctly. It also supports scalability by allowing the profile to be distributed across multiple domains and subsystems, each managing a subset of the data. This distribution is essential in large networks with millions of subscribers, where a centralized database would be a bottleneck. Finally, the profile facilitates the introduction of new services by providing a flexible structure that can be extended with new data elements as needed.

In the context of 5G, the Subscription Profile continues to evolve to support new requirements such as network slicing, where each slice may have its own subscription data. The profile also needs to support new authentication methods (e.g., 5G-AKA) and new service types (e.g., URLLC, mMTC). Thus, the Subscription Profile remains a cornerstone of 3GPP network architecture, enabling efficient and secure service delivery.