Containerized intelligent proxy gateway dynamic management system, method and equipment and storage medium

Abstract

The invention discloses a containerized intelligent proxy gateway dynamic management system, method and device and a storage medium, the system integrates an intelligent routing function into a traffic scheduling module to form a decoupling type collaborative architecture of intelligent scheduling, deep analysis and multi-dimensional monitoring archiving, the technical contradiction that high-performance forwarding and deep analysis cannot be achieved at the same time is solved, and the system has a wide application prospect. And a dynamic rendering and script hot replacement mechanism is provided, so that the customization of system behaviors during operation is realized, the problem of rigid mirror image configuration of a static container is solved, enterprise-level resource isolation and process guarding capabilities are provided, the reliability of the system as a key infrastructure is guaranteed, and the system performance is improved. Through the asynchronous bypass monitoring archiving module, comprehensive monitoring of container states, performance indexes and user behaviors is achieved, specific protocols of all applications can be analyzed, user behavior data can be extracted and mapped to a unified interest label system, cross-application user portraits can be generated, and data support can be provided for commercial applications such as precision marketing and content recommendation.

Description

[0001] Technology Neighborhood This invention relates to the field of computer network communication and information security technology, and in particular to a containerized intelligent proxy gateway dynamic management system, method, device and storage medium. Background Technology

[0002] In modern network environments, proxy gateways are widely used for traffic forwarding, access control, security auditing, and performance optimization. Common proxy tools such as Clash (for rule-based traffic splitting) and mitmproxy (for debugging man-in-the-middle attacks and traffic analysis) are typically deployed and used independently. However, this separate deployment approach has several drawbacks: 1. Limited functionality and lack of synergy: A single proxy tool struggles to simultaneously achieve multiple functions such as efficient traffic splitting, deep packet analysis, intelligent DNS resolution, and real-time multi-dimensional behavior monitoring and reporting. Users need to build complex environments to implement these functions, resulting in high deployment and maintenance costs.

[0003] 2. Limited monitoring dimensions: Lack of comprehensive monitoring of container running status, performance indicators, and user cross-application behavior characteristics.

[0004] 3. Complex configuration and difficult management: The configurations of each component are independent, making unified management and dynamic configuration difficult. Updating configurations or rules requires manual intervention, resulting in low automation and a high risk of errors.

[0005] 4. Rigid resource configuration: Traditional containerized deployments use fixed resource limits, which cannot be dynamically adjusted according to real-time load, resulting in low resource utilization or performance degradation under high load.

[0006] 5. Rigid DNS resolution: Using a fixed DNS server makes it impossible to dynamically select the optimal DNS based on the geographical location of the outbound IP, resulting in problems such as degraded resolution performance and inaccessibility of geographically restricted content when accessing cross-border networks.

[0007] 6. Poor portability and consistency: The environment is complex and it is difficult to ensure the consistency of the environment when deployed on different machines or platforms, which can easily lead to the problem of "it can run on my machine". Summary of the Invention

[0008] The purpose of this invention is to address the technical problems existing in the background art by proposing a containerized intelligent proxy gateway dynamic management system, method, device, and storage medium.

[0009] To achieve the above-mentioned technical objectives, the technical solution adopted by the present invention is as follows: The first aspect of this invention provides a containerized intelligent proxy gateway dynamic management system, including a traffic scheduling module, a traffic analysis module, an asynchronous bypass archiving module, a process guardian management module, and a dynamic unified configuration management module. The traffic scheduling module receives traffic from an external network and performs routing decisions, distribution, and dynamic configuration of corresponding DNS resolution servers based on a pre-configured rule set. The traffic analysis module is connected to the traffic scheduling module and receives the distributed traffic, performs application layer protocol parsing, content recording, and forwarding. The asynchronous bypass archiving module is connected to the traffic analysis module and asynchronously monitors and collects the output information of the traffic analysis module from multiple dimensions, reporting the output information to a pre-configured remote storage server. The process guardian management module manages the traffic scheduling module, traffic analysis module, and process unified configuration management module. The system monitors and manages the lifecycle of the block and asynchronous bypass archiving modules, and dynamically adjusts container resource limits based on real-time performance metrics. The dynamic unified configuration management module is connected to the process guardian management module. The dynamic unified configuration management module includes a configuration template dynamic rendering unit and a startup script hot replacement unit. The configuration template dynamic rendering unit is used to replace variables in the pre-set configuration template file according to the received external dynamic parameters during the system startup phase, and generate the running configuration files of each module. The startup script hot replacement unit is used to detect and load externally provided custom scripts during the system initialization phase, and replace the pre-set default service startup scripts in the system with custom scripts. The modules are the process guardian management module, traffic scheduling module, traffic analysis module, and asynchronous bypass archiving module.

