Information processing device, information processing method, program, and information processing system

Abstract

The present disclosure relates to an information processing device, an information processing method, a program, and an information processing system which make it possible to flexibly use a storage area of a secure element. When an external trigger is acquired from an external trigger device, an applet is installed on or deleted from a secure element in accordance with the type of the acquired trigger. The present disclosure is applicable to an electronic device which is provided with a secure element.

Description

[Technical field]

[0001] The present disclosure relates to an information processing device, an information processing method, a program, and an information processing system, and more particularly to an information processing device, an information processing method, a program, and an information processing system that enable flexible use of the storage area of ​​a secure element. [Background technology]

[0002] An applet that is incorporated into and executed in an application program available to the user contains secure information such as IDs, keys, and logs required to execute the application program, and is generally mounted on an OS such as Java (registered trademark) Card OS within a secure element.

[0003] However, there is an upper limit to the capacity that can be used as an applet storage area within a secure element, from the viewpoint of the cost of the secure element (chip) and the smartphone or the like equipped with the secure element.

[0004] As the number of secure application programs that use applets within the secure element, such as those for payment, electronic transportation passes (transportation tickets), and user authentication, increases, it becomes necessary for users themselves to manage the number of applets that use the finite applet storage area.

[0005] In this case, the user must delete and add applets as necessary.

[0006] Therefore, technologies have been proposed to automatically delete registered applets based on the period during which the registered applet is desired to be used, using a pre-registered deletion date and time, deletion time, or deletion count value from the registration timing (see Patent Documents 1 and 2).

[0007] Furthermore, a technique has been devised that enables registered applets to be automatically deleted in response to changes in location information (see Patent Document 3). [Prior art documents] [Patent documents]

[0008] [Patent Document 1] JP 2005-11469 A [Patent Document 2] Japanese Patent Application Publication No. 8-328915 [Patent Document 3] JP 2003-280992 A Summary of the Invention [Problem to be solved by the invention]

[0009] However, in any of Patent Documents 1 to 3, the user's condition settings for deleting applets registered in a storage area are uniform (Single Trigger) such as the registration period and location information.

[0010] For this reason, applets cannot be deleted or re-added depending on the user's daily activities, etc., and the storage area of ​​the secure element cannot be utilized flexibly.

[0011] The present disclosure has been made in consideration of such circumstances, and in particular enables applets registered in the memory area of ​​a secure element to be deleted or re-added depending on user behavior, etc., thereby enabling flexible use of the memory area of ​​the secure element. [Means for solving the problem]

[0012] According to one aspect of the present disclosure, there is provided an information processing device, a program, and an information processing system, the information processing device including: a trigger acquisition unit that acquires a trigger; and a management unit that manages applets in a secure element based on the trigger. The management unit installs the applet in the secure element based on the trigger, and when installing the applet in the secure element, registers a trigger that is a deletion condition for the installed applet as a deletion trigger rule, and if the trigger is a trigger registered as the deletion trigger rule, deletes the installed applet, manages a log of the installed applet, and when deleting the installed applet, deletes a part of the log and deletes it together with the installed applet, and registers a type of information of the log other than the part that is not deleted as information in the deletion trigger rule in association with the applet.An information processing device, a program, and an information processing system.

[0013] An information processing method according to one aspect of the present disclosure includes: acquiring a trigger; Acquisition and processing Manage applets in a secure element based on the trigger. Management and processing Including the management process installs the applet in the secure element based on the trigger, and when installing the applet in the secure element, registers a trigger that is a deletion condition for the installed applet as a deletion trigger rule, and if the trigger is a trigger registered as the deletion trigger rule, deletes the installed applet, manages a log of the installed applet, and when deleting the installed applet, deletes a part of the log and deletes it together with the installed applet, and registers a type of information of the log other than the part that is not deleted as information in the deletion trigger rule in association with the applet. It is an information processing method.

[0014] In one aspect of the present disclosure, a trigger is obtained, and an applet in a secure element is managed based on the trigger. Based on the trigger, an applet in the secure element is installed, and when the applet in the secure element is installed, a trigger that becomes a deletion condition for the installed applet is registered as a deletion trigger rule, and if the trigger is a trigger registered as the deletion trigger rule, the installed applet is deleted, and a log of the installed applet is managed, and when the installed applet is deleted, a part of the log is deleted and deleted together with the installed applet, and a type of information of the log other than the part that is not deleted is registered in correspondence with the applet as information in the deletion trigger rule. do. [Brief description of the drawings]

[0015] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of an information processing system according to the present disclosure. [Diagram 2] FIG. 2 is a diagram illustrating an example of the configuration of the electronic device in FIG. [Diagram 3] 3 is a diagram illustrating an example of the configuration of the secure element in FIG. 2; [Figure 4] 2 is a diagram illustrating an example of the configuration of a server in FIG. 1; [Diagram 5] FIG. 13 is a diagram illustrating the operation of installing an applet in a secure element. [Figure 6] FIG. 13 is a diagram illustrating an operation of deleting an applet in a secure element. [Figure 7] 11 is a flowchart illustrating an applet issuing process. [Figure 8] 13 is a flowchart illustrating a process of deleting an applet. [Figure 9] FIG. 13 is a diagram illustrating the operation of installing an applet as an electronic ticket. [Figure 10] FIG. 13 is a diagram for explaining the operation of deleting an applet as an electronic ticket. [Figure 11] 13 is a flowchart illustrating an electronic ticket issuing process. [Figure 12] 13 is a flowchart illustrating an electronic ticket deletion process. [Figure 13] FIG. 13 is a diagram illustrating the operation of installing an applet as an administrative ID. [Figure 14] FIG. 13 is a diagram illustrating the operation of deleting an applet as an administrative ID. [Figure 15] 13 is a flowchart illustrating an administrative ID issuing process. [Figure 16] 13 is a flowchart illustrating an administrative ID deletion process. [Figure 17] FIG. 13 is a diagram for explaining the operation of installing an applet as an electronic transportation pass. [Figure 18] FIG. 13 is a diagram for explaining the operation of deleting an applet as a transportation electronic path. [Figure 19] 13 is a flowchart illustrating a transportation electronic pass issuing process. [Figure 20] 13 is a flowchart illustrating a transportation electronic pass deletion process. [Figure 21] FIG. 11 is a diagram illustrating an operation of installing an applet in the wearable device system. [Figure 22] 11 is a diagram illustrating an operation for deleting an applet in the wearable device system. FIG. [Figure 23] FIG. 1 is a diagram illustrating an example of the configuration of a general-purpose personal computer. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In this specification and the drawings, components having substantially the same functional configurations are denoted by the same reference numerals, and redundant description will be omitted.

[0017] Hereinafter, an embodiment of the present technology will be described in the following order. 1. Preferred Embodiments 2. Variations 3. Software implementation example

[0018] <<1. Preferred embodiment>> <Configuration example of information processing system according to the present disclosure> In particular, the present disclosure enables flexible use of the memory area of ​​a secure element by allowing applets registered in the memory area of ​​the secure element to be deleted or re-added depending on user behavior.

[0019] FIG. 1 shows an example of the configuration of an information processing system to which the technology of the present disclosure is applied.

[0020] In the information processing system 11 of Figure 1, an electronic device equipped with a secure element owned by a user registers (installs) an applet (in the secure element) and uses the registered applet to communicate with a management device, which is a transaction device, to realize various transaction processes.

[0021] At this time, in the information processing system 11 of FIG. 1, applets registered in the electronic device are registered, deleted, or re-added to the secure element in response to the user's actions.

[0022] Here, the applet realizes a function as a stored value card such as a transit card or a prepaid card, in addition to the function of realizing the above-mentioned settlement corresponding to a credit card account or a debit card account, for example.

[0023] Applets may also function as access cards, such as for security door access, vehicle control or access, e.g., car control and boat control, loyalty cards, tickets (e.g., government ID for administrative procedures, electronic tickets for travel or events), and multi-function cards (cards used for access, identification, and payment).

[0024] It should be noted that various cards are used herein by way of example to refer to credentials issued by entities such as banks, credit providers, commercial entities, government agencies, etc.

[0025] The information processing system 11 in FIG. 1 is composed of electronic devices 31-1 to 31-n, a server 32, R / W (reader / writers) 33-1 to 33-n, and management devices 34-1 to 34-n, and is configured to be able to electrically communicate with each other via a network 35 consisting of the Internet, a dedicated line, or the like.

[0026] In addition, in FIG. 1, when there is no particular need to distinguish between the electronic devices 31-1 to 31-n, the R / Ws (reader / writers) 33-1 to 33-n, and the management devices 34-1 to 34-n, they will be simply referred to as the electronic devices 31, the R / Ws 33, and the management device 34, respectively.

[0027] In addition, in FIG. 1, the electronic device 31, the R / W 33, and the management device 34 are depicted as having corresponding configurations and consisting of the same number of components, but they do not have to correspond to each other, and they do not have to be the same number.

[0028] That is, in FIG. 1, electronic device 31-1 is depicted as corresponding to R / W 33-1 and management device 34-1, and as being configured to communicate with each other, but electronic device 31-1 is also capable of communicating with R / W 33-2 and management device 34-2, or with R / W 33-n and management device 34-n.

[0029] Furthermore, although only one server 32 is illustrated in FIG. 1, the server 32 may be configured with multiple computers using cloud computing or the like.

[0030] The network 35 communicably connects, for example, electronic devices 31-1 to 31-n and management devices 34-1 to 34-n, which are wireless transaction devices, to a service provider and a server 32 that manages the transaction system.

[0031] At least one of the electronic devices 31-1 to 31-n communicates with one of the management devices 34-1 to 34-n, which are wireless transaction devices, via one of the R / Ws 33-1 to 33-n by direct communication such as near field communication (NFC).

[0032] The management devices 34-1 to 34-n communicate with any of the electronic devices 31-1 to 31-n via the R / Ws 33-1 to 33-n, and function, for example, as an entrance gate opening / closing management device for an event venue etc. using electronic tickets, a personal information disclosure management device based on an administrative ID, and a ticket gate management device using an electronic transportation pass.

[0033] Furthermore, the management devices 34-1 to 34-n may function as other devices, such as a transit management device, a toll management device, a parking management transaction device, a point of sale management device, a wireless mobile management device, or an access management device such as a door or lock.

[0034] Furthermore, the R / Ws 33-1 to 33-n are, for example, devices such as wireless interfaces, and realize communication between any of the electronic devices 31-1 to 31-n and any of the management devices 34-1 to 34-n, for example, through NFC wireless communication, wireless local area network (WLAN) wireless communication, Bluetooth (registered trademark) wireless communication, Zigbee (registered trademark) wireless communication, cellular wireless communication, and other wireless communication.

[0035] Server 32 may be managed, for example, by a financial institution that issues credit or debit cards, a manufacturer of access devices such as transportation agencies, doors, locks, etc., an entity that utilizes access devices such as a company, school, etc., a manufacturer of vehicles such as automobiles, a retailer that offers loyalty card accounts, a ticketing service provider that offers tickets to events, a travel service provider that offers tickets for travel such as airline tickets, or generally any service provider that can provide virtual or physical passes, tickets, cards, etc. to users.

[0036] The electronic devices 31-1 to 31-n are, for example, personal computers, smartphones, peripheral devices (e.g., digital cameras, headphones), tablet devices, or devices that include at least one wireless interface of NFC wireless communication, WLAN wireless communication, Bluetooth (registered trademark) wireless communication, Zigbee (registered trademark) wireless communication, cellular wireless communication, and other wireless communication.

[0037] The electronic devices 31-1 to 31-n each include a secure element 58 (FIGS. 2 and 3) that requests an applet from the server 32, installs (registers) the applet, and executes the installed applet to provide various services between the electronic devices 31-1 to 31-n and the management device 34 via the R / W 33. The secure element 58 will be described in detail later with reference to FIG.

[0038] <Examples of electronic device configurations> Next, a configuration example of the electronic device 31 in FIG. 1 will be described with reference to FIG.

[0039] The electronic device 31 is composed of a control unit 51, an input unit 52, an output unit 53, a memory unit 54, a communication unit 55, a drive 56, a removable storage medium 57, and a secure element 58, which are connected to each other via a bus 59 and can send and receive data and programs.

[0040] The control unit 51 is composed of a processor and a memory, and controls the overall operation of the electronic device 31 .

[0041] In addition, the control unit 51 executes the host program 61 to obtain and supply various triggers for managing applets installed in the secure element 58 .

[0042] The input unit 52 is made up of input devices such as a keyboard through which the user inputs operation commands and a microphone through which voice input is performed, and supplies various input signals to the control unit 51 .

[0043] The output unit 53 is composed of an audio output unit consisting of a speaker etc., a display unit consisting of an LCD (Liquid Crystal Display) or an organic EL (Organic Electro-Luminescence) etc., a light emitting unit consisting of an LED (Light Emitting Diode) etc., and is controlled by the control unit 51 to present various processing results to the user.

[0044] The storage unit 54 is composed of a hard disk drive (HDD), a solid state drive (SSD), a semiconductor memory, or the like, and is controlled by the control unit 51 to write or read various data including content data and programs.

[0045] The communication unit 55 is controlled by the control unit 51, and transmits and receives various data and programs to and from various devices via the network 35 (FIG. 1).

[0046] Further, the communication unit 55 is controlled by the control unit 51 to realize communication with the management device 34 via the R / W 33 .

[0047] The drive 56 reads and writes data from and to a removable storage medium 57 such as a magnetic disk (including a flexible disk), an optical disk (including a CD-ROM (Compact Disc-Read Only Memory) and a DVD (Digital Versatile Disc)), a magneto-optical disk (including an MD (Mini Disc)), or a semiconductor memory.

[0048] The secure element 58 communicates data with the management device 34 via the communication unit 55 and the R / W 33, and executes various types of processing. More specifically, the secure element 58 executes processing (command processing) according to a command (processing request) received from the communication unit 55 by executing an installed applet. The secure element 58 then transmits a response (processing response) that is the execution result of the command processing to the management device 34. Through this series of processing, various types of processing according to the type of applet are executed.

[0049] Furthermore, the secure element 58 installs corresponding applets based on various trigger information supplied from the external trigger device 131 (FIG. 5), executes the installed applets, and deletes or reinstalls the applets as necessary. The secure element 58 will be described in detail later with reference to FIG. 3.

[0050] <Example of secure element configuration> Next, a configuration example of the secure element 58 will be described with reference to FIG.

[0051] The secure element 58 is formed as an IC module including an IC (Integrated Circuit) chip in, for example, a plastic card substrate (an example of a card body). That is, the secure element 58 includes an IC module including an IC chip and a card substrate in which the IC module is embedded. The IC chip is, for example, an LSI (Large Scale Integration) such as a one-chip microprocessor.

[0052] The secure element 58 includes an I / F (interface) 72, a processor 71 consisting of a CPU (Central Processing Unit) etc., a ROM (Read Only Memory) 73, a RAM (Random Access Memory) 74, and an EEPROM (Electrically Erasable Programmable ROM) 75.

[0053] The I / F 72 performs serial data communication with the communication unit 55, for example. The I / F 72 outputs data (for example, 1 byte data) obtained by converting a received serial data signal into parallel data to the processor 71. The I / F 72 also converts data acquired from the processor 71 into serial data and outputs the serial data to the communication unit 55. The I / F 72 receives a command from the communication unit 55 and transmits a response to the communication unit 55, for example.

[0054] The processor 71 executes programs stored in the ROM 73 or the EEPROM 75 to execute various processes of the secure element 58. The processor 71 executes command processing in response to a command received by the I / F 72, for example.

[0055] A management applet 91 is stored in advance in the ROM 73 (or EEPROM 75), and the processor 71 reads and executes the management applet 91 to manage the installation, deletion, and reinstallation of applets used for various services described below.

[0056] In the following description, the process realized by the processor 71 executing the administration applet 91 will be described as a process mainly performed by the administration applet 91.

[0057] In other words, the process realized by the processor 71 executing the administration applet 91 will be described as the process executed by the administration applet 91 .

[0058] The ROM 73 is, for example, a non-volatile memory such as a mask ROM, and stores programs for executing various processes of the secure element 58, and data such as a command table.

[0059] The RAM 74 is, for example, a volatile memory such as a static RAM (SRAM), and temporarily stores data used when the secure element 58 performs various processes.

[0060] The EEPROM 75 is, for example, an electrically rewritable non-volatile memory. The EEPROM 75 stores various data used by the secure element 58. The EEPROM 75 stores, for example, applets used for various services (applications, security functions) using the secure element 58. Note that the EEPROM 75 is only an example, and other configurations may be used as long as the memory is electrically rewritable.

[0061] 3, the secure element 58 is described as a SIM (Subscriber Identity Module) card that is detachable from the electronic device 31, but it may be configured as an embedded subscriber identity module (eSIM) in the main body of the electronic device 31, and the basic structure is the same even if it is an eSIM. Furthermore, the secure element 58 may be configured as something other than a SIM. Also, the management applet 91 may be installed and used in the same way as a normal applet.

[0062] <Server configuration example> Next, a configuration example of the server 32 in FIG. 1 will be described with reference to FIG.

[0063] The server 32 is composed of a control unit 101, an input unit 102, an output unit 103, a memory unit 104, a communication unit 105, a drive 106, and a removable storage medium 107, which are connected to each other via a bus 108 and can send and receive data and programs.

[0064] The control unit 101 is composed of a processor and a memory, and controls the overall operation of the server 32 .

[0065] The control unit 101 also includes an applet issuing processing unit 111. When installation of an applet managed in the secure element 58 of the electronic device 31 is requested, the applet issuing processing unit 111 issues the requested applet, supplies it to the electronic device 31, and installs it.

[0066] The input unit 102 is configured with input devices such as a keyboard through which the user inputs operation commands and a microphone through which voice input is performed, and supplies various input signals to the control unit 101 .

[0067] The output unit 103 is composed of an audio output unit consisting of a speaker, etc., a display unit consisting of an LCD (Liquid Crystal Display) or an organic EL (Organic Electro-Luminescence) or the like, and a light-emitting unit consisting of an LED (Light Emitting Diode) or the like, and is controlled by the control unit 101 to display various search results.

[0068] The storage unit 104 is composed of a hard disk drive (HDD), a solid state drive (SSD), a semiconductor memory, or the like, and is controlled by the control unit 101 to write or read various data including content data and programs.

[0069] The communication unit 105 is controlled by the control unit 101, and transmits and receives various data and programs to and from various devices via a communication network such as a LAN (Local Area Network) via a wired (or wireless (not shown)) connection.

[0070] The drive 106 reads and writes data from and to a removable storage medium 107 such as a magnetic disk (including a flexible disk), an optical disk (including a CD-ROM (Compact Disc-Read Only Memory) and a DVD (Digital Versatile Disc)), a magneto-optical disk (including an MD (Mini Disc)), or a semiconductor memory.

[0071] <Operation of secure elements in electronic devices> Next, the operation of the secure element 58 in the electronic device 31 will be described with reference to the functional block diagrams of FIGS.

[0072] The secure element 58 requests the server 32 to issue an applet based on a trigger supplied from the host program 61 according to the type of applet, and installs the issued applet.

[0073] Here, the trigger information includes location information, time information, information on the time elapsed since the applet was installed, and information input by the user operating the input unit 52, and the like.

[0074] When a specific trigger is supplied, the secure element 58 installs the applet and becomes capable of executing processing corresponding to the type of the applet.

[0075] Furthermore, when the secure element 58 receives another predetermined trigger according to the type of the installed applet, it deletes the installed applet.

[0076] At this time, the secure element 58 does not delete information that is required when reinstalling and using the deleted applet, but leaves it as a log, and deletes the installed applet.

[0077] Furthermore, when the secure element 58 detects a predetermined trigger supplied by the host program 61 according to the type of applet, it requests the server 32 to issue the applet again, and reinstalls the issued applet.

[0078] When the secure element 58 executes a predetermined process using the reinstalled applet, the secure element 58 executes the process using the log information that was left undeleted.

[0079] Through this series of processes, the secure element 58 can install, delete, or reinstall applets registered in the memory area of ​​the secure element 58 depending on the user's actions, etc., thereby enabling the secure element's memory area to be flexibly utilized.

[0080] More specifically, the host program 61 includes a trigger acquisition unit 151 and an internal trigger detection unit 152 .

[0081] The trigger acquisition unit 151 acquires, as a trigger, location information supplied from an external trigger device 131, which is constituted by an ultra wide band (UWB), a global positioning system (GPS), a beacon, or the like.

[0082] In addition, the trigger acquisition unit 151 acquires, as triggers, time information supplied from the internal trigger detection unit 152, information on the elapsed time since a specific applet was installed, and operation information generated when the input unit 52 is operated by a user, and supplies these to the secure element 58.

