WO2017099477A1 - Method for operating mobile device having plurality of card modules installed therein and mobile device therefor - Google Patents

Abstract

Disclosed is a method for operating a mobile device, the method comprising the steps of: extracting at least one card module among a plurality of card modules installed in the mobile device, on the basis of the location of the mobile device; obtaining information on at least one external device capable of interacting with the at least one card module; and providing a user interface including the information on the at least one external device which interacts with the at least one card module.

Description

Operation method of a mobile device having a plurality of card modules installed and the mobile device

The present invention relates to a method of operating a mobile device having a plurality of card modules and a mobile device.

Recently, a contactless card included in a mobile device is a combination of wireless recognition technology and integrated circuit (IC) card technology, which is a breakthrough in the field of electronic devices. When the contactless card is located within a predetermined distance from the card reader (or reader), data can be transmitted and received with the card reader through wireless communication.

Embodiments provide a user interface that provides information about a card reader by obtaining information about at least one card reader that can interact with at least one of the card modules installed in the mobile device, thereby providing a user experience. The purpose is to improve.

Embodiments also aim to improve the memory utilization of a mobile device by optimizing patch data of the card module installed in the mobile device.

A first aspect of the disclosed embodiment for solving the above problems is, based on the location of the mobile device, extracting at least one card module from a plurality of card modules installed in the mobile device; Obtaining information about at least one external device that can interact with at least one card module; And at least one external device that interacts with the at least one card module.

It provides a method of operating a mobile device comprising a.

The providing of the user interface may change information provided through the user interface when the interaction between the at least one card module and the at least one external device fails.

In addition, when information on a plurality of external devices capable of interacting with the at least one card module is obtained, the providing of the user interface may include comparing the information on the plurality of external devices to determine one external device from among the plurality of external devices. Selecting a; And providing a user interface including information on the selected external device.

In addition, extracting at least one card module may include obtaining patch data for at least one card module; And based on the location of the mobile device, performing a patch operation using some patch data among the patch data; It may include.

The extracting of the at least one card module may further include canceling the previous patch operation by comparing the position of the mobile device with the position where the previous patch operation was performed.

The obtaining of the information on the external device may further include predicting a moving path of the mobile device based on the location of the mobile device; And acquiring information about the external device from at least one external device located around the movement path.

In addition, predicting a movement path of the mobile device may include determining a point of interest (POI) of the mobile device based on the information about the external device; And determining a movement path from the location of the mobile device to the nearest POI.

In addition, when the plurality of card modules are extracted, the step of providing the user interface may be based on at least one of the payment limit amount, the cumulative payment amount, the number of times of use, and the balance of the plurality of card modules. Determining an amount; And a user interface displaying the amount of payment to be paid using each card module.

The information on the external device may include at least one of identification information of the external device, type information of the external device, communication strength information of the external device, and location information of the external device.

In addition, when an interaction between at least one card module and an external device is performed, information about the interaction may be transmitted to another mobile device linked to the mobile device.

A second aspect of the disclosed embodiment includes a memory in which a plurality of card modules are stored; And a controller configured to extract at least one card module from the plurality of card modules based on the location of the mobile device. And a communication unit obtaining information about at least one external device that can interact with at least one card module, wherein the control unit includes information about at least one external device that interacts with at least one card module. A mobile device providing a user interface is provided.

A third aspect of the disclosed embodiment provides a computer readable recording medium having recorded thereon a program for implementing the method of the first aspect.

1 is a schematic diagram illustrating a method of operating a mobile device according to an embodiment.

2 is a flowchart illustrating a method of operating a mobile device according to an embodiment.

3 is an example of a user interface including information about an external device.

4 is another example of a user interface including information about an external device.

5 is a flowchart illustrating a method of extracting one card module from the extracted card module according to an embodiment of the present invention.

6 is an example of interaction history information managed by a mobile device.

7 is a flowchart illustrating another method of obtaining information regarding an external device by a mobile device according to an embodiment.

8 illustrates an example in which the mobile device predicts a movement path of the mobile device using POI information.

9 is a diagram illustrating another method of predicting a movement path of a mobile device by a mobile device according to an embodiment.

10 is a diagram illustrating a method of providing a user interface by a mobile device according to an embodiment.

FIG. 11 illustrates an example in which a mobile device changes information provided through a user interface when an interaction between a card module and an external device fails.

12 is an example of a user interface for charging a balance of a cash card module.

13 is an example of a user interface for dividing a payment amount with another card module.

14 is a flow chart illustrating a method for a mobile device to install a new card module usable at a current location in accordance with an embodiment.

15 is an example of a user interface for installing a new card module.

16 is a flowchart illustrating a method of performing a patch operation by a mobile device according to an embodiment.

17 illustrates an example in which the mobile device selects some of the patch data based on the location information.

18 is an example of a user interface for selecting a card module to perform a patch operation from among a plurality of card modules.

19 is a flow chart illustrating a method for a mobile device to cancel a previous patching task according to an embodiment.

20 is an example of a user interface for receiving a user input for canceling a previous patching operation of a card module.

21 is an example of a user interface for managing a preferred area.

22 is a flowchart illustrating a method of extracting at least one card module from a plurality of card modules based on a probability that a mobile device uses a plurality of card modules according to an embodiment.

23 is an example of a user interface recommending at least one card module.

24 is a flowchart illustrating a method in which a mobile device interacts using a traffic card module according to an embodiment.

25 is a flowchart illustrating a method of providing, by a mobile device, interaction information with an external device to another mobile device according to an embodiment.

26 is an example of another mobile device that received interaction information from the mobile device.

FIG. 27 is a flowchart illustrating a method of providing, by a mobile device, a map image indicating a location of a POS terminal according to an embodiment.

28 is an example of a map image in which the position of the POS terminal is displayed.

29 and 30 are diagrams illustrating a configuration of a mobile device according to an embodiment.

Terms used herein will be briefly described and the present invention will be described in detail.

The terms used in the present invention have been selected as widely used general terms as possible in consideration of the functions in the present invention, but this may vary according to the intention or precedent of the person skilled in the art, the emergence of new technologies and the like. In addition, in certain cases, there is also a term arbitrarily selected by the applicant, in which case the meaning will be described in detail in the description of the invention. Therefore, the terms used in the present invention should be defined based on the meanings of the terms and the contents throughout the present invention, rather than the names of the simple terms.

Terms including ordinal numbers such as first and second may be used to describe various components, but the components are not limited by the terms. The terms are only used to distinguish one component from another. For example, without departing from the scope of the present invention, the first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component. The term and / or includes any one of a plurality of related items or a combination of a plurality of related items.

