Method and device for forwarding traffic

Abstract

The embodiment of the invention discloses a method for forwarding traffic, and the method comprises the steps: a first site edge can receive a first service message, and packages the path information of a first end-to-end path at the outer layer of the first service message, so as to obtain a second service message; the incoming endpoint of the first end-to-end path is a first station edge, the outgoing endpoint of the first end-to-end path is a second station edge, and the path information of the first end-to-end path comprises first information for identifying a first backbone network entrance device in the backbone network and second information for identifying a first backbone network exit device in the backbone network. The first site edge is accessed to the backbone network through the first backbone network entrance device, and the second site edge is accessed to the backbone network through the first backbone network exit device. And after the first site edge obtains the second service message, the second service message can be forwarded through the first end-to-end path. By using the scheme, the backbone network does not need to perceive the service, and the forwarding efficiency of the service flow can be effectively improved.

Description

[0001] This application claims the priority of the Chinese patent application filed with the China Patent Office on June 16, 2023, with application number 202310725238.X and invention name “A message forwarding method and device”, the entire contents of which are incorporated by reference in this application. Technical Field

[0002] The present application relates to the field of communications, and in particular to a method and device for forwarding traffic. Background Art

[0003] Business traffic can be transmitted across the backbone network. For example, in scenarios such as enterprises entering multiple clouds, enterprise branch interconnection, and user access to related services, business traffic needs to be transmitted across edge access networks and backbone networks.

[0004] At present, in the scenario where the service traffic needs to be transmitted across the backbone network, it is necessary to perform service-related configuration in the backbone network. Accordingly, in the forwarding stage of the service traffic, the network devices in the backbone network can forward the service traffic in combination with the above configuration. For example, in the service activation stage, it is necessary to perform virtual private network (VPN) configuration on the network devices in the backbone network. Accordingly, in the forwarding stage of the service traffic, the network devices in the backbone network forward the traffic in combination with the VPN configuration.

[0005] However, with this method, the forwarding efficiency of business traffic is low. Therefore, a solution is urgently needed to solve the above problem. Summary of the invention

[0006] The embodiments of the present application provide a method and device for forwarding traffic, which can improve the forwarding efficiency of business traffic.

[0007] In the first aspect, an embodiment of the present application provides a method for forwarding traffic, which can be applied to a first site edge. The first site edge can receive a first service message. After the first site edge receives the first service message, the path information of the first end-to-end path can be encapsulated in the outer layer of the first service message to obtain a second service message. The inbound end point of the first end-to-end path is the first site edge, and the outbound end point of the first end-to-end path is the second site edge. The path information of the first end-to-end path includes: first information identifying a first backbone network ingress device in the backbone network, and second information identifying a first backbone network egress device in the backbone network. The first site edge accesses the backbone network through the first backbone network ingress device, and the second site edge accesses the backbone network through the first backbone network egress device. After the first site edge obtains the second service message, the second service message can be forwarded through the first end-to-end path. It can be seen that, using this solution, the first end-to-end path across the backbone network can be arranged by the site edge, without the need for the equipment in the backbone network to determine the transmission path based on the service configuration, so that the backbone network does not need to perceive the service, thereby improving the forwarding efficiency of the service traffic. Moreover, since the backbone network does not need to be aware of the service, there is no need to perform service-related configuration on the equipment in the backbone network, thereby improving the efficiency of service activation and, correspondingly, the scalability of the backbone network.

[0008] In a possible implementation, the first end-to-end path may be pre-arranged by the first site edge. In a specific example, the first site edge may arrange the first end-to-end path before receiving the first service message. In a specific example, the first service message is used to carry a virtual private network (VPN) service. For this, the first site edge may arrange the first end-to-end path from the first site edge to the second site edge in combination with the first backbone network entry device and the first backbone network exit device as needed according to the VPN service. As an example, the first site edge may arrange an end-to-end path for the VPN route after receiving the VPN route including the destination prefix announced by the second site edge. In a specific example, the first site edge may arrange the first end-to-end path for the VPN route based on the binding relationship between the first site edge and the first backbone network entry device, and the binding relationship between the second site edge and the first backbone network exit device.

[0009] In one possible implementation, the second service message may further include service intent information. Thus, after the first site edge sends the second service message, the forwarding device that receives the second service message may select a corresponding path for forwarding based on the service intent information when further forwarding the second service message, thereby satisfying the service intent and, accordingly, improving the service quality provided to the service.

[0010] In a possible implementation, the second service message may include a metadata field, and the service intent information is carried in the metadata field. The forwarding device that receives the second service message may parse the metadata field to obtain the service intent information, so as to further select a corresponding path for forwarding in combination with the service intent information, so that the service intent is met and, accordingly, the service quality provided for the service is improved.

[0011] In a possible implementation, the first site edge may first determine the path information of the first end-to-end path before encapsulating the first service message using the path information of the first end-to-end path. In a specific example, the first site edge may determine that the next hop for forwarding the first service message is the second site edge based on the destination address of the first service message, and further iterate the first segment routing policy (segment routing policy, SR policy) based on the Internet Protocol (IP) address of the second site edge to obtain the path information of the first end-to-end path.

[0012] In one possible implementation, the first SR policy may be a Segment Routing Internet Protocol Version 6 (SRv6) policy. For this case: the first end-to-end path may be an SRv6 tunnel, and accordingly, the second service message includes an IPv6 header and a segment routing header (SRH), and the aforementioned first information and second information may be carried by the SRH. Moreover, the destination address of the IPv6 header points to the first backbone network ingress device, so that the first site edge forwards the second service message to the first backbone network ingress device based on the destination address of the IPv6 header.

[0013] In a possible implementation, when the first SR policy is an SRv6 policy, the first information may be a first end segment identifier (END.SID) 1 of the first backbone network entry device, and the second information may be a second end segment identifier END.SID2 of the first backbone network exit device. In addition, the SRH also includes an IPv6 address of the second site edge. In this case, the SRH may indicate a path from the first backbone network entry device to the second site edge.

[0014] In a possible implementation, when the first SR policy is an SRv6 policy, the first information is END.SID1 of the first backbone network ingress device, and the second information is an endpoint segment identifier (END.X SID) with a cross connection to a layer 3 adjacency array allocated by the first backbone network device egress device for the adjacency between the first backbone network device egress device and the second site edge. In this case, the SRH may also indicate a path from the first backbone network ingress device to the second site edge.

[0015] In a possible implementation, the END.SID1 can be used to indicate a new message forwarding operation. In this case, the first backbone network ingress device can determine how to forward the second service message based on END.SID1 without combining VPN information to determine how to forward the second service message.

[0016] In a specific example, the operation associated with END.SID1 may be: matching the overly SRv6 Policy from the first backbone network ingress device to the first backbone network egress device according to the next hop SID of END.SID1 in the SRH. In another specific example, when the second service message includes service intent information, the operation associated with END.SID1 may be: matching the overlySRv6 policy from the first backbone network ingress device to the first backbone network egress device according to the next hop SID of END.SID1 in the SRH and the service intent information.

[0017] In one possible implementation, the aforementioned first SR policy may be an MPLS segment routing traffic engineering (SR-TE) policy. For this case, the first end-to-end path is an MPLS SR-TE policy. Accordingly, the second service message includes an MPLS label stack, and the aforementioned first information and second information are carried by the MPLS label stack. For this case, the first information is the first node SID of the first backbone network ingress device, and the second information includes: the second node SID of the first backbone network egress device, and the adjacency segment identifier (adjacency SID, adj-SID) assigned by the first backbone network device egress device to the adjacency relationship between the first backbone network device egress device and the second site edge.

[0018] In a possible implementation, the first node SID can be used to indicate a new message forwarding operation. In this case, the first backbone network ingress device can determine how to forward the second service message based on the first node SID without combining VPN information to determine how to forward the second service message.

[0019] In a specific example, the operation of associating the first node SID may be: matching the upper layer (overly) SR-MPLS TE policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the first node SID in the MPLS label stack. In another specific example, when the second service message includes service intent information, the operation of associating the first node SID may be: matching the upper layer overly SR-MPLS TE policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the first node SID in the MPLS label stack and the service intent information.

[0020] In one possible implementation, the first end-to-end path is a tunnel encapsulated based on the generic network virtualization encapsulation (GENEVE) protocol. In this case, the first site edge can use GENEVE encapsulation when encapsulating the path information of the first end-to-end path in the outer layer of the first service message. In other words, the second service message uses GENEVE encapsulation. When the first end-to-end path is an SRv6 tunnel, the second service message can use SRv6 in GENEVE encapsulation. When the first end-to-end path is MPLS SR-TEpolicy, the second service message can use MPLS in GENEVE encapsulation.

[0021] In one possible implementation, the first end-to-end path is a tunnel encapsulated based on the generic routing encapsulation (GRE) protocol. In this case, the first site edge can use GRE encapsulation when encapsulating the path information of the first end-to-end path in the outer layer of the first service message. In other words, the second service message is encapsulated using GRE. When the first end-to-end path is an SRv6 tunnel, the second service message can be encapsulated using SRv6 over GRE. When the first end-to-end path is an MPLS SR-TE policy, the second service message can be encapsulated using MPLS over GRE.

[0022] In a possible implementation, if the second service message is encapsulated using SRv6 over GRE, the second service message includes: an outer IP header, a User Datagram Protocol (UDP) header, an outer GRE encapsulation, an IPv6 header, an SRH, an inner GRE encapsulation, and a payload, wherein the payload includes the first service message, and the inner GRE encapsulation includes a VPN identifier (VPN identifier, VNI) of the VPN service carried by the first service message. The VPN identifier is carried in the inner GRE encapsulation, and when the second service message is transmitted in the backbone network, the device in the backbone network does not parse the VPN identifier, that is, the backbone network does not perceive the VPN.

[0023] In a possible implementation, the first site edge edge can also receive a third service message, and encapsulate the path information of the second end-to-end path in the outer layer of the third service message to obtain a fourth service message; wherein the path information of the second end-to-end path includes third information identifying the second backbone network entry device in the backbone network and fourth information identifying the second backbone network exit device in the backbone network, the entry point of the second end-to-end path is the first site edge, the exit point of the second end-to-end path is the second site edge, the second end-to-end path passes through the second backbone network entry device and the second backbone network exit device, the first site edge is multi-homed to access the first backbone network entry device and the second backbone network entry device, the second site edge is multi-homed to access the first backbone network exit device and the second backbone network exit device; the first site edge sends the fourth service message through the second end-to-end path. It can be seen that, using this solution, the site edge can arrange the second end-to-end path across the backbone network, without the need for the equipment in the backbone network to determine the transmission path based on the service configuration, so that the backbone network does not need to perceive the service, thereby improving the forwarding efficiency of the service traffic. Moreover, since the backbone network does not need to be aware of the service, there is no need to perform service-related configuration on the equipment in the backbone network, thereby improving the efficiency of service activation and, correspondingly, the scalability of the backbone network.

[0024] In one possible implementation, the first site edge accesses the first backbone network entry device via a software-defined wide area network (SD-WAN) tunnel or the Internet.

[0025] In the second aspect, an embodiment of the present application provides a method for forwarding traffic, which can be applied to a first backbone network entry device in a backbone network. The first backbone network device can receive a second service message from a first site edge, and the payload of the second service message includes a first service message. The outer layer of the first service message encapsulates the path information of the end-to-end path between the first site edge and the second site edge; wherein the path information of the end-to-end path includes: first information identifying the first backbone network entry device, and second information identifying the first backbone network exit device in the backbone network, the entry point of the end-to-end path is the first site edge, the exit point of the end-to-end path is the second site edge, the end-to-end path passes through the first backbone network entry device and the first backbone network exit device, the first site edge accesses the backbone network through the first backbone network entry device, and the second site edge accesses the backbone network through the first backbone network exit device. After the first backbone network entry device receives the second service message, it can process the second service message according to the first information to obtain a third service message, and send the third service message to the first backbone network exit device to forward the service traffic. It can be seen that, using this solution, the first end-to-end path for transmitting the service is determined by the first site edge, and the second service message received by the first backbone network entry device includes the path information of the first end-to-end path. The first backbone network entry device does not need to determine the transmission path based on the service configuration, so that the backbone network does not need to perceive the service, thereby improving the forwarding efficiency of the service traffic. Moreover, since the backbone network does not need to perceive the service, there is no need to perform service-related configuration on the equipment in the backbone network, thereby improving the efficiency of service activation, and correspondingly, also improving the scalability of the backbone network.

[0026] In a possible implementation manner, the second service message also includes service intention information.

[0027] In a possible implementation, the service intention information is carried in a metadata field of the second service message.

[0028] In a possible implementation, the end-to-end path is an SRv6 tunnel, the second service message includes an IPv6 header and a segment routing header SRH, the destination address of the IPv6 header points to the first backbone network ingress device, and the SRH includes the first information and the second information.

[0029] In a possible implementation, the first information is a first endpoint segment identifier END.SID1 allocated by the first backbone network ingress device, the second information is a second endpoint segment identifier END.SID2 allocated by the first backbone network egress device, and the SRH also includes an IPv6 address of the second site edge.

[0030] In a possible implementation, the first information is the first endpoint segment identifier END.SID1 of the first backbone network ingress device, and the second information is the endpoint segment identifier END.X SID with a cross connection to a Layer 3 adjacency relationship array allocated by the first backbone network device egress device for the adjacency relationship between the first backbone network device egress device and the second site edge.

[0031] In a possible implementation, the operation of associating the first endpoint segment identifier END.SID1 includes: matching an upper layer overly SRv6 policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the END.SID1 in the SRH.

[0032] In one possible implementation, when the second service message includes service intent information, the operation associated with the first endpoint segment identifier END.SID1 includes: matching the upper layer overly SRv6 policy from the first backbone network ingress device to the first backbone network egress device according to the next hop SID of the END.SID1 in the SRH and the service intent information.

[0033] In a possible implementation, when the first information is END.SID1, the first backbone network entry device 1 processes the second service message according to the first information. In a specific implementation, the first overly SRv6 policy from the first backbone network entry device to the first backbone network exit device can be matched according to the next hop SID of END.SID1 in the SRH, and the second service message is encapsulated using the first overly SRv6policy to obtain the third service message. Specifically, the first backbone network entry device can insert a new SRH based on the second service message, and the new SRH carries the path information of the first overly SRv6policy.

[0034] In a possible implementation, when the first information is END.SID1, if the second service message includes service intent information, the first backbone network entry device 1 processes the second service message according to the first information. In a specific implementation, the second overly SRv6 policy from the first backbone network entry device to the first backbone network exit device can be matched according to the next hop SID of END.SID1 in the SRH and the service intent information, and the second service message is encapsulated using the second overly SRv6 Policy to obtain the third service message. Specifically, the first backbone network entry device can insert a new SRH based on the second service message, and the new SRH carries the path information of the second overly SRv6 policy. In addition, the first backbone network entry device can also strip the service intent information in the second service message to obtain the third service message.

[0035] In one possible implementation, the end-to-end path is an SR-MPLS TE policy, the second service message includes an MPLS label stack, the MPLS label stack includes the first information and the second information, the first information is the first node SID of the first backbone network ingress device, and the second information includes: the second node SID of the first backbone network egress device, and the adjacency segment identifier adj-SID assigned by the first backbone network device egress device to the adjacency relationship between the first backbone network device egress device and the second site edge.

