CN108897570B - Version compatibility method based on cloud computing and artificial intelligence and robot system - Google Patents
Version compatibility method based on cloud computing and artificial intelligence and robot system Download PDFInfo
- Publication number
- CN108897570B CN108897570B CN201810632876.6A CN201810632876A CN108897570B CN 108897570 B CN108897570 B CN 108897570B CN 201810632876 A CN201810632876 A CN 201810632876A CN 108897570 B CN108897570 B CN 108897570B
- Authority
- CN
- China
- Prior art keywords
- software
- file
- conversion
- version
- preset
- 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.)
- Active
Links
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
Abstract
The version compatible method based on cloud computing and artificial intelligence and the robot system comprise the following steps: judging whether the version of the file to be opened by the user is consistent with the software version of the user side, if not, sending the file to the cloud, converting the file into the file consistent with the local software version at the cloud, sending the converted version to the user side, and opening the file by using the software of the user side. The method and the system enable files with inconsistent versions to be opened at the user side without installing software with different versions at the user side by a user, thereby saving the time of the user, improving the working efficiency of the user, improving the software use experience of the user and improving the performance and efficiency of the user side.
Description
Technical Field
The invention relates to the technical field of information, in particular to a version compatibility method based on cloud computing and artificial intelligence and a robot system.
Background
The complete version number defines three items: < major version number > < minor version number > < revision version number >, such as 1.0.0. Version number upgrading principle: major version number: there are large variations of functional modules, such as adding multiple modules or changes in the overall architecture. Minor version number: upgrades of minor version numbers correspond to only local changes, as opposed to major versions. However, the local change causes incompatibility of the program with the previous version, or causes damage to the previous cooperation relationship of the program, or causes great improvement or enhancement in the function. Revision version number: the local change is mainly the function improvement of the local function, or the correction of the bug, or the expansion of the function. In principle, revision version numbers will change frequently after release from the first stable version, whereas minor version numbers will change as the case may be, with major version numbers changing less frequently unless there is a major reconfiguration or functional improvement. For small items, it can even be simplified to: < minor version number > < revision version number >.
Compatibility, the difference between upward compatibility and downward compatibility. A new version is backwards compatible in that it can support an old version. The new version may sometimes be downward compatible, but many times the old code needs to be abandoned, and the old client needs to find an old version dll that is compatible with the new version. I.e. a branched version is generated. Second, the upward compatibility is that the old version can be compatible with the new version. If the downward compatibility is complete, the branch version does not have to be generated. If the old version is compatible with the new version, the new version does not add an interface, but shrinks the interface. This is also a factor in generating versions. Generally, downward compatibility is more, for example, win7 is software under the xp system.
In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art: the new version may support several relatively old versions, the old version may not support the new version, and the old version supports the new version more difficultly, because the old version is designed without considering what interface the new version may add, which results in incompatibility between different versions, and causes great inconvenience for users, the user often installs version a on his device without opening files generated on another version B, and needs to spend a lot of time searching, downloading, installing the software of version B, and after installing the software of version B, the user may not open the software of version a or the software of version C, thereby causing great trouble to the user, wasting the user's time, affecting the use of the software by the user, and reducing the user experience. Moreover, if a user needs to install different versions of software or even all versions of software on the user terminal to support various versions of files, a lot of storage resources and computing resources are occupied on the user terminal, which may slow down the computer on the user terminal, thereby reducing the performance and efficiency of the user terminal. What makes users feel more difficult is that different versions conflict with each other sometimes, the software of version B must be installed before the software of version A is unloaded, the software of version B cannot open the file which can be opened by the software of version A, and the software of version A cannot open the file which can be opened by the software of version B, so that the use of the software by the users is seriously influenced, and the software use experience and the working efficiency of the users are greatly reduced.
Accordingly, there is a need for improvements and developments in the art.
Disclosure of Invention
Based on this, it is necessary to provide a version compatible method and a robot system based on cloud computing and artificial intelligence aiming at the defects or shortcomings of software versions in the prior art, so as to solve the defects of low version compatible efficiency and poor user experience in the prior art, improve the intelligence and efficiency of version compatibility, save the time of a user, improve the working efficiency of the user, improve the software use experience of the user, and improve the performance and efficiency of a user side.
In a first aspect, an embodiment of the present invention provides a version compatibility method, where the method includes:
judging whether the software version corresponding to the first file which needs to be opened by the user is consistent with the software version of the user side: if not, executing a conversion step;
and a conversion step, namely sending the first file and the version information of the user side software to a preset cloud end, calling preset conversion software at the preset cloud end to convert the first file into a second file supported by the version of the user side software, and sending the second file to the user side from the preset cloud end.
Preferably, the converting step is preceded by:
a first acquisition step, acquiring software and version information of a user side;
a second obtaining step of obtaining a software name and a first version number corresponding to the software and version information;
a third obtaining step of obtaining a second version number of the software;
a conversion acquiring step of acquiring conversion software capable of converting a file type supported by the first version of the software into a file type supported by the second version of the software, and using the conversion software as preset conversion software;
downloading software, namely downloading the preset conversion software at the preset cloud end;
installing software, namely installing the preset conversion software on the preset cloud;
and a knowledge storage step, namely correspondingly storing the software name, the first version number, the second version number and the preset conversion software into a software conversion knowledge base.
Preferably, the converting step is followed by:
and an opening step, calling the software of the user side to open the second file.
Preferably, the opening step is followed by:
and a reverse conversion step, namely judging whether the user closes the second file: the second file is sent to a preset cloud end, preset conversion software is called at the preset cloud end to convert the second file into a third file which is consistent with the first file in version, and the third file is sent to the user end from the preset cloud end.
Preferably, the inverse transformation step is followed by:
and updating, namely replacing the first file with the third file at the user side.
In a second aspect, an embodiment of the present invention provides a version compatible system, where the system includes:
the judging module is used for judging whether the software version corresponding to the first file which needs to be opened by the user is consistent with the software version of the user side: if not, executing a conversion module;
the conversion module is used for sending the first file and the version information of the user side software to a preset cloud end, calling preset conversion software at the preset cloud end to convert the first file into a second file supported by the version of the user side software, and sending the second file to the user side from the preset cloud end.
Preferably, the system further comprises:
the first acquisition module is used for acquiring software and version information of a user side;
the second acquisition module acquires the software name and the first version number corresponding to the software and version information;
the third obtaining module is used for obtaining a second version number of the software;
a conversion acquisition module for acquiring conversion software capable of converting a file type supported by the first version of the software into a file type supported by the second version of the software, and using the conversion software as preset conversion software;
a downloading software module, which downloads the preset conversion software at the preset cloud;
the installation software module is used for installing the preset conversion software at the preset cloud end;
and the knowledge storage module is used for correspondingly storing the software name, the first version number, the second version number and the preset conversion software into a software conversion knowledge base.
Preferably, the system further comprises:
and the opening module calls the software of the user side to open the second file.
Preferably, the system further comprises:
the reverse conversion module is used for judging whether the user closes the second file: the second file is sent to a preset cloud end, preset conversion software is called at the preset cloud end to convert the second file into a third file which is consistent with the first file in version, and the third file is sent to the user end from the preset cloud end.
And the updating module is used for replacing the first file with the third file at the user side.
In a third aspect, embodiments of the present invention provide robot systems, in which the version-compatible systems according to any one of the second aspects are respectively configured.
The embodiment of the invention has the following advantages and beneficial effects:
the version compatible method based on cloud computing and artificial intelligence and the robot system provided by the embodiment of the invention judge whether the version of the file to be opened by the user is consistent with the software version of the user side, if not, the file is sent to the cloud side, the file is converted into the file with the consistent version with the local software version at the cloud side, the converted version is sent to the user side and is opened by using the software of the user side, so that the file with the inconsistent version can be opened at the user side without installing the software of different versions by the user, the time of the user is saved, the working efficiency of the user is improved, and the software use experience of the user is improved. And because the software of all versions is installed in the cloud, file conversion is also carried out on the cloud, the installation and operation of various versions of software do not occupy the storage resource and the computing resource of the user terminal, the conversion of files of different versions is also carried out in the cloud, and the memory and the CPU of the user terminal are not consumed, so that a user does not need to install software of multiple versions or even all versions on the user terminal, and the performance and the efficiency of the user terminal can be greatly improved.
Drawings
Fig. 1 is a flowchart of version compatibility according to embodiment 1 of the present invention;
fig. 2 is a flowchart of version compatibility according to embodiment 2 of the present invention;
fig. 3 is a flowchart of version compatibility according to embodiment 3 of the present invention;
fig. 4 is a flowchart of version compatibility provided in embodiment 4 of the present invention;
fig. 5 is a flowchart of version compatibility provided in embodiment 5 of the present invention;
fig. 6 is a schematic block diagram of a version compatible system provided in embodiment 6 of the present invention;
fig. 7 is a schematic block diagram of a version compatible system provided in embodiment 7 of the present invention;
fig. 8 is a schematic block diagram of a version compatible system provided in embodiment 8 of the present invention;
fig. 9 is a schematic block diagram of a version compatible system provided in embodiment 9 of the present invention.
Detailed Description
The technical solutions in the examples of the present invention are described in detail below with reference to the embodiments of the present invention.
The embodiment of the invention provides a version compatible method based on cloud computing and artificial intelligence and a robot system. The cloud computing technology comprises installation and operation of cloud software; the artificial intelligence technology comprises matching between different software and versions thereof, and also comprises establishing and using a knowledge base.
Embodiment 1, a version compatibility method, as shown in fig. 1, the method includes:
a determining step S210, determining whether the software version corresponding to the first file that the user needs to open is consistent with the software version at the user side: otherwise, executing the conversion step. Preferably, acquiring a software version number corresponding to a first file which needs to be opened by a user; judging whether a user side is provided with software corresponding to a first file which needs to be opened by the user; if the software is not installed, the software is automatically downloaded and installed at a user side; if the software is installed, acquiring the version number of the software installed at the user side; judging whether a software version number corresponding to a first file which needs to be opened by a user is consistent with a version number of the software installed at the user side; if the first file is consistent with the second file, the first file is opened by the software installed on the user side; if not, a conversion step is performed. For example, if the first file is a docx file, the corresponding software version is word2013, and the software version of the user side is word2003, the user side cannot open the file and needs to perform the conversion step.
A conversion step S220, sending the first file and the client software version information to a preset cloud, calling a preset conversion software at the preset cloud to convert the first file into a second file supported by the client software version, and sending the second file from the preset cloud to the client. Preferably, the cloud end is pre-installed with required file conversion software; the first file is sent from a user side to the cloud side; the user side comprises a mobile phone or a computer of a user; the cloud end comprises a cloud server, can be a public cloud such as Aliyun, tencent cloud or Huacheng cloud, or a private cloud, and is in network connection with the user end through a local area network; after receiving the first file and the user side software version information, the cloud acquires a software name and a version number corresponding to the first file, retrieves preset conversion software corresponding to the software name and the version number corresponding to the first file and the user side software version information from a software conversion knowledge base preset by the cloud, namely, the correlation information of each conversion software in the software conversion knowledge base is matched with the software name and the version number corresponding to the first file and the user side software version information, and if the matching is successful, the preset conversion software is called at the cloud to convert the first file into a second file; the associated information of the preset conversion software in the software conversion knowledge base comprises a software name, a first version number and a second version number, wherein the software name is the name of the software corresponding to a file which can be converted by the preset conversion software, and the preset conversion software can convert the file corresponding to the first version number of the software into a file corresponding to the second version number of the software; when the associated information of each piece of preset conversion software in the software conversion knowledge base is matched with the software name and version number corresponding to the first file and the version information of the user-side software, whether the software name corresponding to the first file is consistent with the software name associated with each piece of preset conversion software or not is judged, if not, matching fails, if so, whether the software version number corresponding to the first file is consistent with the first version number associated with each piece of preset conversion software or not is continuously judged, if not, matching fails, if so, whether the user-side software version number is consistent with the second version number associated with each piece of preset conversion software or not is continuously judged, if not, matching fails, and if so, matching succeeds.
Preferably, when the software conversion knowledge base does not retrieve the preset conversion software corresponding to the software name and version number corresponding to the first file and the user-side software version information, S110 to S170 are executed, the required preset conversion software is downloaded and installed to the cloud, and the information of the preset conversion software and the related information thereof are added to the software conversion knowledge base.
Embodiment 2 and the version compatible method according to embodiment 1, as shown in fig. 2, before the converting step S220, the method includes:
the first obtaining step S110 is to obtain software and version information of the user terminal.
A second obtaining step S120, obtaining a software name and a first version number corresponding to the software and version information.
A third obtaining step S130, obtaining a second version number of the software.
A conversion acquiring step S140 of acquiring conversion software capable of converting the file type supported by the first version of the software into the file type supported by the second version of the software, and using the conversion software as preset conversion software.
And a step S150 of downloading software, namely downloading the preset conversion software at the preset cloud.
And a software installing step S160, installing the preset conversion software at the preset cloud.
A knowledge storage step S170, correspondingly storing the software name, the first version number, the second version number, and the preset conversion software into a software conversion knowledge base.
Preferably, S110 to S170 may also be executed after S210 and before S220, and at this time, when the user needs to perform conversion of what type of file, the corresponding conversion software is installed in the cloud, and it is not necessary to install all versions of software in the cloud in advance, so that resource occupation on the cloud can be reduced, and resource utilization rate of the cloud is improved; the method comprises the steps of obtaining software and version information needing to be opened by a user side and software version information installed by the user side in S110, taking the version number of the software needing to be opened by the user side as a first version number in S120, taking the software version number installed by the user side as a second version number in S130, executing S140 to S170 to obtain preset conversion software corresponding to the software name, the first version number and the second version number, namely obtaining the preset conversion software capable of converting a first file into a second file supported by the software version of the user side, and installing the preset conversion software to the cloud.
Preferably, S110 to S170 are performed before S210; the method comprises the steps of obtaining software and version numbers of supported existing files corresponding to existing files of a user end in S110, if the supported software of the existing files is not installed, installing the supported software of the existing files, if the supported software of the existing files is installed on the user end, obtaining the version number of the installed software of the user end, if the version number of the installed software is not consistent with the version number of the supported software of the existing files, taking the version number of the supported software of the existing files as a first version number in S120, taking the version number of the installed software as a second version number in S130, and then executing S140 to S170 to obtain the software, the first version number and the preset conversion software corresponding to the second version number, namely obtaining the preset conversion software capable of converting the existing files into second files supported by the software version installed on the user end and installing the preset conversion software into the cloud end.
Embodiment 3, according to the version compatible method described in embodiment 1, as shown in fig. 3, after the converting step S220, the method includes:
and an opening step S230, calling the software of the user side to open the second file. Preferably, the software supporting the second file at the user end is called, and because the second file generated by conversion in the conversion step S220 is the second file supported by the software version at the user end, there must be a software version capable of opening the second file.
Embodiment 4 and the version compatible method according to embodiment 3, as shown in fig. 4, after the opening step S230, the method includes:
the reverse conversion step S240 determines whether the user has closed the second file: the second file is sent to a preset cloud end, preset conversion software is called at the preset cloud end to convert the second file into a third file which is consistent with the first file in version, and the third file is sent to the user end from the preset cloud end. Preferably, the specific process is the same as the converting step S220, and is not described again.
Preferably, in S140, the method further includes obtaining conversion software for converting the file type supported by the second version of the software into the file type supported by the first version of the software.
Embodiment 5 and the version compatible method according to embodiment 4, as shown in fig. 5, after the inverse conversion step S240, the method includes:
an updating step S250, replacing the first file with the third file at the user side. Preferably, the first file is deleted and then the third file is renamed to the first file.
Embodiment 6, a version compatible system, as shown in fig. 6, the system includes:
the determining module 210 determines whether the software version corresponding to the first file that the user needs to open is consistent with the software version at the user side: otherwise, executing the conversion module.
The conversion module 220 sends the first file and the client software version information to a preset cloud, calls preset conversion software at the preset cloud to convert the first file into a second file supported by the client software version, and sends the second file from the preset cloud to the client.
The preferred embodiment of example 6 corresponds to and is similar to the preferred embodiment of example 1, and is not described again.
Embodiment 7, the version compatible system according to embodiment 6, as shown in fig. 7, the system further includes:
the first obtaining module 110 obtains software and version information of the user terminal.
The second obtaining module 120 obtains the software name and the first version number corresponding to the software and version information.
And a third obtaining module 130, obtaining a second version number of the software.
The conversion obtaining module 140 obtains conversion software capable of converting the file type supported by the first version of the software into the file type supported by the second version of the software, and uses the conversion software as preset conversion software.
And a software downloading module 150 configured to download the preset conversion software at the preset cloud.
And the installation software module 160 is used for installing the preset conversion software at the preset cloud end.
The knowledge storage module 170 correspondingly stores the software name, the first version number, the second version number, and the preset conversion software into a software conversion knowledge base.
The preferred embodiment of example 7 corresponds to and is similar to the preferred embodiment of example 2, and is not described again.
Embodiment 8, the version compatible system according to embodiment 6, as shown in fig. 8, the system further includes:
the opening module 230 calls the software of the user side to open the second file.
The preferred embodiment of example 8 corresponds to and is similar to the preferred embodiment of example 3, and is not described again.
Embodiment 9, the version compatible system according to embodiment 8, as shown in fig. 9, the system further includes:
the reverse conversion module 240 determines whether the user has closed the second file: the second file is sent to a preset cloud end, preset conversion software is called at the preset cloud end to convert the second file into a third file which is consistent with the first file in version, and the third file is sent to the user end from the preset cloud end.
And an updating module 250 for replacing the first file with the third file at the user terminal.
The preferred embodiment of example 9 corresponds to and is similar to the preferred embodiments of examples 4 and 5, and is not described again.
Embodiment 10, a robot system in which the version-compatible systems according to any one of embodiments 6 to 9 are respectively arranged.
The preferred embodiment of example 10 corresponds to and is similar to the preferred embodiments of examples 6-9, and is not described again.
The version compatible method based on cloud computing and artificial intelligence and the robot system provided by the embodiment of the invention judge whether the version of the file to be opened by the user is consistent with the software version of the user side, if not, the file is sent to the cloud side, the file is converted into the file with the consistent version with the local software version at the cloud side, the converted version is sent to the user side and is opened by using the software of the user side, so that the file with the inconsistent version can be opened at the user side without installing the software of different versions by the user, the time of the user is saved, the working efficiency of the user is improved, and the software use experience of the user is improved. And because the software of all versions is installed in the cloud, file conversion is also carried out on the cloud, the installation and operation of various versions of software do not occupy the storage resource and the computing resource of the user terminal, the conversion of files of different versions is also carried out in the cloud, and the memory and the CPU of the user terminal are not consumed, so that a user does not need to install software of multiple versions or even all versions on the user terminal, and the performance and the efficiency of the user terminal can be greatly improved.
The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (5)
1. A version compatibility method, the method comprising:
judging whether the software version corresponding to the first file which needs to be opened by the user is consistent with the software version of the user side: if not, executing a conversion step;
a conversion step, namely sending the first file and the version information of the user-side software to a preset cloud end, calling preset conversion software at the preset cloud end to convert the first file into a second file supported by the version of the user-side software, and sending the second file to the user side from the preset cloud end;
the conversion step specifically comprises: after receiving the first file and the user-side software version information, the cloud acquires a software name and a version number corresponding to the first file, retrieves preset conversion software corresponding to the software name and the version number corresponding to the first file and the user-side software version information from a cloud-preset software conversion knowledge base, namely, the association information of each conversion software in the software conversion knowledge base is matched with the software name and the version number corresponding to the first file and the user-side software version information, and if the matching is successful, the preset conversion software is called at the cloud to convert the first file into a second file; the associated information of the preset conversion software in the software conversion knowledge base comprises a software name, a first version number and a second version number, wherein the software name is the name of the software corresponding to a file which can be converted by the preset conversion software, and the preset conversion software can convert the file corresponding to the first version number of the software into a file corresponding to the second version number of the software; when the associated information of each piece of preset conversion software in the software conversion knowledge base is matched with the software name and version number corresponding to a first file and the version information of user-side software, judging whether the software name corresponding to the first file is consistent with the software name associated with each piece of preset conversion software, if not, the matching fails, if so, continuously judging whether the software version number corresponding to the first file is consistent with the first version number associated with each piece of preset conversion software, if not, the matching fails, if so, continuously judging whether the user-side software version number is consistent with the second version number associated with each piece of preset conversion software, if not, the matching fails, and if so, the matching succeeds; when the software conversion knowledge base does not retrieve the preset conversion software corresponding to the software name and version number corresponding to the first file and the user side software version information, downloading and installing the required preset conversion software to a cloud end, and adding the information of the preset conversion software and the related information thereof to the software conversion knowledge base;
an opening step, namely calling software of the user side to open the second file;
and a reverse conversion step, namely judging whether the user closes the second file: if yes, sending the second file to a preset cloud end, calling preset conversion software at the preset cloud end to convert the second file into a third file with the version consistent with that of the first file, and sending the third file to the user end from the preset cloud end;
the reverse conversion step specifically comprises: after the cloud receives the second file and the user-side software version information, acquiring a software name and a version number corresponding to the second file, retrieving preset conversion software corresponding to the software name and the version number corresponding to the second file and the user-side software version information from a cloud preset software conversion knowledge base, namely matching the associated information of every two pieces of conversion software in the software conversion knowledge base with the software name and the version number corresponding to the second file and the user-side software version information, and calling the preset conversion software at the cloud to convert the second file into a third file if the matching is successful; the associated information of the preset conversion software in the software conversion knowledge base comprises a software name, a second version number and a third version number, wherein the software name is the name of the software corresponding to a file which can be converted by the preset conversion software, and the preset conversion software can convert the file corresponding to the second version number of the software into the file corresponding to the third version number of the software; when the associated information of every two pieces of preset conversion software in the software conversion knowledge base is matched with the software name and the version number corresponding to the second file and the user side software version information, judging whether the software name corresponding to the second file is consistent with the software name associated with every two pieces of preset conversion software or not, if not, the matching fails, if so, continuously judging whether the software version number corresponding to the second file is consistent with the second version number associated with every two pieces of preset conversion software or not, if not, the matching fails, if so, continuously judging whether the user side software version number is consistent with the third version number associated with every two pieces of preset conversion software or not, if not, the matching fails, and if so, the matching succeeds; when the software conversion knowledge base does not retrieve the preset conversion software corresponding to the software name and version number corresponding to the second file and the user side software version information, downloading and installing the required preset conversion software to a cloud end, and adding the information of the preset conversion software and the related information thereof to the software conversion knowledge base;
and updating, namely replacing the first file with the third file at the user side.
2. The version compatibility method according to claim 1, wherein said converting step is preceded by:
a first acquisition step, acquiring software and version information of a user side;
a second obtaining step of obtaining a software name and a first version number corresponding to the software and version information;
a third obtaining step of obtaining a second version number of the software;
a conversion acquiring step of acquiring conversion software capable of converting the file type supported by the first version of the software into the file type supported by the second version of the software, and using the conversion software as preset conversion software;
downloading software, namely downloading the preset conversion software at the preset cloud end;
installing software, namely installing the preset conversion software at the preset cloud end;
and a knowledge storage step, namely correspondingly storing the software name, the first version number, the second version number and the preset conversion software into a software conversion knowledge base.
3. A version compatible system, the system comprising:
the judging module is used for judging whether the software version corresponding to the first file which needs to be opened by the user is consistent with the software version of the user side: if not, executing the conversion module;
the conversion module is used for sending the first file and the version information of the user-side software to a preset cloud end, calling preset conversion software at the preset cloud end to convert the first file into a second file supported by the version of the user-side software, and sending the second file to the user side from the preset cloud end; the conversion module specifically comprises: after receiving the first file and the user side software version information, the cloud acquires a software name and a version number corresponding to the first file, retrieves preset conversion software corresponding to the software name and the version number corresponding to the first file and the user side software version information from a software conversion knowledge base preset by the cloud, namely, the correlation information of each conversion software in the software conversion knowledge base is matched with the software name and the version number corresponding to the first file and the user side software version information, and if the matching is successful, the preset conversion software is called at the cloud to convert the first file into a second file; the association information of the preset conversion software in the software conversion knowledge base comprises a software name, a first version number and a second version number, wherein the software name is the name of the software corresponding to a file which can be converted by the preset conversion software, and the preset conversion software can convert the file corresponding to the first version number of the software into a file corresponding to the second version number of the software; when the associated information of each piece of preset conversion software in the software conversion knowledge base is matched with the software name and version number corresponding to a first file and the version information of user-side software, judging whether the software name corresponding to the first file is consistent with the software name associated with each piece of preset conversion software, if not, the matching fails, if so, continuously judging whether the software version number corresponding to the first file is consistent with the first version number associated with each piece of preset conversion software, if not, the matching fails, if so, continuously judging whether the user-side software version number is consistent with the second version number associated with each piece of preset conversion software, if not, the matching fails, and if so, the matching succeeds; when the software conversion knowledge base does not retrieve the preset conversion software corresponding to the software name and version number corresponding to the first file and the version information of the user-side software, downloading and installing the required preset conversion software to a cloud end, and adding the information of the preset conversion software and the associated information thereof to the software conversion knowledge base; the opening module is used for calling the software of the user side to open the second file;
the reverse conversion module is used for judging whether the user closes the second file: if so, sending the second file to a preset cloud end, calling preset conversion software at the preset cloud end to convert the second file into a third file with the version consistent with that of the first file, and sending the third file to the user end from the preset cloud end; the inverse transformation module specifically comprises: after the cloud receives the second file and the user-side software version information, acquiring a software name and a version number corresponding to the second file, retrieving preset conversion software corresponding to the software name and the version number corresponding to the second file and the user-side software version information from a cloud preset software conversion knowledge base, namely matching the associated information of every two pieces of conversion software in the software conversion knowledge base with the software name and the version number corresponding to the second file and the user-side software version information, and calling the preset conversion software at the cloud to convert the second file into a third file if the matching is successful; the associated information of the preset conversion software in the software conversion knowledge base comprises a software name, a second version number and a third version number, wherein the software name is the name of the software corresponding to a file which can be converted by the preset conversion software, and the preset conversion software can convert the file corresponding to the second version number of the software into the file corresponding to the third version number of the software; when the associated information of every two pieces of preset conversion software in the software conversion knowledge base is matched with the software name and the version number corresponding to the second file and the version information of the user-side software, judging whether the software name corresponding to the second file is consistent with the software name associated with every two pieces of preset conversion software or not, if not, the matching fails, if so, continuously judging whether the software version number corresponding to the second file is consistent with the second version number associated with every two pieces of preset conversion software or not, if not, the matching fails, if so, continuously judging whether the user-side software version number is consistent with the third version number associated with every two pieces of preset conversion software or not, if not, the matching fails, and if so, the matching succeeds; when the software conversion knowledge base does not retrieve the preset conversion software corresponding to the software name and version number corresponding to the second file and the user side software version information, downloading and installing the required preset conversion software to a cloud end, and adding the information of the preset conversion software and the related information thereof to the software conversion knowledge base;
and the updating module is used for replacing the first file with the third file at the user side.
4. The version compatible system of claim 3, further comprising:
the first acquisition module is used for acquiring software and version information of a user side;
the second acquisition module is used for acquiring the software name and the first version number corresponding to the software and version information;
the third acquisition module acquires a second version number of the software;
the conversion acquisition module is used for acquiring conversion software capable of converting the file type supported by the first version of the software into the file type supported by the second version of the software, and taking the conversion software as preset conversion software; a downloading software module, which downloads the preset conversion software at the preset cloud;
the installation software module is used for installing the preset conversion software on the preset cloud end;
and the knowledge storage module is used for correspondingly storing the software name, the first version number, the second version number and the preset conversion software into a software conversion knowledge base.
5. A robot system, characterized in that the robot is provided therein with version-compatible systems according to any one of claims 3-4, respectively.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810632876.6A CN108897570B (en) | 2018-06-20 | 2018-06-20 | Version compatibility method based on cloud computing and artificial intelligence and robot system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810632876.6A CN108897570B (en) | 2018-06-20 | 2018-06-20 | Version compatibility method based on cloud computing and artificial intelligence and robot system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108897570A CN108897570A (en) | 2018-11-27 |
| CN108897570B true CN108897570B (en) | 2023-01-03 |
Family
ID=64345010
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810632876.6A Active CN108897570B (en) | 2018-06-20 | 2018-06-20 | Version compatibility method based on cloud computing and artificial intelligence and robot system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108897570B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109582351B (en) * | 2019-01-09 | 2021-10-29 | 江西理工大学应用科学学院 | Version compatibility method based on cloud computing and artificial intelligence and robot system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103559052A (en) * | 2006-07-26 | 2014-02-05 | 戴尔产品有限公司 | Apparatus and methods for updating firmware |
| CN103853581A (en) * | 2012-12-04 | 2014-06-11 | 国际商业机器公司 | Software version management system and method |
| CN103902299A (en) * | 2012-12-24 | 2014-07-02 | 航天信息股份有限公司 | Software version updating method and system |
| CN106126679A (en) * | 2016-06-29 | 2016-11-16 | 江苏电力信息技术有限公司 | A kind of exploitation O&M application process of cloud service-oriented |
| CN107666460A (en) * | 2016-07-27 | 2018-02-06 | 真相网络科技（北京）有限公司 | Long-distance intelligent evidence-obtaining system and method based on mobile Internet |
| CN107943503A (en) * | 2017-12-07 | 2018-04-20 | 畅捷通信息技术股份有限公司 | The upgrade method of mobile application and the upgrade-system of mobile application |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10783504B2 (en) * | 2010-02-26 | 2020-09-22 | Red Hat, Inc. | Converting standard software licenses for use in cloud computing environments |
| US10275505B2 (en) * | 2014-06-24 | 2019-04-30 | Adobe Inc. | In-application conversion of file versions using cloud services |
| CN104965712B (en) * | 2015-07-17 | 2018-04-20 | 北京奇虎科技有限公司 | Application program method for reinforcing and protecting, device and mobile terminal |
| CN106874004B (en) * | 2017-02-21 | 2020-08-21 | 广州视源电子科技股份有限公司 | Method for enabling low-version software to be compatible with high-version file, client and server |
-
2018
- 2018-06-20 CN CN201810632876.6A patent/CN108897570B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103559052A (en) * | 2006-07-26 | 2014-02-05 | 戴尔产品有限公司 | Apparatus and methods for updating firmware |
| CN103853581A (en) * | 2012-12-04 | 2014-06-11 | 国际商业机器公司 | Software version management system and method |
| CN103902299A (en) * | 2012-12-24 | 2014-07-02 | 航天信息股份有限公司 | Software version updating method and system |
| CN106126679A (en) * | 2016-06-29 | 2016-11-16 | 江苏电力信息技术有限公司 | A kind of exploitation O&M application process of cloud service-oriented |
| CN107666460A (en) * | 2016-07-27 | 2018-02-06 | 真相网络科技（北京）有限公司 | Long-distance intelligent evidence-obtaining system and method based on mobile Internet |
| CN107943503A (en) * | 2017-12-07 | 2018-04-20 | 畅捷通信息技术股份有限公司 | The upgrade method of mobile application and the upgrade-system of mobile application |
Non-Patent Citations (2)
| Title |
|---|
| Combined method of automated temporal information acquisition for development of knowledge bases of intelligent systems;G. V. Rybina 等;《2017 2nd International Conference on Knowledge Engineering and Applications (ICKEA)》;20171211;123-127 * |
| UML模型到OWL本体知识库的转换研究;冉婕 等;《电子设计工程》;20170623;第25卷(第07期);24-26,30 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108897570A (en) | 2018-11-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10235149B2 (en) | Preinstalled application management method for mobile terminal and mobile terminal | |
| US9092286B2 (en) | System to automatically process components on a device | |
| US9519654B2 (en) | Method, device, processing center and system for desktop synchronization | |
| JP5248657B2 (en) | System for registry-based automated installation and component handling on devices | |
| KR101201276B1 (en) | Method, software and apparatus for performing actions on a wireless device using action lists and versioning | |
| CN101146059A (en) | A mail system, method and terminal for supporting attachment format conversion | |
| CN103164247A (en) | Method and device for automatically repairing system application | |
| CN104978224A (en) | Multiple hardware platform oriented application management method | |
| CN102968321A (en) | Application program installation device and application program installation method | |
| CN108897570B (en) | Version compatibility method based on cloud computing and artificial intelligence and robot system | |
| CN111736876A (en) | Client update control method, device, storage medium and server | |
| CN101470609A (en) | Software upgrading method, system and electronic equipment thereof | |
| WO2008082360A1 (en) | Dynamic launcher | |
| CN112256351A (en) | Implementation method of Feign component, micro-service calling method and device | |
| CN109799997B (en) | Management method for presetting third party application, intelligent terminal and storage medium | |
| CN112596773A (en) | Application program updating method, device, equipment and storage medium | |
| CN104239108A (en) | Software update method, software update server, client and software update system | |
| CN105528226A (en) | Method and apparatus for starting intelligent terminal | |
| CN113608773A (en) | Method and device for upgrading and updating component and electronic equipment | |
| CN101405673B (en) | Method and device to automatically process components on a device | |
| CN116483469A (en) | Preassembled application management method and system for cloud mobile phone | |
| CN111258619A (en) | Application program updating method and system | |
| CN117931237A (en) | Software upgrading method and device, intelligent television equipment and medium | |
| CN103631631A (en) | Method for automatically updating program core modules of Android software |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |