CN114090049A - Robot remote packaging and upgrading method and system and related products - Google Patents
Robot remote packaging and upgrading method and system and related products Download PDFInfo
- Publication number
- CN114090049A CN114090049A CN202111440005.2A CN202111440005A CN114090049A CN 114090049 A CN114090049 A CN 114090049A CN 202111440005 A CN202111440005 A CN 202111440005A CN 114090049 A CN114090049 A CN 114090049A
- Authority
- CN
- China
- Prior art keywords
- robot
- upgrading
- package
- version
- suite
- 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
- 238000004806 packaging method and process Methods 0.000 title claims abstract description 53
- 238000000034 method Methods 0.000 title claims abstract description 49
- 238000004590 computer program Methods 0.000 claims description 17
- 238000003860 storage Methods 0.000 claims description 7
- 238000012795 verification Methods 0.000 claims description 7
- 230000008569 process Effects 0.000 description 6
- 238000004891 communication Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 238000005457 optimization Methods 0.000 description 2
- 238000000275 quality assurance Methods 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000004744 fabric Substances 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001960 triggered effect 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/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a robot remote packaging and upgrading method, a system and a related product, wherein the robot remote packaging and upgrading method comprises the following steps: determining all package files and version numbers thereof which need to be upgraded by the robot, packaging the package files and the version numbers thereof in the same external member, and storing the package files in a cloud end, wherein the package files are software and hardware files; the platform issues issuing commands of corresponding suites to a plurality of robots at a robot end through a DevOps main server; and the robot downloads the corresponding package file of the suite from the cloud and then finishes upgrading. According to the invention, the robot can download the required suite from the cloud according to the issuing command and complete the upgrading of the corresponding package file, so that the integrated issuing of the upgrading and updating task is realized in the platform, the management degree of the platform on the task issuing is simplified, and the number of tasks in the cloud is reduced.
Description
[ technical field ] A method for producing a semiconductor device
The invention relates to the technical field of robots, in particular to a robot remote packaging and upgrading method and a related product.
[ background of the invention ]
At present, after the fixed-model mass production of the hardware structure level of the current robot, more upgrading iterations of trusting software/firmware versions in the aspect of subsequent product experience optimization are performed, and then the BUG is repaired or new functions brought to the user in the aspect of use are brought. In the robot release platform, once an action is released, a large amount of software and hardware of the robot need to be updated, so that the number of tasks at the cloud is huge, the task management and release are difficult, and the robot software/firmware can not be updated in time.
In view of the above, there is a need to provide a method, a system and a related product for remote packaging and upgrading of a robot to overcome the above-mentioned drawbacks.
[ summary of the invention ]
The invention aims to provide a remote packaging and upgrading method for a robot and a related product, which aims to solve the problem of huge task quantity when a robot platform is updated and released, avoid the difficulty in managing and releasing tasks and facilitate the timely update of robot software/firmware.
In order to achieve the above object, a first aspect of the present invention provides a robot remote packaging and upgrading method, including the following steps:
determining all the package files and version numbers thereof which need to be upgraded by the robot, packaging the package files and the version numbers thereof, putting the package files in the same external member and storing the package files in a cloud end, wherein the package files are software and hardware files;
the platform issues issuing commands of corresponding suites to the multiple robots of the robot end through the DevOps main server according to the unique serial numbers of the robots;
and after receiving the issuing command of the DevOps main server through a client of the robot, downloading the corresponding package file of the suite from the cloud, and then finishing upgrading.
In a preferred embodiment, after receiving the issuing command of the DevOps master server through a client of the robot, the robot downloads a corresponding package file of the suite from the cloud, and then completes the upgrading step, including the following steps:
and after downloading the corresponding suite from the cloud end, the robot carries out self-checking on the version of the package file of the suite according to the issuing command, confirms whether the version of the package file is correct or not according to the version information reporting time, and if the result is not, reports an error through the DevOps main server.
In a preferred embodiment, the robot remote packaging upgrading method further includes the steps of:
after the robot finishes upgrading, the robot automatically reports the current version information of the robot to the DevOps master server, version verification is carried out on the current version information and the version of the package file of the suite, and if the verification result is not matched, the robot reports an error to the DevOps master server.
In a preferred embodiment, the robot remote packaging upgrading method further includes the steps of:
acquiring the current state of the robot and judging whether the upgrading requirement of the package file is met, if so, updating the upgrade according to the suite; and if the result is negative, suspending the updating and upgrading of the suite.
In a preferred embodiment, the robot remote packaging upgrading method further includes the steps of:
and creating a version dependence map of the robot end.
In a preferred embodiment, the robot sequentially upgrades the package files in the suite according to the dependency relationship in the version dependency graph.
In a preferred embodiment, the robot remote packaging upgrading method further includes the steps of:
and judging the priority level of upgrading the package files, suspending the execution of the current task and updating and upgrading on the robot if the package files exceed the preset level, and executing updating and upgrading after the current task is finished on the robot if the package files do not exceed the preset level.
The invention provides a robot remote packaging and upgrading system in a second aspect, which comprises a platform and a robot;
the platform comprises a file determining module, a file storing module, a suite creating module and a command issuing module;
the file determining module is used for determining all package files and version numbers thereof, which need to be upgraded, of the robot, wherein the package files are software and hardware files;
the file storage module is used for receiving the package file with the corresponding version number and storing the package file in the cloud;
the kit creating module is used for packaging all package files and version numbers thereof which need to be upgraded by the robot and placing the package files and the version numbers in the same kit;
the command issuing module is used for issuing commands of corresponding suites to the multiple robots at the robot end through the DevOps main server according to the unique serial numbers of the robots;
and the robot is used for downloading the corresponding package file of the suite from the cloud after receiving the issuing command of the DevOps main server through a client of the robot, and then finishing upgrading.
A third aspect of the present invention provides a terminal, which includes a memory, a processor, and a computer program stored in the memory, and when the computer program is executed by the processor, the computer program implements the steps of the robot remote packaging and upgrading method according to any one of the above embodiments.
A fourth aspect of the present invention provides a computer-readable storage medium, which stores a computer program, and the computer program, when executed by a processor, implements the steps of the robot remote packaging and upgrading method according to any one of the above embodiments.
A fifth aspect of the present invention provides a computer program product comprising a computer program or instructions which, when being processed and executed, implement the steps of the robot remote packaging upgrade method according to any one of the above embodiments.
According to the remote packaging and upgrading method for the robot and the related product, the package files and versions required by the robot are placed in the same suite in the platform, then the platform issues issuing commands to the multiple robots at the robot end through the DevOps main server, and finally the robot downloads the needed suite from the cloud according to the issuing commands to complete upgrading of the corresponding package files, so that integrated issuing of upgrading and updating tasks is achieved in the platform, the management degree of the platform for task issuing is simplified, and the number of tasks at the cloud is reduced.
[ description of the drawings ]
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.
Fig. 1 is a flowchart of an embodiment of a robot remote packaging and upgrading method provided by the present invention;
FIG. 2 is a flowchart of another embodiment of a remote packaging and upgrading method for a robot according to the present invention;
fig. 3 is a framework diagram of an embodiment of a robot remote packaging upgrade system provided by the present invention.
[ detailed description ] embodiments
In order to make the objects, technical solutions and advantageous effects of the present invention more clearly apparent, the present invention is further described in detail below with reference to the accompanying drawings and the detailed description. It should be understood that the detailed description and specific examples, while indicating the preferred embodiment of the invention, are intended for purposes of illustration only and are not intended to limit the scope of the invention.
It is also to be understood that the terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the specification of the present invention and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
In an embodiment of the invention, a robot remote packaging upgrading method is provided, which is used for remotely sending software, hardware and version updating tasks corresponding to a plurality of robots in a platform, so that the robots remotely complete the upgrading iteration of software/firmware versions on line. The method can realize the corresponding remote upgrading function of the software of the robot through an Over-the-Air Technology (OTA) Technology, and improve the upgrading efficiency.
Example one
As shown in fig. 1, a robot remote packaging upgrading method includes the following steps:
determining all package files and version numbers thereof which need to be upgraded by the robot, packaging the package files and the version numbers thereof in the same external member, and storing the package files in a cloud end, wherein the package files are software and hardware files;
the platform issues issuing commands of corresponding suites to the multiple robots of the robot end through the DevOps main server according to the unique serial numbers of the robots;
and after receiving the issuing command of the DevOps main server through a client of the robot, downloading the corresponding package file of the suite from the cloud, and then finishing upgrading.
The robot remote packaging and upgrading method further comprises the following steps: and creating a version dependence map of the robot end.
The operation and maintenance personnel can determine the package files and the version information to be upgraded according to the current package files and the version information of the robot terminal.
In some embodiments, the determination of all package files and version numbers thereof to be upgraded by the robot may also be issued by operation and maintenance personnel as needed, without checking the package files and version numbers thereof of the current robot, and finally, the robot checks whether upgrading is needed after receiving an issuing command and downloading a suite.
In some embodiments, the version dependency graph may be created on the platform and sent along with the package file, or may be pre-designed, for example, written into the upgrade software in advance, without post configuration.
Example two
As shown in fig. 2, the robot remote packaging upgrade method provided is based on the first embodiment and includes the following steps S101 to S105.
Step S101, a platform creates a version dependence map of a robot end, and the software and hardware names and descriptions of the robot end are determined; wherein each software and hardware file may be defined as a package file.
In this step, the version dependency relationship of each software may be detected directly or through historical version information of an application program preset in the platform, and then the software to be upgraded and its version are added to the previous version dependency relationship to generate a version dependency graph.
It should be noted that, in the above description, referring to the software and hardware to be upgraded, the hardware refers to the firmware-driven version upgrade package of the hardware, and the software refers to the application software version upgrade package installed on the hardware platform.
And step S102, the platform receives the package file with the corresponding version number and stores the package file in the cloud.
And step S103, determining all package files and version numbers of the package files required to be upgraded by the robot according to the current package files and version information of the robot end, and placing the package files and the version numbers in the same suite.
In this step, the operator manages the versions of the package files in a unified manner, and it is clear which versions of which packages are required for software upgrade of a plurality of robots at the robot end. The operator creates a suite on the platform, and places specific package files and versions within the same suite. For example, suite A contains V1.0.0 version of software A and V2.0.0 version of software B that are required for some portion of the robot upgrade.
And step S104, the platform issues issuing commands of corresponding suites to the plurality of robots at the robot end through the DevOps main server according to the unique serial numbers of the robots.
In this step, the person who owns the issuing authority performs the issuing action on the platform. Specifically, a plurality of robots in a plurality of sites may be selected, and a suite to be distributed, that is, a package file including all software and hardware specific versions required by the plurality of robots to be distributed, may be selected. After confirming the robot number to be issued and the issued package and version, the platform back end point triggers the cloth button. The platform front end triggers the task to be issued, the issued task is analyzed by a DevOps Master (DevOps Master server), and a plurality of robots in the issued task issue commands and issue the commands by taking a suite as a unit.
It should be noted that DevOps (a combination of Development and Operations) is a collective term for a group of processes, methods and systems for facilitating communication, collaboration and integration between Development (application/software engineering), technical operation and Quality Assurance (QA) departments.
Step S105, after the robot receives the issuing command of the DevOps main server through the client, the corresponding package file of the suite is downloaded from the cloud, and then the upgrading is completed.
In this step, after receiving the command of the DevOps master server, the DevOps Client on the robot downloads all package files containing specific versions in the suite from the cloud, where the package files are all files required by the robot to upgrade corresponding software or hardware, and upgrade is performed after downloading is completed. Further, in the process of upgrading software and hardware, the robot carries out sequential upgrading on the package files in the suite according to the dependency relationship in the version dependency graph. That is, when a plurality of versions exist in a certain software and hardware in the upgrade process, the upgrade is preferentially performed to a bottom layer or a specific version, and then other versions depending on the bottom layer or the specific version are upgraded. It should be noted that, in order to prevent the file from being lost, the robot downloads the package file from the cloud and backs up the service file of the original software after updating.
In one embodiment, after downloading a corresponding suite from a cloud, the robot performs self-checking on the version of the package file in the suite according to an issuing command, determines whether the version of the package file is correct according to the version information reporting time, if not, the robot reports an error through a DevOps main server, a technician performs package and version checking in a platform, and if the platform uploads the package version at the cloud, the robot uploads the correct version again, and then the robot can download the correct package version again.
In one embodiment, the robot remote packaging upgrading method further comprises the following steps: acquiring the current state of the robot and judging whether the upgrading requirement of the package file is met, if so, updating and upgrading according to the kit; and if the result is negative, suspending the updating and upgrading of the external member.
It should be noted that, at present, due to the complex and diverse field environments, the robot needs to be guaranteed to be executed in a specific environment during the upgrading process, so as to improve the success rate of the software upgrading of the robot. For example, if the robot is charged by a charging pile and the electric quantity is higher than the minimum value of the set upgradable software, or the robot does not have the scheduling task of the cloud task and the local scheduling task currently, the robot executes the upgrade task.
Further, the present embodiment further includes the steps of: and judging the priority level of upgrading the package files, suspending the execution of the current task and updating and upgrading on the robot for the package files exceeding the preset level, and executing updating and upgrading after the current task is finished on the robot for the package file tasks not exceeding the preset level.
It can be appreciated that the priority of optimized software and hardware upgrades is not too high and can be upgraded without affecting field use. However, in a special case, the priority is higher, for example, the problem that forced updating of the robot software BUG bypasses part of experience use, the current task is suspended and stored, the updating mode is switched to, and the task updating is finished and then the original task is resumed.
In one embodiment, the robot remote packaging upgrading method further comprises the following steps: after the robot finishes upgrading, the robot automatically reports the current version information of the robot to the DevOps master server, version verification is carried out on the current version information and the version of the package file of the suite, and if the verification result is not matched, the robot reports an error to the DevOps master server. That is, after the robot completes the upgrade, the version information of the software and hardware to be upgraded is updated, the software and hardware version information of the robot should be consistent with the version information of the downloaded package file under normal conditions, if the software and hardware version information of the robot is inconsistent with the version information of the downloaded package file, the software and hardware upgrade failure of the robot is indicated, and at this time, the package file downloaded by the robot may have problems, so that an error is reported to the DevOps main server.
In the above upgrading process inside the robot, the system monitoring software is used as a main executor and a maintainer for switching the upgrading mode, and is responsible for maintaining and switching the local state and mode of the whole robot, and the upgrading task of the robot should not affect the basic operation of the robot body, and generally should not allow the robot to enter the upgrading mode under the normal use condition of a user. The robot upgrade enters a temporary unavailable state for a user when being switched to the upgrade mode. Robot upgrades need to keep power abundant, and if software upgrades are forced to be performed at low power, there is a great risk of failure or damage. Due to the fact that the robot software package is updated under the condition that a cloud new software package is downloaded, the software package is failed to be downloaded under the condition that the current network state is poor, and the task is further failed to be updated.
The method in the above embodiment does not actively detect whether the remote software version is upgradable by the robot body to trigger the upgrade task, but definitely requires that the upgrade task is actively triggered through the cloud end, and the robot local client receives and executes the task, so that the software and hardware upgrade task is completed invisibly.
As an embodiment, the robot packaging and upgrading method in the first embodiment and the second embodiment may also be implemented by after the robot end reports the version abnormality, determining, by an operation and maintenance person, all package files and version numbers thereof that the robot needs to upgrade according to the current package file and version information of the robot end, packaging the package files and the version numbers thereof in the same suite and storing the package files and the version numbers in the cloud, and performing subsequent upgrading steps, which are not described in detail herein.
It should be noted that, in the process of updating and upgrading the software, a corresponding embedded point record with detailed data is stored in each step, and is transmitted back to the OTA cloud through a message queue, so as to store records for subsequent process optimization and tracing.
In the embodiment, the remote packaging and upgrading method for the robot, provided by the invention, includes the steps of placing package files and versions of the package files required by the robot into the same suite in a platform, then issuing an issuing command to a plurality of robots at a robot end through a DevOps main server by the platform, and finally downloading the needed suite from a cloud end by the robot according to the issuing command to complete upgrading of the corresponding package files, so that integrated issuing of upgrading and updating tasks is realized in the platform, the management degree of the platform for task issuing is simplified, and the number of tasks at the cloud end is reduced.
EXAMPLE III
The invention also provides a robot remote packaging and upgrading system which is used for remotely sending the software, hardware and version updating tasks corresponding to the robot to a plurality of robots in the platform so that the robots can remotely complete the software/firmware version upgrading iteration on line. It should be noted that the implementation principle and the implementation mode of the robot remote packaging and upgrading system 100 are consistent with the above-mentioned robot remote packaging and upgrading method, and therefore, the following description is omitted.
As shown in fig. 3, the robot remote packaging upgrade system 100 includes a platform and a robot 10.
The platform comprises a file determining module 20, a file storing module 30, a suite creating module 40 and a command issuing module 50;
the file determining module 20 is configured to determine all package files and version numbers thereof that the robot needs to upgrade, where the package files are software and hardware files;
the file storage module 30 is used for receiving the package file with the corresponding version number and storing the package file in the cloud;
the kit creating module 40 is used for packaging all package files and version numbers thereof which need to be upgraded by the robot and placing the package files and the version numbers in the same kit;
a command issuing module 50, configured to issue issuing commands of corresponding suites to multiple robots at the robot end through the DevOps master server according to the unique serial numbers of the robots;
the robot 10 is configured to download the package file of the corresponding suite from the cloud after receiving the issuing command of the DevOps master server through the client of the robot, and then complete the upgrade.
The robot is internally integrated with a software upgrading module for upgrading software and a version verification module for verifying software versions.
Example four
The invention provides a terminal, which comprises a memory, a processor and a computer program stored in the memory, wherein the computer program realizes the steps of the robot remote packaging and upgrading method according to any one of the above embodiments when being executed by the processor.
EXAMPLE five
The invention provides a computer-readable storage medium, which stores a computer program that, when executed by a processor, implements the steps of the robot remote packaging and upgrading method according to any one of the above embodiments.
EXAMPLE six
The invention provides a computer program product comprising a computer program or instructions which, when executed by a processor, implement the steps of the robot remote packaging upgrade method according to any one of the above embodiments.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
In the embodiments provided in the present invention, it should be understood that the disclosed system or apparatus/terminal device and method can be implemented in other ways. For example, the above-described system or apparatus/terminal device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The invention is not limited solely to that described in the specification and embodiments, and additional advantages and modifications will readily occur to those skilled in the art, so that the invention is not limited to the specific details, representative apparatus, and illustrative examples shown and described herein, without departing from the spirit and scope of the general concept as defined by the appended claims and their equivalents.
Claims (10)
1. A robot remote packaging and upgrading method is characterized by comprising the following steps:
determining all package files and version numbers thereof which need to be upgraded by the robot, packaging the package files and the version numbers thereof in the same external member, and storing the package files in a cloud end, wherein the package files are software and hardware files;
the platform issues issuing commands of corresponding suites to the multiple robots of the robot end through the DevOps main server according to the unique serial numbers of the robots;
and after receiving the issuing command of the DevOps main server through a client of the robot, downloading the corresponding package file of the suite from the cloud, and then finishing upgrading.
2. The robot remote packaging and upgrading method according to claim 1, wherein the robot downloads the corresponding package file of the suite from the cloud after receiving the issuing command of the DevOps master server through its own client, and then completes the upgrading step, including the steps of:
and after downloading the corresponding suite from the cloud end, the robot carries out self-checking on the version of the package file of the suite according to the issuing command, confirms whether the version of the package file is correct or not according to the version information reporting time, and if the result is not, reports an error through the DevOps main server.
3. The robot remote packaging upgrade method according to claim 1, further comprising the steps of:
after the robot finishes upgrading, the robot automatically reports the current version information of the robot to the DevOps master server, version verification is carried out on the current version information and the version of the package file of the suite, and if the verification result is not matched, the robot reports an error to the DevOps master server.
4. The robot remote packaging upgrade method according to claim 1, further comprising the steps of:
acquiring the current state of the robot and judging whether the upgrading requirement of the package file is met, if so, updating the upgrade according to the suite; and if the result is negative, suspending the updating and upgrading of the suite.
5. The robot remote packaging upgrade method of any one of claims 1 to 4,
and the robot carries out sequential upgrading on the package files in the suite according to the dependency relationship in the preset version dependency graph.
6. The robot remote packaging upgrade method according to claim 5, further comprising the steps of:
and judging the priority level of upgrading the package files, suspending the execution of the current task and updating and upgrading on the robot if the package files exceed the preset level, and executing updating and upgrading after the current task is finished on the robot if the package files do not exceed the preset level.
7. A robot remote packaging and upgrading system is characterized by comprising a platform and a robot;
the platform comprises a file determining module, a file storing module, a suite creating module and a command issuing module;
the file determining module is used for determining all package files and version numbers thereof, which need to be upgraded, of the robot, wherein the package files are software and hardware files;
the file storage module is used for receiving the package file with the corresponding version number and storing the package file in the cloud;
the kit creating module is used for packaging all package files and version numbers thereof which need to be upgraded by the robot and placing the package files and the version numbers in the same kit;
the command issuing module is used for issuing commands of corresponding suites to the multiple robots at the robot end through the DevOps main server according to the unique serial numbers of the robots;
and the robot is used for downloading the corresponding package file of the suite from the cloud after receiving the issuing command of the DevOps main server through a client of the robot, and then finishing upgrading.
8. A terminal, characterized in that the terminal comprises a memory, a processor and a computer program stored in the memory, which computer program, when executed by the processor, performs the steps of the robot remote packaging upgrade method according to any of the claims 1-6.
9. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which, when executed by a processor, performs the steps of the robot remote packaging upgrade method according to any one of claims 1-6.
10. A computer program product comprising a computer program or instructions which, when processed and executed, implement the steps of the robot remote packaging upgrade method according to any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111440005.2A CN114090049A (en) | 2021-11-30 | 2021-11-30 | Robot remote packaging and upgrading method and system and related products |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111440005.2A CN114090049A (en) | 2021-11-30 | 2021-11-30 | Robot remote packaging and upgrading method and system and related products |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114090049A true CN114090049A (en) | 2022-02-25 |
Family
ID=80305681
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111440005.2A Pending CN114090049A (en) | 2021-11-30 | 2021-11-30 | Robot remote packaging and upgrading method and system and related products |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114090049A (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105302613A (en) * | 2015-11-23 | 2016-02-03 | 武汉烽火网络有限责任公司 | Method and system for updating EOC software by adopting combined files |
| CN110737453A (en) * | 2019-10-17 | 2020-01-31 | 北京智芯微电子科技有限公司 | Security chip upgrading method and device and security chip |
| CN110837388A (en) * | 2020-01-09 | 2020-02-25 | 炬星科技（深圳）有限公司 | Software upgrading method of robot, upgrading server, robot and storage medium |
| CN110851157A (en) * | 2019-10-28 | 2020-02-28 | 上海旗旌科技有限公司 | Method and equipment for updating vehicle-mounted terminal equipment system |
| CN111381842A (en) * | 2018-12-27 | 2020-07-07 | 深圳市优必选科技有限公司 | Robot upgrading method, electronic equipment and server |
| CN111796849A (en) * | 2020-07-14 | 2020-10-20 | 深圳市智莱科技股份有限公司 | Firmware remote upgrading method and device |
| CN113326053A (en) * | 2021-06-18 | 2021-08-31 | 上海钛米机器人股份有限公司 | Robot management system and method |
| CN113467811A (en) * | 2021-07-27 | 2021-10-01 | 中国银行股份有限公司 | Intelligent counter terminal version upgrading system and working method thereof |
-
2021
- 2021-11-30 CN CN202111440005.2A patent/CN114090049A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105302613A (en) * | 2015-11-23 | 2016-02-03 | 武汉烽火网络有限责任公司 | Method and system for updating EOC software by adopting combined files |
| CN111381842A (en) * | 2018-12-27 | 2020-07-07 | 深圳市优必选科技有限公司 | Robot upgrading method, electronic equipment and server |
| CN110737453A (en) * | 2019-10-17 | 2020-01-31 | 北京智芯微电子科技有限公司 | Security chip upgrading method and device and security chip |
| CN110851157A (en) * | 2019-10-28 | 2020-02-28 | 上海旗旌科技有限公司 | Method and equipment for updating vehicle-mounted terminal equipment system |
| CN110837388A (en) * | 2020-01-09 | 2020-02-25 | 炬星科技（深圳）有限公司 | Software upgrading method of robot, upgrading server, robot and storage medium |
| CN111796849A (en) * | 2020-07-14 | 2020-10-20 | 深圳市智莱科技股份有限公司 | Firmware remote upgrading method and device |
| CN113326053A (en) * | 2021-06-18 | 2021-08-31 | 上海钛米机器人股份有限公司 | Robot management system and method |
| CN113467811A (en) * | 2021-07-27 | 2021-10-01 | 中国银行股份有限公司 | Intelligent counter terminal version upgrading system and working method thereof |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101411123B (en) | Method, system and computer program for the centralized system management on endpoints of a distributed data processing system | |
| CN107566165B (en) | Method and system for discovering and deploying available resources of power cloud data center | |
| US20150100829A1 (en) | Method and system for selecting and executing test scripts | |
| US20150100832A1 (en) | Method and system for selecting and executing test scripts | |
| CN109298868B (en) | Intelligent dynamic deployment and uninstallation method for mapping image data processing software | |
| CN113569987A (en) | Model training method and device | |
| US20150100830A1 (en) | Method and system for selecting and executing test scripts | |
| US8775552B1 (en) | Methods and systems for distribution of technical manuals | |
| CN111324599B (en) | Block chain experiment system and management method | |
| US20150100831A1 (en) | Method and system for selecting and executing test scripts | |
| CN108052336A (en) | A kind of distributed software upgrade-system and its implementation | |
| CN112230987B (en) | Distributed modular plug-in frame realization system and method | |
| CN109558147A (en) | A kind of continuous integrating platform construction method based on Jenkins and Gitlab | |
| CN111984373B (en) | Method and system for guaranteeing environment consistency in Kubernetes container environment | |
| CN113783953A (en) | Industrial Internet of things network management and control method and system based on cloud edge cooperation | |
| CN114237632A (en) | Hybrid cloud automatic operation and maintenance release system and operation method thereof | |
| CN113434180B (en) | Data processing method and device for application, server and storage medium | |
| CN111324365A (en) | Method and equipment for upgrading super-converged system | |
| CN113296795A (en) | Application deployment method, device, equipment, storage medium and program product | |
| CN109739539A (en) | Application dissemination method, device, equipment and the storage medium of Cross-environment | |
| CN114090050A (en) | Robot software remote automatic updating method, system and related products | |
| CN113157297A (en) | Charging station equipment remote upgrading method and system | |
| CN114090049A (en) | Robot remote packaging and upgrading method and system and related products | |
| CN112035124A (en) | Application deployment method and device | |
| CN113568842B (en) | Automatic testing method and system for batch tasks |
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 |