ONVIF开发者指南：构建网络视频接口应用

3星 · 超过75%的资源需积分: 50 105 浏览量更新于2024-07-27 收藏 939KB PDF 举报

"ONVIF开发文档，ONVIF_WG-APG-Application_Programmer's_Guide，版本1.0，2011年5月发布，由OpenNetworkVideoInterfaceForumInc.（ONVIF）创作并拥有版权。文档允许在保留版权通知、许可和免责声明的情况下复制、分发、发布或展示，但不允许修改文档。该文档按原样提供，不提供任何明示或暗示的保证，包括但不限于适销性、特定用途适用性、非侵权或所有权的保证。" ONVIF（Open Network Video Interface Forum，开放网络视频接口论坛）是一个国际标准组织，致力于定义网络视频设备的互操作性标准。这个开发文档，即"ONVIF应用程序员指南"（ONVIF WG-APG-Application Programmer's Guide），是针对开发者的一份关键参考资料，旨在帮助他们理解和实现ONVIF协议，以便创建兼容的网络视频产品。 ONVIF的核心是提供一套接口，使不同厂商的网络视频设备（如IP摄像头、录像机等）能够互相通信和共享数据。这些接口定义了设备发现、媒体服务、访问控制、事件管理等多个方面，使得开发者可以构建符合标准的软件或硬件解决方案。文档的"版本1.0"表明这是ONVIF协议的早期版本，可能包含了基础的规范和功能，例如： 1. **设备发现**：ONVIF设备通过网络广播自身存在，其他设备可以通过SSDP（Simple Service Discovery Protocol）来找到它们。 2. **媒体服务**：定义了如何流式传输视频和音频，包括编码、解码、分辨率、帧率等参数的管理。 3. **访问控制**：规定了认证和授权机制，确保只有授权的用户和系统可以访问设备和服务。 4. **事件管理**：允许设备报告状态变化，如运动检测、报警触发等，通过SOAP（Simple Object Access Protocol）进行事件订阅和推送。在开发ONVIF兼容的设备或应用时，开发者需要熟悉这些接口，并遵循文档中的指导实现相应的功能。这包括理解XML（eXtensible Markup Language）用于交换数据，SOAP用于请求和响应，以及可能涉及的网络协议，如HTTP/HTTPS。此外，文档强调了知识产权和责任限制。尽管ONVIF允许自由复制和分发，但对基于文档内容创建的产品或服务可能出现的任何直接或间接损害，ONVIF及其成员和关联公司不承担任何责任。这意味着开发者在利用ONVIF标准进行开发时，必须自己承担可能的风险和后果。 "ONVIF开发文档"是开发ONVIF兼容产品的必备资料，它提供了详细的协议规范和技术指南，帮助开发者构建能够无缝集成到ONVIF生态系统中的网络视频解决方案。

ONVIF

– 16 – ONVIF APG - Ver. 1.0

5 Initial Setup and Administration

5.1

First Actions After Discovery

After ONVIF devices are discovered using WS-Discovery, you would typically access a device

using the supplied XAddrs to test where it is reachable. Use device.GetSystemDateAndTime

to accomplish this because it should not require authentication. You can also consider calling

device.GetDeviceInformation and device.GetCapabilities.

5.1.1 Prerequisites

 Devices must already be discovered.

 At least one valid XAddrs for the device service entry point.

5.1.2 Targeted Services and Technologies

 [ONVIF/Device] and [devicemgmt.wsdl]

5.1.3 ONVIF::ProcessMatch

When processing the list of discovered devices, first do a

device.GetDeviceSystemDateAndTime() call:

 To determine if the device is reachable with the supplied XAddr

 To obtain the device time

 To determine the time offset, which will be used later when authenticating (see Section

6.1, Authentication, for more information)

he following subfunction describes how a ProbeMatch message should be processed. It takes

the following parameter:

 aProbeMatch - A ProbeMatch message received as reaction to a Probe request.

// Try to connect to the device and store the XAddr that works.

// Use GetSystemDateAndTime for checking and to get the time offset.

// Find out information and capabilities etc.

ProcessMatch(aProbeMatch)

{

// For authentication to work, it is important to have

// the same time in device and client so the Created time

// is not off with too much. E.g. 5 seconds.

// device.GetSystemDateAndTime should not require authentication,

// we use that function to check the XAddrs in the ProbeMatch response.

// onvifdev is a placeholder that we populate with valid XAddr,

// authentication info and capabilities etc.

onvifdev = App.createNewDeviceInstance();

device = null;

systemDateAndTime = ONVIF::CheckXaddrsAndGetTime(device, onvifdev, aProbeMatch);

if (!aSystemDateAndTime) {

// No valid response – probably communication or authentication failure!

// Return and try next XAddr

return;

}

// Generate a time offset based on device time

// Either UTCDateTime or LocalDateTime or both should be present.

devicetime = ParseSystemDateAndTime(aSystemDateAndTime);

ONVIF

– 17 – ONVIF APG - Ver. 1.0

// Store time offset in the device place holder for later use

// when creating service objects and handling authentication.

onvifdev.timeoffset = devicetime - time(NULL) - 1;

// Assign desired username and password to be used

// (framework dependant). See chapter 6.1 for details.

App.SetAuthenticationInformation(onvifdev);

ONVIF::UpdateCapabilities(device ,onvifdev);

}

5.1.4 ONVIF::UpdateCapabilities

After you have established a valid way to communicate with the device, use actions such as

GetDeviceInformation, GetCapabilities, and possibly GetSystemLog to obtain state and

capabilities for the device. You also must obtain the URIs for the various services that the device

supports.

Parameters are:

 device – An instance that represents the device service.

 onvifdev – Data object for collecting and combining device-specific information that is

required for various services. For example, storing service URLs that are required for

media, PTZ, or other services.

UpdateCapabilities(device, onvifdev)

{

aDeviceInformation = device.GetDeviceInformation();

// Store/Process interesting stuff from DeviceInformation

onvifdev.model = aDeviceInformation.Model;

onvifdev.serial = aDeviceInformation.SerialNumber;

// Get the capabilities and

// store all or interesting portions of the capabilities.

onvifdev.capabilities = device.GetCapabilities(Category = "All");

// Store the XAddr of the different services - these will be used

// later on when accessing Events and Media service.

onvifdev.devicexaddr = onvifdev.capabilities.Device.XAddr;

onvifdev.eventsxaddr = onvifdev.capabilities.Events.XAddr;

onvifdev.mediaxaddr = onvifdev.capabilities.Media.XAddr;

// Other and future ONVIF devices may have additional services

// If Capabilities/System/SystemLogging is true,

// the log could be interesting.

if (aProbeMatch.capabilities.System.SystemLogging) {

log = device.GetSystemLog(LogType = "System");

App.CheckLog(onvifdev, log);

}

NOTICE:

Service addresses are not fixed. They vary according to the vendor and device,

and might require different handling. Therefore, this information must be

updated dynamically.

剩余200页未读，继续阅读

michael1983_csd

粉丝: 1
资源: 1

ONVIF开发者指南：构建网络视频接口应用

onvif开发程序员手册

Event for ONVIF[中文]

Onvif客户端源码

onvif相关文档

onvif说明文档

onvif中文文档

onvif 中文文档 md

onvif wsdl 文档归档包

Onvif开发介绍

ONVIF开发经验总结

最新资源