Task management method, program, and task management system

Abstract

In a task management method, a log relating to the state of a device (2) is acquired by communicating with the device (2) or an external system that manages the device (2) (S1). In this task management method, a task to be executed by a user (U1) using the device (2) is determined on the basis of the acquired log (S2).

Description

Technical Field

[0001] The present disclosure relates to a task management method and the like for managing tasks performed by a user utilizing a device. Background Art

[0002] For example, Patent Document 1 discloses a housework plan creation support device. This device creates a housework plan by having a user specify the type, time, and location of housework to be performed by a housework robot.

[0003] Prior art literature

[0004] Patent Literature

[0005] Patent Document 1: Japanese Patent Application Laid-Open No. 2012-190073 Summary of the Invention

[0006] Problems to be solved by the invention

[0007] The present disclosure provides a task management method and the like that easily reduce the load for managing tasks related to a device.

[0008] Means for solving problems

[0009] In one aspect of the present disclosure, a task management method acquires a log related to the status of a device by communicating with the device or an external system that manages the device. In the task management method, a task to be performed by a user using the device is determined based on the acquired log.

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

[0011] A task management system according to one embodiment of the present disclosure includes an acquisition unit and a processing unit. The acquisition unit acquires a log related to the status of a device by communicating with the device or an external system that manages the device. The processing unit determines a task to be performed by a user utilizing the device based on the log acquired by the acquisition unit.

[0012] Effects of the Invention

[0013] The present disclosure has an advantage of easily reducing the load for managing tasks performed by users utilizing a device. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 This is a block diagram showing the overall structure of the task management system including the first embodiment.

[0015] Figure 2 This is a schematic diagram showing an example of executable operations of the task management system according to the first embodiment.

[0016] Figure 3 This is a schematic diagram showing another example of executable operations of the task management system according to the first embodiment.

[0017] Figure 4 This is a flowchart showing a basic operation example of the task management system according to the first embodiment.

[0018] Figure 5 This is a schematic diagram showing a first operation example of the task management system according to the first embodiment.

[0019] Figure 6 This is a schematic diagram showing a notification example of notifying a user of a registered task in the first operational example of the task management system according to the first embodiment.

[0020] Figure 7 This is a schematic diagram showing an example of a user acquiring list information in the first operational example of the task management system according to the first embodiment.

[0021] Figure 8 This 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 the first embodiment.

[0022] Figure 9 This is a schematic diagram showing a second operation example of the task management system according to the first embodiment.

[0023] Figure 10 This is a schematic diagram showing a third operation example of the task management system according to the first embodiment.

[0024] Figure 11 This is a schematic diagram showing a fourth operation example of the task management system according to the first embodiment.

[0025] Figure 12 This is a schematic diagram showing another registration method in the fourth operation example of the task management system according to the first embodiment.

[0026] Figure 13 This is a schematic diagram showing the fifth operation example of the task management system according to the first embodiment.

[0027] Figure 14 This is a schematic diagram showing the fifth operation example of the task management system according to the first embodiment.

[0028] Figure 15 This is a schematic diagram showing an example of a case where another user cannot change the person in charge of a task in the fifth operational example of the task management system according to the first embodiment.

[0029] Figure 16This is a schematic diagram showing an example of a fifth operational example of the task management system according to the first embodiment, in which the person in charge of a task can be changed by another user.

[0030] Figure 17 This is a schematic diagram showing another example of the fifth operational example of the task management system according to the first embodiment, in which the person in charge of a task can be changed by another user.

[0031] Figure 18 This is a schematic diagram showing another example of the fifth operational example of the task management system according to the first embodiment, in which the person in charge of a task can be changed by another user.

[0032] Figure 19 This is a schematic diagram showing the sixth operation example of the task management system according to the first embodiment.

[0033] Figure 20 This is a schematic diagram showing the seventh operation example of the task management system according to the first embodiment.

[0034] Figure 21 This is a schematic diagram showing the eighth operation example of the task management system according to the first embodiment.

[0035] Figure 22 This is a schematic diagram showing an example of deleting a task after a certain period of time in the eighth operation example of the task management system according to the first embodiment.

[0036] Figure 23 This 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 the first embodiment.

[0037] Figure 24 This is a schematic diagram showing the ninth operation example of the task management system according to the first embodiment.

[0038] Figure 25 This is a schematic diagram showing an example of executable operations of the task management system according to the second embodiment.

[0039] Figure 26 This is a schematic diagram showing an example of list information.

[0040] Figure 27 This is a flowchart showing a basic operation example of the task management system according to the second embodiment.

[0041] Figure 28 This is a schematic diagram showing a first operation example of the task management system according to the second embodiment.

[0042] Figure 29 This 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 the second embodiment.

[0043] Figure 30 This is a schematic diagram showing a second operation example of the task management system according to the second embodiment.

[0044] Figure 31 This is a schematic diagram showing a third operation example of the task management system according to the second embodiment.

[0045] Figure 32 This is a schematic diagram showing a fourth operation example of the task management system according to the second embodiment.

[0046] Figure 33 This is a schematic diagram showing the fifth operation example of the task management system according to the second embodiment.

[0047] Figure 34 This is a schematic diagram showing the sixth operation example of the task management system according to the second embodiment.

[0048] Figure 35 This is a schematic diagram showing an example of executable operations of the task management system according to the third embodiment.

[0049] Figure 36 This is a diagram showing an example of generating pattern information.

[0050] Figure 37 This is a diagram showing another example of generating pattern information.

[0051] Figure 38 This is a schematic diagram showing an example of notification of emergency notification information in the task management system according to the third embodiment.

[0052] Figure 39 This is a flowchart showing a basic operation example of the task management system according to the third embodiment.

[0053] Figure 40 This is a schematic diagram showing a first operation example of the task management system according to the third embodiment.

[0054] Figure 41 This is a schematic diagram showing an example of a case where a determined urgent task is not registered in the first operational example of the task management system according to the third embodiment.

[0055] Figure 42 This is a schematic diagram showing an example of registering a determined urgent task in the first operational example of the task management system according to the third embodiment.

[0056] Figure 43 This is a schematic diagram showing a second operation example of the task management system according to the third embodiment.

[0057] Figure 44This is a schematic diagram showing an example of notification destinations of emergency notification information in the task management system according to the third embodiment. DETAILED DESCRIPTION

[0058] First, the inventor's focus will be described below.

[0059] Conventional technologies exist for managing tasks performed by users, such as housework, or for sharing tasks among multiple users. For example, Patent Document 1 discloses a technology for creating a housework plan by having the user specify the type, time, and location of housework to be performed by a housework robot.

[0060] However, in the above-described technology, users must manually operate a UI (User Interface) provided by an application to register, update, or delete tasks to be managed. This poses a problem in that the burden of managing tasks on users tends to increase.

[0061] In view of the above circumstances, the inventors have completed the present disclosure.

[0062] The following describes the embodiments in detail with reference to the accompanying drawings as appropriate. However, unnecessary detailed descriptions may be omitted. For example, detailed descriptions of well-known matters and repeated descriptions of substantially identical structures may be omitted. This is to avoid unnecessary redundancy in the following description and to facilitate understanding by those skilled in the art.

[0063] Furthermore, the inventor provides the drawings and the following description in order to enable those skilled in the art to fully understand the present disclosure, and does not intend to limit the subject matter described in the claims by them.

[0064] (Implementation 1)

[0065] [1-1. Overall structure]

[0066] First, use Figure 1 The overall configuration of the task management system 100 according to the first embodiment will be described. Figure 1 This is a block diagram showing the overall structure of the task management system 100 including the first embodiment. In the first embodiment, the task management system 100 is a system for managing one or more tasks related to the device 2. The user U1 (refer to Figure 2 or Figure 3 ) By using the information processing terminal 3, the user U1 can obtain a list of one or more tasks managed by the storage device 13 (described later) (hereinafter referred to as "task list") from the task management system 100. In addition, the user U1 can receive a notification of a change in one or more tasks managed by the storage device 13 from the task management system 100 via the information processing terminal 3.

[0067] Device 2 is, for example, a device that can communicate with server 1 (task management system 100) via a network N1 such as the Internet. In embodiment 1, device 2 is an IoT (Internet of Things) device. Device 2 is, for example, a home appliance. Specifically, device 2 is, for example, a washing machine, an air conditioner, a humidifier, an air purifier, a microwave oven, a refrigerator, an electric rice cooker, a robot vacuum cleaner, a fixed television receiver, a portable television receiver, etc. In addition, device 2 is, for example, a Blue-ray Disc (registered trademark) recorder, a DVD (Digital Versatile Disc) (registered trademark) recorder, a lighting fixture, an intercom system, an electric toothbrush, a bathroom scale, or a hair dryer.

[0068] A task is an action performed by user U1 using device 2. In Embodiment 1, any task related to device 2 is sufficient. For example, in addition to actions performed directly by user U1 on device 2, such as loading laundry from a washing machine, tasks performed indirectly by user U1 on device 2, such as purchasing detergent for the washing machine, can also be included. Furthermore, tasks are not limited to tasks related to household chores, i.e., daily household operations, such as cleaning with a cleaning robot, washing with a washing machine, or cooking with a rice cooker. For example, tasks related to daily activities performed by user U1, such as brushing teeth with an electric toothbrush or weighing themselves on a scale, can also be included.

[0069] The information processing terminal 3 is a terminal owned by the user U1, and is, for example, 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 or obtain information sent from the task management system 100 by executing an application for the task management system 100 installed on the information processing terminal 3.

[0070] Furthermore, the user U1 can also instruct the task management system 100 or obtain information sent from the task management system 100 by accessing the URL (Uniform Resource Locator) for the task management system 100 through the web browser installed in the information processing terminal 3 .

[0071] [1-2. Task Management System]

[0072] Next, the details of the task management system 100 will be described. Figure 1As shown, the task management system 100 includes a communication unit 11, a processing unit 12, and a storage device 13. In the first embodiment, the task management system 100 includes the storage device 13, but the storage device 13 may not be a component of the task management system 100.

