CN117955545A - Dynamic release method and device for high-flux satellite system substation route - Google Patents

Abstract

The invention provides a method and a device for dynamically publishing a high-flux satellite system substation route, wherein the method is applied to a data gateway XGW and comprises the following steps: traversing all satellite virtual networks SVNs, and judging whether the satellite virtual networks SVNs support dynamic route release or not; for the satellite virtual network SVN supporting dynamic route release, a starting thread establishes BGP protocol connection with an opposite-end router; when a satellite terminal accesses or leaves a satellite access network through a dispatcher DDM, a BGP message for constructing route update is sent to the opposite-end router; the routing information in the BGP message of the routing update includes a routing IP address and a next-hop IP address, where the routing IP address is an IP address of the satellite terminal, and the next-hop IP address is an IP address of the satellite virtual network SVN.

Description

Dynamic release method and device for high-flux satellite system substation route

Technical Field

The invention belongs to the technical field of high-flux satellite communication, and particularly relates to a method and a device for dynamically publishing a small station route of a high-flux satellite system.

Background

In high throughput satellite systems, routing configuration issues need to be considered in the network topology because the small stations need to switch frequently between multiple satellite access stations.

In particular, when a small station is fixedly accessing a certain satellite access station, static routing can be configured on the router to which the station is connected, at which point the IP data packets can be forwarded correctly to the satellite data gateway. In practice, however, if a small station is connected to another satellite access station, the router to which the satellite access station is connected may not have corresponding routing information, and thus the IP packet will not be forwarded to the satellite data gateway correctly.

As shown in fig. 1, if the small station is fixedly connected to SAS1 (SAS, satellite access station), a static route is configured on R1 to correctly forward the IP packet to XGW1 (XGW, satellite data gateway).

But access SAS2 when the small station moves to the beam to which SAS2 belongs. In this case, in order to correctly forward the IP packet, the same static route needs to be configured in R2. At the same time, the static route of the small station on R1 needs to be deleted, otherwise, the R3 router connected with R1 and R2 does not know how to forward. In a high-throughput satellite system, a network is divided into a plurality of Satellite Virtual Networks (SVNs) according to VLAN IDs, so that the expandability and flexibility of the network can be effectively improved. However, there are tens of hundreds of small stations under each SVN, and manually maintaining their static routes requires cumbersome operations and is too costly.

Especially in the case of a small station switching between multiple satellite access stations, the static routing approach may lead to untimely updating of the small station routing information.

In addition, in a complex network environment, manually adding routing information for a small station to access each satellite access station is prone to route information collisions and duplication, thereby causing network failure.

Disclosure of Invention

In view of this, the present invention provides a method for dynamically publishing a high-throughput satellite system substation route, which is applied to a data gateway XGW, and includes:

Step 1, traversing all satellite virtual networks SVNs, and judging whether the satellite virtual networks SVNs support dynamic route release or not;

Step 2, for the satellite virtual network SVN supporting dynamic route release, a starting thread establishes BGP protocol connection with an opposite-end router;

Step 3, when a satellite terminal accesses or leaves a satellite access network through a dispatcher DDM, constructing a BGP message for route update and sending the BGP message to the opposite-end router; the routing information in the BGP message of the routing update includes a routing IP address and a next-hop IP address, where the routing IP address is an IP address of the satellite terminal, and the next-hop IP address is an IP address of the satellite virtual network SVN.

In particular, in the step 1, the step of determining whether the satellite virtual network SVN supports dynamic route distribution includes any one of the following methods:

whether dynamic route release is supported is explicitly marked in the configuration information of the satellite virtual network SVN, and the configuration item is read to judge;

Receiving registration information of the satellite virtual network SVN at the starting time, wherein the registration information comprises a mark for supporting dynamic route release or not, and storing the registration information of the satellite virtual network SVN;

Sending an inquiry request to the satellite virtual network SVN, and determining whether the satellite virtual network SVN supports dynamic route release according to the reply information of the satellite virtual network SVN to the request;

Maintaining a database, recording the SVN function characteristics of each satellite virtual network, wherein the database can be configured by network management personnel or uploaded by the SVN during registration; XGW loading the database to obtain the information of each satellite virtual network SVN when starting;

The satellite virtual network SVN supporting dynamic route release is configured in one group, and when the system is started, the two satellite virtual network SVN groups are distinguished when the system is not supported in the other group.

In particular, the step 2 of starting the thread to establish BGP connection with the correspondent router includes: configuring an IP address of a tap interface as a local endpoint of a BGP protocol, starting the tap interface, introducing external traffic into a protocol stack for processing, configuring parameters for the BGP protocol, constructing BGP Open information and sending the BGP Open information to the router; and waiting and processing BGP Open information returned by the router, completing three-way handshake and establishing TCP connection.

In particular, the step3 includes: when a satellite terminal accesses a satellite access network through a dispatcher DDM, a message for constructing route update is a BGP message of a newly added route message.

In particular, the step3 includes: when the satellite terminal leaves the satellite access network through the dispatcher DDM, constructing a route update message as a BGP message for deleting the route message.

In particular, the step 3 further includes: and maintaining the session state of the BGP protocol between the opposite-end routers, and if the configuration of the satellite virtual network SVN is detected to change or the BGP protocol connection is restarted, establishing connection with the opposite-end routers again for the routing information of the satellite terminal which is already connected with the network, and retransmitting the BGP message of the routing update.

In particular, the step 3 further includes: loading the connection state data of the satellite terminal from a Redis database after the system is started; checking whether each loaded satellite terminal is on line or not currently; and inquiring a Redis database to acquire the routing information of the satellite terminal which is still on-line, constructing a BGP message of routing update, and sending the BGP message to the opposite-end router.

In particular, the method further comprises sending the message in a DPDK mode through a tap interface according to the updated BGP message.

The invention also provides a device for dynamically publishing the high-flux satellite system substation route, which is applied to the data gateway XGW and comprises the following components:

The dynamic routing capability detection module is used for traversing all the satellite virtual networks SVNs and judging whether the satellite virtual networks SVNs support dynamic routing release or not;

The BGP protocol connection module is used for establishing BGP protocol connection between a starting thread and an opposite-end router for the satellite virtual network SVN supporting dynamic route release;

The route updating module is used for constructing a BGP message for route updating and sending the BGP message to the opposite-end router when the satellite terminal accesses or leaves the satellite access network through the dispatcher DDM; the routing information in the BGP message of the routing update includes a routing IP address and a next-hop IP address, where the routing IP address is an IP address of the satellite terminal, and the next-hop IP address is an IP address of the satellite virtual network SVN.

The beneficial effects are that:

1. the invention realizes the automatic management of the small station route and reduces the manual operation cost; the dynamic route update improves the real-time performance of the route information and avoids the delay of manual configuration.

2. The invention reduces network faults caused by route error configuration and improves system stability.

3. By the scheme of the invention, the seamless switching of the small station among a plurality of stations is supported, the service continuity is ensured, the route management is simplified, and the operation burden of a network manager is reduced.

4. The invention is convenient for optimizing route according to service.

5. According to the invention, the dynamic release route meets the requirements of a large-scale network and frequent scene change, the automatic synchronization of the route information of different sites is realized, and the interoperability and compatibility between routers are improved.

Drawings

FIG. 1 is a schematic diagram of a prior art maintenance of a satellite network topology through static routing;

FIG. 2 is a schematic diagram of maintaining a satellite network topology through dynamic routing in accordance with the present invention;

Fig. 3 is a schematic structural diagram of a high-throughput satellite system substation route dynamic issuing device in the present invention.

Detailed Description

The invention will now be described in detail by way of example with reference to the accompanying drawings.

The invention provides a dynamic release method of a high-flux satellite system substation route, which is applied to a data gateway XGW, wherein the system architecture and the method flow diagram are shown in figure 2, and the functions of each module in the system are as follows: sas: satellite access stations including line cards, DDM, XGW, route, etc.; xgw: the data gateway is a distribution processing unit of the DDM and the user side network equipment; ddm: the method is responsible for the functions of access control, data scheduling and the like of a single SATNET satellite terminal; 4. the small station: a satellite terminal. The method comprises the following steps:

Step 1, traversing all the satellite virtual networks SVNs, and judging whether the satellite virtual networks SVNs support dynamic route release. In this step, the specific method for determining whether the satellite virtual network SVN supports dynamic route distribution by the data gateway XGW may be as follows:

whether dynamic route release is supported is explicitly identified in the configuration information of the satellite virtual network SVN, and the data gateway XGW reads the configuration item to determine.

The satellite virtual network SVN registers its own supported functions with the data gateway XGW at start-up, including a flag as to whether dynamic route distribution is supported. Data gateway XGW stores the functional information of each satellite virtual network SVN.

There is a protocol interaction between the data gateway XGW and the satellite virtual network SVN, and the data gateway XGW may actively query the capability of each satellite virtual network SVN, where the satellite virtual network SVN replies to its own supported functions, indicating whether dynamic route distribution is supported.

Data gateway XGW maintains a database/cache that records the functional characteristics of each satellite virtual network SVN. The database may be configured by the network administrator or uploaded by the satellite virtual network SVN at registration. The data gateway XGW loads the database at startup to obtain information for each satellite virtual network SVN.

The satellite virtual network SVN supporting dynamic route distribution is configured in one group and not in another group. Data gateway XGW, when activated, distinguishes the two satellite virtual network SVN groups.

And 2, for the satellite virtual network SVN supporting dynamic route release, starting a thread to establish BGP protocol connection with the opposite-end router.

Configuring an IP address of a tap interface as a local endpoint of a BGP protocol, starting the tap interface, introducing external traffic into a protocol stack for processing, configuring parameters for the BGP protocol, constructing BGP Open information and sending the BGP Open information to the router; and waiting and processing BGP Open information returned by the router, completing three-way handshake and establishing TCP connection. Then, the two parties exchange BGP Update messages advertising network reachability information. And starting a BGP keep timer, and periodically sending keep messages to maintain the BGP session. And calculating the optimal path according to the routing strategy, and updating the routing table of the optimal path. When the local route changes, an Update message is constructed to advertise the changes. If an error occurs, a BGP Notify message is sent to close the connection.

The specific steps of the data gateway XGW starting the tap interface and establishing BGP connection include configuring an IP address of the tap interface, where the IP address is to be used as a local endpoint of BGP, starting the tap interface, and introducing external traffic into a protocol stack for processing. Parameters such AS local AS number, router ID, etc. are configured for BGP. the tap interface (TAP INTERFACE) is a network interface for monitoring or mirroring network traffic. the tap interface works on the principle that one copy (mirror image) of network traffic is transferred to the tap interface for processing. The original network traffic itself does not pass through the tap interface, but is forwarded on the normal path. the tap interface receives the copy of the mirror image flow to carry out detection, analysis and other processes. After the tap interface is processed, the mirror image flow is not forwarded, and the original flow is forwarded according to the established path. the key feature of the tap interface is that the forwarding path and performance of the original traffic are not affected. The mirror image of the network traffic can be continuously acquired for analysis and processing. The method has the effect of only monitoring and not forwarding network traffic.

Step 3, when a satellite terminal accesses or leaves a satellite access network through a dispatcher DDM, constructing a BGP message for route update and sending the BGP message to the opposite-end router; the routing information in the BGP message of the routing update includes a routing IP address and a next-hop IP address, where the routing IP address is an IP address of the satellite terminal, and the next-hop IP address is an IP address of the satellite virtual network SVN. When a satellite terminal accesses a satellite access network through a dispatcher DDM, constructing a message of route update as a BGP message of a newly added route message; when the satellite terminal leaves the satellite access network through the dispatcher DDM, constructing a route update message as a BGP message for deleting the route message.

In addition, when the configuration of the SVN is modified, the specific steps of re-establishing the BGP connection and updating the routing information include that the data gateway XGW detects that the configuration of the SVN is changed, such as subnet segment and gateway IP address change. The data gateway XGW closes the original BGP connection related to the SVN, and sends out a BGP Notify message to Notify the opposite end. Data gateway XGW clears the original BGP configuration of the SVN, including neighbors, routing policies, etc. Data gateway XGW reconfigures BGP according to the new configuration, including updating local AS, router ID, peer address, etc. Data gateway XGW restarts the BGP connection establishment procedure and sends an OPEN message. The opposite router responds to the OPEN message, and the two parties establish a new BGP connection. Data gateway XGW sends UPDATE message with new information advertising the reconfigured route. The opposite router updates its own routing table to realize the readjustment of the route. The two parties continue to maintain BGP connections and exchange keep-alive messages.

In addition, after the system is restarted, the data is recovered from the Redis, and the small satellite terminal station still accessing the network needs to reissue the route, which comprises the following specific steps: and XGW after the system is started, loading the connection state data of the small station from the Redis. For each small station loaded XGW, check if it is currently online, e.g., by heartbeat detection; for a small station that is checked to be still on-line, XGW queries the Redis to obtain the routing information of the small station, including IP address, subnet, etc. XGW constructs BGP update messages according to the routing information, and sends the BGP update messages to the correspondent router. The border router receives the update message, updates the routing table, and inserts the routing entry for the small station. The route reissue to this small station is completed. Repeating the steps for all online kiosks can complete route batch reissue. And updating the route of the up-and-down line of the small station by using BGP increment.

Redis is a memory-based non-relational (NoSQL) database that supports key-value pair storage. The data storage device has the main characteristics that the data are all stored in the memory, and the reading and writing speed is very high. A variety of data structures are supported, such as strings, hash tables, lists, collections, and the like. With persistence supported, the memory state can be saved to disk. Master-slave replication is supported, achieving high availability. Support transaction functions, etc. Written in ANSI C language, may be embedded in a variety of applications. There are numerous languages of client libraries. Concurrency is handled through multiplexing IO multiplexing techniques using a single-threaded model. Typical application scenarios for Redis include cache systems, with which fast access improves performance. A message queuing system, which uses its list to implement queuing. Real-time functions such as chat, game ranking, etc. are added to the Web application. And analyzing real-time data storage of the system. And the functions of distributed locks and the like are realized.

Based on the above route dynamic management method, the processing of the external message for the data gateway XGW includes the following steps: the data gateway XGW receives the message sent by the external opposite terminal router, checks the destination IP address of the message, and judges whether the message is to be routed to a certain satellite virtual network SVN; if so, it is indicated that the message needs to be processed within the present data gateway XGW. Such as ICMP replies, ARP replies, etc. The data gateway XGW forwards the message to the tap interface for processing. the tap interface can view the message content. Submitting the message to the protocol stack through the tap interface, processing the message according to the normal flow, and generating a response. The generated response message is handed to the corresponding SVN thread. The SVN thread sets the VLAN ID of the response message to the VID of the present SVN. And the SVN thread sends out the response message through a DPDK interface. And finally, the response message is correctly sent to an external opposite-end router through a satellite link. Wherein DPDK (DATA PLANE Development Kit) is a software architecture for high-speed packet processing. The DPDK interface refers to a Network Interface Card (NIC) that supports DPDK. The NIC can work in a user space, and the overhead of turn-back switching in a kernel space is avoided. The DPDK interface has the main advantages that the message can be directly processed in a user mode without passing through a kernel protocol stack, and the context switching overhead is reduced. The driver and the protocol stack are integrated together, so that the deep optimization is performed, and the message processing efficiency is improved. And the direct putting of the message into the queue is supported, and zero copy is realized. The method and the device remarkably improve the message receiving and transmitting rate, reduce delay and jitter, can realize rapid prototype development of network functions, and are suitable for scenes of processing a large number of small packets. Therefore, the DPDK interface transmits the message, mainly refers to the message transmission mode of the high-speed user mode, and can bypass the kernel protocol stack, reduce delay and improve throughput, and the DPDK interface is a key technology and means for realizing high-speed packet processing.

The invention provides a high-flux satellite system substation route dynamic issuing device which is applied to a data gateway XGW, and a schematic frame diagram of the device is shown in fig. 3.

And the dynamic routing capability detection module is used for traversing all the satellite virtual networks SVN and judging whether the satellite virtual networks SVN support dynamic routing release. In the dynamic routing capability detection module, the specific method for determining whether the satellite virtual network SVN supports dynamic routing release by the data gateway XGW may be as follows:

whether dynamic route release is supported is explicitly identified in the configuration information of the satellite virtual network SVN, and the data gateway XGW reads the configuration item to determine.

The satellite virtual network SVN registers its own supported functions with the data gateway XGW at start-up, including a flag as to whether dynamic route distribution is supported. Data gateway XGW stores the functional information of each satellite virtual network SVN.

There is a protocol interaction between the data gateway XGW and the satellite virtual network SVN, and the data gateway XGW may actively query the capability of each satellite virtual network SVN, where the satellite virtual network SVN replies to its own supported functions, indicating whether dynamic route distribution is supported.

Data gateway XGW maintains a database/cache that records the functional characteristics of each satellite virtual network SVN. The database may be configured by the network administrator or uploaded by the satellite virtual network SVN at registration. The data gateway XGW loads the database at startup to obtain information for each satellite virtual network SVN.

The satellite virtual network SVN supporting dynamic route distribution is configured in one group and not in another group. Data gateway XGW, when activated, distinguishes the two satellite virtual network SVN groups.

And the BGP protocol connection module is used for establishing BGP protocol connection with the opposite-end router by the starting thread for the satellite virtual network SVN supporting dynamic route release.

Configuring an IP address of a tap interface as a local endpoint of a BGP protocol, starting the tap interface, introducing external traffic into a protocol stack for processing, configuring parameters for the BGP protocol, constructing BGP Open information and sending the BGP Open information to the router; and waiting and processing BGP Open information returned by the router, completing three-way handshake and establishing TCP connection. Then, the two parties exchange BGP Update messages advertising network reachability information. And starting a BGP keep timer, and periodically sending keep messages to maintain the BGP session. And calculating the optimal path according to the routing strategy, and updating the routing table of the optimal path. When the local route changes, an Update message is constructed to advertise the changes. If an error occurs, a BGP Notify message is sent to close the connection.

The data gateway XGW starts the tap interface and establishes BGP connection specifically includes configuring an IP address of the tap interface, where the IP address is to be used as a local endpoint of BGP, starting the tap interface, and introducing external traffic into a protocol stack for processing. Parameters such AS local AS number, router ID, etc. are configured for BGP. the tap interface (TAP INTERFACE) is a network interface for monitoring or mirroring network traffic. the tap interface works on the principle that one copy (mirror image) of network traffic is transferred to the tap interface for processing. The original network traffic itself does not pass through the tap interface, but is forwarded on the normal path. the tap interface receives the copy of the mirror image flow to carry out detection, analysis and other processes. After the tap interface is processed, the mirror image flow is not forwarded, and the original flow is forwarded according to the established path. the key feature of the tap interface is that the forwarding path and performance of the original traffic are not affected. The mirror image of the network traffic can be continuously acquired for analysis and processing. The method has the effect of only monitoring and not forwarding network traffic.

The route updating module is used for constructing a BGP message for route updating and sending the BGP message to the opposite-end router when the satellite terminal accesses or leaves the satellite access network through the dispatcher DDM; the routing information in the BGP message of the routing update includes a routing IP address and a next-hop IP address, where the routing IP address is an IP address of the satellite terminal, and the next-hop IP address is an IP address of the satellite virtual network SVN. When a satellite terminal accesses a satellite access network through a dispatcher DDM, constructing a message of route update as a BGP message of a newly added route message; when the satellite terminal leaves the satellite access network through the dispatcher DDM, constructing a route update message as a BGP message for deleting the route message.

In addition, the route updating module is also used for: when the configuration of the SVN is modified, BGP connection needs to be re-established and routing information needs to be updated, wherein the method comprises XGW detecting that the configuration of the SVN is changed, such as subnet segment and gateway IP address change. The data gateway XGW closes the original BGP connection related to the SVN, and sends out a BGP Notify message to Notify the opposite end. Data gateway XGW clears the original BGP configuration of the SVN, including neighbors, routing policies, etc. Data gateway XGW reconfigures BGP according to the new configuration, including updating local AS, router ID, peer address, etc. Data gateway XGW restarts the BGP connection establishment procedure and sends an OPEN message. The opposite router responds to the OPEN message, and the two parties establish a new BGP connection. Data gateway XGW sends UPDATE message with new information advertising the reconfigured route. The opposite router updates its own routing table to realize the readjustment of the route. The two parties continue to maintain BGP connections and exchange keep-alive messages.

In addition, the route update module is further configured to recover data from the Redis after the system is restarted, and for a satellite terminal substation that is still connected to the network, the route needs to be reissued, which specifically includes: and XGW after the system is started, loading the connection state data of the small station from the Redis. For each small station loaded XGW, check if it is currently online, e.g., by heartbeat detection; for a small station that is checked to be still on-line, XGW queries the Redis to obtain the routing information of the small station, including IP address, subnet, etc. XGW constructs BGP update messages according to the routing information, and sends the BGP update messages to the correspondent router. The border router receives the update message, updates the routing table, and inserts the routing entry for the small station. The route reissue to this small station is completed. Repeating the steps for all online kiosks can complete route batch reissue. And updating the route of the up-and-down line of the small station by using BGP increment.

Redis is a memory-based non-relational (NoSQL) database that supports key-value pair storage. The data storage device has the main characteristics that the data are all stored in the memory, and the reading and writing speed is very high. A variety of data structures are supported, such as strings, hash tables, lists, collections, and the like. With persistence supported, the memory state can be saved to disk. Master-slave replication is supported, achieving high availability. Support transaction functions, etc. Written in ANSI C language, may be embedded in a variety of applications. There are numerous languages of client libraries. Concurrency is handled through multiplexing IO multiplexing techniques using a single-threaded model. Typical application scenarios for Redis include cache systems, with which fast access improves performance. A message queuing system, which uses its list to implement queuing. Real-time functions such as chat, game ranking, etc. are added to the Web application. And analyzing real-time data storage of the system. And the functions of distributed locks and the like are realized.

Based on the above route dynamic management method, the processing of the external message for the data gateway XGW includes the following steps: the data gateway XGW receives the message sent by the external opposite terminal router, checks the destination IP address of the message, and judges whether the message is to be routed to a certain satellite virtual network SVN; if so, it is indicated that the message needs to be processed within the present data gateway XGW. Such as ICMP replies, ARP replies, etc. The data gateway XGW forwards the message to the tap interface for processing. the tap interface can view the message content. Submitting the message to the protocol stack through the tap interface, processing the message according to the normal flow, and generating a response. The generated response message is handed to the corresponding SVN thread. The SVN thread sets the VLAN ID of the response message to the VID of the present SVN. And the SVN thread sends out the response message through a DPDK interface. And finally, the response message is correctly sent to an external opposite-end router through a satellite link. Wherein DPDK (DATA PLANE Development Kit) is a software architecture for high-speed packet processing. The DPDK interface refers to a Network Interface Card (NIC) that supports DPDK. The NIC can work in a user space, and the overhead of turn-back switching in a kernel space is avoided. The DPDK interface has the main advantages that the message can be directly processed in a user mode without passing through a kernel protocol stack, and the context switching overhead is reduced. The driver and the protocol stack are integrated together, so that the deep optimization is performed, and the message processing efficiency is improved. And the direct putting of the message into the queue is supported, and zero copy is realized. The method and the device remarkably improve the message receiving and transmitting rate, reduce delay and jitter, can realize rapid prototype development of network functions, and are suitable for scenes of processing a large number of small packets. Therefore, the DPDK interface transmits the message, mainly refers to the message transmission mode of the high-speed user mode, and can bypass the kernel protocol stack, reduce delay and improve throughput, and the DPDK interface is a key technology and means for realizing high-speed packet processing.

In summary, the above embodiments are only preferred embodiments of the present invention, and are not intended to limit the scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

It will be evident to those skilled in the art that the embodiments of the invention are not limited to the details of the foregoing illustrative embodiments, and that the embodiments of the present invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive, the scope of embodiments being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned. Furthermore, it is evident that the word "comprising" does not exclude other elements or steps, and that the singular does not exclude a plurality. A plurality of units, modules or means recited in a system, means or terminal claim may also be implemented by means of software or hardware by means of one and the same unit, module or means. The terms first, second, etc. are used to denote a name, but not any particular order.

Finally, it should be noted that the above-mentioned embodiments are merely for illustrating the technical solution of the embodiment of the present invention, and not for limiting, and although the embodiment of the present invention has been described in detail with reference to the above-mentioned preferred embodiments, it should be understood by those skilled in the art that modifications and equivalent substitutions can be made to the technical solution of the embodiment of the present invention without departing from the spirit and scope of the technical solution of the embodiment of the present invention.

Claims (9)

1. A method for dynamically publishing a high-throughput satellite system substation route, the method being applied to a data gateway XGW, comprising:

Step 1, traversing all satellite virtual networks SVNs, and judging whether the satellite virtual networks SVNs support dynamic route release or not;

