A Remote Upgrade Method and System for Intelligent Waveform Recorders Based on Distributed Containerization
By transforming the intelligent waveform recorder application into a containerized microservice architecture and adopting a canary release strategy, the complexity of the intelligent waveform recorder upgrade process was solved, ensuring uninterrupted business operations and efficient reuse of hardware resources, thereby improving the system's reliability and availability.
Patent Information
- Application Number
- CN202610994918.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2026-06-29
- Filing Date
- 2026-07-06
- Publication Date
- 2026-11-17
AI Technical Summary
In existing technologies, the management of edge gateway devices and the input/output data of intelligent waveform recorders are designed independently by each manufacturer, which complicates the upgrade process and makes it impossible to achieve lightweight, modular, and professional division of labor and collaboration.
By adopting a distributed containerized architecture, the intelligent waveform recorder application is transformed into a containerized microservice architecture and deployed in a container management platform. Through canary release strategies and performance monitoring, uninterrupted business operations and high availability are achieved during remote upgrades.
It enables uninterrupted service during the upgrade of intelligent waveform recorders, efficient reuse of hardware resources, reduces the risk of human error, improves system reliability and availability, and supports standardized collaboration of multiple manufacturers' apps.
Smart Images

Figure CN123114504A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the technical field of intelligent waveform recorder upgrades, and more specifically, to a method and system for remote upgrades of intelligent waveform recorders based on distributed containerization. Background Technology
[0002] The intelligent waveform recorder is a bay-level device in the secondary system of an intelligent substation, integrating three major functions: fault waveform recording, network message recording and analysis, and online monitoring and diagnosis of secondary equipment. Fault waveform recording focuses on acquiring fault waveforms for protection professionals to analyze accidents. Network message recording and analysis focuses on acquiring network messages for operators to analyze message communication processes. Online monitoring and diagnosis of secondary equipment focuses on acquiring process-level virtual loop communication status and relay protection information for protection management personnel to analyze relay protection and secondary circuit status.
[0003] Container-related cloud technologies, as productivity tools, can significantly improve development and operations productivity through containerization, microservices, and DevOps automation. They enable the building and running of elastically scalable applications, and the construction of loosely coupled systems that are fault-tolerant, easy to manage, and easy to track and observe. Combined with reliable automation methods, they can effectively support frequent and predictable major system changes. They can forcefully improve the flexibility, module reusability, functional scalability, and maintainability of software architecture; reduce the workload of development, testing, implementation, and operations personnel in adapting, testing, deploying, and managing various system environments, achieving cost reduction and efficiency improvement; and fully leverage a robust and mature supporting ecosystem, benefiting from continuous integration and release, operations monitoring, service governance, and hardware and software resource sharing. They also address the various problems of monolithic software engineering through formal and mature software engineering methods.
[0004] From an information system management perspective, this approach enforces the separation, transparency, orderliness, and robust control and constraints of software development, maintenance, and operation. After testing, the app is uploaded to the app store by the testing organization, with users acting as the sole point of entry for app distribution and version control. Furthermore, the fact that the intelligent waveform recorder manufacturer's personnel have no access to the physical server enhances the system's security, transparency, and controllability.
[0005] Remote upgrades, as an essential function of intelligent waveform recorders, should leverage container management and monitoring platforms such as Kubernetes to build a large-scale, automated, end-to-end technical support platform tailored to the characteristics of the power system, forming a comprehensive system with a strong ecosystem. Due to the need for multi-party collaboration, a "fair scale" should be in place to clarify responsibilities and reduce disputes, with recognized mechanisms for performance evaluation, problem definition, mutual collaborative calls, and remote operation, maintenance, monitoring, and repair. Appropriate supporting systems should be in place for automated production release pipelines, orchestration and scheduling management, and operation and maintenance monitoring, implemented as a middleware with a multi-professional common standard. The organization and management of application software and hardware resources before upgrades, orchestration and scheduling during upgrades (such as canary releases and rollbacks), health checks and operational monitoring after upgrades, and access to the console by application software developers when necessary (such as operating system command consoles and log file access) should all be systematic, application-burden-free, with each component fulfilling its responsibilities and achieving standardization. As a middleware and digital foundation, it reduces the mental burden on application software developers, allowing them to focus on business development.
[0006] In existing technologies, edge gateways offer common functions such as user login, parameter viewing, device configuration, container management, APP management, device upgrades, file transfer, and maintenance terminal requirements. This standard leaves the management of edge gateway devices and the handling of input / output data (such as configuration, logs, models, statistical analysis, and collected data) to each edge gateway device manufacturer for independent design and development. This approach is not a sound architectural concept for a central platform or digital infrastructure. Different manufacturers will inevitably implement these functions differently, with variations in details. This prevents lightweight, modular, and specialized collaboration at the edge, allowing each manufacturer to leverage their strengths, and complicates the upgrade process. Summary of the Invention
[0007] To address the shortcomings of existing technologies, this invention provides a remote upgrade method for intelligent waveform recorders based on distributed containerization. This method enables the intelligent waveform recorder to serve as an extension of hardware resources and auxiliary supporting functions in edge clusters and the cloud, reusing the same unified technology system and supporting ecosystem for remote upgrades.
[0008] The present invention adopts the following technical solution.
[0009] A remote upgrade method for a smart waveform recorder based on distributed containerization includes the following steps: Transform the smart waveform recorder's application into a containerized microservice architecture and deploy it on a container management platform; Before a remote upgrade, apply to the container management platform for the CPU, memory, and storage resources required for the upgrade, and build the upgrade package, configuration script, dependency declaration, change declaration, startup order declaration, rollback plan, and health check plan. Remote upgrades are performed using a canary release strategy, which executes new version service instances on each node and stops old version service instances. After the remote upgrade is completed, performance monitoring and online regression testing are performed on the new version service instance. Performance monitoring includes interface call time, CPU utilization, memory utilization and disk I / O. If the monitoring indicators are abnormal or the test fails, a rollback operation is performed. If performance monitoring is normal and online regression testing is successful, verify the program version and provide a remote operation and maintenance interface to complete the remote upgrade of the intelligent waveform recorder.
[0010] Preferably, the transformation of the intelligent waveform recorder's application into a containerized microservice architecture and its deployment in a container management platform specifically includes: The intelligent waveform recorder is transformed into a distributed system. The communication front-end service of the intelligent waveform recorder maintains a stable IO connection, while enabling distributed load balancing of IO access. It uses packet assembly and decompression of various protocols as a protocol parsing service to handle IO uplink and downlink message queues; Build a task orchestration and scheduling microservice to schedule read and write tasks for various protocol communication according to priority; Build microservice applications, including remote upgrade and configuration update task microservices, remote control microservices, and proxy read, pass-through, and copy-through microservices; Based on the data returned by the above microservice applications, statistical analysis is performed, including waveform analysis, communication status analysis, same source comparison, and fixed value comparison. Build a data storage and forwarding microservice for storing and forwarding data.
[0011] Preferably, the remote upgrade also includes the following preparatory work: Separate I / O communication into an independent communication front-end module; Separate the protocol extension into an independent protocol parsing service module; The business read and write tasks are separated into task orchestration and scheduling microservice modules.
[0012] Preferably, the remote upgrade using a canary release strategy specifically includes: During remote upgrade execution, the new version service instance is started sequentially on each node. After the health check passes, business traffic is switched to the new instance, and the old version service instance is stopped.
[0013] Preferably, the verification program version includes determining whether the installed APP data is valid, as follows: Install the root certificate on the container management platform; After receiving the APP installation package, the container management platform decompresses it to obtain the APP certificate, image, and digital signature; The validity of the APP certificate is verified by the root certificate, and the first digital digest Sum1 is obtained by digitally digesting the image. The first digital digest Sum1 is then encrypted using the private key to obtain the digital signature.
[0014] Obtain the public key through the APP certificate, and use the public key to decrypt the digital signature to obtain the second digital digest Sum2; If the first digital digest Sum1 equals the second digital digest Sum2, then the APP data is considered valid.
[0015] Preferably, the remote operation and maintenance interface includes an access console, an operating system command console, and a log file acquisition interface to support remote debugging and operational evaluation by application software developers.
[0016] Preferably, the original data interface of the Kubernetes container management platform is mapped to an extended service that meets the communication message specifications of the substation secondary system for communication. The operation and maintenance management related data adopts a modeling approach, and combines RPC subscription, dynamic datasets and file services to realize data interaction of management information, equipment status, graphic files, APP files and APP running status.
[0017] This invention also proposes a remote upgrade system for intelligent waveform recorders based on distributed containerization, used to implement the remote upgrade method for intelligent waveform recorders based on distributed containerization, including: The deployment module was modified to transform the application of the intelligent waveform recorder into a containerized microservice architecture and deploy it on a container management platform. The upgrade preparation module is used to request the CPU, memory, and storage resources required for the upgrade from the container management platform before a remote upgrade, and to build the upgrade package, configuration script, dependency declaration, change declaration, startup order declaration, rollback plan, and health check plan. The upgrade execution module is used to start the new version service instance on each node sequentially during remote upgrade execution. After the health check is passed, the business traffic is switched to the new instance and the old version service instance is stopped. The monitoring module is used to perform performance monitoring and online regression testing on the new version service instance after the remote upgrade is completed. Performance monitoring includes interface call time, CPU utilization, memory utilization and disk I / O. If the monitoring indicators are abnormal or the test fails, a rollback operation is performed. The remote operation and maintenance module is used to verify the program version and provide a remote operation and maintenance interface to complete the remote upgrade of the intelligent waveform recorder when performance monitoring is normal and online regression testing is successful.
[0018] The present invention also proposes a terminal, including a processor and a storage medium; The storage medium is used to store instructions; The processor is used to operate according to the instructions to execute the steps of the remote upgrade method for the intelligent waveform recorder based on distributed containerization.
[0019] The present invention also proposes a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the remote upgrade method for the intelligent waveform recorder based on distributed containerization.
[0020] The beneficial effects of this invention are that, compared with the prior art, this invention uses the hardware of numerous intelligent waveform recorders as a hardware resource pool, and the application software is stateless, decentralized, distributed, and highly available. Service availability is guaranteed as long as any single node is functioning normally. It has the ability to ensure uninterrupted business services (such as uplink / downlink access and forwarding communication) during upgrades. The beneficial effects of this invention include at least the following: 1. This invention can maintain uninterrupted service and ensure that real-time data streams are not lost during the upgrade of intelligent waveform recorders. By decoupling the IO communication front-end service from the protocol parsing service, and adopting a node-level canary release combined with a dynamic traffic switching strategy that is aware of queue backlog, it ensures that the underlying link remains connected during the upgrade process, the message queue is temporarily stored and processed by the new instance, and at least one node carries all service traffic at any time. This achieves zero service interruption and zero message loss during the upgrade, overcoming the shortcomings of general containerized upgrades that allow short-term interruptions. 2. This invention transforms the intelligent waveform recorder application into a stateless, decentralized, distributed microservice architecture. All microservice modules are deployed in a distributed manner and support load balancing. As long as one node is normal, the entire system can be guaranteed to be highly available. Before the upgrade, sufficient spare resources (CPU / memory) are applied for and locked through a container management platform to avoid processing delays caused by resource contention, significantly improving system reliability and availability. 3. This invention enables separate bidding for software and hardware, allowing all specialties to reuse hardware resources as much as possible. The intelligent waveform recorder management unit at the substation end is transformed from idle operation and power consumption to actual working condition operation, saving the electricity cost of a single server, while reducing the footprint of the cabinet and improving the resource reuse rate. 4. This invention enables centralized management and control of various professional applications within a unified container management platform, achieving automated and batch upgrades in the background, reducing the risk of manual misconfiguration and improving production release efficiency. Before the upgrade, it supports resource requests, dependency declarations, startup order declarations, rollback plans, and health checks; after the upgrade, it automatically performs performance monitoring (interface latency, CPU, memory, disk I / O) and online regression testing, automatically rolling back in case of anomalies, thus achieving standardized and automated remote upgrade and operation management. 5. This invention decouples each module through a microservice modular design, allowing for independent upgrades, hot orchestration, and hot updates. It supports collaboration between multiple vendors' apps through standardized interfaces, enhancing the system's scalability and maintainability. 6. The statistical analysis services of this invention (wavelength analysis, communication status analysis, source comparison, and fixed value comparison) are traceable and recalculated. Incomplete or abnormal data are marked as unreliable, and recalculation is performed after the data is copied back to normal, ensuring the accuracy of the analysis results and improving the reliability of fault diagnosis and service analysis. Attached Figure Description
[0021] Figure 1 This is a flowchart of the remote upgrade method for an intelligent waveform recorder based on distributed containerization in this invention; Figure 2 This is a schematic diagram of the technical architecture of the distributed microservice module in this invention; Figure 3 This is a schematic diagram illustrating the process of remotely upgrading distributed nodes one by one without interrupting the data flow in this invention; Figure 4 This is a schematic diagram of the transformation of the original software architecture into a distributed microservice module in this invention. Figure 5 This is a schematic diagram of the remote upgrade process in this invention; Figure 6 This is the process of packaging the intelligent waveform recorder container APP business application in this invention; Figure 7 This invention describes the process for verifying the security of the smart waveform recorder container APP business application before remote upgrade; Figure 8 This is a structural diagram of the remote upgrade system for intelligent waveform recorders based on distributed containerization in this invention. Detailed Implementation
[0022] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of this invention. The embodiments described in this application are merely some embodiments of this invention, and not all embodiments. Based on the spirit of this invention, other embodiments obtained by those skilled in the art without creative effort are all within the protection scope of this invention.
[0023] like Figure 1 As shown, this invention proposes a remote upgrade method for intelligent waveform recorders based on distributed containerization. The method specifically includes the following steps: Step 1: Modify the intelligent waveform recorder program using containerization, microservices, distributed systems, and cloud technologies to prepare for secure and convenient remote upgrades. like Figure 2 As shown, the application of the intelligent waveform recorder is transformed into a containerized microservice architecture and deployed in a Kubernetes-based container management platform.
[0024] like Figure 3 and Figure 4 As shown, step 1 specifically includes: Step 1-1: Perform distributed transformation on the intelligent waveform recorder, maintain stable IO connections through a communication front-end service, and achieve distributed load balancing for IO access. In the traditional approach, IO communication and protocol parsing are integrated, and upgrading the protocol module inevitably leads to link interruption; however, this application separates the almost unchanging IO communication (such as TCP and UDP) as an independent communication front-end module, ensuring uninterrupted link operation during the upgrade process.
[0025] Steps 1-2: Use packet assembly and unpacking of various protocols as a protocol parsing service to handle IO uplink and downlink message queues. Separate frequently changing protocol extensions (such as the 61850 protocol extension) into independent protocol parsing service modules to achieve plug-and-play functionality, prevent message loss during upgrades, and allow new and old programs on each node to preemptively process the messages.
[0026] Steps 1-3: Construct a task orchestration and scheduling microservice to schedule various protocol communication read and write tasks according to priority. Separate various business read and write operations based on minutes, days, weeks, months, and temporary one-off tasks to achieve task orchestration, monitoring, online intervention, and hot update capability.
[0027] Steps 1-4: Build multiple microservice applications, including a remote upgrade and configuration update task microservice, a remote control microservice, and a proxy read, pass-through, and copy microservice. This way, when a few modules are changed, the previously almost unchanged IO communication can maintain uninterrupted connections without requiring large-scale re-establishment of connections and application-layer handshakes (such as the 103 protocol).
[0028] Steps 1-5: Perform statistical analysis based on the data returned by the above microservice applications, including waveform analysis, communication status analysis, source comparison, and fixed value comparison.
[0029] Steps 1-6: Build a data storage and forwarding microservice for storing and forwarding data.
[0030] like Figure 4 As shown, the present invention constructs each microservice module in a distributed deployment, supports load balancing, ensures that as long as one node is normal, the high availability of the entire system can be guaranteed, and enables communication messages to remain uninterrupted and not lost during the process of upgrading node by node.
[0031] like Figure 5 As shown, steps 2-5 of the present invention specifically include: Step 2, Preparations for Remote Upgrade; Before a remote upgrade, apply to the container management platform for the necessary CPU, memory, and storage resources, and build the upgrade package, configuration scripts, dependency declarations (e.g., module A depends on module B), change declarations, startup order declarations (e.g., module A needs to start after module C), rollback plan, and health check plan. In addition, necessary approval processes and online testing and verification plans are also included.
[0032] This invention further separates the almost unchanging IO communication into an independent communication front-end module, the frequently changing protocol extensions into an independent protocol parsing service module, and the business read / write tasks into a task orchestration and scheduling microservice module. Through a Kubernetes-based container management platform, it provides systematic pre-upgrade support capabilities for remote upgrades, allowing waveform recorder manufacturers to focus solely on their own business development without needing to prepare differentiated upgrade solutions.
[0033] Step 3: During the remote upgrade process, monitor the upgrade execution and execute various upgrade strategies, such as starting the new service first and stopping the old service or canary release after the health check passes, or only cutting off a portion of the traffic.
[0034] When performing remote upgrades, a canary release strategy is adopted: the new version service instance is started sequentially on each node, and after the health check is passed, business traffic is gradually switched to the new instance, and then the old version service instance is stopped.
[0035] Specifically, first update a very small number of production nodes (e.g., no more than 5% of the total production nodes) or switch a small portion of production traffic (e.g., no more than 5% of the total production traffic) to verify the stability of the new version in a real production environment with small-scale traffic. Once the verification is successful, gradually expand the scope. This strategy can avoid the risk of affecting all users when problems occur, as is the case with the traditional full release method.
[0036] As a preferred implementation, to further improve the reliability and adaptability of remote upgrades, this invention employs an improved canary release strategy to perform remote upgrades. Since conventional Kubernetes rolling updates only determine whether to switch traffic based on Pod readiness probes, without considering the real-time packet queue backlog status of the intelligent waveform recorder during the upgrade process, this invention proposes a dynamic traffic switching strategy based on queue backlog awareness, as follows: Before the canary release, the task orchestration and scheduling microservice built in steps 1-3 is used to monitor the uplink message queue length, downlink message queue length and processing latency on each node in real time. Once the new version service instance starts up and passes the health check, instead of immediately switching all traffic, 1% to 5% of the tagged traffic (such as packets of specific MMS message types or specific device IDs) is first directed to the new instance. At the same time, the packet processing latency, queue backlog change rate, and error rate of the new instance are continuously monitored. A preset observation window is set. If, within the preset observation window, the message processing delay of the new instance does not exceed 1.2 times that of the old instance and the backlog queue length does not continue to increase, it indicates that there is no abnormality. If there is no abnormality, the traffic ratio is gradually increased, and the above monitoring is repeated at each stage. In this invention, the preset observation window is 30 seconds, and the traffic ratio is doubled according to the previous traffic ratio until all traffic is observed. If any stage fails, an automatic rollback will be triggered: traffic will be immediately switched back to the old instance, the upgrade will be paused, and an alarm log will be generated for operations and maintenance personnel to analyze.
[0037] The improved canary release strategy described above, combined with the queue characteristics of real-time data streams in the intelligent waveform recorder service, achieves adaptive and observable traffic switching.
[0038] Furthermore, in the aforementioned improved canary release strategy, the preset observation window and fixed threshold are still passive responses. To further enhance the initiative and robustness of traffic switching during the upgrade process, this embodiment also proposes a dynamic threshold adjustment method based on short-term queue backlog prediction, as follows: The task orchestration and scheduling microservice built in steps 1-3 continuously collects the message queue length change rate, processing latency jitter, and CPU / memory utilization of each node over the past five observation windows, forming a feature vector. An online linear regression model is then used to predict the peak queue backlog for the next observation window.
[0039] Within a preset observation window, the tolerance coefficient is dynamically calculated. : =min(1.5,1+0.5×(predicted peak value / (current queue length of old instances + 1))) If the processing latency of the new instance does not exceed the latency and tolerance factor of the old instance. If the product of the two values is true and the queue backlog change rate does not exceed the preset threshold, it is considered normal, and the traffic ratio can be further increased; otherwise, the traffic switching speed should be reduced or a rollback should be triggered.
[0040] This prediction-driven approach can handle sudden traffic spikes and avoids false rollbacks due to overly strict fixed thresholds or packet loss due to overly lenient thresholds. It is more suitable for upgrading intelligent waveform recorders in high-throughput and high-real-time scenarios.
[0041] Step 4: After the remote upgrade is complete, perform a health check and performance monitoring on the new version service, including API call time, CPU utilization, memory utilization, and disk I / O. Simultaneously, perform online regression testing. If monitoring metrics are abnormal or tests fail, rollback operations are performed according to the pre-prepared rollback plan, reverting to the old version and configuration.
[0042] Step 5: Check program version changes, perform necessary remote operation and maintenance debugging (such as executing Linux commands and downloading program running logs), and evaluate the program's performance.
[0043] This invention verifies the program version and provides a remote operation and maintenance interface for executing debugging commands and downloading runtime logs. For example... Figure 6 and Figure 7 As shown, program version verification includes validally judging the APP data, as detailed below: Step 5-1: Install the root certificate on the platform; Step 5-2: After receiving the APP installation package, the platform decompresses it to obtain the APP certificate, image, and digital signature; Step 5-3: Verify the validity of the APP certificate through the root certificate, and perform a digital digest on the image to obtain the first digital digest Sum1. Use the private key to encrypt the first digital digest Sum1 to obtain the digital signature.
[0044] Step 5-4: Obtain the public key through the APP certificate, and use the public key to decrypt the digital signature to obtain the second digital digest Sum2; Step 5-5: If Sum1 equals Sum2, then the APP data is deemed valid.
[0045] Meanwhile, the remote operation and maintenance interface supports access to the operating system command console and obtaining operation logs, enabling application software developers to perform remote debugging and operation evaluation.
[0046] As a preferred implementation, to adapt to special communication needs, since the power system security zone I cannot use the data interfaces of various modules of conventional Kubernetes container management platforms such as HTTP, this method maps the original data interface to the extended service of the "DL / T 860 Substation Secondary System Communication Message Specification" (CMS) for communication. Operation and maintenance management related data adopts a modeling approach, combining RPC subscriptions, dynamic datasets, and file services to achieve the interaction of various types of data such as management information, equipment status, graphic files, APP files, and APP running status. Standardized interfaces are defined between the APPs of different manufacturers, and the APP design vendors provide JSON-formatted profile capability description files, including APP resource requirements and data interface definitions.
[0047] like Figure 8 As shown, this invention also proposes a remote upgrade system for intelligent waveform recorders based on distributed containerization, used to implement the aforementioned remote upgrade method for intelligent waveform recorders based on distributed containerization. The system includes: The deployment module was modified to transform the application of the intelligent waveform recorder into a containerized microservice architecture and deploy it on a container management platform. The upgrade preparation module is used to request the CPU, memory, and storage resources required for the upgrade from the container management platform before a remote upgrade, and to build the upgrade package, configuration script, dependency declaration, change declaration, startup order declaration, rollback plan, and health check plan. The upgrade execution module is used to start the new version service instance on each node sequentially during remote upgrade execution. After the health check is passed, the business traffic is switched to the new instance and the old version service instance is stopped. The monitoring module is used to perform performance monitoring and online regression testing on the new version service instance after the remote upgrade is completed. Performance monitoring includes interface call time, CPU utilization, memory utilization and disk I / O. If the monitoring indicators are abnormal or the test fails, a rollback operation is performed. The remote operation and maintenance module is used to verify the program version and provide a remote operation and maintenance interface to complete the remote upgrade of the intelligent waveform recorder when performance monitoring is normal and online regression testing is successful.
[0048] The beneficial effects of this invention are that, compared with the prior art, this invention uses the hardware of numerous intelligent waveform recorders as a hardware resource pool, and the application software is stateless, decentralized, distributed, and highly available. As long as any node is normal, the service can be guaranteed to be available, and it has the ability to ensure that business services (such as uplink and downlink access and forwarding communication) are not interrupted during the upgrade process.
[0049] This disclosure can be a system, method, and / or computer program product. A computer program product may include a computer-readable storage medium having computer-readable program instructions loaded thereon for causing a processor to implement various aspects of this disclosure.
[0050] Computer-readable storage media can be tangible devices capable of holding and storing instructions for use by an instruction execution device. Computer-readable storage media can be, for example—but not limited to—electrical storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of computer-readable storage media include: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disc read-only memory (CD-ROM), digital multifunction disc (DVD), memory sticks, floppy disks, mechanical encoding devices, such as punch cards or recessed protrusions storing instructions thereon, and any suitable combination of the foregoing. The computer-readable storage media used herein are not to be construed as transient signals themselves, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., light pulses through fiber optic cables), or electrical signals transmitted through wires.
[0051] The computer-readable program instructions described herein can be downloaded from computer-readable storage media to various computing / processing devices, or downloaded via a network, such as the Internet, local area network, wide area network, and / or wireless network, to an external computer or external storage device. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards them to the computer-readable storage media in the respective computing / processing device.
[0052] Computer program instructions used to perform the operations of this disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages such as Smalltalk, C++, etc., and conventional procedural programming languages such as the "C" language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, electronic circuitry, such as programmable logic circuitry, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), is personalized by utilizing the status information of the computer-readable program instructions to implement various aspects of this disclosure.
[0053] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit it. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that modifications or equivalent substitutions can still be made to the specific implementation of the present invention. Any modifications or equivalent substitutions that do not depart from the spirit and scope of the present invention should be covered within the protection scope of the claims of the present invention.
Claims
1. A remote upgrade method for an intelligent waveform recorder based on distributed containerization, characterized in that, Includes the following steps: Transform the smart waveform recorder's application into a containerized microservice architecture and deploy it on a container management platform; Before a remote upgrade, apply to the container management platform for the CPU, memory, and storage resources required for the upgrade, and build the upgrade package, configuration script, dependency declaration, change declaration, startup order declaration, rollback plan, and health check plan. Remote upgrades are performed using a canary release strategy, which executes new version service instances on each node and stops old version service instances. After the remote upgrade is completed, performance monitoring and online regression testing are performed on the new version service instance. Performance monitoring includes interface call time, CPU utilization, memory utilization and disk I / O. If the monitoring indicators are abnormal or the test fails, a rollback operation is performed. If performance monitoring is normal and online regression testing is successful, verify the program version and provide a remote operation and maintenance interface to complete the remote upgrade of the intelligent waveform recorder.
2. The remote upgrade method for an intelligent waveform recorder based on distributed containerization according to claim 1, characterized in that, The process of transforming the intelligent waveform recorder's application into a containerized microservice architecture and deploying it on a container management platform specifically includes: The intelligent waveform recorder is transformed into a distributed system. The communication front-end service of the intelligent waveform recorder maintains a stable IO connection, while enabling distributed load balancing of IO access. It uses packet assembly and decompression of various protocols as a protocol parsing service to handle IO uplink and downlink message queues; Build a task orchestration and scheduling microservice to schedule read and write tasks for various protocol communication according to priority; Build microservice applications, including remote upgrade and configuration update task microservices, remote control microservices, and proxy read, pass-through, and copy-through microservices; Based on the data returned by the above microservice applications, statistical analysis is performed, including waveform analysis, communication status analysis, same source comparison, and fixed value comparison. Build a data storage and forwarding microservice for storing and forwarding data.
3. The remote upgrade method for an intelligent waveform recorder based on distributed containerization according to claim 1, characterized in that, The remote upgrade also includes the following preparatory work: Separate I / O communication into an independent communication front-end module; Separate the protocol extension into an independent protocol parsing service module; The business read and write tasks are separated into task orchestration and scheduling microservice modules.
4. The remote upgrade method for an intelligent waveform recorder based on distributed containerization according to claim 1, characterized in that, The implementation of a canary release strategy for remote upgrades specifically includes: During remote upgrade execution, the new version service instance is started sequentially on each node. After the health check passes, business traffic is switched to the new instance, and the old version service instance is stopped.
5. The remote upgrade method for an intelligent waveform recorder based on distributed containerization according to claim 1, characterized in that, The verification process includes determining whether the installed APP data is valid, as detailed below: Install the root certificate on the container management platform; After receiving the APP installation package, the container management platform decompresses it to obtain the APP certificate, image, and digital signature; The validity of the APP certificate is verified by the root certificate, and the first digital digest Sum1 is obtained by digitally digesting the image. The first digital digest Sum1 is then encrypted using the private key to obtain the digital signature. Obtain the public key through the APP certificate, and use the public key to decrypt the digital signature to obtain the second digital digest Sum2; If the first digital digest Sum1 equals the second digital digest Sum2, then the APP data is considered valid.
6. The remote upgrade method for an intelligent waveform recorder based on distributed containerization according to claim 1, characterized in that, The remote operation and maintenance interface includes an access console, an operating system command console, and a log file retrieval interface to support application software developers in remote debugging and operational evaluation.
7. The remote upgrade method for an intelligent waveform recorder based on distributed containerization according to claim 1, characterized in that, The original data interface of the Kubernetes container management platform is mapped to an extended service that meets the communication message specifications of the substation secondary system for communication. The operation and maintenance management related data adopts a modeling approach, and combines RPC subscription, dynamic datasets and file services to realize data interaction of management information, equipment status, graphic files, APP files and APP running status.
8. A remote upgrade system for an intelligent waveform recorder based on distributed containerization, used to implement the remote upgrade method for an intelligent waveform recorder based on distributed containerization as described in any one of claims 1-7, characterized in that, include: The deployment module was modified to transform the application of the intelligent waveform recorder into a containerized microservice architecture and deploy it on a container management platform. The upgrade preparation module is used to request the CPU, memory, and storage resources required for the upgrade from the container management platform before a remote upgrade, and to build the upgrade package, configuration script, dependency declaration, change declaration, startup order declaration, rollback plan, and health check plan. The upgrade execution module is used to perform remote upgrades using a canary release strategy, execute new version service instances on each node, and stop old version service instances; The monitoring module is used to perform performance monitoring and online regression testing on the new version service instance after the remote upgrade is completed. Performance monitoring includes interface call time, CPU utilization, memory utilization and disk I / O. If the monitoring indicators are abnormal or the test fails, a rollback operation is performed. The remote operation and maintenance module is used to verify the program version and provide a remote operation and maintenance interface to complete the remote upgrade of the intelligent waveform recorder when performance monitoring is normal and online regression testing is successful.
9. A terminal, comprising a processor and a storage medium; characterized in that: The storage medium is used to store instructions; The processor is configured to operate according to the instructions to perform the steps of the method according to any one of claims 1-7.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the program implements the steps of the method according to any one of claims 1-7.
