JP2017208022A - Schedule estimation method based on presence history - Google Patents

Abstract

PROBLEM TO BE SOLVED: To estimate a future schedule of a user even in a state in which past schedule information on the user is not stored in a database.SOLUTION: When a schedule information management server 1 receives a schedule automatic generation request command from user terminals 2-1 to 2-N, it analyzes past presence history information, extracts periodic presence history information, tentatively registers a future estimation schedule estimated on the basis of an event corresponding to the extracted periodic presence history information, and determines/modifies/deletes the tentatively-registered future estimation schedule in response to a reception command from a notification destination.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a method for estimating a future schedule of a user based on the user's past presence history information.

  In order to input the schedule information to the information device, it is necessary to input the date and time, the place, the business, etc. one by one, which is troublesome for busy businessmen.

  As a technology for supporting the input of this schedule information, in the schedule management server that manages the user's schedule information, the user's past schedule information accumulated in the database is analyzed, and the future of the user is analyzed based on the subject name and the occurrence frequency. There is a technique for predicting a schedule (for example, Patent Document 1). As a result, a regular schedule such as a regular meeting can be predicted with relatively high accuracy, so that the user only has to confirm or correct the predicted schedule, and the labor for inputting and registering schedule information is considerably reduced. Is done.

  However, the technique described in Patent Literature 1 is based on the premise that a huge amount of past schedule information for each user is accumulated in the database, and the user is required to repeat a regular schedule at least several times. In the meantime, it is necessary to register each schedule information with the schedule management server each time.

JP 2012-27840 A

  Therefore, an object of the present invention is to provide a method for estimating a future schedule of a user even when the user's past schedule information is not accumulated in a database.

  In order to solve the above problems, the present invention is based on past presence history information relating to a place or a past state of one or more users, and a part of the future schedule of the users. A method for estimating presence information registration step for registering predetermined presence information and business information related to the business in association with each other; presence history information collecting step for collecting the presence history information from a predetermined information source; A periodic presence history extracting step for analyzing the collected presence history information and extracting periodic presence history information, and extracting the periodic presence history information when the periodic presence history information is extracted. Based on the periodicity and the business information corresponding to the extracted presence history information, a part of the future schedule of the user is estimated. Characterized in that it.

  According to the present invention, since a future schedule is estimated based on past presence history data of each user, it is not necessary that past schedule information of the user is registered in the schedule management server. In addition, each user's presence data can be automatically stored in the presence management server based on various sensors that sense location and status, such as entrance / exit sensors and communication history data. Work is unnecessary or minor.

  In addition, the estimated future schedule is notified to the user or the secretary of the user, and the estimated future schedule is confirmed or corrected, thereby supporting the individual schedule registration to the schedule management server. Is possible.

It is the internal block block diagram and whole block diagram of the apparatus to which this invention is applied. It is an example of the presence history information and business information which estimate a schedule. It is an operation | movement flowchart of the apparatus to which this invention is applied.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is an internal block configuration diagram and an overall configuration diagram of an apparatus to which the present invention is applied. 1 is a schedule information management server (hereinafter abbreviated as the present apparatus) to which the present invention is applied, and 2 is a personal computer or a smart phone. 3 is a presence information management server that accumulates and manages each user's current presence information and past presence history information, and 4 is a LAN (Local Area Network) or WAN (Wide Area Network).

  Upon receiving a schedule registration support request command from any of the user terminals 2, the apparatus 1 refers to the user's past presence history information from the presence information management server 3, and estimates future schedule information of the user. To the user terminal 2. A user who has confirmed the estimated future schedule information can register his / her future schedule in the apparatus 1 simply by confirming, correcting, or deleting the estimated schedule information.

  Next, the internal block configuration of the apparatus 1 will be described. The apparatus 1 includes a control processing unit 10, a communication control unit 11, a user information registration unit 12, a presence / business correspondence registration unit 13, a calendar 14, and a schedule information storage unit 15.

  The control processing unit 10 is a unit that controls each unit of the apparatus 1 and executes various types of information processing (periodicity detection, holiday handling, user authentication, and the like). Details of the operation flow of the control processing unit 10 will be described later.

  The communication control unit 11 is means for executing communication with the user terminals 2-1 to 2-N and the presence information management server 3 via the LAN / WAN. Relay information between them.

  The user information registration unit 12 is means for registering information (ID, password, profile, etc.) relating to each user who uses the user terminal 2-1 to the user terminal 2-N.

  The presence / business correspondence registration unit 13 is a means for registering a correspondence relationship between presence information related to a place or state and business information related to a schedule. For example, if the place is a conference room, the XX conference is registered as the business information.

  The calendar 14 is means for presenting the control processing unit 10 with calendar information including irregular holidays such as holidays and company anniversary.

  The schedule information storage unit 15 is a unit that stores schedule information received from the user terminal 2 and unconfirmed schedule information estimated by the control processing unit 10 for each user.

  FIG. 2 is an example of presence history information and business information for estimating a schedule, FIG. 2A is an example of presence history information of month X stored in the presence information management server 3, and FIG. It is an example of the business corresponding to the presence information registered in the business case registration unit 13.

  In FIG. 2A, column 200 is the date, column 201 is the time zone, and column 202 is the presence history information. Information such as holidays in the column 200 is acquired from the calendar 14. The presence history information in column 202 indicates location information that existed at the date and time of each row. In FIG. 2B, column 210 is presence information, and column 211 is business information.

  Hereinafter, a method for estimating a regular schedule for each week will be described with reference to FIGS. 2A and 2B. First, each piece of information in FIG. 2A is analyzed, and a row in which the day of the week in column 202, the time zone in column 201, and the presence history information in column 202 match is extracted. In the example of FIG. 2A, (1) the presence history information of every day on every Monday is a business trip to the head office, (2) the presence history information of 9:00 to 10:00 on every Tuesday is the D meeting room, 3) Periodic presence history information indicating that the presence history information from 15:00 to 16:00 every Friday is the A conference room is extracted.

  Then, according to FIG. 2B, the extracted periodic presence history information is (1) a progress report at the head office, (2) a video conference in the D conference room, and (3) in the A conference room. It is understood that this is a progress meeting. That is, a regular schedule can be estimated from the periodic presence history information, and a part of the future schedule of the user of the user terminal 2 can be estimated. Examples of regular schedules of (1) to (3) are, for example, a progress meeting on the weekend ((3)), a business trip to the head office with the results ((1)), and instructions from the head office. This corresponds to the case where the video conference <(2)> with the related department is repeated based on the above.

  By the way, there may be holidays other than weekly holidays (for example, Saturdays and Sundays) such as holidays and unique anniversaries within the week. In the example of FIG. 2A, X month 11 (month, holiday) is a holiday, and the schedule for the next few days fluctuates. In the example of FIG. 2A, it can be seen that the progress report at the head office in (1) is shifted to the next day, and the video conference in the D meeting room in (2) is also shifted to the next day. Thus, even if there is a holiday or the like within the week, it is possible to estimate the future schedule (partial) of the user of the user terminal 2 in consideration of it.

  In the example of FIG. 2A, presence history information for one month is illustrated, but if presence history information for several months or more is analyzed, a regular schedule for each day of the week or a holiday within the week It is possible to estimate the schedule change rule when there is a high accuracy. In addition, if long-term presence history information is analyzed, it is possible to predict a regular schedule with a long period of month or year.

  FIG. 3 is an operation flowchart of the apparatus 1. Hereinafter, the operation flow of the apparatus 1 will be described with reference to FIGS. This flow starts with the power turned on (S300).

  In the standby state, the present apparatus 1 circulates each NO in S310, S340, S350, and S360 and waits for the occurrence of each event.

  In S310, when a schedule automatic generation request command is received from any user terminal 2 (S310, YES), the control processing unit 10 stores the past schedule corresponding to the requesting user stored in the schedule information storage unit 15. The history information is analyzed, a regular schedule is extracted, and a change rule for holidays is estimated (S311), and the process proceeds to S320.

  If regular schedule information can be extracted in S320 (S320, YES), a future estimated schedule estimated based on the extracted regular schedule information is provisionally registered in the schedule information storage unit 15, and the estimated schedule is notified. (Sending request or secretary's terminal, etc.), requesting confirmation / correction (S321), and proceeding to S330.

  In addition, the method of extracting the regular schedule information based on the past schedule history information and estimating the future estimated schedule is the same as the estimation method in Patent Document 1, and the past schedule history information is accumulated. Then, it is because it is more reasonable to estimate based on those schedule history information with a track record. However, the feature of the present invention lies in the processing after S322 described later, and a future estimated schedule can be estimated even in the state where past schedule history information is not accumulated.

  If regular schedule information cannot be extracted in S320 (S320, NO), the control processing unit 10 accesses the presence information management server 3 to collect and analyze past presence history information corresponding to the requesting user. Then, the periodic presence history information is extracted, and the fluctuation rule for holidays etc. is estimated (S322), and the process proceeds to S323. In addition, the estimation method of the change rule with respect to a holiday etc. is as having demonstrated FIG. 2A.

  In S323, the periodic presence history information can be extracted (S323, YES), and if the presence history information is registered in the presence / business correspondence registration unit 13 (S324, YES), the extracted periodic presence history is recorded. A future estimated schedule estimated based on the business information corresponding to the information (see FIG. 2B) is provisionally registered in the schedule information storage unit 15, and the estimated schedule is notified to a notification destination (requester or secretary's terminal). Send, request confirmation / correction (S325), and proceed to S330. If NO in S323 or S324, a request that the schedule cannot be estimated is transmitted to the request source (user terminal 2 that has transmitted the automatic schedule generation request command) (S326), and the process returns to S310.

  In S330, when a cancel command is received from the estimated schedule notification destination (S330, YES), the future estimated schedule temporarily registered in the schedule information storage unit 15 is deleted (S331), and the process returns to S310. If NO in S330, the process proceeds to S332.

  In S332, when a confirmation or correction command is received from the notification destination of the estimated schedule (S332, YES), the future estimated schedule provisionally registered in the schedule information storage unit 15 is confirmed or corrected and registered (S333). Return to S310. If NO in S330, the process proceeds to S334.

  In S334, if timeout (for example, 5 minutes) has not occurred (S334, NO), the process returns to S330. If the time-out has occurred (S334, YES), a message indicating that the estimated schedule is temporarily registered in the schedule information storage unit 15 is transmitted to the request source (S327), and the process returns to S310. Note that the estimated schedule that has been temporarily registered can be registered (confirmed), deleted, and modified by threads S340 and S350 described later.

  In S340, when a schedule information registration / deletion request command is received from any user terminal 2 (S340, YES), the control processing unit 10 determines a future estimated schedule temporarily registered in the schedule information storage unit 15 according to the request. Register as a confirmed schedule or delete the schedule (S341), and return to S310.

  In S350, when a schedule information correction request command is received from any of the user terminals 2 (S350, YES), the control processing unit 10 selects a future schedule temporarily registered or confirmed in the schedule information storage unit 15 according to the request. The corresponding requirement information registered in the presence / business correspondence registration unit 13 is also corrected (S351), and the process returns to S310.

  The registered requirement information is corrected when the schedule requirement to be corrected is corrected, and the registered requirement information is not corrected when the schedule is corrected. As a result, even if the regular schedule is changed, the registration contents of the presence / business correspondence registration unit 13 can be automatically updated by changing the schedule once. In addition, whenever this function is actively used and regular presence history information is extracted, the business information corresponding to the presence may be registered in the presence / business correspondence registration unit 13 (see FIG. Not shown).

  In S360, when a schedule information transmission request command is received from any of the user terminals 2 (S360, YES), the control processing unit 10 registers in the request source user terminal 2 in the schedule information storage unit 15 according to the received request. Alternatively, the temporarily registered desired future schedule information is transmitted (S361), and the process returns to S310. The user who has received future schedule information in S361 checks the contents and, if there is correction or deletion, sends the schedule information registration / deletion request command or schedule information correction request command described in S340 and S350 to the apparatus 1. Send.

  By the way, although the place which existed in the past was demonstrated as an example as presence history information, you may make it analyze the periodicity of presence history information other than a place. For example, by simply analyzing presence history information related to presence / absence at the user's own seat, it is possible to extract a periodic absence period and estimate a certain regular schedule (the requirement is unknown).

  The embodiment of the present invention has been described above. According to the present invention, when receiving an automatic schedule generation request command from any user terminal 2, the apparatus 1 analyzes past presence history information and extracts periodic presence history information. A future estimated schedule estimated based on the requirements corresponding to the periodic presence history information can be temporarily registered.

  In addition, when extracting periodic presence history information, if there are holidays or unique anniversaries (closed days) in the calendar information, refer to the presence history information of the days before and after that and change rules for holidays etc. Can be used to estimate future schedules.

  In addition, the device 1 transmits a provisionally registered future estimation schedule to a notification destination (person, secretary, etc.), requests to confirm / correct the estimated schedule, and receives a confirmation / deletion / correction command from the notification destination. Then, the estimated schedule that has been provisionally registered can be confirmed / corrected and can be registered or deleted.

  That is, since the future schedule is estimated based on the past presence data of each user, the regular schedule can be estimated even when the user's past schedule information is not registered in the schedule management server. In addition, each user's presence data can be automatically stored in the presence management server based on various sensors that sense the location and state, such as entrance / exit sensors and communication history data. Registration work is unnecessary or insignificant.

  Note that, as an embodiment, a system in which the schedule information management server 1, the user terminal 2, and the presence information management server 3 are separated has been described as an example, but the present invention is not limited to this. For example, as a device to which the present invention is applied, for example, a personal computer or a smart phone in which all of the functions of the schedule information management server 1, the functions of the user terminal 2, and the functions of the presence information management server 3 are integrated. Also good.

DESCRIPTION OF SYMBOLS 1 ... Schedule information management server 2 ... User terminal 3 ... Presence information management server 4 ... LAN / WAN
DESCRIPTION OF SYMBOLS 10 ... Control processing part 11 ... Communication control part 12 ... User information registration part 13 ... Presence / business correspondence registration part 14 ... Calendar 15 ... Schedule information storage part

Claims (2)

A method for estimating a part of a future schedule of a user based on past presence history information relating to a place or a past state of one or more users,
Presence information registration step for registering predetermined presence information and related business information in association with each other, presence history information collecting step for collecting the presence history information from a predetermined information source, and the collected presence history information And a periodic presence history extraction step for extracting periodic presence history information by analyzing
When the presence history information with periodicity is extracted, a part of the future schedule of the user is estimated based on the extracted periodicity and business information corresponding to the extracted presence history information. A schedule estimation method based on a characteristic presence history. The method of claim 1, wherein
When the information related to the estimated future schedule is notified to a predetermined notification destination and the information for correcting the business information of the estimated schedule is received from the notification destination, the presence is determined based on the received information. A schedule estimation method based on a presence history, wherein the business information registered in the business registration step is corrected.

Images