Description
Within the 3GPP architecture, Extensible Markup Language (XML) is not a 3GPP-invented technology but a fundamental, widely adopted standard (from W3C) used as a data format and messaging syntax across numerous specifications. It works by defining a set of rules for encoding documents in a format that is both human-readable and machine-processable. Data is structured using user-defined tags enclosed in angle brackets, creating a hierarchical tree of elements and attributes. This structured nature allows for the precise definition of complex data models, such as device management commands, service parameters, or policy rules.
XML's role in 3GPP systems is multifaceted. In the core network, it is the foundation for the Open Mobile Alliance Device Management (OMA DM) protocol, used for remote configuration and management of User Equipment (UE). Management commands and device data are formatted as XML documents for exchange between the DM server and the client on the device. For services, XML is used in the IP Multimedia Subsystem (IMS) for service configuration (e.g., in Ut reference point for XCAP) and in Presence service data formats. In network management, the 3GPP Network Resource Model (NRM) and related interface specifications often use XML schemas to define the information model exchanged between network elements and management systems.
The processing of XML in a 3GPP context involves parsers and validators within network elements and devices. When an XML document is received, a parser reads the document, checks it for well-formedness (correct syntax), and may validate it against a predefined XML Schema Definition (XSD) to ensure it conforms to the expected data structure. The extracted data is then used by the application logic—for instance, to update a device configuration, apply a new service policy, or populate a management information base. This decouples the data representation from the processing logic, promoting interoperability. Key components in its usage include XML namespaces (to avoid tag name conflicts), XSD for validation, and XPath for querying specific data within an XML document.
Purpose & Motivation
XML was adopted into 3GPP specifications to solve the problem of heterogeneous data representation and the need for flexible, extensible information exchange between network entities, management systems, and devices. Prior to its widespread use, proprietary binary formats or less structured text formats were common, which hindered multi-vendor interoperability and made system integration complex and costly. XML provided a vendor-neutral, standardized way to describe and transmit structured data.
The historical context for its adoption coincides with the move towards all-IP networks in 3G (UMTS) and the development of rich data services. As networks became more software-driven and services more complex, there was a critical need for a data format that could easily evolve. XML's extensibility allowed 3GPP working groups to define new data elements for new features (like IMS or LTE) without breaking existing systems, as parsers could ignore tags they did not understand. This was crucial for forward and backward compatibility.
Furthermore, XML addressed the need for automation in network and device management. The rise of OMA DM required a format that could represent complex management objects (like a device's APN settings or application preferences). XML's hierarchical structure perfectly modeled these objects. Its text-based nature also simplified debugging and logging compared to binary protocols. Thus, XML's purpose in 3GPP is to be the lingua franca for structured data, enabling the configuration, management, and provisioning of increasingly sophisticated mobile networks and services in an interoperable manner.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (35 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-5, normative work from Rel-15.
In Release 15, corrections were made to the XML schemas and namespace definitions for MCVideo services. Specifically, updates were applied to correct the `session-type` in the MCVideo Information XML schema and to fix the namespace prefix for MC location XML. These changes ensured proper parsing and construction of XML objects for these services, as supported by the underlying `System.XML` capability.
In Release 16, the XML function saw updates to correct and specify its use with 5G access, including fixes to the PIDF+XML schema and the enforcement of access-specific configuration for XCAP. The release also introduced a new XML schema for preconfigured regroup operations. These changes ensured proper policy handling and configuration when the access type involves 5G networks.
- Preconfigured regroup – XML schema for regroup using preconfigured group TS 24.379CR0529
- Error in the pidf+xml schema - 9A.3.1.2 TS 24.379CR0619
- Correct policy for XCAP when access type involves 5G TS 24.424CR0007
- Correct enforcement of access specific configuration for XCAP when using 5Gx TS 24.424CR0009
In Release 17, the XML function was enhanced by adding new attributes—specifically altitude, timestamp, and accuracy—to the location XML schemas for MCVideo, MCData, and MCPTT services. Furthermore, new capabilities for integrity protection were introduced for `pidf+xml` and `xcap-diff+xml` MIME bodies across these services, and support for SNPN configuration was added within the XCAP Management Object. The release also included work to formally define previously undeclared XML elements for location and MBMS usage within the relevant schemas.
- Add altitude, timestamp to MCVideo location XML schema TS 24.281CR0095
- Add accuracy to MCVideo location XML schema TS 24.281CR0115
- Add accuracy to MCData location XML schema TS 24.282CR0221
- Add altitude, timestamp to MCPTT location XML schema TS 24.379CR0625
- Add accuracy to MCPTT location XML schema TS 24.379CR0698
- SNPN configuration in XCAP MO TS 24.424CR0013
+ 8 more changes
In Release 18, the XML function saw specific corrections and enhancements, primarily involving fixes to the XML schemas for MCPTT location information and `mcpttinfo`, along with corrections to MIME body references for `application/resource-lists+xml` and `application/pidf+xml`. Additionally, integrity protection was newly added to the NOTIFY procedure for `xcap-diff` events. These updates focused on improving the robustness and correctness of XML-based data formats and security mechanisms within specified services.
- Fix references to application/resource-lists+xml MIME body TS 24.281CR0194
- Fix references to application/resource-lists+xml MIME body TS 24.282CR0343
- Fix references to application/resource-lists+xml MIME body (mcdata) TS 24.282CR0380
- Correction of application/pidf+xml MIME body extensions TS 24.379CR0845
- Fix references to application/resource-lists+xml MIME body TS 24.379CR0850
- Fix references to application/resource-lists+xml MIME body (mcptt) TS 24.379CR0930
+ 4 more changes
In Release 19, the primary update for the XML function involved corrections to the XML schemas for critical Mission Critical Services, specifically for MCPTT, MCData, and MCVideo Regroup procedures. These corrections ensured the proper parsing and construction of XML objects for service negotiation and user agent profiles as enabled by the System.XML namespace. The changes aimed to maintain interoperability and the correct encoding of profile metadata within the standardized CC/PP framework.
Explore further
Broader topics and technologies where XML plays a role.
Defining Specifications
3GPP specifications that define or reference XML, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.057 vj00 | Mobile Execution Environment (MExE) Specification | Rel-19 |
| TS 23.140 v1600 | MMS Non-Realtime Service Definition | Rel-6 |
| TS 23.218 vj00 | IMS Call Model Specification | Rel-19 |
| TS 24.141 vj00 | Presence Service Protocol Details | Rel-19 |
| TS 24.259 vj00 | Personal Network Management (PNM) Protocol Details | Rel-19 |
| TS 24.281 vj40 | MCVideo Signalling Control Specification | Rel-19 |
| TS 24.282 vj50 | MCData Signalling Control Protocols | Rel-19 |
| TS 24.337 vj00 | IMS Inter-UE Transfer Protocol Specification | Rel-19 |
| TS 24.379 vj50 | Mission Critical Push To Talk (MCPTT) call control | Rel-19 |
| TS 24.424 vj00 | XCAP over Ut for Supplementary Services MO | Rel-19 |
| TS 24.508 v820 | TIP and TIR Service Protocol Description | Rel-8 |
| TS 24.549 vj10 | SEAL Network Slice Capability Enablement Protocol | Rel-19 |
| TS 24.608 vj00 | 3GPP TS 24608: TIP/TIR Services Protocol | Rel-19 |
| TS 26.223 vj00 | IMS Telepresence Client Specification | Rel-19 |
| TS 26.307 vj00 | 3GPP HTML5 Profile Specification | Rel-19 |
| TS 26.802 vj20 | Multicast Enhancements for 5G Media Streaming | Rel-19 |
| TS 26.850 vg00 | Massive File Delivery for IoT Devices | Rel-16 |
| TS 26.851 vb20 | Enhancements to Multimedia (EMM) for PSS, MMS, MBMS | Rel-11 |
| TR 26.907 vj00 | HTML5 for 3GPP Services Study | Rel-19 |
| TR 26.938 vj00 | DASH Deployment Guidelines for 3GPP Networks | Rel-19 |
| TR 26.953 vj00 | Study on Service Interactivity for Streaming & Download | Rel-19 |
| TR 26.957 vj00 | Evaluation of MPEG DASH SAND for 3GPP | Rel-19 |
| TS 28.820 vc00 | Umbrella Operation Model for Fixed Mobile Convergence | Rel-12 |
| TS 29.198 v1900 | OSA API Overview Specification | Rel-9 |
| TS 29.199 v1900 | Multimedia Messaging Web Services | Rel-9 |
| TS 29.201 vj00 | RESTful Rx Interface for AF-PC Communication | Rel-19 |
| TS 29.214 vj20 | Policy and Charging Control over Rx | Rel-19 |
| TS 29.817 vc10 | Study on XML-based Rx interface for PCC | Rel-12 |
| TS 31.113 v1800 | USAT Interpreter Byte Code Specification | Rel-8 |
| TS 32.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 |
| TS 32.612 vj00 | Bulk Configuration Management IRP: Information Service | Rel-19 |
| TS 32.824 v900 | SOA and IRP Gap Analysis | Rel-9 |
| TS 37.579 vi40 | Mission Critical services conformance testing | Rel-18 |