Satellite network architecture, route publishing method, equipment, medium and program product

Abstract

The invention provides a satellite network architecture, a route publishing method, equipment, a medium and a program product. The architecture comprises a plurality of topological domains, each topological domain comprises at least one router node in a satellite orbit, public topological information of ABR nodes in the plurality of topological domains is visible to the router nodes in the plurality of topological domains, and the public topological information comprises node information of the ABR nodes and a first connection relation between the ABR nodes. The private topological information of any first topological domain is only visible to the router nodes in the first topological domain, and the private topological information of the first topological domain comprises node information of each router node in the first topological domain and a second connection relationship of each router node in the first topological domain. Therefore, when a certain node or link has a fault, the fault can be limited within a certain range, and the fault is prevented from being spread in the whole network, so that the fault can be effectively isolated, and the influence on the terminal communication service is reduced.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly to a satellite network architecture, routing method, device, medium, and program product. Background Technology

[0002] A satellite network architecture comprises multiple satellite routers. These routers can use routing protocols and corresponding routing mechanisms to forward data packets, thereby providing communication services to terminals. In recent years, with the accelerated development of low-Earth orbit satellites, the scale of satellite network architectures has also increased significantly. In this context, when a router node or link in the satellite network architecture fails, based on the current routing mechanisms, the failure will propagate throughout the entire network, causing a network-wide outage and severely impacting terminal communication services. Summary of the Invention

[0003] This application provides a satellite network architecture, route publishing method, device, medium, and program product to at least solve the problem of network-wide failure caused by the failure of a router node or link in the satellite network architecture.

[0004] To solve the above-mentioned technical problems, this application is implemented as follows: In a first aspect, a satellite network architecture is provided, comprising multiple topological domains, each topological domain including at least one router node in a satellite orbit. The public topological information of Area Border Router (ABR) nodes in each of the multiple topological domains is visible to all router nodes in the multiple topological domains. The public topological information includes node information of each ABR node and a first connection relationship between the ABR nodes. For any first topological domain among the multiple topological domains, the private topological information of the first topological domain is visible only to the router nodes in the first topological domain. The private topological information of the first topological domain includes node information of each router node in the first topological domain and a second connection relationship between each router node in the first topological domain within the first topological domain.

[0005] Secondly, a route advertising method is provided in a satellite network architecture, the satellite network architecture including multiple topology domains, each topology domain including at least one router node in a satellite orbit, the method being applied to any first router node in any first topology domain among the multiple topology domains, the method comprising: Receive the routing prefix from the second router node; The target path is determined based on at least one of public topology information and private topology information of the first topology domain. The private topology information of the first topology domain includes node information of each router node in the first topology domain and a second connection relationship of each router node in the first topology domain. The public topology information includes node information of each ABR node in the plurality of topology domains and a first connection relationship between each ABR node. The private topology information of the first topology domain is only visible to router nodes in the first topology domain, while the public topology information is visible to all router nodes in the plurality of topology domains. The target path is used by the first router node to forward packets carrying the routing prefix.

[0006] Thirdly, an electronic device is provided, comprising: processor; Memory used to store the processor's executable instructions; The processor is configured to execute the instructions to implement the method as described in the second aspect.

[0007] Fourthly, a computer-readable storage medium is provided, wherein when instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to perform the method described in the second aspect.

[0008] Fifthly, a computer program product is provided, the computer program product including a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform the method as described in the second aspect.

[0009] In this embodiment, the satellite network architecture can be divided into multiple topology domains using router nodes in one or more satellite orbits as basic units. Each topology domain includes at least one router node in a satellite orbit. The common topology information of each ABR node in the multiple topology domains is visible to all router nodes in the multiple topology domains, while the private topology information of each topology domain is only visible to router nodes within that domain. By dividing the satellite network architecture into multiple topology domains and isolating the private topology information of each topology domain from other topology domains, a failure in a node or link can be confined to a certain range, preventing the failure from propagating throughout the network. Compared to related technologies where a failure of a single router node or link in a network-wide scenario can cause a network-wide failure, this approach effectively isolates the failure, thereby reducing the impact on terminal communication services. Attached Figure Description

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

[0011] Figure 1 This is a schematic diagram of the satellite network architecture in related technologies; Figure 2 This is a schematic diagram of a satellite network architecture according to an embodiment of this application; Figure 3 This is a schematic diagram of a private topology in a topological domain, as described in one embodiment of this application. Figure 4 This is a schematic diagram of a common topology in multiple topological domains according to one embodiment of this application; Figure 5 This is a flowchart illustrating a route advertising method in a satellite network architecture according to an embodiment of this application; Figure 6 This is a schematic diagram of a route advertising method in a satellite network architecture according to an embodiment of this application; Figure 7 This is a schematic diagram illustrating cross-domain traffic transmission within a domain, as per an embodiment of this application. Figure 8 This is a schematic diagram of a cross-domain loop prevention method according to an embodiment of this application; Figure 9 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application; Figure 10 This is a schematic diagram of the routing publishing device in a satellite network architecture according to an embodiment of this application. Detailed Implementation

[0012] In related technologies, satellite network architectures are large-scale. When a router node or link fails, the failure will propagate throughout the entire network due to the current routing mechanisms of the satellite routers, causing a network-wide outage and severely impacting terminal communication services. Furthermore, when a router node or link fails, there will be significant route flooding, affecting route convergence. Since satellite routers typically come from multiple equipment manufacturers, debugging from different manufacturers may interfere with each other, leading to debugging difficulties.

[0013] To address the aforementioned issues, the satellite network architecture can be rationally divided into domains.

[0014] Figure 1 This is a schematic diagram of the satellite network architecture in related technologies. Figure 1The satellite network architecture shown is a low-Earth orbit (LEO) satellite network architecture, which adopts a mesh architecture. The satellite network architecture includes N orbits, and each orbit includes N satellite routers (SRs). These satellite routers can use routing protocols (such as Border Gateway Protocol (BGP)) and related routing mechanisms to forward data packets, thereby providing communication services to terminals.

[0015] based on Figure 1 The satellite network architecture shown presents new challenges for domain partitioning compared to terrestrial networks. For example, routers at different levels in a terrestrial network have different functions and capabilities. Based on this characteristic, a terrestrial network can be divided into ordinary domains and backbone domains. However, the functions and capabilities of satellite routers in a satellite network are consistent. Therefore, the current domain partitioning methods for terrestrial networks are not suitable for satellite networks. Furthermore, the links of low-Earth orbit (LEO) satellite routers are valuable. When an inter-satellite link failure causes routing prefixes within the same domain to become unavailable, it is desirable to route traffic back through other domains to ensure service reliability. However, current terrestrial network domain partitioning mechanisms, in order to prevent loops, do not allow intra-domain traffic to reroute across domains.

[0016] To address the aforementioned issues, this application provides a satellite network architecture comprising multiple topology domains. The satellite network architecture is divided into multiple topology domains, each including at least one router node in satellite orbit. The public topology information of the Area Border Router (ABR) nodes in each of the multiple topology domains is visible to all router nodes in the multiple topology domains. This public topology information includes node information for each ABR node and a first connection relationship between ABR nodes. For any first topology domain, the private topology information of the first topology domain is only visible to the router nodes within that first topology domain. This private topology information includes node information for each router node in the first topology domain and a second connection relationship between the router nodes in the first topology domain. By dividing the satellite network architecture into multiple topology domains and isolating the private topology information of each topology domain from other topology domains, a failure in a node or link can be confined to a certain range, preventing the failure from propagating throughout the network. Compared to related technologies where a single node or link failure in a satellite network architecture can lead to a network-wide failure, this approach effectively isolates the failure, thereby reducing the impact on terminal communication services.

[0017] Furthermore, this application also provides a route advertising method, device, medium, and program product in a satellite network architecture. This method can advertise the route prefixes of each router node in the satellite network architecture across the entire network. For a route prefix of a certain second router node, each time the route prefix passes through a first router node, the first router node will calculate the target path from the first router node to the second router node. Thus, when a message carrying the route prefix is ​​received, the message can be forwarded based on the target path, thereby realizing the transmission of messages in the satellite network architecture. This ensures the provision of communication services to terminals based on domain division.

[0018] To enable those skilled in the art to better understand the technical solutions in this application, the technical solutions in this application will be clearly and completely described below with reference to the accompanying drawings of one or more embodiments. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of this application.

[0019] The terms "first," "second," etc., used in this application and the claims are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that this application can be implemented in orders other than those illustrated or described herein. Furthermore, in this application and the claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0020] The technical solutions provided by the various embodiments of this application are described in detail below with reference to the accompanying drawings.

[0021] The satellite network architecture provided in this application includes multiple topology domains, each of which includes at least one router node in a satellite orbit. That is, this application uses a router node in a single satellite orbit as the basic unit to divide the satellite network architecture into multiple topology domains. Each topology domain includes one or more router nodes in a satellite orbit. The router nodes in each topology domain include Area Border Router (ABR) nodes and internal nodes. The public topology information of each ABR node in multiple topology domains is visible to all router nodes in the multiple topology domains. For any first topology domain among the multiple topology domains, the private topology information of that first topology domain is only visible to the router nodes in that first topology domain.

[0022] For easier understanding, please refer to Figure 2 .

[0023] Figure 2 Taking a satellite network architecture comprising four satellite orbits as an example, the satellite network architecture is divided into three topology domains: Topology Domain 1, Topology Domain 2, and Topology Domain 3. Topology Domain 1 includes the router nodes in satellite orbit 1; Topology Domain 2 includes the router nodes in satellite orbits 2 and 3; and Topology Domain 3 includes the router nodes in satellite orbit 4. Specifically, the ABR nodes in Topology Domain 1 are Router 1.1 and Router 1.3, with the other nodes being Router 1.2. The ABR nodes in Topology Domain 2 are Router 2.1.1, Router 2.2.1, Router 2.1.3, and Router 2.2.3, with the other nodes being Router 2.1.2 and Router 2.2.2. The ABR nodes in Topology Domain 3 are Router 3.1 and Router 3.3, with the other nodes being Router 3.2. It should be noted that... Figure 2 The ABR nodes for each topology shown are merely illustrative. In other possible implementations, the ABR nodes in each topology could also be other router nodes within the same topology, without specific limitations. For example, in some possible implementations, the ABR nodes in topology 2 could be routers 2.1.1, 2.2.1, 2.1.2, and 2.2.2.

[0024] Figure 2 In this model, the public topology information of each ABR node in the three topology domains is visible to all router nodes in those three topology domains. For each topology domain, the private topology information is only visible to router nodes within that domain. For example, the public topology information of the eight ABR nodes in the three topology domains is visible to all router nodes in those domains. The private topology information of topology domain 1 is only visible to the three routers in topology domain 1, and not to the nine router nodes in topology domains 2 and 3. The private topology information of topology domain 2 is only visible to the six routers in topology domain 2, and not to the six router nodes in topology domains 1 and 3. The private topology information of topology domain 3 is only visible to the three routers in topology domain 3, and not to the nine router nodes in topology domains 1 and 3.

[0025] In some implementations, taking any first topology domain among multiple topology domains in a satellite network as an example, the private topology information of the first topology domain may include node information (such as node identification information) of each router node in the first topology domain and the second connection relationship of each router node in the first topology domain, wherein the second connection relationship includes physical connection relationship. For example, in Figure 2In the diagram, the private topology information of topology domain 1 includes the node information of routers 1.1, 1.2, and 1.3, the physical link relationships between routers 1.2 and 1.1, and the physical link relationships between routers 1.2 and 1.3. This information is only visible to the three router nodes in topology domain 1 and is not visible to the nine router nodes in topology domains 2 and 3. Similarly, the private topology information of topology domain 2 includes the node information of the six router nodes in topology domain 2, the node information of router 2.2.2, the physical link relationships between router 2.1.2 and routers 2.1.1, 2.2.2, and 2.1.3, and the physical link relationships between router 2.2.2 and routers 2.1.2, 2.2.1, and 2.2.3. This information is only visible to the six router nodes in topology domain 2 and is not visible to the six router nodes in topology domains 1 and 3. The private topology information of topology domain 3 includes the node information of routers 3.1, 3.2 and 3.3, the physical connection relationship between router 3.2 and router 3.1, and the physical connection relationship between router 3.2 and router 3.31. This information is only visible to the three router nodes in topology domain 3 and is not visible to the nine router nodes in topology domain 1 and topology domain 2.

[0026] In some implementations, the common topology information of each ABR node in multiple topology domains within the satellite network architecture includes node information (such as node identification information) of each ABR node in those multiple topology domains and a first connection relationship between each ABR node. This first connection relationship includes a virtual logical connection relationship between two ABR nodes located in the same topology domain and a physical connection relationship between ABR nodes located in different topology domains. For example, Figure 2 In this context, the common topology information for each ABR node in the three topology domains includes the node information for routers 1.1, 1.3, 2.1.1, 2.2.1, 2.1.3, 2.2.3, 3.1, and 3.3; the virtual logical link (vlink) relationship between routers 1.1 and 1.3; the physical link relationship between routers 1.1 and 2.1.1; the virtual logical link relationship between routers 2.1.1 and 2.2.1; the physical link relationship between routers 2.2.1 and 3.1; the virtual logical link relationship between routers 3.1 and 3.3; the physical link relationship between routers 3.3 and 2.2.3; the virtual logical link relationship between routers 2.2.3 and 2.1.3; the physical link relationship between routers 2.1.3 and 1.3; the virtual logical link relationship between routers 2.1.1 and 2.1.3; and the virtual logical link relationship between routers 2.2.1 and 2.2.3. This information is crucial for... Figure 2 All 12 router nodes shown are visible.

