JP2023075988A - Remote meeting support system - Google Patents

Abstract

To provide a remote meeting support system configured to offer food and drink to participants in a remote meeting timely at host's expense.SOLUTION: A server 2 can communicate with terminals 4 of a host and guests over a public communication network 3. The server 2 includes: address acquisition means which acquires contact addresses for communication of the guests that the host invites to a remote meeting; invitation message transmission means which transmits an invitation message including information on attendance at the remote meeting to the contact addresses of the guests; participant data acquisition means which acquires response data on the attendance from the guests having received the invitation message; and distribution means which transmits gift certificate data having a monetary value to the participants in the remote meeting on the basis of the response data.SELECTED DRAWING: Figure 2

Description

The present invention relates to a remote meeting support system using a public communication network.

In various industrial fields, in order to reduce travel expenses, travel time, etc. required to participate in face-to-face meetings, social gatherings, etc., using public communication networks, which are social infrastructure, So-called remote meetings, in which people hold meetings while they are away from each other, are becoming widespread. Especially in recent years, in order to reduce the risk of droplet infection due to face-to-face contact, there are opportunities to hold remote meetings not only for personal use such as family, friends and colleagues, but also for commercial use such as customers and business partners. It is increasing.

When holding a remote meeting, the host who hosts the remote meeting uses various communication means such as telephone and e-mail to confirm whether or not the invited guests will participate. It is necessary to prepare and send materials to be used at the meeting. A remote meeting support system capable of reducing such a burden on the host is known.

For example, the remote meeting support system disclosed in Patent Document 1 includes a server that can communicate with the terminals of the host and guests through a public communication network. Advance acquisition means, invitation message transmission means for transmitting an invitation message including a invitation to participate in a remote meeting to the contact information of the guest, and participant data acquisition means for acquiring data on whether or not to participate from the guest who received the invitation message have. As a result, the server can send instant messages to the guest's contact information, tally the number of participants in the remote meeting based on the guest's participation data, and notify the host of the tally result. there is

Japanese Patent Application Laid-Open No. 2005-190314 (page 7, FIG. 3)

In a remote meeting support system such as that disclosed in Patent Document 1, it is possible to notify the host of the participants in the remote meeting by obtaining data such as the guest's contact information, the date and time of the meeting, and the title of the meeting from the host. Therefore, the load on the host can be reduced.

By the way, in a face-to-face meeting, food and drink may be provided to the participants, but it is difficult to provide such food and drink in a remote meeting where the participants do not face each other face-to-face. For example, even if you try to use a delivery service, it is necessary to confirm the address, which is the personal information of the participant, as the delivery destination, and to record it as an expense, it is necessary to obtain a receipt for each delivery service. In addition to being extremely troublesome, there is the problem that arrangements cannot be made for areas outside the delivery service. As a result, there is a risk that the host will be left with a bad impression by having the guest bear the cost of food and drink, which may interfere with the smooth operation of the meeting.

The present invention has been made by focusing on such problems, and aims to provide a remote meeting support system capable of timely providing food and drink to participants of a remote meeting at the expense of the organizer. aim.

In order to solve the above problems, the remote meeting support system of the present invention includes:
Equipped with a server that can communicate with the terminals of the host and guests through a public communication network,
The server is
a contact obtaining means for obtaining contact information of a guest whom the host invites to a remote meeting;
invitation message transmission means for transmitting an invitation message including invitation to participate in the remote meeting to the contact information of the guest;
Participant data obtaining means for obtaining participation permission data from the guest who received the invitation message;
and distribution means for transmitting gift certificate data having a monetary value to participants of the remote meeting based on the acceptability data.
According to this feature, the gift certificate data can be provided at an appropriate time before the remote meeting starts, so food and drink for the meeting can be prepared without imposing a financial burden on the guest.

payment processing account data obtaining means for obtaining payment processing account data from the host;
and settlement means for settlement of the total amount of the gift certificate data aggregated based on the acceptability data based on the settlement processing account data.
According to this feature, the settlement process can be performed using the server, so that the total amount of the gift certificate data can be settled accurately.

The server is characterized by executing the processing of the distributing means after finishing the processing of the settlement means.
According to this feature, it is possible to reliably obtain the price for the total amount of the gift certificate data.

The server is characterized in that it executes the processing of the payment means at a predetermined time before the remote meeting, and then executes the processing of the distribution means.
According to this feature, payment can be put on hold until just before the remote meeting starts.

The server is characterized by having issuing means for issuing a receipt based on the settlement amount after the processing of the settlement means is completed.
This feature allows the host to accurately obtain a receipt based on the total value of the gift certificate data.

The server is characterized by managing codes that can be exchanged for monetary value as the gift coupon data.
According to this feature, it is possible to manage whether or not the code has been exchanged for monetary value.

1 is a schematic diagram showing a remote meeting support system in an embodiment; FIG. FIG. 4 is a flow chart showing the flow of processing of the remote meeting support system; It is a flowchart which shows the flow of a meeting information registration process. It is a figure which shows the display part of the information terminal for performing start operation of a meeting information registration process. FIG. 4 is a diagram showing a display section of an information terminal for inputting meeting data; FIG. 4 is a diagram showing a display unit of an information terminal for inputting host data; FIG. 4 is a diagram showing a display unit of an information terminal for inputting guest data; It is a figure which shows the display part of the information terminal for inputting credit card information. It is a figure which shows the registration content of meeting data DB. It is a figure which shows the registration content of user data DB. It is a figure which shows the registration content of settlement processing account data DB. It is a figure which shows the display part of the information terminal for a guest to register propriety data. It is a flowchart which shows the flow of settlement processing. It is a figure which shows the registration content of gift coupon data code DB. FIG. 10 is a flow diagram showing the flow of distribution processing; FIG. 10 is a flowchart showing the flow of receipt issuing processing; FIG. 4 is a diagram showing a display section of an information terminal for inputting receipt information; FIG. 10 is a diagram showing the display section of the information terminal on which a receipt is displayed;

A mode for implementing a remote meeting support system according to the present invention will be described below based on an embodiment.

First, as shown in FIG. 1, the remote meeting support system 1 of the present embodiment, when the host holds a remote meeting, confirms whether or not the invited guests can participate, and totals the results so that the host can Information terminals 4, such as smartphones, personal computers, tablet terminals, etc. owned by many users individually, are provided to reduce the burden on users, via public communication networks 3 consisting of the Internet and telephone networks. , and a server 2 owned by a service provider capable of data communication.

FIG. 1 shows an example of a communication configuration using radio such as wireless Internet. In this embodiment, the information terminals 4, . It may be a dedicated terminal used only for sending and receiving.

The server 2 performs various controls in accordance with the program of the remote meeting support system 1, and a control unit 20 capable of communicating with the information terminals 4, . . . A data DB (database) 21, a user data DB 22 in which data of hosts and guests, that is, users of the remote meeting support system 1 are registered, a payment processing account data DB 23 in which credit card information is registered, and electronic money. and a gift certificate data code DB 24 in which codes of gift certificate data to be given are registered.

In this embodiment, the server 2 will be described as having four types of databases for registering each data: the meeting data DB 21, the user data DB 22, the payment processing account data DB 23, and the gift certificate data code DB 24. For example, the user data DB 22 may be a database in which the contents of the payment processing account data DB 23 are stored together, and the configuration and type of each database may be changed as appropriate.

Hereinafter, the procedure for using the remote meeting support system 1 will be described. In this explanation, the remote meeting support system 1 provides services to users in the form of a website that is open to the public. The service may be provided in the form of an application that is provided, or the service may be provided using a combination of a website and an application. good.

The host (Rimoko Sato (see FIG. 10)) who has decided to hold a remote meeting first inputs a URL (Uniform Resource Locator), uses various search systems, etc. Access the TOP page 50 of the website that provides the services of the meeting support system 1 . In response to this access, the control unit 20 displays the TOP page 50 on the display unit 41 of the information terminal 4 of the host.

Then, when the "Start" icon 50a labeled "Remote meeting registration start" displayed on the TOP page 50 is tapped, the control unit 20 starts remote meeting support as shown in FIG.

As shown in FIG. 2, the control unit 20 of the server 2 executes, as processes for supporting a remote meeting, a meeting information registration process S1 for registering meeting data, contact information for the host and guests, and a remote meeting information registration process S1 for the guests. Invitation message transmission processing S2 for transmitting an e-mail containing invitation to participate in the meeting, participant data acquisition processing S3 for obtaining data for determining whether or not the guest who received the invitation message can participate, payment for gift certificate data payment processing S5 for performing payment, distribution processing S6 for distributing gift certificate data to participants, and receipt issuing processing S8 for issuing a receipt showing payment details. Here, the participants refer to the host of the meeting and those who have decided to participate among the guests invited to the meeting.

As shown in FIG. 3, in the meeting information registration process S1, the control unit 20 registers the title of the remote meeting, the date and time of the remote meeting, and the denomination of the gift coupon data to be distributed to the participants of the remote meeting. Meeting data obtaining processing S11, host data obtaining processing S12 for obtaining host information, guest data obtaining processing S13 for obtaining guest information, payment processing account for obtaining payment processing account data such as card numbers. The data acquisition process S14 is performed in order.

As shown in FIGS. 3 and 5, in the meeting data obtaining process S11, the control section 20 causes the display section 41 of the information terminal 4 of the host to display a meeting data input page 51 (see FIG. 5).

The meeting data input page 51 includes a title input field 51a for inputting the title of the meeting, a date input field 51b for inputting the date of the meeting, a start time input field 51c for inputting the start time, and a denomination of the gift certificate data, that is, the amount of money. A plurality of radio buttons 51d to 51m for selecting a type, a "return" icon 51n for returning to the TOP page 50, and "next" for registering meeting information and proceeding to the next host data acquisition process S12. An icon 51p is displayed.

In the title input field 51a, the date input field 51b, and the start time input field 51c, input means such as a keyboard displayed on the display unit 41 of the information terminal 4, a keyboard of an external device connected to the information terminal 4, voice input, etc. can be used to enter. In this description, "Meeting" is entered in the title input field 51a, "October 21, 2021" is entered in the date input field 51b, and "19:00" is entered in the start time input field 51c.

It should be noted that when inputting data in the date input field 51b, a method such as displaying a calendar and selecting a desired date may be used, and the configuration is not limited to directly inputting numeric values or the like. This is the same for each input field that appears later, including the start time input field 51c.

The denomination of the gift certificate data is 500 yen (550 yen including tax) corresponding to the radio button 51d, 700 yen (770 yen including tax) corresponding to the radio button 51e, 1000 yen (1100 yen including tax) corresponding to the radio button 51f, 1500 yen (1650 yen including tax) corresponding to radio button 51g, 2000 yen (2200 yen including tax) corresponding to radio button 51h, 3000 yen (3300 yen including tax) corresponding to radio button 51j, 10000 yen corresponding to radio button 51k (11000 yen including tax) and 20000 yen (22000 yen including tax) corresponding to the radio button 51m.

The control unit 20 taps the "next" icon 51p in a state in which the title input field 51a, the date input field 51b, and the start time input field 51c are filled and one of the plurality of radio buttons 51d to 51m is selected. Then, a meeting ID "KA768" that is not duplicated with other meeting IDs is issued and registered in the meeting ID column of the meeting data DB 21 (see FIG. 9).

Subsequently, as shown in FIG. 9, the control unit 20 registers the title "meeting" input in the title input field 51a in the meeting title field in the meeting data DB 21, and registers the title "meeting" input in the date input field 51b in the date and time field. Register the date "October 21, 2021" and the time "19:00" entered in the start time input field 51c, and enter the gift certificate data corresponding to the radio button 51d selected in the gift certificate data denomination field. Register denomination information "1". Then, the process proceeds to the next host data acquisition process S12.

Here, the denomination information of the gift coupon data registered in the meeting data DB 21 and the gift coupon data code DB 24, which will be described later, is any number from 1 to 8 corresponding to the denomination of the gift coupon data. For details, "1" is 500 yen, "2" is 700 yen, "3" is 1,000 yen, "4" is 1,500 yen, "5" is 2,000 yen, "6" is 3,000 yen, and "7" is 10,000 yen. Yen, "8" corresponds to 20000 yen.

Note that when the “next” icon 51p is tapped, there is an omission or an error (for example, a past date is entered) in any of the title input field 51a, the date input field 51b, and the start time input field 51c. If there is, it does not move to registration in the meeting data DB 21, displays a message pointing out omissions, errors, etc. in the relevant input fields, and waits until the "next" icon 51p is tapped again. do. This also applies to the subsequent description.

As shown in FIGS. 3 and 6, the control section 20 causes the display section 41 of the information terminal 4 of the host to display the host data input page 52 (see FIG. 6) in the host data acquisition process S12.

The host data input page 52 has a host mail address input field 52a for inputting the mail address of the host, a host name input field 52b for inputting the host name, and a host phonetic input field 52c for inputting the phonetic name of the host. , a "return" icon 52d for returning to the meeting data input page 51, and a "next" icon 52e for registering the host data and proceeding to the next guest data obtaining process S13.

When the "next" icon 52e is tapped with the host mail address input field 52a, the host name input field 52b, and the host phonetic name input field 52c filled, the control unit 20 selects another user ID and another user ID. A unique user ID "qaw123" is issued and registered in the user ID column of the user data DB 22 (see FIG. 10).

Subsequently, as shown in FIG. 10, the control unit 20 registers the host name "Rimoko Sato" entered in the host name input field 52b in the name field in the user data DB 22, and enters the host phonetic name input field in the phonetic field. The host's furigana "Rimoko Sato" entered in 52c is registered, and the host's mail address "rimo@xx.ne.jp" entered in the host mail address input field 52a is registered in the mail address field.

In this embodiment, email is used as a communication means for users such as the host and guests, but the communication means is not limited to this, and may be a message application or the like, and the communication means may be changed as appropriate. Therefore, the contact is not limited to the email address, but may be the account ID of the message application, and may be changed as appropriate according to the contact means used.

Further, as shown in FIG. 9, the control unit 20 registers the host user ID "qaw123" in the user ID column of the meeting data DB 21, and registers "1" indicating the host in the host or guest column. ” is registered. Then, the process proceeds to the next guest data acquisition process S13.

If the user data of the host has been registered and authenticated by, for example, membership registration, the host data obtaining process may be omitted. In such a case, after the meeting data obtaining process S11 ends, as described above, the user ID of the host is registered in the user ID column of the meeting data DB 21, and the host or guest column indicates that the host is " 1”, it is preferable to proceed to the next guest data obtaining process S13.

As shown in FIGS. 3 and 7, the control section 20 causes the display section 41 of the information terminal 4 of the host to display the guest data input page 53 (see FIG. 7) in the guest data acquisition process S13.

The guest data input page 53 includes a guest e-mail address input field 53a for inputting the guest's e-mail address, a guest name input field 53b for inputting the guest's name, and a guest phonetic input field 53c for inputting the guest's name. , an “add” icon 53d for adding and registering guest data, a list 53e of prospective participants that displays host names and email addresses of prospective participants in the remote meeting, guest names and email addresses, and a host A "return" icon 53f for returning to the data input page 52 and a "next" icon 53g for proceeding to the next payment processing account data acquisition processing S14 are displayed.

When the "Add" icon 53d is tapped with the guest mail address entry field 53a, the guest name entry field 53b, and the guest phonetic entry field 53c filled with entries, the control unit 20 duplicates other user IDs. A user ID "sed456" that has not been registered is issued and registered in the user ID column of the user data DB 22 (see FIG. 10).

Subsequently, as shown in FIG. 10, the control unit 20 registers the guest name "Suzuki Ako" entered in the guest name input field 53b in the name field in the user data DB 22, and enters the guest's phonetic input field in the phonetic field. The guest's furigana "Eiko Suzuki" entered in 53c is registered, and the guest's e-mail address "eiko@yy.com" entered in the guest e-mail address entry field 53a is registered in the e-mail address field.

Also, in the meeting data DB 21 (see FIG. 9), the ID column, the meeting title column, and the gift data denomination column in the columns next to the host have the same "KA768", "meeting", and "October 21, 2021 19 :00" and "1" are registered, then the user ID of the guest "sed456" is registered in the user ID column of the meeting data DB 21, and "0" indicating that the guest is a guest is registered in the host or guest column. do.

When these registrations are performed, the control unit 20 enters the information entered in the guest email address input field 53a, the guest name input field 53b, and the guest kana input field 53c in the prospective participant list 53e as shown in FIG. Add Also, the guest mail address input field 53a, the guest name input field 53b, and the guest phonetic input field 53c are left blank so that other guest data can be input. Then, each time a guest is added, the registration described above is repeated.

In this embodiment, as shown in FIGS. 9 and 10, the hosts are Ako Suzuki with user ID "sed456", Bta Takahashi with user ID "rft789", and Three people, Csuke Tanaka, have been invited.

When the "next" icon 53g is tapped with at least one guest added (see FIG. 7), the control unit 20 proceeds to the next payment processing account data acquisition processing S14.

In the guest data acquisition process S13, a list of users whom the host has invited in the past, users who have attended meetings in the past, etc. can be displayed, and guests to be invited can be selected from the list and It may be configured to add to the data DB 21 and prospective participant list 53e.

As shown in FIGS. 3 and 8, the control unit 20 causes the display unit 41 of the host information terminal 4 to display a payment processing account data input page 54 (see FIG. 8) in the payment processing account data obtaining process S14. .

The payment processing account data input page 54 includes a card number input field 54a for inputting the number of the credit card used for payment, an expiration date input field 54b for inputting the expiration date of the credit card, and security of the credit card. A security code entry field 54c for entering a code, a "return" icon 54d for returning to the guest data entry page 53, and a "next" icon 54e for registering payment processing account data and moving to the confirmation page are displayed. It is

In addition, when displaying the payment processing account data input page 54, the control unit 20 refers to the gift coupon data denomination “1 (550 yen including tax)” specified in the meeting data acquisition processing S11, After calculating the maximum number of participants "4" when participating, the maximum billed amount "2200 yen (=550 yen x 4 people)", which is the product of the gift certificate data denomination and the maximum number of participants, is calculated.

Also, based on the meeting date and time registered in the meeting data DB 21, a payment date and time “18:30 on October 21, 2021” at which settlement is made a predetermined time (30 minutes before in this embodiment) is calculated. do.

Then, these information are written together on the payment processing account data input page 54, and the maximum billing amount is settled to the host 30 minutes before the start of the remote meeting if all the invited guests participate. to notify you. As a result, the host can check the maximum billing amount, settlement date and time, etc., and can select a suitable credit card while considering the credit card's available balance, expiration date, etc. . It should be noted that the usage fee of the remote support system and the like may be separately added to the billed amount.

When the "Next" icon 54e is tapped with the card number input field 54a, the expiration date input field 54b, and the security code input field 54c filled, the control unit 20 enters another payment processing account data ID. A payment processing account data ID “ujk345” that does not overlap with the above is issued and registered in the payment processing account data ID column of the payment processing account data DB 23 (see FIG. 11).

Next, register the card number "1111-3333-5555-7777" input in the card number input field 54a in the card number field, and enter the expiration date "yy/mm" input in the expiration date input field 54b in the expiration date field. , and the security code "xyz" entered in the security code input field 54c is registered in the security code field.

In addition, the control unit 20 confirms whether the card number, expiration date, and security code are correct, and whether or not the maximum billing amount can be settled using the credit card indicated by them, via the public communication network 3. Ask the card server. If any of the card number, expiration date, or security code is incorrect, if the maximum billing amount exceeds the credit card limit, or if the payment date and time is outside the expiration date, we will notify you to that effect. Then, the user is prompted to correct the erroneous entry or change the credit card, and waits until the "next" icon 54e is tapped again.

On the other hand, if the limit is not exceeded, and if the card number, expiration date, and security code are all correct, the above registration is completed and the next confirmation page is displayed.

Also, the payment processing account data ID "ujk345" linked to the input credit card information is registered in the payment processing account data ID column of the host in the user data DB 22 (see FIG. 10).

If the account data for payment processing has already been registered, it may be confirmed whether or not the registered credit card may be used for payment. After that, when the host selects to change the credit card, the payment processing account data input page 54 described above may be displayed.

Then, the control unit 20 displays a confirmation page (not shown) for confirming the contents of the meeting data, host data, guest data, and payment processing account data. When the host determines that there is a problem with the contents of the confirmation page, such as an error in writing or the addition of a guest, and taps the "return" icon, the control unit 20 returns to the payment processing account data acquisition processing S14. On the other hand, when the host determines that there is no problem and the end icon is tapped, the control unit 20 terminates the meeting information registration process S1.

After completing the meeting information registration process S1, the control unit 20 executes an invitation message transmission process S2. In the invitation message transmission process S2, user IDs "sed456" and "rft789" whose meeting ID is "KA678" in the meeting data DB 21 (see FIG. 9) and whose host or guest column is "0" indicating that they are guests , "gyh012" is detected, and the mail address registered in the mail address column of the user data DB 22 (see FIG. 10) is detected.

After that, by referring to the information recorded in the meeting data DB 21 for the email address detected in association with the meeting ID "KA678", the remote meeting will be held, the host name, the date and time of the meeting, and the distribution Send an invitation email with an invitation message including the amount of the gift certificate data to be used and the URL leading to the website for registering the participation or non-participation.

FIG. 12 shows an attendance confirmation page 55, which is a website for the invited guests to register their attendance or non-participation. Since the URL for guiding to the attendance confirmation page 55 differs according to the meeting ID and the user ID, the control unit 20 can identify the guest who has accessed and the remote meeting to which the guest is trying to answer. It's like As a result, the guest can omit the input of personal information and the like, so that the use of the remote meeting support system 1 is easy.

In response to whether the guest will attend or not, for example, a participation icon and an absence icon are displayed in the mail, and by selecting one of them, the control unit 20 can indicate whether the guest will participate or not. It is good also as a structure which can reply.

As shown in FIGS. 2 and 12, when the URL described in the invitation mail is tapped, the control unit 20 shifts to the participant data obtaining process S3 for the guest linked to the URL, and The display unit 41 of the information terminal 4 displays an attendance confirmation page 55 (see FIG. 12).

When displaying the attendance confirmation page 55, the control unit 20 refers to the meeting data DB 21 and the user data DB 22, displays the title "meeting" in the meeting title display column 55a of the attendance confirmation page 55, and displays the name of the host. "Rimoko Sato" is displayed in the host name display field 55b, and the date and time of the event "October 21, 2021, 19:00" is displayed in the date and time display field 55c.

In addition, radio buttons 55d and 55e for selecting whether or not to attend, a "back" icon 55f for interrupting input, and a "next" icon 55g for registering the description are displayed.

Based on the date and time registered in the meeting data DB 21, the control unit 20 calculates and displays the reply deadline time "October 21, 2021, 18:30" which is 30 minutes earlier.

The control unit 20 allows the invited guest to tap the "next" icon 55g with the "attend" radio button 55d selected in the corresponding guest availability data column in the meeting data DB 21 (see FIG. 9). Then, 1 is registered as the availability data indicating participation, and 0 is registered as the availability data indicating non-participation when the "next" icon 55g is tapped with the "not attend" radio button 55e selected. .

When changing whether to attend or not to attend, the selection of the radio buttons 55d and 55e can be changed by accessing the attendance confirmation page 55 again through the URL. In addition, for example, if the guest's user data has been registered and authenticated by membership registration, etc., select the relevant remote meeting from the guest's personal page and change whether to attend or not to attend the remote meeting. You may make it

In addition, instead of being able to select only whether to attend or not, for example, attendance (gift certificate data code required), attendance (gift certificate data code not required), absence, etc. The type and number of options can be changed as appropriate. may With such a configuration, even if the guests include a person such as a government employee who wants to avoid receiving the gift certificate data code, it is possible to encourage the guest to participate in the meeting.

As shown in FIG. 2, the control unit 20 executes the participant data obtaining process S3 every time a guest accesses the URL until 30 minutes before the meeting starts. Updatable (step S4: N).

On the other hand, when it is 30 minutes before the start of the remote meeting (step S4: Y), the control unit 20 proceeds to the settlement process S5. At this time, if there is a guest who has not answered whether to attend or not, the control unit 20 registers 0 as the availability data indicating non-participation in the availability data column of the meeting data DB 21 corresponding to the guest. , to the settlement process S5.

As shown in FIG. 13 , in the payment processing S5, the control unit 20 performs gift certificate data denomination reference processing S51 for detecting the gift certificate data denomination registered in the meeting information registration processing S1, host and invited Participant count processing S52 for determining the number of participants who will attend among the guests, billed amount calculation processing S53 for calculating the final billed amount based on the denomination of the gift certificate data and the number of participants, card number, etc. A payment processing account data reference processing S54 for confirming the payment processing account data, and a settlement processing S55 for paying the final billed amount through the credit card company based on the payment processing account data are performed in this order.

As shown in FIG. 13, in the gift coupon data denomination reference process S51, the control unit 20 refers to the gift coupon data denomination column of the data matching the meeting ID "KA678" in the meeting data DB 21 (see FIG. 9). Then, the denomination of the gift card data "1 (550 yen including tax)" for each user ID is detected. In this embodiment, a common meeting ID has a configuration in which a common gift coupon data denomination is registered. good too.

Next, the control unit 20 performs a participant counting process S52. In the participant count process S52, the number of "1" registered in the meeting ID "KA678" and the availability data column in the meeting data DB 21 (see FIG. 9) is counted, and the total value, that is, the number of participants is three. Confirm that Subsequently, in the billed amount calculation process S53, the gift coupon data denomination "1 (550 yen including tax)" is multiplied by the number of participants (3) to obtain the final total billed amount "1650 (=550 x 3)". (hereafter simply referred to as "billing amount"). Then, the control unit 20 registers the billed amount "1650" in the billed amount column corresponding to the payment processing account data ID "ujk345" in the payment processing account data DB 23, and proceeds to the next payment processing account data reference processing S54. .

In the payment processing account data reference processing S54, the control unit 20 detects the user ID “qaw123” having the meeting ID “KA678” and the host or guest column “1” in the meeting data DB 21 (see FIG. 9). , the payment processing account data ID “ujk345” in the user data DB 22 (see FIG. 10) is detected, and the card number “1111-3333-5555-7777” and expiration date “yy /mm" and the security code "xyz".

Next, the control unit 20 performs a settlement process S55. In the settlement process S55, the credit card company is accessed via the public communication network 3, and the host uses the card number, expiration date, and security code that have been entered by the host and detected in the settlement process account data reference process S54 to calculate the amount charged. The payment processing of the final billed amount calculated in the calculation processing S53 is performed. Then, the payment processing S5 is terminated, and the next distribution processing S6 is performed.

As shown in FIG. 14, in the distribution processing S6, the control unit 20 performs an issuance confirmation processing S61 for determining whether or not a gift voucher data code has been issued. If it is determined that there is a user ID (S61: Y), gift certificate data code assignment processing S62 for assigning a gift certificate data code to be issued to this user ID, e-mail address to which this gift certificate data code is sent , and the gift certificate data code transmission processing S64 for sending the gift certificate data code corresponding to the target e-mail address are performed in order, and then the process proceeds to the issuance confirmation processing S61 again. When it is determined in the issuance confirmation process S61 that there is no user ID for which the gift certificate data code has not yet been issued (S61: N), the distribution process S6 is terminated.

As shown in FIG. 14, in the issuance confirmation process S61, the control unit 20 determines that the meeting ID is "KA678", the availability data is "1", and the gift certificate data ID column is registered in the meeting data DB 21 (see FIG. 9). Search for user IDs that have not been made.

Then, in the issuance confirmation process S61, when the meeting ID "KA678", the availability data "1" and the user ID "qaw123" not registered in the gift certificate data ID column are detected (S61: Y), The process proceeds to the next gift coupon data code allocation process S62.

In the gift certificate data code allocation process S62, the gift certificate data code DB 24 (see FIG. 15) is queried for the gift certificate data denomination "1" of the user ID "qaw123" detected in the issuance confirmation process S61.

Here, the gift certificate data code DB 24 will be explained. As shown in FIG. 15, in the gift coupon data code DB 24, management information of gift coupons pre-purchased by the operator of the remote meeting support system 1 is registered. Specifically, a gift certificate data ID for managing the gift certificate data, and a gift certificate for registering the denomination of the gift certificate data linked to the gift certificate data ID as electronic money in the corresponding application/website. A data code, gift coupon data denomination, expiration date of gift coupon data, and issuance permission/prohibition data indicating whether or not the gift certificate has already been issued are registered.

The control unit 20 checks that the corresponding gift coupon data denomination is "1" in the gift coupon data code DB 24, is within the expiration date, and issuance permission/prohibition data 0 indicating that it has not been issued in the issued column. The registered gift coupon data ID "azs" is registered in the gift coupon data ID column of the user ID "qaw123" in the meeting data DB 21 (see FIG. 9). Then, in the gift coupon data code DB 24, 1 is registered as issuance permission/prohibition data indicating that the gift coupon has been issued in the issued column of the gift coupon data ID "azs".

Next, the control unit 20 performs a distribution destination reference process S63 shown in FIG. In the distribution destination reference process S63, the mail address "eiko@yy.com" of the user ID "qaw123" is detected from the user data DB 22 (see FIG. 10). Subsequently, the gift coupon data code "111qaz" registered in the gift coupon data code DB 24 (see FIG. 15) is detected from the gift coupon data ID "azs".

Then, the process proceeds to the gift certificate data code transmission processing S64, and an e-mail containing the gift certificate data code detected in the distribution destination reference processing S63 is transmitted to the mail address detected in the distribution destination reference processing S63. After that, the process returns to the issuance confirmation process S61.

After performing these processes (S61 to S64) in a loop for the number of participants (three rounds in this embodiment), the next (fourth round in this embodiment) issuance confirmation process S61 gift certificate data If it is determined that there is no user ID for which a code has not yet been issued (S61: N), the distribution processing S6 is terminated.

As shown in FIG. 2, when the host requests the receipt issuing process S8 within a predetermined period of time (for example, 30 days) after the distribution process S6 ends (step S7: Y ), the receipt issuing process S8 is started. If the host does not request the receipt issuing process S8 before a predetermined period of time (for example, 30 days) elapses (step S7: N), the remote meeting support is terminated.

As shown in FIG. 16, in the receipt issuing process S8, the control unit 20 sequentially performs a receipt information input process S81 for obtaining information necessary for issuing a receipt, and a receipt creating process S82 for creating and issuing a receipt. After that, end the remote meeting support.

As shown in FIGS. 16 and 17, the control section 20 causes the display section 41 of the information terminal 4 of the host to display the receipt information input page 56 (see FIG. 17) in the receipt information input processing S81.

The control unit 20 refers to the meeting data DB 21 (see FIG. 9), the user data DB 22 (see FIG. 10), and the payment processing account data DB 23 (see FIG. 11), and sets the meeting ID "KA678" to the meeting ID display field 56a. display, display the title of the remote meeting "meeting" in the holding name display column 56b, display the billed amount "1650" in the payment amount display column 56c, and the date and time of the meeting "October 21, 2021 19:00" and The title "meeting" is displayed in the proviso column 56f, the gift coupon data denomination "500 yen", the number of issued cards "3", and the names of the participants are displayed in the detail column 56g.

In the proviso column 56f, the date and time of the event and the title described above are automatically entered, but the host can arbitrarily delete or add them. By checking a check box displayed in the proviso column 56f, the proviso can be displayed on the receipt, and by unchecking the check box, the proviso can be hidden on the receipt. This is the same for the detail column 56g. It should be noted that both the proviso column 56f and the description column 56g may be configured so that they are not automatically entered, and only the host can enter by itself.

The control unit 20 also includes an address input field 56d for inputting the address of the receipt, a subject name input field 56e for inputting the subject name of the receipt, and a "download" icon 56h for shifting to download of the receipt. Then, an "open" icon 56j for displaying the receipt on the display unit 41 of the information terminal 4 of the host and a "close" icon 56k for ending the receipt issuing process S8 are displayed.

By tapping the "open" icon 56j, the control unit 20 proceeds to the receipt creation process S82. In the receipt creation process S82, the information detected in the receipt information input process S81, "Patent Co., Ltd." input in the address input field 56d, "meeting expenses" input in the subject name input field 56e, the proviso field 56f and the details A receipt 57 is created as shown in FIG. 18 based on the contents of the column 56g and displayed on the display section 41 of the information terminal 4 of the host.

Also, the receipt 57 shown in FIG. 18 can be printed on a paper medium by tapping the "print" icon 57a. Note that the "print" icon 57a may be omitted, and printing may be performed using various print functions of the information terminal 4 of the host.

Also, when the "download" icon 56h is tapped, the data of the receipt 57 is transmitted to the information terminal 4 of the host. On the other hand, if the "close" icon 56k is tapped, the receipt issuing process S8 is terminated.

As described above, in the remote meeting support system 1 of the present embodiment, the server 2 includes contact obtaining means mainly composed of the control unit 20 and the user data DB 22, the control unit 20, the meeting data DB 21, Invitation message sending means mainly composed of user data DB 22; participant data acquisition means mainly composed of control unit 20 and meeting data DB 21; control unit 20, meeting data DB 21, user data DB 22 , and a distribution means mainly composed of a gift certificate data code DB 24, guest data acquisition processing S13 by contact information acquisition means, invitation message transmission processing S2 by invitation message transmission means, and participant data acquisition means Participant data acquisition processing S3 by the distribution means and distribution processing S6 by the distribution means can be executed.

As a result, the remote meeting support system 1 can provide the gift certificate data code to each participant 30 minutes before the start of the remote meeting. Be able to prepare things.

In addition, the server 2 includes means for obtaining settlement processing account data mainly composed of a control unit 20, a meeting data DB 21, a user data DB 22, and a settlement processing account data DB 23; A settlement means mainly composed of a DB 22 and a settlement process account data DB 23, and can execute a settlement process account data acquisition process S14 by means of settlement process account data acquisition means and a settlement process S5 by the settlement means. It's becoming

As a result, in the remote meeting support system 1, the settlement process S5 can be performed using the server 2, so that the total amount of the gift certificate data can be settled accurately.

In addition, since the server 2 executes the distribution process S6 after completing the payment process S5, it is possible to reliably obtain the amount required for the total amount of the gift certificate data.

In addition, the server 2 executes the distribution process S6 after executing the payment process S5 30 minutes before the remote meeting, so that the payment can be put on hold until just before the remote meeting starts.

In addition, since the server 2 has issuing means mainly composed of the meeting data DB 21, the user data DB 22, and the settlement processing account data DB 23, the host accurately obtains the receipt 57 based on the total amount of the gift coupon data. be able to.

In addition, since the server 2 uses the gift certificate data code DB 24 to manage codes that can be exchanged for monetary value as gift certificate data, the code can be exchanged for monetary value by, for example, inquiring the issuer of the code. It is possible to manage whether it has been done or not.

In addition, since the server 2 can issue a single receipt 57 for the settlement amount of the remote meeting, it is possible to omit the trouble of obtaining a receipt for each guest, for example. For this reason, it is easy to settle as an expense.

Although the embodiments of the present invention have been described above with reference to the drawings, the specific configuration is not limited to these embodiments, and any changes or additions within the scope of the present invention are included in the present invention. be

For example, in the above embodiment, the gift coupon data is described as being electronic money, but it is not limited to this, and may be, for example, the data of an exchange coupon that can be exchanged for a product by presenting it at a store, such as a discount. It may be a coupon that allows you to receive various services, or it may be changed as appropriate as long as it has monetary value.

Further, in the above-described embodiment, the answer deadline time and the settlement time are both set to 30 minutes before. However, the present invention is not limited to this. good too.

Also, in the above-described embodiment, the distribution processing S6 is performed after the payment processing S5 is completed.

Also, in the above-described embodiment, the description has been given of the configuration in which credit card information is registered as account data for settlement processing, but the present invention is not limited to this, and the remote meeting support system 1 may be made to make payment by proxy, such as electronic money owned by the host. Any possible payment means may be changed as appropriate.

1 remote meeting support system 2 server 3 public communication network 4 information terminal 20 control unit (contact acquisition means, invitation message transmission means, participant data acquisition means, distribution means, payment processing account data acquisition means, payment means)
21 meeting data DB (invitation message sending means, participant data obtaining means, distribution means, payment processing account data obtaining means, payment means)
22 User data DB (Means for obtaining contact information, Means for sending invitation message, Means for distributing, Means for obtaining account data for payment processing, Payment method)
23 Payment processing account data DB (means for obtaining payment processing account data, payment method)
24 Gift certificate data code DB (distribution means)

Claims (6)

Equipped with a server that can communicate with the terminals of the host and guests through a public communication network,
The server is
a contact obtaining means for obtaining contact information of a guest whom the host invites to a remote meeting;
invitation message transmission means for transmitting an invitation message including invitation to participate in the remote meeting to the contact information of the guest;
Participant data obtaining means for obtaining participation permission data from the guest who received the invitation message;
and distribution means for transmitting gift coupon data having a monetary value to participants of the remote meeting based on the acceptance/rejection data. payment processing account data obtaining means for obtaining payment processing account data from the host;
2. The remote meeting support system according to claim 1, further comprising settlement means for settlement of the total amount of said gift certificate data aggregated based on said acceptance/rejection data based on said settlement processing account data. 3. The remote meeting support system according to claim 2, wherein the server executes the processing of the distributing means after completing the processing of the settlement means. 4. The remote server according to claim 2 or 3, wherein the server executes the processing of the payment means at a predetermined time before the time of the remote meeting, and then executes the processing of the distributing means. Meeting support system. 5. The remote meeting support system according to any one of claims 2 to 4, wherein said server has issuing means for issuing a receipt based on the settlement amount after the processing of said settlement means is completed. 6. The remote meeting support system according to any one of claims 1 to 5, wherein said server manages a code that can be exchanged for monetary value as said gift coupon data.

Images