CN113810288A

CN113810288A - Message backhaul method and device

Info

Publication number: CN113810288A
Application number: CN202111093260.4A
Authority: CN
Inventors: 陈梦骁; 杨立苹; 李�昊; 林长望
Original assignee: New H3C Security Technologies Co Ltd
Current assignee: New H3C Security Technologies Co Ltd
Priority date: 2021-09-17
Filing date: 2021-09-17
Publication date: 2021-12-17
Anticipated expiration: 2041-09-17
Also published as: CN113810288B

Abstract

The embodiment of the application provides a message backhaul method and a message backhaul device. The scheme is as follows: receiving a request message sent by a source node; the request message comprises a DOH, and the DOH comprises a backhaul BSID; obtaining a SID list of a backhaul path corresponding to a backhaul BSID from a local; the backhaul path is a path from the destination node to the source node; and sending a response message of the request message to the source node, wherein the response message comprises a SID list, so that the end node included in the backhaul path forwards the response message to the source node according to the SID list. By applying the technical scheme provided by the embodiment of the application, the controllability of the return path of the message is improved, so that the normal operation of network service is ensured.

Description

Message backhaul method and device

Technical Field

The present application relates to the field of communications, and in particular, to a method and an apparatus for message backhaul.

Background

In SRv6, for some network services, such as Packet Internet searchers (Ping), Seamless Bidirectional Forwarding Detection (SBFD), Two-Way Active Measurement Protocol (Two-Way Active Measurement Protocol), etc., a source node sends a request Packet to a destination node, and the destination node processes the Packet content of the request Packet to obtain a response Packet and transmits the response Packet to the source node according to a specified backhaul path.

At present, after processing the message content of the received request message to obtain a response message, the destination node directly determines the backhaul path of the response message according to the routing table, thereby transmitting the response message to the source node. Since the backhaul path of the response packet is determined according to the routing table, the determination of the backhaul path is affected by the network topology and the routing calculation method. For example, the backhaul path determined according to the routing table may be a path with the shortest transmission path in the network topology, or may be a transmission path with the lowest network overhead, which causes a deviation between the backhaul path determined according to the routing table and the designated backhaul path, greatly increases the uncontrollable performance of the backhaul path, and affects the normal operation of the network service.

Disclosure of Invention

An object of the embodiments of the present application is to provide a message backhaul method and apparatus, so as to improve controllability of a backhaul path for responding to a message and ensure normal operation of a network service. The specific technical scheme is as follows:

the embodiment of the present application provides a message backhaul method, which is applied to a destination node in an Internet Protocol Version6 Routing (Segment Routing Internet Protocol Version6, SRv6) network, where the SRv6 network further includes a source node, and the method includes:

receiving a request message sent by the source node; the request message includes a Destination Options Header (DOH), and the DOH includes a backhaul Binding Identity (BSID);

obtaining a Segment Identity (SID) list of a backhaul path corresponding to the backhaul BSID from a local; the backhaul path is a path from the destination node to the source node;

and sending a response message of the request message to the source node, wherein the response message comprises the SID list, so that the end node included in the backhaul path forwards the response message to the source node according to the SID list.

Optionally, the request packet includes an Internet Protocol Version6 (IPv 6) basic header, and the DOH including the backhaul BSID is encapsulated behind the IPv6 basic header; or

And if the request message also comprises a Segment Routing Header (SRH), encapsulating the DOH comprising the backhaul BSID behind the SRH.

Optionally, the DOH includes a backhaul BSID option field, and the backhaul BSID is stored in the backhaul BSID option field.

Optionally, the step of locally obtaining the SID list of the backhaul path corresponding to the backhaul BSID specifically includes:

acquiring a target SRv6-TE Policy corresponding to the backhaul BSID from the local according to a corresponding relation between a prestored BSID and a 6 th Version of Internet Protocol Routing-Traffic Engineering Policy (SRv 6-TE Policy);

from within the target SRv6-TE Policy, a list of SIDs for the backhaul path is obtained.

acquiring a target candidate path corresponding to the backhaul BSID from the local according to a pre-stored correspondence between the BSID and the candidate path;

and acquiring a SID list of the backhaul path from the target candidate path.

Optionally, the locally acquiring the SID list of the backhaul path corresponding to the backhaul BSID specifically includes:

and according to the pre-stored corresponding relation between the BSID and the SID list, locally acquiring a target SID list corresponding to the backhaul BSID as the SID list of the backhaul path.

The embodiment of the present application further provides a message backhaul method, which is applied to a source node in an SRv6 network, where the SRv6 network further includes a destination node, and the method includes:

generating a request message, wherein the request message comprises a DOH (data over head) which comprises a backhaul BSID (base station identity);

and sending the request message to the destination node, so that the destination node acquires a SID list for representing a backhaul path from the destination node to the source node according to the backhaul BSID.

Optionally, after sending the request packet to the destination node, the method further includes:

and when a response message of the request message sent by the destination node is received and the response message comprises the SID list, determining that the destination node sends the response message through the backhaul path.

Optionally, the request message includes an IPv6 basic header, and then the DOH including the backhaul BSID is encapsulated behind the IPv6 basic header; or

And if the request message also comprises SRH, encapsulating the DOH comprising the backhaul BSID behind the SRH.

The embodiment of the present application further provides a packet backhaul apparatus, which is applied to a destination node in an SRv6 network, where the SRv6 network further includes a source node, and the apparatus includes:

a receiving module, configured to receive a request packet sent by the source node; the request message comprises a DOH, and the DOH comprises a backhaul BSID;

an obtaining module, configured to locally obtain a SID list of a backhaul path corresponding to the backhaul BSID; the backhaul path is a path from the destination node to the source node;

a first sending module, configured to send a response packet of the request packet to the source node, where the response packet includes the SID list, so that an end node included in the backhaul path forwards the response packet to the source node according to the SID list.

The embodiment of the present application further provides a packet backhaul device, which is applied to a source node in an SRv6 network, where the SRv6 network further includes a destination node, and the device includes:

a generating module, configured to generate a request packet, where the request packet includes a DOH that includes a backhaul BSID;

a second sending module, configured to send the request packet to the destination node, so that the destination node obtains, according to the backhaul BSID, a SID list used for characterizing a backhaul path from the destination node to the source node.

Embodiments of the present application also provide a destination node, including a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor being caused by the machine-executable instructions to: implementing any of the above described message backhaul method steps.

Embodiments of the present application further provide a source node, including a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor being caused by the machine-executable instructions to: implementing any of the above described message backhaul method steps.

Embodiments of the present application further provide a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor being caused by the machine-executable instructions to: implementing any of the above described message backhaul method steps.

In the technical solution provided in the embodiment of the present application, after receiving a request packet sent by a source node, because a DOH of the request packet includes a backhaul BSID, the destination node may locally obtain a SID list of a backhaul path corresponding to the backhaul BSID, thereby sending a response packet carrying the SID list to the source node.

Compared with the related art, the local storage space of the destination node stores the SID list of the backhaul path corresponding to the backhaul BSID, so that after the destination node receives the request message carrying the backhaul BSID, the destination node can locally obtain the SID list of the backhaul path corresponding to the response message according to the backhaul BSID included in the request message, thereby sending the response message to the source node along the backhaul path. While the accuracy of the determined backhaul path is ensured, since the SID list of the backhaul path corresponding to the backhaul BSID in the local storage space of the destination node can be set according to the user requirement, that is, the backhaul path of the response packet can be set according to the user requirement, the controllability of the backhaul path of the response packet is effectively improved, thereby ensuring the normal operation of the network service.

Of course, it is not necessary for any product or method of the present application to achieve all of the above-described advantages at the same time.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a schematic structural diagram of SRv6 network according to an embodiment of the present application;

fig. 2 is a first flowchart of a message backhaul method according to an embodiment of the present application;

fig. 3 is a diagram illustrating a backhaul BSID option field according to an embodiment of the present application;

fig. 4-a is a first schematic diagram of a header of a request packet according to an embodiment of the present application;

fig. 4-b is a second schematic diagram of a header of a request packet according to an embodiment of the present application;

fig. 4-c is a third schematic diagram of a header of a request packet according to the embodiment of the present application;

fig. 5 is a second flowchart of a message backhaul method according to an embodiment of the present application;

fig. 6 is a third flowchart illustrating a message backhaul method according to an embodiment of the present application;

fig. 7 is a fourth flowchart illustrating a message backhaul method according to an embodiment of the present application;

fig. 8 is a fifth flowchart of a message backhaul method according to an embodiment of the present application;

fig. 9 is a sixth flowchart of a message backhaul method according to an embodiment of the present application;

fig. 10 is a seventh flowchart of a message backhaul method according to an embodiment of the present application;

fig. 11 is a schematic diagram of a message transmission process according to an embodiment of the present application;

fig. 12 is a first schematic structural diagram of a message backhaul device according to an embodiment of the present application;

fig. 13 is a second schematic structural diagram of a message backhaul device according to an embodiment of the present application;

fig. 14 is a schematic structural diagram of a destination node according to an embodiment of the present application;

fig. 15 is a schematic structural diagram of a source node according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

In the related art, for network traffic such as Ping, SBFD, Twamp, etc., a deviation exists between a backhaul path determined based on a routing table and a designated backhaul path.

For ease of understanding, the SRv6 network shown in fig. 1 is used as an example for illustration. Now, assume that SBFD messages are used to detect connectivity of Internet Protocol Version6 Routing Policy (SRv 6-TE Policy, Segment Routing Internet Protocol Version6-Traffic Engineering Policy). The outbound path specified by the request message is: A-C-D-B, the return path appointed by the response message is B-D-C-A.

The request message sent by node a will be transmitted to node B along the specified outbound path (i.e., a-C-D-B). And the node B processes the message content of the received request message to obtain a response message. At this time, the node B queries the routing table according to the source address in the request message received by the node B, and determines the backhaul path of the response message according to the egress interface and the next hop of the routing table, so as to send the response message to the node a along the backhaul path.

Since the backhaul path is determined according to the routing table, the network topology and the routing calculation method directly affect the determined backhaul path, for example, the transmission path of the path B-a is shortest and has the least overhead, and the backhaul path is directly determined as the backhaul path of the response packet. At this time, the backhaul path determined according to the routing table will deviate from the designated backhaul path, which affects normal operation of network traffic.

In order to solve the problems in the related art, embodiments of the present application provide a message backhaul method. The method is applied to SRv6 a destination node in a network, and a source node is also included in the SRv6 network. As shown in fig. 2, fig. 2 is a first flowchart of a message backhaul method according to an embodiment of the present application. The method comprises the following steps.

Step S201, receiving a request message sent by a source node; the request message includes a DOH that includes a backhaul BSID.

Step S202, obtaining a SID list of a backhaul path corresponding to a backhaul BSID from local; the backhaul path is a path from the destination node to the source node.

Step S203, sending a response packet of the request packet to the source node, where the response packet includes a SID list, so that the end node included in the backhaul route forwards the response packet to the source node according to the SID list.

Through the method shown in fig. 2, after receiving the request packet sent by the source node, the destination node may locally obtain a SID list of a backhaul path corresponding to the backhaul BSID because the DOH of the request packet includes the backhaul BSID, thereby sending a response packet carrying the SID list to the source node.

