MES system intelligent upgrade management system and method based on front-end and back-end separation architecture

Abstract

The invention discloses an MES system intelligent upgrade management system and method based on a front-end and back-end separation architecture. The system comprises a front end, a back end and an API interface layer. Wherein a WebSocket technology is applied to the API interface layer, and the API interface layer is used for communication interaction between a front end and a rear end; the front end is used for prompting information to a user and receiving an instruction input by the user, acquiring a node selected to be upgraded by the user based on the instruction, and issuing an operation instruction to the rear end through the API interface layer; and the rear end is used for paralleling a multi-node upgrading task according to the operation instruction and feeding back information generated in the process of executing the upgrading task to the front end through the API interface layer. The MES upgrading efficiency, stability and flexibility can be greatly improved, manual intervention is reduced, and a more efficient, safer and more intelligent solution is provided for system upgrading in a large-scale production environment.

Description

Technical Field

[0001] The present invention relates to automated operation and maintenance management in the field of manufacturing execution systems, and in particular to an MES system intelligent upgrade management system and method based on a front-end and back-end separation architecture. Background Art

[0002] In modern manufacturing enterprises, MES systems are widely used for production management and real-time data collection. As the functions of MES systems continue to expand, the system upgrade process becomes more and more complicated. However, existing upgrade tools have certain defects in managing MES system upgrades.

[0003] The existing MES system upgrade relies on manual intervention, and the operation steps are cumbersome and prone to human errors. The existing system also lacks environmental pre-detection functions and cannot detect known problems before upgrading. The upgrade process lacks flexibility and adaptability, and cannot customize the upgrade process according to different user needs or system environments. During the upgrade process, users cannot view the upgrade status in real time, and after the upgrade is completed, the availability of the project and system cannot be automatically verified. There is a lack of complete records of each upgrade process, and the upgrade records are not fully saved, making it impossible to achieve traceability. Once an error occurs during the upgrade process, the existing technology only provides vague error logs, which cannot clearly indicate the failed database statement, its execution time, and the specific location where the error occurred, causing technicians to spend a lot of time on troubleshooting, and the rollback mechanism has not been fully implemented. When the upgrade fails, it cannot automatically restore to the state before the upgrade.

[0004] In contrast, traditional EXE upgrade tools are usually stand-alone and designed for single client operations, and cannot effectively support automated deployment and upgrades in distributed environments. Such tools usually rely on manual operations and local execution, and cannot be centrally managed and collaboratively updated across multiple nodes or clients.

[0005] Based on the defects of the prior art, the present invention proposes an MES system intelligent upgrade management system and method based on a front-end and back-end separation architecture. Summary of the invention

[0006] The main purpose of the present invention is to provide an MES system intelligent upgrade management system and method based on a front-end and back-end separation architecture, which solves the problems faced in traditional MES system upgrade management.

[0007] The technical solution adopted by the present invention is: an MES system intelligent upgrade management system based on a front-end and back-end separation architecture, the system includes a front-end, a back-end and an API interface layer; wherein:

[0008] The API interface layer applies WebSocket technology for communication interaction between the front end and the back end; the front end is used to prompt information to the user and receive instructions input by the user, obtain the node selected by the user for upgrade based on the instructions, and send operation instructions to the back end through the API interface layer; the back end is used to perform upgrade tasks for multiple nodes in parallel according to the operation instructions, and feed back information generated during the execution of the upgrade task to the front end through the API interface layer.

[0009] The front end is deployed on a platform, and the platform includes a web browser, Windows, macOS, and Linux operating systems. Further, the method for starting the front end includes determining whether a default browser exists on the user end, and if so, directly opening the web page for upgrading through the default browser; if not, prompting the user to manually access the web page for upgrading.

[0010] According to the above technical solution, the backend is hosted in the cloud or local server, including a backup and recovery module, a real-time step and feedback module, a service status detection module and a statement database;

