A space-based network edge microservice distributed orchestration system and method

Abstract

The present invention relates to a distributed orchestration system and method for space-based network edge microservices, including a K8S controller and an ODL controller; the K8S controller and the ODL controller are both in a management and control plane, the southbound interfaces of the K8S controller and the ODL controller are respectively connected to a data plane, and the northbound interfaces of the K8S controller and the ODL controller are respectively connected to an application plane; the ODL controller is used to issue flow tables and allocate link bandwidth to the K8S controllers it controls; the K8S controller is used to orchestrate and deploy microservice components required by users to target nodes, and to perform actual deployment and reconfigure operation tasks on the deployed microservice components, and to determine the deployment location of the microservice components in the data plane, the resource allocation amount of the microservice components, the flow table configuration of the entire network, and the bandwidth allocation between nodes; the application plane is used to generate user task requirements and generate orchestration results. The present invention can be widely used in the field of distributed lightweight orchestration.

Description

Technical Field

[0001] The present invention relates to the field of distributed lightweight orchestration in space-based network edge computing scenarios, and in particular to a space-based network edge microservice distributed orchestration system and method based on a microservice architecture. Background Art

[0002] With the rapid development of the Internet, a large number of emerging service applications, such as virtual reality (VR), augmented reality, and interactive games, have emerged at the edge of the network, resulting in an explosive growth in the demand for edge services and edge businesses. On the other hand, due to the rapid development of satellite networks, the traditional satellite network, which only serves as an information transmission pipeline, has seriously hindered the rapid development of satellite networks and is difficult to apply to the aforementioned emerging massive edge service applications with low latency requirements. Therefore, satellites mobile edge computing (Satellites MEC) has emerged. This computing method sinks the computing power of the cloud center to the edge of the space-based network (such as satellite nodes, satellite base station nodes, and other edge network nodes), and provides physical resources such as computing, storage, and bandwidth at the edge of the network to achieve the purpose of providing services on the user side, thereby ensuring the deterministic delivery of latency-sensitive services.

[0003] To meet these requirements, existing approaches deploy general-purpose servers on base stations or satellites, running the microservices required by users within these servers to ensure the smooth execution of user tasks. To ensure the robust operation of intelligent agents, open-source software such as OpenDaylight (ODL), Kubernetes (K8S), K3S, and KubeEdge have been introduced into space-based edge networks.

[0004] However, in existing technologies, the ODL controller is responsible for maintaining and managing the network topology. While this controller has the advantages of facilitating network scalability and centralized control of the network topology, it also has drawbacks, such as instability caused by single node failures. While the K8S controller ensures automated microservices operations and provides a stable operating environment, its drawback is that it is difficult to scale the network. Summary of the Invention

[0005] In response to the problems that the network built with the above-mentioned ODL software lacks stability and the network built with Kubernetes software is difficult to expand the network scale, the purpose of the present invention is to provide a large-scale and lightweight distributed orchestration system and method for space-based network edge microservices.

[0006] To achieve the above objectives, the present invention adopts the following technical solutions: In a first aspect, a space-based network edge microservice distributed orchestration system is provided, including a K8S controller and an ODL controller;

[0007] The K8S controller and the ODL controller are both in the management and control plane. The southbound interfaces of the K8S controller and the ODL controller are respectively connected to the data plane, and the northbound interfaces of the K8S controller and the ODL controller are respectively connected to the application plane;

[0008] The data plane is used to store the underlying network topology, deployment status of microservice components, physical resource information, and user request information;

[0009] The ODL controller is used to issue flow tables and allocate link bandwidth to the K8S controller it controls, providing underlying physical topology support for the K8S controller;

[0010] The K8S controller is used to orchestrate and deploy the microservice components required by the user to the target node, and to perform actual deployment and reconfiguration of operation tasks on the deployed microservice components based on the user task requirements and orchestration results sent by the application plane. Based on the physical topology support of the ODL controller, it determines the deployment location of the microservice components in the data plane, the resource allocation of the microservice components, the flow table configuration of the entire network, and the bandwidth allocation between nodes;

[0011] The application plane is used to generate user task requirements and generate an orchestration result according to the physical resource information and user request information of the data plane.

[0012] Furthermore, the K8S controller is deployed in the general server corresponding to each base station, and the ODL controller is deployed in the container of the K8S controller deployed on some of the general servers.

