Communication link dynamic management and control method and system based on protocol driving pool

Abstract

The invention relates to a communication link dynamic management and control method and system based on a protocol driving pool, and the method comprises the steps: monitoring a network port to capture a suspected link access data packet, and extracting key information; screening legal new links based on the key information; extracting features of a legal new link and standardizing the features, matching belonging groups based on a multi-level grouping rule, calling an adaptive protocol driver from a protocol driver pool and completing binding; according to the service scene and the driving capability of the group to which the link belongs, adding the task into a scheduling queue and verifying the binding validity with the link; analyzing the periodic task information, screening a communication interface, generating and optimizing an issuing instruction, sending the issuing instruction to link equipment through the interface, and monitoring an execution result; real-time data of a multi-network environment and links are collected, optimization parameters are generated through fusion calculation, and global optimization of link communication is achieved. According to the invention, link dynamic access verification can be realized, protocol driving is accurately matched, tasks and interfaces are configured as required, and network parameters are globally optimized.

Description

Technical Field

[0001] This invention relates to the field of network communication technology, and specifically to a method and system for dynamic management and control of communication links based on a protocol-driven pool. Background Technology

[0002] In power control scenarios, communication links carry critical services such as data interaction between substations and dispatch centers, grid-connected monitoring of distributed energy resources, and status feedback from distribution network terminals, placing stringent requirements on latency, stability, and security. However, traditional communication link management methods have significant limitations.

[0003] Traditional methods rely on static rules or simple threshold judgments, resulting in significant adaptation deficiencies: link access is filtered solely by fixed ports or protocol types, failing to consider the periodic characteristics of power services and encrypted data packet identifiers, easily leading to unauthorized access or accidental disconnection of critical links; protocol-driven and fixed link binding ignores the differences in services across different substations, causing delays or resource waste in high-priority links; task scheduling and interface allocation lack scenario adaptability, such as real-time adjustment commands sharing interfaces with regular tasks during wind power grid connection, leading to command delays due to congestion and affecting grid stability. Furthermore, existing methods often focus on a single objective, neglecting resource utilization optimization; weight settings in multi-objective scheduling lack dynamic adjustment; and strategies are not designed for differentiated power system scenarios, making it difficult to adapt to dynamic changes in network topology, service types, and interference environments, easily causing link congestion and disconnections, threatening the safe operation of the power system.

[0004] In summary, existing technologies have significant shortcomings in terms of link access accuracy, protocol-driven adaptation efficiency, and dynamic management capabilities across multiple scenarios. In particular, in power control scenarios, they struggle to meet the demands for high real-time performance and high reliability in communication. There is an urgent need for a communication link management method that can integrate multi-dimensional link characteristics, dynamically match resources, and adapt to complex scenarios. This method would address challenges such as poor link stability, low resource utilization, and weak scenario adaptability in multi-network converged environments, thereby providing communication support for the safe and efficient operation of power systems. Summary of the Invention

[0005] The purpose of this invention is to provide a method and system for dynamic management and control of communication links based on a protocol driver pool, so as to solve the problems of low access detection accuracy, poor protocol driver adaptation, rigid task scheduling, and insufficient multi-network optimization in existing communication link management and control, and realize dynamic access verification of links, accurate matching of protocol drivers, on-demand configuration of tasks and interfaces, and global optimization of network parameters.

[0006] To achieve the above objectives, the technical solution adopted by this invention is: a method for dynamic management and control of communication links based on a protocol-driven pool, comprising: 1) Link access detection: Monitor network ports to capture data packets suspected of link access, extract key information, and trigger new link judgment process; 2) New Link Access Judgment: Receive the key information, verify the legality of the link and determine its novelty, and filter out legal new links; 3) Group matching and protocol driver pool invocation: Extract the features of the legal new link and standardize them, match the group to which it belongs based on multi-level grouping rules, and call the appropriate protocol driver from the protocol driver pool to complete the binding; 4) Periodic task loading: Define periodic tasks and configure parameters according to the business scenario and driving capabilities of the group to which the link belongs, add the tasks to the scheduling queue and verify the binding validity with the link; 5) Communication interface delivery processing: Parse the periodic task information, select suitable communication interfaces, generate and optimize the delivery instructions, send them to the link device through the interface, and monitor the execution results; 6) Multi-network fusion computing: Collect real-time data from multiple network environments and links, generate optimization parameters through fusion computing, and achieve global optimization of link communication.

[0007] Further, in step 1), the link access detection includes: Listening initialization: Start the network listening service, configure the network port to listen on, and set the network protocol type to listen on; initialize the listening buffer to temporarily store the received link access related data; Real-time data capture: Receive data packets from the network using network sockets; when a data packet arrives at the listening port, read the header information of the data packet to make a preliminary judgment on whether it is a data packet related to link access; if it is preliminarily judged to be a possible link access data packet, extract key information from the data packet, including source IP address, source port number and link type identifier, and temporarily store this key information in a temporary data structure; Triggering judgment mechanism: When a data packet that meets the conditions is captured, or when continuous suspected link access data traffic is detected within a set time period, the new link access judgment process is triggered, and the temporarily stored link access related information is passed to the new link access judgment module for new link access judgment.

[0008] Furthermore, in step 2), the verification of the link's legality includes identity authentication verification and access parameter verification; The identity authentication verification process involves querying a pre-stored database of legitimate link identity information to verify the link's identity; the database of legitimate link identity information contains a whitelist of legitimate links' IP addresses and key information. The access parameter verification is as follows: verifying whether the parameters of the link access meet the system requirements, including: verifying whether the protocol version matches the version supported by the system, and verifying whether the expected communication bandwidth and delay parameters of the link are within the range that the system can bear. The determination of link novelty includes: comparing the link's unique identifier with the system record; if no identical identifier exists, it is determined to be a new link; if an identical identifier exists, it is determined to be a reconnection, and the system policy decides whether to process it as a new link. Based on the results of link legitimacy verification and link novelty judgment, a judgment conclusion is generated. If it is determined to be a new legitimate link, the link's detailed information is passed to the packet matching and protocol driver pool invocation module for packet matching and protocol driver pool invocation. If it is determined to be a non-new link or an illegal link, feedback is given to the link access detection module so that it can continue to perform link access detection.

[0009] Furthermore, in step 3), the multi-level grouping rules adopt a three-level classification architecture: Primary classification: Classified by protocol type; the protocol types include TCP Link Group, UDP Link Group, and IoT Protocol Group; Secondary classification: divided by business scenario; the business scenarios include industrial control link group, power grid monitoring link group and video transmission link group; Third-level classification: Classified by performance requirements, which include low-latency link groups and high-reliability link groups.

[0010] Further, in step 3), the protocol driver pool includes: Driver storage unit: Stores drivers according to protocol type, including initialization interface, data encoding / decoding interface and link status monitoring interface; Driver Index Table: Establish a multi-dimensional index of "protocol type-packet identifier-driver version-performance parameters"; Driver status management unit: records driver load rate, running status and version information in real time.

[0011] Further, in step 4), the periodic task loading includes: Task Requirements Analysis: Receive the "protocol type-group identifier-driver version-performance parameters" information passed by the packet matching and protocol driver pool call module; combine the typical business scenarios of the group to which the link belongs, and the task interface capabilities provided by the driver, to analyze the types of periodic tasks that the link needs to execute; Periodic task definition and parameter configuration: Based on the analysis results, select a suitable task template from the system's predefined periodic task template library; then configure the parameters of the selected task template based on the link parameters and driving capabilities. Task scheduling queue management: First, initialize the task scheduling queue, then insert the configured periodic tasks into the corresponding task scheduling queue according to their priority and type, and then set scheduling parameters including execution cycle and first execution delay for each enqueued task; Task and Link Binding Verification: Call the task binding interface provided by the driver to bind the configured periodic task with the corresponding link; then send a test task command to verify whether the task can be triggered and executed correctly. Task loading result feedback: If the task loading and verification are successful, the task scheduling queue information and the task-link binding relationship information are passed to the communication interface delivery processing module so that subsequent modules can generate communication interface delivery instructions based on this information; if the task loading fails, the reason for the failure is recorded and fed back to the group matching and protocol driver pool calling module so that the upstream module can adjust the driver call or link group operation.

[0012] Further, in step 5), the communication interface distribution process includes: Task information reception and parsing: Receives task scheduling queue information and task-link binding relationship data transmitted by the periodic task loading module, and parses this information to extract key content, including task type, execution cycle, link identifier, corresponding protocol driver information, task priority, and specific task parameters; Communication interface filtering and adaptation: Based on the link identifier and protocol driver information, query the communication interface resource library in the system; filter out the communication interfaces that match the current link and task. The filtering principles include: the interface type is compatible with the protocol driver, the current load rate of the interface is lower than the set threshold to ensure the task execution efficiency, and the transmission performance of the interface meets the real-time requirements of the task; if there are multiple adapted interfaces, sort them according to task priority and interface performance, and select the optimal interface. Command generation: Based on the parsed task information and the selected communication interface attributes, generate specific communication interface command generation. Instruction optimization and encapsulation: The generated instructions are optimized; for periodically repetitive instructions, instruction compression technology is used to reduce the amount of data during transmission; for instructions of high-priority tasks, priority markers are added to ensure that the interface processes them first during transmission; then, the instructions are encapsulated according to the frame format requirements of the communication interface. Interface delivery and transmission monitoring: Through the selected communication interface, the encapsulated delivery command is sent to the corresponding device or module of the link; during the transmission process, the transmission monitoring mechanism is activated to monitor the delivery status of the command in real time; if the command delivery fails, it is retried according to the preset retry strategy; if it still fails after multiple retries, the failure information is recorded and the alarm mechanism is triggered. Result verification and feedback: Receive instruction execution response information returned by the link device or module; parse the response information to determine whether the instruction was successfully executed; if the instruction was successfully executed, pass the result to the multi-network fusion computing module and update the execution status of the task in the task scheduling queue; if the instruction failed to execute, analyze the reason for the failure and feed back the failure information to the periodic task loading module so that the task parameters can be readjusted or the communication interface can be changed.

[0013] Further, in step 6), the multi-network fusion computation includes: Real-time data acquisition and standardization: Acquire real-time operational data from multiple networks and links, and after filtering and standardization, provide basic data in a unified format for subsequent evaluation and optimization; Network and link status assessment and bottleneck identification: Based on standardized data, assess the current status of the network and links, and locate key bottlenecks affecting communication quality according to preset rules; Optimize strategy generation and rule matching: For the identified bottleneck type, match the optimal strategy from the preset strategy library and refine it into executable operation directions; Optimize parameter generation and validity verification: Transform refined strategies into configurable parameters, and ensure the feasibility and security of parameters through multi-dimensional verification; Optimization parameter distribution and effect verification: Distribute the verified parameters to the corresponding modules for execution, monitor and verify the optimization effect, and form a closed-loop control.

[0014] Furthermore, in step 6), the optimization parameters are sent to the associated modules according to their type: link migration and channel parameters are sent to the packet matching and protocol driver pool calling module, and bandwidth limitation and priority parameters are sent to the communication interface sending and processing module, and a "command + confirmation" mechanism is used to ensure reception.

[0015] The present invention also provides a communication link dynamic management and control system for implementing the above method, comprising: The link access detection module is used to monitor network ports to capture data packets suspected of link access, extract key information, and trigger the new link judgment process. The new link access judgment module is used to receive the key information, verify the legality of the link and judge the novelty of the link, and filter out legal new links; The group matching and protocol driver pool invocation module is used to extract and standardize the features of the legitimate new link, match the group to which it belongs based on multi-level grouping rules, and call the appropriate protocol driver from the protocol driver pool to complete the binding. The periodic task loading module is used to define periodic tasks and configure parameters according to the business scenario and driving capabilities of the group to which the link belongs, add the task to the scheduling queue and verify the binding validity with the link; The communication interface delivery processing module is used to parse the periodic task information, filter suitable communication interfaces, generate and optimize the delivery instructions, send them to the link device through the interface, and monitor the execution results. The multi-network fusion computing module is used to collect real-time data from multiple network environments and links, and generate optimization parameters through fusion computing to achieve global optimization of link communication.

