Randomized Content Access in Token-Based Delivery Platforms

Abstract

Techniques for randomized content access control in token-based delivery platforms are described herein. In various embodiments, one or more servers hosting a content delivery network receive a request for content from a client device, where the request includes an access token granted to a client associated with the client device. The server(s) obtain a probability of rejection and a randomized probability upon validating the access token and determine whether to reject the request based on comparing the access token and rejected tokens and comparing the probability of rejection and the randomized probability. The server(s) also record the access token to the rejected tokens upon determining to reject the request.

1 . A method comprising:
 at one or more servers including one or more processors and non-transitory memory:   receiving a request for content from a client device, wherein the request includes an access token granted to a client associated with the client device;   obtaining a probability of rejection and a randomized probability upon validating the access token;   determining whether to reject the request based on comparing the access token and rejected tokens and comparing the probability of rejection and the randomized probability; and   recording the access token to the rejected tokens upon determining to reject the request.   
     
     
         2 . The method of  claim 1 , wherein obtaining the probability of rejection includes:
 receiving the probability of rejection configured for the one or more servers.   
     
     
         3 . The method of  claim 2 , wherein the probability of rejection is configured for the one or more servers by a content provider based at least in part on resources provided by the content provider and distributed by the one or more servers. 
     
     
         4 . The method of  claim 2 , wherein the probability of rejection is configured for the one or more servers based on at least in part on statistics provided by the one or more servers. 
     
     
         5 . The method of  claim 1 , wherein obtaining the probability of rejection includes:
 extracting properties from the access token; and   setting the probability of rejection based at least in part on the properties.   
     
     
         6 . The method of  claim 5 , wherein:
 the properties from the access token include a first geographic position; and   setting the probability of rejection includes:
 extracting a second geographic location from the request; and 
 setting the probability of rejection based on the first geographic location and the second geographic location. 
   
     
     
         7 . The method of  claim 5 , wherein the properties include the probability of rejection configured for the client upon granting the access token to the client. 
     
     
         8 . The method of  claim 5 , wherein:
 the properties include an issuance timestamp of the access token; and   setting the probability of rejection includes reducing the probability of rejection in accordance with a timestamp of the request within a threshold from the issuance timestamp of the access token.   
     
     
         9 . The method of  claim 5 , wherein:
 the properties include an issuance timestamp of the access token and an expiration timestamp of the access token; and   setting the probability of rejection includes adjusting the probability of rejection in accordance with a timestamp of the request between the issuance timestamp of the access token and the expiration timestamp of the access token.   
     
     
         10 . The method of  claim 1 , wherein the randomized probability is drawn from a uniform distribution between 0 and 1. 
     
     
         11 . The method of  claim 1 , wherein determining whether to reject the request based on comparing the access token and the rejected tokens and comparing the probability of rejection and the randomized probability includes:
 comparing the access token and the rejected tokens to determine whether the access token exists in the rejected tokens; and   comparing the probability of rejection and the randomized probability to determine whether the randomized probability is less than the probability of rejection.   
     
     
         12 . The method of  claim 11 , wherein determining to reject the request includes:
 rejecting the request upon determining the randomized probability is less than the probability of rejection.   
     
     
         13 . The method of  claim 1 , wherein determining to reject the request includes:
 rejecting the request upon determining the access token exists in the rejected tokens.   
     
     
         14 . The method of  claim 1 , further comprising:
 storing in the non-transitory memory the rejected tokens for a predetermined duration.   
     
     
         15 . The method of  claim 1 , further comprising:
 causing the client device to obtain an updated access token upon rejecting the request.   
     
     
         16 . The method of  claim 1 , wherein rejecting the request causing a frequency of the client requesting an updated access token to be evaluated, and the client is marked in accordance with the frequency deviates from an expected frequency. 
     
     
         17 . The method of  claim 1 , further comprising:
 causing a remote source to aggregate reports of requests being rejected; and   causing the remote source to adjust the probability of rejection based on the aggregated reports.   
     
     
         18 . A non-transitory memory storing one or more programs, which, when executed by one or more servers with one or more processors, cause the one or more servers to:
 receive a request for content from a client device, wherein the request includes an access token granted to a client associated with the client device;   obtain a probability of rejection and a randomized probability upon validating the access token; a   determine whether to reject the request based on comparing the access token and rejected tokens and comparing the probability of rejection and the randomized probability; and   record the access token to the rejected tokens upon determining to reject the request.   
     
     
         19 . The non-transitory memory of  claim 18 , wherein the randomized probability is drawn from a uniform distribution between 0 and 1. 
     
     
         20 . A server comprising:
 one or more processors;   a non-transitory memory;   a network interface; and   one or more programs, stored in the non-transitory memory, which, when executed by the one or more processors, cause the server to:   receive a request for content from a client device, wherein the request includes an access token granted to a client associated with the client device;   obtain a probability of rejection and a randomized probability upon validating the access token; a   determine whether to reject the request based on comparing the access token and rejected tokens and comparing the probability of rejection and the randomized probability; and   record the access token to the rejected tokens upon determining to reject the request.