Containerized deployment method and system for intelligent fusion terminal

Abstract

According to the containerized deployment method and system for the intelligent fusion terminal, applications of different service domains are isolated through the container, application faults in a single service domain cannot be diffused, and the overall operation stability of the terminal is improved. The method comprises the steps of obtaining a to-be-deployed application, performing functional attribute classification on the to-be-deployed application, and dividing the to-be-deployed application into a basic application directly interacting with terminal hardware or an operating system core and a service application for realizing upper-layer service logic; deploying the basic application in a host operating system environment of the intelligent fusion terminal; service attribute classification is carried out on the service applications, the service applications are classified into a plurality of different service domains, a corresponding independent container environment is constructed for each service domain, and each independent container is allocated with a preset resource quota; and respectively deploying the business applications in the independent container environments corresponding to the classified business domains.

Description

Technical Field

[0001] This application relates to the field of power Internet of Things (IoT) technology, specifically to a containerized deployment method and system for intelligent converged terminals. Background Technology

[0002] In recent years, with the deepening development of smart grids, smart converged terminals, as the core edge computing nodes, not only need to carry out traditional power metering and data collection, but also need to efficiently operate increasingly complex and diversified key business applications such as marketing business interaction, distribution automation, and distributed energy management.

[0003] However, traditional terminal software generally adopts an integrated architecture that tightly couples all application software with system services and deploys them together in a single operating system environment. This design pattern has inherent flaws in terms of stability and maintainability. Due to the lack of effective isolation mechanisms, the unexpected crash, memory leak, or CPU overload of any business application (such as a certain advanced analysis module) can affect other innocent businesses, or even trigger a cascading down of the entire terminal system, seriously threatening the stable operation of the local power grid. In addition, this tightly coupled architecture also brings deep-seated operational and maintenance difficulties. Different business software often depend on different versions of system libraries, runtime environments, or configuration files, and their coexistence within the same system can easily lead to dependency conflicts. At the same time, their disorderly contention for underlying resources such as CPU, memory, and network bandwidth also makes system performance difficult to predict.

[0004] Therefore, in view of the above problems and needs, this application proposes a containerized deployment method and system for intelligent converged terminals. Summary of the Invention

[0005] This application provides a containerized deployment method and system for intelligent converged terminals. By isolating applications in different business domains through containers, application failures within a single business domain will not spread, thus avoiding systemic risks and significantly improving the overall operational stability of the terminal.

[0006] To achieve the above objectives, this application adopts the following technical solution:

[0007] Firstly, this application provides a containerized deployment method for intelligent converged terminals, the method comprising:

[0008] Obtain the applications to be deployed and classify them by their functional attributes, dividing them into basic applications that directly interact with the terminal hardware or the core of the operating system, and business applications that implement upper-layer business logic.

[0009] Deploy basic applications within the host operating system environment of intelligent converged terminals;

[0010] Business applications are classified by business attributes and categorized into multiple different business domains. A corresponding independent container environment is built for each business domain, and each independent container is allocated a preset resource quota.

[0011] Deploy business applications in separate container environments corresponding to the business domains they are categorized into.

[0012] Secondly, this application provides a containerized deployment system for intelligent converged terminals, the system comprising:

[0013] The application acquisition and classification module is used to acquire applications to be deployed and classify them by functional attributes, dividing them into basic applications that directly interact with terminal hardware or the core of the operating system, and business applications that implement upper-layer business logic.

[0014] The business domain management module is used to classify business applications by business attributes, categorize business applications into multiple different business domains, and build a corresponding independent container environment for each business domain. Each independent container is allocated a preset resource quota.

[0015] The host operating system environment is used to directly run basic applications that interact with the terminal hardware or the operating system kernel.

[0016] At least one independent container environment is deployed on top of the host operating system environment. Each independent container environment is allocated a preset resource quota to run one or more business applications belonging to the same business domain.

[0017] In this embodiment, by classifying terminal software by function and business dimensions and adopting a differentiated deployment strategy of "basic applications residing in the host operating system and business applications isolated in independent containers," the traditional integrated architecture is fundamentally revolutionized. In addition, by creating dedicated container environments for different business domains such as marketing and power distribution and presetting independent resource quotas, this method achieves strong isolation and resource protection between businesses, accurately curbing the chain reaction caused by the failure of a single application. Furthermore, through the above-mentioned differentiated deployment, it achieves uninterrupted updates and rolling upgrades for single business applications—operations within any container will not affect the stable operation of other businesses or the host system, thereby significantly improving the overall reliability, maintainability, and business continuity of the terminal in complex business scenarios.

