Method, device and system for updating version data of multiple terminals

Abstract

The invention provides a method for updating version data of multiple terminals. The method comprises the steps of obtaining a new version data set and storing the new version data set in a version library; performing version updating on the plurality of terminals based on the new version data set in the version library to obtain updating results of the plurality of terminals; obtaining target incremental data based on new version data and current version data of the first target terminal in a version library under the condition that the updating result of the first target terminal is updating failure; and performing version updating on the first target terminal based on the target incremental data. An intelligent synchronous management system is constructed for the problem of multi-terminal software version chaos in production. Through accurate version identification, flexible triggering update, incremental synchronization retry, one-key version backspacing and visual report, efficient synchronization and rapid fault recovery are realized, and production continuity is guaranteed.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of communication technology, in particular to a multi-terminal version data updating method, device and system. BACKGROUND

[0002] In the field of industrial automation, the cooperative operation of multi-terminal devices (including same type terminal devices and different type terminal devices) in a factory production line depends on the version consistency of the terminal production software configuration files and source files, and therefore the terminals need to be updated in time.

[0003] The prior art has obvious deficiencies in the multi-terminal version data updating process: on the one hand, when the terminal is updated, if some terminals fail to update, the complete new version data usually needs to be retransmitted to the failed terminals for full update, which not only wastes network resources but also leads to low update efficiency. On the other hand, there is a lack of systematic management of the historical version data of each terminal, it is difficult to quickly obtain the difference between the new version data and the current version data of the terminal, and it is not possible to update in a targeted manner, which affects the timeliness and effectiveness of the version update, and may adversely affect the production continuity. Therefore, there is an urgent need for a multi-terminal version data updating method that can efficiently handle terminal version update failures to solve the above problems. SUMMARY

[0004] The purpose of the embodiments of the present application is to provide a multi-terminal version data updating method, device and system to solve the problems of production interruption, low synchronization efficiency and low resource utilization caused by inefficient handling of version update failures in multi-terminal.

[0005] To solve the above technical problems, the embodiments of the present application provide a multi-terminal version data updating method, which adopts the following technical solution: A multi-terminal version data updating method, comprising the following steps: Obtaining a new version data set and storing it in a version library, wherein the new version data set includes new version data corresponding to each of the terminals, and the version library includes a plurality of version data corresponding to each of the terminals; Updating the versions of the plurality of terminals based on the new version data set in the version library to obtain update results of the plurality of terminals, wherein the update result is update success or update failure; In the case where the update result of a first target terminal is update failure, obtaining target incremental data based on the new version data and the current version data of the first target terminal in the version library, wherein the first target terminal is any one of the plurality of terminals, and the target incremental data is the difference between the new version data and the current version data of the first target terminal. updating the first target terminal based on the target incremental data.

[0006] Further, the obtaining the new version data set and storing in the version library comprises: obtaining pre-processed new version data of each terminal; labeling the pre-processed new version data of each terminal to obtain new version data of each terminal, wherein the new version data of each terminal comprises the pre-processed new version data, terminal number and version information; generating the new version data set based on the new version data of multiple terminals and storing in the version library.

[0007] Further, after the above updating the first target terminal based on the target incremental data, the method further comprises: detecting running states of multiple terminals in real time; when detecting that a second target terminal with a running exception exists in the multiple terminals, obtaining historical version data of the second target terminal; performing a rollback operation on version data currently running on the second target terminal based on the historical version data.

[0008] Further, the obtaining the historical version data of the second target terminal when detecting that the second target terminal with the running exception exists in the multiple terminals comprises: obtaining terminal number and version information of the second target terminal; obtaining the historical version data of the second target terminal from the version library based on the terminal number and version information of the second target terminal.

[0009] Further, the updating multiple terminals based on the new version data set in the version library to obtain update results of the multiple terminals comprises: updating multiple terminals based on a preset update cycle to obtain update results of the multiple terminals.

[0010] Further, before the above updating multiple terminals based on the new version data set in the version library to obtain update results of the multiple terminals, the method further comprises: performing offline state detection on multiple terminals to exclude a third target terminal in an offline state; performing a version update operation on terminals other than the third target terminal.

[0011] Further, before the version updating of the plurality of terminals based on the new version data set in the version library, the method further comprises: detecting offline states of the plurality of terminals, and excluding a third target terminal in an offline state; performing a version updating operation on terminals other than the third target terminal in the plurality of terminals.

[0012] Further, after the version updating of the first target terminal based on the target incremental data, the method further comprises: generating version updating information of each terminal; generating a synchronization report based on a terminal number, version information, and version updating information of each terminal.

[0013] To solve the above technical problems, the embodiments of the present application further provide a multi-terminal version data updating device, which adopts the following technical solutions: A multi-terminal version data updating device comprises: an acquisition module configured to acquire a new version data set and store the new version data set in a version library, wherein the new version data set comprises new version data corresponding to a plurality of terminals respectively, and the version library comprises a plurality of version data corresponding to each terminal; a version management module configured to perform version updating of the plurality of terminals based on the new version data set in the version library, and obtain updating results of the plurality of terminals, wherein the updating results are updating success or updating failure; an incremental synchronization module configured to, in a case where the updating result of a first target terminal is updating failure, obtain target incremental data based on new version data and current version data of the first target terminal in the version library, and perform version updating of the first target terminal based on the target incremental data, wherein the first target terminal is any terminal in the plurality of terminals, and the target incremental data is a difference part of the new version data and the current version data of the first target terminal.

[0014] To solve the above technical problems, the embodiments of the present application further provide a multi-terminal version data updating system, which adopts the following technical solutions: A multi-terminal version data updating system comprises a multi-terminal version data updating device and a plurality of terminals, wherein the multi-terminal version data updating device and the plurality of terminals are respectively communicatively connected, and the multi-terminal version data updating device is configured to execute the multi-terminal version data updating method.

[0015] Compared with the prior art, the embodiments of the application have the following beneficial effects: the method for updating version data of multiple terminals disclosed in the application obtains a new version data set and stores it in a version library, updates versions of multiple terminals based on the new version data set in the version library, obtains update results of the multiple terminals, and in the case that the update result of a first target terminal is update failure, obtains target incremental data based on the new version data and the current version data of the first target terminal in the version library, and updates the version of the first target terminal based on the target incremental data.

[0016] The application constructs an intelligent synchronization management system by aiming at the problem of multiple terminal software version confusion in production. Through accurate version identification, flexible trigger update, incremental synchronization retry, one-key version rollback and visual report, efficient synchronization and rapid fault recovery are realized, and production continuity is ensured. BRIEF DESCRIPTION OF DRAWINGS

[0017] In order to more clearly illustrate the scheme in the application, the drawings needed in the description of the embodiments of the application will be briefly introduced below. Obviously, the drawings in the following description are some embodiments of the application, and other drawings can be obtained by those skilled in the art without creative labor on the basis of these drawings.

[0018] Figure 1 is a flowchart of a method for updating version data of multiple terminals provided by the application; Figure 2 is a structural schematic diagram of a device for updating version data of multiple terminals provided by the application; Figure 3 is a structural schematic diagram of a system for updating version data of multiple terminals provided by the application. DETAILED DESCRIPTION

[0019] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the application belongs; the terms used in the specification of the application are only for the purpose of describing specific embodiments and are not intended to limit the application; the specification, claims and above-described drawing of the application; the terms "include" and "have" and any variations thereof in the specification and claims of the application and above-described drawing are intended to cover non-exclusive inclusion. The specification and claims of the application or the above-described drawing of the application; the terms "first", "second", etc. are used to distinguish different objects, not to describe a specific order.

[0020] Reference herein to an "embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are they necessarily mutually exclusive of one another. As will be apparent to those of ordinary skill in the art, embodiments described herein can be combined with other embodiments.

[0021] In order to better understand the scheme of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings.

[0022] The traditional technology is not meticulous in version identification of production software configuration files and source files, lacks unique and comprehensive version information (such as detailed version number, time stamp, hash check value, etc.), and is difficult to accurately distinguish different versions of files, resulting in confusion in version identification and management, and unable to provide reliable basis for synchronization judgment. The traditional synchronization trigger mode is limited, and cannot flexibly select the trigger time according to the complex scene of industrial production (such as timing active push or manual synchronization push), which may cause the terminal to be unable to obtain the new version file in time, or to perform synchronization at an inappropriate time to affect production.

[0023] In order to solve the above problems, we propose a multi-terminal version data updating method, referring to Figure 1 , shows a flowchart of one embodiment of the multi-terminal version data updating method according to the present application. The multi-terminal version data updating method comprises the following steps: Step S01, obtaining a new version data set and storing it in a version library, wherein the new version data set includes a plurality of new version data corresponding to each terminal, and the version library includes a plurality of version data corresponding to each terminal.

[0024] In this embodiment, the server can use a high-performance industrial server with strong computing, storage and network communication capabilities, capable of handling multiple terminal synchronization requests simultaneously; the terminal device can be various industrial control terminals, operation terminals, etc. in the factory production line, with network connection function and certain storage and processing capacity.

[0025] The server side develops corresponding management software, including a database module (for storing file and version information, synchronization state, rollback record and other data), a version management module (for implementing intelligent version management function), a synchronization trigger module (for processing timing and manual synchronization trigger), an incremental synchronization module (for processing incremental retry of failed terminal), a version rollback module (for executing version rollback and recording), a report generation module (for generating visual synchronization report) and a communication module (for data interaction with terminal). The terminal device installs corresponding client software, which has functions of receiving server instructions, executing file synchronization and rollback operation, and feeding back state information.

[0026] In the embodiment, the server and the terminal are connected through a stable network such as industrial Ethernet, to ensure the reliability and real-time performance of data transmission.

[0027] The new version data corresponding to each terminal is collected to form a new version data set, and the set is stored in a version library containing multiple version data of each terminal. The new version data set covers the new version files corresponding to each terminal, such as configuration files and source files. The version library is used for long-term storage of historical version data of each terminal. This step provides data source for multi-version update, and the existence of the version library also facilitates management and tracing of historical versions of each terminal, ensuring that historical data can be retrieved in real time.

[0028] For example, in a server (version updating device) of an automobile parts factory, V1.1 version production configuration software and source files corresponding to 10 terminals are obtained to form a new version data set, which is stored in the version library of the server. The version library also stores historical data such as V1.0 version of the 10 terminals.

[0029] In step S02, the version of the plurality of terminals is updated based on the new version data set in the version library, and the update result of the plurality of terminals is obtained, wherein the update result is update success or update failure.

[0030] The new version data set stored in the version library is used to initiate version update operation to the plurality of terminals, and then the update result of each terminal is recorded. By pushing the new version data to the terminal, the version of the terminal is updated, thereby realizing the consistency of the versions of the terminals. Meanwhile, the update result is recorded, so that the update state of each terminal can be grasped in time, providing basis for subsequent processing.

[0031] For example, in the above automobile parts factory, the server issues an update instruction to 10 terminals based on the V1.1 version data set in the version library. Eight terminals successfully receive the instruction and complete the update operation, one terminal fails to update due to network fluctuations (hereinafter referred to as the first target terminal), and the other terminal is offline due to a fault and does not respond, and is determined to have failed to update. The update result of this V1.1 version update operation is recorded in the memory and the server.

[0032] In step S03, if the update result of the first target terminal is update failure, target incremental data is obtained based on the new version data and the current version data of the first target terminal in the version library, wherein the first target terminal is any one of the plurality of terminals, and the target incremental data is the difference between the new version data and the current version data of the first target terminal.

[0033] For the terminals that fail in the synchronization process, the incremental synchronization method is used for automatic retry, reducing unnecessary resource consumption and improving the success rate and efficiency of synchronization. The target incremental data is the difference between the new version data of a terminal and the version data currently used by the terminal in the version library. If the full data is retransmitted after the update fails, the network bandwidth and time will be wasted. The target incremental data is only the difference, which occupies less bandwidth and time, and can improve the efficiency of subsequent retry update and reduce resource consumption.

[0034] In this embodiment, it can be for a terminal that fails to update due to network fluctuations, i.e. the first target terminal. For example, in the above automobile parts factory, the server retrieves the V1.1 version data of the terminal and the V1.0 version data currently used by the terminal in the version library, and finds that the difference is mainly the modification of a process parameter configuration sub-file, which is the target incremental data.

[0035] In step S04, the first target terminal is updated based on the target incremental data.

[0036] The obtained target incremental data is sent to the first target terminal, so that the terminal completes version update based on the incremental data. By transmitting incremental data, the terminal that fails to update can efficiently complete the update, ensuring that the terminal eventually maintains the same version as other successfully updated terminals, and ensuring the version consistency of the overall system.

[0037] In some embodiments, the server can send the above process parameter configuration sub-file (target incremental data) to the terminal that fails to update, and the terminal integrates the incremental data after receiving it, successfully updating its own version to V1.1.

[0038] The application constructs an intelligent synchronization management system to save network resources and ensure the version consistency of the equipment, reduces manual intervention, reduces operation and maintenance costs, and effectively solves the core problems of low efficiency, high resource consumption, and insufficient success rate in multi-terminal version synchronization In some optional implementations of the embodiment, the step of obtaining the new version data set and storing it in the version library specifically includes: obtaining preprocessed new version data of each terminal; labeling the preprocessed new version data of each terminal to obtain new version data of each terminal, wherein the new version data of each terminal includes the preprocessed new version data, a terminal number, and version information; generating the new version data set based on the new version data of the plurality of terminals and storing it in the version library.

[0039] In the embodiment, the preprocessed new version data refers to original new version data generated or provided by a terminal, which has not been completely labeled or processed (such as not adding terminal number, version information, and the like), but has completed preliminary preparation (such as format standardization, integrity check, redundant information cleaning, and the like). It is the basis for generating new version data. The preprocessed new version data is not limited to source files, but can also include various data records, configuration parameters, and the like.

[0040] The preprocessed new version data of each terminal is labeled based on the version information and the terminal number to generate the new version data of each terminal. In addition, the new version data can be labeled by data generation time, data size, and data type to obtain the new version data. The new version data is integrated into a new version data set and stored in a database.

[0041] For example, in the above-mentioned 10 terminals of the automobile parts factory, the preprocessed new version data can be obtained by the server to obtain the source file of each terminal. The version information and the terminal number are obtained by reading the source file (preprocessed new version data) of each terminal, and then the source file of terminal 1 is labeled as “terminal number: 001, version information: V1.1, [source file content]”, the source file of terminal 2 is labeled as “terminal number: 002, version information: V1.3, [source file content]”, and so on to obtain the new version data of the 10 terminals. The data is integrated into a new version data set and stored in a version library.

[0042] The application clearly defines the acquisition and storage process of new version data. By labeling the preprocessed data, each new version data is associated with a specific terminal and version information, ensuring that the data in the version library is clear and identifiable, providing an accurate data basis for subsequent version updates, queries, and the like, and avoiding data confusion.

[0043] In some optional implementations of the embodiment, after the version update of the first target terminal based on the target incremental data, the method further comprises: detecting the running states of the terminals in real time; when a second target terminal with a running exception is detected among the terminals, obtaining historical version data of the second target terminal; based on the historical version data, performing a rollback operation on the version data currently running on the second target terminal.

[0044] Since the new version data may have unknown problems, it may cause the terminal to run abnormally and affect production or other businesses. Each terminal is detected, and when a second target terminal (any terminal among the multiple terminals) running the new version data has an abnormality, the corresponding historical version data of the terminal in the version library is obtained based on the operation request triggered by the administrator, such as the historical version data before the update, and a rollback operation is performed based on the version to return to the historical version data.

[0045] For example, in the above automobile parts factory, after terminal 2 of the factory is updated to V1.1 version, an abnormal situation of production parameter calculation error occurs. The administrator manually triggers an operation request on the server to request that terminal 2 be rolled back to the previous V1.0 version. The server obtains the V1.0 version data (historical version data) of terminal 2 from the version library based on the request and controls terminal 2 to perform a rollback operation to restore it to the V1.0 version. The related information of the rollback operation is completely recorded to facilitate subsequent tracing and analysis.

[0046] The application quickly responds to the abnormal problems of the new version data, restores the terminal to a stable state, reduces the risk of business interruption caused by version problems, and improves the reliability and stability of the system.

[0047] It should be noted that in addition to manually triggering the operation request by the administrator, the system can also automatically trigger the rollback operation after detecting the exception and confirming it by the administrator; the selection of the historical version data can be the system recommending a suitable historical version according to the terminal running stability record.

[0048] In some optional implementations of the embodiment, when a second target terminal with a running exception is detected among the terminals, the method further comprises: obtaining the terminal number and version information of the second target terminal; based on the terminal number and version information of the second target terminal, obtaining the historical version data of the second target terminal from the version library.

[0049] When detecting that the second target terminal has a new version data running exception, the terminal number and version information of the second target terminal are obtained based on an operation request, and then the version data is obtained from the version library according to the information, so as to ensure the correctness of the version rollback operation.

[0050] For example, in the above automobile parts factory, when the terminal 3 runs the new version data, an exception occurs, the administrator triggers a rollback operation application, and the application contains the terminal number "003" of the terminal 3 and the target historical version information "V0.9". After the server receives the request, the V0.9 version data corresponding to the terminal 3 is accurately found from the version library according to the terminal number "003" and the version information "V0.9", and is used as the historical version data.

[0051] By ensuring the accuracy of the obtained historical version data, the application avoids the failure of the rollback operation or the rollback to an error version due to data errors, and further improves the reliability of the version rollback operation.

[0052] It should be noted that in addition to obtaining the historical version data through the terminal number and the version information, the historical version data can also be obtained through the unique identifier of the terminal, such as the MAC address and the version release time.

[0053] In some optional implementations of the embodiment, the version updating of the plurality of terminals based on the new version data set in the version library to obtain the updating result of the plurality of terminals includes: According to a preset updating period, the version of the plurality of terminals is updated to obtain the updating result of the plurality of terminals.

[0054] By setting the mechanism of triggering the version updating at a predetermined time, the mechanism is suitable for a scenario of needing to perform unified updating at a specific time, such as updating during a production gap or a system maintenance period, so as to avoid the updating operation from interfering with normal business and improve the planning and orderliness of the updating.

[0055] In an industrial environment, the production line needs to continuously and stably operate. If the version is randomly updated, the production may be interrupted due to terminal restart, data loading and the like. The timing triggering can arrange the updating in a non-production period (such as maintenance in the early morning or a lunch break), so as to avoid interference with the production process.

[0056] In the embodiment, the administrator sets the updating time in the version management system of the server according to the operation plan of the production line. The server automatically detects whether the complete new version data set is stored in the version library 10 minutes before the preset time arrives. When the system time reaches the preset value, the synchronization triggering function of the server automatically sends a version updating instruction to all online terminals. The server receives the updating state feedback of each terminal in real time, and records the updating start time, completion time, result and failure reason of each terminal.

[0057] For example, in the above-mentioned automobile parts factory, the administrator presets to send version update instructions to 10 terminals of the factory at 3 a.m. (non-production period) and 20 p.m. every day. At the preset time, the server automatically sends the update instructions based on the new version data set to the 10 terminals, and then collects the update results (success or failure) of the terminals.

[0058] The present application provides a mechanism for timing-triggered version update, which is suitable for scenarios that require unified update at a specific time. The update time can be reasonably arranged according to business needs, reducing the impact of update on normal business, making version update more planned and controllable. For example, update during production gaps or system maintenance periods to avoid interference with normal business and improve the planning and orderliness of updates.

[0059] It should be noted that the preset time can be periodic (e.g., every Monday morning), one-time, or dynamically adjusted according to system load conditions (e.g., when the system load is below a certain threshold).

[0060] In some optional implementations of the present embodiment, the above-mentioned version update of a plurality of terminals based on the new version data set includes: In the case of obtaining the administrator update instruction, the version update of a plurality of terminals is performed to obtain the update results of a plurality of terminals.

[0061] In the present embodiment, the server receives an update instruction issued by the administrator due to the discovery of an important security vulnerability, logs into the system through the management interface of the server (such as a Web-based console, client software), selects the new version data set to be updated in the version management, checks the terminal range to be updated, manually triggers the update, and the system generates an update instruction containing the terminal list, version information, trigger person, and trigger time.

[0062] After the server receives the instruction, it automatically verifies the operation permission of the administrator, whether the selected terminal is online, and whether the new version data is complete. If the verification is passed, the system pops up a confirmation window for the administrator, and the instruction takes effect after the administrator clicks “Confirm”. If the verification fails, the system prompts the specific reason for the administrator to adjust and re-initiate. The server pushes the update instruction to the selected terminal, and the terminal receives the instruction, automatically starts the download, verification, and replacement process of the new version data, and feeds back the progress to the server in real time and collects the update results of each terminal.

[0063] The application provides a mechanism for manually triggering version update, so that the administrator can flexibly control the update time according to actual conditions, such as urgent repair of a bug, release of an important version, etc., thereby improving the flexibility and emergency response capability of version update.

[0064] It should be noted that the triggering mode of the administrator update instruction can also be a remote instruction, an encrypted instruction, etc., and different update instructions can be sent to different terminal groups.

[0065] In some optional implementations of the embodiment, before the version update of the plurality of terminals based on the new version data set in the version library is performed, the method further comprises: detecting the offline state of the plurality of terminals, and excluding a third target terminal in an offline state; performing a version update operation on the terminals other than the third target terminal in the plurality of terminals.

[0066] The offline terminal cannot receive the update instruction, and pushing data to the offline terminal will waste the computing resources and network resources of the server. After the offline terminal is detected and skipped, the resource configuration can be optimized. In the embodiment, when the administrator initiates a manual update instruction and passes the permission check, the server automatically starts the terminal state detection process and completes the detection before issuing the update instruction. The offline detection can be performed by sending a request packet to all terminals to be updated by the server. If a heartbeat response packet is received within 3 seconds, it is determined that the terminal is online. If no response is received or a device offline feedback is received, it is determined that the terminal is offline.

[0067] The server divides the terminals to be updated into an online list and an offline list according to the detection result, and displays the specific information of the two types of terminals to the administrator on the management interface. The server only issues the update instruction to the terminals in the online list, does not perform any update operation on the terminals in the offline list, and marks the reason for not updating in the database.

[0068] For example, in the automobile parts factory described above, before the server prepares to perform version update on 10 terminals, the server checks the online state of each terminal, finds that terminal 5 and terminal 9 are in an offline state, and sends a prompt to the administrator. If the administrator does not perform further operations, the server does not send an update instruction to the two terminals, and only performs an update operation on the remaining 8 terminals.

[0069] The application avoids sending an update instruction to an offline terminal, prevents resource waste (such as network bandwidth and server processing capacity), and also ensures the effectiveness of the update operation, because the offline terminal cannot receive and execute the update instruction. Early detection can improve the update efficiency.

[0070] It should be noted that in addition to simply detecting the offline state, the network connection quality and hardware performance of the terminal can also be detected. For terminals with unstable network or insufficient hardware performance, the updating operation can be temporarily suspended.

[0071] In some optional implementations of the embodiment, after the first target terminal is updated based on the target incremental data, the method further comprises: generating version update information of each terminal; generating a synchronization report based on the terminal number, version information and version update information of each terminal.

[0072] The server extracts the update data of each terminal from the database, which can include terminal basic information, version information, update process information and result information, etc. The server structures the collected data according to a preset template, generates a synchronization report of the version update of each terminal, and stores the structured synchronization report to the database.

[0073] For example, in the above automobile parts factory, in one updating operation, terminal 4 fails to update. After the first target terminal (terminal 4) is updated through incremental data, the server generates version update information of each terminal, such as "terminal 1: update successful, version V1.3, update time 2025-07-04 09:00", "terminal 4: incremental update successful, version V1.3, update time 2025-07-04 09:10", etc. Then, a synchronization report is generated based on the terminal number, version information and these update information of each terminal, and the report clearly lists the relevant information of each terminal.

[0074] By generating a synchronization report, the application can intuitively display the version update status of each terminal, facilitate the administrator to understand the overall update status, discover problems (such as terminals not updated, terminals failed to update, etc.) in time and handle them, and improve the transparency and traceability of version management.

[0075] It should be noted that the form of the synchronization report can be a chart (such as a column chart, a pie chart), a visual dashboard, etc. The report content can also include terminal hardware information, historical update record comparison, etc.

[0076] It should be understood that although each step in the flowchart of the accompanying drawings is shown in sequence according to the direction of the arrow, these steps are not necessarily executed in sequence according to the direction of the arrow. Unless explicitly stated herein, the execution of these steps is not strictly limited in sequence, and they can be executed in other sequences. Moreover, at least part of the steps in the flowchart of the accompanying drawings can include multiple sub-steps or multiple stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution sequence is not necessarily sequential, but can be alternately executed with at least part of other steps or sub-steps or stages of other steps.

