CN113891358A - Load balancing method and device of cloud network and storage medium - Google Patents
Load balancing method and device of cloud network and storage medium Download PDFInfo
- Publication number
- CN113891358A CN113891358A CN202111165320.9A CN202111165320A CN113891358A CN 113891358 A CN113891358 A CN 113891358A CN 202111165320 A CN202111165320 A CN 202111165320A CN 113891358 A CN113891358 A CN 113891358A
- Authority
- CN
- China
- Prior art keywords
- machine node
- base station
- node
- communication
- machine
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/04—Arrangements for maintaining operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/08—Load balancing or load distribution
- H04W28/088—Load balancing or load distribution among core entities
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本申请实施例提供一种云网络的负载均衡方法、设备及存储介质。当云网络中的机器节点异常时，基于容器化应用管理平台的主节点提供的负载均衡能力，可将基站发送至机器节点的通信报文路由至机器节点的备用机器节点中。备用机器节点可共享机器节点与基站之间的会话环境数据，并根据机器节点与基站之间的会话环境数据，接入机器节点与基站之间的通信链路，以与基站进行通信。一方面，可在基站侧无感知的情况下实现主备切换，另一方面，备用机器节点可根据机器节点与基站之间的会话环境数据快速接入机器节点与基站之间通信链路，可迅速恢复通信传输，降低对应用侧的影响。
Embodiments of the present application provide a load balancing method, device and storage medium for a cloud network. When the machine node in the cloud network is abnormal, based on the load balancing capability provided by the master node of the containerized application management platform, the communication message sent by the base station to the machine node can be routed to the standby machine node of the machine node. The standby machine node can share the session environment data between the machine node and the base station, and according to the session environment data between the machine node and the base station, access the communication link between the machine node and the base station to communicate with the base station. On the one hand, the active/standby switchover can be realized without the base station side sensing. On the other hand, the standby machine node can quickly access the communication link between the machine node and the base station according to the session environment data between the machine node and the base station. Quickly resume communication transmission and reduce the impact on the application side.
Description
Technical Field
The present application relates to the field of mobile communications technologies, and in particular, to a load balancing method and device for a cloud network, and a storage medium.
Background
In a mobile network, communication between a base station and the mobile network is typically performed through a specific protocol. In a scenario where servers in a mobile network are in a highly available deployment, each machine node (i.e., primary server node) may be provided with a standby machine node. When the main server node connected with the base station fails, the communication link between the base station and the main node is switched to the communication link between the base station and the standby machine node.
In the prior art, when a communication link is switched between a main node and a standby machine node, a communication connection is generally required to be established between a base station and the standby machine node again based on a specific protocol. The switching mode causes communication interruption, and the user on the original communication link needs to re-attach the network. Therefore, a solution is yet to be proposed.
Disclosure of Invention
Aspects of the present disclosure provide a load balancing method, device, and storage medium for a cloud network, so as to maintain a communication link and avoid interruption of network connection when a master node and a slave node are switched.
The embodiment of the application provides a load balancing method of a cloud network, wherein a main node and a plurality of machine nodes of a containerized application management platform are deployed in the cloud network, and the machine nodes are deployed according to a master-standby mode; aiming at any machine node and a standby machine node corresponding to the machine node, the method comprises the following steps: the standby machine node acquires session environment data of the machine node and a base station; when the machine node is abnormal, receiving a communication message of the base station forwarded by the main node based on a load balancing strategy; and accessing the communication link to which the communication message belongs according to the session environment data so as to respond to the communication message.
Further optionally, before accessing the communication link to which the communication packet belongs according to the session environment data, the method further includes: if the communication link to which the communication message belongs cannot be identified, sending a message containing a termination flag bit to the base station; and intercepting the message containing the termination zone bit so as to enable the base station side to maintain the connection of the communication link.
Further optionally, after accessing the communication link to which the communication packet belongs according to the session environment data, the method further includes: and updating the white list of the interception address according to the communication address of the base station.
Further optionally, the method further comprises: when the communication link to which the communication message belongs cannot be identified, sending an abnormal early warning message to an operation and maintenance terminal; and/or sending a master-slave switching message of the machine node to the operation and maintenance terminal when the communication link to which the communication message belongs is accessed according to the session environment data.
Further optionally, the acquiring, by the standby machine node, session environment data of the machine node and a base station includes: acquiring a data structure in a memory corresponding to the SCTP monitoring socket of the machine node; accessing the communication link to which the communication message belongs according to the session environment data, including: and establishing SCTP association with the base station according to a data structure in a memory corresponding to the SCTP monitoring socket.
Further optionally, the obtaining a data structure in a memory corresponding to the SCTP listening socket in the machine node includes: requesting the machine node to acquire a data structure in a memory corresponding to the SCTP monitoring socket; or requesting a database server in the cloud network to acquire a data structure in a memory corresponding to the SCTP monitoring socket; and uploading a data structure in a memory corresponding to the SCTP monitoring socket to the database server by the machine node.
Further optionally, the core network component of the mobile network deployed in a containerization manner runs on the machine node and the standby machine node.
The application also provides a load balancing method of the cloud network, wherein a plurality of machine nodes of the containerized application management platform are deployed in the cloud network, and the machine nodes are deployed according to a master-standby mode; aiming at any machine node and a standby machine node corresponding to the machine node, the method comprises the following steps: the main node monitors the running state of the machine node, and the machine node is connected with a base station; when the machine node is monitored to be abnormal, the communication message of the base station is routed to a standby machine node of the machine node based on a load balancing strategy, so that the standby machine node receives the communication message of the base station forwarded by the main node, and accesses a communication link to which the communication message belongs according to the session environment data to respond to the communication message.
Further optionally, when it is monitored that the machine node is abnormal, after the communication packet of the base station is routed to a standby machine node of the machine node based on a load balancing policy, the method further includes: analyzing the abnormal reason of the machine node according to the monitored state change of the machine node; and recording the abnormal reason of the machine node so as to optimize the load balancing strategy according to the abnormal reason.
The present application further provides a load balancing system of a cloud network, including: the method comprises the steps that a main node and a plurality of machine nodes of a containerized application management platform are deployed according to a main-standby mode; the main node of the containerized application management platform is used for: monitoring the running state of any machine node; the machine node is connected with a base station; when the machine node is monitored to be abnormal, routing the communication message of the base station to a standby machine node of the machine node based on a load balancing strategy; the standby machine node is to: acquiring session environment data of the machine node and a base station; and receiving the communication message of the base station forwarded by the main node based on the load balancing strategy, and accessing the communication link to which the communication message belongs according to the session environment data so as to respond to the communication message.
An embodiment of the present application further provides a load balancing system of a cloud network, including: the method comprises the steps that a main node and a plurality of machine nodes of a containerized application management platform are deployed according to a main-standby mode; a core network component of a mobile network deployed in a containerization manner runs on any machine node, and the core network component is used for providing a live broadcast traffic processing service; the main node of the containerized application management platform is used for: monitoring the running state of any machine node; the machine node is connected with a base station; when the machine node is monitored to be abnormal, routing a live broadcast flow processing request of the base station to a standby machine node of the machine node based on a load balancing strategy; the standby machine node is to: acquiring session environment data of the machine node and a base station; and receiving the live broadcast traffic processing request of the base station forwarded by the main node, and accessing a communication link to which the live broadcast traffic processing request belongs according to the session environment data so as to process the live broadcast traffic processing request.
Further optionally, when the standby machine node acquires the session environment data of the machine node and the base station, the standby machine node is specifically configured to: acquiring a data structure in a memory corresponding to the SCTP monitoring socket of the machine node; when accessing the communication link to which the communication packet belongs according to the session environment data, the method is specifically configured to: and establishing SCTP association with the base station according to a data structure in a memory corresponding to the SCTP monitoring socket.
An embodiment of the present application further provides a server, including: a memory, a processor, and a communication component; the memory is to store one or more computer instructions; the processor is to execute the one or more computer instructions to: the steps in the methods provided by the embodiments of the present application are performed by a communication component.
Embodiments of the present application further provide a computer-readable storage medium storing a computer program, where the computer program can be executed by a processor to perform the steps in the method provided by the embodiments of the present application.
In the load balancing method for the cloud network provided by the embodiment of the application, when a machine node in the cloud network is abnormal, based on the load balancing capability provided by the main node of the containerized application management platform, a communication message sent to the machine node by the base station can be routed to a standby machine node of the machine node. The standby machine node can share the conversation environment data between the machine node and the base station, and accesses a communication link between the machine node and the base station according to the conversation environment data between the machine node and the base station so as to communicate with the base station. On one hand, the main-standby switching can be realized under the condition that the base station side is not aware, on the other hand, the standby machine node can be quickly accessed into a communication link between the machine node and the base station according to the session environment data between the machine node and the base station, so that the communication transmission can be quickly recovered, and the influence on the application side is reduced.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1 is a schematic architecture diagram of a load balancing system of a cloud network according to an embodiment of the present application;
fig. 2 is a schematic diagram of a core network dual-node hot standby according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a MetalB system-based load balancing according to an exemplary embodiment of the present application;
fig. 4 is a schematic flowchart of a load balancing method of a cloud network according to an embodiment of the present application;
fig. 5 is a schematic flowchart of a load balancing method for a cloud network according to another embodiment of the present application;
fig. 6 is a schematic structural diagram of a server according to an exemplary embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In a mobile network, communication between a base station and the mobile network is typically performed through a specific protocol. In a scenario where servers in a mobile network are in a highly available deployment, each machine node (i.e., primary server node) may be provided with a standby machine node. When the main server node connected with the base station fails, the communication link between the base station and the main node can be switched to the communication link between the base station and the standby machine node.
In the prior art, when a communication link is switched between a main node and a standby machine node, a communication connection is generally required to be established between a base station and the standby machine node again based on a specific protocol. The switching mode causes communication interruption, and the user on the original communication link needs to re-attach the network.
In view of the above technical problems, in some embodiments of the present application, a solution is provided, and the technical solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.
Fig. 1 is a schematic architecture diagram of a load balancing system of a cloud network according to an exemplary embodiment of the present application, and as shown in fig. 1, the load balancing system 100 of the cloud network includes: the main node 10 of the containerized application management platform, multiple machine nodes, and the multiple machine nodes are according to the main/standby mode. Any machine node 11 corresponds to a standby machine node 12.
The containerization application management platform can be realized based on a Kubernetes (container arrangement engine) platform. Kubernets is used to manage containerized applications on multiple hosts (or nodes) in a cloud platform, so that the containerized applications deployed on the hosts run in a desired state. Multiple hosts in a kubernets platform form a kubernets cluster.
The Kubernetes cluster includes a Master Node and a machine Node. The main node runs a main control component of Kubernetes and is used for controlling, scheduling, managing and the like the machine node. One machine node corresponds to one physical machine.
In this embodiment, in a high available deployment scenario, a standby machine node may be set for each machine node. The standby machine node is used for continuously executing interrupted services under the condition that the machine node has inevitable planned or unplanned abnormalities (such as downtime and faults) so as to realize dual-machine equipment. Each server can be implemented based on conventional server equipment, wherein the server equipment mainly comprises a processor, a hard disk, a memory, a system bus and the like, is similar to a general computer architecture, and is not described in detail again.
Wherein, machine node and 11 mainly are used for: and when no abnormity occurs, connecting with the base station and providing data service for the base station. Wherein, the connection between the machine node and the base station can be a long connection, that is: after the connection is established, the connection state can be continuously maintained; there is no need to re-establish a connection at each data transmission before the long connection is terminated.
In load balancing, the master node 10 is mainly configured to: and monitoring the running state of the machine node 11. The operation of monitoring the running state of the machine node 11 may be performed by a monitoring function component disposed on the master node 10. When the machine node 11 is monitored to be abnormal, the communication message of the base station is routed to the standby machine node 12 based on the load balancing strategy. The load balancing policy is a policy for directing an access request of a base station to a machine node or a standby machine node. In the load balancing policy, a trigger condition for forwarding a request between the primary and secondary machines may be customized, where the trigger condition may be a machine node downtime, a machine node failure, a machine node having a certain hardware resource abnormality (for example, the hardware resource occupancy rate reaches a set threshold), or a machine node having a certain software resource abnormality (for example, a software abnormal interruption operation), and the like, and this embodiment is not limited.
Wherein, the standby machine node 12 is mainly used for: acquiring session environment data of a machine node 11 and a base station; the session environment data refers to communication environment related data required for communication interaction between the machine node 11 and the base station, and may include, but is not limited to, a communication address, a serial number of a communication connection, authentication information, and other data. The standby machine node 12 may share the above-described session context data with the machine node 11.
When the standby machine node 12 receives the communication packet of the base station forwarded by the master node 10, the communication link to which the communication packet belongs may be accessed according to the session environment data between the machine node 11 and the base station. After access, the communication link between the base station and the machine node 11 is switched to the communication link between the base station and the machine node 12. In this switching process, the session environment of the correspondent node is not changed for the base station, the long connection can be maintained, and the base station side does not need to perform the operation of establishing a communication connection with the standby machine node 12. After accessing the communication link, the standby machine node 12 may communicate with the base station based on the shared session context data in response to the communication packet sent by the base station.
In some embodiments, for the standby machine node 12, before the machine node 11 does not generate an abnormality, the standby machine node 12 does not establish a communication connection with the base station, and therefore, after the standby machine node 12 receives the communication message of the base station routed by the master node 10, the communication link to which the communication message belongs cannot be identified. Typically, the standby machine node 12 may send a termination communication message to the base station. If the base station receives the termination communication message, the communication connection can be terminated, and the termination information is reported to an Upper Layer Protocol (ULP). When the upper layer protocol senses the interruption of the transmission layer network, the current application is terminated, so that the user senses the interruption of the network.
In this embodiment, in order to implement active/standby switching without sensing by the user, the standby machine node 12 may intercept the termination communication packet after sending the termination communication packet to the base station. Therefore, the base station side cannot sense the main/standby switching of the cloud network side.
When the communication protocols adopted by the cloud network and the base station are different, the termination zone bits in the termination communication message are also different. For example, when SCTP (Stream Control Transmission Protocol) is used for communication Transmission, the termination flag bit may be an ABORT flag bit or a SHUTDOWN flag bit. That is, when the standby machine node 12 does not establish a communication connection with the base station, if a communication packet of the base station is received, a packet including an ABORT flag or a SHUTDOWN flag is sent to the base station based on a communication mechanism set by a communication protocol, and the packet can be intercepted based on a firewall component before the packet is sent. When the base station does not receive the message containing the ABORT flag bit or the SHUTDOWN flag bit, the communication connection does not need to be terminated, and thus the user at the application side cannot sense the interruption caused by the network abnormality. After intercepting the terminating communication packet, the standby machine node 12 may access the communication link to which the communication packet belongs according to the session environment data between the machine node 11 and the base station. After accessing the communication link, the standby machine node 12 may establish a communication connection with the base station, so as to respond to the communication packet sent by the base station.
Based on the above embodiment, the standby machine node 12 can establish connection with the base station and perform communication interaction with the base station instead of the machine node 11, so that the communication requirement of the base station is met.
In this embodiment, when a machine node in the cloud network is abnormal, based on the load balancing capability provided by the master node of the containerized application management platform, a communication packet sent to the machine node by the base station may be routed to a standby machine node of the machine node. The standby machine node can share the conversation environment data between the machine node and the base station, and accesses a communication link between the machine node and the base station according to the conversation environment data between the machine node and the base station so as to communicate with the base station. On one hand, the main-standby switching can be realized under the condition that the base station side is not aware, on the other hand, the standby machine node can be quickly accessed into a communication link between the machine node and the base station according to the session environment data between the machine node and the base station, so that the communication transmission can be quickly recovered, and the influence on the application side is reduced.
In some alternative embodiments, the operation of the standby machine node 12 intercepting the packet containing the termination flag may be implemented based on a gateway or a router connected to the standby machine node 12, or may be implemented by a firewall component (iptables) on the standby machine node 12. The gateway, the router or the firewall component may be configured with a white list of interception addresses, and if the communication address of the correspondent node is in the white list, the terminating communication packet may not be sent to the correspondent node when receiving the communication packet sent by the communication address. If the communication address of the opposite communication terminal is not in the white list, when the communication message sent by the communication address is received, if the communication address cannot be identified, the communication terminal sends a communication termination message to the opposite communication terminal.
Based on this, after the standby machine node 12 accesses the communication link between the machine node 11 and the base station according to the session environment data, the standby machine node 12 establishes a communication connection with the base station, and can perform conventional communication interaction. The communication interaction may include: when a communication connection needs to be terminated (e.g., a link is abnormal), the standby machine node 12 actively sends a termination request to the base station. To avoid continuing to intercept the termination request of the standby machine node 12 during subsequent normal communication interactions, the white list of the intercepted addresses may be updated according to the communication address of the base station. For example, the communication address of the base station may be added to a white list of interception addresses. Therefore, in the subsequent communication process with the base station, when the machine node 11 needs to end the communication connection with the base station, a termination communication packet may be sent to the base station to end the communication session.
In some optional embodiments, the standby machine node 12 may also be used to interact with the operation and maintenance terminal to synchronize the working status to the operation and maintenance personnel in real time. The operation and maintenance terminal can be a mobile phone, a computer, a tablet computer and the like held by operation and maintenance personnel.
Optionally, when the communication link to which the communication packet forwarded by the main node 10 belongs cannot be identified, the standby machine node 12 may send an abnormality warning message to the operation and maintenance terminal to notify the operation and maintenance personnel of performing the abnormality maintenance.
Optionally, when accessing the communication link to which the communication packet forwarded by the master node 10 belongs according to the session environment data between the machine node 11 and the base station, the standby machine node 12 may send a master/standby switching message of the machine node to the operation and maintenance terminal. Therefore, the working state of the main machine and the standby machine can be automatically synchronized with the operation and maintenance personnel.
It should be noted that, in some exemplary embodiments, after the master node 10 routes the communication packet of the base station to the standby machine node when monitoring that the machine node 11 is abnormal, the master node may further analyze the abnormal reason of the machine node according to the monitored state change of the machine node, and record the abnormal reason of the machine node, so as to optimize the load balancing policy according to the abnormal reason.
For example, in some cases, when the master node 10 monitors that the machine node 11 is abnormally down, the master node may analyze the reason for the down according to the state change of the machine node. For example, if the state of the operating environment (e.g., disk state, memory state) changes before the machine node 11 goes down, it may be considered that the down reason of the machine node 11 is the change of the operating environment. For example, if the machine node 11 is subjected to a large number of malicious attacks before going down, it may be considered that the reason why the machine node 11 goes down is caused by the malicious attacks.
The master node 10 may record the above reasons and may optimize the load balancing policy. For example, before optimization, the load balancing policy is: and when the machine node is detected to be down, starting the standby machine node of the machine node to bear the access pressure of the machine node. The optimized load balancing strategy is as follows: when the change of the state of the running environment of the machine node is detected, the standby machine node of the machine node is started to bear the access pressure of the machine node, so that the load balancing can be performed in time before the machine node goes down. For another example, the optimized load balancing policy may be: when detecting that the machine node is attacked maliciously by a certain amount, starting the standby machine node of the machine node to bear the access pressure of the machine node, thereby balancing the load in time before the machine node goes down.
In the above and below embodiments of the present application, the standby machine node 12 mainly acquires data such as a communication address, a serial number of a communication connection, and authentication information between the machine node 11 and a base station when acquiring session environment data of the machine node 11 and the base station. When the communication protocols adopted by the cloud network and the base station are different, the description modes of the communication addresses are different. For example, when the communication Protocol is UDP (User Datagram Protocol), the communication address may be a UDP port number or a socket.
As shown in fig. 2, when the base station communicates with the machine node using the SCTP protocol, the communication address may include an address of an SCTP listening socket. Alternatively, the standby machine node 12 may obtain a data structure in the memory corresponding to the SCTP listening socket of the machine node 11. Accordingly, when accessing the communication link of the base station according to the session environment data, the standby machine node 12 may establish an SCTP association (association) with the base station according to the data structure in the memory corresponding to the SCTP listening socket.
In some exemplary embodiments, when the standby node 12 acquires a data structure in the memory corresponding to the SCTP listening socket in the machine node 11, it may request the acquisition of the data structure in the memory corresponding to the SCTP listening socket from the machine node 11. That is, the standby machine node 12 directly acquires the SCTP listening socket address to the machine node 11.
In other exemplary embodiments, when the standby node 12 acquires the data structure in the memory corresponding to the SCTP listening socket in the machine node 11, it may request to acquire the data structure in the memory corresponding to the SCTP listening socket of the machine node 11 from a database server in the cloud network. Wherein, the data structure in the memory corresponding to the SCTP listening socket is uploaded to the database server by the machine node 11.
Based on the above embodiment, in the cloud network, the socket information may be shared between the machine node 11 and the standby machine node 12, so that when the communication link is switched between the machine node 11 and the standby machine node 12, the standby machine node 12 may quickly access the communication link based on the shared socket information, thereby reducing the link switching delay.
In some exemplary embodiments, the machine nodes in the cloud network and the standby machine nodes are operated with core network components of the mobile network deployed in a containerization manner. The mobile network may be a 4G, 5G, 5.5G or 6G mobile network. Taking the example that the mobile Network is implemented as a 5G mobile Network, a 5G Core Network (5G Core Network, 5GC) may be deployed in a machine node and a standby machine node in a cloud Network in a containerized manner to provide a Core Network service to the base station. Taking the example that the mobile network is implemented as a 4G mobile network, an Evolved Packet Core (EPC) may be deployed in a containerized manner in a machine node and a standby machine node in the cloud network to provide a Core network service for the base station.
Alternatively, kubernets may implement load balancing between machine nodes and standby machine nodes based on MetalLB (a type of load balancer that may operate in a kubernets environment). The controller component (controller) of MetalB resides in the host node of Kubernets. Each machine node in Kubernetes runs the MetalB speaker (spaker) component. The speaker is a daemon of a node where the speaker is located, and is used for executing an announcement service according to an allocated IP (Internet Protocol) address.
As shown in fig. 2, the base station may communicate with a virtual address (vip) using SCTP protocol communications. Wherein, the virtual address is an IP address when the MetalLB exposes the service to the outside in a load balancing mode.
As shown in fig. 3, when a base station accesses a node in kubernets in an off-cluster load manner, the MetalLB may forward a packet of the base station to a machine node in kubernets based on a service of LoadBalancer (a service that forwards traffic to a network). When the message is forwarded, the controller component in the MetalLB can select a leader node (leader) from the plurality of nodes according to the destination IP of the communication message, and inform a speaker (spoke) of the node to be led to respond to the message of the base station. The speaker can send the message to the core network component for processing after the protocol conversion is carried out on the message.
As shown in FIG. 3, the machine node where EPC/5GC _2 is located is a standby machine node of the machine node where EPC/5GC _1 is located. When the machine node where the EPC/5GC _1 is located operates normally, and the controller component in the MetalLB receives the communication message of the base station, the loudspeaker of the machine node where the EPC/5GC _1 is located can be informed to respond to the communication message of the base station based on the destination IP of the communication message. Meanwhile, the controller component of MetalLB can monitor the working state of the machine node where EPC/5GC _1 is located in real time. When the machine node where the EPC/5GC _1 is located is monitored to be abnormal, a controller component in the MetalLB can inform a loudspeaker of the standby machine node (namely the machine node where the EPC/5GC _2 is located) to respond to a communication message of the base station. When the standby machine node can not identify the communication link to which the communication message belongs, the standby machine node can intercept a termination message aiming at the communication link and accesses the communication link according to the session environment data of the machine node so as to respond to the communication message.
In some embodiments, the core network service provided by the mobile network may be a live service, an automatic driving service, a video service, and the like. Taking the live broadcast service as an example, a core network component for providing the live broadcast traffic processing service can be operated on a machine node and a standby machine node in the cloud network.
In a live broadcast scenario, the machine node 11 is mainly used for connecting with a base station and processing a live broadcast traffic processing request of the base station. The live traffic processing request may be a push flow request or a pull flow request of the live traffic, which is not limited in this embodiment.
The master node 10 of the containerized application management platform is mainly used for: monitoring the running state of the machine node 11; when the machine node 11 is monitored to be abnormal, a live broadcast traffic processing request of the base station is routed to the standby machine node 12.
Wherein, the standby machine node 12 is mainly used for: session environment data of the machine node 11 and the base station is acquired. And receiving a live broadcast flow processing request forwarded by the main node based on a load balancing strategy. Intercepting a termination message aiming at a communication link when the communication link to which the live broadcast flow processing request belongs cannot be identified; and accessing the communication link according to the session environment data to process the live broadcast traffic processing request.
For example, when the master node 10 detects a machine node 11 failure, a live traffic pull request sent by a base station may be forwarded to the standby machine node 12. If the standby machine node 12 cannot identify the communication link corresponding to the live broadcast flow pull request, intercepting a termination message for the communication link, and accessing the communication link according to the session environment data of the machine node 11 to process the live broadcast flow pull request.
Based on the implementation mode, when the machine node is abnormal, based on the load balancing strategy and the session environment data of the machine and the shared machine node, the communication link is switched between the machine node and the standby machine node, so that the influence of the abnormal machine node on the live broadcast service can be reduced, and the live broadcast service capability can be improved.
In the automatic driving scenario, the machine node 11 is mainly used for connecting with a base station and processing an automatic driving data processing request of the base station. The automatic driving data processing request may be a downloading request or an uploading request of automatic driving data, and this embodiment is not limited.
The master node 10 of the containerized application management platform is mainly used for: monitoring the running state of the machine node 11; when the machine node 11 is monitored to be abnormal, an automatic driving data processing request of the base station is routed to the standby machine node 12.
Wherein, the standby machine node 12 is mainly used for: session environment data of the machine node 11 and the base station is acquired. And receiving an automatic driving data processing request forwarded by the main node based on a load balancing strategy. Intercepting a termination message for a communication link to which the automatic driving data processing request belongs when the communication link to which the automatic driving data processing request belongs cannot be identified; and accessing the communication link to process the autopilot data processing request based on the session context data.
For example, when the master node 10 monitors that the throughput of the data query of the machine node 11 exceeds a set upper limit, an autonomous driving data download request sent by the base station may be forwarded to the standby machine node 12. If the standby machine node 12 cannot identify the communication link corresponding to the automatic driving data downloading request, intercepting a termination message aiming at the communication link, and accessing the communication link according to the session environment data of the machine node 11 to process the automatic driving data downloading request.
Based on the implementation mode, when the machine node is abnormal, based on the load balancing strategy and the session environment data of the machine and the shared machine node, the communication link is switched between the machine node and the standby machine node, so that the influence of the abnormal machine node on the automatic driving service can be reduced, and the automatic driving service capability is improved.
Fig. 4 is a schematic flowchart of a load balancing method of a cloud network according to an embodiment of the present application. As shown in fig. 4, when executed on the standby machine node side in the cloud network, the method mainly includes the following steps:
And 402, receiving the communication message of the base station forwarded by the main node of the containerized application management platform based on the load balancing strategy when the machine node is abnormal.
In some exemplary embodiments, before accessing the communication link to which the communication packet belongs according to the session environment data, the method further includes: if the communication link to which the communication message belongs cannot be identified, sending a message containing a termination flag bit to the base station; and intercepting the message containing the termination zone bit so as to enable the base station side to maintain the connection of the communication link.
In some exemplary embodiments, after accessing the communication link to which the communication packet belongs according to the session environment data, the method further includes: and updating the white list of the interception address according to the communication address of the base station.
In some exemplary embodiments, the machine node and the standby machine node have core network components of a mobile network running thereon, the core network components being deployed in a containerized manner.
In some exemplary embodiments, the method further comprises: when the communication link to which the communication message belongs cannot be identified, sending an abnormal early warning message to an operation and maintenance terminal; and/or sending a master-slave switching message of the machine node to the operation and maintenance terminal when the communication link to which the communication message belongs is accessed according to the session environment data.
In some exemplary embodiments, one way for the standby machine node to obtain session context data of the machine node and a base station may include: acquiring a data structure in a memory corresponding to the SCTP monitoring socket of the machine node; one way to access the communication link to which the communication packet belongs according to the session environment data may include: and establishing SCTP association with the base station according to a data structure in a memory corresponding to the SCTP monitoring socket.
In some exemplary embodiments, one way to obtain the data structure in the memory corresponding to the SCTP listening socket in the machine node may include: requesting the machine node to acquire a data structure in a memory corresponding to the SCTP monitoring socket; or requesting a database server in the cloud network to acquire a data structure in a memory corresponding to the SCTP monitoring socket; and uploading a data structure in a memory corresponding to the SCTP monitoring socket to the database server by the machine node.
In this embodiment, when a machine node in the cloud network is abnormal, based on the load balancing capability provided by the master node of the containerized application management platform, the communication packet sent by the base station to the machine node may be routed to a standby machine node of the machine node. The standby machine node can share the conversation environment data between the machine node and the base station, and accesses a communication link between the machine node and the base station according to the conversation environment data between the machine node and the base station so as to communicate with the base station. On one hand, the main-standby switching can be realized under the condition that the base station side is not aware, on the other hand, the standby machine node can be quickly accessed into a communication link between the machine node and the base station according to the session environment data between the machine node and the base station, so that the communication transmission can be quickly recovered, and the influence on the application side is reduced.
Fig. 5 is a schematic flowchart of a load balancing method of a cloud network according to another embodiment of the present application. As shown in fig. 5, when executed on the master node side of a containerized application management platform deployed in a cloud network, the method mainly includes the following steps:
In some exemplary embodiments, when the machine node is monitored to be abnormal, after the communication packet of the base station is routed to a standby machine node of the machine node based on a load balancing policy, the method further includes: analyzing the abnormal reason of the machine node according to the monitored state change of the machine node; and recording the abnormal reason of the machine node so as to optimize the load balancing strategy according to the abnormal reason.
In this embodiment, when a machine node in the cloud network is abnormal, based on the load balancing capability provided by the master node of the containerized application management platform, the communication packet sent by the base station to the machine node may be routed to a standby machine node of the machine node. Thus, the standby machine node can access the communication link between the machine node and the base station according to the session environment data between the machine node and the base station to communicate with the base station. Based on the implementation mode, the main-standby switching can be realized under the condition that the base station side does not sense based on the load balancing strategy, and the communication requirement of the base station side is met.
It should be noted that the execution subjects of the steps of the methods provided in the above embodiments may be the same device, or different devices may be used as the execution subjects of the methods. For example, the execution subjects of steps 401 to 403 may be device a; for another example, the execution subject of steps 401 and 402 may be device a, and the execution subject of step 403 may be device B; and so on.
In addition, in some of the flows described in the above embodiments and the drawings, a plurality of operations are included in a specific order, but it should be clearly understood that the operations may be executed out of the order presented herein or in parallel, and the sequence numbers of the operations, such as 401, 402, etc., are merely used to distinguish various operations, and the sequence numbers themselves do not represent any execution order. Additionally, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel.
Fig. 6 illustrates a schematic structural diagram of a server according to an exemplary embodiment of the present application. As shown in fig. 6, the server includes: memory 601, processor 602, and communication component 603.
The memory 601 is used for storing computer programs and may be configured to store other various data to support operations on the server. Examples of such data include instructions for any application or method operating on the server, contact data, phonebook data, messages, pictures, videos, and so forth.
The memory 601 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
In some embodiments, the server illustrated in fig. 6 may be implemented as a master node deployed with a containerized application management platform in a cloud network. The cloud network is also provided with a plurality of machine nodes, and the machine nodes are arranged according to the main/standby mode. A processor 602, coupled to the memory 601, for executing the computer programs in the memory 601 to: monitoring the running state of the machine node in the cloud network, wherein the machine node is connected with a base station; when the machine node is monitored to be abnormal, the communication message of the base station is routed to a standby machine node of the machine node based on a load balancing strategy, so that the standby machine node receives the communication message of the base station forwarded by the main node, and a communication chain to which the communication message belongs is accessed according to the acquired session environment data of the machine node and the base station to respond to the communication message.
Further optionally, when monitoring that the machine node is abnormal, the processor 602, after routing the communication packet of the base station to a standby machine node of the machine node based on a load balancing policy, is further configured to: analyzing the abnormal reason of the machine node according to the monitored state change of the machine node; and recording the abnormal reason of the machine node so as to optimize the load balancing strategy according to the abnormal reason.
In other embodiments, the server illustrated in fig. 6 may be implemented as a standby machine node for any machine node in a cloud network. A processor 602, coupled to the memory 601, for executing the computer programs in the memory 601 to: acquiring session environment data of the machine node and a base station; when the machine node is abnormal, receiving a communication message of the base station forwarded by the main node based on a load balancing strategy; and accessing the communication link to which the communication message belongs according to the session environment data so as to respond to the communication message.
Further optionally, the core network component of the mobile network deployed in a containerization manner runs on the machine node and the standby machine node.
Further optionally, before accessing the communication link to which the communication packet belongs according to the session environment data, the processor 602 is further configured to: if the communication link to which the communication message belongs cannot be identified, sending a message containing a termination flag bit to the base station; and intercepting the message containing the termination zone bit so as to enable the base station side to maintain the connection of the communication link.
Further optionally, after accessing the communication link to which the communication packet belongs according to the session environment data, the processor 602 is further configured to: and updating the white list of the interception address according to the communication address of the base station.
Further optionally, the processor 602 is further configured to: when the communication link to which the communication message belongs cannot be identified, sending an abnormal early warning message to an operation and maintenance terminal; and/or sending a master-slave switching message of the machine node to the operation and maintenance terminal when the communication link to which the communication message belongs is accessed according to the session environment data.
Further optionally, when the standby machine node acquires the session environment data of the machine node and the base station, the processor 602 is specifically configured to: acquiring a data structure in a memory corresponding to the SCTP monitoring socket of the machine node; when accessing the communication link to which the communication packet belongs according to the session environment data, the processor 602 is specifically configured to: and establishing SCTP association with the base station according to a data structure in a memory corresponding to the SCTP monitoring socket.
Further optionally, when acquiring the data structure in the memory corresponding to the SCTP listening socket in the machine node, the processor 602 is specifically configured to: requesting the machine node to acquire a data structure in a memory corresponding to the SCTP monitoring socket; or requesting a database server in the cloud network to acquire a data structure in a memory corresponding to the SCTP monitoring socket; and uploading a data structure in a memory corresponding to the SCTP monitoring socket to the database server by the machine node.
Further, as shown in fig. 6, the server further includes: power supply components 604, and the like. Only some of the components are schematically shown in fig. 6, and it is not meant that the server includes only the components shown in fig. 6.
Wherein the communication component 603 is configured to facilitate communication between the device in which the communication component is located and other devices in a wired or wireless manner. The device in which the communication component is located may access a wireless network based on a communication standard, such as WiFi, 2G, 3G, 4G, or 5G, or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component may be implemented based on Near Field Communication (NFC) technology, Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
The power supply assembly 604 provides power to various components of the device in which the power supply assembly is located. The power components may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device in which the power component is located.
In this embodiment, when a machine node in the cloud network is abnormal, based on the load balancing capability provided by the master node of the containerized application management platform, a communication packet sent to the machine node by the base station may be routed to a standby machine node of the machine node. The standby machine node can share the conversation environment data between the machine node and the base station, and accesses a communication link between the machine node and the base station according to the conversation environment data between the machine node and the base station so as to communicate with the base station. On one hand, the main-standby switching can be realized under the condition that the base station side is not aware, on the other hand, the standby machine node can be quickly accessed into a communication link between the machine node and the base station according to the session environment data between the machine node and the base station, so that the communication transmission can be quickly recovered, and the influence on the application side is reduced.
Accordingly, the present application further provides a computer-readable storage medium storing a computer program, where the computer program can implement the steps that can be executed by the server in the foregoing embodiments when executed.
Accordingly, embodiments of the present application also provide a computer program product, which includes a computer program/instructions, wherein when the computer program is executed by a processor, the processor is caused to implement the steps that can be executed by the server in the above embodiments.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (14)
1. A load balancing method of a cloud network is characterized in that a main node and a plurality of machine nodes of a containerized application management platform are deployed in the cloud network, and the machine nodes are deployed according to a main standby mode; aiming at any machine node and a standby machine node corresponding to the machine node, the method comprises the following steps:
the standby machine node acquires session environment data of the machine node and a base station;
when the machine node is abnormal, receiving a communication message of the base station forwarded by the main node based on a load balancing strategy;
and accessing the communication link to which the communication message belongs according to the session environment data so as to respond to the communication message.
2. The method of claim 1, wherein before accessing the communication link to which the communication packet belongs according to the session context data, further comprising:
if the communication link to which the communication message belongs cannot be identified, sending a message containing a termination flag bit to the base station;
and intercepting the message containing the termination zone bit so as to enable the base station side to maintain the connection of the communication link.
3. The method of claim 2, wherein after accessing the communication link to which the communication packet belongs according to the session environment data, further comprising: and updating the white list of the interception address according to the communication address of the base station.
4. The method of claim 1, further comprising:
when the communication link to which the communication message belongs cannot be identified, sending an abnormal early warning message to an operation and maintenance terminal; and/or the presence of a gas in the gas,
and when the communication link to which the communication message belongs is accessed according to the session environment data, sending a master-slave switching message of the machine node to the operation and maintenance terminal.
5. The method of claim 1, wherein the standby machine node obtaining session context data of the machine node and a base station comprises:
acquiring a data structure in a memory corresponding to the SCTP monitoring socket of the machine node;
accessing the communication link to which the communication message belongs according to the session environment data, including:
and establishing SCTP association with the base station according to a data structure in a memory corresponding to the SCTP monitoring socket.
6. The method of claim 5, wherein obtaining the data structure in the memory corresponding to the SCTP listening socket in the machine node comprises:
requesting the machine node to acquire a data structure in a memory corresponding to the SCTP monitoring socket; or,
requesting a database server in the cloud network to acquire a data structure in a memory corresponding to the SCTP monitoring socket; and uploading a data structure in a memory corresponding to the SCTP monitoring socket to the database server by the machine node.
7. The method according to any of claims 1-6, wherein core network components of the mobile network are run on the machine node and the standby machine node in a containerized deployment.
8. A load balancing method of a cloud network is characterized in that a main node and a plurality of machine nodes of a containerized application management platform are deployed in the cloud network, and the machine nodes are deployed according to a main standby mode; aiming at any machine node and a standby machine node corresponding to the machine node, the method comprises the following steps:
the main node monitors the running state of the machine node, and the machine node is connected with a base station;
when the machine node is monitored to be abnormal, the communication message of the base station is routed to a standby machine node of the machine node based on a load balancing strategy, so that the standby machine node receives the communication message of the base station forwarded by the main node, and a communication link to which the communication message belongs is accessed according to the acquired session environment data of the machine node and the base station to respond to the communication message.
9. The method of claim 8, wherein after monitoring the machine node is abnormal, routing the communication packet of the base station to a standby machine node of the machine node based on a load balancing policy, further comprising:
analyzing the abnormal reason of the machine node according to the monitored state change of the machine node;
and recording the abnormal reason of the machine node so as to optimize the load balancing strategy according to the abnormal reason.
10. A load balancing system for a cloud network, comprising: the method comprises the steps that a main node and a plurality of machine nodes of a containerized application management platform are deployed according to a main-standby mode;
the main node of the containerized application management platform is used for: monitoring the running state of any machine node; the machine node is connected with a base station; when the machine node is monitored to be abnormal, routing the communication message of the base station to a standby machine node of the machine node based on a load balancing strategy;
the standby machine node is to: acquiring session environment data of the machine node and a base station; receiving a communication message of the base station forwarded by the main node based on a load balancing strategy; and accessing the communication link to which the communication message belongs according to the session environment data so as to respond to the communication message.
11. A load balancing system for a cloud network, comprising: the method comprises the steps that a main node and a plurality of machine nodes of a containerized application management platform are deployed according to a main-standby mode; a core network component of a mobile network deployed in a containerization manner runs on any machine node, and the core network component is used for providing a live broadcast traffic processing service;
the main node of the containerized application management platform is used for: monitoring the running state of any machine node; the machine node is connected with a base station; when the machine node is monitored to be abnormal, routing a live broadcast flow processing request of the base station to a standby machine node of the machine node based on a load balancing strategy;
the standby machine node is to: acquiring session environment data of the machine node and a base station; and receiving the live broadcast traffic processing request of the base station forwarded by the main node, and accessing a communication link to which the live broadcast traffic processing request belongs according to the session environment data so as to process the live broadcast traffic processing request.
12. The system of claim 11, wherein the standby machine node, when obtaining the session context data of the machine node and the base station, is specifically configured to: acquiring a data structure in a memory corresponding to the SCTP monitoring socket of the machine node; when accessing the communication link to which the communication packet belongs according to the session environment data, the method is specifically configured to: and establishing SCTP association with the base station according to a data structure in a memory corresponding to the SCTP monitoring socket.
13. A server, comprising: a memory, a processor, and a communication component;
the memory is to store one or more computer instructions;
the processor is to execute the one or more computer instructions to: the steps in the method of any of claims 1-9 are performed by a communication component.
14. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, is adapted to carry out the steps of the method of any one of claims 1 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111165320.9A CN113891358B (en) | 2021-09-30 | 2021-09-30 | Cloud network load balancing method, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111165320.9A CN113891358B (en) | 2021-09-30 | 2021-09-30 | Cloud network load balancing method, device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113891358A true CN113891358A (en) | 2022-01-04 |
| CN113891358B CN113891358B (en) | 2024-04-16 |
Family
ID=79005029
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111165320.9A Active CN113891358B (en) | 2021-09-30 | 2021-09-30 | Cloud network load balancing method, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113891358B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114338360A (en) * | 2022-01-14 | 2022-04-12 | 百果园技术(新加坡)有限公司 | Live list service processing method and system, electronic device and storage medium |
| CN115150592A (en) * | 2022-09-02 | 2022-10-04 | 浙江大华技术股份有限公司 | Audio and video transmission method, server and computer readable storage medium |
| CN115968011A (en) * | 2022-12-29 | 2023-04-14 | 天翼物联科技有限公司 | Equipment session maintenance method, device, equipment and medium for Internet of things platform |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5774660A (en) * | 1996-08-05 | 1998-06-30 | Resonate, Inc. | World-wide-web server with delayed resource-binding for resource-based load balancing on a distributed resource multi-node network |
| WO2012024485A1 (en) * | 2010-08-18 | 2012-02-23 | Airwalk Communications, Inc. | Method and apparatus of load balancing femtocell cluster access |
| CN104503965A (en) * | 2014-10-16 | 2015-04-08 | 杭州斯凯网络科技有限公司 | High-elasticity high availability and load balancing realization method of PostgreSQL (Structured Query Language) |
| CN107454155A (en) * | 2017-07-25 | 2017-12-08 | 北京三快在线科技有限公司 | A kind of fault handling method based on load balancing cluster, device and system |
| CN111885646A (en) * | 2020-07-30 | 2020-11-03 | 北京神州数码云科信息技术有限公司 | Load balancing information transmission method and system of server |
| US20200412651A1 (en) * | 2019-06-27 | 2020-12-31 | Citrix Systems, Inc. | Securing communications between services in a cluster using load balancing systems and methods |
| US20210021671A1 (en) * | 2018-04-28 | 2021-01-21 | Beijing Jingdong Shangke Information Technology Co., Ltd. | Fault handling method and device for gateway server |
| US20210168204A1 (en) * | 2019-12-02 | 2021-06-03 | Microsoft Technology Licensing, Llc | Processing and ordering messages in partitions |
| CN113169895A (en) * | 2018-11-21 | 2021-07-23 | 瑞典爱立信有限公司 | N+1 redundancy for virtualized services with low-latency failover |
-
2021
- 2021-09-30 CN CN202111165320.9A patent/CN113891358B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5774660A (en) * | 1996-08-05 | 1998-06-30 | Resonate, Inc. | World-wide-web server with delayed resource-binding for resource-based load balancing on a distributed resource multi-node network |
| WO2012024485A1 (en) * | 2010-08-18 | 2012-02-23 | Airwalk Communications, Inc. | Method and apparatus of load balancing femtocell cluster access |
| CN104503965A (en) * | 2014-10-16 | 2015-04-08 | 杭州斯凯网络科技有限公司 | High-elasticity high availability and load balancing realization method of PostgreSQL (Structured Query Language) |
| CN107454155A (en) * | 2017-07-25 | 2017-12-08 | 北京三快在线科技有限公司 | A kind of fault handling method based on load balancing cluster, device and system |
| US20210021671A1 (en) * | 2018-04-28 | 2021-01-21 | Beijing Jingdong Shangke Information Technology Co., Ltd. | Fault handling method and device for gateway server |
| CN113169895A (en) * | 2018-11-21 | 2021-07-23 | 瑞典爱立信有限公司 | N+1 redundancy for virtualized services with low-latency failover |
| US20200412651A1 (en) * | 2019-06-27 | 2020-12-31 | Citrix Systems, Inc. | Securing communications between services in a cluster using load balancing systems and methods |
| US20210168204A1 (en) * | 2019-12-02 | 2021-06-03 | Microsoft Technology Licensing, Llc | Processing and ordering messages in partitions |
| CN111885646A (en) * | 2020-07-30 | 2020-11-03 | 北京神州数码云科信息技术有限公司 | Load balancing information transmission method and system of server |
Non-Patent Citations (1)
| Title |
|---|
| 钱周玉: ""基于StarlingX OpenStack集群高可用性的研究"", 《中国优秀博硕士学位论文全文数据库（硕士）》, 15 August 2020 (2020-08-15) * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114338360A (en) * | 2022-01-14 | 2022-04-12 | 百果园技术(新加坡)有限公司 | Live list service processing method and system, electronic device and storage medium |
| CN115150592A (en) * | 2022-09-02 | 2022-10-04 | 浙江大华技术股份有限公司 | Audio and video transmission method, server and computer readable storage medium |
| CN115968011A (en) * | 2022-12-29 | 2023-04-14 | 天翼物联科技有限公司 | Equipment session maintenance method, device, equipment and medium for Internet of things platform |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113891358B (en) | 2024-04-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10715634B2 (en) | System and method for creating virtual interfaces based on network characteristics | |
| US9723069B1 (en) | Redistributing a connection | |
| CN113891358B (en) | Cloud network load balancing method, device and storage medium | |
| US9912633B2 (en) | Selective IP address allocation for probes that do not have assigned IP addresses | |
| JP7389091B2 (en) | METHODS, APPARATUS AND SYSTEM FOR CONTROLLING TRAFFIC FORWARDING | |
| US12526209B1 (en) | Network device and method for searching for edge service implemented in network device | |
| CN114500176A (en) | Multi-stream load balancing method, device and system for VPN and storage medium | |
| US11375441B2 (en) | Systems and methods for connecting wireless clients to preferred edge devices in active-active deployments | |
| WO2013186825A1 (en) | Computer system, communication control server, communication control method, and program | |
| JP2016063425A (en) | COMMUNICATION DEVICE, COMMUNICATION SYSTEM, AND COMMUNICATION METHOD | |
| JP5182051B2 (en) | Service server and communication system using the same | |
| CN114785737A (en) | Message processing method, gateway device, server and storage medium | |
| JP6280223B2 (en) | Method for providing control in a communication network | |
| US12295073B2 (en) | Base station device and method for operating base station device | |
| CN104955125B (en) | Support dispatching method, terminal and the system of multiple types linking Internet | |
| US9866644B2 (en) | Terminal, message distribution system, message distribution method, and computer-readable medium | |
| WO2019242459A1 (en) | Node switching method, network node, network system, and storage medium | |
| US20250168246A1 (en) | Service connection information system for using services in multiple local networks | |
| US20170078196A1 (en) | Communication system, control apparatus, and control method | |
| JP5889122B2 (en) | Control node and communication control method | |
| US20170019845A1 (en) | Communication terminal, communication method, and program-containing storage medium | |
| JP2018055226A (en) | Cluster system, server, operation method, and program | |
| US20150200813A1 (en) | Server connection apparatus and server connection method | |
| CN114389992A (en) | Control flow forwarding method, equipment and system | |
| EP4531372A1 (en) | Methods for optimizing routing of a message and devices thereof |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20240202 Address after: Room 553, 5th Floor, Building 3, No. 969 Wenyi West Road, Wuchang Street, Yuhang District, Hangzhou City, Zhejiang Province, 311121 Applicant after: Hangzhou Alibaba Cloud Feitian Information Technology Co.,Ltd. Country or region after: China Address before: 310023 Room 516, floor 5, building 3, No. 969, Wenyi West Road, Wuchang Street, Yuhang District, Hangzhou City, Zhejiang Province Applicant before: Alibaba Dharma Institute (Hangzhou) Technology Co.,Ltd. Country or region before: China |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |