Task management method, program, and task management system

Abstract

In this task management method, a person in charge of a task to be performed by any user (U1) among a plurality of the users (U1) is determined on the basis of condition information that indicates conditions pertaining to each task of the plurality of users (U1) (S11). In the task management method, information indicating the task to be performed associated with the determined person in charge is output (S13).

Description

Task management method, program, and task management system

[0001] The present disclosure relates to a task management method and the like for managing tasks executed by users who use devices.

[0002] For example, Patent Literature 1 discloses a household chore schedule creation support device, which creates a household chore schedule by having a user specify the type, time, and location of the household chores to be performed by a household robot.

[0003] JP 2012-190073 A

[0004] The present disclosure provides a task management method and the like that can easily reduce the burden of managing tasks related to devices.

[0005] In a task management method according to one aspect of the present disclosure, a person in charge of a target task to be performed by one of a plurality of users is determined based on condition information indicating conditions related to each of the tasks of the plurality of users, and information indicating the target task to which the determined person in charge is associated is output.

[0006] A program according to one aspect of the present disclosure causes one or more processors to execute the task management method.

[0007] A task management system according to one aspect of the present disclosure includes a processing unit and a communication unit. The processing unit determines a person in charge of a target task to be performed by one of a plurality of users based on condition information indicating conditions related to each of the tasks of the plurality of users. The communication unit outputs information indicating the target task to which the person in charge determined by the processing unit is associated.

[0008] The present disclosure has an advantage in that it is easy to reduce the burden of managing tasks performed by a user who uses a device.

[0009] FIG. 1 is a block diagram showing an overall configuration including a task management system according to embodiment 1. FIG. 2 is a schematic diagram showing an example of an executable operation of the task management system according to embodiment 1. FIG. 3 is a schematic diagram showing another example of an executable operation of the task management system according to embodiment 1. FIG. 4 is a flowchart showing an example of a basic operation of the task management system according to embodiment 1. FIG. 5 is a schematic diagram showing a first operation example of the task management system according to embodiment 1. FIG. 6 is a schematic diagram showing an example of notifying a user of a registered task in the first operation example of the task management system according to embodiment 1. FIG. 7 is a schematic diagram showing an example of a user acquiring list information in the first operation example of the task management system according to embodiment 1. FIG. 8 is a schematic diagram showing an example of list information that can be acquired for each group in the first operation example of the task management system according to embodiment 1. FIG. 9 is a schematic diagram showing a second operation example of the task management system according to embodiment 1. FIG. 10 is a schematic diagram showing a third operation example of the task management system according to embodiment 1. FIG. 11 is a schematic diagram showing a fourth operation example of the task management system according to embodiment 1. FIG. 12 is a schematic diagram showing another registration method in the fourth operation example of the task management system according to embodiment 1. FIG. 13 is a schematic diagram showing a fifth operation example of the task management system according to embodiment 1. FIG. 14 is a schematic diagram showing a fifth operation example of the task management system according to embodiment 1. FIG. 15 is a schematic diagram showing an example of a case in which another user cannot change the person in charge of a task in the fifth operation example of the task management system according to embodiment 1. FIG. 16 is a schematic diagram showing an example of a case in which another user can change the person in charge of a task in the fifth operation example of the task management system according to embodiment 1. FIG. 17 is a schematic diagram showing another example of a case in which another user can change the person in charge of a task in the fifth operation example of the task management system according to embodiment 1. FIG. 18 is a schematic diagram showing yet another example of a case in which another user can change the person in charge of a task in the fifth operation example of the task management system according to embodiment 1. FIG. 19 is a schematic diagram showing a sixth operation example of the task management system according to embodiment 1. FIG. 20 is a schematic diagram showing a seventh operation example of the task management system according to embodiment 1.FIG. 21 is a schematic diagram showing an eighth operation example of the task management system according to embodiment 1. FIG. 22 is a schematic diagram showing an example of deleting a task after a certain time period in the eighth operation example of the task management system according to embodiment 1. FIG. 23 is a schematic diagram showing an example of deleting all tasks at a specified time in the eighth operation example of the task management system according to embodiment 1. FIG. 24 is a schematic diagram showing a ninth operation example of the task management system according to embodiment 1. FIG. 25 is a schematic diagram showing an example of an executable operation of the task management system according to embodiment 2. FIG. 26 is a schematic diagram showing an example of list information. FIG. 27 is a flowchart showing an example of a basic operation of the task management system according to embodiment 2. FIG. 28 is a schematic diagram showing a first operation example of the task management system according to embodiment 2. FIG. 29 is a schematic diagram showing an example of determining a person in charge by referring to points in the first operation example of the task management system according to embodiment 2. FIG. 30 is a schematic diagram showing a second operation example of the task management system according to embodiment 2. FIG. 31 is a schematic diagram showing a third operation example of the task management system according to embodiment 2. FIG. 32 is a schematic diagram showing a fourth operation example of the task management system according to embodiment 2. FIG. 33 is a schematic diagram showing a fifth operation example of the task management system according to embodiment 2. FIG. 34 is a schematic diagram showing a sixth operation example of the task management system according to embodiment 2. FIG. 35 is a schematic diagram showing an example of an operation that can be performed by the task management system according to embodiment 3. FIG. 36 is a diagram showing an example of generation of pattern information. FIG. 37 is a diagram showing another example of generation of pattern information. FIG. 38 is a schematic diagram showing an example of notification of emergency notification information in the task management system according to embodiment 3. FIG. 39 is a flowchart showing an example of a basic operation of the task management system according to embodiment 3. FIG. 40 is a schematic diagram showing a first operation example of the task management system according to embodiment 3. FIG. 41 is a schematic diagram showing an example of a case where a determined urgent task is not registered in the first operation example of the task management system according to embodiment 3. FIG. 42 is a schematic diagram showing an example of a case where a determined urgent task is registered in the first operation example of the task management system according to embodiment 3. FIG. 43 is a schematic diagram showing a second operation example of the task management system according to embodiment 3.FIG. 44 is a schematic diagram showing an example of a notification destination of emergency notification information in the task management system according to the third embodiment.

[0010] First, the inventor's point of view will be explained below.

[0011] Conventionally, there are techniques for managing tasks, such as housework, to be performed by a user and for sharing the existence of such tasks among multiple users. For example, Patent Literature 1 discloses a technique for creating a housework schedule by a user specifying the type, time, and location of housework to be performed by a household robot.

[0012] However, with the above-mentioned technology, in order to register, update, or delete a task to be managed, the user must manually operate a UI (User Interface) provided by an application, etc., which has the problem that the burden of managing tasks tends to be heavy for the user.

[0013] In view of the above, the inventors have come up with the present disclosure.

[0014] Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. However, more detailed explanation than necessary may be omitted. For example, detailed explanation of well-known matters or redundant explanation of substantially the same configuration may be omitted. This is to avoid unnecessary redundancy in the following explanation and to facilitate understanding by those skilled in the art.

[0015] The inventors have provided the accompanying drawings and the following description to enable those skilled in the art to fully understand the present disclosure, and do not intend for them to limit the subject matter described in the claims.

[0016] (First Embodiment) [1-1. Overall Configuration] First, an overall configuration including a task management system 100 according to the first embodiment will be described with reference to FIG. 1. FIG. 1 is a block diagram showing the overall configuration including the task management system 100 according to the first embodiment. In the first embodiment, the task management system 100 is a system for managing one or more tasks related to a device 2. A user U1 (see FIG. 2 or FIG. 3) can use an information processing terminal 3 to obtain from the task management system 100 a list of one or more tasks (hereinafter referred to as a "task list") managed in a storage device 13 (described later). Furthermore, the user U1 can receive a notification from the task management system 100, via the information processing terminal 3, that there has been a change in one or more tasks managed in the storage device 13.

[0017] The device 2 is a device capable of communicating with the server 1 (task management system 100) via a network N1 such as the Internet. In the first embodiment, the device 2 is an IoT (Internet of Things) device. The device 2 is, for example, a home appliance. Specifically, the device 2 is, for example, a washing machine, an air conditioner, a humidifier, an air purifier, a microwave oven, a refrigerator, a rice cooker, a robot vacuum cleaner, a stationary television receiver, a portable television receiver, or the like. The device 2 is also, for example, a Blu-ray Disc (registered trademark) recorder, a DVD (Digital Versatile Disc) (registered trademark) recorder, a lighting fixture, an intercom system, an electric toothbrush, a weighing scale, or a hair dryer.

[0018] A task is an action performed by a user U1 who uses the appliance 2. In the first embodiment, the task may be any task related to the appliance 2, and may include an action that the user U1 directly performs on the appliance 2, such as taking laundry out of the washing machine, as well as an action that the user U1 indirectly performs on the appliance 2, such as purchasing detergent to use in the washing machine. Furthermore, the task is not limited to household chores such as cleaning with a cleaning robot, doing laundry with a washing machine, or cooking rice with a rice cooker, i.e., tasks related to actions for managing daily life at home, but may also include tasks related to actions that the user U1 personally performs in daily life, such as brushing teeth with an electric toothbrush or measuring weight with a scale.

[0019] The information processing terminal 3 is a terminal owned by the user U1, such as a smartphone, a tablet terminal, or a desktop or laptop personal computer. In the first embodiment, the user U1 can issue instructions to the task management system 100 and obtain information sent from the task management system 100 by executing an application for the task management system 100 that is installed on the information processing terminal 3.

[0020] In addition, user U1 can also issue instructions to task management system 100 and obtain information sent from task management system 100 by accessing a URL (Uniform Resource Locator) for task management system 100 using a web browser installed on information processing terminal 3.

[0021] [1-2. Task Management System] Next, details of the task management system 100 will be described. As shown in FIG. 1 , the task management system 100 includes a communication unit 11, a processing unit 12, and a storage device 13. Note that, although the task management system 100 includes the storage device 13 in the first embodiment, the storage device 13 does not have to be a component of the task management system 100.

[0022] In the first embodiment, the task management system 100 is realized by a server 1. The server 1 has a processor and a memory, and realizes each component of the task management system 100 by causing the processor to execute a computer program stored in the memory.

[0023] The task management system 100 is configured to be able to communicate with the device 2 and the information processing terminal 3 via the network N1. In the example shown in Fig. 1, there is one device 2 and one information processing terminal 3, but there may be multiple devices 2 and multiple information processing terminals 3.

[0024] The communication unit 11 is a communication interface for communicating with each of the device 2 and the information processing terminal 3 via the network N1. The communication unit 11 communicates with the device 2 to acquire a log relating to the state of the device 2. Hereinafter, the communication unit 11 will also be referred to as the acquisition unit 11.

[0025] In the first embodiment, the acquisition unit (communication unit) 11 acquires the log by receiving a signal including the log acquired by the device 2, which is transmitted from the device 2 via the network N1. The acquisition unit 11 may also acquire the log by communicating with an external system (not shown) that manages the device 2. In this case, the acquisition unit 11 acquires the log by receiving a signal including the log acquired from the device 2, which is transmitted from the external system via the network N1.

