A three-face decoupling software-defined wireless ad hoc network and containerized implementation method

Abstract

The application discloses a kind of three-face decoupling software-defined wireless ad hoc network and containerization implementation method, belong to wireless ad hoc network communication and network management field, including steps: introducing the mixed SDN architecture design of three-face decoupling, respectively set up management face module, control face module and data face module, for the function separation of policy decision, centralized control and data forwarding;Introduce invulnerability design, set the master-slave cluster head switching mechanism of control face module, for when detecting that main cluster head node fails, based on node energy, location and historical load parameter weighted election new cluster head node, and complete cluster scheduling recovery;The application improves link utilization and data transmission performance, with good task adaptability and system resilience.

Description

Technical Field

[0001] This invention relates to the field of wireless ad hoc network communication and network management, and more specifically, to a three-sided decoupled software-defined wireless ad hoc network and containerized implementation method. Background Technology

[0002] With the development of modern communication technologies and the autonomous collaborative capabilities of unmanned platforms, wireless ad hoc networks, as a key support means for battlefield command, mission collaboration, and situational awareness, place higher demands on network communication systems in terms of dynamic adaptability, real-time performance, and resilience. Traditional wireless ad hoc networks mostly adopt static networking and centralized control architectures, with node and link configurations relying on presets. This lack of flexibility makes them difficult to effectively cope with complex environmental conditions such as frequent node movement, drastic changes in link quality, or enemy interference and sabotage.

[0003] In recent years, Software Defined Networking (SDN), a technology that decouples the network control plane from the data forwarding plane to achieve centralized management and flexible programming, has been widely used in data center and wide area network management. SDN can significantly improve network programmability and resource scheduling capabilities by uniformly issuing rules through the controller and dynamically adjusting routing and flow table configurations. However, traditional SDN architectures still have the following prominent problems when applied to wireless ad hoc networks, especially in highly mobile and highly adversarial scenarios:

[0004] First, centralized deployment of controllers leads to a high risk of single points of failure. For example, in high-threat environments, if a controller suffers a physical attack or link loss, it may paralyze the entire cluster or even the global network, lacking the necessary resilience and self-recovery capabilities. Second, standard SDN architectures lack local autonomy. In traditional centralized control models, the response of each data plane node to sudden environmental changes is highly dependent on controller commands. They cannot make autonomous local decisions when links are interrupted or communication with the controller is lost, affecting system survivability and task continuity. Third, domain coordination and state consistency maintenance are difficult. Under distributed control requirements, multiple controllers need to maintain consistent synchronization of topology, state, and policy information. Existing SDN systems do not adequately support state consistency and fault-tolerant switching between controllers, easily leading to data inconsistencies, policy conflicts, or recovery delays.

[0005] Furthermore, while existing improvement solutions, such as distributed SDN frameworks, introduce multi-controller collaboration mechanisms, they have not yet achieved deep application-oriented adaptation and optimization capabilities to meet the unique demands of highly dynamic wireless ad hoc networks, including on-the-spot task adjustments and complex threat countermeasures. For example, core issues such as cluster reorganization caused by frequent node movement, cross-cluster communication link maintenance, adaptive resource scheduling, and task priority assurance still lack systematic technical support. Summary of the Invention

[0006] The purpose of this invention is to overcome the shortcomings of the prior art and provide a three-sided decoupled software-defined wireless ad hoc network and containerized implementation method. It takes into account the characteristics of wireless ad hoc networks, balances centralized control and local autonomy, has distributed consistency management and rapid fault recovery capabilities, and can adapt to the intelligent optimization needs in highly dynamic environments. It improves link utilization and data transmission performance, and has good task adaptability and system resilience.

[0007] The objective of this invention is achieved through the following solution:

[0008] A three-sided decoupled software-defined wireless ad hoc network and containerized implementation method, comprising:

