Device-Specific UI Component Provisioning for Security Sensors

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current ONVIF standards do not effectively reduce development efforts related to the management and maintenance of capabilities for security devices such as video cameras and radar-based sensors, limiting interoperability and efficiency in security systems.

Innovation Solution

A method and system that retrieve a model identifier and firmware version from sensor devices, process a device configuration library to select compatible user interface components, and generate a customized package for provisioning, facilitating the control and operation of these devices through a communication network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If ONVIF standards are used for device interoperability, then product compatibility is improved, but development effort for capability management and maintenance increases

Engineering Contradiction:
Improveproduct compatibilityVSAvoidcapability management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the user interface components into device-specific templates that are independently manageable. Each security device has its own set of UI components defined in configuration files, allowing individual management without affecting other devices. This segmentation reduces overall system complexity while maintaining interoperability across different manufacturers' products.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent uses parameter changes by allowing dynamic selection of UI component sets based on device type, model, and firmware version. The system retrieves device identifiers and automatically selects appropriate UI component parameters from predefined configurations, simplifying capability management through automated parameter adaptation rather than manual configuration.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If manual configuration of each device is performed, then device-specific customization is improved, but time consumption and manual effort increase

Engineering Contradiction:
Improvedevice-specific customizationVSAvoidconfiguration time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-defining device-specific UI component templates and configuration parameters before deployment. These pre-configured templates are stored in the system and automatically retrieved and applied when a security device is detected, eliminating the need for manual configuration time while maintaining device-specific customization.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system performs self-service by automatically detecting device identifiers, retrieving appropriate UI component configurations, and applying the correct settings without human intervention. The automated provisioning process handles device-specific customization independently, reducing manual effort and time consumption while maintaining full adaptability to different device types and models.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11416269B2Method, system and computer program product for serving user settings interface components
Publication Date: 2022.08.16 MOTOROLA SOLUTIONS INC
  • US11416269B2 patent drawing
  • US11416269B2 patent drawing
  • US11416269B2 patent drawing

AI summary

A method, system and computer program product for serving user settings interface components is disclosed. The method includes processing a device configuration library to obtain executable codes for serving a plurality of pre-generated and device-specific user interface components. The method also includes carrying out a selection of a reduced subset of compatible user interface components and available settings, from the plurality of user interface components, as a function of a model identifier for a sensor device and a firmware version installed at the sensor device. The method also includes generating a customized package containing the reduced subset of the compatible user interface components and relevant settings that is served for provisioning at the sensor device.