KR20100007640A - Mobile payment system and method using vm of mobile terminal - Google Patents

Abstract

PURPOSE: A mobile payment system and a method thereof are provided to enable payment using a mobile terminal in order to increase user convenience and reduce the cost caused by the intervention of a VAN company. CONSTITUTION: A PG(Payment Gateway) server(110) comprises a server reception unit(210), a server generation unit(220), a server transmission unit(230), a server payment unit(240), a server calculation unit(250) and a server control unit(260). The server reception unit receives a payment request message from a first portable terminal. The server generation unit(220) transmits a TID(Teleservice ID) message to a second portable terminal when receiving the payment request message. The server transmission unit transmits the payment request message to the second portable terminal according to the request from a purchaser VM(Virtual Machine) which is driven by the transmitted TID message. The server payment unit receives payment information corresponding to the payment request message from the second portable terminal, and the server calculation unit calculates the payment history based on payment information. The server control unit controls the entire operation of the PG server.

Description

Mobile payment system and method {MOBILE PAYMENT SYSTEM AND METHOD USING VM OF MOBILE TERMINAL}

Embodiments of the present invention relate to mobile payment systems and methods.

In modern society, mobile terminals are widely used as a necessity for modern people as a means of convenient communication without regard to place. However, in recent years, as the performance of the processor is improved and the resources of the memory are increased, the portable terminal provides various additional services in various fields as well as the conventional mobile communication service.

As an example of an additional service, a so-called mobile payment service has been started, which enables payment using a portable terminal which has become a necessity for modern people without having to always carry cash or a credit card for payment.

The mobile payment service means providing a payment service by accessing a financial and payment system on a wireless network using a wireless specialized terminal such as a mobile phone or a PDA. Initially, the mobile payment service method mainly used a method of transmitting a payment password using an SMS service provided by a mobile carrier along with user information using mobile phone subscriber information. The most common areas used were small payments such as paid online game access fees and paid content purchases on wired Internet.

The mobile payment market has been recently developed in a specific field as mobile phone technology advances, such as active involvement of mobile operators and financial institution participation, development of short-range wireless communication technology between mobile phones and merchant terminals, and storing financial information in the mobile phones themselves. Beyond simple micropayments, it is expanding to various financial services such as high-payment in various commerce fields.

Currently, the most widely used mobile payment method is a method in which an IC card or a smart card is mounted on a portable terminal and the payment is made by contacting the portable terminal with a reader. In other words, it is a service method in which a chip having functions of various cards such as a credit card, a transportation card, and an electronic money is mounted on a portable terminal to make payments and payments with a mobile phone. With the memory chip method, the user pays the bill by opening the phone and touching the reader like a credit card.

The present invention has been made to improve the prior art as described above, the object of the present invention is to make a payment by using a mobile terminal of the seller instead of a new terminal when the mobile payment, the cost incurred due to going through the VAN company It is to provide a mobile payment system and method that can reduce.

Another object of the present invention is to provide a mobile payment system and method that can facilitate the convenience of people moving with the payment terminal by replacing the payment terminal with the seller's portable terminal.

The object of the present invention is not limited to the above-mentioned objects, and other objects not mentioned will be clearly understood by those skilled in the art from the following description.

In order to achieve the above object and to solve the problems of the prior art, the mobile payment system according to an embodiment of the present invention, receiving a payment request message, including a phone number of the second mobile terminal, from the first mobile terminal A server receiver; A server generator for transmitting a TID message to the second mobile terminal using the telephone number; A server transmitter configured to transmit the payment request message to the second mobile terminal according to a request from a virtual machine (VM) for a buyer, which is driven in the second mobile terminal by the transmitted TID message; And a server payment unit configured to receive payment information corresponding to the payment request message from the second mobile terminal and provide the received payment information to a service server associated with a financial institution.

According to another embodiment of the present invention, a mobile payment system includes: a sales input unit which drives a seller VM and receives a phone number and a payment amount of a second mobile terminal from a seller; A sales payment request unit requesting a payment to a payment gateway (PG) server using the input telephone number and a payment amount; And a sales receiver configured to receive information regarding payment details from the PG server as response information corresponding to the payment request.

Mobile payment system according to another embodiment of the present invention, the purchase receiving unit for receiving a TID message from the PG server in connection with the payment request of the seller; A purchase driver configured to download and drive a VM for a buyer from the PG server using the received TID message; A purchase generator configured to receive a payment request message from the PG server through the driven buyer VM, and generate payment information using the received payment request message; And a purchase transmission unit for transmitting the generated payment information to the PG server.

According to an aspect of the present invention, there is provided a mobile payment method comprising: receiving, from a first portable terminal, a payment request message including a phone number of a second portable terminal; Transmitting a Teleservice ID (TID) message to the second mobile terminal using the telephone number; Transmitting the payment request message to the second mobile terminal according to a request from a virtual machine (VM) for a buyer running in the second mobile terminal by the transmitted TID message; And receiving payment information corresponding to the payment request message from the second mobile terminal and providing the received payment information to a service server associated with a financial institution.

In accordance with another aspect of the present invention, a mobile payment method includes: receiving a TID message from a PG server in association with a payment request of a seller; Downloading and driving a VM for a buyer from the PG server using the received TID message; Receiving a payment request message from the PG server through the driven buyer VM, and generating payment information using the received payment request message; And transmitting the generated payment information to the PG server.

Specific details of other embodiments are included in the detailed description and the accompanying drawings.

Advantages and features of the present invention and methods for achieving them will be apparent with reference to the embodiments described below in detail with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in various different forms, only the present embodiments to make the disclosure of the present invention complete, and common knowledge in the art to which the present invention pertains. It is provided to fully inform the person having the scope of the invention, which is defined only by the scope of the claims. Like reference numerals refer to like elements throughout.

According to an exemplary embodiment of the present invention, the payment is made by using the seller's portable terminal instead of the new terminal during the mobile payment, thereby reducing the cost incurred through the VAN company.

According to the embodiment of the present invention, by replacing the payment terminal with the seller's portable terminal, it is possible to facilitate the convenience of those who move with the payment terminal.

Hereinafter, with reference to the accompanying drawings will be described an embodiment of the present invention;

1 is a network diagram of a mobile payment system according to an embodiment of the present invention.

Referring to FIG. 1, the first mobile terminal 120 of the seller 130 drives a virtual machine (VM) for the seller, and thus the phone number of the second mobile terminal 140 of the buyer 150 from the seller 130. And receive the payment amount. In addition, the first mobile terminal 120 requests a payment to the payment gateway (PG) server 110 by using the input telephone number and the payment amount.

The PG server 110 transmits a Teleservice ID (TID) message to the second mobile terminal 140 corresponding to the input phone number according to the payment request from the first mobile terminal 120.

The second mobile terminal 140 of the purchaser 150 receives the TID message from the PG server 110, downloads and operates the VM for the buyer using the received TID message. The second portable terminal 140 requests a first request, that is, a payment request, to the PG server 110 through the driven buyer VM.

According to the first request from the second mobile terminal 140, the PG server 110 transmits the payment request content including the information about the payment amount to the second mobile terminal 140. Then, the second mobile terminal 140 receives the payment request contents from the PG server 110 and generates payment information using the received payment request contents. In addition, the second mobile terminal 140 transmits the generated payment information to the PG server 110.

The PG server 110 receives the payment information from the second mobile terminal 140 and provides the received payment information to the service server 170 associated with the financial institution 160 to perform the payment. The PG server 110 receives the information regarding the payment details from the service server 170 according to the payment, and receives the information about the received payment details from the first mobile terminal 120 and the purchaser of the seller 130. Transfer to the second mobile terminal 140 of 150. In addition, the PG server 110 may perform the settlement using the information on the payment details.

Hereinafter, a mobile payment system according to an embodiment of the present invention will be described in detail.

FIG. 2 is a block diagram illustrating the PG server 110 of FIG. 1 in more detail.

1 and 2, the PG server 110 may include a server receiver 210, a server generator 220, a server transmitter 230, a server payment unit 240, a server settlement unit 250, and The server controller 260 may be included.

The server receiver 210 receives a payment request message from the first mobile terminal 120 of the seller 130. In this case, the server receiving unit 210 may receive the payment request message from the seller's VM that is mounted and driven in the first portable terminal 120 of the seller 130.

Here, the payment request message may include information about a phone number of the second mobile terminal 140 of the buyer 150, a payment amount, a payment request place (purchase place), and the like.

Alternatively, the server receiving unit 210 may include a phone number, a payment amount, and a payment request place of the second mobile terminal of the buyer 150 from a point of sale (POS) terminal, a credit application terminal (CAT) terminal, or a web server. A payment request message including information regarding (purchase place) and the like can be received.

When the server generation unit 220 receives the payment request message, the server generation unit 220 transmits a teleservice ID (TID) message to the second mobile terminal 140. That is, the server generation unit 220 transmits a TID (Teleservice ID) message to the second mobile terminal 140 by using the phone number in the received payment request message.