[0027] In some implementations, for two ABR nodes in the same topology domain, taking the first ABR node and the second ABR node as examples, the virtual logical connection between these two ABR nodes can be established through first configuration information in the first ABR node. That is, first configuration information can be configured or added to the first ABR node. This first configuration information is used to establish the virtual logical connection between the first ABR node and the second ABR node. The first configuration information includes the address information of the second ABR node. Thus, based on this first configuration information, the first ABR node can establish a virtual logical connection with the second ABR node. Figure 2 Taking topology domain 1 as an example, configuration information can be added to router 1.1. This configuration information specifies the address of router 1.3. Since routers 1.1 and 1.3 are reachable in topology domain 1, router 1.1 can generate a virtual logical link between routers 1.1 and 1.3 based on this configuration information, thereby establishing a virtual logical connection between routers 1.1 and 1.3.

[0028] In some implementations, for any first topology domain, the router nodes within that domain constitute a first private topology. The ABR nodes across multiple topology domains constitute a common topology. Figure 2 Taking topology domain 1 as an example, the private topology of topology domain 1 can be as follows: Figure 3 As shown, the common topology formed by the ABR nodes of the three topological domains can be as follows: Figure 4 As shown. The topology information of the first private topology within the first private topology domain is the private topology information of the first topology domain, while the topology information of the public topology is the public topology information of each ABR node in multiple topology domains.

[0029] From the above Figure 3 and Figure 4 It can be seen that for any first topology domain, the public topology and the first private topology within the first topology domain share all ABR nodes in the first topology domain. In other words, the topology containing the ABR nodes in the first topology domain includes both the public topology and the first private topology within the first topology domain. For example... Figure 2 The topology where router 1.1 is located includes Figure 3 The private topology shown and Figure 4The public topology is shown. In this case, to ensure that the private topology information of the first topology domain is visible only to router nodes within the first topology domain, and that the public topology information of each ABR node in multiple topology domains is visible to each router node in multiple topology domains, in some implementations, ABR nodes shared by the public topology and the first private topology can be configured. Specifically, taking any third ABR node shared by the public topology and the first private topology as an example, the public topology and the first private topology can be configured with the same Border Gateway Protocol (BGP) address family on the third ABR node, that is, the public topology and the first private topology can use the same BGP address family. In addition, a new BGP neighbor type can be added to the third ABR node. Taking the addition of a first BGP neighbor type as an example, the first BGP neighbor type can represent a new route advertising rule. This new route advertising rule can be represented as a preset route advertising rule. The first BGP neighbor type is used to control the route advertising of the third ABR node based on the preset route advertising rule. On this basis, the private topology information of the first topology domain can be seen only by the router nodes in the first topology domain, while the public topology information of each ABR node in multiple topology domains can be seen by each router node in multiple topology domains.

[0030] In some implementations, the aforementioned preset route advertising rules may include: Private topology information of the first topology domain is not allowed to be sent to other router nodes outside the first topology domain; It allows the node information and third connection relationships of the third ABR node to be published on the neighboring nodes of the third ABR node to build a public topology. The third connection relationships include the physical connection relationships and virtual logical connection relationships between the third ABR node and other ABR nodes. It allows the routing prefixes of each router node in the first topology domain to be advertised to other router nodes in multiple topology domains, and there are no restrictions on whether the advertising source is modified; It allows the public topology information of each ABR node in the first topology domain to be published to other router nodes in multiple topology domains.

[0031] By controlling the route advertising of the third ABR node through the above-mentioned route advertising rules, the private topology information of the first topology domain can be seen only by the router nodes in the first topology domain, while the public topology information of each ABR node in multiple topology domains can be seen by each router node in multiple topology domains.

[0032] The satellite network architecture provided in this application can be divided into multiple topology domains using router nodes in one or more satellite orbits as basic units. Each topology domain includes at least one router node in a satellite orbit. The common topology information of each ABR node in the multiple topology domains is visible to all router nodes in the multiple topology domains, while the private topology information of each topology domain is only visible to router nodes within that domain. By dividing the satellite network architecture into multiple topology domains and isolating the private topology information of each topology domain from other topology domains, a failure in a node or link can be limited to a certain range, preventing the failure from propagating throughout the network. Compared to related technologies where a failure of a single router node or link can cause a network-wide failure, this approach effectively isolates the failure, thereby reducing the impact on terminal communication services.

[0033] Based on the satellite network architecture provided in this application embodiment, this application embodiment also provides a route advertising method in the satellite network architecture, which can realize the advertising of each router node in the satellite network architecture across the entire network.

[0034] Figure 5 This is a flowchart illustrating a route advertising method in a satellite network architecture according to an embodiment of this application. Figure 5 The method shown can be applied to any first router node in any first topology domain within multiple topology domains in a satellite network architecture, that is, Figure 5 The method shown can be executed by software or hardware installed on the first router node, which can be an ABR node or any other router node besides an ABR node; no specific limitation is made here. This route advertising method includes the following steps.

[0035] S502: Receive the routing prefix from the second router node.

[0036] The second router node is any router node in the satellite network architecture other than the first router node. The second router node can be an ABR node or any other router node besides an ABR node; there is no specific limitation here. During route advertising, the second router node can advertise its own route prefix to all router nodes in the network. In this case, the first router node can receive the route prefix from the second router node. Specifically, the first router node receiving the route prefix from the second router node can be either receiving the route prefix from the second router node sent to the first router node (which could correspond to a scenario where the first router node and the second router node are adjacent), or receiving the route prefix from the second router node sent to the first router node by a third router node (which could correspond to a scenario where the first router node and the third router node are adjacent, but the first router node is not adjacent to the second router node); there is no specific limitation here. The third router node is any router node other than the first and second router nodes.

[0037] S504: Determine the target path based on at least one of public topology information and private topology information of the first topology domain. The private topology information of the first topology domain includes node information of each router node in the first topology domain and the second connection relationship of each router node in the first topology domain within the first topology domain. The public topology information includes node information of each ABR node in multiple topology domains and the first connection relationship between each ABR node. The private topology information of the first topology domain is only visible to router nodes in the first topology domain, while the public topology information is visible to all router nodes in multiple topology domains. The target path is used by the first router node to forward packets carrying the routing prefix of the second router node.

[0038] During route advertising, each time the route prefix of the second router node passes through a router node, that router node can perform path calculation. Taking the first router node as an example, after receiving the route prefix from the second router node, the first router node can perform path calculation to obtain the target path. The target path can include the optimal or shortest path from the first router node to the second router node, and the target path is used by the first router node to forward packets carrying the route prefix of the second router node.

[0039] When performing path calculation, the first router node can calculate the target path based on at least one of the public topology information and the private topology information of the first topology domain. The public topology information includes the node information of each ABR node in multiple topology domains and the first connection relationships between the ABR nodes. The first connection relationships include the virtual logical connection relationships between ABR nodes located in the same topology domain and the physical connection relationships between two ABR nodes located in different topology domains. Figure 2 Taking the three topology domains shown as examples, the common topology information of each ABR node in these three topology domains includes the node information of routers 1.1, 1.3, 2.1.1, 2.2.1, 2.1.3, 2.2.3, 3.1, and 3.3, the virtual logical link (vlink) relationship between routers 1.1 and 1.3, the physical link relationship between routers 1.1 and 2.1.1, the virtual logical link relationship between routers 2.1.1 and 2.2.1, the physical link relationship between routers 2.2.1 and 3.1, the virtual logical link relationship between routers 3.1 and 3.3, the physical link relationship between routers 3.3 and 2.2.3, the virtual logical link relationship between routers 2.2.3 and 2.1.3, the physical link relationship between routers 2.1.3 and 1.3, the virtual logical link relationship between routers 2.1.1 and 2.1.3, and the virtual logical link relationship between routers 2.2.1 and 2.2.3. This information is crucial for... Figure 2 All 12 router nodes shown are visible.

[0040] The private topology information of the first topology domain includes the node information of each router node in the first topology domain and the second connection relationships of each router node in the first topology domain. The second connection relationships include physical connection relationships. Figure 2 Taking topology domain 1 as an example, the private topology information of topology domain 1 includes the node information of routers 1.1, 1.2 and 1.3, the physical connection relationship between router 1.2 and router 1.1, and the physical connection relationship between router 1.2 and router 1.3. This information is only visible to the router nodes in topology domain 1 and is not visible to the nine router nodes in topology domain 2 and topology domain 3.

[0041] In some implementations, when the first router node is an ABR node in the first topology domain, the first router node may include the following before receiving the routing prefix from the second router node: A virtual logical connection is established between the first router node and other ABR nodes in the first topology domain based on the first configuration information, which includes the address information of the other ABR nodes.

[0042] Specifically, when establishing a virtual logical connection between the first router node and other ABR nodes, first configuration information can be configured or added on the first router node. This first configuration information can specify the address information of the other ABR nodes. In this way, the first router node can establish a virtual logical connection with other ABR nodes based on this first configuration information. The other ABR nodes can be ABR nodes within the first topology domain. Since the other ABR nodes and the first router node are located in the same topology domain and have reachable paths within that domain, the first router node can generate virtual logical connection links with other ABR nodes based on the first configuration information, thereby establishing a virtual logical connection with other ABR nodes.

[0043] Each internal node in the first topology domain constitutes the first private topology in the first topology domain, and each ABR node in multiple topology domains constitutes the common topology. The topology information of the first private topology of the first topology domain, i.e., the private topology information of the first topology domain, is only visible to the router nodes in the first topology domain. The topology information of the common topology, i.e., the common topology information, is visible to all router nodes in multiple topology domains in the satellite network architecture. To achieve this purpose or effect, the ABR nodes in the first topology domain can be configured accordingly. Taking the first router node as the ABR node in the first topology domain as an example, in some implementations, it may include: On the first router node, the same BGP address family is configured for the first private topology and public topology in the first topology domain. The first router node includes a first BGP neighbor type, which is used to control the route advertising of the first router node based on preset route advertising rules, so that the private topology information of the first topology domain is visible only to the router nodes in the first topology domain, and the public topology information of each ABR node in multiple topology domains is visible to each router node in multiple topology domains.

[0044] The aforementioned preset route publishing rules may include: Private topology information of the first topology domain is not allowed to be sent to other router nodes outside the first topology domain; The node information of the first router node and the third connection relationship are allowed to be published on the neighbor nodes of the first router node to build a public topology. The third connection relationship includes the physical connection relationship and virtual logical connection relationship between the first router node and other ABR nodes. It allows the routing prefixes of each router node in the first topology domain to be advertised to other router nodes in multiple topology domains, and there are no restrictions on whether the advertising source is modified; It allows the public topology information of each ABR node in the first topology domain to be published to other router nodes in multiple topology domains.

[0045] In this way, by configuring the same BGP address family for the private and public topologies in the first topology domain on the first router node, and adding a BGP neighbor type on the ABR node in the first topology domain, and controlling the route advertising of the ABR node in the first topology domain through the BGP neighbor type, the topology information of each internal node in the first topology domain can be seen only by the router nodes in the first topology domain, while the topology information of each ABR node in the first topology domain can be seen by router nodes in multiple topology domains.

[0046] When determining a target path based on at least one of public topology information and private topology information of the first topology domain, the first router node can select which topology information to use for path calculation based on its node type to obtain the target path. The node type of the first router node includes ABR nodes in the first topology domain and internal nodes in the first topology domain.

[0047] In some implementations, when the first router node is an ABR node in the first topology domain, the first router node determines the target path based on at least one of public topology information and private topology information, which may include at least the following scenarios 1 to 3.

[0048] Scenario 1: When the second router node is a router node in the first topology domain, the target path is determined based on the private topology information of the first topology domain. The target path includes the path from the first router node to the second router node. In other words, when both the first and second router nodes are located in the first topology domain, the first router node can obtain the target path based on the private topology information within the first topology domain. This target path includes the path from the first router node to the second router node, such as the optimal or shortest path. Figure 2 Taking router 2.1.1 as the first router node and router 2.2.2 as the second router node as an example, router 2.1.1 can calculate the optimal or shortest target path between router 2.1.1 and 2.2.2 based on the private topology information of topology domain 2.

