IoT Device Soft-Wiring for Dynamic Control Group Pairing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing IoT systems face limitations in dynamic control-group pairing and data synchronization across devices, particularly in the absence of a central hub, which restricts flexibility and resilience in device interactions and data management.

Innovation Solution

Devices are programmed to dynamically change control group pairings based on time and location, and they maintain and share operational data, including state, netlist, and control logic, enabling decentralized operation and synchronization among devices within and between control groups.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If devices use fixed inter-device connections, then device connectivity is stable and reliable, but system flexibility and adaptability are reduced

Engineering Contradiction:
Improvesystem flexibilityVSAvoiddevice connectivity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements soft-wiring that allows device connections to be dynamically reconfigured based on operational context, time, and location. Control group pairings are not fixed but can be modified in real-time, enabling the system to adapt to changing conditions while maintaining reliable communication through established protocols.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The soft-wiring architecture enables devices to serve multiple functions and belong to different control groups depending on contextual requirements. A single device can participate in various functional relationships dynamically, increasing system versatility without sacrificing connection reliability through the use of standardized communication protocols.

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

2Ease of operation

If a central hub is used to manage device coordination, then control and management is centralized and simplified, but system complexity and single points of failure increase

Engineering Contradiction:
Improvedevice coordinationVSAvoidsystem architecture
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent segments the centralized control function into distributed components residing on individual devices. Each device maintains its own control logic and can independently coordinate with others in its control group, eliminating the need for a single central hub while distributing management responsibilities across multiple nodes.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Devices are equipped with embedded logic to autonomously manage their own coordination and control functions. Rather than relying on a central hub for all decisions, devices can independently execute control operations based on their programmed logic, reducing system architecture complexity and eliminating single points of failure.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If control group pairings are static, then device relationships are simple and easy to manage, but system adaptability to changing conditions is limited

Engineering Contradiction:
Improvecontrol group pairingVSAvoidpairing management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Control group pairings are implemented as dynamic rather than static relationships. The system can automatically reconfigure which devices belong to which control groups based on contextual factors such as time of day, location data, and operational state, enabling adaptability without requiring complex manual pairing management.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system incorporates feedback mechanisms that monitor contextual conditions and automatically adjust control group pairings in response. This feedback-driven approach allows the system to adapt to changing conditions automatically, reducing the complexity of pairing management by eliminating the need for manual reconfiguration.

Inventive Principle:
Principle #23Feedback

4Reliability

If operational data is maintained centrally, then data synchronization is simplified, but data loss risk and system vulnerability increase

Engineering Contradiction:
Improvedata synchronizationVSAvoiddata management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements local copies of operational data on each device rather than centralized storage. Each device maintains its own copy of the operational data it needs, ensuring that data remains accessible even if other devices or communication channels fail, thereby improving reliability while distributing data management responsibilities.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system uses feedback mechanisms to detect data changes and automatically propagate updates across devices. When operational data changes on one device, this change is communicated to other devices in the control group, ensuring synchronization without requiring complex centralized data management infrastructure.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20240097931A1Decoupling IoT Devices with Soft-Wiring or other Configuration, Including Dynamic Variance of Control Group Pairings Based on Context Such as Time and/or Location
Publication Date: 2024.03.21 ROKU INC
  • US20240097931A1 patent drawing
  • US20240097931A1 patent drawing
  • US20240097931A1 patent drawing

AI summary

A method and system for dynamically controlling operation of a first device, the first device being configurable to respond to receipt of primitive user input (e.g., push of a button on the first device) by carrying out a control action with respect to one or more second devices. An example method includes detecting a context state such as time of day and/or location of the first device. Further, the example method includes, using the detected context state as a basis to control what control action the first device will take in response to the first device receiving the primitive user input, such as which second device the first device will control in response to receiving the primitive user input and/or controlling what operational state of a second device the first device will control in response to receiving the primitive user input.