[0011] Among them, the backup and recovery module is used to back up and store the nodes selected by the user for upgrade; the real-time step and feedback module is used to determine whether the conditions for normal upgrade are met, record and store unmet upgrade conditions, real-time upgrade progress and information generated in the upgrade task, and feedback to the front end through the API interface layer; the service status detection module is used to detect whether there are any abnormalities in the system's service operation after completing the upgrade task; the statement database is used to store statements for executing upgrade tasks.

[0012] According to the above technical solution, the upgrade tasks performed by the backend include:

[0013] According to the operation instructions issued by the front end, obtain the node selected by the user for upgrading;

[0014] Determine whether the user customizes the upgrade steps; if the upgrade steps are not customized, the upgrade process of multiple nodes is carried out in parallel and the upgrade progress is returned to the front end in real time; if the upgrade steps are customized, determine whether the normal upgrade requirements are met. If not, feedback the unmet requirements to the front end, otherwise, the upgrade process of multiple nodes is carried out in parallel and the upgrade progress is returned to the front end in real time;

[0015] Monitor whether errors occur in each node during the upgrade process. If an error occurs in a node, terminate the upgrade of the node, feedback the upgrade error information to the front end, restore the node according to the upgrade restart instruction received from the front end, and re-execute the upgrade process of the node; otherwise, complete the upgrade of each node and feedback the upgrade completion information to the front end, and record the statement for executing the upgrade task; wherein the upgrade completion information includes the upgrade report of each node; the upgrade error information includes the step that generated the error and the execution time of the error operation;

[0016] Check whether the system service is running normally. If there is an abnormality, record the abnormal information for operation and maintenance.

[0017] According to the above technical solution, the upgrade process for each node includes: decompressing the upgrade package, shutting down the node service, backing up the node's engineering files and database, overwriting the upgrade package, updating the database, and restarting the node service.

[0018] According to the above technical solution, the restoration process of each node includes: detecting whether the node has a backup that meets the requirements, and if so, performing the restoration process; otherwise, feeding back backup error information to the front end;

[0019] Monitor whether errors occur during the restoration process. If no errors occur, feedback restoration completion information to the front end; otherwise, feedback restoration error information to the front end, and re-execute the restoration process of the node based on the restoration restart instruction received from the front end.

[0020] According to the above technical solution, the process of restoring the node includes: shutting down the node service, restoring the node's project files and database to the backup project files and backup database respectively, restarting the node service and checking whether it is running normally.

[0021] According to the above technical solution, the content of the upgrade task is adjusted based on the user configuration behavior received by the front end.

[0022] According to the above technical solution, the upgrade process is adjusted based on the user configuration behavior received by the front end.

[0023] Another aspect of the present invention provides an MES system intelligent upgrade management method based on a front-end and back-end separation architecture, the system is adapted to the above-mentioned MES system intelligent upgrade management system based on a front-end and back-end separation architecture, including:

[0024] Based on the instructions input by the user, the node selected by the user for upgrading is obtained to form an operation instruction;

[0025] The upgrade tasks of multiple nodes are performed in parallel based on the operation instructions, and information generated during the execution of the upgrade tasks is fed back to the user.

[0026] The beneficial effects of the present invention are as follows: the present invention provides an MES system intelligent upgrade management system and method based on a front-end and back-end separation architecture, and the upgrade tool of the front-end and back-end separation architecture adopted can provide better cross-platform support, automated deployment, centralized management and distributed support compared to traditional EXE tools, and can significantly improve the upgrade efficiency, reliability and user experience, and is suitable for modern applications and distributed systems. The present invention is based on the instructions input by the user at the front end, and performs system upgrades at the back end. If an error occurs during the upgrade process, the system is restored according to the backup and the upgrade task is restarted. Finally, after the upgrade is completed, detection is performed and timely operation and maintenance are carried out.

