Adjacent segment allocation method and device, segment router, communication device and storage medium

Abstract

The application relates to the technical field of communication networks and discloses a method and device for adjacent segment allocation, a segment router, a communication device and a storage medium. The method comprises the following steps: acquiring configured SRLB multi-attribute configuration information; determining the allocation attribute of the SRLB according to the SRLB multi-attribute configuration information; and obtaining the adjacent segment allocated from the SRLB according to the allocation attribute. In the foregoing manner, a plurality of SRLBs with different attributes can be configured on the segment router, so that the conflict caused when the segment router and the communication device simultaneously allocate adjacent segments from the SRLB can be avoided, and the problem that the traffic engineering or segment routing strategy path is unavailable due to the change of the adjacent segment originally allocated from the SRLB when the link interruption using the adjacent segment is recovered can be solved.

Description

Technical Field

[0001] This invention relates to the field of communication network technology, and in particular to a method, apparatus, segment router, communication equipment, and storage medium for adjacent segment allocation. Background Technology

[0002] In communication networks, when segment routers allocate segments, prefix segments are allocated from the Segment Routing Global Block (SRGB), while adjacent segments are allocated from the Segment Routing Local Block (SRLB). Although adjacent segments will not repeat on the same segment router, they may repeat between different segment routers within the same segment routing domain. Furthermore, network failures or device restarts can cause these adjacent segments to change, resulting in the local and volatile nature of adjacent segments allocated from the SRLB. This can lead to unusable traffic engineering or segment routing policy paths when links using adjacent segment labels are interrupted and then restored, resulting in packet loss. Additionally, when the controller centrally allocates adjacent segments to segment routers, conflicts may occur if these segments are allocated from the same SRLB. Summary of the Invention

[0003] The main objective of this invention is to provide a method, apparatus, segment router, communication device, and storage medium for adjacent segment allocation, aiming to solve the stability of adjacent segments allocated by the segment router and the conflict problem when the segment router and communication device allocate adjacent segments simultaneously.

[0004] To achieve the above objectives, the present invention provides an adjacency segment allocation method, which is applied to the segment router side and includes:

[0005] Retrieve the configured SRLB multi-attribute configuration information;

[0006] The allocation attributes of the SRLB are determined based on the SRLB multi-attribute configuration information;

[0007] The adjacent segments allocated from the SRLB are obtained based on the allocation attributes.

[0008] Optionally, after obtaining the configured SRLB multi-attribute configuration information, the method further includes:

[0009] The SRLB multi-attribute configuration information is reported to the communication device via an extended border gateway link-state protocol or an extended path calculation unit protocol; and

[0010] The SRLB multi-attribute configuration information is advertised to other network elements through an extended intermediate system-to-intermediate system routing protocol or an extended open shortest path first protocol.

[0011] Optionally, the extended border gateway link state protocol includes a multi-attribute SRLB node attribute TLV, wherein the multi-attribute SRLB node attribute TLV includes a corresponding type field, length field, flag field, reserved field, adjacency range, managed attribute and / or persistent attribute flags and corresponding values.

[0012] Optionally, the extended path computation unit protocol includes a multi-attribute SRLB TLV, wherein the multi-attribute SRLB TLV includes a corresponding type field, length field, flag field, reserved field, adjacent segment range, managed attribute and / or persistent attribute flags and corresponding values.

[0013] Optionally, the extended intermediate system to intermediate system routing protocol includes a multi-attribute SRLB Sub-TLV, wherein the multi-attribute SRLB Sub-TLV includes a corresponding type field, length field, flag field, reserved field, adjacency range, managed attribute and / or persistent attribute flags and their corresponding values.

[0014] Optionally, after obtaining the adjacent segment allocated from the SRLB based on the allocation attribute, the method further includes:

[0015] The adjacent segments allocated from the SRLB, along with their corresponding managed and / or persistent attributes, are advertised to other network elements via an extended intermediate system-to-intermediate system routing protocol or an extended open shortest path first protocol, so that these other network elements can obtain the adjacent segments allocated from the SRLB and their corresponding managed and / or persistent attributes; and

[0016] The extended border gateway link state protocol or the extended path computation unit protocol reports the adjacent segments allocated from the SRLB and their corresponding managed attributes and / or persistent attributes to the communication device, so that the communication device can obtain the adjacent segments and their corresponding managed attributes and / or persistent attributes according to the extended border gateway link state protocol or the extended path computation unit protocol.

[0017] Optionally, the extended intermediate system to intermediate system routing protocol includes a first adjacency segment identifier (Sub-TLV).

[0018] The first adjacency segment identifier Sub-TLV includes a corresponding type field, length field, flag field, adjacency segment, and corresponding value. The flag field corresponding to the first adjacency segment identifier Sub-TLV includes defined managed attribute and / or persistent attribute flags.

[0019] Optionally, the extended intermediate system to intermediate system routing protocol includes a first local area network adjacency segment identifier (Sub-TLV).

[0020] The first LAN adjacency segment identifier Sub-TLV includes a corresponding type field, length field, flag field, adjacency segment, and corresponding value. The flag field corresponding to the first LAN adjacency segment identifier Sub-TLV includes defined managed attribute and / or persistent attribute flags.

[0021] Optionally, the extended intermediate system to intermediate system routing protocol includes a first bundled interface Layer 2 member adjacency segment identifier (Sub-TLV).

[0022] The first bundled port Layer 2 member adjacency segment identifier Sub-TLV includes a corresponding type field, length field, flag field, adjacency segment, and corresponding value. The flag field corresponding to the first bundled port Layer 2 member adjacency segment identifier Sub-TLV includes defined managed attribute and / or persistent attribute flags.

[0023] Optionally, the extended intermediate system to intermediate system routing protocol includes a first bundled interface Layer 2 member LAN adjacency segment identifier (Sub-TLV).

[0024] The first bundled port Layer 2 member LAN adjacency segment identifier Sub-TLV includes a corresponding type field, length field, flag field, adjacency segment, and corresponding value. The flag field corresponding to the first bundled port Layer 2 member LAN adjacency segment identifier Sub-TLV includes defined managed attribute and / or persistent attribute flags.

[0025] Optionally, the extended border gateway link state protocol includes a second adjacency segment identifier (Sub-TLV), which includes a corresponding type field, length field, flag field, adjacency segment, and corresponding value. The flag field corresponding to the second adjacency segment identifier (Sub-TLV) includes defined managed attribute and / or persistent attribute flags.

[0026] or,

[0027] The extended border gateway link state protocol includes a second LAN adjacency segment identifier (Sub-TLV). The second LAN adjacency segment identifier (Sub-TLV) includes a corresponding type field, length field, flag field, adjacency segment, and corresponding value. The flag field corresponding to the second LAN adjacency segment identifier (Sub-TLV) includes defined managed attribute and / or persistent attribute flags.

[0028] or,

[0029] The extended border gateway link state protocol includes a second bundled interface Layer 2 member adjacency segment identifier (Sub-TLV). The second bundled interface Layer 2 member adjacency segment identifier (Sub-TLV) includes a corresponding type field, length field, flag field, adjacency segment, and corresponding value. The flag field corresponding to the second bundled interface Layer 2 member adjacency segment identifier (Sub-TLV) includes defined managed attribute and / or persistent attribute flags.

[0030] or,

[0031] The extended border gateway link state protocol includes a second bundled port Layer 2 member LAN adjacency segment identifier (Sub-TLV). The second bundled port Layer 2 member LAN adjacency segment identifier (Sub-TLV) includes a corresponding type field, length field, flag field, adjacency segment, and corresponding value. The flag field corresponding to the second bundled port Layer 2 member LAN adjacency segment identifier (Sub-TLV) includes defined managed attribute and / or persistent attribute flags.

[0032] Optionally, the extended path computation unit protocol includes a flag field, an adjacency segment, and corresponding values, wherein the flag field corresponding to the extended path computation unit protocol includes defined managed attribute and / or persistent attribute flags.

[0033] Optionally, the allocation attribute includes a managed attribute;

[0034] The step of obtaining the adjacent segment allocated from the SRLB according to the allocation attribute includes:

[0035] When the allocation attribute is a managed attribute, the adjacent segment allocated from the SRLB by the communication device is obtained through the extended border gateway link state protocol or the extended path calculation unit protocol.

[0036] Optionally, the allocation attribute includes a persistent attribute;

[0037] The step of obtaining the adjacent segment allocated from the SRLB according to the allocation attribute includes:

[0038] When the allocation attribute is a persistent attribute, an adjacent segment is allocated from the SRLB;

[0039] After obtaining the adjacent segments allocated from the SRLB based on the allocation attributes, the process further includes:

[0040] The adjacent segments are saved in a configuration file or non-volatile memory.

[0041] Furthermore, to achieve the above objectives, the present invention also proposes an adjacent segment allocation device, the adjacent segment allocation device comprising:

[0042] The acquisition module is used to retrieve the configured SRLB multi-attribute configuration information;

[0043] The acquisition module is also used to determine the allocation attribute of SRLB based on the SRLB multi-attribute configuration information;

[0044] The allocation module is used to obtain the adjacent segments allocated from the SRLB based on the allocation attributes.

[0045] Furthermore, to achieve the above objectives, the present invention also proposes a segment router, the segment router comprising: a memory, a processor, and an adjacency segment allocation program stored in the memory and executable on the processor, the adjacency segment allocation program being configured to implement the adjacency segment allocation method as described above.

[0046] In addition, to achieve the above objectives, the present invention also proposes a storage medium storing an adjacency segment allocation program, which, when executed by a processor, implements the adjacency segment allocation method as described above.

[0047] Furthermore, to achieve the above objectives, the present invention also proposes an adjacent segment allocation method, which is applied to the communication equipment side, and the adjacent segment allocation method includes:

[0048] The segment router is configured with SRLB multi-attribute settings using a preset configuration method, so that the segment router can obtain the configured SRLB multi-attribute settings information.

[0049] The SRLB multi-attribute configuration information configured on the segment router, the adjacent segments allocated by the segment router, and the corresponding managed attributes and / or persistent attributes are obtained through the extended border gateway link state protocol or the extended path calculation unit protocol.

[0050] Optionally, the preset configuration method includes a netconf-based configuration method;

[0051] The step of configuring SRLB multiple attributes on the segment router using a preset configuration method includes:

[0052] SRLB multi-attribute configuration is performed using an extended yang model via netconf, wherein the extended yang model includes SRLB multi-attribute configuration fields.

[0053] Optionally, the preset configuration method includes a configuration method based on an extended path calculation unit protocol;

[0054] The step of configuring SRLB multiple attributes on the segment router using a preset configuration method includes:

[0055] SRLB multi-attribute configuration is performed on segment routers based on the extended path computation unit protocol. The extended path computation unit protocol includes a multi-attribute SRLB TLV, which includes a type field, length field, flag field, reserved field, adjacent segment range, managed attribute and / or persistent attribute flags and their corresponding values.

[0056] Furthermore, to achieve the above objectives, the present invention also proposes a communication device, the communication device comprising: a memory, a processor, and an adjacency segment allocation program stored in the memory and executable on the processor, the adjacency segment allocation program being configured to implement the adjacency segment allocation method as described above.

[0057] The adjacent segment allocation method proposed in this invention obtains the configured SRLB multi-attribute configuration information; determines the allocation attribute of the SRLB based on the SRLB multi-attribute configuration information; and obtains the adjacent segment allocated from the SRLB based on the allocation attribute. In this way, multiple SRLBs with different attributes can be configured on the segment router, thereby avoiding the conflicts that may be caused when the segment router and communication equipment simultaneously allocate adjacent segments from the SRLB. It also solves the problem that when the link using the adjacent segment is interrupted and then restored, the adjacent segment originally allocated from the SRLB becomes unusable due to its variability, which leads to traffic engineering or segment routing policy path unavailability. Attached Figure Description

[0058] Figure 1 This is a schematic diagram of the device structure of the adjacent segment allocation method for the hardware operating environment involved in the embodiments of the present invention;

[0059] Figure 2 This is a flowchart illustrating the first embodiment of the adjacent segment allocation method of the present invention;

[0060] Figure 3 This is a flowchart illustrating the second embodiment of the adjacent segment allocation method of the present invention;

[0061] Figure 4 This is a schematic diagram of the extension of the TLV of a multi-attribute SRLB node based on the BGP-LS protocol in an embodiment of the adjacency segment allocation method of the present invention.

[0062] Figure 5 This is a schematic diagram of a multi-attribute SRLB TLV configuration based on the PCEP protocol according to an embodiment of the adjacency segment allocation method of the present invention;

[0063] Figure 6 This is a schematic diagram illustrating the Sub-TLV extension of multi-attribute SRLB node attributes based on the IS-IS protocol in an embodiment of the adjacency segment allocation method of the present invention.

[0064] Figure 7This is a schematic diagram of the Sub-TLV identifier, which is an adjacency segment identifier, according to an embodiment of the adjacency segment allocation method of the present invention.

[0065] Figure 8 This is a schematic diagram of the Sub-TLV identifier for a local area network (LAN) in an embodiment of the adjacency segment allocation method of the present invention.

[0066] Figure 9 This is a schematic diagram of the identifier Sub-TLV, a second-level member adjacency segment identifier, in an embodiment of the adjacency segment allocation method of the present invention.

[0067] Figure 10 This is a schematic diagram of the Sub-TLV (Sub-TLV) identifier for a Layer 2 Member LAN adjacency segment in a bundled port according to an embodiment of the adjacency segment allocation method of the present invention.

[0068] Figure 11 This is a schematic diagram of the functional modules of the first embodiment of the adjacent segment allocation device of the present invention.

[0069] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0070] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0071] Reference Figure 1 , Figure 1 This is a schematic diagram of the device structure of the hardware operating environment involved in the embodiments of the present invention.

[0072] like Figure 1 As shown, the device may include: a processor 1001, such as a CPU; a communication bus 1002; a user interface 1003; a network interface 1004; and a memory 1005. The communication bus 1002 is used to enable communication between these components. The user interface 1003 may include a display screen and input units such as buttons; optionally, the user interface 1003 may also include a standard wired interface or a wireless interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface). The memory 1005 may be high-speed RAM or stable non-volatile memory, such as a disk drive. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0073] Those skilled in the art will understand that Figure 1 The segment router structure shown does not constitute a limitation on the segment router and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0074] like Figure 1 As shown, the memory 1005, which serves as a storage medium, may include an operating system, a network communication module, a user interface module, and an adjacency segment allocation method program.

[0075] exist Figure 1 In the segment router shown, network interface 1004 is mainly used to connect to the server and communicate with the server; user interface 1003 is mainly used to connect to the user terminal and communicate with the terminal; the segment router of the present invention calls the adjacent segment allocation program stored in memory 1005 through processor 1001 and executes the adjacent segment allocation method provided in the embodiment of the present invention.

[0076] Based on the above hardware structure, an embodiment of the adjacent segment allocation method of the present invention is proposed.

[0077] Reference Figure 2 , Figure 2 This is a flowchart illustrating the first embodiment of the adjacent segment allocation method of the present invention.

[0078] In the first embodiment, the adjacent segment allocation method includes the following steps:

[0079] Step S10: Obtain the configured SRLB multi-attribute configuration information.

[0080] It should be noted that the execution subject of this embodiment can be a segment router, which has an adjacent segment allocation method program. It can also be other devices that can achieve the same or similar functions. This embodiment does not limit this. In this embodiment, a segment router is used as an example for explanation. An adjacent segment allocation application is provided on the segment router, which can allocate segments in SRLB according to the adjacent segment allocation application.

[0081] It is understood that SRLB multi-attribute configuration information includes the configuration of managed attributes and / or persistent attributes, as well as multiple SRLB configurations, and may also include other types of configuration attributes. This embodiment does not impose any restrictions on this. Managed attributes and persistent attributes can be used individually or simultaneously.

[0082] In this embodiment, multiple SRLBs are configured on the segment router through manual configuration, the netconf command, or protocols such as the Path Computation Element Protocol (PCEP). Different SRLBs have different attributes, including but not limited to managed attributes and persistent attributes. When the managed attribute of an SRLB is set, it indicates that the segments in that SRLB are centrally allocated by the communication device, and the segment router cannot allocate segments from the SRLB. The communication device can be a controller, or other forms of network management systems, service provisioning systems, and configuration systems, etc. This embodiment does not impose any restrictions; in this embodiment, a controller is used as an example. When the persistent attribute of an SRLB is set, it indicates that the segments in that SRLB should remain unchanged until deleted or modified. Even if the link is interrupted and then restored, or the device restarts, the segment router should store the segments allocated from the SRLB in a configuration file or non-volatile random access memory (NVRAM) to ensure the persistence and immutability of the segments.

[0083] Step S20: Determine the allocation attributes of SRLB based on the SRLB multi-attribute configuration information.

[0084] In this embodiment, the allocation attribute includes a managed attribute and / or a persistent attribute. When the allocation attribute is a managed attribute, the adjacent segments allocated from the SRLB by the communication device through the Extended Border Gateway Link State Protocol or the Extended Path Calculation Unit Protocol are obtained. When the allocation attribute is a persistent attribute, adjacent segments are allocated from the SRLB and stored in a configuration file or non-volatile memory to ensure the persistence and immutability of the segments. This avoids segment conflicts after link interruption and recovery or device restart, thus achieving network maintenance stability.

[0085] Step S30: Obtain the adjacent segments allocated from the SRLB according to the allocation attributes.

[0086] Understandably, since SRLB has managed and / or persistent attributes, when SRLB is managed, adjacent segments are allocated from SRLB through communication devices, avoiding allocation through segment routers. This avoids potential conflicts that might occur when segment routers and communication devices simultaneously allocate adjacent segments from SRLB. When SRLB is persistent, adjacent segments are allocated from SRLB through segment routers, but these adjacent segments are stored in configuration files or non-volatile memory, thus ensuring the persistence and immutability of segments. By allocating and using segments with persistent attributes, issues such as traffic engineering (TE) or segment routing policy (SRP) path unavailability caused by segment changes due to link interruptions or device restarts can be avoided.

[0087] In this embodiment, by obtaining the configured SRLB multi-attribute configuration information; determining the SRLB allocation attribute based on the SRLB multi-attribute configuration information; and obtaining the adjacent segment allocated from the SRLB based on the allocation attribute, multiple SRLBs with different attributes can be configured on the segment router in the above manner. This avoids the conflicts that may be caused when the segment router and communication equipment simultaneously allocate adjacent segments from the SRLB. It also solves the problem that when the link using the adjacent segment is interrupted and then restored, the adjacent segment originally allocated from the SRLB becomes unavailable due to its variability, which leads to traffic engineering or segment routing policy path unavailability.

[0088] In one embodiment, such as Figure 3 As shown, based on the first embodiment, a second embodiment of the adjacency segment allocation method of the present invention is proposed. After step S10, it further includes:

[0089] Step S101: The SRLB multi-attribute configuration information is reported to the communication device through the extended border gateway link state protocol or the extended path calculation unit protocol.

[0090] In this embodiment, the communication device can be a controller or other types of devices. This embodiment does not limit the type of device. In this embodiment, the controller is used as an example for explanation. After configuring the segment router with multiple attributes of SRLB, the segment router will report the configuration information to the controller. Specifically, the SRLB multiple attribute configuration information is reported to the communication device through the extended border gateway link state protocol or the extended path calculation unit protocol. The extended border gateway link state protocol includes the multi-attribute SRLB node attribute TLV, wherein the multi-attribute SRLB node attribute TLV includes the corresponding type field, length field, flag field, reserved field, adjacent segment range, managed attribute and / or persistent attribute flag bits and corresponding values.

[0091] In this embodiment, after multiple SRLBs with different attributes are configured on the segment router, they can be obtained by systems or devices such as controllers through methods such as BGP-LS extension. The controllers or devices can then use SRLBs with different attributes as needed. Optionally, one BGP-LS extension method is to introduce a multi-attribute SRLB node attribute TLV. Optionally, the multi-attribute SRLB node attribute TLV introduces attribute fields for each SRLB based on the SRLB TLV defined in the BGP-LS segment routing extension protocol, while the meanings of other fields remain unchanged. The Type field is used to identify that the TLV is a multi-attribute SRLB node attribute TLV, and the specific value is allocated by the corresponding international standardization organization during standardization. The Length field is used to identify the total number of bytes in the TLV. The D bit corresponds to managed attributes, the P bit corresponds to persistent attributes, and reserved is a reserved field, such as... Figure 4 The diagram shows the extension of the attribute TLV of a multi-attribute SRLB node based on the BGP-LS protocol.

[0092] The extended path computation unit protocol includes a multi-attribute SRLB TLV, wherein the multi-attribute SRLB TLV includes a corresponding type field, length field, flag field, reserved field, adjacent segment range, managed attribute and / or persistent attribute flags and corresponding values.

[0093] Define a multi-attribute SRLB TLV (Type length value), which can be optionally carried in the PCEP OPEN object. It is used by the PCE (Path Computation Element) (the controller, etc. can also act as the PCE) to configure different attributes of SRLB to the PCC (Path Computation Client) path calculation client (segment routers, etc. can implement PCC functions), and can also be used by the PCC to report different attributes of SRLB configured on the segment router to the PCE.

[0094] The Type field identifies this TLV as an SRLB configuration TLV, and its specific value is assigned by the relevant international standardization organization during standardization. The Length field indicates the total number of bytes in this TLV, excluding the length of the Type and Length fields. Each SRLB in the SRLB configuration TLV consists of 12 bytes, with D bits corresponding to managed attributes, P bits corresponding to persistent attributes, Start being the starting segment of the SRLB, range being the range of the SRLB, and reserved being a reserved field.

[0095] When a controller or other system or device needs to centrally allocate and configure segments in an SRLB, the above method can be used to configure one or more SRLBs with managed attributes set on the segment router, and then allocate and configure segments from the configured SRLB, thereby avoiding conflicts with the segment router dynamically allocating segments from the SRLB.

[0096] When it is necessary to allocate and use segments with persistent attributes from SRLBs, the segment router can be configured with one or more SRLBs whose persistent attributes are set using the method described above. Then, segments can be allocated and configured from the configured SRLBs. This avoids problems such as traffic engineering issues or unavailable segment routing policy paths caused by segment changes due to link interruptions or segment router restarts. Figure 5 The diagram shows a multi-attribute SRLBTLV configuration based on the PCEP protocol.

[0097] Step S102: The SRLB multi-attribute configuration information is advertised to other network elements through an extended intermediate system-to-intermediate system routing protocol or an extended open shortest path first protocol.

[0098] The extended intermediate system to intermediate system routing protocol includes a multi-attribute SRLB Sub-TLV, wherein the multi-attribute SRLB Sub-TLV includes a corresponding type field, length field, flag field, reserved field, adjacency range, managed attribute and / or persistent attribute flags and their corresponding values.

[0099] In this embodiment, a segment router configured with multiple SRLBs of different attributes can advertise these SRLBs to other network elements (including segment routers and controllers) through extended routing protocols such as ISIS and OSPF. Optionally, one ISIS extension method is as follows: the SRLB Sub-TLV defined in RFC8667 is extended to a multi-attribute SRLB Sub-TLV. The Type field is used to identify that the TLV is a multi-attribute SRLB Sub-TLV; the specific value is assigned by the corresponding international standardization organization during standardization. The Length field is used to identify the total number of bytes in the TLV. The D bit corresponds to the managed attribute, the P bit corresponds to the persistent attribute, and reserved is a reserved field. The definitions of other fields are the same as those of the SRLB Sub-TLV defined in RFC8667, such as... Figure 6The diagram illustrates the Sub-TLV extension of a multi-attribute SRLB node based on the IS-IS protocol. Referring to the IS-IS extension method, a similar extension can be performed on OSPF according to the OSPF protocol specifications. The specific extension method is similar to that of the IS-IS protocol, adding multi-attribute configuration information to the OSPF protocol to extend it. This involves announcing the multi-attribute configuration information configured on the segment router, or defining managed attribute and / or persistent attribute flags in the OSPF protocol to enable other network elements to obtain the adjacent segments allocated on the segment router and their corresponding managed and / or persistent attributes.

[0100] In one embodiment, after step S30, the method further includes:

[0101] The adjacent segments allocated from the SRLB, along with their corresponding managed and / or persistent attributes, are advertised to other network elements via an extended intermediate system-to-intermediate system routing protocol or an extended open shortest path first protocol, so that these other network elements can obtain the adjacent segments allocated from the SRLB and their corresponding managed and / or persistent attributes; and

[0102] In this embodiment, other network elements can be controllers or segment routers. Taking a segment router as an example, after configuring SRLB multi-attribute configuration information, the segment router allocates adjacent segments from the SRLB and performs self-learning with other routers through the extended intermediate system to intermediate system routing protocol or the extended open shortest path first protocol. The controller can obtain the adjacent segment learning results of the segment router through the extended border gateway link state protocol or the extended path calculation unit protocol, and perform traffic engineering or segment routing policy path programming based on the learning results to control traffic forwarding. The adjacent segment is the value of the allocated adjacent segment, i.e., SID (segment identity).

[0103] It should be noted that the path calculation element protocol is PCEP (Path Computation Element Communication Protocol), the border gateway link-state protocol is BGP-LS (Border Gateway Protocol Link-state), the intermediate system to intermediate system routing protocol is IS-IS (Intermediate System to Intermediate System), and the open shortest path first protocol is OSPF (Open Shortest Path First).

[0104] The extended intermediate system to intermediate system routing protocol includes a first adjacency segment identifier (Sub-TLV); the first adjacency segment identifier (Sub-TLV) includes a corresponding type field, length field, flag field, adjacency segment, and corresponding value, wherein the flag field corresponding to the first adjacency segment identifier (Sub-TLV) includes defined managed attribute and / or persistent attribute flags.

[0105] In this embodiment, segment routers configured with multiple SRLBs of different attributes can advertise segments allocated from different SRLBs to other network elements, including segment routers and controllers, through extended routing protocols such as ISIS and OSPF. Optionally, one ISIS extension method is as follows: a new managed bit D is defined in the Adjacency Segment Identifier (Adj-SID) Sub-TLV defined in RFC8667. The D bit corresponds to the managed attribute, the P bit already defined in Flags corresponds to the persistent attribute, and the definitions of other fields are the same as those in the Adj-SID Sub-TLV in RFC8667. A segment with the managed bit D set can only be allocated from an SRLB with the managed bit D set, and a segment with the persistent bit P set can be allocated from an SRLB with the managed bit P set, such as... Figure 7 The diagram shows the identifier of the adjacent segment identifier Sub-TLV.

[0106] Another embodiment is provided, wherein the extended intermediate system to intermediate system routing protocol includes a first LAN adjacency segment identifier (Sub-TLV). The first LAN adjacency segment identifier (Sub-TLV) includes a corresponding type field, length field, flag field, adjacency segment, and corresponding value. The flag field corresponding to the first LAN adjacency segment identifier (Sub-TLV) includes defined managed attribute and / or persistent attribute flags. Specifically, a new managed bit (D) is defined in the LAN-Adj-SID Sub-TLV defined in RFC8667. The D bit corresponds to the managed attribute, and the P bit, already defined in Flags, corresponds to the persistent attribute. The definitions of other fields are the same as those in the LAN-Adj-SID Sub-TLV of RFC8667. A segment with the managed bit D set can only be allocated from an SRLB with the managed bit D set, and a segment with the persistent bit P set is allocated from an SRLB with the managed bit P set. Figure 8 The diagram shows the identifier of the Sub-TLV (Local Area Network Adjacency Segment Identifier).

[0107] In another embodiment, the extended intermediate system to intermediate system routing protocol includes a first bundled interface Layer 2 member adjacency segment identifier (Sub-TLV); the first bundled interface Layer 2 member adjacency segment identifier (Sub-TLV) includes a corresponding type field, length field, flag field, adjacency segment, and corresponding value, wherein the flag field corresponding to the first bundled interface Layer 2 member adjacency segment identifier (Sub-TLV) includes defined managed attribute and / or persistent attribute flags.

[0108] In another embodiment, the extended intermediate system to intermediate system routing protocol includes a first bundled interface Layer 2 member LAN adjacency segment identifier (Sub-TLV); the first bundled interface Layer 2 member LAN adjacency segment identifier (Sub-TLV) includes a corresponding type field, length field, flag field, adjacency segment, and corresponding value, wherein the flag field corresponding to the first bundled interface Layer 2 member LAN adjacency segment identifier (Sub-TLV) includes defined managed attribute and / or persistent attribute flags.

[0109] Similarly, a new managed bit D can be defined in both the L2 Bundle MemberAdjacency Segment Identifier Sub-TLV and the L2 Bundle Member LAN Adjacency SID Sub-TLV defined in RFC8668. This allows segments allocated to bundled interface Layer 2 member links to also carry managed attributes via ISIS. The D bit corresponds to the managed attribute, the P bit already defined in Flags corresponds to the persistent attribute, and the definitions of other fields are the same as those in the corresponding Sub-TLVs in RFC8668. Segments with the managed bit D set can only be allocated from SRLBs with the managed bit D set, and segments with the persistent bit P set are recommended to be allocated from SRLBs with the managed bit P set. Figure 9 The diagram shows the identifier of the Sub-TLV, a second-level member adjacency segment identifier of the bundled port, and as shown below. Figure 10 The diagram shows the identifier of the Sub-TLV, a Layer 2 member LAN adjacency segment identifier for the bundled port.

[0110] In this embodiment, the segment router also reports the adjacent segments allocated from the SRLB and their corresponding managed attributes and / or persistent attributes to the communication device via an extended border gateway link-state protocol or an extended path computation unit protocol, so that the communication device can obtain the adjacent segments and their corresponding managed attributes and / or persistent attributes according to the extended border gateway link-state protocol or the extended path computation unit protocol.

[0111] The extended border gateway link state protocol includes a second adjacency segment identifier (Sub-TLV), which includes a type field, a length field, a flag field, an adjacency segment, and a corresponding value. The flag field of the second adjacency segment identifier (Sub-TLV) includes defined managed attribute and / or persistent attribute flags. Alternatively, the extended border gateway link state protocol includes a second local area network (LAN) adjacency segment identifier (Sub-TLV), which includes a type field, a length field, a flag field, an adjacency segment, and a corresponding value. The flag field of the second LAN adjacency segment identifier (Sub-TLV) includes defined managed attribute and / or persistent attribute flags. Alternatively, the extended border gateway link state protocol includes a second bundle... The second bound port Layer 2 member adjacency segment identifier Sub-TLV includes a corresponding type field, length field, flag field, adjacency segment, and corresponding value. The flag field of the second bound port Layer 2 member adjacency segment identifier Sub-TLV includes defined managed attribute and / or persistent attribute flags. Alternatively, the extended border gateway link state protocol includes a second bound port Layer 2 member LAN adjacency segment identifier Sub-TLV, which includes a corresponding type field, length field, flag field, adjacency segment, and corresponding value. The flag field of the second bound port Layer 2 member LAN adjacency segment identifier Sub-TLV includes defined managed attribute and / or persistent attribute flags.

[0112] It should be noted that the Adjacency SID TLV, LAN Adjacency SID TLV, and L2 Bundle Member Attribute TLV in the BGP-LS protocol have also been extended. New managed bits (D) and managed attributes are defined in the corresponding Flags, while the P bits already defined in the Flags correspond to persistent attributes. This allows segments configured on segment routers with different attributes to be obtained by network elements such as controllers or systems through the extended BGP-LS protocol. Furthermore, network elements such as controllers or systems can use segments with different attributes for path programming according to the needs of different services. For example, segments with persistent attributes can be used for TE path orchestration. This way, when a link experiences a brief interruption in the path, the traffic engineering or segment routing policy path can immediately forward traffic after the link is restored, without the traffic engineering or segment routing policy path becoming unavailable due to changes in the labels on the corresponding links.

[0113] In another embodiment, the extended path computation unit protocol includes a flag field, an adjacency segment, and corresponding values, wherein the flag field corresponding to the extended path computation unit protocol includes defined managed attribute and / or persistent attribute flags.

[0114] The PCEP protocol can also be extended similarly by introducing a managed bit (D) to correspond to managed attributes and a persistent bit (P) to correspond to persistent attributes. This allows segments configured on segment routers with different attributes to be obtained by network elements such as controllers or systems through the extended PCEP protocol. Furthermore, network elements such as controllers or systems can use segments with different attributes for path programming according to the needs of different services. For example, segments with persistent attributes can be used for traffic engineering or segment routing policy path orchestration. In this way, if a link in the path experiences a brief interruption, the traffic engineering or segment routing policy path can immediately forward traffic after the link is restored, without becoming unusable due to changes in the labels on the corresponding links.

[0115] The present invention further provides an adjacent segment allocation device.

[0116] Reference Figure 11 , Figure 11 This is a schematic diagram of the functional modules of the first embodiment of the adjacent segment allocation device of the present invention.

[0117] In a first embodiment of the adjacent segment allocation device of the present invention, the adjacent segment allocation device includes:

[0118] Module 10 is used to obtain the configured SRLB multi-attribute configuration information.

[0119] It is understood that SRLB multi-attribute configuration information includes the configuration of managed attributes and / or persistent attributes, and may also include other types of configuration attributes. This embodiment does not impose any restrictions on this. Managed attributes and persistent attributes can be used individually or simultaneously.

[0120] In this embodiment, multiple SRLBs are configured on the segment router through manual configuration, the netconf command, or protocols such as the Path Computing Unit Protocol (PCEP). Different SRLBs have different attributes, including but not limited to managed and persistent attributes. When the managed attribute of an SRLB is set, it indicates that the segments in that SRLB are centrally allocated by the communication device, and the segment router cannot allocate segments from the SRLB. The communication device can be a controller or other types of gateway devices; this embodiment does not impose any restrictions, and a controller is used as an example in this description. When the persistent attribute of an SRLB is set, it indicates that the segments in that SRLB should remain unchanged until deleted or modified. Even if the link is interrupted and then restored, or the device restarts, the segment router should store the segments allocated from the SRLB in a configuration file or non-volatile memory (NVRAM) to ensure the persistence of the segments.

[0121] The acquisition module 10 is also used to determine the allocation attribute of SRLB based on the SRLB multi-attribute configuration information.

[0122] In this embodiment, the allocation attribute includes a managed attribute and / or a persistent attribute. When the allocation attribute is a managed attribute, the adjacent segments allocated from the SRLB by the communication device through the extended border gateway link state protocol or the extended path calculation unit protocol are obtained. When the allocation attribute is a persistent attribute, the adjacent segments are allocated from the SRLB through the segment router, and the adjacent segments are saved in the configuration file or non-volatile memory to ensure the persistence and immutability of the segments, thereby avoiding segment conflicts after link interruption and recovery or device restart, and achieving network maintenance stability.

[0123] The allocation module 20 is used to obtain the adjacent segments allocated from the SRLB according to the allocation attributes.

[0124] Understandably, since SRLB has managed and / or persistent attributes, when SRLB is managed, adjacent segments are allocated from SRLB through communication devices, avoiding allocation through segment routers. This avoids potential conflicts that might occur when segment routers and communication devices simultaneously allocate adjacent segments from SRLB. When SRLB is persistent, adjacent segments are allocated from SRLB through segment routers, but these adjacent segments are stored in configuration files or non-volatile memory, thus ensuring the persistence and immutability of segments. By allocating and using segments with persistent attributes, issues such as traffic engineering (TE) or segment routing policy (SRP) path unavailability caused by segment changes due to link interruptions or device restarts can be avoided.

[0125] In this embodiment, by obtaining the configured SRLB multi-attribute configuration information; determining the SRLB allocation attribute based on the SRLB multi-attribute configuration information; and obtaining the adjacent segment allocated from the SRLB based on the allocation attribute, multiple SRLBs with different attributes can be configured on the segment router in the above manner. This avoids the conflicts that may be caused when the segment router and communication equipment simultaneously allocate segments from the SRLB. It also solves the problem that when a link using adjacent segments is interrupted and then restored, the adjacent segments originally allocated from the SRLB may become unavailable due to their variability, leading to traffic engineering or segment routing policy path unavailability.

[0126] Furthermore, to achieve the above objectives, the present invention also proposes a segment router, the segment router comprising: a memory, a processor, and an adjacency segment allocation program stored in the memory and executable on the processor, the adjacency segment allocation program being configured to implement the adjacency segment allocation method as described above.

[0127] Furthermore, this embodiment of the invention also proposes a storage medium storing an adjacency segment allocation program, which, when executed by a processor, implements the adjacency segment allocation method as described above.

[0128] Since this storage medium adopts all the technical solutions of all the above embodiments, it has at least all the beneficial effects brought about by the technical solutions of the above embodiments, which will not be repeated here.

[0129] Furthermore, to achieve the above objectives, the present invention also proposes an adjacent segment allocation method, which is applied to the communication equipment side and includes the following steps:

[0130] The segment router is configured with SRLB multi-attribute configuration through a preset configuration method, so that the segment router can obtain the configured SRLB multi-attribute configuration information, determine the SRLB allocation attribute according to the SRLB multi-attribute configuration information, obtain the adjacent segment allocated from the SRLB according to the allocation attribute, and obtain the SRLB multi-attribute configuration information configured on the segment router, the adjacent segment allocated by the segment router, and the corresponding managed attribute and / or persistent attribute through the extended border gateway link state protocol or the extended path calculation unit protocol.

[0131] It should be noted that the execution subject of this embodiment can be a communication device. In this embodiment, a communication device is used as an example for explanation. The communication device is equipped with an adjacency segment allocation application, which can obtain adjacency segments in SRLB according to the adjacency segment allocation application. In this embodiment, the communication device is used as a controller for explanation.

[0132] It is understood that SRLB multi-attribute configuration information includes the configuration of managed attributes and / or persistent attributes, and may also include other types of configuration attributes. This embodiment does not impose any restrictions on this. Managed attributes and persistent attributes can be used individually or simultaneously. Multi-attribute configuration information is configured on the segment router. The controller communication device or other network element's extensible border gateway link-state protocol or extended path calculation unit protocol obtains the SRLB multi-attribute configuration information configured on the segment router. The specific implementation of the extended border gateway link-state protocol or extended path calculation unit protocol is as described above, and will not be repeated here.

[0133] In this embodiment, the communication device obtains the SRLB multi-attribute configuration information configured on the segment router through the extended border gateway link state protocol or the extended path calculation unit protocol. In this way, when multiple SRLBs with different attributes are configured on the segment router, the conflicts that may be caused when the segment router and the communication device simultaneously allocate adjacent segments from the SRLB can be avoided. It also solves the problem that when the link using the adjacent segment is interrupted and then restored, the adjacent segments originally allocated from the SRLB are unavailable due to their variability, which leads to traffic engineering or segment routing policy paths.

[0134] The preset configuration methods include those based on netconf;

[0135] The step of configuring SRLB multiple attributes on the segment router using a preset configuration method includes:

[0136] SRLB multi-attribute configuration is performed using an extended yang model via netconf, wherein the extended yang model includes SRLB multi-attribute configuration fields.

[0137] For example, a multi-attribute SRLB configuration yang model can be defined, and then the configuration and reading of multi-attribute SRLBs on segment routers can be achieved through netconf.

[0138] +--rw srlb-list[index]

[0139] +--rw index uint8

[0140] +--rw start uint32

[0141] +--rw range uint32

[0142] +--rw delegate boolean

[0143] +--rw persistence boolean

[0144] `start` specifies the starting segment of the SRLB, `range` specifies the range of the SRLB, `delegate` corresponds to the managed attribute, and `persistence` corresponds to the persistent attribute. `srlb-list` is a list type, which allows configuring multiple SRLBs with different attributes on the segment router.