[0026] Here, the log may include, as information indicating the state of the device 2, information indicating an operation performed by the device 2 or information indicating an operation accepted by the device 2. Furthermore, the operation performed by the device 2 may include not only an operation performed by the device 2 itself but also an operation performed by a device such as a sensor provided in the device 2.

[0027] For example, if device 2 is a washing machine with a function to automatically dispense detergent, the log may include information indicating the remaining amount of detergent. Also, for example, if device 2 is a washing machine with a function to determine the state of a filter, the log may include information indicating the state of the filter. Also, for example, if device 2 is a refrigerator, the log may include information indicating the remaining amount of water in the water tank. Also, for example, if device 2 is a refrigerator with a function to recognize ingredients present in the refrigerator, the log may include information indicating the remaining amount of ingredients in the refrigerator.

[0028] The processing unit 12 determines a task to be executed by the user U1 who uses the device 2, based on the log acquired by the acquisition unit (communication unit) 11. In the first embodiment, the processing unit 12 determines a task corresponding to the log by referring to first correspondence information stored in a task determination DB (Database) 132 (described later) of the storage device 13.

[0029] The first correspondence information is information indicating the correspondence between a log and a task. Specifically, the first correspondence information is information indicating the correspondence between the device 2 that generated the log, the content of the log generated by the device 2, and the content of the task that user U1 should perform based on the content of the log. For example, if the device 2 that generated the log is a washing machine, the first correspondence information may include information linking the content of the log indicating that the detergent is running low with the content of the task that user U1 should perform to refill the detergent. Furthermore, if the device 2 that generated the log is a washing machine, the first correspondence information may include information linking the content of the log indicating that the detergent is running low with the content of the task that user U1 should perform to buy detergent.

[0030] As described above, the tasks may include tasks that user U1 performs directly on appliance 2, such as refilling the washing machine with detergent, as well as tasks that user U1 performs indirectly on appliance 2, such as going to buy detergent to refill the washing machine.

[0031] In addition, in embodiment 1, the processing unit 12 executes a process of registering the determined task in the storage device 13 (task DB 131) (described later), or a process of updating a task registered in the storage device 13 (task DB 131) with the determined task.

[0032] For example, if the type of the determined task is different from one or more task types registered in the storage device 13 (task DB 131), the processing unit 12 registers the determined task in the storage device 13. In other words, if the determined task is a new task different from the managed tasks, the processing unit 12 registers the determined task in the storage device 13 as a new task.

[0033] Furthermore, for example, if the type of the determined task is the same as the type of any one of one or more tasks registered in the storage device 13 (task DB 131), the processing unit 12 updates the content of the task to the content of the determined task. In other words, if the determined task is the same as a task already managed, the processing unit 12 updates the content of the task by overwriting it with the content of the determined task.

[0034] Furthermore, in the first embodiment, when a change occurs in one or more tasks registered in the storage device 13 (task DB 131), the processing unit 12 transmits notification information indicating the change to the information processing terminal 3 used by the user U1. The change here may include, for example, the above-mentioned case where a new task is registered in the storage device 13, or the content of an already managed task is updated.

[0035] In addition, in embodiment 1, when the communication unit 11 receives request information requesting the transmission of a task list from the information processing terminal 3, the processing unit 12 transmits list information indicating the task list registered in the storage device 13 to the information processing terminal 3.

[0036] The storage device 13 stores one or more tasks. The one or more tasks stored (registered) in the storage device 13 are managed by the task management system 100. In the first embodiment, the one or more tasks stored in the storage device 13 may include, in addition to a task determined by the processing unit 12, a task registered by the user U1 using the information processing terminal 3, as will be described later.

[0037] In the first embodiment, the storage device 13 includes a task DB 131, a task determination DB 132, and a task deletion DB 133. The storage device 13 also includes a task selection DB 134 (described later) and a task update DB 135 (described later).

[0038] As described above, the task DB 131 stores one or more tasks to be managed by the task management system 100. The task determination DB 132 stores first correspondence information that is referenced when the processing unit 12 determines a task.

[0039] The task deletion DB 133 stores second correspondence information that is referenced by the processing unit 12 when deleting one of one or more tasks registered in the storage device 13 (task DB 131). The second correspondence information is information indicating the correspondence between a log and a task to be deleted. Specifically, the second correspondence information is information indicating the correspondence between the device 2 that generated the log, the content of the log generated by the device 2, and the content of the task to be deleted based on the content of the log. For example, if the device 2 that generated the log is a washing machine, the second correspondence information may include information linking the content of the log indicating that the detergent is running low with the content of the task to be deleted, in which user U1 refills the detergent. Furthermore, if the device 2 that generated the log is a washing machine, the second correspondence information may include information linking the content of the log indicating that the detergent is running low with the content of the task to be deleted, in which user U1 goes to buy detergent.

[0040] 2 is a schematic diagram showing an example of an executable operation of the task management system 100 according to the first embodiment. As shown in FIG. 2, the task management system 100 (1) acquires a log from the device 2, (2) determines a task based on the log, and registers the determined task in the task DB 131 or updates an existing task with the determined task. Then, the task management system 100 (3) transmits notification information indicating that the task has been registered or updated to the information processing terminal 3 of the user U1. The example shown in FIG. 2 indicates that there are multiple users U1, and notification information is transmitted to the information processing terminal 3 of each of the multiple users U1.

[0041] Furthermore, when the task management system 100 (4) acquires request information transmitted from the information processing terminal 3 of any one of the users U1, (5) it transmits list information to the information processing terminal 3 in question.

[0042] The task management system 100 according to the first embodiment can also perform the following operations. FIG. 3 is a schematic diagram illustrating another example of an operation that can be performed by the task management system 100 according to the first embodiment. As illustrated in FIG. 3 , the task management system 100 (1) acquires operation information from the information processing terminal 3 of user U1, and (2) registers a task in the task DB 131 or updates an existing task based on the operation information. Here, the operation information is information input by user U1 operating the information processing terminal 3, and includes, for example, information requesting registration of a task desired by user U1 or information requesting update of a task desired by user U1. Then, the task management system 100 (3) transmits notification information indicating that a task has been registered or updated to the information processing terminal 3 of user U1. The example illustrated in FIG. 3 illustrates that there are one or more users U1 other than the user U1 who transmits the operation information, and the notification information is transmitted to the information processing terminals 3 of all users U1. Furthermore, when the task management system 100 (4) acquires request information transmitted from the information processing terminal 3 of any one of the users U1, (5) it transmits list information to the information processing terminal 3 in question.

[0043] [2. Operation] The operation of the task management system 100 according to the first embodiment (that is, the task management method) will be described in detail below.

[0044] [2-1. Example of Basic Operation] First, an example of basic operation of the task management system 100 according to the first embodiment will be described with reference to Fig. 4. Fig. 4 is a flowchart showing an example of basic operation of the task management system 100 according to the first embodiment. Here, the task management system 100 will be described as acquiring a log from the device 2. Also, here, the description will be given assuming that there is one user U1.

[0045] When a log is generated in the device 2, the device 2 transmits a signal including the generated log to the server 1 (task management system 100) via the network N1. As a result, the communication unit (acquisition unit) 11 acquires the log via the network N1 (S1).

[0046] Next, the processing unit 12 determines a task based on the log acquired by the communication unit (acquisition unit) 11 (S2). Here, the processing unit 12 determines a task corresponding to the content of the log by referring to the first correspondence information stored in the storage device 13 (task determination DB 132).

[0047] If the determined task is a new task (S3: Yes), the processing unit 12 registers the determined task in the storage device 13 (task DB 131) (S4). If the determined task is an existing task (S3: No), the processing unit 12 updates the content of the existing task by overwriting it with the content of the determined task (S5).

[0048] Thereafter, the processing unit 12 transmits notification information indicating that a change has occurred in one or more tasks registered in the storage device 13 (task DB 131) to the information processing terminal 3 of the user U1 via the network N1 (S6).

[0049] The following are specific examples of operations that can be performed by the task management system 100 according to embodiment 1. Note that the task management system 100 may perform an appropriate combination of the following first to ninth operation examples.

[0050] [2-2. First Operation Example] First, a first operation example of the task management system 100 according to the first embodiment will be described with reference to Fig. 5. Fig. 5 is a schematic diagram showing the first operation example of the task management system 100 according to the first embodiment. The first operation example is a specific example of processing in which the processing unit 12 determines a task based on a log acquired by the communication unit (acquisition unit) 11, and registers the determined task in the storage device 13 (task DB 131).

[0051] In the example shown in FIG. 5 , the processing unit 12 acquires a log indicating "low detergent remaining" from the washing machine, which is the device 2. Then, the processing unit 12 determines a task based on the acquired log by referring to the first correspondence information stored in the storage device 13 (task determination DB 132). Here, the processing unit 12 determines a task of "refill detergent" and a task of "shopping (detergent)" that correspond to the log of "low detergent remaining". Then, the processing unit 12 registers the determined task of "refill detergent" and task of "shopping (detergent)" in the storage device 13 (task DB 131).

[0052] As described above, in the first operation example, the processing unit 12 automatically registers a task based on the acquired log, so that the user U1 does not need to manually register a task.

[0053] 6 is a schematic diagram showing an example of notification of registered tasks to user U1 in a first operation example of the task management system 100 according to the first embodiment. In the example shown in FIG. 6, the processing unit 12 transmits notification information indicating that the tasks "refill detergent" and "shopping (detergent)" have been registered to the information processing terminal 3 of user U1. Upon receiving the notification information, the information processing terminal 3 of user U1 displays the notification information on the display via an instant messenger application such as LINE (registered trademark). This allows user U1 to know that new tasks have been registered.

[0054] The information processing terminal 3 may display the notification information on a display via, for example, an application dedicated to the task management system 100 or an application dedicated to the device 2. The information processing terminal 3 may also output the notification information by voice via a built-in speaker.

[0055] FIG. 7 is a schematic diagram illustrating an example in which user U1 acquires list information in a first operation example of the task management system 100 according to the first embodiment. In the example illustrated in FIG. 7, user U1 operates the information processing terminal 3 to transmit request information requesting the transmission of a task list to the task management system 100. Upon receiving the request information, the processing unit 12 reads one or more tasks registered in the storage device 13 (task DB 131). In this example, the processing unit 12 reads the washing machine task "refill detergent" and the "shopping (detergent)" task. The processing unit 12 then transmits list information including the one or more read tasks to the information processing terminal 3. Upon receiving the list information, user U1's information processing terminal 3 displays the list information on a display via, for example, an instant messenger application. This allows user U1 to grasp the one or more registered tasks.

