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

Abstract

The application discloses an MES system intelligent upgrade management system and method based on a front-end and rear-end separation architecture, wherein the system comprises a front end, a rear end and an API interface layer; the API interface layer is applied with a WebSocket technology and is used for communication interaction between the front end and the 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 by the user for upgrading based on the instruction, and issuing an operation instruction to the rear end through the API interface layer; the rear end is used for upgrading tasks of multiple nodes in parallel according to the operation instruction and feeding back information generated in the process of executing the upgrading tasks to the front end through the API interface layer. The application can greatly improve the efficiency, stability and flexibility of the MES system upgrading, reduce manual intervention, and provide a more efficient, safe and intelligent solution for system upgrading in a large-scale production environment.

Description

TECHNICAL FIELD

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

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

[0003] The existing MES system upgrade relies on manual intervention, with complicated operation steps and prone to human error. 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 system cannot automatically verify the availability of the project and the system, lacks 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 statements, their execution time, and the specific location of the error occurrence, resulting in a large amount of time spent by technical personnel in troubleshooting, and the rollback mechanism has not been fully implemented, making it impossible to automatically restore to the pre-upgrade state when the upgrade fails.

[0004] To match, traditional EXE upgrade tools are usually single-machine versions, designed mainly 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 between multiple nodes or clients.

[0005] Based on the defects of the existing technology, the present application proposes an MES system intelligent upgrade management system and method based on a front-end and back-end separation architecture. SUMMARY

[0006] The main purpose of the present application 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 application is: an MES system intelligent upgrade management system based on a front-end and back-end separation architecture, which 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 a user and receive an instruction input by the user, obtain a node selected by the user for upgrade based on the instruction, and issue an operation instruction to the back end through the API interface layer; and the back end is used to perform upgrade tasks of multiple nodes in parallel according to the operation instruction and feed back information generated in the process of performing the upgrade tasks 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 a Linux operating system. Further, a method for starting the front end includes determining whether a default browser exists on a user terminal, directly opening a webpage for upgrade through the default browser if the default browser exists, and prompting a user to manually access the webpage for upgrade if the default browser does not exist.

[0010] According to the technical solution, the back end is hosted in a cloud or a local server and includes a backup and recovery module, a real-time step and feedback module, a service state detection module, and a statement database.

[0011] The backup and recovery module is used to backup and store the node selected by the user for upgrade; the real-time step and feedback module is used to determine whether a condition for normal upgrade is met, record and store an upgrade condition that is not met, a real-time upgrade progress, and information generated in an upgrade task, and feed back to the front end through the API interface layer; the service state detection module is used to detect whether an abnormality exists in service running of a system after completion of the upgrade task; and the statement database is used to store a statement for performing the upgrade task.

[0012] According to the technical solution, the upgrade task performed by the back end includes:

[0013] According to the operation instruction issued by the front end, the node selected by the user for upgrade is obtained.

[0014] It is determined whether the user customizes an upgrade step; when the upgrade step is not customized, the upgrade process of multiple nodes is performed in parallel, and an upgrade progress is returned to the front end in real time; when the upgrade step is customized, it is determined whether a requirement for normal upgrade is met; when the requirement is not met, a requirement that is not met is fed back to the front end; otherwise, the upgrade process of multiple nodes is performed in parallel, and an upgrade progress is returned to the front end in real time.

[0015] Monitor whether errors occur in the nodes during the upgrading process, terminate the upgrading of the node when an error occurs in the node, feed back the upgrading error information to the front end, restore the node according to the received upgrading restart instruction from the front end, re-execute the upgrading process of the node; otherwise, complete the upgrading of the nodes and feed back the upgrading completion information to the front end, record the statement of executing the upgrading task; wherein the upgrading completion information includes the upgrading report of each node; the upgrading error information includes the step of generating the error and the execution time of the error operation.

[0016] Detect whether the service of the system runs normally, and record abnormal information for operation and maintenance if there is an abnormality.

[0017] According to the above technical solution, the upgrading process of each node includes: decompressing the upgrade package, closing the service of the node, backing up the engineering file and the database of the node, covering the upgrade package, updating the database, and restarting the service of the node.

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

[0019] Monitor whether errors occur in the restoration process, feed back the restoration completion information to the front end if no error occurs; otherwise, feed back the restoration error information to the front end, and re-execute the restoration process of the node according to the received restoration restart instruction from the front end.

[0020] According to the above technical solution, the process of restoring the node includes: closing the service of the node, restoring the engineering file and the database of the node to the backup engineering file and the backup database respectively, restarting the service of the node and detecting whether it runs normally.

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

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

[0023] Another aspect of the present application provides an intelligent upgrading management method of an MES system based on a front-end and back-end separation architecture, which is adapted to the intelligent upgrading management system of the MES system based on the front-end and back-end separation architecture, and includes:

[0024] Form an operation instruction based on the instruction input by the user to select the node to be upgraded.

[0025] Parallelly execute the upgrading tasks of the nodes based on the operation instruction, and feed back the information generated during the execution of the upgrading task to the user.

[0026] The beneficial effects of this invention are as follows: This invention provides an intelligent upgrade management system and method for MES systems based on a front-end and back-end separation architecture. Compared to traditional EXE tools, the upgrade tool using this architecture offers better cross-platform support, automated deployment, centralized management, and distributed support, significantly improving upgrade efficiency, reliability, and user experience. It is suitable for modern applications and distributed systems. This invention upgrades the system on the back-end based on user-input commands on the front-end. If errors occur during the upgrade process, the system is restored from backups and the upgrade task is restarted. Finally, after the upgrade is completed, a check is performed for timely maintenance.

[0027] The upgrade process of this invention is fully automated, reducing manual intervention and improving upgrade efficiency and accuracy. Before upgrading, this invention pre-assesses existing conditions to ensure that upgrades will not fail due to environmental issues. This invention allows users to customize the upgrade process according to their actual needs, improving the adaptability of system upgrades. This invention can push backend upgrade progress, status information, and error reports to users in real time, greatly enhancing the user experience. This invention is designed with a restore mechanism, enabling one-click restoration to a normal state in the event of a system upgrade failure, avoiding manual recovery operations, reducing system downtime, and ensuring system stability and production environment continuity. After the upgrade is completed, this invention can automatically verify the upgrade results, ensuring the availability of the project and the system.

[0028] Furthermore, this 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 problems and improve the efficiency of troubleshooting.

[0029] Furthermore, the detailed process of each upgrade is automatically recorded and stored as an upgrade report, ensuring the traceability of each round of upgrades and facilitating subsequent inquiries and problem tracing.

[0030] Furthermore, the backend system adopts a service-oriented design, supporting continuous online operation. Once an upgrade task is completed, the system is immediately ready for the next upgrade, without interruption or reconfiguration, thus improving system automation and efficiency.

[0031] Furthermore, this invention enables incremental upgrades, meaning that in the next upgrade, only newly added content is upgraded by comparing historical records. The system only updates the parts added since the last upgrade, without re-executing all statements. This mechanism significantly improves the efficiency of database statement updates, avoids repetitive operations, and saves time and resources, making it particularly suitable for scenarios with frequent updates.

[0032] Of course, any product implementing this invention does not necessarily need to achieve all of the advantages described above at the same time. Attached Figure Description

[0033] In order to more clearly illustrate the technical solutions of the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or prior art description. Obviously, the drawings in the following description are some embodiments of the present application, and other drawings can also be obtained by those skilled in the art without creative labor.

[0034] Figure 1 is the intelligent upgrade management system structure diagram of the MES system based on the front-end and back-end separation architecture of the embodiments of the present application;

[0035] Figure 2 is the logic diagram of the multi-node architecture of the intelligent upgrade management method of the MES system based on the front-end and back-end separation architecture of the embodiments of the present application.

[0036] Figure 3 is the flowchart of the upgrade task executed by the back-end of the intelligent upgrade management system of the MES system based on the front-end and back-end separation architecture of the embodiments of the present application;

[0037] Figure 4 is the logic diagram of the upgrade task executed by the back-end of the intelligent upgrade management system of the MES system based on the front-end and back-end separation architecture of the embodiments of the present application;

[0038] Figure 5 is the flowchart of the restoration process executed by the back-end of the intelligent upgrade management system of the MES system based on the front-end and back-end separation architecture of the embodiments of the present application;

[0039] Figure 6 is the logic diagram of the restoration process executed by the back-end of the intelligent upgrade management system of the MES system based on the front-end and back-end separation architecture of the embodiments of the present application;

[0040] Figure 7 is the flowchart of the intelligent upgrade management method of the MES system based on the front-end and back-end separation architecture of the embodiments of the present application. DETAILED DESCRIPTION

[0041] In order to make the purpose, technical solutions and advantages of the present application more clear, the following will further describe the present application in combination with the drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application, and not used to limit the present application.

[0042] It should be noted that the diagrams provided in the embodiments of the present application only illustrate the basic concept of the present application in a schematic manner, and therefore, the diagrams only show the components related to the present application, but not drawn according to the number, shape and size of the components in actual implementation. The type, number and proportion of each component in actual implementation can be arbitrarily changed, and the component layout type can also be more complex.

[0043] In the present application, it is also necessary to point out that, as the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer" and the like appear, the indicated orientation or positional relationship is based on the orientation or positional relationship shown in the drawings, only for the convenience of describing the present application and simplifying the description, and is not indicative or suggestive of the device or element referred to must have a particular orientation, be constructed and operated in a particular orientation, and therefore cannot be understood as a limitation on the present application. In addition, as the terms "first", "second" appear, only for description and differentiation purposes, and cannot be understood as indicative or suggestive of relative importance.

[0044] Embodiment 1

[0045] The present embodiment provides an MES system intelligent upgrade management system based on a front-end and back-end separation architecture, which has a structure as shown in Figure 1 The structure includes a front-end, a back-end and an API interface layer.

[0046] The front-end is used to prompt information to the user and receive user input instructions, based on which the user-selected upgrade node is obtained, and operation instructions are issued to the back-end through the API interface layer; the back-end is used to perform parallel multi-node upgrade tasks according to the operation instructions, and feedback the information generated during the execution of the upgrade task process 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 shown in Figure 2 .

[0048] Specifically, the front-end is deployed on a platform, which enables users to manage multiple nodes located in different locations and operating systems through one front-end, and the platform includes a Web browser, Windows, macOS, Linux operating system. The method of starting the front-end includes judging whether there is a default browser, if there is, directly opening the webpage for upgrade through the default browser; if not, prompting the user to manually access the webpage for upgrade.

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

[0050] The backup and recovery module is configured to backup and store the nodes selected by the user for upgrade; the real-time step and feedback module is configured to judge whether the conditions for normal upgrade are met, record and store the information generated in the upgrade conditions not met, real-time upgrade progress and upgrade tasks, and feed back to the front end through the API interface layer, so that the user can query the real-time returned upgrade progress at any time, and ensure that the upgrade process is not interrupted; the service state detection module is configured to detect whether the service operation of the system is abnormal after the upgrade task is completed; and the statement database is configured to store the statements for executing the upgrade task.

[0051] Further, the upgrade task process performed by the backend is as shown in Figure 3 , and includes the following steps.

[0052] S1. According to the operation instruction issued by the front end, the nodes selected by the user for upgrade are obtained.

[0053] S2. It is judged whether the user customizes the upgrade steps; when the upgrade steps are not customized, the upgrade process of the multiple nodes in parallel is performed and the upgrade progress is returned to the front end in real time; when the upgrade steps are customized, it is judged whether the requirements for normal upgrade are met; when the requirements are not met, the requirements not met are fed back to the front end, otherwise, the upgrade process of the multiple nodes in parallel is performed and the upgrade progress is returned to the front end in real time.

[0054] Further, the upgrade process performed on each node includes decompressing the upgrade package, shutting down the service of the node, backing up the engineering files and the database of the node, covering the upgrade package, updating the database, and restarting the service of the node.

[0055] S3. It is monitored whether errors occur in the upgrade process of each node; when errors occur in the node, the upgrade of the node is terminated, the upgrade error information is fed back to the front end, the node is restored according to the received upgrade restart instruction from the front end, and the upgrade process of the node is re-executed; otherwise, the upgrade of each node is completed, the upgrade completion information is fed back to the front end, and the statements for executing the upgrade task are recorded; wherein the upgrade completion information includes the upgrade report of each node; and the upgrade error information includes the step where the error occurs and the execution time of the error operation.

[0056] Further, the process of the restoration process performed on each node is as shown in Figure 5 , and includes the following steps.

[0057] T2. It is monitored whether errors occur in the restoration process; if no error occurs, the restoration completion information is fed back to the front end; otherwise, the restoration error information is fed back to the front end, and the restoration process of the node is re-executed according to the received restoration restart instruction from the front end.

[0058] The process of restoring the node includes: closing the service of the node, restoring the engineering file and the database of the node to the backup engineering file and the backup database respectively, restarting the service of the node and detecting whether the service is running normally.

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

[0060] S4, detecting whether the service of the system is running normally, and recording abnormal information for operation and maintenance if there is an abnormality. By setting this step, if the service is detected to be abnormal, the operation and maintenance personnel can be notified in time for processing through the query of the upgrade error information, so as to ensure the continuous normal operation of the system.

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

[0062] Specifically, the adjustment of the upgrade task is based on the user instruction 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 cope with the urgent update demand.

[0063] Specifically, if the next round of upgrade needs to be performed on the system to be upgraded, the history record of the statement stored in the statement database performing the upgrade task is compared, and only the newly added statement is updated. The user can selectively execute some database statements instead of re-executing all operations. The database statements executed in each upgrade process are recorded, which can provide data basis for subsequent upgrades. In the next upgrade, the history record is compared, and only the newly added database statements are executed. In this way, the system only updates the newly added part since the last upgrade, without the need to re-execute all statements. This can significantly improve the update efficiency of the database statements, avoid repeated operations, save time and resources, and is suitable for frequent update scenarios.

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

[0065] Embodiment 2

[0066] The embodiment provides an MES system intelligent upgrade management method based on a front-end and back-end separation architecture. The implementation of the method is based on the MES system intelligent upgrade management system based on the front-end and back-end separation architecture described in embodiment 1. The flow is as shown in Figure 7 .

[0067] P1, obtaining the node selected by the user for upgrade based on the instruction input by the user to form an operation instruction.

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

[0069] P2, based on the operation instruction, the upgrade task of the parallel multi-node, the information generated in the execution of the upgrade task is fed back to the user.

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

[0071] In summary, the present application provides a MES system intelligent upgrade management system and method based on front-end and back-end separation architecture, which receives user instructions from the front end and judges, and issues operation instructions to the back end, and the back end performs upgrade tasks in parallel with multiple nodes according to the operation instructions of the front end and feeds back information to the front end, and completes the intelligent upgrade management of the MES system. The present application greatly improves the efficiency, stability and flexibility of the MES system upgrade, reduces manual intervention, enhances the reliability of the system, and provides a more efficient, safe and intelligent solution for system upgrade in large-scale production environment.

[0072] It should be pointed out that according to the needs of implementation, each step / component described in this application can be split into more steps / components, or two or more steps / components or part of the operation of the steps / components can be combined into new steps / components to achieve the purpose of the present application.

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

[0074] It should be understood that for those skilled in the art, improvements or changes can be made according to the above description, and all these improvements and changes shall fall within the scope of protection of the appended claims of the present application.

Claims

1. An MES system intelligent upgrade management system based on a front-end and back-end separation architecture, characterized in that, The system comprises a front end, a back end and an API interface layer; wherein: The API interface layer applies WebSocket technology for communication interaction between the front end and the back end; the front end is used for prompting information to a user and receiving an instruction input by the user, obtaining a node selected by the user for upgrade based on the instruction, and issuing an operation instruction to the back end through the API interface layer; the back end is used for performing upgrade tasks of multiple nodes in parallel according to the operation instruction and feeding back information generated in the execution of the upgrade tasks to the front end through the API interface layer; The back end is arranged in a cloud or a local server and comprises a backup and recovery module, a real-time step and feedback module, a service state detection module, an operation execution module and a statement database; wherein the backup and recovery module is used for backing up and storing the node selected by the user for upgrade; the real-time step and feedback module is used for judging whether a normal upgrade condition is met, recording and storing an unmet upgrade condition, a real-time upgrade progress and information generated in the execution of the upgrade task, and feeding back to the front end through the API interface layer; the service state detection module is used for detecting whether there is an abnormality in the service running of the system after the completion of the upgrade task; the operation execution module is used for performing a node upgrade process and a restoration process; and the statement database is used for storing statements for executing the upgrade task; The back end is used for performing an upgrade task, which comprises: obtaining the node selected by the user for upgrade according to the operation instruction issued by the front end; judging whether the user customizes an upgrade step; when the user does not customize the upgrade step, performing the upgrade process of multiple nodes in parallel and returning the upgrade progress to the front end in real time; when the user customizes the upgrade step, judging whether a normal upgrade requirement is met, feeding back the unmet requirement to the front end when the requirement is not met, or performing the upgrade process of multiple nodes in parallel and returning the upgrade progress to the front end in real time when the requirement is met; monitoring whether an error occurs in each node in the upgrade process, terminating the upgrade of the node when an error occurs in the node, feeding back upgrade error information to the front end, restoring the node according to a received upgrade restart instruction from the front end, and re-executing the upgrade process of the node; otherwise, completing the upgrade of each node and feeding back upgrade completion information to the front end, and recording statements for executing the upgrade task; wherein the upgrade completion information comprises an upgrade report of each node; and the upgrade error information comprises a step generating an error and an execution time of an error operation; detecting whether the service running of the system is normal, and recording abnormal information for operation and maintenance if there is an abnormality. 2.The MES system intelligent upgrade management system based on a front-back end separation architecture according to claim 1, characterized in that, The front end is arranged on a platform, and the platform comprises a Web browser and further comprises a Windows, macOS or Linux operating system. 3.The MES system intelligent upgrade management system based on a front-back end separation architecture according to claim 1, characterized in that, The upgrade process performed on each node comprises: decompressing an upgrade package, closing the service of the node, backing up the engineering file and the database of the node, covering the upgrade package, updating the database, and restarting the service of the node. 4.The MES system intelligent upgrade management system based on a front-back end separation architecture according to claim 3, characterized in that, The restoration process performed on each node comprises: detecting whether there is a backup meeting the requirement for the node, and performing the restoration process when there is a backup meeting the requirement; otherwise, feeding back backup error information to the front end. The monitoring whether an error occurs in the reduction process, if no error occurs, feedback to the front end reduction completion information; otherwise, feedback to the front end reduction error information, according to the received from the front end reduction restart instruction, re-executes the reduction process of the node. 5.The MES system intelligent upgrade management system based on a front-back end separation architecture according to claim 4, characterized in that, The process of reducing the node includes: closing the service of the node, restoring the engineering file and the database of the node to the backup engineering file and the backup database respectively, restarting the service of the node and detecting whether it is running normally. 6.The MES system intelligent upgrade management system based on a front-back end separation architecture according to claim 1, characterized in that, The backend does not need to interrupt or reconfigure between each round of upgrade tasks. 7.The MES system intelligent upgrade management system based on a front-back end separation architecture according to claim 1, characterized in that, The content of the upgrade task is adjusted based on the user configuration behavior received by the front end.

8. A method for intelligent upgrade management of an MES system based on a front-back end separation architecture, the execution of which is based on the intelligent upgrade management system of the MES system based on the front-back end separation architecture according to any one of claims 1-7, characterized in that, It includes: Based on the user input instruction, the user selects the upgraded node to form an operation instruction; Based on the operation instruction, the upgrade tasks of multiple nodes are executed in parallel, and the information generated during the execution of the upgrade task is fed back to the user.

Images