ONVIF 2008核心规范最新版：详解与授权要点

需积分: 12 37 浏览量更新于2024-07-15 收藏 1.44MB PDF 举报

"ONVIF Core Specification (20.06版) 是由ONVIF（开放网络视频接口论坛）于2020年6月发布的最新标准，它定义了网络视频接口的核心功能和协议规范。该文档提供了关于视频监控系统设备间通信的基础框架，包括视频流传输、安全认证、设备管理和服务描述等关键组件。ONVIF致力于标准化在IP网络环境下视频监控系统的互操作性，使得不同厂商的设备能够无缝连接和协作。该版本的核心规范包含了以下几个要点： 1. **版权与许可**：ONVIF保留所有权利，接收者只能在保留版权通知、许可和免责声明的情况下复制、分发、发布或展示该文档。未经许可，不得修改文档内容。 2. **免责声明**：提供此文档“原样”供使用，ONVIF及其成员和关联公司不作任何明示或默示的保证，包括但不限于适销性、特定用途的适用性、非侵权性或所有权，也不保证文档内容适合任何目的，或者实施这些内容不会侵犯任何专利、版权、商标或其他权利。 3. **责任限制**：无论何种原因，ONVIF及其成员和关联公司不对因使用或分发此文档导致的任何直接、间接、特殊、附带或后果性损失承担责任。 4. **功能与服务**：ONVIF Core Specification涵盖了视频流的实时传输，如H.264、MJPEG等编码格式，以及用户认证机制，如数字证书、用户名/密码等。此外，还包括设备管理功能，如设备发现、配置和状态查询，以及服务描述，用于设备间的服务交互和协调。 5. **兼容性与互操作性**：遵循ONVIF Core Spec的设备可以实现跨厂商的互通性，这对于集成商和系统管理员来说是一项重要的优点，有助于简化部署和管理复杂的安全视频监控网络。 6. **技术细节**：文档深入到协议的具体细节，如XML消息结构、HTTP请求方法、错误处理机制等，这些都是开发者在实现ONVIF兼容解决方案时必须了解的部分。 ONVIF Core Specification 20.06是确保网络视频监控系统标准化、开放性和互操作性的基石，对于行业内的设备制造商、集成商和技术开发者来说，理解和遵循这一规范是实现产品间无缝协同的关键。"

ONVIF™ – 16 – ONVIF Core Spec. – Ver. 20.06

4.5.3 System

The system commands are used to manage the following device system settings:

• Get device information.

• Make system backups.

• Get and set system date and time.

• Factory default reset.

• Upgrade firmware.

• Get system log.

• Get device diagnostics data (support information).

• Reboot.

• Get and set device discovery parameters.

4.5.4 Retrieval of System Information

System Information, such as system logs, vendor-specific support information and

configuration backup images, may be retrieved using either MTOM or HTTP.

The MTOM method is supported by the GetSystemLog, GetSystemSupportInformation and

GetSystemBackup commands. The HTTP method is supported by the GetSystemUris

command; this retrieves URIs from which the files may be downloaded using an HTTP GET

operation.

4.5.5 Firmware Upgrade

Two mechanisms are provided for upgrading the firmware on a device. The first uses the

UpgradeSystemFirmware command to send the new firmware image using MTOM.

The second is a two stage process; first the client sends the StartFirmwareUpgrade command

to instruct the device to prepare for upgrade, then it sends the firmware image using HTTP

POST.

The HTTP method is designed for resource-limited devices that may not be capable of

receiving a new firmware image in its normal operating state.

4.5.6 System Restore

The System Restore capability allows a device’s configuration to be restored from a backup

image. Again two mechanisms are provided. The first uses the RestoreSystem command to

send the backup image using MTOM. The second uses the StartSystemRestore command

followed by an HTTP POST operation to send the backup image.

4.5.7 Security

The following security operations are used to manage the device security configurations:

ONVIF™ – 17 – ONVIF Core Spec. – Ver. 20.06

• Get and set access security policy.

• Handle user credentials and settings.

For further security related aspects refer to the ONVIF Advanced Security Service

Specification.

4.5.8 Storage configuration

Storage configuration data contains the configuration data related to storage (DAS, NAS,

CDMI). For example, CDMI client configuration data contains the server address and user

credential information for a CDMI server. An ONVIF Device can connect to CDMI Server via

standard CDMI protocol, for example, to store and read device configuration data, archive

alarm video, export video, etc. operations.

4.6 Event handling

Event handling is based on the OASIS WS-BaseNotification and WS-Topics specifications.

These specifications allow the reuse of a rich notification framework without the need to

redefine event handling principles, basic formats and communication patterns.

Firewall traversal, according to WS-BaseNotification, is handled through a PullPoint

notification pattern. This pattern, however, does not allow real-time notification. Hence, this

specification defines an alternative PullPoint communication pattern and service interface.

The PullPoint pattern allows a client residing behind a firewall to receive real-time

notifications while utilizing the WS-BaseNotification framework.

A fully standardized event requires standardized notifications. However, the notification topics

will, to a large extent, depend on the application needs. This specification defines a set of

basic notification topics.

WSDL for the event service including extensions is provided in the Event WSDL file.

4.7 Geo Location

Interface to describes the location of the device and its entities. A two level approach allows

to model both outdoor and indoor situations. See Figure 2 for the orientation of the axis. The

position on earth is defined via the angles lon and lat in degrees as well as the hight in

meter.The model is coined ENU for (East, North, Up). The mapping of the coordinate system

is defined by [WGS1984] and the base for GPS.

ONVIF™ – 19 – ONVIF Core Spec. – Ver. 20.06

A typical ONVIF network system does have multiple clients that handle device configuration

and device management operations for numerous devices. Additionally a device providing

services may also act as a client.

Web Services also require a common way to discover service providers. This discovery is

achieved using the Universal Discovery, Description and Integration Registry (UDDI)

specifications [UDDI API ver2], [UDDI Data Structure ver2]. The UDDI specifications utilize

service brokers for service discovery. This specification targets devices while the UDDI model

is not device oriented. Consequently, UDDI and service brokers are outside the scope of this

specification.

According to this specification, devices (service providers) are discovered using WS-

Discovery [WS-Discovery] based techniques. The service discovery principles are described

in section 7.

Web Services allow developers the freedom to define services and message exchanges,

which may cause interoperability problems. The Web Services interoperability organization

(WS-I) develops standard profiles and guidelines to create interoperable Web Services. The

devices and the clients shall follow the guidelines in the WS-I Basic Profile 2.0 [WS-I BP 2.0],

except for Requirement R2729 (ONVIF defines some shared response wrapper names) and

Requirement R2801 (ONVIF references XML Schema 1.1 rather than XML Schema 1.0).

5.1 Services overview

5.1.1 General

An ONVIF compliant device shall support a number of Web Services which are defined in this

and related specifications.

The device management service is the entry point for all other services of the device and

therefore also the target service for the ONVIF defined WS-Discovery behaviour, see chapter

The entry point for the device management service is fixed to:

http://onvif_host/onvif/device_service

5.1.2 Services requirements

An ONVIF compliant device shall provide the device management and event service.

If an ONVIF compliant device supports a certain service, the device shall respond to all

commands defined in the corresponding service WSDL. If the specific command is not

required for that service and the device does not support the command, the device should

respond to a request with the error codes:

env:Receiver,

ter:ActionNotSupported,

see 5.11.2 for the definitions of the error codes.

5.2 WSDL overview

“WSDL is an XML format for describing network services as a set of endpoints operating on

messages containing either document-oriented or procedure-oriented information. The

ONVIF™ – 20 – ONVIF Core Spec. – Ver. 20.06

operations and messages are described abstractly, and then bound to a concrete network

protocol and message format to define an endpoint. Related concrete endpoints are combined

into abstract endpoints (services). WSDL is extensible to allow description of endpoints and

their messages regardless of what message formats or network protocols are used to

communicate” [WSDL1.1].

This specification follows the WSDL 1.1 specification and uses the document/literal wrapped

pattern.

A WSDL document consists of the following sections:

• types – Definition of data types using XML schema definitions.

• message – Definition of the content of input and output messages.

• operation – Definition of how input and output messages are associated with a logical

operation.

• portType – Groups a set of operations together.

• binding – Specification of which protocols that are used for message exchange for a

particular portType.

Note that neither the port and service definitions are used since the ONVIF interface is not

bound to a concrete server instance.

Since the release of WSDL 1.1 the underlying XML schema reference has undergone two

major revisions. This specification defines that the relaxation of the Unique Particle Attribution

rule of XML Schema 1.1 may be used for schema extensibility.

5.3 Namespaces

Prefix and namespaces used in this standard are listed in Table 1. These prefixes are not part

of the standard and an implementation can use any prefix.

Table 1: Defined namespaces in this specification

Prefix Namespace URI Description

http://www.onvif.org/ver10/schema

XML schema descriptions in this

specification.

tds

http://www.onvif.org/ver10/device/wsdl

The namespace for the WSDL device

service.

trt

http://www.onvif.org/ver10/media/wsdl

The namespace for the WSDL media

service.

tev

http://www.onvif.org/ver10/events/wsdl

The namespace for the WSDL event

service.

ter

http://www.onvif.org/ver10/error

The namespace for ONVIF defined

faults.

http://www.onvif.org/ver10/network/wsdl

The namespace used for the remote

device discovery service in this

specification.

tns1

http://www.onvif.org/ver10/topics

The namespace for the ONVIF topic

namespace

The namespaces listed in table 2 are referenced by this standard.

剩余138页未读，继续阅读

yuweifeng2991

粉丝: 2
资源: 4

ONVIF 2008核心规范最新版：详解与授权要点

ONVIF-CORE-SPECIFICATION

ONVIF-Core-Spec-v210.pdf

ONVIF-Core-Specification.zip_ONVIF

onvif-study-data.rar_ONVIF_onvif IPC_onvif gsoap_onvif-study-dat

onvif-pdf_ONVIF_

ONVIF_Core_Specification

ONVIF-Core-Specification-v240.pdf

ONVIF Specifications V250

onvif协议文档

ONVIFspecification_ONVIF_

最新资源