PSIA_Implementation_IPNC_DM36x

  • 格式:pdf
  • 大小:980.83 KB
  • 文档页数:23
TI DM36x IP Network Camera PSIA Implementation
Document Version 1.0
Physical Security Interoperability Alliance (PSIA) /
Mission:
3
Setup / Demo Instructions for PSIA Demo - 1
1. Add device using the Device Setup Wizard. Password is 9999
2. 3.
• • •
From the Milestone mainscreen, select “DM365 IPNC” Click Setting
Inside the Handler Check for the HTTP request method.
DELETE
Read the ID field from the URI.
Transverse the resource tree and search for the ID matching the request.
2
TI’s PSIA port on the DM36x IPNC
• TI IPNC incorporates basic PSIA IPMedia feature set as well as providing PSIA ready framework for customers to support as many PSIA Services as they need in the future – Based on openly available PSIA reference implementation – Tested with Milestone VMS – Demonstrated at ASIS 2009 Plug-fest (Sep 2009) – Supports the following features:
4
Milestone VMS with TI PSIA IPNC
5
Setup / Demo Instructions for PSIA Demo - 2 4. From taskbar, turn on the recording server
6
Setup / Demo Instructions for PSIA Demo - 3 5. Open the Milestone viewer to play back recorded video.
10
Design Considerations
The PSIA complaint HTTP requests are handled by the Boa Web Server. The URL of the request starts with “/PSIA” specifying that it is a PSIA complaint request. The basic initialization is done for building the trees for all the Service nodes starting with the “Root” node and to add the standard PSIA resources like index, indexr, description and capabilities. The mapping of each Service and the underlying resources with the corresponding handler is done by a “Request Handler” table. The creation and parsing of XML blocks are handled by the APIs as per the reference code released by PSIA.
Click Image Quality to adjust image quality Click Device info to view DM365 IPCamera Device Information Click Motion Detection in setting to see live MJPEG stream.
Based on the resource the corresponding parameters need to be retrieved.
The handler function calls are routed through system server to get the requested parameters to be stored in a structure.
The PSIA is a not-for-profit open industry group which will identify existing and emerging standards relevant to the physical security industry, work to enhance them to support industry requirements, and encourage their adoption by our member companies and the industry. In addition, the group will review and vet specifications that are submitted as open standards. List of Members: /members.html
11
Design Block Diagram
HTTP Request to Boa Web Server
Parse the HTTP Header and populate the request structure with standard header fields like Method, URI, Content_Type, Content_Length etc.
PUT Read the message body and write it to a buffer in the request structure. POST Parse the buffer content using an XML parser and retrieve the parameter values based on the resource name and store these values in a structure.
The Physical Security Interoperability Alliance (PSIA) was founded in February of 2008 with the objective of promoting the interoperability of IP enabled security devices. Participating companies include leaders in the security camera, video management software, access control, system integrator segments of the market.

12
Design Block Diagram Contd…
Create the XML Block being requested with the parameter values received.
Send the response back to the client with the XML Block along with Standard HTTP headers and other API specific parameters.
9
PSIA Spec Overview
PSIA Spec conforms with PSIA Service Model which is based on REST (REpresentational State Transfer) architecture. Device behaviors and configurations of the IP Media Device are grouped into a number of Services and subordinate Resources. PSIA Spec lists a set of HTTP APIs in order to change the device configurations and control the behavior of the IP Media Devices. The Device must support transport of XML via HTTP/1.0 or HTTP1.1 protocol. HTTP requests are made through device’s Web Server and the response contains either XML content or XML response information as defined in the API Spec. Service Model supports four types of HTTP methods: GET, POST, PUT & DELETE
Decode the Uri and parse to get the Service and Resource name.
Resource name field is searched in request handler table in order to get the handler.