Network element fallback processing method, apparatus, device, medium, and program product

Abstract

The application relates to the technical field of communication, and provides a network element back-to-normal processing method, device and equipment, a storage medium and a program product, the method is applied to a pool backup network element of a virtual wideband remote access server, and comprises the following steps: starting a back-to-normal process when detecting that a user plane fault recovery is back to normal, determining a user plane to be switched, a back-to-normal user plane, a user quantity and a user table item according to a user access report; issuing the user table item to the back-to-normal user plane; determining a switching time length according to the user quantity to start a timing task, and issuing the timing task to the back-to-normal user plane; the back-to-normal user plane executes the timing task, and when the timing task reaches a timing time length corresponding to the timing task, the user table item is enabled to back to normal the user plane to be switched. Through the time delay mechanism of the timing task, the user table item issued by the control plane is enabled in a timing manner, so that when the table item of the back-to-normal user plane takes effect, the control plane has completed the issuance of all table items, fast back-to-normal is realized, the back-to-normal time length is reduced, and the influence on services is reduced.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a network element back-switching processing method, apparatus, device, storage medium, and program product. Background Technology

[0002] A Virtual Broadband Remote Access Server (VBRAS) with separate control and switching mechanisms consists of two parts: the VBRAS Control Plane (VBRAS-CP) and the VBRAS User Plane (VBRAS-UP). The VBRAS-CP and VBRAS-UP communicate via a control plane interface protocol. In existing VBRAS-related solutions, VBRAS-UP is typically pooled and backed up by the VBRAS-CP. When VBRAS-UP fails, the relevant services on VBRAS-UP are switched over entirely via the VBRAS-CP, and when VBRAS-UP recovers, the entire service is switched back over.

[0003] During the VBRAS-UP handback process, it's necessary to first delete user-related entries in the original VBRAS-UP, such as user flow tables, pool standby interface ARP (Address Resolution Protocol) tables, and network segment routes, and then add these user-related entries to the VBRAS-UP during the handback. In current network applications, the number of users is growing rapidly. When a large number of users need to be handed back as a whole, it inevitably leads to increased processing by VBRAS-CP and the deletion of numerous user-related entries in VBRAS-UP, resulting in prolonged packet loss during the handback and impacting existing network services. How to minimize service impact during handback when there are a large number of users is a pressing issue that needs to be addressed. Summary of the Invention

[0004] This application provides a network element back-switching processing method, apparatus, device, storage medium, and program product to solve the defect in the prior art where, when there are a large number of users, back-switching the user plane of the virtual broadband remote access server causes a long period of packet loss, affecting the existing network services.

[0005] This application provides a network element switchback processing method, applied to the pooled backup network element of the Virtual Broadband Remote Access Server (VBRAS) control plane. The network element switchback processing method includes:

[0006] When the user plane failure recovery is detected, the failback process is initiated, and the user plane to be switched, the user plane to be switched back, the number of users, and the user table entries are determined according to the user access report.

[0007] The user table entry is sent to the user plane that is switched back;

[0008] The switching duration is determined based on the number of users to start a scheduled task, and the scheduled task is sent to the user plane that is switching back.

[0009] The user plane to be switched back executes the timed task. When the timed duration corresponding to the timed task is reached, the user table entry is used to switch back the user plane to be switched.

[0010] In one embodiment, the user entry includes a pool standby address resolution table, a user flow table, and a network segment route; the step of sending the user entry to the switchback user plane includes:

[0011] The pool backup address resolution table in the user table entry is sent to the operation fault management network element of the user plane that is switched back;

[0012] A first notification message is sent to the user management network element of the control plane; the first notification message is used to notify the user management network element to add a user flow table; the user management network element issues the user flow table in the user table entry to the operation fault management network element of the user plane according to the first notification message.

[0013] A second notification message is sent to the authentication management network element of the control plane; the second notification message is used to notify the authentication management network element to add a network segment route; the authentication management network element issues the network segment route in the user table entry to the authentication management network element of the user plane according to the second notification message.

[0014] In one embodiment, sending the scheduled task to the user plane during the switchback includes:

[0015] A third notification message is sent to the operation fault management network element of the user plane switching back; the third notification message contains the scheduled task, and the third notification message is used to notify the operation fault management network element of the user plane switching back to start the handover;

[0016] The operational fault management network element that switches back to the user plane parses the third notification message, obtains the scheduled task, and initiates the switchover.

[0017] In one embodiment, after determining the switching duration based on the number of users to start the scheduled task, the method further includes:

