Patent Description:
Apparatuses and methods consistent with exemplary embodiments relate to a mobile device and a control method thereof, and more particularly, to a mobile device capable of controlling an operation thereof according to a user's gesture and a control method thereof.

With development of electronic technology, various types of user terminal apparatuses have been used. In particular, recently, spread of high-spec user terminal apparatuses such as smart phones or tablet personal computers (PCs) are greatly increased.

Thus, a type of serve supported by the user terminal apparatuses gradually highly qualified. In particular, the users tend to prefer faster, more convenient, and simpler service as compared in the past. By considering these circumstances, research on services providable from the user terminal apparatuses have consistently progressed in various ways.

There is shopping service among the services. That is, in the past, the users purchase goods off-line only using cash or a credit card. In recent years, the users shop using a method of ordering goods in on-line shopping malls and paying a transaction amount by credit card, mobile phone authorization, deposit without a bankbook, and the like, using a users' own PCs.

However, it is cumbersome in the shopping service in that the user always has to use the credit for a payment. That is, the current user terminal apparatuses support shopping services in the limited level.

Therefore, there is a need for technology capable of providing the shopping services in the users-portable mobile devices.

However, to execute applications required to perform the payment in the mobile devices, it is inconvenient to perform operations several times. Therefore, it is difficult to enable the shopping using the mobile devices.

<CIT> discusses a method of gesture based authentication for wireless payment by a mobile electronic device. <CIT> discusses a method of accessing an online financial account through an applied gesture on a mobile device.

One or more exemplary embodiments may overcome the above disadvantages and other disadvantages not described above. However, it is understood that one or more exemplary embodiment are not required to overcome the disadvantages described above, and may not overcome any of the problems described above.

One or more exemplary embodiments are to provide a mobile device capable of conveniently simply providing shopping service according to a user's operation and a control method thereof.

According to another aspect of an exemplary embodiment, there is provided a payment method of a mobile device. The payment method may include: sensing user's touch done on a surface of a display unit of the mobile device in a disabled state of the display unit; enabling the display unit when a user's touch operation matched with preset gesture information is sensed, executing a wallet application, and display an execution screen; and transmitting information for a selected payment option to an external apparatus when the payment option is selected on the execution screen and performing a payment.

In another exemplary embodiment, the payment method may further include sensing a fingerprint; and determining whether or not the sensed fingerprint is matched with pre-registered fingerprint information. The wallet application may be executed when the user's touch operation matched with the gesture information and a user's fingerprint matched with the fingerprint information are sensed.

The disabled state of the display unit may be a state in which the display unit is off or a locked screen is displayed.

The user's touch operation may be a gesture in which a plurality of points are touched on the surface of the display unit and move to increase a distance therebetween.

According to the above-described exemplary embodiments, shopping services using mobile devices may be simply conveniently performed.

In yet another exemplary embodiment, there is a smartphone including: a touchscreen configured to receive finger input; a memory configured to store a plurality of gesture information; a controller configured to compare the received finger input with the plurality of gesture information and, if the received finger input corresponds to one gesture information of the plurality of gesture information, to perform at least one from among turning on the smartphone, waking up the smartphone, or unlocking the touchscreen, to execute a payment application corresponding to the one gesture information of the plurality of gesture information, and to display a screen of the executed payment application; and a wireless communication unit configured to wirelessly transmit information regarding a payment command received through the payment screen.

In one exemplary embodiment, the controller is configured to automatically execute the payment application after turning on the smartphone, waking up the smartphone or unlocking the touchscreen of the smartphone.

In another exemplary embodiment, the received finger input is an input received at the touchscreen by detecting a physical contact between a finger and the touchscreen.

In yet another exemplary embodiment, the received finger input is an input received at the touchscreen by detecting a finger hovering over the touchscreen.

Additional aspects and advantages of the exemplary embodiments will be set forth in the detailed description, will be obvious from the detailed description, or may be learned by practicing the exemplary embodiments.

The above and/or other aspects will be more apparent by describing in detail exemplary embodiments, with reference to the accompanying drawings, in which:.

Hereinafter, exemplary embodiments will be described in more detail with reference to the accompanying drawings.

In the following description, same reference numerals are used for the same elements when they are depicted in different drawings. The matters defined in the description, such as detailed construction and elements, are provided to assist in a comprehensive understanding of the exemplary embodiments. Thus, it is apparent that the exemplary embodiments can be carried out without those specifically defined matters. Also, functions or elements known in the related art are not described in detail since they would obscure the exemplary embodiments with unnecessary detail.

<FIG> is a block diagram illustrating a configuration of a mobile device according to an exemplary embodiment. The mobile device may be various types of apparatuses such as a mobile phone, a tablet PC, an electronic book, a personal digital assistant (PDA), an MPEG-<NUM> audio layer <NUM> (MP3) player, and a laptop PC.

Referring to <FIG>, the mobile device includes a display unit <NUM>, e.g., display, a sensor <NUM>, a controller <NUM>, and a storage unit <NUM>, e.g., storage.

The display unit <NUM> may be implemented with various types of displays such as a liquid crystal display (LCD), an organic light emitting diode (OLED) display, or a plasma display panel (PDP). A driving circuit which may be implemented with an amorphous (a-Si) thin film transistor (TFT), a low temperature polysilicon (LTPS) TFT, an organic TFT (OTFT), or the like, and a backlight unit, and the like are further included in the display unit.

The sensor <NUM> may sense user' touch done on a surface of the display unit <NUM>. The sensor <NUM> may be implemented with various types of touch sensors such as a capacitive type touch sensor, a resistive type touch sensor, or a piezoelectric type touch sensor. The capacitive touch sensor is configured to sense microelectricity excited to a user's body using a dielectric coated on a surface of the display unit when a part of the user's body is touched on the surface of the display unit110, and calculate a touch coordinate. The resistive type touch sensor is a configured to include two electrode plates built in the display unit <NUM>, sense current through the upper and lower electrode plates in contact with each other at a touched point when the user touches a screen, and calculate a touch coordinate. Thus, the sensor <NUM> may sense various types of user's touch operations such as touch, touch and drag, flick, long tough, and double touch and various types of user operations such as a motion gesture, a motion gesture, and speech input.

