WO2023223516A1

WO2023223516A1 - Meeting assistance method, meeting assistance device, and program

Info

Publication number: WO2023223516A1
Application number: PCT/JP2022/020884
Authority: WO
Inventors: 智樹渡部; 耀柳田; 慈郎長尾
Original assignee: 日本電信電話株式会社
Priority date: 2022-05-19
Filing date: 2022-05-19
Publication date: 2023-11-23

Abstract

This meeting assistance method facilitates the start of a meeting by using a computer to execute: a determination procedure for determining whether second information having a prescribed commonality with first information pertaining to a meeting, the start of which is within a prescribed amount of time, exists in information pertaining to any previously held meeting; and an aroma generation procedure for executing a process for generating, prior to the start of a meeting associated with the first information, the same aroma as an aroma generated during a meeting associated with the second information, when the second information exists.

Description

Meeting support method, meeting support device and program

The present invention relates to a meeting support method, a meeting support device, and a program.

At meetings such as regular meetings, discussions may begin based on the content discussed at the previous meeting. Participants in such a meeting are required to recall the situation of the previous meeting before the meeting begins, in order to facilitate the upcoming meeting. In particular, remote work has become popular in recent years, and opportunities for online meetings have increased. In online meetings, it is more difficult for participants to remember the circumstances of the previous meeting than in face-to-face meetings.

Conventionally, a technology has been disclosed that supports remembering the situation of the previous meeting by displaying the situation of the previous meeting in text and illustrations (Patent Document 1).

Japanese Patent Application Publication No. 2017-004270

However, the technology disclosed in Patent Document 1 requires time and effort for each participant to view text and illustrations. Furthermore, since the display of text and illustrations is not linked to the meeting time, it is difficult to notify each participant that the meeting time is approaching. Therefore, if it is not possible to remember what the meeting is about and what the situation is before the meeting starts, each meeting participant has to retrace their memories, making it difficult to start the meeting smoothly.

The present invention has been made in view of the above points, and an object of the present invention is to facilitate the start of a meeting.

Therefore, in order to solve the above-mentioned problems, the meeting support method provides a meeting support method in which second information that has a predetermined commonality with first information about a meeting whose start time is approaching within a predetermined time is a meeting that has already been implemented. a determination procedure for determining whether or not the second information is present in the information regarding the meeting; and if the second information is present, the first information contains the same odor as the odor generated at the meeting related to the second information; A computer executes an odor generation procedure for executing a process for generating an odor before the start of a meeting related to the odor generation procedure.

It is possible to start the meeting smoothly.

FIG. 1 is a diagram illustrating an example configuration of a meeting support system in a first embodiment. It is a diagram showing an example of the hardware configuration of the user terminal 10 in the first embodiment. It is a diagram showing an example of the functional configuration of the user terminal 10 in the first embodiment. 3 is a flowchart for explaining an example of a processing procedure executed by the registration unit 11. FIG. 5 is a diagram illustrating an example of transition of screens displayed by the registration unit 11. FIG. 3 is a diagram showing an example of the configuration of a storage unit 13. FIG. 3 is a flowchart for explaining an example of a processing procedure executed by the execution unit 12 in the first embodiment. It is a flowchart for explaining an example of a processing procedure executed by the odor generating device 109. 7 is a flowchart for explaining an example of a processing procedure executed by the execution unit 12 in the second embodiment.

The first embodiment will be described below based on the drawings. In this embodiment, a scent is associated with each series of meetings (hereinafter simply referred to as "series"). Here, the series is a classification unit (group) that is defined or distinguished by the name of the meeting (agenda, etc.) and participating members. For example, meetings that have the same meeting name and the same participating members are considered to be meetings of the same series. Alternatively, meetings with a large number of matching character strings (or matching percentage) of meeting names or a large matching number (or matching percentage) of participating members (those that are equal to or greater than a threshold) may be considered to be the same series.

Therefore, for example, meetings that are regularly held with the same members are associated with the same scent. When the start of a meeting approaches, a smell associated with the meeting is generated before the start of the meeting. Therefore, each participant in the meeting can know that the start of the meeting is approaching. Furthermore, the connection between smell and memory has been recognized both academically and empirically. Therefore, each participant can grasp the contents of previous meetings (in the same series as this meeting) that are related to the current meeting (what the meeting was about and what the situation was about) based on the memory associated with the smell. There is a possibility that it can be done. As a result, a smooth start of the meeting can be expected.

FIG. 1 is a diagram showing a configuration example of a meeting support system in the first embodiment. In FIG. 1, a plurality of user terminals 10 connect to a meeting server 20 via a network such as the Internet.

The user terminal 10 is a terminal such as a PC (Personal Computer), a tablet terminal, or a smartphone used by participants in an online meeting (online meeting) such as a web meeting or a video conference.

The meeting server 20 is one or more computers that manage information related to online meetings and relay video and audio of online meetings.

FIG. 2 is a diagram showing an example of the hardware configuration of the user terminal 10 in the first embodiment. The user terminal 10 in FIG. 2 includes a drive device 100, an auxiliary storage device 102, a memory device 103, a CPU 104, an interface device 105, a display device 106, an input device 107, a clock 108, and an odor generator, which are connected to each other via a bus B. It has a device 109 and the like.

A program that implements processing at the user terminal 10 is provided by a recording medium 101 such as a CD-ROM. When the recording medium 101 storing the program is set in the drive device 100, the program is installed from the recording medium 101 to the auxiliary storage device 102 via the drive device 100. However, the program does not necessarily need to be installed from the recording medium 101, and may be downloaded from another computer via a network. The auxiliary storage device 102 stores installed programs as well as necessary files, data, and the like.

The memory device 103 reads and stores the program from the auxiliary storage device 102 when there is an instruction to start the program. The CPU 104 implements functions related to the user terminal 10 according to programs stored in the memory device 103. The interface device 105 is used as an interface for connecting to a network. The display device 106 displays a GUI (Graphical User Interface) or the like based on a program. The input device 107 includes a keyboard, a mouse, and the like, and is used to input various operation instructions.

The clock 108 is a so-called clock, and is a device that indicates the time. The clock 108 of each user terminal 10 indicates the same time as the clock 108 of the other user terminals 10. Therefore, even if each participant belongs to a different time zone, each participant's schedule is managed at the same time. The odor generating device 109 is a device that can generate two or more types of odors with one or more odor densities. For example, an olfactory display may be utilized as the odor generating device 109.

FIG. 3 is a diagram showing an example of the functional configuration of the user terminal 10 in the first embodiment. In FIG. 3, the user terminal 10 includes a registration section 11 and an execution section 12. Each of these units is realized by one or more programs installed on the user terminal 10 causing the CPU 104 to execute the processing. The user terminal 10 also utilizes the storage unit 13. The storage unit 13 can be realized using, for example, the auxiliary storage device 102 or a storage device connectable to the user terminal 10 via a network. Note that each part may be realized by a dedicated device connected to the user terminal 10 via a communication line. In this case, the device may include a clock 108 and an odor generating device 109.

Hereinafter, the processing procedure executed by the user terminal 10 will be explained. FIG. 4 is a flowchart for explaining an example of a processing procedure executed by the registration unit 11.

In step S101, the registration unit 11 receives from the user input of schedule information (hereinafter referred to as "meeting schedule") for a meeting whose schedule is to be registered (hereinafter referred to as "target meeting"). The registration unit 11 may accept input from the user via, for example, a screen displayed on the display device 106 by the registration unit 11.

FIG. 5 is a diagram showing an example of transition of the screen displayed by the registration unit 11. In step S101, the registration unit 11 receives input of a meeting schedule via the meeting schedule input screen 510, for example. The meeting schedule includes parameters such as name, members, scheduled start date and time, and scheduled end date and time. The name is the name of the meeting. Members is a list of names of participants who are expected to (are required to) participate in the meeting. The scheduled start date and time is the scheduled start date and time of the meeting. The scheduled end date and time is the scheduled end date and time of the meeting.

Subsequently, the registration unit 11 determines whether the series of the target meeting is new (S102). That is, it is determined whether a meeting schedule of the same series as the target meeting has been registered in the past. For example, in response to pressing the button 511 on the meeting schedule input screen 510 in FIG. 5, the registration unit 11 displays the series inquiry screen 520 on the display device 106, and inquires of the user whether the series of the target meeting is new. It's okay. Alternatively, the registration unit 11 may refer to the storage unit 13 and automatically determine whether the series of target meetings is new.

FIG. 6 is a diagram showing an example of the configuration of the storage unit 13. For each meeting for which a meeting schedule has already been registered, the storage unit 13 stores information including the meeting schedule (name, members, scheduled start date and time, and scheduled end date and time), odor type, odor intensity, implementation results, etc. (hereinafter referred to as , referred to as "meeting information".9) are stored.

The odor type and odor intensity are odor-related parameters associated with the meeting. Odor types are types of odors, and the differences are differences in the odors themselves. In this embodiment, the types of odors correspond to the series on a one-to-one basis. On the other hand, odor intensity is the intensity (intensity) of an odor. The intensity of the odor corresponds to the type of meeting (form or style, etc.). The type of meeting is distinguished, for example, by whether it is formal or frank. In this embodiment, an example is shown in which an operational rule is applied in which the smell of a formal meeting is made stronger and the smell of a frank meeting is made lighter. However, the opposite operation rule may be adopted, or odor intensity may be assigned to classifications from different viewpoints. The implementation record is information indicating whether or not there is a record of conducting meetings. The value of the implementation record of a meeting with a record of implementation is "Yes". The value of the implementation performance of a meeting that has no implementation performance (to be held from now on) is "Not yet".

The registration unit 11 determines that the series of the target meeting is new if there is no meeting with a name and members that have a predetermined commonality with the name and members of the target meeting (hereinafter referred to as "same series meeting"), If there is a meeting of the same series, it is determined that the series of the target meeting is not new. Note that the same-series meeting does not need to have already been held, and the scheduled start date and time may be after the target meeting.

Note that having a predetermined commonality means, for example, that names and members completely match. Alternatively, even if it is not an exact match, if the number of character string matches (or match percentage) of the meeting name or the number of matches (or match percentage) of participants is large (more than a threshold), the predetermined commonality is determined. It may be determined that the

If the series of target meetings is new (YES in S102), the registration unit 11 acquires the type and intensity of the scent associated with the target meeting from the user (S103). In this case, the registration unit 11 may display a scent selection screen 530 on the display device 106, as shown in FIG. The odor selection screen 530 includes options corresponding to odor type candidates and odor intensity candidates, and is a screen for allowing the user to select the odor type and odor intensity to be associated with the target meeting. . Options corresponding to the type and intensity of odor may be stored in the storage unit 13. Figure 5 includes options corresponding to all odor types, and types that are already used in other series are marked with the character string "(in use)" and cannot be selected. Although an example is shown in which A, C, and E are selectable, only options for types that are not used in any existing series may be displayed. For odor type, the user selects one of the selectable odor types, and for odor intensity, if the target meeting is a formal meeting, the user selects "strong", and then If is Frank, select "Light". The registration unit 11 acquires the selection results on the odor selection screen 530.

Note that whether or not each odor type is in use can be specified by referring to the storage unit 13.

On the other hand, if the series of the target meeting is not new (NO in S102), the registration unit 11 acquires the type and intensity of the odor stored in the storage unit 13 for the same series of meetings (S104).

Following step S103 or S104, the registration unit 11 registers meeting information including the meeting schedule received in step S101 and the odor type and intensity acquired in step S103 or S104 in the storage unit 13 (S105). At this time, the registration unit 11 sets the value of the implementation record of the meeting information to "not yet".

