An electric energy meter and terminal system stability guarantee system adopting containerization and rapid rollback

Abstract

This invention discloses a stability assurance system for electricity meters and terminal systems employing containerization and rapid rollback, relating to the field of power supply or distribution technology. This system generates standardized version images through a containerized environment encapsulation module, coupled with an environment operation status monitoring engine to collect multi-dimensional data in real time. An intelligent rollback decision and control module determines faults based on preset thresholds and automatically triggers rollback. Combined with a data persistent storage volume and task scheduling module, it achieves graceful shutdown of faulty containers, stable image switching, and task resume from breakpoints. Finally, an audit log module records and pushes event notifications. This system achieves 100% consistency of the verification environment, second-level fault recovery, secure version rollback, and fully automated operation and maintenance, significantly improving verification reliability and task continuity, reducing manpower and resource costs, and is suitable for various electricity meter and power terminal equipment verification scenarios.

Description

Technical Field

[0001] This invention relates to the field of power supply or distribution technology, specifically to a stability assurance system for an energy meter and terminal system that employs containerization and rapid rollback. Background Technology

[0002] With the advancement of smart grid construction, the functions of electricity meters and power terminal equipment are becoming increasingly complex, and the complexity of their verification software is also constantly increasing. The stability of the verification environment directly affects the reliability of the equipment verification results, and thus relates to the safe operation of the power supply system.

[0003] Existing technologies for managing verification environments for electricity meters and terminal equipment suffer from the following prominent problems: Verification software relies on specific versions of operating systems, runtime libraries, and configuration files. Significant differences in environment configurations between different physical servers or verification nodes lead to inconsistent results for the same verification task in different environments, making it impossible to reproduce the problem and severely complicating the accuracy of equipment verification results. If environment crashes or service anomalies occur during verification, traditional recovery methods require manual intervention from maintenance personnel to redeploy the operating system, install dependent libraries, and configure the verification environment. This process can take hours or even days, severely disrupting the continuity of verification tasks and impacting equipment verification progress. Verification software iterates frequently, and new versions of the verification environment may contain undiscovered potential defects. However, existing technologies lack efficient version rollback mechanisms. Rollback failures are easily caused by residual files from the old environment or configuration conflicts, making it impossible to quickly switch to a stable version to continue verification work. Existing verification environments lack real-time monitoring of their operational status, making it impossible to detect environmental anomalies in a timely manner. Furthermore, the lack of automatic recovery mechanisms means that environmental stability relies excessively on manual inspection and maintenance, resulting in high maintenance costs and delays in anomaly detection and handling.

[0004] Therefore, how to build a highly available verification environment and system with self-healing capabilities, easy maintenance, and rapid recovery to ensure the continuous execution and reliability of verification tasks for electricity meters and terminal equipment has become a pressing technical problem to be solved in the equipment verification process of power transmission, transformation, distribution, and control equipment. Summary of the Invention

[0005] The purpose of this invention is to provide a stability assurance system for electricity meters and terminal systems that employs containerization and fast rollback, in order to solve the problems mentioned in the background art, such as strong dependence on environment configuration and poor consistency, low efficiency of fault recovery mechanism, imperfect version management mechanism and insufficient automated operation and maintenance capability.

[0006] To achieve the above objectives, the present invention provides the following technical solution: A stability assurance system for electricity meters and terminal systems employing containerization and rapid rollback includes a containerized environment encapsulation module, an environment operation status monitoring engine, an intelligent rollback decision and control module, a data persistence management module, and a task scheduling and recovery coordinator. The containerized environment encapsulation module packages the electricity meter and terminal verification software, the operating system adapted to the software, runtime dependency libraries, and fixed configuration files into a standardized container image, and performs version management on the container image. The environment operation status monitoring engine continuously collects operation status data of the containerized verification environment, including container process survival status, CPU and memory resource utilization, critical service response time, and verification task queue execution progress. The intelligent rollback decision and control module receives the operation status data transmitted by the environment operation status monitoring engine, compares the operation status data with a preset safety threshold, determines whether the verification environment is in a fault state, and if it is determined to be in a fault state, automatically triggers a rollback operation, driving the faulty container to stop running and starting a stable version container instance. The data persistence management module uses a storage volume independent of the container's lifecycle to store verification project configurations, task execution progress, verification results, and report data. The task scheduling and recovery coordinator manages the start, stop, and scheduling of verification tasks. After a rollback operation, it guides a newly started stable version container instance to mount the storage volume and continue executing the verification task from the point of interruption. The modules work together to achieve standardized deployment of the verification environment, real-time monitoring of its running status, automatic rollback in case of anomalies, and continuous execution of verification tasks.

