USD

User Service Description

Services →
Introduced in Rel-8 Also in: User Equipment

USD is a structured XML document that describes a user's multimedia telephony service for personalization, domain interworking, and a consistent cross-device experience.

Category
Services
Introduced
Rel-8
Where
Services › Codecs
Also touches
1 segments
Specifications
14 specs
USD Description Purpose Related Classification Detected Changes Specifications

Description

The User Service Description (USD) is a service-layer concept within the 3GPP architecture, primarily associated with IP Multimedia Subsystem (IMS) and multimedia telephony services. It is defined as an XML document that contains a comprehensive description of the telephony service as provisioned for a specific user. The USD is not a protocol but a data model that encapsulates the user's service profile, including service settings, media capabilities, and supplementary service configurations. It is typically stored in a network repository, such as an XML Document Management Server (XDMS), and can be accessed or provisioned by various network entities and user devices.

The USD works by providing a standardized, machine-readable blueprint of a user's service. When a device registers with the network or initiates a service, it can retrieve the USD to understand how to configure itself. For example, the USD may specify the codecs preferred for audio and video, the settings for call forwarding or barring, the availability of chat or file transfer functions within a call, and the policies for service interworking with legacy Circuit-Switched (CS) networks. The network also uses the USD to apply consistent service logic for the user across different access networks and sessions.

Architecturally, the USD interacts with several key components. The Telephony Application Server (TAS) or Multimedia Telephony Service (MMTel) AS may reference the USD to execute service logic. The UE can fetch the USD using protocols like HTTP or XCAP (XML Configuration Access Protocol). A key role of the USD is to facilitate service continuity and interworking, especially between IMS-based Voice over LTE (VoLTE) and legacy CS networks through Single Radio Voice Call Continuity (SRVCC) or other mechanisms. By having a centralized service description, both the network and the device can align their behavior, ensuring that features like call waiting, conference calling, or media handling work identically regardless of the underlying transport technology.

Purpose & Motivation

The USD was introduced in 3GPP Release 8, coinciding with the full standardization of IMS-based multimedia telephony (MMTel). Its creation was motivated by the complexity of delivering rich, personalized telephony services over all-IP networks. Prior to IMS, telephony services in circuit-switched networks were relatively static and network-controlled, with limited user customization. The shift to packet-switched, application-driven IMS services required a way to describe a user's complex service profile in a flexible, extensible manner.

The USD solves the problem of service portability and consistent user experience. As users employ multiple devices (smartphones, tablets, PCs) and move across different access networks (LTE, Wi-Fi, 3G), the USD ensures their telephony service—with all its personalized features—follows them. It also addresses the critical challenge of interworking between IMS and legacy CS networks during the transition phase to all-IP. By defining service capabilities in a common description, the network can seamlessly map IMS supplementary services to their CS equivalents (and vice versa), maintaining service continuity for the user. The USD provides the necessary abstraction layer between service logic and access technology, future-proofing service deployment.

Classification

Part ofIMS
Specific typesMMTEL
Related approachesXCAPXDMSSRVCC

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (10 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-8, normative work from Rel-15.

Rel-15 1 change

In Release 15, the USD (User Service Description) function was extended to support V2X (Vehicle-to-Everything) communications, introducing two specific USD types. These are the V2X USD for configuring the UE to receive MBMS-based V2X traffic and the V2X Server USD for discovering V2X Application Servers via MBMS. The information elements for these USDs include TMGI, service area identifiers, frequency, and SDP information with IP multicast addresses and port numbers.

  • Update EFHPPLMN description to clarify timer T interpretation based on the RAT in use. TS 31.102CR0795
Rel-16 8 changes

In Release 16, the USD function was extended to formally define the V2X USD and V2X Server USD for Vehicle-to-Everything communications, specifying their information elements like TMGI, service area, and SDP details for MBMS-based service delivery. This release introduced provisioning procedures for these V2X-specific USDs, including via the V1 reference point from the V2X Application Server. It also included corrections and clarifications to the associated XML schemas and data types for robust provisioning.

  • Missing XML Data Type for Attributes in MBMS USD TS 26.346CR0658
  • Clarifications on V2X USD TS 23.286CR0017
  • XML schema for V2X USD provisioning procedure TS 24.486CR0038
  • Update to V2X USD provisioning procedure TS 24.486CR0049
  • Correction of client USD provisioning elements TS 24.486CR0052
  • Correction of V2X-USD-announcement-info element TS 24.486CR0086

+ 2 more changes

Rel-18 1 change

In Release 18, the key new capability for the USD function was the introduction of a specific User Service Description for UE pre-configuration for Multicast MBS services. This builds upon the existing V2X USD framework by defining a mechanism to pre-configure a UE with the necessary service description information, such as TMGI and SDP information, to enable the reception of MBS multicast traffic. This enhancement facilitates faster service access and improved efficiency for multicast service delivery.

  • Description for the UE pre-configuration for Multicast MBS services TS 24.575CR0006

Explore further

Broader topics and technologies where USD plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.285 vj00 V2X Architecture Enhancements for LTE Rel-19
TS 23.286 vj00 V2X Application Enabler Architecture Rel-19
TR 23.785 ve00 Architecture enhancements for LTE V2X services Rel-14
TS 23.792 vg00 MBMS API for Mission Critical Services Rel-16
TS 23.795 vg10 V2X Application Architecture Study Rel-16
TS 24.486 vj00 V2X Application Enabler (VAE) Protocol Spec Rel-19
TS 24.575 vj00 UE Pre-configuration for MBS Rel-19
TS 26.237 vj00 IMS for PSS and MBMS Control Rel-19
TS 26.346 vj20 MBMS User Services Media Codecs & Protocols Rel-19
TS 26.347 vj00 MBMS Transport Protocol and API (TRAPI) Rel-19
TS 26.849 vc10 MBMS Operation on Demand (MooD) Rel-12
TR 26.917 vj00 TV Service Enhancements over 3GPP Rel-19
TS 31.102 vj40 USIM Application Specification Rel-19
TS 36.868 vc00 Study on Group Communication for E-UTRA Rel-12