[0056] The list information includes, for each of one or more registered tasks, information such as the name of the task, task details, the source of the task, the person assigned to the task, and the difficulty level of the task. For example, the list information shown in Figure 7 includes the name of the task "Shopping (detergent)," the content of the task "Please buy a detergent refill (XXX)," the source of the task "Requester: Washing Machine," a question mark icon indicating that no person is assigned to the task, and the difficulty level of the task "QP: 4." The list information shown in Figure 7 also includes the name of a group "△△△" and one or more icons representing one or more members of the group to which user U1 belongs.

[0057] Here, if there are multiple users U1 and each of the multiple users U1 belongs to one of multiple groups, the notification information and list information may have different contents for each of the multiple groups. Specific examples of list information that can be acquired for each of the multiple groups will be described below.

[0058] 8 is a schematic diagram illustrating an example of list information that can be acquired for each group in a first operation example of the task management system 100 according to the first embodiment. In the example illustrated in FIG. 8, three users U1, "User A," "User B," and "User C," belong to "Group A," one user U1, "User D," belongs to "Group B," and one user U1, "User E," belongs to "Group C." Furthermore, "Group A" and "Group B" are related groups, but "Group C" is a group unrelated to either "Group A" or "Group B." As a specific example, if "Group A" is an arbitrary family, "Group B" would be, for example, family members who are relatives or friends of the family, and "Group C" would be third parties.

[0059] 8, when "User A" is used as a reference, "User A" can obtain and view list information including the contents of one or more tasks for which "User A" is responsible. Also, "User B" and "User C," who belong to the same "Group A" as "User A," can obtain and view list information including the contents of one or more tasks performed by "Group A."

[0060] Because "User D" belongs to a different group than "Group A," he or she cannot obtain and view list information including the contents of one or more tasks performed by "Group A." However, because "User D" belongs to "Group B," which is related to "Group A," he or she can obtain and view list information including a summary of one or more tasks performed by "Group A." In the example shown in FIG. 8 , the summary includes information indicating the number of completed tasks performed by "Group A" and the number of completed tasks performed by "Group B." Note that the summary can also be obtained and viewed by "User A," "User B," and "User C," who belong to "Group A."

[0061] "User E" belongs to a group that is different from "Group A" and is unrelated to "Group A," and therefore cannot obtain and view list information related to "Group A."

[0062] Note that notification information regarding "Group A" is sent to the information processing terminal 3 of each of "User A," "User B," and "User C" who belong to "Group A," but is not sent to the information processing terminal 3 of each of "User D" who belongs to "Group B" and "User E" who belongs to "Group C."

[0063] [2-3. Second Operation Example] Next, a second operation example of the task management system 100 according to the first embodiment will be described with reference to Fig. 9. Fig. 9 is a schematic diagram showing the second operation example of the task management system 100 according to the first embodiment. The second operation example differs from the first operation example in that the processing unit 12 determines a task by referring to necessity information indicating whether or not automatic registration of a task set in advance by the user U1 is necessary.

[0064] 9 , before the processing unit 12 acquires a log from the washing machine, which is the device 2, the user U1 operates the information processing terminal 3 to send necessity information to the task management system 100. Upon acquiring the necessity information, the processing unit 12 updates the first correspondence information stored in the storage device 13 (task determination DB 132) based on the acquired necessity information. Here, the processing unit 12 updates the first correspondence information so as to set the "registration necessity" of the task "shopping (detergent)" to "not required" and the "registration necessity" of the task "refill detergent" to "required."

[0065] Thereafter, similarly to the first operation example, the processing unit 12 acquires a log indicating "low detergent remaining" from the washing machine, which is the device 2. Then, the processing unit 12 determines a task based on the acquired log by referring to the first correspondence information stored in the storage device 13 (task determination DB 132). Here, the processing unit 12 determines a task of "refill detergent" that corresponds to the log of "low detergent remaining" and for which "registration required" is set to "required." Then, the processing unit 12 registers the determined task of "refill detergent" in the storage device 13 (task DB 131).

[0066] As described above, in the second operation example, it is possible to automatically register only the tasks desired by the user U1 in the storage device 13 (task DB 131).

[0067] [2-4. Third Operation Example] Next, a third operation example of the task management system 100 according to the first embodiment will be described with reference to Fig. 10. Fig. 10 is a schematic diagram showing the third operation example of the task management system 100 according to the first embodiment. The third operation example differs from the second operation example in that the user U1 operates the information processing terminal 3 to manually register a task that is to be automatically registered.

[0068] 10 , before the processing unit 12 acquires a log from the washing machine, which is the device 2, the user U1 operates the information processing terminal 3 to send operation information indicating the task "check stock detergent" corresponding to the log of "low detergent remaining" of the washing machine to the task management system 100. When the processing unit 12 acquires the operation information, it updates the first correspondence information stored in the storage device 13 (task determination DB 132) based on the acquired operation information. Here, the processing unit 12 updates the first correspondence information to add the task "check stock detergent" corresponding to the log of "low detergent remaining" of the washing machine.

[0069] Thereafter, similarly to the second operation example, the processing unit 12 acquires a log indicating "low detergent remaining" from the washing machine, which is the device 2. Then, the processing unit 12 determines a task based on the acquired log by referring to the first correspondence information stored in the storage device 13 (task determination DB 132). Here, the processing unit 12 determines a "refill detergent" task and a "check stocked detergent" task that correspond to the log indicating "low detergent remaining" and for which "registration required" is set to "required." Then, the processing unit 12 registers the determined "refill detergent" task and "check stocked detergent" task in the storage device 13 (task DB 131).

[0070] As described above, in the third operation example, the user U1 can manually set the tasks to be automatically registered.

[0071] [2-5. Fourth Operation Example] Next, a fourth operation example of the task management system 100 according to the first embodiment will be described with reference to Fig. 11. Fig. 11 is a schematic diagram showing the fourth operation example of the task management system 100 according to the first embodiment. The fourth operation example differs from the first to third operation examples in that the user U1 manually registers a task by operating the information processing terminal 3.

[0072] 11 , user U1 operates information processing terminal 3 to send operation information indicating that the source device 2 is "refrigerator" and the task is "shopping (eggs)" to task management system 100. Upon acquiring the operation information, processing unit 12 updates one or more tasks stored in storage device 13 (task DB 131) based on the acquired operation information. In this example, processing unit 12 updates one or more tasks to add a task "shopping (eggs)" for which the source device 2 is "refrigerator."

[0073] In addition, if the task management system 100 stores one or more tasks that occur relatively frequently, the processing unit 12 may send selection information indicating a list of the one or more tasks to the information processing terminal 3 of the user U1.

[0074] 12 is a schematic diagram illustrating another registration method in a fourth operation example of the task management system 100 according to the first embodiment. In the example illustrated in FIG. 12 , the storage device 13 includes a task selection DB 134 that stores selection information. Then, upon receiving operation information requesting transmission of selection information from the information processing terminal 3 of, for example, user U1, the processing unit 12 transmits the selection information to the information processing terminal 3. By operating the information processing terminal 3, user U1 transmits operation information indicating that "Shopping (Eggs)" has been selected from the selection information to the task management system 100. Upon receiving the operation information, the processing unit 12 updates one or more tasks stored in the storage device 13 (task DB 131) based on the received operation information to add a task called "Shopping (Eggs)" whose source device 2 is the "Refrigerator."

[0075] As described above, in the fourth operation example, the user U1 can manually register a desired task.

[0076] 13 and 14, a fifth operation example of the task management system 100 according to the first embodiment will be described. Both of FIGS. 13 and 14 are schematic diagrams showing the fifth operation example of the task management system 100 according to the first embodiment. The fifth operation example differs from the first to fourth operation examples in that the user U1 manually assigns a person in charge of a task by operating the information processing terminal 3.

[0077] In the example shown in FIG. 13 , user U1 operates the information processing terminal 3 to send request information requesting the transmission of a task list to the task management system 100. Upon receiving the request information, the processing unit 12 sends the list information to the information processing terminal 3. Upon receiving the list information, the information processing terminal 3 of user U1 displays the list information on a display via, for example, an instant messenger application. In this example, the list information includes a task for "replenish detergent" for the washing machine and a task for "shopping (detergent)," but no person is assigned to either task.

[0078] Here, as shown in FIG. 14 , user U1 operates the information processing terminal 3 to send operation information to the task management system 100 requesting that the person in charge of the task "Shopping (detergent)" be changed to "Dad," which is user U1 himself. Upon acquiring the operation information, the processing unit 12 updates one or more tasks stored in the storage device 13 (task DB 131) based on the acquired operation information. Here, the processing unit 12 updates one or more tasks so as to change the person in charge of the task "Shopping (detergent)" to "Dad." Thereafter, in the list information, "Dad" is assigned to the task "Shopping (detergent)" for the washing machine.

[0079] As described above, in the fifth operation example, the user U1 can manually set the person in charge of the task.

[0080] Incidentally, when a person in charge has already been assigned to a given task, the task management system 100 may restrict changing the person in charge of the task as follows. In the following description, the user U1 who is already assigned to a given task will be referred to as the "first user U11," and the other user U1 will be referred to as the "second user U12." In the following description, the first user U11 will be referred to as "Dad," and the second user U12 will be referred to as "Mom."

[0081] 15 is a schematic diagram showing an example in which another user U1 (second user U12) cannot change the person in charge of the task in the fifth operation example of the task management system 100 according to embodiment 1. In the example shown in Fig. 15, as in the example shown in Fig. 14, the person in charge of the task of "shopping (detergent)" for the washing machine is "Dad", who is the first user U11.

[0082] Thereafter, the second user U12 operates the information processing terminal 3 to send operation information to the task management system 100 requesting that the person in charge of the "Shopping (detergent)" task be changed to "Mom," the second user U12. The processing unit 12 then does not execute processing to change the person in charge of the "Shopping (detergent)" task, because the first user U11, "Dad," is already assigned as the person in charge of the "Shopping (detergent)" task. The processing unit 12 then sends information indicating that the person in charge of the "Shopping (detergent)" task cannot be changed to the information processing terminal 3 of the second user U12. This allows the second user U12 to understand that a person in charge has already been assigned to the "Shopping (detergent)" task and that the person in charge cannot be changed.

[0083] Incidentally, the task management system 100 may permit a change of the person in charge of a given task if a predetermined condition is met, even if a person in charge has already been assigned to that task. In other words, if the first user U11 is assigned as the person in charge of one or more tasks stored in the storage device 13, the processing unit 12 may permit a change of the person in charge of the task from the first user U11 to the second user U12 if a second condition is met.

[0084] 16 is a schematic diagram illustrating an example in which another user (second user U12) can change the task assignment in a fifth operation example of the task management system 100 according to the first embodiment. In the example shown in FIG. 16, the second condition is that a predetermined time (unchangeable period) has elapsed since the first user U11 was assigned to a given task. The unchangeable period may be set in advance or may be set appropriately by the user U1 operating the information processing terminal 3.

[0085] As shown in FIG. 16 , if the second user U12 requests the task management system 100 to change the person in charge of the "Shopping (detergent)" task to "Mom," the second user U12 herself, during the non-changeable period, the processing unit 12 prohibits the change of the person in charge of the task. On the other hand, if the second user U12 requests the task management system 100 to change the person in charge of the "Shopping (detergent)" task to "Mom," the second user U12 herself, after the non-changeable period has elapsed, the processing unit 12 changes the person in charge of the task to "Mom." Then, the processing unit 12 transmits information indicating that the person in charge of the "Shopping (detergent)" task has been changed to "Mom" to the information processing terminal 3 of the second user U12. This allows the second user U12 to understand that the person in charge of the "Shopping (detergent)" task has been changed to herself.

[0086] Note that the task management system 100 may allow a change of the person in charge of a given task, even if the person in charge has already been assigned to that task, regardless of whether the second condition is met.

[0087] FIG. 17 is a schematic diagram illustrating another example in which another user (second user U12) can change the person in charge of a task in the fifth operation example of the task management system 100 according to the first embodiment. As shown in FIG. 17 , when the second user U12 requests the task management system 100 to change the person in charge of the "Shopping (detergent)" task to "Mom," the second user U12, the processing unit 12 changes the person in charge of the task to "Mom" regardless of whether the second condition is satisfied. Then, the processing unit 12 transmits information indicating that the person in charge of the "Shopping (detergent)" task has been changed to "Mom" to the information processing terminal 3 of the second user U12. This allows the second user U12 to understand that the person in charge of the "Shopping (detergent)" task has been changed to himself.

[0088] In addition, when the task management system 100 receives operation information sent from the information processing terminal 3 of the second user U12 requesting a change of the person in charge of a task to which a person in charge has already been assigned, the task management system 100 may send confirmation information to the information processing terminal 3 to confirm with the second user U12 whether or not to actually change the person in charge.

[0089] FIG. 18 is a schematic diagram illustrating yet another example in which another user (second user U12) can change the person in charge of a task in the fifth operation example of the task management system 100 according to embodiment 1. When the second user U12 requests the task management system 100 to change the person in charge of the task "Shopping (detergent)" to "Mom," the second user U12 himself, the processing unit 12 transmits confirmation information to the information processing terminal 3. When the information processing terminal 3 acquires the confirmation information, the second user U12 operates the information processing terminal 3 to transmit information indicating his or her intention to "change" to the task management system 100. The processing unit 12 then changes the person in charge of the task to "Mom." The processing unit 12 then transmits information indicating that the person in charge of the task "Shopping (detergent)" has been changed to "Mom" to the information processing terminal 3 of the second user U12.

[0090] Note that the task management system 100 may not permit unlimited changes to the person in charge of a task, but may limit the number of times that the person in charge of a task is permitted to be changed within a predetermined period (e.g., several hours or several days).

[0091] [2-7. Sixth Operation Example] Next, a sixth operation example of the task management system 100 according to the first embodiment will be described with reference to Fig. 19. Fig. 19 is a schematic diagram showing the sixth operation example of the task management system 100 according to the first embodiment. The sixth operation example differs from the first to fifth operation examples in that the processing unit 12 determines a completed task from among one or more tasks registered in the storage device 13 (task DB 131) based on a log acquired by the communication unit (acquisition unit) 11, and automatically updates the status of the task to "completed."

[0092] 19 , processing unit 12 acquires a log indicating “remaining detergent amount (large)” from a washing machine, which is device 2. Then, processing unit 12 determines whether the task is completed based on the acquired log by referring to the second correspondence information stored in storage device 13 (task update DB 135).

[0093] The second correspondence information is information indicating the correspondence between the log and the task whose status is to be updated to "completed." Specifically, the second correspondence information is information indicating the correspondence between the device 2 that generated the log, the status of the device 2, and the content of the task that should be updated to "completed" based on the content of the log. In this case, the processing unit 12 determines that the "Shopping (detergent)" task and the "Detergent Refill" task corresponding to the log of "Detergent Remaining (Large)" are completed tasks. Then, the processing unit 12 updates the status of the "Detergent Refill" task, which has a status of "In Progress" among one or more tasks registered in the storage device 13 (task DB 131), to "Completed."

[0094] As described above, in the sixth operation example, the processing unit 12 automatically updates the status of a completed task to "completed" based on the acquired log, so that the user U1 does not have to manually change the status of the task to "completed."

[0095] [2-8. Seventh Operation Example] Next, a seventh operation example of the task management system 100 according to the first embodiment will be described with reference to Fig. 20. Fig. 20 is a schematic diagram showing the seventh operation example of the task management system 100 according to the first embodiment. The seventh operation example differs from the first to sixth operation examples in that the user U1 manually updates the status of the task to "completed" by operating the information processing terminal 3.

[0096] 20 , the user U1 operates the information processing terminal 3 to send operation information indicating that the task "Shopping (detergent)" has been completed to the task management system 100. Upon acquiring the operation information, the processing unit 12 updates one or more tasks stored in the storage device 13 (task DB 131) based on the acquired operation information. In this example, the processing unit 12 updates one or more tasks so as to change the status of the task "Shopping (detergent)" for which the source device 2 is the "washing machine" from "in progress" to "completed."

[0097] As described above, in the seventh operation example, the user U1 can manually update the status of a completed task to "completed."

[0098] [2-9. Eighth Operation Example] Next, an eighth operation example of the task management system 100 according to the first embodiment will be described with reference to Fig. 21. Fig. 21 is a schematic diagram showing the eighth operation example of the task management system 100 according to the first embodiment. The eighth operation example differs from the first to seventh operation examples in that the processing unit 12 determines a task to be deleted from one or more tasks registered in the storage device 13 (task DB 131) based on a log acquired by the communication unit (acquisition unit) 11, and automatically deletes the determined task to be deleted from the storage device 13.

[0099] In other words, when any one of the one or more tasks registered in the storage device 13 (task DB 131) satisfies a predetermined condition (first condition), the processing unit 12 deletes the task from the storage device 13. The first condition includes determining that the task has been completed based on the acquired log.

[0100] In the example shown in FIG. 21 , the processing unit 12 acquires a log indicating "detergent remaining (high)" from the washing machine, which is the device 2. Then, the processing unit 12 determines a task to be deleted based on the acquired log by referring to the second correspondence information stored in the storage device 13 (task deletion DB 133). Here, the processing unit 12 determines that the task "refill detergent" corresponding to the log indicating "detergent remaining (high)" has been completed, and determines this task as the task to be deleted. Then, the processing unit 12 deletes the determined task "refill detergent" from among one or more tasks registered in the storage device 13 (task DB 131).

[0101] As described above, in the eighth operation example, the processing unit 12 automatically deletes completed tasks based on the acquired log, so that the user U1 does not need to manually delete tasks.

[0102] Incidentally, the task management system 100 may delete a task from the storage device 13 (task DB 131) after a certain period of time (e.g., several hours or several days) has elapsed since it determined that the task was completed, rather than deleting the task from the storage device 13 at the time it determined that the task was completed.

[0103] FIG. 22 is a schematic diagram illustrating an example of deleting a task after a certain period of time in an eighth operation example of the task management system 100 according to the first embodiment. The certain period of time may be set in advance, or may be set appropriately by the user U1 operating the information processing terminal 3. In the example illustrated in FIG. 22 , when a certain period of time has elapsed since the processing unit 12 determined that the washing machine task "refill detergent" has been completed, the processing unit 12 determines the task as a task to be deleted and deletes the determined task from the storage device 13 (task DB 131). This makes it easier to avoid a situation in which the user U1 is unable to determine which tasks have been completed when viewing the list information, compared to when the task is deleted upon completion.

[0104] In addition, the task management system 100 may delete all of one or more tasks registered in the storage device 13 (task DB 131) from the storage device 13 at a predetermined time (e.g., midnight), regardless of whether the task has been completed or not.

[0105] 23 is a schematic diagram illustrating an example of deleting all tasks at a specified time (predetermined time) in an eighth operation example of the task management system 100 according to the first embodiment. The specified time may be set in advance, or may be set appropriately by the user U1 operating the information processing terminal 3. In the example shown in FIG. 23 , the processing unit 12 determines all tasks registered in the storage device 13 (task DB 131) as tasks to be deleted at the specified time, and deletes the determined tasks from the storage device 13. This eliminates the need for the user U1 to manually delete all registered tasks.

[0106] [2-10. Ninth Operation Example] Next, a ninth operation example of the task management system 100 according to the first embodiment will be described with reference to Fig. 24. Fig. 24 is a schematic diagram showing the ninth operation example of the task management system 100 according to the first embodiment. The ninth operation example differs from the first to eighth operation examples in that the user U1 manually deletes a task by operating the information processing terminal 3.

[0107] In the example shown in Fig. 24, the user U1 operates the information processing terminal 3 to send operation information indicating that the task "Shopping (Detergent)" is to be deleted to the task management system 100. Upon acquiring the operation information, the processing unit 12 updates one or more tasks stored in the storage device 13 (task DB 131) based on the acquired operation information. In this example, the processing unit 12 updates one or more tasks so as to delete the task "Shopping (Detergent)" whose source device 2 is the "Washing Machine."

[0108] As described above, in the ninth operation example, the user U1 can manually delete the status of a completed task.

[0109] [3. Advantages, etc.] The following describes advantages of the task management system 100 (task management method) according to embodiment 1. As described above, the task management system 100 (task management method) according to embodiment 1 acquires a log related to the state of the device 2 and automatically determines a task to be executed by the user U1 who uses the device 2 based on the acquired log. Therefore, the task management system 100 (task management method) according to embodiment 1 has the advantage that the user U1 does not need to manually register or update tasks in a UI provided by an application or the like, which makes it easier to reduce the burden of managing tasks.

[0110] (Embodiment 2) [1. Overview] An overview of a task management system 100A according to embodiment 2 will be described below with reference to Fig. 25. Fig. 25 is a schematic diagram showing an example of executable operations of task management system 100A according to embodiment 2. Below, explanations of points of task management system 100A according to embodiment 2 that are common to task management system 100 according to embodiment 1 will be omitted as appropriate.

[0111] In the second embodiment, the processing unit 12 of the task management system 100A determines a person in charge of a task to be performed by one of the multiple users U1 based on condition information indicating conditions related to each task of the multiple users U1. The multiple users U1 may be, for example, family members. In the second embodiment, the processing unit 12 determines a person in charge of a task by referring to the condition information stored in the storage device 13 (the task DB 131, the condition DB 136, etc.).

[0112] In the second embodiment, the task for which the processing unit 12 determines a person in charge (hereinafter also referred to as the "target task") is a task determined based on the log acquired by the acquisition unit (communication unit) 11 in the task management system 100 according to the first embodiment (i.e., a task that is automatically registered in the storage device 13 (task DB 131) or a task that is automatically updated). Of course, the task for which the processing unit 12 determines a person in charge may also include a task that is manually registered in the storage device 13 by the user U1 operating the information processing terminal 3.

