XMPP as a protocol was designed before the wide spread adoption of mobile devices, and is often cited as not being very mobile friendly as a result. However, this mostly stems from undocumented lore and outdated notions of how XMPP works. As the Internet and protocol design have changed to be more accommodating for mobile, so has XMPP.
This XEP aims to provide useful background knowledge of mobile handset behavior, and those considerations that client and server designers can take to ensure that bandwidth and battery are used efficiently.
The two major constraints on mobile devices are power and bandwidth. With the wide spread proliferation of 3G and LTE technologies, mobile bandwidth and speeds have become broadly comparable to broadband. However, they are still relatively expensive compared to traditional wired networks, and therefore conserving them is still desirable. This XEP mostly focuses on LTE as it already has a very wide deployment and will only continue to further replace 3G technologies.
XML, and by extension XMPP, is known to be highly compressible. Compression of XMPP data can be achieved with the DEFLATE algorithm (RFC 1951 ) via TLS compression (RFC 3749 ) or Stream Compression (XEP-0138)  (which also supports other compression algorithms). A description of the security implications of stream compression is beyond the scope of this document (See RFC 3749  or Stream Compression (XEP-0138)  for more information), but the author does not recommend using TLS compression with XMPP (or in general). If compression must be used, stream level compression should be implemented instead, and the compressed stream should have a full flush performed on stanza boundaries to help prevent chosen plaintext attacks. While this may mitigate some of the benefits of compression by raising compression ratios, in a large, real world deployment, network traffic was still observed to decrease by a factor of 0.58 when enabling Stream Compression (XEP-0138)  with ZLIB compression.
While the CPU cost of compression may directly translate to higher power usage, it is vastly outweighed by the benefits of reduced network utilization, especially on modern LTE networks which use a great deal more power per bit than 3G networks as will be seen later in this document. However, CPU usage is also not guaranteed to rise due to compression. In the aforementioned deployment of stream compression, a decrease in CPU utilization by a factor of 0.60 was observed, presumably due to reductions in TLS and packet handling overhead. Therefore CPU time spent on compression (for ZLIB, at least; other algorithms were not tested) can be considered negligable.
Supporting compression and performming a full flush on stanza boundaries is recommended for mobile devices.
While the wide spread adoption of LTE has dramatically increased available bandwidth on mobile devices, it has also increased power consumption. According to one study, early LTE devices consumed 5–20% more power than their 3G counterparts . On some networks that support the legacy SVLTE (Simultaneous Voice and LTE) or CSFB (Circuit-switched fallback) instead of the more modern VoLTE (Voice Over LTE) standard, this number would (presumably) be even higher.
XMPP server and client implementers, bearing this increased power usage in mind, and knowing a bit about how LTE radios work, can optimize their traffic to minimize network usage. For the downlink, LTE user equipment (UE) utilizes Orthogonal Frequency Division Multiplexing (OFDM), which is somewhat inefficient . On the uplink side a different technology, Single-carrier frequency division multiple access (SC-FDMA) is used, which is slightly more efficient than traditional OFDM, slightly offsetting the fact that broadcasting requires more power than receiving. LTE UE also implements a Discontinuous reception (DRX) mode in which the hardware can sleep until it is woken by a paging message or is needed to perform some task. LTE radios have two power modes: RRC_CONNECTED and RRC_IDLE. DRX is supported in both of these power modes. By attempting to minimize the time which the LTE UE state machine spends in the RCC_CONNECTED state, and maximize the time it stays in the DRX state (for RCC_CONNECTED and RRC_IDLE), we can increase battery life without degrading the XMPP experience. To do so, the following rules should be observed:
Whenever possible, data that is not strictly needed should not be transmitted (by the server or client). Supporting Client State Indication (XEP-0352)  is recommended. Most importantly, XMPP pings should be kept as far apart as possible and only used when necessary. Server operators are encouraged to set high ping timeouts, and client implementors are advised to only send pings when absolutely necessary to prevent the server from closing the socket.
If one is on 3G, transmitting a small amount of data will cause the radio to enter FACH mode which is significantly cheaper than its high power mode. On LTE radios, however, transmitting small amounts of data is vastly more expensive per bit due to the higher tail-time (the time it takes for the radio to change state) of approximately 11 seconds . On LTE radios, one should transmit as much data from the client as possible when the radio is already on (eg. by placing messages in a send queue and executing the queue as a batch when the radio is on). Similarly, when data is being received from the server, the mobile devices radio is already in a high power state and therefore any data that needs to be sent to the server should be transmitted.
These rules also apply to server operators: If the server receives data, the phones radio is already on, therefore you should flush any pending data as soon as possible after receiving data from a client.
This section provides pointers to other documents which may be of interest to those developing mobile clients, or considering implementing optimizations for them in servers.
Stream Compression (XEP-0138)  provides stream level compression.
Entity Capabilities (XEP-0115)  provides a mechanism for caching, and hence eliding, the disco#info requests needed to negotiate optional features.
Roster Versioning (XEP-0237)  provides a relatively widely deployed extension for reducing roster fetch sizes.
Stream Management (XEP-0198)  allows the client to send and receive smaller keep-alive messages, and resume existing sessions without the full handshake. This is useful on unstable connections.
Client State Indication (XEP-0352)  allows clients to indicate to the server that they are inactive, allowing the server to optimize and reduce unnecessary traffic.
Push Notifications (XEP-0357)  implements push notifications (third party message delivery), which are often used on mobile devices and highly optimized to conserve battery. Push notifications also allow delivery of notifications to mobile clients that are currently offline (eg. in an XEP-0198 "zombie" state).
Message Archive Management (XEP-0313)  lets clients fetch messages which they missed (eg. due to poor mobile coverage and a flaky network connection).
This XEP was originally written by Dave Cridland, and parts of his original work were used in this rewrite. Thanks to Atlassian (HipChat) for allowing me to release numbers from their XMPP compression deployment.
This document introduces no new security considerations.
This document requires no interaction with the Internet Assigned Numbers Authority (IANA).
No namespaces or parameters need to be registered with the XMPP Registrar as a result of this document.
This document in other formats: XML PDF
This XMPP Extension Protocol is copyright © 1999 – 2020 by the XMPP Standards Foundation (XSF).
Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the "Specification"), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation.
## NOTE WELL: This Specification is provided on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. ##
In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages.
This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which can be found at <https://xmpp.org/about/xsf/ipr-policy> or obtained by writing to XMPP Standards Foundation, P.O. Box 787, Parker, CO 80134 USA).
The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core (RFC 6120) and XMPP IM (RFC 6121) specifications contributed by the XMPP Standards Foundation to the Internet Standards Process, which is managed by the Internet Engineering Task Force in accordance with RFC 2026. Any protocol defined in this document has been developed outside the Internet Standards Process and is to be understood as an extension to XMPP rather than as an evolution, development, or modification of XMPP itself.
The primary venue for discussion of XMPP Extension Protocols is the <email@example.com> discussion list.
Discussion on other xmpp.org discussion lists might also be appropriate; see <http://xmpp.org/about/discuss.shtml> for a complete list.
Errata can be sent to <firstname.lastname@example.org>.
The following requirements keywords as used in this document are to be interpreted as described in RFC 2119: "MUST", "SHALL", "REQUIRED"; "MUST NOT", "SHALL NOT"; "SHOULD", "RECOMMENDED"; "SHOULD NOT", "NOT RECOMMENDED"; "MAY", "OPTIONAL".
4. LTE Smartphone measurements <http://networks.nokia.com/system/files/document/lte_measurements_final.pdf>
Note: Older versions of this specification might be available at http://xmpp.org/extensions/attic/
Advance to Active as per Council vote on 2018-01-10.
Include real world compression numbers and additional recommended reading.
Overhaul to include LTE.
Initial published version.
First draft. Also John's birthday.