JP6891765B2 - Schedule management program, schedule management method and schedule management device - Google Patents

Description

The present invention relates to a schedule management program, a schedule management method, and a schedule management device.

There is known a technique for associating and using the access history of the target person and the schedule information of the target person. The technology acquires history information of usage information used when a mobile terminal accesses an information providing site, latent segment information corresponding to the history information, and user's action schedule information. The technology acquires the user's explicit segment information based on the action schedule information, and determines the recommended content based on the latent segment information and the explicit segment information.

In addition, a technique is also known in which the action schedule of a target person such as an employee shown in the schedule information is matched with the actual action schedule of the target person as much as possible. The technique uses an action performance table that defines the destination of each employee's past business trip, the direction to the departure point of the destination, the means of transportation, and the time of action. When the technology periodically acquires the position information of the terminal device of each employee, the moving direction and the moving distance are determined based on the position information, and the direction information and the transportation name are acquired from these. The technology searches the action performance table using the direction information and the transportation name as search conditions, generates the estimated arrival place and the estimated arrival time based on the detected performance information, and updates the action schedule table.

Japanese Unexamined Patent Publication No. 2013-41343 Japanese Unexamined Patent Publication No. 2015-84199

By the way, there are cases where it is desired to specify whether the target person is in-house or out of the office, such as when he / she wants to have an in-house meeting. In this case, even if the target person plans to go out, it may not be possible to identify that the target person has a plan to go out because the schedule has not been updated. In addition, the method of describing the schedule differs depending on the target person, and it may not be possible to specify whether the schedule is out of the office or planned in-house. With the above technique, it is not estimated whether or not the user actually plans to go out.

One aspect is to provide a schedule management program, a schedule management method, and a schedule management device that can set an outing schedule of a target person.

In one embodiment, the schedule management program causes a computer to perform a process of detecting access to a website by referring to a storage unit that stores information about a website that the user may access before going out. In addition, the schedule management program causes the computer to execute a process of setting the schedule registered in the time zone after the access as going out among the schedules of the detected users who have accessed.

According to one aspect, the subject's outing schedule can be set.

FIG. 1 is a diagram showing an example of a schedule management system according to the first embodiment. FIG. 2 is a diagram showing an example of a log DB in the first embodiment. FIG. 3 is a diagram showing an example of the schedule DB in the first embodiment. FIG. 4 is a diagram showing an example of the site DB in the first embodiment. FIG. 5 is a diagram showing an example of the updated schedule DB in the first embodiment. FIG. 6 is a flowchart showing an example of the schedule management process in the first embodiment. FIG. 7 is a diagram showing an example of the schedule management system according to the second embodiment. FIG. 8 is a diagram showing an example of the site DB in the second embodiment. FIG. 9 is a diagram showing an example of the accuracy DB in the second embodiment. FIG. 10 is a diagram showing an example of the updated schedule DB in the second embodiment. FIG. 11 is a flowchart showing an example of the schedule management process in the second embodiment. FIG. 12 is a diagram showing an example of the schedule management system according to the third embodiment. FIG. 13 is a diagram showing an example of the scheduled update DB in the third embodiment. FIG. 14 is a diagram showing an example of the updated schedule DB in the third embodiment. FIG. 15 is a flowchart showing an example of the schedule management process in the third embodiment. FIG. 16 is a flowchart showing an example of the update monitoring process in the third embodiment. FIG. 17 is a diagram showing an example of the schedule management system according to the fourth embodiment. FIG. 18 is a diagram showing an example of the accuracy DB in the fourth embodiment. FIG. 19 is a diagram showing an example of the date and time range DB in the fourth embodiment. FIG. 20 is a diagram showing an example of the notification target DB in the fourth embodiment. FIG. 21 is an explanatory diagram showing an example of a computer that executes a schedule management program.

Hereinafter, examples of the schedule management program, the schedule management method, and the schedule management device disclosed in the present application will be described in detail with reference to the drawings. The present invention is not limited to this embodiment. In addition, the examples shown below may be appropriately combined as long as they do not cause a contradiction.

The schedule management method in the first embodiment is a method in which a user such as an employee manages a schedule registered in the scheduler. For example, in the schedule management method in the first embodiment, when it is detected that the user has accessed a timetable site, a route search site, etc. that are often accessed before a business trip, the user's schedule after the access is "going out". The computer executes the process of setting. This makes it easy to set an outing schedule.

[Functional block]
The schedule management method in the first embodiment is realized by the schedule management system 1 including the schedule management device 200 as shown in FIG. 1, for example. FIG. 1 is a diagram showing an example of a schedule management system according to the first embodiment. As shown in FIG. 1, the schedule management system 1 in the first embodiment includes a schedule management device 200, a proxy server 300, a scheduler 400, a user terminal 500, and external Web servers 600a to 600c. In the following, when the external Web servers 600a to 600c are expressed without distinction, they may be simply referred to as "external Web server 600".

The schedule management device 200 shown in FIG. 1 is communicably connected to, for example, the proxy server 300 and the scheduler 400 by wireless or wired communication. Further, the user terminal 500 shown in FIG. 1 is communicably connected to, for example, a proxy server 300 and a scheduler 400 via a wireless or wired network N1 such as an in-house LAN (Local Area Network). Then, the proxy server 300 is communicably connected to the external Web server 600 through a network N2 such as the Internet.

The proxy server 300 shown in FIG. 1 relays communication between the user terminal 500 and the external Web server 600. When the proxy server 300 receives an access request from, for example, the user terminal 500, the proxy server 300 acquires the information of the website from the external web server 600 via the network N2 and transmits the information to the user terminal 500. At that time, the proxy server 300 stores the access log of the user terminal 500 to the external Web server 600 in the log DB 321. In the following description, the database may be referred to as "DB".

FIG. 2 is a diagram showing an example of a log DB in the first embodiment. As shown in FIG. 2, the log DB 321 in the first embodiment stores the "time" and the "URL" in association with the "user ID". The information stored in the log DB 321 is input by the proxy server 300 when the user terminal 500 accesses the external Web server 600 via the proxy server 300.

In FIG. 2, the “user ID” indicates an identifier that uniquely identifies each user. Further, the "time" and the "URL" indicate the URL of the website provided by the external Web server 600 accessed by the user corresponding to the user ID, and the access time.

Returning to FIG. 1, the scheduler 400 manages the schedule of each user. The scheduler 400 stores, for example, a schedule input by the user through the user terminal 500 in the schedule DB 421.

