Light fixture as access point in communication network

Abstract

The invention discloses a luminaire as an access point in a communication network. A luminaire is described herein. The luminaire may include a housing having at least one wall forming a cavity. The luminaire may also include a controller configured to control and communicate with at least one sensor located outside the housing. The luminaire may further include at least one luminaire component coupled to the controller and disposed within the cavity of the housing, where the controller further controls the at least one luminaire component.

Description

[0001] This application is a divisional application of the patent application with application number 201680049497.3 filed on February 26, 2018 and invention name “Lamp as an access point in a communication network”. Technical Field

[0002] The present disclosure relates generally to luminaires in wireless networks, and more particularly to systems, methods, and apparatus for luminaires serving as access points in a communication network. Background Art

[0003] In a wireless network, there are nodes and one or more access points that communicate with each other. Nodes send and receive data through access points, and access points send data to and receive other data from controllers within the wireless network. Data is sent and received within a communication network using a communication protocol. Summary of the invention

[0004] In general, in one aspect, the present disclosure is directed to a light fixture. The light fixture may include a housing including at least one wall forming a cavity. The light fixture may also include a controller configured to control and communicate with at least one sensor located outside the housing. The light fixture may further include at least one light fixture component coupled to the controller and disposed within the cavity of the housing, wherein the controller further controls the at least one light fixture component.

[0005] In another aspect, the present disclosure may generally be directed to a controller for a light fixture. The controller may include a memory, the memory including a plurality of instructions. The controller may also include a control engine coupled to the memory, wherein the controller is configured to send and receive communication signals with at least one sensor based on the plurality of instructions, wherein the at least one sensor is external to the light fixture. The controller may further include a communication module coupled to the control engine, wherein the communication module is configured to transmit the communication signals between the control engine and the at least one sensor. The control module may transmit the communication signals using at least one time synchronization communication protocol.

[0006] In yet another aspect, the present disclosure may generally relate to an electrical system. The electrical system may include at least one sensor and a light fixture communicatively coupled to the at least one sensor. The light fixture of the electrical system may include a housing including at least one wall forming a cavity. The light fixture of the electrical system may also include a controller that controls and communicates with the at least one sensor. The light fixture of the electrical system may further include at least one light fixture component that is coupled to the controller and disposed within the cavity of the housing, wherein the controller further controls the at least one light fixture component. The at least one sensor may be located outside the housing of the light fixture.

[0007] These and other aspects, objects, features and embodiments will become apparent from the following description and appended claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] The accompanying drawings illustrate only example embodiments and are therefore not to be considered as limiting the scope, as the example embodiments may admit of other equally effective embodiments. The elements and features shown in the accompanying drawings are not necessarily drawn to scale, but rather emphasize the principles of the example embodiments to be clearly illustrated. In addition, some dimensions or positions may be exaggerated to help visually convey such principles. In the accompanying drawings, reference numerals represent similar or corresponding but not necessarily identical elements.

[0009] Figure 1 A system diagram of a lighting system including a lamp is shown, according to certain example embodiments.

[0010] Figure 2 A computing device is shown in accordance with certain example embodiments.

[0011] Figure 3 A system diagram illustrating the architecture of a network communication system according to certain example embodiments.

[0012] 4 and 5 show system diagrams of network communication systems currently known in the art.

[0013] Figure 6 and 7 A system diagram of a network communication system is shown in accordance with certain example embodiments.

[0014] Figure 8 A network data frame architecture is shown in accordance with certain example embodiments. DETAILED DESCRIPTION

[0015] In general, example embodiments provide systems, methods, and apparatus for a luminaire used as an access point in a communication network. Example luminaires used as access points in a communication network provide a variety of benefits. Such benefits may include, but are not limited to, increased flexibility in sensor placement in the communication network, reduced power consumption, improved communication efficiency, ease of maintenance, and compliance with industry standards for electrical enclosures located in certain environments.

[0016] In some cases, the example embodiments discussed herein may be used in any type of hazardous environment, including, but not limited to, aircraft hangars, drilling rigs (for oil, gas, or water), production rigs (for oil or gas), refineries, chemical plants, power plants, mining operations, wastewater treatment facilities, and steel mills. A user may be anyone who interacts with the example light fixtures used as access points in a communication network. Examples of users may include, but are not limited to, engineers, electricians, instrument control technicians, mechanics, operators, consultants, contractors, and manufacturers' representatives.

[0017] The example luminaires (or components thereof, including controllers) described herein for use as access points in a communication network may be made of one or more of a variety of suitable materials to allow the luminaires and / or other related components of the system to meet certain standards and / or regulations while also maintaining durability in view of the one or more conditions to which the luminaires and / or other related components of the system may be exposed. Examples of such materials may include, but are not limited to, aluminum, stainless steel, fiberglass, glass, plastic, ceramic, and rubber.

[0018] The example lamps described herein for use as access points in a communication network, or portions thereof, may be made from a single part (e.g., from a mold, injection mold, die casting, or extrusion process). Additionally or alternatively, the example lamps for use as access points in a communication network may be made from multiple parts that are mechanically coupled to each other. In this case, the multiple parts may be mechanically coupled to each other using one or more of a variety of coupling methods including, but not limited to, epoxy resins, welding, fasteners, compression fittings, mating threads, and slotted fittings. The one or more parts that are mechanically coupled to each other may be coupled to each other in one or more of a variety of ways including, but not limited to, fixedly, hingedly, removably, slidably, and threadedly.

[0019] In the foregoing figures showing example embodiments of a luminaire for use as an access point in a communication network, one or more of the components shown may be omitted, repeated, and / or substituted. Thus, the example embodiments of a luminaire for use as an access point in a communication network should not be considered limited to the specific arrangement of components shown in any of the figures. For example, features shown in one or more figures or described with respect to one embodiment may be applicable to another embodiment associated with a different figure or description.

[0020] As defined herein, an electrical enclosure is any type of cabinet or housing within which electrical and / or electronic equipment is disposed. Such electrical and / or electronic equipment may include, but is not limited to, control modules, hardware processors, power modules (e.g., batteries, drivers, ballasts), sensor modules, safety barriers, sensors, sensor circuits, light sources, cables, and electrical conductors. Examples of electrical enclosures may include, but are not limited to, housings for light fixtures, housings for sensor devices, electrical connectors, junction boxes, motor control centers, circuit breaker boxes, electrical housings, conduits, control panels, indicator panels, and control cabinets.

[0021] In certain example embodiments, a luminaire used as an access point in a communication network is subject to certain standards and / or requirements. For example, the National Electrical Code (NEC), the National Electrical Manufacturers Association (NEMA), the International Electrotechnical Commission (IEC), the Federal Communications Commission (FCC), and the Institute of Electrical and Electronics Engineers (IEEE) set standards for electrical enclosures, wiring, and electrical connections. When necessary, the use of the example embodiments described herein satisfies (and / or allows the corresponding device to satisfy) such standards. In some (e.g., PV solar) applications, additional standards specific to the application may be met by the electrical enclosures described herein.

[0022] If a component of a figure is described but not explicitly shown or labeled in that figure, the label used for a corresponding component in another figure may be inferred for that component. Conversely, if a component in a figure is labeled but not described, the description of such a component may be substantially the same as the description of the corresponding component in another figure. The numbering scheme for the various components in the figures herein is such that each component is a three-digit number, and the corresponding components in the other figures have the same last two digits.

[0023] Example embodiments of a luminaire used as an access point in a communication network will be described more fully below with reference to the accompanying drawings, in which example embodiments of a luminaire used as an access point in a communication network are shown. However, the luminaire used as an access point in a communication network may be implemented in many different forms and should not be construed as limited to the example embodiments set forth herein. Rather, these example embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the luminaire used as an access point in a communication network to one of ordinary skill in the art. Similar, but not necessarily identical, elements (sometimes also referred to as components) in the various figures are represented by similar reference numerals for consistency.

[0024] Terms such as "first," "second," and "within" are used only to distinguish one component (or a portion of a component or a state of a component) from another. Such terms are not meant to express a preference or a particular orientation, and are not meant to limit the embodiment of the luminaire to being used as an access point in a communication network. In the following detailed description of example embodiments, numerous specific details are set forth to provide a thorough understanding of the invention. However, one of ordinary skill in the art will appreciate that the invention may be practiced without these specific details. In other instances, well-known features have not been described in detail to avoid unnecessarily complicating the description.

[0025] Figure 1 A system diagram of a lighting system 100 including a luminaire 102 is shown in accordance with certain example embodiments. The lighting system 100 may include one or more sensors 160, a user 150, a network manager 180, and the luminaire 102. The luminaire 102 may include a controller 104, a power module 140, a plurality of luminaire components 142, and an optional safety barrier 136. The controller 104 may include one or more of a plurality of components. Such components may include, but are not limited to, a control engine 106, a communication module 108, a timer 110, a power module 112, a repository 130, a hardware processor 120, a memory 122, a transceiver 124, an application program interface 126, and an optional safety module 128. Figure 1 The components shown in are not exhaustive, and in some embodiments, Figure 1 One or more of the components shown in the example luminaire 102 may not be included in the example luminaire 102. Any component of the example luminaire 102 may be discrete or combined with one or more other components of the luminaire 102.

[0026] The user 150 is the same as the user defined above. The user 150 may use a user system (not shown) that may include a display (e.g., a GUI). The user 150 interacts with the controller 104 of the luminaire 102 via an application program interface 126 (described below) (e.g., sends data to the controller, receives data from it). The user 150 may also interact with the network manager 180 and / or one or more sensors 160. Communication links 105 are used to interact between the user 150 and the luminaire 102, the network manager 180, and the sensors 160. Each communication link 105 may include wired (e.g., Class 1 cable, Class 2 cable, electrical connector) and / or wireless (e.g., Wi-Fi, visible light communication, cellular network, Bluetooth, WirelessHART, ISA100, power line carrier, RS485, DALI) technology. For example, the communication link 105 may be (or include) one or more electrical conductors coupled to the housing 103 of the luminaire 102 and coupled to the sensor 160. The communication link 105 may transmit signals (eg, power signals, communication signals, control signals, data) between the light fixture 102 and a user 150 , a network manager 180 , and / or one or more sensors 160 .

[0027] The network manager 180 is a device or component that controls all or a portion of a communication network that includes the controller 104 of the light fixtures 102 and the sensor 160 that is communicatively coupled to the controller 104. The network manager 180 may be substantially similar to the controller 104. Alternatively, the network manager 180 may include one or more of a number of features that are in addition to or altered from the features of the controller 104 described below.

[0028] The one or more sensors 160 may be any type of sensing device that measures one or more parameters. Examples of types of sensors 160 may include, but are not limited to, passive infrared sensors, photocells, pressure sensors, airflow monitors, gas detectors, and resistance temperature detectors. Parameters that may be measured by sensors 160 may include, but are not limited to, motion, amount of ambient light, space occupancy, and ambient temperature. In some cases, the parameter or parameters measured by sensors 160 may be used to operate one or more fixture components 142 of fixture 102. Each sensor 160 may use one or more of a plurality of communication protocols.

[0029] In certain example embodiments, the sensor 160 may include a battery that is used to at least partially power some or all of the rest of the sensor 160. When the system 100 (or at least the sensor 160) is located in a hazardous environment, the sensor 160 may be intrinsically safe. As used herein, the term "intrinsically safe" refers to a device (e.g., a sensor described herein) that is placed in a hazardous environment. To ensure intrinsic safety, the device uses limited electrical energy so that a short circuit or fault does not produce a spark (which could result in ignition of explosive gases found in a hazardous environment). Safety barriers are often used with intrinsically safe devices, where the safety barrier limits the amount of power delivered to the sensor or other device to reduce the risk of explosions, fires, or other adverse conditions that may be caused by large amounts of power in a hazardous environment.

[0030] According to one or more example embodiments, the user 150, the network manager 180, and / or the sensor 160 may interact with the controller 104 of the light fixture 102 using the application interface 126. Specifically, the application interface 126 of the controller 104 receives data (e.g., information, communications, instructions) from and sends data (e.g., information, communications, instructions) to the user 150, the network manager 180, and / or each sensor 160. In certain example embodiments, the user 150, the network manager 180, and / or each sensor 160 may include an interface to receive data from and send data to the controller 104. Examples of such an interface may include, but are not limited to, a graphical user interface, a touch screen, an application interface, a keyboard, a monitor, a mouse, a network service, a data protocol adapter, some other hardware and / or software, or any suitable combination thereof.

[0031] In certain example embodiments, the controller 104, user 150, network manager 180, and / or sensor 160 may use their own system or a shared system. Such a system may be an Internet-based or intranet-based computer system capable of communicating with various software, or a form thereof. The computer system includes any type of computing device and / or communication device, including but not limited to the controller 104. Examples of such systems may include but are not limited to desktop computers with LAN, WAN, Internet or intranet access, laptops with LAN, WAN, Internet or intranet access, smart phones, servers, server farms, Android devices (or equivalent), tablets, smartphones, and personal digital assistants (PDAs). Such a system may correspond to the following description of Figure 2 Describe the computer system.

[0032] Further, as discussed above, such a system may have corresponding software (e.g., user software, sensor software, controller software, network manager software). According to some example embodiments, the software may be executed on the same or separate devices (e.g., servers, mainframes, desktop personal computers (PCs), laptop computers, personal desktop assistants (PDAs), televisions, cable boxes, satellite boxes, all-in-ones, phones, mobile phones, or other computing devices), and may be coupled to wired and / or wireless segments via communication networks (e.g., the Internet, intranets, extranets, local area networks (LANs), wide area networks (WANs), or other network communication methods) and / or communication channels. The software of one system may be part of the software of another system within the system 100, or operate separately from but in conjunction with the software of other systems.

[0033] The luminaire 102 may include a housing 103. The housing 103 may include at least one wall that forms the cavity 101. In some cases, the housing may be designed to comply with any applicable standards so that the luminaire 102 may be located in a particular environment (e.g., a hazardous environment). For example, if the luminaire 102 is located in an explosive environment, the housing 103 may be explosion proof. According to applicable industry standards, an explosion proof enclosure is an enclosure that is configured to contain an explosion that originates from within the enclosure or that may propagate through the enclosure.

[0034] Continuing with this example, the explosion proof enclosure is configured to allow gases from the interior of the enclosure to escape from a joint of the enclosure and cool as the gases exit the explosion proof enclosure. A joint is also known as a fire path and exists where two surfaces meet and provide a path from the interior of the explosion proof enclosure to the exterior of the explosion proof enclosure along which one or more gases can travel. A joint can be the mating of any two or more surfaces. Each surface can be any type of surface including, but not limited to, a flat surface, a threaded surface, and a serrated surface.

[0035] The housing 103 of the lamp 102 may be used to house one or more components of the lamp 102, including one or more components of the controller 104. For example, Figure 1 As shown in FIG, the controller 104 (in this case including the control engine 106, the communication module 108, the timer 110, the power module 112, the storage library 130, the hardware processor 120, the memory 122, the transceiver 124, the application program interface 126 and the optional security module 128), the power module 140 and the light fixture components 142 are disposed in the cavity 101 formed by the housing 103. In alternative embodiments, any one or more of these or other components of the light fixture 102 may be disposed on the housing 103 and / or remote from the housing 103.

[0036] The repository 130 may be a persistent storage device (or a group of devices) that stores software and data used to help the controller 104 communicate with the user 150, the network manager 180, and the one or more sensors 160 in the system 100. In one or more example embodiments, the repository 130 stores one or more communication protocols 132 and sensor data 134. The communication protocol 132 may be any of a plurality of protocols used to send and / or receive data between the controller 104 and the user 150, the network manager 180, and the one or more sensors 160. The one or more communication protocols 132 may be a time synchronization protocol. Examples of such time synchronization protocols may include, but are not limited to, the Highway Addressable Remote Sensor (HART) protocol, the Wireless HART protocol, and the International Society of Automation (ISA) 100 protocol. In this way, the one or more communication protocols 132 may provide a security layer to the data transmitted within the system 100.

[0037] The sensor data 134 may be any data associated with each sensor 160 that is communicatively coupled to the controller 104. Such data may include, but is not limited to, the manufacturer of the sensor 160, the model of the sensor 160, the communication capabilities of the sensor 160, the power requirements of the sensor 160, and the measurements taken by the sensor 160. Examples of the repository 130 may include, but are not limited to, a database (or multiple databases), a file system, a hard drive, flash memory, some other form of solid-state data storage device, or any suitable combination thereof. According to some example embodiments, the repository 130 may be located on multiple physical machines, each of which stores all or a portion of the communication protocol 132 and / or the sensor data 134. Each storage unit or device may be physically located in the same or different geographic locations.

[0038] The repository 130 is operably connected to the control engine 106. In one or more example embodiments, the control engine 106 includes functionality to communicate with the users 150, the network manager 180, and the sensors 160 in the system 100. More specifically, the control engine 106 sends information to and / or receives information from the repository 130 in order to communicate with the users 150, the network manager 180, and the sensors 160. As discussed below, in certain example embodiments, the repository 130 is also operably connected to the communication module 108.

[0039] In certain example embodiments, the control engine 106 of the controller 104 controls the operation of one or more components (e.g., the communication module 108, the timer 110, the transceiver 124) of the controller 104. For example, the control engine 106 may place the communication module 108 in a "sleep" mode when there is no communication between the controller 104 and another component in the system 100 (e.g., the sensor 160, the user 150) or when the communication between the controller 104 and another component in the system 100 follows a regular pattern. In this case, power consumed by the controller 104 is conserved by only enabling the communication module 108 when the communication module 108 is needed.

[0040] As another example, the control engine 106 can direct when the timer 110 provides the current time, begins tracking a time period, and / or performs another function within the capabilities of the timer 110. As yet another example, the control engine 106 can direct the power module 112 to send power signals and / or stop sending power signals to one or more sensors 160 in the system 100. This example provides another situation in which the control engine 106 can conserve power used by the controller 104 and other components of the system 100.

[0041] The control engine 106 may provide control, communication, and / or other similar signals to the user 150, the network manager 180, and the one or more sensors 160. Similarly, the control engine 106 may receive control, communication, and / or other similar signals from the user 150, the network manager 180, and the one or more sensors 160. The control engine 106 may control each sensor 160 automatically (e.g., based on one or more algorithms stored in the control engine 106) and / or based on control, communication, and / or other similar signals received from another device via the communication link 105. The control engine 106 may include a printed circuit board on which one or more discrete components of the hardware processor 120 and / or the controller 104 are located.

[0042] In certain example embodiments, the control engine 106 may include an interface that enables the control engine 106 to communicate with one or more components of the luminaire 102 (e.g., the power module 140). For example, if the power module 140 of the luminaire 102 operates under IEC standard 62386, the power module 140 may include a digital addressable lighting interface (DALI). In such a case, the control engine 106 may also include the DALI to enable communication with the power module 140 within the luminaire 102. Such an interface may operate in conjunction with or independently of the communication protocol 132 used to communicate between the controller 104 and the user 150, the network manager 180, and the sensor 160.

[0043] The control engine 106 (or other components of the controller 104) may also include one or more hardware and / or software architecture components to perform its functions. Such components may include, but are not limited to, a universal asynchronous receiver-transmitter (UART), a serial peripheral interface (SPI), a direct attached capacity (DAC) storage device, an analog-to-digital converter, an inter-integrated circuit (I2C), and a pulse width modulator (PWM).

[0044] By using the control engine 106 as described herein, the controller 104 can (e.g., using the communication link 105) act as an access point in the communication network of the system 100. In other words, while at least a portion of the controller 104 (e.g., the control engine 106) is always on, the rest of the controller 104 and the sensor 160 can be in a sleep mode when not in use. In addition, the controller 104 can control the sensor 160 rather than just collect data measured by the sensor 160, which allows the controller 104 to act as an access point rather than a node in the communication network of the system 100.

[0045] The communication network of the system 100 may have any type of network architecture. For example, the communication network of the system 100 may be a mesh network. As another example, the communication network of the system 100 may be a star network. In any case, the controller 104 acts as an access point, thereby saving power. When the controller 104 includes an energy storage device (e.g., a battery as part of the power module 112), more power can be saved in the operation of the system 100. In addition, using the time synchronization communication protocol 132 described herein, the data transmitted between the controller 104 and the user 150, the network manager 180, and the sensor 160 is secure.

[0046] The communication module 108 of the controller 104 determines and implements a communication protocol (e.g., the communication protocol 132 from the repository 130) used when the control engine 106 communicates with (e.g., sends signals to, receives signals from) the user 150, the network manager 180, and / or one or more sensors 160. In some cases, the communication module 108 accesses the sensor data 134 to determine which communication protocols are within the capabilities of the recipient of the communication sent by the control engine 106. In addition, the communication module 108 can interpret the communication protocol of the communication received by the controller 104 so that the control engine 106 can interpret the communication.

[0047] The communication module 108 may send data (e.g., communication protocol 132, sensor data 134) directly to the repository 130 and / or retrieve data directly from the repository 130. Alternatively, the control engine 106 may facilitate the transfer of data between the communication module 108 and the repository 130. The communication module 108 may also provide encryption for data sent by the controller 104 and decryption for data received by the controller 104. The communication module 108 may also provide one or more of a variety of other services for data sent from and received by the controller 104. Such services may include, but are not limited to, data packet routing information and procedures to follow in the event of a data interruption.

[0048] The timer 110 of the controller 104 can track clock time, time intervals, amounts of time, and / or any other measure of time. The timer 110 can also count the number of occurrences of an event, which is independent of time. Alternatively, the control engine 106 can perform the counting function. The timer 110 is capable of tracking multiple time measurements simultaneously. The timer 110 can track time periods based on instructions received from the control engine 106, based on instructions received from the user 150, based on instructions programmed in the software of the controller 104, based on some other condition, or from other components, or from any combination thereof.

[0049] The power module 112 of the controller 104 provides power to one or more other components of the controller 104 (e.g., the timer 110, the control engine 106). Additionally, in certain example embodiments, the power module 112 may provide power to the power module 140 of the light fixture 102. The power module 112 may include one or more of a plurality of single or multiple discrete components (e.g., transistors, diodes, resistors) and / or a microprocessor. The power module 112 may include a printed circuit board on which the microprocessor and / or one or more discrete components are located.

[0050] The power module 112 may include one or more components (e.g., transformer, diode bridge, inverter, converter) that receive power from a source external to the light fixture 102 (e.g., via a cable) and generate power of a type (e.g., AC, DC) and level (e.g., 12V, 24V, 120V) that can be used by other components of the controller 104 and / or by the power module 140. Additionally or alternatively, the power module 112 itself may be a power source to provide signals to the controller 104 and / or other components of the power module 140. For example, the power module 112 may be a battery. As another example, the power module 112 may be a local photovoltaic power system.

[0051] In certain example embodiments, the power module 112 of the controller 104 may also directly or indirectly provide power and / or control signals to one or more sensors 160. In this case, the control engine 106 may direct the power generated by the power module 112 to the sensor 160 and / or the power module 140 of the light fixture 102. In this way, when the sensor 160 and / or the power module 140 of the light fixture 102 requires power, as determined by the control engine 106, power may be saved by sending power to these devices.

[0052] According to one or more example embodiments, the hardware processor 120 of the controller 104 executes software. Specifically, the hardware processor 120 may execute software on the control engine 106 or any other portion of the controller 104 and execute software used by the user 150, the network manager 180, and / or one or more sensors 160. In one or more example embodiments, the hardware processor 120 may be an integrated circuit, a central processing unit, a multi-core processing chip, a multi-chip module including a plurality of multi-core processing chips, or other hardware processor. The hardware processor 120 is known by other names, including but not limited to a computer processor, a microprocessor, and a multi-core processor.

[0053] In one or more example embodiments, the hardware processor 120 executes software instructions stored in the memory 122. The memory 122 includes one or more cache memories, main memory, and / or any other suitable type of memory. According to some example embodiments, the memory 122 is located within the controller 104 separately from the hardware processor 120. In some configurations, the memory 122 may be integrated with the hardware processor 120.

[0054] In certain example embodiments, the controller 104 does not include a hardware processor 120. In this case, as an example, the controller 104 may include one or more field programmable gate arrays (FPGAs). The use of FPGAs and / or other similar devices known in the art allows the controller 104 (or portions thereof) to be programmed and to function according to certain logic rules and thresholds but without the use of a hardware processor.

[0055] The transceiver 124 of the controller 104 can send and / or receive control and / or communication signals. Specifically, the transceiver 124 can be used to transfer data between the controller 104 and the user 150, the network manager 180 and / or the sensor 160.

[0056] The transceiver 124 may use wired and / or wireless technology. The transceiver 124 may be configured in such a way that control and / or communication signals sent and / or received by the transceiver 124 may be received and / or sent by another transceiver as part of the user 150 , the network manager 180 , and / or the sensor 160 .

[0057] When the transceiver 124 uses wireless technology, the transceiver 124 can use any type of wireless technology to send and receive signals. Such wireless technology may include, but is not limited to, Wi-Fi, visible light communication, cellular networks, and Bluetooth. When sending and / or receiving signals, the transceiver 124 can use one or more of any number of suitable communication protocols (e.g., ISA100, HART). Such communication protocols can be stored in the communication protocols 132 of the repository 130. Further, any transceiver information of the user 150, the network manager 180, and / or the sensor 160 can be part of the sensor data 134 (or similar area) of the repository 130.

[0058] Optionally, in one or more example embodiments, the security module 128 secures interactions between the controller 104, the user 150, the network manager 180, and / or the sensor 160. More specifically, the security module 128 authenticates communications from software based on a security key that verifies the identity of the source of the communication. For example, user software may be associated with a security key that enables the user's 150 software to interact with the controller 104 and / or the sensor 160. Further, in some example embodiments, the security module 128 may restrict the receipt of information, the request for information, and / or the access to information.

[0059] As mentioned above, in addition to the controller 104 and its components, the lamp 102 may include a power module 140, one or more lamp components 142, and an optional safety barrier 136. The lamp components 142 of the lamp 102 are devices and / or components typically found in a lamp for allowing operation of the lamp 102. The lamp components 142 may be electrical, electronic, mechanical, or any combination thereof. The lamp 102 may have one or more of any number and / or type of lamp components 142. Examples of such lamp components 142 may include, but are not limited to, control modules, light sources, light engines, heat sinks, electrical conductors or cables, junction boxes, lenses, diffusers, reflectors, vents, baffles, dimmers, and circuit boards.

[0060] The power module 140 of the lamp 102 provides power to one or more lamp components 142. The power module 140 may be substantially the same as or different from the power module 112 of the controller 104. The power module 140 may include one or more of a plurality of single or multiple discrete components (e.g., transistors, diodes, resistors) and / or a microprocessor. The power module 140 may include a printed circuit board on which the microprocessor and / or one or more discrete components are located.

[0061] The power module 140 may include one or more components (e.g., a transformer, a diode bridge, an inverter, a converter) that receive power from the power module 112 of the controller 104 (e.g., via a cable) and generate power of a type (e.g., AC, DC) and level (e.g., 12V, 24V, 120V) that can be used by the light fixture components 142. Additionally or alternatively, the power module 140 may receive power from a source external to the light fixture 102. Additionally or alternatively, the power module 140 itself may be a power source. For example, the power module 140 may be a battery, a local photovoltaic power system, or some other independent power source.

[0062] The optional safety barrier 136 may provide protection (e.g., overvoltage protection, overcurrent protection) for one or more components of the lamp 102 when the lamp 102 is located in a hazardous environment. For example, the safety barrier 136 may limit the amount of power delivered to the power module 112 of the controller 104 to reduce the risk of explosion, fire, or other adverse conditions that may be caused by large amounts of power in a hazardous environment. The safety barrier 136 may generally be a required component when the lamp 102 is located in a hazardous environment. The safety barrier 136 may include one or more of a plurality of single or multiple discrete components (e.g., capacitors, inductors, transistors, diodes, resistors, fuses) and / or a microprocessor.

[0063] As described above, the luminaire 102 can be placed in any of a number of environments. In such cases, the housing 102 of the luminaire 102 can be configured to comply with applicable standards for use in any of a number of environments. For example, under the NEC standard, the luminaire 102 can be rated as a first section or a second section housing. Similarly, any of the sensors 160 or other devices communicatively coupled to the luminaire 102 can be configured to comply with applicable standards for use in any of a number of environments. For example, under the NEC standard, the sensor 160 can be rated as a first section or a second section housing.

[0064] Figure 2 An embodiment of a computing device 218 is illustrated that implements one or more of the various techniques described herein and that is representative, in whole or in part, of elements described herein, in accordance with certain exemplary embodiments. The computing device 218 is an example of a computing device and is not intended to suggest any limitation on the scope of use or functionality of the computing device and / or its possible architecture. The computing device 218 should also not be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the example computing device 218.

[0065] The computing device 218 includes one or more processors or processing units 214, one or more memory / storage components 215, one or more input / output (I / O) devices 216, and a bus 217 that allows the various components and devices to communicate with each other. The bus 217 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. The bus 217 includes wired and / or wireless buses.

[0066] The memory / storage component 215 represents one or more computer storage media. The memory / storage component 215 includes volatile media (such as random access memory (RAM)) and / or non-volatile media (such as read-only memory (ROM), flash memory, optical disks, magnetic disks, etc.). The memory / storage component 215 includes fixed media (e.g., RAM, ROM, fixed hard disk drives, etc.) and removable media (e.g., flash memory drives, removable hard disk drives, optical disks, etc.).

[0067] One or more I / O devices 216 allow a customer, utility, or other user to input commands and information to computing device 218, and also allow information to be presented to the customer, utility, or other user and / or other components or devices. Examples of input devices include, but are not limited to, keyboards, cursor control devices (e.g., mice), microphones, touch screens, and scanners. Examples of output devices include, but are not limited to, display devices (e.g., monitors or projectors), speakers, outputs for lighting networks (e.g., DMX cards), printers, and network cards.

[0068] Various techniques are described herein in the general context of software or program modules. Typically, software includes routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. Implementations of these modules and techniques are stored on or transmitted across some form of computer-readable media. A computer-readable medium is any available non-transitory medium or non-transitory medium that can be accessed by a computing device. By way of example and not limitation, computer-readable media includes "computer storage media."

[0069] "Computer storage media" and "computer-readable media" include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Computer storage media include, but are not limited to, computer-readable media such as RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage devices, magnetic cassettes, magnetic tape, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer.

[0070] According to some exemplary embodiments, the computer device 218 is connected to a network (not shown) (e.g., a local area network (LAN), a wide area network (WAN) such as the Internet, or any other similar type of network) via a network interface connection (not shown). It will be appreciated by those skilled in the art that there are many different types of computer systems (e.g., desktop computers, laptop computers, personal media devices, mobile devices such as cellular phones or personal digital assistants, or any other computing system capable of executing computer-readable instructions), and in other exemplary embodiments, the above-mentioned input and output devices take other forms now known or later developed. In general, the computer system 218 includes at least the minimum processing, input and / or output devices necessary to practice one or more embodiments.

[0071] Further, it will be appreciated by those skilled in the art that in certain exemplary embodiments, one or more elements of the above-mentioned computer device 218 are located at a remote location and are connected to other elements via a network. Further, one or more embodiments are implemented on a distributed system with one or more nodes, wherein each part of the implementation scheme (e.g., control engine 106) is located on different nodes within the distributed system. In one or more embodiments, the node corresponds to a computer system. Alternatively, in some exemplary embodiments, the node corresponds to a processor with associated physical memory. In some exemplary embodiments, the node alternatively corresponds to a processor with shared memory and / or resources.

[0072] Figure 3 A system diagram illustrating the architecture of a network communication system 300 according to certain example embodiments. Figures 1 to 3 , Figure 3 The system 300 includes a network manager 380 that is communicatively coupled to three different luminaires: luminaire A 302-1, luminaire B 302-2, and luminaire C 302-3 using communication links 305. In certain example embodiments, the luminaires may be referred to as "hoppers."

[0073] Each light fixture in the system 300 can be configured to be communicatively coupled to one or more other light fixtures in the system 300 using a communication link 305. The system 300 also includes a total of six sensors: sensor A 360-1, sensor B 360-2, sensor C 360-3, sensor D 360-4, sensor E 360-5, and sensor F 360-6. Sensor A 360-1 and sensor B 360-2 are communicatively coupled to light fixture A 302-1 using a communication link 305. Sensor C 360-3 and sensor D 360-4 are communicatively coupled to light fixture B 302-2 using a communication link 305. Sensor E 360-5 and sensor F 360-6 are communicatively coupled to light fixture C 302-3 using a communication link 305. Figure 3 The one or more sensors 360 may be at least partially powered by a battery. The sensor 360 directly communicatively coupled to the light fixture 302 may measure one or more parameters that affect the operation of the light fixture 302 or have no effect on the operation of the light fixture 302.

[0074] In other words, Figure 3 The network manager 380 in the system 300 does not communicate directly with any sensor in the system 300. In certain example embodiments, the network manager 380 is unaware of the presence of the sensor 360 or any other device to which the network manager 380 is not directly communicatively coupled. In this way, because the number of devices to which the network manager 380 can be directly communicatively coupled is limited (e.g., the network manager 380 only has 250 channels under the wireless HART communication protocol), the system 300 can be expanded by allowing one or more example light fixtures 302 to adopt direct communication and control of sensors 360 and other remote devices.

[0075] This is different from network communication systems currently known in the art, examples of which are shown in Figures 4 and 5. Specifically, Figure 4 shows a network communication system 400 currently known in the art, and Figure 5 shows a network communication system 500 currently known in the art. Figure 1 4 includes a network manager 480 communicatively coupled to sensor A 490-1 using a communication link 405. Sensor A 490-1 is communicatively coupled to sensor B 490-2 using a communication link 405. Sensor B 490-2 is communicatively coupled to sensor C 490-3 using a communication link 405.

[0076] In this case, the sensors of FIG. 4 (sensor A 460-1, sensor B 460-2, sensor C 460-3) are substantially the same as the example sensors described herein (e.g., sensor 160), except that the sensors of FIG. 4 include one or more of a plurality of components (such as a controller) that allow the sensors to communicate bidirectionally with one or more devices in the system 400. The system 400 of FIG. 4 does not include a light fixture. Instead, sensor A 490-1 acts as a relay for any communications with the network manager 480, and sensor B 490-2 acts as a relay for any communications with the network manager 480, which is not intended solely for sensor A 490-1. As a result, sensor A 490-1 is essentially always "on," consuming a significantly greater amount of power relative to the amount of power consumed by the sensors in the example embodiment. Similarly, but to a lesser extent, sensor B 490-2 consumes more power relative to the power consumed by the sensors in the example embodiment.

[0077] The system 500 of FIG. 5 includes a network manager 580 that is communicatively coupled to light source A 592-1 using a communication link 505. Light source A 592-1 is communicatively coupled to light source B 592-2 and light source C 592-3, and light source B 592-2 and light source C 592-3 are communicatively coupled to light source D 592-4 using a communication link 505. Each light source 592 in FIG. 5 is substantially similar to the example luminaires (e.g., luminaire 102) described herein, except that the light sources in the system 500 of FIG. 5 do not have a controller (e.g., controller 104). Therefore, because none of the luminaires of FIG. 5 include a controller, the light sources in FIG. 5 (e.g., light source A 592-1) merely act as a relay for any communications associated with the network manager 480. As a result, each light source in the system 500 of FIG. 5 consumes a significantly greater amount of power relative to the power consumed by the light sources of the system in the example embodiment. In addition, there are no sensors in the system 500.

[0078] Figure 6 and 7 A system diagram of a network communication system according to some example embodiments is shown. Specifically, Figure 6 The network communication system 600 is shown when all components in the system 600 are functioning properly (under normal operating conditions). Figure 7 Shows that there is Figure 6 A system 700 of all components of the system 600 except for the case where one of the components is not functioning properly. Figures 1 to 7 , Figure 6 The system 600 includes a network manager 680 communicatively coupled to light fixture A 602 - 1 using communication link 505 .

[0079] Light fixture A 602-1 is communicatively coupled to light fixture C 602-3 using communication link 605. Light fixture C 602-3 is communicatively coupled to light fixture B 602-2 and light fixture D 602-4 using communication link 605. Light fixture D 602-4 is communicatively coupled to sensor A 660-1, sensor B 660-2, and sensor C 660-3 using communication link 605. Although not shown in FIG. Figure 6 , but during normal operating conditions, luminaire A 602-1, luminaire B 602-2, and luminaire C 602-3 may each be communicatively coupled to one or more other sensors.

[0080] In this example, multiple different devices save power. For example, when a particular sensor is invoked by a light fixture (in this case, light fixture D 602-4), only sensor A 660-1, sensor B 660-2, and sensor C 660-3 are active ("on"). Therefore, if the sensors are powered by batteries, the life of the batteries can be significantly longer than the life of batteries in sensors (e.g., sensor A 490-1) used in systems currently known in the art. In system 600, network manager 680 communicates with a single light fixture (in this case, light fixture A 602-1) to receive signals from sensors (e.g., sensor B 660-2).

[0081] As a result, the network manager 680 can communicate with a greater number of devices in the system 600, since many of the devices in the system 600 may be indirectly (rather than directly) communicatively coupled to the network manager 680. In other words, a luminaire (e.g., luminaire C 602-3) may use the example controller to control a sub-network of the system 600. As a result, the network manager 680 only needs to send signals to perform functions (read temperature, detect light levels) in the system 600. The various luminaires of the system 600 (each functioning with the example controller) determine which sensor should perform the function and command the sensor to perform the function as needed.

[0082] Figure 6 The example system 600 can also automatically reconfigure in the event of a loss of a lamp in another component of the system. For example, in addition to the loss of lamp D 602-4, Figure 7 System 700 with Figure 6 The system 600 is substantially the same as Figure 6Sensors associated with light fixture D 602-4 in system 600 (in this case, sensor A 660-1, sensor B 660-2, and sensor C 660-3) need to be controlled by and communicate with another light fixture. In this case, when light fixture D 602-4 cannot be used (e.g., loses power, fails), light fixture B 602-2 controls and communicates with sensor A 660-1, sensor B 660-2, and sensor C 660-3.

[0083] When light fixture 602-4 is out of service, fixture B 602-2 may be instructed to communicate with and control sensor A 660-1, sensor B 660-2, and sensor C 660-3 in one or more of a variety of ways. For example, light fixture B 602-2 may receive instructions from the network manager 680, directly or indirectly, to communicate with and control sensor A 660-1, sensor B 660-2, and sensor C 660-3. As another example, when light fixture D 602-4 becomes out of service, a signal is automatically generated to instruct the controller of fixture B 602-2 to establish communication and control with sensor A 660-1, sensor B 660-2, and sensor C 660-3. As yet another example, when one sensor (e.g., sensor A 660-1) loses communication with light fixture D 602-4, the sensor may send a signal to the light fixture closest to the sensor (in this case, light fixture B 602-2).

[0084] When light fixture D 602-4 becomes unavailable, selection of light fixture B 602-2 to assume communication and control of sensor A 660-1, sensor B 660-2, and sensor C 660-3 may be based on one or more of a number of factors. Such factors may include, but are not limited to, proximity of sensor A 660-1, sensor B 660-2, and sensor C 660-3 relative to other light fixtures in network 700, the number of sensors already under control of light fixture B 602-2 relative to other active light fixtures in network 600, the configuration of communication link 605, and default settings. In certain example embodiments, when light fixture D 602-4 is restored to service, the configuration of the components may be automatically restored to the default settings by a command from a user or based on some other factor or event. Figure 6 The system 600 shown in FIG.

[0085] Figure 8A network data frame architecture 800 is shown according to certain example embodiments. As described above, in certain example embodiments, the network manager is unaware of the presence of sensors or any other devices to which the network manager is not directly communicatively coupled. In this manner, only the application software in the server and the controller in the light fixture are aware of the presence of the various sensors communicatively coupled to the light fixture.

[0086] refer to Figures 1 to 8 The network manager can communicate with the light fixture by generating and sending a data packet (e.g., data packet 880). The data packet can have any of a plurality of parts. For example, Figure 8 The data packet 880 may include an identification portion 881, a maintenance portion 882, a priority portion 883, a reliability portion 884, and a payload portion 885. Each of these portions may be populated with data (or in some cases unpopulated). A light fixture communicatively coupled to the network manager includes a portion 886 of its controller having a list of local sensor IDs 887 and control data 888 associated with the various sensors communicatively coupled to the light fixture.

[0087] When the light fixture receives the data packet, the light fixture's controller may perform data mapping 889 to map the data in the data packet to a communication protocol understood by the sensor. The communication protocol may be the same or different than the communication protocol used between the network manager and the light fixture. The resulting data packet 890 may be sent by the light fixture's controller to the appropriate sensor.

[0088] As with data packet 880 generated by the network manager, data packet 890 may include any of a plurality of parts. For example, Figure 8The data packet 890 may include an identification portion 891, a maintenance portion 892, a priority portion 893, a reliability portion 894, and a payload portion 895. Each of these portions may be filled with data (or unfilled in some cases). The various portions of the data packet 890 may be the same as or different from the various portions of the data packet 880. The sensor may receive the data packet 890 in an expected format (e.g., HART) and send one or more data packets back to the luminaire in the same format. Subsequently, the luminaire may perform data mapping 889 using the data received from the sensor to generate a data packet, and send the resulting data packet to the network manager. Example embodiments provide luminaires that serve as access points in a communication network. Specifically, certain example embodiments allow a controller of a luminaire to communicate with and control one or more sensors located outside the luminaire within a system. In some cases, the example luminaire may be located in a specific environment (e.g., a hazardous environment). In this case, the luminaire may comply with one or more applicable standards for the environment. Communication between the example luminaire and other components of the system (e.g., users, sensors, network managers) may be performed using wired and / or wireless technologies.

[0089] By controlling the sensors, example embodiments may be used to place the sensors in sleep mode when they are not in use. Example embodiments use one or more of a plurality of time synchronization protocols for communicating data between the luminaire and the user, network manager, and sensors. Thus, example embodiments may result in lower power usage, as well as more efficient and secure communications between the luminaire and associated sensor devices, users, and / or network managers. When the luminaire is placed in a hazardous environment, a safety barrier disposed within the example luminaire may be used to improve safety practices and help ensure that the luminaire and / or sensors comply with applicable standards for use in hazardous environments.

[0090] Although the embodiments described herein are made with reference to the exemplary embodiments, it will be understood by those skilled in the art that various modifications are fully within the scope and spirit of the present disclosure. It will be understood by those skilled in the art that the exemplary embodiments described herein are not limited to any specific discussed applications, and that the embodiments described herein are illustrative rather than restrictive. From the description of the exemplary embodiments, equivalents of the elements shown therein will be shown to those skilled in the art, and the manner in which other embodiments are constructed using the present disclosure will be shown to practitioners in the art. Therefore, the scope of the exemplary embodiments is not limited herein.

Claims

1. A luminaire for communicating with a network manager and at least one sensor, the luminaire comprising: Lighting parts; as well as a controller for operating the light fixture components and communicating with the network manager, the controller being configured to receive instructions from the network manager, establishing control of at least one sensor based on instructions received from the network manager, and receiving sensor data from the at least one sensor, The controller comprises: Hardware processor; a memory including a plurality of software instructions; a control engine coupled to the memory, wherein the control engine is configured to execute the plurality of software instructions on the hardware processor to control and communicate with the at least one sensor; and a communication module coupled to the control engine, wherein the communication module is configured to communicate between the control engine and the at least one sensor, Wherein the controller is configured to act as an access point rather than a node on the communication network by using the control engine. 2 . The luminaire of claim 1 , wherein the controller is further configured to receive a request from a second sensor, associate with the second sensor based on the received request, and receive second sensor data from the second sensor.

3. A lamp according to claim 1, wherein the controller is further configured to establish communication and control with at least one additional sensor and receive sensor data from the at least one additional sensor based on instructions received from the network manager, wherein when an additional lamp communicatively coupled to the at least one additional sensor using a communication link becomes unusable, other lamps directly or indirectly receive instructions from the network manager to communicate with and control the at least one additional sensor. 4 . The light fixture of claim 1 , wherein the controller is further configured to control operation of the light fixture components in response to sensor data received from the at least one sensor.

5. A method for a luminaire to communicate with a network manager and at least one sensor, the method being performed by a controller and comprising the following steps: receiving a first instruction from the network manager; establishing control of at least one sensor based on a first instruction received from the network manager; as well as receiving sensor data from the at least one sensor, The controller comprises: Hardware processor; a memory including a plurality of software instructions; a control engine coupled to the memory, wherein the control engine is configured to execute the plurality of software instructions on the hardware processor to control and communicate with the at least one sensor; and a communication module coupled to the control engine, wherein the communication module is configured to communicate between the control engine and the at least one sensor, Wherein the controller is configured to act as an access point rather than a node on a communication network by using the control engine. 6 . The method of claim 5 , further comprising receiving a request from a second sensor, associating with the second sensor based on the received request, and receiving second sensor data from the second sensor.

7. The method according to claim 5, further comprising: When an additional light fixture communicatively coupled to at least one additional sensor using a communication link becomes unusable, the other light fixtures directly or indirectly receive instructions from the network manager to communicate with and control the at least one additional sensor; as well as Sensor data is received from the at least one additional sensor.

8. The method of claim 5, further comprising controlling operation of a light fixture component in response to sensor data received from the at least one sensor.

9. A light fixture for communicating with a network manager and a plurality of sensors, the plurality of sensors being external to the light fixture, the light fixture comprising: Lighting parts; as well as A controller for operating the light fixture components and communicating with the network manager, the controller being configured to: establishing control of the plurality of sensors in response to one or more first instructions from the network manager; receiving sensor data from the plurality of sensors; as well as generating one or more data packets based on sensor data received from the plurality of sensors, The controller comprises: Hardware processor; a memory including a plurality of software instructions; a control engine coupled to the memory, wherein the control engine is configured to execute the plurality of software instructions on the hardware processor to control and communicate with the plurality of sensors; and a communication module coupled to the control engine, wherein the communication module is configured to relay communications between the control engine and the plurality of sensors, Wherein the controller is configured to act as an access point rather than a node on a communication network by using the control engine.

10. The luminaire of claim 9, wherein the controller is further configured to: When an additional light fixture communicatively coupled to one or more additional sensors using a communication link becomes unusable, the other light fixtures directly or indirectly receive instructions from the network manager to communicate with and control the one or more additional sensors; receiving sensor data from the one or more additional sensors; as well as One or more additional data packets are generated based on sensor data received from the one or more additional sensors.

Images