System version management method and device, electronic equipment and storage medium

Abstract

The invention discloses a system version management method and device, electronic equipment and a storage medium. Comprising the steps that under the condition that version updating of a first system is detected, to-be-processed data corresponding to the first system and to-be-processed data corresponding to a second system associated with the first system are obtained, and the to-be-processed data comprise system basic information, system operation information and system version information; determining the version consistency state of each second system by determining the fingerprint information and the system version information of each system; processing the fingerprint information, the system operation information and the system version information of each system based on a pre-constructed version compatibility prediction model, and determining a version compatibility state of each second system; and if the version consistency state of any second system is an inconsistent state and / or the version compatibility state is an incompatible state, performing early warning processing. According to the scheme, the version consistency state and the version compatibility state of multiple systems are detected, so that the accuracy and the efficiency of system version management are improved.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a system version management method, device, electronic device and storage medium. Background Art

[0002] In the power system, the Dianhong operating system has a wide range of application scenarios, covering power generation, transmission, transformation, distribution, power consumption and other links. In these links, there are a large number of equipment of different types and manufacturers, which run a variety of software systems. These systems are highly heterogeneous, including differences in hardware architecture, software platform, communication protocol, etc. For example, the wind turbine control system and solar panel monitoring system in the power generation link have completely different hardware performance and software functions.

[0003] At present, the version management of each system only judges the consistency of the system version through the increment of the system version number or the file timestamp change information. This judgment basis is extremely simple and lacks the accuracy of system version control, which makes the management efficiency of the system version low. In addition, it is impossible to manage the system version of a complex system, and it is impossible to accurately determine whether there are compatibility issues between the systems. It is easy to cause version inconsistencies between the systems, which will cause the systems to fail to operate normally and reduce the stability of the system operation. Summary of the invention

[0004] The present invention provides a system version management method, device, electronic device and storage medium to solve the problem of poor version management efficiency for multiple system versions in the prior art.

[0005] According to one aspect of the present invention, there is provided a system version management method, comprising:

[0006] When a version update of the first system is detected, obtaining to-be-processed data corresponding to the first system and to-be-processed data corresponding to at least one second system, wherein the to-be-processed data includes system basic information, system operation information and system version information, and the first system and the second system are associated with each other;

[0007] Determine fingerprint information of the first system based on system basic information of the first system, and determine fingerprint information of each second system based on system basic information of each second system;

[0008] Determine the version consistency status corresponding to each second system based on the fingerprint information and system version information corresponding to the first system and each second system respectively;

[0009] Based on the pre-built version compatibility prediction model, fingerprint information, system operation information and system version information corresponding to the first system and each second system are processed to determine the version compatibility status corresponding to each second system;

[0010] When the version consistency state of any second system is an inconsistent state and / or the version compatibility state is an incompatible state, an early warning process is performed based on the version consistency state and / or the version compatibility state corresponding to the second system.

[0011] Optionally, the system basic information includes one or more of multiple key components, system files and configuration information; determining the fingerprint information of the first system based on the system basic information of the first system includes: performing hash processing on one or more of the multiple key components, system files and configuration information of the first system respectively, and determining one or more of the component fingerprint information, file fingerprint information and configuration fingerprint information of the first system; determining the fingerprint information of the first system based on one or more of the component fingerprint information, file fingerprint information and configuration fingerprint information of the first system; and determining the fingerprint information of each second system based on the system basic information of each second system, including: for any second system, performing hash processing on one or more of the multiple key components, system files and configuration information of the second system respectively, and determining one or more of the component fingerprint information, file fingerprint information and configuration fingerprint information of the second system; determining the fingerprint information of the second system based on one or more of the component fingerprint information, file fingerprint information and configuration fingerprint information of the second system.

[0012] Optionally, the system version information includes a system version number, a system update log, and revision information; the version consistency status corresponding to each second system is determined based on the fingerprint information and system version information corresponding to the first system and each second system, respectively, including: performing semantic recognition on one or more of the system version number, system update log, and revision information of the first system based on a pre-built semantic recognition model to obtain a first information recognition result of the first system; performing semantic recognition on one or more of the system version number, system update log, and revision information of each second system based on a pre-built semantic recognition model to obtain a second information recognition result of each second system; determining similarity data between the second information recognition results of each second system and the first information recognition results, and determining the version consistency status corresponding to each second system based on the similarity data.

[0013] Optionally, after determining the version consistency status corresponding to each second system, the method also includes: for any second system, if the version consistency status corresponding to the second system is an inconsistent state, obtaining the update log and revision information of the first system, and determining the incremental update data based on the update log and revision information of the first system; performing a version update on the second system based on the incremental update data, and updating the version information of the second system, to obtain the update log and revision information of each second system.

[0014] Optionally, the method also includes: transmitting the version consistency status, version compatibility status, update log and revision information of each second system to the test module, and transmitting the update log and revision information of the first system to the test module; testing the version consistency status, version compatibility status, update log and revision information of each second system, and the update log and revision information of the first system through the test cases of the test module, and determining the test results.

[0015] Optionally, determining the association relationship between the first system and the second system includes: obtaining system interaction relationship data and / or a knowledge graph; wherein the knowledge graph is used to characterize the version dependency relationship between the first system and the second system; and determining the association relationship between the first system and the second system based on the system interaction relationship data and / or the knowledge graph.

[0016] Optionally, the method also includes: obtaining multidimensional data corresponding to the first system and each second system, wherein the multidimensional data includes one or more of system version information, system fingerprint information, version consistency status and version compatibility status; constructing a knowledge graph based on the multidimensional data corresponding to the first system and each second system, and the association relationship between the first system and each second system, and storing the knowledge graph.

