ONVIF TM
ONVIF Core Specification Version 2.0
Release Notes
November 2010
2008-2010 by ONVIF: Open Network Video Interface Forum. All rights reserved.
Recipients of this document may copy, distribute, publish, or display this document so long as this copyright notice, license and disclaimer are retained with all copies of the document. No license is granted to modify this document.
THIS DOCUMENT IS PROVIDED "AS IS," AND THE CORPORATION AND ITS MEMBERS AND THEIR AFFILIATES, MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTI
CULAR PURPOSE, NON-INFRINGEMENT, OR TITLE; THAT THE CONTENTS OF THIS DOCUMENT ARE SUITABLE FOR ANY PURPOSE; OR THAT THE IMPLEMENTATION OF SUCH CONTENTS WILL NOT INFRINGE ANY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
IN NO EVENT WILL THE CORPORATION OR ITS MEMBERS OR THEIR AFFILIATES BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE OR CONSEQUENTIAL DAMAGES, ARISING OUT OF OR RELATING TO ANY USE OR DISTRIBUTION OF THIS DOCUMENT, WHETHER OR NOT (1) THE CORPORATION, MEMBERS OR THEIR AFFILIATES HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR (2) SUCH DAMAGES WERE REASONABLY FORESEEABLE, AND ARISING OUT OF OR RELATING TO ANY USE OR DISTRIBUTION OF THIS DOCUMENT.  THE FOREGOING DISCLAIMER AND LIMITATION ON LIABILITY DO NOT APPLY TO, INVALIDATE, OR LIMIT REPRESENTATIONS AND WARRANTIES MADE BY THE MEMBERS AND THEIR RESPECTIVE AFFILIATES TO THE CORPORATION AND OTHER MEMBERS IN CERTAIN WRITTEN POLICIES OF THE CORPORATION.
1. Summary
The ONVIF 2.0 release is the second major specification release. It adds a number of new services and extends functionality of existing services to support multiple new feature sets. Interfaces available with 1.02 have been kept fully backward compatible. A small number of maintenance changes have been applied and are described in section 3.
2. New Features
2.1. Device Types
See section 4.4 for an introduction to the new device types and 5.5.1 for their respective service requirements.  The newly defined device types are called network video storage (NVS), network video display (NVD) and network video analytics (NVA).
2.2. Additions to the Device Management Service
To this section features for remote user management and 802.11 network configuration have been added. The IO features have been moved to a new IO service. Devices must continue to support the existing APIs to ensure client side backward compatibility.
2.3. Device IO Service
This newly defined service gathers all physical IO functionality. The service offers commands to retrieve and configure the settings of physical inputs and outputs of a device.
2.4. Receiver Service
The receiver service provides a receiving mechanism as base building block for the NVD, NVS and NVA. A receiver is an object that acts as an RTSP client endpoint. A receiver has a configuration that determines the RTSP endpoint to which it should connect and the connection parameters it should use.
2.5. Display Service
The display service provides the key functionality of the NVD. The service introduces panes, each of which occupies an area of the physical display. The configuration of the pane maps audio inputs and outputs to a video output. The configuration also references a receiver object which receives the data to be displayed. Functions to retrieve and configure the configuration of a pane are provided. A layout defines how these panes are visible on the display (e.g single view or quad view). The service introduces commands to retrieve the current layout of a display and change the layout.
service fault2.6. Recording Control Service
The recording control service enables a client to manage recordings, and to configure the transfer of data from data sources to recordings. Managing recordings includes creation and deletion of recordings and tracks.
2.7. Recording Search Service
This mandatory service for any NVS provides the facilities for information lookup from simple queries for recorded media up to analytics search. The service enables a client to find information about the recordings on the storage device, for example to construct a “timeline” view, and to find data of interest within a set of recordings. The latter is achieved by searching for events that are included in the metadata track of the recording.
2.8. Playback Control Service
The replay service enables a client to play back recorded data, including video, audio and metadata. Functions are provided to start and stop playback and to change speed and direction of the replayed stream. It also enables a client to download data from the storage device so that export functionality can be provided.
2.9. Video Analytics Device Service
This service provides the necessary hooks for establishing media streams or metadata enhanced media streams an NVA.
2.10. Audio Backchannel
In order to support bidirectional audio connections the media service and the streaming specification have been extended.
3. Changes
Find below all errata’s from Version 1.02 to 2.0 applicable to existing APIs in order to improve interoperability. Note that this list does only include those change requests that apply to items that have been part of the specification 1.02.
Errata # Subject CR#
2.1Typo in PathExpr grammar  190 Document reference Clause Sub-Clause Page(s) Line(s) Core 2 Draft 8 15.5.5 238
Change
Replace
[3]PathExpr ::= // ’Prefix ‘:’ SimpleItem‘ NodeTest | //Prefix ‘:’? ElementItem‘ NodeTest
With (And renumber the items below 3)
[3] PathExpr ::= [‘//’Prefix?’SimpleItem‘ | ’//’Prefix?’ElementItem‘ ] NodeTest
[4] Prefix::= NamespacePrefix’:’ | ‘’
The Prefix shall correspond to the /ver10/schema namespace.
Errata # Subject CR#
2.2 Typo in TopicPath grammar  191 Document reference Clause Sub-Clause Page(s) Line(s) Core 2 Draft 8 15.7.3 241
Change
Replace
[4] TopicPath ::= RootTopic ChildTopicExpression* ('//.)?
With
[4] TopicPath ::= RootTopic ChildTopicExpression* ('//.’)?
Errata # Subject CR#
2.3Add Error Code of “UsernameTooShort” 193 Document reference Clause Sub-Clause Page(s) Line(s) Core 2 Draft 8 Section 8.4.4/8.6 105 / 124
Change
Add error code“ter:UsernameTooShort" with description “The username was too short”
to function CreateUsers(in Table 66) and to Table 90( Device service specific fault codes).
Errata # Subject CR#
2.4 MessageDescription uses two expressions SimpleItem and SimpleItemDescription 194 Document reference Clause Sub-Clause Page(s) Line(s) Core 2 Draft 8 - - - -
Change
Replace from “SimpleItem” in the following chapter to “SimpleItemDescription” :
13.4.1 ChangeState
13.4.2 Connection Failed
14.4.1  Decoding error event
15.10.2 G etEventPropertiesResponse
19.20.1 R ecording job state changes
19.20.2 C onfiguration changes
19.20.3 D ata deletion
19.20.4 R ecording and track creation and deletion
20.17 Recording Event Descriptions
A.1.1 Profile
A.1.2 VideoSourceConfiguration
A.1.3 AudioSourceConfiguration
A.1.4 VideoEncoderConfiguration
A.1.5 AudioEncoderConfiguration
A.1.6 VideoAnalyticsConfiguration
A.1.7 PTZConfiguration
A.1.8 MetaDataConfiguration
A.1.10 Relay
A.1.11 PTZ Controller Topics

版权声明：本站内容均来自互联网，仅供演示用，请勿用于商业和其他非法用途。如果侵犯了您的权益请与我们联系QQ:729038198，我们将在24小时内删除。