[0027] The upgrade process of the present invention can be fully automated, can reduce manual intervention, and improve upgrade efficiency and accuracy. The present invention pre-evaluates existing conditions before upgrading to ensure that there will be no failure due to environmental problems before upgrading. The present invention can meet the needs of users to customize the upgrade process according to actual needs and improve the adaptability of system upgrades. The present invention can push the upgrade progress, status information, error reports, etc. of the backend to users in real time, greatly improving the user experience. The present invention is designed with a restore mechanism, which can restore to a normal state with one click when the system upgrade fails, avoiding manual recovery operations, reducing system downtime, and ensuring the stability of the system and the continuity of the production environment. After the upgrade is completed, the present invention can automatically verify the upgrade results to ensure the availability of the project and the system.

[0028] Furthermore, the present invention can accurately record the execution time and error location of each operation during the upgrade process, thereby quickly locating the erroneous statement and providing debugging commands to help technicians quickly fix the problem and improve the efficiency of troubleshooting.

[0029] Furthermore, the detailed process of each upgrade will be automatically recorded and stored as an upgrade report to ensure the traceability of each round of upgrades and facilitate subsequent inquiries and problem tracing.

[0030] Furthermore, the backend system adopts a service model design to support continuous online operation. Whenever an upgrade task is completed, the system will be immediately ready for the next round of upgrades without interruption or reconfiguration, which improves the automation and efficiency of the system.

[0031] Furthermore, the present invention can realize incremental upgrade, that is, in the next upgrade, only the newly added content is upgraded by comparing the historical records. The system will only update the newly added parts since the last upgrade without re-executing all statements. This mechanism significantly improves the update efficiency of database statements, avoids repeated operations, saves time and resources, and is particularly suitable for scenarios with frequent updates.

[0032] Of course, any product implementing the present invention does not necessarily need to achieve all of the advantages described above at the same time. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0034] Figure 1 It is a structural diagram of an MES system intelligent upgrade management system based on a front-end and back-end separation architecture according to an embodiment of the present invention;

[0035] Figure 2 It is a logic diagram of a multi-node architecture of an MES system intelligent upgrade management method based on a front-end and back-end separation architecture according to an embodiment of the present invention.

[0036] Figure 3 It is a flowchart of the upgrade task performed by the back end of the MES system intelligent upgrade management system based on the front-end and back-end separation architecture according to an embodiment of the present invention;

[0037] Figure 4 It is a logic diagram of the upgrade task performed by the back end of the MES system intelligent upgrade management system based on the front-end and back-end separation architecture according to an embodiment of the present invention;

[0038] Figure 5 It is a flowchart of the restoration process performed by the back end of the MES system intelligent upgrade management system based on the front-end and back-end separation architecture according to an embodiment of the present invention;

[0039] Figure 6 It is a logic diagram of the restoration process performed by the back end of the MES system intelligent upgrade management system based on the front-end and back-end separation architecture according to an embodiment of the present invention;

[0040] Figure 7 It is a flow chart of an MES system intelligent upgrade management method based on a front-end and back-end separation architecture according to an embodiment of the present invention. DETAILED DESCRIPTION

[0041] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0042] It should be noted that the illustrations provided in the embodiments of the present invention are only used to illustrate the basic concept of the present invention in a schematic manner. Therefore, the drawings only show components related to the present invention rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout type may also be more complicated.

[0043] In the present invention, it is also necessary to explain that, if the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", etc. appear, the orientation or position relationship indicated is based on the orientation or position relationship shown in the drawings, which is only for the convenience of describing the present application and simplifying the description, and does not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the present application. In addition, if the terms "first" and "second" appear, they are only used for description and distinction purposes, and cannot be understood as indicating or implying relative importance.

[0044] Example 1

[0045] This embodiment provides an MES system intelligent upgrade management system based on a front-end and back-end separation architecture, the structure of which is as follows: Figure 1 As shown, it includes the front-end, back-end and API interface layers.

