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 sub-domains, the plurality of sub-domains comprise topological domains and a backbone domain, the topological domains comprise at least one router node in a satellite orbit, two adjacent topological domains are connected through the backbone domain, the backbone domain comprises ABR (Area Border Router) nodes in the two topological domains connected with the backbone domain, and for any first sub-domain in the plurality of sub-domains, the topological information of each router node in the first sub-domain is only visible to the router node in the first sub-domain. Therefore, the satellite network architecture is divided into the topological domain and the backbone domain which are isolated from each other, so that a fault can be limited within a certain range when a certain node or link fails, the fault is prevented from being spread in the whole network, the fault can be effectively isolated, and the influence on terminal communication service is reduced.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of communication, and in particular to a satellite network architecture, a route publishing method, a device, a medium and a program product. BACKGROUND

[0002] The satellite network architecture includes a plurality of satellite routers. The plurality of routers can use a routing protocol and transmit data packets through a corresponding routing mechanism, thereby providing communication services for terminals. In recent years, with the accelerated development of low-orbit satellites, the scale of the satellite network architecture is also becoming larger. In this case, when a certain router node or link in the satellite network architecture fails, based on the current routing mechanism, the failure will be propagated throughout the network, causing a network-wide failure, which seriously affects the communication services of the terminals. SUMMARY

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

[0004] To solve the above technical problems, the present application is implemented as follows: In a first aspect, a satellite network architecture is provided, including a plurality of sub-domains, the plurality of sub-domains including a topology domain and a backbone domain, the topology domain including router nodes in at least one satellite orbit, two adjacent topology domains being connected through the backbone domain, the backbone domain including area border router (ABR) nodes in two topology domains connected by the backbone domain, and for any first sub-domain in the plurality of sub-domains, topology information of each router node in the first sub-domain being only visible to router nodes in the first sub-domain.

[0005] In a second aspect, a route publishing method in a satellite network architecture is provided, the satellite network architecture including a plurality of sub-domains, the plurality of sub-domains including a topology domain and a backbone domain, the topology domain including router nodes in at least one satellite orbit, two adjacent topology domains being connected through the backbone domain, the backbone domain including area border router (ABR) nodes in two topology domains connected by the backbone domain; the method being applied to any first router node in the plurality of sub-domains, and including: receiving a routing prefix of a third router node sent by a second router node; determine a target path according to target topology information, the target topology information comprising topology information of each router node in a first sub-domain to which the first router node and the second router node belong, the topology information of each router node in the first sub-domain being only visible to the router nodes in the first sub-domain, the target path being used by the first router node to forward the packet carrying the routing prefix.

[0006] In a third aspect, an electronic device is provided, comprising: a processor; a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions to implement the method according to the second aspect.

[0007] In a fourth aspect, a computer-readable storage medium is provided, which, when instructions in the storage medium are executed by a processor of an electronic device, enables the electronic device to perform the method according to the second aspect.

[0008] In a fifth aspect, a computer program product is provided, the computer program product comprising a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform the method according to the second aspect.

[0009] In the embodiments of the present application, the satellite network architecture can be divided into multiple sub-domains, the multiple sub-domains including topology domains and backbone domains, the topology domains being divided as basic units by router nodes in one or more satellite orbits, each topology domain including router nodes in at least one satellite orbit, two adjacent topology domains being connected through a backbone domain, and the backbone domain including area border router (ABR) nodes in the two topology domains connected by the backbone domain. The topology domains and the backbone domains are isolated from each other, that is, for any first sub-domain in the multiple sub-domains, the topology information of each router node in the first sub-domain is only visible to the router nodes in the first sub-domain. In this way, by dividing the satellite network architecture into isolated topology domains and backbone domains, the fault can be limited within a certain range when a node or a link fails, and the fault is avoided from spreading in the whole network. Compared with the whole network fault caused by the failure of a router node or a link in the satellite network architecture in the related art, the effective isolation of the fault can be achieved, thereby reducing the impact on the terminal communication service. BRIEF DESCRIPTION OF DRAWINGS

[0010] In order to more clearly illustrate the technical solutions in the present application or the prior art, the accompanying drawings needed to be used in the embodiments or prior art description will be briefly introduced. Obviously, the accompanying drawings in the following description only represent some embodiments described in the present application, and for those skilled in the art, other drawings can also be obtained from these drawings without creative labor.

[0011] Figure 1 is a structural schematic diagram of a satellite network architecture in the related art; Figure 2 is a structural schematic diagram of a satellite network architecture in an embodiment of the present application; Figure 3 is a flow schematic diagram of a route publishing method in a satellite network architecture in an embodiment of the present application; Figure 4 is a schematic diagram of a route publishing method in a satellite network architecture in an embodiment of the present application; Figure 5 is a schematic diagram of inter-domain traffic cross-domain transmission in an embodiment of the present application; Figure 6 is a schematic diagram of cross-domain loop prevention in an embodiment of the present application; Figure 7 is a structural schematic diagram of an electronic device in an embodiment of the present application; Figure 8 is a structural schematic diagram of a route publishing device in a satellite network architecture in an embodiment of the present application. DETAILED DESCRIPTION

[0012] In the related art, the scale of the satellite network architecture is large, when a certain router node or link fails, based on the current routing mechanism of each satellite router in the satellite network architecture, the failure will be propagated in the whole network, causing a whole network failure, which seriously affects the communication service of the terminal. In addition, when a certain router node or link fails, there will also be a large amount of route flooding, affecting route convergence, and each satellite router usually comes from multiple device manufacturers, when the satellite router is debugged, the debugging of multiple device manufacturers may affect each other, resulting in difficult debugging.

[0013] In order to solve the above problems, the satellite network architecture can be reasonably divided.

[0014] Figure 1 is a structural schematic diagram of a satellite network architecture in the related art. Figure 1The satellite network architecture shown is a network architecture of low-orbit satellites, and adopts a mesh architecture. The satellite network architecture includes N orbits, each orbit includes N satellite routers (Satellite-Router, S-R), and the satellite routers can use a routing protocol (such as a Border Gateway Protocol (BGP)) and a related routing mechanism to relay data packets, thereby providing communication services for terminals.

[0015] Based on Figure 1 The satellite network architecture shown faces new challenges when it is divided into domains compared to the division of ground networks. For example, the functions and capabilities of different levels of routers in the ground network are different, and based on such characteristics, the ground network can be divided into a normal domain and a backbone domain, and the functions and capabilities of each satellite router in the satellite network are consistent, so the current division method of the ground network is not applicable to the satellite network. For another example, the links of low-orbit satellite routers are valuable, and when an inter-satellite link failure causes the routing prefix in the same domain to be inaccessible within the domain link, it is hoped that the traffic will be bypassed through other domains to ensure the reliability of the service, and the current division mechanism of the ground network does not allow intra-domain traffic to bypass across domains in order to prevent loops.

[0016] In the face of the above problems, an embodiment of the present application provides a satellite network architecture, which includes a plurality of sub-domains, the plurality of sub-domains including a topology domain and a backbone domain, the topology domain including router nodes in at least one satellite orbit, two adjacent topology domains being connected through the backbone domain, the backbone domain including area border router (ABR) nodes in the two topology domains connected by the backbone domain, and for any first sub-domain in the plurality of sub-domains, topology information of each router node in the first sub-domain is only visible to the router nodes in the first sub-domain. In this way, by dividing the satellite network architecture into mutually isolated topology domains and backbone domains, the fault can be limited within a certain range when a node or link fails, avoiding the propagation of the fault in the whole network, and compared to the whole network failure caused by the failure of a router node or link in the satellite network architecture in the related art under the whole domain condition, the effective isolation of the fault can be achieved, thereby reducing the impact on the terminal communication service.

[0017] In addition, the embodiment of the present application further provides a routing publishing method, device, medium and program product in a satellite network architecture, which can publish the routing prefix of each router node in the satellite network architecture. For the routing prefix of a certain third router node, the first router node calculates a target path from the first router node to a second router node when the routing prefix passes through the first router node, so that when a message carrying the routing prefix is received, the message can be forwarded based on the target path, and the transmission of the message in the satellite network architecture is realized, thereby ensuring the communication service provided for the terminal based on the domain.

[0018] In order for those skilled in the art to better understand the technical solutions in the present application, the technical solutions in the present application will be clearly and completely described below in combination with the drawings in one or more embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor should belong to the protection scope of the present application.

[0019] The terms "first", "second", and the like in the present application and claims are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the present application can be implemented in an order other than those illustrated or described herein. In addition, "and / or" in the present application and claims indicates at least one of the connected objects, and the character " / " generally indicates that the front and rear associated objects are in an "or" relationship.

[0020] The technical solutions provided by the embodiments of the present application will be described in detail below in combination with the drawings.

[0021] The satellite network architecture provided in the embodiments of the present application includes a plurality of sub-domains, the plurality of sub-domains including a topology domain and a backbone domain, the number of topology domains can be multiple, and the number of backbone domains can also be multiple. The topology domain includes at least one router node in a satellite orbit, two adjacent topology domains are connected through a backbone domain, and the backbone domain includes an area border router (ABR) node in the two topology domains connected by the backbone domain. That is, the embodiments of the present application take the router node in one or more satellite orbits as a basic unit, divide the satellite network architecture into a plurality of topology domains, each topology domain includes an ABR node, and the ABR nodes in two adjacent topology domains are connected to form a backbone domain, that is, the backbone domain includes two ABR nodes, and the two ABR nodes come from different topology domains. Among them, the topology domain and the backbone domain are isolated from each other, different topology domains are isolated from each other, and different backbone domains are also isolated from each other. In the case of mutual isolation, for any first sub-domain (backbone domain or topology domain) in the plurality of sub-domains, the topology information of each router node in the first router node is only visible to the router node in the first sub-domain. Among them, the topology information of each router node in the first sub-domain includes the node information (such as identification information, etc.) and the connection relationship of each router node in the first sub-domain, and the connection relationship is a physical connection relationship.

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

[0023] Figure 2 Taking the satellite network architecture including three satellite orbits as an example, the satellite network architecture is divided into four sub-domains, which are topology domain 1, topology domain 2, backbone domain 1 and backbone domain 2. The topology domain 1 includes the router nodes in the satellite orbit 1, and the topology domain 2 includes the router nodes in the satellite orbits 2 and 3. The ABR nodes in the topology domain 1 are router 1.1 and router 1.3, and the internal node is router 1.2. The ABR nodes in the topology domain 2 are router 2.1.1, router 2.2.1, router 2.1.3 and router 2.2.3, and the internal nodes are router 2.1.2 and router 2.2.2. The topology domain 1 and the topology domain 2 are connected through the backbone domain 1 and the backbone domain 2, the backbone domain 1 includes two ABR nodes, namely router 1.1 and router 2.1.1, and the backbone domain 2 includes two ABR nodes, namely router 1.3 and router 2.1.3. It should be noted that Figure 2 The ABR nodes in each topology domain shown are only exemplary, and in other possible implementations, the ABR nodes in each topology domain can also be other router nodes in the present topology domain, which is not specifically limited here. For example, in some possible implementations, the ABR nodes in the topology domain 2 can be router 2.1.1, router 2.2.1, router 2.1.2 and router 2.2.2.

[0024] Figure 2 In the above example, the different sub-domains are isolated from each other. For any sub-domain, the topology information of the router nodes in the sub-domain is only visible to the router nodes in the sub-domain. For example, the topology information of the routers in topology domain 1 is only visible to the three routers in topology domain 1, and is not visible to the other six routers. The topology information of the routers in topology domain 2 is only visible to the six routers in topology domain 2, and is not visible to the other three routers. The topology information of the routers in backbone domain 1 is only visible to the two routers in backbone domain 1, and is not visible to the other seven routers. The topology information of the routers in backbone domain 2 is only visible to the two routers in backbone domain 2, and is not visible to the other seven routers.

