Novel industrial cloudization controller undisturbed upgrading method and system and medium

Abstract

The invention relates to a novel industrial cloudization controller undisturbed upgrading method and system and a medium, and the method comprises the steps: creating a cloudization controller; the uploaded cloud controller software mirror image is received and uploaded to the private cloud platform, and mirror image preheating is carried out after verification; in response to the upgrade request, identifying and selecting a standby controller to upgrade by referring to the preheated mirror image, and controlling the standby controller to obtain and update a configuration preheating memory in the corresponding main controller; and switching the upgraded standby controller into the main controller for pilot run, switching the main controller into the standby controller, and continuing to upgrade the original main controller or rolling the upgraded standby controller back to the version before upgrading according to the running state of the current control service in the pilot run. According to the method, the hardware controller is clouded, active and standby undisturbed upgrading and flexible resource management are realized, the system flexibility is improved through an intelligent process, the maintenance cost is reduced, and powerful support is provided for efficient operation and maintenance of the industrial internet.

Description

Technical Field

[0001] The present invention relates to the field of industrial control technology, and in particular to a novel method, system and medium for non-intrusive upgrade of industrial cloud controllers. Background Art

[0002] In recent years, with the rapid development of the industrial Internet, user needs have become increasingly fast-changing, which has put forward higher requirements for the field of industrial automation and intelligent control. In the traditional industrial control system, hardware controllers, as core components in industrial factory environments, have long occupied a dominant position. However, most of these traditional hardware controllers are built based on physical devices to form independent control systems.

[0003] Since traditional hardware controllers are usually designed to execute fixed function blocks (FBD), they lack scalability and flexibility when facing complex and changing industrial automation needs. This fixed design limits the system's rapid integration and adaptation of new functions and cannot meet the growing demand for customization. In addition, traditional hardware controllers are highly dependent on on-site maintenance and management, which not only increases operation and maintenance costs, but may also cause long downtime when equipment fails.

[0004] Therefore, as the hardware controllers have been in operation for a long time, their maintenance costs have gradually increased, becoming a major burden that enterprises have to face. What's worse, when the old generation of controllers reaches the end of their service life or cannot meet the requirements of new technologies, they often need to be replaced with new hardware controllers, which not only involves high replacement costs, but may also cause interruptions in the production process, further affecting the production efficiency and economic benefits of the enterprise. Summary of the invention

[0005] 1. Technical issues to be resolved

[0006] In view of the above-mentioned shortcomings and deficiencies of the prior art, the present invention provides a new method, system and medium for non-intrusive upgrade of industrial cloud controllers, which solves the technical problem that traditional industrial control systems are difficult to meet the rapidly changing user needs and efficient operation and maintenance requirements in the context of the industrial Internet due to insufficient scalability and flexibility of hardware controllers and high maintenance and replacement costs.

[0007] (II) Technical solution

[0008] In order to achieve the above object, the main technical solutions adopted by the present invention include:

[0009] In a first aspect, an embodiment of the present invention provides a novel method for non-disruptive upgrade of an industrial cloud controller, comprising:

[0010] Create redundant cloud controllers according to the creation instructions input by the user;

[0011] After the cloud controller deploys the service and runs, it receives the cloud controller software image uploaded by the user and uploads it to the private cloud platform. After verification, the image is preheated on the service working node.

[0012] In response to a user's upgrade request for any cloud controller, the standby controller of the cloud controller to be upgraded is automatically identified and selected to refer to the preheated image for upgrade, and at the same time, the standby controller is controlled to obtain and update the configuration preheated memory in the corresponding master controller;

[0013] Switch the upgraded standby controller to the main controller for trial operation, and switch the main controller to the standby controller. Based on the operating status of the current control service obtained during the trial operation, continue to upgrade the original main controller that has been switched to the standby controller or roll back the upgraded standby controller to the version before the upgrade.

[0014] Optionally, according to a creation instruction input by a user, creating a redundant cloud controller includes:

[0015] Receive and parse the creation instructions entered by the user in the human-computer interaction interface to determine the number of cloud controllers to be created, configuration parameters, and redundancy requirements;

[0016] Based on the determined requirements, create and initialize a cloud controller instance as the master controller;

[0017] Simultaneously with or subsequently to the primary controller, create and initialize a standby controller instance having the same or similar configuration parameters as the primary controller, and configure a redundancy relationship between the primary controller instance and the standby controller instance to form a redundant pair;

[0018] Feedback to the user includes the creation results of the number of primary controllers and backup controllers created, the creation status, and the redundancy relationship.

[0019] Optionally, after the cloud controller deploys the service and runs, the cloud controller software image uploaded by the user is received and uploaded to the private cloud platform, and the image is preheated on the service working node after verification, including:

[0020] Wait for the cloud controller to deploy services and start running;

[0021] Receive the cloud controller software image uploaded by the user, and transfer the cloud controller software image from the temporary storage location to the designated storage area of ​​the private cloud platform;

[0022] Perform legality verification on uploaded software images on the private cloud platform according to the set verification standards;

[0023] If the verification fails, delete the corresponding software image;

[0024] If the verification passes, the image preheater is used to selectively preheat the software image on some or all of the business work nodes on the private cloud platform to quickly start or switch to the software image.

[0025] Optionally, in response to a user's upgrade request for any cloud controller, automatically identifying and selecting a standby controller of the cloud controller to be upgraded to refer to the preheated image for upgrading, and controlling the standby controller to obtain and update the configuration preheated memory in the corresponding main controller includes:

[0026] Responding to an upgrade request issued by a user on a human-computer interaction interface for any cloud controller;

[0027] Automatically identify a standby controller corresponding to the selected cloud controller to be upgraded according to a unique identifier or selection criteria of the controller to be upgraded in the upgrade request;

