Generic hardware properties configuration for a fire alarm control panel of fire alarm system

The UI generation device for fire alarm systems simplifies the integration of new hardware by using generic configuration data and automated interface generation, addressing complexity, errors, and scalability issues, enabling efficient and consistent updates.

WO2026234286A1PCT designated stage Publication Date: 2026-11-12TYCO FIRE & SECURITY GMBH
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2026/063525
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-09
Filing Date
2026-05-08
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Conventional methods for adding new hardware to fire alarm systems are complex, time-consuming, prone to errors and inconsistencies, and require manual coding, leading to scalability issues and developer dependency.

Method used

A UI generation device for fire alarm control panels that stores generic configuration data, uses a predefined schema to format and validate data, and dynamically generates user interfaces for new remote devices, reducing the need for manual coding and ensuring consistency and reliability.

Benefits of technology

Simplifies the integration of new hardware, reduces time and effort, ensures consistent user experiences, and allows non-developers to contribute, making the system scalable and cost-effective.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2026063525_12112026_PF_FP_ABST
    Figure EP2026063525_12112026_PF_FP_ABST
Patent Text Reader

Abstract

A user interface (UI) generation device is provided for a fire alarm control panel of a fire notification system having remote devices. The UI generation device includes a memory configured to store configuration data for each remote device type, a predefined schema of the configuration data, and remote device specific profile data. The UI generation device further includes one or more processors configured to format the configuration data in adherence to the predefined schema, detect and remove errors and inconsistencies, and to dynamically generate, based on the configuration data and the remote device profile data, a UI for a new remote device having UI elements that are capable of remotely configuring the new remote device. The UI generation device also includes an application programming interface (API) layer configured to facilitate communication between the memory, the data processing engine, and the UI generator.
Need to check novelty before this filing date? Find Prior Art

Description

P700000PC00GENERIC HARDWARE PROPERTIES CONFIGURATION FOR A FIRE ALARM CONTROL PANEL OF FIRE ALARM SYSTEMCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] The present application claims priority to U.S. Provisional Patent Application Serial No. 63 / 803,248, entitled “GENERIC HARDWARE PROPERTIES CONFIGURATION FOR A FIRE ALARM CONTROL PANEL OF FIRE ALARM SYSTEM” filed on May 9, 2025, the entire disclosures of which is incorporated by reference herein.TECHNICAL FIELD

[0002] Aspects of the present disclosure relate generally to fire alarm systems and, more particularly, to a generic hardware properties configuration for a fire alarm control panel of a fire alarm system.BACKGROUND

[0003] Conventionally, it has been complex and not trivial to add new hardware to a fire alarm system: Traditionally, adding support to fire alarm control panel (FACP) programming software for new hardware requires significant code changes.

[0004] Moreover, adding updates for the new hardware is time-consuming. For example, each time new hardware is introduced to a fire alarm system, developers must manually code the necessary support for the new hardware.

[0005] Further, the manual coding of user interface (UI) elements for new hardware can lead to inconsistencies and errors. In this way, different user interfaces may include inconsistent information for the same of similar devices, which is undesirable.

[0006] Also, the addition of new hardware can result in scalability issues. For example, as the variety of hardware increases, maintaining and updating the software becomes more challenging.

[0007] Additionally, the addition of new hardware can result in developer dependency. For example, non-developers often struggle to add new hardware support due to the need for coding knowledge.P700000PC00SUMMARY

[0008] The following presents a simplified summary of one or more aspects to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0009] In an aspect, a user interface (UI) generation device is provided for a fire alarm control panel of a fire notification system having remote devices. The UI generation device includes one or more memory devices configured to store generic configuration data for each remote device type, a predefined schema that outlines expected fields and expected data types of the generic configuration data, and remote device specific profile data for the remote devices. The UI generation device further includes a data processing engine configured to format the generic configuration data in adherence to the predefined schema to generate parsed generic configuration data, and detect and remove errors and inconsistencies from the parsed generic configuration data to generate parsed and valid generic configuration data. The UI generation device also includes a UI generator configured to dynamically generate, based on the parsed and valid generic configuration data and the remote device profile data, a UI for a new remote device having UI elements that are capable of remotely configuring the new remote device. The UI generation device additionally includes an application programming interface (API) layer configured to facilitate communication between the memory device, the data processing engine, and the UI generator.

[0010] In an aspect, a method is provided for generating a user interface (UI) for a fire alarm control panel of a fire notification system having remote devices. The method includes storing, in one or more memory devices, generic configuration data for each remote device type, a predefined schema that outlines expected fields and expected data types of the generic configuration data, and remote device specific profile data for the remote devices. The method further includes formatting, by a data processing engine, the generic configuration data in adherence to the predefined schema to generate parsed generic configuration data. The method also includes detecting and removing, by the data processing engine, errors and inconsistencies from the parsed generic configuration data to generate parsed and valid generic configuration data. The method additionally includesP700000PC00dynamically generating, by a UI generator based on the parsed and valid generic configuration data and the remote device profile data, a UI for a new remote device having UI elements that are capable of remotely configuring the new remote device.

[0011] To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The disclosed aspects will hereinafter be described in conjunction with the appended drawings, provided to illustrate and not to limit the disclosed aspects, wherein like designations denote like elements, and in which.

[0013] FIG. 1 is a block diagram showing a fire notification system 100 having a remote device user interface (UI) generator for generating a remote device UI, in accordance with an example aspect.

[0014] FIG. 2 is a block diagram showing the remote device user interface generator of FIG.1, in accordance with an exemplary aspect.

[0015] FIG. 3 is a block diagram showing a representation of remote device UI of FIG. 1, in accordance with an exemplary aspect.

[0016] FIG. 4 is a block diagram showing a representation of remote device UI of FIG. 1 corresponding to a selection of software settings in FIG. 3, in accordance with an exemplary aspect.

[0017] FIG. 5 is a block diagram showing a representation of remote device UI of FIG. 1 corresponding to a selection of hardware settings in FIG. 3, in accordance with an exemplary aspect.

[0018] FIG. 6 is a block diagram showing a representation of remote device UI of FIG. 1 corresponding to a selection of UI settings in FIG. 3, in accordance with an exemplary aspect.P700000PC00

[0019] FIG. 7 is a block diagram showing a representation of the remote device UI 111 A of FIG. 1 corresponding to a selection of UI options in FIG. 3, in accordance with an exemplary aspect.

[0020] FIG. 8 is a block diagram showing a representation of the remote device UI of FIG. 1 corresponding to the update mechanism of FIG.2, in accordance with an exemplary aspect.

[0021] FIG. 9 is a block diagram showing a representation of the remote device UI of FIG. 1 corresponding to the version control component of FIG. 2, in accordance with an exemplary aspect.

[0022] FIG. 10 is a block diagram showing a representation of the remote device UI of FIG.1 corresponding to the data encryption system 220 of FIG. 2, in accordance with an exemplary aspect.

[0023] FIG. 11 is a block diagram showing a representation of the remote device UI of FIG.1 corresponding to the authentication and authorization system 221 of FIG. 2, in accordance with an exemplary aspect.

[0024] FIGS. 12-13 are a flow diagram showing an example method for generating a user interface (UI) for a fire alarm control panel of a fire notification system having remote devices, in accordance with an example aspect.

[0025] FIGS. 13-14 are flow diagrams showing further blocks of the method of FIGS. 12-13, in accordance with an exemplary aspect.DETAILED DESCRIPTION

[0026] Aspects of the present disclosure are directed to a generic hardware properties configuration for a fire alarm control panel of a fire alarm system.

[0027] Conventional user interface (UI) generation for a remote device such as a smoke detector in a fire alarm system involved manually coding each of the constituent UI elements which was no trivial task but instead burdensome, time-consuming, and error and inconsistency prone.

[0028] Various aspects of the present disclosure overcome the aforementioned deficiencies of conventional UI generation with an automated approach as described herein below.

[0029] Various aspects of the present disclosure meet several needs in the context of fire alarm control panel (FACP) programming software, some of which are listed as follows.P700000PC00

[0030] Ease of Integration: Aspects of the present disclosure simplify the process of integrating new hardware (remote devices) into the system (fire alarm system). Developers and nondevelopers alike can add support for new hardware by updating configuration data, without needing to write extensive new code.

[0031] Speed and Efficiency: By reducing the time and effort required to support new hardware, aspects of the present disclosure allow for quicker updates and faster deployment, ensuring that the system can keep up with the latest hardware advancements.

[0032] Consistency and Reliability: Automatically generating the user interface (UI) based on configuration data ensures a consistent and reliable user experience. This reduces the risk of errors and inconsistencies that can arise from manual coding.

[0033] Scalability: As the variety of hardware expands, the fire notification system can easily scale to accommodate new devices without significant overhauls. This makes the software more adaptable to future needs.

[0034] Accessibility: Non-developers can contribute to the system by updating configuration data, making the process more inclusive and reducing dependency on specialized coding skills.

[0035] Cost-Effectiveness: By streamlining the process of adding new hardware, aspects of the present disclosure can reduce development costs and resource allocation, making it a more cost-effective solution for maintaining and updating FACP programming software.

[0036] Referring now to FIG. 1, a fire notification system 100, also referred to as “a fire alarm system,” is shown, in accordance with an example aspect. Fire notification system 100 is a system for providing notification in the case of a fire.

[0037] In accordance with various aspects of the disclosure, fire notification system 100 includes a fire alarm control panel (FACP) 110 connected to remote devices 120 by fire notification system wiring 130.

[0038] FACP 110 can be considered as a local control center of fire notification system 100 in that remote devices 120 are in signal communication with and “report” to FACP 110 so that one or more actions may be performed by FACP 110 in response to, for example, the reporting of an outbreak of a fire by one or more of remote devices 120. In an aspect, one or more actions that may be performed by FACP 110 include reporting the outbreak of a fire (and / or other emergency condition) to a remote location (e.g., a remote control center,P700000PC00a local fire alarm station, and / so forth). In an aspect, the one or more actions that may be performed by FACP 110 include initiating a response and / or action by another system in signal communication with the FACP 110 such as a fire suppression system. The performance of actions by FACP 110 and the reporting of the occurrence of an emergency by at least one of remote devices 120 can be based on one or more on-board algorithms of FACP 110.

[0039] In an aspect, FACP 110 includes a remote device user interface (UI) generator 111 for generating a remote device UI 111 A for a new remote device 120 A to be added or that was just added to fire notification system 100. In an aspect, remote device UI generator 111 is implemented by one or more processors configured to perform remote device UI generation, e.g., via executing software corresponding to remote device UI generator 111. Remote device UI generator 111 generates a remote device UI 111 A specific to new remote device 120A to enable data exchange between FACP 110 and new remote device 120A. In an aspect, the remote device UI 111A is programmable to include settings and other configuration data corresponding to new remote device 120 A so that new remote device 120 A can operate as intended (including at least periodically checking itself for faults and if a fault exists, reporting the fault to FACP 110) and can exchange information with FACP 110. For example, new remote device 120A may receive instructions and configuration information from FACP 110 via remote device UI 111 A. In an aspect, at least some generic configuration data (that is, expected to be common to all models of a particular type of remote device) is provided to the new remote device 120A from data stored with respect to remote device UI generator 111. In this way, essentially a template of expected functions performed by new remote device 120 A and values for those functions, at least some of which represented by the generic configuration data, can be readily generated and populated to easy integrate new remote device 120A into fire notification system 100.

[0040] In an aspect, FACP 110 further includes one or more connection ports 112 for connecting to an external device (e.g., a tablet, a diagnostic device, and so forth), one or more input / output (VO) devices 113 for receiving user inputs and providing system outputs, a transceiver 114 for wireless receiving and transmitting information, for example, to a remote fire notification system with respect to fire notification system 100, one or more speakers 115 for confirming receipts of inputs / commands and reporting fire notification system 100 data, a microphone 116 for receiving verbal commands, one or more lightP700000PC00sources (light emitting diodes, etc.) 117 for confirming receipts of inputs / commands and reporting fire notification system data.

[0041] In various aspects, one or more I / O devices 113 may include one or more of, e.g.: a display, e.g., having capacitive touch capability; a keypad for receiving inputs representing characters in a set; a keyboard, e.g., a QWERTY keyboard, for receiving inputs representing characters in a set (including, e.g., letters, numbers, punctation, special characters) as well as commands and so forth; a mouse for receiving motion inputs corresponding to a position on a grid of a display and / or a selection of an item corresponding to traversed position on the grid; a camera for capturing facial images for authorization and authentication and / or gestures representing, e.g., commands and / or data (e.g. raising an arm means raising the input value to the system and lowering an arm means lowering the input value to the system); a joystick for receiving motion inputs corresponding to a position on a grid of a display and / or a selection of an item corresponding to traversed position on the grid; and so forth). In an aspect, a capacitive touch capable display of input / output devices 113 may also implement at least part of a system UI 100 A and at least part of remote device UI 111 A.

[0042] In an aspect, FACP 110 includes one or more memories 118, individually or in combination, having instructions. The fire alarm control panel includes one or more processors 119 each coupled to at least one of the one or more memories 118 and configurable to execute the instructions. The one or more memories 118 and the one or more processors 119 implement remote device UI generator 111 as described in further detail herein.

[0043] As used herein, a processor, at least one processor, and / or one or more processors, individually or in combination, configured to perform or operable for performing a plurality of actions is meant to include at least two different processors able to perform different, overlapping or non-overlapping subsets of the plurality actions, or a single processor able to perform all of the plurality of actions. In one non-limiting example of multiple processors being able to perform different ones of the plurality of actions in combination, a description of a processor, at least one processor, and / or one or more processors configured or operable to perform actions X, Y, and Z may include at least a first processor configured or operable to perform a first subset of X, Y, and Z (e.g., to perform X) and at least a second processor configured or operable to perform a second subset of X, Y, and Z (e.g., to perform Y and Z). Alternatively, a first processor, a second processor, and a thirdP700000PC00processor may be respectively configured or operable to perform a respective one of actions X, Y, and Z. It should be understood that any combination of one or more processors each may be configured or operable to perform any one or any combination of a plurality of actions.

[0044] Remote devices 120 include devices capable of detecting a fire or other emergency condition and relaying audible, visible, or other stimuli to alert building occupants of the fire or other emergency condition. For example, a remote device 120 can include, but is not limited to, any of the following: a smoke detector; a heat detector; a speaker; a microphone; a buzzer; a fire alarm switch (e.g., a pull switch); a light (e.g., LED); a relay; and so forth

[0045] Remote devices 120 can include a light notification module and a sound notification module. The light notification module can be implemented as a light emitting device or any component in remote devices 120 that alerts occupants of an emergency by emitting a visible light signal. In some aspects, remote devices 120 emit strobe flashes to alert building occupants of an emergency situation. A sound notification module can be a speaker or any component in remote devices 120 that alerts occupants of an emergency by emitting an audible signal. In some aspects, which should not be construed as limiting, remote devices 120 may emit one or more audible signals.

[0046] Remote devices 120 may be powered by an AC or DC power source. In an aspect, power may be received by at least some remote devices 120 using notification system wiring 130. In an aspect, power may be received by at least some remote devices 120 locally (e.g., from DC batteries and / or an AC receptable and / or an AC junction box). In an aspect, notification system wiring 130 may permit one-way (remote devices 120 to FACP 110) or preferably two-way (remote devices 120 to FACP 110 and FACP 110 to remote devices 120) communications. In a two-way communication approach, remote devices 120, in addition to reporting various statuses (e.g., normal, fault, tripped, etc.) to FACP 110, may receive configuration information from FACP 110 that specifically enables certain selections of certain values and / or functions for operation of remote devices 120.

[0047] In an aspect, notification system wiring 130 is configured to at least enable data (e.g., system status) to be received from remote devices 120 by FACP 110 for further action. In an aspect, further action by FACP 110 may include reporting a system status to a remote location and / or initiating corrective action (e.g., fire suppression) by another system. In an aspect, further action by FACP 110 may be implemented based on and in accordance withP700000PC00one or more stored algorithms in FACP 110 that provide various responses to various input cases (e.g., different combinations of remote devices 120 being actuated). In an aspect, notification system wiring is configured to provide both data and power to remote devices 120 and receive data from remote devices 120.

[0048] New Remote device 120A

[0049] In an aspect, remote devices 120 include a new remote device 120 A to be added or that was just added to fire notification system 100. New remote device 120A may be “new” to FACP 110 in that new remote device 120A may be another device identical to (e.g., same make and model) an existing device of the fire notification system 100, another device similar (same or different make but similar model) to an existing device of the fire notification system 100 or another device completely different (e.g., of a different type) than any existing devices of the fire notification system 100.

[0050] In an aspect, new remote device 120A is “registered with” (as explained more fully below) and / or otherwise integrated into fire notification system 100 by having a remote device UI generated in FACP 110 to enable fire notification system 100 and / or a user to interact with new remote device 120A once new remote device 120A is physically installed (physically connected to a power and data line(s)), to then become referred to simply as a remote device 120 once registered. “Registered” refers to a remote device 120 that is physically connected to a power line and a data line (in an aspect, the power line and the data line can be the same line) and has a remote device UI 111A generated for it. In an aspect, the remote device UI 111 A may be displayed separately from or within system UI 100A. For example, in an aspect, a separate display such as a capacitive-based touch capable display may be used for remote device UI 111 A. In an aspect, another capacitivebased touch capable display may be used for system UI 100A. In an aspect, remote device UI 111 A may be displayed in a fixed or variable portion or section of system UI 100A.

[0051] New remote device 120A needs to be “registered” with fire notification system 100 through FACP 110. New remote device 120A is registered with fire notification system 100 via FACP 110 so fire notification system 100 is made aware that new remote device 120 is to be part of fire notification system. Once registered, new remote device 120A may be checked at least periodically to ensure data communication integrity between FACP 110 and new remote device 120 A.P700000PC00

[0052] In an aspect, registration may be considered as the process of physically connecting new remote device 120 A to power and data and enabling new remote device 120 A and FACP 110 to communicate with each other. In an aspect, registration may involve a user or a device (e.g., a tablet, etc.) providing inputs to system UI 100A indicating a new remote device 120A is to be added or was just added to fire notification system 100 (e.g., physically connected to FACP 110 via fire notification wiring 130). In an aspect, a user or a device (e.g., a tablet) may provide inputs to system UI 100A or remote device UI 111A such as entering a make and model using a keyboard (e.g., physical and / or virtual) to initially register and start a configuration process for new remote device 120A on at least FACP 110. In an aspect, a user may provide inputs on system UI 100A or remote device UI 111 A such as entering part or all of generic configuration data for use by remote device user interface (UI) generator 111 to generate a device specific remote device UI 111 A for new remote device 120 A. In an aspect, the inputted generic configuration data may be retained and stored and optionally replaced as new data becomes available in the case of limited space and / or obsoletion of a particular remote device 120 to build a database of generic configuration data.

[0053] In an aspect, generation of remote device UI 111 A by remote device UI generator 111 may involve creating a shell or template having similar data types and fields as a same or similar device (e.g., of the same type, e.g., smoke detector versus heat detector, etc.) but with device specific ranges and / or specific values for new remote device 120 A to ensure correct and expected functionality as different remote devices will have specific differences that can be captured by representative generic configuration data for the different remote devices.

[0054] Referring now to FIG.2, remote device user interface generator 111 of FIG. 1 is further shown, in accordance with an exemplary aspect.

[0055] As noted above, in an aspect, FACP 110 includes remote device UI generator 111.Remote device UI generator Ill is configured to make it easy for a technician or other user to generate a remote device UI 111 A for a new remote device 120A, that is, a device to be added to (registered with) fire alarm notification system 100 as one of remote devices 120.

[0056] In various aspects, remote device UI generator 111 has various display portions for displaying various items relating to remote device UI generator 111 and hence the various functions of remote devices 120.P700000PC00

[0057] In an aspect, remote device UI generator 111 includes one or more processors (e.g., one or more processors 119 of FIG. 1) and one or more memories (e.g., one of more memories 118 of FIG. 1) operatively coupled to the one or more processors. In an aspect, at least one of the one or more memories 118 has instructions (e.g., program code) and at least one of the one or more processors 119 is coupled to at least one of the one or more memories 118 and configurable to execute the instructions. The instructions can be, for example, based on method 1200 of FIGS. 12-14. In an aspect, elements of remote device UI generator 111 are implemented by one or more memories 118 and / or one or more processors 119 and / or program code stored in one or more memories 118 and executed by one or more processors 119.

[0058] In an aspect, remote device UI generator 111 includes a configuration data storage database or configuration files (hereinafter “configuration data database”) 211.

[0059] In an aspect, configuration data database 211 stores generic configuration data 211 A (including parsed generic configuration data 212P1 and parsed and validated generic configuration data 212 VI) for each type of hardware (remote device 120).

[0060] In an aspect, generic configuration data 211 A may include all settings (e.g., software settings, hardware settings, UI settings, and so forth) and UI options (e.g., appearance (e.g., shape, color, and so forth)) supported by the hardware (remote device 120). In an aspect, at least one of the software, hardware, and UI settings may be configuration settings for configuring at least one of system UI 100A or remote devices 120. For example, in an aspect, the software settings are values capable of being set for software parameters corresponding to functions performed by remote devices 120, the hardware settings are values capable of being set for hardware parameters corresponding to functions performed by remote devices 120, and UI settings are values capable of being set of UI parameters corresponding to functions performed by remote devices 120.

[0061] In an aspect, generic configuration data 211 A further includes hardware profiles. Each hardware type will have a profile 211 Al within generic configuration data 211 A. Each profile 211 Al for a respective hardware type will detail the specific capabilities (smoke detection, heat detection, visual notification, audible notification, etc.) and specific UI requirements (input(s) for smoke detection parameters, input(s) for heat detection parameters, input(s) for visual notification, input(s) for audible notification, etc.) of the respective hardware type.P700000PC00

[0062] An advantage of using configuration data database 211 is the realization of dynamic hardware support. That is, unlike traditional methods that require hardcoding support for each new hardware, aspects of the present disclosure use a generic configuration data approach. This allows remote device UI generator 111 to dynamically support new hardware by simply updating generic configuration data 211 A, without the need for extensive code changes.

[0063] In an aspect, remote device UI generator 111 includes a predefined schema 212.Predefined schema 212 outlines the necessary fields and data types to ensure consistency and allows the software to interpret generic configuration data 211 A correctly.

[0064] In an aspect, remote device UI generator 111 includes a data processing engine 213. An engine is basically software that is executed to, e.g., do something (e.g., parse and validate generic configuration data) or create something (a template). In an aspect, data processing engine 213 includes a parser component (hereinafter “parser”) 213P and a validation component (hereinafter “validator”) 213 V.

[0065] In an aspect, parser 213P parses generic configuration data 211 A from configuration data database 211 by formatting generic configuration data 211 A to adhere to predefined schema 212. The output of parser 213P is parsed generic configuration data 213P1.

[0066] In an aspect, validator 213V validates parsed generic configuration data 213P1 by checking parsed generic configuration data 213P1 for errors or inconsistencies and removing any detected errors or inconsistencies. In an aspect, the checking involves evaluating parsed generic configuration data 213P1 with respect to a set of known errors and set of known inconsistencies. In an aspect, the checking is performed using machine learning. In an aspect, the set of errors and the set of inconsistencies are continually refined by applying machine learning to the functions of error checking and inconsistency checking to better detect actual errors and inconsistencies and minimize a false positive rate. The output of validator 213 V is parsed and validated generic configuration data 213 VI.

[0067] In an aspect, remote device UI generator 111 includes a remote device UI generator 214. In an aspect, remote device UI generator 214 dynamically creates, based on parsed and validated generic configuration data 212V1, remote device UI 111 A for new remote device 120A. Dynamically created UI elements in remote device UI 111A are capable of configuring new remote device 120 A. The UI elements dynamically created by remote device UI element generator 214 include forms, input fields, dropdowns, and otherP700000PC00interactive components. Of course, in a different aspect, other UI elements may be included, and at least one of the preceding UI elements may be omitted.

[0068] Some advantages of UI interface generation based on parsed and validated generic configuration data 213 VI are consistency and efficiency. The ability to auto-generate the user interface (UI) based on parsed and validated generic configuration data 213 VI ensures a consistent and error-free UI for new hardware, reducing the manual effort and potential for inconsistencies that come with hand-coding UI elements.

[0069] In an aspect, remote device UI generator 111 includes a template engine 215. An engine is basically software that is executed to, e.g., do something (e.g., parse and validate generic configuration data) or create something (a template).

[0070] In an aspect, template engine 215 is used to standardize the look and feel of the UI elements created by remote device UI generator 214, ensuring a consistent user experience across different hardware types (different types of remote devices 120). In an aspect, a consistent user experience may be achieved by maintaining a mapping of UI element characteristics (e.g., actuation mechanism (e.g., checkbox, button, slider, etc.), shape, color, value range, name, etc.) for different elements so that when a same or similar element is created for new remote device 120 A, the same or at least some of the same UI element characteristics may be used to provide a consistent user experience across different hardware types.

[0071] In an aspect, remote device UI generator 111 includes an integration application programming interface (API) layer 216. An API is a type of software interface offering a service to other pieces of software, here the service being inter-communication. In an aspect, integration API layer 216 facilitates communication between configuration data database 211, data processing engine 213, and remote device UI element generator 214. Integration API layer 216 ensures that data flows seamlessly between the aforementioned components (configuration data database 211, data processing engine 213, and remote device UI generator 214). In an aspect, “seamless data flow” may involve ensuring the received data by each of the entities (configuration data database 211, data processing engine 213, and remote device UI element generator 214) is in an expected format (e.g., in accordance with predefined schema 212) and includes expected, error-free values, such as the respective functions performed by parser 213P and validator 213 V.P700000PC00

[0072] In an aspect, remote device UI generator 111 includes event handlers 217. An “event handler” is a piece of code within a program that is designed to execute a specific action when a particular event occurs, essentially acting as a response mechanism to user interactions or system changes like mouse clicks, key presses, or network updates. Thus, an event handler may be considered a function that gets called whenever a predefined event happens. In an aspect, event handlers 217 manage interactions between the user and remote device UI 111 A, updating generic configuration data 211 A as needed and triggering actions within the software that are appropriate for generic configuration data 211 A. For example, actions within the capabilities and / or value ranges as specified in generic configuration data 211 A are performed with respect to remote devices 120 and not those that exceed such capabilities and / or value ranges, e.g., to avoid inducing failures in remote devices 120.

[0073] In an aspect, remote device UI generator 111 includes a generic configuration data update system 218 for updating generic configuration data 211 A. In an aspect, developers and / or authorized users can update generic configuration data 211 A to add support for new hardware (new remote devices 120 A). In an aspect, updates to generic configuration data 211 A are made through a dedicated interface of generic configuration data update system 218 and / or by directly modifying the entries of configuration data database 211 storing generic configuration data 211 A. Updates to generic configuration data 211 A may further involve inputting update-associated information such as a time an update takes effect, an identifier of a user inputting the updates, an identifier of a version of the updates, and so forth. Generic configuration data update system 218 ensures that fire notification system 100 can quickly adapt to new hardware releases without significant downtime or resource allocation.

[0074] In an aspect, remote device UI generator 111 includes a version control system 219 for maintaining version information and implementing control over different versions of generic configuration data 211 A. In an aspect, version control system 219 tracks changes to generic configuration data 211 A, allowing for configuration rollback and auditing of updates with respect to generic configuration data 211 A. Configuration rollback is a feature that allows a user to revert a configuration of a remote device 120 to a previous state (previous configuration). Configuration rollback may be used to fix errors, roll back to a previous configuration, or recover from unexpected results. Auditing of updates involves reviewing and verifying the process of applying updates to generic configuration data 211. Auditing of updates may involve one or more of assessing the update content, deploymentP700000PC00methods, testing procedures, impact analysis, and post-update monitoring to ensure security, functionality, and compliance with established policies. The auditing of updates may be used to check that updates are being properly managed and implemented without causing unintended disruptions or vulnerabilities to fire notification system 100. Version control system 219 adds an extra layer of reliability and accountability to the update process.

[0075] In an aspect, remote device UI generator 111 includes a data encryption system 220.Encryption is a method of scrambling data so that only authorized users can read the data. In an aspect, the generic configuration data 211 A is encrypted to protect the generic configuration data 211 A from unauthorized access. In an aspect, the generic configuration data is 211 A encrypted at least one of in one or more memories 118 in which it is stored, and also for transmission by integration API layer 216 to other elements of remote device UI generator 111 (e.g., data processing engine 213 and remote device UI element generator 214).

[0076] In an aspect, remote device UI generator 111 includes an authentication and authorization system 221. In an aspect, authentication and authorization system 221 includes authentication and authorization mechanisms to ensure that only authorized users can update the generic configuration data 211 A. For example, in an aspect, authentication and authorization system 221 utilize a mapping of one or more users to fire notification system 100 using one or more pieces of identifying information (e.g. a personal identification number (PIN), a password, biometric data (fingerprint, retina print, voice print, and so forth). In this way, a keypad and / or camera and / or microphone (as I / O input device 113) may be used to receive data from a user for authentication purposes (e.g., by comparing against a database of pre-obtained matching data).

[0077] The preceding architecture of remote device UI generator 111 ensures that the programming software of FACP 110 can efficiently and reliably support new hardware (e.g., new remote device 120A) with minimal manual intervention, providing a scalable and user-friendly solution.

[0078] FIGS. 3-11 show various representations 300-1100 of remote device UI 111 A of FIG.1 having different input types that can be selected using a selection / deselection mechanism (e.g., 319k, 401k, 501k, 601k, 701k). A selection of an input type using the selection mechanism results in either further selected options (e.g., parameters of remote deviceP700000PC00120 / new remote device 120A and / or values for those parameters, and so forth) that do not require a manual input but rather similar selection and / or an area responsive to an input device for receiving characters such as text specifying parameters, for example, of remote new device 120 and / or remote device UI 111 A, and values for those parameters.

[0079] Referring now to FIG. 3, a representation 300 of remote device UI 111A of FIG. 1 is shown, in accordance with an exemplary aspect.

[0080] Representation 300 includes an input portion 310 configured to receive a user input relating to selecting a particular type of setting or UI option, e.g., by a user input in a box adjacent to each type of setting or UI option (similar selection boxes are included in other related figures herein). The user input may include one or more touch inputs on the display (of I / O devices 113 of FACP 110) showing representation 300, which, in an aspect, may also show a virtual keyboard. Alternatively, the user input may be provided using other I / O devices 113 of FACP 110 such as a keyboard and / or a mouse and / or a trackball).

[0081] The selection of the particular type of setting is made from among software settings 401 A (e.g., in a software settings region 401 shown in further detail in FIG. 4), hardware settings 501 A (e.g., in a hardware setting region 501 shown in further detail in FIG. 5), and UI settings 601 A (e.g., in a UI setting region 601 shown in further detail in FIG. 6).

[0082] Input portion 310 of representation 300 is further configured to receive a user input selecting UI options 701A (in a UI options region 701 shown in further detail in FIG. 7).Regions 401, 501, 601, and 701 may be dynamically sized by a user as desired. For example, a user specifically adding software settings 401 A may increase the size of software setting region 401 while maintaining or decreasing the size of the remaining regions 501, 601, and 701. The user may then switch to specifically adding hardware settings 501 A and increase the size of the hardware setting region 501 while decreasing the size of the software settings region 401. In this way, a user is provided adjustability and accommodation in their preference in viewing the remote device UI 111 A.

[0083] Referring now to FIG. 4, a representation 400 of remote device UI 111A of FIG. 1 corresponding to a selection of software settings in FIG.3 is shown, in accordance with an exemplary aspect.

[0084] Representation 400 includes a software settings region 401. The size of the other regions 501, 601, and 701 may be decreased to be minimal and are thus not explicitly shown in representation 400. Software settings region 401 includes various software settingsP700000PC00401 A. In an aspect, software settings 401 A may include, but are not limited to: zone definitions 40 IB; device assignments to zones 401C; alarm and notification settings (including audible and visual alarms) 40 ID; evacuation plan configurations 40 IE; delay times 40 IF; sensitivity levels for detectors 401G; system reporting options 401H; network connectivity settings 4011; potentially voice evacuation message programming 401J; and so forth. In an aspect, applicable software setting types are automatically invoked (enabled for input) for a given remote device type (e.g., from the preceding listing above) and may be deselected when not applicable by deselecting the software type using a software type selection / deselection mechanism 40 IK.

[0085] Referring now to FIG. 5, a representation 500 of remote device UI 111A of FIG. 1 corresponding to a selection of hardware settings in FIG. 3 is shown, in accordance with an exemplary aspect.

[0086] Representation 500 includes a hardware settings region 501. Hardware settings region 501 includes various hardware settings 501A. In an aspect, hardware settings 501A may include, but are not limited to: operating ranges 50 IB of various hardware-based operational parameters of remote device 120; maximum current and / or voltage and / or sound notification thresholds 501C; candela settings 50 ID; protocols supported 50 IE; version of protocol supported 50 IF; firmware version 501G; hardware version 501H; feature version supported 5011; compatibility modes 501 J; coding patterns supported 501L; and so forth. In an aspect, applicable hardware setting types are automatically invoked (enabled for input) for a given remote device type (e.g., from the preceding listing above) and may be deselected when not applicable by deselecting the hardware type using a hardware type selection / deselection mechanism 501k.

[0087] Referring now to FIG. 6, a representation 600 of remote device UI 111A of FIG. 1 corresponding to a selection of UI settings in FIG. 3 is shown, in accordance with an exemplary aspect.

[0088] Representation 600 includes a UI settings region 601. UI settings region 601 includes various UI settings 601 A. In an aspect, UI settings 601 A may include, but are not limited to: system status 601B; alarms 601C; system tests 601D; UI configuration settings 601E; zone monitoring 60 IF; notification type 601G (e.g., email and / or short message service (SMS) and / or voice message); and so forth. In an aspect, applicable UI setting types are automatically invoked (enabled for input) for a given remote device type (e.g., from theP700000PC00preceding listing above) and may be deselected when not applicable by deselecting the UI type using a UI type selection / deselection mechanism 601k.

[0089] Referring now to FIG. 7, a representation 700 of remote device UI 111A of FIG. 1 corresponding to a selection of UI options in FIG. 3 is shown, in accordance with an exemplary aspect.

[0090] Representation 700 includes a UI options region 701. UI options region 701 includes various UI options 701A. In an aspect, UI options 701A may include, but are not limited to: UI element shapes 701A1; UI element selection mechanisms 701A2 (e.g., checkbox (e.g., checkboxes 319k, 401k, 501k, 601k, 701k), slider, input character line, etc.); screen resolution 701A3; backlight brightness 701A4; audible alarm volume 701A5; tone selection 701 A6; different choices (drop down selection) 701 A7; default language 701 A8; alternate languages or string id 701 A9; type of UI to display the settings 701 A10 (checkbox (Boolean), dropdown, list); options / sub-options 701 All; priority 701 A12; UI order 701A13; and so forth.

[0091] Customization of the aforementioned settings and UI options essentially allows users to customize how fire notification system 100 responds to different fire detection scenarios across various areas of a building or other entity being monitored.

[0092] Selections may be made in the regions of the following representations of FIGS. 7-11 using a selection mechanism 70 IK. In a checkbox selection mechanism, checking the box makes a selection and unchecking the box removes the selection. While a checkbox selection mechanism is shown, other selection mechanisms can also be used.

[0093] Referring now to FIG. 8, a representation 800 of remote device UI 111A of FIG. 1 corresponding to generic configuration data update system 218 of FIG. 2 for updating generic configuration data 211 A is shown, in accordance with an exemplary aspect.

[0094] In an aspect, updates to generic configuration data 211 A are made through a dedicated interface 811U of generic configuration data update system 218 on remote device UI 111 A. In an aspect, updates to generic configuration data 211 A are made by directly modifying entries 211Z of configuration data database 211 storing generic configuration data 211 A. In an aspect, one or more different input devices such as a dedicated keyboard and / or a dedicated mouse of I / O devices 113 may be used.

[0095] In an aspect, the use of generic configuration data update system 218 may involve specifying one or more of the following in a generic configuration data update region 818,P700000PC00for example, to configure generic configuration data update system 218 and / or new remote device 120A: updates 218A to generic configuration data 211 A; a time 218B for updates 218A to take place (i.e., be implemented and / or otherwise take effect in fire notification system 100); an identifier 218C of a user inputting updates 218A; and an identifier 218D of a version of the updates (that may cooperate with version control system 219 to implement version control including version rollback and update auditing).

[0096] Referring now to FIG. 9, a representation 900 of remote device UI 111A of FIG. 1 corresponding to version control system 219 of FIG.2 for maintaining version information and implementing control over different versions of generic configuration data 211 A is shown, in accordance with an exemplary aspect.

[0097] In an aspect, the use of version control system 219 may involve specifying one or more of the following in a version control region 919, for example, to configure version control system 219 and / or new remote device 120A: identifier 218D of a version number; time 218B the update (version) took effect (to enable version searching by the effective time of the version; an identifier 219A of a feature of a particular version (to enable version searching by feature); and identifier 218C of a user whose inputted the updates corresponding to a particular version (to enable version searching by the user who input the updates to the generic configuration data 211 A for a particular version).

[0098] Searching for a version may enable and be performed together with configuration rollback via a configuration rollback selector 219B and / or update (version) auditing via an auditing selector 219C.

[0099] In an aspect, version control system 219 tracks changes to generic configuration data 211 A, allowing for configuration rollback and / or auditing of updates, with respect to generic configuration data 211 A. Configuration rollback is a feature that allows a user to revert a configuration of a remote device 120 to a previous state (previous configuration). A prior version may be found by using one or more of identifiers 218D, 219A, 218C and / or time 218B. Auditing of updates involves reviewing and verifying the process of applying updates to generic configuration data 211. Auditing of a given update may involve assessing one or more of: the update content; an update deployment method(s); an update testing procedure(s); an update impact analysis; and post-update monitoring.P700000PC00

[0100] Referring now to FIG. 10, a representation 1000 of remote device UI 111 A of FIG. 1 corresponding to data encryption system 220 of FIG. 2 for encrypting the generic configuration data 211 A is shown, in accordance with an exemplary aspect.

[0101] In an aspect, the generic configuration data is 211 A can be encrypted at least one of in one or more memories 118 in which it is stored, and also for transmission by integration API layer 216 to other elements of remote device UI generator 111 (e.g., data processing engine 213 and remote device UI element generator 214).

[0102] In an aspect, the use of data encryption system 220 may involve specifying one or more of the following in an encryption control region 1020, for example, to configure data encryption system 220 and / or new remote device 120A: an identifier 220A of one or both of storage or transmission with respect to which forms of the generic configuration data 211 A is encrypted; an identifier 220B of an encryption method selected from one or more encryption methods; and an identifier 220C of a person specifying the encryption, e.g., for auditing and / or security purposes.

[0103] The one or more encryption methods may involve one or more of: symmetric encryption; asymmetric encryption; and elliptic curve cryptography. Symmetrical encryption is also known as private key cryptography. In symmetrical encryption, a single secret key is used to encrypt plaintext and decrypt ciphertext. Both the sender and receiver have private access to the key, which can only be used by authorized recipients. Asymmetric encryption is also known as public key cryptography. In asymmetric encryption, two keys are used: a public key; and a private key. Separate keys are used for both the encryption and decryption processes. Elliptic Curve Cryptography (ECC) is a public-key encryption method that uses elliptic curves to secure data.

[0104] Referring now to FIG. 11, a representation 1100 of remote device UI 111A of FIG. 1 corresponding to authentication and authorization system 221 of FIG. 2 for authenticating authorized users prior to enabling a user to access the generic configuration data 211 A is shown, in accordance with an exemplary aspect.

[0105] In an aspect, the use of authentication and authorization system 221 may involve specifying one or more of the following in an authentication and authorization control region 1121, for example, to configure authentication and authorization system 221 and / or new remote device 120 A: identifiers 221 A of authorized users; and user identifying dataP700000PC0022 IB (e.g. a personal identification number (PIN), a password, biometric data (fingerprint, retina print, voice print, and so forth); certificate 221C; private key 22 ID; and so forth.

[0106] In this way, a keypad and / or camera and / or microphone (as I / O input device 113) may be used to receive data (e.g., user identifying data 221B) from a user for authentication purposes (e.g., by comparing against a database of pre-obtained matching data).

[0107] Referring now to FIGS. 12-13, an example method 1200 for generating a user interface (UI) for a fire alarm control panel of a fire notification system having remote devices is shown, in accordance with an example aspect. The method 1200 may be performed by FACP 110 based on instructions stored in one or more memories 118, individually or in combination, and executable by one or more processors 119, individually or in combination. The one or more processors 119 are configured to execute instructions stored in the one or more memories 118 to implement each of the elements of the remote device UI generator shown in FIG. 2. In an aspect, the one or more memories may also implement configuration data database 211.

[0108] Referring now to FIG. 12, at block 1205, the method 1200 includes storing, in one or more memories 118 (e.g., configuration data database 211), generic configuration data 211 A for each remote device type, a predefined schema 212 that outlines expected fields and expected data types of the generic configuration data 211 A, and remote device specific profile data 211 Al for the remote devices. In an aspect, the generic configuration data includes a UI configuration description that describes an expected appearance of a UI with corresponding appearance and functional options (colors, selection mechanisms, features, etc.). In another aspect, the generic configuration data omits a UI configuration description. In such a case, the system (e.g., a UI generator 214) may consider similar or other remote devices and use portions and / or features of the UI‘s for the similar or other remote devices in generating a UI for a new remote device.

[0109] At block 1210, the method 1200 includes formatting, by a data processing engine 213, the generic configuration data 211 A in adherence to the predefined schema 212 to generate parsed generic configuration data 212P 1. In an aspect, the formatting of the generic configuration data 211 A may involve placing particular parameters of, for example, a new remote device 120 A and values for the parameters in a pre-determined format havingP700000PC00particular locations for particular items (parameters and values) in order to make it possible to check the particular items for errors in a next block 1215.

[0110] At block 1215, the method 1200 includes detecting and removing, by the data processing engine 213, errors and inconsistencies from the parsed generic configuration data 212P1 to generate validated and parsed generic configuration data 212V1. In an aspect, data processing engine 213 detects errors and inconsistencies by enabling comparisons between the parsed generic configuration data 212P1 and known errors and inconsistencies (which also may be stored in configuration data database 211) typically found in parsed generic configuration data 211P1.

[0111] At block 1220, the method 1200 includes dynamically generating, by a UI generator 214 based on the validated and parsed generic configuration data 212V1 and the remote device profile data 211 Al, a remote device UI 111 A for a new remote device 120A having UI elements that are capable of remotely configuring the new remote device 120 A. In an aspect the UI generator 214 generates the remote device UI 111 A to have UI options 701 A specified in representation 700 of FIG. 7, including, but not limited to: UI element shapes 701A1; UI element selection / deselection mechanisms 701A2 (e.g., checkbox, slider, input character line, etc.); screen resolution 701A3; backlight brightness 701A4; audible alarm volume 701A5; tone selection 701 A6; and so forth.

[0112] Referring now to FIGS. 13-14, further blocks of method 1200 are shown, in accordance with an exemplary aspect.

[0113] At block 1225, the method 1200 includes configuring an application programming interface (API) layer 216 to facilitate communication between the one or more memories 118 (e.g., database 211), the data processing engine 213, and the UI generator 214.

[0114] At block 1230, the method 1200 includes configuring the data processing engine 213 to use machine learning to format the generic configuration data 211 A in adherence to the predefined schema 212 and detect and remove the errors and inconsistencies from the parsed generic configuration data 212P1. For example, in an aspect, the data processing engine 213 may be configured to use supervised machine learning, where correctly formatted predefined schema 212 are labeled and provided to the system for training and use in detecting errors and inconsistencies in the generic configuration data 211 A byP700000PC00comparing the parsed generic configuration data 212P1 to one or more predefined schemas that are labeled as correct in a supervised learning system.

[0115] At block 1235, the method 1200 includes configuring a template engine 215 to standardize an appearance of and interaction with the UI elements and provide a consistent user experience across different remote device types. In an aspect, the template engine 215 evaluates the UI elements corresponding to various different remote devices in order to automatically, or with the user’s permission, standardize or recommend similar UI elements. For example, for a given parameter of a remote device 120 or new remote device 120 A, a particular shape and color interface may be automatically implemented by the system (UI generator 214) or with a user’s approval, to standardize the shape and color and response profile of the interface with respect to that parameter. In this way, the parameter can be readily found when scrolling through different remote devices 120 and / or remote device types, due to the assignment of a common shape and / or color and / or response profile to the same parameter across different remote devices and / or remote device types.

[0116] At block 1240, the method 1200 includes configuring a set of event handlers 217 to manage interactions between a user and the remote device UI 111A, update the generic configuration data 211 A and trigger actions within corresponding software for the new remote device 120 to be added to the fire notification system 100. To configure an event handler, the following is typically involved: identifying the element or object that will trigger the event; accessing the properties of the event to specify the event type; and then assigning a function (the event handler) to be executed when that event occurs. In an aspect, triggering actions within corresponding software for the new remote device 120 to be added to the fire notification system 100 may involve sending power to the new remote device 120A, sending configuration signals to the new remote device 120A, receiving reporting (status, and so forth) signals from the new remote device 120. The status signals may indicate if the installation / configuration occurred properly or if there are any errors.

[0117] At block 1245, the method 1200 includes configuring a generic configuration data update system 218, that includes a dedicated interface 811U, to receive updates to the generic configuration data 211 A via the dedicated interface 811U to support the new remote device 120 A.

[0118] In an aspect, configuring generic configuration data update system 218 may involve specifying one or more of the following: updates 218A to generic configurationP700000PC00data 211 A; a time 218B for updates 218A to take place; an identifier 218C of a user inputting updates 218A; and an identifier 218D of a version of the updates 218A to implement version control including version rollback and update auditing. In an aspect, the inputting of updates 218A, identifier 218C, identifier 218D, and time 218B enable the remote devices 120 of fire notification system 100 to keep up with improvements (updates) and have the improvements readily deployed.

[0119] At block 1250, the method 1200 includes configuring a version control system 219 to track changes to the generic configuration data 211 A and provide rollback and updating auditing capabilities for the generic configuration data 211 A. In this way, for example, should a new configuration turn out to be defective and / or otherwise problematic, a reversion can be made to a prior configuration by specifying a version number, a feature, and / or so forth of a particular version to which reversion is sought.

[0120] In an aspect, configuring version control system 219 may involve specifying one or more of the following: identifier 218D of a version number; time 218B the update (version) took effect; an identifier 219A of a feature of a particular version; and identifier 218C of a user whose inputted the updates corresponding to a particular version. One or more of the preceding identifiers and time may be used to search for a particular version to be put into force. To that end, version control system 219 may include a search engine for searching for version information that may be stored therein or along with the generic configuration data 211 A.

[0121] At block 1255, the method 1200 includes configuring a data encryption system 220 to encrypt the generic configuration data 211 A for storage in the one or more memories 118 (database211) and for a transmission between the one or more memories 118 (database 211), the data processing engine 213, and the UI generator 214. In this way, interception of a data stream between any of the entities from among the one or more memories 118, the data processing engine 213, and the UI generator 214 can be rendered trivial by the obtaining of encrypted and thus un-useful data.

[0122] In an aspect, configuring data encryption system 220 may involve specifying one or more of the following: an identifier 220A of one or both of storage or transmission with respect to which forms (stored and / or transmitted) of the generic configuration data 211 A is encrypted; an identifier 220B of an encryption method selected from one or more encryption methods; and an identifier 220C of a person specifying the encryption. UsingP700000PC00the preceding information, the data encryption system 220 can be configured to provide protection to any target data (stored and / or transmitted generic configuration data 211 A) specified for protection.

[0123] At block 1260, the method 1200 includes configuring an authentication and authorization system 221 to only allow authenticated authorized users to update the generic configuration data 211 A stored in the one or more memories 118. In this way, only authenticated authorized users can input updates 218A and / or other information to prevent malfeasance and maintain control of the operation of fire notification system 100.

[0124] In an aspect, configuring authentication and authorization system 221 may involve specifying one or more of the following: identifiers 221 A of authorized users; and user identifying data 22 IB (e.g. a personal identification number (PIN), a password, biometric data (fingerprint, retina print, voice print, and so forth); and so forth. The preceding information

[0125] At block 1265, the method 1200 includes configuring a simulation / emulation of a new remote device 120. In this way, a new remote device 120 can have a user interface generated for the new remote device 120 without requiring an actual hardware implementation of the new remote device 120. In an aspect, new remote devices 120 are configured to determine an optimum configuration before actually installing a hardware implementation of a new remote device 120 into fire notification system 100.

[0126] Additional aspects of the present disclosure may include one or more of the following clauses.

[0127] Clause 1. A user interface (UI) generation device for a fire alarm control panel of a fire notification system having remote devices, the UI generation device comprising: one or more memory devices configured to store generic configuration data for each remote device type, a predefined schema that outlines expected fields and expected data types of the generic configuration data, and remote device specific profile data for the remote devices; one or more processors configured to: format the generic configuration data in adherence to the predefined schema to generate parsed generic configuration data, remove errors and inconsistencies from the parsed generic configuration data to generate parsed and valid generic configuration data; and dynamically generate, based on the parsed and valid generic configuration data and the remote device profile data, a UI for a new remote device having UI elements that are capable of remotely configuring the new remote device;P700000PC00and an application programming interface (API) layer configured to facilitate communication between the memory device and the one or more processors.

[0128] Clause 2. The UI generation device in accordance with clause 1, wherein the generic configuration data for each type of the remote devices comprises settings and UI options supported by the remote devices.

[0129] Clause 3. The UI generation device in accordance with any preceding clauses, wherein the device specific profile data for the remote devices comprises remote device capabilities and remote device UI requirements.

[0130] Clause 4. The UI generation device in accordance with any preceding clauses, wherein settings supported by the remote devices and comprised in the generic configuration data comprise hardware settings, software settings, and UI settings.

[0131] Clause 5. The UI generation device in accordance with any preceding clauses, wherein the one or more processors are further configured to use machine learning to format the generic configuration data in adherence to the predefined schema and detect and remove the errors and inconsistencies from the parsed generic configuration data.

[0132] Clause 6. The UI generation device in accordance with any preceding clauses, wherein the one or more processors are further configured to generate the UI to include UI elements comprising forms, input fields, dropdowns, and other interactive components.

[0133] Clause 7. The UI generation device in accordance with any preceding clauses, wherein the one or more processors are further configured to standardize an appearance of and interaction with the UI elements and provide a consistent user experience across different remote device types.

[0134] Clause 8. The UI generation device in accordance with any preceding clauses, further comprising a set of event handlers configured to manage interactions between a user and the UI, update the generic configuration data and trigger actions within corresponding software for the new remote device to be added to the fire notification system.

[0135] Clause 9. The UI generation device in accordance with any preceding clauses, wherein the one or more processors are further configured to receive updates to the generic configuration data to support the new remote device.

[0136] Clause 10. The UI generation device in accordance with any preceding clauses, wherein the one or more processors are further configured to track changes to the genericP700000PC00configuration data and provide rollback and updating auditing capabilities for the generic configuration data.

[0137] Clause 11. The UI generation device in accordance with any preceding clauses, wherein the one or more processors are further configured to encrypt the generic configuration data for storage in the one or more memory devices and for a transmission between the one or more memory devices and the one or more processors.

[0138] Clause 12. The UI generation device in accordance with any preceding clauses, wherein the one or more processors are further configured to only allow authenticated and authorized users to update the generic configuration data stored in the one or more memory devices.

[0139] Clause 13. The UI generation device in accordance with any preceding clauses, wherein the new remote device is a simulated device.

[0140] Clause 14. A method for generating a user interface (UI) for a fire alarm control panel of a fire notification system having remote devices, the method comprising: storing, in one or more memory devices, generic configuration data for each remote device type, a predefined schema that outlines expected fields and expected data types of the generic configuration data, and remote device specific profile data for the remote devices; formatting, by one or more processors, the generic configuration data in adherence to the predefined schema to generate parsed generic configuration data; detecting and removing, by the one or more processors, errors and inconsistencies from the parsed generic configuration data to generate parsed and valid generic configuration data; dynamically generating, by the one or more processors based on the parsed and valid generic configuration data and the remote device profile data, a UI for a new remote device having UI elements that are capable of remotely configuring the new remote device.

[0141] Clause 15. The method in accordance with clause 14, further comprising configuring an application programming interface (API) layer to facilitate communication between the memory device and the one or more processors.

[0142] Clause 16. The method in accordance with any preceding clauses, further comprising configuring the one or more processors to use machine learning to format the generic configuration data in adherence to the predefined schema and detect and remove the errors and inconsistencies from the parsed generic configuration data.P700000PC00

[0143] Clause 17. The method in accordance with any preceding clauses, further comprising configuring the one or more processors to standardize an appearance of and interaction with the UI elements and provide a consistent user experience across different remote device types.

[0144] Clause 18. The method in accordance with any preceding clauses, further comprising configuring a set of event handlers to manage interactions between a user and the UI, update the generic configuration data and trigger actions within corresponding software for the new remote device to be added to the fire notification system.

[0145] Clause 19. The method in accordance with any preceding clauses, further comprising the one or more processors to receive updates to the generic configuration data via a dedicated interface to support the new remote device.

[0146] Clause 20. The method in accordance with any preceding clauses, further comprising configuring the one or more processors to track changes to the generic configuration data and provide rollback and updating auditing capabilities for the generic configuration data.

[0147] Clause 21. The method in accordance with any preceding clauses, further comprising configuring the one or more processors to encrypt the generic configuration data for storage in the one or more memory devices and for a transmission between the one or more memory devices and the one or more processors.

[0148] Clause 22. The method in accordance with any preceding clauses, further comprising configuring the one or more processors to only allow authenticated and authorized users to update the generic configuration data stored in the one or more memory devices.

[0149] Clause 23. The method in accordance with any preceding clauses, wherein the new remote device is a simulated device.

[0150] Various aspects of the disclosure may take the form of an entirely or partially hardware aspect, an entirely or partially software aspect, or a combination of software and hardware. Furthermore, as described herein, various aspects of the disclosure (e.g., systems and methods) may take the form of a computer program product comprising a computer- readable non-transitory storage medium having computer-accessible instructions (e.g., computer-readable and / or computer-executable instructions) such as computer software, encoded or otherwise embodied in such storage medium. Those instructions can be read orP700000PC00otherwise accessed and executed by one or more processors to perform or permit the performance of the operations described herein. The instructions can be provided in any suitable form, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, assembler code, combinations of the foregoing, and the like. Any suitable computer-readable non-transitory storage medium may be utilized to form the computer program product. For instance, the computer-readable medium may include any tangible non-transitory medium for storing information in a form readable or otherwise accessible by one or more computers or processor(s) functionally coupled thereto. Non- transitory storage media can include read-only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory, and so forth.

[0151] Aspects of this disclosure are described herein with reference to block diagrams and flowchart illustrations of methods, systems, apparatuses, and computer program products. It can be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, respectively, can be implemented by computer-accessible instructions. In certain implementations, the computer-accessible instructions may be loaded or otherwise incorporated into a general-purpose computer, a special-purpose computer, or another programmable information processing apparatus to produce a particular machine, such that the operations or functions specified in the flowchart block or blocks can be implemented in response to execution at the computer or processing apparatus.

[0152] Unless otherwise expressly stated, it is in no way intended that any protocol, procedure, process, or method set forth herein be construed as requiring that its acts or steps be performed in a specific order. Accordingly, where a process or method claim does not actually recite an order to be followed by its acts or steps, or it is not otherwise specifically recited in the claims or descriptions of the subject disclosure that the steps are to be limited to a specific order, it is in no way intended that an order be inferred, in any respect. This holds for any possible non-express basis for interpretation, including: matters of logic with respect to the arrangement of steps or operational flow; plain meaning derived from grammatical organization or punctuation; the number or type of aspects described in the specification or annexed drawings; or the like.

[0153] As used in this disclosure, including the annexed drawings, the terms “component,” “module,” “system,” and the like are intended to refer to a computer-related entity or an entity related to an apparatus with one or more specific functionalities. TheP700000PC00entity can be either hardware, a combination of hardware and software, software, or software in execution. One or more of such entities are also referred to as “functional elements.” As an example, a component can be a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and / or a computer. For example, both an application running on a server or network controller, and the server or network controller can be a component. One or more components can reside within a process and / or thread of execution and a component can be localized on one computer and / or distributed between two or more computers. Also, these components can execute from various computer readable media having various data structures stored thereon. The components can communicate via local and / or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and / or across a network such as the Internet with other systems via the signal). As another example, a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry, which parts can be controlled or otherwise operated by program code executed by a processor. As yet another example, a component can be an apparatus that provides specific functionality through electronic components without mechanical parts, the electronic components can include a processor to execute program code that provides, at least partially, the functionality of the electronic components. As still another example, interface(s) can include I / O components or Application Programming Interface (API) components. While the foregoing examples are directed to aspects of a component, the exemplified aspects or features also apply to a system, module, and similar.

[0154] In addition, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. Moreover, articles “a” and “an” as used in this specification and annexed drawings should be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form.

[0155] In addition, the terms “example” and “such as” and “e.g.” are utilized herein to mean serving as an instance or illustration. Any aspect or design described herein as an “example” or referred to in connection with a “such as” clause or “e.g.” is not necessarily to be construed as preferred or advantageous over other aspects or designs described herein.P700000PC00Rather, use of the terms “example” or “such as” or “e.g.” is intended to present concepts in a concrete fashion. The terms “first,” “second,” “third,” and so forth, as used in the claims and description, unless otherwise clear by context, is for clarity only and does not necessarily indicate or imply any order in time or space.

[0156] The term “processor,” as utilized in this disclosure, can refer to any computing processing unit or device comprising processing circuitry that can operate on data and / or signaling. A computing processing unit or device can include, for example, single-core processors; single-processors with software multithread execution capability; multi-core processors; multi-core processors with software multithread execution capability; multicore processors with hardware multithread technology; parallel platforms; and parallel platforms with distributed shared memory. Additionally, a processor can include an integrated circuit, an application specific integrated circuit (ASIC), a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic controller (PLC), a complex programmable logic device (CPLD), a discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. In some cases, processors can exploit nano-scale architectures, such as molecular and quantum-dot based transistors, switches and gates, in order to optimize space usage or enhance performance of user equipment. A processor may also be implemented as a combination of computing processing units.

[0157] In addition, terms such as “store,” “data store,” data storage,” “database,” and substantially any other information storage component relevant to operation and functionality of a component, refer to “memory components,” or entities embodied in a “memory” or components comprising the memory. It will be appreciated that the memory components described herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. Moreover, a memory component can be removable or affixed to a functional element (e.g., device, server).

[0158] Simply as an illustration, nonvolatile memory can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM), which acts as external cache memory. By way of illustration and not limitation, RAM is available in many forms such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAMP700000PC00(SLDRAM), and direct Rambus RAM (DRRAM). Additionally, the disclosed memory components of systems or methods herein are intended to comprise, without being limited to comprising, these and any other suitable types of memory.

[0159] Various aspects described herein can be implemented as a method, apparatus, or article of manufacture using special programming as described herein. In addition, various of the aspects disclosed herein also can be implemented by means of program modules or other types of computer program instructions specially configured as described herein and stored in a memory device and executed individually or in combination by one or more processors, or other combination of hardware and software, or hardware and firmware. Such specially configured program modules or computer program instructions, as described herein, can be loaded onto a general-purpose computer, a special-purpose computer, or another type of programmable data processing apparatus to produce a machine, such that the instructions which execute on the computer or other programmable data processing apparatus create a means for implementing the functionality of disclosed herein.

[0160] The term “article of manufacture” as used herein is intended to encompass a computer program accessible from any non-transitory computer-readable device, carrier, or media. For example, computer readable media can include but are not limited to magnetic storage devices (e.g., hard drive disk, floppy disk, magnetic strips, or similar), optical discs (e.g., compact disc (CD), digital versatile disc (DVD), blu-ray disc (BD), or similar), smart cards, and flash memory devices (e.g., card, stick, key drive, or similar).

[0161] The detailed description set forth herein in connection with the annexed figures is intended as a description of various configurations or implementations and is not intended to represent the only configurations or implementations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details or with variations of these specific details. In some instances, well-known components are shown in block diagram form, while some blocks may be representative of one or more well-known components.

[0162] The previous description of the disclosure is provided to enable a person skilled in the art to make or use the disclosure. Various modifications to the disclosure will beP700000PC00readily apparent to those skilled in the art, and the common principles defined herein may be applied to other variations without departing from the scope of the disclosure. Furthermore, although elements of the described aspects may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. Additionally, all or a portion of any aspect may be utilized with all or a portion of any other aspect, unless stated otherwise. Thus, the disclosure is not to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

P700000PC00CLAIMSWhat is claimed is:

1. A user interface (UI) generation device for a fire alarm control panel of a fire notification system having remote devices, the UI generation device comprising:one or more memory devices configured to store generic configuration data for each remote device type, a predefined schema that outlines expected fields and expected data types of the generic configuration data, and remote device specific profile data for the remote devices;one or more processors configured to:format the generic configuration data in adherence to the predefined schema to generate parsed generic configuration data,remove errors and inconsistencies from the parsed generic configuration data to generate parsed and valid generic configuration data; anddynamically generate, based on the parsed and valid generic configuration data and the remote device profile data, a UI for a new remote device having UI elements that are capable of remotely configuring the new remote device; andan application programming interface (API) layer configured to facilitate communication between the memory device and the one or more processors.

2. The UI generation device in accordance with claim 1, wherein the generic configuration data for each type of the remote devices comprises settings and UI options supported by the remote devices.

3. The UI generation device in accordance with claim 1, wherein the device specific profile data for the remote devices comprises remote device capabilities and remote device UI requirements.

4. The UI generation device in accordance with claim 1, wherein settings supported by the remote devices and comprised in the generic configuration data comprise hardware settings, software settings, and UI settings.

5. The UI generation device in accordance with claim 1, wherein the one or more processors are further configured to use machine learning to format the generic configurationP700000PC00data in adherence to the predefined schema and detect and remove the errors and inconsistencies from the parsed generic configuration data.

6. The UI generation device in accordance with claim 1, wherein the one or more processors are further configured to generate the UI to include UI elements comprising forms, input fields, dropdowns, and other interactive components.

7. The UI generation device in accordance with claim 1, wherein the one or more processors are further configured to standardize an appearance of and interaction with the UI elements and provide a consistent user experience across different remote device types.

8. The UI generation device in accordance with claim 1, further comprising a set of event handlers configured to manage interactions between a user and the UI, update the generic configuration data and trigger actions within corresponding software for the new remote device to be added to the fire notification system.

9. The UI generation device in accordance with claim 1, wherein the one or more processors are further configured to receive updates to the generic configuration data to support the new remote device.

10. The UI generation device in accordance with claim 1, wherein the one or more processors are further configured to track changes to the generic configuration data and provide rollback and updating auditing capabilities for the generic configuration data.

11. The UI generation device in accordance with claim 1, wherein the one or more processors are further configured to encrypt the generic configuration data for storage in the one or more memory devices and for a transmission between the one or more memory devices and the one or more processors.

12. The UI generation device in accordance with claim 1, wherein the one or more processors are further configured to only allow authenticated and authorized users to update the generic configuration data stored in the one or more memory devices.P700000PC0013. The UI generation device in accordance with claim 1, wherein the new remote device is a simulated device.

14. A method for generating a user interface (UI) for a fire alarm control panel of a fire notification system having remote devices, the method comprising:storing, in one or more memory devices, generic configuration data for each remote device type, a predefined schema that outlines expected fields and expected data types of the generic configuration data, and remote device specific profile data for the remote devices; formatting, by one or more processors, the generic configuration data in adherence to the predefined schema to generate parsed generic configuration data;detecting and removing, by the one or more processors, errors and inconsistencies from the parsed generic configuration data to generate parsed and valid generic configuration data;dynamically generating, by the one or more processors based on the parsed and valid generic configuration data and the remote device profile data, a UI for a new remote device having UI elements that are capable of remotely configuring the new remote device.

15. The method in accordance with claim 14, further comprising configuring an application programming interface (API) layer to facilitate communication between the memory device and the one or more processors.

16. The method in accordance with claim 14, further comprising configuring the one or more processors to use machine learning to format the generic configuration data in adherence to the predefined schema and detect and remove the errors and inconsistencies from the parsed generic configuration data.

17. The method in accordance with claim 14, further comprising configuring the one or more processors to standardize an appearance of and interaction with the UI elements and provide a consistent user experience across different remote device types.

18. The method in accordance with claim 14, further comprising configuring a set of event handlers to manage interactions between a user and the UI, update the generic configuration data and trigger actions within corresponding software for the new remote device to be added to the fire notification system.P700000PC0019. The method in accordance with claim 14, further comprising the one or more processors to:receive updates to the generic configuration data via a dedicated interface to support the new remote device; andtrack changes to the generic configuration data and provide rollback and updating auditing capabilities for the generic configuration data.

20. The method in accordance with claim 14, further comprising configuring the one or more processors to:encrypt the generic configuration data for storage in the one or more memory devices and for a transmission between the one or more memory devices and the one or more processors; andonly allow authenticated and authorized users to update the generic configuration data stored in the one or more memory devices, wherein the new remote device is a simulated device.