Processing device, processing program, and processing method

Abstract

To select holding date candidates for a meeting.SOLUTION: When a first user has authority to adjust a schedule for a second user different from the first user or for a facility scheduled to be used at a meeting, a first terminal device usable by the first user accepts operational input by the first user, and thereby a processing device receives, from the first terminal device via a communication interface, user identification information for identifying the second user selected from among a plurality of users including the first user as a planned participant in the meeting or facility identification information for identifying the facility, and holding date candidates for the meeting selected according to schedule information of the second user or the facility, and generates access information indicating an access destination from which a third user different from the first user and the second user can select a desired holding date from among the holding date candidates as a planned participant in the meeting, and transmits the generated access information to the first terminal device via the communication interface.SELECTED DRAWING: Figure 8A

Description

[Technical field]

[0001] The present disclosure relates to a processing device, a processing program, and a processing method for selecting candidate dates for holding a meeting. [Background technology]

[0002] A conference schedule adjustment program that causes a computer to execute an optimization step of identifying an optimal first schedule for a first user and a second user in accordance with schedule adjustment instructions and the availability data, the optimization step including the steps of connecting the computer to a learning device that has learned the correspondence between the schedule availability of participants for a previously held conference at a time before the conference was held and the schedule in which the previously held conference was actually held, and obtaining the first schedule as an output of the learning device by providing the contents of the schedule adjustment instructions and the availability data as input to the learning device (Patent Document 1).

[0003] However, such a conference schedule adjustment program requires that the first and second users who wish to adjust the conference schedule themselves issue an instruction. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent Publication No. 2021-64030 Summary of the Invention [Problem to be solved by the invention]

[0005] In light of the above-described technology, an object of the present disclosure is to provide, in various embodiments, a better processing device, processing program, and processing method for selecting candidate dates for holding a meeting. [Means for solving the problem]

[0006] According to one aspect of the present disclosure, there is provided a processing device having at least one processor, the at least one processor being configured to execute a process for receiving, from the first terminal device via a communication interface, user identification information for identifying the second user selected as a planned participant of the meeting from among a plurality of users including the first user or equipment identification information for identifying the equipment, and candidate dates for the meeting selected according to schedule information of the second user or the equipment, when a first user has authority to adjust the schedule of a second user different from the first user or equipment to be used in a meeting, by accepting an operational input by the first user on a first terminal device usable by the first user, and generating access information indicating an access destination from which a third user different from the first user and the second user can select a desired date for the meeting from the candidate dates, as a planned participant of the meeting, and transmitting the generated access information to the first terminal device via the communication interface."

[0007] According to one aspect of the present disclosure, there is provided a processing program that causes a computer having at least one processor to function as follows: when a first user has authority to adjust the schedule of a second user different from the first user or equipment to be used in a meeting, a processing program causes the at least one processor to function as follows: when a first user has authority to adjust the schedule of a second user different from the first user or equipment to be used in a meeting, by accepting an operational input from the first user on a first terminal device usable by the first user, receive from the first terminal device via a communication interface user identification information for identifying the second user selected from a plurality of users including the first user as a planned participant of the meeting or equipment identification information for identifying the equipment, and candidate dates for the meeting selected according to schedule information of the second user or the equipment, generate access information indicating an access destination from which a third user different from the first user and the second user can select a desired date for the meeting from the candidate dates, and transmit the generated access information to the first terminal device via the communication interface.

[0008] According to one aspect of the present disclosure, there is provided a processing method executed by at least one processor in a computer having at least one processor, the processing method including the steps of: when a first user has authority to adjust the schedule of a second user different from the first user or equipment to be used in a meeting, receiving, from the first terminal device usable by the first user, user identification information for identifying a second user selected from a plurality of users including the first user as a planned participant of the meeting or equipment identification information for identifying the equipment, and candidate dates for the meeting selected according to schedule information of the second user or the equipment, via a communication interface; generating access information indicating an access destination from which a third user different from the first user and the second user can select a desired date for the meeting from the candidate dates; and transmitting the generated access information to the first terminal device via the communication interface.

[0009] According to one aspect of the present disclosure, there is provided a processing device having at least one processor, the at least one processor being configured to execute a process for accepting an operation input by a first user via an input interface in order to select a second user different from the first user as a planned participant of the meeting from among a plurality of users including the first user, the second user being different from the first user, as the facility to be used in the meeting, or the facility as the facility to be used in the meeting, when the first user has authority to adjust the schedule for a second user different from the first user or a facility to be used in the meeting, accepting an operation input by the first user via the input interface in order to select a candidate date for the meeting based on schedule information of the second user or the facility, transmitting second user identification information for identifying the second user or equipment identification information of the facility and the selected candidate date for the meeting via a communication interface to a server device connected via a communication network, and receiving from the server device access information indicating an access destination for a third user different from the first user and the second user to select a desired candidate date for the meeting from the candidate date for the meeting, as a planned participant of the meeting."

[0010] According to one aspect of the present disclosure, there is provided a processing program that causes a computer having at least one processor to function as follows: when a first user has authority to adjust the schedule of a second user different from the first user or equipment to be used in a meeting, the computer receives an operation input by the first user via an input interface in order to select a second user different from the first user as a planned participant of the meeting from among a plurality of users including the first user, the second user being different from the first user, as the equipment to be used in the meeting, and receives an operation input by the first user via the input interface in order to select a candidate date for the meeting based on schedule information of the second user or the equipment, and transmits, via a communication interface, second user identification information for identifying the second user or equipment identification information of the equipment and the selected candidate date for the meeting to a server device connected via a communication network, and receives from the server device access information indicating an access destination for a third user different from the first user and the second user to select a desired date for the meeting from the candidate date for the meeting as a planned participant of the meeting.

[0011] According to one aspect of the present disclosure, there is provided a processing method executed by at least one processor in a computer having at least one processor, the processing method including: when a first user has authority to adjust a schedule for a second user different from the first user or for equipment to be used in a meeting, a step of accepting an operation input by the first user via an input interface to select a second user different from the first user from a plurality of users including the first user as a planned participant of the meeting, or the equipment as equipment to be used in the meeting; a step of accepting an operation input by the first user via the input interface to select a candidate date for the meeting based on schedule information of the second user or the equipment; a step of transmitting, via a communication interface, second user identification information for identifying the second user or equipment identification information of the equipment and the selected candidate date for the meeting to a server device connected via a communication network; and a step of receiving from the server device access information indicating an access destination for a third user different from the first user and the second user to select a desired date for the meeting from the candidate date for the meeting as a planned participant of the meeting. Effect of the Invention

[0012] According to the present disclosure, it is possible to provide a processing device, a processing program, and a processing method that are improved for selecting candidate dates for holding a meeting.

[0013] It should be noted that the above effects are merely illustrative for the convenience of explanation and are not limiting. In addition to or instead of the above effects, any effect described in this disclosure or any effect obvious to a person skilled in the art may be achieved. [Brief description of the drawings]

[0014] [Figure 1] FIG. 1 is a block diagram showing a configuration of a processing system 1 according to an embodiment of the present disclosure. [Diagram 2]FIG. 2 is a block diagram showing a configuration of the server device 100 according to an embodiment of the present disclosure. [Figure 3A] FIG. 3A is a diagram conceptually illustrating a user management table stored in the server device 100 according to an embodiment of the present disclosure. [Figure 3B] FIG. 3B is a diagram conceptually illustrating a facility management table stored in the server device 100 according to an embodiment of the present disclosure. [Figure 3C] FIG. 3C is a diagram conceptually illustrating a schedule management table stored in the server device 100 according to an embodiment of the present disclosure. [Figure 4A] FIG. 4A is a diagram showing a processing sequence executed by the processing system 1 according to an embodiment of the present disclosure. [Figure 4B] FIG. 4B is a diagram showing a processing sequence executed by the processing system 1 according to an embodiment of the present disclosure. [Figure 4C] FIG. 4C is a diagram showing a processing sequence executed by the processing system 1 according to an embodiment of the present disclosure. [Figure 4D] FIG. 4D is a diagram showing a processing sequence executed by the processing system 1 according to an embodiment of the present disclosure. [Diagram 5] FIG. 5 is a diagram showing a processing flow executed in the first terminal device 200-1 according to an embodiment of the present disclosure. [Figure 6] FIG. 6 is a diagram showing a process flow executed in the server device 100 according to an embodiment of the present disclosure. [Figure 7] FIG. 7 is a diagram showing a processing flow executed in the third terminal device 200-3 according to an embodiment of the present disclosure. [Figure 8A] FIG. 8A is a diagram showing an example of a screen displayed on the first terminal device 200-1 according to an embodiment of the present disclosure. [Figure 8B] FIG. 8B is a diagram showing an example of a screen displayed on the first terminal device 200-1 according to an embodiment of the present disclosure. [Figure 8C]FIG. 8C is a diagram showing an example of a screen displayed on the first terminal device 200-1 according to an embodiment of the present disclosure. [Figure 8D] FIG. 8D is a diagram showing an example of a screen displayed on the first terminal device 200-1 according to an embodiment of the present disclosure. [Figure 8E] FIG. 8E is a diagram showing an example of a screen displayed on the first terminal device 200-1 according to an embodiment of the present disclosure. [Figure 9] FIG. 9 is a diagram showing an example of a screen displayed on the third terminal device 200-3 according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] 1. Overview of Processing System 1 The processing system according to the present disclosure is used by a first user to adjust candidates for a meeting date in which a second user is a planned participant. Typically, the processing system 1 is used when the first user has authority to adjust candidates for a meeting date in which the second user is a planned participant on behalf of the second user. First, an operation input is accepted in a first terminal device available to the first user to designate the second user as a planned participant of the meeting. When the server device receives a request from the first terminal device to extract candidates for a meeting date from the first terminal device, the server device extracts candidates for the meeting date and transmits candidate information. When the first terminal device receives the candidate information, the first terminal device selects candidates to be presented to a third user from among the extracted candidates for the meeting date and transmits a request for access information indicating an access destination to present to the third user who is the person to coordinate the meeting. When the server device receives the request, the server device generates access information and transmits it to the first terminal device. The first terminal device transmits the access information to a third terminal device available to the third user. The third terminal device accepts the operation input from the third user, accesses the access destination indicated in the received access information, and selects the desired meeting date.

[0016] That is, even if the second user is a prospective attendee of the meeting as described above, the first user can arrange the schedule of the meeting on his / her behalf. Also, the first user can arrange the schedule of the meeting without having to attend the meeting as a participant.

[0017] Fig. 1 is a block diagram showing a configuration of a processing system 1 according to an embodiment of the present disclosure. According to Fig. 1, the processing system 1 includes at least a server device 100, a first terminal device 200-1 available to a first user, a second terminal device 200-2 available to a second user, and a third terminal device 200-3 available to a third user. The server device 100, the first terminal device 200-1, the second terminal device 200-2, and the third terminal device 200-3 are connected to at least one of a wireless network and a wired network so as to be able to communicate with each other.

[0018] In the present disclosure, typically, the first user using the first terminal device 200-1 and the second user using the second terminal device 200-2 are users belonging to the same group 300 that is set in advance. The group may be a group set in advance by an administrator who is an administrator of the organization to which the first user and the second user belong. Such a group may be any group in which multiple users permitted by the administrator to be in the same group belong, and does not necessarily have to belong to a specific organization such as a company, department, school, class, etc. Furthermore, in FIG. 1, as described above, the first user using the first terminal device 200-1 and the second user using the second terminal device 200-2 are illustrated as users belonging to the group 300, but the group 300 may naturally include users other than these (including a third user) or may be composed of users other than these.