For example, if regular work report meeting 1 is assigned smell A, report session 2 is assigned smell B, regular online drinking party for person in charge A is assigned smell C, and online chat during lunch for person in charge D is assigned smell D. Debriefing session 1 and debriefing session 2 have a strong odor, while online drinking parties and online chats can be set to have a weak odor. To prevent odor types from overlapping, access the storage unit 13 to obtain combinations of odor types and intensities that have already been applied in other meetings and make them unselectable, or select any combination first. The storage unit 13 may be accessed later to check whether the combination has been applied in another meeting, and caution may be given to combinations that have already been used.

Next, the processing procedure executed by the execution unit 12 will be explained. In addition, the meaning of each symbol in the explanation of the subsequent processing procedure is as follows.
TC: Current time T': A value that determines how long before the scheduled meeting start date and time the odor generation should start. For example, when starting 10 minutes ago, T'=0:10
MTG: Meeting information of a meeting whose scheduled start date and time is after the TC and has the smallest difference between the scheduled start date and time and the TC, and which is not currently in progress TS: Scheduled start date and time of the MTG TE: Scheduled end date and time of the MTG TM: Scheduled start The MTG start time allowed for the date and time TS (the time indicated by TM is when waiting for the start of the MTG, and if the waiting time exceeds the TM, the MTG is considered not to be held)
Allowable time between the scheduled start date and time TS to determine the start of MTG (even if this time deviates, it will be judged as a start)
FK: MTG odor type FL: MTG odor intensity MS: MTG-related meeting status (whether it is being held or not)
O: Value indicating that the event is being held FIG. 7 is a flowchart for explaining an example of the processing procedure executed by the execution unit 12 in the first embodiment.

In step S201, the execution unit 12 obtains the current time TC from the clock 108. Next, the execution unit 12 generates meeting information (MTG ) is acquired (S202). Note that whether or not each meeting is being held can be determined by, for example, inquiring the meeting server 20.

Subsequently, the execution unit 12 determines whether the time obtained by adding T' to the current time TC exceeds the scheduled start date and time TS of the MTG (whether the start timing of the target meeting approaches within T') ( S203). That is, it is determined whether or not the start time for generating an odor regarding the target meeting has passed.

If the time obtained by adding T' to the current time TC is before TS (NO in S203), the process returns to step S201, and the execution unit 12 repeats step S201. In this case, the execution unit 12 may execute step S201 and subsequent steps after waiting for a certain period of time.

If the time obtained by adding T' to the current time TC exceeds TS (that is, if the start time at which TC generates a smell has passed) (YES in S203), the execution unit 12 has the same series as MTG. , it is determined with reference to the storage unit 13 whether or not there are other meetings that have been held (S204). That is, it is determined whether or not there is meeting information that has the same affiliation as MTG and whose implementation record is "Yes."

If there is a corresponding meeting (YES in S204), the execution unit 12 outputs the MTG odor type FK and odor intensity FL and an instruction to start odor generation to the odor generation device 109, thereby generating FK and FL. A process for generating a related odor is executed (S205). The odor generating device 109 generates FK odor at FL intensity in response to the start instruction.

Next, the execution unit 12 waits until the current time TC passes the scheduled start date and time TS of the MTG (NO in S206 and S207). When the current time TC passes the scheduled start date and time TS of the MTG (YES in S207), the execution unit 12 acquires the status MS (whether or not it is being held) of the target meeting from the meeting server 20 (S208). For example, the MS of the target meeting can be obtained by inquiring the meeting server 20 based on the name of the target meeting.

Next, the execution unit 12 determines whether the status MS of the target meeting is O (currently being held) (S209). If the MS is not being held (NO in S209), the execution unit 12 determines whether the current time TC has exceeded the sum of the scheduled start date and time TS of the MTG and TM (S210). If the current time TC has not passed the date and time obtained by adding TM to the scheduled start date and time TS of MTG (NO in S210), steps S208 and subsequent steps are repeated. In this process, if the status MS of the target meeting becomes in progress (YES in S210), the execution unit 12 updates the MTG implementation record to "Yes" (S211). When the current time TC has passed the date and time obtained by adding TM to the scheduled start date and time TS of MTG (YES in S210), the execution unit 12 outputs an instruction to stop the odor generation to the odor generation device 109 (S212).

On the other hand, if there is no other meeting that has the same affiliation as MTG and has a record of implementation (NO in S204), the execution unit 12 waits until the current time TC passes the scheduled start date and time TS of MTG (S213, NO at S214). When the current time TC passes the scheduled start date and time TS of the MTG (YES in S214), the execution unit 12 acquires the status MS (whether or not it is being held) of the target meeting from the meeting server 20 (S215).

Next, the execution unit 12 determines whether the status MS of the target meeting is O (currently being held) (S216). If the MS is not being held (NO in S216), the execution unit 12 determines whether the current time TC has passed the date and time obtained by adding TM to the scheduled start date and time TS of the MTG (S217). If the current time TC has not passed the date and time obtained by adding TM to the scheduled start date and time TS of MTG (NO in S217), steps S215 and subsequent steps are repeated. In this process, if the status MS of the target meeting becomes in progress (YES in S216), the execution unit 12 updates the MTG implementation record to "Yes" (S218). Subsequently, the execution unit 12 outputs the MTG odor type FK and odor intensity FL, and an instruction to start odor generation to the odor generation device 109 (S219). The odor generating device 109 generates FK odor at FL intensity in response to the start instruction. That is, if there is no other meeting that is in the same series as MTG and has a track record of implementation, the odor starts to occur while the target meeting is being held (after it has started). By doing so, participants in the target meeting can remember the content of the target meeting in association with the smell. Subsequently, the execution unit 12 waits until the target meeting status MS is no longer in progress (YES in S220 and S221). When the target meeting status MS is no longer in progress (NO in S221), the execution unit 12 outputs an instruction to stop odor generation to the odor generation device 109 (S222).

Note that if the current time TC passes the date and time obtained by adding TM to the scheduled start date and time TS of the MTG without the status MS of the target meeting becoming O (in progress) (YES in S217), steps S218 to S222 are not executed. Then, the process of FIG. 7 ends.

FIG. 8 is a flowchart for explaining an example of a processing procedure executed by the odor generating device 109.

In step S301, the odor generating device 109 inputs an instruction from the execution unit 12. The instruction is an instruction to start generating odor output from the execution unit 12 in step S205 or S219 of FIG. 7, or an instruction to stop generation of odor output from the execution unit 12 in step S212 or S222.

If the instruction is an instruction to start generating an odor (YES in S302), the odor generating device 109 generates the type of odor specified in the instruction at the density specified in the instruction (S303). On the other hand, if the instruction is an instruction to generate an odor (YES in S302), the odor generation device 109 stops generating odor (S304).

It is assumed that the odor generating device 109 does not generate different odors at the same time. In addition, the intensity of the odor can be changed by changing the amount of odor generated. For example, when it is light, it ejects once from the output part, and when it is dark, it ejects three times in a row from the output part. In addition, in the case of high concentration, it may be possible to eject once from three output parts at the same time.

Next, the above processing procedure will be explained based on a specific example.

[Specific example 1]
<Processing procedure of registration unit 11 (FIG. 4)>
In step S101, the registration unit 11 inputs the following meeting schedule.
・Name: M1
・Scheduled start date and time: 2022/01/12 10:00
・Scheduled end date and time: 2022/01/12 11:00
・Members: u1, u2, u3
It is assumed that the series of target meetings is new (YES in S102).

In step S103, when the registration unit 11 presents F1, F2, F3, and F4 as odor type options and L1 and L2 as odor intensity options, the user selects F1 and L1. .

In step S104, the registration unit 11, as meeting information R1,
・Name: M1
・Scheduled start date and time: 2022/01/12 10:00
・Scheduled end date and time: 2022/01/12 11:00
・Participants: u1, u2, u3
・Smell type: F1
・Smell intensity: L1
-Register implementation record: Not yet in the storage unit 13 (S105).

<Processing procedure of execution unit 12 (FIG. 7)>
Assume that T'0=0:10.

In step S201, the execution unit 12 obtains TC=2022/01/12 9:45.

In this case, the execution unit 12 obtains R1 as the MTG in step S202.

Since TC+T'<TS (YES in S203), the execution unit 12 returns to step S201 (that is, no odor generation start instruction is output).

The execution unit 12 executes step S201 again and obtains TC=2022/01/12 9:51.

In this case as well, the execution unit 12 obtains R1 as the MTG in step S202.

Since TC+T'>TS (NO in S203), the execution unit 12 determines whether there is meeting information in the same series as MTG and whose implementation record is "Yes" (S204).

Since there is no corresponding meeting information (NO in S204), the execution unit 12 obtains TC=2022/01/12 10:01 (S213).

Since TS<TC (YES in S214), the execution unit 12 acquires the MS from the meeting server 20 (S215).

Here, MS=O (YES in S216). The execution unit 12 updates the value of the implementation record of the MTG (R1 here) to "Yes" (S218), specifies F1 and L1, and outputs an instruction to start generating odor to the odor generation device 109 (S218). S219). ――――――(※)
Next, the execution unit 12 repeatedly acquires the MS (S220), and when it is no longer able to acquire O indicating that a meeting is in progress (NO in S221), it outputs an instruction to stop the odor generation to the odor generation device 109 (S222). ). The odor generating device 109 stops generating odor.

In this way, if the MTG series is new, the smell (F1, L1) specified for MTG will be generated during the meeting (after the meeting starts), but if the smell is generated before the meeting starts. will not be carried out.

[Specific example 2]
It is assumed that specific example 2 is executed after specific example 1.

<Processing procedure of registration unit 11 (Figure 4)>
The registration unit 11 inputs the following meeting schedule (S101).
・Name: M1
・Scheduled start date and time: 2022/01/19 10:00
・Scheduled end date and time: 2022/01/19 11:00
・Members: u1, u2, u3
The series of target meetings is the same as R1 registered in specific example 1, so it is not new (NO in S102).

Therefore, the registration unit 11 sets F1 and L1 of R1, which has the same series as the target meeting, as the type of odor and the intensity of the odor of the target meeting.
・Name: M1
・Scheduled start date and time: 2022/01/19 10:00
・Scheduled end date and time: 2022/01/19 11:00
・Participants: u1, u2, u3
・Smell type: F1
・Smell intensity: L1
・Meeting information including implementation record: Not yet registered as R2 in the storage unit 13 (S105).

<Processing procedure of execution unit 12 (FIG. 7)>
In step S201, the execution unit 12 obtains TC=2022/01/19 9:45.

In this case, the execution unit 12 obtains R2 as the MTG in step S202.

The execution unit 12 executes step S201 again and obtains TC=2022/01/19 9:51.

In this case as well, the execution unit 12 obtains R2 as the MTG in step S202.

Since TC+T'>TS (NO in S203), the execution unit 12 determines whether there is meeting information in the same series as MTG and with a record of "Yes" (S204).

Since R1 is applicable (YES in S204), the execution unit 12 specifies F1 and L1 set in R2 and outputs an instruction to start generating odor to the odor generation device 109 (S205).

Subsequently, the execution unit 12 obtains TC=2022/01/19 9:52 (S206). Since TC<TS (NO in S207), the execution unit 12 obtains TC=2022/01/19 10:01 again (S206).

Since TS<TC (YES in S207), the execution unit 12 acquires the MS from the meeting server 20 (S208).

Here, MS=O (YES in S209). The execution unit 12 updates the value of the actual performance of MTG (R2 here) to "Yes" (S211).

Next, the execution unit 12 repeatedly acquires the MS (S208), and when it is no longer able to acquire O indicating that the meeting is in progress (NO in S209), it outputs an instruction to stop the odor generation to the odor generation device 109 (S212). ). The odor generating device 109 stops generating odor.

In this way, if the MTG series is not new, the series is the same as MTG, and the type and intensity of the odor that occurred during a meeting that was held in the past occurs before the start of the meeting related to MTG. .

As described above, according to the first embodiment, the same odor that occurred during a meeting of the same series that was held in the past occurs before the start of the current meeting. Each participant can recognize when it is time to start a meeting based on the occurrence of an odor, and can recall what the meeting is about and the context of the meeting based on the memory associated with that odor. can. As a result, it is possible to start the meeting smoothly. Furthermore, since each participant does not need to take the time to look at text or illustrations, it is possible to reduce the amount of work required to start the meeting smoothly.

Note that it is possible to use sound (for example, BGM), but if the sound is heard during the meeting, it may be difficult to hear each participant's voice. Additionally, when using images, static images may give a weak impression, while videos may show movement, which may reduce participants' concentration. Smells can avoid problems such as making it difficult to hear each participant's voice during a meeting, or causing visual nuisance to each participant.

Next, a second embodiment will be described. In the second embodiment, differences from the first embodiment will be explained. Points not specifically mentioned in the second embodiment may be the same as those in the first embodiment.

In the second embodiment, the processing procedure executed by the execution unit 12 is different. Specifically, if the meeting exceeds the scheduled end time, processing is executed to prompt the meeting to end.

FIG. 9 is a flowchart for explaining an example of a processing procedure executed by the execution unit 12 in the second embodiment. In FIG. 9, steps that are the same as those in FIG. 7 are given the same step numbers, and their explanations will be omitted as appropriate.

Steps S201 to S204 are the same as in FIG. 7. If there is another meeting that has the same affiliation as MTG and has a track record (S204: YES), the execution unit 12 executes steps S205 to S211 in the same manner as in FIG. 7, and proceeds to step S231. However, in step S209, if the MS is not being held (NO in S209), the process proceeds to step S231 without executing step S210 in FIG.

In steps S231 to S234, the execution unit 12 waits until the current time TC exceeds the scheduled end date and time TE of the MSG or until the status MS of the target meeting is no longer O (until the target meeting ends).

When the current time TC exceeds the scheduled end date and time TE of the MSG (YES in S232), the execution unit 12 uses a scent (hereinafter referred to as "exceeding scent") that is pre-assigned to the case where the current time TC exceeds the scheduled end date and time TE of MSG. ), and outputs an instruction to start generating odor to the odor generating device 109 (S235). The odor generating device 109 starts generating the excess odor in response to the start instruction. Incidentally, in order to make the meeting want to quit a meeting that has exceeded the scheduled end date and time TE (a meeting that has lasted longer than scheduled), an unpleasant odor is suitable as the odor for exceeding the scheduled end date and time TE. Examples of unpleasant odors include sulfur compounds such as methyl mercaptan, dimethyl sulfide, and tetrahydrothiophene, which are odorants used for gas odors.

Next, the execution unit 12 waits until the status MS of the target meeting is no longer O (until the target meeting ends) (S236, S237).

When the target meeting ends (NO in S237), the execution unit 12 outputs an instruction to stop odor generation to the odor generation device 109 (S238). The odor generating device 109 stops generating odor.

On the other hand, if there is no other meeting that has the same affiliation as MTG and has a record of implementation (NO in S204), the execution unit 12 executes steps S213 to S219 as in FIG. 7, and then executes steps S231 and subsequent steps. Execute. However, in step S209, if the MS is not being held (NO in S216), the process proceeds to step S231 without executing step S217 in FIG.

[Specific example 3]
<Processing procedure of execution unit 12 (FIG. 9)>
It is assumed that the processing procedure of the execution unit 12 in the first concrete example up to (*) is the same as in the first concrete example.

Subsequently, the execution unit 12 obtains the current time TC=2022/01/12 11:05 (S231). Since TE<TC, the execution unit 12 specifies the type of excess odor and outputs an instruction to start odor generation to the odor generation device 109 (S235).

Subsequently, the execution unit 12 acquires the MS from the meeting server 20 (S236).

Here, MS=O (YES in S237). The execution unit 12 acquires the MS again (S236).

When MS=O is no longer true (NO in S237), the execution unit 12 outputs an instruction to stop odor generation to the odor generation device 109 (S238). The odor generating device 109 stops generating odor.

In this way, if a meeting is being held past the scheduled end date and time, there will be a sense of overrun, which will motivate you to end the meeting within the scheduled end time, resulting in an efficient meeting. can encourage implementation.

Note that in this embodiment, the user terminal 10 is an example of a meeting support device. The registration unit 11 is an example of an input unit and a registration processing unit. The execution unit 12 is an example of a determination unit and an odor generation processing unit.

Although the embodiments of the present invention have been described in detail above, the present invention is not limited to these specific embodiments, and various modifications can be made within the scope of the gist of the present invention as described in the claims. - Can be changed.

10 User terminal 11 Registration unit 12 Execution unit 13 Storage unit 20 Meeting server 100 Drive device 101 Recording medium 102 Auxiliary storage device 103 Memory device 104 CPU
105 Interface device 106 Display device 107 Input device 108 Clock 109 Odor generator B Bus

Claims

Determine whether second information having a predetermined commonality with first information regarding a meeting whose start time is approaching within a predetermined time is included in information regarding any meeting that has already been conducted. a determination procedure to
an odor generation procedure for executing a process for generating the same odor as the odor generated in the meeting related to the second information before the start of the meeting related to the first information when the second information is present; and,
A meeting support method characterized in that a computer executes the following.
an input procedure for inputting the first information;
If the second information having the predetermined commonality with the input first information is stored in a storage unit that stores information regarding the meeting for each meeting, the second information is associated with the second information. registering the inputted information in the storage unit in association with the type of odor that exists, and if the second information is not stored in the storage unit, associating it with any of the information stored in the storage unit; a registration step of registering the input schedule information in the storage unit by associating it with a type of odor that has not been registered;
The computer executes
The determination procedure determines whether the second information is stored in the storage unit,
The odor generation procedure includes, when the second information is stored in the storage unit, generating a type of odor associated with the first information before the start of a meeting related to the first information. , if the second information is not stored in the storage unit, executing a process of generating a type of smell associated with the first information after the start of the meeting related to the first information;
The meeting support method according to claim 1, characterized in that:
The odor generation procedure includes executing a process for generating a predetermined odor when the meeting according to the first information does not end even after the scheduled end time of the meeting has arrived.
The meeting support method according to claim 1 or 2, characterized in that:
Determine whether second information having a predetermined commonality with first information regarding a meeting whose start time is approaching within a predetermined time is included in information regarding any meeting that has already been conducted. a determination unit configured to
If the second information is present, the system is configured to execute processing for generating the same odor as the odor generated in the meeting related to the second information before the start of the meeting related to the first information. An odor generation processing unit that is
A meeting support device comprising:
an input unit configured to input the first information;
If the second information having the predetermined commonality with the input first information is stored in a storage unit that stores information regarding the meeting for each meeting, the second information is associated with the second information. registering the inputted information in the storage unit in association with the type of odor that exists, and if the second information is not stored in the storage unit, associating it with any of the information stored in the storage unit; a registration processing unit configured to register the input schedule information in the storage unit by associating it with a type of odor that has not been registered;
has
The determination unit is configured to determine whether the second information is stored in the storage unit,
When the second information is stored in the storage unit, the odor generation processing unit generates a type of odor associated with the first information before the start of the meeting related to the first information. and if the second information is not stored in the storage unit, execute processing for generating a type of odor associated with the first information after the start of the meeting related to the first information. is composed of
The meeting support device according to claim 4, characterized in that:
The odor generation processing section is configured to execute processing for generating a predetermined odor if the meeting related to the first information does not end even after the scheduled end time. ,
The meeting support device according to claim 4 or 5, characterized in that:
Determine whether second information having a predetermined commonality with first information regarding a meeting whose start time is approaching within a predetermined time is included in information regarding any meeting that has already been conducted. a determination procedure to
an odor generation procedure for executing a process for generating the same odor as the odor generated in the meeting related to the second information before the start of the meeting related to the first information when the second information is present; and,
A program that causes a computer to execute.