[0049] Scenario 2: When the second router node is an ABR node outside the first topology domain, the target path is determined based on common topology information. This target path includes the path from the first router node to the second router node. In other words, when the first and second router nodes are ABR nodes in different topology domains, the first router node can obtain the target path based on common topology information. This target path includes the path from the first router node to the second router node, such as the optimal or shortest path. Figure 2Taking router 2.1.1 as the first router node and router 3.1 as the second router node as an example, when router 2.1.1 calculates the target path, it can do so based on the common topology information (i.e., Figure 5 The optimal or shortest path between routers 2.1.1 and 3.1 is calculated using the topology information of the public topology shown.

[0050] Scenario 3: When the second router node is an internal node in the second topology domain, the target path is determined based on public topology information. The target path includes the path from the first router node to the ABR node in the second topology domain, which is a topology domain other than the first topology domain. That is, when the first and second router nodes are located in different topology domains, and the first router node is an ABR node while the second router node is an internal node, since the public topology information and the private topology information of the first topology domain are visible to the first router node, but the private topology information of the second topology domain where the second router node resides is not visible to the first router node, the first router node, when calculating the target path, can only calculate the path to the ABR node in the second topology domain based on the public topology information and the private topology information of the first topology domain. In other words, the target path includes the path from the first router node to the ABR node in the second topology domain, such as the optimal or shortest path from the first router node to the ABR node in the second topology domain. Figure 2 Taking router 2.1.1 as the first router node and router 3.2 as the second router node as an example, when router 2.1.1 calculates the target path, it can do so based on the common topology information (i.e., Figure 5 The optimal or shortest path between router 2.1.1 and the ABR node in topology domain 3 is calculated using the topology information of the public topology shown. For example, router 2.1.1 calculates the path from itself to router 3.1 and the path from itself to router 3.3 based on the public topology information, and then selects the optimal or shortest path from these paths as the target path.

[0051] In some implementations, when the first router node is an internal node in the first topology domain, the first router node determines the target path based on at least one of public topology information and private topology information, which may include the following scenarios 4 to 6.

[0052] Scenario 4: When the second router node is a router node within the first topology domain, the target path is determined based on the private topology information of the first topology domain. This target path includes the path from the first router node to the second router node. In other words, when both the first and second router nodes are internal nodes of the first topology domain, the first router node can obtain the target path based on the private topology information within the first topology domain. This target path includes the path from the first router node to the second router node, such as the optimal or shortest path. Figure 2 Taking router 2.1.2 as the first router node and router 2.2.2 as the second router node as an example, router 2.1.2 can calculate the optimal or shortest target path between router 2.1.2 and 2.2.2 based on the private topology information of topology domain 2.

[0053] Scenario 5: When the second router node is an ABR node outside the first topology domain, the target path is determined based on public topology information and private topology information of the first topology domain. The target path includes the path from the first router node to the second router node. In other words, when the first router node is an internal node in the first topology domain and the second router node is an ABR node in another topology domain, the first router node can calculate the path between the first and second router nodes (e.g., the optimal or shortest path) because the public topology information and the private topology information of the first topology domain are visible to it. Figure 2 Taking router 2.1.2 as the first router node and router 3.1 as the second router node as an example, when router 2.1.2 calculates the target path, it can do so based on the private topology information and public topology information of topology domain 2 (i.e., Figure 5 The optimal or shortest path between routers 2.1.2 and 3.1 is calculated using the topology information of the public topology shown.

[0054] Scenario 6: When the second router node is an internal node in the third topology domain, the target path is determined based on public topology information and private topology information of the first topology domain. The target path includes the path from the first router node to the ABR node in the third topology domain, which is a topology domain other than the first topology domain. In other words, when the first and second router nodes are internal nodes located in different topology domains, the first router node, when calculating the target path, can only calculate the path to the ABR node in the third topology domain based on the public topology information and the private topology information of the first topology domain. This means the target path includes the path from the first router node to the ABR node in the third topology domain, such as the optimal or shortest path. Figure 2 Taking router 2.1.2 as the first router node and router 3.2 as the second router node as an example, when router 2.1.2 calculates the target path, it can do so based on the private topology information and public topology information of topology domain 2 (i.e., Figure 5 The optimal or shortest path between router 2.1.2 and the ABR node in topology domain 3 is calculated using the public topology information shown. For example, router 2.1.2 calculates the path from itself to router 3.1 and the path from itself to router 3.3 based on the public topology information and the private topology information of topology domain 2, and then selects the optimal or shortest path from these paths as the target path.

[0055] It should be noted that when the first router node performs target path calculation, the calculation method can be found in the path calculation methods in related technologies, and will not be described in detail here.

[0056] In some implementations, after obtaining the target path, the first router node may further include: A routing table is generated based on the routing prefix and destination path of the second router node. The routing table includes a Routing Information Base (RIB) table and a Forwarding Information Base (FIB) table. Upon receiving the first message, the first message is forwarded according to the routing table. The first message carries the routing prefix of the second router node.

[0057] The specific implementation method for the first router node to generate a routing table based on the routing prefix and destination path of the second router node can be found in related technologies, and will not be described in detail here. After generating the routing table, when the first router node receives a first packet carrying the routing prefix of the second router, it can determine the forwarding path based on the routing table and forward the first packet, thereby realizing the transmission of the first packet in the satellite network architecture.

[0058] In some implementations, forwarding the first packet according to the routing table may include: Determine the forwarding path of the first packet based on the routing prefix and routing table in the first packet; When the first router node is an ABR node and the forwarding path includes virtual logical connection links between the first router node and other ABR nodes in the first topology domain, the first path is determined based on the private topology information of the first topology domain. The first path includes physical connection links from the first router node to other ABR nodes in the first topology domain. The first packet is forwarded to the ABR node corresponding to the virtual logical connection link based on the first path.

[0059] The target path determined by the first router node may include at least one of physical connection links and virtual logical connection links. Physical connection links can directly forward packets, while virtual logical connection links cannot. Therefore, when forwarding the first packet, if the forwarding path is a physical connection link, the first router node can directly send the first packet to the next-hop node corresponding to the forwarding path. If the forwarding path is a virtual logical connection link, the first packet cannot be directly forwarded based on that virtual logical connection link. Since the virtual logical connection link connects ABR nodes located in the same topology domain, and ABR nodes in the same topology domain generally have reachable physical connection links, when the forwarding path includes a virtual logical connection link, the corresponding physical connection link can be determined based on the virtual logical connection link during packet forwarding, such as the shortest or optimal physical connection link, and then the first packet can be forwarded through that physical connection link. Taking the first router node as the ABR node, when forwarding the first packet, the forwarding path includes the virtual logical connection link between the first router node and other ABR nodes in the first topology domain. For example, the first router node can determine the optimal or shortest physical connection link from the first router node to the other ABR node, i.e. the first path, based on the private topology information of the first topology domain, and forward the first packet to the ABR node corresponding to the virtual logical connection link based on the first path.

[0060] by Figure 2Router 1.1 is the first router node. Taking the forwarding path of the first packet as the virtual logical link between router 1.1 and 1.3 as an example, when router 1.1 forwards the first packet, it can forward it through the physical link between router 1.1 and 1.3. That is, it first forwards the first packet to router 1.2, and then router 1.2 forwards it to router 1.3, thus realizing the transmission of the first packet between router 1.1 and 1.3.

[0061] To facilitate understanding of the route advertising method provided in this application's embodiments and the forwarding of data packets after route advertising, please refer to... Figure 6 . Figure 6 The satellite network architecture shown includes three topology domains, each containing private and public topologies. The public topologies from multiple topology domains constitute a larger public topology. For details, please refer to [link to relevant documentation]. Figures 2 to 4 The embodiments shown are not described in detail here.

[0062] Figure 6 A new BGP neighbor type (type_abr) is defined on each ABR node to control route advertising, ensuring that private topology information for each topology domain is only visible to routers within that domain, while public topology information is visible to routers across multiple topology domains. For the public topology portion within each topology domain, since it traverses different private topologies, a vlink approach is needed to construct the complete public topology. After the private topologies within each topology domain are isolated, their route prefixes need to be advertised across the entire network. Figure 6 Taking the example of router 3.2 advertising a loopback route to router 1.2, the route advertising process is as follows: Step 1: The routing prefix of router 3.2 is reflected hop-by-hop within the private topology of topology domain 3, and routing RIB and FIB tables are generated on the router nodes it passes through, and then reflected to ABR node 3.1 within the domain.

[0063] Step 2: Because the private topology of topology domain 3 is not visible to the public topology, ABR node 3.1 receives the route and performs the best or shortest path calculation to find the optimal route, and then redistributes it into the public topology. Whether or not the publishing source needs to be modified is not restricted by the method. The route is sent to router node 2.2.1.

[0064] Step 3: Router 2.2.1 is an ABR node. Routes are directly advertised into the private topology of topology domain 2 and reflected to router 2.1.1 within the private topology.

[0065] Step 4: Router 2.1.1 publishes the route to the public topology to Router 1.1 without modifying the publishing source.

[0066] Step 5: Router 1.1 is an ABR node. It publishes routes into the private topology of topology domain 1 and reflects them to router 1.2 within the private topology.

[0067] As the above route passes through each router node, each router node generates a corresponding routing RIB table and FIB table.

[0068] Subsequently, when data packets (or data streams) are forwarded from router 1.2 to router 3.2, the forwarding process is as follows: Step 1: After receiving the data packet, Router 1.2, having access to the topology information of the public topology and the private topology of its own domain, can calculate the optimal path to the public topology ABR node 3.1 in the above route advertising process and generate routes RIB and FIB.

[0069] Step 2: Router 1.2 forwards data packets according to the generated routing FIB table. The forwarding process is the same in the public topology and in the private topology of each topology domain.

[0070] Step 3: After the data packet arrives at router 3.1 in the public topology, router 3.1 follows the shortest path route in the private topology of topology domain 3 to reach the destination node 3.2.

[0071] In this embodiment, the routing prefixes of each router node in the satellite network architecture can be published across the entire network. For a routing prefix of a certain second router node, each time the routing prefix passes through a first router node, the first router node will calculate the target path from the first router node to the second router node. Thus, when a message carrying the routing prefix is ​​received, the message can be forwarded based on the target path, thereby realizing the transmission of the message in the satellite network architecture. This ensures the provision of communication services to the terminal based on the domain division.

[0072] In practical applications, satellite router links are valuable. When inter-satellite links fail, prefix routes within the same topology domain, due to intra-domain link outages, should ideally be able to bypass these links and return via other topologies to maximize service reliability. Figure 7 As shown. Figure 7 Data traffic needs to flow from router 1.1 to router 1.2, but the link between routers 1.1 and 1.2 is faulty, so the data traffic cannot directly reach 1.2 from router 1.1. In this case, the data traffic can flow to router 1.2 through routers 2.1.1 and 2.1.2, that is, data traffic within a domain can be routed across domains. Based on the technical solution provided in the embodiments of this application, it can be seen that after dividing the satellite network architecture into domains, the embodiments of this application can realize cross-domain routing of data traffic within a domain.

[0073] When intra-domain data traffic is allowed to bypass across domains, loop prevention is necessary for cross-domain traffic. In related technologies, within an AS, traffic from an IBGP domain uses a cluster_list for loop prevention. The cluster_list is appended with the IDs of the router nodes it passes through, and returning packets are loop-prevented by checking the node information in the cluster_list. However, in satellite network architectures with tens of thousands of satellite routers, using cluster_list for loop prevention would result in excessively long cluster_list packets being discarded due to the large number of nodes. Furthermore, after domaining the satellite network architecture, all domains may reside in different ASs, making it impossible for cluster_list to traverse different domains. Therefore, based on domain segmentation, the existing loop prevention mechanism (cluster_list) can be used within a domain, with a new extended information layer defined for cross-domain loop prevention. This extended information can record the identification information of the ABR nodes that the data traffic passes through. Since the number of ABR nodes is limited, using extended information for loop prevention checks can significantly reduce packet load. This extended information can be applied to one or more ASs; no specific limitation is made here.

[0074] Based on the aforementioned cross-domain loop prevention mechanism, when advertising routes, the route prefix of the second router node can include the aforementioned extended information. This extended information records the identification information of the ABR nodes traversed by the route prefix. Thus, when the first router node is an ABR node, after receiving the route prefix from the second router node, the first router node can perform cross-domain loop prevention based on the extended information, specifically including: Determine whether the extended information includes the identification information of the first router node; If the extended information includes the identification information of the first router node, it indicates that the loop prevention check failed, and the route prefix can be discarded. If the identification information of the first router node is not included in the extended information, it means that the loop prevention check has passed. In this case, the identification information of the first router node is added to the extended information. After that, the first router node can determine the target path based on at least one of the public topology information and the private topology information of the first topology domain.

[0075] In some implementations, the format of the extended information can be the same as that of the cluster_list defined in the current BGP routing. Optionally, the extended information can be represented as abr_cluster_list. Both abr_cluster_list and cluster_list include a type field, but the value of the type field in abr_cluster_list is different from that in cluster_list, in order to distinguish between abr_cluster_list and cluster_list.

[0076] Optionally, the definition of the extended information (abr_cluster_list) can be: 0 1 2 3 4 5 6 715 +---+---+---+---+---+---+---+---+---+---+ |O|T|P|E|Type Code| +---+---+---+---+---+---+---+---+---+---+ |abr-cluster-list.len| +---+---+---+---+---+---+---+---+---+---+ |abr-cluster-list.val| +---+---+---+---+---+---+---+---+---+---+ Here, O (Optional bit) = 1: This indicates that this is an optional attribute. If the receiver cannot recognize this attribute, it should ignore it and continue processing the message.

[0077] T (Transitive bit) = 0: This indicates that this is a non-transitive attribute. If the receiver cannot recognize this attribute, it will not pass it on to its peer.

[0078] P (Partial bit) = 0: This indicates that this is a complete attribute. Typically, this bit is 0 for non-transitive attributes.

[0079] E (Extended Length bit) = 0 or 1: Determines whether the attribute length field is 1 byte or 2 bytes.

[0080] Type Code: This is the type field, which can be assigned a new value, such as 130.

[0081] To better understand the cross-domain loop prevention provided in the embodiments of this application, please refer to... Figure 8 The example shown. Figure 8 In this scenario, a route prefix originates from router 1.1, passes through router node 2.1 (an ABR node), and its `abr_cluster_list` stores the node identifier of router 2.1, such as `router-id 10.1.1.2`. Similarly, when the prefix passes through router 3.1, its `abr_cluster_list` stores the node identifier of router 3.1, such as `10.1.3.1`, and so on. For router 2.1, upon receiving a route prefix, if the `abr_cluster_list` exists within the prefix and includes its own node identifier, then the route prefix is ​​discarded.

[0082] The foregoing has described specific embodiments of this application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired results. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0083] Figure 9 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Please refer to it. Figure 9 At the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and memory. The memory may include main memory, such as high-speed random-access memory (RAM), or non-volatile memory, such as at least one disk drive. Of course, the electronic device may also include other hardware required for other business operations.

[0084] The processor, network interface, and memory can be interconnected via an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 9The symbol is represented by a single double-headed arrow, but this does not mean that there is only one bus or one type of bus.

[0085] Memory is used to store programs. Specifically, programs may include program code, which includes computer operation instructions. Memory may include main memory and non-volatile memory, and provides instructions and data to the processor.

[0086] The processor reads the corresponding computer program from non-volatile memory into main memory and then executes it, forming the routing distribution device in the satellite network architecture at the logical level. The processor executes the program stored in memory and specifically performs the following operations: Receive the routing prefix from the second router node; The target path is determined based on at least one of public topology information and private topology information of a first topology domain. The private topology information of the first topology domain includes node information of each router node in the first topology domain and a second connection relationship of each router node in the first topology domain. The public topology information includes node information of each ABR node in the plurality of topology domains and a first connection relationship between each ABR node. The private topology information of the first topology domain is only visible to router nodes in the first topology domain, while the public topology information is visible to all router nodes in the plurality of topology domains. The target path is used to forward packets carrying the routing prefix.

[0087] The above is as stated in this application. Figure 9The method executed by the routing announcement device in the satellite network architecture disclosed in the illustrated embodiment can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic diagrams disclosed in this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in this application can be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0088] The electronic device can also perform Figure 5 The method, and implement the route publishing device in the satellite network architecture in Figure 5 The functions described in the illustrated embodiments will not be repeated here.

[0089] Of course, in addition to software implementation, the electronic device of this application does not exclude other implementation methods, such as logic devices or a combination of hardware and software, etc. In other words, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0090] This application also discloses a computer-readable storage medium that stores one or more programs, the programs including instructions that, when executed by a portable electronic device including multiple applications, enable the portable electronic device to perform... Figure 5 The method of the illustrated embodiment is specifically used to perform the following operations: Receive the routing prefix from the second router node; The target path is determined based on at least one of public topology information and private topology information of a first topology domain. The private topology information of the first topology domain includes node information of each router node in the first topology domain and a second connection relationship of each router node in the first topology domain. The public topology information includes node information of each ABR node in the plurality of topology domains and a first connection relationship between each ABR node. The private topology information of the first topology domain is only visible to router nodes in the first topology domain, while the public topology information is visible to all router nodes in the plurality of topology domains. The target path is used to forward packets carrying the routing prefix.

[0091] Figure 10 This is a schematic diagram of the routing publishing device 100 in a satellite network architecture according to an embodiment of this application. Please refer to... Figure 10 In one software implementation, the route publishing device 100 in the satellite network architecture may include: a receiving module 101 and a determining module 102, wherein: The receiving module 101 receives the routing prefix of the second router node; The determination module 102 determines a target path based on at least one of public topology information and private topology information of a first topology domain. The private topology information of the first topology domain includes node information of each router node in the first topology domain and a second connection relationship of each router node in the first topology domain. The public topology information includes node information of each ABR node in the plurality of topology domains and a first connection relationship between each ABR node. The private topology information of the first topology domain is only visible to router nodes in the first topology domain, while the public topology information is visible to all router nodes in the plurality of topology domains. The target path is used to forward packets carrying the routing prefix.

[0092] The routing publishing device 100 in the satellite network architecture provided in this application can also perform... Figure 5 The method, and implement the route publishing device 100 in the satellite network architecture. Figure 5 The functions of the embodiments shown will not be described again in this application.

[0093] This application also proposes a computer program product comprising a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps in the routing announcement method embodiments of the above-described satellite network architecture.

[0094] In summary, the above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

[0095] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0096] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0097] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0098] The various embodiments in this application are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