[0018] A fourth notification message is sent to the operation fault management network element of the user plane to be switched; the fourth notification message contains the scheduled task and is used to notify the operation fault management network element of the user plane to be switched that the switchover is complete.

[0019] The operation fault management network element of the user plane to be switched executes the scheduled task. When the scheduled duration corresponding to the scheduled task is reached, it ages and deletes the user flow table and the pool backup address resolution table in the user table entry, and sends a fifth notification message to the authentication management network element of the user plane to be switched.

[0020] The authentication management network element of the user plane to be switched deletes the network segment route in the user table entry according to the fifth notification message.

[0021] In one embodiment, the user plane switching back executes the scheduled task, and when the scheduled duration corresponding to the scheduled task is reached, the user table entry is used to switch back the user plane to be switched, including:

[0022] When the user plane is switched back to execute the scheduled task, and the scheduled duration is reached, the operation fault management network element in the user plane is activated by the pool backup address resolution table and user flow table in the user table, and sends a sixth notification message to the authentication management network element of the user plane.

[0023] The authentication management network element of the user plane to be switched back enables the network segment routing in the user table entry according to the sixth notification message, and performs the switchback on the user plane to be switched back.

[0024] In one embodiment, after sending the user entry to the back-switch user plane, the method further includes:

[0025] Send first configuration information to the user plane to be switched back, and send second configuration information to the user plane to be switched.

[0026] The first configuration information is used to set the user entries in the user plane being switched back to a first priority, and the second configuration information is used to set the user entries in the user plane to be switched to a second priority; the second priority is higher than the first priority;

[0027] Alternatively, the first configuration information is used to set the status of the user entries in the user plane to be switched back to an invalid state, and the second configuration information is used to set the status of the user entries in the user plane to be switched to an valid state.

[0028] This application embodiment also provides a network element back-switching processing device, including:

[0029] The task startup module is used to initiate the failover process when a user plane failure is detected and recovery is achieved. It determines the user plane to be switched, the user plane to be switched back, the number of users, and the user table entries based on the user access report.

[0030] The table entry distribution module is used to distribute the user table entry to the back-switch user plane;

[0031] The timed switchback module is used to determine the switchback duration based on the number of users to start a timed task, and to send the timed task to the switchback user plane;

[0032] The user plane to be switched back executes the timed task. When the timed duration corresponding to the timed task is reached, the user table entry is used to switch back the user plane to be switched.

[0033] This application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the steps of the network element back-switching processing method described above.

[0034] This application also provides a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the network element back-switching processing method described above.

[0035] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the network element back-switching processing method described above.

[0036] The network element back-off processing method, apparatus, device, storage medium, and program product provided in this application embodiment distribute user entries to the back-off user plane and determine the handover duration based on the number of users to be back-off. This initiates a timed task to be distributed to the back-off user plane. The back-off user plane executes the timed task distributed by the control plane and periodically enables the user entries distributed by the control plane. This ensures that when the back-off user plane entries take effect, the control plane has completed the distribution of all user entries, achieving rapid back-off of the user plane. This helps reduce the back-off duration and thus minimizes the impact on user services. Attached Figure Description

[0037] To more clearly illustrate the technical solutions in this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0038] Figure 1 This is a flowchart illustrating the network element back-switching processing method provided in the embodiments of this application;

[0039] Figure 2 This is a schematic diagram of the network element switchback process provided by existing technology;

[0040] Figure 3This is a schematic diagram of the network element back-switching process provided in the embodiments of this application;

[0041] Figure 4 This is a schematic diagram of the network element back-switching processing device provided in the embodiments of this application;

[0042] Figure 5 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0043] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0044] This application provides a network element rollback processing method applied to the pooled backup network element of the Virtual Broadband Remote Access Server (VBRAS) control plane (i.e., VBRAS-CP) to address the problems existing in the current rollback process. During the service rollback process, user entries are added but not yet effective. By setting a delay mechanism, the user entries take effect later, ensuring that by the time the rollback user plane entries take effect, the control plane has already distributed all user entries related to this rollback, thus minimizing the impact on services during user service rollback. The delay duration can be determined based on the number of users requiring rollback.

[0045] Specifically, Figure 1 This is a flowchart illustrating the network element handover processing method provided in the embodiments of this application, as shown below. Figure 1 As shown in the embodiments of this application, the network element back-switching processing method includes the following steps:

[0046] Step 100: When the user plane failure recovery is detected, the handover process is started. The user plane to be switched, the user plane to be switched back, the number of users, and the user table entries are determined according to the user access report.

[0047] Step 200: Send the user table entry to the user plane that has switched back;

[0048] Step 300: Determine the switching duration based on the number of users to start a scheduled task, and send the scheduled task to the user plane that is switching back.

[0049] The user plane to be switched back executes the timed task. When the timed duration corresponding to the timed task is reached, the user table entry is used to switch back the user plane to be switched.

[0050] When a failover user plane (i.e., failover UP) failure is detected and recovery is achieved, the failover process is initiated. Based on the user access report, the user plane to be switched over, the user plane to be switched over, the number of users, and the user entries are determined. Among them, the user plane to be switched over is the user plane that was pooled and backed up when the failover user plane failed.

[0051] VBRAS-CP can obtain user access packets and generate user access reports when a user comes online. When initiating the handover process, the VBRAS-CP's backup network elements determine the data required for handover based on the user access report. The user plane to be switched is the VBRAS user plane UP (Upon Switching), hereinafter referred to as UP; the user plane to be switched back is the VBRAS user plane UP (Upon Switching), hereinafter referred to as UP. The handover process involves switching all user services in the UP to the UP.

[0052] Optionally, the start of the rollback process can be initiated actively when the rollback UP fails and recovers, or it can be passively triggered based on the rollback request of the rollback UP when the rollback UP fails and recovers. There are no specific limitations on this.

[0053] Furthermore, user entries are sent back to the UP. The user entries to be sent can include one or more. When there are multiple user entries, the sending of user entries can be done in parallel or sequentially, without any specific limitation here.

[0054] The required switching duration is determined based on the number of users. A scheduled task is then started based on this switching duration. Optionally, the duration of the scheduled task is the switching duration itself. The scheduled task is sent to the UP that is switching back. The UP executes the scheduled task, and when the corresponding duration is reached, the sent user entries are activated, thereby switching back the user plane of the VBRAS and transferring the user services of the VBRAS-UP from the UP that is waiting to switch back to the UP that is switching back.

[0055] Among them, a scheduled task is sent to the UP to activate the user table entries at regular intervals. This means that a delay mechanism is set for the UP to ensure that by the time the user table entries of the UP take effect, VBRAS-CP has completed the distribution of all user table entries, thus ensuring that the impact on business can be reduced when user services are switched back.

[0056] In some embodiments, when the number of users is large and the switching time is long, batch control of the switching-back users can be implemented based on the delay mechanism of the scheduled task. Specifically, the switching-back users are divided into multiple batches, and the user table entries corresponding to all the switching-back users are also divided into multiple groups. Each batch of switching-back users corresponds to a group of user table entries. First, the switching time is determined based on the number of switching-back users in the current batch. Then, a scheduled task of the corresponding duration is started, and the user table entries of the switching-back users in the current batch are sent to the switching-back UP, thereby switching back the users in batches.

[0057] In this embodiment, by sending user entries to the user plane that is being switched back, and determining the switching duration based on the number of users to be switched back as needed, a timed task is initiated and sent to the user plane that is being switched back. The user plane that is being switched back executes the timed task sent by the control plane, periodically activating the user entries sent by the control plane. This ensures that when the entries on the user plane that are being switched back take effect, the control plane has already sent all user entries, enabling a fast switchback of the user plane. This helps to reduce the switchback duration and thus reduce the impact on user services.

[0058] In one embodiment, enabling a user entry can be achieved by setting the validity status or priority of the user entry in the fallback UP. Specifically, after issuing the user entry to the fallback UP in step 200, it may further include:

[0059] Step 201: Send first configuration information to the user plane to be switched back, and send second configuration information to the user plane to be switched.

[0060] The first configuration information is used to set the user entries in the user plane being switched back to a first priority, and the second configuration information is used to set the user entries in the user plane to be switched to a second priority; the second priority is higher than the first priority;

[0061] Alternatively, the first configuration information is used to set the status of the user entries in the user plane to be switched back to an invalid state, and the second configuration information is used to set the status of the user entries in the user plane to be switched to an valid state.

[0062] Send first configuration information to the UP that is switched back, and send second configuration information to the UP that is to be switched over. The first configuration information is used to configure the user entries in the UP that is switched back, and the second configuration information is used to configure the user entries in the UP that is to be switched over.

[0063] Specifically, the first configuration information is used to set the user entries in the UP to be switched back to the first priority, and the second configuration information is used to set the user entries in the UP to be switched to the second priority, with the second priority being higher than the first priority.

[0064] The UP that switches back sets its own user entries to first priority based on the first configuration information, and similarly, the UP that is to be switched over sets its own user entries to second priority based on the second configuration information. Optionally, user entries sent to the UP that switches back can be set to low priority, while user entries on the UP that is to be switched over have a higher priority, allowing service forwarding from the UP that is to be switched over. After the scheduled task is completed, the user entries on the UP that is to be switched over are deleted, the user entries on the UP that switches back become higher priority, and the user entries automatically take effect, thus completing the activation of the user entries.

[0065] Alternatively, the first configuration information is used to set the status of the user entries in the UP to be switched back to an invalid state, and the second configuration information is used to set the status of the user entries in the UP to be switched to an valid state.

[0066] The UP that switches back sets its own user entries to an invalid state based on the first configuration information. Similarly, the UP that is to be switched over sets its own user entries to an active state based on the second configuration information. Optionally, the user entries sent to the UP that switches back are set to invalid. In this case, only the user entries on the UP that is to be switched over are active. Therefore, service forwarding can be performed from the UP that is to be switched over. After the scheduled task is completed, the user entries on the UP that is to be switched over are deleted. At the same time, the UP that switches back is notified to set the status of the user entries to active state, thereby completing the activation of the user entries.

[0067] In one embodiment, the user entries include a pool standby address resolution table, a user flow table, and a network segment route. The pool standby address resolution table is the pool standby interface ARP table. The distribution of user entries is based on a message mechanism. Specifically, in step 200, the distribution of user entries to the switchback UP includes:

[0068] Step 210: Send the pool backup address resolution table in the user table entry to the operation fault management network element of the user plane that is switching back;

[0069] Step 220: Send a first notification message to the user management network element of the control plane; the first notification message is used to notify the user management network element to add a user flow table; the user management network element issues the user flow table in the user table entry to the operation fault management network element of the user plane according to the first notification message;

[0070] Step 230: Send a second notification message to the authentication management network element of the control plane; the second notification message is used to notify the authentication management network element to add a network segment route; the authentication management network element issues the network segment route in the user table to the authentication management network element of the user plane according to the second notification message.

[0071] The pool standby interface ARP table, user flow table, and network segment route are distributed by different network elements in the control plane VBRAS-CP, and are uniformly managed by the pool standby network element. When distributing user table entries to the switchback UP, the pool standby address resolution table, i.e., the pool standby interface ARP table, in the user table entries is first distributed to the Operation Failure Management (OFUM) network element in the switchback UP.

[0072] Then, a first notification message is sent to the User Management (UM) network element of VBRAS-CP. This first notification message is used to notify the UM network element to add the user flow table. Based on the first notification message, the UM network element sends the user flow table in the user table entries to the OFUM network element that has switched back to UP.

[0073] Furthermore, a second notification message is sent to the Authentication Management (AM) network element of the VBRAS-CP. This second notification message is used to notify the AM network element to add a network segment route. Based on this second notification message, the AM network element distributes the network segment route from the user table to the AM network element that has switched back to UP.

[0074] Optionally, both the first and second notification messages may contain the identifier and address information of the UP switchback, so as to facilitate the distribution of network segment routes by the AM network element of VBRAS-CP and the distribution of user flow tables by the UM network element.

[0075] In one embodiment, the dispatching of scheduled tasks is also implemented based on a message mechanism. In step 300, dispatching the scheduled task to the callback UP includes:

[0076] Step 310: Send a third notification message to the operation fault management network element of the user plane switching back; the third notification message contains the scheduled task, and the third notification message is used to notify the operation fault management network element of the user plane switching back to start the handover.

[0077] The operational fault management network element that switches back to the user plane parses the third notification message, obtains the scheduled task, and initiates the switchover.

[0078] A third notification message is sent to the OFUM network element that is switched back to UP. This third notification message contains a scheduled task to notify the OFUM network element that is switched back to UP to initiate the handover. The OFUM network element in the switched-back UP parses the received third notification message, obtains the customized task, and initiates the handover.

[0079] In one embodiment, after starting the scheduled task, it is necessary to send the scheduled task not only to the fallback UP but also to the UP to be switched over. This allows the user entries in the fallback UP to be deleted from the UP to be switched over periodically after they take effect, thus completing the user service switchover. Therefore, after determining the switchover duration based on the number of users to start the scheduled task in step 300, it may further include:

[0080] Step 301: Send a fourth notification message to the operation fault management network element of the user plane to be switched; the fourth notification message contains the scheduled task and is used to notify the operation fault management network element of the user plane to be switched that the switchover is complete;

