Local Automation Engine with Cloud Failover for Smart Device Meshes

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Cloud-based smart device mesh automation systems face limitations in responsiveness and availability due to reliance on cloud computing resources and internet connectivity, leading to potential unavailability during network outages.

Innovation Solution

Implementing a local automation system within consumer premises that can execute smart device mesh automations locally with cloud-based failover, allowing for default execution by the local system and failover execution by the cloud system in case of local failure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If cloud-based automation system is used to execute automation routines, then scalability and feature richness are improved, but responsiveness and availability deteriorate due to round-trip communication delays and network dependency

Engineering Contradiction:

Improvefeature richnessVSAvoidresponse time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent segments the automation execution function into two parts: cloud-based automation system for routine execution and local automation system for time-critical execution. This segmentation allows the system to leverage cloud resources for complex automations while maintaining fast local response for time-sensitive operations, thus resolving the contradiction between feature richness and responsiveness

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The local automation system acts as an intermediary between the cloud-based automation system and smart devices. It receives automation routines from the cloud, executes them locally when responsiveness is critical, and synchronizes with the cloud system. This intermediary approach enables both cloud-based feature richness and local responsiveness to coexist

Inventive Principle:

Principle #24Intermediary (Mediator)

2Ease of operation

If cloud-based automation system is used to execute automation routines, then centralized control and management are improved, but system availability deteriorates during network outages or cloud unavailability

Engineering Contradiction:

Improvecentralized controlVSAvoidsystem availability

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The patent implements dynamic execution mode selection where the system can switch between cloud-based execution and local execution based on network availability and automation priority. The local automation system dynamically takes over execution when the cloud system is unavailable, ensuring continuous operation while maintaining centralized control capabilities when the network is functional

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The local automation system is pre-configured with automation routines and device information before network outages occur. This beforehand preparation allows the system to continue executing automations locally during cloud unavailability, cushioning against the reliability deterioration caused by network dependencies

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

3Loss of time

If local automation system is implemented for fast execution, then responsiveness is improved, but system complexity increases due to dual cloud and local infrastructure

Engineering Contradiction:

Improveresponse timeVSAvoidsystem architecture

Core Design Contradiction:

Loss of timeVSDevice complexity

Solution Approach 1:

The patent merges the cloud-based automation system and local automation system into a unified architecture where both systems share common automation routines, device models, and configuration data. This merging reduces the effective complexity by eliminating duplication and providing a single source of truth, while still delivering fast local response times

Inventive Principle:

Principle #5Merging (Combining)

4Reliability

If automation routines are executed locally, then responsiveness and availability are improved, but loss of synchronization with cloud system may increase

Engineering Contradiction:

Improveexecution availabilityVSAvoidsynchronization state

Core Design Contradiction:

ReliabilityVSLoss of information

Solution Approach 1:

The patent implements feedback mechanisms where the local automation system reports execution status, device states, and automation outcomes back to the cloud-based automation system. This feedback loop maintains synchronization between the distributed local systems and the centralized cloud system, preventing information loss while preserving the benefits of local execution availability

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS12348359B2Local automation engine in distributed environment

Publication Date: 2025.07.01 GOOGLE LLC

AI summary

Local execution of smart device mesh automations with cloud-based failover is described herein. Embodiments operate in context of network-connected devices in a smart device mesh with a local automation system, where all devices communicate with cloud-based automation, and at least some also communicate with local automation. A determination is made whether to claim each automation routine for local automation, or to automatically execute the automation by the cloud when triggered. Triggered locally claimed automation routines cause attempted default execution locally by local automation with automatic failover execution by the cloud-based automation. Some embodiments further involve electing an executor device as part of claiming an automation routine and/or monitoring execution of automation routines to determine when to automatically de-claim locally claimed automation routines with poor local execution success rates.