Constellation Network Fusion Method Based on Multi-Constellation Interconnected Distributed Routing Architecture

Abstract

This invention belongs to the field of constellation routing calculation technology, specifically disclosing a constellation network fusion method based on a multi-constellation interconnected distributed routing architecture. The entire routing architecture is divided into a satellite core autonomous system, a satellite access autonomous system, and a satellite user autonomous system. Gateways advertise terrestrial network routing prefix information to connected satellites, and network satellite terminals advertise the address prefixes of their connected user subnets to connected satellites. Satellites advertise routing prefixes to other satellites via internal boundary gateway protocols. When at least two satellites in the satellite core autonomous system are connected to different gateways within the same satellite access autonomous system on the ground, other satellites determine the next hop to reach the satellite access autonomous system based on the internal gateway protocol metric used to reach that satellite, improving the compatibility of satellite constellation network fusion at different construction stages.

Description

Technical Field

[0001] This invention relates to a constellation network fusion method based on a multi-constellation interconnected distributed routing architecture, belonging to the field of constellation routing calculation technology. Background Technology

[0002] The integrated space-ground information network is the core infrastructure for future information acquisition, distribution, transmission, and application, and various constellation networks are important components in building this space-based system. How to integrate these networks and achieve efficient interconnection is a key issue that needs to be addressed in constructing an integrated space-ground network. Among the challenges, designing a routing architecture for network-layer convergence is the first technical hurdle to overcome. On the one hand, because various networks are highly heterogeneous, they differ significantly in transmission technologies, programming strategies, routing protocols, and network management, making it difficult to achieve network convergence using a unified routing architecture. On the other hand, in the long-term process of building the integrated space-ground network, different networks are at different stages of construction, especially with significant differences in the deployment and configuration of different constellation networks, posing another challenge to the routing architecture design.

[0003] The existing work on the integration of space-ground networks at the network layer mainly treats satellite networks as different Autonomous Systems (AS) and uses inter-domain routing to integrate the two networks. The main work currently involved includes: (1) In terms of routing protocol design: a satellite version of the Border Gateway Protocol, namely the BGP-S protocol, has been proposed. This protocol is an improvement on the BGP v4 protocol and can interoperate with it. BGP-S can realize automatic path discovery through the satellite network and achieves lower latency than BGP-4 in the space-ground integrated network. In addition, there are also literature that proposes the Hub & Spoke BGP protocol, which takes into account the limited bandwidth of the satellite-ground link and uses the broadcast characteristics of the wireless network to transmit BGP messages, reducing bandwidth occupation. (2) In terms of routing architecture design: some studies have proposed a method for providing connectivity using the BGP backbone network in the context of mobile air node interconnection for specific network scenarios. In these scenarios, BGP can be deployed in the satellite network, and each mobile network is an independent AS domain, interconnected with each other through BGP. There are also studies that analyze different ways of deploying BGP in DVB-S2 / RCS networks. Regarding the routing architecture of the TSAT system, some studies have proposed that policy-based routing filtering methods can be used to support special connection scenarios, such as VPNs. (3) In terms of the routing performance of BGP-based satellite networks, there are also some discussions involving routing performance, stability, and overhead.

[0004] The above work divides satellite networks into different routing domains and only provides a preliminary solution for network interconnection via the BGP protocol. There are still specific issues related to routing architecture design that have not been discussed, especially considering the characteristics of existing constellation networks at different deployment stages, there are still many problems that need to be solved. Summary of the Invention

[0005] The purpose of this invention is to overcome the shortcomings of the prior art and provide a constellation network fusion method based on a multi-constellation interconnected distributed routing architecture, thereby improving the compatibility of fusion of satellite constellation networks at different construction stages.

[0006] To achieve the above objectives, the present invention is implemented using the following technical solution:

[0007] This invention provides a constellation network fusion method based on a multi-constellation interconnected distributed routing architecture, comprising the following steps:

[0008] Based on the satellites and their connected user terminals, the multi-constellation interconnection routing architecture is divided into a satellite core autonomous system, a satellite access autonomous system, and a satellite user autonomous system. The satellite core autonomous system includes all satellites and user terminals directly connected to the satellites. The satellite access autonomous system includes gateways and terrestrial networks connected to the gateways. The satellite user autonomous system includes network satellite terminals and user subnets connected to the network satellite terminals. Routing policies are configured on the boundary routers of the satellites, gateways, or user subnets.

[0009] The gateway announces the terrestrial network routing prefix information to the connected satellites;

[0010] The network satellite terminal announces the address prefix of the user subnet it is connected to to the connected satellite;

[0011] All of the aforementioned satellites advertise the learned routing prefixes to other satellites via the Internal Border Gateway Protocol;

[0012] When at least two satellites in the satellite core autonomous system are respectively connected to different gateways within the same satellite access autonomous system on the ground, other satellites determine the next hop to reach the satellite access autonomous system based on the internal gateway protocol metric of reaching these two satellites.

[0013] Furthermore, the routing prefixes exchanged in the satellite core autonomous system include the address prefixes advertised by the gateway through the external border gateway protocol, and the address prefixes of the user subnets to which the network satellite terminals connected to the satellite are connected.

[0014] Furthermore, the method includes setting up a network control center, which allocates address space according to the number of satellite terminals in the coverage area of ​​each satellite and distributes it to the regional control center, which then configures the address space to the onboard DHCP server.

[0015] Furthermore, in the satellite core autonomous system, satellite networks operate an internal gateway protocol via inter-satellite links and establish routing peer-to-peer relationships through an internal border gateway protocol, exchanging routing prefixes.

[0016] Furthermore, there are no inter-satellite links between satellite networks in the satellite core autonomous system, or the satellite networks use different underlying communication systems. The satellite networks are divided into different satellite core autonomous systems, and their routing prefixes are exchanged through gateways on the ground.

[0017] Furthermore, the gateway runs the External Border Gateway Protocol (EBGP) and the Terrestrial Network Standard Routing Protocol (TBR) at its satellite network interface and terrestrial network interface, respectively. The gateway announces the converged address prefix of the terrestrial network to the satellite core autonomous system through the EBGP, and at the same time receives address prefix information from the satellite.

[0018] Furthermore, the network satellite terminal exchanges intra-domain reachability information with the satellite through an external boundary gateway protocol and connects to the terrestrial network through a terrestrial network standard routing protocol.

[0019] Furthermore, the routing strategy includes:

[0020] When a satellite is connected to multiple gateways or network satellite terminals, the service traffic that is aggregated at the satellite and needs to be transmitted to the ground selects different gateways or network satellite terminals based on the capacity and bandwidth usage of the feeder links connecting the gateways or network satellite terminals.

[0021] When a gateway or network satellite terminal is connected to multiple satellites, the service traffic that is aggregated at the gateway or network satellite terminal and needs to be transmitted to the satellite can be selected from different satellites based on the capacity and bandwidth usage of the feeder link connecting the gateway or network satellite terminal.

[0022] Compared with the prior art, the beneficial effects achieved by the present invention are as follows:

[0023] A constellation network fusion method based on a multi-constellation interconnected distributed routing architecture is proposed. This method constructs an integrated routing framework, realizes the fusion of space-ground integrated networks at the network layer, and provides optimal path selection, segmentation of management and control boundaries, and reduction of management complexity.

[0024] The architecture design method provided by this invention is compatible with existing routing mechanisms, supports efficient and flexible networking capabilities, supports on-demand establishment of VPNs with different topologies, and provides flexible and diverse routing strategies.

[0025] The routing architecture supports interoperability with standard routing protocols and provides sufficient scalability to support large networks by employing a distributed routing strategy. Attached Figure Description

[0026] Figure 1 This is a schematic diagram illustrating an application scenario of the multi-constellation interconnected distributed routing architecture provided in this embodiment of the invention;

[0027] Figure 2 This is a schematic diagram of the multi-constellation interconnected distributed routing architecture provided in an embodiment of the present invention;

[0028] Figure 3 This is a schematic diagram of the routing protocol running in the multi-constellation interconnected distributed routing architecture provided in the embodiments of the present invention. Detailed Implementation

[0029] The present invention will be further described below with reference to the accompanying drawings. The following embodiments are only used to more clearly illustrate the technical solution of the present invention, and should not be used to limit the scope of protection of the present invention.

[0030] This invention provides a constellation network fusion method based on a multi-constellation interconnected distributed routing architecture. The multi-constellation interconnected routing architecture is divided into a satellite core autonomous system, a satellite access autonomous system, and a satellite user autonomous system based on the satellites and their connected user terminals. The satellite core autonomous system includes all satellites and user terminals directly connected to the satellites. The satellite access autonomous system includes gateways and terrestrial networks connected to the gateways. The satellite user autonomous system includes network satellite terminals and user subnets connected to the network satellite terminals. Routing policies are configured on the boundary routers of the satellites, gateways, or user subnets.

[0031] The gateway advertises the terrestrial network routing prefix information to the connected satellites, the network satellite terminal advertises the address prefix of the connected user subnet to the connected satellites, and all satellites advertise the learned routing prefixes to other satellites through the internal border gateway protocol.

[0032] When at least two satellites in the satellite core autonomous system are respectively connected to different gateways within the same satellite access autonomous system on the ground, other satellites determine the next hop to reach the satellite access autonomous system based on the internal gateway protocol metric of reaching these two satellites.

[0033] Example 1

[0034] This invention provides a constellation network fusion method based on a multi-constellation interconnected distributed routing architecture. The applied network scenario involves multiple satellite networks deployed at different times for different purposes. For example, some satellite networks primarily support narrowband services, such as voice and low-speed data services; others may support broadband services, such as audio and video.

[0035] like Figure 1 The diagram shown illustrates an application scenario of the multi-constellation interconnected distributed routing architecture provided in this embodiment of the invention. This embodiment is mainly for geostationary orbit satellite networks, but is also applicable to other types of satellite networks.

[0036] The following terms are used in this scenario:

[0037] UST: User Satellite Terminal, an earth station that accesses the satellite network via a user link between a satellite and the ground;

[0038] NST: Network Satellite Terminal, an earth station that accesses the satellite network through a user link between the satellite and the ground, and connects to some ground user subnets;

[0039] GW: Satellite Gateway, an earth station that connects to the satellite network via a feeder link between the satellite and the ground, and also connects to some ground-based autonomous system routing systems;

[0040] ISL: Inter-satellite link, a wireless or laser link connecting satellites;

[0041] GSL: Satellite-to-Ground Link, a wireless link connecting earth stations and satellites;

[0042] And SN: Satellite Network, GEO: Geostationary Orbit Satellite, NCC: Network Control Center, ACC: Regional Control Center, AS: Autonomous System, IGP: Interior Gateway Protocol, EGP: Exterior Gateway Protocol, BGP: Border Gateway Protocol, iBGP: Internal Border Gateway Protocol, eBGP: External Border Gateway Protocol, NAT: Network Address Translation, DHCP: Dynamic Host Configuration Protocol.

[0043] The satellite networks in this scenario differ in several ways: each network comprises a different number of GEO satellites covering a specific area. For example, SN2 and SN3 each have four satellites, while SN1 has three. The satellites in these networks vary in their transmission, processing, and storage capabilities, and they can be interconnected via ISLs.

[0044] There are different types of satellite terminals on the ground, including USTs, NSTs, and GWs. NSTs and GWs have routing capabilities, while USTs do not. With the development of integrated space-ground networks, ISLs can be deployed between different satellite networks, or ground links may be added between satellite terminals in different satellite networks, thereby achieving different levels of interconnection at different deployment stages.

[0045] Regarding the management and control relationships in the routing architecture, a control center (NCC) is set up throughout the network, and an area control center (ACC) is set up at a gateway within the satellite coverage area. A gateway (GW) can see multiple satellites simultaneously, and a satellite may also establish communication links with multiple gateways (GWs). The system can select different gateways (GWs) for services aggregated on a single satellite to land, based on the power supply link capacity and bandwidth usage of the gateways (GWs), and can also select different gateways (GWs) for ground users to upload to the satellite.

[0046] ACC is responsible for the management of satellite terminals within the corresponding satellite coverage area, the collection of link and traffic status, and the configuration of routing policies.

[0047] Figure 2 This is a schematic diagram of the multi-constellation interconnected distributed routing architecture provided in this embodiment. This routing architecture constructs a multi-AS distributed routing system with routing policy control capabilities and strong routing scalability.

[0048] All GEO satellites and their connected user terminals can be configured as an independent core AS. The routing architecture in this embodiment includes three types of ASs: satellite core AS, satellite access AS, and satellite user AS. It is assumed that during the development of the satellite network, ISLs are deployed between the satellites of two SNs, such as... Figure 2 If the ISL A is true, then the two SNs can be merged into a single satellite core AS. For GWs, such as... Figure 2 GW1, GW2, and GW3 in the network connect to the satellite network of the terrestrial network. The terrestrial network and the connected GWs can be configured as a satellite access AS. All user subnets connected to NSTs can be configured together with the NSTs as a satellite user AS. Therefore, the satellites, GWs, and USTs in the network are all routing nodes.

[0049] In this routing architecture, routing protocols such as IGP and EGP are deployed in different locations within the network, as detailed below:

[0050] Within a satellite core AS, satellites operate IGPs, such as OSPF, via ISLs. When needed, satellites can establish routing peering relationships via the iBGP routing protocol within the satellite core AS. This means satellites can exchange routing prefixes learned from other ASs, and the fully connected paths between them are provided by the IGP routing protocol. However, the core IGP protocol does not participate in the prefix redistribution of other routing protocols.

[0051] eBGP runs between satellites and GWs or NSTs, with GWs or NSTs acting as border routers to exchange inter-domain routing prefixes. The routing prefixes exchanged between core routers in the core AS via iBGP include the address prefixes advertised from the GWs via eBGP, as well as the address prefixes of the subnets connected to the NSTs linked by the satellite. Therefore, all satellites in the satellite core ASs need to run eBGP, iBGP, and IGP protocols simultaneously.

[0052] When there are no ISLs between SNs, or when two SNs are connected by ISLs but use different underlying communication systems and cannot achieve network layer connectivity, routing information can still be exchanged between the satellites of the two SNs. In this case, the two SNs need to be assigned to different core ASs, and the routing prefixes are exchanged through GWs on the ground.

[0053] GWs run eBGP and terrestrial standard routing protocols at their satellite network interface and terrestrial network interface, respectively. As a border router, GWs advertises the aggregated address prefix of the terrestrial network to the core AS via eBGP, while also receiving address prefix information from the satellite.

[0054] NSTs run eBGP and terrestrial standard routing protocols at their satellite network interface and terrestrial network interface, respectively. NSTs exchange intra-domain reachability information with satellites via BGP and connect to terrestrial networks via terrestrial standard routing protocols.

[0055] The decision-making process for inter-domain routing using BGP can be determined based on the IGP metric to the next hop. When two GEO satellites in a satellite core autonomous system are connected to different GWs in the same ground-based AS, the two GWs can advertise routing prefix information to these satellites, which then advertise the routing prefixes to other satellites via iBGP. Other satellites determine the next hop to the AS based on the IGP metric to reach these two satellites. If the metrics are the same, the GW with the smallest ID is selected. The traffic load from these two satellites can be load-balanced through the two connected GWs using the multipath option of the eBGP protocol configured on the satellite.

[0056] Regarding address allocation, different subnets are naturally formed based on the coverage areas of different satellite beams, each configured with an independent address space. The NCC allocates address space according to the number of satellite terminals in the coverage area of ​​each satellite, and distributes it to the ACC for address pool management. The ACC configures the address pool to the onboard DHCP service, and the onboard module assigns addresses corresponding to the access beams of the satellite terminals through the DHCP service. When a user terminal directly connects to a satellite terminal, including USTs or NSTs, its address is configured as a private address, and the satellite terminal accesses the satellite through NAT.

[0057] Routing policies can be configured on the border routers of satellites, GWs, or user subnets. Load balancing is achieved through routing policy configuration as follows: when a satellite is connected to multiple GWs, the traffic aggregated at the satellite and required to be transmitted to the ground can be selected from different GWs based on the capacity and bandwidth usage of the feeder links connecting the GWs; when a GW is connected to multiple satellites, the traffic aggregated at the GW and required to be transmitted to the satellites can be selected from different satellites based on the capacity and bandwidth usage of the feeder links connecting the GWs.

[0058] Figure 3 This diagram illustrates the routing protocols operating in the multi-constellation interconnected distributed routing architecture provided in this embodiment. N satellites are connected one after the other to form a ring. They reside within a satellite core AS and run IGP protocols such as OSPF or custom routing protocols compatible with standard protocols. The IGP protocols in the core AS are only deployed on the satellites and do not participate in the route redistribution of other routing protocols.

[0059] The iBGP protocol runs in the satellite core AS and enables full connectivity between satellite nodes; the eBGP protocol is deployed between GWs and satellites to exchange aggregation route prefixes that may be filtered; at the same time, eBGP is also deployed and runs between NSTs in the satellite coverage area and satellites, thus preventing any routing state updates in the terrestrial user network from entering the satellite core AS, reducing the burden of onboard processing and storage.

[0060] NSTs and GWs interface with user subnets and terrestrial networks using a standard IGP, thereby achieving interconnection. Path selection for messages from the source satellite terminal to the destination satellite terminal is achieved through routing tables in the satellite terminal and onboard modules. The routing process is transparent to the user, and no additional processing is required by the terrestrial network.

[0061] Specifically, in terms of path selection, the decision-making process of inter-domain routing BGP can be determined based on the IGP metric to the next hop. For example, GEO satellites 3 and 4 in the satellite core autonomous system are connected to different satellite gateways of the same autonomous system on the ground, as shown in GW3 and GW4 in the diagram. The two GWs can advertise route prefix information to these two satellites, and then the satellites advertise the route prefix to other satellites via iBGP. Other satellites select GW3 or GW4 as the next hop to the AS to which GW3 and GW4 belong based on the IGP metric to reach satellites 3 and 4. If the metrics are the same, the GW with the smallest ID is selected. Moreover, the traffic load from these satellites can be load-balanced through these two GWs via the multipath option of the eBGP protocol configured on satellites 3 and 4. Similarly, these satellite gateway GWs can determine which satellite to forward data through based on the IGP metric, ensuring optimal routing.

[0062] Satellite networks exhibit significant differences in constellation configuration, satellite capacity, technical mechanisms, service types, and application requirements. To integrate these satellite networks deployed at different stages, the integrated space-ground network needs to be compatible with existing networks. To address this issue, this invention provides a constellation network fusion method based on a multi-constellation interconnected distributed routing architecture. This method achieves the integration of the space-ground network at the network layer, providing optimal path selection and flexible management capabilities. Specific advantages are as follows:

[0063] In terms of management and control, the architecture design method provided by this invention offers a clear method for delineating management and control boundaries, with eBGP sessions running between the satellite core AS and other ASs. Each AS can easily manage its own network, and satellites within the satellite core AS can be managed by independent administrators. Essentially, the satellite core AS is a service-providing entity for other networks. Furthermore, the boundaries of BGP ASs and IGP processes are consistent; IGP processes within other ASs do not extend to the satellite core AS, and IGP processes within the satellite core AS do not extend to the border routers of other ASs. There are no shared resources between the satellite core AS and other ASs, thus allowing for a clear separation of their management mechanisms.

[0064] Regarding routing strategies, the clear boundaries between the satellite core AS and other ASs allow routing strategies to be deployed at the boundaries of each AS. For example, flow control can be implemented between different user networks. Furthermore, each satellite core AS can have its own set of routing prefixes, which can be aggregated before being injected into BGP. AS-based prefix filtering lists can also be used to block route prefix advertisements, rather than relying on access control lists for packet filtering, thus reducing management complexity.

[0065] In summary, this invention can meet the compatibility and flexibility requirements of integrated air-ground networks: the routing architecture is compatible with existing routing mechanisms and supports efficient and flexible networking capabilities, as well as on-demand establishment of VPNs with different topologies, providing flexible and diverse routing strategies; and the interconnection requirements, the routing architecture supports interoperability with standard routing protocols such as RIP and OSPF, and provides sufficient scalability by adopting distributed routing strategies to facilitate support for large-scale networks.

[0066] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0067] This application is described with reference to flowchart illustrations and / or block diagrams of methods, systems, and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0068] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0069] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0070] The scope of protection of this invention is obviously not limited to these specific embodiments. Without departing from the principles of this invention, those skilled in the art can make equivalent changes or substitutions to the relevant technical features, and the technical solutions resulting from these changes or substitutions will all fall within the scope of protection of this invention.

Claims

1. A constellation network fusion method based on a multi-constellation interconnected distributed routing architecture, characterized in that, Includes the following steps: The multi-constellation interconnection routing architecture is divided into a satellite core autonomous system, a satellite access autonomous system, and a satellite user autonomous system based on the satellites and the user terminals they are connected to. The satellite core autonomous system includes all satellites and user terminals directly connected to the satellites. Satellites operate an internal gateway protocol via inter-satellite links and establish routing peer-to-peer relationships via an internal border gateway protocol. The satellite access autonomous system includes a gateway and a terrestrial network connected to the gateway; the gateway runs an external border gateway protocol on its satellite network interface and a standard routing protocol on its terrestrial network interface. The satellite user autonomous system includes a network satellite terminal and a user subnet connected to the network satellite terminal; routing policies are configured on the boundary routers of the satellite, gateway, or user subnet; The gateway announces the terrestrial network routing prefix information to the connected satellites; The network satellite terminal announces the address prefix of the user subnet it is connected to to the connected satellite; All satellites advertise the learned route prefixes to other satellites via the Internal Border Gateway Protocol; When at least two satellites in the satellite core autonomous system are respectively connected to different gateways in the same satellite access autonomous system on the ground, other satellites determine the next hop to reach the satellite access autonomous system based on the internal gateway protocol metric of the two satellites, and select a gateway or satellite based on the capacity and bandwidth usage of the power supply link.

2. The constellation network fusion method based on a multi-constellation interconnected distributed routing architecture according to claim 1, characterized in that, The routing prefixes exchanged in the satellite core autonomous system include the address prefixes advertised by the gateway through the external border gateway protocol, and the address prefixes of the user subnets to which the satellite terminals of the satellite-connected network are connected.

3. The constellation network fusion method based on a multi-constellation interconnected distributed routing architecture according to claim 1, characterized in that, The method includes setting up a network control center, which allocates address space according to the number of satellite terminals in the coverage area of ​​each satellite and distributes it to the regional control center, which then configures the address space to the on-board DHCP server.

4. The constellation network fusion method based on a multi-constellation interconnected distributed routing architecture according to claim 1, characterized in that, In the satellite core autonomous system, satellite networks operate internal gateway protocols via inter-satellite links and establish routing peer relationships through internal border gateway protocols, exchanging routing prefixes.

5. The constellation network fusion method based on a multi-constellation interconnected distributed routing architecture according to claim 1, characterized in that, The satellite networks in the satellite core autonomous system do not have inter-satellite links, or the satellite networks use different underlying communication systems. The satellite networks are divided into different satellite core autonomous systems, and their routing prefixes are exchanged through gateways on the ground.

6. The constellation network fusion method based on a multi-constellation interconnected distributed routing architecture according to claim 1, characterized in that, The gateway announces the converged address prefix of the terrestrial network to the satellite core autonomous system through the external boundary gateway protocol, and simultaneously receives address prefix information from the satellite.

7. The constellation network fusion method based on a multi-constellation interconnected distributed routing architecture according to claim 1, characterized in that, The network satellite terminal exchanges intra-domain reachability information with the satellite via an external boundary gateway protocol and connects to the terrestrial network via a standard terrestrial network routing protocol.

8. The constellation network fusion method based on a multi-constellation interconnected distributed routing architecture according to claim 1, characterized in that, The routing strategy includes: When a satellite is connected to multiple gateways or network satellite terminals, the service traffic that is aggregated at the satellite and needs to be transmitted to the ground selects different gateways or network satellite terminals based on the capacity and bandwidth usage of the feeder links connecting the gateways or network satellite terminals. When a gateway or network satellite terminal is connected to multiple satellites, the service traffic that is aggregated at the gateway or network satellite terminal and needs to be transmitted to the satellite can be selected from different satellites based on the capacity and bandwidth usage of the feeder link connecting the gateway or network satellite terminal.

Images