CN118175092A

CN118175092A - Communication method and device

Info

Publication number: CN118175092A
Application number: CN202410205184.9A
Authority: CN
Inventors: 徐婧
Original assignee: New H3C Technologies Co Ltd
Current assignee: New H3C Technologies Co Ltd
Priority date: 2024-02-23
Filing date: 2024-02-23
Publication date: 2024-06-11

Abstract

The application provides a communication method and a device, wherein the method comprises the following steps: acquiring a designated source address from the first SID list; along a first forwarding path indicated by the first SID list, sending a first SBFD message to a destination node indicated by a first destination address, where the first SBFD message includes a first IPv6 basic header, and the first IPv6 basic header includes a specified source address; the appointed source address is used for enabling the destination node to search the local forwarding table, the appointed destination address and a second SID list included in a second SRv TE Policy indicating the next hop are obtained from the matched forwarding table items, a second SBFD message is sent to the destination node indicated by the appointed destination address along a second forwarding path indicated by the second SID list, the second SBFD message comprises a second IPv6 basic header, and the second IPv6 basic header comprises the appointed destination address.

Description

Communication method and device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a communications method and apparatus.

Background

In the 5G and cloud computing era, the increase in business functions requires that existing networks provide large-scale connectivity and reliable quality of service guarantees. In the traditional network, traffic engineering (English: TRAFFIC ENGINEERING, TE for short) technology is an important means for providing service quality guarantee. In the segment routing (English: segment Routing IPv6, abbreviated: SRv) network based on the IPv6 forwarding plane, deployment and application of TE become the necessary conditions for the promotion and development of SRv technology. The SRv technology solves the problems of IPv4 and MPLS technologies by means of the strong expansion capability of IPv6, and also integrates an SDN network architecture. Therefore, SRv technology has become the core technology of the data forwarding plane in the 5G and cloud computing era.

SRv6 TE Policy is a novel tunnel drainage technology developed on the basis of SRv technology. SRv6 TE Policy consists of a number of candidate paths (CANDIDATE PATHS) with different priorities. Each candidate path includes one or more forwarding paths identified by a list of segment identifiers (english: SEGMENT IDENTIFIER, abbreviated: SIDs). Each SID list indicates an end-to-end path from a source node to a destination node and indicates that the nodes on the path follow a specified path to forward traffic.

In SRv network, when there are multiple SRv TE policies between the source node and the destination node, the source node can quickly detect the connectivity of SRv TE policies through Seamless BFD (english: alamless BFD, abbreviated: SBFD). Typically, after a SBFD session is established between the source node and the destination node, the source node encapsulates the SID list indicating the outbound path in a SBFD outbound message and forwards it along the outbound path to the destination node. Under the default condition, SBFD backhaul messages sent by the destination node are forwarded according to the existing table lookup. Upon failure of the intermediate node on the path, the SBFD backhaul message is discarded, resulting in SBFD session down. The source node may incorrectly consider the path indicated by the SID list in SRv TE Policy to be faulty.

In order to solve the above problem, the backhaul path is specified to ensure that the outbound path and the backhaul path are consistent. That is, SBFD outbound path and backhaul path matching are achieved by specifying PATH SEGMENT (i.e., end. Psid).

However, to adapt to the SBFD detection scheme based on PATH SEGMENT mode, the service functions in the source node and the destination node are modified so that the source node and the destination node can process the SBFD message carrying the PSID. For example, when the source node encapsulates SBFD the message, it needs to add a PSID after the SID list included in the segment routing header (english: segment Routing Header, abbreviated: SRH header), and set a special flag to prompt the destination node to process; the destination node needs to have a function of identifying, processing PSID, and the like.

Disclosure of Invention

In view of this, the present application provides a communication method and apparatus, which are used to solve the problem that the existing SBFD detection method based on PATH SEGMENT mode will modify the processing modes of the source node and the destination node on the SBFD message respectively, resulting in larger modification of the service functions in the node.

In a first aspect, the present application provides a communication method, where the method is applied to a source node, where a first SRv TE Policy is configured in the source node, and the first SRv TE Policy includes a first destination address and a first SID list, and the method includes:

Acquiring a designated source address from the first SID list;

Along a first forwarding path indicated by the first SID list, sending a first SBFD message to a destination node indicated by the first destination address, where the first SBFD message includes a first IPv6 basic header, and the first IPv6 basic header includes the specified source address;

The specified source address is used for enabling the destination node to search a local forwarding table, a specified destination address and a second SID list included in a second SRv TE Policy indicating a next hop are obtained from the matched forwarding table entry, a second SBFD message is sent to the destination node indicated by the specified destination address along a second forwarding path indicated by the second SID list, the second SBFD message comprises a second IPv6 basic header, and the second IPv6 basic header comprises the specified destination address;

the first forwarding path and the second forwarding path have the same node, the designated source address and the designated destination address are the same, and the source node and the destination node are the same.

In a second aspect, the present application provides a communication method, where the method is applied to a destination node, where a second SRv TE Policy is configured in the destination node, and the second SRv TE Policy includes a second SID list, and the method includes:

receiving a first SBFD message sent by a source node, wherein the first SBFD message comprises a designated source address;

searching a local forwarding table according to the appointed source address, and acquiring a matched forwarding table item from the local forwarding table, wherein the forwarding table item comprises an appointed destination address and a second SID list indicating the next hop;

Along a second forwarding path indicated by the second SID list, sending a second SBFD packet to a target node indicated by the specified destination address, where the second SBFD packet includes a second IPv6 basic header, and the second IPv6 basic header includes the specified destination address;

In a third aspect, the present application provides a communication apparatus, the apparatus being applied to a source node, in which a first SRv TE Policy has been configured, the first SRv TE Policy including a first destination address and a first SID list, the apparatus comprising:

An obtaining unit, configured to obtain a specified source address from the first SID list;

a sending unit, configured to send a first SBFD packet to a destination node indicated by the first destination address along a first forwarding path indicated by the first SID list, where the first SBFD packet includes a first IPv6 basic header, and the first IPv6 basic header includes the specified source address;

In a fourth aspect, the present application provides a communication apparatus, the apparatus being applied to a destination node, in which a second SRv TE Policy has been configured, the second SRv TE Policy including a second SID list, the apparatus comprising:

the receiving unit is configured to receive a first SBFD packet sent by a source node, where the first SBFD packet includes a specified source address;

the searching unit is used for searching a local forwarding table according to the appointed source address and acquiring a matched forwarding table item from the local forwarding table, wherein the forwarding table item comprises an appointed destination address and a second SID list indicating the next hop;

A sending unit, configured to send a second SBFD packet to a target node indicated by the specified destination address along a second forwarding path indicated by the second SID list, where the second SBFD packet includes a second IPv6 basic header, and the second IPv6 basic header includes the specified destination address;

In a fifth aspect, the application provides a network device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor to cause the processor to perform the method provided by the first aspect of the application.

In a sixth aspect, the application provides another network device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor to cause the processor to perform the method provided by the second aspect of the application.

Therefore, by applying the communication method and the device provided by the application, the source node obtains the appointed source address from the first SID list; along a first forwarding path indicated by the first SID list, the source node sends a first SBFD message to a destination node indicated by a first destination address, where the first SBFD message includes a first IPv6 basic header, and the first IPv6 basic header includes a specified source address; the appointed source address is used for enabling the destination node to search a local forwarding table, acquiring an appointed destination address and a second SID list included in a second SRv TE Policy indicating the next hop from the matched forwarding table items, and sending a second SBFD message to the destination node indicated by the appointed destination address along a second forwarding path indicated by the second SID list, wherein the second SBFD message comprises a second IPv6 basic header, and the second IPv6 basic header comprises the appointed destination address; the first forwarding path and the second forwarding path have the same path node, the designated source address and the designated destination address are the same, and the source node and the destination node are the same.

In this way, the consistency of the round trip paths of SBFD messages is ensured by the mode of designating the source address, the connectivity of SRv TE Policy is detected, and the problem that the processing modes of SBFD messages of a source node and a destination node are respectively modified by the existing SBFD detection method based on the PATH SEGMENT mode, so that the internal service functions of the nodes are greatly changed is solved. The communication method and the communication device provided by the application adopt the common IP message processing flow, the new SRv SID type is not introduced or the new message processing flow is not added, no additional requirement is imposed on a chip in the node, the node can support the existing SRv forwarding flow, the support can be realized on the software BFD and the hardware BFD, and the wide deployment and application of the SRv technology are facilitated.

Drawings

Fig. 1 is a flowchart of a communication method according to an embodiment of the present application;

FIG. 2 is a flow chart of another communication method according to an embodiment of the present application;

FIG. 3 is a schematic diagram of a networking for detecting SRv TE Policy connectivity according to an embodiment of the present application;

fig. 4 is a block diagram of a communication device according to an embodiment of the present application;

fig. 5 is a block diagram of another communication device according to an embodiment of the present application;

Fig. 6 is a hardware structure of a network device according to an embodiment of the present application.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the corresponding listed items.

It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the application. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "in response to a determination" depending on the context.

A communication method provided by the embodiment of the present application is described in detail below. Referring to fig. 1, fig. 1 is a flowchart of a communication method according to an embodiment of the present application. The method is applied to a source node. The communication method provided by the embodiment of the application can comprise the following steps.

Step 110, obtaining a specified source address from the first SID list;

Specifically, a first SRv TE Policy has been configured within the source node, the first SRv TE Policy including a first destination address and a first SID list. The first destination address specifically refers to an address indicated by an Endpoint attribute; included in the first SID list are a plurality of SIDs indicating the first forwarding path and a specified source address. The specified source address is at the end of the first SID list.

The source node obtains a specified source address from within the first SID list.

Optionally, before executing this step, the source node further receives a configuration instruction sent by the controller. The configuration instruction includes a first SRv TE Policy. The source node configures a first SRv TE Policy locally. The first SRv TE Policy includes a first destination address, a first SID list, and a specified source address.

Wherein the specified source address is configured by a manager at the controller. The specified source address is different from the address of the source node.

It is appreciated that a triplet, specifically a head-end (HeadEnd) attribute, a Color (Color) attribute, and a tail-end (Endpoint) attribute, is typically used to globally uniquely identify a SRv TE Policy. One SRv TE Policy includes multiple candidate paths (CANDIDATE PATH) with different priorities, each of which is composed of one or more forwarding paths indicated by the SID list. After the source node configures SRv TE Policy locally, the connectivity of SRv TE Policy may be detected by SBFD to determine the current state of each forwarding path.

In SRv TE Policy, the active path with the highest priority is the primary path, and the active path with the next highest priority is the backup path. The source node can detect the main path and the standby path of SRv TE Policy respectively through SBFD. If there are multiple SID lists in the active and standby paths, the source node detects all SID lists through SBFD. When detecting that each forwarding path indicated by all SID lists in SRv TE Policy main paths is abnormal, the source node switches the main paths to backup paths. SBFD can provide millisecond-level fault detection speed for SRv TE Policy connectivity detection, and rapid fault switching is achieved.

The process of detecting each SID list by the source node is the same, and in the embodiment of the present application, the first SID list is described as an example.

Step 120, along a first forwarding path indicated by the first SID list, a first SBFD packet is sent to a destination node indicated by the first destination address, where the first SBFD packet includes a first IPv6 basic header, and the first IPv6 basic header includes the specified source address.

Specifically, according to the description of step 110, after the source node obtains the specified source address from the first SID list, a first SBFD packet is generated. The first SBFD message includes a first IPv6 base header, the first IPv6 base header including a specified source address.

Wherein the first IPv6 base header includes a source address field storing a specified source address.

The source node sends a first SBFD message to the destination node indicated by the first destination address.

And after receiving the first SBFD message, the destination node acquires the specified source address from the first SBFD message. The destination node uses the appointed source address as the appointed destination address to search whether a matched forwarding table item exists in the local forwarding table.

If so, the destination node acquires the designated destination address and a second SID list included in a second SRv TE Policy indicating the next hop from the forwarding table entry. The destination node generates a second SBFD message, where the second SBFD message includes a second IPv6 basic header, and the second IPv6 basic header includes a specified destination address.

Wherein the second IPv6 base header includes a destination address field storing a specified destination address.

Along a second forwarding path indicated by the second SID list, the destination node sends a second SBFD packet to the destination node indicated by the specified destination address.

In the embodiment of the present application, the nodes of the first forwarding path and the second forwarding path are the same, that is, the first forwarding path is the outbound path of the SBFD packet, and the second forwarding path is the backhaul path of the SBFD packet. The specified source address is the same as the specified destination address, that is, the forwarding table entry includes a destination address field, where the specified source address/specified destination address is stored. In this way, the destination node may look up the local forwarding table entry based on the specified source address. The source node is the same as the target node.

It should be noted that, when generating SBFD messages, the source node and the destination node generate according to the existing SRv6 protocol, that is, firstly encapsulate the SRH header at the outer layer of the original SBFD message, and then encapsulate the IPv6 basic header. The SRH header includes a list of SIDs and the encapsulation process is the same as the existing encapsulation process and will not be repeated here. The SRH header may not include a specified source address.

The process of SBFD message transmission on the forwarding path also follows the existing SRv6 protocol and is not repeated here.

Optionally, in the embodiment of the present application, the method further includes a process that the source node determines whether itself receives the second SBFD packet within a preset time.

Specifically, after the source node sends the first SBFD message, a timer is started, and whether the second SBFD message is received is judged within a preset time set by the timer.

If the second SBFD message is received within the preset time, the source node determines that the first forwarding path is in a normal state. Whether the first forwarding path is a primary path or a backup path, the source node may continue to perform SBFD detection on the forwarding paths indicated by the other SID list.

If the second SBFD message is not received within the preset time, the source node determines that the first forwarding path is in an abnormal state. If the first forwarding path is any one of the main paths, the source node may continue to perform SBFD detection on forwarding paths indicated by other SID lists in the main path. If the first forwarding path is the last one in the main paths and the detected forwarding paths in the main paths are in abnormal states, the source node starts a main-standby path switching flow and continues to detect SBFD the forwarding paths indicated by the SID list in the standby paths.

Optionally, in the embodiment of the present application, the first SBFD packet further includes a remote identifier (english: remote-discriminator, abbreviated as RD). After receiving the first SBFD message, the destination node obtains the remote identifier from the first SBFD message, and compares the remote identifier with the local identifier.

If the remote identifier is the same as the local identifier, the destination node obtains the specified source address from the first SBFD message, and performs a process of searching the local forwarding table on the first SBFD message. If the remote identifier is different from the local identifier, the destination node discards the first SBFD message.

It should be noted that, the remote identifier is the same as the remote identifier included in the existing SBFD packet, and the fields are the same, which is not repeated here.

Another communication method provided by the embodiment of the present application is described in detail below. Referring to fig. 2, fig. 2 is a flowchart of another communication method according to an embodiment of the present application. The method is applied to the destination node. The communication method provided by the embodiment of the application can comprise the following steps.

Step 210, receiving a first SBFD message sent by a source node, where the first SBFD message includes a specified source address;

Specifically, according to the foregoing embodiment, after the source node generates the first SBFD packet, the source node sends the first SBFD packet to the destination node along the first forwarding path indicated by the first SID list. And after receiving the first SBFD message, the destination node acquires the specified source address from the first SBFD message.

The process of generating the first SBFD message by the source node is described in detail in the foregoing embodiments and will not be repeated here.

Step 220, searching a local forwarding table according to the specified source address, and acquiring a matched forwarding table item from the local forwarding table, wherein the forwarding table item comprises a specified destination address and a second SID list indicating the next hop;

specifically, according to the description of step 210, after the destination node obtains the specified source address, the destination node uses the specified source address as the specified destination address, and searches whether there is a matching forwarding table entry in the local forwarding table.

If so, the destination node acquires the designated destination address and a second SID list indicating the next hop from the forwarding table entry. Wherein the second SID list is a SID list in a second SRv TE Policy.

Optionally, before executing step 210, the destination node further receives a configuration instruction sent by the controller. The configuration instruction includes a second SRv TE Policy. The destination node configures a second SRv TE Policy locally. Wherein the second SRv TE Policy includes a second SID list.

It should be noted that the forwarding table entry includes a destination address field and a next hop field. In the embodiment of the present application, the destination address field stores a second SID list for the specified source address/specified destination address, and the next hop field stores a second SID list.

It can be understood that, in order to ensure that the forward path and the return path of the SBFD packet are consistent, a static route of the host reaching the specified destination address is generated in the destination node and is sent to the forwarding table. The specified destination address is also referred to as a specified source address. The specified destination address is carried in the second SID list and is issued to the destination node through the second SRv TE Policy, and the generation of the host static path by the destination node will be described later, which will not be repeated here.

Step 230, along a second forwarding path indicated by the second SID list, a second SBFD packet is sent to the target node indicated by the specified destination address, where the second SBFD packet includes a second IPv6 basic header, and the second IPv6 basic header includes the specified destination address.

Specifically, according to the description of step 220, the destination node obtains the specified destination address and the second SID list indicating the next hop from the forwarding table entry, and generates the second SBFD packet. The second SBFD packet includes a second IPv6 base header, where the second IPv6 base header includes a specified destination address.

Optionally, in the embodiment of the present application, the method further includes a process that the destination node generates a static route of the host after configuring the second SRv TE Policy locally.

Further, the tail of the second SID list includes a specified destination address. After the destination node obtains the specified destination address, a host static route matched with the specified destination address is generated, and the host static route comprises a destination address field and a next hop field. Wherein, the destination address field stores a designated destination address, and the next hop field stores a second SID list.

The destination node transmits the generated host static route to the local forwarding table, and generates a corresponding forwarding table item.

Optionally, in an embodiment of the present application, the first SBFD packet further includes a remote identifier. After receiving the first SBFD message, the destination node obtains the remote identifier from the first SBFD message, and compares the remote identifier with the local identifier.

If the remote identifier is the same as the local identifier, the destination node obtains the specified source address from the first SBFD message, and performs a process of searching the local forwarding table on the first SBFD message according to the specified source address. If the remote identifier is different from the local identifier, the destination node discards the first SBFD message.

Therefore, by applying the communication method provided by the application, the source node obtains the appointed source address from the first SID list; along a first forwarding path indicated by the first SID list, the source node sends a first SBFD message to a destination node indicated by a first destination address, where the first SBFD message includes a first IPv6 basic header, and the first IPv6 basic header includes a specified source address; the appointed source address is used for enabling the destination node to search a local forwarding table, acquiring an appointed destination address and a second SID list included in a second SRv TE Policy indicating the next hop from the matched forwarding table items, and sending a second SBFD message to the destination node indicated by the appointed destination address along a second forwarding path indicated by the second SID list, wherein the second SBFD message comprises a second IPv6 basic header, and the second IPv6 basic header comprises the appointed destination address; the first forwarding path and the second forwarding path have the same path node, the designated source address and the designated destination address are the same, and the source node and the destination node are the same.

The communication method provided by the present application will be described by way of an example. As shown in fig. 3, fig. 3 is a networking schematic diagram for detecting SRv TE Policy connectivity according to an embodiment of the present application. The networking includes CE1, PE1, P2, P3, P4, PE2 and CE2. The CE is user side equipment, the PE and the P are network side equipment, and each network side equipment is configured with an IP address.

PE1 is used as a source node and receives a configuration instruction issued by a controller, wherein the configuration instruction comprises SRv TE Policy PE1 PE2.SRv6 TE Policy PE1_PE2 is globally uniquely identified by a triplet, specifically a head-end attribute (1:1), a color attribute (123), and a tail-end attribute (4:1). The SRv TE Policy PE1_PE2 also includes candidate paths, and the list of segments within the candidate paths (SEGMENT LIST, which may also be referred to as a SID list) PE1_PE2 is: p1, P2, PE2, SBFD source addresses 1:2.

PE1 configures SRv TE Policy PE1 PE2 in a local SRv TE Policy module 1, and obtains SBFD source address 1:2 from SRv TE Policy PE1 PE 2.

PE1 pre-detects SRv TE Policy PE1_PE2 connectivity. SRv6 TE Policy module 1 sends a notification message to SBFD module 1 included in PE1, the notification message including SBFD source address 1:2 and SRv TE Policy PE1 PE2 destination address 4:1. SBFD module 1 establishes SBFD session with SBFD module 2 in PE2 according to the destination address in the notification message.

After SBFD session establishment is successful, SBFD module 2 generates original message 1. And the PE1 encapsulates the SRH header and the IPv6 basic header on the outer layer of the original message 1 to obtain SBFD message 1. The source address of the IPv6 basic header is 1:2, the IP address of the destination address is P1 is 2:1, and the SRH header comprises a SID list PE 1-PE 2: p1, P2, PE2.

Along the outgoing path indicated by SID list pe1_pe2, PE1 sends SBFD message 1 to PE 2. It is understood that SBFD that message 1 includes a remote identifier.

After PE1 sends SBFD message 1, a timer is started, and whether SBFD message 2 sent by PE2 is received is judged within preset time set by the timer.

PE2 is used as a destination node, and receives a configuration instruction sent by a controller, wherein the configuration instruction comprises SRv TE Policy PE2 PE1.SRv6 TE PolicyPE2_PE1 is also globally uniquely identified by a triplet, specifically a head-end attribute (4:1), a color attribute (123), and a tail-end attribute (1:1). The SRv TE Policy PE2_PE1 also includes a candidate path, and the candidate path inner segment list (SEGMENT LIST, also referred to as SID list) PE2_PE1 is: p2, P1, PE1, SBFD destination address 1:2.

PE2 configures SRv TE Policy PE 2-PE 1 in a local SRv TE Policy module 2, and obtains SBFD destination address 1:2 from SRv TE Policy PE 2-PE 1. PE2 generates a host static route to SBFD destination address 1:2 (ipv 6 route-atatic 1:2 128srv 6-policy-PE2_PE1-seglist-PE2_PE1) that includes a destination address field and a next hop field. Wherein, the destination address field stores SBFD destination address 1:2, and the next hop field stores SID list PE2 PE1.

And the PE2 transmits the generated host static route to a local forwarding table, and generates a corresponding forwarding table item.

SRv6 TE Policy module 2 sends a notification message to SBFD module 2 included in PE2, the notification message including SBFD destination address 1:2 and SRv TE Policy PE2 PE1 destination address 1:1. SBFD module 2 establishes SBFD session with SBFD module 1 in PE1 according to the destination address in the notification message.

After receiving SBFD message 1, PE2 obtains the remote identifier from SBFD message 1 (after determining that the destination address is self, unpacking SBFD message 1 to obtain the original message 1, and obtaining the remote identifier from the original message 1). PE2 compares the remote identifier with the local identifier; if the remote identifier is different from the local identifier, PE2 discards SBFD message 1.

If the remote identifier is the same as the local identifier, PE2 generates a response message and obtains SBFD source address 1:2 from SBFD message 1. PE2 takes SBFD source address 1:2 as SBFD destination address, and searches whether a matched forwarding table entry exists in the local forwarding table.

If so, PE2 obtains SBFD destination addresses 1:2 and SID list PE2 PE1 from the forwarding table entry. And the PE2 encapsulates the SRH header and the IPv6 basic header at the outer layer of the response message to obtain SBFD message 2. The source address of the IPv6 basic header is 4:1, the destination address is IP address 1:2 of P1, and the SRH header comprises a SID list PE2_PE1: p2, P1, PE1.

Along the backhaul path indicated by SID list pe2_pe1, PE2 sends SBFD packet 2 to PE 1.

If PE1 receives SBFD message 2 within the preset time, PE1 determines that the forward path indicated by SID list PE1_PE2 is in a normal state. Whether the outbound path is the primary path or the standby path, PE1 may continue to perform SBFD detection on paths indicated by other SID lists.

If PE1 does not receive SBFD message 2 within the preset time, PE1 determines that the outgoing path indicated by SID list PE1_PE2 is in an abnormal state. If the outgoing path is any one of the main paths, the PE1 may continue SBFD with the paths indicated by the other SID list in the main path. If the outgoing path is the last path in the main paths and the detected paths in the main paths are in abnormal states, the PE1 starts a main-standby path switching flow, and continues to detect SBFD paths indicated by the SID list in the standby paths.

Based on the same inventive concept, the embodiment of the application also provides a communication device corresponding to the communication method. Referring to fig. 4, fig. 4 is a communication device provided in an embodiment of the present application, where the device is applied to a source node, and a first SRv TE Policy is configured in the source node, and the first SRv TE Policy includes a first destination address and a first SID list, and the device includes:

an obtaining unit 410, configured to obtain a specified source address from the first SID list;

A sending unit 420, configured to send a first SBFD packet to a destination node indicated by the first destination address along a first forwarding path indicated by the first SID list, where the first SBFD packet includes a first IPv6 basic header, and the first IPv6 basic header includes the specified source address;

Optionally, the apparatus further comprises:

