Serialized Event Data for IoT Device Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The challenge in the Internet of Things (IoT) is the complexity of enabling devices from different vendors to communicate and interact seamlessly, due to varied communication protocols, data formats, and APIs, which requires significant programming effort, often exceeding the capacity of available programmers and necessitating a simpler method for non-technical users to control devices.

Innovation Solution

A computer-implemented method and system that uses serialized event data in a human-readable format, such as spreadsheets, to configure and control devices, allowing users to visualize and interact with device states without writing procedural code, by detecting events, generating data, identifying elements, performing operations, and displaying results, with error handling and metadata management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If standardized communication protocols and data formats are implemented across devices from different vendors, then device interoperability is improved, but the complexity of integration and the amount of programming work required increases

Engineering Contradiction:
Improvedevice interoperabilityVSAvoidintegration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a standardized data format and communication protocol as an intermediary layer between devices from different vendors. This mediator enables seamless interoperability by translating diverse device-specific protocols into a universal format, eliminating the need for complex custom integration work for each device pair.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a universal data exchange framework that can handle multiple device types, vendors, and protocols through a single standardized interface. This multi-functional approach allows any device to communicate with any other device without requiring vendor-specific integration code, reducing overall system complexity.

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

2Adaptability or versatility

If comprehensive programming is done to enable device interactions in the Internet of Things, then device functionality and interaction capability are improved, but the amount of programming work and time required increases significantly

Engineering Contradiction:
Improvedevice interaction capabilityVSAvoidprogramming time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent establishes communication protocols, data formats, and interaction frameworks in advance during the device design phase. By performing this programming work preliminarily and embedding it into the device firmware, the system eliminates the need for extensive custom programming when deploying devices in IoT scenarios, significantly reducing programming time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses configurable parameters and metadata within the standardized data format to adapt device interactions to different scenarios. Instead of writing custom code for each interaction type, the system changes parameters and uses pre-defined templates to handle various device interactions, reducing programming effort while maintaining full functionality.

Inventive Principle:
Principle #35Parameter changes

3Extent of automation

If procedural code is used to program devices, then precise control and automation are achieved, but the difficulty of programming increases and requires qualified programmers

Engineering Contradiction:
Improvedevice control precisionVSAvoidprogramming difficulty
Core Design Contradiction:
Extent of automationVSEase of operation

Solution Approach 1:

The patent uses spreadsheet formats as a simplified copy of traditional programming interfaces. Spreadsheets replicate the essential functionality of procedural code (data storage, manipulation, and logic) in a visual, cell-based format that is easier to understand and modify, allowing non-programmers to achieve precise device control without learning complex programming languages.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent replaces the mechanical system of writing and debugging textual procedural code with a visual spreadsheet-based system. This substitution maintains the automation and control precision of traditional programming while eliminating the syntax errors, compilation issues, and debugging complexity associated with code-based approaches.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

4Ease of operation

If visual spreadsheet-based control is used instead of procedural code, then ease of operation and accessibility to non-programmers are improved, but the precision and complexity of control may be reduced

Engineering Contradiction:
Improveuser accessibilityVSAvoidcontrol precision
Core Design Contradiction:
Ease of operationVSExtent of automation

Solution Approach 1:

The patent enhances spreadsheet functionality by allowing complex parameters, formulas, and data transformations that can represent sophisticated control logic. By enabling parameter changes and advanced spreadsheet features, the system maintains control precision while keeping the visual, accessible interface that non-programmers can use.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10474137B2Configuring or controlling a device via serialized event data
Publication Date: 2019.11.12 CEDALO AG
  • US10474137B2 patent drawing
  • US10474137B2 patent drawing
  • US10474137B2 patent drawing

AI summary

A computer-implemented method for configuring or controlling a device is provided. In addition, a computer program product, and a device are provided. The method comprises detecting, by the device, an event, generating serialized event data in response to the event, receiving the event data from the device, identifying, via an expression, at least one element of the event data, wherein the element indicates a state of the device, performing at least one operation on the element of event data, wherein the operation includes determining the state of the device, displaying a result of the operation, determining whether an indication of an error in the result is received, and when a determination is made that there is no error and the result indicates that the state of the device is a specified state, performing, by the device, a task.