[0013] Furthermore, the control plane is also provided with:

[0014] An onboard control manager, configured to determine the deployment locations of microservice components in the data plane, resource allocation for microservice components, network-wide flow table configuration, and bandwidth allocation between nodes based on the physical topology support of the ODL controller;

[0015] The onboard service scheduler is set in each newly created container or unscheduled container to orchestrate and deploy the microservice components required by the user to the target node and select the optimal node to run the container;

[0016] The lifecycle manager is used to perform actual deployment and reconfigure operation tasks for the deployed microservice components according to the user task requirements and orchestration results sent by the application plane, and manage the lifecycle of each container.

[0017] Furthermore, the deployment within the data plane also includes an OpenFlow switch for communication between the ODL controller and the forwarder.

[0018] Furthermore, the OpenFlow switch includes a physical switch and a virtual switch.

[0019] Furthermore, the control plane is also provided with:

[0020] A topology manager, configured to manage the topological connection relationships between the OpenFlow switches;

[0021] The network flow table is used to ensure the forwarding of user service data flows processed by the OpenFlow switch and the bandwidth allocation of network links.

[0022] Furthermore, the deployment in the data plane includes:

[0023] Based on the instructions of the K8S controller, the image file is pulled from the cloud image center, deployed at the edge of the space-based network, and a pod container is created to run the image file and start the space-based microservice to meet the computing needs of the edge of the space-based network.

[0024] In a second aspect, a distributed orchestration method for space-based network edge microservices is provided, including:

[0025] Deploy the K8S controller in the general server corresponding to each base station, and deploy the ODL controller in the container of the K8S controller deployed on some general servers;

[0026] The data plane stores the underlying network topology, deployment status of microservice components, physical resource information, and user request information;

[0027] The ODL controller manages network topology and controls bandwidth between links, sends flow tables to the managed K8S controllers, and allocates link bandwidth.

[0028] The K8S controller sends the data stored in the data plane to the application plane. The application plane generates an orchestration result based on the physical resource information of the data plane and the user request information, and sends it to the K8S controller.

[0029] The K8S controller reconfigures the data plane based on user task requirements and orchestration results, and based on the physical topology support of the ODL controller, determines the deployment location of microservice components in the data plane, the resource allocation of microservice components, the flow table configuration of the entire network, and the bandwidth allocation between nodes.

[0030] In a third aspect, a processing device is provided, comprising computer program instructions, wherein the computer program instructions, when executed by the processing device, are used to implement the steps corresponding to the above-mentioned distributed orchestration method of space-based network edge microservices.

[0031] In a fourth aspect, a computer-readable storage medium is provided, on which computer program instructions are stored, wherein the computer program instructions, when executed by a processor, are used to implement the steps corresponding to the above-mentioned distributed orchestration method of space-based network edge microservices.

[0032] The present invention has the following advantages due to the adoption of the above technical solution:

[0033] 1. The present invention is based on the automated operation and maintenance capabilities of the Kubernetes controller to make up for the single-node failure problem of the ODL controller. At the same time, based on the topological connection function of the underlying network of the ODL controller, it opens up the connection channels between nodes for the Kubernetes controller and expands the cluster scale of the Kubernetes controller. The present invention can give full play to the advantages of the Kubernetes controller and the ODL controller to build a highly available, large-scale distributed orchestration architecture for space-based edge networks. This architecture can quickly and in real time orchestrate microservice applications according to user task requirements, quickly deploy services, and provide a highly reliable and highly concurrent cluster-compatible operating environment.

[0034] 2. Considering the limited resources of satellite nodes, the size of the resources occupied by the orchestration system has become an important consideration for the implementation of orchestration technology in space-based scenarios. The present invention uses the Kubernetes controller and the ODL controller as the system environment to build a distributed lightweight orchestration architecture and device that can be applied to space-based edge scenarios. Since the two software are based on the general Linux operating system and the resources they occupy are within an acceptable range. Therefore, the software combination proposed in the present invention is suitable for space-based network orchestration platforms, especially in the scenario of space-based multi-domain edge networks, it can quickly and in real time orchestrate microservices according to user task requirements, quickly deploy services and provide lightweight and stable operating scenarios.

[0035] 3. The ODL controller in the present invention can perform the functions of adding, deleting, changing and retrieving all physical nodes and virtual nodes in the network, and configure SDN flow tables for nodes, regulate routing paths and achieve load balancing. Moreover, the network topology structure in the present invention can be built based on both physical switches and virtual switches at the same time, which is extremely flexible.

[0036] In summary, the present invention can be widely used in the field of distributed lightweight orchestration in space-based network edge computing scenarios. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Various other advantages and benefits will become apparent to those skilled in the art upon reading the detailed description of the preferred embodiment below. The accompanying drawings are for illustration purposes only and are not to be considered as limiting the present invention. Throughout the drawings, the same reference numerals are used to denote the same components. In the drawings:

[0038] Figure 1 This is a schematic diagram of the application scenario and logical architecture provided by an embodiment of the present invention;

[0039] Figure 2 This is a schematic diagram of a distributed system architecture provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0040] Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present invention are shown in the accompanying drawings, it should be understood that the present invention can be implemented in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of the present invention and to fully convey the scope of the present invention to those skilled in the art.

[0041] It should be understood that the terms used herein are for the purpose of describing specific example embodiments only and are not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms "one", "an" and "said" as used herein may also be meant to include plural forms. The terms "comprise", "include", "contain" and "have" are inclusive and therefore specify the presence of stated features, steps, operations, elements and / or parts, but do not exclude the presence or addition of one or more other features, steps, operations, elements, parts, and / or combinations thereof. The method steps, processes, and operations described herein are not to be construed as necessarily requiring them to be performed in the specific order described or illustrated, unless the order of execution is clearly indicated. It should also be understood that additional or alternative steps may be used.

[0042] Although the terms first, second, third, etc. can be used in the text to describe multiple elements, components, regions, layers and / or sections, these elements, components, regions, layers and / or sections should not be limited by these terms. These terms can only be used to distinguish an element, component, region, layer or section from another region, layer or section. Unless the context clearly indicates otherwise, terms such as "first", "second" and other numerical terms do not imply order or sequence when used in the text. Therefore, the first element, component, region, layer or section discussed below can be referred to as the second element, component, region, layer or section without departing from the teaching of the example embodiments.

[0043] like Figure 1As shown in the figure, the application scenario and logical architecture of the distributed orchestration system and method of the edge microservices of the space-based network of the present invention are composed of the following: the lower part shows the physical topology connection of the edge network. The physical topology is interconnected with the base station (satellite base station) as the core. A general server is placed next to each base station, and a K8S controller and an ODL controller are deployed in the general server (the ODL controller is only deployed in the base station with the shadow). All base station nodes are interconnected via satellite. The physical topology after the controller is deployed can be abstracted as Figure 1 In the logical architecture of the upper part, the ODL controller is responsible for network topology management and inter-link bandwidth control. However, the ODL controller has limited stability. If a single node fails, it will affect the network, which is an inherent drawback of the ODL controller. The Kubernetes controller is responsible for controlling and orchestrating the intelligent agent. Through health checks, self-healing, automatic rescheduling, application scaling, and rolling upgrades, it ensures that application services provide stable services to users. The core control node of Kubernetes is the master node, and all slave nodes (worker nodes) are centrally controlled by the master node. The intelligent agent that provides services to users is deployed in pods (containers), and the containers run on the master node. The master node can view and orchestrate all containers, implementing the top-level orchestration logic. However, the Kubernetes controller's container orchestration services require connectivity to the underlying physical network. This drawback limits the Kubernetes controller's scalability.

[0044] In order to solve the problem of insufficient stability of the ODL controller due to single node failure and the limitations of the K8S controller in terms of usage scale, considering the complementarity of the two and the rigid needs of the industry, the present invention proposes a stable, lightweight and highly reliable distributed orchestration system and method for space-based network edge microservices in edge computing scenarios, especially space-based edge computing scenarios, which fully utilizes the manageable and controllable characteristics of large-scale networks of ODL software and the automated operation and maintenance and stable characteristics of Kubernetes software, and realizes lightweight and stable operation and maintenance in large-scale space-based edge network scenarios by taking advantage of their strengths and overcoming their weaknesses. The core process is as follows: First, use the ODL controller to connect the underlying physical network to provide underlying protection for the K8S controller to control the main node; second, place the ODL controller in the container of the K8S controller, and use the health check and automatic rescheduling of the K8S controller to ensure the stable operation of the ODL controller to avoid the single-node failure problem of the SDN controller; finally, this architecture can use the northbound interface of the K8S controller and the ODL controller to provide real-time feedback on the network status and intelligent agent operation status to the top-level application and algorithm orchestration module, providing the bottom-level physical topology protection and stable operation guarantee of the application business for the top-level orchestration algorithm.

