Message Format Patches for Resource-Constrained Devices
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
Senders transmit the full data format definition only at the start of a messaging session, using data format identifiers and patches to update formats, allowing receivers to modify and store updated definitions efficiently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If full data format definitions are sent with each message, then message format compatibility is ensured, but resource consumption and battery drain increase
Solution Approach 1:
The data format definition is segmented into two parts: a compact identifier and a detailed format specification. The identifier is sent with each message to ensure format compatibility, while the detailed specification is transmitted only when the format actually changes, reducing redundant data transmission and energy consumption.
Solution Approach 2:
The complete data format definition is transmitted in advance at the beginning of a messaging session or when a format change occurs. The receiver stores this definition locally, allowing subsequent messages to reference it by identifier alone, eliminating the need to resend the full definition and thereby reducing energy usage.
2Reliability
If full data format definitions are sent with each message, then message format compatibility is ensured, but message size increases
Solution Approach 1:
The detailed data format definition is extracted from each message and transmitted separately at the session level or on-demand. Each message contains only a lightweight reference to the format definition, dramatically reducing message size while maintaining the ability to ensure format compatibility through the stored definitions.
Solution Approach 2:
The message structure is segmented to separate the compact format identifier (included in every message) from the detailed format specification (transmitted separately). This segmentation allows messages to remain small while still ensuring format compatibility through the identifier-reference mechanism.
3Reliability
If full data format definitions are sent with each message, then message format compatibility is ensured, but compute load increases
Solution Approach 1:
The complete data format definition is processed and stored in advance at the receiver side. When messages arrive with only an identifier reference, the receiver simply retrieves the pre-stored definition rather than processing full format definitions repeatedly, significantly reducing the compute load on resource-constrained devices.
Data Source
Figure 1
Figure 2
Figure 3
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.