JP2022128094A - Meeting support device and control program for the same - Google Patents

Abstract

To flexibly address the diversification of settlement methods for a price generated in an on-line meeting without time and effort.SOLUTION: A meeting support device comprises a first control unit, a determination unit, a second control unit, and a processing unit. The first control unit controls such that a price generated in an on-line meeting is displayed on a display device of a communication terminal used by at least one participant of the participants in the meeting. The determination unit determines a payment amount of the price for each participant according to input by an input device in the communication terminal on which the price is displayed. The second control unit controls such that a payment amount of a participant who pays the price, among the participants, is displayed on the display device of the communication terminal used by the participant. The processing unit executes processing related to the settlement of the price equivalent to the payment amount of the participant who uses the communication terminal on which the payment amount is displayed according to the input by the input device in the communication terminal.SELECTED DRAWING: Figure 11

Description

An embodiment of the present invention relates to a meeting support device and its control program for supporting online meetings.

In recent years, there have been an increasing number of online meetings such as meetings, social gatherings, social gatherings, banquets, and drinking parties using video call functions of communication terminals such as personal computers, smartphones, and tablet terminals. When these meetings involve eating and drinking, it is common for participants to prepare their own food and drinks.

2. Description of the Related Art Recently, the spread of a delivery system in which a delivery company delivers a menu item cooked in a restaurant to a home or the like has been remarkably spread. Therefore, it is speculated that there will be more cases in the future where participants in online meetings prepare food and drinks using delivery systems. However, charges such as product charges and delivery charges when using the delivery system are usually paid by online payment such as credit card or code payment when the user places an order. For this reason, for example, if the organizer of a meeting bears all or part of the costs incurred at the meeting, or splits the bill among the participants equally, the charges will be recalculated after the meeting and money will not be exchanged. It has to be done and it takes time.

Japanese Patent Application Laid-Open No. 2007-219820

The problem to be solved by the embodiments of the present invention is to provide a meeting support device that can flexibly cope with the diversification of payment methods for online meetings.

In one embodiment, a meeting support device includes a first control unit, a determination unit, a second control unit, and a processing unit. The first control unit controls so that the charge generated in the meeting is displayed on the display device of the communication terminal used by one of the participants in the online meeting. The determining unit determines the payment amount of the price for each participant according to the input of the input device in the communication terminal on which the price is displayed. The second control unit controls such that the payment amount of the participant is displayed on the display device of the communication terminal used by the participant who has paid the price. The processing unit executes processing related to settlement of the payment equivalent to the payment amount of the participant using the communication terminal according to the input of the input device of the communication terminal on which the payment amount is displayed.

1 is a system configuration diagram for realizing a meeting support service according to an embodiment; FIG. A block diagram showing the hardware configuration of a meeting server and an order server in the meeting support system. Schematic diagram showing main databases provided in a meeting server and an order server. 4 is a schematic diagram showing the data structure of a host record stored in a host database; FIG. Schematic diagram showing the data structure of a meeting record stored in a meeting database. Schematic diagram showing the data structure of a restaurant record stored in a restaurant database. Schematic diagram showing the data structure of a delivery company record stored in a delivery company database. Schematic diagram showing the data structure of a participant record stored in a participant database. Schematic diagram showing the data structure of an order record stored in an order database. Explanatory diagram of functions realized by a meeting server and an order server in the meeting support system. Explanatory diagram of the meeting payment function. FIG. 4 is a flowchart showing the procedure of information processing executed by the processor of the meeting server; FIG. FIG. 13 is a flow chart showing the procedure of meeting creation processing in FIG. 12; FIG. FIG. 13 is a flow chart showing the procedure of the meeting holding process in FIG. 12; FIG. FIG. 10 is a flow chart showing the procedure of information processing executed by a processor of the order server upon receiving a participant registration request; FIG. 4 is a flow chart showing the procedure of information processing executed by a processor of an order server upon receiving an order request; 4 is a flow chart showing the procedure of information processing executed by the processor of the order server upon receipt of an exit request; FIG. 10 is a flow chart showing the procedure of information processing executed by the processor of the order server upon receipt of the closing request; FIG. FIG. 10 is a flow chart showing the procedure of information processing executed by the processor of the order server upon receipt of the closing request; FIG. FIG. 10 is a transition diagram of screens displayed on the communication terminal when applying for a meeting; FIG. 4 is a transition diagram of screens displayed on a communication terminal when participating in a meeting; FIG. 10 is a transition diagram of screens displayed on the communication terminal when ordering a product; FIG. 10 is a transition diagram of screens displayed on the communication terminal when leaving the meeting; FIG. 10 is a transition diagram of screens displayed on the communication terminal when the meeting is closed. The figure which shows an example of the sorting screen displayed on a communication terminal at the time of the closing of a meeting.

Embodiments of a meeting support device for supporting online meetings involving eating and drinking, such as conferences, social gatherings, social gatherings, banquets, and drinking parties, will be described below with reference to the drawings.

[Description of system configuration]
First, the system configuration including the meeting support device of this embodiment will be described with reference to FIG.
FIG. 1 is a system configuration diagram for realizing a meeting support service according to this embodiment. This system includes a meeting support system 1 , one or more restaurant systems 2 , one or more delivery company systems 3 , multiple access points 4 , and multiple communication terminals 5 . Meeting support system 1 , restaurant system 2 , delivery company system 3 and access point 4 are all connected to communication network 6 . The communication network 6 is the Internet, WAN (Wide Area Network) or LAN (Local Area Network). The communication network 6 may be a wired line or a wireless line. The communication network 6 may have a mixture of wired lines and wireless lines.

Each communication terminal 5 is connected to one of the access points 4 via a wireless LAN, a telephone line, or the like. The access point 4 is a relay point for connecting each communication terminal 5 and the meeting support system 1 via the communication network 6 .

The communication terminal 5 is a computer terminal including at least a display device 51 , an input device 52 and a video call device 53 . The display device 51 is a device capable of screen display such as a liquid crystal display and an EL (Electroluminescent) display. The input device 52 is a keyboard, touch panel, mouse, or the like. A video call device 53 is a camera, a microphone, a speaker, and the like.

The communication terminal 5 is equipped with an application program for a video call function, a so-called video call application, and an application program for a web client function, a so-called web browser. By installing a video call application on the communication terminal 5, the users of each communication terminal 5 can have online meetings using video calls. By installing a web browser in the communication terminal 5, the user of each communication terminal 5 can view and process information provided by the web server. For example, a personal computer, a smart phone, a tablet terminal, or the like is used as the communication terminal 5 .

The meeting support system 1 is a computer system built in a business entity that provides meeting support services, a so-called meeting support business entity. A meeting support system 1 includes a meeting server 10 and an order server 20 . The meeting support system 1 realizes a function as a meeting support device through cooperation between the meeting server 10 and the order server 20 . That is, the meeting support system 1 is one aspect of a meeting support device.

The meeting server 10 is a computer for supporting online meetings, such as conferences, social gatherings, social gatherings, banquets, and drinking parties, held online by each participant using the video call function of the communication terminal 5 . The meeting server 10 has a function as a web server. Therefore, the user of the communication terminal 5 equipped with a web browser can view and process the information provided by the meeting server 10 .

The order server 20 is a computer for assisting the participants in the meeting supported by the meeting server 10 to order products using the communication terminals 5 and to settle the payment for the order. The order server 20 has a function as a web server. Therefore, the user of the communication terminal 5 equipped with a web browser can view and process the information provided by the order server 20 .

The items ordered by the order server 20 are typically menu items prepared in restaurants. A participant orders a menu item by using the communication terminal 5 from home, for example. In that case, the product will be delivered to your home using the delivery system. A participant may place an order using the communication terminal 5 at a restaurant. In that case, the merchandise is served to the participants by the clerk. In other words, no delivery system is used. Alternatively, a participant at a restaurant may order menu items offered at the restaurant to be delivered to other participants at home. In that case, the product is delivered to another participant's home using the delivery system. Note that the product may be a menu item manufactured at a retail store that sells side dishes, lunch boxes, and the like. In the following description, this type of retail store is also defined as a restaurant.

The settlements supported by the order server 20 are individual settlements in which the participants pay the price individually, equal splitting settlements in which the participants split the price in an equal amount (equal splitting), and one of the participants pays the price. This includes a lump sum settlement that pays all together, for example, a distribution settlement that distributes participants who pay for each product. That is, the order server 20 implements a settlement program corresponding to these settlement methods.

The restaurant system 2 is a computer system built in a restaurant that cooperates with the meeting support service. The restaurant system 2 has a function of providing a list of menu items to the participants via the meeting support system 1, and a function of notifying the products of the menu items ordered by the participants via the meeting support system 1. have Upon receiving this notification, the restaurant staff cooks the ordered product by the designated time.

The delivery company system 3 is a computer system built by a delivery company that cooperates with the meeting support service. The delivery company system 3 has a function of notifying the delivery person of the delivery information requested by the participant via the meeting support system 1 . The home delivery information includes information on the menu item ordered by the participant and the restaurant that manufactures the product of the menu item, information on the delivery destination specified by the participant, information on the delivery time, and the like. Upon receiving the delivery information, the delivery staff receives the menu item ordered by the participant from the restaurant at the specified time and delivers it to the location specified by the participant.

[Description of configuration of meeting support device]
FIG. 2 is a block diagram showing the hardware configuration of each server (meeting server 10 and order server 20) included in meeting support system 1. As shown in FIG. The basic hardware configuration of meeting server 10 and order server 20 is the same. Therefore, in the block diagram of FIG. 2, the 1's digits of the two-digit codes indicating the elements of the hardware configuration are common, and the tens' digits are "1" for the meeting server 10 and "2" for the order server 20. FIG. In the following, the main hardware configuration will be described using the meeting server 10 as an example. Since the hardware configuration of the order server 20 is also the same except for the difference in the tens place of the code, the description here is omitted.

Meeting server 10 includes processor 11 , main memory 12 , auxiliary storage device 13 , clock 14 , communication interface 15 and system transmission line 16 . The system transmission line 16 includes an address bus, a data bus, control signal lines and the like. Meeting server 10 connects processor 11 , main memory 12 , auxiliary storage device 13 , clock 14 and communication interface 15 to system transmission line 16 . In the meeting server 10, a computer is composed of a processor 11, a main memory 12, an auxiliary storage device 13, a clock 14, a communication interface 15, and a system transmission line 16 connecting them.

The processor 11 corresponds to the central portion of the computer. The processor 11 controls each part to implement various functions of the meeting server 10 according to an operating system or application program. The processor 11 is, for example, a CPU (Central Processing Unit).

The main memory 12 corresponds to the main memory portion of the computer. Main memory 12 includes a non-volatile memory area and a volatile memory area. The main memory 12 stores an operating system or application programs in a non-volatile memory area. The main memory 12 stores, in a volatile memory area, data necessary for the processor 11 to execute processing for controlling each unit. The above data may be stored in a non-volatile memory area. The main memory 12 uses a volatile memory area as a work area in which data is appropriately rewritten by the processor 11 . The non-volatile memory area is, for example, ROM (Read Only Memory). A volatile memory area is, for example, a RAM (Random Access Memory).

The auxiliary storage device 13 corresponds to the auxiliary storage portion of the computer. As the auxiliary storage device 13, well-known storage devices such as SSDs (Solid State Drives), HDDs (Hard Disc Drives), EEPROMs (Electric Erasable Programmable Read-Only Memories), etc. are used singly or in combination. The auxiliary storage device 13 stores data used by the processor 11 in performing various types of processing, data created by processing in the processor 11, and the like. The auxiliary storage device 13 may store the above application programs.

Clock 14 keeps the date and time. The meeting server 10 acquires the date and time clocked by the clock 14 as the current date and time.

The communication interface 15 is a circuit for transmitting and receiving data to and from each device connected via the communication network 6 according to a predetermined communication protocol. The equipment includes equipment of the restaurant system 2 , equipment of the delivery company system 3 , and communication terminal 5 connected via access point 4 .

FIG. 3 is a schematic diagram showing major databases provided in the meeting server 10 and the order server 20, respectively. The meeting server 10 uses part of the storage area of the auxiliary storage device 13 as an area for a host database 131 and a meeting database 132 . The order server 20 uses part of the storage area of the auxiliary storage device 23 as areas for a restaurant database 231 , a delivery company database 232 , a participant database 233 , and an order database 234 .

The organizer database 131 is an area for accumulating organizer records RCa describing data relating to the organizer of the meeting. The organizer is one person selected from among the participants of the meeting. The organizer will apply to the meeting sponsoring entity to hold the meeting online, and will play a role in determining the opening and closing of the meeting on the date of the meeting. The organizer record RCa, as shown in FIG. 4, includes the organizer ID, the name of the organizer, the e-mail address, the login password, the credit card information, and the like. The organizer ID is a unique identification code assigned to each organizer to identify the organizer. The name, e-mail address, login password and credit card information are the name, e-mail address, login password and credit card information of the organizer identified by the organizer ID.

The meeting database 132 is an area for storing meeting records RCb describing data relating to meetings. As shown in FIG. 5, the meeting record RCb includes meeting ID, meeting name, date and time, number of participants N, organizer ID, organizer's mail address, electronic ticket information for the number of participants N, meeting status, and the like. A meeting ID is a unique identification code assigned to each meeting to identify the meeting. Meeting name, date and time, number of participants N, organizer ID, and organizer email address are the name of the meeting identified by the meeting ID, date and start time, number of participants N, and the organizer ID and email address of the organizer. be. The number of participants N is the sum of the organizer and participants invited to the meeting by the organizer, so-called invitees. Therefore, the number of participants N is a numerical value of 2 or more. The name of the meeting, the date and time of the meeting, and the number of participants N are the requirements for holding the meeting.

Electronic ticket information is information on an electronic ticket issued to each participant. Electronic ticket information includes a ticket ID, a meeting password, and an email address. A ticket ID is a unique identification code assigned to each electronic ticket to identify the electronic ticket. The meeting password is a password for logging in to the meeting by the participant who received the electronic ticket identified by the ticket ID. The e-mail address is the e-mail address of the participant who received the electronic ticket. That is, the e-mail address of the electronic ticket information issued to the organizer is the organizer's e-mail address. The e-mail address of the electronic ticket information issued to the invitee is the invitee's e-mail address.

The meeting status is data indicating the status of the meeting record RCb. The states of the meeting record RCb include "before" until the host decides to start the meeting, "ongoing" after the host decides to start the meeting, and "ongoing" after the host decides to start the meeting. There is an "after closing" after the decision has been made.

The restaurant database 231 is an area for accumulating restaurant records RCc describing data relating to restaurants cooperating with the meeting support service. The restaurant record RCc, as shown in FIG. 6, includes restaurant ID, restaurant name, target area, menu information, deposit amount, and the like. The restaurant ID is a unique identification code assigned to each restaurant to identify the restaurant. The restaurant name, target area and menu information are the name of the restaurant identified by the restaurant ID, the target area contracted to provide products accompanying the meeting support service, information on menu items that can be provided to meeting participants (item name , price, etc.). The received amount is the amount paid to the restaurant from the meeting support entity.

The delivery company database 232 is an area for storing delivery company records RCd describing data relating to delivery companies cooperating with the meeting support service. The delivery company record RCd includes, as shown in FIG. 7, a delivery company ID, a delivery company name, a target area, a delivery charge, a payment amount, and the like. The delivery company ID is a unique identification code assigned to each delivery company to identify the delivery company. The delivery company name, target area, and delivery fee are the name of the delivery company identified by the delivery company ID, the target area for delivery associated with the meeting support service, and the amount charged for one delivery within the target area. be. The amount received is the amount paid by the meeting support entity to the delivery company.

The participant database 233 is an area for storing participant records RCe describing data on participants. The participant record RCe includes, as shown in FIG. 8, a ticket ID, meeting password, meeting ID, meeting name, date and time, category information, mail address, delivery destination information, in-store flag, payment status, and the like. The ticket ID and meeting password are information on the electronic ticket received by the participant. The meeting ID, meeting name, and date and time are the meeting ID, meeting name, and date and time of the meeting in which the participant participates. Classification information is information for classifying whether a participant is a host or an invitee. The e-mail address is the e-mail address used by the participant. The delivery destination information is information such as the address and telephone number of the delivery destination designated by the participant. The in-store flag is 1-bit data for identifying whether the delivery destination designated by the participant is a restaurant cooperating with the meeting support service. In this embodiment, it is "1" in the case of a restaurant, and "0" in the case of a non-restaurant. Payment status is data that indicates the state of a participant's payment. There are three statuses related to payment: "no payment", "payment", and "delayed payment", leaving without payment.

The order database 234 is an area for accumulating order records RCf describing data relating to orders of participants. The order record RCf, as shown in FIG. 9, includes ticket ID, meeting ID, meeting name, order list, total amount, billing amount, payment amount, and the like. The ticket ID is the ticket ID of the electronic ticket received by the participant. The meeting ID and meeting name are the meeting ID and meeting name of the meeting in which the participant participates. The order list is a list of product names, prices, etc. of menu items ordered by participants. The total price is the total price of the menu items ordered by the participant. The billed amount is the amount billed to the participant. The payment amount is the amount paid by the participant.

[Explanation of function of meeting support device]
FIG. 10 is an explanatory diagram of functions realized by the meeting server 10 and the order server 20 of the meeting support system 1. As shown in FIG. The meeting server 10 has a meeting creation function 101 and a meeting holding function 102 . The order server 20 has a participant registration function 201 , a menu provision function 202 , an order reception function 203 , a cooking instruction function 204 , a delivery instruction function 205 and a meeting settlement function 206 .

The meeting creating function 101 communicates with the communication terminal 5 to perform a process of storing the organizer record RCa in the organizer database 131, a process of storing the meeting record RCb in the meeting database 132, and a participant registration function of the order server 20. 201 to request registration of participants. The meeting holding function 102 refers to the host database 131 and the meeting database 132 to control the opening and closing of the meeting by communicating with the communication terminal 5, and cooperates with the participant registration function 201 of the order server 20, By referring to the participant database 233, the process of controlling the participant's participation in and withdrawal from the meeting is executed.

The participant registration function 201 cooperates with the meeting creation function 101 of the meeting server 10 to execute processing for storing the participant record RCe in the participant database 233 . The menu providing function 202 cooperates with the participant registration function 201 to perform processing for providing participants with a list of menu items that can be ordered from restaurants cooperating with the meeting support service. The order reception function 203 refers to the participant database 233 through communication with the communication terminal 5, and cooperates with the menu provision function 202 to process orders for products from participants and to process the order database based on the orders. and updating the H.234 order record RCf. The cooking instruction function 204 refers to the restaurant database 231 and cooperates with the order reception function 203 to instruct the restaurant to cook the product ordered by the participant. The delivery instruction function 205 refers to the delivery company database 232 and cooperates with the order reception function 203 to execute processing for instructing the delivery company to deliver the ordered product.

The meeting settlement function 206 refers to the participant database 233 through communication with the communication terminal 5, and cooperates with the meeting holding function 102 of the meeting server 10 to execute processing related to settlement of charges incurred in the meeting. Specifically, the meeting settlement function 206 executes processing as the first control unit 31, the determination unit 32, the second control unit 33, and the processing unit 34, as shown in FIG.

The first control unit 31 controls the display device 51 of the communication terminal 5 used by one of the participants of the online meeting to display the price generated in the meeting. The determination unit 32 determines the payment amount of the price for each participant according to the input of the input device 52 in the communication terminal 5 on which the price is displayed. The second control unit 33 controls so that the payment amount of the participant is displayed on the display device 51 of the communication terminal 5 used by the participant who has paid the price. The processing unit 34 executes processing related to settlement of the price equivalent to the payment amount of the participant using the communication terminal 5 according to the input of the input device 52 of the communication terminal 5 on which the payment amount is displayed.

[Description of the operation of the meeting support device]
12 to 14 are flowcharts showing procedures of information processing executed by the processor 11 of the meeting server 10 according to the control program. 15 to 19 are flow charts showing procedures of information processing executed by the processor 21 of the order server 20 according to the control program. 20 to 24 are schematic diagrams showing transition examples of screens displayed on the display device 51 of the communication terminal 5 according to the above information processing. Main operations of the meeting support system 1 will be described below with reference to the drawings. It should be noted that the information processing procedure is not limited to the procedure of the flowchart. Any suitable change can be made as long as the same action and effect can be obtained. Also, the screen example is just an example. The layout, images, texts, etc. of each screen are not limited to those shown in the drawings.

Incidentally, the control program for meeting server 10 is installed in auxiliary storage device 13 . The control program may be installed in main memory 12 . Similarly, the control program for order server 20 is installed in auxiliary storage device 23 . The control program may be installed in the main memory 22 . The method of installing the control program in the main memories 12, 22 or the auxiliary storage devices 13, 23 is not particularly limited. The control program can be installed in the main memories 12 and 22 or the auxiliary storage devices 13 and 23 by recording the control program on a removable recording medium or distributing the control program by communication via a network. The recording medium may be of any form, such as an SD memory card, USB memory, etc., as long as it can store the program and can be read by the device.

First, the processor 11 of the meeting server 10 publishes the top screen SCa (see FIGS. 20 to 22) of the website operated by the meeting support entity as ACT1. The top screen SCa is a screen displaying a meeting button BTa and a eating and drinking button BTb. The meeting button BTa is a soft button for enabling the meeting creation function 101 or the meeting holding function 102 . The food and drink button BTb is a soft button for enabling the order reception function 203 of the order server 20 . A soft button can also be called a soft key, an operator, or the like.

When the user of the communication terminal 5 operates the input device 52 to access the website managed by the meeting support entity, the display device 51 displays the top screen SCa. The user operates the input device 52 to input the meeting button BTa when applying to the meeting support entity to hold an online meeting or when participating in the meeting. The user operates the input device 52 to input the food/drink button BTb when ordering menu items provided by the restaurant as food for eating/drinking at the meeting.

The processor 11 that has opened the top screen SCa confirms whether or not the meeting button BTa has been input as ACT2. If the meeting button BTa has not been input, the processor 11 determines NO in ACT2 and proceeds to ACT3. The processor 11 confirms whether or not the food/drink button BTb has been input as ACT3. If the food/drink button BTb is not input, the processor 11 determines NO in ACT3 and returns to ACT2. Thus, the processor 11 waits for input of the meeting button BTa or input of the eating and drinking button BTb as ACT2 and ACT3.

In the standby state of ACT2 and ACT3, when the meeting button BTa is input, the processor 11 determines YES in ACT2 and proceeds to ACT4. The processor 11 controls such that the processing selection screen SCb (see FIG. 20 or 22) is displayed on the display device 51 of the communication terminal 5 to which the meeting button BTa has been input as ACT4. The process selection screen SCb is a screen displaying a create button BTc and a hold button BTd. The creation button BTc is a soft button for enabling the meeting creation function 101 . The holding button BTd is a soft button for enabling the meeting holding function 102 . The user can select a process to be executed by the meeting creation function 101 by inputting the meeting button BTa on the top screen SCa and then pressing the create button BTc on the process selection screen SCb. The user can select a process to be executed by the meeting holding function 102 by inputting the meeting button BTa on the top screen SCa and then pressing the holding button BTd on the process selection screen SCb.

The processor 11 that controls the display of the process selection screen SCb confirms whether or not the creation button BTc has been input as ACT5. If the create button BTc has not been input, the processor 11 determines NO in ACT5 and proceeds to ACT6. The processor 11 confirms whether or not the start button BTd has been input as ACT6. If the hold button BTd is not input, the processor 11 determines NO in ACT6 and returns to ACT5. Thus, the processor 11 waits for input of the create button BTc or input of the start button BTd as ACT5 and ACT6.

In the waiting state of ACT5 and ACT6, when the creation button BTc is input, the processor 11 determines YES in ACT5 and proceeds to ACT7. The processor 11 executes meeting creation processing as ACT7. The meeting creating process is a process executed by the meeting creating function 101 . The procedure for meeting creation processing will be described later. After completing the meeting creation process, the processor 11 ends the information processing for the communication terminal 5 to which the meeting button BTa has been input. The processor 11 opens the top screen SCa again.

In the standby state of ACT5 and ACT6, when the start button BTd is input, the processor 11 determines YES in ACT6 and proceeds to ACT8. Processor 11 executes meeting holding processing as ACT8. The meeting holding process is a process executed by the meeting holding function 102 . The procedure of meeting holding processing will be described later. After completing the meeting holding process, the processor 11 ends the information processing for the communication terminal 5 to which the meeting button BTa has been input. The processor 11 opens the top screen SCa again.

In the standby state of ACT2 and ACT3, when the food and drink button BTb is input, the processor 11 determines YES in ACT3 and proceeds to ACT9. The processor 11 notifies the order server 20 of the order request in ACT9. The operation of the order server 20 that receives this notification will be described later. The processor 11 that has notified the order request ends the information processing for the communication terminal 5 to which the food/drink button BTb has been input. The processor 11 opens the top screen SCa again.

(Explanation of operation when applying for a meeting)
13, 15 and 20, a description will be given of the operation when a participant applies to a meeting support business entity to hold an online meeting.

FIG. 13 is a flow chart showing the procedure of meeting creation processing executed by processor 11 of meeting server 10 . As described above, when the user of the communication terminal 5, that is, the participant who participates in the meeting, inputs the meeting button BTa on the top screen SCa and then the creation button BTc on the process selection screen SCb, the processor 11 creates the meeting. go into processing. The processor 11 controls so that the host login screen SCc (see FIG. 20) is displayed on the display device 51 of the communication terminal 5 to which the creation button BTc has been input as ACT11. The host login screen SCc is a screen displaying a host ID input box BXa, a login password input box BXb, and a new registration button BTe. The new registration button BTe is a soft button for commanding new registration of the organizer.

Participants who apply to the Meeting Supporting Entity to hold a meeting are limited to the organizer. For this reason, participants who have not registered as a host enter the new registration button BTe. On the other hand, a participant who has completed the organizer registration performs a login operation. Specifically, the participant enters the host ID and login password set at the time of host registration into the input boxes BXa and BXb of the host login screen SCc.

The processor 11 that has controlled the display of the host login screen SCc checks as ACT 12 whether or not login has been performed. If the login has not been performed, the processor 11 determines NO in ACT12 and proceeds to ACT13. The processor 11 confirms whether or not the new registration button BTe has been input as ACT13. If the new registration button BTe has not been input, the processor 11 determines NO in ACT13 and returns to ACT12. In this way, the processor 11 waits for login as ACT12 and ACT13 or input of the new registration button BTe.

In the standby state of ACT12 and ACT13, when confirming that the organizer record RCa containing the organizer ID entered in the input box BXa and the login password entered in the input box BXb is stored in the organizer database 131, The processor 11 recognizes that login has been performed. The processor 11 determines YES in ACT12 and proceeds to ACT17. Processing after ACT 17 will be described later.

In the standby state of ACT12 and ACT13, when the new registration button BTe is input, the processor 11 determines YES in ACT13 and proceeds to ACT14. The processor 11 controls so that the organizer registration screen SCd (see FIG. 20) is displayed on the display device 51 of the communication terminal 5 as ACT14. The organizer registration screen SCd is a screen that displays an organizer name input box BXc, an email address input box BXd, a login password input box BXe, a credit card information input box BXf, and a registration button BTf. be. The organizer's name, email address, login password and credit card information are essential organizer information for registering as an organizer. The registration button BTf is a soft button for commanding the registration of the organizer information entered in each of the input boxes BXc-BXf. After confirming the host registration screen SCd, the participant enters his or her name, e-mail address, login password and credit card information in the input boxes BXc to BXf, respectively, and presses the registration button BTf.

The processor 11 that has controlled the display of the organizer registration screen SCd waits for input of the registration button BTf as ACT15. When the name, e-mail address, login password and credit card information are entered in the input boxes BXc to BXf and then the registration button BTf is entered, the processor 11 determines YES in ACT15 and proceeds to ACT16. The processor 11 issues a unique organizer ID as ACT 16 , creates an organizer record RCa, and stores it in the organizer database 131 . The organizer record RCa includes a unique organizer ID, and the name, email address, login password and credit card information entered as organizer information from the organizer registration screen SCd. After storing the host record RCa in host database 131, processor 11 proceeds to ACT 17. FIG.

As ACT17, the processor 11 controls the display device 51 of the communication terminal 5 to display the meeting acceptance screen SCe (see FIG. 20). The meeting reception screen SCe is a screen displaying a meeting name input box BXg, a date and time input box BXh, the number of participants N input box BXi, an invitee email address input box BXj, and an execution button BTg. be. The name of the meeting, the date and time of the meeting, and the number of participants are essential meeting information as requirements for holding the meeting. The inviter's e-mail address is the e-mail address of the so-called invitee of the participants of the meeting, excluding the organizer. Therefore, the number of input boxes BXj displayed is obtained by subtracting "1" from the number N of participants. The execute button BTg is a soft button for instructing registration of the meeting information and the invitee's email address entered in each of the input boxes BXg to BXj. The participant, that is, the organizer who confirmed the meeting reception screen SCe, enters the name of the meeting, the date and time of the meeting, the number of participants N, and the e-mail addresses of the invitees in the input boxes BXg to BXj, respectively, and presses the execution button BTg.

The processor 11 that has controlled the display of the meeting reception screen SCe waits for an input of the execution button BTg as ACT18. When the name of the meeting, the date and time of the meeting, the number of participants N, and the e-mail addresses of the invitees are entered in the input boxes BXg to BXj, and then the execution button BTg is entered, the processor 11 determines YES in ACT18, and proceeds to ACT19. . Processor 11 creates meeting record RCb as ACT 19 and stores it in meeting database 132 . The meeting record RCb includes a unique meeting ID, the meeting name input as meeting information, the date and time of the meeting, the number of participants N, the organizer's organizer ID and organizer's email address, and electronic ticket information for the number of participants N and meeting status. The electronic ticket information consists of a unique ticket ID, meeting password, and e-mail address. One piece of ticket information for the N number of participants includes the email address of the organizer. The other (N-1) ticket information includes the inviter's email address entered on the meeting reception screen SCe.

After storing the meeting record RCb in the meeting database 132, the processor 11 sets the meeting status of the meeting record RCb as ACT 20 to "before holding". The processor 11 also creates an electronic ticket as ACT21. Specifically, the processor 11 creates electronic ticket image data in which the ticket ID, meeting password, meeting name, date and time of the meeting, etc. are visualized for each piece of electronic ticket information included in the meeting record RCb. As ACT 22, the processor 11 distributes the image data of the electronic ticket to the e-mail address included in the electronic ticket information.

After that, the processor 11 notifies the order server 20 of the participant registration request as ACT 23, and ends the meeting creation process. The participant registration request includes the data of the meeting record RCb.

FIG. 15 is a flow chart showing the procedure of information processing as the participant registration function 201 executed by the processor 21 of the order server 20 that has received the notification of the participant registration request from the meeting server 10 . The processor 21 resets the counter n to "0" as ACT51. A counter n is provided in the volatile memory area of the main memory 22 . The processor 21 counts up the counter n by "1" as ACT52. Then, in ACT53, the processor 21 confirms whether or not the counter n has exceeded the number of participants N in the meeting record RCb.

If the counter n does not exceed the number of participants N, the processor 21 determines NO in ACT53 and proceeds to ACT54. The processor 21 selects the n-th electronic ticket information from the meeting record RCb as ACT54. The processor 21 then creates a participant record RCe as ACT 55 and stores it in the participant database 233 . The participant record RCe includes the meeting ID, meeting name and date and time of the meeting record RCb, the ticket ID and e-mail address of the n-th electronic ticket information, the category information, the delivery destination information, the in-store flag, and the payment status. including. If the e-mail address of the electronic ticket information matches the organizer's e-mail address of the meeting record RCb, the classification information becomes data that identifies the organizer. If the e-mail address of the electronic ticket information does not match the organizer's e-mail address of the meeting record RCb, the classification information becomes data identifying the invitees. The delivery destination information is Null data. The in-store flag is the default "0".

After storing the participant record RCe in the participant database 233, the processor 11 sets the payment status of the participant record RCe to "no payment" as ACT56. After that, the processor 21 returns to ACT52 and increments the counter n by "1". Then, the processor 21 repeats the processing of ACT54 to ACT56 in the same manner as described above until the counter n exceeds the number N of participants.

If the counter n exceeds the number of participants N, the processor 21 determines YES in ACT53. The processor 21 ends the information processing of the procedure shown in the flow chart of FIG.

(Explanation of operation when joining a meeting)
14 and 21, a description will be given of operations when a participant participates in an online meeting.

FIG. 14 is a flow chart showing the procedure of meeting holding processing executed by processor 11 of meeting server 10 . As described above, when the user of the communication terminal 5, that is, the participant who participates in the meeting, inputs the meeting button BTa on the top screen SCa and then the holding button BTd on the process selection screen SCb, the processor 11 starts the meeting. go into processing. When entering the meeting holding process, processor 11 controls display of meeting login screen SCf (see FIG. 21) on display device 51 of communication terminal 5 to which holding button BTd has been input as ACT31. The meeting login screen SCf is a screen displaying a ticket ID input box BXk and a meeting password input box BXm.

After confirming the meeting login screen SCf, the participant performs a login operation. Specifically, the participant operates the input device 52 to enter the ticket ID and the meeting password in the input boxes BXk and BXm of the meeting login screen SCf. The ticket ID and meeting password are displayed on the electronic ticket delivered as an e-mail when applying for the meeting.

The processor 11 that has controlled the display of the meeting login screen SCf waits for login as ACT32. After confirming that the participant record RCe including the ticket ID entered in the input box BXk and the meeting password entered in the input box BXl is stored in the participant database 233, the processor 11 determines that the login has been performed. recognize. The processor 11 determines YES in ACT32 and proceeds to ACT33.

The processor 11 checks the meeting status of the meeting record RCb having electronic ticket information including the ticket ID and meeting password entered by the login operation as ACT33. Here, if the meeting status is "before holding", the processor 11 determines YES in ACT33 and proceeds to ACT34. The processor 11 checks in ACT 34 whether or not the e-mail address of the electronic ticket information matches the organizer's e-mail address of the meeting record RCb.

If the e-mail address of the electronic ticket information does not match the organizer's e-mail address, the processor 11 determines NO in ACT34. Processor 11 terminates the meeting support processing as an error. In this way, participants other than the organizer, i.e. invitees, cannot log in from the meeting login screen SCf for the meeting with the meeting ID specified by the meeting record RCb whose meeting status is "before". . Participants who can log in are limited to the host.

If the e-mail address of the electronic ticket information matches the organizer's email address in the meeting record RCb, that is, if the organizer has logged in, the processor 11 determines YES in ACT34 and proceeds to ACT35. As ACT35, the processor 11 changes the meeting status of the meeting record RCb from "before" to "ongoing". Processor 11 then proceeds to ACT 38 . Processing after ACT38 will be described later.

On the other hand, if the meeting status of the meeting record RCb is not “before meeting”, the processor 11 determines NO in ACT33 and proceeds to ACT36. The processor 11 confirms whether the meeting status is "in progress" as ACT36. If the meeting status is not "ongoing", that is, if it is "after closing", the processor 11 determines NO in ACT36. Processor 11 terminates the meeting support processing as an error. In this way, for the meeting with the meeting ID specified by the meeting record RCb whose meeting status is "after closing", regardless of whether the host or the invitee is a host, the user can log in from the meeting login screen SCf. can't

If the meeting status is “ongoing”, processor 11 determines YES in ACT 36 and proceeds to ACT 37 . The processor 11 checks in ACT 37 whether or not the communication terminal 5 used by the organizer has responded with approval. As described above, the meeting status is not changed to "in progress" unless the organizer logs in from the meeting login screen SCf. Then, participants other than the organizer, that is, invitees, also log in from the meeting login screen SCf for the meeting with the meeting ID specified by the meeting record RCb after the meeting status is changed to "ongoing". be able to. When the inviter logs in, the display device 51 of the communication terminal 5 used by the organizer is notified that the inviter has logged in. The organizer then performs an operation to approve the invitees. With this operation, the communication terminal 5 used by the organizer responds with approval, so the processor 11 determines YES in ACT37 and proceeds to ACT38.

As ACT38, the processor 11 enables the video call function between the communication terminals 5 for which the login operation is performed from the meeting login screen SCf. As a result, the video call screen SCg (see FIG. 21) is displayed on the display device 51 of the communication terminal 5. FIG. Also, the video call device 53 of the communication terminal 5 is activated. As a result, a meeting by video call becomes possible between a plurality of participants who have logged in from the meeting login screen SCf, that is, between the organizer and at least one invitee.

A closing button BTh, a eating and drinking button BTi, and an exit button BTj are displayed on the video call screen SCg. The closing button BTh is a soft button for the participants to declare closing of the meeting. The food and drink button BTi is a soft button for participants to declare their order for menu items provided by the restaurant during the meeting. The exit button BTj is a soft button for a participant to declare his/her exit from the meeting.

The processor 11 that has enabled the video call function confirms whether or not the eating and drinking button BTi has been input as ACT39. If the food/drink button BTi has not been input, the processor 11 determines NO in ACT39 and proceeds to ACT40. The processor 11 confirms whether or not the exit button BTj has been input as ACT40. If the exit button BTj is not input, the processor 11 determines NO in ACT40 and proceeds to ACT41. The processor 11 confirms whether or not the closing button BTh has been input as ACT41. If the closing button BTh has not been input, the processor 11 determines NO in ACT41 and returns to ACT39. In this way, the processor 11 waits for input of the eating and drinking button BTi, the exit button BTj, or the closing button BTh as ACT39 to ACT41.

In the standby state of ACT39 to ACT41, when the eating and drinking button BTi is input, the processor 11 determines YES in ACT39 and proceeds to ACT42. The processor 11 notifies the order server 20 of the order request as ACT 42 . The operation of the order server 20 that receives this notification will be described later. The processor 11 that has notified the order request returns to the standby state of ACT39 to ACT41.

In the standby state of ACT39 to ACT41, when the exit button BTj is input, the processor 11 determines YES in ACT40 and proceeds to ACT43. The processor 11 notifies the order server 20 of the exit request in ACT43. The operation of the order server 20 that receives this notification will be described later. The processor 11 that has notified the exit request returns to the standby state of ACT39 to ACT41.

In the waiting state of ACT39 to ACT41, when the closing button BTh is input, the processor 11 determines YES in ACT41 and proceeds to ACT44. The processor 11 determines whether or not the e-mail address when logging in on the meeting login screen SCf as ACT 44 matches the organizer's e-mail address of the meeting record RCb including the ticket ID and meeting password entered by the login as electronic ticket information. Check whether If the e-mail address does not match the organizer's e-mail address, the processor 11 determines NO in ACT44. The processor 11 invalidates the input of the closing button BTh and returns to the standby state of ACT39 to ACT41.

On the other hand, if the e-mail address matches the organizer's e-mail address, that is, if the organizer's communication terminal 5 has entered the closure button BTh, the processor 11 determines YES in ACT 44 and proceeds to ACT 45. . The processor 11 notifies the closing request to the order server 20 as ACT45. The operation of the order server 20 that receives the notification of the closing request will be described later. Thus, only the host of the meeting can input the closing button BTh of the video call screen SCg. Therefore, the close button BTh may be displayed only on the host's video call screen SCg, and may not be displayed or may be grayed out on the inviter's video call screen SCg.

The processor 11 that has notified the meeting closure request confirms in ACT 46 whether or not the meeting has been permitted to close. When the order server 20 responds with closing permission, the processor 11 determines YES in ACT 46 and proceeds to ACT 47 . The processor 11 disables the video call function between the communication terminals 5 as ACT47. The processor 11 also changes the meeting status of the meeting record RCb from 'ongoing' to 'after closing' as ACT48. Processor 11 ends the meeting holding process.

(Explanation of operation when ordering products)
16 and 22, a description will be given of the operation at the time of product ordering, in which participants order food and drinks to be eaten at a meeting from a restaurant.

FIG. 16 is a flow chart showing the procedure of information processing as the order reception function 203 executed by the processor 21 of the order server 20 that has received the notification of the order request. As described above, the order request is sent from the meeting server 10 to the order server 20 when the participant inputs the food and drink button BTb on the top screen SCa or the food and drink button BTi on the video call screen SCg. . A status indicating that the meeting is being held is added to the order request notified to the order server 20 by inputting the eating and drinking button BTi on the video call screen SCg.

Now, the processor 21 that has received the notification of the order request checks as ACT 61 whether or not the meeting is being held. If the status indicating that the meeting is being held is not added to the notification of the order request, the processor 21 determines NO in ACT61 and proceeds to ACT62. The processor 21 controls such that the meeting login screen SCf (see FIG. 22) is displayed on the display device 51 of the communication terminal 5 to which the eating and drinking button BTb has been input as ACT62. The meeting login screen SCf is a screen displaying a ticket ID input box BXk and a meeting password input box BXm.

A participant who has input the eating and drinking button BTb before the meeting is held has not performed a login operation for the meeting. The participant operates the input device 52 to input the ticket ID of the electronic ticket and the meeting password into the input boxes BXk and BXm of the meeting login screen SCf.

The processor 21 that has controlled the display of the meeting login screen SCf waits for login as ACT63. After confirming that the participant record RCe including the ticket ID entered in the input box BXk and the meeting password entered in the input box BXl is stored in the participant database 233, the processor 21 determines that the login has been performed. recognize. The processor 11 determines YES in ACT63 and proceeds to ACT64.

On the other hand, if a status indicating that the meeting is being held is added to the order request notification, the participant has already performed a login operation from the meeting login screen SCf of FIG. The processor 21 determines YES in ACT61, skips the processing of ACT62 and ACT63, and proceeds to ACT64.

The processor 21 checks whether or not the information of the delivery destination is set in the participant record RCe including the ticket ID and the meeting password entered by the login operation as ACT64. If the delivery destination information is not set, that is, if the data is Null data, the processor 21 determines NO in ACT64 and proceeds to ACT65. As ACT65, the processor 21 controls the display device 51 of the communication terminal 5 to display the delivery destination acceptance screen SCh (see FIG. 22). The delivery destination reception screen SCh is a screen displaying a home delivery button BTk and an in-store button BTl. The home delivery button BTk is a soft button for commanding home delivery of the ordered product. The in-store button BTl is a soft button for commanding to receive the ordered product at the restaurant.

The processor 21 that has controlled the display of the delivery destination reception screen SCh waits for input of the home delivery button BTk or input of the in-store button BTl as ACT66. When home delivery button BTk is input, processor 21 determines YES in ACT66 and proceeds to ACT67. As ACT67, the processor 21 controls the display device 51 of the communication terminal 5 to display the delivery destination input screen SCi (see FIG. 22). The delivery destination input screen SCi is a screen displaying an address input box BXm and a name input box BXn. The participant who has entered the home delivery button BTk enters the address of the delivery destination and the name of the recipient on the delivery destination input screen SCi. When the address and name of the delivery destination are entered on the delivery destination input screen SCi, the processor 21 sets the in-store flag of the participant record RCe to "0" in ACT68, and proceeds to ACT71.

On the other hand, when the in-store button BTl is input, the processor 21 determines NO in ACT66 and proceeds to ACT69. As ACT 69, the processor 21 controls the display device 51 of the communication terminal 5 to display the restaurant selection screen SCj (see FIG. 22). The restaurant selection screen SCj is a screen that displays a list of restaurant names cooperating with the meeting support service as a pull-down menu PDa. The participant selects the corresponding store name from the pull-down menu PDa. When the store name is selected, the processor 21 sets the in-store flag of the participant record RCe to "1" in ACT70, and proceeds to ACT71.

The processor 21 sets the delivery destination information in the participant record RCe as ACT71. That is, when the address and name are input from the delivery destination input screen SCi, the processor 21 sets the address and name as the delivery destination information. When a store name is selected from the restaurant selection screen SCj, the processor 21 sets the store name as the delivery destination information.

The processor 21 creates an order record RCf with the ticket ID, meeting ID and meeting name of the participant record RCe as ACT 72 and stores it in the order database 234 . At this time, the order list of the order record RCf is Null data. The total amount, billing amount and payment amount are "0". Having stored the order record RCf in order database 234, processor 21 proceeds to ACT73.

On the other hand, when the information of the delivery destination is set in the participant record RCe, the processor 21 determines YES in ACT64, skips the processing of ACT65 to ACT72, and proceeds to ACT73.

The processor 21 enables the menu providing function 202 as ACT73. As a result, when the in-store flag of the participant record RCe is "0", that is, when an order is placed by a participant who desires home delivery, the processor 21 displays the address of the delivery destination information on the display device 51 of the communication terminal 5. Control is performed so that the menu item list screen SCk (see FIG. 22) of the restaurant serving as the area is displayed. On the other hand, when the in-store flag of the participant record RCe is "1", that is, when an order is placed by a participant who wishes to eat and drink in the store, the display device 51 of the communication terminal 5 specifies the store name in the delivery destination information. Control is performed so that the restaurant menu item list screen SCk is displayed. The menu item list screen SCk is a screen displaying a list of item names and prices of menu items, check boxes for each item, and an order button BTm. The order button BTm is a soft button for commanding an order for a menu item whose check box is checked. After confirming the menu item list screen SCk, the participant puts a check in the check box of the item name to be ordered, and inputs the order button BTm.

The processor 21 that has controlled the display of the menu item list screen SCk waits for input of the order button BTm as ACT74. When the order button BTm is input, the processor 21 determines YES in ACT74 and proceeds to ACT75.

The processor 21 adds the item name, price, etc. of the ordered menu item to the order list of the order record RCf containing the ticket ID of the participant record RCe as ACT75. Then, the processor 21 calculates the total amount based on the order list and describes the total amount as the total amount and billing amount of the same order record RCf. After that, the processor 21 checks the payment status of the participant record RCe as ACT76, and if it is "no payment", updates it to "with payment".

Processor 21 enables cooking instruction function 204 and delivery instruction function 205 as ACT 77 . Accordingly, the processor 21 refers to the restaurant database 231 and instructs the restaurant to cook the product ordered by the participant. The processor 21 then adds the price of the ordered product to the amount of money deposited in the restaurant database 231 . If the participant wishes to deliver the product, the processor 21 refers to the delivery company database 232 and instructs the delivery company to deliver the ordered product. Then, the processor 21 adds the delivery fee to the payment amount in the delivery company database 232 . Also, the processor 21 adds the delivery charge to the total amount and billed amount of the participant record RCe whose order list was updated in ACT75. With this, the processor 21 ends the information processing when receiving the notification of the order request.

(Explanation of how to leave the meeting)
17 and 23, the operation when a participant leaves a meeting in the middle of the meeting will be described.

FIG. 17 is a flow chart showing a part of the procedure of information processing as the meeting payment function 206 executed by the processor 21 of the order server 20 that has received the notice of the exit request. As described above, the exit request is sent from the meeting server 10 to the order server 20 when the participant presses the exit button BTj on the video call screen SCg.

The processor 21, which has received the notice of the leaving request, confirms in ACT81 whether or not the participant is the inviter. If the classification information of the participant record RCe including the ticket ID input when the participant performs a login operation to participate in the meeting is data for identifying the organizer, the processor 21 determines NO in ACT81. . The processor 21 treats the notification of the leaving request as an error, and terminates this process. In this case, the input of the exit button BTj is invalidated. Thus, the organizer cannot leave the meeting in the middle. If the host has to leave the meeting in the middle of the meeting, the meeting will be temporarily closed. After that, another participant becomes the organizer and applies for a new meeting, and the remaining participants log in to the meeting.

If the category information is data that identifies the invitee, the processor 21 determines YES in ACT81 and proceeds to ACT82. The processor 21 controls such that the payment selection screen SCl (see FIG. 23) is displayed on the display device 51 of the communication terminal 5 to which the exit button BTj has been input as ACT82. The payment selection screen SCl is a screen displaying an individual payment button BTn and a collective payment button BTo. The individual payment button BTn is a soft button for instructing individual payment for the ordered product. The collective payment button BTo is a soft button for commanding collective payment for the ordered products. When a participant who leaves the meeting in the middle of the meeting pays for the product he or she ordered, the participant inputs an individual payment button BTn. If another participant who has not left pays instead, the participant inputs the collective payment button BTo.

The processor 21 that controls the display of the payment selection screen SCl waits for input of the individual payment button or input of the collective payment button BTo as ACT83. When the collective payment button BTo is input, the processor 21 determines NO in ACT83 and proceeds to ACT84. In ACT 84, the processor 21 inquires of the organizer of the meeting whose participants are leaving midway through whether or not to approve the collective settlement. Specifically, the processor 21 searches the participant database 233 with the meeting ID included in the participant record RCe of the participant who has pressed the exit button BTj. The processor 21 detects the ticket ID from the participant record RCe whose category information indicates the organizer in the participant record RCe containing the common meeting ID. The processor 21 transmits data inquiring whether or not to approve the collective settlement to the communication terminal 5 among the participants who are participating in the meeting who have logged in with the ticket ID.

The host who receives the inquiry operates the input device 52 of the communication terminal 5 to input whether or not to approve the collective settlement. The processor 21 checks in ACT85 whether or not the collective settlement has been approved. If the collective settlement is not approved, the processor 21 determines NO in ACT85 and returns to ACT83. In this case, the processor 21 waits for the individual payment button to be input.

On the other hand, if the collective settlement is approved, the processor 21 determines YES in ACT85 and proceeds to ACT86. The processor 21 changes the payment status included in the participant record RCe of the participant who has entered the exit button BTj as ACT86 to "pay later". With the above, the processor 21 ends the information processing when receiving the leaving request.

On the other hand, when the individual payment button BTn is input, the processor 21 determines YES in ACT83 and proceeds to ACT87. The processor 21 confirms in ACT87 whether or not the participant is billed for payment. Specifically, the processor 21 searches the order database 234 with the ticket ID included in the participant record RCe of the participant who has pressed the exit button BTj. The processor 21 confirms whether or not the billed amount of the order record RCf containing the common ticket ID is greater than "0" yen. If the billed amount is "0" yen, there is no bill. The processor 21 determines NO in ACT87 and proceeds to ACT91. The processor 21 changes the payment status included in the participant record RCe of the participant who has entered the exit button BTj as ACT91 to "no payment". With the above, the processor 21 ends the information processing when receiving the leaving request.

On the other hand, if the billed amount is greater than "0" yen, the processor 21 determines that there is a bill. The processor 21 determines YES in ACT87 and proceeds to ACT88. The processor 21 controls to display the first payment method selection screen SCm (see FIG. 23) on the display device 51 of the communication terminal 5 to which the exit button BTj has been input as ACT88. The first payment method selection screen SCm is a screen that displays a code payment button BTp and a credit payment button BTq along with the billed amount (payment amount) of the participant who pays the price by individual payment. The code payment button BTp is a soft button for commanding code payment, which is an example of an online payment method. A credit payment button BTq is a soft button for commanding credit card payment, which is an example of an online payment method. A participant who pays the amount equivalent to the billed amount by code settlement inputs the code settlement button BTp. A participant who pays the amount equivalent to the billed amount by credit card settlement inputs the credit settlement button BTq. The code payment button BTp and the credit payment button BTq are examples of the second operator.

The processor 21 that has controlled the display of the first payment method selection screen SCm waits for the payment method to be selected as ACT89. If either code payment or credit card payment is selected, the processor 21 determines YES in ACT89 and proceeds to ACT90. The processor 21 executes settlement processing as ACT90. That is, when the code payment button BTp is input, the processor 21 executes payment processing for processing the price equivalent to the billed amount by code payment. When the credit settlement button BTq is input, the processor 21 executes settlement processing for processing the charge equivalent to the billed amount by credit card settlement. Since these settlement processes are well-known processes, descriptions thereof are omitted here.

After completing the settlement process, the processor 21 proceeds to ACT91. The processor 21 changes the payment status included in the participant record RCe of the participant who has entered the exit button BTj as ACT91 to "no payment". With the above, the processor 21 ends the information processing when receiving the leaving request.

(Explanation of operation at closing of meeting)
18, 19, 24 and 25, the operation at the closing of the meeting when the host closes the meeting will be described.

FIGS. 18 and 19 are flow charts showing a part of the procedure of information processing as the meeting payment function 206 executed by the processor 21 of the order server 20 which has received the notice of closing request. As described above, the closing request is notified from the meeting server 10 to the order server 20 when the host presses the closing button BTh on the video call screen SCg.

The processor 21 that has received the closing request notice searches the order database 234 with the meeting ID included in the organizer's participant record RCe as ACT 101 . Processor 21 then extracts all order records RCf containing a common meeting ID. The processor 21 confirms whether or not all the payment statuses of the order records RCf extracted as ACT 102 are "no payment". If all payment statuses are "no payment", processor 21 determines NO in ACT 102 and proceeds to ACT 130 in FIG. The processor 21 responds to the meeting server 10 as ACT 130 with permission to close the meeting. Then, the processor 21 ends the processing when receiving the notice of the closing request.

If the payment status of at least one order record RCf is “paid” or “postpaid”, the processor 21 determines NO in ACT102 and proceeds to ACT103. The processor 21 controls so that the checkout screen SCn (see FIG. 24) is displayed on the display device 51 of the communication terminal 5 to which the closing button BTh has been input as ACT103. The billing screen SCn is a screen displaying a billing amount list of the organizer and invitees who participated in the meeting, a breakdown button BTr for the number of participants, a distribution button BTs, a split bill button BTt, and a billing confirmation button BTu. be.

The billing amount list is a list of billing amounts of each order record RCf for the organizer and invitees. In addition, the total billed amount is also displayed on the checkout screen SCn. The breakdown button BTr is a soft button for instructing the breakdown of the billed amount. The apportionment button BTs is a soft button for instructing apportionment of the billed amount. The split bill button BTt is a soft button for instructing split bill evenly. The accounting screen SCn also displays the payment amount per person when splitting the bill evenly. The split bill button BTt is an example of a first operator. The settlement confirmation button BTu is a soft button for instructing settlement of the transaction. Note that the mark "*" in the billed amount list indicates participants whose payment status is "postpaid".
The processor 21 that controls the display of the accounting screen SCn confirms whether or not the breakdown button BTr has been input as ACT104. If the breakdown button BTr has not been input, the processor 21 determines NO in ACT104 and proceeds to ACT105. The processor 21 confirms whether or not the distribution button BTs has been input as ACT105. If the distribution button BTs is not input, the processor 21 determines NO in ACT105 and proceeds to ACT106. As ACT 106, the processor 21 confirms whether or not the split bill button BTt has been input. If the split bill button BTt has not been input, the processor 21 determines NO in ACT 106 and proceeds to ACT 107 . As ACT 107, the processor 21 confirms whether or not the checkout button BTu has been input. If the settlement confirmation button BTu has not been input, the processor 21 determines NO in ACT107 and returns to ACT104. In this way, the processor 21 waits for inputs from the details button BTr, the apportionment button BTs, the split bill button BTt, or the checkout button BTu as ACT104 to ACT107.

In the standby state of ACT104 to ACT107, when the detail button BTr is input, the processor 21 determines YES in ACT104 and proceeds to ACT108. The processor 21 controls the display device 51 of the communication terminal 5 to which the close button BTh has been input as the ACT 108 so that the breakdown of the billed amount corresponding to the inputted breakdown button BTr is displayed. The breakdown includes item, amount and form. A subject is, for example, the item name of a menu item. The amount is the price of the menu item. The price is the price including delivery if the menu item is provided to the participant by home delivery. The form is information indicating whether the menu item was provided to the participant by home delivery or provided to the participant in the store. When the communication terminal 5 instructs to end the breakdown display, the processor 21 returns to ACT 103 . That is, the processor 21 returns the screen displayed on the display device 51 of the communication terminal 5 to the checkout screen SCn.

In the standby state of ACT104 to ACT107, when the sorting button BTs is input, the processor 21 determines YES in ACT105 and proceeds to ACT109. The processor 21 executes distribution processing as ACT 109 . Specifically, the processor 21 controls the display device 51 of the communication terminal 5 to which the distribution button BTs is input so that the distribution screen SCq (see FIG. 25) is displayed. The distribution screen SCq is a screen displaying an order menu list ML including a pull-down menu PDb, a pull-down menu PDc for a lump sum payer, and a distribution confirmation button BTv.

The order menu list ML displays the item name, price, and form of each menu item ordered by the participant in a list. The price is the price including delivery if the menu item is provided to the participant by home delivery. The form is information indicating whether the menu item was provided to the participant by home delivery or provided to the participant in the store. The pull-down menu PDb is provided for each menu item, and can display the participant's identification information so that the payer of the corresponding menu item can be selected from among the participants. The pull-down menu PDb is an example of a second selection section.

The pull-down menu PDc can display the identification information of the participants so that a lump-sum payer who pays the bills generated at the meeting in a lump sum can be selected from among the participants. The pull-down menu PDc is an example of a first selection section.

The distribution confirmation button BTv is a soft button for commanding confirmation of the distribution work. The apportionment work is the work of determining each payer or a lump sum payer for the menu items displayed in the order menu list ML.

A participant who confirms the allocation screen SCq, that is, the organizer performs allocation work. Due to this distribution work, the billing amount included in the order record RCf of the participant is updated. For example, when the payer of the menu item displayed in the order menu list ML is changed from the inviter A to the organizer, the price of the menu item (including the delivery charge in the case of home delivery) is changed to that of the inviter A. It will be deducted from the billed amount and added to the organizer's billed amount. For example, if the organizer is selected as a lump sum payer, the amount billed by the inviter is added to the amount billed by the organizer, and the amount billed by the inviter becomes 0 yen. When the billed amount becomes 0 yen, the payment status included in the order record RCf of the participant is changed to "no payment". After completing the distribution work, the organizer inputs the distribution confirmation button BTv.

When the allocation confirmation button BTv is input, the processor 21 returns to ACT103. That is, the processor 21 returns the screen displayed on the display device 51 of the communication terminal 5 to the checkout screen SCn. At this time, the billed amount in the billed amount list displayed on the accounting screen SCn is the billed amount after the distribution work.

In the standby state of ACT104 to ACT107, when the split bill button BTt is input, the processor 21 determines YES in ACT106 and proceeds to ACT110. The processor 21 executes equal division processing as ACT 110 . Specifically, the processor 21 changes the billed amount of each participant to the equal installment amount. Processor 21 then returns to ACT 103 . At this time, the billed amount in the billed amount list displayed on the billing screen SCn is the equal split amount.

In the waiting state of ACT104 to ACT107, if the payment confirmation button BTu is input, the processor 21 determines YES in ACT107 and proceeds to ACT111. The processor 21 checks in ACT 111 whether or not there is a participant whose payment status is "postpaid" among the participants. If there is a “postpaid” participant, processor 21 determines YES in ACT 111 and returns to ACT 103 .

In this way, even if the payment confirmation button BTu is input, if there is a participant whose payment status is "deferred payment", it is not possible to proceed to subsequent processing. Therefore, the organizer needs to perform the allocation work so that the payment status is "postpaid", that is, the amount billed to the invitee who has approved the withdrawal without payment is 0 yen.

If there is no participant whose payment status is originally "pay later" or if the payment status of "pay later" is changed to "no payment" by performing the allocation work, the processor 21 determines NO in ACT 111. and proceed to ACT 121 in FIG. The processor 21 selects one person as a payer from among the participants whose billing amount is greater than 0 yen. The processor 21 determines in ACT 122 whether or not the in-store flag of the participant record RCe for the payer is set. If the in-store flag is not set, ie if the payer is the participant who ordered the home delivery, processor 21 determines NO in ACT 122 and proceeds to ACT 123 . As ACT 123, the processor 21 controls the display device 51 of the communication terminal 5 used by the payer to display the first payment method selection screen SCm (see FIG. 24). The first payment method selection screen SCm has the same configuration as the first payment method selection screen SCm (see FIG. 23) described in the operation when leaving the meeting.

On the other hand, if the in-store flag is set, that is, if the payer is the participant ordering in-store, processor 21 determines YES in ACT 122 and proceeds to ACT 124 . As ACT 124, the processor 21 controls the display device 51 of the communication terminal 5 used by the payer to display the second payment method selection screen SCp (see FIG. 24). The second payment method selection screen SCp is obtained by adding a cash button BTw to the first payment method selection screen SCm. The cash button BTw is a soft button for instructing settlement by cash payment. Participants in the store can pay in cash. When the participant who is the payer pays the price in cash, he/she inputs the cash button BTw. The cash button BTw is also an example of the second operator.

After processing ACT 123 or ACT 124 , processor 21 proceeds to ACT 125 . Processor 21 checks in ACT 125 if the payer selection is complete. If the payer selection has not been completed, processor 21 determines NO in ACT 125 and returns to ACT 121 . That is, the processor 21 selects the next payer and controls the communication terminal 5 used by the payer to display the first payment method selection screen SCm or the second payment method selection screen SCp.

After executing the processing of ACT 123 or ACT 124 for all participants whose billing amount is greater than 0 yen, the processor 21 determines YES in ACT 125 and proceeds to ACT 126 . Processor 21 waits for any payment method to be selected by the participant. If a payment method is selected, processor 21 determines YES in ACT 126 and proceeds to ACT 127 . The processor 21 executes settlement processing as ACT 127 . That is, when the code payment button BTp is input, the processor 21 executes payment processing for processing the price equivalent to the billed amount by code payment. When the credit settlement button BTq is input, the processor 21 executes settlement processing for processing the charge equivalent to the billed amount by credit card settlement. When the cash button BTw is pressed, the processor 21 executes settlement processing for processing the amount equivalent to the billed amount by cash settlement. Since these settlement processes are well-known processes, descriptions thereof are omitted here.

After completing the settlement process, the processor 21 changes the payment status of the participant record RCe for the participant who has completed the settlement process in ACT 128 to "no payment". The processor 21 then confirms whether or not the payment status of the participant records RCe for all participants has become "no payment". If there are still participants whose payment status is “paid”, processor 21 determines NO in ACT 129 and returns to ACT 126 . Processor 21 awaits payment method selection by the next participant. Then, once a payment method has been selected, processor 21 performs the processing of ACT 127 and ACT 128 in the same manner as previously described.

After confirming that all the payment statuses of the participant records RCe for the participants have become “no payment”, the processor 21 determines YES in ACT 129 and proceeds to ACT 130 . The processor 21 responds to the meeting server 10 as ACT 130 with permission to close the meeting. With this, the processor 21 ends the processing when receiving the notification of the closing request.

Here, the processor 21 of the order server 20 performs processing as the first control unit 31 in the processing of ACT103. The processor 21 performs processing as the determination unit 32 in the processing of ACT104 to ACT110. The processor 21 performs processing as the second control unit 33 in the processing of ACT123 and ACT124. The processor 21 performs processing as the processing unit 34 in the processing of ACT126 and ACT127.

(Action and effect of the meeting support device)
For example, the organizer, invitees A, and invitees B hold an online meeting, and the organizer is charged 2,000 yen, invitee A is charged 1,600 yen, and invitee B is charged 2,100 yen. Assume that the It is assumed that the organizer and the invitee A participate in the meeting from home, and the invitee B participates from a restaurant cooperating with the meeting support service. Under this assumption, if no one has left by the closing time, individual payment, equal split payment, lump sum payment, and apportionment payment are possible for the total billed amount of 5700 yen.

In the case of individual payment, the sponsor inputs the checkout button BTu on the checkout screen SCn. Then, the display device 51 of the communication terminal 5 used by the organizer displays the first payment method selection screen SCm with the billed amount (payment amount) of 2000 yen. The display device 51 of the communication terminal 5 used by the inviter A displays the first payment method selection screen SCm with the billed amount (paid amount) of 1600 yen. On the display device 51 of the communication terminal 5 used by the inviter B, a second payment method selection screen SCp with a billing amount (payment amount) of 2100 yen is displayed. Therefore, the organizer and the invitee A can pay the billed amount by code settlement or credit card settlement. Also, the inviter B can pay the billed amount by code settlement, credit card settlement, or cash settlement.

In the case of equal split payment, the sponsor inputs the split payment button BTt on the checkout screen SCn. Then, since the amounts charged by the organizer, invitees A, and B in the billing amount list are all 1900 yen, the organizer inputs the settlement confirmation button BTu. Then, on the display devices 51 of the communication terminal 5 used by the host and the communication terminal 5 used by the invitee A, the first payment method selection screen SCm with a billing amount (payment amount) of 1900 yen is displayed. be. On the display device 51 of the communication terminal 5 used by the inviter B, a second payment method selection screen SCp with a billing amount (payment amount) of 1900 yen is displayed. Therefore, the organizer and the invitee A can pay the billed amount by code settlement or credit card settlement. Also, the inviter B can pay the billed amount by code settlement, credit card settlement, or cash settlement.

In the case of collective settlement by the organizer, the organizer inputs the distribution button BTs on the checkout screen SCn. Then, the accounting screen SCn is switched to the allocation screen SCq, so the organizer selects the organizer from the pull-down menu PDc and inputs the allocation confirmation button BTv. Then, the distribution screen SCq returns to the accounting screen SCn. At this time, in the billing amount list, the organizer's amount is 5700 yen, and the invitee A and invitee B's amounts are 0 yen. Then, the sponsor inputs the settlement confirmation button BTu. Then, the display device 51 of the communication terminal 5 used by the organizer displays the first payment method selection screen SCm with the billed amount (payment amount) of 5700 yen. The display device 51 of the communication terminal 5 used by the invitee A and invitee B does not display the first payment method selection screen SCm or the second payment method selection screen SCp. Therefore, the sponsor can pay the billed amount for the collective payment by code payment or credit card payment.

For example, when the invitee A leaves the meeting in the middle of the meeting and the organizer bears the payment for the invitee A, the organizer inputs the distribution button BTs on the accounting screen SCn. Then, since the accounting screen SCn is switched to the distribution screen SCq, the organizer selects the product ordered by the invitee A from the order menu list ML, and selects the organizer from the pull-down menu PDb for that product. Select as If the orderers of all the products ordered by the invitee A are changed to the organizer, he/she inputs the allocation confirmation button BTv. Then, the distribution screen SCq returns to the accounting screen SCn. At this time, the billed amount list shows that the organizer's billed amount is 3600 yen, the inviter A's billed amount is 0 yen, and the inviter B's billed amount is 2100 yen. Then, the sponsor inputs the settlement confirmation button BTu. Then, the display device 51 of the communication terminal 5 used by the organizer displays the first payment method selection screen SCm with the billed amount (payment amount) of 3600 yen. On the display device 51 of the communication terminal 5 used by the inviter B, a second payment method selection screen SCp with a billing amount (payment amount) of 2100 yen is displayed. The display device 51 of the communication terminal 5 used by the inviter A does not display the first payment method selection screen SCm. Therefore, the organizer can pay the billed amount by code settlement or credit card settlement. Also, the inviter B can pay the billed amount by code settlement, credit card settlement, or cash settlement.

As described above, according to the present embodiment, individual payment, equal split payment, lump sum payment, or apportionment payment can be carried out with simple operations as payment methods for payments generated in online meetings. Therefore, it is possible to flexibly deal with the diversification of payment methods without requiring a lot of trouble on the part of the participants.

(Modification)
In the above-described embodiment, the meeting server 10 and the order server 20 work together to realize the function of a meeting support device. As another embodiment, the functions of the meeting server 10 and the order server 20 may be realized by one server. In this case, the one server becomes the meeting support device. Also, the functions of the meeting server 10 and the order server 20 may be distributed among three or more servers. For example, the functions as the order server 20 are a first server having a participant registration function 201, a menu provision function 202, an order reception function 203, a cooking instruction function 204, and a delivery instruction function 205, and a meeting settlement function 206. distributed to a second server provided. In that case, the second server can be a meeting support device that includes a first control unit 31 , a determination unit 32 , a second control unit 33 , and a processing unit 34 .

In the above-described embodiment, the case where the inviter's email address is entered at the time of meeting application has been exemplified. Input of the invitee's e-mail address is not limited to when applying for a meeting. After applying for the holding of the meeting by inputting the meeting information such as the name of the meeting, the date and time of the meeting, and the number of participants, for example, the e-mail addresses of the invitees may be entered at a later date. Also, the e-mail address may be input at different times for each invitee. In this case, electronic tickets are distributed appropriately at the timing when the inviter's email address is entered.

In the above-described embodiment, the case where the order server 20 executes the payment processing has been exemplified. The settlement process may be executed by another dedicated server for settlement. In this case, the order server 20 outputs information such as the billed amount, the payment amount, and the payment method as information necessary for settlement to the dedicated server for settlement. This process is the process related to settlement of the payment equivalent to the payment amount executed in the processing unit 34 .

In the above embodiment, payment methods selectable on the first payment method selection screen SCm are code payment and credit card payment, and payment methods selectable on the second payment method selection screen SCp are code payment and credit card payment. Payment was made in cash. The type of payment method is not limited to this. The payment method instructed by the second operator may differ depending on the location of the participant. It should be noted that the first payment method selection screen SCm and the second payment method selection screen SCp do not necessarily have to be distinguished by the location of the participant.

In the above-described embodiment, the communication terminal 5 used by the host is used as the communication terminal 5 in which the charge generated at the meeting is displayed on the display device by the first control unit. Regarding this point, it is not necessarily limited to the communication terminal 5 used by the organizer. For example, the first control unit may control the display device 51 of the communication terminal 5 used by the participant who has pressed the closing button BTh earliest among the participants so that the price generated in the meeting is displayed. .

Additionally, while several embodiments of the invention have been described, these embodiments have been presented by way of example and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and modifications can be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the scope of the invention, and are included in the scope of the invention described in the claims and equivalents thereof.

DESCRIPTION OF SYMBOLS 1...Meeting support system 2...Restaurant system 3...Delivery company system 4...Access point 5...Communication terminal 6...Communication network 10...Meeting server 11, 21...Processor 12, 22...Main memory , 13, 23... Auxiliary storage device 14, 24... Clock 15, 25... Communication interface 16, 26... System transmission line 20... Order server 31... First control unit 32... Decision unit 33... Second 2 control unit 34 processing unit 51 display device 51 input device 53 video call device 101 meeting creation function 102 meeting holding function 131 host database 132 meeting database 201 Participant registration function 202 Menu provision function 203 Order reception function 204 Cooking instruction function 205 Delivery instruction function 206 Meeting payment function 231 Restaurant database 232 Distributor database 233 Participation Person database, 234... Order database.

Claims (6)

a first control unit that performs control so that a display device of a communication terminal used by any one of the participants of the online meeting displays the price generated in the meeting;
a determination unit that determines the payment amount of the price for each of the participants according to the input of the input device in the communication terminal on which the price is displayed;
A second control unit that controls so that the payment amount of the participant is displayed on the display device of the communication terminal used by the participant who has paid the price among the participants;
a processing unit that executes processing related to settlement of a price equivalent to the payment amount of a participant using the communication terminal according to the input of the input device in the communication terminal on which the payment amount is displayed;
A meeting support device comprising: The first control unit controls the display device to display a first operator that instructs to split the bill evenly,
2. The determining unit determines, as the amount to be paid by each of the participants, an amount obtained by dividing the price evenly by the number of the participants when the first operator is input by the input device. meeting support equipment. The first control unit controls the display device to display a first selection unit for selecting a participant who makes a lump sum payment,
3. The meeting support device according to claim 1, wherein said determining unit determines said fee as a payment amount of the participant selected by said first selecting unit. The first control unit controls the display device so that a list of subjects constituting the fee is displayed together with a second selection unit that selects a payer of the subject from among the participants,
4. The meeting support device according to any one of claims 1 to 3, wherein said determining unit determines a payment amount for each participant based on information on payers selected for each subject by said second selecting unit. . The second control unit controls the display device to display a second operator for instructing a payment method,
The processing unit executes processing related to settlement of the price equivalent to the payment amount by the payment method instructed by the input of the second operator,
5. The meeting support device according to any one of claims 1 to 4, wherein the payment method instructed by said second operator differs depending on where said participant is. In a computer with a meeting support device equipped with a communication unit that communicates with a communication terminal used by each of a plurality of participants participating in an online meeting,
A function of controlling the display device of the communication terminal used by one of the participants to display the payment generated at the meeting;
A function of determining the payment amount of the price for each participant according to the input of the input device in the communication terminal on which the price is displayed;
A function to control so that the payment amount of the participant is displayed on the display device of the communication terminal used by the participant who has paid the price, and
A function to settle a payment equivalent to the payment amount of the participant using the communication terminal according to the input of the input device on the communication terminal on which the payment amount is displayed;
A control program for realizing

Images