Satellite-based cloud network scheduling method and device and satellite-based computing power node

Abstract

The application provides a scheduling method and device of a space-based cloud network and a space-based computing node. The method comprises the following steps: based on at least one network subdomain, obtaining announcement information sent by a space-based computing node in the network subdomain; constructing a first information table according to the announcement information; the first information table comprises information of a plurality of space-based computing nodes; and performing user task processing or according to a user request and the first information table. Therefore, the network can better adapt to the characteristics of limited space resources and large space-time scales, and the overhead caused by frequent updates due to network dynamics is reduced to a certain extent.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to a scheduling method, apparatus, and space-based computing node for a space-based cloud network. Background Technology

[0002] The space-ground integrated network is a heterogeneous network spanning a large spatiotemporal scale, and with technological advancements, the processing capabilities of nodes on satellites are now comparable to those on the ground. Therefore, satellite resources can be utilized to provide onboard processing services. Consequently, space-based clouds, composed of space-based computing nodes, have emerged.

[0003] Due to the large spatiotemporal scale characteristics of space nodes, space-based cloud nodes can provide various network functions, namely: a node can provide access functions (with Radio Access Network (RAN) type functions), network data plane functions (user plane functions similar to UPF), and service functions (data network (DN) type functions).

[0004] Space-based cloud can solve scenarios where there are no network and computing resources on the ground. It can schedule services to space-based edge cloud, which can collaborate with other space-based computing nodes on the edge or network to provide ubiquitous solutions and achieve relatively deterministic latency.

[0005] However, space-based clouds differ fundamentally from terrestrial clouds. First, the topology of space networks is highly dynamic; low-Earth orbit satellites experience high-speed relative motion with the ground and with each other, resulting in space-based clouds being composed of nodes with dynamically changing topologies. Second, space networks span large spatiotemporal scales, leading to large distances between nodes in space-based clouds, making centralized deployment difficult. Furthermore, the computing power of a single node in a space-based network is still limited, necessitating careful consideration of various resource conditions, including bandwidth and computing resources.

[0006] However, existing technologies mainly define methods for scheduling computing resources on the ground, without considering the characteristics of space-ground integrated networks. Summary of the Invention

[0007] The purpose of this invention is to provide a scheduling method, device, and space-based computing power node for a space-based cloud network, so as to solve the problem that existing computing power resource scheduling methods do not take into account the characteristics of space-ground integrated networks.

[0008] To address the aforementioned problems, embodiments of the present invention provide a scheduling method for a space-based cloud network, executed by a first node, comprising:

[0009] Based on at least one network subdomain, obtain the notification information sent by the space-based computing power nodes within the network subdomain;

[0010] Based on the announcement information, a first information table is constructed; the first information table includes information on multiple space-based computing power nodes.

[0011] Based on the user request and the first information table, perform user task processing or scheduling.

[0012] The first information table is a network node status information table, which includes at least one of the following: node computing power information, network information, service information, and link status information.

[0013] The first node is a space-based computing power node with communication capabilities and computing and storage capabilities. This space-based computing power node is a basic component of the space-based cloud.

[0014] Wherein, the at least one network subdomain includes:

[0015] The network subdomain to which the first node belongs;

[0016] And / or,

[0017] The network subdomain to which the space-based computing power node with a hop count less than or equal to the first threshold belongs.

[0018] Specifically, based on at least one network subdomain, the notification information sent by the space-based computing power nodes within that subdomain is obtained, including:

[0019] The system receives announcement information broadcast by each space-based computing node within the at least one network subdomain; the announcement information includes at least one of the following: the address of the space-based computing node, the type of computing service that the space-based computing node can provide, the network resources of the space-based computing node, and the computing resources of the space-based computing node.

[0020] Where the space-based cloud network supports location addressing, the information of a space-based computing node in the first information table includes:

[0021] The address of the space-based computing node;

[0022] The reachability time between the space-based computing node and the first node;

[0023] The network resources of the space-based computing nodes;

[0024] The computing resources of the space-based computing nodes.

[0025] Where the space-based cloud network does not support location addressing, the information of a space-based computing node in the network node status information includes:

[0026] The address of the space-based computing node;

[0027] The reachability time between the space-based computing node and the first node;

[0028] The path information of the space-based computing nodes.

[0029] The method further includes:

[0030] Based on the address and ephemeris information of the space-based computing node, the reachability time between the space-based computing node and the first node is determined.

[0031] Before performing task processing or scheduling based on the user request and the first information table, the method further includes:

[0032] Receive a first request sent by the user, the first request carrying the type of computing power service requested by the user and the expected service level agreement (SLA) requirements.

[0033] The step of processing or scheduling tasks based on user requests and the first information table includes:

[0034] Based on the first request, determine whether the first node can provide the type of computing power service required by the user, and whether it meets the user's expected SLA requirements;

[0035] If the first node is able to provide the computing power service type required by the user and can meet the user's expected SLA requirements, the first node processes the user's task according to the first request and feeds back the processing result to the user.

[0036] Alternatively, the first node may look up the first information table and schedule the user task to at least one space-based computing power node. Or, if the first node is unable to provide the type of computing power service required by the user or cannot meet the user's expected SLA requirements, the first node may look up the first information table and schedule the user task to at least one space-based computing power node.

[0037] The first node searches the first information table and schedules the user task to at least one space-based computing power node, including:

[0038] Based on the first request, space-based computing power nodes that cannot provide the computing power service type required by the user and space-based computing power nodes that cannot meet the SLA requirements expected by the user are removed from the first information table to obtain a candidate list; the candidate list includes information on at least one space-based computing power node.

[0039] Based on the candidate list, user tasks are scheduled to at least one space-based computing node in the candidate list.

[0040] Among them, the space-based computing nodes that cannot meet the user's expected SLA requirements include:

[0041] Space-based computing nodes that cannot provide computing services within the reachable timeframe due to SLA requirements.

[0042] The method further includes:

[0043] Receive user task processing results returned by at least one space-based computing node;

[0044] The user task processing result is sent to the corresponding user.

[0045] The method further includes:

[0046] If the information of a space-based computing node in at least one network subdomain changes, or if a predetermined time period is reached, the first node updates the first information table based on the notification information of the space-based computing node.

[0047] This invention also provides a scheduling device for a space-based cloud network, applied to a first node, comprising:

[0048] The acquisition module is used to acquire announcement information sent by space-based computing power nodes within at least one network subdomain.

[0049] The construction module is used to construct a first information table based on the announcement information; the first information table includes information on multiple space-based computing power nodes.

[0050] The processing and scheduling module is used to process or schedule user tasks based on user requests and the first information table.

[0051] This invention also provides a first node, including a processor and a transceiver, wherein the transceiver receives and transmits data under the control of the processor, and the processor is configured to perform the following operations:

[0052] Based on at least one network subdomain, obtain the notification information sent by the space-based computing power nodes within the network subdomain;

[0053] Based on the announcement information, a first information table is constructed; the first information table includes information on multiple space-based computing power nodes.

[0054] Based on the user request and the first information table, perform user task processing or scheduling.

[0055] The first information table is a network node status information table, which includes at least one of the following: node computing power information, network information, service information, and link status information.

[0056] The first node is a space-based computing power node with communication capabilities and computing and storage capacity. This space-based computing power node is a basic component of the space-based cloud.

[0057] Wherein, the at least one network subdomain includes:

[0058] The network subdomain to which the first node belongs;

[0059] And / or,

[0060] The network subdomain to which the space-based computing power node with a hop count less than or equal to the first threshold belongs.

[0061] The processor is also used to perform the following operations:

[0062] The system receives announcement information broadcast by each space-based computing node within the at least one network subdomain; the announcement information includes at least one of the following: the address of the space-based computing node, the type of computing service that the space-based computing node can provide, the network resources of the space-based computing node, and the computing resources of the space-based computing node.

[0063] Where the space-based cloud network supports location addressing, the information of a space-based computing node in the first information table includes:

[0064] The address of the space-based computing node;

[0065] The reachability time between the space-based computing node and the first node;

[0066] The network resources of the space-based computing nodes;

[0067] The computing resources of the space-based computing nodes.

[0068] Where the space-based cloud network does not support location addressing, the information of a space-based computing node in the network node status information includes:

[0069] The address of the space-based computing node;

[0070] The reachability time between the space-based computing node and the first node;

[0071] The path information of the space-based computing nodes.

[0072] The processor is also used to perform the following operations:

[0073] Based on the address and ephemeris information of the space-based computing node, the reachability time between the space-based computing node and the first node is determined.

[0074] The processor is also used to perform the following operations:

[0075] Receive a first request sent by the user, the first request carrying the type of computing power service requested by the user and the expected service level agreement (SLA) requirements.

[0076] The processor is also used to perform the following operations:

[0077] If the first node is able to provide the computing power service type required by the user and can meet the user's expected SLA requirements, the first node processes the user's task according to the first request and feeds back the processing result to the user.

[0078] Alternatively, the first node may look up the first information table and schedule the user task to at least one space-based computing power node. Or, if the first node is unable to provide the type of computing power service required by the user or cannot meet the user's expected SLA requirements, the first node may look up the first information table and schedule the user task to at least one space-based computing power node.

[0079] The processor is also used to perform the following operations:

[0080] Based on the first request, space-based computing power nodes that cannot provide the computing power service type required by the user and space-based computing power nodes that cannot meet the SLA requirements expected by the user are removed from the first information table to obtain a candidate list; the candidate list includes information on at least one space-based computing power node.

[0081] Based on the candidate list, user tasks are scheduled to at least one space-based computing node in the candidate list.

[0082] Among them, the space-based computing nodes that cannot meet the user's expected SLA requirements include:

[0083] Space-based computing nodes that cannot provide computing services within the reachable timeframe due to SLA requirements.

[0084] The processor is also used to perform the following operations:

[0085] Receive user task processing results returned by at least one space-based computing node;

[0086] The user task processing result is sent to the corresponding user.

[0087] The processor is also used to perform the following operations:

[0088] When the information of a space-based computing node in at least one network subdomain changes, or when a predetermined time period is reached, the first node updates the first information table based on the notification information of the space-based computing node.

[0089] This invention also provides a space-based computing node, including a memory, a processor, and a program stored in the memory and executable on the processor. When the processor executes the program, it implements the scheduling method of the space-based cloud network as described above.

[0090] This invention also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps in the scheduling method for the space-based cloud network as described above.

[0091] The above-described technical solution of the present invention has at least the following beneficial effects:

[0092] In the scheduling method, apparatus, and space-based computing power node of the space-based cloud network in the embodiments of the present invention, the space-based cloud network is divided into multiple network subdomains. The space-based computing power node in each network subdomain constructs a first information table including the available time dimension, and performs task processing or scheduling based on the first information table. This can better adapt to the characteristics of networks with limited spatial resources and large spatiotemporal scales. At the same time, it reduces the overhead caused by frequent updates due to network dynamism to a certain extent. Attached Figure Description

[0093] Figure 1 A flowchart illustrating the steps of the scheduling method for a space-based cloud network provided in an embodiment of the present invention;

[0094] Figure 2 A flowchart illustrating Example 1 provided in the embodiments of the present invention;

[0095] Figure 3 A flowchart illustrating Example 2 provided in this embodiment of the invention;

[0096] Figure 4 This is a schematic diagram illustrating the structure of the scheduling device for the space-based cloud network provided in an embodiment of the present invention;

[0097] Figure 5 This is a schematic diagram showing the structure of the space-based computing node provided in an embodiment of the present invention. Detailed Implementation

[0098] To make the technical problems, technical solutions and advantages of the present invention clearer, a detailed description will be given below in conjunction with the accompanying drawings and specific embodiments.

[0099] like Figure 1 As shown, this embodiment of the invention provides a scheduling method for a space-based cloud network, which is executed by a first node and includes:

[0100] Step 101: Based on at least one network subdomain, obtain the notification information sent by the space-based computing power nodes within the network subdomain;

[0101] Step 102: Construct a first information table based on the notification information; the first information table includes information on multiple space-based computing nodes;

[0102] Step 103: Based on the user request and the first information table, perform user task processing or scheduling.

[0103] It should be noted that, in the network planning of this embodiment of the invention, the network (i.e., the space-based cloud network) is divided into subdomains (such as an orbital plane being a subdomain, or a cell being a subdomain); a network subdomain can ensure that the topology remains relatively stable for a certain period of time.

[0104] Optionally, the first node can be any node in the network subdomain. In other words, the functions and roles of each space-based computing power node in the network subdomain are the same. All space-based computing power nodes build their own first information tables and can perform computing power scheduling.

[0105] Optionally, the first information table is a network node status information table, which includes at least one of the following: node computing power information, network information, service information, and link status information.

[0106] Optionally, the first node is a space-based computing power node with communication capabilities and computing and storage capabilities, which is a basic component of the space-based cloud.

[0107] As an optional embodiment, the at least one network subdomain includes:

[0108] The network subdomain to which the first node belongs;

[0109] And / or,

[0110] The network subdomain to which the number of hops between the node and the first node is less than or equal to the first threshold.

[0111] In other words, in the embodiments of this application, multicast can be performed across the entire subdomain within a network subdomain, or multicast within a limited number of hops (e.g., 3-5 hops, because the more hops, the longer the latency). Furthermore, broadcasts with a limited number of hops can achieve a 99.8% probability of reaching the target network in a sparse network. For example, the Router Advertisement (RA) function of the IPv6 Neighbor Discovery Protocol can be used, which defaults to sending once every 600 seconds; the sending interval can be shortened.

[0112] In at least one embodiment of this application, step 101 includes:

[0113] The system receives announcement information broadcast by each space-based computing power node within the at least one network subdomain. The announcement information includes at least one of the following: the address of the space-based computing power node (which may be an IP address or a MAC address, etc.), the type of computing power service (service ID) that the space-based computing power node can provide, the network resources of the space-based computing power node, and the computing resources of the space-based computing power node.

[0114] As an optional embodiment, the IP address of the space-based computing node can be a semantically rich IP address; the network resources include transmission bandwidth, etc.; the computing resources include peak computing power, computing load, etc.

[0115] For example, at least one of the following: the address of the space-based computing node (which may be an IP address or a MAC address, etc.), the type of computing service (service ID) that the space-based computing node can provide, the network resources of the space-based computing node, and the computing resources of the space-based computing node, can be encapsulated in the optional information (RA).

[0116] Rich semantic IP addresses can be understood as incorporating location information into the IPv6 addressing space, which facilitates obtaining the approximate area where the satellite is located, avoiding the step of querying ephemeris data based on the satellite ID to calculate the distance. However, the IP addresses of the aforementioned space-based computing nodes need to be updated according to satellite movement.

[0117] Furthermore, the embodiments of this application also form a location-based addressing scheme, specifically a routing method for network layer addressing based on rich semantic IP addresses, which can realize addressing based on rich semantic IP addresses and avoid the problems of routing calculation and convergence difficulties caused by the dynamism of satellites.

[0118] In at least one optional embodiment of the present invention, the first node forms a first information table that is reachable by all subdomains / several hops, which may also be called a network node state information table (NSDB).

[0119] As an optional embodiment, when the space-based cloud network supports location addressing, the information of a space-based computing node in the first information table includes:

[0120] The address of the space-based computing node (which can be an IP address, a MAC address, etc.);

[0121] The reachability time between the space-based computing node and the first node;

[0122] The network resources of the space-based computing nodes;

[0123] The computing resources of the space-based computing nodes.

[0124] For example, the first information table is shown in Table 1:

[0125]

[0126] Table 1

[0127] The method further includes:

[0128] Based on the address of the space-based computing node (which can be an IP address, MAC address, etc.) and ephemeris information, the reachability time between the space-based computing node and the first node is determined.

[0129] Compared to ground-based computing power sensing networks, in this embodiment of the invention, space-based computing power nodes can avoid path calculation using a location-based addressing scheme. Optionally, during the location addressing time, routing table generation / update is performed, and the network is unavailable to provide services.

[0130] As another optional embodiment, when the space-based cloud network does not support location addressing, the information of a space-based computing node in the network node status information includes:

[0131] The address of the space-based computing node (which can be an IP address, a MAC address, etc.);

[0132] The reachability time between the space-based computing node and the first node;

[0133] The path information of the space-based computing nodes.

[0134] For example, the first information table is shown in Table 2:

[0135]

[0136] Table 2

[0137] For example, space-based computing nodes across the entire subdomain form a first information table (NSDB) for reachability across the entire subdomain / several hops based on the received notification information. The reachability time is a timestamp of an available time, which can be calculated using the IP address and ephemeris information. The formed NSDB needs to record the path. Access nodes can calculate the propagation delay based on the destination IP address, ephemeris information, and bandwidth information from the node information table. Combining this with computing power information, they can calculate the processing delay (since computing resource utilization may not be updated in real time, the calculated processing delay is an estimate). Then, based on the delay estimate, the cost of the corresponding path is generated.

[0138] Optionally, during the path calculation time, the routing table is generated / updated, and the network is unavailable to provide services.

[0139] The method further includes:

[0140] Based on the address of the space-based computing node (which can be an IP address, MAC address, etc.) and ephemeris information, the reachability time between the space-based computing node and the first node is determined.

[0141] As an optional embodiment, before step 103, the method further includes:

[0142] Receive a first request sent by the user, the first request carrying the type of computing power service requested by the user and the expected service level agreement (SLA) requirements.

[0143] Accordingly, step 103 includes:

[0144] Based on the first request, determine whether the first node can provide the type of computing power service required by the user, and whether it meets the user's expected SLA requirements;

[0145] If the first node is able to provide the computing power service type required by the user and can meet the user's expected SLA requirements, the first node processes the user's task according to the first request and feeds back the processing result to the user.

[0146] Alternatively, the first node may look up the first information table and schedule the user task to at least one space-based computing power node (i.e., the first node only acts as an access / routing function, forwarding the request to other service nodes according to the node status information table). Or, if the first node cannot provide the computing power service type required by the user or cannot meet the user's expected SLA requirements, the first node may look up the first information table and schedule the user task to at least one space-based computing power node.

[0147] The first node searches the first information table and schedules the user task to at least one space-based computing power node, including:

[0148] Based on the first request, space-based computing power nodes that cannot provide the computing power service type required by the user and space-based computing power nodes that cannot meet the SLA requirements expected by the user are removed from the first information table to obtain a candidate list; the candidate list includes information on at least one space-based computing power node.

[0149] Based on the candidate list, user tasks are scheduled to at least one space-based computing node in the candidate list.

[0150] As an optional embodiment, space-based computing nodes that cannot meet the user's expected SLA requirements include:

[0151] Space-based computing nodes that cannot provide computing services within the reachable timeframe due to SLA requirements.

[0152] In at least one optional embodiment of the present invention, the method further includes:

[0153] Receive user task processing results returned by at least one space-based computing node;

[0154] The user task processing result is sent to the corresponding user.

[0155] In at least one embodiment of the present invention, the method further includes:

[0156] If the information of a space-based computing node in at least one network subdomain changes, or if a predetermined time period is reached, the first node updates the first information table based on the notification information of the space-based computing node.

[0157] In other words, the first information table is updated periodically; when the first information table of a subdomain changes, the table needs to be updated. (For example, if a node's reachability time expires, causing the relatively stable topology of this subdomain to be disrupted, an update is required); and in this embodiment of the invention, the updated content will not cause a large occupation of network resources.

[0158] To more clearly describe the scheduling method of the space-based cloud network provided in the embodiments of the present invention, two examples are given below.

[0159] Example 1, such as Figure 2 As shown:

[0160] Step 1: The user initiates a request, specifying the type of computing power service required and the desired Service Level Agreement (SLA) (placed in the IPv6 options or the SRH in SRv6). For example: SLA, Dst (service ID). The service ID indicates the type of service requested and can be in the form of an IP address. The destination IP address can be provided by the service provider and can be a virtual address or an anycast address; this patent does not specify the exact requirements.

[0161] Step 2: Connect to space-based computing power node 1 and check the computing power service type carried in the request. First, determine whether this node has the service and whether it can fulfill the request.

[0162] Step 3: If the current node cannot fulfill the request (the service is unavailable or resources are insufficient), then query the NSDB table. First, obtain a candidate list of nodes that can provide the computing power service, as shown in Table 3:

[0163]

[0164] Table 3

[0165] Secondly, based on the SLA requirements, nodes that do not meet the SLA requirements are removed from the candidate list, and the remaining nodes are sorted. Specifically, the propagation delay can be calculated based on the destination IP address, ephemeris information, and bandwidth information in the node information table. The processing delay can be calculated based on the computing power information (since computing power utilization may not be updated in real time, the calculated processing delay is an estimate). Then, the nodes are sorted based on the delay estimate, and nodes that do not meet the SLA requirements are removed. N nodes are selected for traffic distribution (N can be calculated based on bandwidth, ensuring no blockage of the transmission link), as shown in Table 4.

[0166] service ID-a SIP1 T1 Bandwidth1 CPU_max1, CPU_idle1

[0167] Table 4

[0168] Step 4: Distribute the task to feasible candidate nodes. Alternatively, if space-based computing node 1 cannot meet the service requirements, then the access node will only act as an access / routing node, forwarding the request to other service nodes according to the node status information table.

[0169] It should be noted that if the capabilities within this subdomain are insufficient to meet a user's request, the user request will be forwarded to the centralized node for further scheduling and allocation.

[0170] Step 5: Return the calculation result. Alternatively, it can be forwarded and returned by other nodes, such as SIP2. For example, the access node (such as SIP1) is not within the user node's line of sight after the calculation is completed; however, it is perceptible to the user because semantically rich addressing only addresses based on the preceding location blocks and does not distinguish the satellite identity IDs within them.

[0171] If the resources of this node can satisfy the request, then steps 3 and 4 are ignored, the task is processed locally, and the result is returned to the user.

[0172] Step 6: After the other distributed nodes have completed their calculations, they return the results to the access node (i.e., space-based computing node 1).

[0173] Example 2, such as Figure 3 As shown:

[0174] Step 1: The user initiates a request, specifying the type of computing power service required and the desired Service Level Agreement (SLA) (placed in the IPv6 options or the SRH in SRv6). For example: SLA, Dst (service ID). The service ID indicates the type of service requested and can be in the form of an IP address. The destination IP address can be provided by the service provider and can be a virtual address or an anycast address; this patent does not specify the exact requirements.

[0175] Step 2: Connect to space-based computing power node 1 and check the computing power service type carried in the request. First, determine whether this node has the service and whether it can fulfill the request.

[0176] Step 3: If the current node cannot fulfill the request (service unavailable or insufficient resources), consult the NSDB table. Based on the location, computing power, and network information in the ephemeris data, select candidate destination nodes.

[0177] Secondly, based on the SLA requirements, nodes that cannot meet the SLA requirements are removed from the candidate list, and a forwarding table is generated by mapping the real IPs according to the NSDB table, as shown in Table 5:

[0178]

[0179] Table 5

[0180] Specifically, this could involve removing nodes that cannot complete computing power services within the reachable timeframe based on SLA requirements. Then, N nodes would be selected for load balancing (N can be calculated based on bandwidth, ensuring no congestion of transmission links).

[0181] Step 4: Based on the forwarding table, the task is distributed to feasible candidate nodes. For example, the forwarding path can be written into the routing in the IPv6 extension header or the SRH in SRv6.

[0182] Step 5: Return the calculation result. Alternatively, it can be forwarded and returned by other nodes, such as SIP2. For example, the access node (such as SIP1) is not within the user node's line of sight after the calculation is completed; however, it is perceptible to the user because semantically rich addressing only addresses based on the preceding location blocks and does not distinguish the satellite identity IDs within them.

[0183] If the resources of this node can satisfy the request, then steps 3 and 4 are ignored, the task is processed locally, and the result is returned to the user.

[0184] Step 6: After the other distributed nodes have completed their calculations, they return the results to the access node (i.e., space-based computing node 1).

[0185] In summary, this embodiment of the invention forms an NSDB table through notification information, and performs task processing or scheduling based on the NSDB table and computing power requirements. Specifically, the space-based cloud network is divided into multiple network subdomains, and the space-based computing power nodes in each network subdomain construct a first information table including the available time dimension, and perform task processing or scheduling based on the first information table. This can better adapt to the characteristics of networks with limited spatial resources and large spatiotemporal scales. At the same time, it reduces the overhead caused by frequent updates due to network dynamism to a certain extent.

[0186] like Figure 4 As shown, this embodiment of the invention also provides a scheduling device for a space-based cloud network, applied to a first node, comprising:

[0187] The acquisition module 401 is used to acquire the announcement information sent by the space-based computing power nodes within the network subdomain based on at least one network subdomain.

[0188] Construction module 402 is used to construct a first information table based on the announcement information; the first information table includes information on multiple space-based computing power nodes;

[0189] The processing and scheduling module 403 is used to process or schedule user tasks based on user requests and the first information table.

[0190] As an optional embodiment, the first information table is a network node status information table, which includes at least one of the following: node computing power information, network information, service information, and link status information.

[0191] As an optional embodiment, the first node is a space-based computing power node with communication functions and computing and storage capabilities, which is a basic component of the space-based cloud.

[0192] As an optional embodiment, the at least one network subdomain includes:

[0193] The network subdomain to which the first node belongs;

[0194] And / or,

[0195] The network subdomain to which the number of hops between the node and the first node is less than or equal to the first threshold.

[0196] As an optional embodiment, the acquisition module includes:

[0197] The acquisition submodule is used to receive announcement information broadcast by each space-based computing power node within the at least one network subdomain; the announcement information includes at least one of the following: the address of the space-based computing power node, the type of computing power service that the space-based computing power node can provide, the network resources of the space-based computing power node, and the computing resources of the space-based computing power node.

[0198] As an optional embodiment, when the space-based cloud network supports location addressing, the information of a space-based computing node in the first information table includes:

[0199] The address of the space-based computing node;

[0200] The reachability time between the space-based computing node and the first node;

[0201] The network resources of the space-based computing nodes;

[0202] The computing resources of the space-based computing nodes.

[0203] As an optional embodiment, when the space-based cloud network does not support location addressing, the information of a space-based computing node in the network node status information includes:

[0204] The address of the space-based computing node;

[0205] The reachability time between the space-based computing node and the first node;

[0206] The path information of the space-based computing nodes.

[0207] As an optional embodiment, the apparatus further includes:

[0208] The time determination module is used to determine the reachability time between the space-based computing node and the first node based on the address and ephemeris information of the space-based computing node.

[0209] As an optional embodiment, the apparatus further includes:

[0210] The request receiving module is used to receive a first request sent by the user, the first request carrying the type of computing power service required by the user and the expected service level agreement (SLA) requirements.

[0211] As an optional embodiment, the processing scheduling module includes:

[0212] The first submodule is used to determine, based on the first request, whether the first node can provide the type of computing power service required by the user, and whether it meets the user's expected SLA requirements;

[0213] The second submodule is used to process user tasks according to the first request and feed back the processing results to the user, provided that the first node can provide the computing power service type required by the user and can meet the user's expected SLA requirements.

[0214] Alternatively, the first information table can be searched to schedule the user task to at least one space-based computing power node. Or, if the first node cannot provide the type of computing power service required by the user or cannot meet the user's expected SLA requirements, the first information table can be searched to schedule the user task to at least one space-based computing power node.

[0215] As an optional embodiment, the second submodule is further configured to:

[0216] Based on the first request, space-based computing power nodes that cannot provide the computing power service type required by the user and space-based computing power nodes that cannot meet the SLA requirements expected by the user are removed from the first information table to obtain a candidate list; the candidate list includes information on at least one space-based computing power node.

[0217] Based on the candidate list, user tasks are scheduled to at least one space-based computing node in the candidate list.

[0218] As an optional embodiment, space-based computing nodes that cannot meet the user's expected SLA requirements include:

[0219] Space-based computing nodes that cannot provide computing services within the reachable timeframe due to SLA requirements.

[0220] As an optional embodiment, the apparatus further includes:

[0221] The result receiving module is used to receive user task processing results returned by at least one space-based computing power node.

[0222] The result sending module is used to send the user task processing result to the corresponding user.

[0223] As an optional embodiment, the apparatus further includes:

[0224] The update module is used to update the first information table based on the announcement information of the space-based computing power nodes when the information of the space-based computing power nodes in at least one network subdomain changes, or when a predetermined time period is reached.

[0225] In this embodiment of the invention, the space-based cloud network is divided into multiple network subdomains. The space-based computing nodes in each network subdomain construct a first information table including the available time dimension, and perform task processing or scheduling based on the first information table. This can better adapt to the characteristics of networks with limited spatial resources and large spatiotemporal scales. At the same time, it can reduce the overhead caused by frequent updates due to network dynamism to a certain extent.

[0226] It should be noted that the scheduling device for the space-based cloud network provided in this embodiment of the invention is a device capable of executing the above-described scheduling method for the space-based cloud network. Therefore, all embodiments of the above-described scheduling method for the space-based cloud network are applicable to this device and can achieve the same or similar beneficial effects.

[0227] like Figure 5 As shown, this embodiment of the invention also provides a space-based computing node, which is a first node, including a processor 500 and a transceiver 510. The transceiver 510 receives and transmits data under the control of the processor 500, and the processor 500 is used to perform the following operations:

[0228] Based on at least one network subdomain, obtain the notification information sent by the space-based computing power nodes within the network subdomain;

[0229] Based on the announcement information, a first information table is constructed; the first information table includes information on multiple space-based computing power nodes.

[0230] Based on the user request and the first information table, perform user task processing or scheduling.

[0231] As an optional embodiment, the first information table is a network node status information table, which includes at least one of the following: node computing power information, network information, service information, and link status information.

[0232] As an optional embodiment, the first node is a space-based computing power node with communication functions and computing and storage capabilities, which is a basic component of the space-based cloud.

[0233] As an optional embodiment, the at least one network subdomain includes:

[0234] The network subdomain to which the first node belongs;

[0235] And / or,

[0236] The network subdomain to which the number of hops between the node and the first node is less than or equal to the first threshold.

[0237] As an optional embodiment, the processor is also configured to perform the following operations:

[0238] The system receives announcement information broadcast by each space-based computing node within the at least one network subdomain; the announcement information includes at least one of the following: the address of the space-based computing node, the type of computing service that the space-based computing node can provide, the network resources of the space-based computing node, and the computing resources of the space-based computing node.

[0239] As an optional embodiment, when the space-based cloud network supports location addressing, the information of a space-based computing node in the first information table includes:

[0240] The address of the space-based computing node;

[0241] The reachability time between the space-based computing node and the first node;

[0242] The network resources of the space-based computing nodes;

[0243] The computing resources of the space-based computing nodes.

[0244] As an optional embodiment, when the space-based cloud network does not support location addressing, the information of a space-based computing node in the network node status information includes:

[0245] The address of the space-based computing node;

[0246] The reachability time between the space-based computing node and the first node;

[0247] The path information of the space-based computing nodes.

[0248] As an optional embodiment, the processor is also configured to perform the following operations:

[0249] Based on the address and ephemeris information of the space-based computing node, the reachability time between the space-based computing node and the first node is determined.

[0250] As an optional embodiment, the processor is also configured to perform the following operations:

[0251] Receive a first request sent by the user, the first request carrying the type of computing power service requested by the user and the expected service level agreement (SLA) requirements.

[0252] As an optional embodiment, the processor is also configured to perform the following operations:

[0253] If the first node is able to provide the computing power service type required by the user and can meet the user's expected SLA requirements, the first node processes the user's task according to the first request and feeds back the processing result to the user.

[0254] Alternatively, the first node may look up the first information table and schedule the user task to at least one space-based computing power node. Or, if the first node is unable to provide the type of computing power service required by the user or cannot meet the user's expected SLA requirements, the first node may look up the first information table and schedule the user task to at least one space-based computing power node.

[0255] As an optional embodiment, the processor is also configured to perform the following operations:

[0256] Based on the first request, space-based computing power nodes that cannot provide the computing power service type required by the user and space-based computing power nodes that cannot meet the SLA requirements expected by the user are removed from the first information table to obtain a candidate list; the candidate list includes information on at least one space-based computing power node.

[0257] Based on the candidate list, user tasks are scheduled to at least one space-based computing node in the candidate list.

[0258] As an optional embodiment, space-based computing nodes that cannot meet the user's expected SLA requirements include:

[0259] Space-based computing nodes that cannot provide computing services within the reachable timeframe due to SLA requirements.

[0260] As an optional embodiment, the processor is also configured to perform the following operations:

[0261] Receive user task processing results returned by at least one space-based computing node;

[0262] The user task processing result is sent to the corresponding user.

[0263] As an optional embodiment, the processor is also configured to perform the following operations:

[0264] If the information of a space-based computing node in at least one network subdomain changes, or if a predetermined time period is reached, the first node updates the first information table based on the notification information of the space-based computing node.

[0265] In this embodiment of the invention, the space-based cloud network is divided into multiple network subdomains. The space-based computing nodes in each network subdomain construct a first information table including the available time dimension, and perform task processing or scheduling based on the first information table. This can better adapt to the characteristics of networks with limited spatial resources and large spatiotemporal scales. At the same time, it can reduce the overhead caused by frequent updates due to network dynamism to a certain extent.

[0266] It should be noted that the space-based computing power node provided in the embodiments of the present invention is a node capable of executing the above-described scheduling method of the space-based cloud network. Therefore, all embodiments of the above-described scheduling method of the space-based cloud network are applicable to this node and can achieve the same or similar beneficial effects.

[0267] This invention also provides a space-based computing node, which is a first node. The communication device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the various processes in the above-described space-based cloud network scheduling method embodiments and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0268] This invention also provides a computer-readable storage medium storing a computer program. When executed by a processor, this program implements the various processes described in the above-described space-based cloud network scheduling method embodiments, achieving the same technical effects. To avoid repetition, it will not be described again here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc.

[0269] 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-readable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0270] 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 A device for one or more processes and / or the functions specified in one or more boxes.

[0271] 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 a paper article including instruction means, the instruction means being implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0272] These computer program instructions can also be loaded onto a computer or other programmable data processing equipment, causing the computer or other programmable equipment to perform a series of operational steps 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.

[0273] The above description represents the preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A scheduling method for a space-based cloud network, executed by a first node, characterized in that, include: Based on at least one network subdomain, obtain the notification information sent by the space-based computing power nodes within the network subdomain; Based on the announcement information, a first information table is constructed; the first information table includes information on multiple space-based computing power nodes. Based on the user request and the first information table, perform user task processing or scheduling; Before performing task processing or scheduling based on the user request and the first information table, the method further includes: Receive a first request sent by the user, the first request carrying the type of computing power service requested by the user and the expected service level agreement (SLA) requirements; The step of processing or scheduling tasks based on user requests and the first information table includes: Based on the first request, determine whether the first node can provide the type of computing power service required by the user, and whether it meets the user's expected SLA requirements; If the first node is able to provide the computing power service type required by the user and can meet the user's expected SLA requirements, the first node processes the user's task according to the first request and feeds back the processing result to the user. Alternatively, the first node may look up the first information table and schedule the user task to at least one space-based computing power node. Or, if the first node is unable to provide the type of computing power service required by the user or cannot meet the user's expected SLA requirements, the first node may look up the first information table and schedule the user task to at least one space-based computing power node.

2. The method according to claim 1, characterized in that, The first information table is a network node status information table, which includes at least one of the following: node computing power information, network information, service information, and link status information.

3. The method according to claim 1, characterized in that, The first node is a space-based computing power node with communication capabilities and computing and storage capabilities. This space-based computing power node is a basic component of the space-based cloud.

4. The method according to claim 1, characterized in that, The at least one network subdomain includes: The network subdomain to which the first node belongs; And / or, The network subdomain to which the number of hops between the node and the first node is less than or equal to the first threshold.

5. The method according to any one of claims 1-4, characterized in that, Based on at least one network subdomain, obtain the announcement information sent by the space-based computing power nodes within the network subdomain, including: The system receives announcement information broadcast by each space-based computing node within the at least one network subdomain; the announcement information includes at least one of the following: the address of the space-based computing node, the type of computing service that the space-based computing node can provide, the network resources of the space-based computing node, and the computing resources of the space-based computing node.

6. The method according to claim 5, characterized in that, When the space-based cloud network supports location-based addressing, the information of a space-based computing node in the first information table includes: The semantically rich IP address of the space-based computing node; The reachability time between the space-based computing node and the first node; The network resources of the space-based computing nodes; The computing resources of the space-based computing nodes.

7. The method according to claim 5, characterized in that, In the case that the space-based cloud network does not support location addressing, the information of a space-based computing node in the network node status information includes: The address of the space-based computing node; The reachability time between the space-based computing node and the first node; The path information of the space-based computing nodes.

8. The method according to claim 6 or 7, characterized in that, The method further includes: Based on the address and ephemeris information of the space-based computing node, the reachability time between the space-based computing node and the first node is determined.

9. The method according to claim 1, characterized in that, The first node searches the first information table and schedules the user task to at least one space-based computing power node, including: Based on the first request, space-based computing power nodes that cannot provide the computing power service type required by the user and space-based computing power nodes that cannot meet the SLA requirements expected by the user are removed from the first information table to obtain a candidate list; the candidate list includes information on at least one space-based computing power node. Based on the candidate list, user tasks are scheduled to at least one space-based computing node in the candidate list.

10. The method according to claim 1 or 9, characterized in that, Space-based computing nodes that cannot meet users' expected SLA requirements include: Space-based computing nodes that cannot provide computing services within the reachable timeframe due to SLA requirements.

11. The method according to claim 1 or 9, characterized in that, The method further includes: Receive user task processing results returned by at least one space-based computing node; The user task processing result is sent to the corresponding user.

12. The method according to claim 6 or 7, characterized in that, The method further includes: If the information of a space-based computing node in at least one network subdomain changes, or if a predetermined time period is reached, the first node updates the first information table based on the notification information of the space-based computing node.

13. A scheduling device for a space-based cloud network, applied to a first node, characterized in that, include: The acquisition module is used to acquire announcement information sent by space-based computing power nodes within at least one network subdomain. The construction module is used to construct a first information table based on the announcement information; the first information table includes information on multiple space-based computing power nodes. The processing and scheduling module is used to process or schedule user tasks based on user requests and the first information table. The device further includes: The request receiving module is used to receive a first request sent by the user, the first request carrying the type of computing power service required by the user and the expected service level agreement (SLA) requirements. The processing and scheduling module includes: The first submodule is used to determine, based on the first request, whether the first node can provide the type of computing power service required by the user, and whether it meets the user's expected SLA requirements; The second submodule is used to process user tasks according to the first request and feed back the processing results to the user, provided that the first node can provide the computing power service type required by the user and can meet the user's expected SLA requirements. Alternatively, the first information table can be searched to schedule the user task to at least one space-based computing power node. Or, if the first node cannot provide the type of computing power service required by the user or cannot meet the user's expected SLA requirements, the first information table can be searched to schedule the user task to at least one space-based computing power node.

14. A first node, comprising a processor and a transceiver, the transceiver receiving and transmitting data under the control of the processor, characterized in that, The processor is used to perform the following operations: Based on at least one network subdomain, obtain the notification information sent by the space-based computing power nodes within the network subdomain; Based on the announcement information, a first information table is constructed; the first information table includes information on multiple space-based computing power nodes. Based on the user request and the first information table, perform user task processing or scheduling; The processor is also used to perform the following operations: Receive a first request sent by the user, the first request carrying the type of computing power service requested by the user and the expected service level agreement (SLA) requirements; The processor is also used to perform the following operations: Based on the first request, determine whether the first node can provide the type of computing power service required by the user, and whether it meets the user's expected SLA requirements; If the first node can provide the computing power service type required by the user and can meet the user's expected SLA requirements, the user task is processed according to the first request and the processing result is fed back to the user. Alternatively, the first information table can be searched to schedule the user task to at least one space-based computing power node. Or, if the first node cannot provide the type of computing power service required by the user or cannot meet the user's expected SLA requirements, the first information table can be searched to schedule the user task to at least one space-based computing power node.

15. The first node according to claim 14, characterized in that, The first information table is a network node status information table, which includes at least one of the following: node computing power information, network information, service information, and link status information.

16. The first node according to claim 14, characterized in that, The first node is a space-based computing power node with communication capabilities and computing and storage capabilities. This space-based computing power node is a basic component of the space-based cloud.

17. The first node according to claim 14, characterized in that, The at least one network subdomain includes: The network subdomain to which the first node belongs; And / or, The network subdomain to which the number of hops between the node and the first node is less than or equal to the first threshold.

18. The first node according to any one of claims 14-17, characterized in that, The processor is also used to perform the following operations: The system receives announcement information broadcast by each space-based computing node within the at least one network subdomain; the announcement information includes at least one of the following: the address of the space-based computing node, the type of computing service that the space-based computing node can provide, the network resources of the space-based computing node, and the computing resources of the space-based computing node.

19. The first node according to claim 18, characterized in that, When the space-based cloud network supports location-based addressing, the information of a space-based computing node in the first information table includes: The address of the space-based computing node; The reachability time between the space-based computing node and the first node; The network resources of the space-based computing nodes; The computing resources of the space-based computing nodes.

20. The first node according to claim 18, characterized in that, In the case that the space-based cloud network does not support location addressing, the information of a space-based computing node in the network node status information includes: The address of the space-based computing node; The reachability time between the space-based computing node and the first node; The path information of the space-based computing nodes.

21. The first node according to claim 19 or 20, characterized in that, The processor is also used to perform the following operations: Based on the address and ephemeris information of the space-based computing node, the reachability time between the space-based computing node and the first node is determined.

22. The first node according to claim 14, characterized in that, The processor is also used to perform the following operations: Based on the first request, space-based computing power nodes that cannot provide the computing power service type required by the user and space-based computing power nodes that cannot meet the SLA requirements expected by the user are removed from the first information table to obtain a candidate list; the candidate list includes information on at least one space-based computing power node. Based on the candidate list, user tasks are scheduled to at least one space-based computing node in the candidate list.

23. The first node according to claim 14 or 22, characterized in that, Space-based computing nodes that cannot meet users' expected SLA requirements include: Space-based computing nodes that cannot provide computing services within the reachable timeframe due to SLA requirements.

24. The first node according to claim 14 or 22, characterized in that, The processor is also used to perform the following operations: Receive user task processing results returned by at least one space-based computing node; The user task processing result is sent to the corresponding user.

25. The first node according to claim 19 or 20, characterized in that, The processor is also used to perform the following operations: If the information of a space-based computing node in at least one network subdomain changes, or if a predetermined time period is reached, the first node updates the first information table based on the notification information of the space-based computing node.

26. A space-based computing node, comprising a memory, a processor, and a program stored in the memory and executable on the processor; characterized in that, When the processor executes the program, it implements the scheduling method for the space-based cloud network as described in any one of claims 1-12.

27. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the program implements the steps of the scheduling method for a space-based cloud network as described in any one of claims 1-12.

Images