[0028] The standby controller is upgraded by using the preheated image, and during the upgrade process, the standby controller is controlled to obtain the configuration preheating memory in the opposite main controller, so that the standby controller maintains the same configuration state as the opposite main controller;

[0029] The configuration preheating memory contains the current and unchanged configuration information of the opposite-end main controller.

[0030] Optionally, the standby controller is upgraded by using the preheated image, and during the upgrade process, the standby controller is controlled to obtain the configuration preheating memory in the opposite master controller so that the standby controller and the opposite master controller maintain the same configuration state, including:

[0031] Obtain a verified, pre-heated cloud controller software image from the private cloud platform;

[0032] Suspending part or all of the services of the standby controller to be upgraded, while maintaining the communication link between the standby controller to be upgraded and the main controller;

[0033] Upgrade the standby controller using a verified, pre-warmed cloud controller software image by incremental update, modular replacement, or complete replacement.

[0034] During the upgrade process of the standby controller, a snapshot or real-time copy of the configuration status of the opposite master controller is loaded into the memory of the standby controller, or the configuration status of the standby controller is updated in real time through a preset synchronization mechanism;

[0035] After the standby controller is upgraded and obtains the configuration preheating memory of the peer master controller, perform version verification and configuration consistency verification;

[0036] If the upgrade and verification are successful, the upgraded standby controller is placed in standby mode.

[0037] Optionally, switching the upgraded standby controller to the main controller for trial operation, and switching the main controller to the standby controller, and continuing to upgrade the original main controller switched to the standby controller or rolling back the upgraded standby controller to the version before the upgrade according to the operation status of the current control service obtained in the trial operation include:

[0038] Switch the upgraded standby controller to the master controller authority for trial operation, switch the master controller to the standby controller authority, and activate the master-standby locking mechanism to ensure that no unexpected master-standby controller switching occurs during the entire upgrade process;

[0039] Monitor and obtain the running status of the current control service during the trial operation, and determine whether the running status of the current control service meets the preset upgrade conditions;

[0040] If the current operating status of the control service meets the preset upgrade conditions, then in response to the user's upgrade request for the next controller, the upgrade work of the original main controller switched to the standby controller authority continues;

[0041] If the current running status of the control service does not meet the preset upgrade conditions, the upgraded standby controller will be rolled back to the version before the upgrade to ensure that the redundant cloud controllers are rolled back to the version before the upgrade at the same time.

[0042] Optionally, activate the active / standby locking mechanism to ensure that no unexpected active / standby controller switching occurs during the entire upgrade process, including:

[0043] Before the upgrade process begins, identify and locate the logic module currently responsible for active / standby switching;

[0044] According to the acquired historical switching data, the locking range, locking granularity and unlocking conditions of the logic module responsible for the active / standby switching are identified;

[0045] For the located logic module, a highly configurable temporary lock for controlling the lock state of the active / standby switch is built based on Boolean variables, lock range, lock granularity, and unlock conditions, and is configured with key-value pairs or dynamic attributes to store additional information;

[0046] Before making any switching decision, check the status of the temporary lock regularly or in real time through system logs, human-computer interaction interfaces or internal monitoring mechanisms;

[0047] If the temporary lock is in the locked state, any master-slave switching operation is prohibited;

[0048] If the temporary lock is not locked successfully, the upgrade process will be suspended and the error handling mechanism will be triggered until the lock status is confirmed to be correct through manual intervention or automatic repair mechanism, and then the upgrade process will continue;

[0049] After the upgrade process is completely completed and all verification steps are successfully passed, unlock the logic module for active / standby switchover by resetting or clearing the temporary lock that was built.

[0050] In a second aspect, an embodiment of the present invention provides a novel non-intrusive upgrade system for industrial cloud controllers, including:

[0051] Human-computer interaction interface, used for users to issue instructions to create redundant controllers, upload software images of cloud-based controllers, select controllers for update, and monitor the upgrade process through the system management center platform;

[0052] Private cloud platform, used to store uploaded cloud-based controller software images to support non-disruptive upgrades of controllers;

[0053] The system management center is connected with the human-machine interaction interface and the private cloud platform, deploys and runs the AppOperator service framework, and the AppOperator service framework is used to execute the new industrial cloud controller non-intrusive upgrade method as described above.

[0054] Optionally, the AppOperator service framework includes:

[0055] A creation module, used to create a redundant cloud controller according to a creation instruction input by a user;

[0056] The image upload and preheating module is used to receive the cloud controller software image uploaded by the user and upload it to the private cloud platform after the cloud controller deploys the service and runs. After verification, the image is preheated on the service working node;

[0057] A standby controller upgrade module is used to respond to a user's upgrade request for any cloud controller, automatically identify and select the standby controller of the cloud controller to be upgraded to refer to the preheated image for upgrade, and control the standby controller to obtain and update the configuration preheated memory in the corresponding main controller;

[0058] The upgrade management and control module is used to switch the upgraded standby controller to the main controller for trial operation, and switch the main controller to the standby controller. According to the operating status of the current control business obtained during the trial operation, the original main controller that has been switched to the standby controller is continued to be upgraded or the upgraded standby controller is rolled back to the version before the upgrade.

[0059] In a third aspect, an embodiment of the present invention provides a computer-readable medium having computer-executable instructions stored thereon, which, when executed by a processor, implement the novel industrial cloud controller non-intrusive upgrade method as described above.

[0060] (III) Beneficial effects

[0061] The beneficial effects of the present invention are:

[0062] The present invention firstly creates redundant cloud controllers flexibly according to the creation instructions input by the user. This step not only reflects the high scalability of the system, but also lays a solid foundation for subsequent non-intrusive upgrades.

