KR20080074825A - System for operating events - Google Patents

Abstract

A system for operating events is provided to keep consumption psychology of buyer clients and increase sales largely in an Internet shopping mall using a joint purchase mode by providing a real article return event discriminated from event services of other Internet shopping malls. An information storage unit stores minimum buyer client number information for opening an event for selling goods to a storage medium by linking with goods information. The event is related to lottery for returning a part of sale profit to at least one buyer client(100) participated in goods purchase. An information checker determines whether or not the event can be opened by checking the number of buyer clients participated in the goods purchase and the minimum buyer client number information capable of opening the event. An event operator opens the event to the buyer clients participated in the goods purchase when the event can be opened based on a determination result.

Description

Event operating system {System for Operating Events}

1 is a simple block diagram showing a structure of a joint purchase event system and an operation method according to an embodiment of the present invention.

Figure 2 is a block diagram illustrating in detail the interior of the joint purchase event management system.

3 is a simple block diagram schematically illustrating the inside of the comprehensive information DB.

4 is a simple example of a virtual profitability information table for a joint purchase transaction.

5 is an example implementation of a user screen provided by a main server to a sales client for event setup.

6 is an example implementation of a simple user screen provided by the main server to the sales client for in-kind payment setting.

7 is a simple flowchart of the process of joint purchase event.

8 illustrates transaction code information used to generate and update transaction information in a main server of a joint purchase event management system as a transaction code table according to an embodiment of the present invention.

9 illustrates an example of a product information table stored in the product information DB by an embodiment of a joint purchase event management system.

FIG. 10 illustrates an example of a buyer information table stored in a buyer DB by one embodiment of a joint purchase event management system.

11 illustrates an example of a seller information table stored in a transaction information DB by one embodiment of a joint purchase event operation system.

12 illustrates an example of a transaction information table stored in a transaction information DB by one embodiment of a joint purchase event operation system.

Fig. 13 is a simple block diagram illustrating the inside of a main server of a joint purchase event operating system.

Fig. 14 is a block diagram briefly showing the internal structure of the information collecting unit, the information processing unit, and the information transmitting unit.

Fig. 15 is a block diagram simply showing an internal configuration of an event logic processing unit.

FIG. 16 is a simple flowchart of a process in which a joint purchase event operation system processes a process of a purchase client accessing a joint purchase event operation system and purchasing an item in a joint purchase manner.

Figure 17 shows a simple flow diagram of the process from when the purchasing client accesses the collective purchase event management system to the collective purchase event operating system to generate and complete the joint purchase event.

18 is a simple flowchart of a process in which a joint purchase event operating system processes a process of a sales client selling a product in a joint purchase manner.

Fig. 19 shows a simple flowchart of the process from when the sales client accesses the joint purchase event operation system to the joint purchase event operation system to generate and complete the joint purchase event.

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

100: purchasing client 105: co-purchase event operating system

110: Sales Client 200: Billing Server

205: Shipping Server 210: Event Server

215: main server 220: comprehensive information DB

225: Product Information DB 230: Buyer DB

235: merchant DB 240: transaction information DB

300: profitability information 305: transaction code information

310: payment information 315: shipping information

320: event information 800: transaction code information table

900: Product Information Table 1000: Buyer Information Table

1100: Merchant Information Table 1200: Transaction Information Table

1300: information collecting unit 1305: event logic processing unit

* 1310: information processor 1315: information transmitter

1420: profitability information collector 1445: code information collector

1430: the payment information collection unit 1440: the event information collection unit

1450: distribution information processing unit 1455: transaction setting processing unit

1460: transaction information processing unit 1455: event information processing unit

1475: product information processing unit 1480: profitability information processing unit

1505: new group reasoning unit 1510: organized group processing unit

1515: spot return reference processing unit 1520: special rule reference processing unit

1525: drawing rule reference processing unit 1530: event logic information transmitting unit

The present invention is a predetermined event by linking the minimum number of buyers information for the event-held event-such as a lottery to return a part of the event-product sales profits to the at least one or more buyers participating in the product purchase Information storage means for storing the information stored in a storage medium, the total number of buyers participating in the product purchase and the minimum number of unit buyers for holding the event stored in the storage medium, and information checking means for determining whether the event can be held; As a result of the determination, when it is possible to hold the event, the present invention relates to an event operating system including an event operating means for holding the event for buyers participating in the product purchase.

Recently, due to the development of communication means such as the Internet, the shopping mall server provides the product information to the terminals of a plurality of buyers connected through the network online, such as the web environment of the Internet, and the payment of the product price is made online. Online shopping malls that carry out various electronic commerce in the form of delivery of goods to buyers using courier services are widely used.

In particular, 'co-purchasing' e-commerce, one of the examples widely used in the field of electronic commerce, generally allows multiple individual individual buyers to purchase the same product at the same time. It is possible to sell a large number of products, the profitability is high, and thus has the advantage of providing a large discount to the co-buyer.

In this co-purchase method, the greater the number of co-purchased products or the number of co-buyers at a time, the more favorable it is to the sales client. You can expect to be able.

For reference, according to the conventional method, the so-called 'sliding' joint purchase method is known as a method in which a commodity price is gradually lowered according to the number of joint purchasers.

However, the joint purchase, which has been conventionally implemented, has a point discount method or coupon payment that is executed in various internet shopping malls dealing with the latest products having shorter market launch cycles compared to the relatively long time-to-market cycles of products. Special offers, such as additional discounts or giveaways, tend to be neglected by buyers, even though they offer high discount rates because of their weak competitiveness.

An object of the present invention is to link the minimum number of buyers information for the event-held event, such as a lottery to return a portion of the event-product sales revenue to the at least one or more buyers participating in the purchase Information storage means for processing and storing in a predetermined storage medium, the total number of buyers participating in the product purchase and the minimum number of buyers for holding the event stored in the storage medium to determine whether the event can be held According to the verification means and the determination result, if the event can be held, it provides an event operating system including an event operating means for holding the event for the buyers participating in the product purchase.

The event management system according to the present invention, the event information, such as a lottery to return a part of the event-product sales profits in accordance with the sale of goods to at least one or more buyers participating in the product purchase-the minimum unit buyer information for holding the product Information storage means for storing information in a predetermined storage medium in association with the information, and checking the total number of buyers participating in the product purchase and the minimum number of unit buyers for holding the event stored in the storage medium to determine whether the event can be held. Information determination means for determining and as a result of the determination, if the event can be held, characterized in that it comprises an event operating means for holding the event for buyers participating in the product purchase.

Hereinafter, with reference to the accompanying drawings and description will be described in detail the operating principle of the preferred embodiment of the present invention.

However, the drawings and the following description shown below are for the preferred method among various methods for effectively explaining the features of the present invention, the present invention is not limited only to the drawings and description below.

In addition, in the following description of the present invention, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted.

In addition, terms to be described below are terms defined in consideration of functions in the present invention, which may vary according to the intention or convention of a user or an operator.

Therefore, the definition should be made based on the contents throughout the present invention.

In addition, preferred embodiments of the present invention to be carried out below are provided in each system functional configuration to efficiently describe the technical components constituting the present invention, or system functions commonly provided in the technical field to which the present invention belongs. The configuration will be omitted, and described mainly on the functional configuration to be additionally provided for the present invention.

If those skilled in the art to which the present invention pertains, it will be able to easily understand the function of the components that are conventionally used among the omitted functional configuration not shown below, and also the configuration omitted as described above The relationship between the elements and the components added for the present invention will also be clearly understood.

In addition, the following examples will be used to appropriately modify the terms so that those skilled in the art to clearly understand the technical features of the present invention to effectively understand, but the present invention It is by no means limited.

As a result, the technical spirit of the present invention is determined by the claims, and the following examples are one means for efficiently explaining the technical spirit of the present invention to those skilled in the art to which the present invention pertains. It is only.

1 is a simple block diagram showing the structure of a joint purchase event operating system 105 and an operating method according to an embodiment of the present invention.

For reference, the event referred to in the present invention is to say in advance that the collective purchase event.

As shown in FIG. 1, the joint purchase event operating system 105 is largely composed of a purchase client 100, a sales client 110, the Internet, and a joint purchase event operating system 105.

The purchase client 100 accesses the co-purchase event system to search for or receive information on a product to purchase, and receives a product purchased through a joint purchase together with the other purchase clients 100 for a purchase decision. As a subject, when the personal information and the target product and transaction information are delivered to the joint purchase event operation system 105 and the desired product is secured through the joint purchase, payment information 310 is received from the joint purchase event operation system 105. The delivery information 315 and the event information 320 are received to participate in the event.

For reference, the personal information means information that records the ID (ID), name, address, shipping address, contact information, bank account number, etc. of the purchaser. If the subject to input the information becomes a sales client, the personal information It can be used as a customer ID (ID), name, address, shipping address, contact, bank account number, etc. of the customer, some of the information in advance in the registration process, such as the joint purchase event operating system 105 It may be provided as.

