CN113810288B

CN113810288B - Message backhaul method and device

Info

Publication number: CN113810288B
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: 2023-05-02
Anticipated expiration: 2041-09-17
Also published as: CN113810288A

Abstract

The embodiment of the application provides a message backhaul method and device. The scheme is as follows: receiving a request message sent by a source node; the request message includes a DOH including a backhaul BSID; locally acquiring 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; 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 path of the opposite report Wen Huicheng is improved, so that the normal operation of network service is ensured.

Description

Message backhaul method and device

Technical Field

The present disclosure relates to the field of communications, and in particular, to a method and apparatus for packet backhaul.

Background

In SRv network, for some network services, such as packet internet searcher (Packet Internet Groper, ping), seamless bidirectional forwarding detection (Seamless Bidirectional Forwarding Detection, SBFD), bidirectional active measurement protocol (Two-Way Active Measurement Protocol, twamp), and the like, after the source node sends the request message to the destination node, the destination node processes the message content of the request message to obtain a response message, and transmits the response message to the source node according to the designated backhaul path.

At present, after processing the message content of the received request message to obtain a response message, the destination node directly determines a return path of the response message according to the routing table, so as to transmit the response message to the source node. Since the backhaul path of the response message is determined according to the routing table, the determination of the backhaul path will be affected by the network topology and the route calculation method. For example, the backhaul path determined according to the routing table may be the path with the shortest transmission path in the network topology, or may be the transmission path with the lowest network overhead, so that the backhaul path determined according to the routing table deviates from the designated backhaul path, which greatly increases the uncontrollability of the backhaul path, thereby affecting the normal running of the network service.

Disclosure of Invention

An object of the embodiments of the present application is to provide a method and an apparatus for packet backhaul, so as to improve the controllability of a path of a response packet Wen Huicheng and ensure normal operation of network services. The specific technical scheme is as follows:

the embodiment of the application provides a message backhaul method, which is applied to a destination node in an internet protocol 6 th edition route (Segment Routing Internet Protocol Version, SRv 6) network, wherein the SRv network further comprises a source node, and the method comprises the following steps:

Receiving a request message sent by the source node; the request message includes a destination option header (Destination Options Header, DOH) including a backhaul binding segment identity (Binding Segment Identity, BSID);

locally acquiring a Segment Identity (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;

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

Optionally, the request message includes an internet protocol version 6 (Internet Protocol Version, IPv 6) basic header, and the DOH including the backhaul BSID is encapsulated after the IPv6 basic header; or (b)

If the request message further includes a segment routing header SRH, the DOH including the backhaul BSID is encapsulated after the SRH.

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

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

According to the corresponding relation between the prestored BSID and the Internet protocol 6 th edition segment route-traffic engineering Policy (Segment Routing Internet Protocol Version 6-Traffic Engineering Policy, SRv6-TE Policy), a target SRv6-TE Policy corresponding to the backhaul BSID is obtained from the local;

and acquiring a SID list of a backhaul path from within the target SRv6-TE Policy.

according to the corresponding relation between the prestored BSID and the candidate path, locally acquiring a target candidate path corresponding to the backhaul BSID;

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 corresponding relation between the prestored BSID and the SID list, locally acquiring a target SID list corresponding to the backhaul BSID as a SID list of a backhaul path.

The embodiment of the application also provides a message backhaul method, which is applied to a source node in a SRv6 network, wherein the SRv6 network also comprises a destination node, and the method comprises the following steps:

Generating a request message, wherein the request message comprises DOH, and the DOH comprises a backhaul BSID;

and sending the request message to the destination node so that the destination node obtains a SID list used for representing a return path of the destination node to the source node according to the return BSID.

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

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, if the request message includes an IPv6 basic header, the DOH including the backhaul BSID is encapsulated after the IPv6 basic header; or (b)

If the request message further includes an SRH, the DOH including the backhaul BSID is encapsulated after the SRH.

The embodiment of the application also provides a message backhaul device, which is applied to a destination node in a SRv6 network, wherein the SRv6 network further comprises a source node, and the device comprises:

The receiving module is used for receiving the request message sent by the source node; the request message comprises DOH, and the DOH comprises a backhaul BSID;

an acquisition module, configured to locally acquire 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;

and the first sending module is used for 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.

The embodiment of the application also provides a message backhaul device, which is applied to a source node in a SRv6 network, wherein the SRv6 network further comprises a destination node, and the device comprises:

the generating module is used for generating a request message, wherein the request message comprises DOH, and the DOH comprises a backhaul BSID;

and the second sending module is used for sending the request message to the destination node so that the destination node obtains a SID list used for representing a return path of the destination node reaching the source node according to the return BSID.

Embodiments of the present application also provide a destination node comprising 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: the message return method steps described in any one of the above are implemented.

The present embodiments also provide a source node comprising 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: the message return method steps described in any one of the above are implemented.

The present embodiments also provide a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor being caused by the machine-executable instructions to: the message return method steps described in any one of the above are implemented.

In the technical solution provided in the embodiment of the present application, after receiving a request packet sent by a source node, a destination node may locally obtain a SID list of a backhaul path corresponding to a 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.

Compared with the related art, the SID list of the backhaul path corresponding to the backhaul BSID is stored in the local storage space of the destination node, so that the destination node can obtain the SID list of the backhaul path corresponding to the response message from the local according to the backhaul BSID included in the request message after receiving the request message carrying the backhaul BSID, and then send the response message to the source node along the backhaul path. While ensuring the accuracy of the determined backhaul path, as 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 message can be set according to the user requirement, the controllability of the path of the response message Wen Huicheng is effectively improved, and the normal running of network service is ensured.

Of course, it is not necessary for any of the products or methods of the present application to be practiced with all of the advantages described above.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

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

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

fig. 3 is a schematic diagram of a backhaul BSID option field provided in an embodiment of the present application;

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

FIG. 4-b is a second schematic diagram of a header of a request message 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 an embodiment of the present application;

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

Fig. 6 is a third flow chart of a packet backhaul method according to an embodiment of the present application;

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

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

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

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

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

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

fig. 13 is a schematic diagram of a second structure of a packet backhaul apparatus 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 following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

In the related art, for network traffic such as Ping, SBFD, twamp, there is a deviation between a backhaul path specified based on a routing table and a designated backhaul path.

For ease of understanding, the SRv network shown in fig. 1 is illustrated as an example. Assume now that connectivity of an internet protocol version6 segment routing Policy (Segment Routing Internet Protocol Version6-Traffic Engineering Policy, SRv6-TE Policy) is detected using SBFD messages. The forward path specified by the request message is as follows: A-C-D-B, the backhaul path designated by the response message is B-D-C-A.

The request message sent by node a will be transmitted along the designated outbound path (i.e., a-C-D-B) to node 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 will query the routing table according to the source address in the received request message, so as to determine the backhaul path of the response message according to the outgoing interface and the next hop of the routing table, and thus 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 route calculation method will directly affect the determined backhaul path, for example, the transmission path of the path B-ase:Sub>A is shortest, the overhead is minimum, and will be directly determined as the backhaul path of the response message. At this time, the backhaul path determined according to the routing table is deviated from the designated backhaul path, which affects the normal operation of the network traffic.

In order to solve the problems in the related art, the embodiment of the application provides a message backhaul method. The method is applied to a destination node in a SRv network, and a source node is further included in the SRv6 network. As shown in fig. 2, fig. 2 is a first flowchart of a packet 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 including a backhaul BSID.

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

Step S203, a response message of the request message is sent to the source node, where 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.

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

The embodiments of the present application will be described below by way of specific examples.

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

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

In this embodiment of the present application, the request packet may be transmitted to the destination node according to a forward path determined by the routing table. The request message can also be forwarded to the destination node according to the SID list.

In an alternative embodiment, when the request packet is transmitted to the destination node according to the outgoing path determined by the routing table, the header of the request packet includes an internet protocol version 6 (Internet Protocol Version, ipv 6) basic header and the DOH.

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

In the embodiment of the present application, the DOH in the header of the request packet includes a backhaul BSID option field (may also be referred to as Reverse BSID Option), where the backhaul BSID is stored in the backhaul BSID option field.

For ease of understanding, fig. 3 is an illustration of backhaul BSID option fields provided in an embodiment of the present application.

The backhaul BSID Option field shown in fig. 3 includes an Option Type (Option Type), an Option Data length (Opt Data Len), and a backhaul BSID (Reverse BSID). Wherein, if the option type needs standardization, the option type can be distributed by an Internet digital distribution organization (The Internet Assigned Numbers Authority, IANA); if normalization is not required, then an unoccupied value in the current IPv6 protocol standard may be selected, for example, a binary number: 00011101, etc. The option data length may be a preset value, such as 16. Here, the option type and the option data length of the fields 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 multiple manners, and encapsulate the backhaul BSID into the DOH of the header of the request message.

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

In another alternative embodiment, when acquiring the backhaul BSID, 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 the embodiment of the present application, the method for acquiring the backhaul SID carried in the request packet is not specifically limited.

In an alternative 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 according to an embodiment of the present application. The backhaul BSID option field of the DOH shown in fig. 4-a includes the backhaul BSID described above.

In another alternative embodiment, when the header of the request message includes SRH, that is, the header of the request message includes IPv6 base header, SRH, and DOH, the DOH including backhaul BSID is encapsulated after SRH. The number of DOH may be one or two. Particularly as shown in fig. 4-b and 4-c. FIG. 4-b is a second schematic diagram of a header of a request message 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 an embodiment of the present application. The backhaul BSID option fields of the DOHs shown in fig. 4-b and 4-c include the backhaul BSID described above.

In the related art, when the header of the message includes the IPv6 basic header, the SRH and the DOH, the DOH may be encapsulated before the SRH, or the DOH may be encapsulated after the SRH. For ease of understanding, this is described in connection with 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, denoted as the 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, denoted as the second DOH).

In the header shown in fig. 4-c, the first DOH is encapsulated before the 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) except the destination node receives the request message, the end node will preferably process the fields included in the first DOH because the first DOH is encapsulated before the SRH, and then forward 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 options 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. I.e., 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 except for the destination node on the outbound path can be enabled to perform forwarding processing preferentially on the received request message, and the DOH including the backhaul BSID in the request message is not processed, so that only the destination node is guaranteed to process the DOH including the backhaul BSID in the request message, and guarantee is provided for normal operation of network services.

The request message may be a message corresponding to network services such as Ping service, SBFD service, twamp service, etc. The message content of the request message is different according to different network services. Here, the request message is not particularly limited.

For the step S202, a SID list of the backhaul path corresponding to the backhaul BSID is locally acquired; the backhaul path is a path from the destination node to the source node.

In this embodiment of the present application, the corresponding relationship between the BSID and the transmission path is stored in the destination node in advance. After receiving the request message, the destination node can search whether a transmission path corresponding to the backhaul BSID in the request message exists according to the pre-stored corresponding relation. 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 message of the request message. At this time, the destination node may acquire the SID list of the backhaul path from the local. I.e., a SID list of transmission paths corresponding to the backhaul BSID is acquired. Wherein the local is the destination node.

For the step S203, a response message of the request message is sent to the source node, where 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.

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, so as to obtain the response content corresponding to the request message. At this time, the destination node may construct a response message according to the SID list and the response content obtained in step S202, and send the response message to the source node.

Because the message content of the request message corresponding to different network services is different, the processing mode adopted by the destination node when processing the message content of the request message of different network services is also different. The processing manner of the message content of the request message is not particularly limited.

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

And after the end node on the return path receives the response message sent by the destination node, forwarding the received response message according to the SID list in the response message, thereby forwarding the response message to the source node along the return path.

In an alternative embodiment, according to the method shown in fig. 2, the embodiment of the application further provides a message backhaul method. As shown in fig. 5, fig. 5 is a second flowchart of a packet backhaul method according to an 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.

In step S502, the target SRv-TE Policy corresponding to the backhaul BSID is obtained locally according to the corresponding relation between the pre-stored BSID and SRv-TE Policy.

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