[0009] Step one introduces a three-plane decoupled hybrid SDN architecture design, establishing a management plane module, a control plane module, and a data plane module to separate the functions of policy decision-making, centralized control, and data forwarding. The management plane module is responsible for global policy formulation and decision-making, generating network topology, managing cluster members, executing primary / backup cluster head election, and maintaining the controller cluster. It issues policies and configuration commands to the control plane module via the northbound interface. The control plane module includes multiple controller nodes, which achieve state synchronization and consistency maintenance through distributed collaborative components. The controller nodes exchange link status, node load, and threat information through the eastbound and westbound interfaces, supporting local autonomy and network-wide collaboration. The data plane module includes virtual switches deployed in each node device. These virtual switches receive control commands and execute data forwarding rules through the southbound interface, ensuring data flow timeliness and enabling autonomous execution of local policies. The northbound, eastbound / westbound, and southbound interfaces achieve functional decoupling and interaction between the management plane module, control plane module, and data plane module.

[0010] Step 2: Introduce a robust design and set up a primary / backup cluster head switching mechanism in the control plane module. When the primary cluster head node fails, a new cluster head node is elected based on a weighted average of node energy, location, and historical load parameters, and intra-cluster scheduling is restored.

[0011] Furthermore, the northbound interface specifically adopts the RESTful API standard, is implemented based on the HTTP protocol, and supports the dynamic injection of policy distribution, control parameter configuration, task priority adjustment, and fault recovery policies.

[0012] Furthermore, the northbound interface is equipped with a modular expansion mechanism to accommodate the data interaction needs of the cloud orchestration platform and the artificial intelligence inference engine.

[0013] Furthermore, the east-west interface is specifically built based on the Raft consensus protocol. The controller node periodically synchronizes its own state information through the east-west interface built based on the Raft consensus protocol. When the heartbeat failure of any node is detected, the master node election and control takeover process is triggered.

[0014] Furthermore, the southbound interface is specifically implemented using the OpenFlow 1.3 protocol, which supports dynamic distribution of flow tables, port monitoring, traffic path adjustment, and priority scheduling rule configuration for virtual switches.

[0015] Furthermore, the controller cluster specifically constructs a global information pool through an east-west interface. The global information pool includes link quality status, node load, resource allocation, and threat detection information.

[0016] Furthermore, the virtual switch is pre-configured with a local control strategy. When the control plane module connection is lost, traffic forwarding and path selection continue according to the pre-configured local control strategy to ensure that local communication is not interrupted.

[0017] The beneficial effects of this invention include:

[0018] This invention, centered on a management plane module, a control plane module, and a data plane module, employs a hybrid software-defined layered design. Through three-plane decoupling, it achieves flexible network control, dynamic adaptation, and intelligent optimization. The management plane module is responsible for global policy formulation and task-driven intelligent decision-making. The control plane module achieves distributed state synchronization and consistency maintenance through a controller cluster and collaborative components based on a distributed consensus protocol. The data plane module, composed of virtual switches, supports real-time perception and forwarding of task data. This architecture introduces distributed and centralized collaborative mechanisms, supporting local autonomy and network-wide collaboration. Combined with robust design, it ensures the survivability and communication continuity of wireless ad hoc networks in highly dynamic and highly adversarial environments. Furthermore, through standardized design of northbound, eastbound, and southbound interfaces, it achieves efficient collaboration in policy issuance, state synchronization, and command execution. Simulation results demonstrate that this architecture maintains high consistency and rapid recovery capabilities under node failure and high load conditions, significantly improving link utilization and data transmission performance, and exhibiting good task adaptability and system resilience. Attached Figure Description

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

[0020] Figure 1This is a schematic diagram of the three-sided decoupled software-defined network architecture based on container technology proposed in this invention;

[0021] Figure 2 This is a schematic diagram of the overall dynamic management process of the present invention;

[0022] Figure 3 This is a schematic diagram of the controller cluster distribution and coordination mechanism of the present invention;

[0023] Figure 4 This is a schematic diagram of the deployment of the simulation platform of the present invention. Detailed Implementation

[0024] All features disclosed in all embodiments of this specification, or steps in all methods or processes implied in the disclosure, may be combined and / or extended or replaced in any way, except for mutually exclusive features and / or steps.

[0025] The specific implementation process of this invention is as follows:

[0026] To address the problems mentioned in the background, this invention proposes a three-sided decoupled software-defined wireless ad hoc network and containerized implementation method, aiming to improve the task execution performance and system resilience of wireless ad hoc networks in complex environments from the architecture level, so as to achieve efficient management and control, intelligent optimization and high-reliability communication guarantee of wireless ad hoc networks.

[0027] In a preferred embodiment, a method for implementing a three-sided decoupled software-defined wireless ad hoc network and containerization is provided, specifically including:

[0028] Step one introduces a three-plane decoupled hybrid SDN architecture design, establishing a management plane module, a control plane module, and a data plane module to separate the functions of policy decision-making, centralized control, and data forwarding. The management plane module is used for global policy formulation and decision-making, generating network topology, managing cluster members, executing primary / backup cluster head election, and maintaining the controller cluster. It issues policies and configuration commands to the control plane module through the northbound interface. The control plane module includes multiple controller nodes. Controllers achieve state synchronization and consistency maintenance through distributed collaborative components. Controller nodes exchange link status, node load, and threat information through east-west interfaces, supporting local autonomy and network-wide collaboration. The data plane module includes virtual switches deployed in each node device. These virtual switches receive control commands and execute data forwarding rules through the southbound interface, ensuring data flow timeliness and enabling autonomous execution of local policies. The functions of the management plane module, control plane module, and data plane module are decoupled and interact through the northbound, east-west, and southbound interfaces.

[0029] Specifically, in the management plane module, a global policy formulation and intelligent decision-making module is deployed. Dynamic control policies are issued to the control plane via a RESTful API, supporting functions such as network topology generation, dynamic cluster member grouping, and primary / backup cluster head switching. In the control plane module, a multi-controller cluster architecture is adopted. Controllers maintain state consistency and role switching capabilities through the Raft protocol and Atomix collaborative components, achieving distributed control and high availability. In the data plane module, virtual switches deployed on front-line equipment are used to execute local control policies and efficiently forward data, ensuring local communication self-sustainability in link interruption scenarios. Distributed and centralized collaborative mechanisms are introduced to achieve local autonomy and network-wide collaborative scheduling, effectively improving system adaptability and resource utilization efficiency. Simultaneously, northbound, eastbound, and southbound interfaces are designed and implemented, corresponding to efficient interaction and task collaboration between the management plane, control plane, and data plane, respectively.

[0030] Step 2: Introduce a robust design and set up a primary / backup cluster head switching mechanism in the control plane module. When the primary cluster head node fails, a new cluster head node is elected based on a weighted average of node energy, location, and historical load parameters, and intra-cluster scheduling is restored.

[0031] Specifically, by employing control plane primary / backup cluster head switching and data plane path reconstruction strategies, the network's self-recovery capability and task continuity in high-adversarial environments can be improved.

[0032] In other embodiments, based on the above embodiments, this invention further proposes a three-plane decoupled software-defined wireless ad hoc network and containerized implementation method, mainly including a management plane module, a control plane module, and a data plane module. These three modules cooperate through interfaces to achieve dynamic management and efficient control of the wireless ad hoc network, specifically including:

[0033] In terms of overall architecture design, such as Figure 1 As shown, the entire system adopts a layered design with three-sided decoupling:

[0034] The management plane module is responsible for policy generation, cluster member management, topology reconstruction, and task scheduling decisions. It issues control policies to the control plane via the northbound interface.

[0035] The control plane module consists of a cluster of multiple controller nodes, which work with a distributed state synchronization component to achieve state consistency and master switching, and exchange state information through an east-west interface.

[0036] The data plane module consists of virtual switches on each terminal node, which are responsible for performing data forwarding and local control, and receive control commands through the southbound interface.

[0037] The system achieves multi-layered collaboration through northbound, eastbound, and southbound interfaces, ensuring that management, control, and forwarding are independent yet closely linked.

[0038] In the specific implementation of the management module's functions, the management module serves as the highest decision-making layer of the system, and its overall dynamic management process is as follows: Figure 2 As shown, the specific process includes the following:

[0039] Global topology generation and maintenance involves real-time collection of data such as the location of cluster nodes and link quality, and the use of a weighted link evaluation algorithm to dynamically generate and update the network topology.

[0040] Cluster members are managed dynamically, adjusting their affiliation based on parameters such as node location and link status, and performing cluster head election and replacement.

[0041] Intelligent decision-making, based on preset strategies and environmental perception, intelligently formulates strategies such as traffic scheduling and fault recovery, and issues commands to the control plane through the northbound interface.

