JP2023073645A - Communication support program, communication support method, and server - Google Patents

Abstract

To provide a technique to make communication between users more feasible.SOLUTION: A communication support program for adjusting a communication date and time between users causes a server to perform a step of receiving from a first user an input of a first communication candidate date and time when the first user can communicate with a second user within a first date range, a step of notifying the second user of the first communication candidate date and time, and a step of receiving a selection of a date and time when the second user can communicate with the first user with in the first communication candidate date and date from the second user. A start date and time in the first date and time range is after a first predetermined time period from a reception time of the first communication candidate date and time from the first user.SELECTED DRAWING: Figure 7

Description

The present disclosure relates to an exchange support program, an exchange support method, and a server.

Techniques for adjusting exchange dates and times between users are widespread. As an example, Japanese Patent No. 6671727 (Patent Document 1) discloses a reception management system for coordinating schedules between a person in charge and a visitor. The reception management system receives an input of a candidate date and time for a meeting from the terminal of the person in charge, and transmits the candidate date and time to the terminal of the visitor. The date and time of the meeting is determined by the visitor's selection of one of the candidate dates and times.

As another example, Japanese Patent Laying-Open No. 2021-2255 (Patent Document 2) discloses a schedule adjustment system capable of adjusting the schedules of User A and User B. User A uses the schedule adjustment system to input a candidate date for the meeting, and user B selects a date that is available from among the candidate dates. On the other hand, if User B does not have any available candidate dates, User B requests User A to send another candidate date.

Japanese Patent No. 6671727 Japanese Patent Application Laid-Open No. 2021-2255

Even if the first user inputs an exchange candidate date and time, the second user does not necessarily confirm the exchange candidate date and time immediately. Further, the second user does not necessarily select the exchange date and time immediately after confirming the candidate exchange date and time. Therefore, the candidate exchange date and time input by the first user may be past date and time when the second user selects the exchange date and time. In that case, interaction between the first user and the second user is not established. Patent Literatures 1 and 2 do not disclose any such problem.

The present disclosure has been made to solve such problems, and an object thereof is to provide a technique for facilitating interaction between users.

An example of the present disclosure provides an exchange support program for adjusting exchange dates and times between users. The interaction support program comprises: receiving from the first user an input of a first candidate date and time for interaction at which the first user can interact with the second user within the first date and time range; The server is caused to execute a step of notifying two users, and a step of accepting from the second user a selection of a date and time when the second user can interact with the first user from among the first candidate date and time for interaction. The start date and time of the first date and time range is after a first predetermined period from the reception of the first candidate date and time for interaction from the first user.

In this exchange support program, the input of exchange candidate date and time is accepted within the first date and time range. The start date and time of the first date and time range is after the first predetermined period from the reception of the first candidate date and time for interaction from the first user. As a result, the exchange candidate date and time is input from within the earlier date and time range, and the possibility that it is past date and time at the time of confirmation by the second user is reduced. As a result, it becomes easier for the first user and the second user to interact with each other.

In an example of the present disclosure, after the first candidate exchange date and time is notified to the second user, the exchange support program inputs a second candidate exchange date and time different from the first candidate exchange date and time in a second date and time range. further causes the server to execute a step of receiving from the second user. The start date and time of the second date and time range is later than the start date and time of the first date and time range.

In this exchange support program, after the second user is notified of the first candidate exchange date and time, the second user's input of the candidate exchange date and time is accepted within the second date and time range. Since the start date and time of the second date and time range is later than the start date and time of the first date and time range, it is possible that the candidate date and time for interaction input by the second user may be in the past at the time of confirmation by the first user. become less sexual. As a result, it becomes easier for the first user and the second user to interact with each other.

In one example of the present disclosure, the exchange support program determines whether the first user has used the function of the server within a second predetermined period before accepting the second exchange candidate date and time. , causing the server to further execute a process of changing the start date and time of the second date and time range. The start date and time of the second date and time range in the case where the first user uses the function of the server within the second predetermined period is It is later than the start date and time of the second date and time range when the function is not used.

In this exchange support program, the second date and time range is such that if the first user uses the computer function within the second predetermined period, the first user uses the computer function within the second predetermined period. It is set earlier than if it had not. This allows the first user to propose a more appropriate candidate date and time for interaction in time with the second user's next use of the function of the computer.

In one example of the present disclosure, the exchange support program, if the selection has not been received within a third predetermined period after the first exchange candidate date and time is accepted, the first exchange candidate Further causing the server to execute a step of receiving an input of a third exchange candidate date and time different from the date and time from the first user or the second user within the third date and time range. The start date and time of the third date and time range is later than the start date and time of the first date and time range.

In this exchange support program, when there is no response from the second user to the first candidate date and time input by the first user for a predetermined period of time, the candidate date and time for interaction can be newly input. An input of a new exchange candidate date and time is accepted from within the third date and time range earlier than the first date and time range. This reduces the possibility that the exchange candidate date and time newly input by one of the first and second users will be past date and time at the time of confirmation by the other user. As a result, it becomes easier for the first user and the second user to interact with each other.

In one example of the present disclosure, the exchange support program causes the server to further execute a step capable of fixing an exchange date and time between the first user and the second user without accepting the selection.

In this exchange support program, the first user and the second user can start the exchange at any timing without depending on the exchange candidate date and time input by the first user.

In one example of the present disclosure, the exchange support program resets the candidate exchange date and time within a fourth date and time range when the exchange at the exchange date and time determined by the selection is canceled on the day. Further causing the server to perform the step of accepting from a second user. The start date and time of the fourth date and time range is after the fourth predetermined period from the reception of the reset. The fourth predetermined period is shorter than the first predetermined period.

In this exchange support program, the first user or the second user can input an exchange candidate date and time from within the most recent fourth date and time range when the exchange at the confirmed exchange date and time is canceled on the day. can. Thereby, the first user or the second user can immediately start the interaction when the interaction is canceled due to forgetfulness.

In one example of the present disclosure, the exchange support program causes at least one of the first user and the second user to reset the exchange date and time when the exchange at the exchange date and time determined by the selection is canceled on the day. Further causing the server to perform the step of sending a notification to prompt.

In this exchange support program, even if the confirmed exchange is canceled once, the exchange between the first user and the second user is promoted.

In one example of the present disclosure, the exchange support program is configured such that the exchange date and time between the first user and the second user are not confirmed until a fifth predetermined period elapses after the first candidate exchange date and time is accepted. If so, cause the server to further execute a step of disabling interaction between the first user and the second user.

In this exchange support program, the exchange is not established when the date and time of the exchange are not fixed for a predetermined period of time. As a result, it is possible to prevent the user from feeling that the adjustment of the exchange date and time is a burden.

In one example of the present disclosure, the exchange support program allows the input of a third candidate exchange date and time at which the first user can interact with the third user, after the exchange date and time between the first user and the second user are confirmed. further causes the server to execute a step of accepting from the first user in.

In this exchange support program, adjustment of the exchange date and time between the first user and the third user is prohibited until the exchange date and time between the first user and the second user are fixed. As a result, the user is prevented from adjusting the exchange date and time many times at the same time. As a result, it is possible to reduce the user's burden related to the adjustment of the exchange date and time.

Another example of the present disclosure provides an exchange support method for adjusting exchange dates and times between users. The interaction support method includes the steps of: accepting from the first user an input of a first candidate interaction date and time at which the first user can interact with the second user within the first date and time range; a step of notifying two users; and a step of accepting from the second user a selection of a date and time when the second user can interact with the first user from among the first candidate date and time for interaction. The start date and time of the first date and time range is after a first predetermined period from the reception of the first candidate date and time for interaction from the first user.

In this exchange support method, the input of exchange candidate date and time is accepted within the first date and time range. Further, the start date and time of the first date and time range is after the first predetermined period from the reception of the first candidate date and time for interaction from the first user. As a result, the exchange candidate date and time is input from within the earlier date and time range, and the possibility that it is past date and time at the time of confirmation by the second user is reduced. As a result, it becomes easier for the first user and the second user to interact with each other.

Another example of the present disclosure provides a server for coordinating interaction dates and times between users. The server includes a control unit for controlling the server. The control unit receives from the first user an input of a first candidate exchange date and time at which the first user can interact with the second user within the first date and time range, and sets the first candidate exchange date and time to the second A process of notifying the user, and a process of receiving from the second user a selection of a date and time when the second user can interact with the first user within the first candidate date and time for interaction are executed. The start date and time of the first date and time range is after a first predetermined period from the reception of the first candidate date and time for interaction from the first user.

In this computer, the input of the exchange candidate date and time is accepted within the first date and time range. Further, the start date and time of the first date and time range is after the first predetermined period from the reception of the first candidate date and time for interaction from the first user. As a result, the exchange candidate date and time is input from within the earlier date and time range, and the possibility that it is past date and time at the time of confirmation by the second user is reduced. As a result, it becomes easier for the first user and the second user to interact with each other.

In a certain aspect, it is possible to provide a technique for facilitating interaction between users.

The above and other objects, features, aspects and advantages of the present invention will become apparent from the following detailed description of the invention taken in conjunction with the accompanying drawings.

It is a figure which shows an example of the apparatus configuration of an exchange support system. FIG. 10 is a diagram schematically showing how exchange candidate dates and times are input from within a predetermined date and time range; It is a schematic diagram which shows an example of the hardware constitutions of a server. 1 is a schematic diagram showing an example of a hardware configuration of a terminal; FIG. It is a figure which shows an example of the data flow between a server and each terminal. It is a figure which shows an example of a start screen. It is a figure which shows an example of an input screen. It is a figure which shows an example of a confirmation screen. It is a figure which shows an example of a confirmation screen. It is a figure which shows an example of a selection screen. It is a figure which shows an example of a screen transition. It is a figure which shows an example of a reminder screen. It is a figure which shows an example of the data flow between a server and each terminal. It is a figure which shows an example of a screen transition. FIG. 10 is a diagram showing the relationship between date and time ranges in which each user can input exchange candidate dates and times; FIG. 10 is a diagram showing a difference in date and time ranges in which each user can input exchange candidate dates and times; It is a figure which shows an example of a confirmation screen. It is a figure which shows an example of the data flow between a server and each terminal. It is a figure which shows an example of an input screen. FIG. 10 is a diagram showing the relationship between date and time ranges in which each user can input exchange candidate dates and times; It is a figure which shows an example of the data flow between a server and each terminal. It is a figure which shows an example of a reminder screen. It is a figure which shows an example of the data flow between a server and each terminal. It is a figure which shows an example of a reminder screen. It is a figure which shows an example of a request screen. It is a figure which shows an example of a reminder screen. It is a figure which shows an example of the data flow between a server and each terminal. It is a figure which shows an example of an input screen. FIG. 10 is a diagram schematically showing how a new exchange candidate date and time is input from within a predetermined date and time range. It is a figure which shows an example of a selection screen. It is a figure which shows an example of a notification screen. FIG. 10 is a diagram showing an example of a notification displayed on a terminal as a wearable terminal;

Hereinafter, each embodiment according to the present invention will be described with reference to the drawings. In the following description, identical parts and components are given identical reference numerals. Their names and functions are also the same. Therefore, detailed description of these will not be repeated. In addition, each embodiment and each modified example described below may be selectively combined as appropriate.

<A. Exchange support system 10>
First, referring to FIG. 1, the device configuration of the exchange support system 10 will be described. FIG. 1 is a diagram showing an example of the device configuration of an exchange support system 10. As shown in FIG.

The exchange support system 10 is used, for example, to support exchanges between employees in a company (enterprise) CM1, which is an example of an organization. Interaction between employees is performed through, for example, an online call function provided in the exchange support system 10 . Hereinafter, interaction between users using the interaction support system 10 is also referred to as “online interaction”.

As shown in FIG. 1, exchange support system 10 includes server 100 and terminal 200 . Server 100 and terminal 200 can communicate through network N1 (for example, the Internet).

The server 100 is, for example, a notebook or desktop PC (Personal Computer), a desktop PC, a tablet terminal, or other computer with a communication function. The number of servers 100 configuring the exchange support system 10 may be one, or may be two or more.

The terminal 200 is, for example, a notebook or desktop PC, tablet terminal, smart phone, wearable terminal, or other computer with a communication function. Although three terminals 200A to 200C are shown in the example of FIG. 1, the number of terminals 200 constituting the exchange support system 10 may be two, or four or more. Hereinafter, terminals 200A to 200C are also referred to as terminal 200 when terminals 200A to 200C are not particularly distinguished.

Terminal 200 is owned, for example, by a user belonging to company CM1. In the example of FIG. 1, terminal 200A is owned by user A, for example. Terminal 200B is owned by user B, for example. Terminal 200C is owned by user C, for example.

As an example, users of the exchange support system 10 are employees of the company CM1. The work style of each user includes going to work and working from home. A user who goes to work uses the terminal 200 at work, and a user who works from home uses the terminal 200 at a place other than the work place (for example, at home, while traveling, etc.).

As another example, users of the exchange support system 10 are school students and staff. The terminal 200 is used in schools by students and teachers who attend in a face-to-face format. In addition, terminal 200 is used at locations other than school (eg, at home) by students and teachers who attend classes online.

As yet another example, the exchange support system 10 is used by family members. Terminal 200 is used by a family member at home, for example. In addition, the terminal 200 is used in a house other than the home of a child who has left his/her parents.

Various types of processing described in this specification may be executed by the server 100, may be executed by the terminal 200, or may be executed by another device. Also, the exchange support system 10 does not necessarily have to include the server 100 , and may be configured only with a plurality of terminals 200 . In this case, various types of processing described in this specification are performed by cooperation of multiple terminals 200 .

<B. Overview of the exchange date and time adjustment function>
Next, with reference to FIG. 2, an overview of the exchange date and time adjustment function provided by the exchange support system 10 will be described. FIG. 2 is a diagram schematically showing how exchange candidate dates and times are input from within the date and time range ΔTR1.

The exchange support system 10 has a function of supporting online exchange between users. The exchange support system 10 creates opportunities for communication by periodically providing users with opportunities for online exchange. Thereby, the exchange support system 10 maintains the user's mental health.

In order for a user to interact with another user online, it is necessary to predetermine the date and time of interaction between the users. However, when users use the exchange support system 10 infrequently (for example, once a day), it becomes difficult to coordinate the date and time of exchange between users. For example, the exchange support system 10 may be configured as part of a system used by the user to maintain mental health, or may be configured as part of a system for managing the working hours of the user. , the user will use the exchange support system 10 about once a day.

As a more specific example, it is assumed that user A inputs an exchange candidate date and time on terminal 200A, and user B's terminal 200B is notified of the exchange candidate date and time. At this time, user B does not necessarily immediately confirm the exchange candidate dates and times presented by user A. In this case, there is a possibility that the exchange candidate date and time has already become a past date and time when user B confirms it.

Therefore, the exchange support system 10 supports the adjustment of exchange dates and times so that online exchanges between users can be easily established. More specifically, first, server 100 causes terminal 200A to receive an input of an exchange candidate date and time when user A can interact with user B from within date and time range ΔTR1.

The start date and time T1S of the date and time range ΔTR1 is a predetermined period ΔTP1 after the reception of the exchange candidate date and time from the user A (that is, the timing T0A). The predetermined period ΔTP1 may be several hours later (for example, 12 to 24 hours later), several days later (for example, 1 to 2 days later), or the next day or the next day of the day to which timing T0A belongs. It may be later.

Note that the timing T0A does not have to be exactly the same as when the reception of the exchange candidate date and time input is started, and may be substantially the same as the time when the reception is started. As an example, timing T0A may be around a predetermined time when server 100 or terminal 200A starts accepting input of exchange candidate dates and times.

The end date and time T1E of the date and time range ΔTR1 may be determined in advance based on the start date and time T1S, or may be arbitrarily set by the user. As an example, the end date and time T1E of the date and time range ΔTR1 is a certain time after the start date and time T1S (for example, several days to several months).

The terminal 200A notifies the server 100 of the candidate exchange date and time based on the reception of the input of the candidate exchange date and time. After that, the server 100 causes the terminal 200B to accept selection of a date and time when the user B can interact with the user A from among the interaction candidate dates and times input by the user A.

In this manner, the exchange support system 10 accepts input of candidate exchange dates and times within the date and time range ΔTR1 after the predetermined period ΔTP1. This reduces the possibility that the exchange candidate date and time input by user A is in the past at the time of user B's confirmation. Further, if the presented candidate date and time for interaction is earlier, user B can decide the date and time for interaction with user A after adjusting his/her own schedule. As a result, it becomes easier for the user A and the user B to interact with each other.

<C. Hardware configuration>
The hardware configurations of the server 100 and the terminal 200 shown in FIG. 1 will be described in order with reference to FIGS. 3 and 4. FIG.

(C1. Hardware Configuration of Server 100)
First, the hardware configuration of the server 100 will be described with reference to FIG. FIG. 3 is a schematic diagram showing an example of the hardware configuration of the server 100. As shown in FIG.

The server 100 includes a control device 101 , a ROM (Read Only Memory) 102 , a RAM (Random Access Memory) 103 , a communication interface 104 , a display interface 105 , an input interface 107 and a storage device 120 . These components are connected to bus 110 .

The control device 101 is composed of, for example, at least one integrated circuit. Integrated circuits include, for example, at least one CPU (Central Processing Unit), at least one GPU (Graphics Processing Unit), at least one ASIC (Application Specific Integrated Circuit), at least one FPGA (Field Programmable Gate Array), or It can be configured by a combination of

The control device 101 controls the operation of the server 100 by executing various programs such as the exchange support program 122 and an operating system. The control device 101 reads the programs from the storage device 120 or the ROM 102 to the RAM 103 based on the execution instructions of various programs. The RAM 103 functions as a working memory and temporarily stores various data necessary for executing various programs.

A LAN (Local Area Network), an antenna, and the like are connected to the communication interface 104 . Server 100 exchanges data with external devices via communication interface 104 . The external device includes, for example, the terminal 200 and the like.

A display 106 is connected to the display interface 105 . Display interface 105 sends an image signal for displaying an image to display 106 in accordance with a command from control device 101 or the like. The display 106 is, for example, a liquid crystal display, an organic EL (Electro Luminescence) display, or other display device. Note that the display 106 may be configured integrally with the server 100 or may be configured separately from the server 100 .

An input device 108 is connected to the input interface 107 . Input device 108 is, for example, a mouse, keyboard, touch panel, or other device capable of receiving user operations. Note that the input device 108 may be configured integrally with the server 100 or may be configured separately from the server 100 .

The storage device 120 is, for example, a storage medium such as a hard disk or flash memory. The storage device 120 stores an exchange support program 122, a user DB (Data Base) 124, a usage history 126, and the like.

The user DB 124 associates, for example, passwords, user names, user images, and user attributes (such as gender, address, department name, etc.) with each user ID (Identification).

The usage history 126 associates the time when the user logged in to the server 100 and the time when the user logged out from the server 100 for each user ID.

The storage locations of the exchange support program 122, the user DB 124, and the usage history 126 are not limited to the storage device 120, but are stored in a storage area of the control device 101 (for example, cache memory, etc.), ROM 102, RAM 103, external devices, and the like. may

It should be noted that the exchange support program 122 may be provided as a part of an arbitrary program, not as a standalone program. In this case, various processes defined in the exchange support program 122 are implemented in cooperation with an arbitrary program. Even a program that does not include such a part of modules does not deviate from the gist of the exchange support program 122 according to the present embodiment. Furthermore, some or all of the functions provided by the exchange support program 122 may be realized by dedicated hardware. Furthermore, the server 100 may be configured in a form such as a so-called cloud service in which at least one server executes part of the processing of the exchange support program 122 .

(C2. Hardware configuration of terminal 200)
Next, the hardware configuration of terminal 200 will be described with reference to FIG. FIG. 4 is a schematic diagram showing an example of the hardware configuration of the terminal 200. As shown in FIG.

Terminal 200 includes control device 201 , ROM 202 , RAM 203 , communication interface 204 , display interface 205 , input interface 207 and storage device 220 . These components are connected to bus 210 .

The control device 201 is, for example, composed of at least one integrated circuit. An integrated circuit may be comprised of, for example, at least one CPU, at least one GPU, at least one ASIC, at least one FPGA, or combinations thereof.

The control device 201 controls the operation of the terminal 200 by executing various programs such as an exchange support program 222 and an operating system. The control device 201 reads the programs from the storage device 220 or the ROM 202 to the RAM 203 based on the execution instructions of various programs. A RAM 203 functions as a working memory and temporarily stores various data necessary for executing the program.

A LAN, an antenna, and the like are connected to the communication interface 204 . Terminal 200 exchanges data with external devices via communication interface 204 . The external device includes, for example, the server 100 or a server. The terminal 200 may be configured to download the exchange support program 222 from the server 100 .

A display 206 is connected to the display interface 205 . Display interface 205 sends an image signal for displaying an image to display 206 in accordance with a command from control device 201 or the like. The display 206 is, for example, a liquid crystal display, organic EL display, or other display device. Note that the display 206 may be configured integrally with the terminal 200 or may be configured separately from the terminal 200 .

An input device 208 is connected to the input interface 207 . Input device 208 is, for example, a mouse, keyboard, touch panel, or other device capable of receiving user operations. Note that the input device 208 may be configured integrally with the terminal 200 or may be configured separately from the terminal 200 .

The storage device 220 is, for example, a storage medium such as a hard disk or flash memory. The storage device 220 stores an exchange support program 222 and the like. The storage location of the exchange support program 222 is not limited to the storage device 220, and may be stored in a storage area of the control device 201 (eg, cache memory, etc.), ROM 202, RAM 203, external device (eg, server), or the like. .

It should be noted that the exchange support program 222 may be provided as a part of an arbitrary program, not as a standalone program. In this case, various processes defined in the exchange support program 222 are implemented in cooperation with an arbitrary program. Even a program that does not include some of these modules does not deviate from the gist of the exchange support program 222 according to the present embodiment. Furthermore, some or all of the functions provided by the exchange support program 222 may be realized by dedicated hardware. Furthermore, the server 100 may be configured in a form such as a so-called cloud service in which at least one server executes part of the processing of the exchange support program 222 .

<D. Operation until the exchange date and time is fixed>
Next, with reference to FIGS. 5 to 12, the operation of the exchange support system 10 until the exchange date and time between users is fixed will be described. FIG. 5 is a diagram showing an example of a data flow between the server 100 and terminals 200A and 200B.

In step S10, user A accesses exchange support system 10 using terminal 200A. Based on this, a login screen is displayed on the terminal 200A. The login screen accepts input of user information such as a user ID and password. When user A presses the login button on the login screen, terminal 200</b>A transmits the input user information to server 100 .

At step S12, the server 100 determines whether or not the user information input at step S10 is registered in the above-described user DB 124 (see FIG. 3). If the server 100 determines that the user information input in step S10 is registered in the user DB 124, the server 100 executes a login process and transmits a notification indicating that the login was successful to the terminal 200A. Otherwise, server 100 sends a notification to terminal 200A indicating that the login has failed.

In the example of FIG. 5, it is assumed that the login process was performed normally in step S12. The result of the login process is written in the aforementioned usage history 126 after being associated with the user information and the login time.

In step S14, the terminal 200A displays the home screen. The home screen includes buttons and the like for using various functions of the exchange support system 10 .

FIG. 6 shows a start screen 300A forming part of the home screen. Start screen 300A accepts an instruction to execute the brush-up function. The brush-up function is a function for maintaining mental health. The brush-up function is executed by the user, for example, once a day. Thereby, user A can maintain his mental health by using the brush-up function.

An instruction to execute the brush-up function is accepted by start button 301 on start screen 300A. Server 100 sequentially sends questions to user A to terminal 200A based on start button 301 being pressed. User A answers each question via terminal 200A. Server 100 generates advice for user A based on the answers to each question, and transmits the advice to terminal 200A.

The brush-up function includes not only a function for generating advice for users, but also a function for supporting online interaction between users. When the support function is executed, the server 100 determines interaction partner candidates suitable for the user A in step S16. At this time, the server 100 determines interaction partner candidates from among the members of the same department or team as the user A.

Interaction partner candidates are determined so that online interaction is easily established and online interaction is performed with potential compatible partners. As an example, the server 100 determines interaction partner candidates based on at least one of the user's personality tendencies, the user's hobbies, and the user's working hours. The user's personality tendency, the user's hobby, and the user's working hours are registered in advance, for example, in the above-described user DB 124 (see FIG. 3).

As an example, the server 100 determines other users who have the same personality tendency as the user A as interaction partner candidates based on the user DB 124 . As another example, the server 100 determines other users who have the same hobby as the user A as interaction partner candidates based on the user DB 124 . As yet another example, the server 100 determines other users who overlap with the working hours of the user A as interaction partner candidates based on the user DB 124 .