[0007] Preferably, the containerization environment encapsulation module generates a standardized container image by writing a Dockerfile declarative script.

[0008] Preferably, the standardized container image is assigned a unique version tag in the format "vX.YZ-stable", where X, Y, and Z are positive integers, and the tag is pushed to a private image repository for centralized management.

[0009] Preferably, the monitoring methods of the environment operation status monitoring engine include survival checks and readiness checks:

[0010] Survival checks periodically verify the running status of the main process within the container;

[0011] Readiness checks verify the readiness status of request processing for the validation service within the container via HTTP / TCP requests or custom scripts.

[0012] Preferably, the monitoring methods of the environment operation status monitoring engine also include resource monitoring and business health checks:

[0013] Resource monitoring: Real-time collection of resource consumption metrics such as container CPU utilization, memory usage, and disk I / O rate;

[0014] Business health checks monitor and verify the execution heartbeat signals of tasks to determine whether tasks are stalled or abnormal.

[0015] Preferably, the preset security thresholds include service response timeout time and memory usage duration. When the intelligent rollback decision and control module continuously exceeds the preset security thresholds, it determines that the verification environment is in a fault state.

[0016] Preferably, the rollback operation process of the intelligent rollback decision and control module is as follows: first, stop the current faulty container instance, then pull the container image marked as "stable version" from the private image repository, and start a new container instance based on the configuration parameters and storage volume mount path of the original faulty container.

[0017] Preferably, a stability assurance system for electricity meters and terminal systems that employs containerization and rapid rollback also includes an audit log and event notification module, which records the occurrence time, triggering reason, image versions before and after rollback, and recovery results of rollback events, and sends event notifications to the system administrator via email or instant messaging tools.

[0018] Preferably, the containerized environment encapsulation module supports the adaptation of multiple types of energy meters and terminal verification software. Through environment template library, configuration parameterization and interface standardization design, it realizes universal encapsulation of verification environments for different models of equipment.

[0019] Preferably, a stability assurance method for an energy meter and terminal system stability assurance system employing containerization and fast rollback includes the following steps:

[0020] S1. Standardized Environment Construction and Version Management: Analyze the operational requirements of the electricity meter and terminal verification software, write Dockerfile scripts, package the verification software, operating system, dependency libraries and configuration files to generate a standardized container image, assign a unique version label and store it in a private image repository;

[0021] S2, One-click deployment of containerized verification environment: Pull the specified version of the container image from the private image repository, create a container instance on the container runtime platform, and mount an external persistent storage volume at the same time;

[0022] S3. Real-time monitoring and health check of operational status: Perform survival checks, readiness checks, resource monitoring and business health checks at preset frequencies, and collect operational status data;

[0023] S4. Anomaly Diagnosis and Automatic Rollback Trigger: Compare the running status data with the preset safety threshold. If a fault state is determined, trigger the rollback operation, stop the faulty container and start the stable version container.

[0024] S5. Seamless business recovery and continuity assurance: The new container instance mounts the original storage volume, reads the task progress data, and resumes the verification task execution from the interruption point;

[0025] S6. Audit Log Recording and Event Notification: Record rollback event details and send notifications to the administrator.

[0026] The technical effects and advantages of this invention are as follows:

[0027] 1. This system for ensuring the stability of electricity meters and terminal systems adopts containerization and fast rollback. Containerized images enable standardized encapsulation of the verification environment, eliminating configuration differences between different physical environments and ensuring complete consistency of the environment from development to deployment. This fundamentally solves the problem of unreproducible verification results and provides reliable results support for the verification of power supply system equipment.

[0028] 2. The energy meter and terminal system stability assurance system adopts containerization and fast rollback. Based on the intelligent monitoring automatic rollback mechanism, it can complete fault identification, container switching and task recovery within seconds, which greatly shortens the system downtime, avoids the interruption of verification tasks due to environmental failures, and ensures the progress of equipment verification.

[0029] 3. The system adopts containerization and fast rollback to ensure the stability of electricity meters and terminal systems. The version management of container images makes environment upgrades and rollbacks simple and controllable. When problems occur in the new version, it can be rolled back to the stable version with one click, reducing the risks and operating costs caused by environment changes and adapting to the needs of frequent software iterations.

[0030] 4. The system adopts containerization and fast rollback to ensure the stability of electricity meters and terminal systems. The persistent storage volume design ensures that critical data is not lost during environment switching and achieves seamless task transition. Containerization technology enables lightweight environment deployment, supports on-demand allocation of computing resources, improves hardware resource utilization, and reduces long-term investment costs for environment maintenance.

[0031] 5. The system adopts containerization and fast rollback for the stability assurance of electricity meters and terminal systems. The system realizes full-process automation from environmental monitoring, anomaly detection, automatic rollback to task recovery, which greatly reduces manual operation and maintenance intervention, reduces labor costs, and improves operation and maintenance efficiency and intelligence level.

[0032] 6. This system adopts containerization and fast rollback for the stability assurance of electricity meters and terminal systems. The system supports verification scenarios for multiple types of electricity meters and terminal devices. It can quickly adapt to different models of devices through environment template library and configuration parameterization. At the same time, it supports multi-node deployment and load balancing, and has strong adaptability and scalability. Attached Figure Description

[0033] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0034] Figure 1 This is a diagram of the overall system architecture of the present invention;

[0035] Figure 2 This is a flowchart of the rollback process of the present invention;

[0036] Figure 3 This is a flowchart of the method of the present invention. Detailed Implementation

[0037] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0038] This invention discloses a stability assurance system for electricity meters and terminal systems employing containerization and rapid rollback, according to the appendix. Figures 1-3As shown, the system includes a containerized environment encapsulation module, an environment runtime status monitoring engine, an intelligent rollback decision and control module, a data persistence management module, and a task scheduling and recovery coordinator. The containerized environment encapsulation module packages the electricity meter and terminal verification software, the operating system adapted to the software, runtime dependencies, and fixed configuration files into standardized container images, and manages the versioning of these container images. The environment runtime status monitoring engine continuously collects runtime status data of the containerized verification environment, including container process liveness status, CPU and memory resource utilization, critical service response time, and verification task queue execution progress. The intelligent rollback decision and control module receives runtime status data from the environment runtime status monitoring engine, compares the runtime status data with preset safety thresholds to determine if the verification environment is in a fault state. If a fault state is determined, a rollback operation is automatically triggered, driving the faulty container to stop running and starting a stable version container instance. The data persistence management module uses storage volumes independent of the container lifecycle to store verification project configurations, task execution progress, verification results, and report data. The task scheduling and recovery coordinator manages the start, stop, and scheduling of verification tasks. After a rollback operation, it guides a newly started stable container instance to mount a storage volume and resume execution of the verification task from the point of interruption. The modules work together to achieve standardized deployment of the verification environment, real-time monitoring of its operational status, automatic rollback in case of anomalies, and continuous execution of verification tasks. The system supports verification scenarios for various types of electricity meters and terminal devices. It can quickly adapt to different device models through an environment template library and parameterized configuration. It also supports multi-node deployment and load balancing, demonstrating strong adaptability and scalability.

[0039] According to the appendix Figures 1-3 As shown, the containerization environment encapsulation module further generates standardized container images by writing a declarative Dockerfile script.

[0040] According to the appendix Figures 1-3 As shown, further, standardized container images are assigned unique version tags in the format "vX.YZ-stable", where X, Y, and Z are positive integers. These tags are then pushed to a private image repository for centralized management. Containerized images achieve standardized encapsulation of the verification environment, eliminating configuration differences between different physical environments and ensuring complete consistency of the environment from development to deployment. This fundamentally solves the problem of unreproducible verification results and provides reliable results support for the verification of power supply system equipment.

[0041] According to the appendix Figures 1-3 As shown, the monitoring methods of the environment operation status monitoring engine further include survival checks and readiness checks. Survival checks periodically verify the running status of the main process inside the container; readiness checks verify the request processing readiness status of the verification service inside the container through HTTP / TCP requests or custom scripts.

[0042] According to the appendix Figures 1-3 As shown, the monitoring methods of the environment operation status monitoring engine further include resource monitoring and business health checks. Resource monitoring collects resource consumption indicators such as container CPU utilization, memory usage, and disk I / O rate in real time. Business health checks monitor and verify the execution heartbeat signal of the task to determine whether the task is stalled or abnormal.

[0043] According to the appendix Figures 1-3 As shown, further, the preset security thresholds include: service response timeout time, memory usage duration, and the intelligent rollback decision and control module determines the verification environment to be in a fault state when the running status data continuously exceeds the preset security thresholds.

[0044] According to the appendix Figure 2 As shown, the rollback operation process of the intelligent rollback decision and control module is as follows: First, stop the current faulty container instance, then pull the container image marked as the stable version from the private image repository, and start a new container instance based on the configuration parameters and storage volume mount path of the original faulty container. Based on the intelligent monitoring automatic rollback mechanism, fault identification, container switching and task recovery can be completed in seconds, which greatly shortens the system downtime, avoids the verification task from being interrupted due to environmental failures, and ensures the progress of device verification.

[0045] According to the appendix Figures 1-3 As shown, it further includes an audit log and event notification module, which records the occurrence time, triggering reason, image version before and after rollback, and recovery result of rollback events, and sends event notifications to system administrators via email or instant messaging tools. Version management of container images makes environment upgrades and rollbacks simple and controllable. When a new version has problems, it can be rolled back to a stable version with one click, reducing the risks and operating costs brought about by environment changes and adapting to the needs of frequent iterations of verification software.

[0046] According to the appendix Figures 1-3 As shown, the containerized environment encapsulation module further supports the adaptation of multiple types of energy meters and terminal verification software. Through environment template library, configuration parameterization and interface standardization design, it realizes the universal encapsulation of verification environments for different models of equipment.

[0047] According to the appendix Figure 3 As shown, a stability assurance method for an energy meter and terminal system stability assurance system employing containerization and fast rollback includes the following steps:

[0048] S1. Standardized Environment Construction and Version Management: Analyze the operational requirements of the electricity meter and terminal verification software, write Dockerfile scripts, package the verification software, operating system, dependency libraries and configuration files to generate a standardized container image, assign a unique version label and store it in a private image repository;

[0049] S2, One-click deployment of containerized verification environment: Pull the specified version of the container image from the private image repository, create a container instance on the container runtime platform, and mount an external persistent storage volume. The persistent storage volume design ensures that critical data is not lost during environment switching, achieving seamless task transition; containerization technology enables lightweight environment deployment, supports on-demand allocation of computing resources, improves hardware resource utilization, and reduces long-term investment costs for environment maintenance.

[0050] S3. Real-time monitoring and health check of operating status: Perform survival check, readiness check, resource monitoring and business health check at preset frequency, collect operating status data, and realize full-process automation from environmental monitoring, anomaly detection, automatic rollback to task recovery. This greatly reduces manual operation and maintenance intervention, lowers labor costs, and improves operation and maintenance efficiency and intelligence level.

[0051] S4. Anomaly Diagnosis and Automatic Rollback Trigger: Compare the running status data with the preset safety threshold. If a fault state is determined, trigger the rollback operation, stop the faulty container and start the stable version container.

[0052] S5. Seamless business recovery and continuity assurance: The new container instance mounts the original storage volume, reads the task progress data, and resumes the verification task execution from the interruption point;

[0053] S6. Audit Log Recording and Event Notification: Record rollback event details and send notifications to the administrator.

[0054] Working Principle: The working principle of this system revolves around the core logic of standardized environment encapsulation, real-time status monitoring, intelligent anomaly handling, seamless rollback recovery, and closed-loop operation and maintenance auditing. Each module works together to ensure the high availability and stability of the verification environment, as detailed below:

[0055] 1. Foundation for standardized environment: The containerized environment encapsulation module uses Dockerfile scripts to package the electricity meter verification software, the adapted operating system, the dependent libraries and fixed configurations into a standardized container image. After being given a unique stable version tag, it is stored in a private image repository, eliminating the differences in environment configuration from the root and laying the foundation for consistent deployment and rapid switching in the future.

[0056] 2. Decoupling of deployment and data: When starting a verification task, the system pulls the specified version of the image from the image repository, deploys the container instance with one click, and mounts a persistent storage volume that is independent of the container's lifecycle. This decouples the verification configuration, task progress, and result data from the container, ensuring that the data is not lost when the container is destroyed.

[0057] 3. Multi-dimensional real-time monitoring: The environment operation status monitoring engine performs four types of checks at a preset frequency: survival, readiness, resources, and business health. It continuously collects data such as container process status, CPU / memory utilization, service response time, and task heartbeat, and transmits them to the intelligent rollback decision and control module in real time.

[0058] 4. Intelligent fault determination: The intelligent rollback decision and control module compares the received monitoring data with the preset safety threshold, excludes instantaneous fluctuations, determines whether it is a fault state that needs to be rolled back, and matches the corresponding rollback strategy.

[0059] 5. Automated rollback execution: After confirming the fault, a stop signal is first sent to the faulty container to allow time for data to be written. Then, the previous stable version image is pulled from the image repository, the original container configuration and storage volume mount path are reused, and a new container instance is started. No manual intervention is required throughout the process.

[0060] 6. Health verification and task recovery: After a new container starts, its running status and data access capabilities are verified through multi-dimensional health checks. After the verification is passed, a signal is pushed to the task scheduling module to guide the verification software to read the interrupted data from the storage volume and seamlessly resume the verification task. Automatic recovery or manual confirmation recovery mode is supported.

[0061] 7. Closed-loop operation and maintenance management: The audit log module records the details of rollback events throughout the process, such as time, reason, version, and result, and synchronizes them to the audit log database. Notifications are also pushed to administrators via email and instant messaging tools to achieve traceability of rollback operations and transparency of operation and maintenance.

[0062] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0063] The foregoing has shown and described the basic principles, main features, and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited to the above embodiments. The embodiments and descriptions in the specification are merely illustrative of the principles of the invention. Various changes and modifications can be made to the invention without departing from its spirit and scope, and all such changes and modifications fall within the scope of the present invention as claimed. The scope of protection of this invention is defined by the appended claims and their equivalents.

Claims

1. A stability assurance system for electricity meters and terminal systems employing containerization and rapid rollback, characterized in that, include: A containerized environment encapsulation module is used to package the electricity meter and terminal verification software, the operating system adapted to the software, the runtime dependency library and fixed configuration file into a standardized container image, and to manage the container image in a versioned manner. An environment operation status monitoring engine is used to continuously collect operation status data of the containerized verification environment. The operation status data includes container process survival status, CPU and memory resource utilization, critical service response time, and verification task queue execution progress. The intelligent rollback decision and control module receives the running status data transmitted by the environment running status monitoring engine, compares the running status data with a preset security threshold, determines whether the verification environment is in a fault state, and if it is determined to be in a fault state, automatically triggers a rollback operation, drives the faulty container to stop running and starts a stable version container instance. The preset security thresholds include: service response timeout time and memory usage duration. When the intelligent rollback decision and control module continuously exceeds the preset security thresholds, it determines that the verification environment is in a fault state. The data persistence management module uses a storage volume independent of the container's lifecycle to store verification project configurations, task execution progress, verification results, and report data. A task scheduling and recovery coordinator is used to manage the start, stop and schedule of verification tasks. After the rollback operation is executed, it guides the newly started stable version container instance to mount the storage volume and continue the execution of the verification task from the point of interruption. The modules work together to achieve standardized deployment of the verification environment, real-time monitoring of its operational status, automatic rollback of anomalies, and continuous execution of verification tasks.

2. The stability assurance system for energy meters and terminal systems employing containerization and rapid rollback as described in claim 1, characterized in that, The containerization environment encapsulation module generates standardized container images by writing a Dockerfile declarative script.

3. The stability assurance system for energy meters and terminal systems employing containerization and rapid rollback as described in claim 2, characterized in that, The standardized container image is assigned a unique version label in the format "vX.YZ-stable", where X, Y, and Z are positive integers, and the label is pushed to a private image repository for centralized management.

4. The stability assurance system for energy meters and terminal systems employing containerization and rapid rollback as described in claim 1, characterized in that, The monitoring methods of the environment operation status monitoring engine include survival checks and readiness checks: Survival checks periodically verify the running status of the main process within the container; Readiness checks verify the readiness status of request processing for the validation service within the container via HTTP / TCP requests or custom scripts.

5. The stability assurance system for energy meters and terminal systems employing containerization and rapid rollback as described in claim 1, characterized in that, The monitoring methods of the environment operation status monitoring engine also include resource monitoring and business health checks: Resource monitoring: Real-time collection of container resource consumption indicators such as CPU utilization, memory usage, and disk I / O rate; Business health check: Monitor and verify the execution heartbeat signal of the task to determine whether the task is stalled or abnormal.

6. The stability assurance system for energy meters and terminal systems employing containerization and rapid rollback as described in claim 1, characterized in that, The rollback operation process of the intelligent rollback decision and control module is as follows: First, stop the current faulty container instance, then pull the container image marked as "stable version" from the private image repository, and start a new container instance based on the configuration parameters and storage volume mount path of the original faulty container.

7. The stability assurance system for energy meters and terminal systems employing containerization and rapid rollback as described in claim 1, characterized in that, It also includes an audit log and event notification module, which records the occurrence time, triggering reason, image version before and after rollback, and recovery result of rollback events, and sends event notifications to system administrators via email or instant messaging tools.

8. The stability assurance system for energy meters and terminal systems employing containerization and rapid rollback as described in claim 1, characterized in that, The containerized environment encapsulation module supports the adaptation of multiple types of energy meters and terminal verification software. Through environment template library, configuration parameterization and interface standardization design, it realizes the universal encapsulation of verification environments for different models of equipment.

9. A stability assurance method for an energy meter and terminal system stability assurance system employing containerization and fast rollback as described in any one of claims 1-8, characterized in that, Includes the following steps: S1: Standardized Environment Construction and Version Management: Analyze the operational requirements of the electricity meter and terminal verification software, write Dockerfile scripts, package the verification software, operating system, dependency libraries and configuration files to generate a standardized container image, assign a unique version label and store it in a private image repository; S2: One-click deployment of containerized verification environment: Pull the specified version of the container image from the private image repository, create a container instance on the container runtime platform, and mount an external persistent storage volume at the same time; S3: Real-time monitoring and health check of operational status: Performs survival checks, readiness checks, resource monitoring and business health checks at preset frequencies, and collects operational status data; S4: Anomaly Diagnosis and Automatic Rollback Trigger: Compare the running status data with the preset safety threshold. If a fault is detected, trigger the rollback operation, stop the faulty container, and start the stable version container. S5: Seamless business recovery and continuity assurance: The new container instance mounts the original storage volume, reads the task progress data, and resumes the verification task execution from the interruption point; S6: Audit Log Recording and Event Notification: Record rollback event details and send notifications to the administrator.

Images