Network routing method, and routing device and storage medium
By dividing network areas according to the node type and capabilities of satellite nodes, and determining the routing table for in-domain or cross-domain forwarding, the problem of large-scale routing computing overhead in large-scale satellite constellations networks is solved, and routing stability and convergence speed are improved.
Patent Information
- Application Number
- PCT/CN2023/143471
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-22
- Filing Date
- 2023-12-29
- Publication Date
- 2024-11-28
AI Technical Summary
Traditional IGP routing protocols are difficult to adapt to large-scale satellite constellations networks, resulting in frequent link state changes, large routing computing overhead, frequent routing reconvergence and routing oscillation.
By dividing network areas according to the node type and node capabilities of satellite nodes, determining the network area to which the destination node of the data packet belongs, and determining the routing table based on the region for intra-domain or cross-domain forwarding, reducing the maintenance of link status information and routing calculation of a single node Overhead.
It improves routing stability and convergence speed, adapts to burst link failures and frequent link characteristics changes, and reduces the waste and occupation of network resources.
Smart Images

Figure CN2023143471_28112024_PF_FP_ABST
Abstract
Description
Network routing method, routing device and storage medium
[0001] Related applications
[0002] This application claims priority to Chinese patent application No. 202310583053.X filed on May 22, 2023, the entire contents of which are incorporated by reference into this application. Technical Field
[0003] The present application relates to the field of network technology, and in particular to a network routing method, routing device, and storage medium. Background Art
[0004] In recent years, low-orbit satellites have garnered increasing attention due to their numerous advantages, including smaller antenna size, lower transmission power, and shorter communication latency. As satellite constellations become increasingly low-orbit and large-scale, the number of nodes in future large-scale constellations could reach thousands, or even tens of thousands (e.g., SpaceX and StarNet). This, in turn, places higher demands on network routing technology.
[0005] Compared to traditional terrestrial networks, satellite networks have typical characteristics such as highly dynamic topology, predictable inter-node link states, and limited onboard resources. This makes traditional IGP (Interior Gateway Protocol) routing technology difficult to adapt to satellite networks. This is because traditional IGP routing protocols are limited in the number of network nodes they can support within a single domain, making it difficult to manage large-scale constellations without domain division. Furthermore, as the dynamic nature of network topology increases, there will be more link state changes and information notifications, increasing routing calculation and protocol overhead, resulting in frequent routing reconvergence and even routing oscillation. To address this issue, routing protocols often utilize network domain division to reduce the amount of link information that needs to be maintained within a single domain.
[0006] Existing network region division methods generally include backbone and non-backbone areas. Backbone areas maintain detailed routing information for all network areas within their network; non-backbone areas are typically built around the backbone area, meaning that the backbone area participates in traffic forwarding between all areas. This requires backbone nodes to possess higher performance and assume primary data forwarding responsibilities. However, in satellite networks, especially those with single-layer satellite constellations, satellite node performance is generally equal and limited. Simply utilizing existing routing region division methods can easily lead to congestion in backbone areas. Furthermore, due to the dynamic nature of satellite network topology, inter-node connectivity and network information constantly change. Simply utilizing existing routing region division methods requires constant exchange of routing information between backbone and non-backbone areas to ensure inter-area traffic forwarding. Therefore, existing network region division methods still face challenges in large-scale satellite constellation networks, where multiple link state changes and information notifications occur, increasing routing computation and protocol overhead, leading to frequent routing reconvergence and even routing oscillation.
[0007] Summary of the Invention
[0008] The main purpose of this application is to provide a network routing method, routing device and storage medium, aiming to solve the routing problem in large-scale satellite constellation networks and reduce the link state information maintenance and routing calculation overhead of a single node.
[0009] To achieve the above objectives, the present application provides a network routing method, which includes:
[0010] Determine the destination address of the data packet to be forwarded by the source node in the satellite node;
[0011] Determining a network area to which the destination node belongs according to the destination address, wherein the network area is obtained by dividing the satellite constellation network according to the node type and node capability of the satellite node;
[0012] A corresponding routing table is determined according to the network area to which the destination node belongs, and the data packet is forwarded within a domain or across domains according to the determined routing table.
[0013] An embodiment of the present application further provides a routing device, which includes a memory, a processor, and a network routing program stored in the memory and executable on the processor. When the network routing program is executed by the processor, the steps of the network routing method described above are implemented.
[0014] An embodiment of the present application further provides a computer-readable storage medium, on which a network routing program is stored. When the network routing program is executed by a processor, the steps of the network routing method described above are implemented. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] FIG1 is a schematic diagram of a system architecture involved in an embodiment of the network routing method of the present application;
[0016] FIG2 is a flow chart of a first exemplary embodiment of a network routing method of the present application;
[0017] 3 is a schematic diagram of a process for configuring the connection establishment capability between a domain edge node and a cross-domain neighbor node involved in a third exemplary embodiment of the network routing method of the present application;
[0018] FIG4 is a schematic diagram of a process for configuring a connection maintenance capability between a domain edge node and a cross-domain neighbor node according to a third exemplary embodiment of the network routing method of the present application;
[0019] FIG5 is a schematic diagram of a scenario of a sudden failure within a domain involved in a third exemplary embodiment of the network routing method of the present application;
[0020] FIG6 is a flow chart of a fourth exemplary embodiment of the network routing method of the present application;
[0021] 7 is a schematic diagram of another process of updating the network information of satellite nodes and the intra-domain network topology involved in the fourth exemplary embodiment of the network routing method of the present application;
[0022] FIG8 is a flowchart illustrating a fourth exemplary embodiment of a network routing method of the present application for configuring a cross-domain connection relationship maintenance capability of a satellite node;
[0023] FIG9 is a schematic diagram of a scenario in which a sudden failure of a satellite constellation network is encountered in accordance with a fourth exemplary embodiment of the network routing method of the present application;
[0024] FIG10 is a schematic diagram of a process for configuring the inter-domain network topology maintenance capability of a satellite node involved in a fourth exemplary embodiment of the network routing method of the present application;
[0025] FIG11 is a schematic diagram of a process for determining an inter-domain routing table according to a fifth exemplary embodiment of the network routing method of the present application;
[0026] FIG12 is a schematic diagram of network area division of a satellite constellation network at a certain moment in Example 1 of the network routing method of the present application;
[0027] FIG13 is a schematic diagram of node distribution within a certain network area in Example 1 of the network routing method of the present application;
[0028] FIG14 is a schematic diagram of network area division of a satellite constellation network at a certain moment in Example 2 of the network routing method of the present application;
[0029] FIG15 is a schematic diagram of a node path for forwarding data from one network area to another network area in Example 2 of the network routing method of the present application;
[0030] FIG16 is a schematic diagram of functional modules of an embodiment of a network routing device of the present application;
[0031] FIG17 is a functional module diagram of an embodiment of a routing device belonging to network routing of the present application.
[0032] The realization of the objectives, functional features and advantages of this application will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION
[0033] It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application.
[0034] The system architecture involved in the embodiment of the present application can be referred to Figure 1.
[0035] As shown in Figure 1, the satellite constellation network system involved in the embodiment of the present application is composed of a plurality of satellite nodes, each of which performs satellite along-track motion in its own orbital plane. The satellite constellation network is divided into a plurality of network regions, each of which contains a group of satellite nodes, wherein each satellite node belongs to and only belongs to one network region.
[0036] As shown in Figure 1, in a network area, such as network area 1, satellite nodes within the network area can be divided into domain-edge nodes located at the edge of the network area, such as nodes 1, 2, 3, 4, 6, 7, 8, and 9, and domain-in-domain nodes located within the encirclement of the domain-edge nodes, such as node 5, based on their location characteristics. In two adjacent network areas, such as network area 1 and network area 3, domain-edge node 8 in network area 1 and domain-edge node 2 in network area 3 are each other's cross-domain neighbor nodes in the neighboring area, based on the adjacency relationship between domain-edge node 8 in network area 1 and domain-edge node 2 in network area 3.
[0037] When data is forwarded based on the satellite constellation network system, intra-domain forwarding and cross-domain forwarding are distinguished according to the network area to which the source node in the satellite node belongs and the network area to which the destination node belongs. Referring to Figure 1, when the satellite node 5 in network area 1 serves as the source node for data forwarding and the satellite node 8 in network area 1 serves as the destination node for data reception, that is, the network area to which the source node belongs and the network area to which the destination node belongs are the same network area, data forwarding is performed by intra-domain forwarding. When the satellite node 5 in network area 1 serves as the source node for data forwarding and the satellite node 2 in network area 3 serves as the destination node for data reception, that is, the network area to which the source node belongs and the network area to which the destination node belongs are not the same network area, data forwarding is performed by cross-domain forwarding.
[0038] Based on the above system architecture but not limited to the above architecture, an embodiment of the network routing method of the present application is proposed.
[0039] 2, which is a flow chart of a first exemplary embodiment of a network routing method of the present application. In this embodiment, the network routing method includes:
[0040] Step S11: determining the destination address of the data packet to be forwarded by the source node in the satellite node.
[0041] This embodiment is targeted at satellite constellation networks, especially large-scale satellite constellation networks, and addresses the problem in large-scale satellite constellation networks of multiple link status changes and information notifications, which increases routing calculation and protocol overhead, resulting in frequent routing reconvergence and even routing oscillation.
[0042] In one embodiment, when a source node in a satellite node needs to forward a data packet to a destination node, a destination address of the data packet to be forwarded by the source node is determined. In this embodiment, the satellite node that receives the data packet forwarded by the source node is used as the destination node, and the satellite address of the destination node is the destination address.
[0043] Step S12: determining the network area to which the destination node belongs according to the destination address, wherein the network area is obtained by dividing the satellite constellation network according to the node type and node capability of the satellite node.
[0044] In one embodiment, the network area to which the destination node belongs is determined based on the destination address of the data packet to be forwarded. In this embodiment, the network area is obtained by dividing the satellite constellation network according to the node type and node capability of the satellite node. Among them, the classification standard of the node type may include but is not limited to the node type classification standard formulated according to the location characteristics of the satellite node, the node type classification standard formulated according to the software and hardware configuration characteristics of the satellite node, and / or the node type classification standard formulated according to the dynamic and static motion characteristics of the satellite node. Node capability refers to the ability of the satellite node configuration to process work tasks, which may include but is not limited to the communication connection capability, computing capability, storage capability, monitoring capability and / or interception capability of the satellite node.
[0045] In one embodiment, based on the regularity and predictability of the satellite constellation network topology, the satellite constellation network is divided according to the node type and node capabilities of the satellite nodes to obtain a number of network regions. After the satellite constellation network is divided into network regions, each satellite node in the satellite constellation network belongs to and only belongs to one network region; each network region consists of a group of satellite nodes. This embodiment does not impose specific restrictions on the number of network regions or the number of satellite nodes contained in each network region. Subsequently, the network region to which the destination node belongs is uniquely determined based on the destination address of the data packet to be forwarded.
[0046] Step S13: determining a corresponding routing table according to the network area to which the destination node belongs, and forwarding the data packet within a domain or across domains according to the determined routing table.
[0047] In one embodiment, a routing table corresponding to forwarding a data packet from a source node to a destination node is determined based on the network area to which the destination node belongs, and the data packet is forwarded within or across domains based on the determined routing table. Specifically, if the source node and the destination node belong to the same network area, the data packet is forwarded within the domain based on the routing table; if the source node and the destination node belong to different network areas, the data packet is forwarded across domains based on the routing table.
[0048] Compared with the existing technology, the solution of this embodiment divides the network area according to the node type and node capability of the satellite node, distinguishes between intra-domain and cross-domain routing, and can effectively utilize the predictability of the satellite constellation network topology, limit the impact of link failures and link switching to the local network, reduce the link status information maintenance and routing calculation overhead of a single node, thereby improving routing stability and convergence speed, and adapting to network changes caused by sudden link failures and frequent changes in link characteristics.
[0049] Based on the embodiment shown in FIG. 2 , in this embodiment, before the step of determining the network area to which the destination node belongs according to the destination address, the network routing method further includes:
[0050] Step S100, configuring the node type and node capability of the satellite node based on the network area model;
[0051] Step S101: Divide the satellite constellation network into several network areas according to the node types and node capabilities.
[0052] In this embodiment, steps S100 - S101 are performed before step S11 . In other embodiments, steps S100 - S101 may also be performed between step S11 and step S12 .
[0053] Compared with the embodiment shown in FIG2 above, this embodiment also includes a solution for dividing the satellite constellation network area.
[0054] In one embodiment, the node type and capabilities of satellite nodes are configured based on a network area model, where the network area model is used to determine the basic area shape and area range of the network area. The basic area shape may include, but is not limited to, a regular polygonal shape, and the area range can be planned by the network management and control layer. In this embodiment, configuration refers to the process of setting or adjusting relevant programs through technical means in software engineering. By configuring the node type and node capabilities of satellite nodes, they can meet the requirements of dividing the satellite constellation network.
[0055] In one embodiment, a network region model is used to determine the basic shape and range of a network region. Based on the determined basic shape and range, satellite nodes are assigned corresponding node types according to node type classification standards. Based on the satellite nodes' workloads, corresponding node capabilities are assigned to the satellite nodes. The entire satellite constellation network is then divided into several network regions based on the node types and capabilities assigned to the satellite nodes.
[0056] In one embodiment, the node types include domain edge nodes located at the edge of the network area and domain mid-nodes located in the enclosed area of the domain edge nodes. The domain edge nodes have an adjacency relationship with other nodes in the network area where the domain edge nodes are located and adjacent nodes in the neighboring area of the network area where the domain edge nodes are located. The domain mid-nodes do not have an adjacency relationship with other nodes outside the network area where the domain mid-nodes are located.
[0057] In one embodiment, based on the planned location characteristics of satellite nodes in the network area model, satellite nodes are divided into domain-edge nodes located at the edge of the network area and domain-mid nodes located within the area surrounded by the domain-edge nodes. Domain-edge nodes have adjacency relationships with other nodes within the network area where the domain-edge nodes are located, and also have adjacency relationships with adjacent nodes in the neighboring area of the network area where the domain-edge nodes are located. In contrast, domain-mid nodes do not have adjacency relationships with other nodes outside the network area where the domain-mid nodes are located. That is, domain-mid nodes only have adjacency relationships with other nodes within the network area where the domain-mid nodes are located.
[0058] By configuring the node types of satellite nodes and the adjacency relationship between nodes, the divided network area has a node type distribution basis in which satellite nodes outside the network area are unaware of changes in the network area.
[0059] Based on the above second embodiment, in this embodiment, the network area model is a quadrilateral network area model.
[0060] In a satellite constellation network, a satellite typically establishes links with the two satellites in front and behind it in the same orbital plane, and with satellites on the left and right sides of the satellites in different orbital planes. Therefore, this embodiment uses a quadrilateral network area model as the basic model for network area division. That is, the divided network areas are adjacent to the network areas in front, behind, left, and right of the network area. This ensures that the adjacency relationship between satellite nodes in each network area, as well as the adjacency relationship between network areas, does not change with dynamic changes in satellite topology.
[0061] In this embodiment, the above step S100 of configuring the node type and node capability of the satellite node based on the network area model may include:
[0062] Step S1001: configuring the node type of the satellite node based on the quadrilateral network area model.
[0063] In one embodiment, the node types of satellite nodes are configured according to a quadrilateral network area model, wherein the node types may include domain-edge nodes located at the edge of the quadrilateral network area and domain-mid nodes located within the enclosed area of the domain-edge nodes.
[0064] Step S1002: When the node type is a domain edge node, configure the node capabilities of the domain edge node, wherein the node capabilities of the domain edge node include one or more of the capability to establish a connection with a cross-domain neighboring node, the capability to maintain a connection, and the capability to isolate network information between regions. The cross-domain neighboring node is an adjacent node in a neighboring area that has an adjacent relationship with the domain edge node.
[0065] In one embodiment, when the node type of the satellite node is a domain edge node, the node capability of the domain edge node is configured based on a quadrilateral network area model, wherein the node capability of the domain edge node includes one or more of the following: the capability to establish a connection between the domain edge node and a cross-domain neighboring node, the capability to maintain a connection between the domain edge node and a cross-domain neighboring node, and the capability to isolate network information between the domain edge node and the cross-domain neighboring node. A cross-domain neighboring node refers to an adjacent node located in a neighboring area that has an adjacency relationship with the domain edge node; the capability to establish a communication connection link between satellite nodes; the capability to maintain a connection link refers to the capability to monitor the communication connection link between satellite nodes; and the capability to isolate network information between regions refers to the capability to intercept link status information transmitted between network areas.
[0066] This embodiment configures the node type of the satellite node based on the quadrilateral network area model; when the node type is a domain edge node, the node capability of the domain edge node is configured, wherein the node capability of the domain edge node includes one or more of the capability to establish connections with cross-domain neighbor nodes, the capability to maintain connections, and the capability to isolate network information between regions. This allows satellite nodes within the network area to transmit information to each other, while satellite nodes outside the network area are unaware of changes within the network area.
[0067] 3, which is a flow chart of configuring the connection establishment capability of a domain edge node and a cross-domain neighbor node according to a third exemplary embodiment of the network routing method of the present application. The steps of configuring the connection establishment capability of the domain edge node and the cross-domain neighbor node may include:
[0068] Step S201: establishing an adjacency relationship between the domain edge node and the cross-domain neighbor node;
[0069] Step S202: According to the adjacency relationship between the domain edge node and the cross-domain neighbor node, the area number of the network area to which the domain edge node belongs is notified to the cross-domain neighbor node;
[0070] Step S203, receiving the neighbor area number announced by the cross-domain neighbor node;
[0071] Step S204: Notify the neighbor area number to other nodes in the network area to which the domain edge node belongs, so as to complete the configuration of the connection establishment capability between the domain edge node and the cross-domain neighbor node.
[0072] In this embodiment, the domain edge node is used as an agent for external connection of the network area, and an adjacency relationship is established with the cross-domain neighbor node of the neighboring area. Based on the established adjacency relationship between the domain edge node and the cross-domain neighbor node, the area number of the network area to which the domain edge node belongs is notified to the cross-domain neighbor node. Reciprocally, the cross-domain neighbor node notifies the area number of its own network area, that is, the neighbor area number, to the domain edge node, and the domain edge node receives the neighbor area number notified by the cross-domain neighbor node. Then, the domain edge node notifies the received neighbor area number to other nodes in the network area to which the domain edge node belongs, so as to complete the configuration of the connection establishment capability of the domain edge node and the cross-domain neighbor node.
[0073] 4, which is a flow chart of configuring the connection maintenance capability of a domain edge node and a cross-domain neighbor node according to a third exemplary embodiment of the network routing method of the present application. The steps of configuring the connection maintenance capability of the domain edge node and the cross-domain neighbor node include:
[0074] Step S301: monitoring the connection relationship change between the domain edge node and the cross-domain neighbor node having the adjacency relationship;
[0075] Step S302: When the connection relationship change is an unpredictable connection relationship change, the unpredictable connection relationship change is notified to other nodes in the network area to which the domain edge node belongs, so as to complete the configuration of the connection maintenance capability between the domain edge node and the cross-domain neighbor node.
[0076] In this embodiment, the connection relationship change between the domain edge node with an adjacency relationship and the cross-domain neighbor node is divided into a predictable connection relationship change and an unpredictable connection relationship change. The connection relationship change between the domain edge node with an adjacency relationship and the cross-domain neighbor node is monitored. When the connection relationship between the domain edge node with an adjacency relationship and the cross-domain neighbor node changes to an unpredictable connection relationship change, the unpredictable connection relationship change is notified to other nodes in the network area to which the domain edge node belongs, so as to complete the configuration of the connection maintenance capability of the domain edge node and the cross-domain neighbor node. For predictable connection relationship changes, each satellite node can obtain them by self-calculation based on the planned orbital parameters.
[0077] In the event of unpredictable connection relationship changes, the domain edge nodes will notify other nodes in the network area to which they belong, while predictable connection relationship changes are obtained through self-calculation by each satellite node based on the planned orbital parameters. This can effectively utilize the predictability of the satellite constellation network topology, further reduce unnecessary link information flooding, and reduce the waste of network resources.
[0078] Referring to Figure 5, which is a schematic diagram of a scenario of a sudden failure within a domain involved in the third exemplary embodiment of the network routing method of the present application, the steps of configuring the inter-regional network information isolation capability of the domain edge node and the cross-domain neighbor node include:
[0079] Step S401, when a network change occurs in the network area to which the domain edge node belongs, intercept the flooding routing information of the influencing node in the network area to which the domain edge node belongs, so as to complete the configuration of the inter-regional network information isolation capability between the domain edge node and the cross-domain neighbor node, wherein the influencing node is a satellite node that generates flooding routing information according to the network change of the network area to which the domain edge node belongs.
[0080] In this embodiment, when a network change occurs within the network area to which a domain edge node belongs, such as a link failure or node failure, the affected satellite node within the network area to which the domain edge node belongs, i.e., the influencing node, generates flooding routing information, such as link failure information, based on the network change, and transmits the flooding routing information to other nodes within the network area to which the domain edge node belongs. When the flooding routing information of the influencing node is transmitted to the domain edge node, the domain edge node intercepts the flooding routing information of the influencing node, preventing the flooding routing information of the influencing node from passing through the domain edge node to its adjacent areas, thereby completing the configuration of the inter-regional network information isolation capability between the domain edge node and its cross-domain neighboring nodes.
[0081] As shown in Figure 5, when a sudden failure occurs in the link between satellite nodes 5 and 8 within a network area, satellite nodes 5 and 8, acting as impacting nodes, generate link failure information and flood it across the network area. When edge nodes within the network area, including satellite node 8, generate or receive this link failure information, they intercept it and flood it to other adjacent areas, preventing satellite nodes in these adjacent areas from receiving it.
[0082] This embodiment configures the inter-regional network information isolation capability between the domain edge node and the cross-domain neighboring nodes, specifically by intercepting the flooding routing information of the influencing node in the network area to which the domain edge node belongs when a network change occurs in the network area to which the domain edge node belongs, so as to complete the configuration of the inter-regional network information isolation capability between the domain edge node and the cross-domain neighboring nodes, wherein the influencing node is a satellite node that generates flooding routing information according to the network change of the network area to which the domain edge node belongs, so that the domain edge node does not flood the flooding routing information generated by the nodes in the network area to which it belongs to other network areas, and does not receive the flooding routing information generated by the nodes in other network areas, thereby reducing the occupation of network resources.
[0083] As shown in Figure 6, Figure 6 is a flow chart of a fourth exemplary embodiment of the network routing method of the present application. Based on the second or third embodiment above, in this embodiment, the node capabilities include intra-domain network information and topology maintenance capabilities, and the step of configuring the node capabilities of the satellite node based on the network area model may include:
[0084] Step S501: Establishing a connection relationship between the satellite node and the neighboring node;
[0085] Step S502, based on the connection relationship between the satellite node and the neighboring nodes, determining other nodes in the network area to which the satellite node belongs according to the network area parameters of the network area model;
[0086] Step S503, based on other nodes in the network area to which the satellite node belongs, generating a network topology within the area according to orbital parameters;
[0087] Step S504: updating the intra-domain network topology according to the first planned time interval to complete the configuration of the intra-domain network information and topology maintenance capability of the satellite node.
[0088] In one embodiment, for a satellite node within a satellite constellation network, a connection relationship between the satellite node and its neighboring nodes is established. After the connection relationship between the satellite node and its neighboring nodes is established, other nodes belonging to the network area to which the satellite node belongs are determined based on network area parameters in the network area model, where the network area parameters may include, but are not limited to, basic area shape parameters and area range parameters. In combination with the satellite node and other nodes in the network area to which the satellite node belongs, an intra-domain network topology is generated based on orbital parameters. Because the satellite constellation network topology is in dynamic change, the generated intra-domain network topology needs to be continuously updated. Because such dynamic changes are predictable, each satellite node can predict network change patterns without the need to announce routing convergence information. Leveraging the predictability of satellite motion along its orbit, the intra-domain network topology is updated according to a first planned time interval to complete the configuration of the satellite node's intra-domain network information and topology maintenance capabilities. The first planned time interval may be a change in cross-domain link connectivity and / or intra-domain link connectivity.
[0089] Referring to FIG. 7 , FIG. 7 is a schematic diagram of another process for updating the network information of a satellite node and the intra-domain network topology, as described in the fourth exemplary embodiment of the network routing method of the present application. In step S503 , after generating the intra-domain network topology based on orbital parameters and other nodes within the network region to which the satellite node belongs, the following steps may also be included:
[0090] Step S505: Notifying the network information of the satellite node to other nodes in the network area to which the satellite node belongs according to the intra-domain network topology;
[0091] Step S506, monitoring the direct link of the satellite node;
[0092] Step S507: When a sudden failure is detected on the direct link, the neighboring node is notified, and the network information of the satellite node and the intra-domain network topology are updated.
[0093] In one embodiment, based on the generated intra-domain network topology, the network information of the satellite node is notified to other nodes within the network area to which the satellite node belongs. The satellite node's direct link is continuously monitored. If a sudden failure of the satellite node's direct link is detected, the satellite node's neighbor nodes are notified, and the satellite node's network information and the intra-domain network topology are updated.
[0094] Referring to Figure 8, Figure 8 is a flow chart of configuring the cross-domain connection relationship maintenance capability of a satellite node involved in the fourth exemplary embodiment of the network routing method of the present application. In this embodiment, the node capability may also include cross-domain connection relationship maintenance capability, and the step of configuring the node capability of the satellite node based on the network area model may also include:
[0095] Step S601: Based on the connection relationship between the satellite node and the neighboring nodes, and according to the notification information of the domain edge nodes in the network area to which the satellite node belongs, a mapping relationship between the domain edge nodes and the neighboring areas is generated.
[0096] In one embodiment, based on the established connection relationship between the satellite node and the neighboring node, the domain edge node of the network area to which the satellite node belongs transmits notification information to the satellite node. The notification information of the domain edge node includes at least the information of the neighboring nodes in the neighboring area that has an adjacent relationship with the domain edge node. Based on the notification information of the domain edge node in the network area to which the satellite node belongs, a mapping relationship between the domain edge node in the network area to which the satellite node belongs and its corresponding neighboring area is generated, that is, a mapping relationship between the domain edge node and the neighboring area. The mapping relationship table between the domain edge node and the neighboring area can be referred to as shown in Table 1 below:
[0097] Table 1: Mapping relationship between domain edge nodes and neighboring areas
[0098] For a domain edge node whose inter-domain link is disconnected, the mapping relationship value between it and the neighboring area will become infinite INF.
[0099] Step S602: Calculate the connectivity between the domain edge node in the network area to which the satellite node belongs and the cross-domain neighbor node adjacent to the domain edge node according to the second planning time interval, and update the mapping relationship between the domain edge node and the neighbor area according to the connectivity to complete the configuration of the cross-domain connection relationship maintenance capability of the satellite node; and / or,
[0100] Step S603, when a sudden failure is detected in the satellite constellation network, link status information notified by the domain edge node in the network area to which the satellite node belongs is received, and the mapping relationship between the domain edge node and the neighboring area is updated according to the link status information to complete the configuration of the cross-domain connection relationship maintenance capability of the satellite node.
[0101] Because satellites constantly orbit, the generated mappings between domain-edge nodes and neighboring regions need to be continuously updated. Leveraging the predictability of satellite orbital motion, the connectivity between domain-edge nodes within the satellite node's network region and its adjacent cross-domain neighboring nodes is calculated based on a second planning interval. This second planning interval can be the time between the regional positions of different neighboring regions. Based on this connectivity, the mappings between domain-edge nodes and neighboring regions are updated to complete the configuration of the satellite node's cross-domain connectivity maintenance capability.
[0102] In one embodiment, the satellite constellation network is continuously monitored. When a sudden failure occurs in the satellite constellation network, the domain-edge node generates link state information and notifies other nodes within the network region to which the domain-edge node belongs. Satellite nodes in the same network region as the domain-edge node then receive the link state information notified by the domain-edge node and, based on the link state information, update the mapping between the domain-edge node and its neighboring regions, thereby configuring the satellite nodes' cross-domain connection maintenance capabilities.
[0103] As shown in Figure 9, when a sudden link failure is detected between domain-edge node 8 in network area 22 and cross-domain neighbor node 2 in neighbor area 26, domain-edge node 8 generates link failure information and notifies other nodes in the same network area. Other nodes in the network area receive the link status information notified by the domain-edge node and update the mapping relationship between the domain-edge node and the neighbor area based on the link status information.
[0104] Referring to Figure 10, Figure 10 is a flow chart illustrating the process of configuring the inter-domain network topology maintenance capability of a satellite node according to the fourth exemplary embodiment of the network routing method of the present application. In this embodiment, the node capability may further include the inter-domain network topology maintenance capability, and the step of configuring the node capability of the satellite node based on the network area model may further include:
[0105] Step S701: The network area to which the satellite node belongs is represented as a virtual node.
[0106] In one embodiment, to facilitate hiding network information and network changes within the satellite node's network region from external network areas, the satellite node's network region is represented as a virtual node, where the geographic location of the virtual node corresponds to a designated satellite node within the represented satellite node's network region. In other words, the abstract virtual node represents the time-varying geographic location of the satellite node's network region within the satellite constellation network.
[0107] In one embodiment, for other network areas within the satellite constellation network, each network area hides the network information and network changes within its own network area from the external network and is abstracted as a single virtual node. The geographical location of the virtual node corresponds to the designated node in the corresponding represented network area, and adjacent virtual nodes are connected by at most one edge.
[0108] Step S702, calculate the geographical locations of other virtual nodes in the satellite constellation network based on the orbital parameters of the satellite nodes in the virtual node and the regional range of the virtual node, and obtain the inter-domain network topology to complete the configuration of the inter-domain network topology maintenance capability of the satellite node.
[0109] In one embodiment, the predictability of satellite motion along the orbit is utilized, and the geographic locations of other virtual nodes in the satellite constellation network are calculated based on the orbital parameters of the satellite nodes in the network area to which the satellite nodes represent, and the area range of the virtual nodes planned based on the network area model. The inter-domain network topology is obtained based on the geographic location of each virtual node to complete the configuration of the inter-domain network topology maintenance capability of the satellite nodes.
[0110] In this embodiment, satellite nodes within each network area operate dynamic and static hybrid routing, maintaining intra-domain and inter-domain link state information bases through dynamic network monitoring and static topology prediction, thereby calculating or updating the intra-domain network topology and the mapping relationship between domain edge nodes and neighboring areas. At the same time, the inter-domain network topology is calculated or updated by abstracting the network areas into virtual nodes. Through the above method, this embodiment can more flexibly maintain intra-domain topology relationships, inter-domain topology relationships, and the mapping relationship between domain edge nodes and neighboring areas through dynamic network monitoring and static topology prediction.
[0111] Based on the above embodiment, in this embodiment, the above step S13 of determining the corresponding routing table according to the network area to which the destination node belongs may include:
[0112] Step S131 : when the network area to which the destination node belongs is the network area to which the source node belongs, determining an intra-domain routing table according to the network area to which the destination node belongs.
[0113] In one embodiment, the network area to which the destination node belongs is determined based on the destination address of the data packet to be forwarded. When the network area to which the destination node belongs is the network area where the source node is located, that is, when the destination node and the source node are in the same network area, an intra-domain routing table is determined within the network area to which the destination node belongs to forward the data packet from the source node to the destination node.
[0114] In one embodiment, when the network area to which the destination node belongs is the network area to which the source node is located, the step of determining the intra-domain routing table according to the network area to which the destination node belongs may include:
[0115] Step S1311: Calculate the intra-domain routing table based on the network area to which the destination node belongs and the intra-domain network topology.
[0116] In one embodiment, an intra-domain routing table is calculated based on the network area to which the destination node belongs and the intra-domain network topology. The intra-domain network topology can be generated based on planned orbital parameters, can be updated based on the intra-domain network topology of the previous time period based on a first planned time interval, and can be updated based on the current intra-domain network topology when a sudden failure of a direct link is detected. Entries in the intra-domain routing table may include, but are not limited to, the destination address, network mask, routing priority, routing cost, forwarding interface, and next-hop satellite address.
[0117] In one embodiment, the above step S13 of determining the corresponding routing table according to the network area to which the destination node belongs may further include:
[0118] Step S132: When the network area to which the destination node belongs is not the network area to which the source node belongs, determine an inter-domain routing table according to the network area to which the destination node belongs.
[0119] In one embodiment, when the network area to which the destination node belongs is not the network area where the source node is located, that is, when the destination node and the source node are not in the same network area, the inter-domain routing table for forwarding the data packet from the source node to the destination node is determined according to the network area to which the destination node belongs.
[0120] In one embodiment, referring to FIG. 11 , when the network area to which the destination node belongs is not the network area to which the source node belongs, the step of determining the inter-domain routing table according to the network area to which the destination node belongs may include:
[0121] Step S1321 : According to the network area to which the destination node belongs and the intra-domain network topology, a first path tree with the source node as the root node is calculated in combination with a first path algorithm.
[0122] In one embodiment, based on the network area to which the destination node belongs and the intra-domain network topology, a first path tree with the source node as the root node is calculated in combination with a first path algorithm. The calculation method is as follows: receiving routing convergence information of a domain edge node located at the edge of the network area where the source node is located, constructing a corresponding relationship between adjacent areas and edge nodes based on the routing convergence information, that is, a mapping relationship between domain edge nodes and neighboring areas, calculating an intra-domain topology matrix based on the satellite node position, including satellite orbit parameters and satellite operating time, and the intra-domain network topology, and calculating a first path tree with the source node as the root node based on the intra-domain topology matrix and the first path algorithm. The intra-domain topology matrix is established based on the connectivity relationship between intra-domain nodes, and the table of connectivity relationships between intra-domain nodes is shown in Table 2 below; the first path algorithm is based on the network area to which the destination node belongs and the intra-domain network topology, and calculates a path algorithm from the source node to the domain edge node in the same network area that can support data transmission to the network area to which the destination node belongs; the first path tree is a set of paths from the source node to the domain edge node in the network area where the source node is located that can support data transmission to the network area to which the destination node belongs.
[0123] Table 2: Connectivity table between nodes in the domain
[0124] Step S1322: According to the network area to which the destination node belongs and the inter-domain network topology, a second path tree with the network area where the source node is located as the root node is calculated in combination with a second path algorithm.
[0125] In one embodiment, based on the network area to which the destination node belongs and the inter-domain network topology, combined with the second path algorithm, a second path tree with the network area where the source node is located as the root node is obtained. The calculation method is: based on the network area where the source node is located, the network area to which the destination node belongs and the inter-domain network topology, an inter-domain reachable path is calculated based on the inter-domain topology matrix and the second path algorithm to obtain a second path tree with the network area where the source node is located as the root node.
[0126] Among them, the inter-domain network topology can be obtained by representing the network area to which the satellite node belongs as a virtual node, calculating the geographical location of other virtual nodes in the satellite constellation network according to the orbital parameters of the satellite nodes in the virtual node and the regional range of the virtual node, and calculating based on the geographical location of each virtual node; the inter-domain topology matrix is established based on the inter-domain connectivity relationship, and the inter-domain connectivity relationship table is shown in Table 3 below; the second path algorithm is an algorithm for calculating the path from the network area where the source node is located to the network area to which the destination node belongs based on the inter-domain network topology; the second path tree refers to the path with the network area where the source node is located as the root node, and is composed of the network areas passed through from the network area where the source node is located to the network area to which the destination node belongs.
[0127] Table 3: Inter-domain connectivity relationship table
[0128] Step S1323: Determine the inter-domain routing table according to the first path tree and the second path tree.
[0129] In one embodiment, the inter-domain routing table is determined based on the first path tree and the second path tree, that is, based on the path set from the source node to the domain edge node in the network area where the source node is located, and the network area passed from the network area where the source node is located to the network area to which the destination node belongs.
[0130] In one embodiment, the above step S1323 of determining the inter-domain routing table according to the first path tree and the second path tree may include:
[0131] Step S3231, determining the next hop network area of the network area to which the satellite node belongs in the second path tree;
[0132] Step S3232: searching the first path tree for a target path to the domain edge node corresponding to the next-hop network area according to the mapping relationship between the domain edge node and the neighboring area;
[0133] Step S3233: Obtain the inter-domain routing table according to the target path and the next-hop network area, wherein the inter-domain routing table includes the network area to which the destination node belongs and the next-hop network area.
[0134] In one embodiment, the second path tree is composed of the network areas traversed from the network area where the source node resides to the network area where the destination node resides. The next-hop network area of the source node's network area in the second path tree is first determined. Based on the next-hop network area, a target path in the first path tree is searched for a domain-edge node corresponding to the next-hop network area according to a mapping relationship between domain-edge nodes and neighboring areas.
[0135] Among them, the mapping relationship between the domain edge node and the neighboring area can be generated according to the announcement information of the domain edge node in the network area to which the satellite node belongs, and the connectivity between the domain edge node in the network area to which the satellite node belongs and its adjacent cross-domain neighboring node in the previous time period can be updated according to the second planning time interval. When a sudden failure in the connectivity is detected, the current mapping relationship between the domain edge node and the neighboring area can be updated according to the link status information announced by the domain edge node in the network area to which the satellite node belongs; the target path refers to a path with the source node as the root node, consisting of the nodes passed through from the source node to the corresponding domain edge node.
[0136] Based on the network area to which the destination node belongs, the inter-domain routing table is obtained according to the target path and the next-hop network area, wherein the table entries of the inter-domain routing table at least include the network area to which the destination node belongs and the next-hop network area.
[0137] In this embodiment, the inter-domain routing table entries replace the destination address and network mask in the existing network routing table with the network area to which the destination node belongs, and add the next-hop network area. In addition, the inter-domain routing table entries may also include routing priority, routing cost, forwarding interface, and next-hop satellite address. For details, please refer to the following Table 4:
[0138] Table 4: Inter-domain routing table
[0139] In the current existing technology, an additional mapping table of routing areas to which address prefixes belong is stored in each satellite node. A global routing table is generated based on the mapping table of routing areas to which address prefixes belong, the routing table within the routing area, and the routing table between routing areas for data forwarding. Since address prefixes correspond one-to-one with routing table entries, this increases the storage requirements of satellite nodes and also requires the nodes to accommodate more routing table entries, resulting in excessive resource usage. Compared to the existing technology, this embodiment greatly reduces the number of routing table entries by replacing the destination address and network mask in the existing routing table with the network area to which the destination node belongs in the table entries of the inter-domain routing table. This also avoids the storage requirements for the routing area mapping table to which address prefixes belong, further reducing the usage of network resources.
[0140] Based on the above embodiment, in this embodiment, the above step S12, the step of determining the network area to which the destination node belongs according to the destination address, may include:
[0141] Step S121, calculating the area number of the network area to which the destination node belongs based on the satellite orbit position information contained in the destination address;
[0142] Step S122: Determine the network area to which the destination node belongs based on the area ID of the network area to which the destination node belongs.
[0143] In one embodiment, a satellite constellation network typically has several orbital planes, each containing a certain number of satellite nodes, each with its own orbital position. For a destination address in a data packet to be forwarded by a specific satellite node, the region ID of the network region to which the destination node belongs is calculated based on the satellite orbital position information contained in the destination address. The corresponding network region to which the destination node belongs is determined based on the region ID of the network region to which the destination node belongs. The satellite orbital position information is stored in the address of the satellite node's communication port through addressing.
[0144] In one embodiment, the method for calculating the area number of the network area includes:
[0145] In a satellite constellation network having M orbital planes, each of which includes N satellite nodes, the region number k of the network region is calculated according to satellite orbital position information, where the satellite orbital position information is identified by (X, Y), and the formula (1) is as follows:
[0146] Where k is the region number, X is the orbital plane where the satellite node is located, and Y is the node order of the satellite node in the orbital plane. l is the number of orbits spanned by the network region, and h is the number of satellite nodes contained in a single orbital plane in the network region. l and h are network region parameters that can be pre-planned by the network management layer. △ is the offset value when calculating the region number.
[0147] Through the above method, each satellite node can determine the area number of its own network area, and determine the area number of the network area to which the destination node belongs according to the satellite orbit position information contained in the destination address during data forwarding.
[0148] This embodiment uses the above scheme, specifically by determining the destination address of the data packet to be forwarded by the source node in the satellite node; calculating the area number of the network area to which the destination node belongs based on the satellite orbital position information contained in the destination address; determining the network area to which the destination node belongs based on the area number of the network area to which the destination node belongs, wherein the network area is obtained by dividing the satellite constellation network according to the node type and node capability of the satellite node; determining the corresponding routing table according to the network area to which the destination node belongs, and forwarding the data packet within or across domains. The present application solution solves the routing problem in large-scale satellite constellation networks, by implementing network area division according to the node type and node capability of the satellite node, distinguishing between intra-domain and inter-domain routing, and combining satellite addressing, it can effectively utilize the regularity and predictability of the satellite constellation topology, limit the impact of link failures and link switching to the local network, reduce the link state information maintenance and routing calculation overhead of a single node, thereby improving routing stability and convergence speed, and adapting to network changes brought about by sudden link failures and frequent changes in link characteristics.
[0149] Example 1
[0150] In Example 1, the destination address of the data packet to be forwarded by the source node is first determined, the network area to which the destination node belongs is determined based on the destination address, and whether the source node and the destination node are in the same network area is determined. If the source node and the destination node are in the same network area, the intra-domain routing table is determined and the data packet is forwarded within the domain.
[0151] Assume that at a certain moment, the satellite constellation network is divided into network regions as shown in Figure 12. Satellite nodes Sat1 and Sat2 are both located in network region 22. The node distribution within network region 22 is shown in Figure 13. Sat1 is node number 2, and Sat2 is node number 7. When Sat1, acting as the source, sends data to Sat2, the destination node. The data transmission path, without crossing network regions, passes through nodes 2, 5, 8, and 7 in network region 22. The routing and forwarding process is identical to that of the terrestrial network. For example, the forwarding process at node 2 in network region 22 is used. Upon receiving a data packet, node 2 first resolves the destination address contained in the packet. Then, based on the destination address, it queries the local routing table to determine the next-hop node and forwarding interface. Finally, the designated forwarding interface forwards the packet to node 5.
[0152] Example 2
[0153] In Example 2, when the source node and the destination node are not in the same network area, the inter-domain routing table is determined and the data packet is forwarded across domains.
[0154] Assume that the network area division of the satellite constellation network at a certain moment is as shown in Figure 14, with satellite node Sat1 located in network area 8 and Sat2 located in network area 22. Sat1, as the source, sends data to the destination Sat2, and the data transmission path will sequentially pass through network areas 8, 12, 16, 15, 19, 18, and 22. As shown in Figure 15, when the data is forwarded from node 8 in network area 12 to node 2 in network area 16, where both node 8 and node 2 are domain edge nodes in their respective network areas, node 2 extracts the orbital position information (X, Y) from the destination address, and then calculates the area number of the network area to which the destination node belongs using the above formula (1), which is 22.
[0155] Because the destination node and Node 2 belong to different network areas, Node 2 queries the inter-domain routing table to forward data across domains. According to the inter-domain routing table, if the destination node is located in network area 22, data will be forwarded via network area 15. The next-hop forwarding node is Node 5 in this network area, so Node 2 sends the data to Node 5. The inter-domain routing table consulted by Node 2 is shown in Table 4 above. Each node in network area 16 then repeats the above steps, ultimately forwarding the data to network area 15. For the domain edge node responsible for forwarding data to the next network area, the next-hop satellite address in the inter-domain routing table will be the port address of the satellite node in the next-hop network area.
[0156] When forwarding data from network area 16 to network area 15, the routing calculation must consider the relative position between network area 16 and the destination node's network area, rather than simply the connection cost between network area 16 and network area 15. For example, the shortest path between node 2 in network area 16 and network area 15 should be 2-1-3. However, the actual forwarding process must consider the relative position between network area 16 and the destination node's network area, so the actual path is 2-5-8-7-9.
[0157] In addition, as shown in FIG16 , an embodiment of the present application provides a network routing device, the network routing device including:
[0158] An address determination module, used to determine the destination address of a data packet to be forwarded by a source node in a satellite node;
[0159] an area determination module, configured to determine a network area to which a destination node belongs according to the destination address, wherein the network area is obtained by dividing a satellite constellation network according to node types and node capabilities of the satellite nodes;
[0160] The forwarding module is used to determine the corresponding routing table according to the network area to which the destination node belongs, and forward the data packet within the domain or across domains.
[0161] The principle and implementation process of network routing implemented in this embodiment can be referred to the above embodiments and will not be described in detail here.
[0162] In addition, as shown in Figure 17, an embodiment of the present application also proposes a routing device, which includes a memory, a processor, and a network routing program stored in the memory and runnable on the processor. When the network routing program is executed by the processor, the steps of the network routing method described above are implemented.
[0163] In this embodiment, the routing device at least includes an output module 110 , a processor 120 , a memory 130 , and a communication module 140 .
[0164] The memory 130 stores an operating system and a network routing program. The network routing device can store the destination address of the data packet to be forwarded by the source node in the determined satellite node, the network area to which the destination node belongs determined according to the destination address, the network area obtained by dividing the satellite constellation network according to the node type and node capability of the satellite node, and the corresponding routing table determined according to the network area to which the destination node belongs, and other information in the memory 130; the output module 110 can be a display screen, etc.; the communication module 140 can include a routing protocol module, etc., and communicate with an external device or server through the communication module 140.
[0165] The network routing program in the memory 130 can implement the network routing methods described in the above embodiments when executed by the processor.
[0166] Since this network routing program adopts all the technical solutions of all the aforementioned embodiments when executed by the processor, it has at least all the beneficial effects brought about by all the technical solutions of all the aforementioned embodiments, which will not be described one by one here.
[0167] In addition, an embodiment of the present application further provides a computer-readable storage medium, on which a network routing program is stored. When the network routing program is executed by a processor, the steps of the network routing method described above are implemented.
[0168] Since this network routing program adopts all the technical solutions of all the aforementioned embodiments when executed by the processor, it has at least all the beneficial effects brought about by all the technical solutions of all the aforementioned embodiments, which will not be described one by one here.
[0169] Compared with the prior art, the network routing method, apparatus, routing device and storage medium proposed in the embodiments of the present application, wherein the network routing method determines the destination address of the data packet to be forwarded by the source node in the satellite node; determines the network area to which the destination node belongs based on the destination address, wherein the network area is obtained by dividing the satellite constellation network based on the node type and node capability of the satellite node; determines the corresponding routing table based on the network area to which the destination node belongs, and forwards the data packet within or across domains. The present application solution solves the routing problem in large-scale satellite constellation networks. By implementing network area division based on the node type and node capability of the satellite node and distinguishing between intra-domain and inter-domain routing, it can effectively utilize the regularity and predictability of the satellite constellation topology, limit the impact of link failures and link switching to the local network, reduce the link state information maintenance and routing calculation overhead of a single node, thereby improving routing stability and convergence speed, and adapting to network changes brought about by sudden link failures and frequent changes in link characteristics.
[0170] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or system comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or system. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or system comprising the element.
[0171] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.
[0172] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, of course, it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, disk, CD) as mentioned above, and includes a number of instructions for enabling a routing device to execute the method of each embodiment of the present application.
[0173] The above are merely optional embodiments of the present application and do not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.
Claims
1. A network routing method, wherein: The network routing method comprises: Determine the destination address of the data packet to be forwarded by the source node in the satellite node; Determining a network area to which the destination node belongs according to the destination address, wherein the network area is obtained by dividing the satellite constellation network according to the node type and node capability of the satellite node; A corresponding routing table is determined according to the network area to which the destination node belongs, and the data packet is forwarded within a domain or across domains according to the determined routing table.
2. The network routing method according to claim 1, wherein: Before the step of determining the network area to which the destination node belongs according to the destination address, the method further includes: Configuring the node type and node capability of the satellite node based on the network area model; The satellite constellation network is divided into a plurality of network areas according to the node types and node capabilities.
3. The network routing method according to claim 2, wherein: The node types include domain edge nodes located at the edge of the network area and domain mid-nodes located in the enclosed area of the domain edge nodes. The domain edge nodes have an adjacency relationship with other nodes in the network area where the domain edge nodes are located and with adjacent nodes in the neighboring area of the network area where the domain edge nodes are located. The domain mid-nodes do not have an adjacency relationship with other nodes outside the network area where the domain mid-nodes are located.
4. The network routing method according to claim 3, wherein: The network area model is a quadrilateral network area model, and the step of configuring the node type and node capability of the satellite node based on the network area model includes: Configuring the node type of the satellite node based on the quadrilateral network area model; In the case where the node type is a domain edge node, the node capabilities of the domain edge node are configured, wherein the node capabilities of the domain edge node include one or more of a connection establishment capability, a connection maintenance capability, and an inter-regional network information isolation capability with a cross-domain neighboring node, wherein the cross-domain neighboring node is an adjacent node in a neighboring area that has an adjacency relationship with the domain edge node.
5. The network routing method according to claim 4, wherein: The step of configuring the connection establishment capability of the domain edge node and the cross-domain neighbor node includes: Establishing an adjacency relationship between the domain edge node and the cross-domain neighbor node; According to the adjacency relationship between the domain edge node and the cross-domain neighbor node, announcing the area number of the network area to which the domain edge node belongs to the cross-domain neighbor node; Receive the neighbor area number announced by the cross-domain neighbor node; The neighbor area number is notified to other nodes in the network area to which the domain edge node belongs, so as to complete the configuration of the connection establishment capability between the domain edge node and the cross-domain neighbor node.
6. The network routing method according to claim 4, wherein: The step of configuring the connection maintenance capability between the domain edge node and the cross-domain neighbor node includes: Monitor the connection relationship changes between the domain edge nodes with adjacent relationships and the cross-domain neighbor nodes; In the case where the connection relationship change is an unpredictable connection relationship change, the unpredictable connection relationship change is notified to other nodes in the network area to which the domain edge node belongs, so as to complete the configuration of the connection maintenance capability between the domain edge node and the cross-domain neighbor node.
7. The network routing method according to claim 4, wherein: The steps of configuring the inter-region network information isolation capability between the domain edge node and the cross-domain neighbor node include: In the event of a network change in the network area to which the domain edge node belongs, the flooding routing information of the influencing node in the network area to which the domain edge node belongs is intercepted to complete the configuration of the inter-regional network information isolation capability between the domain edge node and the cross-domain neighboring nodes, wherein the influencing node is a satellite node that generates flooding routing information according to the network change in the network area to which the domain edge node belongs.
8. The network routing method according to claim 2, wherein: The node capability includes intra-domain network information and topology maintenance capability. The step of configuring the node capability of the satellite node based on the network area model includes: Establishing a connection relationship between the satellite node and a neighbor node; Based on the connection relationship between the satellite node and the neighboring nodes, determining other nodes in the network area to which the satellite node belongs according to the network area parameters of the network area model; Based on other nodes in the network area to which the satellite node belongs, generating a network topology within the domain according to orbital parameters; The intra-domain network topology is updated according to the first planned time interval to complete the configuration of the intra-domain network information and topology maintenance capability of the satellite node.
9. The network routing method according to claim 8, wherein: After the step of generating the intra-domain network topology based on other nodes in the network area to which the satellite node belongs according to orbital parameters, the step further includes: Notifying the network information of the satellite node to other nodes in the network area to which the satellite node belongs according to the intra-domain network topology; Monitoring the direct link of the satellite node; When a sudden failure of the direct link is detected, the neighbor node is notified, and the network information of the satellite node and the intra-domain network topology are updated.
10. The network routing method according to claim 8, wherein: The node capability also includes a cross-domain connection relationship maintenance capability, and the step of configuring the node capability of the satellite node based on the network area model also includes: Based on the connection relationship between the satellite node and the neighboring node, generating a mapping relationship between the domain edge node and the neighboring area according to the notification information of the domain edge node in the network area to which the satellite node belongs; Calculating the connectivity between the domain edge node in the network area to which the satellite node belongs and the cross-domain neighbor node adjacent to the domain edge node according to the second planning time interval, and updating the mapping relationship between the domain edge node and the neighbor area according to the connectivity to complete the configuration of the cross-domain connection relationship maintenance capability of the satellite node; and / or, When a sudden failure is detected in the satellite constellation network, link status information notified by the domain edge node in the network area to which the satellite node belongs is received, and the mapping relationship between the domain edge node and the neighboring area is updated according to the link status information to complete the configuration of the cross-domain connection relationship maintenance capability of the satellite node.
11. The network routing method according to claim 2, wherein: The node capability includes an inter-domain network topology maintenance capability, and the step of configuring the node capability of the satellite node based on the network area model includes: Characterizing the network area to which the satellite node belongs as a virtual node; The geographical locations of other virtual nodes in the satellite constellation network are calculated according to the orbital parameters of the satellite nodes in the virtual node and the regional scope of the virtual node to obtain the inter-domain network topology to complete the configuration of the inter-domain network topology maintenance capability of the satellite node.
12. The network routing method according to claim 1, wherein: The step of determining the corresponding routing table according to the network area to which the destination node belongs comprises: In the case where the network area to which the destination node belongs is the network area to which the source node is located, determining an intra-domain routing table according to the network area to which the destination node belongs; In the case that the network area to which the destination node belongs is not the network area to which the source node is located, the inter-domain routing table is determined according to the network area to which the destination node belongs.
13. The network routing method according to claim 12, wherein: The step of determining the intra-domain routing table according to the network area to which the destination node belongs comprises: The intra-domain routing table is calculated based on the network area to which the destination node belongs and the intra-domain network topology.
14. The network routing method according to claim 12, wherein: The step of determining the inter-domain routing table according to the network area to which the destination node belongs comprises: According to the network area to which the destination node belongs and the network topology within the domain, a first path tree with the source node as the root node is calculated in combination with a first path algorithm; According to the network area to which the destination node belongs and the inter-domain network topology, a second path tree with the network area where the source node is located as the root node is calculated in combination with a second path algorithm; The inter-domain routing table is determined according to the first path tree and the second path tree.
15. The network routing method according to claim 14, wherein: The step of determining the inter-domain routing table according to the first path tree and the second path tree comprises: Determine a next-hop network area of the network area where the source node is located in the second path tree; Searching the target path in the first path tree to reach the domain edge node corresponding to the next hop network area according to the mapping relationship between the domain edge node and the neighbor area; The inter-domain routing table is obtained according to the target path and the next-hop network area, and the inter-domain routing table includes the network area to which the destination node belongs and the next-hop network area.
16. The network routing method according to claim 1, wherein: The step of determining the network area to which the destination node belongs according to the destination address comprises: Calculating the area number of the network area to which the destination node belongs according to the satellite orbit position information contained in the destination address; The network area to which the destination node belongs is determined based on the area number of the network area to which the destination node belongs.
17. A routing device, wherein: The routing device includes a memory, a processor, and a network routing program stored in the memory and executable on the processor. When the network routing program is executed by the processor, the steps of the network routing method according to any one of claims 1 to 16 are implemented.
18. A computer-readable storage medium, wherein: The computer-readable storage medium stores a network routing program, and when the network routing program is executed by a processor, the steps of the network routing method according to any one of claims 1 to 16 are implemented.
Citation Information
Patent Citations
Partition-based constellation satellite network distributed routing method and device
CN112468206A
Distributed routing management method for super-large-scale low-orbit satellite constellation
CN113141622A
Ultra-low latency inter-satellite communication links
US20220345210A1
Satellite 5g terrestrial and non-terrestrial network interference exclusion zones
US20230109635A1
Cited By
Dynamic routing and flow balancing method and system for regionalized network topology
CN120915372A
A dynamic routing and traffic balancing method and system for a regionalized network topology
CN120915372B
Satellite internet simulation system based on digital twinning
CN121791915A
A method and device for routing in a mega constellation network based on topology and flow critical node control
CN122698101A
