AVA works in all network conditions, however the performance will vary depending on the network capacity. When the network is clear and traffic is flowing easily, AVA doesn’t intervene therefore no improvement will be observed. But when AVA detects bottlenecks on the network whether on the backbone, inside the home or related to servers overload, it performs HTTP optimization and playback shaping in order to retrieve the data packets faster. The more congested the network or more hops there are to retrieve the content, the higher the performance gained by AVA.
Yes, AVA is compatible with any HTTP-based content, regardless of the content type, streaming protocol (including HTTPS), encoding format, DRM, therefore AVA could accelerate any content on the device. Currently, AVA supports the most popular standards and requires limited integration for proprietary implementations.
AVA is neither, it is a network optimization technology that increases the internet throughput, whatever the encoding or protocol is (HTTP, HLS, MPEG-DASH, etc). That is why AVA can be implemented easily on top of any open or proprietary standard. AVA is a system service that operates as an HTTP proxy and manages in real-time the player’s HTTP requests and received data.
How does AVA compare with existing acceleration solutions? (CDN, Network Operator QoS solutions, etc)
There are many existing techniques to optimize video delivery by making the content available where it matters by deploying an “optimal” CDN infrastructure, using network analytics, or other bandwidth-efficient encoders. AVA is complementary and enhances those solutions to offer even higher video delivery quality to the end-user.
No. AVA requires only a simple integration on the device. No server side dependency.
No, it just downloads the same data faster. At a given video resolution, AVA does not increase the amount of downloaded data.
AVA accelerates the video streaming by taking advantage of underused network capacity and by breaking down large video file requests into smaller ones that are more digestible to the network. By opening multiple smaller persistent TCP connections, it allows the requested data to be retrieved from less congested servers, or transit through less congested routes, which results overall in a distributed load over the network and servers. All in all, AVA helps preventing congestion.
Most any device which runs Linux, Android, Windows, iOS or MAC. For other lower end devices or operating systems please check with us – we might be able to support those too.
What happens if everybody uses AVA? (Can multiple AVA-accelerated devices coexist and still operate well?)
Everybody will see improved performance when streaming on their device. As mentioned before, AVA doesn’t increase data consumption or network load. Only risk is that if AVA makes end user performance so great, people will consume more content at higher resolutions and that might require some more bandwidth.