Servers, systems, and methods for automatically transforming a MQTT topic-payload into any format

Patent metadata

Field	Value
Publication number	US-12425485-B2
Application number	US-202318371605-A
Country	US
Kind code	B2
Filing date	Sep 22, 2023
Priority date	Sep 23, 2022
Publication date	Sep 23, 2025
Grant date	Sep 23, 2025

Abstract

In some embodiments, the disclosure is directed to systems and methods for automatically generation multiple topic-payload with different formats using a single instance of a topic-payload hard coded into an MQTT client. In some embodiments, the system is configured to allow a user to alter the output of an MQTT client while the MQTT program is executing in a runtime environment. In some embodiments, the system includes instructions hard coded into the MQTT client that cause the client to communication with a transformation module not executing in the runtime environment. In some embodiments, instructions stored on the transformation module can be updated and referenced during a publish and/or subscribe operation. In some embodiments, the MQTT client includes one or more of a publisher, a broker, and a client.

First claim

I claim:

1. A system for enabling communication between Message Queuing Telemetry Transport (MQTT) publishers and MQTT subscribers using different communication formats comprising:
one or more computers comprising one or more processors and one or more non- transitory computer readable media, the one or more non-transitory computer readable media having program instructions stored thereon that when executed cause the one or more computers to:
receive, at a broker device, a first topic-payload in a first hard coded format from a first publisher device executing during runtime in a first runtime environment, the first hard coded format being compatible with a first subscriber device and incompatible with a second subscriber device, the first topic-payload comprising a first topic and a first payload;
transmit, by the broker device, the first topic-payload in the first hard coded format to a transformation element associated with a broker device, the transformation element executing a transformation operation that transforms the first hard coded format to a second format compatible with the second subscriber device, the transformation operation occurring outside the first runtime environment and during the runtime on the first publisher device;
receive, by the broker device, the first topic-payload in the second format, the second format being compatible with the second subscriber device; and
transmit, by the broker device, the first topic-payload in the first hard coded format to the first subscriber device and the first topic-payload in the second format to the second subscriber device.

2. The system of claim 1 ,
wherein the first subscriber device is subscribed to the broker in the first hard coded topic-payload format for to receive the first topic-payload, and the second subscriber device is subscribed to the broker in the second format to receive the first topic payload.

3. The system of claim 2 ,
wherein the first publisher enables a user to define the first hard coded topic-payload format for transmitting the first topic-payload, the first hard coded topic payload format being unmodifiable by the first publisher device while the first publisher device is executing.

4. The system of claim 1 ,
wherein a transformation file associated with the transformation element is modified while the first publisher device is executing in the first publisher runtime environment
and executes the transformation operation.

5. The system of claim 1 , further comprising
receive, at the broker device, a third topic-payload in a third topic payload format from a third subscriber.

6. The system of claim 5 ,
wherein the first subscriber is configured to receive the first topic-payload in the first topic-payload format and cannot be modified while executing in a first subscriber runtime environment,
the second subscriber is configured to receive the first topic-payload in the second topic-payload format and cannot be modified while executing in a second subscriber runtime environment, and the third subscriber is configured to receive the third topic payload in a third topic payload format and cannot be modified while executing in the third subscriber runtime environment.

7. The system of claim 1 ,
wherein the transformation operation comprises a parsing operation.

8. The system of claim 7 ,
wherein the parsing operation is configured to:
identify, by the one or more processors, one or more topics and one or more payloads in the first topic-payload format;
parse, by the one or more processors, the topic-payload format into one or more topics and one or more payloads;
generate, by the one or more processors, the second topic-payload format using the parsed first topic-payload format.

9. A system for enabling communication between Message Queuing Telemetry Transport (MQTT) publishers and MQTT subscribers using different communication formats comprising:
one or more computers comprising one or more processors and one or more non- transitory computer readable media, the one or more non-transitory computer readable media having program instructions stored thereon that when executed cause the one or more computers to:
receive a first topic-payload in a first hard coded format from a first publisher device executing in a first runtime environment, the first hard coded format being compatible with a first subscriber device and incompatible with a second subscriber device, the first topic-payload comprises multiple topics and payloads;
parsing the first topic-payload from the first hard coded format to separate the multiple topic and payloads within the first topic-payload;
executing a transformation operation that transforms each of the multiple topics and payloads in the first hard coded format to at least a second format compatible with the second subscriber device outside the first runtime environment and during runtime on the first publisher device; and
transmit, by the broker device, the first topic-payload and each of the multiple transformed topics and payloads in different formats to the first publisher device for publishing to subscribers associated with the different formats, wherein at least one of the different formats is a second format associated with a second subscriber.

10. The system of claim 9 ,
wherein the first subscriber device is subscribed to receive the first topic-payload in the first hard coded topic-payload format, and the second subscriber device is subscribed to receive the first topic payload in the second format.

11. The system of claim 9 ,
wherein the first publisher enables a user to define the first hard coded topic-payload format for transmitting the first topic-payload, the first hard coded topic payload format being unmodifiable by the first publisher device while the first publisher device is executing.

12. The system of claim 9 ,
wherein at least one of the different formats is a third format associated with a third subscriber.

13. The system of claim 12 ,
wherein the first subscriber is configured to receive the first topic-payload in the first topic- payload format and cannot be modified while executing in a first subscriber runtime environment,
the second subscriber is configured to receive the first topic-payload in the second topic- payload format and cannot be modified while executing in a second subscriber runtime environment, and the third subscriber is configured to receive the third topic payload in a third topic payload format and cannot be modified while executing in the third subscriber runtime environment.

Assignees

• Aveva Software Llc

Inventors

• Hrishekesh Karthik

Classifications

• H04L67/12

  specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks · CPC title

• G06F16/258

  Data format conversion from or to a database · CPC title

• H04L67/567

  Integrating service provisioning from a plurality of service providers · CPC title

• H04L67/55 Primary

  Push-based network services · CPC title