CN111385165B

CN111385165B - Method and device for configuring seamless bidirectional forwarding detection (SBFD) mechanism

Info

Publication number: CN111385165B
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: 2024-04-09
Anticipated expiration: 2038-12-28
Also published as: CN109587009A; CN109587009B; CN111385165A; WO2020134739A1

Abstract

The application provides a method and a device for configuring a Seamless Bidirectional Forwarding Detection (SBFD) mechanism, wherein the SBFD mechanism is configured for a forwarding node through a controller, so that the dynamic configuration of the SBFD mechanism can be realized, and protection is provided for a tunnel. The method comprises the following steps: 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 for the SBFD instance associated with the segment routed 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 bi-directional forwarding detection, SBFD, mechanism.

Background

Segment Routing (SR) is a protocol designed based on the source routing concept to forward packets over a network. SR multiprotocol label switching (MPLS) refers to Segment Routing based on an MPLS forwarding plane. Segment routing-traffic engineering (SR-TE) is a new type of TE tunneling using SR as a control protocol. SR-TE refers to a tunnel created using the SR protocol based on the constraint attributes of TE. The controller is responsible for calculating the forwarding path of the tunnel and forwarding the label stack strictly corresponding to the path to the forwarder. On the ingress 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 for the SR-TE, a link-state packet (LSP) is successfully established as long as the label stack is issued, and the LSP will not have the condition of the protocol Down except for the withdrawal of the label stack. The SR-TE LSP failure detection needs to rely on deployment of bidirectional forwarding detection (bidirectional forwarding detection, BFD) detection by which the backup LSPs are switched. Seamless Bidirectional Forwarding Detection (SBFD) simplifies the state machine of BFD, shortens negotiation time, improves 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 provides end-to-end failure detection for the already created SR Policy tunnel by static configuration of SBFD instances and parameters, and cannot dynamically provide tunnel protection in time.

Disclosure of Invention

In view of this, the present application provides a method and apparatus for configuring a seamless bidirectional forwarding detection SBFD mechanism, which can implement dynamic deployment of SBFD, and is helpful for providing tunnel protection in time.

In a first aspect, a method of configuring a seamless bi-directional forwarding detection, SBFD, mechanism is provided, the method being 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 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 for the SBFD instance associated with the segment routed SR service; the controller sends a Border Gateway Protocol (BGP) message to the first forwarding node, wherein the BGP message carries the SBFD configuration information, namely, the controller can dynamically configure an 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 controller determines SBFD configuration information according to an SBFD mechanism configuration state of a first forwarding node of the plurality of forwarding nodes, including: in the case that the first forwarding node is not configured with an SBFD mechanism, the SBFD configuration information includes information required for the first forwarding node to create an SBFD instance; in the case where the SBFD mechanism is configured in the first forwarding node, the SBFD configuration information includes information for adjusting configuration parameters of the SBFD configured in the first forwarding node. Therefore, whether the first forwarding node is configured with the SBFD mechanism or not, the controller may generate corresponding SBFD configuration information for the first forwarding node, so that the first forwarding node performs establishment or adjustment of the SBFD instance based on the SBFD configuration information, so as to meet the requirements 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 SR traffic in BGP messages, so that the forwarding node creates SR traffic associated with the SBFD instance.

In one possible implementation, the SBFD configuration information is associated with a plurality of the 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, the SBFD configuration information includes one or more of the following: a field for indicating a transceiver type of the first forwarding node, a field for indicating whether the SBFD configuration information is SBFD, a field for a home terminal identifier resource pool of the first forwarding node, a field for a peer terminal identifier resource pool of the first forwarding node.

Optionally, an optional field may be further included in the SBFD configuration information.

In a second aspect, a method of configuring a seamless bi-directional forwarding detection, SBFD, mechanism is provided, the method being 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: a first forwarding node in the plurality of forwarding nodes receives a border gateway protocol BGP message sent by the controller, where the BGP message carries SBFD configuration information, and the SBFD configuration information includes: configuring information required for the SBFD instance associated with the segment routed SR service; the first forwarding node configures an SBFD instance associated with the SR service according to the SBFD configuration information; after the SBFD instance configuration associated with the SR service is successful, the first forwarding node performs SBFD negotiation with the corresponding opposite node of the first forwarding node. Therefore, the first forwarding node can dynamically configure the SBFD instance based on the SBFD configuration information issued by the controller, and the user is not required to statically configure the SBFD instance for the first forwarding node, so that more flexible dynamic deployment can be realized, and the tunnel protection can be provided in time.

Optionally, the SR service is an SR Policy service.

In one possible implementation, in a case where no SBFD mechanism is configured in the first forwarding node, the SBFD configuration information includes information required for the first forwarding node to create an SBFD instance; and the first forwarding node establishes an SBFD instance associated with the SR service based on the SBFD configuration information. Thus, 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 where 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 first forwarding node adjusts the configuration parameters of the configured SBFD based on the SBFD configuration information. Thus, 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. Thus, the first forwarding node may simultaneously create SR traffic associated with the SBFD instance based on the controller carrying information of the SR traffic in BGP messages.

In a third aspect, a controller is provided, the controller comprising means for performing the method of the first aspect or any of the possible implementations of the first aspect.

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

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

Optionally, the first forwarding node is a head node, and the opposite end node corresponding to the first forwarding node is a tail node; alternatively, the first forwarding node is a tail node, and the peer node corresponding to the first forwarding node is a head node.

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

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

In a seventh aspect, a computer readable storage medium is provided, where a program is stored, the program causing a forwarding node to perform the method of the second aspect described above, and any of its various implementation forms, to configure a seamless bidirectional forwarding detection SBFD mechanism.

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

In a ninth aspect, an apparatus is provided for configuring a seamless bidirectional forwarding detection, SBFD, mechanism that includes a processor, a memory, and a transceiver. The processor is connected with 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. The processor, when executing the memory-stored instructions, causes the processor to perform the method of configuring a seamless bidirectional forwarding detection, SBFD, mechanism in the above aspects.

Drawings

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

FIG. 2 is an exemplary diagram of reachability detection by SBFD mechanisms;

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 for configuring 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 for configuring a seamless bi-directional forwarding detection, SBFD, mechanism according to another embodiment of the present application;

FIG. 6 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;

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 solutions 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 Segment Routing (SR) technology or SR Policy 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 traffic. It should be understood that in the embodiment of the present application, the forwarding node may be a switch, a router, or other devices or network elements supporting forwarding of a packet or data, which is not limited in the 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 algorithm calculates the tunnel path according to Color attributes required by the representational traffic tunnel service level agreement (service level agreement, SLA). The business network head node matches the corresponding tunnel to realize business flow forwarding through the extended business route Color group attribute and the network far-end node information. The SR tunnel path can be customized for the service with specific SLA requirement by the SR Policy technology, and the subdivision of the service forwarding network of the application level is realized. Further details of SR policy may be found in the introduction of the prior art and are not described here in detail.

In order to facilitate understanding and describing the method proposed in the embodiments of the present application, an SR Policy service establishment procedure is first described in conjunction with 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., forwarding nodes include a head node RT1, an intermediate node RT2, and a tail node RT 3). The controller may forward SR policy messages to the head node RT1 and the tail node RT3 to deploy SR policy traffic in the network. The node labels and adjacency labels are pre-assigned by any one forwarding node via IGP routing. The controller gathers network topology and label space information via border gateway link state protocol (border gateway protocol link state, BGP-LS) messages. The controller provides an interface; the user plans VPN service source and destination nodes (RT 1-RT 3) and drainage strategies (Color and tunnel service level agreement SLA path constraint corresponding relation) for the specific private network user. 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 an SR policy border gateway protocol (border gateway protocol, BGP) session message through a BGPSR policy address group session, and issues the message to the head node RT1. The tail node RT3 injects Color extended community attribute into the private network route of the specific user and issues BGP routing strategy. The tail node RT3 issues BGP routes carrying Color community attributes to the head node RT1. The head node RT1 stores the BGP route issued by the tail node RT3, and generates a BGP route table. The head node RT1 performs matching based on the stored BGP route and the SR Policy BGP session message issued by the controller, establishes an SR Policy tunnel after the matching is successful, hangs the route next hop to the SR Policy tunnel, and guides the traffic to the SR Policy tunnel for forwarding according to the route table next hop matching BSID 30027 by the entry specific user traffic.

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

Some terms or concepts related to 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 initiator and a reflector, and before the link detection, the initiator and the reflector notify the information such as SBFD descriptor (dispensifier) by sending an SBFD control message (SBFD Control Packet) to each other. When the link is detected, the initiating terminal actively transmits an SBFD Echo message, the reflecting terminal loops back the message according to the condition of the local terminal, and the initiating terminal determines the state of the local terminal according to the reflected message. When the SBFD is applied to SR scene detection, two scenes, namely SBFD for SR LSP and SBFD for SR-TE LSP, are mainly adopted. 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 reflecting terminal is forwarded by a multi-hop IP path to the return path of the initiating terminal.

The initiating terminal is used as a detecting terminal and comprises an SBFD state machine mechanism and a detecting mechanism. The state machine of the initiating terminal only has the Up and Down states, the sent message also has the Up and Down states, and only can receive the Up or 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 may be found in the introduction of the prior art and are not described here in detail.

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

In the prior art, the SBFD instances in the forwarding nodes are all statically configured by users, and are not supported to be selectively managed based on service dynamics, so that the forwarding nodes are not flexible. The embodiment of the application aims to provide a method for configuring a Seamless Bidirectional Forwarding Detection (SBFD) mechanism, which 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 bi-directional forwarding detection, SBFD, mechanism according to an embodiment of the present application. The method 300 is applied to a network supporting a segment routed traffic engineering, SR-TE, the network 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 the SBFD mechanism configuration state of a first forwarding node of the plurality of forwarding nodes, wherein the SBFD configuration information comprises: the information needed to configure the SBFD instance associated with the segment routed SR traffic.

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

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

The controller may extend the address family to the BGP protocol and add the SBFD configuration information described above. For example, the controller adds a BFD extension group (extension communication) attribute based on BGPSR-Policy multi-protocol extension address family for carrying the SBFD configuration information. That is, the controller may issue the above SBFD configuration information through BGPSR-Policy address family routing. Optionally, the SBFD configuration information includes one or more of the following: a field for indicating a transceiver type of the first forwarding node, a field for indicating whether the SBFD configuration information is SBFD, a field of a home terminal identifier resource pool of the first forwarding node, a field of a peer terminal identifier resource pool of the first forwarding node, and the like. For example, the field for indicating the type of transceiver end of the first forwarding node may be a Flags field to indicate whether the first forwarding node is an initiator end or a reflector end; the field for indicating whether the SBFD configuration information is an SBFD may be a Type field to indicate a Type of the SBFD configuration information (a Type may include a Type of a general BFD or an SBFD, etc.); the field of the home terminal identifier resource pool of the first forwarding node may be a Local Discriminatiors field; the fields of the opposite end region identifier resource pool of the first forwarding node may be Remote Discriminatiors fields.

Optionally, the SBFD configuration information may further include other Optional fields, for example, optional Para (Variable), which specifically may include: a field for indicating a minimum transmission interval of the control message (Min-tx-interval field), a field for indicating a minimum reception interval of the control message (Min-rx-interval field), a field for indicating a local detection multiple of the detected BFD session (Detect-multiple field), a field for indicating length information of an authentication data (key) portion (Auth length field), a field for indicating an authentication Type of the control message (Auth Type field), and a field for indicating authentication data (Authentication Data field), and the like. It should be understood that the control packet herein may be a BFD control packet or an SBFD control packet, which is not limited in particular, and what control packet may be determined based on what BFD mechanism (such as an SBFD mechanism or a normal BFD mechanism or a Link bandwidth BFD mechanism) needs to be configured by the controller. It should be understood that the fields included in the SBFD configuration information are not specifically limited, and 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, or may include other fields.

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

based on the above, the extended BGP message carries a Type field, a flag field, a reserved field, a local identifier local Discriminatior field, a remote identifier Remote Discriminatior field, an Optional parameter opa or a variable (variable) field, and so on.

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

Wherein the flag field format is as follows:

in the Flags field, R bits represent a Reflector for indicating a reflection side or an initiation side 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 represents the initiation terminal of SBFD.

In the Flags field, P bits represent Passive, indicating the reflective or initiator end of BFD. The 1 is represented as the reflection end of the common BFD, and the 0 is represented as the initiation end of the common BFD.

When the R bit is set to 0, the originating terminal of the SBFD is represented, and the local area identifier local Discriminatior field carries the local area identifier required for creating the SBFD or BFD, and the length is 4 bytes; the far-end specifier Remote Discriminatior field carries the far-end specifier required to create an SBFD or BFD.

When the R bit is set to 1, the reflective end of the SBFD is indicated, at which point the local end identifier local Discriminatior field carries the reflective end identifier (Reflector Discriminatior) required to create the SBFD or BFD, and the Remote Discriminatior field is set to zero by default.

