Abstract: Provided is an unobtrusive client verification system with one verification devices having processors that are configured to receive a first request from an unverified client device, generate a random number in response to receiving the first request from the unverified client device, define a set of expressions as a browser challenge problem that evaluates to an answer specified by the random number, encrypt the answer within an answer token, provide the browser challenge problem with the answer token to the unverified client device, receive a second request with a solution to the browser challenge problem and the answer token from the unverified client device, and verify the unverified client device in response to the solution matching the answer that is decrypted from the answer token provided with the second request.

Abstract: Provided is an unobtrusive client verification system with one verification devices having processors that are configured to receive a first request from an unverified client device, generate a random number in response to receiving the first request from the unverified client device, define a set of expressions as a browser challenge problem that evaluates to an answer specified by the random number, encrypt the answer within an answer token, provide the browser challenge problem with the answer token to the unverified client device, receive a second request with a solution to the browser challenge problem and the answer token from the unverified client device, and verify the unverified client device in response to the solution matching the answer that is decrypted from the answer token provided with the second request.

Abstract: Provided is an edge compute platform (“ECP”) for serving optimized content from local cache or from output of a shared customizable function executed by a compute device at the network edge on behalf of different customer content such that the function is not redundantly deployed for different customer content, and is not be executed each time the same variant of the optimized content is requested. The ECP may canonicalize first transformation parameters of a received original request according to a transformation parameter definition of a particular function that is implicated by the original request, may generate second transformation parameters with a different ordering than the first transformation parameters as a result of the canonicalization, may generate a variant of the original file by inputting the second transformation parameters to the particular function, and may provide the variant in response to the original request.

Abstract: Provided is a controller for dynamically balancing load between different servers using different thresholds that are continually modified for each of the servers. The controller may generate a baseline load measure based on load measures received from the different servers, and may configure a first threshold for a first server and a second threshold for a second server based on the load measure at the first server deviating from the baseline load measure by a first amount that is greater than a second amount by which the load measure at the second server deviates from the baseline load measure. The controller may allocate an additional server to distribute first content with the first server in response to first content load at the first server satisfying the first threshold and the same load or a greater load of second content at the second server not satisfying the second threshold.

Abstract: Provided is an intelligent prefetcher for prefetching media content segments following a non-sequential naming convention. The prefetching is initiated in response to a server receiving a user request for a particular segment that is not cached. The server passes the request to an origin. The origin scans metadata of a file from which the particular segment is produced. The scanning identifies time or frame offsets for subsequent segments to be prefetched. The origin constructs the requested segment and includes in the segment header, identifiers corresponding to the offset of each subsequent segment selected for prefetching. The segment passes to the server. The server detects the modified header and generates prefetch requests based on each identifier in the modified header. The server issues the prefetch request to the origin and caches the prefetched segments returned by the origin for distribution in response to subsequent user requests for the prefetched segments.

Abstract: An adaptive congestion control device (“ACCD”) may dynamically optimize network congestion control for different active flows. The ACCD may initiate a first flow that is associated with a first set of flow parameters, may select a first congestion control algorithm from a plurality of congestion control algorithms based on the first set of parameters, and may control transmission of packets for the first flow according to the first congestion control algorithm. While the first flow is active, the ACCD may initiate a second flow that is associated with a different second set of flow parameters, may select a different second congestion control algorithm from the plurality of available congestion control algorithms based on the second set of parameters, and may control transmission of packets for the second flow according to the second congestion control algorithm.

Abstract: Dynamic and selective compression for content caching is provided for improving content delivery over a digital network. The dynamic and selective compression increased server cache size for higher cache-hit ratios that offset delays associated with compressing and decompressing content. The dynamic compression involves switching between an available set of compression tools in order to compress different files with the compression tool that is optimal for that file. The selective compression involves selectively compressing the content or files with the optimal compression tool when at least a threshold amount of space savings is obtained in an acceptable amount of time. Thus, the caching server caches compressed copies of a first set of files compressed with a first compression tool, compressed copies of a second set of files compressed with a different second compression tool, and an uncompressed third set of files.

