JP2010117995A - System, device and method for issuing application - Google Patents

Abstract

Provided is a system capable of verifying whether or not a user has applied for an application when downloading the application to a UIM of a mobile phone.
An application issuing system 1 includes a UIM 2 in which an authentication application 24 for authenticating a user authentication code is installed, a mobile phone 3 in which the UIM 2 is installed, and an issuing device 5 for issuing a credit application 25. The issuing device 5 generates an authentication key to be used for authentication of the authentication code input by the user 7 to the mobile phone 3 when receiving the credit application request, and issues the authentication application 24 by writing it in the UIM 2. The second issuing unit 50 issues a credit application 25 to the UIM 2 after allowing the authentication application 24 to authenticate the authentication code input to the mobile phone 3 by the user 7 upon receiving a download request of the one issuing means 50 and the credit application 25. Issuing means 51 is provided.
[Selection] Figure 1

Description

  The present invention relates to a technique for issuing an application to a UIM (UIM: User Identity Module) mounted on a mobile phone.

  In recent years, the use of mobile phones for credit settlement has been studied. When using a mobile phone for credit card payment, a UIM card installed in a mobile phone equipped with a non-contact communication function such as NFC (Near Field Communication) is one of the standards for infrared communication and short-range wireless communication ( When a credit application is installed in a UIM (User Identity Module) and a user who has a mobile phone makes a credit payment, the non-contact communication function of the mobile phone is used to make a credit payment.

  When a mobile phone is used for credit settlement, a credit application, which is an application for using credit settlement, is installed on the UIM card mounted on the mobile phone. Issuing a credit application becomes a problem because it requires a credit check for credit settlement.

  For example, as in the invention disclosed in Patent Document 1, using mobile phone company application information and credit application information combined into one, mobile phone and credit application can be performed simultaneously. The mobile phone service store can issue the mobile phone application and the credit application to the UIM at the same time.

  However, although the mobile phone examination is completed on the same day, if the credit limit is high, it takes several days for the credit examination. Therefore, as in Patent Document 1, the mobile phone application and the credit application are issued simultaneously to the UIM. If it does so, a mobile phone cannot be used from the day when the user applied.

  Of course, it is also technically possible to access the web server operated and managed by the credit company and download the credit application from the web server to the UIM of the mobile phone after starting to use the mobile phone. However, if the credit limit is high, it may take several days for credit credit examination, so it is necessary for the credit company to verify the validity of the user that the credit application downloads to the UIM.

JP 2007-183852 A

  Therefore, in the present invention, when it takes a number of days from application for use of an application, such as a credit application, until the application can be downloaded to the UIM of the mobile phone, when the application is downloaded to the UIM of the mobile phone. An object of the present invention is to provide a system and method capable of verifying the validity of a user who downloads the application to the UIM on the application provider side.

  A first invention that solves the above-described problem includes a UIM preinstalled with an authentication application that authenticates an authentication code of a user possessing the mobile phone using an authentication key, a security domain of the application provider, and the UIM Is an application issuing system configured to issue an application to the UIM attached to the mobile phone, the device for applying for application from the mobile phone. When the access is received, the UIM is requested to input the authentication code, the authentication key is generated from the authentication code input to the mobile phone by the user, and the UIM can be used while the authentication application is available. Write the authentication key under the security domain authority of the first When an issuing means and access for requesting downloading of the application are received from the mobile phone, the user is requested to input the authentication code, and the authentication code input to the mobile phone by the user is authenticated. An application issuing system comprising: a second issuing means for causing an application to authenticate and writing the application under the security domain authority of the UIM when the authentication application succeeds in authenticating the authentication code. It is.

  According to the first invention, since the authentication key used for authentication of the authentication code when downloading the application to the UIM is generated by the device based on the authentication code of the user who applied for the application, The application provider can verify that the user who applied for the application and the user who downloads the application are the same person.

  Further, a second invention is the application issuing system according to the first invention, wherein the first issuing means of the device is generated from the authentication code in association with the unique data of the mobile phone. An authentication key is stored, and the second issuing means encrypts the application to be transmitted to the mobile phone using the authentication key associated with the mobile phone specific information, and the security domain of the UIM is: An application issuing system, wherein an encrypted application is decrypted using the authentication key stored under the security domain authority, and the decrypted application is written under the security domain authority.

  According to the second invention, since a secure channel using the authentication key is established between the UIM and the device, it is possible to ensure the legitimacy between the UIM and the device.

  Further, a third invention is the application issuing system according to the first invention or the second invention, wherein the first issuing means of the device obtains the authentication code from the user, The PIN code of the mobile phone is acquired, the PIN code is authenticated using the function of the mobile phone, and the authentication code is acquired from the user only when the PIN code is successfully authenticated. Application publishing system.

  According to the third invention described above, the user can be authenticated when the first issuing means of the device inputs the authentication code as a basis for generating the authentication key to the mobile phone. become.

  Further, the fourth invention is implemented by a UIM preinstalled with an application provider security domain, an authentication application for authenticating an authentication code of a user carrying the mobile phone using an authentication key, and the UIM An application issuing method using a mobile phone and a device that issues an application to the UIM attached to the mobile phone, when the device receives an access to apply for an application from the mobile phone , Requesting the user to input the authentication code, generating the authentication key from the authentication code input to the mobile phone by the user, and enabling the authentication application to use the security domain authority of the UIM A first issuing step of writing the authentication key below, and the device When the access to request downloading of the application is received from the mobile phone, the user is requested to input the authentication code, and the authentication code input by the user to the mobile phone is authenticated to the authentication application. When the authentication application succeeds in authenticating the authentication code, a second issuing step of writing the application under the security domain authority of the UIM is executed.

  Furthermore, a fifth invention is the application issuing method according to the fourth invention, wherein, in the second issuing step, the device is generated from the authentication code in association with unique data of the mobile phone. The authentication key is stored, and in the second issuing step, the device encrypts the application to be transmitted to the mobile phone using the authentication key associated with the unique information of the mobile phone, and stores the UIM In the application issuing method, the security domain decrypts an encrypted application using the authentication key stored under the security domain authority, and writes the decrypted application under the security domain authority. is there.

  According to the fourth and fifth aspects, the same effects as those of the first and second aspects described above can be obtained.

  According to a sixth aspect of the present invention, there is provided a UIM preinstalled with an application provider security domain, an authentication application for authenticating an authentication code of a user possessing the mobile phone using an authentication key, and a mobile phone on which the UIM is mounted. And a device for issuing an application to the UIM attached to the mobile phone, the device receiving access for applying for an application from the mobile phone. Requesting the user to input the authentication code, generating the authentication key from the authentication code input to the mobile phone by the user, and enabling the authentication application to use the security of the UIM. First issuer who writes the authentication key under domain authority And requesting the user to input the authentication code when receiving access for requesting download of the application from the mobile phone, and sending the authentication code entered by the user to the mobile phone to the authentication application. And a second issuing means for writing the application under the security domain authority of the UIM when the authentication application succeeds in authenticating the authentication code.

  According to the sixth invention, since the authentication key used for authentication of the authentication code when downloading the application to the UIM is generated by the device based on the authentication code of the user who applied for the application, On the application provider side, it is possible to provide an apparatus capable of verifying that the user who has applied for the application and the user who downloads the application are the same person.

  A seventh invention is the device according to the sixth invention, wherein the first issuing means stores the authentication key generated from the authentication code in association with unique data of the mobile phone, and The issuing means encrypts the application to be transmitted to the mobile phone using the authentication key associated with the unique information of the mobile phone, and the security domain of the UIM stores the encrypted application in the security The apparatus is characterized by decrypting using the authentication key stored under domain authority and writing the decrypted application under the security domain authority.

  According to the seventh aspect, since a secure channel using the authentication key is established between the UIM and the device, it is possible to provide a device that can ensure the legitimacy between the UIM and the device.

  An eighth invention is the device according to the sixth invention or the seventh invention, wherein the first issuing means obtains the PIN code of the mobile phone before obtaining the authentication code from the user. The apparatus is characterized in that the authentication code is acquired from the user only when the PIN code is acquired and authenticated using the function of the mobile phone and the PIN code is successfully authenticated.

  According to an eighth aspect of the present invention, there is provided an apparatus capable of performing identity authentication of the user who has input the authentication code, which is the basis for generating the authentication key, by the first issuing means to the mobile phone. can do.

  Furthermore, a ninth invention is a program for causing a computer to operate as the apparatus according to any one of the sixth to eighth inventions by being incorporated in the computer.

According to the ninth aspect, the computer can function as the device according to any one of the sixth to eighth aspects.

  As described above, according to the present invention, when it takes a number of days from applying for use of an application to downloading the application to the mobile phone UIM, such as a credit application, the application is transferred to the mobile phone UIM. When downloading, it is possible to provide a system, an apparatus, and a method capable of verifying the validity of a user who downloads the application into the UIM on the application provider side.

  Hereafter, the best embodiment of the present invention will be described in detail with reference to the drawings. FIG. 1 is a diagram illustrating the configuration of an application issuing system 1 according to the present embodiment.

  As shown in FIG. 1, an application issuing system 1 according to the present embodiment includes a mobile phone 3 to which a UIM 2 (User Identity Module) is attached and an issuing device 5 that is a web server managed and operated by a credit company. At least configured, each of the mobile phone 3 and the issuing device 5 is connected to a network line network 4 including a wireless communication station of the mobile phone 3.

  When the UIM2 is manufactured, the security domain of the mobile phone 3 is implemented by the UIM2 manufacturing company, and a mobile phone application for using the mobile phone 3 is pre-installed in the UIM2 under the security domain authority of the mobile phone 3. Installed.

  When the user 7 applies for the use of the mobile phone 3, the terminal device installed at the service store of the mobile phone company issues a mobile phone application placed under the security domain authority of the mobile phone company and an authentication code. The installation of the authentication application used to authenticate the user 7 and the installation of the security domain of the credit company are executed by the security domain of the mobile phone company.

  The authentication application installed by the mobile phone company security domain is placed under the credit company security domain authority by the Install for Extradition command. When the user 7 applies for credit, the authentication application is installed by the credit company security domain. Is issued.

  When the authentication application is installed in the UIM 2, data such as an authentication key used for authenticating the authentication code of the user 7 is not written under the security company authority of the credit company, and the user 7 Is issued to the issuing device 5, the issuing device 5 generates an authentication key and challenge to be used for authentication of the authentication code entered by the user 7 into the mobile phone 3, and the credit company security domain is used by the authentication application. When possible, the authentication application is issued by writing the authentication key and the challenge under the security company authority of the credit company.

  When the credit examination related to the use of the credit service of the user 7 passes and the credit application is downloaded to the UIM 2 of the mobile phone 3, the authentication application authenticates the authentication code of the user 7 who operates the mobile phone 3. When the validity of the user 7 is verified and the authentication code is successfully authenticated, a secure channel is constructed between the credit company security domain and the issuing device 5 using the authentication key used to authenticate the authentication code. The UIM2 credit application is written under the security company authority of the credit company according to the security domain of the company, and the credit application is issued to the UIM2.

  As described above, according to the application issuing system 1 in the present embodiment, the authentication key used for authenticating the authentication code of the user 7 who downloads the credit application is based on the authentication code of the user 7 who applied for credit. Therefore, the credit company that provides the credit application can verify that the user 7 who applied for credit and the user 7 who downloads the credit application are the same person.

  Furthermore, when a credit application is downloaded, a secure channel is established between the credit company security domain installed in the UIM 2 and the issuing device 5 using an authentication key used for authenticating the authentication code of the user 7. The correctness between the UIM 2 and the issuing device 5 can be secured.

  First, the mobile phone 3, UIM2, and issuing device 5 that constitute the application issuing system 1 shown in FIG. 1 will be described.

  FIG. 2 is a block diagram of the mobile phone 3 and the UIM 2. As shown in FIG. 2, the mobile phone 3 shown in FIG. 1 is a mobile phone 3 compatible with NFC (NFC: Near Field Communication) which is one of non-contact communication standards.

  As the mobile phone 3 compatible with NFC, since the mobile phone 3 compatible with FeliCa standardized by ISO / IEC18092 is widely used, a detailed description is omitted here. 3, a Java (registered trademark) Virtual Machine (hereinafter referred to as JVM), a processor 30 for controlling execution of a browser and data communication, an NFC chip 31 (here, an IC chip for FeliCa), and the like. The UIM 2 is mounted so that it can communicate with the NFC chip 31.

  An IC chip for an IC card equipped with a CPU (Central Processing Unit), a RAM (Random Access Memory), and the like is mounted on the UIM 2 mounted on the mobile phone 3, and a platform type operating system is mounted on the IC chip. A Java (registered trademark) Card Virtual Machine 22 (hereinafter referred to as JCVM) is constructed, and the JCVM 22 includes an ISD 20 (ISD: Issuer Security Domain), which is a security domain of a mobile phone company, as an applet serving as a card manager, An SSD 21 (SSD: Supplementary Security Domain), which is a security domain other than the telephone company (here, a credit company), is implemented.

  The ISD 20 is an applet managed by a UIM2 issuer (in this case, a mobile phone company), and has a function of installing the SSD 21 in the UIM2, a function of installing an application of the mobile phone company under the authority of the ISD20, and the like.

  The SSD 21 is an applet managed by a person other than the UIM2 issuer (here, a credit company), and has a function of installing a credit company application (here, the credit application 25) under the authority of the SSD 21. .

  When the ISD 20 and the mobile phone application 23 are installed in the UIM 2 and the mobile phone 3 is delivered to the user 7 in the UIM2 manufacturing company, the issuing machine installed in the service counter of the mobile phone 3 issues the mobile phone application 23, The installation of the authentication application 24 and the installation of the SSD 21 are executed by the ISD 20, and the authentication application 24 shifts from the authority of the ISD 20 to the authority of the SSD 21 by the Install for Extradition command of the ISD 20.

  The authentication application 24 placed under the authority of the SSD 21 is an application for authenticating the authentication code of the user 7, and the SSD 21 controls the installation of the credit application 25 according to the processing result of the authentication application 24.

  Here, the authentication code means data used for user authentication, and means a password of the user 7 or biometric data of the user 7 (for example, fingerprint data or voiceprint data).

  At the time when the authentication application 24 is installed under the authority of the SSD 21, the authentication application 24 is in an initialized state, and data necessary for authenticating the authentication code is not written under the authority of the SSD 21, and the user 7 carries the mobile phone. When the telephone 3 is operated to apply for a credit to the issuing device 5, an authentication key and a challenge are obtained from the authentication code input to the mobile phone 3 by the user 7 as data used when the authentication application 24 authenticates the authentication code. Generated by the issuing device 5, the authentication key and the challenge are written under the authority of the SSD 21.

  When the credit examination of the user 7 passes and the credit application 25 is downloaded from the issuing device 5, the authentication application 24 authenticates the authentication code of the user 7 who operates the mobile phone 3, and when the authentication is successful, the SSD 21 Installs the credit application 25 on the mobile phone 3 under the authority of the SSD 21.

  FIG. 3 is a block diagram of the issuing device 5 which is a web server managed by a credit company. The issuing device 5 has the same hardware resources (for example, CPU, RAM, hard disk, etc.) as a general-purpose web server, and an authentication application loaded on the UIM 2 of the mobile phone 3 as a function provided in the issuing device 5 by a computer program. 24, a second issuing means 51 for installing the credit application 25 in the UIM 2 of the mobile phone 3, and the issuing device 5 further includes a tamper resistant device for securely performing cryptographic operations. HSM6 (HSM6: Hardware Security Module) is connected.

  As shown in FIG. 3, the first issuing means 50 of the issuing device 5 is a program that operates on the JVM of the mobile phone 3, acquires an authentication code from the user 7 who operates the mobile phone 3, and the authentication code Is sent to the first issuing means 50 of the issuing device 5 and the authentication application 24 is available, the authentication key and challenge received from the first issuing means 50 are written to the SSD 21, and the authentication application 24 is It has the 1st applet 50a provided with the function to issue.

  When the first issuing means 50 of the issuing device receives a credit application request from the mobile phone 3, the first issuing means 50 of the issuing device 5 transmits the first applet 50 a described above to the mobile phone 3. . When the first issuing means 50 receives the authentication code from the first applet 50a operating on the mobile phone 3, the first issuing means 50 uses the HSM 6 connected to the issuing device 5 to obtain the authentication key from the authentication code. And a challenge for authenticating the authentication code using the authentication key.

  When the first issuing means 50 of the issuing device 5 generates the authentication key and the challenge, it can be used as a session key for establishing a secure channel between the UIM 2 and the issuing device 5 (for example, unique data (for example, , The authentication key generated in association with the telephone number of the mobile phone 3) is stored in the hard disk of the issuing device 5 and the authentication key and the challenge are transmitted to the first applet 50a of the mobile phone 3 to the mobile phone 3. The authentication application 24 installed in the attached UIM 2 is issued.

  Note that the PIN code of the mobile phone 3 is acquired from the user 7 to the first applet 50a transmitted from the first issuing means 50 of the issuing device 5 to the mobile phone 3, and the function of the mobile phone 3 is used. If a function for authenticating the PIN code is provided, the validity of the user 7 can be verified when applying for credit.

  Further, as shown in FIG. 3, the second issuing means 51 of the issuing device 5 is a program that operates on the JVM of the mobile phone 3, acquires an authentication code from the user 7 who operates the mobile phone 3, A function for authenticating the authentication code to the authentication application 24. When the authentication code is successfully authenticated, the credit application 25 is requested from the second issuing means 51 to transmit the credit application 25 and received from the second issuing means 51. A second applet 51 a having a function of requesting the SSD 21 to install 25.

  When the second issuing means 51 of the issuing device 5 receives the download request for the credit application 25 from the mobile phone 3, the second issuing means 51 of the issuing device 5 sends the second applet 51 a to the mobile phone 3. Send to. When the second issuing means 51 receives the transmission request of the credit application 25 from the second applet 51a operating on the mobile phone 3, the second issuing means 51 stores the authentication key stored in association with the fixed data of the mobile phone. Is used to encrypt the credit application 25, transmit the encrypted credit application 25 to the second applet 51a, and cause the second applet 51a to issue the credit application 25.

  When receiving the encrypted credit application 25 from the second issuing means 51 of the issuing device 5, the second applet 51 a operating on the mobile phone 3 requests the SSD 21 to install the credit application 25.

  The second applet 51a operating on the mobile phone 3 divides the encrypted credit application 25 into predetermined blocks and transmits it to the SSD 21. The SSD 21 stores the authentication key stored under the authority of the SSD 21. Is used to decrypt the encrypted block of the credit application 25 and write the decrypted block of the credit application 25 under the authority of the SSD 21, so that the credit application 25 is installed in the UIM 2.

  From here on, a series of procedures executed by the application issuing system 1 will be described together with description of the method according to the present invention. 4 is a flowchart showing a procedure for issuing the authentication application 24 installed in the UIM 2 of the mobile phone 3, and FIG. 5 is a flowchart showing a procedure for installing the credit application 25 in the UIM 2 of the mobile phone 3. is there.

  First, the procedure for issuing the authentication application 24 will be described with reference to FIG. When a user 7 operates the mobile phone 3 to access a predetermined URL of the issuing device 5 in order to make a credit use application request (S1), the mobile phone 3 and the issuing device 5 use an encryption protocol (for example, SSL: Secure When the user 7 clicks a predetermined button after the user 7 inputs data necessary for the credit use application such as the name and address of the user 7 to the issuing device 5, the first of the issuing device 5 is transmitted. The first issuing means 50 transmits the first applet 50a to the mobile phone 3 (S2).

  When the first applet 50a is transmitted to the mobile phone 3 and activated on the mobile phone 3, the first applet 50a prompts the user 7 to input the PIN code (PIN: Personal identification number) of the mobile phone 3. When the PIN code is input to the mobile phone 3, the PIN code stored in the memory of the mobile phone 3 or the ISD 20 authority of the UIM 2 is input using the function of the mobile phone 3. The PIN code is collated, and the validity of the user 7 who operates the mobile phone 3 is verified (S3).

  The first applet 50a branches the process according to the PIN code processing result of the mobile phone 3 (S4). When the authentication of the PIN code of the mobile phone 3 is successful, the process of issuing the authentication application 24 is continued. If the PIN code authentication of the mobile phone 3 fails, the process of issuing the authentication application 24 is interrupted, and this procedure is terminated.

  When the authentication of the PIN code of the mobile phone 3 is successful, the first applet 50a displays a screen prompting the user 7 to input the authentication code on the display of the mobile phone 3, and the authentication input by the user 7 to the mobile phone 3 The code is acquired and the authentication code is transmitted to the issuing device 5 (S5).

  Specifically, the authentication code of the user 7 means the password of the user 7, biometric data of the user 7 (for example, fingerprint data), and the method by which the first applet 50a acquires the authentication code varies depending on the authentication code. .

  For example, when the password of the user 7 is used as an authentication code, the first applet 50a displays a screen on which a form for entering the password is displayed on the display of the mobile phone 3, and the user 7 Acquire the characters and numbers entered using as the authentication code.

  When the biometric data of the user 7 (here, fingerprint data) is used as an authentication code, the first applet 50a sends a message for causing the fingerprint sensor provided in the mobile phone 3 to read the fingerprint data. The fingerprint data obtained from the fingerprint sensor of the mobile phone 3 is acquired as an authentication code.

  When the first issuing means 50 of the issuing device 5 receives the authentication code from the first applet 50a operating on the mobile phone 3, it uses the HSM 6 to generate an authentication key from the authentication code, In accordance with the algorithm, a challenge is generated from the authentication code using the authentication key, and the authentication key and the challenge are transmitted to the first applet 50a of the mobile phone 3 (S6).

  When the first applet 50a operating on the mobile phone 3 receives the authentication key and challenge from the issuing device 5, the first applet 50a transmits a command for writing the authentication key and challenge to the authentication application 24 to the SSD 21 (S7). However, by writing the authentication key and the challenge to a file under the authority of the SSD 21, the authentication key and the challenge are written under the authority of the SSD 21 while the authentication application 24 is available, and the authentication application 24 is issued (S8 ), This procedure ends.

  Next, a procedure for installing the credit application 25 in the UIM 2 of the mobile phone 3 will be described with reference to FIG.

  After the procedure of FIG. 4 is executed, if the credit examination of the user 7 who applied for the use of the credit service is passed in S1 of FIG. 4, the issuing device 5 sends the mobile phone 3 possessed by the user 7 by e-mail or the like. Then, it is notified that the credit examination is completed (S10).

  The notification describes the URL of the issuing device 5 that is accessed when the credit application 25 is downloaded. When the user 7 accesses the URL by operating the mobile phone 3, the mobile phone 3 and the issuing device 5 are accessed. When the user 7 performs a predetermined operation and makes a download request for the credit application 25 to the issuing device 5 (S11), the second issuing means 51 of the issuing device 5 operates, and the second issuing means 51 operates. The issuing means 51 transmits the second applet 51a to the mobile phone 3 that has accessed the URL (S12).

  When the second applet 51a operates on the mobile phone 3, the second applet 51a displays a screen for prompting the input of the authentication code on the display of the mobile phone 3 as in S5 of FIG. The authentication code input to the mobile phone 3 is acquired (S13), and the authentication application 24 under the authority of the SSD 21 is requested to authenticate the authentication code (S14).

  Upon receiving the authentication code authentication request from the second applet 51a, the UIM2 authentication application 24 follows the same algorithm as the first issuing means 50 of the issuing device 5 and takes a challenge from the authentication code received from the second applet 51a. The authentication code received from the second applet 51a is authenticated by collating with the challenge generated and executed in the procedure of FIG. 4 and written in the authentication application 24 (S15).

  The second applet 51a branches the process depending on the authentication result of the authentication application 24 (S16). When the authentication result obtained from the authentication application 24 indicates success, the issuance process of the credit application 25 is continued, and the authentication application When the authentication result obtained from 24 indicates failure, the issuing process of the credit application 25 is interrupted, and this procedure is terminated.

  When the authentication result obtained from the authentication application 24 indicates success, the second applet 51a requests the issuing device 5 to transmit the credit application 25 (S17).

  When the issuing device 5 receives a transmission request of the credit application 25 from the second applet 51a activated on the mobile phone 3, the issuing device 5 acquires an authentication key stored in association with the specific data of the mobile phone 3, Using the authentication key, the credit application 25 in which personal information (for example, name) of the user 7 is written is encrypted, and the encrypted credit application 25 is transmitted to the second applet 51a of the mobile phone 3 (S18). .

  When the second applet 51a operating on the mobile phone 3 receives the encrypted credit application 25 from the issuing device 5, the second applet 51a requests the SSD 21 to install the encrypted credit application 25 (S19). .

  The second applet 51a operating on the mobile phone 3 divides the encrypted credit application 25 into predetermined blocks and transmits it to the SSD 21. The SSD 21 stores the authentication key stored under the authority of the SSD 21. Is used to decrypt the encrypted block of the credit application 25 and write the decrypted block of the credit application 25 under the authority of the SSD 21 to install the credit application 25 in the UIM 2 (20).

The figure explaining the structure of an application issuing system. The block diagram of a mobile telephone and UIM. The block diagram of an issuing apparatus. The flowchart which showed the procedure which issues an authentication application. The flowchart which showed the procedure which installs a credit application.

Explanation of symbols

1 Application issue system 2 UIM
20 ISD
21 SSD
23 Virtual Machine
24 authentication application 25 credit application 3 mobile phone 4 network 5 issuing device 50 first issuing means 50a first applet 51 second issuing means 51a second applet 6 HSM

Claims (9)

  A security domain of the application provider, a UIM preinstalled with an authentication application for authenticating an authentication code of a user possessing the mobile phone using an authentication key, a mobile phone on which the UIM is mounted, and the mobile phone An application issuance system comprising an apparatus that issues an application to the installed UIM, and the apparatus receives the authentication code from the mobile phone when receiving an access to apply for an application from the mobile phone. The authentication key is generated from the authentication code input to the mobile phone by the user, and the authentication key is written under the security domain authority of the UIM in a state where the authentication application can be used. The first issuing means and the mobile phone When the access for requesting the download of the application is received, the user is requested to input the authentication code, the authentication code input by the user to the mobile phone is authenticated by the authentication application, and the authentication application An application issuing system comprising: a second issuing means for writing the application under the security domain authority of the UIM when the authentication code is successfully authenticated.   2. The application issuing system according to claim 1, wherein the first issuing means of the device stores the authentication key generated from the authentication code in association with unique data of the mobile phone, Issuing means encrypts the application to be transmitted to the mobile phone using the authentication key associated with the specific information of the mobile phone, and the security domain of the UIM stores the encrypted application in the security domain An application issuance system characterized by decrypting using the authentication key stored under authority and writing the decrypted application under the security domain authority.   The application issuing system according to claim 1 or 2, wherein the first issuing means of the device acquires the PIN code of the mobile phone before acquiring the authentication code from the user, An application issuing system, wherein the PIN code is authenticated by using a function of the mobile phone, and the authentication code is obtained from the user only when the PIN code is successfully authenticated.   A security domain of the application provider, a UIM preinstalled with an authentication application for authenticating an authentication code of a user possessing the mobile phone using an authentication key, a mobile phone on which the UIM is mounted, and the mobile phone An application issuance method using a device that issues an application to the installed UIM, and when the device receives an access to apply for an application from the mobile phone, Requesting input, generating the authentication key from the authentication code input by the user to the mobile phone, and writing the authentication key under the security domain authority of the UIM in a state where the authentication application is available 1 issuance process and the device is When the access for requesting the download of the application is received, the user is requested to input the authentication code, the authentication code input to the mobile phone by the user is authenticated by the authentication application, and the authentication application If the authentication code is successfully authenticated, a second issuing step of writing the application under the security domain authority of the UIM is executed.   5. The application issuing method according to claim 4, wherein in the second issuing step, the device stores the authentication key generated from the authentication code in association with unique data of the mobile phone, and 2, the device encrypts the application to be transmitted to the mobile phone using the authentication key associated with the mobile phone specific information, and the security domain of the UIM is encrypted An application issuing method, comprising: decrypting an application using the authentication key stored under the security domain authority, and writing the decrypted application under the security domain authority.   A security domain of the application provider, a UIM preinstalled with an authentication application for authenticating an authentication code of a user possessing the mobile phone using an authentication key, a mobile phone on which the UIM is mounted, and the mobile phone A device in an application issuance system configured with a device that issues an application to the UIM that is installed, the device receiving the access to apply for the application from the mobile phone, Requesting the input of the authentication code, generating the authentication key from the authentication code input by the user to the mobile phone, and using the authentication application under the security domain authority of the UIM in a state where the authentication application is available A first issuing means for writing a key; When receiving an access for requesting download of the application from a story, the user is requested to input the authentication code, the authentication code input by the user to the mobile phone is authenticated by the authentication application, And a second issuing means for writing the application under the security domain authority of the UIM when the authentication application succeeds in authenticating the authentication code.   7. The apparatus according to claim 6, wherein the first issuing means of the apparatus stores the authentication key generated from the authentication code in association with unique data of the mobile phone, and the second issuing The means encrypts the application to be transmitted to the mobile phone using the authentication key associated with the unique information of the mobile phone, and the security domain of the UIM has the encrypted application under the security domain authority. And decrypting the decrypted application using the authentication key stored therein, and writing the decrypted application under the security domain authority.   The apparatus according to claim 6 or 7, wherein the first issuing means of the issuing device acquires the PIN code of the mobile phone before acquiring the authentication code from the user, An apparatus characterized in that a PIN code is authenticated using a function of the mobile phone, and the authentication code is acquired from the user only when the PIN code is successfully authenticated. A program that causes a computer to operate as the apparatus according to any one of claims 6 to 8 by being incorporated in the computer.

Images