EP1285322A1 - Gestionnaire de licence - Google Patents
Gestionnaire de licenceInfo
- Publication number
- EP1285322A1 EP1285322A1 EP01936011A EP01936011A EP1285322A1 EP 1285322 A1 EP1285322 A1 EP 1285322A1 EP 01936011 A EP01936011 A EP 01936011A EP 01936011 A EP01936011 A EP 01936011A EP 1285322 A1 EP1285322 A1 EP 1285322A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- value points
- software modules
- wpn
- value
- licensing
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
- 238000000034 method Methods 0.000 claims abstract description 18
- 238000013475 authorization Methods 0.000 claims description 31
- 238000009434 installation Methods 0.000 claims description 3
- 238000005516 engineering process Methods 0.000 description 26
- 230000001360 synchronised effect Effects 0.000 description 18
- 230000012447 hatching Effects 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 239000004033 plastic Substances 0.000 description 3
- 229920003023 plastic Polymers 0.000 description 3
- 239000003795 chemical substances by application Substances 0.000 description 2
- 230000006735 deficit Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 230000006855 networking Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 102000005591 NIMA-Interacting Peptidylprolyl Isomerase Human genes 0.000 description 1
- 108010059419 NIMA-Interacting Peptidylprolyl Isomerase Proteins 0.000 description 1
- 239000000969 carrier Substances 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 239000000523 sample Substances 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
- G06F21/12—Protecting executable software
- G06F21/121—Restricting unauthorised execution of programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2135—Metering
Definitions
- the invention relates to a method for licensing and / or access authorization of software modules for indus ⁇ -industrial controllers Us / or computer systems.
- the object of the invention is to provide a user of software modules with a simple, flexible method for licensing and / or access authorization of software modules which is adapted to his changing requirements and which can be used in particular in distributed systems.
- this object is achieved in that a customer acquires value points as a user authorization for the desired software modules, each software module being assigned a value in the form of value points and that the customer is authorized if the number of value points acquired by the customer is at least the sum of the value points of the currently desired software modules is reached, whereby the current balance between acquired and used value points is continuously calculated and monitored by a license manager.
- software module is to be used synonymously with software program or software component.
- a major advantage of the invention is that a customer does not conclude a license agreement for the software modules used and their number, but acquires a license agreement for value points.
- the customer can use the software modules required in a flexible and needs-oriented manner within the "Value Points License" he has acquired. Instead of a price, the software modules are assigned a value in the form of value points, each value point having a price. Changes to the customer's requirements or new software components do not require a change in the license agreement if the value of the software modules currently required is compensated for by the value points already acquired.
- the use of value points as license The use of software modules greatly simplifies the administration and license administration of software for a system, but also for an entire company.
- the licensing procedure is simplified by the invention.
- the licensing also enables a high granularity and easy combinatorics of the software modules.
- the invention permits function-neutral pre-orders, ie a buyer does not have to commit himself to certain software modules when acquiring a license, but can acquire a number of value points and use them for any software modules.
- value points as the authorization currency for the use of software modules, the customer can be satisfied with changes in his software requirements without having to change the license agreement. This saves additional administration and administration processes.
- the customer can thus buy a voucher for a number of value points, so to speak, whereby he is allowed to flexibly exchange and exchange these value points in software modules.
- the customer can thus individually assemble his module delivery and does not have to accept packages prepared by the supplier.
- a further advantage of the invention is that the customer is authorized to use the software modules that are currently desired when the number of value points already acquired by the customer reaches at least the sum of the value points of the software modules currently desired.
- the usage authorization for customers is done by simply checking the total balance of the value points. Because dedicated value points are assigned to each software module, it is very easy to compare the sum of the value points of the currently desired software modules with those from the license agreement acquired value points are carried out. Insofar as the customer's value point account is not exceeded by the sum of the value points of the currently desired software modules, the customer is granted user authorization.
- a license manager permanently records the current number of required value points and compares them with the existing ones, a customer can be billed according to need or use. With the license manager, newly acquired value points can be easily integrated and taken into account in terms of licensing, but also additional value points required in an application can be easily recognized.
- the license manager continuously determines the "value point target", i.e. the sum of the value points of all currently required software modules, and compares them with the "value point having", i.e. the total credit of value points acquired through the license.
- a first advantageous embodiment of the invention is that the license manager is implemented as a mobile agent. This makes the licensing process very easy to use in distributed environments.
- the software modules that are subject to licensing can run on devices that e.g. Are connected via fieldbus connections, but also Local Area Network (LAN) or Internet or. Intranet connections are possible.
- LAN Local Area Network
- Intranet connections are possible.
- Another advantageous embodiment of the invention is that the system automatically calculates the value points required for an application. A user thus immediately recognizes which license costs (in the form of value points) the configuration of software modules selected by him, ie his applications, causes.
- the required value points can be determined by the license manager or, for example, by a routine in the engineering system for industrial controls.
- Another advantageous embodiment of the invention is that the value points are transmitted to the industrial controls or to the computer systems via a data line or via the Internet. This means that no data medium or other hardware component is required to transfer the license currency (value points) to the customer.
- Another advantageous embodiment of the invention is that the value points are supplied on a data carrier that is already available for the operation of the control or the computer system anyway. This makes handling on the control or computer system easier, but also saves storage space and storage costs.
- Another advantageous embodiment of the invention is that the value points are fed to the control or the computer system on a memory card.
- a memory card is usually used in control devices anyway and can be easily inserted into the slot provided.
- MMC memory cards are very suitable as carriers of information due to their size and shape. MMC memory cards are comparable in appearance to a small SIM card as they are known on mobile phones.
- a further advantageous embodiment of the invention is that the value points are fed in at one point or in one device or at different points, ie on several devices for the entire system or for the entire system.
- This enables a customer, for example, to obtain licensing information (license currency in the form of value points) for software components that cover the entire system or affect the entire system at a single point (e.g. device) and in the same way.
- This greatly simplifies license handling for a customer, particularly with regard to distributed applications and network operation.
- a further advantageous embodiment of the invention is that the target / actual comparison of the value points required for the access authorization takes place during the installation of the software modules. This means that it is only when a customer installs the software modules they have purchased on a device or system that a check is made as to whether the number of value points they have acquired is sufficient for the desired software modules.
- the fact that the customer's value point account is only debited when the software modules are loaded onto a device or system means that the check as to whether the customer is authorized to use the software modules takes place at the point in time at which the customer actually intends to use the To use modules.
- the billing of the value points is done for the customer according to need.
- Another advantageous embodiment of the invention is that the target / actual comparison required for the access authorization takes place when the software modules are used.
- the value points can thus be linked to the number of incarnations or instantiations of the software modules. This makes it possible to provide a customer with user-oriented licensing procedures for their respective requirements.
- a customer who uses a software module for motion controls e.g. a technology package
- the "Positioning” technology package includes the "Positioning axis" technology object.
- the number of incarnations or instances of the technology The "positioning axis" object or other technology objects are billed, ie his value point account is debited with the number of incarnations or instances of the technology objects. Due to the incarnation-related authorization at runtime, a customer's value point account is only debited by those software modules that he really needs and uses for his applications. There is therefore a very finely granular billing mechanism, and a customer only has to pay for the functionality required and used.
- FIG. 1 in a schematic representation software modules for a motion control
- FIG. 2 in a schematic representation a technology package positioning with contained technology objects
- FIG. 3 a scenario for the licensing and access authorization of software modules on a device
- FIG. 4 shows a scenario for the licensing and access authorization of software modules for several networked devices using value points
- FIG. 5 shows the structure of an MMC memory card
- FIG. 6 shows a schematic representation of the connection of control devices to a server via an Ethernet or internet connection.
- a motion control usually consists of a basic system BS and software modules POS (positioning), GL (synchronism), KS (cam), IP (interpolation), which a user can acquire depending on his requirements and applications.
- POS positioning
- GL synchronism
- KS cam
- IP interpolation
- a user or buyer has the option of purchasing software modules (POS) for positioning, (GL) for synchronization, (KS) for cams or (IP) for interpolation in addition to the BS base system.
- POS software modules
- GL for synchronization
- KS for cams
- IP IP
- a user or customer can also purchase software modules K (plastic) or WT (other technologies) for certain technologies.
- the software component K (plastic) can be acquired for motion controls which are to be used especially for processing plastics.
- FIG. 1 also shows that specific software components WT can also be acquired for other technologies. All software modules shown are assigned a value in the form of value points. A user can use the desired software modules flexibly within his acquired number of value points (licensing). A user can very easily achieve a technological scaling of his motion control by using certain software modules and thus receive a demand-oriented expression for his control task.
- the technology package includes the following technology objects (shown as rectangles): cam, external encoder, speed axis, probe and positioning axis. In one application, several incarnations or instances of these technology objects can be used by a user.
- the illustration according to FIG. 3 shows a scenario for the licensing and access authorization of software modules on a device using value points.
- Software modules requiring a license here for example instances of technology objects (represented as small circles), are to run on the device G (e.g. a motion control).
- the device G is represented by a rectangle.
- the device G is assigned an identification number PIN on an integrable MMC memory type MMC (symbolized by open arrows), which contains the software value in the form of 25 value points (WP).
- the identification number PIN which contains the software value in the form of value points, is symbolized by a small cross.
- the instances which are to run on the device G are represented by differently patterned small circles.
- a positioning axis instance is represented by a blank circle.
- the value of a positioning axis instance is five value points.
- a synchronized axis instance is represented by a circle with hatching from bottom left to top right.
- the value of a synchronous axis instance is eight value points.
- 3 positioning axis instances should be on device G. (each require 5 WP) and a synchronization instance (requires 8 WP) are running.
- WP value points
- the boxed field at the top right in FIG. 4 shows the required value points.
- a software-implemented license manager continuously checks the target / actual balance at required and existing WP value points.
- the license manager can e.g. be integrated in the base system BS (FIG 1) of the control.
- FIG. 4 shows a scenario for the licensing and access authorization of software modules for several networked devices using value points.
- the system shown consists of three networked devices G1, G2 and G3, the devices being represented by rectangles and the networking being symbolized by connecting lines.
- Each device Gl - G3 is assigned an identification number PIN on an integrable (symbolized by open arrows) MMC memory card MMCl - MMC3, which contains the software value in the form of value points.
- MMCl contains ten
- MMC2 also ten
- the identification number PIN which contains the software value in the form of value points is symbolized by a small cross.
- the software modules that are to run on the devices Gl - G3 are represented by small circles with different patterns. In FIG. 4, the software modules are interpreted as instantiations or instances of object types.
- a positioning axis instance is represented by a blank circle. The value of a positioning axis instance is five value points.
- a synchronized axis instance is represented by a circle with hatching from bottom left to top right. The value of this synchronous axis instance is eight value points.
- a synchronized axis instance with cam is represented by a circle with hatching from top left to bottom right. The value of this software module is ten value points.
- the acquired value points (software value) are encrypted with an identification number PIN.
- the identification numbers PIN are inserted into the system or onto the devices Gl - G3 via MMC memory cards MMCl - MMC3 on which they are located.
- the MMCl memory card contains ten value points
- the MMC2 memory card also contains ten value points
- the MMC3 memory card contains twenty value points.
- the value points present in the system or on the devices are shown in the field at the top left of the display, for a total of forty value points are in the system.
- the existing WP value points can be viewed as credit or as credit points.
- a total of forty value points are available across the three MMC memory cards MMCl - MMC3.
- the license manager keeps a permanent record of the WP value points required by an application and compares them with the WP value points available in the overall system. If a shortage of value points is detected, it does not allow operation in the current constellation.
- the number of required value points may exceed the number of existing value points.
- two synchronous axes with sixteen necessary value points run on the device G2.
- only ten value points are stored on the local MMC memory card MMC2 for device G2.
- this local deficit in value points is compensated for by the value points that were applied to the remaining devices. It is thus also conceivable that individual devices are not assigned any value points at all and that the software components assigned to these devices can still be properly run under license if only the total sum of the value points available in the system is sufficient. It is also possible to bring all the required value points into the system on just one device.
- the MMC memory card is divided into blocks.
- the top block is the Card Identification Block, which is described by the MMC memory card manufacturer becomes.
- This card identification block contains the unique hardware identifier PSN. This area is only readable (by the verification software) and can no longer be copied.
- the next blocks each contain the value points WP1 - WPn, additional information ZU - ZIn (e.g. information from different licensors), as well as identification numbers PIN1 - PINn generated by an encryption algorithm (for different licensors). Programs and data can also be stored on an MMC memory card.
- FIG. 6 shows a controller that consists of three networked devices G1, G2 and G3, the devices being represented by rectangles and the networking being symbolized by connecting lines.
- the control is e.g. connected to a server S via an Ethernet or Internet connection, which among other things contains a value point account. Via this Ethernet or Internet connection, value points can be transferred to the controller to devices Gl - G3.
- the server S is represented by a rectangle on the right side of FIG.
- the software modules (in FIG. 6 examples of technology object instances are shown) which are to run on the devices G1-G3 are represented by small circles with different patterns.
- a positioning axis instance is represented by a blank circle.
- the value of a positioning axis instance is five value points (5 WP).
- a synchronized axis instance is represented by a circle with hatching from bottom left to top right.
- the value of this synchronous axis instance is eight value points (8 WP).
- Through a hatched circle from top left to right A synchronized axis instance with cam is shown below, the value of which is ten value points (10 WP).
- the value point account of server S has ten WP for device Gl, ten WP for device G2 and twenty value points for device G3, so the controller has a total of 40 WP available.
- device Gl requires a positioning axis instance, i.e. 5 WP and a synchronous axis instance, i.e. 8 WP
- device G2 requires two synchronized axis instances, i.e. 2x8 WP
- device G3 require a synchronous axis instance with cam, i.e. 10 WP.
- the field in the middle shows the value points required in the system, namely thirty-nine.
- the required value points represent the consumption or the desired value point. Since there are sufficient value points in total in the system (forty), operation in this constellation, which requires thirty-nine value points, is permissible and in accordance with licensing law. The total sum of the value points in the system is decisive for the access authorization.
- the number of required value points may exceed the number of existing value points.
- two synchronized axes with sixteen necessary value points run on the device G2.
- only ten value points are stored in the account of server S for device G2.
- this local deficit in value points is compensated for by the value points that are assigned to the remaining devices. It is therefore also conceivable that no individual value points are assigned to individual devices and that the software modules assigned to these devices can still be properly executed under license if only the total sum of the value point values available in the system te is sufficient. It is also possible to assign all the value points WP required for the operation of the control to only a single device of the control.
- a software-implemented license manager continuously checks the target / actual balance at required and existing value points WP.
- the license manager could be implemented as a mobile agent in a distributed operation (e.g. distributed over a local area network or over the Internet).
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Computer Security & Cryptography (AREA)
- Theoretical Computer Science (AREA)
- Multimedia (AREA)
- Technology Law (AREA)
- Computer Hardware Design (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Storage Device Security (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE10023818 | 2000-05-15 | ||
DE10023818A DE10023818A1 (de) | 2000-05-15 | 2000-05-15 | Lizenzmanager |
PCT/DE2001/001634 WO2001088669A1 (fr) | 2000-05-15 | 2001-04-30 | Gestionnaire de licence |
Publications (1)
Publication Number | Publication Date |
---|---|
EP1285322A1 true EP1285322A1 (fr) | 2003-02-26 |
Family
ID=7642157
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP01936011A Ceased EP1285322A1 (fr) | 2000-05-15 | 2001-04-30 | Gestionnaire de licence |
Country Status (6)
Country | Link |
---|---|
US (1) | US20030188157A1 (fr) |
EP (1) | EP1285322A1 (fr) |
JP (1) | JP2003533813A (fr) |
CN (1) | CN1440524A (fr) |
DE (1) | DE10023818A1 (fr) |
WO (1) | WO2001088669A1 (fr) |
Families Citing this family (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE10023820B4 (de) * | 2000-05-15 | 2006-10-19 | Siemens Ag | Software-Schutzmechanismus |
DE10352009A1 (de) * | 2003-11-07 | 2005-06-09 | Siemens Ag | Kraftfahrzeug-Informationssystem mit geschützten Dateien |
CN1293437C (zh) * | 2003-12-25 | 2007-01-03 | 英业达股份有限公司 | 软件使用量监控系统及方法 |
DE102005015113A1 (de) * | 2005-04-01 | 2006-10-05 | Siemens Ag | Verfahren zur Verwaltung von Nutzungsrechten an elektronischen Datenobjekten durch einen Rechteerwerber |
EP1860817B1 (fr) | 2006-05-26 | 2009-03-25 | Sap Ag | Procédé et système de protection des données d'un agent mobile dans un système en réseau. |
ATE426966T1 (de) | 2006-05-26 | 2009-04-15 | Sap Ag | Verfahren und vorrichtung zur sicheren bearbeitung eines befehls durch einen mobilen agent in einem netzwerk. |
CN101114924B (zh) * | 2006-07-24 | 2010-09-08 | 华为技术有限公司 | 软件许可证使用数据的处理方法及处理系统 |
US8805743B2 (en) * | 2006-12-27 | 2014-08-12 | International Business Machines Corporation | Tracking, distribution and management of apportionable licenses granted for distributed software products |
EP2713301A1 (fr) | 2012-09-27 | 2014-04-02 | Siemens Aktiengesellschaft | Procédé et système de liaison d'une commande pour une machine sur un système informatique placé en amont |
JP6131674B2 (ja) * | 2013-03-28 | 2017-05-24 | 日本電気株式会社 | ライセンス管理装置 |
US10372104B2 (en) | 2015-02-27 | 2019-08-06 | Rockwell Automation Technologies, Inc. | Industrial automation control system content protection |
EP3067763B1 (fr) | 2015-03-11 | 2022-06-29 | Siemens Aktiengesellschaft | Attribution de capteurs à des pièces de machine |
CN106951739B (zh) * | 2017-03-23 | 2018-10-30 | 北京深思数盾科技股份有限公司 | 软件许可管理方法及软件许可锁 |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0818748A2 (fr) * | 1996-07-08 | 1998-01-14 | Murakoshi, Hiromasa | Méthode et système de gestion de logiciels |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3032788B2 (ja) * | 1991-05-08 | 2000-04-17 | ディジタル イクイプメント コーポレイション | ライセンス管理システム |
US5752041A (en) * | 1995-12-15 | 1998-05-12 | International Business Machines Corporation | Method and system for licensing program management within a distributed data processing system |
DE19824814C2 (de) * | 1998-06-03 | 2000-06-21 | Siemens Ag | Einrichtung zur Ermittlung von freizugebenden Funktionen in einer Telekommunikationsanlage |
US6957186B1 (en) * | 1999-05-27 | 2005-10-18 | Accenture Llp | System method and article of manufacture for building, managing, and supporting various components of a system |
US7013296B1 (en) * | 1999-06-08 | 2006-03-14 | The Trustees Of Columbia University In The City Of New York | Using electronic security value units to control access to a resource |
-
2000
- 2000-05-15 DE DE10023818A patent/DE10023818A1/de not_active Ceased
-
2001
- 2001-04-30 JP JP2001584999A patent/JP2003533813A/ja not_active Withdrawn
- 2001-04-30 US US10/276,604 patent/US20030188157A1/en not_active Abandoned
- 2001-04-30 WO PCT/DE2001/001634 patent/WO2001088669A1/fr not_active Application Discontinuation
- 2001-04-30 CN CN01812154.3A patent/CN1440524A/zh active Pending
- 2001-04-30 EP EP01936011A patent/EP1285322A1/fr not_active Ceased
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0818748A2 (fr) * | 1996-07-08 | 1998-01-14 | Murakoshi, Hiromasa | Méthode et système de gestion de logiciels |
Also Published As
Publication number | Publication date |
---|---|
US20030188157A1 (en) | 2003-10-02 |
DE10023818A1 (de) | 2001-11-22 |
WO2001088669A1 (fr) | 2001-11-22 |
JP2003533813A (ja) | 2003-11-11 |
CN1440524A (zh) | 2003-09-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
DE10155752A1 (de) | Lizenzierungsverfahren | |
DE60212920T3 (de) | Verfahren und system zur verwaltung von digitalen abonnementrechten | |
EP1285322A1 (fr) | Gestionnaire de licence | |
DE10155755A1 (de) | Lizenzgenerierungsverfahren | |
EP1290532A2 (fr) | Licenciation et autorisation d'acces | |
DE102006032129A1 (de) | Skalierbares Verfahren zur Zugriffssteuerung | |
DE10023820A1 (de) | Software-Schutzmechanismus | |
AT504581B1 (de) | Verfahren und system zum auslesen von daten aus einem speicher eines fernen geräts durch einen server | |
DE10324337B4 (de) | Rechnersystem und zugehöriges Verfahren zum Durchführen eines Sicherheitsprogramms | |
EP0224639A1 (fr) | Procédé pour contrôler l'accès à la mémoire d'une carte à circuit intégré et dispositif mettant en oeuvre ledit procédé | |
EP0739509A1 (fr) | Configuration a unites maitresses et asservies | |
WO2019091722A1 (fr) | Système informatique de l'ido ainsi qu'agencement avec un tel système informatique de l'ido et avec un système externe | |
EP1226484A2 (fr) | Appareil electronique | |
DE19709975C2 (de) | Mikrocomputer | |
EP2923264B1 (fr) | Procede et systeme pour l'installation d'application dans un élément de sécurité | |
EP2184705A1 (fr) | Procédé, système et appareil destinés au traitement de droits | |
AT509336B1 (de) | Chipkarte mit autorun-funktion | |
DE69834033T2 (de) | Chipkarte mit zählvorrichtung | |
EP2187282B1 (fr) | Procédé de fonctionnement d'une installation utilisant des données sécurisées contre l'utilisation non autorisée | |
DE60220020T2 (de) | Biometrisches identifikations- oder authentifikationssystem | |
DE19538124A1 (de) | Verfahren und Vorrichtung zum Schutz von Software gegen unautorisierte Benutzung | |
DE4332144A1 (de) | Verfahren zur Funktionsprüfung signaltechnisch nicht sicherer Speicher für mindestens zweikanalig abgespeicherte Nutzdaten und Einrichtung zur Durchführung des Verfahrens | |
DE4201967C2 (de) | Verfahren und Anordnung zum Sicherstellen der Integrität von auszudruckenden oder zu stempelnden Daten | |
DE102020105529A1 (de) | Verfahren zur selektiven Bereitstellung von Daten | |
DE69901318T2 (de) | Verfahren und gerät zur überprüfung des betriebszyklus eines tragbaren gegenstandes, insbesondere einer chipkarte |
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: 20021031 |
|
AK | Designated contracting states |
Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR Kind code of ref document: A1 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR |
|
17Q | First examination report despatched |
Effective date: 20040317 |
|
RBV | Designated contracting states (corrected) |
Designated state(s): AT CH DE ES FR GB LI |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED |
|
18R | Application refused |
Effective date: 20051019 |