[0036] In a possible implementation, the operation of associating the first node SID includes: matching an upper layer overly SR-MPLS TE policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the first node SID in the label stack.

[0037] In one possible implementation, when the second service message includes service intent information, the operation of associating the first node SID includes: matching the upper layer overlySR-MPLS TEpolicy from the first backbone network ingress device to the first backbone network egress device according to the next hop SID of the first node SID in the label stack and the service intent information.

[0038] In one possible implementation, when the first information is the first node SID, the first backbone network entry device 1 processes the second service message according to the first information. In a specific implementation, the first overly SR-MPLS TE policy from the first backbone network entry device to the first backbone network exit device can be matched according to the next-hop SID of the first node SID in the MPLS label stack. And the first overly SR-MPLS TE policy is further used to encapsulate the second service message to obtain the third service message. For example, the first backbone network entry device can replace SID1 and SID2 in the MPLS label stack with the first overly SR-MPLS TE policy to obtain the third service message.

[0039] In a possible implementation, when the first information is the first node SID, if the second service message includes service intent information, the first backbone network entry device 1 processes the second service message according to the first information. In a specific implementation, the second overlySR-MPLS TE policy from the first backbone network entry device to the first backbone network exit device can be matched according to the next hop SID of the first node SID in the MPLS label stack and the service intent information, and the second service message is encapsulated using the second overly SR-MPLS TE policy to obtain the third service message. For example, the first backbone network entry device can replace SID1 and SID2 in the MPLS label stack with the second overly SR-MPLS TE policy to obtain the third service message.

[0040] In a possible implementation, the end-to-end path is a tunnel encapsulated based on the general network virtualization encapsulation GENEVE protocol, and the second service message is encapsulated using SRv6 in GENEVE.

[0041] In a possible implementation, the end-to-end path is a tunnel encapsulated based on the Generic Routing Encapsulation (GRE) protocol, and the second service message includes SRv6 over GRE encapsulation.

[0042] In one possible implementation, the second service message includes: an outer IP header, a User Datagram Protocol UDP header, an outer GRE encapsulation, an IPv6 header, an SRH, an inner GRE encapsulation and a payload, the payload includes the first service message, and the inner GRE encapsulation includes a VPN identifier of the VPN service carried by the first service message.

[0043] In one possible implementation, the first site edge accesses the first backbone network entry device through a software-defined wide area network SD-WAN tunnel or the Internet.

[0044] In a third aspect, an embodiment of the present application provides a device for forwarding traffic, which may include a transceiver unit and a processing unit; the transceiver unit is used to perform the receiving and / or sending operations performed by the first site edge as described in the first aspect above; the processing unit is used to perform operations other than the receiving and / or sending operations performed by the first site edge as described in the first aspect above.

[0045] In a specific example, the device includes: a receiving unit, a processing unit, and a sending unit. The receiving unit is used to receive a first service message; the processing unit is used to encapsulate the path information of the first end-to-end path in the outer layer of the first service message to obtain a second service message; wherein the path information of the first end-to-end path includes first information identifying a first backbone network entry device in the backbone network and second information identifying a first backbone network exit device in the backbone network, the entry point of the first end-to-end path is the first site edge, the exit point of the first end-to-end path is the second site edge, the first end-to-end path passes through the first backbone network entry device and the first backbone network exit device, the first site edge accesses the backbone network through the first backbone network entry device, and the second site edge accesses the backbone network through the first backbone network exit device; the sending unit is used to send the second service message through the first end-to-end path.

[0046] In one possible implementation, the first service message is used to carry a virtual private network VPN service, and the processing unit is further used to: before receiving the first service message, according to the VPN service, combine the first backbone network ingress device and the first backbone network egress device as needed to orchestrate the first end-to-end path from the first site edge to the second site edge.

[0047] In a possible implementation manner, the second service message also includes service intention information.

[0048] In a possible implementation, the service intention information is carried in a metadata field of the second service message.

[0049] In one possible implementation, the processing unit is also used to: before encapsulating the path information of the first end-to-end path, determine that the next hop for forwarding the first service message is the second site edge according to the destination address of the first service message, and iterate the first segment routing policy SRPolicy according to the Internet Protocol IP address of the second site edge to obtain the path information of the first end-to-end path.

[0050] In a possible implementation, the first end-to-end path is an SRv6 tunnel, the second service message includes an IPv6 header and a segment routing header SRH, the destination address of the IPv6 header points to the first backbone network ingress device, and the SRH includes the first information and the second information.

[0051] In a possible implementation, the first information is the first endpoint segment identifier END.SID1 of the first backbone network ingress device, the second information is the second endpoint segment identifier END.SID2 of the first backbone network egress device, and the SRH also includes the IPv6 address of the second site edge.

[0052] In a possible implementation, the first information is the first endpoint segment identifier END.SID1 of the first backbone network ingress device, and the second information is the endpoint segment identifier END.X SID with a cross connection to a Layer 3 adjacency relationship array allocated by the first backbone network device egress device for the adjacency relationship between the first backbone network device egress device and the second site edge.

[0053] In a possible implementation, the operation associated with the first endpoint segment identifier END.SID1 includes: matching an upper layer overly SRv6Policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the END.SID1.

[0054] In one possible implementation, when the second service message includes service intent information, the operation associated with the first endpoint segment identifier END.SID1 includes: matching the upper layer overly SRv6Policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the END.SID1 and the service intent information.

[0055] In a possible implementation, the first end-to-end path is an SR-MPLS TE policy, the second service message includes an MPLS label stack, the MPLS label stack includes the first information and the second information, the first information is the first node SID of the first backbone network ingress device, and the second information includes: the second node SID of the first backbone network egress device, and the adjacency segment identifier adj-SID allocated by the first backbone network device egress device to the adjacency relationship between the first backbone network device egress device and the second site edge.

[0056] In a possible implementation, the operation of associating the first node SID includes: matching an upper layer overly SR-MPLS TE policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the first node SID in the label stack.

[0057] In one possible implementation, when the second service message includes service intent information, the operation of associating the first node SID includes: matching the upper layer overlySR-MPLS TE policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the first node SID in the label stack and the service intent information.

[0058] In a possible implementation, the first end-to-end path is a tunnel encapsulated based on the general network virtualization encapsulation GENEVE protocol, and the second service message is encapsulated using SRv6 in GENEVE.

[0059] In a possible implementation, the first end-to-end path is a tunnel encapsulated based on the Generic Routing Encapsulation (GRE) protocol, and the second service message includes SRv6 over GRE encapsulation.

[0060] In one possible implementation, the second service message includes: an outer IP header, a User Datagram Protocol UDP header, an outer GRE encapsulation, an IPv6 header, an SRH, an inner GRE encapsulation and a payload, the payload includes the first service message, and the inner GRE encapsulation includes a VPN identifier of the VPN service carried by the first service message.

[0061] In a possible implementation, the receiving unit is further used to receive a third service message; the processing unit is further used to encapsulate the path information of the second end-to-end path in the outer layer of the third service message to obtain a fourth service message; wherein the path information of the second end-to-end path includes third information identifying a second backbone network ingress device in the backbone network and fourth information identifying a second backbone network egress device in the backbone network, the ingress endpoint of the second end-to-end path is the first site edge, the egress endpoint of the second end-to-end path is the second site edge, the second end-to-end path passes through the second backbone network ingress device and the second backbone network egress device, the first site edge is multi-homed to access the first backbone network ingress device and the second backbone network ingress device, and the second site edge is multi-homed to access the first backbone network egress device and the second backbone network egress device; the sending unit is further used to send the fourth service message through the second end-to-end path.

[0062] In a possible implementation, the first site edge accesses the first backbone network entry device through a software-defined wide area network SD-WAN tunnel or the Internet.

[0063] In a fourth aspect, an embodiment of the present application provides a device for forwarding traffic, which may include a transceiver unit and a processing unit; the transceiver unit is used to perform the receiving and / or sending operations performed by the first backbone network entry device as described in the second aspect above; the processing unit is used to perform operations other than the receiving and / or sending operations performed by the first backbone network entry device as described in the second aspect above.

[0064] In a specific example, the device includes: a receiving unit, a processing unit, and a sending unit. The receiving unit is used to receive a second service message from a first site edge, the payload of the second service message includes a first service message, and the outer layer of the first service message encapsulates the path information of the end-to-end path between the first site edge and the second site edge; wherein the path information of the end-to-end path includes: first information identifying the first backbone network ingress device and second information identifying the first backbone network egress device in the backbone network, the ingress end point of the end-to-end path is the first site edge, the egress end point of the end-to-end path is the second site edge, the end-to-end path passes through the first backbone network ingress device and the first backbone network egress device, the first site edge accesses the backbone network through the first backbone network ingress device, and the second site edge accesses the backbone network through the first backbone network egress device; the processing unit is used to process the second service message according to the first information to obtain a third service message; the sending unit is used to send the third service message to the first backbone network egress device.

[0065] In a possible implementation manner, the second service message also includes service intention information.

[0066] In a possible implementation, the service intention information is carried in a metadata field of the second service message.

[0067] In a possible implementation, the end-to-end path is an SRv6 tunnel, the second service message includes an IPv6 header and a segment routing header SRH, the destination address of the IPv6 header points to the first backbone network ingress device, and the SRH includes the first information and the second information.

[0068] In a possible implementation, the first information is a first endpoint segment identifier END.SID1 allocated by the first backbone network ingress device, the second information is a second endpoint segment identifier END.SID2 allocated by the first backbone network egress device, and the SRH also includes an IPv6 address of the second site edge.

[0069] In a possible implementation, the first information is the first endpoint segment identifier END.SID1 of the first backbone network ingress device, and the second information is the endpoint segment identifier END.X SID with a cross connection to a Layer 3 adjacency relationship array allocated by the first backbone network device egress device for the adjacency relationship between the first backbone network device egress device and the second site edge.

[0070] In a possible implementation, the operation of associating the first endpoint segment identifier END.SID1 includes: matching an upper layer overly SRv6 policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the END.SID1 in the SRH.

[0071] In one possible implementation, when the second service message includes service intent information, the operation associated with the first endpoint segment identifier END.SID1 includes: matching the upper layer overly SRv6 policy from the first backbone network ingress device to the first backbone network egress device according to the next hop SID of the END.SID1 in the SRH and the service intent information.

[0072] In a possible implementation, the processing unit is used to: match the first overlySRv6 policy between the first backbone network ingress device and the first backbone network egress device according to the next-hop SID of the END.SID1 in the SRH; and encapsulate the second service message using the first overly SRv6policy to obtain the third service message.

[0073] In a possible implementation, the processing unit is used to: match the second overly SRv6 policy between the first backbone network ingress device and the first backbone network egress device according to the next-hop SID of the END.SID1 in the SRH and the service intent information; and encapsulate the second service message using the second overly SRv6 Policy to obtain the third service message.

[0074] In one possible implementation, the end-to-end path is an SR-MPLS TE policy, the second service message includes an MPLS label stack, the MPLS label stack includes the first information and the second information, the first information is the first node SID of the first backbone network ingress device, and the second information includes: the second node SID of the first backbone network egress device, and the adjacency segment identifier adj-SID assigned by the first backbone network device egress device to the adjacency relationship between the first backbone network device egress device and the second site edge.

[0075] In a possible implementation, the operation of associating the first node SID includes: matching an upper layer overly SR-MPLS TE policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the first node SID in the label stack.

[0076] In one possible implementation, when the second service message includes service intent information, the operation of associating the first node SID includes: matching the upper layer overlySR-MPLS TE policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the first node SID in the label stack and the service intent information.

[0077] In one possible implementation, the processing unit is used to: match the first overly SR-MPLS TE policy between the first backbone network ingress device and the first backbone network egress device according to the next-hop SID of the first node SID in the label stack; and encapsulate the second service message using the first overly SR-MPLS TE policy to obtain the third service message.

[0078] In one possible implementation, the processing unit is used to: match the second overly SR-MPLS TE policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the first node SID in the label stack and the service intent information; and encapsulate the second service message using the second overly SR-MPLS TE policy to obtain the third service message.

[0079] In a possible implementation, the end-to-end path is a tunnel encapsulated based on the general network virtualization encapsulation GENEVE protocol, and the second service message is encapsulated using SRv6 in GENEVE.

[0080] In a possible implementation, the end-to-end path is a tunnel encapsulated based on the Generic Routing Encapsulation (GRE) protocol, and the second service message includes SRv6 over GRE encapsulation.

[0081] In one possible implementation, the second service message includes: an outer IP header, a User Datagram Protocol UDP header, an outer GRE encapsulation, an IPv6 header, an SRH, an inner GRE encapsulation and a payload, the payload includes the first service message, and the inner GRE encapsulation includes a VPN identifier of the VPN service carried by the first service message.

[0082] In one possible implementation, the first site edge accesses the first backbone network entry device through a software-defined wide area network SD-WAN tunnel or the Internet.

[0083] In a fifth aspect, an embodiment of the present application provides a communication device, characterized in that it includes: a processor and a memory;

[0084] The memory is used to store instructions; the processor is used to execute the instructions, so that the communication device executes the method described in the first aspect and any one of the first aspect above, or the communication device executes the method described in the second aspect and any one of the second aspect above.

[0085] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, including instructions or a computer program. When the instructions or the computer program are executed on a processor, the method described in the first aspect and any one of the first aspect is implemented, or the method described in the second aspect and any one of the second aspect is implemented.

[0086] In the seventh aspect, an embodiment of the present application provides a computer program product, including a computer program product, which, when running on a processor, implements the method described in the first aspect and any one of the first aspects, or implements the method described in the second aspect and any one of the second aspects.

[0087] In an eighth aspect, an embodiment of the present application provides a communication system, which includes a first site edge that executes the method described in the first aspect and any one of the first aspects, and a first backbone network entry device that executes the method described in the second aspect and any one of the second aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0088] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0089] Figure 1a A schematic diagram of an exemplary application scenario provided for an embodiment of the present application;

[0090] Figure 1b A schematic diagram of another exemplary application scenario provided for an embodiment of the present application;

[0091] Figure 1c A schematic diagram of another exemplary application scenario provided for an embodiment of the present application;

[0092] Figure 2 A signaling interaction diagram of a method for forwarding traffic provided in an embodiment of the present application;

[0093] Figure 3a A schematic diagram of the structure of SRv6 over GRE encapsulation provided in an embodiment of the present application;

[0094] Figure 3b A schematic diagram of the structure of an MPLS over GRE encapsulation provided in an embodiment of the present application;

[0095] Figure 3c A schematic diagram of the structure of an SRv6 in GENEVE package provided in an embodiment of the present application;

[0096] Figure 3d A schematic diagram of the structure of an SRv6 over GENEVE encapsulation provided in an embodiment of the present application;

[0097] Figure 3e A schematic diagram of the structure of an MPLS in GENEVE encapsulation provided in an embodiment of the present application;

[0098] Figure 4a A schematic diagram of a scenario of a traffic forwarding method provided in an embodiment of the present application;

[0099] Figure 4b A schematic diagram of another traffic forwarding method provided in an embodiment of the present application;

[0100] Figure 4c A schematic diagram of another traffic forwarding method provided in an embodiment of the present application;

[0101] Figure 4d A schematic diagram of a scenario of a traffic forwarding method provided in an embodiment of the present application;

