U.S. patent application number 14/870461 was filed with the patent office on 2017-03-30 for adaptive baud rate in light-based communication.
This patent application is currently assigned to OSRAM SYLVANIA INC.. The applicant listed for this patent is Anant Aggarwal, Christian Breuer, Barry Stout. Invention is credited to Anant Aggarwal, Christian Breuer, Barry Stout.
Application Number | 20170093491 14/870461 |
Document ID | / |
Family ID | 57003596 |
Filed Date | 2017-03-30 |
United States Patent
Application |
20170093491 |
Kind Code |
A1 |
Breuer; Christian ; et
al. |
March 30, 2017 |
ADAPTIVE BAUD RATE IN LIGHT-BASED COMMUNICATION
Abstract
Light-based communication (LCom) techniques are disclosed for
adaptively adjusting the baud rate of a luminaire to optimize the
LCom signal transmitted for an intended receiver device. The
adaptive baud rate can be adjusted by a process that includes, for
example: determining decoding parameters of the receiver device,
the device including a camera for receiving LCom signals, and a
display. The process further includes calculating a baud rate
suitable for the receiver device based on the decoding parameters,
and causing the baud rate to be set at the luminaire. The process
may further include at least one of: verifying the baud rate at the
receiver device; adjusting the decoding parameters of the receiver
device if baud rate cannot be adjusted to meet a current
configuration of decoding parameters; and prompting a user to
rotate receiver device to improve orientation of the luminaire with
respect to a raster direction of the camera.
Inventors: |
Breuer; Christian;
(Newburyport, MA) ; Aggarwal; Anant; (Waltham,
MA) ; Stout; Barry; (Beverly, MA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Breuer; Christian
Aggarwal; Anant
Stout; Barry |
Newburyport
Waltham
Beverly |
MA
MA
MA |
US
US
US |
|
|
Assignee: |
OSRAM SYLVANIA INC.
Danvers
MA
|
Family ID: |
57003596 |
Appl. No.: |
14/870461 |
Filed: |
September 30, 2015 |
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
H04W 28/0215 20130101;
H04B 10/114 20130101; H04B 10/07953 20130101; H04W 4/026 20130101;
H04B 10/116 20130101 |
International
Class: |
H04B 10/116 20060101
H04B010/116; H04W 4/02 20060101 H04W004/02; H04W 28/02 20060101
H04W028/02; H04B 10/079 20060101 H04B010/079 |
Claims
1. A method for setting a baud rate for light-based communication
(LCom), the method comprising: determining decoding parameters of a
receiving device, the receiving device including a camera for
receiving LCom signals, and a display; calculating a baud rate
suitable for the receiving device based on the decoding parameters;
and causing the baud rate to be set at an LCom-enabled
luminaire.
2. The method of claim 1, wherein the method is carried out at
least in part on the receiving device.
3. The method of claim 1, wherein the receiving device being a
mobile computing device.
4. The method of claim 3, wherein the receiving device is a
smartphone or tablet computer.
5. The method of claim 1, wherein the decoding parameters include
at least one of shutter speed of the camera, frame resolution of
the camera, and orientation of the luminaire with respect to a
raster direction of the camera.
6. The method of claim 1, wherein determining decoding parameters
of a receiving device includes at least one of: querying a database
of known receiving devices to identify relevant decoding
parameters; and accessing a local storage of the receiving device
to identify relevant decoding parameters.
7. The method of claim 1, wherein causing the baud rate to be set
at an LCom-enabled luminaire comprises passing the baud rate to the
luminaire via a radio frequency wireless communication channel.
8. The method of claim 1, further comprising: measuring and
verifying the baud rate at the receiving device.
9. The method of claim 1, further comprising: adjusting the
decoding parameters of the receiving device if baud rate cannot be
adjusted to meet a current configuration of decoding
parameters.
10. The method of claim 1, further comprising: determining whether
or not an ID being transmitted by the luminaire is decodable at the
baud rate; and in response to the ID being decodable at the given
baud rate, continuing to decode LCom signals at the baud rate; and
in response to the ID not being decodable at the given baud rate,
calculating a different baud rate.
11. The method of claim 1, further comprising: monitoring for
changes of luminaire in frame; and prompting a user to rotate the
receiving device to improve orientation of the luminaire with
respect to a raster direction of the camera.
12. A non-transitory computer readable medium encoded with
instructions that, when executed by one or more processors, causes
a process to be carried out for setting a baud rate for light-based
communication (LCom), the process comprising: determining decoding
parameters of a receiving device, the receiving device including a
camera for receiving LCom signals, and a display; calculating a
baud rate suitable for the receiving device based on the decoding
parameters; and causing the baud rate to be set at an LCom-enabled
luminaire.
13. The computer readable medium of claim 12, wherein the process
is carried out at least in part on the receiving device, and the
computer readable medium and one or more processors are included in
the receiving device, the receiving device being a mobile computing
device.
14. The computer readable medium of claim 12, wherein the decoding
parameters include at least one of shutter speed of the camera,
frame resolution of the camera, and orientation of the luminaire
with respect to a raster direction of the camera.
15. The computer readable medium of claim 12, wherein determining
decoding parameters of a receiving device includes at least one of:
querying a database of known receiving devices to identify relevant
decoding parameters; and accessing a local storage of the receiving
device to identify relevant decoding parameters.
16. The computer readable medium of claim 12, wherein causing the
baud rate to be set at an LCom-enabled luminaire comprises passing
the baud rate to the luminaire via a radio frequency wireless
communication channel.
17. The computer readable medium of claim 12, the process further
comprising: measuring and verifying the baud rate at the receiving
device.
18. The computer readable medium of claim 12, the process further
comprising: adjusting the decoding parameters of the receiving
device if baud rate cannot be adjusted to meet a current
configuration of decoding parameters.
19. The computer readable medium of claim 12, the process further
comprising: determining whether or not an ID being transmitted by
the luminaire is decodable at the baud rate; and in response to the
ID being decodable at the given baud rate, continuing to decode
LCom signals at the baud rate; and in response to the ID not being
decodable at the given baud rate, calculating a different baud
rate.
20. The computer readable medium of claim 12, further comprising:
monitoring for changes of luminaire in frame; and prompting a user
to rotate the receiving device to improve orientation of the
luminaire with respect to a raster direction of the camera.
Description
FIELD OF THE DISCLOSURE
[0001] The present disclosure relates to solid-state lighting (SSL)
and more particularly to light-based communication via SSL.
BACKGROUND
[0002] Global positioning system (GPS) devices are commonly used to
facilitate navigation on Earth. These GPS devices are designed to
communicate with orbiting satellites that transmit location and
time information. Closer to the Earth's surface, such
satellite-based navigation can be supplemented using local area
wireless technologies, such as Wi-Fi, which utilize radio frequency
(RF) signals to communicate with nearby compatible devices. These
types of wireless technologies typically employ wireless access
points (Wi-Fi hotspots) to establish network access, and in cases
of secured wireless networks, a password or other security
credentials normally must be provided in order to gain network
access.
BRIEF DESCRIPTION OF THE DRAWINGS
[0003] FIG. 1 is a block diagram illustrating an example
light-based communication (LCom) system configured in accordance
with an embodiment of the present disclosure.
[0004] FIG. 2A is a block diagram illustrating an LCom-enabled
luminaire configured in accordance with an embodiment of the
present disclosure.
[0005] FIG. 2B is a block diagram illustrating an LCom-enabled
luminaire configured in accordance with another embodiment of the
present disclosure.
[0006] FIG. 3 illustrates an example arbitrary LCom signal as may
be transmitted by an LCom-enabled luminaire, in accordance with an
embodiment of the present disclosure.
[0007] FIG. 4 illustrates an example computing device configured in
accordance with an embodiment of the present disclosure.
[0008] FIG. 5A illustrates an example LCom system, including an
LCom-enabled luminaire and a computing device, in accordance with
an embodiment of the present disclosure.
[0009] FIG. 5B illustrates an example method for emitting position
information from an LCom-enabled luminaire, in accordance with an
embodiment of the present disclosure.
[0010] FIG. 5C illustrates an example graphical map of LCom-enabled
luminaires deployed in a given venue, and corresponding LCom
transmissions indicating the location of that particular luminaire
within the venue, in accordance with an embodiment of the present
disclosure.
[0011] FIG. 5D illustrates an example scenario in which a computing
device is configured to output instruction by way of visual
feedback to a user, in accordance with an embodiment of the present
disclosure.
[0012] FIGS. 6A and 6B each illustrate example orientations between
luminaires and a computing device, and how that affects the ability
of the device raster lines to decode LCom messages from the
luminaires.
[0013] FIG. 7 is a flow chart illustrating a method for setting a
baud rate for LCom communication, in accordance with an embodiment
of the present disclosure.
[0014] FIG. 8 illustrates measurement of the length of the
luminaire in raster lines which corresponds to the ability to
resolve the luminaire's ID, in accordance with an embodiment of the
present disclosure.
[0015] FIG. 9 illustrates different baud rates, according to some
embodiments of the present disclosure.
[0016] These and other features of the present embodiments will be
understood better by reading the following detailed description,
taken together with the figures herein described. The accompanying
drawings are not intended to be drawn to scale. In the drawings,
each identical or nearly identical component that is illustrated in
various figures may be represented by a like numeral. For purposes
of clarity, not every component may be labeled in every
drawing.
DETAILED DESCRIPTION
[0017] Light-based communication (LCom) generally refers to the
communication between a luminary and an optical receiver device,
such as a smartphone, tablet, or other mobile computing device,
using a pulsing light signal that is encoded with data. In
particular, the receiver device includes a camera or other imaging
circuitry capable of sensing pulsing light from the luminary, and
may further include one or more processors for processing the
received light. The light utilized in LCom may be of any spectral
band, visible or otherwise, and may be of any intensity, as desired
for a given target application or end-use. With respect to visible
light, note that the pulsing is done at a relatively high frequency
(e.g., 1 KHz or higher), and is generally imperceptible to the
human eye, so that light-based communication can co-exist with a
given illumination scheme. One application of LCom is indoor
navigation, which can be used to supplement or otherwise enhance
the precision and accuracy over other technologies such as GPS and
WiFi locationing. For instance, LCom could be used in retail
setting to guide customers (empowered with a smartphone or other
suitable mobile computing device) to products of interest on a
given shelf within a given store. LCom for indoor navigation
assumes that the light fixture itself knows its location. However,
a non-trivial challenge associated with LCom is creating an
encoding/decoding schema that works across most if not all mobile
computing devices. In particular, the baud rate of the luminaire
has to be compatible with the given optical receiver device. To
this end, creating a universal or otherwise broadly applicable
encoding/decoding schema is a challenge given the wide variety of
receiver device platform configurations with respect to features
such as cameras, operating systems, and processing power (consider,
for instance, the various smartphones available from manufacturers
such as Samsung and Apple Inc). In short, any given mobile
computing device should work under the same set of luminaires.
[0018] Thus, and in accordance with an embodiment, techniques are
disclosed for adaptively adjusting the baud rate of a given
luminaire to optimize the LCom light signal transmitted for a given
computing device (sometimes referred to as a "receiver" device).
The optimization can be accomplished, for example, by providing
decoding parameters of the given receiver device back to the
luminaire through a wireless back channel, such as a Bluetooth or
WiFi or other radio frequency channel, or even a wired channel such
as a USB port at the entrance of a given LCom-enabled facility
(where the receiver device could be plugged-in and queried for its
decoding parameters). Decoding parameters may generally include any
information which allows the luminaire to identify a baud rate at
which it can transmit LCom signals that will be decodable by the
intended receiver device. Such decoding parameters may be, for
example, a make and model of the receiver device (such that the
decoding capabilities can then be looked up or otherwise inferred
based on that information), or more specific information such as
processing speed, camera/sensor types, number of raster lines,
screen resolution, and other information that can be used to
determine a suitable baud rate. In any such cases, based on the
receiver device's configuration (e.g., type of hardware, decoding
ability), and possibly other factors such as receiver device
orientation and environment, that receiver device can request a
different baud rate to increase the accuracy/reliability of the
LCom messaging. The baud rate can be provided to the luminaire in
real time or computed by the luminaire in real time. Thus, the baud
rate of a given luminaire can be dynamic and controllable
on-the-fly and can therefore be adapted to any receiver device.
Note that the adapting may not only enable an LCom-based
communication channel to be created, but can also be used to
improve an already existing LCom-based communication channel by,
for example, reducing delay times and increasing reliability.
[0019] One application where the techniques provided herein can be
used is for LCom-based indoor navigation, which relies on
luminaires transmitting their location to a user mobile computing
device (e.g., smartphone, tablet, or other mobile computing device
capable of receiving a processing LCom signals). Existing
smartphones, tablets, and other such mobile computing devices
typically utilize a combination of global positioning system (GPS)
and Wi-Fi technologies to provide navigation capabilities, such as
various Wi-Fi positioning systems (WPS). However, these existing
GPS-based and Wi-Fi-based techniques are not particularly
well-suited for indoor navigation. In particular, GPS has an
accuracy of only several meters, and the availability and range of
Wi-Fi network connections are limited by factors such as the
placement of Wi-Fi hotspots, security restrictions imposed by
network providers, and other environmental factors. Thus, the
combination of GPS and Wi-Fi can fail to achieve sufficiently
refined accuracies for purposes of indoor navigation. As will be
appreciated, the LCom techniques provided herein can be used to
supplement such navigation systems, but the techniques may also be
used on their own. Any number of other applications may also
benefit from the adaptive baud rate techniques.
[0020] As will be further appreciated in light of this disclosure,
baud rate for LCom is similar to baud rate for electronic
communication. The definition of baud rate is a number related to
the speed of data transmission in a given communication system. The
rate generally indicates the number of electrical oscillations (or
other intentional oscillations) per second that occurs within a
data transmission. This means that the higher the baud rate, the
more bits per second that are transferred.
[0021] A number of advantages associated with optimizing the baud
rate for LCom will be apparent in light of this disclosure. For
instance, in some embodiments, the techniques provided herein can
be used to adapt the baud rate of given luminaire to accommodate
different decoding hardware (with respect to past, present, and
future receiver devices). In some cases, the techniques can be used
to compensate for orientation and position of the receiver device
relative to the luminaire, and to guarantee that LCom data is
transmitted within one frame (frame captured by camera of receiver
device, such as a smartphone camera). The techniques may also be
used to optimize LCom transmission in terms of delay times and
reliability, even for an established LCom communication link. In
still further embodiments, the techniques can be used to adapt to
LCom-enabled luminaires made by different manufacturers. In other
words, the luminaires could match the baud rate of other luminaires
for interoperability, which is particularly helpful when there are
currently no broadly adopted standards for defining LCom
communications.
[0022] System Architecture
[0023] FIG. 1 is a block diagram illustrating an example
light-based communication (LCom) system 10 configured in accordance
with an embodiment of the present disclosure. As can be seen,
system 10 may include one or more LCom-enabled luminaires 100
configured for light-based communicative coupling with a receiver
computing device 200 via LCom signal(s). As discussed herein, such
LCom may be provided, in accordance with some embodiments, via
visible light-based signals. In some cases, LCom may be provided in
only one direction; for instance, LCom data may be passed from a
given LCom-enabled luminaire 100 (e.g., the transmitter) to a
computing device 200 (e.g., the receiver), or from a computing
device 200 (e.g., the transmitter) to a given LCom-enabled
luminaire 100 (e.g., the receiver). In some other cases, LCom may
be provided in a bi-directional fashion between a given
LCom-enabled luminaire 100 and a computing device 200, where both
act as a transceiver device capable of transmitting and
receiving.
[0024] In some cases in which system 10 includes a plurality of
LCom-enabled luminaires 100, all (or some sub-set thereof) may be
configured for communicative coupling with one another so as to
provide inter-luminaire communication. In one such scenario, for
instance, the inter-luminaire communication can be used to notify
other luminaries 100 that a given computing device 200 is currently
present, as well as the baud rate chosen for that particular device
100. Such inter-luminaire communication is not needed, however, as
will be appreciated in light of this disclosure.
[0025] As can be further seen in this example embodiment, system 10
allows for communicative coupling with a network 300 and one or
more servers or other computer systems 301. Communicative coupling
may be provided, for example, between network 300 and computing
device 200 and/or one or more LCom-enabled luminaires 100, as
desired. The network 300 may be a local area wireless network, a
local wired network, or a combination of local wired and wireless
networks, and may further include access to a wide area network
such as the Internet or a campus-wide network. In short, network
300 can be any communications network. As will be further
appreciated herein, prior to establishing an LCom communication
link between a given device 200 and one or more of the luminaires
100, the network 300 may be used by the device 200 to provide its
decoding parameters to the luminaires 100 or computer system 300,
so that a suitable baud rate can be identified and then adopted by
the luminaires 100 to initiate LCom communications. In still other
embodiments, a pre-computed baud rate suitable for the given device
200 can be provided to the luminaire 100 by the device 200 itself,
or by a computer system 301 via network 300 once the given device
200 has been identified by that computer system 301.
[0026] The computer systems 301 may be any suitable computing
system capable of communicating over a network 300, such as a
cloud-based server computer, and may be programmed or otherwise
configured to provide an LCom related service, according to some
embodiments. For example, an LCom related service might be that the
computer system 301 is configured to provide storage of currently
available receiver device decoding parameters indexed by device
manufacture and model, for example. In that way, only the computing
device make and model need be known and the decoding parameters
could then be looked up and passed to the luminaires 100 so that a
suitable baud rate could be computed and adopted by the luminaires
100. In still other embodiments, a suitable baud rate can be looked
up on the computer system 301, and that baud rate can then be
passed to the luminaries 100 to initiate LCom communication with
the device 200. Numerous other such configurations will be apparent
in light of this disclosure.
[0027] FIG. 2A is a block diagram illustrating an LCom-enabled
luminaire 100a configured in accordance with an embodiment of the
present disclosure. FIG. 2B is a block diagram illustrating an
LCom-enabled luminaire 100b configured in accordance with another
embodiment of the present disclosure. As can be seen, a difference
between luminaire 100a and luminaire 100b is with respect to the
location of controller 150. For consistency and ease of
understanding of the present disclosure, LCom-enabled luminaires
100a and 100b hereinafter may be collectively referred to generally
as an LCom-enabled luminaire 100, except where separately
referenced. Further note that while various modules are shown as
distinct modules for purposes of illustration, any number of the
modules may be integrated with one or more other modules. For
instance, the controller 150 may be integrated with the driver 120.
Similarly, the processor(s) 140 and memory 130 may be integrated
within the controller 150. Numerous other configurations can be
used.
[0028] As can be seen, a given LCom-enabled luminaire 100 may
include one or more solid-state light sources 110, in accordance
with some embodiments. The quantity, density, and arrangement of
solid-state light sources 110 utilized in a given LCom-enabled
luminaire 100 may be customized, as desired for a given target
application or end-use. A given solid-state light source 110 may
include one or more solid-state emitters, which may be any of a
wide range of semiconductor light source devices, such as, for
example, a light-emitting diode (LED), an organic light-emitting
diode (OLED), a polymer light-emitting diode (PLED), or a
combination of any of these. A given solid-state emitter may be
configured to emit electromagnetic radiation, for example, from the
visible spectral band and/or other portions of the electromagnetic
spectrum not limited to the infrared (IR) spectral band and/or the
ultraviolet (UV) spectral band, as desired for a given target
application or end-use. In some embodiments, a given solid-state
emitter may be configured for emissions of a single correlated
color temperature (CCT) (e.g., a white light-emitting semiconductor
light source). In other embodiments, a given solid-state emitter
may be configured for color-tunable emissions. For instance, in
some cases, a given solid-state emitter may be a multi-color (e.g.,
bi-color, tri-color, etc.) semiconductor light source configured
for a combination of emissions, such as: (1) red-green-blue (RGB);
(2) red-green-blue-yellow (RGBY); (3) red-green-blue-white (RGBW);
(4) dual-white; and/or (5) a combination of any one or more
thereof. In some cases, a given solid-state emitter may be
configured as a high-brightness light source. In some embodiments,
a given solid-state emitter may be provided with a combination of
any one or more of the aforementioned example emissions
capabilities. In any case, a given solid-state emitter can be
packaged or non-packaged, as desired, and in some cases may be
populated on a printed circuit board (PCB) or other suitable
intermediate/substrate. In some cases, power and/or control
connections for a given solid-state emitter may be routed from a
given PCB to a driver 120 (discussed in turn below) and/or other
devices/componentry, as desired. Other suitable configurations for
the one or more solid-state emitters of a given solid-state light
source 110 will depend on a given application and will be apparent
in light of this disclosure.
[0029] A given solid-state light source 110 also may include one or
more optics optically coupled with its one or more solid-state
emitters. In accordance with some embodiments, the optic(s) of a
given solid-state light source 110 may be configured to transmit
the one or more wavelengths of interest of the light (e.g.,
visible, UV, IR, etc.) emitted by solid-state emitter(s) optically
coupled therewith. To that end, the optic(s) may include an optical
structure (e.g., a window, lens, dome, etc.) formed from any of a
wide range of optical materials, such as, for example: (1) a
polymer, such as poly(methyl methacrylate) (PMMA) or polycarbonate;
(2) a ceramic, such as sapphire (Al.sub.2O.sub.3) or yttrium
aluminum garnet (YAG); (3) a glass; and/or (4) a combination of any
one or more thereof. In some cases, the optic(s) of a given
solid-state light source 110 may be formed from a single (e.g.,
monolithic) piece of optical material to provide a single,
continuous optical structure. In some other cases, the optic(s) of
a given solid-state light source 110 may be formed from multiple
pieces of optical material to provide a multi-piece optical
structure. In some cases, the optic(s) of a given solid-state light
source 110 may include optical features, such as, for example: (1)
an anti-reflective (AR) coating; (2) a reflector; (3) a diffuser;
(4) a polarizer; (5) a brightness enhancer; (6) a phosphor material
(e.g., which converts light received thereby to light of a
different wavelength); and/or (7) a combination of any one or more
thereof. In some embodiments, the optic(s) of a given solid-state
light source 110 may be configured, for example, to focus and/or
collimate light transmitted therethrough. Other suitable types,
optical transmission characteristics, and configurations for the
optic(s) of a given solid-state light source 110 will depend on a
given application and will be apparent in light of this
disclosure.
[0030] In accordance with some embodiments, the one or more
solid-state light sources 110 of a given LCom-enabled luminaire 100
may be electronically coupled with a driver 120. In some cases,
driver 120 may be an electronic driver (e.g., single-channel;
multi-channel) configured, for example, for use in controlling one
or more solid-state emitters of a given solid-state light source
110. For instance, in some embodiments, driver 120 may be
configured to control the on/off state, dimming level, color of
emissions, correlated color temperature (CCT), and/or color
saturation of a given solid-state emitter (or grouping of
emitters). To such ends, driver 120 may utilize any of a wide range
of driving techniques, including, for example: (1) a pulse-width
modulation (PWM) dimming protocol; (2) a current dimming protocol;
(3) a triode for alternating current (TRIAC) dimming protocol; (4)
a constant current reduction (CCR) dimming protocol; (5) a
pulse-frequency modulation (PFM) dimming protocol; (6) a pulse-code
modulation (PCM) dimming protocol; (7) a line voltage (mains)
dimming protocol (e.g., dimmer is connected before input of driver
120 to adjust AC voltage to driver 120); and/or (8) a combination
of any one or more thereof. Other suitable configurations for
driver 120 and lighting control/driving techniques will depend on a
given application and will be apparent in light of this
disclosure.
[0031] As will be appreciated in light of this disclosure, a given
solid-state light source 110 also may include or otherwise be
operatively coupled with other circuitry/componentry, for example,
which may be used in solid-state lighting. For instance, a given
solid-state light source 110 (and/or host LCom-enabled luminaire
100) may be configured to host or otherwise be operatively coupled
with any of a wide range of electronic components, such as: (1)
power conversion circuitry (e.g., electrical ballast circuitry to
convert an AC signal into a DC signal at a desired current and
voltage to power a given solid-state light source 110); (2)
constant current/voltage driver componentry; (3) transmitter and/or
receiver (e.g., transceiver) componentry; and/or (4) local
processing componentry. When included, such componentry may be
mounted, for example, on one or more driver 120 boards, in
accordance with some embodiments.
[0032] As can be further seen from FIGS. 2A-2B, a given
LCom-enabled luminaire 100 may include memory 130 and one or more
processors 140. Memory 130 can be of any suitable type (e.g., RAM
and/or ROM, or other suitable memory) and size, and in some cases
may be implemented with volatile memory, non-volatile memory, or a
combination thereof. A given processor 140 may be configured as
typically done, and in some embodiments may be configured, for
example, to perform operations associated with a given host
LCom-enabled luminaire 100 and one or more of the applications 132
thereof (e.g., within memory 130 or elsewhere). In some cases,
memory 130 may be configured to be utilized, for example, for
processor workspace (e.g., for one or more processors 140) and/or
to store media, programs, applications, and/or content on a host
LCom-enabled luminaire 100 on a temporary or permanent basis. In
one example embodiment, the memory 130 stores location information
that indicates where the luminaire is deployed (for purposes of
facilitating navigation, as previously explained), and may further
include a look-up table (LUT) or other memory facility that indexes
baud rates by computing device type. Table 1 shows an example
look-up table according to one such embodiment. Assume that each of
A through F represents a transmission baud rate which can be
utilized by luminaires 100. Thus, in some cases, a given processor
140 can identify the baud rate at which the luminary 100 should
transmit based on received decoding parameters (these parameters
may be provided network 300, for example, whether those parameters
be high level information such as make and model of the subject
computing device 200 or lower level information about that device
200 such as its sensing capability (e.g., camera imaging speed and
resolution).
TABLE-US-00001 TABLE 1 Baud Rates LUT Model Make 5S 6S Galaxy S6
Galaxy S5 Moto X Moto G Apple Inc A B Samsung C D Motorola E F
[0033] The one or more applications 132 stored in memory 130 can be
accessed and executed, for example, by the one or more processors
140 of a given LCom-enabled luminaire 100. In accordance with some
embodiments, a given application or module 132 can be implemented
in any suitable standard and/or custom/proprietary programming
language, such as, for example: (1) C; (2) C++; (3) objective C;
(4) JavaScript; and/or (5) any other suitable custom or proprietary
instruction sets. In a more general sense, the applications or
modules 132 can be instructions encoded on any suitable
non-transitory machine-readable medium that, when executed by one
or more processors 140, carries out functionality of a given
LCom-enabled luminaire 100, in part or in whole. In one example
embodiment, at least one of these modules 132 is a routine for
determining a baud rate for a given computing device 200, based on
decoding parameters received from that device 200. In still other
embodiments, the at least one module 132 receives the target baud
rate from the computing device 200 or the network 300. In any case,
the baud rate can be dynamically selected for a given computing
device 200, and the luminaire can then execute LCom communication
using that baud rate.
[0034] In accordance with some embodiments, the one or more
solid-state light sources 110 of a given LCom-enabled luminaire 100
can be electronically controlled, for example, to output light
and/or light encoded with LCom data (e.g., an LCom signal). To that
end, a given LCom-enabled luminaire 100 may include or otherwise be
communicatively coupled with one or more controllers 150. In some
such example embodiments, such as that illustrated in FIG. 2A, a
controller 150 may be hosted by a given LCom-enabled luminaire 100
and operatively coupled (e.g., via a communication
bus/interconnect) with the one or more solid-state light sources
110 (1-N) of that LCom-enabled luminaire 100. In this example case,
controller 150 may output a digital control signal to any one or
more of the solid-state light sources 110 and may do so, for
example, based on wired and/or wireless input received from a given
local source (e.g., such as on-board memory 130) and/or remote
source (e.g., such as a control interface or network 300). As a
result, a given LCom-enabled luminaire 100 may be controlled in
such a manner as to output any number of output beams (1-N), which
may include light and/or LCom data (e.g., an LCom signal), as
desired for a given target application or end-use. However, the
present disclosure is not so limited.
[0035] For example, in some other embodiments, such as that
illustrated in FIG. 2B, a controller 150 may be packaged or
otherwise hosted, in part or in whole, by a given solid-state light
source 110 of a given LCom-enabled luminaire 100 and operatively
coupled (e.g., via a communication bus/interconnect) with the one
or more solid-state light sources 110. If LCom-enabled luminaire
100 includes a plurality of such solid-state light sources 110
hosting their own controllers 150, then each such controller 150
may be considered, in a sense, a mini-controller, providing
LCom-enabled luminaire 100 with a distributed controller 150. In
some embodiments, controller 150 may be populated, for example, on
one or more PCBs of the host solid-state light source 110. In this
example case, controller 150 may output a digital control signal to
an associated solid-state light source 110 of LCom-enabled
luminaire 100 and may do so, for example, based on wired and/or
wireless input received from a given local source (e.g., such as
on-board memory 130) and/or remote source (e.g., such as a control
interface, optional network 300, etc.). As a result, LCom-enabled
luminaire 110 may be controlled in such a manner as to output any
number of output beams (1-N), which may include light and/or LCom
data (e.g., an LCom signal), as desired for a given target
application or end-use.
[0036] In accordance with some embodiments, a given controller 150
may host one or more lighting control modules and can be programmed
or otherwise configured to output one or more control signals, for
example, to adjust the operation of the solid-state emitter(s) of a
given solid-state light source 110 according to the desired baud
rate. For example, in some cases, a given controller 150 may be
configured to output a control signal to control whether the light
beam of a given solid-state emitter is on/off. In some instances, a
given controller 150 may be configured to output a control signal
to control the intensity/brightness (e.g., dimming; brightening) of
the light emitted by a given solid-state emitter. In some cases, a
given controller 150 may be configured to output a control signal
to control the color (e.g., mixing; tuning) of the light emitted by
a given solid-state emitter. Thus, if a given solid-state light
source 110 includes two or more solid-state emitters configured to
emit light having different wavelengths, the control signal may be
used to adjust the relative brightness of the different solid-state
emitters in order to change the mixed color output by that
solid-state light source 110. In some embodiments, controller 150
may be configured to output a control signal to encoder 172
(discussed below) to facilitate encoding of LCom data for
transmission by a given LCom-enabled luminaire 100. In some
embodiments, controller 150 may be configured to output a control
signal to modulator 174 (discussed below) to facilitate modulation
of an LCom signal for transmission by a given LCom-enabled
luminaire 100. Other suitable configurations and control signal
output for a given controller 150 of a given LCom-enabled luminaire
100 will depend on a given application and will be apparent in
light of this disclosure.
[0037] In accordance with some embodiments, a given LCom-enabled
luminaire 100 may include an encoder 172. In some embodiments,
encoder 172 may be configured, for example, to encode LCom data in
preparation for transmission thereof by the host LCom-enabled
luminaire 100. To that end, encoder 172 may be provided with any
suitable configuration, as will be apparent in light of this
disclosure.
[0038] In accordance with some embodiments, a given LCom-enabled
luminaire 100 may include a modulator 174. In some embodiments,
modulator 174 may be configured, for example, to modulate an LCom
signal in preparation for transmission thereof by the host
LCom-enabled luminaire 100. In some embodiments, modulator 174 may
be a single-channel or multi-channel electronic driver (e.g.,
driver 120) configured, for example, for use in controlling the
output of the one or more solid-state emitters of a given
solid-state light source 110. In some embodiments, modulator 174
may be configured to control the on/off state, dimming level, color
of emissions, correlated color temperature (CCT), and/or color
saturation of a given solid-state emitter (or grouping of
emitters). To such ends, modulator 174 may utilize any of a wide
range of driving techniques, including, for example: (1) a
pulse-width modulation (PWM) dimming protocol; (2) a current
dimming protocol; (3) a triode for alternating current (TRIAC)
dimming protocol; (4) a constant current reduction (CCR) dimming
protocol; (5) a pulse-frequency modulation (PFM) dimming protocol;
(6) a pulse-code modulation (PCM) dimming protocol; (7) a line
voltage (mains) dimming protocol (e.g., dimmer is connected before
input of modulator 174 to adjust AC voltage to modulator 174);
and/or (8) any other suitable lighting control/driving technique,
as will be apparent in light of this disclosure. Other suitable
configurations and control/driving techniques for modulator 174
will depend on a given application and will be apparent in light of
this disclosure.
[0039] In accordance with some embodiments, a given LCom-enabled
luminaire 100 may include a multiplier 176. Multiplier 176 may be
configured as typically done, and in some example embodiments may
be configured to combine an input received from an upstream
modulator 174 with an input received from an ambient light sensor
165 (discussed below). In some instances, multiplier 176 may be
configured to increase and/or decrease the amplitude of a signal
passing therethrough, as desired. Other suitable configurations for
multiplier 176 will depend on a given application and will be
apparent in light of this disclosure. In accordance with some
embodiments, a given LCom-enabled luminaire 100 may include an
adder 178. Adder 178 may be configured as typically done, and in
some example embodiments may be configured to combine an input
received from an upstream multiplier 178 with a DC level input. In
some instances, adder 178 may be configured to increase and/or
decrease the amplitude of a signal passing therethrough, as
desired. Other suitable configurations for adder 178 will depend on
a given application and will be apparent in light of this
disclosure.
[0040] In accordance with some embodiments, a given LCom-enabled
luminaire 100 may include a digital-to-analog converter (DAC) 180.
DAC 180 may be configured as typically done, and in some example
embodiments may be configured to convert a digital control signal
into an analog control signal to be applied to a given solid-state
light source 110 of the host LCom-enabled luminaire 100 to output
an LCom signal therefrom. Note that DAC 180 may further be
integrated into controller 150, in some embodiments. Other suitable
configurations will be apparent in light of this disclosure.
[0041] In accordance with some embodiments, a given LCom-enabled
luminaire 100 may include one or more sensors 160. In some
embodiments, a given LCom-enabled luminaire 100 optionally may
include an altimeter 161. When included, altimeter 161 may be
configured as typically done, and in some example embodiments may
be configured to aid in determining the altitude of a host
LCom-enabled luminaire 100 with respect to a given fixed level
(e.g., a floor, a wall, the ground, or other surface). In some
embodiments, a given LCom-enabled luminaire 100 optionally may
include a geomagnetic sensor 163. When included, geomagnetic sensor
163 may be configured as typically done, and in some example
embodiments may be configured to determine the orientation and/or
movement of a host LCom-enabled luminaire 100 relative to a
geomagnetic pole (e.g., geomagnetic north) or other desired
heading, which may be customized as desired for a given target
application or end-use. In some embodiments, a given LCom-enabled
luminaire 100 optionally may include an ambient light sensor 165.
When included, ambient light sensor 165 may be configured as
typically done, and in some example embodiments may be configured
to detect and measure ambient light levels in the surrounding
environment of the host LCom-enabled luminaire 100. In some cases,
ambient light sensor 165 may be configured to output a signal, for
example, to a multiplier 176 of LCom-enabled luminaire 100. In some
embodiments, a given LCom-enabled luminaire 100 optionally may
include a gyroscopic sensor 167. When included, gyroscopic sensor
167 may be configured as typically done, and in some example
embodiments may be configured to determine the orientation (e.g.,
roll, pitch, and/or yaw) of the host LCom-enabled luminaire 100. In
some embodiments, a given LCom-enabled luminaire 100 optionally may
include an accelerometer 169. When included, accelerometer 169 may
be configured as typically done, and in some example embodiments
may be configured to detect motion of the host LCom-enabled
luminaire 100. In any case, a given sensor 160 of a given host
LCom-enabled luminaire 100 may include mechanical and/or
solid-state componentry, as desired for a given target application
or end-use. Also, it should be noted that the present disclosure is
not so limited only to these example optional sensors 160, as
additional and/or different sensors 160 may be provided as desired
for a given target application or end-use, in accordance with some
other embodiments, or no sensors 160 may be provided, as the case
may be. Numerous configurations will be apparent in light of this
disclosure.
[0042] In accordance with some embodiments, a given LCom-enabled
luminaire 100 may include a communication module 170, which may be
configured for wired (e.g., Universal Serial Bus or USB, Ethernet,
FireWire, etc.) and/or wireless (e.g., Wi-Fi, Bluetooth, etc.)
communication, as desired. In accordance with some embodiments,
communication module 170 may be configured to communicate locally
and/or remotely utilizing any of a wide range of wired and/or
wireless communications protocols, including, for example: (1) a
digital multiplexer (DMX) interface protocol; (2) a Wi-Fi protocol;
(3) a Bluetooth protocol; (4) a digital addressable lighting
interface (DALI) protocol; (5) a ZigBee protocol; and/or (6) a
combination of any one or more thereof. It should be noted,
however, that the present disclosure is not so limited to only
these example communications protocols, as in a more general sense,
and in accordance with some embodiments, any suitable
communications protocol, wired and/or wireless, standard and/or
custom/proprietary, may be utilized by communication module 170, as
desired for a given target application or end-use. In some
instances, communication module 170 may be configured to facilitate
inter-luminaire communication between LCom-enabled luminaires 100.
In addition or alternatively, communication module 170 may be
configured so as to allow for receipt of information from network
300, such as decoding parameters associated with the computing
device 200, or a pre-computed baud rate. As explained herein, the
decoding parameters associated with the computing device 200 can be
used by the luminaire to compute a baud rate suitable for that
computing device 200. Whether the baud rate is computed in real
time at the luminaire or received from somewhere else, the baud
rate can then be used to generate the LCom signals emitted by that
luminaire 100. The communication module 170 may be configured to
use any suitable wired and/or wireless transmission technologies
(e.g., radio frequency, or RF, transmission; infrared, or IR, light
modulation; etc.), as desired for a given target application or
end-use. Other suitable configurations for communication module 170
will depend on a given application and will be apparent in light of
this disclosure.
[0043] As previously noted, a given LCom-enabled luminaire 100 may
be configured, in accordance with some embodiments, to output light
and/or light encoded with LCom data (e.g., an LCom signal). FIG. 3
illustrates an example arbitrary LCom signal as may be transmitted
by an LCom-enabled luminaire 100, in accordance with an embodiment
of the present disclosure. As can be seen here, LCom-enabled
luminaire 100 may be configured to transmit a given LCom signal at
a given baud rate over a given time interval (t.sub.1-t.sub.0). In
some cases, a given LCom-enabled luminaire 100 may be configured to
repeatedly output its one or more LCom signals. In any case, the
baud rate may be customized, as desired for a given target
application or end-use.
[0044] FIG. 4 illustrates an example computing device 200
configured in accordance with an embodiment of the present
disclosure. As discussed herein, computing device 200 may be
configured, in accordance with some embodiments: (1) to detect the
light pulses of an LCom signal emitted by a transmitting
LCom-enabled luminaire 100; and (2) to decode the LCom data from a
detected LCom signal. To these ends, computing device 200 can be
any of a wide range of computing platforms, mobile or otherwise.
For example, in accordance with some embodiments, computing device
200 can be, in part or in whole: (1) a laptop/notebook computer or
sub-notebook computer; (2) a tablet or phablet computer; (3) a
mobile phone or smartphone; (4) a personal digital assistant (PDA);
(5) a portable media player (PMP); (6) a cellular handset; (7) a
handheld gaming device; (8) a gaming platform; (9) a desktop
computer; (10) a television set; (11) a wearable or otherwise
body-borne computing device, such as a smartwatch, smart glasses,
or smart headgear; and/or (12) a combination of any one or more
thereof. Other suitable configurations for computing device 200
will depend on a given application and will be apparent in light of
this disclosure.
[0045] As can be further seen from FIG. 4, computing device 200 may
include memory 210 and one or more processors 220. Memory 210 can
be of any suitable type (e.g., RAM and/or ROM, or other suitable
memory) and size, and in some cases may be implemented with
volatile memory, non-volatile memory, or a combination thereof. A
given processor 220 of computing device 200 may be configured as
typically done, and in some embodiments may be configured, for
example, to perform operations associated with computing device 200
and one or more of the modules thereof (e.g., within memory 210 or
elsewhere). In some cases, memory 210 may be configured to be
utilized, for example, for processor workspace (e.g., for one or
more processors 220) and/or to store media, programs, applications,
and/or content on computing device 200 on a temporary or permanent
basis. The one or more modules stored in memory 210 (e.g., such as
OS 212, UI 214, and/or one or more applications 216) can be
accessed and executed, for example, by the one or more processors
220 of computing device 200. Just as explained with respect to
memory 130 of the luminaires 100, memory 210 of the device 200 may
include information that can be used to compute or otherwise set
baud rate, whether it be pre-computed baud rates themselves or
decoding parameters can that can be used to determine an
appropriate baud rate. In some cases, memory 210 includes an LUT or
other memory facility that indexes baud rates by computing device
type, as previously discussed with respect to Table 1.
Alternatively, memory 210 may include one or more files that
contain decoding parameters that can be recalled or otherwise
interrogated to inform the baud rate computing process, as will be
appreciated in light of this disclosure.
[0046] OS 212 can be implemented with any suitable OS, mobile or
otherwise, such as, for example: (1) Android OS from Google, Inc.;
(2) iOS from Apple, Inc.; (3) BlackBerry OS from BlackBerry Ltd.;
(4) Windows Phone OS from Microsoft Corp; (5) Palm OS/Garnet OS
from Palm, Inc.; (6) an open source OS, such as Symbian OS; and/or
(7) a combination of any one or more thereof. As will be
appreciated in light of this disclosure, OS 212 may be configured,
for example, to aid in processing LCom data during its flow through
computing device 200. Other suitable configurations and
capabilities for OS 212 will depend on a given application and will
be apparent in light of this disclosure. A user interface (UI)
module 214 is provided as commonly done, and generally allows for
user interaction with the device 200 (e.g., such as a graphical
touched-based UI on various smartphones and tablets). Any number of
user interface schemes can be used.
[0047] In accordance with some embodiments, memory 210 may have
stored therein (or otherwise have access to) one or more
applications 216. In some instances, computing device 200 may be
configured to receive input, for example, via one or more
applications 216 stored in memory 210 (e.g., such as an indoor
navigation application). In accordance with some embodiments, a
given application or module 216 can be implemented in any suitable
standard and/or custom/proprietary programming language, such as,
for example: (1) C; (2) C++; (3) objective C; (4) JavaScript;
and/or (5) any other suitable custom or proprietary instruction
sets. In a more general sense, the applications or modules 216 can
be instructions encoded on any suitable non-transitory
machine-readable medium that, when executed by one or more
processors 220, carries out functionality of a given computing
device 200, in part or in whole. In one example embodiment, at
least one of these modules 216 is a routine programmed or otherwise
configured to provide decoding parameters of computing device 200
to luminaire 100, so that luminaire 100 can determine a baud rate
suitable for the device 200. In still other embodiments, the at
least one module 216 may be configured to compute the target baud
rate itself and provide that baud rate to the luminaire 100, either
directly via network 300 or indirectly via a computer system 301.
In any case, the baud rate can be dynamically selected for a given
computing device 200, and the luminaire can then execute LCom
communication with that device 200 using that baud rate. The at
least one module 216 may be further configured to receive LCom
signals and decode those signals. In addition, at least one module
216 may be further configured to also monitor the luminaire for any
changes (orientation, with respect to computing device 200), and to
update the baud rate computation periodically (and pass any changes
along to the luminaire 100). Likewise, in some embodiments, the at
least one module 216 may be further configured to optionally try to
adjust its own settings to optimize decoding in effort to deal with
situations where control by luminaire 100 is not available, for
whatever reason.
[0048] As can be seen further from FIG. 4, computing device 200 may
include a display 230, in accordance with some embodiments. Display
230 can be any electronic visual display or other device configured
to display or otherwise generate an image (e.g., image, video,
text, and/or other displayable content) there at. In some
instances, display 230 may be integrated, in part or in whole, with
computing device 200, whereas in some other instances, display 230
may be a stand-alone component configured to communicate with
computing device 200 using any suitable wired and/or wireless
communications means. In some cases, display 230 optionally may be
a touchscreen display or other touch-sensitive display. To that
end, display 230 may utilize any of a wide range of touch-sensing
techniques, such as, for example: (1) resistive touch-sensing; (2)
capacitive touch-sensing; (3) surface acoustic wave (SAW)
touch-sensing; (4) infrared (IR) touch-sensing; (5) optical imaging
touch-sensing; and/or (6) a combination of any one or more thereof.
In a more general sense, and in accordance with some embodiments,
an optionally touch-sensitive display 230 generally may be
configured to detect or otherwise sense direct and/or proximate
contact from a user's finger, stylus, or other suitable implement
at a given location of that display 230. In some cases, an
optionally touch-sensitive display 230 may be configured to
translate such contact into an electronic signal that can be
processed by computing device 200 (e.g., by the one or more
processors 220 thereof) and manipulated or otherwise used to
trigger a given GUI action. In some cases, a touch-sensitive
display 230 may facilitate user interaction with computing device
200 via the GUI 214 presented by such display 230. Numerous
suitable configurations for display 230 will be apparent in light
of this disclosure.
[0049] In accordance with some embodiments, computing device 200
may include a communication module 240, which may be configured for
wired (e.g., Universal Serial Bus or USB, Ethernet, FireWire, etc.)
and/or wireless (e.g., Wi-Fi, Bluetooth, etc.) communication using
any suitable wired and/or wireless transmission technologies (e.g.,
radio frequency, or RF, transmission; infrared, or IR, light
modulation; etc.), as desired. In accordance with some embodiments,
communication module 240 may be configured to communicate locally
and/or remotely utilizing any of a wide range of wired and/or
wireless communications protocols, including, for example: (1) a
digital multiplexer (DMX) interface protocol; (2) a Wi-Fi protocol;
(3) a Bluetooth protocol; (4) a digital addressable lighting
interface (DALI) protocol; (5) a ZigBee protocol; (6) a near field
communication (NFC) protocol; (7) a local area network (LAN)-based
communication protocol; (8) a cellular-based communication
protocol; (9) an Internet-based communication protocol; (10) a
satellite-based communication protocol; and/or (11) a combination
of any one or more thereof. It should be noted, however, that the
present disclosure is not so limited to only these example
communications protocols, as in a more general sense, and in
accordance with some embodiments, any suitable communications
protocol, wired and/or wireless, standard and/or
custom/proprietary, may be utilized by communication module 240, as
desired for a given target application or end-use. In some
instances, communication module 240 may be configured to
communicate with one or more LCom-enabled luminaires 100 via
network 300. Numerous suitable configurations for communication
module 240 will depend on a given application and will be apparent
in light of this disclosure.
[0050] Also, as can be seen from FIG. 4, computing device 200 may
include one or more image capture devices 250, such as a
front-facing image capture device 252 and/or a rear-facing image
capture device 254, in accordance with some embodiments. For
consistency and ease of understanding of the present disclosure,
front-facing image capture device 252 and rear-facing image capture
device 254 hereinafter may be collectively referred to generally as
an image capture device 250, except where separately referenced. A
given image capture device 250 can be any device configured to
capture digital images, such as a still camera (e.g., a camera
configured to capture still photographs) or a video camera (e.g., a
camera configured to capture moving images comprising a plurality
of frames). In some cases, a given image capture device 250 may
include typical components such as, for instance, an optics
assembly, an image sensor, and/or an image/video encoder, and may
be integrated, in part or in whole, with computing device 200. A
given image capture device 250 can be configured to operate using
light, for example, in the visible spectrum and/or other portions
of the electromagnetic spectrum not limited to the infrared (IR)
spectrum, ultraviolet (UV) spectrum, etc. In some instances, a
given image capture device 250 may be configured to continuously
acquire imaging data. As described herein, a given image capture
device 250 of computing device 200 may be configured, in accordance
with some embodiments, to detect the light and/or LCom signal
output of a transmitting LCom-enabled luminaire 100. In some
instances, a given image capture device 250 may be, for example, a
camera like one typically found in smartphones or other mobile
computing devices. Numerous other suitable configurations for a
given image capture device 250 (e.g., front-facing image capture
device 252; rear-facing image capture device 254) of computing
device 200 will depend on a given application and will be apparent
in light of this disclosure.
[0051] In accordance with some embodiments, computing device 200
may include one or more sensors 260. In some embodiments, computing
device 200 optionally may include a geomagnetic sensor 263. When
included, geomagnetic sensor 263 may be configured as typically
done, and in some example embodiments may be configured to
determine the orientation and/or movement of a host computing
device 200 relative to a geomagnetic pole (e.g., geomagnetic north)
or other desired heading, which may be customized as desired for a
given target application or end-use. In some embodiments, computing
device 200 optionally may include an ambient light sensor 265. When
included, ambient light sensor 265 may be configured as typically
done, and in some example embodiments may be configured to detect
and measure ambient light levels in the surrounding environment of
the host computing device 200. In some embodiments, computing
device 200 optionally may include a gyroscopic sensor 267. When
included, gyroscopic sensor 267 may be configured as typically
done, and in some example embodiments may be configured to
determine the orientation (e.g., roll, pitch, and/or yaw) of the
host computing device 200. In some embodiments, computing device
200 optionally may include an accelerometer 269. When included,
accelerometer 269 may be configured as typically done, and in some
example embodiments may be configured to detect motion of the host
computing device 200. In any case, a given sensor 260 of a given
host computing device 200 may include mechanical and/or solid-state
componentry, as desired for a given target application or end-use.
Also, it should be noted that the present disclosure is not so
limited only to these example optional sensors 260, as additional
and/or different sensors 260 may be provided, as desired for a
given target application or end-use, in accordance with some other
embodiments. Numerous sensor configurations for device 200 will be
apparent in light of this disclosure.
[0052] In accordance with some embodiments, computing device 200
may include or otherwise be communicatively coupled with one or
more controllers 270. A given controller 270 may be configured to
output one or more control signals to control any one or more of
the various components/modules of computing device 200 and may do
so, for example, based on wired and/or wireless input received from
a given local source (e.g., such as on-board memory 210) and/or
remote source (e.g., such as a control interface, optional network
300, etc.). In accordance with some embodiments, a given controller
270 may host one or more control modules and can be programmed or
otherwise configured to output one or more control signals, for
example, to adjust the operation of a given portion of computing
device 200. For example, in some cases, a given controller 270 may
be configured to output a control signal to control operation of a
given image capture device 250, and/or to output a control signal
to control operation of one or more sensors 260. Numerous other
configurations and control signal output for a given controller 270
of computing device 200 will depend on a given application and will
be apparent in light of this disclosure.
[0053] As can be seen further from FIG. 4, computing device 200 may
include an audio output device 280, in accordance with some
embodiments. Audio output device 280 can be, for example, a speaker
or any other device capable of producing sound from an audio data
signal, in accordance with some embodiments. Audio output device
280 can be configured, for example, to reproduce sounds local to
and/or received by its host computing device 200. In some
instances, audio output device 280 may be integrated, in part or in
whole, with computing device 200, whereas in some other instances,
audio output device 280 may be a stand-alone component configured
to communicate with computing device 200 using any suitable wired
and/or wireless communications means, as desired. Numerous other
suitable types and configurations for audio output device 280 will
depend on a given application and will be apparent in light of this
disclosure.
[0054] Network 300 can be any suitable public and/or private
communications network. For instance, in some cases, network 300
may be a private local area network (LAN) operatively coupled to a
wide area network (WAN), such as the Internet. In some cases,
network 300 may include one or more second-generation (2G),
third-generation (3G), and/or fourth-generation (4G) mobile
communication technologies. In some cases, network 300 may include
a wireless local area network (WLAN) (e.g., Wi-Fi wireless data
communication technologies). In some instances, network 300 may
include Bluetooth wireless data communication technologies. In some
cases, network 300 may include supporting infrastructure and/or
functionalities, such as a server and a service provider (e.g.,
computer system 301), but such features are not necessary to carry
out communication via network 300. In some instances, computing
device 200 may be configured for communicative coupling, for
example, with a network 300 and one or more LCom-enabled luminaires
100. In some cases, computing device 200 may be configured to
receive data from network 300, for example, which serves to
supplement LCom data received by computing device 200 from a given
LCom-enabled luminaire 100. In some instances, computing device 200
may be configured to receive data (e.g., such as position, ID, baud
rate, and/or other data pertaining to a given LCom-enabled
luminaire 100) from network 300 that facilitates indoor navigation
via one or more LCom-enabled luminaires 100. In some cases, network
300 may include or otherwise have access to one or more lookup
tables of data that may be accessed by a computing device 200
communicatively coupled therewith, for purposes of determining an
appropriate baud rate, as variously provided herein. Numerous
configurations for network 300 will be apparent in light of this
disclosure.
[0055] As previously noted, there are a number of non-trivial
challenges associated with modulating data over light and
transmitting it into space for LCom. For example, to prevent or
otherwise minimize visual artifacts and other perceivable changes
in light output, it may be desirable to have the LCom light source
transmit at a sufficiently high speed. However, effective detection
of the modulated light by a given receiver device depends on
whether that device has sufficient reception capabilities.
Currently available smartphone cameras typically have a maximum
frame rate of 30 frames/second (FPS) or 60 FPS, providing only very
limited low-speed reception capabilities. As such, there is
currently no known way to effectively utilize existing smartphone
camera hardware in obtaining data modulated over light without
either: (1) making a change in the transmitted light output, which
would be perceivable to the user and any bystanders; or (2) adding
costly, specialized receiver hardware to the receiver device.
[0056] Thus, and in accordance with some embodiments, techniques
are disclosed for coding LCom data in a manner that allows for
detection thereof via an image capture device 250 such as, for
example, a standard low-speed smartphone camera having a frame rate
of 30 FPS. In some cases, the disclosed techniques can be used, for
example, in encoding and decoding LCom data in a manner that: (1)
prevents or otherwise minimizes perceivable flicker of the light
output by a transmitting LCom-enabled luminaire 100; and/or (2)
avoids or otherwise reduces a need for additional, specialized
receiver hardware at computing device 200. In some cases, the
disclosed techniques can be used, for example, to enhance the baud
rate between a transmitting LCom-enabled luminaire 100 and a
receiving computing device 200. For instance, if image capture
device 250 is a typical smartphone front-facing camera configured
to capture images at 30 FPS at VGA resolution (640.times.480
pixels), and if a standard RGB color profile is utilized, then each
frame captured by that image capture device 250 is about 900 KB of
image data (640 pixels.times.480 pixels.times.3 colors). Thus, at a
frame rate of 30 FPS, that image capture device 250 may capture
about 27 MB of raw image data each second, in accordance with an
example embodiment. In other embodiments, the resolution of the
image capture device 250 may be different (e.g., 1334.times.750
pixels, or other standard frame resolutions, including high
definition resolutions).
[0057] FIG. 5A illustrates an example LCom system, including an
LCom-enabled luminaire and a computing device, in accordance with
an embodiment of the present disclosure. As can be seen, this
example scenario includes two luminaires 100 each communicating
with a computing device 200, which happens to be a smartphone
running an LCom-based navigation application. The navigation
application can be, for instance, one of the applications 216
stored in memory 210 and executed by processor(s) 220. As can be
further seen, the LCom signals being communicated include data 500,
which generally includes position information, which may be used to
navigate. For instance, if the user is receiving light from a
specific luminaire 100 that has a known location, then the
navigation application `knows` where the user is and can continue
to guide the user along the targeted path.
[0058] The position information 500 transmitted by the luminaires
100 may come in any number of forms. For instance, in some
embodiments, the luminaire positions may be communicated as a
relative position (e.g., relative to another luminaire 100, or some
other object having a known position), and/or as an absolute
position (e.g., x-y coordinates of a grid-based map). In still
other embodiments, the luminaire positions may be communicated as
an environment ID, wherein the transmitted ID translates to a
specific location on a given map of the environment being
navigated. In some such example cases, for instance, a luminaire
might use dual tone multi frequency (DTMF) encoding, which means it
continuously sends two unique frequencies.
[0059] FIG. 5C shows how an example DTMF-based ID system might
work. As can be seen, a given environment 271 is the area being
navigated and has a number of LCom-enabled luminaires 101. The
environment 271 may be, for example, a super market or retail
store, or a shopping mall, or a parking garage, or a large office
space, to name a few examples. The environment 271 is effectively
divided into a grid of physical locations, each location being
associated with at least one luminaire 100. As can be further seen,
each luminaire 100 is associated with two unique frequencies that
it can transmit on a regular basis. The two unique frequencies can
thus be used to correlate that particular luminaire's location to a
specific location within the environment. For instance, if the user
is receiving light from luminaire #1 (which transmits 697 Hz and
1209 Hz in this example embodiment), then the navigation
application `knows` that the user is in the North-West corner of
the environment 271; similarly, if the user is receiving light from
luminaire #12 (which transmits 941 Hz and 1477 Hz in this example
embodiment), then the navigation application `knows` that the user
is in the South-East corner of the environment; and so on. So, in
one example scenario, assuming that environment 271 is a store
selling goods of some kind, each location can be associated with a
specific product or range of products. Thus, a user can be led to a
given product location by the navigation application, according to
some embodiments. Note that the entire frequency-based grid can be
scaled to higher or lower frequencies and still operate as
described here to uniquely identify the location of individual
luminaires 100.
[0060] FIG. 5B illustrates an example method for emitting position
information from an LCom-enabled luminaire, in accordance with an
embodiment of the present disclosure. As can be seen, the method
includes emitting 501, by at least one solid-state light source of
a luminaire, a light output. The method further includes modulating
503 the light output to emit an LCom signal, the LCom signal
comprising data that includes position information indicating the
physical location of the at least one light source. This position
information may indicate that particular luminaire's location
directly by virtue of relative or absolute position information, or
indirectly by virtue of an environment ID that translates to a
specific location on a given map of the environment being
navigated, as previously explained. Numerous variations on using
luminaires having known locations within a given area to be
navigated will be apparent in light of this disclosure.
[0061] FIG. 5D illustrates an example scenario in which a computing
device 200 receiving LCom signals from luminaries 100 and is
configured to output a navigational instruction by way of visual
feedback to a user, in accordance with an embodiment of the present
disclosure. Note how the actual luminaire 100 in the physical space
being navigated is being imaged by way of camera 252, and the
resulting image of that luminaire 100 is provided on the display
230 of the device 200. Based on receiving LCom signals from that
luminaire 100 (which indicate the position of that luminaire 100),
the navigation application continues to guide the user with a
visual cue (an arrow in this example case). As the user progresses
down the passageway, each subsequent luminaire 100 that is
similarly imaged and processed by the device 200 allows the
navigational guidance to continue, until the user arrives at the
luminaire associated with the user's intended destination.
[0062] FIGS. 6A and 6B show a user holding the computing device 200
in two different orientations. The computing device 200 in this
example is a smartphone, but can be any other suitable computing
device as well. As can be seen, the device 200 includes a
front-facing image capture device 252 that is currently imaging the
above-luminaires 100, and the resulting image is shown on display
230. Two luminaires are being imaged, as can be further seen. In
FIG. 6A, the user is holding the computing device 200 where the
luminaires 100 are perpendicular to the raster lines (and therefore
parallel to the raster direction). For this case, the luminaires
100 being imaged spans the maximum number of raster lines. Assume,
for example, camera frame having 750 raster lines perpendicular to
the raster direction. Thus, a luminaire imaged with the device 200
in that orientation will spans the maximum a relatively large
number of raster lines (e.g., 350 raster lines or more). However,
in the example of FIG. 6B, the luminaires 100 are parallel to the
raster lines (and therefore perpendicular to the raster direction).
Consequently, each imaged luminaire 100 effectively spans only a
fraction of the raster lines, or otherwise fewer raster lines
relative to when the device 200 is in the opposite orientation
shown in FIG. 6A. While in some cases the user can be directed to
orient the device 100 to be more like the orientation shown in FIG.
6A (to improve the ability of device 200 to receive and process
LCom messages from luminaires 100), other embodiments can solve
this rastering problem through a variable baud rate which has the
advantage of not requiring any effort/manual intervention with the
user of the device 200.
[0063] As previously mentioned, there are a multitude of different
computing devices on the market. Ideally, all such devices would be
able to decode the LCom signal. However, this may not be physically
possible given all the variations. For instance, phone `A` might
read raster lines at 1,000 raster lines per 100 ms versus phone `B`
that might read 1,000 raster lines per 10 ms. Therefore, the
effective sampling frequency is 10 kHz and 100 kHz respectively.
With respect to the transmission side, assume a DTMF encoding
scheme for purposes of this example scenario, such that one of the
frequencies is 20 kHz, for instance. According to the Nyquist
frequency rule, Camera `A` sampling at 10 kHz would not be high
enough to decode the transmitting frequency without a lot of
aliasing. To solve this problem, the transmitting LCom-enabled
luminaire can utilize slower frequencies. Likewise, if the
smartphone is rotated where only 20 raster lines cover the
luminaire (shown in FIG. 6B), then the sampling period is greatly
reduced. Thus, there are many reasons why the baud rate of an LCom
transmitter may not be optimal for a given receiver device, such
as: faster or slower sampling rate of camera; poor orientation of
raster lines with respect to luminaire orientation; inability for
camera to resolve multiple high frequency transmissions at the same
time; and a given LCom message is spanning multiple frames where
piecing the multi-frame message back together is difficult and
potentially unreliable.
METHODOLOGY
[0064] FIG. 7 is a flow chart illustrating a method for setting a
baud rate for LCom communication, in accordance with an embodiment
of the present disclosure. The method may be carried out, for
example, by an application executing on the receiving device 200,
such as one the applications 216 stored in memory 210 and
executable by one or more processors 220. In other embodiments,
some parts of the method may be carried out elsewhere, as such as
at the luminaire 100 and/or at a remote computer system 300. In any
such cases, a baud rate can be selected for a given receiving
device 200, and that baud rate can then be used by the luminaire(s)
100 which that device 200 is imaging. A given system might include,
for example, 1,000 luminaires in a store that are all transmitting
their ID's through LCom-based signaling. At any one spot in the
store, a user with a smartphone or other receiver device may only
see one to three luminaires in one camera frame. As the user moves,
the number of luminaires and size varies in each camera frame.
According to an example embodiment of the present disclosure, the
smartphone is configured to set the baud rate of the transmitting
luminaire in such a way that decoding the transmitted ID is
reliable.
[0065] As can be seen, the method includes determining 701 the
various decoding parameters of the mobile computing. The may be
accomplished in various ways. For instance, most operating systems
allow for hardware profiles of its various componentry, including
cameras and other sensors, to be recalled or otherwise queried from
a local storage of the device 200 such that fixed decoding
parameters of that componentry is known. One example would be a
navigation app running on iOS operating system indicating that the
hardware is an iPhone 6 with a 4 MP camera running at a shutter
speed of 1/60 second. Other fixed parameters include frame
resolution and raster line timings such as 1334.times.750 pixels
and 16 overlapping raster lines. For comparison, the Galaxy S5
Android phone has an 8 MP camera running at a shutter speed of 1/30
seconds. In other embodiments, a decoding parameter database can be
populated (offline) with the relevant parameters of currently
available computing devices, and that database can be queried for
decoding parameters associated with a given computing device (based
on make and model). Alternatively, the user of the given device 200
can be queried to manually enter various decoding parameters of
interest (e.g., pixels, shutter speed, frame resolution, number of
overlapping raster lines, and processor speed).
[0066] Once the decoding parameters are in hand, the method
continues with calculating 703 a baud rate suitable for the given
computing device. As will be appreciated, using the receiving
device 200 specifications, an optimal baud can be rate computed so
as to allow the device 200 to receive LCom signals in some desired
percentage of the frame, such as 40% to 50%, or more. In more
detail, assume a receiving device 200 having a 4 MP camera running
at a shutter speed of 1/60 second, as well as a frame resolution
and raster line timings of 1334.times.750 pixels and 16 overlapping
raster lines. Thus, the effective sampling rate can be computed as
follows: 750 raster lines per 1/60 second=45 k raster lines/second.
Now, further assume that it is desired to have 10 raster lines per
bit, which means initially that the baud rate should be 4.5 kHz
(=45 k/10).
[0067] With the baud rate calculated, the method continues with
setting 705 the baud rate at the luminaire. Continuing with the
above example case, setting the baud rate would entail setting the
luminaire baud rate to 4.5 KHz or bps (bits per second). So, for
example, this baud rate can be implemented by the controller 150,
which controls the on-off state of the light sources 110. In the
case of multiple smart devices in the same area, the baud rate can
be set for the lowest common denominator (i.e., the device 200
having the lowest baud rate), according to some embodiments. The
luminaire can then start to transmit LCom signals at that baud
rate. For embodiments where the baud rate determination at 705 is
made external to the luminaire, the method may include, for
example, passing the baud rate to the luminaire through a back
channel such as Bluetooth or WiFi (such as via network 300).
[0068] The method continues with measuring 707 and verifying the
baud rate at the receiving device 200. In some such embodiments,
this can be done by measuring the luminaire length in raster lines.
In more detail, and continuing with the above example where the
LCom message is 32 bits long and there are 10 raster lines per bit,
which means at least 320 raster lines are needed to "see" the
entire message at any one time in a single 750 raster line frame.
Further assume a shutter speed of 1/60 second, thereby providing 45
k raster lines per second. With these parameters in mind, note that
the camera frame data of the computing device 200 can be used to
measure the length of luminaire 100 in units of raster lines. If
the entire luminaire 100 covers more than 320 raster lines within a
given frame, then it follows that the entire LCom message (which
covers 320 raster lines) can be seen as well, within that given
frame. As a corollary, if the entire luminaire 100 covers less than
320 raster lines within a given frame, then it further follows that
the entire LCom message (which needs 320 raster lines) cannot all
be received or "seen" within that single frame.
[0069] For instance, in the example scenario shown in FIG. 8, T
refers to the total number of raster lines making up one camera
frame for device 200 (assume T equals 750 raster lines, in the
example case), and L refers to the length (in raster lines) of the
luminaire 100 being imaged in the camera frame currently displayed
(assume L equals 400 raster lines, in this example case). Thus, the
LCom message being broadcast by the imaged luminaire 100 can be
captured in a single camera frame. However, if the imaged luminaire
100 was less than 320 raster lines, then the LCom message being
broadcast by the imaged luminaire 100 will not be complete for that
baud rate. In this case, therefore, the baud rate could be
increased which sacrifices resolution to obtain the entire message
or ID spread out over the luminaire. Thus, for instance, the 10
raster lines per bit can be changed to 5 raster lines per bit,
thereby doubling the baud rate from 4.5 Kbits/sec to 9 Kbits/sec.
FIG. 9 shows a visual of different baud rates, including a
relatively fast baud rate showing four messages within a given time
period, and a relatively slow baud rate showing two messages within
that same given time period. Thus, the fast baud rate is twice as
fast as the slow baud rate. Because the faster baud rate is more
compressed in time, it can be imaged with fewer raster lines.
[0070] The method continues with adjusting 709 the receiving device
parameters, if needed. In the case where the luminaire is either
controlled by some other device or the baud rate is not settable,
then the receiving device itself can try to adapt by changing its
own timing with respect to, for example, shutter speed and/or frame
rate. To find the present baud rate, the receiver can observe the
bit rate period and message length. Note that in this case, the
back channel is not needed to pass along the baud rate to the
luminaire. In some embodiments, note that the receiving device can
request changes in baud rate based on ambient conditions. For
example, if a given receiving device includes a camera and a light
sensor, then ambient light conditions can be sensed and this
information can be fed back to the luminaire to adjust baud rate to
improve signal to noise ratio. For instance, in cases of high
ambient light, the optimal baud rate might be smaller to keep the
desired signal to noise ratio. However, the ambient light might be
a different waveform (and wavelength) such as IR. Thus, the
amplitude and wavelength of ambient light can be measured to assess
same.
[0071] The method continues with determining at 711 whether or not
the ID being transmitted by the luminaire is decodable at the given
baud rate. If not, then the process can repeat back to 703 in
effort to determine a better baud rate. On the other hand, if the
ID being transmitted by the luminaire is decodable at the given
baud rate, then the method continues with decoding 713 LCom
packets.
[0072] The method may further include monitoring 715 for changes of
luminaire in frame. For instance, in some embodiments, the
appearance of the luminaires in the camera frame can be monitored,
and the baud rate can be adjusted based on this information. In one
such embodiment, the receiving device 200 periodically (e.g., every
3-30 frames) recalculates the optimal baud rate based on the
visualization of the luminaires 100 in the camera frame. In some
cases, the receiving device 200 can optionally try to adjust its
own settings to optimize decoding or deal with situations where
luminaire control is not available for whatever reason. In still
other scenarios, there may be a case where the needed baud rate is
too fast for the luminaire. One such example of this is the case
where the luminaire fills up only a small portion of the screen.
For a linear light, this might just mean that the user should
rotate the receiving device 200 to better align the raster lines
perpendicular to the long dimension of the luminaire, as shown in
FIG. 6A, for instance. In such cases, the user could be, for
instance, prompted to rotate the receiving device accordingly. In
still other example embodiments, if the needed baud rate is not
available, then the user may be alerted (e.g., generate and send
alert message to display screen of receiving device 200).
[0073] Thus, after iterating through the methodology as needed, the
baud rate can be set for reliable decoding regardless of any
initial mismatch of the transmitting luminaire 100 and receiving
device 200. As will be appreciated, the methodology allows for both
adjusting the baud rate at the transmitter side, and further allows
the effective baud rate to be changed using internal adjustments of
the receiving device 200. These internal adjustments may include
changes to parameters such as camera shutter speed, camera
resolution, camera frame rate, camera shutter mode, and signal gain
(ISO), to name a few examples. For instance, a camera of a given
receiver device 200 that is imaging the ceiling in video mode might
use a low ISO, fixed frame rate/shutter speed, and video resolution
initially. If possible, the device 200 can be switched (manually by
user or automatically by LCom-based navigation application 216)
from video mode to camera mode to utilize slower shutter speeds
than 1/30 seconds. This effectively increases the baud rate as now
the sampling rate is slower. To compensate for the increased light
with the slower shutter speed, the ISO can decrease. This example
highlights two types of camera parameters that include: direct
timing parameters, and light compensation parameters that do not
directly affect timing but compensate for timing parameters for
proper brightness. Timing parameters include: shutter speed, frame
rate, resolution, and shutter mode. The compensation parameters
include: ISO, aperture, and filters. Depending on the camera
composition constraints and LCom-based application 216
requirements, the timing parameters can be adjusted to effectively
change the baud rate from the point of view of the receiving device
200 while the compensation parameters adjust the light level back
to optimal signal levels. Thus, adjustments to baud rate to not
impact the clarity of the imagery.
[0074] Numerous embodiments will be apparent in light of this
disclosure. One example embodiment provides a method for setting a
baud rate for light-based communication (LCom). The method
includes: determining decoding parameters of a receiving device,
the receiving device including a camera for receiving LCom signals,
and a display; calculating a baud rate suitable for the receiving
device based on the decoding parameters; and causing the baud rate
to be set at an LCom-enabled luminaire. In some cases, the method
is carried out at least in part on the receiving device. In some
cases, the receiving device being a mobile computing device. In one
such case, the receiving device is a smartphone or tablet computer.
In some cases, the decoding parameters include at least one of
shutter speed of the camera, frame resolution of the camera, and
orientation of the luminaire with respect to a raster direction of
the camera. In some cases, determining decoding parameters of a
receiving device includes at least one of: querying a database of
known receiving devices to identify relevant decoding parameters;
and accessing a local storage of the receiving device to identify
relevant decoding parameters. In some cases, causing the baud rate
to be set at an LCom-enabled luminaire comprises passing the baud
rate to the luminaire via a radio frequency wireless communication
channel. In some cases, the method further includes measuring and
verifying the baud rate at the receiving device. In some cases, the
method further includes adjusting the decoding parameters of the
receiving device if baud rate cannot be adjusted to meet a current
configuration of decoding parameters. In some cases, the method
further includes: determining whether or not an ID being
transmitted by the luminaire is decodable at the baud rate; and in
response to the ID being decodable at the given baud rate,
continuing to decode LCom signals at the baud rate; and in response
to the ID not being decodable at the given baud rate, calculating a
different baud rate. In some cases, the method further includes:
monitoring for changes of luminaire in frame; and prompting a user
to rotate the receiving device to improve orientation of the
luminaire with respect to a raster direction of the camera. Another
embodiment provides a non-transitory computer readable medium
encoded with instructions that, when executed by one or more
processors, causes a process for setting a baud rate for
light-based communication (LCom) to be carried out, the process
including the methodology as variously described in this paragraph.
The non-transitory computer readable medium may include, for
example, one or more machine readable mediums, such as a hard disk,
ROM, solid state drive, thumb drive, embedded controller memory,
compact disc, server computer, or other such non-transitory mediums
that can be accessed by one or more processors so that the
instructions thereon can be executed to carry out the process. Note
that the process so encoded on the computer readable medium need
not be carried out, and may remain unexecuted in some such
embodiments.
[0075] The foregoing description of example embodiments has been
presented for the purposes of illustration and description. It is
not intended to be exhaustive or to limit the present disclosure to
the precise forms disclosed. Many modifications and variations are
possible in light of this disclosure. It is intended that the scope
of the present disclosure be limited not by this detailed
description, but rather by the claims appended hereto. Future-filed
applications claiming priority to this application may claim the
disclosed subject matter in a different manner and generally may
include any set of one or more limitations as variously disclosed
or otherwise demonstrated herein.
* * * * *