Normative reference standards contain provisions that, through reference in this text, constitute normative provisions of this Example Platform Specification. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this specification are encouraged to investigate the possibility of applying the most recent editions of the standards listed below. If the referenced standard is dated, the reader is advised to use the version specified.

In the following reference descriptions, the terms:

• "Compliancy of Example to Standard", and
• "Example Specific Implementation"

are defined as "Yes", or "No".

Compliancy of Example to Standard

Yes → Indicates that Example fully complies to the standard.

No → Indicates that Example is not compliant.

Example Specific Implementation

Yes → Indicates that a specific Example profile is defined, meaning a subset of the standard is defined.

No → Indicates that the standard is used without any specific restriction.

▲ Top

Core Specification

This specification covers several major functions including network configuration, account configuration, etc., and also the following advanced security features:

• Keys and certificates management interface (Section 5.2 - Keystore)
• TLS server configuration interface (Section 5.3 - TLS Server)
• IEEE 802.1X (Section 4.3 - IEEE 802.1X)

Basic security features such as user authentication based on WS UsernameToken and HTTP Authentication as well as a default access policy are specified in the ONVIF Core Specification as part of the device management service.

Standards Body: ONVIF

Reference Number: Version 17.06 June 2017

URL: https://www.onvif.org/specs/srv/security/ONVIF-AdvancedSecurity-Service-Spec-v130.pdf

IPR Status: Free

Compliancy of Example to Standard: Yes

Example Specific Implementation: Yes

Comments: Some aspects may use a very specific profile defined, or even diverge from the specification, mainly in the security area and in the notification section.

▲ Top

Streaming Specification

This standard defines media streaming options and formats and the streaming of Video or JPEG information.

• A distinction is made between media plane and control plane (Streaming - Section 4).
• A set of media streaming (audio, video, and meta data) options (Streaming - Section 4), all based on RTP [RFC 3550] , are described in order to provide interoperable media streaming services.

Standards Body: ONVIF

Reference Number: Version 17.06 June 2017

URL: https://www.onvif.org/specs/stream/ONVIF-Streaming-Spec-v1612a.pdf

IPR Status: Free

Compliancy of Example to Standard: Yes

Example Specific Implementation: No

Comments: N/A

▲ Top

Analytics Service Specification

This specification defines a onfiguration framework for the analytics engine called ONVIF Analytics Service.

• It configures the triggering of events:
  • Motion Detection (Analytics Service - Annex C Motion Detection (normative))
  • Crossing of Virtual Lines (Analytics Service - Section 4 Overview)
• This framework enables a client to contact a device implementing the ONV IF Analytics Service for supported analytics modules and their configurations.
• Configurations of such modules can be dynamically added, removed or modified by a client, allowing a client to run multiple Analytics Modules (Analytics Service - Section 5.3: Analytics Modules Interface) in parallel if supported by the device.

Standards Body: ONVIF

Reference Number: Version 17.06 June 2017

URL: https://www.onvif.org/specs/srv/analytics/ONVIF-Analytics-Service-Spec-v1712.pdf

IPR Status: Free

Compliancy of Example to Standard: Yes

Example Specific Implementation: No

Comments: Need to consider whether we use this program to trigger events.

▲ Top

Device IO Service Specification

The DevideIO service offers commands to retrieve and configure the settings of physical inputs and outputs of a device. The DeviceIO service supports the configuration of the following device interfaces:

• Video Outputs (Device IO - Section 5.2 VideoOutputConfiguration)
• Relay Outputs (Device IO - Section 5.6 Relay Outputs)
• Digital Inputs (Device IO - Section 5.7 Digital Inputs)
• Send and/or Receive serial data communication (Device IO - Section 4 Overview)

Standards Body: ONVIF

Reference Number: Version 17.06 June 2017

URL: https://www.onvif.org/specs/srv/io/ONVIF-DeviceIo-Service-Spec-v1712.pdf

IPR Status: Free

Compliancy of Example to Standard: Yes

Example Specific Implementation: No

Comments: N/A

▲ Top

Imaging Service Specification

The Imaging Service provides configuration and control data for imaging specific properties. WSDL is part of the framework and is provided in the Imaging WSDL file. The service includes the following operations:

• Get and set imaging configurations (exposure time, gain and white balance, for example) (Imaging Service - Section  5.2 Imaging Presets).
• Get imaging configuration options (valid ranges for imaging parameters) (Imaging Service - Section 5.1.1 Parameters).
• Move focus lens including position and move status retrieval (Imaging Service - Section 5.1.1 Focus).
• Configure exposure, contrast, focus etc. (Imaging Service - Section 5.1.1 Exposure).
• Generate events if the image becomes too dark, and imaging presets (Imaging Service - Section 5.1.1 Ir Cut Filter).

Standards Body: ONVIF

Reference Number: Version 17.06 June 2017

URL: https://www.onvif.org/specs/srv/img/ONVIF-Imaging-Service-Spec-v1706.pdf

IPR Status: Free

Compliancy of Example to Standard: Yes

Example Specific Implementation: Yes

Comments: N/A

▲ Top

Media Service Specification

Media configurations construct the encoding of video, audio, etc., and are handled through the media service.

• Media configurations are used to determine the streaming properties of requested media streams as defined in this specification. The device provides media configuration through the media service. (Media Service - Section 4 Overview)
• Real-time video and audio streaming configurations are controlled using media profiles (Media Service - Section 4.1.1 Media Profiles).
• A media profile maps a video and/or audio source to a video and/or an audio encoder, PTZ and analytics configurations (Media Service - Section 4.1.1 Media Profiles).

An ONVIF compliant device supporting the media service presents different available profiles depending on its capabilities (the set of available profiles might change dynamically though).

Standards Body: ONVIF

Reference Number: Version 17.06 June 2017

URL: https://www.onvif.org/specs/srv/media/ONVIF-Media-Service-Spec-v240.pdf

IPR Status: Free

Compliancy of Example to Standard: Yes

Example Specific Implementation: No

Comments: N/A

▲ Top

Media 2 Service Specification

This defines the second generation web service interface for configuration of the so-called media profiles.

• These include the selection of Video and Audio inputs as well as PTZ and Analytics modes and the configuration of Video and Audio encoders (Media 2 - Section 5.12.1 Media Profile).
• It configures metadata associated with encoding (Media 2 - Section 5.12.22 Metadata Configuration).

Standards Body: ONVIF

Reference Number: Version 17.06 June 2017

URL: https://www.onvif.org/specs/srv/media/ONVIF-Media2-Service-Spec-v100.pdf

IPR Status: Free

Compliancy of Example to Standard: Yes

Example Specific Implementation: No

Comments: N/A

▲ Top

PTZ Service Specification

The PTZ model groups the possible movements of the PTZ unit into a:

• Pan/Tilt component (PTZ Service - Section 5.2 PTZ Configuration)
• Zoom component (PTZ Service - Section 5.2 PTZ Configuration)

• It enables the PTZ control of a camera. To steer the PTZ unit, the service provides:
  • AbsoluteMove operations (PTZ Service - Section 5.3.1 AbsoluteMove)
  • RelativeMove operations (PTZ Service - Section 5.3.2 RelativeMove)
  • ContinuousMove operations (PTZ Service - Section 5.3.3 ContinuousMove)
• Different coordinate systems and units are used to feed these operations.

Standards Body: ONVIF

Reference Number: Version 17.12 December 2017

URL: https://www.onvif.org/specs/srv/ptz/ONVIF-PTZ-Service-Spec-v1706.pdf

IPR Status: Free

Compliancy of Example to Standard: Yes

Example Specific Implementation: No

Comments: N/A

▲ Top

Recording Control Service Specification

This standard provides the management of recordings with a set of interfaces that enable the support of interoperable network storage devices, such as:

• Network video recorders (NVR)
• Digital video recorders (DVR)
• Cameras with embedded storage

The following functions are supported:

• Recording Control (Recording Control Service - Section 5 Recording control)
• Search (Recording Control Service - Section 4.1 Storage)
• Replay (Recording Control Service -  Section 4.1 Storage)

Standards Body: ONVIF

Reference Number: Version 17.06 June 2017

URL: https://www.onvif.org/specs/srv/rec/ONVIF-RecordingControl-Service-Spec-v221.pdf

IPR Status: Free

Compliancy of Example to Standard: Yes

Example Specific Implementation: No

Comments: N/A

▲ Top

Recording Search Service Specification

This specification regards the search of metadata and recordings. The search service enables a client to find information about the recordings on the storage device, for example to construct a "timeline" view, and to find data of interest within a set of recordings. The latter is achieved b searching for events and other information that is included in the metadata track recording. The search service provides the following functionality:

• Find recordings and information about each recording (Recording Search Service - Section 4 Overview )
• Find events in the metadata and among the historical events (Recording Search Service - Section 4 Overview)
• Find PTZ positions in the metadata (Recording Search Service - Section 4 Overview )
• Find other information in the metadata, e.g., text from EPOS (electronic point-of-sale) systems (Recording Search Service - Section 4 Overview).

Standards Body: ONVIF

Reference Number: Version 17.06 June 2017

URL: https://www.onvif.org/specs/srv/rsrch/ONVIF-RecordingSearch-Service-Spec-v1706.pdf

IPR Status: Free

Compliancy of Example to Standard: Yes

Example Specific Implementation: No

Comments: N/A

▲ Top

Replay Control Service Specification

This manages the replay of recorded video. The Replay Control Service provides a mechanism for replay of stored:

• Video (Replay Control Service - Section 4 Overview) 
• Audio (Replay Control Service - Section 4 Overview)
• Metadata (Replay Control Service - Section 4 Overview)

This mechanism may also be used to download data from the storage device so that export functionality can be provided. The replay protocol is based on RTSP [RFC 2326] . However because RTSP does not directly support all of the requirements for replay, several extensions have been added to the protocol. In particular, an RTP header extension is defined to allow an absolute timestamp to be associated with each access unit (e.g., video frame), and to convey information about stream continuity.

Standards Body: ONVIF

Reference Number: Version 17.06 June 2017

URL: https://www.onvif.org/specs/srv/replay/ONVIF-ReplayControl-Service-Spec-v1706.pdf

IPR Status: Free

Compliancy of Example to Standard: Yes

Example Specific Implementation: No

Comments: N/A

▲ Top

Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile

This specification regards the X.509 Certificate Structure.

• This specification profiles the format and semantics of
  • Certificate and certificate revocation lists (CRLs) (Internet X.509 Section 4 Certificate and Certificate Extensions Profile)
  • Procedures are described for processing of certification paths in the Internet environment (Internet X.509 Section 3.2. Certification Paths and Trust).
  for the Internet PKI.
• Finally, ASN.1 modules are provided in the appendices for all data structures defined or referenced.

Standards Body: IETF

Reference Number: RFC 5280

URL: https://tools.ietf.org/html/rfc5280

IPR Status: Free

Compliancy of Example to Standard: Yes

Example Specific Implementation: Yes

Comments: N/A

▲ Top

RSTP (Real Time Streaming Protocol)

This speicifcation regards the real time streaming of video.

• The Real Time Streaming Protocol, or RTSP, is an application-level protocol for control over the delivery of data with real-time properties.
• RTSP provides an extensible framework to enable controlled, on-demand delivery of real-time data, such as audio and video.
• Sources of data can include both live data feeds and stored clips.

This protocol is intended to control multiple data delivery sessions (RSTP - Section Abstract), provide a means for choosing delivery channels such as UDP, multicast UDP, and TCP, and provide a means for choosing delivery mechanisms based upon RTP (RFC 1889 ).

Standards Body: IETF

Reference Number: RFC 2326

URL: https://tools.ietf.org/html/rfc2326

IPR Status: Free

Compliancy of Example to Standard: Yes

Example Specific Implementation: No

Comments: N/A

▲ Top

SRTP (Secure Real-time Transport Protocol)

SRTP provides a framework for encryption and message authentication of RTP and RTCP streams (Section 3), and encryption of real time video streaming.

• SRTP defines a set of default cryptographic transforms (Sections 4 and 5).
• It allows new transforms to be introduced in the future (Section 6).
• With appropriate key management (Sections 7 and 8), SRTP is secure (Section 9) for unicast and multicast RTP applications.

Standards Body: IETF

Reference Number: RFC 3711

URL: https://tools.ietf.org/html/rfc3711

IPR Status: Free

Compliancy of Example to Standard: Yes

Example Specific Implementation: No

Comments: N/A

▲ Top

SSL (Secure Sockets Layer Protocol Version 3.0)

The primary goal of the SSL protocol is to provide privacy andreliability between two communicating applications.

• The protocol is composed of two layers.
• At the lowest level, layered on top of some reliable transport protocol (e.g., TCP [RFC 793] ), is the SSL record protocol.
• The SSL record protocol (SSL - Section 5.6 Handshake Protocol) is used for encapsulation of various higher level protocols.
• The SSL encapsulated handshake protocol allows the server and client to authenticate each other and to negotiate an encryption algorithm and cryptographic keys before the application protocol transmits or receives its first byte of data.
• One advantage of SSL is that it is application protocol independent. A higher level protocol can layer on top of the SSL protocol transparently.

Standards Body: IETF

Reference Number: RFC 6101

URL: https://tools.ietf.org/html/rfc6101

IPR Status: Free

Compliancy of Example to Standard: Yes

Example Specific Implementation: No

Comments: N/A

▲ Top

Network Time Protocol Version 4: Protocol and Algorithms Specification

The Network Time Protocol describes how clients devices can synchronize time with time servers.

Standards Body: IETF

Reference Number: RFC 5905

URL: https://tools.ietf.org/html/rfc5905

IPR Status: Free

Compliancy of Example to Standard: Yes

Example Specific Implementation: No

Comments: N/A

▲ Top

Network Time Protocol Version 4: Autokey Specification

The Autokey specification describes how Network Time Protocol messages may be secured to prevent various attacks that would fool the device into having the incorrect time.

Standards Body: IETF

Reference Number: RFC 5906

URL: https://tools.ietf.org/html/rfc5906

IPR Status: Free

Compliancy of Example to Standard: Yes

Example Specific Implementation: No

Comments: N/A

▲ Top

H.264 or MPEG-4 Part 10, Advanced Video Coding (MPEG-4 AVC)

This regards Video Compression. This Recommendation/InternationalStandard was developed in response to the growing need for higher compression of moving pictures for various applications such as videoconferencing, digital storage media, television broadcasting, internet streaming, and communication.

• It is also designed to enable the use of the coded video representation (H.264 - Section 0.2 Purpose) in a flexible manner for a wide variety of network environments.
• The use of this Recommendation | International Standard allows motion video to be manipulated as a form of computer data and to be stored on various storage media, transmitted and received over existing and future networks and distributed on existing and future broadcasting channels.

Standards Body: ISO MPEG

Reference Number: ISO/IEC 14496–10, ITU-T H.264

URL: https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-H.264-201704-I!!PDF-E&type=items

IPR Status: MPEG LA (IP Camera already needs to pay these royalties irrespective of Example).

Compliancy of Example to Standard: Yes

Example Specific Implementation: No

Comments: N/A

▲ Top

JPEG

This regards the compression of still images and consists of five parts.

• Part 1 of JPEG (ISO/IEC 10918-1 | ITU-T Recommendation T.81) specifies the core coding technology and it incorporates many options for encoding photographic images.
• Part 2 defines the compliance testing.
• Part 3 defines a set of extensions to the coding technologies of Part 1, and via an amendment the SPIFF file format was introduced.
• Part 4 focuses on the registration of JPEG profiles, SPIFF profiles, SPIFF tags, SPIFF color spaces, SPIFF compression types, and defines the Registration Authorities.
• Part 5 specifies the JPEG File Interchange Format (JFIF). Without any doubt, it can be stated that JPEG has been one of the most successful multimedia standards defined so far.

Standards Body: JPEG

Reference Number: ISO/IEC 10918, ITU-T T.81, ITU-T T.83, ITU-T T.84, ITU-T T.86

URL: https://jpeg.org/jpeg/

IPR Status: Free

Compliancy of Example to Standard: Yes

Example Specific Implementation: No

Comments: N/A

▲ Top

Yara

The regards pattern matching data in incoming files to filter malware.

• YARA is a tool aimed at (but not limited to) helping malware researchers to identify and classify malware samples.
• With YARA you can create descriptions of malware families (or whatever you want to describe) based on textual or binary patterns.
• Each description, a.k.a rule, consists of a set of strings and a boolean expression which determine its logic.

Standards Body: VirusTotal

Reference Number: N/A

URL: https://virustotal.github.io/yara/

IPR Status: Free

Compliancy of Example to Standard: Yes

Example Specific Implementation: No

Comments: N/A

▲ Top