ONVIF device server - What does the library do

ONVIF device server
Introduction
What is ONVIF What does the library do Functionalities supported
User Guide
Implemented requests Important classes Dependencies Basic ONVIF server implementation
Getting Started
How to get the library How to compile
Examples
Server Example Reference Design
Evaluating
Evaluating the library
Contact Us

Basic configurations

RidgeRun offers a solution that can turn any Linux device into a basic non ONVIF compliant device, RidgeRun can extend the ONVIF Device Server to be an ONVIF Profile compliant device (like S profile) depending on customer requirements. It makes use of GStreamer daemon as an example to implement the underlying multimedia functionality (GStreamer Daemon, also called gstd, is a GStreamer framework for controlling audio and video streaming using TCP connection messages) but any API can be used to create the RTSP streams. The modularity offered by the ONVIF server allows the user to easily add new features. It is intended to provide ONVIF support easily, reducing time to market and helping our customers to avoid investing time in dealing with the ONVIF specification implementation.

In its current version, a reduced set of requests of the media and device services are supported in a way that allows the user to have a working stream out of the box. New services and requests can be added based on customer's needs.

Following is an example configuration.

Example configuration

What your team needs to do

The implementation is very simple, the following list contains the necessary implementations that your team need to do:

• The implementation of iNetwork, this one manages the network interfaces the way you want, we currently have an implementation that uses SystemD that can be used in your implementation if you wish.
• The implementation of iSystem only resets and gets the date and time the way you want, we currently also have a generic implementation for Linux systems.
• The implementation of DataSourceDecorator is a class that writes and reads the configuration files, this class is open to implementation in case you want to apply some kind of codification and decodification of the data that is written in the files, we have an example class that applies simple encryption that can be used.
• The implementation of iMediaClient is the one that is in charge of creating and removing the RTSP streams using the data provided by the server, allowing you to have your own implementation, we have an example of an implementation that uses Gstreamer and some Gstreamer plugins developed by RidgeRun.

• Your ONVIF Server is the main class, it instantiates the necessary data that the server needs to function and other data like the firmware version, it also sets the different implementations made by your team so the server can use them.

Implementation of a basic profile S ONVIF server

Licensing

RidgeRun gSOAP license agreement for Commercial Use applies to the RidgeRun ONVIF Server product only and changes to this product can only be made by RidgeRun. RidgeRun offers professional engineering services to extend the library as needed. You can read more about in RidgeRun T&M engineering services. If a customer decided to apply changes to the RidgeRun ONVIF Server product, we advise the customer to contact Genivia to purchase their own License Agreement for Commercial Use as open source conditions will apply to the changed RidgeRun ONVIF server product