ONVIF应用程序员指南：网络视频接口标准解析

需积分: 50 29 浏览量更新于2024-07-26 收藏 939KB PDF 举报

"ONVIF应用程序员指南" ONVIF（开放网络视频接口论坛）是由Axis Communications、Bosch Security Systems和Sony Corporation于2008年共同创立的开放行业论坛，其目标是标准化网络设备之间的通信，确保安全市场的网络产品间具有互操作性。自成立以来，ONVIF已经发布了多个文档和规范，定义了一个灵活、可扩展且不断进化的接口，该接口规定了如何寻址和利用安全设备。 ONVIF Application Programmer's Guide是针对开发人员的一份关键文档，版本1.0，发布于2011年5月。这份指南详细介绍了如何利用ONVIF标准开发和集成网络视频设备。开发者可以通过这份指南了解到如何与符合ONVIF标准的设备进行交互，包括设备发现、配置、控制、媒体流管理以及事件处理等核心功能。 ONVIF的核心在于定义了一系列的协议和服务，其中包括： 1. 设备发现：ONVIF允许设备通过网络广播自身存在，使客户端能够找到并连接到它们。这通常通过SSDP（简单服务发现协议）和UPnP（通用即插即用）实现。 2. 设备配置：开发者可以使用ONVIF接口来配置设备参数，如视频分辨率、帧率、编码设置等。 3. 媒体服务：ONVIF定义了如何访问和控制视频和音频流。它支持多种编码格式，如H.264、MJPEG和AAC等。 4. PTZ（平移/倾斜/缩放）控制：对于支持PTZ功能的摄像机，ONVIF提供了一套标准化的命令集，使得不同厂商的设备可以统一控制。 5. 事件和报警管理：ONVIF提供了事件订阅和发布机制，使得设备可以报告异常情况，如移动检测或入侵报警，而客户端可以相应地作出响应。 6. 访问控制：ONVIF还涵盖了对设备访问的认证和授权，确保只有经过验证的用户可以进行操作。 7. 系统时间同步：为了确保记录的视频和事件的时间准确性，ONVIF支持NTP（网络时间协议）进行设备间的时钟同步。在使用ONVIF标准时，开发者需要注意的是，虽然ONVIF提供了一个统一的接口，但具体设备的实现可能有所不同。因此，在实际开发中，需要参考设备制造商提供的ONVIF实施细节，以确保兼容性。最后，文档中的版权信息指出，接收者可以复制、分发、发布或展示文档，但必须保留版权通知、许可和免责声明。然而，未经许可，不得修改文档内容。同时，ONVIF及其成员和他们的关联公司不对因使用或分发该文档而产生的任何直接、间接、特殊、附带或惩罚性损害负责。 ONVIF Application Programmer's Guide是开发人员理解和利用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页未读，继续阅读

andrewchiou

粉丝: 0
资源: 2

ONVIF应用程序员指南：网络视频接口标准解析

ONVIF编程指南：伪代码详解开发要点

ONVIF应用程序员指南

ONVIF应用开发者指南1.0版：详解与授权

ONVIF Application Programmer's Guide

ONVIF_WG-APG-Application_Programmers_Guide-1.zip_ONVIF_onvif app

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

onvif开发程序员手册

ONVIF程序员开发向导

ONVIF客户端软件2014 NVC

ONVIF官方应用程序员指南

最新资源