A robot charging upgrade device, a robot, and a robot upgrade method

Abstract

The application discloses a robot charging upgrading device, a robot and a robot upgrading method, and provides the robot charging upgrading device, which comprises a first upgrading module, sends upgrading package request information carrying robot identification information to a server, and the server sends the upgrading package of the robot to the first upgrading module. When the power supply module identifies that the robot is in a charging state and the charging power is greater than a preset power threshold, the power supply module sends upgrading indication information carrying the robot identification information to the first upgrading module; the first upgrading module sends the corresponding upgrading package to the robot to instruct the robot to install the upgrading package for upgrading. The robot charging upgrading device provided by the application can automatically obtain the upgrading package of the robot, automatically upgrades the robot in the process of charging the robot, and compared with the manual upgrading scheme, improves the efficiency and convenience of the robot upgrading, and reduces the labor cost.

Description

Technical Field

[0001] This application relates to the field of robotics technology, and more particularly to a robot charging and upgrading device, a robot, and a robot upgrading method. Background Technology

[0002] With the rapid development of robotics technology, robots are quickly entering people's lives, helping them complete a wide variety of tasks. The completion of these tasks depends on the various software programs configured within the robot, and the software functions will differ for robots serving different industries.

[0003] Most robot software packages rely on the Robot Operating System (ROS) or the Intelligent Robot Operating System (IROS). Even after the robot itself is sold, its functionality still requires subsequent repair, updates, and maintenance.

[0004] In related technologies, robot function upgrades are generally performed by maintenance personnel. On the one hand, when the robot is running normally, maintenance personnel may easily overlook upgrade information, and significant omissions in updates could lead to robot malfunctions. On the other hand, in scenarios where multiple robots need to be deployed in widely dispersed locations, manual upgrades are inefficient, inconvenient, and costly in terms of manpower. Summary of the Invention

[0005] This application provides a robot charging and upgrading device, a robot, and a robot upgrading method to solve the problems of poor robot upgrading convenience and high labor costs in related technologies.

[0006] In a first aspect, this application provides a robot charging upgrade device, including: a power supply module and a first upgrade module;

[0007] The first upgrade module is used to send an upgrade package request information to the server, wherein the upgrade package request information carries the robot's identification information, and to receive the robot's upgrade package in response from the server based on the identification information;

[0008] The power supply module is used to send upgrade instruction information to the first upgrade module when it is detected that the robot is in a charging state and the robot's charging power is greater than a preset power threshold, and the upgrade instruction information carries the identification information.

[0009] The first upgrade module is used to send the upgrade package to the robot based on the identification information when it receives the upgrade instruction information, so as to instruct the robot to install the upgrade package for upgrade.

[0010] Secondly, this application provides a robot, including: a power receiving module and a second upgrade module;

[0011] The power receiving module is used to send a charging request message carrying the robot identification information to the robot charging and upgrading device, and to start charging after receiving the charging response from the robot charging and upgrading device.

[0012] The second upgrade module is used to receive an upgrade package from the robot charging upgrade device based on the identification information, and install the upgrade package to perform an upgrade; wherein the upgrade package is obtained by the robot charging upgrade device from the server and responds when it detects that the robot is in a charging state and the robot's charging power is greater than a preset power threshold.

[0013] Thirdly, this application provides a robot upgrade method, applied to robot charging upgrade equipment, comprising:

[0014] Send an upgrade package request to the server, the upgrade package request information carrying the robot's identification information, and receive the robot's upgrade package in response from the server based on the identification information;

[0015] When the robot is detected to be charging and its charge level is greater than a preset power threshold, the upgrade package is sent to the robot based on the identification information to instruct the robot to install the upgrade package for upgrading.

[0016] Fourthly, this application provides a robot upgrade method, applied to a robot, including:

[0017] Send a charging request message carrying the robot's identification information to the robot charging and upgrade device, and start charging after receiving a charging response from the robot charging and upgrade device;

[0018] The robot charging upgrade device receives an upgrade package based on the identification information and installs the upgrade package to perform an upgrade. The upgrade package is requested by the robot charging upgrade device from the server and is responded to when the robot is identified as being in a charging state and the robot's charging power is greater than a preset power threshold.

[0019] Fifthly, this application provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the robot upgrade method steps described above.

[0020] This application provides a robot charging and upgrading device, a robot, and a robot upgrading method. The above-mentioned technical solution has the following advantages or beneficial effects:

[0021] The robot charging and upgrade device provided in this application has the functions of charging the robot and providing the robot with an upgrade package. It includes a first upgrade module that communicates with a server. The first upgrade module sends an upgrade package request message carrying robot identification information to the server, and the server sends the robot's upgrade package to the first upgrade module. When the power supply module detects that the robot is in a charging state and the charging amount is greater than a preset power threshold, it sends an upgrade instruction message carrying robot identification information to the first upgrade module; the first upgrade module then sends the corresponding upgrade package to the robot, instructing the robot to install the upgrade package for upgrade. The robot charging and upgrade device provided in this application can automatically obtain the robot's upgrade package and automatically upgrade the robot during the charging process. Compared with manual upgrade methods, this improves the efficiency and convenience of robot upgrades and reduces labor costs. Attached Figure Description