[0017] According to another aspect of the present invention, there is provided a system version management device, comprising:

[0018] A module for acquiring data to be processed, used to acquire data to be processed corresponding to the first system and data to be processed corresponding to at least one second system when a version update of the first system is detected, wherein the data to be processed includes system basic information, system operation information and system version information, and the first system and the second system are associated with each other;

[0019] A fingerprint information determination module, configured to determine the fingerprint information of the first system based on the system basic information of the first system, and to determine the fingerprint information of each second system based on the system basic information of each second system;

[0020] A version consistency status determination module, used to determine the version consistency status corresponding to each second system based on the fingerprint information and system version information corresponding to the first system and each second system respectively;

[0021] A version compatibility status determination module, used to process fingerprint information, system operation information and system version information corresponding to the first system and each second system respectively based on a pre-built version compatibility prediction model, and determine the version compatibility status corresponding to each second system;

[0022] The warning processing module is used to perform warning processing based on the version consistency state and / or version compatibility state corresponding to the second system when the version consistency state of any second system is an inconsistent state and / or the version compatibility state is an incompatible state.

[0023] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0024] at least one processor; and

[0025] a memory communicatively connected to at least one processor; wherein,

[0026] The memory stores a computer program that can be executed by at least one processor. The computer program is executed by at least one processor so that the at least one processor can execute the system version management method of any embodiment of the present invention.

[0027] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the system version management method of any embodiment of the present invention when executed.

[0028] The technical solution of the embodiment of the present invention is as follows: when a version update of the first system is detected, the to-be-processed data corresponding to the first system and the to-be-processed data corresponding to at least one second system are obtained, wherein the to-be-processed data include system basic information, system operation information and system version information, and the first system and the second system are associated with each other; the fingerprint information of the first system is determined based on the system basic information of the first system, and the fingerprint information of each second system is determined based on the system basic information of each second system; the version consistency status corresponding to each second system is determined based on the fingerprint information and system version information corresponding to the first system and each second system respectively; the fingerprint information, system operation information and system version information corresponding to the first system and each second system are processed based on a pre-built version compatibility prediction model to determine the version compatibility status corresponding to each second system; when the version consistency status of any second system is an inconsistent state and / or the version compatibility status is an incompatible state, early warning processing is performed based on the version consistency status and / or version compatibility status corresponding to the second system. This solution, when detecting that a version update exists in the first system, promptly acquires the second system associated with the first system, and acquires the to-be-processed data of the first system and the second system, thereby being able to accurately determine the version consistency status and version compatibility status of each system based on the multi-dimensional data corresponding to the to-be-processed data, and in the event of an abnormality in the version consistency status and / or version compatibility status, promptly triggering an early warning operation, thereby solving the problem of poor version management efficiency for multiple system versions, making it possible to promptly determine systems with inconsistent versions, and quickly process systems with inconsistent versions, thereby improving version management efficiency.

[0029] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0031] Figure 1 is a flow chart of a system version management method provided by Embodiment 1 of the present invention;

[0032] Figure 2 is a flow chart of a system version management method provided by Embodiment 2 of the present invention;

[0033] Figure 3It is a structural diagram of a system version management device provided by Embodiment 3 of the present invention;

[0034] Figure 4 It is a structural diagram of an electronic device for implementing the system version management method according to an embodiment of the present invention. DETAILED DESCRIPTION

[0035] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0036] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, first system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0037] Embodiment 1

[0038] Figure 1 This is a flowchart of a system version management method provided by the first embodiment of the present invention. This embodiment is applicable to the situation of managing system versions. The method can be executed by a system version management device. The system version management device can be implemented in the form of hardware and / or software. The system version management device can be configured in electronic devices such as computers, servers and edge computers. Figure 1 As shown, the method includes:

[0039] S110. When a version update of the first system is detected, obtain the to-be-processed data corresponding to the first system and the to-be-processed data corresponding to at least one second system, wherein the to-be-processed data includes system basic information, system operation information and system version information, and the first system and the second system are associated with each other.

[0040] Among them, the first system specifically refers to a system with a version update, which can be any system in the power system. For example, the first system can be a wind turbine control system or a solar panel monitoring system in the power generation link; the second system specifically refers to a system that has an association relationship with the first system, including but not limited to a wind turbine control system and a solar panel monitoring system in the power generation link. The data to be processed can be specifically understood as data obtained for judging the system version consistency status and version compatibility status, including but not limited to system basic information, system operation information and system version information. The association relationship specifically represents the connection relationship between the first system and the second system, including but not limited to system version dependency and system interaction relationship. The second system associated with the first system can be determined based on the pre-built interaction relationship data and / or version dependency data between the systems, or the second system associated with the first system can be obtained based on the pre-built association relationship table.

[0041] Specifically, the system is connected with each system through the version management interface, and the latest version information of each system is obtained through the scheduled task. According to the latest version information, it is determined whether there is a system with an updated version. If there is a system with an updated version, the system can be used as the first system, and then at least one system with an associated relationship with the first system is obtained from the association table corresponding to the first system, and the obtained at least one system is respectively used as the second system. The to-be-processed data corresponding to the first system and the to-be-processed data corresponding to each second system are read from the server or the target storage space, and a data acquisition request can also be sent to the first system and each second system to obtain the to-be-processed data corresponding to the first system and the to-be-processed data corresponding to each second system.

[0042] In this embodiment, when a version update of the first system is detected, the second system associated with the first system and the corresponding data to be processed are obtained in a timely manner to determine whether the second system associated with the first system has also completed the version update, which helps to achieve version consistency of each system and avoid the problem of normal operation of the systems due to version inconsistency.

[0043] S120: Determine fingerprint information of the first system based on system basic information of the first system, and determine fingerprint information of each second system based on system basic information of each second system.