[0045] Example 1

[0046] like Figure 2 As shown, this embodiment provides a space-based network edge microservice distributed orchestration system, including a K8S controller and an ODL controller.

[0047] Both the K8S controller and the ODL controller are deployed on the control plane. Their southbound interfaces connect to the data plane, enabling basic control of underlying data. Their northbound interfaces connect to the application plane, providing real-time feedback on the underlying network topology and intelligent agent deployment.

[0048] The data plane is used to store data such as the underlying network topology, deployment status of microservice components, physical resource information, and user request information.

[0049] The ODL controller on the control plane is used to manage network topology and control bandwidth between links. It sends flow tables and allocates link bandwidth to the managed K8S controller, providing underlying physical topology support for the K8S controller.

[0050] The K8S controller of the management and control plane is used to orchestrate and deploy the microservice components required by users to the target nodes to respond to edge user needs. In addition, the K8S controller is also used to perform health checks, automatic rescheduling, and rolling upgrades on the deployed microservice components based on the user task requirements and orchestration results sent by the application plane. Reconfigure actual deployment and operation tasks, and based on the physical topology support of the ODL controller, determine the deployment location of the microservice components in the data plane, the resource allocation of the microservice components, the flow table configuration of the entire network, and the bandwidth allocation between nodes, etc., to ensure that the application business provides stable services to users.

[0051] The application plane is used to generate user task requirements and generate orchestration results based on the physical resource information and user request information of the data plane, that is, the deployment results of microservice components and their resource allocation results.

[0052] In a preferred embodiment, the deployment in the data plane includes:

[0053] Based on the instructions of the K8S controller, the image file is pulled from the cloud image center, deployed at the edge of the space-based network, and a pod container is created to run the image file and start the space-based microservice to meet the computing needs of the space-based network edge. Because the K8S controller has automated operation and maintenance functions, the present invention can achieve stable operation.

[0054] In a preferred embodiment, the deployment in the data plane further includes: an OpenFlow switch, which serves as a basic network node and is used for communication between the ODL controller and the forwarder.

[0055] Specifically, the OpenFlow switch includes a physical switch and a virtual switch, both of which are used for data exchange. The present invention can support both physical exchange and virtual exchange capabilities.

[0056] In a preferred embodiment, a K8S controller is deployed within the general-purpose server corresponding to each base station, assuming the functions of both a master node and a slave node. This means that each general-purpose server exists independently as a master node, adding its neighboring nodes as slave nodes, and is also managed as a slave node by the master node of its neighboring nodes. Therefore, each general-purpose server can manage the operation of microservice components within a certain range (including on-demand migration, health checks, fault repair, and resource allocation of microservice components).

[0057] In a preferred embodiment, an ODL controller is deployed within the container of the K8S controller deployed on some general-purpose servers. This controller issues flow tables and allocates link bandwidth to the nodes it manages, ensuring connectivity of the underlying network topology. The ODL controller, located within the K8S controller, is hosted and operated by the K8S controller. This is because the K8S controller's automated operation and maintenance capabilities effectively prevent single-node failures and other faults, thus providing an environmental foundation for the stable operation of the ODL controller and ensuring high network availability.

[0058] In a preferred embodiment, the management and control plane is further provided with an onboard control manager, an onboard service scheduler and a lifecycle manager.

[0059] The onboard control manager is used to support the physical topology of the ODL controller, determine the deployment location of microservice components in the data plane, the resource allocation of microservice components, the flow table configuration of the entire network, and the bandwidth allocation between nodes, etc., to ensure that the actual status of each resource in the container (Pod) cluster built by the K8S controller is consistent with the user-defined expected status.

[0060] The onboard service scheduler is set in each newly created container or unscheduled container to orchestrate and deploy the microservice components required by the user to the target node and select the optimal node to run the container.

[0061] The lifecycle manager is used to reconfigure actual deployment and operation tasks such as health checks, automatic rescheduling, and rolling upgrades of deployed microservice components based on user task requirements and orchestration results sent by the application plane. It manages the lifecycle of each container, promptly deletes expired containers and adds valid containers, and manages the container lifecycle in real time.

[0062] In a preferred embodiment, a topology manager and a network flow table are also provided in the control plane.

[0063] As one of the core modules of the control plane, the topology manager is used to manage the topological connection relationships between OpenFlow switches (including physical switches and virtual switches), dynamically generate logical connections in the network topology, and ensure the connectivity and reliability of the underlying network.

[0064] The network flow table is the most important table in OpenFlow. It is used to ensure that the OpenFlow switch can smoothly handle the regular forwarding function of user business data flow, ensure the correct forwarding location and forwarding rate, that is, ensure the correct forwarding of user business data flow and the bandwidth allocation of network links.

[0065] The OpenFlow switch, topology manager and network flow table jointly implement network topology management, data routing and bandwidth control between links.

[0066] In a preferred embodiment, the application plane is user-oriented and user-defined. Specifically, for example, the application plane can perform data driving, algorithm management, data management, task threads, and application requirements.

[0067] Example 2

[0068] This embodiment provides a distributed orchestration method for space-based network edge microservices, including the following steps:

[0069] 1) Deploy the K8S controller in the general server corresponding to each base station, and deploy the ODL controller in the container of the K8S controller deployed on some general servers.

[0070] 2) The data plane stores data such as the underlying network topology, deployment status of microservice components, physical resource information, and user request information.

[0071] 3) The ODL controller manages the network topology and controls the bandwidth between links, and sends flow tables and allocates link bandwidth to the managed K8S controllers.

[0072] 4) The K8S controller sends the data stored in the data plane to the application plane. The application plane generates an orchestration result based on the physical resource information of the data plane and the user request information, and sends it to the K8S controller.

[0073] 5) User task requirements are customized by the user in the application plane and sent to the K8S controller.

[0074] 6) The K8S controller reconfigures the actual deployment and operation tasks such as health checks, automatic rescheduling and rolling upgrades of the data plane based on user task requirements and orchestration results. Based on the physical topology support of the ODL controller, it determines the deployment location of the intelligent agent in the data plane, the resource allocation of the intelligent agent, the flow table configuration of the entire network, and the bandwidth allocation between nodes.

[0075] Example 3

[0076] This embodiment provides a processing device corresponding to the distributed orchestration method of space-based network edge microservices provided in this embodiment 2. The processing device can be applicable to a client processing device, such as a mobile phone, laptop computer, tablet computer, desktop computer, etc., to execute the method of embodiment 2.

[0077] The processing device includes a processor, memory, a communication interface, and a bus. The processor, memory, and communication interface are connected via the bus to facilitate communication between them. The memory stores a computer program executable on the processing device. When the processing device executes the computer program, it executes the distributed orchestration method for space-based network edge microservices provided in Example 2.

[0078] In some implementations, the memory may be a high-speed random access memory (RAM), and may also include a non-volatile memory, such as at least one disk storage.

[0079] In other implementations, the processor may be a central processing unit (CPU), a digital signal processor (DSP), or other general-purpose processors, which are not limited herein.

[0080] In addition, the logical instructions in the above-mentioned memory can be implemented in the form of a software functional unit and can be stored in a computer-readable storage medium when sold or used as an independent product. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0081] Those skilled in the art will understand that the structure of the above-mentioned computing device is only a partial structure related to the solution of the present application, and does not constitute a limitation on the computing device to which the solution of the present application is applied. The specific computing device may include more or fewer components, or combine certain components, or have a different component arrangement.

[0082] Example 4

[0083] This embodiment provides a computer program product corresponding to the distributed orchestration method of space-based network edge microservices provided in this embodiment 2. The computer program product may include a computer-readable storage medium carrying computer-readable program instructions for executing the distributed orchestration method of space-based network edge microservices described in this embodiment 2.

[0084] Computer readable storage media can be tangible devices that hold and store instructions used by instruction execution devices. Computer readable storage media can be, for example, but not limited to, electronic storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any combination thereof.

[0085] The above embodiment provides a computer-readable storage medium, whose implementation principle and technical effects are similar to those of the above method embodiment, and will not be repeated here.