[0113] The condition information indicates a condition for automatically assigning one of the users U1 to a task. The condition information may be set in advance, or may be set as appropriate by the user U1 operating the information processing terminal 3 as shown in FIG. 25 .

[0114] For example, the condition information may include information indicating the degree of execution of one or more tasks other than the target task for each of the multiple users U1. The degree of execution may include, for example, the number of times the one or more tasks have been executed, the difficulty level (points) of the one or more tasks, etc.

[0115] Furthermore, for example, the condition information may include information indicating the status of each of the multiple users U1 in charge of related tasks. The related tasks are tasks related to the target task. For example, the related tasks may include tasks related to the same device 2 as the device 2 that generated the target task, or tasks performed at the same location as the target task.

[0116] Furthermore, for example, the condition information may include information indicating the category of the task assigned to each of the multiple users U1. For example, a task called "Shopping (eggs)" and a task called "Shopping (detergent)" belong to the same category.

[0117] Furthermore, for example, the condition information may include information indicating the outcome of a game in which multiple users U1 participate, with each user betting on who will be in charge of a task. The game is a game such as roulette in which each user U1 cannot directly influence the outcome, and is executed on the information processing terminal 3 of each user U1.

[0118] As shown in FIG. 25 , the task management system 100A (1) acquires a log from the device 2, (2) determines a task based on the log, and registers the determined task in the task DB 131. Note that the tasks (1) and (2) do not have to be performed by the task management system 100A. Furthermore, the task management system 100A (3) determines a person in charge of the determined task (target task) based on condition information. Then, the task management system 100A (4) transmits notification information to the information processing terminal 3 of user U1 indicating that the task, including the person in charge, has been registered. The example shown in FIG. 25 indicates that there are multiple users U1, and notification information is transmitted to the information processing terminal 3 of each of the multiple users U1.

[0119] As in the first embodiment, when the task management system 100A receives request information transmitted from the information processing terminal 3 of any user U1, it transmits list information to the information processing terminal 3. FIG. 26 is a schematic diagram showing an example of list information. The diagram on the left side of FIG. 26 represents the list information displayed on the display of the information processing terminal 3 before a person in charge has been assigned to each task. The diagram on the right side of FIG. 26 represents the list information displayed on the display of the information processing terminal 3 after a person in charge has been assigned to each task. In the example shown in FIG. 26, the task management system 100A automatically assigns "Dad" as the person in charge of the tasks "Shopping (Detergent)" and "Refill Detergent."

[0120] [2. Operation] The operation of the task management system 100A according to the second embodiment (that is, the task management method) will be described in detail below.

[0121] [2-1. Example of Basic Operation] First, an example of the basic operation of the task management system 100A according to the second embodiment will be described with reference to Fig. 27. Fig. 27 is a flowchart showing an example of the basic operation of the task management system 100A according to the second embodiment. Here, it is assumed that steps S1 and S2 in the example of the basic operation of the task management system 100 according to the first embodiment are executed. It is also assumed here that there is one user U1.

[0122] The processing unit 12 determines a person in charge of the target task based on condition information indicating conditions related to the tasks of each of the multiple users U1 (S11). Here, the processing unit 12 determines a person in charge of the target task by referring to the condition information stored in the storage device 13 (the task DB 131, the condition DB 136, etc.).

[0123] Then, the processing unit 12 associates the determined person in charge with the target task and registers the person in charge in the storage device 13 (task DB 131) (S12). When updating the target task, the processing unit 12 may update the person in charge of the target task by overwriting it with the determined person in charge.

[0124] Thereafter, the processing unit 12 transmits notification information indicating that a change has occurred in one or more tasks registered in the storage device 13 (task DB 131) to the information processing terminal 3 of the user U1 via the network N1 (S13). That is, the communication unit 11 outputs information indicating the target task associated with the determined person in charge.

[0125] Below, specific examples of operations that can be performed by the task management system 100A according to embodiment 2 are listed. Note that in the first to sixth examples shown below, the multiple users U1 are explained as two people, "Dad" and "Mom." The task management system 100A may also perform an appropriate combination of the first to sixth examples shown below.

[0126] [2-2. First Operation Example] First, a first operation example of the task management system 100A according to the second embodiment will be described with reference to Fig. 28. Fig. 28 is a schematic diagram illustrating the first operation example of the task management system 100A according to the second embodiment. The first operation example is a specific example of processing in which the processing unit 12 determines a person in charge based on the degree of implementation of one or more tasks other than the target task for each of multiple users U1 as condition information, and associates the determined person in charge with the target task and registers the task in the storage device 13 (task DB 131).

[0127] In the example shown in FIG. 28 , the processing unit 12 determines the task (target task) of "shopping (detergent)" based on a log indicating "low detergent remaining" from the washing machine, which is the device 2. The processing unit 12 then determines the person in charge of the target task by referring to the condition information stored in the storage device 13 (task DB 131). Here, the processing unit 12 determines the person in charge of the target task by referring to the number of times each user U1 has performed one or more tasks other than the target task, which are registered in the task DB 131. Here, the number of times each user U1 has performed a task is the sum of the number of tasks that have not yet been completed (i.e., are in progress) and the number of tasks that have been completed.

[0128] Specifically, the processing unit 12 determines the user U1 who has performed the task the fewest number of times among the multiple users U1 as the person in charge of the target task. In this example, "Mom" has performed the task twice, while "Dad" has performed the task once, so the processing unit 12 determines "Dad" as the person in charge of the target task, "Shopping (Detergent)." The processing unit 12 then associates "Dad," the determined person in charge, with the target task, "Shopping (Detergent)," and registers the result in the storage device 13 (task DB 131).

[0129] Meanwhile, the processing unit 12 may determine a person in charge of a target task by referring to the points acquired by each user U1 registered in the storage device 13 (task DB 131) as shown in Fig. 29. Fig. 29 is a schematic diagram showing an example of determining a person in charge by referring to points in a first operation example of the task management system according to the second embodiment.

[0130] As already mentioned, points indicate the difficulty level of a task. That is, the processing unit 12 may determine the person in charge of the target task based on the difficulty levels of one or more tasks other than the target task. Note that the points for each task may be set in advance, or may be set appropriately by any one of the multiple users U1 operating the information processing terminal 3. Furthermore, the setting of the points for each task may be permitted only to an authorized user U1 among the multiple users U1.

[0131] In the example shown in FIG. 29 , the processing unit 12 determines a person in charge of the target task by referring to the points earned by each user U1 registered in the storage device 13 (task DB 131). Specifically, the processing unit 12 determines the user U1 who has earned the fewest points among multiple users U1 as the person in charge of the target task. In this example, since "Mom" has earned 4 + 2 = 6 points and "Dad" has earned 2 points, the processing unit 12 determines "Dad" as the person in charge of the target task, "Shopping (Detergent)." The processing unit 12 then links "Dad," the determined person in charge, to the target task, "Shopping (Detergent)," and registers the task in the storage device 13 (task DB 131).

[0132] As described above, in the first operation example, the person in charge of the target task is determined based on the degree of task implementation of each user U1, so that bias in the person in charge of each task is unlikely to occur.

[0133] [2-3. Second Operation Example] Next, a second operation example of the task management system 100A according to the second embodiment will be described with reference to FIG. 30. FIG. 30 is a schematic diagram illustrating the second operation example of the task management system 100A according to the second embodiment. The second operation example is a specific example of processing in which the processing unit 12 determines a person in charge based on the status of each related task of multiple users U1 as condition information, and associates the determined person in charge with the target task and registers the task in the storage device 13 (task DB 131). As already mentioned, a related task is a task related to the target task.

[0134] In the example shown in FIG. 30 , the processing unit 12 determines a "shopping (detergent)" task (first target task) and a "refill detergent" task (second target task) based on a log indicating "low detergent remaining" from the washing machine, which is the device 2. The processing unit 12 then determines the person in charge of each of the first target task and the second target task by referring to the condition information stored in the storage device 13 (task DB 131). Here, the processing unit 12 determines the person in charge of each of the first target task and the second target task by referring to the status of responsibility for related tasks of each user U1 registered in the task DB 131.

[0135] Specifically, the task "Shopping (eggs)" registered in the storage device 13 (task DB 131) is related to the task "Shopping (detergent)", which is the first target task, from the perspective of "shopping". Therefore, the processing unit 12 determines "Mom", who is the person in charge of the task "Shopping (eggs)", to be the person in charge of the task "Shopping (detergent)". Furthermore, the task "Shopping (detergent)", which is the first target task, is related to the task "Refill detergent", which is the second target task, from the perspective of "washing machine". Therefore, the processing unit 12 further determines "Mom", who was determined to be the person in charge of the task "Shopping (detergent)", to be the person in charge of the task "Refill detergent". Then, the processing unit 12 links the determined person in charge, "Mom", to each of the task "Shopping (detergent)", which is the first target task, and the task "Refill detergent", which is the second target task, and registers them in the storage device 13 (task DB 131).

[0136] As described above, in the second operation example, the same person can be assigned to two or more tasks that are more efficient when performed together, making it easier for the person in charge to perform the tasks efficiently.

[0137] [2-4. Third Operation Example] Next, a third operation example of the task management system 100A according to the second embodiment will be described with reference to Fig. 31. Fig. 31 is a schematic diagram illustrating the third operation example of the task management system 100A according to the second embodiment. The third operation example is a specific example of processing in which the processing unit 12 determines a person in charge based on the category of tasks assigned to each of multiple users U1 as condition information, and associates the determined person in charge with a target task and registers the task in the storage device 13 (task DB 131).

[0138] The task category may be appropriately set by any one of the multiple users U1 operating the information processing terminal 3. Furthermore, the task category may be set only by an authorized user U1 among the multiple users U1.

[0139] 31 , the processing unit 12 determines the task (target task) of "shopping (detergent)" based on a log indicating "low detergent remaining" from the washing machine, which is the device 2. The processing unit 12 then determines a person in charge of the target task by referring to the condition information stored in the storage device 13 (condition DB 136). Here, the processing unit 12 determines a person in charge of the target task by referring to the task categories assigned to each user U1 registered in the condition DB 136.

[0140] Specifically, for tasks belonging to the "shopping" category, "Dad" is responsible for 100% of the tasks, and "Mom" is not responsible for any of them. On the other hand, for tasks belonging to the "laundry" category, "Dad" is responsible for 60% of the tasks, and "Mom" is responsible for 40% of the tasks. In this case, since the target task "shopping (detergent)" belongs to the "shopping" category, the processing unit 12 determines "Dad" as the person in charge of the target task "shopping (detergent)". Then, the processing unit 12 associates "Dad", the determined person in charge, with the target task "shopping (detergent)" and registers it in the storage device 13 (task DB 131).

[0141] As described above, in the third operation example, the person in charge of the target task is determined based on the category of the task assigned to each user U1, so that dissatisfaction is unlikely to arise from the person in charge who has been assigned the target task.

