ONVIF 1.0开发者英文指南：快速入门与实践

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

ONVIF（开放网络视频接口论坛）开发者指南是针对ONVIF 1.0版本的客户端开发手册，它提供了一套清晰且详细的技术规范，帮助开发者理解和实现基于ONVIF标准的网络视频系统。ONVIF是一种广泛应用于安全监控、智能建筑和物联网领域的通信协议，它定义了设备间通信的标准，以便于设备之间交换视频、音频、控制和其他数据。这份文档主要涵盖以下几个关键知识点： 1. **概述与版权信息**：文档由ONVIF发布，所有版权权益归ONVIF所有，允许接收者在保留版权声明、许可和免责声明的前提下复制、分发、出版或展示此文档，但不允许进行修改。这意味着开发者在使用ONVIF标准时必须遵守相关规定，确保合法合规。 2. **适用范围与责任声明**：ONVIF和其成员及关联方不对文档内容的适配性、特定用途的适用性或是否存在侵犯专利、版权、商标等权利负责。同时，他们明确表示文档“按现状”提供，不承担任何明示或默示的质量保证，包括但不限于商品质量、适合特定目的、无侵权风险以及实施内容不会引发法律问题。 3. **法律责任限制**：开发者在利用ONVIF技术时，无论是否符合协议，都不应期待ONVIF或其成员/关联方对其造成的直接、间接、特殊、附带或后果性损害承担责任。这强调了开发者在使用过程中需要自行承担风险和责任。 4. **技术内容**：虽然具体内容没有详细列出，但指南可能包含如何设计和实现ONVIF兼容的视频客户端，如设备发现、连接管理、视频流传输、事件触发、安全认证等核心功能的编码实现方法。此外，开发者还可能了解到关于服务描述语言(SDP)、媒体描述符(MX)以及其他与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页未读，继续阅读

ericxu_00000

粉丝: 0
资源: 1

ONVIF 1.0开发者英文指南：快速入门与实践

onvif客户端开发

onvif协议开发

Onvif开发框架

ONVIF开发者指南：应用程序员手册

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

gSOAP 2.8.14 开发指南：onvif开发者必备

ONVIF应用开发者指南：最新1.0版本详解

ONVIF应用开发者指南：跨平台程序编写

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

零基础入门编译ONVIF框架指南

最新资源