[0044] Among them, the basic information of the system can be specifically understood as the basic information that can describe and characterize the system, including but not limited to multiple key components, system files and configuration information. Key components refer to the components that play a core role in the system. These key components work together to ensure the normal operation and efficient work of the system. System files refer to the core files of the system, including but not limited to kernel files and driver files; configuration information specifically refers to the information set to ensure the normal operation of the system. The fingerprint information of the system can be specifically understood as a set of data that can characterize and describe the system, which is unique and can be a set of data generated by processing the system data through a hash algorithm. The system data can be the basic information of the system. For example, the hash algorithm includes but is not limited to MD5, SHA-1 and SHA-256.

[0045] Specifically, the system basic information of the first system can be hashed using the secure hash algorithm SHA-256, and the obtained hash value can be used as the fingerprint information of the first system; and the system basic information of each second system can be hashed using the secure hash algorithm SHA-256, and the obtained hash value can be used as the fingerprint information of the second system. The obtained fingerprint information of each system can be used as the unique identifier of the corresponding system to provide basic data for subsequently determining the version consistency status and version compatibility status corresponding to each system, thereby avoiding confusion in the version consistency detection results and the version compatibility status detection results.

[0046] In this embodiment, by determining the fingerprint information corresponding to each system, it is used to subsequently determine the version consistency status of each system, which helps to identify the differences between the system versions and helps to improve the accuracy of the version consistency status.

[0047] Optionally, the system basic information includes one or more of multiple key components, system files and configuration information; determining the fingerprint information of the first system based on the system basic information of the first system includes: performing hash processing on one or more of the multiple key components, system files and configuration information of the first system respectively, and determining one or more of the component fingerprint information, file fingerprint information and configuration fingerprint information of the first system; determining the fingerprint information of the first system based on one or more of the component fingerprint information, file fingerprint information and configuration fingerprint information of the first system; and determining the fingerprint information of each second system based on the system basic information of each second system, including: for any second system, performing hash processing on one or more of the multiple key components, system files and configuration information of the second system respectively, and determining one or more of the component fingerprint information, file fingerprint information and configuration fingerprint information of the second system; determining the fingerprint information of the second system based on one or more of the component fingerprint information, file fingerprint information and configuration fingerprint information of the second system.

[0048] The system basic information includes a variety of data. In this embodiment, one or more of a plurality of key components, system files and configuration information are selected as the system basic information to determine the fingerprint information corresponding to each system.

[0049] Specifically, one or more information from multiple key components, system files and configuration information are selected as system basic information for hash processing. Specifically, one or more information from multiple key components, system files and configuration information of the first system are hashed separately by a hash algorithm to obtain one or more component fingerprint information, file fingerprint information and configuration fingerprint information of the first system, and then one or more of the component fingerprint information, file fingerprint information and configuration fingerprint information of the first system are spliced ​​together, and the spliced ​​hash data is used as the fingerprint information of the first system; and, for any second system, one or more information from multiple key components, system files and configuration information of the second system are hashed separately by a hash algorithm to obtain one or more component fingerprint information, file fingerprint information and configuration fingerprint information of the second system, and then one or more of the component fingerprint information, file fingerprint information and configuration fingerprint information of the second system are spliced ​​together, and the spliced ​​hash data is used as the fingerprint information of the second system. In this way, the fingerprint information of each second system is obtained.

[0050] S130: Determine the version consistency status corresponding to each second system based on the fingerprint information and system version information corresponding to the first system and each second system respectively.

[0051] The version consistency state corresponding to the second system specifically represents the version consistency state of the second system relative to the first system. It should be noted that the first system is a system after the system version is updated. Judging the version consistency state corresponding to the second system can determine whether the second system is consistent with the system version of the first system. If there is version consistency, the second system can operate normally with the first system. If there is version inconsistency, it is possible that the second system cannot operate normally with the first system.

[0052] Specifically, the fingerprint information of each system is bound to the corresponding system version information, and the fingerprint information can be used as the identifier of the corresponding system version information. The fingerprint information and system version information corresponding to the first system and the second system are processed by calling the pre-built version consistency state detection model, and the version consistency state of each second system relative to the first system is determined. If the second system is consistent with the first system version, the output result is that the version consistency state is a consistent state. If the second system is inconsistent with the first system version, the output result is that the version consistency state is an inconsistent state. Alternatively, the fingerprint information and system version information corresponding to the first system and the second system can be semantically analyzed respectively to determine the similarity result between the fingerprint information and system version information corresponding to the second system and the fingerprint information and system version information corresponding to the first system, and the version consistency state corresponding to each second system is determined according to the similarity result. For example, it can be set that if the similarity result meets the preset similarity threshold, the version consistency state corresponding to the second system is determined to be a consistent state, and if the similarity result does not meet the preset similarity threshold, the version consistency state corresponding to the second system is determined to be an inconsistent state.

[0053] In this embodiment, the version consistency status is determined by using multi-dimensional information corresponding to the first system and the second system respectively, and the version consistency status corresponding to each second system is obtained. This makes it possible to use more information to determine the version consistency status corresponding to each second system, thereby improving the accuracy of the determined version consistency status.

[0054] Optionally, after determining the version consistency status corresponding to each second system, the method also includes: for any second system, if the version consistency status corresponding to the second system is an inconsistent state, obtaining the update log and revision information of the first system, and determining the incremental update data based on the update log and revision information of the first system; performing a version update on the second system based on the incremental update data, and updating the version information of the second system, to obtain the update log and revision information of each second system.

