阅读说明：本技术 照明装置的到达角度调试 (Angle of arrival commissioning of lighting devices ) 是由 J·卡瓦库蒂 池原正成 于 2021-01-08 设计创作，主要内容包括：一种用于调试光源的技术可以包括：接收指示光源的计划地理位置的数据以及表示光源的调试信息的数据；接收指示到达角度接收器的相对于光源的计划地理位置的实际地理位置的数据；在所述到达角度接收器处接收携载唯一地标识相应光源的相应光源标识符的信标信号；基于a)所述到达角度接收器的相对于光源的计划地理位置的实际地理位置以及b)所述信标信号的相应到达角度来计算光源的实际地理位置；将所述计划地理位置与所述实际地理位置进行比较,以使所述调试信息与所述光源标识符相关；以及将被相关的光源标识符和调试信息发送到相应光源。(A technique for commissioning a light source may include: receiving data indicative of a planned geographical position of a light source and data representing commissioning information of the light source; receiving data indicative of an actual geographical position of the angle-of-arrival receiver relative to a planned geographical position of the light source; receiving, at the angle-of-arrival receiver, beacon signals carrying respective light source identifiers that uniquely identify respective light sources; calculating an actual geographical position of the light source based on a) an actual geographical position of the angle of arrival receiver relative to a planned geographical position of the light source and b) a corresponding angle of arrival of the beacon signal; comparing the planned geographic location to the actual geographic location to correlate the commissioning information with the light source identifier; and sending the correlated light source identifier and commissioning information to the respective light source.)

1. A method for commissioning a light source, comprising:

receiving data indicative of planned geographical positions of a plurality of light sources comprising planned geographical positions of the light sources and data representing commissioning information of the plurality of light sources comprising commissioning information of the light sources;

receiving data indicative of an actual geographical position of the angle-of-arrival receiver relative to a planned geographical position of the plurality of light sources;

transmitting outgoing beacon signals, each outgoing beacon signal including a stored light source identifier that uniquely identifies the light source;

receiving, at the angle-of-arrival receiver, a beacon signal comprising the outgoing beacon signal, the beacon signal carrying a respective light source identifier that uniquely identifies a respective light source, the outgoing beacon signal carrying the stored light source identifier;

calculating actual geographical positions of a plurality of light sources comprising calculated geographical positions of the light sources based on a) actual geographical positions of the angle of arrival receiver relative to planned geographical positions of the plurality of light sources and b) respective angles of arrival of the beacon signals;

comparing the planned geographic location to the actual geographic location to correlate the commissioning information with the light source identifier; and

the correlated light source identifier and commissioning information is sent to the respective light source.

2. The method of claim 1, wherein the commissioning information is predefined and stored, the sending the correlated light source identifier and commissioning information to the respective light source comprising accessing the commissioning information from a local memory or from communication with a remote storage device.

3. The method of claim 1, receiving data indicative of an actual geographic location of the angle of arrival receiver relative to a planned geographic location of a plurality of light sources comprises providing a user interface configured to: a lighting plan map comprising planned geographical locations of a plurality of light sources is displayed, and a user input indicating an actual geographical location of the angle of arrival receiver relative to the planned geographical locations of the plurality of light sources on the lighting plan map is received.

4. A method for commissioning a plurality of light sources, comprising:

receiving data indicative of planned geographical locations of a plurality of light sources and data representing commissioning information of the plurality of light sources;

receiving data indicative of an actual geographical position of the angle-of-arrival receiver relative to a planned geographical position of the plurality of light sources;

receiving, at the angle-of-arrival receiver, beacon signals carrying respective light source identifiers that uniquely identify respective light sources;

calculating actual geographical positions of a plurality of light sources based on a) actual geographical positions of the angle-of-arrival receiver relative to planned geographical positions of the plurality of light sources and b) respective angles of arrival of the beacon signals;

comparing the planned geographic location to the actual geographic location to correlate the commissioning information with the light source identifier; and

the correlated light source identifier and commissioning information is transmitted.

5. The method of claim 4, wherein the commissioning information is predefined and stored, the sending the correlated light source identifier and commissioning information to the respective light source comprising accessing the commissioning information from a local memory or from communication with a remote storage device.

6. The method of claim 4, receiving data indicative of an actual geographic location of the angle of arrival receiver relative to a planned geographic location of a plurality of light sources comprises providing a user interface configured to: a lighting plan map comprising planned geographical locations of a plurality of light sources is displayed, and a user input indicating an actual geographical location of the angle of arrival receiver relative to the planned geographical locations of the plurality of light sources on the lighting plan map is received.

7. A system for commissioning a light source, comprising:

an angle-of-arrival receiver configured to receive a beacon signal;

a processor operably connected to the angle of arrival receiver, the processor configured to receive:

data indicative of planned geographical positions of a plurality of light sources including the planned geographical position of the light source,

data representing commissioning information of a plurality of light sources comprising commissioning information of said light sources, an

Data indicative of an actual geographic position of the angle of arrival receiver relative to a planned geographic position of a plurality of light sources;

a lighting apparatus comprising a first transmitter configured to transmit outgoing beacon signals, each outgoing beacon signal comprising a stored light source identifier that uniquely identifies a light source,

wherein the angle-of-arrival receiver is configured to receive a beacon signal comprising the outgoing beacon signal, the beacon signal carrying a respective light source identifier uniquely identifying a respective light source, the outgoing beacon signal carrying the stored light source identifier;

a processor operably connected to the receiver and the angle-of-arrival receiver, the processor configured to calculate actual geographic positions of a plurality of light sources including calculated geographic positions of the light sources based on a) actual geographic positions of the angle-of-arrival receiver relative to planned geographic positions of the plurality of light sources and b) respective angles of arrival of the beacon signals, the processor further configured to compare the planned geographic positions to the actual geographic positions to correlate the commissioning information with the light source identifiers; and

a second transmitter operably connected to the processor and configured to transmit the correlated light source identifier and commissioning information to the respective light source.

8. The system according to claim 7, wherein the first transmitter comprises a Bluetooth (R) low energy mesh (BLE) mesh device, wherein Bluetooth is a registered trademark.

9. The system of claim 7, wherein the debug information is predefined and stored, the second transmitter accessing the debug information from a local memory or from communication with a remote storage device.

10. The system of claim 7, comprising:

a user interface configured to display a lighting plan map comprising planned geographical locations of a plurality of light sources and to receive a user input indicating an actual geographical location of the angle of arrival receiver relative to the planned geographical locations of the plurality of light sources on the lighting plan map.

11. The system according to claim 7, wherein the second transmitter comprises a Bluetooth (R) low energy mesh (BLE) mesh device, wherein Bluetooth is a registered trademark.

12. A system for commissioning a light source, comprising:

an angle-of-arrival receiver configured to receive a beacon signal;

a processor operably connected to the angle of arrival receiver, the processor configured to receive:

data indicative of planned geographical positions of a plurality of light sources including the planned geographical position of the light source,

data representing commissioning information of a plurality of light sources comprising commissioning information of said light sources, an

Data indicative of an actual geographical position of the angle of arrival receiver relative to a planned geographical position of a plurality of light sources,

wherein the angle-of-arrival receiver is configured to receive beacon signals carrying respective light source identifiers uniquely identifying respective light sources, the beacon signals comprising outgoing beacon signals transmitted by the light sources, each outgoing beacon signal carrying a stored light source identifier uniquely identifying a light source;

a processor operably connected to the receiver and the angle-of-arrival receiver, the processor configured to calculate actual geographic positions of a plurality of light sources including calculated geographic positions of the light sources based on a) actual geographic positions of the angle-of-arrival receiver relative to planned geographic positions of the plurality of light sources and b) respective angles of arrival of the beacon signals, the processor further configured to compare the planned geographic positions to the actual geographic positions to correlate the commissioning information with the light source identifiers; and

a transmitter operably connected to the processor and configured to transmit the correlated light source identifier and commissioning information to a respective light source comprising the light source.

13. The system of claim 12, wherein the angle of arrival receiver is equipped with a Bluetooth Direction Finding (BDF).

14. The system of claim 12, wherein the debug information is predefined and stored, the second transmitter accessing the debug information from a local memory or from communication with a remote storage device.

15. The system of claim 12, comprising:

a user interface configured to display a lighting plan map comprising planned geographical locations of a plurality of light sources and to receive a user input indicating an actual geographical location of the angle of arrival receiver relative to the planned geographical locations of the plurality of light sources on the lighting plan map.

16. An apparatus for commissioning a plurality of light sources, comprising:

a processor configured to communicate with the angle of arrival receiver and configured to receive:

data indicative of planned geographical positions of a plurality of light sources including the planned geographical position of the light source,

