Version management method and device, electronic device, and storage medium
By judging the compatibility and dependency of the robot system, the normal use problem caused by dependencies in the robot system upgrade is solved, ensuring the stable operation of the upgraded robot system.
Patent Information
- Application Number
- CN202011529631.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-12-22
- Publication Date
- 2024-11-29
- Estimated Expiration
- 2040-12-22
AI Technical Summary
During the upgrade of the robot system version, the existing technology failed to effectively consider the dependencies between different application software, resulting in the problem that the robot cannot be used normally after the upgrade.
By determining the target application software, obtaining the current version information and hardware information of the robot, determining whether it is compatible with the latest version, and processing dependencies based on the preset dependency table, ensuring that the robot is compatible at the software and hardware level and deploying the latest version.
The latest version of the target application software has been implemented to ensure that the robot can install and use the latest version of the application software normally, avoiding the problem of using it after upgrading.
Smart Images

Figure CN112463208B_ABST
Abstract
Description
[Technical field]
[0001] The present application relates to the field of robotics technology, and in particular to a version management method and device, electronic equipment, and storage medium. [Background technology]
[0002] With the continuous development of robot technology, robots have been widely used in all walks of life. In order to enable robots to provide better services, there is an increasing demand for updating and upgrading the robot system version. The robot system can be disassembled into application software with different functions according to different business functions. Different application software will inevitably have upper and lower layer dependencies. When updating and upgrading the robot system, it is usually followed to focus on only one application software and improve it as much as possible, so that multiple application software in the robot system can work together.
[0003] In the prior art, when deploying and managing the version upgrade of application software, the dependencies between different applications are not taken into consideration, which may easily lead to an embarrassing situation in which the robot cannot be used normally after installing the latest version of the application software. [Summary of the invention]
[0004] In view of the above problems, the present application is proposed to provide a version management method and device, electronic device, and storage medium that overcome the above problems or at least partially solve the above problems.
[0005] The present application provides a version management method, the method comprising:
[0006] When the preset application software upgrade trigger condition is met, the target application software is determined;
[0007] Get the current version information and hardware information of the robot's current application software;
[0008] Determining whether the robot is compatible with the latest version of the target application software based on the current version information of the current application software and the hardware information;
[0009] If so, the latest version of the target application software is deployed to the robot.
[0010] Optionally, the step of obtaining the current version information of the current application software and the hardware information of the robot includes:
[0011] Receive login information sent by the robot;
[0012] The current version information of the current application software and the hardware information of the robot are obtained from the login information.
[0013] Optionally, the method further comprises:
[0014] Obtaining a preset dependency table, wherein the preset dependency table is used to record dependency information of each application software in the robot system;
[0015] Determining whether the target application software has dependent application software according to the preset dependency table;
[0016] If so, a compatible version of the dependent application software that is compatible with the latest version of the target application software is obtained.
[0017] Optionally, the current application software includes the dependent application software, and the step of determining whether the robot is compatible with the latest version of the target application software based on the current version information and hardware information of the current application software includes:
[0018] Determining whether the current version of the dependent application software belongs to the compatible version;
[0019] If so, it is determined whether the hardware of the robot is compatible with the latest version of the target application software based on the hardware information.
[0020] Optionally, the current application software includes target application software; and the step of deploying the latest version of the target application software to the robot further includes:
[0021] Determining whether the current version of the target application software is the latest version;
[0022] If not, the latest version of the target application software is deployed to the robot.
[0023] Optionally, the step of deploying the latest version of the target application software to the robot includes:
[0024] Sending an upgrade notification to the robot to upgrade the target application software to the latest version; or,
[0025] Send the upgrade package corresponding to the latest version of the target application software to the robot.
[0026] Optionally, when a preset application software upgrade trigger condition is reached, the step of determining the target application software includes:
[0027] When new version release information is received, determining the target application software according to the new version release information;
[0028] Alternatively, when an upgrade request sent by the robot is received, the target application software is determined according to the upgrade request.
[0029] The present application also provides a version management device, the device comprising:
[0030] A first determination module is used to determine the target application software when a preset application software upgrade trigger condition is met;
[0031] The first acquisition module is used to acquire the current version information and hardware information of the current application software of the robot;
[0032] A first judgment module, used for judging whether the robot is compatible with the latest version of the target application software according to the current version information of the current application software and the hardware information;
[0033] The upgrade deployment module is used to deploy the latest version of the target application software to the robot when the robot is compatible with the latest version of the target application software.
[0034] Optionally, the first acquisition module includes:
[0035] The information receiving module is used to receive the login information sent by the robot;
[0036] The parsing and obtaining module is used to obtain the current version information of the current application software and the hardware information of the robot from the login information.
[0037] Optionally, the device further comprises:
[0038] A second acquisition module is used to acquire a preset dependency table, where the preset dependency table is used to record dependency information of each application software in the robot system;
[0039] A second judgment module is used to determine whether the target application software has dependent application software according to the preset dependency table;
[0040] The third acquisition module is used to acquire a compatible version of the dependent application software that is compatible with the latest version of the target application software when the target application software has dependent application software.
[0041] Optionally, the current application software includes the dependent application software, and the first determination module includes:
[0042] A software determination submodule, used to determine whether the current version of the dependent application software belongs to the compatible version;
[0043] The hardware judgment submodule is used to judge whether the hardware of the robot is compatible with the latest version of the target application software according to the hardware information when the current version of the dependent application software belongs to the compatible version.
[0044] Optionally, the current application software includes target application software; and the upgrade deployment module further includes:
[0045] An upgrade determination submodule, used to determine whether the current version of the target application software is the latest version;
[0046] The upgrade deployment submodule is used to deploy the latest version of the target application software to the robot when the current version of the target application software is not the latest version.
[0047] Optionally, the upgrade deployment module is used to send an upgrade notification to the robot to upgrade the target application software to the latest version; or, to send an upgrade package corresponding to the latest version of the target application software to the robot.
[0048] Optionally, the first determination module is used to determine the target application software according to the new version release information when new version release information is received; or, when an upgrade request sent by the robot is received, determine the target application software according to the upgrade request.
[0049] An electronic device comprises a processor, a memory and a computer program stored in the memory and capable of running on the processor, wherein the steps of the version management method described above are implemented when the computer program is executed by the processor.
[0050] A computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the version management method described above are implemented.
[0051] Compared with the prior art, the embodiments of the present application have the following advantages:
[0052] In an embodiment of the present application, when the preset target application software upgrade trigger condition is reached, the target application software is determined, and the current version information and hardware information of the current application software of the robot are obtained; based on the current version information and hardware information of the current application software, it is determined whether the robot is compatible with the latest version of the target application software; if so, the latest version of the target application software is deployed to the robot; thereby achieving targeted deployment of the latest version of the target application software and ensuring that the robot deployed with the latest version of the target application software can normally install and use the latest version of the target application software.
Brief Description of the Drawings
[0053] In order to more clearly illustrate the technical solution of the present application, the drawings required for use in the description of the present application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0054] Figure 1It is a flowchart of the steps of a version management method in an embodiment of the present application;
[0055] Figure 2 is a dependency diagram of the application software dependency relationship of the embodiment of the present application;
[0056] Figure 3 It is a flowchart of a specific example of a version management method in an embodiment of the present application;
[0057] Figure 4 It is a structural block diagram of a version management device according to an embodiment of the present application. [Specific implementation method]
[0058] In order to make the above-mentioned purposes, features and advantages of the present application more obvious and easy to understand, the present application is further described in detail below with reference to the accompanying drawings and specific implementation methods.
[0059] Please refer to Figure 1 , shows a flow chart of the steps of a version management method of an embodiment of the present application, the method is applied to a robot application software management system, and the robot application software management system can be deployed on a server. In this embodiment, a robot is a machine device that automatically performs work, and can include an operating robot, a program-controlled robot, a teaching and reproduction robot, a numerically controlled robot, a sensory control robot, an adaptive control robot, a learning control robot, an intelligent robot, etc. The above method can specifically include
[0060] Step 101, when a preset application software upgrade trigger condition is met, a target application software is determined;
[0061] Step 102, obtaining the current version information and hardware information of the current application software of the robot;
[0062] Step 103, judging whether the robot is compatible with the latest version of the target application software according to the current version information of the current application software and the hardware information;
[0063] Step 104: If yes, deploy the latest version of the target application software to the robot.
[0064] When the preset target application software upgrade trigger condition is met, the embodiment of the present application determines the target application software through the robot application software management system, obtains the current version information and hardware information of the robot's current application software; determines whether the robot is compatible with the latest version of the target application software based on the current version information and hardware information of the current application software; if so, deploys the latest version of the target application software to the robot; thereby achieving targeted deployment of the latest version of the target application software and ensuring that the robot deployed with the latest version of the target application software can normally install and use the latest version of the target application software.
[0065] Next, the version management method in this exemplary embodiment will be further described.
[0066] In step 101, when a preset application software upgrade trigger condition is met, a target application software is determined.
[0067] The target application software may refer to the application software to be deployed by the robot application software management system.
[0068] In one embodiment of the present application, when the robot application software management system receives new version release information, the preset application software upgrade trigger condition is met, and the target application software can be determined based on the new version release information.
[0069] In the specific implementation, when a new version of application software is released on the upgrade server, the robot application software management system will receive the new version release information, which includes the target application software information. Therefore, the robot application software management system can parse the received new version release information and determine the target application software.
[0070] In another embodiment of the present application, the robot application software management system can also receive an upgrade request sent by the robot, the upgrade request includes target application software information, and the target application software can be determined according to the upgrade request.
[0071] In a specific implementation, since each version of application software has a specific life cycle, the robot can time the application software it installs and uses. When the preset usage time is reached, the robot can send an upgrade request for the application software that has reached the preset usage time to the robot application software management system. The application software reaching the preset usage time can refer to the time from the current time to the release time of the current version of the application software reaching the preset usage time; or, it can refer to the time from the current time to the last update time of the application software reaching the preset usage time. The robot application software management system can determine the target application software based on the received upgrade request.
[0072] In step 102, the current version information of the current application software and the hardware information of the robot are obtained.
[0073] The robot may refer to a robot that is connected to the robot application software management system. It is understood that there are generally more than one robot that is connected to the robot application software management system. In the embodiment of the present application, the application software version management can be performed on multiple robots respectively.
[0074] In this embodiment, the robot that is in communication with the robot application software management system will send login information to the robot application software management system when it is turned on; the login information includes the version information of the application software currently installed on the robot and the hardware information of the robot. After receiving the login information sent by the robot, the login information can be parsed to obtain the current version of the current application software and hardware properties of the robot.
[0075] By obtaining the current version information of the robot's current application software, when there is a risk vulnerability in the application software version, the impact can be evaluated based on the current version information of all robots' current application software obtained, and then a targeted remediation plan can be formulated to minimize the losses and impacts.
[0076] In step 103, it is determined whether the robot is compatible with the latest version of the target application software based on the current version information of the current application software and the hardware information.
[0077] After determining the target application software, the robot application software management system can further obtain the latest version information of the target application software, which can include the version number of the latest version and the upgrade package corresponding to the latest version. After obtaining the current version of the robot's current application software and hardware attributes, it can be determined whether the current version of the robot's current application software and hardware attributes are compatible with the latest version of the target application software, and then determine the robots that can be upgraded to the target application software for compatibility, and the robots that cannot be upgraded to the target application software for compatibility.
[0078] In a specific embodiment, before determining whether the robot is compatible with the latest version of the target application software, the following steps may be included:
[0079] Obtaining a preset dependency table, wherein the preset dependency table is used to record dependency information of each application software in the robot system;
[0080] Determining whether the target application software has dependent application software according to the preset dependency table;
[0081] If so, a compatible version of the dependent application software that is compatible with the latest version of the target application software is obtained.
[0082] For easier understanding, please refer to Figure 2 , an exemplary explanation of the concept of application-dependent software is given.
[0083] Assume that there are application software A, B, C, and D. Application software A depends on application software B and application software C, and application software B depends on application software D. At this point, it can be considered that application software B and application software C are dependent applications of application software A, and application software D is a dependent application of application software B. When application software A releases a new version, whether the new version of application software A can run normally depends on the versions of application software B and application software C. Only when the versions of application software B and application software C are compatible with the new version of application software A, the new version of application software A can run normally. Application software D does not have a dependency relationship. Therefore, when application software D is updated, the normal operation of the new version has nothing to do with other application software.
[0084] In this embodiment, the preset dependency table is used to record the dependency information of each application software in the robot system; when a new version of any application software in the robot system is released, a record needs to be generated and saved in the preset dependency table to facilitate the subsequent iteration management and problem tracing of versions. Furthermore, the record may include the version of the dependent application software that the new version of the application software is compatible with. The preset dependency table can be used to determine whether the target application software has dependent application software. When there is a dependency, it is necessary to obtain the dependent application software corresponding to the target application software, and obtain a compatible version of the dependent application software that is compatible with the latest version of the target application software.
[0085] By presetting the dependency table, it can be determined whether the latest version of the target application software has compatibility issues at the software level.
[0086] When the target application software does not have any dependent application software, it means that the latest version of the target application software does not have any compatibility issues at the software level.
[0087] When the target application software has dependent application software, the process of determining whether the latest version of the target application software has software-level compatibility issues may specifically include the following steps:
[0088] Determine whether the current version of the dependent application software belongs to the compatible version.
[0089] Specifically, after obtaining the compatible version of the dependent application software from the preset dependency table, the current version of the dependent application software can be determined from the current version of the current application software of the robot, and the current version of the dependent application software can be compared with the compatible version of the dependent application software. When the current version of the dependent application software is a compatible version, the robot can be compatible with the latest version of the target application software at the software level.
[0090] When the robot is compatible with the latest version of the target application software at the software level, it is necessary to further determine whether the robot's hardware level is compatible with the latest version of the target application software, that is, to determine whether the robot's hardware is compatible with the latest version of the target application software based on the hardware information.
[0091] In the specific implementation, when the latest version of the target application software is released, the hardware environment in which the latest version runs needs to be announced at the same time. The hardware attributes of the robot can be determined from the hardware information reported by the robot. When the hardware attributes belong to the hardware environment in which the latest version runs, it is determined that the robot is compatible with the latest version of the target application software at the hardware level.
[0092] In step 104, if yes, the latest version of the target application software is deployed to the robot.
[0093] When the robot is compatible with the latest version of the target application software at both the software level and the hardware level, the robot application software management system can deploy the latest version of the target application software to the robot.
[0094] Specifically, in an optional embodiment, the step of deploying the latest version of the target application software to the robot may include:
[0095] Sending an upgrade notification to the robot to upgrade the target application software to the latest version; or,
[0096] Send the upgrade package corresponding to the latest version of the target application software to the robot.
[0097] When the robot receives the upgrade notification, it can actively download the upgrade package corresponding to the latest version of the target application software according to the upgrade notification and install it, thereby realizing the upgrade operation of the target application software in the robot.
[0098] When the robot receives the upgrade package, it can directly use the upgrade package to upgrade the target application software.
[0099] Optionally, in order to prevent the robot from repeatedly upgrading the same version of the same application software, the above step of deploying the latest version of the target application software to the robot may further include:
[0100] Determining whether the current version of the target application software is the latest version;
[0101] If not, the above deploys the latest version of the target application software to the robot.
[0102] Before deploying the latest version of the target application software, this embodiment first determines whether the robot has already installed the latest version of the target application software. If so, there is no need to continue sending the corresponding upgrade package or upgrade notification of the latest version of the target application software to the robot; only when the current version of the robot's target application software is not the latest version, the latest version of the target application software is deployed to the robot.
[0103] Because the robot has been verified to be compatible with the latest version of the target application software from the software and hardware levels before the upgrade package corresponding to the latest version of the target application software is deployed, it can be ensured that the robot can normally install and use the latest version of the target application software.
[0104] Furthermore, in order to ensure successful application deployment, the above step of deploying the latest version of the target application software to the robot may further include: receiving update success information of the robot for the latest version of the target application software;
[0105] The current version of the target application version of the robot is updated according to the update success information.
[0106] When the robot's target application software is updated to the latest version, feedback information can be sent to the robot application software management system. The feedback information is the update success information of the latest version of the target application software. The robot application software management system can confirm that the robot has successfully deployed the latest version of the target application software based on the feedback information, and then update the current version of the robot's target application software. If no feedback information from the robot is received within a certain period of time, the latest version of the target application software can be re-deployed to the robot.
[0107] Optionally, the number of times to redeploy the latest version of the target application software to the robot can be set, and when the number of redeployments reaches a preset number, the latest version of the target application software to the robot is deployed. The preset number can range from 1 to 5, for example, 3 times can be selected.
[0108] Please refer to Figure 3 In order to facilitate those skilled in the art to understand the present invention, a specific example will be provided below for explanation.
[0109] Step 301, when the latest version (V1.2) of application software A is released, the preset application software upgrade trigger condition is met, and the target application software is determined to be application software A, and the latest version is V1.2;
[0110] Step 302, the dependency relationship of application software A can be obtained according to the preset dependency relationship table. If application software A does not have any dependent application software, proceed to step 303; if application software A has any dependent application software, proceed to step 304;
[0111] Step 303, check whether the current version of the application software A of the current robot is the latest version (V1.2); if so, proceed to step 305; if not, proceed to step 306;
[0112] Step 304, check whether the current version of the dependent application software of the current robot is compatible with the latest version of application software A; if so, proceed to step 306; if not, proceed to step 307;
[0113] Step 305, it is not necessary to deploy the latest version of application software A to the current robot;
[0114] Step 306, check whether the current robot's hardware is compatible with the latest version of application software A; if so, proceed to step 308; if not, proceed to step 309;
[0115] Step 307, it is necessary to synchronously trigger the upgrade triggering conditions of the dependent application software; optionally, when the hardware of the current robot is compatible with the application software A and its dependent application software, the upgraded application software A and its dependent application software are deployed on the current robot;
[0116] Step 308, deploy and upgrade application software A to the current robot;
[0117] Step 309: Do not upgrade the application software A of the current robot.
[0118] When the preset target application software upgrade trigger condition is met, the embodiment of the present application determines the target application software through the robot application software management system, obtains the current version information and hardware information of the robot's current application software; determines whether the robot is compatible with the latest version of the target application software based on the current version information and hardware information of the current application software; if so, deploys the latest version of the target application software to the robot; thereby achieving targeted deployment of the latest version of the target application software and ensuring that the robot deployed with the latest version of the target application software can normally install and use the latest version of the target application software.
[0119] It should be noted that, for the method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the embodiments of the present application are not limited by the described order of actions, because according to the embodiments of the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present application.
[0120] Reference Figure 4 , Figure 4 The structure block diagram of a version management device according to an embodiment of the present application is shown, and the device may specifically include the following modules:
[0121] The first determination module 401 is used to determine the target application software when a preset application software upgrade trigger condition is met;
[0122] The first acquisition module 402 is used to acquire the current version information and hardware information of the current application software of the robot;
[0123] A first judgment module 403 is used to judge whether the robot is compatible with the latest version of the target application software according to the current version information of the current application software and the hardware information;
[0124] The upgrade deployment module 404 is used to deploy the latest version of the target application software to the robot when the robot is compatible with the latest version of the target application software.
[0125] Optionally, the first acquisition module 402 includes:
[0126] The information receiving module is used to receive the login information sent by the robot;
[0127] The parsing and obtaining module is used to obtain the current version information of the current application software and the hardware information of the robot from the login information.
[0128] Optionally, the device further comprises:
[0129] A second acquisition module is used to acquire a preset dependency table, where the preset dependency table is used to record dependency information of each application software in the robot system;
[0130] A second judgment module is used to determine whether the target application software has dependent application software according to the preset dependency table;
[0131] The third acquisition module is used to acquire a compatible version of the dependent application software that is compatible with the latest version of the target application software when the target application software has dependent application software.
[0132] Optionally, the current application software includes the dependent application software, and the first determining module 403 includes:
[0133] A software determination submodule, used to determine whether the current version of the dependent application software belongs to the compatible version;
[0134] The hardware judgment submodule is used to judge whether the hardware of the robot is compatible with the latest version of the target application software according to the hardware information when the current version of the dependent application software belongs to the compatible version.
[0135] Optionally, the current application software includes target application software; the upgrade deployment module 404 further includes:
[0136] An upgrade determination submodule, used to determine whether the current version of the target application software is the latest version;
[0137] The upgrade deployment submodule is used to deploy the latest version of the target application software to the robot when the current version of the target application software is not the latest version.
[0138] Optionally, the upgrade deployment module 404 is used to send an upgrade notification to the robot to upgrade the target application software to the latest version; or, send an upgrade package corresponding to the latest version of the target application software to the robot.
[0139] Optionally, the first determination module 401 is used to determine the target application software according to the new version release information when new version release information is received; or, when an upgrade request sent by the robot is received, determine the target application software according to the upgrade request.
[0140] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.
[0141] An embodiment of the present application also discloses an electronic device, including a processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein the computer program implements the steps of the version management method described above when executed by the processor.
[0142] The embodiment of the present application further discloses a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the version management method described above are implemented.
[0143] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.
[0144] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, devices, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0145] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, terminal devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing terminal device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing terminal device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0146] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing terminal device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0147] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device so that a series of operating steps are executed on the computer or other programmable terminal device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable terminal device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.
[0148] Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present application.
[0149] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or terminal device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or terminal device including the elements.
[0150] The above is a detailed introduction to a version management method and a version management device provided by the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea. At the same time, for general technical personnel in this field, according to the idea of the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.
Claims
1. A version management method, characterized in that: The method comprises: When the preset application software upgrade trigger condition is met, the target application software is determined; Get the current version information and hardware information of the robot's current application software; Determining whether the robot is compatible with the latest version of the target application software based on the current version information of the current application software and the hardware information; If yes, deploying the latest version of the target application software to the robot; The method further comprises: Obtaining a preset dependency table, wherein the preset dependency table is used to record dependency information of each application software in the robot system; Determining whether the target application software has dependent application software according to the preset dependency table; If so, obtaining a compatible version of the dependent application software that is compatible with the latest version of the target application software; The current application software includes the dependent application software, and the step of judging whether the robot is compatible with the latest version of the target application software based on the current version information and hardware information of the current application software includes: Determining whether the current version of the dependent application software belongs to the compatible version; If so, it is determined whether the hardware of the robot is compatible with the latest version of the target application software based on the hardware information.
2. The method according to claim 1, characterized in that The step of obtaining the current version information of the current application software and the hardware information of the robot includes: Receive login information sent by the robot; The current version information of the current application software and the hardware information of the robot are obtained from the login information.
3. The method according to any one of claims 1 to 2, characterized in that: The current application software includes the target application software; and the step of deploying the latest version of the target application software to the robot further includes: Determining whether the current version of the target application software is the latest version; If not, the latest version of the target application software is deployed to the robot.
4. The method according to claim 3, characterized in that The step of deploying the latest version of the target application software to the robot comprises: Sending an upgrade notification to the robot to upgrade the target application software to the latest version; or, Send the upgrade package corresponding to the latest version of the target application software to the robot.
5. The method according to claim 1, characterized in that The step of determining the target application software when the preset application software upgrade trigger condition is met includes: When new version release information is received, determining the target application software according to the new version release information; Alternatively, when an upgrade request sent by the robot is received, the target application software is determined according to the upgrade request.
6. An electronic device, characterized in that: The method comprises a processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein the computer program implements the steps of the version management method according to any one of claims 1 to 5 when executed by the processor.
7. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the version management method according to any one of claims 1 to 5 are implemented.
Citation Information
Patent Citations
Software upgrade method and upgrade server
CN107463390A
Application software updating method, device, computer device and storage medium
CN109408083A