[0055] Among them, the system's log information and revision information include relevant information about the system version update, the log information includes the update process of the version update, and the revision information includes the revision number and the functional change information represented by the revision number. It is understandable that after each system performs system finer processing, the system's log information and revision information will also be automatically updated in succession. Incremental update data specifically refers to data that is updated and changed when performing a system version update operation. The incremental update data can be determined by analyzing the log information and revision information before and after the system version update.

[0056] Specifically, after determining the version consistency status corresponding to each second system, for any second system, if the version consistency status of the second system is an inconsistent state, it is necessary to determine the incremental update content, specifically by obtaining the update log and revision information of the first system, and processing the update log and revision information of the first system through a binary search algorithm to obtain the incremental update content. It should be noted that the update log and revision information of the first system here include the log information and revision information before and after the first system is updated. The log information and revision information before and after the first system is updated are processed by a binary search algorithm to obtain the difference between the new and old system versions, and the incremental update data for system update is extracted from the difference. After obtaining the incremental update data, the incremental update data is transmitted to the corresponding second system, and the second system automatically updates the version according to the corresponding incremental update data. After the update is completed, the corresponding version information of the second system is updated and the corresponding update log is generated, thereby obtaining the update log and revision information of the second system. After completing the system version update of all second systems in a version inconsistent state, the update log and revision information of each second system are obtained.

[0057] In this embodiment, by determining the incremental update content corresponding to each system, the system version of the corresponding system is updated based on the incremental update content. There is no need to re-download and redeploy the entire system every time the system is updated, thereby reducing the amount of data transmission and update time, and avoiding greater pressure on network bandwidth and system resources. The system version can be updated quickly and effectively to ensure version consistency between systems, and avoid problems such as inability to communicate normally between devices and data interaction errors due to inconsistent system versions.

[0058] Based on the above embodiments, the method also includes: transmitting the version consistency status, version compatibility status, update log and revision information of each second system to the test module, and transmitting the update log and revision information of the first system to the test module; testing the version consistency status, version compatibility status, update log and revision information of each second system, and the update log and revision information of the first system through the test cases of the test module, and determining the test results.

[0059] Specifically, after obtaining the version consistency status, version compatibility status, update log and revision information of each second system, the version consistency status, version compatibility status, update log and revision information of each second system, and the update log and revision information of the first system are transmitted together to the test system, and the version consistency status, version compatibility status, update log and revision information of the second systems, as well as the update log and revision information of the first system are tested through test cases set in the test system, and corresponding test results are obtained to provide a data basis for subsequent analysis of the dependency relationship between system versions and system repair suggestions.

[0060] S140: Process the fingerprint information, system operation information, and system version information corresponding to the first system and each second system respectively based on a pre-built version compatibility prediction model to determine the version compatibility status corresponding to each second system.

[0061] Among them, the version compatibility status can be specifically understood as the system version compatibility status that characterizes each system, and the compatibility status includes the version compatibility status and the version incompatibility status. In this embodiment, by predicting the version compatibility status between the first system and the second system after the version update, it can be predetermined whether there is a version incompatibility problem between the updated first system version and the unupdated second system version. If there is a version incompatibility problem, the compatibility problem of the system with version incompatibility can be solved in time, so that the unupdated second system can be successfully updated when the version is updated later. The pre-built version compatibility prediction model is a machine learning model, which is a model constructed by learning and analyzing a large amount of historical version information and system operation information. Exemplarily, the pre-built version compatibility prediction model can be a version prediction model constructed by a random forest algorithm and a support vector machine.

[0062] Specifically, the pre-built version compatibility prediction model is called, and the fingerprint information, system operation information and system version information corresponding to the first system and each second system are respectively input as input data into the pre-built version compatibility prediction model, and after being processed by the pre-built version compatibility prediction model, the version compatibility status corresponding to each second system is output. In some specific embodiments, the hardware information corresponding to the system will also affect the version compatibility status between systems. Therefore, the hardware information corresponding to each system can also be added to the input parameters of the pre-built version compatibility prediction model to predict the version compatibility status corresponding to each system. Exemplarily, the hardware information includes but is not limited to the hardware model and hardware architecture.

[0063] In this embodiment, the multi-dimensional information of each system is processed through a pre-built version compatibility prediction model to predict the version compatibility status corresponding to each second system, so that potential version conflicts can be identified in advance, which helps to deal with version conflicts in a timely manner and ensure that subsequent version updates can proceed smoothly.

[0064] S150: When the version consistency status of any second system is an inconsistent state and / or the version compatibility status is an incompatible state, perform warning processing based on the version consistency status and / or version compatibility status corresponding to the second system.

[0065] Specifically, the version consistency status and version compatibility status of each second system are identified. If the version consistency status of any second system is inconsistent, corresponding warning information is generated based on the second system and its version consistency status; or, if the version compatibility status of any second system is incompatible, corresponding warning information is generated based on the second system and its version compatibility status; or, if the version consistency status of any second system is inconsistent and the version compatibility status is incompatible, corresponding warning information is generated based on the second system and its corresponding version consistency status and version compatibility status. When warning information of any second system is obtained, the alarm mechanism is triggered, and the warning information is transmitted to relevant personnel through one or more of the preset emails, text messages, and system messages, so that problem solving measures can be taken as soon as possible.

[0066] On the basis of the above embodiment, determining the association relationship between the first system and the second system includes: obtaining system interaction relationship data and / or a knowledge graph; wherein the knowledge graph is used to characterize the version dependency relationship between the first system and the second system; determining the association relationship between the first system and the second system based on the system interaction relationship data and / or the knowledge graph.

[0067] Among them, the system interaction relationship data can be specifically understood as system relationship data including interactive operations such as data transmission, exchange and sharing, which characterizes the association relationship between systems to a certain extent. The system interaction relationship data between systems can be constructed through the historical operation data of each system, and the constructed system interaction relationship data can be stored in the target storage space. The knowledge graph is data used to characterize the version dependency relationship between systems. The knowledge graph corresponding to each system can be constructed through the historical operation data of each system, so that the second system with an association relationship with the first system can be queried through the knowledge graph.

[0068] Specifically, the system interaction relationship data and / or the knowledge graph are obtained from the target storage space. If the system interaction relationship data is obtained, the system interaction relationship data is matched according to the first system to obtain at least one second system associated with the first system. If the knowledge graph is obtained, the knowledge graph is matched according to the first system to obtain at least one second system associated with the first system. If the system interaction relationship data and the knowledge graph are obtained, the system interaction relationship data is matched according to the first system, and the knowledge graph is matched according to the first system, and the same systems in the matching results can be filtered out as the second systems. Therefore, there is a version dependency between the filtered second system and the first system.

[0069] Based on the above embodiments, the method also includes: obtaining multidimensional data corresponding to the first system and each second system respectively, wherein the multidimensional data includes one or more of system version information, system fingerprint information, version consistency status and version compatibility status; constructing a knowledge graph based on the multidimensional data corresponding to the first system and each second system respectively, and the association relationship between the first system and each second system, and storing the knowledge graph.

[0070] Specifically, multidimensional data corresponding to the first system and each second system is obtained from the target storage space, and the multidimensional data includes but is not limited to system version information, system fingerprint information, version consistency status and version compatibility status. The first system and each second system can be regarded as knowledge entities, and the multidimensional data corresponding to each system can be regarded as the attribute information of the corresponding knowledge entity. The association relationship between the corresponding knowledge entities is determined based on the association relationship between the systems, and the corresponding knowledge graph is constructed through the attribute information and association relationship of each knowledge entity. The knowledge graph is stored and used to query the association relationship between the systems.

[0071] Preferably, when one or more of the system basic information, system operation information, system version information, version consistency status, version compatibility status, update log, revision information, knowledge graph, incremental update data and test data corresponding to each system are obtained through the method of the above-mentioned embodiment, one or more of the system basic information, system operation information, system version information, version consistency status, version compatibility status, update log, revision information, knowledge graph, incremental update data and test data of each system can be displayed on a visualization platform, and early warning information can also be displayed on the visualization platform.

[0072] The technical solution of this embodiment is as follows: when a version update of the first system is detected, the to-be-processed data corresponding to the first system and the to-be-processed data corresponding to at least one second system are obtained, wherein the to-be-processed data include system basic information, system operation information and system version information, and the first system and the second system are associated with each other; the fingerprint information of the first system is determined based on the system basic information of the first system, and the fingerprint information of each second system is determined based on the system basic information of each second system; the version consistency status corresponding to each second system is determined based on the fingerprint information and system version information corresponding to the first system and each second system respectively; the fingerprint information, system operation information and system version information corresponding to the first system and each second system are processed based on a pre-built version compatibility prediction model to determine the version compatibility status corresponding to each second system; when the version consistency status of any second system is an inconsistent state and / or the version compatibility status is an incompatible state, early warning processing is performed based on the version consistency status and / or version compatibility status corresponding to the second system. This solution, when detecting that there is a version update in the first system, promptly obtains the second system associated with the first system and obtains the to-be-processed data of the first system and the second system, thereby being able to accurately determine the version consistency status and version compatibility status of each system based on the multi-dimensional data corresponding to the to-be-processed data, and in the event of an abnormality in the version consistency status and / or version compatibility status, promptly triggers an early warning operation, thereby solving the problem of poor version management efficiency for multiple system versions, being able to promptly determine systems with inconsistent versions, and quickly process systems with inconsistent versions, thereby improving version management efficiency.

[0073] Embodiment 2

[0074] Figure 2 It is a flow chart of a system version management method provided in the second embodiment of the present invention. This embodiment is a further optimization of the method of the above embodiment. Optionally, semantic recognition is performed on one or more of the system version number, system update log and revision information of the first system based on a pre-built semantic recognition model to obtain a first information recognition result of the first system; semantic recognition is performed on one or more of the system version number, system update log and revision information of each second system based on a pre-built semantic recognition model to obtain a second information recognition result of each second system; similarity data between the second information recognition results of each second system and the first information recognition results are determined, and the version consistency status corresponding to each second system is determined based on the similarity data. Figure 2 As shown, the method includes:

[0075] S210. When a version update of the first system is detected, obtain the to-be-processed data corresponding to the first system and the to-be-processed data corresponding to at least one second system, wherein the to-be-processed data includes system basic information, system operation information and system version information, and the first system is associated with the second system.

[0076] S220: Determine fingerprint information of the first system based on the system basic information of the first system, and determine fingerprint information of each second system based on the system basic information of each second system.

[0077] S230: Perform semantic recognition on one or more of the system version number, system update log, and revision information of the first system based on a pre-built semantic recognition model to obtain a first information recognition result of the first system.

[0078] Among them, the pre-built semantic recognition model is a model for semantic recognition and analysis, which is constructed from a large language model. In this embodiment, it is used to identify one or more of the system version number, system update log, and revision information, so as to obtain deeper system version information, which helps to improve the accuracy of version consistency status detection. The first information recognition result can be specifically understood as a semantic recognition result corresponding to the first system, which is used to distinguish from the semantic recognition results of other systems. The semantic recognition result specifically includes semantic information related to the system version.

[0079] Specifically, a pre-built semantic recognition model is called to perform semantic recognition on one or more of the system version number, system update log, and revision information of the first system, thereby obtaining semantic recognition results corresponding to one or more of the system version number, system update log, and revision information, respectively, and the obtained semantic recognition results are spliced ​​to obtain the first information recognition result of the first system.