The sensor <NUM> may sense the user touch in a disabled state of the display unit <NUM>. The disabled state of the display unit <NUM> includes a state in which the display unit <NUM> displays a lock screen as well as a state in which the display unit <NUM> is off and a state in which the mobile device is in a sleep state. That is, the mobile device <NUM> automatically enters a lock state to turn off the display unit <NUM> when the user does not use the mobile device for above a certain period of time. In the screen off state, when a hardware button provided in a body of the mobile device is selected, the display unit displays a lock screen. When the user operation for performing an unlock operation on the lock screen, the mobile device releases the lock state and displays a main screen.

The controller <NUM> enables the sensor <NUM> to be consistently maintained in an enable state so that the sensor senses the user touch on a surface of the display unit <NUM> even in the disabled state of the display unit <NUM>.

The storage unit <NUM> stores operating system (OS) for driving the mobile device, programs, data, and various kinds of contents. Preset gesture information is included in the data stored in the storage unit <NUM>.

When the user touch is sensed by the sensor <NUM>, the controller <NUM> determines whether or not the user touch operation matches the gesture information stored in the storage unit <NUM>. When it is determined that the user touch operation matches the gesture information, the controller <NUM> enables the display unit <NUM>, automatically executes an application corresponding to the user touch operation, and immediately displays an execution screen of the application. The application corresponding to the user touch operation may be set by the intention of the designer or the user. In the exemplary embodiment, an example in which a wallet application, which is capable of providing shopping service such as a payment and purchase history management, matches the user touch operation is illustrated. That is, the controller <NUM> immediately displays the execution screen of the wallet application when a specific user touch operation is input even in the disabled state of the display unit <NUM>.

The communication unit <NUM> is configured to perform communication with an external apparatus. The communication unit <NUM> may perform the communication with the external apparatus using at least one of various communication methods such as a wireless local area network (LAN), wireless fidelity (Wi-Fi), Bluetooth, Zigbee, near field communication (NFC), and the like.

With regard to shopping service, the communication unit <NUM> may perform communication with external apparatuses, for example, server apparatuses such as servers of operators operating various online shopping mall sites, portal site servers, or cloud servers, and servers of service providers providing point of sale system (PoS) or other payment gateway (PG) service.

As one example, assuming that the communication unit <NUM> performs communication with the PoS, when the user selects one payment option on an execution screen of a wallet application and then inputs a payment command, the communication unit <NUM> transmits information for the selected payment option to the PoS and performs a payment. At this time, a short-range wireless communication method such as NFC may be used. That is, when the communication unit <NUM> includes an NFC module, the information for the payment option may be transmitted by NFC tagging to the PoS. The NFC tagging means a behavior which approaches and touches the external apparatus (that is, PoS and the like) within a distance range which can perform short-range wireless communication.

<FIG> is a flowchart specifically illustrating a payment method performed in the mobile device of <FIG>. Referring to <FIG>, when the user touch is sensed (S210), the controller <NUM> determines whether or not the sensed touch content matches preset gesture information (S220). The gesture information means information in which various items, for example, a location of a first touch point, the number of touch points, change in the touch point, change in a direction, trajectory, speed, etc., are combined.

The controller <NUM> enables the display unit (S230) when it is determined that the sensed touch content matches the gesture information, executes a wallet application, and immediately displays an execution screen of the wallet application (S240). When the user's next operation is performed on the execution screen, the payment is performed according to the user's next operation (S250). When a payment option set to default exists on the execution screen of the wallet application, the payment may be directly done only through a simple operation such as NFC tagging or button selection without a separate process of selecting a payment option on the execution screen.

According to the above-described exemplary embodiment, the payment is performed only through simple one or two operations of the user even when the mobile device is in a lock state, so that shopping service may be conveniently used.

<FIG> is a view illustrating an example of a user's operation for executing a wallet application. In <FIG>, 3000a illustrates that a display unit <NUM> is in an off state, that is, in a screen off state, or illustrates that the mobile device is in a sleep state. In this state, the user gestures to touch two points T1 and T2 on a surface of the display unit <NUM> using two fingers and then to spread the two fingers at both sides, the controller <NUM> performs an unlock operation, immediately executes the wallet application, and displays an execution screen <NUM> as illustrated in 3000b.

In <FIG>, 3000c illustrates that the display unit <NUM> displays a lock screen <NUM>. When the user performs a preset first user operation on the lock screen <NUM>, unlock is done, and thus a home screen may be displayed. On the other hand, when the user performs a preset second user operation on the lock screen <NUM>, the unlocking is done, and thus the execution screen <NUM> of the wallet application may be immediately displayed. Here, the second user operation may gesture that the user touches the two points T1 and T2 and spreads a gap between the two points.

As the gesture information in the exemplary embodiment of <FIG>, coordinate ranges of the points T1 and T2 at which first touch is done, a trajectory and direction of changes in touch points after the first touch, and the like have been preset and stored in the storage unit <NUM>. Thus, when the gesture information has been strictly set, execution of the wallet application due to the user's unintended touch may be prevented in the mobile device <NUM>.

The wallet application may manage various pieces of information related to the shopping service. The shopping service may be largely divided into a process of searching and selecting goods, a process of purchasing, and a process of managing after the process of purchasing.

The good search and selection may be performed both on-line and off-line. Specifically, the controller <NUM> may execute web browser, access to Internet, and display a site screen provided from various online shopping malls. The user searches for and selects his/her desired goods while the user views the site screen. Additional service such as a wish list may be provided in the selecting process. That is, the user has stored the goods, which are not immediately purchased but intended to purchase, in the wish list and then determines to purchase later. On the other hand, the process of searching for and selecting goods may be done off-line. Specifically, the user directly looks at and chooses the goods in department stores or shops.

When the process of searching for and selecting the goods is performed as described above, the purchase of the goods, that is, a payment may be done through the mobile device. Specifically, the mobile device <NUM> may perform the payment using the wallet application. In the wallet application, the payment may be performed using information for various payment options such as a credit card, an identifier (ID) card, a point card, a coupon, and an event card which are possessed by the user. The specific payment method using the wallet application will be described in more detail later.

After the purchase of the goods is done, the user may receive an electronic receipt or bill and manage a purchasing history. Thus, the wallet application may recognize purchase propensity of the user to recommend appropriate goods, purchase time, a purchase place, and the like, and further recognize problems and advice for the user to refrain from indiscreet purchase.

To provide various shopping services, the wallet application may store and manage various pieces of information related to shopping.

<FIG> illustrates an example of an information system managed by a wallet application.

Referring to <FIG>, a wallet application <NUM> may be divided into a payment part <NUM> configured to be in charge of an amount payment and a shopping management part <NUM>. Information such as a card list <NUM>, a payment mode <NUM>, and bills <NUM> is managed in the payment part <NUM> and information such as wishes <NUM> and a shop path <NUM> is managed in the shopping management part <NUM>.

The card list <NUM> includes card information such as credit card information <NUM>-<NUM>, ID card information <NUM>-<NUM>, point card/stamp information <NUM>-<NUM>, and instant card information <NUM>-<NUM> and the payment mode <NUM> includes mode information such as an automatic mode <NUM>-<NUM> and a manual mode <NUM>-<NUM>. In addition, the bills information <NUM> includes information such as a bill <NUM>-<NUM>, a split <NUM>-<NUM>, and a budget <NUM>-<NUM>. The wishes information <NUM> includes information such as wish items <NUM>-<NUM>, a wish place <NUM>-<NUM>, and a coupon <NUM>-<NUM> and the shop path information <NUM> includes information such as a map <NUM>-<NUM> and an item list <NUM>-<NUM>.

The controller <NUM> may execute the wallet application <NUM> to manage and use various pieces of information as illustrated in <FIG>. Hereinafter, various user interface screens displayed in the display unit <NUM> according to the execution of the wallet application and a method of using the same will be described in detail.

<FIG> illustrates an example of a home screen <NUM> of a wallet application. Credit card information <NUM>, ID card information <NUM>, payment detailed and predicted information <NUM>, shopping guide information <NUM>, menus <NUM>, <NUM>, and <NUM>, and the like are displayed in the home screen <NUM>.

The credit card information <NUM> indicates information for a credit card most frequently used or set to default. A card company, a card name, a total amount used this month, specified limit, a total amount used last month, and the like may be displayed together with the information for the credit card in the credit card information <NUM>. Further, a pay button <NUM> configured to immediately perform a payment using the corresponding credit card may be displayed at one side of the credit card information <NUM>.

The ID card information <NUM> may display information for a basic ID card issued by institutions such as a company or a school. Absenteeism and tardiness and admittance relevant records, and the like may be also displayed in the ID card information <NUM>.

An amount used this month, an estimated amount to be spent, a guide message, and the like may be displayed in the payment detailed and predicted information <NUM>. The guide message may be displayed in various contents according to a case in which expected spending and a budget are balanced, a case in which spending for a specific category is large, a case in which the expected spending is larger than the budget, a case in which the expected spending is smaller than the budget, and the like.

The shopping guide information <NUM> is divided into a plurality of tabbed pages. <FIG> illustrates a state in which the shopping guide information <NUM> is divided into tabbed pages such as shopping tips and recent bills. Information for recommending shopping to the user is displayed in the shipping tips. The 'shopping tips' may be displayed when an item, which satisfies a condition such as a schedule, time, a purchasing pattern, and a current location, exists among items registered in the wish list generated by the user. Information related to a split payment requested by a friend, contents for split payment request, recent receipts of purchase, and the like may be displayed in the 'current bills'. When the 'recent bills' is selected, a detailed view screen for social network service (SNS) or e-mail requesting the spilt payment and an electronic receipt, and the like may be displayed.

In addition, as illustrated in <FIG>, in the menu region, a home menu <NUM> for shortcut to a payment home screen, a card list menu <NUM> for shortcut to a screen providing various cards relevant information, the bills menu <NUM> for providing information relevant to a list of purchase records of the user and spending, and the like may be displayed. Although not shown, in the menu region, a wishes menu for displaying a list in which information for goods or shops interested on-line/off-line, or coupon/discount information is collected or a 'shopping path' menu for displaying a path on a map by automatically grouping the closest path among items registered in the wishes list or by grouping items selected by the user may be further displayed.

<FIG> illustrates an example of a card list screen displayed when the card list menu <NUM> is selected in the payment home screen <NUM>. Referring to <FIG>, a credit card item <NUM>, an ID card item <NUM>, a point card item <NUM>, a ticket item <NUM>, and the like are displayed in the card list screen <NUM>. Information <NUM>, <NUM>, <NUM>, and <NUM> for one representative card is displayed in each item. The menu area <NUM>, <NUM>, and <NUM> illustrated in <FIG> are kept the same in <FIG>.

The number (for example, <NUM>) of registered credit cards is displayed in the credit card item <NUM>. When the credit card item <NUM> is selected, lists for all stored cards may be displayed. The lists will be described later. Further, a pay button <NUM> may be displayed in the credit card item <NUM>. The pay button <NUM> is a button configured to immediately perform a payment using a credit card displayed in the card information <NUM>. When the user presses the pay button <NUM>, the controller <NUM> progresses a payment process using the displayed credit card. Specifically, the detailed payment process will be described in more detail later.

The ID card item <NUM> may be displayed in the same manner as the credit card item <NUM>. That is, information <NUM> for one representative card may be also displayed.

The point card item <NUM> is an item for displaying loyalty cards such as various types of point cards, mileage cards, and stamps. The ticket item <NUM> is an item for displaying information of cards for one-time use such as a ticket, a parking ticket and a gift card.

<FIG> and <FIG> have illustrated the examples of screens implemented in products in which a height length of a display is larger than a width length thereof, such as a mobile phone, but may be applied to a mobile device including a display in which a width length is larger than a height length, such as tablet personal computers (PCs).

<FIG> illustrates a layout of a card list screen <NUM> in which a width length is larger than a height length. Referring to <FIG>, an image <NUM> of a representative card and information <NUM> for the representative card may be displayed in the card list screen <NUM> together with card items <NUM>, <NUM>, <NUM>, and <NUM> and card information <NUM>, <NUM>, <NUM>, and <NUM>. Therefore, a payment using the representative card may be immediately done in the card list screen <NUM> without a process of selecting a separate payment option again.

When the mobile device may sense a rotation state thereof, if the mobile device <NUM> is rotated <NUM> degrees to the left or to the right while displaying the card list screen as illustrated in <FIG>, the screen is converted into the layout as illustrated in <FIG>.

<FIG> illustrates an example of a process of performing a payment through card selection. 8000a illustrates the card list screen <NUM>. When the user touches (T) the card information <NUM> in the card list screen <NUM>, the detailed information screen <NUM> for a selected card, that is, a representative card is displayed as illustrated in 8000b. A front image <NUM> of the card, card benefit information <NUM>, selection menus <NUM> and <NUM>, and the like may be displayed in the detailed information screen <NUM>. A bar code <NUM> including card information, and the like may be displayed in the card benefit information <NUM>. Thus, the payment may be performed using the mobile device in a PoS including a bar code reader.

When the user selects the pay menu <NUM> in the detailed information screen <NUM>, the detailed information screen <NUM> is converted into a personal identification number (PIN) input screen <NUM> as illustrated in 8000c. An input region <NUM>, a key pad <NUM>, selection menus <NUM> and <NUM>, and the like may be displayed in the PIN input screen <NUM>. When the user inputs a correct passcode through the key pad <NUM>, the mobile device transmits payment information to the external apparatus and performs the payment.

When the items <NUM>, <NUM>, <NUM>, and <NUM> are selected on the card list screen, the lists for the cards registered in the corresponding items may be displayed.

<FIG> illustrates an example of screen conversion when an item is selected on the card list screen. When the credit card item <NUM> is selected in the card list screen <NUM> as illustrated in 9000a, the controller <NUM> displays a credit card list <NUM> using information for the credit cards of the user registered in the storage unit <NUM> or an external server apparatus as illustrated in 9000b. Various pieces of card information <NUM> to <NUM> and pay buttons <NUM> to <NUM> for the respective cards are displayed in the list <NUM>. Only the pay buttons <NUM> to <NUM> for the credit cards may be displayed.

When a portion of the credit card item <NUM> is touched (T) in the list <NUM>, the controller <NUM> may convert the credit card screen <NUM> into the screen as illustrated in 9000a again and display the converted screen. When the user uses other credit cards other than the credit cards most frequently used, the user may select the payment option in a state in which the list is displayed as illustrated in 9000b. In the top of the list as illustrated in 9000b, a card designated to a default card by the user or most frequently used, that is, a representative card is displayed. The user may perform long tapping or touching and dragging on one card on the list <NUM> to change a location of the card or to delete the card from the list <NUM>. Further, when a large number of cards which may not be displayed in one screen are registered, the user may perform scrolling on the card list screen in a vertical direction.

<FIG> illustrates an example in which an ID card is selected. When the ID card information <NUM> displayed below the ID card item 621in 10000a is selected, the controller <NUM> displays a detailed information screen <NUM> for the selected ID card. An ID card image <NUM>, detailed information <NUM> including a bar code and the like, an OK button <NUM>, and the like may be displayed in the detailed information screen <NUM>. When the OK button is selected, the screen <NUM> may be converted into the screen as illustrated in 10000b.

<FIG> illustrates an example in which a point card is selected. When the point card information <NUM> is selected in 11000a, the controller <NUM> displays detailed information screen <NUM> for a representative point card as illustrated in 11000b. A representative point card image <NUM>, detailed information <NUM>, selection menus <NUM> and <NUM>, and the like are displayed in the detailed information screen <NUM>. When a use it menu <NUM> of the selection menus is selected, the controller <NUM> applies benefits of the corresponding point card and performs a payment process. For example, when a free coupon or a discount coupon is used, the payment for an amount reduced by the amount stated in the coupon is progressed. 11000c illustrates an example that the point card is applied. When the use it menu is selected in the detailed information screen <NUM>, a mark <NUM> indicating that the coupon has been used is displayed in the card image <NUM> and a mark such as the bar code is deleted from the detailed information <NUM> not to be used any longer. The selection menu is changed to an OK button <NUM>. When the user selects the OK button <NUM> or when a preset period of time (for example, <NUM> seconds) is elapsed, the controller <NUM> displays the card list screen <NUM> as illustrated in 11000a again. When the representative point card has been used, a point card at a top among the unused point cards may be disposed in the point card information <NUM> of the card list screen <NUM>.

Even when the ticket information <NUM> is selected, the payment is processed in a similar manner to the point card and thus illustration and description thereof will be omitted.

Various examples of selecting a payment option have been described. Hereinafter, various examples for a method of proceeding the payment will be described in more detail.

In the state in which the wallet application is automatically executed, the user performs tagging on a host apparatus such as a PoS terminal or access to the host apparatus in a wireless communication manner to proceed the payment. When information for an amount to be paid is transmitted from the PoS terminal by the tagging or wireless communication, the controller <NUM> executes the wallet application to immediately display a payment screen in which the payment amount is displayed. When the pay button in the screen as illustrated in <FIG> or <FIG> is selected, the controller <NUM> may display the payment screen together with the information for the selected credit card. <FIG> illustrates an example of the payment screen in which the payment amount is displayed.

Referring to <FIG>, headline information <NUM>, various kinds of card information <NUM> and <NUM>, selection menus <NUM> and <NUM>, and the like may displayed in a payment screen <NUM>.

Information <NUM> for the selected credit card, an icon <NUM> for changing a card, information such as a requested payment amount <NUM>, and the like may be displayed in the headline information <NUM>. A credit card image <NUM>, a coupon image <NUM>, and the like may be included in the card information. The credit card image <NUM> may be an image corresponding to the credit card displayed in the headline information <NUM>. Icons <NUM>, <NUM>, <NUM>, and <NUM> for conversion into another card and the like may be displayed at both sides of each of the images <NUM> and <NUM>.

A credit card, coupon, point card or the like initially displayed in the payment screen as illustrated in <FIG> may be automatically selected and recommended by the controller <NUM>. That is, by considering a payment detail and a payment time of the user, a shop requesting the payment, an item to be paid, and the like, a card which may provide the greatest benefit, a card having the largest remaining credit limit, a card in which the user's preference is highest, or the like may be selected. The controller <NUM> may display the selected card at the top of the list as a representative card. Even in the case of a coupon, the controller <NUM> may select and display the coupon in the similar manner to the above-described method. When a plurality of coupons are searched, the controller <NUM> may change the benefits of the coupons to amounts and recommend a coupon which provides the greatest benefit or recommend a coupon having the smallest remaining expiration data.

When the user selects an OK menu <NUM> in the screen as illustrated in <FIG>, the screen <NUM> may be converted into an authorization screen for payment. The authorization screen may be implemented with a PIN input screen as illustrated in <FIG>, but the authorization screen is not limited thereto. That is, various authorization screens may be provided according to setting of the user.

<FIG> and <FIG> illustrate various examples of authorization screens.

Referring to <FIG>, information <NUM> for an amount to be paid, an input region <NUM> to which the user's signature is input, selection menus <NUM> and <NUM>, and the like may be displayed in an authorization screen <NUM>. When the user selects an encryption type as a signature in a setting screen, the authorization screen <NUM> as illustrated in <FIG> may be provided.

<FIG> illustrates another example of an authorization screen. Referring to <FIG>, information <NUM> for an amount to be paid, a pattern input region <NUM> to which the user inputs a pattern, selection menus <NUM> and <NUM>, and the like may be displayed in an authorization screen <NUM>. When the user selects an encryption type as a pattern in the setting screen, the authorization screen <NUM> as illustrated in <FIG> may be provided.

In addition, the wallet application may generate the screen using information for a transaction statement or an electronic receipt.

<FIG> illustrates an example of a list screen for an electronic receipt. Referring to <FIG>, details <NUM>, <NUM>, and <NUM> paid using an electronic application are arranged and displayed in a list form in a list screen <NUM>. The list screen as illustrated in <FIG> may be displayed when the bills menu <NUM> is selected in the payment home screen <NUM> as illustrated in <FIG> or other screens.

<FIG> illustrates a screen when one electronic receipt is selected in an electronic receipt list screen. Referring to <FIG>, when one electronic receipt is selected, a detailed information screen <NUM> for the selected receipt is displayed. Specifically, a payment amount, a company name, a payment data, purchase detail, and selection menus <NUM> and <NUM> are displayed. Among the selection menus, a split menu <NUM> is a menu for requesting payment exclusive charge or payment sharing to other users based on the payment amount and an OK menu <NUM> is a menu for terminating the wallet application after the receipt is stored. In addition, a share menu for sharing the payment detail, a list menu for viewing a receipt list, and the like may be further displayed.

<FIG> illustrates an example of a wish list generated by the user. The wallet application as illustrated in <FIG> may also manage information for the wish list. The wish list is a list in which the user has registered interested goods. Referring to <FIG>, various selection menus <NUM>, <NUM>, and <NUM> and the like are displayed in a wish list screen <NUM> together with goods information <NUM> and <NUM> including images, names, and prices of goods. When one piece of goods information is selected in <FIG>, the controller <NUM> may displays detailed information for the selected goods.

When the user selects a shopping path menu <NUM> in the screen as illustrated in <FIG>, the controller <NUM> displays a path guide screen <NUM> configured to display locations of shops which sale the goods registered in the wish list on a map.

<FIG> illustrates an example of the path guide screen <NUM>. <FIG> illustrates that two pieces of path guide information <NUM> and <NUM> for two goods are provided. When one of the two pieces of path guide information is selected, the selected information may be expanded and displayed.

As described above, the wallet application may provide various screens according to managing information. As in the exemplary embodiments described in <FIG> and <FIG>, when the wallet application is immediately executed by the user's gesture in a disabled state of the mobile device, an execution screen of the wallet application initially displayed may be one of the above-described various screens. That is, the payment home screen <NUM> may be initially displayed or the card list screen <NUM> may be initially displayed. Alternatively, the authorization screen for user authorization may be initially displayed. <FIG> is a view explaining a payment process when the authorization screen is first displayed.

Referring to 19000a, when a user operation in which the user touches two points T1 and T2 on a surface of the display unit <NUM> of the mobile device using two fingers and simultaneously moves two fingers outward from the touched points, that is, interaction is performed, an authorization screen <NUM> as illustrated in 19000b is displayed. An input region <NUM> and a key pad region <NUM> may be displayed in the authorization screen <NUM>. When the user inputs a correct passcode, the controller <NUM> displays a card list screen <NUM> as illustrated in 19000c. The card list screen <NUM> illustrated in 19000c is the same as the screen of <FIG> and thus, repeated description thereof will be omitted. The user may perform tagging on the mobile device to a PoS terminal in a state in which the screen as illustrated in 19000c is displayed. In this case, the representative card information <NUM> may be provided to the PoS terminal by a NFC module provided in the communication unit <NUM>. Therefore, the payment is done. On the other hand, when the user selects an application execution termination button or when the user does not perform payment for a certain period of time, a notification message <NUM> as illustrated in 19000d may be displayed. The user may arbitrarily select menus <NUM> and <NUM> displayed in the notification message <NUM> and select whether or not the wallet application is terminated. When the wallet application is terminated, the controller <NUM> converts the mobile device into a disabled state again. That is, the controller converts the mobile device into a lock state and causes the display unit <NUM> to be off.

The wallet application has to be not executed in the disabled state by the user operation. That is, when an icon for the wallet application is selected in a main screen or an icon display screen of the mobile device, the wallet application may be executed. <FIG> illustrates an operation for this case.

As illustrated in 20000a, various icons may be displayed in a main screen <NUM>. When an icon <NUM> corresponding to the wallet application among the icons is selected, an authorization screen <NUM> is displayed as illustrated in 20000b. When the user inputs a passcode using an input region <NUM> and a key pad <NUM>, a payment home screen <NUM> is displayed as illustrated in 20000c. The payment home screen <NUM> has been described in <FIG> and thus, repeated description thereof will be omitted. Like the example of <FIG>, when the user select the application execution termination button in the payment home screen <NUM> or when the user does not perform an operation for a certain period of time, a notification message <NUM> as illustrated in 20000d may be displayed. Various selection menus <NUM> and <NUM> may be displayed in the notification message <NUM>. When the user selects a Yes menu <NUM>, execution of the wallet application is terminated and is restored to an original state as illustrated in 20000a. On the other hand, when the user selects a No menu <NUM>, the screen as illustrated in 20000c is maintained.

The user may arbitrarily set an option with respect to an operation of the wallet application.

<FIG> illustrates an example of a setting screen for setting an option of the wallet application. Referring to <FIG>, a region <NUM> for selecting a payment mode and a region for selecting an authorization method may be displayed in a setting screen <NUM>.

The payment mode may include an automatic mode <NUM> and a manual mode <NUM>. The automatic mode <NUM> may be a mode in which a payment is automatically performed without a credit card and the manual mode <NUM> is a mode in which the credit card has to be selected before the payment. Further, there are a PIN code <NUM>, a signature <NUM>, a pattern input <NUM>, and the like as the authorization method. The user may select a desired option to use the wallet application. Data set by the user through the setting screen <NUM> is stored in the storage unit <NUM>. Therefore, the data may be used in the subsequent execution of the wallet application.

<FIG> is a flowchart specifically illustrating a payment method according to another exemplary embodiment. Referring to <FIG>, the mobile device <NUM> may sense a user operation even in a screen off state of the display unit <NUM> or a locked state of the display state <NUM> (S2210). When the user operation is sensed, the mobile device determines whether or not the sensed user operation is a preset gesture (S2215). When it is determined that the sensed user operation is the preset gesture, the mobile device immediately enables the display unit and automatically executes the wallet application (S2220). Subsequently, the mobile device displays set card information in an execution screen of the wallet application (S2240).

On the other hand, when it is determined that the sensed user operation is not the preset gesture but an operation for performing an unlock operation (S2225), the mobile device performs an unlock operation (S2230) and displays a main screen. When a wallet application icon is selected in the main screen (S2235), the mobile device executes the wallet application (S2220) and display card information (S2240).

In this state, when the user performs tagging on an external apparatus (for example, a PoS terminal) (S2245), the mobile device determines whether or not a transaction amount is small (S2250). A determination criterion amount may be determined according to a financial policy. For example, when the criterion amount is <NUM> thousand won, an amount of below <NUM> thousand won may be determined as a small amount. When it is determined that the transaction amount is small, the mobile device immediately perform the payment and displays payment completion. That is, in the first tagging process, the mobile device may check the amount and immediately transmit payment information. The transmitted payment information may be card information displayed in the execution screen of the wallet application.

On the other hand, when it is determined that the transaction amount is not small, the mobile device displays a PIN input screen (S2255). Amount information acquired from the external apparatus in the tagging process may be also displayed in the displayed PIN input screen.

When the tagging operation is not performed in S2245 and a pay execution button is selected in the execution screen of the wallet application (S2260), a PIN input screen not including the payment amount is displayed (S2265).

When the PIN input is completed in the PIN input screen in S2255 or S2265 (S2270), the mobile device checks whether or not the input PIN is identical with preregistered information (S2275). When it is determined that the input PIN is identical with the preregistered information, a message which guides the user to perform tagging on the PoS terminal may be displayed (SS2285). Thus, when the user performs the tagging on the mobile device to the PoS (S2290), the payment is done and a payment completion message is displayed (S2295). When it is determined that the PIN information is not identical with the preset information in S2275, the PIN input screen is displayed again (S2280). At this time, the number of errors may be also displayed and when the PIN input is failed more than the predetermined number, the wallet application may be forcibly terminated.

Assuming that authorization is performed using the PIN and payment is performed in an NFC manner in <FIG>, the payment method has been described. However, as described above, the authorization and payment method is not limited thereto.

<FIG> is a view explaining a process of performing payment through tagging with the PoS terminal. When the user input a predetermined gesture in the mobile device <NUM> and then performs tagging on a PoS terminal <NUM> to the mobile device <NUM> as illustrated in 23000a, an authorization screen <NUM> is displayed as illustrated in 23000b. When the user input a PIN in the authorization screen <NUM> and then selects a payment menu <NUM>, a screen <NUM> which guides PoS contact is displayed as illustrated in FIG. Information for a payment option, an image of the PoS terminal, a guide phrase, a payment amount, and the like may be displayed in the screen <NUM>.

Accordingly, tagging is performed again as illustrated in 23000d, the payment is done and an electronic receipt <NUM> is issued and displayed as illustrated in 23000e. A payment amount, a company, and a payment detail, and the like may be displayed in the electronic receipt <NUM> and a menu <NUM> for requesting to split the amount to other users, an OK menu <NUM>, and the like may be displayed. When the OK menu is selected in FIG. 23000e or when a preset critical period of time is elapsed without input, the screen is restored to the screen before the Pos terminal contact.

<FIG> illustrates an example of an error message displayed when an incorrect passcode is entered. Referring to <FIG>, an authorization cancel menu <NUM>, a retry menu <NUM>, or the like may be further displayed in an error message <NUM> in addition to the number of incorrect input and a guide phrase. When the authorization cancel menu <NUM> is selected, the payment process may be terminated.

<FIG> illustrates an example of a payment completion message displayed when the payment is completed. When the payment is completed, an electronic receipt as illustrated in 23000e may be displayed or a payment completion message <NUM> as illustrated in <FIG> may be displayed. A payment relevant simple guide phrase may be displayed in the payment completion message <NUM>.

As described above, in the mobile device, the preset user operation is input and the wallet application is immediately executed and used. According to other exemplary embodiments, the user's fingerprint may be recognized to reinforce security of the wallet application.

<FIG> illustrates a configuration of a mobile device according to another exemplary embodiment. Referring to 26000a, a mobile device <NUM> may further include a fingerprint sensor <NUM>. The fingerprint sensor <NUM> may sense a user's fingerprint.

The controller <NUM> determines whether or not the fingerprint sensed in the fingerprint sensor <NUM> matches a user's preregistered fingerprint. Further, the controller <NUM> determines whether or not the user's touch operation performed together with the sensing of the fingerprint matches the preset gesture information. When it is determined that the user's touch operation matched with the gesture information and the user's fingerprint matched with the preregistered fingerprint information are sensed, the controller <NUM> immediately enables the display unit <NUM> and execute the wallet application.

26000b illustrates that a gesture, in which the user inputs his/her fingerprint in the fingerprint sensor <NUM> and at this state, the user moves a finger <NUM> to a direction of the display unit <NUM> (that is, a Z direction), is input. The controller <NUM> determines that the user's predetermined operation is done when the touch is continuously done from a boundary of the display unit <NUM> above the fingerprint sensor <NUM> to a fixed height within a certain period of time after the preregistered fingerprint is recognized. According to this, the controller <NUM> enables the display unit <NUM> and automatically executes the wallet application.

<FIG> illustrates another example of a mobile device including a fingerprint sensor. Referring to FIG. <NUM>(a), a plurality of fingerprint units <NUM> and <NUM> are disposed at both sides of a display unit <NUM>. Each of the fingerprint sensors <NUM> and <NUM> has a thin bar shape. Thus, when two fingers of the user pass through the fingerprint sensors <NUM> and <NUM>, the fingerprint may be recognized.

27000b illustrates that a gesture, in which two fingers touches two points on a surface of the display unit <NUM> and then moves to an X- direction and an X+ direction respectively and passes through the fingerprint sensors <NUM> and <NUM>, is input. The fingerprint sensors <NUM> and <NUM> sense the fingerprints when the user's fingers pass through the fingerprint sensors <NUM> and <NUM> and provide sensed fingerprints to the controller <NUM>. The controller <NUM> compares the provided fingerprints and fingerprints stored in the storage unit <NUM>. The controller <NUM> determines that an execution condition of the wallet application is satisfied when a touch trajectory sensed in the sensor <NUM> matches the preset gesture information and the fingerprints sensed in the fingerprint sensors <NUM> and <NUM> are matched with the registered fingerprints.

The fingerprint recognition may be performed through various methods. Specifically, as the fingerprint recognition method, there are a method using a semiconductor chip and a method using an optical unit.

The method using a semiconductor chip is a method of sensing a shape of a fingerprint using an electric conduction characteristic of a skin. That is, the method is a method of reading change in an amount of charges sensed by a sensor array and obtaining fingerprint information according to pressure of the fingers placed on a chip surface of a silicon chip and a heat image when fingertips come in direct contact with the surface of the silicon chip. The method using a semiconductor chip may be applied to the fingerprint sensors <NUM> having the structure of <FIG>.

The method using an optical unit is a method of emitting light, receiving the light reflected from a surface of a finger, and sensing characteristic of the finger surface.

<FIG> illustrates a fingerprint sensor implemented with the method using an optical unit. Referring to <FIG>, the fingerprint sensor includes a glass plate <NUM>, a light source <NUM>, a lens <NUM>, and a light-receiving unit <NUM>.

The light source <NUM> emits light to the glass plate <NUM> and thus the light from a finger <NUM> placed on the glass plate <NUM> is reflected. The reflected light is incident to the light-receiving unit <NUM> through the lens <NUM>. The light-receiving unit <NUM> may include an image sensor such as a charge coupled device (CCD). The finger image sensed in light-receiving unit <NUM> may be analyzed and a fingerprint may be recognized. For clarity, <FIG> illustrates that the light source <NUM> and the light-receiving unit <NUM> are spaced apart from the glass plate <NUM> to be tilted at a certain angle. However, a distance between the light source <NUM> and the glass plate <NUM> and between the light-receiving unit <NUM> and the glass plate <NUM> may be implemented to be close according to a thickness of the mobile device <NUM>. Further, the light source <NUM> and the light-receiving unit <NUM> may be vertically disposed below the glass plate <NUM> with respect to the glass plate <NUM>.

The number of fingerprint sensors and a size and arrangement location of the fingerprint sensor may be implemented in various structures other than structures illustrated in <FIG> and <FIG>.

<FIG> is a block diagram integrally explaining a configuration of a mobile device according to various exemplary embodiments. Referring to <FIG>, a mobile device <NUM> includes a global positioning system (GPS) chip <NUM>, a digital multimedia broadcasting (DMB) receiver <NUM>, a motion sensor <NUM>, an audio processor <NUM>, a video processor <NUM>, a speaker <NUM>, a button <NUM>, a capturing unit <NUM>, and a microphone <NUM> in addition to a display unit <NUM>, a sensor <NUM>, a controller <NUM>, a storage unit <NUM>, and a communication unit <NUM>.

The controller <NUM> may control an overall operation of a user terminal apparatus using a program stored in the storage unit <NUM>. Specifically, the controller may sense a user operation done on a surface of the display unit <NUM>. According to this, the controller may execute an application corresponding to the user operation. The wallet application may be matched with a specific gesture as in the above-described exemplary embodiments, but this is not limited thereto. For example, various applications such as a mail application or a call application may be matched in addition to the wallet application. Further, only one user gesture does not have to be set. For example, a plurality of user gestures may be set and the user gestures may be matched with applications different from each other.

The controller <NUM> may include a random access memory (RAM) <NUM>, a read only memory (ROM), a min central processing unit (CPU) <NUM>, a graphic processing unit (GPU) <NUM>, a bus <NUM>, and the like. The RAM <NUM>, ROM <NUM>, main CPU <NUM>, GPU <NUM>, and the like may be connected to each other through the bus <NUM>. Various interfaces may be further included, but illustration and description thereof will be omitted.

The main CPU <NUM> access to the storage unit <NUM> and performs booting using operating system (OS) stored in the storage unit <NUM>. A command set for system booting and the like may be stored in the ROM <NUM>. When a turn-on command is input and power is supplied, the main CPU copies the OS stored in the storage unit <NUM> to the RAM <NUM> according to a command stored in the ROM <NUM> and executes the OS to boot the system. When the booting is completed, the main CPU <NUM> copies various types of programs stored in the storage unit <NUM> to the RAM <NUM> and executes the programs copied to the RAM <NUM> to perform various types of operations. When an application set to default exists, if the booting is completed, the main CPU <NUM> may automatically execute the programs. The main CPU <NUM> may monitor a sense signal output from the sensor <NUM> and determine whether or not a wallet application is executed. When it is determined that an execution condition of the wallet application is satisfied, the main CPU <NUM> loads the wallet application from the storage unit <NUM> to the RAM <NUM>. The loaded wallet application controls respective components in the mobile device <NUM> and performs operations according to the above-described various exemplary embodiments.

The GPU <NUM> generates various types of screens. Specifically, the GPU may perform rendering on a wallet screen based on information for various types of payment options stored in the stored in the storage unit <NUM> when the wallet application is executed.

The communication unit is configured to perform communication with various kinds of external apparatuses according to various types of communication methods. The communication unit <NUM> includes a Wi-Fi chip <NUM>, a Bluetooth chip <NUM>, a near field communication (NFC) chip <NUM>, a wireless communication chip <NUM>, and the like.

Among the chips, the NFC chip <NUM> is a chip configured to perform NFC communication. The NFC is a non-contact short-range wireless communication method using a frequency bandwidth of <NUM>. When NFC technology is used, if a plurality of terminals approach each other within a short range of about <NUM>, data may be transmitted and received. Tagging is performed to perform the short-range communication. The tagging is a behavior in which an apparatus including a NFC tag and any one of apparatuses including NFC readers approach each other toward the counterpart and located within a communicable range in which the NFC may be performed. The NFC chip <NUM> may include only NFC tag, but the NFC chip <NUM> may be implemented with one module in which the NFC tag and the NFC reader integrated.

The wireless communication chip <NUM> denotes a chip configured to perform communication according to various communication standards such as Institute of Electrical and Electronic Engineers (IEEE), Zigbee, third generation (<NUM>), third generation partnership project (3RPP), and long term evolution (LTE). The communication unit <NUM> may include at least one among the above-described chips or chips according to other communication standards and perform communication with various external apparatuses using the chips.

The GPS chip <NUM> is configured to receive a GPS signal from a GPS satellite and calculate a current location of the mobile device <NUM>.

The DMB receiver <NUM> is configured to receive and process a DMB signal.

The sensor <NUM> is configured to sense touch on a surface of the display unit <NUM>. The controller <NUM> may compares a coordinate value of each object displayed in a displayed screen and a touch coordinate value of the sensor <NUM> and determines whether which object is selected.

The motion sensor <NUM> is configured to sense a motion such as a rotation state of the mobile device <NUM> using a gyro senor, a geomagnetic sensor, an acceleration sensor, and the like. The controller <NUM> may perform various control operations according to a motion sensed by the motion sensor <NUM> in addition to a touch operation sensed by the sensor <NUM>.

The audio processor <NUM> is configured to perform processing on audio data included in contents. Various processing such as decoding and amplification for the audio data or noise filtering may be performed in the audio processor <NUM>.

The video processor <NUM> is configured to perform processing on video data included in the contents. Various processing such as decoding for the video data, scaling, noise filtering, frame rate conversion, and resolution conversion may be performed in the video processor <NUM>.

The audio processor <NUM> and the video processor <NUM> may be driven when a program for reproducing contents received from an external source or the contents stored in the storage unit <NUM> is executed.

The display unit <NUM> may display an image frame generated in the video processor <NUM> as well as various screens on which the GPU <NUM> performed rendering. The speaker <NUM> output audio data generated in the audio processor <NUM>.

The button <NUM> may be provided in a body of the mobile device <NUM> in various types such as a home button, a push button, a touch button, or a wheel button.

The capturing unit <NUM> is configured to perform a capturing operation. The controller <NUM> may select an image corresponding to an electronic receipt among images captured in the capturing unit <NUM>, attach the image to the electronic receipt, and store the image-attached electronic receipt in the storage unit <NUM>.

The microphone <NUM> is configured to receive user's voice or other sound and convert the user's voice or the sound into audio data. The controller <NUM> may use the user's voice input through the microphone <NUM> in a call process or converts the user's voice into audio data and stores a conversion result.

The above-described exemplary embodiments has described that the application is automatically executed only by the touch gesture on the surface of the display unit <NUM>, but the application may be automatically performed by other types of user operations. For example, the controller <NUM> may immediately execute a matched application even through a motion gesture of a user recognized using the capturing unit <NUM> or speech input through the microphone <NUM>.

<FIG> integrally illustrates mountable various components when the mobile device <NUM> integrally supports various functions such as a communication function, a DMB function, and a GPS reception function. Therefore, in some embodiments, a portion of the components illustrated in <FIG> may be omitted or changed or other components may be further added to the mobile device.

<FIG> illustrates an example of a software hierarchic structure of a mobile device. Referring to <FIG>, the mobile device <NUM> may include various software such as an OS <NUM>, a frame work <NUM>, a call application <NUM>, a wallet application <NUM>, a browser <NUM>, and a phone book application <NUM> as well as a hardware <NUM>.

The hard ware <NUM> denotes various types of hardware illustrated in <FIG>. The OS <NUM> may control an overall operation of the hardware <NUM> and mange functions of the hardware <NUM>. That is, the OS <NUM> is a hierarchy which is in charge of a basic function such as hardware management, memory, and security. The OS <NUM> may drive a display driver configured to drive the display unit <NUM>, a communication driver configured to enable the communication unit <NUM> to transmit/receive signals, a camera driver configured to drive the capturing unit, an audio driver configured to drive the audio processor <NUM>, modules of a power manager and the like to control the operation of the mobile device <NUM>.

The frame work hierarchy <NUM> exists in an upper hierarchy of the OS <NUM>. The framework hierarchy <NUM> performs functions for connecting respective application programs <NUM> to <NUM> of an application hierarchy to the OS hierarchy <NUM>. For example, the frame work hierarchy <NUM> includes a location manager, a notification manager, a frame buffer configured to display an image to the display unit, and the like.

The application hierarchy configured to implement various functions exists in an upper hierarchy of the frame work hierarchy <NUM>. The wallet application <NUM> exists in the application hierarchy. The wallet application <NUM> may provide various shopping services using various pieces of information as illustrated in <FIG>.

According to the above-described exemplary embodiments, shopping services may be used conveniently easily using a user terminal apparatus. In particular, the payment may be rapidly performed using the wallet application. In this disclosure, the application is called the wallet application, but the name of the application performing the above-described operation may be variously determined. Further, the exemplary embodiments have described that the payment application is automatically executed by a user gesture in a disabled state of the display unit, but this is not limited thereto. That, even in an enable state of the mobile device <NUM>, when the predetermined user gesture is input, the payment application may be executed.

The above-described payment methods according to the exemplary embodiments may be implemented with a program which is performed through various computer devices and then recorded in various non-transitory computer-readable media.

Specifically, the non-transitory computer-recordable medium, in which the program which provides the shopping service by sequentially performing of sensing user's touch done on a surface of a display unit of a mobile device in a disabled state of the display unit of the mobile device; enabling the display unit when a user's touch operation matched with preset gesture information, executing a wallet application, and display an execution screen; and transmitting information for a selected payment option to an external apparatus when the payment option is selected on the execution screen and performing a payment is recorded, may be mounted on the user terminal apparatus.

The non-transitory computer-recordable medium, in which a program which implements the methods of providing service according to the above-described exemplary embodiments is recorded, may be mounted on a host apparatus or a server.

The non-transitory computer-recordable medium may be connected to or mounted on the above-described various types of mobile devices and support to execute the methods in the corresponding devices.

The non-transitory computer-recordable medium is not a medium configured to temporarily store data such as a register, a cache, a memory, and the like but an apparatus-readable medium configured to semi-permanently store data. Specifically, the above-described applications or programs may be stored and provided in the non-transitory computer-recordable medium such as a compact disc (CD), a digital versatile disc (DVD), a hard disc (HD), a blu-ray disc, a USB, a memory card, a read only memory (ROM), and the like.

Claim 1:
A mobile device (<NUM>) comprising:
a fingerprint sensor (<NUM>);
a touch screen (<NUM>); and
a processor (<NUM>) configured to:
in response to receiving a first user input while at least one of a lock screen or a black screen is displayed on the touch screen, compare the received first user input with gesture information stored in the mobile device and compare a fingerprint sensed by the fingerprint sensor with a predetermined fingerprint information stored in the mobile device,
based on the first user input matching the gesture information and the fingerprint matching the predetermined fingerprint information, execute a payment application corresponding to the received first user input, and
based on receiving a second user input for requesting to make a payment, transmit, to an external apparatus, information for making the payment while executing the payment application.