After the destination node reads the backhaul BSID from the backhaul BSID option field of the DOH of the request message, it can search whether the target SRv-TE Policy corresponding to the backhaul BSID exists according to the corresponding relationship between the prestored BSID and the SRv-TE Policy. After finding the target SRv6-TE Policy, the destination node may obtain the target SRv-TE Policy locally.

In the embodiment of the present application, the correspondence between BSID and SRv6-TE Policy may be expressed in various forms. For example, the correspondence between BSID and SRv6-TE Policy can be expressed as: correspondence between BSID and SRv6-TE Policy identification information. The SRv-TE Policy identification information can be composed of numbers, letters and other information, and can also be represented by SRv-TE Policy triples. Here, the expression of the correspondence between BSID and SRv6-TE Policy is not particularly limited.

The SRv-TE Policy described above may be composed of BSID and a plurality of 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 is made up 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 (IPv 6 addresses) of all nodes on a forwarding path.

In step S503, a SID list of the backhaul path is acquired from within the target SRv-TE Policy.

In this embodiment of the present application, after the destination node finds the target SRv6-TE Policy, the destination node may select the candidate path with the highest priority in the target SRv-TE Policy as the target candidate path. When the target candidate path consists of a list of SIDs, the destination node may determine the list of SIDs as a list of target SIDs. At this time, the destination node acquires the target SID list from within the locally stored target SRv-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 acquires the target SID list from within the locally stored target SRv-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 paths is used for load sharing.

For ease of understanding, the list of SIDs included in the candidate path is exemplified by list 1 and list 2. Wherein the weight of the list 1 is 2, and the weight of the 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 of list 2 being determined as the target SID list is 8/(2+8) =0.8, i.e., the probability of the forwarding path identified by list 2 being determined as the 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 the response messages corresponding to 20% of the request messages are: the forwarding paths identified in the list 1, and the backhaul paths of response messages corresponding to 80% of request messages are as follows: forwarding paths identified by list 2.

In the embodiment of the present application, when the target candidate path is formed by a plurality of SID lists, any SID list in the target candidate path may be determined as a target SID list, that is, a SID list of a backhaul path corresponding to the backhaul BSID, under the condition that a probability that a forwarding path identified by each SID list is selected as a backhaul path is guaranteed to match a weight corresponding to each SID list.

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

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

Step S504, a response message of the request message is sent to the source node, 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.

Step S504 is the same as step S203.

In another alternative embodiment, according to the method shown in fig. 2, the embodiment of the present application further provides a packet backhaul method. As shown in fig. 6, fig. 6 is a third flowchart of a packet 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 including a backhaul BSID.

Step S601 is the same as step S201.

In step S602, a target candidate path corresponding to the backhaul BSID is obtained locally according to the correspondence between the pre-stored BSID and the candidate path.

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

After the destination node reads the backhaul BSID from the backhaul BSID option field of the DOH of the request message, it can find whether there is a target candidate path corresponding to the backhaul BSID according to the corresponding relationship between the pre-stored BSID and the candidate path. When the target candidate path is found, the destination node may acquire the target candidate path locally.

Step S603, a SID list of the backhaul path is acquired from the target candidate paths.

In an alternative embodiment, when the target candidate path is composed of a SID list, the destination node may determine the SID list as a target SID list, that is, a SID list of the backhaul path corresponding to the backhaul BSID. And determining the forwarding path identified by the SID list as a return path of a response message corresponding to the request message.

In another optional 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 the weight corresponding to each SID list. The specific reference may be made to the above description of step S503, and the details are not repeated here.

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

Step S604, a response message of the request message is sent 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.

Step S604 is the same as step S203.

In yet another alternative embodiment, according to the method shown in fig. 2, the embodiment of the present application further provides a packet backhaul method. As shown in fig. 7, fig. 7 is a fourth flowchart of a packet 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 including a backhaul BSID.

Step S701 is the same as step S201.

