EP2898658A1 - Terminal, monitoring system having said terminal and method for initializing the terminal - Google Patents
Terminal, monitoring system having said terminal and method for initializing the terminalInfo
- Publication number
- EP2898658A1 EP2898658A1 EP13771424.2A EP13771424A EP2898658A1 EP 2898658 A1 EP2898658 A1 EP 2898658A1 EP 13771424 A EP13771424 A EP 13771424A EP 2898658 A1 EP2898658 A1 EP 2898658A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- terminal
- network
- server
- designed
- message
- 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.)
- Ceased
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/10—Mapping addresses of different types
- H04L61/103—Mapping addresses of different types across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/2514—Translation of Internet protocol [IP] addresses between local and global IP addresses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0823—Network architectures or network communication protocols for network security for authentication of entities using certificates
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5038—Address allocation for local use, e.g. in LAN or USB networks, or in a controller area network [CAN]
Definitions
- the monitoring of complex or sprawling buildings or squares requires a variety of monitoring devices, such as surveillance systems.
- surveillance systems Surveillance cameras to cover such surveillance areas over a large area.
- the image data streams were transmitted from the surveillance cameras analog in monitoring centers and evaluated there, it is now known to connect surveillance cameras to a data network and to transmit the image data streams digitally.
- IP address network address
- the surveillance camera must be "found" by the monitoring center in the data network in order to be able to communicate with it. Consequently, the integration of a surveillance camera into a network usually requires the sophisticated expertise of a system administrator to perform the commissioning error-free.
- a terminal for a monitoring system and the monitoring system with the terminal and a method for initialization of the terminal in the monitoring system with the features of claims 1, 9 and 12 are proposed. Preferred or advantageous embodiments of the invention will become apparent from the dependent claims, the following description and the accompanying drawings.
- the invention thus relates to a terminal - also called edge device - which is suitable for integration into a monitoring system and / or trained.
- the terminal forms an interface between the monitoring system and a monitoring area.
- the terminal has at least one functional device, wherein the functional device is designed as a sensor and / or actuator device.
- the functional device can be used, for example, as an automatic or manual fire detector, as a temperature sensor, as an object sensor, e.g. a light barrier, be designed as a door opener, as a turnstile opener, etc.
- the terminal comprises a control device, wherein the control device is designed as a digital data processing device.
- the digital data processing device is realized as a computer with an operating system.
- the terminal comprises at least one network interface, which allows a coupling of the control device or the terminal to a network.
- the network is particularly preferably a data network operating on the basis of the TCP-IP protocol. In particular, it is an Ethernet network.
- the network interface and / or the control device allow data from the functional device to be transmitted to the network and / or data from the network to the functional device.
- it is possible, for example, to transmit sensor data of the sensor device into the network or to transmit command data from the network to the actuator device. It is also possible, for example, for bidirectional communication to configure the functional device via the network interface.
- the terminal has a client address from a first network, wherein the first network is preferably designed as a LAN (Local Area Network).
- the first network is designed as a local subnet.
- the terminal it is proposed that the terminal a
- the memory device in which a server address from another Network is stored.
- the memory device is particularly preferably designed as a non-volatile memory.
- the memory device is preconfigured so that the server address is stored in the memory device, for example, at the factory and thus known.
- the controller is programmatically and / or circuitry designed to send an initialization of the terminal via the network interface, a message to the server address.
- the terminal has the functionality that upon initialization of the terminal, the message is preferably automatically or automatically sent from the terminal to the first network and from there to the other network to the server, the server address being preconfigured in the terminal ,
- the terminal is thus designed in terms of programming and / or circuitry to actively establish communication with the server at the preconfigured server address during initialization.
- the terminal is thus a technical solution to the problem that exists in a widely distributed network having at least one local subnet as the first network and one main network as the other network when the local subnet is partitioned from the main network by a router.
- NAT separation
- network subscribers (clients) in the local subnet are invisible to the applications and devices in the main network as the other network.
- this procedure poses security risks because the unlocked port is also visible to other subscribers in the main network.
- the terminal according to the invention uses the decisive advantage that it knows in advance the remote site, the server as the backend, since the server address is stored preconfigured in the memory device.
- the connection setup from the terminal to the server is a communication from the local subnet as the first network to the main network as the other network and not vice versa.
- Traditional routers or NATs allow connections in this direction and do not have to be reprogrammed consuming.
- the server as the backend can use the established connection to communicate with the terminal and make further inquiries.
- the terminal can be parameterized by the server in this way and data, eg video screens, can be requested or transmitted.
- the terminal has several advantages: It requires less configuration effort, since overcoming a NAT boundary without router configuration is possible.
- the terminal allows a plug-and-play device, since the terminal in the first network only one
- the functional devices and the control device are integrated in a housing.
- the terminal is particularly compact and can be easily installed, since only the housing must be mounted and the network connection must be established.
- the terminal is designed as an embedded system and / or as an intelligent functional component.
- the preferred operating system is Linux (Embedded Linux) NetBSD or Windows (CE, XP Embedded, Automotive or Embedded for PoS). Due to the training as an embedded system / intelligent functional component, a large variety of functions can be implemented with a low hardware cost.
- the message comprises a unique device ID, thus enabling the server to uniquely identify the terminal.
- the device ID - hereinafter also referred to simply as ID - can be embodied, for example, as a number and / or number sequence.
- the ID allows the server to specify the type and / or functionality of the server
- Terminal as well as other information, such as Derive instruction sets and communication details.
- the terminal is designed to establish a bidirectional communication with certificate-based authentication with the server.
- the terminal is formed with the Server to perform an SSL handshake to allow secure communication between the server and the terminal.
- the storage device of the terminal has an authentication certificate.
- SSL communication another encryption protocol can be used for secure data transmission, such as TLS (Transport Layer Security).
- TLS Transport Layer Security
- control device has a connection module, which is formed, the
- the message is sent until a response has been received from the server.
- connection module is designed so that the time intervals between the transmission of the messages in dependence on the time from the initialization and / or in dependence of the transmitted messages are increased. This refinement is based on the consideration that errors can occur during a connection setup, so that it makes sense to send the message repeatedly. However, if it is not possible to establish a connection within a definable period of time, then it can be assumed that physical network problems predominate and that an immediate repetition of the message is meaningless. For example, first the message is sent in an interval of 10 seconds; if a corresponding response from the server is not present within the first hour, the interval is increased to 30 seconds and, if after a period of e.g. There is no response from the server for seven days - the interval is increased to 300 seconds. In this way it is possible, on the one hand, to regularly test the connection establishment or to check and, on the other hand, to operate the terminal in an energy-saving manner.
- the initialization is automatically started by turning on the terminal, in particular by connecting the terminal to a power supply.
- the power is supplied via the network (POE - Power Over Ethernet), so that it is sufficient to connect the terminal to the first network to start the initialization.
- the terminal is designed as a surveillance camera, in particular as a digital surveillance camera.
- the surveillance camera is also realized as a so-called PTZ (Pan-Tilt-Zoom) camera, which can control the viewing direction and the image detail change.
- PTZ Pan-Tilt-Zoom
- Another object of the invention is a monitoring system - also called monitoring system - with at least one terminal, as previously described, or according to one of the preceding claims.
- the monitoring system further comprises the server, the terminal having the client address from the first network and the server having the server address from the other network.
- the two networks are separated from one another via at least one NAT device (network address translation device), so that the message is sent from the terminal to the server via the at least one NAT device.
- NAT device network address translation device
- Such a NAT device is arranged in terms of data between two networks to different
- the NAT device is designed as a router.
- the NAT device has the function of automatically replacing address information in data packets with other address information. In this way, it is possible, for example, for the server to address the terminal with an address that is passed through the IP address.
- Address and a port of the NAT device is formed, but without knowing the actual IP address (client address) in the local network as the first network of the terminal.
- the NAT device assumes the function of translating the own IP address and the port specification into an IP address, ie the client address, and a port specification in the first network.
- the replacement of the address information in the opposite direction preferably takes place in the same way.
- the first network has a DHCP (Dynamic Host Configuration Protocol) functionality, whereby an automatic integration of the terminal into the first network is made possible without manual configuration of the terminal.
- DHCP Dynamic Host Configuration Protocol
- the automatic connection of the IP address is set on the terminal. This embodiment simplifies the installation of the terminal again.
- Another object of the invention relates to a method for initializing the terminal, as described above, in the monitoring system, as also described above, wherein the terminal sends a message to the server address at its initialization.
- the method comprises the intended use of the terminal and / or the monitoring system.
- Figure 1 is a schematic block diagram of a monitoring system as an embodiment of the invention
- FIG. 2 shows a flowchart for explaining the method for starting up a terminal in the monitoring system of FIG. 1;
- FIG. 3 shows a schematic diagram for further explanation of the method of FIG. 2.
- FIG. 1 shows a schematic block diagram of a monitoring system 1 as an exemplary embodiment of the invention.
- the monitoring system 1 comprises at least one local monitoring network as a first network 2.
- the first network 2 is installed in a monitoring object 3, such as in a building or building complex, a railway station, an airport, etc.
- the first network 2 is designed as a local network and defines one or at least one local domain.
- the first network 2 is realized as a LAN, for example.
- Each of the network subscribers in the first network 2 has a local IP address.
- the first network 2 has as an interface to another network 4 a router 5, which comprises a NAT device 6.
- the NAT device 6 is configured to translate network addresses between the first network 2 and the other network 4.
- the first network 2 is an exclusively private network and the other network 4 is the Internet or an Tier 3 or Tier 2 or Tier 1 network.
- At least one terminal 7 with a functional device 12 is arranged.
- the terminal 7 as a surveillance camera, the latter comprises a camera device as the functional device 12, which is designed to monitor a surveillance area 8 in the surveillance object 3.
- the terminals 7 each have a network interface 9, via which the terminals 7 in the first network 2 can communicate.
- the terminals 7 are designed as intelligent terminals 7, which each comprise a control device 10 and a local memory device 11.
- the other network 4 is based on the Internet protocol and may be designed as a public Internet in a first alternative embodiment.
- the other network 4 is designed as a private IP network, wherein all interfaces of the other network 4 are assigned exclusively to the private IP network and the private IP network is in particular separated from the public Internet by data technology.
- the other network 4 may also be formed as a LAN (Local Area Network) or as a WAN (Wide Area Network).
- the other network 4 implements a TCP connection.
- the monitoring system 1 comprises an in particular central or global safety control device, which is designed as a server 13. Of the Server 13 is connected via an interface with the other network 4 and thus indirectly with the first network 2 in terms of data technology.
- monitoring data of the terminals 7 can be forwarded from the first network 2 via the router 5 or the NAT device 6 to the server 13 designed as a security control device.
- the server 13 may subsequently - depending on its training - evaluate the monitoring data and automatically trigger an alarm or forward the monitoring data to a monitoring personnel.
- the server 13 can transmit configuration data or data queries to the terminals 7 via the other network 4, the router / NAT device 5/6. If the terminals 7 are designed as surveillance cameras, images of the surveillance area 8 are transmitted in the direction of the server 13.
- the terminals 7 can also carry out autonomous evaluations of the monitoring data with the control device 10.
- other types of terminals 7, e.g. Door opener, fire detectors, etc. may be integrated alternatively or in addition to the surveillance cameras.
- the terminals 7 are each assigned local IP addresses as client addresses in the first network 2.
- the server 13 is assigned in the other network 4, an IP address as the server address. It may optionally be provided that the server 13 is again arranged in a local network, wherein the server is nevertheless reachable via the server address via the other network 4.
- the terminals 7 each have a socket-knocker transmitter functionality and the server 13 a socket-knocker receiver functionality.
- the server address of the server 13 permanently stored. This can be done for example via a preconfiguration of the terminals 7.
- a unique ID of the terminal 7 is stored in the memory device 1 1.
- a certificate for a mutual authentication of terminal 7 and server 13 is stored in the memory device 1 1.
- the server 13 comprises a device manager 14, which e.g. as a program or a service is formed in the server 13. To explain the connection setup between terminal 7 and
- a step 100 the terminal 7 is turned on, connected to a power supply or connected to the first network 2, so that a start-up of the terminal 7 expires.
- a message N is sent from the terminal 7 to the server 13, in particular to the device manager 14, as a knock.
- the transmission can be implemented by a connection module (not shown) of the control device 10, which is likewise designed as a program or a service.
- the message N includes the unique ID of the terminal 7.
- Connection information in particular the IP addresses, ports and possibly time-outs are stored in a NAT table.
- the NAT device 6 can correctly assign a response data packet from the device manager 14 or the server 13 to the respective terminal 7. By sending the message N to the server 13 thus a bidirectional connection is initiated.
- the device manager 14 adds the terminal 7 on the basis of the unique ID to a list of devices which it makes available to the server 13. Furthermore initiated the
- step 300 the terminal 7 waits to receive a response data packet from the device manager 14. If this is not the case, the sending of the message N is repeated. If this is the case, the SSL handshake is accepted and established in a step 400, a secure connection to the device manager 14 and thus to the server 13.
- step 500 it is checked in a step 500 whether the certificate of the device manager 14 matches the certificate stored in the memory device 11.
- a step 600 the established connection is kept open in order to be able to receive incoming requests from the device manager 14 or the server 13. In the event that the connection is lost or time-out occurs in step 700, the procedure is restarted.
- FIG. 3 again shows the method in another illustration:
- step 100 the terminal 7 is turned on.
- step 150 the terminal 7 receives the client address via DHCP.
- step 200 the message N is transmitted to the device manager 14.
- step 400 the
- step 500 the identity of the device manager 14 is validated by the terminal 7.
- step 800 it is queried externally whether the server 13 or the device manager 14 have new terminals 7 known.
- the server 13 sends a request to the device manager 14 for new devices, and in a step 900 transmits the device list with the terminals 7 to the server 13.
- the sending of the message N is repeated if it has been determined in the step 300 that no response from the
- the time length of a transmission interval is determined in a step 210. For example, if there is no response after a few attempts, the send interval is increased. In a step 220, the time length of the knock interval is awaited and in a step 230 the message N is sent again.
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE201210217144 DE102012217144A1 (en) | 2012-09-24 | 2012-09-24 | Terminal, monitoring system with the terminal and method for initializing the terminal in the monitoring system |
PCT/EP2013/069627 WO2014044824A1 (en) | 2012-09-24 | 2013-09-20 | Terminal, monitoring system having said terminal and method for initializing the terminal |
Publications (1)
Publication Number | Publication Date |
---|---|
EP2898658A1 true EP2898658A1 (en) | 2015-07-29 |
Family
ID=49301447
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP13771424.2A Ceased EP2898658A1 (en) | 2012-09-24 | 2013-09-20 | Terminal, monitoring system having said terminal and method for initializing the terminal |
Country Status (5)
Country | Link |
---|---|
US (1) | US9686132B2 (en) |
EP (1) | EP2898658A1 (en) |
CN (1) | CN104641619A (en) |
DE (1) | DE102012217144A1 (en) |
WO (1) | WO2014044824A1 (en) |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10108238B2 (en) | 2016-07-22 | 2018-10-23 | Rockwell Automation Technologies, Inc. | Intelligent power tap for providing power and communicating in industrial automation applications |
US10126799B2 (en) | 2016-07-22 | 2018-11-13 | Rockwell Automation Technologies, Inc. | Intelligent power tap with zone control and safety zone control |
US10108216B2 (en) | 2016-07-22 | 2018-10-23 | Rockwell Automation Technologies, Inc. | Power tap with adjustable configuration |
US10154006B2 (en) | 2016-07-22 | 2018-12-11 | Rockwell Automation Technologies, Inc. | Systems, methods and apparatus for supporting multiple network addressing modes |
US10218699B2 (en) | 2016-07-22 | 2019-02-26 | Rockwell Automation Technologies, Inc. | Systems and methods for adding a non-inherent component to a device key of a networked device |
US10440620B2 (en) * | 2016-07-22 | 2019-10-08 | Rockwell Automation Technologies, Inc. | Systems and methods for bidirectional network geography delivery |
EP3389237B1 (en) * | 2017-04-10 | 2019-04-03 | ise Individuelle Software und Elektronik GmbH | Method, device, computer-readable medium, and system for establishing links between a client and a target or end device |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2006064575A1 (en) * | 2004-12-15 | 2006-06-22 | Hitachi, Ltd. | Wireless communication terminal and its control method |
SE530217C2 (en) * | 2005-01-10 | 2008-04-01 | Axis Ab | Monitoring system and method for accessing a monitoring unit in a monitoring system |
US20060173997A1 (en) * | 2005-01-10 | 2006-08-03 | Axis Ab. | Method and apparatus for remote management of a monitoring system over the internet |
NO323215B1 (en) * | 2005-02-04 | 2007-01-29 | Tandberg Telecom As | Firewall / NAT Protected Network Monitoring and Configuration Procedure |
ATE458328T1 (en) * | 2005-12-22 | 2010-03-15 | Axis Ab | MONITORING SYSTEM AND METHOD FOR CONNECTING A MONITORING DEVICE TO A SERVICE SERVER |
KR100937872B1 (en) * | 2007-12-17 | 2010-01-21 | 한국전자통신연구원 | Method and Apparatus for dynamic management of sensor module on sensor node in wireless sensor network |
FI123551B (en) * | 2011-02-22 | 2013-07-15 | Tosibox Oy | Procedure and arrangement for the implementation of remote control in real estate |
CN102221995A (en) * | 2011-05-19 | 2011-10-19 | 中国石油集团川庆钻探工程有限公司 | Break restoration method of seismic data processing work |
-
2012
- 2012-09-24 DE DE201210217144 patent/DE102012217144A1/en active Pending
-
2013
- 2013-09-20 WO PCT/EP2013/069627 patent/WO2014044824A1/en active Application Filing
- 2013-09-20 EP EP13771424.2A patent/EP2898658A1/en not_active Ceased
- 2013-09-20 US US14/429,393 patent/US9686132B2/en active Active
- 2013-09-20 CN CN201380048987.8A patent/CN104641619A/en active Pending
Non-Patent Citations (2)
Title |
---|
None * |
See also references of WO2014044824A1 * |
Also Published As
Publication number | Publication date |
---|---|
CN104641619A (en) | 2015-05-20 |
WO2014044824A1 (en) | 2014-03-27 |
DE102012217144A1 (en) | 2014-03-27 |
US9686132B2 (en) | 2017-06-20 |
US20150256389A1 (en) | 2015-09-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2014044824A1 (en) | Terminal, monitoring system having said terminal and method for initializing the terminal | |
DE602005002927T2 (en) | TIME SYNCHRONIZATION DEVICE AND METHOD AND CORRESPONDING PRODUCTS | |
EP3066791B1 (en) | Network system, coupling unit, and method for operating a network system | |
DE112007003657T5 (en) | Method and arrangement for a multimedia gateway and communication terminals | |
DE112008003010T5 (en) | Highly scalable network environment for controlling remote devices | |
EP2201724B1 (en) | Identification and/or addressing of a data terminal device of a local network | |
DE102014113885A1 (en) | Method for establishing a local control channel between a control device and an in-building access portal | |
EP2898649B1 (en) | Monitoring system with message forwarding, a method, and a computer program | |
DE102013109884B3 (en) | Method for establishing the connection of network terminals | |
EP2680497B1 (en) | External access to IP-based house control unit in a local network | |
WO2002013480A1 (en) | System and method for transmitting data via data networks, in particular, the internet, using an asynchronous data connection | |
EP2557733A1 (en) | Configuration of a communication network | |
DE102014112704B3 (en) | Network system and network subscribers for data transmission via a cloud infrastructure and establishment process | |
EP2311240B1 (en) | Method for terminal addressing and network equipped therefor and access node | |
EP3644570B1 (en) | Firewall for building networks, a corresponding system and method and computer readable medium | |
DE102004025056B4 (en) | Method and device for ensuring access protection in a shared medium network | |
DE102014220215A1 (en) | Method for wireless communication | |
EP1919128A1 (en) | Device and method for manufacturing a secure connection between a terminal device and an internet server | |
DE102020207033B4 (en) | Devices and methods for integrating a device into a local area network | |
EP3537654B1 (en) | Method and system for determining a configuration of an interface | |
DE102006056566B3 (en) | Industrial network e.g. virtual local area network, for connection to e.g. laptop, has freely accessible access points connecting mobile terminal with network when terminal is registered with registration unit | |
DE102008055967B4 (en) | Endpoint addressing method, and dedicated network and access node | |
DE102022108427A1 (en) | Computer arrangement, method for connecting a first computer via a cloud to a network of devices and operation of a computer arrangement | |
EP1748619A1 (en) | Method for creating a direct and secure communication connection between two networks | |
DE102006054441A1 (en) | Data exchanging method, involves linking virtual private network platform with mobile functional network of mobile functional terminal, where terminal has access to individual devices and/or device arrangements for controlling platform |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
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 |
|
17P | Request for examination filed |
Effective date: 20150424 |
|
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 |
|
DAX | Request for extension of the european patent (deleted) | ||
17Q | First examination report despatched |
Effective date: 20160922 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R003 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED |
|
18R | Application refused |
Effective date: 20171211 |