Information notification method and device

Abstract

The embodiment of the invention discloses an information notification method. The method can be applied to a first communication device serving as a first site edge. A first communication device can receive a first route notified by a second communication device, and obtain a first binding relationship between a second site edge and a first backbone network exit device according to the first route. Wherein the first route comprises that a first backbone network exit device in the backbone network is accessed to the backbone network, and a first site edge is accessed to the backbone network through a first backbone network entrance device. Therefore, by utilizing the scheme of the embodiment of the invention, the first site edge can obtain the first binding relationship, so that the end-to-end path from the first site edge to the second site edge can be subsequently arranged based on the first binding relationship, the end-to-end path obtained by arrangement is enabled to better meet service requirements, and correspondingly, the service efficiency is improved. The service quality provided by the service flow transmitted through the end-to-end path can be 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 202310726065.3 and invention name “A method and device for information notification”, 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 an information notification method and device. Background Art

[0003] With the development of communication technology, in some scenarios, business traffic needs to be transmitted across multiple network domains in the 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] Currently, in scenarios where business traffic needs to be transmitted across multiple network domains, the quality of service provided by the network for business traffic cannot meet business needs. Therefore, a solution is urgently needed to solve the above problem. Summary of the invention

[0005] The embodiments of the present application provide an information notification method and device, which can improve the service quality provided for business traffic in a scenario where business traffic needs to be transmitted across multiple network domains.

[0006] In the first aspect, an embodiment of the present application provides an information notification method, which can be applied to a first communication device as a first site edge. The first communication device can receive a first route announced by a second communication device, wherein the first route includes a first backbone network egress device in a backbone network accessing the backbone network, and the first site edge accessing the backbone network through a first backbone network entry device. After the first site edge receives the first route, the first binding relationship between the second site edge and the first backbone network egress device can be obtained according to the first route. The first site edge can use the first binding relationship to arrange an end-to-end path from the first site edge to the second site edge. It can be seen that, using the solution of the embodiment of the present application, the first site edge can obtain the first binding relationship between the second site edge and the first backbone network egress device of the second site edge accessing the backbone network, so as to facilitate the subsequent arrangement of the end-to-end path from the first site edge to the second site edge based on the first binding relationship, so that the arranged end-to-end path is more in line with business needs, and accordingly, the service quality provided by the business traffic transmitted through the end-to-end path can be improved.

[0007] In a possible implementation, after the first site edge obtains the first binding relationship, it can determine the first end-to-end path from the first site edge to the second site edge based on the first binding relationship, and the determined first end-to-end path passes through the first backbone network entry device and the first backbone network exit device. It can be seen that, using this solution, when arranging the end-to-end path, the first site edge can combine the information of the backbone network exit device bound to the opposite site edge (the second site edge), so that the arranged end-to-end path is more in line with business needs, and accordingly, it can improve the service quality provided by the business traffic transmitted through the end-to-end path.

[0008] In one possible implementation, the first information may include a first segment identifier (SID) assigned by the first backbone network egress device to the adjacency relationship between the first backbone network egress device and the second site edge, so that in the subsequent traffic forwarding stage, the message can be encapsulated based on the first SID, thereby performing traffic forwarding based on the first SID.

[0009] In a possible implementation, the first information may include the second SID of the first backbone network egress device, so that in the subsequent traffic forwarding stage, the message can be encapsulated based on the second SID, thereby performing traffic forwarding based on the second SID.

[0010] In one possible implementation, the first information may include the routing priority of the first backbone network export device, so that the first site edge can arrange the end-to-end path from the first site edge to the second site edge in combination with the routing priority, or, the first site edge can determine the end-to-end path for transmitting business traffic from the end-to-end path from the first site edge to the second site edge in combination with the routing priority.

[0011] In one possible implementation, the first information may include the load sharing weight of the first backbone network export device, so that the first site edge can determine the end-to-end path for transmitting business traffic from the end-to-end path from the first site edge to the second site edge in combination with the load sharing weight.

[0012] In a possible implementation, if the first site edge supports forwarding using Segment Routing Internet Protocol Version 6 (SRv6) technology, the first SID can be an SRv6 endpoint segment identifier (SRv6 END.X SID) with a cross-connection to a Layer 3 adjacency array, and the second SID can be an SRv6 endpoint segment identifier (SRv6 END.SID).

[0013] In a possible implementation, if the first site edge supports forwarding using Multi-Protocol Label Switching (MPLS) technology, the first SID may be an adjacency segment identifier (adj-SID), and the second SID may be a node SID (node ​​SID).

[0014] In one possible implementation, the second communication device may be a second site edge, in which case the first route may be a software-defined wide area network (SD-WAN) gateway information announcement route. The SD-WAN gateway information announcement route may be a route based on an SD-WAN address family or SD-WAN sub-address family announcement. In one example, the SD-WAN gateway information announcement route includes at least one type length value (TLV), and the at least one TLV carries the first information.

[0015] In one possible implementation, at least one TLV included in the SD-WAN gateway information announcement route may include a first TLV, and the first TLV is used to carry the first information. In a specific example, when the first information includes the first SID and / or the second SID, the value field of the first TLV is used to carry the first SID and / or the second SID in the first information. When the first information also includes the aforementioned routing priority, the first TLV may also include a priority sub-TLV for carrying the routing priority. When the first information also includes the aforementioned load sharing weight, the first TLV also includes a weight sub-TLV for carrying the load sharing weight.

[0016] In a possible implementation, the second communication device is the second site edge, and the first route is a virtual private network (VPN) route. In this case, the second site edge can notify the first site edge of the first information through the VPN route, thereby notifying the first information while notifying the VPN route.

[0017] In a possible implementation, the first information may be carried by a BGP path attribute in a VPN route. In a specific example, the first information may be carried by a first metadata path attribute in the VPN route.

[0018] In a possible implementation, the first route may also include business intent information. The business intent is used to indicate business intent (or business demand). The second communication device notifies the business intent information to the first site edge through the first route, so that in the traffic forwarding stage, the communication device forwarding the business traffic can forward it in combination with the business intent information, so that the business intent can be met.

[0019] In one possible implementation, the business intent information may include one or more information that can indicate the business intent. In one example, the business intent information may include quality of service parameters, and the quality of service parameters may include, but are not limited to, one or more parameters such as latency, packet loss, jitter, bandwidth utilization, and bit error rate. In another example, the business intent parameters may include gateway constraint information that needs to be satisfied by the end-to-end path from the first site edge to the second site edge, and the gateway constraint information includes, but is not limited to, gateways that need to be passed through and / or gateways that need to be detoured.

[0020] In a possible implementation, the business intent information may be carried by a BGP path attribute in the first route. In a specific example, the business intent information may be carried by a second Metadata Path Attribute in the first route. When the first route is a VPN route, the second Metadata Path Attribute and the aforementioned first Metadata Path Attribute may be the same Metadata Path Attribute. In this case, the first information and the business intent information may be carried by one Metadata Path Attribute. Of course, the second Metadata Path Attribute and the aforementioned first Metadata Path Attribute may also be different Metadata Path Attributes.

[0021] In a possible implementation, the second communication device is a first backbone network egress device. In this case, the first backbone network egress device may notify the first site edge of the first route through the first backbone network ingress device. Correspondingly, the first site edge may receive the first route notified by the first backbone network egress device through the first backbone network ingress device.

[0022] In one possible implementation, the first route announced by the first backbone network egress device to the first site edge may be a first SD-WAN gateway automatically discovered route. The first SD-WAN gateway automatically discovered route may be a route announced based on the SD-WAN address family or the SD-WAN sub-address family.

[0023] In one possible implementation, when the second site edge is multi-homed to the first backbone network export device and the second backbone network export device, the first site edge can also receive a second route announced by a third communication device, the second route includes second information of the second backbone network export device in the backbone network and an identifier of the second site edge, and the second site edge accesses the backbone network through the second backbone network export device; after the first site edge receives the second route, it can obtain the second binding relationship between the second site edge and the second backbone network export device according to the second route, so as to subsequently determine the second end-to-end path from the first site edge to the second site edge based on the second binding relationship.

[0024] In a possible implementation, the first site edge can also determine the routing priorities corresponding to the first backbone network export device and the second backbone network export device, respectively, so as to determine the forwarding path of the service traffic based on the routing priorities corresponding to the first backbone network export device and the second backbone network export device, respectively. As an example, the first site edge can determine the routing priority of the first backbone network export device according to its own configured routing strategy or in combination with the load condition of the first backbone network export device. As another example, the first site edge can determine the routing priority of the second backbone network export device according to its own configured routing strategy or in combination with the load condition of the second backbone network export device.

[0025] In a possible implementation, the first site edge can also determine the load sharing weights corresponding to the first backbone network export device and the second backbone network export device, respectively, so as to subsequently determine the forwarding path of the service traffic based on the load sharing weights corresponding to the first backbone network export device and the second backbone network export device, respectively. As an example, the first site edge can, for example, determine the load sharing weight of the first backbone network export device based on its own configured load sharing strategy or in combination with the load condition of the first backbone network export device. As another example, the first site edge can, for example, determine the load sharing weight of the second backbone network export device based on its own configured load sharing strategy or in combination with the load condition of the second backbone network export device.

[0026] In a possible implementation, after the first site edge obtains the second binding relationship, it can determine the first end-to-end path from the first site edge to the second site edge based on the second binding relationship, and the determined second end-to-end path passes through the first backbone network entry device and the second backbone network exit device. It can be seen that, using this solution, when arranging the end-to-end path, the first site edge can combine the information of the backbone network exit device bound to the opposite site edge (second site edge), so that the arranged end-to-end path is more in line with business needs, and accordingly, it can improve the service quality provided by the business traffic transmitted through the end-to-end path.

[0027] In a possible implementation, the first site edge can also receive a third route sent by the first backbone network entry device, and the third route is used to notify the third information of the first backbone network entry device. After the first site edge receives the third route, it can obtain the third binding relationship between the first site edge and the first backbone network entry device according to the third route. It can be seen that, using this solution, the first site edge can determine its own corresponding gateway through the received third route, without the need to manually configure its corresponding gateway on the first site edge.

[0028] In a possible implementation, the third route is the route automatically discovered by the second SD-WAN gateway. In this case, the first site edge can automatically discover the route through the second SD-WAN gateway to determine the third information of the gateway (i.e., the first backbone network entry device) for accessing the backbone network. The route automatically discovered by the second SD-WAN gateway can be a route announced based on the SD-WAN address family or the SD-WAN sub-address family.

[0029] In a possible implementation, the third route is a Border Gateway Protocol Link State (BGP linkstate, BGP LS) route. In this case, the first site edge can determine the third information of the gateway (i.e., the first backbone network entry device) for accessing the backbone network through BGP LS routing. Among them, the BGP LS route can be a route based on the BGP LS address family announcement.

[0030] In one possible implementation, the third information may include a third SID assigned by the first backbone network entry device to the adjacency relationship between the first backbone network entry device and the first site edge, so that in the subsequent traffic forwarding stage, the message is encapsulated based on the third SID, thereby using the third SID for traffic forwarding.

[0031] In a possible implementation, the third information may include the fourth SID of the first backbone network ingress device, so that in a subsequent traffic forwarding stage, the message is encapsulated based on the third SID, thereby using the third SID to forward traffic.

[0032] In a possible implementation, if the first site edge supports forwarding using the SRv6 technology, the third SID may be SRv6END.X SID, and the fourth SID may be SRv6 END.SID.

[0033] In a possible implementation manner, if the first site edge supports forwarding using the MPLS technology, the third SID may be an adj-SID, and the fourth SID may be a node SID.

[0034] In a possible implementation, the third route also includes intermediate gateway information, and the intermediate gateway information indicates at least one intermediate gateway between a backbone network entry device in the backbone network and an exit device in the backbone network, so that the first site edge can perform path orchestration based on the intermediate gateway. In one example, the first site edge can determine the gateway constraints that the end-to-end path needs to follow based on business requirements and the intermediate gateway. The gateway constraints mentioned here include gateways that need to be passed through and / or gateways that need to be bypassed. In a specific example, when the first site edge performs path orchestration based on business requirements, it can determine the gateways that the end-to-end path needs to pass through and / or the gateways that need to be bypassed from the intermediate gateways, so that the determined end-to-end path meets business requirements.

[0035] In a possible implementation, the first site edge can also receive a first service message. After receiving the first service message, the first site edge can 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. 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: fourth information identifying the first backbone network ingress device in the backbone network, and fifth information identifying the 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.

[0036] 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.

[0037] 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.

[0038] 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.

[0039] 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.

[0040] 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 fourth information and the fifth 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.

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

[0042] In a possible implementation, when the first SR policy is an SRv6 policy, the fourth information is END.SID1 of the first backbone network ingress device, and the fifth 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 relationship 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.

[0043] 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.

[0044] 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.

[0045] 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 fourth information and fifth information are carried by the MPLS label stack. For this case, the fourth information is the first node SID of the first backbone network ingress device, and the fifth information includes: the second node SID of the first backbone network egress device, and the first backbone network device egress device is assigned an adjacency segment identifier (adjacency SID, adj-SID) for the adjacency relationship between the first backbone network device egress device and the second site edge.

[0046] 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.

[0047] 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.

[0048] 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.

[0049] 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.

[0050] 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.

[0051] In a possible implementation, the first site edge edge can also receive a third service message, and encapsulate the path information of the third 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 third end-to-end path includes the sixth information identifying the second backbone network entry device in the backbone network and the seventh information identifying the second backbone network exit device in the backbone network, the entry point of the third end-to-end path is the first site edge, the exit point of the third end-to-end path is the second site edge, the third 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 third end-to-end path. It can be seen that, using this solution, the site edge can arrange the third 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.

[0052] 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.

[0053] In the second aspect, an embodiment of the present application provides an information notification method, which can be applied to a second communication device. The second communication device can obtain a first route, wherein the first route includes first information of a first backbone network export device in a backbone network and an identifier of a second site edge, and the second site edge accesses the backbone network through the first backbone network export device. After the second communication device obtains the first route, it can notify the first site edge of the first route, wherein the first site edge accesses the backbone network through the first backbone network entry device. After notifying the first route to the first site edge, the first site edge can obtain the first binding relationship between the second site edge and the first backbone network export device of the second site edge accessing the backbone network, so as to subsequently arrange the end-to-end path from the first site edge to the second site edge based on the first binding relationship, so that the arranged end-to-end path is more in line with business needs, and accordingly, the service quality provided by the business traffic transmitted through the end-to-end path can be improved.

[0054] In a possible implementation, the first information includes one or more of the following: a first segment identifier SID assigned by the first backbone network export device to the adjacency relationship between the first backbone network export device and the second site edge; a second SID of the first backbone network export device; a routing priority of the first backbone network export device; and a load sharing weight of the first backbone network export device.

[0055] In a possible implementation, the first SID is an endpoint segment identifier SRv6 END.X SID of Internet Protocol version 6 segment routing having a cross-connection to a layer 3 adjacency array, and the second SID is an Internet Protocol version 6 segment routing endpoint segment identifier SRv6END.SID; or, the first SID is an adjacency segment identifier adj-SID, and the second SID is a node SID.

[0056] In one possible implementation, the second communication device is the second site edge, and the first route includes: a software-defined wide area network SD-WAN gateway information announcement route, and the SD-WAN gateway information announcement route includes at least one type-length value TLV, and the at least one TLV carries the first information.

[0057] In one possible implementation, the SD-WAN gateway information announcement route includes a first TLV, the value field of the first TLV is used to carry the first SID and / or second SID in the first information, the first TLV also includes a priority sub-TLV and / or a weight sub-TLV, the priority sub-TLV is used to carry the routing priority in the first information, and the weight sub-TLV is used to carry the load sharing weight in the first information.

[0058] In a possible implementation manner, the second communication device is the second site edge, and the first route includes a virtual private network VPN route.

[0059] In a possible implementation manner, the VPN route includes a first metadata path attribute Metadata Path Attribute, and the first Metadata Path Attribute carries the first information.

[0060] In a possible implementation manner, the first route further includes: service intent information.

[0061] In a possible implementation, the service intent information includes one or more of the following: a gateway through which the service traffic needs to pass, a gateway through which the service traffic needs to bypass, and a quality of service parameter that needs to be met when transmitting the service traffic.

[0062] In a possible implementation manner, the first route includes a second Metadata Path Attribute, and the second Metadata Path Attribute includes the service intent information.

[0063] In a possible implementation, the second communication device is the first backbone network egress device, and the notifying the first route to the first site edge includes: notifying the first route to the first site edge through the first backbone network ingress device.

[0064] In one possible implementation, the first route includes: the first SD-WAN gateway automatically discovers the route.

[0065] In one possible implementation, the method also includes: notifying the first site edge of a second route, the second route including second information of a second backbone network export device in the backbone network and an identifier of the second site edge, and the second site edge accesses the backbone network through the second backbone network export device.

[0066] In a possible implementation, the second site edge can also receive a third route sent by the first backbone network egress device, and the third route is used to notify the third information of the first backbone network egress device; after the second site edge receives the third route, it can obtain the first binding relationship between the second site edge and the first backbone network egress device according to the third route. It can be seen that, using this solution, the second site edge can determine its own corresponding gateway through the received third route, without the need to manually configure its corresponding gateway on the first site edge.

[0067] In a possible implementation manner, the third information includes: a third SID allocated by the first backbone network egress device for the adjacency relationship between the first backbone network egress device and the second site edge, and / or a fourth SID of the first backbone network egress device.

[0068] In a possible implementation, if the second site edge is multi-homed to the first backbone network export device and the second backbone network export device, the second site edge can also receive a fourth route sent by the second backbone network export device, and the fourth route is used to notify the fourth information of the second backbone network export device; according to the fourth route, the second binding relationship between the second site edge and the second backbone network export device is obtained.

[0069] In one possible implementation, the second site edge can also determine the routing priorities corresponding to the first backbone network export device and the second backbone network export device respectively; and / or determine the load sharing weights corresponding to the first backbone network export device and the second backbone network export device respectively.

[0070] In one possible implementation, the third route is a route automatically discovered by the second SD-WAN gateway.

[0071] In a possible implementation manner, the third route is a BGP link state LS route, the BGP LS route includes a second TLV, and the second TLV indicates that the third route is used to notify third information of the first backbone network egress device.

[0072] In a possible implementation, the second TLV is a role announcement TLV, and the role announcement TLV indicates that the role of the first backbone network egress device is a gateway. The second site edge can parse the role TLV to determine that the device announcing the third route is its own gateway, thereby obtaining a first binding relationship between the second site edge and the first backbone network egress device.

[0073] In a possible implementation manner, the third route also includes intermediate gateway information, and the intermediate gateway information indicates at least one intermediate gateway between a backbone network ingress device in the backbone network and the first backbone network egress device.

[0074] In a possible implementation manner, the third route includes a third Metadata Path Attribute, and the third Metadata Path Attribute carries the intermediate gateway information.

[0075] In a possible implementation, after receiving the intermediate gateway information, the second site edge can determine the gateway constraint information in the service intent information based on the intermediate gateway information, and the gateway constraint information indicates the gateway constraint conditions that need to be followed to determine the path to reach the second site edge. As an example, after determining the gateway constraint information, the second site edge can notify the first site edge of the gateway constraint information, so that the forwarding device can forward the service traffic transmitted from the first site edge to the second site edge in the forwarding stage in combination with the gateway constraint information.

[0076] In a possible implementation, the gateway constraint condition includes: a gateway that needs to be passed through, and / or a gateway that needs to be detoured.

[0077] In the third aspect, an embodiment of the present application provides an information notification method, which can be applied to a first backbone network entry device in a backbone network, wherein the first backbone network entry device can receive a first route notified by a first backbone network exit device in the backbone network, and notify the first route to a first site edge. The first route includes information of the first backbone network exit device and an identifier of a second site edge, the second site edge accesses the backbone network through the first backbone network exit device, and the first site edge accesses the backbone network through the first backbone network entry device. After notifying the first route to the first site edge, the first site edge can obtain a first binding relationship between the second site edge and the first backbone network exit device of the second site edge accessing the backbone network, so as to subsequently arrange an end-to-end path from the first site edge to the second site edge based on the first binding relationship, so that the arranged end-to-end path is more in line with business requirements, and accordingly, the service quality provided by the business traffic transmitted through the end-to-end path can be improved.

[0078] In a possible implementation, the first backbone network device may also receive a second service packet from the first site edge, and the payload of the second service packet includes the first service packet. The outer layer of the first service packet 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. After receiving the second service packet, the first backbone network ingress device may process the second service packet according to the first information to obtain a third service packet, and send the third service packet to the first backbone network egress device to achieve forwarding of 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.

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

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

[0081] 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.

[0082] 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.

[0083] 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.

[0084] 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.

[0085] 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.

[0086] 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.

[0087] 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.

[0088] 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.

[0089] 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.

[0090] 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.

[0091] 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.

[0092] 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.

[0093] 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.

[0094] 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.

[0095] 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.

[0096] 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.

[0097] In the fourth aspect, an embodiment of the present application provides a route announcement method, which is applied to a site edge, and the method includes: receiving a first route sent by a first backbone network edge device, the first route is used to announce the first information of the first backbone network edge device, and the site edge accesses the backbone network through the first backbone network edge device; according to the first route, obtaining a first binding relationship between the site edge and the first backbone network edge device. It can be seen that, using this solution, the site edge can determine its own corresponding gateway through the received first route, without the need to manually configure its corresponding gateway on the site edge. The first backbone network edge device mentioned here can be a first backbone network egress device or a first backbone network ingress device.

[0098] In a possible implementation manner, the first information includes: a first SID allocated by the first backbone network edge device for an adjacency relationship between the first backbone network edge device and the site edge, and / or a second SID of the first backbone network edge device.

[0099] In a possible implementation, the method also includes: receiving a second route sent by a second backbone network edge device, the second route being used to notify second information of the second backbone network edge device, and the site edge accessing the backbone network through the second backbone network edge device; and obtaining a second binding relationship between the site edge and the second backbone network edge device according to the second route.

[0100] In a possible implementation, the method further includes: determining the routing priorities corresponding to the first backbone network edge device and the second backbone network edge device respectively; and / or determining the load sharing weights corresponding to the first backbone network edge device and the second backbone network edge device respectively.

[0101] In one possible implementation, the first route is an SD-WAN gateway automatic discovery route.

[0102] In a possible implementation manner, the first route is a BGP link state LS route, and the BGP LS route includes a TLV, where the TLV indicates that the first route is used to notify the first information of the first backbone network edge device.

[0103] In a possible implementation manner, the TLV is a role announcement TLV, and the role announcement TLV indicates that the role of the backbone network edge device is a gateway.

[0104] In a possible implementation manner, the first route also includes intermediate gateway information, and the intermediate gateway information indicates at least one intermediate gateway between a backbone network ingress device and a backbone network egress device in the backbone network.

[0105] In a possible implementation manner, the first route includes a Metadata Path Attribute, and the Metadata Path Attribute carries the intermediate gateway information.

[0106] In a possible implementation, the method further includes: determining gateway constraint information in the service intent information according to the intermediate gateway information, wherein the gateway constraint information indicates a gateway constraint condition that needs to be followed to determine a path to reach the site edge.

[0107] In a possible implementation, the gateway constraint condition includes: a gateway that needs to be passed through, and / or a gateway that needs to be detoured.

[0108] In the fifth aspect, an embodiment of the present application provides a route announcement method, which is applied to a backbone network edge device. The backbone network edge device mentioned here can be a backbone network egress device or a backbone network ingress device. The method comprises: obtaining a route, the route is used to announce the information of the backbone network edge device; sending the route to the site edge, and the site edge accesses the backbone network through the backbone network edge device. It can be seen that, using this solution, the backbone network edge device can announce its own information to the site edge through the route, and the site edge can determine its corresponding gateway through the received route, without the need to manually configure its corresponding gateway on the site edge.

[0109] In a possible implementation manner, the information includes: a first SID allocated by the backbone network edge device for the adjacency relationship between the backbone network edge device and the site edge, and / or a second SID of the backbone network edge device.

[0110] In one possible implementation, the route is automatically discovered by the SD-WAN gateway.

[0111] In a possible implementation manner, the route is a BGP link state LS route, and the BGP LS route includes a TLV, where the TLV indicates that the route is used to notify information of the backbone network edge device.

[0112] In a possible implementation manner, the TLV is a role announcement TLV, and the role announcement TLV indicates that the role of the backbone network edge device is a gateway.

[0113] In a possible implementation manner, the route further includes intermediate gateway information, and the intermediate gateway information indicates at least one intermediate gateway between a backbone network ingress device and a backbone network egress device in the backbone network.

[0114] In a possible implementation manner, the route includes a Metadata Path Attribute, and the Metadata Path Attribute carries the intermediate gateway information.

[0115] In a sixth aspect, an embodiment of the present application provides a communication device, which may include a transceiver unit and / or a processing unit; the transceiver unit is used to perform a receiving and / or sending operation; the processing unit is used to perform operations other than the receiving and / or sending operations. The transceiver unit includes a receiving unit and / or a sending unit, the receiving unit is used to perform a receiving operation, and the sending unit is used to perform a sending operation.

[0116] In a specific example: the communication device may include a receiving unit and a processing unit. In this case, the communication device can be used to execute the method described in the first aspect and any one of the first aspect above, or to execute the method described in the fourth aspect and any one of the fourth aspect above.

[0117] When the communication device can be used to execute the method described in the first aspect and any one of the first aspects above:

[0118] A receiving unit is used to receive a first route announced by a second communication device, wherein the first route includes first information of a first backbone network export device in the backbone network and an identifier of a second site edge, the second site edge accesses the backbone network through the first backbone network export device, and the first site edge accesses the backbone network through a first backbone network import device; a processing unit is used to obtain a first binding relationship between the second site edge and the first backbone network export device according to the first route.

[0119] In a possible implementation, the processing unit is further used to: determine a first end-to-end path from the first site edge to the second site edge based on the first binding relationship, and the first end-to-end path passes through the first backbone network ingress device and the first backbone network egress device.

[0120] In a possible implementation, the first information includes one or more of the following: a first segment identifier SID assigned by the first backbone network export device to the adjacency relationship between the first backbone network export device and the second site edge; a second SID of the first backbone network export device; a routing priority of the first backbone network export device; and a load sharing weight of the first backbone network export device.

[0121] In a possible implementation, the first SID is an endpoint segment identifier SRv6 END.X SID of Internet Protocol version 6 segment routing having a cross-connection to a layer 3 adjacency array, and the second SID is an Internet Protocol version 6 segment routing endpoint segment identifier SRv6END.SID; or, the first SID is an adjacency segment identifier adj-SID, and the second SID is a node SID.

[0122] In one possible implementation, the second communication device is the second site edge, and the first route includes: a software-defined wide area network SD-WAN gateway information announcement route, and the SD-WAN gateway information announcement route includes at least one type-length value TLV, and the at least one TLV carries the first information.

[0123] In one possible implementation, the SD-WAN gateway information announcement route includes a first TLV, the value field of the first TLV is used to carry the first SID and / or second SID in the first information, the first TLV also includes a priority sub-TLV and / or a weight sub-TLV, the priority sub-TLV is used to carry the routing priority in the first information, and the weight sub-TLV is used to carry the load sharing weight in the first information.

[0124] In a possible implementation manner, the second communication device is the second site edge, and the first route includes a virtual private network VPN route.

[0125] In a possible implementation manner, the VPN route includes a first metadata path attribute Metadata Path Attribute, and the first Metadata Path Attribute carries the first information.

[0126] In a possible implementation manner, the first route further includes: service intent information.

[0127] In a possible implementation, the service intention information includes one or more of the following: a gateway that the first end-to-end path needs to pass through, a gateway that the first end-to-end path needs to bypass, and a quality of service parameter.

[0128] In a possible implementation manner, the first route includes a second Metadata Path Attribute, and the second Metadata Path Attribute includes the service intent information.

[0129] In a possible implementation manner, the second communication device is the first backbone network egress device, and the receiving unit is used to: receive the first route announced by the first backbone network egress device through the first backbone network ingress device.

[0130] In one possible implementation, the first route includes: the first SD-WAN gateway automatically discovers the route.

[0131] In a possible implementation, the receiving unit is also used to: receive a second route announced by a third communication device, the second route including second information of a second backbone network export device in the backbone network and an identifier of the second site edge, and the second site edge accesses the backbone network through the second backbone network export device; the processing unit is also used to obtain a second binding relationship between the second site edge and the second backbone network export device according to the second route.

[0132] In a possible implementation, the processing unit is further used to: determine the routing priorities corresponding to the first backbone network egress device and the second backbone network egress device respectively; and / or determine the load sharing weights corresponding to the first backbone network egress device and the second backbone network egress device respectively.

[0133] In a possible implementation, the processing unit is further used to: determine, based on the second binding relationship, a second end-to-end path from the first site edge to the second site edge, wherein the second end-to-end path passes through the first backbone network ingress device and the second backbone network egress device.

[0134] In a possible implementation, the receiving unit is further used to: receive a third route sent by the first backbone network entry device, and the third route is used to notify the third information of the first backbone network entry device; the processing unit is further used to: obtain a third binding relationship between the first site edge and the first backbone network entry device according to the third route.

[0135] In one possible implementation, the third route is the second SD-WAN gateway automatic discovery route or the BGP link state LS route.

[0136] In a possible implementation manner, the third information includes: a third SID allocated by the first backbone network entry device for the adjacency relationship between the first backbone network entry device and the first site edge, and / or a fourth SID of the first backbone network entry device.

[0137] In a possible implementation manner, the third route further includes intermediate gateway information, where the intermediate gateway information indicates at least one intermediate gateway between the first backbone network ingress device and the egress device in the backbone network.

[0138] In a possible implementation manner, the device further includes a sending unit. For this situation:

[0139] The receiving unit is also used to receive a first business message; the processing unit is also used to encapsulate the path information of the first end-to-end path in the outer layer of the first business message to obtain a second business message; wherein the path information of the first end-to-end path includes fourth information identifying a first backbone network entry device in the backbone network and fifth 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 business message through the first end-to-end path.

[0140] 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.

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

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

[0143] 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.

[0144] 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 fourth information and the fifth information.

[0145] In a possible implementation, the fourth information is the first endpoint segment identifier END.SID1 of the first backbone network entry device, the fifth 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.

[0146] In a possible implementation, the fourth information is the first endpoint segment identifier END.SID1 of the first backbone network ingress device, and the fifth 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.

[0147] 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.

[0148] 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.

[0149] 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 fourth information and the fifth information, the fourth information is the first node SID of the first backbone network ingress device, and the fifth 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.

[0150] 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.

[0151] 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.

[0152] 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.

[0153] 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.

[0154] 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.

[0155] In a possible implementation, the receiving unit is further used to receive a third service message; the processing unit is further used to encapsulate path information of a third end-to-end path in an outer layer of the third service message to obtain a fourth service message; wherein the path information of the third end-to-end path includes sixth information identifying a second backbone network ingress device in the backbone network and seventh information identifying a second backbone network egress device in the backbone network, the ingress endpoint of the third end-to-end path is the first site edge, the egress endpoint of the third end-to-end path is the second site edge, the third 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 third end-to-end path.

[0156] 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.

[0157] When the communication device can be used to execute the method described in the fourth aspect and any one of the fourth aspects above:

[0158] A receiving unit is used to receive a first route sent by a first backbone network edge device, where the first route is used to notify the first information of the first backbone network edge device, and the site edge accesses the backbone network through the first backbone network edge device; and a processing unit is used to obtain a first binding relationship between the site edge and the first backbone network edge device according to the first route.

[0159] In a possible implementation manner, the first information includes: a first SID allocated by the first backbone network edge device for an adjacency relationship between the first backbone network edge device and the site edge, and / or a second SID of the first backbone network edge device.

[0160] In a possible implementation, the receiving unit is also used to: receive a second route sent by a second backbone network edge device, the second route is used to notify the second information of the second backbone network edge device, and the site edge accesses the backbone network through the second backbone network edge device; the processing unit is also used to obtain a second binding relationship between the site edge and the second backbone network edge device according to the second route.

[0161] In a possible implementation, the processing unit is further used to: determine the routing priorities corresponding to the first backbone network edge device and the second backbone network edge device respectively; and / or determine the load sharing weights corresponding to the first backbone network edge device and the second backbone network edge device respectively.

[0162] In one possible implementation, the first route is an SD-WAN gateway automatic discovery route.

[0163] In a possible implementation manner, the first route is a BGP link state LS route, and the BGP LS route includes a TLV, where the TLV indicates that the first route is used to notify the first information of the first backbone network edge device.

[0164] In a possible implementation manner, the TLV is a role announcement TLV, and the role announcement TLV indicates that the role of the backbone network edge device is a gateway.

[0165] In a possible implementation manner, the first route also includes intermediate gateway information, and the intermediate gateway information indicates at least one intermediate gateway between a backbone network ingress device and a backbone network egress device in the backbone network.

[0166] In a possible implementation manner, the first route includes a Metadata Path Attribute, and the Metadata Path Attribute carries the intermediate gateway information.

[0167] In a possible implementation, the processing unit is further used to: determine gateway constraint information in the service intent information based on the intermediate gateway information, where the gateway constraint information indicates gateway constraint conditions that need to be followed to determine a path to reach the site edge.

[0168] In a possible implementation, the gateway constraint condition includes: a gateway that needs to be passed through, and / or a gateway that needs to be detoured.

[0169] In another specific example: the communication device may include a processing unit and a sending unit. In this case, the communication device can be used to execute the method described in the second aspect and any one of the second aspect above, or to execute the method described in the fifth aspect and any one of the fifth aspect above.

[0170] When the communication device can be used to execute the method described in the second aspect and any one of the second aspects above:

[0171] A processing unit is used to obtain a first route, wherein the first route includes first information of a first backbone network exit device in the backbone network and an identifier of a second site edge, and the second site edge accesses the backbone network through the first backbone network exit device; a sending unit is used to notify the first site edge of the first route, and the first site edge accesses the backbone network through the first backbone network entry device.

[0172] In a possible implementation, the first information includes one or more of the following: a first segment identifier SID assigned by the first backbone network export device to the adjacency relationship between the first backbone network export device and the second site edge; a second SID of the first backbone network export device; a routing priority of the first backbone network export device; and a load sharing weight of the first backbone network export device.

[0173] In a possible implementation, the first SID is an endpoint segment identifier SRv6 END.X SID of Internet Protocol version 6 segment routing having a cross-connection to a layer 3 adjacency array, and the second SID is an Internet Protocol version 6 segment routing endpoint segment identifier SRv6END.SID; or, the first SID is an adjacency segment identifier adj-SID, and the second SID is a node SID.

[0174] In one possible implementation, the second communication device is the second site edge, and the first route includes: a software-defined wide area network SD-WAN gateway information announcement route, and the SD-WAN gateway information announcement route includes at least one type-length value TLV, and the at least one TLV carries the first information.

[0175] In one possible implementation, the SD-WAN gateway information announcement route includes a first TLV, the value field of the first TLV is used to carry the first SID and / or second SID in the first information, the first TLV also includes a priority sub-TLV and / or a weight sub-TLV, the priority sub-TLV is used to carry the routing priority in the first information, and the weight sub-TLV is used to carry the load sharing weight in the first information.

[0176] In a possible implementation manner, the second communication device is the second site edge, and the first route includes a virtual private network VPN route.

[0177] In a possible implementation manner, the VPN route includes a first metadata path attribute Metadata Path Attribute, and the first Metadata Path Attribute carries the first information.

[0178] In a possible implementation manner, the first route further includes: service intent information.

[0179] In a possible implementation, the service intent information includes one or more of the following: a gateway through which the service traffic needs to pass, a gateway through which the service traffic needs to bypass, and a quality of service parameter that needs to be met when transmitting the service traffic.

[0180] In a possible implementation manner, the first route includes a second Metadata Path Attribute, and the second Metadata Path Attribute includes the service intent information.

[0181] In a possible implementation, the second communication device is the first backbone network egress device, and the sending unit is used to: notify the first route to the first site edge through the first backbone network ingress device.

[0182] In one possible implementation, the first route includes: the first SD-WAN gateway automatically discovers the route.

[0183] In a possible implementation, the sending unit is also used to: notify the first site edge of a second route, wherein the second route includes second information of a second backbone network export device in the backbone network and an identifier of the second site edge, and the second site edge accesses the backbone network through the second backbone network export device.

[0184] In one possible implementation, the device also includes: a receiving unit, used to receive a third route sent by the first backbone network export device, and the third route is used to notify the third information of the first backbone network export device; the processing unit is also used to obtain the first binding relationship between the second site edge and the first backbone network export device according to the third route.

[0185] In a possible implementation manner, the third information includes: a third SID allocated by the first backbone network egress device for the adjacency relationship between the first backbone network egress device and the second site edge, and / or a fourth SID of the first backbone network egress device.

[0186] In a possible implementation, the receiving unit is also used to: receive a fourth route sent by the second backbone network export device, and the fourth route is used to announce the fourth information of the second backbone network export device; the processing unit is also used to obtain the second binding relationship between the second site edge and the second backbone network export device according to the fourth route.

[0187] In a possible implementation, the processing unit is further used to: determine the routing priorities corresponding to the first backbone network egress device and the second backbone network egress device respectively; and / or determine the load sharing weights corresponding to the first backbone network egress device and the second backbone network egress device respectively.

[0188] In one possible implementation, the third route is a route automatically discovered by the second SD-WAN gateway.

[0189] In a possible implementation manner, the third route is a BGP link state LS route, the BGP LS route includes a second TLV, and the second TLV indicates that the third route is used to notify third information of the first backbone network egress device.

[0190] In a possible implementation manner, the second TLV is a role announcement TLV, and the role announcement TLV indicates that the role of the first backbone network egress device is a gateway.

[0191] In a possible implementation manner, the third route also includes intermediate gateway information, and the intermediate gateway information indicates at least one intermediate gateway between a backbone network ingress device in the backbone network and the first backbone network egress device.

[0192] In a possible implementation manner, the third route includes a third Metadata Path Attribute, and the third Metadata Path Attribute carries the intermediate gateway information.

[0193] In a possible implementation, the processing unit is further used to: determine gateway constraint information in the service intent information based on the intermediate gateway information, where the gateway constraint information indicates gateway constraint conditions that need to be followed to determine a path to reach the second site edge.

[0194] In a possible implementation, the gateway constraint condition includes: a gateway that needs to be passed through, and / or a gateway that needs to be detoured.

[0195] When the communication device can be used to execute the method described in the fifth aspect and any one of the fifth aspects above:

[0196] A processing unit is used to obtain a route, wherein the route is used to notify information of the backbone network edge device; a sending unit is used to send the route to a site edge, wherein the site edge accesses the backbone network through the backbone network edge device.

[0197] In a possible implementation manner, the information includes: a first SID allocated by the backbone network edge device for the adjacency relationship between the backbone network edge device and the site edge, and / or a second SID of the backbone network edge device.

