Extended JSON Data Format for IoT Efficiency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing human-readable object notation data formats, such as JSON, are not well-suited for use with IoT devices that have limited computing resources, as they lack efficient data packing, object serialization, and hashing/security features, limiting their ability to handle diverse devices and communication protocols effectively.

Innovation Solution

The introduction of extended JSON (xJSON) that includes data packing through compression, object serialization, and hashing/security features, such as Base64 encoding and hashing/security operations, while maintaining compatibility with standard JSON formats by using qualifiers in key-value pairs, allowing selective application of extensions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If standard JSON format is used for IoT device communication, then compatibility and ease of implementation are improved, but data efficiency and processing performance deteriorate due to lack of packing and serialization features

Engineering Contradiction:
ImprovecompatibilityVSAvoiddata processing efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent segments the data transmission process by introducing a type field that divides data into different categories (standard JSON, packed, serialized, hashed). This allows the system to selectively apply different processing methods to different data elements, improving overall efficiency while maintaining compatibility with standard JSON parsers for elements that don't require extension processing.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the parameter state of data by introducing three distinct modes: standard JSON (unchanged), packed (compressed representation), and serialized (converted to different format). The type field indicates which parameter transformation has been applied, allowing receivers to appropriately process each data element based on its state.

Inventive Principle:
Principle #35Parameter changes

2Loss of energy

If data packing and compression are applied to JSON data, then bandwidth usage and processing requirements are reduced, but device complexity and implementation difficulty increase

Engineering Contradiction:
Improvebandwidth usageVSAvoidimplementation complexity
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

The type field acts as an intermediary that mediates between the sender and receiver. It carries metadata information about how the data should be processed without requiring complex negotiation protocols. The receiver uses this simple type indicator to select the appropriate processing method, avoiding the need for complex device logic while still enabling efficient data transmission.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If object serialization and hashing features are added to JSON, then security and data integrity are improved, but processing overhead and computational resources increase

Engineering Contradiction:
Improvedata integrityVSAvoidcomputational resources
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent applies security and efficiency features partially rather than universally. The type field allows the system to apply packing, serialization, or hashing only to specific data elements that benefit from these operations, while leaving other elements in standard JSON format. This selective application reduces overall computational overhead while still providing security and integrity protection where needed.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10609009B2Extended javascript object notation file generator circuitry and process
Publication Date: 2020.03.31 TEXAS INSTRUMENTS INC
  • US10609009B2 patent drawing
  • US10609009B2 patent drawing
  • US10609009B2 patent drawing

AI summary

Methods and apparatus to provide extended object notation data are disclosed. An example apparatus includes a data handler having a first input to receive object data and a first output to output an object notation key-value pair for the object data; a string processor having a second input coupled to the first output and a second output to convey the object notation key-value pair without string literals; and a hashing and encryption handler having a third input coupled to the second output and a third output to convey the key-value pair signed with a private key, to convey the key-value pair encrypted with a public key, and to convey an indication that the encrypted key-value pair is encrypted in a key of the encrypted key-value pair.