Description
The XML Document Management Client (XDMC) is a client-side component within the 3GPP XML Document Management (XDM) framework, responsible for initiating requests to manage XML documents stored on XDM Servers (XDMS). It is typically implemented in user equipment (UE), such as smartphones or IoT devices, or in application servers that require access to user-specific service data. The XDMC communicates with the XDM Server using the XML Configuration Access Protocol (XCAP) over HTTP, supporting operations like HTTP GET (retrieve), PUT (create/update), and DELETE (remove) on XML documents. These documents contain configuration data for various services, such as presence authorization rules, group definitions for messaging, or user preferences for multimedia applications.
How the XDMC works involves a series of steps: first, it authenticates with the network, often via the Aggregation Proxy, which acts as a gateway to the XDM Server. Once authenticated, the XDMC constructs XCAP requests targeting specific XML documents identified by Uniform Resource Identifiers (URIs). For example, to update a presence list, the XDMC sends an HTTP PUT request with the modified XML content to the appropriate XDMS. The XDMC also handles responses from the server, including error codes and conflict resolution, ensuring data consistency. Additionally, the XDMC can subscribe to document changes using SIP-based notifications, allowing it to receive updates when other clients modify shared documents, enabling real-time synchronization across services.
Key components of the XDMC include the XCAP Client, which implements the protocol logic; the Document Manager, which handles local caching and processing of XML data; and the Interface Layer, which integrates with the device's application layer or service enablers. The XDMC's functionality is detailed in specifications like TS 24.481 for XCAP protocol details and TS 24.549 for XDM client behavior. Its role is critical in enabling user-centric services, as it provides the means for users to manage their data directly from their devices. For instance, in a group chat service, the XDMC allows a user to add contacts to a group list stored on the network, which can then be accessed by multiple applications. By standardizing client behavior, the XDMC ensures interoperability across different devices and network implementations, supporting a wide range of 3GPP services from basic voice over LTE (VoLTE) to advanced 5G multimedia applications.
Purpose & Motivation
The XML Document Management Client (XDMC) was developed to provide a standardized client interface for managing XML-based service data in 3GPP networks, addressing the need for user-controlled and application-accessible configuration management. Prior to XDMC, service data management was often server-centric or relied on proprietary client implementations, limiting user autonomy and causing compatibility issues. XDMC solves this by defining a common client protocol (XCAP) that allows any compliant device or application to interact with XDM Servers, empowering users to personalize their services and enabling seamless integration across different service enablers.
Historically, as IMS and rich communication services gained traction, there was a demand for clients that could efficiently handle service data without requiring complex backend integration. XDMC, introduced in 3GPP Release 13 as an evolution of earlier XDM concepts, was motivated by the proliferation of smartphones and the need for consistent data management across diverse applications. It addresses limitations of ad-hoc client implementations by providing a uniform method for document operations, reducing development effort and enhancing user experience. For example, before XDMC, managing group lists might require separate clients for messaging, presence, and conferencing, leading to fragmented data.
The purpose of XDMC extends to supporting regulatory and privacy requirements, as it allows users to control access to their data through client-initiated updates. It also facilitates network efficiency by offloading document processing to the client side, reducing server load. In the context of 5G and IoT, XDMC enables lightweight clients for constrained devices to manage configuration data, supporting use cases like smart city deployments. By serving as the user-facing endpoint of the XDM framework, XDMC plays a vital role in realizing the vision of personalized, interoperable services in modern 3GPP networks.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (31 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-13, normative work from Rel-15.
In Release 15, the XDMC function was introduced for both the MCPTT UE and the MCPTT Server, enabling them to act as XML Document Management Clients to subscribe to and download service configuration documents. This included specifying the procedures for a UE downloading documents after user authentication and for a server to download the configuration document. Additionally, corrections were made to the schemas for the MCPTT UE initial configuration document and the MCPTT User Profile 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 XDMC function was updated to support additional commencement modes for group calls within group documents. The release also introduced service configuration enhancements to limit the number of authorized clients per MCPTT or MCData user. Furthermore, corrections and clarifications were made to the MCx UE configuration document and to various configuration document paths and constraints.
- Update group document to support additional commencement modes for group calls TS 24.481CR0039
- Update service configuration to support limiting the number of authorized clients per MCPTT/MCData user TS 24.484CR0142
- Correction on MCx UE configuration document TS 24.484CR0105
- 24.484 CMS documents paths TS 24.484CR0115
- Document name constraints TS 24.484CR0117
- Corrections on configurations documents TS 24.484CR0153
In Release 17, the XDMC function was enhanced to support new configuration management procedures for Mission Critical services, specifically for call transfer and call forwarding in MCPTT private calls. Additionally, updates were made to service configuration to limit the number of authorized clients per MCVideo service user. The release also introduced the capability to mark a group document for "preconfigured-group-use-only" and added new client procedures for the SNSCE using both CoAP and HTTP.
- Add preconfigured-group-use-only to group document TS 24.481CR0044
- Update service configuration to support limiting the number of authorized clients per MCVideo service user TS 24.484CR0163
- Call transfer for MCPTT private call, Configuration Management part TS 24.484CR0171
- Call forwarding for MCPTT private call, Configuration Management part TS 24.484CR0182
- SNSCE client CoAP procedure TS 24.549CR0006
- SNSCE client HTTP procedure TS 24.549CR0010
In Release 18, the XDMC function was enhanced with new elements for migration within the MCPTT, MCVideo, and MCData user profile configuration documents. Other updates included the ability for a client to retrieve data from the NSCE, clarifications for handling multiple GKTPs in a group document, and the removal of the MCS GW UE initial configuration document. Furthermore, several XSD corrections and changes were made to address implementation errors and service configuration document issues.
- 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
- Retrieve data and information from NSCE client TS 24.549CR0019
- Clarification of multiple GKTPs in group document TS 24.481CR0069
- Removal of MCS GW UE initial configuration document TS 24.484CR0274
+ 3 more changes
In Release 19, the XDMC function was enhanced with the addition of an LMS URI in the MCS UE initial configuration document and the inclusion of an Idm client id. Furthermore, a new IANA registration template was defined for the location user configuration data document.
Explore further
Broader topics and technologies where XDMC plays a role.
Defining Specifications
3GPP specifications that define or reference XDMC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| 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 |