WO2023135828A1 - Program, information processing device, and information processing method - Google Patents

Abstract

This program for causing a computer to manage schedule information of a first user and a second user includes a processor and a memory unit. The program causes the processor to execute: a schedule reception step for receiving a request from the first user to display the schedule information of the second user; and in the reception step, a schedule presentation step for presenting, to the first user as the schedule information of the second user in response to the request, a schedule group that includes a plurality of pieces of schedule information stored for each of a plurality of accounts associated with the second user.

Description

Program, information processing device and information processing method

The present disclosure relates to a program, an information processing device, and an information processing method.

2. Description of the Related Art In recent years, there has been known a system for mutually adjusting schedule dates and times for a plurality of users using an information processing terminal such as a smart phone.
Patent Literature 1 discloses an information processing device and a schedule management program capable of proposing an optimum schedule to a user.
In Patent Document 2, it is possible for the person concerned or the person concerned to always grasp his or her own schedule and work, making it possible to make a schedule that is impossible in terms of time, or to forget a work or event for which the exact date and time are not decided. A schedule management system is disclosed that can solve the problem.

JP 2013-109525 A Japanese Patent Application Laid-Open No. 2006-313429

In recent years, with the diversification of work styles such as side jobs and side jobs, as well as the way people spend their private lives, a single user can manage multiple schedules using multiple accounts that differ for each position, such as work, hobbies, and family. is being done.
When a user had multiple accounts, members who belonged to a company, team, family, etc. could only see the schedule of the account linked to the company, team, or family. . As a result, schedule information for a specific member of a company, team, family, etc. cannot be shared appropriately with members of other companies, teams, families, etc., and there is room for improvement in the convenience of schedule adjustment. .

Therefore, the present disclosure has been made to solve the above problems, and its purpose is to provide a technique for users to conveniently adjust their schedules in a schedule management service.

A program to be executed by a computer comprising a processor and a storage unit and managing schedule information of a first user and a second user, wherein the program causes the processor to transfer schedule information of the second user from the first user to schedule information of the second user. a schedule receiving step for receiving a request to display a schedule group including a plurality of schedule information stored for each of a plurality of accounts associated with the second user in response to the request in the receiving step; and a plan presenting step of presenting the plan information of the second user to the first user.

According to the present disclosure, the first user can check the availability of appointments stored for each of the multiple accounts associated with the second user at once. In a schedule management service in which users are associated with multiple accounts, users can conveniently adjust their schedules.

1 is a diagram showing an overall configuration of an information processing system 1; FIG. 3 is a block diagram showing the functional configuration of the server 10; FIG. 2 is a block diagram showing the functional configuration of a first user terminal 20 used by a first user; FIG. It is a block diagram which shows the functional structure of the 2nd user terminal 30 which a 2nd user uses. FIG. 10 is a diagram showing the data structure of a user table 1012; FIG. FIG. 10 is a diagram showing the data structure of a team table 1013; FIG. FIG. 10 shows the data structure of an account table 1014. FIG. FIG. 10 is a diagram showing the data structure of an affiliation table 1015. FIG. FIG. 10 is a diagram showing the data structure of a public table 1016. FIG. FIG. 10 shows the data structure of a schedule table 1017. FIG. FIG. 10 shows the data structure of a scheduled member table 1018. FIG. FIG. 10 is a diagram showing the data structure of a candidate management table 1019; FIG. FIG. 10 is a diagram showing the data structure of a candidate table 1020; FIG. FIG. 10 shows the data structure of candidate member table 1021. FIG. 4 is a flowchart showing the operation of schedule presentation processing in the server 10. FIG. 4 is a flowchart showing the operation of schedule adjustment processing in the server 10; It is an example of a display screen of the schedule presentation process in the first user terminal 20 4 is an example of a display screen of a calendar screen on the second user terminal 30; FIG. 11 is an example of a display screen of candidate presentation processing in the first user terminal 20; FIG. It is an example of a display screen of the candidate proposal process in the third user terminal 40 FIG. 11 is an example of a display screen of candidate confirmation processing in the first user terminal 20; FIG. 2 is a block diagram showing the basic hardware configuration of computer 90. FIG.

Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In all the drawings for explaining the embodiments, common constituent elements are denoted by the same reference numerals, and repeated explanations are omitted. It should be noted that the following embodiments do not unduly limit the content of the present disclosure described in the claims. Also, not all the components shown in the embodiments are essential components of the present disclosure. Each figure is a schematic diagram and is not necessarily strictly illustrated.

<Overview of information processing system 1>
FIG. 1 is a diagram showing the overall configuration of an information processing system 1. As shown in FIG. An information processing system 1 according to the present disclosure is an information processing system that provides a service for mutually adjusting schedule dates and times for a plurality of users.

<Basic Configuration of Information Processing System 1>
FIG. 1 shows an information processing system 1 according to the present disclosure. The information processing system 1 includes a server 10, a plurality of first user terminals 20, a second user terminal 30, and a third user terminal 40, which are connected via a network N. FIG. FIG. 2 is a block diagram showing the functional configuration of the server 10. As shown in FIG. FIG. 3 is a block diagram showing the functional configuration of the first user terminal 20 used by the first user. FIG. 4 is a block diagram showing the functional configuration of the second user terminal 30 used by the second user. The information processing system 1 may be configured with other user terminals 20A, 20B, 20C, and the like.

The server 10 is an information processing device that provides a service for mutually adjusting schedule dates and times for a plurality of users.

The first user terminal 20, the second user terminal 30, and the third user terminal 40 are information processing devices operated by users who use services. The first user terminal 20, the second user terminal 30, and the third user terminal 40 may be, for example, stationary PCs (Personal Computers), laptop PCs, or mobile terminals such as smartphones and tablets. It may also be a wearable terminal such as an HMD (Head Mount Display) or a wristwatch type terminal.

Each information processing device is composed of a computer equipped with an arithmetic device and a storage device. The basic hardware configuration of the computer and the basic functional configuration of the computer realized by the hardware configuration will be described later. For each of the server 10, the first user terminal 20, the second user terminal 30, and the third user terminal 40, a description that overlaps with the basic hardware configuration of the computer and the basic functional configuration of the computer, which will be described later, will be omitted.

The configuration and operation of each device will be described below.

<Functional Configuration of Server 10>
FIG. 2 shows a functional configuration realized by the hardware configuration of the server 10. As shown in FIG. The server 10 has a storage unit 101 and a control unit 104 .

<Configuration of Storage Unit of Server 10>
Storage unit 101 of server 10 includes application program 1011, user table 1012, team table 1013, account table 1014, affiliation table 1015, public table 1016, schedule table 1017, scheduled member table 1018, candidate management table 1019, candidate table 1020, A candidate member table 1021 is provided.
FIG. 5 is a diagram showing the data structure of the user table 1012. As shown in FIG.
FIG. 6 is a diagram showing the data structure of the team table 1013. As shown in FIG.
FIG. 7 is a diagram showing the data structure of the account table 1014. As shown in FIG.
FIG. 8 is a diagram showing the data structure of the affiliation table 1015. As shown in FIG.
FIG. 9 is a diagram showing the data structure of the public table 1016. As shown in FIG.
FIG. 10 is a diagram showing the data structure of the schedule table 1017. As shown in FIG.
FIG. 11 is a diagram showing the data structure of the scheduled member table 1018. As shown in FIG.
FIG. 12 shows the data structure of the candidate management table 1019. As shown in FIG.
FIG. 13 shows the data structure of the candidate table 1020. As shown in FIG.
FIG. 14 is a diagram showing the data structure of the candidate member table 1021. As shown in FIG.

The user table 1012 is a table that stores and manages information on member users (hereinafter referred to as users) who use the service. By registering to use the service, the user's information is stored in a new record in the user table 1012 . This enables the user to use the service according to the present disclosure.
The user table 1012 is a table having user ID and user name columns with user ID as a primary key.

User ID is an item that stores user identification information for identifying a user. User identification information is an item in which a unique value is set for each user.
The user name is an item that stores the name of the user. Any character string such as a nickname may be set as the user name instead of the full name.

The team table 1013 is a table that stores and manages information on teams made up of group members such as companies, organizations, organizations, circles, and families to which users belong. A user can selectively belong to multiple teams for each of the multiple accounts associated with the user.
The team table 1013 is a table having team ID as a primary key and columns of team ID, team name, and administrator ID.

Team ID is an item that stores team identification information for identifying the team. Team identification information is an item in which a unique value is set for each team.
The team name is an item for storing the name of the team. Any character string can be set for the team name.
The administrator ID is an item that stores the user ID of an administrator who has the authority to make various settings for the team as an administrator. Admins can invite new users to the team.

The account table 1014 is a table that stores and manages information on accounts that are associated with users of the service and that can be independently scheduled. In this disclosure, users are associated with one or more accounts. By associating the account ID with the user identification information, it is expressed that the user has an account.
The account table 1014 is a table having account ID as a primary key and columns of account ID and user ID.