[0046] The front end is used to prompt information to the user and receive instructions input by the user, obtain the nodes selected by the user for upgrade based on the instructions, and send operation instructions to the back end through the API interface layer; the back end is used to perform upgrade tasks for multiple nodes in parallel according to the operation instructions, and feed back information generated during the execution of the upgrade tasks to the front end through the API interface layer.

[0047] Based on the above description, the logic of the multi-node architecture of the MES system intelligent upgrade management method based on the front-end and back-end separation architecture is as follows Figure 2 shown.

[0048] Specifically, the front end is deployed on a platform. This architecture enables a user to manage multiple nodes located in different locations and operating systems through a front end. The platform includes a web browser, Windows, macOS, and Linux operating systems. The method for starting the front end includes determining whether a default browser exists. If so, directly opening a web page for upgrading through the default browser; if not, prompting the user to manually access the web page for upgrading.

[0049] Specifically, the backend is hosted in the cloud or a local server, and includes a backup and recovery module, a real-time step and feedback module, a service status detection module, and a statement database.

[0050] Among them, the backup and recovery module is used to back up and store the nodes selected by the user for upgrade; the real-time step and feedback module is used to determine whether the conditions for normal upgrade are met, record and store the unmet upgrade conditions, real-time upgrade progress and information generated in the upgrade task, and feedback to the front end through the API interface layer. The user can query the real-time returned upgrade progress at any time to ensure that the upgrade process is not interrupted; the service status detection module is used to detect whether there are any abnormalities in the system service operation after completing the upgrade task; the statement database is used to store statements for executing upgrade tasks.

[0051] Furthermore, the backend is used to perform the upgrade task process as follows: Figure 3 As shown, including:

[0052] S1. According to the operation instructions issued by the front end, obtain the node selected by the user to upgrade.

[0053] S2. Determine whether the user customizes the upgrade steps; when the upgrade steps are not customized, perform the upgrade process of multiple nodes in parallel and return the upgrade progress to the front end in real time; when the upgrade steps are customized, determine whether the normal upgrade requirements are met. If not, feedback the unmet requirements to the front end, otherwise, perform the upgrade process of multiple nodes in parallel and return the upgrade progress to the front end in real time.

[0054] Furthermore, the upgrade process for each node includes: unzipping the upgrade package, shutting down the node's service, backing up the node's engineering files and database, overwriting the upgrade package, updating the database, and restarting the node's service.

[0055] S3. Monitor whether errors occur in each node during the upgrade process. When an error occurs in a node, terminate the upgrade of the node, feedback the upgrade error information to the front end, restore the node according to the upgrade restart instruction received from the front end, and re-execute the upgrade process of the node; otherwise, complete the upgrade of each node and feedback the upgrade completion information to the front end, and record the statement for executing the upgrade task; wherein, the upgrade completion information includes the upgrade report of each node; the upgrade error information includes the step where the error occurred and the execution time of the erroneous operation.

[0056] Furthermore, the restoration process for each node is as follows: Figure 5 As shown, it includes: T1, detecting whether the node has a backup that meets the requirements, and if so, performing the restoration process; otherwise, feeding back backup error information to the front end;

[0057] T2. Monitor whether errors occur during the restoration process. If no errors occur, feedback restoration completion information to the front end; otherwise, feedback restoration error information to the front end, and re-execute the restoration process of the node according to the restoration restart instruction received from the front end.

[0058] The process of restoring a node includes: shutting down the node service, restoring the node's project files and database to the backup project files and backup database respectively, restarting the node service and checking whether it is running normally.

[0059] Based on the above description, the logic of the backend to perform the upgrade task is as follows Figure 6 shown.

[0060] S4. Check whether the system service is running normally. If there is an abnormality, record the abnormal information for operation and maintenance. By setting this step, if a service abnormality is detected, the operation and maintenance personnel can be notified in time to handle it by querying and upgrading the error information to ensure the continuous normal operation of the system.

[0061] Based on the above description, the logic of the backend to perform the upgrade task is as follows Figure 4 shown.

[0062] Specifically, the adjustment of the upgrade task is based on the user instructions received by the front end. The user can independently upgrade the database through the configuration file and flexibly control other parts of the upgrade process. For example, the user can configure whether to skip the backup step through the operation interface to meet urgent update needs.

[0063] Specifically, if the next round of upgrades is required for the system to be upgraded, the historical records of the statements for executing the upgrade tasks stored in the statement database are compared, and only the newly added statements are updated. Users can selectively execute certain database statements instead of re-executing all operations. Recording the database statements executed during each upgrade process can provide a data basis for subsequent upgrades. During the next upgrade, the historical records are compared and only the newly added database statements are executed. In this way, the system will only update the newly added parts since the last upgrade without re-executing all statements. It can significantly improve the update efficiency of database statements, avoid repeated operations, save time and resources, and is suitable for scenarios with frequent updates.

[0064] Specifically, the system to be upgraded does not need to be interrupted or reconfigured between each round of upgrade tasks. After each upgrade task is completed, the system will be immediately ready for the next round of upgrade.

[0065] Example 2

[0066] This embodiment provides an MES system intelligent upgrade management method based on a front-end and back-end separation architecture. The implementation of this method is based on the MES system intelligent upgrade management system based on a front-end and back-end separation architecture described in Example 1. Figure 7 As shown, including:

[0067] P1. Based on the instructions input by the user, the node selected by the user for upgrading is obtained to form an operation instruction.

[0068] The implementation of this step is based on the front end in the MES system intelligent upgrade management system based on the front-end and back-end separation architecture described in Example 1. The composition and functions of the front end have been described in Example 1 and will not be repeated here.

[0069] P2. Perform upgrade tasks on multiple nodes in parallel based on the operation instructions, and feed back information generated during the execution of the upgrade tasks to the user.

[0070] The implementation of this step is based on the backend and API interface layer in the MES system intelligent upgrade management system based on the front-end and back-end separation architecture described in Example 1. The composition and functions of the backend and API interface layer have been explained in Example 1 and will not be repeated here.

[0071] In summary, the present invention provides an MES system intelligent upgrade management system and method based on a front-end and back-end separation architecture, in which the front end receives user instructions and makes judgments, issues operation instructions to the back end, and the back end performs multi-node upgrade tasks in parallel according to the operation instructions of the front end and feeds back information to the front end to complete the intelligent upgrade management of the MES system. The present invention greatly improves the efficiency, stability and flexibility of MES system upgrades, reduces manual intervention, enhances the reliability of the system, and provides a more efficient, safe and intelligent solution for system upgrades in large-scale production environments.

[0072] It should be pointed out that, according to the needs of implementation, the various steps / components described in this application can be split into more steps / components, and two or more steps / components or partial operations of steps / components can be combined into new steps / components to achieve the purpose of the present invention.

[0073] The order of execution of each step in the above embodiment does not mean the order of execution. The order of execution of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.

[0074] It should be understood that those skilled in the art can make improvements or changes based on the above description, and all these improvements and changes should fall within the scope of protection of the appended claims of the present invention.

Claims

1. An MES system intelligent upgrade management system based on front-end and back-end separation architecture, characterized in that: The system includes front-end, back-end and API interface layers; among which: The API interface layer applies WebSocket technology for communication interaction between the front end and the back end; the front end is used to prompt information to the user and receive instructions input by the user, obtain the node selected by the user for upgrade based on the instructions, and send operation instructions to the back end through the API interface layer; the back end is used to perform upgrade tasks for multiple nodes in parallel according to the operation instructions, and feed back information generated during the execution of the upgrade task to the front end through the API interface layer.

2. According to claim 1, the MES system intelligent upgrade management system based on the front-end and back-end separation architecture is characterized in that: The front end is arranged on a platform, and the platform includes a Web browser, Windows, macOS, and Linux operating systems.