[0198] In one possible implementation, the route is automatically discovered by the SD-WAN gateway.

[0199] In a possible implementation manner, the route is a BGP link state LS route, and the BGP LS route includes a TLV, where the TLV indicates that the route is used to notify information of the backbone network edge device.

[0200] In a possible implementation manner, the TLV is a role announcement TLV, and the role announcement TLV indicates that the role of the backbone network edge device is a gateway.

[0201] In a possible implementation manner, the route further includes intermediate gateway information, and the intermediate gateway information indicates at least one intermediate gateway between a backbone network ingress device and a backbone network egress device in the backbone network.

[0202] In a possible implementation manner, the route includes a Metadata Path Attribute, and the Metadata Path Attribute carries the intermediate gateway information.

[0203] In another specific example: the communication device may include a receiving unit and a sending unit. In this case, the communication device may be used to execute the method described in the third aspect and any one of the third aspects.

[0204] A receiving unit is used to receive a first route announced by a first backbone network export device in the backbone network, wherein the first route includes information of the first backbone network export device and an identifier of a second site edge, wherein the second site edge accesses the backbone network through the first backbone network export device, and the first site edge accesses the backbone network through the first backbone network import device; and a sending unit is used to announce the first route to the first site edge.

[0205] In a possible implementation manner, the communication device further includes a processing unit. For this situation:

[0206] The receiving unit is also used to receive a second service message from the 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; 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 also used to send the third service message to the first backbone network egress device.

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

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

[0209] 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.

[0210] 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.

[0211] 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.

[0212] 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.

[0213] 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.

[0214] 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.

[0215] 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.

[0216] 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.

[0217] 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.

[0218] 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.

[0219] 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.

[0220] 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.

[0221] 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.

[0222] 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.

[0223] 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.

[0224] 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.

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

[0226] The memory is used to store instructions; the processor is used to execute the instructions, so that the communication device performs the method described in the first aspect and any one of the first aspect, or the communication device performs the method described in the second aspect and any one of the second aspect, or the communication device performs the method described in the third aspect and any one of the third aspect, or the communication device performs the method described in the fourth aspect and any one of the fourth aspect, or the communication device performs the method described in the fifth aspect and any one of the fifth aspect.

[0227] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, comprising 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 aspects is implemented, or the method described in the second aspect and any one of the second aspects is implemented, or the method described in the third aspect and any one of the third aspects is implemented, or the method described in the fourth aspect and any one of the fourth aspects is implemented, or the method described in the fifth aspect and any one of the fifth aspects is implemented.

[0228] In the ninth 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, or implements the method described in the third aspect and any one of the third aspects, or implements the method described in the fourth aspect and any one of the fourth aspects, or implements the method described in the fifth aspect and any one of the fifth aspects.

[0229] In a tenth aspect, an embodiment of the present application provides a communication system, the communication system comprising:

[0230] A first communication device executing the method described in the first aspect and any one of the first aspect, and a second communication device executing the method described in the second aspect and any one of the second aspect; or,

[0231] A site edge that executes the method described in the fourth aspect and any one of the fourth aspects, and a backbone network edge device that executes the method described in the fifth aspect and any one of the fifth aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0232] 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.

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

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

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

[0236] Figure 2a A schematic diagram of the structure of MP_REACH_NLRI provided in an embodiment of the present application;

[0237] Figure 2b A schematic diagram of the structure of a link state NLRI is shown;

[0238] Figure 3 A signaling interaction diagram of an information notification method provided in an embodiment of the present application;

[0239] Figure 4a A schematic diagram of the structure of MP_REACH_NLRI provided in an embodiment of the present application;

[0240] Figure 4b A schematic diagram of the structure of a routing priority sub-TLV provided in an embodiment of the present application;

[0241] Figure 4c A schematic diagram of the structure of a weight sub-TLV provided in an embodiment of the present application;

[0242] Figure 4d A schematic diagram of the structure of a sub-TLV provided in an embodiment of the present application;

[0243] Figure 4e A schematic diagram of the structure of another seed TLV provided in an embodiment of the present application;

[0244] Figure 4f A schematic diagram of the structure of another sub-TLV provided in an embodiment of the present application;

[0245] Figure 5 A signaling interaction diagram of an information notification method provided in an embodiment of the present application;

[0246] Figure 6 A schematic diagram of the structure of a sub-TLV1 included in a Metadata Path Attribute2 provided in an embodiment of the present application;

[0247] Figure 7 A signaling interaction diagram of an information notification method provided in an embodiment of the present application;

[0248] Figure 8 A schematic diagram of the structure of another MP_REACH_NLRI provided in an embodiment of the present application;

[0249] Fig. 9 A signaling interaction diagram of a route announcement method provided in an embodiment of the present application;

[0250] Fig.10 A schematic diagram of the structure of an intermediate gateway sub-TLV provided in an embodiment of the present application;

[0251] Fig.11 A signaling interaction diagram of another route announcement method provided in an embodiment of the present application;

[0252] Fig.12a A schematic diagram of the structure of a role announcement TLV provided in an embodiment of the present application;

[0253] Figure 12b A schematic diagram of the structure of an adjacency relationship SID TLV provided in an embodiment of the present application;

[0254] Fig.12c A schematic diagram of the structure of a node SID TLV provided in an embodiment of the present application;

[0255] Fig.13 A signaling interaction diagram of a method for forwarding traffic provided in an embodiment of the present application;

[0256] Fig.14a A schematic diagram of the structure of SRv6 over GRE encapsulation provided in an embodiment of the present application;

[0257] Fig.14b A schematic diagram of the structure of an MPLS over GRE encapsulation provided in an embodiment of the present application;

[0258] Fig.14c A schematic diagram of the structure of an SRv6 in GENEVE package provided in an embodiment of the present application;

[0259] Fig.14d A schematic diagram of the structure of an SRv6 over GENEVE encapsulation provided in an embodiment of the present application;

[0260] Fig.14eA schematic diagram of the structure of an MPLS in GENEVE encapsulation provided in an embodiment of the present application;

[0261] Fig.15a A schematic diagram of a scenario of a traffic forwarding method provided in an embodiment of the present application;

[0262] Fig.15b A schematic diagram of another traffic forwarding method provided in an embodiment of the present application;

[0263] Fig.15c A schematic diagram of another traffic forwarding method provided in an embodiment of the present application;

[0264] Fig.15d A schematic diagram of a scenario of a traffic forwarding method provided in an embodiment of the present application;

[0265] Fig.15e A schematic diagram of another traffic forwarding method provided in an embodiment of the present application;

[0266] Fig.16 A flowchart of an information notification method provided in an embodiment of the present application;

[0267] Fig.17 A flowchart of another information notification method provided in an embodiment of the present application;

[0268] Fig.18 A flowchart of an information notification method provided in an embodiment of the present application;

[0269] Fig.19 A flowchart of another information notification method provided in an embodiment of the present application;

[0270] Fig. 20 A flowchart of another information notification method provided in an embodiment of the present application;

[0271] Fig.21a A schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0272] Figure 21b A schematic diagram of the structure of another communication device provided in an embodiment of the present application;

[0273] Fig.21c A schematic diagram of the structure of another communication device provided in an embodiment of the present application;

[0274] Fig. 22 A schematic diagram of the structure of another communication device provided in an embodiment of the present application;

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

[0276] The embodiments of the present application provide an information notification method and device, which can improve the service quality provided for business traffic in a scenario where business traffic needs to be transmitted across multiple network domains.

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

[0278] 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.

[0279] 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.

[0280] 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:

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

[0282] 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.

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

[0284] 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.

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

[0286] In the embodiment of the present application, the backbone network may 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 may include a single operator network, a hybrid operator network, or a self-built dedicated line network, which is not specifically limited in the embodiment of the present application. 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.

[0287] like Figure 1b As shown, the backbone network 400 includes: Internet service provider (ISP) network 1 (referred to as ISP1), ISP2, ISP3 and a self-built dedicated line network. Figure 1b The connection method between network devices in the network architecture shown is not described in detail here. 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.

[0288] Currently, when service traffic needs to be transmitted across multiple network domains, the quality of service provided by the network for service traffic cannot meet the requirements. One specific reason is that when the site edge arranges the forwarding path for the service, it cannot flexibly select the backbone network POP used by the remote site edge to access the backbone network, and it cannot select the egress link of the backbone network POP to connect to the remote site edge. Figure 1b Take the following scenario as an example:

[0289] At present, the service quality obtained by the business traffic sent by site edge1 to site edge2 when it is transmitted in the network cannot meet the requirements. This is because when Edge1 arranges the transmission path for the business traffic, it cannot flexibly choose to transmit the business traffic to site edge2 via POP4 connected to site edge2, or to transmit the business traffic to site edge2 via POP9 connected to site edge2.

[0290] When the site edge arranges the forwarding path for the service, the reason why it cannot flexibly select the backbone network POP used by the remote site edge to access the backbone network is that the site edge does not know the information of the backbone network POP used by the remote site edge to access the backbone network.

[0291] In view of this, an embodiment of the present application provides an information notification method and device, which enables the site edge to obtain the binding relationship between the remote site edge and the backbone network POP used by the remote site edge to access the backbone network, so that when the site edge arranges the forwarding path for the service, it can flexibly select the backbone network POP used by the remote site edge to access the backbone network, thereby improving the service quality provided to the service.

[0292] Next, the information notification method provided in the embodiment of the present application is introduced in conjunction with the accompanying drawings.

[0293] Before introducing the information notification method provided in the embodiment of the present application, the routing notification method between network devices is first introduced.

[0294] In one example, two communication devices may communicate with each other via Multi-Protocol Extensions for BGP (MP-BGP). Figure 1a Taking the example of edge2 notifying a route to edge1, edge2 sends BGP message 1 to edge1. BGP message 1 includes MP_REACH_NLRI, and MP_REACH_NLRI is used to carry the route information notified by edge2 to edge1.

[0295] In one example, the structure of MP_REACH_NLRI is as follows Figure 2a As shown, Figure 2a A schematic diagram of the structure of MP_REACH_NLRI provided in an embodiment of the present application. Figure 2aAs shown, the MP_REACH_NLRI includes an address family identifier (AFI), a subsequent address family identifier (SAFI), a next hop information length field, a next hop information field, and a network reachability information field.

[0296] As an example, the AFI field can identify the network layer protocol, for example, the value of the AFI field is 1 to identify IPv4, the value of the AFI field is 2 to identify IPv6, and the value of the AFI field can refer to the relevant description of the address family number in the request for comments (RFC) 1700, which is not described in detail here. The SAFI field identifies the type of the sub-address family, for example, the value of the SAFI field is 1 to identify unicast, the value of the SAFI field is 2 to identify multicast, the value of the SAFI field is 74 to identify SD-WAN, and the value of the SAFI field is 128 to identify a virtual private network (VPN).

[0297] In an example, the aforementioned next-hop network address may refer to the network address of the next device on the path to the destination device.

[0298] In an example, the NLRI field may include one or more NLRIs, each NLRI includes a length field and an NLRI value field, and the specific content of the NLRI value may be determined based on a combination of the AFI field and the SAFI field.

[0299] When the AFI value is 1 and the SAFI value is 1, the NLRI information field of MP_REACH_NLRI carries the Internet Protocol Version 4 (IPv4) unicast route;

[0300] When the AFI value is 1 and the SAFI value is 128, the VPNv4 routes carried in the NLRI information field of MP_REACH_NLRI;

[0301] When the AFI value is 1 and the SAFI value is 4, the BGP label route carried in the NLRI information field of MP_REACH_NLRI;

[0302] When the AFI value is 1 and the SAFI value is 74, the NLRI information field of MP_REACH_NLRI carries the IPv4 SD-WAN address family information;

[0303] When the AFI value is 2 and the SAFI value is 74, the NLRI information field of MP_REACH_NLRI carries the IPv6 SD-WAN address family information.

[0304] The NLRI information field includes a route type field, a length field, and a type specific value field, wherein the route type field is used to indicate the route type, the length field is the length of the type specific value field, and the type specific value field is used to carry a value related to the type corresponding to the route type field.

[0305] In one example, when the NLRI information field of the MP_REACH_NLRI carries IPv4 SD-WAN address family information or IPv6 SD-WAN address family information, if the value of the type field is 1, the NLRI information field can be used to carry SD-WAN transport network port (transport network port, TNP) routing information. The information about TNP routing is not described in detail here.

[0306] In one example, the routing type field in the NLRI information field may also be an NLRI type field. In a specific example, if the NLRI information field is used to carry one type of routing information, the NLRI information field may include an NLRI type field; if the NLRI information field is used to carry multiple types of routing information, the NLRI information field may include a routing type field.

[0307] In another example, two communication devices can use the multi-protocol extension BGP-LS to advertise routes. BGP-LS introduces a series of new NLRs based on the original BGP to carry information related to links, nodes, and IPv4 prefixes or IPv6 prefixes. This new NLRI is called link-state NLRI. In one example, BGP-LS uses the MP_REACH_NLRI attribute as a container for the link-state NLRI, that is, the link-state NLRI is carried in the BGP Update message as a MP_REACH_NLRI attribute. See Figure 2b , Figure 2b FIG. 4 shows a schematic diagram of the structure of a link state NLRI. Figure 2b As shown, the link state NLRI includes an NLRI type field, a total NLRI length field and a link-state NLRI field.

[0308] The NLRI type field is used to indicate the NLRI type;

[0309] The total NLRI length field indicates the length of the entire NLRI;

[0310] The link-state NLRI field is used to carry specific content, and the content of the link-state NLRI field is determined according to the value of the NLRI type field. Specifically, the content of the link-state NLRI field can be understood by referring to the following Table 1.

[0311] Table 1

[0312] NLRI Type Value Link-State NLRI Contents 1 Node NLRI 2 Link NLRI 3 IPv4 Topology Prefix NLRI 4 IPv6 Topology Prefix NLRI

[0313] Next, the information notification method provided in the embodiment of the present application is introduced in conjunction with the accompanying drawings.

[0314] See also Figure 3 , this figure is a signaling interaction diagram of an information notification method provided in an embodiment of the present application.

[0315] Figure 3 The information notification method 100 shown can be applied to Figure 1a or Figure 1b When the method 100 is applied to Figure 1a In the application scenario shown, the backbone network egress device 1 in the method 100 may correspond to Figure 1a GW2 shown, the backbone network egress device 2 in method 100 may correspond to Figure 1a GW4 shown. When the method 100 is applied to Figure 1b In the application scenario shown, the backbone network egress device 1 in the method 100 may correspond to Figure 1b The POP4 shown, the backbone network egress device 2 in the method 100 may correspond to Figure 1b The POP 9 shown. The method 100 may include, for example, the following S101-S104.

[0316] S101: Site edge2 obtains route 1, which is the SD-WAN gateway information announcement route. Route 1 includes the identifier of site edge2 and information 1 of backbone network export device 1. Site edge2 accesses the backbone network through backbone network export device 1.

[0317] In the embodiment of the present application, the site edge2 can generate the route 1 based on the identifier of the site edge2 and the information 1 of the backbone network egress device 1.

[0318] In the embodiment of the present application, the identifier of the site edge2 may be the IP address of the site edge2.

[0319] In the embodiment of the present application, the information 1 of the backbone network egress device 1 at least includes an identifier of the backbone network egress device 1 , and the identifier of the backbone network egress device 1 may be an IP address of the backbone network egress device 1 .

[0320] In one example, the information 1 may also include SID1 assigned by the backbone network egress device 1 for the adjacency relationship between the backbone network egress device 1 and the site edge2, so that in the subsequent traffic forwarding stage, the message can be encapsulated based on SID1, thereby performing traffic forwarding based on the SID1. The SID1 may be an SRv6 END.X SID or an adj-SID. For example, in a network scenario where SRv6 technology is used for forwarding, the SID1 may be an SRv6 END.XSID, and in a network scenario where MPLS technology is used for forwarding, the SID1 may be an adj-SID.

[0321] In another example, the information 1 may also include the SID2 of the backbone network egress device 1, so that in the subsequent traffic forwarding stage, the message can be encapsulated based on SID2, thereby performing traffic forwarding based on the SID2. The SID2 may be an SRv6 END.SID or a node SID. For example, in a network scenario where SRv6 technology is used for forwarding, the SID2 may be an SRv6 END.SID, and in a network scenario where MPLS technology is used for forwarding, the SID2 may be a node SID.

[0322] In another example, the information 1 may also include the routing priority of the backbone network egress device 1, so that the communication device (eg edge1) receiving route 1 arranges an end-to-end path from edge1 to edge2 in combination with the routing priority.

[0323] In another example, the information 1 may also include the load sharing weight of the backbone network egress device 1, so that the communication device (eg, edge1) receiving route 1 determines the end-to-end path for forwarding service traffic in combination with the load sharing weight.

[0324] The route 1 may be carried by the BGP message 1, specifically, the route 1 may be carried by the MP_REACH_NLRI in the BGP message 1. Regarding the MP_REACH_NLRI carrying the route 1, the following is an example in which the route 1 includes the identifier of the site edge2, the identifier of the backbone network egress device 1, SID1, and SID2.

[0325] See also Figure 4a , which is a schematic diagram of the structure of a MP_REACH_NLRI provided in an embodiment of the present application. Figure 4a As shown, the MP_REACH_NLRI includes: a route type field, a length field, a CPE endpoint address (CPE-End-Point) field, a target gateway endpoint address (Destination-GW-End-Point) field, a connection (connection) SID field, and a target gateway SID (Destination-GW-SID) field. Among them:

[0326] route type: Route type. The value of the route type field indicates that route 1 is the SD-WAN gateway information announcement route. In an example, the value of route type can be 3.

[0327] length: length. The value of the length field indicates the total length of each field following the length field.

[0328] CPE-End-Point: carries the CPE endpoint address, for example, carries the IP address of site edge2.

[0329] Destination-GW-End-Point: carries the destination gateway endpoint address, for example, carries the IP address of backbone network egress device 1.

[0330] connection SID: used to carry the aforementioned SID1.

[0331] Destination-GW-SID: used to carry the aforementioned SID2.

[0332] In one example, if the information 1 also includes the routing priority of the backbone network egress device 1, as an example, the MP_REACH_NLRI may also include a routing priority field, which is used to carry the routing priority of the backbone network egress device 1. As another example, the BGP message 1 may carry a BGP path attribute 1, and a routing priority sub-TLV is added to the BGP path attribute 1 to carry the routing priority. Figure 4b As shown, Figure 4b A schematic diagram of the structure of a routing priority sub-TLV provided in an embodiment of the present application. Figure 4b The routing priority sub-TLV shown may include a type, a length, and a gateway priority (priority of the GW) field, where the gateway priority field is used to carry the routing priority of the aforementioned backbone network egress device 1 .

[0333] In another example, the information 1 also includes the load sharing weight of the backbone network egress device 1. As an example, the MP_REACH_NLRI may also include a weight field, which is used to carry the load sharing weight of the backbone network egress device 1. As another example, the BGP message 1 may carry a BGP path attribute 1, and a weight sub-TLV is added to the BGP path attribute 1 to carry the load sharing weight. Figure 4c As shown, Figure 4c A schematic diagram of the structure of a weight sub-TLV provided in an embodiment of the present application. Figure 4c The weight sub-TLV shown may include a type, a length, and a gateway load sharing weight (weight of the GW) field, and the gateway load sharing weight field is used to carry the load sharing weight of the aforementioned backbone network egress device 1.

[0334] S102: The site edge2 notifies the route 1 to the site edge1.

[0335] S103: Site edge1 receives route 1 advertised by site edge2.

[0336] S104: The site edge1 obtains the binding relationship 1 between the site edge2 and the backbone network egress device 1 according to the route 1.

[0337] After site edge2 obtains route 1, it can announce route 1 to site edge1. Correspondingly, site edge1 can receive route 1 announced by site edge2. After site edge1 receives route 1 announced by site edge2, it can parse route 1 to obtain binding relationship 1 between site edge2 and backbone network egress device 1. After site edge1 obtains binding relationship 1, it can store the binding relationship 1 so as to determine the end-to-end path from site edge1 to site edge2 based on the binding relationship 1 later.

[0338] In an example, the binding relationship 1 may include the identifier of the site edge2 and the information 1 of the backbone network egress device 1. As an example, the binding relationship 1 may be as shown in the following Table 2:

[0339] Table 2

[0340]

[0341]

[0342] In one example, if the aforementioned route 1 does not include the routing priority of the backbone network egress device 1, the site edge1 can determine the routing priority of the backbone network egress device 1 by itself. For example, the site edge1 can determine the routing priority of the backbone network egress device 1 according to the routing policy configured by itself, or in combination with the load condition of the backbone network egress device 1.

[0343] In another example, if the aforementioned route 1 does not include the load sharing weight of the backbone network egress device 1, the site edge1 can determine the load sharing weight of the backbone network egress device 1 by itself. For example, the site edge1 can determine the load sharing weight of the backbone network egress device 1 according to the load sharing strategy configured by itself, or in combination with the load condition of the backbone network egress device 1.

[0344] In one example, the route 1 may also include service intent information, which is used to indicate service intent. Site edge2 notifies site edge1 of the service intent information through route 1, so that during the traffic forwarding phase, the communication device that forwards the service traffic can forward the traffic in combination with the service intent information, thereby satisfying the service intent.

[0345] 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.

[0346] In the embodiment of the present application, the route 1 may include a BGP path attribute 1, and the BGP path attribute 1 is used to carry the service intent information. It is noted here that the BGP path attribute 1 may be a Metadata Path Attribute1.

[0347] In an example, if the service intent information includes the aforementioned gateway that needs to be passed, then the MetadataPath Attribute1 may include a sub-TLV1, and the sub-TLV1 is used to carry the gateway that needs to be passed.

[0348] For reference Figure 4d To understand, Figure 4d A schematic diagram of the structure of a sub-TLV1 included in a Metadata PathAttribute1 provided in an embodiment of the present application. Figure 4d As shown, the sub-TLV1 includes an include-GW sub-type field, a length field and a gateway information field.

[0349] The inclusion of the gateway subtype field indicates that this sub-TLV is used to carry information about the gateway that needs to be passed;

[0350] The length field is used to indicate the length of the gateway information field.

[0351] The gateway information field may carry gateway information, and in one example, the gateway information includes a gateway address. In another example, the gateway information may also include a gateway SID, and the gateway SID mentioned here may be a SRv6END.SID or a node SID.

[0352] In yet another example, if the service intent information includes the aforementioned gateway that needs to be bypassed, then the Metadata Path Attribute1 may include a sub-TLV2, and the sub-TLV2 is used to carry the gateway that needs to be bypassed.

[0353] For reference Figure 4e To understand, Figure 4e A schematic diagram of the structure of a sub-TLV2 included in a Metadata PathAttribute1 provided in an embodiment of the present application. Figure 4e As shown, the sub-TLV2 includes an exclude-GW sub-type field, a length field, and a gateway information field.

[0354] The detour gateway subtype field indicates that this sub-TLV is used to carry information about the gateway that needs to be detoured;

[0355] The length field is used to indicate the length of the gateway information field.

[0356] The gateway information field can carry gateway information. For gateway information, please refer to the above Figure 4d The relevant description part will not be repeated here.

[0357] In another example, if the service intent information includes the aforementioned quality of service parameter, the MetadataPath Attribute1 may include a sub-TLV3, and the sub-TLV3 is used to carry the quality of service parameter.

[0358] For reference Figure 4f To understand, Figure 4f A schematic diagram of the structure of a sub-TLV3 included in a Metadata PathAttribute1 provided in an embodiment of the present application. Figure 4f As shown, the sub-TLV3 includes a QoS sub-type field, a length field and a QoS parameter field.

[0359] The Quality of Service Parameter Subtype field indicates that this sub-TLV is used to carry quality of service parameters;

[0360] The length field is used to indicate the length of the quality of service parameter field.

[0361] The service quality parameter field may carry specific service quality parameters, such as one or more parameters such as delay, packet loss, and bit error rate.

[0362] In an embodiment of the present application, when site edge2 is multi-homed to backbone network export device 1 and backbone network export device 2 in the backbone network, the site edge2 can correspond to multiple gateways. That is, in addition to backbone network export device 1 being the gateway of site edge2, backbone network export device 2 is also the gateway of site edge2. In this case, the site edge2 can also obtain route 2 and pass route 2 to site edge1. Route 2 is a route announced by the SD-WAN gateway information, and route 2 includes the identifier of site edge2 and information 2 of backbone network export device 2. The site edge2 accesses the backbone network through backbone network export device 2. Correspondingly, site edge1 can receive route 2 announced by site edge2, and based on route 2, obtain binding relationship 2 between site edge2 and backbone network export device 2.

[0363] Regarding the specific implementation of site edge2 notifying route 2 to site edge1 and site edge1 obtaining binding relationship 2, the implementation principle is the same as method 100, so the relevant implementation can refer to the description of method 100 in the previous text, and no detailed description is given here.

[0364] In an example, after site edge1 receives route 2, its locally stored binding relationship may be as shown in Table 3 below.

[0365] Table 3

[0366]

[0367] See also Figure 5 , this figure is a signaling interaction diagram of an information notification method provided in an embodiment of the present application.

[0368] Figure 5 The information notification method 200 shown can be applied to Figure 1a or Figure 1b When the method 200 is applied to Figure 1aIn the application scenario shown, the backbone network egress device 1 in method 200 may correspond to Figure 1a GW2 shown, the backbone network egress device 2 in method 200 may correspond to Figure 1a GW4 shown. When the method 200 is applied to Figure 1b In the application scenario shown, the backbone network egress device 1 in method 200 may correspond to Figure 1b The POP4 shown, the backbone network egress device 2 in the method 200 may correspond to Figure 1b POP9 shown.

[0369] The method 200 may include, for example, the following S201 - S204 .

[0370] S201: The site edge2 obtains route 1', which is a VPN route. The route 1' includes an identifier of the site edge2 and information 1 of a backbone network egress device 1. The site edge2 accesses the backbone network through the backbone network egress device 1.

[0371] In the embodiment of the present application, the site edge2 can generate the route 1' based on the identifier of the site edge2 and the information 1 of the backbone network egress device 1. In one example, the VPN route can include a destination prefix, for example, Figure 1b In the scenario shown, the target prefix may be a network prefix corresponding to the corporate headquarters.

[0372] Regarding the identifier of the site edge2 and the information 1 of the backbone network egress device 1, reference may be made to the relevant description part in the method 100, and no repeated description is given here.

[0373] In one example, the VPN route may include a BGP path attribute 2, which is used to carry the identifier and information 1 of the aforementioned site edge2. In a specific example, the BGP path attribute 2 may be a MetadataPath Attribute 2. The Metadata Path Attribute 2 may include a sub-TLV1, which is used to carry the identifier and information 1 of the aforementioned site edge2.

[0374] Can be combined Figure 6 To understand, Figure 6 A schematic diagram of the structure of a sub-TLV1 included in a Metadata Path Attribute2 provided in an embodiment of the present application. Figure 6As shown, the sub-TLV1 includes: Destination GW Sub-Type field, length field, priority field, weight field, CPE-End-Point field, Destination-GW-End-Point field, connection SID field, and Destination-GW-SID field. Among them:

[0375] Destination GW Sub-Type: Destination gateway sub-type field, indicating that this sub-TLV carries the information of the destination gateway;

[0376] length: length. The value of the length field indicates the total length of each field following the length field.

[0377] priority: priority field, which carries the routing priority of backbone network egress device 1. In an example, the smaller the value of the priority field, the higher the priority.

[0378] weight: load sharing weight field, carrying the load sharing weight of backbone network egress device 1.

[0379] CPE-End-Point: carries the CPE endpoint address, for example, carries the IP address of site edge2.

[0380] Destination-GW-End-Point: carries the destination gateway endpoint address, for example, carries the IP address of backbone network egress device 1.

[0381] connection SID: used to carry the aforementioned SID1.

[0382] Destination-GW-SID: used to carry the aforementioned SID2.

[0383] S202: The site edge2 notifies the route 1' to the site edge1.

[0384] S203: Site edge1 receives route 1' advertised by site edge2.

[0385] S204: The site edge1 obtains the binding relationship 1 between the site edge2 and the backbone network egress device 1 according to the route 1'.

[0386] After site edge2 obtains route 1', it can announce route 1' to site edge1. Correspondingly, site edge1 can receive route 1' announced by site edge2. After site edge1 receives route 1' announced by site edge2, it can parse route 1' to obtain binding relationship 1 between site edge2 and backbone network exit device 1. After site edge1 obtains binding relationship 1, it can store the binding relationship 1 to facilitate the subsequent determination of the end-to-end path from site edge1 to site edge2 based on the binding relationship 1. Regarding the binding relationship 1, you can refer to Table 2 in method 100 for understanding, and no repeated description is given here.

[0387] In one example, if the aforementioned route 1' does not include the routing priority of the backbone network egress device 1, the site edge1 can determine the routing priority of the backbone network egress device 1 by itself. For example, the site edge1 can determine the routing priority of the backbone network egress device 1 according to the routing policy configured by itself, or in combination with the load condition of the backbone network egress device 1.

[0388] In another example, if the aforementioned route 1' does not include the load sharing weight of the backbone network egress device 1, the site edge1 can determine the load sharing weight of the backbone network egress device 1 by itself. For example, the site edge1 can determine the load sharing weight of the backbone network egress device 1 according to the load sharing strategy configured by itself, or in combination with the load condition of the backbone network egress device 1.

[0389] In one example, the route 1' may also include service intent information, which is used to indicate service intent. Site edge2 notifies site edge1 of the service intent information through route 1, so that during the traffic forwarding phase, the communication device that forwards the service traffic can forward the traffic in combination with the service intent information, thereby satisfying the service intent. For the specific contents of the service intent information, please refer to the relevant description of method 100 in the previous text, which will not be repeated here.

[0390] In the embodiment of the present application, the service intention information can be carried by the BGP path attribute included in route 1'. In one example, the service intention information and the aforementioned information 1 can be carried by the same BGP path attribute or by different BGP path attributes, which is not specifically limited in the embodiment of the present application.

[0391] In a specific example, the business intent information and the aforementioned information 1 can both be carried by MetadataPath Attribute2. In this case, one Metadata Path Attribute can carry both the information 1 and the business intent information.

[0392] Regarding the specific implementation manner of the Metadata Path Attribute2 carrying the service intent information, reference may be made to the description of the Metadata Path Attribute1 carrying the service intent information in method 100, which will not be repeated here.

[0393] In an embodiment of the present application, when the site edge2 is multi-homed to the backbone network export device 1 and the backbone network export device 2 in the backbone network, the site edge2 can correspond to multiple gateways. That is, in addition to the backbone network export device 1 being the gateway of the site edge2, the backbone network export device 2 is also the gateway of the site edge2. For this case, the aforementioned VPN route can carry multiple sub-TLV1s, and one sub-TLV1 is used to carry the information of one gateway. For this case, the site edge1 can parse the multiple sub-TLV1s to obtain the information of multiple gateways bound to the site edge2. For this case, after the site edge1 receives the VPN route, its locally stored binding relationship can refer to Table 3 in method 100, and no repeated description is made here.

[0394] See also Figure 7 , this figure is a signaling interaction diagram of an information notification method provided in an embodiment of the present application.

[0395] Figure 7 The information notification method 300 shown can be applied to Figure 1a or Figure 1b The application scenario shown.

[0396] When the method 300 is applied to Figure 1a In the application scenario shown, the backbone network egress device 1 in method 300 may correspond to Figure 1a GW2 shown, the backbone network egress device 2 in method 300 may correspond to Figure 1a GW4 shown, the backbone network ingress device 1 in method 300 may correspond to Figure 1a GW1 or GW3 shown.

[0397] When the method 300 is applied to Figure 1b In the application scenario shown, the backbone network egress device 1 in method 300 may correspond to Figure 1b The POP4 shown, the backbone network egress device 2 in the method 300 may correspond to Figure 1b The POP9 shown, the backbone network entry device 1 in the method 300 may correspond to Figure 1b POP1 shown.

[0398] The method 300 may include, for example, the following S301 - S304 .

[0399] S301: Backbone network export device 1 obtains route 1", wherein route 1" is a route automatically discovered by the SD-WAN gateway, and route 1" includes the identifier of site edge2 and information 1 of backbone network export device 1. Site edge2 accesses the backbone network through backbone network export device 1.

[0400] In the embodiment of the present application, the backbone network egress device 1 may generate the route 1" based on the identifier of the site edge2 and the information 1 of the backbone network egress device 1.

[0401] Regarding the identifier of the site edge2 and the information 1 of the backbone network egress device 1, reference may be made to the relevant description part in the method 100, and no repeated description is given here.

[0402] The route 1" can be carried by BGP message 2. Specifically, the route 1" can be carried by MP_REACH_NLRI in BGP message 2. Regarding the MP_REACH_NLRI carrying the route 1", the following is an example of route 1" including the identifier of the above-mentioned site edge2, the identifier of the backbone network export device 1, SID1, and SID2.

[0403] See also Figure 8 , which is a schematic diagram of the structure of another MP_REACH_NLRI provided in the embodiment of the present application. Figure 8 As shown, the MP_REACH_NLRI includes: a route type field, a length field, a local-end-point field, a remote-end-point field, a connection SID field, and a local SID field.

[0404] Route type: Route type. The value of the route type field indicates that "route 1" is the route automatically discovered by the SD-WAN gateway. In an example, the value of route type can be 2.

[0405] length: length. The value of the length field indicates the total length of each field following the length field.

[0406] The local-end-point field carries the local address, which in this application carries the IP address of the backbone network egress device 1;

[0407] remote-end-point: carries the CPE endpoint address, for example, carries the IP address of site edge2.

[0408] connection SID: used to carry the aforementioned SID1.

[0409] local SID field: used to carry the local SID, and in this application carries the aforementioned SID2.

[0410] In one example, before executing S301, the backbone network egress device 1 and the site edge1 can announce the TNP route to each other, and then establish an SD-WAN tunnel between the site edge2 and the backbone network egress device 1. After the SD-WAN tunnel is created, the backbone network egress device 1 acts as a GW to allocate a connection SID (i.e., SID1) to the tunnel, so that the route 1 including SID1 can be obtained later.

[0411] In one example, the backbone network egress device 1 can locally configure its own role as a gateway. The backbone network device 1 detects that its own role is a gateway, so after the SD-WAN tunnel is created, the backbone network egress device 1, as a GW, allocates a connection SID to the tunnel.

[0412] S302: Backbone network egress device 1 notifies site edge1 of route 1" through backbone network ingress device 1, and site edge1 accesses the backbone network through backbone network ingress device 1.

[0413] In an embodiment of the present application, a BGP neighbor relationship can be established between the backbone network egress device 1 and the backbone network ingress device 1, and the backbone network egress device 1 can notify the route 1" to the backbone network ingress device 1. After the backbone network ingress device 1 receives the route 1", it can further notify the route 1" to the site edge1.

[0414] S303: Site edge1 receives route 1" advertised by backbone network egress device 1.

[0415] S304: The site edge1 obtains the binding relationship 1 between the site edge2 and the backbone network egress device 1 according to route 1".

[0416] After site edge1 receives route 1", it can parse route 1 to obtain binding relationship 1 between site edge2 and backbone network exit device 1. After site edge1 obtains binding relationship 1, it can store binding relationship 1 to facilitate subsequent determination of the end-to-end path from site edge1 to site edge2 based on binding relationship 1. Regarding the binding relationship 1, you can refer to Table 2 in method 100 for understanding, and no repeated description is given here.

[0417] In an example, after receiving the route 1", the site edge1 can determine the routing priority of the backbone network egress device 1. For example, the site edge1 can determine the routing priority of the backbone network egress device 1 according to the routing policy configured by itself or in combination with the load condition of the backbone network egress device 1.

[0418] In another example, after receiving the route 1", the site edge1 can determine the load sharing weight of the backbone network egress device 1. For example, the site edge1 can determine the load sharing weight of the backbone network egress device 1 according to the load sharing strategy configured by itself, or in combination with the load condition of the backbone network egress device 1.

[0419] In the embodiment of the present application, when the site edge2 is multi-homed to the backbone network egress device 1 and the backbone network egress device 2 in the backbone network, the site edge2 can correspond to multiple gateways. That is, in addition to the backbone network egress device 1 being the gateway of the site edge2, the backbone network egress device 2 is also the gateway of the site edge2. In this case, the backbone network egress device 2 can also notify the site edge1 of the SD-WAN gateway automatic discovery route through the aforementioned backbone network entry device 1, so that the site edge1 obtains the binding relationship 2 between the site edge2 and the backbone network egress device 2. Regarding the specific implementation of "backbone network egress device 2 notifies site edge1 of the SD-WAN gateway's automatic route discovery through backbone network ingress device 1", its implementation principle is the same as the principle of "backbone network egress device 1 notifies site edge1 of the SD-WAN gateway's automatic route discovery through backbone network ingress device 1". Therefore, regarding the specific implementation of "backbone network egress device 2 notifies site edge1 of the SD-WAN gateway's automatic route discovery through backbone network ingress device 1", please refer to the description of method 300 in the previous text, and no repeated description is made here. In this case, after site edge1 receives the SD-WAN Ethernet automatic route discovery notified by backbone network egress device 2, the locally stored binding relationship can refer to Table 3 in method 100, and no repeated description is made here.

[0420] In traditional technologies, the binding relationship between a site edge and its corresponding gateway can be manually configured. Figure 1a In the scenario shown, the gateways at site edge1 can be configured as GW1 and GW3, and the gateways at site edge2 can be configured as GW2 and GW4. Figure 1b In the scenario shown, the gateway of site edge1 can be configured as POP1, and the gateway of site edge2 can be configured as POP4 and POP9 by manual configuration. The manual configuration method is inefficient. In view of this, the embodiment of the present application also provides corresponding routing announcement methods 400 and 500, which enable the site edge to determine its own corresponding gateway through the received route, without the need to manually configure the corresponding gateway on the site edge.

[0421] See also Fig. 9 , this figure is a signaling interaction diagram of a routing announcement method provided in an embodiment of the present application. Fig. 9 The method 400 shown can be applied to Figure 1a The application scenario shown or Figure 1b The application scenario shown.

[0422] When method 400 is applied to Figure 1a The application scenario shown is:

[0423] In one example, the site edge in method 400 may be Figure 1a The site edge1 shown, correspondingly, the gateway in method 400 can be Figure 1a GW1 or GW3 shown.

[0424] In yet another example, the site edge in method 400 may be Figure 1a The site edge2 shown, correspondingly, the gateway in method 400 can be Figure 1a GW2 or GW4 shown.

[0425] When method 400 is applied to Figure 1b The application scenario shown is:

[0426] In one example, the site edge in method 400 may be Figure 1b The site edge1 shown, correspondingly, the gateway in method 400 can be Figure 1b POP1 shown.