Step 2, for the satellite virtual network SVN supporting dynamic route release, a starting thread establishes BGP protocol connection with an opposite-end router;

Step 3, when a satellite terminal accesses or leaves a satellite access network through a dispatcher DDM, constructing a BGP message for route update and sending the BGP message to the opposite-end router; the routing information in the BGP message of the routing update includes a routing IP address and a next-hop IP address, where the routing IP address is an IP address of the satellite terminal, and the next-hop IP address is an IP address of the satellite virtual network SVN.

2. The method for dynamically publishing the routes of the small stations of the high-throughput satellite system according to claim 1, wherein in the step 1, determining whether the satellite virtual network SVN supports dynamic route publishing comprises any one of the following methods:

whether dynamic route release is supported is explicitly marked in the configuration information of the satellite virtual network SVN, and the configuration item is read to judge;

Receiving registration information of the satellite virtual network SVN at the starting time, wherein the registration information comprises a mark for supporting dynamic route release or not, and storing the registration information of the satellite virtual network SVN;

Sending an inquiry request to the satellite virtual network SVN, and determining whether the satellite virtual network SVN supports dynamic route release according to the reply information of the satellite virtual network SVN to the request;

Maintaining a database, recording the SVN function characteristics of each satellite virtual network, wherein the database can be configured by network management personnel or uploaded by the SVN during registration; XGW loading the database to obtain the information of each satellite virtual network SVN when starting;

The satellite virtual network SVN supporting dynamic route release is configured in one group, and when the system is started, the two satellite virtual network SVN groups are distinguished when the system is not supported in the other group.

3. The method for dynamically publishing the high-throughput satellite system substation route according to claim 1, wherein the initiating the thread in step 2 to establish the BGP connection with the peer router comprises: configuring an IP address of a tap interface as a local endpoint of a BGP protocol, starting the tap interface, introducing external traffic into a protocol stack for processing, configuring parameters for the BGP protocol, constructing BGP Open information and sending the BGP Open information to the router; and waiting and processing BGP Open information returned by the router, completing three-way handshake and establishing TCP connection.

4. The method for dynamic distribution of high-throughput satellite system substation routes according to claim 1, wherein said step 3 comprises: when a satellite terminal accesses a satellite access network through a dispatcher DDM, a message for constructing route update is a BGP message of a newly added route message.

5. The method for dynamic distribution of high-throughput satellite system substation routes according to claim 1, wherein said step 3 comprises: when the satellite terminal leaves the satellite access network through the dispatcher DDM, constructing a route update message as a BGP message for deleting the route message.

6. The method for dynamic distribution of high-throughput satellite system substation routes according to claim 1, wherein said step 3 further comprises: and maintaining the session state of the BGP protocol between the opposite-end routers, and if the configuration of the satellite virtual network SVN is detected to change or the BGP protocol connection is restarted, establishing connection with the opposite-end routers again for the routing information of the satellite terminal which is already connected with the network, and retransmitting the BGP message of the routing update.

7. The method for dynamic distribution of high-throughput satellite system substation routes according to claim 1, wherein said step3 further comprises: loading the connection state data of the satellite terminal from a Redis database after the system is started; checking whether each loaded satellite terminal is on line or not currently; and inquiring a Redis database to acquire the routing information of the satellite terminal which is still on-line, constructing a BGP message of routing update, and sending the BGP message to the opposite-end router.

8. The method for dynamically publishing a high-throughput satellite system substation route according to any one of claims 1-7, further comprising sending a message in DPDK mode through a tap interface according to the BGP message updated by the route.

9. A high-throughput satellite system substation routing dynamic issuing device applied to a data gateway XGW, comprising:

The dynamic routing capability detection module is used for traversing all the satellite virtual networks SVNs and judging whether the satellite virtual networks SVNs support dynamic routing release or not;

The BGP protocol connection module is used for establishing BGP protocol connection between a starting thread and an opposite-end router for the satellite virtual network SVN supporting dynamic route release;

The route updating module is used for constructing a BGP message for route updating and sending the BGP message to the opposite-end router when the satellite terminal accesses or leaves the satellite access network through the dispatcher DDM; the routing information in the BGP message of the routing update includes a routing IP address and a next-hop IP address, where the routing IP address is an IP address of the satellite terminal, and the next-hop IP address is an IP address of the satellite virtual network SVN.