US 11,928,456 B2
Software upgrade system, software upgrade method and non-transitory recording medium
Chen-Ying Kuo, Taoyuan (TW); Cheng-Ting Chang, Taoyuan (TW); and Yi-Chen Liu, Taoyuan (TW)
Assigned to ADLINK TECHNOLOGY INC., Taoyuan (TW)
Filed by ADLINK TECHNOLOGY INC., Taoyuan (TW)
Filed on Mar. 16, 2022, as Appl. No. 17/695,849.
Claims priority of application No. 110149650 (TW), filed on Dec. 30, 2021.
Prior Publication US 2023/0214204 A1, Jul. 6, 2023
Int. Cl. G06F 9/44 (2018.01); G06F 8/61 (2018.01); G06F 8/65 (2018.01)
CPC G06F 8/65 (2013.01) [G06F 8/61 (2013.01)] 2 Claims
OG exemplary drawing
 
1. A software upgrade method, which is applicable to at least one autonomous mobile robot installed with software in a data distribution service domain, the software upgrade method comprising the following steps:
allowing the at least one autonomous mobile robot to publish a first version information about the software in the data distribution service domain to a version synchronization topic, and receiving a second version information from the version synchronization topic;
subscribing to the version synchronization topic by a software update module of the at least one autonomous mobile robot, when detecting that the at least one autonomous mobile robot itself is inconsistent with the second version information of the version synchronization topic, a software update procedure is started;
when starting the software update procedure and determining that the first version information of the software of the at least one autonomous mobile robot itself is the latest version compared to the second version information by a software update topic publisher of the at least one autonomous mobile robot, uploading the software to a software update topic; and
when determining that the first version information of the software of the at least one autonomous mobile robot itself is not the latest version by the software update topic subscriber, downloading the latest version of the software from the software update topic and installing it in the at least one autonomous mobile robot,
wherein the first version information and the second version information comprise an identification number and a software version of the at least one autonomous mobile robot, respectively, and
wherein when starting the software update procedure, if it is determined that the software version of the at least one autonomous mobile robot itself and any of software versions of the second version information are the latest version, it is determined whether to take the software of the at least one autonomous mobile robot itself as the latest version and uploaded to the software update topic according to the sequence of the identification number of the at least one autonomous mobile robot.