CN111385165A

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

Info

Publication number: CN111385165A
Application number: CN201911129891.XA
Authority: CN
Inventors: 邰博; 吕金生; 王丽娜; 王海波; 胡志波; 唐宏
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-12-28
Filing date: 2018-12-28
Publication date: 2020-07-07
Anticipated expiration: 2038-12-28
Also published as: CN109587009A; CN111385165B; WO2020134739A1; CN109587009B

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

Segment Routing (SR) is a protocol designed based on the concept of source routing to forward packets over a network. SR multi-protocol label switch (MPLS) refers to Segment Routing based on the MPLS forwarding plane. Segment routing-traffic engineering (SR-TE) is a new TE tunneling technique that uses SR as a control protocol. SR-TE refers to a tunnel created with SR protocol based on TE's constrained properties. The controller is responsible for calculating the forwarding path of the tunnel and issuing the label stack strictly corresponding to the path to the forwarder. On the entry node of the SR-TE tunnel, the repeater can control the transmission path of the message in the network according to the label stack.

Since no protocol is established in SR-TE, as long as the label stack is issued, a link-state packet (LSP) is successfully established, and except for removing the label stack, the LSP does not have the protocol Down. Therefore, SR-TE LSP failure detection requires switching backup LSPs through Bidirectional Forwarding Detection (BFD) detection by deploying BFD detection. Seamless bidirectional forwarding detection (SBFD, BFD) simplifies the state machine of BFD, shortens negotiation time, improves the flexibility of the whole network, and can support SR tunnel detection. SBFD is currently used to provide protection for SR Policy (Policy) traffic. However, SBFD currently only supports static configuration on the forwarder, and static configuration of SBFD instance and parameters provides end-to-end fault detection for the already created SR Policy tunnel, and tunnel protection cannot be dynamically provided in time.

Disclosure of Invention

In view of this, the present application provides a method and an apparatus for configuring a Seamless Bidirectional Forwarding Detection (SBFD) mechanism, which can implement dynamic deployment of SBFD and help provide tunnel protection in time.

In a first 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 comprises a controller and a plurality of forwarding nodes, and the method comprises: the controller determines SBFD configuration information according to the 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; the controller sends a BGP message to the first forwarding node, wherein the BGP message carries the SBFD configuration information, that is, the controller can dynamically configure the SBFD instance for the forwarding node without statically configuring the SBFD instance for the forwarding node by a user, thereby realizing more flexible dynamic deployment and being beneficial to timely providing tunnel protection.

Optionally, the SR service is an SR Policy service.

In one possible implementation manner, the determining, by the controller, SBFD configuration information according to the SBFD mechanism configuration status of the first forwarding node in the plurality of forwarding nodes includes: under the condition that an SBFD mechanism is not configured in the first forwarding node, the SBFD configuration information comprises information required by the first forwarding node for creating an SBFD instance; in a case that an SBFD mechanism is configured in the first forwarding node, the SBFD configuration information includes information for adjusting configuration parameters of an SBFD configured in the first forwarding node. Therefore, no matter whether the SBFD mechanism is configured in the first forwarding node or not, the controller may generate corresponding SBFD configuration information for the first forwarding node, so that the first forwarding node establishes or adjusts an SBFD instance based on the SBFD configuration information to meet the requirement of the forwarding node.

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

In one possible implementation, the SBFD configuration information is associated with a plurality of SR services.

In one possible implementation, the first forwarding node is a head node of the plurality of forwarding nodes, or the first forwarding node is a tail node of the plurality of forwarding nodes.

In one possible implementation manner, the SBFD configuration information includes one or more of the following: a field for indicating a transceiving end type of the first forwarding node, a field for indicating whether the SBFD configuration information is an SBFD, a field of a home delimiter resource pool of the first forwarding node, and a field of an opposite delimiter 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 Bidirectional Forwarding Detection (SBFD) mechanism is provided, the method is applied to a network supporting segment routing traffic engineering (SR-TE), the network comprises a controller and a plurality of forwarding nodes, and the method comprises: a first forwarding node of the multiple forwarding nodes receives a Border Gateway Protocol (BGP) message sent by the controller, wherein the BGP message carries SBFD configuration information, and the SBFD configuration information comprises: configuring information required by an SBFD instance associated with a Segment Routing (SR) service; the first forwarding node configures an SBFD instance associated with the SR service according to the SBFD configuration information; and after the configuration of the SBFD instance associated with the SR service is successful, the first forwarding node performs SBFD negotiation with an opposite node corresponding to the first forwarding node. Therefore, the first forwarding node can dynamically configure the SBFD instance based on the SBFD configuration information sent by the controller, and does not need a user to statically configure the SBFD instance for the first forwarding node, so that more flexible dynamic deployment can be realized, and tunnel protection can be provided in time.

Optionally, the SR service is an SR Policy service.

In a possible implementation manner, in a case that 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; and the first forwarding node establishes an 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 issued by the controller.

In a possible implementation manner, in a case that an SBFD mechanism is configured in the first forwarding node, the SBFD configuration information includes information for adjusting configuration parameters of an SBFD configured in the first forwarding node; and the first forwarding node adjusts the configured configuration parameters of the 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 issued by the controller.

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

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

In a fourth aspect, a forwarding node is provided, which comprises means for performing the method of the second aspect or any possible implementation manner of the second aspect.