[0102] Figure 4e A schematic diagram of another traffic forwarding method provided in an embodiment of the present application;

[0103] Figure 5 A flow chart of a method for forwarding traffic provided in an embodiment of the present application;

[0104] Figure 6 A flowchart of another method for forwarding traffic provided in an embodiment of the present application;

[0105] Figure 7 A schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0106] Figure 8 A schematic diagram of the structure of another communication device provided in an embodiment of the present application;

[0107] Fig. 9 A schematic diagram of the structure of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0108] The embodiments of the present application provide a method and device for forwarding traffic, which can improve the forwarding efficiency of business traffic.

[0109] For ease of understanding, possible application scenarios of the embodiments of the present application are first introduced.

[0110] Currently, in the wide area network, in order to achieve end-to-end fast delivery and flexible scheduling, SD-WAN technology is usually used. On the basis of different layers (Underlay) networks such as the Internet and dedicated line networks, SD-WAN tunnels are established to build an upper layer (Overlay) network based on SD-WAN, so as to decouple the wide area network services from the lower layer networks and improve the end-to-end delivery capabilities.

[0111] After SD-WAN is deployed, the SD-WAN Overlay network under the wide area network builds SD-WAN tunnels between points of presence (POPs), between customer-premises equipment (CPE) and edge points of presence (EPOPs) based on the original Underlay network. The service traffic passes through the intermediate devices in the form of tunnels, so that the intermediate devices are not aware of the service. At the overlay network level, each CPE or POP represents a hop for the service route, and the service traffic is forwarded end-to-end in the POP networking in the form of hop-by-hop or tunnels, labels, etc.

[0112] See also Figure 1a , which is a schematic diagram of an exemplary application scenario provided by an embodiment of the present application. Figure 1a As shown, the service traffic needs to be transmitted across the edge access area 100, the backbone network 200 and the edge access area 300. Among them:

[0113] The edge access network 100 includes: site edge1, site edge3 and site edge4.

[0114] The backbone network 200 includes at least one network device. For example, when the backbone network 200 is a POP backbone network, the backbone network 200 includes at least one POP, wherein the POP connected to the site edge in the POP backbone network is called an EPOP, and the POP not connected to the site edge is called a backbone point of presence (BPOP). In one example, the site edge can be a CPE.

[0115] The edge access network 300 includes: site edge2 and site edge5.

[0116] The site edge in the edge access network 100 and 300 can access the backbone network through the EPOP in the backbone network. The EPOP in the backbone network used by the site edge to access the backbone network can be considered as the gateway corresponding to the site edge. Figure 1a As shown, site edge1 is dual-homed to gateway (GW) 1 and gateway 3, and site edge1 can access backbone network 200 through gateway 1 and gateway 3. For another example, site edge2 is dual-homed to gateway 2 and gateway 4, and site edge2 can access backbone network 200 through gateway 2 and gateway 4.

[0117] The site edge can access its corresponding gateway through the SD-WAN tunnel or the internet.

[0118] In the embodiment of the present application, the backbone network can be a hybrid network including at least one network domain, and the at least one network domain includes but is not limited to: a self-built backbone network and / or a managed service provider (MSP) backbone network, wherein the MSP backbone network can include a single operator network, a hybrid operator network, and a self-built dedicated line network, which is not specifically limited in the embodiment of the present application. MPLS technology can be applied to the backbone network, and SRv6 technology can also be applied, which is not specifically limited in the embodiment of the present application.

[0119] For reference Figure 1b and Figure 1c To understand, Figure 1b and Figure 1c Two other exemplary application scenario schematic diagrams are provided for the embodiments of the present application.

[0120] like Figure 1b As shown, the backbone network 400 includes: Internet service provider (ISP) network 1 (ISP1 for short), ISP2, ISP3 and a self-built dedicated line network. Figure 1c The scene shown is similar to Figure 1b The difference is that Figure 1c The backbone network 500 shown does not include a self-built dedicated line network.

[0121] about Figure 1b and Figure 1c The connection method between network devices in the network architecture shown is not described in detail here.

[0122] At present, when service traffic needs to be transmitted across the backbone network, service-related configurations need to be performed in the backbone network. For example, VPN configurations need to be performed in the backbone network. The configuration efficiency is low, which leads to low service provisioning efficiency. Especially when the backbone network includes multiple heterogeneous network domains, service VPN instances need to be planned at the boundary interconnection of the intermediate heterogeneous networks to perform service re-addressing, forwarding and isolation. Moreover, since the backbone network needs to be aware of the service, the scalability of the backbone network will also be affected.

[0123] Correspondingly, during the forwarding phase of business traffic, the network devices in the backbone network also need to combine VPN configuration to forward traffic, resulting in low forwarding efficiency of business traffic. Figure 1b Taking the scenario shown as an example, when the service traffic reaches POP1, POP1 needs to determine the forwarding path of the service traffic in conjunction with the VPN instance and further forward it. When the service traffic is forwarded to POP2, POP3 and POP4, POP2, POP3 and POP4 also need to further determine the forwarding path of the service traffic in conjunction with the VPN configuration, so as to further forward the service traffic.

[0124] In order to solve the above problems, an embodiment of the present application provides a method for forwarding traffic. Next, the traffic forwarding method is introduced in conjunction with the accompanying drawings.

[0125] See also Figure 2 , this figure is a signaling interaction diagram of a method for forwarding traffic provided in an embodiment of the present application. Figure 2 The method 100 shown can be applied to Figure 1a The application scenario shown can also be applied to Figure 1b The application scenario shown can also be applied to Figure 1c The application scenario shown.

[0126] When the method 100 is applied to Figure 1a In the application scenario shown in the figure, the site edge1 in the method 100 may correspond to Figure 1a The site edge1 shown; the site edge2 in method 100 may correspond to Figure 1a The site edge2 shown; the backbone network entry device 1 in the method 100 may correspond to Figure 1a GW1 shown; the backbone network egress device 1 in method 100 may correspond to Figure 1a GW2 or GW4 shown.

[0127] When the method 100 is applied to Figure 1b In the application scenario shown in the figure, the site edge1 in the method 100 may correspond to Figure 1b The site edge1 shown; the site edge2 in method 100 may correspond to Figure 1bThe site edge2 shown; the backbone network entry device 1 in the method 100 may correspond to Figure 1a The POP1 shown; the backbone network egress device 1 in the method 100 may correspond to Figure 1b POP4 or POP9 as shown.

[0128] When the method 100 is applied to Figure 1c In the application scenario shown in the figure, the site edge1 in the method 100 may correspond to Figure 1c The site edge1 shown; the site edge2 in method 100 may correspond to Figure 1c The site edge2 shown; the backbone network entry device 1 in the method 100 may correspond to Figure 1c The POP1 shown; the backbone network egress device 1 in the method 100 may correspond to Figure 1c POP4 or POP9 as shown.

[0129] The method 100 may, for example, include the following S101 - S106 .

[0130] S101: Site edge1 receives service message 1.

[0131] In an example, the site edge may receive a service message 1 from a user device, where the user device may be a terminal device or a server, which is not specifically limited in the present embodiment. In an example, the service message 1 may include a source address, a destination address, and a payload.

[0132] S102: Site edge1 encapsulates the path information of end-to-end path 1 in the outer layer of service message 1 to obtain service message 2. The input end point of end-to-end path 1 is site edge1, and the output end point of end-to-end path 1 is site edge2. End-to-end path 1 includes backbone network ingress device 1 and backbone network egress device 1. Site edge1 accesses the backbone network through backbone network ingress device 1, and site edge2 accesses the backbone network through backbone network egress device 1. The path information of end-to-end path 1 includes: information 1 identifying backbone network ingress device 1, and information 2 identifying backbone network egress device 1.

[0133] In an embodiment of the present application, site edge1 accesses the backbone network through backbone network entry device 1, and site edge2 accesses the backbone network through backbone network exit device 1. In one example, the site edge1 can access the backbone network entry device 1 through the internet. In another example, the site edge1 can access the backbone network entry device 1 through an SD-WAN tunnel. Similarly, in one example, the site edge2 can access the backbone network exit device 1 through the internet. In another example, the site edge2 can access the backbone network exit device 1 through an SD-WAN tunnel.

[0134] In one example, after receiving service message 1, site edge1 can encapsulate path information of end-to-end path 1 in the outer layer of service message 1 to obtain service message 2. After the outer layer of service message 1 encapsulates the path information, service message 1 belongs to the payload of service message 2.

[0135] In another example, when encapsulating the service message 1, in addition to encapsulating the aforementioned path information in the outer layer of the service message 1, the service intent information can also be encapsulated in the outer layer of the service message 1 to obtain the service message 2 including the path information and the service intent information. In this way, after forwarding the service message 2, the forwarding device that receives the service message 2 can select the corresponding path for forwarding in combination with the service intent information when further forwarding the service message 2, so that the service intent is met, and accordingly, the service quality provided for the service is improved.

[0136] The business intention information in the embodiment of the present application may include one or more information indicating the business intention. In one example, the business intention information may include a quality of service parameter, and the quality of service parameter is not limited to one or more parameters such as latency, packet loss, jitter, bandwidth utilization, and bit error rate. In another example, the business intention parameter may include gateway constraint information that needs to be satisfied by the end-to-end path from site edge1 to site edge2, and the gateway constraint information includes but is not limited to the gateways that need to be passed through and / or the gateways that need to be detoured.

[0137] In a specific example, a metadata field may be encapsulated in the outer layer of the service message 1, and the metadata field is used to carry the service intent information. The metadata field may be carried, for example, by an extension header. In another specific example, the service intent information may be carried by using an available field in the outer layer of the service message 2.

[0138] In one example, before encapsulating the aforementioned path information in the outer layer of the service message 1, the site edge 1 can determine the path information of the end-to-end path 1 for transmitting the service message 1 according to the service message 1. As an example, the site edge can determine the path information of the end-to-end path 1 according to the destination address of the service message 1.

[0139] In a specific example, the site edge1 may pre-store a mapping relationship between the destination address of the service message 1 and the aforementioned path information, and the site edge1 may match the mapping relationship according to the destination address of the service message 1 to obtain the path information.

[0140] In another specific example, the site edge1 can determine the next hop for forwarding the service message according to the destination address of the service message 1. Specifically, the site edge1 can query the service table entry according to the destination address of the service message 1, and determine that the next hop for forwarding the service message 1 is the site edge2. Further, the IP address of the site edge2 is used to iterate SR policy1, so as to obtain the path information of the end-to-end path. In an example, the IP address of the site edge2 can be used to match the destination addresses of multiple SR policies, and when the IP address of the site edge2 successfully matches the destination address of SR policy1, it is determined that the IP address of the site edge2 is iterated to SR policy1. Accordingly, the path information indicated by the SR policy1 can be determined as the path information of the end-to-end path 1.

[0141] In one example, the SR policy 1 may be an SRv6 policy. In this case, the end-to-end path 1 may be an SRv6 tunnel.

[0142] In yet another example, the SR policy 1 may be an MPLS SR policy. In this case, the end-to-end path 1 may be an SR-MPLS TE policy.

[0143] In one example, the end-to-end path 1 may be pre-arranged by the site edge1. In this case, the site edge1 may further arrange the end-to-end path 1 before receiving the service message 1. In a specific example, the service message 1 is used to carry VPN services, and the site edge1 may arrange the end-to-end path 1 between the site edge1 and the site edge2 according to the VPN services and in combination with the aforementioned backbone network entry device 1 and backbone network exit device 1 as needed. As an example, the site edge1 may arrange the end-to-end path for the VPN route after receiving the VPN route including the destination prefix announced by the site edge2. In a specific example, the site edge1 may arrange the end-to-end path 1 for the VPN route based on the binding relationship 1 between the site edge1 and the backbone network entry device 1, and the binding relationship 2 between the site edge2 and the backbone network exit device 1. When the method 100 is applied to Figure 1b or Figure 1c In the application scenario shown, the destination prefix may be, for example, a network prefix corresponding to an enterprise headquarters.

[0144] In one example, if the end-to-end path is an SRv6 tunnel, the service message 2 may include an IPv6 header and an SRH, the aforementioned information 1 and information 2 may be carried in the SRH, and the destination address of the IPv6 header points to the backbone network ingress device 1, so that the site edge1 forwards the service message 2 to the backbone network ingress device 1 based on the destination address of the IPv6 header. In one example, the destination address of the IPv6 header may be END.SID1 of the backbone network ingress device.

[0145] In one example, when the end-to-end path is an SRv6 tunnel, the aforementioned information 1 may be END.SID1 of the backbone network ingress device, and the aforementioned information 2 may be END.SID2 of the backbone network egress device 1. In this case, the information 1 also includes the IPv6 address of the site edge2, and accordingly, the aforementioned SRH may also include the IPv6 address of the site edge2. In this case, the SRH may indicate the path from the backbone network ingress device 1 to the site edge2.

[0146] In another example, when the end-to-end path is an SRv6 tunnel, the aforementioned information 1 may be END.SID1 of the backbone network ingress device, and the aforementioned information 2 may be END.X SID allocated by the backbone network egress device 1 for the adjacency relationship between the backbone network egress device 1 and the site edge 2. In this case, the SRH may also indicate the path from the backbone network ingress device 1 to the site edge 2.

[0147] In one example, the END.SID1 can be used to indicate a new message forwarding operation. In this case, the backbone network entry device 1 can determine how to forward the service message 2 based on END.SID1, without combining VPN information to determine how to forward the service message 2. In a specific example, the operation associated with the END.SID1 includes: matching the overly SRv6 Policy from the backbone network entry device 1 to the backbone network exit device 1 according to the next hop SID of END.SID1. As can be seen from the previous description of the path information, in one example, the next hop SID of the END.SID1 can be END.SID2. In this case, the operation associated with the END.SID1 includes: matching the overly SRv6 Policy from the backbone network entry device 1 to the backbone network exit device 1 according to END.SID2. In another example, the next hop SID of the END.SID1 can be END.X SID. In this case, the operation associated with the END.SID1 includes: matching the overly SRv6 policy from the backbone network entry device 1 to the backbone network exit device 1 according to END.X SID.

[0148] In another specific example, if the service message 2 includes service intent information, the operation associated with the END.SID1 includes: matching the overly SRv6 policy from the backbone network entry device 1 to the backbone network exit device 1 according to the next hop SID of END.SID1 and the service intent information. In this case, when forwarding the service message 2, the backbone network entry device 1 can also determine the corresponding overly SRv6 policy in combination with the service intent information, so that the determined overly SRv6 policy satisfies the service intent as much as possible, thereby improving the service quality provided to the service as much as possible. When the next hop SID of the END.SID1 is END.SID2, the operation associated with the END.SID1 includes: matching the overly SRv6 policy from the backbone network entry device 1 to the backbone network exit device 1 according to END.SID2 and the service intent information. When the next hop SID of the END.SID1 is END.X SID, the operation associated with the END.SID1 includes: matching the overlySRv6 policy from the backbone network ingress device 1 to the backbone network egress device 1 according to the END.X SID and the service intent information.

