CA2620981C - Improved smartcard system - Google Patents
Improved smartcard system Download PDFInfo
- Publication number
- CA2620981C CA2620981C CA2620981A CA2620981A CA2620981C CA 2620981 C CA2620981 C CA 2620981C CA 2620981 A CA2620981 A CA 2620981A CA 2620981 A CA2620981 A CA 2620981A CA 2620981 C CA2620981 C CA 2620981C
- Authority
- CA
- Canada
- Prior art keywords
- commands
- file system
- security
- comparator means
- application
- 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
Links
Classifications
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F7/00—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus
- G07F7/08—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means
- G07F7/10—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means together with a coded signal, e.g. in the form of personal identification information, like personal identification number [PIN] or biometric data
- G07F7/1008—Active credit-cards provided with means to personalise their use, e.g. with PIN-introduction/comparison system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
- G06Q20/355—Personalisation of cards for use
- G06Q20/3552—Downloading or loading of personalisation data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
- G06Q20/367—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02E—REDUCTION OF GREENHOUSE GAS [GHG] EMISSIONS, RELATED TO ENERGY GENERATION, TRANSMISSION OR DISTRIBUTION
- Y02E10/00—Energy generation through renewable energy sources
- Y02E10/30—Energy from the sea, e.g. using wave energy or salinity gradient
Abstract
A programmable smartcard device (10) carries a file system (22, 24) and operating software enabling the on-device file system to interface with at least one off-device file and/or application. It also has a script engine (32) capable of running one or more Application Protocol Data Units (1APDUs') associated with a particular form of transaction so as to modify the structure and/or content of the file system, or the commands to be used for accessing the file system or any security conditions associated therewith. The smartcard device (10) is provided with comparator means (34) configurable by a security APDU run by the script engine (32) so that it operates in use to compare the commands carried out in implementing the transaction with one or more reference commands and to restrict or prevent further access or modifications to the on-device data, file system, commands or security conditions in dependence on the outcome of the comparison carried out by the comparator means (34). Thus, the smartcard device can, because the comparator (34) is configured for each different kind of transaction to be carried out, provide improved security within the contraints of memory storage and processing power availableon the smartcard device itself.
Description
Improved Smartcard System The invention concerns an improvement to the smartcard system described in International Patent Application No W003/049056 and, in particular, it concerns the possibility of improved security arrangements in such systems. Such a smartcard system includes a programmable smartcard device carrying a file system and operating software enabling the on-device file system to interface with at least one off-device file and/or application and comprising a script engine capable of running one or more Application Protocol Data Units ('APDUs') so as to modify the structure and/or content of the file system, or the commands to be used for accessing the file system or any security conditions associated therewith.
In such systems, a programmable smartcard device carries one or more application and/or data files stored in memory on the device itself. For example, the files may hold details of the card carrier's bank balance, or details of financial transactions which have been, or are to, be carried out. To safeguard the integrity of this data, the memory holding these files and the data they contain can be accessed only by means of a processor on the card itself. That processor includes a script engine which is capable of running a script uploaded to it from an interface device into which the card is inserted or to which the card can be connected, so as to modify the structure or content of the file system on the card, or the commands to be used for accessing the file system or any security conditions associated therewith.
In the system of International Patent Application No W003/049056 scripts are written as a file formatted in web (internet) standard language for self -describing messages and are transmitted securely over the internet from a central 'back room' to one or more interface devices where they can be loaded onto the smartcard devices of one or more users. Thus, since it is possible to transmit files in web standard languages such as eXtensible Markup Language ('XML') securely over the internet, it is possible to distribute upgrades to the applications software held on the smartcard device or to modify or reformat data on the cards used in the system quickly and conveniently using the internet while maintaining a good level of security.
However, while the basic system of International Patent Application No W003/049056 is secure, we have appreciated that it may still be desirable to try to improve the security of the system further. For security critical smartcard applications such as those which handle financial transactions, the sequence of commands and responses into and out of the smartcard device should follow a specific flow. While one can develop application specific software to run on the card, which only responds normally if the next command(s) expected is received and which, conversely, throws an error if the command is not the expected one, this approach has all the usual drawbacks in terms of management, particularly of upgrades and modifications.
In accordance with the invention, the smartcard device is characterised in that it comprises comparator means configurable by a security APDU run by the script engine and operable to compare the commands carried out in implementing an application to access and/or modify the on-device data or file system or the commands to be used for accessing the system or any security conditions associated therewith with one or more reference commands and to restrict or prevent further access or modifications to such data, file system, commands or security conditions in dependence on the outcome of the comparison carried out by the comparator means.
Thus, in the smartcard system described in International Patent Application No W003/049056 a script engine is used to set up the card. Improved security can be provided by setting up the card so that the card expects and so monitors the occurrence of a certain sequence of commands, either by comparison of the command code alone or by comparison of both code and operands.
The invention also provides a method for configuring the smartcard device referred to above.
An embodiment of the invention will now be described in detail, by way of example, with reference to the drawing which is a schematic diagram of a smartcard device in accordance with the invention.
In such systems, a programmable smartcard device carries one or more application and/or data files stored in memory on the device itself. For example, the files may hold details of the card carrier's bank balance, or details of financial transactions which have been, or are to, be carried out. To safeguard the integrity of this data, the memory holding these files and the data they contain can be accessed only by means of a processor on the card itself. That processor includes a script engine which is capable of running a script uploaded to it from an interface device into which the card is inserted or to which the card can be connected, so as to modify the structure or content of the file system on the card, or the commands to be used for accessing the file system or any security conditions associated therewith.
In the system of International Patent Application No W003/049056 scripts are written as a file formatted in web (internet) standard language for self -describing messages and are transmitted securely over the internet from a central 'back room' to one or more interface devices where they can be loaded onto the smartcard devices of one or more users. Thus, since it is possible to transmit files in web standard languages such as eXtensible Markup Language ('XML') securely over the internet, it is possible to distribute upgrades to the applications software held on the smartcard device or to modify or reformat data on the cards used in the system quickly and conveniently using the internet while maintaining a good level of security.
However, while the basic system of International Patent Application No W003/049056 is secure, we have appreciated that it may still be desirable to try to improve the security of the system further. For security critical smartcard applications such as those which handle financial transactions, the sequence of commands and responses into and out of the smartcard device should follow a specific flow. While one can develop application specific software to run on the card, which only responds normally if the next command(s) expected is received and which, conversely, throws an error if the command is not the expected one, this approach has all the usual drawbacks in terms of management, particularly of upgrades and modifications.
In accordance with the invention, the smartcard device is characterised in that it comprises comparator means configurable by a security APDU run by the script engine and operable to compare the commands carried out in implementing an application to access and/or modify the on-device data or file system or the commands to be used for accessing the system or any security conditions associated therewith with one or more reference commands and to restrict or prevent further access or modifications to such data, file system, commands or security conditions in dependence on the outcome of the comparison carried out by the comparator means.
Thus, in the smartcard system described in International Patent Application No W003/049056 a script engine is used to set up the card. Improved security can be provided by setting up the card so that the card expects and so monitors the occurrence of a certain sequence of commands, either by comparison of the command code alone or by comparison of both code and operands.
The invention also provides a method for configuring the smartcard device referred to above.
An embodiment of the invention will now be described in detail, by way of example, with reference to the drawing which is a schematic diagram of a smartcard device in accordance with the invention.
A smartcard device 10 used in system of the kind outlined above is shown schematically in the drawing.
The device 10 includes on-device memory 20 in which are stored files 22 and 24 and a processor 30 which includes a script engine 32 and a configurable comparator 34. As previously mentioned, on-device memory 20 is only accessible by processor 30 and cannot be accessed directly from outside the smartcard device 10. The device 10 also includes interface means 40, which allows the device 10 to interact with an external interface device (not shown).
For the purposes of the example described, it is assumed that stored files 22 and 24 contain data representing, respectively, a current account balance and the last previous account balance for a financial account of some kind held by the smartcard device's user. When the card is used to authorise the transfer of funds from the user's account, the device 10 interacts with an interface device to upload a file containing one or more Application Protocol Data Units ('APDUs') which are run by the script engine 32 on the device 10 to modify the content of various files held in the device memory 20. The transaction may be quite complex and involve a number of commands which modify the content of a number of files but, for simplicity, only a single modification is considered here.
When the card's user uses the device 10 to authorise payment to a third party, the current balance held in file 22 is copied to file 24 which stores the last previous account balance and then the current balance data in file 22 is modified to show the new smaller balance.
In such a transaction, one would expect to find in the sequence of commands in the APDU run by the script engine 32 to effeect the transaction, the following pair of commands COPY value in file 22 to file 24 WRITE new current balance to file 22 In the system described above, the smartcard device 10 is inserted into or connected to an interface device which, when a transaction is to be initiated, uploads to the device processor 32 one or more APDUs which are then run by the script engine 32 to modify the data in inter alia files 22 and 24. In accordance with the invention, the APDUs include a security or 'watchdog' APDU which is used to configure the comparator 34 in a manner appropriate to the transaction to be carried out. In effect, the security APDU provides reference commands or code against which the commands run by the script engine 32 are checked.
In the example described above, the security APDU may, when run by the script engine 32, configure the comparator 34 so that it carries out comparisons so as to detect the expected pair of commands 'COPY value in file 22 to file 24' and "WRITE new current balance to file 22'. Unless the comparator makes a positive match, the transaction is aborted.
The example given is a very simple one but it will be understood that the comparator 32 can be configured to monitor a much longer sequence of commands in the same way.
Further, the comparator 32 may be configured to compare only parts of commands with the references provided by the security APDU. For example, it may determine whether a'COPY' command contains the name or identifier of a file from which it may be expected that data will be copied in the context of the particular transaction being carried out. Alternatively, only the operands within commands, or the sequence in which they occur may monitored, for example, to check that a'COPY' command is always followed by a 'WRITE' command.
In some circumstances, it may be appropriate to configure the comparator 32 to cause a transaction to be aborted if a match is detected. In the transaction outlined above, for example, there is no legitimate reason for the script engine 32 to copy from file 24 to file 22, so, if such a command is detected, it may mean that a fraud is being perpetrated. Thus, the comparator 34 could be configured to check for the presence of the command 'COPY from file 24 to file 22' as a basis for restricting or preventing further modification of files or data on the smartcard device 10.
Just as, when seeking a positive match to authenticate a transaction, a 'negative match' may be based on a partial comparison. For example, the comparator 34 may be configured simply to look for particular code such as the name of a particular on-device file, say, 'File 24', if that file should not be mentioned in a particular sequence of commands at all.
Alternatively, the comparator 34 may be configured to detect combinations of command code and operands. In the example given above, the comparator 34 might be configured to detect anv command which requires copying from file 24, since such a command is not appropriate to the transaction to be effected.
In complex situations, whether a positive or negative match with references set by the script engine 32 and security APDU is desired, the comparator 34 may be configured to detect particular sequences of commands rather than single ones.
If the expected command set is not a simple linear sequence but includes logic or arithmetic driven branching of the kind described in International Patent Application No W02005/064555, then the script engine capabilities may be used to map these command paths through the comparator 34.
The comparator 34 can also be configured, where appropriate, to compare commands with a predetermined set or range of possible expected values rather than with a single one.
Thus, the 'expected command' script of APDUs and comparator act together like a state machine where the command(s) within the script represents the sequence of commands expected, either by detecting the commands which should be present or by detecting those which should not, and setting the state to 'error' if a particular comparison produces a particular predetermined result.
It will be appreciated that, because the comparator 34 provided on the smartcard device 10 is configurable by the script engine 32 in dependence on the security APDU(s) uploaded as part of the command sequence for each transaction as the transaction is about to take place, the comparator 34 can make checks appropriate to the particular type of transaction which is to be carried out.
Prior art devices outside the smartcard field have utilised checking or monitoring devices for making such comparisons but these have been 'hard wired' into the devices in question and, because of the need to provide for a number of different types of transaction, have required more processor power and/or memory storage than can be provided on a smartcard device. The use of a configurable comparator 34, configured for each transaction as it takes place, means that a level of security checking which has not been available in smartcard systems previously can now be provided within the constraints of the relatively small processor and memory available on a smartcard device.
In addition, the security APDUs for each type of transaction used by the script engine 32 to configure the comparator 34 can readily be modified as necessary if new fraudulent attacks on security are discovered or new forms of transaction are to be accommodated.
The device 10 includes on-device memory 20 in which are stored files 22 and 24 and a processor 30 which includes a script engine 32 and a configurable comparator 34. As previously mentioned, on-device memory 20 is only accessible by processor 30 and cannot be accessed directly from outside the smartcard device 10. The device 10 also includes interface means 40, which allows the device 10 to interact with an external interface device (not shown).
For the purposes of the example described, it is assumed that stored files 22 and 24 contain data representing, respectively, a current account balance and the last previous account balance for a financial account of some kind held by the smartcard device's user. When the card is used to authorise the transfer of funds from the user's account, the device 10 interacts with an interface device to upload a file containing one or more Application Protocol Data Units ('APDUs') which are run by the script engine 32 on the device 10 to modify the content of various files held in the device memory 20. The transaction may be quite complex and involve a number of commands which modify the content of a number of files but, for simplicity, only a single modification is considered here.
When the card's user uses the device 10 to authorise payment to a third party, the current balance held in file 22 is copied to file 24 which stores the last previous account balance and then the current balance data in file 22 is modified to show the new smaller balance.
In such a transaction, one would expect to find in the sequence of commands in the APDU run by the script engine 32 to effeect the transaction, the following pair of commands COPY value in file 22 to file 24 WRITE new current balance to file 22 In the system described above, the smartcard device 10 is inserted into or connected to an interface device which, when a transaction is to be initiated, uploads to the device processor 32 one or more APDUs which are then run by the script engine 32 to modify the data in inter alia files 22 and 24. In accordance with the invention, the APDUs include a security or 'watchdog' APDU which is used to configure the comparator 34 in a manner appropriate to the transaction to be carried out. In effect, the security APDU provides reference commands or code against which the commands run by the script engine 32 are checked.
In the example described above, the security APDU may, when run by the script engine 32, configure the comparator 34 so that it carries out comparisons so as to detect the expected pair of commands 'COPY value in file 22 to file 24' and "WRITE new current balance to file 22'. Unless the comparator makes a positive match, the transaction is aborted.
The example given is a very simple one but it will be understood that the comparator 32 can be configured to monitor a much longer sequence of commands in the same way.
Further, the comparator 32 may be configured to compare only parts of commands with the references provided by the security APDU. For example, it may determine whether a'COPY' command contains the name or identifier of a file from which it may be expected that data will be copied in the context of the particular transaction being carried out. Alternatively, only the operands within commands, or the sequence in which they occur may monitored, for example, to check that a'COPY' command is always followed by a 'WRITE' command.
In some circumstances, it may be appropriate to configure the comparator 32 to cause a transaction to be aborted if a match is detected. In the transaction outlined above, for example, there is no legitimate reason for the script engine 32 to copy from file 24 to file 22, so, if such a command is detected, it may mean that a fraud is being perpetrated. Thus, the comparator 34 could be configured to check for the presence of the command 'COPY from file 24 to file 22' as a basis for restricting or preventing further modification of files or data on the smartcard device 10.
Just as, when seeking a positive match to authenticate a transaction, a 'negative match' may be based on a partial comparison. For example, the comparator 34 may be configured simply to look for particular code such as the name of a particular on-device file, say, 'File 24', if that file should not be mentioned in a particular sequence of commands at all.
Alternatively, the comparator 34 may be configured to detect combinations of command code and operands. In the example given above, the comparator 34 might be configured to detect anv command which requires copying from file 24, since such a command is not appropriate to the transaction to be effected.
In complex situations, whether a positive or negative match with references set by the script engine 32 and security APDU is desired, the comparator 34 may be configured to detect particular sequences of commands rather than single ones.
If the expected command set is not a simple linear sequence but includes logic or arithmetic driven branching of the kind described in International Patent Application No W02005/064555, then the script engine capabilities may be used to map these command paths through the comparator 34.
The comparator 34 can also be configured, where appropriate, to compare commands with a predetermined set or range of possible expected values rather than with a single one.
Thus, the 'expected command' script of APDUs and comparator act together like a state machine where the command(s) within the script represents the sequence of commands expected, either by detecting the commands which should be present or by detecting those which should not, and setting the state to 'error' if a particular comparison produces a particular predetermined result.
It will be appreciated that, because the comparator 34 provided on the smartcard device 10 is configurable by the script engine 32 in dependence on the security APDU(s) uploaded as part of the command sequence for each transaction as the transaction is about to take place, the comparator 34 can make checks appropriate to the particular type of transaction which is to be carried out.
Prior art devices outside the smartcard field have utilised checking or monitoring devices for making such comparisons but these have been 'hard wired' into the devices in question and, because of the need to provide for a number of different types of transaction, have required more processor power and/or memory storage than can be provided on a smartcard device. The use of a configurable comparator 34, configured for each transaction as it takes place, means that a level of security checking which has not been available in smartcard systems previously can now be provided within the constraints of the relatively small processor and memory available on a smartcard device.
In addition, the security APDUs for each type of transaction used by the script engine 32 to configure the comparator 34 can readily be modified as necessary if new fraudulent attacks on security are discovered or new forms of transaction are to be accommodated.
Claims (11)
1. A programmable smartcard device carrying a file system and operating software enabling the on-device file system to interface with at least one off-device file and/or application and comprising a script engine capable of running one or more Application Protocol Data Units ('APDUs') so as to modify the structure and/or content of the file system, or the commands to be used for accessing the file system or any security conditions associated therewith;
wherein the programmable smartcard device comprises comparator means configurable by a security APDU run by the script engine and operable to compare the commands carried out in implementing an application to access and/or modify the on-device data or file system or the commands to be used for accessing the system or any security conditions associated therewith with one or more reference commands and to restrict or prevent further access or modifications to such data, file system, commands or security conditions in dependence on the outcome of the comparison carried out by the comparator means.
wherein the programmable smartcard device comprises comparator means configurable by a security APDU run by the script engine and operable to compare the commands carried out in implementing an application to access and/or modify the on-device data or file system or the commands to be used for accessing the system or any security conditions associated therewith with one or more reference commands and to restrict or prevent further access or modifications to such data, file system, commands or security conditions in dependence on the outcome of the comparison carried out by the comparator means.
2. A device according to claim 1 wherein the comparator means is operable to compare the code of an APDU run by the script engine to modify on-device data, files, commands or security conditions with reference code.
3. A device according to claim 2 wherein the comparator means is further operable to compare at least one operand of the APDU run by the script engine with a reference operand.
4. A device according to claim 2 or 3 wherein the comparator means is operable to compare the code and/or operand(s) of the APDU run by the script engine with reference code or operands representing a plurality of reference values.
5. A device according to any one of claims 1 to 4 wherein the comparator means is operable to compare the sequence of commands carried out in implementing an application with a reference sequence.
6. A device according to any one of claims 1 to 5 wherein the comparator means is operable to restrict or prevent further access or modifications to data, file system, commands or security conditions when it does not detect a match with a reference command or commands representing an expected command, commands or sequence of commands.
7. A device according to any of claims 1 to 5 wherein the comparator means is operable to restrict or prevent further access or modifications to data, file system, commands or security conditions when it detects a match with a reference command or commands.
8. A device according to any one of claims 1 to 7 wherein the script engine is operable to run one or more APDUs derived from at least one file formatted in a web (internet) standard language for self-describing messages.
9. A method for configuring the programmable smartcard device of any of claims 1 to 8, the method comprising:
providing a card reading interface device for interfacing with the programmable smartcard device at a card reader thereof, and loading to the programmable smartcard device an application script comprising at least one APDU for modifying definitions of the structure and content of the on-device file system, or the commands to be used for accessing the file system or any security conditions associated therewith;
wherein the script uploaded to the programmable smartcard device further comprises a security APDU which is run by a script engine on the smartcard device to configure comparator means operable to compare the commands carried out in implementing an application to access and/or modify the on-device data or file system or the commands to be used for accessing the system or any security conditions associated therewith with one or more reference commands;
further access or modifications to such data, file system, commands or security conditions being restricted or prevented in dependence on the outcome of the comparison carried out by the comparator means.
providing a card reading interface device for interfacing with the programmable smartcard device at a card reader thereof, and loading to the programmable smartcard device an application script comprising at least one APDU for modifying definitions of the structure and content of the on-device file system, or the commands to be used for accessing the file system or any security conditions associated therewith;
wherein the script uploaded to the programmable smartcard device further comprises a security APDU which is run by a script engine on the smartcard device to configure comparator means operable to compare the commands carried out in implementing an application to access and/or modify the on-device data or file system or the commands to be used for accessing the system or any security conditions associated therewith with one or more reference commands;
further access or modifications to such data, file system, commands or security conditions being restricted or prevented in dependence on the outcome of the comparison carried out by the comparator means.
10. A method according to claim 9 wherein a plurality of different application scripts can be loaded to the programmable smartcard device, each of the application scripts having a security APDU associated with it; the associated security APDU being loaded to the device whenever an application script is loaded so that the comparator means is reconfigured each time a different application script is to be run by the script engine.
11. A method according to claim 9 or 10 wherein the application script and security APDU are derived from at least one file formatted in a web (internet) standard language for self-describing messages.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| GBGB0517615.1A GB0517615D0 (en) | 2005-08-30 | 2005-08-30 | Improved smartcard system |
| GB0517615.1 | 2005-08-30 | ||
| PCT/GB2006/003205 WO2007026139A1 (en) | 2005-08-30 | 2006-08-29 | Improved smartcard system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2620981A1 CA2620981A1 (en) | 2007-03-08 |
| CA2620981C true CA2620981C (en) | 2014-08-05 |
Family
ID=35198569
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2620981A Active CA2620981C (en) | 2005-08-30 | 2006-08-29 | Improved smartcard system |
Country Status (8)
| Country | Link |
|---|---|
| US (1) | US8117662B2 (en) |
| EP (1) | EP1937964B8 (en) |
| JP (1) | JP5208741B2 (en) |
| CN (1) | CN100561527C (en) |
| AU (1) | AU2006286382B2 (en) |
| CA (1) | CA2620981C (en) |
| GB (2) | GB0517615D0 (en) |
| WO (1) | WO2007026139A1 (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8745745B2 (en) | 2012-06-26 | 2014-06-03 | Lynuxworks, Inc. | Systems and methods involving features of hardware virtualization such as separation kernel hypervisors, hypervisors, hypervisor guest context, hypervisor context, rootkit detection/prevention, and/or other features |
| CN103473093B (en) * | 2013-09-05 | 2016-08-24 | 飞天诚信科技股份有限公司 | A kind of method managing on card application |
| WO2015176046A1 (en) | 2014-05-15 | 2015-11-19 | Lynx Software Technologies, Inc. | Systems and methods involving features of hardware virtualization, hypervisor, apis of interest, and/or other features |
| US11782745B2 (en) | 2014-07-01 | 2023-10-10 | Lynx Software Technologies, Inc. | Systems and methods involving aspects of hardware virtualization such as separation kernel hypervisors, hypervisors, hypervisor guest context, hypervisor context, anti-fingerprinting and/or other features |
| FR3031613B1 (en) * | 2015-01-09 | 2018-04-06 | Ingenico Group | METHOD FOR PROCESSING A TRANSACTION FROM A COMMUNICATION TERMINAL |
| CN107797930B (en) * | 2017-10-27 | 2021-04-23 | 东信和平科技股份有限公司 | Method, system, device and readable storage medium for testing functions of smart card |
Family Cites Families (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP3176209B2 (en) * | 1994-02-25 | 2001-06-11 | 富士通株式会社 | Card-type storage medium and card-type storage medium issuing device |
| US6742120B1 (en) * | 1998-02-03 | 2004-05-25 | Mondex International Limited | System and method for controlling access to computer code in an IC card |
| US6754886B1 (en) * | 1998-11-30 | 2004-06-22 | International Business Machines Corporation | Method and system for storing java objects in devices having a reduced support of high-level programming concepts |
| US6547150B1 (en) * | 1999-05-11 | 2003-04-15 | Microsoft Corporation | Smart card application development system and method |
| DE19947986A1 (en) * | 1999-10-05 | 2001-04-12 | Ibm | Method of downloading of application parts via distributed systems on to a chip-card, requires provision of secret code or session key by the server prior to loading command-sequence of commands for downloading |
| FR2812419B1 (en) * | 2000-07-31 | 2003-01-17 | Cit Alcatel | METHOD FOR SECURING ACCESS TO A MICROPROCESSOR USER CARD |
| US20060174352A1 (en) * | 2001-07-25 | 2006-08-03 | Seagate Technology Llc | Method and apparatus for providing versatile services on storage devices |
| US7243853B1 (en) * | 2001-12-04 | 2007-07-17 | Visa U.S.A. Inc. | Method and system for facilitating memory and application management on a secured token |
| NZ533945A (en) * | 2001-12-07 | 2006-09-29 | Ecebs Ltd | Smartcard system |
| US8121955B2 (en) * | 2003-01-16 | 2012-02-21 | Oracle America, Inc. | Signing program data payload sequence in program loading |
| JP4242682B2 (en) * | 2003-03-26 | 2009-03-25 | パナソニック株式会社 | Memory device |
| JP4624732B2 (en) * | 2003-07-16 | 2011-02-02 | パナソニック株式会社 | how to access |
-
2005
- 2005-08-30 GB GBGB0517615.1A patent/GB0517615D0/en not_active Ceased
-
2006
- 2006-08-29 US US12/064,848 patent/US8117662B2/en active Active
- 2006-08-29 AU AU2006286382A patent/AU2006286382B2/en active Active
- 2006-08-29 GB GB0804947A patent/GB2444006B/en active Active
- 2006-08-29 JP JP2008528573A patent/JP5208741B2/en active Active
- 2006-08-29 EP EP06779231.7A patent/EP1937964B8/en active Active
- 2006-08-29 WO PCT/GB2006/003205 patent/WO2007026139A1/en active Application Filing
- 2006-08-29 CA CA2620981A patent/CA2620981C/en active Active
- 2006-08-29 CN CNB2006800361499A patent/CN100561527C/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| AU2006286382B2 (en) | 2011-03-31 |
| CA2620981A1 (en) | 2007-03-08 |
| US20080320597A1 (en) | 2008-12-25 |
| GB0517615D0 (en) | 2005-10-05 |
| EP1937964B1 (en) | 2019-03-06 |
| GB0804947D0 (en) | 2008-04-16 |
| JP5208741B2 (en) | 2013-06-12 |
| EP1937964B8 (en) | 2019-08-07 |
| EP1937964A1 (en) | 2008-07-02 |
| GB2444006A (en) | 2008-05-21 |
| US8117662B2 (en) | 2012-02-14 |
| CN100561527C (en) | 2009-11-18 |
| JP2009506447A (en) | 2009-02-12 |
| AU2006286382A1 (en) | 2007-03-08 |
| WO2007026139A1 (en) | 2007-03-08 |
| GB2444006B (en) | 2010-05-05 |
| CN101297110A (en) | 2008-10-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| AU763958B2 (en) | Techniques for permitting access across a context barrier in a small footprint device using global data structures | |
| US8807440B1 (en) | Routing secure element payment requests to an alternate application | |
| CN100334517C (en) | Physical presence determination in a trusted platform | |
| KR100688397B1 (en) | Techniques for permitting access across a context barrier on a small footprint device using an entry point object | |
| CA2620981C (en) | Improved smartcard system | |
| Iguchi-Cartigny et al. | Developing a Trojan applets in a smart card | |
| NZ313777A (en) | Data exchange system comprising portable and non-portable data processing units suitable for use in smart cards | |
| KR100688396B1 (en) | Techniques for implementing security on a small footprint device using a context barrier | |
| AU771765B2 (en) | Techniques for permitting access across a context barrier on a small footprint device using run time environment privileges | |
| US7797682B2 (en) | Controlled execution of a program used for a virtual machine on a portable data carrier | |
| Faraj et al. | Investigation of Java Smart Card Technology for Multi-Task Applications | |
| KR20010103746A (en) | Techniques for permitting access across a context barrier in a small footprint device using shared object interfaces | |
| SI9720049A (en) | Portable, secure transaction system for programable, inteligent devices | |
| JP2009506447A5 (en) | ||
| US20100031357A1 (en) | Defending Smart Cards Against Attacks by Redundant Processing | |
| EP3244340A1 (en) | Method for securely running an application | |
| Gadyatskaya et al. | Java Card architecture for autonomous yet secure evolution of smart cards applications | |
| JP7247638B2 (en) | Electronic information storage medium, IC card, falsification check method, and program | |
| Bernardeschi et al. | Enforcement of applet boundaries in Java card systems. | |
| CN112184212A (en) | Method for controlling applet operation for IC card | |
| EP1447733A1 (en) | Data processing system and method | |
| Markantonakis | Java card technology and security | |
| Mayes et al. | Smart Card Reader APIS | |
| 台灣銘板股份有限公司 | TNP ECC2 CPU Card Security Target | |
| AU2004200758A1 (en) | Techniques for permitting access across a context barrier on a small footprint device using an entry point object |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request |