[0063] Then, after the cloud controller deploys the business and runs stably, it can receive the cloud controller software image uploaded by the user and upload it securely to the private cloud platform. After a strict verification process, these images are preheated on the business work node, making full preparations for subsequent rapid upgrades. This link not only ensures the reliability and security of the software image, but also improves the upgrade efficiency through the preheating mechanism. It is worth emphasizing that the cloud controller supports remote upgrades, and users can maintain and update the control system at any location in the factory, reducing on-site operations.

[0064] When a user initiates an upgrade request for any cloud controller, the standby controller to be upgraded can be automatically identified and selected. Based on the preheated image, the standby controller is upgraded, and the configuration preheated memory in the opposite main controller is simultaneously acquired and updated. Compared with traditional controller upgrades that are limited by hardware architecture and have poor flexibility, and often require overall replacement or major changes, the present invention supports on-demand adjustment and rolling updates, and can more flexibly adapt to different industrial scenarios and needs. This step realizes precise control and efficient execution of upgrades, ensuring that business continuity is not affected during the upgrade process.

[0065] Finally, the upgraded standby controller is switched to the main controller for trial operation. According to the operating status of the current control service during the trial operation, it can intelligently decide whether to continue upgrading the next cloud controller or quickly roll back the upgraded cloud controller to the version before the upgrade. The rollback of traditional hardware controllers is relatively difficult, and usually requires reinstalling the old version or replacing the hardware. The cloud controller of the present invention has a fast rollback function, which can quickly restore to the previous version when the upgrade fails to ensure system stability. This mechanism not only ensures the stability of the system upgrade, but also greatly reduces the risk of upgrade failure.

[0066] Therefore, the present invention utilizes the cloud environment to replace the hardware controller with the cloud controller, realizing the non-disturbance upgrade function of the cloud controller between the master and the standby. The cloud controller realizes the functions of on-demand resource allocation, remote management, real-time data processing and intelligent optimization by migrating the control logic and functions from the hardware to the cloud environment. This architecture breaks through the hardware limitations of the traditional controller, provides higher scalability, stronger computing power and intelligent control capabilities, and adapts to the complex and changeable application scenarios of modern industry. At the same time. The present invention realizes the flexible upgrade and rapid rollback of the controller through a highly automated and intelligent process, significantly improving the scalability, flexibility and stability of the industrial control system, and also reduces maintenance costs by reducing manual intervention, providing strong support for efficient operation and maintenance in the context of the industrial Internet. BRIEF DESCRIPTION OF THE DRAWINGS

[0067] Figure 1 A flowchart of a novel method for non-intrusive upgrade of an industrial cloud controller provided by an embodiment of the present invention;

[0068] Figure 2 An overall view of the method provided for an embodiment of the present invention;

[0069] Figure 3 A schematic diagram of a specific flow chart of step S1 of the method provided in an embodiment of the present invention;

[0070] Figure 4 A schematic diagram of a specific flow chart of step S2 of the method provided in an embodiment of the present invention;

[0071] Figure 5 A schematic diagram of a specific flow chart of step S3 of the method provided in an embodiment of the present invention;

[0072] Figure 6 A schematic diagram of a specific flow chart of step S33 of the method provided in an embodiment of the present invention;

[0073] Figure 7 A schematic diagram of a specific flow chart of step S4 of the method provided in an embodiment of the present invention;

[0074] Figure 8 A schematic diagram of a specific flow chart of step S41 of the method provided in an embodiment of the present invention;

[0075] Fig. 9 An overall timing diagram of the method provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0076] In order to better explain the present invention and facilitate understanding, the present invention is described in detail below through specific implementation modes in conjunction with the accompanying drawings.

[0077] like Figure 1As shown, a novel method for non-intrusive upgrade of industrial cloud controllers proposed in an embodiment of the present invention includes: creating a redundant cloud controller according to a creation instruction input by a user; after the cloud controller deploys services and runs, receiving the cloud controller software image uploaded by the user and uploading it to the private cloud platform, and preheating the image on the business working node after verification; in response to the user's upgrade request for any cloud controller, automatically identifying and selecting the standby controller of the cloud controller to be upgraded for upgrading with reference to the preheated image, and controlling the standby controller to obtain and update the configuration preheating memory in the corresponding main controller; switching the upgraded standby controller to the main controller for trial operation, and switching the main controller to the standby controller, and continuing to upgrade the original main controller switched to the standby controller or rolling back the upgraded standby controller to the version before the upgrade according to the operating status of the current control business in the trial operation.

[0078] The present invention firstly flexibly creates at least one pair of redundant cloud controllers according to the creation instructions input by the user. This step not only reflects the high scalability of the system, but also lays a solid foundation for subsequent non-intrusive upgrades.

[0079] Then, after the cloud controller deploys the business and runs stably, it can receive the cloud controller software image uploaded by the user and upload it securely to the private cloud platform. After a strict verification process, these images are preheated on the business work node, making full preparations for subsequent rapid upgrades. This link not only ensures the reliability and security of the software image, but also improves the upgrade efficiency through the preheating mechanism. It is worth emphasizing that the cloud controller supports remote upgrades, and users can maintain and update the control system at any location in the factory, reducing on-site operations.

[0080] When a user initiates an upgrade request for any cloud controller, the standby controller to be upgraded can be automatically identified and selected. Based on the preheated image, the standby controller is upgraded, and the configuration preheated memory in the opposite main controller is simultaneously acquired and updated. Compared with traditional controller upgrades that are limited by hardware architecture and have poor flexibility, and often require overall replacement or major changes, the present invention supports on-demand adjustment and rolling updates, and can more flexibly adapt to different industrial scenarios and needs. This step realizes precise control and efficient execution of upgrades, ensuring that business continuity is not affected during the upgrade process.