[0010] Optionally, the traffic scheduling module also integrates an intelligent DNS routing function, which dynamically selects the appropriate DNS resolution server based on the geographical location information of the outbound proxy IP.

[0011] Optionally, the asynchronous bypass archiving module collects the output information of the traffic analysis module from three dimensions. These three dimensions include container status information, performance metrics, and comprehensive behavioral data. Container status information is the basic information of the container's operating environment, performance metrics are the performance data of the system during operation, and comprehensive behavioral data are the behavioral characteristics of users in various applications within the traffic.

[0012] Optionally, the asynchronous bypass archiving module also includes a user profile generation unit. This unit maps application-specific content tags to a unified predefined interest tag system, generating a comprehensive user interest profile across applications. Optionally, the process daemon management module calculates container resource limits based on a non-linear response function.

[0013] A second aspect of the present invention provides a dynamic management method for a containerized intelligent proxy gateway, applied to a dynamic management system for a containerized intelligent proxy gateway as described in any of the above solutions. The dynamic management method for the containerized intelligent proxy gateway includes: Integrate all modules into the same container image; The external storage volume is mounted to a predetermined path inside the container, and dynamic environment parameters are injected into the container. The external storage volume contains a custom configuration template and / or a custom startup script. By using the hot-swap unit for startup scripts, a custom configuration template or a custom startup script can be loaded and enabled. By configuring template dynamic rendering units and combining them with dynamic environment parameters, the runtime configuration files of each module are generated through rendering. Based on the corresponding runtime configuration file, the traffic scheduling module receives traffic from the external network and performs routing decisions, distribution, and dynamic configuration of the corresponding DNS resolution server according to the pre-configured rule set. The traffic analysis module performs application layer protocol parsing, content recording, and forwarding on the distributed traffic. The asynchronous bypass archiving module monitors the output of the traffic analysis module and is used for asynchronous monitoring and multi-dimensional collection of the output information of the traffic analysis module, and reports the output information to the pre-configured remote storage server. The process daemon manages and monitors each module, and periodically collects CPU utilization metrics to dynamically adjust container resource limits.

[0014] A first implementation of the third aspect of the present invention provides a containerized intelligent proxy gateway dynamic management device, the containerized intelligent proxy gateway dynamic management device comprising: a memory and at least one processor, wherein the memory stores instructions, and the memory and the at least one processor are interconnected via a line; The at least one processor invokes the instructions in the memory to cause the containerized smart proxy gateway dynamic management device to execute the containerized smart proxy gateway dynamic management system as described in any one of the first aspects of the present invention.

[0015] A first implementation of the fourth aspect of the present invention provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the containerized intelligent proxy gateway dynamic management system as described in any one of the first aspects of the present invention.

[0016] Compared with existing technologies, this invention offers the following beneficial technical effects: By integrating intelligent routing functionality into the traffic scheduling module, a decoupled collaborative architecture of intelligent scheduling, deep analysis, and multi-dimensional monitoring and archiving is formed. This resolves the technical contradiction between high-performance forwarding and deep analysis. Furthermore, the proposed dynamic rendering and script hot-replacement mechanism enables runtime customization of system behavior, solves the problem of rigid static container image configuration, provides enterprise-level resource isolation and process protection capabilities, and ensures the reliability of the system as a critical infrastructure. The asynchronous bypass monitoring and archiving module enables comprehensive monitoring of container status, performance indicators, and user behavior, providing richer data insights. It can parse application-specific protocols, extract user behavior data, and map it to a unified interest tag system to generate cross-application user profiles. The generated user interest profiles can provide data support for commercial applications such as precision marketing and content recommendation. Attached Figure Description

