JP4735024B2 - IC card data migration system and method - Google Patents

Description

  The present invention relates to a data migration method for an IC card or the like, and more particularly, to a system and method for preventing data from being illegally migrated such as an IC card and migrating data of a plurality of applications.

  When an old IC card is switched to a new IC card, there is a great demand to transfer data used by an application program (hereinafter referred to as application) in the old IC card to the new IC card.

  In the case of a single service provider, the above request is realized by the service provider migrating data in the IC card.

  Also, a technology is known in which an IC card is divided into areas for each service provider, and the service provider mounts applications and data (see, for example, Non-Patent Document 1). In the case of a multi-application IC card capable of mounting such a plurality of applications, a plurality of service providers can satisfy the above-mentioned requirements by transferring application data in the IC card.

  These migration tasks are premised to be performed in a safe environment where the person performing the task is authenticated and the device performing the operation is verified to be an unauthorized terminal. As a method for migrating data, a technique is known in which a data transmission / reception log is stored in an IC card and temporary data is not stored in an insecure terminal (see, for example, Patent Document 1).

  In addition, as a method for transferring data without simultaneously inserting two new and old IC cards into the same device, there is a technique using a mail server (see, for example, Patent Document 2).

  In addition, there is a technology that makes it possible to easily update a secret key used when transferring data between IC cards, and enhances safety during data transfer (see, for example, Patent Document 3).

JP 2002-140664 A GlobalPlatform Inc., “GlobalPlatform Card Specification Version 2.1.1”, [online], March 2003, GlobalPlatform Inc., p. 28, [Search April 6, 2005], Internet <URL: http://www.globalplatform.org/specificationview.asp?id=card> JP 2003-44769 A US Patent Application Publication No. 2004 / 0025021A1

  In the prior art, when data is transferred from an old card to a new card using a terminal that cannot be said to be safe, it is assumed that the card administrator must do so, which impairs user convenience. It was. Further, in the case of an IC card on which a plurality of applications are installed by a plurality of service providers, it is necessary for each service provider to perform a data migration operation, which complicates the data migration operation.

  The present invention has been made in view of the above circumstances, and provides a system in which a user can transfer data from an old card to a new card even when using a terminal that is not safe.

  Specifically, an application program for performing data migration processing (hereinafter referred to as a data migration application) is installed in advance in the IC card, and data migration carried on the old IC card and the new IC card is performed at the time of data migration. The present invention provides an IC card data migration method in which an application is executed to embody a data migration unit, and the data migration unit migrates data, and a system to which the method is applied.

  According to this system, the terminal used for data transfer from the old IC card to the new IC card does not need to be secure, and even a user who is not an IC card administrator can freely perform data transfer.

  More specifically, at the time of data migration, the data migration unit of the old IC card once transfers data (hereinafter referred to as migration data) related to the target application (hereinafter referred to as migration data) to a memory area managed by the own data migration unit. The data is copied (backed up) and moved by deleting data to be migrated from the memory area managed by the target application, thereby preventing unauthorized use of data in the old IC card.

  Also, mutual authentication is performed between the data transfer unit of the old IC card and the new IC card, and the transfer data backed up in the old IC card is transmitted to the memory area managed by the data transfer unit of the new IC card. The data migration unit moves data to a memory area managed by the target application. At that time, signatures are added and encrypted to prevent tampering and snooping on the communication path.

  Further, when data migration fails, the data migration unit of the old IC card may restore the backup data stored therein to the application in the old IC card.

  According to the present invention, an administrator or user of an IC card can safely and easily transfer data of a plurality of applications in the IC card from the old IC card to the new IC card. In addition, data can be restored even when data migration fails.

  An embodiment of the present invention will be described. Note that the present invention is not limited thereby.

  FIG. 1 is a configuration diagram of an IC card data migration system to which an embodiment of the present invention is applied.

  As illustrated in FIG. 1, the IC card data migration system of this embodiment transmits and receives data between the IC card 10 that is the data migration source and the IC card 20 that is the data migration destination. The communication path 30 to be performed is connected to each other.

Each of the IC card 10 and the IC card 20 receives a command from the outside, performs processing according to the content of the received command, and returns a processing result. The IC cards 10 and 20 store data transmission / reception units 101 and 201 for receiving commands and transmitting processing results, command analysis units 102 and 202 for analyzing commands, and keys used for analyzing commands. Key storage units 104 _{1 to} 104 _n (hereinafter also referred to as 104), 204 _{1 to} 204 _n (hereinafter also referred to as 204), and application units 103 ₁ to 103 ₁ that execute processing according to commands. 103 _n (hereinafter also referred to as 103), 203 _{1 to} 203 _n (hereinafter also referred to as 203), and data used by each of the application units 103 _{1 to} 103 _n and 203 _{1 to} 203 _n storage to keep the data storage unit ₁₀₅ 1 to 105 _n (hereinafter, sometimes referred to as _105), 205 1 ~205 _n (hereinafter , 205), and when data is migrated, the data migration units 106 and 206 that operate as the data transmission unit and the data reception unit, and the data migration units 106 and 206 perform signature and encryption. The key storage units 107 and 207 for storing the keys, the data storage units 108 and 208 for storing the data used by the data migration unit, and the status of the data migration process managed by the data migration unit Processing progress flag holding units 109 and 209.

  On the communication path 30, a terminal 40 is provided for receiving commands from the IC card 10 and the IC card 20 and transmitting processing results. The terminal 40 includes an IC card access unit 402 that receives commands from the IC card 10 and the IC card 20 and transmits processing results, and a command generation unit 401 that generates a data migration instruction command.

  FIG. 2 is a diagram illustrating a hardware configuration of the IC card 10. The IC card 10 is configured by connecting an input / output device 11, a CPU 12, a tamper resistant storage device 13, and a tamper resistant memory 14 through an internal communication line 15 such as a bus. The hardware configuration of the IC card 20 is the same as the hardware configuration of the IC card 10. Here, the shape of the IC card is not limited to the shape of a business card such as a telephone card, and may be the shape of an SD memory card, for example, as long as the hardware includes the above-described components.

  FIG. 3 is a diagram illustrating a hardware configuration of the terminal 40. The terminal 40 is configured by connecting a storage device 41, at least one IC card input / output device 42, a CPU 43, and a memory 44 via an internal communication line 45 such as a bus.

  In the data transmission / reception units 101 and 201, command analysis units 102 and 202, application units 103 and 203, and data migration units 106 and 206 shown in FIG. 1, the programs stored in the storage devices 13 and 41 of each device are stored in the memories 14 and 44, respectively. Are executed on the terminal 40 and the IC cards 10 and 20 constituting the IC card data migration system. More specifically, the application unit is implemented by executing an application program, and the data migration unit is implemented by executing a data migration application program.

  Each program may be stored in advance in the storage devices 13 and 41, or may be introduced through other storage media or communication media (network or digital signal or carrier wave propagating through the network) when necessary. good.

  A processing flow in the IC card data migration system of this embodiment will be described.

  FIG. 4 is a schematic flowchart for transferring data from the IC card 10 to the IC card 20 in accordance with the data transfer request generated by the terminal 40.

  First, data read processing is performed among the application unit 103, the data migration unit 106, the terminal 40, and the data migration unit 206 (step 401 (expressed as S401, the same applies hereinafter)).

  Next, migration data transmission / reception processing is performed among the data migration unit 106, the terminal 40, and the data migration unit 206 (S402).

  Next, data write processing is performed between the data migration unit 206 and the application unit 203 (S403).

  Next, a migration result transmission / reception process is performed among the data migration unit 106, the terminal 40, and the data migration unit 206 (S404).

  Finally, if necessary, data restoration processing is performed among the application unit 103, the data migration unit 106, and the terminal 30 (S405).

  FIG. 5 is a detailed view of the data reading process (S401) in the processing flow of FIG.

  First, the IC card access unit 402 of the terminal 40 executes a data migration request when the data migration destination IC card 20 is inserted into the IC card input / output device 42 (S501). Next, an ID acquisition command (A501) is transmitted to the data migration unit 206 of the data migration destination IC card 20. If the terminal 40 is provided with an input device that accepts a data migration instruction by the user, the data migration request may be executed when the instruction is input from the input device.

  Next, the data migration unit 206 acquires the ID of the data migration destination IC card 20 (S502). Next, ID (A502) is transmitted to the terminal 40.

  The command generation unit 401 of the terminal 40 generates a data migration command using the acquired ID (S503). Next, the generated data migration command (A503) is transmitted to the data migration unit 106 in the IC card 10 via the IC card access unit 402.

  Next, the data migration unit 106 acquires the ID of the application unit 103 in the data migration source IC card 10 (S504). Next, the data migration unit 106 performs authentication processing with the application unit 103 in order to access the data storage unit 105 of the application unit 103 that is the data migration source (S505). If the authentication is successful, a data read command (A504) is transmitted to the application unit 103. The acquired two types of IDs are incorporated into the migration data and used to specify the source of the migration data.

  Next, the application unit 103 reads the data stored in the data storage unit 105 (S506). Next, the data (A505) acquired in S506 is transmitted to the data migration unit 106. Note that the migration data may be data stored in a data storage unit such as electronic money, or may be the program main body of the application unit 103.

  Next, the data migration unit 106 writes the received data to the data storage unit 108 of the data migration unit 106 (S507). Next, in order to erase the data stored in the data storage unit 105 of the application unit 103, a data deletion command (A506) is transmitted to the application unit 103.

  Next, the application unit 103 analyzes the received command and deletes the data stored in the data storage unit 105 (S508). As a method of erasing data, a method of deleting reference information from a generally used memory management table or a method of erasing data by writing empty data may be used.

  Next, a response (A507) indicating completion of data erasure is transmitted to the data migration unit 106.

  According to the flow from the transmission of the A504 command to the reception of the A507 command, the migration data of the data storage unit 105 of the application unit 103 is moved to the data storage unit 108 of the data migration unit 106 before being transferred to another IC card. When data migration is started, the data of the application unit 103 cannot be used illegally.

  When data of a plurality of application units is migrated, the flow from S505 to S508 is repeated for each application unit.

  Further, instead of erasing data stored in the data storage unit 105 of the application unit 103, the application unit 103 may be locked. Specifically, the application unit 103 is configured not to accept an external command when it receives a lock command, and the data migration application 106 transmits the lock command to the application unit 103.

  Next, the data migration unit 106 converts the data written in the data storage unit 108 in S507 into the migration data format shown in FIG. 13 (S509).

  FIG. 6 is a detailed diagram of the migration data transmission / reception process (S402) in the processing flow of FIG.

  First, mutual authentication processing is performed between the data migration unit 106 in the data migration source IC card 10 and the data migration unit 206 in the data migration destination IC card 20 via the terminal 40, and subsequent signatures and encryptions are performed. A session key used for conversion is shared (S601). The cipher used in the authentication process may be a common key cipher or a public key cipher as long as the session key can be shared during the authentication process. At that time, the terminal 40 performs data transmission / reception between the data migration source IC card 10 and the data migration destination IC card 20.

  Next, the data migration unit 106 generates a signature of the migration data using the session key shared in S601 (S602). Next, the migration data itself is encrypted with the session key (S603). Thereafter, the encrypted migration data and signature (A601) are transmitted to the terminal 40.

  Next, the terminal 40 transmits the received data (A601) to the data migration unit 206 in the IC card 20 (S604).

  Next, the data migration unit 206 decrypts the encrypted migration data using the session key shared in S601 (S605). Next, verification of the signature of the migration data and verification of whether the ID of the migration destination IC card described in the migration data matches the ID of the data migration destination IC card 20 (S606). By this verification, it is possible to avoid transferring the transfer data to different IC cards a plurality of times. If verification of the signature or ID fails, a response indicating that is transmitted to the terminal 40, and the data migration process is stopped (S607). If the signature and ID verification is successful, the migration data is written in the data storage unit 208 of the data migration unit 206 (S608).

  FIG. 7 is a detailed diagram of the data writing process (S403) in the processing flow of FIG.

In order to access the data storage unit 205 of the application unit 203 that is the data migration destination, the data migration unit 206 performs authentication processing with the application unit 203 and confirms that it has read authority (S701).
Next, in order to write the migration data written in the data storage unit 208 of the data migration unit 206 in S607 to the data storage unit 205 of the application unit 203, a data write command (A701) is transmitted to the application unit 203.

Next, the application unit 203 analyzes the received command (including migration data) and writes the migration data in the data storage unit 205 (S702). This migration data is data collected for each application.
Thereafter, the response (A702) is transmitted to the data migration unit 206.

  Next, the data migration unit 206 transmits a data read command (A703) to the application unit 203. This command is the same as the command of A504.

  It is assumed that the data migration unit 206 knows an interface (address or the like) related to data reading / writing of the application unit 203.

  Next, the application unit 203 analyzes the received command and reads data from the data storage unit 205 (S703). Thereafter, the read data (A704) is transmitted to the data migration unit 206.

  Next, the data migration unit 206 compares the received data (A704) with the data written in the data storage unit 208 in S607, and confirms the success or failure of the writing (S704). This verification process makes it possible to cope with a case where the amount of data that can be stored exceeds the amount of data that can be stored during data writing, and the data cannot be written. Next, a data migration processing result is generated based on the result of S704 (S705).

  When data of a plurality of application units is migrated, the data migration unit 206 controls to repeat the flow from S701 to S705 for each application unit.

  FIG. 8 is a detailed view of the migration result transmission / reception process (S404) in the processing flow of FIG.

First, the data migration unit 206 generates a signature of the data migration process result using the session key shared in S601 (S801).
Thereafter, the processing result and the signature (A801) are transmitted to the terminal 40.

  Next, the terminal 40 transmits the received processing result and signature (A801) to the data migration unit 106.

  Next, the data migration unit 106 verifies the signature out of the received processing result and signature (S802). If it is determined that the signature is invalid, the fact is transmitted to the terminal 40, and the data migration process is stopped (S803). If it is determined that the signature is valid, the received processing result is verified (S804). If it is determined that the data migration is successful, the migration data stored in the data storage unit 108 of the data migration unit 106 is deleted (S805), and a response (A802) to the terminal 40 indicating that the process has been completed. ) Is transmitted, and the data migration process is terminated (S806). If it is determined in S804 that data migration has failed, data restoration processing is started (S807).

  Note that IC cards generally handle data requiring security, such as electronic money, and therefore have a recovery process when data writing fails. Therefore, by using this function in S807, it is possible to prevent any halfway data from remaining in the IC card when data writing fails.

  FIG. 9 is a detailed diagram of the data restoration process (S405) in the processing flow of FIG.

  First, the data migration unit 106 performs an authentication process with the application unit 103 in order to access the data storage unit 105 of the application 103 (S901). Next, in order to write the migration data written in the data storage unit 108 of the data migration unit 106 to the data storage unit 105 of the application unit 103, a data write command (A901) is transmitted to the application unit 103. The command includes data to be restored.

Next, the application unit 103 analyzes the received command and writes data in the data storage unit 105 (S902). After the writing, a verify process similar to S704 may be performed, but this is not essential because it is a data restoration process.
Thereafter, a response (A902) indicating that the processing is completed is transmitted to the data migration unit 106.

  Next, the data migration unit 106 deletes the migration data stored in the data storage unit 108 (S903). Thereafter, a response (A903) indicating that the processing is completed is transmitted to the terminal 40, and the data migration processing is stopped (S904).

  If the application unit 103 is locked in S508, the application unit 103 is unlocked instead of S902.

  The flow in FIGS. 5 to 9 may be interrupted in the middle of processing when an operation error or a sudden power interruption occurs. In order to cope with such a case, in the present embodiment, when the internal state of the application unit or the data migration unit changes such as data writing, the process progress flag holding unit 109 of the data migration unit 106 is changed. In addition, the process progress flag is written in the process progress flag holding unit 209 of the data migration unit 206. By referring to these flags, it is possible to restart the data migration process from an intermediate stage. The processing progress flag is configured to be written by the data migration unit 106 and the data migration unit 206.

  In this embodiment, the processing progress flag is written at the timing of completion of S507, reception of A507, completion of S509, completion of S607, reception of A702, completion of S705, completion of S805, reception of A902, and completion of S903. There are a total of 9 locations.

  FIG. 10 is an authentication flow performed when the application unit authenticates the data migration unit, which is performed in S505 of FIG. 5 or S701 of FIG. The authentication is performed inside the IC card. Although the authentication performed in the IC card 10 is shown below, the authentication performed in the IC card 20 is the same.

  First, the data migration unit 106 starts an authentication process (S1001) and generates a random number generation command (S1002). Thereafter, a random number generation command (A1001) is transmitted to the application unit 103.

  Next, the application unit 103 analyzes the received command and generates a random number (S1003). Thereafter, the generated random number (A1002) is transmitted to the data migration unit 106.

  Next, the data migration unit 106 creates authentication data using the received random number (A1002) and the key data stored in the key storage unit 107 (S1004). Thereafter, the generated authentication data (A1003) is transmitted to the application unit 103.

  Next, the application unit 103 compares the received authentication data (A1003) with the authentication data generated in the application unit 103, and performs authentication processing (S1005). Thereafter, the authentication result (A1004) is transmitted to the data migration unit 106.

  Next, the data migration unit 106 verifies the authentication result (A1004) (S1006), and determines whether the authentication has succeeded or failed.

Note that the authentication flow shown in FIG. 10 is an example of an authentication flow using common key encryption. The authentication flow used in the present embodiment is not limited to this method using a challenge response, and may be an authentication method using a one-time password or zero knowledge proof, for example. This is a flow in the case where the mutual authentication performed between the data migration unit 106 in the IC card 10 and the data migration unit 206 in the IC card 20 performed in S601 is performed using common key encryption.

  First, the data migration unit 106 starts an authentication process (S1101) and generates a random number (S1102). Thereafter, the generated random number (A1101) is transmitted to the terminal 30.

  Next, the terminal 40 transmits the received random number (A1101) to the data migration unit 206.

  Next, the data migration unit 206 writes the received random number (A1101) (S1103). Next, a random number is generated internally (S1104). Next, a session key is generated using the received random number (A1101), the internally generated random number, and the key of the key storage unit 207 (S1105). Next, using the generated session key, the combination of the received random number and the internally generated random number is encrypted to generate authentication data 1 (S1106). Thereafter, the generated random number data and authentication data 1 (A1102) are transmitted to the terminal 40.

  Next, the terminal 40 transmits the received data (A1102) to the data migration unit 106.

  Next, the data migration unit 106 writes the received random number (S1107). Next, a session key is generated using the random number generated in S1102, the received random number, and the key of the key storage unit 107 (S1108). Next, it is verified whether the authentication data 1 received from the data migration unit 206 is valid using the generated session key (S1109). If it is determined that the authentication data is unauthorized, the fact is transmitted to the terminal 40, and the terminal 40 displays, for example, an error and notifies the user. If it is determined that the authentication data is valid, then the authentication data 2 is generated by encrypting the combination of the received random number and the internally generated random number using the generated session key (S1110). . Next, a signature of the generated authentication data 2 is generated using the session key (S1111). Thereafter, the authentication data 2 and the signature (A1103) are transmitted to the terminal 40.

  Next, the terminal 40 transmits the received data (A1103) to the data migration unit 206.

  Next, the data migration unit 206 verifies the signature of the received data (A1103) (S1112). Next, verification of the authentication data 2 is performed (S1113). Thereafter, the authentication result is transmitted to the terminal 40 as a response (A1104).

  Next, the terminal 40 transmits the received response (A1104) to the data migration unit 106.

  The data migration unit 106 verifies the received response (S1114) and determines whether the authentication has succeeded or failed.

  Note that the mutual authentication flow shown in FIG. 11 is an example of a mutual authentication flow using common key encryption. The authentication flow used in the present embodiment is not limited to this method using a challenge response, and for example, an authentication method such as a one-time password or zero knowledge proof may be used.

  FIG. 12 is a flow when the mutual authentication flow shown in FIG. 11 is performed using public key cryptography.

  First, the data migration unit 106 starts an authentication process (S1201) and generates a random number (S1202). Next, the public key of the data migration unit 106, the ID of the data migration source IC card 10, the signature of the certification authority proving that the key and the ID have not been tampered with, and the generated random number (A1201) are transmitted to the terminal. 40.

  Next, the terminal 40 transmits the received data (A1201) to the data migration unit 206.

  Next, the data migration unit 206 verifies the signature of the received data with the public key of the certification authority stored in advance in the data migration unit, and the received public key and the ID of the data migration source IC card 10 are falsified. It is verified whether it is not (S1203). If it is determined that the public key is invalid, the fact is transmitted to the terminal 40. If it is determined that it is a valid public key, then the received public key and random number are written (S1204). Next, a random number is generated internally (S1205). Data obtained by combining the received random number and the generated random number is encrypted using a secret key stored in the key storage 207 to generate authentication data 1 (S1206). Thereafter, the public key of the data migration unit 206, the ID of the data migration destination IC card 20, the signature of the certification authority proving that the key and the ID have not been tampered with, the generated authentication data 1, and a random number ( A1202) is transmitted to the terminal 40.

  Next, the terminal 40 transmits the received data (A1202) to the data migration unit 106.

  Next, the data migration unit 106 verifies the signature of the received data (A1202) with the public key of the certification authority stored in the data migration unit, and among the received data, the public key and the data migration destination IC card 20 It is verified whether the ID has been tampered with (S1207). If it is determined that the public key is invalid, the fact is transmitted to the terminal 40. If it is determined that the public key is valid, then the received public key and random number are written (S1208). Next, the received authentication data 1 is verified with the public key of the data migration unit 206 (S1209). When it is determined that the authentication data is unauthorized, the fact is transmitted to the terminal 40. If it is determined that the authentication data is valid, then the data obtained by combining the random number generated in S1202 and the received random number is encrypted using the secret key stored in the key storage 107, and the authentication data 2 is generated (S1210). Thereafter, the generated authentication data 2 (A1203) is transmitted to the terminal 40.

  Next, the terminal 40 transmits the received data (A1203) to the data migration unit 206.

  Next, the data migration unit 206 verifies the received authentication data 2 (A1203) using the public key of the data migration unit 106 (S1211). When it is determined that the authentication data is unauthorized, the fact is transmitted to the terminal 40. If it is determined that the authentication data is valid, a session key is then generated (S1212). Next, a signature of the created session key is generated using the secret key of the data migration unit 206 (S1213). Next, the session key is encrypted using the public key of the data migration unit 106 (S1214). Thereafter, the generated encryption key data and signature (A1204) are transmitted to the terminal 40.

  Next, the terminal 40 transmits the received data (A1204) to the data migration unit 106.

  Next, the data migration unit 106 verifies the received signature using the public key of the data migration unit 206 (S1215). If it is determined that the signature is invalid, the fact is transmitted to the terminal 40. If it is determined that the signature is valid, then the encrypted key data is decrypted with the secret key of the data migration unit 106 to obtain a session key (S1216).

  Note that the mutual authentication flow shown in FIG. 12 is an example of a mutual authentication flow using public key cryptography. The authentication flow used in this embodiment is not limited to this method.

  FIG. 13 is a diagram showing the format of the migration data created in S509 of FIG.

In the data table (A1301), the ID (A1302) of the migration destination IC card 20 acquired by the ID acquisition command of A501 is arranged at the head. After that, the ID (A1303) of the application unit 103 to which data is migrated and the data (A1304) acquired from the application unit are arranged in pairs. When migrating data from a plurality of application units, the data is associated with a combination of (A1303 ₁ , A1304 ₁ )... (A1303 _n , A1304 _n ), and the data migration destination IC card ID (A1302) is followed. Deploy.

  In addition, this invention is not limited to said embodiment, A various deformation | transformation is possible within the range of the summary.

  For example, two terminals having an IC card access unit similar to the terminal 40 may be connected to the IC cards 10 and 20 and connected to each other terminal via a network.

  In such a configuration, each terminal may have a function of converting a data format that can be transmitted / received over the network and a command format that can be transmitted / received to / from the IC card, in addition to the function of the terminal 40 shown in FIG. Even in this configuration, there is no change in the processing performed in the data migration unit 106 and the data migration unit 206.

It is a figure for demonstrating the structure of the data migration system of the IC card to which one Embodiment of this invention was applied. It is a figure which shows the hardware constitutions of IC card shown in FIG. It is a figure which shows the hardware constitutions of the terminal shown in FIG. It is a figure which shows the data migration processing flow of the data migration system of IC to which one Embodiment was applied. It is a figure which illustrates the flow regarding a data read-out process among the said data migration process flows. It is a figure which illustrates the flow regarding transfer data transmission / reception among the said data transfer processing flows. It is a figure which illustrates the flow regarding data writing among the said data migration process flows. It is a figure which illustrates the flow regarding transfer result transmission / reception among the said data transfer process flows. It is a figure which illustrates the flow regarding data restoration among the said data migration processing flows. It is a figure which illustrates the detailed flow for the authentication process performed inside an IC card. It is a figure which illustrates the flow explaining the authentication process performed between IC cards in detail. It is a figure which illustrates the flow explaining the authentication process in detail when the authentication process of FIG. 11 is replaced with public key authentication. It is a figure which illustrates the data structure of the migration data used in FIGS.

Explanation of symbols

10: IC card, 11: input / output device, 12: CPU, 13: tamper resistant storage device, 14: tamper resistant memory, 15: internal communication line, 20: IC card, 30: communication path, 4041: storage device, 42 : IC card input / output device, 43: CPU, 44: memory, 45: internal communication line, 50: terminal, 60: terminal, 70: network, 101: data transmission / reception unit, 102: command analysis unit, 103 _{1 to} 103 _n : Application unit, 104 _{1 to} 104 _n : Key storage unit, 105 _{1 to} 105 _n : Data storage unit, 106: Data transfer unit, 107: Key storage unit, 108: Data storage unit, 109: Processing progress flag holding unit, 201: data transmission and reception unit, 202: command analyzing _unit, 203 1 _{~203 n:} application _unit, 204 1 to 204 _n: key storage unit, 205 To 205 _n: data storage unit, 206: data migration unit, 207: key storage unit, 208: data storage unit, 209: processing progress flag holding unit, 401: command generation unit, 402: IC card access unit, 501: Command Generation unit, 502: IC card access unit, 503: Data transmission / reception unit, 601: Command generation unit, 602: IC card access unit, 603: Data transmission / reception unit, A501: ID acquisition command, A502: ID, A503: Data migration command A504: Data read command, A505: Data, A506: Data erase command, A507: Response, A601: Encrypted data and signature, A701: Data write command, A702: Response, A703: Data read command, A704: Data, A801 :Processing result Signature, A802: Response, A901: Data write command, A902: Response, A903: Response, A1001: Random number generation command, A1002: Random number, A1003: Authentication data, A1004: Authentication result, A1101: Random number, A1102: Random number data and authentication Data 1, A1103: Authentication data 2 and signature, A1104: Response, A1201: Random number, public key, ID, and signature, A1202: Random number, authentication data 1, public key, ID, and signature, A1203: Authentication data 2, A1204: Encryption Key data and signature, A1301: data table, A1302: data migration destination IC card ID, A1303 _{1 to} A1303 _n : application part ID, A1304 _{1 to} A1304 _n : data.

Claims (9)

A data migration source IC card, and the data transfer destination IC card, an IC card data migration system comprising,
The data migration source IC card includes one or more migration source application units and a migration source data migration unit,
The data migration destination IC card includes a migration destination application unit corresponding to the migration source application unit included in the data migration source IC card, and a migration destination data migration unit,
The migration source data migration unit of the data migration source IC card is
The transition from the data storage unit of the source application portion, the read migration data, storing the transition data in the data storage unit of the migration source data transition,
After the storage, erase the migration data from the data storage unit of the migration source application unit,
After the erase, and out-feed of the transition data stored in the data storage unit of the migration source data transition,
The migration destination data migration unit of the data migration destination IC card is
Receives the transition data output sent from the data migration source IC card,
The data migration system , wherein the received migration data is written in a data storage unit of the migration destination application unit. The IC card data migration system according to claim 1 ,
The migration destination data migration unit of the data migration destination IC card is
Received the migration data was, after I write to the data storage portion of the target application section, read the migration data from the data storage unit,
Wherein the transition data read from the data storage unit, by comparing the transition data to which the migration destination data migration unit receives, to verify the result of the writing process of the transition data,
An IC card data migration system, wherein the migration data migration processing result is transmitted . An IC card data migration system according to claim 1 or 2 ,
In addition, with a terminal,
The terminal
A command generation unit that generates a data migration command for the migration source data migration unit of the data migration source IC card;
An IC card data migration system comprising: an IC card access unit that receives the migration data from the migration source data migration unit and transmits the migration data to the migration destination data migration unit of the data migration destination IC card. An IC card data migration system according to claim 3 ,
The command generator of the terminal is
Obtain the ID of the data migration destination IC card,
Based on the acquired ID, the command generation unit generates a data migration command,
The data migration command is transmitted to the migration source data migration unit in the data migration source IC card via the IC card access unit,
The migration source data migration unit of the data migration source IC card follows the data migration command,
Performing the reading, storing, erasing, and sending of the migration data;
The IC card access part of the terminal receives the transmission is the transition data, and transmits to the destination data transition of the data migration destination IC card
An IC card data migration system characterized by the above. An IC card data migration system according to claim 2,
In addition, with a terminal,
The migration destination data migration unit of the data migration destination IC card transmits the migration data migration processing result to the terminal,
The said terminal transmits the said transfer process result to the said transfer source data transfer part of the said data transfer source IC card, The data transfer system of the IC card characterized by the above-mentioned. An IC card data migration system according to any one of claims 1 to 5 ,
The migration source data migration unit of the data migration source IC card adds an ID of the data migration destination IC card and an ID of the migration destination application unit to the migration data stored in the data storage unit,
The data migration system of an IC card, wherein the migration data migration unit of the data migration destination IC card verifies the two IDs added to the migration data. An IC card data migration system according to claim 6 ,
The data migration source IC card and the data migration destination IC card include a plurality of the application units,
The migration source data migration unit of the data migration source IC card adds an ID that identifies one of the plurality of migration source applications to the migration data stored in the data storage unit,
The migration destination data migration unit of the data migration destination IC card is a migration destination of the migration data based on an ID that identifies one of the plurality of migration destination application units added to the migration data. An IC data migration system characterized by determining a destination application part. An IC card data migration system according to claim 2 or 5 ,
The migration source data migration unit of the data migration source IC card is
The data of the IC card, wherein the migration data moved to the data storage unit of the migration source data migration unit is deleted when the migration process result is received and it is determined that the migration process is successful Migration system. An IC card data migration system according to claim 2 or 5 ,
The migration source data migration unit of the data migration source IC card is
IC card data, wherein the migration data moved to the data storage unit of the migration source data migration unit is restored when the migration process result is received and it is determined that the migration process has failed Migration system.

Images