[0073] In the first embodiment, the task management system 100 is implemented by the server 1. The server 1 includes a processor and a memory, and each component of the task management system 100 is implemented by the processor executing a computer program stored in the memory.

[0074] 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. Figure 1 In the example shown, there is one device 2 and one information processing terminal 3 , but there may be multiple devices and information processing terminals 3 .

[0075] The communication unit 11 is a communication interface for communicating with the device 2 and the information processing terminal 3 via the network N1. The communication unit 11 acquires a log related to the status of the device 2 by communicating with the device 2. Hereinafter, the communication unit 11 is also referred to as the acquisition unit 11.

[0076] 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, transmitted from the device 2 via the network N1. Alternatively, the acquisition unit 11 may 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, transmitted from the external system via the network N1.

[0077] Here, the log may include information indicating actions performed by device 2 or information indicating operations accepted by device 2, as information indicating the status of device 2. Furthermore, actions performed by device 2 may include not only actions performed by device 2 itself but also actions performed by sensors or other devices included in device 2.

[0078] For example, if device 2 is a washing machine with an automatic detergent dispenser, the log may include information about the remaining detergent level. Alternatively, if device 2 is a washing machine with a filter status check function, the log may include information about the filter status. Alternatively, if device 2 is a refrigerator, the log may include information about the remaining water level in the water supply tank. Alternatively, if device 2 is a refrigerator with a function for identifying the food inside, the log may include information about the remaining food level inside.

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

[0080] The first corresponding information is information indicating the correspondence between a log and a task. Specifically, the first corresponding information is information indicating the correspondence between device 2, the source of the log, the content of the log generated by device 2, and the content of the task that user U1 should perform based on the content of the log. For example, if device 2 is a washing machine, the first corresponding information may include information associating the content of the log indicating that the remaining amount of detergent has decreased with the content of the task for user U1 to replenish detergent. Alternatively, for example, if device 2 is a washing machine, the first corresponding information may include information associating the content of the log indicating that the remaining amount of detergent has decreased with the content of the task for user U1 to purchase detergent.

[0081] As described above, tasks include not only tasks that the user U1 directly performs on the device 2 , such as refilling the washing machine with detergent, but also tasks that the user U1 indirectly performs on the device 2 , such as going to buy detergent to refill the washing machine.

[0082] In the first embodiment, the processing unit 12 performs processing to register the determined task in the storage device 13 (task DB 131 ) (described later) or to update the task registered in the storage device 13 (task DB 131 ) with the determined task.

[0083] For example, if the type of the determined task is different from the type of one or more tasks 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.

[0084] Furthermore, for example, if the type of the determined task is the same as the type of one of the 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 an already managed task, the processing unit 12 updates the content of the task by overwriting the content of the already managed task with the content of the determined task.

[0085] Furthermore, in the first embodiment, when one or more tasks registered in the storage device 13 (task DB 131) are changed, the processing unit 12 sends notification information indicating the change to the information processing terminal 3 used by the user U1. The change mentioned here may include, for example, registering a new task in the storage device 13 as described above, or updating the content of an already managed task.

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

[0087] 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 not only tasks determined by the processing unit 12 but also tasks registered by the user U1 using the information processing terminal 3 as described later.

[0088] 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 and a task update DB 135, which will be described later.

[0089] 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.

[0090] The task deletion DB 133 stores the second corresponding information that is referenced by the processing unit 12 when deleting one of the one or more tasks registered in the storage device 13 (task DB 131). The second corresponding information is information indicating the correspondence between the log and the task to be deleted. Specifically, the second corresponding information is information indicating the correspondence between the device 2 that is the source of 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, in the case where the device 2 that is the source of the log is a washing machine, the second corresponding information may include information associating the content of the log indicating that the remaining amount of detergent has increased with the content of the task to be deleted, such as the user U1 replenishing the detergent. In addition, for example, in the case where the device 2 that is the source of the log is a washing machine, the second corresponding information may include information associating the content of the log indicating that the remaining amount of detergent has increased with the content of the task to be deleted, such as the user U1 going to buy detergent.

[0091] Figure 21 is a schematic diagram showing an example of executable actions of the task management system 100 according to the first embodiment. Figure 2 As shown, the task management system 100 (1) obtains a log from the device 2, then (2) determines a task based on the log, registers the determined task in the task DB 131, or updates an existing task with the determined task. Furthermore, the task management system 100 (3) sends notification information indicating that the task has been registered or updated to the information processing terminal 3 of the user U1. Figure 2 The example shown indicates that there are a plurality of users U1 , and notification information is transmitted to the information processing terminals 3 of the respective users U1 .

[0092] Furthermore, when the task management system 100 (4) acquires request information transmitted from the information processing terminal 3 of a certain user U1, it (5) transmits the list information to the information processing terminal 3.

[0093] Furthermore, the task management system 100 according to the first embodiment can also perform the following operations. Figure 3 FIG. 1 is a schematic diagram showing another example of executable actions of the task management system 100 according to the first embodiment. Figure 3 As shown, the task management system 100 (1) obtains operation information from the information processing terminal 3 of the user U1, and then (2) registers the task in the task DB 131 or updates an existing task based on the operation information. Here, the operation information is information input by the user U1 by operating the information processing terminal 3, for example, including information requesting the registration of the task desired by the user U1, or information requesting the update of the task desired by the user U1. In addition, the task management system 100 (3) sends notification information indicating that the task has been registered or updated to the information processing terminal 3 of the user U1. Figure 3 The example shown indicates that there are more than one user U1 in addition to the user U1 who sent the operation information, and the notification information is sent to the information processing terminals 3 of all users U1. In addition, if the task management system 100 (4) receives the request information sent from the information processing terminal 3 of a certain user U1, it (5) sends the summary information to the information processing terminal 3.

[0094] [2.Action]

[0095] Hereinafter, the operation of the task management system 100 (ie, the task management method) according to the first embodiment will be described in detail.

[0096] [2-1. Basic operation example]

[0097] First, use Figure 4 A basic operation example of the task management system 100 according to the first embodiment will be described. Figure 4This is a flowchart showing a basic operation example of the task management system 100 according to Embodiment 1. Here, the task management system 100 is described as acquiring a log from the device 2. Here, the case where there is only one user U1 is described.

[0098] 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).

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

[0100] 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 existing task by overwriting the contents of the determined task with the contents of the existing task (S5).

[0101] Then, the processing unit 12 transmits notification information indicating that one or more tasks registered in the storage device 13 (task DB 131 ) have been changed to the information processing terminal 3 of the user U1 via the network N1 ( S6 ).

[0102] The following lists specific operation examples that can be executed by the task management system 100 according to Embodiment 1. The task management system 100 can also execute the first to ninth operation examples described below in combination as appropriate.

[0103] [2-2. Example 1]

[0104] First, use Figure 5 A first operation example of the task management system 100 according to the first embodiment will be described. Figure 5 This is a schematic diagram showing a first operational example of the task management system 100 according to Embodiment 1. The first operational 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 ).

[0105] exist Figure 5In the example shown, processing unit 12 obtains a log indicating "Detergent remaining (low)" from a washing machine, device 2. Processing unit 12 then determines a task based on the obtained log by referencing the first correspondence information stored in storage device 13 (task determination DB 132). Here, processing unit 12 determines a "Replenish detergent" task and a "Shopping (detergent)" task corresponding to the "Detergent remaining (low)" log. Processing unit 12 then registers the determined "Replenish detergent" and "Shopping (detergent)" tasks in storage device 13 (task DB 131).

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

[0107] Figure 6 1 is a schematic diagram showing an example of notifying the user U1 of a registered task in the first operation example of the task management system 100 according to the first embodiment. Figure 6 In the example shown, the processing unit 12 sends notification information to the information processing terminal 3 of user U1 indicating that the "Replenish Detergent" task and the "Shopping (Detergent)" task have been registered. Upon receiving the notification information, the information processing terminal 3 of user U1 displays the notification information on a display, for example, via an instant messaging application such as LINE (registered trademark). This allows user U1 to understand that a new task has been registered.

[0108] Furthermore, 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. Furthermore, the information processing terminal 3 may output the notification information by sound via a built-in speaker.

[0109] Figure 7 1 is a schematic diagram showing an example of user U1 acquiring list information in the first operation example of the task management system 100 according to the first embodiment. Figure 7 In the example shown, user U1 operates the information processing terminal 3 to send a request message requesting the transmission of a task list to the task management system 100. Upon receiving the request message, the processing unit 12 reads out one or more tasks registered in the storage device 13 (task DB 131). Here, the processing unit 12 reads out the "replenish detergent" task and the "shopping (detergent)" task for the washing machine. Furthermore, the processing unit 12 sends a list of the one or more tasks read out to the information processing terminal 3. Upon receiving the list message, the information processing terminal 3 of user U1 displays the list message on a display, for example, via an instant messaging application. In this way, user U1 can grasp the one or more registered tasks.

[0110] The list information includes information such as the name of the task, details of the task, the source of the task, the person in charge assigned to the task, and the difficulty level of the task for each of the one or more registered tasks. Figure 7 The displayed list includes the task name "Shopping (Detergent)", the task content "Please buy a refill of detergent (○○○)", the source of the task "Client: Washing Machine", an icon represented by a question mark indicating that no person responsible for the task has been assigned, and information indicating the difficulty level of the task "QP: 4". Figure 7 The displayed list information also includes a group name “△△△” and one or more icons indicating one or more members of the group to which the user U1 belongs.

[0111] Here, when there are multiple users U1 and each of the multiple users U1 belongs to one of the multiple groups, the content of the notification information and the overview information may be different for each of the multiple groups. Specific examples of the overview information that can be obtained for each of the multiple groups will be described below.

[0112] Figure 8 This is a schematic diagram showing an example of list information that can be obtained for each group in the first operation example of the task management system 100 according to the first embodiment. Figure 8 In the example shown, 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, while Group A and Group B are related groups, Group C is unrelated to either Group A or Group B. For a specific example, if Group A is a family member, Group B is, for example, a relative or close friend of that family member, and Group C is a third party.

[0113] like Figure 8 As shown, if "User A" is used as a reference, "User A" can obtain and browse a list of information including the contents of one or more tasks for which they are responsible. Furthermore, "User B" and "User C," who belong to the same "Group A" as "User A," can also obtain and browse a list of information including the contents of one or more tasks executed by "Group A."

[0114] "User D" belongs to a different group than "Group A", so it cannot obtain and browse the summary information including the content of one or more tasks performed by "Group A". However, "User D" belongs to "Group B" which is associated with "Group A", so it can obtain and browse the summary information including the summary of one or more tasks performed by "Group A". Figure 8In the example shown, the summary includes information indicating the number of completed tasks for one or more tasks performed by "Group A" and the number of completed tasks for one or more tasks performed by "Group B." Furthermore, "User A," "User B," and "User C," who belong to "Group A," can also access and browse this summary.

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

[0116] In addition, notification information related to "Group A" is sent to the information processing terminals 3 of "User A", "User B" and "User C" belonging to "Group A", but is not sent to the information processing terminals 3 of "User D" belonging to "Group B" and "User E" belonging to "Group C".

[0117] [2-3. Second Operation Example]

[0118] Next, use Figure 9 A second operation example of the task management system 100 according to the first embodiment will be described. Figure 9 This is a schematic diagram showing a second operation example of the task management system 100 according to Embodiment 1. 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 automatic task registration is necessary, which is set in advance by the user U1.

[0119] exist Figure 9 In the example shown, before processing unit 12 retrieves the log from the washing machine, device 2, user U1 transmits necessity information to task management system 100 via information processing terminal 3. Upon receiving the necessity information, processing unit 12 updates the first correspondence information stored in storage device 13 (task determination DB 132) based on the acquired necessity information. Here, processing unit 12 updates the first correspondence information to set the "Need to Register" field for the "Shopping (Detergent)" task to "Not Necessary" and the "Need to Register" field for the "Replenish Detergent" task to "Required."

[0120] Next, as in the first operational example, processing unit 12 retrieves a log indicating "Detergent remaining (low)" from the washing machine, device 2. Processing unit 12 then determines a task based on the retrieved log by referencing the first correspondence information stored in storage device 13 (task determination DB 132). Here, processing unit 12 determines a "Replenish detergent" task corresponding to the "Detergent remaining (low)" log and with "Registration necessary" set to "Required." Processing unit 12 then registers the determined "Replenish detergent" task in storage device 13 (task DB 131).

[0121] As described above, in the second operation example, only the tasks desired by the user U1 can be automatically registered in the storage device 13 (task DB 131 ).

[0122] [2-4. Example 3]

[0123] Next, use Figure 10 A third operation example of the task management system 100 according to the first embodiment will be described. Figure 10 This is a schematic diagram showing a third operational example of the task management system 100 according to Embodiment 1. The third operational example differs from the second operational example in that the user U1 manually registers a task to be automatically registered by operating the information processing terminal 3 .

[0124] exist Figure 10 In the example shown, before processing unit 12 retrieves the log from the washing machine, device 2, user U1 operates information processing terminal 3 and transmits operation information indicating a "Check Detergent Reserve" task corresponding to the washing machine's "Detergent Remaining Level (Low)" log to task management system 100. Upon receiving the operation information, processing unit 12 updates the first correspondence information stored in storage device 13 (task determination DB 132) based on the retrieved operation information. Here, processing unit 12 updates the first correspondence information to add the "Check Detergent Reserve" task corresponding to the washing machine's "Detergent Remaining Level (Low)" log.

[0125] Next, similar to the second example operation, processing unit 12 retrieves a log indicating "Detergent remaining (low)" from the washing machine, device 2. Processing unit 12 then determines a task based on the retrieved log by referencing the first correspondence information stored in storage device 13 (task determination DB 132). Here, processing unit 12 determines a "Replenish detergent" task and a "Check detergent reserve" task, which correspond to the "Detergent remaining (low)" log and have "Registration necessary" set to "Required." Processing unit 12 then registers the determined "Replenish detergent" and "Check detergent reserve" tasks in storage device 13 (task DB 131).

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

[0127] [2-5. Example 4]

[0128] Next, use Figure 11 A fourth operation example of the task management system 100 according to the first embodiment will be described. Figure 11This is a schematic diagram showing a fourth operation example of the task management system 100 according to Embodiment 1. 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 .

[0129] exist Figure 11 In the example shown, user U1 operates information processing terminal 3 to send operation information to task management system 100 indicating that the source device 2 is "refrigerator" and the task is "shopping (eggs)." Upon receiving the operation information, processing unit 12 updates one or more tasks stored in storage device 13 (task DB 131) based on the received operation information. Here, processing unit 12 updates one or more tasks by adding the task "shopping (eggs)" whose source device 2 is "refrigerator."

[0130] Furthermore, when the task management system 100 stores one or more tasks with a relatively high occurrence frequency, the processing unit 12 may transmit selection information indicating a list of the one or more tasks to the information processing terminal 3 of the user U1 .

[0131] Figure 12 This is a schematic diagram showing another registration method in the fourth operation example of the task management system 100 according to the first embodiment. Figure 12 In the example shown, the storage device 13 includes a task selection DB 134 that stores selection information. Furthermore, when the processing unit 12 receives operation information requesting the transmission of selection information from the information processing terminal 3 of user U1, for example, it transmits the selection information to the information processing terminal 3. User U1 operates the information processing terminal 3 and transmits operation information indicating the selection of "Shopping (eggs)" 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 by adding a task, "Shopping (eggs)," whose source device 2 is "Refrigerator."

[0132] As described above, in the fourth operation example, the user U1 can manually register a task that he or she desires.

[0133] [2-6. Example 5]

[0134] Next, use Figure 13 and Figure 14 A fifth operation example of the task management system 100 according to the first embodiment will be described. Figure 13 and Figure 14Each of these diagrams schematically illustrates the fifth operation example of the task management system 100 according to Embodiment 1. 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 .

[0135] exist Figure 13 In the example shown, user U1 operates information processing terminal 3 to send a request to task management system 100 requesting the transmission of a task list. Upon receiving the request, processing unit 12 transmits the list to information processing terminal 3. Upon receiving the list, user U1's information processing terminal 3 displays the list on a display, for example, via an instant messaging application. The list includes a "Refill Detergent" task for a washing machine and a "Shopping (Detergent)" task, but no responsible person has been assigned to either task.

[0136] Here, if Figure 14 As shown, user U1 operates information processing terminal 3 to send operation information to task management system 100 requesting that the person responsible for the "Shopping (Detergent)" task be changed to "Dad," user U1's own name. Processing unit 12, upon receiving the operation information, updates one or more tasks stored in storage device 13 (task DB 131) based on the received operation information. Here, processing unit 12 updates one or more tasks by changing the person responsible for the "Shopping (Detergent)" task to "Dad." From now on, the "Shopping (Detergent)" task for the washing machine is assigned to "Dad" in the list.

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

[0138] Furthermore, if a person responsible for a task has already been assigned, the task management system 100 can also restrict changes to the person responsible for that task as follows. In the following description, the user U1 who is the person responsible for a task already assigned is referred to as "first user U11," and another user U1 is referred to as "second user U12." In the following description, the first user U11 is referred to as "Dad," and the second user U12 is referred to as "Mom."

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

[0140] Next, the second user U12 operates the information processing terminal 3 to send an operation message 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 herself. However, because "Dad," the first user U11, is already assigned the "Shopping (Detergent)" task, the processing unit 12 does not change the person in charge of the task. Furthermore, the processing unit 12 sends a message to the information processing terminal 3 of the second user U12 indicating that the person in charge of the "Shopping (Detergent)" task cannot be changed. This allows the second user U12 to understand that a person in charge of the "Shopping (Detergent)" task has already been assigned and cannot be changed.

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

[0142] Figure 16 This is a schematic diagram showing an example of a case where the person in charge of a task can be changed by another user (second user U12) in the fifth operation example of the task management system 100 according to the first embodiment. Figure 16 In the example shown, the second condition is that a predetermined time (unchangeable period) has passed since the first user U11 was assigned to any task. The unchangeable period may be set in advance or may be set appropriately by the user U1 operating the information processing terminal 3 .

[0143] like Figure 16 As shown, if the second user U12 requests the task management system 100 to change the person in charge of the "Shopping (Detergent)" task to "Mom," which is the second user U12, during the unchangeable 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," which is the second user U12, after the unchangeable period has expired, the processing unit 12 changes the person in charge of the task to "Mom." Furthermore, the processing unit 12 sends a message to the information processing terminal 3 of the second user U12 indicating that the person in charge of the "Shopping (Detergent)" task has been changed to "Mom." Thus, the second user U12 can understand that the person in charge of the "Shopping (Detergent)" task has been changed to himself.

[0144] Furthermore, even when a person in charge has already been assigned to any task, the task management system 100 may permit a change in the person in charge of the task regardless of whether the second condition is satisfied.

[0145] Figure 17 This is a schematic diagram showing another example of the fifth operation example of the task management system 100 according to the first embodiment, in which another user (the second user U12) can change the responsibility for the task. Figure 17 As shown, 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 met. Furthermore, the processing unit 12 sends a message to the information processing terminal 3 of the second user U12 indicating that the person in charge of the "Shopping (Detergent)" task has been changed to "Mom." This allows the second user U12 to understand that the person in charge of the "Shopping (Detergent)" task has been changed to themselves.

[0146] In addition, when the task management system 100 obtains operation information sent from the information processing terminal 3 of the second user U12 requesting to change the person in charge of a task to which a person in charge has been assigned, it can also send confirmation information to the information processing terminal 3 to confirm whether the person in charge has been changed to the second user U12.

[0147] Figure 18 This is a schematic diagram showing another example of a case where another user (the second user U12) can change the person in charge of a task in the fifth action example of the task management system 100 of Implementation Method 1. When the second user U12 requests the task management system 100 to change the person in charge of the "Shopping (Detergent)" task to "Mom", which is the second user U12 himself, the processing unit 12 sends a confirmation message to the information processing terminal 3. If the information processing terminal 3 obtains the confirmation message, the second user U12 operates the information processing terminal 3 to send a message indicating the meaning of "making a change" to the task management system 100. Then, the processing unit 12 changes the person in charge of the task to "Mom". In addition, the processing unit 12 sends a message 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.

[0148] Furthermore, the task management system 100 may not permit unlimited changes in the person in charge of a task, but may limit the number of times the person in charge of a task is permitted to be changed within a predetermined period (eg, a few hours or a few days).

[0149] [2-7. Example 6]

[0150] Next, use Figure 19 A sixth operation example of the task management system 100 according to the first embodiment will be described. Figure 19 This is a schematic diagram showing the sixth operation example of the task management system 100 according to Embodiment 1. The sixth operation example differs from the first to fifth operation examples in that the processing unit 12 determines, based on the log acquired by the communication unit (acquisition unit) 11, which task has been completed among one or more tasks registered in the storage device 13 (task DB 131), and automatically updates the status of the task to "completed."

[0151] exist Figure 19 In the example shown, processing unit 12 obtains a log indicating "Detergent remaining (high)" from a washing machine, which is device 2. Processing unit 12 then refers to the second correspondence information stored in storage device 13 (task update DB 135) and determines whether the task has been completed based on the obtained log.

[0152] The second correspondence information is information indicating the correspondence between the log and the task whose status is updated to "Completed." Specifically, the second correspondence information indicates 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. Here, the processing unit 12 determines the "Shopping (Detergent)" task and the "Replenish Detergent" task corresponding to the "Detergent Remaining (Large)" log as completed tasks. Furthermore, the processing unit 12 updates the status of the "Replenish Detergent" task, which has a status of "In Progress," to "Completed," among one or more tasks registered in the storage device 13 (task DB 131).

[0153] As described above, in the sixth operation example, the processing unit 12 automatically updates the status of the completed task to “completed” based on the acquired log. Therefore, the user U1 does not need to manually change the status of the task to “completed”.

[0154] [2-8. Example 7]

[0155] Next, use Figure 20 A seventh operation example of the task management system 100 according to the first embodiment will be described. Figure 20 This is a schematic diagram showing a seventh operation example of the task management system 100 according to Embodiment 1. The seventh operation example differs from the first to sixth operation examples in that the user U1 manually updates the task status to “completed” by operating the information processing terminal 3 .

[0156] exist Figure 20In the example shown, user U1 operates information processing terminal 3 to send operation information indicating the completion of the "Shopping (Detergent)" task to task management system 100. Upon receiving the operation information, processing unit 12 updates one or more tasks stored in storage device 13 (task DB 131) based on the received operation information. Here, processing unit 12 updates one or more tasks by changing the status of the "Shopping (Detergent)" task, whose originating device 2 is a "washing machine," from "in progress" to "completed."

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

[0158] [2-9. Example 8]

[0159] Next, use Figure 21 An eighth operation example of the task management system 100 according to the first embodiment will be described. Figure 21 This is a schematic diagram showing the eighth operation example of the task management system 100 according to Embodiment 1. 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 the log acquired by the communication unit (acquisition unit) 11, and automatically deletes the determined task to be deleted from the storage device 13.

[0160] In other words, if 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 is completed based on the acquired log.

[0161] exist Figure 21 In the example shown, processing unit 12 retrieves a log indicating "Detergent remaining (high)" from a washing machine, device 2. Processing unit 12 then references the second correspondence information stored in storage device 13 (task deletion DB 133) and determines, based on the retrieved log, a task to be deleted. Processing unit 12 determines that the "Replenish detergent" task corresponding to the "Detergent remaining (high)" log has been completed and selects it as a task to be deleted. Processing unit 12 then deletes the determined "Replenish detergent" task from the one or more tasks registered in storage device 13 (task DB 131).

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

[0163] In addition, the task management system 100 may delete the task from the storage device 13 (task DB 131) not at the time when the task is determined to be completed, but after a certain time (for example, several hours or days, etc.) has passed since the time when the task is determined to be completed.

[0164] Figure 22 This is a schematic diagram showing an example of deleting a task after a certain time in the eighth operation example of the task management system 100 according to the first embodiment. The certain time may be set in advance or may be set appropriately by the user U1 operating the information processing terminal 3. Figure 22 In the example shown, if a certain amount of time has passed since the completion of the "Replenish Detergent" task for the washing machine, the processing unit 12 determines that task as a target for deletion and deletes it from the storage device 13 (task DB 131). This makes it easier to avoid situations where the user U1 is unable to understand which task has been completed when viewing the list, compared to deleting the task at the time of completion.

[0165] Furthermore, 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 (eg, 0:00), regardless of whether the tasks are completed.

[0166] Figure 23 This is a schematic diagram showing an example of deleting all tasks at a specified time (predetermined time) in the eighth operation example of the task management system 100 of 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. Figure 23 In the example shown, when the designated time comes, the processing unit 12 determines all tasks registered in the storage device 13 (task DB 131) as tasks to be deleted and deletes the determined tasks from the storage device 13. This eliminates the need for the user U1 to manually delete all registered tasks.

[0167] [2-10. Example 9]

[0168] Next, use Figure 24 A ninth operation example of the task management system 100 according to the first embodiment will be described. Figure 24 This is a schematic diagram showing a ninth operation example of the task management system 100 according to Embodiment 1. 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 .

[0169] exist Figure 24In the example shown, user U1 operates information processing terminal 3 to send operation information indicating the deletion of the "Shopping (Detergent)" task to task management system 100. Processing unit 12, upon receiving the operation information, updates one or more tasks stored in storage device 13 (task DB 131) based on the received operation information. Here, processing unit 12 updates one or more tasks by deleting the "Shopping (Detergent)" task whose originating device 2 is a "washing machine."

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

[0171] [3. Advantages, etc.]

[0172] The following describes the advantages of the task management system 100 (task management method) of Implementation 1. As described above, the task management system 100 (task management method) of Implementation 1 obtains logs related to the status of device 2 and automatically determines tasks to be performed by user U1 using device 2 based on the obtained logs. Therefore, the task management system 100 (task management method) of Implementation 1 has the following advantages: user U1 does not need to manually register or update tasks in a UI provided by an application, etc., which easily reduces the burden of task management.

[0173] (Implementation Method 2)

[0174] [1. Summary]

[0175] Below, use Figure 25 An overview of the task management system 100A according to the second embodiment will be described. Figure 25 This is a schematic diagram showing an example of executable operations of the task management system 100A according to Embodiment 2. Hereinafter, description of points in the task management system 100A according to Embodiment 2 that are common to the task management system 100 according to Embodiment 1 will be appropriately omitted.

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

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

[0178] Condition information is information indicating the conditions for automatically assigning a user U1 among multiple users U1 to a task. Figure 25 The settings are appropriately made by the user U1 operating the information processing terminal 3 .

[0179] For example, the condition information may include information indicating the degree of performance of one or more tasks other than the target task of each of the plurality of users U1. The degree of performance may include, for example, the number of times one or more tasks have been performed or the difficulty level (score) of one or more tasks.

[0180] Furthermore, for example, the condition information may include information indicating the respective status of the associated tasks of the plurality of users U1. Associated tasks are tasks associated with the target task. For example, associated tasks may include tasks associated with the same device 2 as the source device 2 of the target task, or tasks executed at the same location as the execution location of the target task.

[0181] Furthermore, for example, the condition information may include information indicating the category of the tasks assigned to each of the plurality of users U1. For example, the "shopping (eggs)" task and the "shopping (detergent)" task are of the same category.

[0182] For example, the condition information may include information indicating the outcome of a game in which multiple users U1 compete for the role of task leader. The game is a game such as roulette in which each user U1 cannot directly influence the outcome, and is executed by the information processing terminal 3 of each user U1.

[0183] like Figure 25 As shown, if the task management system 100A (1) obtains the log from the device 2, then (2) determines the task based on the log and registers the determined task in the task DB 131. In addition, the processing of these (1) and (2) may not be performed by the task management system 100A. In addition, the task management system 100A (3) determines the person in charge of the determined task (object task) based on the condition information. And, the task management system 100A (4) sends notification information indicating that the task including the person in charge has been registered to the information processing terminal 3 of the user U1. Figure 25In the example shown, there are a plurality of users U1 , and notification information is transmitted to the information processing terminals 3 of the respective users U1 .

[0184] Furthermore, similarly to the first embodiment, upon receiving request information transmitted from the information processing terminal 3 of a certain user U1 , the task management system 100A transmits the list information to the information processing terminal 3 . Figure 26 This is a schematic diagram showing an example of list information. Figure 26 The left side of the figure shows the list of information displayed on the display of the information processing terminal 3 at a time point before the person in charge is assigned to each task. Figure 26 The right side of the figure shows the list of information displayed on the display of the information processing terminal 3 at the time point after the person in charge is assigned to each task. Figure 26 In the example shown, the task management system 100A automatically assigns "Dad" as the person in charge of the "shopping (detergent)" task and the "replenishing detergent" task.

[0185] [2.Action]

[0186] The operation of the task management system 100A according to the second embodiment (ie, the task management method) will be described in detail below.

[0187] [2-1. Basic operation example]

[0188] First, use Figure 27 A basic operation example of the task management system 100A according to the second embodiment will be described. Figure 27 This is a flowchart showing a basic operation example of the task management system 100A according to Embodiment 2. Here, the description is given assuming that steps S1 and S2 in the basic operation example of the task management system 100 according to Embodiment 1 are executed. Here, the description is given of a case where there is only one user U1.

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

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

[0191] Then, the processing unit 12 transmits notification information indicating that one or more tasks registered in the storage device 13 (task DB 131) have changed 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.

[0192] The following lists specific examples of actions that can be performed by the task management system 100A according to Embodiment 2. Furthermore, in the first through sixth examples described below, the description assumes that the multiple users U1 are two users, "Dad" and "Mom." Furthermore, the task management system 100A may appropriately combine the first through sixth examples described below to perform the actions.

[0193] [2-2. Example 1]