Step S702, according to the pre-stored correspondence between BSID and SID list, obtains the target SID list corresponding to the backhaul BSID from the local area as the SID list of the backhaul path.

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

After the destination node reads the backhaul BSID from the backhaul BSID options of the DOH of the request message, it can search whether there is a target SID list corresponding to the BSID according to the corresponding relationship between the pre-stored BSID and the SID list. Upon finding the target SID list, the destination node may determine the target SID list as a SID list of the backhaul path corresponding to the backhaul BSID. And determining the forwarding path identified by the target SID list as a return path of a response message corresponding to the request message.

The step S702 is a refinement of the step S202.

Step S703, sending a response message of the request message to the source node, where 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 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. Namely, the correspondence between BSID and SRv-TE Policy in the embodiment shown in fig. 5, the correspondence between BSID and candidate paths 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 of the determined backhaul path is achieved, flexibility of the corresponding relation between the BSID and the transmission path is improved, controllability of the determined backhaul path is improved, and accordingly normal operation of network service is guaranteed.

In an alternative embodiment, according to the method shown in fig. 2, the embodiment of the application further provides a message backhaul method. As shown in fig. 8, fig. 8 is a fifth flowchart of a packet 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 including a backhaul BSID.

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

Step S803, a response message of the request message is sent to the source node, where 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.

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

Step S804, discard the request message.

In the embodiment of the present application, due to the influence of factors such as the network environment of the SRv network, 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 performs the above step S802, the SID list of the backhaul path corresponding to the backhaul BSID (i.e., the wrong backhaul BSID) cannot be acquired based on the correspondence between the pre-stored BSID and the transmission path. When the destination node locally acquires the SID list of the backhaul path corresponding to the backhaul BSID, the destination node will perform step S803 described above. When the destination node does not locally acquire the SID list of the backhaul path corresponding to the backhaul BSID, the destination node will perform step S804 described above.

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 the response message. In addition, after receiving the request message, the target node may analyze and process the request message to obtain a response message, and then acquire the SID list of the backhaul path corresponding to the backhaul BSID.

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 in addition to discarding the request packet.

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

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 (Internet Control Message Protocol, ICMP) message to the source node. The ICMP message may include the backhaul BSID in the request message. The source node may determine a backhaul BSID error after receiving the ICMP message.

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

In another alternative 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, based on the backhaul path, a response packet corresponding to the request packet to the source node.

Based on the same inventive concept, according to the message backhaul method provided by 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 of a packet backhaul method according to an embodiment of the present application. The method is applied to a source node in a SRv6 network, and a destination node is also included in the SRv6 network. The method comprises the following steps.

In step S901, a request message is generated, where the request message 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 time, the DOH including the backhaul BSID is encapsulated after the IPv6 basic header.

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

The DOH includes a backhaul BSID option field, where a backhaul BSID is stored. The backhaul BSID may be configured by the user for the request message. Or may be sent to the source node by BGP-LS protocol for the destination node. The method for obtaining the backhaul BSID in the backhaul BSID option of the DOH may be referred to the above description, and will not be described herein.

Step S902, a request message is sent to the destination node, so that the destination node obtains a SID list used for representing a backhaul path of the destination node reaching the source node according to the backhaul BSID.

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

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

In this embodiment of the present application, since the DOH of the request packet includes a 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.

By the method shown in fig. 9, the source node sends the request message carrying the backhaul BSID to the destination node, so that the destination node can obtain the SID list of the backhaul path corresponding to the backhaul BSID from the local according to the corresponding relation between the prestored BSID and the transmission path after receiving the request message, thereby sending the response message including the SID list to the source node, and sending the response message to the source node along the forwarding path identified by the SID list.

Compared with the related art, the method and the device have the advantages that the accuracy of the determined backhaul path is ensured, and meanwhile, as 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 requirements, namely, the backhaul path of the response message can be set according to the user requirements, the controllability of the path of the response message Wen Huicheng is effectively improved, and therefore normal operation of network services is ensured.

In an alternative embodiment, according to the method shown in fig. 9, the embodiment of the application further provides a packet backhaul method. Fig. 10 is a schematic diagram of a seventh flow chart of a packet backhaul method according to an embodiment of the present application, as shown in fig. 10. The method comprises the following steps.