When any part of the specification is to "include" any component, this means that it may further include other components, except to exclude other components unless otherwise stated. In addition, the term "part" as used herein refers to a hardware component, such as software, FPGA or ASIC, and "part" plays certain roles. However, "part" is not meant to be limited to software or hardware. The “unit” may be configured to be in an addressable storage medium and may be configured to play one or more processors. Thus, as an example, a "part" refers to components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, Subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays and variables. The functionality provided within the components and "parts" may be combined into a smaller number of components and "parts" or further separated into additional components and "parts".

DETAILED DESCRIPTION Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention. As those skilled in the art would realize, the described embodiments may be modified in various different ways, all without departing from the spirit or scope of the present invention. In the drawings, parts irrelevant to the description are omitted in order to clearly describe the present invention, and like reference numerals designate like parts throughout the specification.

1 is a schematic diagram illustrating a method of operating a mobile device according to an embodiment.

Referring to FIG. 1, the external device 20 may communicate with the plurality of card modules 12 installed in the mobile device 10.

The mobile device 10 may be provided with services such as securities or payment, identity verification, or the like through at least one of the plurality of card modules 12 installed in the mobile device 10. The card module 12 may be software stored in a memory of the mobile device 10. The card module 12 may include, for example, a transportation card module for payment of transportation expenses, a credit card module and a bank card module for sending and receiving securities or payments, an ID card module for identification and an employee (or student) card module, and the like. It may include.

According to an embodiment, the mobile device 10 may manage the plurality of card modules 12. For example, the mobile device 10 may perform a patch operation on the plurality of card modules 12 based on the location information of the mobile device 10. In addition, the mobile device 10 may identify at least one external device 20 located at the periphery of the mobile device 10 and select at least one card module interacting with the external device 20. Here, the interaction of the card module 12 with the external device 20 means that the card module 12 communicates with the external device 20 in a non-contact state through a wireless communication device provided in the mobile device 10. Can be.

According to an exemplary embodiment, the mobile device 10 may provide a user interface including information about the external device 20 interacting with at least one selected card module. Here, the UI may include visual, audio, and / or sensory data output by the mobile device 10 to receive a control signal from a user. For example, the mobile device 10 may compare the installation time of the external device 20 and provide a user interface including recommendation information for recommending an external device having the shortest installation time among the external devices. In addition, the mobile device 10 may provide a user interface including point of interest (POI) information of a user based on past interaction information with external devices.

Meanwhile, the mobile device 10 may be a smart phone, a tablet PC, a PC, a smart TV, a mobile phone, a personal digital assistant (PDA), a laptop, a media player, a micro server, a global positioning system (GPS) device, an e-book device, or digital broadcasting. Terminals, navigation, kiosks, MP3 players, digital cameras, home appliances, etc. may be included, but are not limited thereto. The mobile device 10 may include a wearable device such as a watch, glasses, a hair band and a ring having a communication function and a data processing function.

The external device 20 is a card reader (card reader) capable of transmitting and receiving data with a plurality of card modules 12 installed in the mobile device 10. To this end, the external device 20 may communicate with the mobile device 10 through a wireless network such as a local area network or a mobile communication network. For example, the external device 20 may include Bluetooth, Bluetooth low energy, Zigbee, Wi-Fi Direct (WFD), ultra wideband (UWB), infrared data association (IrDA), and NFC (Near). Field communication) to communicate with the mobile device 10.

The external device 20 may transmit data received from the mobile device 10 to a cloud server, a web server, or a data server, and receive a result value. The external device 20 may perform an operation such as outputting payment information, outputting payment error information, or unlocking the door lock based on the received result value.

The external device 20 may include a point of sale terminal, a bus card terminal, a subway card terminal, a door check terminal, a security device, an automatic teller's machine (ATM), a cash dispenser, and the like. .

2 is a flowchart illustrating a method of operating a mobile device according to an embodiment.

Referring to FIG. 2, in operation S210, the mobile device 10 extracts at least one card module of a plurality of card modules installed in the mobile device 10 based on the location of the mobile device 10.

According to an embodiment, the mobile device 10 may determine the location of the mobile device 10. For example, the mobile device 10 may obtain GPS location information from the GPS device provided in the mobile device 10. In addition, the mobile device 10 uses the cell information (eg, cell ID) of the mobile device 10 obtained through the network, so that the address (eg, country / city) where the mobile device 10 is located. Location, etc.) In addition, the mobile device 10 may determine the location of the mobile device 10 based on a Wi-Fi hotspot ID, an IP address, or the like. The mobile device 10 may also provide a user interface for determining the location of the mobile device 10.

According to an exemplary embodiment, the mobile device 10 may extract at least one card module from among a plurality of card modules according to a location. For example, when the location of the mobile device 10 indicates a bank, a bank card module, an ID card module, or the like may be extracted. In addition, when the location of the mobile device 10 indicates a company where the user works, an employee card module may be extracted.

The mobile device 10 may extract at least one card module, depending on the location and previous interaction history. For example, the previous interaction history may include an interaction time generated in the mobile device 10, information on a card module performing the interaction, an external device, and the like. For example, the mobile device 10 may search the interaction history generated at the current location and select at least one card module corresponding to the searched interaction history.

According to an embodiment, the mobile device 10 may perform a patch operation on the extracted card module. In this case, the mobile device 10 may perform a patch operation using only some patch data based on the location of the mobile device 10. A method in which the mobile device 10 performs a patch operation using the location information of the mobile device 10 will be described later in detail with reference to FIGS. 16 to 21.

Meanwhile, when at least one card module from the plurality of card modules cannot be extracted according to the position of the mobile device 10 in operation S210, a user interface for installing a new card module may be provided. For example, when the user of the mobile device 10 is abroad, the mobile device 10 may provide a user interface for installing a card module that can be used abroad, depending on the location.

In operation S220, the mobile device 10 obtains information on at least one external device that can interact with at least one card module. The information on the external device may include identification information, type, location, height, communication type, communication distance, communication strength, and the like of the external device.

According to an exemplary embodiment, the mobile device 10 may provide information provided by the external device 20 (for example, information broadcast from the external device 20) or an external device based on the extracted card module type. Information about the external device 20 may be obtained from a server (eg, a cloud server or a web server). For example, if the extracted card module is a credit card module or a bank card module, the mobile device 10 may obtain information about a point of sale terminal. In addition, when the extracted card module is an ID card module, the mobile device 10 may obtain information about the ID card terminal.

The mobile device 10 may obtain information about the external device located within a predetermined range (eg, within a 1 meter range, within a 0.5 meter range, etc.) from the mobile device 10 based on the location. Alternatively, the mobile device 10 may predict the next location of the mobile device 10 and obtain information about an external device located around the moving path from the current location to the next location. A method of acquiring information about an external device located around the moving path by the mobile device 10 will be described later in detail with reference to FIGS. 7 to 9.

The mobile device 10 may analyze the previous interaction history to obtain information about an external device that can interact with the extracted at least one card module.

In operation S230, the mobile device 10 provides a user interface including information about an external device that interacts with the extracted at least one card module. For example, the mobile device 10 may provide a user interface including a user guide for guiding a method of interacting with the external device 20 based on the type of the external device 20. In addition, the mobile device 10 includes a user interface including a user guide for guiding the current position of the mobile device 10 closer to the position and height of the external device 20 for stable interaction with the external device 20. Can provide.

According to an exemplary embodiment, when information on a plurality of external devices is received, the mobile device 10 may select one external device 20 by comparing the received information. In addition, the mobile device 10 may provide a user interface including information on the selected external device 20. For example, the mobile device 10 compares the communicable distances of the external devices, selects one external device 20 having the longest possible communication distance, and provides a user interface indicating the selected external device 20. can do. Alternatively, the mobile device 10 may compare the identification information of the external devices and provide a user interface indicating the external device 20 having the shortest installation period. As such, the mobile device 10 may recommend the external device 20 most suitable for the user through the user interface, and induce the user to interact using the recommended external device 20.

Meanwhile, when a plurality of card modules are extracted in operation s210, the mobile device 10 may provide a user interface that distinguishes and displays information about external devices that each card module can interact with. In this case, the mobile device 10 may interact with the selected card module and the external device 20 in response to a user input for selecting one of the extracted plurality of card modules.

Alternatively, the mobile device 10 may interact with an external device using a plurality of card modules. For example, the mobile device 10 may divide the payment price to allow the plurality of card modules to interact with the external device 20 at the divided payment price. In this case, the mobile device 10 may provide a user interface including information on each card module and the divided payment price.

Alternatively, the mobile device 10 may provide a user interface including information on an external device interacting with the highest priority card module by assigning a priority to the plurality of card modules. In this case, the mobile device 10 may determine the priority based on the interaction frequency for each card module, the recent interaction history, the user input, and the like.

According to an exemplary embodiment, the mobile device 10 may change information provided through the user interface according to a result of the interaction between the extracted card module and the external device 20. For example, if the interaction is successful, the mobile device 10 may include a user interface including interaction details (e.g., payment amount, transportation amount, bank balance, cash card balance, e-cash balance, ID verification, etc.). Can provide. In addition, if the interaction fails, the mobile device 10 may change the information provided through the user interface. For example, the mobile device 10 may provide a user guide that guides how to interact with the card module and the external device 20. Alternatively, if the interaction fails, the mobile device 10 may provide a user guide that guides the current position of the mobile device 10 in detail so as to be close to the position and height of the external device 20.

Alternatively, the mobile device 10 may change the information provided through the user interface according to the number of interaction failures. For example, if the Nth interaction between the card module and the external device 20 fails, the mobile device 10 guides the current position of the mobile device 10 in detail so that the position and height of the external device 20 are close to each other. Provide a user interface that includes a user guide and, if the Mth interaction fails, provide a user interface that includes information about another card module or other external device, in order to encourage the use of another card module or another external device. Can be.

According to an exemplary embodiment, the mobile device 10 may determine the information provided through the user interface according to a result of comparing the threshold values with each piece of information about the external device. For example, if the communication signal strength of the external device 20 is smaller than the threshold, the mobile device 10 may provide a user interface indicating the communication signal strength of the external device 20. On the other hand, if the communication signal strength of the external device 20 is greater than the threshold, the mobile device 10 may provide a user interface including other information.

The mobile device 10 may provide a user interface including at least one of a payment limit amount, a cumulative payment amount, a usage count, and a balance of the extracted card module. In addition, when the extracted card module is a cash card module, the user interface may be further provided to fill the amount of cash card module. In this case, the user interface may provide a method for charging the amount of cash card module.

3 is an example of a user interface including information about an external device.

Referring to FIG. 3, the mobile device 10 relates to a subway card terminal capable of extracting a subway traffic card module according to a location (eg, a subway station) of the mobile device 10 and interacting with the subway traffic card module. The user interface 310 including the information may be provided. For example, the user interface 310 may include a graphical user interface (GUI) indicating type information 311, location information 312, communication distance information 313, and the like of the subway card terminal.

According to an exemplary embodiment, when the mobile device 10 obtains information on a plurality of subway card terminals (eg, first to tenth subway card terminals), the mobile device 10 may be configured to include a plurality of subway card terminals. The identification information can be compared. In addition, the mobile device 10 may provide the user interface 310 further including a GUI 314 indicating the most recently installed external device (eg, the tenth subway card terminal) based on the comparison result. have.

In addition, the user interface 310 may include an image of a subway card terminal. In this case, the image of the subway card terminal may be obtained from an imaging device (for example, a camera) provided in the mobile device 10, but is not limited thereto. For example, the image of the subway card terminal may be obtained through an external server (eg, cloud server, web server, etc.) or the Internet.

In addition, the mobile device 10 provides a user guide 315 for guiding the position of the mobile device 10 to be close to the position and height of the subway traffic card terminal for stable interaction between the subway traffic card module and the subway traffic card terminal. The user interface 310 may be further included.

4 is another example of a user interface including information about an external device.

Referring to FIG. 4, the mobile device 10 extracts the W bank card module and the ID card module according to the location of the mobile device 10 (eg, the W bank), and interacts with each card module. The UI 410 may be provided to separately classify the information 411 and 412.

In addition, the mobile device 10 responds to a user input (eg, a touch input) 420 received in a screen area representing information 412 about the external device interacting with the ID card module. Interaction between the card module and the 'ID card terminal # 1' may be performed.

5 is a flowchart illustrating a method of extracting one card module from the extracted card module according to an embodiment of the present invention.

Referring to FIG. 5, in operation 510, the mobile device 10 may obtain interaction history information. For example, when the interaction between the plurality of card modules installed in the mobile device 10 and the external device 20 is performed, the mobile device 10 may perform the interaction, the identification information of the interaction with the card module, and the interaction. Information about an external device that performs the operation may be extracted. In addition, the mobile device 10 may store and manage interaction history information including the extracted information.

6 is an example of interaction history information managed by a mobile device. Referring to FIG. 6, the interaction history information 600 may correspond to a time, a location at which an interaction between the card module installed in the mobile device 10 and the external device 20 is performed, an identification information of the card module, or an external device on which the interaction is performed. Information about the service, and the like. Here, the information about the external device may include an identification value of the external device (for example, X1, C2, etc.), the type of the external device (for example, a POS terminal, a traffic terminal, etc.), or the mobility of the external device (for example, , Mobility or non-mobility), communication distance (for example, 0.3 m, etc.), communication strength (for example, 50 Hz, etc.).

