Automated Error Interface Workflow for Non-Functional Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for determining remedial actions for computing device errors are often incomplete or unfeasible due to insufficient error log data and the inability to obtain user input from non-functional devices or those lacking input/output capabilities.

Innovation Solution

Automated workflow that generates user interfaces via determined communication channels to solicit information from users, using error log data to select relevant interfaces and channels based on error characteristics, ensuring timely and relevant user input collection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If automated workflows are implemented to collect error log data, then the completeness of error information is improved, but the complexity of the system increases

Engineering Contradiction:
Improvecompleteness of error informationVSAvoidsystem complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system enables self-service by allowing non-functional devices to automatically submit error log data without requiring user intervention. The automated workflow initiates communications, collects logs, and routes them appropriately, making the error reporting process autonomous and eliminating the need for manual data gathering from devices that cannot respond to user prompts.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

A server acts as an intermediary between non-functional devices and the error analysis system. The server receives error log data from devices, determines whether additional information is needed, generates appropriate communications, and manages the collection process. This intermediary handles the complexity of coordinating multiple communication channels and devices, shielding the core error analysis system from implementation complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If user input is requested from non-functional devices, then the utility of collected information is improved, but the feasibility of obtaining input deteriorates

Engineering Contradiction:
Improveutility of collected informationVSAvoidfeasibility of obtaining input
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

Instead of requesting user input directly from non-functional devices (which cannot respond), the system inverts the approach by sending communications to functional devices associated with those non-functional devices. Users interact with error reporting interfaces on their smartphones or other functional devices, providing input that is then associated with the original non-functional device's error logs.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The server acts as an intermediary that manages the association between non-functional devices and user input channels. It determines which functional devices are associated with non-functional devices, routes communications appropriately, and ensures that user input is correctly linked to the relevant error data, making the process feasible despite device limitations.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of information

If multiple communication channels are used to solicit user input, then the completeness of information collection is improved, but the device complexity increases

Engineering Contradiction:
Improvecompleteness of information collectionVSAvoidcommunication channel management complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The server implements multi-functionality by managing multiple communication channels (SMS, email, push notifications, in-app messages) through a single unified system. The same server infrastructure handles different communication types, determining the appropriate channel based on device capabilities and error context, rather than requiring separate systems for each communication method.

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

Solution Approach 2:

The system dynamically changes communication parameters based on device characteristics and error types. It selects which communication channel to use by evaluating device capabilities, user preferences, and error urgency, adapting the communication approach without requiring manual configuration for each scenario. This parameter-based selection simplifies management of multiple channels.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10540223B1System for determining error data
Publication Date: 2020.01.21 AMAZON TECH INC
  • US10540223B1 patent drawing
  • US10540223B1 patent drawing
  • US10540223B1 patent drawing

AI summary

Described are techniques for determining occurrence of an error associated with a user device and user interfaces to present to users responsive to the error to acquire additional information. Particular user interfaces that correspond to an error may be determined based on the characteristics of the error. Particular communication channels by which the user interfaces may be provided to a user may be determined based on the devices affected by the error, the characteristics of the user interfaces, and the characteristics of the receiving devices. User input received responsive to a user interface may be associated with a particular error or user device and used to determine an action to be performed responsive to the error.