[0022] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0023] Figure 1 A schematic diagram of the robot charging upgrade device provided in this application;

[0024] Figure 2 Topographical diagram of the upgrade server and robot charging upgrade equipment provided in this application;

[0025] Figure 3 This is a schematic diagram of the robot structure provided in this application;

[0026] Figure 4 A schematic diagram of the robot upgrade process provided in this application;

[0027] Figure 5 A schematic diagram of the robot upgrade process provided in this application;

[0028] Figure 6 This application provides a schematic diagram of a primary robot inspection process;

[0029] Figure 7 Another schematic diagram of a primary robot inspection provided in this application;

[0030] Figure 8 Obtain an upgraded version architecture diagram for the robot charging upgrade device provided in this application;

[0031] Figure 9 The robot upgrade and self-test architecture diagram provided in this application;

[0032] Figure 10 The first-level robot upgrade and licensing architecture diagram provided for this application;

[0033] Figure 11 The interaction architecture diagram of the first-level robot and the second-level robot provided in this application;

[0034] Figure 12 A schematic diagram illustrating the connection between the robot provided in this application and the robot charging and upgrading device for charging and upgrading;

[0035] Figure 13 The illustration shows the effect of charging and upgrading the robot provided in this application. Detailed Implementation

[0036] To make the objectives and implementation methods of this application clearer, the exemplary implementation methods of this application will be clearly and completely described below with reference to the accompanying drawings of the exemplary embodiments of this application. Obviously, the exemplary embodiments described are only some embodiments of this application, and not all embodiments.

[0037] It should be noted that the brief descriptions of terms in this application are only for the convenience of understanding the embodiments described below, and are not intended to limit the embodiments of this application. Unless otherwise stated, these terms should be understood in their ordinary and common meaning.

[0038] The terms "first," "second," "third," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar or related objects or entities, and do not necessarily imply a specific order or sequence, unless otherwise specified. It should be understood that such terms are interchangeable where appropriate.

[0039] The terms “comprising” and “having”, and any variations thereof, are intended to cover but not exclude inclusion, for example, a product or device that includes a range of components is not necessarily limited to all of the components that are clearly listed, but may include other components that are not clearly listed or that are inherent to such product or device.

[0040] The term "module" refers to any known or subsequently developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware and / or software code that is capable of performing the functions associated with that element.

[0041] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

[0042] For ease of explanation, the above description has been provided in conjunction with specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or to limit the embodiments to the specific forms disclosed above. Various modifications and variations can be obtained based on the above teachings. The selection and description of the above embodiments are for the purpose of better explaining the principles and practical applications, thereby enabling those skilled in the art to better utilize the described embodiments and various different variations of embodiments suitable for specific use considerations.

[0043] Figure 1 The schematic diagram of the robot charging and upgrade device provided in this application includes a power supply module 11 and a first upgrade module 12;

[0044] The first upgrade module 12 is used to send an upgrade package request information to the server, wherein the upgrade package request information carries the robot's identification information, and to receive the robot's upgrade package in response from the server based on the identification information;

[0045] The power supply module 11 is used to send upgrade instruction information to the first upgrade module 12 when it is detected that the robot is in a charging state and the robot's charging power is greater than a preset power threshold, and the upgrade instruction information carries the identification information.

[0046] The first upgrade module 12 is used to send the upgrade package to the robot based on the identification information when it receives the upgrade instruction information, so as to instruct the robot to install the upgrade package for upgrade.

[0047] The robot charging and upgrade equipment can be a charging pile device for charging robots. In this application, the functional module involved in charging the robot in the robot charging and upgrade equipment is referred to as the power supply module, and the functional module involved in upgrading the robot in the robot charging and upgrade equipment is referred to as the first upgrade module. The first upgrade module in the robot charging and upgrade equipment establishes communication with a server. The server refers to a server that manages robot upgrade packages. The first upgrade module sends upgrade package request information to the server, carrying the robot's identification information in the upgrade package request information. There is a correspondence between the robot's upgrade packages and the robot's identification information stored in the server. The robot's identification information can be a unique identifier such as the robot's serial number. Based on the robot's identification information, the robot's model, code, and other information can be determined. When storing robot upgrade packages, the server can store them in a one-to-one correspondence between upgrade packages and robot identification information. For robots of the same model with the same upgrade package, it can also store them in a one-to-many correspondence between upgrade packages and robot identification information. After receiving the upgrade package request information, the server can determine the upgrade package corresponding to the robot based on the robot's identification information carried in the upgrade package request information and the saved correspondence between the upgrade package and the robot's identification information. The server then sends the upgrade package corresponding to the robot to the first upgrade module in the robot charging and upgrade device.

