Notification control system and notification control method

Abstract

To notify at an appropriate time to encourage a user to take action to achieve their goal.SOLUTION: A method includes the steps of: using behavioral history data obtained from the user's behavioral history information, which includes user's actions to achieve a user's goal and is managed together with the user's goal, to create behavioral schedule data that estimates a user's schedule of actions; calculating a schedule addition score that indicates the degree of ease of adding a new schedule for the schedule contained in the behavioral schedule data on the basis of whether the situation in which the addition of a new schedule is recommended or whether the additional option satisfies predetermined conditions; calculating a notification score that indicates the degree of ease of success of the notification on the basis of whether the user's response when receiving a notification about a schedule contained in the schedule data meets the predetermined conditions; and controlling the timing of notifying the user to achieve the goal on the basis of the schedule addition score and the notification score.SELECTED DRAWING: Figure 1A

Description

[Technical field]

[0001] The present invention relates to a notification control system and a notification control method. [Background technology]

[0002] Traditionally, when asking someone to take a specific action, it has been considered effective to provide information in a timely manner at a time when it is easiest for them to take that action.

[0003] WO2020 / 049839 is a background art of this technical field. In paragraph 0032 of this publication, it is stated that "when the current user's operation status satisfies a predetermined notification condition, such as when the target operation has not been performed for a certain period of time, the notification unit 18 notifies the user to perform the target operation. In this embodiment, the notification unit 18 notifies at the execution timing or a candidate timing detected by the timing detection unit 17. Note that, when there are multiple such timings in one cycle, the notification unit 18 may notify all the times until the user shows a reaction, that is, each time the timing is detected." [Prior art documents] [Patent documents]

[0004] [Patent Document 1] WO2020 / 049839 publication Summary of the Invention [Problem to be solved by the invention]

[0005] In Patent Document 1, the system only prompts the user to perform a specific action if the target action has not been performed within a certain period of time, and does not control notifications to achieve a target amount (8000 steps, 2 hours) for the action, such as walking 8000 steps or spending 2 hours at the gym. Also, in order to get the user to perform a target amount of action within such a certain period of time, it is often necessary to review the user's schedule, and it would be effective to propose a specific schedule for performing the action, but Patent Document 1 does not address this.

[0006] The present invention aims to provide a technique capable of issuing a notification that prompts a user to take action to achieve a goal at an appropriate time. [Means for solving the problem]

[0007] The notification control system of the present invention is a notification control system that uses a computer having a processor and memory to send a notification to encourage a user to take action, and the processor creates action schedule data that estimates the user's action schedule using action history data including actions for achieving the user's goals, which is obtained from the user's action performance information and is managed together with the user's goals, calculates a schedule addition score that indicates the degree of ease of adding the new schedule to the schedule included in the action schedule data based on whether or not a scene in which the addition of a new schedule or an addition option satisfies a specified condition, calculates a notification score that indicates the degree of ease of success of the notification for the schedule included in the action schedule data based on whether or not the user's response when receiving the notification satisfies a specified condition, and controls the timing of sending the notification to the user to achieve the goal based on the schedule addition score and the notification score. Effect of the Invention

[0008] According to the present invention, it is possible to provide a notification that prompts an action for achieving a goal at an appropriate time. Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiments. [Brief description of the drawings]

[0009] [Figure 1A] 1 is a configuration example of a notification control system. [Figure 1B] 2 is a diagram showing an example of a hardware configuration. [Diagram 2] 13 is an example of a target definition table. [Diagram 3] 4 is an example of a user management table. [Figure 4] 1 is an example of a behavior history table. [Diagram 5] 13 is an example of a notification history table. [Figure 6] 13 is an example of an action schedule table. [Figure 7] 13 is an example of a schedule addition table. [Figure 8] 13 is an example of a behavior history creation flow. [Figure 9] 13 is an example of a notification control flow. [Figure 10] 13 is an example of a planned additional score calculation flow. [Figure 11] 13 is an example of a notification score calculation flow. [Figure 12] 13 is an example of an addition schedule creation flow. [Figure 13] 13 is an example of a screen output. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. The examples are illustrative for explaining the present invention, and are omitted and simplified as appropriate for clarity of explanation. The present invention can be implemented in various other forms. Unless otherwise specified, each component may be singular or plural. The position, size, shape, range, etc. of each component shown in the drawings may not represent the actual position, size, shape, range, etc., in order to facilitate understanding of the invention. Therefore, the present invention is not necessarily limited to the position, size, shape, range, etc. disclosed in the drawings.

[0011] As examples of various information, the various information may be described using expressions such as "table," "list," and "queue," but the various information may be expressed using data structures other than these. For example, various information such as "XX table," "XX list," and "XX queue" may be expressed as "XX information." When describing identification information, expressions such as "identification information," "identifier," "name," "ID," and "number" are used, but these are mutually interchangeable.

[0012] When there are multiple components having the same or similar functions, they may be described by using the same reference numerals with different subscripts, or when there is no need to distinguish between these multiple components, the subscripts may be omitted.