[0081] Finally, the upgraded standby controller is switched to the main controller for trial operation. According to the operating status of the current control service during the trial operation, it can intelligently decide whether to continue upgrading the next cloud controller or quickly roll back the upgraded cloud controller to the version before the upgrade. The rollback of traditional hardware controllers is relatively difficult, and usually requires reinstalling the old version or replacing the hardware. The cloud controller of the present invention has a fast rollback function, which can quickly restore to the previous version when the upgrade fails to ensure system stability. This mechanism not only ensures the stability of the system upgrade, but also greatly reduces the risk of upgrade failure.

[0082] Therefore, the present invention utilizes the cloud environment to replace the hardware controller with the cloud controller, realizing the non-disturbance upgrade function of the cloud controller between the master and the standby. The cloud controller realizes the functions of on-demand resource allocation, remote management, real-time data processing and intelligent optimization by migrating the control logic and functions from the hardware to the cloud environment. This architecture breaks through the hardware limitations of the traditional controller, provides higher scalability, stronger computing power and intelligent control capabilities, and adapts to the complex and changeable application scenarios of modern industry. At the same time. The present invention realizes the flexible upgrade and rapid rollback of the controller through a highly automated and intelligent process, significantly improving the scalability, flexibility and stability of the industrial control system, and also reduces maintenance costs by reducing manual intervention, providing strong support for efficient operation and maintenance in the context of the industrial Internet.

[0083] In order to better understand the above technical solution, exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present invention are shown in the accompanying drawings, it should be understood that the present invention can be implemented in various forms and should not be limited by the embodiments described herein. On the contrary, these embodiments are provided to enable a clearer and more thorough understanding of the present invention and to fully convey the scope of the present invention to those skilled in the art.

[0084] Specifically, an embodiment of the present invention provides a novel method for non-disruptive upgrade of an industrial cloud controller, including:

[0085] S1. Create a redundant cloud controller according to the creation instruction input by the user.

[0086] like Figure 2 As shown in the figure, according to the creation instructions input by the user, a redundant cloud controller is created, and the redundancy relationship is configured as a main controller and a standby controller. The main controller is responsible for the main control tasks when it is working normally, while the standby controller is used as a backup and is ready to take over the control tasks when the main controller fails or needs to be switched.

[0087] Furthermore, if Figure 3 As shown, step S1 includes:

[0088] S11. Receive and parse the creation instruction input by the user in the human-computer interaction interface to determine the requirements including the number of cloud controllers to be created, configuration parameters and redundancy relationships.

[0089] S12. Based on the determined requirements, create and initialize a cloud controller instance as a main controller.

[0090] S13. Simultaneously with or subsequently to the main controller, create and initialize a standby controller instance having the same or similar configuration parameters as the main controller, and configure a redundant relationship between the main controller instance and the standby controller instance to form a redundant pair.

[0091] S14. Feedback to the user the creation result including the creation quantity, creation status and redundancy relationship of the main controller and the backup controller.

[0092] S2: After the cloud controller deploys the service and runs, the cloud controller software image uploaded by the user is received and uploaded to the private cloud platform. After verification, the image is preheated on the service working node.

[0093] Furthermore, if Figure 4 As shown, step S2 includes:

[0094] S21. Wait for the cloud controller to deploy services and start running.

[0095] S22: Receive the cloud-based controller software image uploaded by the user, and transfer the cloud-based controller software image from the temporary storage location to the designated storage area of ​​the private cloud platform.

[0096] S23. Perform a legality check on the uploaded software image on the private cloud platform according to the set verification standards.

[0097] In order to ensure the security and reliability of the uploaded software image, a special verification tool is used to verify the legitimacy of the image according to the preset verification standards. These verification standards include image integrity, version compatibility, version number verification, and other aspects. Only after passing these verifications can the software image be considered legal and used for subsequent deployment and startup.

[0098] S24. If the verification fails, the corresponding software image is deleted; if the verification passes, the image preheater is used to selectively preheat the software image on some or all business working nodes to quickly start or switch to the software image.

[0099] S3. In response to a user's upgrade request for any cloud controller, automatically identify and select the standby controller of the cloud controller to be upgraded to upgrade with reference to the preheated image, and at the same time control the standby controller to obtain and update the configuration preheated memory in the corresponding main controller.

[0100] Furthermore, if Figure 5 As shown, step S3 includes:

[0101] S31. Responding to an upgrade request issued by a user on a human-computer interaction interface for any cloud controller.

[0102] S32: Automatically identify the standby controller corresponding to the selected cloud controller to be upgraded according to the unique identifier or selection criteria of the controller to be upgraded in the upgrade request.

[0103] S33. Use the preheated image to upgrade the standby controller, and during the upgrade process, control the standby controller to obtain the configuration preheating memory in the opposite main controller so that the standby controller and the opposite main controller maintain a consistent configuration state; wherein the configuration preheating memory contains the current and unchanged configuration information of the opposite main controller.

[0104] Furthermore, if Figure 6 As shown, step S33 includes:

[0105] S33. Obtain a verified and preheated cloud controller software image from the private cloud platform.

[0106] S34: Suspend part or all of the services of the standby controller to be upgraded, while maintaining the communication link between the standby controller to be upgraded and the main controller.

[0107] S35. Use incremental update, modular replacement, or complete replacement to upgrade the standby controller using the verified and preheated cloud controller software image.

[0108] S36. During the upgrade process of the standby controller, a snapshot or a real-time copy of the configuration status of the opposite master controller is loaded into the memory of the standby controller, or the configuration status of the standby controller is updated in real time through a preset synchronization mechanism.