[0194] First, use Figure 28 A first operation example of the task management system 100A according to the second embodiment will be described. Figure 28 This is a schematic diagram illustrating a first operational example of the task management system 100A according to Embodiment 2. The first operational 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 by each of the plurality of users U1 as condition information, and registers the determined person in charge in association with the target task in the storage device 13 (task DB 131).

[0195] exist Figure 28 In the example shown, the processing unit 12 determines the "Shopping (Detergent)" task (the target task) based on a log indicating "Detergent remaining (low)" from the washing machine, device 2. Furthermore, the processing unit 12 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 completed one or more tasks other than the target task, as registered in the task DB 131. The number of times each user U1 has completed tasks is the sum of the number of uncompleted (i.e., ongoing) tasks and the number of completed tasks.

[0196] Specifically, the processing unit 12 determines the user U1 with the fewest completion times among the multiple users U1 as the person in charge of the target task. Here, since "Mom" has completed the task twice and "Dad" has completed the task once, the processing unit 12 determines "Dad" as the person in charge of the target task "Shopping (Detergent)". The processing unit 12 then associates "Dad" with the target task "Shopping (Detergent)" and registers it in the storage device 13 (task DB 131).

[0197] In addition, if Figure 29 As shown, the processing unit 12 may determine the person in charge of the target task by referring to the points obtained by each user U1 registered in the storage device 13 (task DB 131 ). Figure 29 This 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 the second embodiment.

[0198] As described above, points represent the difficulty of a task. That is, the processing unit 12 may determine the person in charge of a target task based on the difficulty of one or more tasks other than the target task. Furthermore, the points for each task may be pre-set or appropriately set by any one of the multiple users U1 operating the information processing terminal 3. Furthermore, the points for each task may be set only by authorized users U1 among the multiple users U1.

[0199] exist Figure 29 In the example shown, the processing unit 12 determines the person in charge of the target task by referring to the points obtained by each user U1 registered in the storage device 13 (task DB 131). Specifically, the processing unit 12 determines the user U1 with the fewest points among the multiple users U1 as the person in charge of the target task. Here, since "Mom" has 4+2=6 points and "Dad" has 2 points, the processing unit 12 determines "Dad" as the person in charge of the "Shopping (Detergent)" task, which is the target task. Furthermore, the processing unit 12 associates "Dad", the person in charge, with the "Shopping (Detergent)" task, which is the target task, and registers them in the storage device 13 (task DB 131).

[0200] As described above, in the first operation example, the person in charge of the target task is determined based on the degree of performance of the task by each user U1 . Therefore, the person in charge of each task is less likely to be misaligned.

[0201] [2-3. Second Operation Example]

[0202] Next, use Figure 30 A second operation example of the task management system 100A according to the second embodiment will be described. Figure 30 This is a schematic diagram illustrating a second example operation of the task management system 100A according to Embodiment 2. The second example operation is a specific example of processing in which the processing unit 12 determines a person in charge based on the respective status of the related tasks of multiple users U1 as condition information, and associates the determined person in charge with the target task and registers the associated person in the storage device 13 (task DB 131). As described above, the associated task is a task associated with the target task.

[0203] exist Figure 30In the example shown, the processing unit 12 determines the "Shopping (Detergent)" task (first target task) and the "Replenish Detergent" task (second target task) based on a log indicating "Detergent Remaining (Low)" from the washing machine, device 2. Furthermore, the processing unit 12 determines the responsible persons for the first and second target tasks by referring to the condition information stored in the storage device 13 (task DB 131). Here, the processing unit 12 determines the responsible persons for the first and second target tasks by referring to the responsible status of the related tasks for each user U1 registered in the task DB 131.

[0204] Specifically, from the perspective of "shopping," the "shopping (eggs)" task registered in the storage device 13 (task DB 131) is associated with the "shopping (detergent)" task, which is the first target task. Therefore, the processing unit 12 determines that "Mom," who is the person in charge of the "shopping (eggs)" task, is the person in charge of the "shopping (detergent)" task. In addition, from the perspective of "washing machine," the "shopping (detergent)" task, which is the first target task, is associated with the "replenishing detergent" task, which is the second target task. Therefore, the processing unit 12 further determines that "Mom," who was determined to be the person in charge of the "shopping (detergent)" task, is the person in charge of the "replenishing detergent" task. Furthermore, the processing unit 12 associates "Mom," who is determined to be the person in charge, with the "shopping (detergent)" task, which is the first target task, and the "replenishing detergent" task, which is the second target task, and registers them in the storage device 13 (task DB 131).

[0205] As described above, in the second operation example, the same person in charge can be assigned to two or more efficient tasks during centralized execution, so the person in charge can easily execute the tasks efficiently.

[0206] [2-4. Example 3]

[0207] Next, use Figure 31 A third operation example of the task management system 100A according to the second embodiment will be described. Figure 31 This is a schematic diagram illustrating a third operational example of the task management system 100A according to Embodiment 2. The third operational example is a specific example of processing in which the processing unit 12 determines a person in charge based on the categories of tasks assigned to each of the plurality of users U1 as condition information, and registers the determined person in charge in association with the target tasks in the storage device 13 (task DB 131).

[0208] The type of task may be appropriately set by any one of the plurality of users U1 operating the information processing terminal 3. Alternatively, the type of task may be set only by the authorized user U1 among the plurality of users U1.

[0209] exist Figure 31 In the example shown, the processing unit 12 determines the "Shopping (Detergent)" task (the target task) based on the "Detergent Remaining Amount (Low)" log from the washing machine, device 2. Furthermore, the processing unit 12 determines the 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 the person in charge of the target task by referring to the task categories assigned to each user U1, which are registered in the condition DB 136.

[0210] Specifically, for tasks belonging to the "Shopping" category, "Dad" is responsible for 100% and "Mom" is not responsible. On the other hand, for tasks belonging to the "Washing" category, "Dad" is responsible for 60% and "Mom" is responsible for 40%. Here, the target task, "Shopping (Detergent)", belongs to the "Shopping" category, 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" with the target task, "Shopping (Detergent)", and registers it in the storage device 13 (task DB 131).

[0211] As described above, in the third operation example, the person in charge of the target task is determined based on the type of the task assigned to each user U1 . Therefore, the person in charge to whom the target task is assigned is less likely to be dissatisfied.

[0212] [2-5. Example 4]

[0213] Next, use Figure 32 A fourth operation example of the task management system 100A according to the second embodiment will be described. Figure 32 This is a schematic diagram showing a 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 operation example and the third operation example.

[0214] exist Figure 32 In the example shown, processing unit 12 determines a "Shopping (Detergent)" task (first target task) and a "Replenish Detergent" task (second target task) based on a log indicating "Detergent Remaining (Low)" from a washing machine, device 2. Furthermore, processing unit 12 determines the responsible persons for the first and second target tasks, respectively, by referring to the condition information stored in storage device 13 (task DB 131 and condition DB 136).

[0215] Here, the processing unit 12 first determines the person in charge of the first target task by referring to the associated task status of each user U1 registered in the storage device 13 (task DB 131). Specifically, from the perspective of "shopping," the "shopping (eggs)" task registered in the task DB 131 is associated with the "shopping (detergent)" task, which is the first target task. Therefore, the processing unit 12 determines "Mom," who is the person in charge of the "shopping (eggs)" task, as the person in charge of the "shopping (detergent)" task.

[0216] Next, the processing unit 12 determines the person in charge of the second target task by referring to the categories of tasks assigned to each user U1 and registered in the storage device 13 (condition DB 136). Specifically, for tasks belonging to the "overall" category, "Dad" is responsible for 50% and "Mom" is responsible for 50%. Therefore, the processing unit 12 determines that "Dad" is the person in charge of the "replenishing detergent" task, which is the second target task, so that the number of tasks "Dad" is responsible for and the number of tasks "Mom" is responsible for is 50%:50%. The processing unit 12 then associates "Mom", the person in charge, with the "shopping (detergent)" task, which is the first target task, and registers "Dad", the person in charge, as associated with the "replenishing detergent" task, which is the second target task, in the storage device 13 (task DB 131).

[0217] As described above, in the fourth example, when executing two or more efficient tasks in a centralized manner, the same person in charge can be assigned to each task, making it easier for the person in charge to execute the tasks efficiently. Furthermore, in the fourth example, the person in charge of the target task is determined based on the type of task assigned to each user U1, so the person in charge of the assigned task is less likely to become dissatisfied.

[0218] [2-6. Example 5]

[0219] Next, use Figure 33 A fifth operation example of the task management system 100A according to the second embodiment will be described. Figure 33 This is a schematic diagram illustrating a 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 based on the outcome of a game in which multiple users U1 participate with the person in charge of the target task as the bet target, and registers the determined person in charge in association with the target task in the storage device 13 (task DB 131).

[0220] As described above, the game is a game in which each user U1 cannot directly control the outcome, such as roulette, and is executed by each user U1's information processing terminal 3. Alternatively, the game may be a game in which each user U1 can directly control the outcome, such as rock-paper-scissors, card games, or table games.

[0221] exist Figure 33 In the example shown, processing unit 12 determines a "Shopping (Detergent)" task (target task) based on a log indicating "Detergent remaining (low)" from a washing machine, device 2. Processing unit 12 also determines the person in charge of the target task by referring to condition information stored in storage device 13 (task DB 131, etc.).

[0222] Specifically, the processing unit 12 causes the information processing terminal 3 of each user U1 to execute a game (here, a roulette game). Furthermore, the processing unit 12 determines the user U1 who wins the game (in other words, is selected) as the person in charge of the target task. The probability of winning the game (win rate) is determined based on the number of times each user U1 performs one or more tasks other than the target task registered in the storage device 13 (task DB 131). Here, the number of times "Mom" performs the task is 2 times, and the number of times "Dad" performs the task is 1 time, so the probability of winning the game for "Mom" is determined to be 33.3% (≈100-100×2 / 3)%, and the probability of winning the game for "Dad" is determined to be 66.7% (≈100-100×1 / 3)%. In addition, the probability of winning the game can also be determined based on the points obtained by each user U1, for example.