Abstract: The progressive delivery of targeted secondary content may include determining that primary content requested from a particular distribution point of a distributed platform includes a first tag to integrate targeted secondary content as part of an initial presentation of the primary content, and a second tag to integrate targeted secondary content outside the initial presentation. The progressive delivery may further include modifying the primary content by replacing the first tag so that the primary content and targeted secondary content for the initial presentation (e.g., third-party content associated with the first tag) are provided from the particular distribution point without accessing a third-party content provider, while targeted secondary content outside the initial presentation (e.g., third-party content associated with the second tag) may be selected and provided by one or more third-party content providers as originally specified in the primary content.

Abstract: The embodiments provide systems and methods for efficiently and accurately differentiating requests directed to uncacheable content from requests directed to cacheable content based on identifiers from the requests. The differentiation occurs without analysis or retrieval of the content being requested. Some embodiments hash identifiers of prior requests that resulted in uncacheable content being served in order to set indices within a bloom filter. The bloom filter then tracks prior uncacheable requests without storing each of the identifiers so that subsequent requests for uncacheable requests can be easily identified based on a hash of the request identifier and set indices of the bloom filter. Some embodiments produce a predictive model identifying uncacheable content requests by tracking various characteristics found in identifiers of prior requests that resulted in uncacheable content being served.

Abstract: A two-tier Anycast addressing hierarchy enables deterministic traffic management in an Anycast system. Different locations of the Anycast system advertise a common Anycast cover route comprising a first-tier Anycast address with a first address prefix, and different specific routes comprising a set of second-tier Anycast addresses with a second address prefix, wherein each address of the set of second-tier Anycast addresses falls within the already advertised Anycast cover route, and wherein the second prefix is larger than the first prefix. Domain Name System (DNS) operation can resolve queries to the cover route when normal Anycast operation is desired or can be modified to resolve a subset of queries to a particular second-tier address in order to shift a deterministic amount of traffic based on the resolved subset of queries to a deterministically selected Anycast system location based on the location from which the particular second-tier address is advertised.

Abstract: Some embodiments provide an end-to-end federated CDN solution that assimilates a transparent caching server that is operated by a transparent caching server operator into a CDN that independently operates CDN caching servers. Specifically, the logs from the transparent caching server are assimilated into the CDN by aggregating the logs from the transparent caching server and processing the transparent caching server logs to identify network usage for content of a CDN content provider customer that is delivered by the transparent caching server. The network usage is then combined with the network usage that tracked by the CDN caching servers in order to provide comprehensive report metrics for the content provider customer and to bill the content provider customer for all network usage related to delivering the content provider customer's content irrespective of whether the content was delivered by a transparent caching server or a CDN caching server.

Abstract: A controller may identify a problematic path from several paths over which to route egress traffic from a site, may determine a threshold amount of traffic to shift from the problematic path, and may implement different potential traffic shifts for shifting similar amounts of traffic as the threshold amount. The controller may provide the labels or header values that different nodes in the site may place in the egress traffic in order to control which path is used to distributed that egress traffic. The controller may modify routing policies affecting different Autonomous System numbers, address prefixes, or other routing parameters to select and/or shift egress traffic, that is associated with those routing parameters and that is about equal to the threshold amount of traffic, from the problematic path to a different path.

Abstract: Disclosed is a device for configuring and implementing network security for a connected network node, and for shifting the network security closer to the attack point of origin. In particular, the device may activate attack protections on different Multi-Access Edge Computing (“MEC”) devices that are physically located near or at the attack point of origin. The device may detect an attack signature based on one or more received data packets, and may provide a response with an extended header field, the attack signature, and/or other attack protection instructions. The responses may be passed to an address of a suspected attacker. MEC devices along the network path may detect and receive the responses, and implement attack protections in response. The responses may also be passed to a multicast or broadcast address that the MEC device may use to receive responses.

Abstract: Hybrid pull and push based streaming selectively performs a pull-based distribution of a stream to a first point-of-presence (“PoP”) of a distributed platform having low demand for the stream, and a push-based distribution of the stream to a second PoP of the distributed platform having high demand for the stream. The push-based distribution may be used to prepopulate the second PoP cache with the live stream data as the live stream data is uploaded from an encoder to a source PoP of the distributed platform, and before that live stream data is requested by the second PoP. In doing so, requests for the live stream data received at the second PoP may result in cache hits with the requested live stream data being immediately served from the second PoP cache without having to retrieve the live stream data from outside the second PoP.

Abstract: A controller provides dynamic load distribution in a multi-tier distributed platform. The controller may receive a request at a first Point-of-Presence (“PoP”) with a first set of resources. The first PoP may be part of a distributed platform with several distributed PoPs at different network locations. The controller may classify the requested task with a priority, may determine resource availability, and may dynamically distribute the request by (i) providing the request to the first set of resources in response to classifying the task with a high first priority, and determining the availability of the first set of resources to be less than a threshold, and (ii) providing the request to a second PoP in response to classifying the task with a lower second priority, and determining the availability of the first set of resources to be less than the threshold.

Abstract: Dynamic caching policies and/or dynamic purging policies are provided for modifying the entry and eviction of content to the cache (e.g., storage and/or memory) of a caching server based on the current and past cache performance and/or demand. The caching server may modify or replace a configured policy when cache performance is below one or more thresholds. Modifying the caching policy may change caching behavior of the caching server by changing the conditions that control the content that is entered into cache or the content that is deferred and not entered into cache after a request. This may include assigning different probabilities for entering the same content into cache based on different caching policies. Modifying the purging policy may change eviction behavior of the caching server by changing the conditions that control the cached content that is selected and removed from cache.

Abstract: An Edge Compute Network (“ECN”) may provide compute devices with configurable compute resources at different network edges for selective localized and low latency execution of user-defined operations. A user may provide a set of operations in any of several supported programming languages, and the ECN may create an executable environment that can execute the set of operations using the compute resources of any ECN compute device. A function manager for a compute device may selectively initialize, based on requests to execute the set of operations and an initialization policy, the executable environment so that the set of operations can be directly executed using the compute resources of that compute device upon request. The function manager may also selectively remove initialized executable environments based on compute device resource utilization, executable environment usage, and a removal policy.

Abstract: Provided is an edge key value (“EKV”) store for receiving data from any of network location of a distributed platform, and for distributed a synchronized copy of the data to servers at the network locations where the data is requested regardless of where, how, and when the data is updated. The EKV store may receive a first value for a key at a first storage device of the EKV store based on a message issued by a first user through a first network location, may receive a second value for the key at a second storage device of the EKV store based on a message issued by a second user through a second network location, and may store the second value as a current value for the key by forming a consensus across the storage devices that the second value is the most recent value for the key.

Abstract: Disclosed is a device for configuring and implementing network security for a connected network node, and for shifting the network security closer to the attack point of origin. In particular, the device may activate attack protections on different Multi-Access Edge Computing (“MEC”) devices that are physically located near or at the attack point of origin. The device may detect an attack signature based on one or more received data packets, and may provide a response with an extended header field, the attack signature, and/or other attack protection instructions. The responses may be passed to an address of a suspected attacker. MEC devices along the network path may detect and receive the responses, and implement attack protections in response. The responses may also be passed to a multicast or broadcast address that the MEC device may use to receive responses.

Abstract: Provided is a controller for dynamically balancing load between different servers using different thresholds that are continually modified for each of the servers. The controller may generate a baseline load measure based on load measures received from the different servers, and may configure a first threshold for a first server and a second threshold for a second server based on the load measure at the first server deviating from the baseline load measure by a first amount that is greater than a second amount by which the load measure at the second server deviates from the baseline load measure. The controller may allocate an additional server to distribute first content with the first server in response to first content load at the first server satisfying the first threshold and the same load or a greater load of second content at the second server not satisfying the second threshold.