[0109] S37: After the standby controller is upgraded and the configuration preheating memory of the opposite master controller is obtained, version verification and configuration consistency verification are performed.

[0110] S38. If the upgrade and verification are successful, the upgraded standby controller is placed in a standby state.

[0111] In a specific embodiment, first, a verified and preheated cloud controller software image is obtained from a private cloud platform, the image including the latest control logic, functional modules and necessary configuration files. Then, the preheated image is loaded onto the standby controller to be upgraded, preparing for subsequent upgrade operations.

[0112] Then, before the standby controller starts upgrading, it sends a configuration preheating memory request to the running master controller at the other end through a secure communication channel. This request contains the necessary authentication information and the specific content of the request, such as the required configuration data type, version, and synchronization timestamp, to ensure that the configuration data obtained is the latest and consistent.

[0113] After receiving the configuration preheating memory request, the opposite master controller packages its current configuration status, including but not limited to configuration parameters, operating status, historical data cache, etc., into a configuration preheating memory data packet according to the content of the request, and securely sends it to the standby controller through encrypted communication. After receiving the data packet, the standby controller decrypts and verifies it to ensure the integrity and correctness of the data.

[0114] The standby controller updates its internal configuration state according to the received configuration preheating memory data packet to make it consistent with the configuration state of the opposite master controller. This step ensures that the upgraded standby controller can seamlessly take over the work of the master controller.

[0115] S4. Switch the upgraded standby controller to the main controller for trial operation, and switch the main controller to the standby controller. According to the operating status of the current control service obtained during the trial operation, continue to upgrade the original main controller that has been switched to the standby controller or roll back the upgraded standby controller to the version before the upgrade.

[0116] Furthermore, if Figure 7 As shown, step S4 includes:

[0117] S41, switching the upgraded standby controller to the master controller authority for trial operation, switching the master controller to the standby controller authority, and activating the master-standby locking mechanism to ensure that unexpected master-standby controller switching does not occur during the entire upgrade process.

[0118] Furthermore, if Figure 8 As shown in the figure, activating the active / standby locking mechanism to ensure that unexpected active / standby controller switching does not occur during the entire upgrade process includes:

[0119] S411: Before the upgrade process starts, identify and locate the logic module currently responsible for the active / standby switching.

[0120] S412: According to the acquired historical switching data, the locking range, locking granularity and unlocking condition of the logic module responsible for the active / standby switching are identified.

[0121] S413. For the located logic module, a highly configurable temporary lock for controlling the lock state of the active / standby switching is constructed based on Boolean variables, lock range, lock granularity, and unlock conditions, and is configured with key-value pairs or dynamic attributes to store additional information.

[0122] In a specific embodiment, new attributes can be added based on the Boolean variable to enrich the information of the temporary lock. For example:

[0123] lockStartTime: The timestamp when the lock starts, used to record the specific time of the lock operation.

[0124] lockEndTime (optional): The estimated lock end timestamp, used to plan the lock duration.

[0125] unlockConditions: one or more unlock conditions, which can be specific system status, upgrade completion flag, time conditions, etc.

[0126] lockScope: Lock scope, indicating whether the lock is global or local. A global lock affects the entire system, while a local lock may only affect a specific module or function.

[0127] lockGranularity: Lock granularity, which indicates the degree of fineness of the lock. For example, you can lock specific active / standby switching conditions in a fine-grained manner instead of the entire switching logic.

[0128] Choose the appropriate data structure type based on the properties and requirements of the temporary lock. For example, you can use a class or a structure to define the lock object to encapsulate its properties and methods.

[0129] It is important to emphasize that considering possible changes in future requirements, sufficient expansion space should be reserved for temporary locks. For example, key-value pairs or dynamic attributes can be used to store additional information.

[0130] You can choose to integrate this built temporary lock in the localized logic module and build a corresponding locking mechanism. This mechanism allows users or systems to dynamically configure locking strategies based on upgrade requirements, such as locking scope (global or local), locking granularity (fine-grained control of specific switching conditions), etc.

[0131] S414. Before making any switching decision, check the status of the temporary lock regularly or in real time through the system log, human-computer interaction interface or internal monitoring mechanism.

[0132] S415. If the temporary lock is in a locked state, any master-slave switching operation is prohibited; if the temporary lock is not locked successfully, the upgrade process is suspended and the error handling mechanism is triggered until the lock state is confirmed to be correct through manual intervention or automatic repair mechanism, and then the upgrade process is continued.

[0133] S416: After the upgrade process is completely completed and all verification steps are successfully passed, the logic module for active / standby switching is unlocked by resetting or clearing the constructed temporary lock.

[0134] In addition to the above locking mechanisms, you can also lock the active / standby switch in a relatively rough mode, such as disabling automatic switching: directly turning off or disabling all automatic active / standby switch functions to ensure that no automatic switch based on preset conditions will occur during the upgrade; and modifying the switch condition: setting the trigger condition for active / standby switch to a state that cannot be reached during the upgrade, such as setting an extremely high heartbeat loss threshold or requiring specific manual confirmation.

[0135] S42: Monitor and obtain the running status of the current control service during the trial operation, and determine whether the running status of the current control service meets the preset upgrade condition.

[0136] The purpose of this step is to understand the performance of the controller in the trial operation phase in real time, including key indicators such as performance, stability, and response speed. Then, determine whether these operating conditions meet the preset upgrade conditions. The upgrade conditions are set based on multiple factors such as business needs, system stability requirements, or technical compatibility, and are intended to ensure that the normal operation of the business will not be affected during the upgrade process.

[0137] S43: If the current running state of the control service meets the preset upgrade condition, in response to the user's upgrade request for the next controller, continue to upgrade the original main controller that has switched to the standby controller authority.

