WO2025067946A1

WO2025067946A1 - Systems and devices for lighting communication control

Info

Publication number: WO2025067946A1
Application number: PCT/EP2024/075898
Authority: WO
Inventors: Tim Boescke
Original assignee: Ams-Osram International Gmbh
Priority date: 2023-09-26
Filing date: 2024-09-17
Publication date: 2025-04-03

Abstract

A lighting module including one or more light sources, a controller configured to cause the lighting module enter a first operating mode. When the lighting module is in the first operating mode, the controller is configured to allow the lighting module to receive messages. In response to receiving a skip message while the lighting module is in the first operating mode, the controller is configured to cause the lighting module to enter a second operating mode. In response to receiving a data message while the lighting module is in the first operating mode, the controller is configured to cause the lighting module to enter a third operating mode. When the lighting module is in the second operating mode, the controller is configured to cause the lighting module to retransmit or forward one or more messages received while in the second operating mode.

Description

SYSTEMS AND DEVICES FOR LIGHTING COMMUNICATION CONTROL

Field

This present disclosure generally relates to lighting communication .

Background

FIG . 1A shows an example a network 100 . The network 100 includes a host 110 and a plurality of nodes 120 . The host 110 can be a microcontroller or microcontroller unit (MCU) . As shown in FIG . IB, each node 120 can be a LED unit or LED module including red, green, and blue emitters 130 , an LED driver 140 , and a controller or controller circuitry 160 , and input and output ports 165a and 165b, all which can be combined in one package . The controller circuitry 160 may include communication circuitry for communicating with other modes or microcontrollers coupled to the node 120 . As shown, in the network 100 , the MCU 110 is coupled to the nodes 120 . For example , the nodes 120 and the MCU may be coupled via a bus connection 150 .

The network 100 can be implemented in a variety of settings , such as in automotive fields . For example , the network 100 may be used to try to reali ze lighting ef fects in a car interior .

The network 100 , in the daisy chain configuration, can be controlled by the host/MCU 110 which sends transmissions to the first node in the chain . The first node will accept the data i f it is targeted at this node , or forward the data to the next node i f it is targeted at another node . During forwarding, the data is typically retimed and buf fered . This mechanism can allow for ef ficient forwarding of the data between up to hundreds of nodes without loss of data integrity .

Previously solutions are shown in FIG . 2 . The host communicates with the nodes by sending out telegrams that consist at least of a command field, an address field and a data field as shown below (bit sizes may vary) :

4bit lObit 24bit

A node (e.g., a LED module) can receive a telegram and compares the address field with an individually assigned address. If the address matches, the telegram will be consumed by the node. If the address does not match, the telegram is forwarded to the next devices.

One known solution is to simplify address assignment, such as by an autoadressing scheme is employed: All nodes have an undefined address after power on/reset. A specific command is sent to the chain, which will assign increasing addresses to each device.

However, there are several disadvantages with this approach. The overhead is large. Namely, the address field adds significant overhead to each telegram, reducing the available bandwidth to the sent data.

Further, there is a lack of robustness. For example, during autoadressing the address is stored in volatile memory and may be corrupted during a power spike. Special measures need to be implemented to detect this condition and recover from it. Another issue is the complexity in implementation. That is, the implementation of autoaddressing, address detection and forwarding adds logic complexity, which increases die size and hence cost.

In addition, there are issues with latency. It is necessary to receive at least the complete address field before starting to forward data to the next node. This leads to an accumulative delay that increases with chain length.

Alternatively, another known approach is commonly used in consumer level addressable RGB LEDs. In this approach, instead of using individual addressed nodes, the data designated to the LED module is simple sent to the bus in order of the LED modules. That is, the first packet targets a first LED module, second packet targets a second LED module, and so on.

This behavior can be implemented with a simple state machine 300 that has two states: "Consume" (C) and "Forward" (F) . This simple state machine is illustrated in FIG. 3. FIG. 4 shows one example of the progression and states of the nodes 120 of the network 100 at sequential stages 400a to 400d that implements this approach.

In a Consume mode 310, Data received on the input of the node is stored in an internal register until a full telegram has been received. The telegram can be a data packet, for example.

A node transitions to "Forward 320" from Consume 310 after a data packet has been received. In Forward 320 mode, data received on the input of the node is directly forwarded to the output (e.g., after retiming) . If the bus had idled the state transitions to Consume 310.

This approach also has disadvantages. With this approach, it is not possible to address individual nodes or LED modules. The approach is less forgiving towards bit-errors, since the entire transmission would be lost instead of only single packets. This approach also lacks safety features such as: cyclic redundancy check (CRC) , upstream transfers for monitoring.

Description

In the drawings, like reference characters generally refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis instead generally being placed upon illustrating the principles of the disclosure. In the following description, various aspects of the disclosure are described with reference to the following drawings, in which : FIG . 1A shows an example of a network 100 including a host 110 and a plurality of nodes 120 ;

FIG . IB shows an example of LED node or module ;

FIG . 2 shows examples of communicating in a network;

FIG . 3 illustrate an example of a state machine ;

FIG . 4 shows example of a network in di f ferent stages ;

FIG . 5 illustrates examples of a state machine according to aspects of the present disclosure ;

FIG . 6A to 6B illustrate a network at di f ferent stages according to aspects of the present disclosure ;

FIG . 7 and 8 each illustrate a method according to aspects of the present disclosure .

The following detailed description refers to the accompanying drawings that show, by way of illustration, speci fic details and aspects in which the disclosure may be practiced . One or more aspects are described in suf ficient detail to enable those skilled in the art to practice the disclosure . Other aspects may be utili zed and structural , logical , and electrical changes may be made without departing from the scope of the disclosure . The various aspects described herein are not necessarily mutually exclusive , as some aspects can be combined with one or more other aspects to form new aspects . Various aspects are described in connection with methods and various aspects are described in connection with devices . However, it may be understood that aspects described in connection with methods may similarly apply to the devices , and vice versa . Throughout the drawings , it should be noted that like reference numbers are used to depict the same or similar elements, features, and structures. Throughout the drawings, it should be noted that proportions are not necessary to scale and that the size of features may be emphasized for ease of illustration.

FIG. 5 shows an illustration of an example of simple state machine 500. The state machine 500 may be implemented in various networks and nodes thereof, including networks such as the network 100 of FIG. 1

In implementing the state machine 500, allows an improved way to implement sub-addressing in a network setting. Two different kinds or types of telegrams of variable length can be used in connection with implementing the state machine 500.

A first type of message or telegram to be used can be a "skipmessage". In some examples, the skip message may be implemented using a single bit, for example, a single bit with value of "0". In other cases, more bits maybe used to implement the skip message .

In addition, a second type of telegram or skip message may be used in connection with implementing the state machine 500, namely a data-message . I

In some cases, the data-message includes a first field followed by data field or data payout. The first field may be also a single bit. For example, in the case where the skip message is also 1-bit in length, the skip message may have a value of "0" while the first field of the data message has a value "1", or vice versa. The data field or data payout of the data message may be any suitable length, such as a 24-bits (of RGB values) in one example.

Description of the state may be described in connection with node 120 or lighting module of FIG. IB. However other types or variations of nodes or modules may also implement the state machine 500, mutatis mutandis. For example , the node 120 may be configured or set in a first operating mode . This first operating mode may be a waiting mode W . In the first operating mode or the waiting mode W, the node is configured to receive messages . That is a controller 160 of the node 120 allows the node 120 to receiving messages while in the first operating mode .

Further, the node 120 may transition or switch to another mode . In one example , the node 120 may switch from the first operating mode or waiting mode W in response to receiving certain communications .

