Though OVStream is meant to be for realtime communication and data transmission, Onwards has widely adopted it into its video products. To provide end to end solutions, Onwards additional layers on OVStream so that it could interoperable with third party video streaming platform.
There are properties that OVStream enables features that are useful for live video transmission.
- OVStream considers separated payload as individual object, so instead of handling 1 video + audio stream. We can use OVStream protocol to carry multiple media streams. Therefore switching video quality and audio tracks while streaming, or disabling audio or video during video conference are all controllable in presentation layer.
- As each information object is transmitted independently, live video streaming with OVStream can be fast start.
- OVStream defines the object size close to MTU of IP network, which allows reduces overhead compares with traditional TV transmission (MPEG-TS) to 10%.
- OVStream, like all other Onwards products, is all written in C language, it is light footprint and runnable on mobile devices and set top box.
- With Onwards knowhow in video streaming, gateway functions in nodes is optional which can serve other devices with traditional streaming protocol.
OVAS converts compressed audio video codec data to standard protocol output, and it is also possible for direct codec output. Therefore there is no need for application developer using OVAS to build special player in order to facilitate OVS technology. Moreover, depends on service, it is possible to allow other device to connect to OVAS enabled device for viewing the OVS transmitted content. All player streaming connections are recorded, and transaction logs will be sent via reporting tunnel for service provider billing records.
As a compliment of CDN provider, OVAS supports Out-of-the-band OVS streaming. Media data from ordinary CDN would be cached and served via OVAS to normally application. In parallel, OVAS signals other devices via OVS to form an overlay network, which becomes the primary CDN of the content. OVAS would first seek cache from other OVAS devices before switching over to backup ordinary CDN network. This cache mechanism vastly reduce the CDN stress and network cost of service provider.
Centralised Monitor and Report
As OVAS access data from Core OS, therefore whenever the device is online, OVAS could report device status in real time to centralised server. Moreover, traditionally there is no way to provide QoS on OTT service, OVAS now allows service provider to obtain information about how users viewing the devices. OVAS allows integration with third party server and application, example would be CWMP over OVS; OVAS can support implementation of existing and future device management standards.
Most of the application developers would not have service platform experts to support them. Building interactive applications which requires real time management of large amount of different users at the same time is an impossible mission. Either the platform is not stable, or the application development time becomes too long. Onwards got the experts to overcome both server side and device side challenges. However, Onwards team understands that the applications using this fascinating technology would be so limited if only developed by Onwards. Hence, instead of building all kinds of applications by ourselves, Onwards introduces the APIs of OVAS, which allows programs for communication between applications on different devices becomes like “Hello World” scripting, also the simple HTTP APIs on server side allows any elementary web developer to review and interact with their users in real time. Everyone says Real Time Communication is the next internet evolution, Onwards transforms the abstract technology to simple programming bearer for everyone with OVAS.
Using OVStream to deploy CDN or for transmitting video would have the below advantages compare with other solutions.
- All transmission messages are encrypted and secured
- QoS of viewers is possible as network and playback conditions can be reported
- No single point of failure, adding and removing node in the network would not affect the other viewers
- Self protect overload mechanism, to maintain a maximum service availability when network is overcrowded
- Simple network setup, which do not need to set up in a dedicated CDN network
- Authentication, invalidation of viewers or content are possible
- System fast start, resilience with network conditional
- OVStream able to make use of all available network interfaces of the node, scalable in all directions