data representing commissioning information of a plurality of light sources comprising commissioning information of said light sources, an

Data indicative of an actual geographic position of the angle-of-arrival receiver relative to a planned geographic position of a plurality of light sources, the angle-of-arrival receiver configured to receive beacon signals carrying respective light source identifiers that uniquely identify respective light sources;

the processor is configured to calculate actual geographical positions of a plurality of light sources based on a) actual geographical positions of the angle of arrival receiver relative to planned geographical positions of the plurality of light sources and b) respective angles of arrival of the beacon signals, and the processor is further configured to compare the planned geographical positions with the actual geographical positions to correlate the commissioning information with the light source identifiers.

17. The apparatus of claim 16, comprising:

a transmitter operably connected to the processor and configured to transmit the correlated light source identifier and commissioning information to the respective light source.

18. The apparatus of claim 16, comprising:

a user interface configured to display a lighting plan map comprising planned geographical locations of a plurality of light sources and to receive a user input indicating an actual geographical location of the angle of arrival receiver relative to the planned geographical locations of the plurality of light sources on the lighting plan map.

19. A computer-readable medium having instructions stored thereon that, when executed, perform a method comprising:

receiving data indicative of planned geographical locations of a plurality of light sources and data representing commissioning information of the plurality of light sources;

receiving data indicative of an actual geographical position of the angle-of-arrival receiver relative to a planned geographical position of the plurality of light sources;

calculating actual geographical positions of a plurality of light sources based on a) actual geographical positions of the angle of arrival receiver relative to planned geographical positions of the plurality of light sources and b) respective angles of arrival of beacon signals transmitted by the plurality of light sources;

comparing the planned geographic location to the actual geographic location to correlate the commissioning information with the light source identifier; and

the correlated light source identifier and commissioning information is sent to the respective light source.

20. The computer-readable medium of claim 19, the method comprising:

a lighting plan map comprising planned geographical locations of a plurality of light sources is displayed, and a user input indicating an actual geographical location of the angle of arrival receiver relative to the planned geographical locations of the plurality of light sources on the lighting plan map is received.

Background

Commissioning is a quality assurance process used to ensure that installed building systems are interactively and continuously conducted according to the needs and design intent of the owner. Debugging answer questions "do the building and its system proceed according to the needs of the owner and the designer's intentions? "therefore, the debugging process begins with identifying the owner's project requirements and ends with ensuring that the design intent, the finished design, and the installed system meet these requirements. Benefits of commissioning include reduced energy and operating costs, improved property value and marketability, verification that buildings and their systems are performing as expected, and greater user acceptance and satisfaction.

The guidelines 0-2005 of The american society of heating, refrigeration and air conditioning engineers (ASHRAE), "The commission Process" defines The Process of Commissioning an entire building. In 2011, The Lighting engineering society (IES) has formulated a design guide 29, "The communication Process Applied to Lighting and Control Systems," as a Lighting-specific guide for "The communication Process" described in guide 0.

In the lighting industry, the term "commissioning" is typically applied to lighting control system enablement or initial setup, where a representative of the manufacturer sets and calibrates installed controls as services. Commissioning can be applied to the entire building and its energy usage system, including lighting and control. System enablement and functional testing are steps in a larger process to ensure that all installed systems meet the design intent and owner requirements.

In the example of a large building, warehouse, or retail store, the commissioning process may include assigning individual lighting devices, including light sources, to lighting groups to control or monitor the devices differently according to their assigned lighting groups.

Traditionally, the debugging process is time consuming in terms of manual time and, therefore, is slow, expensive and error prone.

Disclosure of Invention

Techniques are disclosed for determining the actual position of a lighting device using angle-of-arrival techniques, correlating the actual position with a planned position to identify the device, and then sending commissioning information to the identified device.

These novel techniques enable rapid commissioning of light sources, particularly as compared to other processes. Using the techniques disclosed herein, the time required to commission a relatively large commercial or industrial setting (which may include hundreds or thousands of light sources) can be significantly reduced over days or even weeks required for other processes. The novel process is also highly automated and therefore less prone to error. This may mean significant time and cost savings.

These and other advantages of the invention will become apparent when viewed in light of the attached drawings, examples and detailed description.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate various exemplary systems and methods, etc., that show various exemplary embodiments of aspects of the invention. It will be appreciated that the element boundaries (e.g., boxes, groups of boxes, or other shapes) shown in the figures represent one example of boundaries. One of ordinary skill in the art will appreciate that one element may be designed as multiple elements or that multiple elements may be designed as one element. An element shown as an internal component of another element may be implemented as an external component and vice versa. In addition, elements may not be drawn to scale.

Fig. 1 shows a schematic diagram of an exemplary space that may correspond to a warehouse or a large retail space having light sources.

FIG. 2 shows a schematic diagram of an exemplary debugging process.

Fig. 3A shows a schematic diagram of an exemplary lighting fixture commissioning system.

Fig. 3B shows a schematic diagram of an exemplary lighting fixture commissioning system.

Fig. 4A shows a block diagram of an exemplary light source or illumination device.

Fig. 4B illustrates a block diagram of an exemplary computing device and angle of arrival receiver.

Fig. 5 shows a flow diagram of an exemplary method for commissioning a light source.

Detailed Description

Fig. 1 shows a schematic diagram of an exemplary space 100 that may correspond to a warehouse or a large retail space. The space 100 employs a plurality of light sources 101 (e.g., luminaires, etc.) to provide illumination. However, different areas within the space 100 may have different lighting requirements. Thus, the light sources 101 may be divided into lighting groups. Fig. 1 shows three lighting groups: group 1, group 2 and group 3. The light sources in a group may be controlled differently from the light sources in another group. For example, light source 101a in group 1 may be controlled to have a different light intensity than the intensity of light source 101b in group 2. In another example, light sources 101a in group 1 may be controlled to have a different light color temperature than light sources 101c in group 3. In yet another example, light source 101b in group 2 may be controlled to remain on at all times, while light source 101c in group 3 may be turned on and off based on the time of day.

The commissioning process may include assigning individual light sources 101 to their respective groups. During initial setup (prior to regular use), a representative of the manufacturer or other technician may set or program commissioning information into the light sources 101 (including, for example, the respective lighting groups).

FIG. 2 shows a schematic diagram of an exemplary debugging process. At step 1, a representative of the manufacturer or other technician (user 102) may take a computing device 103 (such as a tablet computer or smartphone) around in the space 100.

The light sources 101 (or their control devices) may each be capable of establishing a network with the computing device 103 using known wireless technology standards or protocols (e.g., Bluetooth (registered trademark), Wi-Fi (registered trademark), etc.). Each light source 101 (or its control device) may constantly send advertising data payloads to make the computing device 103 aware that the light source is present (e.g., a General Access Profile (GAP)). In step 2, the computing device 103 may display a list of detected light sources 101.

In step 3, the user 102 may select a light source 101 to debug from the light sources listed by the computing device 103. At step 4, upon selection by the user 102, a network may be formed between the computing device 103 and the selected light source 101 or its control device using known wireless technology standards or protocols, such as generic attribute profile (GATT). The network key may be necessary to establish the network connection. The connected light source 101 may blink to confirm the network connection.

Once the network has been established, the debugging information may be sent by the computing device 103 via the network. The commissioning information may be pre-programmed for the computing device 103 to send to the light source 101 or its control device. At step 5, the user 102 may use the computing device 103 to adjust or fine tune the settings of the light sources 101 currently networked with the mobile device. Once the light source 101 has been commissioned, the user 102 may disconnect the computing device 103 from the formed network and repeat the process for each other light source in the space 100.

The process of fig. 2 is time consuming. In some cases, commissioning of a single light source may take up to two minutes. Commissioning a relatively large commercial or industrial setting (which may include hundreds or thousands of light sources) using this process may take days or even weeks. This process also depends significantly on the ability of the technician, which can make debugging inconsistent and error prone. This can be expensive.

Fig. 3A and 3B show schematic diagrams of a debugging system. The system may include one or more lighting devices or light sources 101 a-b capable of storing identification and commissioning information and capable of communicating (receiving and transmitting) wireless signals including beacon signals 107 a-b. For purposes of simplifying the description, the present invention refers to device 101 as a light source. However, device 101 may generally include lighting devices (such as luminaires, dimmers, sensors, controllers, etc.) that may require commissioning. The light sources 101 a-b may store identification and commissioning information and may communicate (receive and transmit) the signals 107 a-b themselves, or the light sources 101 a-b may be connected to or have stored within them control means capable of storing identification and commissioning information and communicating (receive and transmit) the signals 107 a-b.

