Source: https://patents.google.com/patent/US9386668B2/en
Timestamp: 2019-04-24 11:06:38+00:00

Document:
2018-04-17 Assigned to LUTRON KETRA, LLC reassignment LUTRON KETRA, LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: KETRA, INC.
Intelligent illumination device are disclosed that use components in an LED light to perform one or more of a wide variety of desirable lighting functions for very low cost. The LEDs that produce light can be periodically turned off momentarily, for example, for a duration that the human eye cannot perceive, in order for the light to receive commands optically. The optically transmitted commands can be sent to the light, for example, using a remove control device. The illumination device can use the LEDs that are currently off to receive the data and then configure the light accordingly, or to measure light. Such light can be ambient light for a photosensor function, or light from other LEDs in the illumination device to adjust the color mix.
The present application is a continuation-in-part of U.S. patent application Ser. No. 13/231,077 filed Sep. 13, 2011 which is a continuation-in-part of U.S. patent application Ser. No. 12/924,628 filed Sep. 30, 2010 which claims priority to the following: (1) U.S. Provisional Patent Application No. 61/277,871 filed Sep. 30, 2009; (2) U.S. Provisional Patent Application No. 61/281,046 filed Nov. 12, 2009; (3) U.S. Provisional Patent Application No. 61/336,242 filed Jan. 19, 2010; (4) U.S. Provisional Patent Application No. 61/339,273 filed Mar. 2, 2010; which is further a continuation-in-part of U.S. patent application Ser. Nos. 12/806,114; 12/806,117; 12/806,121; 12/806,118; 12/806,126; 12/806,113, all filed Aug. 5, 2010, all of which claim priority to: (1) U.S. Provisional Patent Application No. 61/273,518 filed Aug. 5, 2009; (2) U.S. Provisional Patent Application No. 61/273,536 filed Aug. 5, 2009; (3) U.S. Provisional Patent Application No. 61/277,871 filed Sep. 30, 2009; (4) U.S. Provisional Patent Application No. 61/281,046 filed Nov. 12, 2009; (5) U.S. Provisional Patent Application No. 61/336,242 filed Jan. 19, 2010; (6) U.S. Provisional Patent Application No. 61/339,273 filed Mar. 2, 2010; all of which are further continuations-in-part of U.S. patent application Ser. No. 12/803,805 filed Jul. 7, 2010 which claims priority to: (1) U.S. Provisional Patent Application No. 61/224,904 filed Jul. 12, 2009; (2) U.S. Provisional Patent Application No. 61/273,518 filed Aug. 5, 2009; (3) U.S. Provisional Patent Application No. 61/273,536 filed Aug. 5, 2009; (4) U.S. Provisional Patent Application No. 61/277,871 filed Sep. 30, 2009; (5) U.S. Provisional Patent Application No. 61/281,046 filed Nov. 12, 2009; (6) U.S. Provisional Patent Application No. 61/336,242 filed Jan. 19, 2010; (7) U.S. Provisional Patent Application No. 61/339,273 filed Mar. 2, 2010; which further is a continuation-in-part of U.S. patent application Ser. No. 12/360,467 filed Jan. 27, 2009; and which further is a continuation-in-part of U.S. patent application Ser. No. 12/584,143 filed Sep. 1, 2009 which claims priority to U.S. Provisional Patent Application No. 61/094,595 filed Sep. 5, 2008.
This invention relates to illumination devices and, more particularly, to controlling illumination devices.
A wide variety of lighting control systems are currently commercially available for controlling a variety of lighting features from simple on/off switching to complex color adjustment and performance monitoring. Such systems also communicate according to a wide variety of protocols over various communication channels. As an example, a simple system could be just a triac dimmer and a single lamp. As another example, a complex system could be a hierarchical campus wide network. In such a complex system, up to 64 intelligent fluorescent lamp ballasts within a room or group of rooms could be wired together using the Digital Addressable Lighting Interface (DALI) standard, for instance, with an Ethernet enabled DALI controller, which then communicates with other DALI controllers and a computer server over Ethernet within each building. At the top layer of the hierarchy, the computer servers in different buildings within a campus could communicate over the Internet using Internet Protocol (IP).
Some lighting control systems use protocols that are somewhat specific to lighting, such as 0-10V, DMX512, DALI, and Dynalite, while others use protocols that target building automation in general, such as X10, LonWorks, C-Bus, and ZigBee. Still other lighting control systems use industry standard networking protocols such as Ethernet, Wi-Fi, and HomePlug. At the campus wide level with communication over the Internet, such complex lighting control systems can also use telecom networking protocols such as SONET and ATM. All theses standards and protocols communicate at different rates, using different modulation and packetizing schemes, over various communication channels. Such channels include powerline for X10 and HomePlug, RF for ZigBee and Wi-Fi, optical fiber for SONET, and dedicated wires for most of the others including 2 wire DC for 0-10V, twisted pair for DALI and others, and CAT5 for Ethernet.
The 0-10V standard was one of the earliest and simplest lighting control signaling system, which is still supported by many fluorescent ballasts produced by companies such as GE, Philips, and Sylvania. Such ballasts produce light from an attached fluorescent lamp that is proportional to the DC voltage input to the ballast through two wires. Although simple to understand and implement, each ballast must have a dedicated cable to the system controller, which can become very expensive and cumbersome in large installations. Additionally, such a lighting control system can only control light level and cannot extract information from the ballast, such as if a bulb has burned out.
The DMX512 stands for “Digital Multiplex with 512 pieces of information” and is a standard for digital communication commonly used in theaters and production studios. DMX512 communicates over shielded twisted pair cable using EIA-485 standard voltages levels with node connected together in a daisy chain manner. Data is sent one byte per packet at 250 kbaud in a manner similar to RS232. The DMX512 protocol is popular for stage lighting due to the robustness of its cable and the relatively long communication distances.
The DALI standard, which is becoming relatively popular for commercial lighting systems, is similar to DMX512 in that various lamps can be individually controlled using a relatively low data rate digital control bus, however, there are many differences ranging from the type of communication cable and interconnections to data format and messaging requirements. While DMX512 communicates uni-directionally over shielded twisted pair cable between two nodes, DALI communicates bi-directionally over un-shielded twisted pair that can be tapped by up to 64 devices. While all DMX512 data frame comprise one start bit, 8 data bits, and two stop bits, DALI has different sized frames for communication in the different directions with both acknowledge and data bytes in one direction and no acknowledge in the other direction.
Unlike DALI, DMX512, 0-10v, and other protocols developed specifically for lighting, X10 was developed for general home automation of which lighting is an important subset. A further substantial difference is that X10 typically communicates data over the power lines that are already connected to most devices. X10 devices typically communicate one bit of information around each zero crossing of a 50 or 60 Hz AC mains cycle, by coupling bursts of a high frequency signal onto the powerline. As such, the data rate is very low. To compensate, the protocol is very simple in which all packets consist of an 8 bit address and a 4 bit command. Since only 16 commands are possible, functionality is limited.
HomePlug is another protocol that uses the power line for communication, however, unlike X10, which was architected for home automation, HomePlug was designed to allow products communicate with each other and the Internet through existing home electrical wiring. A variety of versions of HomePlug have been released with data rates ranging from 10 to 200 Mbit/s. HomePlug achieves such data rates using adaptive modulation and complex error correction algorithms on over a thousand Orthogonal Frequency Division Multiplexed (OFDM) sub-carriers.
Data in a HomePlug network is typically communicated in Ethernet compatible packets, which comprise of a header with about 22 bytes, the payload with up to 1500 bytes, and a CRC code with 4 bytes, however, HomePlug also provides a variety of higher level services that provide, among other things, guaranteed delivery, fixed latency, quasi-error free service, and jitter control. As such, a HomePlug interface is much more complicated than is needed for simply lighting control.
Although communication over a power line is a good solution for some building networking applications, there are some drawbacks. For instance, there can be excessive attenuation between different phases of typically three phase systems, which can be overcome by active repeaters or sometimes with special capacitors. Additionally, signals can propagate through the power line between different buildings causing interference and security concerns. When appliances turn on and off significant noise is generated that can corrupt transmission. HomePlug physical layer interfaces have overcome some of such issues at the expense of complex analog and digital signal processing.
LonWorks is a building automation protocol that typically uses either twisted pair cable at 78 kbit/sec or the power line at a few kilobits per second for the communication channel. For communication over the power line, LonWorks uses dual carrier frequency operation in which messages are sent using one carrier frequency and, if a response is not received, the message is sent a second time using a second carrier frequency. More recent releases of the protocol allow IP data frames to be communicated across a LonWorks network, and a library of commands for a wide variety of appliances and functions have been and continue to be developed for a range of residential and commercial applications.
The C-Bus Protocol targets home automation systems as well as commercial lighting systems. Unlike the X10 protocol, C-Bus typically uses dedicated CAT5 cables and is considered by some to be more robust as a result. Ethernet also typically uses CAT5 cable for communicating between devices in a star topology with a router or switch at the center. Common data rates include 10, 100, and 1000 Mbit/sec, which are all deployed widely worldwide for computer networking. As mentioned previously, Ethernet data frames comprise a header of typically 22 bytes, a payload of up to 1500 bytes, and a CRC of four bytes. In many applications, the payload of an Ethernet frame is an Internet Protocol (IP) packet. Although overkill for simple lighting systems, Ethernet comprises the backbone of a variety of building lighting control networks, such as those from LumEnergi and others.
ZigBee comprises a group of high level communication protocols that typically use the IEEE 802.15.4-2003 standard for Wireless Personal Area Networks (WPANs) as the physical layer. As such, ZigBee typically uses small low power radios to communicate between appliances, light switches, consumer electronic, and other devices in a residence for instance. IEEE 802.15.4 uses either the 868 MHz, 915 MHz, or 2.4 GHz radio frequency bands. Data is direct-sequence spread spectrum coded and then Binary Phase Shift Key (BPSK) or Orthogonal Quadrature Phase Shift Key (OQPSK) modulated prior to transmission. Data is communicated in one of four different types of frames with variable data payload. Such frames include beacon frames, which specify a super-frame structure similar to that of HomePlug, data frames used for transfers of data, acknowledge frames used for confirming reception, and MAC command frame used for controlling the network. The SuperFrame structure allows certain devices guaranteed bandwidth and provides shared bandwidth for other devices. Many aspects of the network enable very low power communication with battery powered devices.
Wi-Fi or 802.11 is a very common wireless network for data communication between computers. A number of versions of the protocol including 802.11a, 802.11b, and 802.11g have been released over the years. The recent version, 802.11g, operates at the 2.4 GHz band and uses Orthogonal Frequency Division Multiplexing (OFDM) and typically achieves about 22 Mbit/sec average throughput. Similar to Ethernet, Wi-Fi frames comprise of a header, payload, and CRC. Similar to 802.15.4, Wi-Fi has a variety of different types of frames for communication management. In general, Internet Protocol (IP) and the associated Transport Control Protocol (TCP) run over Wi-Fi networks.
Although wireless protocols such as ZigBee and Wi-Fi do not need dedicated wires to communicate between devices, nor do they have the limitation previously mentioned associated with power line communication, such wireless networks can be limited by congestion in the increasingly crowded RF spectrum. Additionally, different countries in the world allocate spectrum differently which forces devices to sometimes operate in different frequency bands.
An alternative physical layer communication channel and associated network protocol for lighting control among other applications have been introduced that use modulated visible light traveling through free space to communicate data. According to such visible light communication (VLC) protocol, all devices synchronize to a frequency or phase of the AC mains for instance and produce gaps during which messages can be sent. At other times, lamps using LEDs or any other type of light source, simply produce illumination. During the gap times some number of bytes of data can be sent from one lamp to one or more other lamps that can comprise a complete message in itself, or such data can accumulate over any number of gaps to produce much larger messages.
Using visible light to communicate between lamps and other devices in a lighting system has many advantages over wired, wireless, and powerline communication networks such as those previously described. No dedicated wires are needed, which is important especially for installation in existing buildings. The visible light spectrum is unregulated globally and does not suffer from the congestion and interference common in RF wireless communication. Electrical noise on the powerline, from appliances turning on and off for instance, does not affect communication integrity as in powerline communication protocols. No expensive and complicated analog and digital signal processing is necessary to modulate and demodulate data as in many wireless and powerline protocols. The light source needed to transmit data is necessary anyway to provide illumination, and in the case that the light source is one or more LEDs, the LEDs can operate as the light detector as well. As such, the visible light communication protocol can be implemented in an LED lamp for virtually no additional cost.
A limitation of such a visible light communication protocol is that data cannot be communicated through walls between various rooms in a building. Another limitation is that, other than the remote controller, it is difficult to cost effectively control such a visible light communication network. The invention described herein, in various embodiments, provides solutions to overcome these limitations.
According to one embodiment, an electronic device is provided herein for controlling a lighting system. In certain exemplary embodiments, the electronic device is mounted to a wall in a room or held in a hand, for instance, and comprises a Human Machine Interface (HMI), such as a touch screen or a set of buttons (e.g., dedicated to specific lighting functions or programmable to perform a variety of functions) that are illuminated by a light source. In addition to illuminating the HMI, the light source also transmits messages through free space using visible light to one or more lamps in the room. For example, a HMI could comprise an LCD panel, which is illuminated by an LED backlight for displaying information about the controls or lighting system, and either an overlaid touch screen sensor or additional pushbuttons for entering information. Alternatively, the HMI could comprise just pushbuttons that are illuminated by some light source for use in the dark.
For a handheld electronic device (otherwise referred to herein as a wireless communication device), such as a smart phone or tablet computer, the display backlight could be modulated in a variety of ways including playing a video with alternating light and dark frames to produce light modulated with data. The ambient light sensor available on many handheld electronic devices could be used to receive data transmitted through free space using visible light. An alternative light source in many handheld electronic devices such as smart phones is the camera flash, which typically comprises one or more LEDs that can be modulated through software to transmit data through free space using visible light.
As another example, the light source in an electronic device that is mounted to a wall, for instance, can be synchronized to a frequency or phase of the AC mains, produce communication gaps that are synchronous to the communication gaps used by lamps in the room, and transmit data to the lamps in response to input from a user. Additionally, such an electronic device can have a light detector for receiving information from the lamps that is transmitted through free space using visible light. If the light source is one or more LEDs, then the LEDs can be both the light source and the light detector. In a further embodiment, the light produced by a light source in the electronic device is perceived as unchanging by a user independent of whether data is being transmitted or not. This is accomplished, for instance, by producing a small amount of light continuously when data is not being transmitted and by turning this small amount of light off before or after data is transmitted at high brightness for instance. In this exemplary embodiment, control circuitry within the electronic device is configured to produce commands in response to input directly from a user.
In certain exemplary embodiments, an electronic device comprising an HMI with a light source and a light detector also comprises circuitry to interface to any type of data communication network typically used for lighting or building control information. Such data communication network could communicate over dedicated wires (e.g., Ethernet, DALI, DMX512, and others), the power line (e.g., X10, HomePlug, and others), RF wireless (e.g., ZigBee, Wi-Fi, and others), or any other communication channel including for instance fiber optic cable and wireless infra-red. Such data communication network could interface for instance to a central building controller over Ethernet or DALI, or could interface for instance to a wireless communication device (such as a smartphone) over Wi-Fi, Bluetooth, IRDA, or any other data communication protocol supported by such wireless communication device. In some instances, the electronic device could comprise interfaces to multiple data communication networks, such as Ethernet and Wi-Fi, to support lighting control systems with mixed environments.
In an electronic device comprising an HMI that can communicate through free space using visible light, and interfaces to one or more data communication networks, control circuitry would receive input directly from the user through the HMI, data received from such data communication networks, or data received optically through free space. Such control circuitry in response to such input or data would produce commands encoded and transmitted according to a visible light communication protocol.
In certain exemplary embodiments, a lamp comprises a light source for illuminating an area and transmitting data through free space using visible light, a light detector for receiving data transmitted through free space using visible light, and an interface to one or more other types of data communication networks that carry lighting control information. If one or more LEDs can operate as the light source, then such LEDs could also be operable as both the light source and the light detector. The data communication network could communicate with the lamp over any type of communication channel and communication protocol. The lamp could be a lamp in a ceiling, for instance. In such a lamp, control circuitry receives input from one or more such data communication network or networks and produces commands encoded and transmitted according to a visible light communication protocol such as that described in the one or more priority applications listed herein.
FIG. 1 is an exemplary block diagram of a lighting control system comprising a plurality of lamps, an electronic device and optional wireless communication device.
FIG. 2 is an exemplary block diagram of a lamp that communicates with an electronic device and/or other lamps through free space using visible light.
FIG. 3 is an exemplary block diagram of a lamp that communicates with other lamps through free space using visible light and with a network and other controlling devices through a Wi-Fi interface.
FIG. 4 is an exemplary diagram for the structure of a Wi-Fi data communication packet.
FIG. 5 is an exemplary diagram for a packet communicated through free space using visible light.
FIG. 6 is an exemplary drawing of an electronic device with an HMI, wherein the electronic device controls a lighting system by communicating with lamps through free space with visible light and communicating with a network and other controlling devices through Wi-Fi and Ethernet interfaces.
FIG. 7 is an exemplary block diagram of an electronic device with an HMI, wherein the electronic device controls a lighting system by communicating with lamps through free space with visible light and communicating with a network and other controlling devices through Wi-Fi and Ethernet interfaces.
FIG. 8 is an exemplary timing diagram for communicating between an HMI and lamps through free space using visible light.
The use of the same reference symbols in different drawings indicates similar or identical items. While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that the drawings and detailed description thereto are not intended to limit the invention to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the present invention as defined by the appended claims.
Turning now to the drawings, FIG. 1 is one example of a building lighting system 10 that comprises building controller 11 configured for controlling the lighting system and a network 12 that connects room1 13, room2 14, and roomN 15 to building controller 11. The lighting system 10 shown in FIG. 1 further includes an electronic device 16, or possibly a lamp 22, which communicates with the network 12. The designation room1 through roomN represents any number of rooms in a building or even multiple buildings to one of more central controllers represented by building controller 11. Within any particular room, a plurality of lamps (e.g., lamps 17, 18, and 19 within room1, or lamps 22, 23 and 24 within room2) may communicate with each other and with an electronic device 16 through modulated visible light shown in FIG. 1 with bi-directional arrows.
In example room1 13, electronic device 16 interfaces between network 12, lamps 17, 18, and 19, and optionally wireless communication device 20. Wireless communication device 20 may or may not be part of building lighting system 10, but if included, can be any type of mobile device including but not limited to mobile phones, smart phones, personal digital assistants (PDA), and mobile computers such as netbooks, notebooks, and laptops. Wireless communication device 20 could also be a stationary device, such as a desktop computer. In some embodiments, wireless communication device 20 may communicate with electronic device 16 using any radio or infra-red frequency wireless communication protocol including, but not limited to, Zigbee, Wi-Fi, and Bluetooth. In some embodiments, wireless communication device 20 may be configured for controlling the lighting system, similar to electronic device 16, and may be considered to be a hand held electronic device.
Network 12 typically might communicate according to the wired DALI or Ethernet standards, or the wireless ZigBee or Wi-Fi standards, but could communicate according to any data communication protocol using wired, wireless, powerline, fiber optic, or any other type of communication channels. Network 12 and optional wireless communication device 20 can communicate according to the same or different wireless protocols, or can communicate over different protocols using different wired or wireless communication channels.
Electronic device 16 represents any electronic device that provides an interface between lamps 17, 18 and 19 and network 12, and that also provides a human machine interface (HMI) 21. HMI 21 is configured to receive input from a user, which is typically used, but not limited to, local control of lamps 17, 18, and 19 in room1 13, for instance. In one embodiment, electronic device 16 could be a device mounted on a wall within room1 13 that enables a user to control the lighting within room1 13 independent of and/or overriding commands from building controller 11. Electronic device 16 could be a device about the size of a conventional light switch or a ganged light switch. In one example, electronic device 16 could be implemented with an HMI 21, such as a display and touch screen that enables a user to select lighting functions from a menu or nested menus for instance. Electronic device 16 also, for instance, could be implemented with an HMI 21, such as a set of buttons that are dedicated to particular functions, such as on/off, dimming, color, timing, and other functions such as those described in the one or more priority application listed herein.
In the example lighting system of FIG. 1, electronic device 16 communicates with lamps 17, 18, and 19 through modulated visible light. According to one embodiment, electronic device 16 could comprise a dedicated light source, which is configured to provide illumination and to transmit data optically through free space using visible light, and optionally an additional light detector, which is configured to receive data transmitted optically through free space using visible light. According to another embodiment, the dedicated light source may be used to both illuminate the HMI 21 and to communicate modulated visible light uni-directionally or bi-directionally with lamps 17, 18, and 19 in the example room1 13 of FIG. 1.
In order for the HMI 21 to be visible in the dark, for instance, the electronic device typically comprises a backlight (or a light source positioned behind the HMI) that illuminates the HMI (e.g., various push buttons or an LCD display with an overlaid touch screen sensor) from behind. Many possible HMIs are possible with the commonality that a light source is typically necessary for a user to see in at least a dark environment. Such a light source typically will be an LED or array of LEDs, but could comprise any type of light source including, for instance, Cold Cathode Fluorescent lamps (CCFL). If the light source is a CCFL or, for instance, a white LED with a phosphor coating, preferentially the electronic device also comprises an additional photo-detector.
According to one embodiment of the invention, the light emitted from the backlight of the HMI is modulated in such a way that one or more of lamps 17, 18, and 19 can detect the data represented by such modulation. In some embodiments, electronic device 16 can also receive data sent by lamps 17, 18, or 19, e.g., through the additional photo-detector, or through the backlight. For example, if the backlight comprises one or more LEDs for illumination and data transmission, and preferentially mono-chromatic LEDs such as red, green, and blue, the LEDs used for illumination and data transmission may also be used to receive data sent by lamps 17, 18, or 19.
According to another embodiment of the invention, wireless communication device 20, which could be any type of computing device with a backlit display such as a smart phone, PDA, or a tablet, netbook, notebook, or desktop computer, may communicate directly with electronic device 16 or with lamps 17, 18, and 19 through free space using visible light. For example, wireless communication device 20 may produce commands in response to input received directly from a user, and may transmit such commands to the electronic device 16 or directly to the lamps 17, 18 and 19 using visible light. As with electronic device 16, the backlight for the display of the wireless communication device 20 can be modulated to transmit data or commands optically to the electronic device 16 or directly to lamps 17, 18, and 19. This can be accomplished in various ways including, but not limited to, playing a video with alternating light and dark frames producing the transmitted data. The ambient light sensor available on many wireless communication devices can also be used as a light sensor to receive data. Alternatively, the camera flash, which typically comprises one or more LEDs on a smart phone, for instance, can also be modulated through software to transmit data to electronic device 16 or to lamps 17, 18, and 19 in the example of FIG. 1.
According to another embodiment, a lamp may be used to interface with the network 12 instead of an electronic device. As represented by room2 14, for instance, lamp 22 provides an interface between the lamps 22, 23, and 24 within room2 14 and network 12. As such, lamp 22 comprises a network interface, which is capable of communicating with network 12 according to any protocol using any communication channel including, but not limited to, RF wireless, wired, fiber optic, or power line. In this example room2 14, lamp 22 further comprises a light source for illumination and data transmission, and a light detector for receiving data from lamps 23 and 24. In one embodiment of the invention, if the light source is one or more LEDs, then such LEDs can also operate as the light detector depending on when data is to be sent or received.
As in example room1 13 and wireless communication device 20, wireless communication device 25 in room2 14, for instance, can locally control lamps 22, 23, and 24 by overriding commands from building controller 11 or can implement any functionality supported by lighting system 10. In this example room2 14, wireless communication device 25 communicates with lamp 22, which also provides the interface to network 12. As such, according to one embodiment of the invention, lamp 22 further comprises a wireless interface compatible with wireless (RF, infra-red, etc) communication device 25 and an interface compatible with network 12.
Within the example room1 13 and room2 14, lamps 17, 18, and 19, and lamps 22, 23, and 24 respectively communicate between each other using modulated visible light. When observed by the human eye, although the light is visible, the modulation of the light is typically not discernable and is typically perceived as constant and unchanging light. The maximum distance between any two lamps, for instance lamps 17 and 18, is determined by the brightness and directionality of the data transmitting lamp and the light detection sensitivity of the data receiving lamp. In the example room1 13, lamps 17 and 18 are positioned within such maximum communication distance, and lamps 17 and 19 for instance are positioned beyond such maximum communication distance. According to another embodiment of the invention, lamp 18 in the example room1 13 relays messages sent through modulated visible light between lamps 17 and 19 to enable communication between large numbers of lamps that are large distances apart.
According to the invention, lamps that relay commands first receive data on a light detector and forward such input to control circuitry that regenerates commands in response to such input. For instance, commands can be directed from lamp 17 to lamp 19 only, while lamp 18 simply receives and retransmits such commands along a dedicated path as in the Internet. Alternatively, messages from an example lamp 17 can be broadcast to all lamps in which lamp 18 for instance responds to such broadcast command and also retransmits such command to lamp 19 for instance. As such, commands can be sent through a network of lamps as broadcast messages or through dedicated or ad-hoc paths between particular lamps or groups of lamps. Ad-hoc paths are well known to those practicing in the field of mesh networking, which is commonly used in Zigbee wireless networks for instance.
FIG. 1 is just one example of many possible lighting control systems 10, which could comprise any number of buildings, rooms within each building, and lamps within each room, hallway, entryway, etc. Additionally, lighting control system 10 may comprise of any number of building controllers and any type or multi-types of networks between rooms. The networks 12 between rooms can communicate according to any type of protocol including standards such as Ethernet, DALI, Wi-Fi, and others that use wired, RF, power line, fiber optic, or any other type of data communication channel.
d. lamp 17 that produces commands in response to input received from another lamp 18 or 19 or an electronic device 16 and detected by the light sensor, and transmits such commands using the same light source that is used for illumination.
Preferentially, lamps 17, 18, 19, 22, 23, and 24 and optionally electronic device 16 communicate between each other in synchronization with the AC mains 31, as described in one or more priority applications listed herein; however, such devices could communicate according to any communication protocol that uses visible light traveling through free space. Such communication can be between devices that are in or out of synchronization and according to any modulation technique, data rate, or distance. Likewise, any routing or mesh networking protocol can be implemented using such devices that receive and retransmit commands optically through free space. As noted herein, the term “free space” refers to communication within space, but not confined to, for example, an optical fiber. Thus, transfer of commands occurs optically, but not constrained within an optical fiber or any other type of waveguide device, yet is free and able to travel optically in any non-obstructed direction. The example of a building lighting system 10 does not limit the embodiment to a single building, but can be among several buildings or within a portion of the building. Moreover, each room shown in the lighting system 10 is configured according to one example if, for example, there are several rooms controlled by a lighting system. If the system controls only a single room, then the example in FIG. 1 would apply to different sub-regions within that room, each having a different interface to a network. Likewise, each room or sub-regions of a room can be controlled according to that shown in room1 13, room2 14, or both.
Thus, the lighting system can be controlled with an electronic device 16 that comprises a HMI 21 and provides an interface between lamps 17, 18, 19 and network 12. Alternatively, the lighting system can be controlled with a wireless communication device, e.g., device 25, and interface to the network 12 can be achieved solely with a light source (e.g., lamp 22), which can also function as a light detector. In this case, the HMI can be achieved by a wireless communication device (e.g., device 25) that need not be configured between the lamps 22, 23, and 24 and the network 12.
Accordingly, an electronic device is provided herein having both a light source and a light detector, as well as control circuitry, which is configured to produce commands for controlling the lighting system in response to received input and/or data. The electronic device can further comprise an HMI configured to receive input from a user, and/or a network interface configured to receive data from a network, depending on the configuration shown in the examples of FIG. 1. Various embodiments of lamps are also provided herein having a light source, a light detector and control circuitry that produces commands transmitted by the light source in response to commands received through the light detector. In some embodiments, a lamp may be configured to produce commands in response to input received from a network 12 or a wireless communication device 25 and to transmit such commands to other lamps using the same light source that is used for illumination.
FIG. 2 is one example of a block diagram of a lamp 30 comprising a light source that is configured to provide illumination and transmit data optically through free space, a light detector that is configured to receive data transmitted optically through free space, and a control circuit that produces commands transmitted by the light source in response to commands received through the light detector. According to one embodiment, LEDs 36 may be configured at different times as both the light source and the light detector. Example lamps 17, 18, 19, 23 or 24 could comprise the circuitry represented by this example FIG. 2. As such, in addition to providing general illumination, a lamp comprising such control circuitry can receive messages sent via modulated visible light (e.g., from electronic device 16, wireless communication device 20 or 25, or another lamp) and can retransmit such information according to any pre-determined fixed routing or any ad-hoc mesh networking protocols for instance.
As shown in FIG. 2, lamp 30 connects to the AC mains 31 that provides power and synchronization in this example. Power supply 32 converts AC power to DC power that provides current to LEDs 36 and voltage to the remaining circuitry in lamp 30. Timing 33 typically comprises a phase locked loop (PLL) that locks to the AC mains 31 frequency and/or phase, and provides timing information to visible light communication (VLC) network controller 34 and physical layer interface (PLI) 35. Since the example electronic device 16 and lamps 17, 18, 19, 22, 23, and 24 (FIG. 1) are all coupled and thus synchronized to the same AC mains 31, the timing of the VLC network controllers 34 and PLIs 35 in all such example devices is substantially the same, which simplifies data communication as described in one or more priority applications listed herein.
PLI 35 typically comprises an LED driver circuit (not shown) that produces a substantially DC current to produce illumination from LEDs 36 and modulated current to transmit data from LEDs 36. Such substantially AC and DC currents can be combined in many different ways to produce both illumination and transmit data using the same light source. Periodic time slots can be produced in synchronization with the AC mains 31 during which the example DC current is turned off and the example AC current is turned on during gaps in which data is transmitted.
PLI 35 also typically comprises a receiver circuit (not shown) that in this example FIG. 2 detects photo-current induced in LEDs 36 while receiving data transmitted using visible light through free space. Such receiver typically converts such photo-current to voltage, which is then compared to a reference voltage to determine a sequence of ones and zeros sent by the transmitting device. The details of one example PLI 35 are described in one or more priority applications listed herein.
VLC network controller 34 interfaces with PLI 35 and memory 37 to receive commands transmitted using visible light through free space, to implement the necessary control circuit functionality of lamp 30, and in some cases, re-transmit commands using LEDs 36 that were previously received by LEDs 36 during gap times. Commands received by the light detector, in this case LEDs 36, can be stored in memory 37 and further processed. Commands that target lamp 30 can be interpreted by VLC network controller 34 and processed locally. For instance, the brightness or color of LEDs 36 can be adjusted by adjusting the substantially DC current applied to LEDs 36 by the driver function within PLI 35. Commands that target other or additional lamps can be stored in memory 37 and re-transmitted by PLI 35 and LEDs 36 during subsequent gap times for instance. Such commands can be routed through a pre-determined path, through an ad-hoc mesh network, or broadcast to all electronic devices for instance. VLC network controller 34 may be configured to communicate such commands according to a visible light communication protocol.
In this example FIG. 2, timing 33 can not only synchronize all electronic devices and lamps 30 in the network, but can also provide timing to power supply 32 to minimize noise coupling into PLI 35. As such, FIG. 2 is just one example of many possible lamps 30 that receive commands communicated through free space using a light detector and re-transmit such commands to other electronic devices or lamps using visible light. The preferential visible light communication protocol is described in one or more priority applications listed herein, however, any visible light communication protocol and multiplexing scheme between illumination and data communication are possible. Additionally, lamp 30 could have a variety of block diagrams different from this example FIG. 2. For instance, lamp 30 could be DC or solar powered for instance. Likewise, any type of light source is possible including, but not limited to, fluorescent tubes, compact fluorescent lights, incandescent light, etc. In particular, lamp 30 could comprise a light detector, such as a silicon photo-diode in addition to the light source, which in this example FIG. 2 is LEDs 36.
FIG. 3 is one example block diagram of a lamp 40 (e.g., lamp 22 in FIG. 1) that can transmit and receive data communicated using visible light through free space, and can also communicate according to the wireless 802.11 protocol with building controller 11 and wireless communication devices 20 and 25. As in lamp 30, lamp 40 comprises LEDs 36, PLI 35, VLC Network Controller 34, memory 37, and timing 33. Power supply 41 may be slightly different from power supply 32 due to the additional load provided by the additional processor 42 and Wi-Fi interface 43.
In this example lamp 40, LEDs 36 operate as both the light source and the light detector for transmitting and receiving data using visible light communicated through free space. LEDs 36 also provide illumination. Wireless 802.11 interface 43 can receive messages from wireless communication devices (e.g., a smart phone) 20 and 25, or from building controller 11, and can forward such messages to processor 42, which can implement the control circuitry functionality necessary to interpret or translate such messages to commands that can be transmitted through free space using visible light (e.g., using LEDs 36 as the light source). Likewise, commands transmitted optically through free space can be received by LEDs 36 operating as light detectors, interpreted or translated by processor 42, and transmitted by Wi-Fi interface 43 back to wireless communication devices 20 and 25 or building controller 11.
Whether or not a lamp includes a processor and separate Wi-Fi interface, as shown in FIG. 3, it is appreciated that the lamp operates as a light source and a light detector via one or more LEDs to which it controls. When a separate processor and Wi-Fi interface are not included, as in the embodiment of FIG. 2, the VLC network 34 of the lamp 30 provides the control circuitry through the PLI 35 to the light source and light detector dual purpose function of the LEDs 36. The controllable LEDs can control other LEDs within optical range, both within a bank of LEDs 36 or external to the bank of LEDs as shown by the bi-directional arrows of FIGS. 2 and 3.
FIG. 4 illustrates the typical data frame format 50 for Wi-Fi, which comprises up to thirty bytes for header 60, zero to two thousand three hundred twelve (2312) bytes for data 58, and four bytes for frame check sequence (FCS) 59. Header 60 typically comprises two bytes for frame control 51, two bytes for the duration ID 52, six bytes for source address 53, six bytes for destination address 54, six bytes for receiver address 55, two bytes for sequence control 56, and six bytes for transmitter address 57. Typically in a Wi-Fi network, data 58 comprises packets that conform to the Internet Protocol (IP), which comprise up to an additional 20 bytes of header.
FIG. 5 illustrates a possible data frame format, which is generally compatible with the ZigBee wireless RF protocol, for communicating with visible light. The data frame format shown in FIG. 5 comprises a Physical Protocol Data Unit (PPDU) 70, which further comprises four bytes for preamble sequence 66, one byte for start of frame delimiter 67, one byte for frame length 68, and up to 128 bytes for Mac Protocol Data Unit (MPDU) 69. MPDU 69 comprises two bytes for frame control 61, one byte for data sequence number 62, four to twenty bytes for address information 63, N bytes for data 64, and four bytes for Frame Check Sequence (FCS) 65.
In the example lamp 40 illustrated in FIG. 3, Wi-Fi interface 43 can forward received data frames conforming to the example Wi-Fi protocol illustrated in FIG. 4 to processor 42. Processor 42 interprets such data frames and creates data frames conforming to the example visible light communication protocol illustrated in FIG. 5. Processor 42 inputs such data frames to VLC network controller 34 for transmission through PLI 35 and LEDs 36. Likewise, data frames input to VLC network controller 34 through LEDs 36 and PLI 35 can be processed and transmitted through PLI 35 and LEDs 36 or forwarded to processor 42, which can interpret such data frames, create data frames conforming to the example Wi-Fi protocol and forward such data frames to Wi-Fi interface 43 for transmission over such Wi-Fi network.
FIG. 3 is just one of many possible block diagrams for lamp 40. For instance, instead of the LEDs 36 shown in FIG. 3, the light source could be a fluorescent bulb or any other type of light source. Lamp 40 could also comprise a photo-detector, such as a silicon photodiode, instead of using LEDs 36 as both the light source and light detector. Lamp 40 does not need to be synchronized to the AC mains and comprise timing block 33. Many other means of synchronization are possible and communication even without synchronization is possible. Lamp 40 could be battery or solar powered, for instance, and as such would have a different or no power supply 41. VLC network controller 34 and PLI 35 in this example implement the data frame format illustrated in FIG. 5, but could implement any type of communication protocol using visible light. For instance, the protocol described uses substantially the same frame format as ZigBee, however, any frame format including substantially simpler versions with smaller headers are possible.
Wi-Fi interface 43 is just one example of many different network interfaces using many different types of communication channels that are possible. It is also possible to have multiple interfaces to different networks. Some other network examples include X10, DMX512, DALI, Ethernet, ZigBee, HomePlug, LonWorks, C-Bus, Dynalite, Bluetooth, and even SONET and ATM. A typical configuration for lamp 22 in FIG. 1 could include a Wi-Fi interface 43 for communicating with a smart phone for instance for local control, and an Ethernet interface (not shown) for communicating with a building controller 11.
FIG. 6 illustrates one embodiment of the electronic device 16 from FIG. 1 that interfaces to network 12, wireless communication device 20, and lamps 17, 18 and 19. In this example FIG. 6, a user can also control lamps 17, 18, and 19 within room1 13, and potentially the entire lighting system 10, by pushing regions of touch screen 80 that overlay menu 84 that is an image produced by LCD 81 and illuminated by backlight 82. The example menu 84 provides various buttons to turn lights on and off (ON/OFF), adjust brightness (DIM), change color (COLOR), set the timer (TIMER), adjust the ambient light sensor (AMB), and access advanced programming functions (PROG). In this example FIG. 6, electronic device 16 is powered by the AC mains 31 and is contained within housing 83. The HMI in FIG. 6 is provided by the touch screen 80 and LCD 81.
Electronic device 16 communicates with building controller 11 through network 12 according to any one of many different data communication protocols over any of a variety communication channels including but not limited to CAT5 or twisted pair cable, RF wireless, powerline or fiber optics. Although it need not communicate with device 20, electronic device 16 can also optionally communicate with wireless communication device 20 (which could be a smart phone) using any one of many different RF, infrared, or other wireless communication protocols, including but not limited to Wi-Fi, ZigBee, Bluetooth, IRDA, or others. According to one embodiment of the invention, electronic device 16 communicates with lamps 17, 18, or 19 through free space using modulated visible light that also provides illumination for electronic device 16.
FIG. 7 is an example functional block diagram of the electronic device 16 that comprises a touch screen 80, LCD 81, backlight 82, and housing 83, as shown in FIG. 6. Housing 83 can comprise the same timing 33, memory 37, VLC network controller 34, PLI 35 and Wi-Fi interface 43 as illustrated in FIG. 3, and can also comprise Ethernet interface 91, touch screen controller 93, graphic controller 94, and processor 92. LEDs 36 in the examples of FIG. 6 and FIG. 7 reside in backlight 82 and produce illumination for LCD 81, and transmit data through free space using visible light. Additionally, LEDs 36 (which in the example of FIG. 7 could be red LEDs) can also operate as light detectors for receiving data transmitted through free space using visible light.
In this example FIG. 7, electronic device 16 interfaces with building controller 11 according to the Ethernet protocol, which typically uses CAT5 cable as the communication channel. Messages received by Ethernet interface 91 can be forwarded to processor 92, which can implement the control circuitry necessary to interpret or translate such messages to commands that can be transmitted through free space using visible light with LEDs 36 as the light source. As in FIG. 3, messages received through Wi-Fi interface 43 can also be forwarded to processor 92 for interpretation and translation to commands that can be transmitted through free space using visible light with LEDs 36 as the light source.
In this example FIG. 7, commands transmitted optically through free space can also be received by LEDs 36 operating as light detectors, interpreted or translated by processor 92, and transmitted by Wi-Fi interface 43 back to wireless communication devices 20 or 25, or transmitted by Ethernet interface 91 to building controller 11. Likewise, processor 92 can route messages from any of Ethernet interface 91, Wi-Fi interface 43, and VLC network controller 34 to any other such network interface.
The protocol for communicating through free space using visible light can be the same as, or different from, the protocol described in one or more priority applications listed herein. In this example FIG. 7, LEDs 36 can be configured to continuously provide illumination and communicate for instance with lamps 17, 18, or 19, building controller 11, or wireless communication device 20 at any time. As another possibility, LEDs 36 could typically be turned off and electronic device 16 could be in a low power state until a user first touches touch screen 80, after which electronic device 16 powers up, illuminates LEDs 36, and enables communication.
FIG. 6 and FIG. 7 are just examples of many possible diagrams for an electronic device 16 comprising an HMI 21. Although FIGS. 6 and 7 illustrate the HMI 21 of the electronic device 16 as including a touch screen 80 and LCD 81, the HMI could have any one of many other possible mechanical forms that do not necessarily include touch screen 80 or LCD 81. For example, HMI 21 could comprise mechanical buttons that are illuminated from in front, behind, above, or below. As a further example, HMI 21 could comprise an Organic LED (OLED) display instead of an LCD. Backlight 82 can be any type of light source positioned in any manner to provide illumination for HMI 21, which may have a dedicated light detector (such as a silicon photodiode) or use LEDs 36 for both emitting and detecting light. If HMI 21 comprises an OLED or any other type of active matrix display, such light source could be such active matrix display. Likewise, an OLED display could be the detector as well.
Electronic device 16 could be battery or solar powered, or powered in any other way instead of being powered by AC mains 31. Electronic device 16 could be synchronized to lamps 17, 18, and 19 through any one of a number means, or not at all. Electronic device 16 could be a mobile computing device such as a smart phone, PDA, or netbook, notebook, or laptop computer, or a stationary computing device such as a desktop computer or even a television.
Menu 84 and the associated functionality described herein is just one possibility. Any number of different menus with totally different functionality is possible. If HMI 21 does not comprise some sort of display, then menu 84 may be replaced by pushbuttons for instance.
The block diagram for the electronic device 16 illustrated in FIG. 7 is just one of many possible examples. For instance, the light source could be a CCFL or even a CFL instead of the LEDs 36. The electronic device 16 could also comprise an additional photodetector. Memory 37 could be a part of processor 92. Other than the Wi-Fi and Ethernet interfaces illustrated, any type of network interface is possible to communicate with building controller 11, network 12, or wireless communication device 20. Any number of network interfaces is also possible, including none. For instance, a smart phone could communicate directly with lamps 17, 18, and 19 by modulating the backlight or the camera flash, and as such, would not need a Wi-Fi interface 43 or Ethernet interface 91. Ambient light sensors could be used to receive data transmitted optically.
FIG. 8 is an example timing diagram for transmitting data optically from electronic device 16 in a way that minimizes or eliminates flicker. The current through LEDs 36 is typically I1 103, which should produce sufficient light to see menu 84. As described in one or more priority applications listed herein, the current supplied to the LEDs 36 is periodically reduced from I1 103 to I0 102 to produce communication gaps 100 and 101 in synchronization preferentially with the AC mains 31. As noted in the priority applications, the communication gaps are produced at regular, periodic intervals of each cycle of the AC mains, and the time duration of said communication gaps may be less than one quarter of each cycle of the AC mains. During gaps 100 when data is not being transmitted, the current through LEDs 36 is reduced to I0 102, which could be a low level close to or equal to zero. During gaps 101 when data is being transmitted, the current through LEDs 36 is modulated between I0 102 and I2 104, which is higher than I0 102, so that the LEDs 36 emit light at two different output levels. I2 104 is preferentially, but not necessarily, the highest current LEDs 36 can tolerate in order to produce the most light to communicate the maximum distance. Any data modulation technique is possible including but not limited to Non-Return to Zero (NRZ) and Bi-phase.
To minimize possible flicker produced by gaps 101 during which data is transmitted at high brightness, during time 105 preceding gap 101, as shown in FIG. 8, or after gap 101 (not shown), the current through LEDs 36 is reduced from I1 103 to I0 102, such that the average brightness of light produced by LEDs 36 is the same whether or not data is transmitted during the gap times.
FIG. 8 is just one of many possible examples of a timing diagram for transmitting data optically from electronic device 16. For instance, communication gaps could occur at a faster or slower rate than the AC mains 31, at rates totally unrelated to the AC mains 31, or not at all. As an example, a video could be played on a smart phone that modulates the backlight or the light from an active display, such as an OLED, with light and dark frames in the video. The light from the electronic device could also be allowed to flicker for instance and as such could have a significantly different timing diagram from FIG. 8.
While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown and described by way of example. It should be understood, however, that the drawings and detailed description thereto are not intended to limit the invention to the particular form disclosed.
control circuitry configured to produce commands in synchronization with a frequency of the AC mains for controlling the lighting system in response to the input received from the user through the HMI, the data received by the light detector, and the data received through the network interface, and to transmit said commands to the lighting system using the light source.
2. The electronic device as recited in claim 1, wherein the light source is one or more LEDs.
3. The electronic device as recited claim 2, wherein the light detector is one or more of the LEDs used as the light source.
4. The electronic device as recited in claim 1, wherein the HMI comprises at least one of a display screen and a set of buttons, and wherein the light source illuminates the at least one of the display screen and the set of buttons of the HMI.
5. The electronic device as recited in claim 1, further comprising a wireless communication device, configured to modulate light from a camera flash or a display of the wireless communication device.
6. The electronic device as recited in claim 5, wherein light from the display is modulated with alternating light and dark frames of a video to produce light modulated with the data.
7. The electronic device as recited in claim 1, wherein the network interface is connected to a cable over which data is communicated, and wherein the cable communicates data according to a protocol selected from a group consisting of DALI and Ethernet.
8. The electronic device as recited in claim 1, wherein the network interface communicates data using radio waves, and wherein the radio waves communicate data according to a protocol selected from a group consisting of Zigbee, IEEE802.11, and Bluetooth.
9. The electronic device as recited in claim 1, wherein the data received by the light detector and the data transmitted by the light source are communicated using a visible light communication (VLC) network controller of the electronic device.
control circuitry configured to produce commands for controlling the lighting system in response to the data received by the light detector and the data received through the network interface, and to transmit said commands to the lighting system using the light source.
11. The lamp as recited in claim 10, wherein the control circuitry is configured to retransmit the same command through the light source that is received by the light detector to enable commands to be communicated to other lamps in the lighting system.
12. The lamp as recited in claim 10, wherein the network interface is connected to a cable over which data is communicated, and wherein the cable communicates data according to a protocol selected from a group consisting of DALI and Ethernet.
13. The lamp as recited in claim 10, wherein the network interface communicates data using radio waves, and wherein the radio waves communicate data according to a protocol selected from a group consisting of Zigbee, IEEE802.11, and Bluetooth.
wherein the electronic device is configured to produce commands in response to the user input to the HMI, and to forward at least one of said commands to the light source optically through free space using visible light.
15. The lighting system as recited in claim 14, wherein the building controller communicates with the electronic device over copper wire or an RF communication channel.
16. The lighting system as recited in claim 14, wherein the LED and the electronic device communicate in synchronization with each other.
17. The lighting system as recited in claim 16, wherein the LED and the electronic device are coupled to an AC mains and communicate in synchronization with a frequency or phase of the AC mains.
18. The lighting system as recited in claim 14, wherein the building controller communicates with the electronic device using the DALI protocol.
19. The lighting system as recited in claim 14, wherein the building controller communicates with the electronic device using Ethernet.
20. The lighting system as recited in claim 14, wherein the building controller communicates with the electronic device using Zigbee, IEEE 802.11, or Bluetooth.
21. The lighting system as recited in claim 14, wherein the electronic device enables the user to control the lighting system independent of and/or overriding the commands from the building controller.
a light detector configured for receiving data from the light source of the lighting system.
23. The lighting system as recited in claim 22, wherein the HMI comprises a touch screen or a set of buttons that are illuminated by the light source, wherein the touch screen or the set of buttons are configured for displaying information about the lighting system or for receiving the input from the user.
immediately preceding each of the subset of said communications gaps, reducing the current supplied to the visible light source to the second level for a period of time, such that an average brightness of light produced by the visible light source is the same whether or not data is transmitted during said communication gaps.
25. The method as recited in claim 24, wherein the step of transmitting data comprises modulating the current supplied to the visible light source within each of the subset of said communication gaps, so that the visible light source emits light at two different output light levels.
26. The method as recited in claim 24, further comprising restricting the time duration of said communication gaps to be less than one quarter of each cycle of said AC mains.
ES2643137B1 (en) * 2016-04-18 2018-08-29 Airis Technology Solutions, S.L. Intelligent power supply for LED lighting systems with light sensors and integrated presence and visible light communication and power line.
"Color Management of a Red, Green, and Blue LED Combinational Light Source," Avago Technologies, Mar. 2010, pp. 1-8.
"LED Fundamentals, How to Read a Datasheet (Part 2 of 2) Characteristic Curves, Dimensions and Packaging," Aug. 19, 2011, OSRAM Opto Semiconductors, 17 pages.
Chonko, "Use Forward Voltage Drop to Measure Junction Temperature," Dec. 2005, (c) 2013 Penton Media, Inc., 5 pages.
Final Office Action for U.S. Appl. No. 12/803,805 mailed Jun. 23, 2015.
Final Office Action for U.S. Appl. No. 13/773,322 mailed Sep. 2, 2015.
Final Office Action mailed Jan. 28, 2015 for U.S. Appl. No. 12/806,117.
Final Office Action mailed Jul. 9, 2013 for U.S. Appl. No. 12/806,118.
Final Office Action mailed Jun. 14, 2013 for U.S. Appl. No. 12/806,117.
Final Office Action mailed Jun. 18, 2014 for U.S. Appl. No. 13/231,077.
Final Office Action mailed Nov. 28, 2011 for U.S. Appl. No. 12/360,467.
Final Office Action Mailed Oct. 11, 2012 for U.S. Appl. No. 12/806,121.
Final Office Action Mailed Sep. 12, 2012 for U.S. Appl. No. 12/584,143.
Hall et al., "Jet Engine Control Using Ethernet with a BRAIN (Postprint)," AIAA/ASME/SAE/ASEE Joint Propulsion Conference and Exhibition, Jul. 2008, pp. 1-18.
International Search Report & Written Opinion for PCT/US2012/052774 mailed Feb. 4, 2013.
International Search Report & Written Opinion for PCT/US2014/068556 mailed Jun. 22, 2015.
International Search Report & Written Opinion mailed Oct. 28, 2015 for PCT/US2015/037660.
International Search Report & Written Opinion mailed Sep. 19, 2012 for PCT/US2012/045392.
International Search Report & Written Opinion, PCT/US2010/000219, mailed Oct. 12, 2010.
International Search Report & Written Opinion, PCT/US2010/001919, mailed Feb. 24, 2011.
International Search Report & Written Opinion, PCT/US2010/002171, mailed Nov. 24, 2010.
International Search Report & Written Opinion, PCT/US2010/004953, mailed Mar. 22, 2010.
International Search Report & Written Opinion, PCT/US2013/027157, May 16, 2013.
Johnson, "Visible Light Communications," CTC Tech Brief, Nov. 2009, 2 pages.
Kebemou, "A Partitioning-Centric Approach for the Modeling and the Methodical Design of Automotive Embedded System Architectures," Dissertation of Technical University of Berlin, 2008, 176 pages.
Notice of Allowance for U.S. Appl. No. 12/806,117 mailed Nov. 18, 2015.
Notice of Allowance for U.S. Appl. No. 14/510,243 mailed Nov. 6, 2015.
Notice of Allowance mailed Aug. 21, 2014 for U.S. Appl. No. 12/584,143.
Notice of Allowance mailed Feb. 21, 2014 for U.S. Appl. No. 12/806,118.
Notice of Allowance mailed Feb. 25, 2013 for U.S. Appl. No. 12/806,121.
Notice of Allowance mailed Feb. 4, 2013 for U.S. Appl. No. 12/806,113.
Notice of Allowance mailed Jan. 20, 2012 for U.S. Appl. No. 12/360,467.
Notice of Allowance mailed Jan. 28, 2014 for U.S. Appl. No. 13/178,686.
Notice of Allowance mailed Mar. 30, 2015 for U.S. Appl. No. 14/097,355.
Notice of Allowance mailed May 22, 2015 for U.S. Appl. No. 14/510,212.
Notice of Allowance mailed May 3, 2013 for U.S. Appl. No. 12/806,126.
Notice of Allowance mailed Oct. 15, 2012 for U.S. Appl. No. 12/806,113.
Notice of Allowance mailed Oct. 31, 2013 for U.S. Appl. No. 12/924,628.
Notice of Allowance mailed Oct. 9, 2015 for U.S. Appl. No. 14/604,881.
Notice of Allowance mailed Sep. 11, 2015 for U.S. Appl. No. 13/970,944.
Notice of Allowance mailed Sep. 25, 2015 for U.S. Appl. No. 14/604,886.
O'Brien et al., "Visible Light Communications and Other Developments in Optical Wireless," Wireless World Research Forum, 2006, 26 pages.
Office Action for U.S. Appl. No. 13/970,964 mailed Jun. 29, 2015.
Office Action for U.S. Appl. No. 13/970,990 mailed Aug. 20, 2015.
Office Action for U.S. Appl. No. 14/510,243 mailed Jul. 28, 2015.
Office Action for U.S. Appl. No. 14/510,266 mailed Jul. 31, 2015.
Office Action for U.S. Appl. No. 14/510,283 mailed Jul. 29, 2015.
Office Action mailed Apr. 22, 2014 for U.S. Appl. No. 12/806,114.
Office Action mailed Apr. 8, 2015 for U.S. Appl. No. 14/305,456.
Office Action Mailed Aug. 2, 2012 for U.S. Appl. No. 12/806,114.
Office Action mailed Dec. 17, 2012 for U.S. Appl. No. 12/806,118.
Office Action mailed Dec. 4, 2013 for U.S. Appl. No. 12/803,805.
Office Action Mailed Feb. 1, 2012 for U.S. Appl. No. 12/584,143.
Office Action mailed Feb. 17, 2015 for JP Application 2012-520587.
Office Action mailed Feb. 2, 2015 for CN Application 201080035731.X.
Office Action mailed Jul. 1, 2014 for JP Application 2012-520587.
Office Action mailed Jul. 10, 2012 for U.S. Appl. No. 12/806,113.
Office Action Mailed Jul. 11, 2012 for U.S. Appl. No. 12/806,121.
Office Action mailed Jun. 10, 2013 for U.S. Appl. No. 12/924,628.
Office Action mailed Jun. 23, 2014 for U.S. Appl. No. 12/806,117.
Office Action mailed Jun. 27, 2013 for U.S. Appl. No. 13/178,686.
Office Action mailed Mar. 11, 2014 for JP Application 2012-523605.
Office Action mailed Mar. 25, 2015 for U.S. Appl. No. 14/305,472.
Office Action mailed Mar. 6, 2015 for U.S. Appl. No. 13/773,322.
Office Action mailed May 12, 2011 for U.S. Appl. No. 12/360,467.
Office Action mailed May 27, 2015 for U.S. Appl. No. 12/806,117.
Office Action mailed Nov. 12, 2013 for U.S. Appl. No. 13/231,077.
Office Action mailed Nov. 4, 2013 for CN Application No. 201080032373.7.
Office Action Mailed Oct. 2, 2012 for U.S. Appl. No. 12/806,117.
Office Action mailed Oct. 24, 2013 for U.S. Appl. No. 12/806,117.
Office Action mailed Oct. 9, 2012 for U.S. Appl. No. 12/806,126.
Office Action mailed Sep. 10, 2014 for U.S. Appl. No. 12/803,805.
Office Action mailed Sep. 24, 2014 for JP Application 2012-523605.
Partial International Search Report for PCT/US2015/037660 mailed Aug. 21, 2015.
Partial International Search Report for PCT/US2015/045252 mailed Nov. 18, 2015.
Partial International Search Report mailed Mar. 27, 2015 for PCT/US2014/068556.
Partial International Search Report mailed Nov. 16, 2012 for PCT/US2012/052774.
Visible Light Communication: Tutorial, Project IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs), Mar. 2008.
Zalewski et al., "Safety Issues in Avionics and Automotive Databuses," IFAC World Congress, Jul. 2005, 6 pages.

References: Application No. 61
 Application No. 61
 Application No. 61
 Application No. 61
 Application No. 61
 Application No. 61
 Application No. 61
 Application No. 61
 Application No. 61
 Application No. 61
 Application No. 61
 Application No. 61
 Application No. 61
 Application No. 61
 Application No. 61
 Application No. 61
 Application No. 61
 Application No. 61
 Application No. 201080032373