[0013] In the embodiments, a process performed by executing a program may be described. Here, a computer executes the program using a processor (e.g., CPU, GPU), and performs the process defined by the program while using a storage resource (e.g., memory) and an interface device (e.g., communication port), etc. Therefore, the subject of the process performed by executing the program may be the processor. Similarly, the subject of the process performed by executing the program may be a controller, device, system, computer, or node having a processor. The subject of the process performed by executing the program may be a calculation unit, and may include a dedicated circuit that performs specific processing. Here, the dedicated circuit is, for example, an FPGA (Field Programmable Gate Array), an ASIC (Application Specific Integrated Circuit), or a CPLD (Complex Programmable Logic Device), etc.

[0014] The program may be installed in the computer from a program source. The program source may be, for example, a program distribution server or a computer-readable storage medium. When the program source is a program distribution server, the program distribution server may include a processor and a storage resource for storing the program to be distributed, and the processor of the program distribution server may distribute the program to be distributed to other computers. In addition, in the embodiment, two or more programs may be realized as one program, and one program may be realized as two or more programs.

[0015] The notification control system according to this embodiment will be described below.

[0016] Fig. 1A is a configuration example of a notification control system 1000 in this embodiment. As shown in Fig. 1A, the notification control system 1000 includes a notification control device 1, a user terminal 2, and a content providing device 3, which are connected to each other via a network L1.

[0017] The notification control device 1 is configured to include at least a storage unit 11, a behavior history creation unit 12, a notification control unit 13, an addition schedule creation unit 14, and a score calculation unit 15.

[0018] The notification control device 1 expresses an action by a type of movement and a location. Hereinafter, when expressing an action, information that combines the type of movement and the location is included.

[0019] The storage unit 11 is a device or equipment that stores information necessary for processing. The storage unit 11 has at least a goal definition table 100, a user management table 110, an action history table 120, a notification history table 140, an action schedule table 160, and an additional schedule table 180.

[0020] The goal definition table 100 and the user management table 110 are created in advance and stored in the storage unit 11. The action history table 120 is periodically updated by the execution of the action history creation unit 12, and is stored in the storage unit 11 even after the execution of the action history creation unit 12. The notification history table 140 records the execution result of the notification control unit 13. The action schedule table 160 is newly created based on the information in the action history table 120 as an action schedule within the goal period every time the notification control unit 13 is executed, and is discarded when the execution of the notification control unit 13 is completed. The addition schedule table 180 is created by the addition schedule creation unit 14.

[0021] The notification control device 1 is a computer having a general hardware configuration, such as a PC (Personal Computer), a server, etc. The notification control device 1 is communicatively connected between a user terminal 2 and a content providing device 3 via L1.

[0022] L1 is a communication network such as a local area network (LAN), a wide area network (WAN), or the Internet, and is connected wirelessly or by wire.

[0023] The user terminal 2 is a terminal such as a mobile phone, a smartphone, or a smart watch that can be carried by the user to record activities and output information to the user. The user terminal 2 has sensors such as a heart rate sensor, an acceleration sensor, a temperature sensor, and an air pressure sensor, input devices such as a touch panel and a microphone, output devices such as a display and a speaker, and a storage unit such as a memory. The storage unit stores information obtained from these various sensors, such as location information, number of steps, speed, screen viewing time, etc. (hereinafter referred to as behavioral performance information). The stored behavioral performance information is periodically transmitted to the notification control device 1. The output device of the user terminal 2 is, for example, the screen of the terminal, and may be a touch panel integrated with the input device. The output device displays the information notified at the timing controlled by the notification control device 1.

[0024] The content providing device 3 is a server that holds and provides content information, and is, for example, a computer that provides a spot search service that provides spot information. There may be a plurality of content providing devices.

[0025] FIG. 1B is a diagram showing an example of a hardware configuration in which the terminals and devices constituting the notification control system 1000 shown in FIG. 1A are configured using a computer 200 including a CPU 201.

[0026] A memory 202, a HDD 203, a NW 204, and an IO 205 are connected to a CPU 201 via a bus 206. The NW 204 is an interface for connecting to a network L1, and the IO 205 is an interface for connecting to the above-mentioned sensors, input devices, and output devices.

[0027] 1A (e.g., behavior history creation unit 12, notification control unit 13, addition schedule creation unit 14, score calculation unit 15) are stored in memory 202 and HDD 203 and are configured by programs executed by CPU 201. Storage unit 11 in FIG. 1A is configured by memory 202 and HDD 203.

[0028] In the configuration of Figure 1B, various programs stored in memory 202 are executed by CPU 201 to realize each process, but as described above, each part of the notification control device 1 can also be realized in hardware, for example by being integrated into an integrated circuit as a circuit that performs each process.

[0029] In addition, while FIG. 1A illustrates an example in which the terminals and devices of the notification control system 1000 are configured by a single computer, the functions of the notification control system 1000 may be configured by one or more computers, or all or part of these functions may be distributed across one or more computers, such as a cloud, and similar functions may be realized by communicating with each other via a network.

[0030] An example of the goal definition table 100 will be described with reference to Fig. 2. The goal definition table 100 is a table that defines the goals of a user. In the goal definition table 100, a goal ID 101 is assigned to each goal. In order to define the goal in a form that can be measured by the system, the goal definition table 100 has a target 102, a movement 103, a location 104, a goal value 105, a validity period 106, and a frequency 107.

[0031] Information that can be calculated from behavioral performance information such as the number of steps, movement speed, location information, time, and time of day is specified for the target 102 along with calculation conditions. The calculation conditions are, for example, conditions such as total value and maximum value, and the total number of steps is specified for the total number of steps, and the total time is specified for the total value of time.

[0032] The action to be achieved as a goal is specified by the type of movement 103 (walking, train, car, stay, etc.) and the location 104. The location 104 may be specified by latitude and longitude, or may be the name of a specific location.

[0033] The target value 105 is a specific value that indicates what value the object 102 must reach to be considered as having achieved the goal.

[0034] The effective period 106 is the time period until the goal is achieved, and the frequency 107 is the frequency with which the goal needs to be achieved.

[0035] In Fig. 2, for example, the goal "total number of steps" identified by goal ID "1" is to walk 8000 steps in one day regardless of movement 103 or location 104 (ANY), and is defined as continuing to achieve such a goal every day. In this way, if the goal is to walk 8000 steps every day, as in the case where goal ID 101 in Fig. 2 is "1", target 101 is defined as total number of steps, goal value 105 as 8000 steps, valid period 106 as one day, and frequency 107 as every day. In this example, since it does not matter what action is taken as long as the number of steps increases, movement 103 and location 104 are defined as ANY in the sense that there is no need to limit them.

[0036] When the number of steps cannot be acquired due to the performance of the user terminal 2, a similar goal can be defined using time information that can be acquired more reliably. When the goal ID 101 in Fig. 2 is "2", the sensitivity and measurement accuracy for counting the number of steps of the sensor possessed by the user terminal 2 do not meet a certain standard, so the goal is defined in terms of "time", which is different from the number of steps. Fig. 2 shows an example where the goal is defined as walking 80 minutes every day.

[0037] You can also set a goal to stay in a specific location. If your goal is to go to the gym for 60 minutes every week, you can define goal ID 101 as "3." Gym A is the name of a specific gym.

[0038] In addition, when the goal ID 101 is "4", an example is provided that defines the goal as spending 60 minutes every week in a specific library. In this way, there are many different goals that can be defined, such as goals for when you want to make weekly study a habit.

[0039] An example of the user management table 110 will be described with reference to FIG. 3. The user management table 110 is a table for managing users in association with goals. To identify a user, a user ID 111 is assigned to the user, and a goal that each user aims at is defined as a goal ID 112. The goal ID 112 is the same as the goal ID 101 in the goal definition table 100. A plurality of goal IDs 101 may be defined for one user ID. In addition, the example of the user management table 110 describes only the minimum necessary data, and in reality, other information related to the user, such as the user name and the type of action achievement information that can be acquired by the terminal held by the user, may also be held. In this example, it is shown that a user identified by a user ID "3" has two goals identified by goal IDs "1" and "3".

[0040] An example of the behavior history table 120 will be described with reference to Fig. 4. The behavior history table 120 is a table that accumulates and stores the behavior history of the user. The behavior history table 120 is updated by the behavior history creation unit 12 based on the behavior result information acquired from the user terminal 2. The behavior history table 120 identifies the type and location of movement from the behavior result information, and updates the date 122, day of the week 123, time 124, movement 125, and location 126.

[0041] The time during which the screen display of the user terminal 2 was active is recorded as the screen viewing time 127. The first record example in Fig. 4 indicates that the screen was viewed for 10 minutes between 7:00 and 8:00.

[0042] The behavior history creation unit 12 calculates the goal achievement rate using the target 102 and the target value 105 in the goal definition table 100 based on the goal ID 128, and records the achievement status in the latest record. If the goal validity period 106 is one day, the behavior history creation unit 12 starts calculating the goal achievement rate from the start of the day, and updates the goal achievement rate every time the behavior history is updated.

[0043] 4, the goal achievement rate 129 indicates the goal achievement rate at the end of the action of the corresponding record. For example, in record 401 where the time is 8:00, the goal achievement rate 129 is 20%. This is because the person started walking from the time 8:00, and thus achieved 20% of the number of steps toward the goal.

[0044] The behavior history creation unit 12 is executed periodically, and a record of behavior related to the latest date and time is added to the behavior history table 120. In the example of Fig. 4, when data of the same movement and location continues, the data is aggregated and recorded in one record, but a new record may be added to the behavior history table 120 every time the behavior history creation unit 12 is executed, regardless of the contents of the movement and location.

[0045] In FIG. 4, the first behavior starts at 7:00. This is because the behavior history creation unit 12 creates a new behavior history record for the wake-up time every day. The behavior history creation unit 12 may create the new behavior history record by regarding the time when the user first operates the user terminal 2 in a day (for example, the time when the power is turned on or the time when the screen is touched) as the wake-up time. Alternatively, the behavior history creation unit 12 may estimate the sleep time or morning alarm time set in the user terminal 2 as the wake-up time.

[0046] If the same user has multiple goal IDs, the behavior history creation unit 12 calculates and records the achievement level for each goal ID. Since the content of movement and screen viewing time do not change even if the goal changes, when the goal ID increases, the behavior history creation unit 12 can record behavior history for multiple goals in one record by entering multiple pieces of information in an array format in the columns of goal ID 128 and goal achievement rate 129.

[0047] An example of the notification history table 140 will be described with reference to FIG. 5. The notification history table 140 is a table that accumulates and stores a history of notifications that prompt the user terminal 2 to take action to achieve a goal. The notification history table 140 has at least a notification ID 141, a notification date 142, a notification time 143, a notification viewing date 144, a notification viewing time 145, a notification acceptance 146, a user ID 147, and a goal ID 148. Each time the notification control unit 13 performs a notification, it assigns a notification ID 141 and records the notification implementation date and time in the notification date 142 and the notification time 143. The notification control unit 13 records the date and time when the notification was viewed in the notification viewing date 144 and the notification viewing time 145. When the user performs an acceptance operation on the notification as a result of viewing the notification, the notification control unit 13 records the acceptance status in the notification acceptance 146. For example, the notification control unit 13 notifies the user of an additional schedule and records the acceptance when the user performs an operation to accept the schedule.

[0048] In FIG. 5, for example, the notification identified by the notification ID "1" is a notification for a user identified by the user ID "1" and a goal identified by the goal ID "1", and is notified at 8:20 a.m. on March 1, 2023. It is also shown that the notification was viewed by the user immediately thereafter (for example, the notification content display screen 21 described later was opened). Furthermore, it is also shown that after the user viewed the notification, the notification was accepted (for example, the accept button 1302, the search again button 1303, or the ignore button 1304 on the notification content display screen 21 described later was pressed).

[0049] An example of the action schedule table 160 will be described with reference to FIG. 6. The action schedule table 160 is a table that accumulates and stores the action schedule of the user. This table is created when the notification control unit 13 estimates the action schedule based on the action history table 120. The notification control unit 13 records a date 162 and a day of the week 163 for an estimation target date, which is the date and time for estimating the action schedule, and records the result of estimating the schedule from the action history in a time 164, a movement 165, and a location 166. The notification control unit 13 calculates a goal achievement rate 168 for a goal ID 167 based on the performance in the past action history.

[0050] The schedule addition score 169 and the notification score 170 in the action schedule table 160 are calculated and recorded by the score calculation unit 15 .

[0051] The schedule addition score 169 is the degree of ease of adding a schedule. The ease of adding a schedule is expressed by the type of movement, location, time period, and chronological order in which adding a schedule is recommended, and the number of options (content that can be provided) for adding a schedule for a location or time period. In other words, the greater the number of these situations and the number of options, the greater the ease of adding a schedule.

[0052] A situation where adding an event is recommended is when the user is not on the way to an event that has a fixed time, such as going to work. For example, if the user of this system is an office worker, he or she is bound by the working hours set by the workplace, so even if the user adds an event during the working hours, the added event is unlikely to be accepted. Therefore, in this case, the situation where adding an event is recommended is when the user is leaving the office after working hours, rather than when the user is traveling to the office, and the score is higher.

[0053] In addition, for the option to add a plan, if the location is a train station in an urban area with many stores around, there is a wealth of content that can be provided as a destination during the time when many stores are open. Therefore, the user is more likely to select from the options to add a plan and take action on the added plan, and the score is higher.

[0054] The notification score 170 is the degree of success of the notification. The success of the notification includes the degree of success of the notification, such as the degree of the notification being viewed, the degree of the notification changing behavior, and the degree of the notification achieving a goal.

[0055] An example of the added schedule table 180 will be described with reference to FIG. 7. The items in the table are almost the same as those in the scheduled activity table 160, but the score can be omitted. The added schedule table 180 is a table in which the added schedule creation unit 14 recreates the contents of the scheduled activity table 160 that change due to the addition of a schedule. Consider a case in which a schedule is added to a schedule of staying at Y station at 17:45 in the record 601 in the scheduled activity table 160 in FIG. 6. In this case, the added schedule creation unit 14 recreates a series of schedules from the time of the record 601 to which the schedule was added in the scheduled activity table 160 until the end of the target period, and records the series of schedules in the added schedule table 180. In the example of FIG. 7, the added schedule creation unit 14 recreates the schedule from the time of the record 601 to which the schedule was added in the scheduled activity table 160 as a starting point until the time of the record 602 of the last scheduled activity recorded as record 602. Due to the recreation, a new time is calculated for each schedule as the schedule is added.

[0056] The operation of the behavior history creation unit 12 will be described with reference to Fig. 8. The behavior history creation unit 12 is repeatedly executed at regular intervals. The behavior history creation unit 12 specifies the target ID of the processing target user based on the user management table 110 in advance.

[0057] The behavior history creation unit 12 acquires behavioral achievement information from the user terminal 2 (S801). Specifically, behavioral achievement information corresponding to the period from when the behavior history creation unit 12 is executed last time to when it is executed this time is acquired. For example, if the behavior history creation unit 12 is executed every few minutes, new behavioral achievement information for those few minutes is acquired. The behavioral achievement information is an activity that can be recorded by the user terminal 2, and it is assumed that the user terminal 2 records location information, the number of steps, the screen viewing state, and the like together with a timestamp.

[0058] Next, the behavior history creation unit 12 identifies the type and location of movement from the acquired behavioral achievement information (S802). The location may be either a location represented by latitude and longitude, or a location replaced with the name of the point. The behavior history creation unit 12 infers the type of movement from the location information and its change. For example, if the movement starts from a station and the location information indicates movement along a railroad at a high speed of a predetermined speed or higher, the behavior history creation unit 12 infers that the movement is by train. Also, if the location information indicates that the movement is on a road and the movement is at a high speed of a predetermined speed or higher, the behavior history creation unit 12 infers that the movement is by car. Alternatively, if the movement can be considered to have changed at a low speed (such as 3 km per hour) less than a predetermined speed for a certain period of time, the behavior history creation unit 12 infers that the movement is by walking. Furthermore, if there is no change in the location information over time, the behavior history creation unit 12 infers that the movement is a stay. By setting multiple thresholds for the movement speed or combining it with vibration information and step count information of the user terminal 2, it is also possible to identify movement by running or bicycle.