In a fifth aspect, a network is provided, where the network includes a controller and a plurality of forwarding nodes, where the controller is configured to perform the method in the first aspect or any possible implementation manner of the first aspect; a first forwarding node of the plurality of forwarding nodes is configured to perform the method of the second aspect or any possible implementation manner of the second aspect.

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

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

In a sixth aspect, there is provided a computer readable storage medium storing a program for causing a controller to execute the first aspect described above, and any of its various implementations, to configure a method of a seamless bidirectional forwarding detection, SBFD, mechanism.

In a seventh aspect, a computer-readable storage medium is provided, which stores a program that causes a forwarding node to execute the second aspect described above, and any of its various implementations, to configure a method of seamless bidirectional forwarding detection, SBFD, mechanism.

In an eighth aspect, the present application also provides a computer program product containing instructions which, when run on a computer, cause the computer to perform the method of configuring a seamless bidirectional forwarding detection, SBFD, mechanism of the above aspects.

In a ninth aspect, an apparatus for configuring a Seamless Bidirectional Forwarding Detection (SBFD) mechanism is provided and includes a processor, a memory, and a transceiver. The processor is coupled to the memory and the transceiver. The memory is for storing instructions, the processor is for executing the instructions, and the transceiver is for communicating with other network elements under control of the processor. When the processor executes the memory-stored instructions, the execution causes the processor to perform the method of configuring the Seamless Bidirectional Forwarding Detection (SBFD) mechanism in the above aspects.

Drawings

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

fig. 2 is an exemplary diagram of the SBFD mechanism for reachability detection;

FIG. 3 is a schematic diagram of a method of configuring a Seamless Bidirectional Forwarding Detection (SBFD) mechanism according to an embodiment of the present application;

FIG. 4 is a schematic block diagram of an apparatus configured with a Seamless Bidirectional Forwarding Detection (SBFD) mechanism according to an embodiment of the present application;

FIG. 5 is a schematic block diagram of an apparatus configured with a Seamless Bidirectional Forwarding Detection (SBFD) mechanism according to another embodiment of the present application;

FIG. 6 is a schematic block diagram of an apparatus configured with a Seamless Bidirectional Forwarding Detection (SBFD) mechanism according to an embodiment of the present application;

fig. 7 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.

Detailed Description

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

The technical scheme of the embodiment of the application is suitable for a network supporting a Segment Routing (SR) technology or an SRpolicy technology, wherein the network comprises a controller and a plurality of forwarding nodes. For example, the network may be an SDN network. The tunnel established between forwarding nodes may be a segment-routing-traffic engineering (SR-TE) tunnel. The forwarding node supports 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 of a packet or data, which is not limited in this embodiment of the present application.

The SR policy technology is a new tunnel drainage technology developed on the basis of the SR technology. The SR-TE calculation path calculates a tunnel path according to a Color attribute required by a Service Level Agreement (SLA). And the service network head node matches the corresponding tunnel through the expanded service routing Color community attribute and the information of the network far-end node to realize service flow forwarding. By the SR Policy technology, the SR tunnel path can be customized for the service with specific SLA requirements, and the application-level service forwarding network subdivision is realized. Further details of SR policy can be found in the introduction to the prior art and will not be described herein.

For convenience of understanding and describing the method proposed in the embodiments of the present application, first, an SR Policy service establishment procedure is 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 manager) and forwarding nodes (e.g., the forwarding nodes include a head node RT1, a middle node RT2, and a tail node RT 3). The controller may issue SR policy messages to the head node RT1 and the tail node RT3 in order to deploy SR policy services in the network. The node label and the adjacency label are pre-assigned by any forwarding node through the IGP route. 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 a drainage strategy (Color and a tunnel service level agreement SLA calculation path constraint corresponding relation) for specific private network users. The controller calculates an 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 a SR policy Border Gateway Protocol (BGP) session message through a session of a BGP SR policy address family, and sends the BGP label stack to the head node RT 1. The tail node RT3 injects Color extended community attribute into the private network route of a specific user and issues BGP routing strategy. The tail node RT3 publishes the BGP route carrying the Color community attribute to the head node RT 1. The head node RT1 stores the BGP route issued by the tail node RT3 and generates a BGP route table. The head node RT1 matches with SR Policy BGP session message issued by the controller based on the stored BGP route, establishes SR Policy tunnel after matching is successful, hangs the next hop of the route to the SR Policy tunnel, and guides the flow to the SR Policy tunnel for forwarding by the specific user flow at the entrance according to the next hop matching BSID 30027 of the routing table.

The head node RT1 refers to the traffic ingress node. Tail node RT3 refers to a traffic egress node.

Some terms or concepts related to the embodiments of the present application are described below.

SBFD is a fast detection protocol. The SBFD achieves the purpose of reachability detection by rapidly and uninterruptedly issuing protocol messages. As shown in fig. 2, the SBFD mechanism is divided into an initiating end and a reflecting end, and before link detection, the initiating end and the reflecting end notify information such as an SBFD descriptor (descriptor) by sending an SBFD Control Packet (SBFD Control Packet) to each other. During link detection, the initiating terminal actively sends an SBFD Echo message, the reflecting terminal loops back the message according to the condition of the home terminal, and the initiating terminal determines the state of the home terminal according to the reflecting message. When the SBFD is applied to SR scene detection, two scenes, namely an SBFD for SR LSP and an SBFDfor SR-TE LSP, are mainly used. In the SBFD detection SR scene, the path from the SBFD initiating terminal to the reflecting terminal is forwarded by an MPLS label, and the returning path from the reflecting terminal to the initiating terminal is a multi-hop IP path.

The initiating end is used as a detecting end and is provided with an SBFD state machine mechanism and a detecting mechanism. The state machine of the initiating end only has the Up state and the Down state, the sent message only has the Up state and the Down state, and only can receive the Up state message or the Admin Down state message. The SBFD message is sent from the initiating terminal to the reflecting terminal, the initial state of the message is Down, and the destination port number of the message is 7784. Further details of SBFD can be found in the introduction to the prior art and are not described herein.

It should be understood that in the embodiments of the present application, the head-to-tail nodes should not be mixed with the reflection-initiating end. Wherein, the head node and the tail node are distinguished from the angle of the exit and the entrance of the flow of the tunnel in the network; the initiating terminal and the reflecting terminal are distinguished by the angle of message reachability detection in an SBFD mechanism. For example, in the SBFD mechanism, a head node may be an initiating end, and a corresponding tail node may be a reflecting end; alternatively, the head node may be the reflection end and the corresponding tail node may be the initiation end.

In the prior art, the SBFD instances in the forwarding nodes are all statically configured by the user, and do not support dynamic selective management based on services, which is not flexible enough. The embodiment of the application proposes a method for configuring a Seamless Bidirectional Forwarding Detection (SBFD) mechanism, dynamically configures an SBFD instance for a forwarding node, and can realize more flexible dynamic deployment.

Fig. 3 shows a schematic diagram of a method 300 of 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, comprising 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 an SBFD mechanism configuration state of a first forwarding node of the plurality of forwarding nodes, where the SBFD configuration information includes: configuring information required for SBFD instances associated with segment routing SR traffic.

The SR service may be an SR Policy service. The relevant configuration flow of the SR Policy service can be referred to the above description.

Optionally, the SBFD configuration information includes one or more of the following: a field for indicating a transceiver end type of the first forwarding node, a field for indicating whether the SBFD configuration information is SBFD (for example, when the field value is 1, the field indicates SBFD, and when the field value is 0, the field indicates normal BFD), a field of a home terminal specifier resource pool of the first forwarding node, a field of an opposite terminal specifier resource pool of the first forwarding node, and a reserved field.

The controller may extend an address family to the BGP protocol and add the SBFD configuration information. For example, the controller adds an extended community (BFD community) attribute for carrying the SBFD configuration information based on the BGPSR-Policy multiprotocol extension address family. That is, the controller may distribute the SBFD configuration information via BGP SR-Policy address family routing. Optionally, the SBFD configuration information includes one or more of the following: a field for indicating a transceiving end type of the first forwarding node, a field for indicating whether the SBFD configuration information is an SBFD, a field of a home terminal specifier resource pool of the first forwarding node, a field of a peer terminal specifier resource pool of the first forwarding node, and the like. For example, the field for indicating the transceiving end type of the first forwarding node may be a Flags field to indicate whether the first forwarding node is an originating end or a reflecting end; the field for indicating whether the SBFD configuration information is SBFD may be a Type field to indicate a Type of the SBFD configuration information (the Type may include a Type of normal BFD or SBFD, etc.); the field of the Local identifier resource pool of the first forwarding node may be a Local identifiers field; the field of the peer specifier resource pool of the first forwarding node, etc. may be a Remote specifiers field.

Optionally, the SBFD configuration information may further include other Optional fields, such as Optional Para (Variable), which specifically includes: a field for indicating a minimum transmission interval of the control packet (Min-tx-interval field), a field for indicating a minimum reception interval of the control packet (Min-rx-interval field), a field for indicating a local detection multiple for detecting the BFD session (Detect-multiplexer field), a field for indicating length information of an Authentication Data (key) part (Auth length field), a field for indicating an Authentication Type of the control packet (Auth Type field), and a field for indicating Authentication Data (Authentication Data field), etc. It should be understood that the control message may be a BFD control message or an SBFD control message, which is not limited to this, and the specific control message may be determined based on which BFD mechanism (such as an SBFD mechanism or a general BFD mechanism or a link binding LinkBandle BFD mechanism) the controller needs to configure. It should be understood that, in the embodiment of the present application, the field included in the SBFD configuration information is not specifically limited, and may be determined based on actual requirements, for example, the field included in the SBFD configuration information may be one or more of the above fields, and may also include other fields.

For example, the BGP protocol may be extended as follows, so that the BGP carries the SBFD configuration information, and an example of a format of an attribute of a newly added extended community of the BGP protocol is specifically as follows:

based on the above, the expanded BGP message carries a Type field, a flag field, a reserved field, a local specifier field, a Remote specifier field, an Optional parameter operational Para or variable (variable) field, and so on.

The Type field is used to identify the Type of BFD, for example, Type 0x00 indicates that the BFD (e.g., RFC5880) configuration information is carried, and Type 0x01 indicates that the SBFD configuration information is carried. Optionally, if multiple types of BFDs need to be deployed simultaneously, multiple BFD extended community attributes need to be carried.

Wherein, the format of the Flags field is as follows:

0 1 2 3 4 5 6 7

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

| R | P | Reserved | (Reserved field default set 0)

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

In the Flags field, an R bit indicates a Reflector for indicating a reflection end or an initiation end of the SBFD. For example, when R is set to 1, it represents the reflective end of SBFD; when R is set to 0, it indicates the initiation of SBFD.

In the Flags field, a P bit indicates Passive, indicating the reflection end or the initiation end of BFD. Setting 1 indicates the reflection end of the normal BFD, and setting 0 indicates the initiation end of the normal BFD.

When the R bit is set to 0, the R bit represents the initiating end of the SBFD, and at this time, the local discriminator field carries the local discriminator needed for creating the SBFD or BFD, and the length of the local discriminator is 4 bytes; the remote specifier remotedspecifiator field carries the remote specifier required to create SBFD or BFD. In particular, when the localdescrimitator field is, the segment identifier indicating that no specific designation of creation of SBFD or BFD is made may be configured locally by the forwarding node or automatically generated. In particular, when the Remote descriptor field is, a Remote specifier indicating that no specific specification is made to create an SBFD instance may be configured locally by the forwarding node or automatically generated.

When the R bit is set to 1, it indicates the reflection end of SBFD, and at this time, the local discriminator field carries the reflection end discriminator (Reflector discriminator) required for creating SBFD or BFD, and the remotediscriminator field is set to zero by default.

Wherein, the format of the Optional Para field is as follows:

illustratively, in the embodiment of the application, the minimum transmission interval of the BFD control packet may be carried by a Min-tx-interval field, and the unit is microseconds. It should be understood that the "BFD control packet" referred to in the "Min-tx-interval field" is only an example, and the embodiment of the present application does not limit the type of BFD, and may be a normal BFD or an SBFD, depending on which BFD mechanism is configured by the controller for the forwarding node. That is, the "BFD control packet" referred to in the "optional field" may also be replaced with the "SBFD control packet". Similar explanations can be made for the "BFD control packet" related in the following optional fields, which are not described in detail below.

The minimum receiving interval of the BFD control message can be carried by a Min-rx-interval field in microseconds in the embodiment of the application. The local detection multiple of the BFD session can be carried by a Detect-multiplier field in the embodiment of the application. The embodiment of the application can carry the authentication Type of the BFD control packet through the Auth Type field, and has 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, the embodiment of the present application may assign a type value to each encryption algorithm to refer to a corresponding authentication type. It should be understood that the above 7 values may respectively correspond to the encryption algorithm in the industry standard, and the related explanation or description of the encryption algorithm may refer to the description of the prior art, and the description of the encryption algorithm is not expanded in detail herein.

The embodiment of the application can carry the length information of the authentication data (secret key) part through the Auth Length field.

The embodiment of the application can carry Authentication Data (key) information through the Authentication Data field.

In this embodiment of the present application, the controller may determine a 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.

Describing by taking a first forwarding node as an example, in the case that an SBFD mechanism is not configured in the first forwarding node, the SBFD configuration information determined by the controller for the first forwarding node includes information required for an SBFD instance of the first forwarding node, so that the first forwarding node creates the SBFD instance; in case the SBFD mechanism is configured in the first forwarding node, the SBFD configuration information determined by the controller for the first forwarding node comprises information for adjusting configuration parameters of the configured SBFD. Here, "adjusting the configuration parameters of the configured SBFD" may be interpreted as "supplementing, updating, or deleting the configuration parameters of the configured SBFD" or the like.

And S320, the controller sends a BGP message to the first forwarding node, wherein the BGP message carries the SBFD configuration information. Correspondingly, the first forwarding node receives the BGP message to obtain the SBFD configuration information.

Here, the controller may transmit the SBFD configuration information to the first forwarding node through a BGP message. And after receiving the BGP message, the first forwarding node configures an SBFD instance based on 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 herein.

The first forwarding node configures the SBFD instance associated with the SR service after receiving the SBFD configuration information; and after the configuration of the SBFD instance associated with the SR service is successful, the first forwarding node performs SBFD negotiation with an opposite node corresponding to the first forwarding node. The opposite node corresponding to the first forwarding node is a node which needs to establish an SBFD negotiation with the first forwarding node. For example, the first forwarding node is a head node, and the opposite end 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 limited in particular.

Optionally, the SBFD configuration information may be issued alone, or may be issued together with an SR service associated with the SBFD configuration information, which is not limited to this.

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

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

the specific format of the Flags field is as follows:

0 1 2 3 4 5 6 7

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

i0 |0| Reserved | (Reserved field default set 0)

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

In the SBFD configuration information received by the head node, the Type field is set to 0x01, which indicates that SBFD Type protection is currently used; the bit R of the Flag field is 0, which indicates that the head node is the initiating end of SBFD; the localdescriminator field may be set to a certain value in the local specifier resource pool, in particular, configured locally by the forwarding node or automatically generated when set to 0.

The Remote resolver field is set to a specific value in the peer specifier resource pool, and in particular, when set to 0, is configured locally by the forwarder or obtained by other means. Here, the opposite end refers to an opposite end of the head node, such as the tail node.

The header may be matched using Local and Remote discriminators 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 indicates that the head node needs to read Optional Para (Optional parameter) field.

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

alternatively, the controller may specify a minimum transmission/reception interval of a message, a detection time period, and an authentication encryption algorithm for the head node through the Optional Para field.

After receiving the SBFD configuration information sent by the controller, the head node may create or adjust an 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 BGPSR-Policy routing may be as follows:

wherein, the format of the Flags field is as follows:

0 1 2 3 4 5 6 7

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

i1 |0| Reserved | (Reserved field default set 0)

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

The Type field is set to 0x01, indicating that SBFD Type protection is currently in use; bit position 1 of R in Flag field, mark RT3 is SBFD reflection end; p bit position 0 in the Flag field, indicating that it need not be configured as a BFD reflection end; the localdescriptor field is set to the same value as the Remote escriptor 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. Alternatively, the controller may specify a minimum transmission/reception interval of the packet, a detection time period, and an authentication encryption algorithm for the tail node through the OptionalPara field.

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

In this embodiment of the present application, if both the head node and the tail node receive the BFD extended community attribute issued by the controller, and the head node and the tail node complete service deployment according to the SBFD configuration information carried in the attribute, the head node and the tail node perform SBFD service negotiation. And if the negotiation between the head node and the tail node is successful, the SBFD for SR-Policy service is successfully established.

The following describes the case of whether the SBFD mechanism is configured in the first forwarding node separately. The technical solution of the embodiment of the present application is applicable regardless of whether the SBFD mechanism is configured in the first forwarding node.

The first implementation mode comprises the following steps:

if no SBFD mechanism is configured on the first forwarding node, the SBFD configuration information includes information required by the first forwarding node to create an SBFD instance;

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

and the first forwarding node establishes an SBFD instance associated with the SR service based on the SBFD configuration information.

If the first forwarding node is not configured with the SBFD mechanism, the controller may issue the SBFD configuration information to the first forwarding node separately through the BGP message, or may issue the information for creating the SR service and the SBFD configuration information simultaneously through the BGP message. Here, since the SBFD is not configured in the first forwarding node, all necessary information for creating the SBFD needs to be contained in the SBFD configuration information.

Specifically, for the case that the first forwarding node is the head node, when receiving the information for creating the SR service and the SBFD configuration information in the BGP message sent by the controller at the same time, the head node may first create the SR-Policy service based on the information for creating the SR service in the BGP message, and immediately create the SBFD instance associated with the SR-Policy service after the SR-Policy service is created. For the situation that the first forwarding node is a tail node, in a scenario of a bidirectional tunnel, after receiving information for creating an SR service and SBFD configuration information sent by a controller, the tail node may create an SR-Policy service based on the information for creating the SR service in the message, immediately create a configuration of a reflection end of an SBFD instance associated with the SR-Policy service after the SR-Policy service is created, and wait for SBFD negotiation with a head node after the SBFD instance is created. Or, in a scenario of establishing the unidirectional tunnel, when the tail node does not need the information for creating the SR-Policy service issued by the controller, an endpoint in Network Layer Reachable Information (NLRI) of the SR service received by the tail node is set to zero (the meaning of zero setting means that no information for creating the SR-Policy service is carried in a BGP message issued by the controller to the tail node).

It should be understood that, in the embodiment of the present application, the sequence of first creating the SR-Policy service by the first forwarding node or first creating the SBFD instance by the first forwarding node is not specifically limited, and 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 may perform SBFD negotiation, and associate the SBFD instances with the SR-Policy service, so as to provide fault detection for the SR service.

The second implementation mode comprises the following steps:

if an SBFD mechanism is configured on a first forwarding node, the SBFD configuration information includes information for adjusting configuration parameters of an SBFD configured in the first forwarding node, where the first forwarding node configures an SBFD instance associated with the SR service according to the SBFD configuration information, and includes:

and 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 information for creating the SBFD instance in the BGP message. The first forwarding node may use the base configuration of SBFD of the original static 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, part of the information in the SBFD may be carried as a binding policy and/or parameter supplement to the SBFD configuration. For example, in the fields included in the SBFD configuration information, zeroing Local discriminantor and remotediscriminantor may refer to: the Local descriptor and the Remote descriptor are not carried with information, and the rest of the fields may be newly configured by the controller 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 routing may be as follows:

for the fields of the SBFD configuration information in the BGP SR-Policy route, the controller sets the localdescriptor field to 0 and sets the Remote escriptor field to 0, that is, the two fields use the values statically configured in the first forwarding node. In particular, if the two fields are non-0 values and the first forwarding node has a static configuration, the SBFD instance should be newly created using the value carried in the SBFD configuration information and associated with the SR-Policy service.

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

In a second implementation, the SBFD instance may be updated by the first forwarding node. If the SR service in the first forwarding node is already associated with the SBFD instance but the association needs to be changed, the controller may send the SBFD configuration information to the first forwarding node as the configuration information of the new SBFD instance. And the first forwarding node refreshes the SBFD instance associated with the SR service based on the configuration information of the new SBFD instance.

In this embodiment of the present application, a BGP message sent by the controller to the first forwarding node may carry an SR service and configuration information of an SBFD instance associated with the SR service. Particularly, when the SBFD instance associated with the SR service needs to be deleted, that is, the SR service is no longer associated with the SBFD instance, the BGP message sent by the controller to the first forwarding node carries the information of the SR service, and does not carry the SBFD configuration information any more. Thus, 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 an SBFD instance that has been created, which can release resources, and is helpful to reduce occupation of the forwarding node and network resources.

For example, if the SBFD static configuration does not initially exist in the first forwarding node, after the method in the embodiment of the present application is used to configure an SBFD instance associated with a certain SR service for the first forwarding node, if the first forwarding node subsequently receives a BGP message that needs to cancel or delete the SR service, and the SR service is completely cancelled, the SBFD instance associated with the SR service may also be deleted, so as to save resources.

Optionally, the SBFD configuration information in this embodiment may be associated with multiple SR services. When the controller issues the BGP message to the forwarding node, it may issue, to the first forwarding node, multiple BGP messages corresponding to multiple SR services, where each BGP message carries the same SBFD configuration information. When receiving such a BGP message, the first forwarding node may multiplex the SBFD configuration information to multiple different SR services.

Or, when issuing a BGP message to the first forwarding node, the controller may issue one BGP message to the first forwarding node, where the one 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 for configuring the SBFD mechanism for seamless bidirectional forwarding detection in the embodiment of the present application is described by taking SBFD configuration as an example, and the technical solution in the embodiment of the present application is also applicable to dynamic deployment of general BFD, Link bandwidth BFD, or other BFDs, which is not limited to this. For example, the configuration information of the normal BFD may be extended in other service address families of the BGP, or a special BFD control address family may be added.

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

The method for configuring the SBFD mechanism according to the embodiments of the present application is described in detail above with reference to fig. 1 to 3. An apparatus for configuring the SBFD mechanism according to an embodiment of the present application will be described with reference to fig. 4 to 7. It should be understood that the technical features described in the method embodiments are equally applicable to the following apparatus embodiments.

Fig. 4 shows a schematic block diagram of an apparatus 400 configured with a Seamless Bidirectional Forwarding Detection (SBFD) mechanism according to an embodiment of the present application. Alternatively, the apparatus 400 may be a controller. As shown in fig. 4, the apparatus 400 includes:

a determining module 410, configured to determine SBFD configuration information according to an SBFD mechanism configuration state of a first forwarding node in the multiple forwarding nodes, where the SBFD configuration information includes: configuring information required by an SBFD instance associated with a Segment Routing (SR) service;

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, according to an SBFD mechanism configuration state of a first forwarding node in the multiple forwarding nodes, SBFD configuration information, and specifically includes:

under the condition that an SBFD mechanism is not configured in the first forwarding node, the SBFD configuration information comprises information required by the first forwarding node for creating an SBFD instance;

in a case that an SBFD mechanism is configured in the first forwarding node, the SBFD configuration information includes information for adjusting configuration parameters of an 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 apparatus 400 according to the embodiment of the present application may correspond to the method of the controller side in the foregoing method embodiment, and the above and other management operations and/or functions of the respective modules in the apparatus 400 are respectively for implementing the corresponding steps of the foregoing respective methods, so that the beneficial effects in the foregoing method embodiment may also be implemented, and for brevity, no detailed description is provided here.

Fig. 5 is a schematic block diagram of an apparatus 500 configured with a Seamless Bidirectional Forwarding Detection (SBFD) mechanism according to an embodiment of the present application. As shown in fig. 5, the apparatus 500 includes:

a processor 501, a memory 502, and a transceiver 503.

The processor 501, memory 502, and transceiver 503 communicate with each other via internal connection paths to transfer control and/or data signals. In one possible design, processor 501, memory 502, and transceiver 503 may be implemented by chips. The memory 502 may store program codes, and the processor 501 calls the program codes stored in the memory 502 to realize the 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 of the multiple forwarding nodes, where the SBFD configuration information includes: configuring information required by an SBFD instance associated with a Segment Routing (SR) service; the transceiver 503 is configured to send a BGP message to the first forwarding node, where the BGP message carries the SBFD configuration information.

Alternatively, the determining 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 may be implemented as two components, a receiver and a transmitter.

Fig. 6 shows a schematic block diagram of an apparatus 600 configured with a Seamless Bidirectional Forwarding Detection (SBFD) mechanism according to an embodiment of the present application. The arrangement 600 is applied in a network supporting segment routing traffic engineering, SR-TE, comprising a controller and a plurality of forwarding nodes. Optionally, the apparatus 600 is a first forwarding node of the plurality of forwarding nodes. As shown in fig. 6, the apparatus 600 includes:

a transceiver module 610, configured to receive a BGP message sent by the controller, where the BGP message carries SBFD configuration information, and the SBFD configuration information includes: configuring information required by an SBFD instance associated with a Segment Routing (SR) service;

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

the processing module 620 is further configured to perform SBFD negotiation with the peer 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 a case that 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;

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

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

and adjusting the configured SBFD configuration parameters based on the SBFD configuration information.

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

Optionally, the SBFD configuration information is associated with a plurality of SR services.

Optionally, the first forwarding node is a head node of the plurality of forwarding nodes, or the first forwarding node is a tail node of the plurality of forwarding nodes.

Optionally, the SBFD configuration information includes one or more of the following: a field for indicating a transceiving end type of the first forwarding node, a field for indicating whether the SBFD configuration information is an SBFD, a field of a home delimiter resource pool of the first forwarding node, and a field of an opposite delimiter resource pool of the first forwarding node.

It should be understood that the apparatus 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 each module in the apparatus 600 are respectively for implementing corresponding steps of each foregoing method, so that beneficial effects in the foregoing method embodiment may also be implemented, and for brevity, no detailed description is provided here.

Fig. 7 is a schematic block diagram of an apparatus 700 configured with a Seamless Bidirectional Forwarding Detection (SBFD) mechanism according to an embodiment of the present application. As shown in fig. 7, the apparatus 700 includes:

a processor 701, a memory 702, and a transceiver 703.

The processor 701, memory 702, and transceiver 703 communicate control and/or data signals with each other via internal connection paths. In one possible design, the processor 701, the memory 702, and the transceiver 703 may be implemented by chips. The memory 702 may store program codes, and the processor 701 calls the program codes stored in the memory 702 to realize the 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: configuring information required by an SBFD instance associated with a Segment Routing (SR) service; the processor 701 is configured to configure an SBFD instance associated with the SR service according to the SBFD configuration information; and after the configuration of the SBFD instance associated with the SR service is successful, carrying out SBFD negotiation with the opposite end node corresponding to the first forwarding node.

Alternatively, 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 may be implemented as two components, a receiver and a transmitter.

The application also provides a network comprising a controller, a plurality of forwarding nodes. The controller may perform the method described above as being performed by the controller. The first forwarding node may be included in the plurality of forwarding nodes. The first forwarding node may be a head node of an SR Policy tunnel, or the first forwarding node may be a 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), the network comprising a controller and a plurality of forwarding nodes, the method comprising:

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 includes: 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.

Embodiment 2 and the method of embodiment 1, wherein the determining, by the controller, SBFD configuration information according to the SBFD mechanism configuration status of the first forwarding node of the plurality of forwarding nodes includes:

Embodiment 3 and the method according to embodiment 1 or 2, wherein the BGP message further carries information of the SR service.

Embodiment 4 the method of any one of embodiments 1 to 3, wherein the SBFD configuration information is associated with a plurality of SR services.

Embodiment 5 and the method according to any of embodiments 1 to 4, wherein the first forwarding node is a head node of the plurality of forwarding nodes or the first forwarding node is a tail node of the plurality of forwarding nodes.

Embodiment 6 the method according to any of embodiments 1 to 5, wherein the SBFD configuration information comprises one or more of the following: a field for indicating a transceiving end type of the first forwarding node, a field for indicating whether the SBFD configuration information is an SBFD, a field of a home delimiter resource pool of the first forwarding node, and a field of an opposite delimiter resource pool of the first forwarding node.

Embodiment 7 is a method for configuring a Seamless Bidirectional Forwarding Detection (SBFD) mechanism, where the method is applied to a network supporting segment routing traffic engineering (SR-TE), where the network includes a controller and multiple forwarding nodes, and the method includes:

a first forwarding node of the multiple forwarding nodes receives a Border Gateway Protocol (BGP) message sent by the controller, wherein the BGP message carries SBFD configuration information, and the SBFD configuration information comprises: configuring information required by an SBFD instance associated with a Segment Routing (SR) service;

the first forwarding node configures an SBFD instance associated with the SR service according to the SBFD configuration information;

and after the configuration of the SBFD instance associated with the SR service is successful, the first forwarding node performs SBFD negotiation with an opposite node corresponding to the first forwarding node.

Embodiment 8 is the method according to embodiment 7, wherein in a case that 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;

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

Embodiment 10 and the method according to any one of embodiments 7 to 9, wherein the BGP message further carries information of the SR service.

Embodiment 11 and the method of any of embodiments 7 to 10, wherein the SBFD configuration information is associated with a plurality of SR services.

Embodiment 12 and any one of embodiments 7 to 11 further comprising a forwarding node configured to forward the data to the destination node, wherein the forwarding node is a head node of the plurality of forwarding nodes or the forwarding node is a tail node of the plurality of forwarding nodes.

Embodiment 13 the method according to any of embodiments 7 to 12, wherein the SBFD configuration information comprises one or more of the following: a field for indicating a transceiving end type of the first forwarding node, a field for indicating whether the SBFD configuration information is an SBFD, a field of a home delimiter resource pool of the first forwarding node, and a field of an opposite delimiter resource pool of the first forwarding node.

Embodiment 14, an apparatus for configuring a Seamless Bidirectional Forwarding Detection (SBFD) mechanism, where the apparatus is applied to a network supporting segment routing traffic engineering (SR-TE), the network including a controller and multiple forwarding nodes, and the apparatus includes:

a determining module, configured to determine SBFD configuration information according to an SBFD mechanism configuration state of a first forwarding node of the multiple forwarding nodes, where the SBFD configuration information includes: configuring information required by an SBFD instance associated with a Segment Routing (SR) service;

and the transceiver module is used for sending a Border Gateway Protocol (BGP) message to the first forwarding node, wherein the BGP message carries the SBFD configuration information.

Embodiment 15 and 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 a first forwarding node in the multiple forwarding nodes, and specifically includes:

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

Embodiment 17, the apparatus of any of embodiments 14 to 16, wherein the SBFD configuration information is associated with a plurality of SR services.

Embodiment 18, the apparatus of any one of embodiments 14 to 17, wherein the first forwarding node is a head node of the plurality of forwarding nodes, or wherein the first forwarding node is a tail node of the plurality of forwarding nodes.

Embodiment 19, the apparatus according to any of embodiments 14 to 18, wherein the SBFD configuration information comprises one or more of the following: a field for indicating a transceiving end type of the first forwarding node, a field for indicating whether the SBFD configuration information is an SBFD, a field of a home delimiter resource pool of the first forwarding node, and a field of an opposite delimiter resource pool of the first forwarding node.

Embodiment 20, an apparatus for configuring a Seamless Bidirectional Forwarding Detection (SBFD) mechanism, where the apparatus is applied to a network supporting segment routing traffic engineering (SR-TE), the network including a controller and a plurality of forwarding nodes, and the apparatus is a first forwarding node in the plurality of forwarding nodes, and the apparatus includes:

a transceiver module, configured to receive a BGP message sent by the controller, where the BGP message carries SBFD configuration information, and the SBFD configuration information includes: configuring information required by an SBFD instance associated with a Segment Routing (SR) service;

the processing module is used for configuring an 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 peer node corresponding to the first forwarding node after the SBFD instance associated with the SR service is successfully configured.

Embodiment 21, the apparatus of embodiment 20, wherein in case that 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 is configured to configure, according to the SBFD configuration information, an SBFD instance associated with the SR service, and specifically includes:

and establishing an SBFD instance associated with the SR service based on the SBFD configuration information.

Embodiment 22, the apparatus according to embodiment 20, wherein in a case that an SBFD mechanism is configured in the first forwarding node, the SBFD configuration information includes information for adjusting configuration parameters of an SBFD configured in the first forwarding node; wherein, the processing module is configured to configure, according to the SBFD configuration information, an SBFD instance associated with the SR service, and specifically includes:

The apparatus according to any one of embodiments 20 to 22 and embodiment 23, wherein the BGP message further carries information of the SR service.

Embodiment 24, the apparatus of any of embodiments 20 to 23, wherein the SBFD configuration information is associated with a plurality of SR services.

Embodiment 25, the apparatus of any of embodiments 20 to 24, wherein the first forwarding node is a head node of the plurality of forwarding nodes, or wherein the first forwarding node is a tail node of the plurality of forwarding nodes.

Embodiment 26 and apparatus according to any of embodiments 20 to 25, wherein the SBFD configuration information comprises one or more of: a field for indicating a transceiving end type of the first forwarding node, a field for indicating whether the SBFD configuration information is an SBFD, a field of a home delimiter resource pool of the first forwarding node, and a field of an opposite delimiter resource pool of the first forwarding node.

The method disclosed in the embodiments of the present application may be applied to a processor, or may be implemented by a processor. The processor may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The Processor may be a general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable Gate Array (FPGA) or other programmable logic device, a discrete Gate or transistor logic device, a discrete hardware component, a system on chip (SoC), a Central Processing Unit (CPU), a Network Processor (NP), a Digital Signal Processor (DSP), a Microcontroller (MCU), a programmable logic controller (PLD), or other Integrated chip. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A 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 connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.

It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. 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 (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data rate Synchronous Dynamic random access memory (DDR SDRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and direct memory bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

Various aspects or features of the disclosure may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques. The term "article of manufacture" as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer-readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips, etc.), optical disks (e.g., Compact Disk (CD), Digital Versatile Disk (DVD), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROM), card, stick, or key drive, etc.). In addition, 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" can include, without being limited to, wireless channels and various other media capable of storing, containing, and/or carrying instruction(s) and/or data.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

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

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a read-only memory ROM, a random access memory RAM, a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of configuring a seamless bidirectional forwarding detection, SBFD, mechanism, the method comprising:

the controller determines SBFD configuration information, which includes: configuring information required by an SBFD instance associated with a Segment Routing (SR) service;

and the controller sends a BGP message to the forwarding node, wherein the BGP message carries the SBFD configuration information.

2. The method of claim 1,

the SBFD configuration information comprises 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 configured in the forwarding node.

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

4. The method of any of claims 1 to 3, wherein the SBFD configuration information is associated with a plurality of SR services.

5. The method according to any 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 of any of claims 1 to 5, wherein the SBFD configuration information comprises one or more of: a field for indicating a transceiving end type of the forwarding node, a field for indicating whether the SBFD configuration information is an SBFD, a field of a local end specifier resource pool of the forwarding node, and a field of an opposite end specifier resource pool of the forwarding node.

7. The method of any of claims 1-6, wherein the SBFD configuration information further comprises one or more of: sending the minimum sending interval of the BFD control message; and BFD controls the authentication information of the message.

8. The method according to any of claims 1-7, wherein said SBFD configuration information is carried in an extended community attribute added to said BGP message.

9. A method of configuring a seamless bidirectional forwarding detection, SBFD, mechanism, the method comprising:

a forwarding node receives a Border Gateway Protocol (BGP) message sent by a controller, wherein the BGP message carries SBFD configuration information, and the SBFD configuration information comprises: configuring information required by an SBFD instance associated with a Segment Routing (SR) service;

and the forwarding node configures the SBFD instance according to the SBFD configuration information.

10. The method of claim 9, wherein the forwarding node configures the SBFD instance according to the SBFD configuration information, comprising:

and the forwarding node creates the SBFD according to the SBFD configuration information.

11. The method of claim 9, wherein the forwarding node configures the SBFD instance according to the SBFD configuration information, comprising:

and the forwarding node adjusts the configured configuration parameters of the SBFD instance based on the SBFD configuration information.

12. The method according to any of claims 9-11, wherein the BGP message further carries information of the SR service.

13. The method of any of claims 9-12, wherein the SBFD configuration information is associated with a plurality of the SR services.

14. The method according to any 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 of any of claims 9-14, wherein the SBFD configuration information comprises one or more of: a field for indicating a transceiving end type of the first forwarding node, a field for indicating whether the SBFD configuration information is an SBFD, a field of a home delimiter resource pool of the first forwarding node, and a field of an opposite delimiter resource pool of the first forwarding node.

16. The method of any of claims 9-15, wherein the SBFD configuration information further comprises one or more of the following: sending the minimum sending interval of the BFD control message; and BFD controls the authentication information of the message.

17. The method according to any of claims 9-16, wherein said SBFD configuration information is carried in an extended community attribute added to said BGP message.

18. A controller, comprising:

a 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:

a 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 which, when executed on a computer, cause the computer to perform the method of any one of claims 1-17.

21. A communication system comprising a controller according to claim 18 and a forwarding node according to claim 19.