WO2014084603A1

WO2014084603A1 - Method for managing se applet in connection with application deletion, and mobile device and service management server using same

Info

Publication number: WO2014084603A1
Application number: PCT/KR2013/010855
Authority: WO
Inventors: 최테리
Original assignee: 에스케이씨앤씨 주식회사
Priority date: 2012-11-28
Filing date: 2013-11-27
Publication date: 2014-06-05
Also published as: KR101448085B1; KR20140068440A

Abstract

Provided are a method for managing an SE applet in connection with an application deletion, and a mobile device and a service management server using same. The method for managing an SE applet according to one embodiment of the present invention automatically deletes, from the SE, an applet connected to the application installed in a memory of a mobile device when the application is deleted. Accordingly, an unnecessary applet can be removed from the SE, and therefore, in-advance prevention against unintended payments made by the applet and collisions during the process of issuing another applet can be achieved.

Description

SE Applet Management Method Linked to Application Deletion and Mobile Device and Service Management Server

The present invention relates to an applet management method, and more particularly, to a method for managing applets issued to a secure element (SE) and a mobile device and a service management server to which the same is applied.

In order to perform mobile commerce with a mobile device such as a smartphone, the WA (Wallet Application) must be installed in the memory of the mobile device, and the applet corresponding to the mobile payment card is the SE (Secure Element) of the mobile device. Must be issued at

On the other hand, if the WA that is already installed is not used or needed, the user can delete it from memory. However, deleting a WA does not remove the associated applet from the SE.

Most users are unaware that an applet associated with it other than WA has been issued to SE. And even if the user is aware of this, if he deletes WA, he expects the applet to be deleted from SE, but it is not.

The remaining applets issued to the SE may cause problems in the future. For example, if an applet is left unintentionally and the payment is made or another applet is issued, it may cause a conflict.

The present invention has been made to solve the above problems, an object of the present invention, SE applet management method for automatically deleting or managing the applet associated with it when the application installed in the memory of the mobile device is deleted and The present invention provides a mobile device and a service management server.

SE applet management method according to an embodiment of the present invention for achieving the above object, determining whether to delete the application installed in the memory of the mobile device; And in response to determining that the application has been deleted, requesting the service management server to manage the applet issued to the SE of the mobile device and linked to the application.

The requesting step transmits the ID of the application and the information of the mobile device to the service management server, and requests management of an applet associated with the application, and the service management server is connected with the information of the mobile device. The applet associated with the application may be identified using the ID of the application.

In addition, the mobile device may not grasp the applet associated with the application.

The management of the applet may delete the applet or disable the applet.

The determining step may be determined by a management program that holds an ID list including the ID of the application, and the management program is in a state of holding the ID list before the application is installed in the memory. It may be installed in the memory.

The ID list held by the management program may be updateable by the service management server.

In addition, the update may be performed when another application is developed and distributed or when the other application is installed in a memory of the mobile device and an applet linked to the other application is issued to the SE.

On the other hand, according to another embodiment of the present invention, a mobile device includes a communication unit connected to communicate with the service management server; A memory in which an application is installed; And a processor for determining whether to delete the application installed in the memory and requesting the service management server to manage the applet issued to the SE and linked to the application through the communication unit if the application is deleted. It includes.

On the other hand, SE applet management method according to another embodiment of the present invention, receiving from the mobile device a management request for an applet associated with an application deleted after being installed in the memory of the mobile device; Identifying an applet associated with the deleted application; And managing the applet identified through the identifying step in the SE of the mobile device.

The SE applet management method according to another embodiment of the present invention may further include determining whether the applet identified in the identifying step is linked to another application, and wherein the managing step includes: It may be executed when it is determined that the applet is not associated with the other application.

In addition, the identifying step may identify the applet associated with the application by using the information of the mobile device included in the management request and the ID of the application.

In addition, the managing may delete the applet or stop using the applet.

On the other hand, the service management server according to another embodiment of the present invention, a communication interface connected to communicate with the mobile device; A storage unit configured to store a DB in which the mobile device, an application installed on the mobile device, and applet information associated with the application are built; And an applet associated with the application deleted from the DB stored in the storage unit when a management request for an applet associated with an application deleted after being installed in the memory of the mobile device is received from the mobile device through the communication interface. And a processor for managing the identified applets in the SE of the mobile device.

As described above, according to embodiments of the present invention, when an application installed in a memory of a mobile device is deleted, an applet associated with the same may be automatically deleted from the SE. As a result, it is possible to remove applets that are no longer needed from the SE, thereby preventing collisions in the process of issuing payments and other applets by unintended applets.

In addition, since it does not have unnecessary applets, it is possible to prevent the occurrence of security problems in advance, and there is an advantage that the storage space of the SE can be efficiently used.

1 is a diagram showing an SE applet management system to which the present invention is applicable;

2 is a view provided to explain an SE applet automatic deletion method linked to WA deletion according to an embodiment of the present invention;

3 is a diagram illustrating a WA-ID list held by the SE manager;

4 is a diagram illustrating an AID DB held by a TSM;

5 is a flowchart provided to explain an SE applet automatic deletion method linked to WA deletion according to another embodiment of the present invention;

6 is a detailed block diagram of the mobile device shown in FIG. 1, and

FIG. 7 is a detailed block diagram of the TSM shown in FIG. 1.

Hereinafter, with reference to the drawings will be described the present invention in more detail.

1 is a diagram illustrating a secure element (SE) applet management system to which the present invention is applicable. The SE applet management system to which the present invention is applicable is a system for managing applets 145-1, 145-2,..., 145-n issued to the SE 140 of the mobile device 100. .

Specifically, under the SE applet management system environment shown in FIG. 1, WA (Wallet Applications) 111-1, 111-2,..., 111-m installed in the memory 110 of the mobile device 100. If one of them is deleted, the applet associated with the deleted WA among the applets 145-1, 145-2, ..., 145-n issued to the SE 140 is automatically deleted.

The Trusted Service Manager (TSM) 200 issues applets 145-1, 145-2, ..., 145-n to the SE 140 of the mobile device 100, and deletes the issued applets. Service management server. Applets issued / deleted by the TSM 200 may include mobile payment cards (credit cards, prepaid cards) as well as mobile coupons or mobile membership cards.

Hereinafter, the SE applet automatic deletion process linked to the WA deletion in the mobile device 100 by the SE applet management system shown in FIG. 1 will be described in detail with reference to FIG. 2. FIG. 2 is a diagram provided to explain an SE applet automatic deletion method linked to WA deletion according to an embodiment of the present invention.

As shown in FIG. 2, the SE manager 113 installed in the memory 110 of the mobile device 100 may include WAs 111-1, 111-2,..., 111-m installed in the memory 110. Check periodically whether there is a deleted WA (S310).

The SE manager 113 is installed and operated in the OS porting process. That is, the SE manager 113 is installed in the memory 110 before the WAs 111-1, 111-2, ..., 111-m. For step S310, the SE manager 113 is installed with a list of WA-IDs (Wallet Application-IDs) which are IDs of WAs to be checked for deletion.

That is, the SE manager 113 does not check whether or not to delete all WAs installed in the memory 150, but deletes only the WAs listed in the WA-ID list and installed in the memory 150. Check it.

3 is a diagram illustrating a WA-ID list held by the SE manager 113. In FIG. 3, WAs having WA-IDs of “W1” or “W2” which are marked as installed in the memory 110 among the WA-IDs W1, W2, and W3 listed in the WA-ID list are checked. It is a target.

That is, WA having "W4" not listed in the WA-ID list of FIG. 3 as the WA-ID, or WA having "W3" marked as not installed in the memory 110 as the WA-ID are not to be inspected. .

The SE manager 113 determines that the WA is deleted from the memory 110 by the user when the WA having the WA-ID indicated as installed in the WA-ID list does not exist in the memory 110.

On the other hand, the inspection cycle in step S310 can be flexibly operated according to needs and circumstances.

If the deleted WA is found in the memory 110 (S320), the SE manager 113 requests the TSM 200 to delete the applet (S330). The applet deletion request transmitted from the SE manager 113 to the TSM 200 in step S330 includes the Mobile Station Integrated System Digital Number (MSISDN) of the mobile device 100 and the WA-ID of the deleted WA.

The applet deletion request in step S330 is a deletion request for the applet associated with the deleted WA.

Not only the SE manager 113 but also any application installed in the memory 110 of the mobile device 100 may not grasp the applet associated with the WA and may not delete it.

It is possible to identify and delete the applet associated with the WA only by the TSM 200. Therefore, the SE manager 113 requests the TSM 200 to delete the applet through step S330.

On the other hand, an AID DB (Applet ID DataBase) 235 is built in the storage unit 230 of the TSM 200. 4 illustrates an AID DB 235 held by the TSM 200. As shown in FIG. 4, the AID DB 235 is a DB in which WA-IDs of WAs installed in the mobile device 100 are stored for each MSISDN, and an AID of an applet issued in association with WAs is stored for each WA. .

The TSM 200, which has been requested to delete the applet from the SE manager 113 of the mobile device 100 through step S330 of FIG. 2, refers to the MSISDN and the WA-ID included in the applet deletion request, and AID of the applet to be deleted. It catches from DB 235 (S340).

For example, the AID DB 235 is shown in FIG. 4, and the MSISDN included in the applet deletion request received from the SE manager 113 of the mobile device 100 through step S330 of FIG. M1 "and the WA-ID is" W1 ", the TSM 200 determines the AID of the applet to be deleted as" A1 ".

Thus, the TSM 200 deletes the applet having the AID identified through the step S340 from the SE 140 of the mobile device 100 (S350). Specifically, in step S350, when the TSM 200 requests the deletion of the applet while transmitting the AID to the OTA proxy 115, the SE 140 receives the applet having the AID received by the OTA proxy 115. Is deleted and the result is returned to the TSM 200.

The OTA proxy 115 is an application installed in the memory 110 of the mobile device 100 and has an access right to the SE 140, and is an agent program for relaying the TSM 200 and the SE 140.

Thereafter, the TSM 200 notifies the SE manager 113 that the deletion of the applet requested to be deleted in step S330 is completed (S360).

There is no restriction on the number of applets that are deleted through the above embodiment. That is, when the number of applets associated with the deleted WA is two or more, two or more applets may be deleted.

For example, the AID DB 235 is shown in FIG. 4, and the MSISDN included in the applet deletion request received from the SE manager 113 of the mobile device 100 through step S330 of FIG. M2 "and WA-ID is" W3 ", the TSM 200 deletes" A3 "and" A4 "issued in association with" W3 "installed in" M2 ".

5 is a flowchart provided to explain an SE applet automatic deletion method linked to WA deletion according to another embodiment of the present invention. The flowchart shown in FIG. 5 consists of the procedures performed in the TSM 200.

As shown in FIG. 5, when an applet deletion request is received from the SE manager 113 of the mobile device 100 (S410), the TSM 200 extracts an MSISDN and a WA-ID included in the applet deletion request. (S420).

Thereafter, the TSM 200 determines the AID of the applet to be deleted from the AID DB 235 by referring to the MSISDN and the WA-ID extracted in step S420 (S430).

As an example (①), when the AID DB 235 is as shown in "FIG. 4", the MSISDN extracted through step S420 of FIG. 5 is "M3", and the WA-ID is "W1", the TSM ( 200) identifies the applet to be deleted as "A1".

As another example (②), when the AID DB 235 is as shown in "FIG. 4", the MSISDN extracted through step S420 of FIG. 5 is "M3", and the WA-ID is "W4", the TSM ( 200) identifies the applet to be deleted as "A5".

Next, the TSM 200 determines whether the applet having the AID identified in step S430 is linked to another WA (S440).

The applet with AID "A1" identified in the above example (①) is linked to other WAs installed in "M3" (WA with WA-ID "W4" and WA with WA-ID "W5"). There was not. Therefore, in the example (①), the TSM 200 determines that the applet having the AID identified in step S430 is not associated with another WA.

As such, if the applet having the AID identified in step S430 is not linked to another WA (S440-N), the TSM 200 may identify the SE 140 of the mobile device 100 as the applet having the AID identified through step S430. In step (S450), and notifies the SE manager 113 that the applet deletion is complete (S460).

On the other hand, the applet having the AID "A5" identified in another example (2) above is linked to another WA (WA-ID of WA "W5") installed in "M3". Therefore, in the case of another example (②), the TSM 200 determines that the applet having the AID identified in step S430 is linked to another WA.

As such, if the applet having the AID identified in step S430 is linked to another WA (S440-Y), the TSM 200 may check the SE 140 of the mobile device 100 for the applet having the AID identified in step S430. In step S470, the SE manager 113 is notified that "the applet cannot be deleted" without being deleted.

According to the above embodiment, since the applet associated with only the deleted WA is automatically deleted, the undeleted WA can be prevented from operating abnormally because there is no applet.

So far, the SE applet automatic deletion process linked to the WA deleted from the mobile device 100 has been described in detail with reference to preferred embodiments.

Since the SE manager 113 is installed during the OS porting process, the WA-ID list held by the SE manager 113 may need to be updated, and may be implemented to be updated by the TSM 200.

For example, after the SE manager 113 is installed, a new WA has been developed / distributed, and when the new WA is installed, the WA-ID list update can be implemented when the associated applet is issued to the SE 140. .

As another example, when a new WA is installed in the memory 110 of the mobile device 100 so that the TSM 200 issues an applet associated with the new WA to the SE 140, the TSM 200 may execute the SE manager 113. It is also possible to implement to update the list of WA-IDs owned by.

In the above embodiment, it is assumed that the SE applet is automatically deleted in conjunction with the WA deletion, but this is an example for convenience of explanation. In the case of managing the SE applet in a different manner in conjunction with the WA deletion, Applicable. For example, the applet issued in association with the WA deleted from the mobile device 100 may be replaced with a lock without being deleted.

In addition, in the above embodiment, it is assumed that the WA has been deleted by the user, but the reason for the deletion of the WA is irrelevant. That is, the technical idea of the present invention can be applied to a case in which the WA is deleted by the user as well as when the WA is deleted unintentionally due to a program error or a crash.

In addition, WA mentioned in the above embodiment is a kind of application mentioned for convenience of description, and the technical idea of the present invention is applicable to a case in which WA is replaced with another type of application.

In addition, MSISDN is an example of information for specifying the mobile device 100, of course, can be replaced with other information that can specify the mobile device (100).

Hereinafter, the internal configuration of the devices constituting the SE applet management system shown in FIG. 1 will be described in detail.

FIG. 6 is a detailed block diagram of the mobile device 100 shown in FIG. 1. As illustrated in FIG. 6, the mobile device 100 includes a memory 110, a touch screen 120, a processor 130, an SE 140, and a communication unit 150.

The memory 110 is a storage medium in which WAs 111-1, 111-2,..., 111-m are installed and deleted, and the SE manager 113 and the OTA proxy 115 are installed. The WAs 111-1, 111-2,..., 111-m are installed / deleted by the user, whereas the SE manager 113 and the OTA proxy 115 are installed by the TSM 200.

The SE 140 is a storage medium on which applets 145-1, 145-2, ..., 145-n are issued, and a removable SE (for example, a UICC (Universal IC Card) or an SD card (Secure Digital) Card)) may of course be an embedded SE.

The touch screen 120 functions as a display means for displaying visual information and as a user interface means for receiving a user command through a touch. In relation to the above embodiments, the touch screen 120 displays a WA execution screen and receives a WA deletion command.

The communication unit 150 establishes and maintains a communication connection with the TSM 200 through a mobile communication network.

The processor 130 controls the overall operation of the mobile device 100. In particular, the processor 130 periodically executes the SE manager 113 installed in the memory 110 to check the deleted WA and to delete the applet associated with the deleted WA to the TSM 200 through the communication unit 150. request.

FIG. 7 is a detailed block diagram of the TSM 200 shown in FIG. 1. As shown in FIG. 7, the TSM 200 includes a communication interface 210, a processor 220, and a storage 230.

The communication interface 210 is connected to communicate with the mobile device 100 through a mobile communication network. The storage unit 230 is a storage medium that stores programs and information necessary for the TSM 200 to provide a service. The storage unit 230 stores the AID DB 235 for managing the SE applet according to the present embodiment.

The processor 220 controls the overall operation of the TSM 200. In particular, for managing SE applets according to the present embodiment, the processor 220 performs the procedures performed by the TSM 200 among the procedures illustrated in FIG. 2 and the procedures illustrated in FIG. 5.

On the other hand, the technical idea of the present invention can be applied to a computer-readable recording medium containing a computer program for performing the functions of the apparatus and method according to the present embodiment. In addition, the technical idea according to various embodiments of the present disclosure may be implemented in the form of computer readable codes recorded on a computer readable recording medium. The computer-readable recording medium can be any data storage device that can be read by a computer and can store data. For example, the computer-readable recording medium may be a ROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, an optical disk, a hard disk drive, or the like. In addition, the computer-readable code or program stored in the computer-readable recording medium may be transmitted through a network connected between the computers.

In addition, although the preferred embodiment of the present invention has been shown and described above, the present invention is not limited to the specific embodiments described above, but the technical field to which the invention belongs without departing from the spirit of the invention claimed in the claims. Of course, various modifications can be made by those skilled in the art, and these modifications should not be individually understood from the technical spirit or the prospect of the present invention.

Claims

Determining whether to delete an application installed in a memory of the mobile device; And

If it is determined in the determining step that the application has been deleted, requesting a service management server for management of an applet issued to a SE (Secure Element) of the mobile device and associated with the application; How to manage SE applets.
The method of claim 1,

The requesting step,

Request management of an applet associated with the application while transmitting the ID of the application and the information of the mobile device to the service management server;

The service management server,

SE applet management method characterized by identifying the applet associated with the application using the information of the mobile device and the ID of the application.
The method of claim 2,

The mobile device,

SE applet management method characterized in that it does not identify the applet associated with the application.
The method of claim 1,

The management of the applet is

SE applet management method, characterized in that to delete the applet or to disable the applet.
The method of claim 1,

The determining step,

Determined by a management program having an ID list including the ID of the application,

The management program,

Before the application is installed in the memory, the SE applet management method, characterized in that installed in the memory with the ID list.
The method of claim 5,

And the ID list held by the management program can be updated by the service management server.
The method of claim 6,

The update,

SE application method, characterized in that is performed when another application is developed and distributed or when the other application is installed in the memory of the mobile device and the applet associated with the other application is issued to the SE.
A communication unit connected to communicate with the service management server;

A memory in which an application is installed; And

It is determined whether to delete the application installed in the memory, and if it is determined that the application is deleted, it is issued to the SE (Secure Element) and requests the service management server to manage the applet associated with the application through the communication unit A mobile device comprising a; processor.
Receiving a management request from the mobile device for an applet associated with an application deleted after being installed in a memory of the mobile device;

Identifying an applet associated with the deleted application; And

And managing the applet identified through the identifying step in a SE (Secure Element) of the mobile device.
The method of claim 9,

Determining whether the applet identified in the identifying step is linked to another application;

The management step,

SE applet management method characterized in that the step is performed when it is determined that the applet is not associated with the other application.
The method of claim 9,

The grasping step,

SE applet management method characterized in that to identify the applet associated with the application using the information of the mobile device included in the management request and the ID of the application.
The method of claim 9,

The management step,

SE applet management method, characterized in that to delete the applet or to disable the applet.
A communication interface coupled to communicate with the mobile device;

A storage unit for storing the mobile device, an application installed in the mobile device, and a DB (DataBase) in which applet information associated with the application is built; And

When the management request for an applet associated with an application deleted after being installed in the memory of the mobile device is received from the mobile device through the communication interface, the applet associated with the application deleted from the DB stored in the storage unit is received. And a processor configured to identify and manage the identified applets in a SE (Secure Element) of the mobile device.