REGISTER

FR
Search
×
FR

Placeholder headline

This is just a placeholder headline

API SPEC 14L: Lock Mandrels and Landing Nipples : Reaffirmed

$

273

BUY NOW

Placeholder headline

This is just a placeholder headline

API SPEC 20F: Corrosion Resistant Bolting for Use in the Petroleum and Natural Gas Industries : Reaffirmed

$

169

BUY NOW

Placeholder headline

This is just a placeholder headline

API TR 5NCL Nickel Content Limits for API 5CT Sour Service Products

$

149

BUY NOW

Placeholder headline

This is just a placeholder headline

API SPEC 19ICD: Inflow Control Devices : Reaffirmed

$

189

BUY NOW

Placeholder headline

This is just a placeholder headline

API MPMS CH 23.2: Reconciliation of Liquid Tank Car(s) Quantities : Reaffirmed

$

218

BUY NOW

Placeholder headline

This is just a placeholder headline

API SPEC 16A: Specification for Drill-through Equipment

$

322

BUY NOW

Placeholder headline

This is just a placeholder headline

API RP 13B-2: Field Testing Oil-based Drilling Fluids wA1

$

388

BUY NOW

ISO 20922:2016

ISO 20922:2016 Information technology – Message Queuing Telemetry Transport (MQTT) v3.1.1

CDN $0.00

Description

ISO/IEC 20922:2016 is a Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed so as to be easy to implement. These characteristics make it ideal for use in many situations, including constrained environments such as for communication in Machine to Machine (M2M) and Internet of Things (IoT) contexts where a small code footprint is required and/or network bandwidth is at a premium.

The protocol runs over TCP/IP, or over other network protocols that provide ordered, lossless, bi-directional connections. Its features include:

  • Use of the publish/subscribe message pattern which provides one-to-many message distribution and decoupling of applications.
  • A messaging transport that is agnostic to the content of the payload.
  • Three qualities of service for message delivery:
    • “At most once”, where messages are delivered according to the best efforts of the operating environment. Message loss can occur. This level could be used, for example, with ambient sensor data where it does not matter if an individual reading is lost as the next one will be published soon after.
    • “At least once”, where messages are assured to arrive but duplicates can occur.
    • “Exactly once”, where message are assured to arrive exactly once. This level could be used, for example, with billing systems where duplicate or lost messages could lead to incorrect charges being applied.
Edition

1

Published Date

2016-06-08

Status

PUBLISHED

Pages

73

Language Detail Icon

English

Format Secure Icon

Secure PDF

Abstract

ISO/IEC 20922:2016 is a Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed so as to be easy to implement. These characteristics make it ideal for use in many situations, including constrained environments such as for communication in Machine to Machine (M2M) and Internet of Things (IoT) contexts where a small code footprint is required and/or network bandwidth is at a premium.

The protocol runs over TCP/IP, or over other network protocols that provide ordered, lossless, bi-directional connections. Its features include:

  • Use of the publish/subscribe message pattern which provides one-to-many message distribution and decoupling of applications.
  • A messaging transport that is agnostic to the content of the payload.
  • Three qualities of service for message delivery:
    • "At most once", where messages are delivered according to the best efforts of the operating environment. Message loss can occur. This level could be used, for example, with ambient sensor data where it does not matter if an individual reading is lost as the next one will be published soon after.
    • "At least once", where messages are assured to arrive but duplicates can occur.
    • "Exactly once", where message are assured to arrive exactly once. This level could be used, for example, with billing systems where duplicate or lost messages could lead to incorrect charges being applied.

Previous Editions

Can’t find what you are looking for?

Please contact us at: