A network scheduling method, apparatus, and storage medium based on cloud private lines

Abstract

This application discloses a network scheduling method, apparatus, and storage medium based on cloud private lines, applicable to the fields of mapping and cloud technologies. By configuring an access control list in response to a scheduling request, the method obtains the session packets corresponding to the private line to be migrated. Then, the session packets are simultaneously sent to both the original gateway and the target gateway. This triggers the gateway controller to send configuration information to the target gateway, enabling the target gateway to create a target session in an executing state based on the configuration information and the session packets. This achieves a lossless network scheduling process for cloud private lines. Because session packets are copied during scheduling and the session is configured through the gateway controller, data involved in the session is protected, improving data integrity during cloud private line network scheduling.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a network scheduling method, apparatus and storage medium based on cloud private lines. Background Technology

[0002] With the rapid development of internet technology, people have increasingly higher requirements for network quality. Cloud leased lines are a high-speed, low-latency, stable and secure dedicated connection channel between a user's local data center and a cloud server. It is a static leased line. In some cases, it is necessary to migrate a static leased line and its associated bidirectional forwarding detection (BFD) connection from one availability zone to another to improve network quality.

[0003] Generally, you can first close the static channel with the customer and disable BFD on the existing availability zone, and then open the static channel and start the BFD session to renegotiate on the target availability zone. Once the BFD status is negotiated up, the static channel can be used.

[0004] However, data is generated during the channel closure process, and this data may be lost, affecting the integrity of data during network scheduling. Summary of the Invention

[0005] In view of this, this application provides a network scheduling method based on cloud private lines, which can effectively improve the integrity of data during the network scheduling process.

[0006] The first aspect of this application provides a network scheduling method based on cloud private lines, which can be applied to a system or program in a terminal device that includes network scheduling functionality based on cloud private lines, specifically including:

[0007] In response to a scheduling request, an access control list is configured to obtain the session message corresponding to the leased line to be migrated. The scheduling request is used to instruct the leased line to be migrated from the first availability zone to the second availability zone.

[0008] The session message is copied and simultaneously sent to the first cloud private line gateway in the first availability zone and the second cloud private line gateway in the second availability zone. The first cloud private line gateway and the second cloud private line gateway are configured based on the gateway controller.

[0009] The gateway controller is triggered to send the configuration information corresponding to the leased line to be migrated in the first cloud leased line gateway to the second cloud leased line gateway, so that the second cloud leased line gateway creates a target session in the execution state according to the configuration information and the session message. The target session is used to execute the service corresponding to the leased line to be migrated.

[0010] Optionally, in some possible implementations of this application, the step of triggering the gateway controller to send the configuration information corresponding to the leased line to be migrated in the first cloud leased line gateway to the second cloud leased line gateway, so that the second cloud leased line gateway creates a target session in an execution state according to the configuration information and the session message, includes:

[0011] The gateway controller is triggered to send the configuration information corresponding to the leased line to be migrated in the first cloud leased line gateway to the second cloud leased line gateway, so that the second cloud leased line gateway can determine the address information, transmit and receive parameter information and channel information corresponding to the leased line to be migrated in the configuration information, as well as the receiver data information and sender data information indicated in the session message;

[0012] The second cloud private line gateway determines that it creates the target session in the execution state based on the address information, the transmit and receive parameter information, the channel information, the receiver data information, and the sender data information.

[0013] Optionally, in some possible implementations of this application, after the method triggers the gateway controller to send the configuration information corresponding to the leased line to be migrated in the first cloud leased line gateway to the second cloud leased line gateway, so that the second cloud leased line gateway creates a target session in the execution state according to the configuration information and the session message, the method further includes:

[0014] The routing information corresponding to the leased line to be migrated is sent to the second cloud leased line gateway through the user edge router in the second availability zone.

[0015] The gateway controller sends a deletion command to the first cloud private line gateway, so that the first cloud private line gateway deletes the routing information corresponding to the private line to be migrated.

[0016] Delete the access control list configured in the access switch and adjust the sending target of the session message to the second cloud private line gateway.

[0017] Optionally, in some possible implementations of this application, the step of sending a deletion command to the first cloud private line gateway through the gateway controller, so that the first cloud private line gateway deletes the routing information corresponding to the private line to be migrated, includes:

[0018] The gateway controller sends a deletion command to the first cloud private line gateway, so that the first cloud private line gateway intercepts the stop message sent to the user edge router. In response to the interception of the stop message, the first cloud private line gateway deletes the routing information corresponding to the private line to be migrated.

[0019] Optionally, in some possible implementations of this application, before the gateway controller sends a deletion command to the first cloud private line gateway so that the first cloud private line gateway deletes the routing information corresponding to the private line to be migrated, the method further includes:

[0020] Obtain the execution message sent by the second cloud private line gateway, the execution message containing the first negotiation message configured by the second cloud private line gateway;

[0021] The second negotiation message is fed back to the second cloud private line gateway based on the first negotiation message, and the correspondence between the first negotiation message and the second negotiation message is obtained based on the target session configuration.

[0022] Optionally, in some possible implementations of this application, obtaining the execution message sent by the second cloud private line gateway includes:

[0023] Determine the packet detection multiplier information corresponding to the target session;

[0024] The information sent by the second cloud private line gateway is detected based on the message detection multiple information to obtain the execution message sent by the second cloud private line gateway. The execution message is continuously sent by the second cloud private line gateway based on the number of times configured by the message detection multiple information.

[0025] Optionally, in some possible implementations of this application, the network scheduling method based on cloud private lines is applied to a blockchain device, where the blockchain device is a node in the blockchain.

[0026] A second aspect of this application provides a network scheduling device based on a cloud private line, comprising:

[0027] The acquisition unit is configured to configure the access control list in response to a scheduling request in order to acquire the session message corresponding to the leased line to be migrated. The scheduling request is used to instruct the leased line to be migrated from the first availability zone to the second availability zone.

[0028] The sending unit is used to copy the session message and simultaneously send the session message to the first cloud private line gateway in the first availability zone and the second cloud private line gateway in the second availability zone. The first cloud private line gateway and the second cloud private line gateway are configured based on the gateway controller.

[0029] The scheduling unit is used to trigger the gateway controller to send the configuration information corresponding to the leased line to be migrated in the first cloud leased line gateway to the second cloud leased line gateway, so that the second cloud leased line gateway creates a target session in the execution state according to the configuration information and the session message, and the target session is used to execute the service corresponding to the leased line to be migrated.

[0030] Optionally, in some possible implementations of this application, the scheduling unit is specifically used to trigger the gateway controller to send the configuration information corresponding to the leased line to be migrated in the first cloud leased line gateway to the second cloud leased line gateway, so that the second cloud leased line gateway can determine the address information, transmit / receive parameter information and channel information corresponding to the leased line to be migrated in the configuration information, as well as the receiver data information and sender data information indicated in the session message;

[0031] The scheduling unit is specifically used to determine that the second cloud private line gateway creates the target session in the execution state based on the address information, the transmit and receive parameter information, the channel information, the receiver data information, and the sender data information.

[0032] Optionally, in some possible implementations of this application, the scheduling unit is specifically used to send the routing information corresponding to the leased line to be migrated to the second cloud leased line gateway through the user edge router in the second availability zone;

[0033] The scheduling unit is specifically used to send a deletion command to the first cloud private line gateway through the gateway controller, so that the first cloud private line gateway deletes the routing information corresponding to the private line to be migrated.

[0034] The scheduling unit is specifically used to delete the access control list configured in the access switch and adjust the sending target of the session message to the second cloud private line gateway.

[0035] Optionally, in some possible implementations of this application, the scheduling unit is specifically used to send a deletion command to the first cloud private line gateway through the gateway controller, so that the first cloud private line gateway intercepts the stop message sent to the user edge router, and the first cloud private line gateway deletes the routing information corresponding to the private line to be migrated in response to the interception of the stop message.

[0036] Optionally, in some possible implementations of this application, the scheduling unit is specifically used to obtain the execution message sent by the second cloud private line gateway, the execution message containing the first negotiation message configured by the second cloud private line gateway;

[0037] The scheduling unit is specifically used to send a second negotiation message back to the second cloud private line gateway based on the first negotiation message, and the correspondence between the first negotiation message and the second negotiation message is obtained based on the target session configuration.

[0038] Optionally, in some possible implementations of this application, the scheduling unit is specifically used to determine the packet detection multiple information corresponding to the target session;

[0039] The scheduling unit is specifically used to detect the information sent by the second cloud private line gateway based on the message detection multiple information, so as to obtain the execution message sent by the second cloud private line gateway. The execution message is continuously sent by the second cloud private line gateway based on the number of times configured by the message detection multiple information.

[0040] A third aspect of this application provides a computer device, comprising: a memory, a processor, and a bus system; the memory is used to store program code; the processor is used to execute the network scheduling method based on cloud private lines as described in the first aspect or any one of the first aspects according to the instructions in the program code.

[0041] The fourth aspect of this application provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the network scheduling method based on cloud private lines as described in the first aspect or any one of the first aspects.

[0042] According to one aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the cloud-based dedicated line network scheduling method provided in the first aspect or various optional implementations thereof.

[0043] As can be seen from the above technical solutions, the embodiments of this application have the following advantages:

[0044] By configuring the access control list in response to a scheduling request, the session packets corresponding to the leased line to be migrated are obtained. This scheduling request instructs the leased line to be migrated from the first availability zone to the second availability zone. The session packets are then replicated and simultaneously sent to the first cloud leased line gateway in the first availability zone and the second cloud leased line gateway in the second availability zone. These first and second cloud leased line gateways are configured based on a gateway controller. This triggers the gateway controller to send the configuration information corresponding to the leased line to be migrated from the first cloud leased line gateway to the second cloud leased line gateway. The second cloud leased line gateway then creates a target session in an execution state based on the configuration information and the session packets. This target session is used to execute the service corresponding to the leased line to be migrated. This achieves a lossless network scheduling process for cloud leased lines. Because session packets are replicated during scheduling and the session is configured through the gateway controller, the data involved in the session is protected, improving data integrity during cloud leased line network scheduling. Attached Figure Description

[0045] To more clearly illustrate the technical solutions in the embodiments of 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 only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0046] Figure 1 This is a network architecture diagram for a cloud-based dedicated line network scheduling system.

[0047] Figure 2 A flowchart illustrating a network scheduling process based on a cloud private line, provided for embodiments of this application;

[0048] Figure 3 A flowchart illustrating a network scheduling method based on a cloud private line, provided in this application embodiment;

[0049] Figure 4 A schematic diagram illustrating a network scheduling method based on a cloud private line, provided as an embodiment of this application;

[0050] Figure 5 A schematic diagram illustrating another network scheduling method based on cloud private lines provided in this application embodiment;

[0051] Figure 6 A schematic diagram illustrating another network scheduling method based on cloud private lines provided in this application embodiment;

[0052] Figure 7 A schematic diagram illustrating another network scheduling method based on cloud private lines provided in this application embodiment;

[0053] Figure 8 A schematic diagram illustrating another network scheduling method based on cloud private lines provided in this application embodiment;

[0054] Figure 9 A schematic diagram illustrating another network scheduling method based on cloud private lines provided in this application embodiment;

[0055] Figure 10 A schematic diagram illustrating another network scheduling method based on cloud private lines provided in this application embodiment;

[0056] Figure 11 A schematic diagram illustrating another network scheduling method based on cloud private lines provided in this application embodiment;

[0057] Figure 12 A schematic diagram of the structure of a network scheduling device based on a cloud private line provided in this application embodiment;

[0058] Figure 13 This application provides a schematic diagram of the structure of a server according to an embodiment of the present application.

[0059] Figure 14A A data sharing system provided in this application embodiment;

[0060] Figure 14B This application provides an embodiment of a blockchain block composition;

[0061] Figure 14C This application provides input information for a blockchain node in an embodiment. Detailed Implementation

[0062] This application provides a network scheduling method and related apparatus based on cloud private lines. It can be applied to systems or programs in terminal devices that include cloud private line-based network scheduling functionality. By configuring an access control list in response to a scheduling request, the method obtains the session packets corresponding to the private line to be migrated. The scheduling request instructs the private line to be migrated from a first availability zone to a second availability zone. The session packets are then copied and simultaneously sent to a first cloud private line gateway in the first availability zone and a second cloud private line gateway in the second availability zone. These first and second cloud private line gateways are configured based on a gateway controller. This triggers the gateway controller to send the configuration information corresponding to the private line to be migrated from the first cloud private line gateway to the second cloud private line gateway. The second cloud private line gateway then creates a target session in an execution state based on the configuration information and the session packets. This target session is used to execute the service corresponding to the private line to be migrated. This achieves a lossless network scheduling process for cloud private lines. Because session packets are copied during scheduling and the session is configured through the gateway controller, the data involved in the session is protected, improving data integrity during cloud private line network scheduling.

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

[0064] First, some terms that may appear in the embodiments of this application will be explained.

[0065] Cloud Dedicated Line (Direct Connect): Used to build a high-speed, low-latency, stable and secure dedicated connection channel between the user's local data center and cloud servers.

[0066] Access Control Lists (ACLs) are lists of instructions applied to router interfaces. These lists tell the router which data packets can be accepted and which should be rejected.

[0067] Bidirectional Forwarding Detection (BFD): Used to quickly detect communication failures between systems and notify upper-layer applications when a failure occurs.

[0068] Furthermore, the abbreviations that may appear in the embodiments of this application are explained as shown in Table 1.

[0069] Table 1. Abbreviation Comparison Table

[0070] Abbreviations Full name explain AP Access Point Access point AZ Available Zone Available area CER Customer Edge Router User Edge Router CES Cloud Edge Switch Access Switch AGG Aggregate Switch Aggregator Switch EGW Enterprise Gateway Cloud dedicated line gateway EGWC Enterprise Gateway Controller Cloud dedicated line gateway controller BFD Bidirectional Forwarding Detection Two-way forwarding detection

[0071] It should be understood that the cloud-based network scheduling method provided in this application can be applied to systems or programs in terminal devices that include cloud-based network scheduling functionality, such as network management. Specifically, the cloud-based network scheduling system can run in environments such as... Figure 1 In the network architecture shown, such as Figure 1 The diagram shown is a network architecture diagram of a cloud-based network scheduling system. As can be seen, this system can provide network scheduling services to multiple information sources via cloud-based dedicated lines. Specifically, it provides corresponding data services to terminals through access point scheduling within the cloud server. This can be understood as... Figure 1 The document illustrates various terminal devices, which can be computer devices. In real-world scenarios, more or fewer types of terminal devices may participate in the network scheduling process based on cloud private lines. The specific number and types depend on the actual scenario and are not limited here. Figure 1 The image shows one server, but in real-world scenarios, multiple servers can be involved, with the specific number depending on the actual situation.

[0072] In this embodiment, the server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The terminal can be a smartphone, tablet, laptop, desktop computer, smart speaker, smartwatch, etc., but is not limited to these. The terminal and server can be directly or indirectly connected via wired or wireless communication, and the terminal and server can be connected to form a blockchain network; this application does not impose any restrictions.

[0073] It is understood that the aforementioned cloud-based dedicated line network scheduling system can run on personal mobile terminals, such as as a network management application, or on servers, or on third-party devices to provide cloud-based dedicated line network scheduling in order to obtain the cloud-based dedicated line network scheduling processing results of information sources. Specifically, the cloud-based dedicated line network scheduling system can run as a program on the aforementioned devices, or as a system component of the aforementioned devices, or as a cloud service program. The specific operating mode depends on the actual scenario and is not limited here.

[0074] With the rapid development of internet technology, people have increasingly higher requirements for network quality. Cloud private lines are a high-speed, low-latency, stable and secure dedicated connection channel between a user's local data center and a cloud server. They are a type of static private line. In some cases, it is necessary to migrate a static private line and its associated bidirectional connection from one availability zone to another to improve network quality.

[0075] Generally, you can first close the static channel with the customer and disable BFD on the existing availability zone, and then open the static channel and start the BFD session to renegotiate on the target availability zone. Once the BFD status is negotiated up, the static channel can be used.

[0076] However, data is generated during the channel closure process, and this data may be lost, affecting the integrity of data during network scheduling.

[0077] To address the aforementioned issues, this application proposes a network scheduling method based on cloud private lines, which is applied to... Figure 2 In the network scheduling process framework based on cloud private lines shown, as follows: Figure 2 The diagram shown is a flowchart of a network scheduling process based on a cloud private line provided in an embodiment of this application. The user makes a data request to the cloud server through interactive operation with the terminal. The cloud server determines the cluster that provides data services by performing private line scheduling of the cloud private line, that is, it determines the availability zone, and then migrates the requested session to the availability zone to provide the corresponding data service.

[0078] This embodiment describes the network scheduling process between the user's IDC and the cloud dedicated line gateway in a cloud dedicated line scenario. It involves actively replicating the BFD session across regions and having the controller actively synchronize the BFD configuration to the new cloud dedicated line gateway cluster. The new cluster then actively resumes the session through the BFD configuration and the received replicating messages, ensuring that all session information is completely consistent with the old cluster. This method achieves seamless migration of the overlay BFD session between the old and new clusters, eliminating the need to prematurely shut down the BFD, which would cause users to perceive the BFD session stopping and trigger alarms, and prevent traffic from switching to backup paths. This significantly improves the reliability of cloud dedicated line BFD sessions.