[0016] Compared with the prior art, the present invention has the following beneficial effects: 1. This invention constructs a full-process control mechanism of "access detection - legality judgment - group matching and driver invocation - task loading - interface distribution - fusion optimization" through the collaborative work of six core modules. It is different from the traditional link control method that relies on static rules or simple threshold judgment. It innovates from multiple levels from link access, protocol adaptation, task scheduling to global optimization, and improves the accuracy, dynamic adaptability and resource utilization of communication link control.

[0017] 2. In this invention, the link access detection module enables real-time and accurate access monitoring, the new link access judgment module ensures the legality and novelty of access, the group matching and protocol driver pool calling module enables dynamic adaptation of protocol drivers, the periodic task loading module configures tasks as needed, the communication interface distribution and processing module ensures efficient instruction transmission, and the multi-network fusion computing module achieves global optimization. The cooperation of multiple links enables the communication link to better adapt to multi-protocol and multi-network fusion scenarios, meet the communication requirements of high real-time performance and high reliability, and is especially suitable for scenarios with stringent communication quality requirements such as power control and industrial control. Attached Figure Description

[0018] Figure 1 This is a flowchart illustrating the implementation of the protocol-driven pool-based dynamic management and control method for communication links provided by this invention. Detailed Implementation

[0019] The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0020] It should be noted that the following detailed descriptions are exemplary and intended to provide further explanation of this application. Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains.

[0021] It should be noted that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments according to this application. As used herein, the singular form is intended to include the plural form as well, unless the context clearly indicates otherwise. Furthermore, it should be understood that when the terms "comprising" and / or "including" are used in this specification, they indicate the presence of features, steps, operations, devices, components, and / or combinations thereof.

[0022] like Figure 1 As shown, this embodiment provides a method and system for dynamic management and control of communication links based on a protocol driver pool. Dynamic management and control of communication links is achieved through the collaborative work of six core modules. These modules work in sequence to form a full-process management and control mechanism encompassing "access detection - legality judgment - group matching and driver invocation - task loading - interface distribution - fusion optimization," as detailed below: Link access detection module: Implements link access detection, including: listening to network ports to capture data packets suspected of link access, extracting key information and triggering a new link judgment process.

[0023] New Link Access Judgment Module: Implements new link access judgment, including: receiving access detection information, verifying link legality (identity, parameters) and judging link novelty (first access or reconnection), and filtering legal new links.

[0024] The packet matching and protocol driver pool invocation module implements packet matching and protocol driver pool invocation, including: extracting and standardizing the features of legitimate new links, matching the corresponding packets based on multi-level packet rules, and invoking the appropriate protocol driver from the protocol driver pool and completing the binding.

[0025] Periodic task loading module: Implements periodic task loading, including: defining periodic tasks and configuring parameters according to the business scenario and driving capabilities of the group to which the link belongs, adding the task to the scheduling queue and verifying the binding validity with the link.

[0026] Communication interface delivery processing module: Implements communication interface delivery processing, including: parsing periodic task information, filtering suitable communication interfaces, generating and optimizing delivery instructions, sending them to link devices through the interface, and monitoring the execution results.

[0027] The specific implementation of each module will be further detailed below.

[0028] (a) Link Access Detection Module The link access detection module first completes the initialization of the listening process, including configuring the port, protocol, and buffer. Then, it captures network packets in real time via network sockets, performs preliminary filtering of the packets, extracts key information suspected of link access, and temporarily stores it. Finally, based on packet characteristics or time periods, it triggers a new link access judgment process, transmitting relevant information to continuously monitor whether any new links are attempting to access the network.

[0029] (1) Listener initialization Start the network listening service and configure the network port to listen on (e.g., a specific TCP / UDP port, selected according to communication requirements). Also, set the network protocol type to listen on (e.g., IPv4, IPv6, etc.) to adapt to different network environments.

[0030] Initialize the listening buffer to temporarily store received link access-related data, ensuring the continuity and stability of data reception.

[0031] (2) Real-time data capture It continuously receives data packets from the network using network sockets. When a data packet arrives at the listening port, its header information is immediately read to preliminarily determine whether it is a packet related to the link access. For example, it may perform initial filtering based on the packet's destination port, specific protocol identifier fields, etc.

[0032] If a packet is initially identified as a potential link access packet, extract key information from the packet, such as the source IP address, source port number, and link type identifier, and temporarily store this information in a temporary data structure to provide a basis for subsequent new link access judgments.

[0033] (3) Trigger judgment mechanism When a data packet that meets the initial screening criteria is captured, or when continuous suspected link access data traffic is detected within a certain time period (configurable time threshold, such as checking once every 100 milliseconds), the new link access judgment process is triggered, and the temporarily stored link access related information is passed to the new link access judgment module.

[0034] (ii) New Link Access Judgment Module The new link access judgment module first receives and parses the information from the link access detection module, extracting key elements. Next, it verifies the legitimacy of the link based on both identity and access parameters, and then queries records to determine if the link is novel. Finally, based on the judgment result, it either passes the legitimate new link information to the next module or feeds it back to the link access detection module for continued monitoring.

[0035] (1) Information reception and parsing Receive suspected new link access information transmitted by the link access detection module, including source IP address, source port number, link type identifier, and part of the data packet content.

[0036] This information is analyzed to extract the core elements used to determine new link access, such as the unique identifier of the link (which can be composed of the source IP, source port and link type) and the protocol version of the access request.

[0037] (2) Legality verification Identity authentication verification: Query the pre-stored legitimate link identity authentication information database in the system (such as a whitelist of legitimate links, key information, etc.) to verify the legitimacy of the identity of the suspected new link. For example, check if the source IP address is in the whitelist; if key verification is required, extract the key field from the access information and compare it with the corresponding information in the database.

[0038] Access parameter verification: Verify whether the parameters of the access link meet the system requirements. For example, check whether the protocol version matches the version supported by the system, and whether the expected communication bandwidth, latency, and other parameters of the link are within the system's capacity.

[0039] (3) Novelty judgment The system queries existing link connection records to determine if the link is being accessed for the first time. By comparing the link's unique identifier with the identifier in the record, if no matching identifier is found, it is determined to be a new link; if a matching identifier is found, it is further determined whether the link has been reconnected (e.g., reconnected after being disconnected), and the system policy is used to decide whether to treat it as a new link.

[0040] (4) Results Feedback Based on the results of the legality verification and novelty assessment, a judgment conclusion is generated. If it is determined to be a new and legitimate link, the link's detailed information (such as verified identity information, legitimate access parameters, etc.) is passed to the packet matching and protocol driver pool invocation module; if it is determined to be a non-new link or an illegal link, feedback is given to the link access detection module, which continues to monitor the network.

[0041] (III) Group matching and protocol driver pool invocation module The workflow of the group matching and protocol driver pool invocation module is as follows: After receiving legitimate new link information, the link features are first extracted and standardized; based on the standardized features, the group to which the link belongs is determined through multi-level rule matching; the protocol driver pool is queried according to the group identifier, and the appropriate protocol driver is selected and invoked; the binding and dynamic configuration of the driver and the link are completed, and the validity of the invocation is verified; finally, the successfully bound link information is passed to the periodic task loading module, or error information is fed back to the upstream module.

[0042] (1) Link feature extraction and standardization Receive the legitimate new link information transmitted by the new link access judgment module, and extract the core characteristics of the link, including but not limited to: link protocol type (such as TCP, UDP, MQTT, CoAP, etc.), data type of transmission (text, binary, streaming media, etc.), bandwidth requirements (low bandwidth / high bandwidth), real-time requirements (millisecond-level / second-level response), security level (encrypted / unencrypted), etc.

[0043] The extracted features are standardized to convert unstructured information into structured labels that the system can recognize (such as key-value pairs like "PROTOCOL=MQTT" and "REALTIME=HIGH"), ensuring consistency in feature matching.

[0044] (2) Construction and matching of grouping rule base A pre-built grouping rule base is used, employing a multi-level classification architecture: Primary classification: Classified by protocol type (e.g., TCP link group, UDP link group, IoT protocol group, etc.); Secondary classification: divided by business scenario (such as industrial control link group, power grid monitoring link group, video transmission link group, etc.); Third-level classification: Classified by performance requirements (such as low-latency link groups, high-reliability link groups, etc.).

[0045] A rule-based matching algorithm (such as forward inference matching) is used to compare the standardized link features with the group rule base to determine the optimal matching group. For example, if the link feature is "PROTOCOL=MQTT+REALTIME=LOW+SCENE=SMART_HOME", then it will match to "IoT Protocol Group - Power Grid Monitoring Subgroup - Low Real-Time Link Group".

[0046] (3) Protocol-driven pool architecture and index construction The protocol driver pool adopts a distributed storage architecture, which includes: Driver storage unit: Stores various protocol drivers (such as TCP driver, MQTT driver, etc.) according to protocol type. Each driver contains standardized components such as initialization interface, data encoding / decoding interface, and link status monitoring interface. Driver Index Table: Establish a multi-dimensional index of "protocol type-group identifier-driver version-performance parameters" to support fast query (e.g., indexing the corresponding version of the MQTT driver through "MQTT+power grid monitoring group"). Driver status management unit: Real-time recording of each driver's load rate (e.g., how many links are currently in use), running status (available / under maintenance), version information, etc.

[0047] (4) Driver Invocation and Adaptation Based on the matching group identifier, the appropriate protocol driver is queried through the driver index table, and drivers with load rates below the threshold (e.g., 70%) and version compatibility are selected first. Call the driver initialization interface, pass in the link parameters (such as IP address, port, encryption key, etc.), and complete the binding between the driver and the link; Dynamically configure the driver: Adjust parameters such as driver cache size, retransmission mechanism, and heartbeat detection period according to link performance requirements (e.g., set the heartbeat period to 100ms for high real-time links).

[0048] (5) Verification and feedback of call results Verify driver call results: Check whether the link connection was successfully established through the driver status interface, and test whether the data transmission and reception functions are normal (such as sending test frames and receiving responses). If the call is successful, the "group identifier + driver ID + link parameters" package is passed to the periodic task loading module; if it fails (e.g., no available driver or incompatible parameters), an error code is returned to the new link access judgment module, triggering the link access retry mechanism.

[0049] (iv) Periodic task loading module The periodic task loading module first receives link-related information and analyzes task requirements; then it selects a template from the template library, configures parameters, and defines the periodic task; next, it manages the task scheduling queue, enqueues tasks, and sets scheduling parameters; then it verifies the binding between the task and the link; finally, it passes the information of successfully loaded tasks to the next module, or reports failure information to the upstream module. This entire process ensures that periodic tasks can adapt to link requirements, providing a foundation for task execution for subsequent communication interface distribution and dynamic link management.

[0050] (1) Task requirements analysis Receive the "packet identifier + driver ID + link parameters" information passed by the packet matching and protocol driver pool calling module.

[0051] Based on the typical business scenarios of the link's group (such as the industrial control group requiring periodic data acquisition, and the smart home group requiring timed status synchronization), and the task interface capabilities provided by the driver (such as supported task types and task parameter ranges), analyze the types of periodic tasks that the link needs to execute. For example, for an industrial control link, periodic sensor data acquisition tasks and equipment status monitoring tasks may be required; for a video transmission link, periodic bitrate adjustment tasks and connection stability detection tasks may be required.

