|
|
ONVIF - Open Network Video Interface
|
|
|
|
|
|
|
|
|
|
|
|
|
Mandatory ONVIF Services - updated September 25th 2011
For a productive usage our ONVIF client expects following services and functionalities:
Services
- ONVIF Device Management Service WSDL, ver 1.2
- ONVIF Event Service WSDL, ver 1.2
- ONVIF Device_IO Service WSDL, ver 1.0
- ONVIF Imaging Service WSDL, ver 2.0
- ONVIF Media Service WSDL, ver 1.2
- ONVIF PTZ Service WSDL, ver 2.0
- ONVIF Remote Discovery Proxy Services WSDL, ver 1.1
Security
- HTTP Authentication Basic
- HTTP Authentication Digest
- RTSP Authentication Basic
- RTSP Authentication Digest
- Web Service OASIS UsernameToken Profile 1.0
- SSL/TSL
ONVIF Remote Discovery Proxy Services ver 1.1
- Bye
- Hello
- Probe
|
|
Additional Version ONVIF 1 Services
- ONVIF Imaging Service WSDL, ver 1.0
- ONVIF PTZ Service WSDL, ver 1.0
Transport
- RTSP/RTP multicast (opt.)
- RTSP/RTP unicast (preferred)
- RTSP/RTP over TCP (opt.)
Data formats and compressions
- MPEG-4 video over RTP according to RFC 3640
- H.264 video over RTP according to RFC 3984
- Event meta data over RTP according to ONVIF specification 2.0
- JPEG pull for NVT's preview (if supported by NVT)
- AAC Hbr Audio
- AAC Lbr Audio
- G.711 ALaw/PCMU Audio
- G.711 uLaw/PCMA Audio
- G.726 Audio
- MPEG Audio (not defined in ONVIF specs)
|
|
|
ONVIF Device Management Service ver 1.2
- GetCapabilities
- GetDeviceInformation
- GetDNS
- GetHostname
- GetNetworkDefaultGateway
- GetNetworkInterfaces
- GetNTP
- SetHostname
- SetNetworkDefaultGateway
- SetNetworkInterfaces
- SetNTP
- GetRelayOutputs (if supported by NVT ver 1.02)
- GetSystemDateAndTime
- SetRelayOutputState (if supported by NVT ver 1.02)
- SetScopes
- SetSystemDateAndTime
- SetSystemFactorySetting
- SystemReboot
ONVIF Event Service ver 1.2
- GetEventProperties (if supported by NVT)
- CreatePullPointSubscription (if supported by NVT)
- PullMessages (if supported by NVT)
- UnsubscribeRequest (if supported by NVT)
ONVIF Device_IO Service ver 1.0
- GetRelayOutputs (if supported by NVT ver 2.0)
- SetRelayOutputState (if supported by NVT ver 2.0)
ONVIF Imaging Service ver 2.0
- GetImagingSettings
- GetOptions
- GetStatus
- SetImagingSettings
- Stop
|
|
ONVIF Media Service ver 1.2
- AddAudioEncoderConfiguration
- AddAudioSourceConfiguration
- AddMetadataConfiguration
- AddPTZConfiguration
- AddVideoEncoderConfiguration
- AddVideoSourceConfiguration
- CreateProfile
- DeleteProfile
- GetAudioSourceConfigurations
- GetAudioEncoderConfigurationOptions
- GetAudioEncoderConfigurations
- GetAudioSources
- GetMetadataConfigurations
- GetProfiles
- GetSnapshotUri
- GetStreamUri
- GetVideoSources
- GetVideoSourceConfiguration
- GetVideoSourceConfigurations
- GetVideoEncoderConfigurationOptions
- GetVideoEncoderConfigurations
- SetAudioEncoderConfiguration
- SetMetadataConfiguration
- SetVideoEncoderConfiguration
ONVIF PTZ Service ver 1.0/ver 2.0
- AbsoluteMove (if PTZ available)
- ContinuousMove (if PTZ available)
- GetConfiguration (if PTZ available)
- GetConfigurationOptions (if PTZ available)
- GetConfigurations (if PTZ available)
- GetNodes (if PTZ available)
- GetPresets (if PTZ available)
- GotoHomePosition (if supported by NVT and PTZ available)
- GotoPreset (if PTZ available)
- SendAuxiliaryCommand (if supported by NVT and PTZ available)
- SetPreset (if PTZ available)
- StopRequest (if PTZ available)
|
|
|
|
|
Known Limitations and Comments
Event Service
We are still looking for a ONVIF video source supporting the event interface (ONVIF Event Service ver 1.2) as described in ONVIF version 2.
We have tested several cameras and encoders based on the new version but this optional function
isn't supported or works not properly. That results in a problem. Reading the state of the inputs
and relay outputs is only defined in the event interface. In addition we can't implement the analytics
without reading the results.
NVTs with malfunction ONVIF implementations
After testing several ONVIF compliant video sources we notified that some manufacturers are
offering a limited and sometimes a malfunction functionality via their ONVIF stacks. Due to this condition we are adding a XML-list called
"ONVIF certificated devices" to access these devices alternatively via our native interface.
JPEG over RTP
Our client doesn't support JPEG over RTP (RFC 2435 - RTP Payload Format for JPEG-compressed Video)
and won't be able to do this in the future. It's nonsense to
transmit large frames separated in small packets over the network. In addition this specification
limits the frame size to 4 MPixels. A faster and reliable JPEG transmission is supported via the native
JPEG-pull and MJPEG video source interfaces inside our client.
|
|
PTZ Control
Especially if you use a joystick don't expect a quick and latency free ptz control via ONVIF. The SOAP protocol needs
up to 20 times more data to be transferred for a ptz command as other interfaces. In addition every command has to
be acknowledged via the video source's web server. This results in less control cycles per second for a
smooth ptz speed control.
Here is a sample:
AXIS ptz control left via native interface:
The same command via ONVIF service:
|
|
|
|
|
ONVIF Distribution Service
Automatic Video Source Configuration and Server Setup
As a part of our management servers the ONVIF Distribution Service
allows a complete and automatic video source and video server setup.
All necessary configurations are processed via ONVIF services.
The management server collects new video sources and do the configuration
via pre-defined properties.
The ONVIF Distribution Service works with
any ONVIF conformant and error-free implemented video source.
The ONVIF Distribution Service works as follows:
Step 1 - Discovery
The video sources are discovered via the ONVIF WS Discovery Service.
Step 2 - Configuration
Based on pre-defined properties the service configures ip-addresses,
locations, stream-profiles and encoder configurations.
Step 3 - Server Setup
The video source configuration will be delivered to the video servers.
Step 4 - Video Server Control
The video server requests the video streams and controls the source via
ONVIF Event, I/O, Imaging and PTZ-services.
Step 5 - Client Notification
The service informs the clients about new available sources.
Step 6 - Localization Setup - GEO
If GEO-informations are defined inside the location field the video
sources are placed interactively inside the GEO Informations System.
Step 7 - Localization Setup - Plans
The video source locations are directly inserted into
native AutoCad(tm) or DXF-files with the opinion to select
the device for a connection. In addition the state (offline,
errors etc.) will be shown dynamically.
|
|
|
|
|
|
|
Free ONVIF Management Tool
Based on our client we offer a free ONVIF Management Tool.
Functionalities
- Device Discovery
- Device Report
- Device Reboot/Factory setting
- IP-Configuration
- Location Setting
- Clock Settings
- Media Profile configuration
- Video Encoder configuration
- Audio Encoder configuration
- Imaging configuration
- PTZ-Control (ONVIF version 1&2)
- Output setting
- Preview (snapshot and audio/video stream)
- RTSP Metadata event interface (ONVIF version 2)
- SOAP Metadata event interface (ONVIF version 2)
- Stream test
The stream test connects up to 8 audio/video streams to test the video source signal quality and performance.
- New security recommendations
The client supports the new security recommendations based on Web Service OASIS UsernameToken Profile 1.0 and SSL.
Supported MPEG-4 Decoders:
ELECARD MPEG-4 Decoder
MAINCONCEPT MPEG-4 Decoder
Supported H.264 Decoders:
ELECARD H.264 Decoder
COREAVC CUDA H.264 Decoder
CYBERLINK H.264 Decoder
MAINCONCEPT/BOSCH H.264 Decoder
MAINCONCEPT H.264 Decoder
Supported Audio Decoders:
MAINCONCEPT MPEG Audio Decoder
MAINCONCEPT Demo AAC Audio Decoder
MICROSOFT ACM Wrapper (for G.711)
SHARP G.726 Decoder
We deliver with this version demo decoders from Elecard and Mainconcept.
Actual version: 1.0.12.66
Download SiONVIFManagement
|
|
ONVIF Management Tool
Event Interface
Stream test
|
|
|
|
|
Open Letter To Paul Ritchie, ONVIF managing director
Dear Paul Ritchie,
As soon as your Open Network Interface Forum was founded in November 2008 by Axis, Bosch and Sony, the ideas of a manufacturer independent standard for digital video technique received a lot of attention and applause within our branch. 310 Onvif-conform products and 236 members later it was possible for me in September 2010 at the security fair in Essen to actually participate in the Onvif plug party in order to see and feel what was the most discussed subject since months by all manufacturers.
Now, my impression upfront: I received the event as a disaster. In a room, much too small and overheated the representatives of camera manufacturers crowed around some Onvif-Clients and watched the attempts to show some video signals on the PC screens.
Unfortunately there wasn’t much to be seen and it almost made the impression that each and every step of the integration was accompanied by hoping and trembling.
An example was provided by the representatives of a big Japanese company whose happiness got almost childish, when, after multiple attempts a stamp sized and pixelated image was to be seen in a video management system.
On and off one could hear accusations why or why not one or the other display was presumably not possible. I could see frustrated manufacturers whose brand new models were not shown on any of the systems.
This is supposed to be Onvif?
Of course all parties involved wore the logo, they are publicized on your web site as conform and should therefore be 100 percent compatible towards each other. And last but not least, the various press releases of your forum about successful inter-operability tests pretended that Onvif is a success story of manufacturer independent communication.
But what does this conformity actually mean? Is it not a test, called „Onvif Conformance Test“, which only requests very minimal demands towards the video sources and is hardly tested for functions within the real environment?
Its existence directly leads to a seal of approval even though not even a smooth image or a control function is expected. How should these sources reliably work on clients, which were excluded from the test?
|
|
An even worse picture was provided by an in-house test. Only one single model, of more than 30 actually available Onvif conform cameras of different manufacturers, could handle the main functions. All the others crashed at parameterizing, forgot the settings after reboot or even denied them. Our test included only real environment Onvif-functions, like the settings of the image quality or the control of the PTZ-function.
One gets the impression, as if the members of your forum are focused too much on withstanding their own Onvif-test, which authorizes them to wear the logo – and therefore loose the actual focus, the practical use of the product on the customer’s side. At the plug party one could hear that finally a new test of larger scope is being developed.
I wish that this new test is more oriented towards possible projects and less towards marketing, even when it is actually two years too late.
This test of course should be imperative and should also include the client side. And I also wish that other systems, like for example the access control will be spared for now the integration into the Onvif-world. On one hand the forum has more than enough to do, what the visit in Essen spectacularly has proven, unfortunately, and on the other hand there are enough standards, like OPC, which have successfully been implemented since many years in our branch. Maybe the work of the OPC-Foundation could also be an example for your organization, how practicing experts act by implementation of an interface and that the marketing only gets a voice after the successful work has been done.
We, as manufacturers of video management systems, would like to have this interface and would be happy, if our large scale projects worked with the help of Onvif at some point as easy as it has been in the analogue times with the RG58-cable. Only then will the point be reached, which for sure Axis, Bosch and Sony have targeted when they founded your forum.
Yours truely
Frank Schille
Managing Director, Schille Informationssysteme GmbH, www.schille.com
|
|
|
|
|
ONVIF and the ONVIF logo are trademarks of ONVIF Inc.
The names of actual companies and products mentioned herein may be the trademarks of their
respective owners.
©2008-2011 Schille Informationssysteme GmbH. All rights reserved.
|
|
Content
ONVIF is a global, open forum of well-known manufacturers of video technic for the development of a standard interface to network video products.
It was founded in 2008 by the companies Axis Communications, Bosch and Sony Corporation.
