Access Control Object Hierarchy for Open Device Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Configuration of physical access control systems is labor-intensive and requires significant manual effort, even for non-physical changes such as schedule updates, limiting flexibility and efficiency.

Innovation Solution

An open architecture communication mechanism using a publish-and-subscribe broker with MQTT protocol supports flexible configuration and operation of access control devices through hierarchical message definitions and objects, enabling third-party application development.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If manual configuration methods are used for physical access control systems, then system reliability is maintained through direct control, but configuration time and labor costs increase significantly

Engineering Contradiction:
Improveconfiguration timeVSAvoidmanual configuration effort
Core Design Contradiction:
Loss of timeVSEase of operation

Solution Approach 1:

The system enables self-service configuration through automated message exchange between devices and applications. Devices automatically publish their configuration data and receive update commands without requiring manual intervention, allowing the system to configure itself autonomously and reduce configuration time and labor costs

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Configuration data is prepared and validated in advance through structured message templates and schemas. The publish-and-subscribe broker pre-processes configuration messages before they reach target devices, ensuring readiness and reducing on-site configuration time while maintaining system reliability

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If proprietary communication protocols are used, then device reliability is ensured through controlled interfaces, but system adaptability and third-party integration are limited

Engineering Contradiction:
Improvethird-party application integrationVSAvoidcommunication architecture
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system implements a universal publish-and-subscribe messaging architecture that serves multiple functions: device configuration, status monitoring, event notification, and third-party integration. This single communication framework replaces multiple proprietary protocols, enhancing adaptability while managing complexity through standardization

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The publish-and-subscribe broker acts as an intermediary layer between diverse devices and applications. It translates between different message formats and device protocols, enabling third-party integration without requiring changes to device complexity or communication architecture

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12554949B2Object hierarchy to support device configuration in physical access control systems
Publication Date: 2026.02.17 TYCO FIRE & SECURITY GMBH
  • US12554949B2 patent drawing
  • US12554949B2 patent drawing
  • US12554949B2 patent drawing

AI summary

Example implementations include a method, apparatus, and computer-readable medium for configuring a device in a physical security system via an open architecture. The device receives a command from an application via a publish-and-subscribe broker. The command includes: a type field indicating the command, a source field indicating the application, a timestamp, and a payload including a list of objects, each object including one or more parameters defined by a field name, a datatype, one or more possible values, and a mandatory status. The device transmits an event message to the application via the publish-and-subscribe broker, the event message includes a type field identifying the event message, a source field identifying the device, a timestamp, and a payload including a type field identifying a type of event.