[0052] (2) Periodic task definition and parameter configuration Task Definition: Based on the analysis results, select a suitable task template from the system's predefined periodic task template library. The task template library contains templates for various common periodic tasks, such as data acquisition task templates (defining acquisition frequency, data type, etc.), status monitoring task templates (defining monitoring indicators, monitoring period, etc.), and parameter adjustment task templates (defining adjustment parameter type, adjustment period, etc.).

[0053] Parameter Configuration: Based on link parameters and drive capabilities, configure the parameters of the selected task template. For example, the acquisition cycle of the data acquisition task can be set to 500 milliseconds according to the real-time requirements of the link and network bandwidth; the monitoring indicators of the status monitoring task can be configured as key indicators such as link packet loss rate and latency. At the same time, set the execution priority of the tasks to ensure that critical tasks (such as fault detection tasks) are executed first.

[0054] (3) Task scheduling queue management Queue initialization: The system maintains multiple task scheduling queues, which can be categorized according to task priority, task type, etc. For example, high-priority queues are used to store tasks such as fault detection and urgent parameter adjustment; ordinary-priority queues are used to store tasks such as routine data acquisition and status synchronization.

[0055] Task enqueueing: Configured periodic tasks are inserted into the corresponding task scheduling queues according to their priority and type. During the enqueueing process, the queue capacity is checked. If the queue is full, the tasks in the queue are adjusted according to the queue's scheduling strategy (such as first-in-first-out, priority preemption, etc.) to ensure that new tasks can be added correctly.

[0056] Scheduling parameter settings: Set execution cycle (e.g., execute once every 1 second) and first execution delay (e.g., start the first execution 500 milliseconds after the task is enqueued) for each enqueued task. These parameters will be read by the task scheduler to control the timing of task execution.

[0057] (4) Task and link binding verification The task binding interface provided by the driver is called to bind the configured periodic task to the corresponding link. For example, the data acquisition task can be registered to the driver instance of the link through the driver's task registration function.

[0058] Send a test task command to verify whether the task can be triggered and executed correctly. For example, send a test data acquisition task to check whether data can be successfully acquired from the corresponding device on the link and correctly transmitted back. If the verification fails, roll back the task configuration, redefine the task and reconfigure the parameters until the verification passes.

[0059] (5) Task loading result feedback If the task loading and verification are successful, the task scheduling queue information, the task-link binding relationship, and other information will be passed to the communication interface distribution processing module so that subsequent modules can generate communication interface distribution instructions based on this information.

[0060] If the task loading fails, record the reason for the failure (such as invalid task parameters, driver not supporting the task, etc.) and report it to the group matching and protocol driver pool calling module so that the upstream module can adjust the driver call or link grouping and other operations.

[0061] (v) Communication Interface Processing Module The communication interface delivery processing module first receives and parses the task information from the periodic task loading module, clarifying the task details and link-related data. Next, it selects the optimal interface matching the link and task from the communication interface resource library and generates a delivery command conforming to the protocol specification based on the task information and interface attributes. Then, the command is optimized and encapsulated, delivered through the selected interface, and the transmission process is monitored. After delivery, the execution result returned by the device is verified. Successful results are passed to the multi-network converged computing module; failures are reported back to the periodic task loading module for processing. This process ensures that task commands are accurately and efficiently transmitted to the target link, providing practical operational command support for the dynamic management of the link.

[0062] (1) Task information reception and parsing Receive data such as task scheduling queue information and task-link binding relationships transmitted by the periodic task loading module.

[0063] Analyze this information to extract key details, including task type (e.g., data acquisition, status monitoring, parameter adjustment), execution cycle, link identifier, corresponding protocol driver information, task priority, and specific task parameters (e.g., data points to be acquired, monitoring threshold values, and adjusted parameter values). For example, for a data acquisition task, the device address, data register range, and acquisition frequency must be clearly defined.

[0064] (2) Communication interface selection and adaptation Based on the link identifier and protocol driver information, the system's communication interface resource library is queried. This resource library records the communication interface types supported by each link (such as RS232, RS485, Ethernet, Wi-Fi, LoRa, etc.), the physical attributes of the interface (baud rate, data bits, stop bits, parity, etc.), the current load status of the interface, and the compatibility information between the interface and the protocol driver.

[0065] Select communication interfaces that match the current link and task. The selection criteria include: the interface type is compatible with the protocol driver (e.g., the MQTT protocol is usually adapted to Ethernet or Wi-Fi interfaces), the current load rate of the interface is lower than a set threshold (e.g., not exceeding 60%) to ensure task execution efficiency, and the transmission performance (bandwidth, latency) of the interface meets the real-time requirements of the task.

[0066] If multiple compatible interfaces exist, they should be sorted according to task priority and interface performance, and the optimal interface should be selected. For example, a high-priority fault detection task should preferentially choose the Ethernet interface with lower latency, rather than the Wi-Fi interface.

[0067] (3) Issuing instructions to generate Based on the parsed task information and the selected communication interface attributes, specific communication interface commands are generated. The command format must conform to the interface's communication protocol specifications. For example, for a Modbus protocol task on an RS485 interface, the command must include fields such as slave address, function code, data address, data length, and checksum; for a TCP protocol task on an Ethernet interface, the command must include source port, destination port, sequence number, acknowledgment number, and data segment.

[0068] The instructions must clearly specify the execution parameters of the task. For example, instructions for data acquisition tasks should include the specific acquisition command and the storage address of the returned data; instructions for parameter adjustment tasks should include the name of the parameter to be adjusted and the target value. Additionally, the link identifier and task ID should be embedded in the instructions to facilitate subsequent tracking of instruction execution.

[0069] (4) Instruction optimization and encapsulation The generated instructions are optimized. For example, for periodically recurring instructions, instruction compression technology can be used to reduce the amount of data transmitted; for high-priority tasks, priority markers are added to ensure that the interface processes them first during transmission.

[0070] The instructions are encapsulated according to the frame format requirements of the communication interface. A frame header (containing interface identifier, instruction type, etc.) and a frame trailer (containing checksum information, frame end marker, etc.) are added to ensure that the instructions are not tampered with during transmission and can be correctly identified and parsed by the receiving end.

