Legacy Device Integration via JSON Schema Gateway
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy devices using proprietary data formats incompatible with Web-of-Things (WoT) standards, such as REST, HTTP, and JSON, are excluded from WoT integration due to format incompatibility.
Innovation Solution
A JSON schema is created to correspond with legacy data, including property definitions and a legacy object that describes the proprietary data format, allowing legacy devices to be processed and used as WoT Things, enabling interaction with WoT clients through a gateway.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If legacy devices use proprietary data formats, then device functionality is maintained, but compatibility with WoT standards is lost
Solution Approach 1:
The patent introduces a gateway as an intermediary component that sits between legacy devices and the WoT network. The gateway translates proprietary legacy data formats into standardized WoT formats (JSON, REST, HTTP), enabling legacy devices to communicate within the WoT ecosystem without modifying their core functionality or data formats.
2Adaptability or versatility
If WoT standards are strictly enforced, then system interoperability is improved, but legacy device inclusion is prevented
Solution Approach 1:
The patent segments the WoT architecture into distinct layers: a core WoT network layer that maintains strict standard enforcement for interoperability, and a gateway layer that handles legacy device integration. This segmentation allows the core system to remain simple and standardized while the gateway absorbs the complexity of translating and adapting legacy device protocols.
3Adaptability or versatility
If legacy data formats are translated to JSON format, then WoT compatibility is achieved, but data processing complexity increases
Solution Approach 1:
The gateway is designed to automatically perform format translation and data mapping without requiring manual intervention. The system includes automated schema validation, data type conversion, and protocol adaptation capabilities that enable the gateway to self-configure and self-optimize for different legacy device formats, reducing the processing complexity burden on users.
Data Source
AI summary
According to an aspect of an embodiment, a method may include obtaining a JavaScript Object Notation (JSON) schema that corresponds to legacy data. The legacy data may include a plurality of legacy data points corresponding to device features of a legacy device. The plurality of legacy data points may be delimited according to a legacy data format. The JSON schema may include a plurality of property definitions corresponding to the legacy data points. The JSON schema may additionally include a legacy object that describes the legacy data format in a manner that allows for processing of the legacy data using the JSON schema. The method may also include processing the legacy data using the plurality of property definitions and the legacy object included in the JSON schema in a manner that allows the legacy device to be used as a web-of-things Thing.