OTA Switchboard for Headless Device Software Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Network connected devices, such as those in vehicles, often lack a graphical user interface and feedback mechanism for software updates, making it difficult to initiate updates safely and correctly, especially in scenarios where timing is critical, like during vehicle operation or at service stations.
Innovation Solution
A method and system using an intermediary server, referred to as an over-the-air (OTA) switchboard, allows updates to be initiated and monitored through an electronic device, ensuring that updates are only performed when conditions are met and the correct device is selected, even if the device and electronic device are on different private networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If software updates are pushed to network connected devices without a graphical user interface, then device functionality can be improved, but safety and reliability of the update process deteriorates
Solution Approach 1:
The patent introduces an intermediary system comprising a server and mobile device that mediates between the user and the network connected device. This intermediary provides a graphical user interface on the mobile device for initiating updates, displays update status, and manages the update process, while the actual target device remains headless. This resolves the contradiction by providing UI capabilities through an external intermediary rather than requiring the target device to have its own interface.
2Speed
If updates are automatically pushed to network connected devices, then update speed increases, but the risk of updating at inappropriate times increases
Solution Approach 1:
The system implements feedback mechanisms where the intermediary mobile device provides real-time status information about the update process to the user through its graphical interface. The system waits for user confirmation and monitors update progress, allowing users to see when updates are in progress and when devices are ready for updates. This feedback loop prevents automated updates from occurring at inappropriate times by requiring user awareness and consent.
Solution Approach 2:
The system performs preliminary actions by having the user initiate the update process through the mobile device interface before the actual update is pushed to the target device. The user can review device information, update details, and confirm readiness before the update begins. This preliminary user action ensures that updates are only deployed when appropriate conditions are met.
3Device complexity
If network connected devices lack a graphical user interface for updates, then device simplicity is maintained, but user control and monitoring capability deteriorates
Solution Approach 1:
The patent uses an intermediary mobile device as a remote control and monitoring interface for the headless network connected device. The mobile device displays device information, update status, and provides controls for initiating and managing updates. This allows users to easily operate and monitor updates without adding any interface complexity to the target device itself, resolving the contradiction by externalizing the interface requirements.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method at a device to be updated, the method comprising: receiving, at the device to be updated, a software update download; receiving, using a user interface at the device to be updated, a physical authentication interaction to allow the device to enter an updated state; sending to a computing device acting as a switchboard a connection request to connect the device to the computing device and information indicating that update conditions have been met; receiving, from the computing device, instructions to install the software update download; and in response to the instructions, initiating an installation process to install the software update download.