Patent Description:
With advancement in data processing technique and network technique, a user may pay for an item and a service by using various devices. In particular, a user who uses a vehicle may enter an offline store while driving the vehicle and is thus likely to pay for an item or a service provided in the offline store while riding in the vehicle. Thus, there is a growing need for a user who uses a vehicle to perform a transaction in an easy and safe manner by using a vehicle terminal and/or a mobile device. Patent document <CIT>, discloses an automobile being equipped with a reader to be placed inside of the automobile, the reader being able to read purchasing instrument data of at least one of a contactless credit card or smart card-type credit card or NFC-enabled handset, and the reader being further connected to a wireless communication interface of the automobile, the wireless communication interface being able to transmit the purchasing instrument data to a point of sale. Patent document <CIT>, discloses a method for facilitating automatic payment in a payment system requires less interaction by both the credit card user and store clerks than current payment systems. Patent document <CIT>, discloses systems and methods for processing electronic payments for retail services and goods delivered by a retail establishment. Patent document <CIT>, discloses how to leverage technology in a vehicle to provide various services in a convenient manner.

According to an aspect of exemplary embodiments, a transaction system and a method capable of paying for an item on the basis of a license plate number are provided.

Exemplary embodiments provide a transaction system and a method capable of enabling a payment server to pay for an item provided in an offline store by using a license plate number provided to a mobile device via a vehicle terminal of a vehicle.

Exemplary embodiments provide a transaction system and a method capable of paying for an item without providing credit card information to a store terminal of an offline store.

These and/or other aspects will become more apparent and more readily appreciated from the following description of exemplary embodiments, taken in conjunction with the accompanying drawings. Understanding that these drawings depict only exemplary embodiments and are not therefore to be considered to be limiting of the scope of the disclosure, the principles herein are described and explained with additional specificity and detail through the use of the accompanying drawings, in which:.

Additional aspects of exemplary embodiment will be set forth in part in the description which follows and, in part, will be apparent from the description, or may be learned by practice of exemplary embodiments.

Exemplary embodiments will be described in detail with reference to the accompanying drawings below so that one of ordinary skill in the art can easily implement the present disclosure. However, the present disclosure may be embodied in many different forms and is not limited thereto. For clarity, parts of exemplary embodiments which are not related to describing the exemplary embodiments are omitted in the drawings, and same reference numerals are allocated to the same or analogues elements through.

As used herein, it will be understood that when an element is referred to as being "connected to" another element, the element can be directly connected to another element or can be electrically connected to another element while having intervening elements therebetween. It will be further understood that when an element is referred to as "including" another element, the element should be understood to further include other elements unless mentioned otherwise.

As used herein, the term 'and/or' includes any and all combinations of one or more of the associated listed items. Expressions such as 'at least one of,' when preceding a list of elements, modify the entire list of elements and do not modify the individual elements of the list.

Exemplary embodiments will be described in detail with reference to the accompanying drawings.

<FIG> is a diagram schematically illustrating an item payment system using a license plate number, according to an exemplary embodiment.

Referring to <FIG>, the item payment system according to an exemplary embodiment may include at least one mobile device <NUM>, a vehicle <NUM>, a vehicle terminal <NUM>, a store terminal <NUM>, and a payment server <NUM>.

The store terminal <NUM> may be a terminal located in an offline store. A user who is in the vehicle <NUM> may request the payment server <NUM> to pay for an item provided in the offline store by manipulating the vehicle terminal <NUM> or the mobile device <NUM>.

A license plate number of the vehicle <NUM> may be registered in the vehicle terminal <NUM>. The vehicle terminal <NUM> or the mobile device <NUM> may transmit a payment request including the license plate number to the payment server <NUM> so that the payment server <NUM> may authenticate the payment of the item which the user desires to purchase on the basis of the license plate number. Furthermore, the vehicle terminal <NUM> or the mobile device <NUM> may provide the license plate number to the store terminal <NUM>, and the store terminal <NUM> may transmit the license plate number to the payment server <NUM> so as to request the payment server <NUM> to provide a result of the payment of the item.

In this case, the vehicle terminal <NUM> or the mobile device <NUM> may provide the store terminal <NUM> with the license plate number and purchasing item information regarding the item which the user desires to purchase but exemplary embodiments are not limited thereto. The store terminal <NUM> may obtain a license plate number by photographing the license plate number of the vehicle <NUM> by using a camera <NUM> installed in the offline store. The store terminal <NUM> may obtain the purchasing item information regarding the item which the user desires to purchase from a store clerk on the basis of a user input. The purchasing item information may include, for example, an identification (ID) value and a price (e.g., a settlement or total cost) of the item which the user desires to purchase but is not limited thereto.

The mobile device <NUM> may be, but is not limited to, a smart phone, a tablet personal computer (PC), a cellular phone, a personal digital assistant (PDA), a laptop computer, a media player, a global positioning system (GPS) device, an e-book terminal, an MP3 player, a digital camera, or another mobile computing device. Otherwise, the mobile device <NUM> may be a wearable device, such as a watch, glasses, a hairband, a ring, or the like, which has a communication function and a data processing function.

The vehicle terminal <NUM> may be an electronic device installed in the vehicle <NUM>, and provide various services to a user by controlling various devices included in the vehicle <NUM> and communicating with another electronic device or a server. Various inner devices of the vehicle terminal <NUM> may be located at predetermined positions inside the vehicle <NUM>.

The store terminal <NUM> may be a point-of-sale (POS) terminal used to pay for an item in the offline store but is not limited thereto.

The payment server <NUM> may be a server authenticating payment and be operated by at least one operator. The payment server <NUM> may be one server operated by one operator but is not limited thereto. The payment server <NUM> may include a plurality of servers operated by a plurality of operators. For example, the payment server <NUM> may include a server which manages card information related to payment and handles the payment, and a server which authenticates the payment.

The mobile device <NUM>, the vehicle <NUM>, the vehicle terminal <NUM>, the store terminal <NUM>, and the payment server <NUM> illustrated in <FIG> may communicate with one another in at least one network. The at least one network should be understood to mean a comprehensive data communication network including a local area network (LAN), a wide area network (WAN), a value-added network (VAN), a mobile radio communication network, a satellite communication network, and a combination thereof, and enabling subjects of these networks as illustrated in <FIG> to smoothly communicate with one another. The at least one network may include a wire Internet, a wireless Internet, and a mobile wireless communication network. Examples of wireless communication may include, but are not limited to, Wi-Fi, Bluetooth, Bluetooth low energy, ZigBee, Wi-Fi direct (WFD), ultra-wide band (UWB), infrared data communication (IrDA), near-field communication (NFC), etc..

<FIG> is a diagram illustrating an example in which a mobile device <NUM> requests a payment server <NUM> to pay for an item by using a license plate number received from a vehicle terminal <NUM>, according to an exemplary embodiment.

Referring to <FIG>, when a vehicle <NUM> enters an offline store, the vehicle terminal <NUM> may display a list of items provided in the offline store, and request the payment server <NUM> via the mobile device <NUM> to pay for an item selected by a user from the list of items, thereby paying for the item.

The vehicle terminal <NUM> may provide the mobile device <NUM> with a license plate number and purchasing item information regarding an item which a user desires to purchase. The mobile device <NUM> may select a card stored therein and request the payment server <NUM> to pay for the item.

As the vehicle <NUM> enters the offline store, the store terminal <NUM> may obtain the license plate number by photographing a license plate of the vehicle <NUM> by using a camera <NUM>, and communicate with the vehicle terminal <NUM> located in the vehicle <NUM> to receive the purchasing item information regarding the item which the user desires to purchase and the license plate number from the vehicle terminal <NUM>. The store terminal <NUM> may compare the license plate number obtained by the camera <NUM> with the license plate number received from the vehicle terminal <NUM>, and request the payment server <NUM> to provide a result of paying for the item.

Alternatively, the store terminal <NUM> may obtain the license plate number by photographing the license plate number of the vehicle <NUM> by using the camera <NUM> installed at the offline store, and obtain from a store clerk the purchasing item information regarding the item which the user desires to purchase on the basis of a user input.

The payment server <NUM> may authenticate the payment of the item in response to the payment request received from the mobile device <NUM>. Furthermore, the payment server <NUM> may transmit a result of authenticating the payment to the store terminal <NUM> providing the license plate number which is identical to the license plate number received from the mobile device <NUM>.

<FIG> is a flowchart illustrating a method of providing data to be used to pay for an item, performed by the vehicle terminal <NUM>, according to an exemplary embodiment.

Referring to <FIG>, in operation S300, the vehicle terminal <NUM> may register a license plate number of the vehicle <NUM> therein. The vehicle terminal <NUM> may display a graphical user interface (GUI) on a screen thereof to register the license plate number, and register the license plate number input by a user therein through the GUI.

