Low earth orbit satellite network routing method, control device and computer readable storage medium

Abstract

The application relates to a low-orbit satellite network routing method, a control device and a computer readable storage medium. The method comprises the following steps: in response to a message sent by a gateway node to a satellite node, a first routing path for message transmission is obtained according to a routing path table and information of a terminal satellite in a data packet, wherein the satellite node comprises a starting satellite, a terminal satellite and an intermediate transmission satellite; and the message is sent from the starting satellite to the terminal satellite based on the first routing path information in a label mode. Through the routing path table in the form of labels and the information forwarding operation in the form of labels, the data length of the message header is compressed, and the communication bandwidth is saved relative to the label stack transmission data mode.

Description

Technical Field

[0001] This invention relates to the field of satellite communication technology, and specifically provides a low-Earth orbit satellite network routing method, control device, and computer-readable storage medium. Background Technology

[0002] Low Earth Orbit (LEO) satellites operate in circular orbits at altitudes between 500 and 2000 kilometers. LEO satellites orbit the Earth at very high speeds, and the visibility time of a single LEO satellite is typically around 10 minutes. However, the coverage area of ​​a single LEO satellite is relatively small; to achieve continuous global coverage, a network of dozens to hundreds of satellites is required. Space networks are characterized by continuously changing topologies, limited satellite storage and processing capabilities, and long transmission times for inter-satellite links (ISL).

[0003] Chinese patent application CN 115514407 A discloses a low-Earth orbit satellite network routing method, system, and computer-readable storage medium. The method includes: generating a corresponding tag stack based on the tag IDs of satellites on each routing path, and uploading the tag stack and the IP routing table to the source satellite. When all tags in the first tag stack are popped, the data packet arrives at the destination satellite.

[0004] The above document uses a tag stack for message transmission, but the tag stack occupies more than 2N bytes, which compresses the communication bandwidth.

[0005] Accordingly, a new network routing scheme is needed in this field to solve the above problems. Summary of the Invention

[0006] To overcome the above-mentioned defects, the present invention is proposed to provide a solution or at least a partial solution to the technical disadvantages of the tag stack in the prior art, such as high bandwidth consumption.

[0007] In a first aspect, the present invention provides a low-Earth orbit satellite network routing method, the method comprising:

[0008] In response to a message sent by a gateway node to a satellite node, a first routing path for message transmission is obtained by querying the routing path table and the information of the destination satellite in the data packet. The types of satellite nodes include: origin satellite, destination satellite, and intermediate transmission satellite.

[0009] The message is sent from the originating satellite to the destination satellite using a tag based on the first routing path information.

[0010] During the process of the message being sent from the originating satellite to the destination satellite, inter-satellite tags are selectively pushed, exchanged, or popped in the message according to the position of the sending satellite in the routing path and the first routing path information. The inter-satellite tag is a unique identification tag for the receiving satellite corresponding to the path, and the receiving satellite determines the first routing path based on the inter-satellite tag.

[0011] The step of sending the message from the originating satellite to the destination satellite using tags based on the first routing path information includes:

[0012] A path static label is formed based on the first route path information, wherein the path static label includes origin satellite information, destination satellite information and path information; or an inter-satellite label is created based on the first route path information, wherein the inter-satellite label uniquely corresponds to the path.

[0013] The message is sent from the originating satellite to the destination satellite based on the path static label or inter-satellite label.

[0014] Furthermore, the connection paths between the routing path table and the satellite nodes in the first routing path are both created based on the first routing path, which is a virtual path calculated based on the satellite nodes.

[0015] Before obtaining the first routing path for message transmission based on the routing path table and the destination satellite information in the data packet, the method further includes:

[0016] The routing path table is synchronized to all satellite nodes in the routing path.

[0017] Furthermore, when the intermediate transmission satellite receives a message from another satellite node, it queries the corresponding first routing path based on the routing path table and the inter-satellite label in the message.

[0018] Furthermore, the step of selectively pushing, exchanging, or popping inter-satellite tags in the message based on the position of the transmitting satellite in the routing path and the first routing path information includes:

[0019] If the transmitting satellite is the originating satellite, then the inter-satellite labels corresponding to the secondary satellite nodes are obtained based on the first routing path information, and

[0020] The inter-satellite tags corresponding to the secondary satellite nodes are pushed into the message, and the originating satellite sends the message with the inter-satellite tags to the secondary satellite nodes.

[0021] If the sending satellite is the destination satellite, the inter-satellite tag in the message will pop up, and the destination satellite will send the data packet to the terminal according to the link layer address in the message;

[0022] If the transmitting satellite is an intermediate transmission satellite, then after receiving the message sent by the higher-level satellite node,

[0023] Based on the first route path information, the inter-satellite labels corresponding to the next-level satellite nodes are obtained, and

[0024] The inter-satellite tags in the received messages are exchanged based on the inter-satellite tags corresponding to the next-level satellite nodes, wherein the intermediate transmission satellite sends the messages with inter-satellite tags to the next-level satellite nodes.

[0025] Furthermore, the method for creating the connection path between the routing path table and the satellite nodes in the first routing path includes:

[0026] In response to a lead packet sent by the gateway node to the originating satellite in the first routing path, the originating satellite transmits a path connection request to the next level satellite node level by level based on the first routing path information in the lead packet. The next level satellite node establishes a path connection with the previous level node after receiving the path connection request transmitted by the previous level satellite node.

[0027] After receiving the path connection request, the endpoint satellite transmits the first response information to the next higher level satellite node in reverse first routing path. After receiving the first response information transmitted by the next higher level satellite node, the next higher level satellite node transmits the second response information of the satellite node together with the first response information to the next higher level node. The response information includes the effective time and bandwidth utilization.

[0028] The starting satellite receives response information from the secondary satellite node;

[0029] Based on the response information and the routing path, an inter-satellite label-based routing path table is established.

[0030] Furthermore, the routing path information is expressed in the form of a tag stack, wherein the tag stack includes multiple tag segments, and each tag segment represents the network element number tag of one of the satellite nodes in the routing path;

[0031] The tag segments are arranged sequentially according to the order of the satellite nodes in the routing path, wherein the satellite nodes are determined to be the next-level satellite nodes to which the data needs to be sent based on the order of the tag segments.

[0032] The path connection request includes the tag stack.

[0033] Furthermore, when a satellite node receives a path connection request from the previous node, it pops the tag segment belonging to its own satellite node from the tag stack.

[0034] The path connection request is sent to the next-level satellite node according to the order of the tag segments in the popped-up tag stack.

[0035] Furthermore, after the destination satellite pops up a unique tag segment, it sends the message to the terminal based on the link layer address.

[0036] Furthermore, when a satellite node fails to send a message to the next-level satellite node along the first routing path, a second routing path is obtained based on the information of the destination satellite and the routing path table.

[0037] A label stack corresponding to the routing path information is formed based on the second routing path, wherein the label stack includes multiple label segments, and each label segment represents one of the satellite node labels in the second routing path;

[0038] The tag segments are arranged sequentially according to the order of the satellite nodes in the second routing path, wherein the satellite nodes determine the next-level satellite node to which the data needs to be sent based on the arrangement order of the tag segments.

[0039] In a second aspect, a control device is provided, comprising a processor and a storage device, the storage device being adapted to store a plurality of program codes, the program codes being adapted to be loaded and run by the processor to execute the low-Earth orbit satellite network routing method described in any of the above-described technical solutions.

[0040] In a third aspect, a computer-readable storage medium is provided, wherein a plurality of program codes are stored therein, the program codes being adapted to be loaded and run by a processor to perform the low-Earth orbit satellite network routing method described in any of the above-described technical solutions.

[0041] The present invention comprises one or more of the following technical solutions:

[0042] Beneficial effects:

[0043] In implementing the technical solution of this invention, by using a routing path table in the form of tags and information forwarding operations in the form of tags, the data length of the message header is compressed and communication bandwidth is saved compared to the data transmission method of tag stack. Attached Figure Description

[0044] The disclosure of this invention will become more readily understood with reference to the accompanying drawings. It will be readily understood by those skilled in the art that these drawings are for illustrative purposes only and are not intended to limit the scope of protection of this invention. Furthermore, similar numbers in the drawings are used to denote similar components, wherein:

[0045] Figure 1This is a schematic flowchart of the main steps of a low-Earth orbit satellite network routing method according to an embodiment of the present invention;

[0046] Figure 2 This is a schematic diagram of a satellite node topology according to an embodiment of the present invention;

[0047] Figure 3 This is a schematic diagram of the routing path of a satellite according to an embodiment of the present invention;

[0048] Figure 4 This is a schematic diagram of a tag stack structure according to an embodiment of the present invention;

[0049] Figure 5 This is a schematic diagram illustrating the creation of a satellite routing path according to an embodiment of the present invention;

[0050] Figure 6 This is the main content of a path connection request according to an embodiment of the present invention;

[0051] Figure 7 This is the main content of the response information according to one embodiment of the present invention;

[0052] Figure 8 This is a schematic diagram of data transmission of a satellite according to a routing path according to an embodiment of the present invention;

[0053] Figure 9 This is a schematic diagram of a static label for the endpoint according to an embodiment of the present invention;

[0054] Figure 10 This is a schematic diagram of the tag stack processing flow according to an embodiment of the present invention;

[0055] Figure 11 This is a schematic diagram of a path static label according to an embodiment of the present invention;

[0056] Figure 12 This is a schematic diagram of an inter-satellite tag according to an embodiment of the present invention;

[0057] Figure 13 This is a schematic flowchart of the main steps of a low-Earth orbit satellite network tag stack routing method according to an embodiment of the present invention. Detailed Implementation

[0058] Some embodiments of the present invention will now be described with reference to the accompanying drawings. Those skilled in the art should understand that these embodiments are merely illustrative of the technical principles of the present invention and are not intended to limit the scope of protection of the present invention.

[0059] In the description of this invention, "module" and "processor" can include hardware, software, or a combination of both. A module can include hardware circuitry, various suitable sensors, communication ports, memory, and may also include software components, such as program code, or a combination of software and hardware. A processor can be a central processing unit, microprocessor, image processor, digital signal processor, or any other suitable processor. The processor has data and / or signal processing capabilities. The processor can be implemented in software, in hardware, or a combination of both. Non-transitory computer-readable storage media includes any suitable medium capable of storing program code, such as magnetic disks, hard disks, optical disks, flash memory, read-only memory, random access memory, etc. The term "A and / or B" means all possible combinations of A and B, such as only A, only B, or A and B. The terms "at least one A or B" or "at least one of A and B" have a similar meaning to "A and / or B" and can include only A, only B, or A and B. The singular terms "a" or "this" can also include plural forms.

[0060] Here we will first explain some of the terms involved in this invention.

[0061] In one application scenario of this invention, information needs to be transmitted from gateway node A to terminal B via a satellite link. Gateway node A first sends the information to the originating satellite, which then sequentially sends it to the destination satellite along a certain information transmission path, and finally the destination satellite sends it to terminal B.

[0062] Example 1:

[0063] See appendix Figure 1 , Figure 1 This is a schematic flowchart illustrating the main steps of a low-Earth orbit satellite network routing method according to an embodiment of the present invention. Figure 1 As shown, the low-Earth orbit satellite network routing method in this embodiment of the invention mainly includes the following steps S10-S50.

[0064] Step S10: Calculate the first routing path based on the satellite nodes.

[0065] In this embodiment, a communication channel between satellites needs to be established before satellite communication can begin. In this embodiment, the first routing path is a virtual path calculated based on satellite nodes. The first routing path includes the originating satellite, intermediate transmission satellites, and the destination satellite. The first routing path is obtained based on the satellite node information, which can be queried in real time from the ephemeris.

[0066] In one implementation, the ground control center typically calculates the most suitable first route for information transmission between the originating and destination satellites using ephemeris data. Within a very short timeframe (referred to as a time slice in this embodiment), the satellites on the ephemeris can be considered stationary. Based on this static routing mechanism, within each time slice, the ground station obtains the static topology between satellite nodes according to the ephemeris, i.e., the overall network topology between satellites, such as... Figure 2 As shown.

[0067] Based on the topology within a time slice in this embodiment, the satellites connected to the sending ground station and the receiving ground station in each time slice can be calculated according to strategies such as closest distance and longest visible arc. These satellites are referred to as the starting satellite Sat_s and the ending satellite Sat_d of the on-board route in each time slice.

[0068] The shortest path route Lk (k=0) between the originating satellite Sat_s and the destination satellite Sat_d within each time slice is calculated based on Dijkstra's algorithm, and denoted as the primary path L0. Then, the k-th alternative path is calculated. Specifically, the relevant links of the primary path L0 are deleted from the network topology at the current time, k=k+1. Again, based on Dijkstra's algorithm, the shortest path route between the originating satellite Sat_s and the destination satellite Sat_d within each time slice is calculated. The resulting new route is the k-th alternative path Lk. Figure 3 As shown, (3,5)-(3,6)-(2,1) is a main path. In this embodiment, information is transmitted according to the main path by default. The first routing path in this embodiment is the main path for information transmission between gateway node A and terminal B. The first routing path in this embodiment is a virtual path calculated. Satellite nodes need to build a real information transmission channel for transmitting information based on the first routing path.

[0069] It should be noted that within a time slice, satellites establish several communication channels based on the current topology. During subsequent information transmission, the ground control center selects a suitable channel from these communication channels. In this embodiment, the calculated first route path is one of these communication channels.

[0070] Step S20: Create a table of connection paths and corresponding routing paths between satellite nodes in the first routing path based on the first routing path.

[0071] In this embodiment, the routing path table and the connection paths between satellite nodes in the first routing path are created based on the first routing path. In this embodiment, the connection paths between satellite nodes in the first routing path and the corresponding routing path table are created through steps S201-S205, as detailed below:

[0072] Step S201: The gateway node sends a pilot data packet to the starting satellite in the first routing path.

[0073] In this embodiment, the pilot data packet contains first routing path information, which includes the originating satellite information, the destination satellite information, and the information of intermediate transmission satellites. In this embodiment, when the originating satellite receives the pilot data packet sent from the gateway node, it constructs a connection network between satellite nodes based on the first routing path information in the pilot data packet. The connection path refers to the network information transmission channel constructed between satellite nodes according to the first routing path.

[0074] In one implementation, such as Figure 3 As shown, for example, the calculated first route path is satellite (3,5)-(3,6)-(2,1), where (3,5) is the starting satellite and (2,1) is the ending satellite. The gateway will send a lead packet to satellite node (3,5). Here, (3,5) is the satellite number in the ephemeris, and in this embodiment, it is the network element number of that satellite.

[0075] The lead packet includes first routing path information, which is expressed using a tag stack. For example... Figure 4 As shown, the tag stack routing header includes multiple dynamic tag segments and several fixed routing headers. Each tag segment represents the network element number of one of the satellite nodes in the routing path. The information in the fixed routing headers indicates the attributes of this data packet and the reading method of the dynamic tag segments. For example, when S (Signaling & Management Flag) is 1, it indicates that the data packet is a control and management signaling data packet; when S is 0, it indicates that it is a general data data packet. In this embodiment, the S of the lead data packet is 1, indicating that its function is to transmit signaling.

[0076] In this embodiment, the tag segments are arranged sequentially according to the order of the satellite nodes in the routing path, and the satellite nodes determine the next-level satellite node to which the data needs to be sent based on the arrangement of the tag segments. (Continuing with...) Figure 4 For example, suppose Figure 4 The dynamic tag segment has three segments, in the order of (3,5), (3,6), and (2,1). Therefore, in this embodiment, the starting satellite of the first routing path is (3,5), the ending satellite is (2,1), and the intermediate transmission satellite is (3,6). The starting satellite determines the information transmission path based on the above information, thereby establishing an information transmission channel between the three.

[0077] In this embodiment, preferably, a specific method for transferring tag stacks between satellites is provided, such as... Figure 10 As shown, specifically: when a satellite node receives a path connection request from a previous node, it pops the tag segment belonging to its own satellite node from the tag stack, and sends the path connection request to the next-level satellite node according to the order of the popped tag segments in the stack. The destination satellite, after popping a unique tag segment, sends the message to the terminal based on the link layer address.

[0078] Step S202: Based on the first routing path information in the pilot data packet, the path connection request is transmitted from the starting satellite to the next level of satellite nodes.

[0079] In this embodiment, a path connection request is used to establish connections between satellites, and the path connection request includes first routing path information. The upper-level satellite node forwards the path connection request to the lower-level satellite node, and upon receiving the path connection request from the upper-level satellite node, the lower-level satellite node establishes a path connection with the upper-level node.

[0080] In one implementation, the pilot data packet is a control signaling message sent by gateway node A to establish an inter-satellite channel, while the path connection request is a control signaling message sent by the originating satellite to establish an inter-satellite channel. The difference lies in the format of the pilot data packet after it is sent to the originating satellite; the originating satellite can modify the format of the pilot data packet according to specific settings to meet the communication requirements between satellites. In other words, in some cases, when the originating satellite does not need to change the format of the pilot data packet, the path connection request is the pilot data packet itself. It should be noted that "path connection request is pilot data packet" here means that both have the same format, for example, using the same label stack to represent routing path information. For ease of understanding, in this implementation, the path connection request is referred to as the pilot data packet.

[0081] like Figure 5 and 6 As shown, Figure 6 The image shows the main items in the pilot packet.

[0082] SRC (Source): The starting satellite number.

[0083] DST: (Destination Satellite) Destination satellite number.

[0084] PathID: (Path Identification) A unique number across the entire network that contains routing path information, consisting of the origin satellite number, the destination satellite number, and the sequence number.

[0085] MT (Message Type): CreatePath.

[0086] RP: Routing Path.

[0087] RRP: Record Routing Path.

[0088] like Figure 6 As shown, when the path connection request is passed to S7, RRP has already recorded the relevant routing path. That is, satellite node S7 can tell from the received path connection request that it originated from satellite node S4, and that the request started from satellite node S3, passed through satellite node S4, and reached satellite node S7. Similarly, during the process, satellite node S4 can also obtain the path connection request, which was sent from satellite node S3. Based on this request, satellite node S4 will forward the path connection request to satellite node S7.

[0089] Step S203: After receiving the path connection request, the destination satellite transmits the first response information to the next higher satellite node level by level using the first reverse route.

[0090] In this embodiment, after receiving the first response information transmitted by the next-level satellite node, the next-level satellite node transmits the second response information of the satellite node together with the first response information to the next-level node. The response information includes the effective time and bandwidth utilization.

[0091] In one implementation, such as Figure 7 As shown, after receiving a path connection request, satellite node S7 will transmit response information step by step along the reverse first routing path. This response information includes whether the path connection was successful or failed, bandwidth utilization, and validity period. In this embodiment, the validity period sent by satellite node S7 to satellite node S4 refers to the effective time during which the path established between S4 and S7 can stably transmit data. Specifically, since satellites in orbit are constantly moving, the communication path between satellites can only exist for a limited time. The validity period here refers to the effective time of the path's existence. Bandwidth utilization reflects the bandwidth occupancy rate of this satellite node. The upper limit of the data transmission rate of a satellite node is fixed, but a satellite node may be operating multiple routing paths simultaneously, so the bandwidth available for the first routing path is not full. Bandwidth utilization reflects the upper limit and stability of the current channel's transmission capacity.

[0092] In this embodiment, the endpoint satellite S7 first sends the corresponding information to the satellite node S4, and then the satellite node S4 transmits its own response information and the response information sent by the endpoint satellite S7 to the starting satellite S3.

[0093] Step S204: The originating satellite receives a response message from a secondary satellite node.

[0094] In one implementation, the response information received by the originating satellite S3 includes the response information from satellite node S4 and the response information sent by S7 to satellite node S4.

[0095] Step S205: Establish a routing path table in the form of inter-satellite labels based on the response information and the routing path.

[0096] In this embodiment, an inter-satellite label-based routing path table is established using the collected response information and routing paths. In this embodiment, satellite nodes assign labels to the first routing path. For example, a satellite node may have multiple labels, and one of these labels will be uniquely used on a specific path, such as the first routing path. This label is called the inter-satellite label. The inter-satellite label not only reflects the unique satellite node information it represents, but also represents a specific path. The Routing Path Table (RPT): The routing path table records a series of connection-oriented virtual transmission channels, i.e., label-switched paths.

[0097] In one implementation, such as Figure 12 As shown, for example, satellite node (6,7) has ten unused inter-satellite labels. However, during path establishment, satellite node (6,7) will assign a separate inter-satellite label for this routing path, after which this inter-satellite label and this path are bound together. For example, if the assigned inter-satellite label is S9, representing the first routing path, then when satellite node (6,7) receives data transmitted from other satellite nodes containing the inter-satellite label S9, it indicates that the information transmission path at this time is the first routing path. Based on the first routing path, the next-level satellite node to be transmitted can be obtained, and finally, the information is transmitted to the destination satellite. In this embodiment, the inter-satellite label requires 4 bytes.

[0098] In this embodiment, an inter-satellite label-based routing table is established by combining the response information and the routing path. It should be noted that the response information here includes both the response information from the originating satellite to gateway node A, and the routing table is established by combining this routing information. Then, the routing table is distributed via the Label Path Distribution Protocol (LPDP). Specifically, the routing table is synchronized to each satellite node in the first routing path via LPDP, and also to the ground gateway.

[0099] The routing path table with inter-satellite labels has fewer entries, resulting in faster query speeds and higher forwarding efficiency during synchronous forwarding.

[0100] Step S30: The gateway node sends a message to the satellite node.

[0101] In this embodiment, the gateway node sends a message to the originating satellite. This message is a data message.

[0102] In one implementation, data is ultimately transmitted from gateway node A to terminal B. The first routing path is as follows: Figure 8 As shown, the gateway node sends a message to the originating satellite, which includes information about the destination satellite.

[0103] In a preferred embodiment, such as Figure 9 As shown, the transmission of destination satellite information uses static tags, which include the destination satellite's information. TargetID (target identifier) ​​is the network element number of the destination satellite.

[0104] Step S40: Query the first routing path for message transmission based on the routing path table and the destination satellite information in the message.

[0105] In this embodiment, the originating satellite obtains a first route path to the destination satellite based on the information from the destination satellite. This first route path is the main path for data communication between the originating and destination satellites. Subsequent message transmission also follows this main path.

[0106] Step S50: Based on the first routing path information, the message is sent from the originating satellite to the destination satellite using a label method.

[0107] In this embodiment, tags are used as the information transmission method between satellite nodes. Unlike IP addresses, using tags for inter-satellite communication avoids the frequent parsing of IP addresses in the packets by the satellite nodes during transmission.

[0108] Preferably, in one specific implementation, the message is sent from the originating satellite to the destination satellite via step S501.

[0109] Step S501: Selectively push, exchange, or pop inter-satellite tags in the message according to the location of the transmitting satellite in the routing path and the first routing path information.

[0110] In this embodiment, the transmitting satellite and the receiving satellite are necessarily two adjacent satellite nodes, meaning they must be adjacent nodes on the same routing path. The transmitting and receiving satellites are relative; the transmitting satellite is responsible for sending messages to the receiving satellite or the corresponding terminal. As explained in step S205, the inter-satellite label is a unique identification label for the receiving satellite corresponding to that path, and the receiving satellite determines the first routing path based on the inter-satellite label.

[0111] In this embodiment, the tag operation types include tag push, tag swap, and tag pop, which are the basic actions of tag forwarding.

[0112] Push: When an IP packet enters the IP gateway, the IP gateway adds a new tag before the GSE header at layer 2 of the packet, indicating the satellite number connected to the destination terminal.

[0113] Swap: When an edge satellite receives a message that the destination terminal is not on its own satellite, it searches the routing table and swaps the destination terminal with an inter-satellite label.

[0114] Pop: When a message arrives at the edge satellite where the destination terminal is located, all tags in the message are removed, and the target terminal is located based on the GSE header address.

[0115] It should be noted that the first routing path has its own symmetrical reverse transmission path. This path is largely the same as the first routing path in terms of information transmission, and will not be elaborated here.

[0116] In one implementation, the situation is divided into three cases based on the different positions of the transmitting satellite in the routing path. That is, when the transmitting satellites are the origin satellite, the destination satellite, or the intermediate transmission satellite, the operation of the inter-satellite tag is different, specifically in steps S5011-5013:

[0117] Step S5011: If the transmitting satellite is the originating satellite, the inter-satellite label corresponding to the secondary satellite node is obtained according to the first routing path information, and the inter-satellite label corresponding to the secondary satellite node is pushed into the message. The originating satellite sends the message with the inter-satellite label to the secondary satellite node.

[0118] In this embodiment, the secondary satellite node refers to the receiving satellite of the originating satellite.

[0119] In one implementation, the originating satellite has already obtained the first routing path information in step S40. Then, it uses the first routing path information to look up the inter-satellite label corresponding to the secondary satellite node in the routing path table, adds the inter-satellite label corresponding to the satellite node to the message header, and then sends the message with the inter-satellite label to the secondary satellite node.

[0120] Step S5012: If the sending satellite is the destination satellite, the inter-satellite tag in the message will pop up, and the destination satellite will send the data packet to the terminal according to the link layer address in the message.

[0121] In this embodiment, the destination satellite pops the inter-satellite tag from the message header and then sends the data packet to the terminal according to the link layer address.

[0122] In one implementation, the link layer address of the popped-up message can be obtained by parsing it, and the message is then sent to the corresponding terminal based on the link layer address. The terminal here can be a gateway, a mobile terminal, or other wireless device capable of receiving satellite signal transmissions.

[0123] Step S5013: If the transmitting satellite is an intermediate transmission satellite, after receiving the message sent by the upper-level satellite node, the inter-satellite label corresponding to the next-level satellite node is obtained according to the first routing path information, and the inter-satellite label in the received message is exchanged based on the inter-satellite label corresponding to the next-level satellite node. The intermediate transmission satellite sends the message with the inter-satellite label to the next-level satellite node.

[0124] In this embodiment, the intermediate transmission satellite first obtains the first routing path, and then obtains the inter-satellite label corresponding to the next-level satellite node based on the first routing path information.

[0125] In one implementation, the corresponding first routing path is obtained by querying the routing path table and the inter-satellite labels in the received messages sent from the upstream satellite node. Specifically, since each inter-satellite label corresponds to a unique path, the intermediate transmitting satellite can determine the routing path for the message transmission by combining the inter-satellite label in the message with its routing path table. After finding the corresponding path, the inter-satellite label corresponding to the next-level satellite node can be determined based on the first routing path information. The inter-satellite label corresponding to the next-level satellite node is then used to replace the inter-satellite label in the header of the received message, i.e., a swap operation. The intermediate transmitting satellite then sends the message containing the inter-satellite label of the next-level satellite node to the next-level satellite node.

[0126] It should be noted that some paths do not have intermediate transmission satellites, and the first route path is only composed of the origin satellite and the destination satellite. Therefore, the switching step is omitted in this case.

[0127] In this embodiment, during data transmission, IP packet header compression and Layer 2 data encryption are first performed at the gateway side. Then, Layer 2 (Link Layer) routing is used to complete the inter-satellite transmission. Upon arrival at the user terminal, the Layer 2 data is decrypted, and the packet header and IP datagram are restored. This embodiment uses inter-satellite tags to ensure that only one hop occurs at the network layer during packet transmission. Furthermore, during data transmission, frequent IP address resolution, compression, and decompression are unnecessary, facilitating data forwarding between satellites and increasing the efficiency of inter-satellite data transmission compared to the IP address method. Using tags, compared to tag stacks, reduces the length of data packets, which is beneficial for information transmission.

[0128] Example 2:

[0129] Most of the content in this embodiment is the same as in Embodiment 1, except for step S50. In this embodiment, the message is sent from the originating satellite to the destination satellite through steps S502-S503.

[0130] Step S502: Generate static path labels based on the first routing path information.

[0131] In this embodiment, the static path label includes origin satellite information, destination satellite information, and path information.

[0132] In one implementation, preferably, such as Figure 11 As shown. When the gateway node sends a message to the originating satellite, the originating satellite receives the destination static label and obtains the first routing path information by parsing the destination static label. The path static label is then obtained from the first routing path information. In this embodiment, the path static label includes a path number (PathID). The path number includes originating satellite information, destination satellite information, and path information. The satellite node obtains the information of the next satellite node to send the message by reading the path static label.

[0133] Step S503: Send the message from the origin satellite to the destination satellite according to the path static label.

[0134] In this embodiment, the originating satellite sends the message to the destination satellite based on the path static label.

[0135] In one implementation, such as Figure 11The path static label shown requires 6 bytes, with more bytes needed for the path number. However, compared to inter-satellite labels, path static labels don't require frequent label swapping, although they do require more bytes. Path static labels also reduce the need for frequent compression and decompression of IP addresses during transmission.

[0136] Example 3:

[0137] Most of the content in this embodiment is the same as in Embodiment 1. The difference is that this embodiment provides a solution when the message fails to be sent, such as... Figure 13 As shown, the specific steps are S601-S603, as follows:

[0138] When an inter-satellite link becomes congested or a satellite fails, the satellite network topology changes. Routes pre-defined in the routing table become invalid, meaning they cannot transmit data effectively. At this point, routes are recalculated based on the current network topology and added to the routing table until the link or satellite becomes valid again.

[0139] Step S601: Obtain the second routing path based on the information of the destination satellite and the routing path table.

[0140] In this embodiment, when a satellite node fails to send a message to the next-level satellite node along the first routing path, it searches for a second routing path.

[0141] In one implementation, a satellite node's routing path table contains multiple paths, all of which are paths through which the satellite node can transmit information. Therefore, when a satellite node cannot successfully transmit a message along the first routing path, a new routing path is calculated based on the routing path information in the routing path table and the information of the destination satellite to which the message needs to be sent. This new routing path is the second routing path.

[0142] Step S602: Form a label stack of corresponding routing path information based on the second routing path.

[0143] In this embodiment, the tag stack includes multiple tag segments, each representing a satellite node tag in the second routing path. Data is transmitted using a tag stack.

[0144] In one implementation, the formed tag stack is as follows: Figure 4 As shown, the specific steps for forming the tag stack in this embodiment are largely the same as those for forming the tag stack in step S201 of embodiment 1, and will not be repeated here.

[0145] Step S603: The label segments are arranged in the order of the satellite nodes in the second routing path, wherein the satellite nodes determine the next-level satellite node to which the label segments need to be sent based on the arrangement order of the label segments.

[0146] In this embodiment, a tag stack is used to form a new transmission path when message transmission fails, and the message is sent according to the new path, thus solving the technical problem of message transmission failure during transmission. The system simultaneously supports centralized routing calculated by the ground control center and distributed routing calculated by the on-board processing unit. When the centralized routing path encounters an error during transmission, the distributed routing path is used to continue transmission, increasing the robustness of the system.

[0147] In one implementation, with Figure 4 Taking this as an example, let's explain in detail the working principle between the tag stack and the node satellite. Specifically:

[0148] LT (Label Type): 0 indicates a path static label based on the path ID PathID, 1 indicates a destination static label based on the destination network element ID TargetID, 2 indicates an inter-satellite label based on the dynamic ID dynamically assigned by the satellite, and 3 indicates a label stack.

[0149] S (Signaling & Management Flag): 0 indicates data, 1 indicates control and management signaling.

[0150] E (Encryption Flag): 0 indicates no encryption, 1 indicates encryption.

[0151] D (Direction Flag): 0 indicates forward direction, 1 indicates reverse direction.

[0152] M (Mesh Flag): 0 indicates data between the gateway and the terminal, and 1 indicates Mesh data.

[0153] T(Control Type): 0 indicates forward signaling, and 1 indicates reverse signaling. This field is meaningless when S is 0.

[0154] Reserve: Reserved space.

[0155] Current Entry: Represents the segment index that the current network element needs to process, with 16 items in total, from 0 to 15.

[0156] Last Entry: Indicates the index of the last segment to be processed, ranging from 0 to 15 (16 segments in total). If Last Entry is the same as Current Entry, it means that the last segment has been processed. Last Entry + 1 indicates the total number of segments, which determines the length of the routing header.

[0157] TTL (Time to Live): When this value is 1 or 0, data will no longer be forwarded and will be discarded.

[0158] Segment0-Segment N-1: 16-bit network element number. The routing management card and link gateway on the satellite each have their own network element number.

[0159] First, let's explain the situation when the tag stack is transmitted between different satellite nodes. In this embodiment, the methods for processing the tag stack are different depending on whether a fixed-length Routing Header is used or a dynamic Routing Header is used.

[0160] Specifically, with a fixed-length Routing Header, the Last Entry remains unchanged throughout the routing path, while the Current Entry is incremented by 1 after each satellite node, indicating the completion of a segment. With a dynamic Routing Header, the Current Entry moves forward along the processing path, but remains constant. Meanwhile, the Last Entry is decremented by 1 to indicate the completion of a segment.

[0161] In this embodiment, the system first checks whether the segment corresponding to the Current Entry is the current network element. If it is not, a transmission error is indicated. At this point, steps S601-S603 are used to add a new routing header and send it to the next network element, or an error is reported to the source network element. The source network element is the starting network element of the path corresponding to this label stack. If the current network element is not connected to the next segment, the error reporting execution procedure described above is also initiated.

[0162] When the data is received from a local network element, the satellite node, after receiving the data, will execute different plans based on whether it is the last hop (last segment). If it is the last hop, the control process will handle it separately, distinguishing between control and management through different ports. If it is not the last hop, and the next segment is to the feeder or user line, it is local satellite data, popping up all tags. Forward and mesh data are sent to the user terminal according to the next segment, and in reverse, the data is sent to the feeder according to the next segment. When the next segment is a connected satellite node, it is inter-satellite data, popping up current data, and sent to the next network element according to the next segment.

[0163] In this embodiment, a path starlink is defined as follows: a path starlink is a satellite link composed of multiple node satellites, which, from the outside perspective, is equivalent to a single satellite node. Specifically, in a satellite network, the length of a link between satellites will not exceed MAXPL (Maximum Path Length). That is, when MAXPL is 5, there will be no routing path consisting of a link between six satellite nodes, such as S1-S2-S3-S4-S5-S6. Paths exceeding this length will not be created within the satellite network and require cross-domain routing. Paths exceeding MAXPL are split into multiple paths that meet this length, and each path is established separately. When long-path transmission is required, multiple paths are used for forwarding through border nodes. That is, the sender passes the data packet to the farthest border node in the autonomous system, and then that node forwards it to the final destination. In this embodiment, the intermediate transmission satellite can be a single satellite or a path starlink in the transmission process.

[0164] Specifically, it should be noted that although the steps in the above embodiments are described in a specific order, those skilled in the art will understand that in order to achieve the effects of the present invention, different steps do not necessarily have to be executed in such an order. They can be executed simultaneously (in parallel) or in other orders, and these variations are all within the scope of protection of the present invention.

[0165] Those skilled in the art will understand that all or part of the processes in the method of the above-described embodiment of the present invention can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable file, or some intermediate form. The computer-readable storage medium can include any entity or device capable of carrying the computer program code, a medium, a USB flash drive, a portable hard drive, a magnetic disk, an optical disk, a computer memory, a read-only memory, a random access memory, an electrical carrier signal, a telecommunication signal, and a software distribution medium, etc. It should be noted that the content included in the computer-readable storage medium can be appropriately added or removed according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, the computer-readable storage medium does not include electrical carrier signals and telecommunication signals.

[0166] Furthermore, the present invention also provides a control device. In one embodiment of the control device according to the present invention, the control device includes a processor and a storage device. The storage device can be configured to store a program for executing the low-Earth orbit satellite network routing method of the above-described method embodiments. The processor can be configured to execute the program in the storage device, which includes, but is not limited to, a program for executing the low-Earth orbit satellite network routing method of the above-described method embodiments. For ease of explanation, only the parts related to the embodiments of the present invention are shown; for specific technical details not disclosed, please refer to the method section of the embodiments of the present invention. This control device can be a control device device comprising various electronic devices.

[0167] Furthermore, the present invention also provides a computer-readable storage medium. In one embodiment of the computer-readable storage medium according to the present invention, the computer-readable storage medium can be configured to store a program for executing the low-Earth orbit satellite network routing method of the above-described method embodiments. This program can be loaded and run by a processor to implement the above-described low-Earth orbit satellite network routing method. For ease of explanation, only the parts related to the embodiments of the present invention are shown; for specific technical details not disclosed, please refer to the method section of the embodiments of the present invention. The computer-readable storage medium can be a storage device comprising various electronic devices. Optionally, in the embodiments of the present invention, the computer-readable storage medium is a non-transitory computer-readable storage medium.

[0168] Furthermore, it should be understood that since the various modules are only provided to illustrate the functional units of the device of the present invention, the physical devices corresponding to these modules may be the processor itself, or a part of the processor's software, hardware, or a combination of software and hardware. Therefore, the number of modules shown in the figures is merely illustrative.

[0169] Those skilled in the art will understand that the various modules in the device can be adaptively split or combined. Such splitting or combining of specific modules will not cause the technical solution to deviate from the principles of the present invention; therefore, the technical solutions after splitting or combining will fall within the protection scope of the present invention.

[0170] The technical solution of the present invention has been described above with reference to the preferred embodiments shown in the accompanying drawings. However, it will be readily understood by those skilled in the art that the scope of protection of the present invention is obviously not limited to these specific embodiments. Without departing from the principles of the present invention, those skilled in the art can make equivalent changes or substitutions to the relevant technical features, and the technical solutions after such changes or substitutions will all fall within the scope of protection of the present invention.

Claims

1. A routing method for low-Earth orbit satellite networks, characterized in that, include: In response to a message sent by a gateway node to a satellite node, a first routing path for message transmission is obtained by querying the routing path table and the information of the destination satellite in the data packet. The types of satellite nodes include: origin satellite, destination satellite, and intermediate transmission satellite. Based on the first routing path information, the message is sent from the originating satellite to the destination satellite using a tag-based method; The method for creating the connection path between the routing path table and the satellite nodes in the first routing path includes: In response to a lead packet sent by the gateway node to the originating satellite in the first routing path, the originating satellite transmits a path connection request to the next level satellite node level by level based on the first routing path information in the lead packet. The next level satellite node establishes a path connection with the previous level node after receiving the path connection request transmitted by the previous level satellite node. After receiving the path connection request, the endpoint satellite transmits the first response information to the next higher level satellite node in reverse first routing path. After receiving the first response information transmitted by the next higher level satellite node, the next higher level satellite node transmits the second response information of the satellite node together with the first response information to the next higher level node. The response information includes the effective time and bandwidth utilization. The starting satellite receives response information from the secondary satellite node; Based on the response information and the routing path, a routing path table in the form of inter-satellite labels is established. Inter-satellite labels are bound to routing paths, and inter-satellite labels include dynamic numbers dynamically assigned based on satellites.

2. The low-Earth orbit satellite network routing method according to claim 1, characterized in that, The step of sending the message from the originating satellite to the destination satellite using tags based on the first routing path information includes: During the process of the message being sent from the originating satellite to the destination satellite, Based on the position of the transmitting satellite in the routing path and the first routing path information, inter-satellite tags are selectively pushed, exchanged, or popped in the message, wherein the inter-satellite tag is a unique identification tag for the receiving satellite corresponding to the path, and the receiving satellite determines the first routing path based on the inter-satellite tag.

3. The low-Earth orbit satellite network routing method according to claim 1, characterized in that, The step of sending the message from the originating satellite to the destination satellite using tags based on the first routing path information includes: A static path label is formed based on the first route path information, wherein the static path label includes origin satellite information, destination satellite information, and path information; The message is sent from the originating satellite to the destination satellite according to the path static label.

4. The low-Earth orbit satellite network routing method according to claim 1 or 2, characterized in that, include: The routing path table and the connection path between satellite nodes in the first routing path are both created based on the first routing path, which is a virtual path calculated based on the satellite nodes. Before obtaining the first routing path for message transmission based on the routing path table and the destination satellite information in the data packet, the method further includes: The routing path table is synchronized to all satellite nodes in the routing path.

5. The low-Earth orbit satellite network routing method according to claim 1, 2, or 4, characterized in that, The selective pushing, swapping, or popping of inter-satellite tags in the message based on the position of the transmitting satellite in the routing path and the first routing path information includes: If the transmitting satellite is the originating satellite, then the inter-satellite labels corresponding to the secondary satellite nodes are obtained based on the first routing path information, and The inter-satellite tags corresponding to the secondary satellite nodes are pushed into the message, and the originating satellite sends the message with the inter-satellite tags to the secondary satellite nodes. If the sending satellite is the destination satellite, the inter-satellite tag in the message will pop up, and the destination satellite will send the data packet to the terminal according to the link layer address in the message; If the transmitting satellite is an intermediate transmission satellite, then after receiving the message sent by the higher-level satellite node, The inter-satellite labels corresponding to the next-level satellite nodes are obtained based on the first routing path information, and the inter-satellite labels in the received messages are exchanged based on the inter-satellite labels corresponding to the next-level satellite nodes. The intermediate transmission satellite sends the messages with inter-satellite labels to the next-level satellite nodes.

6. The low-Earth orbit satellite network routing method according to claim 4, characterized in that, The routing path information is expressed in the form of a tag stack, which includes multiple tag segments, each of which represents the network element number tag of one of the satellite nodes in the routing path; The tag segments are arranged sequentially according to the order of the satellite nodes in the routing path, wherein the satellite nodes are determined to be the next-level satellite nodes to which the data needs to be sent based on the order of the tag segments. The path connection request includes the tag stack; When a satellite node receives a path connection request from the previous node, it pops the tag segment belonging to its own satellite node from the tag stack. The path connection request is sent to the next-level satellite node according to the order of the tag segments in the popped-up tag stack.

7. The low-Earth orbit satellite network routing method according to any one of claims 1-6, characterized in that, When a satellite node fails to send a message to the next level satellite node along the first routing path, it obtains the second routing path based on the information of the destination satellite and the routing path table. A label stack corresponding to the routing path information is formed based on the second routing path, wherein the label stack includes multiple label segments, and each label segment represents one of the satellite node labels in the second routing path; The tag segments are arranged sequentially according to the order of the satellite nodes in the second routing path, wherein the satellite nodes determine the next-level satellite node to which the data needs to be sent based on the arrangement order of the tag segments.

8. A control device, comprising a processor and a storage device, said storage device being adapted to store a plurality of program codes, characterized in that, The program code is adapted to be loaded and run by the processor to perform the low-Earth orbit satellite network routing method according to any one of claims 1 to 7.

9. A computer-readable storage medium storing a plurality of program codes, characterized in that, The program code is adapted to be loaded and run by a processor to perform the low-Earth orbit satellite network routing method according to any one of claims 1 to 7.

Images