[0071] (5) Interface distribution and transmission monitoring The encapsulated command is sent to the corresponding device or module via the selected communication interface. During the transmission process, a transmission monitoring mechanism is activated to monitor the transmission status of the command in real time, including whether the transmission was successful, the packet loss rate, and the transmission delay.

[0072] If the command fails to be sent (e.g., no acknowledgment is received within a timeout period), a retry will be performed according to the preset retry strategy (e.g., number of retries, retry interval). If multiple retries still fail, the failure information (e.g., reason for failure, failure time) will be recorded, and an alarm mechanism will be triggered.

[0073] (6) Issuance of results for verification and feedback Receive instruction execution response information returned by the link device or module. Parse the response information to determine whether the instruction was successfully executed (e.g., whether the data acquisition task returned valid data, or whether the parameter adjustment task reported successful adjustment).

[0074] If the instruction executes successfully, the result (such as execution time and returned data summary) is transmitted to the multi-network fusion computing module, and the execution status of the task in the task scheduling queue is updated. If the instruction fails, the cause of failure is analyzed (such as incorrect instruction format, device unresponsiveness, etc.), and the failure information is fed back to the periodic task loading module so that the task parameters can be readjusted or the communication interface can be changed.

[0075] (vi) Multi-network converged computing module The multi-network converged computing module collects multi-dimensional data in real time to complete network and link status assessment, bottleneck location, generate and verify optimization strategies, and finally distribute parameters and verify the effect, forming a closed-loop optimization mechanism of "data collection-status assessment-strategy generation-parameter verification-distribution verification", realizing global dynamic optimization of link communication in multi-network environments.

[0076] (1) Real-time data acquisition and standardized processing It is responsible for acquiring real-time operational data from multiple networks and links, and after filtering and standardization, provides basic data in a unified format for subsequent evaluation and optimization.

[0077] Data collection configuration Initialize the acquisition node and define the acquisition range and period: Collection scope: Includes link data (transmission rate, packet loss rate, round-trip delay, network type), network data (total bandwidth utilization, idle bandwidth, signal strength, number of connected links), and service data (task priority, data transmission direction). Data collection period: By default, data is collected every 500ms; when the network bandwidth utilization is greater than 80%, high-frequency data collection (100ms / time) is triggered.

[0078] Real-time data acquisition Raw data is captured through distributed acquisition interfaces (such as network sniffers and link status sensors), and invalid values ​​(such as abnormal data caused by link interruption and duplicate data) are filtered in real time, retaining only valid operational data.

[0079] Data standardization Standardized format: Convert all data into a structured key-value pair format of "Link ID + Timestamp + Parameter Name + Parameter Value" (e.g., "LINK-001+1620000000000+LOSS_RATE+0.02"). Units are standardized: the rate unit is Mbps, the latency unit is ms, and proportional parameters (such as packet loss rate and bandwidth utilization) are rounded to one decimal place.

[0080] (2) Network and link status assessment and bottleneck identification Based on standardized data, assess the current state of the network and links, and locate key bottlenecks affecting communication quality according to preset rules.

[0081] Evaluation Indicator Definition Define the core evaluation indicators and thresholds: Link status: Availability (1 - packet loss rate, >0.9 is available, <0.7 is low availability), responsiveness (100ms / latency, >1 is excellent, <0.5 is poor), adaptability (high priority tasks need >0.8, others ≥0.5); Network status: load level (≤50% is low load, 50%-80% is medium load, >80% is high load), wireless quality (signal strength ≥-70dBm is excellent, -70~-85dBm is medium, <-85dBm is poor).

[0082] Status assessment execution Calculate the real-time value using the indicator formula: For example, if the packet loss rate of a certain link is 0.15, then the availability = 1 - 0.15 = 0.85; if the latency is 200ms, then the responsiveness = 100 / 200 = 0.5. If a network bandwidth utilization rate is 85%, it is considered to be under high load; if the wireless signal strength is -90dBm, it is considered to be poor.

[0083] Bottleneck Identification Bottleneck type matching based on rules: Network load bottleneck: In a high-load network, the adaptability of ≥3 links is <0.5; Link quality bottleneck: Link availability < 0.7, and the network to which it belongs is under medium / low load; Business adaptation bottleneck: The responsiveness of the link where high-priority tasks are located is <0.8.

[0084] (3) Optimize strategy generation and rule matching For the identified bottleneck type, the optimal strategy is matched from the preset strategy library and refined into executable operation directions.

[0085] Strategy library construction A predefined classification strategy library stores optimization rules according to bottleneck type: Network load bottlenecks: traffic offloading (migrating links with low adaptability to the same type of low-load network), bandwidth limitation (limiting the link rate of low-priority tasks to 70% of the current rate); Link quality bottlenecks: link switching (switching to a backup link of the same type with availability > 0.9), parameter adjustment (switching to a strong signal channel when the wireless link signal is < -85dBm); Business adaptation bottlenecks: resource allocation (relocating ≤30% bandwidth from low-priority links) and priority upgrade (increasing task scheduling priority by 1 level).

[0086] Strategy matching Invoke the corresponding strategy based on the bottleneck type: For example, when a network load bottleneck is identified, the "traffic offloading" strategy is matched first; if the target network has no idle resources, the "bandwidth limiting" strategy is matched then.

[0087] Strategy refinement Translate the matching strategy into specific operational directions: The traffic diversion strategy needs to clearly define the target network ID and the time window for link migration (such as the current task interval). Bandwidth limits need to specify the maximum rate and the effective time.

[0088] (4) Optimize parameter generation and validity verification The refined strategy is transformed into configurable parameters, and the feasibility and security of the parameters are ensured through multi-dimensional verification.

[0089] Parameter extraction Output specific parameter values: Link migration parameters: target network ID (e.g., “NET-002”), handover delay threshold (<100ms); Bandwidth parameters: maximum speed (e.g., 5Mbps), adjustment effective time (e.g., after 10 seconds); Channel parameters: target channel number (e.g., 11), handover execution timing.

