Structured Data Store for IoT Interoperability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current software architecture patterns and communication protocols lack an abstraction layer capable of supporting universal interoperability among machines, leading to fragmented systems and costly integrations in the Internet of Things (IoT) ecosystem.

Innovation Solution

A structured program transfer protocol (SPTP), object event processor (OEP), and object view generator (OVG) within a structured data store (SDS) facilitate unified and normalized management of objects across machines, enabling efficient data and metadata transfer and processing through a two-dimensional dataset structure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional software architecture patterns and communication protocols are used, then existing systems can operate independently, but interoperability among machines is poor and integration costs are high

Engineering Contradiction:
ImproveinteroperabilityVSAvoidintegration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal object dataset structure that can represent any machine or device across different domains. This standardized structure enables diverse machines to communicate through a common interface, achieving multi-functionality and universal interoperability without requiring separate integration approaches for each machine type

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

Solution Approach 2:

The patent introduces an intermediary layer consisting of the structured data store, object event processor, and object view generator. This intermediary translates between different machine representations and a unified object model, facilitating communication while isolating the complexity of individual machine differences

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of manufacture

If machine-specific data structures are used, then each machine can be optimized independently, but systems become fragmented and integration becomes costly

Engineering Contradiction:
Improvesystem integration costVSAvoidsystem fragmentation
Core Design Contradiction:
Ease of manufactureVSStability of the object's composition

Solution Approach 1:

The patent merges disparate machine-specific data structures into a unified object dataset structure. By combining multiple machine representations into a single standardized format, the system eliminates fragmentation and reduces integration costs while maintaining the ability to represent diverse machine types

Inventive Principle:
Principle #5Merging (Combining)

3Adaptability or versatility

If no standardized abstraction layer is implemented, then implementation is simpler, but universal interoperability cannot be achieved

Engineering Contradiction:
Improveuniversal interoperabilityVSAvoidarchitecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent adds an abstraction dimension between physical machines and their representations. By introducing the object dataset structure as an intermediate dimensional layer, the system achieves universal interoperability without significantly increasing apparent complexity, as the abstraction handles machine diversity transparently

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS10545933B2Database-driven entity framework for internet of things
Publication Date: 2020.01.28 MIGLIORI DOUGLAS T
  • US10545933B2 patent drawing
  • US10545933B2 patent drawing
  • US10545933B2 patent drawing

AI summary

Unified and normalized management of an object within a structured data store on any machine and/or across difference machines. In an embodiment, a first resource on a first machine accesses an events dataset representing a two-dimensional structure. Each row in the events dataset comprises a plurality of event types, an identification of an entity, and an identification of an object representing a unique instance of the entity. Each row in the events dataset is processed based on its event type to create, update, or delete the object identified in the row. In a second embodiment, a first resource on a first machine accesses a view definition dataset comprising an identification of one or more attributes of one or more related entities and an identification of one or more objects of the one or more related entities. The view definition dataset is processed to retrieve attribute values for the objects and attributes identified in the view definition dataset.