Specifically, the server generator 220 includes an application for downloading and driving the buyer VM, and generates the TID message. The server generator 220 extracts the phone number from the received payment request message and transmits the generated TID message to the second mobile terminal 140 using the extracted phone number.

As such, the server generator 220 may transmit the generated TID message to the second mobile terminal 140 so that the buyer VM is downloaded and driven in the second mobile terminal 140. As a result, the purchaser 150 may prepare a mobile payment environment using the purchaser VM in the second portable terminal 140.

The server transmitter 230 transmits the payment request message to the second mobile terminal 140 in response to a request from the purchaser VM driven by the transmitted TID message. That is, the server transmitting unit 230, according to the request from the buyer VM, the information regarding the phone number of the second mobile terminal 140 of the buyer 150, payment amount, payment request place (purchase place) and the like. 2 is transmitted to the mobile terminal 140.

The server payment unit 240 receives payment information corresponding to the payment request message from the second mobile terminal 140. The server payment unit 240 provides the received payment information to the service server 170 associated with a financial institution 160, such as a card company, a bank.

As described above, the server payment unit 240 may perform various payments by using the seller VM and the buyer VM mounted in the first and second portable terminals 120 and 140, respectively.

Here, the payment information may include information about a payment medium, payment conditions, etc., and also includes a phone number of the second mobile terminal 140 included in the payment request message, a payment amount, a payment request place (purchase location), and the like. Information may also be included.

The payment medium may be a credit card (credit card number, expiration date, password, etc.), bank transfer (bank name, account number, etc.), phone bill (cell phone number, authentication number, etc.), points (point card number, password) Etc.), a check card (check card number, expiration date, password, etc.). The payment condition may include an installment or the like.

The server payment unit 240 receives information regarding a payment history as a response to the payment information from the service server 170. The server payment unit 240 transmits the information regarding the received payment details to the first portable terminal 120 and the second portable terminal 140.

Alternatively, the server payment unit 240 includes a second phone number of the third mobile terminal of the second buyer associated with the buyer from the second mobile terminal 140 in response to the payment request message. You can receive a message. In this case, the server transmitter 230 may transmit the second payment request message to the third mobile terminal.

The server payment unit 240 receives the second payment information corresponding to the second payment request message from the third mobile terminal, and provides the received second payment information to the service server 170, thereby providing the second payment information. The purchaser 150 may pay through the buyer. In addition, the server payment unit 240 receives a payment history as a response to the second payment information from the service server 170, and the received payment details to the first portable terminal 120, the second portable terminal 140 ), And the third mobile terminal.

Alternatively, the server payment unit 240 may include a second phone number and a payment amount of the third mobile terminal of the second buyer from the VM for the seller of the second mobile terminal 140 in response to the payment request message. The second payment request message may be received. To this end, the second mobile terminal 140 may download and drive the seller VM through a WAP, a callback URL, and the like. The server payment unit 240 transmits the second payment request message (including the remittance request information through a bank transfer) to the third mobile terminal by using the received second phone number, and transmits the information from the third mobile terminal. Second payment information corresponding to the second payment request message may be received.

In this case, the server payment unit 240 includes the TID message in the second payment request message or transmits the TID message to the third mobile terminal separately from the second payment request message, thereby transmitting the third mobile phone. In the terminal, the second purchaser VM may be downloaded and driven. The server payment unit 240 includes payment account information (bank name, account number, password, etc.) of the second buyer from the driven second buyer VM in response to the second payment request message. The second payment information may be received.

The server payment unit 240 may provide the received second payment information to the service server 170 to perform payment of the buyer 150 through the second buyer. In addition, the server payment unit 240 receives a payment history as a response to the second payment information from the service server 170, and the received payment details to the first portable terminal 120, the second portable terminal 140 ), And the third mobile terminal.

Meanwhile, the server payment unit 240 may transmit the payment details to a fourth mobile terminal of a third party (eg, a parent, a parcel delivery company, a head office of the seller 130, etc.) set in advance by the buyer 150. . In this case, the server payment unit 240 may deliver the payment details to the fourth mobile terminal through a message such as a short message service (SMS).

The server settlement unit 250 calculates the payment details by using the information on the payment details. In this case, the server settlement unit 250 may settle the payment details on a predetermined cycle basis (for example, one month, one week, etc.). In addition, the server settlement unit 250 may generate statistical information by using the settlement result, and may analyze the created statistical information to calculate information on a purchase flow of goods and the like.

The server controller 260 controls the overall PG server 110 of FIG. 1. That is, the server controller 260 may control operations of the server receiver 210, the server generator 220, the server transmitter 230, the server payment unit 240, and the server settlement unit 250.

Although not shown in FIG. 2, the PG server 110 may further include a server issuing unit.

The server receiving unit 210 may receive a payment request message further including cash receipt issuing request information from the first mobile terminal 120. That is, the server receiving unit 210 may receive a payment request message further including the cash receipt issuing request information from the seller VM, which is driven in the first portable terminal 120 and equipped with a cash receipt issuing menu.

In this case, the server issuing unit may transmit the cash receipt issuance request information to a cash receipt issuing institution and request the cash receipt. In addition, the server issuing unit may receive a cash receipt from the cash issuance related institution in response to the issuance request, and provide the cash receipt to the first portable terminal 120 or the second portable terminal 140.

In the above embodiment, the case where the purchaser VM is not previously installed in the second portable terminal 140 has been described. Next, as another embodiment, the case where the purchaser VM is pre-installed in the second portable terminal 140 will be described.

The PG server 110 receives a payment request message from the first mobile terminal 120 of the seller 130, including information about a phone number, a payment amount, etc. of the second mobile terminal 140 of the buyer 150. do. The PG server 110 drives the buyer VM, which is preloaded in the second mobile terminal 140 corresponding to the phone number, in association with the reception of the payment request message. To this end, the PG server 110 searches for the second mobile terminal 140 using the phone number and transmits a driving related signal for driving the buyer VM to the searched second mobile terminal 140. Can be.

The PG server 110 transmits the payment request message to the second mobile terminal 140 in response to a request from the driven buyer VM. The PG server 110 receives payment information corresponding to the payment request message from the second mobile terminal 140, and provides the received payment information to the service server 170 linked with the financial institution 160. Payment will be performed.

3 is a block diagram illustrating the first portable terminal 120 of FIG. 1 in more detail.

1 and 3, the first mobile terminal 120 may include a sales register 310, a sales inputter 320, a sales payment requester 330, a sales receiver 340, and a sales controller 350. It may include.

The sales registration unit 310 downloads a VM for a seller by using a WAP or a callback URL (Uniform Resource Locator). The sales registration unit 310 requests the PG server 110 to register the downloaded VM for seller.

In detail, the sales registration unit 310 receives a unique identification number such as a business registration number from the seller 130. The sales registration unit 310 generates a unique ID that matches the phone number of the first mobile terminal 120 of the seller 130 by using the inputted unique identification number. The sales registration unit 310 requests the PG server 110 to register the VM for sellers using the generated unique ID.

In this case, the sales registration unit 310 may associate the phone numbers of the plurality of first portable terminals 120 with one unique identification number. To this end, the sales registration unit 310 may generate a unique ID that matches the phone number of each first mobile terminal 120 for each of the plurality of sellers 130 using one unique identification number.

When the seller VM is registered in the PG server 110 in response to the registration request, the sales input unit 320 drives the registered seller VM so that the second portable terminal of the buyer 150 is sold from the seller 130. Receive a phone number and payment amount of 140.

The sales payment request unit 330 requests a payment to the PG server 110 using the inputted phone number and payment amount. That is, the sales payment request unit 330 generates a payment request message including the input telephone number and information on the payment amount, and transmits the generated payment request message to the PG server 110. In this case, the sales payment request unit 330 may encrypt the generated payment request message and transmit the encrypted payment request message to the PG server 110.

The sales receiving unit 340 receives response information corresponding to the payment request, that is, information about payment details, from the PG server 110.

The sales controller 350 generally controls the first portable terminal 120 of FIG. 1. That is, the sales controller 350 may control operations of the sales register 310, the sales inputter 320, the sales payment requester 330, and the sales receiver 340.

FIG. 4 is a block diagram illustrating the second portable terminal 140 of FIG. 1 in more detail.

Referring to FIGS. 1 and 4, the second mobile terminal 140 includes a purchase receiver 410, a purchase driver 420, a purchase generator 430, a purchase transmitter 440, and a purchase controller 450. It may include.

The purchase receiving unit 410 receives a TID message from the PG server 110 in connection with the payment request of the seller 130. That is, when the PG server 110 receives a payment request from the first mobile terminal 120 of the seller 130, the purchase receiving unit 410 receives the TID message from the PG server 110.

The purchase driver 420 downloads and drives the VM for the buyer by using the received TID message. In this case, the purchase driver 420 may download the buyer VM using a WAP or a call-back Uniform Resource Locator (URL).

In detail, the purchase driver 420 extracts an application for downloading and driving the purchaser VM from the received TID message, and downloads the buyer VM by executing the extracted application. When the purchase driver 420 downloads the buyer VM, the purchase driver 420 requests the PG server 110 to register the buyer VM using a unique identification number (PIN ID) set by the buyer 150. When the buyer VM is registered according to the registration request, the purchase driver 420 drives the downloaded buyer VM.

The purchase generation unit 430 receives a payment request message from the PG server 110 through the driven buyer VM, and generates payment information using the received payment request message. In this case, the payment information may include information regarding a payment medium, payment conditions, and the like, and also includes a phone number, payment amount, and payment request place of the second mobile terminal 140 included in the payment request message. Information about the place of purchase may also be included.

Alternatively, the purchase generation unit 430 receives information regarding payment media or payment terms (information that the buyer 150 may use by default) from the buyer 150, and inputs the payment media or Information about payment terms can be encrypted and stored. In this case, the purchase generation unit 430 may store the information about the encrypted payment medium or payment terms in the second portable terminal 140 or a separate independent server.

The purchase generation unit 430 obtains information about the stored payment medium or payment condition by using the unique identification number set by the buyer 150, and further uses the information about the obtained payment medium or payment condition. To generate the payment information.

That is, the purchase generator 430 may generate the payment information by using the received payment medium or the information about the payment condition together with the received payment request message.

On the other hand, when the purchase generation unit 430 receives a change request for the payment information from the buyer 150, it may change the payment information. That is, the purchase generation unit 430 may change a payment medium such as a credit card, a bank transfer, a phone bill, a point check card, or a payment condition such as an installment to correspond to the change request.

The purchase transmitter 440 transmits the generated payment information to the PG server 110. In this case, the purchase transmitter 440 may encrypt the generated payment information and transmit the encrypted payment information to the PG server 110.

The purchase controller 450 generally controls the second portable terminal 140 of FIG. 1. That is, the purchase controller 450 may control operations of the purchase receiver 410, the purchase driver 420, the purchase generator 430, and the purchase transmitter 440.

In the above embodiment, the case where the purchaser VM is not previously installed in the second portable terminal 140 has been described. Next, as another embodiment, the case where the purchaser VM is pre-installed in the second portable terminal 140 will be described.

The second portable terminal 140 receives the payment request message from the PG server 110 by driving the VM for the buyer. The second mobile terminal 140 generates the payment information by using the received payment request message. The second mobile terminal 140 transmits the generated payment information to the PG server.

5 is a flowchart illustrating a mobile payment method according to an embodiment of the present invention. Here, the mobile payment method may be implemented by a server mobile payment system mounted in the PG server 110 of FIG.

1 and 5, in step S510, the server mobile payment system receives a payment request message from the first mobile terminal 120 of the seller 130. In this case, the server mobile payment system may receive the payment request message from the seller VM that is mounted and driven in the first portable terminal 120 of the seller 130.

Here, the payment request message may include information about a phone number of the second mobile terminal 140 of the buyer 150, a payment amount, a payment request place (purchase place), and the like.

Next, in step S520, when the server mobile payment system receives the payment request message, the server mobile payment system transmits a teleservice ID (TID) message to the second mobile terminal 140. That is, the server mobile payment system transmits a Teleservice ID (TID) message to the second mobile terminal 140 by using the phone number in the received payment request message.

In detail, the server mobile payment system includes an application for downloading and driving the VM for the buyer to generate the TID message. The server mobile payment system extracts the phone number from the received payment request message and transmits the generated TID message to the second mobile terminal 140 using the extracted phone number.

As described above, the server mobile payment system may transmit the generated TID message to the second mobile terminal 140 so that the buyer VM is downloaded and driven in the second mobile terminal 140. As a result, the purchaser 150 may prepare a mobile payment environment using the purchaser VM in the second portable terminal 140.

Next, in step S530, the server mobile payment system transmits the payment request message to the second mobile terminal 140 in response to a request from the buyer VM driven by the transmitted TID message. That is, the server mobile payment system, in response to a request from the VM for the buyer, provides information about a phone number, a payment amount, a payment request location (purchase location), etc. of the second mobile terminal 140 of the buyer 150. Transfer to the mobile terminal 140.

Next, in step S540, the server mobile payment system receives payment information corresponding to the payment request message from the second mobile terminal 140.

Next, in step S550, the server mobile payment system provides the received payment information to the service server 170 associated with financial institutions 160, such as card companies, banks. As described above, the server mobile payment system may perform various payments using the seller VM and the buyer VM mounted in the first and second portable terminals 120 and 140, respectively.

Here, the payment information may include information about a payment medium, payment conditions, etc., and also includes a phone number of the second mobile terminal 140 included in the payment request message, a payment amount, a payment request place (purchase location), and the like. Information may also be included.

The payment medium may be a credit card (credit card number, expiration date, password, etc.), bank transfer (bank name, account number, etc.), phone bill (cell phone number, authentication number, etc.), points (point card number, password, etc.), check Card (check card number, expiration date, password, etc.) and the like. The payment condition may include an installment or the like.

Next, in step S560, the server mobile payment system receives the information on the payment history as a response to the payment information from the service server 170.

Next, in step S570, the server mobile payment system transmits the information regarding the received payment details to the first mobile terminal 120 and the second mobile terminal 140.

Next, in step S580, the server mobile payment system calculates the payment details using the information on the payment details. In this case, the server mobile payment system may settle the payment details on a regular basis (for example, one month, one week, etc.). The server mobile payment system may generate statistical information by using the settlement result, and may calculate information on a purchase flow of goods by analyzing the created statistical information.

6 is a flowchart illustrating a mobile payment method according to another embodiment of the present invention. In this case, the mobile payment method may be implemented by a sales mobile payment system mounted in the first portable terminal 120 of FIG. 1.

1 and 6, in step S610, the selling mobile payment system downloads a seller VM using a WAP or a call-back Uniform Resource Locator (URL).

Next, in step S620, the sales mobile payment system requests the registration of the downloaded VM for seller to the PG server 110.

Specifically, the sales mobile payment system receives a unique identification number, such as a business registration number from the seller 130, using the inputted unique identification number, the phone of the first mobile terminal 120 of the seller 130 Create a unique ID that matches a number. In addition, the sales mobile payment system requests the seller VM to register with the PG server 110 using the generated unique ID.

In this case, the sales mobile payment system may associate the phone numbers of the plurality of first portable terminals 120 with one unique identification number. To this end, the sales mobile payment system may generate a unique ID that matches the phone number of each first mobile terminal 120 for each of the plurality of sellers 130 using one unique identification number.

Next, in step S630, when the seller VM is registered in the PG server 110 by the registration request, the sales mobile payment system drives the registered seller VM from the seller 130. The phone number and payment amount of the second mobile terminal 140 of the purchaser 150 are input.

Next, in step S640, the sales mobile payment system requests a payment to the PG server 110 using the input telephone number and the payment amount. That is, the sales mobile payment system generates a payment request message, which includes information about the input telephone number and payment amount, and transmits the generated payment request message to the PG server 110. In this case, the sales mobile payment system may encrypt the generated payment request message and transmit the encrypted payment request message to the PG server 110.

Next, in step S650, the sales mobile payment system receives response information corresponding to the payment request, that is, information on payment details, from the PG server 110.

7 is a flowchart illustrating a mobile payment method according to another embodiment of the present invention. Here, the mobile payment method may be implemented by a purchase mobile payment system mounted in the second portable terminal 140 of FIG. 1.

1 and 7, in step S710, the purchase mobile payment system receives a TID message from the PG server 110 in association with a payment request of the seller 130. That is, when the PG server 110 receives the payment request from the first mobile terminal 120 of the seller 130, the purchase mobile payment system receives the TID message from the PG server 110.

Next, in step S720, the purchase mobile payment system downloads and runs a VM for a buyer using the received TID message. In this case, the purchase mobile payment system may download the VM for the buyer by using a WAP or a call-back Uniform Resource Locator (URL).

In detail, the purchase mobile payment system extracts an application for downloading and driving the buyer VM from the received TID message, and downloads the buyer VM by executing the extracted application. The purchase mobile payment system requests the PG server 110 to register the buyer VM using the unique identification number set by the buyer 150 when the buyer VM is downloaded. When the buyer VM is registered according to the registration request, the purchase mobile payment system drives the downloaded buyer VM.

Next, in step S730, the purchase mobile payment system receives a payment request message from the PG server 110 through the driven buyer VM.

Next, in step S740, the purchase mobile payment system generates payment information using the received payment request message. In this case, the payment information may include information regarding a payment medium, payment conditions, and the like, and also includes a phone number, payment amount, and payment request place of the second mobile terminal 140 included in the payment request message. Information about the place of purchase may also be included.

In addition, the purchase mobile payment system receives the information regarding the payment medium or payment conditions (information that the buyer 150 can use by default) from the buyer 150, the input payment medium or payment Information about the condition can be encrypted and stored. The generation unit 430 obtains information about the stored payment medium or payment condition by using the unique identification number set by the purchaser 150, and further uses information about the obtained payment medium or payment condition. The payment information may be generated.

That is, the purchase mobile payment system may generate the payment information by using the information about the obtained payment medium or payment condition together with the received payment request message.

Next, in step S750, the purchase mobile payment system transmits the generated payment information to the PG server 110. In this case, the purchase mobile payment system may encrypt the generated payment information and transmit the encrypted payment information to the PG server 110.

Next, in step S760, the purchase mobile payment system receives the information on the payment details in response to the payment information from the PG server 110.

Embodiments of the invention include a computer readable medium containing program instructions for performing various computer-implemented operations. The computer readable medium may include program instructions, local data files, local data structures, or the like, alone or in combination. The media may be those specially designed and constructed for the purposes of the present invention, or they may be of the kind well-known and available to those having skill in the computer software arts. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tape, optical recording media such as CD-ROMs, DVDs, magnetic-optical media such as floppy disks, and ROM, RAM, flash memory, and the like. Hardware devices specifically configured to store and execute the same program instructions are included. Examples of program instructions include not only machine code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like.

As described above, according to embodiments of the present invention, when the mobile payment is made by using the seller's portable terminal instead of the new terminal, the cost incurred through the VAN company can be reduced.

In addition, according to embodiments of the present invention, by replacing the payment terminal with the seller's portable terminal, it is possible to facilitate the convenience of those who move with the payment terminal. For example, according to embodiments of the present invention, a very large payment terminal is carried at the time of a delivery order or a surrogate operation such as a pizza, and this can be replaced with a mobile terminal to facilitate convenience of a pizza delivery or a surrogate driver. Can be.

While specific embodiments of the present invention have been described so far, various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be determined not only by the claims below, but also by the equivalents of the claims.

As described above, the present invention has been described by way of limited embodiments and drawings, but the present invention is not limited to the above-described embodiments, which can be variously modified and modified by those skilled in the art to which the present invention pertains. Modifications are possible. Accordingly, the spirit of the present invention should be understood only by the claims set forth below, and all equivalent or equivalent modifications thereof will belong to the scope of the present invention.

1 is a network diagram of a mobile payment system using a VM of a mobile terminal according to an embodiment of the present invention.

FIG. 2 is a block diagram illustrating the PG server of FIG. 1 in more detail.

FIG. 3 is a block diagram illustrating the first portable terminal of FIG. 1 in more detail.

4 is a block diagram illustrating the second portable terminal of FIG. 1 in more detail.

5 is a flowchart illustrating a mobile payment method using a VM of a mobile terminal according to an embodiment of the present invention.

6 is a flowchart illustrating a mobile payment method using a VM of a mobile terminal according to another embodiment of the present invention.

7 is a flowchart illustrating a mobile payment method using a VM of a mobile terminal according to another embodiment of the present invention.

<Explanation of symbols for the main parts of the drawings>

110: PG server 120: first portable terminal

140: second mobile terminal 160: financial institution

170: service server 210, 340, 410: receiving unit

220, 430: generator 230, 440: transmitter

240: payment unit 250: payment unit

260, 350, 450: control unit 310: register

320: input unit 330: payment request unit

420: drive unit

Claims (24)

A server receiver configured to receive a payment request message from a first portable terminal, the telephone number of the second portable terminal; A server generator for transmitting a TID message to the second mobile terminal using the telephone number; A server transmitter configured to transmit the payment request message to the second mobile terminal according to a request from a virtual machine (VM) for a buyer, which is driven in the second mobile terminal by the transmitted TID message; And A server payment unit that receives payment information corresponding to the payment request message from the second mobile terminal and provides the received payment information to a service server associated with a financial institution. Mobile payment system comprising a. The method of claim 1, The server generation unit, Mobile payment system, characterized in that for generating the TID message, including the application for downloading and driving the VM for the buyer. The method of claim 1, The server receiving unit, And the payment request message from the seller VM running in the first portable terminal. The method of claim 1, The server payment unit, The mobile payment system, characterized in that for receiving the information about the payment history in response to the payment information from the service server to the first mobile terminal or the second mobile terminal. The method of claim 1, The server payment unit, (1) receiving a second payment request message including a second telephone number of a third mobile terminal from the second mobile terminal in response to the payment request message; (2) transmitting the second payment request message to the third mobile terminal by using the received second telephone number, and receiving second payment information corresponding to the second payment request message from the third mobile terminal. Receive, (3) providing the received second payment information to the service server. The method of claim 1, When receiving the payment request message further including the cash receipt issuance request information from the first portable terminal, A server for transmitting the cash receipt issuance request information to a cash receipt issuing institution, receiving a cash receipt from the cash receipt issuing agency, and providing the issued cash receipt to the first mobile terminal or the second mobile terminal. Issuer Mobile payment system characterized in that it further comprises. The method of claim 1, When receiving the information on the payment history in response to the payment information from the service server, Server settlement unit for calculating the payment details Mobile payment system characterized in that it further comprises. A sales input unit which drives a seller VM and receives a phone number and a payment amount of a second mobile terminal from a seller; A sales payment request unit requesting a payment to a payment gateway (PG) server using the input telephone number and a payment amount; And Sales receiving unit for receiving information on the payment history as response information corresponding to the payment request from the PG server Mobile payment system comprising a. The method of claim 8, The sales registration unit which downloads the seller VM and requests registration of the downloaded seller VM to the PG server. Mobile payment system characterized in that it further comprises. The method of claim 9, The sales register, Using a unique identification number input by the seller, generates a unique ID matching the telephone number of the first mobile terminal, Mobile payment system, characterized in that for using the generated unique ID, the seller VM registration request to the PG server. A purchase receiving unit receiving a TID message from a PG server in association with a payment request of a seller; A purchase driver configured to download and drive a VM for a buyer from the PG server using the received TID message; A purchase generator configured to receive a payment request message from the PG server through the driven buyer VM, and generate payment information using the received payment request message; And Purchase transmission unit for transmitting the generated payment information to the PG server Mobile payment system comprising a. The method of claim 11, The purchase driving unit, (1) extracting an application from the received TID message, executing the extracted application and downloading the buyer VM; (2) a registration request relating to the downloaded VM for a buyer to the PG server, (3) The mobile payment system, characterized in that for driving the VM for the buyer as the registration is made in the PG server based on the registration request. The method of claim 10, The purchase driving unit, Mobile payment system, characterized in that the registration request to the PG server using a unique identification number set by the buyer. The method of claim 11, The purchase driving unit, Extracting a second application from the received TID message, executing the extracted second application to download a seller VM, As the downloaded seller VM is registered in the PG server, the seller VM is driven to transmit a second payment request message including a second phone number and a payment amount of a second mobile terminal to the PG server. Mobile payment system characterized by. The method of claim 11, If information about the payment medium or payment terms entered by the buyer is encrypted, The purchase generation unit, Obtaining information about the encrypted payment medium or payment terms using a unique identification number set by the buyer, The mobile payment system, characterized in that for generating the payment information further using information on the obtained payment medium or payment conditions. The method of claim 11, The purchase transmission unit, And encrypting the generated payment information and transmitting the encrypted payment information to the PG server. Receiving, from the first portable terminal, a payment request message including a telephone number of the second portable terminal; Transmitting a Teleservice ID (TID) message to the second mobile terminal using the telephone number; Transmitting the payment request message to the second mobile terminal according to a request from a virtual machine (VM) for a buyer running in the second mobile terminal by the transmitted TID message; And Receiving payment information corresponding to the payment request message from the second mobile terminal and providing the received payment information to a service server associated with a financial institution; Mobile payment method comprising a. The method of claim 17, The step of transmitting a TID (Teleservice ID) message to the second mobile terminal using the telephone number, Generating the TID message including an application for downloading and driving the buyer VM; Mobile payment method comprising a. The method of claim 17, Receiving information on the payment history as a response to the payment information from the service server and transmitting to the first mobile terminal or the second mobile terminal Mobile payment method characterized in that it further comprises. The method of claim 17, When receiving the information on the payment history in response to the payment information from the service server, Calculating the payment details Mobile payment method characterized in that it further comprises. Receiving a TID message from a PG server in association with a seller's payment request; Downloading and driving a VM for a buyer from the PG server using the received TID message; Receiving a payment request message from the PG server through the driven buyer VM, and generating payment information using the received payment request message; And Transmitting the generated payment information to the PG server. Mobile payment method comprising a. The method of claim 21, Downloading and driving a VM for a buyer from the PG server using the received TID message, Extracting an application from the received TID message and downloading the buyer VM by executing the extracted application; Making a registration request relating to the downloaded VM for a buyer to the PG server; And Driving the VM for the buyer as the registration is made in the PG server based on the registration request; Mobile payment method comprising a. The method of claim 22, The requesting registration relating to the downloaded VM for the buyer to the PG server, Requesting the registration to the PG server using a unique identification number set by a purchaser Mobile payment method comprising a. The method of claim 21, If information about the payment medium or payment terms entered by the buyer is encrypted, Generating payment information by using the received payment request message, Acquiring information about the encrypted payment medium or payment terms using a unique identification number set by the buyer; And Generating the payment information by further using information about the obtained payment medium or payment condition; Mobile payment method comprising a.

Images