[0145] Another configuration method is provided, the preset configuration method including a configuration method based on the extended path calculation unit protocol;

[0146] The step of configuring SRLB multiple attributes on the segment router through a preset configuration method includes: configuring SRLB multiple attributes on the segment router based on the extended path computation unit protocol, wherein the extended path computation unit protocol includes a multi-attribute SRLB TLV, and the multi-attribute SRLB TLV includes a corresponding type field, length field, flag field, reserved field, adjacent segment range, managed attribute and / or persistent attribute flags and corresponding values.

[0147] In this embodiment, the path computation unit protocol is based on the PCEP protocol. For example, a multi-attribute SRLB TLV (Type length value) is defined. This multi-attribute SRLB TLV is carried in the PCEP OPEN object and is used by the PCE (Path Computation Element). Controllers can also function as PCEs, and segment routers can implement PCC functions, configuring SRLBs with different attributes. It can also be used by the PCC to report SRLBs with different attributes configured on the segment router to the PCE. Figure 5 The diagram shows a multi-attribute SRLB TLV configuration based on the PCEP protocol.

[0148] The Type field is used to identify that this TLV is an SRLB configuration TLV. The specific value is assigned by the corresponding international standardization organization during standardization. The Length field is used to identify how many bytes this TLV has in total, excluding the length of the Type and Length fields. Each SRLB in the SRLB configuration TLV consists of 12 bytes. The D bit corresponds to the managed attribute, the P bit corresponds to the persistent attribute, Start is the starting segment of the SRLB, range is the range of the SRLB, that is, the range of adjacent segments, and reserved is a reserved field.

[0149] When a controller or other system or device needs to centrally allocate and configure segments in an SRLB, it can configure one or more SRLBs with managed attributes set on the segment router using the Path Computing Unit Protocol configuration method. Then, it can allocate and configure segments from the configured SRLB, thereby avoiding conflicts with the segment router dynamically allocating segments from the SRLB.

[0150] When it is necessary to allocate and use segments with persistent attributes from SRLB, one or more SRLBs with persistent attributes can be configured for the segment router using the Path Computing Unit Protocol configuration method. Then, segments can be allocated and configured from the configured SRLBs. This avoids problems such as traffic engineering or unavailable segment routing policy paths caused by changes in segments allocated from SRLB due to link interruptions or segment router restarts.

[0151] Furthermore, to achieve the above objectives, the present invention also proposes a communication device, the communication device comprising: a memory, a processor, and an adjacency segment allocation program stored in the memory and executable on the processor, the adjacency segment allocation program being configured to implement the adjacency segment allocation method as described above.

[0152] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0153] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0154] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a computer-readable storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a smart terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0155] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

Claims

1. A method for allocating adjacent segments, characterized in that, The adjacent segment allocation method is applied to the segment router side, and the adjacent segment allocation method includes: Retrieve the configured SRLB multi-attribute configuration information; The allocation attributes of the SRLB are determined based on the SRLB multi-attribute configuration information, wherein the allocation attributes include managed attributes and persistent attributes; The adjacent segment allocated from the SRLB is obtained according to the allocation attribute, wherein, when the allocation attribute is a managed attribute, the adjacent segment allocated from the SRLB by the communication device is obtained; when the allocation attribute is a persistent attribute, the adjacent segment is allocated from the SRLB through the segment router, and the adjacent segment is stored in a configuration file or non-volatile memory. After obtaining the configured SRLB multi-attribute configuration information, the method further includes: reporting the SRLB multi-attribute configuration information to the communication device, or the communication device obtaining the SRLB multi-attribute configuration information.

2. The adjacent segment allocation method as described in claim 1, characterized in that, After obtaining the configured SRLB multi-attribute configuration information, the process also includes: The SRLB multi-attribute configuration information is reported to the communication device via an extended border gateway link-state protocol or an extended path calculation unit protocol; and The SRLB multi-attribute configuration information is advertised to other network elements through an extended intermediate system-to-intermediate system routing protocol or an extended open shortest path first protocol.

3. The adjacent segment allocation method as described in claim 2, characterized in that, The extended border gateway link state protocol includes a multi-attribute SRLB node attribute TLV, wherein the multi-attribute SRLB node attribute TLV includes a corresponding type field, length field, flag field, reserved field, adjacency range, managed attribute and / or persistent attribute flags and corresponding values.

4. The adjacent segment allocation method as described in claim 2, characterized in that, The extended path computation unit protocol includes a multi-attribute SRLB TLV, wherein the multi-attribute SRLB TLV includes a corresponding type field, length field, flag field, reserved field, adjacent segment range, managed attribute and / or persistent attribute flags and corresponding values.

5. The adjacent segment allocation method as described in claim 2, characterized in that, The extended intermediate system to intermediate system routing protocol includes a multi-attribute SRLB Sub-TLV, wherein the multi-attribute SRLB Sub-TLV includes a corresponding type field, length field, flag field, reserved field, adjacency range, managed attribute and / or persistent attribute flags and their corresponding values.

6. The adjacent segment allocation method as described in claim 1, characterized in that, After obtaining the adjacent segments allocated from the SRLB based on the allocation attributes, the process further includes: The adjacent segments allocated from the SRLB, along with their corresponding managed and / or persistent attributes, are advertised to other network elements via an extended intermediate system-to-intermediate system routing protocol or an extended open shortest path first protocol, so that these other network elements can obtain the adjacent segments allocated from the SRLB and their corresponding managed and / or persistent attributes; and The extended border gateway link state protocol or the extended path computation unit protocol reports the adjacent segments allocated from the SRLB and their corresponding managed attributes and / or persistent attributes to the communication device, so that the communication device can obtain the adjacent segments and their corresponding managed attributes and / or persistent attributes according to the extended border gateway link state protocol or the extended path computation unit protocol.

7. The adjacent segment allocation method as described in claim 6, characterized in that, The extended intermediate system to intermediate system routing protocol includes a first adjacency segment identifier (Sub-TLV). The first adjacency segment identifier Sub-TLV includes a corresponding type field, length field, flag field, adjacency segment, and corresponding value. The flag field corresponding to the first adjacency segment identifier Sub-TLV includes defined managed attribute and / or persistent attribute flags.

8. The adjacent segment allocation method as described in claim 6, characterized in that, The extended intermediate system to intermediate system routing protocol includes a first local area network adjacency segment identifier (Sub-TLV). The first LAN adjacency segment identifier Sub-TLV includes a corresponding type field, length field, flag field, adjacency segment, and corresponding value. The flag field corresponding to the first LAN adjacency segment identifier Sub-TLV includes defined managed attribute and / or persistent attribute flags.

9. The adjacent segment allocation method as described in claim 6, characterized in that, The extended intermediate system to intermediate system routing protocol includes a first bundled interface Layer 2 member adjacency segment identifier (Sub-TLV). The first bundled port Layer 2 member adjacency segment identifier Sub-TLV includes a corresponding type field, length field, flag field, adjacency segment, and corresponding value. The flag field corresponding to the first bundled port Layer 2 member adjacency segment identifier Sub-TLV includes defined managed attribute and / or persistent attribute flags.

10. The adjacent segment allocation method as described in claim 6, characterized in that, The extended intermediate system to intermediate system routing protocol includes a first bundled interface Layer 2 member LAN adjacency segment identifier (Sub-TLV). The first bundled port Layer 2 member LAN adjacency segment identifier Sub-TLV includes a corresponding type field, length field, flag field, adjacency segment, and corresponding value. The flag field corresponding to the first bundled port Layer 2 member LAN adjacency segment identifier Sub-TLV includes defined managed attribute and / or persistent attribute flags.

11. The adjacent segment allocation method as described in claim 6, characterized in that, The extended border gateway link state protocol includes a second adjacency segment identifier (Sub-TLV). The second adjacency segment identifier (Sub-TLV) includes a corresponding type field, length field, flag field, adjacency segment, and corresponding value. The flag field corresponding to the second adjacency segment identifier (Sub-TLV) includes defined managed attribute and / or persistent attribute flags. or, The extended border gateway link state protocol includes a second LAN adjacency segment identifier (Sub-TLV). The second LAN adjacency segment identifier (Sub-TLV) includes a corresponding type field, length field, flag field, adjacency segment, and corresponding value. The flag field corresponding to the second LAN adjacency segment identifier (Sub-TLV) includes defined managed attribute and / or persistent attribute flags. or, The extended border gateway link state protocol includes a second bundled interface Layer 2 member adjacency segment identifier (Sub-TLV). The second bundled interface Layer 2 member adjacency segment identifier (Sub-TLV) includes a corresponding type field, length field, flag field, adjacency segment, and corresponding value. The flag field corresponding to the second bundled interface Layer 2 member adjacency segment identifier (Sub-TLV) includes defined managed attribute and / or persistent attribute flags. or, The extended border gateway link state protocol includes a second bundled port Layer 2 member LAN adjacency segment identifier (Sub-TLV). The second bundled port Layer 2 member LAN adjacency segment identifier (Sub-TLV) includes a corresponding type field, length field, flag field, adjacency segment, and corresponding value. The flag field corresponding to the second bundled port Layer 2 member LAN adjacency segment identifier (Sub-TLV) includes defined managed attribute and / or persistent attribute flags.

12. The adjacent segment allocation method as described in claim 6, characterized in that, The extended path computation unit protocol includes a flag field, an adjacency segment, and corresponding values, wherein the flag field corresponding to the extended path computation unit protocol includes defined managed attribute and / or persistent attribute flags.

13. The adjacent segment allocation method according to any one of claims 1 to 12, characterized in that, The step of obtaining the adjacent segment allocated from the SRLB according to the allocation attribute includes: When the allocation attribute is a managed attribute, the adjacent segment allocated from the SRLB by the communication device is obtained through the extended border gateway link state protocol or the extended path calculation unit protocol.

14. The adjacent segment allocation method according to any one of claims 1 to 12, characterized in that, The step of obtaining the adjacent segment allocated from the SRLB according to the allocation attribute includes: When the allocation attribute is a persistent attribute, an adjacent segment is allocated from the SRLB; After obtaining the adjacent segments allocated from the SRLB based on the allocation attributes, the process further includes: The adjacent segments are saved in a configuration file or non-volatile memory.

15. An adjacent segment allocation device, characterized in that, The adjacent segment allocation device includes: The acquisition module is used to retrieve the configured SRLB multi-attribute configuration information; The acquisition module is further configured to determine the allocation attributes of the SRLB based on the SRLB multi-attribute configuration information, wherein the allocation attributes include managed attributes and persistent attributes; An allocation module is configured to obtain adjacent segments allocated from the SRLB based on the allocation attribute, wherein, when the allocation attribute is a managed attribute, the module obtains the adjacent segments allocated by the communication device from the SRLB; when the allocation attribute is a persistent attribute, the module allocates the adjacent segments from the SRLB through a segment router and stores the adjacent segments in a configuration file or non-volatile memory. After obtaining the configured SRLB multi-attribute configuration information, the method further includes: reporting the SRLB multi-attribute configuration information to the communication device, or the communication device obtaining the SRLB multi-attribute configuration information.

16. A segment router, characterized in that, The segment router includes: a memory, a processor, and an adjacency segment allocation program stored in the memory and executable on the processor, the segment router being configured to implement the adjacency segment allocation method as described in any one of claims 1 to 14.

17. A storage medium, characterized in that, The storage medium stores an adjacency segment allocation program, which, when executed by a processor, implements the adjacency segment allocation method as described in any one of claims 1 to 14.

18. A method for allocating adjacent segments, characterized in that, The adjacent segment allocation method is applied to the communication equipment side, and the adjacent segment allocation method includes: The segment router is configured with multiple SRLB attributes using a preset configuration method, so that the segment router can obtain the configured SRLB multiple attribute configuration information; when the allocation attribute of the SRLB is determined to be a managed attribute according to the SRLB multiple attribute configuration information, the adjacent segment is allocated from the SRLB through the communication device; when the allocation attribute is a persistent attribute, the adjacent segment is allocated from the SRLB through the segment router, and the adjacent segment is stored in a configuration file or non-volatile memory; The SRLB multi-attribute configuration information configured on the segment router, the adjacent segments allocated by the segment router, and the corresponding managed attributes and / or persistent attributes are obtained through the extended border gateway link state protocol or the extended path calculation unit protocol.

19. The adjacent segment allocation method as described in claim 18, characterized in that, The preset configuration methods include those based on netconf; The step of configuring SRLB multiple attributes on the segment router using a preset configuration method includes: SRLB multi-attribute configuration is performed using an extended yang model via netconf, wherein the extended yang model includes SRLB multi-attribute configuration fields.

20. The adjacent segment allocation method as described in claim 18, characterized in that, The preset configuration method includes a configuration method based on the extended path calculation unit protocol; The step of configuring SRLB multiple attributes on the segment router using a preset configuration method includes: SRLB multi-attribute configuration is performed on segment routers based on the extended path computation unit protocol. The extended path computation unit protocol includes a multi-attribute SRLB TLV, which includes a type field, length field, flag field, reserved field, adjacent segment range, managed attribute and / or persistent attribute flags and their corresponding values.

21. A communication device, characterized in that, The communication device includes: a memory, a processor, and an adjacency segment allocation program stored in the memory and executable on the processor, the communication device being configured to implement the adjacency segment allocation method as described in any one of claims 18-20.

Images