[0048] The power supply module in the robot charging and upgrade equipment receives charging requests from the robot and then charges it. When the power supply module detects that the robot is charging and its charge level exceeds a preset power threshold, it sends an upgrade instruction message carrying the robot's identification information to the first upgrade module. The preset power threshold is, for example, 70% or 75%. Considering the significant power consumption of robot upgrades, sending the upgrade instruction message carrying the robot's identification information to the first upgrade module when the robot's charge level exceeds the preset power threshold ensures sufficient power for the robot during the upgrade process, guaranteeing its correctness. Upon receiving the upgrade instruction message, the first upgrade module sends the corresponding upgrade package to the robot based on the identification information, instructing the robot to install the upgrade package and perform the upgrade.

[0049] The robot charging and upgrade device provided in this application has the functions of charging the robot and providing the robot with an upgrade package. It includes a first upgrade module that communicates with a server. The first upgrade module sends an upgrade package request message carrying robot identification information to the server, and the server sends the robot's upgrade package to the first upgrade module. When the power supply module detects that the robot is in a charging state and the charging power is greater than a preset power threshold, it sends an upgrade instruction message carrying robot identification information to the first upgrade module; the first upgrade module then sends the corresponding upgrade package to the robot, instructing the target robot to install the upgrade package for upgrade. The robot charging and upgrade device provided in this application can automatically obtain the robot's upgrade package and automatically upgrade the robot during the charging process. Compared with manual upgrade methods, this improves the efficiency and convenience of robot upgrades and reduces labor costs.

[0050] Considering that among the robots being charged, some may be eligible for upgrades (i.e., they have a new upgrade package to install) while others may not be eligible for upgrades (i.e., they do not have a new upgrade package to install and do not need to be upgraded), to improve the accuracy and efficiency of robot upgrades, in this application, the first upgrade module is used to request the latest version identifier information and the current version identifier information of the robot from the server; if it is determined that the robot is in a state awaiting upgrade based on the latest version identifier information and the current version identifier information, an upgrade package request information is sent to the server.

[0051] In this application, the first upgrade module sends a latest version request message to the server, which includes the robot's identification information. The server then sends the robot's latest version identification information to the first upgrade module. The first upgrade module also sends a current version request message to the server, which includes the robot's identification information. The server then sends the robot's current version identification information to the first upgrade module.

[0052] Based on the robot's latest version identifier and current version identifier, it is determined whether the robot is in an upgrade-pending state. Optionally, if the robot's latest version identifier and current version identifier are the same, it means the robot does not need to be upgraded; if the robot's latest version identifier and current version identifier are different, it means the robot needs to be upgraded and is in an upgrade-pending state. The first upgrade module, upon determining that the robot is in an upgrade-pending state, sends an upgrade package request to the server, carrying the robot's identifier in the request, and receives the robot's upgrade package from the server based on the identifier. When the power supply module detects that the robot is charging and its charging power exceeds a preset power threshold, it sends an upgrade instruction to the first upgrade module, carrying the robot's identifier in the instruction. Upon receiving the upgrade instruction, the first upgrade module sends an upgrade package to the robot based on the identifier, instructing the robot to install the upgrade package for upgrading.

[0053] For robots that do not require upgrades, there is no need to send their identification information to the server. This improves the upgrade efficiency of robots awaiting upgrades and ensures the accuracy of the upgrades.

[0054] It should be noted that in robot charging scenarios, different servers can manage different information. For example, an upgrade server manages the robot's upgrade package information, an upgrade version server manages the robot's latest version identifier information, and a robot server manages the robot's current version identifier information.

[0055] At this time, the first upgrade module sends an upgrade package request message to the upgrade server, carrying the robot's identification information in the upgrade package request message, and receives the robot's upgrade package in response from the upgrade server based on the identification information; when the power supply module detects that the robot is in a charging state and the robot's charging power is greater than a preset power threshold, it sends an upgrade instruction message to the first upgrade module, carrying the robot's identification information in the upgrade instruction message; when the first upgrade module receives the upgrade instruction message, it sends the upgrade package to the robot based on the robot's identification information to instruct the robot to install the upgrade package for upgrade.

[0056] The first upgrade module communicates with both the upgrade version server and the robot server. The upgrade version server maintains the latest upgrade package version information for each robot, while the robot server maintains the current upgrade package version information for each robot. The first upgrade module sends a request message to the upgrade version server, carrying the robot's identification information. The upgrade version server then sends the first upgrade module the robot's latest version identification information. The first upgrade module also sends a request message to the robot server, carrying the robot's identification information. The robot server then sends the first upgrade module the robot's current version identification information.

[0057] In this application, the first upgrade module is used to send an upgrade package request to the server if, based on the robot's identification information and the identification information of each robot within the scope of responsibility of the robot charging upgrade device, it is determined that the robot is a robot within the scope of responsibility.

[0058] Figure 2 The topological diagrams of the server and robot charging upgrade equipment provided in this application are as follows: Figure 2 As shown, multiple robot charging and upgrade devices are deployed in the scenario. Each device has a specific service area, providing charging and upgrade services to the robots within its area of ​​responsibility. The first upgrade module obtains the identification information of the robot currently charging, as well as the individual identification information of each robot within the service area of ​​the charging and upgrade device. For ease of description, the identification information of the robot currently charging is referred to as the first identification information, and the individual identification information of each robot within the service area of ​​the charging and upgrade device is referred to as the second identification information. If the first identification information is present in any of the second identification information sets, meaning the robot currently charging is within the service area of ​​the charging and upgrade device, an upgrade package request is sent to the server, and the upgrade process begins. If the first identification information is not present in any of the second identification information sets, meaning the robot currently charging is not within the service area of ​​the charging and upgrade device, no upgrade package request is sent to the server, and the upgrade process does not proceed.

[0059] In this application, the first upgrade module is used to send a restart prompt message and a self-test program package to the robot if it is determined that the upgrade package has restart and self-test requirements, so as to instruct the robot to restart after installing the upgrade package, and to perform a self-test based on the self-test program package after restarting.

[0060] For upgrade packages that require restarting and self-checking, the first upgrade module sends a restart prompt and a self-check package to the robot. Upon receiving the restart prompt, the robot automatically restarts after installing the upgrade package and performs a self-check based on the self-check package. The restart has two outcomes: successful or failed. Similarly, the self-check has two outcomes: successful or failed. A successful restart and self-check indicate a successful robot upgrade; otherwise, the upgrade is considered a failure. The robot sends the upgrade success or failure information to the server, which records the robot's upgrade status.

[0061] To improve the efficiency of robot upgrades, in this application, the first upgrade module is configured to, if there is a candidate robot of the same model as the robot that has not been upgraded within the scope of the robot charging and upgrade equipment, modify the status of the robot to an upgrade authorization status and send the identification information of the candidate robot to the robot, so as to instruct the robot to send the upgrade package to the candidate robot.

[0062] This application uses the above-mentioned setup to designate the charging robot as the primary robot and the un-upgraded candidate robot of the same model as the secondary robot. The primary robot has the ability to provide upgrade packages to the secondary robot, thereby realizing a scheme in which the primary robot and the robot charging and upgrade equipment provide upgrade packages to the un-upgraded robot in parallel, thus improving the robot upgrade efficiency.

[0063] Figure 3 The schematic diagram of the robot structure provided in this application includes a power receiving module 21 and a second upgrade module 22;

[0064] The power receiving module 21 is used to send a charging request message carrying the robot identification information to the robot charging upgrade device, and start charging after receiving the charging response from the robot charging upgrade device;

[0065] The second upgrade module 22 is used to receive an upgrade package from the robot charging upgrade device based on the identification information, and install the upgrade package to perform an upgrade; wherein the upgrade package is obtained by the robot charging upgrade device from the server and responds when it detects that the robot is in a charging state and the robot's charging power is greater than a preset power threshold.

[0066] It should be noted that the power receiving module and the second upgrade module in this application can be installed at any location on the robot, and this application does not impose any specific limitations.

[0067] It is understood that the power receiving module and the second upgrade module do not constitute a specific limitation on the robot. The robot in this application may include more components than just the power receiving module and the second upgrade module. For example, it may include camera components, motion components, audio components, etc.

[0068] This application refers to the charging-related functional module in the robot as the power receiving module, and the upgrading-related functional module in the robot as the second upgrading module. The power receiving module in the robot sends a charging request message carrying the robot's identification information to the robot charging and upgrading device. The robot charging and upgrading device returns a charging response according to the charging protocol, and then the robot charging and upgrading device begins charging the robot.

[0069] The robot charging and upgrade device requests an upgrade package for the robot from the server. When it detects that the robot is in a charging state and the robot's charging power is greater than a preset power threshold, it sends the upgrade package to the second upgrade module in the robot. The second upgrade module receives the upgrade package in response from the robot charging and upgrade device and installs the upgrade package to perform the upgrade.

[0070] In one optional embodiment, the second upgrade module receives an indication from the robot charging and upgrade device that the robot is a robot to be upgraded; sends an upgrade package request to the robot charging and upgrade device, receives the upgrade package from the robot charging and upgrade device, and installs the upgrade package to perform the upgrade. If the robot is not a robot to be upgraded, there is no need to send an upgrade package.

[0071] In one optional embodiment, the second upgrade module is configured to receive a restart prompt message and a self-test package sent by the robot charging upgrade device; after installing the upgrade package, the robot restarts, and performs a self-test based on the self-test package after restarting.