[0138] If, after evaluation, the operating status of the current control business fully meets or exceeds the set normal operating conditions, the system will respond to the user's upgrade request for the next controller, that is, the original main controller that is currently in the standby controller authority, and automatically execute the upgrade preparation process, including but not limited to data backup, configuration synchronization and upgrade package loading. Subsequently, it will be switched to the standby controller authority for upgrade according to the established strategy, and the above trial operation and evaluation process will be repeated.

[0139] S44: If the current running status of the control service does not meet the preset upgrade conditions, the upgraded standby controller is rolled back to the version before the upgrade to ensure that the redundant cloud controllers are rolled back to the version before the upgrade at the same time.

[0140] On the contrary, if the current operating status of the control business does not meet the set normal operating conditions, the rollback mechanism will be triggered immediately to automatically restore the upgraded standby controller to the stable version before the upgrade, while ensuring that the paired redundant cloud controller also synchronously rolls back to the state before the upgrade, so as to minimize the impact of the upgrade failure on the overall operation of the system and ensure service continuity and data integrity.

[0141] At the same time, during the entire upgrade process, an upgrade log is maintained to record each upgrade attempt, trial run results, status assessment details and any necessary rollback operations for subsequent analysis, auditing and optimization of upgrade strategies.

[0142] In addition, an embodiment of the present invention provides a novel industrial cloud controller non-disruptive upgrade system, including:

[0143] Human-computer interaction interface, used for users to issue instructions to create redundant controllers, upload software images of cloud-based controllers, select controllers for update, and monitor the upgrade process through the system management center platform;

[0144] Private cloud platform, used to store uploaded cloud-based controller software images to support non-disruptive upgrades of controllers;

[0145] The system management center is connected with the human-machine interaction interface and the private cloud platform, deploys and runs the AppOperator service framework, and the AppOperator service framework is used to execute the new industrial cloud controller non-intrusive upgrade method as described above.

[0146] In order to effectively solve the problem of non-disruptive upgrade, an AppOperator service will run in the entire system, which is mainly responsible for the deployment, deletion, and update and upgrade functions of the entire business. When AppOperator updates the controller, it supports both fully automatic upgrades and manual intervention. For the automatic upgrade business, the user only needs to upload the image in the system management platform, and then select the corresponding controller upgrade to implement a one-click upgrade; for the upgrade of stateful redundant controllers, the core of the AppOperator service handles the steps of manual intervention upgrades, and there will be an interactive process for redundant controllers. The user will upgrade the standby controller first. At this time, AppOperator will handle the waiting state until the standby controller upgrade is completed and runs normally before continuing to upgrade the next controller. At the same time, during the controller upgrade process, the controller implements the configuration memory preheating function. When the controller version is upgraded, the upgraded controller will directly obtain the shared memory whose configuration has not been changed from the opposite controller, and directly and quickly restore the configuration content, ensuring that the controller upgrade function is realized in seconds.

[0147] Furthermore, the AppOperator service framework includes: a creation module, which is used to create a redundant cloud controller according to the creation instructions input by the user. An image upload and preheating module, which is used to receive the cloud controller software image uploaded by the user and upload it to the private cloud platform after the cloud controller deploys the business and runs, and preheat the image on the business working node after verification. A standby controller upgrade module, which is used to respond to the user's upgrade request for any cloud controller, automatically identify and select the standby controller of the cloud controller to be upgraded for upgrading with reference to the preheated image, and at the same time control the standby controller to obtain and update the configuration preheating memory in the corresponding main controller. An upgrade management and control module, which is used to switch the upgraded standby controller to the main controller for trial operation, and switch the main controller to the standby controller, and according to the operating status of the current control business in the trial operation, continue to upgrade the original main controller that has been switched to the standby controller or roll back the upgraded standby controller to the version before the upgrade.

[0148] Furthermore, an embodiment of the present invention provides a computer-readable medium having computer-executable instructions stored thereon, and when the executable instructions are executed by a processor, the novel industrial cloud controller non-intrusive upgrade method as described above is implemented.

[0149] This medium has a storage function and can store computer-executable instructions. When these instructions are read and executed by the processor, they implement an innovative method, namely the non-disruptive upgrade method of the new industrial cloud controller. In short, this computer-readable medium is like a carrier that carries all the instructions and information required to achieve non-disruptive upgrades. When these instructions are run on the appropriate processor, the upgrade process of the cloud controller can be automatically completed, and the process is smooth and non-disruptive, which can ensure the stable operation of the industrial system.

[0150] In summary, the embodiments of the present invention provide a novel method, system and medium for non-intrusive upgrade of industrial cloud controllers, such as Fig. 9 As shown in the figure, first, the user needs to create a pair of redundant controllers through the WEB page of the system management center platform and wait for the deployed business to run normally. Then, the user needs to upload the software image of the cloud controller to the private cloud platform. The platform will verify the legitimacy of the software image package and use the image preheater to quickly preheat the image on each node for subsequent use.

[0151] Next, the user selects the controller to be updated on the management center platform interface, and the AppOperator service will automatically identify and select a standby controller for upgrade. During the standby controller upgrade process, the configuration preheating memory in the opposite main controller is obtained to achieve a fast upgrade of the standby controller.

[0152] After the upgrade is complete, the user needs to manually switch the upgraded controller to the primary controller for trial operation, and switch the original primary controller to the backup controller. At this time, enable the primary and backup lock function to ensure that the primary and backup controllers will not switch during the upgrade process. Afterwards, the user needs to confirm whether the controller business is running normally. If it is running normally, proceed to the next step; if it fails, perform a version rollback to restore the controller to the version before the upgrade.

[0153] Similarly, after the user upgrades an old standby controller that has been switched to the main controller, it is necessary to select the main controller that has been switched to the standby controller for upgrading again. Only when all services are running normally can the next step be performed. If any problems are encountered during the upgrade process, resulting in service failure, the current controller version needs to be rolled back, and the previous upgraded controller version needs to be rolled back at the same time to ensure that a pair of redundant controllers are rolled back to the old version at the same time to maintain system consistency.

[0154] Therefore, the present invention has the following advantages:

[0155] 1) Non-disruptive upgrade: The cloud controller can be upgraded without stopping the system operation, without downtime, avoiding interference with the production environment. It also supports automatic non-intervention upgrades and intervention upgrades. The controller upgrade process can be manually intervened. For the upgrade of the main and standby controllers, the standby controller is upgraded first. After the upgrade of the standby controller is completed and running normally, the main controller is switched to run.

[0156] 2) High efficiency: The controller is equipped with a memory preheating function, which enables the controller version to be updated in seconds.

[0157] 3) Remote upgrade: Cloud controllers support remote upgrades, allowing users to maintain and update the control system at any location in the factory, reducing on-site operations.

[0158] 4) Flexibility: It supports on-demand adjustment and rolling updates, and can adapt to different industrial scenarios and needs more flexibly. Traditional controller upgrades are limited by hardware architecture and have poor flexibility, often requiring overall replacement or major changes.

[0159] 5) Quick rollback: The cloud controller has a quick rollback function, which can quickly restore to the previous version when the upgrade fails to ensure system stability. However, the rollback of traditional hardware controllers is relatively difficult and usually requires reinstalling the old version or replacing the hardware.

[0160] 6) Cost-effectiveness: The upgrade of cloud-based controllers reduces manual intervention and maintenance costs through automated processes; traditional controller upgrades consume a lot of manpower and material resources and are costly.

[0161] Since the system / device described in the above embodiments of the present invention is a system / device used to implement the method of the above embodiments of the present invention, a person skilled in the art can understand the specific structure and deformation of the system / device based on the method described in the above embodiments of the present invention, and thus will not be described in detail here. All systems / devices used in the method of the above embodiments of the present invention belong to the scope of protection of the present invention.

[0162] It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as methods, systems or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0163] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems) and computer program products according to embodiments of the present invention. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions.

[0164] It should be noted that in the claims, any reference numerals placed between brackets shall not be construed as limiting the claims. The word "comprising" does not exclude the presence of components or steps not listed in the claims. The word "a" or "an" preceding a component does not exclude the presence of a plurality of such components. The invention may be implemented by means of hardware comprising several different components and by means of a suitably programmed computer. In the claims enumerating several means, several of these means may be embodied by the same hardware. The use of the words first, second, third, etc., is for convenience of expression only and does not indicate any order. These words may be understood as part of the component name.

[0165] In addition, it should be noted that, in the description of this specification, the description of the terms "one embodiment", "some embodiments", "embodiment", "example", "specific example" or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, unless they are contradictory.

[0166] Although the preferred embodiments of the present invention have been described, those skilled in the art may make other changes and modifications to these embodiments after knowing the basic creative concept. Therefore, the claims should be interpreted as including the preferred embodiments and all changes and modifications falling within the scope of the present invention.

[0167] Obviously, those skilled in the art can make various modifications and variations to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention should also include these modifications and variations.

Claims

1. A novel method for non-intrusive upgrade of industrial cloud controllers, characterized in that: include: Create redundant cloud controllers according to the creation instructions input by the user; After the cloud controller deploys the service and runs, it receives the cloud controller software image uploaded by the user and uploads it to the private cloud platform. After verification, the image is preheated on the service working node. In response to a user's upgrade request for any cloud controller, the standby controller of the cloud controller to be upgraded is automatically identified and selected to refer to the preheated image for upgrade, and at the same time, the standby controller is controlled to obtain and update the configuration preheated memory in the corresponding master controller; Switch the upgraded standby controller to the main controller for trial operation, and switch the main controller to the standby controller. Based on the operating status of the current control service obtained during the trial operation, continue to upgrade the original main controller that has been switched to the standby controller or roll back the upgraded standby controller to the version before the upgrade.

2. The novel industrial cloud controller non-disruptive upgrade method according to claim 1 is characterized in that: According to the creation instruction input by the user, creating a redundant cloud controller includes: Receive and parse the creation instructions entered by the user in the human-computer interaction interface to determine the number of cloud controllers to be created, configuration parameters, and redundancy requirements; Based on the determined requirements, create and initialize a cloud controller instance as the master controller; Simultaneously with or subsequently to the primary controller, create and initialize a standby controller instance having the same or similar configuration parameters as the primary controller, and configure a redundancy relationship between the primary controller instance and the standby controller instance to form a redundant pair; Feedback to the user includes the creation results of the number of primary controllers and backup controllers created, the creation status, and the redundancy relationship.

3. The novel industrial cloud controller non-disruptive upgrade method according to claim 1 is characterized in that: After the cloud controller deploys the service and runs, it receives the cloud controller software image uploaded by the user and uploads it to the private cloud platform. After verification, it preheats the image on the service working node, including: Wait for the cloud controller to deploy services and start running; Receive the cloud controller software image uploaded by the user, and transfer the cloud controller software image from the temporary storage location to the designated storage area of ​​the private cloud platform; Perform legality verification on uploaded software images on the private cloud platform according to the set verification standards; If the verification fails, delete the corresponding software image; If the verification passes, the image preheater is used to selectively preheat the software image on some or all of the business work nodes on the private cloud platform to quickly start or switch to the software image.