[0019] In addition, in the present disclosure, the "processing device" may be any of the server device 100, the first terminal device 200-1, the second terminal device 200-2, and the third terminal device 200-3. In other words, when the processing device is described, it means any of the above devices, and is not limited to any one device unless specifically mentioned. Here, for convenience of explanation, the server device 100 is described as a specific example of the processing device.

[0020] In addition, in the present disclosure, the first terminal device 200-1 to the third terminal device 200-3 are distinguished according to which of the first user to the third user is available. However, this does not mean that the first terminal device 200-1 is available only to the first user, the second terminal device 200-2 is available only to the second user, and the third terminal device 200-3 is available only to the third user. That is, each terminal device may be used by either the first user to the third user or another user, and the name of the device changes depending on the user who is using the device. The first terminal device 200-1 to the third terminal device 200-3 may be simply referred to as the terminal device 200, but this means at least one of the terminal devices including the first terminal device 200-1 to the third terminal device 200-3. Furthermore, in this disclosure, three terminal devices 200, the first terminal device 200-1, the second terminal device 200-2, and the third terminal device 200-3, are exemplified, but other terminal devices 200 may naturally be included.

[0021] In addition, in this disclosure, descriptions such as "first," "second," and "third" may be used, but unless otherwise specified, these are merely names given for the convenience of explanation. Therefore, even if descriptions such as "first," "second," and "third" are used, it does not mean that the elements are limited to those elements to which they are attached. Naturally, multiple elements such as "fourth," "fifth," and more may be included.

[0022] 2. Configuration of the Server Device 100 Fig. 2 is a block diagram showing a configuration of a server device 100 according to an embodiment of the present disclosure. The server device 100 does not need to include all of the components shown in Fig. 2, and may have a configuration in which some components are omitted, or may include other components. In addition, the server device 100 does not need to include the components shown in Fig. 2 in a single housing, and each component and process of the server device 100 may be distributed to processing devices such as a plurality of on-premise server devices and cloud server devices.

[0023] 2, the server device 100 includes a processor 111 including a CPU or the like, a memory 112 including a RAM, a ROM, a non-volatile memory, an HDD, and the like, and a communication interface 113. These components are electrically connected to each other via control lines and data lines.

[0024] The processor 111 is configured with a CPU (microcomputer) and functions as a control unit for controlling other connected components based on various programs stored in the memory 112. The processor 111 reads out and executes a program for executing an application according to the present disclosure and a program for executing an OS from the memory 112. Specifically, the processor 111 performs the following operations: "When a first user has authority to adjust the schedule for a second user different from the first user or for equipment to be used in a meeting, the processor 111 receives, via the communication interface 113 from the first terminal device 200-1 usable by the first user, user identification information for identifying a second user selected from a plurality of users including the first user as a prospective participant in the meeting or equipment identification information for identifying equipment, and candidate dates for holding the meeting selected according to schedule information for the second user or equipment," and "When a third user different from the first user and the second user is selected as a prospective participant in the meeting, the processor 111 receives, via the communication interface 113 from the first terminal device 200-1, user identification information for identifying a second user selected from a plurality of users including the first user as a prospective participant in the meeting or equipment identification information for identifying equipment." The processor 111 executes the following processes based on the program stored in the memory 112: "a process of generating access information indicating an access destination from which a desired meeting date can be selected from among candidate meeting dates by accessing the access destination," "a process of transmitting the generated access information to the first terminal device 200-1 via the communication interface 113," "a process of transmitting a notification that the meeting date has been finalized to the second terminal device 200-2 available to the second user upon receiving selection information of the desired meeting date selected by accessing the access destination from the third terminal device 200-3 available to the third user," and "a process of generating the schedule information of the second user in such a way that candidate meeting dates can be distinguished before and after the third user selects the desired meeting date," etc. The processor 111 is mainly composed of one or more CPUs, but may be appropriately combined with a GPU, FPGA, etc.

[0025] The memory 112 includes a RAM, a ROM, a non-volatile memory, and a HDD, and functions as a storage unit. The ROM stores instructions for executing the application and the OS according to the present disclosure as a program. Such a program is loaded and executed by the processor 111. The RAM is used to write and read data while the program stored in the ROM is being processed by the processor 111. The non-volatile memory is a memory into which data is written and read by the execution of the program, and the data written therein is saved even after the execution of the program is terminated. Specifically, the memory 112 stores a program for the processor 111 to execute the above-mentioned processes and the like. The memory 112 also stores various information such as a user management table (FIG. 3A) and a schedule management table (FIG. 3B). Note that these pieces of information may be stored in a database device communicably connected to the server device 100 as necessary (in this case, the database may also be included as one of the memories 112).

[0026] The communication interface 113 functions as a communication unit that transmits and receives information between the terminal device 200 and other server devices installed remotely via a communication processing circuit and an antenna. The communication processing circuit performs processing for transmitting and receiving information such as programs and various information used in the processing system 1 according to the progress of processing. In the present disclosure, the communication interface 113 receives a login request, a request to extract candidates, a request to provide an access destination, and a request to change a candidate from the first terminal device 200-1, and transmits schedule information, candidate information, access destination information, and the like to the first terminal device 200-1. In addition, the communication interface 113 receives a login request, a request to change a candidate, a request to change a confirmed schedule, and the like from the second terminal device 200-2, and transmits schedule information, a confirmation notice, and the like to the second terminal device 200-2. In addition, the communication interface 113 receives a candidate transmission request and confirmation information from the third terminal device 200-3, and transmits event schedule candidate information and an invitation request to the third terminal device 200-3. The communication processing circuit processes based on a wideband wireless communication system such as the LTE system, but it is also possible to process based on a system related to narrowband wireless communication or a system related to non-contact wireless communication such as wireless LAN such as IEEE802.11 or Bluetooth (registered trademark). Also, wired communication can be used instead of or in addition to wireless communication.

[0027] 3. Configuration of Terminal Device 200 Although the configuration of the terminal device 200 is not specifically illustrated, it includes a processor, a memory, an input interface, an output interface, and a communication interface. These components are electrically connected to each other via a control line and a data line. Note that the terminal device 200 does not need to include all of these components, and it is possible to omit some of them or to add other components.

[0028] Such a terminal device 200 can be suitably applied to any device capable of executing the processes according to the present disclosure, such as a laptop computer, a desktop computer, a smartphone, a tablet terminal, etc. In this embodiment, at least a first terminal device 200-1, a second terminal device 200-2, and a third terminal device 200-3 are present, but they do not need to be the same type of device having the same components. In other words, they may be different types of terminal devices.

[0029] In the terminal device 200, the processor functions as a control unit that controls the terminal device 200 or other components of the processing system 1 based on a program stored in the memory. Specifically, the processor performs the following operations: "a process of accepting an operation input by a first user via an input interface in order to select a second user different from the first user as a prospective participant of the meeting from among a plurality of users including the first user, or a piece of equipment as a piece of equipment to be used in the meeting, when the first user has authority to adjust the schedule for a second user different from the first user or for equipment to be used in the meeting", "a process of accepting an operation input by a first user via an input interface in order to make a selection in accordance with schedule information of the second user", and "a process of transmitting second user identification information for identifying the second user or equipment identification information for identifying equipment to be used in the meeting to the server device 100 connected via a communication network". The processor executes, based on the program stored in the memo, the following operations: "processing of transmitting, via a communication interface, other information and the selected candidate meeting date," "processing of receiving from the server device, access information indicating an access destination for a third user, different from the first user and the second user, to select a desired meeting date from the candidate meeting date as a prospective participant of the meeting," "processing of transmitting the received access information to a third terminal device 200-3 available to the third user," "processing of accessing the access destination indicated in the access information and selecting a desired meeting date from the candidate meeting date," "processing of receiving and displaying a notification that the meeting has been confirmed," "processing of changing the candidate meeting date," and "processing of changing the confirmed meeting date." The processor is mainly composed of one or more CPUs, but may be appropriately combined with a GPU, FPGA, etc.

[0030] The memory is composed of a RAM, a ROM, a non-volatile memory, a HDD, etc., and functions as a storage unit. The memory 212 stores instructions and commands for various controls of the processing system 1 according to this embodiment as a program. Specifically, the memory stores a program for the processor to execute the above-mentioned processes.

[0031] The input interface functions as an input unit that accepts user operation input to the terminal device 200. Examples of the input interface include various hard keys such as a keyboard and a mouse, and a touch panel that is superimposed on the display of the display device and has an input coordinate system corresponding to the display coordinate system of the display. The input interface does not always need to be physically provided in the terminal device 200, and may be connected as necessary via a wired or wireless network.

[0032] The output interface functions as an output unit for outputting various information. An example of the output interface is an interface for connecting to an external device or equipment such as a display device composed of a liquid crystal panel, an organic EL display, a plasma display, or the like. However, when the terminal device 200 itself has a display, the display can function as the output interface. Also, when the terminal device 200 is connected to a display device or the like via a communication interface, the communication interface can function as the output interface.

[0033] The communication interface functions as a communication unit that transmits and receives information between the server device 100 and other terminal devices via a communication processing circuit and an antenna. The communication processing circuit processes programs used in the processing system 1 and various information to transmit and receive information according to the progress of processing. The communication processing circuit can also process based on a contactless wireless communication system such as Bluetooth (registered trademark) or NFC, in addition to a wideband wireless communication system such as the LTE system and a narrowband wireless communication system such as a wireless LAN such as IEEE802.11. Wired communication can also be used instead of or in addition to wireless communication.

[0034] 4. Information stored in the server device 100 3A is a diagram conceptually illustrating a user management table stored in the server device 100 according to an embodiment of the present disclosure. Information stored in the user management table is updated and stored as needed in accordance with the progress of processing by the processor 111 of the server device 100.

[0035] According to FIG. 3A, the user management table stores attribute information, group ID information, schedule information, authority information, and the like in association with user ID information. The "user ID information" is information unique to each user and is used to identify each user. The user ID information is generated in the server device 100 when, for example, an administrator of an organization to which the user belongs transmits a new registration request to a service provided by the processing system 1. The "attribute information" is information that is the attribute of each user. Examples of such attribute information include a user name (first and last name), a title, a nickname, a career history, contact information such as an SNS account, an email address, and a telephone number, a friend list, an address and a company name of the company to which the user belongs, and a department name. These are stored as needed by inputting instructions from the user, etc.

[0036] "Group ID information" is information specific to the group to which each user belongs, and is information for identifying each group. As an example of group ID information, group ID information of a group designated in advance for each user by an administrator is associated with the user ID information of each user. It means that users associated with the same group ID information belong to the same group. Note that there is not necessarily one group in one organization, and multiple groups may exist. Also, there may be groups formed across multiple organizations. Also, the same user may belong to multiple different groups. Also, it is sufficient that at least one user belongs to a group, and it is not necessarily required that multiple users belong to a group.

[0037] "Schedule information" is information for identifying each schedule registered in each user's calendar. Typically, schedule ID information shown in Fig. 3C is stored. Note that the schedule information is not limited to one schedule ID information, and multiple schedule ID information may be stored according to the number of registered schedules.