Preferably, the server 100 excludes other users who are less likely to establish online exchanges with the user A from the exchange partner candidates. As an example, the server 100 refers to the interaction history of user A and excludes other users who interacted 1 to n times before from the interaction partner candidates. As another example, the server 100 excludes other users whose usage rate of the exchange support system 10 is lower than a predetermined threshold from the exchange partner candidates. As yet another example, the server 100 excludes other users whose degree of past online interaction is lower than a predetermined threshold from the interaction partner candidates. As yet another example, the server 100 excludes other users who have a higher frequency than a predetermined threshold value from setting a time slot when other users are not available as interaction candidate dates and times from the interaction partner candidates. As yet another example, the server 100 excludes, from the interaction partner candidates, other users who have canceled online interactions more times than a predetermined threshold within the most recent predetermined period.

In step S16, server 100 transmits the determined interaction partner candidates to terminal 200A.

In step S18, terminal 200A displays a selection screen of interaction partner candidates on display 206. FIG. User A can select any user from among the interaction partner candidates displayed on the selection screen. As an example, assume that user A selects user B as an exchange partner. Based on this, terminal 200A transmits the user information of user B to server 100 as a selection result.

In step S22, the terminal 200A displays an input screen for exchange candidate date and time. FIG. 7 is a diagram showing an input screen 300B as an example.

As shown in FIG. 7, the input screen 300B includes an exchange partner display field 302, an exchange candidate date and time input field 304, and an OK button 306. As shown in FIG.

The display column 302 displays user information related to the exchange partner selected in step S18. The user information displayed in the display field 302 includes, for example, the image of the interaction partner, the user name of the interaction partner, and the hobbies of the interaction partner. The user information is obtained, for example, from the above-described user DB 124 (see FIG. 3).

The input field 304 is configured to accept inputs of exchange candidate dates and times in order of preference. The initial value of the candidate exchange date and time is determined within the date and time range ΔTR1 excluding the predetermined period ΔTP1, as shown in FIG.

User A can change the initial exchange candidate date and time in the input field 304 . The input of the candidate date and time for interaction is realized, for example, by specifying the date of interaction using a pull-down menu and specifying the time of interaction using a text box. If the text box is blank, the terminal 200A assumes that no exchange candidate date and time has been entered.

At this time, the input field 304 accepts input of exchange candidate date and time from within the above-described date and time range ΔTR1 (see FIG. 2) excluding the above-described predetermined period ΔTP1. That is, user A cannot input the most recent date and time as a candidate date and time for interaction. As an example, if the current date is October 2nd, the terminal 200A accepts input of exchange candidate dates and times from October 4th, two days later.

In one aspect, the length of the date and time range ΔTR1 can be varied according to the user's personality traits. Personality tendencies of the user are identified, for example, based on the Big Five, which is a type of taxonomy of personal characteristics. The Big Five personality traits are represented by five factors: Openness, Conscientiousness, Extraversion, Agreeableness, and Neuroticism. Personality tendencies of each user are defined in advance, for example, in the user DB 124 described above.

As an example, terminal 200A shortens date and time range ΔTR1 for users whose neuroticism indicates that they are susceptible to psychological stress. In this case, the start date and time T1S of the date and time range ΔTR1 is set three days after the timing T0A, and the end date and time T1E of the date and time range ΔTR1 is set four days after the timing T0A.

In addition, terminal 200A makes the date and time range ΔTR1 longer for users whose neurotic tendencies indicate that they are less susceptible to psychological stress. In this case, the start date and time T1S of the date and time range ΔTR1 is set two days after the timing T0A, and the end date and time T1E of the date and time range ΔTR1 is set four days after the timing T0A.

In another aspect, the length of the date/time range ΔTR1 can be varied according to the busyness of the user. The degree of busyness of each user is defined in advance, for example, in the user DB 124 described above.

If the user's busyness is lower than a predetermined value, the date/time range ΔTR1 is shortened. As an example, in this case, the start date and time T1S of the date and time range ΔTR1 is set three days after the timing T0A, and the end date and time T1E of the date and time range ΔTR1 is set four days after the timing T0A.

Further, when the degree of busyness of the user is equal to or higher than the predetermined value, terminal 200A extends date and time range ΔTR1. In this case, the start date and time T1S of the date and time range ΔTR1 is set two days after the timing T0A, and the end date and time T1E of the date and time range ΔTR1 is set four days after the timing T0A.

In yet another aspect, the length of the date/time range ΔTR1 can be varied to take into consideration organizational holidays (non-business days) and mutual holidays. As an example, the terminal 200A acquires holidays or working hours set in advance, and does not include the date and time that the interaction partner considers as a holiday in the candidate interaction date and time.

Terminal 200A transmits the exchange candidate date and time entered in input field 304 to server 100 based on pressing of enter button 306 on input screen 300B. Server 100 stores the exchange candidate date and time received from terminal 200A.

Referring to FIG. 5 again, in step S24, terminal 200A displays a confirmation screen for the input candidate exchange date and time. FIG. 8 is a diagram showing a confirmation screen 300C as an example.

The confirmation screen 300</b>C includes an exchange partner display field 302 , a message 307 , an exchange candidate date and time display field 308 , and a forward button 310 .

The display field 302 of the confirmation screen 300C displays the same content as the display field 302 of the input screen 300B described above.

The message 307 is a message for prompting the interaction partner (for example, user B) to verbally inform that the user A has input the exchange candidate date and time. When the exchange partner has not yet input the exchange candidate date and time, the terminal 200A may display a prompt to input through external means (for example, oral, email, message tool, phone call, etc.).

The exchange candidate date and time input by the user A is displayed in the display column 308 of the exchange candidate date and time. Thereby, the user A can confirm whether or not the exchange candidate date and time inputted by himself is the intended date and time.

Terminal 200A closes confirmation screen 300C based on pressing forward button 310 on confirmation screen 300C.

Referring to FIG. 5 again, in step S26, terminal 200A displays the home screen. FIG. 9 shows a confirmation screen 300D forming part of the home screen displayed in step S26.

The confirmation screen 300D is displayed on the home screen from when the candidate date and time for the exchange is notified to the terminal 200B until the date and time for the exchange is fixed. That is, the confirmation screen 300D is displayed on the home screen every time the user A logs into the exchange support system 10. FIG.

The confirmation screen 300</b>D includes an exchange partner display field 302 , an exchange candidate date and time display field 311 , a connect button 312 , and a change button 313 .

The display field 302 of the confirmation screen 300D displays the same content as the display field 302 of the input screen 300B described above.

In the display field 311, exchange candidate dates and times that have already been transmitted to the terminal 200B are displayed. As a result, user A can always confirm the exchange candidate dates and times that he himself has input.

The connection button 312 is a button for connecting to an exchange partner without waiting for the fixed exchange date and time. When the connection button 312 is pressed, communication between the terminal 200A and the terminal 200B is connected, and online exchange between the user A and the user B is started.

In this way, the server 100 can fix the date and time of interaction between the users A and B without accepting the user B's selection of the candidate date and time for interaction presented by the user A. Thereby, the user A can start online interaction with the user B at an arbitrary timing without depending on the interaction candidate date and time presented by the user A. As a result, users A and B can flexibly start online interaction according to their work situation, work style (for example, whether or not they work remotely), the positional relationship between terminals 200A and 200B, and the like.

Note that the online exchange may be started immediately without the user inputting the exchange candidate date and time. Such an immediate online interaction function is used, for example, by users who are close to each other or users who communicate with each other on a daily basis. The user can omit adjustment of the exchange date and time by using the instant online exchange function. This improves the usability of the exchange support system 10 .

The change button 313 is a button for changing the confirmed exchange date and time. When change button 313 is pressed, terminal 200A executes the processes of steps S18 and S22 described above again, and accepts input of a new exchange date and time.

Referring to FIG. 5 again, it is assumed that user B accesses exchange support system 10 using terminal 200B in step S40 after some time has passed since user A entered the exchange candidate date and time. Based on this, a login screen is displayed on the terminal 200B. The terminal 200B transmits the input user information to the server 100 based on the user B inputting the user information on the login screen and pressing the login button.

At step S42, the server 100 determines whether or not the user information input at step S40 is registered in the above-described user DB 124 (see FIG. 3). When determining that the user information input in step S40 is registered in the user DB 124, the server 100 executes login processing and transmits a notification indicating that the login was successful to the terminal 200B. Otherwise, server 100 sends a notification to terminal 200B indicating that the login has failed.

In the example of FIG. 5, it is assumed that the login process was performed normally in step S42. The result of the login process is written in the aforementioned usage history 126 after being associated with the user information and the login time.

After completing the login process, the server 100 transmits the exchange candidate date and time input in step S22 to the terminal 200B.

In step S44, terminal 200B displays on display 206 a selection screen for exchange candidate dates and times. FIG. 10 is a diagram showing a selection screen 400A as an example.

As shown in FIG. 10 , the selection screen 400A includes an exchange partner display field 402 , an exchange candidate date and time selection field 404 , and an NG button 406 .

The display column 402 displays user information related to the communication partner. In the example of FIG. 10, the display column 402 displays the user information related to the user A who entered the exchange candidate date and time in step S22. The user information displayed in the display field 402 includes, for example, the image of the interaction partner, the user name of the interaction partner, and the hobbies of the interaction partner. The user information is obtained, for example, from the above-described user DB 124 (see FIG. 3).

In the selection column 404, the exchange date and time candidates input by the user A in step S22 are displayed in order of preference. A determination button 405 is displayed in line with each of the exchange candidate dates and times. User B can select his/her desired exchange candidate date and time by pressing one decision button 405 . Thereby, the server 100 causes the terminal 200B to accept the selection of the date and time when the user B can interact with the user A.

Note that if part of the candidate exchange dates and times input by user A has already passed at the time of confirmation by user B, terminal 200B does not display the part of candidate exchange dates and times in selection field 404. good too. As a result, unnecessary information is deleted, and the user can more easily select the exchange candidate date and time.

In step S44 shown in FIG. 5, it is assumed that decision button 405 on selection screen 400A has been pressed. Based on this, the terminal 200B transmits the selected exchange candidate date and time to the server 100 . The exchange candidate dates and times transmitted to server 100 are transmitted to terminal 200A when user A logs into exchange support system 10, for example.

FIG. 11 is a diagram showing an example of screen transition when the decision button 405 on the selection screen 400A is pressed. In the example of FIG. 11, the decision button 405 associated with the first desired exchange candidate date and time "10/4 (Monday) 08:00~" is pressed. Based on this, terminal 200B displays confirmation screen 400B shown in FIG. 11 on display 206 in step S46.

Confirmation screen 400</b>B includes exchange partner display field 402 , confirmation message 408 , timer 409 , and OK button 410 . Since the display field 402 is as described above, the description will not be repeated.

Confirmation message 408 includes a message including the exchange date and time determined by user B's selection (hereinafter also referred to as "fixed exchange date and time") and a message for prompting recording of the confirmed exchange date and time. FIG. 11 shows a message "It was set to 08:00 on 10/4 (Monday)" as an example of the message including the fixed exchange date and time. Also, as an example of a message for prompting memorandum of the fixed exchange date and time, the message "Let's make a note on the calendar so as not to forget" is shown. The calendar includes a calendar application and a paper medium calendar.

In the example of FIG. 11, the user is prompted to record the confirmed exchange date and time on the calendar, but the recommended recording destination is not limited to the calendar. As an example, the recommended recording destination may be Notepad. Also, the confirmed exchange date and time may be automatically recorded in a calendar application.

A timer 409 displays the time until the confirmation screen 400B is automatically closed. The terminal 200B closes the confirmation screen 400B when the remaining time of the timer 409 reaches zero. After that, the terminal 200B displays the home screen.

The OK button 410 is a button for closing the confirmation screen 400B. User B presses the OK button 410 after confirming the confirmation screen 400B. This allows user B to close the confirmation screen 400B before the remaining time of the timer 409 reaches zero. After that, the terminal 200B displays the home screen.

Referring to FIG. 5 again, in step S48, terminal 200B displays a reminder screen after displaying confirmation screen 400B. FIG. 12 is a diagram showing a reminder screen 400C as an example.

400 C of reminder screens comprise a part of home screen. The home screen is a screen displayed when logging into the exchange support system 10 . That is, the reminder screen 400C is displayed each time the user logs in to the exchange support system 10 after the fixed exchange date and time is fixed.

