Client-managed hierarchical resource allocation
US-8949429-B1 · Feb 3, 2015 · US
US2019182317A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2019182317-A1 |
| Application number | US-201916275408-A |
| Country | US |
| Kind code | A1 |
| Filing date | Feb 14, 2019 |
| Priority date | Oct 9, 2015 |
| Publication date | Jun 13, 2019 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Systems and methods are provided for managing server loads that accounts for various measures of risk associated with different workloads assigned to servers. The systems and methods may include a memory storing instructions for server load management operations, and a processor configured to execute the stored instructions. The processor may receive a workload, determine a value associated with the workload indicating a predetermined importance of the workload, receive information for a plurality of active servers in a server cluster associated with the processor, determine risk levels associated with the active servers based on the received information, and assign the received workload to one of the active servers based on the determined value and the determined risk levels.
Opening claim text (preview).
1 - 20 . (canceled) 21 . A client device for generating a workload for processing by a load balancer, the client device comprising: one or more memory units for storing instructions; and one or more processors configured to execute the instructions to perform operations comprising: receiving an input associated with a workload; generating the workload based on the received input; determining a workload value associated with the workload, indicating an importance of the workload based on at least one of: a time sensitivity for completing the workload, a value of an expected monetary gain if the workload is completed, or a value of an expected monetary loss if the workload is not completed; transmitting the workload and the workload value to a load balancer, wherein the load balancer is configured to distribute the workload to a server managed by the load balancer based at least on the associated workload value; and receiving a workload result generated by the server upon processing of the workload. 22 . The client device of claim 21 , wherein the generated workload comprises a data set representative of a required task. 23 . The client device of claim 22 , wherein the generated workload further comprises an identification of the client device. 24 . The client device of claim 21 , wherein the input is received from a user of the client device. 25 . The client device of claim 21 , wherein the workload value is determined based on information provided by a user of the client device. 26 . The client device of claim 21 , wherein determining the workload value comprises identifying at least one of a type of the workload or an attribute of the workload. 27 . The client device of claim 26 , wherein determining the workload value further comprises querying a database to select a predetermined value in the database based on the type of the workload or the attribute of the workload. 28 . The client device of claim 27 , wherein the database comprises an array of associations between predetermined workload values and workload types. 29 . The client device of claim 21 , wherein the load balancer is configured to distribute the workload to the server based further on a real-time cumulative resource load of the server, a real-time cumulative workload value status, and a failure rate of the server. 30 . The client device of claim 24 , wherein the client device further comprises a graphical user interface and the user provides the input through the graphical user interface. 31 . The client device of claim 21 , wherein the input is based on a predetermined workload schedule. 32 . The client device of claim 21 , wherein the client device is a point-of-sale terminal and the input comprises instructions to initiate a payment transaction. 33 . A method for generating a workload for processing by a load balancer, the method comprising: receiving an input associated with a workload; generating the workload based on the received input; determining a workload value associated with the workload, indicating an importance of the workload based on at least one of: a time sensitivity for completing the workload, a value of an expected monetary gain if the workload is completed, or a value of an expected monetary loss if the workload is not completed; transmitting the workload and the workload value to a load balancer, wherein the load balancer is configured to distribute the workload to a server managed by the load balancer based at least on the associated workload value; and receiving a workload result generated by the server upon processing of the workload. 34 . The method of claim 33 , wherein the generated workload comprises a data set representative of a required task. 35 . The method of claim 34 , wherein the generated workload further comprises an identification of a client device associated with the workload. 36 . The method of claim 33 , wherein the input is received from a user of a client device associated with the workload. 37 . The method of claim 33 , wherein the workload value is determined based on information provided by a user of a client device associated with the workload. 38 . The method of claim 33 , wherein determining the workload value comprises: identifying at least one of a type of the workload or an attribute of the workload, and querying a database to select a predetermined workload value in the database based on the type of the workload or the attribute of the workload. 39 . The method of claim 33 , wherein the load balancer is configured to distribute the workload to the server based further on a real-time cumulative resource load of the server, a real-time cumulative workload value status, and a failure rate of the server. 40 . A client device for generating a workload for processing by a load balancer, the client device comprising: one or more memory units for storing instructions; and one or more processors configured to execute the instructions to perform operations comprising: receiving an input associated with a workload; generating the workload based on the received input; determining a workload value associated with the workload, indicating an importance of the workload based on at least one of: a time sensitivity for completing the workload, a value of an expected monetary gain if the workload is completed, or a value of an expected monetary loss if the workload is not completed; transmitting the workload and the workload value to a load balancer, wherein the load balancer distributes the workload to a server managed by the load balancer based at least on the associated workload value; and wherein the workload comprises instructions for the server to provide a workload result associated with the workload to a device other than the client device.
using data related to the state of servers by a load balancer · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.