[0149] In one example, when the end-to-end path is an SR-MPLS TE policy, the service message 2 may include an MPLS label stack, and the aforementioned information 1 and information 2 may be carried in the MPLS label stack. In this scenario, the information 1 may be the node SID1 of the backbone network ingress device, and the information 2 may be the node SID2 of the backbone network egress device 1. For this case, the path information also includes the adj-SID assigned by the backbone network egress device 1 for the adjacency relationship between the backbone network egress device 1 and the site edge2, and accordingly, the MPLS label stack also includes the adj-SID. For this case, the node SID1, node SID2, and adj-SID in the MPLS label stack may indicate the path from the backbone network ingress device 1 to the site edge2.

[0150] In one example, the node SID1 can be used to indicate a new message forwarding operation. In this case, the backbone network entry device 1 can determine how to forward the service message 2 based on the node SID1, without combining the VPN information to determine how to forward the service message 2. In a specific example, the operation associated with the node SID1 includes: matching the overly SR-MPLS TE policy from the backbone network entry device 1 to the backbone network exit device 1 according to the next hop SID of the node SID1. As can be seen from the previous description of the path information, the next hop SID of the node SID1 can be the node SID2. In this case, the operation associated with the node SID1 includes: matching the overly SR-MPLS TE policy from the backbone network entry device 1 to the backbone network exit device 1 according to the node SID2.

[0151] In another specific example, if the service message 2 includes service intent information, the operation associated with the node SID1 includes: matching the overly SR-MPLS TE policy from the backbone network ingress device 1 to the backbone network egress device 1 according to the next hop SID of the node SID1 and the service intent information. In this case, when forwarding the service message 2, the backbone network ingress device 1 can also determine the corresponding overly SR-MPLS TE policy in combination with the service intent information, so that the determined overly SR-MPLS TE policy satisfies the service intent as much as possible, thereby improving the service quality provided to the service as much as possible. When the next hop SID of the node SID1 is node SID2, the operation associated with the node SID1 includes: matching the overly SR-MPLS TE policy from the backbone network ingress device 1 to the backbone network egress device 1 according to the node SID2 and the service intent information.

[0152] In an example, the end-to-end path 1 may be a tunnel based on GRE protocol encapsulation. In this case, the service message may be encapsulated using GRE.

[0153] In a specific example, if the end-to-end path 1 is an SRv6 tunnel, the service message 2 can be encapsulated using SRv6 over GRE. For this case, the encapsulation format of the service message 2 can refer to Figure 3a To understand, Figure 3a A schematic diagram of the structure of SRv6 over GRE encapsulation provided in an embodiment of the present application. Figure 3a As shown, the service message 2 includes: an outer IP header, a UDP header, an outer GRE encapsulation, an IPv6 header, an SRH, an inner GRE encapsulation and a payload, wherein the payload includes the aforementioned service message 1; the inner GRE encapsulation includes the VPN identifier of the VPN service carried by the service message 1. The VPN identifier is carried in the inner GRE encapsulation. When the service message 2 is transmitted in the backbone network, the equipment in the backbone network does not parse the VPN identifier (VPN identifier, VNI), that is, the backbone network does not perceive the VPN. In one example, a metadata field may also be included between the SRH and the inner GRE encapsulation. In another example, the service message 2 may also include a security check field, such as an Encapsulating Security Protocol (ESP) field, which is not described in detail here.

[0154] In another specific example, if the end-to-end path 1 is an SR-MPLS TE policy, the service message 2 can be encapsulated using MPLS over GRE. Figure 3b To understand, Figure 3b A schematic diagram of the structure of an MPLS over GRE encapsulation provided in an embodiment of the present application. Figure 3b As shown, the service message 2 includes: an outer IP header, a UDP header, an outer GRE encapsulation, an MPLS label stack, an inner GRE encapsulation and a payload, wherein the payload includes the aforementioned service message 1; the inner GRE encapsulation includes the VPN identifier of the VPN service carried by the service message 1. The VPN identifier is carried in the inner GRE encapsulation. When the service message 2 is transmitted in the backbone network, the equipment in the backbone network does not parse the VPN identifier, that is, the backbone network does not perceive the VPN. In one example, a metadata field may also be included between the MPLS label stack and the inner GRE encapsulation. In another example, the service message 2 may also include a security check field, such as an ESP field, which is not described in detail here.

[0155] In another example, the end-to-end path 1 may be a tunnel based on GENEVE protocol encapsulation. In this case, the service message may be encapsulated using GENEVE.

[0156] In a specific example, if the end-to-end path 1 is an SRv6 tunnel, the service message 2 may be encapsulated using SRv6 in GENEVE. For this case, the encapsulation format of the service message 2 may refer to Figure 3c To understand, Figure 3c A schematic diagram of the structure of an SRv6 in GENEVE package provided in an embodiment of the present application. Figure 3c As shown, the service message 2 includes: an outer IP header, a UDP header, a GENEVE encapsulation, an SRH and a payload, wherein the payload includes the aforementioned service message 1; the GENEVE encapsulation includes the VPN identifier of the VPN service carried by the service message 1. In one example, a metadata field may also be included between the SRH and the payload. In another example, the service message 2 may also include a security check field, such as an ESP field, which is not described in detail here. Of course, the service message 2 may also use SRv6 overGENEVE encapsulation. The difference between SRv6 over GENEVE encapsulation and SRv6in GENEVE encapsulation is that the service message 2 using SRv6over GENEVE encapsulation also includes an IPv6 header. See Figure 3d To understand, Figure 3d A schematic diagram of the structure of an SRv6 over GENEVE encapsulation provided in an embodiment of the present application. Figure 3d The package structure shown is relative to Figure 3c As for the SRv6 in GENEVE encapsulation shown in the figure, an IPv6 header is also included between the GENEVE encapsulation and the SRH. The encapsulation overhead of SRv6 over GENEVE encapsulation is larger than that of SRv6 in GENEVE encapsulation, but SRv6 over GENEVE encapsulation complies with the standard encapsulation format of SRv6.

[0157] In another specific example, if the end-to-end path 1 is an SR-MPLS TE policy, the service message 2 may be encapsulated using MPLS in GENEVE. Figure 3e To understand, Figure 3e A schematic diagram of the structure of an MPLS in GENEVE encapsulation provided in an embodiment of the present application. Figure 3eAs shown, the service message 2 includes: an outer IP header, a UDP header, a GENEVE encapsulation, an MPLS label stack and a payload, wherein the payload includes the aforementioned service message 1; the GENEVE encapsulation includes the VPN identifier of the VPN service carried by the service message 1. In one example, a metadata field may also be included between the MPLS label stack and the payload. In another example, the service message 2 may also include a security check field, such as an ESP field, which is not described in detail here.

[0158] S103: Site edge1 sends service message 2 through end-to-end path 1.

[0159] S104: Backbone network ingress device 1 receives service message 2 from site edge1.

[0160] S105: The backbone network ingress device 1 processes the service message 2 according to the information 1 to obtain the service message 3.

[0161] After receiving the service message 2, the site edge1 can forward the service message 2. In one example, the source address of the outer IP header of the service message 2 is the IP address of the site edge1, and the destination address is the IP address of the backbone network ingress device 1. The site edge1 forwards the service message 2 to the backbone network ingress device 1 according to the destination address in the outer IP header.

[0162] Backbone network ingress device 1 may receive service message 2 from site edge 1 , further parse service message 2 , and process service message 2 using information 1 in message 2 to obtain service message 3 .

[0163] As mentioned above, in one example, the information 1 may be END.SID1. In this case:

[0164] In one example, the backbone network ingress device 1 can match the overly SRv6 policy from the backbone network ingress device 1 to the backbone network egress device 1 according to the next hop SID of END.SID1 in the SRH of the service message 2. In one example, the backbone network ingress device 1 can use the next hop SID of END.SID1 to match the destination address of the overlySRv6 policy. When the destination address of the overly SRv6 policy1 successfully matches the next hop SID, it is determined that the match of overly SRv6 policy1 is successful. In a specific example, the backbone network ingress device 1 can use END.SID2 to match the overly SRv6 policy1. In another specific example, the backbone network ingress device 1 can use the aforementioned END.X SID to match the overly SRv6 policy1. After backbone network ingress device 1 matches and obtains overly SRv6 policy1, the overly SRv6 policy1 can be used to re-encapsulate service message 2. For example, backbone network ingress device 1 can insert a new SRH in service message 2 to carry the overly SRv6 policy1 to obtain service message 3. In one example, the SRH carrying overly SRv6policy1 can be located at the outer layer of the aforementioned SRH carrying information 1 and information 2.

[0165] In another example, if the service message 2 includes service intent information, the backbone network ingress device 1 can match the overly SRv6 policy from the backbone network ingress device 1 to the backbone network egress device 1 according to the next hop SID of END.SID1 in the SRH of the service message 2 and the service intent information. In one example, the backbone network ingress device 1 can use the next hop SID of END.SID1 to match the destination address of the overly SRv6 policy to obtain at least one overly SRv6 policy that matches the next hop SID of END.SID1, and then determine the overly SRv6 policy2 that meets the service intent information from the at least one overly SRv6 policy. In a specific example, the backbone network ingress device 1 can use END.SID2 and the service intent information to match the overly SRv6 policy2. In another specific example, the backbone network ingress device 1 can use the aforementioned END.XSID and the service intent information to match the overly SRv6 policy2. After the backbone network ingress device 1 matches and obtains the overly SRv6policy2, the overly SRv6 policy2 can be used to re-encapsulate the service message 2 to obtain the service message 3. For example, the backbone network ingress device 1 can insert a new SRH in the service message 2 to carry the overly SRv6 policy2 to obtain the service message 3. In one example, the SRH carrying the overlySRv6 policy2 can be located at the outer layer of the aforementioned SRH carrying the information 1 and the information 2.

[0166] As mentioned above, in one example, the information 1 may be the node SID1. In this case:

[0167] In one example, the backbone network ingress device 1 can match the overly SR-MPLS TE policy from the backbone network ingress device 1 to the backbone network egress device 1 according to the next hop SID of the node SID1 in the MPLS label stack of the service message 2. In one example, the backbone network ingress device 1 can use the next hop SID of the node SID1 to match the destination address of the overly SR-MPLS TE policy, and when the destination address of the overly SR-MPLS TEpolicy1 successfully matches the next hop SID, it is determined that the match of overly SR-MPLS TEpolicy1 is successful. In a specific example, the backbone network ingress device 1 can use the node SID2 to match the overly SR-MPLS TEpolicy1. After backbone network ingress device 1 matches and obtains overly SR-MPLS TE policy 1, it can use the overly SR-MPLS TE policy 1 to re-encapsulate service message 2. For example, backbone network ingress device 1 can replace node SID1 and node SID2 in the MPLS label stack in the service message 2 with the overly SR-MPLS TE policy 1 to obtain the service message 3.

[0168] In another example, if the service message 2 includes service intent information, the backbone network ingress device 1 can match the overly SR-MPLS TE policy from the backbone network ingress device 1 to the backbone network egress device 1 according to the next hop SID of the node SID1 in the MPLS label stack of the service message 2 and the service intent information. In one example, the backbone network ingress device 1 can use the next hop SID of the node SID1 to match the destination address of the overly SR-MPLS TE policy to obtain at least one overly SR-MPLS TE policy that matches the next hop SID of the node SID1, and then determine the overly SR-MPLS TE policy2 that meets the service intent information from the at least one overly SR-MPLS TE policy. After the backbone network ingress device 1 matches and obtains the overly SR-MPLS TE policy2, it can use the overly SR-MPLS TE policy2 to re-encapsulate the service message 2 to obtain the service message 3. For example, the backbone network ingress device 1 may replace the node SID1 and the node SID2 in the MPLS label stack in the service message 2 with the overly SR-MPLS TE policy 2 to obtain the service message 3.

[0169] S106: Backbone network ingress device 1 sends service message 3 to backbone network egress device 1.

[0170] After the backbone network ingress device 1 obtains the service message 3, it can send the service message 3 to the backbone network egress device 1. In one example, the backbone network ingress device 1 can send the service message 3 to the backbone network egress device 1 based on the aforementioned overly SRv6 policy1 or overlySRv6 policy2. In another example, the backbone network ingress device 1 can send the service message 3 to the backbone network egress device 1 based on the aforementioned overly SR-MPLS TE policy1 or overly SR-MPLS TE policy2.

[0171] From the above description, it can be known that, by using the method 100 provided in the embodiment of the present application, the site edge1 can arrange the end-to-end path 1 across the backbone network, without the need for the equipment in the backbone network to determine the transmission path based on the VPN configuration, so that the backbone network does not need to perceive the service, thereby improving the forwarding efficiency of the service traffic. Moreover, since the backbone network does not need to perceive the service, there is no need to perform service-related configuration on the equipment in the backbone network, thereby improving the efficiency of service activation, and correspondingly, also improving the scalability of the backbone network.

[0172] In one example, site edge1 can be dual-homed to backbone network entry device 1 and backbone network entry device 2. In other words, in addition to accessing the backbone network through backbone network entry device 1, site edge1 can also access the backbone network through backbone network entry device 2. Site edge2 can be dual-homed to backbone network exit device 1 and backbone network exit device 2. In other words, in addition to accessing the backbone network through backbone network exit device 1, site edge2 can also access the backbone network through backbone network exit device 2. For this case, the site edge1 can also arrange an end-to-end path 2 from site edge1 to site edge2, and the end-to-end path 2 includes an entry point of site edge1 and an exit point of site edge2, and the end-to-end path 2 includes the backbone network entry device 2 and backbone network exit device 2. For this case:

[0173] The site edge1 can also receive the service message 4, and encapsulate the path information of the end-to-end path 2 in the outer layer of the service message 4 to obtain the service message 5, and send the service message 5 through the end-to-end path 2. The path information of the end-to-end path 2 includes: information 3 identifying the backbone network ingress device 2 and information 4 identifying the backbone network egress device 2.

[0174] For the path information of the end-to-end path 2, please refer to the description of the path information of the end-to-end path 1 in the previous text. For the specific implementation of the site edge1 "encapsulating the path information of the end-to-end path 2 in the outer layer of the business message 4 to obtain the business message 5", please refer to the specific description of S102 in method 100, which will not be repeated here.

[0175] After the site edge1 sends the service message 5 through the end-to-end path 2, the backbone network ingress device 2 can receive the service message 5 from the site edge1, and further process the service message 5 based on the information 3 to obtain the service message 6, and further forward the service message 6. Regarding the processing method of the backbone network ingress device 2 on the service message 5, reference can be made to the processing method of the site edge1 on the service message 2 in the method 100, and no repeated description is given here.

[0176] The above describes the method for forwarding traffic provided by the embodiment of the present application. Figure 1b and Figure 1c The application scenario shown takes the end-to-end path between site edge1 and site edge2 as an end-to-end tunnel using GRE encapsulation as an example to illustrate the method for forwarding traffic provided in an embodiment of the present application.

[0177] First, combine Figure 1bThe application scenario shown introduces the solution of the embodiment of the present application.

[0178] See also Figure 4a , Figure 4a A scenario diagram of a traffic forwarding method provided in an embodiment of the present application. Figure 4a It shows that the solution provided by the embodiment of the present application is applied to Figure 1b In the scenario shown, the encapsulation format of the service traffic transmitted in the network. Figure 4a In the scenario shown, the end-to-end path between site edge1 and site edge2 is an SRv6 tunnel. The specific process of traffic forwarding is as follows:

[0179] Site edge1: The service message from the enterprise user to the headquarters arrives at the branch site edge1. The source address of the service message is the IP address of the enterprise user (client-ip), and the destination address of the service message is the IP address of the headquarters (server-ip). Site edge1 queries the server-ip route and determines that the next hop is the IP address system-ip2 of site edge2. Based on the iterative SRv6 policy of system-ip2 (the path list is: END.SID1, END.SID2, system-ip2), site edge1 encapsulates the IPv6 header and SRH in the outer layer of the service message, and encapsulates the service intent information at the same time. According to the SRv6 forwarding next hop END.SID1, the route forwarding continues to be checked. END.SID1 iterates the SDWAN tunnel and encapsulates the SDWAN tunnel link information: source address (sourceaddress, SA) = tnp1, destination address (destination address, DA) = tnp2) and sends the message to POP1. Among them: tnp1 is the IP address of the port used by site edge1 to communicate with POP1, and tnp2 is the IP address of the port used by POP1 to communicate with site edge1.

[0180] POP1: Decapsulate the outer SDWAN tunnel of the received message, query the IPv6 DA (END.SID1) to match the local SID table entry, and the operation associated with END.SID1 is to match the SR policy according to the next hop SID + business intent information. If the tunnel matching policy matches successfully, a new SRH (including the SR list: END.SID3, END.SID2) is inserted into the message, and the IPv6 header DA is replaced with END.SID3 to continue to query the route forwarding. END.SID3 iterates the SDWAN tunnel and sends the SDWAN tunnel link information (SA = tnp3, DA = tnp4) on the message encapsulation to POP2. If no SR policy is matched, continue to query the IPv6 DA (END.SID2) route forwarding to POP4. Among them: tnp3 is the IP address of the port used by POP1 to communicate with POP2, and tnp2 is the IP address of the port used by POP2 to communicate with POP1.

[0181] POP2: Decapsulate the outer SDWAN tunnel for the received message, query the IPv6 DA (END.SID3) to match the local SID table entry, change the IPv6 header DA to END.SID2 to continue to check the route forwarding, END.SID2 iterates the SDWAN tunnel, encapsulates the SDWAN tunnel link information (SA = tnp5, DA = tnp6), and sends the message to POP3. Among them: tnp5 is the IP address of the port used by POP2 to communicate with POP3, and tnp6 is the IP address of the port used by POP3 to communicate with POP2.

[0182] POP3: Decapsulate the outer SDWAN tunnel for the received message, continue to check the route forwarding according to IPv6 DA (END.SID2), and forward POP4 through the local direct connection interface according to the END.X SID route output interface.

[0183] POP4: Query the IPv6 DA (END.SID2) for the received message to match the local SID table entry, and SL is 0, remove the SRH encapsulation, change the IPv6 header DA to system-ip2 to continue to check the route forwarding, system-ip2 iterates the SDWAN tunnel, encapsulates the SDWAN tunnel link information (SA = tnp7, DA = tnp8), and sends the message to site edge2. Among them: tnp7 is the IP address of the port used by POP4 to communicate with site edge2, and tnp8 is the IP address of the port used by site edge2 to communicate with POP4.

[0184] Site edge2: decapsulates the outer SDWAN tunnel, queries system-ip2 for the local route, removes the IPv6 encapsulation, processes ESP, queries the server-ip route based on the VPN identifier in the GRE private network, and forwards the route to the destination.

[0185] See also Figure 4b , Figure 4b A scenario diagram of another traffic forwarding method provided in an embodiment of the present application. Figure 4b It shows that the solution provided by the embodiment of the present application is applied to Figure 1b In the scenario shown, the encapsulation format of the service traffic transmitted in the network. Figure 4b In the scenario shown, the end-to-end path between site edge1 and site edge2 is an SRv6 tunnel. The specific process of traffic forwarding is as follows:

[0186] Site edge1: The service message from the enterprise user to the headquarters arrives at the branch site edge1. The source address of the service message is the IP address of the enterprise user (client-ip), and the destination address of the service message is the IP address of the headquarters (server-ip). Site edge1 queries the server-ip route and determines that the next hop is the IP address system-ip2 of site edge2. It iterates the SRv6 policy based on system-ip2 (the path list is: END.SID1, END.X SID). Site edge1 encapsulates the IPv6 header and SRH in the outer layer of the service message, and encapsulates the service intent information at the same time. . According to the SRv6 forwarding next hop END.SID1, the route forwarding continues to be checked. END.SID1 iterates the SDWAN tunnel, encapsulates the SDWAN tunnel link information (SA=tnp1, DA=tnp2), and sends the message to POP1.

[0187] POP1: Decapsulate the outer SDWAN tunnel of the received message, query the IPv6 DA (END.SID1) to match the local SID table entry, and the operation associated with END.SID1 is to take the next hop SID + business intent information to match the SR policy. If the tunnel matching policy matches successfully, a new SRH (including the SR list: END.SID3, END.X SID) is inserted into the message, and the IPv6 header DA is replaced with END.SID3 to continue to check the route forwarding. END.SID3 iterates the SDWAN tunnel and sends the SDWAN tunnel link information (SA = tnp3, DA = tnp4) on the message encapsulation to POP2. If there is no match to the SR policy path, continue to check the IPv6 DA (END.X SID) route forwarding to POP4.

[0188] POP2: Decapsulates the outer SDWAN tunnel of the received message, queries the IPv6 DA (END.SID3) to match the local SID table entry, changes the IPv6 header DA to END.X SID to continue to check the route forwarding, iterates the END.X SID route to the SDWAN tunnel, encapsulates the SDWAN tunnel link information (SA=tnp5, DA=tnp6), and sends the message to POP3.

[0189] POP3: Decapsulate the outer SDWAN tunnel for the received message, continue to check the route forwarding according to the IPv6 DA (END.X SID), and forward POP4 directly through the local direct connection interface according to the END.X SID route output interface.

[0190] POP4: Query the IPv6 DA (END.X SID) for the received message to match the local SID table entry. At the same time, SL is 0, remove the SRH encapsulation, and remove the IPv6 header encapsulation. Iterate the SDWAN tunnel according to system-ip2, encapsulate the SDWAN tunnel link information (SA=tnp7, DA=tnp8), and send the message to site edge2.

[0191] Site edge2: Decapsulates the outer SDWAN tunnel of the received message, queries system-ip2 for the local route, removes the IPv6 encapsulation, processes ESP, queries the server-ip route based on the VPN identifier in the GRE private network, and forwards the route to the destination.

[0192] See also Figure 4c , Figure 4c A scenario diagram of another traffic forwarding method provided in an embodiment of the present application. Figure 4c It shows that the solution provided by the embodiment of the present application is applied to Figure 1b In the scenario shown, the encapsulation format of the service traffic transmitted in the network. Figure 4c In the scenario shown, the end-to-end path between site edge1 and site edge2 is SR-MPLS TEpolicy. The specific process of traffic forwarding is as follows:

[0193] Site edge1: The service message from the enterprise user to the headquarters arrives at the branch site edge1. The source address of the service message is the IP address of the enterprise user (client-ip), and the destination address of the service message is the IP address of the headquarters (server-ip). Site edge1 queries the server-ip route and determines that the next hop is the IP address system-ip2 of site edge2. Based on system-ip2, it iterates the SR-MPLS TE policy (the path list is: NODE.SID1, NODE.SID5, AdjacencySID), and encapsulates the MPLS label stack. According to the label forwarding next hop NODE.SID1, it continues to query the route and forward. NODE.SID1 iterates the SDWAN tunnel, encapsulates the SDWAN tunnel link information (SA=tnp1, DA=tnp2), and sends the message to POP1.

[0194] POP1: Decapsulates the outer SDWAN tunnel of the received message, queries NODE.SID1 to match the local SID table entry, and the operation associated with NODE.SID1 is to match the SR-MPLS TE policy based on the next-hop SID of NODE.SID1 in the MPLS label stack as the egress node information of the intermediate POP backbone network SR-MPLS label stack path. If the tunnel matching policy matches successfully, the local NODE.SID1 and the next-hop label NODE.SID5 in the message are replaced with the label stack corresponding to the intermediate POP backbone network SR-MPLS TEpolicy (backbone network SR-MPLS TE policy path: NODE.SID3, NODE.SID4, NODE.SID5), and the table is forwarded according to the top label NODE.SID3 in the stack. NODE.SID3 iterates the SDWAN tunnel, encapsulates the SDWAN tunnel link information (SA=tnp3, DA=tnp4), and sends the message to POP2. If POP1 does not match the POP backbone network SR-MPLS TE policy, it directly forwards the packet to POP4 based on the next hop label NODE.SID5 in the packet.

[0195] POP2: Decapsulates the outer SDWAN tunnel of the received message, queries the label NODE.SID3 to match the local SID table entry, then pops up the current NODE.SID3 label, and uses the next hop label NODE.SID4 to continue to look up the table and forward. The NODE.SID4 route iterates the SDWAN tunnel, encapsulates the SDWAN tunnel link information (SA=tnp5, DA=tnp6), and sends the message to POP3.

[0196] POP3: Decapsulate the outer SDWAN tunnel of the received message, pop up the current NODE.SID4 label, continue to look up the table and forward with the next hop label NODE.SID5, and forward POP4 through the local direct connection interface.

[0197] POP4: Decapsulates the outer SDWAN tunnel of the received message, matches the label NODE.SID5 with the local SID table entry, pops up the current NODE.SID5 label, continues to look up the table and forwards with the next hop label Adjacency SID, indicates that the next hop is the incoming SDWAN tunnel forwarding according to the Adjacency SID, pops up the current label Adjacency SID, encapsulates the SDWAN tunnel link information (SA=tnp7, DA=tnp8), and sends the message to site edge2.

[0198] Site edge2: decapsulates the outer SDWAN tunnel, processes ESP, queries the server-ip route in the private network identified by the VPN in GRE, queries the destination system-ip2 route, and forwards it to the destination.

[0199] See also Figure 4d , Figure 4d A scenario diagram of a traffic forwarding method provided in an embodiment of the present application. Figure 4d It shows that the solution provided by the embodiment of the present application is applied to Figure 1c In the scenario shown, the encapsulation format of the service traffic transmitted in the network. Figure 4d In the scenario shown, the end-to-end path between site edge1 and site edge2 is an SRv6 tunnel. The specific process of traffic forwarding is as follows:

[0200] Site edge1: The service message from the enterprise user to the headquarters arrives at the branch site edge1. The source address of the service message is the IP address of the enterprise user (client-ip), and the destination address of the service message is the IP address of the headquarters (server-ip). Site edge1 queries the server-ip route and determines that the next hop is the IP address system-ip2 of site edge2. Based on the iterative SRv6 policy of system-ip2 (the path list is: END.SID1, END.SID2, system-ip2), site edge1 encapsulates the IPv6 header and SRH in the outer layer of the service message, and encapsulates the service intent information. According to the SRv6 forwarding next hop END.SID1, the route forwarding continues to be checked. END.SID1 iterates the SDWAN tunnel, encapsulates the SDWAN tunnel link information (SA=tnp1, DA=tnp2), and sends the message to POP1.

[0201] POP1: Decapsulate the outer SDWAN tunnel of the received message, query the IPv6 DA (END.SID1) to match the local SID table entry, the operation associated with END.SID1 is to match the SR policy according to the next hop SID + business intent information, and insert a new SRH (including SR list: END.SID3, END.SID2) into the message if the tunnel matching policy matches successfully, and replace the IPV6 header DA with END.SID3 to continue to check the route forwarding, END.SID3 iterates the SDWAN tunnel, and sends the SDWAN tunnel link information (SA = tnp3, DA = tnp4) on the message encapsulation to POP2. If no SR policy is matched, continue to check the IPv6 DA (END.SID2) route forwarding to POP4. POP2: Decapsulate the outer SDWAN tunnel for the received message, query the IPv6DA (END.SID3) to match the local SID table entry, change the IPv6 header DA to END.SID2 to continue to check the route forwarding, END.SID2 iterates the SDWAN tunnel, encapsulates the SDWAN tunnel link information (SA = tnp5, DA = tnp9), and sends the message to POP4. Among them: tnp5 is the IP address of the port used by POP2 to communicate with POP4, and tnp9 is the IP address of the port used by POP4 to communicate with POP2.

[0202] POP4: Query the IPv6 DA (END.SID2) for the received message to match the local SID table entry. At the same time, SL is 0, remove the SRH encapsulation, change the IPV6 header DA to system-ip2 to continue to check the route forwarding, system-ip2 iterates the SDWAN tunnel, encapsulates the SDWAN tunnel link information (SA=tnp7, DA=tnp8), and sends the message to site edge2.

[0203] Site edge2: decapsulates the outer SDWAN tunnel, queries system-ip2 for the local route, removes the IPv6 encapsulation, processes ESP, queries the server-ip route in the private network based on the VNI identifier in GRE, and forwards the route to the destination.

[0204] See also Figure 4e , Figure 4e A scenario diagram of another traffic forwarding method provided in an embodiment of the present application. Figure 4e It shows that the solution provided by the embodiment of the present application is applied to Figure 1c In the scenario shown, the encapsulation format of the service traffic transmitted in the network. Figure 4e In the scenario shown, the end-to-end path between site edge1 and site edge2 is SR-MPLS TEpolicy. The specific process of traffic forwarding is as follows:

[0205] Site edge1: The service message from the enterprise user to the headquarters arrives at the branch site edge1. The source address of the service message is the IP address of the enterprise user (client-ip), and the destination address of the service message is the IP address of the headquarters (server-ip). Site edge1 queries the server-ip route and determines that the next hop is the IP address system-ip2 of site edge2. Based on system-ip2, it iterates the SR-MPLS TE policy (the path list is: NODE.SID1, NODE.SID5, AdjacencySID), and encapsulates the MPLS label stack. According to the label forwarding next hop NODE.SID1, it continues to query the route and forward. NODE.SID1 iterates the SDWAN tunnel, encapsulates the SDWAN tunnel link information (SA=tnp1, DA=tnp2), and sends the message to POP1.

[0206] POP1: Decapsulates the outer SDWAN tunnel of the received message, queries NODE.SID1 to match the local SID table entry, and the operation associated with NODE.SID1 is to match the SR-MPLS TE policy based on the next-hop SID of NODE.SID1 in the MPLS label stack as the egress node information of the intermediate POP backbone network SR-MPLS label stack path. If the tunnel matching policy matches successfully, the local NODE.SID1 and the next-hop label NODE.SID5 in the message are replaced with the label stack corresponding to the intermediate POP backbone network SRMPLS policy (backbone network SR-MPLS TE policy path: NODE.SID3, NODE.SID5), and the table is forwarded according to the top label NODE.SID3 in the stack. NODE.SID3 iterates the SDWAN tunnel, encapsulates the SDWAN tunnel link information (SA=tnp3, DA=tnp4), and sends the message to POP2. If POP1 does not match the POP backbone network SR-MPLS TE policy, it directly forwards the packet to POP4 based on the next hop label NODE.SID5 in the packet.

[0207] POP2: Decapsulates the outer SDWAN tunnel of the received message, queries the label NODE.SID3 to match the local SID table entry, then pops up the current NODE.SID3 label, uses the next hop label NODE.SID5 to continue to look up the table and forward, NODE.SID5 routes iterate the SDWAN tunnel, encapsulates the SDWAN tunnel link information (SA=tnp5, DA=tnp9), and sends the message to POP4.

[0208] POP4: Decapsulates the outer SDWAN tunnel of the received message, matches the label NODE.SID5 with the local SID table entry, pops up the current NODE.SID5 label, continues to look up the table and forwards with the next hop label Adjacency SID, indicates that the next hop is the incoming SDWAN tunnel forwarding according to the Adjacency SID, pops up the current label Adjacency SID, encapsulates the SDWAN tunnel link information (SA=tnp7, DA=tnp8), and sends the message to site edge2.

[0209] Site edge2: decapsulates the outer SDWAN tunnel, processes ESP, queries the server-ip route in the private network identified by the VPN in GRE, queries the destination system-ip2 route, and forwards it to the destination.

[0210] See also Figure 5 , which is a flow chart of a method for forwarding traffic provided in an embodiment of the present application. Figure 5 The traffic forwarding method 200 shown can be applied to the above method 100 .

[0211] The method 200 for forwarding traffic may include the following S201 - S203 .

[0212] S201: The first site edge receives a first service message.

[0213] S202: The first site edge encapsulates the path information of the first end-to-end path in the outer layer of the first service message to obtain the second service message; wherein the path information of the first end-to-end path includes first information identifying the first backbone network entry device in the backbone network and second information identifying the first backbone network exit device in the backbone network, the entry point of the first end-to-end path is the first site edge, the exit point of the first end-to-end path is the second site edge, the first end-to-end path passes through the first backbone network entry device and the first backbone network exit device, the first site edge accesses the backbone network through the first backbone network entry device, and the second site edge accesses the backbone network through the first backbone network exit device.

[0214] S203: The first site edge sends the second service message through the first end-to-end path.

[0215] The first site edge in method 200 may correspond to site edge1 in method 100; the first business message in method 200 may correspond to business message 1 in method 100; the second business message in method 200 may correspond to business message 2 in method 100; the first end-to-end path in method 200 may correspond to end-to-end path 1 in method 100; the first information in method 200 may correspond to information 1 in method 100; the second information in method 200 may correspond to information 2 in method 100; the first backbone network ingress device in method 200 may correspond to backbone network ingress device 1 in method 100; the first backbone network egress device in method 200 may correspond to backbone network egress device 1 in method 100; the second site edge in method 200 may correspond to site edge2 in method 100.

[0216] In one possible implementation, the first service message is used to carry a virtual private network VPN service. Before receiving the first service message, the method also includes: the first site edge, based on the VPN service, combines the first backbone network entry device and the first backbone network exit device as needed to orchestrate the first end-to-end path from the first site edge to the second site edge.

[0217] In a possible implementation manner, the second service message also includes service intention information.

[0218] In a possible implementation, the service intention information is carried in a metadata field of the second service message.

[0219] In one possible implementation, before encapsulating the path information of the first end-to-end path, the method also includes: the first site edge determines, based on the destination address of the first service message, that the next hop for forwarding the first service message is the second site edge, and iterates the first segment routing policy SR policy based on the Internet Protocol IP address of the second site edge to obtain the path information of the first end-to-end path.

[0220] The first SR policy in method 200 may correspond to SR policy1 in method 100 .

[0221] In a possible implementation, the first end-to-end path is an SRv6 tunnel, the second service message includes an IPv6 header and a segment routing header SRH, the destination address of the IPv6 header points to the first backbone network ingress device, and the SRH includes the first information and the second information.

[0222] In a possible implementation, the first information is the first endpoint segment identifier END.SID1 of the first backbone network ingress device, the second information is the second endpoint segment identifier END.SID2 of the first backbone network egress device, and the SRH also includes the IPv6 address of the second site edge.

[0223] In a possible implementation, the first information is the first endpoint segment identifier END.SID1 of the first backbone network ingress device, and the second information is the endpoint segment identifier END.X SID with a cross connection to a Layer 3 adjacency relationship array allocated by the first backbone network device egress device for the adjacency relationship between the first backbone network device egress device and the second site edge.

[0224] In a possible implementation, the operation associated with the first endpoint segment identifier END.SID1 includes: matching an upper layer overly SRv6Policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the END.SID1.

[0225] In one possible implementation, when the second service message includes service intent information, the operation associated with the first endpoint segment identifier END.SID1 includes: matching the upper layer overly SRv6Policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the END.SID1 and the service intent information.

[0226] In a possible implementation, the first end-to-end path is an SR-MPLS TE policy, the second service message includes an MPLS label stack, the MPLS label stack includes the first information and the second information, the first information is the first node SID of the first backbone network ingress device, and the second information includes: the second node SID of the first backbone network egress device, and the adjacency segment identifier adj-SID allocated by the first backbone network device egress device to the adjacency relationship between the first backbone network device egress device and the second site edge.

[0227] In a possible implementation, the operation of associating the first node SID includes: matching an upper layer overly SR-MPLS TE policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the first node SID in the label stack.

[0228] In one possible implementation, when the second service message includes service intent information, the operation of associating the first node SID includes: matching the upper layer overlySR-MPLS TE policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the first node SID in the label stack and the service intent information.

[0229] In a possible implementation, the first end-to-end path is a tunnel encapsulated based on the general network virtualization encapsulation GENEVE protocol, and the second service message is encapsulated using SRv6 in GENEVE.

[0230] In a possible implementation, the first end-to-end path is a tunnel encapsulated based on the Generic Routing Encapsulation (GRE) protocol, and the second service message includes SRv6 over GRE encapsulation.

[0231] In one possible implementation, the second service message includes: an outer IP header, a User Datagram Protocol UDP header, an outer GRE encapsulation, an IPv6 header, an SRH, an inner GRE encapsulation and a payload, the payload includes the first service message, and the inner GRE encapsulation includes a VPN identifier of the VPN service carried by the first service message.

[0232] In a possible implementation, the method further includes:

[0233] The first site edge receives the third service message;

[0234] The first site edge encapsulates the path information of the second end-to-end path in the outer layer of the third service message to obtain a fourth service message; wherein the path information of the second end-to-end path includes third information identifying a second backbone network ingress device in the backbone network and fourth information identifying a second backbone network egress device in the backbone network, the ingress endpoint of the second end-to-end path is the first site edge, the egress endpoint of the second end-to-end path is the second site edge, the second end-to-end path passes through the second backbone network ingress device and the second backbone network egress device, the first site edge is multi-homed to access the first backbone network ingress device and the second backbone network ingress device, and the second site edge is multi-homed to access the first backbone network egress device and the second backbone network egress device;

[0235] The first site edge sends the fourth service message through the second end-to-end path.

[0236] The third business message in method 200 may correspond to business message 4 in method 100; the fourth business message in method 200 may correspond to business message 5 in method 100; the second end-to-end path in method 200 may correspond to end-to-end path 2 in method 100; the third information in method 200 may correspond to information 3 in method 100; the fourth information in method 200 may correspond to information 4 in method 100; the second backbone network ingress device in method 200 may correspond to backbone network ingress device 2 in method 100; the second backbone network egress device in method 200 may correspond to backbone network egress device 2 in method 100.

[0237] In a possible implementation, the first site edge accesses the first backbone network entry device through a software-defined wide area network SD-WAN tunnel or the Internet.

[0238] See also Figure 6 , this figure is a flow chart of another method for forwarding traffic provided in an embodiment of the present application. Figure 6 The traffic forwarding method 300 shown can be applied to the above method 100 .

[0239] The method 300 for forwarding traffic may include the following S301-S303.

[0240] S301: A first backbone network ingress device in a backbone network receives a second service message from a first site edge, the payload of the second service message includes the first service message, and the outer layer of the first service message encapsulates path information of an end-to-end path between the first site edge and the second site edge; wherein the path information of the end-to-end path includes: first information identifying the first backbone network ingress device and second information identifying the first backbone network egress device in the backbone network, the ingress endpoint of the end-to-end path is the first site edge, the egress endpoint of the end-to-end path is the second site edge, the end-to-end path passes through the first backbone network ingress device and the first backbone network egress device, the first site edge accesses the backbone network through the first backbone network ingress device, and the second site edge accesses the backbone network through the first backbone network egress device.

[0241] S302: The first backbone network ingress device processes the second service message according to the first information to obtain a third service message.

[0242] S303: The first backbone network ingress device sends the third service message to the first backbone network egress device.

[0243] The first site edge in method 300 may correspond to site edge1 in method 100; the first service message in method 300 may correspond to service message 1 in method 100; the second service message in method 300 may correspond to service message 2 in method 100; the first end-to-end path in method 300 may correspond to end-to-end path 1 in method 100; the first information in method 300 may correspond to information 1 in method 100; the second information in method 300 may correspond to information 2 in method 100; the first backbone network ingress device in method 300 may correspond to backbone network ingress device 1 in method 100; the first backbone network egress device in method 300 may correspond to backbone network egress device 1 in method 100; the second site edge in method 300 may correspond to site edge2 in method 100. The third service message in method 300 may correspond to service message 3 in method 100.

[0244] In a possible implementation manner, the second service message also includes service intention information.

[0245] In a possible implementation, the service intention information is carried in a metadata field of the second service message.

[0246] In a possible implementation, the end-to-end path is an SRv6 tunnel, the second service message includes an IPv6 header and a segment routing header SRH, the destination address of the IPv6 header points to the first backbone network ingress device, and the SRH includes the first information and the second information.

[0247] In a possible implementation, the first information is a first endpoint segment identifier END.SID1 allocated by the first backbone network ingress device, the second information is a second endpoint segment identifier END.SID2 allocated by the first backbone network egress device, and the SRH also includes an IPv6 address of the second site edge.

[0248] In a possible implementation, the first information is the first endpoint segment identifier END.SID1 of the first backbone network ingress device, and the second information is the endpoint segment identifier END.X SID with a cross connection to a Layer 3 adjacency relationship array allocated by the first backbone network device egress device for the adjacency relationship between the first backbone network device egress device and the second site edge.

[0249] In a possible implementation, the operation of associating the first endpoint segment identifier END.SID1 includes: matching an upper layer overly SRv6 policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the END.SID1 in the SRH.

[0250] In one possible implementation, when the second service message includes service intent information, the operation associated with the first endpoint segment identifier END.SID1 includes: matching the upper layer overly SRv6 policy from the first backbone network ingress device to the first backbone network egress device according to the next hop SID of the END.SID1 in the SRH and the service intent information.

[0251] In a possible implementation, the second service message is processed according to the first information to obtain a third service message, including: matching the first overly SRv6 policy from the first backbone network ingress device to the first backbone network egress device according to the next-hop SID of END.SID1 in the SRH; and encapsulating the second service message using the first overly SRv6policy to obtain the third service message.

[0252] In a possible implementation, the second service message is processed according to the first information to obtain a third service message, including: matching the second overly SRv6policy from the first backbone network ingress device to the first backbone network egress device according to the next-hop SID of END.SID1 in the SRH and the service intent information; and encapsulating the second service message using the second overly SRv6Policy to obtain the third service message.

[0253] In one possible implementation, the end-to-end path is an SR-MPLS TE policy, the second service message includes an MPLS label stack, the MPLS label stack includes the first information and the second information, the first information is the first node SID of the first backbone network ingress device, and the second information includes: the second node SID of the first backbone network egress device, and the adjacency segment identifier adj-SID assigned by the first backbone network device egress device to the adjacency relationship between the first backbone network device egress device and the second site edge.

[0254] In a possible implementation, the operation of associating the first node SID includes: matching an upper layer overly SR-MPLS TE policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the first node SID in the label stack.

[0255] In one possible implementation, when the second service message includes service intent information, the operation of associating the first node SID includes: matching the upper layer overlySR-MPLS TEpolicy from the first backbone network ingress device to the first backbone network egress device according to the next hop SID of the first node SID in the label stack and the service intent information.

[0256] In a possible implementation, the second service message is processed according to the first information to obtain a third service message, including: matching the first overly SR-MPLS TE policy from the first backbone network ingress device to the first backbone network egress device according to the next-hop SID of the first node SID in the label stack; and encapsulating the second service message using the first overly SR-MPLS TE policy to obtain the third service message.

[0257] In a possible implementation, the second service message is processed according to the first information to obtain a third service message, including: matching the second overly SR-MPLS TE policy from the first backbone network ingress device to the first backbone network egress device according to the next hop SID of the first node SID in the label stack and the service intent information; and encapsulating the second service message using the second overly SR-MPLS TE policy to obtain the third service message.

[0258] In a possible implementation, the end-to-end path is a tunnel encapsulated based on the general network virtualization encapsulation GENEVE protocol, and the second service message is encapsulated using SRv6 in GENEVE.

[0259] In a possible implementation, the end-to-end path is a tunnel encapsulated based on the Generic Routing Encapsulation (GRE) protocol, and the second service message includes SRv6 over GRE encapsulation.

[0260] In one possible implementation, the second service message includes: an outer IP header, a User Datagram Protocol UDP header, an outer GRE encapsulation, an IPv6 header, an SRH, an inner GRE encapsulation and a payload, the payload includes the first service message, and the inner GRE encapsulation includes a VPN identifier of the VPN service carried by the first service message.

[0261] In one possible implementation, the first site edge accesses the first backbone network entry device through a software-defined wide area network SD-WAN tunnel or the Internet.

[0262] See also Figure 7 , which is a structural diagram of a communication device provided in an embodiment of the present application.

[0263] Figure 7 The communication device 700 shown includes: a receiving unit 701, a processing unit 702 and a sending unit 703. The receiving unit 701 is used to perform a receiving operation, the sending unit 703 is used to perform a sending operation, and the processing unit 702 is used to perform other operations besides the receiving operation and the sending operation.

[0264] In an example, the communication device 700 may be applied to a first site edge, and is used to perform the operations performed by the first site edge provided in the above method embodiment.

[0265] The receiving unit 701 is configured to receive a first service message;

[0266] The processing unit 702 is configured to encapsulate the path information of the first end-to-end path in the outer layer of the first service message to obtain the second service message; wherein the path information of the first end-to-end path includes first information identifying a first backbone network ingress device in the backbone network and second information identifying a first backbone network egress device in the backbone network, the ingress endpoint of the first end-to-end path is the first site edge, the egress endpoint of the first end-to-end path is the second site edge, the first end-to-end path passes through the first backbone network ingress device and the first backbone network egress device, the first site edge accesses the backbone network through the first backbone network ingress device, and the second site edge accesses the backbone network through the first backbone network egress device;

[0267] The sending unit 703 is used to send the second service message through the first end-to-end path.

[0268] In one possible implementation, the first service message is used to carry a virtual private network VPN service, and the processing unit 702 is further used to: before receiving the first service message, according to the VPN service, combine the first backbone network ingress device and the first backbone network egress device as needed to orchestrate the first end-to-end path from the first site edge to the second site edge.

[0269] In a possible implementation manner, the second service message also includes service intention information.

[0270] In a possible implementation, the service intention information is carried in a metadata field of the second service message.

[0271] In one possible implementation, the processing unit 702 is also used to: before encapsulating the path information of the first end-to-end path, determine that the next hop for forwarding the first service message is the second site edge according to the destination address of the first service message, and iterate the first segment routing policy SR Policy according to the Internet Protocol IP address of the second site edge to obtain the path information of the first end-to-end path.

[0272] In a possible implementation, the first end-to-end path is an SRv6 tunnel, the second service message includes an IPv6 header and a segment routing header SRH, the destination address of the IPv6 header points to the first backbone network ingress device, and the SRH includes the first information and the second information.

[0273] In a possible implementation, the first information is the first endpoint segment identifier END.SID1 of the first backbone network ingress device, the second information is the second endpoint segment identifier END.SID2 of the first backbone network egress device, and the SRH also includes the IPv6 address of the second site edge.

[0274] In a possible implementation, the first information is the first endpoint segment identifier END.SID1 of the first backbone network ingress device, and the second information is the endpoint segment identifier END.X SID with a cross connection to a Layer 3 adjacency relationship array allocated by the first backbone network device egress device for the adjacency relationship between the first backbone network device egress device and the second site edge.

[0275] In a possible implementation, the operation associated with the first endpoint segment identifier END.SID1 includes: matching an upper layer overly SRv6Policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the END.SID1.

[0276] In one possible implementation, when the second service message includes service intent information, the operation associated with the first endpoint segment identifier END.SID1 includes: matching the upper layer overly SRv6Policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the END.SID1 and the service intent information.

[0277] In a possible implementation, the first end-to-end path is an SR-MPLS TE policy, the second service message includes an MPLS label stack, the MPLS label stack includes the first information and the second information, the first information is the first node SID of the first backbone network ingress device, and the second information includes: the second node SID of the first backbone network egress device, and the adjacency segment identifier adj-SID allocated by the first backbone network device egress device to the adjacency relationship between the first backbone network device egress device and the second site edge.

[0278] In a possible implementation, the operation of associating the first node SID includes: matching an upper layer overly SR-MPLS TE policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the first node SID in the label stack.

[0279] In one possible implementation, when the second service message includes service intent information, the operation of associating the first node SID includes: matching the upper layer overlySR-MPLS TE policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the first node SID in the label stack and the service intent information.

[0280] In a possible implementation, the first end-to-end path is a tunnel encapsulated based on the general network virtualization encapsulation GENEVE protocol, and the second service message is encapsulated using SRv6 in GENEVE.

[0281] In a possible implementation, the first end-to-end path is a tunnel encapsulated based on the Generic Routing Encapsulation (GRE) protocol, and the second service message includes SRv6 over GRE encapsulation.

[0282] In one possible implementation, the second service message includes: an outer IP header, a User Datagram Protocol UDP header, an outer GRE encapsulation, an IPv6 header, an SRH, an inner GRE encapsulation and a payload, the payload includes the first service message, and the inner GRE encapsulation includes a VPN identifier of the VPN service carried by the first service message.

[0283] In a possible implementation, the receiving unit 701 is further used to receive a third service message; the processing unit 702 is further used to encapsulate the path information of the second end-to-end path in the outer layer of the third service message to obtain a fourth service message; wherein the path information of the second end-to-end path includes third information identifying a second backbone network ingress device in the backbone network and fourth information identifying a second backbone network egress device in the backbone network, the ingress endpoint of the second end-to-end path is the first site edge, the egress endpoint of the second end-to-end path is the second site edge, the second end-to-end path passes through the second backbone network ingress device and the second backbone network egress device, the first site edge is multi-homed to access the first backbone network ingress device and the second backbone network ingress device, and the second site edge is multi-homed to access the first backbone network egress device and the second backbone network egress device; the sending unit 703 is further used to send the fourth service message through the second end-to-end path.

[0284] In a possible implementation, the first site edge accesses the first backbone network entry device through a software-defined wide area network SD-WAN tunnel or the Internet.

[0285] In another example, the communication device 700 may be applied to a first backbone network entry device in a backbone network, and is used to perform the operations performed by the first backbone network entry device provided in the above method embodiment.

[0286] A receiving unit 701 is used to receive a second service message from a first site edge edge, the payload of the second service message includes the first service message, and the outer layer of the first service message encapsulates the path information of the end-to-end path between the first site edge and the second site edge; wherein the path information of the end-to-end path includes: first information identifying the first backbone network ingress device and second information identifying the first backbone network egress device in the backbone network, the ingress endpoint of the end-to-end path is the first site edge, the egress endpoint of the end-to-end path is the second site edge, the end-to-end path passes through the first backbone network ingress device and the first backbone network egress device, the first site edge accesses the backbone network through the first backbone network ingress device, and the second site edge accesses the backbone network through the first backbone network egress device;

[0287] A processing unit 702, configured to process the second service message according to the first information to obtain a third service message;

[0288] The sending unit 703 is used to send the third service message to the first backbone network egress device.

[0289] In a possible implementation manner, the second service message also includes service intention information.

[0290] In a possible implementation, the service intention information is carried in a metadata field of the second service message.

[0291] In a possible implementation, the end-to-end path is an SRv6 tunnel, the second service message includes an IPv6 header and a segment routing header SRH, the destination address of the IPv6 header points to the first backbone network ingress device, and the SRH includes the first information and the second information.

[0292] In a possible implementation, the first information is a first endpoint segment identifier END.SID1 allocated by the first backbone network ingress device, the second information is a second endpoint segment identifier END.SID2 allocated by the first backbone network egress device, and the SRH also includes an IPv6 address of the second site edge.

[0293] In a possible implementation, the first information is the first endpoint segment identifier END.SID1 of the first backbone network ingress device, and the second information is the endpoint segment identifier END.X SID with a cross connection to a Layer 3 adjacency relationship array allocated by the first backbone network device egress device for the adjacency relationship between the first backbone network device egress device and the second site edge.

[0294] In a possible implementation, the operation of associating the first endpoint segment identifier END.SID1 includes: matching an upper layer overly SRv6 policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the END.SID1 in the SRH.

[0295] In one possible implementation, when the second service message includes service intent information, the operation associated with the first endpoint segment identifier END.SID1 includes: matching the upper layer overly SRv6 policy from the first backbone network ingress device to the first backbone network egress device according to the next hop SID of the END.SID1 in the SRH and the service intent information.

[0296] In a possible implementation, the processing unit 702 is used to: match the first overly SRv6 policy from the first backbone network ingress device to the first backbone network egress device according to the next-hop SID of the END.SID1 in the SRH; and encapsulate the second service message using the first overly SRv6 policy to obtain the third service message.

[0297] In a possible implementation, the processing unit 702 is used to: match the second overly SRv6 policy between the first backbone network ingress device and the first backbone network egress device according to the next-hop SID of the END.SID1 in the SRH and the service intent information; and encapsulate the second service message using the second overly SRv6 Policy to obtain the third service message.

[0298] In one possible implementation, the end-to-end path is an SR-MPLS TE policy, the second service message includes an MPLS label stack, the MPLS label stack includes the first information and the second information, the first information is the first node SID of the first backbone network ingress device, and the second information includes: the second node SID of the first backbone network egress device, and the adjacency segment identifier adj-SID assigned by the first backbone network device egress device to the adjacency relationship between the first backbone network device egress device and the second site edge.

[0299] In a possible implementation, the operation of associating the first node SID includes: matching an upper layer overly SR-MPLS TE policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the first node SID in the label stack.

[0300] In one possible implementation, when the second service message includes service intent information, the operation of associating the first node SID includes: matching the upper layer overlySR-MPLS TEpolicy from the first backbone network ingress device to the first backbone network egress device according to the next hop SID of the first node SID in the label stack and the service intent information.

[0301] In one possible implementation, the processing unit 702 is used to: match the first overly SR-MPLS TE policy between the first backbone network ingress device and the first backbone network egress device according to the next-hop SID of the first node SID in the label stack; and encapsulate the second service message using the first overly SR-MPLS TE policy to obtain the third service message.

[0302] In one possible implementation, the processing unit 702 is used to: match the second overly SR-MPLS TE policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the first node SID in the label stack and the service intent information; and encapsulate the second service message using the second overly SR-MPLS TE policy to obtain the third service message.

[0303] In a possible implementation, the end-to-end path is a tunnel encapsulated based on the general network virtualization encapsulation GENEVE protocol, and the second service message is encapsulated using SRv6 in GENEVE.

[0304] In a possible implementation, the end-to-end path is a tunnel encapsulated based on the Generic Routing Encapsulation (GRE) protocol, and the second service message includes SRv6 over GRE encapsulation.

[0305] In one possible implementation, the second service message includes: an outer IP header, a User Datagram Protocol UDP header, an outer GRE encapsulation, an IPv6 header, an SRH, an inner GRE encapsulation and a payload, the payload includes the first service message, and the inner GRE encapsulation includes a VPN identifier of the VPN service carried by the first service message.

[0306] In one possible implementation, the first site edge accesses the first backbone network entry device through a software-defined wide area network SD-WAN tunnel or the Internet.

[0307] In addition, the present application embodiment also provides a communication device 800, see Figure 8 As shown, Figure 8 The present invention provides a schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device 800 includes a communication interface 801 and a processor 802 connected to the communication interface 801. The communication device 800 can be used to execute the method 100, method 200 or method 300 in the above embodiment.

[0308] When the communication device 800 is used to execute the above method 100:

[0309] In one example, the communication device 800 is equivalent to the site edge1 in the method 100. The communication interface 801 is used to perform the sending and receiving operations performed by the site edge1 in the method 100. The processor 802 is used to perform operations other than the sending and receiving operations performed by the site edge1 in the method 100. For example: the communication interface 801 is used to receive the service message 1; the processor 802 is used to encapsulate the path information of the end-to-end path 1 in the outer layer of the service message 1 to obtain the service message 2, the input end point of the end-to-end path 1 is the site edge1, the output end point of the end-to-end path 1 is the site edge2, the end-to-end path 1 includes the backbone network inlet device 1 and the backbone network outlet device 1, the site edge1 accesses the backbone network through the backbone network inlet device 1, and the site edge2 accesses the backbone network through the backbone network outlet device 1, and the path information of the end-to-end path 1 includes: information 1 identifying the backbone network inlet device 1, and information 2 identifying the backbone network outlet device 1; the communication interface 801 is also used to send the service message 2 through the end-to-end path 1.

[0310] In another example, the communication device 800 is equivalent to the backbone network entry device 1 in the method 100. The communication interface 801 is used to perform the sending and receiving operations performed by the backbone network entry device 1 in the method 100. The processor 802 is used to perform operations other than the sending and receiving operations performed by the backbone network entry device 1 in the method 100. For example: the communication interface 801 is used to receive the service message 2 from the site edge1; the processor 802 is used to process the service message 2 according to the information 1 to obtain the service message 3; the communication interface 801 is also used to send the service message 3 to the backbone network exit device 1. When the communication device 800 is used to execute the above method 200, the communication device 800 is equivalent to the first site edge in the method 200. The communication interface 801 is used to perform the sending and receiving operations performed by the first site edge in the method 200. The processor 802 is used to perform operations other than the sending and receiving operations performed by the first site edge in the method 200. For example: the communication interface 801 is used to receive a first service message; the processor 802 is used to encapsulate the path information of the first end-to-end path in the outer layer of the first service message to obtain a second service message; wherein the path information of the first end-to-end path includes first information identifying a first backbone network entry device in the backbone network and second information identifying a first backbone network exit device in the backbone network, the entry point of the first end-to-end path is the first site edge, the exit point of the first end-to-end path is the second site edge, the first end-to-end path passes through the first backbone network entry device and the first backbone network exit device, the first site edge accesses the backbone network through the first backbone network entry device, and the second site edge accesses the backbone network through the first backbone network exit device; the communication interface 801 is also used to send the second service message through the first end-to-end path.

[0311] When the communication device 800 is used to execute the above method 300, the communication device 800 is equivalent to the first backbone network access device in the method 300. The communication interface 801 is used to execute the transceiver operation executed by the first backbone network access device in the method 300. The processor 802 is used to execute the operation other than the transceiver operation executed by the first backbone network access device in the method 300. For example: the communication interface 801 is used to receive a second service message from the edge of the first site, the payload of the second service message includes the first service message, and the outer layer of the first service message encapsulates the path information of the end-to-end path between the first site edge and the second site edge; wherein the path information of the end-to-end path includes: first information identifying the first backbone network ingress device and second information identifying the first backbone network egress device in the backbone network, the ingress endpoint of the end-to-end path is the first site edge, the egress endpoint of the end-to-end path is the second site edge, the end-to-end path passes through the first backbone network ingress device and the first backbone network egress device, the first site edge accesses the backbone network through the first backbone network ingress device, and the second site edge accesses the backbone network through the first backbone network egress device; the processor 802 is used to process the second service message according to the first information to obtain a third service message; the communication interface 801 is also used to send the third service message to the first backbone network egress device.

[0312] In addition, the present application embodiment also provides a communication device 900, see Fig. 9 As shown, Fig. 9 The present invention provides a schematic diagram of the structure of a communication device according to an embodiment of the present invention. The communication device 900 can be used to execute the method 100, 200 or 300 in the above embodiment.

[0313] like Fig. 9As shown, the communication device 900 may include a processor 910, a memory 920 coupled to the processor 910, and a transceiver 930. The transceiver 930 may be, for example, a communication interface, an optical module, etc. The processor 910 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and a NP. The processor may also be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof. The processor 910 may refer to one processor or may include multiple processors. The memory 920 may include a volatile memory (English: volatile memory), such as a random access memory (English: random-access memory, abbreviated: RAM); the memory may also include a non-volatile memory (English: non-volatile memory), such as a read-only memory (English: read-only memory, abbreviated: ROM), a flash memory (English: flash memory), a hard disk drive (English: hard disk drive, abbreviated: HDD) or a solid-state drive (English: solid-state drive, abbreviated: SSD); the memory 920 may also include a combination of the above-mentioned types of memories. The memory 920 may refer to one memory or may include multiple memories. In one embodiment, the memory 920 stores computer-readable instructions, and the computer-readable instructions include multiple software modules, such as a sending module 921, a processing module 922 and a receiving module 923. After executing each software module, the processor 910 may perform corresponding operations according to the instructions of each software module. In this embodiment, the operation performed by a software module actually refers to the operation performed by the processor 910 according to the instructions of the software module.

[0314] When the communication device 900 is used to execute the above method 100:

[0315] In one example, the communication device 900 is equivalent to the site edge1 in the method 100. The transceiver 930 is used to perform the transceiver operation performed by the site edge1 in the method 100. The processor 910 is used to perform operations other than the transceiver operation performed by the site edge1 in the method 100. For example: the transceiver 930 is used to receive the service message 1; the processor 910 is used to encapsulate the path information of the end-to-end path 1 in the outer layer of the service message 1 to obtain the service message 2, the input end point of the end-to-end path 1 is the site edge1, the output end point of the end-to-end path 1 is the site edge2, the end-to-end path 1 includes the backbone network inlet device 1 and the backbone network outlet device 1, the site edge1 accesses the backbone network through the backbone network inlet device 1, the site edge2 accesses the backbone network through the backbone network outlet device 1, and the path information of the end-to-end path 1 includes: information 1 identifying the backbone network inlet device 1, and information 2 identifying the backbone network outlet device 1; the transceiver 930 is also used to send the service message 2 through the end-to-end path 1.

