FRRouting-based SRV6 SID unified distribution management method

By establishing SID Pool in the Zebra module of FRRouting, the conflict problem between IGP and BGP protocols during SRV6 SID allocation is solved, the uniqueness management of SID and the acquisition of SID Locator information in the routing protocol process is realized, and SID allocation and management are improved efficiency.

CN119071213APending Publication Date: 2024-12-03JIANGSU FUTURE NETWORKS INNOVATION
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202411187221.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-28
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

In the existing FRRouting implementation, the IGP protocol and the BGP protocol are prone to conflicts when allocating SRV6 SIDs, and the statically allocated SRV6 SID may also conflict with the SID assigned by the BGP protocol.

Method used

By establishing a public SID Pool in the Zebra module of FRRouting, adding SID message interaction types and deleting SID message interaction types, each routing protocol applies and releases SID to the Zebra module statically or dynamically according to its own needs to avoid SID conflicts.

Benefits of technology

It effectively avoids duplicate allocation of dynamic and static SIDs, ensures the uniqueness and management efficiency of SIDs, and ensures that the Locator information of SIDs in the routing protocol process is available.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119071213A_ABST
    Figure CN119071213A_ABST
Patent Text Reader

Abstract

The invention discloses an SRV6 SID unified distribution management method based on FRRouting, and the method comprises the steps: building a public SID Pool in a Zebraa module of the FRRouting, adding an SID message interaction type and deleting the SID message interaction type in a netlink message interaction type, and enabling the FRRouting to comprise a CLI command interface; each routing protocol sends a static SID application message or a dynamic SID application message to the Zebra module in a static allocation or dynamic allocation mode according to the own protocol process demand, applies for allocating a static SID or a dynamic SID, and stores the SID of the successfully allocated static SID or dynamic SID into an SID Pool, and the SID comprises Locator information; deleting the static SID or the dynamic SID according to each routing protocol process requirement or Zebra process requirement to finish deletion and release of the SID; according to the method, the Zebraa is used as a public management module for dynamic and static distribution, the situation that SID distributed dynamically and statically is repeated is avoided, meanwhile, SID information needed by a protocol process in an FRRouting framework is stored in the Zebraa module, and specific information of Locator of the SID can be conveniently obtained.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of SR technology, and in particular to a SRV6 SID unified allocation management method based on FRRouting. Background Art

[0002] FRRouting is a free, open source Internet routing protocol suite that is widely used to build and manage data networks. It provides a series of routing protocols, including BGP, OSPF, RIP, IS-IS, PIM, LDP, BFD, Babel, PBR, VRRP and other routing protocols, and supports different types of networks such as IP, IPv6 and MPLS.

[0003] FRRouting is a highly flexible and reliable routing solution with powerful performance and scalability.

[0004] In the existing FRRouting implementation, only the BGP protocol extension supports the routing function of SRV6 END.DT4, END.DT6 and END.DT46 SIDs. However, the BGP protocol allocates SIDs automatically in its own process according to the Locator prefix through dynamic automatic allocation and the configuration of specified index. If the IGP protocol also needs to support the extended function of SRV6, and allocates END and END.X SIDs when bound to the same SRV6 Locator as the BGP protocol, it is easy to cause conflicts between the SIDs allocated by the IGP protocol and the SIDs allocated by the BGP protocol. At the same time, if the SRV6 SIDs specified by static allocation are the same as the SRV6 Locator, they may also conflict with the SIDs allocated by the BGP protocol. Summary of the invention

[0005] The present invention avoids conflicts between SIDs allocated by IGP and BGP protocols and SIDs assigned by static allocation by establishing a mechanism for public allocation and management of SRV6 SIDs.

[0006] The present invention proposes a SRV6 SID unified allocation management method based on FRRouting, and the technical solution adopted is: A unified SRV6 SID allocation management method based on FRRouting, the allocation management method comprising the following steps: AS1. Establish a public SID Pool in the Zebra module of FRRouting, add the add SID message interaction type and delete SID message interaction type in the netlink message interaction type, and FRRouting includes a CLI command interface; AS2. Each routing protocol sends a static SID application message or a dynamic SID application message to the Zebra module to apply for the allocation of a static SID or a dynamic SID through static allocation or dynamic allocation according to the needs of its own protocol process, and stores the SID of the successfully allocated static SID or dynamic SID in the SID Pool. The SID includes the Locator information; AS3. Based on AS2, the static SID or dynamic SID is deleted according to the requirements of each routing protocol process or the Zebra process, and the deletion and release of the SID is completed.

[0007] In a further preferred embodiment of the technical solution of the present invention, the routing protocol sends a dynamic SID application message to the Zebra module by adding a SID message interaction type, and the Zebra module sends a dynamically allocated dynamic SID to the routing protocol by adding a SID message interaction type.

[0008] In a further preferred embodiment of the technical solution of the present invention, the routing protocol sends a static SID application message to the Zebra module through the CLI command interface, and the static SID application message includes the applied static SID.

[0009] Further optimization of the technical solution of the present invention, in step AS2, each routing protocol sends a static SID application message or a dynamic SID application message to the Zebra module to apply for allocation of a static SID or a dynamic SID by static allocation or dynamic allocation according to the requirements of its own protocol process, and stores the successfully allocated SID in the SID Pool, including the following three situations: Each routing protocol applies for a static SID. Each routing protocol sends multiple static SID application messages to the Zebra module through the CLI command interface. The Zebra module compares the static SIDs with the SIDs in the SID Pool one by one in the order in which the static SID application messages are sent. If the static SID being compared does not exist in the SID Pool, the application is successful and the static SID is stored in the SID Pool. At the same time, the statically allocated static SID returns a successful application message through the CLI command interface. If the static SID being compared exists in the SID Pool, the application is unsuccessful and the Zebra module sends an error prompt to the routing protocol that applied for the static SID through the CLI command interface. Each routing protocol applies for a dynamic SID. Each routing protocol sends multiple dynamic SID application messages to the Zebra module by adding a SID message interaction type. The Zebra module receives multiple dynamic SID application messages, automatically generates a dynamic SID, and compares them one by one with the SIDs in SID POOl in the time sequence of sending the dynamic SID application messages. If the dynamic SID being compared does not have the same SID in the SID Pool, the application is successful and the dynamic SID is stored in the SID Pool. The dynamically allocated dynamic SID returns the successfully dynamically allocated dynamic SID by adding a SID message interaction type. If the dynamic SID being compared has the same SID in the SID Pool, the application is unsuccessful. The Zebra module recalculates and generates another dynamic SID and compares them again in time sequence until the application is successful. Each routing protocol applies for static SID and dynamic SID, and sends corresponding application messages through CLI command interface and adding SID message interaction type respectively. Zebra module receives dynamic SID application message and static SID application message. When Zebra module receives dynamic SID application message, it automatically generates dynamic SID and compares it with SID information in SID Pool one by one according to the time sequence of receiving static SID application message and dynamic SID application message. If the dynamic SID or static SID to be compared does not exist in the SID Pool, the application is successful. The static SID successfully allocated returns a successful application message through the CLI command interface. The dynamic SID successfully allocated returns the successfully dynamically allocated dynamic SID by adding the SID message interaction type, and the successfully allocated SID is stored in the SIDPool. If the dynamic SID or static SID being compared has the same SID in the SID Pool, if the dynamic SID exists, the application fails, and the Zebra module recalculates and generates another dynamic SID, and compares again in chronological order until the application is successful; if the static SID exists, the Zebra module sends an error prompt to the routing protocol that applied for this static SID through the CLI command interface.

[0010] In a further preferred embodiment of the technical solution of the present invention, the routing protocol and the Zebra module send a dynamic SID deletion message to each other through a delete SID message interaction type.

[0011] In a further preferred embodiment of the technical solution of the present invention, the routing protocol also sends a static SID deletion message to the Zebra module through the CLI command interface.

[0012] Further optimization of the technical solution of the present invention, in step AS3, the static SID or dynamic SID is deleted according to the requirements of each routing protocol process or the Zebra process, including deleting the dynamic SID and the static SID according to the requirements of each routing protocol process and deleting the dynamic SID according to the requirements of the Zebra process, as follows: Delete dynamic SIDs and static SIDs according to the requirements of each routing protocol process. The specific steps are as follows: BS1. Each routing protocol deletes the dynamic SID or static SID in its own protocol process according to its own protocol process requirements, and sends a SID deletion message to the Zebra module, and the SID deletion message includes the SID to be deleted; BS2.Zebra module searches and compares the SID in the received SID deletion message with the SID in the SID Pool, and then deletes it to complete the deletion and release of the SID; Delete the dynamic SID according to the Zebra process requirements. The specific steps are as follows: When the CS1.Zebra module deletes the Locator information according to the requirements of the Zebra process, it clears all SIDs containing this Locator information in the corresponding SID Pool, and sends a Locator deletion message to the routing protocol through the deletion SID message interaction type. The Locator deletion message includes the Locator information. CS2. Each routing protocol receives the Locator deletion message and clears all dynamic SIDs containing the Locator information in each routing protocol process.

[0013] An electronic device comprises a processor and a memory, wherein the memory stores a computer program that can be run on the processor, and the processor executes the steps of the above method when running the computer program.

[0014] Compared with the prior art, the present invention has the following beneficial effects: 1. The present invention uses Zebra as a public management module for dynamic and static allocation to avoid duplication of dynamically allocated dynamic SIDs and statically allocated static SIDs. At the same time, the SID information required by the routing protocol process in the FRRouting architecture is stored in the Zebra module, which is convenient for obtaining the specific information of the SID Locator.

[0015] 2. The present invention establishes a SID Pool in the Zebra module to compare the dynamic SID applied for allocation, the static SID and the existing SID in the SIDPool, to ensure that the static SID and the dynamic SID in the successfully allocated routing protocol will not conflict. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 It is a flow chart of a unified SRV6 SID allocation management method based on FRRouting; Figure 2 It is a flowchart for deleting dynamic SIDs and static SIDs according to the requirements of the routing protocol process; Figure 3 It is a flowchart for deleting dynamic SID according to the requirements of Zebra process. DETAILED DESCRIPTION

[0017] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the following Figure 1-3 , the present invention is described in further detail.

[0018] It should be understood that the description herein is only used to explain the present invention, and is not used to limit the present invention.

[0019] like Figure 1 As shown, a SRV6 SID unified allocation management method based on FRRouting in this embodiment includes the following steps: AS1. Establish a public SID Pool in the Zebra module of FRRouting, add the add SID message interaction type and delete SID message interaction type in the netlink message interaction type, and FRRouting includes a CLI command interface; AS2. Each routing protocol sends a static SID application message or a dynamic SID application message to the Zebra module to apply for the allocation of a static SID or a dynamic SID through static allocation or dynamic allocation according to the needs of its own protocol process, and stores the SID of the successfully allocated static SID or dynamic SID in the SID Pool. The SID includes the Locator information; AS3. Based on AS2, the static SID or dynamic SID is deleted according to the requirements of each routing protocol process or the Zebra process, and the deletion and release of the SID is completed.

[0020] Before implementing the allocation management method, modify the FRRouting configuration and remove the process of self-allocation of SIDs by the BGP protocol. The process of self-allocation of SIDs in the BGP protocol includes automatic generation of SIDs and allocation of SIDs; configure the process of self-allocation of SIDs into the Zebra module, and the Zebra module automatically generates SIDs inside the Zebra module according to the application messages of each routing protocol and then dynamically allocates them.

[0021] The Zebra module can centrally manage statically and dynamically assigned SIDs.

[0022] The SID Pool is set in the Zebra module. The SID Pool contains the dynamic SIDs and static SIDs applied for by each routing protocol and the protocols applied for each SID for storage, which is convenient for users to view.

[0023] In this embodiment, the SID message interaction type is added to complete the routing protocol sending a dynamic SID application message to the Zebra module. At the same time, the Zebra module sends the successfully dynamically allocated dynamic SID to the routing protocol corresponding to the sending application message by adding the SID message interaction type.

[0024] The Delete SID message interaction type is used for each routing protocol and Zebra module to send SID deletion messages to each other through the Delete SID message type when they need to delete dynamic SIDs according to their own process changes. That is, when each routing protocol needs to delete dynamic SIDs according to its own protocol process changes, it sends SID deletion messages to the Zebra module through the Delete SID message interaction type; when the Zebra module needs to delete Locator information according to the Zebra process change requirements, the Zebra module sends a Locator deletion message to the routing protocol through the Delete SID message interaction type, and the routing protocol deletes the dynamic SID containing the Locator information in the routing protocol according to the Locator deletion message.

[0025] The routing protocol sends a static SID application message to the Zebra module through the CLI command interface. The static SID application message includes the applied static SID.

[0026] When the routing protocol needs to delete the statically configured static SID according to its own protocol process requirements, the routing protocol sends a SID deletion message to the Zebra module through the CLI command interface.

[0027] The Zebra module can identify the current routing protocol's dynamic SID application and dynamic SID deletion operations according to the add SID message interaction type and delete SID message interaction type.

[0028] In step AS2, each routing protocol sends a static SID application message or a dynamic SID application message to the Zebra module to apply for the allocation of a static SID or a dynamic SID through static allocation or dynamic allocation according to the requirements of its own protocol process, and stores the successfully allocated SID in the SID Pool, including the following three situations: Each routing protocol applies for a static SID. Each routing protocol sends multiple static SID application messages to the Zebra module through the CLI command interface. The Zebra module compares the static SIDs with the SIDs in the SID Pool one by one in the order in which the static SID application messages are sent. If the static SID being compared does not exist in the SID Pool, the application is successful and the static SID is stored in the SIDPool. At the same time, the statically allocated static SID returns a successful application message through the CLI command interface. If the static SID being compared does exist in the SID Pool, the application is unsuccessful and the Zebra module sends an error prompt to the routing protocol that applied for the static SID through the CLI command interface. Each routing protocol applies for a dynamic SID. Each routing protocol sends multiple dynamic SID application messages to the Zebra module by adding a SID message interaction type. The Zebra module receives multiple dynamic SID application messages, automatically generates a dynamic SID, and compares them one by one with the SIDs in SID POOl in the time sequence of sending the dynamic SID application messages. If the dynamic SID being compared does not have the same SID in the SID Pool, the application is successful and the dynamic SID is stored in the SID Pool. The dynamically allocated dynamic SID returns the successfully dynamically allocated dynamic SID by adding a SID message interaction type. If the dynamic SID being compared has the same SID in the SID Pool, the application is unsuccessful. The Zebra module recalculates and generates another dynamic SID and compares them again in time sequence until the application is successful. Each routing protocol applies for static SID and dynamic SID, and sends corresponding application messages through CLI command interface and adding SID message interaction type respectively. Zebra module receives dynamic SID application message and static SID application message. When Zebra module receives dynamic SID application message, it automatically generates dynamic SID and compares it with SID information in SID Pool one by one according to the time sequence of receiving static SID application message and dynamic SID application message. If the dynamic SID or static SID to be compared does not exist in the SID Pool, the application is successful. The static SID successfully allocated returns a successful application message through the CLI command interface. The dynamic SID successfully allocated returns the successfully dynamically allocated dynamic SID by adding the SID message interaction type, and the successfully allocated SID is stored in the SIDPool. If the dynamic SID or static SID being compared has the same SID in the SID Pool, if the dynamic SID exists, the application fails, and the Zebra module recalculates and generates another dynamic SID, and compares again in chronological order until the application is successful; if the static SID exists, the Zebra module sends an error prompt to the routing protocol that applied for this static SID through the CLI command interface.

[0029] For example, the current Zebra module does not contain SID: 2001:db8:236:100::2 and SID: 2001:db8:236:100::3. The BGP protocol sends a dynamic SID application message to the Zebra module by adding the SID message interaction type. The ISIS protocol applies for a static SID: 2001:db8:236:100::2 from the Zebra module through the CLI command interface. The Zebra module receives the dynamic SID application message from the BGP protocol and the static SID: 2001:db8:236:100::2 applied by the ISIS protocol. When the Zebra module receives the dynamic SID application message from the BGP protocol, it automatically generates a dynamic SID: 2001:db8:236:100::2. If the Zebra module receives the dynamic SID application message from the BGP protocol before the static SID applied by the ISIS protocol, the dynamic SID is first compared with the SID in the SID Pool. If the dynamic SID is in the SID Pool, the dynamic SID is compared with the SID in the SID Pool. If it does not exist in the Pool, the dynamic SID application is successful, and the dynamic SID: 2001:db8:236:100::2 is returned to the BGP protocol by adding the SID message interaction type, and the dynamic SID is saved in the SID Pool; then the static SID: 2001:db8:236:100::2 is compared with the SID Pool again, and it is found that the SID Pool already has the same SID as the applied static SID, then the application is unsuccessful, and the Zebra module sends an error prompt to the ISIS protocol through the CLI command interface to reconfigure the application.

[0030] If the Zebra module receives the dynamic SID application message of the BGP protocol after the time of receiving the static SID application time of the ISIS protocol, the static SID: 2001:db8:236:100::2 is first compared with the SID Pool. If the Zebra module does not contain the static SID at this time, the static SID application is successful. The Zebra module sends a successful application message through the CLI command interface and stores the static SID in the SID Pool. Then the dynamic SID: 2001:db8:236:100::2 is compared with the SID Pool. It is found that the SID Pool already has the same SID as the dynamic SID: 2001:db8:236:100::2. At this time, the Zebra module recalculates another dynamic SID: 2001:db8:236:100::3, sorts them according to the time sequence of the Zebra module receiving the application message, and then compares them with the SID stored in the SID Pool. If the SID If there is no SID in the pool that is the same as the dynamic SID: 2001:db8:236:100::2, the application is successful.

[0031] In step AS3, the static SID or dynamic SID is deleted according to the requirements of each routing protocol process or the Zebra process, including deleting the dynamic SID and the static SID according to the routing protocol process requirements and deleting the dynamic SID according to the Zebra process requirements, as follows: like Figure 2 As shown in the figure, delete the dynamic SID and static SID according to the requirements of each routing protocol process. The specific steps are as follows: BS1. Each routing protocol deletes the dynamic SID or static SID in its own protocol process according to its own protocol process requirements, and the routing protocol sends a SID deletion message to the Zebra module; if the dynamic SID needs to be deleted, the routing protocol sends a SID deletion message to the Zebra module through the delete SID message interaction type, and the SID deletion message includes the dynamic SID to be deleted; if the static SID needs to be deleted, the routing protocol sends a SID deletion message through the CLI command interface, and the SID deletion message includes the static SID to be deleted.

[0032] If each routing protocol deletes the dynamic SID or static SID in its own protocol process according to its own protocol process requirements but does not send a SID deletion message to the Zebra module, the Zebra module will always retain the dynamic SID or static SID, making it impossible to reallocate the SID that is the same as the dynamic SID or static SID.

[0033] For example, the dynamically allocated dynamic SID is 2001:db8:236:100::2, and the static SID allocated statically is 2001:db8:236:100::3. The dynamic SID and static SID are stored in the SID Pool of the Zebra module. The routing protocol deletes the dynamic SID according to its own protocol requirements, but does not send SID deletion information to the Zebra module. The dynamic SID 2001:db8:236:100::2 is always present in the SID Pool of the Zebra module by default. When a dynamic SID is generated according to the requirements of the routing protocol process, the SID containing 2001:db8:236:100::2 will be avoided. If the static allocation wants to use 2001:db8:236:100::2 as the static SID information to apply, the application cannot be successful, resulting in the dynamic SID information remaining in the Zebra module.

[0034] The BS2.Zebra module searches and compares the SID information of the received deletion message with the SID information in the SID Pool, and then deletes it to complete the deletion and release of the SID.

[0035] like Figure 3 As shown, the dynamic SID is deleted according to the Zebra process requirements. The specific steps are as follows: When the CS1.Zebra module deletes the Locator information in the Zebra process according to the requirements of the Zebra process, it clears all SIDs containing this Locator information in the corresponding SID Pool, and sends a Locator deletion message to the corresponding routing protocol through the deletion SID message interaction type. The Locator deletion message includes the Locator information. CS2. Each routing protocol receives the Locator deletion message and clears all dynamic SIDs containing the Locator in each routing protocol process.

[0036] The parts not involved in the present invention are the same as the prior art or can be implemented by using the prior art.

[0037] As described above, although the present invention has been shown and described with reference to specific preferred embodiments, it should not be construed as limiting the present invention itself. Various changes in form and details may be made without departing from the spirit and scope of the present invention as defined in the appended claims.

Claims

1. A SRV6 SID unified allocation management method based on FRRouting, characterized by: The allocation management method comprises the following steps: AS1. Establish a public SID Pool in the Zebra module of FRRouting, add the add SID message interaction type and delete SID message interaction type in the netlink message interaction type, and FRRouting includes a CLI command interface; AS2. Each routing protocol sends a static SID application message or a dynamic SID application message to the Zebra module to apply for the allocation of a static SID or a dynamic SID through static allocation or dynamic allocation according to the needs of its own protocol process, and stores the SID of the successfully allocated static SID or dynamic SID in the SID Pool. The SID includes the Locator information; AS3. Based on AS2, the static SID or dynamic SID is deleted according to the requirements of each routing protocol process or the Zebra process, and the deletion and release of the SID is completed.

2. According to claim 1, a SRV6 SID unified allocation management method based on FRRouting is characterized in that: The routing protocol sends a dynamic SID application message to the Zebra module by adding the SID message interaction type, and the Zebra module sends the dynamically allocated dynamic SID to the routing protocol by adding the SID message interaction type.

3. The method for unified allocation and management of SRV6 SID based on FRRouting according to claim 1, characterized in that: The routing protocol sends a static SID application message to the Zebra module through the CLI command interface. The static SID application message includes the applied static SID.

4. The method for unified allocation and management of SRV6 SID based on FRRouting according to claim 3 is characterized in that: In step AS2, each routing protocol sends a static SID application message or a dynamic SID application message to the Zebra module to apply for the allocation of a static SID or a dynamic SID through static allocation or dynamic allocation according to the requirements of its own protocol process, and stores the successfully allocated SID in the SID Pool, including the following three situations: Each routing protocol applies for a static SID. Each routing protocol sends multiple static SID application messages to the Zebra module through the CLI command interface. The Zebra module compares the static SIDs with the SIDs in the SID Pool one by one in the order in which the static SID application messages are sent. If the static SID being compared does not exist in the SID Pool, the application is successful and the static SID is stored in the SIDPool. At the same time, the statically allocated static SID returns a successful application message through the CLI command interface. If the static SID being compared exists in the SID Pool, the application is unsuccessful and the Zebra module sends an error prompt to the routing protocol that applied for the static SID through the CLI command interface. Each routing protocol applies for a dynamic SID. Each routing protocol sends multiple dynamic SID application messages to the Zebra module by adding a SID message interaction type. The Zebra module receives multiple dynamic SID application messages, automatically generates a dynamic SID, and compares them one by one with the SIDs in SID POOl in the time sequence of sending the dynamic SID application messages. If the dynamic SID being compared does not have the same SID in the SID Pool, the application is successful and the dynamic SID is stored in the SID Pool. The dynamically allocated dynamic SID returns the successfully dynamically allocated dynamic SID by adding a SID message interaction type. If the dynamic SID being compared has the same SID in the SID Pool, the application is unsuccessful. The Zebra module recalculates and generates another dynamic SID and compares them again in time sequence until the application is successful. Each routing protocol applies for static SID and dynamic SID, and sends corresponding application messages through CLI command interface and adding SID message interaction type respectively. Zebra module receives dynamic SID application message and static SID application message. When Zebra module receives dynamic SID application message, it automatically generates dynamic SID and compares it with SID information in SID Pool one by one according to the time sequence of receiving static SID application message and dynamic SID application message. If the dynamic SID or static SID to be compared does not exist in the SID Pool, the application is successful. The static SID successfully allocated returns a successful application message through the CLI command interface. The dynamic SID successfully allocated returns the successfully dynamically allocated dynamic SID by adding the SID message interaction type, and the successfully allocated SID is stored in the SID Pool. If the dynamic SID or static SID being compared has the same SID in the SID Pool, if the dynamic SID exists, the application fails, and the Zebra module recalculates and generates another dynamic SID, and compares again in chronological order until the application is successful; if the static SID exists, the Zebra module sends an error prompt to the routing protocol that applied for this static SID through the CLI command interface.

5. The method for unified allocation and management of SRV6 SID based on FRRouting according to claim 1, characterized in that: The routing protocol and the Zebra module send dynamic SID deletion messages to each other through the Delete SID message interaction type.

6. The method for unified allocation and management of SRV6 SID based on FRRouting according to claim 1, characterized in that: The routing protocol also sends a static SID deletion message to the Zebra module through the CLI command interface.

7. The method for unified allocation and management of SRV6 SID based on FRRouting according to claim 1, characterized in that: In step AS3, the static SID or dynamic SID is deleted according to the requirements of each routing protocol process or the Zebra process, including deleting the dynamic SID and the static SID according to the requirements of each routing protocol process and deleting the dynamic SID according to the requirements of the Zebra process, as follows: Delete dynamic SIDs and static SIDs according to the requirements of each routing protocol process. The specific steps are as follows: BS1. Each routing protocol deletes the dynamic SID or static SID in its own protocol process according to its own protocol process requirements, and sends a SID deletion message to the Zebra module, and the SID deletion message includes the SID to be deleted; BS2.Zebra module searches and compares the SID in the received SID deletion message with the SID in the SID Pool, and then deletes it to complete the deletion and release of the SID; Delete the dynamic SID according to the Zebra process requirements. The specific steps are as follows: When the CS1.Zebra module deletes the Locator information according to the requirements of the Zebra process, it clears all SIDs containing this Locator information in the corresponding SID Pool, and sends a Locator deletion message to the routing protocol through the deletion SID message interaction type. The Locator deletion message includes the Locator information. CS2. Each routing protocol receives the Locator deletion message and clears all dynamic SIDs containing the Locator information in each routing protocol process.

8. An electronic device comprising a processor and a memory, wherein the memory stores a computer program that can be run on the processor, wherein: When the processor runs the computer program, the steps of the method according to any one of claims 1 to 7 are performed.

Citation Information

Cited By

  • Center-free multi-partition NAVDAT time slot coordination method

    CN121771968A