Methods, Systems and Applications for Managing Wireless Services on a Wireless Device
US-2020014804-A1 · Jan 9, 2020 · US
US11201828B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11201828-B2 |
| Application number | US-201816154475-A |
| Country | US |
| Kind code | B2 |
| Filing date | Oct 8, 2018 |
| Priority date | Oct 8, 2018 |
| Publication date | Dec 14, 2021 |
| Grant date | Dec 14, 2021 |
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 for allocating resources are disclosed. Resources such as streams are allocated using a stream credit system. Credits are issued to the clients in a manner that ensure the system is operating in a safe allocation state. The credits can be used not only to allocate resources but also to throttle clients where necessary. Credits can be granted fully, partially, and in a number greater than a request. Zero or negative credits can also be issued to throttle clients.
Opening claim text (preview).
What is claimed is: 1. A method for allocating resources of a cluster of servers to clients when performing a data protection operation, the method comprising: streaming one or more streams with respect to the clients using the resources of the cluster, wherein each of the one or more streams consumes some of the resources of the cluster of servers; receiving a request for stream credits from a client at the cluster, wherein the stream credits are for using streams provided by the cluster of servers; determining a current allocation matrix that identifies streams currently allocated to each of the clients, wherein the current allocation matrix is based on a total number of streams available from the cluster and streams currently allocated to the clients; determining a current demand matrix that specifies a maximum number of streams that can be requested by each of the clients at a point in time; determining a current need matrix based on the current demand matrix and the current allocation matrix, wherein the current need matrix identifies a number of stream credits that each of the clients can request to acquire their maximum number of stream credits; determining, by the cluster, an allocation state of the cluster in response to the request for stream credits from the client, wherein determining the allocation state includes determining the number of streams available from the servers, assuming that the request for stream credits is granted, and determining whether the client and each of the other clients could request and use their maximum stream credits in succession based on the current allocation matrix, the current demand matrix, the current need matrix and the request for stream credits from the client, wherein the allocation state is safe when each of the clients including the requesting client could request and use their maximum stream credits, and wherein the allocation state is unsafe when the resources associated with the maximum stream credits of each of the clients cannot be allocated and used; and issuing the stream credits in response to the request for stream credits based on the allocation state. 2. The method of claim 1 , further comprising defining a maximum number of streams for allocation for each of the servers in the cluster. 3. The method of claim 2 , wherein the maximum number of streams for allocation is related to processing abilities of the servers. 4. The method of claim 1 , wherein each of the clients can request stream credits from any of the servers. 5. The method of claim 1 , wherein issuing credits based on the allocation state includes at least one of: issuing stream credits in an amount equal to the request when the allocation state is safe; and when the allocation state is unsafe, issuing stream credits in an amount greater than the request; issuing stream credits in an amount greater than zero and less than the request; issuing zero stream credits; or issuing negative stream credits. 6. The method of claim 1 , further comprising throttling the client when the allocation state is not safe until the allocation state is safe. 7. A non-transitory computer readable medium including instructions for implementing a method for allocating resources of a cluster of servers to clients when performing a data protection operation, the method comprising: streaming one or more streams with respect to the clients using the resources of the cluster, wherein each of the one or more streams consumes some of the resources of the cluster of servers; receiving a request for stream credits from a client at the cluster, wherein the stream credits are for using streams provided by the cluster of servers; determining a current allocation matrix that identifies streams currently allocated to each of the clients, wherein the current allocation matrix is based on a total number of streams available from the cluster and streams currently allocated to the clients; determining a current demand matrix that specifies a maximum number of streams that can be requested by each of the clients at a point in time; determining a current need matrix based on the current demand matrix and the current allocation matrix, wherein the current need matrix identifies a number of stream credits that each of the clients can request to acquire their maximum number of stream credits; determining, by the cluster, an allocation state of the cluster in response to the request for stream credits from the client, wherein determining the allocation state includes determining the number of streams available from the servers, assuming that the request for stream credits is granted, and determining whether the client and each of the other clients could request and use their maximum stream credits in succession based on the current allocation matrix, the current demand matrix, the current need matrix and the request for stream credits from the client, wherein the allocation state is safe when each of the clients including the requesting client could request and use their maximum stream credits, and wherein the allocation state is unsafe when the resources associated with the maximum stream credits of each of the clients cannot be allocated and used; and issuing the stream credits in response to the request for stream credits based on the allocation state. 8. The non-transitory computer readable medium of claim 7 , further comprising defining a maximum number of streams for allocation for each of the servers in the cluster. 9. The non-transitory computer readable medium of claim 8 , wherein the maximum number of streams for allocation is related to processing abilities of the servers. 10. The non-transitory computer readable medium of claim 7 , wherein each of the clients can request stream credits from any of the servers. 11. The non-transitory computer readable medium of claim 7 , wherein issuing credits based on the allocation state includes at least one of: issuing stream credits in an amount equal to the request when the allocation state is safe; and when the allocation state is unsafe, issuing stream credits in an amount greater than the request; issuing stream credits in an amount greater than zero and less than the request; issuing zero stream credits; or issuing negative stream credits. 12. The non-transitory computer readable medium of claim 11 , further comprising throttling the client when the allocation state is not safe until the allocation state is safe.
for unicast · CPC title
the resource being a machine, e.g. CPUs, Servers, Terminals · CPC title
by changing the path, e.g. traffic rerouting, path reconfiguration · CPC title
in relation to availability · CPC title
Resource capping · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.