[0072] For upgrade packages that require restarting and self-checking, the first upgrade module sends a restart prompt and a self-check package to the robot. Upon receiving the restart prompt, the robot automatically restarts after installing the upgrade package and performs a self-check based on the self-check package. The restart has two outcomes: successful or failed. Similarly, the self-check has two outcomes: successful or failed. A successful restart and self-check indicate a successful robot upgrade; otherwise, the upgrade is considered a failure. The robot sends the upgrade success or failure information to the server, which records the robot's upgrade status.

[0073] In one optional embodiment, the second upgrade module is configured to receive authorization status indication information sent by the robot charging and upgrade device, modify its own status to upgrade authorization status; receive identification information of a candidate robot of the same model as the robot and which has not been upgraded, sent by the robot charging and upgrade device, and send the upgrade package to the candidate robot according to the identification information to instruct the candidate robot to install the upgrade package for upgrade.

[0074] This application enables a scheme whereby the robot and the robot charging and upgrade equipment provide upgrade packages to the un-upgraded robot in parallel, thereby improving the robot upgrade efficiency.

[0075] Figure 4 The robot upgrade process diagram provided for this application includes the following steps:

[0076] S101: Send an upgrade package request message to the server, the upgrade package request message carrying the robot's identification information, and receive the robot's upgrade package in response from the server based on the identification information.

[0077] S102: When it is detected that the robot is in a charging state and the robot's charging power is greater than a preset power threshold, the upgrade package is sent to the robot based on the identification information to instruct the robot to install the upgrade package for upgrading.

[0078] The robot upgrade method provided in this application is applied to robot charging upgrade equipment.

[0079] Figure 5 The robot upgrade process diagram provided for this application includes the following steps:

[0080] S201: Send a charging request message carrying the robot identification information to the robot charging and upgrading device, and start charging after receiving the charging response from the robot charging and upgrading device.

[0081] S202: Receive the upgrade package from the robot charging upgrade device based on the identification information, and install the upgrade package to perform the upgrade; wherein, the upgrade package is obtained by the robot charging upgrade device from the server and is responded to when it is detected that the robot is in a charging state and the robot's charging power is greater than a preset power threshold.

[0082] The robot upgrade method provided in this application is applied to robots.

[0083] The robot upgrade process provided in this application will be described in detail below with reference to the accompanying drawings.

[0084] Robots are expensive, so a strategy for upgrading them can be to first upgrade on a small scale for verification, and then upgrade comprehensively. Taking a major update as an example, to ensure the upgrade scope is controllable, the upgrade server adopts a local upgrade strategy. The upgrade server can set the scope of robot charging and upgrade devices and specify the robot update list. When a robot charging and upgrade device requests upgrade information, the upgrade server transmits the necessary upgrade information to the device. The device then performs upgrades, self-checks, and other operations on each robot within that area, maintaining a robot list. After a successful upgrade or periodically, it reports the robot list information to the upgrade server, which then performs statistical analysis of the upgrade results to ensure a smooth upgrade process. The robot charging and upgrade device maintains a list of required robot module versions, upgradable hardware, and software models, acting as a secondary server within its local area for even smaller-scale upgrades. The upgrade server maintains the robot charging and upgrade device and robot list information.

[0085] The information on the robot charging upgrade equipment maintenance list includes: the unique identification code of the charging pile, the area covered by the charging pile, and the number of robots in the area covered.

[0086] The robot charging upgrade equipment maintenance robot upgrade list information includes: unique identification code of charging pile, unique identification code of robot, robot model, robot software version number, robot hardware version number, robot upper limb arm version number, robot upper limb algorithm version number, robot lower limb motion algorithm version number, and robot operating system dual system version number.

[0087] The robot charging upgrade equipment maintenance robot upgrade success and failure list information includes: charging pile unique identification code, robot unique identification code, upgrade success / failure, self-test success / failure, and startup success / failure.

[0088] The information for upgrading and maintaining the charging pile list includes: the unique identification code of the charging pile, the area covered by the charging pile, whether it overlaps with the area covered by other charging piles, and the number of robots in the area it is responsible for.

[0089] The information for upgrading the server and maintaining the robot list includes: the robot's unique identifier, the robot's model, the robot's software version number, the robot's hardware version number, the robot's upper limb arm version number, the robot's upper limb algorithm version number, the robot's lower limb motion algorithm version number, the number of charging stations the robot can use, and the robot's dual-system operating system version number.

[0090] The upgrade list information for the server maintenance robot includes: unique identification code of charging pile, number of successful robot upgrades, robot upgrade failures, successful robot self-test, failed robot self-test, successful robot startup, and failed robot startup.

[0091] The list of robots whose upgrades failed includes: the unique identifier of the charging station and the unique identifier of the robot whose upgrade was unsuccessful.

[0092] The process for obtaining the upgrade version of the robot charging upgrade equipment is as follows:

[0093] If it's an upgrade for a specific region or a specific robot, the upgrade server will send an upgrade message (including robot model, upgrade model, etc.) to the designated robot charging and upgrade devices in that region. Only the designated robot charging and upgrade devices will receive this message. The robot charging and upgrade devices will then download the upgrade package from the specified robot list and complete the upgrade process.

[0094] The robot charging upgrade equipment communicates with the upgrade server periodically to determine if an upgrade version is available.

[0095] The upgrade server will search for a list of version information suitable for robot upgrades in the area and send it back to the robot charging and upgrade equipment.

[0096] The robot charging and upgrade equipment obtains the list of robots that need maintenance in the area based on the robot list information it maintains and the robot server information.

[0097] The robot charging and upgrade equipment searches the robot list for version information that can be used to upgrade robots in that area, and then requests the upgrade version to be downloaded from the upgrade server.

[0098] The robot upgrade process is as follows:

[0099] When the robot is charging, it will report its model, code, version and other information to the robot charging and upgrade equipment.

[0100] The robot charging and upgrade equipment checks the robot upgrade list to determine whether the robot needs to be upgraded.

[0101] After the robot finishes charging or reaches a certain power threshold, it receives an upgrade message and requests information to download the upgrade package.

[0102] After receiving the upgrade package, the robot will verify it and complete the version upgrade.

[0103] The robot requests a power upgrade from the robot charging equipment, asking whether a restart is required for this upgrade.

[0104] The robot charging upgrade equipment checks the version and upgrade requirements, and then issues a restart command.

[0105] The robot restarts, and after restarting, it requests a self-test version list from the robot charging and upgrade equipment.

[0106] After receiving the self-test version list, the robot performs a self-test and reports the results to the robot's charging and upgrade equipment.

[0107] The robot charging and upgrade equipment maintains a list of robot information, including whether the upgrade was successful and whether the self-test was successful. The robot charging and upgrade equipment then deactivates the robot from upgrade mode. The robot is now ready to work.

[0108] The robot charging and upgrade equipment periodically uploads reports of robot information lists to the upgrade server.

[0109] Considering the tight upgrade schedules and the wide coverage of robot charging stations, using specific charging stations may not be able to complete the upgrades for all robots within a certain timeframe. Therefore, a collaborative upgrade method among robots was developed. Robots that successfully upgrade via charging stations are designated as Level 1 robots. Robots that fail to upgrade are designated as Level 2 robots.

[0110] After the Level 1 robot upgrade is completed, it will interact with the charging station upgrade equipment to inquire whether all robots of the same model in the area have been upgraded. If not, the robot retains the corresponding upgrade package and self-test list. The charging station upgrade equipment will then provide the robot's model and serial number information and authorize the upgrade. The Level 1 robot will then upgrade the Level 2 robot via Bluetooth, network, or other communication methods.

[0111] After a Level 1 robot has the upgrade authorization function, it needs to perform area inspection function to upgrade the robots in the area that have not been upgraded.

[0112] The Level 1 robot contacts the Level 2 robot, confirming the model number, serial number, and other information to verify communication. After confirmation, the Level 1 robot transmits the upgrade package and self-test information via Bluetooth or network.

[0113] After downloading the upgrade package, the Level 2 robot will install the upgrade, perform a self-test according to the self-test checklist, and report the upgrade installation and self-test status to the Level 1 robot.

[0114] Based on the received upgrade success feedback, the Level 1 robot continues the above steps until all Level 2 robots in the area have been upgraded or are unable to be upgraded.

[0115] The Level 1 robot returns to the robot charging and upgrade equipment to submit an upgrade report and uploads the upgrade status list to the robot charging and upgrade equipment. The robot charging and upgrade equipment then reports the upgrade status to the upgrade server. Once the upgrade is confirmed to be complete, the Level 1 robot's upgrade authorization function is revoked.

[0116] The Level 1 robot deletes the upgrade package, self-test list, and Level 2 robot upgrade status list, and returns to normal working mode.

[0117] If the upgrade server does not receive notification of robot completion within the specified statistical time, on-site manual upgrade is required.

[0118] Figure 6 This application provides a schematic diagram of a primary robot inspection system. Figure 7 This is another schematic diagram of a first-level robot inspection provided in this application.

[0119] Figure 8 To obtain the upgraded version architecture diagram of the robot charging upgrade device provided in this application, such as... Figure 8 As shown, the robot charging and upgrade device requests a new version from the upgrade server; the upgrade server obtains the updated version information from the upgrade version server; the upgrade version server saves the updated version information to the upgrade cache; the upgrade cache sends the version information back to the upgrade server; the upgrade server sends the upgrade version information back to the robot charging and upgrade device; the robot charging and upgrade device requests robot version list information from the robot server; the robot server sends the robot version list information back to the robot charging and upgrade device; when the robot charging and upgrade device determines that an upgrade is needed, it requests an upgrade package from the upgrade server; the upgrade server sends the upgrade package to the robot charging and upgrade device. Optionally, the upgrade package can also be stored on the upgrade version server, and when the robot charging and upgrade device determines that an upgrade is needed, it requests the upgrade package from the upgrade version server; the upgrade version server sends the upgrade package to the robot charging and upgrade device.

[0120] Figure 9 The robot upgrade and self-test architecture diagram provided for this application is as follows: Figure 9As shown, the robot requests charging from the robot charging and upgrade device and reports robot information; the robot charging and upgrade device determines whether the robot needs an upgrade and provides feedback to the robot; if an upgrade is needed, the robot requests an upgrade package from the robot charging and upgrade device; the robot charging and upgrade device sends the upgrade package to the robot; the robot installs the upgrade package; the robot requests whether the version needs to be restarted from the robot charging and upgrade device; the robot charging and upgrade device determines whether the robot needs to be restarted after the upgrade; the robot charging and upgrade device provides feedback to the robot regarding whether a restart is needed; if a restart is needed, the robot adjusts to the restart state and restarts; the robot reports a successful restart to the robot charging and upgrade device; the robot charging and upgrade device sends self-test information to the robot; the robot performs a self-test and reports success or failure information to the robot charging and upgrade device; the robot charging and upgrade device updates the locally maintained robot list information and reports it to the robot server; the robot server provides feedback to the robot charging and upgrade device that the process is complete; the robot charging and upgrade device changes the robot status to a working state.

[0121] Figure 10 The Level 1 robot upgrade and licensing architecture diagram provided for this application is as follows: Figure 10 As shown, the first-level robot requests charging from the robot charging and upgrade device and reports robot information; the robot charging and upgrade device determines whether the first-level robot needs an upgrade and provides feedback to the first-level robot; if an upgrade is needed, the first-level robot requests the upgrade package from the robot charging and upgrade device; the robot charging and upgrade device sends the upgrade package to the first-level robot; the first-level robot installs the upgrade package; the first-level robot requests the robot charging and upgrade device whether this version requires a restart; the robot charging and upgrade device determines whether the first-level robot needs a restart after the upgrade; the robot charging and upgrade device provides feedback to the first-level robot regarding whether a restart is needed; if a restart is needed, the first-level robot adjusts to the restart state and restarts; the first-level robot will... The system performs the following steps: Successful restart is reported to the robot charging and upgrade device; the device sends self-test information to the primary robot; the primary robot performs a self-test and reports success or failure to the charging and upgrade device; the device updates its locally maintained robot list and reports it to the robot server; the robot server reports completion to the charging and upgrade device; the device determines if there are any un-upgraded secondary robots within its area of ​​responsibility; the device changes the primary robot's status to "upgradeable"; the primary robot requests an upgradeable list of secondary robots from the charging and upgrade device; and the charging and upgrade device sends the upgradeable list of secondary robots to the primary robot.

[0122] Figure 11The interaction architecture diagram of the first-level robot and the second-level robot provided in this application is as follows: Figure 11 As shown, the first-level robot begins area inspection and requests model and serial number information from the second-level robot; the second-level robot responds with the same information; the first-level robot checks if the second-level robot can be upgraded; if an upgrade is needed, the second-level robot enters an upgradeable state and requests an upgrade package from the first-level robot; the first-level robot sends the upgrade package to the second-level robot; the second-level robot installs the upgrade package; the second-level robot requests self-test information from the first-level robot; the first-level robot sends a self-test list to the second-level robot; the second-level robot restarts and performs a self-test; the second-level robot sends self-test and upgrade information to the first-level robot; the second-level robot is set to working mode; the second-level robot deletes the upgrade package and sets its working mode; the second-level robot sends a setup success message to the first-level robot; the first-level robot's area inspection ends; the first-level robot reports the second-level robot's upgrade information to the robot charging and upgrade device; the robot charging and upgrade device sends a deauthorization instruction to the first-level robot; the first-level robot deletes its local robot list information, deletes the upgrade package, and resets to working mode.

[0123] The robot upgrade solution provided in this application can automatically acquire robot upgrade packages, automatically upgrade the robot during the charging process, and achieve collaborative upgrades between robots. Compared with manual upgrade solutions, it improves the efficiency and convenience of robot upgrades and reduces labor costs.

[0124] Figure 12 This is a schematic diagram illustrating the connection between the robot and the robot charging and upgrading device provided in this application for charging and upgrading. The robot's power receiving module is connected to the power supply module of the robot charging and upgrading device, and the robot's second upgrading module is connected to the first upgrading module of the robot charging and upgrading device. Figure 13 The illustration shows the effect of charging and upgrading the robot provided in this application.

[0125] This application also provides a computer-readable storage medium storing a computer program executable by an electronic device, which, when run on the electronic device, causes the electronic device to perform any of the above method steps.