[0223] exist Figure 33 In the example shown, the winner of the game is "Dad," so the processing unit 12 determines "Dad" as the person in charge of the target task, "Shopping (Detergent)." Furthermore, the processing unit 12 associates "Dad," the person in charge, with the target task, "Shopping (Detergent)," and registers the association in the storage device 13 (task DB 131).

[0224] 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 the person in charge to whom the target task is assigned is less likely to feel dissatisfied.

[0225] [2-7. Example 6]

[0226] Next, use Figure 34 A sixth operation example of the task management system 100A according to the second embodiment will be described. Figure 34 This is a schematic diagram illustrating the sixth example operation of the task management system 100A according to Embodiment 2. The sixth example operation differs from the first to fifth examples in that a person responsible for the target task has already been assigned. Furthermore, the sixth example operation is a specific example of processing in which the processing unit 12 re-determines the person responsible for the target task based on environmental information indicating a change in the environment in which the target task exists.

[0227] Environmental information may include, for example, information indicating changes in the weather at the location where the target task is to be performed, such as a change from sunny to rainy. Processing unit 12 may obtain this information by, for example, obtaining weather information from a server providing weather information via communication unit 11. Furthermore, environmental information may include information indicating changes in the presence / absence of the person in charge of the target task, such as delays in their return home due to transportation disruptions such as train delays. Processing unit 12 may obtain this information by, for example, obtaining location information (e.g., positioning information from a positioning system such as GPS (Global Positioning System)) of the information processing terminal 3 of the person in charge of the target task via communication unit 11.

[0228] exist Figure 34 In the example shown, "Dad" has been assigned to the person in charge of the "Laundry Pickup" task (the target task) in storage device 13 (task DB 131). Upon receiving weather information indicating a change from sunny to rainy, processing unit 12 determines that the target task should be prioritized. Furthermore, processing unit 12 determines whether the person in charge of the target task is home or absent by referencing the presence / absence information of each user U1 stored in storage device 13 (presence / absence DB 137).

[0229] Here, because the person in charge of the target task, "Laundry Pickup," is away, the processing unit 12 updates the person in charge of the target task by changing it to "Mom," who is at home. The processing unit 12 then sends a notification message to the information processing terminal 3 of each user U1. This allows "Mom" to understand that the target task, "Laundry Pickup," should be executed.

[0230] 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 exists, so it is easy to make an appropriate person in charge execute the target task.

[0231] [3. Advantages, etc.]

[0232] The following describes the advantages of the task management system 100A (task management method) of embodiment 2. As described above, the task management system 100A (task management method) of embodiment 2 automatically determines the person in charge of a task (target task) performed by a certain user U1 among multiple users U1 based on condition information representing conditions related to the tasks of each of the multiple users U1. Therefore, the task management system 100A (task management method) of embodiment 2 has the following advantages: the user does not need to manually assign a person in charge in the UI provided by the application, etc., which easily reduces the load for managing tasks. In addition, in the task management system 100A (task management method) of embodiment 2, tasks are automatically assigned to a person in charge, so there is also the following advantage: it is easy to avoid situations where the user U1 feels pressured by being rejected or having an argument with another user U1 when assigning the person in charge of the task to the user U1.

[0233] (Implementation 3)

[0234] [1. Summary]

[0235] Below, use Figure 35 An overview of the task management system 100B according to the third embodiment will be described. Figure 35 This is a schematic diagram showing an example of executable operations of the task management system 100B according to Embodiment 3. Hereinafter, description of points in the task management system 100B according to Embodiment 3 that are common to the task management system 100 according to Embodiment 1 will be appropriately omitted.

[0236] In the third embodiment, the processing unit 12 of the task management system 100B generates pattern information indicating an action pattern to be performed on the device 2 during a predetermined time period based on the acquired log. Furthermore, if the acquired log does not contain the action pattern indicated by the pattern information during the predetermined time period, the processing unit 12 determines that the action pattern is an urgent task.

[0237] An urgent task is a task that user U1 using device 2 should perform. More specifically, an urgent task is a task recommended for user U1 to perform immediately. Furthermore, determining an urgent task means registering the task in storage device 13 (task DB 131) and increasing the importance of the registered task if no task corresponding to the action pattern is registered in storage device 13 (task DB 131). Alternatively, determining an urgent task means increasing the importance of the task if the task is already registered in storage device 13.

[0238] Importance, also known as urgency, indicates whether a task should be prioritized by user U1. In Embodiment 3, importance is represented by three levels: "small," "medium," and "high." Tasks with "small" importance can be performed by user U1 at an appropriate time and do not need to be prioritized. Tasks with "medium" importance are recommended for priority over tasks with "small" importance. Tasks with "high" importance are tasks that user U1 should perform immediately and are the highest priority.

[0239] Processing unit 12, for example, stores a predetermined number of logs acquired by acquisition unit 11 and performs statistical processing, such as finding the most frequent value, on the stored predetermined number of logs to generate pattern information. Alternatively, processing unit 12 may use a plurality of logs as learning data and generate pattern information using a learned model that has been learned through machine learning using the logs acquired by acquisition unit 11 as input and outputting pattern information.

[0240] Figure 36 This is a diagram showing an example of generating pattern information. Figure 36 In the example shown, the processing unit 12 generates pattern information indicating an action pattern of "setting a cooking start timer (16:00)" on a rice cooker and an action pattern of "starting cooking at around 7:00 on a weekday" and an action pattern of "starting cooking at 16:00 on a weekday" based on multiple logs indicating that the "cooking start timer (16:00)" operation was performed on a rice cooker and that this operation was performed between 7:00 and 7:30 on a weekday. Furthermore, the processing unit 12 generates pattern information indicating an action pattern of "performing a drum cleaning cycle at the end of each month" based on multiple logs indicating that the "drum cleaning cycle" operation was performed on a washing machine and that this operation was performed between 22:00 and 22:30 at the end of the month.

[0241] Figure 37 is a diagram showing another example of generating pattern information. Figure 37 In the example shown, the processing unit 12 generates pattern information indicating an action pattern of "weighing every day" based on multiple logs indicating that a scale operation was performed "weighing" and that this operation was performed between 6:30 and 7:00 every day. Furthermore, the processing unit 12 generates pattern information indicating an action pattern of "blood pressure measurement every day" based on multiple logs indicating that a blood pressure monitor operation was performed "blood pressure measurement" and that this operation was performed between 6:30 and 7:00 every day. Since these action patterns share a common time period and are performed every day, the processing unit 12 generates pattern information that aggregates these action patterns into a single action pattern of "weighing and blood pressure measurement every day." The pattern information generated by the processing unit 12 is stored in the pattern DB 138 of the storage device 13.

[0242] return Figure 35 , the task management system 100B, if (1) obtaining the log from the device 2, then (2) determines the task based on the log and registers the determined task in the task DB 131. In addition, the task management system 100B, (3) determines the person in charge of the determined task (object task) based on the condition information. And, the task management system 100B, (4) sends notification information indicating that the task including the person in charge has been registered to the information processing terminal 3 of the user U1. Figure 35 In the example shown, there are a plurality of users U1, and notification information is transmitted to the information processing terminals 3 of the respective users U1. The plurality of users U1 are, for example, family members.

[0243] Furthermore, after (1) acquiring the log from the device 2, the task management system 100B then (5) determines an emergency task by referring to the pattern information stored in the storage device 13 (pattern DB 138). Furthermore, the task management system 100B (6) transmits emergency notification information indicating the occurrence of the emergency task to the information processing terminal 3 of each user U1. Furthermore, the processes (2) to (4) above do not necessarily need to be performed by the task management system 100B.

[0244] Figure 38 This is a schematic diagram showing an example of notification of emergency notification information in the task management system 100B according to the third embodiment. Figure 38 (a) shows a list of emergency notification information. Figure 38 (b) indicates notification information as emergency notification information. Figure 38 In the example shown in (a) of FIG. 1 , as shown in the area surrounded by the dotted line, the content of the urgent task "rice cooking start reservation" is displayed on the display of the information processing terminal 3 .

[0245] In addition, Figure 38 In the example shown in (b), as shown in the area surrounded by the dotted line, a message indicating that an emergency task has occurred regarding the rice cooker and a hyperlink for making a reservation for starting the cooking action of the rice cooker through a remote operation such as "cooking reservation" are displayed on the display of the information processing terminal 3.

[0246] In this way, the processing unit 12 may include information for remotely operating the device 2 (here, the rice cooker) that is the target of the emergency task in the emergency notification information and send it to the information processing terminal 3 of each user U1. Alternatively, the processing unit 12 may send the emergency notification information to the information processing terminal 3 of each user U1 without including the information for remote operation.

[0247] In addition, Figure 38In the example shown, the area surrounded by the dotted line can also be displayed in a manner that visually emphasizes other areas. For example, if a character string is displayed in black in other areas, the character string can be displayed in red in the area surrounded by the dotted line. Furthermore, for example, the area surrounded by the dotted line can be displayed at the upper side of the display relative to other areas.

[0248] [2.Action]

[0249] Hereinafter, the operation of the task management system 100B according to the third embodiment (ie, the task management method) will be described in detail.

[0250] [2-1. Basic operation example]

[0251] First, use Figure 39 A basic operation example of the task management system 100B according to the third embodiment will be described. Figure 39 This is a flowchart showing a basic operation example of the task management system 100B according to Embodiment 3. Here, the description is given assuming that the task management system 100B obtains a log from the device 2. In addition, the description is given here of a case where there is only one user U1.

[0252] 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. As a result, the communication unit (acquisition unit) 11 acquires the log via the network N1 (S21).

[0253] Next, the processing unit 12 generates pattern information indicating the behavior pattern based on the logs acquired by the communication unit (acquisition unit) 11 (S22). Step S22 need not 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.

[0254] Next, the processing unit 12 determines whether the log of the specified time period contains the action pattern (S23). Here, the processing unit 12 refers to the pattern information stored in the storage device 13 (pattern DB 138) to determine whether the action pattern executed in the specified time period is included in the log of the specified time period.

[0255] If the log of the predetermined time period does not include the action pattern (S23: No), the processing unit 12 determines an urgent task (S24). Here, the processing unit 12 determines the action pattern as an urgent task.

[0256] Then, the processing unit 12 sends emergency notification information indicating that an emergency task has occurred to the information processing terminal 3 of the user U1 (S25). If the log of the predetermined time period contains an action pattern (S23: Yes), the processing unit 12 does not execute steps S24 and S25.

[0257] The following lists specific examples of actions that can be performed by the task management system 100B according to Implementation 3. Furthermore, in the first and second examples below, the description is based on the assumption that the multiple users U1 are "Dad" and "Mom." Furthermore, in the first and second examples below, the description is based on the assumption that pattern information has already been generated. Furthermore, the task management system 100B may also perform an appropriate combination of the first and second examples below.

[0258] [2-2. Example 1]

[0259] First, use Figure 40 A first operation example of the task management system 100B according to the third embodiment will be described. Figure 40 This is a schematic diagram showing a first operational example of the task management system 100B according to Embodiment 3. The first operational example is a specific example of a process in which the processing unit 12 determines an urgent task by referring to the mode information.

[0260] exist Figure 40 In the example shown, device 2 is a rice cooker. The rice cooker is usually set to "cooking start reservation" during the time period of 7:00 to 7:30, and a signal including a log indicating that the "cooking start reservation" operation was performed during this time period is sent to the task management system 100B. Figure 40 In the example shown, since the "rice cooking start reservation" operation is not performed in the time period, the rice cooker does not transmit a signal including a log indicating that the "rice cooking start reservation" operation is performed in the time period to the task management system 100B.

[0261] Since the action pattern of "cooking start reservation" is not included in the log, the processing unit 12 of the task management system 100B determines the action pattern of "cooking start reservation" as an urgent task and sends the urgent notification information to the information processing terminal 3 of each user U1. Figure 40 In the example shown, the processing unit 12 usually determines whether the log includes the action pattern of "rice cooking start reservation" at a predetermined time (here, 2 hours) before 16:00 when the rice cooker starts cooking.

[0262] exist Figure 40 In the example shown, one of the multiple users U1 sees the emergency notification information received by the information processing terminal 3, recognizes that an emergency task, "pre-set cooking," has occurred, and remotely controls the rice cooker to "pre-set cooking" (i.e., completes the emergency task). As a result, the rice cooker starts cooking at the scheduled time (here, 4 p.m.).

[0263] Here, in the first operation example, the processing unit 12 executes different processes when the determined urgent task is not registered in the storage device 13 (task DB 131 ) and when the determined urgent task is registered.

[0264] Figure 41 This 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 100B according to the third embodiment. Figure 41 In the example shown, processing unit 12 determines the action pattern "Reserve the start of cooking (16:00)" included in the pattern information stored in storage device 13 (pattern DB 138) as an urgent task. Furthermore, since the "Reserve the start of cooking (16:00)" task is not registered in storage device 13 (task DB 131), processing unit 12 registers the "Reserve the start of cooking (16:00)" task in storage device 13 with its importance set to "High." Consequently, the "Reserve the start of cooking (16:00)" task is registered in storage device 13 as an urgent task.

[0265] Figure 42 This is a schematic diagram showing an example of registering a determined urgent task in the first operation example of the task management system 100B according to the third embodiment. Figure 42 In the example shown, Figure 41 In the example shown, processing unit 12 determines the action pattern "Reserve the start of cooking (16:00)" included in the pattern information stored in storage device 13 (pattern DB 138) as an urgent task. Furthermore, since the "Reserve the start of cooking (16:00)" task is already registered in storage device 13 (task DB 131), processing unit 12 updates the "Reserve the start of cooking (16:00)" task by changing its importance from "Medium" to "High." Consequently, the "Reserve the start of cooking (16:00)" task is registered in storage device 13 as an urgent task.

[0266] As described above, in the first example operation, when a task (action pattern) that should have been executed is not executed, the task is determined to be an urgent task, and urgent notification information is sent to the information processing terminal 3 of each user U1. Therefore, in the first example operation, each user U1 is more likely to notice the task (urgent task) that was forgotten to be executed, and it is easier to avoid the situation where the task is left unexecuted and put on hold.

[0267] [2-3. Second Operation Example]

[0268] Next, use Figure 43 A second operation example of the task management system 100B according to the third embodiment will be described. Figure 43This is a schematic diagram showing a 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 based on environmental information indicating changes in the environments of one or more tasks registered in the storage device 13 (task DB 131).

[0269] Environmental information may include, for example, information indicating changes in the weather at the location where the target task is to be performed, such as a change from sunny to rainy. The processing unit 12 may obtain this information, for example, by obtaining weather information from a server providing weather information via the communication unit (acquisition unit) 11. Furthermore, environmental information may include information indicating changes in the presence / absence of the person in charge of the target task, such as delays in their return home due to transportation disruptions such as train delays. The processing unit 12 may obtain this information, for example, by obtaining 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.

[0270] exist Figure 43 In the example shown, the "Laundry Loading" task is already registered in storage device 13 (task DB 131). Upon receiving weather information indicating a change from sunny to rainy, processing unit 12 determines that this task should be prioritized. Furthermore, processing unit 12 changes the task's importance from "Medium" to "High," registering it as an urgent task.

[0271] Furthermore, the processing unit 12 determines whether the person in charge of the urgent task is home or away by referring to the presence / absence information of each user U1 stored in the storage device 13 (presence / absence DB 137). Here, since "Dad," the person in charge of the urgent task "Taking in Laundry," is away, the processing unit 12 updates the person in charge of the urgent task by changing it to "Mom," who is at home. The processing unit 12 then sends an emergency notification message to the information processing terminal 3 of each user U1. This allows "Mom" to understand that the urgent task "Taking in Laundry" should be performed.

[0272] As described above, in the second example operation, an urgent task is determined based on changes in the environment of one or more tasks registered in the storage device 13 (task DB 131), and urgent notification information is transmitted to the information processing terminal 3 of each user U1. Therefore, in the second example operation, each user U1 is easily aware of tasks that need to be executed due to changes in the environment (urgent tasks), and it is easier to avoid situations where such tasks are left unexecuted and put on hold.

[0273] In addition, in the above description, it is assumed that multiple users U1 are a group such as family members, but the present invention is not limited to this. Figure 44As shown, the plurality of users U1 may also include a plurality of (here, two) groups. Figure 44 This is a schematic diagram showing an example of notification destinations of emergency notification information in the task management system 100B according to the third embodiment.

[0274] exist Figure 44 In the example shown, "Group α" consists of family members, and "Group β" consists of grandparents. In this case, if an urgent task occurs within "Group β," the processing unit 12 of the task management system 100B transmits urgent notification information not only to the information processing terminals 3 of each user U1 belonging to "Group β," but also to the information processing terminals 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 within "Group β," allowing them to perform the urgent task even if they forgot to do so.

[0275] [3. Advantages, etc.]

[0276] The advantages of the task management system 100B (task management method) of embodiment 3 are described below. As described above, the task management system 100B (task management method) of embodiment 3 generates pattern information indicating an action pattern to be performed on the device 2 during a specified time period based on the obtained log. Furthermore, the task management system 100B (task management method) of embodiment 3 determines the action pattern as an urgent task when the action pattern indicated by the pattern information is not included in the obtained log during the specified time period. Therefore, in the task management system 100B (task management method) of embodiment 3, usually, when a task (action pattern) that should have been performed is not performed, the task is determined to be an urgent task, and thus has the advantage that each user U1 can easily notice a task (urgent task) that has been forgotten to be performed, and can easily avoid the situation where the task is shelved without being performed.

[0277] (Variation)

[0278] As described above, Embodiments 1 to 3 have been described as examples of the technology disclosed in this application. However, the technology disclosed herein is not limited thereto and can be applied to Embodiments 1 to 3 with appropriate modifications, substitutions, additions, or omissions. Furthermore, the components described in Embodiments 1 to 3 can be combined to create new Embodiments 1 to 3.

[0279] Therefore, modified examples of Embodiments 1 to 3 are described below.

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

[0281] For example, the task management system 100 may include only the aforementioned registration function. Specifically, in the task management method, a log related to the status of device 2 is acquired through communication with device 2 or an external system that manages device 2. Based on the acquired log, the task to be performed by user U1 utilizing device 2 is determined. The determined task is then registered in the storage device 13.

[0282] Alternatively, for example, the task management system 100 may include only the aforementioned update function. Specifically, in the task management method, a log regarding the status of device 2 is acquired through communication with device 2 or an external system that manages device 2. Based on the acquired log, the task to be executed by user U1 utilizing device 2 is determined. In this task management method, the content of a task of the same type as the determined task registered in the storage device 13 is updated with the content of the determined task.

[0283] In the third embodiment described above, the processing unit 12 of the task management system 100B may also determine whether to send an emergency notification based on, for example, schedule information indicating the schedule of each user U1. For example, if the processing unit 12 determines the "reserve to start cooking" task as an urgent task, then the emergency notification may not be sent if the schedule information indicates that each user U1 is dining out.

[0284] In the third embodiment described above, the processing unit 12 of the task management system 100B may also modify the importance 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 a sports event on the weekend, the processing unit 12 may estimate that there is a high probability of eggs being included in the lunch box prepared for the sports event, and therefore may increase the importance of the "Shopping (Eggs)" task. Alternatively, if a task such as "Making Fried Rice" is registered in the storage device 13, the processing unit 12 may also increase the importance of the "Shopping (Eggs)" task also registered in the storage device 13.

[0285] In the above-mentioned embodiments 1 to 3, the task management systems 100, 100A, and 100B may also be implemented by a device other than the server 1. In addition, for example, in the above-mentioned embodiments 1 to 3, the task management systems 100, 100A, and 100B are implemented as a single device, but may also be implemented by multiple devices. In the case where the system is implemented by multiple devices, the components of the task management systems 100, 100A, and 100B may be arbitrarily distributed to multiple devices. For example, in the above-mentioned embodiments 1 to 3, part of the components of the task management systems 100, 100A, and 100B may also be set up in the facility where the user U1 lives. That is, the present disclosure may be implemented by cloud computing or by edge computing.

