EP1814088B1 - Système comprenant plusieurs dispositifs de puissance avec dispositifs de contrôle d'accès - Google Patents
Système comprenant plusieurs dispositifs de puissance avec dispositifs de contrôle d'accès Download PDFInfo
- Publication number
- EP1814088B1 EP1814088B1 EP06001818A EP06001818A EP1814088B1 EP 1814088 B1 EP1814088 B1 EP 1814088B1 EP 06001818 A EP06001818 A EP 06001818A EP 06001818 A EP06001818 A EP 06001818A EP 1814088 B1 EP1814088 B1 EP 1814088B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- transaction
- data
- read
- database
- group
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Not-in-force
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/20—Individual registration on entry or exit involving the use of a pass
- G07C9/21—Individual registration on entry or exit involving the use of a pass having a variable access code
-
- 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
- G07C9/28—Individual registration on entry or exit involving the use of a pass the pass enabling tracking or indicating presence
Definitions
- the invention relates to a method for access control to at least two groups of transport devices, to each of which at least one access control device is provided, according to the preamble of claim 1. It also has an apparatus for performing the method of the subject.
- the read / write device reads out the application data from the data carrier, e.g. have been coded at a checkout with a data input device to the disk. If the read application data give a valid authorization to access a transport device, such as a ski lift, the access control device releases the access to the transport device.
- the checking of the application data can be done, for example, by the read / write device, which reads out the application data and controls the access control device, or e.g. when accessing multiple access lanes with a PC.
- ski lifts of a winter sports region are often far apart. So one group of ski lifts can be in one valley and another group in a valley far away. Although it is possible to network the ski lifts of the individual valleys with a common database. However, the networking of all ski lifts of all valleys requires a considerable effort.
- a chip card which has, in addition to an identification area, a transaction counter which increments by a value of 1 after a debiting operation in a terminal. All transactions are stored in the terminal and, if necessary, transferred to a background system, ie to a central database.
- the object of the invention is therefore, in two or more groups of transport devices that are far apart, the reading time at the access control device to shorten in a simple manner, if only one disk is used.
- the data carrier having an identification number is additionally provided with a transaction counter.
- the application data and a transaction count are written to disk.
- the identification number, the application data and this transaction number are stored in the database of the group of transport devices that the user visits with the data carrier.
- Transport device of this group is read with the read / write device of the access control device of the transport device, the identification number and the transaction number from the transaction counter of the disk and in accordance with the read identification number and transaction number with the database stored in the database identification number and transaction number - instead of reading and checking the Application data from the data carrier - a readout of the application data from the database and a subsequent review of the application data, wherein the access control device releases access in the case of a valid access authorization check.
- the examination of the application data can be done, for example, directly by the read / write device that controls the access control device, by a PC or the like computer, which controls several access control devices, especially in an access with multiple access tracks, each with an access control device with a read / write device, or directly the server of the database.
- the transaction counter and the identification number of the data carrier are thus used together as the key for the database of the relevant group of transport devices. If the user stays with the data carrier in the area of this group, reading the serial number and the transaction number from the data carrier with the read / write device at the access control device suffices. Thus, the reading duration can be shortened to 25 ms to 50 ms or less, for example.
- the database with which the read / write device is networked will contain the reads out the data carrier, changes the transaction number and stores the changed application data and stores the changed transaction number on the transaction counter of the data carrier, together with the changed application data.
- the transport devices may e.g. Be ski lifts.
- each group While the transport devices and their read / write devices of each group are adjacent to each other and networked with a common database, according to the invention, the groups can be far away from each other without additional effort.
- one group may be ski lifts or similar transport facilities in one valley and the other group may be ski lifts and the like in a valley far away from it.
- the invention is particularly intended for non-contact data carriers, in particular RFID data carriers. It is particularly suitable for "hands free" data with a data transmission distance of more than 100 mm.
- the unambiguous identification number of the data carrier is preferably the serial number of the chip of the RFID data carrier.
- the access control device may be a turnstile, a light barrier or other motunterzelungs announced.
- the release of the access with a turnstile can take place in that the locked turnstile is transferred to the release position or in the release position located turnstile remains open.
- the invention has proven particularly suitable for an access control device according to German patent no. 10 2004 013 965 proved. Two antennas are successively provided at the access, wherein the access control device is controlled as a function of the reading with the first and the second antenna and the detection of a person with a personal sensor.
- the period of time for reading the data carrier is reduced to a particularly short period of time, namely the time span in which the area of the first antenna is passed.
- the storage of the application data, the identification number and the transaction number of the transaction counter of the data carrier in the database can be done in various ways.
- the application data, the identification number and the transaction number can be read out with the read / write device of an access control device of the relevant group and stored on the database with which this read / write device is networked ,
- a data entry device is provided at a ticket counter or the like point of sale networked with the database of the adjacent group of service facilities.
- the application data is encoded on the data carrier and a transaction number on the transaction counter the data carrier, and on the other hand at the same time the identification number, the application data and the transaction number are stored in the database of this group.
- the data input device may also be formed by a PC or similar terminal, which may be e.g. connected to the database via the Internet.
- the identification number can be visibly attached to the data carrier or read out by the data entry device.
- the application data, the identification number and the transaction number that have been read from the data carrier with the read / write device are stored in stored in the database.
- the invention is particularly suitable for data carriers with an access authorization, which extends to a certain period, so for example for time cards, such as multi-hour, half-day, daily, multi-day, weekly, monthly or season tickets.
- time cards such as multi-hour, half-day, daily, multi-day, weekly, monthly or season tickets.
- the data carrier can also be designed in another way, for example in the form of a wristwatch.
- This can be a validity period, eg one day, or eg two half days. These validity periods then form part of the application data. If the validity period changes, for example the first half of the day on which the data carrier is stored, on which a total of two half days are stored, this changes the application data.
- the changed application data is stored on the data carrier with a changed transaction number in the database and with the read / write device. That is, every time you write with a read / write device, the transaction count is changed.
- the identification number, the changed application data and the changed transaction number of the transaction counter are read with a read / write device of the other group and stored in the database of this group.
- the invention is particularly suitable for so-called election subscriptions.
- the access authorization data defines a total validity period and, within the overall validity period, one or more individual validity periods for using the transport facilities of the groups comprising the system. This may be, for example, a disk that is valid for a total of one week, but this week, for example, only five days or seven half-days or the like time-limited individual validity periods.
- the data carrier must therefore be read when it must be written outside the network of a group of transport facilities. If the volume stays within a group, the reading of the identification number and the transaction number is sufficient.
- the transaction count can be formed by a storage space on the data carrier which is overwritten when the application data is changed with a new transaction number.
- the transaction counter may be formed by a count logic integrated into the volume, whereby upon a change in the application data, the transaction number is changed either automatically or on command.
- the application or application data include e.g. in addition to the total validity period and / or individual periods of validity, all data required by the data carrier for the processing of the access control.
- each data carrier there is applied a transaction counter which, together with the one-to-one identification number, e.g. the serial number of the volume used as the key for the central database of each network of a group of transport facilities.
- the one-to-one identification number e.g. the serial number of the volume used as the key for the central database of each network of a group of transport facilities.
- the data carrier is first described with the application or application data, for example, at the point of sale and then with the read / write device of an access control device whenever it is debited, that is, the transaction number is changed on the transaction counter.
- the application data plus identification number plus transaction number are stored in the database of the network of the relevant group.
- Reading with the read / write device of an access control device involves reading the identification number and the transaction number from the data carrier. The query then takes place in the database of the respective network. If an entry with an identical combination of identification number and transaction number exists in the database, the application data from the database is used for the further transaction. However, if there is no entry with an identical combination of identification number and transaction number in the database, the application data are read with the read / write device from the disk. That is, if the disk lingers in the network of a group of transport facilities, that's enough Reading the identification number and the transaction number from the disk with the read / write device.
- FIG. 1 are two groups of performance facilities, namely the ski areas A and B, provided with ski lifts 1 and 2 or 3 and 4 or the like transport facilities.
- the ski areas A and B form a winter sports region.
- Each ski lift 1 to 4 is in each case provided with an access control device 5 to 8 with a turnstile 9 to 12 or the like Mounterzelungs observed having a read / write device 13 to 16.
- FIG. 1 At each lift 1 to 4 only one control device 5 to 8 with a turnstile 9 to 12 and a read / write device 13 to 16 is shown. At a lift, however, several access tracks can be provided, each with an access control device with a read / write device.
- the group A read / write devices 13, 14 and group B write / read devices 15, 16 are networked to a database 17, 18, respectively, via lines 13a through 16a.
- the database 17 of the group A is also connected via the line 19a to the data input device 19, that is, for example, a cash register on which the data carrier 20 is purchased.
- the data carrier 20 has an identification number 21, for example the serial number of the chip of the RFID data carrier, for example "7412".
- the data carrier 20 is provided with a transaction counter 22.
- a transaction number for example "1”
- the data input device 19 in the transaction counter 22 furthermore the application data 23 including the validity data.
- the identification number and the application data in the electronic data carrier 20 are, as usual, stored in binary form, as well as the transaction number.
- the application data includes as validity dates, for example, the date of the first day, e.g. "10.01.XX", and the last day, e.g. "17.01.XX", the total validity period of the data carrier and the days or individual validity periods "5" that the data carrier 20 applies within the total validity period.
- the transaction count of the transaction counter 22 is assigned to the days or individual periods as a reference.
- the identification number 21 (“7412"), the transaction number ("1") and the application data 23 including validity periods (5 days valid in the period 10.01.-17.01.XX) are at the same time the purchase of the disk 20 with the data input device 19 to the database 17 of the ski A transmitted and stored there.
- the read / write device 13 of the access control device 15 receives the identification number 21 ("7412") and the transaction number ("1"). from the transaction counter 22 read. With the access to the lift 1, the skier has taken the first day of the five days on which the disk 20 applies. The disk 20 is therefore only four more days. In the database 17, therefore, an update of the application data is made, and the changed application data is assigned the transaction number "2". At the same time, the modified application data are stored in the data carrier 20 with the read / write device 13, as is the transaction number "2" in the transaction counter 22 of the data carrier 20.
- the read / write device 13 and 14 of the access control device 5 and 6 Upon renewed access on the first day to one of the lifts 1, 2 of the ski A is read with the read / write device 13 and 14 of the access control device 5 and 6, the identification number 21 and the transaction number "2" of the transaction counter 22 from the disk 20 and if the read identification number 21 and the number of transactions match the identification number and transaction number stored in the database 17, the application data is read from the database 17 and the read application data is checked as to whether it contains a valid access authorization. If this is the case, the turnstile is 9 or 10 driven so that the access to the lift 1 or 2 is released. The verification of the application data to a valid access authorization can be done by the read / write device 13 and 14, which also controls the turnstile 9 and 10 respectively.
- the data transmission between the read / write device 13 and the database 17 takes place online and thus very fast.
- the transaction number (“2") and the identification number 21 (“7412") form the key to access the ski lifts 1, 2 in the ski area A.
- the read / write device 13 only the identification number 21 is needed and the transaction number of the transaction counter 22 are read without contact, so that the reading time is reduced to, for example, 25 ms to 50 ms.
- the identification number 21 and the application data 23 of the database 18 are transmitted with the read / write device 15 of the access control device 7 on access to the lift 3. Since the access authorization data has changed, namely only three more days within the remaining validity period until 17.01.XX, the transaction number is stored in the database 18 e.g. is changed to "3" and the changed transaction number is stored in the transaction counter 22 of the data carrier 20, together with the changed application data 23.
- the read / write device 14 of the access control device 6 becomes the identification number 21, the changed transaction number ("3") of the transaction counter 22 and the changed application data 23 of the data carrier 20 are read from the data carrier 20 and stored in the database 17.
- the read / write device 13, 14 of the access control device 5 6 read only the identification number 21 and the transaction number on the transaction counter 22 of the disk and with the in the Database 17 stored identification number and transaction number matched, read the application data from the database 17 and to be checked by the read / write device 13 and 14 to a valid access authorization.
- the application data 23, including the authorization data 24 of the disk 20 must be read and stored in the respective database 17, 18, while if the skier in the ski resort A, B, to which he has changed, dwells, with each further use of the lifts 1, 2 or 3, 4 of this ski A, B with the read / write device 13, 14 and 15, 16 only the identification number 21 and the transaction number of the transaction counter 2 must be read to read the application data from the database 17, 18.
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Selective Calling Equipment (AREA)
- Remote Monitoring And Control Of Power-Distribution Networks (AREA)
- Storage Device Security (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Devices For Checking Fares Or Tickets At Control Points (AREA)
Claims (11)
- Procédé de contrôle d'accès à au moins deux groupes (A, B) de dispositifs de transport (1 à 4) sur chacun desquels est prévu au moins un dispositif de contrôle d'accès (5 à 8) avec au moins un dispositif d'écriture/de lecture (13 à 16) pour des supports de données (20), les dispositifs d'écriture/de lecture (13 à 16) de chaque groupe (A, B) étant reliés en réseau avec une banque de données (17, 18), et le support de données (20) présentant un numéro d'identification (21) et des données d'application (23) étant stockées en mémoire sur le support de données (20), caractérisé en ce qu'un support de données (20) est utilisé avec un compteur de transactions (22) avec un chiffre de transaction qui est modifié en cas de modification des données d'application (23), les données d'application (23), le numéro d'identification (21) et le chiffre de transaction du compteur de transactions (22) du support de données (20) sont stockés en mémoire dans la banque de données (17, 18) du groupe (A, B) des dispositifs de transport (1 à 4) que l'utilisateur consulte, et en cas d'accès à un dispositif de transport (1 à 4) de ce groupe (A, B), le numéro d'identification (21) et le chiffre de transaction étant lus du compteur de transactions (22) du support de données (20) avec le dispositif d'écriture/de lecture (13 à 16), et en cas de concordance du numéro d'identification (21) lu par le support de donnée (20) et du chiffre de transaction lu par le compteur de transactions (22) avec le numéro d'identification et le chiffres de transaction stockés en mémoire dans la banque de données (17, 18), les données d'application sont prélevées de la banque de données, et en cas de validité de l'examen d'autorisation d'accès, le dispositif de contrôle d'accès respectif (5 à 8) autorise l'accès, et dans le cas d'un changement d'un groupe (A, B) à un autre groupe (A, B) de dispositifs de transport (1 à 4), le numéro d'identification (21), les données d'application (23) et le chiffre de transaction du compteur de transaction (22) sont lus avec un dispositif d'écriture/de lecture (13 à 16) du groupe (A, B) vers lequel le changement a eu lieu, et stockés en mémoire dans la banque de données (17, 18) de ce groupe (A, B).
- Procédé selon la revendication 1, caractérisé en ce que les données d'application (23), le numéro d'identification (21) et le chiffre de transaction du compteur de transactions (22) du support de données (20) sont lus avec le dispositif d'écriture/de lecture (13 à 16) du dispositif de contrôle d'accès (5 à 8) d'un groupe (A, B) du dispositif de transport (1 à 4) et stockés en mémoire dans la banque de données (17, 18) du groupe (A, B).
- Procédé selon la revendication 1 ou 2, caractérisé en ce qu'en cas de modification des données d'application (23), le compteur de transactions (22) modifie le chiffre de transaction par une logique de comptage intégrée dans le support de données (20) soit automatiquement soit sur ordre.
- Dispositif de mise en oeuvre du procédé selon l'une quelconque des revendications précédentes, caractérisé par au moins deux groupes (A, B) de dispositifs de transport (1 à 4) sur chacun desquels est prévu au moins un dispositif de contrôle d'accès (5 à 8) avec au moins un dispositif d'écriture/de lecture (13 à 16) pour des supports de données (20), les dispositifs d'écriture/de lecture (13 à 16) de chaque groupe (A, B) étant reliés en réseau avec une banque de données (17, 18), et le support de données (20) présentant un numéro d'identification (21) et des données d'application (23) pouvant être stockées en mémoire sur le support de données (20), le support de données (20) étant pourvu d'un compteur de transactions (22) avec un chiffre de transaction qui se modifie en cas de modification des données d'application (23), les données d'application (23), le numéro d'identification (21) et le chiffre de transaction du compteur de transactions (22) du support de données (20) pouvant être stockés en mémoire dans la banque de données (17, 18) du groupe (A, B) des dispositifs de transport (1 à 4) que l'utilisateur consulte, et en cas d'accès à un dispositif de transport (1 à 4) de ce groupe (A, B), le numéro d'identification (21) et le chiffre de transaction pouvant être lus depuis le compteur de transactions (22) du support de données (20) avec le dispositif d'écriture/de lecture (13 à 16) pour, en cas de concordance du numéro d'identification (21) lu par le support de donnée (20) et du chiffre de transaction lu par le compteur de transactions (22) avec le numéro d'identification et le chiffres de transaction stockés en mémoire dans la banque de données (17, 18), prélever les données d'application de la banque de données et pour, en cas de validité de l'examen d'autorisation d'accès par le dispositif de contrôle d'accès respectif (5 à 8), autoriser l'accès, et dans le cas d'un changement d'un groupe (A, B) à un autre groupe (A, B) de dispositifs de transport (1 à 4), le numéro d'identification (21), les données d'application (23) et le chiffre de transaction du compteur de transaction (22) peuvent être lus avec un dispositif d'écriture/de lecture (13 à 16) du groupe (A, B) vers lequel le changement a eu lieu, et stockés en mémoire dans la banque de données (17, 18) de ce groupe (A, B).
- Dispositif selon la revendication 4, caractérisé en ce qu'il est prévu un dispositif d'entrée de données (19) par lequel les données d'application (23) peuvent être stockées en mémoire sur le support de données et un chiffre de transaction peut être stocké dans le compteur de transactions (22) du support de données (20).
- Dispositif selon la revendication 5, caractérisé en ce que le dispositif d'entrée de données (19) est relié en réseau avec la banque de données d'un groupe (A, B) des dispositifs de transport (1 à 4), et avec le dispositif d'entrée de données (19), les données d'application (23), le numéro d'identification (21) et le chiffre de transaction peuvent être stockés en mémoire dans la banque de données (17, 18) avec laquelle le dispositif d'entrée de données (19) est relié en réseau.
- Dispositif selon la revendication 4, caractérisé en ce qu'avec les données d'application (23) sont déterminées une ou plusieurs périodes de temps de validité pour utiliser les dispositifs de transport (1 à 4) des groupes (A, B) du système.
- Dispositif selon la revendication 7, caractérisé en ce qu'avec les données d'application (23) est déterminée une période de temps de validité totale, et dans la période de temps de validité totale sont déterminées une ou plusieurs périodes de temps de validité individuelle pour utiliser les dispositifs de transport (1 à 4) des groupes (A, B) du système.
- Dispositif selon la revendication 4, caractérisé en ce que le support de données (20) est un support de données travaillant sans contact.
- Dispositif selon la revendication 4, caractérisé en ce que le compteur de transactions (22) est formé par un emplacement de mémoire sur le support de données (20), qui est remplacé par un nouveau chiffre de transaction à chaque modification des données d'application (23).
- Dispositif selon la revendication 4, caractérisé en ce que le dispositif de contrôle d'accès (5 à 8) est formé par un dispositif d'individualisation de personnes.
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE502006000840T DE502006000840D1 (de) | 2006-01-30 | 2006-01-30 | System mit mehreren Leistungseinrichtungen mit Zugangskontrolleinrichtungen |
EP06001818A EP1814088B1 (fr) | 2006-01-30 | 2006-01-30 | Système comprenant plusieurs dispositifs de puissance avec dispositifs de contrôle d'accès |
AT06001818T ATE397259T1 (de) | 2006-01-30 | 2006-01-30 | System mit mehreren leistungseinrichtungen mit zugangskontrolleinrichtungen |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP06001818A EP1814088B1 (fr) | 2006-01-30 | 2006-01-30 | Système comprenant plusieurs dispositifs de puissance avec dispositifs de contrôle d'accès |
Publications (2)
Publication Number | Publication Date |
---|---|
EP1814088A1 EP1814088A1 (fr) | 2007-08-01 |
EP1814088B1 true EP1814088B1 (fr) | 2008-05-28 |
Family
ID=37441784
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP06001818A Not-in-force EP1814088B1 (fr) | 2006-01-30 | 2006-01-30 | Système comprenant plusieurs dispositifs de puissance avec dispositifs de contrôle d'accès |
Country Status (3)
Country | Link |
---|---|
EP (1) | EP1814088B1 (fr) |
AT (1) | ATE397259T1 (fr) |
DE (1) | DE502006000840D1 (fr) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7857213B2 (en) * | 2007-11-01 | 2010-12-28 | Skidata Ag | System having a plurality of service facilities with access control devices |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE3223034C2 (de) * | 1982-06-19 | 1986-12-11 | Mico Datensysteme GmbH, 7252 Weil der Stadt | Verfahren zur Erkennung von gefälschten Datenträgern |
EP0257596B1 (fr) * | 1986-08-26 | 1992-11-11 | Siemens Aktiengesellschaft | Procédé pour reconnaître un usage illicite d'une carte à circuit intégré |
US5317636A (en) * | 1992-12-09 | 1994-05-31 | Arris, Inc. | Method and apparatus for securing credit card transactions |
DE19604876C1 (de) * | 1996-02-10 | 1997-09-04 | Deutsche Telekom Ag | Verfahren zur Transaktionskontrolle elektronischer Geldbörsensysteme |
FR2781592B1 (fr) * | 1998-07-27 | 2000-09-08 | Gemplus Card Int | Procede de controle de l'execution d'une demande d'actions transmise par un serveur vers une carte a puce via un terminal |
US20020198848A1 (en) * | 2001-06-26 | 2002-12-26 | Michener John R. | Transaction verification system and method |
US7705732B2 (en) * | 2001-07-10 | 2010-04-27 | Fred Bishop | Authenticating an RF transaction using a transaction counter |
DE102004013965B3 (de) | 2004-03-19 | 2005-12-01 | Skidata Ag | Zutrittskontrollvorrichtung |
-
2006
- 2006-01-30 DE DE502006000840T patent/DE502006000840D1/de not_active Expired - Fee Related
- 2006-01-30 AT AT06001818T patent/ATE397259T1/de active
- 2006-01-30 EP EP06001818A patent/EP1814088B1/fr not_active Not-in-force
Also Published As
Publication number | Publication date |
---|---|
DE502006000840D1 (de) | 2008-07-10 |
ATE397259T1 (de) | 2008-06-15 |
EP1814088A1 (fr) | 2007-08-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
DE2512935C2 (de) | Datenaustauschsystem | |
DE3811378C3 (de) | Informationsaufzeichnungssystem | |
DE69014817T2 (de) | System zum Bezahlen oder Transferieren von Informationen mit einer als Geldbörse dienenden elektronischen Speicherkarte. | |
DE2612693A1 (de) | Bargeldausgabevorrichtung | |
DE19844360A1 (de) | Zugangskontrollsystem | |
DE2738113A1 (de) | Vorrichtung zur durchfuehrung von bearbeitungsvorgaengen mit einem in eine aufnahmeeinrichtung der vorrichtung eingebbaren identifikanden | |
DE2338365A1 (de) | Ueberpruefungs- oder kontrollsystem | |
DE3523237A1 (de) | Anordnung zum sichern des transports von chipkarten | |
DE69100001T2 (de) | Faelschungssichere karte, die einen aufzeichnungstraeger mit hochdichter information und eine mikroschaltung enthaelt und ihre anwendung bei einem kartenleser. | |
DE2044414A1 (de) | Einrichtung zum Ausscheiden ungültiger Karten in einer Kreditkarteneinrichtung oder dergleichen | |
EP1185960B1 (fr) | Procede et dispositif servant a sauvegarder et a retrouver des codes pin | |
DE69228388T3 (de) | Verfahren und vorrichtung zur überwachung, insbesondere zur zeit- und/oder durchgangskontrolle | |
EP1814088B1 (fr) | Système comprenant plusieurs dispositifs de puissance avec dispositifs de contrôle d'accès | |
EP1178452A2 (fr) | Méthode pour une transmission de données sécurisée dans les ventes de marchandises | |
DE68905505T2 (de) | Personenkontrollsystem unter verwendung von ic-karten. | |
EP0818749A2 (fr) | Procédé et système pour la protection de données | |
DE19856362C2 (de) | Datenaustauschsystem | |
DE10019469A1 (de) | Ausleihsystem für Sportgeräte | |
DE19816541A1 (de) | Datenaustauschsystem | |
DE2802472A1 (de) | Verfahren und anordnung fuer verschluesselung von identitaetsnachweis, kontofuehrung, datenspeicherung, oder fuer sicherung von gut und eigentum und/oder zum schutz vor inbetriebnahme elektrisch gesicherter einrichtungen durch unbefugte personen | |
DE202006020688U1 (de) | Wert-Bon-Entwertungssystem | |
WO1994000829A1 (fr) | Systeme de paiement | |
DE3922347A1 (de) | Diebstahlsichere berechtigungskarte, insbesondere kredit- und scheckkarte | |
AT500452B1 (de) | Verfahren zum betätigen zumindest einer sperrvorrichtung | |
DE10049261A1 (de) | Abrechnungssystem zur zentralen Zahlungsabwicklung durch ein biometrisches Merkmal |
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: 20070407 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR |
|
AX | Request for extension of the european patent |
Extension state: AL BA HR MK YU |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
AKX | Designation fees paid |
Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D Free format text: NOT ENGLISH |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REF | Corresponds to: |
Ref document number: 502006000840 Country of ref document: DE Date of ref document: 20080710 Kind code of ref document: P |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: NV Representative=s name: LEMAN CONSULTING S.A. |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D Free format text: LANGUAGE OF EP DOCUMENT: GERMAN |
|
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: 20080528 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080908 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: 20080528 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080528 Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080528 |
|
NLV1 | Nl: lapsed or annulled due to failure to fulfill the requirements of art. 29p and 29m of the patents act | ||
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: 20080928 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FD4D |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080528 Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080528 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: 20080528 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: 20080828 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: 20080528 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080528 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: 20081028 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: 20080528 |
|
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: 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: 20080528 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: 20080828 |
|
26N | No opposition filed |
Effective date: 20090303 |
|
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 NON-PAYMENT OF DUE FEES Effective date: 20090131 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20090801 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20090131 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080528 |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20100130 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20080829 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GB Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20100130 |
|
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: 20090130 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: HU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20081129 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: TR 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: 20080528 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20080528 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 11 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 12 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 13 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20191219 Year of fee payment: 15 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: CH Payment date: 20191224 Year of fee payment: 15 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: IT Payment date: 20200102 Year of fee payment: 15 Ref country code: AT Payment date: 20191223 Year of fee payment: 15 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MM01 Ref document number: 397259 Country of ref document: AT Kind code of ref document: T Effective date: 20210130 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: AT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20210130 Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20210131 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20210131 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20210131 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20210130 |