[0081] The operation fault management network element of the user plane to be switched executes the scheduled task. When the scheduled duration corresponding to the scheduled task is reached, it ages and deletes the user flow table and the pool backup address resolution table in the user table entry, and sends a fifth notification message to the authentication management network element of the user plane to be switched.

[0082] The authentication management network element of the user plane to be switched deletes the network segment route in the user table entry according to the fifth notification message.

[0083] The scheduled task is also implemented based on a message mechanism when it is sent to the UP (Up Unit) to be switched over. Specifically, a fourth notification message containing the scheduled task is sent to the OFUM (Output Unit) network element of the UP to be switched over. This fourth notification message is used to notify the OFUM network element of the UP to be switched over that the switchover is complete. The OFUM network element of the UP to be switched over executes the scheduled task. When the scheduled timeout period is reached, it ages and deletes the user flow table and the pool standby interface ARP table in the UP to be switched over, and sends a fifth notification message to the AM (Advanced Management Unit) network element of the UP to be switched over. This fifth notification message is used to notify the AM network element of the UP to age and delete the network segment routes. The AM network element of the UP to be switched over then ages and deletes the network segment routes in the UP to be switched over based on the received fifth notification message.

[0084] Optionally, when enabling user entries during the handover UP, different entries from the user table are sent to different network elements of the handover UP. Therefore, different network elements need to enable the sent entries separately. Thus, the handover UP executes a scheduled task. When the scheduled duration is reached, the user table entries are enabled for the UP to be switched over, specifically including:

[0085] When the user plane is switched back to execute the scheduled task, and the scheduled duration is reached, the operation fault management network element in the user plane is activated by the pool backup address resolution table and user flow table in the user table, and sends a sixth notification message to the authentication management network element of the user plane.

[0086] The authentication management network element of the user plane to be switched back enables the network segment routing in the user table entry according to the sixth notification message, and performs the switchback on the user plane to be switched back.

[0087] When the UP (Up) is switched back, it executes a scheduled task. Upon reaching the scheduled duration, the OFUM (Output Node) element of the UP activates the user flow table and the pool standby interface ARP table, and sends a sixth notification message to the AM (Advanced Node) element. This sixth notification message notifies the AM element to enable segment routing. Based on the received sixth notification message, the AM element enables the assigned segment routing, thus performing the switchback for the UP.

[0088] In some embodiments, when switching back users in batches based on the delay mechanism of the scheduled task, for the current batch of switched-back users, the corresponding user table entries for the current batch are issued. When the switchback UP executes the scheduled task, the user table entries corresponding to the current batch of switched-back users are activated when the scheduled task's duration is reached. Similarly, when the pending switchback UP executes the scheduled task, the user table entries corresponding to the current batch of switched-back users are aged out and deleted when the scheduled task's duration is reached.

[0089] In one embodiment, refer to Figure 2 The existing VBRAS-UP handover process, as shown, firstly, in the event of a handover UP failure, the user services of the handover UP are switched to a new VBRAS-UP, which is the UP to be switched over. During service switching, the ACCESS network element of the VBRAS-CP is responsible for the management and control of access users and the forwarding of user data. When a user dials up, they request an address from the AM network element of the VBRAS-CP, and the AM network element of the VBRAS-CP sends the user flow table to the AM network element of the UP to be switched over. When the handover UP failure is recovered, the pool standby network element initiates the handover process and notifies the UM network element of the VBRAS-CP to perform the switchover. The UM network element notifies the OFUM network element to be switched up to delete the user flow table and sends the user flow table back to the OFUM network element to be switched back up; the pool standby network element notifies the AM network element of the VBRAS-CP to perform a network segment route switch, and the AM network element of the VBRAS-CP further notifies the AM network element to be switched up to delete the network segment route and sends the network segment route back to the AM network element to be switched back up; then, the pool standby network element notifies the OFUM network element to be switched up to delete the pool standby interface ARP table and sends the pool standby interface ARP table back to the OFUM network element to be switched back up.

[0090] Therefore, during the VBRAS-UP handover process, it is necessary to sequentially delete and distribute user flow tables, network segment routes, and pool backup interface ARP tables to complete the user service switchover. This handover method will cause user service interruption, especially when there are a large number of users in the backup pool. The handover process after a failure during the UP handover has a long convergence time, which will also affect surrounding services.

[0091] Furthermore, referring to Figure 3 The VBRAS-UP handover process provided in this embodiment of the application, as shown, involves the pool standby network element initiating the handover process. Immediately after initiating the handover, it sends the pool standby interface ARP table to the OFUM network element of the handover UP, and then notifies the UM network element of the VBRAS-CP to add a user flow table. The UM network element then sends the user flow table to the OFUM network element of the handover UP based on the notification message from the pool standby network element. Further, the pool standby network element notifies the AM network element of the VBRAS-CP to add a network segment route, and the AM network element of the VBRAS-CP sends the network segment route to the AM network element of the handover UP based on the notification message from the pool standby network element.

