Decentralized Software Upgrade for Autonomous Mobile Robots
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current software upgrade methods for autonomous mobile robots rely on a central control server, which limits decentralization and efficiency in updating software across multiple robots in different domains.
Innovation Solution
A decentralized software upgrade system that uses a data distribution service domain with version synchronization and software update topics, allowing autonomous mobile robots to publish and subscribe to version information, initiate updates, and upload or download software without a central server, enabling peer-to-peer communication and logical equality among nodes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If a central control server is used to manage software upgrades, then centralized control and coordination are achieved, but system complexity increases and decentralization is limited
Solution Approach 1:
The patent extracts the central control server from the software upgrade system, removing the centralized management component. Each autonomous mobile robot is equipped with independent software upgrade functionality, including version comparison modules and update execution modules, enabling them to perform upgrades autonomously without relying on centralized control.
Solution Approach 2:
Each autonomous mobile robot is designed to self-manage its software upgrades. The robots publish their version information to topics, subscribe to upgrade notifications, compare versions, and execute updates independently. This self-service mechanism eliminates the need for a central control server while maintaining coordinated upgrades across the fleet.
2Productivity
If a central control server manages software distribution, then unified version control is achieved, but update efficiency and speed are reduced
Solution Approach 1:
The patent implements a mechanism where software packages are pre-uploaded to a distributed file system before being needed. When a robot requires an update, the software is already available in the distributed network, eliminating download wait times. The version comparison and update preparation are also performed in advance through continuous topic subscription and version checking.
Solution Approach 2:
The software upgrade system transitions from static centralized distribution to dynamic peer-to-peer distribution. Robots dynamically publish their version status, dynamically subscribe to upgrade topics, and dynamically exchange software packages based on real-time needs. This dynamic behavior enables parallel updates across multiple robots simultaneously, significantly improving update efficiency.
3Adaptability or versatility
If decentralized peer-to-peer communication is implemented, then system flexibility and adaptability improve, but ensuring consistent version synchronization becomes more difficult
Solution Approach 1:
The patent implements continuous feedback mechanisms through topic-based publishing and subscribing. Each robot publishes its version information to a version topic and subscribes to upgrade notification topics. The system continuously monitors version consistency across the network, with robots comparing their local versions against published versions and automatically initiating updates when inconsistencies are detected, ensuring reliable synchronization in a decentralized environment.
Solution Approach 2:
The patent creates a universal communication interface using standardized topics for version publishing, upgrade notifications, and software exchange. This universal topic-based approach allows robots across different domains to communicate and synchronize versions consistently, regardless of their specific domain or implementation details, enabling both flexibility and reliability.
Data Source
AI summary
The present disclosure provides a software upgrade system, which is applicable to at least one autonomous mobile robot installed with software in a data distribution service domain. The at least one autonomous mobile robot publishes a version information about the software to the version synchronization topic and receives other version information from the version synchronization topic. Also, the at least one autonomous mobile robot subscribes to a version synchronization topic, and takes the software of the at least one autonomous mobile robot itself as the latest version by a software update procedure to upload to a software update topic, or downloads the latest version of the software from the software update topic and installs it. The present disclosure provides a software upgrade method and a non-transitory recording medium.