Registered Profile

Description

The Registered Profile is a concept defined in 3GPP Technical Specifications 22.097 and 23.097, primarily within the context of the Personal Network Management (PNM) service. It serves as the default subscription profile that is automatically applied to all mobile-originated (MO) calls and short messages (SMS) when the user has not explicitly selected an alternative profile. Each registered entity (such as a mobile device or a user) within a Personal Network or Personal Area Network is associated with a Registered Profile. This profile dictates the service settings, call handling, and messaging behavior for that entity.

The Registered Profile is part of a broader profile management framework where multiple profiles can be defined, each potentially offering different service configurations (e.g., for work, personal use, or specific contexts). When no profile is manually chosen by the user or by an application, the network falls back to the Registered Profile to ensure that communication services function without interruption. The profile is stored in the network and can be managed by the user or the network operator. It is linked to the registration status of the entity within the Personal Network.

The concept ensures that even without explicit profile selection, the network can provide a predictable and consistent user experience. For example, if a user has multiple profiles for different roles, the Registered Profile acts as the baseline, ensuring that calls and messages are always handled according to a default set of rules. This is particularly important in multi-device scenarios where a single user may own several devices, each with its own Registered Profile, allowing for unified or differentiated service handling.

Because the Registered Profile is tied to the registration of an entity, it is only active as long as the entity remains registered in the Personal Network. Deregistration may remove the association, but the profile itself may persist in the network for future use. The profile can be updated or replaced by the user or the operator, and changes typically take effect for subsequent communications. The actual contents of a profile (e.g., forwarding settings, barring rules, message handling) are defined by the operator and may include parameters such as call forwarding numbers, blacklists, or priority levels.

From an architectural perspective, the Registered Profile is managed by the Personal Network Management (PNM) functional entity, which resides in the home network. The PNM interacts with other core network elements, such as the HLR/HSS, MSC, and SMSC, to enforce profile-based routing and service control. When a MO call or SMS is initiated, the serving network queries the PNM to retrieve the applicable profile. If no specific profile is selected, the Registered Profile is used. This query and enforcement mechanism ensures that the correct service logic is applied consistently, regardless of the access network or device used.

Purpose & Motivation

The Registered Profile exists to guarantee that mobile-originated calls and short messages are always governed by a set of predefined service rules, even when the user has not explicitly chosen a profile. In multi-profile systems, users can define various profiles for different contexts, but without a default, the network would lack a consistent fallback, potentially leading to service failures or unpredictable behavior. The Registered Profile solves this by providing a baseline configuration that is automatically applied.

Historically, before the introduction of Personal Network Management, users had limited ability to manage multiple devices or service profiles under a single subscription. With the proliferation of personal devices, the need arose for a flexible yet reliable way to manage services across them. The Registered Profile was introduced as part of the PNM framework to ensure that basic services (calls, SMS) function out-of-the-box. It also simplifies network operations because the profile is tied to the registered entity and remains stable until deregistration.

The concept also addresses the need for seamless user experience. Users expect their devices to work immediately after registration, without requiring them to manually select a profile. The Registered Profile enables this by being the active profile by default. It also provides a foundation for more advanced features, such as profile-based routing or charging, by ensuring a known state from which other profiles can be selected or modified.