JP2012059022A - Seller/buyer complex type multiple-transaction auction system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To realize many-to-many competitive bidding and a plurality of transactions by complexly managing a seller initiative type and a buyer initiative type.SOLUTION: This seller/buyer type multiple-transaction auction system includes: individual bidding interfaces allowing both bidders of buyers and sellers to bid at a same auction transaction; a data storage device and data storage means capable of identifying the buyers and the sellers from bidding information and discriminating bidding sequences thereof respectively; control means capable of sequentially selecting bidders in a seller side in the ascending sequence of bidding order of the buyer side when finishing an auction period; and reference means of bidder list information for selecting the seller side bidders.

Description

  The present invention relates to a system in which a seller-initiated auction and a buyer-initiated auction (reverse auction) are concurrently held in an Internet auction and a plurality of transactions are completed in one auction.

  Recently, it has become possible to easily obtain the sales price at each store when purchasing a product and its comparison information via the Internet, so information is collected using the Internet to purchase the product as cheaply as possible. Consumers are increasing. One option is the Internet auction. In most Internet auctions, transactions often occur due to inventory management at stores or disposal of products that are no longer needed by general consumers. It is often cheap.

  In Internet auctions, multiple buyers who bid for multiple sellers and who have recorded the highest price can obtain a purchase right for the product, as well as multiple There are buyer-driven auctions where sellers who bid for and record the lowest price can acquire merchandise sales rights, and these are the mainstream in current Internet auctions. In seller-led auctions, there is a system that allows the seller to set a prompt price when listing a product and launching a new auction, and there are bidders who can accept the prompt price. In this case, the auction period is shortened by making a successful bid when a bid is made at a prompt decision price, and both the exhibitor and the purchaser can complete the transaction at an early stage.

  In addition, in a system in which information can be exchanged between a plurality of transactions in both a seller-driven auction and a buyer-driven auction, the system can provide other auction information to a bidder who has failed to make a successful bid in a certain auction. It is possible to shift to other auctions as soon as possible by introducing etc. As described above, in addition to the significance of the original auction where prices are simply contending, various improvements have been made so that both buyers and sellers can make transactions quickly and with higher probability. It is coming. As a known technique related to the present invention, Patent Document 1 can be cited.

JP 2007-140599 A

  By the way, as described above, the Internet auction has a seller-driven type and a buyer-driven type, but in either type, transactions are performed one-to-many. Therefore, when limited to a single auction transaction, many buyers cannot achieve the purpose in the seller-driven auction, and many sellers cannot achieve the purpose in the buyer-driven auction.

  For this reason, an auction participant who cannot achieve the purpose of purchasing or selling a product needs to participate in another auction again after the end of the auction. As mentioned above, there is a system that introduces other auction information to auction participants who could not make a successful bid, and supports a quick transition to other auctions. If not, it is necessary to wait for the completion of the transaction until the end of the event period. In general, Internet auctions often have holding periods ranging from several days to a week, and there is no guarantee that they can make a successful bid at the destination auction, so it may take a long time to buy or sell goods. .

  The object of the present invention is to realize a many-to-many bidding competition by operating a seller-driven auction and a buyer-driven auction for a single product in an Internet auction, thereby enabling a plurality of transactions in a single auction. It is an object of the present invention to provide a seller / buyer combined multi-transaction auction system that enables a bidder to achieve buying and selling of goods with higher probability.

  In order to achieve the above object, the seller-buyer composite multi-transaction auction system of the present invention has a user interface that allows a bidder to auction to select whether to bid as a buyer or as a seller, An external storage device having a data structure that can identify whether a bidder who bids is a buyer side or a seller side, a bid rank calculation means according to the bid amount on each buyer side seller side, and data that can identify the calculated bid rank An external storage device having a structure, a means for searching for a bidder having the highest bid order on the buyer side when the auction period ends, and a list for selecting a seller-side bidder for the searched bidder Information creation means, notification means for selecting the seller-side bidder for the searched bidder, and the searched bidder is the seller A user interface that enables selection of a bidder, a means for calculating a transaction amount to be traded between the searched bidder and the selected seller-side bidder, and the searched bidder and the selected seller-side bidder. Search means for notifying the successful bid, an external storage device with a data structure that can identify the successful bidder, and the bidder who has the highest bid order on the buyer side again for the bidder who has not been traded. And a control means for repeating the process of selecting a seller-side bidder and establishing a transaction until there is no target bidder.

  According to the seller-buyer combined multi-transaction auction system of the present invention, a one-to-one auction transaction enables a many-to-many bid competition between a buyer and a seller, and a transaction can be established with a plurality of combinations. This increases the probability that the bidder will establish a transaction with one participation in the auction, and therefore the purpose of purchasing or selling the product can be achieved more quickly.

<System overview>
FIG. 1 is a system configuration diagram showing an embodiment of the present invention. <Data structure diagram> FIG. 2 is a data configuration diagram showing a data configuration of the transaction management DB. FIG. 3 is a data configuration diagram showing a data configuration of the transaction participant management DB. FIG. 4 is a data configuration diagram showing a data configuration of the product information DB. FIG. 5 is a data configuration diagram showing a data configuration of the exhibitor product information DB. FIG. 6 is a data configuration diagram showing the data configuration of the user management DB. <Screen layout diagram> FIG. 7 is a screen layout diagram showing a screen configuration of the auction list screen. FIG. 8 is a screen layout diagram showing a screen configuration of a new auction creation screen. FIG. 9 is a screen layout diagram showing the screen configuration of the auction creation result screen. FIG. 10 is a screen layout diagram showing the screen configuration of the auction detailed information display screen. FIG. 11 is a screen layout diagram showing a screen configuration of a bid screen as a purchaser. FIG. 12 is a screen layout diagram showing a screen configuration of a bid result screen as a purchaser. FIG. 13 is a screen layout diagram showing a screen configuration of a bid screen as an exhibitor. FIG. 14 is a screen layout diagram showing a screen configuration of a bid result screen as an exhibitor. FIG. 15 is a screen layout diagram showing the screen configuration of the seller information inquiry screen. FIG. 16 is a screen layout diagram showing a screen configuration of the exhibitor selection screen. <Flowchart> FIG. 17 is a flowchart showing a processing procedure of data reception processing. FIG. 18 is a flowchart showing a processing procedure of data transmission processing. FIG. 19 is a flowchart showing the processing procedure of the auction list creation processing. FIG. 20 is a flowchart showing a processing procedure of new auction creation processing. FIG. 21 is a flowchart showing a processing procedure of the auction basic information inquiry processing. FIG. 22 is a flowchart showing the processing procedure of the bidder list creation processing. FIG. 23 is a flowchart showing a processing procedure of bid distribution processing. FIG. 24 is a flowchart showing the processing procedure of the new purchaser addition processing. FIG. 25 is a flowchart showing the processing procedure of the new exhibitor addition processing. FIG. 26 is a flowchart showing the processing procedure of the existing participant purchaser information update processing. FIG. 27 is a flowchart showing a processing procedure of existing participant information update processing. FIG. 28 is a flowchart showing a processing procedure of exhibitor information inquiry processing. FIG. 29 is a flowchart showing the processing procedure of the auction period monitoring process. FIG. 30 is a flowchart showing the processing procedure of the auction period end processing. FIG. 31 is a flowchart showing the processing procedure of the upper bidder search process. FIG. 32 is a flowchart showing a processing procedure of transaction record creation processing.

