CN110855764A - Network traffic scheduling method and device and electronic equipment - Google Patents
Network traffic scheduling method and device and electronic equipment Download PDFInfo
- Publication number
- CN110855764A CN110855764A CN201911067213.5A CN201911067213A CN110855764A CN 110855764 A CN110855764 A CN 110855764A CN 201911067213 A CN201911067213 A CN 201911067213A CN 110855764 A CN110855764 A CN 110855764A
- Authority
- CN
- China
- Prior art keywords
- service server
- server
- response message
- health
- service
- 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.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
Abstract
The application provides a network traffic scheduling method, a network traffic scheduling device, an electronic device and a machine-readable storage medium. In the application, health monitoring configuration input by a user is received and stored locally; wherein the health monitoring configuration at least comprises a server address of the business server and a business type of the business server; based on the health monitoring configuration, carrying out health state check on the business server to obtain the business server with abnormal health state; the method and the system schedule the target network traffic of the service server with the abnormal health state destination address and schedule the target network traffic to the service server with the normal health state, thereby reducing the service interruption time and improving the network traffic scheduling efficiency for bearing different service types.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a network traffic scheduling method and apparatus, an electronic device, and a machine-readable storage medium.
Background
Load Balance (LB) is a clustering technique for servers or network devices. The load balancing equipment shares the specific service request to a plurality of servers or network equipment connected and communicated with the load balancing equipment, thereby improving the service processing capacity and ensuring the high availability of the service.
For example, in implementation, a server set can be formed by a plurality of servers in a symmetric manner, each server in the server set has an equivalent status, and can provide external service independently without the assistance of other servers; through the load balancing technology, the service request which is targeted to be responsible for the server set is uniformly distributed to one server in the server set, so that the server receiving the service request independently responds to the request of the client. Based on the load balancing technology, the client requests can be evenly distributed to the server array, important data can be rapidly acquired, and the problem of massive concurrent access service is solved.
Disclosure of Invention
The application provides a network traffic scheduling method, which is applied to load balancing equipment, wherein the load balancing equipment is connected with a butted service server for communication, and the method comprises the following steps:
receiving health monitoring configuration input by a user and storing the health monitoring configuration in local; wherein the health monitoring configuration at least comprises a server address of the business server and a business type of the business server;
based on the health monitoring configuration, carrying out health state check on the business server to obtain the business server with abnormal health state;
and scheduling the target network flow of the service server with the abnormal health state as the destination address, and scheduling the target network flow to the service server with the normal health state.
Optionally, both the load balancing device and the service server use a Diameter protocol; the load balancing equipment is used as a Diameter client of the service server, and the service server is used as a Diameter server of the load balancing equipment;
the health monitoring configuration further includes Diameter attribute information;
the performing health status check on the service server based on the health monitoring configuration to obtain the service server with abnormal health status includes:
constructing a request message indicating Diameter capability exchange according to a preset period based on the service type of a service server in the health monitoring configuration and Diameter attribute information corresponding to the service type, and sending the request message to the service server;
receiving a response message which is sent by the service server and corresponds to the request message; wherein, the response message includes a status code indicating the Diameter capability exchange result of the service server;
and obtaining the service server with abnormal health state based on the state code of the response message.
Optionally, the obtaining of the service server with an abnormal health state based on the state code of the response packet includes:
checking whether the value of the status code of the response message is a value with 2 as a first factor;
and if the value of the state code of the response message is not a value with the head of 2, indicating that the health state of the service server corresponding to the response message is abnormal, and obtaining the server address of the corresponding service server from the response message.
Optionally, the method further includes:
and if the value of the state code of the response message is a value with the priority of 2, indicating that the health state of the service server corresponding to the response message is normal, and obtaining the server address of the corresponding service server from the response message.
The present application further provides a network traffic scheduling apparatus, where the apparatus is applied to a load balancing device, the load balancing device is connected to a service server for communication, and the apparatus includes:
the configuration module receives the health monitoring configuration input by the user and stores the health monitoring configuration locally; wherein the health monitoring configuration at least comprises a server address of the business server and a business type of the business server;
the monitoring module is used for carrying out health state check on the business server based on the health monitoring configuration to obtain the business server with abnormal health state;
and the scheduling module is used for scheduling the target network traffic of the service server with the abnormal health state as the destination address and scheduling the target network traffic to the service server with the normal health state.
Optionally, both the load balancing device and the service server use a Diameter protocol; the load balancing equipment is used as a Diameter client of the service server, and the service server is used as a Diameter server of the load balancing equipment;
the health monitoring configuration further includes Diameter attribute information;
the monitoring module further:
constructing a request message indicating Diameter capability exchange according to a preset period based on the service type of a service server in the health monitoring configuration and Diameter attribute information corresponding to the service type, and sending the request message to the service server;
receiving a response message which is sent by the service server and corresponds to the request message; wherein, the response message includes a status code indicating the Diameter capability exchange result of the service server;
and obtaining the service server with abnormal health state based on the state code of the response message.
Optionally, the monitoring module further:
checking whether the value of the status code of the response message is a value with 2 as a first factor;
and if the value of the state code of the response message is not a value with the head of 2, indicating that the health state of the service server corresponding to the response message is abnormal, and obtaining the server address of the corresponding service server from the response message.
Optionally, the monitoring module further:
and if the value of the state code of the response message is a value with the priority of 2, indicating that the health state of the service server corresponding to the response message is normal, and obtaining the server address of the corresponding service server from the response message.
The application also provides an electronic device, which comprises a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are mutually connected through the bus;
the memory stores machine-readable instructions, and the processor executes the method by calling the machine-readable instructions.
The present application also provides a machine-readable storage medium having stored thereon machine-readable instructions which, when invoked and executed by a processor, implement the above-described method.
Through the embodiment, the Diameter request message is constructed based on the health monitoring configuration period; and sending the Diameter request message to a service server based on the Diameter request message, acquiring a corresponding Diameter response message, further acquiring the service server with abnormal health state according to the state code of the Diameter response message, and rescheduling the target flow of the abnormal service server to the service server with normal health state, thereby reducing the service interruption time and improving the network flow scheduling efficiency for bearing different service types.
Drawings
FIG. 1 is a networking diagram of a load balancing system provided by an exemplary embodiment;
FIG. 2 is a flow chart of a method for network traffic scheduling provided by an exemplary embodiment;
fig. 3 is a block diagram of a network traffic scheduling apparatus according to an exemplary embodiment;
fig. 4 is a hardware block diagram of an electronic device according to an exemplary embodiment.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
In order to enable those skilled in the art to better understand the technical solution in the embodiment of the present application, a brief description will be given below to the related technology of network traffic scheduling related to the embodiment of the present application.
Referring to fig. 1, fig. 1 is a networking diagram of a load balancing system according to an embodiment of the present application.
The load balancing system shown in fig. 1 includes: load balancing devices (SLB), clients (C1, C2, C3), servers (S1, S2, S3);
the clients (C1, C2, C3) are connected to and communicate with the service servers (S1, S2, S3) through the load balancing device SLB via the network shown in fig. 1.
In implementation, a service request from a client to a service server as shown in fig. 1 may be forwarded by a load balancing device to a corresponding service server selected by a load balancing algorithm.
For example: the SLB may forward the service request from the C1 client to the service server S1 selected by the load balancing algorithm; the SLB may also forward the service request from the C2 client to the service server S2 selected by the load balancing algorithm; the SLB may also forward the service request from the C3 client to the service server S3 selected by the load balancing algorithm.
On the basis of the networking architecture, the method aims to provide a method for monitoring the health of a service server based on a Diameter protocol; and scheduling the target network traffic of the service server with the abnormal health state as the destination address.
When the method is realized, the load balancing equipment is connected with the butted service server for communication; the load balancing equipment receives health monitoring configuration input by a user and stores the health monitoring configuration locally; the health monitoring configuration at least comprises a server address of the business server and a business type of the business server.
Further, the load balancing device performs health state check on the service server based on the health monitoring configuration to obtain the service server with abnormal health state; and scheduling the target network flow of the service server with the abnormal health state as the destination address, and scheduling the target network flow to the service server with the normal health state.
In the scheme, a Diameter request message is constructed based on a health monitoring configuration cycle; and sending the Diameter request message to a service server based on the Diameter request message, acquiring a corresponding Diameter response message, further acquiring the service server with abnormal health state according to the state code of the Diameter response message, and rescheduling the target flow of the abnormal service server to the service server with normal health state, thereby reducing the service interruption time and improving the network flow scheduling efficiency for bearing different service types.
The present application is described below with reference to specific embodiments and specific application scenarios.
Referring to fig. 2, fig. 2 is a flowchart of a network traffic scheduling method according to an embodiment of the present application, where the method is applied to a load balancing device, and the load balancing device is connected to a docked service server for communication, where the method performs the following steps:
And 204, based on the health monitoring configuration, carrying out health state check on the service server to obtain the service server with abnormal health state.
And step 206, scheduling the target network traffic of the service server with the abnormal health state as the destination address, and scheduling the target network traffic to the service server with the normal health state.
In this specification, the load balancing device may include any device integrated with a load balancing function.
For example, in practical applications, the load balancing device may specifically include a switch, a router, a firewall, a server, a load balancer, and the like, which have a load balancing function.
In one embodiment, the load balancing device is a Diameter protocol supported and enabled load balancing device.
For example, in practical applications, the load balancing device may specifically include a Diameter protocol-enabled switch, a router, a firewall, a server, a load balancer, and the like, which have a load balancing function.
In this specification, the service server includes one or more servers of any service type connected to and communicating with the load balancing device and managed by the load balancing device in a scheduling manner.
In one embodiment, the service server is a service server supporting and enabling a Diameter protocol.
For example, in an actual application, the service server may specifically include a server cluster that is supported by the load balancing device for scheduling management and enables a Diameter protocol, and the like.
In this specification, the health monitoring configuration refers to any configuration for the load balancing device to perform health monitoring on the service server.
For example, in practical applications, the health monitoring configuration may specifically include a configuration based on text file or binary data or an entry for the load balancing device to perform health monitoring on the service server.
In this specification, the health monitoring configuration at least includes a server address of the service server and a service type of the service server.
For example, referring to fig. 1, the health monitoring configuration at least includes the server address of the service server S1, the service type of the service server S1; the server address of the service server S2, the service type of the service server S2; the server address of the service server S3, the service type of the service server S3.
It should be noted that the service type of the service server is not limited in this specification. For example, in practical applications, the service types of the service server may include Web services, audio/video services, mobile communication services such as 2G/3G/4G, various app application services, and the like.
In this specification, the load balancing device receives the health monitoring configuration input by the user and stores the health monitoring configuration locally.
For example, in practical applications, the load balancing device may output an interface for inputting the health monitoring configuration to a user through a web page or a command line, and the user inputs the health monitoring configuration on the interface, and the load balancing device receives the health monitoring configuration input by the user and stores the health monitoring configuration locally.
In this specification, when receiving and storing the health monitoring configuration, the load balancing device performs a health status check on the service server based on the health monitoring configuration, and obtains a service server with an abnormal health status.
In an embodiment shown, the health monitoring configuration further includes Diameter attribute information in addition to a server address of the service server and a service type of the service server;
the Diameter Attribute information includes any Attribute Pair information or Attribute Pair information that conforms to the Diameter message format and that can be encapsulated in an AVP (Attribute-Value-Pair) of the Diameter message.
For example, in practical applications, the Diameter attribute information may include AVP information indicating a service type of the service server; and the AVP information can also be used for indicating the service type of the service server to carry out authentication, charging and auditing.
It should be noted that the type and number of the attribute pair information included in the Diameter attribute information, which may be used as an AVP, are not specifically limited in this specification, and for a specific attribute information format and content, please refer to the description of the Diameter message format, which is not described herein again.
In an embodiment shown, the load balancing device and the service server both use a Diameter protocol; the load balancing device is used as a Diameter client of the service server, and the service server is used as a Diameter server of the load balancing device.
For example, referring to fig. 1, the load balancing device SLB and the traffic servers S1, S2, S3 all enable the Diameter protocol; the load balancing device SLB as a Diameter client and S1, S2, and S3 as a Diameter server, respectively, may perform interactive communication based on a Diameter protocol.
Further, in an embodiment shown in the present disclosure, in a process of performing a health status check on the service server based on the health monitoring configuration to obtain a service server with an abnormal health status, the load balancing device constructs, according to a preset period, a request packet indicating Diameter capability exchange based on a service type of the service server in the health monitoring configuration and Diameter attribute information corresponding to the service type, and sends the request packet to the service server.
For example, referring to fig. 1, the service servers S1 and S3 may be Web service type servers, and the service server S2 may be an audio/video service type server; the health monitoring configuration comprises Web service types of service servers S1 and S3, a plurality of Diameter attribute information corresponding to the service types, and server addresses corresponding to the service servers S1 and S3 respectively; the health monitoring configuration further includes an audio/video service type of the service server S2, a plurality of Diameter attribute information corresponding to the service type, and a server address corresponding to the service server S2. The load balancing device SLB constructs request messages indicating Diameter capability exchange according to a preset period (for example, every 1 second) based on the Web service types of the service servers S1 and S3 and the Diameter attribute information corresponding to the service types, respectively, and sends the request messages to the service server S1 and the service server S3, respectively. Similarly, a corresponding Diameter capability exchange request message is constructed and sent for the service server S2.
It should be noted that, in this specification, please refer to the Diameter protocol description for the specific format of the request message for indicating Diameter capability exchange, which is not described herein again. The health detection of the service server is carried out through the Diameter protocol, and whether the application service borne by the service server is normal or not can be accurately detected.
Of course, in practical applications, the request message indicating Diameter capability exchange may include an application identifier and the like in addition to the service type of the service server and the Diameter attribute information corresponding to the service type, and refer to the Diameter protocol description specifically, which is not described herein again.
In this specification, further, the load balancing device receives a response message corresponding to the request message, which is sent by the service server; wherein, the response message includes a status code indicating the Diameter capability exchange result of the service server.
Continuing the example from the above example, further, the load balancing device SLB receives response messages corresponding to the request messages (request messages indicating Diameter capability exchange) sent by the service servers S1, S2, and S3, respectively; wherein, the response message at least includes a status code indicating the Diameter capability exchange result of the service server; the status code may generally include 1xxx, 2xxx, 3xxx, 4xxx, and 5xxx, which refer to different statuses corresponding to the Diameter capability exchange result procedure of the service server (x represents any integer between 0 and 9 (including 0 and 9)); the status code 2xxx indicates that the status of the Diameter capability exchange result of the service server is a successful status, and the other status codes are unsuccessful status, which is specifically referred to the Diameter protocol description and will not be described here.
In this specification, further, the load balancing device obtains a service server with an abnormal health status based on the status code of the response packet.
In an embodiment shown in the present invention, in the process of obtaining a service server with an abnormal health state based on the status code of the response packet, the load balancing device checks whether the value of the status code of the response packet is a value beginning with 2.
For example, in practical applications, the value of the status code of the reply message may be 2xxx or may not be 2xxx (including any of 1xxx, 3xxx, 4xxx and 5 xxx).
In an illustrated embodiment, if the value of the status code of the response packet is not a value beginning with 2, the health status of the service server corresponding to the response packet is indicated to be abnormal, and the load balancing device obtains the server address of the corresponding service server from the response packet.
Continuing with the above example, referring to fig. 1, if the value of the status code of the service response packet corresponding to the service server S1 is not 2xxx (the value of the status code may be any one of 1xxx, 3xxx, 4xxx and 5 xxx); by checking that the value of the status code of the response packet is not a value beginning with 2, the health status of the service server S1 corresponding to the response packet is indicated to be abnormal, and the load balancing device obtains the server address of the corresponding service server S1 from the response packet.
In an illustrated embodiment, if the value of the status code of the response packet is a value with 2 as the first, the health status of the service server corresponding to the response packet is indicated to be normal, and the load balancing device obtains the server address of the corresponding service server from the response packet.
Continuing the example from the above example, please refer to fig. 1, if the value of the status code of the service response message corresponding to the service server S3 is 2 xxx; by checking that the value of the status code of the response packet is a value beginning with 2, the health status of the service server S3 corresponding to the response packet is indicated to be normal, and the load balancing device obtains the server address of the corresponding service server S3 from the response packet.
In this specification, the load balancing device schedules a target network traffic of a service server with an abnormal health status as a destination address, and schedules the target network traffic to the service server with a normal health status.
Continuing the example from the above example, when the target network traffic is the service server S1 with the destination address being abnormal in health status, the load balancing device schedules the target network traffic from the service server S1 to the service server S3 with the normal health status.
In the technical scheme, a Diameter request message is constructed based on a health monitoring configuration cycle; and sending the Diameter request message to a service server based on the Diameter request message, acquiring a corresponding Diameter response message, further acquiring the service server with abnormal health state according to the state code of the Diameter response message, and rescheduling the target flow of the abnormal service server to the service server with normal health state, thereby reducing the service interruption time and improving the network flow scheduling efficiency for bearing different service types.
Fig. 3 is a block diagram of a network traffic scheduling apparatus according to an exemplary embodiment of the present application. Corresponding to the foregoing method embodiment, the present application further provides an embodiment of a network traffic scheduling apparatus, where the apparatus is applied to a load balancing device, and the load balancing device is connected to a docked service server for communication, please refer to an example of a network traffic scheduling apparatus 30 illustrated in fig. 3, where the apparatus includes:
the configuration module 301 receives health monitoring configuration input by a user and stores the health monitoring configuration locally; wherein the health monitoring configuration at least comprises a server address of the business server and a business type of the business server;
a monitoring module 302, configured to perform health status check on the service server based on the health monitoring configuration, so as to obtain a service server with an abnormal health status;
the scheduling module 303 schedules a target network traffic of a service server with an abnormal health status as a destination address, and schedules the target network traffic to the service server with a normal health status.
In this embodiment, both the load balancing device and the service server use a Diameter protocol; the load balancing equipment is used as a Diameter client of the service server, and the service server is used as a Diameter server of the load balancing equipment;
the health monitoring configuration further includes Diameter attribute information;
the monitoring module 302 further:
constructing a request message indicating Diameter capability exchange according to a preset period based on the service type of a service server in the health monitoring configuration and Diameter attribute information corresponding to the service type, and sending the request message to the service server;
receiving a response message which is sent by the service server and corresponds to the request message; wherein, the response message includes a status code indicating the Diameter capability exchange result of the service server;
and obtaining the service server with abnormal health state based on the state code of the response message.
In this embodiment, the monitoring module 302 further:
checking whether the value of the status code of the response message is a value with 2 as a first factor;
and if the value of the state code of the response message is not a value with the head of 2, indicating that the health state of the service server corresponding to the response message is abnormal, and obtaining the server address of the corresponding service server from the response message.
In this embodiment, the monitoring module 403 further:
and if the value of the state code of the response message is a value with the priority of 2, indicating that the health state of the service server corresponding to the response message is normal, and obtaining the server address of the corresponding service server from the response message.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, wherein the modules described as separate parts may or may not be physically separate, and the parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
The systems, devices, modules or modules illustrated in the above embodiments may be implemented by a computer chip or an entity, or by an article of manufacture with certain functionality. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
The embodiment of the network traffic scheduling apparatus of the present application can be applied to the electronic device shown in fig. 4. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. Taking a software implementation as an example, as a logical device, the device is a machine executable instruction formed by reading a corresponding computer program instruction in a machine readable storage medium through a processor of the electronic device where the device is located and then running the computer program instruction. In terms of hardware, as shown in fig. 4, the electronic device in which the network traffic scheduling apparatus is located according to the present application is a hardware structure diagram, except for the processor, the communication interface, the bus, and the machine-readable storage medium shown in fig. 4, the electronic device in which the apparatus is located in the embodiment may also include other hardware according to an actual function of the electronic device, which is not described again.
Correspondingly, an embodiment of the present application further provides a hardware structure of an electronic device of the apparatus shown in fig. 3, please refer to fig. 4, and fig. 4 is a schematic diagram of the hardware structure of the electronic device provided in the embodiment of the present application. The apparatus comprises: a communication interface 401, a processor 402, a machine-readable storage medium 403, and a bus 404; the communication interface 401, the processor 402 and the machine-readable storage medium 403 are configured to communicate with each other via a bus 404. The communication interface 401 is used for performing network communication. The processor 402 may be a Central Processing Unit (CPU), and the processor 402 may execute machine-readable instructions stored in a machine-readable storage medium 403 to implement the methods described above.
The machine-readable storage medium 403 referred to herein may be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and the like. For example, the machine-readable storage medium may be: volatile memory, non-volatile memory, or similar storage media. In particular, the machine-readable storage medium 403 may be a RAM (random Access Memory), a flash Memory, a storage drive (e.g., a hard disk drive), a solid state disk, any type of storage disk (e.g., a compact disk, a DVD, etc.), or similar storage medium, or a combination thereof.
Up to this point, the description of the hardware configuration shown in fig. 4 is completed.
Further, the present application provides a machine-readable storage medium, such as machine-readable storage medium 403 in fig. 4, including machine-executable instructions, which can be executed by processor 402 in the data processing apparatus to implement the data processing method described above.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (10)
1. A network traffic scheduling method is applied to a load balancing device, wherein the load balancing device is connected with a butted service server for communication, and the method comprises the following steps:
receiving health monitoring configuration input by a user and storing the health monitoring configuration in local; wherein the health monitoring configuration at least comprises a server address of the business server and a business type of the business server;
based on the health monitoring configuration, carrying out health state check on the business server to obtain the business server with abnormal health state;
and scheduling the target network flow of the service server with the abnormal health state as the destination address, and scheduling the target network flow to the service server with the normal health state.
2. The method of claim 1, wherein the load balancing device and the traffic server both enable Diameter protocol; the load balancing equipment is used as a Diameter client of the service server, and the service server is used as a Diameter server of the load balancing equipment;
the health monitoring configuration further includes Diameter attribute information;
the performing health status check on the service server based on the health monitoring configuration to obtain the service server with abnormal health status includes:
constructing a request message indicating Diameter capability exchange according to a preset period based on the service type of a service server in the health monitoring configuration and Diameter attribute information corresponding to the service type, and sending the request message to the service server;
receiving a response message which is sent by the service server and corresponds to the request message; wherein, the response message includes a status code indicating the Diameter capability exchange result of the service server;
and obtaining the service server with abnormal health state based on the state code of the response message.
3. The method according to claim 2, wherein obtaining the service server with abnormal health status based on the status code of the response packet comprises:
checking whether the value of the status code of the response message is a value with 2 as a first factor;
and if the value of the state code of the response message is not a value with the head of 2, indicating that the health state of the service server corresponding to the response message is abnormal, and obtaining the server address of the corresponding service server from the response message.
4. The method of claim 3, further comprising:
and if the value of the state code of the response message is a value with the priority of 2, indicating that the health state of the service server corresponding to the response message is normal, and obtaining the server address of the corresponding service server from the response message.
5. A network traffic scheduling device is applied to a load balancing device, the load balancing device is connected with a butted service server for communication, and the device comprises:
the configuration module receives the health monitoring configuration input by the user and stores the health monitoring configuration locally; wherein the health monitoring configuration at least comprises a server address of the business server and a business type of the business server;
the monitoring module is used for carrying out health state check on the business server based on the health monitoring configuration to obtain the business server with abnormal health state;
and the scheduling module is used for scheduling the target network traffic of the service server with the abnormal health state as the destination address and scheduling the target network traffic to the service server with the normal health state.
6. The apparatus of claim 5, wherein the load balancing device and the traffic server both enable Diameter protocol; the load balancing equipment is used as a Diameter client of the service server, and the service server is used as a Diameter server of the load balancing equipment;
the health monitoring configuration further includes Diameter attribute information;
the monitoring module further:
constructing a request message indicating Diameter capability exchange according to a preset period based on the service type of a service server in the health monitoring configuration and Diameter attribute information corresponding to the service type, and sending the request message to the service server;
receiving a response message which is sent by the service server and corresponds to the request message; wherein, the response message includes a status code indicating the Diameter capability exchange result of the service server;
and obtaining the service server with abnormal health state based on the state code of the response message.
7. The apparatus of claim 6, wherein the monitoring module is further to:
checking whether the value of the status code of the response message is a value with 2 as a first factor;
and if the value of the state code of the response message is not a value with the head of 2, indicating that the health state of the service server corresponding to the response message is abnormal, and obtaining the server address of the corresponding service server from the response message.
8. The apparatus of claim 7, wherein the monitoring module is further to:
and if the value of the state code of the response message is a value with the priority of 2, indicating that the health state of the service server corresponding to the response message is normal, and obtaining the server address of the corresponding service server from the response message.
9. An electronic device is characterized by comprising a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are connected with each other through the bus;
the memory has stored therein machine-readable instructions, the processor executing the method of any of claims 1 to 4 by calling the machine-readable instructions.
10. A machine-readable storage medium having stored thereon machine-readable instructions which, when invoked and executed by a processor, carry out the method of any of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911067213.5A CN110855764A (en) | 2019-11-04 | 2019-11-04 | Network traffic scheduling method and device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911067213.5A CN110855764A (en) | 2019-11-04 | 2019-11-04 | Network traffic scheduling method and device and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110855764A true CN110855764A (en) | 2020-02-28 |
Family
ID=69598788
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911067213.5A Pending CN110855764A (en) | 2019-11-04 | 2019-11-04 | Network traffic scheduling method and device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110855764A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112749009A (en) * | 2020-12-30 | 2021-05-04 | 杭州迪普科技股份有限公司 | Server scheduling method and device |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101079742A (en) * | 2007-07-03 | 2007-11-28 | 中兴通讯股份有限公司 | Data synchronization method and system between disaster tolerance home user servers |
| US20110276982A1 (en) * | 2010-05-06 | 2011-11-10 | Hitachi, Ltd. | Load Balancer and Load Balancing System |
| CN103124290A (en) * | 2012-12-11 | 2013-05-29 | 广东电网公司电力调度控制中心 | Load balancing method based on combined application of reverse isolation devices and isolation gateway |
| CN104468169A (en) * | 2013-09-23 | 2015-03-25 | 中兴通讯股份有限公司 | Method, device, equipment and system for operation and maintenance monitoring based on site state |
| CN108199914A (en) * | 2017-12-27 | 2018-06-22 | 杭州迪普科技股份有限公司 | Server-side condition detection method and device |
| CN108322362A (en) * | 2018-01-31 | 2018-07-24 | 广州市中南民航空管通信网络科技有限公司 | Monitoring method, electronic equipment and the storage medium of service transmission quality in a kind of transmission network |
| CN109558246A (en) * | 2018-12-04 | 2019-04-02 | 北京字节跳动网络技术有限公司 | A kind of load-balancing method, device, electronic equipment and storage medium |
-
2019
- 2019-11-04 CN CN201911067213.5A patent/CN110855764A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101079742A (en) * | 2007-07-03 | 2007-11-28 | 中兴通讯股份有限公司 | Data synchronization method and system between disaster tolerance home user servers |
| US20110276982A1 (en) * | 2010-05-06 | 2011-11-10 | Hitachi, Ltd. | Load Balancer and Load Balancing System |
| CN103124290A (en) * | 2012-12-11 | 2013-05-29 | 广东电网公司电力调度控制中心 | Load balancing method based on combined application of reverse isolation devices and isolation gateway |
| CN104468169A (en) * | 2013-09-23 | 2015-03-25 | 中兴通讯股份有限公司 | Method, device, equipment and system for operation and maintenance monitoring based on site state |
| CN108199914A (en) * | 2017-12-27 | 2018-06-22 | 杭州迪普科技股份有限公司 | Server-side condition detection method and device |
| CN108322362A (en) * | 2018-01-31 | 2018-07-24 | 广州市中南民航空管通信网络科技有限公司 | Monitoring method, electronic equipment and the storage medium of service transmission quality in a kind of transmission network |
| CN109558246A (en) * | 2018-12-04 | 2019-04-02 | 北京字节跳动网络技术有限公司 | A kind of load-balancing method, device, electronic equipment and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112749009A (en) * | 2020-12-30 | 2021-05-04 | 杭州迪普科技股份有限公司 | Server scheduling method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10454795B1 (en) | Intermediate batch service for serverless computing environment metrics | |
| CN110166570B (en) | Service session management method and device, and electronic device | |
| JP6505843B2 (en) | Technology for Contextual Mobile Data Access | |
| CN107888787B (en) | Method and device for processing media access request | |
| CN113783922A (en) | Load balancing method, system and device | |
| CN111163130A (en) | Network service system and data transmission method thereof | |
| CN102594716B (en) | A kind of transmission method, system and equipment of instant communication message | |
| CN112600878B (en) | Data transmission method and device | |
| US9699132B2 (en) | Method, apparatus, and system for exchanging electronic business card | |
| CN115022318B (en) | Message publishing method and system based on micro-service architecture | |
| CN111064804A (en) | Network access method and device | |
| CN110233902B (en) | Session processing method and device, electronic equipment and machine-readable storage medium | |
| CN108399175B (en) | Data storage and query method and device | |
| CN104601448A (en) | Method and device for handling virtual card | |
| CN110855764A (en) | Network traffic scheduling method and device and electronic equipment | |
| CN109167819A (en) | Data synchronous system, method, apparatus and storage medium | |
| CN110581784B (en) | Node health check method, device and equipment | |
| US9736661B2 (en) | Handling of messages in a partially deployed IMS network | |
| CN110545296A (en) | Log data acquisition method, device and equipment | |
| EP3493486A1 (en) | Publishing message conversations to electronic forums | |
| US11783075B2 (en) | Systems and methods of providing access to secure data | |
| CN107547382B (en) | Neighbor relation discovery method and device | |
| US20150120607A1 (en) | System and method for customer event email consolidation and delivery | |
| CN114157720A (en) | Method, device, electronic equipment and medium for processing service request | |
| JP2014135713A (en) | Notification system |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200228 |
|
| RJ01 | Rejection of invention patent application after publication |