[0126] Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.

[0127] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A robotic charging upgrade apparatus, comprising: The method comprises the steps of: The power supply module and the first upgrade module; The first upgrade module is configured to send an upgrade package request information to a server, wherein the upgrade package request information carries identification information of a robot, and receive an upgrade package of the robot in response to the identification information from the server; The power supply module is configured to send an upgrade instruction information to the first upgrade module when it is identified that the robot is in a charging state and the charging power of the robot is greater than a preset power threshold, wherein the upgrade instruction information carries the identification information; The first upgrade module is configured to send the upgrade package to the robot based on the identification information to instruct the robot to install the upgrade package for upgrading when the upgrade instruction information is received; The first upgrade module is configured to modify a state of the robot that has successfully upgraded to an upgrade authorized state and send identification information of a candidate robot that has not been upgraded to the robot that has successfully upgraded to instruct the robot that has successfully upgraded to send the upgrade package to the candidate robot if the candidate robot that has not been upgraded is of the same type as the robot that has successfully upgraded and exists within a responsible range of the robot charging and upgrading device; The robot that has successfully upgraded and the robot charging and upgrading device provide the upgrade package to the robot that has not been upgraded in parallel.

2. The robotic charging upgrade device of claim 1, wherein, The first upgrade module is configured to request the latest version identification information of the robot and the current version identification information of the robot from the server, and send the upgrade package request information to the server if it is determined that the robot is in a state to be upgraded according to the latest version identification information and the current version identification information of the robot.

3. The robotic charging upgrade apparatus of claim 1 or 2, wherein, The first upgrade module is configured to send the upgrade package request information to the server if it is determined that the robot is a robot within the responsible range according to the identification information of the robot and the identification information of each robot within the responsible range of the robot charging and upgrading device.

4. The robotic charging upgrade device of claim 1, wherein, The first upgrade module is configured to send a restart prompt information and a self-check program package to the robot to instruct the robot to restart after installing the upgrade package and perform self-checking based on the self-check program package after restarting if it is determined that the upgrade package has a restart and self-checking requirement.

5. A robot, characterized in that The method comprises the steps of: The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power supply module and the first upgrade module; The power The second upgrade module is configured to receive authorization state indication information sent by the robot charging upgrade device, modify the state of the robot to an upgrade authorization state, receive identification information of a candidate robot of the same type as the upgrade authorization state robot and not upgraded sent by the robot charging upgrade device, and send the upgrade package to the candidate robot according to the identification information, to instruct the candidate robot to install the upgrade package for upgrading. The upgrade authorization state robot and the robot charging upgrade device provide the upgrade package to the robot not upgraded in parallel.

6. The robot of claim 5, wherein, The second upgrade module is configured to receive restart prompt information and a self-check program package sent by the robot charging upgrade device, restart after the upgrade package is installed, and perform self-checking based on the self-check program package after restarting.

7. A method of upgrading a robot, c h a r a c t e r i s e d by, The method is applied to a robot charging upgrade device, and the robot charging upgrade device comprises a power supply module and a first upgrade module. The first upgrade module is configured to send upgrade package request information to a server, carry identification information of a robot in the upgrade package request information, and receive an upgrade package of the robot responded by the server based on the identification information. The power supply module is configured to, when it is identified that the robot is in a charging state and the charging power of the robot is greater than a preset power threshold, send the upgrade package to the robot based on the identification information, to instruct the robot to install the upgrade package for upgrading. The first upgrade module is configured to, if there is a candidate robot of the same type as the robot of which upgrading is successful and not upgraded in a range responsible by the robot charging upgrade device, modify the state of the robot of which upgrading is successful to an upgrade authorization state, and send identification information of the candidate robot to the robot of which upgrading is successful, to instruct the robot of which upgrading is successful to send the upgrade package to the candidate robot. The robot of which upgrading is successful and the robot charging upgrade device provide the upgrade package to the robot not upgraded in parallel.

8. A method of upgrading a robot, characterized by, The method is applied to a robot, and the robot comprises a power receiving module and a second upgrade module. The power receiving module is configured to send charging request information carrying identification information of the robot to a robot charging upgrade device, and start charging after receiving a charging response of the robot charging upgrade device. The second upgrade module is configured to receive an upgrade package responded by the robot charging upgrade device based on the identification information, and install the upgrade package for upgrading. The second upgrade module is configured to receive authorization state indication information sent by the robot charging upgrade device, modify the state of the robot to an upgrade authorization state, receive identification information of a candidate robot of the same type as the upgrade authorization state robot and not upgraded sent by the robot charging upgrade device, and send the upgrade package to the candidate robot according to the identification information, to instruct the candidate robot to install the upgrade package for upgrading. The upgrade authorization state machine robot and the robot charging upgrade device provide an upgrade package to the non-upgraded robot in parallel.

Images