Abnormity processing method and device based on service provider network

Abstract

The invention discloses an exception handling method and device based on a service provider network. The method comprises the following steps: under the condition that a routing address corresponding to a first user edge device is obtained, sending first indication information carrying the routing address and a routing label allocated by a first service edge device for the routing address to a second service edge device; sending second indication information carrying a routing label and a tunnel interface address corresponding to the first service edge device to a second service edge device; and when the first connection relationship is in the abnormal state, sending the abnormal response instruction to the second service edge device, which can be applied to a cloud technology scene. According to the method and the device, the technical problem of relatively low exception handling efficiency based on a service provider network is solved.

Description

Technical Field

[0001] This application relates to the field of computers, and more specifically, to an anomaly handling method and apparatus based on a service provider network. Background Technology

[0002] When a customer network communicates through a service provider network, link failures or anomalies may occur. However, to address such failures or anomalies, it's necessary to revoke the associated route labels one by one, and these revocation messages must propagate throughout the entire service provider network. This process can be time-consuming, especially with a large number of routes, leading to low efficiency in anomaly handling based on the service provider network. Therefore, there is a problem with the low efficiency of anomaly handling based on the service provider network.

[0003] There is currently no effective solution to the above problems. Summary of the Invention

[0004] This application provides an anomaly handling method and apparatus based on a service provider network to at least solve the technical problem of low efficiency in anomaly handling based on a service provider network.

[0005] According to one aspect of the embodiments of this application, an anomaly handling method based on a service provider network is provided, comprising: upon obtaining a routing address corresponding to a first user edge device, sending first indication information carrying the routing address and a routing label allocated by the first service edge device for the routing address to a second service edge device, wherein the first user edge device is a device located at the edge of a first customer network, the first service edge device is an edge router in the service provider network having a first connection relationship with the first user edge device, the second service edge device is an edge router in the service provider network having a second connection relationship with the second user edge device, the second user edge device is a device located at the edge of a second customer network, the first user edge device and the second user edge device are configured to communicate through the service provider network, and the first indication information is responded to by the second service edge device, setting the data to be sent to the routing address. The packet needs to be encapsulated using the aforementioned routing label; a second indication information carrying the aforementioned routing label and the tunnel interface address corresponding to the aforementioned first service edge device is sent to the aforementioned second service edge device, wherein the aforementioned tunnel interface address is used to indicate the logical interface of the tunnel path, the aforementioned logical interface is used to encapsulate and decapsulate the aforementioned data packet between the two ends of the aforementioned tunnel path, the two ends of the aforementioned tunnel path include the aforementioned first service edge device and the aforementioned second service edge device, the aforementioned tunnel path is used to transmit the encapsulated aforementioned data packet, the aforementioned second indication information is responded to by the aforementioned second service edge device, setting that the data packet encapsulated using the aforementioned routing label needs to be sent to the aforementioned tunnel interface address; in the case that the aforementioned first connection relationship is in an abnormal state, an abnormal response instruction is sent to the aforementioned second service edge device, wherein the aforementioned abnormal response instruction is used to instruct the aforementioned second service edge device to mark the indication information carrying the aforementioned routing label as abnormal information, and the indication information marked as abnormal information is set to prohibit response.

[0006] As an optional approach, sending the first indication information carrying the routing address and the routing label assigned to the routing address by the first service edge device to the second service edge device includes: sending the first indication information to the second service edge device via a multi-protocol border gateway protocol, wherein the multi-protocol border gateway protocol is used to transmit routing information between edge devices of the service provider network, and the routing information includes the routing address and the routing label; sending the second indication information carrying the routing label and the tunnel interface address corresponding to the first service edge device to the second service edge device includes: enabling a specific virtual private network address family in the multi-protocol border gateway protocol and sending the second indication information to the second service edge device, wherein the specific virtual private network address family is an address space or routing information set defined to support the tunnel interface address.

[0007] As an optional approach, before enabling a specific Virtual Private Network (VPN) address family in the aforementioned Multiprotocol Border Gateway Protocol (MPBTP) and sending the second indication information to the aforementioned second service edge device, the method further includes: extending the MPBTP to define the specific VPN address family and obtaining a specific information structure matching the specific VPN address family, wherein the specific information structure is used to define the standard format for transmitting information in the MPBTP after the specific VPN address family is enabled.

[0008] As an optional approach, after sending the abnormal response instruction to the second service edge device, the method further includes: when the first connection relationship is restored from the abnormal state to the normal state, a normal response instruction is sent to the second service edge device, wherein the normal response instruction is used to instruct the second service edge device to remove the marking of the abnormal information from the indication information carrying the routing label.

[0009] As an optional approach, in the process of sending the abnormal response instruction to the second service edge device, the method further includes: sending a backup activation instruction to the second service edge device, wherein the backup activation instruction is used to instruct the second service edge device to activate a backup tunnel path, the backup tunnel path being the transmission path that takes over the data packet when the instruction tunnel path fails.

[0010] According to another aspect of the embodiments of this application, another anomaly handling method based on a service provider network is provided, including: obtaining first indication information sent when a first service edge device obtains a routing address corresponding to a first user edge device, and responding to the first indication information, setting that data packets sent to the routing address need to be encapsulated using the routing label, wherein the first indication information carries the routing address and a routing label assigned to the routing address by the first service edge device, the first user edge device is a device located at the edge of a first customer network, the first service edge device is an edge router in the service provider network that has a first connection relationship with the first user edge device, the second service edge device is an edge router in the service provider network that has a second connection relationship with the second user edge device, the second user edge device is a device located at the edge of a second customer network, and the first user edge device and the second user edge device... The communication is configured to occur through the aforementioned service provider network; a second indication message is obtained from the first service edge device and responded to the second indication message; data packets encapsulated using the aforementioned routing label are configured to be sent to the tunnel interface address corresponding to the first service edge device; wherein the second indication message carries the aforementioned routing label and the second indication message of the tunnel interface address; the tunnel interface address is used to indicate the logical interface of the tunnel path; the logical interface is used to encapsulate and decapsulate the data packets between the two ends of the tunnel path; the two ends of the tunnel path include the first service edge device and the second service edge device; the tunnel path is used to transmit the encapsulated data packets; an abnormal response instruction is obtained from the first service edge device when the first connection relationship is in an abnormal state; and the indication message carrying the aforementioned routing label is marked as abnormal information; wherein the indication message marked as abnormal information is set to prohibit response.

[0011] As an optional solution, the data packets sent to the aforementioned routing address by the above configuration need to be encapsulated using the aforementioned routing label, including: creating a first entry in the routing table created by the aforementioned second service edge device, wherein the aforementioned first entry is used to associate the aforementioned routing address with the aforementioned routing label; the data packets encapsulated using the aforementioned routing label by the above configuration need to be sent to the aforementioned tunnel interface address, including: creating a second entry in the aforementioned created routing table, wherein the aforementioned second entry is used to associate the aforementioned tunnel interface address with the aforementioned routing label.

[0012] As an optional approach, marking the indication information carrying the aforementioned routing label as abnormal information includes: determining at least one specific entry carrying the aforementioned routing label from the aforementioned created routing table, and marking the indication information in the aforementioned at least one specific entry as the aforementioned abnormal information, wherein the aforementioned at least one specific entry includes the aforementioned first entry and the aforementioned second entry.

[0013] As an optional solution, the above-mentioned acquisition of the abnormal response instruction sent by the first service edge device when the first connection is in an abnormal state, and the marking of the indication information carrying the routing label as abnormal information, includes: acquiring the abnormal response instruction sent by the first service edge device when the first connection is in an abnormal state, setting a suppression time, wherein the suppression time is used to wait for a change in the state of the first connection; when the suppression time ends, and no normal response instruction sent by the first service edge device when the first connection is in a normal state is acquired, marking the indication information carrying the routing label as abnormal information, wherein the normal response instruction is used to instruct the second service edge device to cancel the marking of the abnormal information on the indication information carrying the routing label.

[0014] According to another aspect of the embodiments of this application, an anomaly handling apparatus based on a service provider network is also provided, comprising: a first sending unit, configured to, upon obtaining a routing address corresponding to a first user edge device, send first indication information carrying the routing address and a routing label allocated by the first service edge device for the routing address to a second service edge device, wherein the first user edge device is a device located at the edge of a first customer network, the first service edge device is an edge router in the service provider network having a first connection relationship with the first user edge device, the second service edge device is an edge router in the service provider network having a second connection relationship with the second user edge device, the second user edge device is a device located at the edge of a second customer network, the first user edge device and the second user edge device are configured to communicate through the service provider network, the first indication information is responded to by the second service edge device, and the data packet sent to the routing address needs to be configured to... The data packets are encapsulated using the aforementioned routing label; a second sending unit is configured to send second indication information carrying the aforementioned routing label and the tunnel interface address corresponding to the aforementioned first service edge device to the aforementioned second service edge device, wherein the aforementioned tunnel interface address is used to indicate the logical interface of the tunnel path, the aforementioned logical interface is used to encapsulate and decapsulate the aforementioned data packets between the two ends of the aforementioned tunnel path, the two ends of the aforementioned tunnel path include the aforementioned first service edge device and the aforementioned second service edge device, the aforementioned tunnel path is used to transmit the encapsulated aforementioned data packets, the aforementioned second indication information is responded to by the aforementioned second service edge device, setting that the data packets encapsulated using the aforementioned routing label need to be sent to the aforementioned tunnel interface address; a third sending unit is configured to send an abnormal response instruction to the aforementioned second service edge device when the aforementioned first connection relationship is in an abnormal state, wherein the aforementioned abnormal response instruction is used to instruct the aforementioned second service edge device to mark the indication information carrying the aforementioned routing label as abnormal information, and set the indication information marked as abnormal information to prohibit response.

[0015] As an optional solution, the first sending unit includes: a first sending module, configured to send the first indication information to the second service edge device via a multi-protocol border gateway protocol, wherein the multi-protocol border gateway protocol is used to transmit routing information between edge devices of the service provider network, and the routing information includes the routing address and the routing label; the second sending unit includes: a second sending module, configured to enable a specific virtual private network address family in the multi-protocol border gateway protocol and send the second indication information to the second service edge device, wherein the specific virtual private network address family is an address space or routing information set defined to support the tunnel interface address.

[0016] As an optional solution, the above-mentioned device further includes: an extension module, used to enable a specific virtual private network address family in the above-mentioned multi-protocol border gateway protocol, extend the above-mentioned multi-protocol border gateway protocol before sending the above-mentioned second indication information to the above-mentioned second service edge device, define the above-mentioned specific virtual private network address family, and obtain a specific information structure matching the above-mentioned specific virtual private network address family, wherein the above-mentioned specific information structure is used to define the standard format for transmitting information in the above-mentioned multi-protocol border gateway protocol after the above-mentioned specific virtual private network address family is enabled.

[0017] As an optional solution, the above-mentioned apparatus further includes: a fourth sending unit, configured to send a normal response instruction to the second service edge device after the above-mentioned abnormal response instruction has been sent to the second service edge device, and after the first connection relationship has been restored from the above-mentioned abnormal state to the normal state, wherein the above-mentioned normal response instruction is used to instruct the second service edge device to cancel the marking of the above-mentioned abnormal information by carrying the indication information carrying the above-mentioned routing label.

[0018] As an optional solution, the above apparatus further includes: a fifth sending unit, configured to send a backup activation instruction to the second service edge device during the process of sending the abnormal response instruction to the second service edge device, wherein the backup activation instruction is used to instruct the second service edge device to activate a backup tunnel path, the backup tunnel path being the transmission path that takes over the data packet when the indicated tunnel path fails.

[0019] According to another aspect of the embodiments of this application, another anomaly handling apparatus based on a service provider network is also provided, including: a first acquisition unit, configured to acquire first indication information sent by a first service edge device when it obtains a routing address corresponding to a first user edge device, and respond to the first indication information by setting that data packets sent to the routing address need to be encapsulated using the routing label, wherein the first indication information carries the routing address and a routing label assigned by the first service edge device to the routing address, the first user edge device is a device located at the edge of a first customer network, the first service edge device is an edge router in the service provider network that has a first connection relationship with the first user edge device, the second service edge device is an edge router in the service provider network that has a second connection relationship with the second user edge device, the second user edge device is a device located at the edge of a second customer network, and the first user edge device and the second user edge device are configured to be connected. The communication is conducted through the aforementioned service provider network; the second acquisition unit is configured to acquire the second indication information sent by the first service edge device, and respond to the second indication information, setting that the data packet encapsulated using the aforementioned routing label needs to be sent to the tunnel interface address corresponding to the first service edge device, wherein the aforementioned second indication information carries the aforementioned routing label and the second indication information of the aforementioned tunnel interface address, the aforementioned tunnel interface address is used to indicate the logical interface of the tunnel path, the aforementioned logical interface is used to encapsulate and decapsulate the aforementioned data packet between the two ends of the aforementioned tunnel path, the two ends of the aforementioned tunnel path include the aforementioned first service edge device and the aforementioned second service edge device, the aforementioned tunnel path is used to transmit the encapsulated aforementioned data packet; the third acquisition unit is configured to acquire the abnormal response instruction sent by the aforementioned first service edge device when the aforementioned first connection relationship is in an abnormal state, and mark the indication information carrying the aforementioned routing label as abnormal information, wherein the indication information marked as abnormal information is set to prohibit response.

[0020] As an optional solution, the first acquisition unit includes: a first acquisition module, configured to create a first entry in the routing table created by the second service edge device, wherein the first entry is used to associate the routing address with the routing label; the second acquisition unit includes: a second acquisition module, configured to create a second entry in the created routing table, wherein the second entry is used to associate the tunnel interface address with the routing label.

[0021] As an optional solution, the third acquisition unit includes: a first marking module, used to determine at least one specific entry carrying the route label from the route table created above, and to mark the indication information in the at least one specific entry as the abnormal information, wherein the at least one specific entry includes the first entry and the second entry.

[0022] As an optional solution, the third acquisition unit includes: a third acquisition module, configured to acquire the abnormal response instruction sent by the first service edge device when the first connection is in an abnormal state, and set a suppression time, wherein the suppression time is used to wait for a change in the state of the first connection; and a second marking module, configured to mark the indication information carrying the routing label as abnormal information when the suppression time ends and no normal response instruction sent by the first service edge device when the first connection is in a normal state is acquired, wherein the normal response instruction is used to instruct the second service edge device to cancel the marking of the abnormal information by removing the indication information carrying the routing label.

[0023] According to another aspect of the embodiments of this application, a computer program product or computer program is provided, which includes computer instructions stored in a computer-readable storage medium. A processor of an electronic device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the electronic device to perform the above-described exception handling method based on a service provider network.

[0024] According to another aspect of the embodiments of this application, an electronic device is also provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the above-described exception handling method based on a service provider network through the computer program.

[0025] In this embodiment, when the service provider network obtains the routing address of the first user edge device, it sends this routing address and its associated routing label to the second service edge device via first indication information. In this way, the second service edge device knows how to send data packets to this specific routing address (i.e., encapsulate them using a specific routing label).

[0026] Next, in this embodiment, the routing label and the tunnel interface address of the first serving edge device are sent to the second serving edge device via the second indication information. This makes it clear to the second serving edge device that all data packets encapsulated using this specific routing label should be sent to this tunnel interface address.

[0027] By directly configuring the tunnel interface, this embodiment avoids the need for complex route lookups and calculations for each data packet transmission. Because the tunnel interface has predefined the data packet transmission path, data packets can be forwarded to their destination more quickly, thereby improving data transmission efficiency.

[0028] Furthermore, if the first connection (i.e., the connection between the first user edge device and the first service edge device) becomes abnormal, this embodiment will immediately send an abnormal response command to the second service edge device. This command tells the second service edge device to mark all indication information carrying specific routing labels as abnormal information and to prohibit responding to these abnormal information.

[0029] By directly sending an anomaly response command to the second service edge device, the network can immediately stop responding to anomaly information, thereby avoiding unnecessary routing updates and propagation delays. This achieves the technical effect of improving the anomaly handling efficiency of service provider networks and solves the technical problem of low anomaly handling efficiency in service provider networks. Attached Figure Description

[0030] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0031] Figure 1 This is a schematic diagram of an application environment for an optional exception handling method based on a service provider network according to an embodiment of this application;

[0032] Figure 2 This is a schematic diagram of the flow of an optional exception handling method based on a service provider network according to an embodiment of this application;

[0033] Figure 3 This is a schematic diagram of an optional anomaly handling method based on a service provider network according to an embodiment of this application;

[0034] Figure 4 This is a schematic diagram of the flow of another optional exception handling method based on a service provider network according to an embodiment of this application;

[0035] Figure 5 This is a schematic diagram of another optional exception handling method based on a service provider network according to an embodiment of this application;

[0036] Figure 6 This is a schematic diagram of another optional exception handling method based on a service provider network according to an embodiment of this application;

[0037] Figure 7 This is a schematic diagram of another optional exception handling method based on a service provider network according to an embodiment of this application;

[0038] Figure 8 This is a schematic diagram of another optional exception handling method based on a service provider network according to an embodiment of this application;

[0039] Figure 9 This is a schematic diagram of an optional exception handling apparatus based on a service provider network according to an embodiment of this application;

[0040] Figure 10 This is a schematic diagram of another optional exception handling device based on a service provider network according to an embodiment of this application;

[0041] Figure 11 This is a schematic diagram of the structure of an optional electronic device according to an embodiment of this application. Detailed Implementation

[0042] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0043] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0044] For ease of understanding, the following terms are explained:

[0045] Cloud technology refers to a hosting technology that unifies a series of resources such as hardware, software, and networks within a wide area network or local area network to achieve data computing, storage, processing, and sharing.

[0046] Cloud technology is a collective term for network technologies, information technologies, integration technologies, management platform technologies, and application technologies applied to the cloud computing business model. It can form resource pools, providing flexible and convenient on-demand access. Cloud computing technology will become a crucial support. Backend services of technical network systems require substantial computing and storage resources, such as video websites, image websites, and many portal websites. With the rapid development and application of the internet industry, every item may have its own identification mark in the future, requiring transmission to backend systems for logical processing. Data at different levels will be processed separately, and various industry data will all require robust system support, which can only be achieved through cloud computing.

[0047] According to one aspect of the embodiments of this application, an anomaly handling method based on a service provider network is provided. Optionally, as an optional implementation, the above-described anomaly handling method based on a service provider network can be applied to, but is not limited to, situations such as... Figure 1 The environment shown may include, but is not limited to, user equipment 102 (first user edge device) and service device 112 (first service edge device). The user equipment 102 may include, but is not limited to, a display 104, a processor 106 and a memory 108, and the service device 112 includes a database 114 and a processing engine 116.

[0048] The specific process can be summarized in the following steps:

[0049] Step S102: User equipment 102 obtains the routing address corresponding to the first user edge device;

[0050] Step S104: Send the routing address to the service device 112 via network 110;

[0051] In steps S106-S110, the service device 112 assigns a routing label to the routing address through the processing engine 116, and further sends the first indication information carrying the routing address and the routing label to the second service edge device, and sends the second indication information carrying the routing label and the tunnel interface address corresponding to the first service edge device to the second service edge device, and sends an abnormal response command to the second service edge device if the first connection relationship between the first service edge device and the first user edge device is in an abnormal state.

[0052] In step S112, the routing results are sent to user equipment 102 via network 110. User equipment 102 displays the routing results on display 104 via processor 106 and stores the routing results in memory 108.

[0053] remove Figure 1Beyond the examples shown, the terminal devices described above can be terminal devices configured with a target client, including but not limited to at least one of the following: mobile phones (such as Android phones, iOS phones, etc.), laptops, tablets, PDAs, MIDs (Mobile Internet Devices), PADs, desktop computers, smart TVs, etc. The target client can be a video client, instant messaging client, browser client, educational client, etc. The networks described above can include, but are not limited to, wired networks and wireless networks. The wired networks include local area networks (LANs), metropolitan area networks (MANs), and wide area networks (WANs). The wireless networks include Bluetooth, Wi-Fi, and other networks that enable wireless communication. The server described above can be a single server, a server cluster consisting of multiple servers, or a cloud server. The above is merely an example, and no limitations are imposed in this embodiment.

[0054] Alternatively, as an alternative implementation method, such as Figure 2 As shown, the anomaly handling method based on the service provider network can be executed by an electronic device, such as... Figure 1 The user equipment or server shown includes the following specific steps:

[0055] S202, upon obtaining the routing address corresponding to the first user edge device, first indication information carrying the routing address and the routing label assigned to the routing address by the first service edge device is sent to the second service edge device. Here, the first user edge device is a device located at the edge of the first customer network, the first service edge device is an edge router in the service provider network with a first connection to the first user edge device, the second service edge device is an edge router in the service provider network with a second connection to the second user edge device, and the second user edge device is located at the edge of the second customer network. The first user edge device and the second user edge device are configured to communicate through the service provider network. The first indication information is responded to by the second service edge device, and the data packets sent to the routing address are encapsulated using routing labels.

[0056] S204, the second indication information carrying the routing label and the tunnel interface address corresponding to the first service edge device is sent to the second service edge device. The tunnel interface address is used to indicate the logical interface of the tunnel path. The logical interface is used to encapsulate and decapsulate data packets between the two ends of the tunnel path. The two ends of the tunnel path include the first service edge device and the second service edge device. The tunnel path is used to transmit encapsulated data packets. The second indication information is responded to by the second service edge device, which sets that data packets encapsulated using the routing label need to be sent to the tunnel interface address.

[0057] S206, if the first connection relationship is in an abnormal state, an abnormal response instruction is sent to the second service edge device, wherein the abnormal response instruction is used to instruct the second service edge device to mark the indication information carrying the routing label as abnormal information, and the indication information marked as abnormal information is set to prohibit response.

[0058] Optionally, in this embodiment, the above-described anomaly handling method based on the service provider network can be applied, but is not limited to, cloud technology scenarios. In a cloud technology environment, the service provider network typically carries a large amount of cloud computing service traffic, including virtual machine migration, data backup, and distributed application communication. Therefore, effectively handling network anomalies is crucial for ensuring the continuity and performance of cloud services.

[0059] First, user edge devices in a cloud environment are typically customer virtual machines or container instances, located at the edge of different cloud tenant networks. These edge devices connect to service edge devices in the service provider network (SPF) to facilitate cross-cloud tenant data communication. In this scenario, the SPF acts as a bridge for communication between cloud tenants.

[0060] When applying the above-described anomaly handling method based on the service provider network, when the first user edge device (i.e., a customer's virtual machine or container) needs to communicate with the second user edge devices of other cloud tenants, the first service edge device in the service provider network assigns a routing label and a tunnel interface address to the communication path. This label and address information is sent to the second service edge device via first and second indication information to ensure that data packets can be correctly transmitted through the tunnel path.

[0061] In cloud technology scenarios, networks are highly dynamic and complex. Events such as virtual machine migration and network topology changes can cause anomalies in the primary connectivity. In such cases, the first service edge device detects the anomaly and sends an anomaly response command to the second service edge device. Upon receiving the command, the second service edge device marks any indications related to the abnormal routing as abnormal and prohibits responding to these indications. This blocks any data packets attempting to be sent via the abnormal routing path, thus preventing invalid data packet transmission and potential performance loss in the network.

[0062] Furthermore, by tagging anomaly information, cloud service detection and management systems can quickly identify affected network paths and promptly trigger fault recovery mechanisms. This may include operations such as switching to backup paths, reassigning route labels, and initiating virtual machine migrations to minimize the impact of network anomalies on cloud services.

[0063] Therefore, applying the above-mentioned anomaly handling methods based on service provider networks to cloud technology scenarios can achieve effective detection and rapid fault response of cloud service networks, improving the reliability and performance of cloud services. This is of great significance for ensuring the continuity of cloud tenant services, optimizing the utilization of cloud computing resources, and enhancing user experience.

[0064] Optionally, in this embodiment, the first user edge is a device located at the edge of a first customer network (e.g., the internal network of a company or organization), which can be responsible for handling data traffic entering and leaving the customer network and is connected to the service provider network, serving as a bridge between the customer's internal network and the service provider network, and realizing communication and data exchange between the two networks.

[0065] Optionally, in this embodiment, the first service edge device is located in the service provider network, and the edge router directly connected to the first user edge device can be an access point between the service provider network and the customer network. It is responsible for receiving data packets from the first customer network and performing routing selection based on network layer information (such as IP address) to forward the data packets to their destination.

[0066] Optionally, in this embodiment, the second service edge device is an edge router directly connected to the second user edge device in the service provider network. It can also be an interface between the service provider network and another customer network, similar to the first service edge device, but the second service edge device processes data traffic related to the second customer network.

[0067] Optionally, in this embodiment, the second user edge device is a device located at the edge of the second customer network, similar to the first user edge device, but the second user edge device belongs to a different customer network, thereby realizing the connection and communication between the second customer network and the service provider network.

[0068] Optionally, in this embodiment, the routing address is the address used to make routing decisions in the network. It can be an IP address (in an IP network) or other types of network addresses that identify network devices or network segments so that data packets can be correctly routed to their destination based on these addresses.

[0069] Optionally, in this embodiment, the routing label can be understood as an identifier attached to a data packet for making fast forwarding decisions in the network. In an MPLS (Multiprotocol Label Switching) network, the routing label can be used to specify the forwarding path of a data packet, improve data packet forwarding efficiency, reduce the need to look up the routing table for each hop, and thus speed up data transmission.

[0070] Optionally, in this embodiment, the first indication information can be understood as information containing a routing address and a corresponding routing label, used to guide network devices (such as the second service edge device) on how to process and forward data packets, ensuring that data packets can be encapsulated and forwarded according to the correct path and label, thereby realizing communication between the first user edge device and the second user edge device.

[0071] Optionally, in this embodiment, the first customer network edge can be understood as the boundary or edge of the first customer network, that is, the place where it connects to the customer's own internal network and the service provider network. It can also be understood as the gateway for data to enter and exit the customer network, and it is also a key point for network security, stability, and performance management. The second customer network edge is similar to the first customer network edge and may belong to the same or different customer networks (e.g., the network of another company or organization).

[0072] Optionally, in this embodiment, the first / second connection relationship can be used to describe the connection relationship between edge devices of the service provider network (such as the first or second service edge device) and edge devices of the customer network (such as the first or second user edge device). This connection relationship is typically established through physical links or virtual connections and requires the configuration of corresponding routing and network policies to enable communication.

[0073] Optionally, in this embodiment, when a data packet needs to be sent to a specific routing address, the network device (such as the first serving edge device) encapsulates these data packets with corresponding routing labels. Alternatively, a header containing routing labels is added to the front of each data packet.

[0074] When the encapsulated data packets are transmitted through the network, intermediate routers can make fast forwarding decisions based on this label without needing to look up complex routing tables. This greatly improves the speed and efficiency of data packet forwarding. Furthermore, by using different labels, service provider networks can also implement advanced functions such as traffic isolation, prioritization, and load balancing.

[0075] Specifically, after the network obtains the routing address of the first user edge device located at the edge of the customer network, this embodiment generates first indication information containing this routing address and the corresponding routing label, and sends this information to another service edge device. The purpose of this process is to ensure that data packets can be correctly sent from the first user edge device to the second user edge device through the service provider network.

[0076] By sending initial indication information containing routing addresses and routing labels, service provider networks can quickly establish communication paths and ensure that data packets are accurately and efficiently forwarded from one customer network to another. This mechanism reduces routing convergence time and the possibility of network outages, improving network availability and quality of service. Furthermore, by using technologies such as routing labels, service provider networks can also achieve flexible traffic control and load balancing to meet the needs of different customers and applications.

[0077] To further illustrate, consider the optional assumption that Company A and Company B are located in different geographical locations but are connected through the same service provider network. Company A's network edge device (first user edge device) wants to communicate with Company B's network edge device (second user edge device). Edge routers (first service edge device and second service edge device) within the service provider network handle these communication requests. When Company A's device connects to the network, its routing address is obtained and a routing label is assigned. This routing address and label are encapsulated in first indication information and sent to another edge router in the service provider network to ensure that data packets are forwarded to Company B's device along the correct path.

[0078] Optionally, in this embodiment, the tunnel interface address can be understood as a network address used to uniquely identify a logical interface on the tunnel path. This address does not directly correspond to a physical network interface, but rather represents a virtual connection point established between the devices at both ends of the tunnel path. The tunnel interface address enables network devices (such as serving edge devices) to know where to encapsulate and decapsulate data packets so that they can be correctly transmitted on the tunnel path.

[0079] In this embodiment, the tunnel path can be understood as a logical connection, starting from a first service edge device and ending at a second service edge device. These two devices are located at the edge of the service provider network and are connected to the first and second customer networks, respectively. The tunnel path can be specifically used to transmit encapsulated data packets. Encapsulation typically includes adding routing labels and / or tunnel interface addresses to ensure that data packets can be transmitted in the network according to the specified path and method.

[0080] Optionally, in this embodiment, the second indication information can be understood as a signal or message carrying necessary routing and network configuration information to guide network devices on how to process and forward specific data packets. The second indication information ensures that the second serving edge device can correctly identify and process data packets from the first serving edge device, especially those packets that need to be transmitted through a specific tunnel path.

[0081] Optionally, in this embodiment, when a data packet needs to traverse a service provider network, especially when using tunneling technology (such as MPLS), the data packet is encapsulated with additional header information at the beginning of the tunnel path (such as the first service edge device). This process is called encapsulation. The encapsulated data packet is transmitted along the tunnel path until it reaches the end of the tunnel path (such as the second service edge device), where the additional header information is removed. This process is called decapsulation to restore the original data packet format.

[0082] Optionally, in this embodiment, a configuration is required on the second service edge device to ensure that packets encapsulated with specific routing labels are directed to the designated tunnel interface address. This configuration ensures that packets correctly enter the tunnel path and are decapsulated and further processed or forwarded at the end of the tunnel path (the second service edge device). In this way, the service provider network can efficiently transmit data between customer networks while maintaining packet integrity and correct routing.

[0083] Specifically, when data packets need to be transmitted between the first and second service edge devices, this embodiment uses specific tunnel interface addresses and routing labels to encapsulate and decapsulate the data packets. To ensure correct transmission, a second indication message carrying this information is sent to the second service edge device.

[0084] By sending a second indication message carrying routing labels and tunnel interface addresses, service provider networks can quickly establish tunnel paths and ensure that data packets are accurately transmitted between the first and second service edge devices. This mechanism improves network availability and quality of service, while also enhancing data security and privacy (because data packets are encapsulated during transmission). Furthermore, by using routing labels and tunneling technology, service provider networks can achieve flexible flow control and efficient resource management.

[0085] To further illustrate, consider two companies, A and B, located in different cities, connected through the same service provider network. To ensure secure and fast data packet transmission between these two companies, the service provider network might use MPLS (Multiprotocol Label Switching) technology to establish a tunnel path. In this process, the first service edge device generates a second indication message containing a route label and the tunnel interface address, and sends it to the second service edge device. Upon receiving this message, the second service edge device knows that all data packets encapsulated with this route label should be sent to the specified tunnel interface address.

[0086] Optionally, in network communication, when the connection between two network devices (such as a service edge device and a user edge device) is problematic and data cannot be transmitted normally, this state is referred to as an abnormal state in this embodiment. The abnormal state can be caused by physical link failure, configuration error, device failure, network congestion, etc.

[0087] Optionally, in this embodiment, the anomaly response instruction can be understood as a type of network signaling, generated and sent by the network device when a network connection anomaly is detected. The purpose of this instruction is to notify other network devices of the change in connection status and guide these devices to take appropriate measures to handle the anomaly.

[0088] To further illustrate, consider an optional scenario where the first customer network loses connection with the first serving edge device for some reason (such as a fiber optic cable break), causing the first connection to be in an abnormal state. In this case, the first serving edge device might detect this anomaly and generate an anomaly response command sent to the second serving edge device. This command tells the second serving edge device that any data packets carrying specific routing labels (which were originally intended to be transmitted through the first connection) should now be marked as abnormal information, and responses to such information should be prohibited.

[0089] Optionally, in network communication, when a data packet or information flow cannot be processed normally for some reason (such as a routing failure), this embodiment marks it as abnormal information so that the network management system or related equipment can identify it and take appropriate action.

[0090] Optionally, in this embodiment, prohibiting response means that after receiving a specific instruction, the network device stops responding to a certain type of data packet or request in order to prevent network congestion, avoid error propagation, or mitigate the impact of failure.

[0091] Specifically, when the first connection is in an abnormal state, this embodiment sends an abnormal response command to the second service edge device, enabling the network to react quickly to the anomaly. Upon receiving the command, the second service edge device marks data packets carrying specific routing tags as abnormal information and sets them to disable response. This mechanism helps prevent the spread of network faults, reduces unnecessary communication attempts, and thus maintains network stability and reliability. Simultaneously, it provides network administrators with an opportunity to quickly locate and resolve problems, improving the overall availability and quality of service of the network.

[0092] To further illustrate, consider an optional scenario where the connection (first interconnection) between the first serving edge device and the first customer network is interrupted due to a physical link failure. In this case, the first serving edge device detects the abnormal state and generates an abnormal response instruction. This instruction is sent to the second serving edge device, instructing it to mark all data packets carrying specific routing labels that should have been transmitted through the first interconnection as abnormal. In response, the second serving edge device marks these data packets as abnormal and is configured not to respond to them, thus preventing further escalation of the network problem.

[0093] It should be noted that when the service provider network obtains the routing address of the first user edge device, it sends this routing address and its associated routing label to the second service edge device via a first indication message. In this way, the second service edge device knows how to send data packets to this specific routing address (i.e., encapsulate them using a specific routing label).

[0094] Next, in this embodiment, the routing label and the tunnel interface address of the first serving edge device are sent to the second serving edge device via the second indication information. This makes it clear to the second serving edge device that all data packets encapsulated using this specific routing label should be sent to this tunnel interface address.

[0095] By directly configuring the tunnel interface, this embodiment avoids the need for complex route lookups and calculations for each data packet transmission. Because the tunnel interface has predefined the data packet transmission path, data packets can be forwarded to their destination more quickly, thereby improving data transmission efficiency.

[0096] Furthermore, if the first connection (i.e., the connection between the first user edge device and the first service edge device) becomes abnormal, this embodiment will immediately send an abnormal response command to the second service edge device. This command tells the second service edge device to mark all indication information carrying specific routing labels as abnormal information and to prohibit responding to these abnormal information.

[0097] By directly sending anomaly response commands to the second service edge device, the network can immediately stop responding to anomaly information, avoiding unnecessary routing updates and propagation delays, thereby achieving the technical effect of improving the efficiency of anomaly handling based on service provider networks.

[0098] To further illustrate, optional examples include... Figure 3As shown, upon obtaining the routing address corresponding to the first user edge device 302, first indication information carrying the routing address and the routing label assigned to the routing address by the first service edge device 304 is sent to the second service edge device 306. Here, the first user edge device 302 is a device located at the edge of the first customer network; the first service edge device 304 is an edge router in the service provider network with a first connection to the first user edge device 302; the second service edge device 306 is an edge router in the service provider network with a second connection to the second user edge device 308; and the second user edge device 308 is a device located at the edge of the second customer network. The first user edge device 302 and the second user edge device 308 are configured to communicate through the service provider network. The first indication information is responded to by the second service edge device 306, which sets the data packet to be sent to the routing address. Encapsulation using routing labels is required. A second indication message carrying the routing label and the tunnel interface address corresponding to the first service edge device 304 is sent to the second service edge device 306. The tunnel interface address indicates the logical interface of the tunnel path, which is used for encapsulating and decapsulating data packets between the two ends of the tunnel path. The two ends of the tunnel path include the first service edge device 304 and the second service edge device 306. The tunnel path is used to transmit encapsulated data packets. The second indication message is responded to by the second service edge device 306, which sets that data packets encapsulated using routing labels must be sent to the tunnel interface address. If the first connection relationship is in an abnormal state, an abnormal response instruction is sent to the second service edge device 306. This abnormal response instruction instructs the second service edge device 306 to mark the indication message carrying the routing label as abnormal information, and sets the marked abnormal information to disable response.

[0099] According to the embodiments provided in this application, when the routing address corresponding to the first user edge device is obtained, first indication information carrying the routing address and the routing label allocated by the first service edge device for the routing address is sent to the second service edge device. The first user edge device is a device located at the edge of the first customer network, the first service edge device is an edge router in the service provider network with a first connection relationship to the first user edge device, and the second service edge device is an edge router in the service provider network with a second connection relationship to the second user edge device. The second user edge device is located at the edge of the second customer network. The first user edge device and the second user edge device are configured to communicate through the service provider network. The first indication information is responded to by the second service edge device. The data packet sent to the routing address is encapsulated using a routing label. The first indication information carrying the routing label and the routing label allocated by the first service edge device are sent to the second service edge device. The second indication information corresponding to the tunnel interface address is sent to the second service edge device. The tunnel interface address is used to indicate the logical interface of the tunnel path. The logical interface is used to encapsulate and decapsulate data packets between the two ends of the tunnel path. The two ends of the tunnel path include the first service edge device and the second service edge device. The tunnel path is used to transmit encapsulated data packets. The second indication information is responded to by the second service edge device. Data packets encapsulated with routing labels are set to be sent to the tunnel interface address. In the case that the first connection relationship is in an abnormal state, an abnormal response instruction is sent to the second service edge device. The abnormal response instruction is used to instruct the second service edge device to mark the indication information carrying the routing label as abnormal information. The indication information marked as abnormal information is set to prohibit response, thereby achieving the purpose of avoiding unnecessary route updates and propagation delays, and thus realizing the technical effect of improving the abnormal handling efficiency based on the service provider network.

[0100] As an optional approach, first indication information carrying a routing address and a routing label assigned to the routing address by the first service edge device is sent to the second service edge device, including: sending the first indication information to the second service edge device via a multi-protocol border gateway protocol, wherein the multi-protocol border gateway protocol is used to transmit routing information between edge devices of a service provider network, and the routing information includes a routing address and a routing label;

[0101] Optionally, in this embodiment, Multiprotocol Border Gateway Protocol (MP-BGP) is an extension of Border Gateway Protocol (BGP) that supports the propagation of routing information for multiple network layer protocols (such as IPv4, IPv6, etc.). Between edge devices in a service provider network, MP-BGP is used to transmit routing information, including routing addresses and associated routing labels. Alternatively, MP-BGP can be understood as a protocol for transmitting routing information between autonomous systems, supporting multiple network layer protocols, and capable of transmitting routing information, including routing addresses and routing labels, between edge devices in a service provider network.

[0102] It should be noted that this embodiment uses the MP-BGP protocol to send first indication information carrying the routing address and routing label to the second serving edge device, enabling the network to achieve rapid routing information propagation and packet forwarding. The first serving edge device can determine the forwarding path of the packet based on the routing address and assign a routing label to that path. Then, it sends the first indication information containing this information to the second serving edge device via the MP-BGP protocol. After receiving this information, the second serving edge device can use it to prepare for forwarding the packet within the service provider network. This mechanism improves the network's forwarding performance and flexibility, enabling packets to reach their destination quickly and accurately.

[0103] To further illustrate, optionally assume that a first serving edge device receives a data packet destined for a device in a second customer network. The first serving edge device looks up the packet's routing table, determines its routing address, and assigns a routing label to that address. Then, the first serving edge device sends first indication information, containing the routing address and routing label, to the second serving edge device via the MP-BGP protocol. Upon receiving this first indication information, the second serving edge device can use it to prepare for forwarding the data packet within the service provider network.

[0104] As an optional approach, second indication information carrying a routing label and the tunnel interface address corresponding to the first service edge device is sent to the second service edge device. This includes: enabling a specific virtual private network address family in the multi-protocol border gateway protocol and sending the second indication information to the second service edge device, wherein the specific virtual private network address family is an address space or routing information set defined to support the tunnel interface address.

[0105] Optionally, in this embodiment, a Virtual Private Network (VPN) address family can be understood as a set of addresses or routing information defined in the Multiprotocol Border Gateway Protocol (MP-BGP) to support VPN routing and forwarding. VPN address families allow service providers to build logically isolated VPNs on public networks, providing secure, private network services to customers. Alternatively, a VPN address family can be understood as a set of addresses or routing information in MP-BGP used to support VPN routing and forwarding.

[0106] It should be noted that this embodiment enables the establishment of VPN tunnels and secure packet forwarding by enabling specific VPN address families in MP-BGP and sending second indication information carrying routing labels and tunnel interface addresses to the second service edge device. This mechanism allows service providers to offer logically isolated and secure VPN services to customers on public networks, meeting customers' needs for network security, privacy, and flexibility. Simultaneously, by using tunnel interface addresses and routing labels, the network can achieve fast and accurate packet forwarding and routing information updates, improving network performance and reliability.

[0107] To further illustrate, consider the optional assumption that a VPN tunnel needs to be established between the first and second serving edge devices to support secure communication between the first and second customer networks. In this process, the first serving edge device assigns an address to its tunnel interface and encapsulates this address and its associated routing label in second indication information. Then, by enabling a specific VPN address family in MP-BGP, the first serving edge device sends the second indication information to the second serving edge device. Upon receiving this information, the second serving edge device can use it to establish the corresponding VPN tunnel and prepare to forward data packets within the tunnel.

[0108] As an optional approach, before enabling a specific Virtual Private Network address family in the Multiprotocol Border Gateway Protocol (MPBTP) and sending the second indication information to the second serving edge device, the method further includes:

[0109] The Multiprotocol Border Gateway Protocol (MPBGP) is extended to define a specific Virtual Private Network (VPN) address family and obtain a specific information structure that matches the specific VPN address family. The specific information structure is used to define the standard format for transmitting information in the MPBGP after the specific VPN address family is enabled.

[0110] Optionally, in this embodiment, the extension of the Multiprotocol Border Gateway Protocol (MP-BGP) can refer to the addition or modification of functionality to the original protocol to adapt to new network requirements or technologies. In network technology, extending protocols is a common practice, allowing protocols to adapt to new application scenarios or support new features. Alternatively, MP-BGP extension can be understood as the functional addition or modification of the Multiprotocol Border Gateway Protocol, aimed at meeting specific network requirements or supporting new network technologies.

[0111] Optionally, in this embodiment, a specific information structure can refer to a data structure defined during protocol extension that specifies the standard format used by the protocol when transmitting information. This structure ensures consistency and interoperability when the protocol transmits information between different devices. Alternatively, a specific information structure can be understood as a data structure defined in protocol extension that specifies the standard format and rules for the protocol when transmitting information.

[0112] To further illustrate, consider an optional scenario where a service provider needs to offer a new VPN service to its customers, requiring a specific routing and forwarding mechanism. To achieve this, the service provider decides to extend the existing MP-BGP protocol. During the extension process, they define a new VPN address family and design a specific information structure for it. This information structure specifies how routing information related to this new VPN address family is transmitted within the MP-BGP protocol. When the first service edge device needs to send a second indication message to the second service edge device, it uses this new information structure to format this information, ensuring that the second service edge device can correctly parse and process it.

[0113] The embodiments provided in this application extend the MP-BGP protocol and define specific virtual private network address families and their matching specific information structures, enabling the network to achieve more flexible and efficient routing information propagation and packet forwarding. This extension allows service providers to customize routing policies according to customer needs and network environments, improving network adaptability and scalability. Simultaneously, by using a standard information structure to format routing information, it ensures that different devices can correctly parse and process this information, thereby guaranteeing network stability and reliability.

[0114] As an optional approach, after sending the exception response command to the second service edge device, the method further includes:

[0115] When the first connection relationship recovers from an abnormal state to a normal state, a normal response command is sent to the second service edge device. The normal response command is used to instruct the second service edge device to remove the marking of the abnormal information from the indication information carrying the routing label.

[0116] Optionally, in this embodiment, a normal response command can be relative to an abnormal response command, and is used to indicate that a specific network state or event has returned to normal during communication between network devices. In other words, a normal response command can be understood as a command used in network communication to indicate that the state has returned to normal or to cancel a previous abnormal state marker.

[0117] It should be noted that, in this embodiment, abnormal and normal response commands are one of the important mechanisms to ensure network stability and reliability. They allow network devices to quickly transmit information about changes in network status and thus take appropriate actions. Abnormal response commands can be used to trigger fault recovery mechanisms, notify other devices to adjust routes, etc.; while normal response commands can be used to restore the network to its normal operating state, clear previous fault indications, etc.

[0118] To further illustrate, consider an optional assumption that a VPN tunnel is established between the first and second service edge devices to transmit data packets from the client network. For some reason, the first service edge device detects an anomaly in its connection with the second service edge device and sends an anomaly response command to the second service edge device, informing it of the anomaly. This anomaly response command may cause the second service edge device to mark routing information associated with the first service edge device, indicating that this information may no longer be reliable. When the first service edge device detects that the anomaly has been resolved, i.e., the first connection has returned to normal, it sends a normal response command to the second service edge device. The purpose of this normal response command is to instruct the second service edge device to undo the previous anomaly marking of the routing information associated with the first service edge device, allowing this routing information to be trusted and used again.

[0119] Through the embodiments provided in this application, by sending anomaly response commands and normal response commands, the first and second service edge devices can work together to respond to network anomalies and recovery operations. Sending anomaly response commands allows the second service edge device to react quickly, such as switching to an alternate path or suspending certain services to avoid potential communication problems. Sending normal response commands ensures that the network can quickly return to normal operation after the anomaly is resolved, thereby minimizing the impact on users and network services. This mechanism improves network robustness and availability, providing users with a more stable and reliable network service experience.

[0120] As an optional approach, the method further includes the following steps in sending the exception response command to the second service edge device:

[0121] A backup activation command is sent to the second service edge device, wherein the backup activation command is used to instruct the second service edge device to activate the backup tunnel path, which is the transmission path that takes over the data packets when the indicated tunnel path fails.

[0122] Optionally, in this embodiment, the backup activation command can be an instruction sent to the network device when the primary tunnel path encounters a problem or fails, used to activate a previously configured backup tunnel path. Alternatively, the backup activation command can be understood as a specific instruction in network communication used to trigger the activation of the backup tunnel path when the primary tunnel path fails.

[0123] Optionally, in this embodiment, the backup tunnel path can be a pre-configured alternative path used to take over data transmission tasks when the main tunnel path fails. Alternatively, the backup tunnel path can be a pre-set alternative communication path that can quickly take over and ensure data transmission continuity when the main tunnel path fails.

[0124] It should be noted that configuring a backup tunnel path in this embodiment not only improves network availability but also ensures that critical data is not lost in the event of an unforeseen incident on the primary path. The selection and configuration of the backup path must be based on the network topology, traffic demands, and Quality of Service (QoS) requirements. Furthermore, to achieve rapid switching, the backup path can maintain similar bandwidth and latency characteristics to the primary path.

[0125] To further illustrate, consider the optional assumption that two service edge devices A and B transmit data packets via a primary tunnel path, while a backup tunnel path is configured in case the primary path fails. When device A detects a failure in the primary tunnel path, it not only sends an exception response command to device B to inform it of the failure, but also sends a backup activation command. Upon receiving the backup activation command, device B immediately activates the previously configured backup tunnel path, ensuring that data packets can continue to be transmitted through the backup path, thereby minimizing service interruption time caused by the primary path failure.

[0126] By sending a backup activation command to activate the backup tunnel path through the embodiments provided in this application, it can be ensured that data packets can still be effectively transmitted through the backup path when the primary tunnel path fails. This mechanism greatly improves the fault tolerance and availability of the network and reduces the risk of service interruption due to network failures. At the same time, by properly configuring and managing the backup tunnel path, network load balancing and resource optimization can also be achieved.

[0127] Alternatively, as another alternative implementation, such as Figure 4 As shown, the anomaly handling method based on the service provider network can be executed by an electronic device, such as... Figure 1 The user equipment or server shown includes the following specific steps:

[0128] S402, when the first serving edge device obtains the routing address corresponding to the first user edge device, it sends a first indication message and responds to the first indication message, setting the data packet sent to the routing address to be encapsulated with a routing label. The first indication message carries the routing address and the routing label assigned to the routing address by the first serving edge device. The first user edge device is a device located at the edge of the first customer network. The first serving edge device is an edge router in the service provider network that has a first connection relationship with the first user edge device. The second serving edge device is an edge router in the service provider network that has a second connection relationship with the second user edge device. The second user edge device is a device located at the edge of the second customer network. The first user edge device and the second user edge device are configured to communicate through the service provider network.

[0129] S404, obtain the second indication information sent by the first service edge device, and respond to the second indication information. Set the data packet encapsulated with the routing label to be sent to the tunnel interface address corresponding to the first service edge device. The second indication information carries the routing label and the second indication information of the tunnel interface address. The tunnel interface address is used to indicate the logical interface of the tunnel path. The logical interface is used to encapsulate and decapsulate the data packet between the two ends of the tunnel path. The two ends of the tunnel path include the first service edge device and the second service edge device. The tunnel path is used to transmit the encapsulated data packet.

[0130] S406, obtain the abnormal response instruction sent by the first service edge device when the first connection relationship is in an abnormal state, and mark the indication information carrying the routing label as abnormal information, wherein the indication information marked as abnormal information is set to prohibit response.

[0131] For specific implementation examples, please refer to the examples shown in the above-described exception handling method based on service provider network, which will not be repeated here.

[0132] According to the embodiments provided in this application, when the first serving edge device obtains the routing address corresponding to the first user edge device, it sends a first indication message and responds to the first indication message. It is set that the data packets sent to the routing address need to be encapsulated using routing labels. The first indication message carries the routing address and the routing label assigned to the routing address by the first serving edge device. The first user edge device is a device located at the edge of the first customer network. The first serving edge device is an edge router in the service provider network that has a first connection relationship with the first user edge device. The second serving edge device is an edge router in the service provider network that has a second connection relationship with the second user edge device. The second user edge device is a device located at the edge of the second customer network. The first user edge device and the second user edge device are configured to communicate through the service provider network. The first serving edge device sends a second indication message. The system receives an instruction message and responds with a second instruction message. It sets that data packets encapsulated with routing labels must be sent to the tunnel interface address corresponding to the first service edge device. The second instruction message carries a routing label and a second instruction message for the tunnel interface address. The tunnel interface address indicates the logical interface of the tunnel path, which is used for encapsulating and decapsulating data packets between the two ends of the tunnel path. The two ends of the tunnel path include the first service edge device and the second service edge device. The tunnel path is used to transmit encapsulated data packets. The system also receives an exception response command sent by the first service edge device when the first connection relationship is in an abnormal state, and marks the instruction message carrying the routing label as exception information. The exception information marked as exception information is set to disable response, thereby avoiding unnecessary route updates and propagation delays, and thus achieving the technical effect of improving the efficiency of exception handling based on the service provider network.

[0133] As an optional approach, the data packets sent to the routing address are to be encapsulated using routing labels, including: creating a first entry in the routing table created by the second service edge device, wherein the first entry is used to associate the routing address with the routing label;

[0134] As an optional approach, packets encapsulated with route labels are configured to be sent to the tunnel interface address. This includes creating a second entry in the created routing table, where the second entry is used to associate the tunnel interface address with the route label.

[0135] Optionally, in this embodiment, the routing table can be understood as a data table in a network device (such as a router or serving edge device) used to store routing information, containing key information such as the destination network address, next-hop address, and interface, used to guide the forwarding of data packets. Alternatively, the routing table is a table in a network device used to determine the forwarding path of data packets, containing a mapping relationship between network addresses and corresponding forwarding information.

[0136] Optionally, in this embodiment, the first entry and the second entry can refer to two entries in the routing table, where the first entry is used to associate a routing address with a routing label, and the second entry is used to associate a tunnel interface address with a routing label. Alternatively, the first entry is the entry in the routing table used to establish the mapping relationship between a routing address and a routing label; the second entry is the entry used to establish the mapping relationship between a tunnel interface address and the same routing label.

[0137] It should be noted that, in addition to the basic mapping of routing addresses and tunnel interface addresses, the routing table and entries in this embodiment may also include other information, such as priority, metric value, next-hop address, etc.

[0138] To illustrate further, suppose the second serving edge device needs to send data packets to a specific routing address, and these packets need to be encapsulated using a specific routing label. To achieve this, it first creates a first entry in its routing table, associating the destination routing address with the corresponding routing label. Thus, when data packets are sent to that routing address, they automatically carry this routing label.

[0139] Next, to ensure that these packets encapsulated with routing labels are correctly sent to the tunnel interface address, the second serving edge device creates a second entry in its routing table, associating the tunnel interface address with the same routing label. Thus, when a packet is ready to be sent, the device checks its routing label and, based on the information in the second entry, sends the packet to the correct tunnel interface address.

[0140] The embodiments provided in this application create corresponding entries in the routing table to associate routing addresses, tunnel interface addresses, and routing labels, enabling network devices to accurately encapsulate and forward data packets. This mechanism ensures that data packets are forwarded according to predetermined paths and rules during transmission, improving network reliability and performance. Furthermore, by dynamically updating and maintaining the routing table, network devices can adapt to changes in network topology and traffic fluctuations, achieving more flexible and efficient data transmission.

[0141] As an optional approach, indication information carrying routing labels can be marked as abnormal information, including:

[0142] Identify at least one specific entry carrying a route label from the created routing table, and mark the indication information in the at least one specific entry as abnormal information, wherein the at least one specific entry includes a first entry and a second entry.

[0143] Optionally, in this embodiment, a specific entry may refer to an entry in the routing table associated with a specific route label. These entries contain indication information related to the specific route, such as the route address, tunnel interface address, etc. Alternatively, a specific entry is a record in the routing table associated with a specific route label, used to guide the forwarding and processing of packets related to that label.

[0144] Optionally, in this embodiment, anomaly information marking can refer to marking certain indication information in the routing table as an abnormal state to indicate that there is a problem or failure in the route or tunnel associated with these indication information. Alternatively, anomaly information marking is a process in network management used to identify specific entries in the routing table as abnormal, typically involving changing the entry's state or adding additional marking information.

[0145] It should be noted that the anomaly labeling in this embodiment may involve more complex logic and operations. For example, network devices may need to determine how to label anomaly information based on the type and severity of the fault. Furthermore, after labeling anomaly information, network devices may also need to trigger alarms or notify administrators to take timely troubleshooting measures. Simultaneously, network devices also need to be able to process information labeled as anomaly to ensure that data packets can be correctly routed to alternative paths or subjected to other appropriate processing.

[0146] To further illustrate, optionally assume that the routing table of the second serving edge device contains a first entry and a second entry associated with a specific route label. When the device detects a failure in the route or tunnel associated with that route label, it performs an anomaly marking process. This process may involve traversing the routing table, finding all specific entries carrying that route label (i.e., the first and second entries), and marking the indication information in these entries as an anomaly. Thus, any subsequent packets attempting to use that route or tunnel will be informed of the failure and may be redirected to an alternative path or undergo other fault-handling operations.

[0147] The embodiments provided in this application mark indication information carrying specific routing labels as abnormal information, enabling network devices to quickly identify and respond to routing or tunnel failures. This mechanism helps reduce the impact of failures on network services and improves network availability and reliability. Simultaneously, by promptly notifying administrators and implementing alternative paths, it ensures that critical services can continue operating during failures, thereby maintaining the overall stability and performance of the network.

[0148] As an optional approach, the system obtains the abnormal response command sent by the first serving edge device when the first interconnection is in an abnormal state, and marks the indication information carrying the routing label as abnormal information, including:

[0149] S1-1, Obtain the abnormal response command sent by the first service edge device when the first connection relationship is in an abnormal state, and set the suppression time, wherein the suppression time is used to wait for the state of the first connection relationship to change;

[0150] S1-2, when the suppression time ends and no normal response instruction is received from the first service edge device when the first connection relationship is in a normal state, the indication information carrying the routing label is marked as abnormal information. The normal response instruction is used to instruct the second service edge device to remove the marking of the indication information carrying the routing label as abnormal information.

[0151] Optionally, in this embodiment, the suppression time can be a waiting period set after receiving an abnormal response command, used to observe whether the state of the first interconnected relationship will change, particularly whether it will recover from an abnormal state to a normal state. Alternatively, the suppression time is a parameter in network fault handling, used to temporarily refrain from performing certain operations (such as marking abnormal information) after receiving an abnormal signal, and instead wait for a period of time to observe changes in the network state.

[0152] It should be noted that the suppression time is set to prevent erroneous operations caused by brief network fluctuations or false alarms. By setting a reasonable suppression time, network devices can reduce misjudgments and unnecessary operations to a certain extent, thereby improving network stability and reliability.

[0153] To further illustrate, optionally assume that the first connection between the first and second serving edge devices fails for some reason, causing data transmission interruption. The first serving edge device detects this abnormal state and sends an abnormal response command to the second serving edge device. Upon receiving this command, the second serving edge device does not immediately mark the indication information carrying the relevant routing label as abnormal information, but instead sets a suppression time, such as 5 seconds. During these 5 seconds, the second serving edge device waits for a normal response command from the first serving edge device to confirm whether the fault has been resolved. If no normal response command is received after 5 seconds, then the second serving edge device will mark the indication information carrying the relevant routing label as abnormal information.

[0154] By setting a suppression time and determining whether to mark the indication information carrying the relevant routing label as abnormal information based on whether a normal response instruction is received after the suppression time expires, the second service edge device can more accurately identify and handle network faults. This mechanism helps reduce misjudgments and unnecessary operations, improving network stability and reliability. Furthermore, by reasonably configuring the length of the suppression time, network performance and availability can also be optimized to some extent.

[0155] As an optional solution, for ease of understanding, the above-mentioned anomaly handling method based on the service provider network is applied to the scenario of network-wide announcement of routing labels and tunnel interface status. This embodiment extends a new Virtual Private Network (VPN) address family on the basis of Multi-Protocol Border Gateway Protocol (MP-BGP) to announce the IP prefix and routing label information of the Virtual Tunnel Endpoints (VTEPs) of the Provider Edge (PE). The status information of the tunnel interface and label of the PE is announced to the entire network through the routing protocol, realizing automatic detection of tunnel and label changes across the entire network. The remote PE device realizes fast and dynamic convergence of local forwarding based on label routing and tunnel interface status, which greatly improves network availability.

[0156] Optionally, such as Figure 5 As shown, Customer Edge (CE) 1 advertises all local route prefixes, such as Net 1, to PE1 via a routing protocol. PE1 assigns Label 1 to all routes of CE1 and transmits the labeled routes to PE1 via MP-BGP through VPN protocols (such as VPNv4, VPNv6, etc.). Simultaneously, it enables VPN address families and transmits PE1's VTEP IP prefix and CE1's label value information to PE2. PE2 simultaneously receives both VPNv4 / v6 routes and VPN VTEP IP and Label routes.

[0157] During local VPNv4 / v6 activity verification, the VTEP IP and Label information under the VPN address family is checked to see if it was learned from the remote PE1. If it exists, the route is active and can be prioritized. When the link between CE1 and PE1 fails, PE1 automatically detects this and will first withdraw the route information of PE1's VTEP IP and Label advertised by the VPN address family. PE2's VPN address family will also withdraw in response. After withdrawal, all routes with that label learned locally by PE2 from CE1 will automatically become invalid, completing local fast convergence (VPN route convergence and VPNv4 / v6 route convergence do not affect each other. VPNv4 routes will continue to be withdrawn one by one according to the original protocol because T-VPN has already marked the route as inactive, and withdrawing VPNv4 routes does not affect the local route selection results).

[0158] Once the CE1 link is restored, VPN and VPNv4 / v6 will again advertise the new routes, ensuring that the original tunnel forwarding capability can be automatically restored after the routes are restored. If the failure is due to PE1 itself, a highly sensitive BFD linkage is configured in the peer of the VPN address family to quickly disable the peer and quickly converge all labels and tunnel interface routes advertised by that PE, achieving rapid detection of tunnel failures and completing rapid convergence (when convergence is performed by canceling routes through the underlay, the underlay may be unable to perform convergence because there may be network segment routes matching the VTE PIP).

[0159] Optionally, in an SDN network where a controller is deployed, there will be a large number of controller-injected scheduling routes used for traffic tuning. For example... Figure 6 As shown, the controller injects a scheduled route into Net 1, with the tunnel endpoint being VTEP1 of PE1 and Label 1, and the traffic is forwarded to CE1. When the link of CE1 fails, PE1 detects this and removes the routes VTEP1 and Label 1 from the VPN address family. Since the VPN removes the routes VTEP1 and Label 1, the injected Net 1 route becomes invalid, ensuring that the injected route will no longer be forwarded to PE1, ultimately leading to a black hole (many L3 VPNs do not support tunnel state awareness capabilities, but can use this routing information to transmit tunnel state and achieve local automatic convergence).

[0160] Once the CE1 link is restored, the VPN address family again advertises the routes for VTEP1 and Label 1. Net 1, injected by the controller, becomes active again, scheduling traffic to continue forwarding to CE1, thus achieving dynamic convergence. If manually configured static routes point to the tunnel interface for forwarding, automatic convergence can also be achieved using the above method, without needing to use IPSLA or BFD-based collaborative probe mechanisms for dynamic convergence. Excessive probe sessions would consume significant device CPU resources.

[0161] It should be noted that this embodiment uses the extended capabilities of MP-BGP to implement a new VPN address family, which is used to carry VTEP IP prefix (host routing) and label information for network-wide routing. The NLRI is of variable length, and a single packet can carry multiple NLRIs. The specific routing information structure definition is as follows: Figure 7 As shown, the VPN routing field is defined as follows: Figure 8 As shown.

[0162] To further illustrate, optionally, when a PE assigns a new Label, it automatically generates an MP_REACH_NLRI route for the VPN and advertises it to all MP-BGP Peer nodes. Upon receiving this, the Peer node re-verifies all local routes carrying labels, changes the status of labels matching the VPN information to active, and enters the route selection process. If ultimately selected, it sends the route to the forwarding plane, enabling tunnel forwarding capability for the label route. If the object assigning the Label fails (e.g., BGPPeer down), it generates an MP_UNREACH_NLRI route for the VPN and advertises it to the MP-BGP Peer. Upon receiving this, the Peer node revokes the routing information under its local VPN address family and re-verifies the local routes carrying labels. It changes the status of all revoked VTEP IPs and Labels to inactive, revokes all selected routes in batches, and quickly revokes the locally advertised label routes learned from PE1. Simultaneously, it changes the tunnel exit status corresponding to Label 1 forwarded to PE1 to down, completing rapid convergence of routes and forwarding.

[0163] The embodiments provided in this application transmit routing information for tunnel interfaces VTEP and Labels via VPN address families and advertise them within the MP-BGP network. This enables rapid batch route convergence at remote locations, significantly reducing the time for traffic black holes in scenarios where label routes fail (actual tests show convergence of 900,000 global routes within 10 seconds), thus improving network availability. Simultaneously, VPN address families can advertise tunnel availability through routes within the network, allowing remote devices to quickly perceive tunnel status and achieve dynamic convergence capabilities for injecting routes pointing to remote tunnels, resolving the route black hole problem.

[0164] It is understood that in the specific embodiments of this application, data such as user information are involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0165] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0166] According to another aspect of the embodiments of this application, a service provider network-based exception handling apparatus is also provided for implementing the above-described exception handling method based on a service provider network. For example... Figure 9 As shown, the device includes:

[0167] The first sending unit 902 is configured to, upon obtaining the routing address corresponding to the first user edge device, send first indication information carrying the routing address and a routing label assigned to the routing address by the first service edge device to the second service edge device. The first user edge device is a device located at the edge of the first customer network, the first service edge device is an edge router in the service provider network with a first connection to the first user edge device, the second service edge device is an edge router in the service provider network with a second connection to the second user edge device, and the second user edge device is located at the edge of the second customer network. The first user edge device and the second user edge device are configured to communicate through the service provider network. The first indication information is responded to by the second service edge device, and the data packet sent to the routing address is encapsulated using a routing label.

[0168] The second sending unit 904 is used to send second indication information carrying a routing label and the tunnel interface address corresponding to the first service edge device to the second service edge device. The tunnel interface address is used to indicate the logical interface of the tunnel path. The logical interface is used to encapsulate and decapsulate data packets between the two ends of the tunnel path. The two ends of the tunnel path include the first service edge device and the second service edge device. The tunnel path is used to transmit encapsulated data packets. The second indication information is responded to by the second service edge device, which sets that data packets encapsulated using routing labels need to be sent to the tunnel interface address.

[0169] The third sending unit 906 is used to send an abnormal response instruction to the second service edge device when the first connection relationship is in an abnormal state. The abnormal response instruction is used to instruct the second service edge device to mark the indication information carrying the routing label as abnormal information, and the indication information marked as abnormal information is set to prohibit response.

[0170] For specific implementation examples, please refer to the examples shown in the above-described exception handling method based on service provider network, which will not be repeated here.

[0171] As an optional solution, the first sending unit 902 includes: a first sending module, used to send first indication information to a second service edge device via a multi-protocol border gateway protocol, wherein the multi-protocol border gateway protocol is used to transmit routing information between edge devices of a service provider network, and the routing information includes a routing address and a routing label;

[0172] The second sending unit 904 includes: a second sending module, used to enable a specific virtual private network address family in a multi-protocol border gateway protocol and send second indication information to a second serving edge device, wherein the specific virtual private network address family is an address space or routing information set defined to support tunnel interface addresses.

[0173] For specific implementation examples, please refer to the examples shown in the above-described exception handling method based on service provider network, which will not be repeated here.

[0174] As an optional solution, the device also includes:

[0175] An extension module is used to enable a specific virtual private network address family in the multi-protocol border gateway protocol. Before sending the second indication information to the second serving edge device, the multi-protocol border gateway protocol is extended to define the specific virtual private network address family and obtain a specific information structure that matches the specific virtual private network address family. The specific information structure is used to define the standard format for transmitting information in the multi-protocol border gateway protocol after the specific virtual private network address family is enabled.

[0176] For specific implementation examples, please refer to the examples shown in the above-described exception handling method based on service provider network, which will not be repeated here.

[0177] As an optional solution, the device also includes:

[0178] The fourth sending unit is used to send a normal response instruction to the second service edge device after the abnormal response instruction has been sent to the second service edge device, in the case that the first connection relationship has been restored from the abnormal state to the normal state. The normal response instruction is used to instruct the second service edge device to remove the marking of the abnormal information from the indication information carrying the routing label.

[0179] For specific implementation examples, please refer to the examples shown in the above-described exception handling method based on service provider network, which will not be repeated here.

[0180] As an optional solution, the device also includes:

[0181] The fifth sending unit is used to send a backup activation instruction to the second service edge device during the process of sending an abnormal response instruction to the second service edge device. The backup activation instruction is used to instruct the second service edge device to activate the backup tunnel path, which is the transmission path that takes over the data packet when the indicated tunnel path fails.

[0182] For specific implementation examples, please refer to the examples shown in the above-described exception handling method based on service provider network, which will not be repeated here.

[0183] According to another aspect of the embodiments of this application, another service provider network-based exception handling apparatus for implementing the above-described service provider network-based exception handling method is also provided. Figure 10 As shown, the device includes:

[0184] The first acquisition unit 1002 is used to acquire the first indication information sent by the first service edge device when it obtains the routing address corresponding to the first user edge device, and respond to the first indication information. It sets that the data packets sent to the routing address need to be encapsulated with routing labels. The first indication information carries the routing address and the routing label assigned by the first service edge device to the routing address. The first user edge device is a device located at the edge of the first customer network. The first service edge device is an edge router in the service provider network that has a first connection relationship with the first user edge device. The second service edge device is an edge router in the service provider network that has a second connection relationship with the second user edge device. The second user edge device is a device located at the edge of the second customer network. The first user edge device and the second user edge device are configured to communicate through the service provider network.

[0185] The second acquisition unit 1004 is used to acquire the second indication information sent by the first service edge device, and respond to the second indication information to set that the data packet encapsulated with the routing label needs to be sent to the tunnel interface address corresponding to the first service edge device. The second indication information carries the routing label and the second indication information of the tunnel interface address. The tunnel interface address is used to indicate the logical interface of the tunnel path. The logical interface is used to encapsulate and decapsulate the data packet between the two ends of the tunnel path. The two ends of the tunnel path include the first service edge device and the second service edge device. The tunnel path is used to transmit the encapsulated data packet.

[0186] The third acquisition unit 1006 is used to acquire the abnormal response instruction sent by the first service edge device when the first connection relationship is in an abnormal state, and to mark the indication information carrying the routing label as abnormal information, wherein the indication information marked as abnormal information is set to prohibit response.

[0187] For specific implementation examples, please refer to the examples shown in the above-described exception handling method based on service provider network, which will not be repeated here.

[0188] As an optional solution, the first acquisition unit 1002 includes: a first acquisition module, used to create a first entry in the routing table created by the second service edge device, wherein the first entry is used to associate a routing address with a routing label;

[0189] The second acquisition unit 1004 includes: a second acquisition module, used to create a second entry in the created routing table, wherein the second entry is used to associate the tunnel interface address with the routing label.

[0190] For specific implementation examples, please refer to the examples shown in the above-described exception handling method based on service provider network, which will not be repeated here.

[0191] As an optional solution, the third acquisition unit 1006 includes:

[0192] The first marking module is used to determine at least one specific entry carrying a route label from the created routing table and mark the indication information in the at least one specific entry as abnormal information, wherein the at least one specific entry includes a first entry and a second entry.

[0193] For specific implementation examples, please refer to the examples shown in the above-described exception handling method based on service provider network, which will not be repeated here.

[0194] As an optional solution, the third acquisition unit 1006 includes:

[0195] The third acquisition module is used to acquire information about the first service edge device being in an abnormal state in the first interconnection relationship, the abnormal response command sent, and to set a suppression time, wherein the suppression time is used to wait for the state of the first interconnection relationship to change.

[0196] The second marking module is used to mark the indication information carrying the routing label as abnormal information when the suppression time ends and no normal response instruction is received from the first service edge device when the first connection relationship is in a normal state. The normal response instruction is used to instruct the second service edge device to remove the marking of the indication information carrying the routing label as abnormal information.

[0197] For specific implementation examples, please refer to the examples shown in the above-described exception handling method based on service provider network, which will not be repeated here.

[0198] According to another aspect of the embodiments of this application, an electronic device for implementing the above-described anomaly handling method based on a service provider network is also provided. This electronic device may, but is not limited to, […]. Figure 1 The user equipment 112 or service equipment 112 shown in the figure, in this embodiment, is an electronic device as an example of user equipment 112, and further as follows: Figure 11 As shown, the electronic device includes a memory 1102 and a processor 1104. The memory 1102 stores a computer program, and the processor 1104 is configured to execute the steps of any of the above method embodiments via the computer program.

[0199] Optionally, in this embodiment, the aforementioned electronic device may be located in at least one of a plurality of network devices in a computer network.

[0200] Optionally, in this embodiment, the processor can be configured to perform the following steps via a computer program:

[0201] S2-1, upon obtaining the routing address corresponding to the first user edge device, first indication information carrying the routing address and the routing label assigned to the routing address by the first service edge device is sent to the second service edge device. Here, the first user edge device is a device located at the edge of the first customer network, the first service edge device is an edge router in the service provider network that has a first connection relationship with the first user edge device, the second service edge device is an edge router in the service provider network that has a second connection relationship with the second user edge device, and the second user edge device is a device located at the edge of the second customer network. The first user edge device and the second user edge device are configured to communicate through the service provider network. The first indication information is responded to by the second service edge device. It is set that the data packet sent to the routing address needs to be encapsulated using a routing label.

[0202] S2-2, the second indication information carrying the routing label and the tunnel interface address corresponding to the first service edge device is sent to the second service edge device. The tunnel interface address is used to indicate the logical interface of the tunnel path. The logical interface is used to encapsulate and decapsulate data packets between the two ends of the tunnel path. The two ends of the tunnel path include the first service edge device and the second service edge device. The tunnel path is used to transmit encapsulated data packets. The second indication information is responded to by the second service edge device, which sets that data packets encapsulated using the routing label need to be sent to the tunnel interface address.

[0203] S2-3, if the first connection is in an abnormal state, an abnormal response command is sent to the second serving edge device. This abnormal response command instructs the second serving edge device to mark the indication information carrying the routing label as abnormal information, and sets the indication information marked as abnormal to a no-response mode. Alternatively,

[0204] S3-1, when the first serving edge device obtains the routing address corresponding to the first user edge device, it sends a first indication message and responds to the first indication message. It sets that the data packets sent to the routing address need to be encapsulated with routing labels. The first indication message carries the routing address and the routing label assigned by the first serving edge device to the routing address. The first user edge device is a device located at the edge of the first customer network. The first serving edge device is an edge router in the service provider network that has a first connection relationship with the first user edge device. The second serving edge device is an edge router in the service provider network that has a second connection relationship with the second user edge device. The second user edge device is a device located at the edge of the second customer network. The first user edge device and the second user edge device are configured to communicate through the service provider network.

[0205] S3-2, Obtain the second indication information sent by the first service edge device, and respond to the second indication information. Set the data packet encapsulated with the routing label to be sent to the tunnel interface address corresponding to the first service edge device. The second indication information carries the routing label and the second indication information of the tunnel interface address. The tunnel interface address is used to indicate the logical interface of the tunnel path. The logical interface is used to encapsulate and decapsulate the data packet between the two ends of the tunnel path. The two ends of the tunnel path include the first service edge device and the second service edge device. The tunnel path is used to transmit the encapsulated data packet.

[0206] S3-3, obtain the abnormal response instruction sent by the first service edge device when the first connection relationship is in an abnormal state, and mark the indication information carrying the routing label as abnormal information, wherein the indication information marked as abnormal information is set to prohibit response.

[0207] Alternatively, as those skilled in the art will understand, Figure 11 The structure shown is for illustrative purposes only. Figure 11 This does not limit the structure of the aforementioned electronic devices. For example, the electronic device may also include components that are more... Figure 11 The more or fewer components shown (such as network interfaces, etc.), or having the same Figure 11 The different configurations shown.

[0208] The memory 1102 can be used to store software programs and modules, such as the program instructions / modules corresponding to the service provider network-based exception handling method and apparatus in this embodiment. The processor 1104 executes various functional applications and data processing by running the software programs and modules stored in the memory 1102, thereby implementing the aforementioned service provider network-based exception handling method. The memory 1102 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 1102 may further include memory remotely located relative to the processor 1104, and these remote memories can be connected to electronic devices via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof. Specifically, the memory 1102 may be used, but is not limited to, to store first indication information, second indication information, and exception response instructions, etc. As an example, such as... Figure 11 As shown, the memory 1102 may include, but is not limited to, the first sending unit 902, the second sending unit 904, and the third sending unit 906 in the above-mentioned service provider network-based exception handling device, or... Figure 11 The first acquisition unit 1002, the second acquisition unit 1004, and the third acquisition unit 1006 are not shown in the diagram. In addition, other module units, including but not limited to those in the above-described anomaly handling device based on a service provider network, may also be included, but will not be described further in this example.

[0209] Optionally, the transmission device 1106 described above is used to receive or send data via a network. Specific examples of the network described above may include wired networks and wireless networks. In one example, the transmission device 1106 includes a Network Interface Controller (NIC), which can be connected to other network devices and a router via a network cable to communicate with the Internet or a local area network. In another example, the transmission device 1106 is a radio frequency (RF) module, used for wireless communication with the Internet.

[0210] In addition, the above-mentioned electronic device also includes: a display 1108 for displaying the first indication information, the second indication information, and abnormal response instructions, etc.; and a connection bus 1111 for connecting the various module components in the above-mentioned electronic device.

[0211] In other embodiments, the aforementioned user equipment or server can be a node in a distributed system, wherein the distributed system can be a blockchain system, which is a distributed system formed by connecting multiple nodes through network communication. The nodes can form a peer-to-peer network, and any form of computing device, such as a server, user equipment, or other electronic device, can become a node in the blockchain system by joining this peer-to-peer network.

[0212] According to one aspect of this application, a computer program product is provided, comprising a computer program / instructions containing program code for performing the methods shown in the flowchart. In such embodiments, the computer program can be downloaded and installed from a network via a communication component, and / or installed from a removable medium. When the computer program is executed by a central processing unit, it performs various functions provided in embodiments of this application.

[0213] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0214] It should be noted that the computer system of the electronic device is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0215] A computer system includes a Central Processing Unit (CPU), which performs various appropriate actions and processes based on programs stored in Read-Only Memory (ROM) or loaded from RAM. ROM also stores various programs and data required for system operation. The CPU, ROM, and RAM are interconnected via a bus. Input / output interfaces (I / O interfaces) are also connected to the bus.

[0216] The following components are connected to the input / output interface: input sections including keyboards, mice, etc.; output sections including cathode ray tubes (CRTs), liquid crystal displays (LCDs), and speakers; storage sections including hard drives; and communication sections including network interface cards such as LAN cards and modems. The communication section performs communication processing via a network such as the Internet. Drives are also connected to the input / output interface as needed. Removable media, such as disks, optical discs, magneto-optical discs, semiconductor memories, etc., are installed on the drive as needed so that computer programs read from them can be installed into the storage section as required.

[0217] Specifically, according to embodiments of this application, the processes described in the various method flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication component, and / or installed from a removable medium. When the computer program is executed by a central processing unit, it performs various functions defined in the system of this application.

[0218] According to one aspect of this application, a computer-readable storage medium is provided, wherein a processor of a computer device reads computer instructions from the computer-readable storage medium, and executes the computer instructions, causing the computer device to perform the methods provided in the various alternative implementations described above.

[0219] Optionally, in this embodiment, the computer-readable storage medium described above may be configured to store a computer program for performing the following steps:

[0220] S2-1, upon obtaining the routing address corresponding to the first user edge device, first indication information carrying the routing address and the routing label assigned to the routing address by the first service edge device is sent to the second service edge device. Here, the first user edge device is a device located at the edge of the first customer network, the first service edge device is an edge router in the service provider network that has a first connection relationship with the first user edge device, the second service edge device is an edge router in the service provider network that has a second connection relationship with the second user edge device, and the second user edge device is a device located at the edge of the second customer network. The first user edge device and the second user edge device are configured to communicate through the service provider network. The first indication information is responded to by the second service edge device. It is set that the data packet sent to the routing address needs to be encapsulated using a routing label.

[0221] S2-2, the second indication information carrying the routing label and the tunnel interface address corresponding to the first service edge device is sent to the second service edge device. The tunnel interface address is used to indicate the logical interface of the tunnel path. The logical interface is used to encapsulate and decapsulate data packets between the two ends of the tunnel path. The two ends of the tunnel path include the first service edge device and the second service edge device. The tunnel path is used to transmit encapsulated data packets. The second indication information is responded to by the second service edge device, which sets that data packets encapsulated using the routing label need to be sent to the tunnel interface address.

[0222] S2-3, if the first connection is in an abnormal state, an abnormal response command is sent to the second serving edge device. This abnormal response command instructs the second serving edge device to mark the indication information carrying the routing label as abnormal information, and sets the indication information marked as abnormal to a no-response mode. Alternatively,

[0223] S3-1, when the first serving edge device obtains the routing address corresponding to the first user edge device, it sends a first indication message and responds to the first indication message. It sets that the data packets sent to the routing address need to be encapsulated with routing labels. The first indication message carries the routing address and the routing label assigned by the first serving edge device to the routing address. The first user edge device is a device located at the edge of the first customer network. The first serving edge device is an edge router in the service provider network that has a first connection relationship with the first user edge device. The second serving edge device is an edge router in the service provider network that has a second connection relationship with the second user edge device. The second user edge device is a device located at the edge of the second customer network. The first user edge device and the second user edge device are configured to communicate through the service provider network.

[0224] S3-2, Obtain the second indication information sent by the first service edge device, and respond to the second indication information. Set the data packet encapsulated with the routing label to be sent to the tunnel interface address corresponding to the first service edge device. The second indication information carries the routing label and the second indication information of the tunnel interface address. The tunnel interface address is used to indicate the logical interface of the tunnel path. The logical interface is used to encapsulate and decapsulate the data packet between the two ends of the tunnel path. The two ends of the tunnel path include the first service edge device and the second service edge device. The tunnel path is used to transmit the encapsulated data packet.

[0225] S3-3, obtain the abnormal response instruction sent by the first service edge device when the first connection relationship is in an abnormal state, and mark the indication information carrying the routing label as abnormal information, wherein the indication information marked as abnormal information is set to prohibit response.

[0226] Optionally, in embodiments of this application, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0227] Optionally, in this embodiment, those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing related hardware of an electronic device. The program can be stored in a computer-readable storage medium, which may include: flash drive, read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0228] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0229] If the integrated units in the above embodiments are implemented as software functional units and sold or used as independent products, they can be stored in the aforementioned computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause one or more computer devices (which may be personal computers, servers, or network devices, etc.) to execute all or part of the steps of the methods of the various embodiments of this application.

[0230] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0231] In the several embodiments provided in this application, it should be understood that the disclosed user equipment can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection of units or modules may be electrical or other forms.

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

[0233] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0234] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. An anomaly handling method based on a service provider network, characterized in that, include: Upon obtaining the routing address corresponding to the first user edge device, first indication information carrying the routing address and the routing label allocated by the first service edge device for the routing address is sent to the second service edge device. Here, the first user edge device is a device located at the edge of the first customer network, the first service edge device is an edge router in the service provider network with a first connection to the first user edge device, the second service edge device is an edge router in the service provider network with a second connection to the second user edge device, and the second user edge device is located at the edge of the second customer network. The first user edge device and the second user edge device are configured to communicate through the service provider network. The first indication information is responded to by the second service edge device, and the data packet sent to the routing address is encapsulated using the routing label. The second indication information, carrying the routing label and the tunnel interface address corresponding to the first service edge device, is sent to the second service edge device. The tunnel interface address is used to indicate the logical interface of the tunnel path. The logical interface is used to encapsulate and decapsulate the data packet between the two ends of the tunnel path. The two ends of the tunnel path include the first service edge device and the second service edge device. The tunnel path is used to transmit the encapsulated data packet. The second indication information is responded to by the second service edge device, which sets that the data packet encapsulated using the routing label needs to be sent to the tunnel interface address. If the first connection is in an abnormal state, an abnormal response instruction is sent to the second service edge device. The abnormal response instruction is used to instruct the second service edge device to mark the indication information carrying the routing label as abnormal information, and the indication information marked as abnormal information is set to prohibit response.

2. The method according to claim 1, characterized in that, Sending first indication information carrying the routing address and the routing label assigned to the routing address by the first service edge device to the second service edge device includes: sending the first indication information to the second service edge device via a multi-protocol border gateway protocol, wherein the multi-protocol border gateway protocol is used to transmit routing information between edge devices of the service provider network, and the routing information includes the routing address and the routing label; The step of sending the second indication information, carrying the routing label and the tunnel interface address corresponding to the first service edge device, to the second service edge device includes: In the multi-protocol border gateway protocol, a specific virtual private network address family is enabled, and the second indication information is sent to the second service edge device, wherein the specific virtual private network address family is an address space or routing information set defined to support the tunnel interface address.

3. The method according to claim 2, characterized in that, Before enabling a specific Virtual Private Network address family in the Multiprotocol Border Gateway Protocol and sending the second indication information to the second serving edge device, the method further includes: The multi-protocol border gateway protocol is extended to define a specific virtual private network address family and obtain a specific information structure that matches the specific virtual private network address family. The specific information structure is used to define the standard format for transmitting information in the multi-protocol border gateway protocol after the specific virtual private network address family is enabled.

4. The method according to any one of claims 1 to 3, characterized in that, After sending the exception response command to the second service edge device, the method further includes: When the first connection is restored from the abnormal state to the normal state, a normal response instruction is sent to the second service edge device, wherein the normal response instruction is used to instruct the second service edge device to remove the marking of the abnormal information by carrying the indication information of the routing label.

5. The method according to any one of claims 1 to 3, characterized in that, In the process of sending the exception response command to the second service edge device, the method further includes: A backup activation instruction is sent to the second service edge device, wherein the backup activation instruction is used to instruct the second service edge device to activate a backup tunnel path, which is the transmission path that takes over the data packet when the instruction tunnel path fails.

6. An anomaly handling method based on a service provider network, characterized in that, include: When the first service edge device obtains the routing address corresponding to the first user edge device, it sends a first indication message and responds to the first indication message. It sets that the data packets sent to the routing address need to be encapsulated using the routing label. The first indication message carries the routing address and the routing label assigned to the routing address by the first service edge device. The first user edge device is a device located at the edge of the first customer network. The first service edge device is an edge router in the service provider network that has a first connection relationship with the first user edge device. The second service edge device is an edge router in the service provider network that has a second connection relationship with the second user edge device. The second user edge device is a device located at the edge of the second customer network. The first user edge device and the second user edge device are configured to communicate through the service provider network. Obtain the second indication information sent by the first service edge device, and respond to the second indication information. Set the data packet encapsulated using the routing label to be sent to the tunnel interface address corresponding to the first service edge device. The second indication information carries the routing label and the second indication information of the tunnel interface address. The tunnel interface address is used to indicate the logical interface of the tunnel path. The logical interface is used to encapsulate and decapsulate the data packet between the two ends of the tunnel path. The two ends of the tunnel path include the first service edge device and the second service edge device. The tunnel path is used to transmit the encapsulated data packet. The system obtains the abnormal response instruction sent by the first service edge device when the first connection relationship is in an abnormal state, and marks the indication information carrying the routing label as abnormal information, wherein the indication information marked as abnormal information is set to prohibit response.

7. The method according to claim 6, characterized in that, The data packets sent to the routing address are to be encapsulated using the routing label, including: creating a first entry in the routing table created by the second service edge device, wherein the first entry is used to associate the routing address with the routing label; The setting requires that the data packet encapsulated by the routing label be sent to the tunnel interface address, including: creating a second entry in the created routing table, wherein the second entry is used to associate the tunnel interface address with the routing label.

8. The method according to claim 7, characterized in that, The step of marking the indication information carrying the routing label as abnormal information includes: Determine at least one specific entry carrying the route label from the created routing table, and mark the indication information in the at least one specific entry as the abnormal information, wherein the at least one specific entry includes the first entry and the second entry.

9. The method according to any one of claims 6 to 8, characterized in that, The step of obtaining the abnormal response command sent by the first service edge device when the first connection relationship is in an abnormal state, and marking the indication information carrying the routing label as abnormal information, includes: The system obtains the abnormal response command sent by the first service edge device when the first connection is in an abnormal state, and sets a suppression time, wherein the suppression time is used to wait for the state of the first connection to change; If the suppression time ends and no normal response instruction is received from the first service edge device when the first connection relationship is in a normal state, the indication information carrying the routing label is marked as abnormal information. The normal response instruction is used to instruct the second service edge device to remove the marking of the abnormal information from the indication information carrying the routing label.

10. An anomaly handling device based on a service provider network, characterized in that, include: The first sending unit is configured to, upon obtaining the routing address corresponding to the first user edge device, send first indication information carrying the routing address and a routing label allocated by the first service edge device for the routing address to the second service edge device. The first user edge device is a device located at the edge of a first customer network, the first service edge device is an edge router in the service provider network with a first connection to the first user edge device, the second service edge device is an edge router in the service provider network with a second connection to the second user edge device, the second user edge device is located at the edge of a second customer network, the first user edge device and the second user edge device are configured to communicate through the service provider network, the first indication information is responded to by the second service edge device, and the data packet sent to the routing address is configured to be encapsulated using the routing label. The second sending unit is configured to send second indication information carrying the routing label and the tunnel interface address corresponding to the first service edge device to the second service edge device. The tunnel interface address is used to indicate the logical interface of the tunnel path. The logical interface is used to encapsulate and decapsulate the data packet between the two ends of the tunnel path. The two ends of the tunnel path include the first service edge device and the second service edge device. The tunnel path is used to transmit the encapsulated data packet. The second indication information is responded to by the second service edge device, which sets that the data packet encapsulated using the routing label needs to be sent to the tunnel interface address. The third sending unit is configured to send an abnormal response instruction to the second service edge device when the first connection relationship is in an abnormal state. The abnormal response instruction is configured to instruct the second service edge device to mark the indication information carrying the routing label as abnormal information, and set the indication information marked as abnormal information to prohibit response.

11. An anomaly handling device based on a service provider network, characterized in that, include: The first acquisition unit is configured to acquire first indication information sent by the first service edge device when it obtains the routing address corresponding to the first user edge device, and respond to the first indication information to set that the data packet sent to the routing address needs to be encapsulated using the routing label. The first indication information carries the routing address and the routing label assigned to the routing address by the first service edge device. The first user edge device is a device located at the edge of a first customer network. The first service edge device is an edge router in the service provider network that has a first connection relationship with the first user edge device. The second service edge device is an edge router in the service provider network that has a second connection relationship with the second user edge device. The second user edge device is a device located at the edge of a second customer network. The first user edge device and the second user edge device are configured to communicate through the service provider network. The second acquisition unit is configured to acquire the second indication information sent by the first service edge device, and respond to the second indication information by setting that the data packet encapsulated using the routing label needs to be sent to the tunnel interface address corresponding to the first service edge device. The second indication information carries the routing label and the second indication information of the tunnel interface address. The tunnel interface address is used to indicate the logical interface of the tunnel path. The logical interface is used to encapsulate and decapsulate the data packet between the two ends of the tunnel path. The two ends of the tunnel path include the first service edge device and the second service edge device. The tunnel path is used to transmit the encapsulated data packet. The third acquisition unit is used to acquire the abnormal response instruction sent by the first service edge device when the first connection relationship is in an abnormal state, and to mark the indication information carrying the routing label as abnormal information, wherein the indication information marked as abnormal information is set to prohibit response.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein the program is executed by an electronic device to perform the method described in any one of claims 1 to 11.

13. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the steps of the method described in any one of claims 1 to 11.

14. An electronic device comprising a memory and a processor, characterized in that, The memory stores a computer program, and the processor is configured to execute the method described in any one of claims 1 to 11 through the computer program.

Images