[0083] The secure element 58 includes an administration applet 91 .

[0084] The management applet 91 is a dedicated applet that manages the installation, deletion, and reinstallation of applets for implementing predetermined processes, and is an applet that is permanently installed in the secure element 58 .

[0085] More specifically, the management applet 91 requests the server 32 to issue an applet according to the type of applet to be installed, and stores a trigger, which is a condition for installation, as the issuance trigger rule 171 .

[0086] When an applet is installed, the management applet 91 stores a deletion trigger rule 172 in which a trigger that is a condition for deleting the installed applet is registered, and when the applet is deleted, the management applet 91 also deletes the deletion trigger rule 172 in which trigger information for deletion is registered.

[0087] Therefore, when the management applet 91 receives a trigger from the trigger acquisition unit 151 of the host program 61, it refers to the issue trigger rule 171 to determine whether or not a corresponding trigger exists.

[0088] Then, if the acquired trigger is a trigger stored in the issuance trigger rule 171 and is a trigger that is a condition for installing a specified applet, the management applet 91 requests the host program 61 to issue the specified applet.

[0089] The host program 61 controls the communication unit 55 to access the server 32 and request the issuance of a specific applet.

[0090] Through this process, the host program 61 obtains the applet issued by the server 32 and supplies it to the administration applet 91 .

[0091] The administration applet 91 obtains an applet issued by the server 32 via the host program 61, and installs it in the secure element 58 as, for example, an applet 181 indicated by a solid line in FIG.

[0092] At this time, the management applet 91 registers in the deletion trigger rule 172 information on a trigger that is a condition for deleting the installed applet 181 .

[0093] In this manner, when a new applet 181 is installed in the secure element 58, the secure element 58 (its processor 71 (Figure 3)) is able to execute the corresponding processing by executing the installed applet 181.

[0094] Furthermore, if the trigger supplied from the trigger acquisition unit 151 of the host program 61 is a trigger registered in the deletion trigger rule 172 and is a trigger that satisfies the condition for deleting a specified applet, the management applet 91 deletes (uninstalls) the installed applet 181, for example, as shown by the dotted line in Figure 6.

[0095] At this time, the management applet 91 deletes the deletion trigger rule 172 in which the trigger that is the condition for deleting the applet 181 is registered, as shown by the dotted line.

[0096] Then, the administration applet 91 notifies the server 32 via the host program 61 of information indicating that the deletion of the applet 181 has been completed.

[0097] Furthermore, the management applet 91 leaves and stores, as a log 173, information required for reinstalling and executing the applet 181 that has already been installed.

[0098] Here, when applet 181 that has been installed is deleted, the type of information to be left as log 173 may be registered in deletion trigger rule 172, for example, in association with a trigger that is a condition for deletion.

[0099] When the management applet 91 reinstalls the applet, it reads out the stored information of the log 173 and transmits it to the server 32 via the host program 61 as necessary, and reinstalls the applet according to the information of the log 173.

[0100] Through the above processing, in the secure element 58, when the trigger information acquired by the trigger acquisition unit 151 in response to the user's actions, including the operation input corresponding to the user's operation, the location information of the movement, the time information, and the elapsed time since the applet was installed, is a trigger that is a condition for installing an applet defined in the issuance trigger rule 171, the applet is installed at the timing when the trigger is detected.

[0101] In addition, when the trigger information acquired by the trigger acquisition unit 151 is a trigger that is a condition for deleting an applet defined in the deletion trigger rule 172, the applet is deleted (uninstalled) at the timing when the trigger is detected.

[0102] As a result, in response to a user action corresponding to a trigger set according to the type of applet 181, the applet 181 is installed in the secure element 58, the installed applet 181 is deleted, or the applet 181 is reinstalled.

[0103] As a result, depending on the type of applet 181, the applet 181 is installed in the secure element 58 at the necessary timing, and at other unnecessary timings, the installed applet 181 is deleted (uninstalled), making it possible to flexibly utilize the limited memory area in the secure element 58.

[0104] In principle, the installation and uninstallation of applets for the secure element 58 is a function that can only be realized by the server 32 .

[0105] That is, in response to a request from the administration applet 91 to the server 32 to install an applet, the server 32 issues an applet, and the issued applet is installed in the secure element 58 by the server 32 .

[0106] Therefore, for example, the host program 61 cannot issue and install or uninstall applets to the secure element 58 .

[0107] Therefore, in the following explanation, we will use the expression that the management applet 91 requests the server 32 to issue an applet, and then the management applet 91 installs the issued applet. However, as described above, in detail, in response to the request for applet installation from the management applet 91, the server 32 issues the applet and installs it in the secure element 58.

[0108] However, in the present disclosure, since the administration applet 91 is provided within the secure element 58, the applet can be uninstalled (deleted) independently.

[0109] As a result, even in an environment where communication with the server 32 is not possible, for example, the management applet 91 can independently uninstall unnecessary applets installed in the secure element 58, making it possible to flexibly utilize the limited memory space in the secure element 58.

[0110] <Applet publishing process> Next, the applet issuing process will be described with reference to the flowchart in FIG.

[0111] In step S11, the trigger acquisition unit 151 of the host program 61 determines whether or not at least any of information that can be recognized as a trigger, such as position information from the external trigger device 131, time information or elapsed time information from the internal trigger detection unit 152, and operation information generated by the user operating the input unit 52, has been detected, and repeats the same process until it is detected.

[0112] If any trigger is detected in step S11, the process proceeds to step S12.

[0113] In step S12, the trigger acquisition unit 151 acquires information about the detected trigger.

[0114] In step S 13 , the trigger acquisition unit 151 supplies the acquired trigger information to the management applet 91 of the secure element 58 .

[0115] In step S 31 , the management applet 91 acquires the trigger information supplied from the trigger acquisition unit 151 .

[0116] In step S32, the management applet 91 refers to the obtained trigger information in the issuance trigger rule 171 to determine whether the trigger is a condition that requests issuance of an applet.

[0117] In step S32, if the acquired trigger information is not a trigger that satisfies the condition for requesting the issuance of an applet, the process ends.

[0118] Also, in step S32, if the acquired trigger information is a trigger that is a condition for requesting the issuance of an applet, the process proceeds to step S33.

[0119] In step S33, the administration applet 91 requests the host program 61 to issue the applet.

[0120] In step S 14 , the host program 61 receives the applet issuance request from the administration applet 91 .

[0121] In step S15, the host program 61 controls the communication unit 55 to request the server 32 to issue an applet.

[0122] In step S 51 , the applet issuing processor 111 executed by the controller 101 of the server 32 controls the communication unit 105 to receive an applet issuing request from the electronic device 31 .

[0123] In step S52, the applet issuing processor 111 controls the communication section 105 to request the electronic device 31 to send a log, which is information to be reused when the applet requested to be issued is used.

[0124] In step S16, the host program 61 receives a request for a log from the server 32 via the communication unit 55.

[0125] In step S 17 , the host program 61 notifies the management applet 91 of the secure element 58 of the log request from the server 32 .

[0126] In step S 34 , the administration applet 91 receives a request for a log from the server 32 via the host program 61 .

[0127] In step S 35 , in response to the log request, the management applet 91 reads out the stored information of the log 173 of the applet that requested issuance, and transmits it to the host program 61 .

[0128] In step S36, the administration applet 91 deletes or holds the requested log information depending on the type of the applet. That is, the administration applet 91 deletes log information that is unlikely to be used continuously in the future and holds logs that are likely to be used continuously in the future depending on the type of the applet.

[0129] On the other hand, in step S 18 , the host program 61 acquires the log sent from the administration applet 91 .

[0130] In step S 19 , the host program 61 controls the communication unit 55 to transmit the log information transmitted from the management applet 91 to the server 32 .

[0131] In step S 53 , the applet issuing processor 111 of the server 32 controls the communication unit 105 to obtain the log transmitted from the administration applet 91 via the host program 61 .

[0132] In steps S54 and S71, the applet issuing processor 111 controls the communication unit 105 to install the applet 181 in the secure element 58 of the electronic device 31, as indicated by the solid line in Fig. 5. At this time, the applet issuing processor 111 installs the applet by using the transmitted log as necessary.

[0133] In steps S55 and S37, the applet publication processor 111 controls the communication unit 105 to register in the deletion trigger rule 172 of the management applet 91 a trigger that is a condition for deleting the installed applet.

[0134] At this time, in the process of step S36, the applet issuing processor 111 registers the types of information to be stored as a log and information to be deleted in the deletion trigger rule 172 in association with the installed applet.

[0135] That is, in the processing of step S36 described above, when a log is requested, the management applet 91 deletes or retains the requested log information according to the type of applet 181, based on the information to be retained as a log and the information to be deleted that are registered in association with the applet in this deletion trigger rule 172.

[0136] By the above process, applet 181 is installed if the trigger associated with the user's action is a trigger that is a condition for installing an applet and is registered in advance in issue trigger rule 171. As a result, the installed applet 181 is read by R / W 33, and predetermined processing can be performed in management device 34 based on the read information.

[0137] Incidentally, the log information provided by the series of steps S52, S16, S17, S34, S35, S18, S19, and S53 in the flowchart of FIG. 7 is processing for the case where the applet was previously installed, so there may be no actual log information in the initial installation.

[0138] <Applet removal process> Next, a deletion process for deleting an applet installed by the applet issuing process of FIG. 7 will be described with reference to a flowchart of FIG.

[0139] In step S111, the trigger acquisition unit 151 of the host program 61 determines whether or not at least any of information that can be recognized as a trigger, such as position information from the external trigger device 131, time information or elapsed time information from the internal trigger detection unit 152, and operation information generated by the user operating the input unit 52, has been detected, and repeats the same process until it is detected.

[0140] If any trigger is detected in step S111, the process proceeds to step S112.

[0141] In step S112, the trigger acquisition unit 151 acquires information about the detected trigger.

[0142] In step S 113 , the trigger acquisition unit 151 supplies the acquired trigger information to the management applet 91 of the secure element 58 .

[0143] In step S 131 , the management applet 91 acquires the trigger information supplied from the trigger acquisition unit 151 .

[0144] In step S132, the management applet 91 refers to the acquired trigger information in the deletion trigger rule 172 to determine whether the trigger is a deletion condition for the applet.

[0145] If it is determined in step S132 that the acquired trigger information is not a trigger that serves as a deletion condition for the applet, the process ends.

[0146] Also, in step S132, if the acquired trigger information is a trigger for which the applet is to be deleted, the process proceeds to step S133.

[0147] In steps S133 and S151, the management applet 91 reads the log and data from the installed applet 181.

[0148] In step S134, the management applet 91 holds the log read from the installed applet 181.

[0149] The log information retained here is information registered in the log 173 as information of a type retained as a log registered in association with the applet 181 in the deletion trigger rule 172 in the above-mentioned issuance process, and information registered as information of a type to be deleted is deleted.

[0150] In steps S 135 and S 152 , the administration applet 91 deletes the applet 181 .

[0151] In step S136, the management applet 91 deletes the deletion trigger rule 172 in which the trigger that is the deletion condition for the deleted applet 181 is registered.

[0152] In step S137, the administration applet 91 notifies the server 32 via the host program 61 that the log has been stored and the applet 181 has been deleted.

[0153] In step S171, the applet issuing processor 111 of the server 32 receives a notification from the management applet 91 of the electronic device 31 indicating that the log has been stored and that the deletion of the applet 181 has been completed.

[0154] By the above process, if a trigger detected due to a user's action is a trigger that serves as a deletion condition for an installed applet, the applet is deleted and a log is stored as necessary.

[0155] In this way, an installed applet is deleted by a trigger detected according to a user's action, so that it is possible for the user to delete unnecessary applets without consciously deleting the applets.

[0156] Furthermore, when the applet is installed again, the log information required for processing is stored, so that when the applet is installed again, processing based on the stored log can be realized.

[0157] As a result, the limited storage area within the secure element 58 can be utilized flexibly.

[0158] Furthermore, applets are installed or deleted through interactions between the management applet 91 provided in the secure element 58 and the server 32, making it possible to manage applets in a secure environment between the secure element 58 and the server 32, thereby improving security in managing applets.

[0159] In the above, we have described an example in which, when an applet is deleted, the server 32 is notified that the deletion of the applet has been completed and the log has been retained. However, in a case in which communication between the electronic device 31 and the server 32 is not established, the notification to the server 32 indicating that the deletion of the applet has been completed and the log has been retained may be omitted, and the notification may be sent when the communication state is restored.

[0160] In this way, even in an environment where communication between the electronic device 31 and the server 32 has not been established, such as on an airplane or where mobile phone signals are difficult to reach, or where the electronic device 31 is standalone, it is possible to delete unnecessary applets in the electronic device 31, and it becomes possible to flexibly utilize the limited memory area in the secure element 58 without being affected by the communication environment with the server 32.

[0161] <If the applet is an electronic ticket> Next, an example in which the applet is an electronic ticket for an event or the like will be described.

[0162] That is, in this case, the server 32 is a server 32A that functions as a ticket issuing system, as shown in FIG.

[0163] Moreover, the electronic device 31 is assumed to be an electronic device 31A owned by a user who purchases an electronic ticket for admission to an event.

[0164] Here, the electronic device 31A includes a host program 61A and a secure element 58A.

[0165] The host program 61A shows a form when the host program 61 functions as a ticket purchasing application (application program), and has the same basic functions as the host program 61.

[0166] The host program 61A also includes a trigger acquiring section 151A and an internal trigger detecting section 152A, which are similar in basic function to the trigger acquiring section 151 and the internal trigger detecting section 152, respectively.

[0167] Furthermore, administration applet 91A shows an applet 181A in a form in which applet 181 functions as an electronic ticket, and its basic functions are the same as those of administration applet 91.

[0168] That is, for example, when the input unit 52 is operated and the internal trigger detection unit 152A detects a trigger such as an operational input requesting the purchase of an electronic ticket, the trigger acquisition unit 151A acquires the detected trigger and supplies it to the management applet 91A.

[0169] The management applet 91A consults the issuance trigger rule 171A with the detected trigger, and determines whether or not the trigger is a condition for requesting the issuance of an electronic ticket.

[0170] In the issuance trigger rule 171A, for example, a trigger that is a condition for requesting the issuance of an applet as an electronic ticket, such as an operational input for requesting the purchase of an electronic ticket, is registered.

[0171] Therefore, when the supplied trigger is a trigger such as an operational input requesting the purchase of an electronic ticket being operated by the input unit 52 and is a trigger registered in the issuance trigger rule 171A, the management applet 91A requests the server 32A to issue an electronic ticket and installs the applet 181A as the electronic ticket shown by the solid line in Figure 9.

[0172] At this time, the management applet 91A registers, as the deletion trigger rule 172A, trigger information of the electronic ticket deletion condition that is the deletion condition for the applet 181A as the electronic ticket.

[0173] The electronic ticket deletion condition is, for example, time information indicating the date and time after the event is held.

[0174] The issuance trigger rule 171A indicates a form when a condition for requesting issuance of an electronic ticket is stored as the issuance trigger rule 171, and has the same basic function as the issuance trigger rule 171. The deletion trigger rule 172A indicates a form when an electronic ticket deletion condition is stored as the deletion trigger rule 172, and has the same basic function as the deletion trigger rule 172.

[0175] When applet 181A as an electronic ticket is installed in secure element 58A, it is read by R / W 33A installed at the gate of the event venue and supplied to management device 34 which manages admission to the event. For example, if it is recognized as a valid electronic ticket, the gate to the event venue is opened and the user possessing electronic device 31A is allowed to enter the event venue.

[0176] In addition, the management applet 91A checks the detected trigger against the deletion trigger rule 172, and if the detected trigger satisfies the electronic ticket deletion condition and is time information indicating a date and time after the above-mentioned event has been held, the management applet 91A deletes the applet 181A as the installed electronic ticket, as shown by the dotted line in Figure 10.

[0177] At this time, the management applet 91A also deletes the deletion trigger rule 172A as the electronic ticket deletion condition, as indicated by the dotted line in FIG.

[0178] Through this series of processes, when a user performs an operation to request the purchase of an electronic ticket for an event venue, this purchase request operation triggers the installation of an applet as the electronic ticket, and further, when time information indicating the date and time after the event is held is detected, the detection of this time information triggers the deletion of the applet as the electronic ticket.

[0179] As a result, it becomes possible to install and delete applets as electronic tickets registered in the memory area of ​​the secure element depending on the user's actions, making it possible to flexibly utilize the memory area of ​​the secure element.

[0180] <Electronic ticket issuing process> Next, the electronic ticket issuing process in which applet 181A is installed as an electronic ticket will be described with reference to the flowchart of FIG.

[0181] In step S211, the trigger acquisition unit 151A of the host program 61A determines whether or not at least any of information that can be recognized as a trigger, such as position information from the external trigger device 131A, time information or elapsed time information from the internal trigger detection unit 152, and operation information performed on the input unit 52, has been detected as a trigger, and repeats the same process until it is supplied.

[0182] If any trigger is detected in step S211, the process proceeds to step S212.

[0183] In step S212, the trigger acquiring unit 151A acquires the detected trigger.

[0184] In step S213, the trigger acquiring unit 151A supplies the acquired trigger to the management applet 91A of the secure element 58A.

[0185] In step S231, the management applet 91A acquires the trigger information supplied from the trigger acquiring unit 151A.

[0186] In step S232, the management applet 91A refers to the obtained trigger information in the issuance trigger rule 171A, and determines whether the trigger is a condition for issuing an applet as an electronic ticket.

[0187] In step S232, if the acquired trigger information is not a trigger that is a condition for issuing an applet as an electronic ticket, the process ends.

[0188] Also, in step S232, if the acquired trigger information is a trigger for issuing an applet as an electronic ticket, the process proceeds to step S233.

[0189] In step S233, the administration applet 91A requests the host program 61A to issue the applet as an electronic ticket.

[0190] In step S214, the host program 61A receives a request for issuing an applet as an electronic ticket from the management applet 91A.

[0191] In step S215, the host program 61A controls the communication unit 55 to request the server 32A to issue an applet as an electronic ticket.

[0192] In step S251, the applet issuance processing unit 111 in the control unit 101 of the server 32A controls the communication unit 105 to obtain a request for issuing an applet as an electronic ticket from the electronic device 31.

[0193] In step S252, the applet issuance processing unit 111 controls the communication unit 105 to request the electronic device 31A to transmit a log, which is information to be reused when the applet serving as the electronic ticket for which issuance is requested, is used.

[0194] Here, the log includes, for example, information on points given each time an electronic ticket is purchased, information on discounts according to the number of purchases, and the like.

[0195] In step S216, the host program 61A receives a request for a log from the server 32 via the communication unit 55.

[0196] In step S217, the host program 61A notifies the management applet 91A of the secure element 58A of the log request from the server 32A.

[0197] In step S234, the administration applet 91A receives a log request from the server 32A via the host program 61A.

[0198] In step S 235 , in response to the log request, the management applet 91 A reads out the stored applet log information as the electronic ticket for which issuance has been requested, and transmits it to the host program 61 .

[0199] In step S236, the management applet 91A holds, for example, information on points and discounts as a log of requests for issuing applets as electronic tickets.

[0200] On the other hand, in step S218, the host program 61A acquires the log sent from the administration applet 91A.

[0201] In step S219, the host program 61A controls the communication unit 55 to transmit the log information transmitted from the management applet 91 to the server 32A.

[0202] In step S253, the applet issuing processor 111 of the server 32A controls the communication unit 105 to obtain the transmitted log.

[0203] In steps S254 and S271, the applet issuing processor 111 controls the communication unit 105 to install the applet 181A as an electronic ticket in the secure element 58A of the electronic device 31A. At this time, the applet issuing processor 111 installs the applet 181A as an electronic ticket by using the transmitted log as necessary.

[0204] In steps S255 and S237, the applet issue processor 111 controls the communication unit 105 to register the applet 181A as the installed electronic ticket, which is a trigger that serves as a deletion condition, in the management applet 91 as the deletion trigger rule 172A.

[0205] With the above processing, if the trigger according to the user's behavior is a trigger for installing an applet as an electronic ticket, the applet as an electronic ticket is installed, and the installed applet as an electronic ticket can realize processing for managing entry to the event venue, for example, by processing with the management device 34 via R / W 33 installed at the gate of the event venue.

[0206] <Electronic ticket deletion process> Next, with reference to the flowchart in FIG. 12, an electronic ticket deletion process for deleting applet 181A as an electronic ticket installed by the electronic ticket issuing process in FIG. 11 will be described.

[0207] In step S311, the trigger acquisition unit 151A of the host program 61A determines whether or not at least any of information that can be recognized as a trigger, such as position information from the external trigger device 131A, time information or elapsed time information from the internal trigger detection unit 152, and operation information performed on the input unit 52, has been detected as a trigger, and repeats the same process until it is supplied.

[0208] If any trigger is detected in step S311, the process proceeds to step S312.

[0209] In step S312, the trigger acquiring unit 151A acquires the detected trigger.

[0210] In step S313, the trigger acquiring unit 151A supplies the acquired trigger to the management applet 91A of the secure element 58A.

[0211] In step S331, the management applet 91A acquires the trigger information supplied from the trigger acquiring unit 151.

[0212] In step S332, the management applet 91A refers to the acquired trigger information in the deletion trigger rule 172A, and determines whether or not the trigger satisfies the deletion condition of the applet 181A as an electronic ticket.

[0213] In step S332, if the acquired trigger information is not a trigger that satisfies the deletion condition for the applet as an electronic ticket, the process ends.

[0214] Also, in step S332, if the acquired trigger information is a trigger that satisfies the deletion condition for the applet as an electronic ticket, the process proceeds to step S333.

[0215] In steps S333 and S351, the management applet 91A reads out the log and data from the applet 181 as the electronic ticket.

[0216] In step S334, the management applet 91A holds the log read by the applet 181 as an electronic ticket.

[0217] In steps S335 and S352, the management applet 91A deletes the applet 181A as an electronic ticket. Here, the applet 181A as an electronic ticket is deleted, but the information remaining as a log registered in the deletion trigger rule 172A is not deleted. Here, the information remaining as a log is, for example, points and discount information that are given according to the number of times an electronic ticket is purchased.

[0218] In step S336, the management applet 91A deletes the deletion trigger rule 172A in which the trigger that is the deletion condition for the applet 181A as the deleted electronic ticket is registered.

[0219] In step S337, the administration applet 91A notifies the server 32A via the host program 61A that the log has been stored and the applet 181A has been deleted.

[0220] In step S371, the applet issue processor 111 of the server 32A receives a notification from the management applet 91A of the electronic device 31A indicating that the log has been stored and that the applet 181A as an electronic ticket has been deleted.

[0221] Through the above processing, if a trigger detected based on user behavior is a trigger that, according to the trigger rule, results in the deletion of an applet as an installed electronic ticket, the applet as an electronic ticket is deleted and, for example, a log of points and discount information associated with purchasing an electronic ticket is maintained.

[0222] As a result, an applet as an installed electronic ticket is deleted by a trigger detected according to a user's action, so that the user can delete an applet as an unnecessary electronic ticket without consciously deleting an applet of an electronic ticket that has already been used.

[0223] Furthermore, when the applet as an electronic ticket is installed (purchased) again, the log information required for, for example, awarding points or discounts is retained, making it possible to award points or discounts based on the retained log.

[0224] As a result, the limited storage area within the secure element 58 can be utilized flexibly.

[0225] <If the applet is an administrative ID> Next, an example in which the applet is an administrative ID used in an administrative agency or the like will be described.

[0226] That is, in this case, the server 32 is a server 32B that functions as an ID issuing system, as shown in FIG.

[0227] Moreover, the electronic device 31 is, for example, electronic device 31B that the user possesses when requesting disclosure of personal information at an administrative agency.

[0228] Here, the electronic device 31B includes a host program 61B and a secure element 58B.

[0229] Here, host program 61B shows a form when host program 61 functions as an administrative ID management application (application program), and has the same basic functions as host program 61.

[0230] Furthermore, the host program 61B includes a trigger acquiring section 151B and an internal trigger detecting section 152B, which are similar in basic function to the trigger acquiring section 151 and the internal trigger detecting section 152, respectively.

[0231] Furthermore, the administration applet 91B shows a form when the applet 181 manages the applet 181B which shows a form when the applet 181 functions as an administrative ID, and has the same basic functions as the administration applet 91.

[0232] That is, for example, when a trigger is detected from the location information of electronic device 31B that a user carrying electronic device 31B is present within a predetermined distance from the location of an administrative agency, trigger acquisition unit 151B acquires the detected trigger and supplies it to management applet 91B.

[0233] The administration applet 91B checks the detected trigger against the issuance trigger rule 171B to determine whether or not the trigger is a condition for requesting the issuance of an administrative ID.

[0234] In the issuance trigger rule 171B, for example, a trigger that is a condition for requesting the issuance of an applet as an administrative ID, such as a trigger that a user carrying the electronic device 31B is present within a predetermined distance from the location of an administrative agency, is registered.

[0235] Therefore, when the supplied trigger is a trigger such as location information indicating that the user possessing the electronic device 31B is within a specified distance from the location of an administrative agency and is a trigger registered in the issuance trigger rule 171B, the management applet 91B requests the server 32B to issue an administrative ID, and installs the applet 181B as the administrative ID shown by the solid line in Figure 13.

[0236] At this time, the administration applet 91B registers, in the deletion trigger rule 172B, information on a trigger that is an administrative ID deletion condition, which is a deletion condition for the applet 181B as an administrative ID.

[0237] The administrative ID deletion condition is, for example, that the time that has elapsed since applet 181B as an administrative ID was installed is longer than a predetermined time.

[0238] Here, issuance trigger rule 171B shows a form when a condition for requesting issuance of an administrative ID is stored as issuance trigger rule 171, and the basic function is the same as that of issuance trigger rule 171. Also, deletion trigger rule 172B shows a form when an administrative ID deletion condition is stored as deletion trigger rule 172, and the basic function is the same as that of deletion trigger rule 172.

[0239] When applet 181B as an administrative ID is installed in secure element 58B, it is read by R / W 33A installed in an administrative agency, and if the administrative agency's management device 34 recognizes it as, for example, a valid administrative ID, personal information can be disclosed to the user who possesses electronic device 31A.

[0240] In addition, when the administrative ID deletion condition is satisfied and the elapsed time since the installation of applet 181B as an administrative ID is detected by the above-mentioned internal trigger detection unit 152B, which indicates that a predetermined time has elapsed, the management applet 91B regards the detection of the elapsed time information as a trigger and deletes the installed applet 181B as an administrative ID, as shown by the dotted line in Figure 14.

[0241] At this time, the administration applet 91B deletes the deletion trigger rule 172B in which the trigger as the administrative ID deletion condition is registered, as indicated by the dotted line in FIG.

[0242] Through this series of processes, when a user approaches an administrative agency, the location information triggers the installation of an applet as an administrative ID, and if elapsed time information is detected indicating that the time that has elapsed since the applet was installed is longer than a predetermined time, the detection of this elapsed time information triggers the deletion of the applet as an administrative ID.

[0243] As a result, it becomes possible to install and delete applets as administrative IDs registered in the memory area of ​​the secure element depending on the user's actions, making it possible to flexibly utilize the memory area of ​​the secure element.

[0244] <Administrative ID issuing process> Next, with reference to the flowchart of FIG. 15, an administrative ID issuing process will be described in the case where applet 181B is installed as an administrative ID for identifying a user in an administrative organization.

[0245] In step S411, the trigger acquisition unit 151B of the host program 61B determines whether or not at least any of information that can be recognized as a trigger, such as position information from the external trigger device 131B, time information or elapsed time information from the internal trigger detection unit 152, and operation information performed on the input unit 52, has been detected, and repeats the same process until a trigger is detected.

[0246] In step S411, if the trigger acquisition unit 151B detects any trigger, the process proceeds to step S412.

[0247] In step S412, the trigger acquiring unit 151B acquires the detected trigger.

[0248] In step S413, the trigger acquisition section 151B supplies the acquired trigger to the management applet 91B of the secure element 58B.

[0249] In step S431, the management applet 91B acquires the trigger information supplied from the trigger acquiring unit 151B.

[0250] In step S432, the administration applet 91B refers the acquired trigger information to the issuance trigger rule 171B and determines whether the trigger is a condition for issuing an administrative ID as an applet.

[0251] In step S432, if the acquired trigger information is not a trigger that is a condition for issuing an applet as an administrative ID, the process ends.

[0252] Also, in step S432, if the acquired trigger information is a trigger that is a condition for issuing an applet as an administrative ID, the process proceeds to step S433.

[0253] In step S433, administration applet 91B requests host program 61B to issue an applet as an administrative ID.

[0254] In step S414, the host program 61B receives a request for issuing an applet as an administrative ID from the administration applet 91B.

[0255] In step S415, host program 61B controls communication unit 55 to request server 32B to issue an applet as an administrative ID.

[0256] In step S451, the applet issuance processing unit 111 in the control unit 101 of the server 32B controls the communication unit 105 to obtain a request for issuance of an applet as an administrative ID from the electronic device 31B.

[0257] In step S452, the applet issuance processing unit 111 controls the communication unit 105 to request the electronic device 31B for a log, which is information to be reused when using the applet serving as the administrative ID for which issuance is being requested.

[0258] Here, the log includes, for example, information on the past issue date and time, as well as the usage history of personal information and the like disclosed based on the administrative ID.

[0259] In step S416, the host program 61B receives, via the communication unit 55, a request for the log from the server 32B.

[0260] In step S417, the host program 61B notifies the management applet 91B of the secure element 58B of the log request from the server 32B.

[0261] In step S434, the administration applet 91B receives a log request from the server 32B via the host program 61B.

[0262] In step S435, in response to the log request, administration applet 91B reads out the stored log information of the applet serving as the administrative ID for which issuance has been requested, and transmits it to host program 61B.

[0263] In step S436, administration applet 91B, as an applet serving as an administrative ID, holds information such as the date and time of issue and the history of use as a log of the request for issue.

[0264] On the other hand, in step S418, the host program 61B acquires the log sent from the management applet 91B.

[0265] In step S419, the host program 61B controls the communication unit 55 to transmit the log information transmitted from the management applet 91B to the server 32B.

[0266] In step S453, the applet issuing processor 111 of the server 32B controls the communication unit 105 to obtain the transmitted log.

[0267] In steps S454 and S471, applet issuance processing unit 111 controls communication unit 105 to install applet 181B as an administrative ID in secure element 58B of electronic device 31B. At this time, applet issuance processing unit 111 installs applet 181B as an administrative ID by using the transmitted log as necessary.

[0268] In steps S455 and S437, the applet issuance processing unit 111 controls the communication unit 105 to register, in the deletion trigger rule 172B in the management applet 91B, information on a trigger that is a condition for deleting the applet 181B that has been installed as an administrative ID.

[0269] With the above processing, if the trigger according to the user's behavior is a trigger when an applet serving as an administrative ID is installed, the applet serving as an administrative ID is installed, and the installed applet serving as an administrative ID presents the administrative ID to a management device 34, for example, via an R / W 33 provided in an administrative agency, thereby making it possible to realize processing such as disclosing personal information when the administrative ID is recognized to be a proper administrative ID.

[0270] <Administrative ID deletion process> Next, with reference to the flowchart of FIG. 16, a deletion process for deleting applet 181B as an administrative ID installed by the administrative ID issuing process of FIG. 15 will be described.

[0271] In step S511, the trigger acquisition unit 151B of the host program 61B determines whether or not at least any of information that can be recognized as a trigger, such as position information from the external trigger device 131B, time information or elapsed time information from the internal trigger detection unit 152B, and operation information performed on the input unit 52, etc., has been detected as a trigger, and repeats the same process until it is supplied.

[0272] If any trigger is detected in step S511, processing proceeds to step S512.

[0273] In step S512, the trigger acquisition unit 151 acquires the detected trigger.

[0274] In step S513, the trigger acquisition unit 151 supplies the acquired trigger to the management applet 91B of the secure element 58B.

[0275] In step S531, the management applet 91B acquires the trigger information supplied from the trigger acquiring unit 151B.

[0276] In step S532, the administration applet 91B refers the acquired trigger information to the deletion trigger rule 172B, and determines whether the trigger is a condition for deleting an applet as an administrative ID.

[0277] In step S532, if the acquired trigger information is not a trigger that serves as a condition for deleting the applet as the administrative ID, the process ends.

[0278] Also, in step S532, if the acquired trigger information is a trigger that is a condition for deleting the applet as the administrative ID, the process proceeds to step S533.

[0279] In steps S533 and S551, the administration applet 91B reads out the log and data from the applet 181B as the administrative ID.

[0280] In step S534, the administration applet 91B holds the log read out by the applet 181 as the administrative ID.

[0281] In steps S535 and S552, the administration applet 91B deletes the applet 181B as the administrative ID.

[0282] In step S536, the administration applet 91B deletes the deletion trigger rule 172B in which the trigger that is the deletion condition for the applet 181B having the deleted administrative ID is registered.

[0283] In step S537, administration applet 91B notifies server 32B via host program 61B that the log has been stored and that deletion of applet 181B as an administrative ID has been completed.

[0284] In step S571, the applet issuing processor 111 of the server 32B receives a notification from the administration applet 91B of the electronic device 31B indicating that the log has been stored and that the applet 181B as an administrative ID has been deleted.

[0285] Through the above processing, if a trigger detected due to user behavior is a trigger that, according to the trigger rules, results in the deletion of an applet serving as an installed administrative ID, the applet serving as an administrative ID is deleted and logs such as the issuance date and time of the administrative ID and information on usage history are retained.

[0286] As a result, an applet that has been installed as an administrative ID is deleted by a trigger that is detected according to the user's actions, so that the user can delete unnecessary applets that serve as administrative IDs without having to consciously delete the applets.

[0287] Furthermore, when the applet as an administrative ID is installed again, information such as the issue date and time and the usage history log is retained, so that when the applet as an administrative ID is installed again, it is possible to smoothly disclose information based on the retained logs.

[0288] As a result, the limited storage area within the secure element 58 can be utilized flexibly.

[0289] <If the applet is a transportation electronic pass> Next, an example in which the applet is an electronic transportation pass used in transportation facilities or the like will be described.

[0290] In this case, it is assumed that there exists a transportation electronic pass A that is valid for transportation facilities in country A, and a transportation electronic pass B that is valid for transportation facilities in country B. The transportation electronic pass A is valid for transportation facilities in country A, and the transportation electronic pass B is valid for transportation facilities in country B. Here, the explanation will be given using the transportation electronic pass A for the transportation facilities in country A as an example.

[0291] That is, in this case, the server 32 is, for example, a server 32C that functions as an A-transport electronic pass issuing system, as shown in FIG.

[0292] Moreover, the electronic device 31 is, for example, an electronic device 31C that a user carries when using it as an electronic transportation pass in transportation facilities.

[0293] Here, the electronic device 31C includes a host program 61C and a secure element 58C.

[0294] Here, the host program 61C shows a form when the host program 61 functions as an electronic transportation pass application (application program), and has the same basic functions as the host program 61.

[0295] The host program 61C also includes a trigger acquiring section 151C and an internal trigger detecting section 152C, which are similar in basic function to the trigger acquiring section 151 and the internal trigger detecting section 152, respectively.

[0296] Furthermore, the management applet 91C shows a form when managing the applet 181C which shows a form when the applet 181 functions as an A-transport electronic pass, and its basic functions are the same as those of the management applet 91.

[0297] That is, for example, when a trigger is detected from the location information of the electronic device 31C that a user carrying the electronic device 31B is in country A, the trigger acquisition unit 151C acquires the detected trigger and supplies it to the management applet 91C.

[0298] The management applet 91C consults the issuance trigger rule 171C with the detected trigger, and judges whether or not the trigger is a condition that requires the issuance of an applet as an A-transport electronic pass.

[0299] In the issuance trigger rule 171C, for example, a trigger that a user who possesses the electronic device 31C is in country A is registered as a trigger that is a condition for requesting the issuance of an applet as an electronic transportation pass A.

[0300] Therefore, when the supplied trigger is a trigger such as location information indicating that the user possessing electronic device 31B is in country A and is a trigger registered in issuance trigger rule 171C, management applet 91C requests server 32C to issue an applet as transportation electronic pass A, and installs applet 181C as transportation electronic pass A shown by a solid line in Figure 17.

[0301] At this time, the management applet 91C registers, in the deletion trigger rule 172C, information on the trigger that is the A-traffic electronic path deletion condition, which is the deletion condition for the applet 181C as the A-traffic electronic path.

[0302] The condition for deleting the A transportation electronic pass is, for example, that the location information is outside A country.

[0303] Here, the issuance trigger rule 171C shows a form when a condition for requesting the issuance of the A-transport electronic pass is stored as the issuance trigger rule 171, and the basic function is the same as that of the issuance trigger rule 171. Also, the deletion trigger rule 172C shows a form when a deletion condition for the A-transport electronic pass is stored as the deletion trigger rule 172, and the basic function is the same as that of the deletion trigger rule 172.

[0304] When the applet 181C as an A-type transportation electronic pass is installed in the secure element 58C, it is read by the R / W 33C installed at the ticket gate of the transportation facility, and if the transportation facility's management device 34 recognizes it as, for example, a valid A-type transportation electronic pass, the user carrying the electronic device 31C is allowed to enter the station premises.

[0305] In addition, when the location information detected by the above-mentioned external trigger device 131A, which satisfies the A transportation electronic path deletion condition, indicates a location outside A, the management applet 91C regards the detection of the location information as a trigger and deletes the applet 181C as the installed A transportation electronic path, as shown by the dotted line in Figure 18.

[0306] At this time, the management applet 91C deletes the deletion trigger rule 172C as the A-traffic electronic path deletion condition, as indicated by the dotted line in FIG.

[0307] Through this series of processes, when the user enters country A, the location information triggers the installation of an applet as the A-transport electronic pass, and when location information indicating that the user is outside country A is detected, the detection of this location information triggers the deletion of the applet as the A-transport electronic pass.

[0308] As a result, it becomes possible to install and delete applets as A-transport electronic passes registered in the memory area of ​​the secure element depending on the user's actions, enabling flexible use of the memory area of ​​the secure element.

[0309] <Transportation electronic pass issuance process> Next, with reference to the flowchart in FIG. 19, an electronic transportation pass issuing process in the case where the applet 181 is an A-type electronic transportation pass will be described as an example of the applet 181.

[0310] In step S611, the trigger acquisition unit 151C of the host program 61C determines whether or not at least any of information that can be recognized as a trigger, such as position information from the external trigger device 131C, time information or elapsed time information from the internal trigger detection unit 152C, and operation information performed on the input unit 52, etc., has been detected as a trigger, and repeats the same process until it is supplied.

[0311] In step S611, if the trigger acquiring unit 151C detects any trigger, the process proceeds to step S612.

[0312] In step S612, the trigger acquiring unit 151C acquires information about the detected trigger.

[0313] In step S613, the trigger acquisition unit 151C supplies the acquired trigger information to the management applet 91C of the secure element 58C.

[0314] In step S631, the management applet 91C acquires the trigger information supplied from the trigger acquiring unit 151C.

[0315] In step S632, the management applet 91C refers to the obtained trigger information in the issuance trigger rule 171C, and determines whether the trigger is a condition for issuing an applet as the A-transport electronic pass.

[0316] In step S632, if the acquired trigger information is not a trigger that is a condition for issuing an applet as the A-transport electronic pass, the process ends.

[0317] Also, in step S632, if the acquired trigger information is a trigger that is a condition for issuing an applet as the A-transport electronic pass, the process proceeds to step S633.

[0318] In step S633, the management applet 91C requests the host program 61C to issue an applet as the A-transport electronic pass.

[0319] In step S614, the host program 61C receives a request for issuing an applet as the A-transport electronic pass from the management applet 91C.

[0320] In step S615, the host program 61C controls the communication unit 55 to request the server 32C to issue an applet as the A transportation electronic pass.

[0321] In step S651, the applet issuance processing unit 111 in the control unit 101 of the server 32C controls the communication unit 105 to obtain a request for issuance of an applet as the A-transport electronic pass from the electronic device 31C.

[0322] In step S652, the applet issuance processing unit 111 controls the communication unit 105 to request the electronic device 31C to transmit a log, which is information to be reused when the applet serving as the A-transport electronic pass for which issuance is requested, to the electronic device 31C.

[0323] Here, the log includes, for example, information on the charge amount that can be used for the A-transport electronic pass, commuter passes, and usage history.

[0324] In step S616, the host program 61C receives via the communication unit 55 a request for a log from the server 32C.

[0325] In step S617, the host program 61C notifies the management applet 91C of the secure element 58C of the log request from the server 32C.

[0326] In step S634, the administration applet 91C receives a request for a log from the server 32C via the host program 61C.

[0327] In step S635, in response to the log request, the management applet 91C reads out the stored log information of the applet that requested the issuance of the A-transport electronic pass, and transmits it to the host program 61C.

[0328] In step S636, the management applet 91C, as an applet for the A-transport electronic pass, retains a log of requests for issuance, such as the charge amount and commuter pass that can be used for the A-transport electronic pass, and information on the usage history.

[0329] On the other hand, in step S618, the host program 61C acquires the log sent from the management applet 91C.

[0330] In step S619, the host program 61C controls the communication unit 55 to transmit the log information transmitted from the management applet 91C to the server 32C.

[0331] In step S653, the applet issuing processor 111 of the server 32C controls the communication unit 105 to obtain the transmitted log.

[0332] In steps S654 and S671, the applet issuance processing unit 111 controls the communication unit 105 to install the applet 181C as the A-transport electronic pass in the secure element 58 of the electronic device 31C.

[0333] In steps S655 and S637, the applet issuing processor 111 controls the communication unit 105 to register trigger information, which is a deletion condition, for the applet 181C installed as the A-transport electronic pass in the deletion trigger rule 172C in the management applet 91C.

[0334] With the above processing, if the trigger according to the user's behavior is a trigger when an applet as the A-type transportation electronic pass is installed, the applet as the A-type transportation electronic pass is installed, and the installed applet as the A-type transportation electronic pass can, for example, realize processing to manage the opening and closing of a ticket gate by processing with a management device 34 via an R / W 33 provided at the transportation system ticket gate.

[0335] In the above, the process of issuing an applet for the A-transport electronic pass has been explained. However, in the case of the B-transport electronic pass, when the location information is within B country, the applet is also installed in the same way.

[0336] <Transportation Electronic Pass Deletion Processing> Next, with reference to the flowchart of FIG. 20, a description will be given of an electronic transportation pass deletion process for deleting the applet as the A-transport electronic pass installed by the issuance process of the applet as the A-transport electronic pass in FIG.

[0337] In step S711, the trigger acquisition unit 151C of the host program 61C determines whether or not at least any of information that can be recognized as a trigger, such as position information from the external trigger device 131C, time information or elapsed time information from the internal trigger detection unit 152C, and operation information performed on the input unit 52, etc., has been detected as a trigger, and repeats the same process until it is supplied.

[0338] If any trigger is detected in step S711, processing proceeds to step S712.

[0339] In step S712, the trigger acquiring unit 151C acquires the detected trigger.

[0340] In step S713, the trigger acquisition unit 151C supplies the acquired trigger to the management applet 91C of the secure element 58C.

[0341] In step S731, the management applet 91C acquires the trigger information supplied from the trigger acquiring unit 151C.

[0342] In step S732, the management applet 91C refers to the acquired trigger information in the deletion trigger rule 172C and determines whether the information is a trigger for deleting the applet as the A-transport electronic pass.

[0343] Here, for example, a trigger that the detected location information is not within country A is regarded as a trigger that serves as a deletion condition for the applet as transportation electronic pass A.

[0344] In step S732, if the acquired trigger information is not a trigger that serves as a deletion condition for the applet as the A-transport electronic pass, the process ends.

[0345] Also, in step S732, if the acquired trigger information is a trigger that is a deletion condition for the applet as the A-transport electronic pass, the process proceeds to step S733.

[0346] In steps S733 and S751, the management applet 91C reads out the log and data from the applet 181C as the A-transport electronic path.

[0347] In step S734, the management applet 91C holds the log read out from the applet 181C as the A-transport electronic path.

[0348] In steps S735 and S752, the management applet 91C deletes the applet 181C as the A traffic electronic path.

[0349] In step S736, the management applet 91C deletes the deletion trigger rule 172C in which the trigger that is the deletion condition for the applet 181C serving as the deleted A-transport electronic pass is registered.

[0350] In step S737, the management applet 91C notifies the server 32C via the host program 61C that the log has been stored and the applet 181C has been deleted as the A-transport electronic path.

[0351] In step S771, the applet issuing processor 111 of the server 32C receives a notification from the management applet 91C of the electronic device 31C indicating that the log has been stored and that the applet 181C as the A-transport electronic pass has been deleted.

[0352] Through the above processing, if a trigger detected due to user behavior is a trigger that, according to the deletion trigger rules, results in the deletion of the installed applet as the A-transport electronic pass, the applet as the A-transport electronic pass is deleted and logs such as the charge amount and commuter pass that can be used as the A-transport electronic pass, and information on usage history are retained.

[0353] As a result, the installed applet as the A-transport electronic pass is deleted by a trigger detected according to the user's behavior, so that it is possible to delete unnecessary applets as the A-transport electronic pass without the user having to consciously delete the A-transport electronic pass applet when he or she leaves country A.

[0354] Furthermore, when the applet as the A transportation electronic pass is installed again, for example, information such as the charge amount and commuter pass available for the A transportation electronic pass, and the log of usage history is retained, so that when the applet as the A transportation electronic pass is installed again, it becomes possible to use the A transportation electronic pass smoothly based on the retained log.

[0355] As a result, the limited storage area within the secure element 58 can be utilized flexibly.

[0356] In addition, B Transportation Electronic Passes will also be deleted in the same way.

[0357] Therefore, if the A-transport electronic pass is installed when entering country A, and then the user travels from country A to country B, the applet as the A-transport electronic pass will be deleted when the user leaves country A by traveling into country B, and the B-transport electronic pass will be installed because the user is in country B.

[0358] Then, when returning from country B to country A, the applet as the B transport electronic pass will be deleted when leaving country B by moving into country A, and because you are still in country A, the A transport electronic pass will be installed again.

[0359] <<2. Modifications>> The above describes processing realized by electronic device 31 equipped with a secure element 58, but the processing may also be realized by a wearable device equipped with a secure element and an electronic device capable of communicating with the wearable device.

[0360] 21 and 22 show an example of the configuration of a wearable device system realized by a wearable device having a secure element and an electronic device capable of communicating with the wearable device.

[0361] A wearable device system 200 in FIGS. 21 and 22 is configured with an electronic device 201 and a wearable device 202, which are capable of communicating with each other via short-range communication such as Bluetooth (registered trademark).

[0362] The electronic device 201 is, for example, a personal computer or a smartphone, and includes a trigger acquisition unit 241 and an internal trigger detection unit 242.

[0363] Incidentally, the trigger acquiring section 241 and the internal trigger detecting section 242 correspond to the trigger acquiring section 151 and the internal trigger detecting section 152 in FIG. 5 and FIG. 6, respectively, and therefore description thereof will be omitted.

[0364] The wearable device 202 is, for example, a smart watch or a wristband, and is worn by a user. The wearable device 202 may be in other forms, such as a ring-type or glove-type device, as long as it can be worn by a user. Furthermore, the wearable device 202 may be a device in which an electronic circuit is formed in fabric and which generates power by sweat, body heat, or human body movement. In this case, the wearable device 202 may be configured as a type of device that is made of wearable clothing, such as a shirt or jacket.

[0365] The wearable device 202 includes a management applet 261 and an applet 281. The management applet 261 stores an issue trigger rule 271 and a deletion trigger rule 272.

[0366] Incidentally, the administration applet 261 and the applet 281 correspond to the administration applet 91 and the applet 81 in FIG. 5 and FIG. 6, respectively, and therefore a description thereof will be omitted.

[0367] That is, as shown in FIG. 21, when the trigger acquisition unit 241 acquires a trigger, the trigger is supplied to the management applet 261 of the wearable device 202.

[0368] The management applet 261 checks the supplied trigger against the issuance trigger rule 271, determines whether the supplied trigger is a trigger that is a condition for installing a specified applet 281, and if the trigger is a trigger that is a condition for installing the specified applet 281, requests the server 32 to issue the applet 281.

[0369] The server 32 issues the applet 281 in response to a request from the wearable device 202, and transmits the applet 281 to the wearable device 202 via the electronic device 201 for installation.

[0370] This allows the applet 281 to be read by holding the wearable device 202 over the R / W 33, making it possible to execute a specified process.

[0371] Also, as shown in FIG. 22, the management applet 261 checks the supplied trigger against the deletion trigger rule 272 to determine whether the supplied trigger is a trigger that satisfies the deletion condition for a specified applet 281, and if the trigger is a trigger that satisfies the deletion condition for the specified applet 281, the applet is deleted as shown by the dotted line in FIG. 22.

[0372] That is, in the wearable device system 200 as well, it becomes possible to install or delete applets in response to triggers detected according to user actions, making it possible to flexibly use the storage area of ​​the secure element.

[0373] In addition, in the wearable device system 200 of Figures 21 and 22, an example has been described in which the trigger acquisition unit 241 is provided in the electronic device 201, but it may be provided in a configuration other than the electronic device 201, for example, it may be provided in the wearable device 202.

[0374] <<3. Example of execution by software>> 23 shows an example of the configuration of a general-purpose computer. This personal computer has a built-in CPU (Central Processing Unit) 1001. An input / output interface 1005 is connected to the CPU 1001 via a bus 1004. A ROM (Read Only Memory) 1002 and a RAM (Random Access Memory) 1003 are connected to the bus 1004.

[0375] An input unit 1006 consisting of input devices such as a keyboard and a mouse through which a user inputs operation commands, an output unit 1007 for outputting a processing operation screen and an image of the processing result to a display device, a storage unit 1008 consisting of a hard disk drive for storing programs and various data, and a communication unit 1009 consisting of a LAN (Local Area Network) adapter and the like for executing communication processing via a network such as the Internet are connected to the input / output interface 1005. Also connected is a drive 1010 for reading and writing data from and to a removable storage medium 1011 such as a magnetic disk (including a flexible disk), an optical disk (including a CD-ROM (Compact Disc-Read Only Memory) and a DVD (Digital Versatile Disc)), a magneto-optical disk (including an MD (Mini Disc)), or a semiconductor memory.

[0376] The CPU 1001 executes various processes according to a program stored in a ROM 1002 or a program read from a removable storage medium 1011 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory and installed in a storage unit 1008, and loaded from the storage unit 1008 to a RAM 1003. The RAM 1003 also stores data and the like necessary for the CPU 1001 to execute various processes, as appropriate.

[0377] In a computer configured as described above, the CPU 1001 loads, for example, a program stored in the memory unit 1008 into the RAM 1003 via the input / output interface 1005 and the bus 1004, and executes the program, thereby performing the series of processes described above.

[0378] The program executed by the computer (CPU 1001) can be provided by being recorded on a removable storage medium 1011 such as a package medium, for example. The program can also be provided via a wired or wireless transmission medium such as a local area network, the Internet, or digital satellite broadcasting.

[0379] In the computer, the program can be installed in the storage unit 1008 via the input / output interface 1005 by mounting the removable storage medium 1011 in the drive 1010. The program can also be received by the communication unit 1009 via a wired or wireless transmission medium and installed in the storage unit 1008. Alternatively, the program can be pre-installed in the ROM 1002 or the storage unit 1008.

[0380] In addition, the program executed by the computer may be a program in which processing is performed chronologically in the order described in this specification, or it may be a program in which processing is performed in parallel or at the required timing, such as when called.

[0381] 23. Incidentally, the CPU 1001 in FIG. 23 realizes the functions of the processor 71 in FIG.

[0382] In this specification, a system refers to a collection of multiple components (devices, modules (parts), etc.), regardless of whether all the components are in the same case. Therefore, multiple devices housed in separate cases and connected via a network, and a single device in which multiple modules are housed in a single case, are both systems.

[0383] The embodiments of the present disclosure are not limited to the above-described embodiments, and various modifications are possible without departing from the gist of the present disclosure.

[0384] For example, the present disclosure can take the form of cloud computing in which a single function is shared and processed collaboratively by multiple devices via a network.

[0385] Furthermore, each step described in the above flow chart can be executed by one device, or can be shared and executed by a plurality of devices.

[0386] Furthermore, when a single step includes multiple processes, the multiple processes included in the single step can be executed by a single device, or can be shared and executed by multiple devices.

[0387] The present disclosure can also be configured as follows.

[0388] <1> A trigger acquisition unit that acquires a trigger; a management unit that manages applets in the secure element based on the trigger; An information processing device comprising: <2> The trigger includes location information, time information, elapsed time information, and operation information. <1> The information processing device described in <3> The management unit installs an applet in the secure element based on the trigger. <1> or <2> The information processing device described in <4> When the management unit installs an applet in the secure element, the management unit registers a trigger that is a deletion condition for the installed applet as a deletion trigger rule. <3> The information processing device described in <5> The management unit deletes the installed applet when the trigger is a trigger registered as the deletion trigger rule. <4> The information processing device described in <6> The applets are e-tickets, government IDs, and transport e-passes. <5> The information processing device described in <7> When the applet is the electronic ticket, a trigger indicating that a predetermined date and time has come after the electronic ticket has been used is registered in the deletion trigger rule as a trigger that becomes a deletion condition; When the trigger acquisition unit acquires, as the trigger, time information indicating that the predetermined date and time has arrived, the management unit regards the trigger as a trigger registered as the deletion trigger rule, and deletes the applet serving as the installed electronic ticket. <6> The information processing device described in <8> When the applet is an administrative ID, the deletion trigger rule is a trigger that a deletion condition is that a predetermined time has elapsed since the applet serving as the administrative ID was installed, When the trigger acquisition unit acquires the trigger that is an elapsed time indicating that a predetermined time has elapsed since the applet serving as the administrative ID was installed, the management unit considers the trigger to be a trigger registered as the deletion trigger rule, and deletes the installed applet serving as the administrative ID. <6> The information processing device described in <9> When the applet is a transportation electronic pass for a specific country, the deletion trigger rule is that the current location is not within the specific country, When the trigger acquisition unit acquires the trigger consisting of location information indicating that the current location is not within the specified country, the management unit considers the trigger to be a trigger registered as the deletion trigger rule, and deletes the applet serving as the installed electronic transportation pass. <6> The information processing device described in <10> The management unit manages a log of the installed applet, and when deleting the installed applet, deletes a part of the log and deletes it together with the installed applet. <5> The information processing device described in <11> When the installed applet is deleted, the type of information of the log other than the part that is not deleted is registered in association with the applet as information in the deletion trigger rule. <10> The information processing device described in <12> When the management unit deletes the installed applet and then installs the same applet again, the reinstalled applet uses the log. <11> The information processing device described in <13> The log includes information on the charge amount, points, discount information, and usage history generated by executing the applet. <11> The information processing device described in <14> The management unit stores a trigger that is a condition for installing an applet in the secure element as an issuance trigger rule, and installs the applet when the trigger is a trigger registered as the issuance trigger rule. <3> The information processing device described in <15> Get the trigger, Manage applets in the secure element based on the trigger. An information processing method comprising the steps of: <16> A trigger acquisition unit that acquires a trigger; a management unit that manages applets in the secure element based on the trigger; A program that makes a computer function as a <17> An information processing system including an information processing device and a wearable device that performs proximity communication with the information processing device, The information processing device includes a trigger acquisition unit that acquires a trigger, The wearable device includes a management unit that manages applets in a secure element based on the trigger. Information processing system. <18> the information processing device includes a trigger acquisition unit that acquires a trigger, The wearable device includes a management unit that manages applets in a secure element based on the trigger. <17> An information processing system according to the present invention. <19> The wearable device, A trigger acquisition unit that acquires a trigger; a management unit that manages applets in the secure element based on the trigger. <17> An information processing system according to the present invention. <20> The wearable device is a smart watch or a wristband. <17> An information processing system according to the present invention. [Explanation of symbols]

[0389] 11 information processing system, 31, 31-1 to 31-n, 31A to 31C electronic device, 32, 32A to 32C server, 33, 33-1 to 33-n, 33A to 33C R / W, 34, 34-1 to 34-n management device, 51 control unit, 52 input unit, 53 output unit, 54 storage unit, 55 communication unit, 58 secure element, 61 host program, 71 processor, 73 ROM, 74 RAM, 75, EEPROM, 91 management applet, 101 control unit, 111 applet issuance processing unit, 131, 131A to 131C external trigger device, 151, 151A to 151C trigger acquisition unit, 152, 152A to 152C internal trigger detection unit, 171, 171A to 171C trigger rules, 172, 172A to 172C logs, 181, 181A to 181C applets, 231 host program, 241 trigger acquisition unit, 242 internal trigger detection unit, 271 trigger rules, 272 logs, 281 applets

Claims

1. A trigger acquisition unit that acquires a trigger; a management unit that manages applets in the secure element based on the trigger, The management unit Installing an applet in the secure element based on the trigger; When installing an applet in the secure element, a trigger that is a deletion condition for the installed applet is registered as a deletion trigger rule; If the trigger is a trigger registered as the deletion trigger rule, deleting the installed applet; A log of the installed applet is managed, and when the installed applet is deleted, a part of the log is deleted together with the installed applet, and the type of information of the log other than the part that is not deleted is registered as information in the deletion trigger rule in association with the applet. Information processing device.

2. The trigger includes location information, time information, elapsed time information, and operation information. The information processing device according to claim 1 .

3. The applets are e-tickets, government IDs, and transport e-passes. The information processing device according to claim 1 .

4. When the applet is the electronic ticket, a trigger indicating that a predetermined date and time has come after the electronic ticket has been used is registered in the deletion trigger rule as a trigger that becomes a deletion condition; When the trigger acquisition unit acquires, as the trigger, time information indicating that the predetermined date and time has arrived, the management unit regards the trigger as a trigger registered as the deletion trigger rule, and deletes the applet serving as the installed electronic ticket. The information processing device according to claim 3 .

5. When the applet is an administrative ID, the deletion trigger rule is a trigger that a deletion condition is that a predetermined time has elapsed since the applet serving as the administrative ID was installed; When the trigger acquisition unit acquires the trigger that is an elapsed time indicating that a predetermined time has elapsed since the applet serving as the administrative ID was installed, the management unit considers the trigger to be a trigger registered as the deletion trigger rule, and deletes the installed applet serving as the administrative ID. The information processing device according to claim 3 .

6. When the applet is a transportation electronic pass for a specific country, the deletion trigger rule is that the current location is not within the specific country, When the trigger acquisition unit acquires the trigger consisting of location information indicating that the current location is not within the specified country, the management unit considers the trigger to be a trigger registered as the deletion trigger rule, and deletes the applet serving as the installed electronic transportation pass. The information processing device according to claim 3 .

7. When the management unit deletes the installed applet and then installs the same applet again, the reinstalled applet uses the log. The information processing device according to claim 1 .

8. The log includes information on the charge amount, points, discount information, and usage history generated by executing the applet. The information processing device according to claim 1 .

9. The management unit stores a trigger that is a condition for installing an applet in the secure element as an issuance trigger rule, and installs the applet when the trigger is a trigger registered as the issuance trigger rule. The information processing device according to claim 1 .

10. acquiring the trigger; performing a management process for managing applets in the secure element based on the trigger; Including, The management process includes: Installing an applet in the secure element based on the trigger; When installing an applet in the secure element, a trigger that is a deletion condition for the installed applet is registered as a deletion trigger rule; If the trigger is a trigger registered as the deletion trigger rule, deleting the installed applet; A log of the installed applet is managed, and when the installed applet is deleted, a part of the log is deleted together with the installed applet, and the type of information of the log other than the part that is not deleted is registered as information in the deletion trigger rule in association with the applet. Information processing methods.

11. A trigger acquisition unit that acquires a trigger; causing a computer to function as a management unit that manages applets in a secure element based on the trigger; The management unit Installing an applet in the secure element based on the trigger; When installing an applet in the secure element, a trigger that is a deletion condition for the installed applet is registered as a deletion trigger rule; If the trigger is a trigger registered as the deletion trigger rule, deleting the installed applet; A log of the installed applet is managed, and when the installed applet is deleted, a part of the log is deleted together with the installed applet, and the type of information of the log other than the part that is not deleted is registered as information in the deletion trigger rule in association with the applet. program.

12. An information processing system including an information processing device and a wearable device that performs proximity communication with the information processing device, A trigger acquisition unit that acquires a trigger; a management unit that manages applets in the secure element based on the trigger, The management unit Installing an applet in the secure element based on the trigger; When installing an applet in the secure element, a trigger that is a deletion condition for the installed applet is registered as a deletion trigger rule; If the trigger is a trigger registered as the deletion trigger rule, deleting the installed applet; A log of the installed applet is managed, and when the installed applet is deleted, a part of the log is deleted together with the installed applet, and the type of information of the log other than the part that is not deleted is registered as information in the deletion trigger rule in association with the applet. Information processing system.

13. the information processing device includes a trigger acquisition unit that acquires a trigger, The wearable device includes a management unit that manages applets in a secure element based on the trigger. The information processing system according to claim 12.

14. The wearable device, A trigger acquisition unit that acquires a trigger; a management unit that manages applets in the secure element based on the trigger. The information processing system according to claim 12.

15. The wearable device is a smart watch or a wristband. The information processing system according to claim 12.

Images