[0042] The control plane module is the command and execution layer of the system. The specific functions of the control plane module include:

[0043] Controller cluster construction involves deploying multiple ONOS controller nodes (e.g., controller 1 to controller N), such as... Figure 3 As shown, each node synchronizes its state through the east-west interface based on the distributed consensus Raft protocol.

[0044] The distributed state maintenance and master switch mechanism uses Atomix components as state management middleware to ensure that the cluster can quickly complete the master role transfer when the controller node fails.

[0045] Flow table distribution and dynamic updates: Based on the strategy issued by the management plane, flow table rules are published to the data plane nodes under its jurisdiction to achieve dynamic optimization and forwarding of data flows.

[0046] In the specific implementation of the data plane module, the data plane module serves as the execution layer for the actual carrying and forwarding of task data, and its specific functions are as follows:

[0047] Virtual switch deployment and management: embedding containerized OpenvSwitch (OVS) virtual switches in various cutting-edge devices (such as drones and ground stations).

[0048] The local autonomous control mechanism allows nodes to make temporary autonomous decisions based on pre-configured rules downloaded locally when they lose contact with the control plane, ensuring that the local link is not interrupted.

[0049] Efficient data forwarding and link status monitoring; real-time matching of flow tables for data forwarding; and periodic reporting of link statistics (such as port packet loss rate and bandwidth usage) to support dynamic optimization of the control plane.

[0050] Among them, distributed and centralized collaboration mechanisms are implemented, such as Figure 2 As shown, this invention establishes a logically unified virtual control plane by deploying distributed collaborative components within the control plane, specifically implemented as follows:

[0051] Local autonomous management allows each controller to independently maintain the resources of its assigned cluster, autonomously schedule traffic, and update forwarding tables.

[0052] Global consistency maintenance involves periodically synchronizing node status, link information, and policy execution status among controllers to ensure consistent status across the entire network.

[0053] Joint task fragmentation and execution: When a cross-cluster task is received, the management plane breaks down the overall task strategy into local execution fragments, which are distributed and executed by different controllers, and cross-cluster collaboration is completed through control plane logic bridging.

[0054] For example, in a multi-cluster collaborative strike mission, controller 1 is responsible for path planning, and controller 2 is responsible for link assurance. The two share data through a consistent state pool to ensure precise synchronization of collaborative actions.

[0055] In the process of survivability design and implementation, in order to cope with highly aggressive environments, the embodiment of the present invention specifically designs a dual redundancy survivability mechanism:

[0056] Control plane module primary / backup cluster head switching: When a cluster head node fails, the system elects a new cluster head based on parameters such as node energy and location information in a weighted manner to ensure that the control logic is not interrupted.

[0057] Data plane module path reconstruction and failover: When a cluster goes out of control due to a controller or link failure, the adjacent controller can automatically take over the switch resources, replan the traffic path, and complete the lossless data migration.

[0058] In the interface design and implementation, to achieve efficient interaction and task collaboration between the management plane, control plane, and data plane, this embodiment of the invention designs and implements three types of interfaces: northbound interface, eastbound interface, and southbound interface, specifically including:

[0059] The northbound interface adopts the RESTful API standard to enable policy distribution and status query between the management plane and the control plane. The management plane can dynamically adjust network policies, such as cluster head election parameters and resource allocation schemes, and transmit them to the controller cluster in real time via API, improving task adaptability.

[0060] The controller cluster uses an east-west interface based on the Raft protocol for state synchronization and logical consistency maintenance. Controller nodes periodically synchronize link status, load information, and fault warnings to ensure consistent status across the entire network and enable rapid master switchover and task takeover in the event of a single point of failure.

[0061] The control plane connects to the data plane via a southbound interface and uses the OpenFlow 1.3 protocol to control the virtual switches, enabling flow table management, path optimization, and link monitoring. It supports real-time adjustment of forwarding policies based on task priority, ensuring priority transmission of critical data flows and link reliability.

[0062] Through the collaborative design of the above three types of interfaces, the system achieves multi-layer decoupling and efficient linkage, improving the overall architecture's flexibility, scalability, and task adaptability.

[0063] The technical effects of the embodiments of the present invention are verified as follows:

