Dinner matching method, dinner matching system, and dinner matching program

Abstract

To provide a dinner matching method, a system and a program for reducing a burden of an organizer of dinner.SOLUTION: A dinner matching method which is executed by a dinner matching system includes: a participant invitation step of inviting participants in dinner on the basis of dinner information registered by an organizer of the dinner; an application receiving step of receiving an application for participation from applicants for the dinner; and a participant receiving step of receiving participants selected by the organizer from among the applicants.SELECTED DRAWING: Figure 8

Description

[Technical field]

[0001] The present invention relates to a dinner party matching method, a dinner party matching system, and a dinner party matching program. [Background technology]

[0002] Popular restaurants that are difficult to make reservations for often have existing customers book their next reservation when they visit, so they often have their reservations booked for many days in advance. When making their next reservation, these existing customers often make reservations for multiple people at once and hold a dinner party by inviting the same number of people. In other words, existing customers of popular restaurants act as organizers of dinner parties at the restaurant.

[0003] A method for supporting an event organizer is known that includes a control method of a server equipped with a memory unit, which includes the steps of: storing schedule data indicating the schedules of each of a plurality of users in the memory unit; accepting settings of a plurality of convening users to be invited to the event and a plurality of candidate dates and times for the event from an organizing terminal of an organizing user among the plurality of users; reading out schedule data for the plurality of candidate dates and times for each of the plurality of convening users from the memory unit; and outputting screen information to the user terminals of the plurality of convening users that displays the plurality of candidate dates and times with a distinction between candidate dates and times with a small number of convening users who have plans and candidate dates and times with a large number of convening users who have plans (Reference 1). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2017-33292 A Summary of the Invention [Problem to be solved by the invention]

[0005] When recruiting participants for a dinner party, the organizer must consider many things, such as the restaurant, menu, price, location, date and time, and human relationships. Also, if someone who had planned to attend cancels at the last minute, the organizer must quickly find new participants, taking these factors into consideration. Furthermore, the organizer must collect the meal fee from the participants and inform the restaurants in advance of the participants' food allergies. All of this work places a heavy burden on the organizer.

[0006] The present invention has been made in consideration of the above problems, and aims to reduce the burden on the organizer of a dinner party. [Means for solving the problem]

[0007] In one embodiment, the dinner party matching method is a dinner party matching method executed by a dinner party matching system, and includes a participant recruiting step of recruiting participants for the dinner party based on dinner party information registered by a dinner party organizer, an application acceptance step of accepting applications to participate in the dinner party from applicants, and a participant acceptance step of accepting a selection of participants from among the applicants. Effect of the Invention

[0008] According to one embodiment, the burden on the organizer of a dinner party can be reduced. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 illustrates an example of the configuration of a dinner party matching system 1000. [Diagram 2] FIG. 2 illustrates an example of a hardware configuration of an information processing device. [Diagram 3] 1 is a diagram illustrating an example of a functional configuration of a dinner party matching device 1. FIG. [Figure 4] FIG. 2 is a diagram showing an example of user information 121. [Diagram 5] FIG. 13 is a diagram showing an example of dinner party information 122. [Figure 6] FIG. 13 is a diagram showing an example of applicant information 123. [Figure 7] FIG. 2 is a diagram illustrating an example of a functional configuration of a user terminal 2. [Figure 8] 13 is a flowchart showing an example of a dinner party registration process. [Figure 9] FIG. 13 is a diagram showing an example of a dinner party registration screen sc1. [Figure 10] 13 is a flowchart illustrating an example of a dinner party invitation process. [Figure 11] FIG. 13 is a diagram showing an example of a dinner party list screen sc2. [Figure 12] FIG. 13 is a diagram showing an example of a dinner party invitation screen sc3. [Figure 13] FIG. 13 is a diagram showing an example of an applicant list screen sc4. [Figure 14] FIG. 13 is a diagram showing an example of a participant list screen sc5. [Figure 15] 13 is a flowchart showing an example of a dinner party cancellation process. [Figure 16] FIG. 13 is a diagram showing an example of a dinner party invitation screen sc6. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, each embodiment of the present invention will be described with reference to the accompanying drawings. In the description of the specification and drawings of each embodiment, components having substantially the same functional configuration are designated by the same reference numerals, and redundant description will be omitted.

[0011] <Configuration of the dining party matching system> First, an overview of the dinner party matching system 1000 according to this embodiment will be described. The dinner party matching system 1000 is an information processing system that provides a dinner party matching service that matches dinner parties and their participants online. By using the dinner party matching system 1000, the burden on the organizer who planned the dinner party can be reduced.

[0012] Fig. 1 is a diagram showing an example of the configuration of a dinner party matching system 1000. As shown in Fig. 1, the dinner party matching system 1000 includes a dinner party matching device 1 and a user terminal 2, which are communicably connected to each other via a network N. The network N is, for example, a wired LAN (Local Area Network), a wireless LAN, the Internet, a public line network, a mobile data communication network, or a combination of these. In the example of Fig. 1, the dinner party matching system 1000 includes one dinner party matching device 1, but may include multiple dinner party matching devices 1.

[0013] The dinner party matching device 1 is an information processing device that recruits participants for a dinner party and matches the dinner party with the participants. The dinner party matching device 1 is, for example, a server device, but is not limited to this. The dinner party matching device 1 will be described in detail later.

[0014] The user terminal 2 is an information processing device used by a user of the dinner party matching system 1000 (dinner party matching service). The user terminal 2 is, for example, a PC (Personal Computer), a smartphone, or a tablet terminal, but is not limited to these. As shown in FIG. 1, users of the dinner party matching system 1000 include organizers, applicants, participants, and invitees.

[0015] An organizer is a user who plans a dinner party. An applicant is a user who applies to attend a dinner party planned by an organizer. A participant is a user who is accepted to attend a dinner party planned by an organizer. An invitee is a user who is invited to a dinner party by an organizer. In the following, users of the dinner party matching system 1000 will be referred to as organizers, applicants, participants, invitees, or simply users, depending on their role. Note that users of the dinner party matching system 1000 can hold multiple of these roles.

[0016] <Hardware configuration of information processing device 100> Next, a description will be given of a hardware configuration of the information processing device 100. Fig. 2 is a diagram showing an example of a hardware configuration of the information processing device 100. As shown in Fig. 2, the information processing device 100 includes a processor 101, a memory 102, a storage 103, a communication I / F 104, an input device 105, an output device 106, and a drive device 107, which are connected to each other via a bus B.

[0017] The processor 101 controls each component of the information processing device 100 and realizes the functions of the information processing device 100 by expanding into the memory 102 various programs including an OS (Operating System) and a dinner party matching program stored in the storage 103 and executing them. The processor 101 is, for example, a CPU (Central Processing Unit), an MPU (Micro Processing Unit), a GPU (Graphics Processing Unit), an ASIC (Application Specific Integrated Circuit), or a DSP (Digital Signal Processor), but is not limited to these.

[0018] The memory 102 is, for example, a Read Only Memory (ROM), a Random Access Memory (RAM), or a combination thereof. The ROM is, for example, a Programmable ROM (PROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), or a combination thereof. The RAM is, for example, but is not limited to, a Dynamic RAM (DRAM) or a Static RAM (SRAM).

[0019] The storage 103 stores various programs and data including an OS and a dinner party matching program. The storage 103 is, for example, a flash memory, a hard disk drive (HDD), a solid state drive (SSD), or a storage class memory (SCM), but is not limited to these.

[0020] The communication I / F 104 is an interface for connecting the information processing device 100 to an external device via the network N and controlling communication. The communication I / F 104 is, for example, Bluetooth (registered trademark), Wi-Fi (registered trademark), ZigBee (registered trademark), or Ethernet (registered trademark), but is not limited thereto.

[0021] The input device 105 is a device for inputting information to the information processing device 100. The input device 105 is, for example, a mouse, a keyboard, a touch panel, a microphone, a scanner, a photographing device (camera), various sensors, or an operation button, but is not limited to these.

[0022] The output device 106 is a device for outputting information from the information processing device 100. The output device 106 is, for example, a display device, a projector, a printer, a speaker, or a vibrator, but is not limited to these.

[0023] The drive device 107 is a device that reads and writes data to the recording medium 108. The drive device 107 is, for example, but not limited to, a magnetic disk drive, an optical disk drive, a magneto-optical disk drive, or an SD card reader. The recording medium 108 is, for example, but not limited to, a CD (Compact Disc), a DVD (Digital Versatile Disc), a FD (Floppy Disk), an MO (Magneto-Optical disk), a BD (Blu-ray (registered trademark) Disc), a USB (registered trademark) memory, or an SD card.

[0024] In this embodiment, the dinner party matching program may be written into the memory 102 or storage 103 during the manufacturing stage of the information processing device 100, or may be provided to the information processing device 100 via the network N, or may be provided to the information processing device 100 via a non-transitory computer-readable recording medium such as a recording medium 108.

[0025] <Functional configuration of the dinner party matching device 1> Next, a description will be given of the functional configuration of the dinner party matching device 1. Fig. 3 is a diagram showing an example of the functional configuration of the dinner party matching device 1. As shown in Fig. 3, the dinner party matching device 1 includes a communication unit 11, a storage unit 12, and a control unit 13.

[0026] The communication unit 11 is realized by the communication I / F 104. The communication unit 11 transmits and receives information to and from the user terminal 2 via the network N.

[0027] The storage unit 12 is realized by the memory 102 and the storage 103. The storage unit 12 stores user information 121, dinner party information 122, and applicant information 123.

[0028] The user information 121 is information related to a user. The user information 121 is stored for each user.

[0029] Fig. 4 is a diagram showing an example of user information 121. The user information 121 in Fig. 4 includes, as information items, "UID", "user name", "age", "gender", "address", "favorite food", "amount eaten", "disliked ingredients", "allergy ingredients", "dinner party (organizer)", "dinner party (participant)", "restaurant (already visited)", and "restaurant (preferred)".

[0030] "UID" is identification information that uniquely identifies a user. Hereinafter, a user whose "UID" is UXXX may be referred to as user XXX. In addition, if user XXX is a manager, applicant, participant, or invitee, they may be referred to as manager XXX, applicant XXX, participant XXX, or invitee XXX, respectively.

[0031] "User name" is information indicating the name of a user. In the example of Fig. 4, the "user names" of user 001, user 002, and user 003 are "xxx", "yyy", and "zzz", respectively.

[0032] "Age" is information indicating the age of the user. In the example of Fig. 4, the "ages" of user 001, user 002, and user 003 are "30 (years old)", "40 (years old)", and "50 (years old)", respectively.

[0033] "Gender" is information indicating the gender of the user. In the example of Fig. 4, the "gender" of user 001, user 002, and user 003 is "male", "female", and "female", respectively. Note that the gender of the user is not limited to male and female.

[0034] "Address" is information indicating the address of the user. In the example of Fig. 4, the "Addresses" of User 001, User 002, and User 003 are "Tokyo," "Chiba," and "Saitama," respectively.

[0035] "Favorite food" is information indicating a user's favorite food. In the example of FIG. 4, the "favorite food" of user 001, user 002, and user 003 are "sushi," "wine," and "French food," respectively. A user's favorite food can be set arbitrarily, such as an ingredient (e.g., meat), a dish (e.g., sushi), a food genre (e.g., French food), or a type of alcohol (e.g., wine). A user may set multiple favorite foods.

[0036] "Amount of food eaten" is information indicating the amount of food eaten by the user. In the example of FIG. 4, the "amount of food eaten" of user 001, user 002, and user 003 is "normal", "small", and "large", respectively. The amount of food eaten by the user can be set to any level, not limited to the three levels of "small, normal, and large". Furthermore, the amount of alcohol consumed by the user may be set as the amount of food eaten by the user.

[0037] "Disliked ingredients" is information that indicates ingredients that the user dislikes. In the example of Fig. 4, the "disliked ingredients" of user 001, user 002, and user 003 are "-", "tomato", and "-", respectively. A user may set multiple disliked ingredients.

[0038] "Allergy ingredients" is information that indicates the allergy ingredients of the user. In the example of Fig. 4, the "allergy ingredients" of user 001, user 002, and user 003 are "-", "-", and "buckwheat", respectively. A user may set multiple allergy ingredients.

[0039] "Dinner Party (Organizer)" is information indicating a dinner party for which a user acted as organizer. In the example of Fig. 4, "Dinner Party (Organizer)" is a PID, and the "Dinner Party (Organizer)" for User 001, User 002, and User 003 are "P001", "-", and "P003", respectively. Note that a PID is identification information that uniquely identifies a dinner party.

[0040] "Dinner Party (Participant)" is information indicating a dinner party in which a user participated as a participant. In the example of Fig. 4, "Dinner Party (Participant)" is a PID, and "Dinner Party (Participant)" for User 001, User 002, and User 003 are "P002", "P001", and "-", respectively.

[0041] "Store (Already visited)" is information indicating a restaurant that the user has been to. In the example of FIG. 4, "Store (Already visited)" is an RID, and the "Store (Already visited)" for user 001, user 002, and user 003 are "R001, R002," "R001," and "R003," respectively. RID is identification information that uniquely identifies a restaurant. Hereinafter, a restaurant with an RID of RXXX may be referred to as restaurant XXX.

[0042] "Store (desired)" is information indicating the restaurant the user wants to go to and the reward. In the example of Fig. 4, the information indicating the restaurant the user wants to go to is an RID.

[0043] The reward is generated when the organizer of a dinner party invites the user to a dinner party held at a restaurant registered by the user as a restaurant the user would like to visit. The reward may be registered by the user, or may be automatically set by the dinner party matching device 1. The reward may be set as a percentage based on the "amount" or as a percentage of a reference amount set separately from the "amount". The reward may also be set as the amount itself rather than a percentage. The reward may be cash, points that can be used on the dinner party matching service, or cryptocurrency (virtual currency). The reward may be paid in full by the user to the organizer, the restaurant, or the operator of the dinner party matching service, or may be paid in installments to two or more of these parties.

[0044] In the example of FIG. 4, the "restaurant (desired)" of user 001 is "R004:10,000p." This indicates that if user 001 wishes to visit restaurant 004, and the organizer holds a dinner party at restaurant 004 and invites user 001 to the dinner party, a reward of 10,000 points that can be used on the dinner party matching service will be generated from user 001. For example, user 001 will pay 4,500 points to the organizer, 4,500 points to restaurant 004, and 1,000 points to the operator of the dinner party matching service.

[0045] Furthermore, the reward may be a right to participate in a dinner party hosted by the user at another restaurant. In the example of Fig. 4, the "restaurant (desired)" of user 002 is "R005:R001". This indicates that user 002 wishes to visit restaurant 005, and when an organizer hosts a dinner party at restaurant 005 and invites user 002 to the dinner party, the organizer will be given a right to participate in the dinner party hosted by user 002 at restaurant 001.

[0046] The "UID" is automatically assigned by the dining party matching device 1 when the user registers for the dining party matching service. The "user name," "age," "gender," "address," "favorite foods," "meal size," "disliked ingredients," "allergy ingredients," and "restaurant (preferred)" are registered by the user via the user terminal 2. The "dinner party (organizer)" and "dinner party (participants)" are automatically added by the dining party matching device 1 each time the user plans or attends a dining party. The "restaurant (already visited)" may be registered by the user via the user terminal 2, or may be automatically added by the dining party matching device 1 each time the user plans or attends a dining party.

[0047] It should be noted that the user information 121 is not limited to the example in Fig. 4. The user information 121 may not include some of the above information items, and may include information items other than those described above.

[0048] The dinner party information 122 is information related to a dinner party. The dinner party information 122 is stored for each dinner party.

[0049] Fig. 5 is a diagram showing an example of dinner party information 122. The dinner party information 122 in Fig. 5 includes, as information items, "PID", "dinner party name", "restaurant name", "address", "URL", "date and time of event", "number of people making reservations", "number of people wanted", "amount", "display range", "organizer", "invitees", "participants", "desired conditions", "payment method", "free text", and "cancellation policy".

[0050] "PID" is identification information that uniquely identifies a dinner party. Hereinafter, a dinner party with a "PID" of PXXX may be referred to as "dinner party XXX."

[0051] "Meal name" is information that indicates the name of a meal. In the example of Fig. 5, the "Meal name" of meal 004 is "May meal."

[0052] "Store name" is information that indicates the name of the restaurant where the dinner party will be held. In the example of Fig. 5, the "Store name" of dinner party 004 is "AAA".

[0053] "Address" is information that indicates the address of the restaurant where the dinner party will be held. In the example of Fig. 5, the "Address" of Dinner Party 004 is "Tokyo".

[0054] "URL" is information indicating the URL of the restaurant where the dinner party will be held. In the example of Fig. 5, the "URL" of Dinner Party 004 is "aaa.com".

[0055] "Date and time of holding" is information that indicates the date and time of holding a dinner party. In the example of Fig. 5, the "Date and time of holding" of dinner party 004 is "5 / 25 18:00".

[0056] "Number of people with reservation" is information indicating the number of people who have made a reservation at a restaurant to hold a dinner party. In the example of Fig. 5, the "number of people with reservation" for dinner party 004 is "6 (people)".

[0057] "Number of people wanted" is information that indicates the number of people being invited to a dinner party. In the example of FIG. 5, the "number of people wanted" for dinner party 004 is "4 people." Since the "number of people with reservations" is the sum of the organizer and participants, the "number of people wanted" is less than the "number of people with reservations." For example, if the "number of people with reservations" is 6 people, the maximum number of people wanted is 5 people.

[0058] "Amount" is information indicating an estimate of the amount of the dinner party. In the example of Fig. 5, the "amount" of dinner party 004 is "10,000 (yen)." The "amount" may be a range.

[0059] The "display range" is information indicating the range of users for which the dinner party invitation is displayed. The "display range" can be set to any range that can be restricted based on one or more pieces of user information 121. The "display range" may be set as the range of users who are displayed, or as the range of users who are not displayed. In the example of FIG. 5, the "display range" for dinner party 004 is "Age: 30s". This indicates that invitation for participants for dinner party 004 is only open to users with an "age" of 30s.

[0060] "Organizer" is information that indicates the organizer of the dinner party. In the example of Fig. 5, "organizer" is the UID of the organizer, and the "organizer" of dinner party 004 is "U004".

[0061] "Invitee" is information indicating the invitee of the dinner party and whether or not they will attend. In the example of Fig. 5, "Invitee" is the invitee's UID and whether or not they will attend, and the "Invitee" for dinner party 004 is "U005: Not yet decided". This indicates that the attendance of invitee 005 is not yet decided.

[0062] "Participant" is information indicating the participants of the dinner party. In the example of Fig. 5, "Participant" is the UID of the participant, and the "Participant" of dinner party 004 is "U006".

[0063] "Desired conditions" is information indicating the conditions desired by the organizer for the participants of the dinner party. Any conditions that can be set based on one or more pieces of user information 121 can be set as "desired conditions." In the example of FIG. 5, the "desired conditions" for dinner party 004 is "Favorite food: wine." This indicates that the organizer is hoping for users whose "favorite food" is wine to participate in dinner party 004.

[0064] "Payment method" is information that indicates the payment method for the dinner party. In the example of Fig. 5, the "Payment method" for dinner party 004 is "cash".

[0065] "Free text" is information that indicates text that can be freely written by the organizer and is displayed on the dinner party invitation screen. In the example of Fig. 5, the "free text" for dinner party 004 is "···".

[0066] The "cancellation policy" is information indicating penalties for participants of a dinner party. The "cancellation policy" may be registered by the organizer, or may be automatically set by the dinner party matching device 1. The "cancellation policy" includes information indicating the conditions and details of the penalty. The "cancellation policy" includes, for example, information indicating the cancellation deadline and cancellation fee.

[0067] The cancellation deadline is an example of a penalty occurrence condition, and is the date by which participation in the dinner party must be canceled based on the "date and time of the event." The cancellation deadline may be set, for example, on the day, one day before, two days before, or three days before. Multiple cancellation deadlines may be set for one dinner party.

[0068] The cancellation fee is an example of a penalty, and is a fee that is incurred when a participant cancels participation in a dinner party within the cancellation deadline. The cancellation fee may be set as a percentage based on the "amount," or may be set as a percentage of a base amount set separately from the "amount." The amount itself may be set as the cancellation fee, rather than a percentage. The cancellation fee may be in the form of cash, points that can be used on the dinner party matching service, or cryptocurrency (virtual currency). It is preferable that the cancellation fee is set higher the closer the cancellation deadline is to the "date and time of the event."

[0069] In the example of Figure 5, the "cancellation policy" for Dinner Party 004 is "On the day: 100%, One day before: 80%." If the cancellation fee is based on the "amount," this "cancellation policy" indicates that if a participant cancels their participation in the dinner party on the day of the "date and time," they will be charged a cancellation fee of 10,000 yen (100% of the "amount"), and if they cancel their participation in the dinner party one day before the "date and time," they will be charged a cancellation fee of 8,000 yen (80% of the "amount").

[0070] The "PID" is automatically assigned by the dinner party matching device 1 when the organizer registers the dinner party. The "dinner party name," "restaurant name," "address," "URL," "date and time of event," "number of people making reservations," "number of people wanted," "price," "display range," "organizer," "desired conditions," "payment method," "free text," and "cancellation policy" are registered by the user via the user terminal 2. The "number of people wanted" and "participants" are automatically updated by the dinner party matching device 1 each time participants for the dinner party are decided.

[0071] It should be noted that the dinner party information 122 is not limited to the example in Fig. 5. The dinner party information 122 may not include some of the above information items, or may include information items other than those described above.

[0072] The applicant information 123 is information about applicants for the dinner party. The applicant information 123 is stored for each dinner party.

[0073] Fig. 6 is a diagram showing an example of the applicant information 123. The applicant information 123 in Fig. 6 includes "PID" and "applicant" as information items.

[0074] "PID" is identification information that uniquely identifies a dinner party.

[0075] "Applicant" is information indicating the applicant who applied to participate in the dinner party. In the example of Fig. 6, "Applicant" is the UID of the applicant, and the "Applicants" for dinner party 004 and dinner party 005 are "U007, U008" and "U009", respectively.

[0076] The "applicants" are automatically updated by the dinner party matching device 1 every time an application for a dinner party is accepted.

[0077] It should be noted that the applicant information 123 is not limited to the example in Fig. 6. The applicant information 123 may not include some of the above information items, or may include information items other than those above.

[0078] The control unit 13 is realized by the processor 101 reading and executing a program from the memory 102 and cooperating with other hardware configurations. The control unit 13 controls the overall operation of the dinner party matching device 1. The control unit 13 includes a participant recruiting unit 131, an application receiving unit 132, a participant receiving unit 133, and a cancellation processing unit 134.

[0079] The participant recruiting unit 131 recruits participants for the dinner party based on the dinner party information 121 registered by the organizer of the dinner party. Specifically, in response to a request from the user terminal 2, the participant recruiting unit 131 transmits the dinner party information 122 to the user terminal 2 of the user included in the display range, and causes the user terminal 2 to display a dinner party recruitment screen.

[0080] The application receiving unit 132 receives applications from applicants to participate in the dinner party. Specifically, the application receiving unit 132 receives a request to participate in the dinner party from the applicant's user terminal 2, and adds the "applicant" to the applicant information 123. Furthermore, in response to a request from the user terminal 2 of the organizer, the application receiving unit 132 transmits the user information 121 of the applicant for the dinner party registered by the organizer, and causes the user terminal 2 of the organizer to display it.

[0081] The participant receiving unit 133 receives the selection of participants from among the applicants for the dinner party by the organizer. The participant receiving unit 133 may compare the user information 121 of the applicant with the desired conditions for the dinner party and recommend the applicant who most closely matches the desired conditions to the organizer as a participant. When the participant receiving unit 133 receives the selection of participants, it adds "participants" to the dinner party information 122 and reduces the "number of people wanted."

[0082] The cancellation processing unit 134 performs a process of canceling a participant's participation in a dinner party. Specifically, when the cancellation processing unit 134 is notified of a cancellation from the participant's user terminal 2, it deletes the participant from the "Participants" in the dinner party information 122 and increases the "Number of participants wanted". In addition, the cancellation processing unit 134 executes payment of a cancellation fee from the participant in accordance with the "Privacy Policy" of the canceled dinner party. The cancellation fee may be paid in its entirety to the organizer, or it may be paid in part to the organizer and in part to the operator of the dinner party matching service.

[0083] The functional configuration of the dinner party matching device 1 is not limited to the above example. For example, the dinner party matching device 1 may have a part of the functional configuration described above, and the user terminal 2 may have the rest. The dinner party matching device 1 may also have functional configurations other than those described above. Each functional configuration of the dinner party matching device 1 may be realized by software as described above, or may be realized by hardware such as an IC chip, a SoC (System on Chip), an LSI (Large Scale Integration), or a microcomputer.

[0084] <Functional configuration of user terminal 2> Next, a description will be given of the functional configuration of the user terminal 2. Fig. 7 is a diagram showing an example of the functional configuration of the user terminal 2. As shown in Fig. 7, the user terminal 2 includes a communication unit 21, a storage unit 22, and a control unit 23.

[0085] The communication unit 21 is realized by the communication I / F 104. The communication unit 21 transmits and receives information to and from the dinner party matching device 1 via the network N.

[0086] The storage unit 22 is realized by the memory 102 and the storage 103. The storage unit 22 stores user information 221, dinner party information 222, and applicant information 223.

[0087] The user information 221 is information relating to the user of the user terminal 2. The contents of the user information 221 are similar to those of the user information 121, and therefore a description thereof will be omitted.

[0088] The dinner party information 222 is information about a dinner party planned by the user of the user terminal 2. The contents of the dinner party information 222 are similar to those of the dinner party information 122, and therefore a description thereof will be omitted.

[0089] The applicant information 223 is information about applicants for a dinner party planned by the user of the user terminal 2. The content of the applicant information 223 is similar to that of the applicant information 123, and therefore a description thereof will be omitted.

[0090] The control unit 23 is realized by the processor 101 reading and executing a program from the memory 102 and working in cooperation with other hardware configurations. The control unit 23 controls the overall operation of the user terminal 2. The control unit 23 includes a display control unit 231.

[0091] In response to a user's operation, the display control unit 231 displays various screens on the display device of the user terminal 2. The screens displayed on the user terminal 2 will be described in detail later.

[0092] The functional configuration of the user terminal 2 is not limited to the above example. For example, the user terminal 2 may have part of the functional configuration described above, and the dinner party matching device 1 may have the rest. The user terminal 2 may also have functional configurations other than those described above. Each functional configuration of the user terminal 2 may be realized by software as described above, or may be realized by hardware such as an IC chip, SoC, LSI, or microcomputer.

[0093] <Meal party registration process> Next, a dinner party registration process executed by the dinner party matching system 1000 will be described. Fig. 8 is a flowchart showing an example of the dinner party registration process executed by the dinner party matching system 1000. Below, a case where the organizer 004 plans the dinner party 004 will be described as an example (see Fig. 5). Hereinafter, the user terminal 2 of the organizer 004 will be referred to as user terminal 2A, and the user terminal 2 of the invitee 005 will be referred to as user terminal 2B.

[0094] (Step S101) First, the organizer 004 operates the user terminal 2A to display the dinner party registration screen sc1 on the user terminal 2A (step S101). In other words, the display control unit 231 of the user terminal 2A displays the dinner party registration screen sc1 on the display device of the user terminal 2A in response to the operation of the organizer 004. The dinner party registration screen sc1 is a screen for the organizer 004 to plan and register the dinner party 004.

[0095] Fig. 9 is a diagram showing an example of the dinner party registration screen sc1. The dinner party registration screen sc1 in Fig. 9 includes a basic information setting area c11, a desired condition setting area c12, a cancellation policy setting area c13, a clear button c14, and a registration button c15.

[0096] The basic information setting area c11 is an area for setting basic information for the dinner party 004. The basic information setting area c11 includes input fields for "dinner party name," "restaurant name," "date and time," "number of people reserved," "number of people wanted," "amount," "address," "URL," "display range," "invitees," "payment method," and "free text."

[0097] The "store name," "address," and "URL" may be automatically input in cooperation with an external service, thereby reducing the effort required of the organizer 004 to input the information.

[0098] In addition, it is preferable that the "number of people to be recruited" be smaller than the "number of people to reserve." Specifically, in the example of FIG. 9, it is preferable that the input field for "number of people to be recruited" be controlled so that when 6 is entered in the "number of people to reserve" input field, 1 to 5 are selectable in the "number of people to be recruited" input field (drop-down list). This allows the number of people to be registered that is smaller than the number of people to reserve, and therefore prevents an excessive number of people to be registered by mistake, resulting in more participants than the number of people to reserve.

[0099] The "invitee" may be selected by the organizer 004 from among users who are friends, or from among users recommended by the dinner party matching device 1 based on the desired conditions and user information 221. The "invitee" may be selected from a list of users who have registered the restaurant where the dinner party will be held as a restaurant they would like to visit ("restaurant (desired)"). In this case, it is preferable that the list of users display the reward that will be generated when each user is invited. This allows the organizer 004 to select invitees with reference to the reward.

[0100] The desired condition setting area c12 is an area for setting desired conditions for the dinner party 004. The desired condition setting area c12 includes input fields for "favorite food (type of alcohol)", "amount of food (amount of alcohol, amount eaten)", "gender", and "age". In the desired condition setting area c12, desired conditions other than those mentioned above may be set.

[0101] The cancellation policy setting area c13 is an area for setting a cancellation policy for the dinner party 004. The cancellation policy setting area c13 includes an input field for the "cancellation policy (cancellation deadline and cancellation fee)." In the cancellation policy setting area c13, four or more "cancellation policies" may be set.

[0102] The clear button c14 is a button for clearing the input contents on the dinner party registration screen sc1. When the organizer 004 selects the clear button c14, the input contents on the dinner party registration screen sc1 are cleared.

[0103] The registration button c15 is a button for registering dinner party 004 using the information entered on the dinner party registration screen sc1.

[0104] (Step S102) When the organizer 004 selects the registration button c15, the user terminal 2A stores the information entered on the dinner party registration screen sc1 as dinner party information 222 for dinner party 004 in the memory unit 22, and transmits the dinner party information 222 for dinner party 004 to the dinner party matching device 1 (step S102).

[0105] (Step S103) When the participant recruiting unit 131 of the dinner party matching device 1 receives the dinner party information 222 for dinner party 004 from the user terminal 2A, it stores it in the memory unit 12 as dinner party information 122 for dinner party 004 (see FIG. 5) and registers dinner party 004 (step S103). At this time, the participant recruiting unit 131 assigns "PID (P004)" to dinner party 004 and adds P004 to "Dinner Party (Organizer)" in the user information 121 of the organizer 004. At this point, since no participants have been decided other than the organizer 004, "Invites" is "U005: Not Yet" and "Participants" is "-".

[0106] (Step S104) Next, the participant recruiting unit 131 starts recruiting participants for the dinner party 004 (step S104). Specifically, the participant recruiting unit 131 starts transmitting the dinner party information 122 for the dinner party 004 in response to a request from the user terminal 2. At this time, the participant recruiting unit 131 compares the user information 121 of the user who requested the dinner party information 122 for the dinner party 004 with the "display range" of the dinner party 004 to determine whether the user is included in the "display range", and if the user is included in the "display range", transmits the dinner party information 122 for the dinner party 004 to the user terminal 2 of that user.

[0107] In addition, when there is a high degree of similarity between the user information 121 of a user included in the "display range" and the dinner party information 122 of the dinner party 004, the participant recruiting unit 131 may recommend the dinner party 004 to the user. Examples of a method for recommending the dinner party 004 include a method of displaying the dinner party 004 on the user terminal 2 as a "dinner party recommended for you" or displaying the dinner party 004 with a "recommended" mark.

[0108] (Step S105) Next, the participant recruiting unit 131 checks whether an invitee has been set for the dinner party 004 by referring to the dinner party information 122 of the dinner party 004 (step S105). If an invitee has not been set (step S105: NO), the registration process ends. On the other hand, if an invitee has been set (step S105: YES), the registration process proceeds to step S106.

[0109] (Step S106) The participant recruiting unit 131 sends an invitation to the dinner party 004 to the user terminal 2B of the invitee 005 of the dinner party 004 (step S106). The invitation may be sent on the dinner party matching service, or may be sent by e-mail or the like.

[0110] (Step S107) The invitee 005 who has received the invitation to the dinner party 004 on the user terminal 2B operates the user terminal 2B to send an indication of whether or not he or she will attend the dinner party 004 to the dinner party matching device 1 (step S107).

[0111] (Step S108) The participants recruiting unit 131 of the dinner party matching device 1, which has received the invitation to attend the dinner party 004 from the user terminal 2B of the invitee 005, updates the dinner party information 122 of the dinner party 004 according to the invitation to attend (step S108). Specifically, if the invitee 005 attends the dinner party, the participants recruiting unit 131 changes "Inviter" to "P005: Yes" and adds "P005" to "Participants". On the other hand, if the invitee 005 does not attend the dinner party, the participants recruiting unit 131 changes "Inviter" to "P005: No".

[0112] (Step S109) Thereafter, the participant recruiting unit 131 notifies the user terminal 2A of the organizer 004 of whether the invitee 005 can participate in the dinner party 004 (step S109). The notification of whether or not the invitee can participate may be made on the dinner party matching service or by e-mail or the like.

[0113] <Meal Party Recruitment Processing> Next, a dinner party recruitment process executed by the dinner party matching system 1000 will be described. Fig. 10 is a flowchart showing an example of the dinner party recruitment process executed by the dinner party matching system 1000. In the following, a case where the user 006 applies for the dinner party 004 will be described as an example (see Fig. 5). Hereinafter, the user terminal 2 of the user 006 will be referred to as the user terminal 2C.

[0114] (Step S201) First, in response to an operation by the user 006, the user terminal 2C requests the dinner party information 122 from the dinner party matching device 1 (step S201).

[0115] (Step S202) When the dinner party information 122 is requested, the application receiving unit 132 of the dinner party matching device 1 compares the user information 121 of the user 006 with the "display range" of the dinner party information 122 of each dinner party, and selects a dinner party whose "display range" includes the user 006 (step S202). In the example of FIG. 5, the "display range" of dinner party 004 is "Age: 30s". Therefore, if the user 006 is in his 30s, dinner party 004 is selected. On the other hand, if the user 006 is not in his 30s, dinner party 004 is not selected. Here, it is assumed that the user 006 is 30, and dinner party 004 is selected.

[0116] (Step S203) Then, the application receiving unit 132 transmits the dinner party information 122 of the selected dinner party to the user terminal 2C (step S203). As a result, the dinner party information 122 of a plurality of dinner parties including the dinner party 004 is transmitted to the user terminal 2C.

[0117] (Step S204) The display control unit 231 of the user terminal 2C stores the dinner party information 122 received from the dinner party matching device 1 in the memory unit 22 as dinner party information 222, and displays the dinner party list screen sc2 on the display device of the user terminal 2C based on the dinner party information 222 (step S204). The dinner party list screen sc2 is a screen that displays a list of dinner parties registered in the dinner party matching device 1 that include the user 006 in the display range.

[0118] Fig. 11 is a diagram showing an example of the dinner party list screen sc2. A dinner party selection button c21, a sort button c22, and a dinner party information display area c23 are displayed on the dinner party list screen sc2 in Fig. 11.

[0119] The dinner party selection button c21 is a button for selecting the dinner party for which the dinner party information 122 is to be displayed. In the example of FIG. 11, the dinner party selection button c21 allows one to be selected from three options: "All," "Planned to be held," and "Planned to attend," and "All" is selected. "All" is a button that displays dinner party information 122 for all dinner parties for which the dinner party information 122 has been obtained from the dinner party matching device 1. "Planned to be held" is a button that displays dinner party information 122 for dinner parties for which the user is the organizer. "Planned to attend" is a button that displays dinner party information 122 for dinner parties for which the user has been approved as a participant.

[0120] The sort button c22 is a button for sorting the dinner parties displayed in the dinner party information display area c23 for the dinner party information 122. In the example of Fig. 11, the dinner parties are sorted by date. Possible sorting methods include new arrival, number of people wanted, amount of money, etc.

[0121] The dinner party information display area c23 is an area that displays an overview of each dinner party (part of the dinner party information 122). In the example of Fig. 11, the dinner party information display area c23 displays "date and time of event", "organizer", "restaurant name", "address", "dinner party name", "number of people booked", and "number of people wanted".

[0122] When the dinner party list screen sc2 is displayed, the user 006 selects the dinner party information area c23 for the dinner party 004, and displays the dinner party invitation screen sc3 for the dinner party 004. The dinner party invitation screen sc3 is a screen for inviting guests to the dinner party, on which detailed information about the dinner party is displayed.

[0123] Fig. 12 is a diagram showing an example of the dinner party invitation screen sc3. The dinner party invitation screen sc3 in Fig. 12 displays a dinner party information display area c31 and an application button c32.

[0124] The dinner party information display area c31 is an area that displays the details of each dinner party (all or part of the dinner party information 122). In the example of Fig. 12, the dinner party information display area c31 displays the "Date and time of the event", "Organizer", "Restaurant name", "Address", "Dinner party name", "Number of people reserved", "Number of people wanted", "Participants", "Desired conditions", "Free text (comments from the organizer)", and "Cancellation policy" for dinner party 004.

[0125] The apply button c32 is a button for applying to participate in the dinner party 004.

[0126] (Step S205) When the user 006 selects the apply button sc32, the user terminal 2C applies to participate in the dinner party 004 to the dinner party matching device 1 (step S205). Hereinafter, the user 006 is referred to as the applicant 006.

[0127] (Step S206) When the application receiving unit 132 of the dinner party matching device 1 receives the application from the user terminal 2C, it updates the applicant information 123 (step S206). Specifically, the application receiving unit 132 adds the applicant 006 as an applicant to the applicant information 123 of the dinner party 004.

[0128] (Step S207) Thereafter, in response to an operation by the organizer 004, the user terminal 2A requests the applicant information 123 for the dinner party 004 from the dinner party matching device 1 (step S207).

[0129] (Step S208) When the applicant information 123 is requested, the application receiving unit 132 of the dinner party matching device 1 transmits the applicant information 123 of the dinner party 004 to the user terminal 2A (step S208). At this time, the application receiving unit 132 also transmits user information 121 of the applicants of the dinner party 004, including the applicant 006 (excluding "allergic ingredients" and "disliked ingredients"), together with the applicant information 123, to the user terminal 2A.

[0130] (Step S209) When the display control unit 131 of the user terminal 2A receives the applicant information 123, it saves it as applicant information 223 and displays the applicant list screen sc4 based on the applicant information 223 (step S209). The applicant list screen sc4 is a screen that displays a list of applicants for the dinner party 004.

[0131] Fig. 13 is a diagram showing an example of the applicant list screen sc4. The applicant list screen sc4 in Fig. 13 displays a dinner party information display area c41 and an applicant information display area c42.

[0132] The dinner party information display area c41 is an area that displays an overview (part of the dinner party information 122) of the dinner party 004. In the example of Fig. 13, the dinner party information display area c41 displays the "date and time of the dinner party," "organizer," "restaurant name," "address," "dinner party name," and "recruitment number of people," as well as the number of applications for the dinner party 004.

[0133] The applicant information display area c42 is an area that displays an overview of each applicant (part of the user information 121). In the example of Fig. 13, the applicant information display area c42 displays "UID", "age", "gender", and "address", the application date and time, a reject button c43, and an approve button c44.

[0134] The reject button c43 is a button for rejecting the participation of an applicant in the dinner party 004.

[0135] The approval button c44 is a button for approving the applicant's participation in the dinner party 004.

[0136] (Step S210) The organizer 004 selects the applicant 006 as a participant by selecting the approval button c44 for the applicant 006. When the organizer 004 selects the approval button c44 for the applicant 006, the user terminal 2A notifies the dinner party matching device 1 that the applicant 006 has been approved as a participant (step S210).

[0137] (Step S211) When the participant acceptance unit 133 of the dinner party matching device 1 is notified by the user terminal 2A that the applicant 006 has been approved as a participant, the participant acceptance unit 133 updates the dinner party information 122 of the dinner party 004 (step S211). Specifically, the participant acceptance unit 133 adds the applicant 006 to the "participants" of the dinner party 004, and reduces the "number of participants" by one.

[0138] (Step S212) Then, the participant acceptance unit 133 notifies the user terminal 2C of the applicant 006 that the applicant 006 has been approved as a participant (step S212). The notification that the applicant 006 has been approved as a participant may be made on the dinner party matching service or by e-mail or the like. Hereinafter, the applicant 006 will be referred to as the participant 006.

[0139] (Step S213) The participant reception unit 133 also notifies the user terminal 2A of the organizer 004 of the "allergenic ingredients" and "disliked ingredients" in the user information 121 of the participant 006 (step S213). The display control unit 131 of the user terminal 2A displays the "allergenic ingredients" and "disliked ingredients" of each participant including the participant 006 on the participant list screen sc5, for example.

[0140] Fig. 14 is a diagram showing an example of the participant list screen sc5. The participant list screen sc5 in Fig. 14 displays a dinner party information display area c51 and a participant information display area c52.

[0141] The dinner party information display area c51 is an area that displays an overview (part of the dinner party information 122) of the dinner party 004. In the example of Fig. 14, the dinner party information display area c51 displays the "date and time of the dinner party," "organizer," "restaurant name," "address," and "dinner party name" of the dinner party 004.

[0142] The participant information display area c52 is an area that displays an overview of each applicant (part of the user information 121). In the example of Fig. 14, the participant information display area c52 displays "UID", "ingredients that cause allergies", "ingredients that you dislike", and a cancel button c53.

[0143] The cancel button c53 is a button for cancelling the participation of a participant.

[0144] By checking the participant list screen sc5, the organizer 004 can ascertain the "allergenic ingredients" and "disliked ingredients" of each participant, including the participant 006, without having to check with each participant individually, and can contact the restaurant in advance. The "allergenic ingredients" and "disliked ingredients" may be displayed on another screen. At least one of the "allergenic ingredients" and "disliked ingredients" may be sent to the user terminal 2A in step S208.

[0145] <Cancellation of dinner party> Next, a description will be given of the dinner party cancellation process executed by the dinner party matching system 1000. Fig. 15 is a flowchart showing an example of the dinner party cancellation process executed by the dinner party matching system 1000. In the following, an example will be described in which the participant 006 cancels participation in the dinner party 004.

[0146] (Step S301) First, the participant 006 operates the user terminal 2C to display the dinner party invitation screen sc6 on the user terminal 2C (step S301). In other words, the display control unit 231 of the user terminal 2C displays the dinner party invitation screen sc6 on the display device of the user terminal 2C in response to the operation of the participant 006.

[0147] Fig. 16 is a diagram showing an example of a dinner party invitation screen sc6. As shown in Fig. 16, a cancel button c61 is displayed on the dinner party invitation screen sc6 for the dinner party 004 in which the participant 006 will participate. The cancel button c61 is a button for canceling participation in the dinner party 004.

[0148] (Step S302) When the participant 006 selects the cancel button c61, the user terminal 2C notifies the dinner party matching device 1 of the cancellation of participation in the dinner party 004 (step S302).

[0149] (Step S303) When the cancellation of the participant 006's participation in the dinner party 004 is notified from the user terminal 2C, the cancellation processing unit 134 of the dinner party matching device 1 updates the dinner party information 122 of the dinner party 004 (step S303). Specifically, the cancellation processing unit 134 deletes the participant 006 from "Participants" and increases the "Number of participants" by one.

[0150] (Step S304) The cancellation processing unit 134 also notifies the organizer 004 that the participant 006 has canceled participation in the dinner party 004 (step S304). The cancellation notification may be made on the dinner party matching service, or may be made by e-mail or the like.

[0151] (Step S305) Thereafter, the cancellation processing unit 134 refers to the "cancellation policy" of the dinner party 004 and determines whether the timing of the cancellation by the participant 006 falls within the cancellation deadline (step S305). If the timing does not fall within the cancellation deadline (step S305: NO), the cancellation processing ends. On the other hand, if the timing falls within the cancellation deadline (step S305: YES), the processing proceeds to step S306.

[0152] (Step S306) If the timing of the cancellation by the participant 006 falls within the cancellation deadline, the cancellation processing unit 134 refers to the "cancellation policy" of the dinner party 004 and pays the cancellation fee corresponding to the applicable cancellation deadline. For example, if the participant 006 cancels the dinner party 004 on 5 / 24 (the day before the "date and time of the event (5 / 25 18:00)"), the cancellation processing unit 134 pays a cancellation fee of 8,000 yen (80% of the "amount (10,000 yen)" of the dinner party 004) from the participant 006 to the organizer 004. This can reduce the effort of the organizer 004 in collecting the cancellation fee from the participant 006. It can also ensure that the cancellation fee is collected from the participant 006. Note that a portion of the cancellation fee may be paid to the operator of the dinner party matching service.

[0153] <Summary> As described above, the dinner party matching system 1000 recruits participants for the dinner party based on the dinner party information 122 registered by the dinner party organizer, accepts applications from applicants to participate in the dinner party, and accepts the selection of participants from among the applicants. By using the dinner party matching system 1000, the dinner party organizer can complete each task of recruiting participants for the dinner party, accepting applications, and selecting participants using a well-formatted online dinner party matching service. This reduces the burden on the organizer compared to when the organizer individually asks potential participants to participate in the dinner party or when the organizer personally recruits participants through SNS or the like.

[0154] <Additional Notes> The present embodiment includes the following disclosure.

[0155] (Appendix 1) A dinner party matching method executed by a dinner party matching system, A participant recruiting step of recruiting participants for the dinner party based on the dinner party information registered by the organizer of the dinner party; an application acceptance step of accepting an application from an applicant to participate in the dinner party; a participant acceptance step of accepting a selection of participants from among the applicants; A method for matching meals including:

[0156] (Appendix 2) The dinner party information includes a cancellation policy. The method for matching a dinner party described in appendix 1.

[0157] (Appendix 3) The cancellation policy includes information indicating a cancellation period and a cancellation fee. The method for matching a dinner party described in Appendix 2.

[0158] (Appendix 4) If the participant cancels participation in the dinner party within the cancellation period, the participant will pay the cancellation fee. The method for matching a dinner party described in Appendix 3.

[0159] (Appendix 5) The cancellation policy is set by the organizer. The method for matching a dinner party described in Appendix 2.

[0160] (Appendix 6) The user information of the participant is notified to the organizer. The method for matching a dinner party described in appendix 1.

[0161] (Appendix 7) The user information includes information indicating ingredients to which the participant has an allergy. The method of matching a dinner party described in Appendix 6.

[0162] (Appendix 8) The user information includes information indicating ingredients that the participant dislikes. The method of matching a dinner party described in Appendix 6.

[0163] (Appendix 9) The dinner party information includes information indicating the number of people reserved and the number of people being recruited, The number of people to be recruited that is less than the number of people to be reserved can be registered. The method for matching a dinner party described in appendix 1.

[0164] (Appendix 10) Recommending a dinner party to a user based on the user information of the user The method for matching a dinner party described in appendix 1.

[0165] (Appendix 11) Recommending the applicant to the organizer based on the user information of the applicant. The method for matching a dinner party described in appendix 1.

[0166] (Appendix 12) The user information of the user includes information indicating a reward to be generated when the user is invited to a dinner party. The method for matching a dinner party described in appendix 1.

[0167] (Appendix 13) A dinner party matching method executed by a dinner party matching system, A participant recruiting unit that recruits participants for the dinner party based on the dinner party information registered by the organizer of the dinner party; an application receiving unit that receives applications from applicants to participate in the dinner party; a participant reception unit that receives a selection of participants from among the applicants; A dinner party matching system that includes:

[0168] (Appendix 14) For the dinner party matching system, A participant recruiting step of recruiting participants for the dinner party based on the dinner party information registered by the organizer of the dinner party; an application acceptance step of accepting an application from an applicant to participate in the dinner party; a participant acceptance step of accepting a selection of participants from among the applicants; A dinner party matching program for executing a dinner party matching method including the steps of:

[0169] The embodiments disclosed herein are illustrative in all respects and should not be considered as limiting. The scope of the present invention is indicated by the claims, not by the above meaning, and is intended to include all modifications within the meaning and scope of the claims. The present invention is not limited to the above-mentioned embodiments, and various modifications are possible within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. [Explanation of symbols]

[0170] 1: Dinner party matching device 2: User terminal 121: User information 122: Dinner party information 123: Applicant information 131:Participant Recruitment Department 132: Application Reception Department 133: Participant reception 134: Cancellation processing unit 231: Display control unit 1000: Dinner party matching system

Claims

1. A dinner party matching method executed by a dinner party matching system, A participant recruiting step of recruiting participants for the dinner party based on the dinner party information registered by the organizer of the dinner party; an application acceptance step of accepting an application from an applicant to participate in the dinner party; a participant acceptance step of accepting a selection of participants from among the applicants; A method for matching meals including:

2. The dinner party information includes a cancellation policy. The method for matching a dinner party according to claim 1 .

3. The cancellation policy includes information indicating a cancellation period and a cancellation fee. The dinner party matching method according to claim 2 .

4. If the participant cancels participation in the dinner party within the cancellation period, the participant will pay the cancellation fee. The dinner party matching method according to claim 3.

5. The cancellation policy is set by the organizer. The dinner party matching method according to claim 2 .

6. The user information of the participant is notified to the organizer. The method for matching a dinner party according to claim 1 .

7. The user information includes information indicating ingredients to which the participant has an allergy. The dinner party matching method according to claim 6.

8. The user information includes information indicating ingredients that the participant dislikes. The dinner party matching method according to claim 6.

9. The dinner party information includes information indicating the number of people reserved and the number of people being recruited, The number of people to be recruited that is less than the number of people to be reserved can be registered. The method for matching a dinner party according to claim 1 .

10. Recommending a dinner party to a user based on the user information of the user The method for matching a dinner party according to claim 1 .

11. Recommending the applicant to the organizer based on the user information of the applicant. The method for matching a dinner party according to claim 1 .

12. The user information of the user includes information indicating a reward to be generated when the user is invited to a dinner party. The method for matching a dinner party according to claim 1 .

13. A dinner party matching method executed by a dinner party matching system, A participant recruiting unit that recruits participants for the dinner party based on the dinner party information registered by the organizer of the dinner party; an application receiving unit that receives applications from applicants to participate in the dinner party; a participant reception unit that receives a selection of participants from among the applicants; A dinner party matching system that includes:

14. For the dinner party matching system, A participant recruiting step of recruiting participants for the dinner party based on the dinner party information registered by the organizer of the dinner party; an application acceptance step of accepting an application from an applicant to participate in the dinner party; a participant acceptance step of accepting a selection of participants from among the applicants; A dinner party matching program for executing a dinner party matching method including the steps of:

Images