[0079] It is understood that the method provided in this application can be a program written as processing logic in a hardware system, or it can be a cloud-based network scheduling device that implements the above processing logic in an integrated or external manner. As one implementation, the cloud-based network scheduling device configures an access control list in response to a scheduling request to obtain the session message corresponding to the leased line to be migrated. This scheduling request instructs the leased line to be migrated from a first availability zone to a second availability zone. The session message is then copied and simultaneously sent to a first cloud-based gateway in the first availability zone and a second cloud-based gateway in the second availability zone. The first and second cloud-based gateways are configured based on a gateway controller. This triggers the gateway controller to send the configuration information corresponding to the leased line to be migrated from the first cloud-based gateway to the second cloud-based gateway, enabling the second cloud-based gateway to create a target session in an execution state based on the configuration information and the session message. This target session is used to execute the service corresponding to the leased line to be migrated. This enables lossless network scheduling of cloud private lines. Because session packets are copied during scheduling and sessions are configured through the gateway controller, data involved in the session is protected, thus improving the integrity of data during cloud private line network scheduling.

[0080] Based on the above process architecture, the network scheduling method based on cloud private lines in this application will be described below. Please refer to [link / reference]. Figure 3 , Figure 3 The flowchart illustrates a network scheduling method based on a cloud private line, provided in this application embodiment. This scheduling method can be executed by the access point device corresponding to a server or terminal. This application embodiment includes at least the following steps:

[0081] 301. In response to the scheduling request, configure the access control list to obtain the session messages corresponding to the leased line to be migrated.

[0082] In this embodiment, the scheduling request is used to instruct the migration of the leased line to be migrated from the first availability zone to the second availability zone; specifically, as shown in the example... Figure 4As shown, Figure 4 This is a schematic diagram of a network scheduling method based on a cloud private line provided in an embodiment of this application. The scheduling request is to migrate the private line to be migrated corresponding to the second access point from the first availability zone to the second availability zone, so that the user edge router in the second access point can be connected to the second cloud private line gateway. This embodiment uses the second access point as the execution subject for illustration, that is, the subject that needs to be scheduled. The specific device form depends on the actual scenario.

[0083] In one possible scenario, the leased line to be migrated is a static leased line. The specific leased line mode depends on the actual scenario. Here, we take a static leased line as an example. Since establishing a static leased line between the user's IDC and the cloud leased line gateway and enabling BFD requires the line to fall within the nearest availability zone according to the proximity principle, availability zone migration is necessary. Figure 5 As shown, Figure 5 This is a schematic diagram of another network scheduling method based on cloud private lines provided in the embodiments of this application. For the connection pair 1.1.1.1 / 29 and 1.1.1.2 / 29, access point AP1 accesses the nearest availability zone AZ1. However, for the connection pair 1.1.2.1 / 29 and 1.1.2.2 / 29, which is at access point AP2, the cloud private line gateway in the nearest availability zone AZ2 may not have the necessary resources. Therefore, it can only access AZ1 across campuses. However, this cross-AZ deployment will cause significant latency, and reliability will be easily affected by factors such as links between DRs.

[0084] When migration is required, such as Figure 6 As shown, Figure 6 This is a schematic diagram of another network scheduling method based on cloud private lines provided in the embodiments of this application. The diagram shows that after the resources of the cloud private line gateway in the nearest availability zone AZ2 of access point AP2 are ready, according to the affinity principle, the connection pair 1.1.2.1 / 29 and 1.1.2.2 / 29 needs to be migrated to the nearest availability zone AZ2. However, the current migration process is to first close the static channel with the customer 1.1.2.1 on availability zone AZ1 and close BFD, and then open the static channel on availability zone AZ2 and start BFD session renegotiation. The static channel can only be used after the BFD status negotiation is up. During the migration period, the static channel is unavailable. That is to say, this is a lossy migration process, and the user edge router CER can clearly detect the alarm of BFD session down. It can only be restored after the BFD session is brought up again after the migration is completed.

[0085] This embodiment achieves seamless migration of Overlay BFD sessions between the old and new dedicated line gateway clusters by actively replicating packets and the controller actively synchronizing BFD configurations to the new cloud dedicated line gateway cluster. The new cluster actively restores the up session through the BFD configuration and the received replicated packets, ensuring that all session information is completely consistent with the old cluster. This eliminates the need to pre-download BFD, thus avoiding user-perceived BFD session downtime alarms and traffic switching to backup paths, thereby improving the high reliability of cloud dedicated line BFD sessions.

[0086] 302. Replicate the session message and simultaneously send the session message to the first cloud private line gateway in the first availability zone and the second cloud private line gateway in the second availability zone.

[0087] In this embodiment, the first and second cloud private line gateways are configured based on a gateway controller; this gateway controller is the cloud private line gateway controller (EGWC). Specifically, the process of acquiring and copying BFD session packets is as follows: Figure 7 As shown, Figure 7 This diagram illustrates another scenario of a cloud-based network scheduling method provided in this application. The diagram shows that, firstly, the CES access switch at access point AP2 is configured with an ACL (Access Control List) to match the BFD packets to be migrated, specifically the BFD packets for the address pair 1.1.2.1 / 1.1.2.2. The BFD packets sent from the CER user edge router to the EGW cloud-based gateway are simultaneously sent to the EGW cloud-based gateways in both availability zones AZ1 and AZ2. Thus, the BFD session remains in an up state between access point AP2 and availability zone AZ1, and an additional up packet is sent to the EGW cloud-based gateway in availability zone AZ2.

[0088] It is understandable that configuring ACLs through access switches can improve the accuracy of data acquisition during cloud private line communication. In other words, access switches can ensure that the matched data has not been transmitted through the internal transmission of the access point, thus ensuring the validity of the data.

[0089] 303. Trigger the gateway controller to send the configuration information corresponding to the leased line to be migrated in the first cloud leased line gateway to the second cloud leased line gateway, so that the second cloud leased line gateway can create the target session in the execution state according to the configuration information and session message.

[0090] In this embodiment, the target session is used to execute the service corresponding to the leased line to be migrated. This embodiment takes the BFD session as the target session as an example for illustration. In actual scenarios, it can be the session type corresponding to other session mechanisms in the cloud leased line, which is not limited here.

[0091] Specifically, for creating a target session in the up state, the user corresponding to the second access point is unaware of the handover process, achieving a smooth migration. The following explanation uses specific scenarios as examples. Figure 8 As shown, Figure 8 This is a schematic diagram illustrating another scenario of a network scheduling method based on cloud private lines provided in this application embodiment. The diagram shows the EGWC cloud private line gateway controller as the management device for all EGW cloud private line gateways. It contains the configuration information of all private line channels. The EGWC cloud private line gateway can send the BFD configuration information of the private line to be migrated to the EGW cloud private line gateway in the destination availability zone AZ2. At the same time, it is necessary to ensure that the BFD configuration information sent to the EGW cloud private line gateway in availability zone AZ2 is completely consistent with the original AZ1, including the source address, destination address information, transmission time interval, reception time detection, detection multiple, and the private line channel information of the BFD session.

[0092] In one possible scenario, the creation of the target session involves the second cloud leased line gateway parsing configuration information and session messages. First, the gateway controller is triggered to send the configuration information corresponding to the leased line to be migrated from the first cloud leased line gateway to the second cloud leased line gateway. This allows the second cloud leased line gateway to determine the address information (e.g., BFD session source and destination address), send / receive parameters (e.g., send time interval, receive time detection, detection multiple), and channel information (e.g., the leased line channel information), as well as the receiver and sender data information indicated in the session message. Then, the second cloud leased line gateway creates the target session in the execution state based on the address information, send / receive parameters, channel information, receiver data information, and sender data information. Specifically, in... Figure 9 In the scene shown, Figure 9This is a schematic diagram illustrating another network scheduling method based on cloud private lines provided in this application embodiment. The EGW cloud private line gateway (second cloud private line gateway) in the destination availability zone AZ2 (second availability zone) performs smooth migration of BFD sessions based on two pieces of data: first, the BFD session source address, destination address information, transmission time interval, reception time detection, detection multiple, and the private line channel information issued by the EGWC cloud private line gateway controller; second, the BFD session up message copied from the AP2 access point CES switch, from which the BFD session's my disc and your disc information, as well as the transmission time interval, reception time detection, detection multiple, and other information configured by the customer edge router (receiver data information and sender data information) are obtained. The BFD EGW cloud leased line gateway needs to perform a special smoothing process for this session. It directly creates a BFD session in the up state, and ensures that the source address, destination address, sending time interval, receiving time detection, detection multiplier, leased line channel information, my disc and your disc information are the same as the original session in availability zone AZ1 (the session corresponding to the leased line to be migrated). Then, it directly sends up messages, and the BFD up messages sent are also the same as those in the original session.

[0093] Optionally, after the EGW cloud leased line gateway in the destination availability zone AZ2 completes the BFD session migration, the session in the first availability zone can also be deleted. That is, firstly, the routing information corresponding to the leased line to be migrated is sent to the second cloud leased line gateway through the user edge router in the second availability zone; then, the gateway controller sends a deletion command to the first cloud leased line gateway so that the first cloud leased line gateway deletes the routing information corresponding to the leased line to be migrated; then, the access control list configured in the access switch is deleted, and the sending target of the session packets is adjusted to the second cloud leased line gateway.

[0094] Furthermore, to prevent the BFD session from stopping due to the customer edge router of the second access point receiving a down / ADMINdown message (stop message), interception is required. This is achieved by sending a deletion command to the first cloud leased line gateway via the gateway controller. The first cloud leased line gateway then intercepts the stop message sent to the user edge router, and in response to the interception, deletes the routing information corresponding to the leased line to be migrated.

[0095] In one possible scenario, such as Figure 10 As shown, Figure 10This is a schematic diagram of another network scheduling method based on cloud private lines provided in the embodiments of this application. The diagram shows that after the BFD session migration is completed at the EGW cloud private line gateway (second cloud private line gateway) in the destination availability zone AZ2 (second availability zone), the static route of the static private line can be issued at the EGW cloud private line gateway in availability zone AZ2, and the static route and BFD session of the static private line can be deleted on availability zone AZ1.

[0096] It should be noted that deleting a BFD session on Availability Zone AZ1 (the first Availability Zone) also requires a special procedure. Down / ADMINdown messages (stop messages) must not be sent out to prevent the customer edge router from receiving down / ADMINdown messages and causing the BFD session to go down. Finally, delete the ACL added in step 301 on the CES access switch at access point AP2, cancel BFD message replication, and only send messages to the destination Availability Zone AZ2. This completes the smooth handover of the static leased line BFD session. During the migration process, the BFD session remains up, and the customer will not be aware of the migration process.

[0097] Optionally, in step 303, after the EGW cloud private line gateway in the second availability zone AZ2 completes the BFD session migration, how can we confirm that the CER customer edge router has received and correctly processed the BFD up message sent by the new cloud private line gateway cluster in availability zone AZ2? Because at this time, the BFD up message of the old cloud private line gateway cluster in availability zone AZ1 is still being sent. Even if the CER customer edge router does not receive the BFD up message sent by the new cluster, the BFD session can still remain up. However, after the BFD of the old cluster is deleted, if the CER customer edge router does not receive the BFD up message sent by the new cluster, the BFD session on the CER customer edge router side will experience a session timeout down, causing the smooth migration of BFD to fail.