The remind screen 400</b>C includes a display field 412 for the fixed exchange date and time, a connection button 414 , and a change button 416 .

The display field 412 displays the user information of the next interaction partner, the confirmed exchange date and time, and a message for prompting to record the confirmed exchange date and time in the calendar.

The connection button 414 is a button for connecting to an exchange partner without waiting for the fixed exchange date and time. When the connection button 414 is pressed, communication between the terminal 200A and the terminal 200B is connected, and online communication between the user A and the user B is started.

In this way, the server 100 can confirm the date and time of interaction between the users A and B without waiting for the date and time of the interaction to be confirmed. Thereby, user B can start online interaction with user A at any timing. As a result, users A and B can flexibly start online interaction according to their work situation, work style (for example, whether or not they work remotely), the positional relationship between terminals 200A and 200B, and the like.

The change button 416 is a button for canceling the fixed exchange date and time and readjusting the exchange date and time. This allows user B to change the date and time of the meeting at any time when it becomes inconvenient for him/herself.

<E. Operation when the proposed exchange date and time is rejected>
Next, with reference to FIGS. 13 to 17, the operation of the exchange support system 10 when the exchange candidate date and time presented by the user A is rejected by the user B will be described. FIG. 13 is a diagram showing an example of data flow between the server 100 and the terminals 200A and 200B.

In the example of FIG. 5 described above, the process of step S46 is executed next based on the decision button 405 (see FIG. 11) being pressed in step S44. On the other hand, if the NG button 406 (see FIG. 11) is pressed in step S44, then the process of step S52 shown in FIG. 13 is executed. The NG button 406 is pressed when the exchange candidate date and time presented by user A is not convenient for user B.

FIG. 14 is a diagram showing an example of screen transition when the NG button 406 is pressed in step S44 shown in FIG.

As shown in FIG. 14, terminal 200B displays an exchange candidate date and time input screen 400D on display 206 based on NG button 406 being pressed. The input screen 400</b>D includes an exchange partner display field 402 , an exchange candidate date and time input field 424 , and an OK button 426 .

A display column 402 displays user information of user A who is a communication partner. The user information displayed in the display column 402 includes, for example, an image of user A, a user name of user A, and hobbies of user A. The user information is obtained, for example, from the above-described user DB 124 (see FIG. 3).

The input field 424 is configured to accept inputs of exchange candidate dates and times in order of preference. The input of the candidate date and time for interaction is realized, for example, by specifying the date of interaction using a pull-down menu and specifying the time of interaction using a text box. If the text box is blank, terminal 200B assumes that no exchange candidate date and time has been entered.

The exchange candidate date and time is input from within the restricted date and time range. FIG. 15 is a diagram showing the relationship between a date/time range ΔTR1 in which user A can enter candidate exchange dates and times and a date/time range ΔTR2 in which user B can enter candidate exchange dates and times.

As described above with reference to FIG. 2, user A's input of exchange candidate date and time is accepted within the date and time range ΔTR1. Further, the start date and time T1S of the date and time range ΔTR1 was after the predetermined period ΔTP1 after the server 100 or the terminal 200A started accepting the input of the exchange candidate date and time (that is, the timing T0A).

On the other hand, user B's input of exchange candidate date and time is accepted within the date and time range ΔTR2. The start date and time T2S of the date and time range ΔTR2 is later than the start date and time T1S of the date and time range ΔTR1. As an example, the start date and time T2S of the date and time range ΔTR2 is a predetermined period after the server 100 or the terminal 200B starts accepting the input of the exchange candidate date and time (that is, the timing T0B).

The end date and time T2E of the date and time range ΔTR2 is later than the end date and time T1E of the date and time range ΔTR1. As an example, the end date and time T2E of the date and time range ΔTR2 is a certain time (for example, several days to several months) after the start date and time T2S of the date and time range ΔTR2.

In this way, server 100 allows terminal 200B to accept an input of an exchange candidate date and time different from the exchange candidate date and time within date and time range ΔTR2 after terminal 200B is notified of user A's candidate exchange date and time. At this time, since the start date and time T2S of the date and time range ΔTR2 is later than the start date and time T1S of the date and time range ΔTR1, the exchange candidate date and time input by the user B is in the past at the time of confirmation by the user A. less likely. Further, if the presented candidate date and time for interaction is earlier, user A can decide the date and time for interaction with user B after adjusting his/her own schedule.

Preferably, the server 100 changes the start date and time T2S of the date and time range ΔTR2 according to the timing when the user A uses the exchange support system 10 . FIG. 16 is a diagram showing a difference in the date and time range ΔTR2 depending on the timing when user A uses the exchange support system 10. As shown in FIG.

Timing T0B shown in FIG. 16 indicates the timing at which server 100 or terminal 200B starts accepting input of exchange candidate dates and times. The server 100 changes the start date and time T2S of the date and time range ΔTR2 depending on whether or not the user A who is the communication partner has been using the server 100 for a predetermined period ΔTP2 before the timing T0B. Whether or not the function of server 100 has been used for a predetermined period of time ΔTP2 is determined, for example, based on the aforementioned usage history 126 (see FIG. 3).

As an example, the server 100 determines that the user A used the function of the server 100 within the predetermined period ΔTP2 when the usage history 126 contains a record that the user A logged in to the predetermined period ΔTP2. Otherwise, the server 100 determines that the user A has not used the function of the server 100 within the predetermined period ΔTP2.

As another example, the server 100 determines that the user A used the function of the server 100 within the predetermined period ΔTP2 when there is a record in the usage history 126 that the user A logged out during the predetermined period ΔTP2. Otherwise, the server 100 determines that the user A has not used the function of the server 100 within the predetermined period ΔTP2.

If user A has already used the exchange support system 10 within the past predetermined period of time ΔTP2, the possibility that user A will use the exchange support system 10 immediately thereafter is low. In particular, this possibility is low when the exchange support system 10 is used infrequently (for example, about once a day).

Therefore, the server 100 sets the start date and time T2S of the date and time range ΔTR2 when the user A uses the function of the server 100 within the predetermined period ΔTP2. After the start date and time T2S' of the date and time range .DELTA.TR2 in the case where it has not been done. The period between the start date and time T2S and the start date and time T2S' is, for example, one day.

Further, the server 100 sets the end date T2E of the date range ΔTR2 when the user A uses the function of the server 100 within the predetermined period ΔTP2, and the user A uses the function of the server 100 within the predetermined period ΔTP2. After the end date and time T2E' of the date and time range ΔTR2 in the case where the date and time range ΔTR2 has not been set. The period between the end date and time T2E and the end date and time T2E' is, for example, one day.

As a result, the exchange support system 10 can set the date and time range ΔTR2 in accordance with the timing when the user A uses the system next time. This reduces the possibility that the exchange candidate date and time input by user B is in the past at the time of user A's confirmation. Further, if the presented candidate date and time for interaction is earlier, user A can decide the date and time for interaction with user B after adjusting his/her own schedule. As a result, online interaction between user A and user B is facilitated.

Referring to FIG. 13 again, in step S52, terminal 200B receives an input of an exchange candidate date and time convenient for user B from within date and time range ΔTR2. After that, the terminal 200B transmits the exchange candidate date and time input in the input field 424 to the server 100 based on pressing of the enter button 426 on the input screen 400D. Server 100 stores the exchange candidate date and time received from terminal 200B.

In step S54, the terminal 200B displays a confirmation screen for the exchange candidate dates and times that have been input. FIG. 17 is a diagram showing a confirmation screen 400E as an example.

The confirmation screen 400</b>E includes an exchange partner display field 402 , an exchange candidate date and time display field 432 , a connect button 434 , and a change button 436 . The display column 402 of the confirmation screen 400E displays the same content as the display column 402 of the selection screen 400A described above.

In the display field 432 of the exchange candidate date and time, the exchange candidate date and time input by the user B in step S52 is displayed.

The connect button 434 is a button for connecting to an exchange partner without waiting for the fixed exchange date and time. When the connection button 434 is pressed, communication between the terminal 200A and the terminal 200B is connected, and online exchange between the user A and the user B is started. The connection button 434 is used, for example, when the gap time between the user A and the user B coincides with each other.

The change button 436 is a button for canceling the fixed exchange date and time and readjusting the exchange date and time.

Referring to FIG. 13 again, it is assumed that user A accesses exchange support system 10 using terminal 200A after some time has passed since user B entered the exchange candidate date and time. Based on this, a login screen is displayed on the terminal 200A. The terminal 200</b>A transmits the input user information to the server 100 when the user A presses the login button after inputting the user information on the login screen.

At step S62, the server 100 determines whether or not the user information input at step S60 is registered in the above-described user DB 124 (see FIG. 3). When determining that the user information input in step S60 is registered in the user DB 124, the server 100 executes a login process and transmits a notification indicating that the login was successful to the terminal 200A. Otherwise, server 100 sends a notification to terminal 200A indicating that the login has failed.

In the example of FIG. 13, it is assumed that the login process was performed normally in step S62. After that, server 100 transmits the exchange candidate date and time input in step S52 to terminal 200A.

In step S64, terminal 200A displays on display 206 a selection screen for exchange candidate dates and times. Since the selection screen is the same as the selection screen 400A described above, the description thereof will not be repeated.

<F. Operation when there is no response after presentation of exchange candidate date and time>
Next, with reference to FIGS. 18 to 20, the operation of the exchange support system 10 when the user B does not respond to the exchange candidate dates and times presented by the user A for several days will be described.

FIG. 18 is a diagram showing an example of data flow between the server 100 and the terminals 200A and 200B. By executing steps S10, S12, S14, S16, S18, S22, S24, and S26 shown in FIG. 18, user A's candidate exchange date and time are input. These steps are as described in FIG. 5, so their description will not be repeated.

If user B does not log in to the exchange support system 10 for several days after user A has entered an exchange candidate date and time, the exchange candidate date and time may be the most recent/past date and time. Therefore, if terminal 200B has not received selection of an exchange candidate date and time within a predetermined period of time after user A's candidate exchange date and time has been accepted by terminal 200A, server 100 prompts the user to input an exchange candidate date and time. Accept again.

More specifically, in step S70, user A accesses exchange support system 10 using terminal 200A. Based on this, a login screen is displayed on the terminal 200A. The terminal 200</b>A transmits the input user information to the server 100 when the user A presses the login button after inputting the user information on the login screen.

At step S72, the server 100 determines whether or not the user information input at step S70 is registered in the above-described user DB 124 (see FIG. 3). When determining that the user information input in step S70 is registered in the user DB 124, the server 100 executes a login process and transmits a notification indicating that the login was successful to the terminal 200A. In the example of FIG. 18, it is assumed that the login process was performed normally in step S72. The result of the login process is written in the aforementioned usage history 126 after being associated with the user information and the login time.

In step S74, the terminal 200A displays the home screen. FIG. 19 shows an input screen 300E forming part of the home screen. The input screen 300E is displayed on the home screen when user B has not logged in to the exchange support system 10 for a predetermined period of time (for example, two days) after user A has entered an exchange candidate date and time.

The input screen 300</b>E includes an exchange partner display field 302 , a message 314 , an exchange candidate date and time input field 316 , and an OK button 318 .

The display field 302 of the input screen 300E displays the same contents as the display field 302 of the above-described input screen 300B (see FIG. 7).

The message 314 indicates that the user B has not confirmed the exchange candidate date and time input by the user A in step S22. By checking the message 314, the user A can understand that the user B has not used the exchange support system 10 for several days.

The input field 316 is configured to accept input of a new exchange candidate date and time. The input of the candidate date and time for interaction is realized, for example, by specifying the date of interaction using a pull-down menu and specifying the time of interaction using a text box. If the text box is blank, the terminal 200A assumes that no exchange candidate date and time has been entered.

A new exchange candidate date and time is input from within the restricted date and time range. FIG. 20 is a diagram showing the relationship between a date/time range ΔTR1 when user A first inputs an exchange candidate date/time and a date/time range ΔTR3 when user A inputs a new exchange candidate date/time.

As described above, the input of the first exchange candidate date and time is accepted within the date and time range ΔTR1. On the other hand, the input of a new exchange candidate date and time is accepted within the date and time range ΔTR3.

The start date and time T3S of the date and time range ΔTR3 is later than the start date and time T1S of the date and time range ΔTR1. The end date and time T3E of the date and time range ΔTR3 is later than the end date and time T1E of the date and time range ΔTR1. As an example, the end date and time T3E of the date and time range ΔTR3 is a certain time (for example, several days to several months) after the start date and time T3S of the date and time range ΔTR3.

Further, the start date and time T3S of the date and time range ΔTR3 is later than the start date and time T2S of the above-described date and time range ΔTR2 (see FIG. 16). Furthermore, the end date and time T3E of the date and time range ΔTR3 is later than the end date and time T2E of the above-described date and time range ΔTR2.

In this way, if terminal 200B has not received selection of an exchange date and time before a predetermined period (for example, two days) has elapsed since the candidate exchange date and time was accepted at terminal 200A, server 100 selects a different exchange date and time. The terminal 200A is made to receive the input of the candidate date and time from within the date and time range ΔTR3. Since the user A can input the exchange candidate date and time from the date and time range ΔTR3 later than the date and time range ΔTR1, the exchange candidate date and time will be input from the date and time range earlier than the first input. This reduces the possibility that the exchange candidate date and time newly input by user A is past date and time when user B confirms. As a result, online interaction between user A and user B is facilitated.

In the above description, an example in which User A inputs a new candidate exchange date and time when User B has not used the exchange support system 10 for a predetermined period of time has been described. may be entered by In this case, if terminal 200B has not received selection of an exchange date and time within a predetermined period of time (for example, two days) after terminal 200A accepts the candidate exchange date and time, server 100 selects a different exchange candidate. The terminal 200B is made to accept the date and time input from within the date and time range ΔTR3.

Terminal 200A transmits the exchange candidate date and time entered in input field 316 to server 100 based on pressing of enter button 318 on input screen 300E. Server 100 stores the new exchange candidate date and time received from terminal 200A.

The server 100 transmits the new exchange candidate date and time to the terminal 200B at arbitrary timing. As an example, the server 100 transmits new candidate exchange dates and times to the terminal 200B at the timing when the user B logs into the exchange support system 10 .

<G. Operation when starting online exchange without waiting for the confirmed exchange date and time>
Next, with reference to FIGS. 21 and 22, the operation of the exchange support system 10 in the case of starting online exchange without waiting for the exchange date and time after the exchange date and time of users A and B is fixed will be described.

FIG. 21 is a diagram showing an example of data flow between the server 100 and the terminals 200A and 200B.

When online exchange is started without waiting for the fixed exchange date and time, user A first accesses the exchange support system 10 in step S80. Based on this, a login screen is displayed on the terminal 200A. The terminal 200</b>A transmits the input user information to the server 100 when the user A presses the login button after inputting the user information on the login screen.

At step S82, the server 100 determines whether or not the user information input at step S80 is registered in the above-described user DB 124 (see FIG. 3). When determining that the user information input in step S80 is registered in the user DB 124, the server 100 executes a login process and transmits a notification indicating that the login was successful to the terminal 200A. In the example of FIG. 21, it is assumed that the login process was performed normally in step S82.

In step S84, the terminal 200A displays the home screen. FIG. 22 shows a reminder screen 300F forming part of the home screen.

The reminder screen 300F is displayed each time the user logs in after the fixed exchange date and time is fixed. The reminder screen 300</b>F includes a display field 322 for the confirmed exchange date and time, a connection button 324 and a change button 326 .

The display column 322 displays the user information of the next interaction partner, the confirmed exchange date and time, and a message for prompting to record the confirmed exchange date and time in the calendar.

The connection button 324 is a button for communication connection with an exchange partner without waiting for the fixed exchange date and time. When the connection button 324 is pressed, communication between the terminal 200A and the terminal 200B is connected, and online communication between the user A and the user B is started.

As an example, assume that the connection button 324 is pressed in step S84 shown in FIG. Based on this, the terminal 200A transmits a connection request to the server 100. FIG. The connection request includes the IP address of terminal 200B, which is the connection destination, and the like. Upon receiving the connection request from terminal 200A, server 100 transmits the connection request to terminal 200B. Note that the connection request may be directly transmitted from the terminal 200A to the terminal 200B without going through the server 100. FIG.

In step S<b>90 , the terminal 200</b>B displays a connection permission/prohibition selection screen based on the reception of the connection request from the server 100 . As an example, the selection screen includes an OK button and an NG button. When the OK button is pressed, terminal 200B permits communication connection with terminal 200A. When the NG button is pressed, terminal 200B rejects communication connection with terminal 200A.

In the example of FIG. 21, it is assumed that the OK button is pressed in step S90. Based on this, the terminal 200B transmits a connection request to the server 100. FIG. The connection request includes the IP address of terminal 200A, which is the connection destination, and the like. Upon receiving the connection request from terminal 200B, server 100 transmits the connection request to terminal 200A. Note that the connection request may be directly transmitted from the terminal 200B to the terminal 200A without going through the server 100. FIG.

In step S92, a process for connecting the terminals 200A and 200B for communication is executed. Thereby, user A and user B can start online interaction.

In addition, although the example in which the communication connection operation is accepted by the terminal 200A has been described above, the communication connection operation may be accepted by the terminal 200B.

<H. Operation when changing the fixed exchange date and time>
Next, with reference to FIGS. 23 to 25, the operation of the exchange support system 10 when changing the exchange date and time after the exchange date and time between the user A and the user B is fixed will be described.

FIG. 23 is a diagram showing an example of data flow between the server 100 and terminals 200A and 200B.

When changing the fixed exchange date and time, user A first accesses the exchange support system 10 in step S100. Based on this, a login screen is displayed on the terminal 200A. The terminal 200</b>A transmits the input user information to the server 100 when the user A presses the login button after inputting the user information on the login screen.

At step S102, the server 100 determines whether or not the user information input at step S100 is registered in the above-described user DB 124 (see FIG. 3). When determining that the user information input in step S100 is registered in the user DB 124, the server 100 executes a login process and transmits a notification indicating that the login was successful to the terminal 200A. In the example of FIG. 23, it is assumed that the login process was performed normally in step S102.

In step S104, the terminal 200A displays the home screen. FIG. 24 is a diagram showing a reminder screen 300G forming part of the home screen.

The reminder screen 300G is displayed at each login after the fixed exchange date and time is fixed. The reminder screen 300</b>G includes a display field 330 for the confirmed exchange date and time, an input field 332 for time, an OK button 334 , and a Cancel button 336 .

The display field 330 displays the user information of the next interaction partner, the date and time of the confirmed interaction, and a message prompting the user to record the date and time of the confirmed interaction on the calendar.

The input field 332 accepts the input of the exchange date and time after the change. At this time, the input field 332 may be configured to accept the input of the time and not to accept the input of the date. In this case, user A can change the time of the fixed exchange date and time, but cannot change the date.

In the example of FIG. 24, “10/4 (Monday) 08:00~” is shown as the fixed exchange date and time, and “09:15” is entered in the input field 332 . In this case, the exchange date and time is changed to "10/4 (Monday) 09:15~".

When the OK button 334 is pressed, the terminal 200A transmits the exchange date and time after the change to the server 100 . When the cancel button 336 is pressed, the terminal 200A closes the reminder screen 300G without transmitting the changed exchange date and time to the server 100. FIG.

Assume that the OK button 334 is pressed in step S104. Based on this, the terminal 200A transmits the exchange date and time after the change to the server 100 . Server 100 transmits the changed exchange date and time to terminal 200B based on having received the changed exchange date and time from terminal 200A. Note that the exchange date and time after the change may be directly transmitted from the terminal 200A to the terminal 200B without going through the server 100 .

After that, in step S110, user B accesses exchange support system 10 using terminal 200B. Based on this, a login screen is displayed on the terminal 200B. The terminal 200B transmits the input user information to the server 100 based on the user B inputting the user information on the login screen and pressing the login button.

At step S112, the server 100 determines whether or not the user information input at step S110 is registered in the above-described user DB 124 (see FIG. 3). In the example of FIG. 23, it is assumed that the login process was performed normally in step S112.

In step S114, the terminal 200B displays the home screen. FIG. 25 shows a request screen 400G forming part of the home screen.

As shown in FIG. 25 , the request screen 400G includes a display field 440 for the fixed exchange date and time before change, a request message 442 , an OK button 444 and an NG button 446 .

The display field 440 displays the user information of the next interaction partner, the confirmed exchange date and time before change, and a message for prompting to record the confirmed exchange date and time before change on the calendar.

The request message 442 is a message indicating that a request for changing the confirmed exchange date and time has been received. Request message 442 includes the date and time of exchange after change input in step S104.

When the OK button 444 is pressed, the terminal 200B transmits to the server 100 a notification indicating acceptance of the changed exchange date and time as a response result. When the NG button 446 is pressed, the terminal 200A transmits to the server 100, as a response result, a notification indicating that the exchange date and time after the change has been rejected. The answer result is notified, for example, when user A logs into server 100 using terminal 200A.

In addition, although the example in which the request screen 400G is displayed when the user B logs in has been described above, the display timing of the request screen 400G is arbitrary. As an example, the request screen 400G may be displayed at the end of execution of the above-described brush-up function. Also, the request screen 400G may be displayed as a pop-up screen.

Also, the request screen 400G may be displayed multiple times. As an example, the request screen 400G may be displayed at the time of user B's login and at the end of execution of the brush-up function.

<I. Reminder screen after the exchange date and time is confirmed>
Next, referring to FIG. 26, the reminder function after the exchange date and time is fixed will be described. FIG. 26 is a diagram showing a reminder screen 300H that is periodically displayed after the exchange date and time are fixed.

In the example of FIG. 26, a reminder screen 300H displayed on user A's terminal 200A is shown. The reminder screen 300H is a screen for reminding the user that there is a schedule for online exchange.

The reminder screen 300H can be displayed at any timing. As an example, the reminder screen 300H is displayed at the end of execution of the above-described brush-up function. As another example, the reminder screen 300</b>H is displayed at the timing when the user logs into the server 100 . As another example, the reminder screen 300H is displayed as a pop-up screen at a pre-scheduled time.

The reminder screen 300F includes a confirmation message 340, a timer 341, and an OK button 342.

The confirmation message 340 includes a message including the confirmed exchange date and time and a message for prompting recording of the confirmed exchange date and time. FIG. 26 shows a message "The next connection is set for 10/4 (Monday) 08:00" as an example of the message including the fixed exchange date and time. Also, as an example of a message for prompting recording of the fixed exchange date and time, a message "Have you made a note on the calendar so as not to forget it?" is shown.

A timer 341 displays the time until the reminder screen 300H is closed. The terminal 200A closes the reminder screen 300H when the remaining time of the timer 341 reaches zero.

The OK button 342 is a button for closing the reminder screen 300H. User A presses the OK button 342 after confirming the reminder screen 300H. Thereby, the user A can close the reminder screen 300H before the remaining time of the timer 341 reaches zero.

In addition, although the example in which the reminder screen 300H is displayed on the terminal 200A of the user A has been described above, the reminder screen may be displayed on the terminal 200B of the user B who is the communication partner.

<J. Operation when online exchange is canceled on the day>
Next, the operation of the exchange support system 10 when the online exchange is canceled on the day of the fixed exchange date and time will be described with reference to FIGS. 27 to 30. FIG.

FIG. 27 is a diagram showing an example of a data flow between the server 100 and terminals 200A and 200B.

Examples of the case where online interaction is canceled on the day of the fixed date and time of interaction include the case where users A and B forget the schedule for online interaction, and the case where users A and B cancel online interaction just before. .

If the online exchange is canceled on the day of the confirmed exchange date and time, the exchange candidate date and time will be reset. When user A resets the fixed exchange date and time, user A first accesses the exchange support system 10 in step S120. Based on this, a login screen is displayed on the terminal 200A. The terminal 200</b>A transmits the input user information to the server 100 when the user A presses the login button after inputting the user information on the login screen.

At step S122, the server 100 determines whether or not the user information input at step S120 is registered in the above-described user DB 124 (see FIG. 3). When determining that the user information input in step S120 is registered in the user DB 124, the server 100 executes a login process and transmits a notification indicating that the login was successful to the terminal 200A. In the example of FIG. 27, it is assumed that the login process was performed normally in step S122.

In step S124, the terminal 200A displays the home screen. FIG. 28 is a diagram showing an input screen 300I forming part of the home screen. The input screen 300I is displayed on the home screen when the online exchange is canceled on the day of the confirmed exchange date and time.

The input screen 300</b>I includes an exchange partner display field 302 , a message 348 , an exchange candidate date and time input field 350 , a connect button 352 , and an enter button 354 .

The display field 302 of the input screen 300I displays the same contents as the display field 302 of the above-described input screen 300B (see FIG. 7).

Message 348 includes a message indicating that user B has canceled the online interaction on the day of the fixed date and time of interaction, and a message for prompting resetting of the date and time of interaction. In this way, when the online exchange at the confirmed exchange date and time is canceled on the day, the server 100 sends a notification to the terminal 200A to prompt the user to reset the exchange date and time.

By checking the message 348, User A can recognize that the online interaction has been cancelled. Note that message 348 may be sent to either terminal 200A or terminal 200B, or may be sent to both terminal 200A and terminal 200B.

The input field 350 is configured to accept input of a new exchange candidate date and time. The input of the candidate date and time for interaction is realized, for example, by specifying the date of interaction using a pull-down menu and specifying the time of interaction using a text box. If the text box is blank, the terminal 200A assumes that no exchange candidate date and time has been entered.

The exchange candidate date and time is input from within the restricted date and time range. FIG. 29 is a diagram schematically showing how a new exchange candidate date and time is input from within the date and time range ΔTR4.

Referring to FIG. 29, server 100 allows terminal 200A to accept resetting of candidate exchange date and time within date and time range ΔTR4 when online interaction at the fixed date and time is canceled on the current day. Note that the server 100 may allow the terminal 200B to accept resetting of the exchange candidate date and time.

The start date and time T4S of the date and time range ΔTR4 is a predetermined period ΔTP4 after the server 100 or the terminal 200A starts accepting the input of the new exchange candidate date and time (that is, the timing T0A′).

At this time, the predetermined period ΔTP4 is shorter than the predetermined period ΔTP1 (see FIG. 2). As a result, if the online interaction is canceled on the day, the user A can select an interaction candidate date and time from the most recent date.

As an example, the predetermined period ΔTP1 is 3 to 4 days, and the predetermined period ΔTP4 is 1 to 2 days. Alternatively, the predetermined period ΔTP4 may be several hours (for example, one hour). Alternatively, the predetermined period ΔTP4 may be zero.

The start date and time T4S of the date and time range ΔTR4 is later than the start date and time T1S of the date and time range ΔTR1. The end date and time T4E of the date and time range ΔTR4 is later than the end date and time T4E of the above-described date and time range ΔTR1. As an example, the end date and time T4E of the date and time range ΔTR4 is a certain time (for example, several days to several months) after the start date and time T4S of the date and time range ΔTR4.

The start date and time T4S of the date and time range ΔTR4 is later than the start date and time T2S of the date and time range ΔTR2 (see FIG. 16). The end date and time T4E of the date and time range ΔTR4 is later than the end date and time T2E of the above-described date and time range ΔTR2.

Further, the start date and time T4S of the date and time range ΔTR4 is after the start date and time T3S of the above-described date and time range ΔTR3 (see FIG. 20). The end date and time T4E of the date and time range ΔTR4 is later than the end date and time T3E of the date and time range ΔTR3.

Terminal 200A transmits the exchange candidate date and time entered in input field 350 to server 100 based on pressing of enter button 354 on input screen 300I. Server 100 stores the exchange candidate date and time received from terminal 200A.

The connection button 352 is a button for communication connection with an exchange partner without inputting a new exchange candidate date and time. When the connection button 324 is pressed, communication between the terminal 200A and the terminal 200B is connected, and online communication between the user A and the user B is started. In the example of FIG. 27, it is assumed that the OK button 354 is pressed without the connection button 352 being pressed in step S124.

Referring to FIG. 27 again, it is assumed that user B accesses exchange support system 10 using terminal 200B in step S130 after some time has passed since user A entered the exchange candidate date and time. Based on this, a login screen is displayed on the terminal 200B. The terminal 200B transmits the input user information to the server 100 based on the user B inputting the user information on the login screen and pressing the login button.

At step S132, the server 100 determines whether or not the user information input at step S130 is registered in the above-described user DB 124 (see FIG. 3). If the server 100 determines that the user information input in step S130 is registered in the user DB 124, the server 100 executes a login process and transmits a notification indicating that the login was successful to the terminal 200B. In the example of FIG. 27, it is assumed that the login process was performed normally in step S132. After that, server 100 transmits the exchange candidate date and time input in step S124 to terminal 200B.

In step S134, terminal 200B displays on display 206 a selection screen for exchange candidate dates and times. FIG. 30 is a diagram showing a selection screen 400H as an example.

As shown in FIG. 30 , the selection screen 400</b>H includes an exchange partner display field 402 , a message 452 , an exchange candidate date and time selection field 454 , and an NG button 456 .

The display field 402 of the selection screen 400H displays the same content as the display field 402 of the above-described selection screen 400A (see FIG. 10).

The message 452 includes a message indicating that online interaction has been canceled on the day of the fixed date and time of interaction, and a message for prompting selection of a candidate interaction date and time.

In the selection field 454, the exchange candidate dates and times input by the user A in step S124 are displayed in order of preference. A determination button 455 is displayed in line with each of the exchange candidate dates and times. User B can select his/her desired exchange candidate date and time by pressing one decision button 455 . Based on the decision button 455 being pressed, the terminal 200B transmits the selected exchange candidate date and time to the server 100 . The exchange candidate dates and times transmitted to server 100 are transmitted to terminal 200A when user A logs into exchange support system 10, for example.

The NG button 456 is a button for rejecting the exchange candidate date and time displayed on the selection screen 450H. The processing when NG button 456 is pressed is as described above with reference to FIGS. 13 to 17, so description thereof will not be repeated.

In addition, in the example of FIG. 27, an example was described in which user B's consent is sought for the new candidate date and time for interaction proposed by user A, but the consent may not be requested. As an example, in preparation for a case where user A and user B verbally decide on an exchange date and time, server 100 may store an exchange date and time received from either terminal 200A or terminal 200B as a new confirmed exchange date and time. . In this case, the server 100 does not execute the process of accepting the selection of the exchange candidate date and time. That is, a new exchange date and time is determined without executing the process of step S134.

<K. Notification screen of failure to establish an exchange date and time>
Next, with reference to FIG. 31, the notification function when the exchange date and time is not fixed within a certain period of time will be described. FIG. 31 is a diagram showing a notification screen 300J indicating that an exchange has not been established.

Server 100 displays notification screen 300J on at least one of terminal 200A and terminal 200B when a condition indicating that exchange is not established (hereinafter, also referred to as "non-establishment condition") is satisfied. The notification screen 300J includes a message 360 indicating that the exchange is not established.

As an example, the above unsatisfied condition is met when user A and user B have adjusted the date and time of interaction a predetermined number of times. The unsatisfied condition is satisfied, for example, based on user B rejecting the exchange candidate date and time presented by user A, and then user A rejecting the exchange candidate date and time presented by user B.

As another example, the non-satisfaction condition is satisfied when the exchange date and time are not determined within a certain period of time. More specifically, the server 100 is satisfied when the exchange date and time between the user A and the user B are not confirmed within a predetermined period of time after the first candidate exchange date and time is accepted at the terminal 200A. . The predetermined period may be shorter or longer than the above-described predetermined period ΔTP1 (see FIG. 2). The predetermined period is, for example, one week.

The notification screen 300J can be displayed at any timing. As an example, notification screen 300J is displayed at the end of execution of the above-described brush-up function. As another example, the notification screen 300J is displayed when the user logs into the server 100 . As another example, notification screen 300J is displayed as a pop-up screen at a pre-scheduled time.

<L1. Others>
In the above description, an example of adjusting the date and time of exchange on one line between user A's terminal 200A and user B's terminal 200B has been described. However, the adjustment of the exchange date and time may be performed on multiple lines at the same time.

As an example, the terminal 200A may execute the exchange date and time adjustment process with the user C's terminal 200C (see FIG. 1) while executing the exchange date and time adjustment process with the user B's terminal 200B. Preferably, the server 100 causes the terminal 200A to accept input of candidate dates and times for interaction between the user A and the user C after the dates and times for the interaction between the user A and the user B are fixed. In other words, the server 100 does not adjust the date and time of interaction with other users until the date and time of interaction between user A and user B are determined. As a result, the server 100 prevents the user from adjusting the exchange date and time many times at the same time. As a result, it is possible to reduce the user's burden related to the adjustment of the exchange date and time.

Assume that user A completes the adjustment of the exchange date and time with user B in the latter half of the week, and the exchange date and time are fixed for the next week. In this case, user A can also adjust the exchange date and time for the next week at the same time. As an example, it is assumed that on-line interaction between user A and user B is decided on "Tuesday of the second week" on Thursday of the first week. In this case, user A can start adjusting the date and time of interaction with user C from Monday of the second week. If the date and time of interaction between user A and user C are determined to be "Friday of the second week", user A will have online interaction with another partner twice a week.

Preferably, the server 100 determines the maximum number of lines that can simultaneously adjust the exchange date and time based on at least one of the user's busyness, the user's personality tendency, the user's responsiveness, and other information. change. The maximum number of lines means the maximum number of lines that one user can coordinate with other users in parallel. As an example, a user whose maximum number of lines is 2 can adjust the exchange date and time on the exchange support system 10 at the same time as two other users. Each user's busyness, each user's personality tendency, and each user's responsiveness are, for example, digitized and defined in advance in the above-described user DB 124 (see FIG. 3).

As an example, the server 100 reduces the maximum number of lines for busy users, and increases the maximum number of lines for idle users. As another example, the server 100 reduces the maximum number of lines for less social users and increases the maximum number of lines for more social users. As another example, the server 100 reduces the maximum number of lines for users with lower responsiveness, and increases the maximum number of lines for users with higher responsiveness. Note that the maximum number of lines may be manually set for each user.

As a more specific example, server 100 sets the maximum number of lines to a first value (for example, 1) when the degree of busyness of the user is equal to or greater than a predetermined value. On the other hand, the server 100 sets the maximum number of lines to a second value (for example, 2 or 3) larger than the first value when the user's degree of busyness is less than the predetermined value.

As another example, server 100 sets the maximum number of lines to a first value (for example, 1) for users with low sociability in the Big Five. On the other hand, server 100 sets the maximum number of lines to a second value (for example, 2 or 3) larger than the first value for users with high sociability in the Big Five.

As another example, the server 100 sets the maximum number of lines to a first value (for example, 1) for users with low responsiveness. For the responsiveness, for example, as one of the components of resilience, an index representing the user's problem-solving ability calculated from the user's answers to a plurality of questions is used. Each user's responsiveness is defined in advance, for example, in the above-described user DB 124 . On the other hand, server 100 sets the maximum number of lines to a second value (for example, 2 or 3) larger than the first value for users with high responsiveness.

<L2. Others>
Further, in the above description, the server 100 does not accept the input of the reason for the rejection when the candidate date and time for interaction proposed by the interaction partner is rejected. However, the server 100 may cause the terminal 200 to receive an input of the reason for rejecting the proposed exchange candidate date and time. The reason may be received by text input or may be received from among predetermined options. The entry fields are provided, for example, in the above-described selection screen 400A (see FIG. 10) and the above-described request screen 400G (see FIG. 25).

<L3. Others>
Also, in the above description, an example has been described in which input/selection of various information such as exchange candidate date and time is realized on the screen using an input device such as a mouse. However, input/selection of various information may be realized by voice input. In this case, terminal 200 has an audio input unit such as a microphone. The voice input to the voice input unit is voice-processed by the server 100 or the terminal 200 .

Also, in the above description, an example has been described in which output of various types of information such as notification of exchange candidate dates and times is realized using a display device such as a display. However, the means for outputting various information is not limited to the display device. As an example, the output of various information may be realized by voice output. In this case, the terminal 200 serves as an audio output unit such as a speaker. The server 100 causes the terminal 200 to output various notifications through the audio output unit. As an example, when user A inputs an exchange candidate date and time, the server 100 causes the terminal 200B to output a voice saying "the exchange candidate date and time has arrived from user A."

The output of various information may be realized by hologram display. Alternatively, the output of various information may be realized using a wearable terminal. FIG. 32 is a diagram showing an example in which a notification indicating that user A has entered an exchange candidate date and time is displayed on terminal 200 as a wearable terminal. In the example of FIG. 32, the notification is displayed on the display 206 of the wearable terminal.

Preferably, the mode of outputting various information and the method of outputting various information may be changed according to the user data defined in the above-described user DB 124 (see FIG. 3). The user data includes, for example, at least one of a user's personality tendency, a user's ability indicated by IQ (Intelligence Quotient), EQ (Educational Quotient), or the like, and user settings.

As an example, terminal 200 increases the amount of information to be output for users with high capabilities. On the other hand, terminal 200 reduces the amount of information to be output for users with low capabilities. Methods for reducing the amount of information include, for example, short articles, visualization using graphs and diagrams, and the like. Also, the terminal 200 may output information by voice to a user with low ability.

Examples of output terminals of various information include wearable terminals, hologram devices, PC terminals, and mobile terminals such as smartphones. If the user has multiple types of output terminals, the server 100 changes the information output destination according to the user's current situation. As an example, the server 100 causes the wearable terminal to output information when the user is wearing the wearable terminal while away from home. Further, the server 100 causes the PC terminal to output information when the user is operating the PC terminal. Moreover, it is highly probable that the user puts the smartphone by the bedside during sleeping hours. In this case, the server 100 causes the smartphone to output information. A user's sleep time is preset, for example.

<L4. Others>
In addition, in the above description, input screen 300B (refer to FIG. 7), input screen 300E (refer to FIG. 19), input screen 300I (refer to FIG. 28), and input screen 400D (refer to FIG. An example of accepting up to three candidates has been described. However, the number of exchange candidate dates and times that can be input is not limited to three. The number of exchange candidate dates and times that can be input may be one or more.

The number of exchange candidate dates and times that can be input may be determined in advance, or may be arbitrarily set by the user. Preferably, the number of exchange candidate dates and times that can be input is changed according to the user's personality tendency, degree of busyness, and the like. A user's personality traits are part of the Big Five (i.e., openness, conscientiousness, extraversion, agreeableness, and neuroticism) and the components of resilience in psychology (e.g., axis, flexible thinking, responsiveness, human connection, self-control, and lifestyle) and other indicators.

As an example, terminal 200A reduces the number of exchange candidate dates and times that can be input for a user whose neuroticism indicates that he or she is susceptible to psychological stress, in order to reduce the stress caused by selection. In this case, for example, two possible exchange dates and times are set.

In addition, terminal 200A increases the number of exchange candidate dates and times that can be input for users whose neurotic tendencies indicate that they are less susceptible to psychological stress. In this case, the number of exchange candidate dates and times that can be input is set to, for example, three or four.

As another example, the terminal 200A reduces the number of exchange candidate dates and times that can be input for a user with low responsiveness in order to reduce the stress caused by selection. In this case, for example, two possible exchange dates and times are set.

In addition, terminal 200A increases the number of exchange candidate dates and times that can be input for a user with high responsiveness. In this case, the number of exchange candidate dates and times that can be input is set to, for example, three or four.

<L5. Others>
Further, in the above description, the input screen 300B (see FIG. 7), the input screen 300E (see FIG. 19), the input screen 300I (see FIG. 28), and the input screen 400D (see FIG. 14) accept the input of the exchange candidate date and time. had been At this time, the server 100 may refer to the user's schedule information.

As a more specific process, the server 100 acquires the user's schedule information from the terminal 200 . The schedule information is obtained, for example, from a calendar application (eg, Google Calendar) installed on terminal 200 . Alternatively, the schedule information may be obtained from a calendar application on the cloud server. Alternatively, the schedule information may be obtained from a pre-registered electronic notebook.

The schedule information may be acquired only from user A's terminal 200A, may be acquired only from user B's terminal 200B, or may be acquired from both terminal 200A and terminal 200B.

The server 100 acquires a time slot in which the user's schedule is already filled from the acquired schedule information, and causes the terminal 200 to present the time slot.

<L6. Others>
In addition, the exchange candidate date and time may be input using a guide function based on voice recognition processing, may be input using a guide function combining screen effects and text information, or may be input using a dialogue function. may be

As an example of using the dialogue function, the terminal 200 outputs a message "Your schedule for the period near the exchange candidate date and time is ..." by voice. In response to this, the user inputs into the terminal 200 a voice saying, "Are you busy during that period?" Based on this, terminal 200 calculates the degree of busyness around the candidate exchange date and time based on the schedule information. The degree of busyness is calculated based on, for example, the number of registered schedules, the length of time of the registered schedules, and the like. If the degree of busyness exceeds a predetermined value, the terminal 200 outputs a voice response saying, "You may have a little too much schedule." After that, the user inputs into the terminal 200 a voice saying, "Make a reservation for ~ date." This completes the input of the exchange candidate date and time.

<L7. Others>
In addition, when the degree of busyness of the user, the degree of busyness of the team to which the user belongs, or the degree of busyness of the exchange partner exceeds a predetermined value, the terminal 200 selects an exchange candidate from a plurality of predetermined candidates. The user may be assisted to select the date and time. By designating the candidate exchange date and time to some extent, it is possible to reduce the trouble of selecting the candidate exchange date and time.

Further, the terminal 200 may present candidate exchange dates and times according to the user, based on the aforementioned usage history 126 (see FIG. 3) or the user's schedule information. As an example, assume that User A's system utilization is high on certain days of the week (eg, Monday, Wednesday, and Friday). In this case, the terminal 200 presents the date and time of the specific day of the week as the exchange candidate date and time.

Preferably, the terminal 200 further uses the usage history 126 (see FIG. 3) of the interaction partner or the schedule information of the interaction partner to present the candidate date and time for interaction according to the user. As an example, assume that User A's system utilization is high on certain days of the week (eg, Monday, Wednesday, and Friday). It is also assumed that the system utilization rate of user B, who is the interaction partner, is high on other days of the week (for example, Monday, Tuesday, and Wednesday). It is also assumed that user A or user B schedules a meeting every Monday in the schedule information. In this case, the terminal 200 presents the date and time of Wednesday, which is a day of the week when users A and B have a high system usage rate and has no schedule, as a candidate date and time for interaction.

Further, in the above description, an example has been described in which the exchange support system 10 supports the user to select a candidate exchange date and time from a plurality of predetermined candidates. It can include not only how to do it, but also how to get approval.

As an example of a method of obtaining approval, the server 100 stores the schedule information of the user scheduled to interact, the degree of busyness of the user, the usage history 126, the relationship between the users, the possibility of having a schedule, and the user's schedule. One or more candidate exchange dates and times are tentatively determined based on at least one of the occupation and other information. The user's schedule information is obtained, for example, from Google Calendar or a schedule management device/software. Human relationships between users are represented, for example, by whether or not they are on good terms, or by the relationship between superiors and subordinates. Based on the tentatively decided candidate exchange date and time, the server 100 obtains approval from the user for the tentatively decided candidate exchange date and time.

If there are a plurality of tentatively determined exchange candidate dates and times, priority and whether or not to participate may be given. The priority and whether or not to participate are input by the user, for example. The server 100 determines an exchange candidate date and time that has a high priority and is available for participation as a confirmed exchange date and time.

As another example, the server 100 may propose an exchange candidate date and time in the near future when the relationship between users scheduled to interact is not good. As a result, the online exchange can be implemented earlier, and the user's mental burden can be reduced until the online exchange is implemented. In this case, the server 100 may cause the terminal 200 to display a message "Why don't you have an online exchange today?"

As another example, the server 100 may determine exchange candidate dates and times based not only on the user's future schedule information, but also on the user's past schedule information. As an example, the server 100 estimates the user's schedule based on past schedule information patterns, the user's occupation, and the status of the organization to which the user belongs. After that, the server 100 determines an exchange candidate date and time based on the estimated schedule, and presents the exchange candidate date and time to each user. Alternatively, server 100 may determine a combination of candidate exchange dates and times based on the estimated schedule.

As an example, it is assumed that user A has weekly meetings at 13:00 on Mondays and frequently holds meetings with external parties on Wednesdays from 13:00 to 15:00. In such a case, the user is likely to schedule a meeting on Monday and Wednesday even though the meeting was not scheduled in the schedule information for Monday and Wednesday. The server 100 may identify such a pattern of schedule information, and exclude days of the week on which there is a high possibility that a schedule will be included from the exchange candidate dates and times.

Preferably, server 100 performs the same process for user B, who is an interaction partner, and similarly determines an interaction candidate date and time to be excluded. In this case, the server 100 determines the exchange candidate date and time from the time slots when both users A and B are available.

If users A and B have the same occupation (for example, sales), they may have the same schedule (for example, internal meeting). In such a case, the server 100 may estimate the future schedule information of one of the users A and B from the past schedule information of the other user. After that, the server 100 determines exchange candidate dates and times based on the estimated schedule information.

In addition, the server 100 reduces the maximum number of lines for a user who is expected to become more busy during a specific period of time, such as starting a new project or responding to an emergency, in a certain department or team. Alternatively, the input date and time range ΔTR1 (see FIG. 2) may be widened. As a result, it is possible to reduce the burden on the user during the busy season. As a result, it becomes easier for users to interact online.

In addition, depending on the degree of busyness of the user and the user's mental state estimated from the user's biodata, the server 100 may allow a predetermined time (hereinafter also referred to as "slack time") from the schedule before or after the schedule. You may present an exchange candidate date and time as follows. This can prevent the schedule from becoming overcrowded. In addition, when the server 100 determines that the conversation itself will be a rest for the mind, the server 100 determines how much leeway is allowed in the schedule for interaction according to how busy the schedule is and whether the user is in a hurry or not. It may be determined automatically whether to present a candidate date and time.

In addition, the server 100 estimates the optimum time zone for presenting the exchange candidate date and time, the free time before and after, or the content of the conversation, based on the user data defined in the above-described user DB 124 (see FIG. 3), May decide/suggest. This maintains the user's mental health.

<L8. Others>
In addition, the server 100 may limit the date and time of exchange candidates that can be input based on the schedule information of the exchange partner. Whether or not to allow the restriction may be set in advance by the user or the contact. In addition, the content of the schedule of the communication partner may not be notified from the viewpoint of privacy.

<L9. Others>
Further, the server 100 may refer to the schedule information of the exchange partner, extract a blank period without a plan, and determine the candidate date and time for the exchange based on the blank period. As an example, the server 100 determines the date and time in the middle of the blank period as the candidate date and time for interaction.

<L10. Others>
Moreover, the server 100 may estimate the travel time for each schedule registered in the schedule information based on the location information, position information, etc. set in the calendar. The travel time may be input by voice using natural language processing. If the server 100 has a schedule before or after a certain date and time and it is estimated that sufficient free time will not be secured for that date and time due to the scheduled travel time, the server 100 excludes that time from the candidate exchange date and time.

<L11. Others>
Also, the server 100 may present the schedule information of one of the users A and B to the other user. The other user confirms the presented schedule information and then inputs the exchange candidate date and time. After that, the other user confirms the exchange date and time candidates input by the one user, and selects one of the exchange date and time candidates.

<L12. Others>
In addition, the exchange candidate date and time that can be input may be set in advance by the user. As an example, the user presets an invalid date and time range. An invalid date and time range is set using, for example, a calendar app. As an example, a user who does not want to work after a predetermined time (for example, after 22:00) presets the time after that time as an invalid date and time range. The server 100 excludes the set invalid date and time range from the exchange candidate dates and times that can be input. Note that the server 100 may accept valid date and time range settings instead of invalid date and time range settings.

Preferably, the server 100 extracts a free time slot in which the user has no schedule from the time slots excluding the invalid date and time range. After that, the server 100 identifies the longest available time slot, and presents candidate exchange dates and times belonging to that available time slot. In this way, the server 100 may prioritize the proposed exchange date and time.

Moreover, the server 100 may learn an input pattern of interaction date and time by a user by machine learning technology (for example, multivariable regression, classification tree, neural network, etc.) based on the history of interaction date and time of each user. More specifically, the server 100 uses the learned model generated by the learning to estimate an input pattern of interaction dates and times by each user. After that, the server 100 presents the estimated exchange date and time as an exchange candidate date and time. As an example, when user A and user B have interacted online multiple times in the past, server 100 determines days of the week and dates and times of past online interactions as candidate dates and times for interaction.

<L13. Others>
Also, in the above description, an example in which the user A first inputs the exchange candidate date and time has been described, but the user B may be the first user to input the exchange candidate date and time.

Also, the user who first enters the exchange candidate date and time may be automatically determined. As an example, the server 100 calculates the degree of busyness of each of the users A and B from the schedule information, and causes the user with the higher degree of busyness to input the exchange candidate date and time first.

As an example, suppose user A is busier than user B. In this case, the server 100 may determine an exchange candidate date and time based on user A's schedule information and present the exchange candidate date and time to user B. FIG. As a result, it is possible to shorten the time required to adjust the exchange date and time.

Also, the order of inputting the exchange candidate dates and times may be determined based on user settings. As an example, it is assumed that user B has set in advance to propose exchange candidate dates and times first. In this case, the server 100 causes the user B to input the exchange candidate date and time first, and then allows the user A to select the exchange candidate date and time.

<L14. Others>
Moreover, the server 100 may change the output mode of various information in accordance with the user's personality (for example, meticulousness and taste). The output mode includes, for example, a visual output mode such as a screen and an auditory output mode such as a voice. Output modes that match the user's personality are registered in advance for each personality classification, for example. The personality classification of each user is registered in advance in the above-described user DB 124 (see FIG. 3), for example. The personality classification includes, for example, “methodical” and “rough”.

Further, the server 100 may summarize and output various types of information according to the user's personality (for example, meticulousness and taste). As an example, the server 100 summarizes and outputs various types of information for users whose personality classification is "rough". On the other hand, the server 100 outputs various types of information without summarizing for users whose personality classification is "methodical".

As a more specific example, the server 100 outputs more detailed information to a user whose personality classification is "methodical" or a user who is highly "diligent" in the Big Five. As an example of more detailed information, the server 100 may say, "At this date and time, after finishing the meeting from 1:00 p.m., you will have about an hour to spare before moving to the office. Would you like to select this date and time?" is displayed.

On the other hand, the server 100 outputs simpler information for a user whose personality classification is "crude" or a user who is low in "diligence" in the Big Five. As an example of simpler information, the server 100 displays a message "This date and time is recommended. Is this okay?" together with a diagram of a simple schedule.

In addition, when the exchange candidate date and time is set by the voice guide, the server 100 accepts the setting under the initiative of the user with a high degree of "diligence" and a low degree of busyness. As an example, the server 100 accepts voices such as "set the time slot on Wednesday when it is the most free" and "is there a recommended date and time on Thursday?"

On the other hand, the server 100 accepts settings for users with a high degree of busyness under the initiative of the system. As an example, the server 100 makes a suggestion to the user from the system side, such as "I have a schedule on Wednesday at this time, but may I make a request for this time?"

<L15. Others>
Also, in the above description, an example in which the exchange date and time are adjusted between two users has been described. However, the date and time of interaction may be coordinated among three or more users.

As an example, it is assumed that the date and time of interaction are coordinated by three users A to C. FIG. In this case, user A's terminal 200A first accepts an input of an exchange candidate date and time. After that, user B's terminal 200B accepts selection of one or more dates and times from the candidate exchange dates and times input by user A. FIG. Thereafter, user C's terminal 200C accepts selection of one of the exchange candidate dates and times selected by user B. FIG. The exchange candidate date and time selected by user C is notified from terminal 200C to terminals 200A and 200B. Thus, the exchange date and time are determined.

As another example, assume that social dates and times are coordinated with a number of users (eg, ten users). In this case, the rank of each user is preset. The ranks include, for example, a higher rank that has the authority to coordinate exchange candidates (e.g., decision maker or chairperson) and a lower rank that does not have the authority to coordinate exchange candidates (e.g., those without decision-making authority). and Coordination of exchange dates and times is carried out among users of higher ranks. The date and time of interaction determined between high-ranking users is notified not only to high-ranking users but also to low-ranking users. Lower-ranked users follow the date and time of interaction established among higher-ranked users. Note that the server 100 may receive an input of a date and time when a schedule is filled from a user of a lower rank, and notify the terminal 200 of a user of a higher rank to exclude the date and time from the candidate exchange dates and times.

<L16. Others>
In addition, the immediate online exchange function that allows users to start online exchange at any timing can be used in various situations.

As an example, the instant online socializing feature may be utilized in spare time after an office meeting has ended. In-house meetings and free times that each user is scheduled to participate in common may be automatically acquired from an in-house tool, or may be automatically acquired from the user's schedule information, for example. When the exchange support system 10 judges that there is free time after an in-house meeting scheduled to be attended by users ends, it sends a notice prompting to use an immediate online exchange function to the terminal 200.例文帳に追加The notification includes, for example, the message "Would you like to start interacting now?"

As another example, the instant online socializing feature may be used during breaks between users. Each user's break time is automatically acquired from the user's schedule information, for example. The server 100 identifies a time slot for which no schedule is registered in the schedule information as the user's break time. After that, the server 100 sends a notification to the terminal 200 prompting to use the instant online interaction function if the users have overlapping free time and the users are close to each other. The notification includes, for example, the message "Would you like to start interacting now?" The user's location information is obtained, for example, from a GPS (Global Positioning System) provided in terminal 200 . The server 100 determines that the users are close to each other when the distance between the users is equal to or less than a predetermined distance, or when the users are on the same floor.

Note that the user's location information includes not only location information in the real world, but also location information in the virtual space. The server 100 may determine that the users are close to each other when the distance between the users in the virtual space is equal to or less than a predetermined distance.

As another example, the instant online interaction feature may be utilized when users are both logged in. The server 100 sends a notification to the terminals 200 prompting them to use the instant online interaction feature when both users are logged in. The notification includes, for example, the message "Would you like to start socializing online now?"

<L17. Others>
In addition, the server 100 may change the timing and frequency of notifying the user that the exchange partner has entered the exchange candidate date and time according to the user's busyness, personality tendency, and usage status of the exchange support system 10. The notification is displayed on the screen of a mobile terminal such as a smartphone or a wearable terminal, for example. The notification screen is configured to accept an operation of selecting a desired date from among the candidate dates and times for interaction presented by the interaction partner.

As an example, when the probability of a user reacting to a notification is higher than a certain level, it is effective to frequently display the notification to the user. Therefore, the server 100 notifies such a user each time immediately after the user logs in or immediately after the exchange partner inputs the exchange candidate date and time. On the other hand, the server 100 does not notify users who are very busy. In addition, the server 100 always notifies users whose usage rate of the exchange support system 10 is below a certain level so as to ensure that they input exchange candidate dates and times at the timing of using the exchange support system 10 .

As another example, the server 100 notifies the user when the candidate exchange date and time or the confirmed exchange date and time is close to the current date (for example, the next day). This allows the user to more reliably recognize information with a high degree of urgency. As a result, it becomes easier for users to interact online.

<M. Summary>
As described above, server 100 allows terminal 200A to accept input of candidate dates and times for interaction between user A and user B within date and time range ΔTR1 (see FIG. 2). The start date and time T1S of the date and time range ΔTR1 is a predetermined period ΔTP1 after the server 100 or the terminal 200A starts accepting the input of the exchange candidate date and time (that is, the timing T0A).

This reduces the possibility that the exchange candidate date and time input by user A is in the past at the time of user B's confirmation. Further, if the presented candidate date and time for interaction is earlier, user B can decide the date and time for interaction with user A after adjusting his/her own schedule. As a result, online interaction between user A and user B is facilitated.

It should be considered that the embodiments disclosed this time are illustrative in all respects and not restrictive. The scope of the present invention is indicated by the scope of the claims rather than the above description, and is intended to include all modifications within the scope and meaning equivalent to the scope of the claims.

10 exchange support system, 100 server, 101 control device, 102 ROM, 103 RAM, 104 communication interface, 105 display interface, 106 display, 107 input interface, 108 input device, 110 bus, 120 storage device, 122 exchange support program, 124 User DB, 126 usage history, 200 terminal, 200A terminal, 200B terminal, 200C terminal, 201 control device, 202 ROM, 203 RAM, 204 communication interface, 205 display interface, 206 display, 207 input interface, 208 input device, 210 bus , 220 storage device, 222 exchange support program, 300A start screen, 300B input screen, 300C confirmation screen, 300D confirmation screen, 300E input screen, 300F reminder screen, 300G reminder screen, 300H reminder screen, 300I input screen, 300J notification screen, 301 start button, 302 display field, 304 input field, 306 decision button, 307 message, 308 display field, 310 button, 311 display field, 312 connection button, 313 change button, 314 message, 316 input field, 318 decision button, 322 display field, 324 connect button, 326 change button, 330 display field, 332 input field, 334 OK button, 336 cancel button, 340 confirmation message, 341 timer, 342 OK button, 348 message, 350 input field, 352 connect button, 354 decision button, 360 message, 400A selection screen, 400B confirmation screen, 400C reminder screen, 400D input screen, 400E confirmation screen, 400G request screen, 400H selection screen, 402 display column, 404 selection column, 405 decision button, 406 NG button, 408 confirmation message, 409 timer, 410 OK button, 412 display field, 414 connection button, 416 change button, 424 input field, 426 decision button, 432 display field, 434 connection button, 436 change button, 440 display field, 442 request message , 444 OK button, 446 NG button, 450H selection screen, 452 message, 454 selection column, 455 decision button, 456 NG button.

Claims (11)

An exchange support program for adjusting exchange dates and times between users,
The exchange support program is
receiving, from the first user, input of a first candidate date and time for interaction between the first user and the second user within the first date and time range;
a step of notifying the second user of the first exchange candidate date and time;
causing a server to execute a step of receiving a selection of a date and time when said second user can interact with said first user from said second user within said first candidate date and time for interaction;
The exchange support program, wherein the start date and time of the first date and time range is after a first predetermined period from the reception of the first candidate date and time for interaction from the first user. The exchange support program is
receiving from the second user an input of a second candidate exchange date and time different from the first candidate exchange date and time within a second date and time range after the second user is notified of the first candidate exchange date and time; Let the server do more,
2. The exchange support program according to claim 1, wherein the start date and time of said second range of dates and times is later than the start date and time of said first range of dates and times. The exchange support program is
changing the starting date and time of the second date and time range according to whether or not the first user has used the function of the server within a second predetermined period before accepting the second candidate date and time; causing the server to perform further processing;
The start date and time of the second date and time range when the first user uses the function of the server within the second predetermined period is 3. The exchange support program according to claim 2, which is after the start date and time of the second date and time range when the function is not being used. The exchange support program is
If the selection is not received within a third predetermined period after the first candidate exchange date and time is accepted, a third candidate exchange date and time that is different from the first candidate exchange date and time is input. causing the server to further perform the step of accepting from the first user or the second user within a third date and time range;
4. The exchange support program according to any one of claims 1 to 3, wherein the start date and time of said third date and time range is later than the start date and time of said first date and time range. The exchange support program is
5. The interaction according to any one of claims 1 to 4, further causing the server to execute a step capable of fixing an interaction date and time between the first user and the second user without accepting the selection. support program. The exchange support program is
If the exchange at the exchange date and time determined by the selection is canceled on the current day, the server further executes a step of accepting resetting of the candidate exchange date and time from the first user or the second user within a fourth date and time range. let
6. Any one of claims 1 to 5, wherein the start date and time of the fourth date and time range is after a fourth predetermined period from the reception of the resetting, and the fourth predetermined period is shorter than the first predetermined period. Exchange support program described in section. The exchange support program is
Sending a notification to the server to prompt at least one of the first user and the second user to reset the exchange date and time when the exchange at the exchange date and time determined by the selection is canceled on the day. The exchange support program according to any one of claims 1 to 6, which is executed. The exchange support program is
If the date and time of interaction between the first user and the second user are not fixed within a fifth predetermined period after the first candidate date and time is accepted, the first user and the second user 8. The exchange support program according to any one of claims 1 to 7, further causing the server to execute a step of disabling the exchange with. The exchange support program is
receiving, from the first user, an input of a third candidate date and time for interaction between the first user and the third user after the date and time for interaction between the first user and the second user are determined; The exchange support program according to any one of claims 1 to 8, further executed. An exchange support method for adjusting exchange dates and times between users,
receiving, from the first user, input of a first candidate date and time for interaction between the first user and the second user within the first date and time range;
a step of notifying the second user of the first exchange candidate date and time;
receiving a selection of a date and time when the second user can interact with the first user from the second user within the first candidate date and time for interaction;
The interaction support method, wherein the start date and time of the first date and time range is after a first predetermined period from the reception of the first candidate date and time for interaction from the first user. A server for adjusting exchange dates and times between users,
A control unit for controlling the server,
The control unit
A process of accepting input of a first candidate date and time for interaction between the first user and the second user from the first user within the first date and time range;
A process of notifying the second user of the first exchange candidate date and time;
and performing a process of receiving from the second user a selection of a date and time when the second user can interact with the first user from among the first candidate date and time for interaction,
The server, wherein the start date and time of the first date and time range is after a first predetermined period from the reception of the first candidate date and time for interaction from the first user.

Images