Mobile Subscriber Provisioning

Description

Mobile Subscriber Provisioning (MSP) is a core concept within 3GPP specifications that defines the subscriber as a logical entity provisioned with a set of services. The MSP is not the physical device (Mobile Station) but the subscription identity (e.g., linked to an IMSI or MSISDN) that holds the service profile. This profile includes data such as subscribed QoS parameters, allowed services (like voice, SMS, data), roaming permissions, and billing information. The MSP entity is stored within network databases, primarily the Home Subscriber Server (HSS) in UMTS/LTE or the Unified Data Management (UDM) in 5GC. When a subscriber attempts to attach to the network, the network retrieves the MSP's service profile to authorize the session, apply appropriate policies, and ensure correct charging. The MSP acts as the anchor point for personalizing the user experience across different access technologies (e.g., GERAN, UTRAN, E-UTRAN, NG-RAN) supported by the core network. Its management involves provisioning systems that populate the HSS/UDM with subscriber data, and it interfaces with policy control functions (like PCRF/PCF) for dynamic service authorization. The concept ensures a consistent service identity independent of the user's device or temporary location.

Purpose & Motivation

The MSP concept was formalized to separate the subscription identity from the physical device, enabling flexible service delivery and multi-device scenarios. Prior to its clear definition, services were often tightly coupled to a specific SIM card or device, limiting personalization and complicating service portability. By defining the subscriber as a provisioned entity (MSP), 3GPP enabled operators to offer complex service packages, roaming agreements, and convergent billing across circuit-switched and packet-switched domains. It solved the problem of managing user-centric services in a standardized way, providing a clear reference for service authorization, mobility management, and charging functions. The creation of MSP was motivated by the need for a scalable, subscriber-centric architecture that could support the growing variety of mobile services introduced from 3G (Rel-4) onwards, including multimedia messaging, location-based services, and IMS-based offerings.

Key Features

• Represents the subscriber identity independent of the User Equipment (UE).
• Stores the service profile including subscribed QoS and allowed services.
• Centralized in the HSS (3G/4G) or UDM (5G) for access-agnostic management.
• Enables service authorization and policy enforcement during network attachment.
• Forms the basis for accurate charging and billing records.
• Supports roaming through interaction with visited network elements.

Evolution Across Releases

Defining Specifications