[0098] To address the aforementioned issues, a state determination mechanism can be implemented between the user edge router and the second cloud leased line gateway in the second access point. Specifically, before the gateway controller sends a deletion command to the first cloud leased line gateway, causing the first cloud leased line gateway to delete the routing information corresponding to the leased line to be migrated, it can obtain an execution message sent by the second cloud leased line gateway. This execution message contains a first negotiation message configured by the second cloud leased line gateway. Then, based on the first negotiation message, a second negotiation message is fed back to the second cloud leased line gateway. The correspondence between the first and second negotiation messages is based on the target session configuration. In other words, the second cloud leased line gateway only determines that the user edge router has responded upon receiving the second negotiation message, thus improving the accuracy of the response process.

[0099] In addition, since user edge routers generally have detection intervals set, in order to prevent missed reception of negotiation messages, the second cloud leased line gateway can continuously send multiple execution messages based on the message detection multiple information of the user edge router. That is, firstly, the message detection multiple information corresponding to the target session is determined; then, the information sent by the second cloud leased line gateway is detected based on the message detection multiple information to obtain the execution message sent by the second cloud leased line gateway. The second cloud leased line gateway continuously sends the execution message based on the number of times configured by the message detection multiple information, thereby ensuring the effectiveness of the confirmation process.

[0100] In one possible scenario, such as Figure 11 As shown, Figure 11 This is a schematic diagram illustrating another scenario of a cloud-based network scheduling method provided in this application embodiment. The diagram shows that after the EGW cloud-based gateway in the destination availability zone AZ2 completes the BFD session creation, it actively sends a negotiation message (first negotiation message) setting the P bit in the sent BFD up message, continuously sending 3-5 messages (determined according to the detection multiple configured in the BFD session). According to the relevant BFD RFC5880, if the CER customer edge router receives the P bit negotiation message in the BFD, it will reply with an F bit negotiation message (second negotiation message). If the new cluster (second availability zone) receives the F bit negotiation message, it means that the CER customer edge router can receive and process the BFD message of the new cluster correctly, and notifies the EGWC cloud-based gateway controller that the BFD session migration is successful, and the BFD session deletion of the old cluster (first availability zone) can be performed.

[0101] As described in the above embodiments, by configuring the access control list in response to a scheduling request to obtain the session packets corresponding to the leased line to be migrated, the scheduling request is used to instruct the leased line to be migrated from the first availability zone to the second availability zone. Then, the session packets are copied and sent simultaneously to the first cloud leased line gateway in the first availability zone and the second cloud leased line gateway in the second availability zone. The first and second cloud leased line gateways are configured based on the gateway controller. This triggers the gateway controller to send the configuration information corresponding to the leased line to be migrated in the first cloud leased line gateway to the second cloud leased line gateway, so that the second cloud leased line gateway creates a target session in an execution state according to the configuration information and the session packets. This target session is used to execute the service corresponding to the leased line to be migrated. This achieves a lossless network scheduling process for cloud leased lines. Because the session packets are copied during the scheduling process and the session is configured through the gateway controller, the data involved in the session is protected, improving the data integrity during the cloud leased line network scheduling process.

[0102] To better implement the above-described solutions of the embodiments of this application, related apparatus for implementing the above solutions is also provided below. Please refer to... Figure 12 , Figure 12 This application provides a schematic diagram of the structure of a cloud-based network scheduling device 1200, which includes:

[0103] The acquisition unit 1201 is configured to configure the access control list in response to a scheduling request in order to acquire the session message corresponding to the leased line to be migrated. The scheduling request is used to instruct the leased line to be migrated from the first availability zone to the second availability zone.

[0104] The sending unit 1202 is used to copy the session message and simultaneously send the session message to the first cloud private line gateway in the first availability zone and the second cloud private line gateway in the second availability zone. The first cloud private line gateway and the second cloud private line gateway are configured based on the gateway controller.

[0105] The scheduling unit 1203 is used to trigger the gateway controller to send the configuration information corresponding to the leased line to be migrated in the first cloud leased line gateway to the second cloud leased line gateway, so that the second cloud leased line gateway creates a target session in the execution state according to the configuration information and the session message, and the target session is used to execute the service corresponding to the leased line to be migrated.

[0106] Optionally, in some possible implementations of this application, the scheduling unit 1203 is specifically used to trigger the gateway controller to send the configuration information corresponding to the leased line to be migrated in the first cloud leased line gateway to the second cloud leased line gateway, so that the second cloud leased line gateway can determine the address information, transmit and receive parameter information and channel information corresponding to the leased line to be migrated in the configuration information, as well as the receiver data information and sender data information indicated in the session message;

[0107] The scheduling unit 1203 is specifically used to determine that the second cloud private line gateway creates the target session in the execution state based on the address information, the transmit and receive parameter information, the channel information, the receiver data information and the sender data information.

[0108] Optionally, in some possible implementations of this application, the scheduling unit 1203 is specifically used to send the routing information corresponding to the leased line to be migrated to the second cloud leased line gateway through the user edge router in the second availability zone;

[0109] The scheduling unit 1203 is specifically used to send a deletion command to the first cloud private line gateway through the gateway controller, so that the first cloud private line gateway deletes the routing information corresponding to the private line to be migrated.

[0110] The scheduling unit 1203 is specifically used to delete the access control list configured in the access switch and adjust the sending target of the session message to the second cloud private line gateway.

[0111] Optionally, in some possible implementations of this application, the scheduling unit 1203 is specifically used to send a deletion command to the first cloud private line gateway through the gateway controller, so that the first cloud private line gateway intercepts the stop message sent to the user edge router, and the first cloud private line gateway deletes the routing information corresponding to the private line to be migrated in response to the interception of the stop message.

[0112] Optionally, in some possible implementations of this application, the scheduling unit 1203 is specifically used to obtain the execution message sent by the second cloud private line gateway, the execution message containing the first negotiation message configured by the second cloud private line gateway;

[0113] The scheduling unit 1203 is specifically used to send a second negotiation message back to the second cloud private line gateway based on the first negotiation message, wherein the correspondence between the first negotiation message and the second negotiation message is obtained based on the target session configuration.

[0114] Optionally, in some possible implementations of this application, the scheduling unit 1203 is specifically used to determine the packet detection multiple information corresponding to the target session;

[0115] The scheduling unit 1203 is specifically used to detect the information sent by the second cloud private line gateway based on the message detection multiple information in order to obtain the execution message sent by the second cloud private line gateway. The execution message is continuously sent by the second cloud private line gateway based on the number of times configured by the message detection multiple information.

[0116] By configuring the access control list in response to a scheduling request, the session packets corresponding to the leased line to be migrated are obtained. This scheduling request instructs the leased line to be migrated from the first availability zone to the second availability zone. The session packets are then replicated and simultaneously sent to the first cloud leased line gateway in the first availability zone and the second cloud leased line gateway in the second availability zone. These first and second cloud leased line gateways are configured based on a gateway controller. This triggers the gateway controller to send the configuration information corresponding to the leased line to be migrated from the first cloud leased line gateway to the second cloud leased line gateway. The second cloud leased line gateway then creates a target session in an execution state based on the configuration information and the session packets. This target session is used to execute the service corresponding to the leased line to be migrated. This achieves a lossless network scheduling process for cloud leased lines. Because session packets are replicated during scheduling and the session is configured through the gateway controller, the data involved in the session is protected, improving data integrity during cloud leased line network scheduling.

[0117] This application also provides a server; please refer to [link / reference]. Figure 13 , Figure 13 This is a schematic diagram of a server structure provided in an embodiment of this application. The server 1300 can vary significantly due to different configurations or performance. It may include one or more central processing units (CPUs) 1322 (e.g., one or more processors) and memory 1332, and one or more storage media 1330 (e.g., one or more mass storage devices) for storing application programs 1342 or data 1344. The memory 1332 and storage media 1330 can be temporary or persistent storage. The program stored in the storage media 1330 may include one or more modules (not shown in the diagram), each module including a series of instruction operations on the server. Furthermore, the CPU 1322 may be configured to communicate with the storage media 1330 and execute the series of instruction operations in the storage media 1330 on the server 1300.

[0118] Server 1300 may also include one or more power supplies 1326, one or more wired or wireless network interfaces 1350, one or more input / output interfaces 1358, and / or one or more operating systems 1341, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, etc.

[0119] The steps performed by the management device in the above embodiments can be based on this Figure 13 The server structure shown.

[0120] This application also provides a computer-readable storage medium storing network scheduling instructions based on cloud private lines. When these instructions are executed on a computer, they cause the computer to perform the aforementioned actions. Figures 3 to 11 The steps performed by the network scheduling device based on cloud private lines in the method described in the illustrated embodiment.

[0121] This application also provides a computer program product that includes network scheduling instructions based on cloud private lines. When run on a computer, it causes the computer to execute the aforementioned commands. Figures 3 to 11 The steps performed by the network scheduling device based on cloud private lines in the method described in the illustrated embodiment.

[0122] This application also provides a cloud-based dedicated line network scheduling system, which may include... Figure 12 The network scheduling device based on cloud private lines in the described embodiments, or Figure 13 The server described.

[0123] In one possible scenario, the network resource management method of this application is applied to a blockchain device, i.e., the authoritative DNS, LDNS, or terminal is a blockchain device, and this blockchain device is a node in the blockchain. This is described below with reference to the accompanying drawings; see also... Figure 14A The data sharing system 1400 shown refers to a system for data sharing between nodes. This system may include multiple nodes 1401, which can refer to various clients within the system. Each node 1401, during normal operation, receives input information and maintains the shared data within the system based on this information. To ensure interoperability within the system, information connections exist between nodes, allowing for information transmission. For example, when any node in the system receives input information, other nodes retrieve this information according to a consensus algorithm and store it as part of the shared data, ensuring consistency across all nodes.

[0124] Each node in the data sharing system has a corresponding node identifier, and each node can also store the node identifiers of other nodes in the data sharing system. This allows for the subsequent broadcasting of generated blocks to other nodes in the data sharing system based on their node identifiers. Each node can maintain a node identifier list as shown in the table below, storing the node name and node identifier in this list. The node identifier can be an IP (Internet Protocol) address or any other information that can be used to identify the node. Table 2 only uses IP addresses as an example.

[0125] Table 2. Correspondence between node names and node identifiers

[0126] Node Name Node identifier Node 1 117.114.151.174 Node 2 117.116.189.145 … … Node N 119.123.789.258

[0127] Each node in the data-sharing system stores the same blockchain. A blockchain consists of multiple blocks; see [link to blockchain documentation]. Figure 14B A blockchain consists of multiple blocks. The genesis block includes a block header and a block body. The block header stores input information feature values, version number, timestamp, and difficulty value, while the block body stores the input information. The next block after the genesis block takes the genesis block as its parent block. The next block also includes a block header and a block body. The block header stores the input information feature values ​​of the current block, the block header feature values ​​of the parent block, version number, timestamp, and difficulty value, and so on. This ensures that the block data stored in each block is related to the block data stored in the parent block, guaranteeing the security of the input information in the blocks.

[0128] When generating the individual blocks in the blockchain, see Figure 14C When a node in the blockchain receives input information, it verifies the input information. After verification, it stores the input information in a memory pool and updates its hash tree used to record the input information. Then, it updates the timestamp to the time the input information was received and tries different random numbers multiple times to calculate the feature value, ensuring that the calculated feature value satisfies the following formula:

