OTAcast supports gigabyte file sizes and up to 1000s of receivers over a unidirectional link (multicast/broadcast).
Since time is always a critical resource, we wanted to make it as easy as possible to try out. To facilitate this, the OTAcast package contains three different parts:
- The core library consisting of:
- the encoding algorithm which generates equations from a data-file/memory section at the server side (the code to be integrated into, e.g., a firmware management server)
- the decoding algorithm which converts equations back into a data-file/memory section for use on the client side (the code to be integrated into, e.g., the user terminals or IoT devices).
The reference design is a reference implementation which shows how to use the core library in a typical implementation both on the server and client side. The reference design will typically be used as the basis or as a template for the real implementation of OTAcast in your application.
- The stand-alone application, which includes functionality to broadcast a file over an IP network, and receive the file over the IP network. The application is meant to be an easy way to set up an evaluation environment where a server can broadcast a file, and a set of clients can be used to receive it. The stand-alone application is implemented using the The reference design.
To get started quickly we recommend trying first the stand-alone application. It works on any operating system and uses standard IP multicast. Making it possible to easily experiment with OTAcast almost anywhere (WiFi, Ethernet, etc).
So if you can find a few free hours to experiment, get in touch (firstname.lastname@example.org) and we will be happy to provide access and assistance.