Client side backoff filter for rate limiting
US-2024314075-A1 · Sep 19, 2024 · US
US2024406287A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2024406287-A1 |
| Application number | US-202418743693-A |
| Country | US |
| Kind code | A1 |
| Filing date | Jun 14, 2024 |
| Priority date | Mar 29, 2011 |
| Publication date | Dec 5, 2024 |
| 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.
Mechanisms are provided to allow efficient delivery of content through a content delivery network (CDN) without taxing an origin server while maintaining fine grained location based access control. Requests to a CDN are augmented with quantized and non-quantized versions of location information. A CDN can use quantized location information in a URI to identify and return content if content corresponding to the URI is available in cache. If the content is not available in cache, the CDN can contact an origin server to obtain a result for the request using non-quantized location information. The origin server examines the non-quantized location information to determine whether to respond to the client request with content. The origin server examines the area corresponding to the quantized location information to determine whether the content should be cached at the CDN.
Opening claim text (preview).
1 .- 20 . (canceled) 21 . A method comprising: receiving a service request from a client device, wherein the service request comprises first location coordinates; identifying a first geographical region based on the first location coordinates; determining whether devices located in entirety of the first geographical region are allowed access to the requested service; based at least in part on determining that: (a) devices in a first part of the first geographical region are allowed to access the requested service, and (b) devices in a second part of the first geographical region are not allowed to access the requested service: sending a request for more precise location coordinates from the client device; and receiving second location coordinates that are more precise than the first location coordinates based on the request; identifying a second geographical region based on the second location coordinates, wherein the second geographical region is within an area wherein devices are allowed access to the requested service; and based at least in part on determining that the second geographical region is within the first part of the first geographical region, providing a service requested by the service request to the client device. 22 . The method of claim 21 , wherein the first location coordinates comprise first latitude coordinates and first longitude coordinates and the second location coordinates comprise second latitude coordinates and second longitude coordinates. 23 . The method of claim 21 , wherein the second location coordinates comprise more significant digits than the first location coordinates. 24 . The method of claim 21 , comprising: obtaining at least one of the first location coordinates or the second location coordinates from at least one of an origin server, a content delivery network (CDN) server, a client server, a global positioning system (GPS) device, a cell tower triangulation, a wireless fidelity (WiFi) device, a radio frequency identification (RFID) device, a near field communication (NFC) device, or a device based location application program interface (API). 25 . The method of claim 21 , comprising: storing in a cache at least one of a cacheable portion of a uniform resource identifier (URI), wherein the URI comprises at least the first location coordinates, or a query parameter of a uniform resource locator (URL), wherein the URL comprises at least the first location coordinates. 26 . The method of claim 25 , comprising: supplying the requested service from the cache, in response to determining that the requested service corresponds to at least one of cacheable portion of a URI or query parameter of a URL stored in the cache. 27 . The method of claim 21 , wherein: the providing the service requested by the service request to the client device is further based at least in part on verifying subscription information of the client device. 28 . The method of claim 21 , comprising: creating an audit record identifying the service request, a service request time, and the requested service. 29 . A system comprising control comprising: an input/output circuitry configured to: receive a service request from a client device, wherein the service request comprises first location coordinates; and a control circuitry configured to: identify a first geographical region based on the first location coordinates; determine whether devices located in entirety of the first geographical region are allowed access to the requested service; wherein the input/output circuitry is further configured to: based at least in part on determining that: (a) devices in a first part of the first geographical region are allowed to access the requested service, and (b) devices in a second part of the first geographical region are not allowed to access the requested service: send a request for more precise location coordinates from the client device; and receive second location coordinates that are more precise than the first location coordinates based on the request; wherein the control circuitry is further configured to: identify a second geographical region based on the second location coordinates, wherein the second geographical region is within an area wherein devices are allowed access to the requested service; and based at least in part on determining that the second geographical region is within the first part of the first geographical region, provide a service requested by the service request to the client device. 30 . The system of claim 29 , wherein the first location coordinates comprise first latitude coordinates and first longitude coordinates and the second location coordinates comprise second latitude coordinates and second longitude coordinates. 31 . The system of claim 29 , wherein the second location coordinates comprise more significant digits than the first location coordinates. 32 . The system of claim 29 , wherein the control circuitry is configured to: obtain at least one of the first location coordinates or the second location coordinates from at least one of an origin server, a content delivery network (CDN) server, a client server, a global positioning system (GPS) device, a cell tower triangulation, a wireless fidelity (WiFi) device, a radio frequency identification (RFID) device, a near field communication (NFC) device, or a device based location application program interface (API). 33 . The system of claim 29 , wherein the control circuitry is configured to: store in a cache at least one of a cacheable portion of a uniform resource identifier (URI), wherein the URI comprises at least the first location coordinates, or a query parameter of a uniform resource locator (URL), wherein the URL comprises at least the first location coordinates. 34 . The system of claim 33 , wherein the control circuitry is configured to: supply the requested service from the cache, in response to determining that the requested service corresponds to at least one of cacheable portion of a URI or query parameter of a URL stored in the cache. 35 . The system of claim 29 , wherein the control circuitry is configured to: provide the service requested by the service request to the client device, wherein the providing the service requested by the service request to the client device is further based at least in part on verifying subscription information of the client device. 36 . The system of claim 29 , wherein the control circuitry is configured to: create an audit record identifying the service request, a service request time, and the requested service.
Protocols · CPC title
Admission control; Resource allocation · CPC title
Storing data temporarily at an intermediate stage, e.g. caching · CPC title
specially adapted for file transfer, e.g. file transfer protocol [FTP] · CPC title
in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.