Verizon Digital Media Services Inc.

Edgecast Networks, Inc.

Verizon Patent and Licensing Inc.

Hayes Kim

Derek Shiell

Robert J Peters

David Andrews

Sergio Leonardo Ruiz

Brian W Joe

James Segil

Vikas Phonsa

Harkeerat Singh Bedi

Walter John Schmidt

Kevin Shen

Donnevan Scott Yeager

Joseph F Einstein

Asynchronous file tracking may include a first process that adds files to a cache and that generates different instances of a tracking file to track the files as they are entered into the cache. A second process, executing on the device, asynchronously accesses one or more instances of the tracking file at a different rate than the first process generates the tracking file instances. The second process may update a record of cached files based on a set of entries from each of the different instances of the tracking file accessed by the second process. Each set of entries may identify a different set of files that are cached by the device. The second process may then purge one or more cached files that satisfy eviction criteria while the first process continues to asynchronously add files to the cache and create new instances to track the newly cached files.

Asynchronous tracking for high-frequency and high-volume storage

A network device receives, from a customer, a customer subscription to a media transformation service; receives, from the customer as a first component of the subscription, data associated with customer media; and receives, from the customer as a second component of the subscription, one or more customer-selected parameters that specify media transformations to be performed upon the customer media. The network device receives, from a client browser, a request for the customer media, and transforms, responsive to receipt of the request from the client browser, the customer media based on the one or more customer-selected parameters to produce a transformed version of the customer media. The network device sends the transformed version of the customer media, via a content delivery network, to the client browser.

Dynamic media transformation service in a CDN

A device can receive streaming content from an origin device. The device can identify a user device to potentially receive the streaming content and an edge device associated with the user device. The device can modify a format of the streaming content based on a format acceptable to the user device. The format of the streaming content can be modified to match the format acceptable to the user device. The device can proactively provide the streaming content to the edge device to cause the edge device to make the streaming content available to be provided for presentation on the user device. The streaming content can be proactively provided to the edge device before the user device requests the streaming content from the edge device.

Proactively providing content for content distribution networks

Some embodiments provide reconfigurable web application firewall (WAF) functionality across a distributed platform. Specifically, the WAF function at each distributed platform server is customizable on a per customer and per inbound message basis. When a server receives an inbound message, the server identities the content or services of which specific customer are implicated by the inbound message. The server screens the inbound message for attacks using a first set of rules and policies defined as part of a production profile from a WAF instance defined by the specific customer while contemporaneously testing the inbound message against a second set of rules and polices defined as part of an audit profile from the same WAF instance. In this manner, the specific customer tests the audit profile rules and policies while still receiving the protections of the production profile rules and policies.

Real-time reconfigurable web application firewall for a distributed platform

Some embodiments provide systems and methods for sandboxing content optimization to occur entirely within a network edge or PoP of a CDN. Some embodiments pass a first request for a first URL to a first back-end at the network edge that is configured to cache an optimized instance of the particular object. When the optimized instance of the particular object is not cached at the first back-end, a second request is issued for a second URL identifying a non-optimized instance of the particular object. The second request resolves internally within the network edge to a second back-end that is configured to cache the non-optimized object. The non-optimized object from the second back-end is optimized and passed to the first back-end. The first back-end caches the optimized instance of the non-optimized object and serves the optimized instance to a requesting end user.

Sandboxing content optimization at the network edge

Growing community of inventors

Porter Ranch, CA, United States of America

Hayes Kim