[0038] The "authority information" is information indicating whether or not a user has the authority to adjust the schedule of another user. The authority information may typically be any of the following information that may be set in advance by an administrator or by each user.

[0039] (A) Before the candidate dates are selected -Privilege A1: Cannot view schedule information or adjust schedules of other users who belong to the same organization as the user - Authority A2: Can only view schedule information of specific users who have been granted permission in advance and adjust the schedule of those specific users - Authority A3: Can view schedule information of users in the same group as the user and adjust the schedule of those users - Authority A4: Can view schedule information of users who belong to the same organization as the user and adjust the schedule of the users (B) Before a candidate date for the event is selected and the desired date for the event is confirmed by a third user. -Privilege B1: Cannot view schedule information of other users who belong to the same organization as the user, or modify the proposed dates of events - Authority B2: Can only view schedule information of specific users who have been approved in advance and can only modify the proposed dates of events for those specific users. Can only view schedule information and propose modifications for other users who belong to the same organization as themselves, other than the specific users. - Authority B3: Can only view schedule information of users who belong to the same group as themselves and modify the proposed dates of events for those users. Can only view schedule information and propose modifications for other users who belong to the same organization as themselves. - Authority B4: Can view schedule information of users who belong to the same organization as the user and can edit the proposed dates of events for those users (C) After the desired event date is confirmed by the third user - Permission C1: Cannot view other users' schedule information or modify event dates - Authority C2: Can only view schedule information of specific users who have been granted permission in advance and modify the dates of events held by those specific users. Can only view schedule information and propose modifications to other users who belong to the same organization as the user, other than the specific users. - Authority C3: Can only view schedule information of users who belong to the same group as the user and can only modify the schedule of the user. Can only view schedule information and propose modifications for other users who belong to the same organization as the user. - Authority C4: Can view schedule information of users who belong to the same organization as the user and can modify the schedule of events held by those users

[0040] As described above, by setting the authority for each individual user, it becomes possible for the administrator who sets the authority, the coordinator (first user), and the second user to set more flexible authority. By setting different authority according to the status related to the confirmation of the candidate schedule, it becomes possible to set flexibly according to the degree of impact of schedule adjustment or modification.

[0041] Although the above describes a case where authority information is set in association with the user ID information of each user, it is also possible to set authority information for groups collectively in association with the group ID information of each group. Also, the above authority information is merely an example, and it is of course possible to set other information than the above.

[0042] Although the authority information for the equipment is not described in detail, the authority information for the equipment is set in association with each user ID information, similar to the authority information for the user as described above.

[0043] Also, the above-mentioned authority information has been described as being set collectively between a user and other users (equipment), but it is also possible to set it in detail for each schedule by associating it with schedule ID information. For example, as the authority information of the first user, it is possible to set authority A1 for schedule A and authority A2 for schedule B. In such a case, a user who will be the coordinator of the first user or a user who will be a prospective participant of the second user can set authority information for each schedule information when generating each schedule information for revising candidate dates for the event or revisions to the confirmed date for the event.

[0044] 3B is a diagram conceptually illustrating an equipment management table stored in the server device 100 according to an embodiment of the present disclosure. Information stored in the equipment management table is updated and stored as needed in accordance with the progress of processing by the processor 111 of the server device 100.

[0045] According to FIG. 3B, the facility management table stores attribute information, schedule information, and the like in association with facility ID information. The "facility ID information" is information specific to each facility and is information for identifying each facility. The facility ID information is information generated in the server device 100, for example, when a new registration request for facilities available to each user is sent by an administrator of an organization that manages each facility. Examples of facilities include spaces available to users for meetings, such as conference rooms, conference booths, shared offices, and work booths; equipment available to users for meetings, such as projectors, microphones, earphones, lighting, displays, PCs, game consoles, smartphones, tablets, memories, recording devices, videos, and cameras; and means of transportation available to users for traveling to meetings, such as cars and bicycles.

[0046] "Attribute information" is information that is an attribute of each facility. Examples of such attribute information include the name of the facility, the storage location, the conditions of use, the method of use, and the facility manager. These are stored as needed, for example, in response to instructions input by the facility manager.

[0047] "Schedule information" is information for identifying each schedule registered in the calendar of each facility. Typically, the schedule ID information shown in Fig. 3C is stored. Note that the schedule information is not limited to one schedule ID information, and multiple schedule ID information may be stored according to the number of registered schedules.

[0048] 3C is a diagram conceptually illustrating a schedule management table stored in the server device 100 according to an embodiment of the present disclosure. Information stored in the schedule management table is updated and stored as needed in accordance with the progress of processing by the processor 111 of the server device 100.

[0049] According to FIG. 3C, the schedule management table stores basic information, expected participant information, facility information, destination information, candidate information, access destination information, confirmed schedule information, candidate change information, and authority information in association with schedule ID information. "Schedule ID information" is information specific to at least one of a schedule to be held and a schedule whose holding date is being adjusted, and is information for identifying each schedule. The schedule ID information is information generated in the server device 100 when a user, an administrator, or an adjuster starts adjusting a new schedule. Note that a schedule means an event associated with a specific time (the unit may be any of year, month, week, day of the week, date, hour, minute, and second) on a calendar, for example, and a meeting means an event in a schedule in which multiple users may participate.

[0050] "Basic information" is information that indicates the basic contents of a schedule. Examples of basic information include the title of the schedule, the time required for the meeting, the method of holding the meeting (selection of a web conference tool or selection of a phone number for a telephone conference, etc.), and information that identifies other users who will be attending the meeting and will be participants (e.g., user ID information and group ID information, etc.). This information is stored by operational input by the user who adjusts the schedule.

[0051] "Prospective participant information" is information for identifying users who are scheduled to participate as participants in each schedule. Typically, user ID information or group ID information as shown in FIG. 3A is stored. Prospective participant information is not limited to one user ID information or group ID information, and multiple pieces of information may be stored according to the number of prospective participants. In addition, a user identified by the stored information does not necessarily have to participate in the schedule, and naturally may not attend depending on the circumstances. For example, when multiple user ID information or group ID information of a group to which multiple users belong is stored as prospective participant information, it is not necessary for all users identified above to actually participate in the meeting. One or multiple users who have free schedules on the confirmed dates may participate.

[0052] "Facility information" is information for identifying the facility desired to be used in each schedule. Typically, facility ID information shown in Fig. 3B is stored. Facility information is not limited to one piece of facility ID information, and multiple pieces of information may be stored according to the number of facilities the user desires to use.

[0053] "Destination information" is information for identifying the destination of various notifications (e.g., schedule confirmation notifications) sent from the server device 100, etc. Typically, information such as user ID information, email address, telephone number, and SNS account shown in Fig. 3A is stored. Destination information is not limited to information indicating one destination, and multiple pieces of information may be stored according to the number of desired destinations.

[0054] "Candidate information" is information that indicates candidate dates for a schedule. Typically, it is information that specifies candidate periods for dates for a schedule such as a meeting by date and time. The period is the period required for the schedule such as a meeting (e.g., 60 minutes) plus a period to be secured for travel before and after the meeting, if necessary (e.g., 30 minutes before and after the meeting). Note that the candidate information does not need to be limited to only one specific candidate for one schedule, and multiple candidates may be stored.

[0055] "Access destination information" is information indicating an access destination that a third user, who will be coordinating a schedule such as a meeting, accesses to select a desired date from the candidate dates after the candidate dates have been determined. Typically, the URL of a website where the candidate dates are displayed as a calendar or a list and the desired candidate is output so that it can be selected, is stored as the access destination information.

[0056] "Confirmed schedule information" is information indicating a time that is confirmed as a schedule for an event. Typically, the confirmed schedule information is information that is confirmed when a third user accesses a URL that is a website specified in the access destination information and selects a candidate for a desired event date. When the confirmed schedule information is stored, changes to the schedule by users other than the specified user may be restricted.

[0057] 5. Processing sequence performed by processing system 1 (A) Process for generating candidate dates Fig. 4A is a diagram showing a processing sequence executed by the processing system 1 according to an embodiment of the present disclosure. Specifically, Fig. 4A shows a processing sequence for generating candidates for the date of an event when a first user who is a schedule adjuster adjusts a new schedule in which a second user is a prospective participant. This processing sequence is mainly performed by the processor of each device executing a program stored in the memory or the like of each device.

[0058] According to FIG. 4A, when the processor of the first terminal device 200-1 accepts an operation input of the first user through the input interface, it starts an application program for schedule adjustment (S11). The application program may be a program stored locally in the first terminal device 200-1 dedicated to schedule adjustment, or may be a browser application program for executing a function for schedule adjustment on a browser. When the application program starts, the processor of the first terminal device 200-1 displays a login screen for the schedule adjustment service provided by the processing system 1 through the output interface. Then, the processor of the first terminal device 200-1 accepts an operation input of the first user related to the user ID information and password of the first user through the input interface (S12). The processor of the first terminal device 200-1 transmits the accepted user ID information and password to the server device 100 through the communication interface together with a login request (T11) for logging in to the schedule adjustment service.

[0059] When the processor 111 of the server device 100 receives the login request via the communication interface 113, it authenticates whether or not the first user is a user who has been registered in advance based on the user ID information and password received together (S13). Here, the user ID information is specified in the user management table shown in FIG. 3A, and the user ID information is information that is generated when a new registration request to the schedule adjustment service is sent by an administrator of the organization to which the user belongs, and is stored in the user management table. In a series of processes when a new user is registered, the processor 111 of the server device 100 stores a password (not shown) in association with the user ID information. Therefore, in S13, the processor 111 of the server device 100 refers to the user management table and checks whether or not the received user ID information is stored in the user management table. If the user ID information is stored in the user management table, the processor 111 of the server device 100 checks whether or not the password associated with the user ID information matches the received password. If the passwords match, the processor 111 of the server device 100 authenticates that the first user who sent the login request is a legitimate user.

[0060] When the processor 111 of the server device 100 authenticates that the first user is a valid user, it refers to the user management table and reads out various information stored in the user management table, such as schedule information associated with the user ID information of the first user. Then, the processor 111 of the server device 100 transmits the read schedule information, etc. (T12) via the communication interface 113 to the first terminal device 200-1 that has transmitted the login request.

[0061] When the processor of the first terminal device 200-1 receives the schedule information via the communication interface, it executes a schedule adjustment process to adjust the schedule (meeting) with the second user as a prospective participant (S14). At this time, the processor of the first terminal device 200-1 refers to the authority information received together with the schedule information at T12, and checks whether the second user who is a prospective participant of the schedule has the authority to adjust the schedule, that is, any of the authorities A2 to A4, and allows adjustment only if the second user has the authority.

[0062] Here, Fig. 5 and Fig. 6 are diagrams showing a process flow executed in the first terminal device 200-1 according to an embodiment of the present disclosure. Specifically, Fig. 5 and Fig. 6 are diagrams showing a process flow of the schedule adjustment process shown in S14 of Fig. 4A. This process flow is mainly performed by the processor of the first terminal device 200-1 reading and executing a program stored in a memory.

