Message Format Patching for Resource-Constrained Edge Devices

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing messaging protocols, particularly in edge computing environments, require sending full data format definitions with each message, leading to increased resource consumption and battery drain in resource-constrained devices.

Innovation Solution

Implementing a system where senders send data format identifiers and patches to update message formats, allowing receivers to modify and store updated definitions, reducing the need to send full definitions with every message.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If full data format definitions are sent with each message, then message format completeness is ensured, but resource consumption and battery drain increase in edge devices

Engineering Contradiction:

Improvemessage format completenessVSAvoidbattery consumption

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The data format definition is segmented into a base format and incremental patches. Instead of transmitting the complete format definition each time, only the necessary patch segments are sent to update the format, reducing transmission data volume and energy consumption while maintaining format completeness through incremental updates.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The base data format definition is established in advance and stored in the data structure before actual message transmission. This preliminary action allows subsequent messages to reference the pre-stored base format and only transmit incremental patches, eliminating the need to resend the complete format definition and thereby reducing energy consumption.

Inventive Principle:

Principle #10Preliminary action

2Manufacturing precision

If full data format definitions are sent with each message, then format accuracy is maintained, but message size increases

Engineering Contradiction:

Improveformat accuracyVSAvoidmessage size

Core Design Contradiction:

Manufacturing precisionVSQuantity of substance

Solution Approach 1:

The incremental patch extracting the necessary update information from the complete data format definition. This extraction process separates the essential format changes from the redundant base format information, allowing transmission of only the minimal required data to maintain format accuracy while significantly reducing message size.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of transmitting the complete data format definition, the system transmits a lightweight patch that copies only the necessary update information. The receiver applies this patch to the stored base format, achieving format accuracy update with minimal message size transmission.

Inventive Principle:

Principle #26Copying

3Reliability

If full data format definitions are sent with each message, then format completeness is ensured, but CPU usage increases

Engineering Contradiction:

Improveformat completenessVSAvoidCPU usage

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system applies partial action by transmitting and processing only the necessary incremental patch information rather than the complete data format definition. This partial transmission and processing approach maintains format completeness through incremental updates while significantly reducing CPU usage during message handling.

Inventive Principle:

Principle #16Partial or excessive action

4Use of energy by moving object

If data format identifiers and patches are sent instead of full definitions, then resource consumption is reduced, but system complexity increases

Engineering Contradiction:

Improvebattery consumptionVSAvoidmessage format management

Core Design Contradiction:

Use of energy by moving objectVSDevice complexity

Solution Approach 1:

The data format identifier acts as an intermediary between the complete data format definition and the message transmission process. By referencing the stored base format through this identifier and applying incremental patches, the system manages format complexity centrally while keeping individual message transmissions simple and resource-efficient.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS12556620B2Message format indicator for resource-constrained devices

Publication Date: 2026.02.17 RED HAT INC

AI summary

Systems and methods for message format communication among resource-constrained devices are generally described. In some examples, a first message sent by an edge computing device may be received. A determination may be made that the first message comprises a first data format identifier. A determination may be made that the first message comprises a first data format patch. A determination may be made that the first data format identifier was previously stored in a data structure in association with a first data format. In various examples, the first data format may be modified using the first data format patch to generate a first modified data format. The first modified data format may be stored in the data structure in association with the first data format identifier. In some examples, a payload of the first message may be read using the first modified data format.