JP2017059025A - Schedule management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To prevent double booking in making a schedule arrangement about multiple cases.SOLUTION: A schedule management system has a processor and a memory to be connected to the processor. The memory holds schedule information where one or more schedules extracted from each of multiple messages to be transmitted for adjusting an event schedule are registered as undecided schedules corresponding to identification information for the respective messages. When receiving information for newly deciding any one of the undecided schedules, the processor determines whether or not any one of the undecided schedules corresponding to the messages other than the message corresponding to the newly decided schedule overlaps with the newly decided schedule, and when any one of the undecided schedule overlaps with the newly decided schedule, it outputs information announcing the overlapping undecided schedule.SELECTED DRAWING: Figure 2

Description

  The present invention relates to a schedule management technique using a computer.

  As a technique for automating the schedule, there are techniques disclosed in Japanese Patent Application Laid-Open No. 2006-53705 (Patent Document 1) and Japanese Patent Application Laid-Open No. 2010-191812 (Patent Document 2).

  Patent Document 1 states that “a mail distribution system that distributes an e-mail having one or more schedule information having a schedule date and schedule contents to a schedule information notification device, via the mail distribution system and a communication line” A schedule information notification system comprising one or more schedule information notification devices connected, and when the schedule information notification device receives an email, it sequentially reads the schedule information from the email and corresponds to each schedule information Creates posting data with scheduled date and schedule content to be output, and outputs mailer to schedule part, and schedule part to register posting data in schedule data and execute notification of schedule information based on this schedule data The schedule information notification system characterized by the above. "

  Patent Document 2 includes “a communication processing unit that transmits and receives data to and from other terminals by wireless communication, and a schedule function unit that registers or reads schedule information in and from the schedule book. Generates a reservation request including destination information of a communication partner for wireless communication and schedule information to be registered in the schedule book, and outputs the reservation request to the communication processing unit, and receives it via the communication processing unit And a message analysis unit for extracting schedule information from the reservation request, and when the user inputs an instruction to accept the reservation request, the schedule information extracted by the message analysis unit is scheduled. It is output to the function part and schedule information is registered in the schedule book. "

JP 2006-53705 A JP 2010-191812 A

  Conventionally, when determining a schedule, the schedule information is generally described and managed in a schedule table or scheduler in the PC. Meeting time, meeting, meeting, etc. meeting for business people and friends are coordinated via telephone, e-mail, or SNS (Social Network Service). However, when using a telephone as a means to make an appointment reservation, it is necessary for the recipient to be able to answer the call when making a call, unless the telephone with the person you want to make an appointment with is connected. There was a problem that the schedule could not be confirmed. Even if the telephone is connected and the reservation can be confirmed, the partner who has received the reservation needs to manually fill in the schedule in the scheduler or the like in the PC, which is troublesome. This trouble also occurs when a promise request is sent through electronic mail. Also, when communicating via SNS, the possibility of information being viewed by a third party must also be taken into account. For this reason, for example, Patent Document 1 describes a technique for automatically registering schedule information described in an e-mail in a schedule book. In Patent Document 2, it is possible to confirm and select whether to write in a schedule book for each mail.

  However, when a contact such as a meeting is received by a large number of mails, a plurality of candidate dates may be described in each mail. In that case, it is common to notify the schedule that can be attended as a reply to an email in which a plurality of candidate dates are described. If the attendance date is communicated to a large number of emails as described above, schedules may overlap. Since it is a tentative schedule at the time when the available schedule is notified, even if they overlap, there is no particular problem. However, when an e-mail is received, the meeting schedule is first determined, the meeting schedule described in the e-mail is recorded in the scheduler, and then another e-mail is received. If it is the same time as the schedule information of the mail, the problem is that the schedule already determined according to the first mail is duplicated.

  In order to solve the above problems, one embodiment of the present invention is a schedule management system including a processor and a storage device connected to the processor, the storage device adjusting an event schedule. One or more schedules extracted from each of the plurality of messages transmitted to the network holds schedule information registered as undetermined schedules corresponding to the identification information of each message, and the processor When receiving information for newly determining the undecided schedule, whether any of the undecided schedules corresponding to the message other than the message corresponding to the newly determined schedule overlap with the newly determined schedule And if any undecided schedule overlaps with the newly determined schedule, output information notifying the duplicated undecided schedule And wherein the Rukoto.

  According to one aspect of the present invention, schedule information is extracted from a plurality of messages, a temporary schedule is registered from the time at which each schedule can attend, and then a duplicate reservation is made even if the schedule is determined from the determined message. Without having to decide which message schedule information to attend.

It is a block diagram which shows the hardware constitutions of the personal computer which implement | achieves the schedule management system of embodiment of this invention. It is a functional block diagram at the time of performing a schedule process in the memory of PC of embodiment of this invention. It is explanatory drawing which shows an example of the keyword table which PC of embodiment of this invention hold | maintains. It is explanatory drawing of the example of a schedule at the time of temporary reservation in embodiment of this invention. It is explanatory drawing of the example of a schedule at the time of this reservation in embodiment of this invention. It is explanatory drawing of an example of the schedule information in the case of temporary reservation in embodiment of this invention. It is a flowchart of the message transmission process which PC of embodiment of this invention performs. It is a flowchart of the message creation process which PC of embodiment of this invention performs. It is a flowchart of the message analysis process which PC of embodiment of this invention performs. It is a flowchart of the message reception process which PC of embodiment of this invention performs. It is a flowchart of the message confirmation process which PC of embodiment of this invention performs. It is explanatory drawing of the example of the 1st message output when PC of embodiment of this invention produces a reply message. It is explanatory drawing of the 2nd example of a message output when PC of embodiment of this invention produces a reply message. It is explanatory drawing of the 1st example of a message output when the message which notifies the schedule determined by PC of embodiment of this invention is received. It is explanatory drawing of the example of a message which PC of embodiment of this invention transmits automatically in order to cancel the schedule which already returned that attendance was possible. It is explanatory drawing of the 2nd example of a message output when the message which notifies the schedule determined by PC of embodiment of this invention is received. It is explanatory drawing of the example of a message automatically transmitted in order to notify that PC of embodiment of this invention became unable to attend the determined schedule. It is explanatory drawing of the example of the pop-up which PC displays, when a schedule overlaps in embodiment of this invention.

  The above issues can be solved by memorizing the schedule for all messages and sending them as a message when attendance becomes impossible. However, it is impossible to remember where the schedule information was placed in all messages. Also, if the schedule information overlaps at the same time, it takes time to notify each message that it is impossible to attend.

  Therefore, the schedule management system according to the embodiment of the present invention checks that there is schedule information when replying to a message with schedule information, and saves a schedule that can be participated as a provisional schedule. After that, when a message with a fixed schedule is received, the fixed information described in the message is reflected in the scheduler, and the message for the same time schedule information stored in the temporary schedule is displayed at that time. It is only necessary to automatically reply that it has become impossible to participate.

  Hereinafter, a specific registration method will be described.

  In this embodiment, when schedules such as meetings are received, a message containing multiple candidate dates is received, a schedule that can be participated as a reply is entered, registered in a temporary schedule, and participation is not possible Therefore, it is possible to avoid overlapping schedules by automatically replying to a message that has become impossible to participate in synchronization with the temporary schedule.

  First, after receiving a message, the user checks the number of lines to be registered as a provisional schedule in the message when replying. The schedule management system checks the date information in the keyword table by comparing the number of checked lines with the keyword table in the message analysis unit. The temporary schedule reservation unit temporarily reserves date information in the keyword table. Here, a provisional reservation is a schedule in which one or more schedules that a user can attend are registered as schedule information among a plurality of schedule candidates, and on which schedule a meeting etc. will be held. It is not yet decided. Since the temporary schedule reservation unit makes a temporary reservation for each message to be returned, there is a possibility that the schedules of a plurality of meetings and the like overlap at this point. However, since no schedule has yet been decided at this point, there is no problem even if there is an overlap.

  Next, when a message notifying that the schedule has been determined is received, the user confirms the message and checks the number of lines to be registered in the scheduler as schedule information. After checking, the message analysis unit checks the date / time information in the keyword table and reflects it in the scheduler. At this time, among the schedule information registered as the temporary schedule, messages that have a temporary schedule other than the final decision are automatically transmitted to indicate that attendance at the meeting at this time is impossible.

  However, the meeting or the like may be determined at the same time as the time initially determined by another message. In that case, the message receiving unit receives the message, confirms it, and registers it in the scheduler. However, because the schedule information has already been written, it informs the screen that the schedule information is duplicated as a pop-up. . The user determines which of the overlapping schedules has the higher priority. If the priority of a later message is high, the scheduler schedule information is changed. When the schedule information of the scheduler is changed, the schedule management system automatically replies to the message having the schedule information that was originally scheduled that attendance has become impossible.

  DESCRIPTION OF EMBODIMENTS Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings as appropriate.

  FIG. 1 is a block diagram showing a hardware configuration of a personal computer (PC) 1 that implements a schedule management system according to an embodiment of the present invention.

  The PC 1 includes a CPU 10 (Central Processing Unit) responsible for various arithmetic processing, a memory 20 that passes and stores information processed by the CPU 10, a graphic board 30 that processes graphics and screen data, and displays them on a display. A hard disk 40 for storing the created data, an optical disk 50 for reproducing and recording an optical disk such as a CD (Compact Disc) or a DVD (Digital Versatile Disc), and a motherboard 60 on which the above parts are mounted are incorporated. Thus, the PC 1 has the same hardware as a general computer. The function of the schedule management system of the present embodiment is realized by the CPU 10 executing a program stored in the memory 20 of the PC 1. These will be described below.

  FIG. 2 is a functional block diagram when performing schedule processing in the memory 20 of the PC 1 according to the embodiment of this invention.

  The message creation unit 110, the message analysis unit 120, the temporary schedule reservation unit 140, the message transmission unit 150, the message reception unit 160, and the message confirmation unit 170 in FIG. 2 are realized by the CPU 10 executing a program stored in the memory 20. Function block. Therefore, in the following description, the processing executed by each of the above units is actually executed by the CPU 10 in accordance with an instruction described in the program.

  The received message folder 100 in the hard disk 40 stores the received message. When the user selects a message to be returned from the received message folder 100, the message creation unit 110 creates a message to be returned. At this time, if there is schedule information, the user checks the number of lines with the information. The message creation unit 110 sends the created message to the message analysis unit 120.

  The message analysis unit 120 compares the line checked by the user with the information in the keyword table 130, refers to the keyword table 130, extracts the time of the schedule information, and the temporary schedule reservation unit 140 temporarily reserves the schedule information. . At this time, if there are a plurality of time zones that can be attended in the provisional schedule, all of them are registered as provisional schedules, and after registration, the message transmission unit 150 transmits a message.

  The message reception unit 160 receives a message, and the message confirmation unit 170 confirms whether there is schedule information in the received message. If there is schedule information, the user checks the number of rows that contain the schedule information. The message confirmation unit 170 sends the confirmed message to the message analysis unit 120.

  The message analysis unit 120 compares the sent message with the keyword table 130, extracts schedule information, registers it in the scheduler 180, and sends the message to the received message folder 100.

  FIG. 3 is an explanatory diagram illustrating an example of the keyword table 130 held by the PC 1 according to the embodiment of this invention.

  The keyword table 130 is a table that is referred to in order to extract schedule information from a received message, and indicates date information 200 indicating a description format of a date included in the schedule information and a description format of a time included in the schedule information. Time information 210.

  For example, if the received message is for adjusting the schedule of a meeting related to a certain case, and one of the candidates for the schedule is “March 6, 2015”, the candidate is “2015”. "March 6th of the year" may be written, but the year in the year will be omitted as "March 6", and the month will be omitted as "6th" It may be described, or may be described as “2015/3/6” by omitting characters such as Japanese “year”. As described above, keywords of various possible description formats are held as the date information 200.

  Similarly, as a format for describing time, a format in which “hour” and “minute” are divided by “:”, a format in which “am” or “afternoon” is described, and a half hour is described in “half” The form to do is considered. For this reason, keywords of these various description formats are held as time information 210. However, the keyword described in FIG. 3 is an example, and is not limited to this.

  FIG. 4 is an explanatory diagram of a schedule example at the time of provisional reservation in the embodiment of the present invention.

  FIG. 4 shows an example in which the schedule extracted from the message a and the message b is provisionally reserved. Here, the message “a” and the message “b” are replies to a message for requesting schedule adjustment for different projects, respectively, and include information on the schedule that the user answered that he / she can attend. From these messages, all schedules for which the user answered that he / she can attend are extracted and temporarily reserved.

  In the schedule example (provisional reservation) 220 shown in FIG. 4, 1/6 to 16:00 on 3/6 are provisionally reserved based on the message a. 3/6 15:30 to 17:00 and 18:30 to 20:00 are provisionally reserved based on the message b. 3/7 13:30 to 14:30 are provisionally reserved based on the message a. 3/7 13:00 to 14:30 are provisionally reserved based on the message b.

  In this example, the temporary reservation from 16:00 to 17:00 on 3/6 based on message a overlaps with a part of the temporary reservation from 15:30 to 17:00 on 3/6 based on message b. Yes. In this case, the temporary reservation based on the message a received earlier is registered as “reservation 1”, and the temporary reservation based on the message b received later is registered as “reservation 2”. The same applies to the 3/7 temporary reservation duplication.

  FIG. 5 is an explanatory diagram of a schedule example at the time of the reservation in the embodiment of the present invention.

  In the schedule example (main reservation) 230 shown in FIG. 5 after the provisional reservation shown in FIG. 4 is made, the main reservation is made on the schedule from 15:30 to 17:00 on 3/6 based on the message b. It is an example when it is decided. 3/6 15:30 to 17:00 based on message b becomes a book reservation, 3/6 18:30 to 20:00 and 3/7 13:00 to 14 based on the same message b : 30 provisional reservation is no longer needed and will be deleted. On the other hand, in this example, the tentative reservation based on the message a still remains, and both may be determined as the main reservation, but the tentative reservation of 3/6 may overlap with the main reservation based on the message b. Therefore, information indicating that may be added (strikethrough in the example of FIG. 5).

  FIG. 6 is an explanatory diagram showing an example of the schedule information 240 at the time of provisional reservation in the embodiment of the present invention.

  The schedule information 240 is information stored in the memory 20 and includes a message ID 241 for identifying each message from which the schedule information is extracted, a message title 242 attached to each message, and a schedule included in the text of each message. The number of lines 243 for specifying the description location of the date, and date information 244 and time information 245 extracted from each description location (line) based on the keyword table 130 are included. The message ID 241 is numbered in association with the message title 242.

  FIG. 6 shows an example in which a plurality of schedules extracted from one message (message a) are registered in the schedule information 240. Actually, in addition to a plurality of messages (for example, a message to be described later in addition to the message a) b), one or a plurality of schedules extracted from each are registered in the schedule information 240. By registering each schedule in association with the identification information (for example, message ID 241) of the message from which it was extracted as described above, any two schedules included in the schedule information 240 are extracted from the same message. (That is, whether it is a schedule related to the same item).

  Although omitted in FIG. 6, the schedule information 240 may include information (for example, a destination mail address) indicating a transmission destination of each message.

  Next, a description will be given of a method for creating a temporary schedule when making a conference reservation so that the schedule does not overlap.

  FIG. 7 is a flowchart of message transmission processing executed by the PC 1 according to the embodiment of this invention.

  This process is executed when a time communication such as a meeting is received and the message is returned. After the process is started (step 300), a message to be returned is selected from the received messages stored in the received message folder 100 (step 310). This selection may be performed by the message creation unit 110 or the like according to an instruction input to the PC 1 by the user.

  Next, the message creation unit 110 performs a message creation process for checking a line including schedule information (step 320). Details of this processing will be described later with reference to FIG.

  Next, the message creation unit 110 sends a message to the message analysis unit 120, and the message analysis unit 120 performs a message analysis process for retrieving the schedule information 240 (step 330). Details of this processing will be described later with reference to FIG.

  The message analysis unit 120 sends the message and the schedule information 240 from the analysis process to the temporary schedule reservation unit 140 (step 340). The temporary schedule reservation unit 140 checks whether or not the schedule information 240 has been sent (step 350). If the schedule information is not sent, the schedule information 240 is not extracted in step 330, that is, the schedule to be provisionally reserved is not included in the created message, so that the provisional reservation is not created. The process proceeds to step 370. If the schedule information 240 has been sent, the temporary schedule reservation unit 140 creates a temporary reservation based on the schedule information 240 (step 360).

  After the creation of the provisional reservation is completed, the message transmission unit 150 sends a message (step 370), and the processing ends (step 380).

  FIG. 8 is a flowchart of message creation processing executed by the PC 1 according to the embodiment of this invention.

  After starting the processing (step 400), the message creation unit 110 selects a message to be returned from the received message folder 100 (step 410). If a message has already been selected in step 310, step 410 is omitted.

  Next, the message creation unit 110 displays the message selected in step 410 (step 420). Next, the message creation unit 110 creates a reply message (step 430). For example, the user may input an instruction to change the displayed message to the PC 1, and the message creation unit 110 may create a reply message by changing the displayed message according to the instruction.

  Next, the message creation unit 110 confirms whether or not the schedule information 240 is included in the reply message (step 440), and if there is the schedule information 240, checks the schedule check for the corresponding number of rows ( Step 450), if there is no schedule information 240 in the reply message, nothing is done and the process ends (Step 460). A specific example of the reply message to be created and a check for it will be described later with reference to FIG.

  FIG. 9 is a flowchart of message analysis processing executed by the PC 1 according to the embodiment of this invention.

  After the start of processing (step 500), the message analysis unit 120 confirms that the creation of the reply message by the message creation unit 110 is completed (step 510), and refers to the first line of the created reply message (step 500). 520). Next, the message analysis unit 120 confirms whether or not a check is input in the schedule check column of the row being referred to (step 530). Date information and time information are extracted from the line (step 540) and stored as schedule information 240 (step 550). Next, the message analysis unit 120 checks whether or not the line being referred to is the last line of the message (step 560). If it is not the last line, the next line is referenced (step 570). The following processing is executed. If the referenced line is the last line, the process is terminated (step 580).

  FIG. 10 is a flowchart of message reception processing executed by the PC 1 according to the embodiment of this invention.

  After the processing is started (step 600), the message receiving unit 160 stands by until the message is received (step 610). When the message receiving unit 160 receives the message, the message confirming unit 170 confirms the message (step 620). The message confirmation unit 170 confirms whether there is schedule information 240 in the message body and whether the schedule information 240 is the present decision. Details of this processing will be described later with reference to FIG.

  Thereafter, the message confirmation unit 170 sends a message to the message analysis unit 120 (step 630), and the message analysis unit 120 performs the message analysis process of FIG. 9 (step 640). In this case, step 510 is omitted, and the processing from step 520 onward is executed for the message sent from the message confirmation unit 170.

  After the message analysis, the message analysis unit 120 sends the message and the schedule information 240 to the temporary schedule reservation unit 140 (step 650). The temporary schedule reservation unit 140 confirms whether or not the schedule information 240 is included in the sent information (step 660), and if there is no schedule information 240, the received message folder 100 is treated as a general message. (Step 670), and the process is terminated (step 790).

  If the sent information includes the schedule information 240, the temporary schedule reservation unit 140 transmits an instruction to register the schedule information to the scheduler 180 (step 680). Next, the scheduler 180 checks whether or not a book reservation that overlaps with the schedule information instructed to be registered has already been registered (step 690).

  If a duplicate book reservation has already been registered, the temporary schedule reservation unit 140 outputs a message confirming which schedule is to be prioritized by pop-up, and the schedule that the user wants to prioritize over that message. Information for selecting registration information is input (step 700).

  The temporary schedule reservation unit 140 confirms whether or not there is a change from the currently registered reservation information based on the selected schedule (step 710). Specifically, if a schedule included in the already registered reservation information is selected, the reservation information is not changed, and if the schedule information to be registered is selected, the already registered schedule is canceled. Therefore, the reservation information is changed.

  When there is a change in the reservation information, the provisional schedule reservation unit 140 automatically notifies that it is impossible to attend the schedule before the change (that is, the book reservation that has already been registered) (step 720). After the automatic contact, the temporary schedule reservation unit 140 deletes unnecessary information by deleting the pre-change schedule (step 730). Thereafter, the provisional schedule reservation unit 140 registers the selected schedule as a new book reservation in the reservation information (step 735), and the schedule of the corresponding message that is a provisional reservation (that is, the same schedule as the selected schedule) Is deleted (step 740), the message is sent to the received message folder 100 (step 780), and the process is terminated (step 790).

  In step 690, if a duplicate main reservation is not registered in the scheduler 180, the temporary schedule reservation unit 140 determines the schedule of the corresponding message that is a temporary reservation (that is, another schedule of the same item as the schedule to be registered from now on). (Temporary reservation) is deleted (step 750), and it is confirmed whether or not the schedule to be registered overlaps with any of the temporary reservations of another case (step 760).

  If there are duplicate provisional reservations, the provisional schedule reservation unit 140 searches for the duplicate provisional reservation message ID 241 and indicates that the reservation has been buried in the corresponding message (that is, attend the meeting of the relevant case). A reply that cannot be made (step 770). If there is no overlapping temporary reservation, the temporary schedule reservation unit 140 sends the received message to the received message folder 100 without doing anything (step 780), and the process ends (step 790).

  If there is no change in the reservation information in step 710, the temporary schedule reservation unit 140 deletes the temporary reservation of the schedule that has not been selected and all the temporary reservations of the same case (step 715), and proceeds to step 780. In this case, the schedule sent in step 650 (that is, the newly determined schedule) is not registered as a final reservation in the end, but the fact that it is not possible to attend the schedule meeting or the like is the step when the overlapping main reservation is registered. Since notification has already been made at 770, there is no need to notify again at step 715.

  Note that the deletion of schedules in steps 715, 730, 740, and 750 is an example of a process for invalidating schedule reservations, and a method of adding information indicating that the schedule is invalidated in place of deletion. May be adopted.

  FIG. 11 is a flowchart of message confirmation processing executed by the PC 1 according to the embodiment of this invention.

  This process is executed by the message confirmation unit 170 in step 640 of the reception process in FIG. After the start of processing (step 800), the message receiving unit 160 waits until a message is received (step 810), and sends the message to the message confirmation unit 170 triggered by the reception of the message (step 820). If reception of the message is confirmed in step 610, step 810 is omitted.

  Next, the message confirmation unit 170 confirms whether or not the schedule information is included in the body of the received message (step 830), and if the schedule information is included, the user checks the schedule check column in the corresponding line. Input (step 840). If the schedule information is not included, the message confirmation unit 170 does not execute Step 840.

  Next, the message confirmation unit 170 determines whether or not the schedule information is a final reservation (step 850). If the main reservation is determined, the user confirms the final determination on the line in which the determined main reservation is described. A check is input to the flag (step 860), and the process ends (step 870).

  Hereinafter, an example of display data output when the PC 1 according to the embodiment of the present invention executes the above-described process will be described. These display data are output to a display device (not shown) via the graphic board 30.

  FIG. 12 is an explanatory diagram of a first message example output when the PC 1 according to the embodiment of the present invention creates a reply message.

  A reply message example 900 shown in FIG. 12 is an example of a reply message created and transmitted in the processes of FIGS. 7 to 9, and specifically, a message for requesting a schedule adjustment for a meeting with respect to a certain case (C case). It is an example of the message displayed when the message a which is a reply to is created. A subject 901, a sender 902, a recipient 903, a body 904, and the like included in the reply message example 900 are equivalent to a general message. The difference from a general message is that there are a row number 905, a check box 906 for schedule check, and a check box 907 for this decision flag.

  Line number 905 is attached to the text and contents. A check box 906 for schedule check is displayed corresponding to each line in the text. When the user (in this example, the sender AAA of the reply message) enters a check in a check box 906 corresponding to the line in which the schedule contents are described in the text (step 450), the message analysis unit 120 uses the line as a keyword. Schedule information is extracted in comparison with the table 130 (steps 530 to 550). The check box 907 for the final decision flag is used when the schedule information described in the message body is decided as the final reservation.

  In the example of FIG. 12, three candidate schedules 2015/3/6 16: 00-17: 00, 2015/3/7 10: 00-11 are included in the message for requesting the schedule adjustment for the meeting C received by the user. 00 and 2015/3/7 13: 30-14: 30 are described, of which the user is concerned about 2015/3/6 16: 00-17: 00 and 2015/3/7 13: 30-14: 30 The example of the reply message which answers that it can attend is shown. Since the schedule information that can be attended is described in the line number “7” and the line number “9”, the user checks the check box 906 for the schedule check of the line number “7” and the line number “9”. On the other hand, since it is not possible to participate in 2015/3/7 10: 00-11: 0, it is not necessary to register as a temporary schedule, so the check box of the schedule check of the line number “8” in which the schedule is described is displayed. Do not check.

  Next, as shown in FIG. 12, since there is a schedule check for two candidate days, the message analysis unit 120 compares the character strings of those lines with the keyword table 130, and sets the schedule information 240 as shown in FIG. Take out. At this time, the message analysis unit 120 assigns a message title 242 based on the message title 901 and assigns a message ID 241 corresponding to the message title 242 as “message a”.

  The temporary schedule reservation unit 140 creates a temporary schedule as shown in FIG. 4 based on the schedule information 240 of FIG. 6 (step 360). In this example, based on the message a, 2015/3/6 16: 00-17: 00 and 2015/3/7 13: 30-14: 30 are provisionally reserved.

  Since the line number 905, the check box 906, and the check box 907 are used to create a temporary reservation, the message transmission unit 150 creates a message a after the temporary schedule reservation unit 140 creates a temporary reservation. When transmitting (step 370), it may be deleted. The same applies to the example of FIG. 13 described later.

  FIG. 13 is an explanatory diagram of a second message example output when the PC 1 according to the embodiment of this invention creates a reply message.

  A reply message example 910 shown in FIG. 13 is an example of the reply message created and transmitted in the processes of FIGS. 7 to 9 as in the reply message example 900 shown in FIG. 12, but what is shown in FIG. It is an example of the message b which is a reply to the message which requests the schedule adjustment of the meeting regarding another case (E case).

  Similarly to the reply message example 900 of FIG. 12, the reply message example 910 of FIG. 13 includes a subject 911, a sender 912, a receiver 913, a body 914, a line number 915, a check box 916 for schedule check, and this determination. It includes a check box 917 for flags. Also for this reply message example 910, the same processing as in FIG. 12 is performed. In this example, all three schedules listed as candidates can be attended, so as shown in FIG. 4, 2015/3/6 15: 30-17: 00, 18: 30-20: 00, and 2015 / 3/7 13: 00-14: 30 is provisionally reserved.

  FIG. 14 is an explanatory diagram of a first message example that is output when the PC 1 according to the embodiment of the present invention receives a message that informs the determined schedule.

  The message example 920 shown in FIG. 14 is displayed when the PC 1 receives the message that informs that the schedule has been determined for the message b after sending the message a shown in FIG. 12 and the message b shown in FIG. This is an example of a message. The message example 920 of FIG. 14 also includes a subject 921, a sender 922, a receiver 923, a body 924, a line number 925, a check box 926 for schedule check, and a main determination flag, as in the examples of FIGS. The check box 927 is included.

  In this example, since the schedule information to be registered is included in the seventh line of the text 924, the user inputs a check in the check box 926 for the schedule check in that line, and this message is further determined by this message. Is checked, the check box 927 of the main decision flag on the seventh line is checked. In this example, since the schedule information of the message b is the main decision, the provisional reservation in FIG. 4 is changed as shown in FIG.

  Specifically, since 2015/3/6 15: 30-17: 00 will be the main reservation, attend the temporary reservation of 2015/3/6 16: 00-17: 00 based on the duplicate message a Information indicating that it is disabled is added, and a message indicating that attendance is disabled is automatically transmitted to the transmission destination of the message a (steps 760 and 770). In addition, the temporarily reserved schedules 2015/3/6 18: 30-20: 00 and 2015/3/7 13: 00-14: 30 other than the final decision of the message b are unnecessary and are deleted. (Step 750).

  FIG. 15 is an explanatory diagram of an example of a message that is automatically transmitted by the PC 1 according to the embodiment of the present invention to cancel a schedule that has already been returned as being available for attendance.

  Specifically, the message example 930 shown in FIG. 15 informs that the case C can be attended at 2015/3/6 16: 00-17: 00 and 2015/3/7 13: 30-14: 30. After the message “a” is transmitted, a message (FIG. 14) is notified that the schedule of 2015/3/6 15: 30-17: 00 has been determined for the E case. 3/6 16: 00-17: 00 automatically sent to notify that attendance is not possible (step 770). A message to be automatically replied to is selected based on the message ID of the schedule information 240.

  The message example 930 in FIG. 15 also includes a subject 931, a sender 932, a recipient 933, and a body 934, similar to the examples in FIGS. Although the content of the message body 934 is arbitrary, it includes at least the time when attendance is disabled, which is specified from the schedule information 240.

  FIG. 16 is an explanatory diagram of a second message example that is output when the PC 1 according to the embodiment of the present invention receives a message that informs the determined schedule.

  In the example message 940 shown in FIG. 16, after the PC 1 transmits the message a shown in FIG. 12 and the message b shown in FIG. 13, the message shown in FIG. 14 is received, and the schedule regarding the message b is determined. It is an example of the message displayed when it is received that the schedule regarding the message a is determined. In this example, as a result of the schedule relating to the message b being determined, one of the two schedules that can be attended to the message a is not allowed to attend, and a message (FIG. 15) notifying that is automatically transmitted. The date when the attendance was not possible was decided as the date of the event.

  The message example 940 of FIG. 16 also includes a subject 941, a sender 942, a receiver 943, a body 944, a line number 945, a check box 946 for schedule check, and a main determination flag, as in the examples of FIGS. Check box 947. In the example of FIG. 16, since the received message includes schedule information for notifying the determined schedule, in the message confirmation processing executed by the message confirmation unit 170, the user includes a line including the schedule information (in FIG. 16). In the example, a check is entered in the check box 946 for schedule check in the eighth line (steps 830 to 840), and since this is the final decision, a check is also entered in the check box 947 for the final decision flag ( Steps 850-860).

  Since the check box 946 for schedule check and the check box 947 for final determination flag are checked, the temporary schedule reservation unit 140 registers the extracted schedule information in the scheduler 180, but is described in the message body. Since the schedule overlaps with the schedule already reserved based on the message b (step 690: YES), a message (for example, pop-up) for determining which schedule is to be prioritized is output (step 700).

  If the user who referred to the pop-up determines that the schedule based on the message b that has already been reserved is higher than the schedule based on the newly determined message a and decides to attend the meeting of the matter of the message b, The result of the determination is input to the PC 1, and the temporary schedule reservation unit 140 deletes all the temporary schedules based on the message a accordingly (step 715).

  On the other hand, if the user determines that the schedule based on the message a has a higher priority than the schedule based on the message b that has already been reserved, and that he / she attends the meeting of the case of the message a, the user sets the result of the determination to the PC 1. The provisional schedule reservation unit 140 changes the information of the scheduler 180 according to the input (steps 730 to 740), and automatically transmits a message indicating that participation in the notified conference is impossible to the destination of the message b ( Step 720).

  FIG. 17 is an explanatory diagram of an example of a message that is automatically transmitted by the PC 1 according to the embodiment of this invention to notify that it is impossible to attend the determined schedule.

  A message example 950 shown in FIG. 17 is an example of the message transmitted in step 720 of the example described with reference to FIG. The message example 950 in FIG. 16 also includes a subject 951, a sender 952, a recipient 953, and a body text 954, as in the examples in FIGS. As a result, it is notified that the participation of the matter relating to the message b is not possible.

  In the above example, in steps 720 and 770 of FIG. 10, a message notifying attendance (for example, FIGS. 17 and 15 respectively) is automatically transmitted. This is information for the PC 1 to notify that the reservation is duplicated. This is an example of a method for outputting, and another method may be adopted. For example, in step 720 and 770, the PC 1 may notify the user by a method such as outputting a screen displaying that the reservation is duplicated. If the user refers to the notification and determines that it is necessary, the user may manually transmit a message similar to FIG.

  When the message is automatically transmitted in steps 720 and 770 of FIG. 10, the transmission destination is the same as the transmission destination of the message first extracted with the schedule for notifying attendance by each message. For example, when the message of FIG. 17 is transmitted in step 720, the transmission destination is the same as the transmission destination of the message b shown in FIG. When the message of FIG. 15 is transmitted in step 770, the transmission destination is the same as the transmission destination of the message a shown in FIG. When the message a and the message b are normal e-mails, the PC 1 may extract a transmission destination from a transmitted mail managed by software that has transmitted these e-mails. Alternatively, information specifying these transmission destinations may be included in the schedule information 240.

  FIG. 18 is an explanatory diagram of an example of a popup displayed by the PC 1 when schedules overlap in the embodiment of the present invention.

  Since the message title is associated with the message ID, the pop-up example 1000 displays the titles of the corresponding messages as information for identifying the duplicate schedules (in this example, “Date and time of meeting C case” and “E case By displaying a check box or a radio button and a confirmation button, the user is requested to confirm which is prioritized.

  In the above embodiment of the present invention, an example in which the schedule management system is used for schedule adjustment of a meeting (meeting) has been shown. However, the schedule management system of this embodiment is not limited to a meeting, and schedule adjustment of any type of event. Can be used for

  According to the embodiment of the present invention described above, the schedule is extracted from the message transmitted to notify the schedule that the user can participate in, and is stored in association with the identification information of the message from which the user extracted. Since this is a provisional reservation at this point, the user does not need to be aware of whether there is any overlap between schedules. The range is extracted by the user, and the schedule is extracted from the range according to a keyword set in advance, whereby the schedule is correctly extracted. After that, when the notification of the determined schedule is received, the duplicate reservation is prevented by notifying the schedule of the provisional reservation overlapping therewith. By automatically transmitting a notification that participation is not possible for overlapping schedules of provisional reservations, the user's trouble is saved. When a schedule that overlaps with a schedule that has already been determined is newly determined, duplicate reservation is prevented by giving the user an opportunity to select one. When a schedule that has already been determined is not selected, a user's trouble is saved by automatically transmitting a notification indicating that the schedule is not available for participation.

  In addition, this invention is not limited to above-described embodiment, Various modifications are included. For example, the above-described embodiment has been described in detail for easy understanding of the present invention, and is not necessarily limited to one having all the configurations described.

  Each of the above-described configurations, functions, processing units, processing means, and the like may be realized by hardware by designing a part or all of them with, for example, an integrated circuit. Further, each of the above-described configurations, functions, and the like may be realized by software by interpreting and executing a program that realizes each function by the processor. Information such as programs, tables, and files for realizing each function is stored in a non-volatile semiconductor memory, a hard disk drive, a storage device such as an SSD (Solid State Drive), or a computer-readable non-readable information such as an IC card, an SD card, or a DVD. It can be stored on a temporary data storage medium.

  Further, the control lines and information lines indicate what is considered necessary for the explanation, and not all the control lines and information lines on the product are necessarily shown. Actually, it may be considered that almost all the components are connected to each other.

1 PC
10 CPU
20 Memory 40 Hard disk 100 Received message folder 110 Message creation unit 120 Message analysis unit 130 Keyword table 140 Temporary schedule reservation unit 170 Message confirmation unit 180 Scheduler 200, 210 Keyword table 220 Schedule example (temporary reservation)
230 Schedule Example (Booking)
240 Schedule information 900, 910, 920, 930, 940, 950 Message example 1000 Example of duplicate schedule pop-up message

Claims (5)

A schedule management system comprising a processor and a storage device connected to the processor,
The storage device is a schedule in which one or more schedules extracted from each of a plurality of messages transmitted to adjust the schedule of an event are registered as undetermined schedules corresponding to the identification information of the respective messages. Keep information,
The processor is
If any information that newly determines the undecided schedule is received, any undecided schedule corresponding to the message other than the message corresponding to the newly determined schedule is the newly determined schedule. Determine if they overlap,
When any undecided schedule overlaps with the newly determined schedule, the schedule management system outputs information notifying the duplicated undecided schedule. The schedule management system according to claim 1,
Each message transmitted by the schedule management system is a message for notifying one or more schedules that the user can participate in among schedule candidates for each event,
When any of the undecided schedules overlaps with the newly determined schedule, the processor, when the message corresponding to the duplicated undecided schedule, participates in the overlapping undecided schedule. A schedule management system characterized by transmitting a notification that it has become impossible. The schedule management system according to claim 2,
The processor is
When receiving information specifying one of the one or more undecided schedules corresponding to any of the messages as a newly determined schedule, any message other than the message corresponding to the newly determined schedule Determining whether the already determined date corresponding to the message overlaps with the newly determined date,
If the already determined schedule overlaps with the newly determined schedule, output information for selecting one of the already determined schedule and the newly determined schedule,
When the newly determined schedule is selected, a notification that participation in the already determined schedule is not possible is transmitted to the destination of the message corresponding to the already determined schedule. And schedule management system. The schedule management system according to claim 3,
The processor is
If the already determined schedule does not overlap with the newly determined schedule, delete all other pending schedules corresponding to the same message as the newly determined schedule from the schedule information;
If the already determined schedule overlaps with the newly determined schedule and the newly determined schedule is selected, all other undecided corresponding to the same message as the newly determined schedule Delete the schedule and the already determined schedule from the schedule information,
If the already determined schedule overlaps with the newly determined schedule and the already determined schedule is selected, all other undecided corresponding to the same message as the newly determined schedule And a schedule management system, wherein the schedule and the newly determined schedule are deleted from the schedule information. The schedule management system according to claim 4,
The storage device holds keyword information for extracting a schedule,
When the processor is input with information specifying a range in the body of each message transmitted by the schedule management system, the processor extracts the one or more schedules from the specified range based on the keyword information. Then, the schedule management system is registered in the schedule information as an undetermined schedule corresponding to the identification information of each message.