A receiving unit (not shown in the figure) configured to receive a configuration instruction sent by the controller, where the configuration instruction includes the first SRv TE Policy;

A configuration unit (not shown in the figure) is configured to configure the first SRv TE Policy locally.

Optionally, the apparatus further comprises:

A determining unit (not shown in the figure) configured to determine that the first forwarding path is in a normal state if the second SBFD packet is received within a preset time;

the determining unit (not shown in the figure) is further configured to determine that the first forwarding path is in an abnormal state if the second SBFD packet is not received within the preset time.

Optionally, the first SBFD packet further includes a remote identifier, where the remote identifier is used to enable the destination node to perform a local forwarding table lookup process on the first SBFD packet when identifying that a local identifier is the same as the remote identifier; and discarding the first SBFD message when the local identifier is identified to be different from the remote identifier.

Based on the same inventive concept, the embodiment of the application also provides a communication device corresponding to another communication method. Referring to fig. 5, fig. 5 is another communication apparatus provided in an embodiment of the present application, where the apparatus is applied to a destination node, and a second SRv TE Policy is configured in the destination node, and the second SRv TE Policy includes a second SID list, and the apparatus includes:

A receiving unit 510, configured to receive a first SBFD packet sent by a source node, where the first SBFD packet includes a specified source address;

A searching unit 520, configured to search a local forwarding table according to the specified source address, and obtain a matched forwarding table entry from the local forwarding table, where the forwarding table entry includes a specified destination address and a second SID list indicating a next hop;

A sending unit 530, configured to send a second SBFD packet to the target node indicated by the specified destination address along a second forwarding path indicated by the second SID list, where the second SBFD packet includes a second IPv6 basic header, and the second IPv6 basic header includes the specified destination address;

Wherein the first forwarding path and the second forwarding path have the same node, the specified source address and the specified destination address are the same, and the source node and the destination node are the same

Optionally, the receiving unit 510 is further configured to receive a configuration instruction sent by the controller, where the configuration instruction includes the second SRv TE Policy;

the apparatus further comprises: a configuration unit (not shown in the figure) is configured to configure the second SRv TE Policy locally.

Optionally, the second SID list includes the specified destination address, and the apparatus further includes:

A generating unit (not shown in the figure) for generating a host static route matching the specified destination address, the host static route including the second SID list, the second SID list indicating a next hop;

and the issuing unit (not shown in the figure) is used for issuing the host static route to the local forwarding table and generating a corresponding forwarding table item.

Optionally, the first SBFD packet further includes a remote identifier, and the apparatus further includes:

An identification unit (not shown in the figure) for identifying whether the remote identifier is identical to the local identifier;

The searching unit 520 is further configured to search a local forwarding table according to the specified source address if the source address is the same;

the apparatus further comprises:

A discarding unit (not shown in the figure) configured to discard the first SBFD packet if the first packet is different.

Therefore, by applying the communication device provided by the application, the source node obtains the appointed source address from the first SID list; along a first forwarding path indicated by the first SID list, the source node sends a first SBFD message to a destination node indicated by a first destination address, where the first SBFD message includes a first IPv6 basic header, and the first IPv6 basic header includes a specified source address; the appointed source address is used for enabling the destination node to search a local forwarding table, acquiring an appointed destination address and a second SID list included in a second SRv TE Policy indicating the next hop from the matched forwarding table items, and sending a second SBFD message to the destination node indicated by the appointed destination address along a second forwarding path indicated by the second SID list, wherein the second SBFD message comprises a second IPv6 basic header, and the second IPv6 basic header comprises the appointed destination address; the first forwarding path and the second forwarding path have the same path node, the designated source address and the designated destination address are the same, and the source node and the destination node are the same.

Based on the same inventive concept, the embodiment of the present application further provides a network device, as shown in fig. 6, including a processor 610, a transceiver 620, and a machine-readable storage medium 630, where the machine-readable storage medium 630 stores machine-executable instructions capable of being executed by the processor 610, and the processor 610 is caused to perform the communication method provided by the embodiment of the present application. The communication devices shown in fig. 4 and 5 may be implemented by using a hardware structure of a network device as shown in fig. 6.

The computer readable storage medium 630 may include a random access Memory (english: random Access Memory, abbreviated as RAM) or a nonvolatile Memory (english: non-volatile Memory, abbreviated as NVM), such as at least one magnetic disk Memory. Optionally, the computer readable storage medium 630 may also be at least one storage device located remotely from the aforementioned processor 610.

The processor 610 may be a general-purpose processor, including a central processing unit (english: central Processing Unit, abbreviated as CPU), a network processor (english: network Processor, abbreviated as NP), etc.; it may also be a digital signal Processor (English: DIGITAL SIGNAL Processor; DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable gate array (Field-Programmable GATE ARRAY; FPGA), or other Programmable logic device, discrete gate or transistor logic device, or discrete hardware component.

In an embodiment of the present application, processor 610, by reading machine-executable instructions stored in machine-readable storage medium 630, is caused by the machine-executable instructions to implement processor 610 itself and invoke transceiver 620 to perform the communication methods described in the previous embodiments of the present application.

Additionally, embodiments of the present application provide a machine-readable storage medium 630, the machine-readable storage medium 630 storing machine-executable instructions that, when invoked and executed by the processor 610, cause the processor 610 itself and the invoking transceiver 620 to perform the communication methods described in the foregoing embodiments of the present application.

The implementation process of the functions and roles of each unit in the above device is specifically shown in the implementation process of the corresponding steps in the above method, and will not be described herein again.

For the device embodiments, reference is made to the description of the method embodiments for the relevant points, since they essentially correspond to the method embodiments. The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purposes of the present application. Those of ordinary skill in the art will understand and implement the present application without undue burden.

For the communication device and the machine-readable storage medium embodiments, since the method content involved is substantially similar to the method embodiments described above, the description is relatively simple, and reference will only be made to part of the description of the method embodiments.

The foregoing description of the preferred embodiments of the application is not intended to be limiting, but rather to enable any modification, equivalent replacement, improvement or the like to be made within the spirit and principles of the application.

Claims

1. A communication method, wherein the method is applied to a source node, and a first SRv TE Policy is configured in the source node, and the first SRv TE Policy includes a first destination address and a first SID list, and the method includes:

Acquiring a designated source address from the first SID list;

2. The method of claim 1, wherein the method further comprises, prior to obtaining a specified source address from within the first SID list:

receiving a configuration instruction sent by a controller, wherein the configuration instruction comprises the first SRv TE Policy;

and configuring the first SRv TE Policy locally.

3. The method according to claim 1, wherein the method further comprises:

if the second SBFD message is received within the preset time, determining that the first forwarding path is in a normal state;

If the second SBFD message is not received within the preset time, determining that the first forwarding path is in an abnormal state.

4. The method of claim 1, wherein the first SBFD packet further includes a remote identifier, the remote identifier being configured to cause the destination node to perform a lookup local forwarding table processing on the first SBFD packet when the local identifier is identified as being the same as the remote identifier; and discarding the first SBFD message when the local identifier is identified to be different from the remote identifier.

5. A communication method, wherein the method is applied to a destination node, and a second SRv TE Policy is configured in the destination node, and the second SRv TE Policy includes a second SID list, and the method includes:

6. The method of claim 5, wherein prior to receiving the first SBFD message sent by the source node, the method further comprises:

Receiving a configuration instruction sent by a controller, wherein the configuration instruction comprises the second SRv TE Policy;

And configuring the second SRv TE Policy locally.

7. The method of claim 6, wherein the second SID list includes the specified destination address, and wherein after locally configuring the second SRv TE Policy, the method further comprises:

Generating a host static route matched with the appointed destination address, wherein the host static route comprises the second SID list, and the second SID list is used for indicating a next hop;

and issuing the host static route to a local forwarding table, and generating a corresponding forwarding table item.

8. The method of claim 5, wherein the first SBFD message further includes a remote identifier, and wherein after the first SBFD message sent by the receiving source node, the message further includes:

Identifying whether the remote identifier is the same as a local identifier;

If the source addresses are the same, searching a local forwarding table according to the appointed source addresses;

and if the first SBFD messages are different, discarding the first SBFD messages.

9. A communications apparatus for use with a source node, the source node having a first SRv TE Policy configured therein, the first SRv TE Policy including a first destination address and a first SID list, the apparatus comprising:

10. A communications apparatus for use with a destination node, the destination node having a second SRv TE Policy configured therein, the second SRv TE Policy comprising a second SID list, the apparatus comprising: