Versioning Protocol for Disconnected Access Control Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face challenges in reliably managing configuration data for disconnected remote devices, such as access control devices, as they cannot communicate with a central server, leading to inconsistencies and errors when updating configuration data using manual update devices.

Innovation Solution

Implementing a versioning protocol that allows disconnected remote devices to communicate with manual update devices, determining the latest version of configuration data, and selectively applying updates, ensuring that the most current data is propagated throughout the system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual update devices are used to transport configuration data to disconnected remote devices, then the devices can be configured without network connection, but it becomes unreliable to know what data has been applied and which version is current

Engineering Contradiction:
Improveability to configure disconnected devicesVSAvoidconfidence in configuration data version
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system embeds version information within the configuration data itself before transmission. This preliminary action ensures that when configuration data is transferred via manual update devices, the receiving device can automatically determine whether the incoming data is newer than what it currently holds, eliminating the need to track which devices received which updates.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The disconnected remote device compares the embedded version information against its current configuration version and provides feedback by selectively applying only newer configurations. This automatic feedback mechanism ensures the device always maintains the most current configuration without requiring external verification of what has been applied.

Inventive Principle:
Principle #23Feedback

2Productivity

If multiple manual update devices are used by different users, then configuration can be propagated across multiple devices, but inconsistencies arise when devices have different configuration versions

Engineering Contradiction:
Improvespeed of configuration propagationVSAvoidconsistency of configuration data
Core Design Contradiction:
ProductivityVSStability of the object's composition

Solution Approach 1:

Version information is embedded in the configuration data before distribution to multiple manual update devices. This preliminary tagging allows any device in the chain to determine whether incoming configuration data should be applied, ensuring consistency across all devices regardless of which update device is used.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Each disconnected remote device autonomously determines whether to apply received configuration data by comparing embedded version information with its current version. This self-service capability eliminates the need for centralized coordination or manual tracking, allowing multiple users to propagate configurations independently while maintaining system-wide consistency.

Inventive Principle:
Principle #25Self-service

3Productivity

If configuration data is blindly applied without version control, then updates can be quickly deployed, but errors occur when outdated data overwrites current configurations

Engineering Contradiction:
Improvespeed of configuration deploymentVSAvoidaccuracy of configuration application
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

Version information is embedded within the configuration data before transmission. This preliminary action enables the receiving device to perform a quick version comparison before applying the configuration, ensuring that only newer data overwrites existing configurations and preventing erroneous overwrites while maintaining rapid deployment.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9280365B2Systems and methods for managing configuration data at disconnected remote devices
Publication Date: 2016.03.08 HONEYWELL INTERNATIONAL INC
  • US9280365B2 patent drawing
  • US9280365B2 patent drawing
  • US9280365B2 patent drawing

AI summary

Described herein are systems and methods for managing configuration data. These are particularly directed towards the management of configuration data in disconnected remote devices of a host system. For example, this may be an access control environment having one or more connected access control devices (i.e. devices in communication with a central server), and one or more disconnected access control devices (i.e. devices operating without communication with the central server), the latter being regarded as disconnected remote devices. In overview, the present systems and methods make use of a versioning protocol to allow the reliable distribution of configuration data at the disconnected remote devices, this protocol operating to best ensure the propagation of the most current configuration data.