In one case , while the node 120 or controller 160 is in the first operating mode , the controller 160 may cause the node 120 to switch to enter a second operating mode in response to the controller 160 determining the node 120 receives a skip message . This second operating mode may be the forward mode F depicted in FIG . 5 . The skip message may include a skip field or may only include a skip field in some examples . In one case , the wherein the skip message is a one-bit message , e . g . , where a value of " 0" indicates to skip .

In another case , while the node 120 or controller 160 is in the first operating mode (waiting mode W) , the controller 160 may cause the node 120 to switch to enter a third operating mode in response to the controller 160 determining the node 120 receives a data message ( a certain type of data message as described) . This third operating mode may be the consume mode C depicted in FIG . 5 .

In at least one example , the data message telegram may that causes the node 120/controller 160 to transition the node 120 from the first operating mode to the third operating mode may have a certain format . In at last one case , data message or data message telegram can include a data field indicating one or more settings . In the context of node 120 being a lighting module , the settings can be lighting settings including, for example , pulse-width-modulation settings , brightness , colors , which light sources to emit , etc . for the lighting module . The data message or data message telegram can also include a skip field and hold a value that indicates for the node not skip (e.g., forward or retransmit) the data message or data payout. In addition, the data message can include data field trails bitwise behind the skip field. This means that the skip field can be bitwise the first field received by the node 120, followed by the data field or data payout which can include the settings. In some situations, the skip field can hold a value of "1", such as when the skip field holding a value of "0" indicates to skip (a skip message) .

In some cases, in response to the skip message being received while the node 120 is in the first operating mode, the controller 160 can be configured to cause the node 120/controller 160 to immediately enter the second operating mode (e.g., forwarding mode F) . That is, the controller 160 may cause the node 120 to enter the second operating mode without any other actions occurring or intervening.

Similarly, in response to the data message being received while the node 120 is in the first operating mode, the controller 160 can be configured to cause the node 120/controller 160 to immediately enter the third operating mode (e.g., consume mode F) .

FIG. 6A shows an example of a network 600 in which the nodes can function according to the state machine such 500 of FIG. 5. Specifically, the FIG. 6 shows the network in states, 600a, 600b, and. 600c. The result of the transitions shows an instance where the host/MCU 610 can specifically address the second node in the network, node 620b.

The nodes 620a to 620N may be any suitable nodes including lighting modules (e.g., LED modules) such as depicted in FIG. IB. The nodes may be coupled in series with a connection 650.

At stage 600a, the nodes 620a-620N each are operating in the first operating mode or in the waiting mode W. In one case, the nodes 620a-620N may have been initialized or reset to such values .

At 600b, the states or the operating modes have changed as the state or operating modes of node 620a and 620b have changed. In this case, the node 620a is in the forward operating mode or second operating mode while the node 620b is in the consume mode or the third operating mode.

For example, the change from stage 600a to 600b could occur by the host or MCU 610 sending out a skip message that arrives at the node 620a. The node 620a, which was in the first mode, now transitions to the second operating mode or forwarding mode. Hence, while in the forwarding mode, the node 620a is configured to forward messages (e.g. to the next or successive node in the network) .

The transition from stage 600b to 600c for the network can occur in response to another message sent by the host/MCU 610. The host/MCU 610 sends a data message (e.g., a data telegram message with a skip field indicating to skip) . The data message first arrives at the node 620a. Since the node 620a is still in forwarding mode, the node 620a can forward the data message to the next node, 620b. The node 620b, which was in the waiting mode or first operating mode, can in response to the data message transition into the consume mode or third operating mode. As a result of receiving the forwarded data message originating from the host 610, the node 620b transitions into the consume mode and stores data from the data message (e.g., reads/stores data from data field of the data message) . Thereafter, the node 620b may update some of its settings using the stored data.

As a result of the progression from stages 600a to 600c, the host/MCU 610 has been able to address the node 610b by first sending a single skip message to node 620a and then a data message which is forwarded to node 620b. FIG. 6B shows another example of progression of the network 600 in which the nodes can operate according to a state machine such as the state machine 500.

In FIG. 6B, the host 610 can be configured to specifically address the node 620c (third in series) . From stage 600, the host 610 sends two skip messages in succession. This would result in the nodes 620a and 620 to enter the forwarding mode (second operating mode) . In particular, stage 600b, is a result of the first skip message, which causes the first node in series, node 620, to enter the forwarding mode F.

Stage 600c is realized after the host 610 sends the second skip message in a row. The second skip message is sent out which arrives first at the first node 620a. Since the node 620 at stage 600b is in the forwarding mode F, the node 620a forwards the skip message to the node 620b. As a result, the node 620b transitions to forwarding mode F, as shown in stage 600c.

Next, the host 610 sends a data message. The data message is forwarded first by the nodes 620a and then by the node 620b to the third in series node 620c. As a result of received the forwarded data message originating from the host 610, the node 620c transitions into the consume mode and stores data from the data message (e.g., stores/reads data from data field of the data message) . Thereafter, the node 620c may update some of its settings, using the stored data, either while in the consume mode, or while in another mode, e.g., a forwarding mode.

In the both cases shown in FIG. 6A and FIG. 6B, the state of the nodes 620a-620N may transition back to waiting mode W or first operating mode. For example, referring to FIG. 6A, the node 620b may transition to forwarding mode F after "consuming" the data of the data message at stage 600c, and then may transition to waiting mode W if no communications are sent, e.g., the connection or bus 650 connecting to the node 620b is idle. Similarly, the node 620a which is in forwarding mode F at stage 600c, can transition to waiting mode W provided the connection 650 to the node 620 is idle FIG . 7 shows a method 700 for communicating with a plurality of lighting modules connected in series in a network . The method 700 includes at 710 , sending, by a host device a N number of skip messages arranged in a data stream to the plurality of lighting modules . At 715 , the method includes sending by the host device , after sending the N number of skip messages , one or more data messages in a data stream .

At 720 , the method includes receiving by the plurality of lighting modules , the data stream including the number N of skip messages , which further includes each of the first N in series lighting modules : at 722 , receiving a respective one of the skip messages of the data stream, and at 724 , retransmitting any skip messages and/or data messages received after receiving the respective one of the skip messages to a successive in-series lighting module .

At 730 , the method 700 includes receiving by the plurality of lighting modules , the one or more data messages which further comprises receiving at the N+ l lighting module the one or more data messages forwarded from the first N in-series lighting modules .

FIG 8 shows a method 800 for communicating by a node arranged in series in a network with one or more other nodes and host device . The method 800 includes at 810 , entering, by the node , a first operating mode . At 820 , the method 800 includes that while in the first operating mode , receiving, at the node , a first message including a skip field indicating for the node to forward messages . The method 800 further includes at 830 , in response to the first message , entering, by the node , a second operating mode . At 840 , the method 800 includes while in the second operating mode , retransmitting, by the LED unit , one or more messages received subsequent to the first message . The method 800 includes at 850 , re-entering, by the node , the first operating mode and at 860 , receiving, at the node , a second message at the input port , the second message including a skip field and a data message , the skip field indicating to process the data message . At 870 , the method 800 includes , in response to the second message , entering, by the node , a third operating mode . The method 800 includes at 880 , while in the third operating mode , processing, by the node , the data message ; and at 890 re-entering, by the node , the first operating mode . The node of the method 800 can be light-emitting diode ( LED) modules each including one or more light-emitting diodes .

In the following some examples are described, which relate to what is described herein and shown in the figures .

Example 1 is a lighting module including : one or more light sources ; a controller configured to cause the lighting module enter a first operating mode ; and wherein while the lighting module is in the first operating mode , the controller is configured to allow the lighting module to receive messages ; wherein in response to receiving a skip message while the lighting module is in the first operating mode , the controller is configured to cause the lighting module to enter a second operating mode ; wherein in response to receiving a data message while the lighting module is in the first operating mode , the controller is configured to cause the lighting module to enter a third operating mode ; wherein while the lighting module is in the second operating mode , the controller is configured to cause the lighting module to retransmit or forward one or more messages received while in the second operating mode ; wherein while the lighting module is in the third operating mode , the controller is configured to cause the lighting module to read and store data from the data message received while in the first operating mode and then enter the second operating mode .

Example 2 is the subj ect matter of Example 1 , wherein while the lighting module is in the second operating mode , the controller may be configured to cause the lighting module to retransmit or forward one or more received messages automatically without reading data thereof .

Example 3 is the subj ect matter of Example 1 or 2 , wherein while the lighting module is in the second operating mode , the controller may be configured retransmit or forward one or more received messages on a data bus coupling the lighting module to one or more other lighting modules .

Example 4 is the subj ect matter of any of Examples 1 to 3 , wherein while the lighting module is in the second operating mode , the controller may be configured to cause the lighting module to enter the first operating mode .

Example 5 is the subj ect matter of Example 4 , wherein while the lighting module is in the second operating mode , the controller may be configured to cause the lighting module to enter the first operating mode after experiencing a predefined idle period in which either no messages are received by the lighting module or a bus connected to the lighting module is idle .

Example 6 is the subj ect matter of Example 5 , wherein the predefined idle period may be 50 microseconds or less .

Example 7 is the subj ect matter of Example 5 , wherein the predefined idle period may be 500 microseconds or less .

Example 8 is the subj ect matter of Example 5 , wherein after the predefined idle the lighting module may be configured to send an end message .

Example 9 is the subj ect matter of any of Examples 1 to 8 , wherein while the lighting module is in the second operating mode , the controller may be configured to process and update one or more lighting module settings based on data message stored previously while the lighting module was previously in the third operating mode .

Example 10 is the subj ect matter of any of Examples 1 to 9 , wherein the skip message may include a skip field .

Example 11 is the subj ect matter of Example 10 , wherein the skip message may be a one-bit message .

Example 12 is the subj ect matter of Example 10 or 11 , wherein the skip field of the skip message may have a value of zero .

Example 13 is the subj ect matter of any of Examples 1 to 12 , wherein the data message may include a data field indicating one or more settings for the lighting module .

Example 14 is the subj ect matter of Example 13 , wherein the data message may further include a skip field, wherein the data field trails bitwise behind the skip field, and wherein the skip field indicates not to skip or forward the data message .

Example 15 is the subj ect matter of Example 14 , wherein the skip field may have a value of one .

Example 16 is the subj ect matter of any of Examples 1 to 15 , wherein in response to receiving the skip message while the lighting module is in the first operating mode , the controller may be configured to cause the lighting module to immediately enter the second operating mode .

Example 17 is the subj ect matter of any of Examples 1 to 16 , wherein in response to receiving the skip message while the lighting module is in the first operating mode , the controller may be configured to cause the lighting module to immediately enter the third operating mode . Example 18 is the subj ect matter of any of Examples 1 to 17 , wherein the lighting module may be a light emitting diode module , and wherein the one or more light sources may be light-emitting diodes .

Example 1A is a method for communicating with a plurality of lighting modules connected in series in a network, the method including : sending, by a host device a N number of skip messages arranged in a data stream to the plurality of lighting modules ; and sending by the host device , after sending the N number of skip messages , one or more data messages in a data stream; receiving by the plurality of lighting modules , the data stream including the number N of skip messages , which further comprises each of the first N in series lighting modules : receiving a respective one of the skip messages of the data stream, and retransmitting any skip messages and/or data messages received after receiving the respective one of the skip messages to a successive in-series lighting module ; receiving by the plurality of lighting modules , the one or more data messages which further comprises receiving at the N+ l lighting module the one or more data messages forwarded from the first N in-series lighting modules .

Example 2A is the subj ect matter of Example 1A, wherein receiving, at the N+ l lighting module , a first one of the one or more received data messages forwarded from the first N inseries lighting modules may further include : storing data from the first one of the one or more received data messages .

Example 3A is the subj ect matter of Example 2A, which may further include after storing the data from the first one of the one or more received data messages , automatically forwarding, by the N+ l lighting module , any data messages received thereafter to a successive in series lighting module . Example 4A is the subj ect matter of Example 3A, wherein forwarding any data message received after the first one of the one or more received data messages may include automatically forwarding any data message received thereafter for a predefined period of time .

Example 5A is the subj ect matter of Example 3A or 4A, which may further include updating settings of the N+ l lighting module based on data stored from the first one of the one or more received data messages .

Example 6A is the subj ect matter of any of Examples 1A to 5A, wherein the skip message may include a message including a skip field .

Example 7A is the subj ect matter of Example 6A, wherein the skip message may be a one-bit message .

Example 8A is the subj ect matter of Example 6A or 7A, wherein the skip field may include a value of zero .

Example 9A is the subj ect matter of any of Examples 1A to 8A, wherein the data message may include a data field indicating one or more settings for the lighting module .

Example 10A is the subj ect matter of Example 9A, wherein the data message may include a skip field, wherein the data field bitwise trails the skip field, and wherein the skip field indicates not to skip the message .

Example 11A is the subj ect matter of Example 10A, wherein the skip field may have a value of one .

Example 12A is the subj ect matter of any of Examples 1A to 11A, wherein the lighting modules may be light-emitting diode modules including one or more light-emitting diodes . Example IB is a method for controlling communication at a node arranged in series in a network with one or more other nodes and host device, the method comprising: entering, by the node, a first operating mode; while in the first operating mode, receiving, at the node, a first message comprising a skip field indicating for the node to forward messages; in response to the first message, entering, by the node, a second operating mode; while in the second operating mode, retransmitting, by the LED unit, one or more messages received subsequent to the first message ; re-entering, by the node, the first operating mode; receiving, at the node, a second message at the input port, the second message comprising a skip field and a data message, the skip field indicating to process the data message; in response to the second message, entering, by the node, a third operating mode; while in the third operating mode, processing, by the node, the data message; and re-entering, by the node, the first operating mode.

Example 2B is the subject matter of Example IB, wherein the nodes may be light-emitting diode (LED) modules including one or more light-emitting diodes.

The examples above may be combined with each other in any suitable manner. For example, any apparatus of devices described herein may be implemented as a method and methods described herein may be implemented as an apparatus or device.

The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any example or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other examples or designs .

The words "plurality" and "multiple" in the description or the claims expressly refer to a quantity greater than one. The terms "group (of) ", "set [of] ", "collection (of) ", "series (of)", "sequence (of)", "grouping (of)", etc., and the like in the description or in the claims refer to a quantity equal to or greater than one, i.e. one or more. Any term expressed in plural form that does not expressly state "plurality" or "multiple" likewise refers to a quantity equal to or greater than one .

The term "connected" can be understood in the sense of a (e.g. mechanical, optical and/or electrical) , e.g. direct or indirect, connection and/or interaction. For example, several elements can be connected together mechanically such that they are physically retained (e.g., a plug connected to a socket) and electrically such that they have an electrically conductive path (e.g., signal paths exist along a communicative chain) .

As used herein, unless otherwise specified the use of the ordinal adjectives "first", "second", "third" etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.

As utilized herein, terms "module", "component," "system," "circuit, " "element, " "slice, " "circuitry, " and the like are intended to refer to a set of one or more electronic components, a computer-related entity, hardware, software (e.g., in execution) , and/or firmware. For example, circuitry or a similar term can be a processor, a process running on a processor, a controller, an object, an executable program, a storage device, and/or a computer with a processing device. By way of illustration, an application running on a server and the server can also be circuitry. One or more circuits can reside within the same circuitry, and circuitry can be localized on one computer and/or distributed between two or more computers. A set of elements or a set of other circuits can be described herein, in which the term "set" can be interpreted as "one or more . Such electric or electronic circuitry can be operated by a software application or a firmware application executed by one or more processors. The one or more processors can be internal or external to the apparatus and can execute at least a part of the software or firmware application. As yet another example, circuitry can be an apparatus that provides specific functionality through electronic components without mechanical parts; the electronic components can include one or more processors therein to execute executable instructions stored in computer readable storage medium and/or firmware that confer (s) , at least in part, the functionality of the electronic components. As another example, circuitry or similar term can be implemented in hardware such as application specific integrated circuit (ASIC) , programmable gate array (PGA) , discrete digital circuits, etc.) or in a combination of hardware and software (e.g., a software model executed by a corresponding processor) .

The term "data" as used herein may be understood to include information in any suitable analog or digital form, e.g., provided as a file, a portion of a file, a set of files, a signal or stream, a portion of a signal or stream, a set of signals or streams, and the like. Further, the term "data" may also be used to mean a reference to information, e.g., in form of a pointer. The term data, however, is not limited to the aforementioned examples and may take various forms and represent any information as understood in the art.

As used herein, a signal that is "indicative of" a value or other information may be a digital or analog signal that encodes or otherwise communicates the value or other information in a manner that can be decoded by and/or cause a responsive action in a component receiving the signal. The signal may be stored or buffered in computer readable storage medium prior to its receipt by the receiving component and the receiving component may retrieve the signal from the storage medium. Further, a "value" that is "indicative of" some quantity, state, or parameter may be physically embodied as a digital signal , an analog signal , or stored bits that encode or otherwise communicate the value .

As used herein, a signal may be transmitted or conducted through a signal chain in which the signal is processed to change characteristics such as phase , amplitude , frequency, and so on . The signal may be referred to as the same signal even as such characteristics are adapted . In general , so long as a signal continues to encode the same information, the signal may be considered as the same signal . For example , a transmit signal may be considered as referring to the transmit signal in baseband, intermediate , and radio frequencies .

While the above descriptions and connected figures may depict device components as separate elements , skilled persons will appreciate the various possibilities to combine or integrate discrete features , functions into a single element . Such may include combining two or more components into a single component . Conversely, skilled persons will recogni ze the possibility to separate a single element into two or more discrete elements , such as splitting a single component into two or more separate components .

It is appreciated that implementations of methods detailed herein are exemplary in nature , and are thus understood as capable of being implemented in a corresponding device . Likewise , it is appreciated that implementations of devices detailed herein are understood as capable o f being implemented as a corresponding method . It is thus understood that a device corresponding to a method detailed herein may include one or more components configured to perform each aspect of the related method .

All acronyms defined in the above description additionally hold in all claims included herein .

While the disclosure has been particularly shown and described with reference to speci fic embodiments , it should be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the disclosure as defined by the appended claims . The scope of the disclosure is thus indicated by the appended claims and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced .

Reference Numeral List lOO/lOOa/lOOb network

110 host/microcontroller

120 node/LED unit

130 light emitter

140 driver/ LED driver

150 bus connection

160 controller/controller circuitry

165a input port

165b output port

300 state machine

310 consume mode state

320 forward mode state

400 network

400a-400d network at different states/stages 500 state machine

510-530 state/mode transitions

600 network

600a-600d network at different states/stages 610 host/microcontroller unit

620/ 620a- 62 ON node/nodes

700 method

710-730 method steps 800 method

810-890 method steps

Claims

1 . A lighting module comprising : one or more light sources , a controller configured to cause the lighting module enter a first operating mode ; and wherein while the lighting module is in the first operating mode , the controller is configured to allow the lighting module to receive messages ; wherein in response to receiving a s kip message while the lighting module is in the first operating mode , the controller is configured to cause the lighting module to enter a second operating mode ; wherein in response to receiving a data message while the lighting module is in the first operating mode , the controller is configured to cause the lighting module to enter a third operating mode ; wherein while the lighting module is in the second operating mode , the controller is configured to cause the lighting module to retransmit or forward one or more messages received while in the second operating mode ; wherein while the lighting module is in the third operating mode , the controller is configured to cause the lighting module to read and store data from the data message received while in the first operating mode and then enter the second operating mode .

2 . The lighting module of claim 1 , wherein while the lighting module is in the second operating mode , the controller is configured to cause the lighting module to retransmit or forward one or more received messages automatically without reading data thereof .

3 . The lighting module of claim 1 , wherein while the lighting module is in the second operating mode , the controller is configured retransmit or forward one or more received messages on a data bus coupling the lighting module to one or more other lighting modules .

4 . The lighting module of claim 1 , wherein while the lighting module is in the second operating mode , the controller is configured to cause the lighting module to enter the first operating mode .

5 . The lighting module of claim 4 , wherein while the lighting module is in the second operating mode , the controller is configured to cause the lighting module to enter the first operating mode after experiencing a predefined idle period in which either no messages are received by the lighting module or a bus connected to the lighting module is idle .

6 . The lighting module of claim 5 , wherein the predefined idle period is 50 microseconds or less .

7 . The lighting module of claim 5 , wherein after the predefined idle the lighting module is configured to send an end message .

8 . The lighting module of claim 1 , wherein while the lighting module is in the second operating mode , the controller is configured to process and update one or more lighting module settings based on data message stored previously while the lighting module was previously in the third operating mode .

9 . The lighting module of claim 1 , wherein the skip message comprises a s kip field .

10 . The lighting module of claim 1 , wherein the data message comprises a data field indicating one or more settings for the lighting module .

11 . The lighting module of claim 10 , wherein the data message further comprises a s kip field, wherein the data field trails bitwise behind the s kip field, and wherein the skip field indicates not to skip or forward the data message .

12 . The lighting module of claim 1 , wherein in response to receiving the s kip message while the lighting module is in the first operating mode , the controller is configured to cause the lighting module to immediately enter the second operating mode .

13 . The lighting module of any of claims 1 to 12 , wherein in response to receiving the s kip message while the lighting module is in the first operating mode , the controller is configured to cause the lighting module to immediately enter the third operating mode .

14 . The lighting module of claim 1 , wherein the lighting module is a light emitting diode module , and wherein the one or more light sources are light-emitting diodes .

15 . A method for communicating with a plurality of lighting modules connected in series in a network, the method comprising : sending, by a host device a N number of skip messages arranged in a data stream to the plurality of lighting modules ; and sending by the host device , after sending the N number of skip messages , one or more data messages in a data stream; receiving by the plurality of lighting modules , the data stream including the number N of skip messages , which further comprises each of the first N in series lighting modules : receiving a respective one of the skip messages of the data stream, and retransmitting any skip messages and/or data messages received after receiving the respective one of the skip messages to a successive in-series lighting module ; receiving by the plurality of lighting modules , the one or more data messages which further comprises receiving at the N+ l lighting module the one or more data messages forwarded from the first N in-series lighting modules .

16 . The method of claim 15 , wherein receiving, at the N+ l lighting module , a first one of the one or more received data messages forwarded from the first N inseries lighting modules further comprises : storing data from the first one of the one or more received data messages .

17 . The method of claim 16 , further comprising : after storing the data from the first one of the one or more received data messages , automatically forwarding, by the N+ l lighting module , any data messages received thereafter to a successive in series lighting module .

18 . The method of claim 17 , wherein forwarding any data message received after the first one of the one or more received data messages comprises automatically forwarding any data message received thereafter for a predefined period of time .

19 . The method of claim 17 or 18 , further comprising : updating settings of the N+ l lighting module based on data stored from the first one of the one or more received data messages .

20 . The method of claim 15 , wherein the data message comprises a data field indicating one or more settings for the lighting module , and wherein the data message comprises a skip field, wherein the data field bitwise trails the skip field, and wherein the skip field indicates not to skip the message .