[0025] For any first sub-domain, the topology information of the router nodes in the first sub-domain includes the node information of the router nodes in the first sub-domain and the connection relationship between the router nodes in the first sub-domain. For example, the topology information of the router nodes in topology domain 1 includes the node information of routers 1.1, 1.2 and 1.3, the connection relationship between router 1.2 and router 1.1, and the connection relationship between router 1.2 and router 1.3. The topology information of the router nodes in topology domain 2 includes the node information of routers 2.1.1, 2.1.2, 2.1.3, 2.2.1, 2.2.2 and 2.2.3, the connection relationship between router 2.1.2 and routers 2.1.1, 2.2.2 and 2.1.3, and the connection relationship between router 2.2.2 and routers 2.1.2, 2.2.1 and 2.2.3. The topology information of the router nodes in backbone domain 1 includes the node information of routers 1.1 and 2.1.1, and the connection relationship between routers 1.1 and 2.1.1. The topology information of the router nodes in backbone domain 2 includes the node information of routers 1.3 and 2.1.3, and the connection relationship between routers 1.3 and 2.1.3. The connection relationship between the router nodes includes a physical connection relationship.

[0026] In this way, by dividing the satellite network architecture into isolated topology domains and backbone domains, the fault can be limited within a certain range when a node or link fails, avoiding the propagation of the fault in the entire network. Compared with the entire network fault caused by the failure of a router node or link in the satellite network architecture in the related art, the fault can be effectively isolated, thereby reducing the impact on the terminal communication service.

[0027] Based on the division mode of the satellite network architecture according to the embodiments of the present application, for any ABR node in the satellite network architecture, the sub-domain where the ABR node is located or belongs to has two sub-domains. For example, Figure 2The sub-domain in which the router 1.1 in the above table is located includes the topology domain 1 and the backbone domain 1. In order to realize that the topology information of each router node in any first sub-domain is only visible to the router nodes in the first sub-domain, that is, in order to realize the isolation between different sub-domains, the ABR node can be configured accordingly. Taking any topology domain and the backbone domain adjacent to the topology domain as an example, the topology domain and the adjacent backbone domain can be isolated from each other in any one of the following modes 1 to 3, that is, the topology domain and the adjacent backbone domain can satisfy the content recorded in any one of the following modes.

[0028] Mode 1: The topology domain and the backbone domain configure the same Border Gateway Protocol (BGP) address family on the first ABR node. In addition, a BGP neighbor type can be added in the first ABR node. Taking the first BGP neighbor type as an example, the first BGP neighbor type can represent a new route publishing rule, which can be represented as a preset route publishing rule. The first BGP neighbor type is used to control the route publishing of the first ABR node based on the preset route publishing rule to realize the mutual isolation between the topology domain to which the first ABR node belongs and the backbone domain to which the first ABR node belongs.

[0029] In some embodiments, the preset route publishing rule can include: not allowing the topology information of each router node in the topology domain in which the first ABR node is located to be published to the router nodes in the adjacent backbone domain; allowing the node information of the first ABR node and the connection relationship between the first ABR node and the adjacent ABR node to be published on the adjacent ABR node to construct the backbone domain; allowing the route prefix of each router node in the topology domain in which the first ABR node is located to be redistributed to the backbone domain in which the first ABR node is located, and modifying the publishing source to the first ABR node; not allowing the topology information of each router node in the backbone domain in which the first ABR node is located to be published to the router nodes in any topology domain; allowing the route prefix of each router node in the backbone domain in which the first ABR node is located to be redistributed to the topology domain in which the first ABR node is located, and modifying the publishing source to the first ABR node.

[0030] Mode 2: The topology domain and the backbone domain configure different BGP instances on the first ABR node. The route prefix of each router node in the topology domain and the route prefix of each router node in the backbone domain are mutually directed between the different BGP instances through redistribution. The publishing source of the route prefix after mutual direction is modified to the first ABR node.

[0031] The BGP of the topology domain and the backbone domain can be the same address family or different address families, and no limitation is made. In the manner 2, the route publishing rule of the first ABR node is: The topology routes of different BGP instances are naturally isolated, and the route prefixes of the router nodes in the topology domain and the backbone domain where the first ABR node is located are mutually guided between different BGP instances through redistribution. After mutual guidance, the publishing source of the route prefix is modified to the first ABR node. The mutual guidance can be understood as the meaning of intercommunication and interaction, and the route prefixes in different sub-domains are mutually guided, that is, the route prefixes can reach from one sub-domain to another sub-domain.

[0032] Manner 3: Different BGP address families are configured for the topology domain and the backbone domain on the first ABR node, the route prefixes of the router nodes in the topology domain and the route prefixes of the router nodes in the backbone domain are mutually guided through redistribution between different BGP address families, and the publishing source of the route prefix after mutual guidance is modified to the first ABR node.

[0033] Different BGP address families are configured for the topology domain and the backbone domain on the first ABR node, for example, the BGP-SPF address family is enabled for the topology domain, and the BGPv6 address family is enabled for the backbone domain.

[0034] In the manner 3, the route publishing rule of the first ABR node is: The topology of the topology domain and the backbone domain is naturally isolated because different BGP address families are used, the route prefixes of the router nodes in the topology domain and the backbone domain are mutually guided through redistribution between different BGP address families, and the publishing source of the route prefix after mutual guidance is modified to the first ABR node. The mutual guidance can be understood as the meaning of intercommunication and interaction, and the route prefixes in different sub-domains are mutually guided, that is, the route prefixes can reach from one sub-domain to another sub-domain.

[0035] In this way, by configuring the first ABR node as described above, the mutual isolation between the topology domain to which the first ABR node belongs and the backbone domain to which the first ABR node belongs can be achieved. It should be noted that in actual application, any one of the manners 1 to 3 described above can be selected to isolate the topology domain and the backbone domain to which the first ABR node belongs according to actual needs, and no specific limitation is made here.

[0036] The satellite network architecture provided in the embodiments of the present application can be divided into multiple sub-domains, the multiple sub-domains include a topology domain and a backbone domain, the topology domain is divided into basic units of router nodes in one or more satellite orbits, each topology domain includes at least one router node in a satellite orbit, two adjacent topology domains are connected through the backbone domain, and the backbone domain includes area border router (ABR) nodes in two topology domains connected by the backbone domain. The topology domain and the backbone domain are isolated from each other, that is, for any first sub-domain in the multiple sub-domains, the topology information of each router node in the first sub-domain is only visible to the router nodes in the first sub-domain. In this way, by dividing the satellite network architecture into the isolated topology domain and the backbone domain, the fault can be limited within a certain range when a node or a link fails, and the fault is prevented from spreading in the whole network. Compared with the whole network fault caused by the failure of a router node or a link in the satellite network architecture in the related art in the whole domain, the effective isolation of the fault can be implemented, and the influence on the terminal communication service is reduced.

[0037] Based on the satellite network architecture provided in the embodiments of the present application, a routing distribution method in the satellite network architecture is further provided, and the routing distribution of each router node in the satellite network architecture in the whole network can be implemented.

[0038] Figure 3 FIG. 1 is a flowchart of a routing distribution method in a satellite network architecture according to an embodiment of the present application. Figure 3 The method shown in FIG. 1 can be applied to any first router node in any sub-domain in the multiple sub-domains of the satellite network architecture, that is, Figure 3 The method shown in FIG. 1 can be executed by software or hardware installed in the first router node. The first router node can be an ABR node or a router node other than the ABR node, which is not limited here. The routing distribution method includes the following steps.

[0039] S302: receiving a routing prefix of a third router node sent by a second router node.

[0040] The second router node is any router node adjacent to the first router node in the satellite network architecture. The second router node can be an ABR node or a router node other than the ABR node, which is not limited here. The third router node is any router node other than the first router node in the satellite network architecture. The third router node can be an ABR node or a router node other than the ABR node, which is not limited here. The second router node and the third router node can be the same router node or different router nodes, which is not limited here.

[0041] In the routing publishing, the routing prefix of the third router node can be published to all the router nodes in the network. In this case, for the second router node, after receiving the routing prefix of the third router node, the second router node can send the routing prefix of the third router node to the first router node. The first router node can receive the routing prefix of the third router node sent by the second router node. Alternatively, if the second router node and the third router node are the same router node, the first router node can directly receive the routing prefix of the second router node (i.e., the routing prefix of the third router node) sent by the second router node.

[0042] S304: determining a target path according to target topology information, the target topology information including topology information of each router node in a first sub-domain to which the first router node and the second router node belong, the topology information of each router node in the first sub-domain being visible only to the router nodes in the first sub-domain, the target path being used for the first router node to forward a packet carrying the routing prefix of the third router node.

[0043] In the routing publishing, the routing prefix of the third router node can be published to all the router nodes in the network. In this case, for the second router node, after receiving the routing prefix of the third router node, the second router node can send the routing prefix of the third router node to the first router node. The first router node can receive the routing prefix of the third router node sent by the second router node. Alternatively, if the second router node and the third router node are the same router node, the first router node can directly receive the routing prefix of the second router node (i.e., the routing prefix of the third router node) sent by the second router node.

[0044] In the routing publishing, the routing prefix of the third router node can be published to all the router nodes in the network. In this case, for the second router node, after receiving the routing prefix of the third router node, the second router node can send the routing prefix of the third router node to the first router node. The first router node can receive the routing prefix of the third router node sent by the second router node. Alternatively, if the second router node and the third router node are the same router node, the first router node can directly receive the routing prefix of the second router node (i.e., the routing prefix of the third router node) sent by the second router node. Figure 2In the backbone domain 1, which is the first subdomain, router 1.1 is the first router node, router 2.1.1 is the second router node, and router 2.2.2 is the third router node. Since the topology information of each router node in each subdomain is only visible to router nodes within that subdomain, the topology information visible to router 1.1 only includes the topology information of each router node in topology domain 1 and the topology information of each router node in backbone domain 1. Because the routing prefix of router 2.2.2 is sent from router 2.1.1 to router 1.1, and both routers 2.1.1 and 1.1 reside in backbone domain 1, router 1.1 determines the target path based on the topology information of each router node in backbone domain 1 (i.e., the target topology information) when calculating the target path.

[0045] In some implementations, the topology information of each router node in the first subdomain includes the node information of each router node in the first subdomain and the connection relationships between the router nodes in the first subdomain. For example, using... Figure 2 Taking topology domain 1 and backbone domain 1 as examples, the topology information of each router node in topology domain 1 includes the node information of routers 1.1, 1.2, and 1.3, the connection relationship between router 1.2 and router 1.1, and the connection relationship between router 1.2 and router 1.3. This information is only visible to the three router nodes in topology domain 1 and is not visible to the other six router nodes. The topology information of each router node in backbone domain 1 includes the node information of routers 1.1 and 2.1.1, and the connection relationship between routers 1.1 and 2.1.1. This information is only visible to the two router nodes in backbone domain 1 and is not visible to the other seven router nodes. The connection relationships between the router nodes include physical connections.

[0046] For any ABR node in the satellite network architecture, the domain to which the ABR node is located or belongs has two domains. For example, Figure 2 Router 1.1 in the diagram belongs to a domain comprising topology domain 1 and backbone domain 1. To ensure that the topology information of each router node in any first domain is only visible to router nodes within that first domain, i.e., to achieve isolation between different domains, the ABR node can be configured accordingly. Taking the first domain as an example, when the first router node is the ABR node in the first domain, the first topology domain to which the first router node belongs and the first backbone domain to which the first router node belongs can be mutually isolated using any of the following methods.

[0047] Method 1: configuring the same BGP address family for the first topology domain and the first backbone domain on the first router node, and additionally, adding a BGP neighbor type in the first router node, taking the first BGP neighbor type as an example, the first BGP neighbor type can represent a new route publishing rule, which can be represented as a preset route publishing rule, and the first BGP neighbor type is used to control the route publishing of the first router node according to the preset route publishing rule to realize the mutual isolation of the first topology domain and the first backbone domain.

[0048] In some embodiments, the preset route publishing rule can include: not allowing the topology information of each router node in the first topology domain to be published to the router nodes in the first backbone domain; allowing the node information of the first router node and the connection relationship between the first router node and the neighbor ABR node to be published on the neighbor ABR node to construct the first backbone domain; allowing the route prefix of each router node in the first topology domain to be redistributed to the first backbone domain, and modifying the publishing source to the first router node; not allowing the topology information of each router node in the first backbone domain to be published to the router nodes in the first topology domain; allowing the route prefix of each router node in the first backbone domain to be redistributed to the first topology domain, and modifying the publishing source to the first router node.

[0049] Method 2: configuring different BGP instances for the first topology domain and the first backbone domain on the first router node, and the route prefix of each router node in the first topology domain and the route prefix of each router node in the first backbone domain are mutually directed between different BGP instances through redistribution, and the publishing source of the route prefix after mutual direction is modified to the first router node.

[0050] Wherein, the BGP of the first topology domain and the first backbone domain can be the same address family or different address families, which is not limited. In method 2, the route publishing rule of the first router node is: The topology routes between different BGP instances are naturally isolated, the route prefix of each router node in the first topology domain and the first backbone domain is mutually directed between different BGP instances through redistribution, and the publishing source of the route prefix after mutual direction is modified to the first router node. Wherein, mutual direction can be understood as the meaning of mutual communication and interaction, and the route prefix in different domains is mutually directed, that is, the route prefix can reach from one domain to another domain.

[0051] Method 3: configuring different BGP address families for the first topology domain and the first backbone domain on the first router node, and realizing mutual guidance between the routing prefixes of the router nodes in the first topology domain and the routing prefixes of the router nodes in the first backbone domain through redistribution between the different BGP address families, and modifying the publication source of the routing prefixes after mutual guidance to the first router node.

[0052] In the first router node, different BGP address families are configured for the first topology domain and the first backbone domain, for example, BGP-SPF address family can be enabled in the first topology domain, and BGPv6 address family can be enabled in the first backbone domain.

[0053] In method 3, the routing publication rule of the first router node is: The topology of the first topology domain and the first backbone domain is naturally isolated because different BGP address families are used, the routing prefixes of the router nodes in the first topology domain and the first backbone domain are guided through redistribution between the different BGP address families, and the publication source of the routing after mutual guidance is modified to the first router node. The mutual guidance can be understood as mutual and interactive, and the routing prefixes in different domains are guided, that is, the routing prefixes can reach from one domain to another domain.

[0054] In this way, the first router node can realize mutual isolation between the first topology domain and the first backbone domain to which the first router node belongs by performing the above configuration. It should be noted that in actual application, the first router node can select any one of the above methods 1 to 3 to isolate the first topology domain and the first backbone domain to which the first router node belongs according to actual needs, which is not limited here.

[0055] When the first router node calculates the target path, because the domain to which the first router node belongs is isolated from other domains, the topology information of the router nodes in other domains is invisible to the first router node, therefore, for different scenarios, such as whether the first router node and the third router node are in the same domain, whether the domain is a topology domain or a backbone domain, etc., the finally calculated target path can have multiple cases, In some embodiments, the first domain to which the first router node and the second router node belong is a topology domain, in which case, the calculated target path can be divided into the following scenarios 1 to 3.

[0056] Scenario 1: in the case where the third router node is located in the first sub-domain, the target path is the path between the first router node and the third router node. That is, in the case where the first router node, the second router node and the third router node are all located in the same topology domain, the target path calculated by the first router node includes the path from the first router node to the third router node. Taking the routers 2.1.1, 2.1.2 and 2.2.3 shown in FIG. 2 as an example, the router 2.1.1 is the first router node, the router 2.1.2 is the second router node and the router 2.2.3 is the third router node, and the target path calculated by the router 2.1.1 is the optimal or shortest path from the router 2.1.1 to the router 2.2.3. Figure 2

[0057] Scenario 2: in the case where the third router node is located in another sub-domain other than the first sub-domain and the second router node is an internal node in the first sub-domain, the target path is the path between the first router node and the ABR node in the first sub-domain receiving the routing prefix of the third router node, and the internal node is a router node other than the ABR node in the first sub-domain. Taking the routers 2.2.2, 2.1.2 and 1.1 shown in FIG. 2 as an example, the router 2.2.2 is the first router node, the router 2.1.2 is the second router node and the router 1.1 is the third router node, and the target path calculated by the router 2.2.2 is the optimal or shortest path from the router 2.2.2 to the router 2.1.1. Figure 2

[0058] Scenario 3: in the case where the third router node is located in another sub-domain other than the first sub-domain and the second router node is an ABR node in the first sub-domain, the target path is the path between the first router node and the second router node. Taking the routers 2.1.2, 2.1.1 and 1.1 shown in FIG. 2 as an example, the router 2.1.2 is the first router node, the router 2.1.1 is the second router node and the router 1.1 is the third router node, and the target path calculated by the router 2.1.2 is the optimal or shortest path from the router 2.1.2 to the router 2.1.1. Figure 2

[0059] In some embodiments, the first sub-domain to which the first router node and the second router node belong is a backbone domain, and in this case, the target path is the path from the first router node to the second router node. Taking the routers 2.1.1, 1.1 and 1.2 shown in FIG. 2 as an example, the router 2.1.1 is the first router node, the router 1.1 is the second router node and the router 1.2 is the third router node, and the target path calculated by the router 2.1.1 is the optimal or shortest path from the router 2.1.1 to the router 1.1. Figure 2

[0060] In some embodiments, after determining the target path according to the target topology information, the first router node further includes: ​​​​In the case that the first router node is an ABR node, the third router node's routing prefix is sent to other router nodes in the first sub-domain, or the third router node's routing prefix is redistributed to a second sub-domain where the first router node is located, and the publishing source of the routing prefix is modified to the first router node, and the second sub-domain is another sub-domain other than the first sub-domain, which can be a backbone domain or a topology domain. For example, as shown in FIG. 2, the router 2.1.1 is the first router node, the router 1.1 is the second router node, and the router 1.2 is the third router node. The router 2.1.1 can send the router 1.2's routing prefix to other router nodes in the topology domain 2. Figure 2 For another example, as shown in FIG. 3, the router 2.1.1 is the first router node, the router 2.1.2 is the second router node, and the router 2.2.2 is the third router node. The router 2.1.1 can redistribute the router 2.2.2's routing prefix to the backbone domain 1, and modify the publishing source of the router 2.2.2's routing prefix to the router 2.1.1. Figure 2 For another example, as shown in FIG. 3, the router 2.1.1 is the first router node, the router 2.1.2 is the second router node, and the router 2.2.2 is the third router node. The router 2.1.1 can redistribute the router 2.2.2's routing prefix to the backbone domain 1, and modify the publishing source of the router 2.2.2's routing prefix to the router 2.1.1.

[0061] In some embodiments, after determining the target path according to the target topology information, the first router node further includes: In the case that the first sub-domain is a topology domain and the first router node is an internal node, the third router node's routing prefix is sent to other router nodes in the first sub-domain, and the internal node is another router node in the first sub-domain other than the ABR node. For example, as shown in FIG. 2, the router 2.1.2 is the first router node, the router 2.1.1 is the second router node, and the router 1.1 is the third router node. The router 2.1.2 can send the router 1.1's routing prefix to other router nodes in the topology domain 2. Figure 2 For another example, as shown in FIG. 3, the router 2.1.2 is the first router node, the router 2.1.1 is the second router node, and the router 1.1 is the third router node. The router 2.1.2 can send the router 1.1's routing prefix to other router nodes in the topology domain 2.

[0062] In some embodiments, after obtaining the target path, the first router node further includes: generating a routing table according to the third router node's routing prefix and the target path, the routing table including a Routing Information Base (RIB) table and a Forwarding Information Base (FIB) table; in response to receiving the first packet, forwarding the first packet according to the routing table, and the first packet carrying the third router's routing prefix.

[0063] 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.

[0064] 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 4 . Figure 4 The satellite network architecture shown includes two topology domains and two backbone domains, which can be found in the following documents. Figure 2 The illustrated embodiment will not be described in detail here. Different domains are isolated from each other; the isolation method can be found in the description above and will not be repeated here. When different domains are isolated from each other, the routing prefix of each router node in each domain needs to be advertised across the entire network. Figure 4 Taking the example of router 2.2.2 advertising a loopback route to router 1.2, the route advertising process is as follows: Step 1: The routing prefix of router 2.2.2 is reflected hop-by-hop within topology domain 2, and routing RIB and FIB tables are generated on the router nodes it passes through, and then reflected to ABR node 2.1.1 within the domain.

[0065] Step 2: Because topology domain 2 and backbone domain 1 ( Figure 4 The skeletal region 1 is not shown in the text; please refer to [reference needed]. Figure 2 (As shown in the embodiment) isolation, so after receiving the route prefix, ABR node 2.1.1 will perform the best or shortest path calculation, calculate the optimal route, and then redistribute it into backbone domain 1 and modify the publishing source to router 2.1.1.

[0066] Step 3: There is only one path in backbone domain 1 (the connection between router 1.1 and router 2.1.1). After the control plane routes to router 1.1, because backbone domain 1 and topology domain 1 are isolated, ABR node 1.1 receives the route and performs the best or shortest path calculation to calculate the optimal route, generate the routing RIB and FIB tables, and then redistributes it into topology domain 1 and modifies the advertising source to router 1.1.

[0067] Step 4: Within topology domain 1, the route prefix is ​​reflected hop-by-hop to route node 1.2, and route RIB and FIB tables are generated on the router nodes traversed, thus ending the control plane route advertising process.

[0068] When the above control plane routing passes through each router node, the router node performs shortest path calculation and generates a corresponding routing RIB and FIB table.

[0069] Afterwards, when a data packet (or data flow) is forwarded from router 1.2 to router 2.2.2, the forwarding process is as follows: Router 1.2 forwards the data packet according to the generated routing FIB table and sends the data packet to router 1.1. Router 1.1 sends the data packet to router 2.1.1 based on the routing FIB table. Router 2.1.1 sends the data packet to router 2.2.2 based on the routing FIB table, and the forwarding process ends. The forwarding process of the data packet in the topology domain and the backbone domain is the same.

[0070] In the embodiment of the present application, the routing prefixes of each router node in the satellite network architecture can be published in the entire network. For the routing prefix of a third router node, the first router node calculates a target path from the first router node to the third router node when the routing prefix passes through the first router node. Therefore, when a packet carrying the routing prefix is received, the packet can be forwarded based on the target path, and the transmission of the packet in the satellite network architecture is realized, thereby ensuring the communication service for the terminal based on the domain division.

[0071] In actual applications, the link of the satellite router is very valuable. When the inter-satellite link fails, the prefix routing in the same topology domain cannot pass through the link in the domain, and it is hoped that the prefix routing can bypass through other topology domains to return, thereby maximizing the reliability of the service, as shown in FIG. 1. Figure 5 Figure 5 The data flow in FIG. 1 needs to flow from router 1.1 to router 1.2, but the link between router 1.1 and 1.2 fails, so the data flow cannot directly flow from router 1.1 to 1.2. In this case, the data flow can flow from router 2.1.1 and 2.1.2 to router 1.2, that is, the data flow in the domain can bypass through the domain. Based on the technical solution provided in the embodiment of the present application, the domain bypass of the data flow in the domain can be realized after the domain division of the satellite network architecture.

[0072] ​In the case of allowing data traffic in a domain to bypass the domain, anti-looping needs to be performed on the cross-domain traffic. In the related art, within an AS, the traffic of an IBGP domain adopts cluster_list anti-looping, the cluster_list is added with the ID of the router node along the way, and the message returned by the bypassing is checked for the node information of the cluster_list to perform anti-looping. In the satellite network architecture, if the cluster_list is still used for anti-looping by the tens of thousands of satellite routers, the length of the cluster_list message will be too long to be discarded. In addition, after the satellite network architecture is divided into domains, all the domains can be in different ASs, and the cluster_list cannot cross different domains. Therefore, on the basis of the domain division, the original anti-looping mechanism can be used in the domain, that is, the cluster_list is used for anti-looping, and then an extended information is newly defined for cross-domain anti-looping. The extended information can record the identification information of the ABR node passed by the data traffic. Since the number of ABR nodes is limited, the extended information is used for anti-looping check, which can greatly reduce the message load. The extended information can be applied to one AS or multiple ASs, which is not limited here.

[0073] Based on the above cross-domain anti-looping mechanism, when the route is published, the extended information recording the identification information of the ABR node passed by the route prefix can be included in the route prefix of the second router node. In this way, in the case that the first router node is an ABR node, the first router node can perform cross-domain anti-looping based on the extended information after receiving the route prefix of the second router node, which can specifically include: determining whether the identification information of the first router node is included in the extended information; in the case that the identification information of the first router node is included in the extended information, it indicates that the anti-looping check fails, and at this time, the route prefix can be discarded; in the case that the identification information of the first router node is not included in the extended information, it indicates that the anti-looping check passes, and at this time, the identification information of the first router node is added to the extended information, and then the first router node can determine the target path according to at least one of the public topology information and the private topology information of the first topology domain.

[0074] In some embodiments, the format of the extended information can be the same as the format of the cluster_list defined in the current BGP route. Alternatively, the extended information can be denoted as abr_cluster_list, both abr_cluster_list and cluster_list include a type field, the value of the type field of abr_cluster_list is different from the value of the type field of cluster_list, so as to distinguish abr_cluster_list and cluster_list.

[0075] Alternatively, 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| +---+---+---+---+---+---+---+---+---+---+ Wherein, O (Optional bit) = 1: indicates that this is an optional attribute. If the receiving party cannot identify this attribute, it should ignore the attribute and continue processing the message.

[0076] T (Transitive bit) = 0: indicates that this is a non-transitive attribute. If the receiving party cannot identify this attribute, it will not pass this attribute to its peer.

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

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

[0079] Type Code: that is, the type field, a new value can be allocated, such as 130.

[0080] For the convenience of understanding the cross-domain loop prevention provided by the embodiments of the present application, please refer to Figure 6 the embodiments shown in the drawings. Figure 6 In the embodiment, a route prefix is sent from a router 1.1, and passes through a router node 2.1, which is an ABR node. The node identifier of the router 2.1 is recorded in the abr_cluster_list of the route prefix, for example, the identifier is router-id 10.1.1.2. Similarly, when the prefix route passes through a router 3.1, the node identifier 10.1.3.1 of the router 3.1 is recorded in the abr_cluster_list of the route prefix, and the like. For the router 2.1, when the route prefix is received, if the abr_cluster_list exists in the route prefix and the node identifier of the node itself is included in the abr_cluster_list, the route prefix is discarded.

[0081] The above describes specific embodiments of the present application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in a different order and still accomplish desirable results. Additionally, the processes depicted in the figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In certain implementations, multitasking and parallel processing can be advantageous.

[0082] Figure 7 is a structural schematic diagram of an electronic device according to an embodiment of the present application. Please refer to Figure 7 At the hardware level, the electronic device includes a processor, and optionally further includes an internal bus, a network interface, and a memory. The memory can include a memory such as a high-speed random-access memory (RAM), and can further include a non-volatile memory such as at least one disk memory. Of course, the electronic device can further include other hardware required by a business.

[0083] The processor, the network interface, and the memory can be connected to each other through the 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. The bus can be divided into an address bus, a data bus, a control bus, etc. For the convenience of representation, Figure 7Only one bidirectional arrow is used to represent both directions, but this does not mean there is only one bus or only one type of bus.

[0084] The memory is configured to store a program. Specifically, the program can include program code including computer operation instructions. The memory can include an internal memory and a non-volatile memory, and provide instructions and data for the processor.

[0085] The processor reads the corresponding computer program from the non-volatile memory into the internal memory and then runs, and forms a route publishing device in a satellite network architecture at a logical level. The processor executes the program stored in the memory, and is specifically configured to perform the following operations: receive a route prefix of a third router node sent by a second router node; determine a target path according to target topology information, the target topology information including topology information of each router node in a first sub-domain to which the first router node and the second router node belong, the topology information of each router node in the first sub-domain being visible only to the router nodes in the first sub-domain, and the target path being used for the first router node to forward a packet carrying the route prefix.

[0086] The above as described in the present application Figure 7The method performed by the route publishing device in the satellite network architecture disclosed in the embodiment can be applied to a processor or implemented by the processor. The processor can be an integrated circuit chip with processing capability. In implementation process, each step of the above method can be completed by integrated logic circuit of hardware in the processor or by instructions in the form of software. 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, discrete hardware components. Each method, step and logic block diagram disclosed in the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the present application can be directly embodied as a hardware code processor for execution, or a combination of hardware and software modules in the code processor for execution. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method.

[0087] The electronic device can also perform the method of Figure 3 and realize the function of the route publishing device in the satellite network architecture in the embodiment, which will not be described herein. Figure 3

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

[0089] The present application also proposes a computer readable storage medium, which stores one or more programs, the one or more programs including instructions, which when executed by a portable electronic device including a plurality of application programs, can enable the portable electronic device to perform the method of the embodiment of Figure 3 and specifically perform the following operations: receiving a route prefix of the third router node sent by the second router node; ​determine a target path according to target topology information, the target topology information comprising topology information of each router node in a first sub-domain to which the first router node and the second router node belong, the topology information of each router node in the first sub-domain being visible only to the router nodes in the first sub-domain, the target path being used by the first router node to forward the packet carrying the route prefix.

[0090] Figure 8 is a structural schematic diagram of a route publishing device 80 in a satellite network architecture according to an embodiment of the present application. Please refer to Figure 8 In a software implementation, the route publishing device 80 in the satellite network architecture can comprise a receiving module 81 and a determining module 82, wherein: The receiving module 81 receives a route prefix of a third router node sent by a second router node. The determining module 82 determines a target path according to target topology information, the target topology information comprising topology information of each router node in a first sub-domain to which the first router node and the second router node belong, the topology information of each router node in the first sub-domain being visible only to the router nodes in the first sub-domain, the target path being used by the first router node to forward the packet carrying the route prefix.

[0091] The route publishing device 80 in the satellite network architecture provided by the present application can also execute the method in Figure 3 , and realize the functions of the route publishing device 80 in the satellite network architecture in Figure 3 the illustrated embodiment. The present application will not be repeated here.

[0092] The present application also provides a computer program product, which comprises a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to execute part or all of the steps in the above-mentioned route publishing method embodiments in the satellite network architecture.

[0093] In summary, the above only describes preferred embodiments of the present application and is not used to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

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

[0095] Computer readable media includes permanent and non-permanent, removable and non-removable media, which can be implemented by any method or technology to store information. The information can be computer readable instructions, data structures, program modules 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 technology, compact disc read only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible by a computing device. According to the definition herein, computer readable media does not include transitory media such as modulated data signals and carriers.

[0096] It should also be noted that the terms "comprising", "including", or any other variant thereof are intended to cover non-exclusive inclusion, so that processes, methods, articles or devices including a series of elements not only include those elements, but also include other elements not explicitly listed or inherent to such processes, methods, articles or devices. Without more limitations, the element defined by the statement "comprising a" does not exclude the presence of additional identical elements in the process, method, article or device including the element.

[0097] The various embodiments in the present application are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on the difference from other embodiments. In particular, the system embodiment is basically similar to the method embodiment, so the description is relatively simple, and the relevant parts can be referred to the part of the method embodiment.

Claims

1. A satellite network architecture comprising multiple subdomains, the multiple subdomains including a topology domain and a backbone domain, the topology domain including at least one router node in a satellite orbit, two adjacent topology domains being connected via the backbone domain, the backbone domain including Area Border Router (ABR) nodes in the two topology domains connected by the backbone domain, wherein for any first subdomain among the multiple subdomains, the topology information of each router node in the first subdomain is only visible to the router nodes in the first subdomain.

2. The architecture of claim 1, wherein the topology domain and the adjacent backbone domain satisfy one of the following: The topology domain and the backbone domain are configured with the same Border Gateway Protocol (BGP) address family on a shared first ABR node. The first ABR node includes a first BGP neighbor type, which is used to control the route advertising of the first ABR node according to preset route advertising rules to achieve isolation between the topology domain and the backbone domain. The topology domain and the backbone domain are configured with different BGP instances on the first ABR node. The routing prefixes of each router node in the topology domain and the routing prefixes of each router node in the backbone domain are mutually transmitted between the different BGP instances through redistribution. The advertising source of the mutually transmitted routing prefixes is modified to the first ABR node. The topology domain and the backbone domain are configured with different BGP address families on the first ABR node. The routing prefixes of each router node in the topology domain and the routing prefixes of each router node in the backbone domain are mutually redirected through redistribution between the different BGP address families. The advertising source of the redirected routing prefixes is modified to the first ABR node.

3. The architecture as described in claim 2, wherein the routing publication rules include: It is not permitted to send the topology information of each router node in the topology domain where the first ABR node is located to the router nodes in the backbone domain. The node information of the first ABR node and the connection relationship between the first ABR node and its neighboring ABR nodes are allowed to be published on the neighboring ABR nodes to construct the backbone domain; Allow the redistribution of the routing prefixes of each router node within the topology domain where the first ABR node is located to the backbone domain where the first ABR node is located, and modify the publishing source to the first ABR node; It is not permitted to publish the topology information of each router node in the backbone domain where the first ABR node is located to the router nodes in the topology domain. It allows the redistribution of the routing prefixes of each router node within the backbone domain where the first ABR node is located to the topology domain where the first ABR node is located, and modifies the publishing source to the first ABR node.

4. A route publishing method in a satellite network architecture, the satellite network architecture including multiple subdomains, the multiple subdomains including topology domains and backbone domains, the topology domain including at least one router node in a satellite orbit, two adjacent topology domains being connected through the backbone domain, the backbone domain including Area Border Router (ABR) nodes in the two topology domains connected by the backbone domain; The method is applied to any first router node in the plurality of domains, including: Receive the routing prefix of the third router node sent by the second router node; The target path is determined based on the target topology information, which includes the topology information of each router node in the first subdomain to which the first router node and the second router node belong. The topology information of each router node in the first subdomain is only visible to the router nodes in the first subdomain. The target path is used by the first router node to forward packets carrying the routing prefix.

5. The method as described in claim 4, wherein the topology information of each router node in the first subdomain includes the node information of each router node in the first subdomain and the connection relationship between each router node in the first subdomain.

6. The method of claim 4, wherein when the first router node is an ABR node, for the first topology domain to which the first router node belongs and the first backbone domain to which the first router node belongs, the method further includes one of the following: The first router node is configured with the same BGP address family for the first topology domain and the first backbone domain. The first router node includes a first BGP neighbor type. The first BGP neighbor type is used to control the route advertising of the first router node according to the preset route advertising rules to achieve isolation between the first topology domain and the first backbone domain. On the first router node, different BGP instances are configured for the first topology domain and the first backbone domain. The routing prefixes of each router node in the first topology domain and the routing prefixes of each router node in the first backbone domain are mutually transmitted between the different BGP instances through redistribution. The advertising source of the mutually transmitted routing prefixes is modified to the first router node. On the first router node, different BGP address families are configured for the first topology domain and the first backbone domain. The routing prefixes of each router node in the first topology domain and the routing prefixes of each router node in the first backbone domain are mutually redirected through redistribution between the different BGP address families. The advertising source of the redirected routing prefixes is modified to the first router node.

7. The method of claim 6, wherein the route publishing rules include: Topology information of each router node in the first topology domain is not allowed to be sent to router nodes in the first backbone domain. The node information of the first router node and the connection relationship between the first router node and the neighboring ABR node are allowed to be published on the neighboring ABR node to construct the first backbone domain. Allow the redistribution of the routing prefixes of each router node within the first topology domain to the first backbone domain, and modify the publishing source to the first router node; The topology information of each router node in the first backbone domain is not allowed to be published to the router nodes in the first topology domain. Allow the redistribution of the routing prefixes of each router node in the first backbone domain to the first topology domain, and modify the publishing source to the first router node.

8. The method of any one of claims 4 to 7, wherein the first domain is a topological domain, the method comprising: When the third router node is located within the first domain, the target path is the path between the first router node and the third router node; When the third router node is located in a domain other than the first domain and the second router node is an internal node in the first domain, the target path is the path between the first router node and the ABR node in the first domain that receives the routing prefix, and the internal node is the other router node in the first domain besides the ABR node. When the third router node is located in a domain other than the first domain and the second router node is an ABR node in the first domain, the target path is the path between the first router node and the second router node.

9. The method of any one of claims 4 to 7, wherein the first subdomain is a backbone domain, the method comprising: The target path is the path from the first router node to the second router node.

10. The method of claim 4, wherein after determining the target path based on the target topology information, the method further includes: When the first router node is an ABR node, the routing prefix is ​​sent to other router nodes within the first subdomain, or the routing prefix is ​​redistributed to the second subdomain where the first router node is located, and the advertising source of the routing prefix is ​​modified to the first router node, wherein the second subdomain is another subdomain outside the first subdomain; When the first subdomain is the topology domain and the first router node is an internal node, the routing prefix is ​​sent to other router nodes within the first subdomain, where the internal nodes are other router nodes within the first subdomain besides the ABR node.

11. The method of claim 4, wherein the routing prefix includes extended information, and the extended information records the identification information of the ABR nodes traversed by the routing prefix; after receiving the routing prefix of the third router node sent by 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.

12. The method as described in claim 11, 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.

13. The method of claim 4, 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.

14. 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 4 to 13.

15. 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 4 to 13.

16. 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 4 to 13.

Images