Location based access control for content delivery network resources

• US 8,874,750 B2
• Filed: 03/29/2011
• Issued: 10/28/2014
• Est. Priority Date: 03/29/2011
• Status: Active Grant

• Current Assignee: TiVo Corporation (Adeia Inc.)
• Original Assignee: MobiTV Incorporated (Adeia Inc.)
• Inventors: Roseborough, James, Coney, Stephen
• Primary Examiner(s): Tran, Phuc
• Assistant Examiner(s): Rivas, Raul
• Application Number:
  US13/074,989
• Publication Number:
  US 20120254432A1
• Time in Patent Office: 1,309 Days
• Field of Search: 707/7.34, 707 1457- 1458, 707/724, 709/219, 709/226, 4554561-457
• US Class Current: 709/226
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 63/107 wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

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.

Claims

1. A method, comprising:

receiving a resource request from a client, the resource request received at a content delivery network server, the resource request including non-quantized location coordinates and quantized location coordinates;

parsing the resource request to identify quantized location coordinates;

determining whether a location restricted resource is currently available in cache by using the quantized location coordinates,

wherein quantized location coordinates comprise latitude and longitude coordinates having fewer significant digits than the non-quantized location coordinates.

2. The method of claim 1, wherein the location restricted resource is location restricted media content.

3. The method of claim 1, wherein quantized location coordinates and the non-quantized location coordinates are different versions of the same coordinates.

4. The method of claim 1, wherein the quantized location coordinates are included in a cacheable portion of a uniform resource identifier.

5. The method of claim 1, wherein the non-quantized location coordinates are included in a non-cacheable portion of the resource request.

6. The method of claim 5, wherein the non-quantized location coordinates are included in query parameters of a uniform resource locator.

7. The method of claim 1, wherein the quantized location coordinates are used to determine whether the client has access to the location restricted resource when the location restricted resource is available in a content delivery network server cache.

8. The method of claim 1, wherein the content delivery network server contacts an origin server to obtain the location restricted resource when the location restricted resource is not available in a content delivery network server cache, wherein the origin server provides the location restricted resource based on non-quantized latitude and longitude parameters.

9. The method of claim 8, wherein the origin server creates an audit record identifying the resource request, a request time, and the location restricted resource.

10. The method of claim 8, wherein the origin server returns the location restricted resource to the content delivery network server and indicates whether the location restricted resource should be cached.

11. The method of claim 8, wherein the origin server indicates to the content delivery network server that the location restricted resource should be cached if the region defined by the quantized location coordinates falls entirely within a non-restricted zone.

12. The method of claim 8, wherein the origin server indicates to the content delivery network server that the location restricted resource should not be cached if the region defined by the quantized location coordinates falls partially within a non-restricted zone.

13. A system, comprising:

an interface configured to receive a resource request from a client, the resource request received at a content delivery network server, the resource request including non-quantized location coordinates and quantized location coordinates;

a processor configured to parse the resource request to identify quantized location coordinates and determine whether a location restricted resource is currently available in cache by using the quantized location coordinates,

wherein quantized location coordinates comprise latitude and longitude coordinates having fewer significant digits than the non-quantized location coordinates.

14. The system of claim 13, wherein the location restricted resource is location restricted media content.

15. The system of claim 13, wherein quantized location coordinates and the non-quantized location coordinates are different versions of the same coordinates.

16. An apparatus, comprising:

means for receiving a resource request from a client, the resource request received at a content delivery network server, the resource request including non-quantized location coordinates and quantized location coordinates;

means for parsing the resource request to identify quantized location coordinates;

means for determining whether a location restricted resource is currently available in cache by using the quantized location coordinates, wherein quantized location coordinates comprise latitude and longitude coordinates having fewer significant digits than the non-quantized location coordinates.