Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Identifier

IMPU

IP Multimedia Public User Identity

Identifier →

IMPU is any identity used by a user within the IMS for requesting communication to another user; it takes the form of either a SIP URI or a Tel URI.

Introduced
Rel-5
Where
Core Network › Legacy Core
Specifications
3 specs
IMPU Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

In 3GPP TS 23.003, clause 13.4, a Public User Identity is any identity used by a user within the IMS subsystem for requesting communication to another user. The Public User Identity takes the form of either a SIP URI (IETF RFC 3261) or a Tel URI (IETF RFC 3966). The 3GPP specifications describing the interfaces over which Public User Identities are transferred specify the allowed formats, in particular TS 24.229 for SIP signalling interfaces.

The Public User Identity is distinct from the Private User Identity (IMPI). According to TS 23.003, clause 13.3, the private user identity takes the form of a Network Access Identifier (NAI) with the form username@realm.

Purpose & Motivation

The IMPU is the identity by which a user is addressed when communication is requested within the IMS (3GPP TS 23.003, clause 13.4).

What changed in its specifications

The latest release-to-release comparison of specifications that define IMPU. Each summary describes the whole specification, not only this term.

TS 23.003Rel-18 → Rel-19

Rel-19 adds clauses 31.1 to 31.7 to TS 23.003 defining identifier and information structures for Ambient IoT devices and areas, plus new normative references. It also adds SNPN support to ProSe identifiers, including an optional NID part in the PLMN ID and a revised temporary identity length.

Full comparison in TS 23.003 →
TS 23.228Rel-18 → Rel-19

Rel-19 TS 23.228 adds SBI service operations for IMS data channels, event subscription, and user information, plus HSS lookup of the serving IMS AS. It adds PS Data Off handling for IMS Data Channel services and Multimedia Priority Service for Messaging.

Full comparison in TS 23.228 →

Technology family

Subscriber and device identifiers · User Equipment

  1. Phase 1 IMEI, IMSI, MSIN, MSISDN, TMSI
  2. Phase 2 IMEISV
  3. R96 TLLI
  4. R97 P-TMSI
  5. R98 CTSMSI
  6. Rel-5 IMPI, IMPU, Temporary Public User Identity
  7. Rel-8 GUTI, M-TMSI
  8. Rel-15 5G-GUTI, 5G-S-TMSI, 5G-TMSI, GPSI, NSI, PEI, SUCI, SUPI
  9. Rel-16 GCI, GLI, Truncated 5G-S-TMSI
  • IMPU extended by Temporary Public User Identity
    “For 3GPP systems, if there is no ISIM application to host the Public User Identity, a Temporary Public User Identity shall be derived, based on the IMSI.” TS 23.003

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 11 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-5 introduced

TS 33.203 first specifies the IMPU in Rel-5: a subscriber has at least one external IMPU, registered (explicitly or implicitly) and tied to the IMPI during IMS authentication and registration.

  • “The subscriber will have one (network internal) user private identity (IMPI) and at least one external user public identity (IMPU).” TS 33.203 v5.12.0
  • “It shall be possible to implicitly register IMPU(s). The implicitly registered IMPU(s) all belong to the same Service Profile.” TS 33.203 v5.12.0
  • “Before a user can get access to the IM services at least one IMPU needs to be registered” TS 33.203 v5.12.0
Rel-6 specification text

Requirements for implicit registration of IMPUs were revised: the statement that implicitly registered IMPUs all belong to the same Service Profile was removed, and the P-CSCF key handling now also stores CKIM.

  • “All the IMPU(s) being implicitly registered shall be delivered by the HSS to the S‑CSCF and subsequently to the P‑CSCF.” TS 33.203 v6.11.0
  • “The implicitly registered IMPU(s) all belong to the same Service Profile.” TS 33.203 v6.11.0
Rel-8 1 CR

IMPU handling was extended: wildcarded IMPU identity types and attributes were added in Cx, and registration/authentication procedures per IMPU were specified, plus service restoration for registered IMPUs.

  • “The attribute WildcardedIMPU shall be present when IdentityType is a non distinct IMPU or it may be optionally present when IdentityType is a Wildcarded IMPU.” TS 29.228 v8.19.0
  • “It is the policy of the HN that decides if an authentication shall take place for the registration of an additional IMPU” TS 33.203 v8.8.0
  • Service Restoration for Registered IMPU TS 29.228CR0427
Rel-9 2 CRs

IMS notification must be sent to all UEs sharing an IMPU, and the Cx handling of a default IMPU was corrected.

  • Notification is to be sent to all UEs sharing the IMPU TS 23.380CR0027
  • Default IMPU TS 29.228CR0462
Rel-10 specification text

When a REGISTER omits the IMPI, the IMPI is derived from the registering IMPU, and the I-CSCF and S-CSCF must perform this derivation; the registering IMPU then cannot be shared across UEs.

  • “If SM3 does not contain an IMPI the S-CSCF shall derive the IMPI from the IMPU in the REGISTER request” TS 33.203 v10.3.0
  • “the registering IMPU in this case cannot be shared across multiple UEs” TS 33.203 v10.3.0
Rel-12 1 CR

Rel-12 specifies how WebRTC IMS clients are authorised and registered using IMPI/IMPU, including the IMPU being determined from authorization information, and the WWSF assigning IMPUs from a subscription pool.

  • “shall securely determine from the received authorization information the IMPI and IMPU of the authenticated WIC attempting to register with the IMS network.” TS 33.203 v12.9.0
  • “The WWSF is provided with a pool of subscriptions, each containing a single unique IMPU/IMPI pair, to IMS” TS 23.228 v12.11.0
  • IMPU As Access Key for User State and Location Information TS 29.328CR0466
Rel-13 1 CR

For WebRTC IMS Client registration, the WWSF's pool is clarified to consist of subscriptions each holding a single unique IMPU/IMPI pair, from which Public and Private identities are assigned.

  • “each containing a single unique IMPU/IMPI pair, to IMS and can assign individual Public and Private User Identities from this pool.” TS 33.203 v13.4.0
  • Clarifying IMPU/IMPI relationship for WIC registration from a pool of Identities TS 23.228CR1135
Rel-14 1 CR

A correction in TS 23.167 replaced an erroneous reference to IMPI with IMPU, fixing which identity the specification refers to.

  • Correction from IMPI to IMPU TS 23.167CR0306
Rel-16 specification text

TS 29.562 Nudm/HSS service operations now specify IMPU handling: IMS UE identity must be an IMPU for registration, deregistration of the IMPU and its implicit registration set, plus a shared IMPU correction.

  • “If an IMPU is received as ImsUeId, HSS shall deregister the IMPU and related IMPUs in the Implicit Registration Set for the related IMPI.” TS 29.562 v16.10.0
  • “The request contains the IMS UE's identity (/{imsUeId}) which shall be an IMPU, the S-CSCF Registration Information and the Registration Type.” TS 29.562 v16.10.0
  • “Correction to shared IMPU” TS 29.562 v16.10.0
Rel-17 2 CRs

Rel-17 adds IMPU handling in IMS authentication (33.203 S-CSCF check with new algorithms) and adds a shared IMPU feature and correction in the 29.562 HSS service procedures.

  • Shared IMPU TS 29.562CR0056
  • Correction to shared IMPU TS 29.562CR0088
  • “during a registration procedure, during an originating request procedure or during a terminating request procedure” TS 29.562 v17.10.0
Rel-19 specification text

Rel-19 adds IMPU-based handling in HSS/IMS AS service operations: IMPU as imsUeId in register, deregister, retrieval and event subscription requests, plus IMPU-keyed RCD information storage and provisioning.

  • “The request contains the IMS UE's identity (/{imsUeId}) which shall be an IMPU, the IMS AS Registration Information and the Registration Type.” TS 29.562 v19.6.0
  • “HSS stores either one RCD server address or one RCD URL per IMPU or wildcarded IMPU” TS 23.228 v19.8.0
  • “If the AF authorization for the IMPU is revoked, the HSS unsubscribes to the subscriber specific IMS event in the IMS AS” TS 23.228 v19.8.0

Defining Specifications

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

SpecificationTitleRelease
TS 23.003 vk10 Numbering, Addressing and Identification Rel-20 read
TS 23.228 vk10 IP Multimedia Core Network Subsystem Rel-20 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read