[0077] Further referring to Figure 2 , as an implementation of the method shown in the above Figure 1 , the present application provides an embodiment of a multi-terminal version data updating device, which corresponds to the method embodiment shown in Figure 1 , and the device can be applied to various electronic devices.

[0078] As shown in Figure 2 , the multi-terminal version data updating device 300 described in the embodiment includes an acquisition module 301, a version management module 302, and an incremental synchronization module 303. Among them: The acquisition module 301 is configured to acquire a new version data set and store it in a version library, wherein the new version data set includes new version data corresponding to a plurality of terminals respectively, and the version library includes a plurality of version data corresponding to each terminal; The version management module 302 is configured to perform version updating on a plurality of terminals based on the new version data set in the version library, to obtain an update result of the plurality of terminals, wherein the update result is update success or update failure; The incremental synchronization module 303 is configured to, in the case that the update result of a first target terminal is update failure, obtain target incremental data based on the new version data and the current version data of the first target terminal in the version library, and perform version updating on the first target terminal based on the target incremental data; wherein the first target terminal is any terminal in the plurality of terminals, and the target incremental data is the difference between the new version data and the current version data of the target terminal.

[0079] The multi-terminal version data updating device provided by the present application solves the problem of chaotic software version of multiple terminals in production by constructing an intelligent synchronization management system. Through accurate version identification, flexible update triggering, incremental synchronization retry, one-key version rollback, and visual report, efficient synchronization and rapid fault recovery are realized, and production continuity is ensured.

[0080] To solve the above technical problems, the embodiment of the present application also provides a multi-terminal version data updating system. For details, please refer to Figure 3 , Figure 3 The basic structure block diagram of the system of the embodiment is shown in the figure.

[0081] A multi-terminal version data updating system comprises a multi-terminal version data updating device and a plurality of terminals, and the device and the plurality of terminals are respectively in communication connection. The multi-terminal version data updating device is used for the method described in any one of the above. A system composed of a version data updating device and 20 terminals, the device and each terminal are in communication connection through a wireless network. The device performs the method of multi-terminal version data updating described above, acquires new version data and stores it, updates the online terminal, re-updates the terminal that fails to update through incremental data, generates a synchronization report, and so on, and each terminal cooperates with the device to complete the corresponding operation. The terminal 1 to terminal 20 are in communication connection with the version data updating device through a system bus.

[0082] The terminal can be an industrial control terminal (such as a PLC terminal for controlling the operating parameters of production equipment), an operation terminal (an industrial computer for production parameter setting and process monitoring by an operator), a detection terminal (a device terminal for detecting the quality, size, performance, etc. of a production product), a data acquisition terminal (a terminal responsible for acquiring various data in the production process), and a robot control terminal (a terminal for controlling an industrial robot to perform welding, assembly, and carrying operations). It should be noted that Figure 3 The number of terminals in the above embodiment is 20, and the number of terminals can be increased or decreased according to requirements.

[0083] The version data updating device can be an industrial server (a special server with high-performance computing, large-capacity storage, and stable network communication capability), an edge computing gateway (deployed in a local edge gateway device in an industrial Internet of Things scene), a distributed management node (a management system composed of a plurality of distributed nodes in a large factory, each node is responsible for a specific area or type of terminal), and a special industrial computer (an industrial control computer with server functions, integrating hardware and software modules required for version data updating).

[0084] The communication mode of the version data updating device and the terminal can be industrial Ethernet, wired network communication, or wireless network communication, to ensure smooth network communication between the server and the terminal, realize reliable transmission of version information, update instructions, incremental data, etc., and guarantee smooth execution of the multi-terminal version synchronization process.

[0085] The multi-terminal version data updating system of the application integrates version data updating devices and multiple terminals from the system level, realizes the overall process of multi-terminal version data updating through the communication connection between the devices and the terminals, ensures the complete implementation of the method in practical application, and meets the demand of multi-terminal version management in actual scenarios. The construction of the system forms a complete multi-terminal version data updating system, ensures the consistency of the versions of the terminals and the efficiency of the updating, and improves the stability and operation and maintenance efficiency of the whole system.

[0086] Obviously, the above-described embodiments are only some of the embodiments of the application, not all the embodiments, and the preferred embodiments of the application are given in the drawings, but do not limit the patent scope of the application. The application can be implemented in many different forms, and conversely, the purpose of providing these embodiments is to make the disclosure of the application more thorough and comprehensive. Although the application has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions recorded in the foregoing specific embodiments or make equivalent replacements to some technical features. Any equivalent structure made by using the content of the specification and drawings, directly or indirectly applied to other related technical fields, is also within the patent protection scope of the application.

Claims

1. A method for updating version data across multiple terminals, characterized in that, The method includes: The new version dataset is obtained, merged, and stored in the version repository. The new version dataset includes new version data corresponding to multiple terminals, and the version repository includes multiple version data corresponding to each terminal. Based on the new version data set in the version library, the versions of multiple terminals are updated to obtain update results for multiple terminals, wherein the update result is either successful or failed. If the update result of the first target terminal is an update failure, target incremental data is obtained based on the new version data and the current version data of the first target terminal in the version library. The first target terminal is any one of the multiple terminals, and the target incremental data is the data of the difference between the new version data and the current version data of the first target terminal. The first target terminal is updated based on the target incremental data.

2. The method according to claim 1, characterized in that, The process of obtaining the new version dataset and merging it into the version control repository includes: Obtain the preprocessed new version data for each of the terminals; The preprocessed new version data of each terminal is marked to obtain the new version data of each terminal. The new version data of the terminal includes the preprocessed new version data, the terminal number and the version information. The new version data set is generated based on the new version data of multiple terminals and stored in the version library.

3. The method according to claim 1, characterized in that, After updating the version of the first target terminal based on the target incremental data, the process further includes: Real-time monitoring of the operating status of multiple terminals; When a second target terminal with abnormal operation is detected among the multiple terminals, the historical version data of the second target terminal is obtained; Based on the historical version data, a rollback operation is performed on the version data currently running on the second target terminal.

4. The method according to claim 3, characterized in that, When a second target terminal with abnormal operation is detected among the multiple terminals, obtaining the historical version data of the second target terminal includes: Obtain the terminal number and version information of the second target terminal; Based on the terminal number and version information of the second target terminal, historical version data of the second target terminal are obtained from the version library.

5. The method according to claim 1, characterized in that, The process of updating the versions of multiple terminals based on the new version data set in the version repository, and obtaining the update results for the multiple terminals, includes: According to a preset update cycle, multiple terminals are updated to obtain update results for multiple terminals.

6. The method according to any one of claims 1-5, characterized in that, Before updating the versions of the multiple terminals based on the new version data set in the version repository to obtain the update results of the multiple terminals, the method further includes: Offline status detection is performed on multiple terminals to filter out third target terminals that are offline; Perform a version update operation on all terminals except the third target terminal among the multiple terminals.

7. The method according to claim 6, characterized in that, After updating the version of the first target terminal based on the target incremental data, the method further includes: Generate version update information for each of the terminals; A synchronization report is generated based on the terminal number, version information, and version update information of each terminal.

8. A multi-terminal version data update device, characterized in that, include: The acquisition module is used to acquire a new version dataset and store it in a version repository. The new version dataset includes new version data corresponding to multiple terminals respectively, and the version repository includes multiple version data corresponding to each terminal. The version management module is used to update the versions of multiple terminals based on the new version data set in the version repository, and obtain the update results of the multiple terminals, wherein the update result is either successful or failed. The incremental synchronization module is used to obtain target incremental data based on the new version data and the current version data of the first target terminal in the version library when the update result of the first target terminal is an update failure, and to update the version of the first target terminal based on the target incremental data; wherein, the first target terminal is any one of the multiple terminals, and the target incremental data is the data of the difference between the new version data and the current version data of the first target terminal.

9. A multi-terminal version data update system, characterized in that, The device includes a version data update device for multiple terminals and multiple terminals, wherein the version data update device for multiple terminals is communicatively connected to each of the multiple terminals, and the version data update device for multiple terminals is used to perform the method described in any one of claims 1-7.

Images