Beacon signals are low energy signals that a transmitting device can broadcast (usually continuously and indiscriminately) and that a receiving device (such as a computer, smart phone, etc.) can scan for and receive. Examples of the beacon signal include iBeacon (registered trademark), Eddystone (registered trademark), Bluetooth (registered trademark) low energy (BLE) signal, and the like. A common feature of beacon signals is that they contain a unique ID number. In some embodiments, the techniques disclosed herein use a unique ID number as the light source identifier. However, in other embodiments, the light source identifier may be part of the beacon signal or part of a packet other than the unique ID number. In some embodiments, the light source identifier may be a MAC address.

The system may also include a computing device 103 (e.g., a laptop, a smartphone, a tablet, etc.), the computing device 103 having a debugging program or application installed thereon, or may have access to debugging information and be capable of communicating (receiving and sending) wireless signals. The computing device 103 may also be able to communicate over a network (e.g., the internet) with a remote storage device that may already have debugging information stored therein. Via the network, device 103 may receive debug information from a remote storage device.

The commissioning information may include the planned position of the light source 101 in 3D, including a horizontal position (as shown in fig. 1) and a vertical position (e.g., height relative to the floor). The commissioning information may also include information such as lighting groups, timing of operation, dimming details, intensity, color temperature, etc.

The system may also include an angle of arrival (AoA) array or receiver 106 connected to the computing device 103. For purposes of illustration, the AoA receiver 106 is shown in fig. 3 as being separate from the computing device 103 and connected by a cable 108. However, in some embodiments, the AoA receiver 106 may be internal to the computing device 103 or part of the computing device 103. The AoA receiver 106 may be used to measure the angles of arrival alpha and beta of the beacon signals 107 a-b, respectively. The measurement of the angle of arrival may be done by determining the direction of propagation of the radio frequency wave of the signal 107 incident on the AoA receiver 106 antenna array. In one embodiment, the AoA device 106 is equipped with Bluetooth Direction Finding (BDF) AoA technology (a main feature of Bluetooth (registered trademark) 5.1 core specification). The BDF may be used to detect the location of the beacon signal transmitting device in 2D or 3D.

As best seen in fig. 3B, the computing device 103 may be used to display the space 1 and the planned position of the light source 101 in the space 1. The user may move a symbol 114 (which symbolizes the AoA receiver 106, including arrows indicating relative orientations) to a horizontal position and orientation on the screen of the computing device 103 that corresponds to the actual horizontal position and orientation of the AoA receiver 106 using a graphical user interface of the computing device 103 (e.g., using the cursor 110). The user may also enter the vertical position (i.e., height) of the AoA receiver 106. In the example shown, the AoA receiver 106 shown in fig. 3A is placed on a table 116. The user may input the height of the upper surface of the table 116 on which the AoA receiver 106 is placed as a vertical position in column 118 of fig. 3B. The user may also rotate the symbol 114 so that its arrow 114a may align with a corresponding arrow 106a (or similar orientation indicator) on the AoA receiver 106.

In summary, if the planned position (including the horizontal (as shown in fig. 1) and vertical position) of the light source 101a, and the position (including the horizontal and vertical position) and orientation of the AoA receiver 106 relative to the planned position of the light source 101a, are known, the measured angle of arrival of the beacon signal 107a can be used to determine the actual position of the corresponding light source 101 a. Then, the planned position of the light source 101a may be correlated with the actual position of the light source 101a to identify the installed light source 101a as corresponding to the planned light source 101 a.

Upon identifying the light source 101a, the computing device 103 (or other device) may send an incoming signal 109 carrying corresponding commissioning information for the light source 101 a. The same process may be repeated for light source 101b and all other light sources 101 within range of the AoA receiver 106. For light sources 101 that are not within range of the AoA receiver 106, the arrangement of fig. 3A may need to be moved along the space 1 to bring other light sources 101 within range of the AoA receiver 106. The range of the system is limited by the energy of the signal comprising the beacon signal 107.

The process of fig. 3A and 3B may be used to accomplish relatively fast and accurate debugging as compared to the process of fig. 2. The time required to commission a relatively large commercial or industrial setting (which may include hundreds or thousands of light sources) using the process of fig. 3A and 3B can be significantly reduced from the days or even weeks required for the process of fig. 2. Most of the processing of fig. 2 is spent on walking in the space 1 and establishing separate, one at a time, network connections with the light sources 101. The process of fig. 3A and 3B reduces the need for a technician to walk in space 1. Furthermore, since the computing device 103 is primarily responsible for the identification and transmission of debug information, errors will be significantly reduced. This may mean significant time and cost savings.

In one embodiment, prior to installing the light source 101, default commissioning information including default values for lighting groups (e.g., group 1) may be assigned to the light source 101, possibly during manufacturing, for example by storing the information in a memory. Assuming that most lighting installations will have group 1, storing default commissioning information including group 1 as the default value for the lighting group may help save additional commissioning time. In one embodiment, a light source identifier that uniquely identifies the light source may also be stored in memory during the same pre-installation process.

Fig. 4A shows a block diagram of an exemplary light source or illumination device 101. Lighting device 101 may include an AC electrical connection 121 to connect to an external power source. In this example, the lighting device 101 is an LED light source and thus includes an LED 122. The lighting device 101 may also include an AC/DC converter 123 to convert AC to DC, a modulator 125 to turn the LEDs on and off as needed to change, for example, intensity, color temperature, etc. The lighting device 101 may also include a controller 127, the controller 127 controlling the operation of the lighting device 101, including controlling the modulator 125.

Lighting device 101 may also include a memory 129 that stores commissioning information including, for example, values assigned to lighting groups of lighting device 101 and a stored light source identifier that uniquely identifies lighting device 101. The lighting device 101 may further comprise a receiver 130 and a transmitter 131 for receiving and transmitting signals, respectively.

Transmitter 131 may transmit an outgoing beacon signal. Each outgoing beacon signal may include a stored light source identifier that uniquely identifies the lighting device 101. The receiver 130 may receive an incoming wireless signal carrying debug information.

Although the controller 127 is shown in fig. 4A as controlling both the lighting and communication functions of the lighting device 101, in some embodiments, the lighting device 101 may include two or more controllers that may be used to control these and other functions. For example, a first controller may be used to control lighting functions, while a second controller may be used to control communications. The controller 127, receiver 130, and transmitter 131 may be implemented in any combination of hardware and software, and may include a processor. The processor may be a variety of different processors including dual microprocessors and other multiprocessor architectures.

Memory 129 may include volatile memory or non-volatile memory. Non-volatile memory may include, but is not limited to, ROM, PROM, EPROM, EEPROM, and the like. Volatile memory may include, for example, RAM, Synchronous RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), and direct RAM bus RAM (DRRAM).

Although in fig. 4A, the receiver 130 and the transmitter 131 are shown separate from each other, in some embodiments, the receiver 130 and the transmitter 131 may be implemented as one transceiver interface that allows the lighting devices 101 to communicate. The receiver 130 and the sender 131 may interact with a Local Area Network (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN), and other networks. The receiver 130 and the transmitter 131 may include and interact with communication technologies including, but not limited to, Fiber Distributed Data Interface (FDDI), Copper Distributed Data Interface (CDDI), ethernet (IEEE 802.3), token ring (IEEE 802.5), wireless computer communication (IEEE 802.11), Bluetooth (registered trademark) (IEEE 802.15.1), Zigbee (registered trademark) (IEEE 802.15.4), iBeacon (registered trademark), and Eddystone (registered trademark), among others.

Fig. 4B shows a block diagram of an exemplary computing device 103 and an exemplary AoA receiver 106. Although in fig. 4B, the AoA receiver 106 is shown external to the computing device 103, in some embodiments, the AoA receiver 106 may be part of the computing device 103.

The computing device 103 may include a processor 113, memory 117, and a network adapter 119 to send and receive information. The computing device 103 may also include receiving logic 115 that works with the network adapter 119 to receive data from received beacon signals carrying individual light source identifiers that uniquely identify individual lighting devices 101. The computing device 103 may also include display logic 111 to display a mapping of the lighting devices 101 as planned (e.g., in space 1), and user selection logic 112 to detect a user selection of a horizontal position and a user indication of a vertical position of the AoA receiver 106.

The processor 113 may calculate the actual geographical position of the light source 101 based on the planned position of the light source 101, the actual geographical position/orientation of the AoA receiver 106 and the measured angle of arrival of the beacon signal 107. The processor 113 may also correlate the planned position of the light source 101 (and corresponding commissioning information) with the actual position of the light source 101 to identify the installed light source 101 as corresponding to the planned light source 101.

The computing device 103 may also include transmit logic 105 that works with the network adapter 119 to transmit corresponding commissioning information to the light source 101.

The receiving logic 115, sending logic 105, display logic 111, and selection logic 112 may be implemented in any combination of hardware and software. These logics may be stored in the memory 117 and executed by the processor 113. These logics may be part of an application running on the computing device 103.

The processor 113 may be a general purpose CPU found in modern computing devices. The CPU 113 processes the received information and sends the relevant information to the network adapter 119. In addition, the CPU 113 reads information and writes the information to the memory 117. The CPU 113 may use any standard computer architecture. The general architecture of the microcontroller device includes ARM and x 86.

The network adapter 119 is a network interface that allows the computing device 103, as well as the receive logic 115 and transmit logic 105, to connect to cellular networks, Wi-Fi (registered trademark), Bluetooth (registered trademark), and other networks. The computing device 103 may access the debugging information from a remote source (e.g., a remote server) using the network adapter 119. However, by storing the data locally to memory 117 of mobile device 103, the obtaining of this information may be accomplished without a data connection. However, the network adapter 119 allows for greater flexibility and reduces the resources required locally to the computing device 103.

Although shown as separate from each other in fig. 4B, receive logic 115 and transmit logic 105 may, in some embodiments, be implemented as a transceiver interface that allows computing device 103 to communicate. The receiving logic 115 and the sending logic 105 may interact with a Local Area Network (LAN), Wide Area Network (WAN), Personal Area Network (PAN), cellular data network (Edge, 3G, 4G, LTS, CDMA, GSM, LTE, etc.), and other networks via the network adapter 119. The receiver 130 and the transmitter 131 may include and interact with communication technologies including, but not limited to, Fiber Distributed Data Interface (FDDI), Copper Distributed Data Interface (CDDI), ethernet (IEEE 802.3), token ring (IEEE 802.5), wireless computer communication (IEEE 802.11), Bluetooth (registered trademark) (IEEE 802.15.1), Zigbee (registered trademark) (IEEE 802.15.4), iBeacon (registered trademark), and Eddystone (registered trademark), among others.

The AoA receiver 106 may include an antenna array, and may be equipped with Bluetooth Direction Finding (BDF) AoA technology (a main feature of Bluetooth (registered trademark) 5.1 core specification). The BDF may be used to detect the location of the beacon signal transmitting device in 2D or 3D. Nordic (registered trademark) semiconductor nRF5XXXx series of system-on-chip integrated circuits are examples of solutions that may be used to implement the AoA receiver 106.

The exemplary method may be better understood with reference to the flowchart of fig. 5. While, for purposes of simplicity of explanation, the methodologies shown are shown and described as a series of blocks, it is to be understood and appreciated that the methodologies are not limited by the order of the blocks, as some blocks may occur in different orders or concurrently with other blocks from what is shown and described. Moreover, less than all illustrated blocks may be required to implement an example method. Moreover, additional methods, alternative methods, or both may employ additional blocks (not shown).

In the flow diagrams, the blocks represent process blocks that may be implemented in logic. The processing blocks may represent method steps or apparatus elements for performing the method steps. The flow diagrams do not depict the syntax of any particular programming language, method, or style (e.g., procedural, object oriented). Rather, the flow diagrams illustrate functional information one of ordinary skill in the art can use to develop logic to perform the illustrated processing. It will be appreciated that in some examples, programming elements such as temporary variables and routine loops are not shown. It will be further appreciated that electronic and software applications may involve dynamic and flexible processes such that the illustrated blocks may be performed in other sequences different than those illustrated, or that the blocks may be combined or separated into multiple components. It is to be appreciated that the processes can be implemented using various programming approaches such as machine language, procedural, object oriented or artificial intelligence techniques.

Fig. 5 shows a flow diagram of an exemplary method 500 for commissioning a light source. At 510, the computing device 103 may receive data indicative of a planned geographic location of the light source 101 and data representative of commissioning information of the light source 101. At 520, the computing device 103 may receive data indicative of an actual geographic location of the arrival angle receiver 106 relative to the planned geographic location of the light source 101. At 530, the light source 101 may transmit outgoing beacon signals 107, each including a stored light source identifier that uniquely identifies the light source 101. At 540, angle-of-arrival receiver 106 may receive a beacon signal including outgoing beacon signal 107. The beacon signals carry individual light source identifiers that uniquely identify the individual light sources 101. At 550, the computing device 103 may calculate the actual geographic location of the light source 101 based on the following information: a) the actual geographic position of the angle of arrival receiver 106 relative to the planned geographic position of the light source 101; and b) the respective angles of arrival of the beacon signals 107. At 560, the computing device 103 may compare the planned geographic location to the actual geographic location to correlate the commissioning information with the light source identifier. At 570, the computing device 103 may send the associated light source identifier and commissioning information to the individual light sources 101.

While the figures illustrate various actions occurring in series, it is to be understood that the various actions illustrated may occur substantially in parallel, and that, while actions may be illustrated as occurring in parallel, it is to be understood that such actions may occur substantially in series. While multiple processes are described with respect to the illustrated approach, it is understood that a greater or lesser number of processes may be employed, and that lightweight processes, conventional processes, threads, and other approaches may be employed. It is to be understood that other exemplary methods may also include acts that occur substantially in parallel in some cases. The exemplary method and other embodiments shown may operate in real time, faster than real time in a software or hardware or hybrid software/hardware implementation, or slower than real time in a software or hardware or hybrid software/hardware implementation.

While exemplary systems and methods, etc., have been illustrated by the description of examples and while the examples have been described in considerable detail, it is not the intention to restrict or in any way limit the scope of the appended claims to such detail. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the systems, methods, and so on described herein. Additional advantages and modifications will readily appear to those skilled in the art. Therefore, the invention is not limited to the specific details and illustrative examples shown or described. Accordingly, this application is intended to embrace alterations, modifications, and variations that fall within the scope of the appended claims. Furthermore, the foregoing description is not meant to limit the scope of the invention. Rather, the scope of the invention is to be determined by the appended claims and their equivalents.

(definition)

The following includes definitions of selected terms employed herein. The definitions include various examples or forms of components that fall within the scope of a term and that may be used for implementation. These examples are not intended to be limiting. Both singular and plural forms of terms may be within the definitions.

As used herein, a "data store" or "database" refers to a physical or logical entity that can store data. The data store may be, for example, a database, a table, a file, a list, a queue, a heap, a memory, a register, and so forth. The data store may reside in one logical or physical entity, or may be distributed between two or more logical or physical entities.

"logic", as used herein, includes but is not limited to hardware, firmware, software, or combinations of each to perform a function or an action, or to cause a function or an action from other logic, method, or system. For example, based on a desired application or needs, logic may include a software controlled microprocessor, discrete logic such as an Application Specific Integrated Circuit (ASIC), a programmed logic device, or a memory device including instructions, etc. Logic may include one or more gates, combinations of gates, or other circuit components. Logic may also be fully embodied as software. Where multiple logical logics are described, the multiple logical logics may be combined into one physical logic. Similarly, where a single logical logic is described, it may be distributed among multiple physical logics.

"Signal", as used herein, includes but is not limited to one or more electrical or optical signals, analog or digital signals, data, one or more computer or processor instructions, messages, bits or bit streams, or other means that can be received, transmitted, or detected.

In the context of signals, a connection via which "operably connected" or entities are "operably connected" is one that can send or receive signals, physical communications, or logical communications. Typically, an operable connection includes a physical interface, an electrical interface, or a data interface, but it should be noted that an operable connection may include different combinations of these or other types of connections sufficient to allow operable control. For example, two entities may be operably connected by being able to communicate signals to each other directly or through one or more intermediate entities such as a processor, operating system, logic, software, or other entity. Logical or physical communication channels may be used to create the operative connection.

To the extent that the terms "in …" or "within … (into)" are used in the specification or claims, it is intended to mean otherwise "on …" or "on … (onto)". Furthermore, to the extent that the term "connected" is used in either the specification or the claims, it is intended to mean "directly connected" not only, but also "indirectly connected," such as through one or more other components or the like. A connection by which "operably connected" or entities are "operably connected" is one by which an operably connected entity or an operable connection carries out its intended purpose. An operable connection may be a direct connection or one or more intervening entities that cooperate or otherwise are part of a connection or an indirect connection between operatively connected entities.

To the extent that the term "includes" or "including" is used in either the detailed description or the claims, it is intended to be inclusive in a manner similar to the term "comprising" as that term is interpreted when employed as a transitional word in a claim. Furthermore, to the extent that the term "or" (e.g., a or B) is employed in the detailed description or claims, it is intended to mean "a or B or both". When applicants intend to indicate "only a or B but not both," then the term "only a or B but not both" will be employed. Thus, use of the term "or" herein is the inclusive, and not the exclusive use. See, Bryan A. Garner, A Dictionary of model Legal Usage 624(3D. Ed. 1995).