Satellite network backup path switching control method and device

Abstract

The application provides a satellite network backup path switching control method and device, the method comprises the following steps: when a flash failure is detected by a hardware detection module, a local repair node switches a current original basic routing path to a backup routing path to forward a data packet based on the backup routing path; when the flash failure evolves into a long-time stable failure based on a link detection module, the local repair node floods link states to all nodes of the satellite network, each node calculates a new basic routing path, and replaces a corresponding original basic routing path based on each new basic routing path; the local repair node switches the backup routing path to a new basic routing path corresponding to the local repair node to forward the data packet based on the new basic routing path. The application improves the stability of traffic forwarding under failure of the satellite network and reduces the waste of computing resources.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of satellite communication technology, and in particular to a satellite network backup path switching control method and device. BACKGROUND

[0002] Satellite communication systems play an irreplaceable role in space-air-ground-sea integrated networks due to their wide coverage, large scale, and no geographical blind area. However, the variability and instability of the satellite network topology in practice result in relatively high transmission delay of the satellite network, and link or node failures are more likely to occur. Link or node failures can affect the stability of satellite network traffic transmission; therefore, it is of great significance to improve the existing satellite network fast re-routing scheme (FRR).

[0003] In dealing with link or node failures in the field of satellite networks, the common emergency measure is to quickly adjust the physical device state to restore the underlying transmission network. However, relying solely on such physical adjustments is not sufficient to ensure reliability, because network level often needs to re-plan the route for failure conditions; when the satellite network system discovers a link or node failure through a fault detection mechanism, the routing protocol will use a fast re-routing mechanism to direct traffic to a new path that bypasses the failure area.

[0004] Based on the mature practice of ground networks, the re-routing method in satellite networks can be refined into passive re-routing and active re-routing; among them, the passive re-routing strategy plays a role after sensing the failure, this strategy uses the IGP routing protocol to sense network failures, and ensures that new routes are issued only after the convergence of the entire network topology information. However, during the convergence time of several seconds or even several minutes, the satellite communication system still cannot direct traffic to the new path. Compared with passive re-routing, the active re-routing strategy pre-configures backup resources for traffic before data transmission; once a satellite node detects an abnormal link or adjacent node, it can quickly activate the backup path and direct traffic to the pre-calculated backup path; however, this strategy also faces challenges: the direct perception of satellite node failures is limited to neighboring nodes, while other non-directly adjacent nodes in the network still need to rely on the convergence mechanism of the IGP protocol to gradually perceive the failure, which is relatively slow. In addition, due to the asynchronous update of network state, there may be some nodes still forwarding data according to the old routing information, which may cause routing loops (i.e. the Loop Free Alternate path LFA problem).

[0005] At present, although the satellite fast rerouting mechanism of the prior art can complete the forwarding of data packets based on backup paths when a link or node fails, the existing satellite fast rerouting mechanism does not classify the link failure into a stable failure of seconds and a millisecond-level flashover failure caused by laser instability, thereby limiting the perception ability of the satellite network to the flashover failure, reducing the stability of the satellite network in traffic forwarding under failure, and also causing frequent switching of the basic routing path and the backup routing path, thereby causing waste of on-board computing resources. Therefore, how to improve the stability of the satellite network in traffic forwarding under failure and reduce the waste of computing resources is a technical problem to be solved. SUMMARY

[0006] In view of this, the embodiments of the present application provide a satellite network backup path switching control method and device to eliminate or improve one or more defects in the prior art.

[0007] In one aspect of the present application, a satellite network backup path switching control method is provided, the method comprising:

[0008] When the flashover failure is detected by the hardware detection module, the local repair node switches the current original basic routing path to a backup routing path to forward data packets based on the backup routing path;

[0009] When the flashover failure evolves into a long-time stable failure based on the link detection module, the local repair node floods link states to all nodes of the satellite network, each node calculates a new basic routing path, and replaces the corresponding original basic routing path based on each new basic routing path;

[0010] The local repair node switches the backup routing path to a new basic routing path corresponding to the local repair node to forward the data packets based on the new basic routing path.

[0011] In some embodiments of the present application, before the step of detecting that the flashover failure evolves into a long-time stable failure based on the link detection module, the method further comprises:

[0012] determining whether the backup routing path reaches a preset effective time;

[0013] When the preset effective time is reached, determining whether the flashover failure is repaired;

[0014] When the flashover failure is repaired, the local repair node switches the backup routing path to the original basic routing path.

[0015] In some embodiments of the present application, the method further comprises:

[0016] When the backup routing path is not switched to the new base routing path corresponding to the local repair node at the preset time, it is determined whether the flashover fault has evolved into a long-term stable fault.

[0017] In some embodiments of the present application, the local repair node switches the backup routing path to the new base routing path corresponding to the local repair node, comprising:

[0018] When the backup routing path is not switched to the new base routing path corresponding to the local repair node at the preset time, it is determined whether the flashover fault has evolved into a long-term stable fault.

[0019] In some embodiments of the present application, the local repair node switches the current original base routing path to the backup routing path, comprising:

[0020] The local repair node sets the priority of the backup routing path to be higher than the priority of the original base routing path.

[0021] In some embodiments of the present application, the new base routing path replaces the corresponding original base routing path, comprising: setting the priority of each new base routing path to be the same priority as the corresponding original base routing path; and / or,

[0022] The local repair node switches the backup routing path to the new base routing path corresponding to the local repair node, comprising:

[0023] The local repair node sets the priority of the corresponding new base routing path to be higher than the priority of the backup routing path.

[0024] In some embodiments of the present application, it is determined whether the backup routing path reaches the preset time, comprising: determining whether the backup routing path reaches the preset time based on a backup path activation timer.

[0025] It is determined whether the backup routing path reaches the preset time, comprising: determining whether the backup routing path reaches the preset time based on a backup path activation timer.

[0026] According to an aspect of the present application, a satellite network backup path switching control system is also disclosed, the system comprising a processor, a memory and a computer program stored in the memory, the processor being configured to execute the computer program, and when the computer program is executed, the system implements the steps of the method according to any one of the above embodiments.

[0027] According to another aspect of the present invention, a computer-readable storage medium is also disclosed, on which a computer program is stored, which, when executed by a processor, implements the steps of the method as described in any of the above embodiments.

[0028] According to another aspect of the present invention, a computer program product is also disclosed, comprising a computer program that, when executed by a processor, implements the steps of the method as described in any of the above embodiments.

[0029] The satellite network backup path switching control method and apparatus disclosed in the above embodiments of the present invention, when a transient fault is detected, switches the current original basic routing path to a backup routing path. When a long-term stable fault is detected, each node recalculates its corresponding new basic routing path and further switches the backup routing path to the new basic routing path corresponding to the local repair node. This method determines the routing path switching mode based on the type of fault, preventing frequent switching between basic and backup routing paths, reducing the waste of onboard computing resources, and avoiding oscillations in service traffic caused by frequent switching between primary and backup paths, thereby improving the stability of satellite network traffic forwarding under fault conditions.

[0030] In addition to the above, this method further determines whether to switch between the basic routing path and the backup routing path by checking the effective time and deactivation time of the backup routing path. This method further improves the rationality of switching between the basic routing path and the backup routing path, thereby further improving the stability of the satellite communication system and reducing the waste of computing resources.

[0031] Additional advantages, objects, and features of the invention will be set forth in part in the description which follows, and will also become apparent in part to those skilled in the art upon studying the description, or may be learned by practice of the invention. The objects and other advantages of the invention can be realized and obtained by means of the structures specifically pointed out in the description and drawings.

[0032] Those skilled in the art will understand that the objectives and advantages achievable with the present invention are not limited to those specifically described above, and that the above and other objectives achievable with the present invention will become clearer from the following detailed description. Attached Figure Description

[0033] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, are not intended to limit the scope of the invention. The components in the drawings are not drawn to scale but are merely illustrative of the principles of the invention. For ease of illustration and description of certain parts of the invention, corresponding portions in the drawings may be enlarged, i.e., may appear larger relative to other components in an exemplary device actually manufactured according to the invention. In the drawings:

[0034] Figure 1 A flowchart of a satellite network backup path switching control method according to an embodiment of the present application.

[0035] Figure 2 A routing path diagram of a satellite network according to an embodiment of the present application.

[0036] Figure 3 A flowchart of a satellite network backup path switching control method according to another embodiment of the present application.

[0037] Figure 4 A timing diagram of a satellite network backup path switching control method according to an embodiment of the present application.

[0038] Figure 5 A node structure diagram of a satellite network according to an embodiment of the present application. DETAILED DESCRIPTION

[0039] In order to make the objects, technical solutions and advantages of the present application clearer, further detailed description will be given to the present application in combination with embodiments and drawings. Herein, the illustrative embodiments of the present application and the description thereof are used to explain the present application, but not as a limitation to the present application.

[0040] It should be noted that, in order to avoid the present application being obscured by unnecessary details, only the structures and / or processing steps closely related to the solutions according to the present application are shown in the drawings, and other details not closely related to the present application are omitted.

[0041] It should be emphasized that the term "comprise / comprising" is used herein to indicate the presence of a feature, element, step or component, but not to exclude the presence or addition of one or more other features, elements, steps or components.

[0042] It should be noted that, if not otherwise specified, the term "connection" is used herein not only to indicate direct connection, but also to indicate indirect connection with an intermediate object, and not only to indicate wired connection, but also to indicate wireless connection, which can be changed based on actual application scenarios.

[0043] In order to better understand the present application, the following are explanations of terms related to the technical solutions:

[0044] PLR (Point of Local Repair) is a device in the network, which mainly functions to reduce the impact of network failure on service transmission by quickly switching to a backup path when the network fails. Specifically, when the main LSP (Label Switched Path) link or node in the network fails, the PLR can automatically generate a backup path configuration without human intervention, thereby ensuring the continuity of the service and the stability of the network.

[0045] SR is a data forwarding protocol based on the concept of source routing, which has become the mainstream network architecture of SDN. SR divides the forwarding path into segments and assigns segment identifiers (IDs) to these segments and forwarding points. By ordering the segments and network nodes (SegmentList), a forwarding path can be obtained. SR encodes the SegmentList in the header and transmits it with the packet; after receiving the data packet, the SegmentList is parsed, and if the top identifier of the SegmentList is the node, the identifier is popped out; if it is not the node, the data packet is sent to the next point using ECMP. Based on SR, the present application can provide 100% coverage of link protection under single-link failure conditions; the present application encodes the backup path as a Segment list with order, i.e., a backup path label stack, to instruct the satellite nodes receiving these data packets to process and forward them. Segment, i.e., label, is an instruction that the satellite node needs to execute for the received data packet. By combining multiple Segments into an ordered list, the data packet can be guided to any path in the satellite network, which is not affected by the routing protocol or the shortest path. The SR backup path data packet carries a backup path label stack in its header, and the node will execute the instructions in the label stack and maintain the label stack itself through three basic operations of PUSH, CONTINUE, and NEXT. On the SR backup path, the source node is responsible for converting the basic routing data packet into the SR backup path data packet and pushing the SR backup path label; the intermediate node receives the data packet and forwards it according to the SR mode; the node at the end of the backup path receives the data packet and further converts it into a basic routing data packet and forwards it on the satellite basic routing.

[0046] In addition, in the satellite fast rerouting mechanism disclosed in the prior art, link faults are not classified into stable faults of seconds and millisecond-level flash faults caused by laser instability, thereby limiting the perception ability of the satellite network to flash faults and reducing the stability of traffic forwarding of the satellite network under flash faults. In view of the defects of the mechanism, it is necessary to make full use of the fault detection mechanism, perceive flash faults in time with the aid of hardware detection, capture long-time stable faults through the link fault detection mechanism, prevent service traffic oscillation caused by frequent switching of primary and backup paths, and further enhance the fault processing capability of the satellite network. In addition, the scheme for supporting on-board routing forwarding in the prior art cannot realize reasonable switching between the basic path and the backup path. The hardware detection and the link fault detection of the present application can prevent frequent switching of the primary path and the backup path, reduce the waste of on-board computing resources; and the present application further sets the backup path activation timer and the backup path release timer to further realize reasonable switching of the basic routing path and the backup routing path.

[0047] In summary, the satellite network rerouting mechanism based on segment routing in the prior art has weak perception ability to flash faults, thereby causing a dithering temporary communication interruption, which is not conducive to the stability of the satellite communication system; at the same time, the prior art does not consider how to smoothly and stably switch the primary path and the backup path, which is easy to cause frequent switching of the primary and backup paths, thereby causing unnecessary waste of on-board computing resources. In order to solve the above series of problems existing in the prior art, the present application discloses a satellite network backup path switching control method and device.

[0048] It should be understood that the satellite network backup path switching control method and device of the present application are used for inter-satellite links, which are links used for communication between satellites, also known as inter-satellite links or crosslinks. Through the inter-satellite link, information transmission and exchange between satellites can be realized, and multiple satellites can be interconnected through the inter-satellite link to form a space communication network with satellites as switching nodes.

[0049] In the following, embodiments of the present application will be described with reference to the accompanying drawings. In the drawings, the same reference numerals represent the same or similar components, or the same or similar steps.

[0050] Figure 1 For the flowchart of the satellite network backup path switching control method of an embodiment of the present application, as shown in Figure 1 The method at least includes steps S10 to S30.

[0051] Step S10: When a flash fault is detected based on a hardware detection module, the local repair node switches the current original basic routing path to a backup routing path to forward data packets based on the backup routing path.

[0052] The backup routing path mentioned in this step needs to be calculated before the fault occurs and the path is saved on the star; when the fault is detected, the backup path routing table item is enabled, and the basic routing message is guided to the pre-calculated SR backup routing path. On the SR backup routing path, the nodes on the star can be divided into PLR nodes (local repair nodes), intermediate nodes and stack bottom nodes according to the control and forwarding behaviors. Before the fault is detected, the PLR node pre-calculates the backup routing path under the surrounding link fault; in order to realize the table lookup forwarding of the basic routing, the PLR as the head node of the SR backup path needs to add the ability of guiding to the SR backup path table item in the table lookup forwarding process of the basic routing table when the fault is encountered, that is, adding a backup routing table item in the IP routing table, which has a lower priority than the original basic routing table item, and guiding the traffic to the virtual port of the SR backup routing path by means of the virtual port of the backup routing table item.

[0053] The flash fault can be a millisecond-level fault, that is, the PLR node detects the flash fault through a hardware detection module with millisecond-level precision, the PLR activates the SR backup routing path, that is, switches the current original basic routing path to the backup routing path, so as to guide the traffic to the virtual port of the backup routing path. Illustratively, the local repair node switches the current original basic routing path to the backup routing path, which can specifically include: the local repair node sets the priority of the backup routing path to be higher than the priority of the original basic routing path; that is, when the PLR activates the SR backup routing path, the priority of the routing table item of the backup routing path in the basic routing table is increased, so that it is higher than the table item of the basic routing path; this operation only modifies the table item priority of the backup routing path affected by the fault, and does not modify the table item of the basic routing path, which has a small operation on the routing table and can reduce the influence of the switching of the backup routing path on the service traffic.

[0054] In the above embodiment, the PLR node is in the pre-update basic routing path state under normal working condition, which is the initial state, in which the PLR node processes and forwards data packets through the basic routing path, and pre-calculates and issues the backup routing path; the priority of the backup routing path in this state is lower than that of the basic routing path, and only when the hardware detection module senses the fault, the PLR node will transfer from the initial state to the backup routing path state. The backup routing path state is the intermediate state, in which the priority of the backup routing path is modified to be higher than that of the basic routing path.

[0055] Step S20: When the flash fault evolves into a long-time stable fault based on the detection of the link detection module, the local repair node floods the link state to all nodes of the satellite network, each node calculates a new basic routing path, and replaces the corresponding original basic routing path based on each new basic routing path.

[0056] In this step, the long-time stable fault can be detected based on the link fault detection module; the long-time stable fault can be a second-level fault. It can be understood that the stable fault has a longer duration than the flash fault, which triggers the timeout of the link fault detection timer, at which time the base routing recalculation is triggered to generate the base routing bypassing the fault. Illustratively, replacing the corresponding original base routing path based on each new base routing path includes setting the priority of each new base routing path to the same priority as the corresponding original base routing path; after calculating the new base routing path at each node, the base routing entry with a lower priority than the backup routing path is issued, at which time the table entry priority of the new base routing path is lower than the table entry priority of the backup routing path, and the data is still forwarded through the backup routing path, and the new base routing path is not effective.

[0057] Step S30: The local repair node switches the backup routing path to the new base routing path corresponding to the local repair node to forward the data packet based on the new base routing path.

[0058] This step further switches the backup routing path to the new base routing path, so that the data packet is further forwarded through the new base routing path. The local repair node switches the backup routing path to the new base routing path corresponding to the local repair node, including: the local repair node sets the priority of the corresponding new base routing path to be higher than the priority of the backup routing path; in this embodiment, the priority of the backup routing path is lowered to be lower than the priority of the new base routing path, and the related traffic is switched to the converged new base routing path; in this case, the PLR is transferred from the backup path state to the updated new base routing path state, and the updated new base routing path state is the stable state of the base routing convergence after the fault; at this time, the priority of the backup routing path is modified to be lower than the priority of the converged new base routing path, and the PLR forwards the data packet through the converged new base routing path.

[0059] Reference Figure 4 When detecting the occurrence of a fault, the PLR node first detects and senses the fault in time through hardware, and immediately switches the backup path locally to ensure that the business traffic does not interrupt. At the same time, if the fault is a stable long-time fault, as the fault time reaches the scale that can be sensed by the link fault detection mechanism, the network topology synchronization update is triggered, and the new base routing on the star is converged, at which time the backup routing path can be switched back to the new base routing path state.

[0060] The method of the above embodiment guides the affected traffic to the backup routing path by means of segment routing to restore the fault; and the application also considers that, when a stable fault is perceived based on a link fault detection mechanism, if the fault perception time threshold is set too short, the primary and backup paths will be frequently switched, thereby generating unnecessary overhead; if the fault perception time threshold is set too long, when facing a flash fault, a longer time of communication interruption will be caused; therefore, the application specifically limits the millisecond-level fault as a flash fault and limits the second-level fault as a long-time stable fault. The satellite network backup path switching control method of the application does not need to frequently switch the primary and backup paths on the satellite for a long-time stable fault, and can perform data transmission with lower overhead, that is, the backup path switching mode under the cooperation of the hardware detection and the link fault detection of the application remedies the communication interruption caused by the flash fault.

[0061] In some embodiments of the application, before the step of detecting that the flash fault evolves into a long-time stable fault based on the link detection module, the method further comprises: judging whether the effective time of the backup routing path reaches an effective preset time; when the effective preset time is reached, judging whether the flash fault is repaired; when the flash fault is repaired, the local repair node switches the backup routing path to the original basic routing path.

[0062] In the above embodiment, to avoid the overhead caused by the frequent switching of the primary path and the backup path under the flash fault, after the PLR detects the flash fault based on the hardware detection module and switches from the basic routing path to the backup routing path, the backup routing path is further monitored for the effective time. For example, as shown in Figure 5 The satellite node specifically comprises a backup path effective timer module, and at this time, the backup routing path can be judged based on the backup path effective timer, that is, whether the effective time of the backup routing path reaches the effective preset time is judged based on the backup path effective timer; the backup path effective timer timeout indicates that the effective time of the backup routing path reaches the effective preset time, and the backup path effective timer not timeout indicates that the effective time of the backup routing path does not reach the effective preset time.

[0063] As shown in Figure 3As shown, when the backup path effective timer expires, it is further determined whether the fault is repaired; the backup path effective timer expires and the fault is repaired, the backup route path is switched to the original basic route path, i.e. the priority of the backup route path is reduced to be lower than the priority of the original basic route path, so as to switch to the original basic route path; if the backup path effective timer expires and the fault is not repaired, the packet is still forwarded based on the backup route path at this time. When the fault is repaired and the backup route path is switched to the original basic route path, if a new flash fault occurs, the original basic route path is switched to the backup route path again, and the backup path effective timer is reset to determine the effective time of the backup route path.

[0064] In some other embodiments, if the effective time of the backup route path does not reach the preset effective time, it is determined whether the flash fault evolves into a long-time stable fault; in this embodiment, during the timing period of the backup path effective timer, it is determined whether the flash fault evolves into a long-time stable fault based on the link fault detection mechanism.

[0065] When the link fault detection module senses the long-time stable fault, in the step of switching the backup route path to the new basic route path corresponding to the local repair node by the local repair node, it specifically includes: determining whether the release time of the backup route path reaches the preset release time, and when the preset release time is reached, the local repair node switches the backup route path to the new basic route path corresponding to the local repair node. As shown in Figure 5 As shown, the satellite node specifically includes a backup path release timer module, in this embodiment, the backup route path release time is determined based on the backup path release timer, i.e. it is determined whether the release time of the backup route path reaches the preset release time based on the backup path release timer, the backup path release timer expires indicates that the release time of the backup route path reaches the preset release time, and the backup path release timer does not expire indicates that the release time of the backup route path does not reach the preset release time, when the preset release time is reached, the backup route path is switched to the new basic route path.

[0066] As shown in Figure 3 As shown, if the link fault detection mechanism senses that the fault is a long-time stable fault, the fault information is flooded to the whole network, a new converged basic route path with a priority equal to the priority of the original basic route path is issued, and a backup path release timer is set, after the backup path release timer expires, the priority of the backup route path is reduced to be lower than the priority of the new basic route path, so as to switch to the new basic route path on the satellite. Wherein, the converged route path is shown in Figure 2 As shown in Figure 2In the present application, the P space and the Q space in the TI-LFA are used for definition; the P space refers to a set of nodes that can be reached in the SPF tree with the source end of the protection link as the root node, but the nodes do not pass through the protection link; the Q space refers to a set of nodes that can be reached in the reverse SPF tree with the end of the protection link as the root node, but the nodes do not pass through the protection link; the PQ node refers to a node that is located in the extended P space and the Q space at the same time; when the intersection contains multiple nodes, the node closest to the source node is selected as the PQ node; if the P space and the Q space have no intersection, the adjacent nodes in the P space and the Q space are selected as the P point and the Q point, which are used as the destination end of the SR backup path.

[0067] To more clearly describe the master-slave path switching in the PLR control plane process, Figure 3 The state transition of the PLR is shown; the following content starts from the state of the PLR, analyzes the relationship between the backup routing path and the basic routing path in each state of the PLR, the trigger condition of the backup routing path and the basic routing path switching, and the role of the timer, and the like.

[0068] 1) Basic routing path state before update

[0069] The PLR is in the basic routing path state before update under normal circumstances; the state is the initial state, in which the PLR processes and forwards data packets through the basic routing path, and the backup routing path is calculated and issued in advance, and the priority of the backup routing path is lower than that of the basic routing path; only in the case that the hardware detection senses a fault, the PLR will be transferred from the initial state to the backup routing path state.

[0070] 2) Backup routing path state

[0071] The backup routing path state is an intermediate state; at this time, the priority of the backup routing path is modified to be higher than that of the basic routing path, the state is relatively complex, and the maintenance and transition of the state are affected by the backup path effective timer and the backup path release timer; the specific roles of the two timers are as follows:

[0072] After the hardware detection module senses the flashover fault and switches to the backup routing path, in order to avoid the overhead caused by frequent switching between the backup routing path and the basic routing path, the backup path effective timer is set at this time, and before the backup path effective timer expires, the path is always maintained on the backup routing path.

[0073] When the link fault detection module detects a fault as a long stable fault, the PLR also provides backup route path switching capability for long stable faults. After the link fault detection module discovers a fault, in order to reduce the micro-loop caused by the fault information flooding delay, the backup path release timer is set. The timer length is recommended to be seconds, and the purpose is to cover the maximum flooding, basic route calculation and downlink efficiency delay of the entire network, so the timing length of the timer depends on the size of the constellation, and the network management system needs to be configured.

[0074] During the timing period specified by the backup path effective timer, if the link fault detection module senses a fault, the backup path effective timer should be canceled, and the backup path release timer should be set.

[0075] The backup route path state transitions to the basic route path state according to the type of the fault, which includes the following two cases:

[0076] Case one: flash fault, the fault duration cannot be sensed by the link fault detection module, that is, it will not trigger the basic route path change of the entire network, in this case, the backup route path is directly invalidated after the backup path effective timer expires and the fault is recovered, that is, it switches back to the original basic route path; specifically, the backup route path priority is reduced to be lower than the priority of the original basic route path; in this case, the PLR transitions from the backup route path state to the original basic route path state before updating.

[0077] Case two: stable fault, the fault duration is relatively long, which will trigger the timeout of the corresponding fault detection timer of the link fault detection module, at this time, a new basic route path bypassing the fault is calculated, and the backup route path needs to be released and switched to the new basic route path. After the link fault detection module detects the fault, it will flood the link state to the entire network to synchronize the topology information, but due to the flooding delay, the topology information of the nodes on the star may appear inconsistent for a short time, which eventually leads to a micro-loop of the route and affects data transmission; to solve this problem, the new basic route path is delayed for a period of time before it takes effect, and the backup route path is still used to forward data during this period. Since the backup route path is based on the SR route, the data packet path can be explicitly specified, so the loop can be avoided.

[0078] The specific implementation of the above case two includes the following two stages:

[0079] In the first stage, after the new basic routing path is calculated, the new basic routing path entry with a lower priority than the backup routing path is issued, the backup path effective timer is canceled, and the backup path release timer is set. Since the priority of the new basic routing path is lower than the priority of the backup routing path at this time, data is still forwarded through the backup routing path, and the new basic routing path is not effective. During the preset time period of the backup path release timer, the PLR guides the traffic to the explicit loop-free backup routing path.

[0080] In the second stage, after the backup path release timer expires, the PLR converges to the new basic routing path. At this time, the priority of the backup routing path is lowered to be lower than the priority of the new basic routing path, and the related traffic is switched to the converged new basic routing path. In this case, the PLR is transferred from the backup routing path state to the updated new basic routing path state.

[0081] In addition, for the intermediate node of the SR backup routing path, after receiving the data packet, it is judged that the data packet is an SR backup routing path data packet. The intermediate node only needs to forward the data packet along the path specified by the label. Specifically, the intermediate node finds the out port and label operation code of the data packet according to the label mode, then pops the top adjacent label of the header label stack, and then forwards the data packet.

[0082] For the bottom node of the SR backup routing path, after receiving the data packet, if the data packet is an SR backup routing path data packet and the label in the label stack is a bottom label, it indicates that the node is a bottom node. The bottom node pops the bottom SR node label, and at the same time, converts the message into a basic routing path message, continues the table lookup forwarding of the basic routing path, and finally forwards according to the matched out port.

[0083] It can be found from the above embodiments that the satellite network backup path switching control method reduces the communication interruption time of the satellite communication system after a fault occurs, enhances the stability of data transmission of the satellite communication system, and reduces the consumption of on-board computing resources through a reasonable primary and backup path switching mechanism. Through the cooperative work of the hardware detection and link fault detection mechanism, the satellite communication system improves the perception ability of the flash fault, reduces the jitter communication interruption caused by the flash fault, and makes the data transmission during the flash fault period more stable, that is, the stability of the satellite communication system after a fault is optimized. Moreover, the backup path effective timer is used to avoid the overhead caused by frequent switching between the backup routing path and the basic routing path, and the backup path release timer is used to reduce the local micro-loop at the fault caused by the fault information flooding delay, thereby optimizing the utilization of on-board resources and improving the efficiency of fault recovery.