[0017] Figure 1 This is a schematic diagram of the containerized intelligent proxy gateway dynamic management system in an embodiment of the present invention; Figure 2 This is a schematic diagram illustrating the usage process of the containerized intelligent proxy gateway dynamic management system in an embodiment of the present invention; Figure 3 This is a schematic diagram of one embodiment of the containerized intelligent proxy gateway dynamic management device in this invention.

[0018] Icon labels: 100 Traffic scheduling module, 200 Traffic analysis module, 300 Asynchronous bypass archiving module, 301 User profile generation unit, 400 Process guardian management module, 500 Dynamic unified configuration management module, 501 Template dynamic rendering unit, 502 Startup script hot replacement unit. Detailed Implementation

[0019] It should be noted that, unless otherwise specified, the embodiments and features described in the present invention can be combined with each other.

[0020] For ease of understanding, the specific process of the embodiments of the present invention is described below. Please refer to [link / reference]. Figure 1 - Appendix Figure 2 The containerized intelligent proxy gateway dynamic management system in this embodiment of the invention includes: Traffic scheduling module 100, traffic analysis module 200, asynchronous bypass archiving module 300, process guardian management module 400, and dynamic unified configuration management module 500; The traffic scheduling module 100 receives traffic from the external network and performs routing decisions, distribution, and dynamic configuration of corresponding DNS resolution servers based on a pre-configured rule set. A preferred implementation utilizes the open-source Clash software for enhanced functionality, integrating the GEOIP database and dynamic DNS selection algorithm. Its pre-configured configuration template file is in YAML format and includes placeholders for environment variable substitution. It should be noted that the traffic originates from the external network, which means requests initiated by users, client applications, or other services on the Internet (such as HTTP / HTTPS requests, API calls, DNS queries, etc.). After the traffic scheduling module 100 receives this traffic, it processes different types of traffic according to a set of decision logic, i.e., rule sets, predefined by the administrator, and distributes them to the specified backend service clusters or resource pools, such as application server groups, server rooms, or data centers. This achieves intelligent traffic routing, load balancing, and service differentiation, ensuring that user requests are efficiently and reasonably directed to the correct backend resources.

[0021] By dynamically selecting the optimal DNS resolution server based on the geographical location information of the traffic exit proxy IP, users in different geographical locations are guided to the network node with the fastest response and best access quality for them through DNS queries, realizing the core capability of global intelligent traffic management. It dynamically decides and returns the most suitable server IP address by sensing the user's location in real time and combining it with preset business rules. This not only significantly improves the access speed and experience for end users, but also provides strong technical support for high availability, compliance, and cost control of services.

[0022] Traffic analysis module 200 is connected to traffic scheduling module 100 and is used to receive distributed traffic, perform application layer protocol parsing, content recording, and forwarding of the traffic. Asynchronous bypass archiving module 300 is connected to traffic analysis module 200 and is used for asynchronous monitoring and multi-dimensional collection of output information from traffic analysis module 200, and reports the output information to a pre-configured remote storage server. Preferably, this is implemented using the open-source mitmproxy software. Its configuration is injected through startup command parameters and environment variables. It should be noted that the traffic analysis module 200 no longer stays at the IP / TCP / UDP level, but delves into application layer protocols such as HTTP, DNS, MQTT, and gRPC to understand the specific business meaning of traffic. According to the configuration, it extracts and records the key information parsed, such as request parameters, response status codes, and user tokens. The parsed traffic is then forwarded to the actual backend business server. In addition to traffic forwarding, it also generates output information, namely the parsing results and the recorded content. The asynchronous bypass archiving module 300 is responsible for independent, non-intrusive data acquisition and persistence. It asynchronously listens to and collects the output information generated by the traffic analysis module 200. The asynchronous bypass archiving module 300 is decoupled from the traffic analysis module 200. After the traffic analysis module 200 completes forwarding, it can directly transmit the data to the asynchronous bypass archiving module 300 without waiting for the asynchronous bypass archiving module 300 to complete processing. This will not affect the forwarding performance of the traffic analysis module 200. It should be noted that the multi-dimensional acquisition used by the asynchronous bypass archiving module 300 can be content dimension, performance dimension, security dimension, session dimension, etc. Finally, the collected and processed information is reported to a pre-configured remote storage server for long-term storage, auditing, and analysis.