[0286] Furthermore, for example, all or part of the components of the task management system 100, 100A, and 100B of the present disclosure may be formed by dedicated hardware, or may be implemented by executing software programs suitable for each component. Each component may also be implemented 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 a semiconductor memory.

[0287] Furthermore, the components of the task management systems 100, 100A, and 100B in the present disclosure may also be composed of one or more electronic circuits, which may be general-purpose circuits or dedicated circuits.

[0288] One or more electronic circuits may include, for example, semiconductor devices, ICs (Integrated Circuits), or LSIs (Large Scale Integrations). ICs or LSIs can be integrated into a single chip or multiple chips. While referred to herein as ICs or LSIs, the terminology varies depending on the degree of integration and may also be referred to as system LSIs, VLSIs (Very Large Scale Integrations), or ULSIs (Ultra Large Scale Integrations). Field Programmable Gate Arrays (FPGAs), which are programmed after LSI manufacturing, can also be used for the same purpose.

[0289] In addition, the overall or specific technical solutions of the present disclosure may also be implemented through a system, device, method, integrated circuit or computer program. Alternatively, it may be implemented through a computer-readable non-temporary recording medium such as an optical disc, HDD or semiconductor memory storing the computer program. For example, the present disclosure may also be implemented as a program for causing a computer to execute the task management method in the above-mentioned embodiments 1 to 3. In addition, the program may be recorded on a computer-readable non-temporary recording medium such as a CD-ROM, or distributed through a communication path such as the Internet.

[0290] Furthermore, for example, the above-mentioned program is not limited to a program executed by a single computer, and may be a program executed in a distributed manner by a plurality of computers.

[0291] As described above, Embodiments 1 to 3 have been described as examples of the technology in the present disclosure. Therefore, drawings and detailed descriptions are provided.

[0292] Therefore, the components described in the drawings and detailed descriptions include not only components essential for solving the problems but also components that are not essential for illustrating the above-mentioned technology. Therefore, it should not be directly assumed that these non-essential components are essential just because they are described in the drawings and detailed descriptions.

[0293] Furthermore, the above-described Embodiments 1 to 3 are provided to illustrate the technology of the present disclosure, and therefore various changes, substitutions, additions, omissions, etc. can be made within the scope of the claims or their equivalents.

[0294] (Summarize)

[0295] As described above, in the first embodiment of the task management method, a log related to the status of device 2 is acquired (S1) by communicating with device 2 or an external system that manages device 2. In this task management method, a task to be executed by user U1 using device 2 is determined based on the acquired log (S2).

[0296] Thus, the tasks executed by the user U1 using the device 2 are automatically determined based on the obtained logs. This has the advantage that the user U1 does not need to manually register or update tasks in the UI provided by the application, etc., and the load for managing tasks can be easily reduced.

[0297] In the second aspect of the task management method, in the first aspect, when the type of the determined task is different from the type of one or more tasks registered in the storage device 13 ( S3 : YES), the determined task is registered in the storage device 13 ( S4 ).

[0298] As a result, the new task is automatically registered in the storage device 13 , which has the advantage that the user U1 does not need to manually register the new task.

[0299] In addition, in the task management method of the third mode, in the first or second mode, when the type of the determined task is the same as the type of one of the one or more tasks registered in the storage device 13 (S3: No), the content of the task is updated to the content of the determined task (S5).

[0300] Thus, among one or more tasks registered in the storage device 13 , tasks with changed contents are automatically updated, which has the advantage that the user U1 does not need to manually update the registered tasks.

[0301] In the task management method of the fourth embodiment, in any of the first to third embodiments, when one or more tasks registered in the storage device 13 are changed, notification information indicating the change is sent to the information processing terminal 3 used by the user U1 (S6).

[0302] This allows the user U1 to obtain notification information via the information processing terminal 3 , thereby providing an advantage in that the user U1 can understand that a new task has been registered or a registered task has been updated.

[0303] In the task management method of the fifth aspect, in the fourth aspect, there are multiple users U1, each of which belongs to one of the multiple groups, and the notification information has different contents in each of the multiple groups.

[0304] This provides an advantage in that the content of the notification information differs for each group, making it easy to avoid a situation in which the notification information of a certain group is known by the user U1 of another group.

[0305] Furthermore, in the task management method of the sixth aspect, in any one of the first to fifth aspects, if any one of the one or more tasks registered in the storage device 13 satisfies the first condition, the task is deleted from the storage device 13 .

[0306] Thus, if the first condition is satisfied, the task is automatically deleted, which provides an advantage in that the user U1 does not need to manually delete the task.

[0307] Furthermore, in the task management method according to the seventh aspect, in the sixth aspect, the first condition includes determining that the task is completed based on the acquired log.

[0308] This provides an advantage in that the completed task is automatically deleted based on the acquired log, and thus the user U1 does not need to manually delete the task.

[0309] Furthermore, in the task management method according to an eighth aspect, in the sixth or seventh aspect, the first condition includes a lapse of a predetermined time (a fixed time) after the task is determined to be completed.

[0310] This has the advantage of easily avoiding a situation where the user U1 cannot understand which task has been completed, compared to a case where the task is deleted at the time of completion.

[0311] Furthermore, in the task management method of the ninth aspect, in any one of the first to eighth aspects, at a predetermined time (designated time), all of one or more tasks registered in the storage device 13 are deleted from the storage device 13 .

[0312] As a result, all registered tasks are deleted at the designated time, which provides an advantage in that the user U1 does not need to manually delete all registered tasks.

[0313] In addition, in the task management method of the tenth mode, in any one of the first to ninth modes, when the first user U11 is assigned to the person in charge of one of one or more tasks stored in the storage device 13, when the second condition is met, it is permitted to change the person in charge of the task from the first user U11 to the second user U12.

[0314] Thus, the person in charge of the task to which the person in charge has been assigned is prohibited from being changed until the second condition is satisfied. This has the advantage of easily avoiding a situation where the person in charge is confused by a sudden change of the person in charge.

[0315] Furthermore, in the task management method of the eleventh aspect, in the tenth aspect, the second condition includes a lapse of a predetermined time (unchangeable period) after the first user U11 is assigned to the task.

[0316] This allows the person in charge of a task to be changed when a predetermined time has passed since the person in charge of the task was assigned, thereby advantageously preventing a situation in which a task is left unexecuted.

[0317] Furthermore, the program according to the twelfth aspect causes one or more processors to execute the task management method according to any one of the first to eleventh aspects.

[0318] Thus, the tasks executed by the user U1 using the device 2 are automatically determined based on the acquired logs. This has the advantage that the user U1 does not need to manually register or update tasks in the UI provided by the application, etc., and the load for managing tasks can be easily reduced.

[0319] Furthermore, the task management system 100 of the thirteenth embodiment includes an acquisition unit (communication unit) 11 and a processing unit 12. The acquisition unit 11 acquires a log related to the status of the device 2 by communicating with the device 2 or an external system that manages the device 2. The processing unit 12 determines the task to be executed by the user U1 who uses the device 2 based on the log acquired by the acquisition unit 11.

[0320] Thus, the tasks executed by the user U1 using the device 2 are automatically determined based on the obtained logs. This has the advantage that the user U1 does not need to manually register or update tasks in the UI provided by the application, etc., and the load for managing tasks can be easily reduced.

[0321] Industrial Applicability

[0322] The present disclosure can be applied to a system or the like that manages tasks performed by users utilizing devices.

[0323] Description of Reference Numerals

[0324] 1 server

[0325] 11 Acquisition Department (Communications Department)

[0326] 12 Processing Department

[0327] 13 Storage Device

[0328] 131 Task DB

[0329] 132 Task Decision DB

[0330] 133 Task deletion DB

[0331] 134 Task Selection DB

[0332] 135 Task Update DB

[0333] 136 Condition DB

[0334] 137 In / Out of DB

[0335] 138 Pattern DB

[0336] 2 Equipment

[0337] 3 Information processing terminal

[0338] 100,100A,100B Task Management System

[0339] N1 Network

[0340] U1 users

[0341] U11 first user

[0342] U12 Second User

Claims

1. A task management method, wherein: By communicating with the device or an external system that manages the device, logs related to the status of the device are obtained. Based on the acquired log, a task performed by the user utilizing the device is determined.

2. The task management method according to claim 1, wherein: When the type of the determined task is different from the types of one or more tasks registered in a storage device, the determined task is registered in the storage device.

3. The task management method according to claim 1, wherein: When the determined type of the task is the same as the type of any one of the one or more tasks registered in the storage device, the content of the task is updated to the determined content of the task.

4. The task management method according to any one of claims 1 to 3, wherein: When one or more tasks registered in the storage device are changed, notification information indicating the change is transmitted to the information processing terminal used by the user.

5. The task management method according to claim 4, wherein: There are multiple users. The multiple users each belong to one of the multiple groups. The notification information has different contents in each of the plurality of groups.

6. The task management method according to any one of claims 1 to 3, wherein: When any one of the one or more tasks registered in the storage device satisfies a first condition, the task is deleted from the storage device.

7. The task management method according to claim 6, wherein: The first condition includes determining that the task is completed based on the acquired log.

8. The task management method according to claim 6, wherein: The first condition includes that a predetermined time has passed since it was determined that the task was completed.

9. The task management method according to any one of claims 1 to 3, wherein: When a predetermined time comes, all of one or more tasks registered in the storage device are deleted from the storage device.

10. The task management method according to any one of claims 1 to 3, wherein: When a first user is assigned to a person in charge of one of one or more tasks stored in a storage device, changing the person in charge of the task from the first user to a second user is permitted if a second condition is satisfied. The task management method according to claim 10 , wherein: The second condition includes that a predetermined time has passed since the first user was assigned to the task. 12 . A program for causing one or more processors to execute the task management method according to claim 1 .

13. A task management system, wherein: include: an acquiring unit that acquires a log related to a status of the device by communicating with the device or an external system that manages the device; as well as The processing unit determines a task performed by the user who uses the device based on the log acquired by the acquisition unit.

Images