[0080] S240: Perform semantic recognition on one or more of the system version number, system update log, and revision information of each second system based on a pre-built semantic recognition model to obtain second information recognition results of each second system.

[0081] The second information recognition result can be specifically understood as a semantic recognition result corresponding to the second system, which is used to distinguish it from the semantic recognition result of the first system.

[0082] Specifically, corresponding to any second system, a pre-built semantic recognition model is called to perform semantic recognition on one or more of the system version number, system update log, and revision information of the second system, thereby obtaining semantic recognition results corresponding to one or more of the system version number, system update log, and revision information, respectively, and the obtained semantic recognition results are spliced ​​to obtain the second information recognition result of the second system.

[0083] S250: Determine similarity data between the second information identification results of each second system and the first information identification results, and determine the version consistency status corresponding to each second system based on the similarity data.

[0084] Specifically, the similarity data of the second information identification results of each second system and the first information identification results are calculated by a similarity calculation method to obtain the similarity data corresponding to each second system. Exemplarily, the similarity algorithm includes but is not limited to the cosine similarity algorithm, the Euclidean distance algorithm, the Manhattan distance algorithm and the Minkowski distance algorithm. The corresponding similarity threshold can be pre-set according to the version consistency judgment requirement, and the judgment is made based on each second system and the similarity threshold to obtain the judgment result. The version consistency state corresponding to each second system is determined according to the judgment result corresponding to each second system. For any second system, if the judgment result is that the similarity data corresponding to the second system meets the similarity threshold, the version consistency state of the second system is determined to be a version consistent state. If the judgment result is that the similarity data corresponding to the second system does not meet the similarity threshold, the version consistency state of the second system is determined to be a version inconsistent state.

[0085] S260: Process the fingerprint information, system operation information, and system version information corresponding to the first system and each second system respectively based on a pre-built version compatibility prediction model to determine the version compatibility status corresponding to each second system.

[0086] S270: When the version consistency status of any second system is an inconsistent state and / or the version compatibility status is an incompatible state, perform warning processing based on the version consistency status and / or version compatibility status corresponding to the second system.

[0087] The technical solution of this embodiment is as follows: when a version update of the first system is detected, the to-be-processed data corresponding to the first system and the to-be-processed data corresponding to at least one second system are obtained, wherein the to-be-processed data include system basic information, system operation information and system version information, and the first system and the second system are associated with each other; the fingerprint information of the first system is determined based on the system basic information of the first system, and the fingerprint information of each second system is determined based on the system basic information of each second system; semantic recognition is performed on one or more of the system version number, system update log and revision information of the first system based on a pre-built semantic recognition model to obtain a first information recognition result of the first system; the system version number of each second system is determined based on the pre-built semantic recognition model. One or more of the version number, system update log and revision information are semantically identified to obtain the second information identification results of each second system; the similarity data between the second information identification results of each second system and the first information identification results are determined, and the version consistency status corresponding to each second system is determined based on the similarity data; the fingerprint information, system operation information and system version information corresponding to the first system and each second system are processed based on the pre-built version compatibility prediction model to determine the version compatibility status corresponding to each second system; when the version consistency status of any second system is inconsistent and / or the version compatibility status is incompatible, an early warning is performed based on the version consistency status and / or version compatibility status corresponding to the second system. This solution obtains the second system associated with the first system in a timely manner when a version update of the first system is detected, and obtains the data to be processed of the first system and the second system, so that the version consistency status and version compatibility status of each system can be accurately determined according to the multi-dimensional data corresponding to the data to be processed, and the early warning operation is triggered in a timely manner when there is an abnormality in the version consistency status and / or version compatibility status, thereby solving the problem of poor version management efficiency for multiple system versions, and can timely determine the system with inconsistent versions, and can quickly process the system with inconsistent versions, thereby improving the version management efficiency.

[0088] Embodiment 3

[0089] Figure 3 Schematic diagram of the structure of a system version management device provided by Embodiment 3 of the present invention. Figure 3 As shown, the device comprises:

[0090] The to-be-processed data acquisition module 310 is used to acquire the to-be-processed data corresponding to the first system and the to-be-processed data corresponding to at least one second system when a version update of the first system is detected, wherein the to-be-processed data includes system basic information, system operation information and system version information, and the first system and the second system are associated with each other;

[0091] A fingerprint information determination module 320, configured to determine fingerprint information of the first system based on system basic information of the first system, and to determine fingerprint information of each second system based on system basic information of each second system;

[0092] A version consistency status determination module 330, configured to determine the version consistency status corresponding to each second system based on the fingerprint information and system version information corresponding to the first system and each second system respectively;

[0093] A version compatibility status determination module 340 is used to process the fingerprint information, system operation information and system version information corresponding to the first system and each second system respectively based on a pre-built version compatibility prediction model to determine the version compatibility status corresponding to each second system;

[0094] The warning processing module 350 is used to perform warning processing based on the version consistency status and / or version compatibility status corresponding to the second system when the version consistency status of any second system is inconsistent and / or the version compatibility status is incompatible.