In addition, the transaction information is generated by the joint purchase event operating system 105 whenever a transaction for a joint purchase occurs, transaction information ID, product ID, transaction details, payment means, amount, buyer ID, transaction quantity It means a status code (code), and the payment information 310 and the delivery information 315 are information related to the progress and results of payment and delivery that are commonly understood in the current Internet market service, and a detailed description thereof will be omitted. .

In addition, the above-mentioned event information 320 is related to the execution logic of the differential spot return event for the joint purchase customers, and more specifically, it is applied in relation to the differential setting of event participant oversufficiency and spot return. Information including an event rule and a winning criteria, which will be described in more detail with reference to FIG. 3.

The sales client 110 is a subject that accesses the joint purchase event operation system 105 to provide product information of a target to be sold in the form of a joint purchase and provides a joint purchase event to buyers participating in the joint purchase. The sales client 110 having one ID provides product information, such as product name, collective purchase transaction quantity, profit margin per transaction quantity, and joint purchase offer restriction period, to the joint purchase system through the network connection. After that, the sales client 110 refers to the profitability information 300, the payment information 310, the delivery information 315, and the event information 320 in the comprehensive information DB 220 of FIG. By inputting a condition of a joint purchase event to be provided to the client 100 to the joint purchase system, it serves as a subject providing the event.

Here, the product information may include at least one or more of the name of the product to be purchased jointly, the quantity of the joint purchase transaction, the profit margin per unit of the joint purchase, the limited period of the joint purchase offer, the proposed price of the joint purchase transaction, the joint purchase event operation The process of the system 105 receiving and processing the condition of the event from the sales client 110 will be described with reference to FIGS. 4, 5, 6, and 7 shown below.

In addition, all the above-mentioned information is basically provided to the purchase client 100 or the sales client 110 who requested the information through a process of creation and update in the main server in the joint purchase system. According to the needs of the progress, it can be provided to the purchasing client 100 or the selling client 110 in the joint purchase event system.

The joint purchase event management system 105 receives and processes the purchaser information of the purchase client 100, the seller information of the sales client 110, and product information, and processes the comprehensive information DB 220 and the product information DB 225. , The buyer DB 230, the seller DB 235, and the transaction information DB 240, respectively, and the purchase client 100 or the sales client 110 request information generated or updated in the main server 215. If not provided or otherwise requested, the purchase client 100 and the sales client 110 related to the joint purchase or joint purchase event proceedings related information, that is, updated profitability information 300, payment information 310, It is characterized in that the delivery information 315, event information 320 and the like.

In addition, the joint purchase event management system 105 refers to the respective information stored in the product information DB 225, the buyer DB 230, the seller DB 235, the transaction information DB 240 in Figure 3 shown below In providing the event information 320 in the comprehensive information DB 220 generated by the above, the event information (priorly to the purchase client 100 participating in the joint purchase after receiving the approval of the sales client 110 who is the organizer of the event) 320).

Here, the situation of the joint purchase, event participation and lottery method, event winners and dropouts, etc. applied to the purchase client 100 participating in the event by the joint purchase event operation system 105 are shown in FIG. 13. In the event that the event logic processing unit 1305 located in the main server 215 of the joint purchase event management system 105 is processed according to the criteria presented, detailed processing methods are shown in Figures 13 and 14 below. This will be described in detail with reference to FIG. 15.

2 is a block diagram illustrating in detail the interior of the joint purchase event operating system 105.

The interior of the joint purchase event management system 105, as shown in Figure 2, the payment server 200, delivery server 205, event server 210, main server 215, comprehensive information DB 230 , The product information DB, the buyer DB 230, the seller DB 235, the transaction information DB 240 may be made.

The payment server 200 receives payment information about a product that a purchase client 100 purchases from a network, and transmits the payment information generated or updated through the internal processing of the payment server 200 to the comprehensive information DB 220. When the purchase client 100 requests payment confirmation information, the purchase client 100 extracts and provides payment confirmation information only by requesting payment information corresponding to the purchase client 100. More specifically, the purchase client 100 transmits the payment confirmation information. In the joint purchase system 105 to provide the desired product information and joint purchase information, the payment information for the payment method, payment time, payment progress method, etc. of the joint purchase is generated or processed internally in the payment server 200 or By updating, the main server 215 references the product information DB 225, the buyer DB 230, the seller DB 235, and the transaction information DB 240. It serves as a basis for transaction information that is referred to together when presenting the information related to the process of the joint purchase and joint purchase event, that is, the joint purchase condition information, such as recruitment requirements of the joint purchase, to the purchase client 100 in detail. .

The delivery server 205 is a sales client 110 confirming the payment information related to the joint purchase order from the network, the delivery information of the product paid to the purchase client 100, that is, delivery preparation, delivery progress, delivery completion, etc. As a part for providing information related to the information, more specifically, when the purchase client 100 requests the joint purchase to the joint purchase event management system 105, the delivery server 205 from the buyer DB 230 After referring to the information of the delivery address, contact information, and the like, it is generated or updated with the delivery information 315 shown in FIG. 3 and provided to the main server 215 requiring the delivery date, delivery method, delivery processing period, and the like. Or, it serves to extract and provide only the delivery information 315 corresponding to the purchase client 100 or the sales client 110 by request.

In addition, according to an embodiment of the present invention, the delivery server 205 refers to the type of spot desired by the purchase client 100 included in the pool purchase event winner, in the transaction information of the main server 215, It may serve to deliver to the purchase client 100 in the form of the spot.

When the purchase client 100 and the sales client 110 request the joint purchase event information 320, the event server 210 includes the event information 320 in the comprehensive information DB 220 shown in FIG. Extract and provide.

In addition, when there is event information 320 generated or updated from the main server 215, the event server 210 generates notification information on the process and result of the joint purchase event in the form of a message to the sales client. Priority is delivered to 110 and the purchase client 100 is provided with limited information provided by the sales client 110.

More specifically, the event server 210 may include information about event winners and dropouts generated by the event logic processor 1305 and the information processor 1310 in the main server 215 shown in FIG. 13 below. After receiving the event information 320, such as the spot payment level to deliver to the sales client 110, and receives the authentication information provided by the sales client serves to provide only the information for each purchase client (100).

In addition, according to an embodiment of the present invention, in the event server 210 pays the spot to the co-purchase event winner, the form of the spot provided by the purchase client 100 is cash, points, miles, gift certificates. And a gift certificate including an exchange voucher and a joint purchase transaction product as a spot in the form of a donation in the real name of the purchase client 100, and confirm the input information on the spot type selected by the purchase client 100. After the transfer to the main server 215, the event server 210 may provide a form of a spot desired by the purchase client 100 by approval of the main server confirming the approval information of the sales client 110.

The main server 215 refers to the comprehensive information DB 220, the product information DB 225, the buyer DB 230, the seller DB 235, the transaction information DB 240, the joint purchase transaction and joint purchase event Collect the information for the processing process of each processing unit shown in Figure 14 shown below to process the various information for the joint purchase transaction and joint purchase event participated in the sales client 110 and the purchase client 100 Next, it acts as a subject for a series of processes to distinguish the information to be delivered to each transmitter.

For reference, the above-mentioned information for the joint purchase transaction and the joint purchase event may include transaction information, buyer information, seller information, product information, profitability information, code information, payment information, shipping information, event information, and the main information. The information processed and processed by the server 215 to be generated or updated includes information such as transaction information, buyer information, product information, seller information, profitability information, event information, and the like.

More specifically, the main server 215 is a profitability information table of the applied profit rate for inputting the profitability information that can be formed by the sales client 110 through the network as shown in Figure 4 shown in an embodiment of the present invention Present it to the sales client 110 by processing it as a user screen including the network, and the sales client according to the participation level of the purchase client network information about the event detailed settings such as the joint purchase sales amount, event recruitment unit, event recruitment period If the input via the main server 215, the joint client and joint purchase event proceeds according to the information, that is, the condition entered by the sales client.

In addition, the main server 215 provides the event information to the purchasing client 100 by the approval of the sales client, and then receives the request for participation of the purchasing client 100, and the event logic shown in FIG. Event information including information on a joint purchase event rule that can provide a benefit to the sales client 110 through the processor 1305 and the information processor 1310 and information on how to execute the joint purchase event and its progress state. The event information 320 is provided to the sales client 110 and is generated or updated in the main server 215 and stored in the comprehensive information DB 220 according to an event progress. ) Requests the event server 210 and provides the purchase client 100 separately in the form of winner and dropout information.

Here, a process of processing information generated from the main server 215, that is, transaction information, buyer information, seller information, product information, profitability information, code information, payment information, delivery information, and event information, is shown in the drawings below. 13 and 14 will be described in detail.

The comprehensive information DB 230 is operated in conjunction with the seller DB 235, the product information DB 225, the buyer DB 230, the transaction information DB 240 by the main server 215 And store profitability information 300, transaction code information 305, delivery information 315, payment information 310, and event information 320 generated and updated through the main server 215, and the purchase client. When the specific information is requested from the 100 and the sales client 110, the main server 215 serves as a main storage medium for extracting the information.

Here, the profitability information 300, the transaction code information 305, the delivery information 315, the payment information 310, and the event information 320 stored in the comprehensive information DB 230 are shown in FIG. I'll explain in detail.

The product information DB 225 is a medium for storing information on the joint purchase transaction product provided by the sales client 110. More specifically, the product information DB 225 includes an owner, a product ID, a product name, and inventory for each product traded in the joint purchase. A product information table having a form as shown in FIG. 9 shown below for configuring information such as information is stored.

In addition, the product information DB 225 may provide the product ID, which is the basic information for generating the transaction information processed in the main server 215, and the stock status information for comparing the transaction volume of the day with respect to the total inventory. Stores product information generated or updated in the main server 215 at the request of the sales client 110.

The seller DB 235 is a medium for storing seller information of the sales client 110 provided by the sales client 110 in a table having a format as shown in FIG. The main server 215 stores information, and when the specific information is requested, serves as a storage medium for extracting the information.

According to one embodiment of the present invention, the seller ID stored in the seller DB 235 is identification information of the corresponding sales client 110 corresponding to the purchase client 100 in the main server 215 in the product information and transaction information. In the process of selectively extracting and referring to the main server 215 or generating and updating the delivery information 315, the payment information 310, and the profitability information 300 when the reference as a reference is required, the main server ( 215) Fast and effective information processing is possible by extracting and referring to the seller DB 235.

The buyer DB 230 is a storage medium for storing personal information of the purchase client 100 delivered by the purchase client 100, and more specifically, a buyer ID, a delivery address, and a point stored in the buyer DB 230. The buyer information such as information is used as reference information for processing the joint purchase transaction and the joint purchase event related information generated and processed by the main server 215.

Here, the information used by the main server 215 with reference to the buyer DB 230 includes transaction information, buyer information, seller information, product information, profitability information, and code information generated and updated directly by the main server 215. , Payment information, shipping information, event information associated with the buyer ID, name, shipping address, contact number, account number, can be cumulative points.

The transaction information DB 240 stores a list of transactions occurring between the purchase client 100 and the sales client 110 and information on transaction progress in a table having a format as shown in FIG. 12, and the main When the server 215 needs the transaction related information, the storage medium may extract and refer to the corresponding information.

In addition, the transaction information DB 240 stores the transaction information generated and updated for the joint purchase transaction, and then, through the processing of the main server 215, if necessary, the sales client 110 and the purchase client 100 It can be provided to).

3 is a simple block diagram illustrating in detail the interior of the comprehensive information DB 230.

The comprehensive information DB 220 shown in FIG. 3 is composed of profitability information 300, transaction code information 305, payment information 310, delivery information 315, and event information 320. Each of the information generated and updated by the main server 215 is stored, and when the joint purchase and joint purchase event occurs, the main server 215 serves as a storage medium for extracting and referring to necessary information.

The profitability information 300 receives profit rate information provided by the sales client 110 as product information, and then the main server 215 processes the information in the information processing unit 1310 of FIG. It is information including the information on the net profit change of the sales cost of the sales client 110 according to the applied profit rate of the product to be processed and traded in the joint purchase in the same form as the user screen of Figure 4 shown below.

More specifically, the sales client 110 refers to the profitability information 300 to sell the cost of the joint purchase product, the joint purchase recruitment period of the rational joint purchase product that can provide the spot return event while the sales client 110 maintains the lowest profit. And reference information in the designation of the event winner's refund coverage, the establishment of an openable event group, and the time limit, which will be provided to the purchasing client 100 participating in the joint purchase after the joint purchase transaction is ended. Use for

In addition, the main server 215 provides the sales client 110 with the minimum number of buyers for holding an event, checks the approval information of the sales client, and then requests the participation in the joint purchase. By determining the number of to determine whether or not to provide a joint purchase event to the purchase client (100).

According to an embodiment of the present invention, if the main server 215 has a profit rate of 10%, the joint purchase transaction of the product is 100% of the purchase price to one person when at least 11 or more purchase clients 100 participate in the joint purchase. Providing that it is possible to pay in-kind corresponding to the sales client 110 through the profitability information, and confirming the approval information of the sales client that confirmed this the main server 215 through the purchase client participating in the joint purchase transaction After confirming that the number of (100) is 11 or more, the internal processing proceeds to the joint purchase transaction and the joint purchase event.

The transaction code information 305 converts the transaction state information necessary for the co-purchase transaction and the co-purchase event in the main server 215 into a code format. It is shown separately.

More specifically, as shown in FIG. 8 shown below according to an embodiment of the present invention, in the transaction code information 305, each of the eight items set to represent the status information, the transaction status, payment status, sending process It is defined as cash return, return process, spot return method, payment method, cash return level, and each item is applied to the processing of the transaction information by combining the states of preparation, in progress, and completion according to the state.

The payment information 310 refers to information related to payment processed by the payment server 200 in accordance with the joint purchase transaction progress, more specifically divided into two stages of deposit preparation, deposit completion is stored in the form of payment code, When the request of the main server 215 occurs, the stored payment code refers to the payment code corresponding to the code information of the comprehensive information DB 230 and provides the corresponding information.

The delivery information 315 refers to information related to the delivery progress that is processed by the delivery server 205 according to the joint purchase transaction progress, more specifically, the delivery information 315 is ready for shipment, shipment in progress, completion of the shipment, It is stored in the form of a shipping code divided into eight stages of return preparation, return in progress, and completion of return, and when the request of the main server 215 occurs, the stored delivery code corresponds to the code information of the comprehensive information DB 230. The code is read by the main server 215 and read by the code processor 1445 of FIG. 14 to be converted into a language format that can be understood by the purchase client 100 and the sales client 110. The delivery information 315 will be provided.

The event information 320 may provide event setting information input by the sales client 110 to the main server 215 to provide an event to the purchasing client 100 participating in the joint purchase transaction after the joint purchase transaction is ended. It is generated by receiving information and consists of information on the types of events that can participate and event participation conditions.

4 shows a simple example of a virtual profitability information table for a joint purchase transaction.

4 shows the information on the applied profit rate, the selling cost, the joint purchase offer period, and the joint purchase quantity for the product to be sold through the joint purchase by the sales client 110 accessing the joint purchase event operation system 105. When inputted, the main server 215 processes the presented information and then generates the generated profitability information 300 according to an embodiment of the present invention. In detail, FIG. An example of when information processed by the profitability information processor 1480 in the information processor 1310 of FIG. 14 is implemented on a user screen (UI) is shown. The profitability information processor 1480 ) Is the transaction information, buyer information, seller information, product information extracted with reference to the comprehensive information DB (220), product information DB (225), buyer DB (230), seller DB (235), transaction information DB (240) , The profitability information 300 is expressed as a user screen having a format as shown in FIG. 4 by combining information such as profitability information, code information, payment information, delivery information, and event information.

Referring to FIG. 4 according to an embodiment of the present invention, a product having a product ID of P090745 is a product of the sales client 110 having the ID SC020667 by reference to the product information DB 225, and the purchase. If the applied profit rate input by the client 100 is set to 12%, the co-purchase recruitment unit is 10 persons, and the co-purchase quantity is set to 50, if 50 sales are generated, the distribution information processing unit 1310 sells the unit at 918,400 won per unit. It will be seen that the product is expected to generate a total sales of 45,920,000 won, and the operating profit is 4,920,000 won from this information, thereby providing profitable information 300 to the sales client 110.

5 illustrates an example of a user screen provided by the main server 215 to the sales client 110 to set an event.

FIG. 5 illustrates a virtual implementation of a process in which the sales client 110 accesses the joint purchase event operation system 105 and inputs related information to set up event processing according to a joint purchase. The main server 215 refers to the product ID, the applied profit rate input by the sales client 110 through a user screen having a format similar to that of FIG. Winners will receive input and set the payment method in kind according to the event winning.

According to an embodiment of the present invention, if the sales client 110 wants to set only the co-purchase event winners without setting a separate co-purchase event recruiting unit, the purchase client 100 who participated in the co-purchase transaction If the sales client 110 sets the number of the event winners to 5 by referring to the number of the purchasing clients 100 participating in the joint purchase when the total number is 55, the joint purchase event operation system 105 is configured to perform the joint purchase. Among the 55 clients who participated in the purchase 100, 5 winners will be drawn.

According to another embodiment of the present invention, when the sales client 110 wants to set up the co-purchase event recruiting unit and the co-purchase event winners together, the total number of the purchase clients 100 participating in the co-purchase transaction is 55 When the sales client 110 sets the event recruiting unit to 11 persons and the number of winners of each event by referring to the number of the purchasing clients 100 participating in the joint purchase when the number of persons, the joint purchase event operating system 105 ) May divide the 55 purchase clients 100 participating in the joint purchase into five groups through an internal process, and draw one winner for each group.

According to another embodiment of the present invention, when the sales client 110 wants to set up the co-purchase event recruiting unit and the co-purchase event winners together, the total number of the purchase clients 100 participating in the co-purchase transaction When the sales client 110 sets the event recruitment unit to 11 people and the number of winners of each event to 60, the co-purchase event operating system 105 divides 55 people into 5 groups to participate in the event. In addition, the remaining five purchase clients who did not participate in the event are provided with a compensation service through an internal process of the main server 215.

For reference, the process and type of the reward service provided to the purchase client 100 that the main server 215 does not participate in the event will be described in detail with reference to FIG. 7.

In addition, according to an embodiment of the present invention, when the sales client 110 sets the spot payment method for the event winner as the differential payment, the user screen for the spot payment differential setting in the joint purchase event operation system 105 is recalled. When presented to the sales client 110, the joint purchase event operating system 105 processes the input information regarding the spot payment differential setting entered through the user screen.

For reference, the user screen for the spot payment differential setting will be described in detail with reference to FIG.

6 illustrates an example of a simple user screen provided by the main server 215 to the sales client 110 to set up a payment in kind.

More specifically, FIG. 6 shows that the sales client 110 sets the event winners to a number of persons instead of one, and makes the differential payment of the spot according to the winning rank of the event winners. If you want to specify directly to the implementation of the user screen provided by the main server (215).

According to an embodiment of the present invention, when the sales client 100 sets the winning number to two, and sets the spot payment differential setting for the winning number to 100% for the first place and 50% for the second place, The joint purchase event management system 105 is the purchase client 100 participated in the joint purchase event, the purchase client 100 of the two winning through the event processing process of the main server 215 according to the selection order 1 In return, the spot corresponding to 100% of the purchase price of the joint purchase goods and the spot corresponding to 50% of the purchase price to the second place are returned in the form of the spot desired by the purchasing client 100.

According to another embodiment of the present invention, the sales client 100 sets the number of winners to five, and sets the spot payment differential for the number of winners to 100% for first place, 80% for second place, to third place. When set to 60%, 40% to the fourth place, 20% to the fifth place, the joint purchase event system 105 performs the event processing process of the main server 215 among the purchase client 100 participating in the joint purchase event. According to the selection order, the five winning clients 100 won the spot corresponding to 100% of the purchase price of the joint purchase product to the first place, the spot corresponding to 80% of the purchase price to the second place, and the purchase price to the third place. A spot corresponding to 60% of the spot, a spot corresponding to 40% of the purchase price to the fourth place, and a spot corresponding to 20% of the purchase price to the fifth place are returned in the form of the spot desired by the purchase client.

For reference, according to an exemplary embodiment of the present invention, when the sales client 110 sets only the event winners without setting an event recruiting unit, the main server 215 draws an event lottery for all the persons who participated in the joint purchase. By doing so, the winning client set by the sales client 110 may be selected.

In addition, according to another embodiment of the present invention, when the sales client 110 sets the event recruiting unit and the event winners, the main server 215 recruits events among the purchase clients 100 participating in the joint purchase. First, an event participation group that satisfies a unit is generated first, and when the sales client 110 approves, a joint purchase event is performed for each recruitment unit, and the purchase client who did not participate in the event due to lack of event recruitment unit ( 100 receives a compensation service through an internal process of the main server 215.

For reference, the process and type of the reward service provided to the purchase client 100 that the main server 215 does not participate in the event will be described in detail with reference to FIG. 7.

7 is a simple flowchart of the process of joint purchase event.

7 is a diagram illustrating an event progress process after the purchase client 100 participates in an event hosted by the sales client 110 and until the event ends, and the sales client 110 wins the joint purchase event. In addition, when the event recruitment unit is set together, the logical solution process for solving the case where the number of the purchase client 100 to participate in the joint purchase event is not divided into the event recruitment unit is shown.

More specifically, the process of completing the event in which the purchasing client 100 participated in the joint purchase is briefly described, the purchase client 100 requests the participation in the joint purchase (700), and after the joint purchase, the main The server 215 checks the total number of the purchase client 100 requesting to participate in the joint purchase event (705), generates and provides transaction information to the sales client 110, and then the sales client 110 After checking the set co-purchase event recruitment unit (710), the purchase client 100 requesting to participate in the event determines whether it is a multiple of the event recruitment unit (715) and if the event corresponds to a multiple of the event recruitment unit After opening (760), the purchase client (100) is grouped by recruitment unit to participate in the event (765), and the internal processing of the main server (215) is performed. The winners will be drawn and announced (770) to complete the series.

According to an exemplary embodiment of the present invention, when 100 of 200 purchase clients 100 participating in a joint purchase request to participate in the event, the main server 215 refers to an event recruiting unit. After confirming that the event recruitment unit set by the sales client 110 is 10, the 100 purchasing clients 100 who have requested to participate in the event are divided into 10 groups, and then events for each of the 10 groups When the purchase client 100 participates in the opened event, the main server 215 draws and announces an event winner to the purchase client 100 participating in the event to complete the event. .

If the purchase client 100 requesting to participate in the joint purchase event falls short of or exceeds the multiple of the event recruiting unit set by the sales client 110, the main server 215 fails to jointly purchase the sales client. Alternatively, the transaction information about the excess is generated and transmitted to the sales client 110 (720), and the joint purchase transaction of the purchase client 100 requesting to participate in the joint purchase event by confirming the approval of the sales client 110. Allow the participation of the event to the purchase client 100 that satisfies the recruitment unit on a first-come, first-served basis by using the ranking (725), and then provide the waiting guide information for the reward service to the purchase client 100 who did not participate in the event. 730.

According to an embodiment of the present invention, if a specific case is presented, 115 purchase clients requesting to participate in a joint purchase event request to participate in a joint purchase event, and the main server 215 refers to the event recruiting unit to sell the sale. After confirming that the event recruitment unit set by the client 110 is 20, the main server 215 generates and transmits transaction information for 15 persons lacking in the event recruitment unit to the sales client and sends the transaction information to the sales client 110. Event of up to 100 purchase clients 100 satisfying the recruitment unit on a first-come, first-served basis by utilizing the joint purchase transaction ranking of the purchase client 100 requesting to participate in the joint purchase event by confirming the approval of the sales client 110. Allow 15 participants to attend the event because they were unable to fill the event recruitment unit The server 215 provides the air guide service in a service compensation processed internally.

In addition, the main server 215 provides the purchase client 100 who did not participate in the event as a reward service, the opportunity to earn points that can have priority in participating in the next event or to participate in other waiting groups, If the purchase client 100 who has not participated in the event wishes to earn points, the main server 215 accumulates points in the purchaser information of the purchase client who wishes to earn points, and requests for participation in the next event rather than the joint purchase transaction order. Priority is applied (775).

If the purchasing client 100 who has not participated in the joint purchase event wishes to join another waiting group, the main server 215 may not be able to meet the recruitment unit and remaining waiting time information for participating in the waiting group for participating in the event. Providing condition information, such as point deduction that may occur, to the purchasing client 100 (740), placing the purchasing client 100 in another waiting group currently waiting, and guide service for the recruitment of the waiting group Determine (745) whether the recruitment capacity of the event recruitment capacity (750), and if the event recruitment capacity is filled within the waiting time (760) by opening an event (760) the purchasing client 100 of the waiting group to the event progress group Renewal proceeds with the event, but if the event recruitment capacity is not filled, it is determined whether the waiting time is reached (755) When the waiting time is reached, the main server 215 finishes the series of processes by subtracting the purchase client's points and excluding the participation point (780).

For reference, embodiments of the present invention may be presented in various ways, but in general, the main server 215 joins another waiting group to fill an event recruitment capacity within a limited time period, and then purchases that want to participate in the event. When the client 100 requests a participation request to the joint purchase event operation system 105, the joint purchase event operation system 105 of the joint purchase event operation system 105 sends a waiting group to the purchase client 100. When a certain amount of points are deducted according to the participation and the event service is completed at the same time as the event lottery is completed, it is preferable to deduct the points of the purchase client 100 who participated in the event regardless of the event result.

8 illustrates transaction code information 305 used to generate and update transaction information in the main server 215 of the joint purchase event operation system 105 as a transaction code table according to an embodiment of the present invention. will be.

More specifically, the transaction code used in the joint purchase event management system 105 includes eight codes for each of transaction status, payment status, shipping process, cash return, return process, spot return method, payment method, and cash return level. It is applied to transaction information in combination with numbers that are appropriate for the state.

According to an embodiment of the present invention, in the transaction information creation, when the transaction content corresponds to the payment and the payment processing is in an unopened state, the main server 215 sets the transaction status to BC1 and the payment status to MR1. Display the transaction information and generate payment information including payment completion information according to the joint purchase process in the payment server 200, and when the payment information is received from the main server 215, the main server 215 updates the transaction code of the existing transaction information by updating the transaction code to MR2.

According to another embodiment of the present invention, in the case of the purchase client 100 winning the event at which the cash return level is 100%, the main server 215 records the status of the transaction information as MBL1 or the sales client 110. Sets the cash return level applied to the event to 80%, the main server 215 records the state of the transaction information in MBL2 so that the transaction information used and processed in the event information 320 can be recorded using only a simple transaction code record. You can finish.

9 illustrates an example of a product information table 900 stored in the product information DB 225 by one embodiment of the joint purchase event operating system 105.

According to an embodiment of the present invention, the product information table 900 may be configured to include the contents of the product ID, product name, product total inventory, owner ID, etc., as shown in FIG. The ID refers to the seller ID of the seller information table 1100 illustrated below, that is, information corresponding to the seller ID.

In addition, according to an embodiment of the present invention, when a joint purchase transaction occurs or the main server 215 receives a product search request of the sales client 110, the main server 215 is the product information DB ( Through the product information table 900 stored in 225, the sales client 110 may provide the sales client 110 with a result of matching or approximating the product information requested by the sales client 110 in association with the owner ID.

Here, the product information table 900 implements an embodiment of a table of product information generated in the main server 215 of the joint purchase event management system 105, the presented product information table 900 It does not limit the format.

FIG. 10 illustrates, as an example, a buyer information table 1000 stored in the buyer DB 230 by one embodiment of the joint purchase event operating system 105.

According to an embodiment of the present invention, the buyer information table 1000 is generated in the main server 215 including contents of a buyer's ID, name, address, origin, contact, bank account number, point, etc. Stored in the buyer DB 230, the main server 215 can be referenced to generate the transaction information, payment information, shipping information, event information necessary for the joint purchase transaction and joint purchase event progress.

11 illustrates an example of a seller information table 1100 stored in the seller DB 235 by one embodiment of the joint purchase event operating system 105.

According to an embodiment of the present invention, the seller information table 1100 is generated in the main server 215 including contents of a seller ID, a name, an address, a shipping address, a contact number, a bank account number, and the like, and then the seller. Stored in the DB 235, the main server 215 may refer to the transaction information, payment information, delivery information, event information necessary for the joint purchase transaction and the joint purchase event.

FIG. 12 illustrates, by way of example, a transaction information table 1200 stored in the transaction information DB 240 by one embodiment of the joint purchase event operation system 105.

According to an embodiment of the present invention, the transaction information table 1200, the main server 215 is a transaction information ID, product ID, transaction details, transaction means, transaction amount, transaction quantity, transaction status, buyer ID, etc. After generating, including the contents, it is stored in the transaction information DB (240).

More specifically, the transaction information table 1200 is the main server 215, the respective information stored in the product information DB 225, buyer DB 230, seller DB 235, transaction information DB 240 The main server 215 is stored in the transaction information DB 240 when the main server 215 receives a request for information from the sales client 110 and the purchase client 100. Information corresponding to the request is provided with reference to the transaction information table 1200, and the main server 215 may generate, update, and refer to the reference information for the joint purchase transaction and the joint purchase event.

FIG. 13 is a simple block diagram illustrating the inside of the main server 215 in the collective purchase event operating system 105. As shown in FIG.

As shown in FIG. 13, the main server 215 is divided into an information collecting unit 1300, an event logic processing unit 1305, an information processing unit 1310, and an information transmitting unit 1315. Each of the information stored in the comprehensive information DB 230, the buyer DB 230, the seller DB 235, the product information DB 225, the transaction information DB 240 is the information collection unit 1300 When the extracted information is transmitted to the information processor 1310 and then updated to match the progress of the co-purchase transaction or when a new co-purchase transaction occurs, the information is transmitted to the information transmitter 1315 through an operation and a process of generating new information. The information transmitter 1315 separates each piece of information processed by the information processor 1310 into the comprehensive information DB 230, the buyer DB 230, the seller DB 235, and the product information DB. 225, to the transaction information DB (240) It serves up.

According to an embodiment of the present invention, the information collecting unit 1300 extracts the buyer information after the joint purchase transaction (100) is completed for the purchase client participating in the joint purchase and transmits the buyer information to the information processing unit 1310, and the information. The processing unit 1305 applies the winning method according to the event rule of the event logic processing unit to the purchase client 100 participating in the event in cooperation with the event logic processing unit 1305, and then provides information on an event winner and a dropout. After delivering the event information to the information transfer unit 1315, the information transfer unit 1315 transfers the information processed by the information processor 1310 to the comprehensive information DB 230, the buyer DB 230, and the information. Seller DB 235, the product information DB 225, the transaction information DB 240 is delivered to and stored.

Here, the internal structure and role of each unit for the information collecting unit 1300, the information processing unit 1310, the information processing unit 1315, and the event logic processing unit 1305 are described with reference to FIG. 14. This will be described in detail with reference to FIG. 15.

14 is a block diagram schematically illustrating an internal structure of the information collecting unit 1300, the information processing unit 1310, and the information processing unit 1315.

As shown in FIG. 14, the information collecting unit 1300 includes a transaction information collecting unit 1400, a buyer information collecting unit 1405, a seller information collecting unit 1410, a product information collecting unit 1415, and a profitability. The information collecting unit 1420, code information collecting unit 1425, payment information collecting unit 1430, shipping information collecting unit 1435, event information collecting unit 1440, if the joint purchase transaction occurs, the information collection The unit 1300 may include the comprehensive information DB 220 for transaction information, buyer information, seller information, product information, profitability information, code information, payment information, delivery information, and event information corresponding to each collection unit. The most recent information stored in the product information DB 225, the buyer DB 230, the seller DB 235, and the transaction information DB 240 is extracted and then sent to the information processor 1310.

For reference, the roles and functions of transaction information, buyer information, seller information, product information, profitability information, code information, payment information, shipping information, and event information extracted by the respective collection units may be different from those shown in FIG. Since the same content, the description of the information extracted by each collector will be omitted.

The information processing unit 1310 may include a code processing unit 1445, a distribution information processing unit 1450, a transaction setting processing unit 1455, a transaction information processing unit 1460, and a buyer information processing unit 1465, as shown in FIG. 14 shown below. , A seller information processing unit 1470, a product information processing unit 1475, a profitability information processing unit 1480, and an event information processing unit 1485, wherein the information transmitted through the information collecting unit 1300 is the information processing unit ( The information corresponding to the transaction information, the buyer information, the seller information, the product information, the profitability information, the code information, the payment information, the delivery information, the event information is generated through the respective processing units in 1310), or the joint purchase transaction and the joint As the purchase event progresses, the existing information is updated and transmitted to the information transmitting unit 1315.

The code processor 1445 generates, updates, and processes the main server 215, the comprehensive information DB 220, the product information DB 225, the buyer DB 230, the seller DB 235, and the like. According to an embodiment of the present invention, a variety of codes applied to all information stored in the transaction information DB 240 are converted into information that can be understood by the sales client 110 and the purchasing client 100. When the purchase client 100 completes cash payment and then requests confirmation of payment, the code processor 1445 deposits the code MR2 recorded in the transaction contents and transaction status fields on the transaction information table 1200. Complete, 'AM1 is converted into' cash 'and transmitted to the information transmitter 1315.

The distribution information processing unit 1450 generates and updates a virtual table, and when a request for the transaction information, buyer information, seller information, product information, profitability information, code information, payment information, shipping information, and event information occurs, Where the information is provided directly without going through the process, more specifically, the information is continuously generated and updated in the information processing unit 1310 and stored in the DBs in accordance with the information co-purchase transaction and co-purchase event proceeds. When the request of the main server 215 or the purchase client 110 and the sales client 100 occurs for the information, the comprehensive information DB 220, product information DB 225, buyer DB 230 ), Instead of going through a predetermined processing procedure for extracting and referring to the information stored in the seller DB 235 and the transaction information DB 240, the distribution information processor 1450 is previously generated. W by providing the information corresponding to the request directly from the table of the updated virtual functions to minimize the processing time of the data.

According to an embodiment of the present invention, the virtual table generated by the distribution information processor 1450 may be configured to include a transaction ID, a product ID, a product profit rate, a buyer ID, a transaction state, and transaction details, and joint purchase. When the transaction and the joint purchase event are completed, the virtual table is deleted in the distribution information processing unit 1450 without being stored independently for the efficiency of information storage and processing.

The transaction setting processing unit 1455 processes setting of seller information such as an applied rate of return, a joint purchase period, and a sales quantity, which are input through a user screen provided by the joint purchase event operating system 105 to the sales client 110. And when the user inputs more information than the allowable range for the purchaser information such as the collective purchase quantity and the shipping address, which are input through the user screen provided to the purchase client 100, the joint purchase due to the error by rejecting the input with an error message. It serves to prevent the failure of the event management system 105.

Although embodiments of the present invention can be presented in various ways, the joint purchase event management system 105 does not input a joint purchase transaction amount from the sales client 110 or the joint client for the item for which the purchase client 100 is completed. When applying for a purchase, the transaction setting processing unit 1455 may reject the processing of the input information and present a guide message regarding re-entry of the allowed information together with an error message.

The transaction information processing unit 1460 is configured to process the transaction setting processing unit 1455 and the comprehensive information DB together with information including the applicable profit rate, the joint purchase limit period, and the joint purchase quantity of the sales client 110 set. 220, product information DB 225, buyer DB 230, seller DB 235, transaction ID by extracting information such as product ID, product selling price, and buyer ID stored in transaction information DB 240. It creates and updates a transaction information table including product ID, transaction details, transaction means, transaction quantity, transaction amount, buyer ID, and status information.

In addition, the transaction information processing unit 1460 extracts the latest information of the transaction ID, the product ID, the transaction content, the transaction means, the transaction quantity, the transaction amount, the buyer ID, and the status information requested by each of the processing units, respectively. The transaction information processed by the transaction information processing unit 1460 when there is no request from the processing unit or the purchase client 100 and the sales client 110. Product information DB (225), seller DB (235), buyer DB (230), the transaction information DB (240) to pass the role from time to time.

Various embodiments may exist in the form of information processing of the buyer information processing unit 1465, the seller information processing unit 1470, the product information processing unit 1475, and the profitability information processing unit 1480, according to an embodiment of the present invention. The processing units extract the latest information in the same manner as described in the transaction information processing unit 1460 and transfer the corresponding information to each processing unit, or the processing unit or the purchase client 100 and the sales client 110. If there is no request from the transaction information processing unit 1460 the transaction information processed in the comprehensive information DB (230), product information DB (225), seller DB (235), buyer DB (230), transaction information DB ( It is desirable to go through a predetermined process that is often delivered to 240).

The event information processor 1485 receives the processed information from each of the information processors and generates and updates event information in association with the event logic processor 1305.

According to the embodiment of the present invention, various embodiments may exist, but the event information processor 1485 may include the distribution information processor 14450, the transaction information processor 1460, the buyer information processor 1465, the seller information processor 1470, and the like. A buyer who can or cannot participate in an event by receiving the delivery information from the product information processing unit 1475 and the profitability information processing unit 1480 and the event logic information generated by the event logic processing unit 1305, a buyer group participating in the event, an event Generates event information for providing to the sales client 110 and the purchase client 100 by processing constraints such as an event recruitment period applied to participation, event progress status for each group, and the sales client 110. And request for the event information of the purchase client 100 or the event information in the comprehensive information DB 220. It is preferable to transfer to the information transmission unit 1315 to store the.

In addition, according to an embodiment of the present invention, when the event information processing unit 1485 provides the sales client 110 with an event participation request of the purchase client 100 participating in the joint purchase, the event information processing unit 1485 is After confirming the approval of the sales client 110, the purchase client 100 transmits the approval with the event guide information, and the event information processor 1485 refers to the event logic information of the event logic processor 1305. The event information is generated or updated by processing event related information changed as the joint purchase event progresses, for example, new group creation, addition, dropout, and winner and dropout information of the event end.

For reference, the event logic information generated by the event logic processor 1305 is generated when one joint purchase event occurs, and when the joint purchase event ends, the event information processing unit ( 1485) transmits the event information to the information transmitter 1315 and then deletes the temporary information.

In addition, according to an embodiment of the present invention, the guide information related to the event progress processed by the event information processing unit 1485 is received from the event server 210 via the information transmitting unit 1315, the pop-up of a wired communication network It may be provided to the purchase client 100 in real time via a window or a wireless communication text message.

The information transmitter 1315 is a transaction information transmitter 1490, a buyer information transmitter 1495, a product information transmitter 14100, a seller information transmitter 14105, and profitability information, as shown in FIG. 14. It is composed of a transmission unit 14110, an event information transmission unit 14115, each information transmission unit receives the information processed and generated and updated from the information processing unit 1310 and classified according to the type of information To the purchase client 100 and the sales client 110 requesting a comprehensive information DB 230, product information DB 225, seller DB 235, buyer DB 230, for storage of the information It serves to provide the corresponding information to the transaction information DB (240).

The transaction information transmitter 1490, the buyer information transmitter 1495, the product information transmitter 14100, the seller information transmitter 14105, the profitability information transmitter 14110, and the event information transmitter There may be various embodiments in the information transmission procedure of 14115, but according to the embodiment of the present invention, the information transmitted by the information processor 1310 is classified according to the type of information in the information transmitter 1315. Next, the comprehensive information DB 230, the product information DB 225, the seller DB 235, the buyer DB 230, and the transaction information DB 240 may be delivered first, and the information transmitting unit 1315 may be transmitted. The role and function of transaction information, buyer information, product information, seller information, profitability information, and event information delivered in the above) are the same as those shown in FIG. 3, and thus, description of the information extracted by each collector is omitted. Ha To do that.

The event logic processor 1305 serves to generate event logic information, which is temporary information that the event information processor 1485 refers to in the process of generating the event information 320 for proceeding with a unit of a joint purchase event.

More specifically, when one joint purchase transaction occurs, when the event logic processor 1305 generates event logic information to be applied to the joint purchase event in cooperation with the event information processor 1485, the event information processor 1485. With reference to the event logic information it is possible to provide the event information 320 provided after the joint purchase participation to the purchase client 100 participating in the joint purchase.

In addition, according to an embodiment of the present invention, when an event participation request of the purchase client 100 occurs, the event information processor 1485 receives the approval of the sales client 110 to receive the purchase client 100. In this case, the event logic processor 1305 generates event logic information to be applied to the creation of a new group for the purchase client 100 and the arrangement into the organized group according to the entire event rule, and the event information processor Performs a joint purchase event with reference to the event logic information.

For reference, the event logic information generated by the event logic processor 1305 may process a spot return rule, a competition rule between the purchase client 100, and a lottery rule that the event information 320 applies to an event winner. The logical processing of all the variable situations occurring during the joint purchase event serves as an information processing criterion until the end of a unit of the joint purchase event.

Here, according to an embodiment of the present invention, the event server 210 provides the spot return event information provided by the event information processing unit 1485 to the purchase client 100 participating in the joint purchase transaction as a joint purchase participation. In this case, the event logic information of the event logic processing unit 1305 includes the differential execution processing logic to be applied to the co-purchase event winner using the information in FIG. The event information processor 1485 is transmitted to the event information processor 1485 to process the spot information to be paid as a result of the differential execution of the event winner and update the event information 320.

For reference, an information processing procedure processed in the event logic processor 1305 will be described in detail with reference to FIG. 15 shown below.

Fig. 15 is a block diagram briefly showing the logic configuration of the event logic processing unit 1305. Figs.

According to an embodiment of the present invention, the inside of the event logic processing unit is largely represented as shown in FIG. 15, the event information receiving unit 1500, the new group processing unit 1505, the organized group processing unit 1510, the spot return It is divided into seven parts: a reference processor 1515, a special rule reference processor 1520, a lottery rule reference processor 1525, and an event logic information transmitter 1530, and the event logic processor 1305 is the information collector. With reference to the event information 320 delivered to the 1300, the event logic information corresponding to the event progress is generated while processing through the seven processing units, and then transmitted to the event information processing unit 1485 to the event. Generate and update the event information 320 that can be applied to the participating purchase client (100).

The event information receiver 1500 receives the latest event information about a unit of the joint purchase event, and the received event information 320 refers to the event logic information to be generated by the event logic processor 1305. It is information.

In addition, according to an embodiment of the present invention, the information delivered through the event information receiver 1500 may include seller information including the approval of the sales client 110 in addition to the event information 320.

The new group processing unit 1505 is a processing unit for creating and managing a new group to which the purchasing client 100 participating in the event belongs. According to an embodiment of the present invention, a joint purchase event may display characteristics of a joint purchase. Since a spot return event may be provided for each event recruiting unit, the new group processing unit 1505 may check the purchase client 100 participating in the event after confirming the approval information of the sales client 110. It acts as a virtual guide that guides and controls the recruitment of specific units to participate in the event.

According to an embodiment of the present invention, if a simple example of the role of the new group processing unit 1505 is presented, the purchase client 100 participating in the event through the event process described with reference to FIG. ) Provides a co-purchase event for the number of people recruited during the recruitment period to the purchase client 100 of 22 units who have co-purchased a specific product, so that the two winners receive a spot corresponding to 100% of the purchased product. The event sales information of the sales client 110 to return and provide the information, and the 44 sales clients (100) for the formation of the group to support the event new participation group of the desired conditions within the recruitment period (the sales client ( When the sales client 110 approves the request to 110, the new group processing unit 1505 is requested. After confirming the seller information and dividing the 44 purchasing clients 100 into two groups of 22 persons each to create two new groups, 44 purchasing clients 100 who requested to participate in the new group were established in each new group. At the same time, the new group is converted into an event progress group, the updated event information 320 is transmitted to the spot return criterion processor 1515, and the event progress group restricts further participation. Play a role.

According to another embodiment of the present invention,

The organized group processor 1510 presents predetermined event guide information to the purchase client 100 in the same manner as the new group processor 1505, but selects the event waiting due to the over / under of the event recruitment unit. If the purchase client 100 requests to join a specific unit 'waiting group' without forming a group under time constraints without joining the new group for reasons separate from the clients 100, The group processing unit 1510 provides the sales client 110 with the information on the waiting group and the current status information, and then confirms the approval of the sales client 110 to place it in the waiting group where the purchasing client 100 requests to participate. Role.

According to an embodiment of the present invention, a simple example of the role of the organized group processing unit 1510 is presented. For example, the 44 clients who have contacted the event guide information through the same procedure as that presented in the new group processing unit 1505 are provided. 22 of (100) participate in the events presented above, and 11 of the remaining 22 would like to join the sales client 110 in an organized group of other conditions that are not filled in the event recruitment and waiting for the new group. When requested, the organized group processing unit 1510 extracts the information about the purchasing client 100 and the organized group which the purchasing client 100 wants to participate in and provides it to the sales client 110. After confirming the approval information of the sales client 110, the purchase client 100 is placed in a waiting group to request participation Do it.

According to another embodiment of the present invention,

The spot return reference processor 1515 serves to process the standard of 100% or the differential spot payment that is paid to the event winner according to the spot payment differential setting of the sales client 110, so that the purchase client 100 In case of winning the event, the spot return reference processor 1515 may refer to the event information 320 including the event condition set by the sales client 110, and the purchase client 100 who has won the event may have a desired form. Allow you to pay in kind.

According to an embodiment of the present invention, a simple example of the role of the spot return criterion processor 1515 is set. The spot payment differential is set for the 55 purchase clients 100 participating in the event. If you enter 100%, 80%, 60%, 40%, 20% in order from the first place to the fifth place, the event server 210 to the spot level to be paid to the co-purchase event winner to the purchase client 100 Apart from providing information about the spot return processing unit, the purchase client 100 that has won the event by referring to the spot payment differential setting input by the sales client 110 through the user screen of FIG. 6. The sales client 110 serves to pay the spot by applying the same conditions entered into the user screen.

The special rule criterion processor 1520 checks the approval of the sales client 110 and applies a special rule to the new group when a request for applying the special rule of the purchase client 100 occurs when a new group is created. Do it.

According to the exemplary embodiment of the present invention, the purchase client 100 requesting the participation of the event progress group generally limits the participation under the control of the new group processing unit 1505 since the group requesting participation exceeds the recruitment unit. However, when creating a new group, the purchasing client 100 participating in the event group requests a special rule, and the special rule generated by the special rule standard processing unit 1520 by the sales client 110 is approved. In the case of an applied event progressing group, the purchasing client 100 removes one of the purchasing clients 100 participating in the event progressing group filled with the recruitment unit by holding point confrontation with the permission of the special rule criterion processing unit 1520. Participate in a progress group.

In addition, according to an embodiment of the present invention to present a more specific case for the role of the special rule criteria processing unit 1520, the purchase client 100 is the information about the event progress group to which the special rule is applied; After confirming through the event information guide, requesting the participation approval in order to participate in the event progress group, the special rule criterion processor 1520 checks the special rule and allows the purchase client 100 to participate. The purchase client 100 confronts with another purchase client participating in the event progress group by holding points, and the purchase client 100 who has won the confrontation expells the purchase client 100 lost in the confrontation. The purchase class you wish to participate in, along with event progress information, indicating that you can join a later event group. The purchaser information of the client 100 is processed together and included in the event information 320 and provided to the sales client 110.

The lottery rule reference processor 1525 is a processor that sets and manages a rule criteria for lottery winners among the purchase clients 100 participating in an event group. According to an embodiment of the present invention, the lottery rule reference processor 1525 The purchase client 100 itself participates in the event lottery by combining the number directly within the limited number combination, or participates in the event lottery by the randomly combined number. Presented to the client 100, the purchase client 100 is to draw the event winner by the selected lottery method.

In addition, according to an embodiment of the present invention to present a simple example for the lottery rule reference processing unit 1525, the purchase client 100 participating in the event group by selecting a natural number from 0 to 9 of the four digits do not overlap When a natural number combination is created, the lottery processor presents the purchase client 100 through the event server 320 after a predetermined process of selecting a random combination or a random combination lottery, and responding to the lottery. If there are 10 group event participants, the lottery number can be registered through the user screen in 10 different combinations such as 1234, 2519, 6923, 9731, 6718, 2768, 7934, 4619, 3781, 5729. The lottery rule reference processing unit 1525 may refer to the event information 320 including the winning number setting, and the lottery number as shown in the above example. Through the random drawing process is selected events winners and losers.

The event logic information transmitting unit 1530 may include the new group processing unit 1505, the organized group processing unit 1510, the spot return reference processing unit 1515, the special rule reference processing unit 1520, and the lottery rule reference processing unit. The event logic information is transmitted to the event information processor 1485 in order to apply the event processing criteria generated and updated at 1525 in real time according to the event progress.

According to an embodiment of the present invention, the event logic information transmission unit 1530 receives the event logic information generated through each processing unit when a request relating to a unit of event processing from the event information processing unit 1485 occurs. The event logic information transmitted to the information processing unit 1485 serves as a rule for various situations occurring in the course of the event after the event information processing unit 1485 processes, and when the event ends, the event information processing unit (1485) delete.

FIG. 16 is a simplified diagram of a process in which the joint purchase event operation system 105 processes a process of the purchase client 100 accessing the joint purchase event operation system 105 to purchase an item in a joint purchase manner. It is a flow chart.

Referring to FIG. 16, the purchase client 100 accesses the joint purchase event operating system 105 through a network and undergoes a predetermined authentication process (1600). When requesting information retrieval from the joint purchase event operating system 105 through a user screen (1605), the main server 215 of the joint purchase event operating system 105 retrieves a product information DB 225 to purchase a client. In operation 10010, the search result for the product that matches or is close to the requested information may be provided.

The purchase client 100 may provide information about the total quantity of the joint purchase product, the joint purchase recruitment unit that allows the joint purchase, the limit of the period of the joint purchase, and the proposed joint purchase price from the searched result. When the request is made (1615) and informed (1620), and the purchase client 100 selects a desired product to purchase a joint purchase and determines whether to participate in the joint purchase, and requests authentication to the joint purchase event operating system 105 ( 1625), the joint purchase event operation system 105 confirms the joint purchase participation approval of the sales client 110, permits the joint purchase participation of the purchase client 100, and then the sales client 110 In operation 1630, the total purchase of the purchase client 100 is determined.

Subsequently, when the main server 215 confirms the joint purchase price determined by the sales client 110 by reaching the limited period condition of the recruitment of the joint purchase recruitment number and the joint purchase, the joint purchase price is determined. The fixed sales price applied is stored in the product information DB 225 shown in FIG. 2 and then informed to the purchase client 100 (1635), and the silver designated by the payment server 200 is assigned. The payment guide information is transferred to a row account and a payment request is made to transmit the guide information for the purchase client 100 to deposit (1640).

Here, the payment server 200 checks the payment of the joint purchase product of the purchase client from the network, and when the purchase client makes a payment for the joint purchase, payment information 310 to the payment server 200. ) Is stored in the comprehensive information DB 230 shown in FIG. 2, and at the same time, the transaction status information of the transaction information table 1200 shown in FIG. 12 is updated, and then the purchase client 100 is updated. Information about the updated payment confirmation is transmitted (1645).

The delivery information 315 of the product sent by the sales client 110 is generated and updated as the delivery information 315 suitable for the shipment situation through the delivery server 205, and is a text message or the like to the purchase client 100. Providing guide information in the form of (1650), and if the delivery is completed, the delivery server 205 provides the guide information for the completion of the product to the purchase client 100 (1655).

After the purchase client 100 receives the co-purchased goods and confirms the state of the goods, the purchase client 100 determines whether to return the co-purchased goods sent (1660) and the co-purchase event operating system 105. When the request for delivery is made and the co-purchased product is sent, the receipt approval information for the product is transmitted to the co-purchase event operating system 105, and if there is no return request, the process of the co-purchase transaction is completed. (1665).

If the product sent to the purchase client 100 is rejected by the purchase client 100 and returned, the joint purchase event management system 105 processes the product return to the purchase client 100. Providing guide regulation information about (1670), through the main server 215 to update the transaction information for the product return processing and return processing (1675), through the payment server 200 of the purchase client 100 The refund information is transmitted, and the refund confirmation and the refund information of the purchase client 100 are updated (1680) to complete a series of processes.

FIG. 17 is a simple flowchart of a process for generating and completing a joint purchase event by the joint purchase event operation system 105 when the purchase client 100 accesses the joint purchase event operation system 105. It is shown.

When the purchase client 100 accesses the joint purchase event operation system 105, the event information processor 1485 refers to the event logic information of the event logic processor 1305 and participates in the joint purchase transaction. The event information 320 previously provided to the client 100 before participating in the joint purchase is divided into event progress groups, participation conditions for each event group, and participation group information (1700), and then provided to the purchase client 100. Whether to participate in the event (1705), whether to participate in a new group or organized group participation (1710), and in the case of new group participation, whether a rule to be applied to the new group as a general rule or a special rule (1715). Request the input information for the purchase client 100, and receives the input information (1720) from the information collector 1300 The event information processor 1485 and the event logic processor 1305 work together to complete the event formation (1745).

The purchase client 100 that has been approved to participate in the desired event group from the joint purchase event operation system 105 inputs its transaction information ID into the joint purchase event operation system 105 through a network. (1750) joining an event group approved by the joint purchase event management system 105 (1755), and then the event information processing unit 1485 refers to the event logic information generated by the event logic processing unit 1305 and performs an event. The lottery will be conducted (1760).

Here, the purchase client 100 participating in the joint purchase event is the event logic processing unit 1305 and the event information processing unit 1485 through the interlocked process of the event as a result of the progress of the event as a result of the winner and the winners The purchase client 100 guides the purchase client 100 (1765) and checks the information on the winners and dropouts provided as a result of the event (1770) by requesting a refund means input provided by the main server 215 (1770). When each spot return means is selected and input on the network, the main server 215 checks the input information and pays the spot in the selected spot return form (1790). The transaction information and the event information generated and updated by the main server 215 may be included in the comprehensive information DB 220, product information DB 225, buyer DB 230, and the like. Seller DB (235), transaction information DB (240) is stored and a series of processes are completed.

For reference, after the spot return type request 1770 according to another embodiment of the present invention, if the purchase client 100 inputs a desired spot type as a donation, the main server 215 is associated with the event server 210. By processing the donation to another bank account under the real name of the purchase client 100.

FIG. 18 is a simple flowchart of a process in which the joint purchase event operating system 105 processes a process from the sales client 110 to selling the product in a joint purchase manner.

In more detail, after the sales client 110 connects to the joint purchase event operation system 105 to sell the goods in a joint purchase manner, the sales client 110 approves the participation behavior of the purchase client 100 participating in the event, This is a simple flow diagram of the sequence of steps from shipping a purchased product to completing a joint purchase transaction.

Referring to FIG. 18, the sales client 110 accesses the joint purchase event operating system 105 through a network (1800) and checks the transaction information and product information of the product held by the sales client 110. Next (1805), if you enter the stock information for the product that is in high demand of the purchasing client 100 or the product to be registered in the joint purchase transaction, the joint purchase allowance unit, the joint purchase period limit, and the transaction price information to be presented in the joint purchase ( 1810) The main server 215 generates and updates the applied profit rate, the joint purchase allowance unit, the joint purchase offer period, and the event setting information input by the sales client 110 through the process of the main server 215. Store in the DB (1815).

When the purchase client 100 requests the information on the joint purchase product and the event information 320 according to the joint purchase, the main server 215 may store the product information DB (which has already been input by the sales client 110). 225) and the detailed information such as the total quantity of the joint purchase product, the joint purchase recruitment unit, the time limit and the joint purchase price corresponding to the request are provided through the search of the information stored in the comprehensive information DB 220 (1820). When the authentication request information for the purchase client 100 requesting to participate in the joint purchase is transmitted to the sales client 110 and the approval information of the sales client is checked (1825), the main server 215 receives the joint purchase. After confirming the co-purchase unit and the recruitment period for creating a transaction (1830), the co-purchase participation request of the purchase client 100 is finally approved, and then the sales client The co-purchase transaction price, which has been confirmed through the approval of the client 110, is determined to be the final price to be applied by the co-purchase event operation system 105 for a unit of the co-purchase transaction and the co-purchase event, and is confirmed to the buyer client. Inform the price (1835).

In addition, the main server 215 extracts bank account information from the seller information DB and transmits a payment request message for a limited period to the purchase client 100 to the purchase client 100 through the payment server 200. Next, when the payment server 200 checks the payment information of the designated account through the network and transmits it to the main server 215, the purchase client 100 that has confirmed the payment is the sales client 110. After the approval of the delivery server 205 is informed of the goods delivery information (1845) after updating and storing the delivery information according to the delivery progress status and then providing the updated delivery information to the sales client (1850), the delivery When it is completed, the sales client 110 provides the guide information on the completion of the shipment (1855).

In addition, according to an embodiment of the present invention, the main server 215 confirms whether the purchase client 100 returns to the dispatched product (1860), and checks whether the purchase client 100 receives approval for joint purchase. After completing the transaction, the sales client 110 is informed of completion of the transaction (1865).

If the purchase client 100 determines the return in the process of determining whether to return the sent goods (1860), the delivery server 205 provides a return progress status to the sales client 110 to request for approval. In operation 1870, upon confirming the return approval information of the sales client 110, the main server 215 may provide that the renewal and refund execution guide information is provided to the purchase client 100 with respect to the transaction information according to the return approval. After notifying the client 110 (1875), the delivery information about the refund processing state is extracted from the delivery server 205 and provided to the sales client 110 to update the transaction information (1880), and then terminated.

19 is a simple flowchart of the process from when the sales client 110 accesses the joint purchase event operation system 105 to the joint purchase event operation system 105 to generate and complete the joint purchase event. It is shown.

The main server 215 checks the transaction status information for the purchase client 100 in which the joint purchase transaction is completed (1900), and the joint client inputted to the joint purchase transaction system 105 by the sales client 110. Check the spot return level information for each purchase product and the event winner (1905), extract the purchase client 100 ID of the transaction information recorded as the event target in the transaction information DB 240, and then send it to the sales client 110 At the same time, the event information processor 1485 provides the sales client 110 with information about the progress event group, the participation condition for each event group, and the event waiting group.

In addition, when the purchasing client 100 requests the participation in the event of joint purchase event management system 105, the main server 215 purchases the unit or part of the purchasing client 100 who has requested the event participation approval. Information, transaction information, and event information 320 are extracted and provided to the sales client 110, and the event information processor 1485 actually participates in an event rule to be applied to the purchase client 100 who wishes to participate in the event. Providing possible event group information to the sales client 110, the event participation request approval 1910 or participation group selection approval 1915, event rule approval 1920 and the purchase requested by the sales client 110. It is possible to determine the final approval 1945 for event scheduling of the client 100.

When the sales client 110 confirms the event information 320 provided by the main server 215, the main server 215 joins and organizes a new group of the event group requested from the purchase client 100. In response to the approval of the arrangement of the group participation, the new group participation, the general rule or the special rule approved, the sales client 110 transmits a message requesting information approval and completes the event organization (1950). .

Thereafter, the event information processing unit 1485 confirms the joint purchase transaction ID input by the purchase client 100 to participate in the event, approves the participation of the purchase client 100 (1955), and the event lottery. The purchase client 100 registers a lottery number created in a desired manner (1960), and draws an event according to a corresponding lottery method for each event group, and provides the result to the sales client (1965).

Subsequently, when the sales client 110 approves (1970) the result of the processed event after selecting and confirming an event winner and a dropout (1970), the main server 215 returns a spot return means selected by the purchase client 100. The approval request is transmitted to the sales client 110 to confirm the approval (1975). The service according to the spot return information selected by the purchase client 100 is provided through the delivery server 205 and the event according to the joint purchase transaction is provided. This completes the sequence of steps to completion.

Those skilled in the art will understand that the present invention can be implemented in other specific forms without changing the technical spirit or essential features.

It is to be understood that the examples presented above are illustrative and not restrictive.

The scope of the invention is indicated by the following claims rather than the above description, in particular all changes or modifications derived from the meaning and scope of the claims and their equivalents are included in the scope of the invention. Should be interpreted as

In-kind return events provided by implementing the present invention has the effect of greatly increasing the sales growth for the joint shopping method Internet shopping mall.

In the competitive system where existing co-purchased Internet shopping malls do not differentiate price discounts for new shopping malls and compete in bleeding competition, they provide event services differentiated from other Internet shopping malls to sustain consumer sentiment of purchasing clients and co-purchase methods. It is effective to increase sales growth of Internet shopping malls.

In addition, the implementation of the present invention can be expected to activate the healthy consumption.

Although the spot return event similar to the present invention had an adverse effect of causing meandering, it had to be abolished even before most of it was revealed, but the spot return event of the present invention was generated and stored from a system structure that specifies profitability information on the sales client side. And because it is being utilized, it is not possible to exploit the mediocreity by manipulating the event, and it can be expected to activate healthy consumption because the purchasing client who participates in the joint purchase transaction has the expectation in the appropriate compensation line.

Claims (1)

Event related to the sale of the product-an event such as a lottery to return a part of the product sales profit to at least one or more buyers participating in the product purchase-the minimum unit buyer information for holding in association with the product information to a predetermined storage medium Information storage means for storing in; Information checking means for determining whether the event can be held by checking the total number of buyers participating in the product purchase and the minimum number of unit buyers for holding the event stored in the storage medium; And And the event operation means for holding the event for the buyers participating in the product purchase as a result of the determination.

Images