Control and monitoring of battery-backed emergency lighting systems

[0009] As discussed above, battery backed emergency lighting systems require a considerable amount of routine monitoring and testing to ensure proper operation in the event of an emergency. However, currently available methods have many drawbacks including, wiring, a limited number of connections, a limited range, and the like.

[0010] Embodiments of the present disclosure provide the ability to remotely monitor and configure battery backed emergency lighting systems by configuring the battery backed emergency lighting systems with a Wireless Fidelity (WiFi) module that can communicate with a remotely located web server. The novel aspects of the present disclosure allow remotely located clients and endpoint devices to access the battery backed emergency lighting systems via the web server. As a result, the limitations and drawbacks of the

CA 02976012 2017-09-04

WO 2016/145143 PCT/US2016/021689

-3previously available methods to monitor and test the battery backed emergency lighting systems are eliminated.

[0011] FIG. 1 illustrates a high level block diagram of a communication network 100 of the present disclosure. In one embodiment, the network 100 may include an Internet Protocol (IP) network 102 that includes an application server (AS) 104. In one embodiment, the (AS) 104 may be deployed as a computer as illustrated and described below with respect to FIG. 3.

[0012] In one embodiment, the network 100 may include a battery backed emergency lighting system (BBELS) 106. In one embodiment, the BBELS 106 may include a WiFi module/Access Point 112, a battery 108 and a light emitting diode (LED) driver 110. In one embodiment, the LED driver 110 may include one or more LEDs. It should be noted that the BBELS 106 has been simplified and may include other components not shown. In addition, although a single BBELS 106 is illustrated In FIG. 1, the embodiments of the present disclosure may be used to request information from and/or request configuration changes for any number of BBELS 106 (e.g., multiple BBELS 106 in a single building, in multiple buildings, in various different locations, and the like).

[0013] In one embodiment, the BBELS 106 may be a lighting system that typically runs from a continuous power source (e.g., a standard 120 Volt outlet), which switches to the battery 108 if the continuous power source is disrupted. As discussed above, it is important that the BBELS 106 is properly configured to operate when power is lost and that the health and functionality of the battery 108 is periodically monitored and/or tested. Previously, the configuration and testing of the BBELS 106 was performed over a wired connection or using a wireless connection with a limited range. In other words, devices used to test the BBELS 106 would have to be within the limited range of the wireless connection or be directly wired to the BBELS 106.

[0014] In one embodiment of the present disclosure, the BBELS 106 is modified to include the WiFi module/Access Point 112. As a result, the BBELS 106 may be remotely configured or tested by remotely located endpoints 114 or 116 via the IP network 102 and the AS 104. In one

CA 02974012 2017-00-0«

WO 2016/145143 PCT/US2016/021689 embodiment the endpoints 114 or 116 may be any type of endpoint device including, such as for example, a smart phone, a tablet computer, a desktop computer, a laptop computer, a netbook computer, and the like.

(0015] In one embodiment, the endpoints 114 and 116 may be located at a different physical location (e.g., in another building, in another city, in another state, in another country, hundreds of miles away, and the like) than the BBELS 106. The endpoints 114 or 116 may be used to remotely configure and test the BBELS 106 from a much farther distance than previously possible using ZigBee communication protocols and without the need for a wired connection as with a DALI system.

[0016] In one embodiment, the AS 104 may host a web page that may be accessed by the endpoint 114 or 116 and used to request information related to the BBELS 106 and/or a request to change a configuration of the BBELS 106. In another embodiment, the WiFi module/Access Point 112 may host a web page that can be accessed by the endpoint 114 or 116 and used to request information related to the BBELS 106 and/or a request to change a configuration of the BBELS 106. A wireless communication session may be established between the AS 104 and the BBELS 106 via the Wi-Fi module/Access Point 112 to forward the requests to the BBELS 106.

[001 η In one embodiment, the wireless communication session may be established using the WiFi module/Access Point 112 as an access point and assigning a static IP address to a hosted web page. In another embodiment, the wireless communication session may be established using the WiFi module/Access Point 112 as a client having a dynamic host configuration protocol enabled that allows the WiFi module/Access Point 112 to be assigned any IP address and joining a WiFi network via a WiFi Protected Access (WPA) protocol.

[0018] In one embodiment, the request for information related to the BBELS 106 may include information related to the battery 108, a voltage of a light within the BBELS 106, a current of the light sources within the BBELS 106, and the like. For example, the information related to the battery 108 may include results of a battery health check, when the battery 108 was last replaced, when the battery 108 was last tested, a make and model of the

CA 02974012 2017-00-0«

WO 2016/145143 PCT/US2016/021689

-5battery 108, the last time the battery 108 was charged, how often the battery 108 was discharged, a history of when the BBELS 106 was operated in the battery back-up mode, and the like.

[0019] In one embodiment, the request to change the configuration of the BBELS 106 may include changing a schedule of automatic tests (e.g., automated battery tests, automated lighting tests, automated testing of a change over from the continuous power source to the battery 108, and the like), changing a light brightness profile when in a back-up mode, changing a light brightness profile during a normal operating mode, changing a configuration of the BBELS 106 to handle different power loads, and the like.

[0020] As a result, embodiments of the present disclosure allow the BBELS 106 to be accessed or re-configured remotely and wirelessly from a wider range than previously possible. As a result, maintaining, monitoring and checking the functionality of the BBELS 106 and the battery 108 of the BBELS 106 is made more convenient and efficient.

[0021] It should be noted that the communication network 100 has been simplified and that other access networks (e.g., cellular access networks, other IP networks, broadband communications networks, and the like) may be deployed between the Wi-Fi module/Access Point 112 and the IP network 102 and between the endpoints 114 and 116 and the IP network 102.

[0022] It should be noted that Wi-Fi is defined herein as a specific wireless communication technology that can be used to connect to the Internet (e.g., the AS 104 in the IP network 102) using the IEEE 802.11a/b/g/n standard. In another embodiment, Wi-Fi may be defined as a wireless communication technology that can be used to connect to the Internet (e.g., the AS 104 in the IP network 102) using a 2.4 Gigahertz (GHz) Ultra High Frequency (UHF) and 5 GHz Super High Frequency (SHF) radio waves. It should be noted that WiFi is not intended to include short range wireless communication protocols such as ZigBee, Bluetooth, general Radio Frequency (RF), and the like that may have a limited range and cannot be used to connect to the Internet.

[0023] FIG. 2 illustrates an example flowchart of one embodiment of a method 200 for remotely receiving information from and configuring a batterybacked emergency lighting system. In one embodiment, the steps, functions

CA 02974012 2017-00-0«

WO 2016/145143 PCT/US2016/021689

-6or operations of the method 200 may be performed by the AS 104 or a computer described below in FIG. 3.

[0024] The method 200 begins at step 202. At step 204, the method 200 establishes a wireless communication session with a web server via a WiFi connection. In one embodiment, the web server may be an application server located remotely in an IP network. In one embodiment, the WiFi connection may be established by the battery backed emergency lighting system that is configured with a WiFi module/Access Point.

[0025] In one embodiment, the wireless communication session may be established using the WiFi module/Access Point as an access point and assigning a static IP address to a hosted web page. In another embodiment, the wireless communication session may be established using the WiFi module/Access Point as a client having a dynamic host configuration protocol enabled that allows the WiFi module/Access Point to be assigned any IP address and joining a WiFi network via a WiFi Protected Access (WPA) protocol.

[0026] At step 206, the method 200 receives a request for information related to the battery-backed emergency lighting system and a request to change a configuration of the battery-backed emergency lighting system over the wireless communication system. In one embodiment, the request may be initiated from an endpoint device in communication with a web server (e g., the AS 104) and located remotely from the battery backed emergency lighting system.

[0027] In one embodiment, the request for information related to the battery-backed emergency lighting system may include information related to the battery, a voltage of a light within the battery-backed emergency lighting system, a current of the light sources within the battery-backed emergency lighting system, and the like. For example, the information related to the battery may include results of a battery health check, when the battery was last replaced, when the battery was last tested, a make and model of the battery, the last time the battery 108 was charged, how often the battery 108 was discharged, a history of when the BBELS 106 was operated in the battery back-up mode, and the like.

CA 02974012 2017-00-0«

WO 2016/145143 PCT/US2016/021689

-7[0028] In one embodiment, the request to change the configuration of the battery-backed emergency lighting system may include changing a schedule of automatic tests (e.g., automated battery tests, automated lighting tests, automated testing of a change over from the continuous power source to the battery, and the like), changing a light brightness profile when in a back-up mode, changing a light brightness profile during a normal operating mode, changing a configuration of the battery-backed emergency lighting system to handle different power loads, and the like.

[0029] At step 208, the method 200 configures the battery-backed emergency lighting system in accordance with the request to change the configuration. For example, the schedule of the automatic testing may be modified in accordance with the request, the light brightness profile may be changed (e.g., making the battery-backed emergency lighting system brighter or dimmer during a back-up mode), and the like.

[0030] At step 210, the method 200 sends the information that is requested. For example, the battery-backed emergency lighting system may send information related to the battery that was requested back to the endpoint that initiated the request via the WiFi module/Access Point and the AS in the IP network.

[0031] At optional step 212, the method 200 may send a confirmation that the configuration was successfully changed. In one embodiment, the confirmation may be sent via a text message, an email, or a pop message displayed on the web page that is accessed by the endpoints. The confirmation will allow the user to see that the request to change the configuration of the battery-backed emergency lighting system was successfully changed.

[0032] At decision step 214, the method 200 determines if additional requests are received. If additional requests for configuration changes and/or information are received, then the method 200 may return to step 206. The method 200 may then repeat steps 206-214.

[0033] However, if no additional requests are received, the wireless communication session may be terminated and the method 200 may proceed to step 216. At step 216 the method 200 ends.

CA 02974012 2017-00-0«

WO 2016/145143

PCT/US2016/021689

-8[0034} It should be noted that although not explicitly specified, one or more steps or operations of the method 200 described above may include a storing, displaying and/or outputting step as required for a particular application. In other words, any data, records, fields, and/or intermediate results discussed in the methods can be stored, displayed, and/or outputted to another device as required for a particular application. Furthermore, steps, operations or blocks in FIG. 2 that recite a determining operation, or involve a decision, do not necessarily require that both branches of the determining operation be practiced. In other words, one of the branches of the determining operation can be deemed as an optional step. Furthermore, operations, steps or blocks of the above described methods can be combined, separated, and/or performed in a different order from that described above, without departing from the example embodiments of the present disclosure.

[0035] FIG. 3 depicts a high-level block diagram of a computer that can be transformed to into a machine that is dedicated to perform the functions described herein. Notably, no computer or machine currently exists that performs the functions as described herein. As a result, the embodiments of the present disclosure improve the operation and functioning of the generalpurpose computer to develop complex queries, as disclosed herein.

[0036] As depicted in FIG. 3, the computer 300 comprises one or more hardware processor elements 302 (e.g., a Central Processing Unit (CPU), a microprocessor, or a multi-core processor), a memory 304, e.g., Random Access Memory (RAM) and/or Read Only Memory (ROM), a module 305 for remotely receiving information from and configuring a battery-backed emergency lighting system, and various input/output devices 306 (e.g., storage devices, including but not limited to, a tape drive, a floppy drive, a hard disk drive or a compact disk drive, a receiver, a transmitter, a speaker, a display, a speech synthesizer, an output port and an input port). Although only one processor element is shown, it should be noted that the generalpurpose computer may employ a plurality of processor elements.

[0037] It should be noted that the present disclosure can be implemented in software and/or in a combination of software and hardware, e.g., using application specific integrated circuits (ASIC), a programmable logic array

CA 02974012 2017-00-0«

WO 2016/145143 PCT/US2016/021689

-9(PLA), including a field-programmable gate array (FPGA), or a state machine deployed on a hardware device, a general purpose computer or any other hardware equivalents, e.g., computer readable instructions pertaining to the method(s) discussed above can be used to configure a hardware processor to perform the steps, functions and/or operations of the above disclosed methods. In one embodiment, instructions and data for the present module or process 305 for remotely receiving information from and configuring a batterybacked emergency lighting system (e.g., a software program comprising computer-executable instructions) can be loaded into memory 304 and executed by hardware processor element 302 to implement the steps, functions or operations as discussed above. Furthermore, when a hardware processor executes instructions to perform “operations,” this could include the hardware processor performing the operations directly and/or facilitating, directing, or cooperating with another hardware device or component (e.g., a co-processor and the like) to perform the operations.

[0038] The processor executing the computer readable or software instructions relating to the above described method(s) can be perceived as a programmed processor or a specialized processor. As such, the present module 305 for remotely receiving information from and configuring a batterybacked emergency lighting system (including associated data structures) of the present disclosure can be stored on a tangible or physical (broadly nontransitory) computer-readable storage device or medium, e.g., volatile memory, non-volatile memory, ROM memory, RAM memory, magnetic or optical drive, device or diskette and the like. More specifically, the computerreadable storage device may comprise any physical devices that provide the ability to store information such as data and/or instructions to be accessed by a processor or a computing device such as a computer or an application server.

[0039] While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of a preferred embodiment should not be limited by any of the above-described exemplary embodiments, but

CA 02976012 2017-09-04

WO 2016/145143

PCT/US2016/021689

-10should be defined only in accordance with the following claims and their equivalents.