---
title: "MQTT explained: versions 3.1.1, 5.0 and Sparkplug | Quantlix"
description: "MQTT is the OASIS publish-subscribe messaging protocol for IoT and industrial telemetry. Compare MQTT 3.1.1 and 5.0, quality of service levels and Sparkplug."
canonical: "https://quantlix.com/en/standards/mqtt/"
last-updated: 2026-11-16
---

Source: https://quantlix.com/en/standards/mqtt/
Language: en
Description: MQTT is the OASIS publish-subscribe messaging protocol for IoT and industrial telemetry. Compare MQTT 3.1.1 and 5.0, quality of service levels and Sparkplug.

**MQTT** [Industrial and technical data](https://quantlix.com/en/standards/#industrial)

# MQTT: lightweight publish-subscribe messaging for devices

MQTT is the OASIS standard publish-subscribe messaging protocol for devices and telemetry, in which clients exchange messages through a broker. Versions 3.1.1 (also ISO/IEC 20922) and 5.0 are in use.

[Discuss your project](https://quantlix.com/en/contact/) [Read the key points](https://quantlix.com/en/standards/mqtt/#standard-overview)

## At a glance

**Full name**

MQTT Version 5.0 and MQTT Version 3.1.1 (ISO/IEC 20922:2016, Message Queuing Telemetry Transport v3.1.1)

**Published by**

OASIS MQTT Technical Committee; ISO/IEC JTC 1 for ISO/IEC 20922

**Type**

Open messaging protocol standard

**Current version**

MQTT 5.0, OASIS Standard of 7 March 2019; MQTT 3.1.1, OASIS Standard of 29 October 2014 (Errata 01, 2015), also ISO/IEC 20922:2016

**Applies to**

Devices, gateways, brokers and applications that exchange telemetry and events over TCP/IP networks, in IoT, manufacturing, energy and oil and gas

**Last reviewed**

November 16, 2026 (2026-11-16)

## In plain terms

### Key points

- Clients publish messages to topics on a broker, and the broker forwards them to every client subscribed to a matching topic.
- Three quality of service levels trade speed for delivery guarantees: at most once, at least once and exactly once.
- MQTT 5.0 adds reason codes, user properties, session and message expiry, shared subscriptions and enhanced authentication.
- MQTT carries any payload, so the meaning of the data comes from a payload convention such as Sparkplug or your own schema.

### What is MQTT?

MQTT is **a lightweight publish-subscribe messaging protocol** standardized by OASIS. Clients connect to a server, usually called a broker, publish messages to named topics and subscribe to the topics they care about, so a sensor never needs to know which applications read its data.

It was built for constrained devices and unreliable networks, where small packets, simple clients and low bandwidth matter. That makes it a common choice for IoT telemetry, connected products and industrial data, from factory machines to remote sites with limited connectivity.

### What MQTT covers

- **Connections and sessions.** A client connects with an identifier, optional credentials and a keep-alive interval, and the broker can hold session state, such as subscriptions and undelivered messages, between connections.
- **Topics and wildcards.** Topics are hierarchical strings such as ` plant/line1/temperature `, and subscriptions can use the ` + ` and ` # ` wildcards to match many topics at once.
- **Quality of service.** QoS 0 delivers at most once, QoS 1 at least once with possible duplicates, and QoS 2 exactly once through a four-packet handshake.
- **Retained and will messages.** A retained message gives new subscribers the last known value right away, and a will message tells others when a client disconnects unexpectedly.
- **Security hooks.** User name and password fields, an extended authentication exchange in version 5.0, and guidance for running over TLS.

### MQTT 3.1.1, MQTT 5.0 and Sparkplug

MQTT 3.1.1 became an OASIS Standard on 29 October 2014, gained Errata 01 in December 2015 and is also published as ISO/IEC 20922:2016. MQTT 5.0, an OASIS Standard since 7 March 2019, keeps the same model and adds reason codes on acknowledgements, user properties, session and message expiry, topic aliases, request-response fields, shared subscriptions for load balancing and flow control.

MQTT deliberately says nothing about payload content. **Sparkplug**, from the Eclipse Foundation, fills that gap for industrial systems. Version 3.0.0, released in October 2022 and published as ISO/IEC 20237:2023, defines a topic namespace that begins with ` spBv1.0 `, a Protocol Buffers payload, and birth and death messages so host applications know which edge nodes and devices are online and which values are current. It works with both MQTT 3.1.1 and 5.0.

### How it shows up in software projects

- **Topic design.** A documented topic hierarchy, naming rules and access rules per topic prevent collisions and keep permissions manageable as devices are added.
- **Payload contracts.** Each topic has an agreed schema with units, timestamps and quality flags, whether that is Sparkplug or a documented JSON or Protocol Buffers format.
- **Delivery choices.** QoS, retained messages and session expiry are chosen per data stream, and consumers handle the duplicates that QoS 1 allows.
- **Broker security.** TLS, client certificates or credentials and per-topic authorization are configured on the broker, with publishing rights limited to the clients that need them.
- **Version records.** Each connection records its protocol version, since 3.1.1 and 5.0 clients behave differently on errors and sessions.

### How we work with MQTT

We design and build MQTT-based data platforms: edge gateways that publish plant or device data, broker and topic designs with clear permissions, and consumers that turn messages into dashboards, analytics and alerts. It is a regular part of our [IoT and edge computing](https://quantlix.com/en/services/iot-edge-computing/) work for [manufacturing](https://quantlix.com/en/industries/manufacturing/) and [oil and gas](https://quantlix.com/en/industries/oil-and-gas/) operations.

Where a plant already exposes [OPC UA](https://quantlix.com/en/standards/opc-ua/), the two can work together: OPC UA for rich models at the source and MQTT for distribution. We state Sparkplug or broker compatibility only with recorded test results for the specific versions involved.

## Where it applies

Industries where this standard often shapes the work.

- ### [Manufacturing](https://quantlix.com/en/industries/manufacturing/)

  Connected factories, quality inspection and production planning
- ### [Oil & Gas](https://quantlix.com/en/industries/oil-and-gas/)

  Asset monitoring, field data and maintenance planning

## Related standards

[All standards](https://quantlix.com/en/standards/)

- OPC UA

  ### [Industrial data and device interoperability](https://quantlix.com/en/standards/opc-ua/)

  OPC UA is the OPC Foundation's platform-independent architecture for exchanging industrial data securely, combining an information model with client-server and publish-subscribe communication. It is also IEC 62541.
- ISA-95

  ### [Enterprise and manufacturing integration](https://quantlix.com/en/standards/isa-95/)

  ISA-95 is the international standard, also published as IEC 62264, that defines how business systems such as ERP exchange information with manufacturing operations and control, using shared models and terms.
- IEC 62443

  ### [Industrial control system security](https://quantlix.com/en/standards/iec-62443/)

  IEC 62443 is the international series of standards for securing industrial automation and control systems, with requirements for asset owners, service providers, system integrators and product suppliers.

## Services that support this work

The services we usually bring to projects that involve this standard.

[View all services](https://quantlix.com/en/services/)

### [IoT and edge computing](https://quantlix.com/en/services/iot-edge-computing/)

Connect machines, sensors and business software with assessed IoT and edge integrations. Define data meaning, connectivity, permitted actions and recovery.

### [Data analytics](https://quantlix.com/en/services/data-analytics/)

Quantlix builds analytics pipelines and business intelligence tools that turn operational data into defined metrics, useful reports and decision support.

### [Cloud architecture](https://quantlix.com/en/services/cloud-architecture/)

Quantlix designs cloud infrastructure around workload requirements, security boundaries, operational visibility and cost, with an explicit path for deployment and recovery.

## Questions, answered

What teams usually ask us about this standard.

**Should I use MQTT 3.1.1 or MQTT 5.0?**

Use 5.0 for new systems when your broker and clients support it, since it adds reason codes, expiry, shared subscriptions and better error reporting. Version 3.1.1 remains widely deployed, and many brokers accept both.

**Is MQTT an ISO standard?**

Version 3.1.1 is also published as ISO/IEC 20922:2016. MQTT 5.0 is an OASIS Standard, and the related Sparkplug 3.0 specification for industrial payloads is published as ISO/IEC 20237:2023.

**Is MQTT secure?**

MQTT provides user name and password fields and, in version 5.0, an extended authentication exchange. Encryption comes from running it over TLS, on TCP port 8883 by convention, and the broker enforces which clients may publish or subscribe to each topic.

**What is Sparkplug?**

Sparkplug is an Eclipse Foundation specification that defines a topic namespace, payload encoding and session state management on top of MQTT for industrial systems. Version 3.0.0 was released in October 2022 and is published as ISO/IEC 20237:2023.

**What is the difference between MQTT and OPC UA?**

MQTT moves messages but does not define what they mean. OPC UA defines an information model and services, and its PubSub part can use an MQTT broker as a transport.

## Official sources

Read the official text before relying on any detail. What applies to you depends on your role, your location and the version in force.

- [MQTT Version 5.0, OASIS Standard](https://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html)
- [MQTT Version 3.1.1 Plus Errata 01, OASIS Standard](https://docs.oasis-open.org/mqtt/mqtt/v3.1.1/mqtt-v3.1.1.html)
- [ISO/IEC 20922:2016 (MQTT v3.1.1)](https://www.iso.org/standard/69466.html)
- [Eclipse Sparkplug specification](https://sparkplug.eclipse.org/specification/)

These guides explain each standard in plain terms. They are not legal advice, and they do not state that any product or organization conforms to a standard.

## Planning software around this standard?

Tell us which systems are involved and what you need to show. We will help you build the requirements in from the start.

[Discuss your project](https://quantlix.com/en/contact/)