The user can share the schedule information in each of the accounts owned by the user with other users belonging to the same team. A user can use multiple accounts owned by the user to coordinate schedules with various members belonging to the same team.
Account ID is an item that stores account identification information for identifying an account associated with a user. Account identification information is an item in which a unique value is set for each account.
Any character string may be used as the account identification information, but it is preferable to set an e-mail address. Users who belong to multiple teams often use different e-mail addresses as means of communication for each team. By using an e-mail address as the account ID, the user can naturally use multiple accounts according to the team to which the user belongs.
For example, a user can associate a first work email address, a second work email address, and a hobby email address as account IDs with their user ID.
The user ID is user identification information of the user associated with the account ID. By associating the account ID with the user identification information, it is expressed that the user has an account.

The affiliation table 1015 is a table for associating user IDs and team IDs. By associating the user ID with the team ID, it is expressed that the user belongs to the team. One user can belong to multiple teams.
The affiliation table 1015 is a table having columns of user ID and team ID.

An administrator can invite a user to a team by performing a predetermined operation. When the user approves the invitation to the team, the user ID and the team ID are associated and stored in the affiliation table, and the user belongs to the team.
It should be noted that the account ID may be associated with the team ID instead of the user ID.
The user ID is user identification information.
Team ID is the team identification information of the team associated with the user. By associating the user ID with the team ID, it is expressed that the user belongs to the team.

The disclosure table 1016 is a table that stores disclosure setting information for each account ID and team ID when schedule information related to an account is disclosed to other members belonging to the team. The user can store different disclosure setting information for each of the multiple accounts owned by the user for each team to which the user belongs.
The public table 1016 is a table having columns of account ID, team ID, and public flag.

Account ID is account identification information.
The team ID is team identification information of the team associated with the account ID.
The public flag is an item that stores the value of public setting information when the schedule related to the account is made public to other members belonging to the team. The public setting information can be selected by the user from among "detailed sharing", "time frame only sharing", "not sharing", and the like. A user can select and set a public flag for each account ID and team ID from a setting screen (not shown).

The schedule table 1017 is a table that stores and manages schedule information. The schedule table stores schedule information for each account held by the user.
The schedule table 1017 has a schedule ID as a primary key and columns of schedule ID, schedule start date and time, schedule end date and time, and schedule content data.

The schedule ID is an item for storing schedule identification information for identifying a schedule. The schedule identification information is an item in which a unique value is set for each schedule.
The scheduled start date and time is an item for storing the start date and time of the schedule.
The scheduled end date and time is an item for storing the scheduled end date and time.
The schedule data is an item that stores information about the contents of the schedule. The contents of the schedule include information such as the title of the schedule, an explanation, organizer information including the organizer's user ID, and labels. Schedule data is information used when drawing a schedule object on the calendar screen. Specifically, a title, an explanation, an organizer, etc. are drawn on the schedule object, and the user can grasp the outline of the schedule by confirming the contents of the schedule data drawn on the schedule object.

The scheduled member table 1018 is a table that stores and manages information on users participating in or invited to a schedule. By associating the schedule ID with the account ID, it is expressed that the user having the account is participating in or being invited to the schedule. A user is associated with an appointment ID for each account held by the user.
The scheduled member table 1018 is a table having a schedule ID as a primary key and columns of a schedule ID, an account ID, and a participation flag.

The schedule ID is schedule identification information.
Account ID is account identification information. By associating the schedule ID with the account ID, it is expressed that the user is participating in or being invited to the schedule for each account.
The participation flag is an item that stores information regarding whether or not to participate in a schedule for each account. The user can select the information about whether or not to participate from among "participation", "non-participation", "hold", "others", and the like. A user can respond to a schedule invited by another user by selecting "participate", "non-participate", "hold", "other", etc., to indicate their willingness to participate in the scheduled event to which they are invited. . Depending on the contents of the participation flag selection, the display mode of the schedule object such as the color, frame line, and filling of the schedule object changes in drawing of the schedule object on the calendar screen. That is, the schedule object is displayed in an identifiable display mode according to the value of the selected participation flag.
Specifically, the schedule objects corresponding to the schedules for which participation is selected on the calendar screen are displayed in solid color, and the schedule objects for unselected schedules are displayed with only a frame, allowing the user to visually check the status of participation in the schedule. can be verified.

The candidate management table 1019 is a table for storing and managing information on schedule candidates. The schedule candidate includes a plurality of candidate information regarding schedules to be coordinated among users. The user can designate a plurality of users and invite them to the schedule candidates. Note that a configuration may be adopted in which a plurality of accounts owned by the user are specified, and each account is invited to the schedule candidate.
The candidate management table 1019 is a table having a candidate management ID as a primary key and columns of a candidate management ID and a status.

The candidate management ID is an item that stores candidate management identification information for identifying a schedule candidate. Candidate management identification information is an item in which a unique value is set for each schedule candidate.
The status is an item that stores status information of the appointment candidate specified by the candidate management identification information. The status has values such as "Waiting for approval", "Waiting for confirmation", and "Confirmed". A schedule candidate whose status is "Waiting for approval" is waiting for completion of candidate approval processing by the invited user. A schedule candidate whose status is "Waiting for Confirmation" is in a state of waiting for completion of candidate confirmation processing by the host user. A schedule candidate whose status is "confirmed" is a state in which the schedule has been confirmed and the schedule adjustment processing has been completed.

The candidate table 1020 is a table that stores and manages candidate information included in schedule candidates.
The candidate table 1020 is a table having candidate ID as a primary key and columns of candidate ID, candidate management ID, candidate start date and time, candidate end date and time, and candidate content data.

The candidate ID is an item that stores candidate identification information for identifying candidate information. Candidate identification information is an item in which a unique value is set for each piece of candidate information.
The candidate management ID is candidate management identification information. By associating the candidate ID with the candidate management ID, it is expressed that a plurality of pieces of candidate information are included in one schedule candidate.

The candidate start date and time is an item for storing the start date and time of candidate information.
Candidate end date and time is an item for storing the end date and time of candidate information.
Candidate content data is an item that stores information about candidate content. The candidate contents include information such as the title of the schedule candidate, a description, organizer information, and a label.

The candidate member table 1021 is a table that stores and manages information on users invited to participate in a schedule candidate. By associating the candidate ID with the user ID, it is expressed that the user is invited to participate in the schedule. A single user can be invited to participate in multiple appointments.
The candidate member table 1021 is a table having columns of candidate ID, user ID, and approval flag. An account ID may be used instead of the user ID. In other words, a configuration may be adopted in which an invitation to participate in a schedule candidate can be made for each account.

Candidate ID is candidate identification information.
The user ID is user identification information. By associating the candidate ID with the user ID, it is expressed that each user is invited to participate in the candidate information included in the schedule candidate.
The approval flag is an item that stores information regarding whether or not candidate information included in the schedule candidates is approved for each user. The user can select the information about approval or non-approval from "approval", "disapproval", and the like. The user can approve and respond to his/her willingness to participate for each of the invited candidate information.

<Configuration of Control Unit of Server 10>
The control unit 104 of the server 10 has a user registration control unit 1041 . Control unit 104 implements each functional unit by executing application program 1011 stored in storage unit 101 .

The user registration control unit 1041 performs processing for storing information of users who wish to use the service according to the present disclosure in the user table 1012 .
The user ID and user name information stored in the user table 1012 can be obtained by opening a web page or the like operated by the service provider from any information processing terminal and entering the user ID and user name in a predetermined input form. Send to server 10 . The user registration control unit 1041 of the server 10 stores the received user ID and user name in a new record of the user table 1012, and user registration is completed. As a result, the users stored in the user table 1012 can use the service.
Prior to registration of user information in the user table 1012 by the user registration control unit 1041, the service provider may perform a predetermined examination to limit whether the user can use the service.
The user ID may be any character string or number that can identify the user, any character string or number desired by the user, or any character string or number automatically set by the user registration control unit 1041 of the server 10. can be

<Functional Configuration of First User Terminal 20>
A functional configuration realized by the hardware configuration of the first user terminal 20 is shown in FIG. The first user terminal 20 has a storage unit 201 and a control unit 204 . The first user terminal 20 is connected to an input device 206 and an output device 208 . Input device 206 includes camera 2061, microphone 2062, keyboard 2063, mouse 2064, and the like. The output device 208 includes a display 2081, speakers 2082, and the like.

<Configuration of Storage Unit of First User Terminal 20>
The storage unit 201 of the first user terminal 20 stores a first user ID 2011 for identifying a user who uses the first user terminal 20 and an application program 2012 .
The user ID is the user's account ID. The user transmits the first user ID 2011 from the first user terminal 20 to the server 10 . The server 10 identifies the user based on the first user ID 2011 and provides the user with the service according to the present disclosure. The first user ID includes information such as a session ID temporarily assigned by the server 10 to identify the user using the first user terminal 20 .
The application program 2012 may be stored in the storage unit 201 in advance, or may be downloaded from a web server or the like operated by the service provider via the communication IF. The application program 2012 includes an interpreted programming language such as JavaScript (registered trademark) that runs on a web browser application stored in the first user terminal 20 .

