CN111385165A - Method and device for configuring Seamless Bidirectional Forwarding Detection (SBFD) mechanism - Google Patents

Abstract

The application provides a method and a device for configuring a Seamless Bidirectional Forwarding Detection (SBFD) mechanism. The method comprises the following steps: the controller determines SBFD configuration information according to an SBFD mechanism configuration state of a first forwarding node of the plurality of forwarding nodes, wherein the SBFD configuration information comprises: configuring information required by an SBFD instance associated with a Segment Routing (SR) service; and the controller sends a Border Gateway Protocol (BGP) message to the first forwarding node, wherein the BGP message carries the SBFD configuration information.

Description

Method and device for configuring seamless bidirectional forwarding detection SBFD mechanism

technical field

The present application relates to the field of computers, and more particularly, to a method and apparatus for configuring a seamless bidirectional 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 switch (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 using SR as a control protocol. SR-TE refers to the tunnel created by the SR protocol based on the constraint attribute of TE. The controller is responsible for calculating the forwarding path of the tunnel and delivering the label stack strictly corresponding to the path to the forwarder. On the ingress node of the SR-TE tunnel, the forwarder can control the transmission path of the packet in the network according to the label stack.

Since SR-TE does not have a protocol established, the link-state packet (LSP) will be established successfully as long as the label stack is delivered, and the LSP will not be in protocol Down except for the label stack cancellation. Therefore, SR-TE LSP fault detection needs to rely on the deployment of bidirectional forwarding detection (BFD) detection, and switch the backup LSP through BFD fault detection. Seamless bidirectional forwarding detection (seamless BFD, SBFD) simplifies the state machine of BFD, 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 the forwarder. Static configuration of SBFD instances and parameters provides end-to-end fault detection for the created SR Policy tunnel, and cannot provide timely and dynamic tunnel protection.

SUMMARY OF THE INVENTION

In view of this, the present application provides a method and apparatus for configuring a seamless bidirectional forwarding detection SBFD mechanism, which can realize dynamic deployment of SBFD and help to provide tunnel protection in time.

A first aspect provides a method for configuring a seamless bidirectional forwarding detection SBFD mechanism, the method is applied to a network supporting segment routing traffic engineering SR-TE, the network includes a controller and a plurality of forwarding nodes, the The method includes: a controller determines SBFD configuration information according to the SBFD mechanism configuration state of a first forwarding node in the plurality of forwarding nodes, where the SBFD configuration information includes: information required for configuring an SBFD instance associated with a 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, Enables more flexible dynamic deployment, which helps to provide tunnel protection in a timely manner.

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 in the plurality of forwarding nodes, including: SBFD is not configured in the first forwarding node In the case of the SBFD mechanism, the SBFD configuration information includes the 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 Including 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 establishes or adjusts the SBFD instance based on the SBFD configuration information to meet the forwarding requirements. Node requirements.

In a possible implementation manner, the BGP message also carries the information of the SR service. Therefore, the controller can also carry the information of the SR service 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 a plurality of the 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 contents: a field used to indicate the transceiver type of the first forwarding node, a field used to indicate the SBFD configuration information Whether it is a field of SBFD, a field of the local end discriminator resource pool of the first forwarding node, a field of the opposite end discriminator resource pool of the first forwarding node.

Optionally, the SBFD configuration information may further include optional fields.

In a second aspect, a method for configuring a seamless bidirectional forwarding detection SBFD mechanism is provided, the method is applied to a network supporting segment routing traffic engineering SR-TE, the network includes a controller and a plurality of forwarding nodes, the The method includes: a first forwarding node of 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 information required by the SBFD instance associated with the segment routing SR service; the first forwarding node configures the SBFD instance associated with the SR service according to the SBFD configuration information; configure 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 enables more flexible dynamic deployment and helps to provide tunnel protection in time.

Optionally, the SR service is an SR Policy service.

In a possible implementation manner, in the 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, in the case where the SBFD mechanism is configured in the first forwarding node, the SBFD configuration information includes a parameter for adjusting the configuration parameters of the SBFD configured in the first forwarding node information; the first forwarding node adjusts the configured configuration parameters of the SBFD based on the SBFD configuration information. Therefore, the first forwarding node can 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 the information of the SR service. Therefore, the first forwarding node can create the SR service associated with the SBFD instance based on the information of the SR service carried in the BGP message by the controller.

In a possible implementation manner, the SBFD configuration information is associated with a plurality of the 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 contents: a field used to indicate the transceiver type of the first forwarding node, a field used to indicate the SBFD configuration information Whether it is a field of SBFD, a field of the local end discriminator resource pool of the first forwarding node, a field of the opposite end discriminator resource pool of the first forwarding node.

Optionally, the SBFD configuration information may further include optional fields.

In a third aspect, a controller is provided, the controller comprising a module for performing the method in the above-mentioned first aspect or any possible implementation manner of the first aspect.

In a fourth aspect, a forwarding node is provided, the forwarding node comprising a module for performing the method in the second aspect or any possible implementation manner of the second aspect.

In a fifth aspect, a network is provided, the network includes a controller and multiple forwarding nodes, wherein the controller is configured to execute the method in the first aspect or any possible implementation manner of the first aspect; the multiple forwarding nodes The first forwarding node among the nodes is configured to execute 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.

Optionally, the network may be a network supporting segment routing traffic engineering SR-TE, such as an SDN network.

In a sixth aspect, a computer-readable storage medium is provided, the computer-readable storage medium stores a program, the program enables the controller to execute the above-mentioned first aspect, and any one of its various implementations is configured in a seamless bidirectional manner The method of forwarding detection SBFD mechanism.

In a seventh aspect, a computer-readable storage medium is provided, and the computer-readable storage medium stores a program, the program enables the forwarding node to execute the second aspect, and any one of its various implementations is configured in a seamless bidirectional manner The method of forwarding detection SBFD mechanism.

In an eighth aspect, the present application further provides a computer program product comprising instructions, which, when run on a computer, cause the computer to execute the method for configuring the seamless bidirectional forwarding detection SBFD mechanism in the above aspects.

In a ninth aspect, an apparatus for configuring a seamless bidirectional forwarding detection SBFD mechanism is provided, the apparatus including 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 bidirectional forwarding detection SBFD mechanism in the above aspects.

Description of drawings

1 is a schematic diagram of a network scenario applying an embodiment of the present application;

Fig. 2 is an example diagram of reachability detection performed by the SBFD mechanism;

3 is a schematic diagram of a method for configuring a seamless bidirectional 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 bidirectional forwarding detection SBFD mechanism according to an embodiment of the present application;

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

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

FIG. 7 is a schematic structural diagram of an apparatus for configuring a seamless bidirectional forwarding detection SBFD mechanism according to another embodiment of the present application.

Detailed ways

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

The technical solutions of the embodiments of the present application are applicable to a network supporting segment routing (SR) technology or SRPolicy technology, wherein 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 this embodiment 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, which is not limited in this embodiment of the present application.

SR policy technology is a new tunnel traffic diversion technology developed on the basis of SR technology. The SR-TE path calculation calculates the tunnel path according to the Color attribute required by the service level agreement (Service Level Agreement, SLA) representing the service tunnel. The service network head node matches the corresponding tunnel through the extended service route Color community attribute and the network remote node information to realize service traffic forwarding. The SR Policy technology can customize SR tunnel paths for services with specific SLA requirements, and implement application-level service forwarding network segmentation. For a further detailed description of the SR policy, reference may be made to the introduction of the prior art, which will not be repeated here.

In order to facilitate understanding and description of the method proposed by the embodiments of the present application, the SR Policy service establishment process is first described with reference to FIG. 1 . 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 management) and forwarding nodes (for example, the forwarding nodes include 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 adjacency labels are pre-allocated by any forwarding node through IGP routing. The controller collects network topology and label space information through border gateway protocol link state (BGP-LS) messages. The controller provides an interface; the user plans the VPN service source and sink nodes (RT1-RT3) and traffic diversion strategies (correspondence between Color and tunnel service level agreement SLA path 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 the session of the BGP SR policy address family. In the (border gateway protocol, BGP) session packet, it 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 issues a 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 routes delivered by the tail node RT3, and generates a BGP routing table. The head node RT1 matches the stored BGP routes with the SR Policy BGP session packets sent by the controller, establishes an SR policy tunnel after successful matching, and attaches the next hop of the route to the SR policy tunnel. The next hop in the table matches BSID 30027 and the traffic is directed to the SR policy tunnel for forwarding.

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

Some terms or concepts involved in the embodiments of the present application are introduced below.

SBFD is a rapid detection protocol. SBFD achieves reachability detection by rapidly and uninterruptedly publishing protocol packets. As shown in Figure 2, the SBFD mechanism is divided into an initiator and a reflector. Before link detection, the initiator and the reflector notify each other of information such as SBFD descriptors (Discriminators) by sending SBFD Control Packets to each other. During link detection, the initiator actively sends an SBFD Echo packet, the reflector loops back this packet according to the local situation, and the initiator determines the local state according to the reflected packet. When SBFD is applied to SR scenario detection, there are mainly two scenarios: SBFD for SR LSP and SBFD for SR-TE LSP. In the SBFD detection SR scenario, the path from the SBFD initiator to the reflector uses MPLS label forwarding, and the return path from the reflector to the initiator uses a multi-hop IP path.

As the detection end, the initiator has SBFD state machine mechanism and detection mechanism. The state machine of the initiator has only Up and Down states, and only sends packets in Up and Down states, and can only receive Up or Admin Down state packets. SBFD packets are sent from the initiator to the reflector. The initial status of the packets is Down, and the destination port number of the packets is 7784. For a further detailed description of the SBFD, reference may be made to the introduction of the prior art, which will not be repeated here.

It should be understood that, in this embodiment of the present application, the head and tail nodes should not be confused with the initiating reflection end. Among them, the head node and the tail node are distinguished from the point of entry and exit of the traffic of the tunnel in the network; the initiator and the reflector are distinguished from the point of view of packet reachability detection in the SBFD mechanism. 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 nodes are all statically configured by the user, which does not support selective management based on service dynamics, and is not flexible enough. The embodiment of the present application proposes a method for configuring a seamless bidirectional forwarding detection SBFD mechanism, which dynamically configures an SBFD instance for a forwarding node, which can realize more flexible dynamic deployment.

FIG. 3 shows a schematic diagram of a method 300 for configuring a seamless bidirectional forwarding detection SBFD mechanism according to an embodiment of the present application. The method 300 is applied to a network supporting segment routing traffic engineering SR-TE, the network including a controller and a plurality of forwarding nodes. As shown in FIG. 3, the method 300 includes:

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

The SR service may be an SR Policy service. For the related configuration process of the SR Policy service, please refer to the above description.

Optionally, the SBFD configuration information includes one or more of the following: a field used to indicate the transceiver type of the first forwarding node, a field used to indicate whether the SBFD configuration information is SBFD (For example, when the field value is 1, it means SBFD, and when the field value is 0, it means normal BFD), the field of the local identifier resource pool of the first forwarding node, and the peer identifier of the first forwarding node Resource pool fields, reserved fields.

The controller can extend the address family to the BGP protocol and add the above-mentioned SBFD configuration information. For example, the controller adds a BFD extended community (extend community) attribute based on the BGPSR-Policy multi-protocol extended address family, which is used to carry the above-mentioned SBFD configuration information. That is, the controller can advertise the above-mentioned SBFD configuration information through the BGP SR-Policy address family route. Optionally, the SBFD configuration information includes one or more of the following: a field used to indicate the transceiver type of the first forwarding node, a field used to indicate whether the SBFD configuration information is SBFD , a field of the local identifier resource pool of the first forwarding node, a field of the peer identifier resource pool of the first forwarding node, and other fields. For example, the field used to indicate the transceiver type of the first forwarding node may be the Flags field to indicate whether the first forwarding node is an initiator or a 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 common BFD or SBFD types); the field of the local discriminator resource pool of the first forwarding node may be the Local Discriminators field; the first forwarding node Fields such as the peer discriminator resource pool field can be the Remote Discriminators 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 control packets, A field used to indicate the minimum reception interval of control packets (Min-rx-interval field), a field used to indicate the local detection multiple of BFD sessions (Detect-multiplier field), a field used to indicate authentication data (key) A field (Auth Lenth field) of length information of a part, a field (Auth Type field) for indicating the authentication type of the control message, a field (Authentication Data field) for indicating authentication data, and the like. It should be understood that the control packet here can be a BFD control packet or an SBFD control packet, which is not specifically limited. The specific control packet can be based on which BFD mechanism needs to be configured on the controller (such as the SBFD mechanism or the SBFD mechanism). Ordinary BFD mechanism or LinkBandle 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, which may be determined based on actual requirements. For example, the fields included in the SBFD configuration information may be one or more of the above fields , and can include other fields as well.

For example, the BGP protocol can be extended as follows, so that the SBFD configuration information is carried in the BGP protocol, and an example of a format for adding an extended community attribute to the BGP protocol is as follows:

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

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 at the same time, multiple BFD extended community attributes need to be carried.

Among them, the Flags field format is as follows:

0 1 2 3 4 5 6 7

+-+-+-+-+-+-+-+-+

|R|P|Reserved| (Reserved reserved field is set to 0 by default)

+-+-+-+-+-+-+-+-+

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

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

When the R bit is set to 0, it indicates the initiator of SBFD. At this time, the local discriminator field carries the local discriminator required to create SBFD or BFD, and the length is 4 bytes; the remote discriminator The RemoteDiscriminatior field carries Create the far-end specifier required for SBFD or BFD. In particular, when the localDiscriminatior field is , it indicates that the segment discriminator 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 , it indicates that the remote discriminator for creating an SBFD instance is not specified, and can be configured locally or automatically generated by the forwarding node.

When the R bit is set to 1, it indicates the reflector of the SBFD. In this case, the local discriminator field carries the reflector discriminatior (Reflector Discriminatior) required to create SBFD or BFD, and the RemoteDiscriminatior field is set to zero by default.

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

Exemplarily, in this embodiment of the present application, the Min-tx-interval field may carry the minimum sending interval of the BFD control packet, and the unit is microseconds. It should be understood that the "BFD control message" involved in the above "Min-tx-interval field" is only an example, and the embodiment of this application does not limit the type of BFD, which may be ordinary BFD or SBFD, depending on Which BFD mechanism the controller configures for the forwarding node. That is to say, the "BFD control message" involved in the "optional field" may also be replaced with an "SBFD control message". The "BFD control packet" involved in the following optional fields can also be similarly interpreted, and will not be repeated below.

In this embodiment of the present application, the Min-rx-interval field may carry the minimum receiving interval of the BFD control packet, and the unit is microseconds. In this embodiment of the present application, the local detection multiple of the BFD session may be carried through the Detect-multiplier field. In this embodiment of the present application, the Auth Type field can carry the authentication type of the BFD control packet, and there are the following values:

0-Reserved

1-Simple Password

2-Keyed MD5

3-Meticulous Keyed MD5

4-Keyed SHA1

5-Meticulous Keyed SHA1

6-255-Reserved for future use

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

In this embodiment of the present application, the Auth Lenth field may carry the length information of the authentication data (secret key) part.

In this embodiment of the present application, authentication data (key) information may be carried 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 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 the SBFD configuration information required for the first forwarding node SBFD instance. information, so that the first forwarding node can 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 SBFD information about the configuration parameters. Among them, "adjusting the configuration parameters of the configured SBFD" can be interpreted as operations such as "adding, updating or deleting the configuration parameters of the configured SBFD".

S320, the controller sends a BGP packet to the first forwarding node, where the BGP packet carries the SBFD configuration information. Correspondingly, the first forwarding node receives the BGP packet 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 an 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 communicates with the first forwarding node. The peer node corresponding to the forwarding node performs SBFD negotiation. The opposite 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 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 a head node, which is not specified. limited.

Optionally, the SBFD configuration information may be delivered independently, 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, local discriminator field, and remote discriminatior field of the Flag field in the SBFD configuration information 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 BGPSR-Policy route may be as follows:

The specific format of the Flags field is as follows:

0 1 2 3 4 5 6 7

+-+-+-+-+-+-+-+-+

|0|0|Reserved| (Reserved reserved field is set to 0 by default)

+-+-+-+-+-+-+-+-+

In the SBFD configuration information received by the 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 LocalDiscriminatior field can be set to this A specific value in the end-specifier resource pool, in particular, when set to 0, it is configured locally or automatically generated by the forwarding node.

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 use Local Discriminatior and Remote Discriminatior to match to create an SBFD instance.

If the total length of the fields corresponding to the above 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 (optional parameter) field.

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

Optionally, the controller may specify the minimum packet sending/receiving interval, the detection time period and the authentication encryption algorithm for the head node through the above-mentioned Optional Para field.

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 above-mentioned first forwarding node is a tail node, the format of the SBFD configuration information received by the tail node in the BGPSR-Policy route can be as follows:

Among them, the Flags field format is as follows:

0 1 2 3 4 5 6 7

+-+-+-+-+-+-+-+-+

|1|0|Reserved| (Reserved reserved field is set to 0 by default)

+-+-+-+-+-+-+-+-+

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

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

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 have received the BFD extended community attribute delivered by the controller, and after the head node and the tail node complete the service deployment according to the above-mentioned 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 will describe the situations of whether or not 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 implementation method:

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;

The first forwarding node configures the SBFD instance associated with the SR service according to the SBFD configuration information, including:

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

If the SBFD mechanism is not configured in the first forwarding node, the controller can individually deliver the SBFD configuration information to the first forwarding node through a BGP packet, or it can simultaneously deliver the SR service creation information and the SBFD configuration through a BGP packet. information. Here, since SBFD is not configured in the first forwarding node, the SBFD configuration information needs to include all necessary information for creating SBFD.

Specifically, for the case where the first forwarding node is the head node, when the head node receives the BGP message sent by the controller to create the SR service information and the SBFD configuration information at the same time, it can first create the SR based on the BGP message The SR-Policy service is created based on the service information, and the SBFD instance associated with the SR-Policy service is created immediately after the SR-Policy service is established. In the case where the first forwarding node is the tail node, in the scenario of a bidirectional tunnel, after receiving the SR service creation information and SBFD configuration information sent by the controller, the tail node can first create an SR service based on the information in the packet. Create the SR-Policy service, and create the SBFD instance associated with the SR-Policy service immediately after the SR-Policy service is established. Configure the reflector side. After the SBFD instance is created, wait for SBFD negotiation with the head node. Or, in the scenario of establishing a unidirectional tunnel, when the tail node does not need the information for creating the SR-Policy service sent by the controller, the network layer reachable information of the SR service received by the tail node (network layer reachable information) , NLRI) will be set to zero (zero means that the BGP packet sent by the controller to the tail node will not carry the information for creating 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 first creates the SR-Policy service or first creates the SBFD instance, which may be determined based on actual requirements.

After the SBFD instances in 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 implement:

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

The first forwarding node adjusts the configured configuration parameters of the 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 the information for creating an SBFD instance in the BGP message. The first forwarding node may use the original statically configured basic configuration of the SBFD, such as a local static configuration or an automatically generated configuration value. Here, the SBFD configuration information sent by the controller to the first forwarding node may carry some information in the SBFD as a supplement to the binding policy and/or parameters corresponding to the SBFD configuration. For example, in the fields included in the SBFD configuration information, the Local Discriminatior and the Remote Discriminatior can be set to zero, and the Local Discriminatior and the Remote Discriminatior can be set to zero. The information of the Local Discriminatior and the Remote Discriminatior is not carried, and the rest of the fields can be controlled The server 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 LocalDiscriminatior 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 some information, so that the first forwarding node can adjust the parameters of the basic SBFD 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 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 this embodiment of the present application, the BGP message sent by the controller to the first forwarding node may carry the SR service and the configuration information of the SBFD instance associated with the SR service. In particular, when the SBFD instance associated with the SR service needs to be deleted, that is, when the SR service is no longer associated with the SBFD instance, the BGP packet 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 can 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 created SBFD instance, which can release resources and help reduce the occupation of forwarding nodes and network resources.

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

Optionally, the SBFD configuration information in this embodiment of the present application may be associated with multiple SR services. When delivering BGP packets to the forwarding node, the controller may deliver multiple BGP packets corresponding to multiple SR services to the first forwarding node, wherein each BGP packet carries the same SBFD configuration information. The first forwarding node may multiplex the SBFD configuration information to multiple different SR services when receiving such BGP packets.

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

It should be understood that the method for configuring the seamless bidirectional forwarding detection SBFD mechanism in the embodiment of the present application is described by taking the configuration of SBFD as an example, and the technical solution in the embodiment of the present application is also applicable to the dynamic deployment of ordinary BFD, Link Bandle BFD, or other BFDs. , which is not limited. For example, the configuration information of common BFD can be extended to other BGP service address families, or a special BFD control address family can be added.

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 perform equivalent transformations or adjustments based on the above examples, and these equivalent transformations or adjustments should be fall into the protection scope of the embodiments of the present application.

The method for configuring a seamless bidirectional forwarding detection SBFD mechanism according to an embodiment of the present application is described in detail above with reference to FIGS. 1 to 3 . An apparatus for configuring a seamless bidirectional forwarding detection SBFD mechanism according to an embodiment of the present application will be described below with reference to FIG. 4 to FIG. 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 bidirectional forwarding detection SBFD mechanism according to an embodiment of the present application. Alternatively, apparatus 400 may be a controller. As shown in FIG. 4, the apparatus 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 in the plurality of 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 packet to the first forwarding node, where the BGP packet carries the SBFD configuration information.

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

In the 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;

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

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

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 contents: a field used to indicate the transceiver type of the first forwarding node, a field used to indicate the SBFD configuration information Whether it is a field of SBFD, a field of the local end discriminator resource pool of the first forwarding node, a field of the opposite end discriminator resource pool of the first forwarding node.

It should be understood that the apparatus 400 according to this embodiment of the present application may correspond to the method on the controller side in the foregoing method embodiments, and the above-mentioned and other management operations and/or functions of each module in the apparatus 400 are respectively to implement the corresponding methods of the foregoing methods. Therefore, the beneficial effects in the foregoing method embodiments can also be achieved. For the sake of brevity, details are not described here.

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

Processor 501 , memory 502 and transceiver 503 .

The processor 501, the memory 502 and the transceiver 503 communicate with each other through an internal connection path to transmit control and/or data signals. In one possible design, the processor 501, the memory 502 and the transceiver 503 may be implemented in a chip. The memory 502 can 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 an SBFD mechanism configuration state of a first forwarding node in the plurality of forwarding nodes, where the SBFD configuration information includes: configuring an SBFD associated with a segment routing SR service Information required by the instance; the transceiver 503 is configured 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 implementation manner, the transceiver may be implemented by being divided into two components: 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 apparatus 600 is applied to a network supporting segment routing traffic engineering SR-TE, and the network includes a controller and a plurality of forwarding nodes. Optionally, the apparatus 600 is a first forwarding node among the plurality of forwarding nodes. As shown in FIG. 6, the apparatus 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, where the SBFD configuration information includes: the configuration required for the SBFD instance associated with the segment route SR service information;

a processing module 620, 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 perform SBFD negotiation with the opposite node corresponding to the first forwarding node after the SBFD instance associated with the SR service is successfully configured.

In a possible implementation manner, in the case that 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 processing module 620 is configured to configure the SBFD instance associated with the SR service according to the SBFD configuration information, specifically including:

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

In a possible implementation manner, in the case where the SBFD mechanism is configured in the first forwarding node, the SBFD configuration information includes a parameter for adjusting the configuration parameters of the SBFD configured in the first forwarding node information; wherein, the processing module 620 is configured to configure the 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 the information of 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 used to indicate the transceiver type of the first forwarding node, a field used to indicate whether the SBFD configuration information is SBFD , a field of the local end discriminator resource pool of the first forwarding node, and a field of the opposite end discriminator resource pool of the first forwarding node.

It should be understood that the apparatus 600 according to this embodiment of the present application may correspond to the method on the forwarding node side in the foregoing method embodiments, and the above-mentioned and other management operations and/or functions of the various modules in the apparatus 600 are to implement the corresponding methods of the foregoing methods, respectively. Therefore, the beneficial effects in the foregoing method embodiments can also be achieved. For the sake of brevity, details are not described here.

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

Processor 701 , memory 702 and transceiver 703 .

The processor 701, the memory 702 and the transceiver 703 communicate with each other through an internal connection path to transmit control and/or data signals. In one possible design, the processor 701, the memory 702 and the transceiver 703 may be implemented in a chip. The memory 702 can 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, where the SBFD configuration information includes: required for configuring the SBFD instance associated with the segment route SR service information; the processor 701 is configured to configure the 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 implementation manner, the transceiver may be implemented by being divided into two components: a receiver and a transmitter.

The present application also provides a network including a controller and a plurality of forwarding nodes. The controller may execute the methods described above for execution by the controller. The first forwarding node may be included in the plurality of 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.

Embodiment 1. A method for configuring a seamless bidirectional forwarding detection SBFD mechanism, wherein the method is applied to a network supporting segment routing traffic engineering SR-TE, and the network includes a controller and a plurality of forwarding nodes, The method includes:

The controller determines SBFD configuration information according to the SBFD mechanism configuration state of the first forwarding node in the plurality of forwarding nodes, where the SBFD configuration information includes: the configuration required for the SBFD instance associated with the segment routing SR service. information;

The controller sends a Border Gateway Protocol BGP packet to the first forwarding node, where the BGP packet carries the SBFD configuration information.

Embodiment 2. The method according to Embodiment 1, wherein the controller determines the SBFD configuration information according to the SBFD mechanism configuration state of the first forwarding node in the plurality of forwarding nodes, including:

In the 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;

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

Embodiment 3. The method according to Embodiment 1 or 2, wherein the BGP packet further carries the information of the SR service.

Embodiment 4. The method according to any one of Embodiments 1 to 3, wherein the SBFD configuration information is associated with multiple SR services.

Embodiment 5. The method according to any one of Embodiments 1 to 4, wherein the first forwarding node is a head node among the plurality of forwarding nodes, or the first forwarding node is a a tail node in the plurality of forwarding nodes.

Embodiment 6. The method according to any one of Embodiments 1 to 5, wherein the SBFD configuration information includes one or more of the following: A field of the transceiver type, a field used to indicate whether the SBFD configuration information is SBFD, a field of the local identifier resource pool of the first forwarding node, a field of the peer identifier resource pool of the first forwarding node. field.

Embodiment 7. A method for configuring a seamless bidirectional forwarding detection SBFD mechanism, characterized in that the method is applied to a network supporting segment routing traffic engineering SR-TE, and the network includes a controller and a plurality of 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 segment routing SR Information required by the SBFD instance associated with the business;

The first forwarding node configures the 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, the first forwarding node performs SBFD negotiation with a peer node corresponding to the first forwarding node.

Embodiment 8. The method according to Embodiment 7, wherein, in the case that the SBFD mechanism is not configured in the first forwarding node, the SBFD configuration information includes a method for the first forwarding node to create an SBFD. information required by the instance;

The first forwarding node configures the SBFD instance associated with the SR service according to the SBFD configuration information, including:

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

Embodiment 9. The method according to Embodiment 7, wherein, in a case where an SBFD mechanism is configured in the first forwarding node, the SBFD configuration information includes a method for adjusting the first forwarding node. Information about the configuration parameters of the configured SBFD; wherein, the first forwarding node configures the SBFD instance associated with the SR service according to the SBFD configuration information, including:

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

Embodiment 10. The method according to any one of Embodiments 7 to 9, wherein the BGP packet further carries the information of the SR service.

Embodiment 11. The method according to any one of Embodiments 7 to 10, wherein the SBFD configuration information is associated with a plurality of the SR services.

Embodiment 12. The method according to any one of Embodiments 7 to 11, wherein the first forwarding node is a head node in the plurality of forwarding nodes, or the first forwarding node is a a tail node in the plurality of forwarding nodes.

Embodiment 13. The method according to any one of Embodiments 7 to 12, wherein the SBFD configuration information includes one or more of the following: A field of the transceiver type, a field used to indicate whether the SBFD configuration information is SBFD, a field of the local identifier resource pool of the first forwarding node, a field of the peer identifier resource pool of the first forwarding node. field.

Embodiment 14. An apparatus for configuring a seamless bidirectional forwarding detection SBFD mechanism, wherein the apparatus is applied to a network supporting segment routing traffic engineering SR-TE, and the network includes a controller and a plurality of forwarding nodes, The device includes:

A determining module, configured to determine SBFD configuration information according to the SBFD mechanism configuration state of the first forwarding node in the plurality of forwarding nodes, where the SBFD configuration information includes: required for configuring the SBFD instance associated with the segment routing SR service Information;

A transceiver module, configured to send a border gateway protocol BGP message to the first forwarding node, where the BGP message carries the SBFD configuration information.

Embodiment 15. The apparatus according to Embodiment 14, wherein the determining module is configured to determine the SBFD configuration information according to the SBFD mechanism configuration state of the first forwarding node in the plurality of forwarding nodes, specifically including:

In the 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;

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

Embodiment 16. The apparatus according to Embodiment 14 or 15, wherein the BGP packet further carries the information of the SR service.

Embodiment 17. The apparatus according to any one of Embodiments 14 to 16, wherein the SBFD configuration information is associated with multiple SR services.

Embodiment 18: The apparatus according to any one of Embodiments 14 to 17, wherein the first forwarding node is a head node in the plurality of forwarding nodes, or the first forwarding node is a a tail node in the plurality of forwarding nodes.

Embodiment 19. The apparatus according to any one of Embodiments 14 to 18, wherein the SBFD configuration information includes one or more of the following: A field of the transceiver type, a field used to indicate whether the SBFD configuration information is SBFD, a field of the local identifier resource pool of the first forwarding node, a field of the peer identifier resource pool of the first forwarding node. field.

Embodiment 20. An apparatus for configuring a seamless bidirectional forwarding detection SBFD mechanism, wherein the apparatus is applied to a network supporting segment routing traffic engineering SR-TE, and the network includes a controller and a plurality of forwarding nodes, The apparatus is a first forwarding node among the plurality of forwarding nodes, and the apparatus includes:

A transceiver module, configured to receive a border gateway protocol BGP message sent by the controller, where the BGP message carries SBFD configuration information, where the SBFD configuration information includes: configuring the SBFD instance associated with the segment route SR service required information;

a processing module, configured to configure the SBFD instance associated with the SR service according to the SBFD configuration information;

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

Embodiment 21. The apparatus according to Embodiment 20, wherein, in the case where the SBFD mechanism is not configured in the first forwarding node, the SBFD configuration information includes a method for the first forwarding node to create an SBFD. information required by the instance;

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

Based on the SBFD configuration information, create a new SBFD instance associated with the SR service.

Embodiment 22. The apparatus according to Embodiment 20, wherein, in a case where an SBFD mechanism is configured in the first forwarding node, the SBFD configuration information includes a method for adjusting the SBFD in the first forwarding node. Information about the configuration parameters of the configured SBFD; wherein, the processing module is configured to configure the 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.

Embodiment 23. The apparatus according to any one of Embodiments 20 to 22, wherein the BGP packet further carries the information of the SR service.

Embodiment 24. The apparatus according to any one of Embodiments 20 to 23, wherein the SBFD configuration information is associated with multiple SR services.

Embodiment 25: The apparatus according to any one of Embodiments 20 to 24, wherein the first forwarding node is a head node in the plurality of forwarding nodes, or the first forwarding node is a a tail node in the plurality of forwarding nodes.

Embodiment 26. The apparatus according to any one of Embodiments 20 to 25, wherein the SBFD configuration information includes one or more of the following: A field of the transceiver type, a field used to indicate whether the SBFD configuration information is SBFD, a field of the local identifier resource pool of the first forwarding node, a field of the peer identifier resource pool of the first forwarding node. field.

The methods disclosed in the above embodiments of the present application may be applied to a processor, or implemented by a processor. A processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiments may be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software. The above-mentioned 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 off-the-shelf programmable gate array (FieldProgrammable Gate Array, FPGA) or other programmable A logic device, a discrete gate or transistor logic device, and a discrete hardware component may also be a system on chip (SoC), a central processor unit (CPU), or a network processor (network processor, NP), may also be a digital signal processing circuit (digital signal processor, DSP), may also be a microcontroller unit (micro controller unit, MCU), may also be a programmable logic device (programmable logic device, PLD) or other integrated chips. The methods, steps, and logic block diagrams disclosed in the embodiments of this application can be implemented or executed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the methods disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art. 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 this embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Wherein, the non-volatile memory may be Read-Only Memory (ROM), Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (Erasable PROM, EPROM), Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. The volatile memory may be random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), 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 link dynamic random access memory (Synchlink DRAM, SLDRAM) And direct memory bus random access memory (DirectRambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but not be limited to, these and any other suitable types of memory.

Various aspects or features of the present application may be implemented as methods, apparatus, or articles of manufacture 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, computer readable media may include, but are not limited to: magnetic storage devices (eg, hard disks, floppy disks, or magnetic tapes, etc.), optical disks (eg, compact discs (CDs), digital versatile discs (DVDs) etc.), smart cards and flash memory devices (eg, erasable programmable read-only memory (EPROM), cards, stick or key drives, etc.). Additionally, various storage media described herein can 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.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described systems, devices and units may refer to the corresponding processes 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, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. 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. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of 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 components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in 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 physically alone, or two or more units may be integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, removable hard disk, read-only memory ROM, random access memory RAM, magnetic disk or optical disk and other media that can store program codes.

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited to this. should be covered within the scope of protection of this application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims (21)

1. a method for configuring seamless bidirectional forwarding detection SBFD mechanism, is characterized in that, described method comprises: The controller determines SBFD configuration information, where the SBFD configuration information includes: information required for configuring the 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. 2. The method according to claim 1, wherein The SBFD configuration information includes information required for the forwarding node to create the SBFD instance; or The SBFD configuration information includes information for adjusting the configuration parameters of the SBFD instance configured in the forwarding node. 3. The method according to claim 1 or 2, wherein the BGP message further carries the information of the SR service. 4. The method according to any one of claims 1 to 3, wherein the SBFD configuration information is associated with multiple SR services. 5. 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. 6. The method according to any one of claims 1 to 5, wherein the SBFD configuration information includes one or more of the following: field, a field used to indicate whether the SBFD configuration information is SBFD, a field of the local end discriminator resource pool of the forwarding node, and a field of the opposite end discriminator resource pool of the forwarding node. 7. The method according to any one of claims 1-6, wherein the SBFD configuration information may further include one or more of the following contents: a minimum sending interval for sending BFD control packets; BFD control The authentication information of the packet. 8 . The method according to claim 1 , wherein the SBFD configuration information is carried in an extended community attribute newly added in the BGP message. 9 . 9. A method for configuring seamless bidirectional forwarding detection SBFD mechanism, characterized in that the method comprises: The forwarding node receives the Border Gateway Protocol BGP message sent by the controller, the BGP message carries SBFD configuration information, and the SBFD configuration information includes: information required for configuring the SBFD instance associated with the segment route SR service; The forwarding node configures the SBFD instance according to the SBFD configuration information. 10. The method according to claim 9, wherein the forwarding node configures the SBFD instance according to the SBFD configuration information, comprising: The forwarding node creates the SBFD according to the SBFD configuration information. 11. The method according to claim 9, wherein the forwarding node configures the SBFD instance according to the SBFD configuration information, comprising: 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-11, wherein the BGP message further carries the information of the SR service. 13. The method according to any one of claims 9-12, wherein the SBFD configuration information is associated with a plurality of the SR services. 14. 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. 15. The method according to any one of claims 9-14, wherein the SBFD configuration information includes one or more of the following contents: used to indicate a transceiver of the first forwarding node A field of type, a field used to indicate whether the SBFD configuration information is SBFD, a field of the local end specifier resource pool of the first forwarding node, and a field of the opposite end specifier resource pool of the first forwarding node. 16. The method according to any one of claims 9-15, wherein the SBFD configuration information can further include one or more of the following contents: a minimum sending interval for sending BFD control packets; BFD control The authentication information of the packet. 17. The method according to any one of claims 9-16, wherein the SBFD configuration information is carried in an extended community attribute newly added in the BGP message. 18. A controller, characterized in that it comprises: memory, storing instructions; A processor in communication with the memory, the processor executing the instructions to cause the apparatus to perform the method of any of claims 1-8. 19. A forwarding node, comprising: memory, storing instructions; A processor in communication with the memory, the processor executing the instructions to cause the apparatus to perform the method of any of claims 9-17. 20. A computer-readable storage medium, comprising computer-readable instructions that, when executed on a computer, cause the computer to perform the method of any one of claims 1-17. 21. A communication system, comprising the controller of claim 18 and the forwarding node of claim 19.

Images