[0064] Build a simulation platform to verify performance.

[0065] like Figure 4 As shown, the simulation platform built using the ONOS controller includes:

[0066] 3-node controller cluster deployment: Synchronizes state through Atomix module, supports master election and consistency maintenance.

[0067] Virtual switch deployment: 27 OVS nodes simulate a drone networking environment and support dynamic topology changes.

[0068] Incident injection test: Introduce node failure, link breakage and high load traffic to test the system's response capability and recovery speed.

[0069] Simulation results show that the architecture of this invention can maintain high consistency and fast recovery capability under node failure and high load conditions, significantly improve link utilization and data transmission performance, and has good task adaptability and system resilience.

[0070] The units described in the embodiments of the present invention can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0071] According to one aspect of the present invention, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and executes the computer instructions, causing the computer device to perform the methods provided in the various optional implementations described above.

[0072] In another aspect, embodiments of the present invention also provide a computer-readable medium, which may be included in the electronic device described in the above embodiments; or it may exist independently and not assembled into the electronic device. The computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to perform the methods described in the above embodiments.

Claims

1. A method for implementing a three-sided decoupled software-defined wireless ad hoc network and containerization, characterized in that, include: Step one introduces a three-plane decoupled hybrid SDN architecture design, establishing a management plane module, a control plane module, and a data plane module to separate the functions of policy decision-making, centralized control, and data forwarding. The management plane module is responsible for global policy formulation and decision-making, generating network topology, managing cluster members, executing primary / backup cluster head election, and maintaining the controller cluster. It issues policies and configuration commands to the control plane module via the northbound interface. The control plane module includes multiple controller nodes, which achieve state synchronization and consistency maintenance through distributed collaborative components. The controller nodes exchange link status, node load, and threat information through the eastbound and westbound interfaces, supporting local autonomy and network-wide collaboration. The data plane module includes virtual switches deployed in each node device. These virtual switches receive control commands and execute data forwarding rules through the southbound interface, ensuring data flow timeliness and enabling autonomous execution of local policies. The northbound, eastbound / westbound, and southbound interfaces achieve functional decoupling and interaction between the management plane module, control plane module, and data plane module. Step 2: Introduce a robust design and set up a primary / backup cluster head switching mechanism in the control plane module. When the primary cluster head node fails, a new cluster head node is elected based on a weighted average of node energy, location, and historical load parameters, and intra-cluster scheduling is restored.

2. The method for implementing a three-sided decoupled software-defined wireless ad hoc network and containerization according to claim 1, characterized in that, The northbound interface specifically adopts the RESTful API standard, is implemented based on the HTTP protocol, and supports the dynamic injection of policy distribution, control parameter configuration, task priority adjustment, and fault recovery policies.

3. The three-sided decoupled software-defined wireless ad hoc network and containerized implementation method according to any one of claims 1 or 2, characterized in that, The northbound interface is equipped with a modular expansion mechanism to accommodate the data interaction needs of cloud orchestration platforms and artificial intelligence inference engines.

4. The method for implementing a three-sided decoupled software-defined wireless ad hoc network and containerization according to claim 1, characterized in that, The east-west interface is specifically built on the Raft consensus protocol. The controller node periodically synchronizes its own state information through the east-west interface built on the Raft consensus protocol. When the heartbeat failure of any node is detected, the master node election and control takeover process is triggered.

5. The method for implementing a three-sided decoupled software-defined wireless ad hoc network and containerization according to claim 1, characterized in that, The southbound interface is specifically implemented using the OpenFlow 1.3 protocol, which supports dynamic distribution of flow tables, port monitoring, traffic path adjustment, and priority scheduling rule configuration for virtual switches.

6. The method for implementing a three-sided decoupled software-defined wireless ad hoc network and containerization according to claim 1, characterized in that, The controller cluster specifically constructs a global information pool through an east-west interface. The global information pool includes link quality status, node load, resource allocation, and threat detection information.

7. The method for implementing a three-sided decoupled software-defined wireless ad hoc network and containerization according to claim 1, characterized in that, The virtual switch is pre-configured with local control policies. When the control plane module connection is lost, traffic forwarding and path selection continue according to the pre-configured local control policies to ensure that local communication is not interrupted.

Images