A routing publication method and apparatus

Abstract

The application discloses a routing publishing method and device, and relates to the technical field of communication. The method can avoid traffic bypassing when a user terminal device accesses a network through a backup network device, and further avoid resource waste. The method is executed by a first device. The method comprises the following steps: determining that any communication link between a second device and a plurality of user terminal devices is faulty; and publishing a host route of a user terminal device connected with the any communication link to a network terminal device. The host route is used to instruct the network terminal device to send a response message of a service message to the user terminal device connected with the any communication link via the first device after receiving the service message from the user terminal device. A master-backup protocol is run between the first device and the second device. The first device is a backup device, and the second device is a master device. The second device is used to forward messages between the plurality of user terminal devices and the network terminal device when the link is normal.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a route publishing method and apparatus. Background Technology

[0002] When connecting user devices to the network via network access devices, to ensure the stability of user device network access, the network access devices typically include a primary network access device and a backup network access device running a primary / backup protocol. The primary and backup network access devices are configured with a shared address pool. Addresses in this pool are used to allocate to user devices that request network access through the primary or backup network access device and have passed authentication. This allows the user device to advertise host routes based on the allocated addresses to access the network.

[0003] Typically, after configuring a shared address pool, the primary and backup network access devices publish user network routes (UNRs) for that address pool to the network end devices. Thus, when a user device communicates with the network end devices through the primary network, if any communication link between the primary network access device and the user device fails, according to the primary / backup protocol running between the primary and backup network access devices, the user device connected to the failed communication link can access the network through the backup network access device. In this case, the response message from the network end device to the user device's service message first reaches the primary network access device, which publishes the UNR including the lower cost value. Then, the response message is routed from the primary network access device to the backup network access device via the network end devices before being sent from the backup network access device to the user device.

[0004] In other words, when user-end devices and network devices are exchanging messages, after the network access device used to connect the user-end device connected to the network via the faulty communication link performs a primary / backup switch, the response messages sent by the network device to the user-end device are detoured, i.e., traffic is detoured, thus causing a waste of resources. Summary of the Invention

[0005] This application provides a route publishing method and apparatus that can avoid traffic detours when user devices access the network through backup network devices, thereby avoiding resource waste.

[0006] To achieve the above objectives, this application provides the following technical solution:

[0007] Firstly, this application provides a route advertising method, which is executed by a first device running a master-slave protocol with a second device, wherein the first device is a backup device and the second device is a master device, and the second device is used to forward packets between multiple user terminal devices and network terminal devices when the link is normal. The method includes: determining an arbitrary communication link failure between the second device and the multiple user terminal devices; and advertising a host route for the user terminal devices connected to the arbitrary communication link to the network terminal devices. The host route instructs the network terminal devices, upon receiving a service packet from the user terminal devices connected to the arbitrary communication link, to send a response packet of the service packet via the first device to the user terminal devices connected to the arbitrary communication link.

[0008] The routing publication method provided in this application addresses a scenario where, after a failure of the user-side communication link of the second device (the primary access device) fails, the first device (the backup access device) forwards service packets from the user-end device connected to the failed communication link to the network device. In this scenario, the first device publishes a host route for the user-end device connected to the failed communication link to the network device. This enables the network device to generate a forwarding table entry with this host route as the destination address and the backup access device as the next-hop device. After the first device forwards the service packets from the user-end device connected to the failed communication link to the network device, the network device can use this forwarding table entry to forward response packets from the first device to the user-end device. This ensures consistent uplink and downlink paths when the user-end device communicates through the first device and the network device, thus avoiding... Figure 1 The traffic detour issue shown is addressed, thereby avoiding resource waste.

[0009] In one possible design approach, the above-mentioned method of publishing the host route of the user terminal device connected to the arbitrary communication link to the network end device includes: modifying the attribute of the host route to publishable; and then sending the host route to the network end device.

[0010] In another possible design, determining any communication link failure between the second device and the multiple user terminal devices includes: receiving a status message sent by the second device indicating the status of the communication link between the second device and the multiple user terminal devices; and determining any communication link failure between the second device and the multiple user terminal devices based on the status message.

[0011] Through this possible implementation, the first device can determine the user-side link failure of the second device by communicating with the status message between the second device and the second device. This can trigger the first device to send the host route of the user-side device corresponding to the faulty link to the network end device, thereby ensuring that the return traffic of the user end does not detour and thus avoiding resource waste.

[0012] In another possible design, after determining that any communication link between the second device and multiple user terminal devices has failed, the method further includes forwarding messages between the user terminal devices and network terminal devices connected by the arbitrary communication link.

[0013] In another possible design, the host route mentioned above is generated based on the address pool shared by the first and second devices when the user device connected by any of the above communication links requests to establish a connection with the network device.

[0014] In another possible design, the UNRs of the aforementioned address pool are pre-published to the network end devices by the first and second devices, respectively.

[0015] In another possible design approach, the method further includes: determining fault recovery for any of the aforementioned communication links; revoking the host route published to the network device; and modifying the attribute of that host route to be unpublishable.

[0016] In this possible implementation, after the faulty link of the second device is restored to normal operation, the first device cancels the previously published host route for the user device connected to the faulty link. This allows the network device to delete or invalidate the forwarding table entry corresponding to that host route. Consequently, after the user device accesses the network via the second device, its return traffic can be forwarded according to the forwarding table entry generated by the UNR pre-published by the second device. That is, the return traffic is forwarded to the user device via the second device, ensuring consistency between the uplink and downlink traffic paths for the user device.

[0017] Secondly, this application provides a route publishing device.

[0018] In one possible design, the route publishing device is used to execute any of the methods provided in the first aspect. This application can divide the route publishing device into functional modules according to any of the methods provided in the first aspect. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. For instance, this application can divide the route publishing device into a determining unit and a sending unit, etc., according to function. The descriptions of possible technical solutions and beneficial effects of the various functional modules described above can be found in the technical solutions provided in the first aspect or its corresponding possible designs, and will not be repeated here.

[0019] In another possible design, the routing publishing device includes one or more processors and a transmission interface through which the one or more processors receive or send data, and the one or more processors are configured to invoke program instructions stored in memory to cause the routing publishing device to perform any of the methods provided by the first aspect and any of its possible design embodiments.

[0020] Thirdly, this application provides a computer-readable storage medium including program instructions that, when executed on a computer or processor, cause the computer or processor to perform any method provided by any possible implementation of the first aspect described above.

[0021] Fourthly, this application provides a computer program product that, when run on a routing publishing device, causes any method provided by any possible implementation of the first aspect to be executed.

[0022] Fifthly, this application provides a chip system comprising: a processor, the processor being configured to retrieve and execute a computer program stored in a memory, performing any method provided by any possible implementation of the first aspect.

[0023] It is understood that any of the devices, computer storage media, computer program products or chip systems provided above can be applied to the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0024] In this application, the name of the aforementioned route publishing device does not limit the device or functional module itself. In actual implementation, these devices or functional modules may appear under other names. As long as the functions of each device or functional module are similar to those in this application, they fall within the scope of the claims of this application and their equivalents.

[0025] These or other aspects of this application will become more readily apparent in the following description. Attached Figure Description

[0026] Figure 1 This is a schematic diagram of a traffic flow detour.

[0027] Figure 2 A schematic diagram of the hardware structure of a routing publishing device provided in an embodiment of this application;

[0028] Figure 3 A schematic diagram of a network architecture provided in an embodiment of this application;

[0029] Figure 4A flowchart illustrating a route publishing method provided in an embodiment of this application;

[0030] Figure 5 A schematic diagram illustrating the beneficial effects of the route publishing method provided in the embodiments of this application;

[0031] Figure 6 This is a schematic diagram of the structure of a route publishing device provided in an embodiment of this application;

[0032] Figure 7 This is a schematic diagram of the structure of a chip system provided in an embodiment of this application;

[0033] Figure 8 A hardware architecture diagram of a processor provided in an embodiment of this application;

[0034] Figure 9 This is a schematic diagram of the structure of a signal carrying medium for carrying a computer program product, provided in an embodiment of this application. Detailed Implementation

[0035] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0036] In the embodiments of this application, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0037] In this application, the term "at least one" means one or more, and the term "multiple" means two or more. For example, multiple second messages refer to two or more second messages. The terms "system" and "network" are often used interchangeably in this document.

[0038] It should be understood that the terminology used in the description of the various examples herein is for the purpose of describing particular examples only and is not intended to be limiting. As used in the description of the various examples and the appended claims, the singular forms “a” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise.

[0039] It should also be understood that the term "and / or" as used herein refers to and covers any and all possible combinations of one or more of the associated listed items. The term "and / or" describes an association between related objects, indicating that three relationships can exist; for example, A and / or B can represent: A alone, A and B simultaneously, or B alone. Additionally, the character " / " in this application generally indicates that the preceding and following related objects are in an "or" relationship.

[0040] It should also be understood that, in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0041] It should be understood that determining B based on A does not mean determining B solely based on A; B can also be determined based on A and / or other information.

[0042] It should also be understood that the term “comprising” (also referred to as “includes”, “including”, “comprises” and / or “comprising”) as used in this specification specifies the presence of the stated features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0043] It should also be understood that the term "if" can be interpreted as meaning "when" or "upon" or "in response to determination" or "in response to detection." Similarly, depending on the context, the phrases "if determination..." or "if detection [the stated condition or event]" can be interpreted as meaning "when determination..." or "in response to determination..." or "when detection [the stated condition or event]" or "in response to detection [the stated condition or event]."

[0044] It should be understood that the phrases "an embodiment," "an embodiment," and "a possible implementation" used throughout the specification mean that a specific feature, structure, or characteristic related to an embodiment or implementation is included in at least one embodiment of this application. Therefore, the phrases "in an embodiment," "an embodiment," or "a possible implementation" appearing throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments.

[0045] refer to Figure 1 , Figure 1 A schematic diagram of a flow detour is shown.

[0046] like Figure 1 As shown, a master-slave protocol operates between network access device 12 and network access device 13. For simplicity, "network access device" will be referred to as "access device" in the following text. Access device 12 is the master device, and access device 13 is the backup device. Access device 12 and access device 13 are configured with a shared address pool.

[0047] It should be understood that the address pool can be an address pool configured by an Internet service provider (ISP) or network operator for access devices 12 and 13. After access devices 12 and 13 are configured with this address pool, they can publish the UNR of this address pool to network-side devices, such as... Figure 1 The network-side devices, such as service servers, in the ISP 14 network shown are illustrated. In this way, the network-side devices can generate forwarding table entries based on the received UNR. Specifically, when access devices 12 and 13 publish UNRs to the network-side devices, the cost value of the UNR published by access device 12 is lower than the cost value of the UNR published by access device 13.

[0048] It should be understood here that in forwarding table entry 1 generated by the network device based on the UNR published by access device 12, the destination address is the UNR of the aforementioned address pool, and the next-hop device is access device 12. Similarly, in forwarding table entry 2 generated by the network device based on the UNR published by access device 13, the destination address is the UNR of the aforementioned address pool, and the next-hop device is access device 13. Furthermore, the cost value in forwarding table entry 1 is less than the cost value in forwarding table entry 2.

[0049] When a user device (e.g., user device 11) requests access to the ISP's network (e.g., the network of ISP 14) from access device 12 (or access device 13), after successful authentication of user device 11, access device 12 (or access device 13) can allocate an address from the address pool to user device 11, so that user device 11 can publish host routes based on the allocated address, thereby accessing the network of ISP 14.

[0050] Specifically, when the communication links between access device 12 and user terminal device 11 are normal, user terminal device 11 can communicate with network terminal devices (such as a service server in the 1SP 14 network) through access device 12. Figure 1 As shown, user terminal device 11 can communicate with network terminal devices in the 1SP 14 network via communication links L1-1 and L1-2, and access device 12.

[0051] It should be understood that communication link L1-1 is any one of the multiple communication links between user terminal device 11 and access device 12.

[0052] When the communication link L1-1 between user terminal device 11 and access device 12 fails, according to the primary and backup protocol running between access device 12 and access device 13, user terminal device 11 can send service messages to network terminal devices in the 1SP 14 network through communication links L2-1 and L2-2 and access device 13.

[0053] Then, after the network device processes the service message and obtains the response message, it queries the forwarding table entry in the routing table based on the destination address in the response message (i.e., the source address in the service message, which is also the address assigned to user device 11 by the access device when it accesses the network). Since the destination address belongs to the UNR in the address pool shared by access devices 12 and 13, the network device can determine to forward the response message based on the forwarding table entry that includes the UNR and has the lowest cost value. Because the cost value of the UNR published by access device 12 is lower than that of the UNR published by access device 13, the network device forwards the response message based on the forwarding table entry generated according to the UNR published by access device 12, that is, sends the response message to access device 12 through communication link L3-1.

[0054] Then, due to a failure in communication link L1-1 between access device 12 and user terminal device 11, access device 12 needs to send the response message to access device 13 through the protection tunnel L3-2 of the ISP 14 network. Then, access device 13 sends the response message to user terminal device 11 through communication link L3-3, thus completing one message exchange between user terminal device 11 and the network terminal device of ISP 14 network.

[0055] It can be seen that after the communication link L1-1 between user terminal device 11 and access device 12 fails, when user terminal device 11 communicates with network terminal device, the return traffic (i.e. the response message sent by the network terminal) is detoured, which leads to the waste of resources of access device and ISP 14 network.

[0056] To address the aforementioned traffic routing issue, one possible implementation involves configuring a separate address pool for each communication link on the user side of the access device. Here, the user side of the access device refers to the side where the access device connects to the user terminal device. In this way, the primary access device can publish the UNR (Unified Address Reference) for each address pool to the network. When any communication link on the user side of the primary access device fails, the primary access device withdraws the UNR for the address pool corresponding to that communication link from the network. Simultaneously, according to the primary / backup protocol running between the primary and backup access devices, the user terminal device communicates with the network through the backup access device. In this case, the backup access device publishes the UNR for the address pool corresponding to that communication link to the network. Thus, when the user terminal device connected to that communication link communicates with the network through the backup access device, its uplink and downlink paths are consistent.

[0057] However, network operators or ISPs typically do not configure address pools for access devices based on users, but rather on service types. In this case, this route advertising method cannot be applied to actual network communication.

[0058] In another possible implementation, when the user terminal device communicates with the network terminal device through the primary access device, the primary access device pre-publishes the host route of the user terminal device to the network terminal. When any communication link on the user side of the primary access device fails, according to the primary / backup protocol running between the primary and backup access devices, the user terminal device communicates with the network terminal through the backup access device. In this case, the primary access device withdraws the host route of the user terminal device connected to the arbitrary communication link, and the backup access device publishes the host route of the user terminal device connected to the arbitrary communication link to the network terminal device. In this way, when the user terminal device connected to the arbitrary communication link communicates with the network terminal device through the backup access device, its uplink and downlink paths are consistent.

[0059] However, in practical applications, if the number of user devices connected to the network by the access device is large, then publishing the host routes of the user devices to the network requires high routing switching capabilities from the access device and high routing processing performance from the network. Therefore, this method is not universally applicable.

[0060] Based on this, this application provides a route publishing method, which can ensure that the uplink and downlink paths of user devices are consistent when communicating through access devices and network devices without affecting the performance of access devices and network devices.

[0061] This application also provides a route publishing device, which can be deployed in a backup access device running a primary / backup protocol. The access device can be a network access device used to connect user devices to the network, such as a Broadband Remote Access Server (BRAS) device, a Broadband Network Gateway (BNG), etc., and this application does not specifically limit this.

[0062] refer to Figure 2 , Figure 2 A schematic diagram of the hardware structure of a route publishing device provided in an embodiment of this application is shown. Figure 2 As shown, the routing publishing device 20 includes a processor 21, a memory 22, a communication interface 23, and a bus 24. The processor 21, the memory 22, and the communication interface 23 can be connected via the bus 24.

[0063] The processor 21 is the control center of the routing publishing device 20. It can be a general-purpose central processing unit (CPU) or other general-purpose processors. The general-purpose processor can be a microprocessor or any conventional processor.

[0064] As an example, processor 21 may include one or more CPUs, for example Figure 2 CPU 0 and CPU 1 are shown in the diagram.

[0065] The memory 22 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto.

[0066] In one possible implementation, the memory 22 can exist independently of the processor 21. The memory 22 can be connected to the processor 21 via a bus 24 and is used to store data, instructions, or program code. When the processor 21 calls and executes the instructions or program code stored in the memory 22, it can implement the routing and publishing method provided in the embodiments of this application.

[0067] In another possible implementation, the memory 22 can also be integrated with the processor 21.

[0068] Communication interface 23 is used for the routing publishing device 20 to connect with other devices (such as user terminal devices or main access devices) via a communication network, which may be Ethernet, radio access network (RAN), wireless local area network (WLAN), etc. Communication interface 23 may include a receiving unit for receiving data and a sending unit for sending data.

[0069] Bus 24 can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 2 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0070] It should be pointed out that, Figure 2 The structure shown does not constitute a limitation on the routing publishing device, except Figure 2 In addition to the components shown, the routing publishing device 20 may include more or fewer components than illustrated, or combine certain components, or have different component arrangements.

[0071] In addition, this application embodiment also provides a network architecture. This network architecture includes at least two access devices running a primary / backup protocol, and a network end device connected to the at least two access devices. The at least two access devices are configured with a shared address pool. The at least two access devices are used to connect user devices to the network end device, thereby enabling user devices to access the network.

[0072] The description of the address pool shared by the at least two access devices can be found in the description of the shared address pool of access device 12 and access device 13 above, and will not be repeated here.

[0073] The network device can be a network device in the core network or a network device in an ISP, etc., and is not limited thereto. The network device can be a server, or a relay device connected to a server, etc., and is not limited thereto in this embodiment.

[0074] Taking a scenario where the number of at least two access devices running a primary / backup protocol is 2 as an example, refer to... Figure 3 , Figure 3 A schematic diagram of a network architecture 30 provided in an embodiment of this application is shown.

[0075] like Figure 3 As shown, a primary / backup protocol operates between access device 31 and access device 32. Access device 31 is the primary access device, and access device 32 is the backup access device. Furthermore, access device 31 and access device 32 are configured with a shared address pool.

[0076] Access devices 31 and 32 are respectively connected to network-side devices in the ISP 33 network. Access devices 31 and 32 are also respectively connected to switch 30. Switch 30 can connect multiple user-end devices, such as... Figure 3 The user terminal device shown is 1, 2, ..., and m, where m is a positive integer.

[0077] Of course, access devices 31 and 32 can also be directly connected to multiple user terminal devices without relaying through a switch. This application embodiment does not specifically limit this.

[0078] The routing publication method provided in the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0079] refer to Figure 4 , Figure 4 A flowchart illustrating a route advertising method provided in an embodiment of this application is shown. This method can be applied to... Figure 3 The network architecture shown in 30.

[0080] For simplicity, in this embodiment, access device 32, i.e., the backup access device, will be referred to as the first device, and access device 31, i.e., the primary access device, will be referred to as the second device. In this way, the first device and the second device share the address pool. The route advertising method provided in this embodiment can be executed by the first device, that is, the route advertising method provided in this embodiment can be executed by the backup access device running the primary / backup protocol. This method may include the following steps:

[0081] S101. Determine any communication link failure between the second device and multiple user terminal devices.

[0082] Specifically, the first device can determine any communication link failure between the second device and multiple user terminal devices based on the status message received from the second device.

[0083] Among them, the status message is used to indicate the status of the user-side communication link of the second device, that is, to indicate the status of the communication link between the second device and multiple user terminal devices.

[0084] Optionally, the second device can monitor the user-side communication link status by detecting whether there is a fault in the interface of the user-side communication link, or by monitoring the user-side communication link status through link probe messages between the second device and the user terminal device. In this way, the second device can report the monitored user-side communication link status to the first device through status messages.

[0085] Optionally, the second device may periodically send status messages to the first device. If the second device detects that all communication links on the current user side are normal, i.e., no faulty communication links are detected, the status message indicates that the communication links between the second device and multiple user terminal devices are in a normal state. If the second device detects a fault in any communication link on the current user side, the status message includes the host routes of all user terminal devices connected to that faulty communication link; that is, the status message includes the host routes of all user terminal devices connected to the faulty communication link.

[0086] In response, the first device receives the status message, and when the status message includes the host routes of all user devices connected to the arbitrary communication link, the first device determines that the arbitrary communication link between the second device and the multiple user devices is faulty.

[0087] S102. Publish the host route of the user terminal device connected to any of the above communication links to the network terminal device.

[0088] As described above, if the second device detects a failure in any communication link on the current user side, the status message received by the first device will include the host routes of all user-end devices connected to that arbitrary communication link. Therefore, the first device can determine the host routes of all user-end devices connected to that arbitrary communication link based on the received status message.

[0089] In this first possible implementation, the first device can modify the attribute of the host routes of all user devices connected to the determined arbitrary communication link to be publishable. In this way, the first device can send the host routes of all user devices to the network device, thus achieving the purpose of publishing the host routes of the user devices connected to the aforementioned arbitrary communication link to the network device.

[0090] The host route published by the first device to the network terminal device can be used to instruct the network terminal device to send the response message of the service message to the user terminal device connected to the arbitrary communication link after receiving the service message from the user terminal device connected to any of the above communication links.

[0091] Specifically, the network device can generate a first forwarding table entry based on the host route received from the user device connected by the arbitrary communication link. The destination address in this first forwarding table entry is the host route received from the first device, and the next-hop device of this first forwarding table entry is the first device that published the host route.

[0092] It should be understood that, according to the primary / backup agreement between the first and second devices, when the user-side communication link of the second device fails, the user-end device corresponding to the failed communication link can send service messages to the network device through the first device. The specific process can be found in S103, and will not be elaborated here. In this way, any user-end device connected by the aforementioned communication link can send service messages to the network device through the first device.

[0093] When a network device receives a service packet sent by a user terminal device via a first device, it can determine the target forwarding entry from multiple forwarding entries in the routing table based on the destination address and longest mask matching method in the response packet of the service packet. Here, the number of high-order matching bits between the destination address in the target forwarding entry and the destination address in the response packet is greater than the number of high-order matching bits between the destination address in any of the other forwarding entries (excluding the target forwarding entry) and the destination address in the response packet. The source address of the service packet is the same as the destination address in the response packet, which is also the host route of the user terminal device connected by any of the aforementioned communication links.

[0094] It should be understood that, for network devices, in addition to the first forwarding table entry, the network device also includes a second forwarding table entry and a third forwarding table entry generated based on the UNRs pre-published by the first and second devices. The destination address in the second and third forwarding table entries is the UNR, and the description of the second and third forwarding table entries can be found in the description above of the forwarding table entries generated by the network device based on the UNRs published by access devices 12 and 13; it will not be repeated here.

[0095] In this way, the network device can determine that the third forwarding table entry is the target forwarding table entry based on the destination address and longest mask matching method in the response message of the service message. Therefore, the first device can forward the response message through the third forwarding table entry. That is, the response message is sent to the first device, and then the first device can send the response message to the user terminal device connected to the arbitrary communication link.

[0096] In this way, the network device can match the forwarding table entry of the host route of the user device connected by any of the aforementioned communication links in its own routing table according to the longest mask matching method, and send the response message according to the route indicated in the forwarding table entry. That is, the network device sends the response message to the next-hop device indicated by the route in the forwarding table entry, i.e., the first device. Then, the first device can send the response message to the user device, thereby ensuring that the uplink and downlink paths are consistent when the user device connected by any of the aforementioned communication links communicates with the network device through the first device.

[0097] In the second possible implementation, the first device can modify the attributes of the host routes of a subset of the user terminal devices connected to the aforementioned arbitrary communication link to publishable, based on pre-negotiated and configured routing publication rules. For the host routes of the remaining subset of user terminal devices connected to the aforementioned arbitrary communication link, the first device maintains the default attributes of those host routes.

[0098] It should be noted that the default property of the host route on the user's terminal device is that it is not publishable.

[0099] In this way, the first device can modify the host routing attribute of all user-end devices connected by the aforementioned communication link to the host routing of publishable user-end devices and send it to the network device. This ensures that the uplink and downlink paths of these user-end devices are consistent when communicating with the network device through the first device. For a detailed description of the process of achieving consistent uplink and downlink paths when these user-end devices communicate with the network device through the first device, please refer to the description in the first possible implementation method; it will not be repeated here.

[0100] It is understandable that, for all user-end devices connected by any of the aforementioned communication links, those whose host routing attributes have not been modified to be publishable, when these user-end devices communicate with the network device through the first device, the response messages sent by the network device are routed to the second device, then through the protection tunnel of the network where the network device resides, and finally to the first device, before being sent by the first device to the user-end device. In other words, when these user-end devices communicate with the network device through the first device, traffic routing occurs when the network device sends response messages to these user-end devices; that is, the uplink and downlink paths are inconsistent when these user-end devices communicate with the network device through the first device. A detailed description of this traffic routing can be found above. Figure 1 The relevant descriptions of medium-volume detours will not be repeated here.

[0101] It should be understood that for communication links that connect a large number of user-end devices but occupy a small amount of bandwidth, it is permissible for the network device to bypass the protection tunnel when sending response messages to the user-end devices through the backup access device and the network device. This application embodiment does not limit this.

[0102] It is understandable that when the first device determines that all communication links on the user side of the second device are faulty based on the status message, the first device can publish routes according to the preset route publication rules.

[0103] It should be noted that the routing publication rule can be a routing publication rule for user-side communication links negotiated and determined by the first and second devices during configuration. Specifically, for any one or more communication links among multiple user-side communication links, the routing publication rule instructs the first or second device, which connects to the user-end device connected to that communication link, to publish the host route for that user-end device.

[0104] Additionally, it is understandable that it is used in Figure 3 The access device shown that forwards packets between the user terminal device and the network terminal device, if including multiple backup access devices, then the first device mentioned above is the access device with the highest priority among the multiple backup access devices. Specifically, when the user-side communication link of the primary access device fails, the higher-priority backup access device is preferentially used to replace the second device in forwarding packets between the user terminal and the network terminal device connected by the failed communication link, and is used to publish the host route of the user terminal connected by the failed communication link to the network terminal.

[0105] S103. Forward messages between the user terminal device and the network terminal device connected by the arbitrary communication link.

[0106] Specifically, after determining that any communication link between the second device and multiple user terminal devices has failed, the first device can send an Address Resolution Protocol (ARP) message to the user terminal device connected to that communication link. This ARP message includes the media access control address (MAC) of the first device.

[0107] When the user terminal device connected by the arbitrary communication link receives an ARP packet, it can modify the MAC address of the next-hop device in the forwarding table entry routed to the network terminal device to the MAC address of the first device.

[0108] In this way, when a user terminal device connected to any communication link sends a service message to a network terminal device, it first sends the service message to the first device, and then the first device forwards the service message to the network terminal device.

[0109] It can be seen that when the user terminal device connected by the arbitrary communication link forwards service packets to the network terminal device through the first device, the first device is upgraded from a backup access device to a primary access device for the arbitrary communication link.

[0110] It should be understood that the process of the first device sending an ARP message to the user terminal device connected to the arbitrary communication link can be executed simultaneously with step S102, or before step S102, or after step S102. This application embodiment does not limit this.

[0111] Thus, based on step S102, after the first device forwards the service message received from the user terminal device connected by the arbitrary communication link to the network terminal device, the network terminal device can then send the response message of the service message to the user terminal device connected by the arbitrary communication link via the first device, according to the host route of the user terminal device connected by the arbitrary communication link published by the first device in step S102. That is, the first device achieves consistent uplink and downlink path forwarding of messages between the user terminal device and the network terminal device connected by the arbitrary communication link.

[0112] S104. If the failure of any of the above communication links is confirmed to be resolved, then the host route published by the first device to the network device is revoked, and the host route attribute of the user device connected to the arbitrary communication link is modified to be unpublishable.

[0113] Specifically, the first device can determine the recovery of any of the aforementioned communication links based on the status messages received from the second device.

[0114] In one possible implementation, if the status message received by the first device does not include the host routes of all user terminal devices connected to any of the aforementioned communication links, then the first device determines that the fault of that arbitrary communication link has been recovered. Here, the description of the status message can be referred to in the description of the status message in S101 above, and will not be repeated here.

[0115] In another possible implementation, the status message received by the first device may include the host route of the user terminal device connected to the communication link that has recovered from the fault. In this way, the first device can compare the host route of the user terminal device connected to the communication link that has recovered from the fault in the status message with the host route of any of the aforementioned communication links. If they are the same, the first device determines that the fault of that arbitrary communication link has been recovered.

[0116] Then, the first device sends a route withdrawal message to the network device, instructing the network device to invalidate or delete the forwarding table entries generated by the host routes of the user devices connected by the aforementioned communication links, thereby realizing the withdrawal of the host routes published by the first device to the network device.

[0117] Furthermore, the first device will also change the host routing attribute of the user terminal device connected to the arbitrary communication link from publishable back to non-publishable.

[0118] Thus, when a network device receives a service packet from a user device connected via any communication link, it matches the destination address in the response packet in the routing table using the longest mask method. Since the destination address belongs to an UNR (Unified Address Reference) pre-published by the first and second devices, the network device can determine to forward the response packet based on the forwarding table entry with the lowest cost value that includes the UNR. Because the cost value of the UNR published by the second device is lower than that of the UNR published by the first device, the network device forwards the response packet based on the forwarding table entry generated according to the UNR published by the second device. That is, the network device sends the response packet to the second device, and then the second device forwards the response packet to the user device.

[0119] It is understandable that when the second device detects that any of the above communication links has returned to normal, in addition to sending a status message to the first device to notify the first device that the communication link has returned to normal, it also sends an ARP message to the user terminal device connected to the communication link, so that the user terminal device connected to the communication link can send service messages to the network terminal device through the second device.

[0120] Here, the process of the second device sending an ARP message to the user terminal device connected to the arbitrary communication link, so that the user terminal device connected to the arbitrary communication link can send service messages to the network terminal device through the second device, can be referred to in S103 above, which describes the process of the second device sending an ARP message to the user terminal device connected to the arbitrary communication link, so that the user terminal device connected to the arbitrary communication link can send service messages to the network terminal device through the first device. It will not be repeated here.

[0121] It can be seen that when the user terminal device connected by the arbitrary communication link forwards service packets to the network terminal device through the second device, the second device becomes the primary access device for the arbitrary communication link.

[0122] To enhance understanding of the route advertising method provided in the embodiments of this application, the following examples will further illustrate the route advertising method provided in the embodiments of this application.

[0123] Combination Figure 3 ,refer to Figure 5 ,exist Figure 5 In the multiple communication links on the user side of the access device 31 shown, if link 1 fails, the status message sent by access device 31 to access device 32 includes the host route of the user terminal device connected to link 1. For example, if the user terminal device connected to link 1 is... Figure 5 If the user terminal device is 1, then the access device 31 includes the host route of the user terminal device 1 in the status message sent to the access device 32.

[0124] Then, after determining that Link 1 is faulty based on the received status message, Access Device 32 modifies the host route attribute of User Terminal Device 1 connected to Link 1 to be publishable, and publishes the host route of User Terminal Device 1 carried in the status message to the network device in ISP 33. In this way, the network device can generate forwarding table entry 1 based on the received host route of User Terminal Device 1. Here, the destination address of forwarding table entry 1 is the host route of User Terminal Device 1, and the next-hop device of forwarding table entry 1 is Access Device 32.

[0125] Next, based on the primary / backup protocol running between access device 31 and access device 32, access device 32 also sends an ARP message to user device 1, so that user device can send service messages to network device via access device 32.

[0126] When the network device receives a service packet from user device 1 sent via access device 32, it executes step S103 based on the destination address in the response packet (i.e., the host route of user device 1) and the longest match mask method to determine whether to forward the response packet through forwarding table entry 1. That is, the network device sends the response packet to user device 1 via access device 32. Figure 5 As shown, user terminal device 1 and network terminal device communicate through link L2. This ensures that when link 1 on the user side of access device 31 fails, user terminal device 1 maintains consistent uplink and downlink paths when communicating with network terminal device through access device 32.

[0127] When access device 31 determines that the fault in link 1 has been repaired, it can notify access device 32 via a status message. In this case, based on the primary / backup protocol running between access device 31 and access device 32, access device 31 sends an ARP message to user device 1, so that user device 1 can send service messages to network devices via access device 31.

[0128] Simultaneously, after determining from the status message that the failure of link 1 has been recovered, access device 32 sends a route withdrawal message to the network device, causing the network device to invalidate or delete the forwarding table entry 1 generated based on the host route of user device 1. Furthermore, access device 32 also modifies the host route attribute of user device 1 from publishable back to non-publishable.

[0129] Thus, when a network device receives a service packet from user device 1 through access device 31, it determines, based on the destination address in the response packet, to forward the response packet using the forwarding table entry with the lowest cost value that includes the UNR (Unified Address Range) shared by access devices 31 and 32. That is, as follows... Figure 5 As shown, user terminal device 1 and network terminal device communicate via link L1. Further details are omitted.

[0130] Therefore, this application provides a route publishing method. In scenarios where the user-side communication link of the primary access device fails, and the backup access device forwards service packets from the user-end device connected to the failed communication link to the network device, the backup access device publishes a host route for the user-end device connected to the failed communication link to the network device. This causes the network device to generate a forwarding table entry with the host route as the destination address and the backup access device as the next-hop device. In this way, after the backup access device forwards the service packets from the user-end device connected to the failed communication link to the network device, the network device can forward response packets to the user-end device via the backup access device according to the forwarding table entry. This ensures that the uplink and downlink paths are consistent when the user-end device communicates through the backup access device and the network device, thus avoiding... Figure 1 The traffic detour problem is shown.

[0131] Since the method in this application is a route advertising method based on UNR with published address pool, the backup access device only publishes the host route of the user terminal device connected by the failed communication link when the user-side communication link of the primary access device fails. Therefore, it will not consume too many resources of the backup access device and the network terminal device. That is, the method ensures that the uplink and downlink paths are consistent when the user terminal device communicates through the backup access device and the network terminal device without affecting the performance of the access device.

[0132] The foregoing mainly describes the solutions provided by the embodiments of this application from a methodological perspective. To achieve the above functions, it includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0133] This application embodiment can divide the routing publishing device into functional modules according to the above method example. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0134] like Figure 6 As shown, Figure 6 A schematic diagram of a route publishing device 60 provided in an embodiment of this application is shown. The route publishing device 60 can be used to perform... Figure 4 The route advertising method is illustrated. The route advertising device 60 can be deployed on a first device, and a master-slave protocol runs between the first device and a second device. The first device is the backup device, and the second device is the master device. The second device is used to forward packets among multiple user terminal devices and network terminal devices when the link is normal. The route advertising device 60 may include a determining unit 61 and a sending unit 62.

[0135] The determining unit 61 is used to determine any communication link failure between the second device and multiple user terminal devices. The sending unit 62 is used to publish the host route of the user terminal device connected by the arbitrary communication link to the network terminal device. The host route instructs the network terminal device, upon receiving a service message from the user terminal device connected by the arbitrary communication link, to send a response message of that service message to the user terminal device connected by the arbitrary communication link via the first device.

[0136] As an example, combined Figure 4 The determining unit 61 can be used to execute S101, and the sending unit 62 can be used to execute S102.

[0137] Optionally, the route publishing device 60 further includes: a processing unit 63, configured to modify the attributes of the aforementioned host route to be publishable; and a sending unit 62, configured to send the host route to network end devices.

[0138] As an example, combined Figure 4 The processing unit 63 and the sending unit 62 can be used to execute S102.

[0139] Optionally, the route publishing device 60 further includes: a receiving unit 64, configured to receive a status message sent by the second device indicating the status of the communication link between the second device and multiple user terminal devices; and a determining unit 61, specifically configured to determine any communication link failure between the second device and the multiple user terminal devices based on the status message.

[0140] As an example, combined Figure 4 The receiving unit 64 and the determining unit 61 can be used to execute S101.

[0141] Optionally, the sending unit 62 and the receiving unit 64 are further configured to forward messages between the user terminal devices and network terminal devices connected by the arbitrary communication link after the determining unit 61 determines that any communication link between the second device and the plurality of user terminal devices is faulty.

[0142] As an example, combined Figure 4 The transmitting unit 62 and the receiving unit 64 can be used to execute S103.

[0143] Optionally, the determining unit 61 is further configured to determine the fault recovery of any of the aforementioned communication links. The processing unit 63 is further configured to revoke the host route published to the network end device and modify the attribute of the host route to be unpublishable.

[0144] As an example, combined Figure 4 The determining unit 61 and the processing unit 63 can be used to execute S104.

[0145] Optionally, the aforementioned host route is generated based on the address in the address pool shared by the first and second devices when the user terminal device connected by any of the aforementioned communication links requests to establish a connection with the network terminal device.

[0146] Optionally, the UNRs of the aforementioned address pool are pre-published to the network end devices by the first and second devices, respectively.

[0147] For a detailed description of the above-mentioned optional methods, please refer to the foregoing method embodiments, which will not be repeated here. Furthermore, the explanation of any of the route publishing devices 60 provided above, as well as the description of its beneficial effects, can be found in the corresponding method embodiments described above, and will not be repeated here.

[0148] As an example, combined Figure 2 The functions implemented by the determining unit 61 and the processing unit 63 in the route publishing device 60 can be achieved through... Figure 2 The processor 21 in the middle executes Figure 2 The program code in memory 22 is used for implementation. The functions implemented by the transmitting unit 62 and the receiving unit 64 can be achieved through... Figure 2 The communication interface 23 is implemented in the middle.

[0149] This application embodiment also provides a chip system 70, such as Figure 7 As shown, the chip system 70 includes at least one processor and at least one interface circuit. As an example, when the chip system 70 includes one processor and one interface circuit, the processor can be... Figure 7 The processor 71 shown in the solid box (or the processor 71 shown in the dashed box) can be an interface circuit. Figure 7 The interface circuit 72 is shown in the solid box (or the dashed box). When the chip system 70 includes two processors and two interface circuits, the two processors include... Figure 7 The processor 71 shown in the solid box and the processor 71 shown in the dashed box, these two interface circuits include Figure 7 Interface circuit 72 is shown in both solid and dashed boxes. No limitations are imposed on this.

[0150] The processor 71 and the interface circuit 72 can be interconnected via a line. For example, the interface circuit 72 can be used to receive signals (e.g., acquire status messages). As another example, the interface circuit 72 can be used to send signals to other devices (e.g., the processor 71). Exemplarily, the interface circuit 72 can read instructions stored in memory and send those instructions to the processor 71. When the instruction is executed by the processor 71, it can cause the routing publishing device to perform the steps in the above embodiments. Of course, the chip system 70 may also include other discrete components, and this application embodiment does not specifically limit this.

[0151] refer to Figure 8 , Figure 8 A hardware architecture diagram of processor 71 is shown.

[0152] like Figure 8 As shown, the processor 71 includes: at least one CPU, memory (the type of memory may include SRAM and ROM, for example), a microcontroller unit (MCU), a security subsystem, a WLAN subsystem, a bus, a transmission interface, etc. Although Figure 7As not shown in the diagram, the chip system 70 may also include an application processor (AP), an NPU, and other dedicated processors, as well as other subsystems such as a power management subsystem, a clock management subsystem, and a power consumption management subsystem.

[0153] The various parts of the chip system 70 are coupled together by connectors. For example, the connectors include various interfaces, transmission lines or buses. These interfaces are usually electrical communication interfaces, but may also be mechanical interfaces or other forms of interfaces. This embodiment does not limit them.

[0154] Optionally, the CPU can be a single-core or multi-core processor; alternatively, the CPU can be a processor group consisting of multiple processors, which are coupled to each other through one or more buses. In one optional case, the CPU implements any of the wireless screen projection methods described in the foregoing method embodiments by calling program instructions stored in on-chip memory or off-chip memory. In one optional case, the CPU and MCU jointly implement any of the wireless screen projection methods described in the foregoing method embodiments; for example, the CPU completes some steps of the wireless screen projection method, while the MCU completes other steps. In one optional case, the AP or other dedicated processor implements any of the wireless screen projection methods described in the foregoing method embodiments by calling program instructions stored in on-chip memory or off-chip memory.

[0155] This transmission interface can serve as the interface for the processor chip to receive and send data. It typically includes multiple interfaces; optionally, it may include an Inter-Integrated Circuit (I2C) interface, a Serial Peripheral Interface (SPI), a Universal Asynchronous Receiver-Transmitter (UART) interface, or a General-Purpose Input / Output (GPIO) interface. It should be understood that these interfaces can achieve different functions by multiplexing the same physical interface.

[0156] In one alternative, the transmission interface may also include High Definition Multimedia Interface (HDMI), V-By-One interface, Embedded Display Port (eDP), Mobile Industry Processor Interface (MIPI), or Display Port (DP), etc.

[0157] In one alternative scenario, the aforementioned components are integrated onto the same chip; in another alternative scenario, the memory can be a separate chip.

[0158] The security subsystem can be used to implement encryption algorithms related to security authentication. It should be understood that encryption algorithms related to security authentication are typically implemented in hardware, which can further enhance the security of the encryption algorithms.

[0159] A WLAN subsystem may include, for example, RF circuitry and a baseband.

[0160] Another embodiment of this application also provides a computer-readable storage medium storing instructions that, when executed on a routing publishing device, perform each step of the routing publishing device in the method flow shown in the above method embodiment.

[0161] In some embodiments, the disclosed method may be implemented as computer program instructions encoded in a machine-readable format on a computer-readable storage medium or on other non-transitory media or articles of art.

[0162] Figure 9 This illustration shows a schematic diagram of the structure of a signal carrying medium for carrying a computer program product, provided in an embodiment of this application. The signal carrying medium is used to store the computer program product or to store a computer program that executes computer processes on a computing device.

[0163] like Figure 9 As shown, the signal carrying medium 90 may include one or more program instructions, which, when executed by one or more processors, can provide the above-mentioned... Figure 4 The described function or part of the function. Therefore, for example, refer to... Figure 4 One or more features of S101 to S104 can be assumed by one or more instructions associated with the signal carrying medium 90. Furthermore, Figure 9 The program instructions in the document also describe example instructions.

[0164] In some examples, the signal carrying medium 90 may include a computer-readable medium 91, such as, but not limited to, a hard disk drive, a compact disc (CD), a digital video optical disc (DVD), a digital magnetic tape, a memory, read-only memory (ROM), or random access memory (RAM), etc.

[0165] In some implementations, the signal carrying medium 90 may include a computer recordable medium 92, such as, but not limited to, a memory, a read / write (R / W) CD, a R / W DVD, and so on.

[0166] In some implementations, the signal carrying medium 90 may include a communication medium 93, such as, but not limited to, digital and / or analog communication media (e.g., fiber optic cables, waveguides, wired communication links, wireless communication links, etc.).

[0167] The signal-bearing medium 90 can be transmitted by a wireless communication medium 93 (e.g., a wireless communication medium conforming to the IEEE 1902.11 standard or other transmission protocols). One or more program instructions can be, for example, computer-executable instructions or logical implementation instructions.

[0168] In some examples, such as targeting Figure 4 The described routing publishing device can be configured to provide various operations, functions, or actions in response to one or more program instructions in a computer-readable medium 91, a computer-recordable medium 92, and / or a communication medium 93.

[0169] It should be understood that the arrangements described herein are for illustrative purposes only. Therefore, those skilled in the art will understand that other arrangements and other elements (e.g., machines, interfaces, functions, sequences, and functional groups, etc.) can be used instead, and some elements may be omitted depending on the desired outcome. Furthermore, many of the described elements are functional entities that can be implemented as discrete or distributed components, or in any suitable combination and location with other components.

[0170] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When executed on a computer and when the computer execution instructions are executed, all or part of the processes or functions according to the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs).

[0171] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A route advertising method, characterized in that, The method is executed by a first device, and a master-slave protocol runs between the first device and a second device. The first device is the backup device, and the second device is the master device. The second device is used to forward packets among multiple user terminal devices and network terminal devices. The method includes: Determine any communication link failure between the second device and the plurality of user terminal devices; Based on the failure of any communication link, the network terminal device publishes the host route of the user terminal device connected by the arbitrary communication link to the network terminal device. The host route is used to instruct the network terminal device to send the response message of the service message to the user terminal device connected by the arbitrary communication link via the first device after receiving the service message from the user terminal device connected by the arbitrary communication link.

2. The method according to claim 1, characterized in that, The step of publishing the host route of the user terminal device connected to the arbitrary communication link to the network terminal device includes: Modify the properties of the host route to publishable; Send the host route to the network terminal device.

3. The method according to claim 1 or 2, characterized in that, Determining any communication link failure between the second device and the plurality of user terminal devices includes: Receive a status message sent by the second device, the status message being used to indicate the status of the communication link between the second device and the plurality of user terminal devices; Based on the status message, an arbitrary communication link failure is determined between the second device and the plurality of user terminal devices.

4. The method according to claim 1 or 2, characterized in that, After determining that any communication link between the second device and the plurality of user terminal devices is faulty, the method further includes: Messages are forwarded between the user terminal device and the network terminal device connected by the arbitrary communication link.

5. The method according to claim 1 or 2, characterized in that, The method further includes: Determine the fault recovery of the arbitrary communication link; Revoke the host route published to the network terminal device and modify the attribute of the host route to be unpublishable.

6. The method according to claim 1 or 2, characterized in that, The host route is generated based on the address pool shared by the first device and the second device when the user terminal device connected by the arbitrary communication link requests to establish a connection with the network terminal device.

7. The method according to claim 6, characterized in that, The user network segment routes (UNRs) of the address pool are pre-published by the first device and the second device to the network end devices, respectively.

8. A route publishing device, characterized in that, The device is deployed on a first device, and a master-slave protocol runs between the first device and the second device. The first device is the backup device, and the second device is the master device. The second device is used to forward packets between multiple user terminal devices and network terminal devices. The device includes: A determining unit is configured to determine any communication link failure between the second device and the plurality of user terminal devices; The sending unit is configured to publish a host route for the user terminal device connected to the arbitrary communication link to the network terminal device based on the failure of the arbitrary communication link. The host route is configured to instruct the network terminal device to send a response message of the service message to the user terminal device connected to the arbitrary communication link via the first device after receiving a service message from the user terminal device connected to the arbitrary communication link.

9. The apparatus according to claim 8, characterized in that, The device further includes: A processing unit is used to modify the attributes of the host route to be publishable; The sending unit is used to send the host route to the network terminal device.

10. The apparatus according to claim 8 or 9, characterized in that, The device further includes: A receiving unit is configured to receive a status message sent by the second device, the status message being used to indicate the status of the communication link between the second device and the plurality of user terminal devices; The determining unit is specifically used to determine any communication link failure between the second device and the plurality of user terminal devices based on the status message.

11. The apparatus according to claim 8 or 9, characterized in that, The sending unit and the receiving unit are further configured to forward messages between the user terminal device connected by the arbitrary communication link and the network terminal device after the determining unit determines that any communication link between the second device and the plurality of user terminal devices is faulty.

12. The apparatus according to claim 8 or 9, characterized in that, The determining unit is further configured to determine the fault recovery of the arbitrary communication link; The processing unit is further configured to revoke the host route published to the network terminal device and modify the attribute of the host route to be unpublishable.

13. The apparatus according to claim 8 or 9, characterized in that, The host route is generated based on the address pool shared by the first device and the second device when the user terminal device connected by the arbitrary communication link requests to establish a connection with the network terminal device.

14. The apparatus according to claim 13, characterized in that, The user network segment routes (UNRs) of the address pool are pre-published by the first device and the second device to the network end devices, respectively.

15. A route publishing device, characterized in that, The apparatus includes: one or more processors and a transmission interface, the one or more processors receiving or transmitting data through the transmission interface, the one or more processors being configured to invoke program instructions stored in a memory to cause the routing publishing apparatus to perform the method as described in any one of claims 1-7.

16. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes program instructions that, when executed on a computer or processor, cause the computer or processor to perform the method of any one of claims 1-7.

Images