EP3382657B1 - Procédé de fonctionnement d'un système d'accès - Google Patents

Procédé de fonctionnement d'un système d'accès Download PDF

Info

Publication number
EP3382657B1
EP3382657B1 EP17164187.1A EP17164187A EP3382657B1 EP 3382657 B1 EP3382657 B1 EP 3382657B1 EP 17164187 A EP17164187 A EP 17164187A EP 3382657 B1 EP3382657 B1 EP 3382657B1
Authority
EP
European Patent Office
Prior art keywords
access
gate
mobile terminal
signal
data set
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
EP17164187.1A
Other languages
German (de)
English (en)
Other versions
EP3382657A1 (fr
Inventor
Norbert Miller
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.)
Scheidt and Bachmann GmbH
Original Assignee
Scheidt and Bachmann GmbH
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 Scheidt and Bachmann GmbH filed Critical Scheidt and Bachmann GmbH
Priority to PL17164187.1T priority Critical patent/PL3382657T3/pl
Priority to EP17164187.1A priority patent/EP3382657B1/fr
Priority to HUE17164187A priority patent/HUE059098T2/hu
Priority to ES17164187T priority patent/ES2919127T3/es
Publication of EP3382657A1 publication Critical patent/EP3382657A1/fr
Application granted granted Critical
Publication of EP3382657B1 publication Critical patent/EP3382657B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C9/00—Individual registration on entry or exit
    • G07C9/10—Movable barriers with registering means
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C9/00—Individual registration on entry or exit
    • G07C9/20—Individual registration on entry or exit involving the use of a pass
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C9/00—Individual registration on entry or exit
    • G07C9/00174—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys
    • G07C2009/00753—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys operated by active electrical keys
    • G07C2009/00769—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys operated by active electrical keys with data transmission performed by wireless means
    • G07C2009/00793—Electronically operated locks; Circuits therefor; Nonmechanical keys therefor, e.g. passive or active electrical keys or other data carriers without mechanical keys operated by active electrical keys with data transmission performed by wireless means by Hertzian waves

Definitions

  • the application relates to a method for operating an access system and an access system.
  • Access to and/or exit from a specific area can be controlled using an access system.
  • An access system can have at least one gate.
  • a gate is in particular a passage barrier.
  • a gate can be used to ensure that only authorized users can pass through the gate, for example to get to the specific area.
  • a user acquires a (paper) ticket with a readable access data record, for example in the form of a readable code, at a ticket machine.
  • a readable access data record for example in the form of a readable code
  • the ticket in particular the access data record, is received or recorded by the gate and then checked. Access through the gate is granted or denied depending on the test result.
  • Access systems are therefore known from the prior art in which the access data record is transmitted from a remote central computing device (eg a backend system) via a long-distance communication network (eg cellular network) to a mobile terminal device of a user.
  • a remote central computing device eg a backend system
  • a long-distance communication network eg cellular network
  • the user can then use their mobile device instead of a separate (paper) ticket.
  • the readable access data record can be read out of the mobile terminal device by an interface device of the gate.
  • a corresponding system and procedure is in the U.S. 9,317,976 B2 disclosed.
  • a first signal in particular a beacon signal
  • the application then starts communication with a remotely located central computing device via a long-distance communication network (in particular a cellular network) using the mobile terminal device.
  • the central computing device transmits a readable access data record both to the mobile terminal device and to the gate.
  • the access data record is now read out from the mobile terminal by an interface device of the gate and compared with the access data record transmitted by the central computing device. If the test result is positive, access or passage through the gate is released in a conventional manner.
  • an access system for a specific area to be controlled can be located in a geographical area in which a mobile radio network is only available with insufficient quality. This can be the case in particular with underground access systems (eg subway stations and the like).
  • underground access systems eg subway stations and the like.
  • the invention is therefore based on the object of providing a method for operating an access system which improves both the user-friendliness and the reliability of the operation of the access system.
  • the previously derived and presented object is achieved by a method for operating an access system according to claim 1 .
  • the access system comprises at least one gate and at least one first near-field transmission device assigned to the gate.
  • a first signal is sent out via a wireless channel in such a way that a mobile terminal device receiving the first signal generates a local access data record, at least based on a transmitted first transmitter identifier and one stored on the mobile terminal device Access identifier, both the user-friendliness and the reliability of the access system are improved.
  • no communication between a remote central processing device and the gate is required when verifying the approval of entry or passage through the gate.
  • the present access system can be operated without communication with a remote central computing device.
  • the present access system can be used to control entry into and/or exit from at least one specified area.
  • exemplary and non-exhaustive areas of application of an access system are buildings and/or areas of buildings such as office buildings, airports, train stations, platforms, gates, residential buildings, amusement parks, swimming pools and the like, and vehicles such as rail vehicles, buses or airplanes.
  • An access system can have one or have multiple gate(s).
  • a gate is a barrier to passage to and/or from a specific area. Examples of gates are doors or turnstiles.
  • the access system comprises one or more first transmission devices.
  • the first transmission device is assigned to the at least one gate or a gate arrangement (also called a gate array) comprising the at least one gate.
  • An association can in particular include a (wireless and/or preferably wired) communication connection between the gate and the first transmission device.
  • At least the transmitted first transmitter identifier can be made available to the gate, in particular to a checking device of the gate, via the communication connection.
  • an assignment is to be understood in particular as meaning that the first transmission field of the one or more first transmission device(s) covers the uncontrolled area in front of the gate or the gate arrangement with the gate. In other words, a user usually only gets to the gate by having previously passed through the first transmission field.
  • the present method includes the preferably (quasi) continuous transmission of a first signal by the first transmission device.
  • the first signal can include at least a first transmitter identifier of the first transmitter device.
  • a first transmitter identifier for example a specific character code, is in particular clearly assigned to a first transmitter device emitting the corresponding first signal. In other words, the first transmitter device can be uniquely identified by the first transmitter identifier.
  • the first signal causes an access data record to be generated.
  • the first signal can include instructions which, after receiving the first signal and extracting the instructions and the first transmitter identifier, bring about the local generation of a readable access data record on the mobile terminal device.
  • the access data record comprises at least one key corresponding to the received transmitter identifier and an access identifier.
  • the key is identical to the first transmitter ID.
  • the access identifier can be a unique identifier, in particular a unique user identifier.
  • the access code can be uniquely assigned to the user of the mobile terminal, at least indirectly.
  • Exemplary and non-exhaustive access identifiers are user names, phone number of the mobile device, an IMEI (International Mobile Station Equipment Identity) number of the mobile device, a MAC (Media Access Control) address of the mobile device, a credit card number, and/or a SIM (Subscriber Identity Module).
  • a mobile terminal has processing means such as processor(s), memory, receiving means such as an antenna, etc., in order to receive a wireless first signal and process it in such a way that the access data record can be created locally.
  • processing means such as processor(s), memory, receiving means such as an antenna, etc.
  • receiving means such as an antenna, etc.
  • Exemplary and non-exhaustive mobile end devices are smartphones, tablet computers, mobile game consoles, laptops, netbooks, data glasses, smart watches and similar wearables.
  • the method includes receiving an access data record from a mobile terminal device by an interface device of the gate, preferably via a wireless channel.
  • Receiving includes in particular a detection of the access data record by the interface device.
  • the at least one interface device of the gate can correspond to at least one interface device of the mobile terminal device.
  • At least the key can be extracted from the received access data set and used for authentication of the received access data set.
  • the received key is compared with the one or more provided first transmitter identifier(s) of the one or more first transmitter device(s) assigned to the gate.
  • Access through the gate is then enabled at least as a function of the first test result of the first test step.
  • a release only takes place if it is determined in the first test step that the key received corresponds to a first transmitter identifier provided. If no such adjustment is found in the first test step, the gate remains blocked.
  • various interface devices can be provided and/or used to receive the access data record from a mobile terminal device, such as a Bluetooth interface or a WLAN interface.
  • the interface device of the gate is preferably provided for communication distances of less than 10 cm, preferably less than 2 cm. This ensures that the gate is only opened when the user is in the immediate vicinity of the gate.
  • an RFID (Radio Frequency Identification) interface in particular an NFC (Near Field Communication) interface, can be provided.
  • receiving the access data record from the mobile terminal device by the interface device of the gate includes reading out a barcode and/or QR code displayed by the mobile terminal device by the interface device of the gate.
  • a barcode reader and/or QR code reader of the gate (which is provided anyway) can be used as an interface device.
  • a barcode and/or QR code can be displayed by an interface device, in particular a display of the mobile terminal device, and can be detected by the barcode reader and/or QR code reader of the gate.
  • an access data record comprising at least the key and the access identifier, can be represented in a simple manner by a barcode and/or QR code.
  • the key and the access identifier can easily be used for further testing by the processing means (e.g Processor, memory, etc.) of the gate can be extracted from the recorded barcode and/or QR code.
  • a first transmission device is a near-field transmission device.
  • the first transmission device can have a minimum range of at least 5 m, preferably at least 8 m, and a maximum range of at most 20 m, preferably at most 12 m.
  • RFID technology infrared technology
  • WLAN technology and/or sonic technology can be used.
  • the first signal can preferably be a Bluetooth signal emitted by a Bluetooth beacon.
  • a BLE (Bluetooth Low Energy) beacon can particularly preferably be used as the first transmission device.
  • a received access code can be checked in a second test step, the security of the access system can be improved. Access by unauthorized users can at least be made more difficult.
  • a local authorization list can preferably be stored in a local memory device which is assigned to the gate (e.g. all gates of a gate arrangement can access this memory device).
  • the memory device can be integrated in the gate, for example, or can be connected via a communication connection.
  • the local authorization list can in particular be a so-called negative list.
  • the authorization list can have at least one include access identifiers from unauthorized users/mobile devices. Access through the gate can be enabled at least as a function of the second test result of the second test step.
  • a release can take place at least only if it is determined in the second test step that the received access identifier does not correspond to any identifier stored in the authorization list. If it is determined in the second test step that the access identifier received corresponds to an access identifier on the authorization list, the gate remains blocked (despite a possibly positive first test result).
  • a so-called positive list can also be stored in the memory device of the gate and used for the second test step.
  • Another advantage of using a local authorization list is that no communication with a remote central computing device is required when performing the second verification step.
  • an access identifier received by the gate can be transmitted from a suitable transmission device of the gate to a corresponding reception device of the central computing device.
  • the central computing device may include one or more servers (e.g. cloud servers).
  • the central computing device can also be referred to as a "backend system".
  • the central computing device can include at least one test device for carrying out the third test step.
  • the received access identifier can be compared with stored permissible access identifiers.
  • the third verification step can take place, for example, as part of a (conventional) billing step; in particular, the third verification step can take place subsequently, after access has been granted by the gate. If it is determined that the received access identifier is an unauthorized access identifier, the central computing device can update the authorization list accordingly.
  • a locally generated access data record can preferably have a limited validity period (e.g. a maximum of x minutes).
  • provision can be made for the gate to check, for example in a fourth checking step, whether a received access data record is a chronologically valid access data record (or not).
  • the at least one transmission device and the gate associated with the at least one transmission device can be synchronized in time.
  • the first signal preferably has a time stamp corresponding to the transmission time of the first signal.
  • Time information can be inserted into the access data record based on the received time stamp.
  • a maximum permissible period of time e.g. x min from the time of transmission
  • the fourth test step for example, the difference between the time the access data record was received and the time stamp received can first be determined. The determined difference can then be compared with the specified maximum permissible time period. This can be used to check whether the access data record is (still) valid. At least depending on the fourth test result of the fourth test step, access through the gate can be enabled.
  • a release can at least only take place if it is determined in the fourth test step that the determined difference between the time of receipt of the access data record and the received time stamp is less than or equal to the predetermined maximum permissible period of time. If it is determined in the fourth test step that the difference is greater, the gate remains blocked. Since the fourth test step can be carried out in addition to the first test step described above and preferably in addition to the second test step described above, the security of the access system can be improved even further. Access by unauthorized users can be made even more difficult.
  • Code generation device to be set up The code generation device can include at least one generation means, set up to generate the access data record (described above).
  • the code generation device can in particular be in the form of a software module, such as a so-called “app”.
  • the code generating device can in particular be a computer program with instructions that can be executed on a processor of the mobile terminal device, such that a previously described access data record is generated locally.
  • Such a code generation device can be arranged, in particular installed, on a mobile terminal device.
  • Registration of the user/mobile end device with the central computing device may preferably be required before or during installation or when used for the first time.
  • a unique access identifier can be defined during registration and stored both in a memory device of the mobile terminal device (if it does not already exist there) and in a memory device of the central computing device.
  • the first signal can include instructions that activate or wake up the code generation device on the mobile terminal device and in particular subsequent automatic generation of the access data record described above.
  • this can include an automatic representation of the barcode or QR code corresponding to the access data record on a display of the mobile terminal device.
  • An access data record can be created and made available for reading in a particularly user-friendly manner.
  • the second signal can preferably be a signal which can be received and processed by a large number of different end devices.
  • the first signal can be a signal which can only be processed by a mobile terminal device if the mobile terminal device has previously received the second signal.
  • the first signal can be set up to bring about the generation of the access data record on the mobile terminal only after prior receipt of the received information of the second signal.
  • a second BLE beacon can be set up to emit a second signal, which can be used by almost any mobile device, in particular with a commercially available operating system (e.g. Apple iOS, Google Android, Microsoft Windows Mobile, Microsoft Mobile Phone, Blackberry OS, Symbian OS, Firefox OS , Tizen, Aliyun OS) can be received.
  • the second signal includes a configuration data record set up for configuring the mobile terminal device, in particular a code generation device arranged on the mobile terminal device.
  • the mobile terminal device, in particular the code generation device can preferably only process a first signal from a first BLE beacon after the configuration, in particular by means of the received information.
  • the configuration data record can preferably be received information in the form of a UUID (Universally Unique Identifier) of the first transmission device.
  • UUID Universally Unique Identifier
  • the UUID of the first sending device can be formed as a function of a hash value of the variable data of the received information.
  • the code generation device can be started and, in particular, configured on the mobile terminal device. As a result of the configuration, the mobile terminal device, including the code generation device, is set up to scan for signals including the received information.
  • the third signal can be sent out by a third sending device (eg a Bluetooth beacon).
  • the third transmission device can be assigned to the gate.
  • the third transmission device can include a communication link to the central computing device.
  • the location-related data set can be generated, for example, by the central computing device (eg after receipt and evaluation of the access code).
  • communication can be performed between the gate and the central computing device.
  • the gate is a terminal configured in the central computing device, whose operating data, in particular its location, can be known to the central computing device. Based on the location data (e.g.
  • the central computing device can determine the location-based (and preferably Generate user-related) data record.
  • Individual user information can preferably be stored in the central computing device for the respective access identifiers.
  • the desired use of a specific train can be stored as user information.
  • the location-based data record can include navigation data that show the user the way to the siding of the specific train.
  • the central computing device can be set up to detect change(s) with regard to the specific train (eg delay, change in the car sequence, platform change, etc.) and to generate a location-based data record with corresponding data.
  • This data record can be transmitted from the central computing device to the at least one third transmission device. Based on the access identifier, the third signal can be set up in such a way that it can only be processed by the mobile terminal device that has stored the access identifier.
  • the location-related data record can preferably be generated based on a recorded movement data record of the mobile terminal device. If, for example, based on the movement data record and/or the location of the gate and the stored user information, the central computing device detects that the mobile device or the user is (probably) moving in the wrong direction, a location-based data record with corresponding data can be generated. As previously described, a third signal can be sent out with this data set.
  • the movement data record can be recorded and transmitted by sensors of the mobile terminal device or can be recorded, for example, by passing specific transmission devices and/or gates and/or the like.
  • the method described above can preferably be used to operate the access system.
  • the first transmission device can be a Bluetooth beacon.
  • the (at least one) interface device of the gate is a barcode reader and/or a QR code reader.
  • the application also describes a code generation device for a mobile terminal device for (local) generation of an access data record.
  • the code generating device comprises at least one receiving means, set up to receive at least one first transmitter identifier transmitted by a first signal.
  • the code generation device in particular the receiving means, is set up to receive at least one access identifier stored in a memory device of the mobile terminal device.
  • the code generating device comprises at least one generating means, set up to generate the access data record with at least one key corresponding to the received transmitter identifier and the received access identifier.
  • the code generation device comprises at least one provision means, set up for providing the generated access data record in such a way that the access data record can be received by an interface device of a gate.
  • the code generation device can in particular be in the form of a software module, such as a so-called “app”.
  • the code generation device can in particular be a computer program with instructions that can be executed on a processor (of the mobile terminal device) in such a way that a previously described access data record is generated locally.
  • Such a code generation device can be arranged, in particular installed, on a mobile terminal device.
  • the first (or second) signal can include instructions that activate or wake up the code generation device on the mobile terminal device and in particular subsequent automatic generation of the access data record described above.
  • the received first transmitter identifier and the stored access identifier can be made available to the code generating device via the receiving means.
  • the access data record After the access data record has been generated, it can be sent to an interface device of the mobile terminal device by the Provision funds are provided.
  • this can include an automatic representation of a barcode or QR code corresponding to the access data record on a display of the mobile terminal device.
  • An access data record can be created and made available for reading in a particularly user-friendly manner. This allows an access data record to be generated locally without using a central computing device.
  • the mobile terminal comprises at least one code generation device as described above.
  • the code generation device can be implemented on the mobile terminal device.
  • the mobile terminal comprises at least one memory device set up to store at least one access identifier for at least one access system.
  • the figure 1 10 shows a schematic view of an embodiment of an access system 100 according to the present application.
  • the access system 100 comprises at least one first transmission device 102 and at least one gate 104.
  • two or more first transmission devices and/or at least one gate arrangement with two or more gates can be provided.
  • the first transmission device 102 is assigned to the gate 104 .
  • a communication connection 112 is provided for this purpose between the first transmission device 102 and the gate 104, for example via a wired channel.
  • the first transmission field covers in particular the area in front of the gate. Data can be exchanged between the first transmission device 102 and the gate 104 via the communication connection 112 .
  • time data for a time synchronization of the respective time means transmitted and/or the first transmitter identifier is provided by the first transmitter device 102 for the gate 104.
  • the first transmission device 102 in particular a transmission device with a defined transmission range (e.g. approx. 10 m), is set up to transmit a first signal.
  • the signal can preferably be sent out (almost) continuously.
  • the first signal includes at least a first transmitter identifier (unambiguously associated with the transmitting transmitter device).
  • the first signal can include additional data, such as a time stamp.
  • the initial transmitter ID may be changed periodically to improve security.
  • the access system 100 can ensure, for example, that only authorized users 110 can enter a specific area controlled by the access system 100 (behind the gate 104). For the authentication at the gate 104 it is proposed here to use a mobile terminal 106 . In addition to using a mobile terminal device 106, the access system 100 can also be designed for using other media (such as a paper ticket, magnetic stripe ticket, etc.).
  • a mobile terminal device 106 has, in particular, a first interface device (not shown) (e.g. a Bluetooth transceiver) set up to receive the first signal. If a mobile terminal 106 arrives in the first transmission field of the first transmission device 102, it receives the first signal. The first signal is set up to cause an access data record to be generated on mobile terminal device 106, in particular in cooperation with a code generation device installed on mobile terminal device 106, with at least one key corresponding to the first transmitter identifier and an access identifier stored on mobile terminal device 106.
  • a first interface device not shown
  • a Bluetooth transceiver e.g. a Bluetooth transceiver
  • Gate 104 has at least one interface device 108 for authentication at gate 104 .
  • the interface device 108 in the form of a Barcode reader 108 and/or QR code reader 108 is set up to receive, in particular to record, the access data record from mobile terminal device 106 .
  • the mobile terminal device 106 can preferably have a further interface device (not shown) corresponding to the interface device 108 , for example a display for showing a barcode or QR code.
  • the access data record can be read out by means of the interface device 108 .
  • the gate 104 includes means (not shown) for extracting the data (e.g. key, time stamp, access identifier, etc.) from the read access data record, which is formed by a barcode or QR code.
  • data e.g. key, time stamp, access identifier, etc.
  • a test device 114 can test the received data in one or more test steps. Depending on the at least one test result, access/passage through the gate 104 can be enabled by an enabling device 118 (in a known manner).
  • checking device 114 can be set up to check the access authorization at least by comparing the received key with the at least one first transmitter identifier provided by first transmitting device 102 in a first checking step. If the key corresponds to the first transmitter identifier provided (positive first test result), release can take place. If the first test result is negative, the gate 104 remains blocked and access is denied.
  • FIG. 12 shows a diagram of an embodiment of a method according to the application.
  • a first signal is transmitted by the first transmitting device 102.
  • step 402 the first signal causes an access data record to be generated with at least one key corresponding to the first transmitter identifier and an access identifier stored on mobile terminal device 106 .
  • step 403 the generated access data record is read out by an interface device 108 of the gate 104, and the access data of the received access data record are made available to the checking device 114.
  • step 404 at least a first test step is carried out. The access authorization is checked at least by comparing the received key with the at least one provided first transmitter identifier.
  • step 405 the gate 104 is enabled if the test result is positive. In other words, an authorized user 110 can pass through gate 104 .
  • figure 2 shows a schematic view of a further exemplary embodiment of an access system 200 according to the application. To avoid repetition, essentially only the differences from the exemplary embodiment are explained below figure 1 described. For the other components of the access system 200, reference is made to the statements above.
  • the gate 204 includes a storage device 216 .
  • the test device 214 in particular can access the memory device 216 .
  • An updatable (local) authorization list can preferably be stored in the storage device 216 .
  • a negative list can be stored that includes access identifiers that are not authorized for access.
  • the access system 200 comprises at least one second transmitting device 226 in addition to at least one first transmitting device 202.
  • the second transmitting device 226 is in particular a (Near-field) transmission device 226 with a defined transmission range (eg approx. 10 m).
  • the second transmitting device 226 can be a Bluetooth beacon.
  • the second transmission device 226 can be assigned at least to the first transmission device 202 .
  • a communication connection 234 between the second transmission device 226 and the first transmission device can be provided directly or indirectly (eg via the gate 204). In this way, for example, the received information of the configuration data set contained in the second signal can be compared between the transmitting devices 202, 226.
  • the second transmission device 226 can be set up to transmit the second signal.
  • the present access system 200 comprises at least one third transmission device 232. While the first transmission device(s) 202 and/or second transmission device(s) 226 can essentially cover the uncontrolled area in front of the gate 204 with their respective transmission field, the at least one third transmission device 232 cover the controlled area behind the gate 204 with their transmission field.
  • the third transmitting device 232 e.g., a Bluetooth beacon 232
  • the third transmission device 232 can have at least one communication link 236 with a long-distance communication data network 220 (e.g. Internet).
  • a remotely located central computing device 222 is located in the present embodiment.
  • the central computing device 222 can be connected to the long-distance communication data network 220 via an interface device 230 in order, for example, to exchange data with the gate 204, in particular via an interface module 220 of the gate 204, and/or with the third transmitting device 232.
  • the central computing device 222 can have at least one checking device 224 and at least one storage device 228 (for example a database for storing access identifiers, user information, etc.).
  • figure 3 shows a schematic view of an embodiment of a code generation device 350 according to the present application, which is arranged on a mobile terminal 306 according to the present application.
  • the code generating device 350 in particular a software module 350, can be installed on the mobile terminal device 306.
  • the code generating device 350 comprises a receiving means 338.
  • the receiving means 338 shown is set up to receive a received first transmitter identifier and an access identifier provided by a storage device 344 for further processing by a generating means 340.
  • the generating means 340 further processes the data received by creating a readable access data record locally (according to a predetermined generation scheme).
  • the generated access data record is provided by a provision module 342 to an interface device 352 of the mobile terminal device 306 .
  • the interface device 352 is a display 352 of the mobile terminal device 306.
  • other interface devices e.g. an NFC transceiver, a Bluetooth interface or a WLAN interface
  • FIG. 12 shows a diagram of another embodiment of a method according to the present application.
  • the first transmitter device 202 can transmit a first signal with a first transmitter identifier and optionally reception information
  • the second transmitter device 226 can transmit a second signal with a configuration data record, comprising a contained reception information corresponding reception information, are sent out.
  • the first signal and the second signal are configured in particular in such a way that the data content of the first signal is only processed if the second signal has been received beforehand and in particular after the mobile terminal device 306, in particular the code generating device 350, has been configured in accordance with the received configuration data record of the second signal , can be carried out.
  • the second signal is received by the mobile terminal 306 in step 502 .
  • the configuration data record is extracted and the mobile terminal 306, in particular the code generating device 350, is configured accordingly.
  • the mobile terminal 306 can then receive the first signal and extract and process the data contained therein.
  • at least the first transmitter identifier and a time stamp can be extracted from the first signal and made available to the code generation device 350 for further processing.
  • the second signal may include a UUID (e.g. according to the iBeacon standard) and so-called major and minor data (e.g. according to the iBeacon standard).
  • the UUID data can be chosen such that a mobile device recognizes the second signal as originating from an iBeacon.
  • the major and minor data can be used to represent received information in the form of a UUID of the first sending device 202 .
  • the UUID of the first sending device 202 may be formed as a function of a hash value of the major and minor data of the second signal.
  • the code generator 350 knows which UUIDs it must scan for in order to receive and process the first signal. Because of the association, the second signal can be matched to the first signal.
  • a readable access data record is then generated locally in step 506 .
  • the at least one Receiving means 338 receive the first transmitter identifier, the time stamp and an access identifier (in particular a user identifier valid for the access system 200 from the memory device 344).
  • the generation module 340 can generate an access data record based on the data received in step 503 and according to the instructions stored in the mobile terminal device 306.
  • the stored instructions can, for example, specify the generation of a barcode or QR code and the integration of the data received into this code.
  • an access data record is generated, which includes a key corresponding to the first transmitter identifier (namely the received first transmitter identifier), time information (e.g. the received time stamp) and the access identifier.
  • the provision means 342 can provide the generated access data record to an interface device 352 of the mobile terminal device 306.
  • the barcode or QR code can preferably be made available to a display 352 and automatically displayed by it for reading. It is understood that user confirmation may be required for the code to be displayed.
  • the interface device 352 of the mobile terminal device 306 can also be another suitable interface device, such as an NFC transceiver, a Bluetooth interface or a WLAN interface.
  • step 507 the generated access data record is received by an interface device 208 corresponding to the interface device 352 (a barcode reader and/or QR code reader) of the gate 204 .
  • the gate 204 is set up to receive the data encoded in a code (in particular keys, To extract time information and access code) and to provide at least one test device 214.
  • step 508 which can include a number of checking steps, the checking device 214 of the gate 204 can in particular check the validity of the received access data record, in particular the above-mentioned data.
  • a first test step it can be checked whether the key corresponds to at least one provided first transmitter identifier. If the first check result is negative (that is, if no correspondence is found), the gate 204 is blocked in step 511 or remains blocked (regardless of the result of the other check steps).
  • the access identifier can be compared with the access identifiers stored in the authorization list. If a correspondence between the received and stored access identifier is detected (negative second test result), the method (in the case of a negative list) is ended with step 511: the gate 204 is or remains blocked.
  • access through the gate 204 in step 510 is only released by the release device 218 if the first test result, the second test result and the fourth test result are positive.
  • a third signal can be sent out (step 515), which can be encoded in such a way that it can only be received and processed by the mobile terminal 306, which has previously transmitted the permissible access data set to the gate 204.
  • the access code can be used for this.
  • the data content of the third signal can be a location-related and preferably user-related data set, which can include navigation data, for example.
  • the generation can depend in particular on the location data of the gate 204 that the user passed and, for example, on user information stored in the central computing device 222 and/or recorded movement data of the mobile terminal device 306.
  • step 512 at least the access identifier received from the gate 204 can be transmitted to the central computing device 222 for further processing.
  • the transmitted access identifier can be checked by the checking device 224 of the central computing device 222 in step 513--for example as part of a billing step. If, for example, billing is not possible (e.g. no credit on the user's account) and/or the received access identifier does not correspond to any permitted (registered) access identifiers stored in storage device 228, that is Third test result of the third test step negative.
  • an update of the authorization list stored in the storage device 216 of the gate 204 can be performed.
  • the central computing device 222 can bring about a corresponding update, for example by transmitting an updated authorization list to the gate 204 .
  • the corresponding access identifier can be added, for example, in order to prevent at least renewed unauthorized access through the gate 204 or the gate arrangement. It goes without saying that all locally stored authorization lists of an access system 200 can be updated accordingly.
  • central computing device 222 If the central computing device 222 is provided for the control of two or more access systems, further local authorization lists of the gates of the further access systems can be updated accordingly.
  • step 515 can only be carried out after steps 512 and 513 in particular. It is further understood that some of the steps described above may be performed in a different order or in parallel.

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
  • Selective Calling Equipment (AREA)

Claims (10)

  1. Procédé d'exploitation d'un système d'accès (100, 200) ayant au moins une porte (104, 204) et au moins un premier dispositif d'émission en champ rapproché (102, 202) associé à la porte (104, 204), comprenant :
    - émission, par le premier dispositif d'émission en champ rapproché, d'au moins un premier signal comprenant au moins un premier identifiant d'émetteur du premier dispositif d'émission (102, 202),
    - où le premier signal est configuré pour susciter, sur un terminal mobile (106, 206, 306), une génération d'un ensemble de données d'accès avec au moins une clé correspondant au premier identifiant d'émetteur reçu et un identifiant d'accès sauvegardé sur le terminal mobile (106, 206, 306),
    - où le terminal mobile (106, 206, 306) comprend un dispositif de génération de code (350), où le terminal mobile (106, 206, 306) reçoit le premier signal et le traite de telle sorte que l'ensemble de données d'accès est généré localement,
    - où la clé est identique au premier identifiant d'émetteur reçu,
    - réception de l'ensemble de données d'accès du terminal mobile (106, 206, 306) par un dispositif d'interface (108, 208) de la porte (104, 204),
    - vérification d'autorisation d'accès au moins par comparaison de la clé reçue avec l'au moins un premier identifiant d'émetteur mis à disposition dans une première étape de vérification et
    - déverrouillage de l'accès par la porte (104, 204), au moins en dépendance du premier résultat de vérification,
    - où la réception de l'ensemble de données d'accès du terminal mobile (106, 206, 306) par le dispositif d'interface (108, 208) de la porte (104, 204) comprend la capture d'un code à barres et/ou d'un code QR affiché par le terminal mobile (106, 206, 306) par le dispositif d'interface (108, 208) de la porte (104, 204).
  2. Procédé selon la revendication 1, caractérisé en ce que le premier signal est un signal Bluetooth émis par une radiobalise Bluetooth (102, 201).
  3. Procédé selon l'une des revendications précédentes, caractérisé en ce que
    - la réception de l'ensemble de données d'accès comprend la réception de l'identifiant d'accès, et
    - le procédé comprend en outre :
    - vérification de l'autorisation d'accès par comparaison de l'identifiant d'accès reçu avec à au moins une liste d'autorisation sauvegardée dans un dispositif de stockage (216) de la porte (104, 204) dans une deuxième étape de vérification, et
    - déverrouillage de l'accès par la porte (104, 204), au moins en dépendance du résultat de la deuxième vérification.
  4. Procédé selon la revendication 3, caractérisé en ce que le procédé comprend en outre :
    - transmission de l'identifiant d'accès reçu de la porte (104, 204) à un dispositif de calcul central (222) situé à distance,
    - vérification, par le dispositif de calcul central (222), si l'identifiant d'accès transmis est un identifiant d'accès admissible dans une troisième étape de vérification, et
    - effectuer une mise à jour de la liste d'autorisation stockée dans le dispositif de stockage (216) de la porte (204), au moins en dépendance du résultat de la troisième vérification.
  5. Procédé selon l'une des revendications précédentes, caractérisé en ce que
    - le premier signal comprend un horodatage représentant l'instant d'émission du premier signal,
    - où le premier signal est configuré pour susciter sur le terminal mobile (106, 206, 306) la génération de l'ensemble de données d'accès avec une information temporelle correspondant à l'horodatage, où le terminal mobile (106, 206, 306) reçoit le premier signal et le traite de telle sorte que l'ensemble de données d'accès est généré localement, et
    - le procédé comprend en outre :
    - réception de l'ensemble de données d'accès comprenant l'information temporelle du terminal mobile (106, 206, 306) par le dispositif d'interface (108, 208) de la porte (104, 204),
    - vérification de l'autorisation d'accès par comparaison des informations temporelles avec une durée autorisée dans une quatrième étape de vérification, et
    - déverrouillage de l'accès par la porte (104, 204), au moins en dépendance du résultat de la quatrième vérification.
  6. Procédé selon l'une des revendications précédentes, caractérisé en ce que
    - le premier signal est configuré pour activer un dispositif de génération de code (350) disposé sur le terminai mobile (106, 206, 306),
    - où le dispositif de génération de code (350) comprend au moins un moyen de génération (340) configuré pour générer l'ensemble de données d'accès.
  7. Procédé selon l'une des revendications précédentes, caractérisé en ce que le procédé comprend :
    - l'émission d'un deuxième signal par au moins un deuxième dispositif d'émission (226),
    - où le deuxième signal comprend au moins un ensemble de données de configuration comprenant au moins une information de réception sur le premier signal, et
    - où le terminal mobile (106, 206, 306) est configuré pour recevoir le premier signal uniquement après la réception préalable des informations de réception du deuxième signal.
  8. Procédé selon l'une des revendications précédentes, caractérisé en ce que le procédé comprend :
    - émission d'au moins un troisième signal comprenant au moins un ensemble de données relatives à la localisation après un déverrouillage de l'accès par la porte (104, 204),
    - où l'ensemble de données relatives à la localisation est généré au moins basé sur des données de site de la porte (104, 204).
  9. Procédé selon la revendication 8, caractérisé en ce que l'ensemble de données relatives à la localisation est généré sur la base d'un ensemble de données de mouvement saisi du terminal mobile (106, 206, 306).
  10. Système d'accès (100, 200) avec au moins une porte (104, 204) et au moins un terminal mobile (106, 206, 306), comprenant:
    - au moins un premier dispositif d'émission en champ rapproché (102, 202) associé à l'au moins une porte (104, 204), configuré pour émettre au moins un premier signal comprenant au moins un premier identifiant d'émetteur du premier dispositif d'émission (102, 202),
    - où le premier signal est configuré pour susciter sur un terminal mobile (106, 206, 306) une génération d'un ensemble de données d'accès avec au moins une clé correspondant au premier identifiant d'émetteur reçu et un identifiant d'accès sauvegardé sur le terminal mobile (106, 206, 306), où le terminal mobile (106, 206, 306) est configuré pour sauvegarder l'identifiant d'accès, où le terminal mobile (106, 206, 306) comprend un moyen de génération de code (350), où le terminal mobile (106, 206, 306) est configuré pour recevoir le premier signal et pour traiter de telle sorte que l'ensemble de données d'accès est généré localement, où la clé est identique au premier identifiant d'émetteur reçu,
    - où la porte (104, 204) comprend au moins un dispositif d'interface (108, 208) configuré pour recevoir l'ensemble de données d'accès du terminal mobile (106, 206,306),
    - où la porte (104, 204) comprend au moins un dispositif de vérification (216) au moins adapté pour vérifier l'autorisation d'accès au moins par comparaison de la clé reçue avec le au moins un premier identifiant d'émetteur fourni dans une première étape de vérification, et
    - où la porte (104, 204) comprend au moins un dispositif de déverrouillage (118, 218) configuré pour déverrouiller l'accès par la porte (104, 204) au moins en dépendance du premier résultat de vérification,
    - où la réception de l'ensemble de données d'accès du terminal mobile (106, 206, 306) par le dispositif d'interface (108, 208) de la porte (104, 204) comprend la capture d'un code à barres et/ou d'un code QR affiché par le terminal mobile (106, 206, 306) par le dispositif d'interface (108, 208) de la porte (104, 204).
EP17164187.1A 2017-03-31 2017-03-31 Procédé de fonctionnement d'un système d'accès Active EP3382657B1 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PL17164187.1T PL3382657T3 (pl) 2017-03-31 2017-03-31 Sposób obsługi systemu dostępu
EP17164187.1A EP3382657B1 (fr) 2017-03-31 2017-03-31 Procédé de fonctionnement d'un système d'accès
HUE17164187A HUE059098T2 (hu) 2017-03-31 2017-03-31 Eljárás hozzáférési rendszer üzemeltetésére
ES17164187T ES2919127T3 (es) 2017-03-31 2017-03-31 Procedimiento para hacer funcionar un sistema de acceso

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP17164187.1A EP3382657B1 (fr) 2017-03-31 2017-03-31 Procédé de fonctionnement d'un système d'accès

Publications (2)

Publication Number Publication Date
EP3382657A1 EP3382657A1 (fr) 2018-10-03
EP3382657B1 true EP3382657B1 (fr) 2022-06-08

Family

ID=58548971

Family Applications (1)

Application Number Title Priority Date Filing Date
EP17164187.1A Active EP3382657B1 (fr) 2017-03-31 2017-03-31 Procédé de fonctionnement d'un système d'accès

Country Status (4)

Country Link
EP (1) EP3382657B1 (fr)
ES (1) ES2919127T3 (fr)
HU (1) HUE059098T2 (fr)
PL (1) PL3382657T3 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020243950A1 (fr) * 2019-06-06 2020-12-10 中控智慧科技股份有限公司 Grille barrière
US11631329B2 (en) 2020-07-08 2023-04-18 Honda Motor Co., Ltd Venue location identification for vehicular access control
DE102021130970A1 (de) 2021-11-25 2023-05-25 Scheidt & Bachmann Gmbh Fest montierte Ticketerfassungsvorrichtung für ein Zugangskontrollsystem

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102013013391A1 (de) * 2013-08-13 2015-02-19 Huf Hülsbeck & Fürst Gmbh & Co. Kg Authentifizierungsverfahren zur Berechtigungsüberprüfung eines Benutzers bei einem Kraftfahrzeugschließsystem

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100307206A1 (en) * 2009-06-08 2010-12-09 Harrow Products Llc Electronic door lock for reduced power consumption
US8396485B2 (en) * 2010-11-09 2013-03-12 Apple Inc. Beacon-based geofencing
US20130082820A1 (en) * 2011-09-29 2013-04-04 Delphi Technologies, Inc. Unattended fleet vehicle security system and method
US9520939B2 (en) * 2013-03-06 2016-12-13 Qualcomm Incorporated Methods and apparatus for using visible light communications for controlling access to an area
AU2014342341B2 (en) 2013-10-29 2019-07-25 Cubic Corporation Fare collection using wireless beacons
CN107005798B (zh) * 2014-12-02 2021-11-09 开利公司 在与多个进入控制交互时捕获用户意图

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102013013391A1 (de) * 2013-08-13 2015-02-19 Huf Hülsbeck & Fürst Gmbh & Co. Kg Authentifizierungsverfahren zur Berechtigungsüberprüfung eines Benutzers bei einem Kraftfahrzeugschließsystem

Also Published As

Publication number Publication date
ES2919127T3 (es) 2022-07-22
HUE059098T2 (hu) 2022-10-28
EP3382657A1 (fr) 2018-10-03
PL3382657T3 (pl) 2022-08-01

Similar Documents

Publication Publication Date Title
DE102013203949B4 (de) Kommunikationssystem, Kommunikationsverfahren und tragbares Gerät
DE102006042358B4 (de) Verfahren und Servicezentrale zum Aktualisieren von Berechtigungsdaten in einer Zugangsanordnung
EP3382657B1 (fr) Procédé de fonctionnement d'un système d'accès
EP3704674B1 (fr) Système et procédé de contrôle d'accès de personnes
DE102019123628A1 (de) Authentifizierungssystem und Authentifizierungsverfahren
EP3407307B1 (fr) Système de stationnement et son procédé de fonctionnement
DE102014116183A1 (de) Verfahren zum Bereitstellen eines Zugangscodes auf einem portablen Gerät und portables Gerät
EP3955219A2 (fr) Procédé de fonctionnement d'un dispositif de stationnement
WO2013007555A1 (fr) Procédé permettant d'exploiter un dispositif de réseau
EP3910606A1 (fr) Système d'accès pourvu d'au moins un portail
DE102010047257A1 (de) Mobilfunkbasiertes Transaktionssystem
EP3621042B1 (fr) Procédé de vérification
EP2081140A1 (fr) Procédé et système destinés à la protection d'une transaction
EP3306578A1 (fr) Autorisation d'ouverture d'un compartiment de réception d'un véhicule téléguidé
EP3708413A1 (fr) Procédé de démarrage d'un processus de charge à une station de charge
EP2996299B1 (fr) Procédé et système d'autorisation d'une action sur un système auto-commandé
EP3335199A1 (fr) Procédé et dispositif pour effectuer un contrôle de personnes
EP3252697B1 (fr) Dispositif de validation pour un systeme de ticket
EP3910603A1 (fr) Système de stationnement
WO2013110407A1 (fr) Commande d'accès
EP3817406B1 (fr) Procédé de fonctionnement d'une application de service installée sur un dispositif terminal mobile
EP3404627A1 (fr) Système d'accès et son procédé de fonctionnement
DE102014225484A1 (de) Anordnung und Verfahren zur Positionsbestimmung in Gebäuden
EP3300037B1 (fr) Dispositif de gestion d'accès, dispositif d'évaluation des informations d'accès et procédé de gestion d'accès
DE102014209191A1 (de) System und Verfahren zum Herunterladen von auf einem Tachografen gespeicherten Daten

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

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

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

RBV Designated contracting states (corrected)

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

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

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

RIC1 Information provided on ipc code assigned before grant

Ipc: G07C 9/00 20200101ALN20211115BHEP

Ipc: G07C 9/20 20200101ALI20211115BHEP

Ipc: G07C 9/10 20200101AFI20211115BHEP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 502017013267

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: G07C0009000000

Ipc: G07C0009100000

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

RIC1 Information provided on ipc code assigned before grant

Ipc: G07C 9/00 20060101ALN20220107BHEP

Ipc: G07C 9/20 20200101ALI20220107BHEP

Ipc: G07C 9/10 20200101AFI20220107BHEP

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

Ref legal event code: REF

Ref document number: 1497452

Country of ref document: AT

Kind code of ref document: T

Effective date: 20220615

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

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

Ref legal event code: FP

REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2919127

Country of ref document: ES

Kind code of ref document: T3

Effective date: 20220722

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: HU

Ref legal event code: AG4A

Ref document number: E059098

Country of ref document: HU

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 502017013267

Country of ref document: DE

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

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

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

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

Ref country code: IE

Payment date: 20230323

Year of fee payment: 7

Ref country code: FR

Payment date: 20230323

Year of fee payment: 7

Ref country code: CZ

Payment date: 20230228

Year of fee payment: 7

26N No opposition filed

Effective date: 20230310

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

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

Ref country code: PL

Payment date: 20230322

Year of fee payment: 7

Ref country code: IT

Payment date: 20230323

Year of fee payment: 7

Ref country code: HU

Payment date: 20230303

Year of fee payment: 7

Ref country code: GB

Payment date: 20230322

Year of fee payment: 7

Ref country code: DE

Payment date: 20230322

Year of fee payment: 7

Ref country code: BE

Payment date: 20230322

Year of fee payment: 7

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

Effective date: 20230427

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

Ref country code: NL

Payment date: 20230322

Year of fee payment: 7

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

Ref country code: ES

Payment date: 20230421

Year of fee payment: 7

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

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

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

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

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230331

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230331

REG Reference to a national code

Ref country code: AT

Ref legal event code: MM01

Ref document number: 1497452

Country of ref document: AT

Kind code of ref document: T

Effective date: 20230331