FIG. 3 is a diagram showing an example of the schedule DB in the first embodiment. As shown in FIG. 3, the schedule DB 421 stores, for example, each item of "time" and "content" in association with "user ID". The information stored in the schedule DB 421 is registered by the scheduler 400 that receives the schedule input from the user terminal 500, and is updated by the setting unit 234 of the schedule management device 200, which will be described later.

In FIG. 3, "time" and "content" indicate the time and content scheduled to be registered by the user corresponding to the user ID. By the way, the format of the contents of the schedule is not limited, and even if the schedule has the same contents, the input method may differ depending on the user. In this case, as shown in FIG. 2, the content to be registered by the user does not include a specific place such as "meeting" or the place is "● Building". Even if it is described, it may be difficult to tell at first glance whether or not to go out.

Returning to FIG. 1, the schedule management device 200 in the first embodiment updates the information stored in the schedule DB 421 with reference to the log DB 321 and the schedule DB 421. The schedule management device 200 includes a communication unit 210, a storage unit 220, and a control unit 230.

The communication unit 210 controls communication with the proxy server 300, the scheduler 400, and other computers, regardless of whether they are wired or wireless. The communication unit 210 is, for example, a communication interface such as a NIC (Network Interface Card).

The storage unit 220 stores various data such as a program executed by the control unit 230, for example. The storage unit 220 corresponds to semiconductor memory elements such as RAM (Random Access Memory), ROM (Read Only Memory), and flash memory, and storage devices such as HDD (Hard Disk Drive). In addition, the storage unit 220 has a site DB 221.

The site DB 221 stores information about a website that the user often refers to before going out among the websites provided by the external web server 600. FIG. 4 is a diagram showing an example of the site DB in the first embodiment. As shown in FIG. 4, the site DB221 stores, for example, the "type" and the "URL" in association with the "site ID". The information stored in the site DB 221 is input in advance by, for example, the administrator of the schedule management device 200 (not shown). Further, in the following, a website that a user often refers to before going out may be referred to as a “target website”.

In FIG. 4, the "type" and "URL" store the type and URL of the target website. As shown in FIG. 4, the target website includes various sites related to going out, such as a "map" site, a "timetable" site, and a "transfer guidance" site.

Returning to FIG. 1, the control unit 230 is a processing unit that controls the overall processing of the schedule management device 200. The control unit 230 is realized by, for example, a CPU (Central Processing Unit), an MPU (Micro Processing Unit), or the like executing a program stored in an internal storage device using a RAM as a work area. Further, the control unit 230 may be realized by, for example, an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).

The control unit 230 has a log acquisition unit 231, a schedule acquisition unit 232, a determination unit 233, and a setting unit 234. The log acquisition unit 231, the schedule acquisition unit 232, the determination unit 233, and the setting unit 234 are examples of electronic circuits included in the processor and examples of processes executed by the processor.

The log acquisition unit 231 acquires the access log of the user to the website. The log acquisition unit 231 acquires the access log stored in the log DB 321 of the proxy server 300, for example, through the communication unit 210. The log acquisition unit 231 outputs the acquired access log to the determination unit 233. The log acquisition unit 231 is an example of a detection unit.

The schedule acquisition unit 232 acquires the schedule registered by the user. The schedule acquisition unit 232 acquires the schedule stored in the schedule DB 421 of the scheduler 400, for example, through the communication unit 210. The schedule acquisition unit 232 outputs the acquired schedule to the determination unit 233. The schedule acquisition unit 232 is an example of an acquisition unit.

The determination unit 233 determines whether or not the user's access log satisfies a predetermined condition. Upon receiving the input of the access log from the log acquisition unit 231, the determination unit 233 refers to the site DB 221 and determines whether or not the URL included in the access log corresponds to the URL of the target website. When the determination unit 233 determines that the URL corresponds to the target website, the determination unit 233 sets the determination result including the user ID and time included in the access log and the information indicating that the URL corresponds to the target website. Output to 234.

The determination unit 233 acquires the access log stored in the log DB 321 as shown in FIG. 2, for example. The determination unit 233 refers to the site DB 221 shown in FIG. 4 and determines that the access destination URL "map.example.co.jp" of the user ID "A" corresponds to the URL of the target website. On the other hand, in the determination unit 233, the access destination URL "news.example.co.jp" of the user ID "B" and the access destination URL "sports.example.co.jp" of the user ID "C" are the target websites. Judge that it does not correspond to the URL.

The setting unit 234 updates the user's schedule stored in the scheduler 400 based on the determination result by the determination unit 233. When the setting unit 234 receives the output of the determination result from the determination unit 233, the setting unit 234 refers to the schedule DB 421 of the scheduler 400 through the communication unit 210. Then, the setting unit 234 searches for the schedule of the user including the time after the time included in the determination result by using the user ID included in the determination result.

When the setting unit 234 determines that the schedule of the user including the time is registered in the schedule DB 421, the setting unit 234 updates the contents of the schedule. For example, when the determination result includes the user ID "A" and the schedule of the user "A" is registered in the schedule DB 421 after the time, the setting unit 234 sets the contents of the schedule to "going out schedule" or the like. , Update to indicate that you are out.

An example in which the scheduled contents of the user “A” are updated by the setting unit 234 will be described with reference to FIG. FIG. 5 is a diagram showing an example of the updated schedule DB in the first embodiment. As shown in FIG. 5, the setting unit 234 updates the content of the schedule that was “meeting” in FIG. 3 to the content 5011 indicating “planned to go out”. On the other hand, the setting unit 234 does not update the schedules of other users.

[Processing flow]
Next, the flow of processing in Example 1 will be described with reference to FIG. FIG. 6 is a flowchart showing an example of the schedule management process in the first embodiment. As shown in FIG. 6, the log acquisition unit 231 of the schedule management device 200 waits until, for example, the communication unit 210 receives an instruction to start the schedule management process from an administrator (not shown) (S100: No).

When the log acquisition unit 231 determines that the start instruction has been accepted (S100: Yes), the log acquisition unit 231 accesses the proxy server 300 through the communication unit 210, and determines whether or not there is an unacquired access log in the log DB 321 (S110). .. When the log acquisition unit 231 determines that there is no unacquired access log (S110: No), the log acquisition unit 231 waits until a new access log is recorded.

When the log acquisition unit 231 determines that there is an unacquired access log (S110: Yes), the log acquisition unit 231 acquires the access log from the proxy server 300 and outputs the access log to the determination unit 233. The determination unit 233 refers to the site DB 221 and determines whether or not the access destination is the target site, that is, whether or not the URL included in the access log corresponds to the URL of the target website (S120).

When the determination unit 233 determines that the access destination is not the target site (S120: No), the determination unit 233 returns to S110 and repeats the process. On the other hand, when the determination unit 233 determines that the access destination is the target site (S120: Yes), the determination unit 233 requests the schedule acquisition unit 232 to acquire the schedule corresponding to the user ID included in the access log.

The schedule acquisition unit 232 accesses the scheduler 400 through the communication unit 210, acquires information on the schedule corresponding to the user ID, and outputs the information to the determination unit 233 (S121). The determination unit 233 determines whether or not the user has a schedule after the time included in the access log (S130). When the determination unit 233 determines that the user has no schedule (S130: No), the determination unit 233 returns to S110 and repeats the process.

When the determination unit 233 determines that the user has a schedule (S130: Yes), the determination unit 233 outputs the determination result to the setting unit 234. The setting unit 234 sets the content of the user's schedule to "scheduled to go out" (S180).

After that, the log acquisition unit 231 returns to S110 and repeats the process until it receives an instruction to end the schedule management process from an administrator (not shown) (S190: No). When the log acquisition unit 231 determines that the end instruction has been accepted (S190: Yes), the log acquisition unit 231 ends the process.

[effect]
As described above, the schedule management program in the first embodiment refers to a storage unit that stores information about a website that the user may access before going out, and performs a process of detecting access to the website. Let the computer do it. In addition, the schedule management program causes the computer to execute a process of setting the schedule registered in the time zone after the access as going out among the schedules of the detected users who have accessed. This makes it possible to set the outing schedule of the target person.

For example, when another user wishes to have an interview with a specific user, he / she refers to the schedule of the specific user. However, if the location is not described in the schedule registered in the schedule or the location is unclear, it cannot be specified whether or not the specific user is planning to go out. In this case, it is difficult for other users to determine whether they can meet with a specific user. According to the first embodiment, whether or not the user is going out is set based on the access log of the user, so that the user's going out schedule can be set without depending on the registered contents of the schedule by the user. ..

By the way, in the first embodiment, a map site, a timetable site, and a transfer guidance site are illustrated as the target websites, but the possibility that the user goes out when accessing may differ depending on the target websites. For example, a user accessing a map site may be more likely to go out than a user accessing a transfer information site. Therefore, in the second embodiment, an "accuracy" indicating the possibility of the user going out is set for each target website, and when the user's schedule is updated, the accuracy of the target website accessed by the user is further stored. The configuration will be described.

[Functional block]
The schedule management method in the second embodiment is realized by the schedule management system 2 including the schedule management device 700 as shown in FIG. 7, for example. FIG. 7 is a diagram showing an example of the schedule management system according to the second embodiment. In the following examples, the same parts as those shown in the drawings described above are designated by the same reference numerals, and duplicate description will be omitted.

As shown in FIG. 7, the schedule management device 700 in the second embodiment has a communication unit 210, a storage unit 720, and a control unit 730.

The storage unit 720 stores various data such as a program executed by the control unit 730, for example. The storage unit 720 corresponds to semiconductor memory elements such as RAM, ROM, and flash memory, and storage devices such as HDD. In addition, the storage unit 720 has a site DB721 and an accuracy DB722.

The site DB721 in the second embodiment stores information about the target website in association with the "accuracy" of the website. FIG. 8 is a diagram showing an example of the site DB in the second embodiment. As shown in FIG. 8, the site DB721 stores, for example, "accuracy" 7010 in association with "site ID" in addition to "type" and "URL". The information stored in the site DB 721 is input in advance by, for example, the administrator of the schedule management device 700 (not shown).

As shown in FIG. 8, the site DB721 stores "accuracy" that differs for each site in association with the site ID. For example, the accuracy of the URL having the site ID "0001" and the type "map" is "100", and the accuracy of the URL having the site ID "0002" and the type "timetable" is "80". ..

Next, the accuracy DB 722 in the second embodiment stores the "accuracy" of each current user. FIG. 9 is a diagram showing an example of the accuracy DB in the second embodiment. As shown in FIG. 9, the accuracy DB 722 stores the “current accuracy” in association with the “user ID”. The information stored in the accuracy DB 722 is input by, for example, the setting unit 734 described later.

In the second embodiment, the accuracy DB 722 stores "0" as the initial value of the accuracy of each user, for example. For example, when the determination unit 733 described later determines that the user "A" has accessed the target website having an accuracy of "100", "100" is input to the "current accuracy" of the accuracy DB 722.

Returning to FIG. 7, the control unit 730 is a processing unit that controls the overall processing of the schedule management device 700. The control unit 730 is realized by, for example, a CPU, an MPU, or the like executing a program stored in an internal storage device using the RAM as a work area. Further, the control unit 730 may be realized by an integrated circuit such as an ASIC or FPGA.

The control unit 730 has a log acquisition unit 231, a schedule acquisition unit 232, a determination unit 733, and a setting unit 734. The determination unit 733 and the setting unit 734 are also examples of electronic circuits included in the processor and examples of processes executed by the processor.

The determination unit 733 further determines whether or not the URL included in the user's access log satisfies a predetermined condition, and whether or not the accuracy included in the access log satisfies a predetermined condition. When the determination unit 733 determines that the URL corresponds to the target website, the determination unit 733 refers to the site DB721 and acquires the accuracy of the access destination target site. Further, the determination unit 733 refers to the accuracy DB 722 and acquires the current accuracy of the corresponding user.

Then, the determination unit 733 is the target of the access destination when the current accuracy of the corresponding user is "0", that is, when the user's schedule is not updated to "going out schedule" by the setting unit 734 described later. The determination result including the accuracy of the site is output to the setting unit 734.

Further, when the current accuracy of the corresponding user is not "0", that is, when the user's schedule has already been updated to "going out scheduled" by the setting unit 734, the determination unit 733 of the access destination target site. Further determine if the accuracy is greater than the current accuracy of the user. When the accuracy of the target site of the access destination is larger than the current accuracy of the corresponding user, the determination unit 733 outputs the determination result including the accuracy of the target site of the access destination to the setting unit 734.

The determination unit 733 acquires the access log stored in the log DB 321 as shown in FIG. 2, for example. The determination unit 733 refers to the site DB721 shown in FIG. 8 and acquires the accuracy "100" of the access destination URL "map.example.co.jp" of the user ID "A". Further, the determination unit 733 refers to the accuracy DB 722 shown in FIG. 9 and acquires the current accuracy “80” of the user ID “A”. In this case, since the accuracy "100" of the access destination target site is larger than the current accuracy "80" of the corresponding user, the determination unit 733 sends the determination result including the accuracy of the access destination target site to the setting unit 734. Output.