The following examples are given to illustrate the examples of the present application.

For the step S201, the request packet sent by the source node is received; the request message includes a DOH that includes a backhaul BSID.

In this step, SRv6 the source node in the network sends the request message to the destination node along the outbound path of the request message. The destination node will receive the request message.

In this embodiment, the request packet may be transmitted to the destination node according to the outbound path determined by the routing table. The request packet may also be forwarded to the destination node according to the SID list.

In an optional embodiment, when the request message is transmitted to the destination node according to the outbound path determined by the routing table, the message header of the request message includes an Internet Protocol Version6 (IPv 6) basic header and the DOH.

In another alternative embodiment, when the request packet is forwarded to the destination node according to the SID list, the packet header of the request packet includes an IPv6 basic header, an SRH, and a DOH. Wherein, the SRH is packaged with SID list.

In this embodiment, the DOH in the header of the request packet includes a backhaul BSID Option field (also referred to as Reverse BSID Option), and the backhaul BSID Option field stores the backhaul BSID.

For convenience of understanding, fig. 3 is an exemplary illustration of a backhaul BSID option field provided in an embodiment of the present application.

The Option Type (Option Type), the Option Data length (Opt Data Len), and the backhaul BSID (reverse BSID) are included in the backhaul BSID Option field shown in fig. 3. Wherein, if The option type needs to be standardized, The option type can be distributed by The Internet Assigned Numbers Authority (IANA); if no standardization is required, values not occupied in the current IPv6 protocol standard, such as binary numbers: 00011101, etc. The length of the option data can be a preset value, such as 16. Here, the option type and the option data length of the field in the backhaul BSID option are not specifically described.

For the backhaul BSID included in the request message, the source node may obtain the backhaul BSID in various ways, and encapsulate the backhaul BSID in the DOH of the packet header of the request message.

In an optional embodiment, when obtaining the backhaul BSID, the source node may receive a packet carrying the BSID sent by a user, and obtain the backhaul BSID from the received packet.

In another optional embodiment, when the backhaul BSID is obtained, the destination node may send the backhaul BSID to the source node through a Border Gateway routing Protocol-Link State (BGP-LS) Protocol. The source node will receive the backhaul BSID.

In this embodiment, the obtaining manner of the backhaul SID carried in the request packet is not specifically limited.

In an optional embodiment, when the header of the request message does not include the SRH, that is, the header of the request message includes the IPv6 basic header and the DOH, the DOH including the backhaul BSID is encapsulated after the IPv6 basic header. Specifically, as shown in fig. 4-a, fig. 4-a is a first schematic diagram of a header of a request packet provided in this embodiment. The backhaul BSID option field of the DOH shown in fig. 4-a includes the backhaul BSID.

In another alternative embodiment, when the header of the request message includes the SRH, that is, the header of the request message includes the IPv6 basic header, the SRH, and the DOH including the backhaul BSID is encapsulated after the SRH. The number of DOHs may be one or two. As shown in particular in fig. 4-b and 4-c. Fig. 4-b is a second schematic diagram of a header of a request packet according to an embodiment of the present application; fig. 4-c is a third schematic diagram of a header of a request packet according to the embodiment of the present application. The backhaul BSID option field of the DOH shown in fig. 4-b and 4-c includes the backhaul BSID.

In the related art, when the header of the packet includes the IPv6 basic header, the SRH, and the DOH at the same time, the DOH may be encapsulated before the SRH, or the DOH may be encapsulated after the SRH. For ease of understanding, the description will be made by taking fig. 4-c as an example.

Two DOHs are included in the header shown in fig. 4-c, one DOH is a DOH that does not include the backhaul BSID option field (i.e., the DOH before SRH shown in fig. 4-c is denoted as a first DOH), and the other DOH is a DOH that includes the backhaul BSID option field (i.e., the DOH after SRH shown in fig. 4-c is denoted as a second DOH).

In the header shown in fig. 4-c, the first DOH is encapsulated before SRH. Because the SRH of the request message includes the SID list of the outbound path, the request message is transmitted to the destination node according to the outbound path. After each end node (also called Endpoint, i.e. the node corresponding to each SID in the SID list) on the outbound path receives the request message, because the first DOH is encapsulated before the SRH, the end node preferentially processes the field included in the first DOH, and then forwards the request message according to the outbound path indicated by the SID list included in the SRH. At this time, the end node will not process the second DOH in the header of the request message. I.e., the end node will not process the backhaul BSID in the backhaul BSID option field of the second DOH. When the end node forwards the request message to the last end node (i.e. the destination node) on the outbound path according to the outbound path indicated by the SID list included in the SRH, the destination node will process the DOH in the request message after receiving the request message. That is, the backhaul BSID in the backhaul BSID option field of the second DOH is processed by the destination node.

In the embodiment of the application, after the DOH including the backhaul BSID is encapsulated in the SRH, each end node on the outbound path except the destination node can preferentially forward the received request packet without processing the DOH including the backhaul BSID in the request packet, so that it is ensured that only the destination node processes the DOH including the backhaul BSID in the request packet, and a guarantee is provided for normal network service.

The request message may be a message corresponding to a Ping service, an SBFD service, a Twamp service, and other network services. The message content of the request message is different according to different network services. Here, the request message is not particularly limited.

For the above step S202, a SID list of backhaul paths corresponding to backhaul BSIDs is locally obtained; the backhaul path is a path from the destination node to the source node.

In the embodiment of the present application, the destination node stores a correspondence between the BSID and the transmission path in advance. After receiving the request message, the destination node may search whether a transmission path corresponding to the backhaul BSID in the request message exists according to a pre-stored correspondence relationship. If the transmission path corresponding to the backhaul BSID is found, the destination node may determine the found transmission path as the backhaul path corresponding to the response packet of the request packet. At this time, the destination node may locally obtain a list of SIDs for the backhaul path. That is, a list of SIDs of transmission paths corresponding to backhaul BSIDs is acquired. Wherein the local is the destination node.

For the step S203, a response packet of the request packet is sent to the source node, where the response packet includes a SID list, so that the end node included in the backhaul path forwards the response packet to the source node according to the SID list.

In this step, after receiving the request message, the destination node may parse the request message, and process the message content of the parsed request message, thereby obtaining the response content corresponding to the request message. At this time, the destination node may construct a response packet according to the SID list and the response content acquired in step S202, and send the response packet to the source node.

Because the message contents of the request messages corresponding to different network services are different, the processing modes adopted by the destination node when processing the message contents of the request messages of different network services are also different. Here, the processing method of the message content of the request message is not particularly limited.

In this embodiment, the response packet includes a packet header and a packet payload. Wherein, the message load includes the above response content, and the message header includes an IPv6 basic header and an SRH. The SRH includes a SID list, i.e., the SID list of the backhaul path.

After the end node on the return path receives the response message sent by the destination node, the received response message is forwarded according to the SID list in the response message, so that the response message is forwarded to the source node along the return path.

In an optional embodiment, according to the method shown in fig. 2, an embodiment of the present application further provides a message backhaul method. As shown in fig. 5, fig. 5 is a second flowchart of a message backhaul method according to the embodiment of the present application. The method comprises the following steps.

Step S501, receiving a request message sent by a source node; the request message includes a DOH that includes a backhaul BSID.

Step S501 is the same as step S201.

Step S502, according to the pre-stored corresponding relationship between BSID and SRv6-TE Policy, locally obtain the target SRv6-TE Policy corresponding to the backhaul BSID.

In this embodiment of the present application, the correspondence between the BSID and the transmission path pre-stored in the destination node may be represented as: correspondence between BSID and SRv6-TE Policy.

After reading the backhaul BSID from the backhaul BSID option field of the DOH of the request message, the destination node may search whether there is a target SRv6-TE Policy corresponding to the backhaul BSID according to a correspondence between the BSID and SRv6-TE Policy stored in advance. When the target SRv6-TE Policy is located, the destination node can locally obtain the target SRv6-TE Policy.

In the embodiment of the present application, the correspondence between the BSID and the SRv6-TE Policy may be expressed in various forms. For example, the correspondence between BSID and SRv6-TE Policy may be expressed as: the correspondence between BSID and identification information of SRv6-TE Policy. The identification information of SRv6-TE Policy may be composed of information such as numbers, letters, etc., or may be represented by triplet of SRv6-TE Policy. The expression format of the correspondence between BSID and SRv6-TE Policy is not particularly limited.

The SRv6-TE Policy may consist of BSID and multiple Candidate Paths (Candidate Paths) with different priorities. Each candidate path includes one or more forwarding paths identified by a SID List (Segment List). When a candidate path consists of multiple SID lists, there is a corresponding weight for each SID list. The SID list contains message forwarding path information, and consists of SIDs (IPv6 addresses) of each node on the forwarding path.

In step S503, a SID list of the backhaul path is obtained from the target SRv6-TE Policy.

In this embodiment, after finding the target SRv6-TE Policy, the destination node may select a candidate path with the highest priority in the targets SRv6-TE Policy as a target candidate path. When the target candidate path consists of a list of SIDs, the destination node may determine the list of SIDs as the target list of SIDs. At this time, the destination node obtains the target SID list from the locally stored target SRv6-TE Policy as the SID list of the backhaul path corresponding to the backhaul BSID.

When the target candidate path is composed of a plurality of SID lists, the destination node may determine a target SID list from the plurality of SID lists according to the weight of each SID list. At this time, the destination node obtains the target SID list from the locally stored target SRv6-TE Policy as the SID list of the backhaul path corresponding to the backhaul BSID.

The weight corresponding to each SID list in the candidate path is used for load sharing.

For ease of understanding, the SID lists included in the candidate paths are list 1 and list 2. Wherein the weight of list 1 is 2 and the weight of list 2 is 8. When the candidate path is determined as the target candidate path, the probability that the list 1 is determined as the target SID list is 2/(2+8) ═ 0.2, that is, the probability that the forwarding path identified by the list 1 is determined as the backhaul path is 20%; the probability that list 2 is determined to be the target SID list is 8/(2+8) ═ 0.8, i.e., the probability that the forwarding path identified by list 2 is determined to be a forwarding path is 80%. For example, when the target candidate path corresponding to the plurality of request messages is the candidate path, the backhaul paths of 20% of the response messages corresponding to the request messages are: in the forwarding paths identified in table 1, the backhaul paths of response messages corresponding to 80% of the request messages are: list 2 identifies the forwarding paths.

In this embodiment, when the target candidate path is composed of a plurality of SID lists, under the condition that it is ensured that the probability that the forwarding path identified by each SID list is selected as the backhaul path matches the weight corresponding to each SID list, any SID list in the target candidate path may be determined as the target SID list, that is, the SID list of the backhaul path corresponding to the backhaul BSID.

Still taking the above list 1 and list 2 as examples, after determining that the candidate paths including the list 1 and list 2 are target candidate paths, the destination node may determine the list 1 and list 2 as SID lists of the backhaul paths according to a ratio of 2:8, respectively. Here, the method of determining the SID list of the backhaul path is not particularly limited.

The above steps S502 to S503 are refinements of the above step S202.

Step S504, a response message of the request message is sent to the source node, and the response message includes a SID list, so that the end node included in the backhaul path forwards the response message to the source node according to the SID list.

Step S504 is the same as step S203.

In another optional embodiment, according to the method shown in fig. 2, an embodiment of the present application further provides a message backhaul method. As shown in fig. 6, fig. 6 is a third flowchart illustrating a message backhaul method according to an embodiment of the present application. The method comprises the following steps.

Step S601, receiving a request message sent by a source node; the request message includes a DOH that includes a backhaul BSID.

Step S601 is the same as step S201.

Step S602, according to the pre-stored correspondence between the BSID and the candidate route, locally acquire a target candidate route corresponding to the backhaul BSID.

In this embodiment of the present application, the correspondence between the BSID and the transmission path pre-stored in the destination node may be represented as: correspondence between BSID and candidate path.

After reading the backhaul BSID from the backhaul BSID option field of the DOH of the request message, the destination node may search whether a target candidate path corresponding to the backhaul BSID exists according to a correspondence between the BSID and the candidate path stored in advance. When the target candidate path is found, the destination node may locally acquire the target candidate path.

In step S603, a SID list of the backhaul path is acquired from the target candidate path.

In an alternative embodiment, when the target candidate path consists of a SID list, the destination node may determine the SID list as a target SID list, that is, a SID list of a backhaul path corresponding to the backhaul BSID. That is, the forwarding path identified by the SID list is determined as the backhaul path of the response packet corresponding to the request packet.

In another alternative embodiment, when the target candidate path is composed of a plurality of SID lists, the destination node may determine a target SID list, that is, a SID list of the backhaul path corresponding to the backhaul BSID, according to a weight corresponding to each SID list. Specifically, refer to the description in step S503, which is not described herein again.

The above steps S602 to S603 are refinements of the above step S202.

Step S604, sending a response packet of the request packet to the source node, where the response packet includes a SID list, so that the end node included in the backhaul route forwards the response packet to the source node according to the SID list.

Step S604 is the same as step S203.

In yet another alternative embodiment, according to the method shown in fig. 2, an embodiment of the present application further provides a message backhaul method. As shown in fig. 7, fig. 7 is a fourth flowchart illustrating a message backhaul method according to an embodiment of the present application. The method comprises the following steps.

Step S701, receiving a request message sent by a source node; the request message includes a DOH that includes a backhaul BSID.

Step S701 is the same as step S201.

Step S702, according to the pre-stored correspondence between the BSID and the SID list, locally acquire a target SID list corresponding to the backhaul BSID as a SID list of the backhaul path.

In this embodiment of the present application, the correspondence between the BSID and the transmission path pre-stored in the destination node may be represented as: the correspondence between BSID and SID list.

After reading the backhaul BSID from the backhaul BSID option of the DOH of the request message, the destination node may search whether a target SID list corresponding to the BSID exists according to a correspondence between the BSID and the SID list stored in advance. When the target SID list is found, the destination node may determine the target SID list as a SID list for the backhaul path corresponding to the backhaul BSID. That is, the forwarding path identified by the target SID list is determined as the backhaul path of the response packet corresponding to the request packet.

The above step S702 is a refinement of the above step S202.

Step S703, sending a response packet of the request packet to the source node, where the response packet includes a SID list, so that the end node included in the backhaul route forwards the response packet to the source node according to the SID list.

Step S703 is the same as step S203.

In the embodiments shown in fig. 5 to 7, the correspondence between BSIDs and transmission paths may be expressed in various forms. I.e., the correspondence between BSID and SRv6-TE Policy in the embodiment shown in fig. 5, the correspondence between BSID and candidate path in the embodiment shown in fig. 6, and the correspondence between BSID and SID list in the embodiment shown in fig. 7. The user can set corresponding relations of different forms in the destination node according to specific requirements, control over the determined backhaul path is achieved, the flexibility of the corresponding relation between the BSID and the transmission path is improved, and meanwhile the controllability of the determined backhaul path is improved, so that normal operation of network services is guaranteed.

In an optional embodiment, according to the method shown in fig. 2, an embodiment of the present application further provides a message backhaul method. As shown in fig. 8, fig. 8 is a fifth flowchart illustrating a message backhaul method according to an embodiment of the present application. The method comprises the following steps.

Step S801, receiving a request message sent by a source node; the request message includes a DOH that includes a backhaul BSID.

Step S802, obtaining a SID list of a backhaul path corresponding to a backhaul BSID from local; the backhaul path is a path from the destination node to the source node.

Step S803, a response packet of the request packet is sent to the source node, where the response packet includes a SID list, so that the end node included in the backhaul route forwards the response packet to the source node according to the SID list.

The above steps S801 to S803 are the same as the above steps S201 to S203.

Step S804, discards the request message.

In the embodiment of the present application, due to the influence of the network environment of the SRv6 network and other factors, an error may occur in the backhaul BSID in the request message sent by the source node to the destination node. At this time, when the destination node executes the step S802, the destination node cannot acquire the SID list of the backhaul path corresponding to the backhaul BSID (i.e., the erroneous backhaul BSID) according to the correspondence relationship between the BSID and the transmission path, which is stored in advance. When the destination node locally acquires the SID list of the backhaul path corresponding to the backhaul BSID, the destination node executes the above step S803. When the destination node does not locally acquire the SID list of the backhaul path corresponding to the backhaul BSID, the destination node executes the step S804.

In the embodiment shown in fig. 8, after receiving the request message, the target node first obtains the SID list of the backhaul path corresponding to the backhaul BSID, and then analyzes and processes the request message to obtain a response message. In addition, after receiving the request message, the target node may also analyze and process the request message to obtain a response message, and then obtain the SID list of the backhaul path corresponding to the backhaul BSID, at this time, if the SID list of the backhaul path corresponding to the backhaul BSID is not obtained, the target node may discard the request message and the response message.

In this embodiment of the present application, if the SID list of the backhaul path corresponding to the backhaul BSID is not obtained, the destination node may perform other processing on the received request packet besides discarding the request packet.

In an optional embodiment, if the SID list of the backhaul path corresponding to the backhaul BSID is not obtained, the destination node may send a notification message to the source node, where the notification message is used to indicate that the backhaul BSID included in the request message is incorrect.

For example, when the SID list of the backhaul path corresponding to the backhaul BSID is not acquired, the destination node may send an Internet Control Message Protocol (ICMP) Message to the source node. The ICMP message may include the backhaul BSID in the request message. After receiving the ICMP message, the source node may determine that the backhaul BSID is erroneous.

In an optional embodiment, the ICMP message may be sent to the source node based on a transmission path determined by the routing table, where a sending manner of the ICMP message is not specifically limited.

In another optional embodiment, if the SID list of the backhaul path corresponding to the backhaul BSID is not obtained, the destination node may determine the backhaul path according to the routing table, so as to send a response packet corresponding to the request packet to the source node based on the backhaul path.

Based on the same inventive concept, according to the message backhaul method provided in the embodiment of the present application, the embodiment of the present application further provides a message backhaul method. As shown in fig. 9, fig. 9 is a sixth flowchart illustrating a message backhaul method according to an embodiment of the present application. The method is applied to SRv6 a source node in a network, and a destination node is also included in the SRv6 network. The method comprises the following steps.

Step S901 generates a request packet, where the request packet includes a DOH, and the DOH includes a backhaul BSID.

In an alternative embodiment, the header of the request message may include an IPv6 basic header and a DOH. At this point, the DOH including the backhaul BSID is encapsulated behind the IPv6 base header.

In another alternative embodiment, the header of the request message may include an IPv6 basic header, SRH, and DOH. At this point, the DOH including the backhaul BSID is encapsulated after the SRH.

The DOH includes a backhaul BSID option field, and the backhaul BSID option field stores a backhaul BSID therein. The backhaul BSID may be configured by the user for the request message. Or sent to the source node by the destination node through the BGP-LS protocol. The backhaul BSID in the backhaul BSID option of the DOH can be obtained as described above, and is not described herein.

Step S902, sending a request packet to the destination node, so that the destination node obtains, according to the backhaul BSID, a SID list for characterizing a backhaul path from the destination node to the source node.

In an optional embodiment, when the header of the request packet includes the IPv6 basic header and the DOH, the source node may determine a journey path of the request packet according to the routing table, and send the request packet to the destination node along the journey path.

In another optional embodiment, when the header of the request message includes the IPv6 basic header, the SRH, and the DOH, the source node may obtain a SID list of the forward path, encapsulate the SID list into the SRH of the request message, and send the request message to the destination node. Each end node on the outbound path forwards the request message according to the SID list.

In this embodiment of the present application, since the DOH of the request packet includes the backhaul BSID, after receiving the request packet sent by the source node, the destination node may locally obtain a SID list of a backhaul path corresponding to the backhaul BSID, so as to send a response packet of the request packet according to a forwarding path identified by the SID.

Through the method shown in fig. 9, the source node sends the request packet carrying the backhaul BSID to the destination node, so that the destination node can locally obtain the SID list of the backhaul path corresponding to the backhaul BSID according to the pre-stored correspondence between the BSID and the transmission path after receiving the request packet, and thus send the response packet including the SID list to the source node, so that the response packet can be sent to the source node along the forwarding path identified by the SID list.

Compared with the related art, the accuracy of the determined backhaul path is ensured, and meanwhile, the SID list of the backhaul path corresponding to the backhaul BSID in the local storage space of the destination node can be set according to the user requirement, that is, the backhaul path of the response packet can be set according to the user requirement, so that the controllability of the backhaul path of the response packet is effectively improved, and the normal operation of the network service is ensured.

In an optional embodiment, according to the method shown in fig. 9, an embodiment of the present application further provides a message backhaul method. As shown in fig. 10, fig. 10 is a seventh flowchart illustrating a message backhaul method according to an embodiment of the present application. The method comprises the following steps.

Step S1001, a request message is generated, the request message includes a DOH, and the DOH includes a backhaul BSID.

Step S1002, a request packet is sent to the destination node, so that the destination node obtains, according to the backhaul BSID, a SID list for representing a backhaul path from the destination node to the source node.

The above-described steps S1001 to S1002 are the same as the above-described steps S901 to S902.

Step S1003, when receiving a response packet of the request packet sent by the destination node, and the response packet includes a SID list, determining that the destination node sends the response packet through the backhaul path.

In this step, within a preset time length after the source node sends the request message to the destination node, if a response message of the request message sent by the destination node is received and the SRH of the message header of the response message includes a SID list, the source node may determine that the response message is sent by the destination node through the determined backhaul path.

The preset time length may be determined according to a transmission distance between the source node and the destination node and a processing time length of the destination node for the request packet, where the preset time length is not specifically limited.

In the embodiment of the present application, the source node can accurately determine the response packet sent through the specified backhaul path through the SID list carried in the received response packet, thereby ensuring the accuracy of the network service performed based on the SRv6 network.

In an optional embodiment, the source node may receive a response packet that does not carry the SID list within a preset time length after sending the request packet to the destination node.

For example, when the destination node does not acquire the SID list of the backhaul path corresponding to the backhaul BSID, the destination node may send a response packet of the request packet to the source node according to the routing table. After receiving the response message, the source receives a SID list of the backhaul path that does not include the backhaul BSID.

For another example, when the target node acquires the SID list of the backhaul path corresponding to the backhaul BSID, the target node sends a response packet of the request packet according to the backhaul path identified by the SID list. In order to reduce the burden of the source node, the response message sent by the destination node includes SID attachment behaviors (Flavors), and the SID attachment behaviors are: PSP (Pelletimese Segment POP of the SRH). PSP denotes that the penultimate Endpoint node on the backhaul path (i.e., the previous Endpoint of the source node) performs an SRH removal operation. At this time, the response message received by the source node will not include the SID list of the backhaul path corresponding to the backhaul BSID.

In another optional embodiment, the source node may further receive a notification message sent by the destination node for the request message within a preset time length after the source node sends the request message to the destination node. The notification message may include the backhaul BSID.

When the destination node does not locally acquire the SID list of the backhaul path corresponding to the backhaul BSID, it may be determined that the BSID included in the request message is in error. At this time, the destination node may send the notification message, such as the ICMP message, to the source node.

For ease of understanding, the above message backhaul procedure is described below with reference to fig. 11. Fig. 11 is a schematic diagram of a message transmission process according to an embodiment of the present application.

In the SRv6 network shown in fig. 11, node a deploys SRv6-TE Policy a for packets transmitted along path 11 to node B, specifically, SRv6-TE Policy a: BSID 1, Path (Path) C, D, B. Node B deploys SRv6-TE Policy B for packets transmitted to node a along path 12, specifically, SRv6-TE Policy B: BSID is 2::2, Path is < D, C, A >.

After the node A generates the message A which needs to be sent to the node B, a request message can be constructed according to the deployed BSIDs in SRv6-TE Policy A and SRv6-TE Policy B. That is, the node a may encapsulate a SID list corresponding to the transmission Path in SRv6-TE Policy a, that is, Path ═ C, D, B > into the SRH of the packet header of the packet a, and encapsulate the BSID in SRv6-TE Policy B, that is, 2::2 into the DOH of the packet header of the packet a, to obtain the request packet, where the packet header of the request packet is the packet header 21 shown in fig. 11.

Node a sends the request message to node B via path 11 in fig. 11. After receiving the request message, the node B may locally obtain, according to the backhaul BSID included in the request message, a SID list of a backhaul Path corresponding to the backhaul BSID, that is, locally obtain SRv6 — Path ═ D, C, a > in TE Policy B. The node B encapsulates the SID list into a response message corresponding to the request message, and a header of the response message is a header 22 shown in fig. 11.

And the node B sends the response message to the node A according to the Path < D, C and A > encapsulated in the message header of the response message. That is, node B sends the response message to node a according to path 12 shown in fig. 11.

Based on the same inventive concept, according to the message backhaul method provided in the embodiment of the present application, the embodiment of the present application further provides a message backhaul device. The device is applied to the destination node. As shown in fig. 12, fig. 12 is a schematic view of a first structure of a message backhaul device according to an embodiment of the present application. The apparatus includes the following modules.

A receiving module 1201, configured to receive a request packet sent by a source node; the request message comprises a DOH, and the DOH comprises a backhaul BSID;

an obtaining module 1202, configured to locally obtain a SID list of a backhaul path corresponding to a backhaul BSID; the backhaul path is a path from the destination node to the source node;

a first sending module 1203, configured to send a response packet of the request packet to the source node, where the response packet includes a SID list, so that an end node included in the backhaul path forwards the response packet to the source node according to the SID list.

If the request message also includes a Segment Routing Header (SRH), then a DOH including a backhaul BSID is encapsulated behind the SRH.

Optionally, the DOH includes a backhaul BSID option field, and the backhaul BSID option field stores a backhaul BSID.

Optionally, the obtaining module 1202 may be specifically configured to locally obtain a target SRv6-TE Policy corresponding to the backhaul BSID according to a pre-stored correspondence between the BSID and the SRv6-TE Policy; from within the target SRv6-TE Policy, a list of SIDs for the backhaul path is obtained.

Optionally, the obtaining module 1202 may be specifically configured to locally obtain a target candidate path corresponding to the backhaul BSID according to a correspondence between a pre-stored BSID and a candidate path; and acquiring a SID list of the backhaul path from the target candidate path.

Optionally, the obtaining module 1202 may be specifically configured to locally obtain, according to a pre-stored correspondence between the BSID and the SID list, a target SID list corresponding to the backhaul BSID, as the SID list of the backhaul path.

Based on the same inventive concept, according to the message backhaul method provided in the embodiment of the present application, the embodiment of the present application further provides a message backhaul device. The device is applied to the source node. As shown in fig. 13, fig. 13 is a schematic diagram of a second structure of a message backhaul device according to an embodiment of the present application. The apparatus includes the following modules.

A generating module 1301, configured to generate a request packet, where the request packet includes a DOH, and the DOH includes a backhaul BSID;

a second sending module 1302, configured to send a request packet to a destination node, so that the destination node obtains, according to a backhaul BSID, a SID list used for representing a backhaul path from the destination node to a source node.

Optionally, the message backhaul apparatus may further include:

and the determining module is used for determining that the destination node sends the response message through the return path when the response message of the request message sent by the destination node is received and the response message comprises the SID list after the request message is sent to the destination node.

By the apparatus provided in the embodiment of the present application, after receiving a request packet sent by a source node, because a DOH of the request packet includes a backhaul BSID, the destination node may locally obtain a SID list of a backhaul path corresponding to the backhaul BSID, thereby sending a response packet carrying the SID list to the source node.