[0092] The pool standby network element determines the handover duration based on the number of users switching back, and then initiates a scheduled task based on this duration, sending it to both the UP (Upset Controller) and the UP to be switched over. It also notifies the OFUM (Output Node) element of the UP to be switched over that the handover is complete, and notifies the OFUM element of the UP to initiate the handover. On one hand, the OFUM element of the UP to be switched over executes the scheduled task. Upon reaching the corresponding timeout period, it ages and deletes the user flow table and the pool standby interface ARP table, and then notifies the AM (Advanced Node) element of the UP to be switched over to age and delete the network segment routes. On the other hand, the OFUM element of the UP to be switched back executes the scheduled task. Upon reaching the corresponding timeout period, it enables user scarring and the pool standby interface ARP table, and then notifies the AM element of the UP to be switched back to enable the network segment routes, completing the handover back to the VBRAS-UP.

[0093] Furthermore, in the VBRAS-UP handover process shown in Figure 3, the scheduled task is started based on a timer, and the activation of user entries is implemented based on the timer's delay mechanism. Specifically, the user entries sent to the handover UP can be set to low priority. At this time, the user entries on the UP to be switched over have a higher priority. Therefore, service forwarding is performed on the UP to be switched over. After the timer's duration is reached, the user entries on the UP to be switched over are deleted, and the user entries on the handover UP are then activated.

[0094] Alternatively, the status of the user entries sent to the switchback UP can be set to invalid. In this case, the user entries on the pending switchback UP will be valid, allowing service forwarding from the pending switchback UP. When the timer expires, the user entries on the pending switchback UP are deleted, and the switchback UP is notified to set the user entries to valid, thereby enabling the user entries on the switchback UP and completing the switchback.

[0095] In this embodiment, a scheduled task is started according to the number of users that need to be switched. A delay mechanism is used to enable and send the user entries to the switchback UP, ensuring that the user entries have been sent by the time the user entries on the switchback UP are enabled. This avoids packet loss caused by the deletion and addition of user entries, effectively reduces packet loss time, and reduces the impact of the switchback process on user services.

[0096] Furthermore, a scheduled task delay mechanism enables batch control of users switching back. The delay duration is calculated based on the required number of users to be switched back, and user flow tables, pool standby interface ARP tables, and network segment routes are periodically activated. This ensures that all entries related to the users in this batch are distributed during the switchback process, guaranteeing rapid traffic switching back once the scheduled task delay is reached and various user table entries are activated. Especially when there are many users, batch switchback processing can be performed, avoiding excessively long switchover times during a single process, which could lead to significant packet loss and impact on user services. This effectively prevents network instability and anomalies caused by switchbacks, improving overall network stability.

[0097] The network element back-switching processing apparatus provided in the embodiments of this application is described below. The network element back-switching processing apparatus described below can be referred to in correspondence with the network element back-switching processing method described above.

[0098] Reference Figure 4 The network element back-switching processing device provided in this application embodiment includes:

[0099] Task startup module 10 is used to start the back-off process when the user plane failure is detected to be recovered, and to determine the user plane to be switched, the user plane to be switched back, the number of users and the number of user entries based on the user access report;

[0100] The table entry distribution module 20 is used to distribute the user table entry to the back-switching user plane;

[0101] The timed switchback module 30 is used to determine the switchback duration based on the number of users to start a timed task, and to send the timed task to the switchback user plane;

[0102] The user plane to be switched back executes the timed task. When the timed duration corresponding to the timed task is reached, the user table entry is used to switch back the user plane to be switched.

[0103] In one embodiment, the user entry includes a pool standby address resolution table, a user flow table, and a network segment route; the entry distribution module 20 is further configured to:

[0104] The pool backup address resolution table in the user table entry is sent to the operation fault management network element of the user plane that is switched back;

[0105] A first notification message is sent to the user management network element of the control plane; the first notification message is used to notify the user management network element to add a user flow table; the user management network element issues the user flow table in the user table entry to the operation fault management network element of the user plane according to the first notification message.

[0106] A second notification message is sent to the authentication management network element of the control plane; the second notification message is used to notify the authentication management network element to add a network segment route; the authentication management network element issues the network segment route in the user table entry to the authentication management network element of the user plane according to the second notification message.

[0107] In one embodiment, the timed back-cut module 30 is further configured to:

[0108] A third notification message is sent to the operation fault management network element of the user plane switching back; the third notification message contains the scheduled task, and the third notification message is used to notify the operation fault management network element of the user plane switching back to start the handover;

[0109] The operational fault management network element that switches back to the user plane parses the third notification message, obtains the scheduled task, and initiates the switchover.

[0110] In one embodiment, the timed back-cut module 30 is further configured to:

[0111] A fourth notification message is sent to the operation fault management network element of the user plane to be switched; the fourth notification message contains the scheduled task and is used to notify the operation fault management network element of the user plane to be switched that the switchover is complete.

[0112] The operation fault management network element of the user plane to be switched executes the scheduled task. When the scheduled duration corresponding to the scheduled task is reached, it ages and deletes the user flow table and the pool backup address resolution table in the user table entry, and sends a fifth notification message to the authentication management network element of the user plane to be switched.

[0113] The authentication management network element of the user plane to be switched deletes the network segment route in the user table entry according to the fifth notification message.

[0114] In one embodiment, the user plane switching back executes the scheduled task, and when the scheduled duration corresponding to the scheduled task is reached, the user table entry is used to switch back the user plane to be switched, including:

[0115] When the user plane is switched back to execute the scheduled task, and the scheduled duration is reached, the operation fault management network element in the user plane is activated by the pool backup address resolution table and user flow table in the user table, and sends a sixth notification message to the authentication management network element of the user plane.

[0116] The authentication management network element of the user plane to be switched back enables the network segment routing in the user table entry according to the sixth notification message, and performs the switchback on the user plane to be switched back.

[0117] In one embodiment, the table entry issuing module 20 is further configured to:

[0118] Send first configuration information to the user plane to be switched back, and send second configuration information to the user plane to be switched.

[0119] The first configuration information is used to set the user entries in the user plane being switched back to a first priority, and the second configuration information is used to set the user entries in the user plane to be switched to a second priority; the second priority is higher than the first priority;

[0120] Alternatively, the first configuration information is used to set the status of the user entries in the user plane to be switched back to an invalid state, and the second configuration information is used to set the status of the user entries in the user plane to be switched to an valid state.

[0121] Figure 5 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 5 As shown, the electronic device may include: a processor 510, a communications interface 520, a memory 530, and a communication bus 540, wherein the processor 510, the communications interface 520, and the memory 530 communicate with each other via the communication bus 540. The processor 510 can call logical instructions in the memory 530 to execute the steps of the network element handover processing method, which includes:

[0122] When the user plane failure recovery is detected, the failback process is initiated, and the user plane to be switched, the user plane to be switched back, the number of users, and the user table entries are determined according to the user access report.

[0123] The user table entry is sent to the user plane that is switched back;

[0124] The switching duration is determined based on the number of users to start a scheduled task, and the scheduled task is sent to the user plane that is switching back.

[0125] The user plane to be switched back executes the timed task. When the timed duration corresponding to the timed task is reached, the user table entry is used to switch back the user plane to be switched.

[0126] Furthermore, the logical instructions in the aforementioned memory 530 can be implemented as software functional units and, when sold or used as independent products, can be stored in a 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 a portion 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 a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0127] On the other hand, this application also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can perform the steps of the network element back-switching processing method provided in the above embodiments. The method includes:

[0128] When the user plane failure recovery is detected, the failback process is initiated, and the user plane to be switched, the user plane to be switched back, the number of users, and the user table entries are determined according to the user access report.

[0129] The user table entry is sent to the user plane that is switched back;

[0130] The switching duration is determined based on the number of users to start a scheduled task, and the scheduled task is sent to the user plane that is switching back.

[0131] The user plane to be switched back executes the timed task. When the timed duration corresponding to the timed task is reached, the user table entry is used to switch back the user plane to be switched.

[0132] In another aspect, this application also provides a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the network element handover processing method provided in the above embodiments, the method comprising:

[0133] When the user plane failure recovery is detected, the failback process is initiated, and the user plane to be switched, the user plane to be switched back, the number of users, and the user table entries are determined according to the user access report.

[0134] The user table entry is sent to the user plane that is switched back;

[0135] The switching duration is determined based on the number of users to start a scheduled task, and the scheduled task is sent to the user plane that is switching back.

[0136] The user plane to be switched back executes the timed task. When the timed duration corresponding to the timed task is reached, the user table entry is used to switch back the user plane to be switched.

[0137] The device embodiments described above are merely illustrative. 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 modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0138] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0139] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for network element back-switching processing, characterized in that, A pooled backup network element applied to the control plane of a Virtual Broadband Remote Access Server (VBRAS) includes a network element switchback processing method comprising: When the user plane failure recovery is detected, the failback process is initiated, and the user plane to be switched, the user plane to be switched back, the number of users, and the user table entries are determined based on the user access report. The user table entry is sent to the user plane that is switched back; The required switching duration for the rollback is determined based on the number of users to start a scheduled task, and the scheduled task is sent to the user plane being rolled back. The user plane to be switched back executes the timed task. When the timed duration corresponding to the timed task is reached, the user table entry is used to switch back the user plane to be switched. The timed duration is the switching duration. After determining the handover duration based on the number of users to start the scheduled task, the method further includes: sending a fourth notification message to the user plane to be switched; the fourth notification message contains the scheduled task; the user plane to be switched executes the scheduled task, and when the scheduled duration corresponding to the scheduled task is reached, it ages and deletes the user flow table, pool backup address resolution table and network segment route in the user table entry.

2. The network element back-switching processing method according to claim 1, characterized in that, The user entries include the pool standby address resolution table, user flow table, and network segment routing; Sending the user table entry to the back-switch user plane includes: The pool backup address resolution table in the user table entry is sent to the operation fault management network element of the user plane that is switched back; A first notification message is sent to the user management network element of the control plane; the first notification message is used to notify the user management network element to add a user flow table; the user management network element issues the user flow table in the user table entry to the operation fault management network element of the user plane according to the first notification message. A second notification message is sent to the authentication management network element of the control plane; the second notification message is used to notify the authentication management network element to add a network segment route; the authentication management network element issues the network segment route in the user table entry to the authentication management network element of the user plane according to the second notification message.

3. The network element back-switching processing method according to claim 1, characterized in that, The step of sending the scheduled task to the user plane that switches back includes: A third notification message is sent to the operation fault management network element of the user plane switching back; the third notification message contains the scheduled task, and the third notification message is used to notify the operation fault management network element of the user plane switching back to start the handover; The operational fault management network element that switches back to the user plane parses the third notification message, obtains the scheduled task, and initiates the switchover.

4. The network element back-switching processing method according to claim 1, characterized in that, The user plane being switched back executes the scheduled task. When the scheduled duration corresponding to the scheduled task is reached, the user table entry is used to switch back the user plane to be switched, including: When the user plane is switched back to execute the scheduled task, and the scheduled duration is reached, the operation fault management network element in the user plane is activated by the pool backup address resolution table and user flow table in the user table, and sends a sixth notification message to the authentication management network element of the user plane. The authentication management network element of the user plane to be switched back enables the network segment routing in the user table entry according to the sixth notification message, and performs the switchback on the user plane to be switched back.

5. The network element back-switching processing method according to claim 1, characterized in that, After sending the user table entry to the back-switch user plane, the method further includes: Send first configuration information to the user plane to be switched back, and send second configuration information to the user plane to be switched. The first configuration information is used to set the user entries in the user plane being switched back to a first priority, and the second configuration information is used to set the user entries in the user plane to be switched to a second priority; the second priority is higher than the first priority; Alternatively, the first configuration information is used to set the status of the user entries in the user plane to be switched back to an invalid state, and the second configuration information is used to set the status of the user entries in the user plane to be switched to an valid state.

6. A network element back-cutting processing device, characterized in that, include: The task startup module is used to initiate the failover process when a user plane failure is detected and recovery is achieved. It determines the user plane to be switched, the user plane to be switched back, the number of users, and the user table entries based on the user access report. The table entry distribution module is used to distribute the user table entry to the back-switch user plane; The timed rollback module is used to determine the required switching duration for rollback based on the number of users, start a timed task, and send the timed task to the user plane being rolled back. The user plane to be switched back executes the timed task. When the timed duration corresponding to the timed task is reached, the user table entry is used to switch back the user plane to be switched. The timing duration is the switching duration; After determining the handover duration based on the number of users to start the scheduled task, the method further includes: sending a fourth notification message to the user plane to be switched; the fourth notification message contains the scheduled task; the user plane to be switched executes the scheduled task, and when the scheduled duration corresponding to the scheduled task is reached, it ages and deletes the user flow table, pool backup address resolution table and network segment route in the user table entry.

7. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps of the network element back-switching processing method as described in any one of claims 1 to 5.

8. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the network element back-switching processing method as described in any one of claims 1 to 5.

9. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the network element back-switching processing method as described in any one of claims 1 to 5.

Images