JP2004265241A - Online e-commerce system and method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To ensure a reliable payment of charges to a service provider and transfer only necessary pieces of a user's personal information to agencies. <P>SOLUTION: A service providing server 2S comprises a service providing part 2S1, a charging information recording part 2S2 and a deposit/sales management part 2S3, and accumulates information on a user 1 in user information 2SDB1. A billing part 4S1 of a bill collection server 4S creates billing information on the user 1 and accumulates it in billing information 4SDB4, as referring to user collection information 4SDB1, service provider information 4SDB2 and charging/clearing agency information 4SDB3. Information on a deposit is managed in deposit information 4SDB5. An ID management server 5S has an ID management part 5S1 that manages a common ID of the user as a common identification number and an ID issued by each agency as a user identification number, an ID issued to a service provider, and an ID issued to a bill collection agency. <P>COPYRIGHT: (C)2004,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to an electronic online commerce system and method, and more particularly, to an electronic online commerce system and method for performing billing and payment agency processing of a service deployed on a computer network.
[0002]
[Prior art]
With the adoption of broadband networks, it is expected that various services will be developed on the networks in the future. As a result, the usage fee of the user also increases, and the sales amount of the entire service sharply increases. As a service provider, the usage fee is usually settled on a monthly basis, but as the monthly sales amount increases, it becomes more difficult to reliably collect the fee from the user.
[0003]
In the prior art, there is one in which a computer for operating a billing / settlement unit system calculates a fee before a purchase is completed (temporary billing process) and determines whether the amount is equal to or less than a budget amount, thereby guaranteeing the billing of a purchase act. (For example, see Patent Document 1). However, the present technology does not include the payment processing itself as an invention, although a credit card and a prepaid card are described as payment means.
[0004]
Another conventional technique is a method of adding a content fee to a telephone fee, and is regarded as one of the settlement means (see, for example, Patent Document 2).
[0005]
In addition, services such as home delivery services, which allow users unfamiliar with credit card payment to select cash-on-delivery means at the time of delivery, are increasing the variety of payment means.
[0006]
As described above, the technology proposed as a conventional technology for reliably collecting fees from users does not guarantee that the fees have been collected, and in general, some improvement is expected by operation. Often trying. For example, in the case of a subscribed telephone, when a delinquent payment is serious, the user is urged to collect the fee by taking measures such as a reminder and a suspension of use of the service.
[0007]
Therefore, in the related art, there is a method in which a contract relating to payment of a fee and a contract for collecting a fee are generated to perform a fee collection agency (for example, refer to Patent Literature 3). It is assumed that this method is not mentioned and is added to the connection fee and usage fee of the provider. Further, since there is no specific description regarding the payment and fee collection contract, the source of the fee paid to the service provider is not clear.
[0008]
Further, there is a conventional technique of using a fixed deposit (see, for example, Patent Document 4), in which buyers and suppliers become members of the vegetable and vegetable forward transaction site and pay the deposit, but the so-called lifestyle cooperative It is the same as the union's stake and is not used to collect fees.
[0009]
[Patent Document 1]
JP 2001-236386 A
[0010]
[Patent Document 2]
JP 2002-312685 A
[0011]
[Patent Document 3]
JP-A-10-162058
[0012]
[Patent Document 4]
JP-A-2002-032599
[0013]
[Problems to be solved by the invention]
As described above, the conventional electronic online transaction system and method can guarantee the business operator, at least if the service provider is not surely paid for it, which may affect the business operation of the business operator. There is no problem. In addition, since the number of specialized traders increases, it is necessary to take over the personal information of the user between the traders, so that there is a problem that the possibility of leakage of the personal information increases.
[0014]
The present invention has been made in view of the above-mentioned problems, and its purpose is to ensure that a fee is paid to a service provider and to provide necessary information among the personal information of a user between respective providers. It is to provide an electronic online trading system and method that realizes taking over only things.
[0015]
[Means for Solving the Problems]
In order to achieve such an object, the invention according to claim 1 includes a network connecting a plurality of servers to each other, a network connected to the network, transmitting data input by a user, and transmitting data from the plurality of servers. A plurality of user terminals for receiving, a plurality of service providing servers for providing a service corresponding to a request from the user terminal via the network, and a service based on service usage information received from the service providing server via the network In an electronic online commerce system having a billing server that manages billing information corresponding to a user identification number that each of a plurality of servers individually assigns to identify one user from another user, A plurality of servers are managed in association with a common identification number for uniquely identifying one user, and An identification number management server that receives these inquiries and sends a corresponding common identification number or user identification number in response to the inquiry, and a common number obtained by inquiring the identification number management server about the user identification number included in the usage information. A charge collection server for transmitting, via a network, billing information to a user terminal, the billing information including a fee for a service provided based on the billing information received from the billing server for each identification number; I do.
[0016]
According to a second aspect of the present invention, in the electronic online commerce system according to the first aspect, the fee collection server manages the amount of the deposit and the balance of the deposit transmitted in advance for each of the plurality of service providing servers. A service providing server for transmitting billing information including a fee aggregated for each common identification number to a user terminal via a network, and transmitting sales payment information including sales aggregated for each of a plurality of service providing servers; And the deposit management means stores the total of the deposit and the total of the fees collected by the user up to the present, and subtracts the sales paid to the service provider as the deposit balance. And
[0017]
According to a third aspect of the present invention, in the electronic online commerce system according to the first or second aspect, the user terminal includes a payment information for instructing which one of a plurality of different methods the user should perform the payment. And transmitting the payment information output by the payment method selecting means to the fee collection server in advance or as a response to the received billing information, and the fee collection server outputs the payment information based on the payment information. It has a settlement means for transmitting a settlement request by a method designated by a user among a plurality of different methods via a network.
[0018]
According to a fourth aspect of the present invention, in the electronic online commerce system according to the third aspect, the settlement means requests settlement by another method when the settlement is not possible even by the method instructed by the user. A settlement request is transmitted.
[0019]
According to a fifth aspect of the present invention, in the electronic online commerce system according to any one of the first to fourth aspects, the deposit management means stores the deposit balance for each of the plurality of service providing servers in all of the plurality of service providing servers. When the sum total of the calculated value is less than a predetermined amount, a deposit deposit adding means for transmitting an additional request for adding the deposit to each of the plurality of service providing servers is provided.
[0020]
According to a sixth aspect of the present invention, in the electronic online commerce system according to the fifth aspect, the deposit addition means includes a plurality of service deposit servers based on a total amount of charges collected for a plurality of service providing servers over a predetermined period. The additional requests are transmitted only to the predetermined number of service providing servers from the top of the service providing servers in descending order of the amount, and the amount of the deposit added for each service providing server is the total amount of each service providing server The amount is proportional to the amount calculated over a predetermined period of time.
[0021]
According to a seventh aspect of the present invention, in the electronic online commerce method, a plurality of user terminals transmit data input by a user via a network connecting the plurality of servers to each other and receive data from the plurality of servers. A step in which the plurality of service providing servers provide a service corresponding to the request from the user terminal via the network; and a step in which the billing server provides the service based on the service usage information received from the service providing server via the network. An electronic online commerce method having a step of managing corresponding billing information, wherein each of the plurality of servers individually assigns a user identification number to identify one user from another user; Is managed in association with a common identification number that uniquely identifies Receiving the inquiry from the user and transmitting the corresponding common identification number or user identification number in response to the inquiry, and for each common identification number obtained by inquiring the user identification number included in the usage information to the identification number management server. And transmitting to the user terminal via the network, billing information including a fee obtained by summing up the value of the service provided based on the billing information received from the billing server.
[0022]
As described above, in the present invention, the servers for charge management and charge collection are further independent. The fee collection server manages the deposits and their balances collected in advance from a plurality of service providers, and based on them, subtracts the amount corresponding to the sales paid according to the monthly service provision from the deposit balance at that time. to manage. Then, in order to charge and collect the fee from the user, the settlement request is made to the settlement company. At this time, the settlement company can prepare various settlement means such as credit card, bank account withdrawal, postal transfer, etc. based on the user's selection, and can increase the certainty of fee collection.
[0023]
Further, according to the present invention, an identification number management server for issuing a common identification number for each user is further provided, and information relating to individual user numbers issued by a service providing server or the like is managed, and a billing server or a fee is charged. The user is specified in response to an inquiry from the collection server.
[0024]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
FIG. 1 is a diagram showing a relationship among a user, a service provider, a fee collection agency, and a settlement company. The service provider 2 provides a service to the user 1 (21). The service provider 2 deposits a deposit between the two in advance to the fee collection agent 3 (23). The fee collection agent 3 provides the service provider 2 with service revenue. A considerable amount of payment is made (32), and at the same time, a fee is collected for the user 1 (13).
[0025]
If the fee collection agent 3 does not have the settlement means by itself, it requests the fee collection from the settlement company 4 having the settlement means (34), and the settlement company 4 bills the user and collects the fee accordingly. Perform (14). If the fee collection agency 3 does not have its own settlement means, it pays the fee for requesting the fee collection to the settlement company 4 having the settlement means (34), and the settlement company 4 bills the user accordingly. Perform recovery.
[0026]
FIG. 2 is a diagram showing a block configuration of a system according to an embodiment of the present invention. The service providing server 2S includes a service providing unit 2S1, a charging information recording unit 2S2, and a deposit / sales management unit 2S3. When a service use contract is concluded between the user 1 and the service provider 2, that is, when a service request is made from the user terminal 1S to the service providing server 2S, the information on the user 1 is stored in the user information 2SDB1. You. The service providing unit 2S1 provides a service to the user terminal 1S. The billing information recording unit 2S2 records the service use history information of the user 1 in the history information 2SDB2, and transmits it to the billing information collecting unit 3S1 of the billing server 3S.
[0027]
The service usage history information is transmitted from the charging information recording unit 2S2 to the charging information collection unit 3S1, and conversely, the service usage history information can be periodically collected from the charging information collection unit 3S1 to the charging information recording unit 2S2. is there. The deposit / sales management unit 2S3 transmits / receives information on the deposit paid to the fee collection company 4 and information on the sales proceeds from the fee collection server 4S to / from the fee collection server.
[0028]
The billing server 3S includes a billing information collecting unit 3S1, a billing processing unit 3S2, and a billing unit 3S3. The charging information collecting unit 3S1 collects service usage history information from the charging information recording unit 2S2. The information is sent to the billing unit 3S2, where billing is performed. At this time, the charging unit 3S2 refers to the service provider information 3SDB1 and the charge setting information 3SDB2. The information subjected to the charging process is stored in the charging information 3SDB3. The fee detail unit 3S3 transmits the billing information of the user 1 to the billing unit 4S1 of the fee collection server 4S.
[0029]
The fee collection server 4S includes a billing unit 4S1 and a settlement GW unit 4S2. The billing unit 4S1 receives the billing information of the user 1 from the billing unit 3S3 of the billing and settlement server 3S, creates billing information of the user 1, and stores the billing information in the billing information 4SDB4. At this time, the billing unit 4S1 refers to the user collection information 4SDB1, the service provider collection information 4SDB2, and the billing and settlement agent information 4SDB3. The settlement GW unit 4S2 performs a task of receiving information on a deposit from a plurality of service providing servers and a task of presenting an amount equivalent to the sales amount to the corresponding service providing server 2S. For the toll collection agency 4 having no settlement means, it is also possible to separately request the settlement institution 6S for the settlement business processing. The information of the deposit received from the plurality of service providing servers is managed by the deposit information 4SDB5. Using the total amount of the deposits as a source, the service providing server 2S is notified of an amount equivalent to the sales amount paid in exchange for the corresponding service provider. Then, the fee is collected for the user.
[0030]
The settlement GW unit 4S2 also determines a collection method based on the billing information of the user 1. When the user 1 wishes to pay the bill, the settlement GW unit 4S2 issues a bill, and the fee collection agent 4 can mail the payment form to the user 1 or directly collect money. However, if the toll collection agency 4 does not have a settlement means, it is also possible to separately send a settlement request to the settlement institution 6S to collect the toll from the user.
[0031]
The ID management server 5S, which is an identification number management server, includes an ID management unit 5S1, which includes a common ID of the user 1 as a common identification number and a user ID (5SDB1) issued by each trader as a user identification number. It manages the service provider ID (5SDB2) issued by the ID management server 5S to the service provider 2, and the fee collection company ID (5SDB3) issued by the ID management server 5S to the fee collection agency.
[0032]
FIG. 3 is a diagram showing a table of the user information 2SDB1. The service providing server 2S manages the information of the user 1 based on the information transmitted from the user terminal 1S. This table manages information about the user 1 such as an ID (T01C02), which is a user identification number issued individually for each user, and other information such as a name and a contact address. In the present embodiment, the service providing server 2S does not manage information related to the settlement of the user 1 (credit card number, financial institution account number, etc.).
[0033]
FIG. 4 is a diagram showing a table of the history information 2SDB2. This table includes, in addition to the ID (T02C01) specifying the history information, the service use time (T02C02, T02C03), the service ID used (T02T04), and the user (T02C05) using the service.
[0034]
FIG. 5 is a diagram showing a table of the service provider information 3SDB1. In this table, information such as an ID (T03C01) issued by the accounting server 3S to the service providing server 2S, a business name, and a contact (T03C02 and later) are managed.
[0035]
FIG. 6 is a diagram showing a table of service charge setting information 3SDB2. The distinction of whether to perform the charge calculation at a fixed amount or at a metered amount is recorded in T04C04, the basic charge is recorded in T04C05, and T04C06 indicates whether the amount is a tax-included price or a tax-exclusive price. After T04C07, discount-related information such as time-based discount and campaign discount is set.
[0036]
FIG. 7 is a diagram showing a table of the billing information 3SDB3. In this table, an ID (T05C01) for specifying billing information, a user ID (T05C02), a used service name (T05C03), a use time (T05C04), a charge calculated by taking into account discount information of 3SDB2, and the like ( T05C05) and the like. The user ID of T05C02 is a common identification number of the user 1 issued by the ID management server 5S.
[0037]
FIG. 8 is a diagram showing a table of the user collection information 4SDB1. In this table, in addition to the user information 2SDB1, information relating to settlement is also managed. In the user collection information 4SDB1, the account information of the financial institution is described after T06C07. Since it is determined based on a contract with the trader 3, various information such as credit card information is managed depending on the contract.
[0038]
FIG. 9 is a diagram illustrating a table of the service provider collection information 4SDB2. The ID (T07C01) is issued by the fee collection server 4S to the corresponding service providing server 2S. T07C02 to T07C07 are contact information for the corresponding service provider 2. After T07C08, information on the financial institution necessary for the fee collection agency 3 to pay the service sales equivalent to the corresponding service provider 2 is described.
[0039]
FIG. 10 is a diagram showing a table of the charging agent collection information 4SDB3. The ID (T08C01) is issued by the fee collection server 4S to the corresponding charging server 3S. After T08C02, information on contact information for the corresponding charging server 3S administrator, information on financial institutions, and the like are described.
[0040]
FIG. 11 is a diagram showing a table of the bill collection information 4SDB4. This table includes an ID (T09C01) for specifying billing information, an ID of user 1 (T09C02), and the like. T05C02 is the ID of the corresponding user 1 issued by the fee collection server 4S. Then, the total amount of the fee using the service is described in the price including the consumption tax (T09C03), and the related billing information is described below T09C04.
[0041]
FIG. 12 is a diagram showing a table of the user ID information 5SDB1. T10C01 is a common ID issued to the corresponding user 1, and T10C02 is the name of the user 1. T10C11 and thereafter are IDs issued by the plurality of service providing servers to the corresponding user 1, and T10C21 and thereafter are IDs issued by the plurality of fee collection servers to the corresponding user.
[0042]
FIG. 13 is a diagram showing a table of the service provider ID information 5SDB2. This table includes information such as the name and address of the service providing server 2S, in addition to the ID (T11C01) for specifying the service providing server 2S.
[0043]
FIG. 14 is a diagram showing a table of the fee collection agency ID information 5SDB3. This table includes information such as the name and address of the fee collection agent 2 in addition to the ID (T12C01) specifying the fee collection agent 3.
[0044]
FIG. 15 shows a common ID issued by the ID management server S5 to the user 1, an ID individually issued by the service providing server 2S to the user 1, and a charge collection agent 3 for the user 1. FIG. 4 is a tree diagram showing a relationship between IDs to be issued. Now, it is assumed that the ID management server 5S has issued a common ID (UID) = dfjljdsgerponbvngt to a user named “Jiro Yamada”. This is indicated by T10C01 in FIG. The ID management server 5S also issues a common ID to the service providers A, B,..., The charge collection companies a, b,. In FIG. 15, the common ID issued to the service providing server 2S is PID, the common ID issued to the fee collection agent 3 is CID, and the service providers A, B,. , To each other, Oewpweotrju456gh, 102389fh4rtbftr,..., Weqrerg4y4gh56y, gjdft58bngfhj564523, etc. are assumed to be issued. These are described as T11C01, T11C02,..., T12C01, T12C02, etc., respectively. Then, IDs issued by each service provider and each fee collection agent to the user "Jiro Yamada" are written as T10C11, T10C12,..., T10C21, T10C22, etc., and (P-UID) A = gfdjgtry56hf, (P-UID) B = 049tri845ert,..., (C-UID) a = we293457845gf, (C-UID) b = vcxk468gh4576, and the like.
[0045]
As described above, T10 manages the UID, P-UID, and C-UID in association with each other, and T11 and T12 manage the PID and CID, respectively.
[0046]
FIG. 16 is a flowchart in the case where the user 1 of one embodiment requests a service from the user terminal 1S to the service providing server 2S. It is assumed that the user 1 has been issued a common ID (UID) from the ID management server 5S. The user terminal 1S makes a service request to the service providing server 2S and registers necessary information (STEP001). At that time, the user terminal 1S also registers the UID. The service providing server 2S writes the registration information other than the common ID into the 2SDB 1 (STEP002), and sends the ID management server 5S the UID of the user terminal 1S and the user ID (P-UID) issued by itself. Is written (STEP003). The ID management server 5S confirms that the UID of the user 1 has been registered, and registers the P-UID in the 5SDB1 (STEP004). Then, the service providing server 2S notifies that the registration has been completed (STEP005), and in response, the service providing server 2S notifies the user terminal 1S that the service registration has been completed (STEP006). All transactions can prevent eavesdropping from outside by using an encryption technique such as SSL.
[0047]
FIG. 17 is a flowchart illustrating communication between the service providing server 2S and the charging server 3S according to the embodiment. The service providing server 2S requests registration from the charging server 3S (STEP011). The accounting server 3S writes the registration information 3SDB1 (STEP012), and finally notifies the service providing server 2S that the registration has been completed (STEP013). All transactions can prevent eavesdropping from outside by using an encryption technique such as SSL.
[0048]
FIG. 18 is a flowchart of service registration between the service providing server 2S and the accounting server 3S according to one embodiment. The service providing server 2S registers service charge information in the charging server 3S (STEP021). The accounting server 3S writes the registration information in the 3SDB2 (STEP 022), and finally notifies the service providing server 2S of the completion of the registration (STEP 023). All transactions can prevent eavesdropping from outside by using an encryption technique such as SSL.
[0049]
FIG. 19 is a flowchart for registering a service between the charging server 3S and the fee collection server 4S according to the embodiment. The accounting server 3S requests the fee collection server 4S to register (STEP031), the fee collection server 4S writes the registration information in the 4SDB3 (STEP032), and finally notifies the accounting server 3S of the completion of the registration (STEP033). . All transactions can prevent eavesdropping from outside by using an encryption technique such as SSL.
[0050]
FIG. 20 is a flowchart for registering between the service providing server 2S and the fee collection server 4S of the embodiment. The service providing server 2S requests the fee collection server 4S for registration (STEP041). The fee collection server 4S writes the registration information into the 4SDB2 (STEP042), requests the financial institution designated by the service provider to withdraw the amount of the deposit determined between the two, and deposits the deposit in the account of the fee collection agency. It is confirmed that has been transferred (STEP043). In the present embodiment, STEP043 is processed online between the fee collection server 4S and the financial institution. Finally, the service providing server 2S is notified of the completion of the registration (STEP044). All transactions can prevent eavesdropping from outside by using an encryption technique such as SSL.
[0051]
FIG. 21 is a flowchart for performing registration between the user terminal 1S and the fee collection server 4S according to one embodiment. Here, it is assumed that the user 1 has been issued a common ID (UID) from the ID management server 5S via the user terminal 1S. The user terminal 1S registers necessary information in the fee collection server 4S (STEP 051). At that time, the user terminal 1S also registers the UID. The fee collection server 4S writes the registration information other than the UID into the 4SDB1 (STEP 052), and registers the UID of the user terminal 1S and the user ID (C-UID) issued by the user into the ID management server 5S. Request (STEP053). The ID management server 5S confirms that the UID of the user 1 is registered, and writes the C-UID in the 5SDB1 (STEP054). Then, the charge collection server 4S is notified that the registration is completed (STEP 055), and in response, the charge collection server 4S notifies the user terminal 1S that the registration is completed (STEP 056). All transactions can prevent eavesdropping from outside by using an encryption technique such as SSL.
[0052]
FIG. 22 is a communication flow diagram between the user terminal 1S and the ID management server 5S according to one embodiment. The ID management server 5S is requested to issue an ID from the user terminal 1S (STEP061). The ID management server 5S issues the ID, writes it in the 5SDB1 (STEP062), and transmits the issued UID to the user terminal 1S (STEP063). All transactions can prevent eavesdropping from outside by using an encryption technique such as SSL.
[0053]
FIG. 23 is a flowchart illustrating communication between the service providing server 2S and the ID management server 5S according to the embodiment. The service providing server 2S requests the ID management server 5S to issue an ID (STEP071). The ID management server 5S issues an ID and writes it in the 5SDB1 (STEP072), and notifies the service providing server 2S of the issued UID (STEP073). All transactions can prevent eavesdropping from outside by using an encryption technique such as SSL.
[0054]
FIG. 24 is a flowchart showing communication between the fee collection server 4S and the ID management server 5S according to one embodiment. The fee collection server 4S requests the ID management server 5S to issue an ID (STEP081). The ID management server 5S issues an ID, writes it in the 5SDB1 (STEP082), and notifies the fee collection server 4S of the issued UID. (STEP083). All transactions can prevent eavesdropping from outside by using an encryption technique such as SSL.
[0055]
FIG. 25 is a flowchart showing a series of service providing methods in the case where the fee collection company 4 of one embodiment performs settlement. When the user 1 uses the service from the user terminal 1S (STEP0901), the service providing server 2S records the usage history (STEP0902), and sends the history, the P-UID, and the PID to the charging server 3S (STEP0903). Using the P-UID and the PID as key information, the charging server 3S inquires of the corresponding user's UID using the P-UID and the PID as key information, and obtains an answer (STEP0904, STEP0905). Thereby, it is also possible to authenticate that the corresponding user is a registered user. Then, the accounting server 3S performs an accounting process (STEP0906), and passes the result, the UID, and the PID to the fee collection server 4S (STEP0907).
[0056]
The fee collection server 4S queries the ID management server 5S for the corresponding user's C-UID using the UID as key information, and obtains a reply (STEP0908, STEP0909). As a result, it is possible to authenticate that the user is a registered user. Then, the sales equivalent amount is transferred to the service provider 2 corresponding to the PID (STEP0910), the billing process for the user 1 is performed (STEP0911), and the fee is charged via the corresponding user terminal 1S (STEP0911). (STEP0912). The user 1 pays a fee based on the request (STEP0913). All transactions can prevent eavesdropping from outside by using an encryption technique such as SSL.
[0057]
FIG. 26 is a service flow diagram in the case where the fee collection company 4 of one embodiment requests another settlement company for settlement. When the user 1 uses the service via the user terminal 1S (STEP 1001), the service providing server 2S records the use history (STEP 1002), and sends the history, the P-UID and the PID to the charging server 3S (STEP 1003). ). The accounting server 3S inquires of the ID management server 5S about the UID of the corresponding user 1 using the P-UID and the PID as key information, and obtains an answer (STEP1004, STEP1005). Thereby, it is also possible to authenticate that the corresponding user 1 is a registered user. Then, the accounting server 3S performs an accounting process (STEP 1006), and transmits the result, the UID and the PID to the fee collection server 4S (STEP 1007). The fee collection server 4S uses the UID as key information to the ID management server 5S, inquires of the C-UID of the corresponding user 1, and obtains a response (STEP1008, STEP1009). Thereby, it is also possible to authenticate that the corresponding user 1 is a registered user. Then, the service provider 2 corresponding to the PID receives the amount equivalent to the sales (STEP 1010), performs a billing process (STEP 1011), and requests the settlement institution 6S for settlement (STEP 1012). The settlement institution 6S charges a fee via the corresponding user terminal 1S (STEP 1013). The user 1 pays a fee based on the request (STEP 1014). The settlement institution 6S notifies the fee collection server 4S that the settlement has been completed (STEP 1015). All transactions can prevent eavesdropping from outside by using an encryption technique such as SSL.
[0058]
FIG. 27 is a flowchart in the case of substituting the settlement means, which is the details of STEP 1012 in FIG. First, the fee collection server 4S makes a settlement request to a certain settlement institution 6S1 with a deadline (STEP10021). When a notice that the fee has not been collected from the user has been received from the settlement institution 6S1 (STEP10022), the fee collection server 4S determines a deadline again to the next settlement institution 6S2 and makes a settlement request (STEP10023). When a notice from the settlement institution 6S2 that a charge has not yet been collected has been received from the user (STEP10024), the charge collection server 4S further sets a time limit to the next settlement institution 6S3 and makes a settlement request (STEP10025). When the notice that the fee has not been collected yet from the user is received from the settlement institution 6S3 (STEP 10026), the fee collection server 4S repeatedly sets a time limit to the next settlement company and makes a settlement request repeatedly.
[0059]
FIG. 28 is a diagram showing a table of the deposit collection information 4SDB5 managed by the charge collection server of one embodiment. The table T13 manages the total amount of deposit money deposited from each service provider. The amount of the deposit deposited individually for each service provider is further managed individually. For example, as shown in FIG. 28, a table T131 is managed by a table such as a deposit management table of the service provider A, a table T132 is a deposit management table of the service provider B, and so on. The deposit is determined in advance between the fee collection agency and the service provider regarding the amount to be deposited and the method of depositing the deposit, so that the deposit can be deposited in a lump sum depending on the service provider (T131), and a small monthly amount. It is also possible to deposit (T132).
[0060]
Further, in the table T14, the amount used for reimbursement of sales is managed, and this also manages the amount individually reimbursed for each service provider. For example, as shown in FIG. 28, a table T141 is a management table of a payment for the service provider A, and a table T142 is a management table of a payment for the service provider B. Further, the table T15 manages the total amount of fees collected from users.
[0061]
FIG. 29 is a flowchart showing a process in a case where the total amount of deposits is insufficient for replacement payment in one embodiment. If the balance of the deposit, which is the sum of the deposit plus the fee already collected and the amount of the reimbursement, is less than the sales amount to be reimbursed next, reimburse the service provider Therefore, the object of the present invention to guarantee the collection of the sales proceeds cannot be achieved because of the shortage of resources for the above. For this reason, in the present invention, when the amount of the deposit is smaller than the amount obtained by adding the predetermined amount to the current sales reimbursement (STEP1101), the payment result within the past predetermined number of months is checked based on 4SDB5. A request is made to the service providers of the top M companies with a high sales performance to share the shortfall in accordance with the sales ratio (STEP 1102).
[0062]
【The invention's effect】
As described above, according to the present invention, the fee collection server has a deposit management means for managing the amount of the deposit transmitted in advance for each of the plurality of service providing servers and the current deposit balance, and In addition to invoking the user terminal via the network with the totalized charge for each service, the totalized charge for each of the multiple service providing servers is paid out to the service provider, and the deposit management means subtracts the paid fee from the deposit. Is stored as a new deposit balance, so that the sales are reliably transferred to the service provider by the charge collection of the charge collection agency. In addition, since the operation of the service and the fee collection are completely separated by this, it is possible to eliminate the influence of the two. According to the present invention, since the fee is reimbursed based on the deposit, business can be performed even by a company having less financial power than a financial institution.
[0063]
Further, in the present invention, a common ID is paid out for the user, and information of the user circulating between the service provider, the billing agent and the fee collection agent is collected into the common ID, whereby the personal information of the user is obtained. The security is further improved by preventing leakage of data and using secret communication using means such as encryption.
[Brief description of the drawings]
FIG. 1 is a diagram showing a relationship among a user, a service provider, a fee collection agency, and a settlement company.
FIG. 2 is a diagram showing a block configuration of a system according to an embodiment of the present invention.
FIG. 3 is a diagram showing a table of user information 2SDB1.
FIG. 4 is a diagram showing a table of history information 2SDB2.
FIG. 5 is a diagram showing a table of service provider information 3SDB1.
FIG. 6 is a diagram showing a table of service charge setting information 3SDB2.
FIG. 7 is a diagram showing a table of charging information 3SDB3.
FIG. 8 is a diagram showing a table of user collection information 4SDB1.
FIG. 9 is a diagram showing a table of service provider information 4SDB2.
FIG. 10 is a diagram showing a table of accounting settlement agent information 4SDB3.
FIG. 11 is a diagram showing a table of billing information 4SDB4.
FIG. 12 is a diagram showing a table of user ID information 5SDB1.
FIG. 13 is a diagram showing a table of service provider ID information 5SDB2.
FIG. 14 is a diagram showing a table of fee collection agency ID information 5SDB3;
FIG. 15 shows the relationship between the common ID issued by the ID management server to the user, the ID issued individually by the service providing server to the user, and the ID issued by the fee collection agent to the user. It is a tree diagram shown.
FIG. 16 is a flowchart in a case where a user of the embodiment of the present invention requests a service from a user terminal to a service providing server.
FIG. 17 is a flowchart showing communication between a service providing server and a billing server according to an embodiment of the present invention.
FIG. 18 is a flowchart of service registration between a service providing server and a billing server according to an embodiment of the present invention.
FIG. 19 is a flowchart for registering a service between the charging server and the fee collection server according to the embodiment of the present invention.
FIG. 20 is a flowchart for registering between a service providing server and a fee collection server according to an embodiment of the present invention.
FIG. 21 is a flowchart for performing registration between a user terminal and a fee collection server according to one embodiment.
FIG. 22 is a communication flow diagram between a user terminal and an ID management server according to an embodiment of the present invention.
FIG. 23 is a flowchart showing communication between a service providing server and an ID management server according to an embodiment of the present invention.
FIG. 24 is a flowchart showing communication between a fee collection server and an ID management server according to an embodiment of the present invention.
FIG. 25 is a flowchart showing a series of service providing methods in the case where the charge collection company of the embodiment of the present invention performs settlement.
FIG. 26 is a service flow diagram in the case where the fee collection agency of one embodiment of the present invention requests settlement to another settlement agency.
FIG. 27 is a flowchart showing the details of STEP 1012 in FIG. 26 in the case of substituting the settlement means.
FIG. 28 is a diagram showing a table of deposit information 4SDB5 managed by the fee collection server according to one embodiment of the present invention.
FIG. 29 is a flowchart showing a case where the total amount of deposits is insufficient for replacement payment in one embodiment of the present invention.
[Explanation of symbols]
1 user
2 service providers
3 fee collection agency
4 settlement companies
21 Provision of Services
23 Deposit
32 Repayment proceeds
13 Service Charge
34 Settlement agency fee
14 Service Charge
1S user terminal
2S service providing server
2S1 Service Provider
2S2 Billing information recording unit
2S3 Deposit and Sales Management Department
2SDB1 user information
2SDB2 history information
3S billing server
3S1 Billing information collection unit
3S2 Billing unit
3S3 charge details department
3SDB1 service provider information
3SDB2 pricing information
3SDB3 billing information
4S fee collection server
4S1 Claims department
4S2 Settlement GW
4SDB1 user collection information
4SDB2 service provider information
4SDB3 Billing agency information
4SDB4 Billing information
4SDB5 Deposit information
5S ID management server
5S1 ID management unit
5SDB1 User ID information
5SDB2 service provider ID information
5SDB3 fee collection agency ID information
6S payment institution

Claims (7)

A network connecting a plurality of servers to each other, a plurality of user terminals connected to the network, transmitting user-input data, and receiving data from the plurality of servers; and A plurality of service providing servers that provide a service corresponding to a request from a terminal, and a billing server that manages billing information corresponding to the service based on use information of the service received from the service providing server via the network. In an electronic online commerce system having
Each of the plurality of servers associates a user identification number individually assigned to identify one user with another user, and a common identification number uniquely identifying the one user. An identification number management server that manages and receives an inquiry from the plurality of servers via the network, and transmits the common identification number or the user identification number corresponding to the inquiry,
For each of the common identification numbers obtained by inquiring the identification number management server for the user identification number included in the usage information, a charge for the service provided based on the accounting information received from the accounting server for each common identification number And a charge collection server for transmitting charge billing information to the user terminal via the network. The fee collection server has a deposit management means for managing a deposit amount and a deposit balance transmitted in advance for each of the plurality of service providing servers, and a fee bill including a fee totalized for each common identification number. Transmitting information to the user terminal via the network, and transmitting sales payment information including sales totaled for each of the plurality of service providing servers to the service providing server;
The deposit management means is characterized by adding a charge totaled from the user to the amount of the deposit to the amount of the deposit and subtracting the sales paid to the service provider as a deposit balance. The electronic online commerce system according to claim 1. The user terminal has a payment method selection unit that outputs payment information indicating which one of the plurality of different methods the user performs the payment, and the user terminal outputs the payment information by the payment method selection unit. Transmitting the payment information to the fee collection server in advance or as a response to the received billing information,
The said fee collection | recovery server has the payment means which transmits the said payment request by the method instruct | indicated by the said user among the said several different methods based on the said payment information via the said network. 3. The electronic online commerce system according to 1 or 2. 4. The electronic device according to claim 3, wherein the payment unit transmits the payment request for requesting payment by another method when the payment is not performed by the method instructed by the user. 5. Online commerce system. The deposit management means, when the sum of the deposit balances of the plurality of service providing servers for all the plurality of service providing servers is less than a predetermined amount, an additional request for adding the amount of the deposit. The electronic online commerce system according to any one of claims 1 to 4, further comprising deposit money adding means for transmitting a deposit to each of the plurality of service providing servers. The deposit deposit adding means is configured to determine a predetermined number of services from the top of the plurality of service providing servers in descending order of the amount based on an amount of the charges totaled for each of the plurality of service providing servers over a predetermined period. Sending the additional request only to the providing server,
6. The electronic device according to claim 5, wherein the amount of the deposit added to each of the service providing servers is an amount proportional to the amount of the fee collected for each service providing server over a predetermined period. Online commerce system. A plurality of user terminals transmitting data input by the user via a network connecting the plurality of servers to each other and receiving data from the plurality of servers; and a plurality of service providing servers via the network. Providing a service corresponding to the request from the user terminal, and managing a charging information corresponding to the service based on usage information of the service received from the service providing server via the network from the service providing server. An electronic online commerce method having
Each of the plurality of servers associates a user identification number individually assigned to identify one user with another user, and a common identification number uniquely identifying the one user. Managing, receiving an inquiry from the plurality of servers via the network, and transmitting the common identification number or the user identification number corresponding to the inquiry,
For each of the common identification numbers obtained by inquiring the identification number management server for the user identification number included in the usage information, a charge for the service provided based on the accounting information received from the accounting server for each common identification number Transmitting to the user terminal via the network the billing information including the following.

Images