[0063] According to FIG. 5, when the processor of the first terminal device 200-1 receives schedule information via the communication interface, it accepts the operation input of the first user via the input interface and displays the schedule adjustment screen via the output interface (S111). Then, the processor of the first terminal device 200-1 detects the operation input of the first user via the input interface and accepts the input of basic information (S112). Examples of the basic information include the title of the schedule to be adjusted, the time required for the meeting, the holding method (selection of a tool for Web conference or selection of a phone number for a telephone conference, etc.), and information identifying other users who will be attending the meeting and will be participants (for example, user ID information). Note that the basic information is merely an example, and naturally other information may be included, and all of this information may not be input.

[0064] Here, Fig. 8A is a diagram showing an example of a screen displayed on the first terminal device 200-1 according to an embodiment of the present disclosure. Specifically, it is a diagram showing an example of a schedule adjustment screen 10-1 displayed in S111 of Fig. 5. According to Fig. 8A, the schedule adjustment screen 10-1 includes an information input area 11a on the left side and a calendar display area 11b on the right side.

[0065] The information input area 11a includes, from the top, a participant selection area 12 for selecting participants, a destination setting area 13 for selecting a destination for notifications regarding the meeting, a basic information input area 14 for inputting basic information, and a facility selection area 16 for selecting facilities to be used for the meeting. Furthermore, the information input area 11a includes, at the bottom, an icon 15 for instructing automatic extraction of candidate dates.

[0066] The basic information input area 14 includes an input field for the title of the schedule to be adjusted, an input field for the time required for the meeting, an input field for the holding method (selection of a Web conference tool, selection of a telephone number for a telephone conference, etc.), and an input field for information identifying other users who are scheduled to attend the meeting and will be participants (e.g., user ID information). In the title input field, an arbitrary character string (e.g., "Job interview for Mr. XX") is input, or a desired title is selected from options prepared in advance as the title of the meeting, by the processor of the first terminal device 200-1 accepting an operation input by the first user via the input interface.

[0067] In the input field for the holding method, the processor of the first terminal device 200-1 accepts an operational input from the first user via the input interface, and a desired holding method is selected from predetermined holding method options (for example, WEB conference tool A, WEB conference tool B, and conference call phone number A, etc.). When any WEB conference tool is selected, a URL for accessing when holding a WEB conference may be automatically generated and displayed in the input field.

[0068] In the input field for the attending users, at least one of user ID information and group ID information of the attendees who are scheduled to attend the meeting as prospective participants is inputted by the processor of the first terminal device 200-1 accepting an operation input of the first user via the input interface. As an example of the input method, when the first user inputs at least a part of the user name or user ID information of a desired user, the corresponding user ID information is automatically inputted, when the first user inputs at least a part of the desired group name or group ID information, the corresponding group ID information is automatically inputted, or when the first user selects the desired user ID or group ID from a list of user ID information and group ID information, the input is performed. Note that multiple user ID information or multiple group ID information may be inputted in the input field.

[0069] The calendar display area 11b includes a display that specifies the schedule currently planned for each day of the week, with the days of the week on the horizontal axis and the time on the vertical axis. For example, in the example of FIG. 8A, schedule A1 is displayed from 9:00 to 11:00 on Monday the 3rd, and schedule A2 is displayed from 12:00 to 15:00 on Monday the 3rd, and so on. Here, schedules A1 to A6 and schedules B1 to B3 are displayed in different ways. This indicates that schedules A1 to A6 are schedules whose dates of holding have been confirmed, and schedules B1 to B3 are schedules whose dates of holding are currently being adjusted (i.e., schedules that are candidates for the dates of holding). In other words, the processor of the first terminal device 200-1 outputs the schedules whose dates of holding have been confirmed and the schedules whose dates of holding are currently being adjusted in different display ways so that they can be distinguished by the first user.

[0070] Returning to FIG. 5 again, when the processor of the first terminal device 200-1 accepts the input of basic information via the schedule adjustment screen 10-1 illustrated in FIG. 8A, it detects the operation input of the first user via the input interface and accepts the input of the expected participants (S113). The expected participants are other users different from the first user who is the schedule adjuster, and are preferably any user selected from the group or organization to which the first user belongs, or any group selected from the group to which the first user belongs or other groups of the organization to which the first user belongs. Specifically, the processor of the first terminal device 200-1 refers to the authority information set in association with the user ID information of the first user, and confirms which authority information is set as the authority "before the candidate schedule for the event is selected". Then, the processor of the first terminal device 200-1 accepts the input of the expected participants from among other users to whom the first user has the authority to "adjust the schedule".

[0071] For any user or group selected as a prospective participant, it may be possible to select whether participation is mandatory or optional for each user or group. A user designated as a mandatory prospective participant may be granted special authority as the organizer of the meeting, such as rearranging the schedule or starting the meeting. In addition, when multiple users are selected as prospective participants, a minimum number of participants may be set from among them, and when candidates for the date of the event are extracted, the minimum number of participants may be taken into consideration.

[0072] Here, FIG. 8B is a diagram showing an example of a screen displayed on the first terminal device 200-1 according to an embodiment of the present disclosure. Specifically, it is a diagram showing an example of the schedule adjustment screen 10-1 displayed in S113 of FIG. 5. According to FIG. 8B, the processor of the first terminal device 200-1 accepts an operation input of the first user to the prospective attendee selection area 12 displayed in the information input area 11a of the schedule adjustment screen 10-1 via an input interface, and a user selection menu 18 is displayed superimposed on the information input area 11a. In the example of FIG. 8B, for example, authority A4 is set as authority information for the first user. Therefore, the user selection menu displays a list 19 of other users belonging to the organization to which the first user belongs and groups in the organization to which the first user belongs.

[0073] The processor of the first terminal device 100-1 selects people scheduled to attend the meeting by accepting an operational input for selecting any one of the users or any one of the groups displayed in the list via the input interface.

[0074] The users and groups displayed in the list 19 may be users previously set as the same group by the administrator, or groups previously set to be displayed by the administrator. Although FIG. 8B shows that one second user is selected, it is possible to select multiple users, multiple groups, or a combination of them. Although FIG. 8B does not show the selection of whether participation is mandatory or optional for each user and group, or the setting of the minimum number of participants, it is possible to provide a new input area for selecting these. In addition, the input method of the prospective participants may be, other than the method shown in FIG. 8B, automatically inputting the user ID information associated with the user name or user ID information of the desired user when the first user inputs at least a part of the user name or user ID information of the desired group, or automatically inputting the group ID information associated with the desired group when the first user inputs at least a part of the group name or group ID information.

[0075] Furthermore, although the selection of equipment in the equipment selection area 16 will not be described in detail, it is performed in the same manner as the selection of prospective participants in the prospective participants selection area 12. For example, the processor of the first terminal device 200-1 accepts an operation input of the first user to the equipment selection area 16 via an input interface, and a equipment menu is displayed superimposed on the information input area 11a. For example, information that "the first user can refer to schedule information of equipment owned by the same organization to which the first user belongs and can adjust the schedule of the equipment" is set as authority information for the first user. In such a case, the equipment selection menu displays, for example, equipment ID information of equipment such as conference rooms and conference booths owned by the organization as a list 19. Then, the processor of the first terminal device 100-1 selects prospective participants of the meeting by accepting an operation input for selecting any of the equipment displayed in the list via the input interface.

[0076] Returning to FIG. 5, when the processor of the first terminal device 200-1 accepts the selection of prospective attendees via the schedule adjustment screen 10-1 illustrated in FIG. 8B, it accepts input of a destination for notifications regarding the meeting (e.g., notifications when the meeting dates have been finalized) (S114).

[0077] Here, Fig. 8C is a diagram showing an example of a screen displayed on the first terminal device 200-1 according to an embodiment of the present disclosure. Specifically, it is a diagram showing an example of the schedule adjustment screen 10-1 displayed in S114 of Fig. 5. According to Fig. 8C, the processor of the first terminal device 200-1 accepts an operation input by the first user to the destination setting region 13 displayed in the information input area 11a of the schedule adjustment screen 10-1 via the input interface, whereby the destination input box 21 and the additional icon 22 are displayed superimposed on the information input area 11a.

[0078] An arbitrary character string (for example, an email address of a user to be a destination) is input into the input box 21 by the processor of the first terminal device 200-1 accepting an operational input by the first user via the input interface. Also, the processor of the first terminal device 200-1 accepts an operational input by the first user to the add icon 22 via the input interface, so that the email address input into the input box 21 is added as a destination.

[0079] In addition, the destination may be set by selecting a desired destination from a list according to authority information, for example, as in the selection of a prospective participant shown in FIG. 8B. The destination is not limited to the group, organization, and authority information to which the first user belongs, but may be a destination of any user. The destination is not limited to one specific destination, but may be multiple destinations. The destination is not limited to an email address, but may be various information such as user ID information, phone number, and SNS account.

[0080] Returning to Fig. 5, when the processor of the first terminal device 200-1 accepts the setting of the destination via the schedule adjustment screen 10-1 illustrated in Fig. 8C, it accepts the selection of automatic extraction of candidates for the schedule via the input interface. The processor of the first terminal device 200-1 displays a condition input area 11c for automatic extraction of candidates in the information input area 11a via the output interface. The condition input area 11c includes input fields for inputting various conditions for automatic extraction of candidates, as will be described later in Fig. 8D. Examples of conditions for automatic extraction include the following conditions: - Other users' schedule information (other users' free time) Possible days and times for the meeting to be held The starting date for extracting candidates -Time to be secured before and after the meeting (e.g. travel time, etc.) -Dates to be excluded from the possible dates

[0081] That is, the processor of the first terminal device 200-1 accepts an operation input from the first user via the input interface, and accepts the settings of each of the conditions exemplified above (S115).

[0082] Here, Fig. 8D is a diagram showing an example of a screen displayed on the first terminal device 200-1 according to an embodiment of the present disclosure. Specifically, Fig. 8D is a diagram showing an example of a schedule adjustment screen 10-1 displayed in S115 of Fig. 5. The schedule adjustment screen 10-1 is displayed when the processor of the first terminal device 200-1 accepts an operation input by the first user on the icon 15 for automatically extracting candidates arranged in the information input area 11a of the schedule adjustment screen 10-1 shown in Figs. 8A to 8C via the input interface.

[0083] 8D, the schedule adjustment screen 10-1 includes a condition input area 11c in which input fields for conditions for automatically extracting candidate dates for the event are arranged, and a calendar display area 11b. The condition input area 11c includes the following input fields, for example: - Input field for setting other users' schedule information (other users' free time) as a condition 25 - Input fields for setting possible days and times for the meeting being scheduled26 - Input field for setting the starting date for extracting candidates27 - Input field 28 for setting the time (e.g. travel time) that should be reserved before and after the meeting - Input field for setting the dates to be excluded from the event schedule candidates29

[0084] The processor of the first terminal device 200-1 accepts the operation input of the first user via the input interface and selects a user to be considered in the input field 25 in order to set the schedule information of other users (free time of other users) as a condition. The selection may be performed in the same manner as the selection of the expected participants described in FIG. 8B. That is, the processor of the first terminal device 200-1 refers to the authority information of the first user. Authority A4, that is, the authority that "schedule information of users belonging to the same organization can be referenced" is set as the authority information for the first user. Therefore, a list of other users belonging to the organization to which the first user belongs is displayed, and a desired user or group is selected from the list to select the user to be considered. Then, when the user to be considered is selected, the user ID information of the user is displayed in the input field as shown in FIG. 8D.

[0085] Note that the expected participants selected in S113 of Fig. 5 may be automatically selected. Although not described in detail, it is also possible to select facilities to be considered in addition to users to be considered.

[0086] The processor of the first terminal device 200-1 also receives an operation input from the first user via the input interface to receive a selection of candidate days and time slots for the date of the meeting being arranged. As an example, the selection is performed by the first user selecting a desired day and time slot as a candidate date of the meeting on a screen displaying a list from Sunday to Saturday and a list of times corresponding to each day of the week. Note that although the day and time slot are selected here, it is of course possible to directly select a specific date or a specific date and time. As shown in FIG. 8D, the selected day and time slot are displayed in the input field 26 (for example, "Monday to Friday" and "9:00 to 17:00").

[0087] The processor of the first terminal device 200-1 also accepts an operation input from the first user via the input interface to accept the selection of the start date. As an example, the selection is made by the first user selecting a desired option from among options such as "now", "one day later", "one week later", and "one month later". Note that the start date is selected from a plurality of options here, but it is also possible to directly input a specific date or time. As shown in FIG. 8D, the selected option is displayed in the input field 27 (for example, "now" means that the start date for extracting candidate dates is today).

[0088] The processor of the first terminal device 200-1 also receives an operation input from the first user via the input interface to receive a selection of the time to be secured before and after the meeting. The selection is made by the first user selecting a desired option from among options such as "15 minutes," "30 minutes," "1 hour," and "1 hour 15 minutes." Note that, although the time to be secured before and after the meeting is selected from a plurality of options here, it is of course possible to input any desired time directly. Also, different times may be selected before and after the meeting. As shown in FIG. 8D, the selected option is displayed in the input field 28 (for example, "30 minutes" means that an additional 30 minutes of time is secured before and after the time selected in the meeting time of FIG. 8A).

[0089] The processor of the first terminal device 200-1 also accepts an operation input from the first user via the input interface to accept the selection of an excluded day. The selection is made by the first user selecting a desired option from among options such as "holiday," "anniversary," and "six days of the week." Note that, although the excluded day is selected from a plurality of options here, it is of course also possible to input any date directly. As shown in FIG. 8D, the selected option is displayed in the input field 29 (for example, "-" is displayed, which means that no excluded day was selected).

[0090] When each condition is input as described above, the processor of the first terminal device 200-1 accepts the first user's operation input on the execution icon 30 via the input interface, and sets the input condition.

[0091] When candidates are automatically extracted, as shown in FIG. 8D, the display of the first user's schedule information in calendar display area 11b shown in FIG. 8A etc. may be reset so that no schedule information is displayed.

[0092] Returning to Fig. 5 again, when the conditions are set as described above, the processor of the first terminal device 200-1 transmits a request for providing the user ID information of the user input in the input field 25, the equipment ID information of the equipment input in the equipment selection area 16 (Fig. 8B, etc.), and the schedule information of the user to the server device 100 via the communication interface (S116). Although not shown in particular, when the processor 111 of the server device 100 receives the request for providing via the communication interface 113, it refers to the user management table to read out the schedule information of the user associated with the received user ID information, and also refers to the equipment management table to read out the schedule information of the equipment associated with the received equipment ID information. Then, the processor 111 of the server device 100 transmits the request to the first terminal device 200-1 via the communication interface 113.

[0093] The processor of the first terminal device 200-1 receives the schedule information of each user and each facility transmitted from the server device 100 via the communication interface (S117). Then, the processor of the first terminal device 200-1 displays the schedule information of each user and each facility received via the output interface in the calendar display area 11b of the schedule adjustment screen 10-1. In addition, the processor of the first terminal device 200-1 extracts free time of each user as a candidate for the event date based on each schedule specified in the schedule information of each user and each facility (S118).

[0094] The processor of the first terminal device 200-1 narrows down the extracted candidates for the event schedule based on the day of the week and the time period entered in the entry field 26 in Fig. 8D (S119). For example, when "Monday to Friday" and "9:00 to 17:00" are set as shown in Fig. 8D, only candidates that satisfy the conditions set as described above are further extracted from the extracted candidates for the event schedule.

[0095] Next, the processor of the first terminal device 200-1 narrows down the extracted candidates for the event date from the start date entered in the entry field 27 in Fig. 8D (S120). For example, as shown in Fig. 8D, when "immediately" is set, the candidates extracted in S119 are ultimately extracted as they are, but when "one day later" is selected, only candidates that satisfy the conditions set as described above are further extracted from the candidates for the event date extracted in S119.

[0096] Next, as shown in Fig. 6, the processor of the first terminal device 200-1 narrows down the extracted candidate dates based on the time to be reserved before and after the meeting input in the input field 28 in Fig. 8D (S121). For example, when "30 minutes" is set as in Fig. 8D, only candidates that can reserve a total of 120 minutes are extracted from the candidate dates extracted in S120, which is the 60 minutes input as the meeting time in Fig. 8B, plus an additional 30 minutes to be reserved before the meeting and an additional 30 minutes to be reserved after the meeting.

[0097] Next, the processor of the first terminal device 200-1 narrows down the extracted candidates for the event date from the excluded date entered in the entry field 29 in Fig. 8D (S122). For example, as in Fig. 8D, if "-" is set, no excluded date is set, so the candidates extracted in S121 are extracted as they are, but if "Holiday" is selected, only candidates other than holidays are further extracted from the candidates for the event date extracted in S121.

[0098] As described above, when the candidate schedules are extracted, the processor of the first terminal device 200-1 displays the extracted candidates in the calendar display area 11b via the output interface (S123). Furthermore, the processor of the first terminal device 200-1 accepts an operation input from the first user via the input interface, accepts a selection of a specific candidate to be excluded from the automatically extracted candidate schedules, and confirms the candidate schedules (S124).

[0099] Here, Fig. 8E is a diagram showing an example of a screen displayed on the first terminal device 200-1 according to an embodiment of the present disclosure. Specifically, Fig. 8E is a diagram showing an example of a schedule adjustment screen 10-1 displayed in S123 of Fig. 6. According to Fig. 8E, the schedule adjustment screen 10-1 includes a condition input area 11c and a calendar display area 11b. In the condition input area 11c, each condition input in Fig. 8D is displayed, and a confirmation icon 31 for confirming the candidate is displayed.

[0100] In addition, the calendar display area 11b displays the schedule information of the second user, the tenth user, and the eleventh user selected as the users to be considered. Specifically, in the example of FIG. 8E, it is shown that there is a schedule A11 from 9:00 to 11:00 on Monday the 3rd, a schedule A12 from 12:00 to 14:00 on Monday the 3rd, and a schedule A1 from 12:00 to 15:00 on Tuesday the 4th. Here, the schedules A11 to A18 and the schedules B11 and B12 are displayed in different manners. This indicates that the schedules A11 to A18 indicate that there is a schedule for which the date of holding is fixed for any of the above users, and the schedules B11 and B12 indicate that there is a schedule for which the date of holding is currently being adjusted for any of the above users. In other words, the processor of the first terminal device 200-1 outputs the schedule for which the date of holding is fixed and the schedule for which the date of holding is being adjusted in different display manners so that they can be distinguished by the first user.

[0101] Furthermore, in addition to schedules A11 to A18 and schedules B11 and B12, candidates C11 to C15 are displayed in the calendar display area 11b in a display mode different from that of schedules A11 to A18 and schedules B11 and B12. Candidates C11 to C15 are candidates extracted in S116 to S122 of Fig. 5 and Fig. 6. That is, the candidates are narrowed down to those that satisfy "Monday to Friday" and "9:00 to 17:00" based on the day of the week and time period entered in the input field 26 (for example, although there is a free time of more than two hours from 16:00 on the 6th, it is excluded from the candidates because it does not satisfy the above time period).

[0102] Furthermore, the start date entered in input field 27 narrows down the candidates to those from today (for example, the 3rd) onwards. Furthermore, the time before and after the start date entered in input field 28 narrows down the candidates to those for which more than two hours can be secured (for example, since the meeting time is 60 minutes, only a meeting starting at 9:00 on the 5th is possible, but since it does not meet the above time period, it is excluded from the candidates). Furthermore, since "-" (i.e., no excluded days are set) is selected as the excluded date entered in input field 29, the candidates are not narrowed down by that condition.

[0103] Then, as described in S124 of Fig. 6, the processor of the first terminal device 200-1 accepts the operation input of the first user via the input interface and accepts the selection of a specific candidate to be excluded from among the automatically extracted candidates for the event schedule. As an example, the processor of the first terminal device 200-1 accepts the tap operation input of the first user on the specific candidate to be excluded via the input interface in the calendar display area 11b of Fig. 8E. In addition to the above, the processor of the first terminal device 200-1 may display a list of candidate time slots in the condition input area 11c and accept the operation input of the first user for the specific candidate to be excluded from the list.

[0104] The processor of the first terminal device 200-1 accepts an operation input by the first user on the confirmation icon 31 via the input interface, whereby the candidate date for the event is confirmed.

[0105] 6, when the candidate schedule is finalized, the processor of the first terminal device 200-1 accepts an operation input from the first user via the input interface and determines whether or not to display a preview screen that reproduces the screen displayed to the third user with whom the event is to be coordinated (S125). If the first user selects to display the preview screen, the processor of the first terminal device 200-1 displays the preview screen (S126).

[0106] Next, the processor of the first terminal device 200-1 accepts the operation input of the first user via the input interface, and saves the candidate information for the event schedule (i.e., the date, day of the week, and time period specified by the candidates C11 to C15) (S127). The processor of the first terminal device 200-1 also generates a request to generate access destination information together with the basic information, expected participant information, facility information, destination information, and candidate information for the event schedule (i.e., the date, day of the week, and time period specified by the candidates C11 to C15) input in Figures 5 and 6 (S128). This ends the process flow of the schedule adjustment process.

[0107] Although not shown in the figures, in the series of processes in Figs. 5 and 6, the first user who is the schedule adjuster can set authority information for correcting candidates for the schedule and correcting the confirmed schedule. Specifically, the processor of the first terminal device 200-1 accepts the operation input of the first user via the input interface and selects which of the authorities B1 to B4 should be granted to each user (including the first user himself / herself and the second user) or each group for correcting candidates for the schedule and which of the authorities C1 to C4 should be granted to correct the confirmed schedule. The processor of the first terminal device 200-1 generates the result of the selection as authority information. The processor of the first terminal device 200-1 transmits the generated authority information to the server device 100 via the communication interface together with a request for generating access destination information.

[0108] 4A, when the candidates for the date of the event are saved by the schedule adjustment process, the processor of the first terminal device 200-1 transmits, via the communication interface, to the server device 100, a request (T13) to generate access destination information indicating an access destination for the third user, with whom the schedule is to be adjusted, to select a candidate date. The request includes schedule information including the user ID information of the first user, as well as basic information, information on potential participants, facility information, destination information, and candidate information for the date of the event (i.e., the date, day of the week, and time period specified by candidates C11 to C15).

[0109] When the processor 111 of the server device 100 receives the creation request via the communication interface 113, the processor 111 stores information included in the received creation request in the user management table (S15). Specifically, the processor 111 of the server device 100 generates schedule ID information for identifying the received schedule information, and stores various information included in the schedule information in the schedule management table (FIG. 3C) in association with the generated schedule ID information. The processor 111 of the server device 100 also refers to the user management table (FIG. 3A) and stores the newly stored schedule ID information in the schedule management table in association with the user ID information of the user (second user) identified as a prospective participant. The processor 111 of the server device 100 also refers to the equipment management table (FIG. 3B) and stores the newly stored schedule ID information in the schedule management table in association with the equipment ID information of the equipment identified as a scheduled use. At this time, if authority information for each schedule set by the first user has been received, the authority information in the user management table is updated and stored.

[0110] When the schedule ID information, etc. is stored in the user management table, etc., the processor 111 of the server device 100 transmits the schedule information including candidate information indicating candidate dates for the schedule to the second terminal device 200-2 of the second user who is a prospective participant of the schedule, or to a destination specified in the destination information via the communication interface 113. The second terminal device 200-2 or the terminal device specified as the destination notifies the second user, etc., of a notification indicating that a new schedule has been adjusted and the candidate information, etc., via the output interface. The second terminal device 200-2, etc., which has received the notification, notifies the second user, etc., by displaying the notification received via the output interface.

[0111] When the schedule ID information or the like is stored in the user management table or the like, the processor 111 of the server device 100 generates access destination information (S16). The access destination information is information indicating an access destination that a third user, who is to coordinate a schedule such as a meeting, accesses to select a desired event date from among the candidate event dates. Typically, as the access destination information, a URL of a website is generated in which the candidate event dates are displayed as a calendar or a list and a desired candidate is output so as to be selectable (S16). It is desirable that the access destination information is generated as a unique URL for at least a schedule that is being adjusted or has not yet reached the time that has been confirmed as the event date. The processor 111 of the server device 100 stores the generated access destination information in the schedule management table, and transmits the generated access destination information (T14) via the communication interface 113 to the first terminal device 200-1 that has transmitted the generation request.

[0112] When the processor of the first terminal device 200-1 receives the access destination information via the communication interface, it accepts the operation input of the first user via the input interface, and transmits the received access information (T15) via the communication interface to the third terminal device 200-3 of the third user with whom the schedule is to be adjusted (S17). Specifically, when the URL, which is the received access destination information, is displayed on a display or the like via the input interface, the processor of the first terminal device 200-1 accepts the operation input for copying the URL. Then, the processor of the first terminal device 200-1 specifies the email address or account of the third user as the destination using an application program for communication such as email or SNS, and shares the access destination information by pasting the copied URL in the message. This ends the process of generating candidates for the event schedule.

[0113] The above-mentioned method of sharing the access destination information is merely an example, and is not limited to this method. For example, the processor of the first terminal device 200-1 may select the destination of the third user as the adjustment partner in advance, and when the access destination information is received from the server device 100, the information may be automatically transmitted to the destination, or the server device 100 may directly transmit the information to the destination of the third user without going through the first terminal device 200-1.

[0114] (B) Modifying proposed event dates Fig. 4B is a diagram showing a processing sequence executed by the processing system 1 according to an embodiment of the present disclosure. Specifically, Fig. 4B shows a processing sequence for a first user who is a schedule adjuster and a second user who is a prospective participant in the schedule to each revise a candidate date for the event. The processing sequence is mainly performed by a processor of each device executing a program stored in a memory or the like of each device.

[0115] First, a case will be described in which a second user who is a prospective participant of a schedule whose candidate schedule has been adjusted by a first user modifies the candidate schedule. According to FIG. 4B, when the processor of the second terminal device 200-2 accepts an operation input from the second user via the input interface, the processor starts an application program for schedule adjustment, executes a process related to login, and receives schedule information associated with the user ID information of the second user from the server device 100. Note that the processes of S21 to S23 and T21 and T22 are similar to the processes of S11 to S13 and T11 and T12 in FIG. 4A, and therefore detailed description thereof will be omitted. Also, the schedule information received at T22 includes authority information associated with the schedule ID of each schedule to be received.

[0116] When the processor of the second terminal device 200-2 receives the schedule information via the communication interface, it displays, for example, in a list, schedules for which the date of the event is being adjusted (i.e., schedules that are candidates for the date of the event) among the schedule information received via the output interface (S24). Then, the processor of the second terminal device 200-2 accepts an operation input of the second user via the input interface and selects a schedule to be modified from each schedule displayed in the list. At this time, the processor of the second terminal device 200-2 refers to the authority information of the second user and determines whether the second user is a user who has the authority to modify the schedule. Then, when it is determined that the second user is a user who has the authority, the processor of the second terminal device 200-2 accepts an operation input of the second user via the input interface and displays, for example, a screen similar to the screen shown in FIG. 8E, and modifies the candidates for the date of the event (for example, C11 to C15) (S25). The correction is performed by accepting a tap operation input on a candidate to be excluded, accepting an operation input to shorten or extend the period secured as a candidate, or re-inputting each condition.

[0117] When the processor of the second terminal device 200-2 accepts the second user's operation input on the save icon via the input interface, it transmits a schedule modification request (T23) via the communication interface together with the schedule ID information associated with the modified schedule and the modified schedule information.

[0118] When the processor 111 of the server device 100 receives the modification request or the like, it refers to the schedule management table and stores the modified schedule information received in association with the schedule ID information received together (S26). This ends the processing sequence when the second user, who is a prospective participant, modifies the candidate schedule.

[0119] Although not shown in the figure, for example, in the series of processes in FIG. 4B, the second user who is a prospective participant of the schedule can set authority information for modifying the candidate schedule of the schedule and for modifying the schedule after the schedule is confirmed. Specifically, the processor of the second terminal device 200-2 accepts the operation input of the second user via the input interface and selects which of the authorities B1 to B4 to grant to each user (including the first user and the second user himself) or each group for modifying the candidate schedule of the schedule and which of the authorities C1 to C4 to grant to modify the schedule after the schedule is confirmed. The processor of the second terminal device 200-2 generates the result of the selection as authority information. The processor of the second terminal device 200-2 transmits the generated authority information to the server device 100 via the communication interface together with a request for generating access destination information.

[0120] The processor 111 of the server device 100 that receives the authority information updates the authority information stored in the user management table based on the received authority information.

[0121] Next, a case will be described in which the first user, who is the adjuster of a candidate date for a schedule in which the second user is a prospective participant, corrects the candidate date. According to FIG. 4B, when the processor of the first terminal device 200-1 accepts an operation input from the first user via the input interface, it starts an application program for schedule adjustment, executes a process related to login, and receives schedule information associated with the user ID information of the first user from the server device 100. Note that, except for the point that in T32, the processor also receives schedule information in which the first user is the adjuster even though the first user is not included as a prospective participant, the processes of S31 to S33 and T31 and T32 are the same as the processes of S11 to S13 and T11 and T12 in FIG. 4A, and detailed description thereof will be omitted. In addition, the schedule information received in T32 includes authority information associated with the user ID information of the first user.

[0122] When the processor of the first terminal device 200-1 receives the schedule information via the communication interface, it displays, for example, in a list, schedules that it is coordinating (i.e., schedules that are candidates for the date of holding the event) among the schedule information received via the output interface. Then, the processor of the first terminal device 200-1 accepts an operation input by the first user via the input interface and selects a schedule for which the candidate is to be revised from each schedule displayed in the list.

[0123] At this time, the processor of the first terminal device 200-1 refers to its own authority information to determine whether the user has authority to modify the schedule. For example, before the candidate schedule for the event is selected and the desired schedule is confirmed by the third user, B4 is set as the authority information for the first user. In this case, the processor of the first terminal device 200-1 accepts an operation input from the first user via the input interface, displays a screen similar to the screen shown in FIG. 8E, and modifies the candidates for the event schedule (for example, C11 to C15) (S35). The modification is performed by accepting a tap operation input for a candidate to be excluded, accepting an operation input to shorten or extend the period reserved as a candidate, or re-inputting each condition.

[0124] When the processor of the first terminal device 200-1 accepts the first user's operation input on the save icon via the input interface, it transmits a schedule modification request (T33) via the communication interface together with the schedule ID information associated with the modified schedule and the modified schedule information.

[0125] When the processor 111 of the server device 100 receives the modification request or the like, it refers to the schedule management table and stores the modified schedule information received in association with the schedule ID information received together (S36). This ends the processing sequence when the first user, who is the coordinator, modifies the candidate schedule for the event.

[0126] As shown in Fig. 4B, according to the authority information, even a first user who is merely a coordinator and not a prospective participant can modify the schedule before the date of the event is finalized, just like a second user who is a prospective participant. In this way, even if the candidate date of the event needs to be modified, the first user who is coordinating on behalf of the first user can flexibly respond.

[0127] In addition, in FIG. 4B, both the first user and the second user are allowed to modify the schedule, but it is also possible to prohibit modification based on authority information.

[0128] (C) Confirmation of event schedule Fig. 4C is a diagram showing a processing sequence executed by the processing system 1 according to an embodiment of the present disclosure. Specifically, Fig. 4C shows a processing sequence for a third user, who is a partner in adjusting the schedule, to confirm the date of the event. This processing sequence is mainly performed by the processor of each device executing a program stored in the memory or the like of each device.

[0129] According to Fig. 4C, the processor of the third terminal device 200-3 available to the third user with whom the schedule is to be adjusted receives the access destination information transmitted at T15 in Fig. 4A via the communication interface. The processor of the third terminal device 200-3 then detects an operation input by the third user via the input interface and accepts an access request to the URL stored as the received access destination information (S41). The processor of the third terminal device 200-3 transmits an access request (T41) to the server device 100 via the communication interface to the website stored in the URL requested to be accessed.

[0130] When the processor 111 of the server device 100 receives the access request, it refers to the schedule management table and reads out the candidate information for the event date associated with the URL (access destination information) specified in the access request (S42). Then, the processor 111 of the server device 100 transmits the display information of the website including the read candidate information for the event date (T42) and the schedule ID information to the third terminal device 200-3 via the communication interface 113. The processor of the third terminal device 200-3 executes a process of selecting the candidate information for the event date (S43).

[0131] Here, Fig. 7 is a diagram showing a process flow executed in the third terminal device 200-3 according to an embodiment of the present disclosure. Specifically, Fig. 7 is a diagram showing a process flow for selecting candidates for the event schedule shown in S43 of Fig. 4C. This process flow is mainly performed by the processor of the third terminal device 200-3 reading and executing a program stored in a memory.

[0132] 7, when the processor of the third terminal device 200-3 receives display information of a website including candidate information via the communication interface, the processor displays the display information received via the output interface on a display or the like (S311). Then, the processor of the third terminal device 200-3 accepts an operation input from the third user via the input interface and selects a desired event date from among the candidate event dates (S312).

[0133] Here, Fig. 9 is a diagram showing an example of a screen displayed on the third terminal device 200-3 according to an embodiment of the present disclosure. Specifically, it is a diagram showing an example of an event schedule selection screen 10-3 displayed in S311 of Fig. 7. According to Fig. 9, the event schedule selection screen includes a schedule selection area 51a and a calendar display area 51b.

[0134] The date selection area 51a includes a list 52 of candidate dates for a schedule (meeting) associated with the access destination information, and a selection icon 53 for each candidate associated with each candidate. The calendar display area 51b displays candidates C11 to C15 (corresponding to candidates C11 to C15 in FIG. 8E) included as candidate information for the date of the meeting, showing the corresponding time period.

[0135] Here, candidate C11 is from 14:00 to 16:00 on Monday the 3rd, and it is possible to create one possible slot of 120 minutes during that period, which is the total time required for the meeting (60 minutes) and the time to reserve before and after (30 minutes each). Therefore, list 52 in schedule selection area 51a displays only one slot, "14:00 to 16:00," as a candidate for Monday the 3rd.

[0136] Candidate C12 is from 9:00 to 12:00 on Tuesday the 4th, and three different slots for the 120 minutes required for the meeting can be created by shifting the time in 30-minute increments. Therefore, in list 52 of schedule selection area 51a, three slots, "9:00 to 11:00," "9:30 to 11:30," and "10:00 to 12:00," are displayed as candidates for Tuesday the 4th. Candidate C13 is from 15:00 to 17:00 on Tuesday the 4th, and one different slot for the 120 minutes required for the meeting can be created. Therefore, in list 52 of schedule selection area 51a, one more slot, "15:00 to 17:00," is displayed as a candidate for Tuesday the 4th.

[0137] Candidate C14 is from 14:00 to 16:00 on Wednesday the 5th, and one slot for the 120 minutes required for the meeting can be created. Therefore, in the list 52 of the schedule selection area 51a, one more slot, "14:00 to 16:00", is displayed as a candidate for Wednesday the 5th. Candidate C15 is from 11:00 to 15:00 on Thursday the 6th, and five slots for the 120 minutes required for the meeting can be created by shifting the time in 30-minute increments. Therefore, in the list 52 of the schedule selection area 51a, five slots, "11:00 to 13:00", "11:30 to 13:30", "12:00 to 14:00", "12:30 to 14:30", and "13:00 to 15:00", are displayed as candidates for Thursday the 6th.

[0138] The third user selects the selection icon corresponding to the desired time slot from among the selection icons 53 displayed next to each time slot displayed in the list, thereby selecting the event date.

[0139] Although the slots are shifted in 30-minute increments here, any increment may be used, such as 5-minute increments, 10-minute increments, 15-minute increments, 60-minute increments, etc. Also, instead of displaying slots shifted by increments, candidate time slots may be displayed all at once, for example, from 9:00 to 12:00, and the third user may select a desired 120-minute slot by arbitrarily inputting it.

[0140] Also, although not specifically shown here, the processor of the third terminal device 200-3 may accept operational input from the third user via an input interface and input user information (e.g., name, user ID information, email address, etc.).

[0141] 7, when a candidate event date is selected as shown in Fig. 9, the processor of the third terminal device 200-3 generates selection information including information for identifying the selected event date. This ends the process flow for selecting candidate event dates.

[0142] Returning to Fig. 4C again, when the process of selecting candidates for the event date is performed as shown in Fig. 7, selection information (T43) including the selected event date and schedule ID information are transmitted to the server device 100 via the communication interface together with the user information of the third user. When the processor 111 of the server device 100 receives the selection information, etc., it refers to the schedule management table and stores the selected event date in association with the schedule ID information received together as confirmed schedule information (S44). Although not specifically shown in Fig. 3C, the user information of the third user received together is stored in the schedule management table as the party to adjust the event date.

[0143] When the opening date of the schedule being adjusted is confirmed, the processor 111 of the server device 100 refers to the schedule management table and transmits a confirmation notice (T44) including the confirmed opening date and the fact that the schedule has been confirmed, together with basic information, etc., associated with the schedule ID information, based on the destination information (e.g., the second user) associated with the schedule ID information. When the processor of the second terminal device 200-2 of the second user receives the confirmation notice, it displays the opening date included in the received confirmation notice and the basic information, etc., received together with it on a display, etc., via an output interface. This ends the process of confirming the opening date.

[0144] In FIG. 4C, the destination of the final notification does not include the first user who is the coordinator. However, the final notification may be sent to the first terminal device 200-1 of the first user, for example, depending on the desire of the first user.

[0145] (D) Amendments to confirmed event dates Fig. 4D is a diagram showing a processing sequence executed by the processing system 1 according to an embodiment of the present disclosure. Specifically, Fig. 4D shows a processing sequence for modifying the confirmed date of the event by a first user who is the schedule adjuster and a second user who is a prospective participant in the schedule. The processing sequence is mainly performed by the processor of each device executing a program stored in the memory or the like of each device.

[0146] First, a case where a second user who is a prospective participant of the schedule modifies the confirmed schedule will be described. According to FIG. 4D, when the processor of the second terminal device 200-2 accepts an operation input from the second user via the input interface, the processor starts an application program for adjusting the schedule, executes a process related to login, and receives schedule information associated with the user ID information of the second user from the server device 100. Note that the processes of S51 to S53 and T51 and T52 are similar to the processes of S11 to S13 and T11 and T12 in FIG. 4A, and therefore detailed description thereof will be omitted. Also, the schedule information etc. received at T22 includes authority information associated with the user ID information of the second user.

[0147] When the processor of the second terminal device 200-2 receives the schedule information via the communication interface, it displays, for example, on a calendar, the schedules for which the date of the event has been confirmed among the schedule information received via the output interface (S54). Then, the processor of the second terminal device 200-2 accepts the operation input of the second user via the input interface and selects the schedule to be modified from among the schedules displayed on the calendar. At this time, the processor of the second terminal device 200-2 refers to its own authority information and determines whether the second user is a user who has the authority to modify the schedule. Then, if it is determined that the second user is a user who has the authority, the processor of the second terminal device 200-2 accepts the operation input of the second user via the input interface and modifies the date of the event. The modification is performed, for example, by the second user specifying a new time period (60 minutes for the meeting time and 30 minutes each for the time to be secured before and after the meeting time).

[0148] When the processor of the second terminal device 200-2 accepts the second user's operation input on the save icon via the input interface, it transmits a schedule modification request (T53) via the communication interface together with the schedule ID information associated with the modified schedule and the modified schedule information.

[0149] When the processor 111 of the server device 100 receives a request for revision or the like, it refers to the schedule management table and stores the received revised schedule information in association with the schedule ID information received together (S56). The processor 111 of the server device 100 also sends an invitation request to the revised meeting to the email address of the third user stored in the schedule ID information as a party with whom to adjust the schedule. When the processor of the third terminal device 200-3 of the third user receives the invitation request, it selects whether to accept or reject the invitation, or send an alternative, and confirms the revised meeting dates. This ends the processing sequence when the second user, who is a prospective participant, revisions the confirmed meeting dates.

[0150] Next, a case will be described in which the first user, who is the coordinator of the schedule for a schedule in which the second user is a prospective participant, corrects a candidate for the schedule. According to FIG. 4D, when the processor of the first terminal device 200-1 accepts an operation input from the first user via the input interface, it starts an application program for schedule adjustment, executes a process related to login, and receives schedule information associated with the user ID information of the first user from the server device 100. Note that, except for the point that in T32, the processor also receives schedule information in which the first user is the coordinator even though the first user is not included as a prospective participant, the processes of S61 to S63 and T61 and T62 are the same as the processes of S11 to S13 and T11 and T12 in FIG. 4A, and detailed description thereof will be omitted. In addition, the schedule information received in T62 includes authority information associated with the user ID information of the first user.

[0151] When the processor of the first terminal device 200-1 receives the schedule information via the communication interface, it displays, for example, on a calendar, the confirmed schedule for which the first user is the coordinator, among the schedule information received via the output interface (S64). Then, the processor of the first terminal device 200-1 accepts the operation input of the first user via the input interface and selects the schedule to be modified from among the schedules displayed on the calendar. At this time, the processor of the first terminal device 200-1 refers to the authority information associated with the first user's user ID information to determine whether the first user is a user who has the authority to modify the schedule. For example, after the desired event date is confirmed by the third user, C2 is set as the authority information of the first user. That is, the first user does not have the authority to modify the schedule for which the event date has been confirmed, and can only make suggestions. Therefore, instead of displaying a screen for modifying the event date, the processor of the first terminal device 200-1 displays a message indicating that the first user does not have the authority to modify, thereby restricting the first user from modifying the event date (S65). If the user has the authority, the same processes as S55 to S56 are carried out. With the above, the process sequence for when the first user, who is the coordinator, modifies the event schedule is completed.

[0152] As shown in FIG. 4D, according to the authority information, after the event schedule is finalized, the first user, who is not a prospective participant but merely a coordinator, is restricted from modifying the event schedule. This makes it possible to restrict schedule modifications that are not intended by the second user. In addition, after the event schedule is finalized, coordination with the third user, who is the coordinator, is also required, so stricter restrictions must be imposed. Therefore, compared to FIG. 4B, the users who can modify the schedule are different before and after the event schedule is finalized. In this way, it is possible to set more flexible authority settings before and after the event schedule is finalized.

[0153] Although only the first user has been described above, it is possible to process other users other than the planned participants in the same way. For example, "C2" is set as the authority information for the second user's schedule for other users in the group to which the first user and the second user belong. In such a case, these users are restricted from modifying the event date, just like the first user, and are only allowed to suggest the date. On the other hand, for example, "C3" may be set in advance as the authority information for the second user's schedule by an administrator. In such a case, since the second user belongs to the same group as the first user and the second user, the candidate event date can be modified even after it has been selected.

[0154] As described above, in this embodiment, it is possible to provide a better processing device, processing program, and processing method for selecting candidate dates for holding a meeting.

[0155] 6.Other (A) Minimum number of participants In the above embodiment, three users, the second user, the tenth user, and the eleventh user, are selected as users whose expected participants and schedules are to be considered, and a time when none of the three users has any plans is extracted as a candidate from the schedule information of the three users. However, if a minimum number of participants is set for a meeting, candidates that can accommodate a number of participants that meets the minimum number of participants may be extracted from the users selected above.

[0156] For example, when two people are set as the minimum number of participants, the processor of the first terminal device 200-1 extracts a date on which any two of the second user, the tenth user, and the eleventh user can participate as a candidate date for the meeting. Then, when the third user finally selects one of the multiple candidate dates, the processor 111 of the server device 100 stores the user ID information of the two users who can participate in the selected candidate date in the schedule management table as information on the participants of the meeting. At this time, if all three users are able to participate, the processor 111 of the server device 100 may select two users randomly selected or two users selected based on a predetermined priority as the participants.

[0157] (B) Required Participants In the above embodiment, three users, the second user, the tenth user, and the eleventh user, are selected as users whose expected participants and schedules are to be considered, and a time when none of the three users has any plans is extracted as a candidate from the schedule information of the three users. However, if any of the users is set as a required expected participant and the remaining users are set as optional expected participants, candidates according to the setting may be extracted.

[0158] For example, when the second user is set as a required participant and the tenth and eleventh users are set as optional participants, the processor of the first terminal device 200-1 extracts a time slot that is free in the schedule information of the second user as a candidate for the meeting schedule. On the other hand, the processor of the first terminal device 200-1 does not particularly refer to the schedule information of the tenth and eleventh users in extracting the candidates. When the third user finally selects one of the multiple candidates for the meeting schedule, the processor 111 of the server device 100 stores the user ID information of the second user, who is a required participant, in the schedule management table as a scheduled participant of the meeting. In addition, the processor 111 of the server device 100 determines whether the tenth and eleventh users can also participate in the candidate time slot selected by the third user, and if so, stores the user ID information of the tenth and eleventh users in the schedule management table as a scheduled participant of the meeting. Note that if the tenth and eleventh users are not able to participate, their user ID information is not stored.

[0159] (C) Permission Information In the above embodiment, the authority information regarding the modification of the schedule is set such that the second user who is a prospective participant of the schedule can modify the schedule both before and after the schedule is confirmed. However, this is not limited to this, and various information can be set as the authority information. For example, among the users selected as prospective participants, it is possible to set users who can modify only before the schedule is confirmed, users who can modify both before and after the schedule is confirmed, and users who can only send a request to reset the schedule before or after the schedule is held.

[0160] For example, the authority information is set such that the second user who is a prospective participant is a user who can modify the schedule both before and after it is confirmed, the tenth user is a user who can modify the schedule only before it is confirmed, and the eleventh user is a user who can only send a request for re-setting the schedule before or after it is held. In this case, the processor of the second terminal device 200-2 refers to the authority information when modifying the candidate schedule of the event in S25 of FIG. 4B and when modifying the confirmed schedule of the event in S55 of FIG. 4D, and allows both modifications. On the other hand, the processor of the terminal device available to the tenth user refers to the authority information and allows only modifications to the candidate schedule of the event, and restricts modifications to the confirmed schedule. In addition, the processor of the terminal device available to the eleventh user refers to the authority information and transmits a request for re-setting the schedule of the event to the server device 100 when it accepts modifications to the candidate schedule of the event and modifications to the confirmed schedule. The server device 100 transmits the request to the terminal device of the coordinator or any of the users who have authority.

[0161] In addition, the administrator or coordinator can set various types of authority information as described above for each user who belongs to the same group or organization as the first user or the users who are scheduled to attend. For example, for a fourth user who belongs to the same organization as the first user and the second user but is not scheduled to attend the meeting being coordinated, it is possible to set the user as a user who can only modify the schedule before the schedule is finalized, a user who can modify the schedule both before and after the schedule is finalized, or a user who can only send a request to reset the schedule before or after the meeting is held.

[0162] In addition, in the authority information for the schedule information of other users, the authority of "can propose modifications" is set in FIG. 3A. In such a case, the processor of the terminal device of the user having the authority refers to the schedule information of the users of the planned participants to modify the candidate schedule of the event or select one or more dates for which the schedule of the event can be modified, and transmits the selected dates to the server device 100 as proposed information. Then, the terminal device of any of the planned participants that receives the proposed information may make the modifications shown in FIG. 4B or FIG. 4C. Alternatively, instead of this method, the processor of the terminal device of the user having the authority may request any of the terminal devices of the planned participants to grant authority to temporarily enable modifications, and make the modifications shown in FIG. 4B or FIG. 4C only if the request is granted.

[0163] (D) Permission of Third Parties In the above embodiment, there is no particular detail about the third user, who is the person coordinating the meeting, modifying the candidate or confirmed meeting date. However, the third user can also set the authority information in the same way as other users. However, the third user generally belongs to a different group or organization (e.g., a customer of another company) from the first and second users. In such a case, it may be undesirable from the viewpoint of security to have the authority to modify the schedule information of the second user. Therefore, it is desirable to set the authority information for the third user as a user who can only send a request for re-setting before or after the meeting date is held. The processor of the third terminal device 200-3 of the third user refers to the authority information, and when it accepts the modification of the candidate or confirmed meeting date, it transmits a request for re-setting the meeting date to the server device 100. The server device 100 transmits the request to the terminal device of the coordinator or any user with authority (e.g., a prospective participant). Then, after the re-setting request is received by each terminal device, access destination information for selecting candidate event dates again is generated by processing similar to the processing sequence shown in Figure 4A, and the desired candidate is selected from the access destination information.

[0164] (E) Extraction process for candidate dates In the above embodiment, the process of extracting candidates for the date of the event is performed by the first terminal device 200-1 that receives the schedule information of the prospective participants or the facilities, as shown in Fig. 5 and Fig. 6. However, instead of this, when the processes of S112 to S115 in Fig. 5 are performed by the first terminal device 200-1, the processor of the first terminal device 200-1 may transmit each piece of information input via the communication interface to the server device 100. Then, the processor 111 of the server device 100 executes the same processes as S118 to S122 in Fig. 5 and Fig. 6 based on each piece of information received, and extracts candidates for the date of the event. The processor 111 of the server device 100 transmits the extracted candidates to the first terminal device 200-1, and thereafter executes the same processes as in Fig. 6.

[0165] The above-described embodiment and modified examples can be appropriately substituted or appropriately combined for implementation.

[0166] The processes and procedures described in this specification can be realized not only by those explicitly described in the embodiments, but also by software, hardware, or a combination of these. Specifically, the processes and procedures described in this specification can be realized by implementing logic corresponding to the processes in a medium such as an integrated circuit, a volatile memory, a non-volatile memory, a magnetic disk, or an optical storage. In addition, the processes and procedures described in this specification can be implemented as computer programs and executed by various computers including a processing device and a server device.

[0167] Although the processes and procedures described herein are described as being executed by a single device, software, component, or module, such processes or procedures may be executed by multiple devices, multiple software, multiple components, and / or multiple modules. Furthermore, although the various information described herein is described as being stored in a single memory or storage unit, such information may be stored in multiple memories provided in a single device or multiple memories distributed across multiple devices. Furthermore, the software and hardware elements described herein may be realized by integrating them into fewer components or breaking them down into more components. [Explanation of symbols]

[0168] 1 Processing System 100 Server device 200 Terminal Equipment 200-1 First terminal device 200-2 Second terminal device 200-3 Third terminal device

Claims

1. A processing device comprising at least one processor, The at least one processor: when a first user has authority to adjust a schedule for a second user different from the first user or for equipment to be used in a meeting, a first terminal device usable by the first user accepts an operation input by the first user, and receives from the first terminal device via a communication interface user identification information for identifying the second user selected as a prospective participant of the meeting from among a plurality of users including the first user or equipment identification information for identifying the equipment, and candidate dates for holding the meeting selected according to schedule information of the second user or the equipment; generating access information indicating an access destination from which a third user, different from the first user and the second user, can select a desired meeting date from among the candidate meeting dates as a planned participant of the meeting; transmitting the generated access information to the first terminal device via the communication interface; 2. A processing device configured to perform processing for:

2. The processing device according to claim 1, wherein the at least one processor is configured to execute processing for, when it receives selection information of the desired meeting date selected by accessing the access destination from a third terminal device usable by the third user, sending a notification that the meeting date has been confirmed to a second terminal device usable by the second user or an administrator terminal device of an administrator who manages the facility.

3. The processing device according to claim 2 , wherein the notification is transmitted to a destination selected by the first user in addition to the second terminal device or the administrator terminal device.

4. The processing device according to claim 1 , wherein the plurality of users are users belonging to a group that is set in advance by an administrator who manages the plurality of users.

5. The processing device according to claim 4 , wherein the third user is not a user belonging to the group.

6. The processing device according to claim 4 , wherein users including a first user and a second user belonging to the group have authority to modify the candidate event dates before the desired event date is selected by the third user.

7. The processing device according to claim 4 , wherein users belonging to the group other than the second user who is a planned attendee of the meeting are restricted from amending the desired meeting date after the third user has selected the desired meeting date.

8. The processing device according to claim 4 , wherein a user selected by the administrator from among the users belonging to the group has authority to modify the desired event schedule after the desired event schedule has been selected by the third user.

9. The processing device according to claim 4 , wherein after the desired event date has been selected by the third user, the third user is able to reselect the event date by sending a request for re-setting to the first user or the second user.

10. The processing device according to claim 4 , wherein the first user is a user who, as a result of a setting by the second user or the administrator, has authority in advance to select candidate dates for a meeting in which the second user is a prospective participant.

11. The processing device according to claim 1 , wherein the at least one processor generates the schedule information of the second user in such a way that the candidate event dates can be distinguished before and after the desired event date is selected by the third user.

12. In a computer having at least one processor, the at least one processor is when a first user has authority to adjust a schedule for a second user different from the first user or for equipment to be used in a meeting, a first terminal device usable by the first user accepts an operation input by the first user, and receives from the first terminal device via a communication interface user identification information for identifying the second user selected as a prospective participant of the meeting from among a plurality of users including the first user or equipment identification information for identifying the equipment, and candidate dates for holding the meeting selected according to schedule information of the second user or the equipment; generating access information indicating an access destination from which a third user, different from the first user and the second user, can select a desired meeting date from among the candidate meeting dates as a planned participant of the meeting; transmitting the generated access information to the first terminal device via the communication interface; A processing program that makes it function as follows.

13. A processing method executed by at least one processor in a computer having the at least one processor, comprising: receiving, when a first user has authority to adjust the schedule of a second user different from the first user or a piece of equipment to be used in a meeting, from a first terminal device usable by the first user through a communication interface, user identification information for identifying a second user selected as a prospective participant of the meeting from among a plurality of users including the first user or equipment identification information for identifying the equipment, and candidate dates for holding the meeting selected according to schedule information of the second user or the equipment from the first terminal device; generating access information indicating an access destination from which a third user, different from the first user and the second user, can select a desired meeting date from among the candidate meeting dates as a prospective participant of the meeting; transmitting the generated access information to the first terminal device via the communication interface; A processing method comprising:

14. A processing device comprising at least one processor, The at least one processor: when a first user has authority to adjust a schedule for a second user different from the first user or for equipment to be used in a meeting, an operation input by the first user is accepted via an input interface in order to select a second user different from the first user from among a plurality of users including the first user as a person to attend the meeting or the equipment as equipment to be used in the meeting; accepting an input from the first user via the input interface to select a candidate date for the meeting according to schedule information of the second user or the facility; Transmitting second user identification information for identifying the second user or facility identification information of the facility and the selected candidate schedule for the event via a communication interface to a server device connected via a communication network; receiving, from the server device, access information indicating an access destination for a third user, different from the first user and the second user, to select a desired meeting date from among the candidate meeting dates as a planned participant of the meeting; 2. A processing device configured to perform processing for:

15. In a computer having at least one processor, the at least one processor is when a first user has authority to adjust a schedule for a second user different from the first user or for equipment to be used in a meeting, an operation input by the first user is accepted via an input interface in order to select a second user different from the first user from among a plurality of users including the first user as a person to attend the meeting or the equipment as equipment to be used in the meeting; accepting an input from the first user via the input interface to select a candidate date for the meeting according to schedule information of the second user or the facility; Transmitting second user identification information for identifying the second user or facility identification information of the facility and the selected candidate schedule for the event via a communication interface to a server device connected via a communication network; receiving, from the server device, access information indicating an access destination for a third user, different from the first user and the second user, to select a desired meeting date from among the candidate meeting dates as a planned participant of the meeting; A processing program that makes it function as follows.

16. A processing method executed by at least one processor in a computer having the at least one processor, comprising: receiving an operation input by a first user via an input interface in order to select a second user different from the first user as a scheduled participant of the meeting from among a plurality of users including the first user, or the facility as a facility to be used in the meeting, when the first user has authority to adjust a schedule for a second user different from the first user or a facility to be used in the meeting; receiving an input from the first user via the input interface to select a candidate date for the meeting according to schedule information of the second user or the facility; transmitting, via a communication interface, second user identification information for identifying the second user or facility identification information of the facility, and the selected candidate schedule for the event, to a server device connected via a communication network; receiving, from the server device, access information indicating an access destination for a third user, different from the first user and the second user, to select a desired meeting date from among the candidate meeting dates as a prospective participant of the meeting; A processing method comprising:

Images