FIG. 1 is a system configuration diagram showing an embodiment of the present invention. The seller-buyer composite multi-transaction auction system of this embodiment is premised on providing the service at an Internet auction, and includes a Web server (1), a database management server (2), and a mail server (3). The Web server (1) and the mail server (3) are connected to the Internet through the public network (5), and the auction participants who are end users use the Internet browser from their own client terminals (4). Then, via the Internet, the website provided by the seller / buyer combined multiple transaction auction system is accessed and the service is received.
The Web server (1) includes a new auction creation unit (12) that manages a process for creating a new auction, an auction period monitoring unit (13) that monitors the end of the period of all auction transactions, and an auction period Is completed and the end notification is received from the auction period monitoring unit (13), the auction period end unit (14) that manages the closing process of the auction, the bid management unit (15) that manages the bidding process from the end user, the auction Is composed of an auction information inquiry management unit (16) that manages information inquiry processing related to product information handled by each seller and individual product information of each exhibitor. These processing units receive data in response to requests from end users. It is activated by the transceiver (11).
Further, when the processing result of each processing unit is transmitted to the client terminal 4, a data transmission request is sent to the data transmitting / receiving unit (11).
The Web server (1) is connected to the database management server (2). In the database management server (2), a transaction management DB (D1) for managing each auction transaction, specifications of products handled in each auction, etc. Product information DB (D2) that manages information about the product, image files of the product, user management DB (D3) that manages account information such as names, addresses, and email addresses of end users participating in the auction, participates in each auction Trading participant management DB (D4) that manages the bid amount of the end user who is doing, information on the individual product of the end user participating as an exhibitor in the auction, for example, the usage state (new unopened), etc. The seller product information DB (D5) for managing the image files is constructed. In response to a request from an end user, the Web server (1) makes an access request to the database management server (2) when performing necessary database search processing or record addition / update processing.
When the auction period ends, or when the transaction between the exhibitor and the purchaser is completed and the process proceeds to an approval process, a mail transmission request is made from the Web server (1) to the mail server (3). Information is sent to the end user by e-mail.
In addition, the well-known technique at the time of application of this application is applied regarding an end user's account registration, account authentication, and the approval process after transaction completion.

FIG. 2 is a data configuration diagram showing a data configuration of a transaction management DB (D1) that manages basic information of each auction transaction. When the end user requests a new auction transaction on the new auction creation screen (M08) described later, a record (T02) in the transaction management DB is added by the new auction creation unit (12).
The auction ID (T021) uniquely identifies each auction transaction, and stores an ID numbered by the new auction creation unit (12) so as not to overlap with other auction transactions.
The auction start date and time (T022) represents the date and time when an auction transaction is newly created, and is used as information for calculating the auction end date and time. Information acquired by the new auction creation unit (12) is stored.
The auction end date / time (T023) represents the end of the holding period of each auction transaction, and is calculated by the new auction creation unit (12) from the auction start date / time (T022). This information is displayed on the screen and can be used by the end user as a basis for making a bid.
The auction completion flag (T024) is set as “0 (in transaction)” when an auction is newly created, and when the system time reaches the auction end date (T023), the auction period end part (14). Is updated to “1 (end)”. Thereafter, the auction transaction is not displayed on the auction list screen (M07) to be described later, and a transaction partner is selected between bidders as buyers / exhibitors.
The number of purchaser participants (T025) stores the number of end users who are bidding as buyers in each auction transaction. When a new auction is created, 0 is set as an initial value in the new auction creation unit (12), and a bid request is made on the bid screen (M11) as a purchaser, which will be described later, by the end user. Will be counted up one by one when bidding for the first time in the auction transaction. This information is displayed on the screen and can be used by the end user as a basis for making a bid. If this information exceeds the number of exhibitor participants (T026), which will be described later, all bidders who are bidding as buyers cannot complete the transaction.
The number of exhibitor participants (T026) stores the number of end users who are bidding as exhibitors in each auction transaction. When a new auction is created, 0 is set as an initial value in the new auction creation unit (12), and then a bid request is made on the bid screen (M13) as an exhibitor, which will be described later, by the end user. Will be counted up one by one when bidding for the first time in the auction transaction. This information is displayed on the screen and can be used by the end user as a basis for making a bid. If this information exceeds the number of buyers (T025), all bidders who are bidding as exhibitors cannot establish a transaction.
Stored as the number of purchaser transactions (T027) stores the number of purchasers who have already completed transactions with exhibitors in each auction transaction. After the auction end flag (T024) is updated to “1 (end)” at the end of the auction period (14), the transaction is concluded from a purchaser with a higher rank in the bid rank (T036) described later. The seller as a trading partner is selected in order, and when the transaction is established by this, the auction period end part (14) counts up one by one.
The number of exhibitor transactions established (T028) stores the number of exhibitors who have already completed transactions with purchasers in each auction transaction. After the auction end flag (T024) is updated to “1 (end)” at the end of the auction period (14), the transaction is concluded from a purchaser with a higher rank in the bid rank (T036) described later. The seller as a trading partner is selected in order, and when the transaction is established by this, the auction period end part (14) counts up one by one.

FIG. 3 is a data configuration diagram showing a data configuration of a transaction participant management DB that manages participants who bid as purchase applicants or exhibitors for each auction transaction. A record is added by the bid management section (15) when an end user who makes a bid for the first time in the auction transaction makes a bid request on the bid screen (M11) as a purchaser or the bid screen (M13) as an exhibitor described later The
The auction ID (T031) uniquely identifies each auction transaction, and is associated with the record (T02) and the auction ID (T021) in the transaction management DB (D1).
The user ID (T032) uniquely identifies each end user who is bidding in the auction, and stores an ID determined when each end user separately registers an account. This is used when acquiring the destination address of the notification mail to be transmitted when notifying the end of the auction to each end user from the record (T06) of the user management DB described later.
The bid type (T033) is information for determining whether the end user bidding in the auction is a bid as a purchase applicant or a bid as an exhibitor. When the end user makes a bid request from the bid screen (M11) as a purchaser, which will be described later, “1 (purchaser)”, and when the end user makes a bid request from the bid screen (M13), “2” (Exhibitor) "is stored in the bid management section (15).
The transaction establishment flag (T034) is information for determining whether or not each end user participating in the auction has already determined a transaction partner and a transaction has been established. When the record is added by the bid management unit (15), the initial value “0 (not established)” is stored, and the auction completed flag (T024) is set to “1 (end)” by the auction period end unit (14). Is updated to “1 (confirmed)” when a transaction is completed by selecting an exhibitor as a trading partner in order from a purchaser with higher priority in a bid order (T036), which will be described later. The
The bid price (T035) stores the bid price entered by the end user on the bid screen (M11) as a purchaser described later or the bid screen (M13) as an exhibitor. Based on this information, a bid rank (T036) described later is calculated.
The bid rank (T036) stores the rank calculated based on the bid amount (T035) for each purchase applicant / exhibitor in each auction transaction. Among the purchase requesters, the rank is calculated in descending order of the bid amount (T035), and the purchase requester who bids the highest price is ranked first. Among the exhibitors, the rank is calculated in ascending order of the bid amount (T035), and the exhibitor who bids the lowest price is ranked first.

FIG. 4 is a data configuration diagram showing a data configuration of a product information DB that manages information such as specifications related to products to be traded in each auction transaction and image files. When the end user makes an auction creation request on the new auction creation screen (M08) described later, a record is added by the new auction creation unit (12).
The auction ID (T041) uniquely identifies each auction transaction, and is associated with the record (T02) in the transaction management DB through the auction ID (T021).
The product name (T042) stores the name of the product handled in the auction transaction corresponding to the auction ID (T041). The product name (M081) input on the new auction creation screen (M08) described later is stored.
The product basic information (T043) stores information on specifications related to products handled in the auction transaction corresponding to the auction ID (T041). Stored is a description (M082) of a product input on a new auction creation screen (M08) described later. There are no particular restrictions on the input contents, and an end user who newly creates an auction transaction inputs arbitrarily.
The product image file 1 (T044) stores an image file related to the product. The file registered on the new auction creation screen (M08) described later is stored. Up to three product images can be registered for each auction transaction. The second file is stored in the product image file 2 (T045), and the third file is stored in the product image file 3 (T046).

FIG. 5 is a data configuration diagram showing the data configuration of the seller product information DB that manages the state explanation and image files for each seller who bids on each auction transaction. As an exhibitor, which will be described later, on the bid screen (M13), individual information related to the product is stored in the bid management unit (15). When an exhibitor bids for the first time as an exhibitor in the auction transaction, a record is added in the bid management section (15), and when the exhibitor makes a bid as an exhibitor for the second time or later in the auction transaction. Updates a record that has already been registered.
The auction ID (T051) uniquely identifies each auction transaction, and is associated with the record (T02) in the transaction management DB through the auction ID (T021). Even when the exhibitor participates in a plurality of auction transactions, the corresponding auction transaction can be specified.
The user ID (T052) uniquely identifies each end user who is bidding in the auction, and stores an ID determined when each end user separately registers an account. It is associated through a record (T03) in the transaction participant management DB and a user ID (T032).
The product information explanation (T053) stores individual explanations about the products owned by each seller regarding the products handled in the auction transaction, and mainly relates to the state of the product (whether it is new or used), and the product. Stores the contents inputted as the description (M135) of the commodity on the bidding screen (M13) as an exhibitor to be described later with notes (such as failure).
The product image file 1 (T054) stores individual image files related to products owned by each seller with respect to the products handled in the auction transaction, and the file registered on the bid screen (M13) as an exhibitor described later. Stored. Up to three product images can be registered for each auction transaction. The second file is stored in the product image file 2 (T055), and the third file is stored in the product image file 3 (T056).

FIG. 6 is a data configuration diagram showing a data configuration of a user management DB that manages information of end users who have registered accounts in the auction system. It is accessed when acquiring a destination address of a notification mail to be transmitted when notifying an end of an auction to each end user.
The user ID (T061) uniquely identifies an end user who has registered an account in the auction, and stores an ID determined when each end user registers an account. It is associated through a record (T03) in the transaction participant management DB and a user ID (T032).
The name (T062) stores the name information of the end user who has registered the account in the auction.
The address (T063) stores the address information of the end user who has registered an account in the auction.
The mail address (T064) stores the mail address of the end user who has registered an account in the auction. It is used as a destination for a notification mail that is transmitted when notifying an end of an auction to each end user.
The telephone number (T065) stores the telephone number information of the end user who has registered an account in the auction.

FIG. 7 is a screen layout diagram showing a screen configuration of an auction list screen that is initially displayed when the auction system is accessed. The end user can search for an auction transaction desired to be traded on this screen, or can create a new auction transaction when there is no desired auction transaction.
The auction list display field (M071) displays a list of records in which the auction completed flag (T024) is “0 (in transaction)” among the auction transactions registered in the record (T02) of the transaction management DB. The
The auction detailed information display button (M072) is installed for each auction transaction displayed in the auction list display field (M071), and when the end user clicks on this transaction, the auction information is displayed. Through the inquiry management unit (16), an auction detailed information display screen (M10), which will be described later, is displayed, and it becomes possible to browse detailed information related to the auction transaction.
The button (M073) for creating a new auction is clicked when a new auction transaction is created when the end user cannot find a transaction he / she wants to participate in from the auction list display field (M071). A new auction creation screen (M08) is displayed.

FIG. 8 is a screen layout diagram illustrating a screen configuration of a new auction creation screen for inputting information on products handled in the created transaction when the end user newly creates an auction transaction. The contents of the auction transaction created here are stored in the record (T02) in the transaction management DB and the record (T04) in the product information DB by the new auction creation unit (12).
In the product name input field (M081), the product name of the product handled in the newly created auction transaction is input. The content input here is stored in the product name (T042) of the record (T04) in the product information DB.
In the product description input field (M082), general information such as specifications of products handled in the newly created auction transaction is input. The content entered here is stored in the basic product information (T043) of the record (T04) in the product information DB.
The image file reference button (T083) is a button for registering an image file related to a product handled in a newly created auction transaction, and refers to a directory in the client terminal (4) of the end user and designates the image file. To do. For the designated image file, the path of the storage directory in the client terminal (4) is displayed in the registered image confirmation field (M084). From 0 to a maximum of 3 image files can be specified.
A new auction creation button (M085) is a button for confirming a new auction transaction after inputting information on a product handled in a newly created auction transaction. Through (12), records are added as a record (T02) in the transaction management DB and a record (T04) in the product information DB. Further, after the record is added to the DB, the new auction creation unit (12) shifts the screen to an auction creation result screen (M09) described later.

FIG. 9 is a screen layout diagram showing a screen configuration of an auction creation result screen that displays a creation result of a new auction transaction input on the new auction creation screen (M08). This screen was entered on the new auction creation screen (M08) in the new auction creation section (12) started by clicking the new auction creation button (M085) placed on the new auction creation screen (M08) The screen content is created and displayed based on the content.
The product image (M091) displays the contents of the image file designated by the image file reference button (M083) on the new auction creation screen (M08).
The button for returning to the auction list (M092), when clicked, changes the screen to the auction list screen (M07).

FIG. 10 is a screen layout diagram showing a screen configuration of an auction detailed information display screen for displaying detailed information of auction transactions displayed as a list on the auction list screen (M07). This screen is displayed when the auction detailed information display button (M072) arranged in the auction list display field (M071) on the auction list screen (M07) is clicked, the transaction management DB record (T02), and the product information DB record. The screen content is created and displayed by the auction information inquiry management unit (16) based on the information of (T04).
The auction basic information display field (M101) is based on the auction start date / time (T022), the auction end date / time (T023) of the record (T02) of the transaction management DB, and the product name (T042) of the record (T04) of the product information DB. Basic information about the auction transaction is displayed.
The detailed information display column (M102) of the product contains detailed information on the product handled in the auction transaction based on the basic product information (T043) and the product image files 1 to 3 (T044 to T046) in the record (T04) of the product information DB. Is displayed.
The auction bid field (M103) is obtained from the record number (T02) of the purchaser in the transaction management DB (T02), the number of participants (T026), and the auction ID (T031) from the record (T03) in the transaction participant management DB. ) Matches the auction ID of the auction transaction and the bid type (T033) is “1 (buyer)”, the amount information with the highest bid amount (T035), and the record of the transaction participant management DB (T03) to the auction ID (T031) matches the auction ID of the auction transaction and the bid type (T033) is “2 (exhibitor)”. Is displayed.
A bid button (M104) as a purchaser is a bidding screen as a purchaser described later by the bid management unit (15) when the user clicks this button when bidding as a purchase applicant in the auction transaction displayed on the screen. The screen is changed to (M11).
When a bid button (M105) as an exhibitor makes a bid for an auction transaction displayed on this screen as an exhibitor, when the button is clicked, the bid management unit (15) displays a bid screen ( The screen is changed to M13).
When the seller information display button (M106) is clicked when it is desired to refer to the individual information of the seller who has already participated in the auction transaction, the seller information display button (M106) is displayed through the auction information inquiry management unit (16). The person information inquiry screen (M15) is displayed.

FIG. 11 shows the screen configuration of the bid screen as a purchaser that is transitioned and displayed by the bid management section (15) when the bid button (M104) is clicked as a purchaser on the auction detailed information display screen (M10). FIG.
The auction basic information display field (M111) is based on the auction start date / time (T022), the auction end date / time (T023) of the record (T02) in the transaction management DB, and the product name (T042) of the record (T04) in the product information DB. Basic information about the auction transaction is displayed.
The purchase applicant list display field (M112) displays the bid amount of the participant who has already bid as a purchase candidate in the auction transaction together with the bid order, and is used as a judgment material in setting the bid amount of the end user who will bid from now on. It will be. This display content is stored in the bid management section (15) from the record (T03) in the transaction participant management DB, and the auction type (T031) is the same as the auction ID of the auction transaction currently displayed. The bid amount (T035) is acquired and displayed in the ascending order of the bid order (T036) with respect to those in which T033) is “1 (buyer)”.
The button for returning to the auction list (M113) is clicked to stop bidding and shift the screen to the auction list screen (M07).
The bid amount input field (M114) is an input field for inputting a bid amount.
The bid button (M115) is a button for confirming a bid as a purchaser, and the bid amount input in the bid amount input field (M114) is passed through the bid management unit (15) to the record ( Stored in the bid amount (T035) of T03). Here, the record in which the auction ID (T031) of the record (T03) in the transaction participant management DB matches the auction ID of the currently displayed auction transaction and the bid type (T033) is “1 (buyer)”. The order of the current bid amount input in the bid amount input field (M114) is determined and stored in the bid order (T036) of the record (T03) in the transaction participant management DB.

FIG. 12 is a screen layout diagram showing a screen configuration of the bid result screen as a purchaser displaying the bid result of the bid amount input on the bid screen (M11) as the purchaser. This screen shows the contents entered in the bid amount input field (M114) in the bid management section (15) and the bid amount when the bid button (M115) installed on the bid screen (M11) is clicked as a purchaser. The screen content is created and displayed based on the bid order calculated from the input content in the input field (M114).
The auction basic information display field (M121) is based on the auction start date / time (T022), the auction end date / time (T023) of the record (T02) in the transaction management DB, and the product name (T042) of the record (T04) in the product information DB. Basic information about the auction transaction is displayed.
In the bid result display field (M122), information on the bid type (T033), the bid amount (T035), and the bid rank (T036) stored in the record (T03) of the transaction participant management DB in the bid management unit (15) is displayed. Is displayed. The bid order displayed here is a material for determining whether the purchase applicant wishes to bid again.
The button for returning to the auction list (M123) changes the screen to the auction list screen (M07).

FIG. 13 shows the screen configuration of the bid screen as an exhibitor displayed by transition by the bid management unit (15) when the bid button (M105) is clicked as the exhibitor on the auction detailed information display screen (M10). FIG.
The auction basic information display field (M131) is based on the auction start date and time (T022), the auction end date and time (T023) of the record (T02) in the transaction management DB, and the product name (T042) of the record (T04) in the product information DB. Basic information about the auction transaction is displayed.
The exhibitor list display field (M132) displays the bid amount of the participant who has already bid as an exhibitor in the auction transaction together with the bid order, and is used as a judgment material in setting the bid amount of the end user who will make a bid from now on. Is. This display content is stored in the bid management section (15) from the record (T03) in the transaction participant management DB, and the auction type (T031) is the same as the auction ID of the auction transaction currently displayed. For T033) “2 (exhibitor)”, the bid amount (T035) is acquired and displayed in ascending order of the bid order (T036).
The button for returning to the auction list (M133) is clicked to stop bidding and shift the screen to the auction list screen (M07).
The bid amount input field (M134) is an input field for inputting a bid amount.
The product description input field (M135) is a field for inputting the state description of the product owned by the seller, and is stored in the product information description (T053) of the record (T05) of the seller product information DB. In the case of bidding for the same auction transaction for the second time and later, if this input field is not entered, the content entered last time will be maintained, but if there is input in this input field, the content entered last time will be the seller Discard from the product information description (T053) of the record (T05) in the product information DB, and register the contents input this time by overwriting.
The image file reference button (M136) is a button for registering an image file related to the merchandise owned by the seller, and refers to the directory in the client terminal (4) of the seller and designates the image file. For the designated image file, the path of the storage directory in the client terminal (4) is displayed in the registered image confirmation field (M137). From 0 to a maximum of 3 image files can be specified. In the case of bidding for the second time or more for the same auction transaction, if you do not specify an image file, the previously registered image file will be maintained, but if you specify even one image file, the previously registered image file will be used as the seller's product The product image files 1 to 3 (T054 to T056) in the record (T05) of the information DB are discarded, and the file designated this time is overwritten and registered.
The bid button (M138) is a button for confirming a bid as a purchaser. The bid amount input in the bid amount input field (M134) and the individual description of the owned product input in the product description input field (M135) The individual image file of the owned product designated by the image file reference button (M136) is passed through the bid management section (15), respectively, the bid amount (T035) of the record (T03) in the transaction participant management DB, and the exhibitor product. Stored in the product information description (T053) and product image files 1 to 3 (T054 to T056) of the record (T05) in the information DB. Here, the record in which the auction ID (T031) of the record (T03) in the transaction participant management DB matches the auction ID of the currently displayed auction transaction and the bid type (T033) is “2 (exhibitor)”. From this, the order of the current bid amount input in the bid amount input field (M134) is determined and stored in the bid order (T036) of the record (T03) of the transaction participant management DB.

FIG. 14 is a screen layout diagram showing a screen configuration of a bid result screen as an exhibitor displaying a bid result such as a bid amount inputted on the bid screen (M13) as an exhibitor. This screen is displayed when the bid button (M138) installed on the bid screen (M13) as an exhibitor is clicked, in the bid management section (15), the bid amount input field (M134), the product description input field ( M135), the screen content is created and displayed based on the bid order calculated from the image file designated by the image file reference button (M136) and the input content of the bid amount input field (M134).
The auction basic information display field (M141) is based on the auction start date / time (T022), the auction end date / time (T023) of the record (T02) of the transaction management DB, and the product name (T042) of the record (T04) of the product information DB. Basic information about the auction transaction is displayed.
The bid result display field (M142) includes information on the bid type (T033), bid amount (T035), bid rank (T036) stored in the record (T03) of the transaction participant management DB in the bid management unit (15), And the product information description (T053) stored in the record (T05) of the seller product information DB and the product image files 1 to 3 (T054 to T056). The bid order displayed here is a material for determining whether the applicant wishes to bid again.
The button for returning to the auction list (M143) changes the screen to the auction list screen (M07).

FIG. 15 is a screen layout diagram showing a screen configuration of a seller information inquiry screen for inquiring individual product information of sellers who are bidding for auction transactions. This screen is displayed when the exhibitor information display button (M106) is clicked on the auction detailed information display screen (M10).
The auction basic information display field (M151) is based on the auction start date / time (T022), the auction end date / time (T023) of the record (T02) of the transaction management DB, and the product name (T042) of the record (T04) of the product information DB. Basic information about auction transactions is displayed.
The seller list display field (M152) is the same as the auction ID of the auction transaction currently displayed by the auction ID (T031) of the record (T03) in the transaction participant management DB in the auction information inquiry management unit (16). The list is displayed in ascending order of the bid rank (T036) based on the bid amount (T035) and bid rank (T036) of the record whose bid type (T033) is “2 (exhibitor)”.
The seller information display button (M153) is installed for each record displayed in the seller list display field (M152), and the individual information of the corresponding seller will be described later by clicking this button. Displayed in the person information display field (M154).
In the seller information display field (M154), the individual information of the corresponding seller is displayed in the transaction participant management DB in the auction information inquiry management unit (16) by clicking the display button (M153) of the seller information. Based on the bid amount (T035) of the record (T03), the bid ranking (T036), the product information description (T053) of the record (T05) in the seller product information DB, and the product image files 1 to 3 (T054 to T056) Is displayed. The purchase applicant can refer to the contents of the inquiry and use it as a judgment material for determining whether or not to bid as a purchaser of the auction transaction.
The button for returning to the auction list (M155) changes the screen to the auction list screen (M07).

FIG. 16 shows that the auction period end unit (14) is activated for the auction transaction in which the auction period monitoring unit (13) detects that the end date and time of the auction has been reached. Screen layout diagram showing the screen configuration of the seller selection screen displayed by clicking on the URL described in the partner selection email notified to the highest bidder who is bidding through the mail server (3) It is. The auction ID of the corresponding auction can be identified from the address in the URL.
The auction basic information display field (M161) is based on the auction start date / time (T022), the auction end date / time (T023) of the record (T02) of the transaction management DB, and the product name (T042) of the record (T04) of the product information DB. Basic information about the auction transaction is displayed.
In the selectable exhibitor list display field (M162), the auction ID (T031) of the record (T03) in the transaction participant management DB can be identified from the URL in the notification mail at the end of the auction period (14). The bid amount (T035) and bid rank (T036) of the records that match, the bid type (T033) is “2 (exhibitor)”, and the transaction establishment flag (T034) is “0 (unestablished)”. The list is displayed in ascending order of the bid order (T036).
The selectable exhibitor information display button (M163) is installed for each record displayed in the selectable exhibitor list display field (M162), and by clicking this button, individual information of the corresponding exhibitor is displayed. Is displayed in the selectable exhibitor information display field (M164) described later.
In the selectable exhibitor information display field (M164), by clicking the display button (M163) of the selectable exhibitor information, the individual information of the corresponding exhibitor is entered into the transaction at the auction information inquiry management unit (16). Bid amount (T035), bid rank (T036) of the record (T03) of the seller management DB, product information description (T053) of the record (T05) of the seller product information DB, and product image files 1 to 3 (T054 to T056) ) Is displayed. The purchase applicant refers to the contents of the inquiry and selects a trading partner.
This seller selection button (M165) is a button for selecting the seller currently displayed in the selectable seller information display field (M164) as a trading partner. The establishment of the transaction between the applicant and the selected exhibitor is confirmed, and the purchase requester and the selected exhibitor are notified by e-mail through the mail server (3) at the end of the auction period (14). The Thereafter, approval processing is performed according to the contents of the mail.

FIG. 17 is a flowchart showing a processing procedure of data reception processing which is internal processing of the data transmitting / receiving unit (11). When the end user displays the site of this system on the Web browser and clicks the button on the screen, the processing request is transmitted to the data transmitting / receiving unit (11) of the Web server (1) through the public line network (5). The data transmission / reception unit (11) receives the processing request from the client terminal (4) and activates the processing (F1701).
In the message transmitted from the client terminal (4), the screen ID of the screen where the button or the like is clicked and the control ID of the clicked button are edited, and the data reception process corresponds to the screen ID in the processing request message. In addition, the function distribution process for each screen is activated (F1702).
The function distribution processing for each screen activated by the above refers to the control ID in the processing request message and activates internal processing (F1703). Thereafter, the next screen creation process corresponding to each screen ID / control ID is performed, and a transmission request is made to a data transmission process described later (F1704). Here, the details regarding the function distribution for each screen are listed below. However, the symbol added to each button in the screen layout diagram is used as the button control ID.
<Function distribution process when logging in to this auction system>
The auction list creation process (F19) is started, and then an auction list screen (M07) is created and a data transmission request is made.
<Function distribution process on auction list screen (M07)>
When the control ID is “M072”, the auction basic information inquiry process (F21) is started, and then an auction detailed information display screen (M10) is created to make a data transmission request. When the control ID is “M073”, a new auction creation screen (M08) is created and a data transmission request is made.
<Functional distribution process of new auction creation screen (M08)>
When the control ID is “M085”, a new auction creation process (F20) is started, and then an auction creation result screen (M09) is created and a data transmission request is made.
<Function distribution process on auction creation result screen (M09)>
When the control ID is “M092”, the auction list creation process (F19) is started, and then an auction list screen (M07) is created and a data transmission request is made.
<Function distribution process on auction detailed information display screen (M10)>
When the control ID is “M104”, a bidder list creation process (F22) is started, and then a bid screen (M11) is created as a purchaser to make a data transmission request.
When the control ID is “M105”, a bidder list creation process (F22) is started, and then a bid screen (M13) is created as an exhibitor and a data transmission request is made.
When the control ID is “M106”, the bidder list creation process (F22) is started, an exhibitor information inquiry screen (M15) is created, and a data transmission request is made.
<Functional distribution process of bid screen (M11) as a purchaser>
When the control ID is “M113”, the auction list creation process (F19) is started, and then an auction list screen (M07) is created and a data transmission request is made.
When the control ID is “M115”, the bid distribution process (F23) is started, and then a bid result screen (M12) is created as a purchaser and a data transmission request is made.
<Functional distribution process on the bid result screen (M12) as a purchaser>
When the control ID is “123”, the auction list creation process (F19) is started, and then the auction list screen (M07) is created and a data transmission request is made.
<Functional distribution process of bid screen (M13) as an exhibitor>
When the control ID is “M133”, the auction list creation process (F19) is started, and then the auction list screen (M07) is created and a data transmission request is made.
When the control ID is “M138”, the bid distribution process (F23) is started, and then a bid result screen (M14) is created as an exhibitor and a data transmission request is made.
<Functional distribution process of bid result screen (M14) as an exhibitor>
When the control ID is “M143”, the auction list creation process (F19) is started, and then the auction list screen (M07) is created and a data transmission request is made.
<Function distribution process on seller information inquiry screen (M15)>
When the control ID is “M155”, the auction list creation process (F19) is started, and then the auction list screen (M07) is created and a data transmission request is made.
When the control ID is “M153”, the seller information inquiry process (F28) is started, and then the seller information inquiry screen (M15) is created to make a data transmission request.
<Function distribution process on exhibitor selection screen (M16)>
When the control ID is “M163”, the seller information inquiry process (F28) is started, and thereafter, an exhibitor selection screen (M16) is created and a data transmission request is made.
When the control ID is “M165”, the transaction record creation process (F32) is started, and then mail transmission data is created and a mail transmission request is made.
<Function distribution process when starting from URL in the partner selection notification email>
A bidder list creation process (F22) is started, and then an exhibitor selection screen (M16) is created and a data transmission request is made.

  FIG. 18 is a flowchart showing a processing procedure of data transmission processing which is internal processing of the data transmitting / receiving unit (11). Screen data transmission request from data reception process (F17), mail transmission request from auction period end process (F30) described later, mail transmission request from higher bidder search process (F31) described later, transaction record creation process described later It is activated by a mail transmission request from (F32) (F1801), and determines whether the transmission request is screen data or mail transmission (F1802). If the transmission request is screen data transmission, the client is sent through the public line network (5). Screen data is transmitted to the terminal (4) (F1803), and in the case of mail transmission, a mail transmission request is made to the mail server (3) (F1804).

FIG. 19 is a flowchart showing a processing procedure of an auction list creation process which is an internal process of the auction information inquiry management unit (16). When the end user logs in to the auction system at the client terminal (4) and clicks the return to auction list button (M092) on the auction creation result screen (M09), the purchaser enters the auction list on the bid screen (M11). When the return button (M113) is clicked, the purchaser returns to the auction list on the bid screen (M13) when the user clicks the return to auction list (M123) on the bid result screen (M12) (M133). When the button is clicked, when the button for returning to the auction list (M143) is clicked on the bid result screen (M14) as the seller, the button for returning to the auction list (M155) is clicked on the seller information inquiry screen (M15). Activated by data reception processing (F17) That.
In this process, a record in which the auction completed flag (T024) is “0 (trading)” is read from the record (T02) in the transaction management DB in ascending order of the auction start date (T022), and the auction ID (T021), auction The start date / time (T022), the end date / time of the auction (T023), the number of purchaser participants (T025), and the number of exhibitor participants (T026) are acquired (F1901). Next, the record in which the auction ID (T041) is the same as the auction ID (T021) acquired from the record (T02) in the transaction management DB is read from the record (T04) in the product information DB, and the product name is acquired (F1902). This is repeated until the record end of the record (T02) in the transaction management DB is detected (F1903). Then, auction list data is created using the acquired information (F1904), and control is returned to the activation source. In the data reception process (F17), screen data is created based on the auction list data and a transmission request is made.

FIG. 20 is a flowchart showing a processing procedure of a new auction creation process which is an internal process of the new auction creation unit (12). When the new auction creation button (M085) is clicked on the new auction creation screen (M08), it is activated by the data reception process (F17).
In this process, the auction ID of the auction transaction created this time is numbered as a unique ID that does not overlap with the existing auction ID (F2001), the current time is acquired (F2002), and a prescribed auction transaction period (for example, 7 days) Etc.) (F2003), the auction ID / current time / auction end date / time is calculated from the auction ID (T021) / auction start date / time (T022) / auction end date / time (T02) in the transaction management DB record (T02). As for T023), the auction completed flag (T024) is “0 (trading)”, the number of buyers participating (T025), the number of exhibitor participants (T026), the number of buyer transactions established (T027), the seller transactions The number of established people (T028) is 0 and a record is added (F20 4) The input contents of the product name input field (M081) and product description input field (M082) edited in the processing request message and the image file specified in the registered image confirmation field (M084) are stored in the product information DB. Product name (T042), product basic information (T043), product image files 1 to 3 (T044 to T046) of record (T04), record added (F2005), auction stored in record (T02) of transaction management DB ID (T021), auction start date / time (T022), auction end date / time (T023), product name (T042) stored in record (T04) of product information DB, product basic information (T043), product image files 1 to 3 ( Auction creation result data is created based on T044-T046) (F2006), and control is performed to the activation source. It is. In the data reception process (F17), screen data is created based on the auction creation result data, and a transmission request is made.

FIG. 21 is a flowchart showing a processing procedure of the auction basic information inquiry process which is an internal process of the auction information inquiry management unit (16). When the auction detailed information display button (M072) is clicked on the auction list screen (M07), it is activated by the data reception process (F17).
In this process, a record in which the auction ID (T021) matches the inquiry target auction ID edited in the processing request message is read from the record (T02) in the transaction management DB (F2101), and the record ( The record in which the auction ID (T041) matches the inquiry target auction ID edited in the processing request message is read from (T04) (F2102), and the record read from the record (T02) in the transaction management DB is read. When the number of purchaser participants (T025) is one or more, the auction ID (T031) matches the inquiry target auction ID edited in the processing request message from the record (T03) in the transaction participant management DB and Records with a bid type (T033) of “1 (buyer)” and a bid rank (T036) of 1st (F2103), and when the number of exhibitor participants (T026) in the record read from the record (T02) in the transaction management DB is one or more, the record in the transaction participant management DB (T03) To the record in which the auction ID (T031) matches the inquiry target auction ID edited in the processing request message, the bid type (T033) is “2 (exhibitor)”, and the bid ranking (T036) is first. Read (F2104), auction based on bid amount (buyer and exhibitor) (T035), basic product information (T043), and product image files 1 to 3 (T044 to T046) read from each DB record above Detailed information data is created (F2105), and control is returned to the activation source. In the data reception process (F17), screen data is created based on the auction detailed information data and a transmission request is made.

FIG. 22 is a flowchart showing a processing procedure of a bidder list creation process which is an internal process of the auction information inquiry management unit (16). When a bid button (M104) is clicked as a buyer on the auction detailed information display screen (M10), when a bid button (M105) is clicked as an exhibitor on the same screen, a seller information display button (M106) is displayed on the same screen. When the button is clicked, when the system is accessed from the URL in the partner selection notification mail, it is activated by the data reception process (F17).
In the processing request message, in order to determine whether the acquisition target of the list is a purchaser or an exhibitor, “1 (buyer)” in the case of a bid button (M104) as a purchaser according to the activation source, In the case of accessing the system from the URL in the bid button (M105), the seller information display button (M106), and the partner selection notification mail as the seller, “2 (exhibitor)” is edited.
In this processing, the auction ID (T031) in the transaction participant management DB record (T03) matches the inquiry target auction ID edited in the processing request message, and the transaction establishment flag (T034) is set to “0 (not yet). Records) are read in ascending order of bid rank (T036) (F2201), this is repeated until the end of the record is detected (F2202), and the bid rank (T03) acquired from the record (T03) in the transaction participant management DB (T036)-Bidder list data is created based on the bid amount (T035) (F2203), and control is returned to the activation source. The data reception process (F17) creates screen data based on the bidder list data and requests transmission.

FIG. 23 is a flowchart showing a processing procedure of a bid distribution process which is an internal process of the bid management unit (15). When the buyer clicks the bid button (M115) on the bid screen (M11) as the purchaser, when the seller clicks the bid button (M138) on the bid screen (M13), it is activated by the data reception process (F17). .
In the processing request message, “1 (buyer)” is set as the bid type in the case of activation from the bid screen (M11) as a purchaser according to the activation source, and bidding is performed in the case of activation from the bid screen (M13) as the seller. “2 (exhibitor)” is edited as the type.
In this process, the auction ID (T031) matches the auction ID edited in the process request message from the record (T03) in the transaction participant management DB, and the user ID (T032) is edited in the process request message. The record that matches the user ID of the logged-in user is read (F2301), and it is determined whether or not the corresponding record exists (F2302). If there is no record, the process request message is entered as a new bidder. It is determined whether or not the bid is as a purchase applicant with reference to the edited bid type (2303). If the bid type is “1 (purchaser)”, a new purchaser addition process (F24) described later is performed. (F2304), if the bid type is “2 (exhibitor)”, a new exhibitor addition process (F25), which will be described later, is activated (F2305). If there is a record corresponding to the record (T03) in the customer management DB, whether the bid is a bid as a purchase requester with reference to the bid type already edited in the processing request message as a bidder who has already bid for the auction transaction. (2306) If the bid type is “1 (buyer)”, an existing participating buyer information update process (F26) described later is started (F2307), and the bid type is “2 (exhibitor). ) ”, An existing participant information update process (F27) described later is started (F2308). As soon as the activation destination process is completed, control is returned to the data reception process (F17) as the activation source.

FIG. 24 is a flowchart showing a processing procedure of a new purchaser addition process which is an internal process of the bid management unit (15). When the end user bids for the first time as a purchase applicant in the auction transaction, the bidding process (F23) is started.
In this process, the auction ID (T031) matches the auction ID edited in the processing request message from the record (T03) in the transaction participant management DB, and the bid type (T033) is “1 (buyer)”. A record in which the record to be read is read in descending order of the bid amount (T035) (F2401), the bid order (T036) of the acquired record is saved, and this is the purchaser whose bid amount (T035) is edited in the processing request message As described above, the transaction request message is auctioned to the record (T03) in the transaction participant management DB until it is smaller than the value of the bid amount input field (M114) input on the bid screen (M11) or until the end of the record is detected (F2402). ID / user ID / bid amount as auction ID (T031) / user ID (T032) / bid amount (T035) The tag type (T033) is “1 (buyer)”, the transaction establishment flag (T034) is “0 (unestablished)”, and the bid ranking (T036) is the last from the record (T03) in the transaction participant management DB. A record is added as a bid ranking of the read record (F2403), and the record (T03) in the transaction participant management DB matches the auction ID whose auction ID (T031) is edited in the processing request message and the bid type ( An update is performed to add the bid rank (T036) one by one to the record (T033) is “1 (buyer)” and the bid amount (T035) is smaller than the bid amount edited in the processing request message (F2404) This is repeated until the end of the record is detected (F2405), and the record (T02) in the transaction management DB is processed by the auction ID (T031). An update is made by adding one person (T025) to the record that matches the auction ID edited in the request message (F2406), and the bid type / bid amount / transaction edited in the processing request message is updated. Bidding result information data is created based on the contents stored in the bid ranking (T036) of the record (T03) additional record in the participant management DB (F2407), and control is returned to the activation source.

FIG. 25 is a flowchart showing a processing procedure of a new exhibitor addition process which is an internal process of the bid management unit (15). When the end user bids for the first time as an exhibitor in the auction transaction, it is activated from the bid distribution process (F23).
In this processing, the auction ID (T031) in the transaction participant management DB record (T03) matches the auction ID edited in the processing request message, and the bid type (T033) is “2 (exhibitor)”. Records that are read in ascending order of bid amount (T035) (F2501), the bid order (T036) of the acquired record is saved, and the bid amount (T035) is edited in the processing request message. Until the value of the bid amount input field (M134) entered on the bid screen (M13) becomes larger than the value or until the end of the record is detected (F2502), and the transaction request message auction is stored in the record (T03) of the transaction participant management DB. ID / user ID / bid amount as auction ID (T031) / user ID (T032) / bid amount (T035) The tag type (T033) is “2 (exhibitor)”, the transaction establishment flag (T034) is “0 (unestablished)”, and the bid ranking (T036) is the last from the record (T03) in the transaction participant management DB. A record is added as a bid rank of the read record (F2503), and the auction ID / user ID / product description input field (M135) edited in the processing request message is added to the record (T05) of the seller product information DB. Record the image file specified in the input contents / registered image confirmation field (M137) as auction ID (T051), user ID (T052), product information description (T053), product image files 1 to 3 (T054 to T056) Is added (F2504), and the record (T03) in the transaction participant management DB is processed by the auction ID (T031). Bid order (T033) is “2 (exhibitor)” and the bid amount (T035) is larger than the bid amount edited in the processing request message. T036) is added one by one (F2505), and this is repeated until the end of the record is detected (F2506), and the record (T02) in the transaction management DB is edited into the auction request message (T031). An update is performed by adding one exhibitor participant number (T026) to the record that matches the current auction ID (F2507), and the bid type / bid amount / transaction participant management DB edited in the processing request message is updated. Contents (Exhibitor Product Information DB) record (T05) added to record (T03) added record bid rank (T036) Bid result information data is created based on the contents stored in the product information description (T053) and product image files 1 to 3 (T054 to T056) of the record (F2508), and control is returned to the activation source.

FIG. 26 is a flowchart showing a processing procedure of an existing participant purchaser information update process which is an internal process of the bid management unit (15). When the end user bids on the auction transaction as a purchase requester for the second time or later, it is started from the bid distribution process (F23).
In this process, the auction ID (T031) matches the auction ID edited in the processing request message from the record (T03) in the transaction participant management DB, and the bid type (T033) is “1 (buyer)”. A record in which the record to be read is read in descending order of the bid amount (T035) (F2601), the bid order (T036) of the acquired record is saved, and the purchase amount whose bid amount (T035) is edited in the processing request message Until it is smaller than the value in the bid amount input field (M114) input on the bid screen (M11) or until the end of the record is detected (F2602), and the auction ID (T031) of the record (T03) in the transaction participant management DB That match the auction ID of the processing request message and the user ID (T032) matches the user ID of the processing request message. Update the record with the bid amount (T035) for the transaction mode and the bid amount and bid rank (T036) of the request message in the above as the bid rank of the record last read from the record (T03) in the transaction participant management DB (F2603), the record (T03) of the transaction participant management DB matches the auction ID edited in the processing request message in the auction ID (T031) and the bid type (T033) is “1 (buyer)” and An update is performed by adding the bid rank (T036) to the record whose bid price (T035) is smaller than the bid price edited in the processing request message (F2604), and this is repeated until the end of the record is detected. (F2605), record (T03) update record of bid type / bid amount / transaction participant management DB edited in the processing request message The contents stored in the bidding ranking (T036) to create the bid result information data based on (F2606), control is returned to the originator.

FIG. 27 is a flowchart showing a processing procedure of an existing participant information update process that is an internal process of the bid management unit (15). When the end user bids for the auction transaction as an exhibitor for the second time or later, it is started from the bid distribution process (F23).
In this processing, the auction ID (T031) matches the auction ID edited in the processing request message from the record (T03) in the transaction participant management DB, and the bid type (T033) becomes “2 (exhibitor)”. Records are read in ascending order of the bid amount (T035) (F2701), the bid order (T036) of the acquired record is saved, and this is bid as an exhibitor whose bid amount (T035) is edited in the processing request message Repeat until the value of the bid amount input field (M134) input on the screen (M13) becomes larger than the value of the record or the end of the record is detected (F2702), and the auction ID (T031) of the record (T03) in the transaction participant management DB is processed. In a record that matches the auction ID of the request message and the user ID (T032) matches the user ID of the process request message The bid amount (T035) is updated with the bid amount / bid rank (T036) of the processing request message as the bid rank of the record read last from the record (T03) in the transaction participant management DB (F2703). ), The auction ID (T051) of the record (T05) in the seller product information DB matches the auction ID edited in the processing request message, and the user ID (T052) matches the user ID edited in the processing request message. If the product description is edited in the processing request message for the record to be processed, the product information description (T053). If the product image file is edited in the processing request message, the product image files 1 to 3 (T054 to T054). The record is updated as (T056) (F2704), and the record (T03) in the transaction participant management DB is auctioned. From the bid amount whose ID (T031) matches the auction ID edited in the processing request message, the bid type (T033) is “2 (exhibitor)”, and the bid amount (T035) is edited in the processing request message Update the bid order (T036) by 1 for each large record (F2705), repeat this until the end of the record is detected (F2706), and edit the bid type / bid amount edited in the processing request message -Contents stored in bidding rank (T036) of record (T03) update record in transaction participant management DB-Exhibitor product information DB record (T05) Product information description of update record (T053)-Product image files 1-3 Bidding result information data is created based on the contents stored in (T054-T056) (F2707), and control is returned to the activation source.

FIG. 28 is a flowchart showing the procedure of the seller information inquiry process, which is an internal process of the auction information inquiry management unit (16). Data is displayed when the display of seller information that can be selected is clicked on the seller selection screen (M16) when the display button (M163) of the seller is clicked on the seller information inquiry screen (M15). It is activated by the reception process (F17).
In this process, the user whose auction ID (T051) matches the auction ID edited in the processing request message from the record (T05) in the seller product information DB and whose user ID (T052) is edited in the processing request message. The record that matches the ID is read (F2801), the seller information based on the product information description (T053) and product image files 1 to 3 (T054 to T056) of the record acquired from the record (T05) of the seller product information DB. Inquiry data is created (F2802), and control is returned to the activation group. In the data reception process (F17), screen data is created based on the data and a transmission request is made.

FIG. 29 is a flowchart showing a processing procedure of an auction period monitoring process which is an internal process of the auction period monitoring unit (13). This process is started periodically (for example, every second) in this system.
In this processing, the current time is acquired (F2901), the auction end date / time (T023) is before the current time acquired above from the record (T02) in the transaction management DB, and the auction end flag (T024) is “0 (transaction). Middle) ”is read in ascending order of the auction end date and time (T023) (F2902), the acquired records are delivered and an auction period end process (F30) described later is started (F2903). Until it is detected (F2904).

FIG. 30 is a flowchart showing a processing procedure of an auction period end process which is an internal process of the auction period end unit (14). The record of the record (T02) in the transaction management DB is activated as input information for the auction transaction in which the end of the auction holding period is detected in the auction period monitoring process (F29).
In this process, the auction completed flag (T024) is set to “1 (end)” for the record in which the auction ID (T021) of the record (T02) in the transaction management DB matches the auction ID received from the auction period monitoring process (F29). (F3001), the record in which the auction ID matches the auction ID (T021) received from the auction period monitoring process (F29) is read from the record (T03) in the transaction participant management DB (F3002), and the user management DB From the record (T06), the record in which the user ID (T061) matches the user ID (T032) of the record acquired from the record (T03) in the transaction participant management DB is read (F3003), and the record (T06) in the user management DB E-mail address obtained from (T0 4) Create auction end notification data based on the contents of (4) (F3004), send a mail transmission request to the data transmission process (F18) (F3005), and execute the processes from F3002 to F3005 in the record of the transaction participant management DB It repeats until the end of the record of (T03) is detected (F3006), the record of the record (T02) of the transaction management DB received from the auction period monitoring process (F29) is delivered and the upper bidder search process (F31) is started ( F3007), the process is terminated.

FIG. 31 is a flowchart showing a processing procedure of a higher bidder search process which is an internal process of the auction period end unit (14). Either any purchase applicant or exhibitor who is bidding on the auction transaction has completed the transaction, or bids a bid amount that is smaller than the bid amount of the purchaser with the highest bid rank where the transaction has not been completed. It is started from a transaction record creation process (F32) described later until no exhibitor exists.
In this process, the auction ID (T031) from the record (T03) in the transaction participant management DB matches the auction ID received from the auction period end process, the bid type (T033) is “1 (buyer)”, and the transaction is completed. One record with the flag (T034) being “0 (not established)” is read in ascending order of bid rank (T036) (F3101). If there is a corresponding record (F3102), a record ( The auction ID (T031) from T03) matches the auction ID received from the auction period end process, the bid type (T033) is “2 (exhibitor)”, and the transaction establishment flag (T034) is “0 (not established)”. And the bid amount (T035) of the purchase applicant obtained from the record (T03) of the transaction participant management DB as described above One record smaller than the bill amount (T035) is read in ascending order of bid order (T036) (F3103). If there is a corresponding record (F3104), the user ID (T061) is obtained from the record (T06) in the user management DB. A record that matches the user ID (T032) of the purchase applicant obtained from the record (T03) in the transaction participant management DB is read (F3105), and the mail address of the record obtained from the record (T06) in the user management DB ( T064)-Create seller selection notification data as a trading partner for the buyer who wishes to purchase based on the URL information for seller selection (F3106), and send a mail transmission request to the data transmission process (F18). (F3107) and the process is terminated.

FIG. 32 is a flowchart showing the transaction procedure for creating transaction results, which is an internal process of the auction period end section (14). When the purchase applicant clicks this seller selection button (M165) on the seller selection screen (M16) from the URL described in the body of the seller selection notification email transmitted in the upper bidder search process (F31) Is activated by the data reception process (F17).
In the processing request message, the bid order of the exhibitor selected by the purchase applicant from the exhibitor selection screen (M16) is edited.
In this processing, the auction ID (T031) matches the auction ID edited in the processing request message from the record (T03) in the transaction participant management DB, and the user ID (T032) is edited in the processing request message. A record that matches the user ID of the purchase applicant is read (F3201), and the auction ID (T031) matches the auction ID edited in the processing request message from the record (T03) in the transaction participant management DB and the bid type ( T033) is read as “2 (exhibitor)” and the bid order (T036) is edited in the processing request message, and the record corresponding to the bid order of the seller selected by the purchase applicant is read (F3202). The bid amount (T035) of the record acquired from the record (T03) in the transaction participant management DB and the above F In 202, the total amount of the bid amount (T035) of the record acquired from the record (T03) in the transaction participant management DB is divided by 2 (truncated after the decimal point) as the transaction amount (F3203). A record in which the auction ID (T031) of the record (T03) matches the auction ID edited in the processing request message and the user ID (T032) matches the user ID of the purchase requester edited in the processing request message The transaction completion flag (T034) is updated to “1 (completed)” (F3204), and the auction ID (T031) of the record (T03) in the transaction participant management DB is edited in the processing request message. The user ID (T03) of the record that matches the ID and the user ID (T032) is acquired in F3202 above. ) Is updated to “1 (confirmed)” for the record that matches (), and the user ID (T061) is edited from the record (T06) in the user management DB into a processing request message. A record that matches the user ID of the purchase applicant is read (F3206), and the user ID (T061) from the record (T06) in the user management DB matches the user ID (T032) of the record acquired in F3202 above. (F3207), transaction completion notification data is created based on the transaction amount calculated in F3203, the mail address (T064) of the record acquired in F3206, and the mail address (T064) of the record acquired in F3207. A mail transmission request is made to the transmission process (F18) (F320). 8) The number of buyer transactions established (T027) and the number of exhibitor transactions established (T027) and the number of seller transactions established (T027) for the record in which the auction ID (T021) of the record (T02) in the transaction management DB matches the auction ID edited in the processing request message. T028) is added and updated (F3209), and the number of purchaser transactions established (T027) after the update in F3209 is equal to the number of purchasers participating (T025) or the number of exhibitor transactions established (T028) When the number of exhibitors has become equal to the number of participants (T026), the process is terminated.

  The present invention can be used not only for an auction system in which a purchaser and an exhibitor purchase and sell one item of merchandise, but also in an auction system for purchasing or listing a plurality of the same items. Further, the present invention can be applied to a system that processes transactions similar to an auction, such as a second-hand goods sales system, a recycling system, and a reuse system, without sticking to the naming of an auction system.

Symbols described in parentheses at the end of each object name also indicate the reference numerals assigned to the objects in the figure in order to clearly indicate each object defined in the figure.
When the code is only a number (one digit), it represents a system component in the system configuration diagram.
DESCRIPTION OF SYMBOLS 1 Web server 2 Database management server 3 Mail server 4 Client terminal 5 Public line network When a code | symbol is only a number (2 digits), it represents the processing element in a system block diagram.
11 Data transmission / reception unit 12 New auction creation unit 13 Auction period monitoring unit 14 Auction period end unit 15 Bid management unit 16 Auction information inquiry management unit When a code starts with an initial D, it represents a database in the system configuration diagram.
D1 Transaction management DB
D2 Product information DB
D3 User management DB
D4 Trading Participant Management DB
D5 Exhibitor Product Information DB
When the code starts with the initial letter T and the number that continues is two digits, it represents a table in the data structure diagram.
T02 Transaction Management DB Record T03 Transaction Participant Management DB Record T04 Product Information DB Record T05 Exhibitor Product Information DB Record T06 User Management DB Record If the number starts with the initial letter T and the number continues is 3 digits, data Represents a table component of a configuration diagram.
T021 Auction ID
T022 Auction start date and time T023 Auction end date and time T024 Auction finished flag T025 Purchaser participation number T026 Exhibitor participation number T027 Purchaser transaction establishment number T028 Exhibitor transaction establishment number T031 Auction ID
T032 User ID
T033 Bid type T034 Transaction establishment flag T035 Bid amount T036 Bid rank T041 Auction ID
T042 Product name T043 Product basic information T044 Product image file 1
T045 product image file 2
T046 product image file 3
T051 Auction ID
T052 User ID
T053 Product information description T054 Product image file 1
T055 product image file 2
T056 product image file 3
T061 User ID
T062 Name T063 Address T064 E-mail address T065 Telephone number When the number starts with the initial letter M and the number is two digits, it represents the screen of the screen layout diagram.
M07 Auction list screen M08 New auction creation screen M09 Auction creation result screen M10 Auction detailed information display screen M11 Bid screen as a buyer M12 Bid result screen as a buyer M13 Bid screen as an exhibitor M14 Bid result screen as an exhibitor M15 Exhibitor information Inquiry screen M16 Exhibitor selection screen When the code starts with the initial letter M and the number that continues is three digits, it represents a screen component of the screen layout diagram.
M071 Auction list display field M072 Auction detailed information display button M073 Button for creating new auction button M081 Product name M082 Product description M083 Image file reference button M084 Image file file path M081 New auction creation button M091 Image of this product M092 Button for returning to auction list M101 Auction basic information display field M102 Detailed information display field for product M103 Auction bid field M104 Bid button as a buyer M105 Bid button as an exhibitor M106 Display seller information button M111 Auction basic information display field M112 Person list display field M113 Return to auction list button M114 Bid amount input field M115 Bid button M121 Auction basic information display Field M122 Bid result display field M123 Auction list return button M131 Auction basic information display field M132 Exhibitor list display field M133 Return to auction list button M134 Bid amount input field M135 Product description M136 Image file reference button M137 Registered image confirmation field M138 Button for bidding M141 Auction basic information display field M142 Bid result display field M143 Return to auction list button M151 Auction basic information display field M152 Exhibitor list display field M153 Exhibitor information display button M154 Exhibitor information display field M155 Auction list Back button M161 Auction basic information display field M162 Selectable exhibitor list display field M163 Display information of selectable exhibitor button M164 Selectable exhibitor information display field M1 65 Select this exhibitor button If the number starts with the initial letter F and continues for two digits, it represents the processing of the flowchart.
F17 Data reception process F18 Data transmission process F19 Auction list creation process F20 New auction creation process F21 Auction basic information inquiry process F22 Bidder list creation process F23 Bid allocation process F24 New buyer addition process F25 New exhibitor addition process F26 Existing participation Purchaser information update process F27 Participant information update process F28 Exhibitor information inquiry process F29 Auction period monitoring process F30 Auction period end process F31 Upper bidder search process F32 Transaction record creation process Numbers starting with the initial letter F In the case of 4 digits, it represents a processing element of the flowchart.
F1701 Start by receiving data from client terminal F1702 Processing distribution by source screen When the code starts with an alphabet, the first two digits of the following numeric part correspond to each figure number.

Claims (3)

A system with a seller-driven auction in which the buyer bids the purchase price to acquire the purchase right of the product and a buyer-driven auction in which the seller bids the sale price and acquires the right to sell the product. There,
A user interface that allows a bidder who wishes to participate in an auction transaction to select whether to bid as a buyer who wants to purchase a product or as a seller who wants to sell a product;
Means for managing bids as buyers who wish to purchase products according to the bidder's selection, means for managing bids as sellers who wish to sell products, and control distribution means to the management means,
It has a data structure that makes it possible to distinguish between a specific auction transaction, bidders participating in the auction transaction, and whether each bidder is a buyer who wants to purchase a product or a seller who wants to sell a product An external storage device;
Including data storage means for the external storage device;
This enables bidding for both buyers who want to purchase products and sellers who want to sell products for a single auction transaction, combining seller-driven auctions with buyer-driven auctions. A multi-transaction auction system with combined seller-buyer. A system with a seller-driven auction in which the buyer bids the purchase price to acquire the purchase right of the product and a buyer-driven auction in which the seller bids the sale price and acquires the right to sell the product. There,
A user interface for entering individual product information of bidders who are bidding as sellers in auction transactions;
An external storage device for storing the information;
Data storage means in the external storage device,
A user interface that allows a specific bidder bidding on the seller side to be selected to query individual product information of each bidder who is bidding on the seller side for those who wish to bid on auction transactions;
Means for retrieving individual product information of the selected bidder from an external storage device;
A means for displaying individual product information of a specific bidder searched for to a requester and a user interface,
In addition, a user interface for a person who wishes to bid for an auction transaction inquires a list information regarding a bid amount and a bid rank in each of a bidder as a buyer and a bidder as a seller in the auction transaction;
Means for creating the list information;
By providing a user interface that displays the list information to the requester,
A seller-buyer combined multi-transaction auction system that enables a person who wishes to bid for an auction transaction to provide information for determining whether or not to bid and setting a bid amount. A seller-driven auction in which the buyer bids for the purchase amount to acquire the purchase rights of the item,
A buyer-driven auction management method in which the seller side bids the sale amount and acquires the right to sell the product,
Means for calculating the current bidding order for each buyer and seller when bidding for an auction transaction;
An external storage device having a data structure for storing the calculated bid order;
Data storage means in the external storage device,
Means to find the highest bidder bidder among the buyers at the end of the auction transaction period,
Means for creating list information for selecting seller-side bidders for buyers with highest bidder-side bidders;
A communication means for communicating a notification for selecting a seller-side bidder;
A user interface for a buyer with the highest bidder to select a seller bidder,
A transaction amount calculation means for setting a transaction amount traded between both bidders as an intermediate value of both bid amounts;
Communication means for notifying both bidders of the completion of the transaction,
Until all of the buyer-side bidder and the seller-side bidder are successful in the transaction between the bidders excluding the buyer-side highest bid ranking and the seller-side bidder selected by the buyer-side highest bid ranking, By providing a control means to select the seller-side bidder for the buyer-side highest bidder and repeat the transaction,
Multiple seller-buyer complex types that allow a bidder to participate in a single auction and establish a product transaction with a higher probability by establishing a combination of multiple transactions between seller-side bidder and buyer-side bidder in one auction transaction Trading auction system.

Images