Based on the same inventive concept, according to the message backhaul method provided in the foregoing embodiment of the present application, an embodiment of the present application further provides a destination node, as shown in fig. 14, including a processor 1401 and a machine-readable storage medium 1402, where the machine-readable storage medium 1402 stores machine-executable instructions that can be executed by the processor 1401. Processor 1401 is caused by machine executable instructions to implement any of the steps shown in fig. 2, 5-8 described above.

In an optional embodiment, as shown in fig. 14, the destination node may further include: a communication interface 1403 and a communication bus 1404; the processor 1401, the machine-readable storage medium 1402 and the communication interface 1403 are used for communication between the destination node and other devices via a communication bus 1404.

Based on the same inventive concept, according to the message backhaul method provided in the embodiment of the present application, as shown in fig. 15, the embodiment of the present application further provides a source node, which includes a processor 1501 and a machine-readable storage medium 1502, where the machine-readable storage medium 1502 stores machine-executable instructions that can be executed by the processor 1501. Processor 1501 is caused by machine executable instructions to implement any of the steps shown in fig. 9-10 described above.

In an optional embodiment, as shown in fig. 15, the source node may further include: a communication interface 1503 and a communication bus 1504; the processor 1501, the machine-readable storage medium 1502 and the communication interface 1503 communicate with each other through the communication bus 1504, and the communication interface 1503 is used for communication between the source node and other devices.

Based on the same inventive concept, according to the message backhaul method provided in the embodiment of the present application, an embodiment of the present application further provides a machine-readable storage medium, where a machine-executable instruction capable of being executed by a processor is stored in the machine-readable storage medium. The processor is caused by machine executable instructions to implement any of the steps shown in fig. 2, 5-10 above.

The communication bus may be a PCI (Peripheral Component Interconnect) bus, an EISA (Extended Industry Standard Architecture) bus, or the like. The communication bus may be divided into an address bus, a data bus, a control bus, etc.

The machine-readable storage medium may include a RAM (Random Access Memory) and a NVM (Non-Volatile Memory), such as at least one disk Memory. Additionally, the machine-readable storage medium may be at least one memory device located remotely from the aforementioned processor.

The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also DSPs (Digital Signal Processing), ASICs (Application Specific Integrated circuits), FPGAs (Field Programmable Gate arrays) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.

It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the embodiments of the message backhaul apparatus, the destination node, the source node, and the machine-readable storage medium, since they are substantially similar to the embodiments of the message backhaul method, the description is relatively simple, and for relevant points, reference may be made to part of the description of the embodiments of the message backhaul method.

The above description is only for the preferred embodiment of the present application, and is not intended to limit the scope of the present application. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application are included in the protection scope of the present application.

Claims

1. A message backhaul method is applied to a destination node in SRv6 network, the SRv6 network further includes a source node, and the method includes:

receiving a request message sent by the source node; the request message comprises a destination option header DOH, and the DOH comprises a backhaul binding segment identifier BSID;

acquiring a Segment Identifier (SID) list of a backhaul path corresponding to the backhaul BSID from a local area; the backhaul path is a path from the destination node to the source node;

2. The method of claim 1, wherein the request message includes an IPv6 base header, and the DOH including the backhaul BSID is encapsulated after the IPv6 base header; or

3. The method of claim 1, in which the DOH comprises a backhaul BSID option field in which the backhaul BSID is stored.

4. The method of claim 1, wherein the step of locally obtaining the SID list of the backhaul path corresponding to the backhaul BSID specifically includes:

acquiring a target SRv6-TE Policy corresponding to the backhaul BSID from the local according to a pre-stored corresponding relation between the BSID and SRv6-TE Policy;

5. The method of claim 1, wherein the step of locally obtaining the SID list of the backhaul path corresponding to the backhaul BSID specifically includes:

and acquiring a SID list of the backhaul path from the target candidate path.

6. The method of claim 1, wherein the locally obtaining the SID list of the backhaul path corresponding to the backhaul BSID comprises:

7. A message backhaul method is applied to a source node in SRv6 network, the SRv6 network further includes a destination node, the method includes:

generating a request message, wherein the request message comprises a Destination Option Header (DOH), and the DOH comprises a backhaul Binding Segment Identifier (BSID);

and sending the request message to the destination node, so that the destination node acquires a segment identifier SID list for representing a backhaul path from the destination node to the source node according to the backhaul BSID.

8. The method of claim 7, wherein after sending the request packet to the destination node, the method further comprises:

9. The method of claim 7, wherein the request message includes an IPv6 base header, and the DOH including the backhaul BSID is encapsulated after the IPv6 base header; or

10. The method of claim 7, in which the DOH comprises a backhaul BSID option field in which the backhaul BSID is stored.

11. A message backhaul apparatus, applied to a destination node in SRv6 network, wherein the SRv6 network further includes a source node, the apparatus includes:

a receiving module, configured to receive a request packet sent by the source node; the request message comprises a destination option header DOH, and the DOH comprises a backhaul binding segment identifier BSID;

an obtaining module, configured to locally obtain a segment identifier SID list of a backhaul path corresponding to the backhaul BSID; the backhaul path is a path from the destination node to the source node;

12. A message backhaul apparatus, applied to a source node in SRv6 network, wherein the SRv6 network further includes a destination node, the apparatus comprising:

a generating module, configured to generate a request packet, where the request packet includes a destination option header DOH, and the DOH includes a backhaul binding segment identifier BSID;

a second sending module, configured to send the request packet to the destination node, so that the destination node obtains, according to the backhaul BSID, a segment identifier SID list used for characterizing a backhaul path from the destination node to the source node.