ONVIF Core Specification v2.2：开放网络视频接口标准详解

需积分: 16 109 浏览量更新于2024-07-23 收藏 1.65MB PDF 举报

ONVIF Core Specification v2.2 是由开放网络视频接口论坛（ONVIF）制定的一份关键标准，它定义了网络视频接口的基础架构，以便在不同的安全视频监控系统之间实现互操作性。这份文档于2012年5月发布，版本2.2标志着其发展的一个重要里程碑。 ONVIF (Open Network Video Interface Forum) 是一个非盈利组织，致力于推动基于IP的视频监控系统之间的标准化。该规范的核心目标是通过一套统一的标准，确保不同厂商生产的视频设备能在同一个网络环境中无缝集成，提供诸如视频流传输、事件触发、访问控制等基本功能。 v2.2版本的主要内容可能包括以下几个方面： 1. **协议架构**：该版本详细规定了视频监控系统间的通信协议，如如何建立和维护连接，数据包结构，以及错误处理机制。 2. **视频传输**：它涵盖了视频流的编码格式、分辨率、帧率等参数的管理，确保视频质量的一致性和兼容性。 3. **安全措施**：包含用户认证、访问控制和数据加密等方面的指导，保障系统的安全性。 4. **事件管理**：定义了如何检测和响应事件，如运动检测、画面丢失或报警，以及与第三方系统集成的能力。 5. **设备描述和发现**：允许系统自动识别和配置其他设备，便于集成和管理。 6. **服务质量（QoS）管理**：确保视频流在不同网络条件下稳定传输，提供可预测的性能。 7. **版权和许可**：明确声明了文档的使用权限，不允许未经许可进行修改，同时强调了法律责任限制，指出不保证内容的特定用途适用，也不承担侵犯知识产权的责任。 ONVIF Core Specification v2.2 的实施对于视频监控行业至关重要，因为它促进了设备间通信的标准化，降低了集成成本，提升了系统的可靠性和互操作性。随着技术的发展，后续的更新可能会进一步扩展功能，优化用户体验，并与物联网（IoT）和其他智能安全解决方案更好地融合。

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

4.5

Device management

vice management functions are handled through the device service. The device service is

the entry point to all other services provided by a device. WSDL for the device service is

provided in in the Device Management WSDL file. The device management interfaces consist

of these subcategories:

 Capabilities

 Network

 System

 Security

4.5.1 Capabilities

he capability commands allow a client to ask for the services provided by a device and to

determine which general and vendor specific services are offered by the device. The

capabilities are structured per service. This document defines the capability exchange for the

device and the event service. For the other services refer to the respective service

specification:

 Device

o Network

o System

o Security

 Event

The capabilities for the different categories indicate those commands and parameter settings

that are available for the particular service or service subcategory.

4.5.2 Network

he following set of network commands allows standardized management of functions:

 Get and set hostname.

 Get and set DNS configurations.

 Get and set NTP configurations.

 Get and set dynamic DNS.

 Get and set network interface configurations.

 Enable/disable and list network protocols.

 Get and set default gateway.

ONVIF™ – 18 – ONVIF Core Spec. – Ver. 2.2

4.5.

6 System Restore

he 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

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

 Get and set access security policy.

 Handle user credentials and settings.

 Handle HTTPS server certificates.

 Enable/disable HTTPS client authentication.

 Key generation and certificate download functions.

 Handle IEEE 802.1X supplicant certificate

 Handle IEEE 802.1X CA certificate

 IEEE 802.1X configuration

4.6 Event handling

Even

t 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 that a device is recommended to support, see Appendix A. In addition,

for some services, this specification extends the basic notification topics with mandatory

events.

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

4.7 Security

his clause describes network security requirements. This specification defines security

mechanism on two different communication levels:

 Transport-level security

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

5 Web Services framework

All management and configuration commands are based on Web Services.

For the purpose of this standard:

 The device is a service provider.

 The client is a service requester.

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.

b 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].

The service descriptions in the ONVIF specification follow the WS-I Basic Profile 2.0

recommendations.

5.1 Services overview

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 7.

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

http://onvif_host/onvif/device_service

5.1.1 Services requirements

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

service requirements for the different device types are defined in the device type

specifications.

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:

剩余143页未读，继续阅读

普通网友

粉丝: 0
资源:
4

ONVIF Core Specification v2.2：开放网络视频接口标准详解

onvif-pdf_ONVIF_

ONVIF-CORE-SPECIFICATION

onvif-qt-server-client怎么使用

onvif-java-1.0-snapshot.jar

onvif-ipc设备服务端

https://github.com/mhei/onvif-qt-client，该网址无效

https://github.com/alexeyakimov/onvif-qt-client，该网址无效

https://github.com/ossim/onvif-qt-client，该网址无效

https://github.com/ZeWaren/onvif-qt-client，该网址无效

onvif的java类库有哪些

最新资源