Further, when the determination unit 733 determines, for example, that the access destination URL of the user ID "B" is "timetable.example.co.jp", the determination unit 733 refers to the site DB721 shown in FIG. 8 and determines the accuracy of the target website. Get "80". Further, the determination unit 733 refers to the accuracy DB 722 shown in FIG. 9 and acquires the current accuracy “0” of the user ID “B”. In this case, since the current accuracy of the corresponding user is "0", the determination unit 733 outputs the determination result including the accuracy of the target site of the access destination to the setting unit 734.

On the other hand, when the determination unit 733 determines, for example, that the access destination URL of the user ID "C" is "transit.example.co.jp", the determination unit 733 refers to the site DB721 shown in FIG. Get "60". Further, the determination unit 733 refers to the accuracy DB 722 shown in FIG. 9 and acquires the current accuracy “60” of the user ID “C”. In this case, the determination unit 733 does not output the determination result to the setting unit 734 because the accuracy "60" of the access destination target site is equal to or less than the current accuracy "60" of the corresponding user.

The setting unit 734 updates the user's schedule stored in the scheduler 400 based on the determination result including the accuracy of the target website. When the setting unit 734 receives the output of the determination result from the determination unit 733, the setting unit 734 refers to the schedule DB 421 of the scheduler 400 through the communication unit 210. Then, the setting unit 734 searches the schedule of the user including the time after the time included in the determination result by using the user ID included in the determination result.

When the setting unit 734 determines that the schedule of the user including the time is registered in the schedule DB 421, the setting unit 734 updates the contents of the schedule. For example, when the schedule of the corresponding user is registered in the schedule DB 421 after the time, the setting unit 734 determines that the schedule is out of the office, such as "planned to go out (accuracy 100)", and the accuracy. Update to the content shown.

An example in which the schedule content of the user “A” is updated by the setting unit 734 will be described with reference to FIG. FIG. 10 is a diagram showing an example of the updated schedule DB in the second embodiment. As shown in FIG. 10, the setting unit 734 updates the content of the schedule to the content 5211 indicating the accuracy in addition to the schedule to go out, such as “Scheduled to go out (accuracy 100)”.

[Processing flow]
Next, the flow of processing in Example 2 will be described. FIG. 11 is a flowchart showing an example of the schedule management process in the second embodiment. In the following description, since the same steps as those shown in FIG. 6 are the same steps, detailed description thereof will be omitted.

When the determination unit 733 determines that the user has a schedule (S130: Yes), the determination unit 733 refers to the site DB721 and acquires the accuracy of the target site to be accessed (S140). Further, the determination unit 733 refers to the accuracy DB 722 and acquires the current accuracy of the user (S141).

Then, the determination unit 733 determines whether or not the current accuracy of the user is "0" (S150). When the determination unit 733 determines that the current accuracy of the user is "0" (S150: Yes), the determination unit 733 outputs a determination result including the accuracy of the access destination target site to the setting unit 734. The setting unit 734 sets the content of the user's schedule stored in the schedule DB 421 to "scheduled to go out" and sets the accuracy of the target site to be accessed (S181).

On the other hand, when the determination unit 733 determines that the current accuracy of the user is not "0" (S150: No), whether or not the accuracy of the target site to be accessed is greater than the current accuracy of the user. Is further determined (S160). When the determination unit 733 determines that the accuracy of the access destination target site is equal to or less than the current accuracy of the user (S160: No), the determination unit 733 shifts to S190.

On the other hand, when the determination unit 733 determines that the accuracy of the access destination target site is larger than the current accuracy of the user (S160: Yes), the determination unit 733 sets the determination result including the accuracy of the access destination target site to the setting unit 734. Output. The setting unit 734 updates the accuracy set in the schedule content of the user stored in the schedule DB 421 with the accuracy of the target site of the access destination (S161), and shifts to S190.

[effect]
As described above, the schedule management program in the second embodiment causes the computer to perform a process of further storing the accuracy indicating the high degree of association between the website and going out. In addition, the schedule management program causes the computer to execute a process of further associating the accuracy of the website where the access is detected with the schedule set to go out. This makes it possible to set an outing schedule that includes an accuracy indicating the possibility that the user will go out.

Further, when the schedule management program determines that the accuracy of the website is higher than the accuracy associated with the schedule, the schedule management program may further cause the computer to execute a process of updating the accuracy associated with the schedule. Good. As a result, even when the user's outing schedule has already been set, it is possible to set a more accurate outing schedule.

By the way, even when the outing schedule is set by the schedule management process in each of the above embodiments, the user's schedule may not actually be accompanied by going out. For example, when a user frequently accesses the target website but actually has few opportunities to go out, the outing schedule set by the schedule management process may be further updated by the user.

Further, when the set outing schedule is often further updated by the user, it is highly possible that the user is not actually going out even if the outing schedule is set. That is, it is assumed that the reliability of the set outing schedule is low for the user.

Therefore, in the third embodiment, a configuration for detecting the re-update for the set out-of-home schedule and a configuration for setting the reliability of the out-of-home schedule according to the detected re-update will be described.

[Functional block]
The schedule management method in the third embodiment is realized by the schedule management system 3 including the schedule management device 800 as shown in FIG. 12, for example. FIG. 12 is a diagram showing an example of the schedule management system according to the third embodiment. As shown in FIG. 12, the schedule management device 800 in the third embodiment has a communication unit 210, a storage unit 820, and a control unit 830.

The storage unit 820 stores various data such as a program executed by the control unit 830, for example. The storage unit 820 corresponds to semiconductor memory elements such as RAM, ROM, and flash memory, and storage devices such as HDD. In addition, the storage unit 820 has a site DB 221 and a schedule update DB 823.

The schedule update DB 823 in the third embodiment stores information regarding re-update for the outing schedule set in the schedule management process. FIG. 13 is a diagram showing an example of the scheduled update DB in the third embodiment. As shown in FIG. 13, the scheduled update DB 823 stores, for example, the “set count” and the “update count” in association with the “user ID”. The information stored in the schedule update DB 823 is input by, for example, the schedule acquisition unit 832 and the setting unit 834, which will be described later.

In FIG. 13, the “set number of times” indicates the number of times that “going out scheduled” is set by the schedule management process for the user's schedule. The "update count" indicates the number of times the set "going out schedule" schedule has been re-updated.

Next, the control unit 830 is a processing unit that controls the overall processing of the schedule management device 800. The control unit 830 is realized by, for example, a CPU, an MPU, or the like executing a program stored in an internal storage device using the RAM as a work area. Further, the control unit 830 may be realized by an integrated circuit such as an ASIC or FPGA.

The control unit 830 has a log acquisition unit 231, a schedule acquisition unit 832, a determination unit 833, and a setting unit 834. The schedule acquisition unit 832, the determination unit 833, and the setting unit 834 are also examples of electronic circuits included in the processor and examples of processes executed by the processor.

The schedule acquisition unit 832 acquires the schedule registered by the user and detects that the schedule of "going out schedule" has been re-updated. The schedule acquisition unit 832 is an example of an acquisition unit.

The schedule acquisition unit 832 acquires the schedule stored in the schedule DB 421 of the scheduler 400, for example, through the communication unit 210. The schedule acquisition unit 832 determines whether or not the schedule for which "scheduled to go out" is set during the day has been updated among the acquired schedules. When the schedule acquisition unit 832 determines that the schedule for which "going out schedule" is set has been updated, the schedule acquisition unit 832 increments the update count of the corresponding user stored in the schedule update DB 823 by one.

Next, the determination unit 833 further determines whether or not the URL included in the user's access log satisfies a predetermined condition, and whether or not the number of times the user's schedule is set and the number of updates satisfies the predetermined condition. To do.

When the determination unit 833 determines that the URL of the target website corresponds to the URL of the target website and the user has a schedule, the determination unit 833 refers to the schedule update DB 823 and acquires the set number of times and the update number of the corresponding user. Then, the determination unit 833 determines whether or not, for example, the ratio of the update count to the set count is equal to or higher than a predetermined threshold value (50% or the like). In the following, the ratio of the user's update count to the set count may be referred to as "update ratio".

The determination unit 833 includes information indicating that the reliability is low when the update rate is equal to or higher than a predetermined threshold value, that is, when the set "scheduled going out" schedule is re-updated frequently. Is output to the setting unit 834.

The determination unit 833 identifies, for example, in the scheduled update DB 823 shown in FIG. 13, that the update rate of the user ID "A" is "60/100 = 60%". In this case, if the predetermined threshold value is 50%, the determination unit 833 determines that the update rate is equal to or higher than the predetermined threshold value. Therefore, the user ID "A" includes information indicating that the reliability is low. The determination result is output to the setting unit 834.

Further, the determination unit 833 specifies that the update rate of the user ID "B" is "80/200 = 40%". That is, although the number of updates of the user ID "B" exceeds the number of updates of the user ID "A", the update rate is less than a predetermined threshold value. In this case, the determination unit 833 outputs to the setting unit 834 a determination result that does not include information on the reliability of the user ID “B”. Similarly, the determination unit 833 outputs a determination result that does not include information on the reliability to the setting unit 834 even for the user ID “C” whose update rate is less than a predetermined threshold value.

The setting unit 834 further sets information on reliability when setting a user's schedule stored in the scheduler 400. When the setting unit 834 receives the output of the determination result including the information indicating that the reliability is low from the determination unit 833, the setting unit 834 registers the outing schedule indicating that the reliability is low in the schedule DB 421. On the other hand, when the setting unit 834 receives the output of the determination result that does not include the information about the reliability from the determination unit 833, the setting unit 834 registers the outing schedule that does not include the information about the reliability in the schedule DB 421. Further, the setting unit 834 increments the set number of the corresponding user stored in the schedule update DB 823 by 1 when receiving the output of the determination result regardless of whether or not the information regarding the reliability is included.

An example in which the contents of the schedule are updated by the setting unit 834 will be described with reference to FIG. FIG. 14 is a diagram showing an example of the updated schedule DB in the third embodiment. As shown in FIG. 14, the setting unit 834 sets the outing schedule 5311 indicating that the reliability is low for the user ID “A” that has received the output of the determination result including the information indicating that the reliability is low. On the other hand, when the setting unit 834 receives the output of the determination result that does not include the information about the reliability for the user ID "D", for example, the setting unit 834 sets the outing schedule 5312 that does not include the information about the reliability.

[Processing flow]
Next, the processing in this embodiment will be described with reference to FIGS. 15 and 16. FIG. 15 is a flowchart showing an example of the schedule management process in the third embodiment. In the following description, since the same steps as those shown in FIG. 6 are the same steps, detailed description thereof will be omitted.

When the determination unit 833 determines that the user has a schedule (S130: Yes), the determination unit 833 refers to the schedule update DB 823 and acquires the set number of times and the update number of the corresponding user. Then, the determination unit 833 calculates the update rate of the corresponding user, and determines whether or not the update rate is equal to or higher than a predetermined threshold value (for example, 50%) (S170).

When the determination unit 833 determines that the update rate is equal to or higher than a predetermined threshold value (S170: Yes), the determination unit 833 outputs a determination result indicating that the reliability is low to the setting unit 834. The setting unit 834 sets the contents of the user's schedule stored in the schedule DB 421 to "going out schedule (low reliability)" (S180), and shifts to S188.

On the other hand, when the determination unit 833 determines that the update rate is less than a predetermined threshold value (S170: No), the determination unit 833 outputs a determination result that does not include information on the reliability to the setting unit 834. The setting unit 834 sets the contents of the user's schedule stored in the schedule DB 421 to "scheduled to go out" (S171), and shifts to S188.

Next, the setting unit 834 increments the number of updates of the corresponding user stored in the scheduled update DB 823 by 1 (S188). Then, the schedule acquisition unit 832 starts the update monitoring process (S189) and shifts to S190.

FIG. 16 is a flowchart showing an example of the update monitoring process in the third embodiment. First, the schedule acquisition unit 832 acquires the schedule stored in the schedule DB 421 of the scheduler 400 (S201). Next, the schedule acquisition unit 832 searches for a schedule set as "scheduled to go out" and determines whether or not the schedule has been re-updated (S210).

When the schedule acquisition unit 832 determines that the schedule set as "going out schedule" has been re-updated (S210: Yes), the schedule acquisition unit 832 increments the number of updates corresponding to the user stored in the schedule update DB 823 by one (S210: Yes). S211). After that, it shifts to S220.

On the other hand, when the schedule acquisition unit 832 determines that the schedule set as "going out schedule" has not been re-updated (S210: No), it returns to S210 and repeats the process until the date changes (S220: No). .. When the date changes (S220: Yes), the schedule acquisition unit 832 ends the process.

[effect]
As described above, the schedule management program in the third embodiment causes the computer to execute a process of acquiring information indicating that the schedule set as going out has been updated by the user. Further, in the schedule management program in the third embodiment, when the relationship between the total number of schedules set for going out and the number of updated schedules satisfies a predetermined condition, the reliability of the schedules set for going out is low. Have the computer execute the process of further setting the information indicating. As a result, it is possible to set a schedule including the reliability of the outing schedule according to the schedule update by the user.

By the way, the timing at which the user accesses the target website differs depending on the outing schedule. For example, if the user accesses the map site in the morning, it is estimated that the user will go out in the afternoon, but if the user accesses the transfer information site just before the closing time, the user will go out the next day. It is estimated to be.

In addition, when a user's outing schedule is set, the user or another user who wants to confirm the user's schedule may want to know that the outing schedule has been set.

Therefore, in the fourth embodiment, a configuration for setting an outing schedule and a configuration for notifying the user that the outing schedule has been set will be described in the time zone corresponding to the access to the target website by the user.

[Functional block]
The schedule management method in the fourth embodiment is realized by the schedule management system 4 including the schedule management device 900 as shown in FIG. 17, for example. FIG. 17 is a diagram showing an example of the schedule management system according to the fourth embodiment. In the following examples, the same parts as those shown in the drawings described above are designated by the same reference numerals, and duplicate description will be omitted.

The storage unit 920 stores various data such as a program executed by the control unit 930, for example. The storage unit 920 corresponds to semiconductor memory elements such as RAM, ROM, and flash memory, and storage devices such as HDD. Further, the storage unit 920 has a site DB 721, an accuracy DB 922, a date and time range DB 924, and a notification target DB 925.

The accuracy DB 922 in the fourth embodiment stores the "accuracy" of each user separately as "accuracy of the current day" and "accuracy of the next day". FIG. 18 is a diagram showing an example of the accuracy DB in the fourth embodiment. As shown in FIG. 18, the accuracy DB 922 stores the “accuracy of the current day” and the “accuracy of the next day” in association with the “user ID”. The information stored in the accuracy DB 922 is input by, for example, the setting unit 934 described later.

As shown in FIG. 18, the accuracy DB 922 stores, for example, that the user with the user ID “C” is scheduled to go out with the accuracy “60” on the day. On the other hand, the accuracy DB 922 stores that the accuracy of the user "C" on the next day is "0", that is, the user "C" is not scheduled to go out on the next day.

The date / time range DB 924 in the fourth embodiment stores the time included in the access log and the search range of the target date / time for which the outing schedule is set in association with each other. FIG. 19 is a diagram showing an example of the date and time range DB in the fourth embodiment. The information stored in the accuracy DB 922 is input by, for example, the setting unit 934 described later. The information stored in the date and time range DB 924 is input in advance by, for example, the administrator of the schedule management device 900 (not shown).

As shown in FIG. 19, when the time included in the access log is "until 15:00", the date and time range DB 924 stores that the schedule after that time on the day is the target for setting the outing schedule. To do. Similarly, when the time included in the access log is "after 15:00", the date and time range DB 924 stores that the schedule for the next business day is the target for setting the outing schedule.

The notification target DB 925 in the fourth embodiment stores information about a user who is a target for notifying that an outing schedule has been set. FIG. 20 is a diagram showing an example of the notification target DB in the fourth embodiment. As shown in FIG. 20, the notification target DB 925 stores the “notification destination user ID” in association with the “target user ID”. The information stored in the notification target DB 925 is input in advance by, for example, the administrator of the schedule management device 900.

In FIG. 20, the “target user ID” indicates the user ID of the target user for which the outing schedule is set. The "notification destination user ID" stores the user ID of the target user to be notified when the outing schedule is set in the schedule of the user of the target user ID. The user ID of the notification destination may include, for example, a "target user ID", or may be a user ID of another user who wants to confirm the schedule of the user. Further, instead of the user ID, the e-mail address of the notification destination or the like may be stored.

Next, the control unit 930 is a processing unit that controls the overall processing of the schedule management device 900. The control unit 930 is realized by, for example, a CPU, an MPU, or the like executing a program stored in an internal storage device using the RAM as a work area. Further, the control unit 930 may be realized by an integrated circuit such as an ASIC or FPGA.

The control unit 930 has a log acquisition unit 231, a schedule acquisition unit 232, a determination unit 933, a setting unit 934, and a notification unit 935. The determination unit 933, the setting unit 934, and the notification unit 935 are also examples of electronic circuits included in the processor and examples of processes executed by the processor.

The determination unit 933 further determines whether or not the time included in the access log satisfies the predetermined condition, in addition to whether or not the URL included in the user's access log satisfies the predetermined condition.

When the determination unit 933 determines that it corresponds to the URL of the target website, it refers to the date and time range DB 924 and specifies the search range corresponding to the time included in the access log. Then, the determination unit 933 determines whether or not the schedule of the user is registered in the specified search range. When the schedule of the user is registered in the specified search range, the determination unit 933 outputs a determination result including information for designating the schedule of the user to the setting unit 934.

When the determination unit 933 determines that the time included in the access log to the target website is "14:00" and the schedule of the user is registered after "14:00" on the current day, the determination unit 933 determines that the schedule of the user is registered. , Outputs the judgment result including the information that specifies the schedule of the user on the day. Further, when the determination unit 933 determines that the schedule of the user is registered on the next day when the time included in the access log is "16:00", the determination unit 933 specifies the schedule of the user on the next day. Output the judgment result including information.

The setting unit 934 sets the outing schedule for the schedule specified in the determination result output from the determination unit 933. In addition, the setting unit 934 notifies the notification unit 935 that the outing schedule has been set.

The notification unit 935 notifies the user terminal 500 of the designated user that the outing schedule has been set by the setting unit 934 through the communication unit 210. For example, when the outing schedule is set in the schedule of the user with the user ID "A", the notification unit 935 notifies the users with the user IDs "A" and "B" that the outing schedule has been set.

[effect]
As described above, the schedule management program in the fourth embodiment goes out of the schedule of the user registered in the time zone corresponding to the predetermined condition when the time when the website is accessed satisfies the predetermined condition. Let the computer execute the process to set. As a result, it is possible to set an outing schedule according to the time when the user accesses the target website.

In addition, since the schedule management program causes the computer to execute a process of notifying a user other than the user of information about the schedule set to go out, it is possible to notify the other user of the setting of the schedule to go out.

By the way, although the examples of the present invention have been described so far, the present invention may be implemented in various different forms other than the above-mentioned examples. For example, the number of each device shown in FIG. 1 is an example, and may be configured to include two or more user terminals 500 and four or more external Web servers 600.

Further, in the first embodiment, the information included in the access log acquired by the log acquisition unit 231 from the proxy server 300 is an example, and may include, for example, the information input by the user terminal 500 and transmitted to the website. Further, although the log acquisition unit 231 has shown an example of acquiring only the domain name as the URL, the present invention is not limited to this, and the URL of the entire page may be acquired if possible. Further, the log acquisition unit 231 may use the IP address or MAC address of the user terminal 500 instead of the "user ID" when identifying the access source user terminal 500.

Further, the log acquisition unit 231 may acquire the access log from the user terminal 500 instead of accessing the proxy server 300. For example, the log acquisition unit 231 may acquire the access log transmitted from the user terminal 500 by using the access log investigation program installed in the user terminal 500.

Further, in the configuration using the accuracy of the target website stored in the site DB721 shown in FIG. 8 in the second embodiment, it is conceivable that the user accesses a plurality of target websites such as a timetable site and a transfer guidance site. .. In this case, the schedule management program may further cause the computer to perform a process of setting the highest accuracy among the accuracy of the plurality of websites in association with the schedule set as going out.

For example, when the determination unit 733 determines that the user with the user ID "A" has accessed the timetable site "timetable.example.co.jp" and the transfer guidance site "transit.example.co.jp", FIG. The accuracy of each site is extracted with reference to the site DB721 shown in. As shown in FIG. 8, the accuracy of the timetable site is "80", and the accuracy of the transfer guidance site is "60". In this case, the determination unit 733 refers to the accuracy DB 722 shown in FIG. 9 and compares the higher accuracy "80" with the accuracy of the user ID "A".

In this way, the schedule management program, for example, when it is detected that a user has accessed a plurality of websites, associates the highest accuracy among the accuracy of the plurality of websites with the schedule set as going out. You may let the computer execute the process to be set. This makes it possible to set a more accurate outing schedule.

Further, when the user accesses a plurality of websites, the schedule management program may cause the computer to execute, for example, a process of adding up the accuracy of all the websites. In addition, the schedule management program may calculate the average value of other accuracy excluding the one with the highest accuracy and the one with the lowest accuracy.

Further, the user may refer to the target website even when he / she does not plan to go out or regardless of his / her plan to go out. For example, a user may refer to a map site when selecting a store to hold a welcome and farewell party after the closing time, or a timetable site to check the train time when returning home.

In such a case, the user may also access a site other than the target website, such as a restaurant reservation site. Therefore, the site DB 721 of the schedule management device 700 may further store websites other than the target website in association with the accuracy of a negative value. Further, when the schedule management program determines that the user has accessed a website having a negative value, the schedule management program uses the accuracy of the negative value to determine the "current accuracy" of the accuracy DB 722 shown in FIG. You may let the computer execute the process of updating.

For example, site DB721 may further store records relating to restaurant search sites with an accuracy of "-20". In this case, when the user accesses the timetable site "timetable.example.co.jp" with an accuracy of "80" and the restaurant search site, the determination unit 733 determines that the accuracy of the timetable site is "80". Add up the accuracy "-20" of the restaurant search site. Then, the determination unit 733 refers to the accuracy DB 722 shown in FIG. 9 and compares the total accuracy “60” with the accuracy of the user. The setting unit 734 may add the accuracy "-20" of the restaurant search site to the "current accuracy" of the accuracy DB 722 shown in FIG.

As described above, the schedule management program in the second embodiment may cause the computer to execute the process of updating the accuracy associated with the schedule when the accuracy of the website where the access is detected is a negative value. This makes it possible to set the accuracy that reflects the low possibility of going out.

The accuracy stored in the site DB 721 shown in FIG. 8 may be uniformly determined for each "type" of the site, or may be determined even for sites of the same "type" or at different angles.

Further, in the configuration for determining the reliability of going out using the update rate in the third embodiment, the determination unit 833 may determine the reliability by using the number of updates instead of the update rate. For example, the determination unit 833 may output a determination result including information indicating that the reliability is low for a user whose update count is "70" or more to the setting unit 834.

For example, in the scheduled update DB 823 shown in FIG. 13, the "update count" of the user ID "A" is "60" times, and the "update count" of the user ID "B" is "80" times. In this case, the determination unit 833 outputs a determination result including information indicating that the reliability is low for the user ID "B", but does not include information on the reliability for the user ID "A". Output.

Further, although the configuration for outputting the determination result including the information indicating that the reliability is low has been described, the embodiment is not limited to this. For example, the determination unit 833 may output a determination result including "information indicating that the reliability is high" when the "update rate" or the "update count" is less than a predetermined threshold value.

Further, in the configuration of the fourth embodiment in which the date and time range is changed according to the timing of access to the target website, the timing of the user accessing the target website may differ depending on the user. Therefore, the date and time range DB 924 as shown in FIG. 19 may be prepared individually for each user. Further, the search range of the date and time range DB 924 may be changed for a user having a low reliability by combining the configuration for determining the reliability of the scheduled going out in the third embodiment.

[system]
Further, among the processes described in each embodiment, a part of the processes described as being automatically performed can also be performed manually. Alternatively, all or part of the processing described as being performed manually can be automatically performed by a known method. In addition, the processing procedure, control procedure, specific name, and information including various data and parameters shown in the above document and drawings can be arbitrarily changed unless otherwise specified.

Further, each component of each of the illustrated devices is a functional concept, and does not necessarily have to be physically configured as shown in the figure. That is, the specific forms of distribution and integration of each device are not limited to those shown in the figure. That is, all or a part thereof can be functionally or physically distributed / integrated in any unit according to various loads, usage conditions, and the like. For example, the determination unit 233 and the setting unit 234 shown in FIG. 1 may be integrated. Further, each processing function performed by each device may be realized by a CPU and a program analyzed and executed by the CPU, or may be realized as hardware by wired logic.

Further, the various processing functions performed by the schedule management device 200 may execute all or any part thereof on a CPU or a microcomputer such as an MPU or an MCU (Micro Controller Unit). Further, various processing functions may be executed in whole or in any part on a program analyzed and executed by a CPU (or a microcomputer such as an MPU or MCU) or on hardware by wired logic. Needless to say.

By the way, various processes described in this embodiment can be realized by executing a program prepared in advance on a computer. Therefore, an example of a computer that executes a program having the same function as that of the above embodiment will be described below. FIG. 21 is an explanatory diagram showing an example of a computer that executes a schedule management program. In the following, the schedule management device 200 in the first embodiment will be described as an example, but the schedule management devices 700, 800, and 900 in the second to fourth embodiments can also be realized by the same computer.

The computer 100 that executes the schedule management program in FIG. 21 includes a communication unit 110, a secondary storage device 120, a memory 130, a CPU 140, and a bus 150.

Then, the secondary storage device 120 stores in advance a schedule management program that exhibits the same functions as those in the above embodiment. The processing program may be recorded on a recording medium that can be read by a drive (not shown) instead of the secondary storage device 120. The recording medium may be, for example, a portable recording medium such as a CD-ROM, a DVD, a USB memory, an SD card, or a semiconductor memory such as a flash memory. The processing programs include a log acquisition program 120A, a schedule acquisition program 120B, a determination program 120C, and a setting program 120D. The log acquisition program 120A, the schedule acquisition program 120B, the determination program 120C, and the setting program 120D may be integrated or distributed as appropriate. Further, the computer 100 may acquire and execute the delivery destination setting program from these portable physical media. Further, the delivery destination setting program is stored in another computer or the like connected to the computer 100 via a public line, the Internet, LAN, WAN, or the like, and the computer 100 acquires and executes the delivery destination setting program from these. You may do so.

Then, the CPU 140 reads the log acquisition program 120A, the schedule acquisition program 120B, the determination program 120C, and the setting program 120D from the secondary storage device 120, and expands each of these read programs on the memory 130. The CPU 140 causes the log acquisition program 120A, the schedule acquisition program 120B, the determination program 120C, and the setting program 120D to function as the log acquisition process 130A, the schedule acquisition process 130B, the determination process 130C, and the setting process 130D on the memory 130. In the CPU 140, not all the processing units shown in this embodiment need to operate, and it is sufficient that the processing units corresponding to the processes to be executed are virtually realized.

The following additional notes will be further disclosed with respect to the embodiments including each of the above embodiments.

(Appendix 1) To the computer
By referring to a storage unit that stores information about a website that the user may access before going out, the access to the website is detected.
A schedule management program that executes a process of setting a schedule registered in a time zone after the access as going out among the schedules of the users who have made the detected access.

(Appendix 2) The storage unit further stores the accuracy indicating the high degree of association between the website and going out.
The schedule management program according to Appendix 1, wherein the process to be set is set by further associating the accuracy of the website on which the access is detected with the schedule set to go out.

(Appendix 3) In the process to be set, when it is detected that the user has accessed a plurality of the websites, the highest accuracy among the plurality of websites is scheduled to be set as going out. The schedule management program according to Appendix 2, wherein the schedule management program is set in association with each other.

(Appendix 4) The process to be set is characterized in that when it is determined that the accuracy of the website is higher than the accuracy associated with the schedule, the accuracy associated with the schedule is updated. The schedule management program described in Appendix 2 or 3.

(Appendix 5) The process to be set is any of Appendix 2 to 4, characterized in that the accuracy associated with the schedule is updated when the accuracy of the website on which the access is detected is a negative value. The schedule management program described in one.

(Appendix 6) In the process to be set, when the time when the website is accessed satisfies a predetermined condition, the schedule of the user registered in the time zone corresponding to the predetermined condition is set as going out. The schedule management program according to any one of Supplementary note 1 to 5, wherein the schedule management program is described.

(Appendix 7) The user further causes the computer to execute a process of acquiring information indicating that the schedule set as going out has been updated.
The process to be set indicates that the reliability of the outing and the set schedule is low when the relationship between the total number of the outing and the set schedule and the number of the updated schedule satisfies a predetermined condition. The schedule management program according to any one of Supplementary notes 1 to 6, wherein the information is further set.

(Appendix 8) When the ratio of the number of updated schedules to the total number of schedules set as going out is equal to or greater than a predetermined threshold value, the computer is further subjected to a process of determining that the relationship satisfies a predetermined condition. The schedule management program according to Appendix 7, which is characterized in that it is executed.

(Appendix 9) The schedule according to any one of the appendices 1 to 8, wherein the computer further executes a process of notifying a user other than the user of information about the schedule set as going out. Management program.

(Appendix 10) The computer
By referring to a storage unit that stores information about a website that the user may access before going out, the access to the website is detected.
A schedule management method for performing a process of setting a schedule registered in a time zone after the access as going out among the schedules of the users who have made the detected access.

(Appendix 11) A storage unit that stores information about websites that the user may access before going out,
A detector that detects access to the website and
Of the schedules of the users who made the detected access, the setting unit that sets the schedule registered in the time zone after the access as going out, and the setting unit.
A schedule management device characterized by having.

1, 2, 3, 4 Schedule management system 200, 700, 800, 900 Schedule management device 210 Communication unit 220, 720, 820, 920 Storage unit 221, 721 Site DB
722, 922 Accuracy DB
823 Scheduled update DB
924 Date and time range DB
925 Notification target DB
230, 730, 830, 930 Control unit 231 Log acquisition unit 232, 832 Schedule acquisition unit 233, 733, 833, 933 Judgment unit 234, 734, 834, 934 Setting unit 935 Notification unit 300 Proxy server 321 Log DB
400 Scheduler 421 Schedule DB
500 User terminals 600a to 600c External Web server N1, N2 network

Claims (8)

On the computer
By referring to a storage unit that stores information about a website that the user may access before going out, the access to the website is detected.
A schedule management program that executes a process of setting a schedule registered in a time zone after the access as going out among the schedules of the users who have made the detected access. The storage unit further stores the accuracy indicating the high degree of association between the website and going out.
The schedule management program according to claim 1, wherein the process to be set is set by further associating the accuracy of the website on which the access is detected with the schedule set to go out. When it is detected that the user has accessed a plurality of the websites, the setting process sets the highest accuracy among the plurality of websites in association with the schedule set as going out. The schedule management program according to claim 2, wherein the schedule management program is performed. The process of setting is characterized in that, when it is determined that the accuracy of the website is higher than the accuracy associated with the schedule, the accuracy associated with the schedule is updated. Schedule management program according to 2 or 3. The process of setting is characterized in that, when the time when the website is accessed satisfies a predetermined condition, the schedule of the user registered in the time zone corresponding to the predetermined condition is set as going out. The schedule management program according to any one of claims 1 to 4. The user further causes the computer to execute a process of acquiring information indicating that the schedule set as going out has been updated.
The process to be set indicates that the reliability of the outing and the set schedule is low when the relationship between the total number of the outing and the set schedule and the number of the updated schedule satisfies a predetermined condition. The schedule management program according to any one of claims 1 to 5, wherein the information is further set. The computer
By referring to a storage unit that stores information about a website that the user may access before going out, the access to the website is detected.
A schedule management method for performing a process of setting a schedule registered in a time zone after the access as going out among the schedules of the users who have made the detected access. A storage unit that stores information about websites that users may access before going out,
A detector that detects access to the website and
Of the schedules of the users who made the detected access, the setting unit that sets the schedule registered in the time zone after the access as going out, and the setting unit.
A schedule management device characterized by having.

Images