4. The novel industrial cloud controller non-disruptive upgrade method according to claim 1 is characterized in that: In response to a user's upgrade request for any cloud controller, automatically identifying and selecting a standby controller of the cloud controller to be upgraded to refer to the preheated image for upgrading, and controlling the standby controller to obtain and update the configuration preheated memory in the corresponding main controller includes: Responding to an upgrade request issued by a user on a human-computer interaction interface for any cloud controller; Automatically identify a standby controller corresponding to the selected cloud controller to be upgraded according to a unique identifier or selection criteria of the controller to be upgraded in the upgrade request; The standby controller is upgraded by using the preheated image, and during the upgrade process, the standby controller is controlled to obtain the configuration preheating memory in the opposite main controller, so that the standby controller maintains the same configuration state as the opposite main controller; The configuration preheating memory contains the current and unchanged configuration information of the opposite-end main controller.

5. The novel method for non-intrusive upgrade of industrial cloud controller according to claim 4 is characterized in that: The standby controller is upgraded by using the preheated image. During the upgrade process, the standby controller is controlled to obtain the configuration preheating memory in the opposite master controller so that the standby controller and the opposite master controller are consistent in configuration status including: Obtain a verified, pre-heated cloud controller software image from the private cloud platform; Suspending part or all of the services of the standby controller to be upgraded, while maintaining the communication link between the standby controller to be upgraded and the main controller; Upgrade the standby controller using a verified, pre-warmed cloud controller software image by incremental update, modular replacement, or complete replacement. During the upgrade process of the standby controller, a snapshot or real-time copy of the configuration status of the opposite master controller is loaded into the memory of the standby controller, or the configuration status of the standby controller is updated in real time through a preset synchronization mechanism; After the standby controller is upgraded and obtains the configuration preheating memory of the peer master controller, perform version verification and configuration consistency verification; If the upgrade and verification are successful, the upgraded standby controller is placed in standby mode.

6. The novel method for non-intrusive upgrade of industrial cloud controllers according to claim 1 is characterized in that: Switching the upgraded standby controller to the main controller for trial operation, and switching the main controller to the standby controller, and continuing to upgrade the original main controller switched to the standby controller or rolling back the upgraded standby controller to the version before the upgrade according to the running status of the current control service obtained during the trial operation include: Switch the upgraded standby controller to the master controller authority for trial operation, switch the master controller to the standby controller authority, and activate the master-standby locking mechanism to ensure that no unexpected master-standby controller switching occurs during the entire upgrade process; Monitor and obtain the running status of the current control service during the trial operation, and determine whether the running status of the current control service meets the preset upgrade conditions; If the current operating status of the control service meets the preset upgrade conditions, then in response to the user's upgrade request for the next controller, the upgrade work of the original main controller switched to the standby controller authority continues; If the current running status of the control service does not meet the preset upgrade conditions, the upgraded standby controller will be rolled back to the version before the upgrade to ensure that the redundant cloud controllers are rolled back to the version before the upgrade at the same time.

7. The novel method for non-intrusive upgrade of industrial cloud controller according to claim 6 is characterized in that: Activate the active / standby locking mechanism to ensure that no unexpected active / standby controller switching occurs during the upgrade process, including: Before the upgrade process begins, identify and locate the logic module currently responsible for active / standby switching; According to the acquired historical switching data, the locking range, locking granularity and unlocking conditions of the logic module responsible for the active / standby switching are identified; For the located logic module, a highly configurable temporary lock for controlling the lock state of the active / standby switch is built based on Boolean variables, lock range, lock granularity, and unlock conditions, and is configured with key-value pairs or dynamic attributes to store additional information; Before making any switching decision, check the status of the temporary lock regularly or in real time through system logs, human-computer interaction interfaces or internal monitoring mechanisms; If the temporary lock is in the locked state, any master-slave switching operation is prohibited; If the temporary lock is not locked successfully, the upgrade process will be suspended and the error handling mechanism will be triggered until the lock status is confirmed to be correct through manual intervention or automatic repair mechanism, and then the upgrade process will continue; After the upgrade process is completely completed and all verification steps are successfully passed, unlock the logic module for active / standby switchover by resetting or clearing the temporary lock that was built.

8. A new type of industrial cloud controller non-intrusive upgrade system, characterized by: include: Human-computer interaction interface, used for users to issue instructions to create redundant controllers, upload software images of cloud-based controllers, select controllers for update, and monitor the upgrade process through the system management center platform; Private cloud platform, used to store uploaded cloud-based controller software images to support non-disruptive upgrades of controllers; The system management center is connected with the human-computer interaction interface and the private cloud platform, deploys and runs the AppOperator service framework, and the AppOperator service framework is used to execute the new industrial cloud controller non-intrusive upgrade method as described in any one of claims 1-7.

9. The novel industrial cloud controller non-intrusive upgrade system as claimed in claim 8 is characterized in that: The AppOperator service framework includes: A creation module, used to create a redundant cloud controller according to a creation instruction input by a user; The image upload and preheating module is used to receive the cloud controller software image uploaded by the user and upload it to the private cloud platform after the cloud controller deploys the service and runs. After verification, the image is preheated on the service working node; A standby controller upgrade module is used to respond to a user's upgrade request for any cloud controller, automatically identify and select the standby controller of the cloud controller to be upgraded to refer to the preheated image for upgrade, and control the standby controller to obtain and update the configuration preheated memory in the corresponding main controller; The upgrade management and control module is used to switch the upgraded standby controller to the main controller for trial operation, and switch the main controller to the standby controller. According to the operating status of the current control business obtained during the trial operation, the original main controller that has been switched to the standby controller is continued to be upgraded or the upgraded standby controller is rolled back to the version before the upgrade.

10. A computer-readable medium having computer-executable instructions stored thereon, characterized in that: When the executable instructions are executed by the processor, the novel industrial cloud controller non-intrusive upgrade method as described in any one of claims 1 to 7 is implemented.

Images