<Configuration of Control Unit of First User Terminal 20>
The control unit 204 of the first user terminal 20 has an input control unit 2041 and an output control unit 2042 . By executing the application program 2012 stored in the storage unit 201 , the control unit 204 implements functional units of an input control unit 2041 and an output control unit 2042 .
The input control unit 2041 of the first user terminal 20 acquires information output from an input device such as a keyboard 2063 and a mouse 2064 of the input device 206 by the user, voice input to the microphone 2062, and information output from an input device such as the camera 2061. Execute the process. The input control unit 2041 of the first user terminal 20 executes a process of transmitting the information acquired from the input device to the server 10 together with the first user ID 2011 .
The output control unit 2042 of the first user terminal 20 receives the user's operation on the input device and information from the server 10 , and executes control processing of the display content of the display 2081 and the audio output content of the speaker 2082 .

<Functional Configuration of Second User Terminal 30>
A functional configuration realized by the hardware configuration of the second user terminal 30 is shown in FIG. The configurations of the storage unit and the control unit of the second user terminal 30 are the same as the configurations of the storage unit and the control unit of the first user terminal 20, respectively, so the description thereof will be omitted.
<Functional Configuration of Third User Terminal 40>
The configurations of the storage unit and the control unit of the third user terminal 40 are the same as the configurations of the storage unit and the control unit of the first user terminal 20, respectively, so the description thereof will be omitted.

<Operation of information processing system 1>
Each process of the information processing system 1 will be described below.
FIG. 15 is a flow chart showing the operation of the schedule presentation process in the server 10. As shown in FIG.
FIG. 16 is a flow chart showing the operation of schedule adjustment processing in the server 10 .
17 is a display screen example of the schedule presentation process in the first user terminal 20. FIG. 18 is a display screen example of the calendar screen in the second user terminal 30. FIG. 19 is a candidate presentation process in the first user terminal 20. 20 is an example of a display screen of the candidate proposal process in the third user terminal 40. FIG. 21 is an example of a display screen of the candidate confirmation process in the first user terminal 20.

<Schedule presentation process>
The schedule presentation process is a process of integrating schedule information of a plurality of accounts owned by the second user and presenting it to the first user as schedule information of the second user. Details of the schedule presentation process will be described below using the flowchart of FIG. 15 and display screen examples of FIGS. 17 and 18 .

<Overview of schedule presentation processing>
The schedule presenting process receives a request from the first user to display the schedule information of the second user, and in response to the request, displays a plurality of schedules stored for each of a plurality of accounts associated with the second user. It is a series of processes of acquiring a schedule group including information, integrating the acquired schedule group, and presenting the integrated schedule group to the first user as schedule information of the second user.

The first user launches a browser application or the like on the first user terminal 20 and accesses the website that provides the schedule management service according to the present disclosure. A website that provides a schedule management service is provided by the server 10 or the like. When the first user accesses the website, the display 2081 of the first user terminal 20 displays a calendar screen 70 including a calendar 741 and a list 723 of other members belonging to the same team as the first user. The second user can similarly access a website that provides a schedule management service on the second user terminal 30 and receive the service according to the present disclosure. A third user can similarly access a website that provides a schedule management service on the third user terminal 40 and receive the service according to the present disclosure.

17 shows a display screen example of the calendar screen 70 on the display 2081 of the first user terminal 20. FIG. On the calendar screen 70, a user name 701 of the first user who uses the service, a list 703 of team names to which the first user belongs, a list 721 of accounts owned by the user, and other information for each team to which the first user belongs. Objects such as a list of members 723 and a calendar 741 are drawn. The first user can operate various objects drawn on the calendar screen 70 by operating the input device 206 of the first user terminal 20 .

<Details of schedule presentation processing>
In step S101, the first user transmits to the server 10 a request for displaying the schedule information of the second user.
Specifically, the first user operates the input device 206 and selects the check box of the second user (USER-B) from the other members displayed in the member list 723 as the schedule information display target. . The control unit 204 of the first user terminal 20 transmits a request including the first user ID 2011 and the user ID of the second user (second user ID) to the server 10 in response to the selection of the second user by the first user. .

<Schedule Acquisition Processing>
In step S102, in response to the request, the control unit 104 of the server 10 acquires a schedule group including a plurality of schedule information stored for each of a plurality of accounts associated with the second user. , when the request is received from the first user terminal 20, the control unit 104 of the server 10 retrieves the user ID of the account table 1014 based on the second user ID included in the request, thereby obtaining the user ID associated with the second user. Acquire one or more account IDs (second account IDs).
The control unit 104 of the server 10 acquires one or more schedule IDs (second schedule IDs) associated with the second account ID by searching for the account ID in the schedule member table 1018 based on the second account ID. do.
Based on the second schedule ID, the control unit 104 of the server 10 retrieves the schedule ID of the schedule member table 1018, and retrieves one or more schedule start dates, schedule end dates, and schedule data associated with the second schedule ID. Get appointment information including .
By executing the above process for all second account IDs, schedule information can be obtained for each second account ID. A collection of schedule information for all second account IDs is called a schedule group.

The control unit 104 of the server 10 acquires the team ID (first team ID) associated with the first user by searching for the user ID in the affiliation table 1015 based on the first user ID included in the request.
The control unit 104 of the server 10 searches the public table 1016 for the account ID and team ID based on the second account ID and first team ID, and acquires the public flag for each second account ID.

In step S103, the control unit 104 of the server 10 integrates the acquired schedule group to generate integrated schedule data.
Specifically, when the public flag associated with the account ID is "share details", schedule information including schedule start date and time, schedule end date and time, and schedule data is included in the integrated schedule data. If the public flag associated with the account ID is "share only the time frame", the schedule start date and time and schedule end date and time are included, and the organizer information, schedule title, description, label, etc. are included in the schedule data. Schedule information that does not include at least one of the information about is included in the integrated schedule data. When the public flag associated with the account ID is "not shared", the schedule information is not included in the integrated schedule data.

For example, the control unit 104 of the server 10 assumes that the second account ID includes two accounts, account A and account B. When the public flag of account A is "shared in detail" and the public flag of account B is "shared in detail", the schedule information of account A and the schedule information of account B are included in the integrated schedule data. If the public flag of account A is "share details" and the public flag of account B is "share only time frame", the schedule information of account A, the scheduled start date and time of account B, and the scheduled end date and time of the integrated schedule data Include appointment information that does not include appointment data. When the public flag of account A is "share details" and the public flag of account B is "not shared", the schedule information of account A is included in the integrated schedule data, but the schedule information of account B is not included.

In step S102, if the public flag associated with the account ID is "share only the time frame", the control unit 104 of the server 10 sets the schedule including the scheduled start date and time and the scheduled end date and time, but not including the schedule data. It may be configured to acquire information. Specifically, the control unit 104 of the server 10 acquires only the scheduled start date and time and the scheduled end date and time from the schedule table 1017, and does not acquire the items of the schedule data.
Similarly, in step S102, if the public flag associated with the account ID is "do not share", the control unit 104 of the server 10 may be configured not to acquire the schedule information.
In this case, in generating the integration schedule data in step S103, the schedule information for each account ID acquired in step S102 may be included in the integration schedule data as it is. The process of integrating schedule groups and generating integrated schedule data in the present disclosure also includes such processing.

In step S104, the control unit 104 of the server 10 presents the integrated schedule data generated by integrating the schedule group to the first user as schedule information of the second user.
Specifically, the control unit 104 of the server 10 transmits the generated integration schedule data to the first user terminal 20 . The display 2081 of the first user terminal 20 displays and presents integrated schedule data to the first user as schedule information of the second user.
At this time, the display 2081 of the first user terminal may display the schedule information including the first user's schedule information. The schedule information of the first user and the schedule information of the second user are presented to the first user in an identifiable display manner by differentiating the display manner such as the color of the schedule object indicating the schedule information. do.

The schedule information of the second user, which is displayed on the display 2081 of the first user terminal, may be presented to the first user in a display mode in which the schedule information of each of the two accounts of the second user can be identified. Thereby, the first user can identify the second user's schedule information for each account, and can grasp the second user's schedule in more detail.
The schedule information of the second user displayed on the display 2081 of the first user terminal may be presented to the first user in a display mode in which the schedule information for each of the two accounts of the second user cannot be identified. . Accordingly, the first user cannot identify and grasp the schedule information of the second user for each account. The second user can prevent the first user from knowing the schedule information for each own account.
The second user sets the display settings for each predetermined account, so that the second user's schedule information presented to the first user can be displayed in a display mode in which the second user's schedule information for each of the two accounts can be identified. The schedule information for each of the two accounts of the second user may be selectively presented to the first user in one of the unidentifiable display modes.

The execution contents of the schedule presentation process will be explained based on the display screen examples of FIGS. 17 and 18.

FIG. 18 shows an example of a display screen of the calendar screen 70 on the display 3081 of the second user terminal 30. As shown in FIG. Among the objects drawn on the calendar screen 70, descriptions of objects similar to the example of the display screen of the calendar screen 70 of FIG. 17 are omitted.
The second user has two accounts, "userb@ainc..." and "userb@binc...", which are drawn in the list 723 of accounts owned by users. In the calendar 741, a schedule object 7411 based on the schedule information of the account "userb@ainc..." and a schedule object 7412 based on the schedule information of the account "userb@binc..." can be identified as objects of different colors. is presented to the second user in a display mode.
In the list 723 of other members for each team, in the team "A-INC", "userb@ainc..." is selected and set to disclose schedule information to the team members. "userb@binc..." is not in a selected state and is set not to disclose schedule information to team members. In team "B-INC", both accounts are in a selected state, and schedule information of both accounts is set to be disclosed to team members.

FIG. 17 shows an example of a display screen of the schedule presentation process in the first user terminal 20. As shown in FIG. In the list 723 of other members of each team, the second user (USER-B) is selected. At this time, when the first user has a plurality of accounts, the first user can selectively confirm the schedule information for each of his/her own accounts in a display form that can be identified as a schedule object. schedule information cannot be confirmed in an identifiable display mode.
The calendar 741 includes a schedule object 7413 based on the schedule information of the first user's account "usera@ainc..." and a schedule object 7411 based on the schedule information of the second user's account "userb@ainc...". are presented to the first user in an identifiable display manner as objects of different colors. At this time, the schedule object 7412 based on the schedule information of the second user's account "userb@binc...", which has been drawn on the calendar screen 70 of the second user terminal in FIG. 18, is not drawn.
In the schedule presentation process, the control unit 104 of the server 10 converts the schedule information of the account "userb@ainc..." which the second user is set to disclose to "A-INC" into the integrated schedule data. In addition, the schedule information of the account "userb@binc...", which is not set to be disclosed, is not included in the integrated schedule data. The appointment object based on the information is not rendered and the first user cannot see the appointment information of the second user's account "userb@binc...".

<Schedule adjustment process>
The schedule adjustment process is a process of generating schedule candidates based on the free time of the first user and the second user, and adjusting the schedules of the users, specifically the first user and the third user. The details of the schedule adjustment process will be described below using the flowchart of FIG. 16 and the display screen examples of FIGS. 19 to 21 .

<Outline of schedule adjustment processing>
In the schedule adjustment process, based on the first user's schedule information and the second user's integrated schedule information, free time is presented to the first user as a plurality of candidate information, and the plurality of candidate information presented by the first user are displayed. Receiving selection of one or a plurality of candidate information among the candidate information as selection candidate information, proposing the selection candidate information to a third user, and accepting one or a plurality of candidate information among the selection candidate information from the third user as an approval candidate This is a series of processes for accepting a selection as information, accepting a selection of at least one candidate information from the approval candidate information from the first user, and confirming the schedule candidate. It should be noted that selection of at least one candidate information from the selection candidate information may be accepted from the third user, and the schedule candidate may be confirmed.

<Details of schedule adjustment processing>
In step S301, the first user who is the host of the schedule candidate transmits to the server 10 a request for starting the schedule adjustment process following the schedule presentation process.
Specifically, a calendar is displayed on the display 2081 of the first user terminal 20 . In the calendar, a schedule object 7413 based on the first user's schedule information and a schedule object 7411 based on the integrated schedule data as the second user's schedule information shown in FIG. 17 are displayed in an identifiable display mode.
The first user operates the input device 206 of the first user terminal 20 and presses the schedule candidate creation button 781 displayed on the display 2081 of the first user terminal 20 . The control unit 204 of the first user terminal 20 transmits a request including the first user ID and the second user ID to the server 10 .
In the present disclosure, in the schedule adjustment process, the first user selects the second user (USER-B) from the member list 723, but selects another user from the member list 723 during the schedule adjustment process. Accordingly, it is possible to invite the other member to the schedule candidate and execute the schedule adjustment process. At this time, in the calendar 741, as the schedule information of the other member, a schedule object based on the integrated schedule data generated from the schedule information associated with the account of the other member is displayed as the schedule information of the first user and the second user. It is displayed in a display mode that can be distinguished from the schedule object based on.

<Candidate presentation process>
In step S302, upon receiving the request, the control unit 104 of the server 10 performs a candidate presentation process of presenting the first user with a plurality of candidate information of available times based on the first user's schedule information and integrated schedule data. Execute.
Specifically, the control unit 104 of the server 10 identifies a period that is not filled by the first user's schedule information and the integrated schedule data in a predetermined period such as the most recent one week, and identifies each period as one or a plurality of candidate data. Identify as Specifically, the control unit 104 of the server 10 selects from the scheduled start date and time to the scheduled end date and time of the schedule information included in the schedule information of the first user, the schedule information included in the integrated schedule data, and A period obtained by excluding the scheduled end date and time from the scheduled start date and time is specified as candidate data.
At this time, the control unit 104 of the server 10 may divide the candidate information into predetermined period units such as 30 minutes and 1 hour. This is because the schedule is generally adjusted in units of 30 minutes or 1 hour.
The control unit 104 of the server 10 may specify, as candidate information, excluding times outside operating hours such as 20:00 to 6:00. This is because schedules are rarely set outside of working hours.
When information indicating that an important schedule is associated with the schedule information is stored, the control unit 104 of the server 10 excludes the information before and after the important schedule and specifies it as candidate information. Also good.
When the control unit 104 of the server 10 stores information associated with the schedule information to the effect that a schedule that is not important or that other schedules such as a buffer time may be included is associated with the schedule information. , the schedule information may be specified as candidate information without being excluded.

Candidate data is data that stores candidate information regarding schedules to be coordinated between users. The candidate information includes information such as the scheduled start date and time, the scheduled end date and time, schedule content data, and the user ID or account ID of the user invited to the schedule.
In the present disclosure, the user ID of the user invited to the schedule includes the user ID of the user selected by the first user in step S301 as the adjustment partner of the schedule adjustment process. The user ID of the user invited to the appointment includes the first user ID.
Specifically, the user ID of the second user is included as the user ID of the user invited to the schedule. In step S301, when another team member is selected, the user ID of the team member is included as the user ID of the user invited to the schedule.

The control unit 104 of the server 10 transmits to the first user terminal 20 the information of the schedule candidate including one or more candidate data. The display 2081 of the first user terminal 20 draws a candidate object 7414 corresponding to the candidate data on the calendar. Candidate object 7414 is presented to the first user in a manner different from scheduled objects 7411 and 7413, whose outline is drawn with dashed lines and whose outline is drawn with solid lines, to the first user.
FIG. 19 shows a display screen example of the calendar screen 70 displayed on the display 2081 of the first user terminal 20 in the candidate presentation process.

<Candidate setting process>
In step S303, a candidate setting process is executed to receive setting of one or a plurality of pieces of candidate information among the pieces of candidate information presented by the first user as selection candidate information.
Specifically, the first user selects the candidate object 7414 corresponding to the candidate information drawn on the display 2081 of the first user terminal 20 using the input device 206 .
For example, the first user selects the candidate object 7414 drawn on the display 2081 of the first user terminal 20 using the input device 206 . The first user may select multiple candidate objects 7414 . Alternatively, the drawn candidate object 7414 may be selected as an exclusion target. A candidate object 7414 that has been selected for exclusion is labeled as excluded and displayed as an excluded candidate object 7415 .
Further, the first user can newly add and set a candidate object 7417 or the like by operating the input device 206 . The first user can set the candidate object 7417 overlapping the scheduled objects 7411 and 7413 . That is, the first user can set one or a plurality of pieces of candidate information as selection candidate information at a date and time that overlaps the first user's schedule information and the second user's integrated schedule information.
Thereby, the first user can set a plurality of pieces of candidate information corresponding to candidate objects as selection candidate information, and the first user terminal 20 can receive the selection candidate information.
After completing the setting of the candidate object 7414 , the first user operates the input device 206 of the first user terminal 20 and presses the candidate proposal button 783 drawn on the display 2081 of the first user terminal 20 . As a result, the selection candidate information is determined. The control unit 204 of the first user terminal 20 transmits a request including the received selection candidate information to the server 10 .

Note that the candidate presentation process in step S302 is not necessarily essential for executing the candidate setting process. By skipping the candidate presentation processing in step S302 and operating the input device 206, the first user can newly add the candidate object 7414 and set it as selection candidate information. That is, the first user may set selection candidate information without presenting a plurality of pieces of candidate information in step S302.

The control unit 104 of the server 10 receives selection candidate information from the received request. Control unit 104 of server 10 stores candidate data included in the received selection candidate information in candidate management table 1019 , candidate table 1020 , and candidate member table 1021 .
Upon receiving the selection candidate information, the control unit 104 of the server 10 stores in the candidate management table 1019 a new record having an arbitrary unique candidate management ID and a value of “waiting for approval” in the status. Thereby, the server 10 stores that the selection candidate information has been newly received.
The control unit 104 of the server 10 associates the scheduled start date and time, scheduled end date and time, and scheduled content data of one or more candidate data included in the selection candidate information with candidate management IDs in the candidate management table 1019 of the selection candidate information. They are associated and stored in the items of candidate start date and time, candidate end date and time, and candidate content data of a new record in the candidate table 1020 . The control unit 104 of the server 10 associates the user ID of the user invited to the schedule of one or more candidate data included in the selection candidate information with the candidate ID of the candidate table of the candidate data, and sets the user ID item. memorize to
As a result, one or a plurality of candidate data included in the selection candidate information are stored in association with the candidate management table 1019, the candidate table 1020, and the candidate member table 1021. FIG.

By operating the input device 206, the first user designates the third user as an invited user from a screen (not shown) for designating an invited user for a schedule candidate. Note that the first user and the third user do not need to belong to the same team. Also, the third user does not need to be a member of the schedule management service according to the present disclosure.

The control unit 104 of the server 10 notifies the third user by sending a message or the like indicating that the invitation to the schedule candidate has been received from the first user by means of contact means such as e-mail.
The control unit 104 of the server 10 sends a message including candidate start date and time, candidate end date and time, candidate content data, etc. to the user by e-mail or the like based on the user ID of the user invited to the schedule, which is included in the candidate data. Send and notify by means of communication. In the present disclosure, the control unit 104 of the server 10 notifies the third user by sending a message or the like indicating that the third user is invited to the schedule based on the selection candidate information by means of contact means such as e-mail.
The message may include a URL (Uniform Resource Locator) to a web page displaying a calendar for checking selection candidate information. A character string for identifying the candidate management ID of the record newly stored in the candidate management table 1019 is embedded in the URL. The character string for specifying the candidate management ID can be the candidate management ID or any character string associated with the candidate management ID by a table (not shown) or the like.

<Candidate Proposal Processing>
In step S304, the control unit 104 of the server 10 executes candidate proposal processing for proposing the selection candidate information for which the selection has been accepted to the third user.
Specifically, the third user receives the message or the like transmitted by the first user's candidate setting process by means of contact means such as e-mail. The third user can open the URL with the browser application of the third user terminal 40 by selecting the URL described in the received message on the third user terminal 40 owned by the third user. Thereby, the third user terminal 40 transmits a request for executing the candidate proposal process to the server 10 .
Upon receiving the request, the control unit 104 of the server 10 identifies the candidate management ID from the character string included in the URL. Based on the candidate management ID, the control unit 104 of the server 10 searches for the candidate management ID in the candidate table 1020, and acquires the record of the candidate ID, the candidate management ID, the candidate start date and time, the candidate end date and time, and the candidate content data. The control unit 104 of the server 10 searches the candidate ID in the candidate member table 1021 for each acquired candidate ID, and acquires the user ID.
The control unit 104 of the server 10 identifies candidate data based on the acquired candidate start date and time, candidate end date and time, candidate content data, and user ID. The control unit 104 of the server 10 reconstructs the selection candidate information selected by the first user in step S303 based on the specified candidate data. At this time, each candidate data included in the selection candidate information includes a candidate ID for specifying candidate information in candidate table 1020 .
The control unit 104 of the server 10 transmits selection candidate information including one or more candidate data to the third user terminal 40 . The display of the third user terminal 40 draws a candidate object 7416 corresponding to the candidate data on the calendar and proposes selection candidate information to the third user. The candidate object 7416 has a dashed outline and is presented to the third user in a manner different from the scheduled objects 7411 and 7412, which have a solid outline. Note that the display of the third user terminal 40 displays the third user's own schedule information and other user's schedule information that can be displayed by the third user in a manner that can be identified as schedule objects 7411 and 7112, respectively. to display. That is, in the candidate proposal process, the third user's schedule information, the other user's schedule information that can be displayed by the third user, and the selection candidate information that has been set in the candidate setting process are individually identifiable. 3 Propose to users.
FIG. 20 shows a display screen example of the calendar screen 70 displayed on the display of the third user terminal 40 in the candidate proposal process.

<Candidate approval process>
In step S305, a candidate approval process is executed for accepting selection of one or a plurality of candidate information as approval candidate information from among the selection candidate information proposed in the candidate proposal process from the third user.
Specifically, the third user selects the candidate object 7416 corresponding to the candidate information included in the selection candidate information drawn on the display of the third user terminal 40 using the input device. For example, the third user selects candidate object 7416 drawn on the display with an input device. A third user may select multiple candidate objects 7416 . Thereby, the third user can select a plurality of pieces of candidate information corresponding to the candidate object 7416 as approval candidate information, and the third user terminal 40 can receive the approval candidate information.
After completing the selection of the candidate object 7416 , the third user operates the input device of the third user terminal 40 and presses the approval button 785 drawn on the display of the third user terminal 40 . As a result, the approval candidate information is determined. The control unit 304 of the third user terminal 40 transmits a request including the third user ID and the received approval candidate information to the server 10 .

Control unit 104 of server 10 receives approval candidate information from the received request. Control unit 104 of server 10 stores the value of "approval" in the approval flag of the candidate member table based on the candidate data included in the received approval candidate information.
Specifically, the control unit 104 of the server 10 searches for the candidate ID and user ID in the candidate member table 1021 using the candidate ID and the third user ID included in the candidate data of the approval candidate information, and searches for the record specified by the search. store the value of "approval" in the approval flag item of . Thereby, the third user can approve the approved candidate information as the approval candidate information among the selection candidate information proposed by the first user.

The control unit 104 of the server 10 stores the value of “waiting for confirmation” in the status item of the target record in the candidate management table 1019 .
If a plurality of users have been invited, the control unit 104 of the server 10 sets the status item of the target record in the candidate management table 1019 to the value of "Waiting for confirmation" after candidate approval processing by all users is completed. may be remembered.
If a plurality of users have been invited, the control unit 104 of the server 10 sets the status item of the target record in the candidate management table 1019 to the value of "Waiting for confirmation" after candidate approval processing by all users is completed. may be remembered.

The control unit 104 of the server 10 notifies the first user by sending a message or the like indicating that the third user has approved the invitation of the schedule candidate by means of contact means such as e-mail.
The message may include a URL to a web page that displays a calendar for checking approval candidate information. A character string for identifying the candidate management ID in the candidate management table 1019 related to the schedule candidate approved by the third user is embedded in the URL.
If a plurality of users have been invited, the control unit 104 of the server 10 confirms that the host (first user) of the schedule candidate has been invited after candidate approval processing has been completed by all users. A message or the like indicating that all users have approved may be sent by communication means such as e-mail.

<Candidate confirmation process>
In step S306, candidate confirmation processing is executed to receive selection of at least one piece of candidate information from among the approval candidate information selected in the candidate approval processing from the first user.
Specifically, the first user receives the message or the like transmitted by the third user's candidate approval process by means of contact means such as e-mail. The first user can open the URL with the browser application of the first user terminal 20 by selecting the URL described in the received message on the first user terminal 20 . Accordingly, the first user terminal 20 transmits to the server 10 a request for executing the candidate confirmation process.

Upon receiving the request, the control unit 104 of the server 10 identifies the candidate management ID from the character string included in the URL. Based on the candidate management ID, the control unit 104 of the server 10 searches the candidate table 1020 for the candidate management ID, and acquires the record of the candidate ID, candidate management ID, candidate start date and time, candidate end date and time, and candidate content data. The control unit 104 of the server 10 searches the candidate ID in the candidate member table 1021 for each acquired candidate ID, and acquires the user ID.
The control unit 104 of the server 10 identifies candidate data based on the acquired candidate start date and time, candidate end date and time, candidate content data, and user ID. Control unit 104 of server 10 reconstructs approval candidate information approved by the third user in step S305 based on the specified candidate data. At this time, each candidate data included in the approval candidate information includes a candidate ID for specifying the candidate information in the candidate table 1020 and an approval flag value for each invited user.

At this time, the approval candidate information may be reconstructed by excluding records whose approval flag is “disapproved” in the candidate member table 1021 . If multiple users have been invited, it may be reconfigured to exclude records that have not been "approved" by all users.
Control unit 104 of server 10 transmits approval candidate information including one or more candidate data to first user terminal 20 . Display 2081 of first user terminal 20 presents to the first user an approval object 765 based on candidate data included in the approval candidate information. The first user operates the input device 206 of the first user terminal 20 to select one or more approval objects 765 from the approval objects 765 displayed on the display 2081 of the first user terminal 20 . The first user operates the input device 206 of the first user terminal 20 and presses the confirm button 787 displayed on the display 2081 of the first user terminal 20 . As a result, the schedule candidate is determined. The control unit 204 of the first user terminal 20 transmits to the server 10 a request including a plurality of pieces of candidate information that have been selected and confirmed.

FIG. 21 shows an example of a display screen displayed on the display 2081 of the first user terminal 20 in the candidate confirmation process. On the display screen, the user name 701 of the first user who uses the service, a list 703 of team names to which the first user belongs, a candidate period 761 of the schedule candidate currently being adjusted, a meeting time 762, candidate content data 763, An approval object 765 is rendered. The approval object 765 may be drawn as a plurality of approval objects 765 obtained by dividing the period from the candidate start date and time to the candidate end date and time by the meeting time based on the candidate start date and time, the candidate end date and time, and the meeting time of the candidate data. .

<Candidate memory processing>
In step S307, the control unit 104 of the server 10 receives candidate information from the received request. The control unit 104 of the server 10 stores the new schedule in the schedule table 1017 and scheduled member table 1018 based on the candidate data included in the candidate information.
The control unit 104 of the server 10 generates a new record for each selected candidate data, and stores the candidate start date and time, the candidate end date and time, and the candidate content data included in the candidate data in the new record of the schedule table 1017. It is stored in the items of scheduled start date and time, scheduled end date and time, and scheduled content data. The control unit 104 of the server 10 searches for the user ID of the account table 1014 based on the user ID of the user invited to the schedule included in the candidate data, and retrieves the account ID associated with each user invited to the schedule. to get The control unit 104 of the server 10 stores the schedule ID of the newly created record in the schedule table 1017 and the acquired account ID in the items of the schedule ID and account ID of the new record of the scheduled member table 1018, respectively. If a user invited to a schedule is associated with a plurality of accounts, only a predetermined account may be stored according to the user's wishes. Thereby, only a predetermined account ID can be associated with the schedule ID according to the user's desire.
The control unit 104 of the server 10 stores a value of “confirmed” in the status item of the target record in the candidate management table 1019 .

<Candidate notification process>
In step S308, the control unit 104 of the server 10 notifies the third user by sending a message or the like indicating that the schedule candidate has been confirmed by means of communication means such as e-mail. By selecting the schedule object of the calendar displayed on the display of the third user terminal 40, the third user can answer whether or not to participate in the schedule corresponding to the schedule object. At this time, the third user can select a predetermined account from among one or a plurality of accounts held, and answer whether or not to participate.
When the third user operates the input device of the third user terminal 40 and presses the "participate" button arranged in the schedule object displayed on the display of the third user terminal 40, the control unit of the third user terminal 40 transmits to the server 10 a request including the schedule ID associated with the schedule object, the reply value of participation/non-participation, and the account ID of the account that answers the participation/non-participation. The control unit 104 of the server 10 searches for the account ID and the schedule ID in the scheduled member table 1018 based on the account ID and the schedule ID included in the received request, and enters the participation flag in the entry of the record specified by the search. - Store the answer value of non-participation. As a result, the will of the third user regarding participation or non-participation in the schedule is stored, and the first user can confirm whether the third user will participate in the schedule or not.

<Modification>
In place of the candidate proposal process in step S305, in place of the candidate confirmation process in step S306, candidate confirmation process for accepting selection of at least one of the candidate information proposed in the candidate proposal process from the third user. may be executed.
Specifically, the third user selects the candidate object 7416 corresponding to the candidate information included in the selection candidate information drawn on the display of the third user terminal 40 using the input device. For example, the third user selects candidate object 7416 drawn on the display with an input device. A third user may select multiple candidate objects 7416 .
The third user operates the input device of the third user terminal 40 and presses the confirm button 787 displayed on the display of the third user terminal 40 . As a result, the schedule candidate is determined. The control unit of the third user terminal 40 transmits to the server 10 a request including a plurality of pieces of candidate information that have been selected and confirmed.

The control unit 104 of the server 10 executes candidate storage processing. Since the candidate storage process is the same as step S307, description thereof is omitted.
After the candidate storage process, the control unit 104 of the server 10 executes the candidate notification process for the first user. The candidate notification process is the same as step S308 except that the notification destination is not the third user but the first user, and thus the description is omitted.

<Computer hardware configuration>
FIG. 22 is a block diagram showing the basic hardware configuration of the computer 90. As shown in FIG. The computer 90 includes at least a processor 901, a main storage device 902, an auxiliary storage device 903, and a communication IF 991 (Interface). These are electrically connected to each other by a communication bus 921 .

The processor 901 is hardware for executing the instruction set described in the program. The processor 901 is composed of an arithmetic unit, registers, peripheral circuits, and the like.

The main storage device 902 is for temporarily storing programs and data processed by the programs. For example, it is a volatile memory such as a DRAM (Dynamic Random Access Memory).

The auxiliary storage device 903 is a storage device for storing data and programs. Examples include flash memory, HDD (Hard Disc Drive), magneto-optical disk, CD-ROM, DVD-ROM, and semiconductor memory.

The communication IF 991 is an interface for inputting and outputting signals for communicating with other computers via a network using a wired or wireless communication standard.
The network is composed of various mobile communication systems constructed by the Internet, LAN, wireless base stations, and the like. For example, networks include 3G, 4G, and 5G mobile communication systems, LTE (Long Term Evolution), wireless networks (for example, Wi-Fi (registered trademark)) that can be connected to the Internet through predetermined access points, and the like. For wireless connection, communication protocols include, for example, Z-Wave (registered trademark), ZigBee (registered trademark), Bluetooth (registered trademark), and the like. In the case of wired connection, the network includes direct connection using a USB (Universal Serial Bus) cable or the like.

It should be noted that the computer 90 can be virtually realized by distributing all or part of each hardware configuration to a plurality of computers 90 and connecting them to each other via a network. Thus, the computer 90 is a concept that includes not only the computer 90 housed in a single housing or case, but also a virtualized computer system.

<Basic Functional Configuration of Computer 90>
A functional configuration of the computer realized by the basic hardware configuration (FIG. 22) of the computer 90 will be described. The computer includes at least functional units of a control section, a storage section, and a communication section.

It should be noted that the functional units included in the computer 90 can be implemented by distributing all or part of each functional unit to a plurality of computers 90 interconnected via a network. The computer 90 is a concept that includes not only a single computer 90 but also a virtualized computer system.

The control unit is implemented by the processor 901 reading various programs stored in the auxiliary storage device 903, developing them in the main storage device 902, and executing processing according to the programs. The control unit can implement functional units that perform various information processing according to the type of program. Thereby, the computer is implemented as an information processing device that performs information processing.

The storage unit is realized by the main storage device 902 and the auxiliary storage device 903. The storage unit stores data, various programs, and various databases. Also, the processor 901 can secure a storage area corresponding to the storage unit in the main storage device 902 or the auxiliary storage device 903 according to a program. In addition, the control unit can cause the processor 901 to execute addition, update, and deletion processing of data stored in the storage unit according to various programs.

A database refers to a relational database, and is used to manage tabular tables structurally defined by rows and columns, and data sets called masters in association with each other. In a database, a table is called a table, a master is called a column, and a row is called a record. In a relational database, relationships between tables and masters can be set and associated.
Normally, each table and each master has a primary key column for uniquely identifying a record, but setting a primary key to a column is not essential. The control unit can cause the processor 901 to add, delete, and update records in specific tables and masters stored in the storage unit according to various programs.

Note that the database and master in the present disclosure may include any data structure (list, dictionary, associative array, object, etc.) in which information is structurally defined. The data structure also includes data that can be regarded as a data structure by combining data with functions, classes, methods, etc. written in any programming language.

The communication unit is realized by the communication IF 991. The communication unit implements a function of communicating with another computer 90 via a network. The communication section can receive information transmitted from another computer 90 and input it to the control section. The control unit can cause the processor 901 to execute information processing on the received information according to various programs. Also, the communication section can transmit information output from the control section to another computer 90 .

<Appendix>
The items described in the above embodiments will be added below.

(Appendix 1)
A program to be executed by a computer comprising a processor and a storage unit and managing schedule information of a first user and a second user, wherein the program causes the processor to transfer schedule information of the second user from the first user to schedule information of the second user. a schedule receiving step (S101) for receiving a request to display a schedule including a plurality of schedule information stored for each of a plurality of accounts associated with the second user in response to the request in the receiving step A program for executing a schedule presenting step (S102, S103, S104) of presenting a schedule group to a first user as schedule information of a second user.
As a result, the user can conveniently adjust the schedule. The first user can identify the second user's schedule information for each account, and can grasp the second user's schedule in more detail.

(Appendix 2)
The schedule presenting step integrates a schedule group including a plurality of schedule information stored for each of a plurality of accounts associated with the second user, and presents the schedule information to the first user as schedule information of the second user. The program according to Appendix 1, which is a step of:
Thereby, the second user can prevent the schedule information for each own account from being known to the first user.

(Appendix 3)
A program to be executed by a computer comprising a processor and a storage unit and managing schedule information of a first user and a second user, wherein the program causes the processor to transfer schedule information of the second user from the first user to schedule information of the second user. a schedule receiving step (S101) for receiving a request to display a schedule including a plurality of schedule information stored for each of a plurality of accounts associated with the second user in response to the request in the receiving step A program for executing an acquisition step (S102) of acquiring a schedule group and a schedule presentation step (S104) of presenting the schedule group to a first user as schedule information of a second user.
This allows the user to conveniently adjust the schedule. The first user can identify the second user's schedule information for each account, and can grasp the second user's schedule in more detail.

(Appendix 4)
The program causes the processor to execute an integration step (S103) for integrating the schedule group acquired in the acquisition step, and the schedule presentation step includes the schedule group integrated in the integration step as schedule information of the second user. 3. The program of Appendix 3, which is the step of presenting to.
Thereby, the second user can prevent the schedule information for each own account from being known to the first user.

(Appendix 5)
A plurality of schedule information included in the schedule group acquired in the acquisition step are associated with a plurality of public flags corresponding to each of the plurality of schedule information, and the plurality of public flags are associated with each team to which the second user belongs. 5. The program of clause 4, wherein different values can be set.
Thereby, the second user can set a different public flag for each team to which the second user belongs, for each of the multiple accounts associated with the second user.

(Appendix 6)
A plurality of pieces of schedule information included in the schedule group acquired in the acquisition step are associated with a plurality of public flags corresponding to the plurality of pieces of schedule information, and a different value can be set for each of the plurality of public flags. A program according to Appendix 4 or 5.
This allows the second user to set different public flags for each of the multiple accounts associated with the second user.

(Appendix 7)
The schedule group obtained in the obtaining step includes first schedule information stored for a first account associated with the second user and second schedule information stored for a second account associated with the second user. 2 schedule information, wherein the first schedule information is associated with the first disclosure flag, the second schedule information is associated with the second disclosure flag, and the integrating step includes: the first schedule information, the second schedule information, and the second schedule information. 7. The program according to any one of Appendices 4 to 6, which is a step of integrating the schedule group based on the schedule information, the first disclosure flag and the second disclosure flag.
This allows the second user to set a public flag for each of the multiple accounts associated with the second user.

(Appendix 8)
the integrating step includes integrating the first schedule information and not including the second schedule information in the schedule group when the first disclosure flag is open and the second disclosure flag is not shared; The program according to Appendix 7.
As a result, the schedule of one's own specific account can be disclosed to a specific team or kept secret.

(Appendix 9)
In the integration step, when the first disclosure flag is open and the second disclosure flag is shared only for the time frame, the first schedule information is included in the schedule group, and the second schedule information other than the start date and time and the end date and time is included in the schedule group. 9. A program according to clause 7 or 8, which is the step of consolidating so as not to include information.
As a result, it is possible to disclose only the time frame for adjusting the schedule to the specific team while keeping the schedule contents of the user's specific account secret from the specific team.

(Appendix 10)
8. The program according to any one of appendices 3 to 7, wherein the first user belongs to the same team as the second user.
As a result, it is possible to disclose only the time frame for adjusting the schedule to the specific team while keeping the schedule contents of the user's specific account secret from the specific team.

(Appendix 11)
11. Any one of attachments 8 to 10, wherein the schedule presenting step is a step of presenting the first user's schedule information and the integrated second user's schedule information in an identifiable manner to the first user. program as described.
Thereby, the first user can confirm his/her own schedule information and the integrated schedule information of the second user in an identifiable manner, and can conveniently adjust the schedule with the second user. .

(Appendix 12)
The program provides the processor with a candidate setting step (S303) for accepting setting of one or a plurality of candidate information as selection candidate information from the first user, and sending the selection candidate information set accepted in the candidate setting step to the third user. 12. The program according to any one of Appendices 1 to 11, which executes a candidate proposal step (S304) of making a proposal to the candidate.
Thereby, the third user can check the presented selection candidate information and adjust the schedule. You can adjust your schedule conveniently.

(Appendix 13)
In the candidate proposal step, the schedule information of the third user, the schedule information of other users that can be displayed by the third user, and the selection candidate information whose setting is accepted in the candidate setting step are respectively identifiable, and the third user 13. The program according to Appendix 12, which is a step of proposing to
As a result, the third user can confirm the presented selection candidate information while confirming his own schedule, and can adjust the schedule. You can adjust your schedule conveniently.

(Appendix 14)
A program to be executed by a computer that includes a processor and a storage unit and manages schedule information of a first user and a third user, the program causing the processor to receive one or more pieces of candidate information from the first user as selection candidate information, and a candidate proposal step (S304) of proposing the selection candidate information set in the candidate setting step to the third user. In the proposing step, the schedule information of the third user, the schedule information of other users that can be displayed by the third user, and the selection candidate information whose setting is accepted in the candidate setting step are respectively identifiable to the third user. The program, which is the step to propose against.
As a result, the third user can check the presented selection candidate information while checking his/her own schedule, and adjust the schedule. You can adjust your schedule conveniently.

(Appendix 15)
The program causes the processor to present a plurality of candidates of free time to the first user as a plurality of candidate information based on the first user's schedule information and the second user's integrated schedule information presented in the schedule presentation step. a presentation step (S302); a candidate setting step (S303) of receiving, from the first user, setting one or a plurality of candidate information among the plurality of pieces of candidate information presented in the candidate presentation step as selection candidate information; 14. The program according to appendix 12 or 13, causing a candidate proposal step (S304) of proposing the selection candidate information set in the step to the third user.
This makes it possible to adjust the schedule conveniently.

(Appendix 16)
Any of attachments 12 to 15, wherein the candidate setting step is a step capable of setting one or a plurality of candidate information as selection candidate information at a date and time that overlaps the first user's schedule information and the second user's integrated schedule information. or the program described.
Thereby, the first user can set one or a plurality of pieces of candidate information as selection candidate information for the date and time overlapping the first user's schedule information and the second user's integrated schedule information.

(Appendix 17)
The program causes the processor to execute a candidate approval step (S305) of receiving, as approval candidate information, one or a plurality of candidate information from among the selection candidate information proposed in the candidate proposal step from the third user; 17. The program according to any one of appendices 12-16.
This makes it possible to adjust the schedule conveniently.

(Appendix 18)
The program provides the processor with a candidate confirmation step (S306) for receiving, from the first user, selection of at least one of the approval candidate information selected in the candidate approval step, and receiving the selection in the candidate confirmation step. and storing the schedule information as the schedule information of the first user and the third user.
This makes it possible to adjust the schedule conveniently.

(Appendix 19)
The program provides the processor with a candidate confirmation step (S305) for receiving the selection of at least one of the selection candidate information proposed in the candidate proposal step from the third user; 17. The program according to any one of appendices 12 to 16, causing the execution of the step of storing the information as schedule information of the first user and the third user.
As a result, schedule adjustment can be performed in the candidate confirmation step by the third user, so that it is possible to reduce the time and effort of the first user to confirm the candidate.

(Appendix 20)
An information processing apparatus comprising a processor and a storage unit, wherein the processor receives a request from a first user to display schedule information of a second user (S101); schedule presentation for presenting a schedule group including a plurality of schedule information stored for each of a plurality of accounts associated with the second user as schedule information of the second user to the first user in response to the An information processing device for executing steps (S102, S103, S104).
As a result, the user can conveniently adjust the schedule. The first user can identify the second user's schedule information for each account, and can grasp the second user's schedule in more detail.

(Appendix 21)
An information processing apparatus comprising a processor and a storage unit, wherein the processor receives a request from a first user to display schedule information of a second user (S101); an obtaining step (S102) of obtaining a schedule group including a plurality of schedule information stored for each of a plurality of accounts associated with the second user, and obtaining the schedule group as schedule information of the second user; and a schedule presentation step (S104) of presenting to the first user as a schedule presentation step (S104).
As a result, the user can conveniently adjust the schedule. The first user can identify the second user's schedule information for each account, and can grasp the second user's schedule in more detail.

(Appendix 22)
An information processing apparatus comprising a processor and a storage unit, wherein a candidate setting step (S303) of receiving setting of one or a plurality of candidate information as selection candidate information from a first user to the processor, and setting in the candidate setting step and a candidate proposal step (S304) of proposing the received selection candidate information to the third user, and the candidate proposal step includes the third user's schedule information, the third user's displayable other users' and the selection candidate information set in the candidate setting step are proposed to the third user in an identifiable manner.
As a result, the third user can confirm the presented selection candidate information while confirming his own schedule, and can adjust the schedule. You can adjust your schedule conveniently.

(Appendix 23)
An information processing method executed by a computer comprising a processor and a storage unit, comprising: a schedule receiving step (S101) of receiving a request from a first user to the processor to display schedule information of a second user; In the receiving step, in response to a request, a schedule group including a plurality of schedule information stored for each of a plurality of accounts associated with the second user is sent to the first user as schedule information of the second user and a schedule presentation step (S102, S103, S104) of presenting a schedule.
This allows the user to conveniently adjust the schedule. The first user can identify the second user's schedule information for each account, and can grasp the second user's schedule in more detail.

(Appendix 24)
An information processing method executed by a computer comprising a processor and a storage unit, comprising: a schedule receiving step (S101) of receiving a request from a first user to the processor to display schedule information of a second user; an obtaining step (S102) of obtaining, in response to a request, a schedule group including a plurality of schedule information stored for each of a plurality of accounts associated with the second user in the receiving step; A schedule presenting step (S104) of presenting schedule information of two users to a first user.
As a result, the user can conveniently adjust the schedule. The first user can identify the second user's schedule information for each account, and can grasp the second user's schedule in more detail.

(Appendix 25)
An information processing method executed by a computer comprising a processor and a storage unit, comprising a candidate setting step (S303) of receiving, in the processor, setting of one or a plurality of pieces of candidate information as selection candidate information from a first user; a candidate proposal step (S304) of proposing the selection candidate information set in the candidate setting step to the third user; An information processing method, comprising: a step of proposing, to a third user, schedule information of possible other users and selection candidate information whose setting is received in the candidate setting step, in an identifiable manner.
As a result, the third user can check the presented selection candidate information while checking his/her own schedule, and adjust the schedule. You can adjust your schedule conveniently.

1 information processing system 10 server 101 storage unit 103 control unit 20 first user terminal 201 storage unit 204 control unit 30 second user terminal 301 storage unit 304 control unit

Claims (25)

1. A program comprising a processor and a storage unit and executed by a computer that manages schedule information of a first user and a second user,
   The program causes the processor to:
   a schedule receiving step of receiving a request from the first user to display the schedule information of the second user;
   In the receiving step, in response to the request, a schedule group including a plurality of schedule information stored for each of a plurality of accounts associated with the second user is set as schedule information of the second user by the first user. an appointment presentation step to present to
   program to run.
2. The schedule presenting step integrates a schedule group including a plurality of schedule information stored for each of a plurality of accounts associated with the second user, and presents the schedule information to the first user as schedule information of the second user. The steps to present,
   A program according to claim 1.
3. A program comprising a processor and a storage unit and executed by a computer that manages schedule information of a first user and a second user,
   The program causes the processor to:
   a schedule receiving step of receiving a request from the first user to display the schedule information of the second user;
   an obtaining step of obtaining, in the receiving step, a schedule group including a plurality of schedule information stored for each of a plurality of accounts associated with the second user in response to the request;
   a schedule presenting step of presenting the schedule group to the first user as schedule information of the second user;
   program to run.
4. The program causes the processor to:
   an integration step of integrating the schedule group acquired in the acquisition step;
   and
   The schedule presentation step is a step of presenting the schedule group integrated in the integration step to the first user as schedule information of the second user.
   4. A program according to claim 3.
5. the plurality of schedule information included in the schedule group acquired in the acquiring step are associated with a plurality of public flags corresponding to each of the plurality of schedule information;
   The plurality of public flags can set different values for each team to which the second user belongs,
   5. The program according to claim 4.
6. the plurality of schedule information included in the schedule group acquired in the acquiring step are associated with a plurality of public flags corresponding to each of the plurality of schedule information;
   The plurality of public flags can set different values for each user,
   6. A program according to claim 4 or 5.
7. The scheduled group obtained in the obtaining step includes:
   first appointment information stored for a first account associated with a second user;
   second appointment information stored for a second account associated with a second user;
   The first schedule information is associated with the first public flag,
   The second schedule information is associated with the second public flag,
   The integration step is a step of integrating the schedule group based on first schedule information, second schedule information, a first public flag and a second public flag,
   A program according to any one of claims 4 to 6.
8. The integration step is a step of integrating the schedule group so that the first schedule information is included in the schedule group and the second schedule information is not included when the first disclosure flag is open and the second disclosure flag is not shared. be,
   8. A program according to claim 7.
9. In the integration step, when the first public flag is open and the second public flag is shared only in the time frame, the first schedule information is included in the schedule group, and the start date and time and the end date and time of the second schedule information are included in the schedule group. is a step that integrates so as not to include information other than
   9. A program according to claim 7 or 8.
10. The first user belongs to the same team as the second user,
    A program according to any one of claims 3 to 7.
11. The schedule presenting step is a step of presenting the schedule information of the first user and the integrated schedule information of the second user in an identifiable manner to the first user.
    A program according to any one of claims 8 to 10.
12. The program causes the processor to:
    a candidate setting step of receiving a setting of one or a plurality of candidate information as selection candidate information from a first user;
    a candidate proposing step of proposing to a third user the selection candidate information set in the candidate setting step;
    12. The program according to any one of claims 1 to 11, causing the execution of
13. In the candidate proposal step, the schedule information of the third user, the schedule information of other users that can be displayed by the third user, and the selection candidate information whose setting is received in the candidate setting step are each identifiable, A step of proposing to a third user,
    13. A program according to claim 12.
14. A program comprising a processor and a storage unit and executed by a computer that manages schedule information of a first user and a third user,
    The program causes the processor to:
    a candidate setting step of receiving a setting of one or a plurality of candidate information as selection candidate information from a first user;
    a candidate proposing step of proposing to a third user the selection candidate information set in the candidate setting step;
    and
    In the candidate proposal step, the schedule information of the third user, the schedule information of other users that can be displayed by the third user, and the selection candidate information whose setting is received in the candidate setting step are each identifiable, A step of proposing to a third user,
    program.
15. The program causes the processor to:
    a candidate presenting step of presenting a first user with a plurality of candidate information of available times based on the first user's schedule information and the integrated second user's schedule information presented in the schedule presenting step;
    a candidate setting step of receiving, from a first user, setting one or a plurality of the candidate information among the plurality of pieces of candidate information presented in the candidate presentation step as selection candidate information;
    a candidate proposing step of proposing to a third user the selection candidate information set in the candidate setting step;
    to run
    14. A program according to claim 12 or 13.
16. The candidate setting step is a step in which one or a plurality of candidate information can be set as selection candidate information at a date and time that overlaps the schedule information of the first user and the integrated schedule information of the second user.
    16. The program according to any one of claims 12-15.
17. The program causes the processor to:
    a candidate approval step of receiving, from a third user, selection of one or more of the candidate information proposed in the candidate proposal step as approval candidate information;
    to run
    A program according to any one of claims 12 to 16.
18. The program causes the processor to:
    a candidate confirmation step of receiving, from a first user, selection of at least one of the approval candidate information selected in the candidate approval step;
    a step of storing the schedule information selected in the candidate confirming step as schedule information of a first user and a third user;
    to run
    18. A program according to claim 17.
19. The program causes the processor to:
    a candidate confirmation step of receiving a selection of at least one of the candidate information proposed in the candidate proposal step from a third user;
    a step of storing the schedule information selected in the candidate confirming step as schedule information of a first user and a third user;
    to run
    A program according to any one of claims 12 to 16.
20. An information processing device comprising a processor and a storage unit,
    to the processor;
    a schedule receiving step of receiving a request from the first user to display the schedule information of the second user;
    In the receiving step, in response to the request, a schedule group including a plurality of schedule information stored for each of a plurality of accounts associated with the second user is set as schedule information of the second user by the first user. a schedule presentation step to present to
    Information processing device that executes
21. An information processing device comprising a processor and a storage unit,
    to the processor;
    a schedule receiving step of receiving a request from the first user to display the schedule information of the second user;
    an obtaining step of obtaining, in the receiving step, a schedule group including a plurality of schedule information stored for each of a plurality of accounts associated with the second user, in response to the request;
    a schedule presenting step of presenting the schedule group to the first user as schedule information of the second user;
    Information processing device that executes
22. An information processing device comprising a processor and a storage unit,
    to the processor;
    a candidate setting step of receiving a setting of one or a plurality of candidate information as selection candidate information from a first user;
    a candidate proposing step of proposing to a third user the selection candidate information set in the candidate setting step;
    and
    In the candidate proposal step, the schedule information of the third user, the schedule information of other users that can be displayed by the third user, and the selection candidate information whose setting is received in the candidate setting step are each identifiable, A step of proposing to a third user,
    Information processing equipment.
23. An information processing method executed by a computer comprising a processor and a storage unit,
    to the processor;
    a schedule receiving step of receiving a request from the first user to display the schedule information of the second user;
    In the receiving step, in response to the request, a schedule group including a plurality of schedule information stored for each of a plurality of accounts associated with the second user is set as schedule information of the second user by the first user. an appointment presentation step to present to
    Information processing method that causes the execution of
24. An information processing method executed by a computer comprising a processor and a storage unit,
    to the processor;
    a schedule receiving step of receiving a request from the first user to display the schedule information of the second user;
    an obtaining step of obtaining, in the receiving step, a schedule group including a plurality of schedule information stored for each of a plurality of accounts associated with the second user, in response to the request;
    a schedule presenting step of presenting the schedule group to the first user as schedule information of the second user;
    Information processing method that causes the execution of
25. An information processing method executed by a computer comprising a processor and a storage unit,
    to the processor;
    a candidate setting step of receiving a setting of one or a plurality of candidate information as selection candidate information from a first user;
    a candidate proposing step of proposing to a third user the selection candidate information set in the candidate setting step;
    and
    In the candidate proposal step, the schedule information of the third user, the schedule information of other users that can be displayed by the third user, and the selection candidate information whose setting is received in the candidate setting step are each identifiable, A step of proposing to a third user,
    Information processing methods.