[0059] Next, the behavior history creation unit 12 calculates the goal achievement rate from the acquired behavior result information (S803). The behavior history creation unit 12 calculates what percentage of the goal the behavior result information acquired as the difference from the previous execution time represents, and records the calculated percentage in the latest record of the behavior history table 120 as the latest goal achievement rate added to the goal achievement rate at the previous execution time.

[0060] The operation of the notification control unit 13 will be described with reference to Fig. 9. The notification control unit 13 starts to execute, for example, at the start of the effective period of the goal. If the effective period of the goal is one day and the frequency is daily, the notification control unit 13 starts to execute at the timing of waking up every morning.

[0061] First, the notification control unit 13 estimates the action schedule until the end of the valid period of the goal of the user, and updates the action schedule table 160 (S901). For example, if the valid period is one day, the notification control unit 13 estimates the action schedule from the estimated time to the end of the day (e.g., midnight).

[0062] In estimating the planned behavior, the notification control unit 13 may refer to the behavior history table 120, read the behavior history with the most similar tendency from the location information at the time of estimation and the behavior history up to immediately before, and adopt the behavior history as the planned behavior. As a means for this, statistical analysis may be used.

[0063] For example, the notification control unit 13 clusters the behavior history recorded in the behavior history table 120 by date 162, day of the week 163, time 164, movement 165, and location 166 to classify them into patterns. Then, the notification control unit 13 calculates a distance indicating the closeness between the feature amount of the behavior history for the last few hours and the feature amount of each behavior history pattern, and identifies the behavior history pattern that is the closest among the calculated distances. The notification control unit 13 may select a representative example from the identified patterns. This representative example may be, for example, a method of adopting the latest behavior history from the corresponding pattern, or a method of adopting a behavior history that is considered to be statistically average among the patterns. Note that, when statistical analysis is not performed or there is no corresponding pattern, a method of adopting the behavior history for the most recent same day of the week as the behavior schedule may be used, assuming that the same behavior is repeated on the same day of the week.

[0064] Every time the notification control unit 13 estimates an action schedule, it overwrites the contents of the action schedule table 160 with new action schedule contents with the re-estimated time as the start time. Note that, when S901 is the second or subsequent execution executed in response to the result of the determination that the target period has not ended (S908; No), and in the previous loop, when the notification control unit 13 notifies the user of an additional schedule in S906 and the user accepts the additional schedule in S907, the schedule after the additional schedule start time in the action schedule table 160 is replaced with the contents of the corresponding additional schedule.

[0065] Next, the notification control unit 13 calls the score calculation unit 15, and calculates the planned addition score 169 and the notification score 170 (S902, S903). The processes of S902 and S903 will be described later with reference to Figs. 10 and 11, respectively.

[0066] The notification control unit 13 judges whether the estimated goal achievement rate of the last record in the action schedule table 160 has reached 100% (S904), and if not (S904; No), executes the additional schedule creation unit 14 to create an additional schedule (S905). The process of S905 will be described later with reference to FIG. 12.

[0067] When the notification control unit 13 detects the start of an action that is before the start time of the created additional schedule and has the highest notification score in the action schedule table 160, it notifies the user of the additional schedule (S906). The notification control unit 13 may detect the start of an action by checking whether the action (type of movement, location), time series, etc. of the latest action history matches the action to be notified while periodically and repeatedly executing the action history creation unit 12. The time series here indicates that even if the time does not match the action schedule, the start of the target action is identified from the context between the action at one time, such as "started walking after staying at the office," and the action at another time.

[0068] The notification control unit 13 records, in response to the notification, the time when the notification was viewed and whether the notified additional schedule was accepted in the notification history table 140 (S907).

[0069] The notification control unit 13 judges whether the estimated planned action period has ended, and loops this flow at regular intervals (S908) until it judges that the period has ended (S908; Yes). If the goal period is one day, execution ends when the date changes, and when the action history creation unit 12 detects the start of the effective period of the next goal, execution of the notification control unit starts again.

[0070] A method for calculating the planned additional score will be described with reference to FIG.

[0071] The score calculation unit 15 selects records for which score calculation has not been performed, starting from the top of the activity schedule table 160 (S1001). The score calculation unit 15 determines whether the movement 165 and location 166 of the extracted record are a specific type of movement, location, time period, and time series (S1002). If the determination in S1002 is Yes, the score calculation unit 15 increases the schedule addition score 168 (S1003).

[0072] For example, if the location is a station, the score calculation unit 15 increases the score since it is easy to add a plan such as a detour. Furthermore, if the time period is in the afternoon, the score calculation unit 15 increases the score since it considers that the success rate of adding a plan is high when it is on the way home after finishing an errand. In addition, it is possible to specify a condition by time series, and a time series of multiple actions such as "walking or traveling by train after staying at the office" is defined, and the score calculation unit 15 increases the score if it corresponds.