In operation S310, the vehicle terminal <NUM> may display item information regarding items provided in an offline store. The vehicle terminal <NUM> may receive the item information from the store terminal <NUM> located in the offline store and display the item information on the screen thereof. Alternatively, the vehicle terminal <NUM> may display the item information regarding the items provided in the offline store on the screen thereof by determining the location of the vehicle <NUM> and being connected to a web site of the offline store at the location. The item information may be information needed to purchase the items, and may include, for example, a list of the items, the prices of the items, discount information, coupon information, etc. but is not limited thereto. The vehicle terminal <NUM> may display the list of the items on the screen thereof, and receive a user input for selecting a desired item.

In operation S320, the vehicle terminal <NUM> may access the mobile device <NUM> at short range, i.e., by using short range communication methods such as Bluetooth. As the mobile device <NUM> approaches a range of communication of a short-distance communication module or short-distance communicator having circuitry for performing the communication, of the vehicle terminal <NUM>, communication may be established between the vehicle terminal <NUM> and the mobile device <NUM>. The short-distance communication module of the vehicle terminal <NUM> may be installed at a predetermined location in the vehicle <NUM>, e.g., near a steering handle of the vehicle <NUM>, but is not limited thereto.

In operation S330, the vehicle terminal <NUM> may transmit the license plate number and purchasing item information to the mobile device <NUM>. The vehicle terminal <NUM> may display received item information on the screen thereof and receive a user input for selecting a desired item. The vehicle terminal <NUM> may transmit the license plate number registered therein and purchasing item information regarding an item which a user desires to purchase to the mobile device <NUM> through short-distance communication. The purchasing item information may include, for example, the name of an item (or the names of items) which the user desires to purchase, images of the item(s), the price(s) of the item(s), discount information of the item(s), coupon information applicable to the item(s), etc., but is not limited thereto. The prices of the items may include, for example, the prices of the items and a total price of the items.

Thereafter, the mobile device <NUM> may authenticate the user who will pay for the item and provide the payment server <NUM> with the license plate number and the purchasing item information so as to request the payment server <NUM> to pay for the item. For example, the mobile device <NUM> may transmit the license plate number, a total cost for the purchase, and the coupon information to the payment server <NUM>.

<FIG> is a flowchart illustrating a method of requesting the payment server <NUM> to handle payment by using a license plate number, performed by the mobile device <NUM>, according to an exemplary embodiment.

Referring to <FIG>, in operation S400, the mobile device <NUM> may access the vehicle terminal <NUM> at short range. As the mobile device <NUM> approaches a range of communication of a short-distance communication module of the vehicle terminal <NUM>, communication may be established between the vehicle terminal <NUM> and the mobile device <NUM>.

In operation S410, the mobile device <NUM> may receive a license plate number from the vehicle terminal <NUM>. The mobile device <NUM> may receive the license plate number registered in the vehicle terminal <NUM> from the vehicle terminal <NUM> through short-distance communication.

In operation S420, the mobile device <NUM> may obtain purchasing item information regarding an item or items which a user desires to purchase. When the vehicle terminal <NUM> displays item information regarding items provided in an offline store on a screen thereof, the mobile device <NUM> may receive the item information regarding the item which the user desires to purchase from the vehicle terminal <NUM> through short-distance communication.

Alternatively, the mobile device <NUM> may be connected to a server (not shown) of the offline store, receive the item information regarding the items provided in the offline store from the server, and select the item which the user desires to purchase on the basis of a user input. In this case, for example, the mobile device <NUM> may be connected to a web site of the offline store on the basis of a location of the mobile device <NUM>, and may select the item which the user desires to purchase at the web site of the offline store.

In operation S430, the mobile device <NUM> may select a card to be used to pay for the item. The mobile device <NUM> may execute a payment application for paying for the item, and select one of credit cards registered therein by using the payment application.

Furthermore, the mobile device <NUM> may authenticate the user who will use the selected credit card. For example, the mobile device <NUM> may authenticate the user by using at least one among the user's bio-information, password, and authentication certificate but exemplary embodiments are not limited thereto.

In operation S440, the mobile device <NUM> may transmit the license plate number, the purchasing item information, and card information to the payment server <NUM>. When the user who will use the selected credit card is authenticated, the mobile device <NUM> may request the payment server <NUM> to pay for the item while providing the payment server <NUM> with the license plate number, the purchasing item information, and the card information. For example, the mobile device <NUM> may request the payment server <NUM> to pay for the item while providing the payment server <NUM> with the license plate number, a total cost of the purchase, and the card information.

Although it is described above that the mobile device <NUM> selects the credit card, exemplary embodiments are not limited thereto. For example, credit cards may be registered beforehand in the payment server <NUM> based on or corresponding to individual mobile devices <NUM>. In this case, the mobile device <NUM> may provide the payment server <NUM> with an ID value of the mobile device <NUM> or user ID instead of the card information, and the payment server <NUM> may then select a credit card corresponding to the ID value of the mobile device <NUM> or the user ID. The ID value may be a mobile identification number (MIN) or a mobile subscription identification number (MSIN), which are provided by way of an exemplary and not by way of a limitation.

<FIG> is a flow diagram illustrating a method of paying for an item, performed in an item payment system, in which a vehicle terminal <NUM> selects an item which a user desires to purchase and a mobile device <NUM> requests to pay for the item by using a license plate number received from the vehicle terminal <NUM>, according to an exemplary embodiment.

Referring to <FIG>, in operation S500, a store terminal <NUM> may obtain a license plate number of the vehicle <NUM>. When the vehicle <NUM> enters an offline store, the store terminal <NUM> may obtain a license plate number by photographing a license plate of the vehicle <NUM> by using the camera <NUM>. Alternatively, a clerk of the offline store may check the license plate number of the vehicle <NUM> and input the license plate number to the store terminal <NUM>. In this case, the store terminal <NUM> may obtain the license plate number on the basis of a user input indicating the license plate number. Alternatively, the store terminal <NUM> may receive the license plate number from the vehicle terminal <NUM> or the mobile device <NUM> located in the vehicle <NUM>. In this case, the vehicle terminal <NUM> or the mobile device <NUM> located in the vehicle <NUM> may broadcast the license plate number of the vehicle <NUM>.

In operation S505, the store terminal <NUM> may provide the vehicle terminal <NUM> with item information. As a communication module installed outside the vehicle <NUM> accesses a communication module of the store terminal <NUM> at short range, the store terminal <NUM> may transmit the item information to the vehicle terminal <NUM>. The item information is information regarding items provided in the offline store, and may include, for example, the names, prices, images, discount information, coupon information, etc. of the items but exemplary embodiment are not limited thereto.

In operation S510, the vehicle terminal <NUM> may display the item information on a screen thereof. The vehicle terminal <NUM> may execute an application for purchasing an item in the offline store when the vehicle <NUM> enters the offline store or when the item information is received from the store terminal <NUM>. Furthermore, the vehicle terminal <NUM> may display the item information on the screen by using the application. For example, the vehicle terminal <NUM> may display a GUI including a list of the items provided in the offline store.

In operation S515, the vehicle terminal <NUM> may select one or more items to be purchased. The vehicle terminal <NUM> may select an item which the user desires to purchase on the basis of a user input for selecting the item from the displayed list of the items. For example, the items may be selected using the selection keys of the vehicle terminal <NUM> such as buttons, touch screen, dials, and so on.

In operation S520, the vehicle terminal <NUM> may access the mobile device <NUM> at short range. As the mobile device <NUM> approaches a range of communication of a short-distance communication module of the vehicle terminal <NUM>, the vehicle terminal <NUM> and the mobile device <NUM> may be connected to each other through short-distance communication.

In operation S525, the vehicle terminal <NUM> may transmit the license plate number and purchasing item information to the mobile device <NUM>. The vehicle terminal <NUM> may transmit the license plate number registered therein and the purchasing item information regarding the item which the user desires to purchase to the mobile device <NUM> through short-distance communication. Although it is described above that, in operation S525, the license plate number is provided from the vehicle terminal <NUM> to the mobile device <NUM> when the mobile device <NUM> and the vehicle terminal <NUM> access each other at short range, the providing of the license plate number to the mobile device <NUM> is not limited thereto. For example, the mobile device <NUM> may register beforehand therein the license plate number of the vehicle <NUM>, as such only the purchasing item information is provided without the license plate number.

In operation S530, the mobile device <NUM> may execute a payment application for paying for the item. As the mobile device <NUM> accesses the vehicle terminal <NUM> at short range, the mobile device <NUM> may execute the payment application.

However, exemplary embodiments are not limited thereto, and the mobile device <NUM> may access the vehicle terminal <NUM> at short range after the mobile device <NUM> executes the payment application. Alternatively, after the payment application is executed, the mobile device <NUM> may receive the license plate number and the purchasing item information from the vehicle terminal <NUM>.

In operation S535, the mobile device <NUM> may select a card to be used to pay for the item. The mobile device <NUM> may display a list of credit cards registered therein, and determine a credit card to be used to pay for the item on the basis of a user input for selecting the credit card.

Furthermore, the mobile device <NUM> may recommend a credit card to be used to pay for the item on the basis of discount information or coupon information related to the item. The mobile device <NUM> may display a list of recommended credit cards, and determine a credit card to be used to pay for the item on the basis of a user input for selecting the credit card from the list of recommended credit cards.

In addition, the mobile device <NUM> may authenticate a user who will use the selected credit card. The mobile device <NUM> may receive, for example, the user's bio-information and/or password from the user, and authenticate the user on the basis of the bio-information and/or the password. Alternatively, the mobile device <NUM> may authenticate the user on the basis of an authentication certificate. In this case, the mobile device <NUM> may display a GUI for authenticating the user on a screen thereof.

In operation S540, the vehicle terminal <NUM> may provide the license plate number and the purchasing item information to the store terminal <NUM>. As an item to be purchased is selected by the vehicle terminal <NUM>, the vehicle terminal <NUM> may provide the store terminal <NUM> with purchasing item information regarding the selected item and the license plate number registered in the vehicle terminal <NUM>. The vehicle terminal <NUM> may provide the store terminal <NUM> with the license plate number and the purchasing item information through a communication module installed outside the vehicle <NUM>.

In operation S545, the mobile device <NUM> may request a payment server <NUM> to pay for the item. The mobile device <NUM> may request the payment server <NUM> to pay for the item by transmitting the license plate number, a total amount owed for the item or items i.e., total cost, card information, and device information regarding the mobile device <NUM> to the payment server <NUM>. The device information may include, for example, an ID value of the mobile device <NUM> and/or an ID value of a user of the mobile device <NUM>.

In operation S550, the store terminal <NUM> may request the payment server <NUM> to provide a payment authentication result. The store terminal <NUM> may determine whether the license plate number obtained in operation S500 and the license plate number received in operation S540 are identical to each other. When the license plate number obtained in operation S500 and the license plate number received in operation S540 are identical to each other, the store terminal <NUM> may request the payment server <NUM> to provide the payment authentication result by transmitting the license plate number and the total cost to the payment server <NUM>.

Although it is described above that the store terminal <NUM> requests the payment server <NUM> to provide the payment authentication result by transmitting the total cost to the payment server <NUM> on the basis of the purchasing item information received from the vehicle terminal <NUM> in operation S540, exemplary embodiments are not limited thereto. For example, the store terminal <NUM> may request the payment server <NUM> to provide the payment authentication result without providing the total cost to the payment server <NUM>. In this case, the store terminal <NUM> may request the payment server <NUM> to provide the payment authentication result by providing the payment server <NUM> with only the license plate number.

In operation S555, the payment server <NUM> may authenticate payment of the item. The payment server <NUM> may authenticate the payment of the item which the user desires to purchase on the basis of the card information and the total cost received from the mobile device <NUM>.

In this case, the payment server <NUM> may search for the store terminal <NUM> transmitting the same license plate number as the license plate number received from the mobile device <NUM>. Furthermore, the payment server <NUM> may compare the total cost received from the store terminal <NUM> transmitting the same license plate number as the license plate number received from the mobile device <NUM> with a total cost received from the mobile device <NUM>. The payment server <NUM> may authenticate the payment of the item when the total cost received from the store terminal <NUM> transmitting the same license plate number as the license plate number received from the mobile device <NUM> and the total cost received from the mobile device <NUM> are identical to each other. Thus, the payment server <NUM> may verify whether the item which the user of the mobile device <NUM> desires to purchase will be rightly paid for.

In operation S560, the payment server <NUM> may transmit the payment authentication result which is a result of authenticating the payment of the item to the store terminal <NUM>. The payment server <NUM> may transmit vehicle information and the payment authentication result to the store terminal <NUM>. Alternatively, the payment server <NUM> may transmit the vehicle information, the card information, and the payment authentication result to the store terminal <NUM>. Alternatively, the payment server <NUM> may not transmit the card information to the store terminal <NUM>. In this case, the payment server <NUM> may transmit the vehicle information and the payment authentication result to the store terminal <NUM>.

In operation S565, the payment server <NUM> may transmit the payment authentication result of the item to the mobile device <NUM>. The payment server <NUM> may transmit the vehicle information and the payment authentication result to the mobile device <NUM>. Alternatively, the payment server <NUM> may transmit the card information and the payment authentication result to the mobile device <NUM>. Alternatively, the payment server <NUM> may transmit the vehicle information, the card information, and the payment authentication result to the mobile device <NUM>. The payment server <NUM> may not transmit the card information to the mobile device <NUM>. In this case, the vehicle information and the payment authentication result may be transmitted to the mobile device <NUM>.

In operation S570, the store terminal <NUM> may complete the payment of the item on the basis of the payment authentication result, and display a message indicating the completion of the payment on a screen thereof. Furthermore, when the payment is completed, the user may receive the item from the offline store. In addition, the store terminal <NUM> may check whether the payment of the item which the user desires to purchase is completed on the basis of the purchasing item information. In this case, the purchasing item information may be information received from the vehicle terminal <NUM> or information generated by the store terminal <NUM>.

Although it is described above with reference to <FIG> that the mobile device <NUM> selects the credit card and provides the card information regarding the selected credit card to the payment server <NUM>, exemplary embodiments are not limited thereto. The mobile device <NUM> or a credit card corresponding to the user may be registered beforehand in the payment server <NUM>. In this case, the mobile device <NUM> may provide the payment server <NUM> with device ID value or user ID instead of the card information, which uniquely identifies the device or user, respectively. Furthermore, the payment server <NUM> may select a credit card matching the device ID value or the user ID as a credit card for paying for the item. The mobile device <NUM> may be connected to the payment server <NUM> and register and manage a credit card to be used for payment based on a license plate number.

<FIG> is a flow diagram illustrating a method of paying for an item, performed in an item payment system, in which a mobile terminal <NUM> selects an item which a user desires to purchase and requests to pay for the item by using a license plate number received from a vehicle terminal <NUM>, according to the invention.

In operation S600, a store terminal <NUM> obtains a license plate number of the vehicle <NUM>. In operation S605, a vehicle terminal <NUM> and a mobile device <NUM> access each other at short range. In operation S610, the vehicle terminal <NUM> may transmit a license plate number to the mobile device <NUM> through short-range wireless communication.

In operation S615, the mobile device <NUM> may execute a payment application for paying for the item. The mobile device <NUM> may execute the payment application as the vehicle terminal <NUM> accesses the mobile device <NUM> at short range.

In operation S620, mobile device <NUM> may display item information. The mobile device <NUM> may display the item information on a screen thereof as the vehicle terminal <NUM> accesses the mobile device <NUM> at short range.

The mobile device <NUM> may be connected to a service server of an offline store and obtain item information regarding items provided in the offline store. The mobile device <NUM> may display on a screen thereof the item information obtained from the service server of the offline store. For example, the mobile device <NUM> may display a GUI including a list of the items provided in the offline store and the prices of the items on the screen thereof.

Furthermore, the mobile device <NUM> may be connected to the service server of the offline store by identifying the offline store which the vehicle <NUM> enters on the basis of a location of the mobile device <NUM>. The identifying of the offline store may include identifying, for example, the name of the offline store, a district of the offline store, and/or an access address of the service server of the offline store.

For example, the mobile device <NUM> may identify the offline store by identifying the location of the mobile device <NUM> by using a global positioning system (GPS) signal. Alternatively, for example, the mobile device <NUM> may identify the offline store by identifying the location of the mobile device <NUM> on the basis of a signal received from an access point (AP) near the offline store. Alternatively, for example, the mobile device <NUM> may identify the offline store on the basis of a signal broadcast from a communication module in the offline store. In this case, the broadcast signal may include, for example, the name of the offline store, the district of the offline store, and or the access address of the service server of the offline store.

In operation S625, the mobile device <NUM> may select an item to be purchased. In operation S630, the mobile device <NUM> may select a card to be used to pay for the item.

In operation S635, the mobile device <NUM> provides the vehicle terminal <NUM> with a license plate number and purchasing item information. The mobile device <NUM> may transmit the license plate number and the purchasing item information to the vehicle terminal <NUM> through short-distance communication.

Operations S640 to S655 correspond to operations S540 to S555 of <FIG> and thus a description thereof is omitted here.

<FIG> is a flow diagram illustrating a method of paying for an item, performed in an item payment system, in which a first mobile device <NUM> and a second mobile device <NUM> request a payment server <NUM> to pay for the item, according to an exemplary embodiment.

Operations S700 to S715 correspond to operations S500 to S515 of <FIG> and thus a description thereof is omitted here for convenience of explanation.

In operation S720, a vehicle terminal <NUM> and the first mobile device <NUM> may access each other at short range. The first mobile device <NUM> may access the vehicle terminal <NUM> at short range while an application for using a payment service according to an exemplary embodiment is executed.

In operation S725, the vehicle terminal <NUM> and the second mobile device <NUM> may access each other at short range. The second mobile device <NUM> may access the vehicle terminal <NUM> at short range while an application for using a payment service according to an exemplary embodiment is executed.

In operation S730, the vehicle terminal <NUM> may determine divided payment costs. The vehicle terminal <NUM> may display a GUI for inputting the divided payment costs on a screen thereof so that a total cost of the item may be divided and paid by the first mobile device <NUM> and the second mobile device <NUM>. For example, a user may enter a cost to be paid by the first mobile device <NUM> and a cost to be paid by the second mobile device <NUM> through the GUI for inputting the divided payment costs. Alternatively, for example, the user may input a ratio or a percentage between the cost to be paid by the first mobile device <NUM> and the cost to be paid by the second mobile device <NUM> through the GUI for inputting a divided payment cost.

In operation S735, the vehicle terminal <NUM> may transmit a license plate number and information regarding the divided payment cost to be paid by the first mobile device <NUM> to the first mobile device <NUM>. The vehicle terminal <NUM> may transmit the license plate number and the information regarding the divided payment cost to be paid by the first mobile device <NUM> to the first mobile device <NUM> through short-range wireless communication.

In operation S740, the vehicle terminal <NUM> may transmit the license plate number and information regarding the divided payment cost to be paid by the second mobile device <NUM> to the second mobile device <NUM>. The vehicle terminal <NUM> may transmit the license plate number and the information regarding the divided payment cost to be paid by the second mobile device <NUM> to the second mobile device <NUM> through short-range wireless communication.

If a user of the first mobile device <NUM> is an owner of the vehicle <NUM>, the vehicle terminal <NUM> may transmit the license plate number to the second mobile device <NUM> only when an approval is received from the user of the first mobile device <NUM>. In this case, the first mobile device <NUM> of the owner of the vehicle <NUM> may be registered as a main payment device beforehand in the vehicle terminal <NUM>. The vehicle terminal <NUM> may display on a screen thereof a GUI for receiving an approval to the transmission of the license plate number to the second mobile device <NUM>. When the approval is input by the user of the first mobile device <NUM> through the displayed GUI, the vehicle terminal <NUM> may provide the second mobile device <NUM> with the license plate number.

Alternatively, for example, the first mobile device <NUM> may transmit approval information indicating the approval from the user of the first mobile device <NUM> to the second mobile device <NUM>, and the second mobile device <NUM> may receive the license plate number from the vehicle terminal <NUM> by using the approval information of the user of the first mobile device <NUM>.

Although it is described above that the license plate number is provided from the vehicle terminal <NUM> to the second mobile device <NUM>, the providing of the license plate number to the second mobile device <NUM> is not limited thereto.

For example, the second mobile device <NUM> may receive the license plate number of the vehicle <NUM> from the first mobile device <NUM>. For example, the first mobile device <NUM> may transmit the license plate number stored therein to the second mobile device <NUM> after the user of the first mobile device <NUM> is authenticated.

Alternatively, for example, a user of the second mobile device <NUM> may input the license plate number to the second mobile device <NUM> by using authentication information (e.g., a password, fingerprints, an iris, etc.) of the user of the first mobile device <NUM>. In this case, a GUI for authenticating the user of the first mobile device <NUM> may be displayed on a screen of the second mobile device <NUM>. Alternatively, when the authentication information of the user of the first mobile device <NUM> is input via the displayed GUI, the second mobile device <NUM> may receive the license plate number.

In operation S745, the vehicle terminal <NUM> may transmit the license plate number and purchasing item information to a store terminal <NUM>. Furthermore, the vehicle terminal <NUM> may transmit information regarding the divided payment cost to be paid by the first mobile device <NUM> and the divided payment cost to be paid by the second mobile device <NUM> to the store terminal <NUM>.

In operation S750, the first mobile device <NUM> may select a card to be used to pay for the item. In operation S755, the first mobile device <NUM> may authenticate the user to pay for the item. In operation S760, the second mobile device <NUM> may select a card to be used to pay for the item. In operation S765, the second mobile device <NUM> may authenticate the user to pay for the item. In an exemplary embodiment, the selection and authentication of the two terminals may occur at substantially same time.

In operation S770, the first mobile device <NUM> may request the payment server <NUM> to pay for the item. The first mobile device <NUM> may request the payment server <NUM> to pay for the item while transmitting the license plate number, the information regarding a first divided payment cost, and the card information to the payment server <NUM>. The first divided payment cost may be a part of the total cost of the item to be paid by the first mobile device <NUM>. The card information may be information regarding a credit card selected by the first mobile device <NUM>. The first mobile device <NUM> may provide a coupon related to the payment of the item to the payment server <NUM>.

In operation S775, the second mobile device <NUM> may request the payment server <NUM> to pay for the item. The second mobile device <NUM> may request the payment server <NUM> to pay for the item while transmitting the license plate number, the information regarding second divided payment cost, and the card information to the payment server <NUM>. The second divided payment cost may be a part of the total cost of the item to be paid by the second mobile device <NUM>. The card information may be information regarding a credit card selected by the second mobile device <NUM>. Furthermore, the second mobile device <NUM> may provide a coupon related to the payment of the item to the payment server <NUM>.

In operation S780, the store terminal <NUM> may request the payment server <NUM> to provide a payment authentication result. The store terminal <NUM> may transmit the license plate number and information regarding the total cost of the purchase to the payment server <NUM>. The store terminal <NUM> may transmit, for example, information regarding the total cost of the item to be paid, the cost of the item to be paid by the first mobile device <NUM>, and the cost of the item to be paid by the second mobile device <NUM> to the payment server <NUM>. Alternatively, the store terminal <NUM> may not provide the information regarding the total cost to the payment server <NUM>. In this case, the store terminal <NUM> may request the payment server <NUM> to provide the payment authentication result while transmitting only the license plate number to the payment server <NUM>.

In operation S785, the payment server <NUM> may authenticate the payment of the item. The payment server <NUM> may check the item to be paid and the divided payment costs of the item on the basis of the license plate number. The payment server <NUM> may divide and pay the total cost of the item or items by using the credit card selected by the first mobile device <NUM> and the credit card selected by the second mobile device <NUM>.

<FIG> is a diagram illustrating a vehicle terminal <NUM> requesting a payment server <NUM> to pay for an item by using a license plate number, according to an exemplary embodiment.

Referring to <FIG>, the vehicle terminal <NUM> may select an item to be purchased on the basis of a user input, and receive card information from a mobile device <NUM> through short-range wireless communication. Furthermore, the vehicle terminal <NUM> may request the payment server <NUM> to pay for the item by using the card information.

<FIG> is a flow diagram illustrating a method of paying for an item by requesting a payment server <NUM> to pay for the item, performed by a vehicle terminal <NUM>, according to an exemplary embodiment.

Operations S900 to S920 correspond to operations S500 to S520 of <FIG> and thus a description thereof is omitted here for convenience of an explanation. Operations S925 and S930 correspond to operations S530 and S535 of <FIG> and thus a description thereof is omitted here for convenience of an explanation.

In operation S935, a mobile device <NUM> may transmit card information to the vehicle terminal <NUM>. The mobile device <NUM> may access the vehicle terminal <NUM> at a short range, and transmit the card information to the vehicle terminal <NUM> through short-range wireless communication.

In operation S940, the vehicle terminal <NUM> may provide the license plate number and the purchasing item information to the store terminal <NUM>. As an item to be purchased is selected by the vehicle terminal <NUM>, the vehicle terminal <NUM> may provide the store terminal <NUM> with purchasing item information regarding the selected item and the license plate number registered in the vehicle terminal <NUM>. The vehicle terminal <NUM> may provide the store terminal <NUM> with the license plate number and the purchasing item information through a communication module installed outside the vehicle <NUM>.

In operation S945, the vehicle terminal <NUM> may request the payment server <NUM> to pay for the item. The vehicle terminal <NUM> may request the payment server <NUM> to pay for the item by transmitting the license plate number, a total cost, the card information, and the device information regarding the mobile device <NUM> to the payment server <NUM>.

Operations S950 to S970 are substantially the same as operations S550 to S570 of <FIG> and thus a description thereof is omitted here for convenience of explanation.

<FIG> is a flow diagram illustrating a method of paying for an item by requesting a payment server <NUM> to make divided payment of the item, performed by a vehicle terminal <NUM>, according to an exemplary embodiment.

Operations S1000 to S1065 correspond to operations S700 to S765 of <FIG> and thus a description thereof is omitted here for convenience of explanation.

In operation S1070, a first mobile device <NUM> may request the vehicle terminal <NUM> to pay for an item. The first mobile device <NUM> may request the vehicle terminal <NUM> to pay for the item by transmitting a license plate number, information regarding a first divided payment cost, and card information to the vehicle terminal <NUM>. Furthermore, the first mobile device <NUM> may provide a coupon related to the payment of the item to the vehicle terminal <NUM>.

In operation S1075, a second mobile device <NUM> may request the vehicle terminal <NUM> to pay for the item. The second mobile device <NUM> may request the vehicle terminal <NUM> to pay for the item while transmitting the license plate number, information regarding a second divided payment cost, and card information to the vehicle terminal <NUM>. Furthermore, the second mobile device <NUM> may provide a coupon related to the payment of the item to the vehicle terminal <NUM>.

In operation S1080, the vehicle terminal <NUM> may request the payment server <NUM> to pay for the item. The vehicle terminal <NUM> may request the payment server <NUM> to pay for the item while transmitting the license plate number, the information regarding the first divided payment cost and the second divided payment cost, and the card information to the payment server <NUM>. The card information may include information regarding a credit card selected by the first mobile device <NUM> and information regarding a credit card selected by the second mobile device <NUM>. Furthermore, the vehicle terminal <NUM> may provide a coupon related to the payment of the item to the payment server <NUM>.

Operations S1085 and S1090 correspond to operations S780 and S785 of <FIG> and thus a description thereof is omitted here for convenience of explanation.

<FIG> is a diagram illustrating an exemplary embodiment in which an item is paid by requesting a payment server <NUM> to pay for the item via a store server <NUM> without using a vehicle terminal <NUM>, performed by a mobile device <NUM>, according to an exemplary embodiment.

Referring to <FIG>, a user who gets or is in a vehicle <NUM> may pay for an item by using the mobile device <NUM> without using the vehicle terminal <NUM>. The mobile device <NUM> may check whether the mobile device <NUM> enters an offline store and be then connected to a store server <NUM> of the offline store. Furthermore, the mobile device <NUM> may receive item information regarding items provided in the offline store from the store server <NUM>, and display a GUI for purchasing an item. Furthermore, the mobile device <NUM> may select a desired item or items on the basis of a user input, and select a credit card for paying for the selected item.

Furthermore, the mobile device <NUM> may request the store server <NUM> to pay for the item by transmitting a license plate number, card information, and purchasing item information to the store server <NUM>. The store server <NUM> may be a server operated in the offline store. Furthermore, the store server <NUM> may be a server located in the offline store or may be a separate server managing the offline store. The mobile device <NUM> may register beforehand the license plate number therein or receive the license plate number in real time through a user input. Alternatively, the mobile device <NUM> may receive only the license plate number from the vehicle terminal <NUM>.

Thereafter, the store server <NUM> may request the payment server <NUM> to pay for the item, and the payment server <NUM> may authenticate the payment of the item and transmit a payment authentication result to the store terminal <NUM>. The payment authentication result may include the license plate number, whether the payment of the item is authenticated or not, a list of items, and information regarding a settlement cost or total cost of the purchase.

Furthermore, the store terminal <NUM> may complete the payment of the item by obtaining a license plate number by using a camera <NUM> and comparing the obtained license plate number with the payment authentication result. Furthermore, the store terminal <NUM> may display the purchasing item information, a progress of the payment, and whether the payment is completed or not on a separate display device (not shown) connected thereto, so that a user may view the purchasing item information, the progress of the payment, and whether the payment is completed or not.

<FIG> is a diagram illustrating an exemplary embodiment in which an item is paid by requesting a store terminal <NUM> to pay for the item via a store server <NUM> without using a vehicle terminal <NUM>, performed by a mobile device <NUM>.

Referring to <FIG>, a user who is in a vehicle <NUM> may pay for an item by using the mobile device <NUM> without using the vehicle terminal <NUM>. The mobile device <NUM> may check whether the vehicle <NUM> enters an offline store, be connected to the store server <NUM> of the offline store, and receive item information regarding items provided in the offline store from the store server <NUM>. Furthermore, the mobile device <NUM> may select an item to be purchased on the basis of a user input, and select a credit card for paying for the selected item. Furthermore, the mobile device <NUM> may request the store server <NUM> to pay for the selected item by transmitting a license plate number, card information, and purchasing item information to the store server <NUM>.

Then the store server <NUM> may request the store terminal <NUM> to pay for the item by transmitting the license plate number, the card information, and the purchasing item information to the store terminal <NUM>. The store terminal <NUM> may obtain a license plate number through a camera <NUM> and compare the obtained license plate number with the license plate number received from the store server <NUM>. Furthermore, the store terminal <NUM> may request the payment server <NUM> to pay for the item by providing the payment server <NUM> with the license plate number, the card information, and a total cost of the purchase on the basis of a result of the comparison. The payment server <NUM> may authenticate the payment of the item and transmit a payment authentication result to the store terminal <NUM>. The store terminal <NUM> may provide the mobile device <NUM> with the payment authentication result via the store server <NUM>. Furthermore, the store terminal <NUM> may display the purchasing item information, a progress of the payment, and whether the payment is completed or not on a separate display device (not shown) connected thereto, so that a user may view the purchasing item information, the progress of the payment, and whether the payment is completed or not.

<FIG> is a diagram illustrating a license plate number registration by a vehicle terminal <NUM>, according to an exemplary embodiment.

Referring to <FIG>, the vehicle terminal <NUM> may display a GUI for inputting a license plate number and receive the license plate number on the basis of a user input received through the GUI. Furthermore, the vehicle terminal <NUM> may inquire of a vehicle management server <NUM> about whether a correct license plate number is received. When the received license plate number is correct, the vehicle terminal <NUM> may register it therein. The vehicle management server <NUM> may be a server managing a license plate number of a vehicle <NUM>. The vehicle management server <NUM> may store a vehicle ID number (VIN) of the vehicle <NUM> and the license plate number such that they match each other.

<FIG> is a flow diagram illustrating a method of registering a license plate number, performed by a vehicle terminal <NUM>, according to an exemplary embodiment.

In operation S1400, the vehicle terminal <NUM> may display a GUI for registering a license plate number therein on a screen thereof. When a user executes a function of using a license plate number-based payment service in the vehicle terminal <NUM>, the vehicle terminal <NUM> may display the GUI for registering the license plate number. Alternatively, when the user selects a button for registering the license plate number, the vehicle terminal <NUM> may display the GUI for registering the license plate number.

In operation S1405, the vehicle terminal <NUM> may receive a user input indicating a license plate number. The user may input the license plate number by using an alphabetical keyboard provided in the GUI.

In operation S1410, the vehicle terminal <NUM> may request a vehicle management server <NUM> to authenticate the license plate number. The vehicle terminal <NUM> may request the vehicle management server <NUM> to authenticate the license plate number by providing a vehicle ID number of the vehicle <NUM> and the license plate number to the vehicle management server <NUM>. In this case, the vehicle ID number of the vehicle <NUM> may be registered beforehand in the vehicle terminal <NUM> by a manufacturer of the vehicle <NUM> during the manufacture of the vehicle <NUM>.

In operation S1415, the vehicle management server <NUM> may authenticate the license plate number received from the vehicle terminal <NUM>. The vehicle management server <NUM> may store the vehicle ID number and the license plate number of the vehicle <NUM> such that they match each other during the registering of the vehicle <NUM>. Furthermore, the vehicle management server <NUM> may authenticate the license plate number received from the vehicle terminal <NUM> by comparing the vehicle ID number and the license plate number received from the vehicle terminal <NUM> with those stored in the vehicle management server <NUM>.

In operation S1420, the vehicle management server <NUM> may transmit a result of authenticating the license plate number to the vehicle terminal <NUM>. In operation S1425, the vehicle terminal <NUM> may register the received license plate number therein.

Although it is described above with reference to <FIG> that the vehicle terminal <NUM> receives the license plate number on the basis of the user input, exemplary embodiments are not limited thereto. When a user executes a function of using a license plate number-based payment service in the vehicle terminal <NUM> or selects a button for registering the license plate number, the vehicle terminal <NUM> may receive the license plate number by requesting the vehicle management server <NUM> to provide it. In this case, the vehicle terminal <NUM> may request the vehicle management server <NUM> to provide the license plate number by transmitting the vehicle ID number to the vehicle management server <NUM>. Furthermore, the vehicle terminal <NUM> may display the license plate number received from the vehicle management server <NUM> on a screen thereof to receive a confirmation as to whether the received license plate number is correct from a user.

<FIG> is a diagram illustrating a location of a vehicle <NUM> being checked by a vehicle terminal <NUM>, according to an exemplary embodiment.

Referring to <FIG>, for example, the vehicle terminal <NUM> may determine a location of the vehicle <NUM> by using a GPS device located in the vehicle terminal <NUM>. Furthermore, the vehicle terminal <NUM> may determine the location of the vehicle <NUM>, for example, on the basis of a signal received from an access point (AP) <NUM> near the vehicle terminal <NUM>. Furthermore, the vehicle terminal <NUM> may determine the location of the vehicle <NUM>, for example, on the basis of a signal broadcast from a Bluetooth device <NUM> located in an offline store.

<FIG> is a diagram illustrating divided payment costs being entered into a vehicle terminal <NUM>, according to an exemplary embodiment.

Referring to reference number <NUM> of <FIG>, the vehicle terminal <NUM> may display a list of items and receive a user input for selecting a desired item from the list of items. A first mobile device <NUM> and a second mobile device <NUM> access the vehicle terminal <NUM> at short range and transmit device information thereof to the vehicle terminal <NUM> through short-range wireless communication.

Referring to reference numeral <NUM> of <FIG>, the vehicle terminal <NUM> may display on a screen thereof the name of an item or items selected, the price of each of the selected item, and a sentence requesting to enter a divided payment cost. For example, the vehicle terminal <NUM> may display on the screen thereof phrases 'Enter the amount of money to be paid', 'Device A: ', and 'Device B: ', and receive information regarding the amount of money to be paid by the device A and the amount of money to be paid by the device B from a user.

<FIG> is a diagram illustrating a location at a short-distance communication module <NUM> of the vehicle terminal <NUM>, according to an exemplary embodiment.

Referring to <FIG>, the short-distance communication module <NUM> of the vehicle terminal <NUM> may be installed near a steering wheel of the vehicle <NUM>. For example, the short-distance communication module <NUM> may be installed in a horn of the vehicle. When a mobile device <NUM> is located near the horn of the vehicle <NUM>, the mobile device <NUM> may perform short-range wireless communication with the vehicle terminal <NUM> through the short-distance communication module <NUM>. By way of an example, the short-distance communication module <NUM> may be Bluetooth circuitry.

<FIG> is a diagram illustrating at least one communication module, e.g., communication modules <NUM>, <NUM>, <NUM>, and <NUM>, installed outside the vehicle <NUM>, according to an exemplary embodiment.

Referring to <FIG>, the communication modules <NUM>, <NUM>, <NUM>, and <NUM> may be installed outside the vehicle <NUM> to communicate with a store terminal <NUM>. For example, the communication modules <NUM>, <NUM>, <NUM>, and <NUM> may be installed at a side mirror, a left bumper, and a right bumper of the vehicle <NUM>. Furthermore, when a short-distance communication module (not shown) of the store terminal <NUM> accesses at least one among the communication modules <NUM>, <NUM>, <NUM>, and <NUM>, the store terminal <NUM> may exchange data with the vehicle terminal <NUM> through short-range wireless communication.

<FIG> are views illustrating a list of items being displayed by the vehicle terminal <NUM>, according to an exemplary embodiment.

Referring to <FIG>, as the vehicle <NUM> of <FIG> enters a hamburger store, the vehicle terminal <NUM> may receive menu information from the store terminal <NUM> of <FIG> located in the hamburger store and display a list of hamburgers on a screen of the vehicle terminal <NUM>.

Referring to <FIG>, as the vehicle <NUM> enters a gas station, the vehicle terminal <NUM> may receive oil price information from the store terminal <NUM> located in the gas station to put oil into the vehicle <NUM>, and display a list of oil types on the screen of the vehicle terminal <NUM>.

<FIG> is a flow diagram illustrating a method of authenticating payment of an item, performed by a payment server <NUM>, according to an exemplary embodiment.

Referring to <FIG>, the payment server <NUM> according to an exemplary embodiment may include a payment agent server <NUM> and a card company server <NUM>. Furthermore, the payment agent server <NUM> and the card company server <NUM> may be embodied as one or more servers. Furthermore, the payment agent server <NUM> and the card company server <NUM> may be operated by the same business operator or different business operators.

In operation S2000, the payment agent server <NUM> may receive a request to pay for an item. The payment agent server <NUM> may receive a request to pay for an item which a user desires to purchase from at least one among the vehicle terminal <NUM>, the mobile device <NUM>, the store terminal <NUM>, and the store server <NUM>.

The request to pay for the item from at least one among the vehicle terminal <NUM>, the mobile device <NUM>, the store terminal <NUM>, and the store server <NUM> may include information regarding a total cost for purchase, card information, and first authentication information. The first authentication information may be authentication information managed by the payment agent server <NUM> to authenticate use of a card. Alternatively, for example, the request to pay for the item from at least one among the vehicle terminal <NUM>, the mobile device <NUM>, the store terminal <NUM>, and the store server <NUM> may include the information regarding the total cost for purchase, a license plate number, and the first authentication information. Alternatively, for example, the request to pay for the item from at least one among the vehicle terminal <NUM>, the mobile device <NUM>, the store terminal <NUM>, and the store server <NUM> may include i) the information regarding the total cost, ii) an ID value of the mobile device <NUM> or user ID, and iii) the first authentication information.

Furthermore, the payment agent server <NUM> may register and manage card information, first authentication information, and second authentication information of each of users. The second authentication information may be authentication information managed by the card company server <NUM> to authenticate use of a card.

In operation S2010, the payment agent server <NUM> may authenticate a user by using the first authentication information. When the payment agent server <NUM> receives the card information and the first authentication information from at least one among the vehicle terminal <NUM>, the mobile device <NUM>, the store terminal <NUM>, and the store server <NUM>, the payment agent server <NUM> may authenticate use of a card corresponding to the received card information by using the received first authentication information.

When receiving the license plate number and the first authentication information from at least one among the vehicle terminal <NUM>, the mobile device <NUM>, the store terminal <NUM>, and the store server <NUM>, the payment agent server <NUM> may extract previously registered card information corresponding to the license plate number from database (DB) of the payment agent server <NUM>. Furthermore, the payment agent server <NUM> may authenticate use of a card corresponding to the extracted card information by using the received first authentication information.

When receiving i) device ID value or user ID and ii) first authentication information from at least one among the vehicle terminal <NUM>, the mobile device <NUM>, the store terminal <NUM>, and the store server <NUM>, the payment agent server <NUM> may extract previously registered card information corresponding to the ID value of the mobile device <NUM> or the user ID from the DB of the payment agent server <NUM>. Furthermore, the payment agent server <NUM> may authenticate use of a card corresponding to the extracted card information by using the received first authentication information.

In operation S2020, the payment agent server <NUM> may extract second authentication information to be provided to the card company server <NUM> from the DB thereof. The payment agent server <NUM> may register and manage a license plate number, card information, first authentication information, and second authentication information of each of the users.

When receiving the card information from at least one among the vehicle terminal <NUM>, the mobile device <NUM>, the store terminal <NUM>, and the store server <NUM>, the payment agent server <NUM> may extract previously registered second authentication information corresponding to a user from the DB thereof on the basis of the received card information.

When receiving the license plate number from at least one among the vehicle terminal <NUM>, the mobile device <NUM>, the store terminal <NUM>, and the store server <NUM>, the payment agent server <NUM> may extract previously registered card information and second authentication information corresponding to a user from the DB thereof on the basis of the license plate number.

When receiving the ID value of the mobile device <NUM> or the user ID from at least one among the vehicle terminal <NUM>, the mobile device <NUM>, the store terminal <NUM>, and the store server <NUM>, the payment agent server <NUM> may extract previously registered card information and second authentication information corresponding to a user from the DB thereof on the basis of the ID value of the mobile device <NUM> or the user ID.

In operation S2030, the payment agent server <NUM> may request the card company server <NUM> to pay for the item. The payment agent server <NUM> may request the card company server <NUM> to pay for the item by transmitting the information regarding the total cost of purchase, the card information, and the second authentication information to the card company server <NUM>.

In operation S2040, the card company server <NUM> may pay for the item. The card company server <NUM> may authenticate use of a card corresponding to the card information on the basis of the information regarding the total cost for the purchase, the card information, and the second authentication information which are received.

In operation S2050, the card company server <NUM> may provide the payment agent server <NUM> with a payment authentication result. In operation S2060, the payment agent server <NUM> may transmit the payment authentication result.

Alternatively, the card company server <NUM> may transmit the payment authentication result to the at least one among the vehicle terminal <NUM>, the mobile device <NUM>, the store terminal <NUM>, and the store server <NUM> without going through the payment agent server <NUM>. In this case, the card company server <NUM> may receive beforehand information for communicating with the vehicle terminal <NUM>, the mobile device <NUM>, the store terminal <NUM>, and the store server <NUM> from the payment agent server <NUM>. For example, when receiving the request to pay for the item, the card company server <NUM> may receive beforehand the information for communicating with the vehicle terminal <NUM>, the mobile device <NUM>, the store terminal <NUM>, and the store server <NUM> from the payment agent server <NUM>.

<FIG> is a block diagram of a vehicle terminal <NUM> according to an exemplary embodiment.

As illustrated in <FIG>, the vehicle terminal <NUM> according to an exemplary embodiment may include a user input interface <NUM>, a display <NUM>, a controller (or a processor) <NUM>, and a communicator <NUM>. However, all the elements illustrated in <FIG> are not indispensable elements of the vehicle terminal <NUM>. The vehicle terminal <NUM> may further include other elements in addition to the elements illustrated in <FIG> or may include only some of the elements illustrated in <FIG>.

The user input interface <NUM> should be understood as a means through which a user inputs data for controlling the vehicle terminal <NUM>. Examples of the user input interface <NUM> may include, but are not limited to, a key pad, a touch pad (a contact type capacitive touch pad, a pressure type resistive overlay touch pad, an infrared sensor type touch pad, a surface acoustic wave conduction touch pad, an integration type tension measurement touch pad, a piezo effect type touch pad, or the like), a jog wheel, a jog switch, etc. A user input for performing card number-based payment may be received via the user input interface <NUM>.

The display <NUM> displays and outputs information processed by the vehicle terminal <NUM>. For example, the display <NUM> may display a GUI for performing card number-based payment.

When the display <NUM> and a touch pad form a touch screen in a layered structure together, the display <NUM> may be used as an input device as well as an output device. Furthermore, the vehicle terminal <NUM> may include two or more displays <NUM>.

The communicator <NUM> may include one or more elements for communicating the mobile device <NUM>, the store terminal <NUM>, the store server <NUM>, and the payment server <NUM> with one another. For example, the communicator <NUM> may include at least one short-distance communication component, a mobile communication component, a broadcast receiver, etc. The short-distance communication component may be installed inside the vehicle <NUM> to communicate with the mobile device <NUM>. In this case, the short-distance communication component may be installed near the steering wheel of the vehicle <NUM> but is not limited thereto.

Furthermore, a plurality of short-distance communication components may be installed outside the vehicle <NUM> to communicate with the store terminal <NUM>. In this case, the plurality of short-distance communication components may be installed, for example, at a side mirror, a left bumper, and a right bumper of the vehicle <NUM> but is not limited thereto. Furthermore, the plurality of short-distance communication components may be selectively activated by the controller <NUM>. An activated short-distance communication component may communicate with the store terminal <NUM>.

Generally, the controller <NUM> controls overall operations of the vehicle terminal <NUM>. For example, the controller <NUM> may execute programs stored in a memory included in the vehicle terminal <NUM> to control overall operations of the user input interface <NUM>, the display <NUM>, the controller <NUM>, the communication unit <NUM>, etc. The controller <NUM> may execute programs stored in a memory (not shown) to perform operations of the vehicle terminal <NUM> described above with reference to <FIG>.

The controller <NUM> may register a license plate number of the vehicle <NUM>. The controller <NUM> may control the display <NUM> to display a GUI for registering the license plate number. The controller <NUM> may register in the vehicle terminal <NUM> the license plate number input by a user through the GUI.

The controller <NUM> may control the display <NUM> to display item information regarding items provided in an offline store. The controller <NUM> may control the communicator <NUM> to receive the item information from the store terminal <NUM> of the offline store, and display the received item information on the display <NUM> of the vehicle terminal <NUM>. Alternatively, the controller <NUM> may determine a location of the vehicle <NUM> and be connected to a web site of the offline store at the determined location of the vehicle <NUM> so as to display the item information regarding the items provided in the offline store on the display <NUM> of the vehicle terminal <NUM>. Furthermore, the vehicle terminal <NUM> may display a list of the items on the display <NUM> of the vehicle terminal <NUM> and receive a user input for selecting a desired item.

The vehicle terminal <NUM> may control the communicator <NUM> to access the mobile device <NUM> at short range. As the vehicle device <NUM> approaches a range of communication of the short-distance communication component of the vehicle terminal <NUM>, communication may be established between the vehicle terminal <NUM> and the mobile device <NUM>.

The controller <NUM> may control the communicator <NUM> to transmit the license plate number and purchasing item information to the mobile device <NUM>. The controller <NUM> may transmit the license plate number registered in the vehicle terminal <NUM> and purchasing item information regarding an item which a user desires to purchase to the mobile device <NUM> through short-range wireless communication.

The controller <NUM> may receive card information from the mobile device <NUM> and transmit the license plate number, the purchasing item information, and the card information to the payment server <NUM> so as to request the payment server <NUM> to pay for the item.

Furthermore, the controller <NUM> may determine divided payment costs. The controller <NUM> may display a GUI for inputting the divided payment costs of the item on the display <NUM> so that the total cost may be divided and paid by the first mobile device <NUM> and the second mobile device <NUM>.

<FIG> and <FIG> are block diagrams of mobile devices <NUM> according to exemplary embodiments.

As illustrated in <FIG>, the mobile device <NUM> according to an exemplary embodiment may include a user input unit <NUM>, an output unit <NUM>, a controller <NUM>, and a communication unit <NUM>. However, all the elements illustrated in <FIG> are not indispensable elements of the mobile device <NUM>. The mobile device <NUM> may further include elements other than the elements illustrated in <FIG> or may include only some of the elements illustrated in <FIG>.

For example, as illustrated in <FIG>, the mobile device <NUM> according to another exemplary embodiment may include a user input interface <NUM>, an output interface <NUM>, a controller <NUM>, and a communicator <NUM>, and may further include a sensing component <NUM>, an audio/video (A/V) input interface <NUM>, and the memory <NUM>.

The user input interface <NUM> provides an interface with the user through which a user inputs data for controlling the mobile device <NUM>. Examples of the user input interface <NUM> may include, but are not limited to, a key pad, a dome switch, a touch pad (a contact type capacitive touch pad, a pressure type resistive overlay touch pad, an infrared sensor type touch pad, a surface acoustic wave conduction touch pad, an integration type tension measurement touch pad, a piezo effect type touch pad, or the like), a jog wheel, a jog switch, etc. A user input for paying for an item on the basis of a license plate number may be received via the user input interface <NUM>.

The output interface <NUM> may output an audio signal, a video signal, or a vibration signal. The output interface <NUM> may include a display <NUM>, a sound outputter <NUM>, and a vibration motor <NUM>.

The display <NUM> displays and outputs information processed by the mobile device <NUM>. For example, the display <NUM> may display a GUI for paying for the item on the basis of the license plate number.

When the display <NUM> and a touch pad form a touch screen in a layered structure together, the display <NUM> may be used as an input device as well as an output device.

The sound outputter <NUM> outputs audio data received from the communicator <NUM> or audio data stored in the memory <NUM>. The vibration motor <NUM> may output a vibration signal.

Generally, the controller <NUM> controls overall operations of the mobile device <NUM>. For example, the controller <NUM> may control overall operations of the user input interface <NUM>, the display <NUM>, the communicator <NUM>, etc. by executing the programs stored in the memory <NUM>. The controller <NUM> may perform the operations of the mobile device <NUM> described above with reference to <FIG> by executing the programs stored in the memory <NUM>.

In detail, the controller <NUM> may access the vehicle terminal <NUM> at short range by controlling the communicator <NUM>. Communication may be established between the vehicle terminal <NUM> and the mobile device <NUM> as the mobile device <NUM> approaches a range of communication of the short-distance communication module of the vehicle terminal <NUM>.

The controller <NUM> may control the communicator <NUM> to receive a license plate number from the vehicle terminal <NUM>. The controller <NUM> may receive a license plate number registered in the vehicle terminal <NUM> from the vehicle terminal <NUM> through short-range wireless communication.

The controller <NUM> may obtain purchasing item information of an item which a user desires to purchase. When the vehicle terminal <NUM> displays item information of items provided in an offline store on a screen thereof, the controller <NUM> may control the communicator <NUM> to receive the item information of the item which the user desires to purchase from the vehicle terminal <NUM> through short-range wireless communication.

Alternatively, the controller <NUM> may be connected to a server (not shown) of the offline store, receive the item information regarding the items provided in the offline store from the server, and select an item which a user desires to purchase on the basis of a user input. In this case, for example, the controller <NUM> may be connected to a web site of the offline store on the basis of a location of the mobile device <NUM>, and select the item which the user desires to purchase at the web site of the offline store.

The controller <NUM> may select a card to be used to pay for the item. The controller <NUM> may execute a payment application to pay for the item, and select one of credit cards registered in the mobile device <NUM> by using the executed payment application.

Furthermore, controller <NUM> may authenticate the user who will use the selected credit card. For example, the controller <NUM> may authenticate the user by using at least one among the user's bio-information, password, and authentication certificate but is not limited thereto.

The controller <NUM> may control the communicator <NUM> to transmit the license plate number, the purchasing item information, and card information to the payment server <NUM>. When the user who will use the selected credit card is authenticated, the controller <NUM> may request the payment server <NUM> to pay for the item by transmitting the license plate number, a settlement cost, and the card information to the payment server <NUM>.

Alternatively, the controller <NUM> may control the communicator <NUM> to transmit the card information to the vehicle terminal <NUM>, and the vehicle terminal <NUM> may transmit the license plate number, the total cost, and the card information to the payment server <NUM>.

Although it is described above that the controller <NUM> selects the credit card, exemplary embodiments are not limited thereto. For example, credit cards may be registered in the payment server <NUM> in units of mobile devices <NUM>. In this case, the controller <NUM> may provide the payment server <NUM> with an ID value of the mobile device <NUM> instead of the card information, and the payment server <NUM> may select a credit card corresponding to the ID value of the mobile device <NUM>.

Furthermore, when the mobile device <NUM> requests divided payment, the controller <NUM> may receive information regarding divided payment costs from the vehicle terminal <NUM> and authenticate a user who will pay the divided payment costs.

The sensing component <NUM> may sense a state of the mobile device <NUM> or a state of the vicinity of the mobile device <NUM> and transmit sensed information to the controller <NUM>.

The sensing component <NUM> may include at least one among a geomagnetic sensor <NUM>, an acceleration sensor <NUM>, a temperature/humidity sensor <NUM>, an infrared sensor <NUM>, a gyroscope sensor <NUM>, a position sensor (e.g., a GPS) <NUM>, a barometer sensor <NUM>, a proximity sensor <NUM>, and an RGB sensor (illuminance sensor) <NUM> but is not limited thereto. Functions of the sensors may be intuitively reasoned from the names thereof by one of ordinary skill in the art and are thus not described in detail here.

The communicator <NUM> may include one or more elements to establish communication with the vehicle terminal <NUM>, the store terminal <NUM>, the store server <NUM>, and the payment server <NUM>. For example, the communicator <NUM> may include a short-range wireless communicator <NUM>, a mobile communicator <NUM>, and a broadcast receiver <NUM>.

Examples of the short-range wireless communicator <NUM> may include, but are not limited to, a Bluetooth communication component, a Bluetooth low energy (BLE) communication component, a near-field communication component, a WLAN (Wi-Fi) communication component, a ZigBee communication component, an infrared data association (IrDA) communication component, a Wi-Fi Direct (WFD) communication component, a ultra-wideband (UWB) communication component, an Ant+ communication component, etc..

The mobile communicator <NUM> transmits a radio signal to or receives a radio signal from at least one among a base station, an external terminal, and a server in a mobile communication network. Here, the radio signal may include various types of data according to the exchange of a voice call signal, a video call signal, or a text/multimedia message.

The broadcast receiver <NUM> receives a broadcast signal and/or information related to a broadcast from the outside via a broadcast channel. The broadcast channel may include a satellite channel or a terrestrial channel. In one exemplary embodiment, the mobile device <NUM> may not include the broadcast receiver <NUM>.

Furthermore, the communicator <NUM> may exchange data for a transaction based on the license plate number with the vehicle terminal <NUM>, the store terminal <NUM>, the store server <NUM>, and the payment server <NUM>.

The memory <NUM> may store programs needed to perform processing and control by the controller <NUM>, and data to be input to or output from the mobile device <NUM>.

The memory <NUM> may include at least one among a flash memory type memory, a hard disk type memory, a multimedia card micro type memory, a card type memory (e.g., an SD or XD memory or the like), a random access memory (RAM), a static random access memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, and an optical disc.

The programs stored in the memory <NUM> may be divided into a plurality of modules according to functions thereof. For example, the programs may be classified into a user interface (UI) module <NUM>, a touch screen module <NUM>, a notification module <NUM>, etc..

The UI module <NUM> may provide a UI, a GUI, etc. which are specialized and linked to the mobile device <NUM> in units of applications. The touch screen module <NUM> may sense a user's touch gesture on a touch screen and provide information regarding the touch gesture to the controller <NUM>. In one exemplary embodiment, the touch screen module <NUM> may recognize and analyze touch code. The touch screen module <NUM> may be embodied as separate hardware including a controller.

<FIG> is a block diagram of a payment server <NUM> according to an exemplary embodiment.

Referring to <FIG>, the payment server <NUM> according to an exemplary embodiment may include a communicator <NUM>, a DB <NUM>, and a controller (processor) <NUM>.

The communicator <NUM> may include one or more elements to establish communication among the mobile device <NUM>, the store terminal <NUM>, the store server <NUM>, and the vehicle terminal <NUM>.

The DB <NUM> may store data for authenticating a transaction based on a license plate number.

Generally, the controller <NUM> controls overall operations of the payment server <NUM>. For example, the controller <NUM> may execute programs stored in the DB <NUM> of the payment server <NUM> to control overall operations of the DB <NUM>, the communicator <NUM>, etc. The controller <NUM> may execute the programs stored in the DB <NUM> to perform the operations of the payment server <NUM> described above with reference to <FIG>.

The controller <NUM> may receive a request to pay for an item from the mobile device <NUM> through the communicator <NUM>. The controller <NUM> may receive a license plate number, a list of items, information regarding a settlement cost, card information, and device information regarding the mobile device <NUM>.

The controller <NUM> may receive a request to provide a payment authentication result from the store terminal <NUM> through the communicator <NUM>.

The controller <NUM> may authenticate the payment of the item using a credit card which a user selects on the basis of the card information and the information regarding the settlement cost received from the mobile device <NUM>.

The controller <NUM> may search for the store terminal <NUM> transmitting the same license plate number as that received from the mobile device <NUM>. Furthermore, the controller <NUM> may compare information regarding a settlement cost received from the store terminal <NUM> transmitting the same license plate number as that received from the mobile device <NUM> with that regarding the total cost received from the mobile device <NUM>. The controller <NUM> may authenticate the payment of the item when an item included in purchasing item information received from the store terminal <NUM> transmitting the same license plate number as that received from the mobile device <NUM> is the same as an item included in purchasing item information received from the mobile device <NUM>. Thus, the controller <NUM> may authenticate whether an item which a user of the mobile device <NUM> desires to purchase is to be rightly paid.

The controller <NUM> may control the communicator <NUM> to transmit the payment authentication result of the item to the store terminal <NUM> and the mobile device <NUM>.

Furthermore, the controller <NUM> may register beforehand information regarding a credit card corresponding to the mobile device <NUM>. In this case, the controller <NUM> may select the credit card of the mobile device <NUM> on the basis of the device information of the mobile device <NUM>, and authenticate the payment by using the selected credit card.

Although the payment of the item provided in the offline store has been described above, exemplary embodiments are not limited thereto. The above exemplary embodiments are also applicable to paying for a service provided in the offline store.

Some exemplary embodiments may be embodied as a computer-readable recording medium having recorded thereon commands such as program modules which can be executed by a computer. The computer-readable recording medium may be any medium accessible by a computer, and include a volatile/nonvolatile medium and a separable/non-separable medium. Furthermore, the computer-readable recording medium may include a computer storage medium and a communication medium. The computer-readable recording medium may include a volatile/nonvolatile medium and a separable/non-separable medium realized according to any method or technology to store information such as computer-readable commands, data structures, program modules, or other data. In general, the communication medium includes a computer-readable command, a data structure, a program module, data of a modulated data signal, or a transmission mechanism, and may include any information transfer medium.

In the detailed description, the term "unit" or "module" should be understood to mean a hardware component such as a processor or a circuit and/or a software component executed by a hardware component such as a processor.

Exemplary embodiments described above merely provides examples and it will be understood by those of ordinary skill in the art that the present disclosure may be embodied in many different forms without departing from the scope of the present disclosure. Thus, the exemplary embodiments set forth herein should be considered in descriptive sense only and not for purposes of limitation. For example, elements described as being included in a single unit or component may be dispersed and elements described as being dispersed may be combined with one another.

Claim 1:
A system comprising a mobile device (<NUM>), a store terminal (<NUM>) and a payment server (<NUM>),
wherein the mobile device (<NUM>) comprises:
a memory storing executable instructions;
at least one communication interface configured to transmit data to or receive data from a vehicle terminal (<NUM>) and the payment server (<NUM>); and
a processor configured to provide the data for paying by executing the instructions,
wherein the instructions comprise:
receiving a license plate number from the vehicle terminal (<NUM>);
obtaining, based on a user input, purchasing item information for an item and credit card information to pay for the item;
providing, to the vehicle terminal (<NUM>), the received license plate number and the purchasing item information for the item; and
transmitting the received license plate number, a total cost of the item, device information regarding the mobile device (<NUM>) and the credit card information to the payment server (<NUM>),
wherein the store terminal (<NUM>) is configured to:
receive the license plate number and the purchasing item information from the vehicle terminal (<NUM>), and
transmit, to the payment server (<NUM>), a request for a payment authentication result comprising the license plate number and a total cost of the item based on the purchasing item information; and
wherein the payment server (<NUM>) is configured to:
authenticate payment of the item based on a comparison of the total costs received from the mobile device (<NUM>) and the store terminal (<NUM>), respectively, the store terminal (<NUM>) having transmitted the same license plate number as the license plate number received from the mobile device (<NUM>).