IP Library Granted Patent US 12,554,949
Granted Patent B2
US 12,554,949 · App. 18/458,584 · Granted Feb 17, 2026

Object hierarchy to support device configuration in physical access control systems

Inventor: Rolando Herrero (Amherst, NH)
Assignee: Tyco Fire & Security GmbH
G06K7/10227
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,554,949
App. No.
18/458,584
Granted
Feb 17, 2026
Kind
B2
Abstract

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.

Claims (34)

1 . A method comprising:

receiving, at a device, a command from an application via a publish-and-subscribe broker, the command including:

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; and

transmitting, from the device, an event message to the application via the publish-and-subscribe broker, the event message including:

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.

2 . The method of claim 1 , wherein the one or more parameters of a first object in the list of objects include a parameter that references a second object defined in the command or in another message.

3 . The method of claim 1 , wherein the list of objects includes an object corresponding to the device, the one or more parameters for the object include a method performed by the device, and the value associated with the parameter indicates which method to perform.

4 . The method of claim 3 , wherein the object corresponding to the device includes additional parameters defining parameters of the method.

5 . The method of claim 1 , wherein the list of objects includes an object corresponding to a configuration of permissions, schedules, or an interface of the device.

6 . The method of claim 1 , wherein the list of objects includes an input configuration or an output configuration that indicates a method to be performed at an input of the device or an output of the device.

7 . The method of claim 1 , wherein the type of event of the event message is an object status event including a code indicating whether an action corresponding to the command was performed on an object.

8 . The method of claim 1 , wherein the type of event of the event message is an object information event including information for an object stored at the device.

9 . The method of claim 1 , wherein the type of event of the event message is an activity report event identifying a change in the device and including an identifier of the device, a type of activity, a timestamp and one or more additional parameters specific to the type of activity.

10 . The method of claim 1 , wherein the event message indicates a periodic heartbeat signal to maintain a session between the device and the application.

11 . A configurable security device, comprising:

one or more non-transitory memories storing computer executable instructions; and

one or more processors coupled to the one or more memories and, individually or in combination, configured to cause the device to:

receive, at the device, a command from an application via a publish-and-subscribe broker, the command including:

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; and

transmit, from the device, an event message to the application via the publish-and-subscribe broker, the event message including:

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.

12 . The configurable security device of claim 11 , wherein the one or more parameters of a first object in the list of objects include a parameter that references a second object defined in the command or in another message.

13 . The configurable security device of claim 11 , wherein the list of objects includes an object corresponding to the device, the one or more parameters for the object include a method performed by the device, and the value associated with the parameter indicates which method to perform.

14 . The configurable security device of claim 13 , wherein the object corresponding to the device includes additional parameters defining parameters of the method.

15 . The configurable security device of claim 11 , wherein the list of objects includes an object corresponding to a configuration of permissions, schedules, or an interface of the device.

16 . A method comprising:

transmitting a command from an application to a device via a publish-and-subscribe broker, the command including:

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; and

receiving an event message from the device at the application via the publish-and-subscribe broker, the event message including:

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.

17 . The method of claim 16 , wherein the one or more parameters of a first object in the list of objects include a parameter that references a second object defined in the command or in another message.

18 . The method of claim 16 , wherein the list of objects includes an object corresponding to the device, the one or more parameters for the object include a method performed by the device, and the value associated with the parameter indicates which method to perform.

19 . The method of claim 16 , wherein the object corresponding to the device includes additional parameters defining parameters of the method.

20 . The method of claim 16 , wherein the list of objects includes an object corresponding to a configuration of permissions, schedules, or an interface of the device.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 31, 2024
From: JOHNSON CONTROLS TYCO IP HOLDING LLP
To: TYCO FIRE & SECURITY GMBH
Reel/Frame 068223/0067 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 23, 2024
From: JOHNSON CONTROLS TYCO IP HOLDINGS LLP
To: TYCO FIRE & SECURITY GMBH
Reel/Frame 068494/0384 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 6, 2023
From: HERRERO, ROLANDO
To: JOHNSON CONTROLS TYCO IP HOLDINGS LLP
Reel/Frame 064805/0031 →
Continuity (1)
Related Publication 20250077806A1 · Mar 6, 2025
References Cited (24)
US 7331049B1 · Jin · 2008 [cited by examiner]
US 8098160B2 · Howarth · 2012 [cited by examiner]
US 9699205B2 · Muddu · 2017 [cited by examiner]
US 9867036B2 · Gopalan · 2018 [cited by examiner]
US 11507568B2 · Michaelis · 2022 [cited by examiner]
US 20100153434A1 · Erickson · 2010 [cited by examiner]
US 20100162268A1 · Thomas · 2010 [cited by examiner]
US 20110102140A1 · McGeachie · 2011 [cited by examiner]
US 20110285502A1 · Steinmetz · 2011 [cited by examiner]
US 20110320550A1 · Lawson · 2011 [cited by examiner]
US 20170214672A1 · Alhalabi · 2017 [cited by examiner]
US 20180300678A1 · Drako · 2018 [cited by examiner]
US 20190095510A1 · Cruise · 2019 [cited by examiner]
US 20200074338A1 · Florentino · 2020 [cited by examiner]
US 20200145820A1 · Hoyer · 2020 [cited by examiner]
US 20210004874A1 · Bur · 2021 [cited by examiner]
US 20240061729A1 · Xiong · 2024 [cited by examiner]
US 20250080614A1 · Herrero · 2025 [cited by examiner]
US 20250109946A1 · Karuppiah · 2025 [cited by examiner]
“MQTT Version 3.1.1,” OASIS Committee Specification, Oct. 29, 2014, pp. 1-76. [cited by applicant]
Bray, T., “RFC8259: The JavaScript Object Notation (JSON) Data Interchange Format,” IETF, Dec. 2017, pp. 1-16. [cited by applicant]
Postel, J., “RFC793: Transmission Control Protocol,” IETF, Sep. 1981, pp. 1-81. [cited by applicant]
Rescorla, E., “RFC8446: The Transport Layer Security (TLS) Protocol Version 1.3,” IETF, Aug. 2018, pp. 1-160. [cited by applicant]
Extended European Search Report issued in corresponding European Application No. EP 24 19 7131 dated Jan. 31, 2025. [cited by applicant]