KR20040093582A - Apparatus and Method for Mobile Payment, Mobile Communication System - Google Patents

Abstract

PURPOSE: A mobile settlement device, and a mobile communication system and a mobile settlement method equipped with the same are provided to simplify a customer authentication procedure without a process for generating/transmitting a random number by using authentication data previously registered to the mobile communication system for a settlement process using the mobile communication terminal. CONSTITUTION: A PG(Payment Gateway)(610) collects the authentication data from the mobile communication terminal by being connected between the mobile communication terminal and an CP(Contents Provider) server, collects settlement information from the CP server, and transmits a charge settlement result depending on the settlement information to the CP server and the mobile communication terminal. An ISAS(Internet Shopping Authentication System) serve(620) performs the user authentication by receiving the authentication data from the PG, processes the charge by using the settlement information received from the PG if the user is a legal user, and generates charge settlement data for the CP server depending on contents purchase particulars of each user.

Description

Mobile payment device, mobile communication system and mobile payment method having the same {Apparatus and Method for Mobile Payment, Mobile Communication System}

The present invention relates to a payment system and method using a mobile communication terminal, and more particularly to a mobile payment device and method for simplifying a customer authentication process, and a mobile communication system for the same.

Recently, a micro payment service is being activated, in which payment for content purchased online or offline is added to a mobile communication service fee. Small payment service using a mobile communication terminal to compensate for the shortcomings of credit card payment, credit card payment has a problem that it is difficult to maintain a small payment and security. Micropayment has the advantage of preventing the leakage of credit information by enabling the payment of the purchase price in real time using a mobile communication terminal number instead of entering credit information such as a credit card number and a bank account number.

8 is a diagram illustrating a general mobile payment method.

When a customer who subscribes to a mobile communication service connects to a content provider (CP) server 90 using a personal computer 100 or the like and requests to select and purchase desired content (S501), the CP server 90 acts as a payment agent. The system 110 transmits customer information (resident registration number, mobile communication terminal number, etc.) to request that the user be authenticated as a legitimate user (S502). Accordingly, the payment agency system 110 requests authentication by transmitting customer information to the mobile communication system 120 (S503), and the mobile communication system performs authentication with reference to the customer information to the payment agency system 110. When the authentication result is transmitted, a random number is also transmitted when it is determined to be a legitimate user (S504). The payment agency system 110 receiving the authentication result and the random number transmits the authentication result and the random number to the CP server 90, and the mobile communication system 120 transmits the random number to the mobile communication terminal of the customer in a text message ( S506).

After receiving the random number, the customer enters a random number on the payment page of the CP server 90 (S507), the CP server 90 compares the random number input from the customer and the random number transmitted from the payment agent system 10 Check whether the same (S508). If the result of the check is the same random number, the CP server 90 transmits the payment information (customer information, purchased goods, purchase price, CP server information, etc.) to the payment agency system 110 (S509), payment agency system 110 The payment information is transmitted to the mobile communication system 120 (S510) to be added to the mobile communication service usage fee of the customer.

The mobile communication system 120 includes the content purchase price in the customer's mobile communication service bill payment bill (S511), and according to the customer pays the purchase price (S512), the mobile communication system 120 and the payment agent system ( 110, the settlement is made between the payment agent system 110 and the CP server 90 (S513, S514).

As described above, in the case of micropayment using the current mobile communication terminal, the payment agent system 110 served as a relay between the CP server 90 and the mobile communication system 120 in the processing of user authentication and payment. Accordingly, the CP server 90 operator has a disadvantage in that a fee must be repeatedly paid to the operator of the mobile communication system 120 and the payment agent system 110.

In addition, when authenticating a user for micropayment, a random number generated by the mobile communication system 120 is currently used. The random number is transmitted to the CP server 90 and the mobile communication terminal 10, and a random number is received from the user. The authentication procedure is complicated, such as a comparison process, and data may be lost when random numbers are transmitted.

The present invention has been made to solve the problems and disadvantages described above, the authentication data unique to the mobile communication terminal user in the payment process using the mobile communication terminal and authentication data registered in the mobile communication system when the mobile communication service subscription (eg For example, it is an object of the present invention to provide a mobile payment device and method that can simplify the customer authentication process without performing a separate random number generation, transmission, etc. by using a social security number.

Another object of the present invention is to be charged to the content provider by performing a micropayment using the authentication and payment module built in the mobile communication system without the payment agent system relaying the payment and authentication in the content provider server and the mobile communication system The fee can be reduced, and thus the content price can be reduced.

1 is a view for explaining a mobile communication system having a mobile payment device according to the present invention;

2 is a detailed configuration diagram of the mobile payment device shown in FIG. 1;

3 is a flowchart illustrating a mobile payment method according to the present invention;

4 to 6 is a flow chart for explaining the authentication data collection procedure in the mobile payment method according to the present invention,

7 is a flowchart illustrating a mobile payment cancellation procedure according to the present invention;

8 is a diagram illustrating a general mobile payment method.

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

10: mobile communication terminal 20: base station / base international controller

30: exchanger 40: interlocking device

50: gateway 60: mobile payment device

70: Data Core Network 80: Internet

90: content provider server 100: personal computer

110: payment agency system 120: mobile communication system

610: payment gateway 611: communication network interface

613: database management unit 615: ISAS format processing unit

617: authentication and payment request unit 619: I / O processing unit

620: ISAS server 621: customer authentication unit

623: approval processing unit 625: billing processing unit

627: payment settlement 629: I / O processing

630: Database 631: CP Information Database

633: Purchase history database 635: Sumi payment information database

The present invention for achieving the above object is connected to a plurality of content provider server through a communication network, the mobile communication terminal user who purchased the content from the content provider server to pay a small amount of the content purchase price mobile communication service A mobile communication system for processing by adding up a usage fee, the mobile communication system receiving authentication data from a mobile communication terminal user requesting the micro payment and performing the user authentication, and performing charging if the user is a legitimate user. And generating billing information and storing the billing information together with the mobile communication service usage fee, and transmitting the billing result to the content provider server and the mobile communication terminal, wherein the authentication data is the user. Mobile communication System as characterized in that the service registration of registration data.

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

1 is a view for explaining an application example of a mobile payment device according to the present invention.

The content purchaser can access the CP server 90 by wire or wireless connection using a communication terminal such as the mobile communication terminal 10 or the personal computer 100 to select and purchase the desired content or the content in an offline store. You can buy it. Payment and settlement according to the content purchase can be made in a variety of ways, such as small payments, credit card payments, electronic money payments using a mobile communication terminal will be described only in the payment settlement method by a small payment.

The mobile communication terminal 10 is connected to a base station / base station controller (BTS / BSC) 20 for wireless section communication between the mobile communication terminal 10 and the mobile communication system 120 and one or more base stations to perform a call exchange. When connected to the mobile payment device 60 through the IWF (Inter Working Function 40) and the gateway 50 as an interface for supporting the data service to the user of the exchange 30, the mobile communication terminal 10, the content payment is made. Authentication and payment process is performed through the data transmission and reception with the mobile payment device 60.

On the other hand, the mobile communication terminal 10 is a CP server connected to the Internet 80 through the base core / base station controller 20 and the data core network (DCN, 70) for performing signal conversion for providing wireless Internet service The user may access 90 to view, use, and purchase content.

When the mobile terminal 10 user requests payment to the mobile payment device 60 using the mobile terminal 10 in order to select content online or offline and pay for the content in a small payment method, mobile payment The payment device 60 requests payment information from the CP server 90. The mobile payment device 60 receiving payment information from the CP server 90 collects authentication data according to the authentication environment of the mobile communication terminal 10 and performs authentication using the same. Here, it is preferable that authentication data uses a social security number. This is because the user registers the resident registration number in the mobile communication system 120 when the user subscribes to the mobile communication service and is personalized identification information. In this respect, the authentication data may use data registered in the mobile communication system 120 with the customer when the mobile communication service is subscribed.

When the authentication is completed by the personalized identification information, the mobile payment device 60 performs the charging with reference to the payment information and transmits the result to the CP server 90 and the mobile communication terminal 10.

The mobile communication system 120 further includes a billing management system 130, and stores and manages all billing information through the mobile communication system 120, such as voice call charges and data service charges through the mobile communication terminal 10. Accordingly, monthly billing data is generated and managed, and storage and management information for each user, unpaid information, and the like are stored.

As described above, in the mobile payment according to the present invention, the mobile communication system 120 generates a random number for authenticating whether the content purchaser and the owner of the mobile communication terminal 10 are the same user, and the CP server 90 and the mobile communication terminal. Since the user authentication is performed using the authentication data registered when the mobile communication service is subscribed without the procedure of transmitting to (10), the authentication process can be simplified.

The mobile payment device 60 is divided into a functional unit which is connected between the mobile communication terminal 10 and the CP server 90 to perform authentication data collection, payment information collection, etc., and a functional unit that performs user authentication and billing processing. In this case, the mobile payment device 60 is configured as shown in FIG. 2. In addition, although the mobile payment device 60 of the present invention is preferably operated in the mobile communication system 120, it is also possible to operate by an operator independent of the mobile communication system 120.

FIG. 2 is a detailed configuration diagram of the mobile payment device shown in FIG. 1.

The mobile payment device 60 is connected between the mobile communication terminal 10 and the CP server 90 to perform authentication data collection, payment information collection, and the like, and transmit a processing result, and user authentication and billing. An authentication / billing server (hereinafter referred to as an 'ISAS server') server 320 that performs the processing.

First, the payment gateway 610 is a communication network interface 611 for communicating with the gateway 50 for communicating with the mobile communication terminal 10, the CP server 90, user information, purchase history for each user, user Database management unit 613 for managing payment details, CP information, etc., ISAS format processing unit 615 for transmitting and receiving data with ISAS, and requesting authentication data input to the mobile communication terminal 10, to the CP server 90 Request for payment information for each user, and includes an authentication and payment request unit 617 for performing authentication request, billing request, payment request, etc. to the ISAS server 620 and I / O processing unit 619 for data input and output processing do.

The ISAS processing unit 620, upon request of the payment gateway 610, refers to the customer authentication unit 621 to confirm whether the user is a legitimate user, and confirms the payment authorization information when the user authentication unit 621 is confirmed as a legitimate user. Authorization processing unit 623 for generating and transmitting to payment gateway 610, Billing processing unit 625 for generating and storing billing information by receiving content payment information of a user who has been approved for payment from payment gateway 610, Mobile communication The terminal 10 includes a payment settlement unit 627 for performing settlement with the CP server 90 on the content payment paid by the user, and an I / O processing unit 629 for transmitting and receiving data with the payment gateway. Here, the approval processing unit 623 checks the remaining limit that the user of the mobile communication terminal 10 can use for payment and notifies the payment gateway 610, and the small payment using the mobile communication terminal 10 is postpaid payment. In this regard, the user's purchase limit is limited and the remaining limit is notified.

The payment gateway 610 and the ISAS server 620 refer to various information stored in the database 630 in user authentication, billing, payment, etc. The database 630 may include a CP information DB (DB) for storing and managing CP related information. 631), purchase history DB (633) for storing and managing the purchase history (purchased goods, purchase date, purchase price, etc.) for each user, and sui payment for managing and periodically updating the user's content purchase price storage and unpaid information Information DB 635 is included. These databases can consist of one table or each separate table.

On the other hand, the authentication and payment request unit 617 of the payment gateway 610 according to the present invention, if the user wants to cancel the purchase before the user pays for the billed content, the billing processing unit of the ISAS server 620 ( 625) to allow the charge to be canceled. The purchase cancellation procedure is similar to the charging request, but by setting the content purchase price to a negative value, the charging processing unit 625 of the ISAS server 620 allows the charging to be canceled without error. That is, the ISAS server 620 performs the billing processing in the same manner as the billing process at the time of purchase, but since the amount is negative, the remaining limit of the user is returned by the amount of the content to cancel the purchase, and the billed amount is the content to cancel the purchase. Will be lowered by.

3 is a flowchart illustrating a mobile payment method according to the present invention.

Before performing the payment process, the user selects the desired content online or offline. When the user requests to pay for the content price to the mobile payment device 60 using the mobile communication terminal 10 (S101), the payment gateway 610 of the mobile payment device 60 is the mobile communication terminal 10 To select a payment method (S102).

Accordingly, when the mobile communication terminal user selects a small payment method (S103), the payment gateway 610 requests the CP server 90 to transmit the payment information of the corresponding user (S104). In the present embodiment, the case in which the payment information is requested to the CP server 90 according to the payment request of the user has been described. However, the payment gateway 610 of the mobile communication terminal 10 according to the payment request of the CP server 90 is described. It is also possible to send a connection prompt and allow the mobile communication terminal 10 to access the payment gateway 610 to perform a micro payment.

The payment gateway 610 receiving payment information from the CP server 90 collects authentication data according to the authentication environment of the mobile communication terminal 10. Here, it is preferable that authentication data uses a social security number. This is because the user registers the resident registration number in the mobile communication system 120 when the user subscribes to the mobile communication service and is personalized identification information. In this respect, the authentication data may use data registered in the mobile communication system 120 with the customer when the mobile communication service is subscribed. In addition, since the authentication environment is different according to the mobile communication terminal 10, it is necessary to collect authentication data in a lawful manner according to the authentication environment. That is, the mobile communication terminal 10 used for micropayment includes an end-to-end (E2E) swap (WAP) terminal, a mobile electronic wallet service support terminal, a smart card built-in or a smart card one-chip terminal, and the like. The authentication data collection procedure for each case will be described later.

The payment gateway 610 receiving the authentication data from the mobile communication terminal 10 transmits a connection request message to the ISAS server 620 to request a connection (S107). When the ISAS server 620 responds (S108), The payment gateway 610 transmits the full authentication request message to the ISAS server 620 (S109). The full authentication request includes a mobile terminal number, authentication data, CP information (CP code, etc.), the purchase amount.

The ISAS server 620 receiving the full authentication request message performs user authentication with reference to the data and database 630 included in the full text of the authentication request and transmits the result to the payment gateway 610 (S110). In this case, the available amount is calculated and sent to the payment gateway 610 as a result of the approval.

The payment gateway 610 compares the purchase price with the available amount transmitted from the ISAS server 620 and requests a charge to the ISAS server 620 when the available amount is more than the purchase price (S111). In addition to the data included in the full certification request, the billing request further includes a product code, a purchase date, a purchase number, and a flat / separate classification code. The ISAS server 620 stores the purchase history for each user in the database 630, performs charging processing, generates and stores charging information, and transmits the charging processing result to the payment gateway 610 (S112).

The payment gateway 610 which has received this transmits the payment processing result to the CP server 90 (S113). When the payment gateway 610 receives the response of receiving the payment processing result from the CP server 90, the payment gateway 610 transmits the payment result to the mobile communication terminal. (S115). If the response signal for receiving the payment processing result from the CP server 90 is not transmitted, it is preferable to cancel the charging process.

4 to 6 are flowcharts illustrating a procedure of collecting authentication data in the mobile payment method according to the present invention.

First, FIG. 4 illustrates a case of collecting authentication data in the case of an E2E WAP terminal. E2E is a standard encryption method of a terminal supporting a wireless Internet service and can be used in most terminals supporting a wireless Internet service. The E2E WAP terminal is a terminal in which the E2E security module is embedded. The E2E WAP terminal exchanges payment information through a symmetric key security channel.

In step S103 of selecting a payment method of FIG. 3, when the user selects to perform a small payment by directly inputting authentication data, the payment gateway 610 inputs authentication data into the mobile communication terminal 10. If requested (S201), the user operates the keypad of the mobile communication terminal 10 to input the authentication data, the mobile communication terminal 10 encrypts it (S202) and transmits to the payment gateway (610) (S203). . Subsequently, the payment gateway 610 decrypts the encrypted authentication data (S204) and uses the authentication request to the ISAS server 620. When the payment gateway 610 requests authentication data from the mobile communication terminal 10, a direct link page (DLP) is used. The DLP directly accesses or allows the user to input user information and terminal information stored in the mobile communication terminal, and transmits the terminal number and authentication data to the payment gateway 610. In addition, when the payment information is requested to the CP server 90 in step S104 described above, the DLP is used.

Next, FIG. 5 illustrates a case in which authentication data is collected for a mobile wallet service support terminal and is applied to a mobile communication terminal including an electronic wallet. The mobile wallet service supporting terminal has an electronic wallet module embedded in the terminal and may input payment information into the wallet and use the information as necessary. The payment information is used after digital signature and encryption using the wireless public key infrastructure (WPKI).

In the step S103 of selecting the payment method of FIG. 3, when the user selects to perform the micro payment with the electronic wallet, the payment gateway 610 requests authentication data from the mobile communication terminal 10 (S301). At this time, a certificate, an encryption command, security-related parameters, etc. are transmitted together and use DLP. On the other hand, the user inputs a password to the mobile communication terminal 10 (S302) and if the input password and the password set in the electronic wallet coincides, the mobile communication terminal 610 according to the authentication data request of the payment gateway 610 It is required to call the authentication data with the electronic wallet (S303).

Accordingly, the electronic wallet extracts the mobile communication terminal number and authentication data with reference to a certificate, an encryption command, security-related parameters, etc. transmitted from the payment gateway 610, encrypts it (S304), and transmits it to the payment gateway (S306). . The payment gateway 610, which receives this, decrypts the encrypted authentication data (S306) and uses the authentication request to the ISAS server 620.

6 shows a case of collecting authentication data for a smart card embedded or smart card one-chip terminal.

In the step S103 of selecting the payment method of FIG. 3, when the user selects to perform the micro payment in a card one-chip manner, the payment gateway 610 uses a DLP to send a certificate to the mobile terminal 10. At the same time as transmitting the encryption command, security-related parameters, and the like to request authentication data (S401), the mobile communication terminal 10 requests the authentication data to the billing management system 130 (S402). At this time, routing information for transmitting the authentication data (ie, access information to the payment gateway), a certificate received from the payment gateway 610, an encryption command, security-related parameters, etc. are transmitted together.

The billing management system 130 extracts authentication data of the corresponding user with reference to the mobile communication terminal number (S403), and then encrypts the authentication data with reference to a certificate, an encryption command, security-related parameters, etc. transmitted from the payment gateway (404). ). Thereafter, the encrypted authentication data is transmitted to the payment gateway 610, and the payment gateway 610 decrypts it (S406) and uses the authentication request to the ISAS server 620.

The authentication data described with reference to FIGS. 4 to 6 further include not only personalized identification information but also delivery address information, emergency contact numbers, and e-mail addresses.

7 is a flowchart illustrating a mobile payment cancellation procedure according to the present invention.

In the present invention, if the user wants to cancel the purchase before the user pays for the charged content, it should be able to cancel it. The purchase cancellation procedure is similar to the charging request, but by setting the content purchase price to a negative value, the charging processing unit 625 of the ISAS server 620 allows the charging to be canceled without error. That is, the ISAS server 620 performs the billing processing in the same manner as the billing process at the time of purchase, but since the amount is negative, the remaining limit of the user is returned by the amount of the content to cancel the purchase, and the billed amount is the content to cancel the purchase. Will be lowered by. Referring to the drawings in more detail as follows.

When the user requests the CP server 90 to cancel the content purchase online or offline (S601), the CP server 90 sends an access page for performing the cancellation procedure to the mobile terminal 10 of the user. While transmitting (S602), the payment gateway 610 requests the cancellation processing (S603).

Subsequently, the mobile communication terminal 10 requests a cancellation by accessing the payment gateway 610 by using an access page for performing a cancellation procedure (S604). At this time, purchase of customer information, CP information, purchase information, purchase time, etc. The details are sent together. The payment gateway 610 checks the payment details by referring to the information transmitted from the mobile communication terminal 10 and the database 630 (S605), and requests a connection to the ISAS server 620 when the payment is completed (S605). S606).

As the ISAS server 620 responds to the connection request of the payment gateway 610 (S607), the payment gateway transmits the full charge cancellation request message to the ISAS server 620 (S608). It includes the number, authentication data, CP information, commodity code, date and time of purchase, purchase number, fixed / fixed division code, and negative purchase price. In response to the charge cancellation request, the ISAS server 620 performs the charge processing and transmits the execution result to the payment gateway 610 (S609). The payment gateway 610 transmits the charge cancellation result to the CP server 90 and the mobile communication. The cancellation procedure is completed by transmitting to the terminal 10 (S610 and S611).

As such, those skilled in the art will appreciate that the present invention can be implemented in other specific forms without changing the technical spirit or essential features thereof. Therefore, the above-described embodiments are to be understood as illustrative in all respects and not as restrictive. The scope of the present invention is shown by the following claims rather than the above description, and all changes or modifications derived from the meaning and scope of the claims and their equivalents should be construed as being included in the scope of the present invention. do.

Since the present invention performs user authentication using authentication data such as a social security number when making a small payment using a mobile communication terminal, the authentication procedure at the time of small payment is compared with a method of performing user authentication by generating and comparing a random number in a conventional mobile communication system. There is an advantage that can be simplified. In addition, since the authentication procedure is performed according to the case where the mobile communication terminal is an E2E WAP terminal, a mobile electronic wallet service supporting terminal, or a smart card embedded or one-chip terminal, data security characteristics can be improved in a wireless section. .

In addition, when the payment gateway and the ISAS server are operated by the mobile communication system operator, the burden on the content provider can be reduced, resulting in a drop in the content price.

Claims (29)

A mobile communication system connected to a plurality of content provider servers through a communication network, and the mobile communication terminal user who purchases the content from the content provider server wants to make a small payment, and the content purchase price is added to the mobile communication service fee to process the mobile communication. As a system, The mobile communication system receives the authentication data from the mobile communication terminal user requesting the micropayment, performs the user authentication, and if the user is a legitimate user, performs the charging and generates the charging information to generate the billing information. And a mobile payment device for transmitting the result of the billing to the content provider server and the mobile communication terminal, wherein the authentication data is data registered when the user subscribes to the mobile communication system. Mobile communication system. The method of claim 1, The authentication data is a mobile communication system having a mobile payment device, characterized in that the resident registration number. The method of claim 1, And the mobile payment device further stores the contents payment receipt information, non-payment information, and settlement information with the content provider server. The method of claim 1, The mobile payment device further stores the content purchase history for each user, the content purchase history is provided with a mobile payment device characterized in that it comprises a product code, content provider code, purchase date, purchase number, amount information One mobile communication system. The method of claim 1, The mobile payment device deletes the content purchase price from the billing information according to the user's request when the mobile communication terminal user who has purchased the content and made the payment wants to cancel the content purchase. And a function for transmitting to the content provider and a mobile communication terminal. A mobile communication terminal user who is connected to a plurality of content provider servers through a communication network and is connected to a mobile communication terminal through a mobile communication system, and purchases content from the content provider server, moves the content purchase price as a small payment is made. A mobile payment device for adding up and storing a communication service charge, Is connected between the mobile communication terminal and a content provider server, collects authentication data from the mobile communication terminal, collects payment information from the content provider server, and displays a result of billing processing according to the payment information. A payment gateway for transmitting to the server; And Receive authentication data from the payment gateway to perform user authentication, and if the user is found to be a legitimate user, perform billing processing using the payment information received from the payment gateway, An authentication / billing server for generating billing data with the content provider server; And the authentication data is data registered when the user subscribes to a service through a mobile communication system. The method of claim 6, The payment gateway includes a communication network interface for performing communication with the mobile communication terminal and a content provider; A database manager for managing the user information, purchase history for each user, payment history for each user, and content provider information; An ISAS format processing unit for transmitting and receiving data with the authentication / billing server; An authentication and payment request unit for requesting authentication data input to the mobile communication terminal, requesting user-specific payment information to the content provider server, and performing an authentication request, a billing request, a payment request, etc. to the authentication / billing server; And An I / O processing unit for data input / output processing; Mobile payment device comprising a. The method of claim 6, The ISAS processing unit may include a customer authentication unit for confirming whether the user is a legitimate user by referring to the user information at the request of the payment gateway; An approval processing unit for generating payment authorization information and transmitting the payment authorization information to the payment gateway when it is confirmed as a legitimate user in the customer authentication unit; A billing processing unit for generating and storing billing information by receiving the content payment information of the payment approved user from the payment gateway; A payment settlement unit for performing settlement with the content provider server on the content payment paid by the mobile communication terminal user; And An I / O processor for data transmission and reception with a payment gateway; Mobile payment device comprising a. The method of claim 8, The usage limit is specified for each user of the mobile communication terminal, and the approval processing unit checks the remaining limit that the mobile communication terminal user can use for payment and notifies the payment gateway. The method of claim 6, The mobile payment device includes a content provider information database for storing and managing content provider related information; A purchase history database for storing and managing the purchase history for each user; And A non-payment information database for managing and periodically updating the user's content purchase price storage and non-payment information; Mobile payment device comprising a. The method of claim 6, If the user wants to cancel the purchase of the content for which the billing process is completed, the payment gateway requests the billing cancellation to the authentication / billing server, and the authentication / billing server processes the billing cancellation according to the request of the payment gateway. Mobile payment device, characterized in that for performing. The method of claim 11, The payment gateway converts the purchase price to be canceled by the user to the authentication / billing server to a negative number, and sends a negative purchase information to the authentication / billing server to request a billing processing. The method of claim 6, The payment gateway is a mobile payment device, characterized in that for transmitting an authentication request to the authentication / billing server mobile communication terminal number, authentication data, content provider information, content amount. The method of claim 6, And the payment gateway transmits the mobile communication terminal number, authentication data, content provider information, content amount, product code, purchase date and time, and purchase number when the payment request is made to the authentication / billing server. A mobile communication terminal user who is connected to a plurality of content provider servers through a communication network and is connected to a mobile communication terminal through a mobile communication system, and purchases content from the content provider server, moves the content purchase price as a small payment is made. A payment method in a mobile communication system using a mobile payment device for summing and storing a communication service usage fee, wherein the mobile payment device is connected between the mobile communication terminal and a content provider server to collect authentication data and collect payment information. A payment gateway configured to perform a transaction and transmit a billing processing result, and an Internet Shopping Authentication System (ISAS) server configured to perform the user authentication and billing processing, Requesting the payment gateway to select a payment method from the mobile communication terminal when a user who wants to purchase the content requests to pay for the content to the mobile payment device; Requesting payment information of the user from the payment gateway to the content provider server as the mobile terminal user selects a small payment method; Collecting, by the payment gateway, receiving payment information from the content provider server, authentication data according to a model of the mobile communication terminal; Transmitting, by the payment gateway, receiving authentication data from the mobile communication terminal, an authentication request message to the authentication / billing server; An authentication / billing server receiving the full authentication request message, performing user authentication and transmitting a result to the payment gateway; If the user is a legitimate user, transmitting, by the payment gateway, a full request for charging to the authentication / billing server; Storing, by the authentication / billing server, the purchase history for each user, generating and storing billing information, and then transmitting a billing result to the payment gateway; And Sending, by the payment gateway, the charging result to the content provider server; Mobile payment method comprising a. The method of claim 15, The authentication data is a mobile payment method, characterized in that the social security number. The method of claim 15, The authentication data is a mobile payment method, characterized in that the data registered when the user subscribes to the service to the mobile communication system. The method of claim 15, The mobile communication terminal may be any one of an end-to-end (E2E) WAP terminal, a mobile electronic wallet service supporting terminal, a smart card embedded terminal, and a smart card one-chip terminal. Payment Method. The method of claim 18, If the mobile communication terminal is an end-to-end swap terminal, the authentication data collection procedure may include: requesting authentication data from the payment gateway to the mobile communication terminal; Encrypting the authentication data by the mobile communication terminal as the authentication data is input to the mobile communication terminal; Transmitting, by the mobile communication terminal, the encrypted authentication data to the payment gateway; And Decrypting, by the payment gateway, the encrypted and transmitted authentication data; Mobile payment method comprising a. The method of claim 18, If the mobile communication terminal is a mobile electronic wallet service support terminal, the authentication data collection process includes the step of requesting authentication data from the payment gateway to the mobile communication terminal; Causing the mobile communication terminal to call authentication data of the electronic wallet; Calling and authenticating authentication data from the electronic wallet; Transmitting, by the electronic wallet, the encrypted authentication data to the payment gateway; And Decrypting, by the payment gateway, the encrypted and transmitted authentication data; Mobile payment method comprising a. The method of claim 18, The mobile communication system stores and manages billing information through a mobile communication system including a voice call charge and a data service charge through the mobile communication terminal, generates and manages billing data according to a period, and stores the user for each user. It further includes a billing management system for storing and managing information, non-payment information, etc., When the mobile communication terminal is one of a smart card embedded terminal and a smart card one-chip terminal, the authentication data collection procedure may include: requesting the mobile communication terminal authentication data from the payment gateway; Requesting, by the mobile terminal, authentication data to the charging management system; Encrypting, by the charging management system, authentication data of the corresponding user with reference to the mobile communication terminal number; Sending the encrypted authentication data to the payment gateway; And Decrypting, by the payment gateway, the encrypted and transmitted authentication data; Mobile payment method comprising a. The method according to any one of claims 19, 20, 21, And requesting authentication data from the payment gateway to the mobile communication terminal uses a direct link page (DLP). The method according to any one of claims 20 and 21, Requesting authentication data from the payment gateway to the mobile communication terminal comprises transmitting a certificate, an encryption command, and a security related parameter. The method of claim 21, The requesting of the authentication data to the billing management system by the mobile communication terminal may include routing information for transmitting the authentication data, a certificate received from the payment gateway, an encryption command, and a security related parameter. Payment method. The method of claim 24, And the routing information is access information to the payment gateway. The method of claim 15, The full text of the authentication request includes a mobile communication terminal number, authentication data, content provider information, and purchase amount. The method of claim 15, And transmitting the authentication result to the payment gateway by the authentication / billing server calculates and transmits an available amount of the user when the user is a legitimate user. The method of claim 15, The full billing request is a mobile payment method comprising the mobile terminal number, authentication data, content provider information, purchase amount, product code, purchase date, purchase number. The method of claim 15, After the payment gateway transmits the charging processing result to the content provider server, if the payment signal is received from the content provider server in response to the charging processing result, the payment gateway transmits the charging processing result to the mobile communication terminal. Canceling the billing process if a response signal for the billing processing result is not received from the mobile payment method.