WO2020134739A1

WO2020134739A1 - Method and device for configuring seamless bidirectional forwarding detection (sbfd) mechanism

Info

Publication number: WO2020134739A1
Application number: PCT/CN2019/119825
Authority: WO
Inventors: 邰博; 吕金生; 王丽娜; 王海波; 胡志波
Original assignee: 华为技术有限公司
Priority date: 2018-12-28
Filing date: 2019-11-21
Publication date: 2020-07-02
Also published as: CN109587009B; CN111385165A; CN111385165B; CN109587009A

Abstract

The present invention provides a method and device for configuring a seamless bidirectional forwarding detection (SBFD) mechanism. An SBFD mechanism is configured for a forwarding node by means of a controller, dynamic configuration of the SBFD mechanism is achieved, and protection is provided for a tunnel. The method comprises: the controller determines SBFD configuration information according to a SBFD mechanism configuration status of a first forwarding node in a plurality of forwarding nodes, the SBFD configuration information comprising information required for configuring a SBFD instance related to a segment routing (SR) service; and the controller sends to the first forwarding node a border gateway protocol (BGP) message, the BGP message carrying the SBFD configuration information therein.

Description

Method and device for configuring seamless two-way forwarding detection SBFD mechanism

This application requires the priority of the Chinese patent application submitted to the State Intellectual Property Office of China on December 28, 2018, with the application number 201811626536.9 and the application name as "Method and Device for Configuring Seamless Two-Way Forwarding Detection SBFD Mechanism", all of its content Incorporated by reference in this application.

Technical field

The present application relates to the computer field, and more specifically, to a method and apparatus for configuring a seamless two-way forwarding detection SBFD mechanism.

Background technique

Segment routing (SR) is a protocol designed to forward data packets on the network based on the concept of source routing. SR multi-protocol label switching (multi-protocol label switch, MPLS) refers to Segment Routing based on the MPLS forwarding plane. Segment routing-traffic engineering (SR-TE) is a new type of TE tunneling technology that uses SR as a control protocol. SR-TE refers to the tunnel based on the constraint attribute of TE and created by SR protocol. The controller is responsible for calculating the forwarding path of the tunnel and delivering the label stack corresponding to the path to the repeater. On the ingress node of the SR-TE tunnel, the repeater can control the transmission path of the packet in the network according to the label stack.

Since SR-TE has no protocol establishment, as long as the label stack is delivered, a link-state packet (LSP) will be established successfully, and except for the cancellation of the label stack, the LSP will not have a protocol Down situation. Therefore, SR-TE LSP failure detection needs to rely on the deployment of bidirectional forwarding detection (bidirectional forwarding detection, BFD) detection, and switch back-up LSPs through BFD failure detection. Seamless bidirectional forwarding detection (seamless BFD, SBFD) simplifies the BFD state machine, shortens the negotiation time, improves the flexibility of the entire network, and can support SR tunnel detection. Currently, SBFD is used to provide protection for SR policy (Policy) services. However, SBFD currently only supports static configuration on transponders. By statically configuring SBFD instances and parameters to provide end-to-end fault detection for the SR Policy tunnel that has been created, it cannot provide tunnel protection in a timely and dynamic manner.

Summary of the invention

In view of this, the present application provides a method and device for configuring a seamless two-way forwarding detection SBFD mechanism, which can realize the dynamic deployment of SBFD and help to provide timely tunnel protection.

In a first aspect, a method for configuring a seamless two-way forwarding detection SBFD mechanism is provided. The method is applied to a network that supports segmented routing traffic engineering SR-TE. The network includes a controller and multiple forwarding nodes. The method includes: the controller determines the SBFD configuration information according to the SBFD mechanism configuration state of the first forwarding node among the plurality of forwarding nodes, and the SBFD configuration information includes: information required to configure an SBFD instance associated with the segment routing SR service ; The controller sends a border gateway protocol BGP message to the first forwarding node, and the BGP message carries the SBFD configuration information, that is, the controller can dynamically configure the SBFD instance for the forwarding node, and the user does not need to statically configure the SBFD instance for the forwarding node. It can realize more flexible and dynamic deployment and help to provide tunnel protection in time.

Optionally, the SR service is an SR Policy service.

In a possible implementation manner, the controller determines the SBFD configuration information according to the SBFD mechanism configuration state of the first forwarding node among the multiple forwarding nodes, including: no SBFD is configured in the first forwarding node In the case of a mechanism, the SBFD configuration information includes information required for the first forwarding node to create an SBFD instance; in the case where the SBFD mechanism is configured in the first forwarding node, the SBFD configuration information It includes information for adjusting the configuration parameters of the SBFD configured in the first forwarding node. Therefore, regardless of whether the SBFD mechanism is configured in the first forwarding node, the controller can generate corresponding SBFD configuration information for the first forwarding node, so that the first forwarding node can establish or adjust the SBFD instance based on the SBFD configuration information to satisfy the forwarding Node needs.

In a possible implementation manner, the BGP message also carries information of the SR service. Therefore, the controller may also carry the SR service information in the BGP message, so that the forwarding node creates the SR service associated with the SBFD instance.

In a possible implementation manner, the SBFD configuration information is associated with multiple SR services.

In a possible implementation manner, the first forwarding node is a head node among the multiple forwarding nodes, or the first forwarding node is a tail node among the multiple forwarding nodes.

In a possible implementation manner, the SBFD configuration information includes one or more of the following: a field indicating the type of the transceiver end of the first forwarding node, and indicating the SBFD configuration information Whether it is the field of SBFD, the field of the local discriminator resource pool of the first forwarding node, and the field of the peer discriminator resource pool of the first forwarding node.

Optionally, the SBFD configuration information may further include an optional field.

In a second aspect, a method for configuring a seamless two-way forwarding detection SBFD mechanism is provided. The method is applied to a network that supports segmented routing traffic engineering SR-TE. The network includes a controller and multiple forwarding nodes. The method includes: a first forwarding node among the plurality of forwarding nodes receives a border gateway protocol BGP message sent by the controller, the BGP message carries SBFD configuration information, and the SBFD configuration information includes: configuration and The information required for the SBFD instance associated with the SR service of the segment route; the first forwarding node configures the SBFD instance associated with the SR service according to the SBFD configuration information; and configures the SBFD instance associated with the SR service After success, the first forwarding node performs SBFD negotiation with the peer node corresponding to the first forwarding node. Therefore, the first forwarding node can dynamically configure the SBFD instance based on the SBFD configuration information delivered by the controller, and the user does not need to statically configure the SBFD instance for the first forwarding node, which can realize more flexible and dynamic deployment and help provide timely tunnel protection.

Optionally, the SR service is an SR Policy service.

In a possible implementation manner, in a case where the SBFD mechanism is not configured in the first forwarding node, the SBFD configuration information includes information required for the first forwarding node to create an SBFD instance; the The first forwarding node creates a new SBFD instance associated with the SR service based on the SBFD configuration information. Therefore, the first forwarding node may create an SBFD instance associated with the SR service based on the SBFD configuration information delivered by the controller.

In a possible implementation manner, when the SBFD mechanism is configured in the first forwarding node, the SBFD configuration information includes configuration parameters for adjusting the SBFD configured in the first forwarding node Information; the first forwarding node adjusts the configuration parameters of the configured SBFD based on the SBFD configuration information. Therefore, the first forwarding node may adjust the SBFD instance associated with the SR service based on the SBFD configuration information delivered by the controller.

In a possible implementation manner, the BGP message also carries information of the SR service. Therefore, the first forwarding node may create the SR service associated with the SBFD instance based on the controller carrying SR service information in the BGP message.

In a third aspect, a controller is provided, which includes a module for performing the method in the first aspect or any possible implementation manner of the first aspect.

According to a fourth aspect, a forwarding node is provided. The forwarding node includes a module for performing the method in the second aspect or any possible implementation manner of the second aspect.

According to a fifth aspect, a network is provided, the network including a controller and a plurality of forwarding nodes, wherein the controller is used to perform the method in the first aspect or any possible implementation manner of the first aspect; the multiple forwarding The first forwarding node in the node is used to perform the method in the second aspect or any possible implementation manner of the second aspect.

Optionally, the first forwarding node is a head node, and the opposite node corresponding to the first forwarding node is a tail node; or, the first forwarding node is a tail node and the opposite node corresponding to the first forwarding node Is the head node.

Alternatively, the network may be a network that supports segmented routing traffic engineering SR-TE, for example, an SDN network.

According to a sixth aspect, there is provided a computer-readable storage medium that stores a program that causes a controller to execute the first aspect described above and any of its various implementations to seamlessly configure Forwarding detection method of SBFD mechanism.

In a seventh aspect, a computer-readable storage medium is provided, the computer-readable storage medium stores a program that causes a forwarding node to perform the second aspect described above, and any one of its various implementations in a seamless two-way configuration Forwarding detection method of SBFD mechanism.

In an eighth aspect, the present application also provides a computer program product containing instructions that, when run on a computer, causes the computer to perform the method for configuring the seamless two-way forwarding detection SBFD mechanism in the above aspects.

In a ninth aspect, an apparatus for configuring a seamless two-way forwarding detection SBFD mechanism is provided. The apparatus includes a processor, a memory, and a transceiver. The processor is connected to the memory and the transceiver. The memory is used to store instructions, the processor is used to execute the instructions, and the transceiver is used to communicate with other network elements under the control of the processor. When the processor executes the instructions stored in the memory, the execution causes the processor to execute the method for configuring the seamless two-way forwarding detection SBFD mechanism in the above aspects.

BRIEF DESCRIPTION

FIG. 1 is a schematic diagram of a network scenario to which an embodiment of the present application is applied;

Figure 2 is an example diagram of SBFD mechanism for reachability detection;

3 is a schematic diagram of a method for configuring a seamless two-way forwarding detection SBFD mechanism according to an embodiment of the present application;

4 is a schematic block diagram of an apparatus for configuring a seamless two-way forwarding detection SBFD mechanism according to an embodiment of the present application;

5 is a schematic block diagram of an apparatus for configuring a SBFD mechanism for seamless bidirectional forwarding detection according to another embodiment of the present application;

6 is a schematic structural diagram of an apparatus for configuring a SBFD mechanism for seamless bidirectional forwarding detection according to an embodiment of the present application;

7 is a schematic structural diagram of an apparatus for configuring a seamless two-way forwarding detection SBFD mechanism according to another embodiment of the present application. detailed description

The technical solutions in this application will be described below with reference to the drawings.

The technical solutions of the embodiments of the present application are applicable to a network supporting segment routing (SR) technology or SR Policy technology, where the network includes a controller and multiple forwarding nodes. For example, the network may be an SDN network. The tunnel established between the forwarding nodes may be a segment routing-traffic engineering (SR-TE) tunnel. The forwarding node supports the SR Policy service. It should be understood that, in the embodiments of the present application, the forwarding node may be a switch, a router, or other devices or network elements that support forwarding packets or data. This embodiment of the present application does not limit this.

SRpolicy technology is a new tunnel drainage technology developed on the basis of SR technology. SR-TE calculates the path according to the Color attribute required by the service level agreement (SLA) representing the service tunnel. The service network head node matches the corresponding tunnel to realize the forwarding of service traffic through the extended service routing Color community attribute and the information of the remote node of the network. Through the SRPolicy technology, the SR tunnel path can be customized for services with specific SLA requirements, and the application-level service forwarding network can be subdivided. For further detailed description of SRpolicy, please refer to the introduction of the prior art, which will not be repeated here.

In order to facilitate understanding and description of the method proposed in the embodiments of the present application, the process of establishing an SR Policy service will be described with reference to FIG. 1 first. FIG. 1 shows a schematic diagram of a network scenario to which an embodiment of the present application is applied. As shown in FIG. 1, the network includes a controller (or network manager) and a forwarding node (for example, the forwarding node includes a head node RT1, an intermediate node RT2, and a tail node RT3). The controller can deliver the SR policy message to the head node RT1 and the tail node RT3, so as to deploy the SR policy service in the network. Node labels and adjacent labels are pre-distributed by any forwarding node through IGP routing. The controller collects network topology and label space information through border gateway link state protocol (BGP-LS) messages. The controller provides an interface; users plan VPN service source and sink nodes (RT1-RT3) and diversion strategies (correspondence between Color and tunnel service level agreement SLA calculation constraints) for specific private network users. The controller calculates the SR policy tunnel path from the head node RT1 to the tail node RT3, and converts the calculated tunnel path into a label stack; the controller encapsulates the path label stack in the SR policy border gateway protocol through a session of the BGP SR policy address family (border gateway protocol, BGP) The session message is delivered to the head node RT1. The tail node RT3 injects the Color extended community attribute into the private network route of a specific user, and delivers the BGP routing policy. The tail node RT3 advertises the BGP route carrying the Color community attribute to the head node RT1. The head node RT1 stores the BGP route delivered by the tail node RT3, and generates a BGP routing table. The head node RT1 matches the SR Policy sent by the controller based on the stored BGP route, and establishes the SR policy tunnel after the match is successful, connects the next hop of the route to the SR policy tunnel, and the ingress specific user traffic is based on the route The next hop in the table matches the BSID 30027 to direct traffic to the SR policy tunnel for forwarding.

The head node RT1 refers to a traffic ingress node. The tail node RT3 refers to the traffic exit node.

The following describes some terms or concepts involved in the embodiments of the present application.

SBFD is a fast detection protocol. SBFD achieves the purpose of reachability detection by quickly and continuously releasing protocol messages. As shown in Figure 2, the SBFD mechanism is divided into an initiator and a reflector. Before the link is detected, the initiator and the reflector send SBFD control packets (SBFD Control Packet) to notify the SBFD descriptor (Discriminator) and other information. During link detection, the initiator actively sends the SBFD Echo message, and the reflector loops back the message according to the local situation. The initiator determines the local status based on the reflected message. When SBFD is applied to SR scene detection, there are mainly two scenarios: SBFD for SR LSP and SBFD for SR-TE LSP. In the SR scenario where SBFD detects SR, the SBFD initiator-to-reflector path takes MPLS label forwarding, and the reflective end takes the multi-hop IP path to the initiator return path.

As the detection end, the initiator has SBFD state machine mechanism and detection mechanism. The initiator's state machine has only Up and Down states, and the outgoing messages are only Up and Down states, and can only receive Up or Admin Down messages. The SBFD message is sent from the initiator to the reflector. The initial state of the message is Down and the destination port number of the message is 7784. For further detailed description of SBFD, please refer to the introduction of the prior art, which will not be repeated here.

It should be understood that in the embodiments of the present application, the head and tail nodes should not be confused with the initiating reflector. Among them, the head node and the tail node are distinguished from the perspective of the entrance and exit of the tunnel traffic in the network; and the initiator and the reflector are distinguished from the perspective of the SBFD mechanism for packet reachability detection. For example, in the SBFD mechanism, the head node may be the initiator and the corresponding tail node may be the reflector; or, the head node may be the reflector and the corresponding tail node may be the initiator.

In the prior art, the SBFD instances in the forwarding node are all statically configured by the user, do not support selective management based on service dynamics, and are not flexible enough. The embodiment of the present application intends to propose a method for configuring a seamless two-way forwarding detection SBFD mechanism to dynamically configure SBFD instances for forwarding nodes, so as to achieve more flexible and dynamic deployment.

FIG. 3 shows a schematic diagram of a method 300 for configuring a seamless two-way forwarding detection SBFD mechanism according to an embodiment of the present application. The method 300 is applied to a network that supports segmented routing traffic engineering SR-TE, and the network includes a controller and multiple forwarding nodes. As shown in FIG. 3, the method 300 includes:

S310. The controller determines SBFD configuration information according to the configuration state of the SBFD mechanism of the first forwarding node among the multiple forwarding nodes. The SBFD configuration information includes: required for configuring an SBFD instance associated with the segment routing SR service. information.

Among them, the SR service may be an SR Policy service. The relevant configuration process of the SR Policy service can be described above.

Optionally, the SBFD configuration information includes one or more of the following: a field indicating the type of the transceiver of the first forwarding node, and a field indicating whether the SBFD configuration information is SBFD (For example, when the field value is 1, it indicates SBFD, and when the field value is 0, it indicates ordinary BFD), the field of the local distinguisher resource pool of the first forwarding node, and the peer distinguisher of the first forwarding node Fields and reserved fields of the resource pool.

The controller can extend the address family to the BGP protocol and add the above SBFD configuration information. For example, based on the BGP SR-Policy multi-protocol extended address family, the controller adds a BFD extended community attribute to carry the above SBFD configuration information. In other words, the controller can advertise the SBFD configuration information through BGP-SR-Policy address family routing. Optionally, the SBFD configuration information includes one or more of the following: a field indicating the type of the transceiver of the first forwarding node, and a field indicating whether the SBFD configuration information is SBFD , The field of the local discriminator resource pool of the first forwarding node, the field of the peer discriminator resource pool of the first forwarding node, and the like. For example, the field used to indicate the type of the transceiver of the first forwarding node may be the Flags field to indicate whether the first forwarding node is the initiator or the reflector; the field used to indicate whether the SBFD configuration information is SBFD may be Type field to indicate the type of the SBFD configuration information (types may include ordinary BFD or SBFD, etc.); the field of the local discriminator resource pool of the first forwarding node may be the Local Discriminatiors field; the first forwarding node Fields such as the peer discriminator resource pool field can be the Remote Discriminatiors field.

Optionally, the SBFD configuration information may also include other optional fields, such as Optional Para (Variable), which may specifically include: a field (Min-tx-interval field) used to indicate the minimum transmission interval of the control message, Fields used to indicate the minimum reception interval of control packets (Min-rx-interval field), fields used to indicate the local detection multiple of the BFD session (Detect-multiplier field), and used to indicate authentication data (secret key) Fields for part of the length information (AuthLenth field), a field for indicating the authentication type of the control message (AuthType field), a field for indicating the authentication data (AuthenticationData field), etc. It should be understood that the control message here may be a BFD control message or an SBFD control message, which is not specifically limited, and what control message can be based on which BFD mechanism (such as the SBFD mechanism or Ordinary BFD mechanism or link bundling Link (Bandle BFD mechanism) to decide. It should be understood that the embodiments of the present application do not specifically limit the fields included in the SBFD configuration information, and may be determined based on actual needs. For example, the fields included in the SBFD configuration information may be one or more of the above fields , Can also include other fields.

For example, the BGP protocol can be extended as follows, so that BGP carries the SBFD configuration information, and an example of a format in which the BGP protocol adds an extended community attribute is as follows:

Based on the above, the extended BGP packet carries the Type field, flag field, reserved field, local discriminator local field, discriminatior field, remote discriminator remote field, optional parameter Optional Para or variable field.

The Type field is used to identify the type of BFD. For example, Type=0x00 means carrying common BFD (for example, RFC5880) configuration information, and Type=0x01 means carrying SBFD configuration information. Optionally, if multiple types of BFD need to be deployed simultaneously, multiple BFD extended community attributes need to be carried.

Among them, the Flags field format is as follows:

(The Reserved field is set to 0 by default)

In the Flags field, the R bit represents Reflector, which is used to indicate the reflecting end or initiating end of SBFD. For example, when R is set to 1, it indicates the reflective end of SBFD; when R is set to 0, it indicates the initiator of SBFD.

In the Flags field, the P bit indicates Passive, which is used to indicate the reflective or initiating end of BFD. When set to 1, it indicates the reflection end of the ordinary BFD, and when set to 0, it indicates the origination end of the ordinary BFD.

When the R bit is set to 0, it indicates the initiator of SBFD. At this time, the local discriminator local field carries the local discriminator required to create SBFD or BFD, and the length is 4 bytes; the remote discriminator Remote Discriminatior field Carry the remote discriminator required to create SBFD or BFD. In particular, when the local Discriminatior field is set, it means that the segment specifier for creating SBFD or BFD is not specified and can be configured locally or automatically generated by the forwarding node. In particular, when the Remote Discriminatior field is set, it indicates that the remote discriminator to create the SBFD instance is not specifically specified, and can be locally configured or automatically generated by the forwarding node.

When the R bit is set to 1, it indicates the reflection end of SBFD. At this time, the local discriminator local field carries the reflection end discriminator (Reflector Discriminatior) required to create SBFD or BFD. The Remote Discriminatior field is set to zero by default.

Among them, the Optional Para field format is as follows:

Exemplarily, the embodiment of the present application may carry the minimum sending interval of the BFD control message through the Min-tx-interval field, in units of microseconds. It should be understood that the “BFD control message” referred to in the above “Min-tx-interval field” is only an example, and the embodiment of the present application does not limit the type of BFD, which may be ordinary BFD or SBFD, depending on The controller configures which BFD mechanism to forward the node. In other words, the "BFD control message" involved in the "optional field" can also be replaced with "SBFD control message". The "BFD control message" involved in the optional field below can also be explained similarly, and will not be repeated here.

In this embodiment of the present application, the Min-rx-interval field may be used to carry the minimum receiving interval of the BFD control message, in microseconds. In this embodiment of the present application, the Detect-multiplier field may be used to carry the local detection multiple of the BFD session. The embodiment of the present application may carry the authentication type of the BFD control message through the AuthType field, which has the following values:

0-Reserved

1-SimplePassword

2-Keyed MD5

3-Meticulous Keyed MD5

4-Keyed SHA1

5-Meticulous Keyed SHA1

6-255-Reserved for future use

That is to say, in this embodiment of the present application, each encryption algorithm may be assigned a type value to refer to the corresponding authentication type. It should be understood that the above seven values may correspond to the encryption algorithm in the industry standard respectively. For the relevant explanation or description of the encryption algorithm, please refer to the description of the prior art, and the description of the encryption algorithm will not be expanded in detail here.

The embodiment of the present application may carry the length information of the authentication data (secret key) through the AuthLenth field.

The embodiment of the present application may carry authentication data (secret key) information through the Authentication Data field.

In the embodiment of the present application, the controller may determine the configuration state of the SBFD in the forwarding node, and then determine the corresponding SBFD configuration information for the forwarding node based on whether the SBFD mechanism is configured in the forwarding node.

Taking the first forwarding node as an example, in the case where the SBFD mechanism is not configured in the first forwarding node, the SBFD configuration information determined by the controller for the first forwarding node includes required for the SBFD instance of the first forwarding node Information to facilitate the first forwarding node to create an SBFD instance; when the SBFD mechanism is configured in the first forwarding node, the SBFD configuration information determined by the controller for the first forwarding node includes the SBFD used to adjust the configured Configuration information. Among them, "adjust the configuration parameters of the configured SBFD" can be interpreted as "supplement, update, or delete the configuration parameters of the configured SBFD" and other operations.

S320. The controller sends a BGP message to the first forwarding node, where the BGP message carries the SBFD configuration information. Correspondingly, the first forwarding node receives the BGP message and obtains the SBFD configuration information.

Here, the controller may send the SBFD configuration information to the first forwarding node through a BGP message. After receiving the BGP message, the first forwarding node configures the SBFD instance based on the SBFD configuration information carried in the BGP message. The first forwarding node may be a head node or a tail node, which is not limited.

After receiving the SBFD configuration information, the first forwarding node configures the SBFD instance associated with the SR service; after the SBFD instance associated with the SR service is successfully configured, the first forwarding node and the first forwarding node The peer node corresponding to the forwarding node performs SBFD negotiation. The peer node corresponding to the first forwarding node refers to a node that needs to establish SBFD negotiation with the first forwarding node. For example, the first forwarding node is the head node, and the opposite node corresponding to the first forwarding node is the tail node; or, the first forwarding node is the tail node, and the opposite node corresponding to the first forwarding node is the head node, which is not specific. limited.

Optionally, the SBFD configuration information may be delivered separately, or may be delivered together with the SR service associated with the SBFD configuration information, which is not limited.

Optionally, the controller may assign different values to the R bit, P bit of the Flag field in the SBFD configuration information, the local discriminator local field, and the remote discriminator remote field to distinguish the head node or the tail node SBFD configuration information.

For example, if the first forwarding node is the head node, the format of the SBFD configuration information received by the head node in the BGP SR-Policy route may be as follows:

Among them, the specific format of the Flags field is as follows:

(The Reserved field is set to 0 by default)

In the SBFD configuration information received by the above head node, the Type field is set to 0x01, indicating that SBFD type protection is currently used; the R bit of the Flag field is 0, indicating that the head node is the initiator of SBFD; the Local Discriminatior field can be set to A specific value in the local discriminator resource pool. In particular, when set to 0, it is locally configured by the forwarding node or automatically generated.

The Remote Discriminatior field is set to a specific value in the peer discriminator resource pool. In particular, when set to 0, it is configured locally by the repeater or obtained by other means. Here, the peer refers to the peer of the head node, such as the tail node.

The head node can be matched with Local Discriminatior and Remote Discriminatior to create an SBFD instance.

If the total length of the field corresponding to the SBFD configuration information received by the head node is greater than 12 bytes, it means that the head node needs to read the Optional Para field.

For example, the format of the Optional Para field is as follows:

Optionally, the controller can specify the minimum message sending/receiving interval, detection time period, and authentication encryption algorithm for the head node through the Optional Para field described above.

After receiving the SBFD configuration information sent by the controller, the head node may create or adjust the SBFD instance based on the specific content of the SBFD configuration information.

For example, if the first forwarding node is a tail node, the format of the SBFD configuration information received by the tail node in the BGP SR-Policy route may be as follows:

Among them, the Flags field format is as follows:

(The Reserved field is set to 0 by default)

The Type field is set to 0x01, indicating that the SBFD type protection is currently used; the R bit position in the Flag field is 1, indicating that RT3 is the SBFD reflective end; the P bit position in the Flag field is 0, indicating that it does not need to be configured as a BFD reflective end; Local The Discriminatior field is set to the same value as the Remote Discriminatior field in the head node.

Similarly, if the total length of the field corresponding to the SBFD configuration information received by the tail node is greater than 12 bytes, it indicates that the tail node needs to read the optional parameter (Optional Para) field. Optionally, the controller can specify the minimum message sending/receiving interval, detection time period, and authentication encryption algorithm for the tail node through the Optional Para field described above.

After receiving the SBFD configuration information sent by the controller, the tail node can create or adjust the SBFD instance based on the specific content of the SBFD configuration information.

In the example of this application, if both the head node and the tail node receive the BFD extended community attribute delivered by the controller, and the head node and the tail node complete the service deployment according to the above SBFD configuration information carried in the attribute, the head node Negotiate the SBFD service with the tail node. If the negotiation between the head node and the tail node is successful, the SBFD for SR-Policy service is successfully created.

The following describes whether the SBFD mechanism is configured in the first forwarding node. Regardless of whether the SBFD mechanism is configured in the first forwarding node, the technical solutions of the embodiments of the present application are applicable.

The first way to achieve:

If the SBFD mechanism is not configured on the first forwarding node, the SBFD configuration information includes information required for the first forwarding node to create an SBFD instance;

Wherein, the first forwarding node configuring the SBFD instance associated with the SR service according to the SBFD configuration information includes:

Based on the SBFD configuration information, the first forwarding node creates a new SBFD instance associated with the SR service.

If the SBFD mechanism is not configured in the first forwarding node, the controller can separately deliver the SBFD configuration information to the first forwarding node through BGP packets, or it can also simultaneously deliver the information for creating SR services and the SBFD configuration through BGP packets. information. Here, since SBFD is not configured in the first forwarding node, the SBFD configuration information needs to contain all necessary information for creating SBFD.

Specifically, for the case where the first forwarding node is the head node, the head node may first create the SR based on the BGP packet when receiving the BGP message and the SBFD configuration information from the BGP message delivered by the controller The information of the service creates an SR-Policy service, and immediately creates an SBFD instance associated with the SR-Policy service after the SR-Policy service is established. For the case where the first forwarding node is the tail node, in the scenario of a two-way tunnel, after receiving the SR service creation information and SBFD configuration information delivered by the controller, the tail node may first create the SR service information based on the message Create an SR-Policy service. After the SR-Policy service is established, create the configuration of the reflective end of the SBFD instance associated with the SR-Policy service. After creating the SBFD instance, wait for SBFD negotiation with the head node. Or, in the scenario of establishing a one-way tunnel, when the tail node does not need the information issued by the controller to create the SR-Policy service, the network layer reachable information (network layer reachable information) of the SR service received by the tail node , NLRI) The endpoint will be set to zero (zero means that the BGP message sent by the controller to the tail node will not carry the information used to create the SR-Policy service).

It should be understood that the embodiment of the present application does not specifically limit the order in which the first forwarding node creates the SR-Policy service or the SBFD instance first, and may be determined based on actual requirements.

After the SBFD instances in both the head node and the tail node are created, the head node and the tail node can negotiate SBFD and associate the SBFD instance with the SR-Policy service to provide fault detection for the SR service.

The second way to achieve:

If the SBFD mechanism is configured on the first forwarding node, the SBFD configuration information includes information for adjusting configuration parameters of the SBFD configured in the first forwarding node, wherein the first forwarding node is based on the SBFD Configuration information, configuring the SBFD instance associated with the SR service, including:

The first forwarding node adjusts the configuration parameters of the configured SBFD based on the SBFD configuration information.

Specifically, if the SBFD mechanism is configured in the first forwarding node, the controller does not need to carry all information for creating an SBFD instance in the BGP packet. The first forwarding node may use the original statically configured SBFD basic configuration, such as a local static configuration or an automatically generated configuration value. Here, in the SBFD configuration information sent by the controller to the first forwarding node, some information in the SBFD may be carried as a supplement to the binding strategy and/or parameters corresponding to the SBFD configuration. For example, in the fields included in the SBFD configuration information, Local Discriminatior and Remote Discriminatior can be set to zero, and Local Discriminatior and Remote Discriminatior can be set to zero. This means that information about Local Discriminatior and Remote Discriminatior is not carried, and the remaining fields can be The controller is newly configured for the first forwarding node (refer to the foregoing description).

For example, the format of the SBFD configuration information received by the first forwarding node in the BGP SR-Policy route may be as follows:

For the fields of the SBFD configuration information in the BGP SR-Policy route, the controller sets the Local Discriminatior field to 0 and the Remote Discriminatior field to 0, which means that these two fields use the statically configured values in the first forwarding node. In particular, if these two fields are non-zero values and the first forwarding node is also statically configured, the value carried in the SBFD configuration information should be used to create a new SBFD instance and associate it with the SR-Policy service.

Therefore, in the second implementation manner, the SBFD configuration information delivered by the controller may carry part of the information, so that the first forwarding node can adjust the parameters of the SBFD basic configuration.

In the second implementation manner, the first forwarding node may update the SBFD instance. If the SR service in the first forwarding node has been associated with the SBFD instance, but the association relationship needs to be changed, the SBFD configuration information delivered by the controller to the first forwarding node may be the configuration information of the new SBFD instance. The first forwarding node refreshes the SBFD instance that has been associated with the SR service based on the configuration information of the new SBFD instance.

In the embodiment of the present application, the BGP message sent by the controller to the first forwarding node may carry the configuration information of the SR service and the SBFD instance associated with the SR service. In particular, when it is necessary to delete the SBFD instance associated with the SR service, that is, when the SR service is no longer associated with the SBFD instance, the BGP message delivered by the controller to the first forwarding node carries the information of the SR service, and No longer carry SBFD configuration information. In this way, when receiving the BGP message, the first forwarding node may delete or unbind the association relationship between the SBFD instance and the SR service.

Optionally, as an implementation manner, the first forwarding node may delete the SBFD instance that has been created, which can release resources, which helps reduce the occupation of forwarding nodes and network resources.

For example, if the first forwarding node does not initially have a static configuration of SBFD, after configuring the first forwarding node with an SBFD instance associated with a certain SR service by using the method of the embodiment of the present application, if the first forwarding node subsequently receives a need If the BGP message of the SR service is revoked or deleted, and the SR service has been completely revoked, the SBFD instance associated with the SR service can also be deleted, so as to save resources.

Optionally, the SBFD configuration information in the embodiment of the present application may be associated with multiple SR services. When delivering the BGP message to the forwarding node, the controller may deliver multiple BGP messages corresponding to multiple SR services to the first forwarding node, where each BGP message carries the same SBFD configuration information. When receiving the BGP message, the first forwarding node may multiplex the SBFD configuration information to multiple different SR services.

Alternatively, when the controller delivers the BGP message to the first forwarding node, it may deliver a BGP message to the first forwarding node, where the BGP message carries configuration information of multiple SR services and the same SBFD configuration information. When receiving the BGP message, the first forwarding node may multiplex the SBFD configuration information to multiple different SR services.

It should be understood that the method of configuring the seamless two-way forwarding detection SBFD mechanism in the embodiment of the present application is described by using SBFD as an example. The technical solution in the embodiment of the present application is also applicable to the dynamic deployment of ordinary BFD, LinkBandle BFD, or other BFD. , This is not limited. For example, you can extend the configuration information of common BFD to other BGP service address families, or add a special BFD control address family.

It should also be understood that the examples of the format of each field appearing in the embodiments of the present application do not limit the embodiments of the present application, and those skilled in the art can make equivalent transformations or adjustments based on the above examples, and these equivalent transformations or adjustments should fall It falls into the protection scope of the embodiments of the present application.

The method for configuring a seamless two-way forwarding detection SBFD mechanism according to an embodiment of the present application is described in detail above with reference to FIGS. 1 to 3. The following describes an apparatus for configuring a seamless two-way forwarding detection SBFD mechanism according to an embodiment of the present application with reference to FIGS. 4 to 7. It should be understood that the technical features described in the method embodiments are also applicable to the following device embodiments.

FIG. 4 shows a schematic block diagram of an apparatus 400 for configuring a seamless two-way forwarding detection SBFD mechanism according to an embodiment of the present application. Alternatively, the device 400 may be a controller. As shown in FIG. 4, the device 400 includes:

The determining module 410 is configured to determine SBFD configuration information according to the SBFD mechanism configuration state of the first forwarding node among the multiple forwarding nodes, where the SBFD configuration information includes: configuring the SBFD instance associated with the segment routing SR service Required information;

The transceiver module 420 is configured to send a BGP message to the first forwarding node, where the BGP message carries the SBFD configuration information.

In a possible implementation manner, the determining module 410 is configured to determine SBFD configuration information according to the SBFD mechanism configuration state of the first forwarding node among the multiple forwarding nodes, specifically including:

When the SBFD mechanism is not configured in the first forwarding node, the SBFD configuration information includes information required for the first forwarding node to create an SBFD instance;

When the SBFD mechanism is configured in the first forwarding node, the SBFD configuration information includes information for adjusting configuration parameters of the SBFD configured in the first forwarding node.

In a possible implementation manner, the BGP message also carries information of the SR service.

It should be understood that the device 400 according to an embodiment of the present application may correspond to the method on the controller side in the foregoing method embodiments, and the above and other management operations and/or functions of the various modules in the device 400 are to implement the corresponding Steps, therefore, the beneficial effects in the foregoing method embodiments can also be achieved, and for the sake of brevity, they will not be repeated here.

FIG. 5 shows a schematic structural diagram of an apparatus 500 for configuring a seamless two-way forwarding detection SBFD mechanism according to an embodiment of the present application. As shown in FIG. 5, the device 500 includes:

The processor 501, the memory 502, and the transceiver 503.

The processor 501, the memory 502, and the transceiver 503 communicate with each other through an internal connection path, and transfer control and/or data signals. In one possible design, the processor 501, the memory 502, and the transceiver 503 may be implemented by a chip. The memory 502 may store program codes, and the processor 501 calls the program codes stored in the memory 502 to implement corresponding functions of the terminal device.

The processor 501 is configured to determine SBFD configuration information according to the SBFD mechanism configuration state of the first forwarding node among the multiple forwarding nodes, where the SBFD configuration information includes: configuring SBFD associated with the segment routing SR service Information required by the example; the transceiver 503 is used to send a BGP packet to the first forwarding node, where the BGP packet carries the SBFD configuration information.

Optionally, the determination module 410 in FIG. 4 may correspond to the processor 501 in FIG. 5, and the transceiver module 420 may correspond to the transceiver 503 in FIG. 5. In another embodiment, the transceiver can be divided into two parts: a receiver and a transmitter.

FIG. 6 shows a schematic block diagram of an apparatus 600 for configuring a seamless bidirectional forwarding detection SBFD mechanism according to an embodiment of the present application. The device 600 is applied to a network that supports segmented routing traffic engineering SR-TE, and the network includes a controller and multiple forwarding nodes. Optionally, the device 600 is the first forwarding node among the multiple forwarding nodes. As shown in FIG. 6, the device 600 includes:

The transceiver module 610 is configured to receive a BGP message sent by the controller, where the BGP message carries SBFD configuration information, and the SBFD configuration information includes: required for configuring an SBFD instance associated with the segment routing SR service information;

The processing module 620 is configured to configure an SBFD instance associated with the SR service according to the SBFD configuration information;

The processing module 620 is further configured to, after the SBFD instance associated with the SR service is successfully configured, perform SBFD negotiation with the peer node corresponding to the first forwarding node.

In a possible implementation manner, in a case where no SBFD mechanism is configured in the first forwarding node, the SBFD configuration information includes information required for the first forwarding node to create an SBFD instance;

Wherein, the processing module 620 is configured to configure an SBFD instance associated with the SR service according to the SBFD configuration information, specifically including:

In a possible implementation manner, when the SBFD mechanism is configured in the first forwarding node, the SBFD configuration information includes configuration parameters for adjusting the SBFD configured in the first forwarding node Information; wherein, the processing module 620 is configured to configure an SBFD instance associated with the SR service according to the SBFD configuration information, specifically including:

Based on the SBFD configuration information, the configuration parameters of the configured SBFD are adjusted.

Optionally, the BGP message also carries information about the SR service.

Optionally, the SBFD configuration information is associated with multiple SR services.

Optionally, the first forwarding node is a head node among the multiple forwarding nodes, or the first forwarding node is a tail node among the multiple forwarding nodes.

Optionally, the SBFD configuration information includes one or more of the following: a field indicating the type of the transceiver of the first forwarding node, and a field indicating whether the SBFD configuration information is SBFD , The field of the local discriminator resource pool of the first forwarding node, and the field of the peer discriminator resource pool of the first forwarding node.

It should be understood that the device 600 according to the embodiment of the present application may correspond to the method on the forwarding node side in the foregoing method embodiment, and the above and other management operations and/or functions of the various modules in the device 600 are respectively to implement the corresponding Steps, therefore, the beneficial effects in the foregoing method embodiments can also be achieved, and for the sake of brevity, they will not be repeated here.

FIG. 7 shows a schematic structural diagram of an apparatus 700 for configuring a seamless two-way forwarding detection SBFD mechanism according to an embodiment of the present application. As shown in FIG. 7, the device 700 includes:

The processor 701, the memory 702, and the transceiver 703.

The processor 701, the memory 702, and the transceiver 703 communicate with each other through an internal connection path, and transfer control and/or data signals. In a possible design, the processor 701, the memory 702, and the transceiver 703 may be implemented by a chip. The memory 702 may store program codes, and the processor 701 calls the program codes stored in the memory 702 to implement corresponding functions of the terminal device.

The transceiver 703 is configured to receive a BGP message sent by the controller, where the BGP message carries SBFD configuration information, and the SBFD configuration information includes: required to configure an SBFD instance associated with the segment routing SR service Information; the processor 701 is configured to configure an SBFD instance associated with the SR service according to the SBFD configuration information; after the SBFD instance associated with the SR service is successfully configured, communicate with the first forwarding node The corresponding peer node performs SBFD negotiation.

Optionally, the processing module 620 in FIG. 6 may correspond to the processor 701 in FIG. 7, and the transceiver module 610 may correspond to the transceiver 703 in FIG. 7. In another embodiment, the transceiver can be divided into two parts: a receiver and a transmitter.

The present application also provides a network including a controller and multiple forwarding nodes. The controller can execute the method performed by the controller described above. The first forwarding node may be included in the multiple forwarding nodes. The first forwarding node may be the head node of an SR Policy tunnel, or the first forwarding node may be the tail node of an SR Policy tunnel.

The method disclosed in the above embodiments of the present application may be applied to a processor, or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method embodiment may be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software. The aforementioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an existing programmable gate array (Field Programmable Gate Array, FPGA), or other available Programming logic devices, discrete gates or transistor logic devices, discrete hardware components, can also be a system chip (system on chip, SoC), can also be a central processor (central processor (unit), CPU), can also be a network processor (network processor (NP), can also be a digital signal processing circuit (digital signal processor, DSP), can also be a microcontroller (micro controller (unit), MCU), can also be a programmable controller (programmable logic device (PLD) or other Integrated chip. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application may be implemented or executed. The general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied and executed by a hardware decoding processor, or may be executed and completed by a combination of hardware and software modules in the decoding processor. The software module may be located in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, and registers. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory may be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electronically Erasable programmable read only memory (Electrically, EPROM, EEPROM) or flash memory. The volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (Synchlink DRAM, SLDRAM) ) And direct memory bus random access memory (Direct Rambus RAM, DR RAM). It should be noted that the memories of the systems and methods described herein are intended to include, but are not limited to these and any other suitable types of memories.

Various aspects or features of the present application may be implemented as methods, devices, or articles using standard programming and/or engineering techniques. The term "article of manufacture" as used in this application encompasses a computer program accessible from any computer-readable device, carrier, or medium. For example, the computer-readable medium may include, but is not limited to: magnetic storage devices (for example, hard disks, floppy disks, or magnetic tapes, etc.), optical disks (for example, compact discs (CDs), digital universal discs (digital discs, digital discs, DVDs)) Etc.), smart cards and flash memory devices (for example, erasable programmable read-only memory (EPROM), cards, sticks or key drives, etc.). In addition, the various storage media described herein may represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and/or carrying instructions and/or data.

Persons of ordinary skill in the art may realize that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on the specific application of the technical solution and design constraints. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that for the convenience and conciseness of the description, the specific working process of the system, device and unit described above can refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical, or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.

If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application essentially or part of the contribution to the existing technology or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to enable a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. The foregoing storage media include various media that can store program codes, such as a U disk, a mobile hard disk, a read-only memory ROM, a random access memory RAM, a magnetic disk, or an optical disk.

The above is only the specific implementation of this application, but the scope of protection of this application is not limited to this, any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in this application. It should be covered by the scope of protection of this application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

The above are only the specific embodiments of the present invention, but the scope of protection of the present invention is not limited to this. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed by the present invention. It should be covered by the protection scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

A method for configuring a seamless two-way forwarding detection SBFD mechanism, characterized in that the method includes:

The controller determines SBFD configuration information, where the SBFD configuration information includes: information required to configure an SBFD instance associated with the segment routing SR service;

The controller sends a border gateway protocol BGP message to the forwarding node, where the BGP message carries the SBFD configuration information.
The method of claim 1, wherein:

The SBFD configuration information includes information required by the forwarding node to create the SBFD instance; or

The SBFD configuration information includes information for adjusting configuration parameters of the SBFD instance that have been configured in the forwarding node.
The method according to claim 1 or 2, wherein the BGP message further carries information of the SR service.
The method according to any one of claims 1 to 3, wherein the SBFD configuration information is associated with multiple SR services.
The method according to any one of claims 1 to 4, wherein the forwarding node is a head node of a tunnel, or the forwarding node is a tail node of a tunnel.
The method according to any one of claims 1 to 5, wherein the SBFD configuration information includes one or more of the following: a field indicating the type of the transceiver end of the forwarding node, A field for indicating whether the SBFD configuration information is an SBFD, a field of a local discriminator resource pool of the forwarding node, and a field of a peer discriminator resource pool of the forwarding node.
The method according to any one of claims 1-6, wherein the SBFD configuration information may further include one or more of the following: a minimum transmission interval for sending BFD control messages; BFD control messages Authentication information.
The method according to any one of claims 1-7, wherein the SBFD configuration information is carried in an extended community attribute added to the BGP packet.
A method for configuring a seamless two-way forwarding detection SBFD mechanism, characterized in that the method includes:

The forwarding node receives the border gateway protocol BGP message sent by the controller, and the BGP message carries SBFD configuration information, and the SBFD configuration information includes: information required to configure an SBFD instance associated with the segment routing SR service;

The forwarding node configures the SBFD instance according to the SBFD configuration information.
The method according to claim 9, wherein the forwarding node configuring the SBFD instance according to the SBFD configuration information includes:

The forwarding node creates the SBFD according to the SBFD configuration information.
The method according to claim 9, wherein the forwarding node configuring the SBFD instance according to the SBFD configuration information includes:

The forwarding node adjusts the configured configuration parameters of the SBFD instance based on the SBFD configuration information.
The method according to any one of claims 9 to 11, wherein the BGP message also carries information of the SR service.
The method according to any one of claims 9-12, wherein the SBFD configuration information is associated with multiple SR services.
The method according to any one of claims 9-13, wherein the forwarding node is a head node of a tunnel, or the forwarding node is a tail node of a tunnel.
The method according to any one of claims 9 to 14, wherein the SBFD configuration information includes one or more of the following: used to indicate the type of the transceiver end of the first forwarding node A field, a field for indicating whether the SBFD configuration information is SBFD, a field of the local discriminator resource pool of the first forwarding node, and a field of the peer discriminator resource pool of the first forwarding node.
The method according to any one of claims 9 to 15, wherein the SBFD configuration information may further include one or more of the following: a minimum transmission interval for sending BFD control messages; BFD control messages Authentication information.
The method according to any one of claims 9 to 16, wherein the SBFD configuration information is carried in the extended community attribute added to the BGP packet.
A controller, characterized in that it includes:

Memory, storing instructions;

A processor in communication with the memory, the processor executing the instructions, causing the device to perform the method of any one of claims 1-8.
A forwarding node, characterized in that it includes:

Memory, storing instructions;

A processor in communication with the memory, the processor executing the instructions, causing the device to perform the method of any one of claims 9-17.
A computer-readable storage medium, characterized by comprising computer-readable instructions, which when run on a computer, causes the computer to perform the method of any one of claims 1-17.
A communication system, characterized by comprising the controller of claim 18 and the forwarding node of claim 19.