[0023] The process guardian management module 400 is used to monitor the lifecycle of the processes of the traffic scheduling module 100, the traffic analysis module 200, and the asynchronous bypass archiving module 300, and to dynamically adjust the limits of container resources based on real-time performance indicators. It should be noted that lifecycle monitoring refers to monitoring the liveness and health status of containers. Liveness status refers to whether the monitored process exists and is running. If the process crashes or becomes unresponsive, it will be detected and reported immediately. Health status refers to whether the monitored process is healthy. A process may be running, but it may not be able to work properly due to deadlock, resource exhaustion, or unavailability of dependent services. The process guardian management module 400 will determine this through heartbeat detection or by calling the health check interfaces built into each module, ensuring that every component of the system is in a live state, providing a foundation for subsequent management and protection.

[0024] Guardian management refers to automatically taking measures to repair and manage when monitoring detects problems, thereby enabling the system to have self-healing capabilities and reducing human intervention.

[0025] If a module, such as the traffic analysis module 200, is detected to have crashed or abnormally exited, the process guardian management module 400 will immediately and automatically restart a new process / container instance to restore service. In a high-availability deployment, if the primary instance fails, it can trigger a standby instance to take over the service. When a serious problem occurs that cannot be automatically recovered, such as consecutive restart failures, an alarm is triggered to notify operations and maintenance personnel to intervene, greatly improving the system's availability and robustness. Even when a single component fails, the entire system can quickly self-repair, ensuring business continuity.

[0026] The dynamic unified configuration management module 500 is connected to the process guardian management module 400. The dynamic unified configuration management module 500 includes a configuration template dynamic rendering unit 501 and a startup script hot replacement unit 502. The configuration template dynamic rendering unit 501 is used to perform variable replacement on the preset configuration template file according to the received external dynamic parameters during the system startup phase, and generate the running configuration file of each module. The startup script hot replacement unit 502 is used to detect and load the custom script provided by the outside during the system initialization phase, and replace the default service startup script preset in the system with the custom script. The modules are the process guardian management module 400, the traffic scheduling module 100, the traffic analysis module 200, and the asynchronous bypass archiving module 300.

[0027] It should be noted that a preferred implementation of the configuration template dynamic rendering unit is through the envsubst command in the Linux system. This command can replace environment variable values ​​in the template file. A preferred implementation of the startup script hot-swap unit is to write logic in the container initialization script (such as 01-config-setup) to check whether a custom script file with a specific name (such as clash.run) exists in the mounted volume (such as the / config directory). If it exists, it is copied and overwritten to the s6-overlay service directory (such as / etc / services.d / clash / run).

[0028] In one embodiment of this application, the traffic scheduling module 100 also integrates an intelligent DNS routing function, which dynamically selects an appropriate DNS resolution server based on the geographical location information of the outbound proxy IP.

[0029] In one embodiment of this application, the asynchronous bypass archiving module 300 collects the output information of the traffic analysis module 200 from three dimensions, namely, container status information, performance indicators, and comprehensive behavioral data. The container status information is the basic information of the container running environment, the performance indicators are the performance data of the system running, and the comprehensive behavioral data are the behavioral characteristics of users in each application in the traffic.

[0030] In one embodiment of this application, the asynchronous bypass archiving module 300 further includes a user profile generation unit 301, which is used to map the content tags unique to each application to a unified predefined interest tag system to generate a comprehensive user interest profile across applications.

[0031] In one embodiment of this application, the process guardian management module 400 calculates the container resource limits based on a nonlinear response function.

[0032] It should be noted that by periodically collecting CPU usage (C_usage), calculating the target CPU limit based on a non-linear response function, and dynamically updating the container's CPU limit, the CPU_limit is kept within the range of 0.1 to 1.5 to prevent over-adjustment. The non-linear response function is as follows: CPU_limit = 0.8+0.7 [tanh(2×(C_usage - 0.7)) + 0.3×(C_usage - 0.7)³]; Based on the following considerations: 1. Baseline value 0.8: Provides stable resource availability under moderate load; 2. tanh function: Provides a smooth transition near the critical point (C_usage=0.7), avoiding resource fluctuations; 3. Cubic terms: Provide stronger response under extreme loads, ensuring system stability; 4. Scaling factor 0.7: Controls the adjustment range and avoids over-response; This function has the following characteristic: When C_usage > 0.9, CPU_limit quickly approaches the upper limit of 1.5.

[0033] As attached Figure 1 The system workflow in this embodiment is as follows: 1. The user equipment sets the proxy to the address and port of this system instance.

[0034] 2. Traffic first enters the traffic scheduling module 100 (Clash). Clash determines whether the traffic is directly connected or forwarded based on the rule configuration (such as GEOIP, CN, DIRECT).

[0035] 3. Traffic that is determined to be forwarded is sent to the traffic analysis module 200 (mitmproxy). mitmproxy decrypts and analyzes the traffic in detail, logs the data, and forwards the traffic to the final upstream proxy server.

[0036] 4. The asynchronous bypass archiving module 300 collects container status information and performance metrics, and continuously monitors mitmproxy's log files. It extracts URL access records in real time, parses the unique API protocol formats for different applications, extracts user behavior features from the protocol data (browsed products, watched videos, searched keywords, etc.), maps application-specific content tags to a unified predefined interest tag system (e.g., mapping "food tutorials" on Douyin to "cooking interests"), and generates user interest profiles based on time-series behavioral data, including the following dimensions (interest tag weight distribution, behavioral time pattern analysis, cross-application interest consistency score, interest evolution trend analysis), and constructs them into JSON format to report to the remote API via an HTTP POST request.

[0037] The container runtime environment uses the Docker container engine, the process guardian management module 400 uses the s6-overlay framework, s6-overlay monitors the processes of the above three services to ensure their continuous operation, the intelligent resource scheduling unit periodically obtains the CPU utilization, calculates the target CPU limit based on the non-linear function, and dynamically adjusts the resource limit through the container engine API.

[0038] As attached Figure 2 The dynamic deployment process in this embodiment is as follows: 1. Users prepare a custom configuration template (such as clash-custom.config.yaml.template) and a custom script (such as my-startup.run), and place them in a directory on the host machine (such as / home / user / configs).

[0039] 2. The user executes the Docker run command; The command is as follows: docker run -d \ -v / home / user / configs: / config:ro # Mount custom configurations and scripts -e UPSTREAM_PROTOCOL=http # Inject dynamic environment variables -e API_URL=https: / / api.example.com \ --name my-proxy-gateway \ proxy-gateway-image:tag 3. When the container starts, before s6-overlay starts, the initialization script runs. The startup script hot-swap unit 502 checks the / config directory, finds the my-startup.run file, and then copies it to overwrite the default script.

[0040] 4. Subsequently, before the service starts, configure the template dynamic rendering unit 501 (via the envsubst command) to read the environment variables, replace ${UPSTREAM_PROTOCOL} with http, and generate the final Clash configuration file.

[0041] 5. The system ultimately runs using user-defined scripts and rendered configurations.

[0042] This system integrates intelligent DNS routing functionality into the traffic scheduling module, forming a decoupled collaborative architecture of "intelligent scheduling - deep analysis - multi-dimensional monitoring and archiving," resolving the technical contradiction of the incompatibility between high-performance forwarding and deep analysis. The proposed dynamic rendering and script hot-swap mechanism enables runtime customization of system behavior, solving the industry problem of rigid static container image configuration. It provides enterprise-level resource isolation and process protection capabilities, ensuring the reliability of the system as critical infrastructure. The built-in asynchronous bypass archiving mechanism provides an out-of-the-box automated data pipeline for network behavior auditing. The asynchronous bypass monitoring and archiving module enables comprehensive monitoring of container status, performance indicators, and user behavior, providing richer data insights. It can parse application-specific protocols, extract user behavior data, and map it to a unified interest tag system to generate cross-application user profiles. The generated user interest profiles can provide data support for commercial applications such as precision marketing and content recommendation. By dynamically adjusting CPU resource limits through a non-linear response function, it improves resource utilization while ensuring performance stability.

[0043] The containerized intelligent proxy gateway dynamic management system in this embodiment of the invention has been described above. The containerized intelligent proxy gateway dynamic management method in this embodiment of the invention is described below. Please refer to [link / reference]. Figure 2 The containerized intelligent proxy gateway dynamic management method includes: Integrate all modules into the same container image; The external storage volume is mounted to a predetermined path inside the container, and dynamic environment parameters are injected into the container. The external storage volume contains a custom configuration template and / or a custom startup script. The custom configuration template or custom startup script is loaded and enabled via the startup script hot-swap unit 502. By configuring the template dynamic rendering unit 501 and combining it with dynamic environment parameters, the runtime configuration files of each module are generated through rendering. Based on the corresponding runtime configuration file, the traffic scheduling module 100 receives traffic from the external network and performs routing decisions, distribution, and dynamic configuration of the corresponding DNS resolution server according to the pre-configured rule set. The traffic analysis module 200 performs application layer protocol parsing, content recording, and forwarding on the distributed traffic. The asynchronous bypass archiving module 300 monitors the output of the traffic analysis module 200 and is used for asynchronous monitoring and multi-dimensional collection of the output information of the traffic analysis module 200, and reports the output information to the preset remote storage server. The process management module 400 monitors each module and periodically collects CPU utilization metrics to dynamically adjust container resource limits.

[0044] This method integrates intelligent DNS routing functionality into the traffic scheduling module, forming a decoupled collaborative architecture of "intelligent scheduling - deep analysis - multi-dimensional monitoring and archiving," thus resolving the technical contradiction that high-performance forwarding and deep analysis cannot be achieved simultaneously. The proposed dynamic rendering and script hot-swap mechanism enables runtime customization of system behavior and solves the industry problem of rigid static container image configuration. It provides enterprise-grade resource isolation and process protection capabilities, ensuring the reliability of the system as a critical infrastructure; the built-in asynchronous bypass archiving mechanism provides an out-of-the-box automated data pipeline for network behavior auditing. The asynchronous bypass monitoring and archiving module enables comprehensive monitoring of container status, performance metrics, and user behavior, providing richer data insights. It can parse application-specific protocols, extract user behavior data, and map it to a unified interest tagging system to generate cross-application user profiles. These generated user interest profiles can provide data support for commercial applications such as precision marketing and content recommendation. Furthermore, by dynamically adjusting CPU resource limits through a non-linear response function, it improves resource utilization while ensuring stable performance.

[0045] The containerized intelligent proxy gateway dynamic management system in this embodiment of the invention is described in detail from the perspective of unitized functional entities. The containerized intelligent proxy gateway dynamic management device in this embodiment of the invention is described in detail from the perspective of hardware processing.

[0046] Figure 3This is a schematic diagram of the structure of a containerized intelligent proxy gateway dynamic management device provided in an embodiment of the present invention. This containerized intelligent proxy gateway dynamic management device can vary significantly due to different configurations or performance. It may include one or more central processing units (CPUs) 310 (e.g., one or more processors) and a memory 320, and one or more storage media 330 (e.g., one or more mass storage devices) for storing applications 333 or data 332. The memory 320 and storage media 330 can be temporary or persistent storage. The program stored in the storage media 330 may include one or more units (not shown in the diagram), each unit may include a series of instruction operations on the containerized intelligent proxy gateway dynamic management device. Furthermore, the processor 310 may be configured to communicate with the storage media 330 and execute the series of instruction operations in the storage media 330 on the containerized intelligent proxy gateway dynamic management device.

[0047] The containerized intelligent agent gateway-based dynamic management device may also include one or more power supplies 340, one or more wired or wireless network interfaces 350, one or more input / output interfaces 360, and / or one or more operating systems 331, such as Windows Server, Mac OS X, Unix, Linux, FreeBSD, etc. Those skilled in the art will understand that... Figure 3 The containerized intelligent proxy gateway dynamic management device structure shown does not constitute a limitation on communication protocol devices based on LAN projection. It may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0048] The present invention also provides a computer-readable storage medium, which can be a non-volatile computer-readable storage medium or a volatile computer-readable storage medium, wherein the computer-readable storage medium stores instructions that, when the instructions are executed on a computer, cause the computer to perform the steps of the containerized intelligent proxy gateway dynamic management system.

[0049] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0050] The above describes a containerized intelligent proxy gateway dynamic management system or various implementation methods in conjunction with specific content, and does not imply that the specific implementation of the present invention is limited to these descriptions. Any methods or structures that are similar to or identical to those of the present invention, or any technical deductions or substitutions made under the premise of the present invention, should be considered within the scope of protection of the present invention.

Claims

1. A containerized intelligent proxy gateway dynamic management system, characterized in that, include: The traffic scheduling module is used to receive traffic from external networks and make routing decisions, distribute traffic, and dynamically configure corresponding DNS resolution servers according to a pre-configured rule set. The traffic analysis module is connected to the traffic scheduling module and is used to receive distributed traffic, perform application layer protocol parsing, content recording and forwarding of the traffic; An asynchronous bypass archiving module is connected to the traffic analysis module and is used for asynchronous monitoring and collecting the output information of the traffic analysis module from multiple dimensions, and reporting the output information to a preset remote storage server; The process protection and management module is used to monitor and protect the processes of the traffic scheduling module, the traffic analysis module, and the asynchronous bypass archiving module, and to dynamically adjust the limits of container resources based on real-time performance indicators. A dynamic unified configuration management module is connected to the process guardian management module. The dynamic unified configuration management module includes a configuration template dynamic rendering unit and a startup script hot-replacement unit. The configuration template dynamic rendering unit is used to perform variable replacement on the preset configuration template file according to the received external dynamic parameters during the system startup phase to generate the running configuration files of each module. The startup script hot-replacement unit is used to detect and load the externally provided custom script during the system initialization phase and replace the preset default service startup script in the system with the custom script. The modules are the process guardian management module, the traffic scheduling module, the traffic analysis module, and the asynchronous bypass archiving module.

2. The containerized intelligent proxy gateway dynamic management system according to claim 1, characterized in that, The traffic scheduling module also integrates an intelligent DNS routing function, which dynamically selects the appropriate DNS resolution server based on the geographical location information of the outbound proxy IP.

3. The containerized intelligent proxy gateway dynamic management system according to claim 2, characterized in that, The asynchronous bypass archiving module collects the output information of the traffic analysis module from three dimensions, namely, container status information, performance indicators, and comprehensive behavioral data. The container status information is the basic information of the container's operating environment, the performance indicators are the performance data of the system during operation, and the comprehensive behavioral data are the behavioral characteristics of users in various applications within the traffic.

4. The containerized intelligent proxy gateway dynamic management system according to claim 3, characterized in that, The asynchronous bypass archiving module also includes a user profile generation unit, which maps application-specific content tags to a unified predefined interest tag system to generate a comprehensive user interest profile across applications.

5. The containerized intelligent proxy gateway dynamic management system according to claim 4, characterized in that, The process guardian management module calculates container resource limits based on a non-linear response function.

6. A dynamic management method for a containerized intelligent proxy gateway, characterized in that, Applied to a containerized intelligent proxy gateway dynamic management system as described in any one of claims 1-5, the containerized intelligent proxy gateway dynamic management method includes: Integrate all modules into the same container image; An external storage volume is mounted to a predetermined path within the container, and dynamic environment parameters are injected into the container. The external storage volume contains a custom configuration template and / or a custom startup script. The custom configuration template or the custom startup script is loaded and enabled through the startup script hot-swap unit; The configuration template dynamic rendering unit, combined with the dynamic environment parameters, is used to render and generate the runtime configuration files for each module; Based on the corresponding running configuration file, the traffic scheduling module receives traffic from the external network and performs routing decisions, distribution, and dynamic configuration of the corresponding DNS resolution server for the traffic according to the pre-configured rule set. The traffic analysis module performs application layer protocol parsing, content recording, and forwarding on the distributed traffic. The asynchronous bypass archiving module monitors the output of the traffic analysis module and is used for asynchronous monitoring and multi-dimensional collection of the output information of the traffic analysis module, and reports the output information to a preset remote storage server. The process guardian management module monitors each module and periodically collects CPU utilization metrics to dynamically adjust container resource limits.

7. A containerized intelligent proxy gateway dynamic management device, characterized in that, The containerized intelligent proxy gateway dynamic management device includes: a memory and at least one processor, wherein the memory stores instructions, and the memory and the at least one processor are interconnected via a line; The at least one processor invokes the instructions in the memory to cause the containerized smart proxy gateway dynamic management device to execute the containerized smart proxy gateway dynamic management method as described in claim 6.

8. A computer-readable storage medium storing a computer program thereon, characterized in that, When the computer program is executed by the processor, it implements the containerized intelligent proxy gateway dynamic management method as described in claim 6.

Images