Claims

1. A satellite network architecture comprising multiple topology domains, each topology domain including at least one router node in a satellite orbit, wherein public topology information of Area Border Router (ABR) nodes in the multiple topology domains is visible to all router nodes in the multiple topology domains, the public topology information including node information of each ABR node and a first connection relationship between each ABR node, and for any first topology domain in the multiple topology domains, private topology information of the first topology domain is visible only to the router nodes in the first topology domain, the private topology information of the first topology domain including node information of each router node in the first topology domain and a second connection relationship of each router node in the first topology domain within the first topology domain.

2. The satellite network architecture as described in claim 1, wherein the first connection relationship includes a virtual logical connection relationship between ABR nodes located in the same topology domain and a physical connection relationship between two ABR nodes located in different topology domains, and the second connection relationship includes a physical connection relationship; in, For the first ABR node and the second ABR node in the same topology domain, the virtual logical connection between the first ABR node and the second ABR node is established through the first configuration information in the first ABR node, the first configuration information including the address information of the second ABR node.

3. The satellite network architecture as described in claim 1, wherein each router node in the first topology domain constitutes a first private topology in the first topology domain, each ABR node in the plurality of topology domains constitutes a common topology, and the first private topology and the common topology share each ABR node in the first topology domain; in, For any third ABR node in the first topology domain, the first private topology and the public topology are configured with the same Border Gateway Protocol (BGP) address family on the third ABR node. The third ABR node includes a first BGP neighbor type, which is used to control the route advertising of the third ABR node based on preset route advertising rules, so that the private topology information of the first topology domain is visible only to the router nodes in the first topology domain, and the public topology information of each ABR node in the multiple topology domains is visible to each router node in the multiple topology domains.

4. The satellite network architecture as described in claim 3, wherein the routing announcement rules include: Private topology information of the first topology domain is not allowed to be sent to other router nodes outside the first topology domain; The node information and third connection relationship of the third ABR node are allowed to be published on the neighboring nodes of the third ABR node. The third connection relationship includes the physical connection relationship and virtual logical connection relationship between the third ABR node and other ABR nodes. Allows the routing prefixes of each router node in the first topology domain to be advertised to other router nodes in the multiple topology domains; It allows the public topology information of each ABR node in the first topology domain to be published to other router nodes in the multiple topology domains.

5. A route advertising method in a satellite network architecture, the satellite network architecture comprising multiple topology domains, each topology domain comprising at least one router node in a satellite orbit, the method being applied to any first router node in any first topology domain among the multiple topology domains, the method comprising: Receive the routing prefix from the second router node; The target path is determined based on at least one of public topology information and private topology information of the first topology domain. The private topology information of the first topology domain includes node information of each router node in the first topology domain and a second connection relationship of each router node in the first topology domain. The public topology information includes node information of each ABR node in the plurality of topology domains and a first connection relationship between each ABR node. The private topology information of the first topology domain is only visible to router nodes in the first topology domain, while the public topology information is visible to all router nodes in the plurality of topology domains. The target path is used by the first router node to forward packets carrying the routing prefix.

6. The method of claim 5, wherein the first connection relationship includes a virtual logical connection relationship between ABR nodes located in the same topology domain and a physical connection relationship between two ABR nodes located in different topology domains, and the second connection relationship includes a physical connection relationship.

7. The method of claim 6, wherein, when the first router node is an ABR node in the first topology domain, before receiving the routing prefix of the second router node, the method further comprises: A virtual logical connection is established between the first router node and other ABR nodes in the first topology domain based on the first configuration information, wherein the first configuration information includes the address information of the other ABR nodes.

8. The method as described in claim 5, wherein each internal node in the first topology domain constitutes a first private topology in the first topology domain, each ABR node in the plurality of topology domains constitutes a public topology, and the first private topology and the public topology share each ABR node in the first topology domain. in, When the first router node is an ABR node in the first topology domain, the method further includes: The first router node is configured with the same BGP address family for the first private topology and the public topology. The first router node includes a first BGP neighbor type, which is used to control the route advertising of the first router node based on preset route advertising rules, so that the private topology information of the first topology domain is visible only to the router nodes in the first topology domain, and the public topology information of each ABR node in the multiple topology domains is visible to each router node in the multiple topology domains.

9. The method of claim 8, wherein the route publishing rules include: Private topology information of the first topology domain is not allowed to be sent to router nodes in other topology domains outside the first topology domain; The node information and third connection relationship of the first router node are allowed to be published on the neighboring nodes of the first router node. The third connection relationship includes the physical connection relationship and virtual logical connection relationship between the first router node and other ABR nodes. Allows the routing prefixes of each router node in the first topology domain to be advertised to other router nodes in the multiple topology domains; It allows the public topology information of each ABR node in the first topology domain to be published to other router nodes in the multiple topology domains.

10. The method of any one of claims 5 to 9, wherein the first router node is an ABR node in the first topology domain, and the step of determining the target path based on at least one of public topology information and private topology information of the first topology domain includes: When the second router node is a router node in the first topology domain, the target path is determined based on the private topology information of the first topology domain, and the target path includes the path from the first router node to the second router node; If the second router node is an ABR node outside the first topology domain, the target path is determined based on the public topology information, and the target path includes the path from the first router node to the second router node; When the second router node is an internal node in the second topology domain, the target path is determined based on the public topology information. The target path includes the path from the first router node to the ABR node in the second topology domain, where the second topology domain is another topology domain outside the first topology domain.

11. The method of any one of claims 5 to 9, wherein the first router node is an internal node in the first topology domain, and the step of determining the target path based on at least one of public topology information and private topology information of the first topology domain includes: When the second router node is a router node within the first topology domain, the target path is determined based on the private topology information of the first topology domain, and the target path includes the path from the first router node to the second router node; When the second router node is an ABR node outside the first topology domain, the target path is determined based on the public topology information and the private topology information of the first topology domain. The target path includes the path from the first router node to the second router node. When the second router node is an internal node in the third topology domain, the target path is determined based on the public topology information and the private topology information of the first topology domain. The target path includes the path from the first router node to the ABR node in the third topology domain, where the third topology domain is a topology domain other than the first topology domain.

12. The method of claim 5, wherein the routing prefix includes extended information, the extended information recording the identification information of the ABR nodes traversed by the routing prefix; after receiving the routing prefix of the second router node, the method further includes: If the first router node is an ABR node, determine whether the extended information includes the identification information of the first router node; If the extended information includes the identification information of the first router node, the routing prefix is ​​discarded; If the identification information of the first router node is not included in the extended information, the identification information of the first router node shall be added to the extended information.

13. The method as described in claim 12, wherein the format of the extended information is the same as the format of the cluster_list defined in the BGP route, both the extended information and the cluster_list include a type field, and the value of the type field of the extended information is different from the value of the type field of the cluster_list.

14. The method of claim 5, further comprising: A routing table is generated based on the routing prefix and the destination path. The routing table includes a routing information base (RIB) table and a forwarding information base (FIB) table. In response to receiving the first message, the first message is forwarded according to the routing table, the first message carrying the routing prefix.

15. The method of claim 14, wherein forwarding the first packet according to the routing table comprises: The forwarding path of the first packet is determined based on the routing prefix in the first packet and the routing table. When the first router node is an ABR node and the forwarding path includes virtual logical connection links between the first router node and other ABR nodes in the first topology domain, a first path is determined based on the private topology information of the first topology domain. The first path includes physical connection links from the first router node to other ABR nodes in the first topology domain. The first message is forwarded to the ABR node corresponding to the virtual logical connection link based on the first path.

16. An electronic device comprising: processor; Memory used to store the processor's executable instructions; The processor is configured to execute the instructions to implement the method as described in any one of claims 5 to 15.

17. A computer-readable storage medium, wherein instructions in the storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the method as described in any one of claims 5 to 15.

18. A computer program product comprising a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform the method as claimed in any one of claims 5 to 15.

Images