Description
XML Document Management (XDM) is a standardized service capability within the 3GPP IP Multimedia Subsystem (IMS) architecture that provides a framework for storing, accessing, and managing user-related service data in XML documents. It operates through a set of functional entities, primarily the XDM Client (XDMC) and the XDM Server (XDMS), which interact using protocols like XML Configuration Access Protocol (XCAP) over HTTP. The XDM Server, which includes components such as the Shared XDMS, Aggregation Proxy, and Search Proxy, stores XML documents in repositories and handles requests for document manipulation. These documents contain service-specific data, such as presence lists, group definitions, or user preferences, enabling applications to retrieve and update user configurations in a consistent manner.
How XDM works involves a client-server model where the XDM Client, typically embedded in user equipment or application servers, sends XCAP requests to the XDM Server to perform operations like creating, reading, updating, or deleting XML documents. The Aggregation Proxy acts as a single entry point, authenticating requests and routing them to the appropriate XDMS based on the document type. For example, a Presence XDMS manages presence-related documents, while a Shared XDMS handles common data like contact lists. The XDM Server validates requests against XML schemas and applies access control policies to ensure data security and integrity. This architecture allows multiple services to share and reuse user data, reducing redundancy and enhancing service integration.
Key components of XDM include the XCAP protocol, which defines methods for manipulating XML documents over HTTP; the XDM-3 reference point, which specifies interfaces between XDMCs and XDMSs; and various XDMS types tailored for specific services. The XDM framework also supports subscription mechanisms, allowing clients to be notified of document changes via SIP notifications. This enables real-time updates across services, such as when a user modifies their group membership. XDM's role is detailed in specifications like TS 24.484 for XCAP protocol usage and TS 32.808 for management aspects, ensuring interoperability across different network implementations. By providing a unified data management layer, XDM facilitates the creation of rich, personalized services in 3GPP networks, from basic telephony to advanced multimedia applications.
Purpose & Motivation
XML Document Management (XDM) was created to address the need for a standardized way to manage user-specific service data in IP-based networks, particularly within the IMS framework. Before XDM, service data was often stored in proprietary formats or siloed within individual applications, leading to fragmentation, duplication, and limited interoperability. This made it difficult to offer integrated services like presence-enhanced messaging or dynamic group management. XDM solves these problems by introducing a common XML-based repository and access mechanism, allowing data to be shared across multiple services and network domains.
Historically, as telecom services evolved from circuit-switched to packet-switched architectures, there was a growing demand for personalized and convergent services. XDM emerged in 3GPP Release 8 as part of the IMS suite, motivated by the success of XML in web services and the need for flexible data management. It addresses limitations of earlier approaches by providing a scalable, extensible framework that supports diverse service requirements, from simple configuration storage to complex data aggregation. For example, XDM enables services like Push-to-talk over Cellular (PoC) and Rich Communication Services (RCS) to manage group lists and user preferences consistently.
The purpose of XDM extends beyond basic data storage; it enables service enablers that enhance user experience and operational efficiency. By centralizing management of XML documents, XDM reduces development overhead for new services, as they can leverage existing data without reinventing storage mechanisms. It also supports regulatory requirements, such as privacy controls through access policies. As networks advanced to 4G and 5G, XDM's role expanded to support new use cases like network slicing and IoT service management, demonstrating its adaptability and ongoing relevance in 3GPP ecosystems.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (21 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-8, normative work from Rel-15.
In Release 15, the XDM function was enhanced to support Mission Critical Services (MCS) by introducing new configuration documents and management procedures. Specifically, it defined the formats and flows for the MCS UE initial configuration document, MCPTT user profile, and service configuration documents, enabling service administrators to configure them via an MCS UE. The release also detailed procedures for an MCPTT UE to subscribe to and download these documents after user authentication, and for a server to subscribe to the service configuration document.
- Sevice document updates for functional alias TS 24.484CR0086
- MCPTT UE subscribing to and downloading documents after MCPTT user authentication Flow TS 24.484CR0053
- MCPTT Server subscribing to and downloading the service configuration document Flow TS 24.484CR0054
- Document Creation Flow TS 24.484CR0055
- Correct MCPTT UE initial configuration document schema TS 24.484CR0070
- Corrections to configuration management TS 24.484CR0074
+ 1 more changes
In Release 16, the XDM (XML Document Management) function introduced new specifications for managing configuration documents for Mission Critical Services (MCS), including MCPTT, MCVideo, and MCData. This encompassed the definition of specific UE configuration, user profile, and service configuration documents, along with procedures for creating, updating, and deleting them on a configuration management server. The release also detailed the integration of these XDM management processes with MCS user authentication and subscription mechanisms.
In Release 17, the XDM (XML Document Management) function was enhanced for Mission Critical Services (MCS) to support new configuration management procedures for MCPTT private calls. Specifically, the release introduced capabilities for configuring call transfer and call forwarding for MCPTT private calls through the configuration management server, as detailed in the MCPTT service configuration document. These updates allowed administrators to manage these features using the existing XDM framework for MCS UE configuration documents.
In Release 18, the XDM function introduced new elements for migration within the user profile configuration documents for MCPTT, MCVideo, and MCData services. It also removed the MCS GW UE initial configuration document and implemented XSD corrections to address backward compatibility issues and implementation errors in service and configuration management documents.
- New element for migration in the MCPTT user profile configuration document TS 24.484CR0249
- New element for migration in the MCVideo user profile configuration document TS 24.484CR0250
- New element for migration in the MCData user profile configuration document TS 24.484CR0251
- Removal of MCS GW UE initial configuration document TS 24.484CR0274
- XSD changes due to BC issues in service config document TS 24.484CR0278
- XSD corrections to config management documents (CR implementation error corrections) TS 24.484CR0279
In Release 19, the XDM function introduced the ability to include an LMS URI within the MCS UE initial configuration document for server discovery. Furthermore, a new Location user configuration data document was formally defined and registered with IANA for standardized management.
Explore further
Broader topics and technologies where XDM plays a role.
Defining Specifications
3GPP specifications that define or reference XDM, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 24.484 vj30 | MCS Configuration Management | Rel-19 |
| TS 32.808 v1800 | Common User Profile Storage Framework | Rel-8 |