Description
The Complete User Profile is an IMS subscription data concept defined in the 3GPP IMS specifications, primarily TS 29.228 (Cx and Dx interfaces) and TS 29.562 (Sh interface). It represents the union of the Initial Filter Criteria (iFC) instances that belong to all three parts of an IMS user profile: the registered part, the unregistered part, and the common part. The iFCs are the rules that tell the Serving-CSCF which application servers should be invoked, and under what conditions, when a user registers or initiates a session.
IMS user data is partitioned so that different service conditions can be applied depending on the user's registration state. The registered part contains service triggers that apply when the user is registered (for example, terminating services for an available user). The unregistered part contains triggers that apply when the user is not registered but the network still needs to route sessions, such as forwarding to voicemail. The common part contains triggers that apply regardless of registration state. Each part holds its own set of iFC instances, and the Complete User Profile aggregates them so that a network entity can obtain a full picture of the user's service logic in one view.
The profile is stored in the Home Subscriber Server (HSS) and retrieved by IMS nodes over the Cx interface. When a user registers, the S-CSCF downloads the relevant user profile, including iFCs, from the HSS using a Cx Pull or is provisioned via Cx Put. The S-CSCF then evaluates the iFCs in priority order against the session or registration request, invoking the indicated application servers when the trigger conditions match. The Sh interface allows application servers (such as an AS managing supplementary services) to query or update user data, including the complete profile, transparently.
The concept matters because it provides a single, consistent representation of a subscriber's service triggers across registration states. Without it, an S-CSCF or application server would need to assemble the applicable iFCs from multiple partial views, risking inconsistency. By defining the Complete User Profile, 3GPP ensures that the same authoritative data set is used for service invocation whether the user is registered, unregistered, or in a state where common triggers apply.
Operationally, the Complete User Profile is manipulated through the user data handling procedures of TS 29.228, where the HSS sends the profile to the S-CSCF and the S-CSCF acknowledges or requests updates. The profile is also relevant to interworking and to service centralization scenarios, where consistent iFC evaluation across states is required for correct call handling.
Purpose & Motivation
The Complete User Profile exists to solve the problem of applying IMS service triggers consistently across different registration states. IMS services are controlled by Initial Filter Criteria, which determine which application servers are invoked for a given session. Because a subscriber can be registered, unregistered, or in a state where common rules apply, the service logic is split into three profile parts. The Complete User Profile aggregates the iFC instances of all three parts so that network entities have one authoritative, complete view.
Before this concept was formalized, there was a risk that different nodes would apply different subsets of triggers depending on which profile part they happened to retrieve, leading to inconsistent service invocation — for example, a terminating service firing when the user was unregistered but should have been forwarded. By defining the complete profile, 3GPP ensured that the HSS, S-CSCF, and application servers all operate on the same data set.
Its longevity reflects the stability of the IMS service architecture.
What changed in its specifications
The latest release-to-release comparison of specifications that define Complete user profile. Each summary describes the whole specification, not only this term.
Rel-19 adds a second traffic abatement algorithm alongside the RFC 7683 default. It also extends the OC-OLR AVP and has I/S-CSCFs act on OC-OLR when OC-Ext-Reg-Timer is TRUE.
Full comparison in TS 29.228 →Rel-19 adds IMS AS registration, deregistration, retrieval, subscription, modification, and notification procedures, plus new Nhss_imsEE API clauses for event exposure monitoring.
Full comparison in TS 29.562 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference Complete user profile, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 29.228 vk00 | IMS Cx and Dx Interface Procedures | Rel-20 read |
| TS 29.562 vk10 | HSS Nhss Services for IMS and GBA | Rel-20 read |