[0427] In yet another example, the site edge in method 400 may be Figure 1b The site edge2 shown, correspondingly, the gateway in method 400 can be Figure 1bPOP4 or POP9 as shown.

[0428] Fig. 9 The method 400 shown may include the following S401 - S404 .

[0429] S401: The gateway obtains route 3, where route 3 is the route automatically discovered by the SD-WAN gateway and route 3 includes gateway information 3.

[0430] In the embodiment of the present application, the gateway may generate the route 3 based on its own information 3.

[0431] In one example, before executing S401, the gateway and the site edge can announce the TNP route to each other, and then establish an SD-WAN tunnel between the site edge and the gateway. After the SD-WAN tunnel is created, the gateway assigns a connection SID (i.e., SID3) to the tunnel, so that route 3 including SID3 can be obtained later.

[0432] In one example, the gateway can locally configure its own role as a gateway. The gateway detects that its own role is a gateway, so after the SD-WAN tunnel is created, the gateway allocates a connection SID to the tunnel. In one example, the information 3 can include the IP address of the gateway and the IP address of the site edge.

[0433] In one example, the information 3 may include SID3 assigned by the gateway to the adjacency relationship between the gateway and the site edge, so that in the subsequent traffic forwarding stage, the message can be encapsulated based on SID3, thereby performing traffic forwarding based on the SID3. The SID3 can be an SRv6 END.X SID or an adj-SID. For example, in a network scenario where SRv6 technology is used for forwarding, the SID3 can be an SRv6 END.X SID, and in a network scenario where MPLS technology is used for forwarding, the SID3 can be an adj-SID.

[0434] In another example, the information 3 may include the SID4 of the gateway, so that in the subsequent traffic forwarding stage, the message can be encapsulated based on SID4, thereby performing traffic forwarding based on SID4. The SID4 may be SRv6END.SID or a node SID. For example, in a network scenario where SRv6 technology is used for forwarding, the SID4 may be SRv6 END.SID, and in a network scenario where MPLS technology is used for forwarding, the SID4 may be a node SID.

[0435] The route 3 may be carried by the BGP message 3. Specifically, the route 3 may be carried by the MP_REACH_NLRI in the BGP message 3. A possible structure of the MP_REACH_NLRI carrying the route 3 may be referred to: Figure 8 , no repetitive explanation is given here.

[0436] S402: The gateway notifies the route 3 to the site edge, and the site edge accesses the backbone network through the gateway.

[0437] S403: The site edge receives route 3 announced by the gateway.

[0438] S404: The site edge obtains the binding relationship 3 between the site edge and the gateway according to the route 3.

[0439] After the gateway obtains route 3, it can notify route 3 to the site edge, and accordingly, the site edge can receive the route 3 notified by the gateway. After receiving route 3, the site edge can parse route 3 to obtain the binding relationship 3 between the site edge and the gateway, so as to determine the end-to-end path based on the binding relationship 3 later.

[0440] In one example, the site edge may also determine the routing priority of the gateway after receiving the route 3. For example, the site edge may determine the routing priority of the gateway according to the routing policy configured by itself or in combination with the load condition of the gateway.

[0441] In another example, the site edge may also determine the load sharing weight of the gateway after receiving the route 3. For example, the site edge may determine the load sharing weight of the gateway according to the load sharing strategy configured by itself or in combination with the load condition of the gateway.

[0442] In one example, the route 3 may also include intermediate gateway information, and the intermediate gateway information indicates at least one intermediate gateway between the backbone network entry device and the backbone network exit device in the backbone network, so that the site edge can perform path orchestration based on the intermediate gateway. In one example, the site edge can determine the gateway constraints that the end-to-end path needs to follow based on business requirements and the intermediate gateway. The gateway constraints mentioned here include gateways that need to be passed through and / or gateways that need to be bypassed. In a specific example, when the site edge performs path orchestration according to business requirements, it can determine the gateways that the end-to-end path needs to pass through and / or the gateways that need to be bypassed from the intermediate gateways, so that the determined end-to-end path meets business requirements.

[0443] In one example, the intermediate gateway information may be carried by a BGP path attribute. In a specific example, the intermediate gateway information may be carried by Metadata Path Attribute 3. For example, the Metadata Path Attribute 3 may include at least one intermediate gateway sub-TLV, the intermediate gateway sub-TLV is used to carry the information of the intermediate gateway, and one intermediate gateway sub-TLV is used to carry the information of one intermediate gateway.

[0444] In an embodiment of the present application, for a certain intermediate gateway, the information of the intermediate gateway includes at least the endpoint address (e.g., IP address) of the intermediate gateway. Optionally, the information of the intermediate gateway may also include the SID of the intermediate gateway. The SID of the intermediate gateway may be an SRv6 END.SID or a node SID.

[0445] Regarding the intermediate gateway sub-TLV, you can combine Fig.10 To understand, Fig.10 A schematic diagram of the structure of an intermediate gateway sub-TLV provided in an embodiment of the present application. Fig.10 As shown, the intermediate gateway sub-TLV includes: an intermediate gateway sub-type field (transit-GW sub-type), a length field, an intermediate gateway endpoint address (transit-GW-end-point) field and an intermediate gateway SID (transit-GW-SID) field.

[0446] transit-GW sub-type field: indicates that this sub-TLV carries the gateway information of an intermediate gateway.

[0447] Length field: indicates the total length value of each field following the length field.

[0448] transit-GW-end-point field: indicates the endpoint address of the intermediate gateway.

[0449] transit-GW-SID field: indicates the SID corresponding to the intermediate gateway.

[0450] In some examples, a site edge may correspond to multiple gateways. In this case, each gateway may send an SD-WAN gateway auto-discovery route to the site edge so that the site edge obtains the binding relationship between itself and the gateway. Figure 1aIn the scenario shown, site edge1 is multi-homed to GW1 and GW3, then GW1 can send an SD-WAN gateway automatic discovery route with GW1's information to site edge1, and GW3 can send an SD-WAN gateway automatic discovery route with GW3's information to site edge1. Figure 1b In the described scenario, site edge2 is dual-homed to POP4 and POP9. Then POP4 can send the SD-WAN gateway automatic discovery route carrying POP4 information to site edge2, and POP9 can send the SD-WAN gateway automatic discovery route carrying POP9 information to site edge2.

[0451] by Figure 1a Taking the site edge1 shown as an example, after GW1 and GW3 send the SD-WAN gateway automatic discovery route to the site edge1, the site edge1 can obtain the binding relationship shown in Table 4 below.

[0452] Table 4

[0453]

[0454] See also Fig.11 , this figure is a signaling interaction diagram of another routing announcement method provided in an embodiment of the present application. Fig.11 The method 500 shown can be applied to Figure 1a The application scenario shown or Figure 1b The application scenario shown.

[0455] Regarding the site edge and gateway in method 500, reference may be made to the description of the site edge and gateway in method 400, and no repeated description is given here.

[0456] Fig.11 The method 500 shown may include the following S501 - S504 .

[0457] S501: The gateway obtains route 3', where route 3' is a BGP LS route and includes gateway information 3.

[0458] In the embodiment of the present application, the gateway may generate the route 3' based on its own information 3.

[0459] In one example, before executing S501, a GRE tunnel can be established between the gateway and the site edge, and then a BGP session is established between the site edge and the gateway using the GRE tunnel address, and the BGP LS address family is enabled between the site edge and the gateway. In addition, the gateway enables the BGP egress peer engineering (EPE) function. In this case, the gateway can allocate SID3 for the adjacency relationship (BGP session) between the gateway and the site. The SID3 can be an SRv6 END.X SID or an adj-SID.

[0460] Regarding BGP EPE, it should be noted that BGP EPE can allocate BGP peer SIDs for inter-domain paths, and peer SIDs can be directly passed to the network controller through BGP-LS extension. For forwarding devices that have not established BGP-LS neighbors with the controller, the peer SID information can be first passed to the BGP neighbor through BGP-LS, and then the BGP neighbor can pass it to the network controller through BGP-LS. BGP EPE can allocate peer-node SIDs and peer-adj SIDs for peers. Among them:

[0461] The peer-node SID is used to indicate a peer node. Each BGP session will be assigned a peer-node SID. For an External Border Gateway Protocol (EBGP) neighbor established based on a loopback interface, there may be multiple corresponding physical links, so the peer-node SID for the neighbor will correspond to multiple outbound interfaces.

[0462] The peer-adj SID is used to indicate an adjacency to a peer. For EBGP neighbors established based on loopback interfaces, there may be multiple corresponding physical links. In this case, each adjacency will be assigned a peer-adj SID, and the specified link (corresponding to the specified outbound interface) will be used for forwarding.

[0463] In one example, the route 3' may include TLV1, which is used to indicate that the route 3' is used to announce the information of the gateway. In a specific example, the TLV1 may be a role announcement TLV, which is used to indicate that the role of the device that publishes the route 3' is a gateway. In another specific example, the TLV1 may be a gateway information indication TLV, and the type field of the TLV indicates that the device that publishes the route 3' is a gateway.

[0464] Regarding the role announcement TLV, you can combine Fig.12a To understand, Fig.12a A schematic diagram of the structure of a role notification TLV provided in an embodiment of the present application. Fig.12a As shown, the role announcement TLV includes: a type field, a length field and a device role field.

[0465] The Type field indicates that the TLV is a role announcement TLV.

[0466] The length field indicates the length of the device role field.

[0467] The device role field carries the device role. For example, when the value of the device role field is 1, it indicates that the device role is a gateway.

[0468] As can be seen from the above description of SID3, in one example, the information 3 may include SID3 and / or SID4. In this case, the route 3' may include TLV2 and TLV3, where TLV2 is used to carry SID3 and TLV3 is used to carry SID4.

[0469] In one example, the TLV2 may be an adjacency SID TLV. The structure of the adjacency SID TLV may be combined with Figure 12b To understand, Figure 12b A schematic diagram of the structure of an adjacency relationship SID TLV provided in an embodiment of the present application. Figure 12b As shown, the adjacency SID TLV includes: a type field, a length field and an adjacency SID field.

[0470] The Type field indicates that the TLV is an adjacency SID TLV.

[0471] The length field indicates the length of the adjacency SID field.

[0472] The adjacency relationship SID field carries the SID assigned by the gateway to the adjacency relationship between the gateway and the site edge. In an embodiment of the present application, the adjacency relationship SID field can be used to carry the aforementioned SID3.

[0473] In yet another example, when SID3 is an SRv6 End.X SID, the TLV2 may be an SRv6 End.X SIDTLV.

[0474] In an example, the TLV3 may be a node SID TLV. The structure of the node SID TLV may be combined with Fig.12c To understand, Fig.12cA schematic diagram of the structure of a node SID TLV provided in an embodiment of the present application. Fig.12c As shown, the node SID TLV includes: a type field, a length field and a node SID field.

[0475] The type field indicates that the TLV is a node SID TLV.

[0476] The length field indicates the length of the node SID field.

[0477] The node SID field carries the gateway SID. In the embodiment of the present application, the node SID field can be used to carry the aforementioned SID4.

[0478] S502: The gateway notifies the route 3' to the site edge, and the site edge accesses the backbone network through the gateway.

[0479] S503: The site edge receives the route 3' advertised by the gateway.

[0480] S504: The site edge obtains the binding relationship 3 between the site edge and the gateway according to the route 3'.

[0481] After the gateway obtains the route 3', it can notify the site edge of the route 3'. Correspondingly, the site edge can receive the route 3' notified by the gateway. After the site edge receives the route 3', it can parse the route 3' to obtain the binding relationship 3 between the site edge and the gateway, so as to determine the end-to-end path based on the binding relationship 3 later.

[0482] In one example, after receiving the route 3', the site edge may also determine the routing priority of the gateway. For example, the site edge may determine the routing priority of the gateway according to its own configured routing strategy or in combination with the load condition of the gateway.

[0483] In another example, after receiving the route 3', the site edge may also determine the load sharing weight of the gateway. For example, the site edge may determine the load sharing weight of the gateway according to a load sharing strategy configured by itself or in combination with the load condition of the gateway.

[0484] In one example, the route 3' may also include intermediate gateway information, and the intermediate gateway information indicates at least one intermediate gateway between the backbone network inlet device and the backbone network outlet device in the backbone network, so that the site edge can perform path orchestration based on the intermediate gateway. In one example, the site edge can determine the gateway constraints that the end-to-end path needs to follow based on business requirements and the intermediate gateway. The gateway constraints mentioned here include gateways that need to be passed through and / or gateways that need to be bypassed. In a specific example, when the site edge performs path orchestration based on business requirements, it can determine the gateways that the end-to-end path needs to pass through and / or the gateways that need to be bypassed from the intermediate gateways, so that the determined end-to-end path meets business requirements.

[0485] In one example, the intermediate gateway information may be carried by a BGP path attribute. In a specific example, the intermediate gateway information may be carried by Metadata Path Attribute 4. For example, the Metadata Path Attribute 4 may include at least one intermediate gateway sub-TLV, the intermediate gateway sub-TLV is used to carry the information of the intermediate gateway, and one intermediate gateway sub-TLV is used to carry the information of one intermediate gateway.

[0486] In an embodiment of the present application, for a certain intermediate gateway, the information of the intermediate gateway includes at least the endpoint address (e.g., IP address) of the intermediate gateway. Optionally, the information of the intermediate gateway may also include the SID of the intermediate gateway. The SID of the intermediate gateway may be an SRv6 END.SID or a node SID.

[0487] For the intermediate gateway sub-TLV, please refer to the above Fig.10 The description part is not repeated here.

[0488] In some examples, a site edge may correspond to multiple gateways. In this case, each gateway may send a BGP LS route to the site edge so that the site edge obtains the binding relationship between itself and the gateway. Figure 1a In the scenario shown, site edge1 is multi-homed to GW1 and GW3, so GW1 can send a BGP LS route carrying GW1's information to site edge1, and GW3 can send a BGP LS route carrying GW3's information to site edge1. Figure 1bIn the described scenario, site edge2 is dual-homed to POP4 and POP9. Then POP4 can send a BGP LS route carrying POP4 information to site edge2, and POP9 can send a BGP LS route carrying POP9 information to site edge2.

[0489] by Figure 1a Taking the site edge1 as an example, after GW1 and GW3 both send BGP LS routes to the site edge1, the site edge1 can obtain the binding relationship shown in Table 4 above.

[0490] Using method 500, the gateway and site edge do not need to enable the SD-WAN address family, but only need to enable the BGP-LS address family.

[0491] After executing one of the above methods 100-300 and one of the methods 400-500, the site edge1 can combine the locally stored binding relationship between the site edge and the gateway to orchestrate the end-to-end path.

[0492] Next, a specific implementation method of orchestrating an end-to-end path at site edge1 is introduced with reference to a specific example.

[0493] by Figure 1b Taking the scenario shown in the figure as an example, the binding relationship between the site edge and the gateway saved locally at site edge1 can be shown in the following Table 5:

[0494] Table 5

[0495] Serial number CPE IP GW IP Connection SID Gateway SID Routing priority Load sharing weight 1 edge2-IP POP4-IP edge2-POP4-SID POP4-SID POP4-priority POP4-weight 2 edge2-IP POP9-IP edge2-POP9-SID POP9-SID POP9-priority POP9-weight 3 edge1-IP POP1-IP edge1-POP1-SID POP1-SID POP1-priority POP1-weight

[0496] In Table 5:

[0497] "*-IP" means the IP address of "*", for example, edge2-IP means the IP address of site edge2;

[0498] "ab-SID" indicates the SID of the adjacency relationship between a and b. For example, "edge2-POP4-SID" indicates the SID of the adjacency relationship between edge2 and POP4.

[0499] "*-SID" means the SID of "*", for example, POP4-SID means the SID of POP4;

[0500] "*-priority" indicates the routing priority of "*". For example, POP4-priority indicates the routing priority of POP4.

[0501] "*-weight" indicates the load sharing weight of "*". For example, POP4-weight indicates the load sharing weight of POP4.

[0502] In an example, after receiving the service route (eg, VPN route) published by the site edge1, the site edge2 can arrange an end-to-end path for the service route.

[0503] In a specific example, the site edge2 can determine the end-to-end path 1 from the site edge1 to edge2 based on the binding relationship shown in the first row and the binding relationship shown in the third row of Table 5, and the end-to-end path 1 includes POP1 and POP4, that is, the end-to-end path 1 can be: edge1-POP1-POP4-edge2.

[0504] In another specific example, the site edge2 can determine the end-to-end path 2 from the site edge1 to edge2 based on the binding relationship shown in the second row and the binding relationship shown in the third row of Table 5, and the end-to-end path 2 includes POP1 and POP9, that is, the end-to-end path 2 can be: edge1-POP1-POP9-edge2.

[0505] In one example, after the site edge1 arranges the aforementioned end-to-end path 1 and end-to-end path 2, one of the two end-to-end paths can be selected as the path for actually forwarding the service traffic. As an example, the site edge1 can determine the end-to-end path corresponding to the POP with a higher routing priority as the path for actually forwarding the service traffic based on the routing priority of POP4 and the routing priority of POP9. For example, if the routing priority of POP4 is higher than the routing priority of POP9, the end-to-end path 1 can be determined as the path for actually forwarding the service traffic.

[0506] In another example, after the site edge1 arranges the aforementioned end-to-end path 1 and end-to-end path 2, the two end-to-end paths can be set as primary and backup paths. As an example, the site edge1 can determine the end-to-end path corresponding to the POP with a high routing priority as the primary path, and determine the end-to-end path corresponding to the POP with a low routing priority as the backup path, based on the routing priority of POP4 and the routing priority of POP9. For example, if the routing priority of POP4 is higher than the routing priority of POP9, the end-to-end path 1 can be determined as the primary path, and the end-to-end path 2 can be determined as the backup path.

[0507] In another example, after the site edge1 choreographs the aforementioned end-to-end path 1 and end-to-end path 2, the two end-to-end paths can be set as load sharing paths. The end-to-end path 1 and the end-to-end path 2 can be set as equal-cost load sharing paths or as unequal-cost load sharing paths, which is not specifically limited in the embodiments of the present application.

[0508] As an example, the load sharing weight of the end-to-end path 1 can be determined according to the load sharing weight of POP4, and the load sharing weight of the end-to-end path 2 can be determined according to the load sharing weight of POP9. For example, the load sharing weight of the end-to-end path 1 can be equal to the load sharing weight of POP4, and the load sharing weight of the end-to-end path 2 can be equal to the load sharing weight of POP9. In this case, when the load sharing weight of POP4 is equal to the load sharing weight of POP9, the end-to-end path 1 and the end-to-end path 2 can achieve equal load sharing, and when the load sharing weight of POP4 is not equal to the load sharing weight of POP9, the end-to-end path 1 and the end-to-end path 2 can achieve unequal load sharing.

[0509] As another example, the load sharing weights of end-to-end path 1 and end-to-end path 2 may also be set by edge1, independent of the load sharing weights of POP4 and POP9, and the embodiment of the present application does not make any specific limitation.

[0510] Similarly, in Figure 1a In the scenario shown, site edge1 can orchestrate four end-to-end paths based on the locally saved binding relationship between the site edge and the gateway. They are:

[0511] End-to-end path: site edge1-GW1-GW2-edge2.

[0512] End-to-end path: site edge1-GW1-GW4-edge2.

[0513] End-to-end path: site edge1-GW3-GW2-edge2.

[0514] End-to-end path: site edge1-GW3-GW4-edge2.

[0515] about Figure 1a Based on the binding relationship between the site edge and the gateway saved locally, the specific implementation method of arranging four end-to-end paths can be referred to the description part of the end-to-end path 1 and the end-to-end path 2 orchestrated by the site edge 1 above, and will not be repeated here.

