Description
The XML Document Management Server (XDMS) is a fundamental network entity within the 3GPP IP Multimedia Subsystem (IMS) architecture, specifically defined for the management of service-related configuration data. It functions as a repository and processing engine for XML documents that define user-specific service settings, preferences, and data sets. These documents are central to enabling advanced IMS services such as Presence, Messaging, Conferencing, and Group Management. The XDMS provides a standardized, secure, and reliable mechanism for authorized clients—typically Application Servers (AS) or User Equipment (UE) via proxies—to manipulate these XML documents using the XML Configuration Access Protocol (XCAP).
Architecturally, an XDMS is not a single monolithic server but a logical function that can be implemented as a dedicated server for a specific service (e.g., a Presence XDMS for presence lists) or as a shared resource. It interfaces with other IMS core elements like the Home Subscriber Server (HSS) for authentication and subscription data. The core protocol for interaction is XCAP, an HTTP-based protocol that maps XML document elements and attributes to HTTP URIs. This allows clients to use standard HTTP methods (GET, PUT, DELETE) to perform operations on specific fragments of an XML document without needing to handle the entire document, enabling efficient updates and reducing network traffic.
A key operational role of the XDMS is to enforce authorization policies, ensuring that only subscribed and authenticated users or authorized network entities can access or modify specific documents. It also handles document versioning and conflict resolution when concurrent updates occur. The XDMS often works in conjunction with an Aggregation Proxy, which acts as a single point of contact for the UE, routing XCAP requests to the correct specific XDMS (e.g., Shared XDMS, Group XDMS, RLS XDMS) based on the application usage. This modular design allows for scalable service deployment and clear separation of concerns between different service enablers in the IMS ecosystem.
Purpose & Motivation
The XDMS was created to address the need for a standardized, centralized, and secure method to manage user data and service configuration within the IMS framework. Prior to its specification, service data was often stored in proprietary, siloed formats within individual application servers, making data sharing between services difficult and hindering service interoperability. This fragmentation limited the creation of composite services that could leverage common user data, such as a shared contact list for presence, messaging, and conferencing.
Its introduction in Release 6 was motivated by the vision of IMS as a service delivery platform capable of supporting a wide range of multimedia services from different vendors. The XDMS, by leveraging XML for data representation and HTTP/XCAP for management, provided a vendor-neutral, web-friendly paradigm for data handling. This solved critical problems of data consistency, access control, and network efficiency, enabling personalized and interactive services. It laid the groundwork for rich communication suites by ensuring that user-defined data—like buddy lists, group definitions, and service preferences—could be consistently managed and accessed across the network, forming the data layer for the IMS service architecture.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (32 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-6, normative work from Rel-15.
In Release 15, the XDMS function was enhanced to support new subscription and download procedures for the MCPTT UE and MCPTT Server, specifically after MCPTT user authentication and for the service configuration document. The release also introduced a formal Document Creation Flow and included corrections to the MCPTT UE initial configuration document schema, configuration management, and the MCPTT User Profile Document name.
- 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 XDMS updates included enhancements to support additional commencement modes for group calls in group documents and the inclusion of an absolute URI for the media storage function of the MCData content server. The release also introduced corrections and additions to configuration documents, server URIs, IP versions, and CMS document paths, alongside implementing document name constraints.
- Update group document to support additional commencement modes for group calls TS 24.481CR0039
- Included absolute URI associated with the media storage function of MCData content server TS 24.484CR0135
- Correction on MCx UE configuration document TS 24.484CR0105
- 24.484 Server URI and IP version additions TS 24.484CR0108
- 24.484 CMS documents paths TS 24.484CR0115
- Document name constraints TS 24.484CR0117
+ 1 more changes
In Release 17, the XDMS function was enhanced to support new configuration management capabilities for Mission Critical services, specifically for call transfer and call forwarding in MCPTT private calls. It also introduced new procedures for the SNSCE server using both CoAP and HTTP protocols. Furthermore, updates were made to group documents to include a "preconfigured-group-use-only" attribute and to the MCData service configuration to manage the hostname of notification servers.
- Add preconfigured-group-use-only to group document TS 24.481CR0044
- Call transfer for MCPTT private call, Configuration Management part TS 24.484CR0171
- Call forwarding for MCPTT private call, Configuration Management part TS 24.484CR0182
- The hostname of the MCData notification server(s) configured in the MCData service configuration TS 24.484CR0208
- SNSCE server CoAP procedure TS 24.549CR0007
- SNSCE server HTTP procedure TS 24.549CR0011
In Release 18, the XDMS function introduced new migration elements within the user profile configuration documents for MCPTT, MCVideo, and MCData services. The release also provided clarifications on the usage of the `<Server-URI>` element and on handling multiple GKTPs in the group document, while removing the obsolete MCS GW UE initial configuration document. Additionally, it included several XSD corrections and updates to address implementation errors and backward compatibility issues in service configuration and group 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
- Clarification of multiple GKTPs in group document TS 24.481CR0069
- Clarification on the usage of <Server-URI> element TS 24.484CR0259
- Removal of MCS GW UE initial configuration document TS 24.484CR0274
+ 3 more changes
In Release 19, the XDMS function introduced the addition of an LMS URI within the MCS UE initial configuration document and defined a new IANA registration template for the Location user configuration data document. These changes were accompanied by corrections to the MCS Server configurations. The updates specifically enhanced the management of user configuration data and registration formats for location-based services within the XML document management framework.
Explore further
Broader topics and technologies where XDMS plays a role.
Defining Specifications
3GPP specifications that define or reference XDMS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.779 vd00 | MCPTT over LTE Stage 2 Study | Rel-13 |
| TR 23.979 vj00 | PoC over 3GPP Systems Architectural Requirements | Rel-19 |
| TS 24.481 vj20 | Mission Critical Services (MCS) group management | Rel-19 |
| TS 24.484 vj30 | MCS Configuration Management | Rel-19 |
| TS 24.549 vj10 | SEAL Network Slice Capability Enablement Protocol | Rel-19 |
| TS 32.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 |
| TS 32.808 v1800 | Common User Profile Storage Framework | Rel-8 |