Patent Description:
Large facilities (e.g., buildings), such as commercial facilities, office buildings, hospitals, and the like, may have an alarm system that can be triggered during an emergency situation (e.g., a fire) to warn occupants to evacuate. For example, an alarm system may include a control panel (e.g., a fire control panel) and a plurality of event devices (e.g., hazard sensing devices, input devices, output devices, etc.) located throughout the facility (e.g., on different floors and/or in different rooms of the facility) that can perform an action when a hazard event is occurring in the facility and provide a notification of the hazard event to the occupants of the facility via alarms or other mechanisms.

Maintaining the alarm system can include regular testing of event devices. Such regular testing may be mandated by codes of practice in an attempt to ensure that the event devices are functioning properly. Document <CIT> discloses a system and method for facilitating inspection of fire alarm systems including a graphical user interface rendered on a touchscreen display of a mobile computing device receiving selections of inspection results.

Devices, systems, and methods for event device maintenance are described herein. The invention concerns a mobile device as defined in claim <NUM> and the corresponding method as defined in claim <NUM>.

Maintenance of event devices can include a first user (e.g., such as a technician, engineer, etc.) walking around the facility and visually checking the alarm system components, typically, at the same time as they carry out functional testing of event devices and other components of the alarm system. For example, carrying out smoke testing of fire sensors and visual inspection of fire sensors at the same time the inspector is close enough to visually inspect each fire sensor. While the first user is functionally testing and visually inspecting event devices, a second user may typically interpret signals received at the alarm system control panel. Such signals can be the result of the first user functionally testing event devices in the facility.

Such a manual testing process between the second user at the control panel and the first user testing event devices in the facility may be subject to error. For instance, the first user may identify and test an event device in a space of the facility and activate such a device while the second user views the output from the event device on the alarm system control panel. The first user has to be in continuous communication with the second user to ensure the correct event device is tested, as identifying an incorrect event device can lead to errors in the testing process.

Additionally, in some instances the first user may identify and test an event device in a space of the facility that has multiple event devices. In such an instance, the first user may test a first event device while misinterpreting it to be a second event device as the first and second event devices may be located proximately to one another. Further, in some examples such a facility may not have a network relationship available for the first user to be in communication with the second user and/or the alarm system control panel so that the first user is able to verify they have tested the first event device and not the second event device.

Event device maintenance according to the present disclosure can allow for a user to differentiate between different event devices for testing in a facility. Such an approach can allow a mobile device to be in communication with an event device even if the mobile device may not be in communication with an alarm system control panel. Additionally, the mobile device can allow the user to more easily determine which event device they are interacting with even in an instance where multiple event devices are located near the mobile device as compared with previous approaches. Accordingly, such an approach can ensure a user is able to confirm which event device they are interacting with to avoid errors in the testing process.

These embodiments are described in sufficient detail to enable those of ordinary skill in the art to practice one or more embodiments of this disclosure. It is to be understood that other embodiments may be utilized and that process, electrical, and/or structural changes may be made without departing from the scope of the appended claims.

The proportion and the relative scale of the elements provided in the figures are intended to illustrate the embodiments of the present disclosure and should not be taken in a limiting sense.

As used herein, "a", "an", or "a number of" something can refer to one or more such things, while "a plurality of" something can refer to more than one such things. For example, "a number of components" can refer to one or more components, while "a plurality of components" can refer to more than one component.

<FIG> is an example of a system <NUM> for event device maintenance, in accordance with one or more embodiments of the present disclosure. The system <NUM> includes a mobile device <NUM>, a group <NUM> of event devices <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, a network <NUM>, a gateway device <NUM>, a control panel <NUM>, and a remote computing device <NUM>. Each of the event devices <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM> can include a beacon <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, respectively, and includes an indicator <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM> respectively.

As illustrated in <FIG>, the system <NUM> includes a control panel <NUM>. As used herein, the term "control panel" refers to a device to control components of an alarm system of a facility. For example, the control panel <NUM> can be a fire control panel that can receive information from event devices <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM> (referred to collectively herein as event devices <NUM>) and determine whether a hazard event is occurring or has occurred.

The control panel <NUM> is connected to the group <NUM> of event devices <NUM>. As used herein, the term "event device" refers to a device that can receive an input relating to an event and/or generate an output relating to an event. Such an event can be, for instance, a hazard event such as a fire. For example, an event device can receive an input relating to a fire occurring in the facility. Such event devices <NUM> can be a part of an alarm system of the facility and can include devices such as fire sensors, smoke detectors, heat detectors, carbon monoxide (CO) detectors, or combinations of these; interfaces; pull stations; input/output modules; aspirating units; and/or audio/visual devices (e.g., speakers, sounders, buzzers, microphones, cameras, video displays, video screens, etc.), among other types of event devices.

These event devices <NUM> can be automatic, self-test devices, such as smoke detectors, heat detectors, CO detectors, and/or others. Such self-test devices can include mechanisms that generate aerosols, heat, carbon monoxide, etc. and sense these items as appropriate to the type of device being tested in the device to test the performance of the device. This can, for example, be to test the event device's thermal and/or photo sensing capabilities.

The event devices <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM> can be included in a group <NUM>. Although the group <NUM> is illustrated in <FIG> as including three event devices <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, embodiments of the current disclosure are not so limited. For example, the group <NUM> can include more than three event devices or less than three event devices. Additionally, the system <NUM> can include more than one group <NUM> of event devices.

Each of the event devices <NUM> includes a beacon <NUM>. For example, event device <NUM>-<NUM> can include a beacon <NUM>-<NUM>, event device <NUM>-<NUM> can include a beacon <NUM>-<NUM>, and event device <NUM>-<NUM> can include a beacon <NUM>-<NUM>. As used herein, the term "beacon" refers to a wireless device that broadcasts radio signals. For example, the beacons <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM> can emit radio signals to be detected by, for example, a mobile device such as mobile device <NUM>. The beacons <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM> can be Bluetooth, Bluetooth LE (e.g., Bluetooth Smart), Bluetooth low energy (BLE), among other types of beacons.

According to the invention, each of the event devices <NUM> includes an indicator <NUM>. For example, event device <NUM>-<NUM> can include an indicator <NUM>-<NUM>, event device <NUM>-<NUM> can include an indicator <NUM>-<NUM>, and event device <NUM>-<NUM> can include an indicator <NUM>-<NUM> (referred to collectively herein as indicators <NUM>). As used herein, the term "indicator" refers to a signaling mechanism.

According to the invention, the indicators <NUM> are visual indicators. For instance, the indicator <NUM>-<NUM> for the event device <NUM>-<NUM> can be a light emitting diode (LED) that, when activated, emits visible light so that a user of the mobile device <NUM> can locate the event device <NUM>-<NUM>.

In some examples, the indicator <NUM>-<NUM> can comprise an audible indicator. For instance, the indicator <NUM>-<NUM> for the event device <NUM>-<NUM> can comprise an audio output device (e.g., a speaker, buzzer, etc.) that, when activated emits an audible sound so that a user of the mobile device <NUM> can locate the event device <NUM>-<NUM>.

The mobile device <NUM> is connected to the control panel <NUM> via a gateway device <NUM>. As used herein, the term "gateway device" refers to a device to provide an interface between the control panel <NUM> and other devices. For example, the gateway device <NUM> can provide an interface between the mobile device <NUM> and the control panel <NUM>/event devices <NUM>.

As illustrated in <FIG>, the control panel <NUM> can be connected to the mobile device <NUM> via the gateway device <NUM> and a network <NUM>. As used herein, a mobile device can include devices that are (or can be) carried and/or worn by the user. Mobile device <NUM> can be a phone (e.g., a smart phone), a tablet, a personal digital assistant (PDA), smart glasses, and/or a wrist-worn device (e.g., a smart watch), among other types of mobile devices.

The mobile device <NUM> can be connected to the gateway device <NUM> via the network <NUM>. For example, the network <NUM> can provide for a network relationship between the mobile device <NUM> and the gateway device <NUM>/control panel <NUM>. Such a network relationship can be a wired or wireless network connection. Examples of such a network relationship can include a local area network (LAN), wide area network (WAN), personal area network (PAN), a distributed computing environment (e.g., a cloud computing environment), storage area network (SAN), Metropolitan area network (MAN), a cellular communications network, Long Term Evolution (LTE), visible light communication (VLC), Bluetooth, Worldwide Interoperability for Microwave Access (WiMAX), Near Field Communication (NFC), infrared (IR) communication, Public Switched Telephone Network (PSTN), radio waves, and/or the Internet, among other types of network relationships.

As described above, in some not claimed instances the mobile device <NUM> may not be in communication with the control panel <NUM>. For instance, a facility may not have a network relationship available such that the mobile device <NUM> is unable to be in communication with the network <NUM> (e.g., as illustrated by the dashed line in <FIG>). For example, a Wi-Fi connection via the network <NUM> may not be available for the mobile device <NUM> (e.g., as a result of renovation, new construction, etc.) As another not claimed example, the mobile device <NUM> may be located in an area of the facility having event devices <NUM> but may not have LTE connectivity available via the network <NUM> in such an area. Accordingly, the mobile device <NUM> can be in communication with the event devices <NUM> without being in communication with the network <NUM>, as is further described herein.

The mobile device <NUM> is configured to receive an inventory of the group <NUM> of event devices <NUM>. For instance, in some examples prior to losing communication with the network <NUM>, the mobile device <NUM> can receive, via the network <NUM>, an inventory of the group <NUM> of event devices <NUM> from the gateway device <NUM>. The inventory can include an amount of event devices for a facility, for a space in the facility, etc. For example, the inventory received by the mobile device <NUM> can include the event devices <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM> included in the group <NUM> of event devices.

Although the mobile device <NUM> is described above as receiving an inventory of the group <NUM> of event devices <NUM> from the gateway device <NUM>, embodiments of the present disclosure are not so limited. For example, the mobile device <NUM> can receive an inventory of the group <NUM> of event devices <NUM> from the remote computing device <NUM> via the network <NUM>, from another mobile device, and/or from any other source.

The control panel <NUM> can further transmit an enable signal to the group <NUM> of event devices <NUM>. For example, the enable signal can be transmitted from the control panel <NUM> to each of the event devices <NUM>. The enable signal can be transmitted to the group <NUM> when the control panel <NUM> is put in a service mode, such as during servicing and/or maintenance of the alarm system of the facility that includes the system <NUM>. Such an enable signal can cause each event device <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM> of the group <NUM> to enable their beacons <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, respectively. Such beacons <NUM> can be utilized to communicate with the mobile device <NUM> when the mobile device <NUM> is within range of the beacons <NUM>, as is further described herein.

A user, such as a technician, engineer, etc., may carry mobile device <NUM> into different areas of the facility. For example, the user may carry the mobile device <NUM> into an area of the facility having the group <NUM> of event devices <NUM> in order to perform various actions that can include auditing, maintenance, inspection, and/or other actions related to the event devices <NUM>. In a not claimed example, the user can utilize the mobile device <NUM> to perform such actions, even when a network relationship between the mobile device <NUM> and the network <NUM> is unavailable, as is further described herein.

The mobile device <NUM> is configured to determine a signal strength between the mobile device <NUM> and each beacon <NUM> of each event device <NUM> of the group <NUM>. When the mobile device <NUM> is within communication range of the beacons <NUM> of the event devices <NUM>, the mobile device <NUM> can determine a signal strength between the mobile device <NUM> and the beacons <NUM> of each event device <NUM> of the group <NUM>. For example, the mobile device <NUM> can determine a first signal strength between the mobile device <NUM> and the beacon <NUM>-<NUM> (e.g., -<NUM> decibels (dBm), a second signal strength between the mobile device <NUM> and the beacon <NUM>-<NUM> (e.g., - <NUM> dBm), and a third signal strength between the mobile device <NUM> and the beacon <NUM>-<NUM> (e.g., -<NUM> dBm). The signal strength can be, for instance, a received signal strength indicator (RSSI), although embodiments of the present disclosure are not limited to RSSI. Accordingly, the mobile device <NUM> can determine that it has the highest signal strength with the beacon <NUM>-<NUM> of the event device <NUM>-<NUM>, the lowest signal strength with the beacon <NUM>-<NUM> of the event device <NUM>-<NUM>, and that the signal strength with the beacon <NUM>-<NUM> of the event device <NUM>-<NUM> lies therebetween.

The mobile device <NUM> is configured to generate, using the inventory, a device identification analysis for the group <NUM> of event devices <NUM>. The device identification analysis for the group <NUM> of event devices <NUM> includes a list of event devices <NUM> included in the inventory, as is further described herein.

Such a list of event devices <NUM> included in the inventory is based on the signal strength between the mobile device <NUM> and each beacon <NUM> of each event device <NUM> included in the group <NUM>. The list based on the signal strength is sorted according to signal strength such that the event devices <NUM> can be included in the list from highest signal strength to lowest signal strength. For instance, the list of event devices <NUM> can include the event device <NUM>-<NUM> listed first having the beacon <NUM>-<NUM> having the highest signal strength with the mobile device <NUM>, the event device <NUM>-<NUM> can be listed second having the beacon <NUM>-<NUM> having the next highest signal strength with the mobile device <NUM>, and the event device <NUM>-<NUM> can be listed third as having the beacon <NUM>-<NUM> having the lowest signal strength with the mobile device <NUM>.

The mobile device <NUM> can include an indication of which beacon <NUM> of an event device <NUM> of the group has the highest signal strength with the mobile device <NUM>. As used herein, the term "indication" refers to a sign to direct attention to an item. As mentioned above, the event device <NUM>-<NUM> having the beacon <NUM>-<NUM> can include the highest signal strength to the mobile device of the group of event devices <NUM>. Accordingly, the mobile device <NUM> can include an indication to direct attention to a user of the mobile device <NUM> that the beacon <NUM>-<NUM> has the highest signal strength with the mobile device <NUM>. The indication can serve to easily notify a user of which of the event devices <NUM> of the group <NUM> has a beacon <NUM> that has the highest signal strength with the mobile device <NUM>. The indication can include, for example, color coding, a marking that is uniquely different from markings associated with other event devices <NUM> of the group <NUM>, among other types of indications, as is further described in connection with <FIG>.

The mobile device <NUM> is configured to display the device identification analysis. Although not illustrated in <FIG>, the mobile device <NUM> includes a user interface to display the device identification analysis. Such a user interface is further described in connection with <FIG>, <FIG>.

The user of the mobile device <NUM> can utilize the mobile device <NUM> to interact with event devices <NUM> of the group <NUM>. For example, the user of the mobile device <NUM> may utilize the mobile device <NUM> to interact with the event device <NUM>-<NUM> that has the beacon <NUM> having the highest signal strength with the mobile device <NUM>. The user can input information to the mobile device <NUM> to initiate an event device <NUM> to take an audit action, as is further described herein.

However, although the mobile device <NUM> is described above as interacting with the event device <NUM>-<NUM> that has the beacon <NUM> having the highest signal strength with the mobile device <NUM>, embodiments of the present disclosure are not so limited. For example, the user of the mobile device <NUM> may utilize the mobile device <NUM> to interact with any of the other event devices <NUM>-<NUM>, <NUM>-<NUM> that include beacons <NUM>-<NUM>, <NUM>-<NUM> having a signal strength with the mobile device <NUM>.

The mobile device <NUM> is configured to receive, via the device identification analysis, an input for the event device <NUM> of the group <NUM> to take an audit action. As used herein, the term "audit action" refers to an act taken in furtherance of an inspection and/or examination of a device to evaluate and/or improve the devices specified condition, operation, or state. For example, the mobile device <NUM> can receive an input (e.g., a user input) for event device <NUM>-<NUM> to take an audit action.

The audit action can include, for instance, modifying an address and/or a label of the event device <NUM>, recording inspection data about the event device <NUM>, causing the event device <NUM> to perform a maintenance self-test, generating a report, among other types of audit actions as are further described in connection with <FIG>. The mobile device <NUM> is configured to initiate the audit action to be taken by the event device <NUM> of the group <NUM> in response to the input.

Once the audit action is initiated by the event device <NUM>, the mobile device <NUM> can upload the audit action to a remote computing device <NUM>. For example, upon completion of the audit action by event device <NUM>-<NUM>, and upon the mobile device <NUM> establishing/re-establishing a network relationship via the network <NUM>, the mobile device <NUM> can upload the audit action taken by the event device <NUM>-<NUM> to the remote computing device <NUM>. For instance, the mobile device <NUM> may interact with the event device <NUM>-<NUM> to record inspection data about the event device <NUM>-<NUM> (e.g., event device <NUM>-<NUM> passed a visual inspection by a user of the mobile device <NUM>), and such information can be transmitted to the remote computing device <NUM> via the network <NUM> when such a network relationship is active between the mobile device <NUM> and the network <NUM>. Such uploading to the remote computing device <NUM> can ensure that audit actions taken by the event devices <NUM> via the mobile device <NUM> are properly synced in a cloud-computing environment (e.g., via remote computing device <NUM>), especially when the mobile device <NUM> does not have an established network relationship via the network <NUM>.

As described above, a user of the mobile device <NUM> can carry the mobile device <NUM> into different areas of a facility to perform various actions that can include auditing, maintenance, inspection, and/or other actions related to the event devices <NUM>. In some instances, a user may not be able to distinguish between two closely located event devices <NUM> (e.g., event device <NUM>-<NUM> and event device <NUM>-<NUM>). In such an instance, and when a network relationship between the mobile device <NUM> and the network <NUM> is established, the mobile device <NUM> can transmit an indicator signal to the gateway device <NUM> for the event device <NUM> of the group <NUM>.

For example, a user may have located event devices <NUM>-<NUM> and <NUM>-<NUM> in an area of the facility utilizing the mobile device <NUM>. The mobile device <NUM> can indicate that the event device <NUM>-<NUM> has the beacon <NUM>-<NUM> having the highest signal strength with the mobile device <NUM>. If the event device <NUM>-<NUM> is the event device <NUM> the user intends to interact with, the user can cause an input to the mobile device <NUM>. In response to the input, the mobile device <NUM> is configured to transmit an indicator signal via the network <NUM> to the gateway device <NUM>. The gateway device <NUM> can transmit the indicator signal to the event device <NUM>-<NUM> via the control panel <NUM>.

The event device <NUM>-<NUM> is configured to receive the indicator signal and emit an indicator in response to receiving the indicator signal. The event device <NUM>-<NUM> is configured to receive the indicator signal from the gateway device <NUM>/control panel <NUM> and emit an indicator. As described above, the indicator is a visual indicator, and optionally comprises an audible indicator. For instance, the event device <NUM>-<NUM> can activate an LED to emit a visible light (e.g., a strobe, continuous light, etc.) and activate an audio output device (e.g., a speaker, buzzer, etc.) to emit an audible sound. Such indicators can ensure a user of the mobile device <NUM> is interacting with the intended event device <NUM>.

<FIG> is an illustration of a display provided on a user interface <NUM> showing a device identification analysis <NUM> including a list <NUM>, generated in accordance with one or more embodiments of the present disclosure. The list <NUM> can include, for instance, information about event devices <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>.

As illustrated in <FIG>, the user interface <NUM> can be displayed on a mobile device. The mobile device is configured to generate a device identification analysis <NUM> which can be displayed via the user interface <NUM>. The device identification analysis <NUM> includes a list <NUM>.

As illustrated in <FIG>, the list <NUM> can include event devices <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM> (e.g., event devices <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, previously described in connection with <FIG>). As previously described in connection with <FIG>, such event devices <NUM> can each include a beacon. Accordingly, the list <NUM> includes a group of event devices <NUM> whose beacons have a signal strength with the mobile device.

The list <NUM> of event devices <NUM> is based on a signal strength between the mobile device and each beacon of each event device <NUM> included in a group of event devices <NUM>. The event devices <NUM> included in the list <NUM> can be listed from highest signal strength to lowest signal strength. For example, the event device <NUM>-<NUM> can have a beacon having the highest signal strength with the mobile device, the event device <NUM>-<NUM> can have a beacon having the lowest signal strength with the mobile device, and the event device <NUM>-<NUM> can have a beacon having a signal strength with the mobile device between that of the beacons of event device <NUM>-<NUM> and event device <NUM>-<NUM>.

As previously described in connection with <FIG>, there may be additional event devices in the facility. However, such devices may not include a beacon having a signal strength with the mobile device. In such an instance, those event devices having beacons that do not include a signal strength with the mobile device are not included in the list <NUM>.

<FIG> is an illustration of a display provided on a user interface <NUM> showing a device identification analysis <NUM> including color coded event devices <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>, generated in accordance with one or more embodiments of the present disclosure. The device identification analysis <NUM> can include a list <NUM> that can include, for instance, information about event devices <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>.

As previously described in connection with <FIG>, the mobile device is configured to display, on the user interface <NUM>, the device identification analysis <NUM>. The device identification analysis <NUM> can include the list <NUM> of event devices <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM> from highest signal strength to lowest signal strength. The device identification analysis <NUM> includes an indication of which event device <NUM> has the beacon <NUM> having the highest signal strength with the mobile device, and can include color coding, as is further described herein.

As illustrated in <FIG>, the list <NUM> of event devices <NUM> can be color coded based on the signal strength between the mobile device and each beacon of each event device <NUM> of the group. For example, as indicated in <FIG> by the solid rectangle adjacent to the event device <NUM>-<NUM>, the event device <NUM>-<NUM> can be color coded differently than the event devices <NUM>-<NUM> and <NUM>-<NUM> as the event device <NUM>-<NUM> can include a beacon that has a higher signal strength with the mobile device than beacons included in event devices <NUM>-<NUM> and <NUM>-<NUM>. That is, the event devices <NUM> included in the list <NUM> can be color coded according to the signal strength between the mobile device and the beacon of each event device <NUM>.

The event device <NUM>-<NUM> can be color coded differently than the other event devices <NUM>-<NUM> and <NUM>-<NUM>. For example, as illustrated in <FIG>, the event device <NUM>-<NUM> can include a solid rectangle adjacent to the event device <NUM>-<NUM>, whereas the event devices <NUM>-<NUM> and <NUM>-<NUM> can include white rectangles with a black border. Such a solid rectangle can represent color coding of the event device <NUM>-<NUM> indicating event device <NUM>-<NUM> has a beacon with a higher signal strength with the mobile device than beacons included in event devices <NUM>-<NUM> and <NUM>-<NUM>.

Although the event device <NUM>-<NUM> is illustrated in <FIG> and described above as including an indication comprising color coding to illustrate the event device <NUM>-<NUM> has the beacon having the highest signal strength with the mobile device, embodiments of the present disclosure are not so limited. For example, the event device <NUM>-<NUM> can include a unique marking (e.g., an "X", a circle, or other icon) to indicate to a user of the mobile device that the event device <NUM>-<NUM> has the beacon having the highest signal strength with the mobile device.

<FIG> is an illustration of a display provided on a user interface <NUM> showing a device identification analysis <NUM> including causing an audit action to be initiated, generated in accordance with one or more embodiments of the present disclosure. The device identification analysis <NUM> includes a list <NUM> that includes, for instance, information about event devices <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>.

As previously described in connection with <FIG>, the mobile device is arranged to display, on the user interface <NUM>, the device identification analysis <NUM>. The device identification analysis <NUM> can include the list <NUM> of event devices <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM> from highest signal strength to lowest signal strength.

The mobile device is configured to carr receive, via the device identification analysis <NUM> displayed on the user interface <NUM>, an input for an event device <NUM> in the list <NUM> to take an audit action. For example, the event device <NUM>-<NUM> is indicated in <FIG> as having a beacon having the highest signal strength with to the mobile device (e.g., by way of being color coded as such as well as being listed first in the list <NUM>). The mobile device can receive an input for the event device <NUM>-<NUM> to take an audit action, and the mobile device can initiate the audit action to be taken by the event device <NUM>-<NUM> in response to the input, as is further described herein. As another example, the mobile device can receive an input for the event device <NUM>-<NUM> to take an audit action, and the mobile device can initiate the audit action to be taken by the event device <NUM>-<NUM> in response to the input, as is further described herein.

In some examples, the mobile device can initiate the audit action to be taken for the event device <NUM>-<NUM> by modifying an address <NUM> of the event device <NUM>. For example, the address <NUM> for the event device <NUM>-<NUM> may be indicated on the user interface <NUM> as "N1. D1", and the user may notice that address <NUM> is incorrect. The user may modify the address <NUM> by entering an input to the mobile device at the device identification analysis <NUM>.

In addition and/or alternatively to modifying the address <NUM> of the event device <NUM>, the mobile device can initiate the audit action to be taken for the event device <NUM>-<NUM> by modifying a label <NUM> of the event device <NUM>. For example, the label <NUM> for the event device <NUM>-<NUM> may be indicated on the user interface <NUM> as "West Wing Exit Floor <NUM>", and the user may notice that label <NUM> is incorrect. The user may modify the label <NUM> by selecting a change label input <NUM> via the user interface <NUM> and can modify the label <NUM> accordingly.

Additional audit actions can include a maintenance self-test. The mobile device can initiate an audit action to be taken by causing the event device <NUM> to perform a maintenance self-test. For example, as previously described in connection with <FIG>, the event devices <NUM> can be automatic, self-test devices which can be performed in order to test the event device's specific sensing capabilities (e.g., smoke, CO, heat, etc.). The mobile device can cause the event device <NUM>-<NUM> to perform a maintenance self-test by selecting a maintenance self-test input <NUM> (e.g., "Start Self-Test") as illustrated in <FIG>. Further, in the event the event device <NUM>-<NUM> fails the maintenance self-test, the mobile device can cause the event device <NUM>-<NUM> to take other actions (e.g., take corrective measures, re-running the maintenance self-test, etc.).

The mobile device can initiate an audit action to be taken by recording, for an inspection, inspection data about the event device <NUM>. For example, the user of the mobile device may perform a visual inspection of the event device <NUM>-<NUM> and can record audible inputs about the event device <NUM>-<NUM> via an audio input device of the mobile device (e.g., a microphone), can record textual inputs about the event device <NUM>-<NUM> to the mobile device via the user interface <NUM>, can record photos and/or video of the event device <NUM>-<NUM> via an image capture device (e.g., a camera) of the mobile device, etc. Such visual (e.g., photos and/or video), audible, and/or textual inputs may include, for instance, images and/or descriptions of the event device <NUM>-<NUM> such as an image and/or description of the appearance of event device <NUM>-<NUM> (e.g., new, old, dirty, clean, etc.), an image and/or description of the location of the event device <NUM>-<NUM> (e.g., located behind a column near the ceiling, etc.), an image and/or description of the age of the event device <NUM>-<NUM>, among other examples.

The mobile device can generate a report about the audit action. For example, the mobile device can generate a report for the event device <NUM>-<NUM> detailing results of any maintenance self-tests executed, detailing inspection data, any address <NUM> or label <NUM> modifications, among other information. Further, the mobile device can add a signature to such a report, where the signature may be a predetermined signature associated with a user of the mobile device.

Lastly, the mobile device can upload the audit action to a remote computing device. For example, as previously described in connection with <FIG>, the mobile device can upload the audit action including any generated reports to a remote computing device upon establishing/re-establishing a network relationship via a network to ensure that any audit actions taken by the event devices <NUM> via the mobile device are properly synced.

In some instances, the event device <NUM> may detect an actual hazard event occurring in the facility. In such an instance, the mobile device can terminate the audit action in response to the hazard event being detected by the event device <NUM>. For example, while the user is recording inspection data for the event device <NUM>-<NUM>, the event device <NUM>-<NUM> may detect levels of CO in the building space that exceed a threshold amount and as a result determine a hazard event is occurring. The mobile device can, in response, terminate the recording of inspection data to allow the event device <NUM>-<NUM> to transmit information regarding the CO levels in the building space to a control panel.

<FIG> is an illustration of a display provided on a user interface <NUM> showing a device identification analysis <NUM> including receiving an input <NUM>, generated in accordance with one or more embodiments of the present disclosure. The input <NUM> can be made to the device identification analysis <NUM> displayed via the user interface <NUM>.

As illustrated in <FIG>, the mobile device can receive, via the device identification analysis <NUM> displayed on the user interface <NUM>, an input <NUM> that the inspection is completed. For example, a user may perform an inspection on the event device <NUM>-<NUM> and, once completed, indicate as such by providing the input <NUM> to the user interface <NUM>. The input can be, for example, a "swiping" motion where the user utilizes their finger to select the event device <NUM>-<NUM> and "swipes" across a screen of the mobile device displaying the user interface <NUM>. The mobile device can mark the inspection as completed in response to receiving the input.

Once the mobile device has received the input <NUM> indicating the audit action is completed, the mobile device can remove the event device <NUM> from the list <NUM> of event devices <NUM> in response to receiving the input <NUM>. For example, a user can complete the audit action for the event device <NUM>-<NUM> and "swipe" it from the list <NUM>. The mobile device can update the list <NUM> to remove the event device <NUM>-<NUM> from the list <NUM>. Removal from the list <NUM> can ensure a user does not perform further audit actions on the event device <NUM>-<NUM> that may be redundant.

As such, event device maintenance according to not claimed examples can allow for a user to utilize a mobile device to be in communication with and initiate audit actions to be taken by event devices in a facility, even in instances where the mobile device may not have a network relationship available. Such an approach can allow for the user of the mobile device to more easily determine and confirm which event device they are interacting with to avoid errors in the testing process, as compared with previous approaches.

<FIG> is an example of a mobile device <NUM> for event device maintenance, in accordance with one or more embodiments of the present disclosure. As illustrated in <FIG>, the mobile device <NUM> includes a memory <NUM> and a processor <NUM> for event device maintenance in accordance with the present invention.

The memory <NUM> can be any type of storage medium that can be accessed by the processor <NUM> to perform various examples of the present disclosure. For example, the memory <NUM> can be a non-transitory computer readable medium having computer readable instructions (e.g., executable instructions/computer program instructions) stored thereon that are executable by the processor <NUM> for event device maintenance in accordance with the present disclosure. The computer readable instructions can be executable by the processor <NUM> to redundantly generate an automated test analysis for event device maintenance.

The memory <NUM> can be volatile or nonvolatile memory. The memory <NUM> can also be removable (e.g., portable) memory, or non-removable (e.g., internal) memory. For example, the memory <NUM> can be random access memory (RAM) (e.g., dynamic random access memory (DRAM) and/or phase change random access memory (PCRAM)), read-only memory (ROM) (e.g., electrically erasable programmable read-only memory (EEPROM) and/or compact-disc read-only memory (CD-ROM)), flash memory, a laser disc, a digital versatile disc (DVD) or other optical storage, and/or a magnetic medium such as magnetic cassettes, tapes, or disks, among other types of memory.

In not claimed examples memory <NUM> can also be located internal to another computing resource (e.g., enabling computer readable instructions to be downloaded over the Internet or another wired or wireless connection).

As illustrated in <FIG>, mobile device <NUM> includes a user interface <NUM>. For example, the user interface <NUM> can display a device identification analysis (e.g., as previously described in connection with <FIG>, <FIG>, <FIG>, <FIG>) in a single integrated display. A user (e.g., operator) of mobile device <NUM> can interact with mobile device <NUM> via user interface <NUM>. User interface <NUM> is configured to provide (e.g., display and/or present) information to the user of mobile device <NUM>, and/or receive information from (e.g., input by) the user of mobile device <NUM>. For instance, in some embodiments, user interface <NUM> can be a graphical user interface (GUI) that can provide and/or receive information to and/or from the user of mobile device <NUM>. The display can be, for instance, a touch-screen (e.g., the GUI can include touch-screen capabilities). In not claimed alternatives, a display can include a television, computer monitor, mobile device screen, other type of display device, or any combination thereof, connected to mobile device <NUM> and configured to receive a video signal output from the mobile device <NUM>.

As an additional not claimed example, user interface <NUM> can include a keyboard and/or mouse the user can use to input information into mobile device <NUM>. Embodiments of the present disclosure, however, are not limited to a particular type(s) of user interface.

User interface <NUM> can be localized to any language. For example, user interface <NUM> can utilize any language, such as English, Spanish, German, French, Mandarin, Arabic, Japanese, Hindi, etc..

The scope of various embodiments of the disclosure should be determined with reference to the appended claims.

Claim 1:
A mobile device (<NUM>, <NUM>) for event device maintenance, comprising:
a user interface (<NUM>, <NUM>);
a memory (<NUM>); and
a processor (<NUM>) configured to execute executable instructions stored in the memory (<NUM>) to:
receive an inventory including a group (<NUM>) of event devices (<NUM>, <NUM>, <NUM>);
generate, using the inventory, a device identification analysis (<NUM>) for the group (<NUM>) of event devices (<NUM>, <NUM>, <NUM>) including:
a list (<NUM>) of the event devices (<NUM>, <NUM>, <NUM>) of the group (<NUM>) based on a signal strength between the mobile device (<NUM>, <NUM>) and each event device (<NUM>, <NUM>, <NUM>) of the group (<NUM>); and
an indication of which event device (<NUM>, <NUM>, <NUM>) of the group (<NUM>) has the highest signal strength with the mobile device (<NUM>, <NUM>);
display, on the user interface (<NUM>, <NUM>), the device identification analysis (<NUM>);
transmit, to a gateway device (<NUM>) in response to receiving a first input to the user interface (<NUM>, <NUM>), an indicator signal to cause a control panel to transmit the indicator signal to an event device (<NUM>, <NUM>, <NUM>) of the group (<NUM>) to cause the event device (<NUM>, <NUM>, <NUM>) to emit a visual indicator in response to receiving the indicator signal from the control panel to distinguish the event device (<NUM>, <NUM>, <NUM>) from other event devices (<NUM>, <NUM>, <NUM>) in the group (<NUM>);
receive, via the device identification analysis (<NUM>) displayed on the user interface (<NUM>, <NUM>), a second input for the event device (<NUM>, <NUM>, <NUM>) of the group (<NUM>) that has the highest signal strength with the mobile device (<NUM>, <NUM>) to take an audit action; and
initiate the audit action to be taken by an event device (<NUM>, <NUM>, <NUM>) of the group (<NUM>) in response to the second input.