[0018] Other features and advantages of this application will be described in detail in the following detailed description section. Attached Figure Description

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

[0020] Figure 1 A flowchart illustrating the containerized deployment method for intelligent converged terminals provided in this application embodiment;

[0021] Figure 2 This is a schematic diagram of the architecture of the host operating system environment and the independent container environment provided in the embodiments of this application. Detailed Implementation

[0022] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application. At the same time, in the description of the embodiments of this application, the terms "first," "second," etc., are only used to distinguish descriptions and should not be construed as indicating or implying relative importance. Thus, features defined with "first" and "second" may explicitly or implicitly include one or more features. In the description of the embodiments of this application, "multiple" means two or more, unless otherwise explicitly specified.

[0023] Figure 1 This is a flowchart illustrating a containerized deployment method for intelligent converged terminals provided in an embodiment of this application.

[0024] The process for containerized deployment of intelligent converged terminals is as follows:

[0025] Step S101: Obtain the application to be deployed and classify the application by its functional attributes, dividing it into basic applications that directly interact with the terminal hardware or the core of the operating system, and business applications that implement upper-layer business logic.

[0026] Step S102: Deploy the basic application in the host operating system environment of the smart converged terminal.

[0027] Step S103: Classify business applications by business attributes, categorize business applications into multiple different business domains, and build a corresponding independent container environment for each business domain. Each independent container is allocated a preset resource quota.

[0028] Step S104: Deploy the business applications in the independent container environments corresponding to the respective business domains.

[0029] In this embodiment, resource quotas include at least the memory usage limit and the CPU utilization limit.

[0030] This configuration effectively prevents a single business container from excessively consuming system resources, ensuring that resources between different business domains do not encroach on each other's resources. For example, a maximum of 1GB of memory and 30% CPU utilization can be allocated to the marketing business container, while a maximum of 2GB of memory and 50% CPU utilization can be allocated to the power distribution business container. This resource limitation mechanism ensures the reliable operation of critical businesses while preventing system-level resource exhaustion caused by an anomaly in a single business, thereby significantly improving the overall stability of the terminal system and the quality of business services.

[0031] In this embodiment, the basic application includes at least the application responsible for hardware interface management.

[0032] For example, core components that directly interact with the terminal's physical hardware include serial communication services, Ethernet driver management modules, and wireless communication protocol stacks. By deploying these components within the host operating system, exclusive and efficient access to hardware resources can be ensured, avoiding performance degradation and access latency caused by containerization.

[0033] In this embodiment, multiple different business domains include the marketing business domain, the power distribution business domain, and the metering business domain.

[0034] It is understandable that by deploying business applications in different professional domains in independent container environments, refined management of business functions is achieved. For example, containers in the marketing business domain can deploy applications such as electricity billing and user information management; containers in the power distribution business domain can run core businesses such as fault detection and topology analysis; and containers in the metering business domain can handle tasks such as data acquisition and power quality analysis. This containerized deployment approach, divided by business domain, not only ensures a specialized operating environment for various businesses but also effectively prevents mutual interference between different business domains through container isolation mechanisms, greatly improving the reliability and maintainability of the system.

[0035] In this embodiment, after deploying the business applications in independent container environments corresponding to the categorized business domains, the method further includes:

[0036] When a failure is detected in any independent container, the faulty container is automatically isolated.

[0037] It should be noted that when a failure is detected in any independent container's application, the faulty container can be automatically isolated. This can also be understood as the fault isolation mechanism built upon the aforementioned containerized architecture enabling rapid fault detection and intelligent isolation.

[0038] In addition to isolating faulty containers, it can also automatically create new container instances and redeploy the same business applications within the preset resource quota, thereby enabling rapid business recovery.

[0039] For example, when a business application software in any container environment fails, the impact of the failure is limited to the boundary of that container, without affecting the stability of the basic application software in the host operating system or the normal operation of business application software in other container environments.

[0040] In this embodiment, the independent container supports elastic scaling, which can dynamically adjust the allocated resources according to the load of the business applications within the independent container.

[0041] It should be noted that the elastic scaling mechanism achieves intelligent resource allocation by monitoring key performance indicators of each container in real time (such as CPU utilization, memory utilization, network throughput, etc.).

[0042] When the resource utilization rate of a container is detected to continuously exceed the preset threshold, additional computing resources will be automatically allocated to it; conversely, when the resource utilization rate is detected to be low for a long period of time, the resource quota will be appropriately reduced to improve the overall resource utilization rate.

[0043] In summary, this application embodiment fundamentally revolutionizes the traditional integrated architecture by classifying terminal software according to functional and business dimensions and adopting a differentiated deployment strategy of "basic applications residing in the host operating system and business applications isolated in independent containers." Furthermore, by creating dedicated container environments for different business domains such as marketing and power distribution and pre-setting independent resource quotas, this method achieves strong isolation and resource assurance between businesses, precisely curbing the chain reaction caused by a single application failure. Additionally, through the aforementioned differentiated deployment, it enables uninterrupted updates and rolling upgrades of single business applications—operations within any container will not affect the stable operation of other businesses or the host system, thereby significantly improving the overall reliability, maintainability, and business continuity of the terminal in complex business scenarios.

[0044] The above combination Figures 1-2 The containerized deployment method for intelligent converged terminals provided in the embodiments of this application is described in detail. The following examples illustrate the above-mentioned containerized deployment method for intelligent converged terminals.

[0045] Step 1: Categorize a batch of application software to be deployed.

[0046] Analysis revealed that uartManager (serial port management) and smiOS (system management) are directly interacted with hardware or operating system core services, and therefore they are uniformly classified as basic application classes;

[0047] Meanwhile, the analysis concluded that puAmr (low-voltage centralized meter reading) and IEC104 (protocol interaction) are classified as business application classes because they implement specific upper-layer business logic.

[0048] Step 2: Implement differentiated deployment based on the above classification results.

[0049] uartManager and smiOS, as basic application software, are deployed directly in the host operating system environment of the terminal to ensure the highest running efficiency.

[0050] puAmr and IEC104, as business application software, were transferred to the next step for containerized deployment.

[0051] Step 3: Perform containerized deployment for puAmr and IEC104.

[0052] Based on their business attributes, puAmr is classified into the marketing business domain, and IEC104 is classified into the power distribution business domain.

[0053] Subsequently, the system created a separate container named amrContainer for the marketing business domain and configured it with a resource quota of 400MB memory and 90% CPU utilization.

[0054] At the same time, a pdContainer container is created for the power distribution business domain, and a resource quota of 300MB memory and 90% CPU utilization is configured.

[0055] Finally, puAmr is deployed in amrContainer and IEC104 is deployed in pdContainer, thus completing the construction of a two-tier heterogeneous software runtime architecture.

[0056] Based on steps one through three above, when the terminal is running normally, basic application software such as uartManager running on the host operating system and business application software running in amrContainer and pdContainer are completely isolated in terms of process space and resource allocation.

[0057] For example, suppose the puAmr software within amrContainer experiences a memory leak due to a program defect.

[0058] Due to the resource quota limitations of the container, the impact of this failure will be strictly limited to the 400MB memory boundary of the amrContainer and will not exhaust the total system memory.

[0059] Therefore, the stable operation of uartManager in the host operating system and the normal operation of IEC104 in pdContainer are not affected in any way, thus achieving precise fault domain limitation.

[0060] For example, based on the stable operating state of isolation, non-disruptive updates to individual business applications can be achieved.

[0061] Based on steps one through three above, when an upgrade of the IEC104 software is required, the system first identifies the pdContainer containing the software as the unique target domain for operation. Within this unique target domain, the system performs update operations such as stopping, replacing, and restarting the old version of the IEC104 software.

[0062] Throughout the update process, thanks to the isolation features established in this application, the basic application software in the host operating system and the business application software in other containers continue to run without being affected by the update operation, thus achieving a non-disruptive update of individual services.

[0063] In addition, in practical applications, the containerized deployment in step three of this application can be carried out with reference to Table 1.

[0064] Table 1

[0065]

[0066]

[0067]

[0068] The above describes the containerized deployment method and application for intelligent converged terminals provided in the embodiments of this application. The following details the containerized deployment system for intelligent converged terminals provided in the embodiments of this application.

[0069] The system specifically includes: an application acquisition and classification module, a business domain management module, a host operating system environment, and at least one independent container environment, as shown below.

[0070] The application acquisition and classification module is used to acquire applications to be deployed and classify them by functional attributes, dividing them into basic applications that directly interact with terminal hardware or the core of the operating system, and business applications that implement upper-layer business logic.

[0071] The business domain management module is used to classify business applications by business attributes, categorize business applications into multiple different business domains, and build a corresponding independent container environment for each business domain. Each independent container is allocated a preset resource quota.

[0072] The host operating system environment is used to directly run basic applications that interact with the terminal hardware or the operating system kernel.

[0073] At least one independent container environment is deployed on top of the host operating system environment. Each independent container environment is allocated a preset resource quota to run one or more business applications belonging to the same business domain.

[0074] In this embodiment, the system also includes a remote management interface module, which is used to receive remote instructions and, based on the remote instructions, perform lifecycle management and resource quota configuration for each independent container environment.

