Local Device Stimulus Scheduling for Network Outage Reliability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Smart devices that rely on network-based services often fail to function during network outages or unavailability, leading to unreliable performance of critical functions like alarms and home automation, especially when users attempt to schedule stimulus-dependent notifications or actions.

Innovation Solution

A voice-based service platform that includes a local audio device and a network-based control service, where the local device can initiate actions independently without real-time network instructions, using a stimulus responder to perform scheduled notifications and home automation tasks even in the absence of network connectivity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If devices rely on network-based services for functionality, then service capability and connectivity are improved, but reliability during network outages deteriorates

Engineering Contradiction:
Improveservice capabilityVSAvoidfunctionality during network outages
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary actions by scheduling stimulus-based actions in advance on the local device before network connectivity is lost. The local device stores these scheduled actions locally and executes them automatically when their corresponding stimuli occur, without requiring real-time network communication. This ensures critical functions like alarms and notifications continue to operate reliably during network outages.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If real-time network communication is required for stimulus-based actions, then control precision is improved, but reliability during network unavailability deteriorates

Engineering Contradiction:
Improvecontrol precisionVSAvoidexecution reliability
Core Design Contradiction:
Measurement precisionVSReliability

Solution Approach 1:

The system segments the control function by separating the scheduling of stimulus-based actions from their execution. The control service schedules actions and stores them locally on the device, while the local device independently executes them when stimuli occur. This segmentation allows precise control scheduling while maintaining execution reliability without continuous network communication.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If critical functions are scheduled dependent on network availability, then service integration is improved, but functional reliability deteriorates

Engineering Contradiction:
Improveservice integrationVSAvoidfunctional reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The local device performs self-service by executing scheduled stimulus-based actions autonomously without requiring network-based control service intervention at execution time. The device monitors for stimuli locally and automatically performs the scheduled actions, ensuring functional reliability even when the network-based control service is unavailable.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11132173B1Network scheduling of stimulus-based actions
Publication Date: 2021.09.28 AMAZON TECH INC
  • US11132173B1 patent drawing
  • US11132173B1 patent drawing

AI summary

A speech-based service platform includes a local device in a user premises and a network-based control service that directs the local device to perform actions for a user. The user may at times request that the service schedule a notification or other action at a specified future time or in response to other stimuli that may occur in the future. Upon receiving a request from the user, the control service immediately instructs the local device to schedule the notification or other action. If the control service is unable to contact the local device, however, the request is canceled and the user is notified that the action has not been scheduled. Non-priority actions requested by the user may be accepted and implemented at the local device when communications become available.