3. According to claim 1, the MES system intelligent upgrade management system based on the front-end and back-end separation architecture is characterized in that: The backend is set in the cloud or local server, including a backup and recovery module, a real-time step and feedback module, a service status detection module, an operation execution module and a statement database; Among them, the backup and recovery module is used to back up and store the nodes selected by the user for upgrade; the real-time step and feedback module is used to determine whether the conditions for normal upgrade are met, record and store the unmet upgrade conditions, real-time upgrade progress and information generated during the execution of the upgrade task, and feedback to the front end through the API interface layer; the service status detection module is used to detect whether there are any abnormalities in the service operation of the system after completing the upgrade task; the operation execution module is used to perform the node upgrade process and restore process; the statement database is used to store statements for executing upgrade tasks.

4. According to claim 3, the MES system intelligent upgrade management system based on the front-end and back-end separation architecture is characterized in that: The upgrade tasks performed by the backend include: According to the operation instructions issued by the front end, obtain the node selected by the user for upgrading; Determine whether the user customizes the upgrade steps; if the upgrade steps are not customized, the upgrade process of multiple nodes is carried out in parallel and the upgrade progress is returned to the front end in real time; if the upgrade steps are customized, determine whether the normal upgrade requirements are met. If not, feedback the unmet requirements to the front end, otherwise, the upgrade process of multiple nodes is carried out in parallel and the upgrade progress is returned to the front end in real time; Monitor whether errors occur in each node during the upgrade process. If an error occurs in a node, terminate the upgrade of the node, feedback the upgrade error information to the front end, restore the node according to the upgrade restart instruction received from the front end, and re-execute the upgrade process of the node; otherwise, complete the upgrade of each node and feedback the upgrade completion information to the front end, and record the statement for executing the upgrade task; wherein the upgrade completion information includes the upgrade report of each node; the upgrade error information includes the step that generated the error and the execution time of the error operation; Check whether the system service is running normally. If there is an abnormality, record the abnormal information for operation and maintenance.

5. According to claim 4, the MES system intelligent upgrade management system based on the front-end and back-end separation architecture is characterized in that: The upgrade process for each node includes: unzipping the upgrade package, shutting down the node service, backing up the node's project files and database, overwriting the upgrade package, updating the database, and restarting the node service.

6. The MES system intelligent upgrade management system based on the front-end and back-end separation architecture according to claim 5 is characterized in that: The restoration process for each node includes: detecting whether there is a backup that meets the requirements for the node, and if so, performing the restoration process; otherwise, feeding back backup error information to the front end; Monitor whether errors occur during the restoration process. If no errors occur, feedback restoration completion information to the front end; otherwise, feedback restoration error information to the front end, and re-execute the restoration process of the node based on the restoration restart instruction received from the front end.

7. The MES system intelligent upgrade management system based on the front-end and back-end separation architecture according to claim 6 is characterized in that: The process of restoring a node includes: shutting down the node service, restoring the node's project files and database to the backup project files and backup database respectively, restarting the node service and checking whether it is running normally.

8. The MES system intelligent upgrade management system based on the front-end and back-end separation architecture according to claim 1 is characterized in that: There is no need for interruption or reconfiguration between each round of upgrade tasks performed by the backend.

9. The MES system intelligent upgrade management system based on the front-end and back-end separation architecture according to claim 1 is characterized in that: The content of the upgrade task is adjusted based on the user configuration behavior received by the front end.

10. A method for intelligent upgrade management of an MES system based on a front-end and back-end separation architecture, the method being executed based on the MES system intelligent upgrade management system based on a front-end and back-end separation architecture as claimed in any one of claims 1 to 9, characterized in that: include: Based on the instructions input by the user, the node selected by the user for upgrading is obtained to form an operation instruction; The upgrade tasks of multiple nodes are performed in parallel based on the operation instructions, and information generated during the execution of the upgrade tasks is fed back to the user.

Images