The format of the Optional Para field is as follows:

illustratively, the embodiment of the present application may carry the minimum transmission interval of the BFD control message in microseconds through the Min-tx-interval field. It should be understood that the "BFD control message" referred to in the "Min-tx-interval field" above is only an example, and the embodiment of the present application does not limit the type of BFD, and may be general BFD or SBFD, depending on which BFD mechanism is configured by the controller for the forwarding node. That is, the "BFD control messages" referred to in the "optional field" may also be replaced with "SBFD control messages". The "BFD control messages" referred to in the following optional fields may also be similarly explained, and will not be described in detail.

The embodiment of the application can carry the minimum receiving interval of the BFD control message through the Min-rx-interval field, and the unit is microseconds. The embodiment of the application can carry the local detection multiple of the BFD session through the detection-multiplexer field. The embodiment of the application can carry the authentication Type of the BFD control message 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 an encryption algorithm in industry standards, and a description of the encryption algorithm may be referred to a description of the prior art, and the description of the encryption algorithm is not described in detail herein.

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

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

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

Taking the first forwarding node as an example for description, in the case that the first forwarding node is not configured with an SBFD mechanism, the controller includes information required for the first forwarding node SBFD instance in the SBFD configuration information determined for the first forwarding node so as to facilitate the first forwarding node to create the SBFD instance; in the case where the SBFD mechanism is configured in the first forwarding node, the SBFD configuration information determined by the controller for the first forwarding node includes information for adjusting the configuration parameters of the configured SBFD. Wherein, "adjusting the configuration parameters of the configured SBFD" may be interpreted as operations such as "supplementing, updating, or deleting the configuration parameters of the configured SBFD".

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

The first forwarding node receives the SBFD configuration information and configures an SBFD instance associated with the SR service; after the SBFD instance configuration associated with the SR service is successful, the first forwarding node performs SBFD negotiation with the corresponding opposite node of the first forwarding node. The correspondent 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 corresponding opposite end node of the first forwarding node is a tail node; alternatively, the first forwarding node is a tail node, and the corresponding peer node of the first forwarding node is a head node, which is not particularly limited.

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

Alternatively, the controller may distinguish the SBFD configuration information of the head node or the tail node by giving different values to the R bit, the P bit, the local end identifier local Discriminatior field, and the end identifier Remote Discriminatior field of the Flag field in the SBFD configuration information.

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 BGP SR-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.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 Flag field R bit is 0, which indicates that the head node is the initiating terminal of SBFD; the Local Discriminatior field may be set to a specific value in the local identifier resource pool, in particular, configured locally or generated automatically by the forwarding node when set to 0.

The Remote Discriminatior field is set to a particular value in the opposite-end identifier resource pool, and in particular, when set to 0, is configured locally or otherwise obtained by the repeater. Here, the opposite end refers to an opposite end of the head node, such as a tail node.

The head node may use Local Discriminatior and Remote Discriminatior to match to establish the 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 an Optional parameter (Optional parameter) field.

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

alternatively, the controller may specify a message minimum transmission/reception interval, a detection time period and an 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 first forwarding node is a tail node, the format of the SBFD configuration information received by the tail node in the BGP SR-Policy route may be as follows:

wherein the flag field format is as follows:

the Type field is set to 0x01, indicating that SBFD Type protection is currently used; r bit position 1 in Flag field, label RT3 is SBFD reflecting end; the P bit position 0 in the Flag field indicates that no configuration as BFD reflector is required; the Local Discriminatior field is set to the same value as the Remote Discriminatior field in the head node.

Similarly, if the total length of the field corresponding to the SBFD configuration information received by the tail node is greater than 12 bytes, it indicates that the tail node needs to read an Optional parameter (Optional Para) field. Alternatively, the controller may specify a minimum transmission/reception interval of the message, a detection time period and an authentication encryption algorithm for the tail node through the above-mentioned Optional Para field.

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

In the embodiment of the application, if the head node and the tail node both receive the BFD extended group 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 created.

The case of whether the SBFD mechanism is configured in the first forwarding node will be described separately. The technical solution of the embodiment of the present application is applicable regardless of whether the first forwarding node is configured with an SBFD mechanism.

The first implementation mode:

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

Wherein the first forwarding node configures an 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 SBFD mechanism is not configured in the first forwarding node, the controller can independently issue the SBFD configuration information to the first forwarding node through a BGP message, or can 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 transfer 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 the head node receives the information of the SR service and the SBFD configuration information simultaneously created in the BGP message issued by the controller, the SR-Policy service may be created first based on the information of the SR service created in the BGP message, and the SBFD instance associated with the SR-Policy service may be created immediately after the SR-Policy service is created. In the case that the first forwarding node is the tail node, in the scene of the bidirectional tunnel, after receiving the information for creating the SR service and the SBFD configuration information issued by the controller, the tail node may first create the SR-Policy service based on the information for creating the SR service in the message, immediately create the configuration of the reflection end of the SBFD instance associated with the SR-Policy service after the SR-Policy service is created, and wait for performing SBFD negotiation with the head node after creating the SBFD instance. Or in the scene of establishing the unidirectional tunnel, when the tail node does not need the information for creating the SR-Policy service issued by the controller, the endpoint in the network layer reachable information (network layer reachable information, NLRI) of the SR service received by the tail node is set to zero (the zero setting means that the BGP message issued by the controller to the tail node does not carry the information for creating the SR-Policy service).

It should be understood that, in the embodiment of the present application, the sequence of first creating the SR-Policy service or first creating the SBFD instance by the first forwarding node is not specifically limited, and may be based on actual requirements.

After the SBFD instances in the head node and the tail node are established, the head node and the tail node can carry out SBFD negotiation, and the SBFD instances are associated with the SR-Policy service to provide fault detection for the SR service.

The second implementation mode:

if the first forwarding node configures an SBFD mechanism, the SBFD configuration information includes information for adjusting configuration parameters of the 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 the method includes:

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

In particular, if the SBFD mechanism is configured in the first forwarding node, the controller need not carry all the information to create the SBFD instance in BGP messages. The first forwarding node may use the base configuration of the original static configuration SBFD, such as the local static configuration or automatically generated configuration values. 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 corresponding to the SBFD configuration. For example, in the fields included in the SBFD configuration information, zeros may be set to Local Discriminatior and Remote Discriminatior, and zeros may be set to Local Discriminatior and Remote Discriminatior to refer to: no information is carried Local Discriminatior and Remote Discriminatior, and the remaining fields may be newly configured by the controller for the first forwarding node (see description above).

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

/>

for the above-mentioned field of SBFD configuration information in BGPSR-Policy routing, the controller sets Local Discriminatior field to 0 and Remote Discriminatior field to 0, i.e., a value indicating that both fields are statically configured in the first forwarding node. In particular, if these two fields are non-0 values, and there is also a static configuration situation for the first forwarding node, the value carried in the SBFD configuration information should be used to create an SBFD instance and associated with the SR-Policy service.

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

In a second implementation, the first forwarding node may update the SBFD instance. If the SR service in the first forwarding node is already associated with the SBFD instance, but the association needs to be changed, the configuration information of the new SBFD instance may be in the configuration information of the SBFD configuration information sent by the controller to the first forwarding node. The first forwarding node refreshes the SBFD instance with which the SR service has been associated 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 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, the SR service is no longer associated with the SBFD instance, the BGP message issued by the controller to the first forwarding node carries the information of the SR service, but no longer carries the SBFD configuration information. In this way, when the first forwarding node receives the BGP message, the association relationship between the SBFD instance and the SR service may be deleted or unbinding.

Alternatively, as an implementation manner, the first forwarding node may delete the created SBFD instance, which can release resources, and help to reduce occupation of forwarding nodes and network resources.

For example, if the first forwarding node does not initially have the SBFD static configuration, after the method in the embodiment of the present application configures the first forwarding node with the SBFD instance associated with a SR service, if the first forwarding node subsequently receives a BGP packet that needs to cancel or delete the SR service, and the SR service has been completely cancelled, then the SBFD instance associated with the SR service may also be deleted, so as to save resources.

Alternatively, the SBFD configuration information in the embodiments of the present application may be associated with multiple SR services. When the controller issues BGP messages to the forwarding node, the controller may issue a plurality of BGP messages corresponding to a plurality of SR services to the first forwarding node, where each BGP message carries the same SBFD configuration information. When receiving such BGP messages, the first forwarding node may multiplex SBFD configuration information to multiple different SR services.

Or when the controller issues a BGP message to the first forwarding node, the controller may issue a BGP message to the first forwarding node, where the BGP message carries configuration information of multiple SR services and the same SBFD configuration information. When receiving the BGP message, the first forwarding node may multiplex the SBFD configuration information to a plurality of 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 configuration SBFD as an example, and the technical solution in the embodiment of the present application is also applicable to dynamic deployment of common BFD, link band BFD or other BFD, which is not limited. For example, the configuration information of the common BFD may be extended in BGP other service address families, or a special BFD control address family may be added.

It should also be understood that the format examples of the fields presented in the embodiments of the present application are not limited to the embodiments of the present application, and those skilled in the art may make equivalent changes or modifications based on the examples described above, and these equivalent changes or modifications should fall within the protection scope of the embodiments of the present application.

A method of configuring a seamless bidirectional forwarding detection, SBFD, mechanism according to embodiments of the present application is described in detail above in connection with fig. 1-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 7. It should be understood that the technical features described for the method embodiments are equally applicable to the following device embodiments.

Fig. 4 shows a schematic block diagram of an apparatus 400 for configuring a seamless bi-directional 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 status of a first forwarding node of the plurality of forwarding nodes, where the SBFD configuration information includes: configuring information required for the SBFD instance associated with the segment routed SR service;

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

In a possible implementation manner, the determining module 410 is configured to determine SBFD configuration information according to an SBFD mechanism configuration status of a first forwarding node of the plurality of forwarding nodes, and specifically includes:

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

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

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

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

It should be understood that the apparatus 400 according to the embodiment of the present application may correspond to the method on the controller side in the foregoing method embodiment, and the foregoing and other management operations and/or functions of each module in the apparatus 400 are respectively for implementing the corresponding steps of each foregoing method, so that the beneficial effects in the foregoing method embodiment may also be implemented, which is not repeated herein for brevity.

Fig. 5 shows a schematic block 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:

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

The processor 501, memory 502 and transceiver 503 communicate with each other via internal communication paths to communicate control and/or data signals. In one possible design, processor 501, memory 502, and transceiver 503 may be implemented as chips. The memory 502 may store program codes and the processor 501 invokes 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 status of a first forwarding node of the plurality of forwarding nodes, where the SBFD configuration information includes: configuring information required for the SBFD instance associated with the segment routed 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 parts, a receiver and a transmitter.

Fig. 6 shows a schematic block diagram of an apparatus 600 for configuring a seamless bi-directional forwarding detection, SBFD, mechanism according to an embodiment of the present application. The apparatus 600 is applied to a network supporting a segment routed traffic engineering, SR-TE, the network 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 for the SBFD instance associated with the segment routed SR service;

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 corresponding peer node of the first forwarding node after the configuration of the SBFD instance associated with the SR service is successful.

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

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

In a possible implementation manner, in a case where 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 an SBFD instance associated with the SR service according to the SBFD configuration information, and specifically includes:

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

Optionally, the BGP message further 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 transceiver type of the first forwarding node, a field for indicating whether the SBFD configuration information is SBFD, a field for a home terminal identifier resource pool of the first forwarding node, a field for a peer terminal identifier 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 of forwarding the node side in the foregoing method embodiment, and the foregoing and other management operations and/or functions of each module in the apparatus 600 are respectively for implementing the corresponding steps of each foregoing method, so that the beneficial effects in the foregoing method embodiment may also be implemented, which is not repeated herein for brevity.

Fig. 7 shows a schematic block diagram of an apparatus 700 for configuring a seamless bidirectional forwarding detection, SBFD, mechanism in accordance with 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, the memory 702 and the transceiver 703 communicate with each other via internal communication paths to transfer control and/or data signals. In one possible design, processor 701, memory 702, and transceiver 703 may be implemented by a chip. The memory 702 may store program codes and the processor 701 invokes 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 for the SBFD instance associated with the segment routed SR service; the processor 701 is configured to configure an SBFD instance associated with the SR service according to the SBFD configuration information; after the SBFD instance configuration associated with the SR service is successful, the corresponding node of the first forwarding node carries out SBFD negotiation.

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 parts, a receiver and a transmitter.

The present application also provides a network comprising a controller, a plurality of forwarding nodes. The controller may perform the method described previously as being performed by the controller. The plurality of forwarding nodes may include a first forwarding node. 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 of configuring a seamless bidirectional forwarding detection, SBFD, mechanism, the method being 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 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 for the SBFD instance associated with the segment routed 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, the method according to embodiment 1, wherein the controller determines SBFD configuration information according to an SBFD mechanism configuration state of a first forwarding node of the plurality of forwarding nodes, including:

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

Embodiment 4, the method according to any of embodiments 1 to 3, characterized in that the SBFD configuration information is associated with a plurality of SR services.

Embodiment 5, the method according to any of embodiments 1 to 4, characterized in that 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 one of embodiments 1 to 5, wherein the SBFD configuration information includes one or more of the following: a field for indicating a transceiver type of the first forwarding node, a field for indicating whether the SBFD configuration information is SBFD, a field for a home terminal identifier resource pool of the first forwarding node, a field for a peer terminal identifier resource pool of the first forwarding node.

Embodiment 7, a method of configuring a seamless bidirectional forwarding detection, SBFD, mechanism, the method being 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:

a first forwarding node in the plurality of forwarding nodes receives a border gateway protocol BGP message sent by the controller, where the BGP message carries SBFD configuration information, and the SBFD configuration information includes: configuring information required for the SBFD instance associated with the segment routed SR service;

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

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

Embodiment 8 the method according to embodiment 7, wherein in the case where no SBFD mechanism is configured in the first forwarding node, the SBFD configuration information includes information required for the first forwarding node to create an SBFD instance;

Embodiment 9 of the method according to embodiment 7, wherein, in the case where 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 an SBFD instance associated with the SR service according to the SBFD configuration information, including:

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

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

Embodiment 12, the method according to any of embodiments 7 to 11, characterized in that 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 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 for indicating a transceiver type of the first forwarding node, a field for indicating whether the SBFD configuration information is SBFD, a field for a home terminal identifier resource pool of the first forwarding node, a field for a peer terminal identifier resource pool of the first forwarding node.

An apparatus of embodiment 14, an apparatus for configuring a seamless bidirectional forwarding detection, SBFD, mechanism, the apparatus being applied to a network supporting segment routing traffic engineering, SR-TE, the network comprising a controller and a plurality of forwarding nodes, the apparatus comprising:

a determining module, configured to determine 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 the SBFD instance associated with the segment routed SR service;

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

An embodiment 15, an apparatus according to embodiment 14, wherein the determining module is configured to determine SBFD configuration information according to an SBFD mechanism configuration status of a first forwarding node of the plurality of forwarding nodes, specifically includes:

An embodiment 16, an apparatus according to embodiment 14 or 15, wherein the BGP message further carries 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 a plurality of SR services.

The apparatus according to any one of embodiments 14 to 17, 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.

The apparatus according to embodiment 19, any one of embodiments 14 to 18, wherein the SBFD configuration information includes one or more of the following: a field for indicating a transceiver type of the first forwarding node, a field for indicating whether the SBFD configuration information is SBFD, a field for a home terminal identifier resource pool of the first forwarding node, a field for a peer terminal identifier resource pool of the first forwarding node.

Embodiment 20, an apparatus for configuring a seamless bidirectional forwarding detection, SBFD, mechanism, the apparatus being applied to a network supporting segment routing traffic engineering, SR-TE, the network comprising a controller and a plurality of forwarding nodes, the apparatus being a first forwarding node of the plurality of forwarding nodes, the apparatus comprising:

The receiving and transmitting module is configured to receive a border gateway protocol BGP message sent by the controller, where the BGP message carries SBFD configuration information, and the SBFD configuration information includes: configuring information required for the SBFD instance associated with the segment routed SR service;

the processing module is used for configuring SBFD examples associated with the SR service according to the SBFD configuration information;

the processing module is further configured to perform SBFD negotiation with a corresponding node of the first forwarding node after the configuration of the SBFD instance associated with the SR service is successful.

Embodiment 21, the apparatus according to embodiment 20, wherein in the case where no SBFD mechanism is configured in the first forwarding node, the SBFD configuration information includes information required for the first forwarding node to create an SBFD instance;

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

based on the SBFD configuration information, creating an SBFD instance associated with the SR service.

An 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 information for adjusting configuration parameters of an SBFD configured in the first forwarding node; the processing module is configured to configure an SBFD instance associated with the SR service according to the SBFD configuration information, and specifically includes:

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

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

The apparatus according to any one of embodiments 20 to 24, 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.

The apparatus according to embodiment 26, any one of embodiments 20 to 25, wherein the SBFD configuration information includes one or more of the following: a field for indicating a transceiver type of the first forwarding node, a field for indicating whether the SBFD configuration information is SBFD, a field for a home terminal identifier resource pool of the first forwarding node, a field for a peer terminal identifier resource pool of the first forwarding node.

The method disclosed in the embodiments of the present application may be applied to a processor or 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 implemented by integrated logic circuits of hardware in a processor or instructions in software form. The 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 (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, a system on chip (SoC), a central processor (central processor unit, CPU), a network processor (network processor, NP), a digital signal processing circuit (digital signal processor, DSP), a microcontroller (micro controller unit, MCU), a programmable controller (programmable logic device, PLD) or other integrated chip. The disclosed methods, steps, and logic blocks 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 a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts 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 SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct 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 present application can 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 encompasses 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, or magnetic strips, etc.), optical disks (e.g., compact disk, CD, digital versatile disk, digital versatiledisc, DVD, etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory, EPROM), cards, sticks, 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" 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 solution. 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 will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown 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 may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in 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 may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely 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 think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to 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 bi-directional forwarding detection, SBFD, mechanism, the method comprising:

the controller determines SBFD configuration information, wherein the SBFD configuration information comprises: configuring information required for the SBFD instance associated with the segment routed SR service;

and the controller sends a Border Gateway Protocol (BGP) message to the forwarding node, wherein the BGP message carries the SBFD configuration information.

2. The method of claim 1, wherein the step of determining the position of the substrate comprises,

the SBFD configuration information comprises information required by the forwarding node to create the SBFD instance; or alternatively

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 according to claim 1 or 2, characterized in that the SBFD configuration information is associated with a plurality of SR services.

5. A method according to claim 1 or 2, characterized in that 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 claim 1 or 2, wherein the SBFD configuration information includes one or more of the following: a field for indicating a transceiver type of the forwarding node, a field for indicating whether the SBFD configuration information is SBFD, a field of a home terminal identifier resource pool of the forwarding node, a field of a peer terminal identifier resource pool of the forwarding node.

7. The method according to claim 1 or 2, wherein the SBFD configuration information further comprises one or more of the following: minimum transmission interval for transmitting BFD control message; BFD controls authentication information of the message.

8. The method according to claim 1 or 2, wherein the SBFD configuration information is carried in an extended community attribute newly added to the BGP message.

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

the forwarding node 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 for the SBFD instance associated with the segment routed 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:

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

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

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

14. The method according to any of claims 9-11, 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-11, wherein the SBFD configuration information includes one or more of the following: a field for indicating a transceiver type of the forwarding node, a field for indicating whether the SBFD configuration information is SBFD, a field of a home terminal identifier resource pool of the forwarding node, a field of a peer terminal identifier resource pool of the forwarding node.

16. The method according to any one of claims 9-11, wherein the SBFD configuration information further includes one or more of: minimum transmission interval for transmitting BFD control message; BFD controls authentication information of the message.

17. The method according to any one of claims 9-11, wherein the SBFD configuration information is carried in an extended community attribute newly added to the 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 controller 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 forwarding node to perform the method of any of claims 9-17.

20. A computer readable storage medium comprising computer readable instructions which, when run on a computer, cause the computer to perform the method of any of claims 1-17.

21. A communication system comprising the controller of claim 18 and the forwarding node of claim 19.

22. A controller, comprising:

a determining module, configured to determine SBFD configuration information, where the SBFD configuration information includes: configuring information required for the SBFD instance associated with the segment routed SR service;

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

23. The controller of claim 22, wherein the controller is configured to,

24. The controller according to claim 22 or 23, wherein the BGP message further carries information of the SR service.

25. The controller according to claim 22 or 23, wherein the SBFD configuration information is associated with a plurality of SR services.

26. A controller according to claim 22 or 23, wherein the forwarding node is a head node of a tunnel or the forwarding node is a tail node of a tunnel.

27. The controller according to claim 22 or 23, wherein the SBFD configuration information includes one or more of the following: a field for indicating a transceiver type of the forwarding node, a field for indicating whether the SBFD configuration information is SBFD, a field of a home terminal identifier resource pool of the forwarding node, a field of a peer terminal identifier resource pool of the forwarding node.

28. The controller according to claim 22 or 23, wherein the SBFD configuration information further comprises one or more of the following: minimum transmission interval for transmitting BFD control message; BFD controls authentication information of the message.

29. The controller according to claim 22 or 23, wherein the SBFD configuration information is carried in an extended community attribute of the BGP message.