EP4169357A1 - Detection and correction of a de-synchronization of a luminaire - Google Patents
Detection and correction of a de-synchronization of a luminaireInfo
- Publication number
- EP4169357A1 EP4169357A1 EP21731184.4A EP21731184A EP4169357A1 EP 4169357 A1 EP4169357 A1 EP 4169357A1 EP 21731184 A EP21731184 A EP 21731184A EP 4169357 A1 EP4169357 A1 EP 4169357A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- luminaire
- status
- luminaires
- trigger
- group
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H05—ELECTRIC TECHNIQUES NOT OTHERWISE PROVIDED FOR
- H05B—ELECTRIC HEATING; ELECTRIC LIGHT SOURCES NOT OTHERWISE PROVIDED FOR; CIRCUIT ARRANGEMENTS FOR ELECTRIC LIGHT SOURCES, IN GENERAL
- H05B47/00—Circuit arrangements for operating light sources in general, i.e. where the type of light source is not relevant
- H05B47/10—Controlling the light source
- H05B47/105—Controlling the light source in response to determined parameters
- H05B47/115—Controlling the light source in response to determined parameters by determining the presence or movement of objects or living beings
-
- H—ELECTRICITY
- H05—ELECTRIC TECHNIQUES NOT OTHERWISE PROVIDED FOR
- H05B—ELECTRIC HEATING; ELECTRIC LIGHT SOURCES NOT OTHERWISE PROVIDED FOR; CIRCUIT ARRANGEMENTS FOR ELECTRIC LIGHT SOURCES, IN GENERAL
- H05B47/00—Circuit arrangements for operating light sources in general, i.e. where the type of light source is not relevant
- H05B47/10—Controlling the light source
- H05B47/155—Coordinated control of two or more light sources
-
- H—ELECTRICITY
- H05—ELECTRIC TECHNIQUES NOT OTHERWISE PROVIDED FOR
- H05B—ELECTRIC HEATING; ELECTRIC LIGHT SOURCES NOT OTHERWISE PROVIDED FOR; CIRCUIT ARRANGEMENTS FOR ELECTRIC LIGHT SOURCES, IN GENERAL
- H05B47/00—Circuit arrangements for operating light sources in general, i.e. where the type of light source is not relevant
- H05B47/10—Controlling the light source
- H05B47/175—Controlling the light source by remote control
-
- H—ELECTRICITY
- H05—ELECTRIC TECHNIQUES NOT OTHERWISE PROVIDED FOR
- H05B—ELECTRIC HEATING; ELECTRIC LIGHT SOURCES NOT OTHERWISE PROVIDED FOR; CIRCUIT ARRANGEMENTS FOR ELECTRIC LIGHT SOURCES, IN GENERAL
- H05B47/00—Circuit arrangements for operating light sources in general, i.e. where the type of light source is not relevant
- H05B47/10—Controlling the light source
- H05B47/175—Controlling the light source by remote control
- H05B47/19—Controlling the light source by remote control via wireless transmission
-
- H—ELECTRICITY
- H05—ELECTRIC TECHNIQUES NOT OTHERWISE PROVIDED FOR
- H05B—ELECTRIC HEATING; ELECTRIC LIGHT SOURCES NOT OTHERWISE PROVIDED FOR; CIRCUIT ARRANGEMENTS FOR ELECTRIC LIGHT SOURCES, IN GENERAL
- H05B47/00—Circuit arrangements for operating light sources in general, i.e. where the type of light source is not relevant
- H05B47/10—Controlling the light source
- H05B47/175—Controlling the light source by remote control
- H05B47/196—Controlling the light source by remote control characterised by user interface arrangements
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02B—CLIMATE CHANGE MITIGATION TECHNOLOGIES RELATED TO BUILDINGS, e.g. HOUSING, HOUSE APPLIANCES OR RELATED END-USER APPLICATIONS
- Y02B20/00—Energy efficient lighting technologies, e.g. halogen lamps or gas discharge lamps
- Y02B20/40—Control techniques providing energy savings, e.g. smart controller or presence detection
Definitions
- the invention is generally related to the lighting devices which are connected to each other in a communication network. More specifically, the invention relates to a luminaire connected to a plurality of further luminaires allocated to at least one group via a network and to a method for changing a status of a luminaire connected to a plurality of further luminaires allocated to at least one group via a network.
- each group may include lighting devices arranged in a certain area of a room, building or public space.
- the lighting devices may, for example, be operated such that the luminaires in a group associated with an area occupied by one or more subjects have a higher lighting level than luminaires in groups associated with unoccupied areas. Such an operation of the luminaires particularly allows for saving energy.
- control messages for adjusting the lighting state of the luminaires such as messages of a sensor indicating an occupancy of an area associated with a certain group, are sent to all luminaires of the group, typically in a multicast transmission.
- a control message may not be correctly received by one or more individual luminaires included in a group, e.g. due to a routing failure in the network.
- the affected luminaires, which do not receive the control message are not synchronized with the other luminaires of the group.
- these luminaires may maintain a lower lighting level in case the control message instructs the luminaires to increase their lighting level (e.g.
- control message instructs the luminaires to decrease their lighting level (e.g. when it is detected that the area associated with the group is no longer occupied after a previous occupancy).
- One possible approach to detect de-synchronized lighting devices and re synchronize them with their groups is applicable in a lighting network having a central controller which maintains the intended lighting status of each luminaire included in the network.
- each luminaire may exchange status information with the central controller in order to determine whether or not the luminaire is operating as intended.
- lighting networks are often configured in accordance with a distributed architecture in which the lighting devices directly communicate with each other to exchange control commands without involving a central controller. As a consequence, these networks do usually not include a central device which maintains the status of the luminaires. Therefore, the aforementioned approach for detecting de-synchronized luminaires is not applicable in these networks.
- Distributed lighting networks are typically configured as mesh networks, such as for example wireless mesh networks according to the Zigbee or Bluetooth specification.
- a mesh network the nodes connect directly and dynamically to as many other nodes as possible and cooperate with each other to route messages to their intended recipients. Due to the open and dynamic nature of such a network, the nodes do typically not have complete information about the other nodes in the network. Especially in such a network, an unacknowledged transmission is often more efficient. In fact, an acknowledged transmission would not ensure that all recipients correctly receive a message because the sender of a multicast message does not know all intendent recipients of such a message from which it has to expect an acknowledgement of receipt.
- the invention suggests a luminaire connected to a plurality of further luminaires allocated to at least one group via a network.
- the luminaire is configured to (i) receive a status message from each of the further luminaires, each status message including status information indicating a current status of the respective luminaire and trigger information about a trigger that prompted the respective luminaire to adopt the current status, (ii) select at least some of the received status messages based on the trigger information included therein, (iii) compare the selected status messages and (iv) change its own status to a new status based on the comparison.
- the status of the luminaire or the status of a further luminaire, which is indicated in the status messages from this luminaire may particularly comprise a lighting level.
- the luminaire can detect a de-synchronization from the further luminaires on its own. This allows for detecting a de-synchronization in a network which does not include a central device managing the status of the luminaires included in the network. Moreover, by taking the trigger information into consideration in the selection of the status messages which are used for detecting and correcting a de-synchronization, it is possible to distinguish between status messages originating from luminaires which are synchronized with other luminaires from status messages originating from luminaires which are not synchronized with other luminaires. For the detection and correction of a de-synchronization of the luminaire, the latter status messages are preferably not taken into account. This allows for a reliable detection and correction of a de-synchronization.
- the trigger information included in each status message received from a further luminaire is indicative of whether the trigger relates to all luminaires of a group or is only valid for the respective further luminaire.
- the trigger information included in each status message received from a further luminaire is indicative of whether the trigger relates to all luminaires of a group or is only valid for the respective further luminaire.
- the trigger information configured in the aforementioned way can particularly be used in order to select the status messages which are compared in order to detect and correct a desynchronization of the luminaire.
- the luminaire is included in an allocated group and is configured to select status messages for the comparison, which include trigger information indicative of a trigger relating to all luminaires of the allocated group and which do not include trigger information indicative of a trigger that is only valid for the luminaire having sent the respective status messages.
- the trigger information included in the status messages may particularly specify the trigger reasons that prompted the luminaires to change to the status indicated in the status messages.
- possible trigger reasons include an occupancy of an area assigned to a certain group of luminaires, which may be detected by an occupancy sensor. For instance, such a detected occupancy of a certain area may prompt all luminaires of the group assigned to the area to operate at a first lighting level. Moreover, it may prompt all luminaires of a neighboring group to operate at a second lighting level, which is lower than the first lighting level.
- the information indicative of a trigger relating to all luminaires of the allocated group specifies a detection of an occupancy of an area assigned to the allocated group and/or a detection of an occupancy of an area assigned to a group of luminaires differing from the allocated group.
- the group differing from the allocated group may particularly be a neighboring group of the allocated group, when an occupancy of the area of the neighboring group prompts the luminaires of the allocated group to operate at a certain lighting level.
- the trigger information included in the status messages may specify a reception mode for the trigger that prompted the luminaires to the status indicated in the status messages.
- triggers may be messages including control commands and/or notifying about a detected occupancy of a certain area.
- Such messages may be received via groupcast or broadcast transmissions which are addressed to luminaires of one or more groups.
- such messages may be received via unicast transmissions, which are addressed to individual luminaires only.
- control commands relating to individual luminaires may be input manually only.
- one embodiment includes that the information indicative of a trigger that is only valid for one further luminaire having sent the status information specifies a reception of a message via a unicast transmission and/or a manual control input relating to the respective luminaire.
- the luminaire is configured to check whether a number of the selected status messages greater than a predetermined threshold include identical status information and/or corresponding trigger information, and to change its status to a new status selected in accordance with this status information or trigger information, if the check is affirmative.
- a number of the selected status messages greater than the predetermined threshold includes identical status information and/or trigger information corresponding to each other, there is a high likelihood that the luminaires having sent these status messages are intentionally synchronized with each other. Therefore, the new status of the luminaire can be determined based on this status information or the trigger information.
- trigger information may be regarded as corresponding to each other if they are identical. In one embodiment, trigger information may also be regarded as corresponding to each other, if they do not conflict with each other. This may particularly be the case if they can coexist in a group of synchronized luminaires.
- a de-synchronization can particularly be detected and corrected on the basis of status messages received from further luminaires of the group allocated to the luminaire carrying out the detection and correction.
- a de-synchronization can likewise be detected and corrected on the basis of status messages received from luminaires of other groups.
- the luminaire is therefore configured to obtain status messages from further luminaires not assigned to the allocated group, and to determine the new status at least on the basis of these status messages. This determination may particularly be carried out in a second step in case the number of selected status messages received from the luminaires of the allocated group, which include identical status information and/or trigger information corresponding to each other, is not greater than the threshold.
- a detection and correction of a de-synchronization may be also be possible in this situation.
- the luminaire is configured to select status messages from the further luminaires not assigned to the allocated group, which do not include trigger information indicative of a trigger that is only valid for the luminaire having sent the respective status messages, and to determine the new status on the basis of the selected status messages received from the further luminaires not assigned to the allocated group.
- the status messages received from the luminaires of the allocated group may additionally be taken into consideration in the determination of the new status and selected in order to determine the new status.
- the luminaire is configured to check whether a number of the selected status messages greater than a predetermined threshold include trigger information agreeing with each other, and to change its status to a new status selected in accordance with this trigger information, if the check is affirmative.
- the trigger information included in these messages may have to be identical in order to be regarded as agreeing with each other.
- trigger information which do not conflict with each other, may also be regarded as agreeing with to each other.
- the selected status messages used for determining the new status in this embodiment include status messages received from luminaires of multiple groups including the allocated groups
- trigger information included in status messages received from luminaires of different groups do not have to be identical in order to be regarded as agreeing with each other.
- the included trigger information has to be in agreement in order for them to be regarded as agreeing with each other.
- this is the case for a status message from a luminaire of a first group, which indicates a detected occupancy of an area assigned to this group as a trigger, and a status message from a luminaire of a neighboring group, which indicates a detected occupancy of the first area as a trigger.
- the luminaire may be connected to the further luminaires via a distributed communication network, particularly a mesh network. Moreover, the luminaire may be configured to obtain the status messages from the further luminaires by retrieving the status messages from the further luminaires, particularly by transmitting a related request to the further luminaires via a multicast transmission.
- the multicast transmission may be a groupcast transmission addressed to all luminaires of a group or a broadcast transmission addressed to all luminaires of the network.
- the invention suggests a method for changing a status of a luminaire connected to a plurality of further luminaires allocated to at least one group via a network.
- the method comprises: (i) receiving a status message from each of the further luminaires, each status message including status information indicating a current status of the respective luminaire and trigger information about a trigger that prompted the respective luminaire to adopt the current status, (ii) selecting at least some of the received status messages based on the trigger information included therein, (iii) comparing the selected status messages and (iv) changing its own status to a new status based on the comparison.
- Fig. 1 schematically and exemplarily shows luminaires connected to each other in a distributed communication network
- Fig. 2 schematically and exemplarily shows steps of a procedure for detecting and correction a de-synchronization of a luminaire with respect to other luminaires of a group.
- Fig. 1 schematically and exemplarily shows luminaires la-d, 2a-e, which are connected to each other in a communication network having a distributed network architecture.
- the communication network may particularly be a wireless mesh network, which may be configured according to the Zigbee or Bluetooth specification, for example. However, in further embodiments, the communication network may be configured in another way.
- the luminaires la-d, 2a-e are assigned to different groups. In the example shown in Fig. 1, there are two groups which are also referred to as group 1 and group 2 herein below and where the luminaires la-d are assigned to group 1 and the luminaires 2a-e are assigned to group 2. In addition, there may be further groups, which are not shown in the figure.
- each group may include luminaires la-d, 2a-e illuminating a particular area of a building, such as a particular room or part of a room, or public space, such as a section of a street, which differs from the area illuminated by the luminaires la-d, 2a-e of the other group(s).
- control devices are provided for controlling the luminaires la-d, 2a-e.
- these control devices may be used for controlling the lighting levels of the luminaires.
- At least some of the control devices are provided for a joint control of the lighting levels of each group, so that the luminaires 1-d, 2a-e of each group are in synchronization with each other in the normal operation of the luminaires, i.e. if no failures occur and if individual luminaires are not controlled in another way, as will be explained further below.
- the control devices for jointly controlling the luminaires la-d, 2a-e include occupancy sensors 3. These are sensors which are capable of detecting the presence of persons in a monitored area on the basis of their intrinsic features, such as the heat generated by the persons, their natural motion and/or their shape.
- occupancy sensors 3 are known to the person skilled in art as such and may be configured as infrared sensors (for detecting the heat emitted by persons), motion detectors or cameras, for example.
- one or more occupancy sensor(s) 3 may be assigned to each group of luminaires la-d, 2a-e, and the occupancy sensor(s) 3 assigned to a group may monitor a certain area assigned to this group. This area may at least approximately correspond to the area illuminated by the luminaires la-d, 2a-e of the group. Further, the occupancy sensor(s) 3 assigned to a group may be configured as separate devices communicating with the luminaires via the communication network, or it/they may be integrated into one or more luminaire(s) la-d, 2a-e of the relevant group as shown by way of example for the luminaire la in Fig. 1, which includes an occupancy sensor 3.
- the occupancy sensors 3 do not explicitly command the luminaires la-d, 2a-e to set a particularly lighting level. Rather, each occupancy sensor 3 may notify about a detected occupancy of its monitored area, and the luminaires la-d, 2a-e may set their lighting levels in response to such notifications in accordance with a predefined rule.
- the luminaires la-d, 2a-e of the group to which the occupancy sensor 3, which detected an occupancy, is assigned shall set their lighting level to a high value X, which may be between 70 % and 100 % of their maximum lighting level, for example, and the luminaires of the neighboring group shall set their lighting level to a lower value Y, which may be between 20 % and 50 % of their maximum lighting level, for example.
- a separate occupancy sensor 3 When a separate occupancy sensor 3 detects an occupancy of its monitored area, it may transmit a corresponding control message notifying about the detection to the luminaires la-d, 2a-e via the communication network and the luminaires la-d, 2a-e react to the control message in accordance with the rule.
- the control message notifying about the detection may be sent by the luminaire la-d, 2a-e and, in addition, the luminaire la-d, 2a-e may set its lighting level to the high value X in accordance with the rule, while the other luminaires react to the message according to the rule.
- the control messages notifying about the detection of an occupancy are also referred to as occupancy messages.
- An occupancy message may be sent in a broadcast mode, i.e. it is addressed to all luminaires la-d, 2a-e of the network.
- an occupancy message may be sent in a groupcast mode, i.e. addressed to all luminaires la-d, 2a-e of a particular group, to group 1 in one transmission and to the neighboring group 2 in another transmission.
- the occupancy message may identify the group to which the occupancy sensor 3, which detected the occupancy, is assigned. This information is used by the luminaires la-d, 2a-e receiving an occupancy message to set their lighting levels in accordance with the predefined rule.
- a luminaire receiving the control message sets its lighting level to the high value X, if it belongs to the same group as the occupancy sensor 4, which detected the occupancy. Otherwise, if the luminaire belongs to another group, it sets its lighting level to the lower value Y.
- control devices may be provided for individually controlling one or more particular luminaire(s) la-d, 2a-e.
- These control devices may include one or more user interaction (UI) elements 4, such as switches or graphical user interfaces.
- UI user interaction
- the control devices may allow a user to input level commands for instructing the associated luminaires la-d, 2a-e to set a desired lighting level and/or they may allow for inputting other commands that prompt the associated luminaires la-d, 2a-e to set a particular lighting level.
- An example of such a command is the command for activating a luminaire la-d, 2a-e, which has previously been inactive, where the luminaire la-d, 2a-e may set a predefined initial lighting level upon the activation.
- the UI elements 4 for individually controlling particular luminaires la-d, 2a-e may be integrated into these luminaires la-d, 2a-e, as shown by way of example for the luminaire lb in Fig. 1, which includes a UI element 4.
- a control command may be generated by the UI element 4, which may explicitly or implicitly specify a particular lighting level as described above, and the control command may be internally forwarded to a control circuit of the luminaire la-d, 2a-e, which sets the lighting level of the luminaire la-d, 2a-e in accordance with the control command.
- UI elements 4 for individually controlling particularly the luminaires la-d, 2a-e may be configured as separate devices.
- each control command is transmitted to the target luminaire la-d, 2a-e using a suitable communication medium.
- it may be transmitted to the target luminaire la-d, 2a-e over the communication network using a unicast transmission.
- Such a transmission is made using a message which is addressed only to the relevant luminaire la-d, 2a-e and which is only processed by this luminaire la-d, 2a-e and ignored by the other luminaires la-d, 2a-e.
- an individually controllable luminaire la-d, 2a-e may react to both the occupancy messages and the control commands of the associated UI element 4.
- the lighting level of the luminaire la-d, 2a-e may be determined by the last command received, which may be an occupancy message or a control command of the UI element 4.
- a luminaire la-d, 2a-e may be configurable such that it only reacts to the control commands for a certain period of time and returns to its previous lighting level set before receipt of the command or to a predefined default lighting level upon the expiration of the time period.
- the desired synchronization of the luminaires la-d, 2a-e in groups is only achieved, when the luminaires la-d, 2a-e correctly receive and process the occupancy messages.
- this will not always be the case, particularly because individual luminaires la-d, 2a-e may not correctly receive each occupancy message due to routing failures in the communication network or due to other reasons.
- an undesired de-synchronization of the luminaires la-d, 2a-e may occur.
- the luminaire Id evaluates status messages received from other luminaires la-c, 2a-e.
- the status message originating from a particular luminaire la-c, 2a-e includes status information indicating a current status of this luminaire la-c, 2a-e.
- the status information indicates the current lighting level of the luminaire la-c, 2a-e.
- the status message originating from a particular luminaire la-c, 2a-e includes trigger information about a trigger that prompted the luminaire la-c, 2a-e to adopt the current status including the current lighting level.
- the trigger information for a luminaire la-c, 2a-e is particularly indicative of whether the trigger for the luminaire la-c, 2a-e relates to all luminaires la-c, 2a-e of its group or is only valid for the respective luminaire la-c, 2a-e, and it preferably also specifies the reason for the trigger. Possible exemplary trigger reasons that may be specified in the trigger information include:
- a further trigger reason may be assigned to this change, which specifies that the luminaire la-d, 2a-e has corrected its status.
- the aforementioned trigger reasons are often also indicative of whether the trigger relates to all luminaires la-c, 2a-e of a group or only to an individual luminaire la-c, 2a-e. So, local and neighboring occupancies are trigger reasons relating to a whole group of luminaires la-c, 2a-e while an individual control is a trigger reason only relating to a single luminaire 1-ac, 2a-e. Therefore, the trigger information may not necessarily include further data indicating whether the trigger relates to all luminaires la- c, 2a-e of a group or to an individual luminaire.
- the trigger information may optionally further indicate a reception mode of the command and/or message that prompted the luminaire la-c, 2a-e to adopt the current status, where possible reception modes include (a) “Internal generation”: An internal generation of the command setting the current status (e.g. in response to an input to an internal UI element 4 or a detection signal of an internal occupancy sensor 3),
- the reception mode may likewise be considered in order to determine a desynchronization of a luminaire.
- This is particularly advantageous in lighting systems in which the trigger reason alone is not always indicative of whether the trigger relates to all luminaires la-c, 2a-e of a group or only to an individual luminaire la-c, 2a-e.
- this may be the case in a lighting system, in which the luminaires la-c, 2a-e can be controlled using manual control commands which override control commands received from occupancy sensors 3 and which can be addressed either to an individual luminaire la-c, 2a-e via unicast transmission or to a whole group of luminaires la-c, 2a-e via groupcast transmission.
- the trigger reason “manual override” is not indicative of whether the trigger relates to all luminaires la-c, 2a-e of a group or only to an individual luminaire la-c, 2a-e and the reception mode may additionally be taken into consideration in order to determine whether the trigger relates to all luminaires la-c, 2a-e of a group or only to an individual luminaire la- c, 2a-e.
- a status message originating from a particular luminaire la-c, 2a-e may indicate the group to which the luminaire la-c, 2a-e belongs.
- the luminaire Id may retrieve them from the other luminaires la-c, 2a-e b by sending one or more polling messages, which the other luminaires la-c, 2a-e answer by sending the status messages.
- the status messages may be retrieved upon the expiration of a predefined time period from the last correct receipt of an occupancy message and/or in predefined intervals, for example.
- the luminaire Id firstly evaluates the status messages from the other luminaires la-c of its own group 1 and optionally evaluates the status messages from the luminaires 2a-e of the other group 2 under certain conditions.
- the luminaire Id may firstly retrieve status messages only from the luminaires la-c of its own group 1, and it may then optionally retrieve status messages from the luminaires 2a-e of the other group 2, if required.
- the luminaire Id may send a polling message to the luminaires la-c, 2a-e of the respective group via a groupcast transmission.
- the luminaire 2c may only send one polling message to all luminaires la-c, 2a- e via a broadcast transmission and firstly store the status messages received from the luminaires 2a-e of group 2 without a further processing. These status messages may then be evaluated later, if necessary; or they may be discarded. In both implementations, i.e. in case of groupcast and broadcast transmissions of the polling messages, the status messages may be sent by other luminaires la-c, 2a-e via a unicast transmission to the luminaire Id that sent the polling message.
- the broadcast transmission of the polling message can result in unnecessary transmissions of status messages.
- a broadcast transmission is also possible if the luminaire Id does not know the groupcast addresses for groupcast transmissions to the luminaires la-c of its own group 1 and the luminaires 2a-e of the neighboring group 2. Therefore, a groupcast transmission of the polling messages may be preferred in case the luminaires la-d, 2a-e dispose of the groupcast addresses of their own group and the neighboring group. Otherwise, the polling messages may be sent via broadcast transmission.
- the luminaire Id Upon having received at least the status messages of the other luminaires la-c of its own group 1 (step 201), the luminaire Id checks whether all status messages include identical status information and whether the status indicated in the status information equal its own status (step 202). In particular, the luminaire Id checks whether the current lighting levels of the other luminaires la-c of its own group 1 are identical and equal to its own current lighting level. If this is the case, the luminaire Id determines that it is synchronized with the other luminaires of its group 1 and the procedure ends (step 203).
- the luminaire Id determines in step 202 that the status of the other luminaires la-c of its own group 1 are not identical and/or that its own status is not equal to the status of the other luminaires la-c of its own group 1, it proceeds with evaluation of the trigger information included in the status messages received from the luminaires la-c of its own group 1. On the basis of this evaluation, the luminaire Id selects the status messages which are further processed to detect a de-synchronization with the other luminaires la-c of its group 1 and to correct the de-synchronization, if necessary. In particular, it selects the status messages that do not include trigger information indicating a trigger that is only valid for the luminaire la-c having sent the relevant status information (step 204). The luminaires la-c which have adapted their current status in response to such a trigger are intentionally not synchronized with the other luminaires la-d of their group. Therefore, their status messages are ignored in the detection and correction of a de-synchronization.
- the evaluation of the status information comprises that the luminaire Id checks whether the status messages received from the other luminaires la-c of its own group 1 include trigger information indicating an “individual control” as trigger reason and/or a “unicast” reception mode.
- trigger information is indicative of a trigger that is only valid for the luminaire la-c having sent the respective status messages. Therefore, the luminaire Id ignores the status messages including such trigger information in the further procedure, and only the status messages not including such trigger information are selected for the further processing.
- the luminaire Id evaluates the status message selected in the preceding step. In so doing, it may particularly evaluate the status information included in the status messages and may compare the indicated status with its own status.
- This may comprise a check whether the status messages include identical status information and whether the status indicated therein is equal to its own status (step 205).
- the luminaire Id may check whether the lighting levels indicated in the selected messages are identical and equal to its own current lighting level. If this is the case, the luminaire Id determines that it is synchronized with the other luminaires la-c of its group 1, which are not individually controlled, and the procedure ends (step 206).
- the luminaire Id may check in the next step whether a number of the selected status messages, which is greater than a predefined threshold, indicate identical status, particularly identical lighting levels (step 207).
- the predefined threshold may correspond to a predefined percentage of the selected status messages, which is preferably greater than 50 % and which may particularly be between 55 % and 70 %.
- the luminaire Id may additionally check in an optional configuration, whether all of these status messages or a subset thereof, which still includes a number of status messages greater than the threshold, indicates trigger reasons corresponding to each other.
- trigger reasons may be regarded as corresponding to each other if they are identical or if they do not conflict with each other. This may particularly be the case if they can coexist in a group of synchronized luminaires la-c, 2a-e.
- Trigger reasons corresponding to each other may particularly be assumed when one status message indicates a correction of the status as trigger reason. This trigger reason may be regarded as corresponding to a trigger reason indicating a local or neighboring occupancy.
- the luminaire Id determines in step 207 that a number of the selected status messages above the predefined threshold include identical status information, particularly identical lighting levels, and optionally also trigger reasons, which correspond to each other, the luminaire Id compares its own status to the status indicated in the relevant status messages and changes its status to the indicated status if there is a discrepancy (step 208). In particular, the luminaire Id compares its lighting level with the lighting level indicated in these status messages and changes its lighting level to the indicated lighting in case of a discrepancy. This behavior of the luminaire Id is due to the fact that there is a high likelihood that the identical status indicated in the relevant status messages corresponds to the correct status desired for the jointly controlled luminaires la-d.
- the desired status for the luminaire Id can be correctly determined with an even higher likelihood.
- the luminaire Id may further memorize the correction as a trigger reason for the change - this trigger reason is included in status messages sent by the luminaire Id to other luminaires la- c, 2a-e upon the change. Thereupon, the procedure ends.
- the current lighting level of the luminaire Id is Y
- the aforementioned threshold is 60 %
- status messages received by the luminaire Id from the other luminaires of group 1 include the following status and trigger information:
- the luminaire Id selects all status messages for a further processing in step 204 of the procedure and determines in step 207 that more than 60 % of the selected status messages indicate the identical lighting level Y. Since this lighting level is identical to its own lighting level, the luminaire Id does not have to change its own lighting level in step 208 and the procedure ends without such a change.
- the luminaire Id again selects ah status messages for a further processing in step 204 of the procedure. Further, it determines in step 207 that more than 60 % of the selected status messages indicate the identical lighting level X. Since this lighting level differs from its own lighting level, the luminaire Id changes its own lighting level to the lighting level X in step 208.
- step 207 it will be appreciated that there will not always be a number of the selected status messages above the predefined threshold, which include identical status information. If the luminaire Id determines in step 207 that this is not the case, the procedure may be aborted in one embodiment. Thereupon, it may be repeated at a later time. Since the other luminaires la-c of the group 1 also perform the procedure for detecting and correcting a de-synchronization, one or more of them may have corrected their status at a later time so that the procedure may lead to a different (better) result for the luminaire Id.
- the luminaire Id may evaluate status messages from the luminaires 2a-e of the neighboring group 2 in the next steps of the procedure, if the check in step 207 is not affirmative. As described above, these status messages may be newly retrieved for this purpose or they may have been retrieved previously together with the status messages from the luminaires la-c of the group 1. In the evaluation of the status messages from the luminaires 2a-e of the neighboring group 2, the luminaire Id may again select those status messages that do not include trigger information indicating a trigger that is only valid for the luminaire 2a-e having sent the relevant status information (step 209). This selection may be made in a way already described above in connection with step 204 with respect to the status messages received form the luminaires la-c of the own group of luminaire Id.
- the luminaire Id may check whether a number of selected status messages from the luminaires la-c, 2a-e of the neighboring group 2, which is greater than a predetermined threshold, include identical status information and, optionally, trigger reasons corresponding to each other in step 210, where corresponding trigger reasons are determined in a similar way as described above.
- the luminaire Id may check whether a number of selected status messages from its own group 1 and the neighboring group 2, which is greater than a predetermined threshold, include trigger information agreeing with each other, particularly corresponding trigger reasons agreeing with each other.
- trigger information may have to be identical in order to be regarded as agreeing with each other.
- trigger reasons which do not conflict with each other, may be regarded as agreeing with to each other, as described above with respect to the correspondence of trigger reasons.
- the trigger reasons do not have to be identical in order to be regarded as agreeing with each other.
- the included trigger information has to be in agreement in order for them to be regarded as corresponding to each other. This is particularly the case for status messages from luminaires la-d, 2a-e of one group, which indicate the trigger reason “local occupancy”, and status messages la-d, 2a-e of the other group, which indicate the trigger reason “neighboring occupancy”.
- the luminaire Id determines trigger information relating to its own group on the basis of the trigger information included in the relevant status messages and derives a status, particularly a lighting level, from the determined trigger information using the predefined rule (step 211). If the relevant status messages received from the luminaires la-c of its own group 1 include the trigger reason “local occupancy” and the relevant status messages received from the luminaires 2a-e of the other group 2 include the trigger reason “neighboring occupancy”, the luminaire Id particularly determines the trigger reason “local occupancy” in step 211 and derives a lighting level of value X from this trigger reason.
- the luminaire Id particularly determines the trigger reason “neighboring occupancy” in step 211 and derives a lighting level of value Y from this trigger reason.
- the luminaire compares the derived status with its own current status and changes its status to the derived status in case of a discrepancy (step 212).
- the luminaire Id may again memorize the correction as a trigger reason for the change - so that this trigger reason is included in status messages sent by the luminaire Id to other luminaires la-c, 2a-e upon the change. Then, the procedure ends.
- step 210 the procedure ends without a change of the status of the luminaire Id (step 213). As described above, it may be repeated at a later time. When one or more of luminaires la-d, 2a-e may have corrected their status at that time, the repeated procedure may lead to a different (better) result for the luminaire Id.
- a single unit or device may fulfill the functions of several items recited in the claims.
- the mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.
- a computer program may be stored/distributed on a suitable medium, such as an optical storage medium or a solid-state medium, supplied together with or as part of other hardware, but may also be distributed in other forms, such as via the Internet or other wired or wireless telecommunication systems.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Circuit Arrangement For Electric Light Sources In General (AREA)
Abstract
Description
Claims
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| IN202041025483 | 2020-06-17 | ||
| EP20192897 | 2020-08-26 | ||
| PCT/EP2021/065764 WO2021254898A1 (en) | 2020-06-17 | 2021-06-11 | Detection and correction of a de-synchronization of a luminaire |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| EP4169357A1 true EP4169357A1 (en) | 2023-04-26 |
| EP4169357B1 EP4169357B1 (en) | 2025-03-19 |
Family
ID=76355519
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| EP21731184.4A Active EP4169357B1 (en) | 2020-06-17 | 2021-06-11 | Detection and correction of a de-synchronization of a luminaire |
Country Status (4)
| Country | Link |
|---|---|
| US (1) | US12114406B2 (en) |
| EP (1) | EP4169357B1 (en) |
| CN (1) | CN115943733A (en) |
| WO (1) | WO2021254898A1 (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| FI4236629T3 (en) * | 2022-02-25 | 2026-03-24 | Helvar Oy Ab | Lighting control |
| US12477639B2 (en) * | 2023-03-30 | 2025-11-18 | Electronic Arts Inc. | System and methods for automated light rigging in virtual interactive environments |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2754195C (en) * | 2009-03-06 | 2018-01-02 | Koninklijke Philips Electronics N.V. | Automatically configuring of a lighting |
| US9930741B2 (en) | 2015-02-27 | 2018-03-27 | Xicato, Inc. | Synchronized light control over a wireless network |
| GB2542806B (en) | 2015-09-30 | 2021-07-21 | Tridonic Gmbh & Co Kg | Lighting state synchronization |
| EP3300459B1 (en) | 2016-09-21 | 2019-08-28 | Helvar Oy Ab | Method and arrangement for controlling lighting based on user tracking |
| US10405404B1 (en) | 2018-11-12 | 2019-09-03 | Abl Ip Holding Llc | Lighting controls data synchronization |
| US11902874B2 (en) * | 2019-02-15 | 2024-02-13 | Signify Holding B.V. | Determining a network route which avoids nodes with a RF-based presence and/or location detection function |
| EP4111146B1 (en) * | 2020-02-24 | 2023-11-15 | Signify Holding B.V. | Selection criteria for passive sound sensing in a lighting iot network |
| EP4324300A1 (en) * | 2021-04-12 | 2024-02-21 | Appleton Grp LLC | Providing industrial network reliability using luminaires |
| US12156313B2 (en) * | 2021-12-22 | 2024-11-26 | Appleton Grp Llc | Controlling networked dimmable luminaires based on energy consumption |
-
2021
- 2021-06-11 EP EP21731184.4A patent/EP4169357B1/en active Active
- 2021-06-11 US US17/928,047 patent/US12114406B2/en active Active
- 2021-06-11 WO PCT/EP2021/065764 patent/WO2021254898A1/en not_active Ceased
- 2021-06-11 CN CN202180043107.2A patent/CN115943733A/en active Pending
Also Published As
| Publication number | Publication date |
|---|---|
| WO2021254898A1 (en) | 2021-12-23 |
| US20230284359A1 (en) | 2023-09-07 |
| US12114406B2 (en) | 2024-10-08 |
| CN115943733A (en) | 2023-04-07 |
| EP4169357B1 (en) | 2025-03-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20220345363A1 (en) | Commissioning and controlling load control devices | |
| CN108432282B (en) | Method and apparatus for managing electronic devices through wireless communication | |
| US8536984B2 (en) | Method of semi-automatic ballast replacement | |
| US9220151B2 (en) | Method for controlling a lighting system, and lighting system | |
| EP3245763B1 (en) | Adaptive recovery from node failures in a network system | |
| US20150084547A1 (en) | DALI commissioning tools and methods for implementing | |
| US12114406B2 (en) | Detection and correction of a de-synchronization of a luminaire | |
| KR20180037180A (en) | Smart home system | |
| US10728991B1 (en) | Fixture grouping and configuration in distributed lighting systems | |
| US11546874B1 (en) | Systems and methods for reducing network traffic | |
| US11678296B1 (en) | Systems and methods for controlling nodes of a wireless network in response to sensed events | |
| EP4066450B1 (en) | A networked system, having a controlling device and a plurality of controlled devices, and devices and methods used by the system | |
| US20230199611A1 (en) | Positioning routers of a network around noise sources | |
| US11284476B1 (en) | Systems and methods for commissioning nodes of a wireless network | |
| US20160192241A1 (en) | Establishing method for self-organization network of wireless nodes | |
| EP4095819A1 (en) | Alarm system and alarm device | |
| HK40088887A (en) | Automatic adjustment of a discovery range for discovering wireless control devices | |
| HK40066154A (en) | Commissioning and controlling load control devices | |
| EP4136807A1 (en) | Network node for operation under non-availability of application control hub | |
| HK40066154B (en) | Commissioning and controlling load control devices | |
| HK40066150A (en) | Commissioning and controlling load control devices | |
| JP2000115101A (en) | Studio control system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: UNKNOWN |
|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE |
|
| PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
| 17P | Request for examination filed |
Effective date: 20230117 |
|
| AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
| DAV | Request for validation of the european patent (deleted) | ||
| DAX | Request for extension of the european patent (deleted) | ||
| GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
| INTG | Intention to grant announced |
Effective date: 20241009 |
|
| P01 | Opt-out of the competence of the unified patent court (upc) registered |
Free format text: CASE NUMBER: APP_65461/2024 Effective date: 20241211 |
|
| GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
| GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE PATENT HAS BEEN GRANTED |
|
| AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
| REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
| REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
| REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602021027817 Country of ref document: DE |
|
| REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: RS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250619 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250319 |
|
| PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20250617 Year of fee payment: 5 |
|
| REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG9D |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: NO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250619 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: HR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250319 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250319 |
|
| PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20250624 Year of fee payment: 5 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250319 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250620 |
|
| REG | Reference to a national code |
Ref country code: NL Ref legal event code: MP Effective date: 20250319 |
|
| REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 1778059 Country of ref document: AT Kind code of ref document: T Effective date: 20250319 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250319 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250319 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SM Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250319 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250319 Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250721 |
|
| PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20250827 Year of fee payment: 5 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250319 Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250319 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250319 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250319 Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250319 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250319 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250319 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250719 |
|
| REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602021027817 Country of ref document: DE |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250319 |
|
| PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
| REG | Reference to a national code |
Ref country code: CH Ref legal event code: H13 Free format text: ST27 STATUS EVENT CODE: U-0-0-H10-H13 (AS PROVIDED BY THE NATIONAL OFFICE) Effective date: 20260127 |
|
| REG | Reference to a national code |
Ref country code: CH Ref legal event code: L10 Free format text: ST27 STATUS EVENT CODE: U-0-0-L10-L00 (AS PROVIDED BY THE NATIONAL OFFICE) Effective date: 20260128 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20250319 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20250611 |
|
| 26N | No opposition filed |
Effective date: 20251222 |
|
| REG | Reference to a national code |
Ref country code: BE Ref legal event code: MM Effective date: 20250630 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20250611 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20250630 |
|
| PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20250630 |