WAP Binary XML

Description

WBXML (WAP Binary XML) is a binary formatting protocol that encodes XML documents into a compact byte stream. It was developed by the WAP Forum to address the inefficiencies of transmitting verbose, text-based XML over slow and costly wireless links. The protocol works by tokenizing the XML structure: tags and attribute names are replaced with predefined binary codes from a document-specific code space, while string tables handle common strings to avoid repetition. The encoded document consists of a version byte, a public identifier for the document type, a string table, and the tokenized body. This binary representation significantly reduces the message size compared to its textual XML counterpart, leading to faster transmission and lower processing requirements on resource-constrained mobile devices.

Architecturally, WBXML is a presentation-layer protocol that sits above the transport layer (often WSP or HTTP) and below the application logic. A key component is the code space, defined in a Document Type Definition (DTD), which maps XML tags and attributes to specific single-byte tokens. The protocol supports multiple token pages for extensibility, allowing different XML vocabularies to be efficiently encoded. The string table, placed at the beginning of the WBXML stream, contains literal strings used in the document (like attribute values or text content) that are not tokenized, referenced later via index pointers.

In operation, an encoder parses an XML document, replaces known tags and attributes with their corresponding tokens, adds unknown strings to the string table, and outputs a sequential byte stream. The decoder reverses this process, using the same code space to reconstruct the original XML structure. WBXML supports content compression and can indicate the character encoding used. Within 3GPP networks, it is primarily specified in TS 23.057 for Mobile Station Application Execution Environment (MExE) services, enabling the delivery of compact, structured data for applications like service provisioning, configuration, and lightweight browsing in the WAP environment.

Purpose & Motivation

WBXML was created to enable efficient use of XML-based data formats in the early mobile internet era, characterized by severe bandwidth limitations, high latency, and limited device processing power. The WAP Forum, aiming to bring web-like services to mobile phones, needed a way to transmit structured data without the overhead of verbose text-based XML, which was impractical over slow circuit-switched data connections. WBXML solved this by providing a compact binary encoding that reduced transmission times, lowered air interface costs, and decreased the parsing complexity and memory footprint on devices.

The technology addressed the limitations of plain XML transmission, which consumed excessive bytes for repetitive tags and whitespace. By tokenizing common elements and using a shared string table, WBXML could often reduce document size by 50-80%, making interactive services feasible. Its adoption into 3GPP standards, starting in Release 10 for MExE, provided a standardized method for device management and service provisioning, ensuring interoperability across networks and handsets. WBXML facilitated the deployment of mobile data services before the widespread adoption of high-speed packet networks and powerful smartphones.

Key Features

• Binary tokenization of XML tags and attributes for compact representation
• String table mechanism to avoid repetition of literal strings
• Support for multiple code pages to encode different XML vocabularies
• Indication of document public identifier and character encoding
• Capability for inline string data and opaque application-specific data
• Stream-based encoding suitable for sequential transmission and parsing

Evolution Across Releases

Defining Specifications