[0084] The embodiments of the present application further provide a computer readable storage medium and a computer program product, and the computer program is stored on the computer readable storage medium and is executed by a processor to implement the steps of the method according to any of the above embodiments. The computer readable storage medium can be a tangible storage medium, such as a random access memory (RAM), a memory, a read only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a floppy disk, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0085] Those skilled in the art should understand that the exemplary components, systems and methods described in connection with the embodiments disclosed herein can be implemented in hardware, software or a combination thereof. The decision to implement in hardware or software depends on the particular application and design constraints imposed on the technological solution. Those skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered beyond the scope of the present application. When implemented in hardware, it can be, for example, an electronic circuit, an application specific integrated circuit (ASIC), appropriate firmware, a plug-in, a functional card, etc. When implemented in software, the elements of the present application are program or code segments used to perform the required tasks. The program or code segments can be stored in a machine readable medium or transmitted through a data signal carried in a carrier wave over a transmission medium or communication link.

[0086] It should be noted that the present application is not limited to the specific configurations and processes described above and shown in the drawings. For the sake of brevity, detailed descriptions of known methods are omitted. In the above embodiments, several specific steps are described and shown as examples. However, the method processes of the present application are not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order of the steps, after understanding the spirit of the present application.

[0087] In the present application, the features described and / or illustrated for one embodiment can be used in the same way or in a similar way in one or more other embodiments, and / or in combination with or instead of features of other embodiments.

[0088] The above description is merely the preferred embodiments of the present application, and is not intended to limit the present application. Those skilled in the art can make various modifications and changes to the embodiments of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. A satellite network backup path handover control method characterized by comprising: The method comprises: When the hardware detection module detects a flash failure, the local repair node switches the current original basic routing path to a backup routing path to forward data packets based on the backup routing path; determining whether the backup routing path is effective for a predetermined time; when the predetermined time is reached, determining whether the flash failure is repaired; when the flash failure is repaired, the local repair node switches the backup routing path to the original basic routing path; when the backup routing path is not effective for a predetermined time, determining whether the flash failure evolves into a long-term stable failure; When the link detection module detects that the flash failure evolves into a long-term stable failure, the local repair node floods link states to all nodes of the satellite network, each node calculates a new basic routing path, and replaces the corresponding original basic routing path based on each new basic routing path; The local repair node switches the backup routing path to the new basic routing path corresponding to the local repair node to forward the data packets based on the new basic routing path.

2. The satellite network backup path switch-over control method according to claim 1, characterized by, The local repair node switches the backup routing path to the new basic routing path corresponding to the local repair node, comprising: determining whether the backup routing path is effective for a predetermined time; when the predetermined time is reached, the local repair node switches the backup routing path to the new basic routing path corresponding to the local repair node.

3. The satellite network backup path switch-over control method according to claim 1, characterized by, The local repair node switches the current original basic routing path to the backup routing path, comprising: The local repair node sets the priority of the backup routing path to be higher than the priority of the original basic routing path.

4. The satellite network backup path switch-over control method according to claim 1, characterized by, Replacing the corresponding original basic routing path based on each new basic routing path comprises setting the priority of each new basic routing path to be the same priority as the corresponding original basic routing path; and / or, The local repair node switches the backup routing path to the new basic routing path corresponding to the local repair node, comprising: The local repair node sets the priority of the corresponding new basic routing path to be higher than the priority of the backup routing path.

5. The satellite network backup path switch-over control method according to claim 2, characterized by, Determining whether the backup routing path is effective for a predetermined time comprises determining whether the backup routing path is effective for a predetermined time based on a backup path validity timer; Determining whether the backup routing path is effective for a predetermined time comprises determining whether the backup routing path is effective for a predetermined time based on a backup path validity timer.

6. A satellite network backup path handover control system, the system comprising a processor, a memory, and a computer program stored on the memory, wherein, The processor is configured to execute the computer program, and when the computer program is executed, the system implements the steps of the method according to any one of claims 1 to 5.

7. A computer-readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by the processor to implement the steps of the method according to any one of claims 1 to 5.

8. A computer program product comprising a computer program, characterized in that, The computer program is executed by the processor to implement the steps of the method according to any one of claims 1 to 5.

Images