EP3378286B1 - Appareil ballast pour moyen d'éclairage avec microprocesseur et interface de programmation - Google Patents

Appareil ballast pour moyen d'éclairage avec microprocesseur et interface de programmation Download PDF

Info

Publication number
EP3378286B1
EP3378286B1 EP16797910.3A EP16797910A EP3378286B1 EP 3378286 B1 EP3378286 B1 EP 3378286B1 EP 16797910 A EP16797910 A EP 16797910A EP 3378286 B1 EP3378286 B1 EP 3378286B1
Authority
EP
European Patent Office
Prior art keywords
interface
microprocessor
application software
programming interface
ballast
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.)
Active
Application number
EP16797910.3A
Other languages
German (de)
English (en)
Other versions
EP3378286A1 (fr
Inventor
Markus Mayerhofer
Frank Lochmann
Florian Moosmann
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tridonic GmbH and Co KG
Original Assignee
Tridonic GmbH and Co KG
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Tridonic GmbH and Co KG filed Critical Tridonic GmbH and Co KG
Priority to EP24153076.5A priority Critical patent/EP4355033A3/fr
Priority to EP21201386.6A priority patent/EP3955705B1/fr
Publication of EP3378286A1 publication Critical patent/EP3378286A1/fr
Application granted granted Critical
Publication of EP3378286B1 publication Critical patent/EP3378286B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

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
    • 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/165—Controlling the light source following a pre-assigned programmed sequence; Logic control [LC]
    • 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/18—Controlling the light source by remote control via data-bus 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/19—Controlling the light source by remote control via wireless transmission

Definitions

  • the invention relates to a ballast for at least one light source and in particular an LED that can be largely and essentially freely configured by a user.
  • the document DE 10 2014 200 297 A1 shows a control gear and a communication adapter for outdoor lighting systems. In particular, the transfer of configuration data via one of several interfaces is shown.
  • the document US 2012/0086345 A1 shows a lighting system in which various components of the lighting system communicate with one another by means of encrypted optical signals.
  • the document U.S. 2015/0257229 A1 shows a lighting system in which the various components of the lighting system communicate with one another by means of encrypted wireless radio communication.
  • the ballast has a programmable Microprocessor that has a relatively large computing power and in different ways, ie can communicate with the aid of a variety of interfaces.
  • a DALI, SPI, DSI, WLAN, Bluetooth, LAN or USB interface can be provided for this purpose.
  • Both sensors and signal transmitters can be connected to the ballast, and the microprocessor is connected to the interfaces in order, for example, to also evaluate sensor signals and signals from signal transmitters. Based on incoming signals from sensors and/or signal transmitters, or signals coming in via the interfaces, the microprocessor can then, for example, change the operating properties of the ballast and thus, for example, influence the light emission or other functionalities of the ballast. Communication with external communication partners is possible, for example, via LAN, Bluetooth, USB, DALI, WLAN, ....
  • the ballast has a programming interface via which application software can be transmitted to a memory unit provided in the ballast.
  • This is a software and/or software component that can be executed and run by the microprocessor and that can be part of a firmware and/or the operating system or can be executed by it.
  • the application software is then executed, inter alia, by the microprocessor.
  • the operating system manages in particular a memory area divided into a user area ("user space") and a Operating system core area (“kernel space”) can be divided. This division serves to allow protection of parts of the memory area.
  • the operating system kernel area is then reserved for executing the operating system kernel, while the user area is provided for executing application software and/or drivers for interfaces and/or devices connected to the microprocessor.
  • the memory area can be part of a memory provided by the memory unit.
  • a user can influence and define the manner in which the ballast behaves, or how, for example, signals from sensors or signal transmitters are evaluated and used to control the at least one light source will. It can also be configured how an evaluation for controlling components connected to the ballast via the interfaces is processed. In particular, the evaluation and processing of input signals can be configured or changed by means of the application software and, in particular, lighting control can be defined as a function of detected signals.
  • the invention thus provides a ballast and a luminaire according to the independent claims. Developments of the invention are the subject matter of the dependent claims.
  • a microprocessor 2 is therefore provided in the ballast V, which microprocessor is connected to at least one memory unit 3 so that it can access the memory unit 3 and read data from there and write data to it.
  • the microprocessor 2 (e.g. ARM Cortex-A5x, ARM Cortex-A7x, ...) is preferably provided on a circuit board 1, which preferably has at least one edge, and on which the memory unit 3 can also be mounted.
  • the microprocessor 2 and/or the memory unit 3 can also be provided on a separate circuit board which is connected to the circuit board 1, for example by means of a socket connection.
  • the board has a programming interface P on the at least one edge and at least one signaling interface S, which can also be attached to the at least one edge of the board, but also to another edge of the board.
  • At least the programming interface P is accessible from outside the ballast.
  • the programming interface for a wired or set up wireless communication.
  • the programming interface P can be a radio interface (Bluetooth, WLAN, ZigBee, RFID, ...) or a wired (parallel, RS323, USB, JTAG, GPIO, ...) interface. It is therefore not always necessary for the programming interface P to be exposed to the outside, for example. Rather, for example, the programming interface P can also be accessed inductively from the outside in order, for example, to transmit data from a programming device 4 to the memory unit 3 and/or the microprocessor 2 by means of the programming interface P. This ensures that the ballast V can be designed to suit its place of use and can have a prescribed degree of protection (International Protection Code (IP) certification), for example.
  • IP International Protection Code
  • the programming interface P can be exposed to the outside.
  • the programming interface P can thus be accessed by means of a wired connection.
  • a programming device 4 can thus be connected to the programming interface P by means of a cable and data can be transmitted to or from the memory unit 3 and/or the microprocessor 2 .
  • Data transmitted via the programming interface P can be used to configure the microprocessor 2 or its information processing.
  • application software A also called “app” can be transferred to or into the storage unit will.
  • This application software A is then executed by the microprocessor 2, it being understood that the microprocessor 2 can also execute a large number of application software components.
  • the programming interface P and the signaling interface S can, for example, also use the same hardware and only be separated in terms of software.
  • the application software A stored in the memory unit 3 and executed by the microprocessor 2 can then influence one of the following functionalities of the ballast V: For example, the interaction or the evaluation of sensor data supplied by sensors interacting with the ballast V can be defined or changed. In particular, the sensors can transmit signals via the signaling interface S to the ballast. These signals are then evaluated by the at least one application software A and processed according to a definition specified by the application software A.
  • the application software A can also be used to specify how the ballast V interacts with the connected signal sources (sensors, signal transmitters, ). In particular, it can be determined which signals are evaluated or processed and with which type of signal generator the ballast V works together. In this way, the signal sources can be defined whose signals are evaluated at all. Signal sources or interfaces can also be blocked or released and it is possible, for example, that the range of functions of the ballast V can be expanded or restricted in this way.
  • the at least one application software A can also influence the controller with which the ballast V controls the at least one light source, for example.
  • the lighting means can thus be controlled by the application software A, in particular depending on the incoming signals from the signal sources.
  • an application software A which is stored in the memory unit 3 of the ballast V, can of course also change the evaluation of the signals.
  • the application software A can also be used to change the functionality provided by the ballast Vv, and In particular, provided interfaces can be activated or deactivated. The range of functions of the ballast V can also be controlled in this way.
  • communication protocols that are provided for communication between the ballast and communication partners, for example other ballasts, operating devices or central control units, can be activated or deactivated. In this way, the ballast V can be adapted for different application scenarios, for example by only requiring individual communication protocols.
  • the functionality of the ballast V can also be expanded if additional communication protocols need to be added or deactivated. This can be the case, for example, if the application scenario for the ballast changes. Overall, the application software therefore allows the operating data and/or operating parameters of the ballast V to be recorded, defined, evaluated and changed.
  • the at least one application software A in the memory unit 3 can also be updated and changed. This can then also be done via the programming interface P.
  • more than one application software A it is possible for more than one application software A to be stored in the memory unit 3 and executed by the microprocessor.
  • additional features of the ballast V can be activated or deactivated. For example, it is possible that an application only provides a basic functionality, while another application software A additional functionalities of the ballast V deactivated or activated.
  • the application software A can also provide or change an application programming interface. This application programming interface can then be used to add further software components to the application software, which also relate to functionalities of the ballast, and in particular to activate or deactivate functions.
  • the microprocessor 2 preferably executes a hardware abstraction subsystem (HAL, Hardware Abstraction Layer).
  • HAL Hardware Abstraction Layer
  • the application software then preferably accesses the programming interface and/or the signaling interface via the hardware abstraction subsystem.
  • the programming interface can be a wireless or wired interface.
  • the signaling interface S can likewise be a DALI or DSI, SPI or I 2 C interface.
  • the programming interface P can also be designed in such a way that programming or the transmission of application software is initially not possible.
  • a programming interface that is initially blocked in this way can require that a code or an activation key, for example a cryptographic key, must first be transmitted to the ballast in order to activate the programming interface P.
  • the programming interface P can only be activated (for example for a predetermined period of time) if a corresponding activation of the programming interface P has taken place.
  • the application software can also be transmitted in encrypted form via the programming interface, with the ballast having a first code or activation key, eg a cryptographic key, which is stored in the ballast.
  • this first code or activation key is a public key that can be used to decrypt the application software transmitted on the programming interface.
  • this first code or activation key eg cryptographic key
  • the programmer may have a second code or activation key, eg cryptographic key, which is a type of private key and which preferably can be used for both encryption and decryption.
  • the programming device can enable encrypted transmission of the application software via the programming interface, with the ballast being able to receive and read out this encrypted application software.
  • the programming interface p can only be activated if, for example, a programming device 4 is positioned at a certain distance from the programming interface P or is connected to the programming interface P.
  • the programming device 4 can then automatically receive an identifier or a key via the programming interface P transmitted to the microprocessor 2, which is recognized by this (e.g. using NFC).
  • the microprocessor 2 can then allow data to be transferred to the memory unit 3 and thus enable the programming interface P to be activated.
  • the ballast V can also have wired and/or wireless communication interfaces in order to communicate with other ballasts or operating devices, for example. These communication interfaces are attached to an edge of the circuit board, for example.
  • the ballast V can have a converter interface via which one or more other ballasts or converters can be connected to the ballast.
  • the application software A or the microprocessor 2 can thus control one or more other ballasts or converters connected to the ballast V.
  • the microprocessor 2 is in particular a single-chip system (system on a chip, SoC).
  • SoC system on a chip
  • the shape of the circuit board 1 essentially corresponds to an n-corner. Alternatively, a round or oval shape would also be possible.
  • the circuit board can be essentially rectangular, triangular or trapezoidal in shape, and the interfaces provided can be arranged along the edges of the circuit board 1 accordingly.
  • the microprocessor 2 with the memory unit 3 can be connected wirelessly or by wire to the circuit board.
  • FIG. 1 shows a circuit board 1 of a ballast V, on which a microprocessor 2 and a memory unit 3 are arranged.
  • the essentially trapezoidal design of the circuit board 1 shown as an example has four edges which are labeled a, b, c and d.
  • Different interfaces can now be attached to the edges a, b, c, d of the circuit board 1, which can also be assigned to different functional groups.
  • the interfaces on a first edge a can be set up for communication with other ballasts (converters) or other participants in a lighting system.
  • interfaces are shown as examples, which are designed, for example, as a communication interface for communication using DALI, SPI and/or I 2 C (inter-integrated circuit) buses/protocols.
  • interfaces for communication with control units can be provided on a second edge b.
  • a DALI, a Bluetooth (Bluetooth Low Energy, BLE) and a LAN interface are shown as examples on the second edge.
  • An interface P is provided at a third edge c.
  • the interface P is preferably the programming interface. As already mentioned, this can be protected against access by mechanical or software-related measures, or can be activated selectively.
  • a programming device 4 is also shown as an example, from which at least one application software A can be transmitted to and/or from the interface P, which is can also be a Bluetooth (e.g. BLE) interface.
  • interfaces are provided on a fourth edge d, which are used, for example, to connect sensors and/or other hardware that is to be connected to the ballast.
  • a WLAN or WiFi
  • a USB or a serial RS232 interface
  • These can, for example, enable communication with a microphone arrangement 5, a moisture sensor 6 and/or a presence sensor 7.
  • the sensors can be active or passive.
  • the programming interface P and the signaling interface S can, for example, also use the same hardware and only be separated in terms of software.
  • the signaling interface S can be used for the encrypted transmission of the application software A, with this encrypted transmission forming the programming interface P in this case.
  • the signaling interface S is also used for encrypted transmission of the application software A and thus also forms the programming interface P.
  • the signaling interface S and the programming interface P use the same hardware as infrastructure, but are separate in terms of software.
  • the programming interface P can use the signaling interface S for data traffic, in particular for the transmission of the application software A.
  • the ballast V can have a first code or Activation key, eg cryptographic key, have that is stored in the V ballast.
  • this first code or activation key eg cryptographic key
  • this first code or activation key is a public key which can be used to decrypt the application software A transmitted on the programming interface P.
  • the programmer may have a second code or activation key, eg cryptographic key, which is a type of private key and which preferably can be used for both encryption and decryption.
  • the programming device can enable encrypted transmission of the application software A via the programming interface P, with the ballast being able to receive and read out this encrypted application software.
  • the application software A can be transmitted via the programming interface P in individual packages.
  • these packets can each be provided with a port address.
  • the packets with the port address can be received by the ballast V and assigned to the appropriate port within the ballast.
  • the individual packets can be transmitted via the programming interface P in encrypted form.
  • the ballast V can receive the encrypted packets and be assigned to the appropriate port according to their port address.
  • In 1 is also another ballast (also Converter called) or at least one other participant of a lighting system 8 shown, which can be communicatively connected to one of the interfaces on the first edge a.
  • the interfaces at edge a can also be referred to as converter interfaces.
  • a coupling element 9 eg a switch or router
  • a time control circuit 10 or time switch can also be connected to one of the interfaces on the second edge b.
  • communication with a remote control 11 via radio or infrared and corresponding interfaces is also possible.
  • the signaling interface is labeled S as an example. In principle, any interface that is different from the programming interface is to be regarded as the signaling interface S.
  • the circuit board 1 does not have to be a regular geometric body.
  • the interfaces arranged on the at least one edge can also be arranged one above the other in the manner of a pyramid.
  • a further interface arranged above/below an interface can be arranged slightly offset to the inside of the circuit board 1 .
  • the programming interface can be protected against misuse in that it can be separated in terms of hardware and/or secured cryptographically.
  • the signaling interface S can be used to connect switches, timers, remote controls, etc.
  • a separate interface can be provided for other signal transmitters such as sensors (motion sensor, brightness sensor, humidity sensor, microphones, presence sensor, etc.). However, the corresponding signals can also be fed to the signaling interface.
  • the signaling interface S and optionally other further interfaces is preferably a USB interface, I2C interface or also a DALI interface.
  • the microprocessor 2 can provide suitable microprocessor interfaces for connecting the interfaces.
  • the processing by the microprocessor 2 can be configured via the application software A, as explained above, and this can thus change the ballast V and in particular a lighting system or its functionality. It is thus possible for a user to create application software A, which then enables specific functionalities of the ballast V.
  • the at least one application software A can then be used independently of an implementation of the interfaces and configurations used.
  • the microprocessor can be connected to another ballast or converter via a fourth interface. This interface can be in the form of a DALI, SPI or I 2 C interface.
  • the microprocessor can also be integrated in the additional ballast or converter.
  • the ballast V can only have a single signaling interface S in terms of hardware, which at the same time forms further interfaces in terms of software.
  • the programming device 4, a microphone arrangement 5, a moisture sensor 6 and/or a presence sensor 7 can be connected to the signaling interface S.
  • further subscribers T such as further ballasts of a lighting system, for example the lighting system 8, can be connected to the signaling interface S.
  • a coupling element 9 can be connected to the signaling interface S in addition or as an alternative.
  • a time control circuit 10 or time switch and/or a remote control 11 can be connected to the signaling interface S.
  • the signaling interface S can form the programming interface P at the same time.
  • the signaling interface S can be formed by a LAN interface or WLAN interface, which at the same time Programming interface P forms.
  • the ballast V can also have an I2C interface, for example to forward the data transmitted via the LAN interface or WLAN interface to other participants connected to the I2C interface, such as other ballasts and/or sensors. It would be possible for both the LAN interface or WLAN interface and the I2C interface to form the signaling interface S, which forms the programming interface P at the same time.
  • ballast V can also have a DALI interface in order, for example, to communicate with DALI sensors and/or DALI ballasts connected there.
  • the ballast V can have a signaling interface S and for at least one additional interface to be hardware-based in order to connect additional participants who cannot communicate using a protocol of the signaling interface S.
  • the signaling interface S can be formed by a LAN interface or WLAN interface, which forms the programming interface P at the same time.
  • the ballast V can have a DALI interface, for example with DALI sensors connected there and / or to communicate with DALI ballasts.
  • FIG. 2 shows an example of a way in which the microprocessor 2 communicates with one or more ballasts 20, 21, 22, 23.
  • Figure 2a shows a lamp 24 with a ballast 20, which has the microprocessor 2 and the memory unit 3.
  • the ballast 20 corresponds to the ballast V der 1 or the other examples.
  • the memory unit 3 can be integrated into the microprocessor 2, for example.
  • the microprocessor 2 and the memory unit 3 are preferably arranged within the ballast 20 . However, it would also be possible for the microprocessor 2 and the memory unit 3 to be arranged outside the ballast 20 but inside the lamp 24 . At least there is a connection of the microprocessor 2 to the ballast 20.
  • ballasts 21, 22, 23 of lights (not shown) are shown, each of which has only one converter but does not itself provide a microprocessor.
  • the various ballasts or converters can then communicate, for example, via a DALI bus or an I2C bus.
  • only one of the lights or one of the ballasts can be expanded using application software A.
  • the application software A can also determine the activation of the other ballasts (converters), so that, for example, depending on the configuration of the ballast (converter) 20, the application software A can carry out a situation- and site-specific configuration or such an operation.
  • ballasts can each have a microprocessor and a memory unit.
  • the multiple ballasts can be connected via a signaling interface S, which can simultaneously form the programming interface P, so that the application software A can be transmitted to multiple ballasts.
  • the microprocessor 2 does not necessarily have to be housed in a lamp or in a ballast, but can also be provided externally.
  • the microprocessor can be connected to a number of stations and in particular to a number of ballasts, converters or lights 25, 26, 27 in a network using the coupling element 9, the coupling element 9 being, for example, a gateway with a LAN interface, a WLAN router or a May be DALI bus master to which several ballasts, converters or lights 25, 26, 27 can be connected. Communication with the ballasts, converters or lights 25, 26, 27 can then take place digitally via the connection provided, for example by means of I2C, DALI or DSI protocol.
  • a microprocessor can also be provided in each ballast or in each lamp.
  • the coupling element 9 it would also be possible for the coupling element 9 to be designed in such a way that it has a LAN interface or WLAN interface.
  • This LAN interface or WLAN interface can form the signaling interface S.
  • the coupling element 9 can also have an I2C interface, for example via the LAN interface or WLAN interface forward the transmitted data to other participants connected to the I2C interface, such as a ballast V or ballast 20 and/or sensors. It would be possible for both the LAN interface or WLAN interface and the I2C interface to form the signaling interface S, which forms the programming interface P at the same time.
  • data received from the coupling element 9 via the LAN interface or WLAN interface can be passed on to the ballast V or ballast 20 connected there on the I2C interface.
  • a signaling interface S and at the same time a programming interface P can be formed, so that application software A that can be configured via the programming interface P can be run on the ballast V or 20 .
  • the coupling element 9 can also be designed to run the application software A.
  • the coupling element 9 can also have a DALI interface in order, for example, to communicate with DALI sensors and/or DALI ballasts connected there.
  • the application software A can be transmitted in individual packets via the programming interface P in the various exemplary embodiments.
  • these packets can each be provided with a port address.
  • the packets with the port address can be received by the microprocessor 2 of the ballast 20 and the corresponding port within of memory 3 can be assigned.
  • the individual packets can be transmitted via the programming interface P in encrypted form.
  • the microprocessor 2 of the ballast 20 can receive the encrypted packets and be assigned to the corresponding port of the memory unit 3 according to their port address.
  • operating data can be recorded, set and/or evaluated by the application software A in the ballast V or 20 and/or operating parameters can be recorded, set and/or evaluated and specified, for example a dimming/lighting level for a room and/or set a maximum/minimum operating temperature, or define when an incoming signal is evaluated as detecting occupancy in a room.
  • the limit and/or threshold values for a humidity, an air pressure, a CO 2 content or a noise level of the environment can be specified, when they are reached specific actions are then to be carried out by the application software.
  • the application software can specify, for example, that an image is recorded via a camera module when certain operating data or operating parameters (for example supplied by a presence sensor) exceed a threshold value or level.
  • a DALI interface, a Bluetooth interface, a LAN interface, a PLC interface and/or a USB interface can be provided as signaling interface S on the hardware side for communication.
  • the application software A can also specify how incoming signals are evaluated. For example, filters (noise filters, echo filters, etc.) can be applied to the signals. Parameters and evaluations can also be defined for specific application scenarios (e.g. large room with a large number of office room dividers (cubicles)) or picking situations. Also, for example, the room size in which an installation is to take place or the number of lights can be defined in an application software, which can then be selected or specified accordingly.
  • the application software A can also be used to run test programs.
  • the application software can be created in JAVA, PYTHON, PEARL, C, C++, C#, RUBY, GO,...
  • ballast mentioned above is representative of converters, sensors, lights and other participants in a lighting system.
  • the techniques, configurations and protocols specified for the interfaces are essentially interchangeable.
  • the interfaces can either be open to the outside or hidden. A selectively openable and closable cover of the respective interfaces is of course also possible.
  • circuit board 1 was described above primarily as being arranged in the ballast, it should be understood that the circuit board 1 can alternatively or additionally also be arranged in other participants and components of a lighting system, for example the lighting system 8 .
  • circuit board 1 can also be part of a sensor or an actuator.
  • An intelligent sensor IS is described below, which preferably includes circuit board 1 as described above. Consequently, the description of the ballast V and the 1 essentially also for the intelligent sensor IS.
  • the intelligent sensor IS can be connected to the BS lighting system.
  • the intelligent sensor IS can also be connected to a higher-level bus system (eg an IPv6 bus system, overlay network, . . . ) and can have a microprocessor 2, a memory unit 3 and, in particular, application software A.
  • the intelligent sensor IS can communicate with the microprocessor 2 in a wired or wireless manner (dashed double-headed arrow).
  • the microprocessor 2 does not necessarily have to be part of the intelligent sensor IS.
  • the intelligent sensor IS can read out and store data from a number of connected sensors NIS, which have no intelligence, ie in particular no microprocessor and memory, in a wired manner via a bus line BL or wirelessly. Read out data can be processed by the microprocessor 2.
  • the lighting system BS can also have other intelligent sensors and thus connect at least two sensors to one another.
  • the bus line BL can form the signaling interface S.
  • the programming interface P and the signaling interface S can use the same hardware and only be separated in terms of software.
  • the intelligent sensor IS can also specify or adopt functions and/or limit values for the non-intelligent sensors NIS or other intelligent sensors IS.
  • the intelligent sensor IS can control and/or configure one or more ballasts or converters depending on the data collected, e.g. from the non-intelligent sensors NIS and/or its own data.
  • the non-intelligent NIS sensors can be designed as simple motion detectors (e.g. PIR) or light sensors (e.g. LDR).
  • the intelligent sensor IS can be a thermal imaging camera. If a detection event is recorded by a non-intelligent sensor NIS, then this can transmit information to the intelligent sensor IS about the fact that a detection event has been recorded.
  • the application software A of the intelligent sensor IS can evaluate the transmitted information in an application-specific manner and, depending on this, control at least one other subscriber T of the lighting system BS, preferably a ballast or a converter.
  • the intelligent sensor IS and / or the non-intelligent sensors NIS can also be in one or several ballasts or converters can be integrated.

Landscapes

  • Circuit Arrangement For Electric Light Sources In General (AREA)

Claims (9)

  1. Appareil ballast (V) pour moyen d'éclairage, en particulier des DEL, présentant un microprocesseur (2) comprenant au moins une unité de mémoire (3) et une carte de circuit imprimé (1) et au moins une interface de programmation (P) et au moins une interface de signalisation (S),
    le microprocesseur (2) pouvant être configuré à travers l'interface de programmation (P) et
    au moins un logiciel d'application (A) exécutable par le microprocesseur (2) pouvant être transmis à travers l'interface de programmation (P), l'au moins un logiciel d'application (A) exécutable par le microprocesseur (2) étant mémorisé dans l'au moins une unité de mémoire (3), le logiciel d'application (A) configurant au moins une des fonctionnalités de l'appareil ballast (V) suivantes :
    - évaluation de signaux transmis à l'interface de signalisation,
    - commande du moyen d'éclairage,
    - activation/désactivation d'interfaces de l'appareil ballast,
    - activation/désactivation de protocoles de communication et
    - détection, réglage et/ou évaluation de données de fonctionnement et/ou de paramètres de fonctionnement de l'appareil ballast (V),
    caractérisé en ce
    que l'interface de programmation (P) est bloquée pour une transmission du logiciel d'application (A) et peut être activée par transmission d'une clé cryptographique à l'appareil ballast (V) pour la transmission du logiciel d'application (A) à travers l'interface de programmation (P) dans l'unité de mémoire (3) pour la configuration du microprocesseur (2).
  2. Appareil ballast (V) selon la revendication 1, l'au moins un logiciel d'application (A) fournissant et/ou modifiant une interface de programmation d'application.
  3. Appareil ballast (V) selon la revendication 1 ou 2, le microprocesseur exécutant un sous-système d'abstraction matérielle, à travers lequel l'au moins un logiciel d'application (A) accède à l'interface de programmation (P) et/ou l'interface de signalisation (S).
  4. Appareil ballast (V) selon l'une quelconque des revendications précédentes, l'interface de programmation (P) étant une interface filaire ou sans fil.
  5. Appareil ballast (V) selon l'une quelconque des revendications précédentes, l'interface de signalisation (S) servant à la connexion d'au moins une unité de signalisation.
  6. Appareil ballast (V) selon l'une quelconque des revendications précédentes, l'interface de signalisation (S) étant conçue comme une interface DALI, DSI, SPI, USB ou I2C.
  7. Appareil ballast (V) selon l'une quelconque des revendications précédentes, l'interface de programmation (P) et l'interface de signalisation (S) utilisant le même matériel et étant séparées l'une de l'autre uniquement côté logiciel.
  8. Appareil ballast (V) selon l'une quelconque des revendications précédentes, toutes les interfaces étant disposées sur au moins un bord (a, b, c, d) de la carte de circuit imprimé (1).
  9. Appareil ballast (V) selon l'une quelconque des revendications précédentes, le microprocesseur (2) étant un système à une puce.
EP16797910.3A 2015-11-17 2016-11-17 Appareil ballast pour moyen d'éclairage avec microprocesseur et interface de programmation Active EP3378286B1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP24153076.5A EP4355033A3 (fr) 2015-11-17 2016-11-17 Composant pour un système d'éclairage à microprocesseur et interface de programmation
EP21201386.6A EP3955705B1 (fr) 2015-11-17 2016-11-17 Composant pour un système d'éclairage pourvu de microprocesseur et interface de programmation

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE202015106224.9U DE202015106224U1 (de) 2015-11-17 2015-11-17 Vorschaltgerät für Leuchtmittel mit Mikroprozessor und Programmierungsschnittstelle
PCT/EP2016/077994 WO2017085182A1 (fr) 2015-11-17 2016-11-17 Appareil ballast pour moyen d'éclairage avec microprocesseur et interface de programmation

Related Child Applications (3)

Application Number Title Priority Date Filing Date
EP21201386.6A Division EP3955705B1 (fr) 2015-11-17 2016-11-17 Composant pour un système d'éclairage pourvu de microprocesseur et interface de programmation
EP21201386.6A Division-Into EP3955705B1 (fr) 2015-11-17 2016-11-17 Composant pour un système d'éclairage pourvu de microprocesseur et interface de programmation
EP24153076.5A Division EP4355033A3 (fr) 2015-11-17 2016-11-17 Composant pour un système d'éclairage à microprocesseur et interface de programmation

Publications (2)

Publication Number Publication Date
EP3378286A1 EP3378286A1 (fr) 2018-09-26
EP3378286B1 true EP3378286B1 (fr) 2022-03-09

Family

ID=57345949

Family Applications (3)

Application Number Title Priority Date Filing Date
EP24153076.5A Pending EP4355033A3 (fr) 2015-11-17 2016-11-17 Composant pour un système d'éclairage à microprocesseur et interface de programmation
EP21201386.6A Active EP3955705B1 (fr) 2015-11-17 2016-11-17 Composant pour un système d'éclairage pourvu de microprocesseur et interface de programmation
EP16797910.3A Active EP3378286B1 (fr) 2015-11-17 2016-11-17 Appareil ballast pour moyen d'éclairage avec microprocesseur et interface de programmation

Family Applications Before (2)

Application Number Title Priority Date Filing Date
EP24153076.5A Pending EP4355033A3 (fr) 2015-11-17 2016-11-17 Composant pour un système d'éclairage à microprocesseur et interface de programmation
EP21201386.6A Active EP3955705B1 (fr) 2015-11-17 2016-11-17 Composant pour un système d'éclairage pourvu de microprocesseur et interface de programmation

Country Status (6)

Country Link
US (1) US10257912B2 (fr)
EP (3) EP4355033A3 (fr)
CN (1) CN108605399A (fr)
AT (1) AT16920U1 (fr)
DE (1) DE202015106224U1 (fr)
WO (1) WO2017085182A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102020117446A1 (de) 2020-07-02 2022-01-05 Zumtobel Lighting Gmbh Vorrichtung mit multifunktionalem Anschluss für Nicht-DALI-Bediengeräte
US11966213B2 (en) * 2020-08-03 2024-04-23 Abl Ip Holding Llc Handheld programmer for LED drivers

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120086345A1 (en) * 2011-11-20 2012-04-12 Tran Bao Q Solid state light system with broadband optical communication capability
US20150257229A1 (en) * 2011-08-19 2015-09-10 Appalachian Lighting Systems, Inc. Lighting device monitor and communication apparatus

Family Cites Families (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7619539B2 (en) * 2004-02-13 2009-11-17 Lutron Electronics Co., Inc. Multiple-input electronic ballast with processor
DE102004061294B4 (de) 2004-12-20 2020-03-19 Tridonic Gmbh & Co Kg Verfahren zur Programmierung eines Betriebsgerätes für Leuchtmittel, Schnittstelle für ein Betriebsgerät für Leuchtmittel und Betriebsgerät für Leuchtmittel
US20080211427A1 (en) * 2005-06-02 2008-09-04 Koninklijke Philips Electronics, N.V. Lighting System and Method for Controlling a Lighting System
US8994276B2 (en) * 2006-03-28 2015-03-31 Wireless Environment, Llc Grid shifting system for a lighting circuit
US8491159B2 (en) * 2006-03-28 2013-07-23 Wireless Environment, Llc Wireless emergency lighting system
US9338839B2 (en) * 2006-03-28 2016-05-10 Wireless Environment, Llc Off-grid LED power failure lights
US20070288738A1 (en) * 2006-06-09 2007-12-13 Dale Jason N System and method for selecting a random processor to boot on a multiprocessor system
DE102007004397B4 (de) * 2007-01-29 2019-06-13 Tridonic Gmbh & Co Kg Verfahren und System zur Datenübertragung
WO2009097900A1 (fr) * 2008-02-08 2009-08-13 Osram Gesellschaft mit beschränkter Haftung Dispositif et procédé en particulier pour la commande d'une lampe
US8543249B2 (en) * 2008-04-14 2013-09-24 Digital Lumens Incorporated Power management unit with modular sensor bus
DE102008053486A1 (de) 2008-10-28 2010-05-27 Osram Gesellschaft mit beschränkter Haftung Elektronisches Vorschaltgerät mit standardisierten Datenschnittstelle
DE102009032026A1 (de) 2009-07-07 2011-01-13 Tridonicatco Gmbh & Co. Kg Betriebsgerät für Leuchtmittel
US8466628B2 (en) * 2009-10-07 2013-06-18 Lutron Electronics Co., Inc. Closed-loop load control circuit having a wide output range
DE102009056152A1 (de) * 2009-11-27 2011-06-01 Ledon Lighting Jennersdorf Gmbh Beleuchtungsfernsteuerung
US20130057158A1 (en) * 2010-03-01 2013-03-07 Led Roadway Lighting Ltd. Gps-based streetlight wireless command and control system
DE102010025082A1 (de) 2010-06-25 2011-12-29 Hella Kgaa Hueck & Co. Beleuchtungsvorrichtung für Straßen
DE102011086702A1 (de) 2011-11-21 2013-05-23 Tridonic Gmbh & Co. Kg Konfiguration von Betriebsgeräten für Leuchtmittel
DE102012011049A1 (de) 2012-06-02 2013-12-05 Diehl Aerospace Gmbh Leuchtvorrichtung mit einem zumindest eine LED aufweisenden Leuchtmittel
US10064251B2 (en) * 2013-03-15 2018-08-28 Cree, Inc. Updatable lighting fixtures and related components
KR20150009880A (ko) * 2013-07-17 2015-01-27 삼성전자주식회사 직관형 발광 장치
CN105659703B (zh) 2013-08-19 2019-07-05 飞利浦照明控股有限公司 可编程照明设备和用于对照明设备进行编程的方法和系统
US9332619B2 (en) * 2013-09-20 2016-05-03 Osram Sylvania Inc. Solid-state luminaire with modular light sources and electronically adjustable light beam distribution
US10154569B2 (en) * 2014-01-06 2018-12-11 Cree, Inc. Power over ethernet lighting fixture
DE102014200297A1 (de) * 2014-01-10 2015-07-16 Tridonic Gmbh & Co Kg Betriebsgerät und Kommunikationsadapter für den Außeneinsatz
CN103870403A (zh) * 2014-02-16 2014-06-18 金德奎 可用手机或电脑进行软件更新和/或自定义控制方案的led灯具及其方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150257229A1 (en) * 2011-08-19 2015-09-10 Appalachian Lighting Systems, Inc. Lighting device monitor and communication apparatus
US20120086345A1 (en) * 2011-11-20 2012-04-12 Tran Bao Q Solid state light system with broadband optical communication capability

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
W CAELLI ET AL: "Cryptographic Application Programming Interfaces (APls)", 1 January 1993 (1993-01-01), pages 640 - 645, XP055600804, Retrieved from the Internet <URL:https://s3.amazonaws.com/academia.edu.documents/46985566/0167-4048_2893_2990079-k20160703-6257-1edpuxa.pdf?response-content-disposition=inline;%20filename=Cryptographic_Application_Programming_In.pdf&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWOWYYGZ2Y53UL3A/20190701/us-east-1/s3/aws4_re> [retrieved on 20190701] *

Also Published As

Publication number Publication date
EP3955705A1 (fr) 2022-02-16
DE202015106224U1 (de) 2017-02-20
EP3378286A1 (fr) 2018-09-26
EP4355033A2 (fr) 2024-04-17
WO2017085182A1 (fr) 2017-05-26
US20180270932A1 (en) 2018-09-20
AT16920U1 (de) 2020-12-15
US10257912B2 (en) 2019-04-09
EP4355033A3 (fr) 2024-05-29
EP3955705B1 (fr) 2024-05-08
CN108605399A (zh) 2018-09-28

Similar Documents

Publication Publication Date Title
EP3683691B1 (fr) Dispositif pour la connexion en tant que noeud de bus à un bus de données différentiel à deux fils d&#39;un système de bus de données pour la transmission de données d&#39;éclairage pour des moyens d&#39;éclairage
WO2008009637A1 (fr) Appareil de commutation, système de commande d&#39;une lampe et système de commande de lampe pour un bâtiment comportant au moins un dispositif d&#39;éclairage
DE102014012252A1 (de) Verhindern einer verkehrsanalyse
EP3127099B1 (fr) Dispositif d&#39;affichage équipé d&#39;une interface sans fil et d&#39;une interface avec un système de bus d&#39;un système de commande en réseau
DE102016210414B4 (de) Adresszuweisung und Konfigurierung von Komponenten eines Beleuchtungssystems mittels Transponder
DE102012205964B4 (de) Beleuchtungssystem sowie Steuereinheit und Verfahren hierfür
EP3378286B1 (fr) Appareil ballast pour moyen d&#39;éclairage avec microprocesseur et interface de programmation
EP3391713B1 (fr) Protocolisation décentralisé des états de fonctionnement de composants de la technique du bâtiment
DE102015218243A1 (de) Mobilgerät und Verfahren zum Konfigurieren und/oder Kommissionieren eines Beleuchtungssystems und Beleuchtungssystemeinrichtung
WO2016094921A1 (fr) Système de communication domotique
DE102017121252B4 (de) System, Verfahren und Funkmodul zur Anwesenheitserkennung zwecks Energieeinsparung
DE202014106166U1 (de) Gebäudetechnik-Kommunikationssystem
EP3793139A1 (fr) Système de commande de bâtiment
EP3944565B1 (fr) Système et procédé d&#39;établissement d&#39;une connexion de données selon la norme io-link entre une unité maîtrisasse et au moins un appareil dispositif
DE102020123332B4 (de) Basismodul eines Netzwerkaufbaus sowie Netzwerkaufbau und Verfahren zum Konfigurieren eines Erweiterungsmoduls des Netzwerkaufbaus
DE102011075608A1 (de) Verfahren zum Zuordnen eines physikalischen Kanals eines Sensors, der an einen Bus eines Bus-Systems angeschlossen ist, zu einem Kanal eines in einem Inbetriebnahmeprogramm virtuell dargestellten Sensors sowie Sensor und Inbetriebnahmeprogramm
DE102016207919A1 (de) Mobiles Kommunikationsgerät mit einer Benutzerschnittstellendarstellung abhängig von einem an einer Schnittstelle erfassten Parameter
EP4152895A1 (fr) Système d&#39;éclairage
AT518226A2 (de) Steuersystem und Verfahren
DE102016104483A1 (de) Beleuchtungssystem mit automatischer Bakenkonfiguration
DE102020117446A1 (de) Vorrichtung mit multifunktionalem Anschluss für Nicht-DALI-Bediengeräte
DE102021116895A1 (de) System zur Gebäudeautomatisation
EP2992741B1 (fr) Procédé de commande d&#39;un appareil de fonctionnement destiné à des moyens d&#39;éclairage
DE102019103889A1 (de) Ein- und Auskoppelung von Daten und Datentransport über elektrische Versorgungsleitung von Beleuchtungssystemen
DE102009051386A1 (de) Verfahren zum Zuordnen eines physikalischen Kanals eines Sensors, der an einen Bus eines Bus-Systems angeschlossen ist, zu einem Kanal eines in einem Inbetriebnahmeprogramm virtuell dargestellten Sensors sowie Sensor und Inbetriebnahmeprogramm

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: 20180515

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

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20190321

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 502016014632

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H05B0037020000

Ipc: H05B0047165000

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

RIC1 Information provided on ipc code assigned before grant

Ipc: H05B 47/165 20200101AFI20211027BHEP

INTG Intention to grant announced

Effective date: 20211115

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

Free format text: NOT ENGLISH

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

Ref country code: AT

Ref legal event code: REF

Ref document number: 1475214

Country of ref document: AT

Kind code of ref document: T

Effective date: 20220315

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 502016014632

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

Free format text: LANGUAGE OF EP DOCUMENT: GERMAN

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20220309

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: 20220309

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: 20220309

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: 20220609

Ref country code: LT

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: 20220309

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: 20220309

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: 20220609

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: 20220309

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: 20220610

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: 20220309

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: 20220309

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: 20220309

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: 20220309

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: 20220309

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: 20220711

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: 20220309

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: 20220309

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: 20220309

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

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: 20220309

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: 20220709

Ref country code: AL

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: 20220309

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 502016014632

Country of ref document: DE

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

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: 20220309

26N No opposition filed

Effective date: 20221212

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

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: 20220309

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: 20220309

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230530

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20221130

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: 20220309

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: 20221117

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: 20221117

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: 20221130

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20231121

Year of fee payment: 8

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20231123

Year of fee payment: 8

Ref country code: DE

Payment date: 20231127

Year of fee payment: 8

Ref country code: CH

Payment date: 20231201

Year of fee payment: 8

Ref country code: AT

Payment date: 20231117

Year of fee payment: 8

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20161117

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

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: 20220309