[0516] 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.

[0517] 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.

[0518] 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.

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

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

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

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

[0523] The method 600 may, for example, include the following S601 - S606 .

[0524] S601: Site edge1 receives service message 1.

[0525] 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.

[0526] S602: 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.

[0527] 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.

[0528] 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.

[0529] 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.

[0530] 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.

[0531] 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.

[0532] 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.

[0533] 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.

[0534] 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.

[0535] 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.

[0536] 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.

[0537] In one example, the end-to-end path 1 may be pre-arranged by the site edge 1. In this case, the site edge 1 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 a VPN service, and the site edge 1 may arrange the end-to-end path 1 between the site edge 1 and the site edge 2 according to the VPN service and in combination with the aforementioned backbone network entry device 1 and backbone network exit device 1 as needed. As an example, the site edge 1 may arrange the end-to-end path for the VPN route after receiving the VPN route including the destination prefix announced by the site edge 2. In a specific example, the site edge 1 may arrange the end-to-end path 1 for the VPN route based on the binding relationship 1 between the site edge 1 and the backbone network entry device 1, and the binding relationship 2 between the site edge 2 and the backbone network exit device 1. When the method 600 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.

[0538] 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.

[0539] 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.

[0540] 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.

[0541] 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.

[0542] 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.

[0543] 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.

[0544] 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.

[0545] 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.

[0546] 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.

[0547] 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 Fig.14a To understand, Fig.14a A schematic diagram of the structure of SRv6 over GRE encapsulation provided in an embodiment of the present application. Fig.14a 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.

[0548] 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. Fig.14b To understand, Fig.14b A schematic diagram of the structure of an MPLS over GRE encapsulation provided in an embodiment of the present application. Fig.14b 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.

[0549] 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.

[0550] 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 Fig.14c To understand, Fig.14c A schematic diagram of the structure of an SRv6 in GENEVE package provided in an embodiment of the present application. Fig.14c 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 Fig.14d To understand, Fig.14d A schematic diagram of the structure of an SRv6 over GENEVE encapsulation provided in an embodiment of the present application. Fig.14d The package structure shown is relative to Fig.14c 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.

[0551] 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. Fig.14e To understand, Fig.14e A schematic diagram of the structure of an MPLS in GENEVE encapsulation provided in an embodiment of the present application. Fig.14eAs 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.

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

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

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

[0555] 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.

[0556] 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 .

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

[0558] 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.

[0559] 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.

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

[0561] 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.

[0562] 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.

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

[0564] 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.

[0565] From the above description, it can be known that, by using the method 600 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.

[0566] 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:

[0567] 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.

[0568] For the path information of the end-to-end path 2, please refer to the previous description of the path information of the end-to-end path 1. 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 S602 in method 600, which will not be repeated here.

[0569] 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 600, and no repeated description is given here.

[0570] 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.

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

[0572] See also Fig.15a , Fig.15a A scenario diagram of a traffic forwarding method provided in an embodiment of the present application. Fig.15a 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. Fig.15a 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:

[0573] 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.

[0574] 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.

[0575] 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.

[0576] 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.

[0577] 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.

[0578] 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.

[0579] See also Fig.15b , Fig.15b A scenario diagram of another traffic forwarding method provided in an embodiment of the present application. Fig.15b 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. Fig.15b 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:

[0580] 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.

[0581] 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 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.XSID) 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.

[0582] 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.

[0583] 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.

[0584] 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.

[0585] 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.

[0586] See also Fig.15c , Fig.15c A scenario diagram of another traffic forwarding method provided in an embodiment of the present application. Fig.15c 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. Fig.15c In the scenario shown, the end-to-end path between site edge1 and site edge2 is SR-MPLSTE policy. The specific process of traffic forwarding is as follows:

[0587] 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.

[0588] 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 TEpolicy according to 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.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.

[0589] 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.

[0590] 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.

[0591] 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.

[0592] 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.

[0593] See also Fig.15d , Fig.15d A scenario diagram of a traffic forwarding method provided in an embodiment of the present application. Fig.15d 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. Fig.15d 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:

[0594] 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.

[0595] 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.

[0596] 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 = 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.

[0597] 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.

[0598] 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.

[0599] See also Fig.15e , Fig.15e A scenario diagram of another traffic forwarding method provided in an embodiment of the present application. Fig.15e 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. Fig.15eIn the scenario shown, the end-to-end path between site edge1 and site edge2 is SR-MPLSTE policy. The specific process of traffic forwarding is as follows:

[0600] 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.

[0601] 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.

[0602] 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.

[0603] 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.

[0604] 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.

[0605] See also Fig.16 , which is a flow chart of an information notification method provided in an embodiment of the present application. Fig.16 The information notification method 700 shown can be applied to the above method 100 or method 200 or method 300 or method 400 or method 500 or method 600.

[0606] Fig.16 The information notification method 700 shown can be applied to a first communication device serving as a first site edge.

[0607] In the embodiment of the present application, the method 700 may include the following S701-S702.

[0608] S701: Receive a first route announced by a second communication device, wherein the first route includes first information of a first backbone network exit device and an identifier of a second site edge in the backbone network, wherein the second site edge accesses the backbone network through the first backbone network exit device, and the first site edge accesses the backbone network through a first backbone network entry device.

[0609] S702: Acquire a first binding relationship between the second site edge and the first backbone network egress device according to the first route.

[0610] When the method 700 is applied to the method 100:

[0611] The first site edge in method 700 may correspond to site edge1 in method 100; the second communication device in method 700 may correspond to site edge2 in method 100; the first route in method 700 may correspond to route 1 in method 100; the first backbone network export device in method 700 may correspond to backbone network export device 1 in method 100; the first information in method 700 may correspond to information 1 in method 100; the first binding relationship in method 700 may correspond to binding relationship 1 in method 100.

[0612] When the method 700 is applied to the method 200:

[0613] The first site edge in method 700 may correspond to site edge1 in method 200; the second communication device in method 700 may correspond to site edge2 in method 200; the first route in method 700 may correspond to route 1' in method 100; the first backbone network export device in method 700 may correspond to backbone network export device 1 in method 200; the first information in method 700 may correspond to information 1 in method 200; the first binding relationship in method 700 may correspond to binding relationship 1 in method 200.

[0614] When the method 700 is applied to the method 300:

[0615] The first site edge in method 700 may correspond to site edge1 in method 300; the second communication device in method 700 may correspond to backbone network export device 1 in method 300; the first route in method 700 may correspond to route 1" in method 300; the first backbone network export device in method 700 may correspond to backbone network export device 1 in method 300; the first information in method 700 may correspond to information 1 in method 300; the first binding relationship in method 700 may correspond to binding relationship 1 in method 300.

[0616] In a possible implementation, the method further includes: determining a first end-to-end path from the first site edge to the second site edge based on the first binding relationship, the first end-to-end path passing through the first backbone network ingress device and the first backbone network egress device.

[0617] The first end-to-end path mentioned in method 700 may be, for example, the end-to-end path 1 or the end-to-end path 2 mentioned in the above method embodiments.

[0618] In a possible implementation, the first information includes one or more of the following: a first segment identifier SID assigned by the first backbone network export device to the adjacency relationship between the first backbone network export device and the second site edge; a second SID of the first backbone network export device; a routing priority of the first backbone network export device; and a load sharing weight of the first backbone network export device.

[0619] When the method 700 is applied to the method 100 , the first SID in the method 700 may be SID1 in the method 100 ; and the second SID in the method 700 may be SID2 in the method 100 .

[0620] When the method 700 is applied to the method 200 , the first SID in the method 700 may be SID1 in the method 200 ; and the second SID in the method 700 may be SID2 in the method 200 .

[0621] When the method 700 is applied to the method 300 , the first SID in the method 700 may be SID1 in the method 300 ; and the second SID in the method 700 may be SID2 in the method 300 .

[0622] In a possible implementation, the first SID is an endpoint segment identifier SRv6 END.X SID of Internet Protocol version 6 segment routing having a cross-connection to a layer 3 adjacency array, and the second SID is an Internet Protocol version 6 segment routing endpoint segment identifier SRv6END.SID; or, the first SID is an adjacency segment identifier adj-SID, and the second SID is a node SID.

[0623] In one possible implementation, when the method 700 is applied to the above method 100, the second communication device is the second site edge, and the first route includes: a software-defined wide area network SD-WAN gateway information announcement route, and the SD-WAN gateway information announcement route includes at least one type-length value TLV, and the at least one TLV carries the first information.

[0624] In one possible implementation, the SD-WAN gateway information announcement route includes a first TLV, the value field of the first TLV is used to carry the first SID and / or second SID in the first information, the first TLV also includes a priority sub-TLV and / or a weight sub-TLV, the priority sub-TLV is used to carry the routing priority in the first information, and the weight sub-TLV is used to carry the load sharing weight in the first information.

[0625] The first TLV mentioned in method 700 may be the first TLV mentioned in method 100. Figure 4a MP_REACH_NLRI shown.

[0626] In a possible implementation, when the method 700 is applied to the above method 200, the second communication device is the second site edge, and the first route includes a virtual private network VPN route.

[0627] In a possible implementation manner, the VPN route includes a first metadata path attribute Metadata Path Attribute, and the first Metadata Path Attribute carries the first information.

[0628] The first Metadata Path Attribute in method 700 may correspond to Metadata Path Attribute2 in method 100 .

[0629] In a possible implementation manner, the first route further includes: service intent information.

[0630] In a possible implementation, the service intention information includes one or more of the following: a gateway that the first end-to-end path needs to pass through, a gateway that the first end-to-end path needs to bypass, and a quality of service parameter.

[0631] In a possible implementation manner, the first route includes a second Metadata Path Attribute, and the second Metadata Path Attribute includes the service intent information.

[0632] When the method 700 is applied to the above method 100 , the second Metadata Path Attribute in the method 700 may correspond to the Metadata Path Attribute1 in the method 100 .

[0633] When the method 700 is applied to the above method 200 , the second Metadata Path Attribute in the method 700 may correspond to the Metadata Path Attribute2 in the method 200 .

[0634] In a possible implementation, when the method 700 is applied to the above method 200, the second communication device is the first backbone network egress device, and the receiving of the first route announced by the second communication device includes: receiving the first route announced by the first backbone network egress device through the first backbone network ingress device.

[0635] The first backbone network access device in method 700 may correspond to backbone network access device 1 in method 300 .

[0636] In one possible implementation, the first route includes: the first SD-WAN gateway automatically discovers the route.

[0637] In one possible implementation, the method also includes: receiving a second route announced by a third communication device, the second route including second information of a second backbone network export device in the backbone network and an identifier of the second site edge, the second site edge accessing the backbone network through the second backbone network export device; according to the second route, obtaining a second binding relationship between the second site edge and the second backbone network export device.

[0638] When the method 700 is applied to the above method 100:

[0639] The third communication device in method 700 may correspond to the site edge2 in method 100; the second route in method 700 may correspond to route 2 in method 100; the second backbone network export device in method 700 may correspond to backbone network export device 2 in method 100; the second information in method 700 may correspond to information 2 in method 100; the second binding relationship in method 700 may correspond to binding relationship 2 in method 100.

[0640] When the method 700 is applied to the above method 200:

[0641] The third communication device in method 700 can correspond to the site edge2 in method 200; the second route in method 700 can correspond to route 1' in method 200; the second backbone network export device in method 700 can correspond to the backbone network export device 2 in method 200; the second information in method 700 can correspond to the information 2 in method 200; the second binding relationship in method 700 can correspond to the binding relationship 2 in method 200.

[0642] In a possible implementation, the method further includes: determining the routing priorities corresponding to the first backbone network egress device and the second backbone network egress device respectively; and / or determining the load sharing weights corresponding to the first backbone network egress device and the second backbone network egress device respectively.

[0643] In a possible implementation, the method further includes: determining, based on the second binding relationship, a second end-to-end path from the first site edge to the second site edge, wherein the second end-to-end path passes through the first backbone network ingress device and the second backbone network egress device.

[0644] The second end-to-end path in method 700 may be another end-to-end path from the first site edge to the second site edge that is different from the first end-to-end path. The second end-to-end path mentioned in method 700 may be, for example, the end-to-end path 1 or the end-to-end path 2 mentioned in the above method embodiments.

[0645] In a possible implementation, the method 700 can also be applied to the above method 400 or 500. In this case, the method also includes: receiving a third route sent by the first backbone network entry device, and the third route is used to notify the third information of the first backbone network entry device; according to the third route, obtaining the third binding relationship between the first site edge and the first backbone network entry device.

[0646] When the method 700 is applied to the above method 400:

[0647] The first site edge in method 700 may correspond to the site edge in method 400; the first backbone network entry device in method 700 may correspond to the gateway in method 400; the third route in method 700 may correspond to route 3 in method 400; the third information in method 700 may correspond to information 3 in method 400. The third binding relationship in method 700 may correspond to binding relationship 3 in method 400.

[0648] When the method 700 is applied to the above method 500:

[0649] The first site edge in method 700 may correspond to the site edge in method 500; the first backbone network entry device in method 700 may correspond to the gateway in method 500; the third route in method 700 may correspond to route 3' in method 500; the third information in method 700 may correspond to information 3 in method 500. The third binding relationship in method 700 may correspond to binding relationship 3 in method 500.

[0650] In one possible implementation, when the method 700 is applied to the above method 400, the third route is a route automatically discovered by the second SD-WAN gateway.

[0651] In a possible implementation, when the method 700 is applied to the above method 500, the third route is a BGP link state LS route.

[0652] In a possible implementation manner, the third information includes: a third SID allocated by the first backbone network entry device for the adjacency relationship between the first backbone network entry device and the first site edge, and / or a fourth SID of the first backbone network entry device.

[0653] When the method 700 is applied to the above method 400 , the third SID in the method 700 may correspond to SID3 in the method 400 , and the fourth SID in the method 700 may correspond to SID4 in the method 400 .

[0654] When the method 700 is applied to the above method 500 , the third SID in the method 700 may correspond to SID3 in the method 500 , and the fourth SID in the method 700 may correspond to SID4 in the method 500 .

[0655] In a possible implementation manner, the third route further includes intermediate gateway information, where the intermediate gateway information indicates at least one intermediate gateway between the first backbone network ingress device and the egress device in the backbone network.

[0656] The method 700 may also be applied to the above method 600. Specifically, the method further includes:

[0657] The first site edge receives the first service message, and 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 fourth information identifying the first backbone network entry device in the backbone network and fifth 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. The first site edge sends the second service message through the first end-to-end path.

[0658] The first site edge in method 700 may correspond to site edge1 in method 600; the first business message in method 700 may correspond to business message 1 in method 600; the second business message in method 700 may correspond to business message 2 in method 600; the first end-to-end path in method 700 may correspond to end-to-end path 1 in method 600; the fourth information in method 700 may correspond to information 1 in method 600; the fifth information in method 700 may correspond to information 2 in method 600; the first backbone network ingress device in method 700 may correspond to backbone network ingress device 1 in method 600; the first backbone network egress device in method 700 may correspond to backbone network egress device 1 in method 600; the second site edge in method 700 may correspond to site edge2 in method 600.

[0659] 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.

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

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

[0662] 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.

[0663] The first SR policy in method 700 may correspond to SR policy1 in method 600 .

[0664] 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 fourth information and the fifth information.

[0665] In a possible implementation, the fourth information is the first endpoint segment identifier END.SID1 of the first backbone network entry device, the fifth 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.

[0666] In a possible implementation, the fourth information is the first endpoint segment identifier END.SID1 of the first backbone network ingress device, and the fifth 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.

[0667] 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.

[0668] 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.

[0669] 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 fourth information and the fifth information, the fourth information is the first node SID of the first backbone network ingress device, and the fifth 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.

[0670] 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.

[0671] 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.

[0672] 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.

[0673] 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.

[0674] 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.

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

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

[0677] The first site edge encapsulates the path information of the third end-to-end path in the outer layer of the third service message to obtain the fourth service message; wherein the path information of the third end-to-end path includes the sixth information identifying the second backbone network entry device in the backbone network and the seventh information identifying the second backbone network exit device in the backbone network, the entry point of the third end-to-end path is the first site edge, the exit point of the third end-to-end path is the second site edge, the third end-to-end path passes through the second backbone network entry device and the second backbone network exit device, the first site edge multi-homes access to the first backbone network entry device and the second backbone network entry device, and the second site edge multi-homes access to the first backbone network exit device and the second backbone network exit device;

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

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

[0680] 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.

[0681] See also Fig.17 , which is a flow chart of another information notification method provided in an embodiment of the present application. Fig.17 The information notification method 800 shown can be applied to the above method 100 or method 200 or method 300 or method 400 or method 500.

[0682] Fig.17 The information notification method 800 shown can be applied to the second communication device.

[0683] In the embodiment of the present application, the method 800 may include the following S701-S702.

[0684] S801: Acquire a first route, where the first route includes first information of a first backbone network egress device in a backbone network and an identifier of a second site edge, where the second site edge accesses the backbone network through the first backbone network egress device.

[0685] S802: Notify the first route to a first site edge, and the first site edge accesses the backbone network through a first backbone network ingress device.

[0686] When the method 800 is applied to the method 100:

[0687] The first site edge in method 800 may correspond to site edge1 in method 100; the second site edge in method 800 may correspond to site edge2 in method 100; the first route in method 800 may correspond to route 1 in method 100; the first backbone network export device in method 800 may correspond to backbone network export device 1 in method 100; the first information in method 800 may correspond to information 1 in method 100.

[0688] When the method 800 is applied to the method 200:

[0689] The first site edge in method 800 may correspond to site edge1 in method 200; the second site edge in method 800 may correspond to site edge2 in method 200; the first route in method 800 may correspond to route 1' in method 100; the first backbone network export device in method 800 may correspond to backbone network export device 1 in method 200; the first information in method 800 may correspond to information 1 in method 200.

[0690] When the method 800 is applied to the method 300:

[0691] The first site edge in method 800 may correspond to site edge1 in method 300; the first route in method 800 may correspond to route 1" in method 300; the first backbone network egress device in method 800 may correspond to backbone network egress device 1 in method 300; the first information in method 800 may correspond to information 1 in method 300.

[0692] In a possible implementation, the first information includes one or more of the following: a first segment identifier SID assigned by the first backbone network export device to the adjacency relationship between the first backbone network export device and the second site edge; a second SID of the first backbone network export device; a routing priority of the first backbone network export device; and a load sharing weight of the first backbone network export device.

[0693] When the method 800 is applied to the method 100 , the first SID in the method 800 may be SID1 in the method 100 ; and the second SID in the method 800 may be SID2 in the method 100 .

[0694] When the method 800 is applied to the method 200 , the first SID in the method 800 may be SID1 in the method 200 ; and the second SID in the method 800 may be SID2 in the method 200 .

[0695] When the method 800 is applied to the method 300 , the first SID in the method 800 may be SID1 in the method 300 ; and the second SID in the method 800 may be SID2 in the method 300 .

[0696] In a possible implementation, the first SID is an endpoint segment identifier SRv6 END.X SID of Internet Protocol version 6 segment routing having a cross-connection to a layer 3 adjacency array, and the second SID is an Internet Protocol version 6 segment routing endpoint segment identifier SRv6END.SID; or, the first SID is an adjacency segment identifier adj-SID, and the second SID is a node SID.

[0697] In one possible implementation, when the method 800 is applied to the above method 100, the second communication device is the second site edge, and the first route includes: a software-defined wide area network SD-WAN gateway information announcement route, and the SD-WAN gateway information announcement route includes at least one type-length value TLV, and the at least one TLV carries the first information.

[0698] In one possible implementation, the SD-WAN gateway information announcement route includes a first TLV, the value field of the first TLV is used to carry the first SID and / or second SID in the first information, the first TLV also includes a priority sub-TLV and / or a weight sub-TLV, the priority sub-TLV is used to carry the routing priority in the first information, and the weight sub-TLV is used to carry the load sharing weight in the first information.

[0699] The first TLV mentioned in method 700 may be the first TLV mentioned in method 100. Figure 4a MP_REACH_NLRI shown.

[0700] In a possible implementation, when the method 800 is applied to the above method 200, the second communication device is the second site edge, and the first route includes a virtual private network VPN route.

[0701] In a possible implementation manner, the VPN route includes a first metadata path attribute Metadata Path Attribute, and the first Metadata Path Attribute carries the first information.

[0702] The first Metadata Path Attribute in method 800 may correspond to Metadata Path Attribute2 in method 100 .

[0703] In a possible implementation manner, the first route further includes: service intent information.

[0704] In a possible implementation, the service intent information includes one or more of the following: a gateway through which the service traffic needs to pass, a gateway through which the service traffic needs to bypass, and a quality of service parameter that needs to be met when transmitting the service traffic.

[0705] In a possible implementation manner, the first route includes a second Metadata Path Attribute, and the second Metadata Path Attribute includes the service intent information.

[0706] When the method 800 is applied to the above method 100 , the second Metadata Path Attribute in the method 800 may correspond to the Metadata Path Attribute1 in the method 100 .

[0707] When the method 800 is applied to the above method 200, the second Metadata PathAttribute in the method 800 may correspond to the Metadata Path Attribute2 in the method 200. In a possible implementation, when the method 800 is applied to the above method 200, the second communication device is the first backbone network egress device, and the notifying the first site edge of the first route includes: notifying the first route to the first site edge through the first backbone network ingress device.

[0708] The first backbone network access device in method 700 may correspond to backbone network access device 1 in method 300 .

[0709] In one possible implementation, the first route includes: the first SD-WAN gateway automatically discovers the route.

[0710] In one possible implementation, when the method 800 is applied to the above method 100 or 200, the method also includes: notifying the first site edge of a second route, the second route including second information of a second backbone network export device in the backbone network and an identifier of the second site edge, and the second site edge accesses the backbone network through the second backbone network export device.

[0711] When the method 800 is applied to the above method 100:

[0712] The second route in method 800 may correspond to route 2 in method 100; the second backbone network export device in method 800 may correspond to backbone network export device 2 in method 100; the second information in method 800 may correspond to information 2 in method 100; the second binding relationship in method 800 may correspond to binding relationship 2 in method 100.

[0713] When the method 800 is applied to the above method 200:

[0714] The second route in method 800 may correspond to route 1' in method 200; the second backbone network egress device in method 800 may correspond to backbone network egress device 2 in method 200; the second information in method 800 may correspond to information 2 in method 200; the second binding relationship in method 800 may correspond to binding relationship 2 in method 200.

[0715] In one possible implementation, when the second communication device is a second site edge, the method 800 can also be applied to the above method 400 or 500. In this case, the method also includes: receiving a third route sent by the first backbone network export device, and the third route is used to notify the third information of the first backbone network export device; according to the third route, obtaining the first binding relationship between the second site edge and the first backbone network export device.

[0716] When the method 800 is applied to the above method 400:

[0717] The second site edge in method 800 may correspond to the site edge in method 400; the first backbone network egress device in method 800 may correspond to the gateway in method 400; the third route in method 800 may correspond to route 3 in method 400; the third information in method 800 may correspond to information 3 in method 400. The third binding relationship in method 800 may correspond to binding relationship 3 in method 400.

[0718] When the method 800 is applied to the above method 500:

[0719] The second site edge in method 800 may correspond to the site edge in method 500; the first backbone network egress device in method 800 may correspond to the gateway in method 500; the third route in method 800 may correspond to route 3' in method 500; the third information in method 800 may correspond to information 3 in method 500. The third binding relationship in method 800 may correspond to binding relationship 3 in method 500.

[0720] In a possible implementation manner, the third information includes: a third SID allocated by the first backbone network egress device for the adjacency relationship between the first backbone network egress device and the second site edge, and / or a fourth SID of the first backbone network egress device.

[0721] When the method 800 is applied to the above method 400 , the third SID in the method 800 may correspond to SID3 in the method 400 , and the fourth SID in the method 800 may correspond to SID4 in the method 400 .

[0722] When the method 800 is applied to the above method 500 , the third SID in the method 800 may correspond to SID3 in the method 500 , and the fourth SID in the method 800 may correspond to SID4 in the method 500 .

[0723] In a possible implementation, when the method 800 can also be applied to the above method 400 or 500, the method also includes: receiving a fourth route sent by a second backbone network export device, the fourth route being used to announce fourth information of the second backbone network export device; and obtaining a second binding relationship between the second site edge and the second backbone network export device according to the fourth route.

[0724] In a possible implementation, the method further includes: determining the routing priorities corresponding to the first backbone network egress device and the second backbone network egress device respectively; and / or determining the load sharing weights corresponding to the first backbone network egress device and the second backbone network egress device respectively.

[0725] In one possible implementation, when the method 800 is applied to the above method 400, the third route is a route automatically discovered by the second SD-WAN gateway.

[0726] In a possible implementation, when the method 800 is applied to the above method 500, the third route is a BGP link state LS route, and the BGP LS route includes a second TLV, and the second TLV indicates that the third route is used to notify the third information of the first backbone network egress device.

[0727] The second TLV in method 800 may correspond to TLV1 in method 500 .

[0728] In a possible implementation manner, the second TLV is a role announcement TLV, and the role announcement TLV indicates that the role of the first backbone network egress device is a gateway.

[0729] In a possible implementation manner, the third route also includes intermediate gateway information, and the intermediate gateway information indicates at least one intermediate gateway between a backbone network ingress device in the backbone network and the first backbone network egress device.

[0730] In a possible implementation manner, the third route includes a third Metadata Path Attribute, and the third Metadata Path Attribute carries the intermediate gateway information.

[0731] When the method 800 is applied to the above method 400 , the third Metadata Path Attribute in the method 800 may correspond to the Metadata Path Attribute3 in the method 400 .

[0732] When the method 800 is applied to the above method 500 , the third Metadata Path Attribute in the method 800 may correspond to Metadata Path Attribute 4 in the method 500 .

[0733] In a possible implementation, the method further includes: determining gateway constraint information in the service intent information according to the intermediate gateway information, wherein the gateway constraint information indicates a gateway constraint condition that needs to be followed to determine a path to reach the second site edge.

[0734] In a possible implementation, the gateway constraint condition includes: a gateway that needs to be passed through, and / or a gateway that needs to be detoured.

[0735] See also Fig.18 , which is a flow chart of another information notification method provided in an embodiment of the present application. Fig.18 The information notification method 900 shown can be applied to the above method 300 or method 600.

[0736] Fig.18 The information notification method 900 shown can be applied to the first backbone network ingress device.

[0737] In the embodiment of the present application, the method 900 may include the following S901-S902.

[0738] S901: Receive a first route announced by a first backbone network egress device in the backbone network, wherein the first route includes information of the first backbone network egress device and an identifier of a second site edge, wherein the second site edge accesses the backbone network through the first backbone network egress device, and the first site edge accesses the backbone network through the first backbone network ingress device.

[0739] S902: Notify the first route to the first site edge.

[0740] When the method 900 is applied to the above method 300, the first backbone network egress device in method 900 corresponds to backbone network egress device 1 in method 300; the first route in method 900 may correspond to route 1" in method 300; the information of the first backbone network egress device in method 900 may correspond to information 1 in method 300; the second site edge in method 900 may correspond to site edge2 in method 300; the first backbone network entry device in method 900 may correspond to backbone network entry device 1 in method 300; the first site edge in method 900 may correspond to site edge1 in method 300.

[0741] When the method 900 is applied to the above method 600, the method 900 may further include the following contents:

[0742] The first backbone network ingress device receives a second service message from the first site edge edge, the payload of the second service message includes the 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 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.

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

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

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

[0746] 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.

[0747] 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.

[0748] 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.

[0749] 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.

[0750] 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.

[0751] 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.

[0752] 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.

[0753] 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.

[0754] 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.

[0755] 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.

[0756] 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.

[0757] 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.

[0758] 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.

[0759] 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.

[0760] 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.

[0761] 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.

[0762] See also Fig.19 , which is a flow chart of another information notification method provided in an embodiment of the present application. Fig.19 The information notification method 1000 shown can be applied to the above method 400 or method 500.

[0763] The information notification method 1000 may be applied to a site edge, and the method may include the following S1001 - S1002 .

[0764] S1001: Receive a first route sent by a first backbone network edge device, where the first route is used to notify first information of the first backbone network edge device, and the site edge accesses the backbone network through the first backbone network edge device.

[0765] S1002: Obtain a first binding relationship between the site edge and the first backbone network edge device according to the first route.

[0766] When the method 1000 is applied to the above method 400, the first backbone network edge device in method 1000 can correspond to the gateway in method 400; the site edge in method 1000 can correspond to the site edge in method 400; the first route in method 1000 can correspond to route 3 in method 400; the first information in method 1000 can correspond to information 3 in method 400; the first binding relationship in method 1000 can correspond to binding relationship 3 in method 400.

[0767] When the method 1000 is applied to the above method 500, the first backbone network edge device in method 1000 can correspond to the gateway in method 500; the site edge in method 1000 can correspond to the site edge in method 500; the first route in method 1000 can correspond to route 3' in method 500; the first information in method 1000 can correspond to information 3 in method 500; the first binding relationship in method 1000 can correspond to binding relationship 3 in method 500.

[0768] In a possible implementation manner, the first information includes: a first SID allocated by the first backbone network edge device for an adjacency relationship between the first backbone network edge device and the site edge, and / or a second SID of the first backbone network edge device.

[0769] When the method 1000 is applied to the above method 400 , the first SID in the method 1000 may correspond to SID3 in the method 400 ; the second SID in the method 1000 may correspond to SID4 in the method 400 .

[0770] When the method 1000 is applied to the above method 500 , the first SID in the method 1000 may correspond to SID3 in the method 500 ; the second SID in the method 1000 may correspond to SID4 in the method 500 .

[0771] In a possible implementation, the method further includes: receiving a second route sent by a second backbone network edge device, the second route being used to notify second information of the second backbone network edge device; and obtaining a second binding relationship between the site edge and the second backbone network edge device according to the second route.

[0772] In a possible implementation, the method further includes: determining the routing priorities corresponding to the first backbone network edge device and the second backbone network edge device respectively; and / or determining the load sharing weights corresponding to the first backbone network edge device and the second backbone network edge device respectively.

[0773] In one possible implementation, when the method 1000 is applied to the above method 400, the first route is an SD-WAN gateway automatic discovery route.

[0774] In a possible implementation, when the method 1000 is applied to the above method 500, the first route is a BGP link state LS route, and the BGP LS route includes a TLV, and the TLV indicates that the first route is used to notify the first information of the first backbone network edge device.

[0775] The TLV in method 1000 may correspond to TLV1 in method 500 .

[0776] In a possible implementation manner, the TLV is a role announcement TLV, and the role announcement TLV indicates that the role of the backbone network edge device is a gateway.

[0777] In a possible implementation manner, the first route also includes intermediate gateway information, and the intermediate gateway information indicates at least one intermediate gateway between a backbone network ingress device and a backbone network egress device in the backbone network.

[0778] In a possible implementation manner, the first route includes a Metadata Path Attribute, and the Metadata Path Attribute carries the intermediate gateway information.

[0779] When the method 1000 is applied to the above method 400 , the Metadata Path Attribute in the method 1000 may correspond to the Metadata Path Attribute3 in the method 400 .

[0780] When the method 1000 is applied to the above method 500 , the Metadata Path Attribute in the method 1000 may correspond to the Metadata Path Attribute 4 in the method 500 .

[0781] In a possible implementation, the method further includes: determining gateway constraint information in the service intent information according to the intermediate gateway information, wherein the gateway constraint information indicates a gateway constraint condition that needs to be followed to determine a path to reach the site edge.

[0782] In a possible implementation, the gateway constraint condition includes: a gateway that needs to be passed through, and / or a gateway that needs to be detoured.

[0783] See also Fig. 20 , which is a flow chart of another information notification method provided in an embodiment of the present application. Fig. 20 The information notification method 1100 shown can be applied to the above method 400 or method 500.

[0784] The information notification method 1100 may be applied to a backbone network edge device, and the method may include the following S1101 - S1102 .

[0785] S1101: Acquire a route, where the route is used to notify information of the backbone network edge device.

[0786] S1102: Send the route to the site edge, and the site edge accesses the backbone network through the backbone network edge device.

[0787] When the method 1100 is applied to the above method 400, the backbone network edge device in method 1100 can correspond to the gateway in method 400; the site edge in method 1100 can correspond to the site edge in method 400; the route in method 1100 can correspond to route 3 in method 400; the information in method 1100 can correspond to information 3 in method 400.

[0788] When the method 1100 is applied to the above method 500, the backbone network edge device in method 1100 can correspond to the gateway in method 500; the site edge in method 1100 can correspond to the site edge in method 500; the route in method 1100 can correspond to route 3' in method 400; the information in method 1100 can correspond to information 3 in method 500.

[0789] In a possible implementation manner, the information includes: a first SID allocated by the backbone network edge device for the adjacency relationship between the backbone network edge device and the site edge, and / or a second SID of the backbone network edge device.

[0790] When the method 1100 is applied to the above method 400 , the first SID in the method 1100 may correspond to SID3 in the method 400 ; the second SID in the method 1100 may correspond to SID4 in the method 400 .

[0791] When the method 1100 is applied to the above method 500 , the first SID in the method 1100 may correspond to SID3 in the method 500 ; the second SID in the method 1100 may correspond to SID4 in the method 500 .

[0792] In one possible implementation, when the method 1100 is applied to the above method 400, the route is an SD-WAN gateway automatic discovery route.

[0793] In a possible implementation, when the method 1100 is applied to the above method 500, the route is a BGP link state LS route, and the BGP LS route includes a TLV, and the TLV indicates that the route is used to notify the backbone network edge device of information.

[0794] The TLV in method 1100 may correspond to TLV1 in method 500 .

[0795] In a possible implementation manner, the TLV is a role announcement TLV, and the role announcement TLV indicates that the role of the backbone network edge device is a gateway.

[0796] In a possible implementation manner, the route further includes intermediate gateway information, and the intermediate gateway information indicates at least one intermediate gateway between a backbone network ingress device and a backbone network egress device in the backbone network.

[0797] In a possible implementation manner, the route includes a Metadata Path Attribute, and the Metadata Path Attribute carries the intermediate gateway information.

[0798] When the method 1100 is applied to the above method 400 , the Metadata Path Attribute in the method 1100 may correspond to the Metadata Path Attribute3 in the method 400 .

[0799] When the method 1100 is applied to the above method 500 , the Metadata Path Attribute in the method 1100 may correspond to the Metadata Path Attribute 4 in the method 500 .

[0800] The embodiment of the present application also provides a communication device for executing the information notification method provided in the above method embodiment. The communication device may include a transceiver unit and / or a processing unit; the transceiver unit is used to perform receiving and / or sending operations; the processing unit is used to perform operations other than receiving and / or sending operations. In one example, the transceiver unit includes a receiving unit and / or a sending unit, the receiving unit is used to perform a receiving operation, and the sending unit is used to perform a sending operation.

[0801] In a specific example, the structure of the communication device can be as follows: Fig.21a As shown, Fig.21a A schematic diagram of the structure of a communication device provided in an embodiment of the present application. Fig.21a As shown:

[0802] The communication device 2110 includes: a receiving unit 2111 and a processing unit 2112 .

[0803] In a specific example, the communication device 2110 may be applied to a first communication device as a first site edge. For this case:

[0804] The receiving unit 2111 is configured to receive a first route announced by a second communication device, wherein the first route includes first information of a first backbone network egress device and an identifier of a second site edge in the backbone network, wherein the second site edge accesses the backbone network through the first backbone network egress device, and the first site edge accesses the backbone network through a first backbone network ingress device;

[0805] The processing unit 2112 is used to obtain a first binding relationship between the second site edge and the first backbone network egress device according to the first route.

[0806] In a possible implementation, the processing unit 2112 is also used to: determine a first end-to-end path from the first site edge to the second site edge based on the first binding relationship, and the first end-to-end path passes through the first backbone network ingress device and the first backbone network egress device.

[0807] In a possible implementation, the first information includes one or more of the following: a first segment identifier SID assigned by the first backbone network export device to the adjacency relationship between the first backbone network export device and the second site edge; a second SID of the first backbone network export device; a routing priority of the first backbone network export device; and a load sharing weight of the first backbone network export device.

[0808] In a possible implementation, the first SID is an endpoint segment identifier SRv6 END.X SID of Internet Protocol version 6 segment routing having a cross-connection to a layer 3 adjacency array, and the second SID is an Internet Protocol version 6 segment routing endpoint segment identifier SRv6END.SID; or, the first SID is an adjacency segment identifier adj-SID, and the second SID is a node SID.

[0809] In one possible implementation, the second communication device is the second site edge, and the first route includes: a software-defined wide area network SD-WAN gateway information announcement route, and the SD-WAN gateway information announcement route includes at least one type-length value TLV, and the at least one TLV carries the first information.

[0810] In one possible implementation, the SD-WAN gateway information announcement route includes a first TLV, the value field of the first TLV is used to carry the first SID and / or second SID in the first information, the first TLV also includes a priority sub-TLV and / or a weight sub-TLV, the priority sub-TLV is used to carry the routing priority in the first information, and the weight sub-TLV is used to carry the load sharing weight in the first information.

[0811] In a possible implementation manner, the second communication device is the second site edge, and the first route includes a virtual private network VPN route.

[0812] In a possible implementation manner, the VPN route includes a first metadata path attribute Metadata Path Attribute, and the first Metadata Path Attribute carries the first information.

[0813] In a possible implementation manner, the first route further includes: service intent information.

[0814] In a possible implementation, the service intention information includes one or more of the following: a gateway that the first end-to-end path needs to pass through, a gateway that the first end-to-end path needs to bypass, and a quality of service parameter.

[0815] In a possible implementation manner, the first route includes a second Metadata Path Attribute, and the second Metadata Path Attribute includes the service intent information.

[0816] In a possible implementation, the second communication device is the first backbone network egress device, and the receiving unit 2111 is configured to: receive the first route announced by the first backbone network egress device through the first backbone network ingress device.

[0817] In one possible implementation, the first route includes: the first SD-WAN gateway automatically discovers the route.

[0818] In a possible implementation, the receiving unit 2111 is also used to: receive a second route announced by a third communication device, the second route including second information of a second backbone network export device in the backbone network and an identifier of the second site edge, and the second site edge accesses the backbone network through the second backbone network export device; the processing unit 2112 is also used to obtain a second binding relationship between the second site edge and the second backbone network export device according to the second route.

[0819] In a possible implementation, the processing unit 2112 is further used to: determine the routing priorities corresponding to the first backbone network egress device and the second backbone network egress device respectively; and / or determine the load sharing weights corresponding to the first backbone network egress device and the second backbone network egress device respectively.

[0820] In a possible implementation, the processing unit 2112 is also used to: determine, based on the second binding relationship, a second end-to-end path from the first site edge to the second site edge, where the second end-to-end path passes through the first backbone network ingress device and the second backbone network egress device.