[0075] It should be noted that the remote management interface module provides centralized operation and maintenance management capabilities for the intelligent converged terminal. This module establishes a connection with the cloud management platform or local operation and maintenance terminal through secure communication protocols (such as HTTPS, MQTT, etc.). Specifically, lifecycle management includes at least: completing the entire lifecycle operations of containers, such as creation, startup, stopping, restarting, and deletion, based on remote commands; resource quota configuration supports remote dynamic adjustment of key parameters such as the number of CPU cores, memory size, storage space, and network bandwidth of each container.

[0076] In this embodiment, each independent container environment includes a monitoring module for monitoring the business applications in each independent container environment for faults. When a fault is detected in any independent container, the faulty container is automatically isolated.

[0077] In this embodiment, each independent container environment includes an application management submodule, which is used to perform operations such as stopping the old version, deploying the new version, and restarting the business applications in each independent container environment.

[0078] For example, when an update is required for a single business application, the independent container environment in which the application resides is identified as the unique target domain for the operation. Throughout the update process, the basic application in the host operating system and other business application programs in other container environments continue to run unaffected due to their isolation characteristics.

[0079] Furthermore, the specific implementation of the above system is basically similar to the method implementation, so the description is relatively simple. For relevant details, please refer to the description of the method implementation. Moreover, it should be noted that in the various modules of the system of this application, the components are logically divided according to the functions they are to perform. However, this application is not limited to this and can re-divide or combine the components as needed.

[0080] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps described in the claims may be performed in a different order than those shown in the embodiments and still achieve the desired result. Furthermore, the specific order or sequential order shown in the drawings is not necessarily required to achieve the desired result; in some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0081] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A containerized deployment method for intelligent converged terminals, characterized in that, The method includes: Obtain the applications to be deployed and classify them by their functional attributes, dividing them into basic applications that directly interact with the terminal hardware or the core of the operating system, and business applications that implement upper-layer business logic. The basic application is deployed in the host operating system environment of the intelligent converged terminal; The business applications are classified by business attributes and categorized into multiple different business domains. A corresponding independent container environment is built for each business domain, wherein each independent container is allocated a preset resource quota. The business applications are deployed in separate container environments corresponding to the business domains they are classified into.

2. The containerized deployment method for intelligent converged terminals according to claim 1, characterized in that, The resource quotas include at least the memory usage limit and the CPU utilization limit.

3. The containerized deployment method for intelligent converged terminals according to claim 1, characterized in that, The basic applications include at least the application responsible for hardware interface management.

4. The containerized deployment method for intelligent converged terminals according to claim 1, characterized in that, The various business domains include the marketing business domain, the power distribution business domain, and the metering business domain.

5. The containerized deployment method for intelligent converged terminals according to claim 1, characterized in that, After deploying the business applications in independent container environments corresponding to their respective business domains, the method further includes: When a failure is detected in any independent container, the failed container is automatically isolated.

6. The containerized deployment method for intelligent converged terminals according to claim 1, characterized in that, The independent container supports elastic scaling, and can dynamically adjust the allocated resources according to the load of the business applications within the independent container.

7. A containerized deployment system for intelligent converged terminals, characterized in that, The system includes: The application acquisition and classification module is used to acquire applications to be deployed and classify them by functional attributes, dividing them into basic applications that directly interact with terminal hardware or the core of the operating system, and business applications that implement upper-layer business logic. The business domain management module is used to classify the business applications by business attributes, categorize the business applications into multiple different business domains, and build a corresponding independent container environment for each business domain, wherein each independent container is allocated a preset resource quota. The host operating system environment is used to directly run basic applications that interact with the terminal hardware or the operating system kernel. At least one independent container environment is deployed on top of the host operating system environment. Each independent container environment is allocated a preset resource quota for running one or more business applications belonging to the same business domain.

8. The containerized deployment method for intelligent converged terminals according to claim 1, characterized in that, The system also includes a remote management interface module, which is used to receive remote instructions and, based on the remote instructions, perform lifecycle management and resource quota configuration for each independent container environment.

9. The containerized deployment method for intelligent converged terminals according to claim 1, characterized in that, Each independent container environment includes a monitoring module for monitoring the business applications in each independent container environment for faults. When a fault is detected in any business application in an independent container, the faulty container is automatically isolated.

10. The containerized deployment method for intelligent converged terminals according to claim 1, characterized in that, Each independent container environment includes an application management submodule, which is used to perform operations such as stopping the old version, deploying the new version, and restarting the business applications in each independent container environment.

Images