CN112463208A - Version management method and device, electronic equipment and storage medium - Google Patents
Version management method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN112463208A CN112463208A CN202011529631.4A CN202011529631A CN112463208A CN 112463208 A CN112463208 A CN 112463208A CN 202011529631 A CN202011529631 A CN 202011529631A CN 112463208 A CN112463208 A CN 112463208A
- Authority
- CN
- China
- Prior art keywords
- application software
- robot
- version
- target application
- current
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 28
- 238000000034 method Methods 0.000 claims abstract description 28
- 230000001419 dependent effect Effects 0.000 claims description 41
- 238000004590 computer program Methods 0.000 claims description 17
- 238000010586 diagram Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 6
- 230000008569 process Effects 0.000 description 5
- 238000012545 processing Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000035807 sensation Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the application provides a version management method and device, electronic equipment and a storage medium, wherein the method comprises the following steps: when a preset target application software upgrading triggering condition is reached, determining target application software, and acquiring current version information and hardware information of current application software of the robot; judging whether the robot is compatible with the latest version of the target application software according to the current version information and the hardware information of the current application software; if so, deploying the latest version of the target application software for the robot; therefore, the latest version of the target application software is deployed in a targeted mode, and the robot which deploys the latest version of the target application software can be ensured to install and use the latest version of the target application software normally.
Description
[ technical field ] A method for producing a semiconductor device
The present application relates to the field of robotics, and in particular, to a version management method and apparatus, an electronic device, and a storage medium.
[ background of the invention ]
With the continuous development of robot technology, robots are widely applied in various industries. In order to make the robot provide better service, the need for updating and upgrading the version of the robot system is increasing. The robot system can be disassembled into application software with different functions according to different business functions, and the dependence of upper and lower layers can be inevitably generated among different application software. When updating and upgrading the robot system, a design principle that only one application software is concerned and is as perfect as possible is usually followed, so that a plurality of application software in the robot system can work in cooperation with each other.
In the prior art, when the version upgrade of the application software is deployed and managed, the dependency relationship existing in different applications is not considered, which easily causes an embarrassing situation that the robot cannot be normally used after the application software of the latest version is installed.
[ summary of the invention ]
In view of the above, the present application is proposed to provide a version management method and apparatus, an electronic device, a storage medium that overcome or at least partially solve the above problems.
The embodiment of the application provides a version management method, which comprises the following steps:
when a preset application software upgrading triggering condition is reached, determining target application software;
acquiring current version information and hardware information of current application software of the robot;
judging whether the robot is compatible with the latest version of the target application software according to the current version information and the hardware information of the current application software;
and if so, deploying the latest version of the target application software for the robot.
Optionally, the step of acquiring current version information and hardware information of current application software of the robot includes:
receiving login information sent by a robot;
and acquiring the current version information and the hardware information of the current application software of the robot from the login information.
Optionally, the method further comprises:
acquiring a preset dependency relationship table, wherein the preset dependency relationship table is used for recording dependency relationship information of each application software in the robot system;
determining whether the target application software has dependent application software according to the preset dependency relationship table;
and if so, acquiring a compatible version of the dependent application software which is compatible with the latest version of the target application software.
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 according to the current version information and the hardware information of the current application software includes:
judging whether the current version of the dependent application software belongs to the compatible version;
and if so, judging whether the hardware of the robot is compatible with the latest version of the target application software according to the hardware information.
Optionally, the current application software comprises target application software; the step of deploying the latest version of the target application software to the robot further comprises:
judging whether the current version of the target application software is the latest version;
if not, deploying the latest version of the target application software for the robot.
Optionally, the step of deploying the latest version of the target application software to the robot includes:
sending an upgrade notification to the robot to upgrade the target application software to a latest version; or,
and sending the upgrade package corresponding to the latest version of the target application software to the robot.
Optionally, the step of determining the target application software when a preset application software upgrade trigger condition is reached includes:
when receiving the release information of the new version, determining target application software according to the release information of the new version;
or when an upgrading request sent by the robot is received, determining target application software according to the upgrading request.
An embodiment of the present application further provides a version management apparatus, where the apparatus includes:
the first determining module is used for determining target application software when a preset application software upgrading triggering condition is reached;
the first acquisition module is used for acquiring the current version information and the hardware information of the current application software of the robot;
the first judgment module is used for judging whether the robot is compatible with the latest version of the target application software according to the current version information and the hardware information of the current application software;
and the upgrading deployment module is used for deploying the latest version of the target application software for the robot when the robot is compatible with the latest version of the target application software.
Optionally, the first obtaining module includes:
the information receiving module is used for receiving login information sent by the robot;
and the analysis acquisition module is used for acquiring the current version information and the hardware information of the current application software of the robot from the login information.
Optionally, the apparatus further comprises:
the second acquisition module is used for acquiring a preset dependency relationship table, and the preset dependency relationship table is used for recording dependency relationship information of each application software in the robot system;
the second judgment module is used for determining whether the target application software has dependent application software according to the preset dependency relationship table;
and the third acquisition module is used for acquiring a compatible version of the dependent application software, which is compatible with the latest version of the target application software, when the target application software has the dependent application software.
Optionally, the current application software includes the dependent application software, and the first determining module includes:
a software judgment sub-module, configured to judge whether the current version of the dependent application software belongs to the compatible version;
and the hardware judgment sub-module is used for judging 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.
Optionally, the current application software comprises target application software; the upgrade deployment module further comprises:
the upgrading judgment sub-module is used for judging whether the current version of the target application software is the latest version;
and the upgrading deployment submodule is used for deploying 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.
Optionally, the upgrade deployment module is configured to send an upgrade notification to the robot to upgrade the target application software to a latest version; or sending an upgrade package corresponding to the latest version of the target application software to the robot.
Optionally, the first determining module is configured to determine, when receiving the new release information, the target application software according to the new release information; or when an upgrading request sent by the robot is received, determining target application software according to the upgrading request.
An electronic device comprising a processor, a memory and a computer program stored on the memory and being executable on the processor, the computer program, when executed by the processor, implementing the steps of the method of version management as described above.
A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method of version management as set forth above.
Compared with the prior art, the embodiment of the application has the following advantages:
in the embodiment of the application, when a preset target application software upgrading triggering condition is reached, the target application software is determined, and the current version information and the hardware information of the current application software of the robot are acquired; judging whether the robot is compatible with the latest version of the target application software according to the current version information and the hardware information of the current application software; if so, deploying the latest version of the target application software for the robot; therefore, the latest version of the target application software is deployed in a targeted mode, and the robot which deploys the latest version of the target application software can be ensured to install and use the latest version of the target application software normally.
[ description of the drawings ]
In order to more clearly illustrate the technical solutions of the present application, the drawings needed to be used in the description of the present application will be briefly introduced below, and it is apparent that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive labor.
FIG. 1 is a flowchart illustrating the steps of a version management method according to an embodiment of the present application;
FIG. 2 is a dependency graph of application software dependencies for an embodiment of the application;
FIG. 3 is a flowchart illustrating steps of a specific example of a version management method according to an embodiment of the present application;
fig. 4 is a block diagram of a version management apparatus according to an embodiment of the present application.
[ detailed description ] embodiments
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, the present application is described in further detail with reference to the accompanying drawings and the detailed description.
Referring to fig. 1, a flowchart illustrating steps of a version management method according to an embodiment of the present application is shown, where the method is applied to a robot application management system, and the robot application management system may be deployed on a server. In this embodiment, the robot is a machine device that automatically executes work, and may include an operation type robot, a program control type robot, a teaching/playback type robot, a numerical control type robot, a sensation control type robot, an adaptation control type robot, a learning control type robot, an intelligent robot, and the like. The method may specifically comprise
102, acquiring current version information and hardware information of current application software of the robot;
103, judging whether the robot is compatible with the latest version of the target application software according to the current version information and the hardware information of the current application software;
and 104, if yes, deploying the latest version of the target application software to the robot.
When a preset target application software upgrading triggering condition is reached, determining target application software through a robot application software management system, and acquiring current version information and hardware information of current application software of a robot; judging whether the robot is compatible with the latest version of the target application software according to the current version information and the hardware information of the current application software; if so, deploying the latest version of the target application software for the robot; therefore, the latest version of the target application software is deployed in a targeted mode, and the robot which deploys the latest version of the target application software can be ensured to install and use the latest version of the target application software normally.
Next, a version management method in the present exemplary embodiment will be further described.
In step 101, when a preset application software upgrade trigger condition is reached, target application software is determined.
The target application software may refer to application software to be deployed by the robot application software management system.
In an embodiment of the application, when the robot application software management system receives the new version release information, that is, a preset application software upgrade trigger condition is reached, the target application software can be determined according to the new version release information.
In a specific implementation, when a new version of application software is released on the upgrade server, the robot application software management system receives new version release information, where the new version release information includes target application software information, and therefore the robot application software management system can analyze the received new version release information to determine the target application software.
In another embodiment of the application, the robot application software management system may further receive an upgrade request sent by the robot, where the upgrade request includes target application software information, and the target application software may be determined according to the upgrade request.
In a specific implementation, since each version of the application software has a specific life cycle, the robot may time the application software installed and used by the robot, and when the preset use time is reached, the robot may send an upgrade request for the application software reaching the preset use time to the robot application software management system. The time for the application software to reach the preset use time can mean that the time between the current time and the release time of the current version of the application software reaches the preset use time; or, the time length from the current time to the latest update time of the application software may be the preset use time. The robot application software management system may determine the target application software based on the received upgrade request.
In step 102, current version information and hardware information of current application software of the robot are acquired.
Wherein, a robot may refer to a robot that is communicatively connected to a robot application management system. It can be understood that there is generally more than one robot in communication connection with the robot application software management system, and in the embodiment of the present application, version management of application software may be performed on a plurality of robots, respectively.
In this embodiment, the robot in communication connection with the robot application software management system sends login information to the robot application software management system when the robot is started; the login information includes version information of application software currently installed by the robot and hardware information of the robot. After the login information sent by the robot is received, the login information can be analyzed, so that the current version and the hardware attribute of the current application software of the robot can be obtained.
By acquiring the current version information of the current application software of the robot, when the version of the application software has a risk vulnerability, the influence surface can be evaluated according to the acquired current version information of the current application software of the robot, so that a remedy scheme can be made in a targeted manner, and the loss and the influence are compressed to the minimum.
In step 103, it is determined whether the robot is compatible with the latest version of the target application software according to the current version information and the hardware information of the current application software.
After determining the target application software, the robot application software management system may further obtain latest version information of the target application software, where the latest version information may include a version number of the latest version and an upgrade package corresponding to the latest version. After the current version and the hardware attribute of the current application software of the robot are obtained, whether the current version and the hardware attribute of the current application software of the robot are compatible with the latest version of the target application software or not can be judged, and then the robot capable of compatibly upgrading the target application software and the robot incapable of compatibly upgrading the target application software are determined.
In a specific embodiment, before the determining whether the robot is compatible with the latest version of the target application software, the method may include the following steps:
acquiring a preset dependency relationship table, wherein the preset dependency relationship table is used for recording dependency relationship information of each application software in the robot system;
determining whether the target application software has dependent application software according to the preset dependency relationship table;
and if so, acquiring a compatible version of the dependent application software which is compatible with the latest version of the target application software.
For ease of understanding, the concept of relying on application software is exemplarily explained with reference to fig. 2.
Assume that application software A, B, C, D exists, application software a depends on application software B and application software C, and application software B depends on application software D. At this time, it is assumed that the application software B and the application software C are dependent application software of the application software a, and the application software D is dependent application software of the application software B. And when the application software A releases a new version, whether the application software A of the new version can normally run is related to the versions of the application software B and the application software C, and the new version of the application software A can normally run only when the versions of the application software B and the application software C can be compatible with the new version of the application software A. And the application software D has no dependency relationship, so when the application software D updates the version, the new version can normally run independent of other application software.
In this embodiment, the preset dependency relationship table is used to record dependency relationship 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 stored in the preset dependency relationship table, so that iterative management and problem tracing of subsequent versions are facilitated. Further, the record may include versions of dependent application software that are compatible with the new version of the application software. Whether the target application software has the dependent application software can be determined through the preset dependency relation table. When the dependency relationship exists, the dependent application software corresponding to the target application software needs to be acquired, and a compatible version of the latest version of the target application software, which can be compatible with the dependent application software, is acquired.
By presetting the dependency relationship table, whether the latest version of the target application software has the compatibility problem of the software layer or not can be judged.
When the target application software does not have the dependent application software, the compatibility problem of the software level does not exist in the latest version of the target application software.
When the target application software has a dependent application software, the process of determining whether the latest version of the target application software has a software-level compatibility problem may specifically include the following steps:
determining whether the current version of the dependent application software belongs to the compatible version.
Specifically, after the compatible version of the dependent application software is acquired from the preset dependency relationship table, the current version of the dependent application software can be determined from the current version of the current application software of the robot, the current version of the dependent application software is compared with the compatible version of the dependent application software, and when the current version of the dependent application software belongs to the compatible version, the robot can be compatible with the latest version of the target application software at a software level.
When the robot can be compatible with the latest version of the target application software at the software level, it needs to further judge whether the hardware level of the robot is compatible with the latest version of the target application software, that is, judge whether the hardware of the robot is compatible with the latest version of the target application software according to the hardware information.
In a 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 simultaneously published. The hardware attribute of the robot can be determined from the hardware information reported by the robot, and when the hardware attribute belongs to the hardware environment with the latest version running, the robot is determined to be compatible with the latest version of the target application software in the hardware level.
In step 104, if yes, the latest version of the target application software is deployed to the robot.
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.
Specifically, in an optional embodiment, the step of deploying the latest version of the target application software to the robot may include:
sending an upgrade notification to the robot to upgrade the target application software to a latest version; or,
and sending the upgrade package corresponding to the latest version of the target application software to the robot.
When the robot receives the upgrade notification, the robot can actively execute the upgrade package corresponding to the latest version of the downloaded target application software according to the upgrade notification, and install the upgrade package, so that the upgrade operation of the target application software in the robot is realized.
When the robot receives the upgrade package, the target application software can be upgraded by directly using the upgrade package.
Optionally, in order to prevent the robot from performing repeated upgrade operations on the same version of the same application software, the deploying the latest version of the target application software to the robot may further include:
judging whether the current version of the target application software is the latest version;
and if not, deploying the latest version of the target application software to the robot.
In this embodiment, before deploying the latest version of the target application software, it is first determined whether the robot has installed the latest version of the target application software, and if so, it is not necessary to continue to send the corresponding upgrade package or upgrade notification of the latest version of the target application software to the robot; only if the current version of the target application software of the robot is not the latest version, the latest version of the target application software is deployed to the robot.
Since it is verified from the software level and the hardware level that the robot can be compatible with the latest version of the target application software 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.
Further, in order to ensure that the application deployment is successful, the deploying the latest version of the target application software to the robot may further include: receiving update success information of the robot aiming at the latest version of the target application software;
and updating the current version of the target application version of the robot according to the updating success information.
When the target application software of the robot is updated to the latest version, feedback information can be sent to the robot application software management system, wherein the feedback information is the update success information of the latest version of the target application software, and the robot application software management system can confirm that the robot has successfully deployed the latest version of the target application software according to the feedback information, so as to update the current version of the target application software of the robot. If the feedback information of the robot is not received within a certain time, the latest version of the target application software can be deployed to the robot again.
Optionally, the number of times of redeploying the latest version of the target application software to the robot may be set, and when the number of redeployments reaches a preset number of times, the robot is terminated to deploy the latest version of the target application software. The range of the preset number of times may be: 1-5, for example, 3 times can be selected.
Referring to fig. 3, the following description will be made with reference to a specific example in order to facilitate understanding of the present solution by those skilled in the art.
305, deploying the latest version of the application software A to the current robot;
308, deploying and upgrading application software A for the current robot;
When a preset target application software upgrading triggering condition is reached, determining target application software through a robot application software management system, and acquiring current version information and hardware information of current application software of a robot; judging whether the robot is compatible with the latest version of the target application software according to the current version information and the hardware information of the current application software; if so, deploying the latest version of the target application software for the robot; therefore, the latest version of the target application software is deployed in a targeted mode, and the robot which deploys the latest version of the target application software can be ensured to install and use the latest version of the target application software normally.
It should be noted that, for simplicity of description, the method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the embodiments are not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the embodiments. Further, those skilled in the art will also appreciate that the embodiments described in the specification are presently preferred and that no particular act is required of the embodiments of the application.
Referring to fig. 4, fig. 4 is a block diagram illustrating a version management apparatus according to an embodiment of the present application, where the apparatus may specifically include the following modules:
a first determining module 401, configured to determine target application software when a preset application software upgrade trigger condition is reached;
a first obtaining module 402, configured to obtain current version information and hardware information of current application software of the robot;
a first judging module 403, configured to judge, according to the current version information and the hardware information of the current application software, whether the robot is compatible with the latest version of the target application software;
an upgrade deployment module 404, configured 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.
Optionally, the first obtaining module 402 includes:
the information receiving module is used for receiving login information sent by the robot;
and the analysis acquisition module is used for acquiring the current version information and the hardware information of the current application software of the robot from the login information.
Optionally, the apparatus further comprises:
the second acquisition module is used for acquiring a preset dependency relationship table, and the preset dependency relationship table is used for recording dependency relationship information of each application software in the robot system;
the second judgment module is used for determining whether the target application software has dependent application software according to the preset dependency relationship table;
and the third acquisition module is used for acquiring a compatible version of the dependent application software, which is compatible with the latest version of the target application software, when the target application software has the dependent application software.
Optionally, the current application software includes the dependent application software, and the first determining module 403 includes:
a software judgment sub-module, configured to judge whether the current version of the dependent application software belongs to the compatible version;
and the hardware judgment sub-module is used for judging 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.
Optionally, the current application software comprises target application software; the upgrade deployment module 404 further includes:
the upgrading judgment sub-module is used for judging whether the current version of the target application software is the latest version;
and the upgrading deployment submodule is used for deploying 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.
Optionally, the upgrade deployment module 404 is configured to send an upgrade notification to the robot to upgrade the target application software to the latest version; or sending an upgrade package corresponding to the latest version of the target application software to the robot.
Optionally, the first determining module 401 is configured to determine, when receiving a new release message, a target application software according to the new release message; or when an upgrading request sent by the robot is received, determining target application software according to the upgrading request.
For the device embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.
The embodiment of the application also discloses an electronic device, which comprises a processor, a memory and a computer program stored on the memory and capable of running on the processor, wherein when the computer program is executed by the processor, the steps of the version management method are realized.
The embodiment of the application also discloses a computer readable storage medium, wherein a computer program is stored on the computer readable storage medium, and when the computer program is executed by a processor, the steps of the version management method are realized.
The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.
As will be appreciated by one of skill in the art, embodiments of the present application may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing terminal to cause a series of operational steps to be performed on the computer or other programmable terminal to produce a computer implemented process such that the instructions which execute on the computer or other programmable terminal provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present application have been described, additional variations and modifications of these embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including the preferred embodiment and all such alterations and modifications as fall within the true scope of the embodiments of the application.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or terminal that comprises the element.
The foregoing detailed description is directed to a version management method and a version management apparatus provided in the present application, and specific examples are applied herein to illustrate the principles and embodiments of the present application, and the description of the foregoing embodiments is only used to help understand the method and the core ideas of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (10)
1. A version management method, characterized in that the method comprises:
when a preset application software upgrading triggering condition is reached, determining target application software;
acquiring current version information and hardware information of current application software of the robot;
judging whether the robot is compatible with the latest version of the target application software according to the current version information and the hardware information of the current application software;
and if so, deploying the latest version of the target application software for the robot.
2. The method of claim 1, wherein the step of obtaining the current version information and the hardware information of the current application software of the robot comprises:
receiving login information sent by a robot;
and acquiring the current version information and the hardware information of the current application software of the robot from the login information.
3. The method of claim 2, further comprising:
acquiring a preset dependency relationship table, wherein the preset dependency relationship table is used for recording dependency relationship information of each application software in the robot system;
determining whether the target application software has dependent application software according to the preset dependency relationship table;
and if so, acquiring a compatible version of the dependent application software which is compatible with the latest version of the target application software.
4. The method of claim 3, wherein the current application software comprises the dependent application software, and the step of determining whether the robot is compatible with the latest version of the target application software according to the current version information and the hardware information of the current application software comprises:
judging whether the current version of the dependent application software belongs to the compatible version;
and if so, judging whether the hardware of the robot is compatible with the latest version of the target application software according to the hardware information.
5. The method of any of claims 1-4, wherein the current application software comprises a target application software; the step of deploying the latest version of the target application software to the robot further comprises:
judging whether the current version of the target application software is the latest version;
if not, deploying the latest version of the target application software for the robot.
6. The method of claim 5, wherein 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 a latest version; or,
and sending the upgrade package corresponding to the latest version of the target application software to the robot.
7. The method of claim 1, wherein the step of determining the target application software when the preset application software upgrade triggering condition is reached comprises:
when receiving the release information of the new version, determining target application software according to the release information of the new version;
or when an upgrading request sent by the robot is received, determining target application software according to the upgrading request.
8. A version management apparatus, characterized in that the apparatus comprises:
the first determining module is used for determining target application software when a preset application software upgrading triggering condition is reached;
the first acquisition module is used for acquiring the current version information and the hardware information of the current application software of the robot;
the first judgment module is used for judging whether the robot is compatible with the latest version of the target application software according to the current version information and the hardware information of the current application software;
and the upgrading deployment module is used for deploying the latest version of the target application software for the robot when the robot is compatible with the latest version of the target application software.
9. An electronic device comprising a processor, a memory and a computer program stored on the memory and capable of running on the processor, the computer program, when executed by the processor, implementing the steps of the version management method of any one of claims 1 to 7.
10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the version management method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011529631.4A CN112463208A (en) | 2020-12-22 | 2020-12-22 | Version management method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011529631.4A CN112463208A (en) | 2020-12-22 | 2020-12-22 | Version management method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112463208A true CN112463208A (en) | 2021-03-09 |
Family
ID=74804554
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011529631.4A Pending CN112463208A (en) | 2020-12-22 | 2020-12-22 | Version management method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112463208A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116028101A (en) * | 2022-12-26 | 2023-04-28 | 郑州云智信安安全技术有限公司 | Method for scheduling and retrieving based on component feature category |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107015828A (en) * | 2017-03-31 | 2017-08-04 | 广东欧珀移动通信有限公司 | Audio software upgrade method, application program updating method, apparatus and system |
| CN107463390A (en) * | 2016-06-02 | 2017-12-12 | 阿里巴巴集团控股有限公司 | A kind of method for upgrading software and upgrade server |
| CN109408083A (en) * | 2018-09-26 | 2019-03-01 | 平安普惠企业管理有限公司 | Application software update method, device, computer equipment and storage medium |
| CN111381842A (en) * | 2018-12-27 | 2020-07-07 | 深圳市优必选科技有限公司 | Robot upgrading method, electronic equipment and server |
-
2020
- 2020-12-22 CN CN202011529631.4A patent/CN112463208A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107463390A (en) * | 2016-06-02 | 2017-12-12 | 阿里巴巴集团控股有限公司 | A kind of method for upgrading software and upgrade server |
| CN107015828A (en) * | 2017-03-31 | 2017-08-04 | 广东欧珀移动通信有限公司 | Audio software upgrade method, application program updating method, apparatus and system |
| CN109408083A (en) * | 2018-09-26 | 2019-03-01 | 平安普惠企业管理有限公司 | Application software update method, device, computer equipment and storage medium |
| CN111381842A (en) * | 2018-12-27 | 2020-07-07 | 深圳市优必选科技有限公司 | Robot upgrading method, electronic equipment and server |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116028101A (en) * | 2022-12-26 | 2023-04-28 | 郑州云智信安安全技术有限公司 | Method for scheduling and retrieving based on component feature category |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10545469B2 (en) | Systems and methods for self provisioning building equipment | |
| EP3002930A1 (en) | Method, system, terminal and device management server for installing software components | |
| US20060236083A1 (en) | Method and system for controlling software version updates | |
| CN106886436B (en) | Android system upgrading method and device | |
| EP2456257A1 (en) | Method and system for upgrading wireless data card | |
| JP2006268172A (en) | Server system and method for updating online software | |
| CN111679888A (en) | Deployment method and device of agent container | |
| CN105045640A (en) | Software upgrading method and device and intelligent equipment | |
| CN116820493A (en) | Mirror image file deployment method, system, equipment and storage medium | |
| CN116257438A (en) | Updating method of interface test case and related equipment | |
| CN107463390B (en) | Software upgrading method and upgrading server | |
| CN112463208A (en) | Version management method and device, electronic equipment and storage medium | |
| CN111324365A (en) | Method and equipment for upgrading super-converged system | |
| CN112860251A (en) | Method and system for constructing website front end | |
| CN114138296A (en) | Multi-system gateway upgrading method, equipment and storage medium | |
| CN104158906A (en) | Server agent manipulation system and manipulation method | |
| CN113608831B (en) | Plug-in instance management method, system, storage medium and equipment | |
| CN113448609B (en) | Container upgrading method, device, equipment and storage medium | |
| CN101420322B (en) | Upgrading method, device and system for network equipment | |
| CN113010266A (en) | Cloud service restarting method and device | |
| CN113031977A (en) | Software batch installation method and related device | |
| CN110752950A (en) | Update detection method and device for cloud resource pool and terminal equipment | |
| CN106843922B (en) | Program updating method and device | |
| CN110825406A (en) | Software upgrading method and related equipment | |
| CN104298522A (en) | Information processing method and first electronic device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |