VODDLER’SVNET IN ACTION

Voddler’s Vnet connects end-user devices

Vnet – How it works

Patentedbalancingalgorithms

A centrally managed but distributed solution

• A small installation on end-user device makes it work like a small edge server, or “node”.

• Nodes communicate in real time and share data between each other.

• Data is distributed in small encrypted slices, complete file never stored at any given place

• Patented balancing algorithms control distribution and replication of slices

• This distribution of data on the network’s true edge significantly reduces costs and improves QoS by shortening data packet routes.

• Each active node is fully controlled by Voddler, stored content is inaccessible to device owner. (Hence the short-hand description of Vnet as ”controlled peer-to-peer”.)

• A full node both receives data and sends forwards. Typical use case: The movie you watch remains partly on your hard drive for further distribution.

• Historically, this has required a ”strong device” (”strong” in sense of hardware, memory, OS and power). ”Weak devices” is then primarily used as receivers (“leechers”) only, unless when the user device signals to Vnet that it has excess capacity or connection speed to share.

• This allows for Vnet implementation on all types of devices (smartphones, phablets, tablets, set-top boxes, routers) in addition to PCs.

Vnet in Action: Playing a movie – 1 (3)

User has clicked Play-button and node starts collecting metadata from its cluster (and other nodes outside of cluster as needed) for that content, loading the first slices to allow movie to start to play

Vnet in Action: Playing a movie – 2 (3)

Movie is playing, node is getting slices from a stable number of active nearby nodes

Vnet in Action: Playing a movie – 3 (3)

User pauses movie; the number of nodes remains for a while as node buffers content

Pull process – true multi-point to point delivery

Cluster group

Playing device

slice = 4MB

chunk = 50KB

Multi-point-to-point delivery of chunks

If time outthen go tofallback

Amazoncloud

HTTPS (slice)

TCP

c1

c2c3

c4

c1

c2c3

c4

User has clicked Play-button and node starts establishing cluster and collect metadata

Cluster established, movie playing, node getting slices from its cluster

User pauses movie; the number of nodes remains for a while as node buffers content