[0316] In another example, the communication device 900 is equivalent to the backbone network entry device 1 in the method 100. The transceiver 930 is used to perform the transceiver operation performed by the backbone network entry device 1 in the method 100. The processor 910 is used to perform operations other than the transceiver operation performed by the backbone network entry device 1 in the method 100. For example: the transceiver 930 is used to receive the service message 2 from the site edge1; the processor 910 is used to process the service message 2 according to the information 1 to obtain the service message 3; the transceiver 930 is also used to send the service message 3 to the backbone network exit device 1. When the communication device 900 is used to execute the above method 200, the communication device 900 is equivalent to the first site edge in the method 200. The transceiver 930 is used to perform the transceiver operation performed by the first site edge in the method 200. The processor 910 is used to perform operations other than the transceiver operation performed by the first site edge in the method 200. For example: the transceiver 930 is used to receive a first service message; the processor 910 is used to encapsulate the path information of the first end-to-end path in the outer layer of the first service message to obtain a second service message; wherein the path information of the first end-to-end path includes first information identifying a first backbone network ingress device in the backbone network and second information identifying a first backbone network egress device in the backbone network, the ingress endpoint of the first end-to-end path is the first site edge, the egress endpoint of the first end-to-end path is the second site edge, the first end-to-end path passes through the first backbone network ingress device and the first backbone network egress device, the first site edge accesses the backbone network through the first backbone network ingress device, and the second site edge accesses the backbone network through the first backbone network egress device; the transceiver 930 is also used to send the second service message through the first end-to-end path.

[0317] When the communication device 900 is used to execute the above method 300, the communication device 900 is equivalent to the first backbone network access device in the method 300. The transceiver 930 is used to execute the transceiver operation executed by the first backbone network access device in the method 300. The processor 910 is used to execute the operation other than the transceiver operation executed by the first backbone network access device in the method 300. For example: the transceiver 930 is used to receive a second service message from the edge of the first site, the payload of the second service message includes the first service message, and the outer layer of the first service message encapsulates the path information of the end-to-end path between the first site edge and the second site edge; wherein the path information of the end-to-end path includes: first information identifying the first backbone network ingress device and second information identifying the first backbone network egress device in the backbone network, the ingress endpoint of the end-to-end path is the first site edge, the egress endpoint of the end-to-end path is the second site edge, the end-to-end path passes through the first backbone network ingress device and the first backbone network egress device, the first site edge accesses the backbone network through the first backbone network ingress device, and the second site edge accesses the backbone network through the first backbone network egress device; the processor 910 is used to process the second service message according to the first information to obtain a third service message; the transceiver 930 is also used to send the third service message to the first backbone network egress device.

[0318] The present application also provides a computer-readable storage medium, in which instructions or computer programs are stored. When the instruction computer program runs on a processor, any one or more operations of the methods described in the foregoing embodiments (such as method 100 or method 200) can be implemented.

[0319] The present application also provides a computer program product, including a computer program. When the computer program is executed on a processor, any one or more operations of the methods (eg, method 100 or method 200) described in the foregoing embodiments can be implemented.

[0320] The embodiment of the present application also provides a communication system for executing the method for forwarding traffic provided in the above method embodiment. In one example, the communication system includes: the site edge1 and the backbone network entry device 1 in the method 100. In another example, the communication system includes: the first site edge executing the above method 200 and the first backbone network entry device executing the above method 200.

[0321] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0322] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0323] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units is only a logical business division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0324] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0325] In addition, each business unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software business units.

[0326] If the integrated unit is implemented in the form of a software business unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0327] Those skilled in the art will appreciate that in one or more of the above examples, the services described in the present invention may be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, the services may be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another. Storage media may be any available media that can be accessed by a general-purpose or special-purpose computer.

[0328] The above specific implementation modes further describe the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above are only specific implementation modes of the present invention.

[0329] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person of ordinary skill in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features thereof may be replaced by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for forwarding traffic, characterized in that: The method comprises: The first site edge receives the first service message; The first site edge encapsulates the path information of the first end-to-end path in the outer layer of the first service message to obtain the second service message; wherein the path information of the first end-to-end path includes first information identifying a first backbone network ingress device in the backbone network and second information identifying a first backbone network egress device in the backbone network, the ingress endpoint of the first end-to-end path is the first site edge, the egress endpoint of the first end-to-end path is the second site edge, the first end-to-end path passes through the first backbone network ingress device and the first backbone network egress device, the first site edge accesses the backbone network through the first backbone network ingress device, and the second site edge accesses the backbone network through the first backbone network egress device; The first site edge sends the second service message through the first end-to-end path.

2. The method according to claim 1, characterized in that: The first service message is used to carry a virtual private network VPN service. Before receiving the first service message, the method further includes: The first site edge, based on the VPN service, combines the first backbone network ingress device and the first backbone network egress device as needed to orchestrate the first end-to-end path from the first site edge to the second site edge.

3. The method according to claim 1 or 2, characterized in that: The second service message also includes service intention information.

4. The method according to claim 3, characterized in that The service intention information is carried in the metadata field of the second service message.

5. The method according to any one of claims 1 to 4, characterized in that: Before encapsulating the path information of the first end-to-end path, the method further includes: The first site edge determines that the next hop for forwarding the first service message is the second site edge according to the destination address of the first service message, and iterates the first segment routing policy SR Policy according to the Internet Protocol IP address of the second site edge to obtain the path information of the first end-to-end path.

6. The method according to any one of claims 1 to 5, characterized in that: The first end-to-end path is an SRv6 tunnel, the second service message includes an Internet Protocol version 6 IPv6 header and a segment routing header SRH, the destination address of the IPv6 header points to the first backbone network ingress device, and the SRH includes the first information and the second information.

7. The method according to claim 6, characterized in that The first information is the first endpoint segment identifier END.SID1 of the first backbone network ingress device, the second information is the second endpoint segment identifier END.SID2 of the first backbone network egress device, and the SRH further includes the IPv6 address of the second site edge.

8. The method according to claim 6, characterized in that The first information is the first endpoint segment identifier END.SID1 of the first backbone network ingress device, and the second information is the endpoint segment identifier END.X SID with a cross connection to a layer 3 adjacency relationship array allocated by the first backbone network device egress device for the adjacency relationship between the first backbone network device egress device and the second site edge.

9. The method according to claim 7 or 8, characterized in that: The operation associated with the first endpoint segment identifier END.SID1 includes: matching an upper layer overly SRv6 policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the END.SID1.

10. The method according to claim 7 or 8, characterized in that: When the second service message includes service intent information, the operation associated with the first endpoint segment identifier END.SID1 includes: matching the upper layer overly SRv6 policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the END.SID1 and the service intent information.

11. The method according to any one of claims 1 to 5, characterized in that: The first end-to-end path is a segment routing multi-protocol label switching traffic engineering strategy SR-MPLS TE policy, the second service message includes an MPLS label stack, the MPLS label stack includes the first information and the second information, the first information is the first node SID of the first backbone network ingress device, and the second information includes: the second node SID of the first backbone network egress device, and the adjacency segment identifier adj-SID allocated by the first backbone network device egress device to the adjacency relationship between the first backbone network device egress device and the second site edge.

12. The method according to claim 11, characterized in that The operation of associating the first node SID includes: An overly SR-MPLS TE policy between the first backbone network ingress device and the first backbone network egress device is matched according to the next hop SID of the first node SID in the label stack.

13. The method according to claim 11, characterized in that When the second service message includes service intent information, the operation of associating the first node SID includes: matching the upper layer overly SR-MPLS TE policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the first node SID in the label stack and the service intent information.

14. The method according to any one of claims 6 to 10, characterized in that: The first end-to-end path is a tunnel encapsulated based on the general network virtualization encapsulation GENEVE protocol, and the second service message is encapsulated using SRv6 in GENEVE.

15. The method according to any one of claims 6 to 10, characterized in that: The first end-to-end path is a tunnel encapsulated based on the Generic Routing Encapsulation (GRE) protocol, and the second service message includes SRv6 over GRE encapsulation.

16. The method according to claim 15, characterized in that The second service message includes: Outer IP header, User Datagram Protocol UDP header, outer GRE encapsulation, IPv6 header, SRH, inner GRE encapsulation and payload, the payload includes the first service message, and the inner GRE encapsulation includes the VPN identifier of the VPN service carried by the first service message.

17. The method according to any one of claims 1 to 16, characterized in that: The method further comprises: The first site edge receives the third service message; The first site edge encapsulates the path information of the second end-to-end path in the outer layer of the third service message to obtain a fourth service message; wherein the path information of the second end-to-end path includes third information identifying a second backbone network ingress device in the backbone network and fourth information identifying a second backbone network egress device in the backbone network, the ingress endpoint of the second end-to-end path is the first site edge, the egress endpoint of the second end-to-end path is the second site edge, the second end-to-end path passes through the second backbone network ingress device and the second backbone network egress device, the first site edge is multi-homed to access the first backbone network ingress device and the second backbone network ingress device, and the second site edge is multi-homed to access the first backbone network egress device and the second backbone network egress device; The first site edge sends the fourth service message through the second end-to-end path.

18. The method according to any one of claims 1 to 17, characterized in that: The first site edge accesses the first backbone network entry device through a software-defined wide area network SD-WAN tunnel or the Internet.

19. A method for forwarding traffic, characterized in that: The method comprises: A first backbone network ingress device in a backbone network receives a second service message from a first site edge edge, the payload of the second service message includes the first service message, and the outer layer of the first service message encapsulates path information of an end-to-end path between the first site edge and the second site edge; wherein the path information of the end-to-end path includes: first information identifying the first backbone network ingress device and second information identifying the first backbone network egress device in the backbone network, the ingress endpoint of the end-to-end path is the first site edge, the egress endpoint of the end-to-end path is the second site edge, the end-to-end path passes through the first backbone network ingress device and the first backbone network egress device, the first site edge accesses the backbone network through the first backbone network ingress device, and the second site edge accesses the backbone network through the first backbone network egress device; The first backbone network ingress device processes the second service message according to the first information to obtain a third service message; The first backbone network ingress device sends the third service message to the first backbone network egress device.

20. The method according to claim 19, characterized in that The second service message also includes service intention information.

21. The method according to claim 20, characterized in that The service intention information is carried in the metadata field of the second service message.

22. The method according to any one of claims 19 to 21, characterized in that: The end-to-end path is an SRv6 tunnel, the second service message includes an Internet Protocol version 6 IPv6 header and a segment routing header SRH, the destination address of the IPv6 header points to the first backbone network ingress device, and the SRH includes the first information and the second information.

23. The method according to claim 22, characterized in that The first information is the first endpoint segment identifier END.SID1 allocated by the first backbone network ingress device, the second information is the second endpoint segment identifier END.SID2 allocated by the first backbone network egress device, and the SRH also includes the IPv6 address of the second site edge.

24. The method according to claim 22, characterized in that The first information is the first endpoint segment identifier END.SID1 of the first backbone network entry device, and the second information is the endpoint segment identifier END.XSID with a cross-connection to the Layer 3 adjacency relationship array allocated by the first backbone network device egress device for the adjacency relationship between the first backbone network device egress device and the second site edge.

25. The method according to claim 23 or 24, characterized in that The operation of associating the first endpoint segment identifier END.SID1 includes: matching the upper layer overly SRv6 policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the END.SID1 in the SRH.

26. The method according to claim 23 or 24, characterized in that When the second service message includes service intent information, the operation associated with the first endpoint segment identifier END.SID1 includes: matching the upper layer overly SRv6 policy from the first backbone network ingress device to the first backbone network egress device according to the next hop SID of the END.SID1 in the SRH and the service intent information.

27. The method according to claim 25, characterized in that The processing, according to the first information, of the second service message to obtain a third service message includes: Matching a first overly SRv6 policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of END.SID1 in the SRH; The second service message is encapsulated by using the first overly SRv6 policy to obtain the third service message.

28. The method according to claim 25, characterized in that The processing, according to the first information, of the second service message to obtain a third service message includes: Matching a second overly SRv6 policy between the first backbone network ingress device and the first backbone network egress device according to the next hop SID of the END.SID1 in the SRH and the service intent information; The second service message is encapsulated by using the second overly SRv6 Policy to obtain the third service message.

29. The method according to any one of claims 19 to 21, characterized in that: The end-to-end path is a segment routing multi-protocol label switching traffic engineering strategy SR-MPLS TE policy, the second service message includes an MPLS label stack, the MPLS label stack includes the first information and the second information, the first information is the first node SID of the first backbone network ingress device, and the second information includes: the second node SID of the first backbone network egress device, and the adjacency segment identifier adj-SID allocated by the first backbone network device egress device to the adjacency relationship between the first backbone network device egress device and the second site edge.

30. The method according to claim 29, characterized in that The operation of associating the first node SID includes: An upper layer overly SR-MPLS TE policy between the first backbone network ingress device and the first backbone network egress device is matched according to the next hop SID of the first node SID in the label stack.

31. The method according to claim 29, characterized in that When the second service message includes service intent information, the operation of associating the first node SID includes: matching the upper layer overly SR-MPLS TE policy from the first backbone network ingress device to the first backbone network egress device according to the next hop SID of the first node SID in the label stack and the service intent information.

32. The method according to claim 30, characterized in that The processing, according to the first information, of the second service message to obtain a third service message includes: According to the next hop SID of the first node SID in the label stack, a first overly SR-MPLS TE policy between the first backbone network ingress device and the first backbone network egress device is matched; The second service message is encapsulated by using the first overly SR-MPLS TE policy to obtain the third service message.

33. The method according to claim 31, characterized in that The processing, according to the first information, of the second service message to obtain a third service message includes: According to the next hop SID of the first node SID in the label stack and the service intent information, a second overly SR-MPLS TE policy between the first backbone network ingress device and the first backbone network egress device is matched; The second service message is encapsulated by using the second overly SR-MPLS TE policy to obtain the third service message.

34. The method according to any one of claims 22 to 28, characterized in that The end-to-end path is a tunnel encapsulated based on the general network virtualization encapsulation GENEVE protocol, and the second service message is encapsulated using SRv6 in GENEVE.

35. The method according to any one of claims 22 to 28, characterized in that The end-to-end path is a tunnel encapsulated based on the Generic Routing Encapsulation (GRE) protocol, and the second service message includes SRv6 over GRE encapsulation.

36. The method according to claim 35, characterized in that The second service message includes: Outer IP header, User Datagram Protocol UDP header, outer GRE encapsulation, IPv6 header, SRH, inner GRE encapsulation and payload, the payload includes the first service message, and the inner GRE encapsulation includes the VPN identifier of the VPN service carried by the first service message.

37. The method according to any one of claims 19 to 36, characterized in that: The first site edge accesses the first backbone network entry device through a software-defined wide area network SD-WAN tunnel or the Internet.

38. A communication device, characterized in that: The device comprises: Transceiver unit and processing unit; The transceiver unit is used to perform the receiving and / or sending operations performed by the first site edge as described in any one of claims 1-18; the processing unit is used to perform operations other than the receiving and / or sending operations performed by the first site edge as described in any one of claims 1-18; or, The transceiver unit is used to perform the receiving and / or sending operations performed by the first backbone network access device as described in any one of claims 19-37; the processing unit is used to perform operations other than the receiving and / or sending operations performed by the first backbone network access device as described in any one of claims 19-37.

39. A communication device, characterized in that: include: Processor and memory; The memory is used to store instructions; The processor is used to execute the instructions so that the communication device executes the method according to any one of claims 1-37.

40. A communication system, characterized in that: The system comprises: A first site edge that executes the method described in any one of claims 1-18, and a first backbone network ingress device that executes the method described in any one of claims 19-37.

41. A computer-readable storage medium, characterized in that The method comprises instructions or computer programs, which, when executed on a processor, implement the method according to any one of claims 1 to 37.

Images