[0821] In a possible implementation, the receiving unit 2111 is further used to: receive a third route sent by the first backbone network entry device, and the third route is used to notify the third information of the first backbone network entry device; the processing unit 2112 is further used to: obtain a third binding relationship between the first site edge and the first backbone network entry device according to the third route.

[0822] In one possible implementation, the third route is the second SD-WAN gateway automatic discovery route or the BGP link state LS route.

[0823] In a possible implementation manner, the third information includes: a third SID allocated by the first backbone network entry device for the adjacency relationship between the first backbone network entry device and the first site edge, and / or a fourth SID of the first backbone network entry device.

[0824] In a possible implementation manner, the third route further includes intermediate gateway information, where the intermediate gateway information indicates at least one intermediate gateway between the first backbone network ingress device and the egress device in the backbone network.

[0825] In a possible implementation, the communication device 2110 further includes a sending unit. For this case:

[0826] The receiving unit 2111 is also used to receive a first business message; the processing unit 2112 is also used to encapsulate the path information of the first end-to-end path in the outer layer of the first business message to obtain a second business message; wherein the path information of the first end-to-end path includes fourth information identifying a first backbone network entry device in the backbone network and fifth 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 business message through the first end-to-end path.

[0827] In one possible implementation, the first service message is used to carry a virtual private network VPN service, and the processing unit 2112 is also 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.

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

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

[0830] In one possible implementation, the processing unit 2112 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.

[0831] 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 fourth information and the fifth information.

[0832] In a possible implementation, the fourth information is the first endpoint segment identifier END.SID1 of the first backbone network entry device, the fifth 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.

[0833] In a possible implementation, the fourth information is the first endpoint segment identifier END.SID1 of the first backbone network ingress device, and the fifth 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.

[0834] 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.

[0835] 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.

[0836] 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 fourth information and the fifth information, the fourth information is the first node SID of the first backbone network ingress device, and the fifth 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.

[0837] 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.

[0838] 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.

[0839] 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.

[0840] 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.

[0841] 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.

[0842] In a possible implementation, the receiving unit 2111 is further used to receive a third service message; the processing unit 2112 is further used to encapsulate path information of a third end-to-end path in an outer layer of the third service message to obtain a fourth service message; wherein the path information of the third end-to-end path includes sixth information identifying a second backbone network ingress device in the backbone network and seventh information identifying a second backbone network egress device in the backbone network, the ingress endpoint of the third end-to-end path is the first site edge, the egress endpoint of the third end-to-end path is the second site edge, the third 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 third end-to-end path.

[0843] 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.

[0844] In yet another example, the communication device 2110 may be applied to a site edge. In this case:

[0845] A receiving unit 2111 is configured to receive a first route sent by a first backbone network edge device, where the first route is used to notify the first information of the first backbone network edge device, and the site edge accesses the backbone network through the first backbone network edge device;

[0846] The processing unit 2112 is configured to obtain a first binding relationship between the site edge and the first backbone network edge device according to the first route.

[0847] In a possible implementation manner, the first information includes: a first SID allocated by the first backbone network edge device for an adjacency relationship between the first backbone network edge device and the site edge, and / or a second SID of the first backbone network edge device.

[0848] In a possible implementation, the receiving unit 2111 is also used to: receive a second route sent by a second backbone network edge device, where the second route is used to notify the second information of the second backbone network edge device; the processing unit 2112 is also used to obtain a second binding relationship between the site edge and the second backbone network edge device based on the second route.

[0849] In a possible implementation, the processing unit 2112 is further used to: determine the routing priorities corresponding to the first backbone network edge device and the second backbone network edge device respectively; and / or determine the load sharing weights corresponding to the first backbone network edge device and the second backbone network edge device respectively.

[0850] In one possible implementation, the first route is an SD-WAN gateway automatic discovery route.

[0851] In a possible implementation manner, the first route is a BGP link state LS route, and the BGP LS route includes a TLV, where the TLV indicates that the first route is used to notify the first information of the first backbone network edge device.

[0852] In a possible implementation manner, the TLV is a role announcement TLV, and the role announcement TLV indicates that the role of the backbone network edge device is a gateway.

[0853] In a possible implementation manner, the first route also includes intermediate gateway information, and the intermediate gateway information indicates at least one intermediate gateway between a backbone network ingress device and a backbone network egress device in the backbone network.

[0854] In a possible implementation manner, the first route includes a Metadata Path Attribute, and the Metadata Path Attribute carries the intermediate gateway information.

[0855] In a possible implementation, the processing unit 2112 is further used to: determine gateway constraint information in the service intent information based on the intermediate gateway information, where the gateway constraint information indicates gateway constraint conditions that need to be followed to determine a path to reach the site edge.

[0856] In a possible implementation, the gateway constraint condition includes: a gateway that needs to be passed through, and / or a gateway that needs to be detoured.

[0857] In another specific example, the structure of the communication device can be as follows: Figure 21b As shown, Figure 21b This is a schematic diagram of the structure of another communication device provided in an embodiment of the present application. Figure 21b As shown:

[0858] The communication device 2120 includes: a processing unit 2121 and a sending unit 2122 .

[0859] In a specific example, the communication device 2120 may be applied to a second communication device. For this case:

[0860] The processing unit 2121 is configured to obtain a first route, where the first route includes first information of a first backbone network egress device in the backbone netwo...

Claims

1. An information notification method, It is characterized in that Applied to a first communication device as a first site edge, the method includes: Receive a first route announced by a second communication device, wherein the first route includes first information of a first backbone network egress device in the backbone network and an identifier of a second site edge, wherein the second site edge accesses the backbone network through the first backbone network egress device, and the first site edge accesses the backbone network through a first backbone network ingress device; According to the first route, a first binding relationship between the second site edge and the first backbone network egress device is obtained.

2. The method according to claim 1, It is characterized in that The method further comprises: According to the first binding relationship, a first end-to-end path from the first site edge to the second site edge is determined, where the first end-to-end path passes through the first backbone network ingress device and the first backbone network egress device.

3. The method according to claim 2, It is characterized in that The first information includes one or more of the following: The first backbone network egress device is allocated a first segment identifier SID for an adjacency relationship between the first backbone network egress device and the second site edge; A second SID of the first backbone network egress device; The routing priority of the first backbone network egress device; The load sharing weight of the first backbone network egress device.

4. The method according to claim 3, It is characterized in that The first SID is an Internet Protocol version 6 segment routing endpoint segment identifier SRv6 END.X SID having a cross-connection to a layer 3 adjacency array, and the second SID is an Internet Protocol version 6 segment routing endpoint segment identifier SRv6 END.SID; or, The first SID is an adjacency segment identifier adj-SID, and the second SID is a node SID.

5. The method according to claim 3 or 4, It is characterized in that The second communication device is the second site edge, and the first route includes: a software-defined wide area network SD-WAN gateway information announcement route, and the SD-WAN gateway information announcement route includes at least one type-length value TLV, and the at least one TLV carries the first information.

6. The method according to claim 5, It is characterized in that The SD-WAN gateway information announcement route includes a first TLV, the value field of the first TLV is used to carry the first SID and / or second SID in the first information, the first TLV also includes a priority sub-TLV and / or a weight sub-TLV, the priority sub-TLV is used to carry the routing priority in the first information, and the weight sub-TLV is used to carry the load sharing weight in the first information.

7. The method according to any one of claims 2 to 4, It is characterized in that The second communication device is the second site edge, and the first route includes a virtual private network VPN route.

8. The method according to claim 7, It is characterized in that The VPN route includes a first metadata path attribute Metadata Path Attribute, and the first Metadata Path Attribute carries the first information.

9. The method according to any one of claims 2 to 8, It is characterized in that The first route also includes: business intention information.

10. The method according to claim 9, It is characterized in that The business intention information includes one or more of the following: The gateways that the first end-to-end path needs to pass through, the gateways that the first end-to-end path needs to bypass, and quality of service parameters.

11. The method according to claim 9 or 10, It is characterized in that The first route includes a second Metadata Path Attribute, and the second Metadata Path Attribute includes the business intent information.

12. The method according to any one of claims 1 to 4, It is characterized in that The second communication device is the first backbone network egress device, and the receiving the first route announced by the second communication device includes: The first route announced by the first backbone network egress device is received through the first backbone network ingress device.

13. The method according to claim 12, It is characterized in that The first route includes: the first SD-WAN gateway automatically discovers the route.

14. The method according to any one of claims 1 to 13, It is characterized in that The method further comprises: receiving a second route announced by a third communication device, wherein the second route includes second information of a second backbone network egress device in the backbone network and an identifier of the second site edge, and the second site edge accesses the backbone network through the second backbone network egress device; According to the second route, a second binding relationship between the second site edge and the second backbone network egress device is obtained.

15. The method according to claim 14, It is characterized in that The method further comprises: Determine the routing priorities corresponding to the first backbone network egress device and the second backbone network egress device respectively; and / or, Determine the load sharing weights corresponding to the first backbone network egress device and the second backbone network egress device respectively.

16. The method according to claim 14 or 15, It is characterized in that The method further comprises: A second end-to-end path from the first site edge to the second site edge is determined according to the second binding relationship. The second end-to-end path passes through the first backbone network ingress device and the second backbone network egress device.

17. The method according to any one of claims 1 to 16, It is characterized in that The method further comprises: receiving a third route sent by the first backbone network ingress device, where the third route is used to notify the first backbone network ingress device of third information; According to the third route, a third binding relationship between the first site edge and the first backbone network ingress device is obtained.

18. The method according to claim 17, It is characterized in that The third route is the second SD-WAN gateway automatic discovery route or the BGP link state LS route.

19. The method according to claim 17, It is characterized in that The third information includes: The first backbone network entry device is a third SID allocated by the first backbone network entry device for the adjacency relationship between the first backbone network entry device and the first site edge, and / or a fourth SID of the first backbone network entry device.

20. The method according to claim 18 or 19, It is characterized in that The third route also includes intermediate gateway information, where the intermediate gateway information indicates at least one intermediate gateway between the first backbone network ingress device and the egress device in the backbone network.

21. The method according to any one of claims 2 to 11, It is characterized in that The method comprises: Receiving a first service message; Encapsulating 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 fourth information identifying a first backbone network ingress device in the backbone network and fifth 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, and the egress endpoint of the first end-to-end path is the second site edge; The second service message is sent through the first end-to-end path.

22. The method according to claim 11, It is 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.

23. The method according to claim 21 or 22, It is characterized in that The second service message also includes service intention information.

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

25. The method according to any one of claims 21 to 24, It is 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.

26. The method according to any one of claims 21 to 25, It is characterized in that 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 fourth information and the fifth information.

27. The method according to claim 26, It is characterized in that The fourth information is the first endpoint segment identifier END.SID1 of the first backbone network ingress device, the fifth 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.

28. The method according to claim 26, It is characterized in that The fourth information is the first endpoint segment identifier END.SID1 of the first backbone network entry device, and the fifth 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.

29. The method according to claim 27 or 28, It is characterized in that 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.

30. The method according to claim 27 or 28, It is 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.

31. The method according to any one of claims 21 to 25, It is 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 fourth information and the fifth information, the fourth information is the first node SID of the first backbone network ingress device, and the fifth 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.

32. The method according to claim 31, It is 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.

33. The method according to claim 31, It is 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.

34. The method according to any one of claims 26 to 30, It is 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.

35. The method according to any one of claims 36 to 30, It is 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.

36. The method according to claim 35, It is 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 21 to 36, It is characterized in that The method further comprises: Receiving a third service message; The path information of the third end-to-end path is encapsulated in the outer layer of the third service message to obtain the fourth service message; wherein the path information of the third end-to-end path includes sixth information identifying a second backbone network entry device in the backbone network and seventh information identifying a second backbone network exit device in the backbone network, the entry point of the third end-to-end path is the first site edge, the exit point of the third end-to-end path is the second site edge, the third 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, and 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 third end-to-end path.

38. The method according to any one of claims 21 to 37, It is 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.

39. A method for notifying information, It is characterized in that Applied to a second communication device, the method comprises: Acquire a first route, where the first route includes first information of a first backbone network egress device in the backbone network and an identifier of a second site edge, where the second site edge accesses the backbone network through the first backbone network egress device; The first route is notified to a first site edge, and the first site edge accesses the backbone network through a first backbone network ingress device.

40. The method according to claim 39, It is characterized in that The first information includes one or more of the following: The first backbone network egress device is allocated a first segment identifier SID for an adjacency relationship between the first backbone network egress device and the second site edge; A second SID of the first backbone network egress device; The routing priority of the first backbone network egress device; The load sharing weight of the first backbone network egress device.

41. The method according to claim 40, It is characterized in that The first SID is an Internet Protocol version 6 segment routing endpoint segment identifier SRv6END.X SID having a cross-connection to a layer 3 adjacency array, and the second SID is an Internet Protocol version 6 segment routing endpoint segment identifier SRv6 END.SID; or, The first SID is an adjacency segment identifier adj-SID, and the second SID is a node SID.

42. The method according to claim 40 or 41, It is characterized in that The second communication device is the second site edge, and the first route includes: a software-defined wide area network SD-WAN gateway information announcement route, and the SD-WAN gateway information announcement route includes at least one type-length value TLV, and the at least one TLV carries the first information.

43. The method according to claim 42, It is characterized in that The SD-WAN gateway information announcement route includes a first TLV, the value field of the first TLV is used to carry the first SID and / or second SID in the first information, the first TLV also includes a priority sub-TLV and / or a weight sub-TLV, the priority sub-TLV is used to carry the routing priority in the first information, and the weight sub-TLV is used to carry the load sharing weight in the first information.

44. The method according to claim 40 or 41, It is characterized in that The second communication device is the second site edge, and the first route includes a virtual private network VPN route.

45. The method according to claim 44, It is characterized in that The VPN route includes a first metadata path attribute Metadata Path Attribute, and the first Metadata Path Attribute carries the first information.

46. ​​The method according to any one of claims 39 to 45, It is characterized in that The first route also includes: business intention information.

47. The method according to claim 46, It is characterized in that The business intention information includes one or more of the following: The gateways that the business traffic needs to pass through, the gateways that the business traffic needs to bypass when transmitting, and the quality of service parameters that need to be met when transmitting the business traffic.

48. The method according to claim 46 or 47, It is characterized in that The first route includes a second Metadata Path Attribute, and the second Metadata Path Attribute includes the business intent information.

49. The method according to any one of claims 39 to 41, It is characterized in that The second communication device is the first backbone network egress device, and the notifying the first route to the first site edge includes: The first route is announced to the first site edge through the first backbone network ingress device.

50. The method according to claim 49, It is characterized in that The first route includes: the first SD-WAN gateway automatically discovers the route.

51. The method according to any one of claims 42 to 45, It is characterized in that The method further comprises: A second route is notified to the first site edge, where the second route includes second information of a second backbone network egress device in the backbone network and an identifier of the second site edge, and the second site edge accesses the backbone network through the second backbone network egress device.

52. The method according to any one of claims 42 to 45, It is characterized in that The method further comprises: receiving a third route sent by the first backbone network egress device, where the third route is used to notify the first backbone network egress device of third information; According to the third route, a first binding relationship between the second site edge and the first backbone network egress device is obtained.

53. The method according to claim 52, It is characterized in that The third information includes: a third SID allocated by the first backbone network egress device for the adjacency relationship between the first backbone network egress device and the second site edge, and / or a fourth SID of the first backbone network egress device.

54. The method according to claim 52 or 53, It is characterized in that The method further comprises: receiving a fourth route sent by a second backbone network egress device, wherein the fourth route is used to notify fourth information of the second backbone network egress device; According to the fourth route, a second binding relationship between the second site edge and the second backbone network egress device is obtained.

55. The method according to claim 54, It is characterized in that The method further comprises: Determine the routing priorities corresponding to the first backbone network egress device and the second backbone network egress device respectively; and / or, Determine the load sharing weights corresponding to the first backbone network egress device and the second backbone network egress device respectively.

56. The method according to any one of claims 52 to 55, It is characterized in that The third route is the route automatically discovered by the second SD-WAN gateway.

57. The method according to any one of claims 52 to 55, It is characterized in that The third route is a BGP link state LS route, and the BGP LS route includes a second TLV, and the second TLV indicates that the third route is used to notify third information of the first backbone network egress device.

58. The method according to claim 57, It is characterized in that The second TLV is a role announcement TLV, and the role announcement TLV indicates that the role of the first backbone network egress device is a gateway.

59. The method according to any one of claims 52 to 58, It is characterized in that The third route also includes intermediate gateway information, and the intermediate gateway information indicates at least one intermediate gateway between a backbone network ingress device in the backbone network and the first backbone network egress device.

60. The method according to claim 59, It is characterized in that The third route includes a third Metadata Path Attribute, and the third Metadata Path Attribute carries the intermediate gateway information.

61. The method according to claim 59 or 60, It is characterized in that The method further comprises: According to the intermediate gateway information, gateway constraint information in the service intention information is determined, where the gateway constraint information indicates a gateway constraint condition that needs to be followed in determining a path to reach the second site edge.

62. The method according to claim 61, It is characterized in that The gateway constraints include: Gateways that need to be passed through and / or gateways that need to be detoured.

63. A method for notifying information, It is characterized in that Applied to a first backbone network entry device in a backbone network, the method comprises: receiving a first route announced by a first backbone network egress device in the backbone network, wherein the first route includes information of the first backbone network egress device and an identifier of a second site edge, the second site edge accesses the backbone network through the first backbone network egress device, and the first site edge accesses the backbone network through the first backbone network ingress device; The first route is advertised to the first site edge.

64. The method according to claim 63, It is characterized in that The method further comprises: Receive a second service message from a first site edge edge, the payload of the second service message includes the first service message, 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; Processing 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.

65. The method according to claim 64, It is characterized in that The second service message also includes service intention information.

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

67. The method according to any one of claims 64 to 66, It is characterized in that 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.

68. The method according to claim 67, It is 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.

69. The method according to claim 67, It is 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.

70. The method according to claim 68 or 69, It is 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.

71. The method according to claim 68 or 69, It is 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.

72. The method according to claim 70, It is 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.

73. The method according to claim 71, It is 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.

74. The method according to any one of claims 64 to 66, It is 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.

75. The method according to claim 74, It is 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.

76. The method according to claim 74, It is 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.

77. The method according to claim 75, It is 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.

78. The method according to claim 76, It is 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.

79. The method according to any one of claims 67 to 73, It is 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.

80. The method according to any one of claims 67 to 73, It is 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.

81. The method according to claim 80, It is 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.

82. The method according to any one of claims 64 to 81, It is 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.

83. A communication device, It is 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 communication device as described in any one of claims 1-38; the processing unit is used to perform operations other than the receiving and / or sending operations performed by the first communication device as described in any one of claims 1-38; or, The transceiver unit is used to perform the receiving and / or sending operations performed by the second communication device as described in any one of claims 39-62; the processing unit is used to perform operations other than the receiving and / or sending operations performed by the second communication device as described in any one of claims 39-62; 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 63-82; 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 63-82.

84. A communication device, It is 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 described in any one of claims 1-82.

85. A communication system, It is characterized in that The system comprises: A first communication device for executing the method described in any one of claims 1 to 38 above, and a second communication device for executing the method described in any one of claims 39 to 62 above; or, A first communication device for executing the method described in any one of claims 1 to 38, and a first backbone network access device for executing the method described in any one of claims 63 to 82.

86. A computer readable storage medium, It is characterized in that The method comprises instructions or computer programs, which, when executed on a processor, implement the method described in any one of claims 1 to 82.

Images