[0073] The score calculation unit 15 may judge each of these elements of movement, place, time period, and time series individually, and may add a score each time the element meets a predetermined condition. Alternatively, the score calculation unit 15 may add a score when a combination of movement, place, time period, and time series meets a predetermined condition. Furthermore, the score calculation unit 15 may change the amount of increase in the score depending on the content of the corresponding element, such as the type of movement or the type of place.

[0074] The score calculation unit 15 determines whether or not there is a record for which the score has not been calculated (S1004), and if S1004 is Yes, the process returns to the beginning of the flow and calculates the score.

[0075] The above explanation is an example of calculating the schedule addition score, and the score may be added based on other factors. For example, the goal achievement rate when a schedule is added for the target behavior may be predicted based on the past goal achievement rate and notification acceptance results, and the score may be increased.

[0076] A method for calculating the notification score will be described with reference to FIG.

[0077] The score calculation unit 15 selects records for which the notification score calculation has not been performed, starting from the top of the action schedule table 160 (S1101). As described below, the notification score is calculated based on whether or not the user's response when receiving the notification satisfies predetermined conditions such as S1102, S1104, S1106, S1108, and S1110.

[0078] The score calculation unit 15 reads the movement, location, and time period of the corresponding record, searches a certain range of the behavior history table 120 for past behavior history including the same values ​​as those read, and judges whether the screen viewing time 127 is longer than a certain standard length (S1102). If S1102 is Yes, the score calculation unit 15 considers that there is a high possibility that the notification will be viewed, and increases the notification score 170 (S1103). For example, the score calculation unit 15 increases the notification score when it judges from the behavior history stored in the behavior history table 120 that the behavior has a track record of screen viewing time 127 of one minute or more on average.

[0079] The score calculation unit 15 searches the past notification history table 140 corresponding to the movement, location, and time period of the corresponding record, and judges whether the notification viewing time 145 remains in the corresponding record (S1104). If S1104 is Yes, the score calculation unit 15 judges that the notification success rate is high and increases the notification score (S1105). For example, if the notification acceptance 146 of the record in the notification history table 140 that matches the notification viewing date and notification viewing time among the movement, location, and time period of the corresponding record in the action schedule table 160, or that is within a predetermined time range from the corresponding date and time, is set to "accepted", the score calculation unit 15 judges that there is a high possibility that the user will view the notification if it is notified at that timing, and increases the notification score.

[0080] Furthermore, the score calculation unit 15 searches the past notification history table 140 corresponding to the movement, location, and time period of the corresponding record, and judges whether or not the difference between the notification time 143 and the notification viewing time 145 in the corresponding record is smaller than a predetermined time width (S1106). If S1106 is Yes, the score calculation unit 15 judges that it is an appropriate timing and increases the notification score (S1107). For example, if the difference between the notification time 143 and the notification viewing time 145 is less than 30 seconds, the score calculation unit 15 judges that the user viewed the notification immediately after the notification, so that the user is unlikely to be bound by another action, and it is a timing when the notification can be confirmed immediately, and increases the notification score. Furthermore, the score calculation unit 15 searches the past notification history table 140 corresponding to the movement, location, and time period of the corresponding record, and judges whether or not the ratio of "accepted" indicating that the notification was accepted is recorded in the notification acceptance 146 of the corresponding record is equal to or higher than a certain level (S1108). If S1108 is Yes, the score calculation unit 15 determines that the notification success rate is high and increases the notification score (S1109). For example, the score calculation unit 15 searches the notification history table 140 for records including the notification viewing date 144 and notification viewing time 145 in the same time period as the corresponding record, and counts the number of times the notification acceptance 146 of the searched records is set to "accepted". If the counted value is equal to or greater than a predetermined threshold, the score calculation unit 15 determines that the user is in an environment where it is easy to accept notifications (for example, a standby state where the user is thinking about what to do next after finishing work, or a relaxed state where the user is mentally free during a break during work), and increases the notification score.

[0081] Furthermore, the score calculation unit 15 judges whether the probability of the goal achievement is high when the notification was given in a similar situation in the past (S1110). If S1110 is Yes, it is judged that the goal achievement record is high, and the notification score is increased (S1111). The time when the notification was given in a similar situation in the past refers to a case where a past notification history corresponding to the movement, place, and time period of the record currently being processed exists in the notification history record. The score calculation unit 15 searches the behavior history of the date of this notification from the behavior history table 120, and if the goal achievement rate exceeds 100%, it is judged that the goal was achieved. If there are multiple corresponding past notification histories, it searches the behavior history of each date from the behavior history table 120 for each notification that matches the movement, place, and time period of the record currently being processed, and checks the goal achievement status on each date. If the number of dates on which the goal achievement rate on each date exceeds 100% is equal to or greater than a predetermined threshold, the score calculation unit 15 judges that the goal achievement record is high and that the probability of the goal achievement rate being 100% this time is also high, and increases the notification score.

[0082] The score calculation unit 15 determines whether there is any record for which the score has not been calculated (S1112). If the result of S1112 is Yes, the process returns to the beginning of the flow and the score is calculated.