[0129] SHA256(SHA256(version+prev_hash+merkle_root+ntime+nbits+x))<TARGET

[0130] Wherein, SHA256 is the feature value algorithm used to calculate the feature value; version (version number) is the version information of the relevant block protocol in the blockchain; prev_hash is the block header feature value of the parent block of the current block; merkle_root is the feature value of the input information; ntime is the update time of the update timestamp; nbits is the current difficulty, which is a fixed value for a period of time and is determined again after exceeding the fixed time period; x is a random number; TARGET is the feature value threshold, which can be determined based on nbits.

[0131] Therefore, when a random number satisfying the above formula is calculated, the information can be stored accordingly, generating a block header and a block body to obtain the current block. Subsequently, the node where the blockchain resides sends the newly generated block to other nodes in its data sharing system based on the node identifiers of other nodes in the data sharing system. The other nodes then verify the newly generated block and add it to their stored blockchain after verification.

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

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

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

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

[0136] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a cloud-based network scheduling device, or a 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.

[0137] The above-described 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 network scheduling method based on cloud private lines, characterized in that, include: In response to a scheduling request, an access control list is configured to obtain the session message corresponding to the leased line to be migrated. The scheduling request is used to instruct the leased line to be migrated from the first availability zone to the second availability zone. The session message is copied and simultaneously sent to the first cloud private line gateway in the first availability zone and the second cloud private line gateway in the second availability zone. The first cloud private line gateway and the second cloud private line gateway are configured based on the gateway controller. The gateway controller is triggered to send the configuration information corresponding to the leased line to be migrated in the first cloud leased line gateway to the second cloud leased line gateway, so that the second cloud leased line gateway creates a target session in the execution state according to the configuration information and the session message. The target session is used to execute the service corresponding to the leased line to be migrated.

2. The method according to claim 1, characterized in that, The step of triggering the gateway controller to send the configuration information corresponding to the leased line to be migrated in the first cloud leased line gateway to the second cloud leased line gateway, so that the second cloud leased line gateway creates a target session in the execution state according to the configuration information and the session message, includes: The gateway controller is triggered to send the configuration information corresponding to the leased line to be migrated in the first cloud leased line gateway to the second cloud leased line gateway, so that the second cloud leased line gateway can determine the address information, transmit and receive parameter information and channel information corresponding to the leased line to be migrated in the configuration information, as well as the receiver data information and sender data information indicated in the session message; The second cloud private line gateway determines that it creates the target session in the execution state based on the address information, the transmit and receive parameter information, the channel information, the receiver data information, and the sender data information.

3. The method according to claim 1, characterized in that, After the method triggers the gateway controller to send the configuration information corresponding to the leased line to be migrated in the first cloud leased line gateway to the second cloud leased line gateway, so that the second cloud leased line gateway creates a target session in the execution state according to the configuration information and the session message, the method further includes: The routing information corresponding to the leased line to be migrated is sent to the second cloud leased line gateway through the user edge router in the second availability zone. The gateway controller sends a deletion command to the first cloud private line gateway, so that the first cloud private line gateway deletes the routing information corresponding to the private line to be migrated. Delete the access control list configured in the access switch and adjust the sending target of the session message to the second cloud private line gateway.

4. The method according to claim 3, characterized in that, The step of sending a deletion command to the first cloud private line gateway through the gateway controller, so that the first cloud private line gateway deletes the routing information corresponding to the private line to be migrated, includes: The gateway controller sends a deletion command to the first cloud private line gateway, so that the first cloud private line gateway intercepts the stop message sent to the user edge router. In response to the interception of the stop message, the first cloud private line gateway deletes the routing information corresponding to the private line to be migrated.

5. The method according to claim 3, characterized in that, Before the method of sending a deletion command to the first cloud private line gateway through the gateway controller, so that the first cloud private line gateway deletes the routing information corresponding to the private line to be migrated, the method further includes: Obtain the execution message sent by the second cloud private line gateway, the execution message containing the first negotiation message configured by the second cloud private line gateway; The second negotiation message is fed back to the second cloud private line gateway based on the first negotiation message, and the correspondence between the first negotiation message and the second negotiation message is obtained based on the target session configuration.

6. The method according to claim 5, characterized in that, The step of obtaining the execution message sent by the second cloud private line gateway includes: Determine the packet detection multiplier information corresponding to the target session; The information sent by the second cloud private line gateway is detected based on the message detection multiple information to obtain the execution message sent by the second cloud private line gateway. The execution message is continuously sent by the second cloud private line gateway based on the number of times configured by the message detection multiple information.

7. The method according to claim 1, characterized in that, The network scheduling method based on cloud private lines is applied to blockchain devices, where the blockchain device is a node in the blockchain.

8. A network scheduling device based on cloud private lines, characterized in that, include: The acquisition unit is configured to configure the access control list in response to a scheduling request in order to acquire the session message corresponding to the leased line to be migrated. The scheduling request is used to instruct the leased line to be migrated from the first availability zone to the second availability zone. The sending unit is used to copy the session message and simultaneously send the session message to the first cloud private line gateway in the first availability zone and the second cloud private line gateway in the second availability zone. The first cloud private line gateway and the second cloud private line gateway are configured based on the gateway controller. The scheduling unit is used to trigger the gateway controller to send the configuration information corresponding to the leased line to be migrated in the first cloud leased line gateway to the second cloud leased line gateway, so that the second cloud leased line gateway creates a target session in the execution state according to the configuration information and the session message, and the target session is used to execute the service corresponding to the leased line to be migrated.

9. A computer device, characterized in that, The computer device includes a processor and memory: The memory is used to store program code; the processor is used to execute the network scheduling method based on cloud private lines according to any one of the instructions in the program code.

10. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instruction is executed by the processor, it implements the steps of the network scheduling method based on cloud private lines as described in any one of claims 1 to 7.

Images