[0086] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the steps in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0087] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0088] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0089] The above embodiments are only used to illustrate the present invention, wherein the structure, connection mode and manufacturing process of each component can be changed. Any equivalent transformations and improvements based on the technical solution of the present invention should not be excluded from the scope of protection of the present invention.

Claims

1. A space-based network edge microservice distributed orchestration system, characterized by: Including K8S controller and ODL controller; The K8S controller and the ODL controller are both in the management and control plane. The southbound interfaces of the K8S controller and the ODL controller are respectively connected to the data plane, and the northbound interfaces of the K8S controller and the ODL controller are respectively connected to the application plane; The data plane is used to store the underlying network topology, deployment status of microservice components, physical resource information, and user request information; The ODL controller is used to issue flow tables and allocate link bandwidth to the K8S controller it controls, providing underlying physical topology support for the K8S controller; The K8S controller is used to orchestrate and deploy the microservice components required by the user to the target node, and to perform actual deployment and reconfiguration of operation tasks on the deployed microservice components based on the user task requirements and orchestration results sent by the application plane. Based on the physical topology support of the ODL controller, it determines the deployment location of the microservice components in the data plane, the resource allocation of the microservice components, the flow table configuration of the entire network, and the bandwidth allocation between nodes; The application plane is used to generate user task requirements and generate an orchestration result according to the physical resource information and user request information of the data plane.

2. A space-based network edge microservice distributed orchestration system according to claim 1, characterized in that: The K8S controller is deployed in the general server corresponding to each base station, and the ODL controller is deployed in the container of the K8S controller deployed on some of the general servers.

3. A space-based network edge microservice distributed orchestration system as claimed in claim 2, characterized in that: The control plane is also provided with: An onboard control manager, configured to determine the deployment locations of microservice components in the data plane, resource allocation for microservice components, network-wide flow table configuration, and bandwidth allocation between nodes based on the physical topology support of the ODL controller; The onboard service scheduler is set in each newly created container or unscheduled container to orchestrate and deploy the microservice components required by the user to the target node and select the optimal node to run the container; The lifecycle manager is used to perform actual deployment and reconfigure operation tasks for the deployed microservice components according to the user task requirements and orchestration results sent by the application plane, and manage the lifecycle of each container.

4. A space-based network edge microservice distributed orchestration system as claimed in claim 2, characterized in that: The deployment within the data plane also includes an OpenFlow switch for communication between the ODL controller and the forwarder.

5. A space-based network edge microservice distributed orchestration system according to claim 4, characterized in that: The OpenFlow switch includes a physical switch and a virtual switch.

6. A space-based network edge microservice distributed orchestration system as claimed in claim 4, characterized in that: The control plane is also provided with: A topology manager, configured to manage the topological connection relationships between the OpenFlow switches; The network flow table is used to ensure the forwarding of user service data flows processed by the OpenFlow switch and the bandwidth allocation of network links.

7. A space-based network edge microservice distributed orchestration system according to claim 1, characterized in that: The deployment in the data plane includes: Based on the instructions of the K8S controller, the image file is pulled from the cloud image center, deployed at the edge of the space-based network, and a pod container is created to run the image file and start the space-based microservice to meet the computing needs of the edge of the space-based network.

8. A distributed orchestration method for space-based network edge microservices, characterized in that: include: Deploy the K8S controller in the general server corresponding to each base station, and deploy the ODL controller in the container of the K8S controller deployed on some general servers; The data plane stores the underlying network topology, deployment status of microservice components, physical resource information, and user request information; The ODL controller manages network topology and controls bandwidth between links, sends flow tables to the managed K8S controllers, and allocates link bandwidth. The K8S controller sends the data stored in the data plane to the application plane. The application plane generates an orchestration result based on the physical resource information of the data plane and the user request information, and sends it to the K8S controller. The K8S controller reconfigures the data plane based on user task requirements and orchestration results, and based on the physical topology support of the ODL controller, determines the deployment location of microservice components in the data plane, the resource allocation of microservice components, the flow table configuration of the entire network, and the bandwidth allocation between nodes.

9. A processing device, characterized in that The method comprises computer program instructions, wherein when the computer program instructions are executed by a processing device, they are used to implement the steps corresponding to the method for distributed orchestration of space-based network edge microservices according to claim 8.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer program instructions, wherein the computer program instructions, when executed by the processor, are used to implement the steps corresponding to the distributed orchestration method of space-based network edge microservices described in claim 8.

Images