[0090] Multi-dimensional verification Feasibility verification: The target network's idle bandwidth must be greater than or equal to the current link speed (e.g., if the current link speed is 3Mbps, the target network's idle bandwidth must be greater than or equal to 3Mbps). Security verification: After high-priority task bandwidth is allocated, the availability of the allocated link must be ≥0.8; Conflict check: The sum of all bandwidth adjustments within the same network is less than or equal to the network's available bandwidth.

[0091] Verification result processing Validation passed: Parameters are entered into the distribution queue and marked as "pending execution"; Verification failed: Return to the policy generation stage and readjust the policy (e.g., change the target network or reduce the bandwidth allocation ratio).

[0092] (5) Optimize parameter distribution and effect verification The validated parameters are distributed to the corresponding modules for execution, and the optimization effect is monitored and verified to form a closed-loop control.

[0093] Parameter distribution Send data to the relevant module based on parameter type: Link migration, channel parameters → packet matching and protocol driver pool calling module (used for driver switching and link rebinding). Bandwidth limitations and priority parameters → Communication interface processing module (used for interface resource adjustment).

[0094] A "command + confirmation" mechanism is adopted to ensure that the module successfully receives parameters (after the receiver returns a confirmation code, it is marked as "received").

[0095] Send monitoring Real-time monitoring of parameter transmission status: Record the delivery time and transmission delay (must be <50ms); If no confirmation is received within a timeout period (e.g., after 3 retries), an alarm is triggered and the reason for the failure is recorded (e.g., module offline, network interruption).

[0096] Effect evaluation Evaluation cycle: Effect detection to be completed within 10 seconds of parameter distribution; Success criteria: Network load bottleneck: Target network load rate decreases by ≥15%; Link quality bottleneck: Link availability improvement ≥ 0.2; Business adaptation bottleneck: Task responsiveness improvement ≥ 0.3.

[0097] Failure handling: If the target is not met, immediately roll back to the original parameters, record the reason (such as no available backup link, insufficient bandwidth allocation), and include it in the next optimization analysis.

[0098] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0099] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0100] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0101] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0102] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention in any other way. Any person skilled in the art may make changes or modifications to the above-disclosed technical content to create equivalent embodiments. However, any simple modifications, equivalent changes, and modifications made to the above embodiments based on the technical essence of the present invention without departing from the scope of the present invention shall still fall within the protection scope of the present invention.

Claims

1. A method for dynamic management and control of communication links based on a protocol-driven pool, characterized in that, include: 1) Link access detection: Monitor network ports to capture data packets suspected of link access, extract key information, and trigger new link judgment process; 2) New Link Access Judgment: Receive the key information, verify the legality of the link and determine its novelty, and filter out legal new links; 3) Group matching and protocol driver pool invocation: Extract the features of the legal new link and standardize them, match the group to which it belongs based on multi-level grouping rules, and call the appropriate protocol driver from the protocol driver pool to complete the binding; 4) Periodic task loading: Define periodic tasks and configure parameters according to the business scenario and driving capabilities of the group to which the link belongs, add the tasks to the scheduling queue and verify the binding validity with the link; 5) Communication interface delivery processing: Parse the periodic task information, select suitable communication interfaces, generate and optimize the delivery instructions, send them to the link device through the interface, and monitor the execution results; 6) Multi-network fusion computing: Collect real-time data from multiple network environments and links, generate optimization parameters through fusion computing, and achieve global optimization of link communication.

2. The method for dynamic management and control of communication links based on a protocol-driven pool according to claim 1, characterized in that, In step 1), the link access detection includes: Listening initialization: Start the network listening service, configure the network port to listen on, and set the network protocol type to listen on; initialize the listening buffer to temporarily store the received link access related data; Real-time data capture: Receive data packets from the network using network sockets; when a data packet arrives at the listening port, read the header information of the data packet to make a preliminary judgment on whether it is a data packet related to link access; if it is preliminarily judged to be a possible link access data packet, extract key information from the data packet, including source IP address, source port number and link type identifier, and temporarily store this key information in a temporary data structure; Triggering judgment mechanism: When a data packet that meets the conditions is captured, or when continuous suspected link access data traffic is detected within a set time period, the new link access judgment process is triggered, and the temporarily stored link access related information is passed to the new link access judgment module for new link access judgment.

3. The method for dynamic management and control of communication links based on a protocol-driven pool according to claim 1, characterized in that, In step 2), the verification of the link's legitimacy includes identity authentication verification and access parameter verification; The identity authentication verification process involves: querying a pre-stored database of legitimate link identity information to verify the link identity; The legitimate link identity information database contains a whitelist of legitimate links and key information; The access parameter verification is as follows: verifying whether the parameters of the link access meet the system requirements, including: verifying whether the protocol version matches the version supported by the system, and verifying whether the expected communication bandwidth and delay parameters of the link are within the range that the system can bear. The determination of link novelty includes: comparing the link's unique identifier with the system record; if no identical identifier exists, it is determined to be a new link; if an identical identifier exists, it is determined to be a reconnection, and the system policy decides whether to process it as a new link. Based on the results of link legitimacy verification and link novelty judgment, a judgment conclusion is generated. If it is determined to be a new legitimate link, the link's detailed information is passed to the packet matching and protocol driver pool invocation module for packet matching and protocol driver pool invocation. If it is determined to be a non-new link or an illegal link, feedback is given to the link access detection module so that it can continue to perform link access detection.

4. The method for dynamic management and control of communication links based on a protocol-driven pool according to claim 1, characterized in that, In step 3), the multi-level grouping rules adopt a three-level classification architecture: Primary classification: Classified by protocol type; the protocol types include TCP Link Group, UDP Link Group, and IoT Protocol Group; Secondary classification: divided by business scenario; the business scenarios include industrial control link group, power grid monitoring link group and video transmission link group; Third-level classification: Classified by performance requirements, which include low-latency link groups and high-reliability link groups.

5. The method for dynamic management and control of communication links based on a protocol-driven pool according to claim 1, characterized in that, In step 3), the protocol driver pool includes: Driver storage unit: Stores drivers according to protocol type, including initialization interface, data encoding / decoding interface and link status monitoring interface; Driver Index Table: Create a multi-dimensional index based on "protocol type - packet identifier - driver version - performance parameters"; Driver status management unit: records driver load rate, running status and version information in real time.

6. The method for dynamic management and control of communication links based on a protocol-driven pool according to claim 1, characterized in that, In step 4), the periodic task loading includes: Task Requirements Analysis: Receive the "protocol type-packet identifier-driver version-performance parameters" information passed by the packet matching and protocol driver pool call module; combine the typical business scenarios of the packet to which the link belongs, and the task interface capabilities provided by the driver, to analyze the types of periodic tasks that the link needs to execute; Periodic task definition and parameter configuration: Based on the analysis results, select a suitable task template from the system's predefined periodic task template library; then configure the parameters of the selected task template based on the link parameters and driving capabilities. Task scheduling queue management: First, initialize the task scheduling queue, then insert the configured periodic tasks into the corresponding task scheduling queue according to their priority and type, and then set scheduling parameters including execution cycle and first execution delay for each enqueued task; Task and Link Binding Verification: Call the task binding interface provided by the driver to bind the configured periodic task with the corresponding link; then send a test task command to verify whether the task can be triggered and executed correctly. Task loading result feedback: If the task loading and verification are successful, the task scheduling queue information and the task-link binding relationship information are passed to the communication interface delivery processing module so that subsequent modules can generate communication interface delivery instructions based on this information; if the task loading fails, the reason for the failure is recorded and fed back to the group matching and protocol driver pool calling module so that the upstream module can adjust the driver call or link group operation.

7. The method for dynamic management and control of communication links based on a protocol-driven pool according to claim 1, characterized in that, In step 5), the communication interface sending process includes: Task information reception and parsing: Receives task scheduling queue information and task-link binding relationship data transmitted by the periodic task loading module, and parses this information to extract key content, including task type, execution cycle, link identifier, corresponding protocol driver information, task priority, and specific task parameters; Communication interface filtering and adaptation: Based on the link identifier and protocol driver information, query the communication interface resource library in the system; filter out the communication interfaces that match the current link and task. The filtering principles include: the interface type is compatible with the protocol driver, the current load rate of the interface is lower than the set threshold to ensure the task execution efficiency, and the transmission performance of the interface meets the real-time requirements of the task; if there are multiple adapted interfaces, sort them according to task priority and interface performance, and select the optimal interface. Command generation: Based on the parsed task information and the selected communication interface attributes, generate specific communication interface command generation. Instruction optimization and encapsulation: The generated instructions are optimized; for periodically repetitive instructions, instruction compression technology is used to reduce the amount of data during transmission; for instructions of high-priority tasks, priority markers are added to ensure that the interface processes them first during transmission; then, the instructions are encapsulated according to the frame format requirements of the communication interface. Interface delivery and transmission monitoring: Through the selected communication interface, the encapsulated delivery command is sent to the corresponding device or module of the link; during the transmission process, the transmission monitoring mechanism is activated to monitor the delivery status of the command in real time; if the command delivery fails, it is retried according to the preset retry strategy; if it still fails after multiple retries, the failure information is recorded and the alarm mechanism is triggered. Result verification and feedback: Receive instruction execution response information returned by the link device or module; parse the response information to determine whether the instruction was successfully executed; if the instruction was successfully executed, pass the result to the multi-network fusion computing module and update the execution status of the task in the task scheduling queue; if the instruction failed to execute, analyze the reason for the failure and feed back the failure information to the periodic task loading module so that the task parameters can be readjusted or the communication interface can be changed.

8. The method for dynamic management and control of communication links based on a protocol-driven pool according to claim 1, characterized in that, In step 6), the multi-network fusion computation includes: Real-time data acquisition and standardization: Acquire real-time operational data from multiple networks and links, and after filtering and standardization, provide basic data in a unified format for subsequent evaluation and optimization; Network and link status assessment and bottleneck identification: Based on standardized data, assess the current status of the network and links, and locate key bottlenecks affecting communication quality according to preset rules; Optimize strategy generation and rule matching: For the identified bottleneck type, match the optimal strategy from the preset strategy library and refine it into executable operation directions; Optimize parameter generation and validity verification: Transform refined strategies into configurable parameters, and ensure the feasibility and security of parameters through multi-dimensional verification; Optimization parameter distribution and effect verification: Distribute the verified parameters to the corresponding modules for execution, monitor and verify the optimization effect, and form a closed-loop control.

9. The method for dynamic management and control of communication links based on a protocol-driven pool according to claim 1, characterized in that, In step 6), the optimization parameters are sent to the associated modules according to their type: link migration and channel parameters are sent to the packet matching and protocol driver pool calling module, and bandwidth limitation and priority parameters are sent to the communication interface sending and processing module. A "command + confirmation" mechanism is used to ensure reception.

10. A communication link dynamic management and control system for implementing the method as described in any one of claims 1-9, characterized in that, include: The link access detection module is used to monitor network ports to capture data packets suspected of link access, extract key information, and trigger the new link judgment process. The new link access judgment module is used to receive the key information, verify the legality of the link and judge the novelty of the link, and filter out legal new links; The group matching and protocol driver pool invocation module is used to extract and standardize the features of the legitimate new link, match the group to which it belongs based on multi-level grouping rules, and call the appropriate protocol driver from the protocol driver pool to complete the binding. The periodic task loading module is used to define periodic tasks and configure parameters according to the business scenario and driving capabilities of the group to which the link belongs, add the task to the scheduling queue and verify the binding validity with the link; The communication interface delivery processing module is used to parse the periodic task information, filter suitable communication interfaces, generate and optimize the delivery instructions, send them to the link device through the interface, and monitor the execution results. The multi-network fusion computing module is used to collect real-time data from multiple network environments and links, and generate optimization parameters through fusion computing to achieve global optimization of link communication.

Images