Meanwhile, in FIG. 6, the interaction location is expressed as GPS information in the interaction history information 600, but is not limited thereto. For example, the interaction history information 600 may be expressed as a name of a store on which the interaction is performed, a company name, a name of a subway station, a name of a stop, and the like.

In the above description, it has been described that the mobile device 10 generates, stores, and manages interaction history information, but is not limited thereto. The interaction history information may be provided from an external server (eg, a server of a card module provider, etc.).

Referring back to FIG. 5, in operation 520, the mobile device 10 may obtain information about an external device that can interact with the extracted card module based on the type of the extracted card module and the interaction history information.

7 is a flowchart illustrating another method of obtaining information regarding an external device by a mobile device according to an embodiment.

Referring to FIG. 7, in operation 710, the mobile device 10 may predict a moving path of the mobile device 10 based on the interaction history information.

According to an exemplary embodiment, the mobile device 10 may extract point of interest (POI) information of the user using the interaction history information (600 of FIG. 6). For example, the mobile device 10 calculates the interaction frequency for each external device from the interaction history information 600, and if the usage frequency for each external device is greater than or equal to the threshold value, designates the location of the external device 20 as POI. Can be.

The mobile device 10 may predict the movement path of the mobile device 10 by comparing the location of the mobile device 10 with the extracted POI information. For example, the POI information nearest to the current location of the mobile device 10 may be determined as the next location. Alternatively, the mobile device 10 may receive a user input for selecting a next location of the mobile device 10 by providing a user interface including POI information.

In operation s720, the mobile device 10 may obtain information about external devices located around the predicted movement path.

For example, the mobile device 10 may interact with the extracted card module from among external devices located around a moving path from an external server (eg, a cloud server, a web server, etc.) from the current location to the next location. Information about the external device 20 may be obtained.

Alternatively, the mobile device 10 may receive POI information of another mobile device having a friend relationship with the mobile device 10. The mobile device 10 may obtain information on at least one external device 20 based on POI information of another mobile device.

8 illustrates an example in which the mobile device predicts a movement path of the mobile device using POI information.

Referring to FIG. 8, the mobile device 10 may extract first POIs to seventh POIs 811 to 817 of the mobile device 10 using the interaction history information (600 of FIG. 6).

According to an embodiment, the second POI 802 nearest to the current location 801 of the mobile device 10 may be predicted as the next location. Also, the mobile device 10 may obtain POI information 831 and 832 of another mobile device having a friend relationship with the mobile device 10. Accordingly, the mobile device 10 may obtain information about an external device located in the movement path of the mobile device 10 using the POI information 831 and 832 of the other mobile device.

9 is a diagram for describing another method of predicting, by a mobile device, a movement path of a mobile device, according to an embodiment.

Referring to FIG. 9, the mobile device 10 may extract the interaction history 900 for each time using the interaction history information (600 of FIG. 6). For example, the interaction history 900 for each time may include a location where an interaction is generated in a predetermined time unit, identification information of a card module used for the interaction, and the like.

According to an embodiment, the mobile device 10 may determine the next location based on the current time. For example, if the mobile device 10 is currently PM 19:30, it may determine the B mart as the next moving location. In addition, the mobile device 10 may obtain information about an external device located around a moving path from the current location to the B mart.

10 is a diagram illustrating a method of providing a user interface by a mobile device according to an embodiment.

Referring to FIG. 10, in operation S1010, the mobile device 10 may provide a user interface including information about an external device interacting with the extracted card module. For example, the mobile device 10 may provide a user interface including information about the type, location, signal strength, and the like of the external device 20.

In operation s1020, the mobile device 10 may determine whether the interaction between the extracted card module and the external device 20 is successful. For example, the mobile device 10 may determine whether an interaction completion signal is received from the external device 20 or an external server (for example, a card company server, etc.) within a predetermined time after the interaction start signal. have. If the interaction completion signal is not received within a predetermined time after the interaction start signal, the mobile device 10 may determine that the interaction has failed.

If it is determined that the interaction has failed, in operation s1030, the mobile device 10 may change information provided through the user interface.

For example, the mobile device 10 may generate a detailed user guide that guides the current location of the mobile device 10 to be close to the location and height of the external device 20. Alternatively, the mobile device 10 may provide a user interface that compares information about external devices and induces the user to use another external device. Alternatively, when a plurality of card modules are extracted, the mobile device 10 may select one card module and provide a user interface indicating the selected card module.

On the other hand, the interaction between the card module and the external device 20 fails due to insufficient balance of the card module, exceeding a preset limit amount (eg, daily limit amount, monthly limit amount, cumulative limit amount, etc.) of the payment amount. You may. In this case, the mobile device 10 may provide a user interface for charging the balance of the card module or a user interface for dividing a payment with another card module. In addition, the mobile device 10 may provide a user interface for dividing a payment amount with a card module installed in another user's mobile device. The mobile device 10 may communicate with a mobile device of another user to activate a card module installed in the mobile device of another user.

FIG. 11 illustrates an example in which a mobile device changes information provided through a user interface when an interaction between a card module and an external device fails.

Referring to FIG. 11, the mobile device 10 includes a first user interface including type, location, and communication signal strength information of a 'subway card terminal # 1' interacting with the extracted subway card module. 1110 may be provided.

If the interaction fails, the mobile device 10 may provide a second user interface 1120 including a user guide that guides the location of the mobile device 10 to the location and height of the subway card terminal # 1.

In addition, if the interaction fails again, the mobile device 10 may be configured to represent another external device in order to induce the user to interact via another external device (eg, subway card terminal # 2). 3 may provide a user interface 1130.

12 is an example of a user interface for charging a balance of a cash card module.

Referring to FIG. 12, when the balance of the cash card module is insufficient, the mobile device 10 may provide a first pop-up window 1210 that receives a user input for filling the balance of the cash card module. have. In addition, when the user input 1220 for charging the balance of the cash card module is received, the mobile device 10 may provide a second pop-up window 1230 indicating how to charge the balance.

13 is an example of a user interface for dividing a payment amount with another card module.

Referring to FIG. 13, when the payment amount of the card module exceeds a preset limit amount, the mobile device 10 includes information about the payment amount of the card module and the preset limit amount, and changes the payment amount of the card module to another. A first popup window 1310 may be provided to receive a user input for dividing the card module.

When the mobile device 10 receives a user input 1320 for dividing the payment amount of the card module from another card module in the first pop-up window 1310, the mobile device 10 receives the user input for determining and modifying the payment amount of each card module. The second pop-up window 1330 may be provided.

14 is a flow chart illustrating a method for a mobile device to install a new card module usable at a current location in accordance with an embodiment.

Referring to FIG. 14, in operation s1410, the mobile device 10 may determine a location of the mobile device 10.

In operation s1420, the mobile device 10 may determine whether there is a card module available at the determined location.

According to an exemplary embodiment, the mobile device 10 may determine whether there is a card module available at the determined location, based on the interaction history information (600 of FIG. 6).

Alternatively, the mobile device 10 may obtain information about the type of card module available at the determined location. For example, the mobile device 10 may obtain information on the type of card module that can be used in a store, according to the information broadcast by a beacon device placed in a store or the like.

If there is a usable card module, in operation s1430 the mobile device 10 may extract the usable card module.

If no usable card module exists, the mobile device 10 may provide a user interface for installing a new card module in operation S1440. For example, the mobile device 10 can provide a user interface that includes a list of card modules that can be installed on the mobile device 10. In addition, the mobile device 10 may install a new card module in response to the user input.

Meanwhile, the list of card modules available at the location of the mobile device 10 may be obtained from an external server (for example, a server of a store or a server of a card module provider), but is not limited thereto.

15 is an example of a user interface for installing a new card module.

Referring to FIG. 15, the mobile device 10 may include a user interface 1510 including location information 1511 of the mobile device 10, a list 1512 of installable card modules, and external device recommendation information 1513. Can provide. The external device recommendation information 1513 may include information about an external device closest to the mobile device 10, an external device having the largest communication strength, or an external device most recently installed.

16 is a flowchart illustrating a method of performing a patch operation by a mobile device according to an embodiment.

Referring to FIG. 16, in operation s1610, the mobile device 10 may obtain patch data of at least one card module extracted.

According to an exemplary embodiment, the mobile device 10 compares version information of patch data of a card module stored in an external server (eg, a cloud server or a web server) with version information of a card module installed in the mobile device 10. In this way, it is possible to determine whether to obtain patch data.

In addition, when the plurality of card modules are extracted, the mobile device 10 may provide a user interface for selecting a card module to be patched from among the plurality of card modules.

In operation S1620, the mobile device 10 may perform a patch operation using some patch data among the patch data based on the location.

The patch data registered in the external server may be generated in consideration of a card module installed in various regions or various devices. Accordingly, the mobile device 10 may select a portion of the patch data based on the location to perform a patch operation.

For example, if the patch data includes the first to fourth languages or the like, the mobile device 10 selects some patch data including the first language based on the location of the mobile device 10 to perform a patch operation. Can be performed. Meanwhile, the mobile device 10 may delete the patch data that is not selected.

According to an embodiment, the mobile device 10 may extract POI information of the mobile device 10 based on the interaction history information 600. The mobile device 10 may select a part of the patch data based on the extracted POI information. If the POI information is distributed in an area using the first language and the second language, the mobile device 10 selects some patch data including the first language and the second language from among patch data and performs a patch operation. Can be done.

Meanwhile, in the above description, it has been described that some patch data is selected using a language, but is not limited thereto. For example, when different interaction standards are required for different regions, the mobile device 10 may select only some patch data including a specific standard and perform a patch operation based on the location of the mobile device 10. .

17 illustrates an example in which the mobile device selects some of the patch data based on the location information.

Referring to FIG. 17, as the bus traffic card module is extracted, the mobile device 10 may obtain patch data that may be used in both city A through city C from the bus traffic card server 1710. The mobile device 10 may select some patch data that can be used in the city A among the patch data based on the location of the mobile device 10.

In addition, according to an exemplary embodiment, the mobile device 10 may analyze the POI information of the mobile device 10 to determine that the POI information is distributed in the A city and the C city. Accordingly, the mobile device 10 may select some patch data that can be used in city A and city C among patch data based on the POI information.

18 is an example of a user interface for selecting a card module to perform a patch operation from among a plurality of card modules.

Referring to FIG. 18, as the mobile device 10 is located in a shopping mall, the first to third credit card modules may be extracted. In addition, the mobile device 10 may provide a user interface 1810 for selecting a card module to be patched among the first to third credit card modules.

The mobile device 10 may perform a patch operation on at least one card module in response to a user input to the user interface 1810.

19 is a flow chart illustrating a method for a mobile device to cancel a previous patching task according to an embodiment.

Referring to FIG. 19, in operation s1910, the mobile device 10 may acquire location information of a previous patching operation of a card module performing a patching operation.

According to an embodiment, the mobile device 10 may manage the patch operation history of the card module. For example, the patch operation history may include at least one of a time, a location at which the patch operation is performed, a location where the patch data used for the patch operation is stored, or a combination thereof for each card module. The mobile device 10 may obtain location information on which the previous patching operation is performed based on the patching history.

In operation s1920, the mobile device 10 may cancel the previous patching operation of the card module based on a result of comparing the current location of the mobile device 10 with the location information on which the previous patching operation is performed. Canceling the previous patch task may be to delete the patch data used for the previous patch task.

For example, if the current location of the mobile device 10 represents city A and the location where the previous patch operation of the card module was performed represents the city C, the mobile device 10 may cancel the patch operation performed in the city C. Can be.

Alternatively, the mobile device 10 may provide a user interface for receiving a user input for canceling a previous patching operation of the card module.

Meanwhile, in the above description, the mobile device 10 determines whether to cancel the previous patching operation when performing the patching operation of the card module, but the present invention is not limited thereto. According to an embodiment, the mobile device 10 may perform operations s1510 and s1520 when the free storage space of the memory of the mobile device 10 is equal to or less than a threshold value (for example, 1 G (gigabytes), 256 M (megabytes), etc.). It can also be done.

20 is an example of a user interface for receiving a user input for canceling a previous patching operation of a card module.

Referring to FIG. 20, the mobile device 10 may provide a user interface 2010 for canceling a previous patching operation of a card module. The user interface 2010 may further include a button image 2020 that registers the region where the previous patching operation of the card module is performed as a favorite region. If the location where the previous patching operation was performed is registered as a preferred region, the mobile device 10 may maintain the previous patching operation.

21 is an example of a user interface for managing a preferred area.

Referring to FIG. 21, the mobile device 10 may provide a user interface 2110 for adding and deleting a preferred region in order to apply and / or delete patch data for a card module installed in the mobile device 10. have. The mobile device 10 may provide a user with a 'delete' button image 2111 for deleting a preferred region included in the user interface 2110 or a 'add' button image 2112 for adding a preferred region. In response to the input, you can add and delete favorite areas.

In addition, the user interface 2110 may include a map image 2113 for adding a preferred region. The mobile device 10 may add a location corresponding to the user input received from the map image 2113 as the preferred region.

When the mobile device 10 performs a patch operation on the card module, the mobile device 10 may perform the patch operation using patch data corresponding to the current location and the preferred region of the mobile device 10. In addition, when the mobile device 10 cancels a patch operation for the card module, the mobile device 10 may not cancel the patch operation corresponding to the preferred region.

On the other hand, it has been described above that the preferred region is added and deleted according to the user input, but is not limited thereto. According to an embodiment, the mobile device 10 may register the predetermined area as the preferred area when the predetermined area includes the POI greater than or equal to the threshold value using the POI information extracted from the interaction history information (600 of FIG. 6).

In addition, the mobile device 10 may add a preferred region based on information collected from applications installed in the mobile device 10. For example, the mobile device 10 may add the F region to the preferred region when the information from the schedule management application that the user visits the F region after 3 days is collected.

22 is a flowchart illustrating a method of extracting at least one card module from a plurality of card modules based on a probability that a mobile device uses a plurality of card modules according to an embodiment.

Referring to FIG. 22, in operation s2210, the mobile device 10 may obtain interaction history information. Since operation s2210 may correspond to operation s510 of FIG. 5, a detailed description thereof will be omitted.

In operation s2220, the mobile device 10 may calculate a probability that each card module installed in the mobile device 10 will be used based on the interaction history information.

According to an embodiment, the mobile device 10 may extract the interaction history for each time (eg, 900 of FIG. 9) or the interaction frequency for each card module from the interaction history information. In addition, the mobile device 10 may calculate the probability of using each card module based on at least one of the interaction history for each card module and the frequency of interaction for each card module, corresponding to the location and time of the mobile device 10.

Referring to FIG. 9, for example, when the current time is AM 7:00, the second card module may be used with a 60% probability based on the interaction history by time and the interaction frequency by card module. It can be determined that the third card module can be used with a 40% probability.

In operation s2230, the mobile device 10 may extract at least one card module from the plurality of card modules based on the calculated probability. For example, the mobile device 10 may extract a card module having a high probability of being used among the plurality of card modules.

In addition, the mobile device 10 may provide a user interface indicating information on the calculated probability and a card module having a high probability.

23 is an example of a user interface recommending at least one card module.

Referring to FIG. 23, the mobile device 10 may extract at least one card module having a high probability of being used, based on an interaction history at the current location of the mobile device 10.

In addition, the mobile device 10 may determine the current position information 2311 of the mobile device 10, the extracted card module and the probability information 2312 of the extracted card module, and the identification information 2313 of the card module having the highest probability. It may provide a user interface 2310 including a. The mobile device 10 may receive a user input for identification information 2313 of the card module having the highest probability, and activate the card module having the highest probability.

24 is a flowchart illustrating a method in which a mobile device interacts using a traffic card module according to an embodiment.

Referring to FIG. 24, in operation s2410, the mobile device 10 may perform a check-in interaction between the traffic card module installed in the mobile device 10 and the traffic card terminal.

In operation s2420, the mobile device 10 may provide a user interface including check-out information based on the interaction history information.

For example, the mobile device 10 may predict the check-out location of the traffic card module and the time until the check-out based on the interaction history information. Accordingly, mobile device 10 may provide a notification message to check out when the check-out time is near (eg, a previous stop or one minute ago).

Meanwhile, the mobile device 10 may further provide a user interface for setting a time point (eg, two stops before, five minutes before, etc.) when the notification message is provided.

25 is a flowchart illustrating a method of providing, by a mobile device, interaction information with an external device to another mobile device according to an embodiment.

Referring to FIG. 25, in operation s2510, the mobile device 10 may interact with the external device 20.

In operation s2520, the mobile device 10 may detect another mobile device (or wearable device) 30 associated with the mobile device 10. The other mobile device (or wearable device) 30 associated with the mobile device 10 may be another mobile device or wearable device configured to share all or part of the information processed by the mobile device 10. For example, a smart watch sharing a text message received at the mobile device 10 is associated with the mobile device 10.

In operation s2530, the mobile device 10 may transmit the interaction information to the other mobile device 30.

When the other mobile device 30 approaches the interaction range with the external device 20, in operation s2540, the other mobile device 30 warns that the interaction has already been performed based on the interaction information provided from the mobile device 10. Can be provided. In this case, the warning message may include time information on which the interaction between the mobile device 10 and the external device 20 is performed.

26 is an example of another mobile device that received interaction information from the mobile device.

Referring to FIG. 26, the smart watch 31 associated with the mobile device 10 may receive interaction information from the mobile device 10. Thereafter, when the external device 20 approaches the interactable range, the smart watch 31 warns that the interaction with the external device 20 has already been performed, based on the interaction information received from the mobile device 10. ) Can be provided.

FIG. 27 is a flowchart illustrating a method of providing, by a mobile device, a map image indicating a location of a POS terminal according to an embodiment.

Referring to FIG. 27, in operation S2710, the mobile device 10 may obtain information about a POS terminal. For example, the mobile device 10 may obtain information about the POS terminal located in the vicinity of the mobile device 10 or in the vicinity of the moving path.

According to an exemplary embodiment, the mobile device 10 may obtain information on the POS terminal having a frequency of interaction with the card module installed in the mobile device 10 or more based on the interaction history information.

In operation s2720, the mobile device 10 may provide a map image in which the location of the POS terminal is displayed. In this case, the mobile device 10 may highlight and display the position of the POS whose interaction frequency with the card module installed in the mobile device 10 is greater than or equal to the threshold value.

According to an embodiment, when the POS terminal is mobile, the mobile device 10 may track the location of the moving POS terminal. In addition, the mobile device 10 may display the location of the POS terminal to be tracked in the map image.

Meanwhile, according to an exemplary embodiment, the mobile device 10 may provide a user interface for reporting an error of the POS terminal.

28 is an example of a map image in which the position of the POS terminal is displayed.

Referring to FIG. 28, the mobile device 10 may provide a user interface including a map image 2810 in which a location of a POS terminal is displayed. The mobile device 10 may highlight and display the locations 2811, 2812, and 2813 of POS terminals whose interaction frequency with the card module installed in the mobile device 10 is greater than or equal to a threshold value in the map image 2810.

In addition, the mobile device 10 may add a new POS terminal, delete an existing POS terminal, or update information on the POS terminal through the map image 2810. For example, as shown in FIG. 28, the mobile device 10 adds a new POS terminal, deletes an existing POS terminal, or POS at a location where a user input 2814 is received in the map image 2810. The button image 2815 may be provided to update information about the terminal.

29 and 30 are diagrams illustrating a configuration of a mobile device according to an embodiment.

The operation of each configuration shown in FIGS. 29 and 30 is related to the embodiment described in FIGS. 1 to 28 described above. Therefore, although omitted below, the contents described above in FIGS. 1 to 28 may be applied to the operation of each component of FIGS. 29 and 30.

As illustrated in FIG. 29, the mobile device 10 according to the embodiment may include a display unit 2910, a controller 2920, a communication unit 2930, and a memory 2940. However, not all of the components shown in FIG. 29 are essential components of the mobile device 10. The mobile device 10 may be implemented by more components than the components shown in FIG. 29, and the mobile device 10 may be implemented by fewer components than the components shown in FIG. 29.

For example, as shown in FIG. 30, the mobile device 10 according to the embodiment may include, in addition to the output unit 3400, the controller 3200, the communication unit 3300, and the memory 3700 corresponding to the configuration of FIG. 29. The apparatus may further include an input unit 3100, a sensing unit 3500, and an A / V input unit 3600.

The input unit 3100 may mean a means for a user to input data for controlling the mobile device 10.

According to an exemplary embodiment, the input unit 3100 may provide a control signal corresponding to the user input to the controller 3200 in response to user inputs received from various user interfaces. Meanwhile, the user's input may include a press, continuous press, long press, tap, touch and hold, double tap, drag, pan, flick, drag and drop, and swipe.

In addition, the input unit 3100 is a means for inputting data using a touch pad (contact capacitive method, pressure resistive film method, infrared sensing method, surface ultrasonic conduction method, integral tension measuring method, piezo effect method, etc.). Can be. In addition, the input unit 3100 may further include a dome switch, a jog wheel, and the like.

The controller 3200 may typically control the overall operation of the mobile device 10. For example, the controller 3200 executes programs stored in the memory 3700, such as an input unit 3100, a communication unit 3300, an output unit 3400, a sensing unit 3500, an A / V input unit 3600, and the like. You can control the overall. The controller 3200 may include an input unit 3100, a communication unit 3300, an output unit 3400, a sensing unit 3500, and an A / V input unit to perform operations of the mobile device 10 of FIGS. 1 to 28. 3600, etc., can be controlled overall.

According to an embodiment, the controller 3200 extracts at least one card module from among a plurality of card modules stored in the memory 3700 based on the location of the mobile device 10. In this case, the position of the mobile device 10 may be obtained from the position sensor 3560 or the like provided in the mobile device 10. In addition, the location of the mobile device 10 may be obtained from cell information of the mobile device 10 obtained through the communication unit 3300. If the location of the mobile device 10 is a bank, the controller 3200 may extract at least one card module that can be used in the bank. Alternatively, the mobile device 10 may extract at least one card module based on a previous interaction history generated at the current location.

The controller 3200 may perform a patch operation on the extracted card module. The controller 3200 may perform a patch operation using only some patch data among the patch data based on the location of the mobile device 10. In addition, the controller 3200 may provide a user interface for canceling the previous patch operation of the card module by comparing the position of the mobile device 10 with the position where the previous patch operation is performed.

According to an embodiment, the controller 3200 obtains information on at least one external device that can interact with at least one card module. The information on the external device may include identification information, type, location, height, communication type, communication distance, communication strength, and the like of the external device.

For example, the controller 3200 may include information provided by the external device 20 (for example, information broadcast from the external device 20) or an external server based on the extracted card module type. The communication unit 3300 may be controlled to obtain information about the external device 20 from the controller. Alternatively, the controller 3200 may be configured to acquire information about an external device located within a predetermined range (for example, within a 1 meter range, within a 0.5 meter range, etc.) from the mobile device 10 based on the location. 3300 may be controlled. For example, the controller 3200 may activate the short range communication unit 3310 so that the communication unit 3300 obtains information broadcast from the outside.

Alternatively, the controller 3200 may analyze the interaction history information to obtain information about an external device that can interact with the extracted at least one card module. The interaction history information may include a time when the interaction between the card module stored in the memory 3700 and the external device 20 is performed, a location, identification information of the card module, or information about the external device on which the interaction is performed.

For example, the controller 3200 may extract point of interest (POI) information of the user using the interaction history information. In addition, the controller 3200 may predict the movement path of the mobile device 10 by comparing the location of the POI close to the location of the mobile device 10. In addition, the controller 3200 may acquire information about external devices located around the predicted movement path through the communication unit 3300. Alternatively, the controller 3200 may obtain information on at least one external device 20 by receiving POI information of another mobile device having a friend relationship with the mobile device 10.

According to an embodiment, the controller 3200 provides a user interface including information on an external device interacting with the extracted at least one card module. The controller 3200 may provide a visual, audio and / or sensory user interface by controlling the output unit 3400.

For example, the controller 3200 may provide a user guide that guides an interaction method with the external device 20 through a user interface. In addition, the controller 3200 may provide a user guide for guiding the position of the mobile device 10 to be closer to the position and height of the external device 20 so that the communication unit 3300 can stably interact with the external device 20. It can provide a user interface that includes.

When the controller 3200 receives information about a plurality of external devices through the communication unit 3300, the controller 3200 may provide a user interface that recommends one external device 20 by comparing the received information.

When a plurality of card modules are extracted, the controller 3200 may provide a user interface that distinguishes and displays information on an external device that each card module can interact with.

The controller 3200 may interact with an external device using a plurality of card modules. For example, the controller 3200 may divide the payment price and control the input unit 3100 and the communication unit 3300 so that the plurality of card modules interact with the external device 20 using the divided payment price. .

The controller 3200 may change the information provided through the user interface according to the result of the interaction between the extracted card module and the external device 20. In addition, the controller 3200 may change the information provided through the user interface according to the number of interaction failures. In addition, the controller 3200 may determine the information provided through the user interface according to a result of comparing the threshold information with each piece of information about the external device.

The controller 3200 may provide a user interface including at least one of a payment limit amount, a cumulative payment amount, a usage count, and a balance of the extracted card module.

The communicator 3300 may include one or more components that allow the mobile device 10 to communicate with at least one external device 20. For example, the communicator 3300 may include at least one of a short range communicator 3310, a mobile communicator 3320, and a broadcast receiver 3330.

The short-range wireless communication unit 3310 includes a Bluetooth communication unit, a Bluetooth low energy (BLE) communication unit, a near field communication unit, a WLAN (Wi-Fi) communication unit, a Zigbee communication unit, an infrared ray ( IrDA (Infrared Data Association) communication unit, WFD (Wi-Fi Direct) communication unit, UWB (ultra wideband) communication unit, Ant + communication unit and the like, but may not be limited thereto.

The mobile communication unit 3320 may transmit / receive a radio signal with at least one of a base station, an external terminal, and a server on a mobile communication network.

According to an embodiment, the communication unit 3300 may interact with the external device 20. For example, the communicator 3300 may transmit / receive encrypted data or non-encrypted data with the external device 20.

The communication unit 3300 may request information about the external device 20 from an external server and receive information about the external device 20. In addition, the communication unit 3300 may receive patch data or installation data of a card module from an external server. In addition, the communication unit 3300 may transmit the interaction history information of the mobile device 10 to an external server.

The output unit 3400 may output an audio signal, a video signal, or a vibration signal, and the output unit 3400 may include a display unit 3410, an audio output unit 3420, and a vibration motor 3430. have.

The display 3410 may output a user interface processed by the controller 3200. For example, the display 3410 may output a user interface for guiding an interaction method with the external device 20 under the control of the controller 3200. In addition, the display 3410 may change and output the information provided through the user interface under the control of the controller 3200.

The display 3410 may output a notification message, a pop-up message, a configuration window, a widget, and the like under the control of the controller 3200.

The display unit 3410 may be combined with the input unit 3100 to display a GUI provided to control the mobile device 10. For example, the display unit 3410 and the touch pad may be configured as a touch screen by forming a layer structure.

The display unit 3410 may include a liquid crystal display, a thin film transistor-liquid crystal display, an organic light-emitting diode, a flexible display, and a three-dimensional display. The display may include, but is not limited to, at least one of a 3D display and an electrophoretic display. In addition, depending on the implementation form, the mobile device 10 may include a plurality of display units.

The sound output unit 3420 outputs audio data received from the communication unit 3300 or stored in the memory 3700. The vibration motor 3430 may output a vibration signal.

The sensing unit 3500 may detect a state of the mobile device 10 or a state around the mobile device 10 and transmit the detected information to the controller 3200. For example, the sensing unit 3500 may include a geomagnetic sensor 3510, an acceleration sensor 3520, a temperature / humidity sensor 3530, an infrared sensor 3540, and a gyroscope sensor 3550. , At least one of a position sensor (eg, GPS) 3560, an air pressure sensor 3570, a proximity sensor 3580, and an RGB sensor (illuminance sensor) 3590, but is not limited thereto.

The A / V input unit 3600 is for inputting an audio signal or a video signal, and may include a camera 3610 and a microphone 3620.

The camera 3610 may obtain an image frame such as a still image or a moving image through an image sensor in a video call mode or a photographing mode. In addition, the microphone 3620 receives an external sound signal and processes the external sound signal into electrical voice data.

The memory 3700 may store a program for processing and controlling the controller 3200, and may store data input to or output from the mobile device 10.

The memory 3700 may include a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (for example, SD or XD memory), RAM Random Access Memory (RAM) Static Random Access Memory (SRAM), Read-Only Memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Programmable Read-Only Memory (PROM), Magnetic Memory, Magnetic Disk It may include at least one type of storage medium of the optical disk.

Programs stored in the memory 3700 may be classified into a plurality of modules according to their functions. For example, the programs may be classified into a UI module 3710, a touch screen module 1720, a card module 3730, and the like. .

The UI module 3710 may support a user interface or the like provided for controlling the mobile device 10. The touch screen module 3720 may detect a touch gesture on the touch screen of the user and support information about the touch gesture. The touch screen module 3720 according to some embodiments may recognize and analyze a touch code. Meanwhile, the touch screen module 3720 may be configured as separate hardware including a controller.

The card module 3730 may support data transmitted and received between the plurality of card modules and the external device 20. In addition, the card module 3730 may manage installation data, patch data, and the like of each card module. For example, the card module 3730 may classify the patch data according to the patch version.

The disclosed embodiments may also be embodied in the form of a recording medium containing instructions executable by a computer, such as a program module executed by the computer. Computer readable media can be any available media that can be accessed by a computer and includes both volatile and nonvolatile media, removable and non-removable media. In addition, computer readable media may include both computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Communication media typically includes computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave, or other transmission mechanism, and includes any information delivery media.

The foregoing description is for illustrative purposes, and it will be understood by those skilled in the art that the present invention may be easily modified in other specific forms without changing the technical spirit or essential features of the present invention. Therefore, it should be understood that the embodiments described above are exemplary in all respects and not restrictive. For example, each component described as a single type may be implemented in a distributed manner, and similarly, components described as distributed may be implemented in a combined form.

The scope of the present invention is shown by the following claims rather than the above description, and all changes or modifications derived from the meaning and scope of the claims and their equivalents should be construed as being included in the scope of the present invention. do.

Claims (15)

In the operating method of the mobile device, Extracting at least one card module from a plurality of card modules installed in the mobile device based on the location of the mobile device; Acquiring information about at least one external device that can interact with the at least one card module; And And providing a user interface comprising information about the at least one external device interacting with the at least one card module. The method of claim 1, Providing the user interface, Changing information provided through the user interface when the interaction between the at least one card module and the at least one external device fails. The method of claim 1, When information about a plurality of external devices that can interact with the at least one card module is obtained, Providing the user interface, Comparing information about the plurality of external devices and selecting one external device from the plurality of external devices; And And providing a user interface including information about the selected external device. The method of claim 1, Extracting the at least one card module, Acquiring patch data for the at least one card module; And Performing a patch operation using some patch data among the patch data based on the location of the mobile device; Including, the method of operation. The method of claim 4, wherein Extracting the at least one card module, Canceling the previous patch operation by comparing the location of the mobile device with the location where the previous patch operation was performed. The method of claim 1, Acquiring information about the external device, Predicting a movement path of the mobile device based on the location of the mobile device; And Acquiring information about an external device from at least one external device located at the periphery of the movement path. The method of claim 6, Predicting the movement path of the mobile device, Determining a point of interest (POI) of the mobile device based on the information about the external device; And Determining a movement path from the location of the mobile device to the nearest POI. The method of claim 1, When the plurality of card modules are extracted, Providing the user interface, Determining an amount to be paid using each card module based on at least one of a payment limit amount, a cumulative payment amount, a number of times of use, and a balance of the plurality of card modules; And And providing a user interface displaying an amount paid using each of the card modules. The method of claim 1, The information on the external device includes at least one of identification information of the external device, type information of the external device, communication strength information of the external device, and location information of the external device. The method of claim 1, And when the interaction between the at least one card module and the external device is performed, transmitting information about the interaction to another mobile device associated with the mobile device. In a mobile device, A memory in which a plurality of card modules are stored; And A controller configured to extract at least one card module from the plurality of card modules based on the location of the mobile device; And And a communication unit for obtaining information about at least one external device that can interact with the at least one card module. The controller provides a user interface including information about the at least one external device interacting with the at least one card module. The method of claim 11, The control unit changes the information provided through the user interface when the interaction between the at least one card module and the at least one external device fails. The method of claim 11, When information about a plurality of external devices that can interact with the at least one card module is obtained, The controller compares information about the plurality of external devices, selects one external device from the plurality of external devices, and provides a user interface including information on the selected external device. The method of claim 11, The control unit obtains patch data for the at least one card module and performs a patch operation using some patch data among the patch data based on the location of the mobile device. A computer readable recording medium having recorded thereon a program for implementing the method of any one of claims 1 to 10.

Images