[0083] The amount of increase in the score can be changed depending on which element the record corresponds to (screen viewing time 127, notification acceptance 146 is "accepted", etc.). Even if the element is the same, the amount of increase in the score can be changed depending on the degree of the element. For example, when the record corresponds to "long screen viewing time 127" (S1102), the score calculation unit 15 can change the amount of increase in the score depending on the degree of the element, such as 1 point if the viewing time is 1 minute or more, 2 points if it is 5 minutes or more, and 3 points if it is 10 minutes or more. This is an example of score calculation, and the determination of the element's applicability may be added.

[0084] The operation of the addition schedule creator 14 will be described with reference to FIG.

[0085] During execution of the notification control section 13, if the estimated action schedule is not sufficient to achieve the goal, the execution of the additional schedule creating section 14 is started.

[0086] The additional schedule creating unit 14 extracts the location and time of the record with the highest schedule addition score 169 from the scheduled activity table 160 (S1201).

[0087] The addition schedule creation unit 14 searches for content in the content providing device 3 using the acquired location and time as search conditions (S1202). For example, since the content providing device 3 is a computer that executes a spot search service, if the schedule addition score for the time "17:45" and the location "Y Station" is high, it searches for and acquires spots that can be visited at the time "17:45" within a certain distance range from "Y Station". Note that if there are multiple records with the highest schedule addition score in S1201, the content providing device 3 searches for content for each location and time.

[0088] The addition schedule creation unit 14 creates a new action schedule that includes visits to the acquired content, starting from the time and place used in the content search, and creates an addition schedule. If there are multiple contents as a result of executing S1202, the addition schedule creation unit 14 creates an addition schedule by adding a record to the addition schedule table 180 for each content. When creating an addition schedule, the addition schedule creation unit 14 also calculates information to be stored in the goal achievement rate 181 of the addition schedule table 180. If there are multiple addition schedules, the addition schedule creation unit 14 records only the addition schedule that meets a specific condition as a record in the addition schedule table 180, and discards the other addition schedules (S1203). The specific condition is, for example, a case where the goal achievement rate of the addition schedule is within a specific range. For example, when the goal achievement rate 168 of the action schedule table 160 and the goal achievement rate of the addition schedule table 180 are sequentially added, if the goal achievement rate becomes 100% to 150%, the addition schedule creating unit 14 records the addition schedule up to that point in the addition schedule table 180, but does not record other addition schedules. This makes it possible to prevent the registration of excessive addition schedules.

[0089] The contents of the notification to the user terminal 2 will be described with reference to Fig. 13. First, the notification control unit 13 transmits a notification to the user terminal 2 by push notification or the like. The user terminal 2 displays on the terminal screen that the notification has arrived. When the user terminal 2 accepts a selection of information on the arrival of the notification by clicking or the like from the user, the screen transitions to a notification content display screen 21.

[0090] The notification content display screen 21 has an addition schedule display area 1301 , an accept button 1302 , a search again button 1303 , and an ignore button 1304 .

[0091] The content of the addition schedule table 180 at the time of the notification is displayed in the addition schedule display area 1301. When there are multiple candidates for the addition schedule, the user terminal 2 may prepare tabs at the top of the addition schedule display area 1301, so that the display content can be switched between multiple ones. The user terminal 2 may determine information indicating whether the addition schedule has been accepted or not based on the presence or absence of a button input by the user. For example, when the accept button 1302 is pressed in the user terminal 2, the notification control unit 13 records information of "accepted" in the notification acceptance for the corresponding notification ID in the notification history table 140. The notification control unit 13 reflects the accepted addition schedule by adding a record to the action schedule table 160. When the re-search button 1303 is pressed in the user terminal 2, the addition schedule creation unit 14 creates a new addition schedule starting from the current time and current location. This assumes a case in which time has passed between the time of notification and viewing the notification, and the displayed addition schedule does not match the user's situation, and the user searches again. When this operation is performed, the notification control unit 13 also records "accepted" in the notification history table 140. Moreover, when the ignore button 1304 is pressed in the user terminal 2, the notification control unit 13 records "ignored" in the notification history table 140. In this manner, the notification control unit 13 updates the notification acceptance 146 according to the type of response to the notification content input from the user terminal 2.

[0092] As described above, the notification control system 100 in this embodiment is a notification control system that issues a notification encouraging a user to take an action by a computer having a processor and a memory, as described in S901 to S903 of FIG. 9, FIGS. 4, 6, 10, 11, etc., and the processor creates action schedule data (e.g., action schedule table 160) that estimates the action schedule of the user using action history data (e.g., action history table 120) including actions for achieving the user's goal, which is obtained from the action achievement information of the user and is managed together with the user's goal, and for the schedule included in the action schedule data, A schedule addition score indicating the degree of ease of adding the new schedule is calculated based on whether or not the scene where the addition of a new schedule is recommended or the option for adding the new schedule satisfies a predetermined condition (e.g., a certain type of movement, location, time period, or time sequence), and a notification score indicating the degree of ease of success of the notification is calculated based on whether or not the user's response when receiving the notification for the schedule included in the action schedule data satisfies a predetermined condition (e.g., the condition of the decision branch shown in FIG. 11), and the timing of sending the notification to the user to achieve the goal is controlled based on the schedule addition score and the notification score. This makes it possible to send a notification at an appropriate timing to encourage action to achieve the goal. Specifically, the goal achievement rate can be increased by controlling the notification to be sent at a timing with a high success rate.

[0093] 12, etc., if the user's goal cannot be achieved by the action schedule obtained from the user's goal and the action history data, the processor adds the new plan for which the plan addition score satisfies a predetermined condition (e.g., the plan addition score is the highest), and notifies the user of the added plan when it detects the start of an action for which the notification score satisfies a predetermined condition (e.g., the notification score is the highest) before the start of the addition. In this way, even if it is foreseen that the goal will not be achieved, an additional plan that makes it easy to take action to achieve the goal can be created, and a notification can be issued to encourage the user to take action to achieve the goal.

[0094] 11 and the like, the processor increases the notification score when the user's response when receiving the notification satisfies a predetermined condition, which is the length of time the screen of the terminal receiving the notification is viewed as in S1102, the degree of viewing record of the notification as in S1104, the difference between the time of the notification and the time of viewing the notification as in S1106, the degree of acceptance record of the notification as in S1108, or whether the goal was achieved by the past notification as in S1110. Thus, the notification score can be managed based on these conditions.

[0095] As described in Fig. 5, S907 in Fig. 9, Fig. 13, etc., the notification control system has an input display interface (e.g., IO205), and the processor displays the added new schedule and information for selecting whether or not to accept the new schedule on the input display interface, and records the result of the selection by the user as the notification history (e.g., notification acceptance 146 in the notification history table 140). This makes it possible to grasp the track record of when the user has tended to accept notifications in the past.

[0096] The present invention is not limited to the above-described embodiments as they are, and in the implementation stage, the components can be modified and embodied within the scope of the gist of the present invention, or multiple components disclosed in the above-described embodiments can be appropriately combined. [Explanation of symbols]

[0097] 1 Notification Control Device 2. User terminal 11 Storage section 12 Behavioral History Creation Department 13 Notification control section 14 Additional Schedule Creation Department 15 Score calculation section 100 Goal Definition Table 110 User Management Table 120 Action History Table 140 Notification History Table 160 Action Schedule Table 180 Additional Schedule Table 21 Notification content display screen 1301 Additional Display Area 1302 Accept button 1303 Search again button 1304 Ignore button

Claims

1. A notification control system for notifying a user of an action by a computer having a processor and a memory, The processor, creating behavior schedule data that estimates a behavior schedule of the user using behavior history data that is obtained from the behavioral performance information of the user and that includes behavior for achieving the goal and is managed together with the goal of the user; calculating a schedule addition score indicating the degree of ease of adding a new schedule to the schedule included in the action schedule data, based on whether or not a scene for which the addition of a new schedule or an option for addition satisfies a predetermined condition; calculating a notification score indicating the likelihood of success of the notification based on whether or not a response of the user when receiving the notification for the schedule included in the action schedule data satisfies a predetermined condition; and controlling a timing for notifying the user so as to achieve the goal based on the scheduled addition score and the notification score. A notification control system comprising:

2. The processor, If the user's goal cannot be achieved by the action schedule obtained from the user's goal and the action history data, adding the new schedule whose schedule addition score satisfies a predetermined condition; When a start of an action in which the notification score satisfies a predetermined condition is detected before the start of the addition, the added schedule is notified. The notification control system according to claim 1 .

3. The processor, When the user's response when receiving the notification satisfies a predetermined condition, which is the length of time the screen of the terminal receiving the notification is viewed, the degree of viewing of the notification, the difference between the time of the notification and the time of viewing the notification, the degree of acceptance of the notification, or whether the goal was achieved by the notification in the past, the notification score is increased. The notification control system according to claim 1 .

4. The notification control system includes: An input display interface is provided, The processor, displaying, on the input display interface, the new schedule that has been added and information for selecting whether or not to accept the new schedule; recording the result of the selection from the user as a history of the notification; The notification control system according to claim 3 .

5. A notification control method for notifying a user of an action by a computer, comprising: creating behavior schedule data that estimates a behavior schedule of the user using behavior history data that is obtained from the behavioral performance information of the user and that includes behavior for achieving the goal and is managed together with the goal of the user; calculating a schedule addition score indicating the degree of ease of adding a new schedule to the schedule included in the action schedule data, based on whether or not a scene for which the addition of a new schedule or an option for addition satisfies a predetermined condition; calculating a notification score indicating the likelihood of success of the notification based on whether or not a response of the user when receiving the notification for the schedule included in the action schedule data satisfies a predetermined condition; and controlling a timing for notifying the user of the achievement of the goal based on the schedule addition score and the notification score. A notification control method comprising:

6. If the user's goal cannot be achieved by the action schedule obtained from the user's goal and the action history data, adding the new schedule whose schedule addition score satisfies a predetermined condition; When a start of an action in which the notification score satisfies a predetermined condition is detected before the start of the addition, the added schedule is notified. The notification control method according to claim 5 .

7. When the user's response when receiving the notification satisfies a predetermined condition, which is the length of time the screen of the terminal receiving the notification is viewed, the degree of viewing of the notification, the difference between the time of the notification and the time of viewing the notification, the degree of acceptance of the notification, or whether the goal was achieved by the notification in the past, the notification score is increased. The notification control method according to claim 5 .

8. Displaying the added new schedule and information for selecting whether or not to accept the new schedule on an input display interface; recording the result of the selection from the user as a history of the notification; The notification control method according to claim 7 .

Images