[0095] The technical solution of this embodiment is to obtain the to-be-processed data corresponding to the first system and the to-be-processed data corresponding to at least one second system through the to-be-processed data acquisition module when a version update of the first system is detected, wherein the to-be-processed data includes system basic information, system operation information and system version information, and the first system and the second system are associated with each other; the fingerprint information determination module determines the fingerprint information of the first system based on the system basic information of the first system, and determines the fingerprint information of each second system based on the system basic information of each second system; the version consistency state determination module determines the version consistency state corresponding to each second system based on the fingerprint information and system version information corresponding to the first system and each second system respectively; the version compatibility state determination module processes the fingerprint information, system operation information and system version information corresponding to the first system and each second system respectively based on a pre-built version compatibility prediction model, and determines the version compatibility state corresponding to each second system; the warning processing module performs warning processing based on the version consistency state and / or version compatibility state corresponding to the second system when the version consistency state of any second system is an inconsistent state and / or the version compatibility state is an incompatible state. This solution, when detecting that there is a version update in the first system, promptly obtains the second system associated with the first system and obtains the to-be-processed data of the first system and the second system, thereby being able to accurately determine the version consistency status and version compatibility status of each system based on the multi-dimensional data corresponding to the to-be-processed data, and in the event of an abnormality in the version consistency status and / or version compatibility status, promptly triggers an early warning operation, thereby solving the problem of poor version management efficiency for multiple system versions, being able to promptly determine systems with inconsistent versions, and quickly process systems with inconsistent versions, thereby improving version management efficiency.

[0096] On the basis of the above embodiment, optionally, the system basic information includes one or more of multiple key components, system files and configuration information; the fingerprint information determination module 320 is specifically used to perform hash processing on one or more of the multiple key components, system files and configuration information of the first system, and determine one or more of the component fingerprint information, file fingerprint information and configuration fingerprint information of the first system; determine the fingerprint information of the first system based on one or more of the component fingerprint information, file fingerprint information and configuration fingerprint information of the first system; and, for any second system, perform hash processing on one or more of the multiple key components, system files and configuration information of the second system, and determine one or more of the component fingerprint information, file fingerprint information and configuration fingerprint information of the second system; determine the fingerprint information of the second system based on one or more of the component fingerprint information, file fingerprint information and configuration fingerprint information of the second system.

[0097] Optionally, the system version information includes the system version number, system update log and revision information; the version consistency status determination module 330 is specifically used to perform semantic recognition on one or more of the system version number, system update log and revision information of the first system based on a pre-built semantic recognition model to obtain a first information recognition result of the first system; perform semantic recognition on one or more of the system version number, system update log and revision information of each second system based on a pre-built semantic recognition model to obtain a second information recognition result of each second system; determine the similarity data between the second information recognition results of each second system and the first information recognition result, and determine the version consistency status corresponding to each second system based on the similarity data.

[0098] Optionally, after determining the version consistency status corresponding to each second system, the device is specifically used to obtain the update log and revision information of the first system for any second system if the version consistency status corresponding to the second system is an inconsistent state, and determine the incremental update data based on the update log and revision information of the first system; perform version update on the second system based on the incremental update data, and update the version information of the second system to obtain the update log and revision information of each second system.

[0099] Optionally, the device is also specifically used to transmit the version consistency status, version compatibility status, update log and revision information of each second system to the test module, and transmit the update log and revision information of the first system to the test module; test the version consistency status, version compatibility status, update log and revision information of each second system, and the update log and revision information of the first system through the test cases of the test module, and determine the test results.

[0100] Optionally, the module for acquiring data to be processed 310 also includes a system association relationship determination unit, which is used to obtain system interaction relationship data and / or a knowledge graph; wherein the knowledge graph is used to characterize the version dependency relationship between the first system and the second system; and determine the association relationship between the first system and the second system based on the system interaction relationship data and / or the knowledge graph.

[0101] Optionally, the device is also specifically used to obtain multidimensional data corresponding to the first system and each second system, wherein the multidimensional data includes one or more of system version information, system fingerprint information, version consistency status and version compatibility status; based on the multidimensional data corresponding to the first system and each second system, and the association relationship between the first system and each second system, a knowledge graph is constructed, and the knowledge graph is stored.

[0102] The system version management device provided in the embodiment of the present invention can execute the system version management method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0103] Embodiment 4

[0104] Figure 4 1 is a schematic diagram of the structure of an electronic device provided in Embodiment 4 of the present invention. The electronic device 10 is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0105] like Figure 4 As shown, the electronic device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0106] A number of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0107] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as the system version management method.

[0108] In some embodiments, the system version management method may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the system version management method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to execute the system version management method in any other appropriate manner (e.g., by means of firmware).

[0109] Various implementations of the first system and techniques described above herein can be implemented in a digital electronic circuit first system, an integrated circuit first system, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), an application specific standard product (ASSP), a first system on a chip first system (SOC), a load programmable logic device (CPLD), computer hardware, firmware, software, and / or a combination thereof. These various implementations may include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable first system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage first system, at least one input device, and at least one output device, and transmit data and instructions to the storage first system, the at least one input device, and the at least one output device.

[0110] The computer program for implementing the system version management method of the present invention can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general-purpose computer, a special-purpose computer or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program can be executed completely on the machine, partially on the machine, partially on the machine as an independent software package and partially on a remote machine, or completely on a remote machine or server.

[0111] Embodiment 5

[0112] Embodiment 5 of the present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to cause a processor to execute a system version management method, the method comprising:

[0113] When a version update of the first system is detected, obtaining to-be-processed data corresponding to the first system and to-be-processed data corresponding to at least one second system, wherein the to-be-processed data includes system basic information, system operation information and system version information, and the first system and the second system are associated with each other;

[0114] Determine fingerprint information of the first system based on system basic information of the first system, and determine fingerprint information of each second system based on system basic information of each second system;

[0115] Determine the version consistency status corresponding to each second system based on the fingerprint information and system version information corresponding to the first system and each second system respectively;

[0116] Based on the pre-built version compatibility prediction model, fingerprint information, system operation information and system version information corresponding to the first system and each second system are processed to determine the version compatibility status corresponding to each second system;

[0117] When the version consistency state of any second system is an inconsistent state and / or the version compatibility state is an incompatible state, an early warning process is performed based on the version consistency state and / or the version compatibility state corresponding to the second system.

[0118] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction-executing first system, device, or equipment. A computer-readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor first system, device, or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0119] To provide interaction with a user, the first system and technology described herein can be implemented on an electronic device, which has: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball), through which the user can provide input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and the input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0120] The first system and techniques described herein may be implemented in a computing first system including backend components (e.g., as a data server), or a computing first system including middleware components (e.g., an application server), or a computing first system including frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with an implementation of the first system and techniques described herein), or a computing first system including any combination of such backend components, middleware components, or frontend components. The components of the first system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0121] The computing first system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The relationship between the client and the server is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0122] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0123] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A system version management method, characterized in that: include: When a version update of the first system is detected, obtaining to-be-processed data corresponding to the first system and to-be-processed data corresponding to at least one second system, wherein the to-be-processed data includes system basic information, system operation information and system version information, and the first system is associated with the second system; Determine fingerprint information of the first system based on system basic information of the first system, and determine fingerprint information of each of the second systems based on system basic information of each of the second systems; Determine the version consistency status corresponding to each of the second systems based on the fingerprint information and the system version information respectively corresponding to the first system and each of the second systems; Processing the fingerprint information, the system operation information, and the system version information respectively corresponding to the first system and each of the second systems based on a pre-built version compatibility prediction model to determine a version compatibility status corresponding to each of the second systems; In the case that the version consistency state of any second system is an inconsistent state and / or the version compatibility state is an incompatible state, early warning processing is performed based on the version consistency state and / or the version compatibility state corresponding to the second system.

2. The method according to claim 1, characterized in that: The system basic information includes one or more of a plurality of key components, system files and configuration information; The determining the fingerprint information of the first system based on the system basic information of the first system includes: Performing hash processing on one or more of the plurality of key components, system files, and configuration information of the first system respectively to determine one or more of the component fingerprint information, file fingerprint information, and configuration fingerprint information of the first system; determining the fingerprint information of the first system based on one or more of the component fingerprint information, file fingerprint information, and configuration fingerprint information of the first system; And, determining the fingerprint information of each second system based on the system basic information of each second system includes: For any of the second systems, hash processing is performed on one or more of the multiple key components, system files and configuration information of the second system to determine one or more of the component fingerprint information, file fingerprint information and configuration fingerprint information of the second system; the fingerprint information of the second system is determined based on one or more of the component fingerprint information, file fingerprint information and configuration fingerprint information of the second system.

3. The method according to claim 1, characterized in that The system version information includes the system version number, system update log and revision information; The determining the version consistency status corresponding to each of the second systems based on the fingerprint information and the system version information respectively corresponding to the first system and each of the second systems includes: Based on a pre-built semantic recognition model, semantic recognition is performed on one or more of the system version number, system update log, and revision information of the first system to obtain a first information recognition result of the first system; Based on the pre-built semantic recognition model, semantic recognition is performed on one or more of the system version number, system update log, and revision information of each of the second systems to obtain a second information recognition result of each of the second systems; Determine similarity data between the second information identification results of each of the second systems and the first information identification results, and determine version consistency states corresponding to each of the second systems based on the similarity data.

4. The method according to claim 1, characterized in that: After determining the version consistency status corresponding to each of the second systems, the method further includes: For any second system, if the version consistency state corresponding to the second system is an inconsistent state, obtaining the update log and revision information of the first system, and determining the incremental update data based on the update log and revision information of the first system; The second system is updated based on the incremental update data, and the version information of the second system is updated to obtain the update log and revision information of each second system.

5. The method according to claim 4, characterized in that The method also includes: Transmitting the version consistency status, version compatibility status, update log and revision information of each of the second systems to the test module, and transmitting the update log and revision information of the first system to the test module; The version consistency status, version compatibility status, update log and revision information of each of the second systems, as well as the update log and revision information of the first system are tested through the test cases of the test module, and the test results are determined.

6. The method according to claim 1, characterized in that Determining an association relationship between the first system and the second system includes: Acquire system interaction relationship data and / or a knowledge graph; wherein the knowledge graph is used to characterize the version dependency relationship between the first system and the second system; An association relationship between the first system and the second system is determined based on the system interaction relationship data and / or the knowledge graph.

7. The method according to claim 6, characterized in that The method also includes: Acquire multidimensional data corresponding to the first system and each of the second systems, wherein the multidimensional data includes one or more of system version information, system fingerprint information, version consistency status, and version compatibility status; A knowledge graph is constructed based on the multidimensional data corresponding to the first system and each of the second systems, and the association relationship between the first system and each of the second systems, and the knowledge graph is stored.

8. A system version management device, characterized in that: include: a module for acquiring data to be processed, used to acquire data to be processed corresponding to the first system and data to be processed corresponding to at least one second system when a version update of the first system is detected, wherein the data to be processed includes system basic information, system operation information and system version information, and the first system and the second system are associated with each other; a fingerprint information determination module, configured to determine the fingerprint information of the first system based on the system basic information of the first system, and to determine the fingerprint information of each of the second systems based on the system basic information of each of the second systems; A version consistency status determination module, configured to determine the version consistency status corresponding to each of the second systems based on the fingerprint information and the system version information corresponding to the first system and each of the second systems respectively; a version compatibility status determination module, configured to process the fingerprint information, the system operation information and the system version information respectively corresponding to the first system and each of the second systems based on a pre-built version compatibility prediction model, and determine the version compatibility status corresponding to each of the second systems; The warning processing module is used to perform warning processing based on the version consistency status and / or the version compatibility status corresponding to the second system when the version consistency status of any second system is an inconsistent state and / or the version compatibility status is an incompatible state.

9. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the system version management method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the system version management method according to any one of claims 1 to 7 when executed.

Images