IoT Tasking via JSON Description Files and Keyword Replacement

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current IoT technologies face challenges due to the use of resource-intensive XML formats and lack of standardized protocols, leading to inefficiencies in connecting and controlling diverse IoT devices, with most standards focusing on sensing capabilities rather than tasking capacities and requiring custom connectors for unified operation.

Innovation Solution

The proposal involves using lightweight JSON format description files and a keyword replacement method with a placeholder '{ID}' to standardize tasking capabilities, defining essential sections for communication, actuation, and authentication, enabling unified control of IoT devices through a web-service platform.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If XML format is used for describing IoT protocols, then flexibility and ease of use are improved, but storage space consumption increases

Engineering Contradiction:
Improveflexibility and ease of useVSAvoidstorage space
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The patent changes the format parameter from XML to JSON, which maintains the flexibility and ease of use for describing IoT protocols while significantly reducing the storage space required. JSON's more compact syntax achieves the same descriptive functionality with fewer bytes, directly resolving the contradiction between operational ease and storage consumption.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If individual connectors are used for different IoT brands, then specific protocol compatibility is improved, but device complexity and development cost increase

Engineering Contradiction:
Improveprotocol compatibilityVSAvoidnumber of connectors
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal connector based on JSON format that can handle multiple IoT protocols and brands through a standardized interface. This single multi-functional connector replaces the need for numerous brand-specific connectors, reducing system complexity while maintaining broad protocol compatibility through the unified JSON description framework.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The JSON description file acts as an intermediary layer between the universal connector and specific IoT devices. This intermediary standardizes the communication interface, allowing the connector to work with different IoT brands and protocols without requiring custom connectors for each, thereby reducing overall system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If customized connectors are developed for each IoT brand, then specific device control capability is improved, but productivity and development efficiency decrease

Engineering Contradiction:
Improvedevice control capabilityVSAvoiddevelopment efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The universal JSON-based connector maintains reliable device control capability while significantly improving development efficiency. Developers can control different IoT brands using the same standardized approach without needing to learn multiple proprietary connector interfaces, thus enhancing productivity while preserving control reliability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS10009410B2Description files and web service protocols for tasking capability on internet of things
Publication Date: 2018.06.26 NAT CENT UNIV
  • US10009410B2 patent drawing
  • US10009410B2 patent drawing
  • US10009410B2 patent drawing

AI summary

Description files and web service protocols for actuating things on Internet of things (IoT) are proposed. Essentials of every thing on IoT (‘IoT thing’) are defined in a description file. The description file is lightweight, versatile and standardized for web services. Thus, the IoT thing can be communicated through its protocol described in the description file. Therein, a keyword replacement method is used. In a command sent by a user at a client end, a specific keyword is used to replace an essential in the description file. Then, a complete message based on the protocol is generated to control the IoT thing. The present invention uniformly uses the same way for operating and managing IoT things of all brands and solving heterogeneity. The present invention significantly reduces development cost and may work out an automatic, high-performance and interoperable IoT ecosystem with applications.