Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

26 Mar

ONVIF PROFILE M

What is ONVIF PROFILE M

Profile M – From ONVIF Website

  • Analytics configuration and information query for metadata
  • Configuration and streaming of metadata
  • Generic object classification support
  • Metadata definition for geolocation, vehicle, license plate, human face and body
  • Event interfaces for object counter, face and license plate recognition analytics
  • Sending events through metadata stream, ONVIF event service or over MQTT
  • Rule configuration for events

ONVIF Profile M supports analytics configuration and information query for metadata, as well as filtering and streaming of metadata. It has interfaces for generic object classification, and specified metadata for geolocation, vehicle, license plate, human face and human body. If conformant products have native support for features such as media profile management, video streaming, adding images in metadata streams, event handling or rule configuration, then Profile M interfaces for those features must also be supported. And if conformant products support analytics for object counting (e.g. for people, vehicles), license plate recognition or facial recognition, or MQTT (Message Queuing Telemetry Transport) protocol used by IoT (Internet of Things) systems, then there should also be Profile M event handling interfaces for those functions.

A Profile M conformant product can be an edge device (such as an IP camera or video-based drone) or a service (such as a server- or cloud-based app) with analytics capabilities that can use Profile M interfaces to send metadata over an IP network to a client. A Profile M conformant client can be a video management software (VMS) program, a network video recorder (NVR), or a server- or cloud-based service that can make use of Profile M interfaces to configure, request and control the streaming of metadata over an IP network from a Profile M edge device or service. Profile M devices or clients with support for MQTT can also communicate with an IoT platform/application that can then communicate with IoT devices and applications.

See the ONVIF Profile Feature Overview v2.6 (April 2022) to get an overview and a comparison of the features supported by all ONVIF profiles, and whether the features are considered mandatory (M) or conditional (C) for a conformant device or client. ONVIF PROFILE M PRESENTATION