In step S1001, a request message is generated, where 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 a SID list for characterizing the backhaul path of the destination node to the source node according to the backhaul BSID.

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

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

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

The preset duration may be determined according to a transmission distance between the source node and the destination node, and a processing duration of the request message by the destination node, where the preset duration is not specifically limited.

In the embodiment of the application, the source node can accurately determine the response message sent through the appointed return path through the SID list carried in the received response message, thereby ensuring the accuracy of network service based on the SRv network.

In an alternative embodiment, the source node may receive the response message that does not carry the SID list within a preset time period after sending the request message 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 message of the request message to the source node according to the routing table. The source receives the response message, and the response message does not include the SID list of the backhaul path corresponding to the backhaul BSID.

For another example, when the target node obtains the SID list of the backhaul path corresponding to the backhaul BSID, the target node sends a response message of the request message according to the backhaul path identified by the SID list. In order to relieve the burden of the source node, the response message sent by the destination node includes SID attachment behaviors (flives), and the SID attachment behaviors are: PSP (Penultimate Segment POP of the SRH). PSP represents the next to last Endpoint node on the backhaul path (i.e., the previous Endpoint of the source node) performing the SRH removal operation. At this time, the SID list of the backhaul path corresponding to the backhaul BSID will not be included in the response message received by the source node.

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 duration after sending the request message to the destination node. The notification message may include the backhaul BSID described above.

When the destination node does not obtain the SID list of the backhaul path corresponding to the backhaul BSID locally, it may determine that an error occurs in the BSID included in the request message. 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 SRv network shown in fig. 11, node a has deployed thereon SRv-TE Policy a, specifically SRv-6-TE Policy a, for transmission of packets along path 11 to node B: bsid=1:1, path= < C, D, B >. Node B has deployed thereon a SRv6-TE Policy B, specifically SRv6-TE Policy B, for transmission of messages along path 12 to node a: bsid=2:2, path= < D, C, a >.

After generating the message A to be sent to the node B, the node A can construct a request message according to the deployed SRv6-TE Policy A and the BSID in SRv6-TE Policy B. That is, node a may encapsulate the SID list corresponding to the transmission Path in SRv6-TE Policy a, i.e., path= < C, D, B > into the SRH of the header of the message a, and encapsulate the BSID in SRv6-TE Policy B, i.e., 2:2, into the DOH of the header of the message a to obtain the request message, where the header of the request message is shown as header 21 in fig. 11.

Node a sends a request message to node B via path 11 in fig. 11. After receiving the request message, the node B may obtain, from the local, a SID list of the backhaul Path corresponding to the backhaul BSID according to the backhaul BSID included in the request message, that is, obtain, from the local, path= < D, C, a > in SRv-TE Policy B. The node B encapsulates the SID list into a response message corresponding to the request message, where the header of the response message is shown as header 22 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 a 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 by 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 diagram of a first structure of a packet backhaul device according to an embodiment of the present application. The device comprises the following modules.

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

an acquisition module 1202, configured to locally acquire 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;

The first sending module 1203 is configured to send 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 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, the DOH including the backhaul BSID is encapsulated after the SRH.

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

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

Optionally, the acquiring module 1202 may be specifically configured to acquire, from the local area, a target candidate path corresponding to the backhaul BSID according to a pre-stored correspondence between BSIDs and candidate paths; and acquiring a SID list of the backhaul path from the target candidate path.

Optionally, the acquiring module 1202 may specifically be configured to acquire, from the local area, a target SID list corresponding to the backhaul BSID according to a pre-stored correspondence between the BSID and the SID list, as the SID list of the backhaul path.

Based on the same inventive concept, according to the message backhaul method provided by 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. Fig. 13 is a schematic diagram of a second structure of a packet backhaul device according to an embodiment of the present application, as shown in fig. 13. The device comprises 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 the destination node, so that the destination node obtains, according to the backhaul BSID, a SID list for characterizing a backhaul path of the destination node to reach the source node.

Optionally, the message backhaul device may further include:

and the determining module is used for determining that the destination node transmits the response message through the backhaul path when receiving the response message of the request message transmitted by the destination node after transmitting the request message to the destination node and the response message comprises the SID list.

By the device provided by the embodiment of the application, after receiving the request message sent by the source node, the destination node can obtain the SID list of the backhaul path corresponding to the backhaul BSID from the local because the DOH of the request message comprises the backhaul BSID, so as to send the response message carrying the SID list to the source node.

Based on the same inventive concept, according to the message backhaul method provided in the above embodiment of the present application, the 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 capable of being 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 alternative embodiment, as shown in fig. 14, the destination node may further include: a communication interface 1403 and a communication bus 1404; wherein the processor 1401, the machine-readable storage medium 1402 and the communication interface 1403 perform communication with each other through a communication bus 1404, the communication interface 1403 is used for communication between the destination node and other devices.

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

In an alternative 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 perform communication with each other through the communication bus 1504, where 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 above embodiments of the present application, the embodiments of the present application further provide a machine-readable storage medium, where machine-executable instructions capable of being executed by a processor are stored in the machine-readable storage medium. The processor is caused by the machine-executable instructions to perform any of the steps shown in fig. 2, 5-10 described above.

The communication bus may be a PCI (Peripheral Component Interconnect, peripheral component interconnect standard) bus, or an EISA (Extended Industry Standard Architecture ) bus, or the like. The communication bus may be classified as an address bus, a data bus, a control bus, or the like.

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

The processor may be a general-purpose processor, including a CPU (Central Processing Unit ), NP (Network Processor, network processor), etc.; but also DSP (Digital Signal Processing, digital signal processor), ASIC (Application Specific Integrated Circuit ), FPGA (Field-Programmable Gate Array, field programmable gate array) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components.

It is noted that relational terms such as first and second, and the like are 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. Moreover, 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 one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

In this specification, each embodiment is described in a related manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for the embodiments of the message backhaul device, the destination node, the source node, and the machine-readable storage medium, the description is relatively simple, and the relevant points are referred to in the description of the embodiments of the message backhaul method, because they are basically similar to the embodiments of the message backhaul method.

The foregoing description is only of the preferred embodiments of the present application and is not intended to limit the scope of the present application. Any modifications, equivalent substitutions, improvements, etc. that are within the spirit and principles of the present application are intended to be included within the scope of the present application.

Claims

1. A method for packet backhaul, applied to a destination node in a SRv network, where the SRv network further includes a source node, the method comprising:

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

locally acquiring a segment identification 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;

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 (b)

3. The method of claim 1, wherein 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 acquiring the SID list of the backhaul path corresponding to the backhaul BSID specifically comprises:

according to the corresponding relation between the prestored BSID and SRv6-TE Policy, the target SRv6-TE Policy corresponding to the backhaul BSID is obtained from the local;

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

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 specifically comprises:

7. A method for packet backhaul, applied to a source node in a SRv network, where the SRv network further includes a destination node, the method comprising:

generating a request message, wherein the request message comprises a destination option header DOH, and the DOH comprises a backhaul binding segment identifier BSID;

sending the request message to the destination node, so that the destination node obtains a segment identification SID list used for representing a backhaul path of the destination node to the source node according to the backhaul BSID;

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

8. 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 (b)

9. The method of claim 7, wherein the DOH includes a backhaul BSID option field in which the backhaul BSID is stored.

10. A packet backhaul device, applied to a destination node in a SRv network, the SRv network further including a source node, the device comprising:

the receiving module is used for receiving the request message sent by the source node; the request message comprises a destination option header DOH, wherein the DOH comprises a backhaul binding segment identifier BSID;

an acquisition module, configured to locally acquire a segment identification 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;

11. A packet backhaul device, applied to a source node in a SRv network, the SRv network further including a destination node, the device comprising:

the generating module is used for generating a request message, wherein the request message comprises a destination option header DOH, and the DOH comprises 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 identification SID list for characterizing a backhaul path of the destination node to the source node;

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