[0142] [2-5. Fourth Operation Example] Next, a fourth operation example of the task management system 100A according to embodiment 2 will be described with reference to Fig. 32. Fig. 32 is a schematic diagram showing the fourth operation example of the task management system 100A according to embodiment 2. The fourth operation example is a specific example of processing that combines the second and third operation examples.

[0143] 32, the processing unit 12 determines a task of "shopping (detergent)" (first target task) and a task of "replenish detergent" (second target task) based on a log indicating "low detergent remaining" from a washing machine, which is the device 2. Then, the processing unit 12 determines a person in charge of each of the first target task and the second target task by referring to the condition information stored in the storage device 13 (task DB 131 and condition DB 136).

[0144] Here, the processing unit 12 first determines a person in charge of the first target task by referring to the status of each user U1's related tasks registered in the storage device 13 (task DB 131). Specifically, the task "Shopping (Eggs)" registered in the task DB 131 is related to the first target task, "Shopping (Detergent)," from the perspective of "shopping." Therefore, the processing unit 12 determines that "Mom," who is the person in charge of the task "Shopping (Eggs)," will be the person in charge of the task "Shopping (Detergent)."

[0145] Next, the processing unit 12 determines a person in charge of the second target task by referencing the task categories assigned to each user U1 registered in the storage device 13 (condition DB 136). Specifically, for tasks belonging to the "All" category, "Dad" is responsible for 50% and "Mom" is responsible for the other 50%. Therefore, the processing unit 12 determines "Dad" as the person in charge of the second target task, "Refill Detergent," so that the ratio of the number of tasks handled by "Dad" to the number of tasks handled by "Mom" is 50%:50%. The processing unit 12 then links "Mom," the determined person in charge, to the first target task, "Shopping (Detergent)," and also links "Dad," the determined person in charge, to the second target task, "Refill Detergent," and registers them in the storage device 13 (task DB 131).

[0146] As described above, in the fourth operation example, the same person can be assigned to two or more tasks that are more efficient when performed together, making it easier for the person in charge to perform the tasks efficiently. Also, in the fourth operation example, the person in charge of the target task is determined based on the category of the task assigned to each user U1, making it less likely that the person in charge of the target task will be dissatisfied.

[0147] [2-6. Fifth Operation Example] Next, a fifth operation example of the task management system 100A according to embodiment 2 will be described with reference to Fig. 33. Fig. 33 is a schematic diagram illustrating the fifth operation example of the task management system 100A according to embodiment 2. The fifth operation example is a specific example of processing in which the processing unit 12 determines a person in charge of a target task as condition information based on the outcome of a game in which multiple users U1 participate and bet on the person in charge, and associates the determined person in charge with the target task and registers the person in the storage device 13 (task DB 131).

[0148] As already mentioned, the game is a game such as roulette in which each user U1 cannot directly intervene in the outcome of the game, and is executed on each user U1's information processing terminal 3. Note that the game may also be a game in which each user U1 can directly intervene in the outcome of the game, such as a rock-paper-scissors game, a card game, or a board game.

[0149] 33, the processing unit 12 determines a task (target task) of "shopping (detergent)" based on a log indicating "low detergent remaining" from a washing machine, which is the device 2. Then, the processing unit 12 determines a person in charge of the target task by referring to condition information stored in the storage device 13 (task DB 131, etc.).

[0150] Specifically, the processing unit 12 causes each user U1 to play a game (here, a roulette game) on the information processing terminal 3. The processing unit 12 then determines the user U1 who wins the game (in other words, who has won) as the person in charge of the target task. The probability of winning the game (winning rate) is determined based on the number of times each user U1 has performed one or more tasks other than the target task, which are registered in the storage device 13 (task DB 131). In this example, since "Mom" has performed the task twice and "Dad" has performed the task once, the probability of winning for "Mom" is set to 33.3% (≒100-100×2 / 3)% and the probability of winning for "Dad" is set to 66.7% (≒100-100×1 / 3). The probability of winning the game may also be determined based on, for example, the points earned by each user U1.

[0151] 33, the winner of the game is "Dad," and therefore the processing unit 12 determines "Dad" as the person in charge of the target task, "Shopping (detergent)." The processing unit 12 then associates "Dad," the determined person in charge, with the target task, "Shopping (detergent)," and registers the person in charge in the storage device 13 (task DB 131).

[0152] As described above, in the fifth operation example, the person in charge of the target task is determined based on the outcome of the game, so that the person in charge who is assigned the target task is unlikely to become dissatisfied.

[0153] [2-7. Sixth Operation Example] Next, a sixth operation example of the task management system 100A according to the second embodiment will be described with reference to FIG. 34. FIG. 34 is a schematic diagram illustrating the sixth operation example of the task management system 100A according to the second embodiment. The sixth operation example differs from the first to fifth operation examples in that a person in charge of the target task has already been assigned. The sixth operation example is a specific example of processing in which the processing unit 12 re-determines a person in charge of the target task based on environmental information indicating a change in the environment in which the target task is placed.

[0154] The environmental information may include information indicating a change in weather at the location where the target task is to be performed, such as a change from sunny to rainy weather. The processing unit 12 can acquire the information by, for example, obtaining weather information from a server that provides weather information via the communication unit 11. The environmental information may also include information indicating a change in the presence or absence of a person in charge of the target task, such as a delay in the person's return home due to a disruption in transportation, such as a train delay. The processing unit 12 can acquire the information by, for example, obtaining location information of the information processing terminal 3 of the person in charge of the target task (e.g., positioning information from a positioning system such as GPS (Global Positioning System)) via the communication unit 11.

[0155] In the example shown in Fig. 34, "Dad" has already been assigned in the storage device 13 (task DB 131) as the person in charge of the task "taking in the laundry" (target task). Here, when the processing unit 12 acquires weather information indicating that the weather will change from sunny to rainy, it determines that the target task should be executed with priority. Then, the processing unit 12 determines whether the person in charge of the target task is at home or absent by referring to the presence / absence information of each user U1 stored in the storage device 13 (presence / absence DB 137).

[0156] In this case, since "Dad," who is in charge of the target task "taking in the laundry," is not at home, the processing unit 12 updates the person in charge of the target task by changing the person in charge of the target task to "Mom," who is at home. Then, the processing unit 12 sends notification information to the information processing terminal 3 of each user U1. This allows "Mom" to know that she should perform the target task, "taking in the laundry."

[0157] As described above, in the sixth operation example, the person in charge of the target task can be changed based on changes in the environment in which the target task is placed, making it easier to have the target task executed by an appropriate person.

[0158] [3. Advantages, etc.] Advantages of the task management system 100A (task management method) according to the second embodiment are described below. As described above, the task management system 100A (task management method) according to the second embodiment automatically determines the person in charge of a task (target task) to be performed by one of multiple users U1 based on condition information indicating conditions related to each task of the multiple users U1. Therefore, the task management system 100A (task management method) according to the second embodiment has the advantage that the user does not need to manually assign a person in charge in a UI provided by an application or the like, thereby easily reducing the burden of managing tasks. Furthermore, because the task management system 100A (task management method) according to the second embodiment automatically assigns a person in charge to a task, it also has the advantage that it easily avoids situations in which user U1 feels stressed when assigning another user U1 to a task because the other user U1 refuses or gets into an argument with the other user U1.

[0159] (Third Embodiment) [1. Overview] An overview of a task management system 100B according to the third embodiment will be described below with reference to Fig. 35. Fig. 35 is a schematic diagram showing an example of executable operations of the task management system 100B according to the third embodiment. Below, explanations of the points of the task management system 100B according to the third embodiment that are common to the task management system 100 according to the first embodiment will be omitted as appropriate.

[0160] In the third embodiment, the processing unit 12 of the task management system 100B generates pattern information indicating an action pattern to be executed on the device 2 in a predetermined time period based on the acquired log. If the action pattern indicated by the pattern information is not included in the acquired log in the predetermined time period, the processing unit 12 determines that the action pattern is an urgent task.

[0161] An urgent task is a task that should be executed by user U1 who uses device 2. More specifically, an urgent task is a task that is recommended to be executed immediately by user U1. Note that, when a task corresponding to a behavior pattern is not registered in storage device 13 (task DB 131), determining an urgent task means registering the task in storage device 13 and increasing the importance of the registered task. Also, when a task is already registered in storage device 13, determining an urgent task means increasing the importance of the task.

[0162] The importance, which can also be referred to as the urgency, indicates the degree to which the task should be executed by user U1 with priority. In the third embodiment, the importance is expressed in three levels: "low," "medium," and "high." A task with a "low" importance level is a task that can be executed at a time that is convenient for user U1 and does not need to be executed with priority. A task with a "medium" importance level is a task that is recommended to be executed with priority over a task with a "low" importance level. A task with a "high" importance level is a task that should be executed immediately by user U1 and is the task that should be executed with the highest priority.

[0163] The processing unit 12 generates pattern information by, for example, accumulating a predetermined number of logs acquired by the acquisition unit 11 and performing statistical processing such as determining a mode value for the accumulated predetermined number of logs. Note that the processing unit 12 may generate pattern information by using, for example, a large number of logs as learning data, inputting the logs acquired by the acquisition unit 11, and learning a trained model trained by machine learning to output pattern information.

[0164] 36 is a diagram showing an example of generating pattern information. In the example shown in FIG. 36, the processing unit 12 generates pattern information indicating a behavior pattern of "reserving rice cooking to start around 7:00 on weekdays" and a behavior pattern of "starting rice cooking at 4:00 PM on weekdays" based on, for example, a number of logs indicating that a "rice cooking start reservation (at 4:00 PM)" operation was performed on a rice cooker and that the operation was performed between 7:00 AM and 7:30 AM on weekdays. Furthermore, the processing unit 12 generates pattern information indicating a behavior pattern of "performing the tub cleaning course at the end of every month" based on, for example, a number of logs indicating that a "tub cleaning course" operation was performed on a washing machine and that the operation was performed between 10:00 PM and 10:30 PM on the end of the month.

[0165] FIG. 37 is a diagram showing another example of generating pattern information. In the example shown in FIG. 37 , the processing unit 12 generates pattern information indicating a behavioral pattern of “measure weight every day” based on a large number of logs indicating, for example, that an operation “measure weight” was performed on a weight scale and that the operation was performed between 6:30 and 7:00 every day. The processing unit 12 also generates pattern information indicating a behavioral pattern of “measure blood pressure every day” based on a large number of logs indicating, for example, that an operation “measure blood pressure” was performed on a sphygmomanometer and that the operation was performed between 6:30 and 7:00 every day. Here, because these behavioral patterns share a common time period and are performed every day, the processing unit 12 generates pattern information that combines these behavioral patterns into a single behavioral pattern of “measure weight / blood pressure every day.” The pattern information generated by the processing unit 12 is stored in the pattern DB 138 of the storage device 13.

[0166] Returning to FIG. 35 , task management system 100B (1) acquires a log from device 2, (2) determines a task based on the log, and registers the determined task in task DB 131. Task management system 100B also (3) determines a person in charge of the determined task (target task) based on condition information. Then, task management system 100B (4) transmits notification information to user U1's information processing terminal 3 indicating that the task, including the person in charge, has been registered. The example shown in FIG. 35 indicates that there are multiple users U1, and notification information is transmitted to each of the multiple users U1's information processing terminals 3. The multiple users U1 are, for example, family members.

[0167] Furthermore, task management system 100B (1) acquires a log from device 2, and (5) determines an urgent task by referencing pattern information stored in storage device 13 (pattern DB 138). Then, task management system 100B (6) transmits emergency notification information indicating that an urgent task has occurred to information processing terminal 3 of each user U1. Note that task management system 100B does not have to perform the above processes (2) to (4).

[0168] Fig. 38 is a schematic diagram showing an example of notification of emergency notification information in the task management system 100B according to embodiment 3. Fig. 38(a) shows list information as emergency notification information, and Fig. 38(b) shows notification information as emergency notification information. In the example shown in Fig. 38(a), as shown in the area surrounded by a dashed line, the content of the emergency task "reserving the start of rice cooking" is displayed on the display of the information processing terminal 3.

[0169] In the example shown in (b) of Figure 38, as shown in the area surrounded by dashed lines, a message indicating that an emergency task has occurred regarding the rice cooker and a hyperlink called ``Reserve rice cooking'' for remotely reserving the start of rice cooking operation of the rice cooker are displayed on the display of the information processing terminal 3.

[0170] In this way, the processing unit 12 may include information for remotely operating the device 2 (here, a rice cooker) that is the target of the emergency task in the emergency notification information and transmit the information to the information processing terminal 3 of each user U1. Note that the processing unit 12 may also transmit the emergency notification information to the information processing terminal 3 of each user U1 without including information for remotely operating the device 2.

[0171] 38, the area surrounded by the dashed line may be displayed in a manner that makes it more visually emphasized than the other areas. For example, if text is displayed in black in the other areas, the text in the area surrounded by the dashed line may be displayed in red. Also, for example, the area surrounded by the dashed line may be displayed higher on the display than the other areas.

[0172] [2. Operation] The operation of the task management system 100B according to the third embodiment (that is, the task management method) will be described in detail below.

[0173] [2-1. Example of Basic Operation] First, an example of basic operation of the task management system 100B according to the third embodiment will be described with reference to Fig. 39. Fig. 39 is a flowchart showing an example of basic operation of the task management system 100B according to the third embodiment. Here, the task management system 100B is described as acquiring a log from the device 2. Also, here, the description is given assuming that there is one user U1.

[0174] When a log is generated in the device 2, the device 2 transmits a signal including the generated log to the server 1 (task management system 100B) via the network N1, whereby the communication unit (acquisition unit) 11 acquires the log via the network N1 (S21).

[0175] Next, the processing unit 12 generates pattern information indicating a behavioral pattern based on the logs acquired by the communication unit (acquisition unit) 11 (S22). Step S22 does not have to be executed every time step S21 is executed. For example, step S22 may be executed every time a predetermined number of logs acquired in step S21 are accumulated.

[0176] Next, the processing unit 12 determines whether or not the log for the predetermined time period includes a behavior pattern (S23). Here, the processing unit 12 determines whether or not the log for the predetermined time period includes a behavior pattern executed during the predetermined time period by referring to the pattern information stored in the storage device 13 (pattern DB 138).

[0177] If the behavior pattern is not included in the log for the predetermined time period (S23: No), the processing unit 12 determines an urgent task (S24). Here, the processing unit 12 determines the behavior pattern as the urgent task.

[0178] Then, the processing unit 12 transmits emergency notification information indicating that an emergency task has occurred to the information processing terminal 3 of the user U1 (S25). Note that if the behavior pattern is included in the log for the predetermined time period (S23: Yes), the processing unit 12 does not execute steps S24 and S25.

[0179] Below, specific examples of operations that can be performed by the task management system 100B according to the third embodiment are listed. In the first and second examples of operations described below, the multiple users U1 are described as two people, "Dad" and "Mom." In the first and second examples of operations described below, the pattern information has already been generated. The task management system 100B may also perform an appropriate combination of the first and second examples of operations described below.

[0180] [2-2. First Operation Example] First, a first operation example of the task management system 100B according to embodiment 3 will be described with reference to Fig. 40. Fig. 40 is a schematic diagram showing the first operation example of the task management system 100B according to embodiment 3. The first operation example is a specific example of processing in which the processing unit 12 determines an urgent task by referring to pattern information.

[0181] In the example shown in Fig. 40, device 2 is a rice cooker. When a rice cooker is normally operated to "reserve rice cooking start" between 7:00 and 7:30, it sends a signal to task management system 100B containing a log indicating that the "reserve rice cooking start" operation was performed during that time period. However, in the example shown in Fig. 40, because the "reserve rice cooking start" operation was not performed during that time period, the rice cooker does not send a signal to task management system 100B containing a log indicating that the "reserve rice cooking start" operation was performed during that time period.

[0182] Because the log does not contain the behavior pattern "reserving rice cooking start," the processing unit 12 of the task management system 100B determines that the behavior pattern "reserving rice cooking start" is an urgent task and sends urgent notification information to each user U1's information processing terminal 3. In the example shown in Fig. 40, the processing unit 12 determines whether the log contains the behavior pattern "reserving rice cooking start" a predetermined time (here, two hours) before 4:00 PM, which is the time when the rice cooker normally starts cooking rice.

[0183] In the example shown in Figure 40, one of the multiple users U1 sees the emergency notification information received on the information processing terminal 3 and realizes that the urgent task of "reserving rice cooking start" has occurred, and remotely controls the rice cooker to "reserving rice cooking start" (i.e., completing the urgent task). As a result, the rice cooker starts cooking rice at the reserved time (here, 4:00 PM).

[0184] Here, in the first operation example, the processing performed by the processing unit 12 differs depending on whether the determined urgent task is not registered in the storage device 13 (task DB 131) or whether the determined urgent task is already registered.

[0185] 41 is a schematic diagram illustrating an example in which a determined urgent task is not registered in the first operation example of the task management system 100B according to embodiment 3. In the example shown in FIG. 41, the processing unit 12 determines the behavior pattern "reserving rice cooking start (4:00 PM)" included in the pattern information stored in the storage device 13 (pattern DB 138) as an urgent task. Then, since the task "reserving rice cooking start (4:00 PM)" is not registered in the storage device 13 (task DB 131), the processing unit 12 registers the task "reserving rice cooking start (4:00 PM)" with its importance set to "high" in the storage device 13. As a result, the task "reserving rice cooking start (4:00 PM)" is registered in the storage device 13 as an urgent task.

[0186] Fig. 42 is a schematic diagram showing an example in which a determined urgent task is registered in the first operation example of the task management system 100B according to embodiment 3. In the example shown in Fig. 42, the processing unit 12 determines, as in the example shown in Fig. 41, the behavior pattern "reserving rice cooking start (4:00 PM)" included in the pattern information stored in the storage device 13 (pattern DB 138) as an urgent task. Then, since the task "reserving rice cooking start (4:00 PM)" is already registered in the storage device 13 (task DB 131), the processing unit 12 updates the "reserving rice cooking start" task by changing its importance from "medium" to "high." As a result, the task "reserving rice cooking start (4:00 PM)" is registered in the storage device 13 as an urgent task.

[0187] As described above, in the first operation example, when a task (behavioral pattern) that is normally executed is not executed, the task is determined to be an urgent task, and emergency notification information is transmitted to each user U1's information processing terminal 3. Therefore, in the first operation example, each user U1 can easily notice a task that they have forgotten to execute (urgent task), and can easily avoid a situation where the task is left unexecuted.

[0188] [2-3. Second Operation Example] Next, a second operation example of the task management system 100B according to embodiment 3 will be described with reference to Fig. 43. Fig. 43 is a schematic diagram showing the second operation example of the task management system 100B according to embodiment 3. The second operation example differs from the first operation example in that an urgent task is determined further based on environmental information that indicates changes in the environment in which one or more tasks registered in the storage device 13 (task DB 131) are placed.

[0189] The environmental information may include information indicating a change in weather at the location where the target task is to be performed, such as a change from sunny to rainy weather. The processing unit 12 can acquire the information by, for example, acquiring weather information from a server that provides weather information via the communication unit (acquisition unit) 11. The environmental information may also include information indicating a change in the presence or absence of a person in charge of the target task, such as a delay in the person's return home due to a disruption in transportation such as a train delay. The processing unit 12 can acquire the information by, for example, acquiring location information (e.g., positioning information from a positioning system such as GPS) of the information processing terminal 3 of the person in charge of the target task via the communication unit 11.

[0190] 43, the task "take in laundry" has already been registered in the storage device 13 (task DB 131). Here, when the processing unit 12 acquires weather information indicating that the weather will change from sunny to rainy, it determines that the task should be executed with priority. Then, the processing unit 12 changes the importance of the task from "medium" to "high," thereby registering the task as an urgent task.

[0191] The processing unit 12 also determines whether the person in charge of the urgent task is at home or absent by referencing the presence / absence information of each user U1 stored in the storage device 13 (presence / absence DB 137). In this case, since "Dad," who is in charge of the urgent task of "taking in the laundry," is absent, the processing unit 12 updates the person in charge of the urgent task by changing the person in charge of the urgent task to "Mom," who is at home. The processing unit 12 then transmits emergency notification information to the information processing terminal 3 of each user U1. This allows "Mom" to know that she should perform the urgent task of "taking in the laundry."

[0192] As described above, in the second operation example, an urgent task is determined based on a change in the environment in which one or more tasks registered in the storage device 13 (task DB 131) are placed, and emergency notification information is transmitted to the information processing terminal 3 of each user U1. Therefore, in the second operation example, each user U1 can easily notice a task (urgent task) that needs to be executed due to a change in the environment, and can easily avoid a situation in which the task is left unexecuted.

[0193] In the above description, the multiple users U1 are assumed to be a single group such as a family, but this is not limiting. For example, as shown in Figure 44, the multiple users U1 may include multiple groups (two groups in this example). Figure 44 is a schematic diagram showing an example of destinations of emergency notification information in the task management system 100B according to the third embodiment.

[0194] In the example shown in Fig. 44, "group α" is the family, and "group β" is the grandparents. In this case, when an urgent task occurs in "group β," the processing unit 12 of the task management system 100B not only transmits emergency notification information to the information processing terminal 3 of each user U1 belonging to "group β," but also transmits the emergency notification information to the information processing terminal 3 of each user U1 belonging to "group α." This makes it easier for each user U1 in "group α" to notice that an urgent task has occurred in "group β," and allows each user U1 in "group β" to execute the urgent task even if they forget to execute it.

[0195] [3. Advantages, etc.] Advantages of the task management system 100B (task management method) according to the third embodiment will be described below. As described above, the task management system 100B (task management method) according to the third embodiment generates pattern information indicating an action pattern to be executed on the device 2 during a predetermined time period based on the acquired log. Then, if the acquired log does not contain an action pattern indicated by the pattern information during the predetermined time period, the task management system 100B (task management method) according to the third embodiment determines the action pattern as an urgent task. Therefore, the task management system 100B (task management method) according to the third embodiment determines a task (action pattern) that is normally executed as an urgent task when the task is not executed. This has the advantage that each user U1 can easily notice a task (urgent task) that they forgot to execute, making it easier to avoid a situation in which the task is left unexecuted.

[0196] (Modifications) As described above, the first to third embodiments have been described as examples of the technology disclosed in the present application. However, the technology in the present disclosure is not limited to this, and can be applied to the first to third embodiments with appropriate modifications, substitutions, additions, omissions, etc. Furthermore, it is also possible to combine the components described in the first to third embodiments to create new first to third embodiments.

[0197] Therefore, modifications of the first to third embodiments will be exemplified below.

[0198] In the above-mentioned embodiment 1, the task management system 100 has both a registration function that registers a task determined based on the acquired log in the storage device 13 (task DB 131) if the task is a new task, and an update function that updates the task with the content of the determined task if the task is already registered in the storage device 13, but is not limited to this.

[0199] For example, the task management system 100 may only have the above-mentioned registration function. That is, in the task management method, a log relating to the state of the device 2 is acquired by communicating with the device 2 or an external system that manages the device 2. In this task management method, a task to be executed by the user U1 who uses the device 2 is determined based on the acquired log. In this task management method, the determined task is registered in the storage device 13.

[0200] Furthermore, for example, the task management system 100 may only have the above-described update function. That is, in the task management method, a log relating to the state of the device 2 is acquired by communicating with the device 2 or an external system that manages the device 2. In this task management method, a task to be executed by the user U1 who uses the device 2 is determined based on the acquired log. In this task management method, the content of a task of the same type as the determined task, which is registered in the storage device 13, is updated to the content of the determined task.

[0201] In the third embodiment, the processing unit 12 of the task management system 100B may determine whether to send emergency notification information based on, for example, schedule information indicating the schedule of each user U1. For example, if the processing unit 12 determines that the task of "reserving the start of rice cooking" is an emergency task, the processing unit 12 may not need to send emergency notification information if the schedule information indicates that each user U1 is going out to eat.

[0202] In the third embodiment, the processing unit 12 of the task management system 100B may change the importance of each of one or more tasks registered in the storage device 13 (task DB 131) based on various information such as schedule information. For example, if the schedule information indicates that a sports day is scheduled for the weekend, the processing unit 12 may increase the importance of the task "Shopping (Eggs)" because it is estimated that there is a high possibility that eggs will be included in the lunch box prepared for the sports day. Also, for example, if a task "Make fried rice" is registered in the storage device 13, the processing unit 12 may increase the importance of the task "Shopping (Eggs)" also registered in the storage device 13.

[0203] In the first to third embodiments, the task management systems 100, 100A, and 100B may be implemented by a device other than the server 1. Furthermore, for example, while the task management systems 100, 100A, and 100B are implemented as a single device in the first to third embodiments, they may be implemented by multiple devices. When the system is implemented by multiple devices, the components of the task management systems 100, 100A, and 100B may be distributed in any manner among the multiple devices. For example, some of the components of the task management systems 100, 100A, and 100B in the first to third embodiments may be provided in the facility where user U1 resides. In other words, the present disclosure may be implemented by cloud computing or edge computing.

[0204] Furthermore, for example, all or some of the components of the task management systems 100, 100A, and 100B disclosed herein may be configured with dedicated hardware, or may be realized by executing a software program suitable for each component. Each component may be realized by a program execution unit such as a CPU (Central Processing Unit) or a processor reading and executing a software program recorded on a recording medium such as an HDD (Hard Disk Drive) or semiconductor memory.

[0205] Furthermore, the components of the task management systems 100, 100A, and 100B according to the present disclosure may be configured with one or more electronic circuits. Each of the one or more electronic circuits may be a general-purpose circuit or a dedicated circuit.

[0206] The one or more electronic circuits may include, for example, a semiconductor device, an integrated circuit (IC), or a large-scale integration (LSI). The IC or LSI may be integrated on a single chip or on multiple chips. Although the IC or LSI is referred to here as an IC or LSI, the name may vary depending on the degree of integration, and may be called a system LSI, a very large-scale integration (VLSI), or an ultra-large-scale integration (ULSI). A field programmable gate array (FPGA), which is programmed after the LSI is manufactured, can also be used for the same purpose.

[0207] Furthermore, the general or specific aspects of the present disclosure may be realized as a system, device, method, integrated circuit, or computer program. Alternatively, the computer program may be stored on a non-transitory computer-readable recording medium such as an optical disc, HDD, or semiconductor memory. For example, the present disclosure may be realized as a program for causing a computer to execute the task management method according to the first to third embodiments. The program may be recorded on a non-transitory computer-readable recording medium such as a CD-ROM, or may be distributed via a communication channel such as the Internet.

[0208] Furthermore, for example, the program is not limited to a program executed by a single computer, but may be a program executed in a distributed manner by a plurality of computers.

[0209] As described above, the first to third embodiments have been described as examples of the technology in the present disclosure, and the accompanying drawings and detailed descriptions have been provided for this purpose.

[0210] Therefore, the components shown in the accompanying drawings and detailed description may include not only essential components for solving the problem, but also components that are not essential for solving the problem in order to illustrate the above technology. Therefore, the fact that these non-essential components are shown in the accompanying drawings or detailed description should not be interpreted as immediately indicating that these non-essential components are essential.

[0211] Furthermore, since the above-described first to third embodiments are intended to illustrate the technology of the present disclosure, various modifications, substitutions, additions, omissions, etc. can be made within the scope of the claims or their equivalents.

[0212] As described above, in the task management method according to the first aspect, a person in charge of a target task to be performed by one of multiple users U1 is determined based on condition information indicating conditions related to each of the tasks of the multiple users U1 (S11). In this task management method, information indicating the target task associated with the determined person in charge is output (S13).

[0213] This has the advantage that the person in charge of the target task is automatically determined based on the condition information, so the user does not have to manually assign a person in charge in a UI provided by an application, etc., and the burden of managing tasks is easily reduced.

[0214] In the task management method according to the second aspect, in the first aspect, the person in charge is determined based on the degree of implementation of one or more tasks other than the target task for each of the multiple users U1 as condition information.

[0215] This has the advantage that the person in charge of the target task is determined based on the degree of task implementation of each user U1, making it less likely that a bias will occur in the people in charge of each task.

[0216] In addition, in the task management method according to the third aspect, in the first or second aspect, the person in charge is determined based on the status of responsibility for related tasks related to the target task for each of the multiple users U1 as condition information.

[0217] This has the advantage that the same person can be assigned to two or more tasks that are more efficient when performed together, making it easier for the person in charge to perform the tasks efficiently.

[0218] In addition, in the task management method according to the fourth aspect, in any one of the first to third aspects, the person in charge is determined based on the category of the task assigned to each of the multiple users U1 as condition information.

[0219] This has the advantage that the person in charge of the target task is determined based on the category of the task assigned to each user U1, making it less likely that the person in charge of the target task will be dissatisfied.

[0220] In addition, in the task management method according to the fifth aspect, in any one of the first to fourth aspects, the person in charge is determined based on the outcome of a game in which multiple users U1 participate, with the person in charge being bet as condition information.

[0221] This has the advantage that the person in charge of the target task is less likely to become dissatisfied with the person assigned the target task, since the person in charge of the target task is determined based on the outcome of the game.

[0222] In addition, in the task management method according to the sixth aspect, in any one of the first to fifth aspects, when a person in charge has been assigned to the target task, the person in charge is re-determined based on environmental information indicating changes in the environment in which the target task is placed.

[0223] This has the advantage that the person in charge of the target task can be changed based on changes in the environment in which the target task is placed, making it easier to have the target task executed by an appropriate person.

[0224] A program according to a seventh aspect causes one or more processors to execute the task management method according to any one of the first to sixth aspects.

[0225] This has the advantage that the person in charge of the target task is automatically determined based on the condition information, so the user does not have to manually assign a person in charge in a UI provided by an application, etc., and the burden of managing tasks is easily reduced.

[0226] Furthermore, a task management system 100A according to an eighth aspect includes a processing unit 12 and a communication unit (acquisition unit) 11. The processing unit 12 determines a person in charge of a target task to be performed by one of multiple users U1 based on condition information indicating conditions related to each task of the multiple users U1. The communication unit 11 outputs information indicating the target task to which the person in charge determined by the processing unit 12 is linked.

[0227] This has the advantage that the person in charge of the target task is automatically determined based on the condition information, so the user does not have to manually assign a person in charge in a UI provided by an application, etc., and the burden of managing tasks is easily reduced.

[0228] The present disclosure is applicable to systems that manage tasks performed by users who use devices.

[0229] DESCRIPTION OF SYMBOLS 1 Server 11 Acquisition unit (communication unit) 12 Processing unit 13 Storage device 131 Task DB 132 Task determination DB 133 Task deletion DB 134 Task selection DB 135 Task update DB 136 Condition DB 137 Presence / absence DB 138 Pattern DB 2 Device 3 Information processing terminal 100, 100A, 100B Task management system N1 Network U1 User U11 First user U12 Second user

Claims

1. A task management method comprising: determining a person in charge of a target task to be performed by any one of a plurality of users based on condition information indicating conditions related to each of the tasks of the plurality of users; and outputting information indicating the target task to which the determined person in charge is linked.

2. The task management method according to claim 1, further comprising determining the person in charge based on the degree of implementation of one or more tasks other than the target task for each of the plurality of users as the condition information.

3. The task management method according to claim 1, further comprising the step of determining the person in charge based on the condition information indicating a status of each of the plurality of users in charge of related tasks related to the target task.

4. The task management method according to claim 1, further comprising determining the person in charge based on a category of a task assigned to each of the plurality of users as the condition information.

5. The task management method according to claim 1, wherein the person in charge is determined based on the outcome of a game in which the plurality of users participate and the person in charge is bet on as the condition information.

6. A task management method according to any one of claims 1 to 5, further comprising the step of: when the person in charge has been assigned to the target task, re-determining the person in charge based on environmental information indicating a change in the environment in which the target task is placed.

7. A program for causing one or more processors to execute the task management method according to any one of claims 1 to 5.

8. A task management system comprising: a processing unit that determines a person in charge of a target task to be performed by any one of a plurality of users based on condition information indicating conditions related to each task of the plurality of users; and a communication unit that outputs information indicating the target task to which the person in charge determined by the processing unit is linked.

Images