JP6696599B2 - Object management device and object management system - Google Patents

Description

  The present invention relates to a product management device and a product management system.

  2. Description of the Related Art Conventionally, a user has created a ToDo list or the like for tasks such as his or her work and schedule and manages the tasks with a smartphone or the like. In recent years, a technique is known in which a transmitter is attached to an information storage medium such as a magnetic tape or paper, the transmitter periodically transmits an identifier to a management device, and the management device centrally manages the identifier.

JP, 2003-36429, A

  However, in the above technique, when one user manages a task, processing and management become complicated. For example, the method using the to-do list is troublesome because tasks are manually registered and deleted. Although the method using a transmitter can manage the position of the information storage medium or the like by the identifier, the task is executed, completed, or deleted manually. As described above, it is difficult to say that managing tasks by these methods imposes a heavy burden on the user, takes time, and takes time.

  In one aspect, it is an object to provide an object management device and an object management system capable of easily managing tasks.

  In the first proposal, the management device for an object is that the user is physically associated with an object used to execute a task and / or the physical association between the object and the object is released. It has a detection part which detects. The object management device, when the detection unit detects that the object is associated with the object, or the association with the object is released, a device physically associated with the object. The task management apparatus that manages the association with the task of the user includes a transmission unit that transmits the identifier of the own apparatus and requests generation of the association or deletion of the association. The object management device has a detection unit that detects that the object is physically associated and / or that the object is not physically associated. The object management device has a transmission unit that transmits the identifier of the device itself when the detection unit detects that the object is associated with the object or that the association with the object is released.

  According to one embodiment, tasks can be easily managed.

FIG. 1 is a diagram illustrating an example of the overall configuration of the system according to the first embodiment. FIG. 2 is a functional block diagram of a functional configuration example of the system according to the first embodiment. FIG. 3 is a diagram showing a format example of a request transmitted from the clip. FIG. 4 is a diagram showing an example of information stored in the task DB. FIG. 5 is a diagram illustrating a transition example of screen display in task registration. FIG. 6 is a diagram for explaining task deletion from task notification. FIG. 7 is a sequence diagram illustrating the flow of processing according to the first embodiment. FIG. 8 is a diagram illustrating an example of the overall configuration of the system according to the second embodiment. FIG. 9 is a functional block diagram of a functional configuration example of the system according to the second embodiment. FIG. 10 is a diagram showing an example of information stored in the task allocation DB. FIG. 11 is a diagram illustrating task assignment according to the second embodiment. FIG. 12 is a diagram illustrating an example of changing task assignment according to the second embodiment. FIG. 13 is a sequence diagram of a process flow according to the second embodiment. FIG. 14 is a diagram illustrating an example of simultaneous notification to clips. FIG. 15 is a diagram showing an example of an alert screen when a clip is not nearby. FIG. 16 is a diagram illustrating a hardware configuration example.

  Hereinafter, embodiments of the object management apparatus and the object management system disclosed in the present application will be described in detail with reference to the drawings. The present invention is not limited to the embodiments. The respective examples can be appropriately combined within a range without contradiction.

[overall structure]
FIG. 1 is a diagram illustrating an example of the overall configuration of the system according to the first embodiment. As shown in FIG. 1, the management system for this object includes a clip 10 and a smartphone 30. The clip 10 and the smartphone 30 are connected using short-range wireless communication such as Bluetooth (registered trademark, hereinafter sometimes referred to as BT). In addition to BT, near field communication such as NFC (Near Field Communication) can be adopted.

  The clip 10 holds a unique identifier and detects a device that is physically associated with an object or that the physical association between an object is released, a management apparatus, and an object management apparatus. Is an example. For example, the clip 10 has the grip portion 14, detects that the document 1 is physically associated with the document 1 when sandwiched, and physically detaches the document 1 when the document 1 is removed. Detect release. An energization sensor 14a is installed at the tip of the grip portion 14 of the clip 10, and it is possible to detect whether or not an object is pinched by the state of the energization sensor 14a. Specifically, the energization sensor 14a energizes when an object is not sandwiched and interrupts energization when an object is sandwiched.

  Note that the document 1 will be described here as an example of an object to be sandwiched, but the invention is not limited to this. For example, a storage medium such as a memory card or a USB (Universal Serial Bus) memory, an envelope, a writing instrument, or the like. Can be similarly applied. Further, in the present embodiment, the clip 10 having the grip portion 14 will be described as an example, but the present invention is not limited to this, and for example, an envelope or a file into which an object is put may be used.

  The smartphone 30 is an example of a task management device having a display, a touch panel, or the like, or a first computer. Here, the smartphone 30 will be described as an example, but the present invention is not limited to this, and can be applied to mobile terminals such as mobile phones and PDAs (Personal Digital Assistants) and various computers.

  In such a state, the clip 10 determines the state of the grip portion 14, and when detecting that it is in the grip state, transmits the identifier of the clip 10 to the smartphone 30 by BT. When the smartphone 30 receives the identifier of the clip 10 from the clip 10, the smartphone 30 stores the received identifier of the clip 10. After that, the smartphone 30 displays the information regarding the identifier of the clip 10 stored in the storage unit.

  For example, as shown in FIG. 1, the clip 10 detects that the document 1 is gripped when the document 1 is sandwiched, and transmits the identifier held by the clip 10 to the smartphone 30. Upon receiving the identifier from the clip 10, the smartphone 30 registers the task associated with the received identifier as the task of the user of the smartphone 30.

  Further, the clip 10 detects that the document 1 is not gripped when the document 1 is detached, and transmits the identifier held by the clip 10 to the smartphone 30. Upon receiving the identifier from the clip 10, the smartphone 30 specifies that the identifier has already been received. Then, the smartphone 30 deletes the task associated with the received identifier from the tasks of the user of the smartphone 30.

  In this way, the clip 10 sends a task entry request to the smartphone 30 when the document 1 is sandwiched and sends a task completion request to the smartphone 30 when the document is removed. The task related to can be easily managed by the smartphone 30.

[Function configuration]
FIG. 2 is a functional block diagram of a functional configuration example of the system according to the first embodiment. Here, the functional configuration of the clip 10 and the functional configuration of the smartphone 30 will be described.

(Functional configuration of clip 10)
As shown in FIG. 2, the clip 10 includes a wireless unit 11, a light emitting unit 12, a vibrating unit 13, a gripping unit 14, an energization sensor 14a, a storage unit 15, and a control unit 20.

  The wireless unit 11 is a processing unit that performs short-range wireless communication with the smartphone 30 using BT, and is, for example, a wireless interface. For example, the wireless unit 11 transmits a task entry request including the identifier to the smartphone 30, and transmits a task completion request including the identifier to the smartphone 30. The wireless unit 11 also periodically transmits a signal to detect a device as a communication destination. For communication between the wireless unit 11 of the clip 10 and the wireless unit 31 of the smartphone 30, any communication method may be used as long as information can be transmitted and received. For example, a communication method such as broadcasting may be used.

  The light emitting unit 12 is a processing unit that emits light according to an instruction from the control unit 20, and is, for example, an LED (Light Emitting Diode). Specifically, the light emitting unit 12 turns on when it receives a lighting instruction from the control unit 20, and turns off when it receives an extinguishing instruction from the control unit 20. It should be noted that the light emission pattern can be arbitrarily set to turn on or blink.

  The vibrating unit 13 is a processing unit that vibrates according to an instruction from the control unit 20, and is, for example, a vibration or the like. Specifically, the vibration unit 13 vibrates when it receives a vibration instruction from the control unit 20, and stops the vibration when it receives a stop instruction from the control unit 20. The vibration pattern can be set arbitrarily.

  The grip unit 14 is a processing unit that has an energization sensor 14a and that sandwiches or removes the document 1. Specifically, the two gripping parts 14 constitute one gripping part 14 and exert a gripping function. Further, in each of the grips 14, an energization sensor 14a is installed at a portion sandwiching a document. The energization sensor 14a is a sensor that detects that a current is flowing. When each energization sensor 14a installed in each gripping part 14 comes into contact, a current flows.

  For example, the grip portion 14 is in a non-grip state when energization is detected by the energization sensor 14a, and is in a grip state when energization is not detected by the energization sensor 14a. In other words, the gripping portion 14 being in the gripping state means that the object such as the document 1 and the clip 10 are physically associated with each other, and the gripping portion 14 being in the non-grasping state means that the document 1 and the like. That is, the physical association between the object and the clip 10 is released.

  The storage unit 15 is a storage device that stores a program executed by the control unit 20 and various data, and is, for example, a hard disk or a memory. The storage unit 15 stores the unique identifier (ID001) assigned to the clip 10.

  The control unit 20 is a processing unit that controls the overall processing of the clip 10, and is, for example, a processor. The control unit 20 has a determination unit 21 and a notification unit 22. The determination unit 21 and the notification unit 22 are examples of electronic circuits included in the processor, examples of processes executed by the processor, and the like.

  The determination unit 21 is a processing unit that determines the gripped state of the clip 10. Specifically, the determination unit 21 determines whether the clip 10 is in the grasping state or the non-grasping state based on the state of the energization sensor 14a included in the grasping unit 14, and outputs the determination result to the notifying unit 22. Therefore, the grip portion 14 or the grip portion 14 and the determination portion 21 cooperate with each other so that the clip 10 grips an object, that is, the clip 10 is physically associated with the object and / or the physical relationship between the object. It operates as a detection unit that detects that the physical association has been released.

  For example, the determination unit 21 determines that the gripping unit 14 is in the gripping state when the state of the energization sensor 14a changes from being energized to being not energized due to the document 1 being sandwiched. In general, when sandwiching an object with the clip 10, the user sandwiches the object while maintaining the opened state of the clip 10 for a predetermined time. Therefore, the determination unit 21 can also determine that the grip portion 14 is in the gripping state when the non-energized state of the energization sensor 14a continues for a predetermined time. When the state of the energization sensor 14a changes from non-energized to energized when the document 1 is removed, the determination unit 21 determines that the gripping unit 14 is in the non-grip state.

  The notification unit 22 is a processing unit that transmits various requests to the smartphone 30 according to the change in the grip state determined by the determination unit 21. Therefore, it operates as a transmitter or a wireless transmitter from the clip 10 to the smartphone 30. Specifically, when the state of the gripping unit 14 changes from the non-grasping state to the gripping state, the notification unit 22 transmits a task entry request including the identifier stored in the storage unit 15 to the smartphone 30. In addition, the notification unit 22 transmits a task release request including the identifier stored in the storage unit 15 to the smartphone 30 when the state of the gripping unit 14 changes from the gripping state to the non-gripping state.

  Here, various requests transmitted by the notification unit 22 will be described. FIG. 3 is a diagram showing a format example of a request (signal) transmitted from the clip. As shown in FIG. 3, each request has “identifier, time, grip state”. The "identifier" is an identifier stored in the storage unit 15, and is "ID001" in this embodiment. The "time" is the time when the gripping state is determined. The “holding state” is information that identifies the determination result determined by the determining unit 21, and “Hold” is set in the holding state, and “Release” is set in the non-holding state.

  For example, when the determination unit 21 determines that the gripping unit 14 is in the gripping state at 6:00, the notification unit 22 transmits an entry request including “ID001, 6:00, Hold” to the smartphone 30. To do. After that, when the determination unit 21 determines that the gripping unit 14 is in the non-grasping state at 12:00, the notification unit 22 sends the smartphone 30 a release request including “ID001, 12:00, Release”. Send.

  The format shown here is an example, and the present invention is not limited to this. For example, when the clip 10 stores the task name in advance, the notification unit 22 can also transmit the task name including the “task name” in addition to the information illustrated in FIG. 3. Further, the notification unit 22 can also send only the identifier without including the time information and the information on the gripping state. The notification unit 22 can also include the task start time and the like.

(Functional configuration of smartphone 30)
As shown in FIG. 2, the smartphone 30 includes a wireless unit 31, a display unit 32, an input unit 33, a storage unit 34, and a control unit 40.

  The wireless unit 31 is a processing unit that executes short-range wireless communication with the clip 10 using BT, and is, for example, a wireless interface. For example, the wireless unit 31 receives from the clip 10 a task entry request or a deletion request including an identifier. The wireless unit 31 also transmits a vibration instruction, a lighting instruction, a light-off instruction, and the like to the clip 10.

  The display unit 32 is a processing unit that displays various types of information, and is, for example, a touch panel. For example, the display unit 32 displays information about registered tasks. The input unit 33 is a processing unit that receives input of various kinds of information from the user, and is, for example, a software keyboard. For example, the input unit 33 receives an input such as registration or change of the task name and outputs it to the control unit 40.

  The storage unit 34 is a storage device that stores a program executed by the control unit 40 and various data, and is, for example, a hard disk or a memory. The storage unit 34 stores the task DB 35.

  The task DB 35 is a database that stores information about registered tasks. FIG. 4 is a diagram showing an example of information stored in the task DB 35. As shown in FIG. 4, the task DB 35 stores “reception time, task execution time, identifier, task name” in association with each other.

  The “reception time” stored here is the time when the entry request is received. The “task execution time” is the start time of the task and can be specified by the clip 10 or set by the user on the smartphone 30 side. The “identifier” is an identifier of the clip 10 registered as a task. The “task name” is the name of the task displayed in the task list, which can be specified by the clip 10 or set by the user on the smartphone 30 side.

  In the example of FIG. 4, the entry request transmitted from the clip 10 with the identifier “ID001” is received at “6:01”, the task name of this task is “business trip settlement”, and the task start time is “9: 00 ”. The task DB 35 stores information used for BT communication that can be acquired from the information received by the receiving unit 41 in association with each task.

  The control unit 40 is a processing unit that controls the overall processing of the smartphone 30, and is, for example, a processor. The control unit 40 includes a reception unit 41, a registration unit 42, a notification unit 43, and a deletion unit 44. The reception unit 41, the registration unit 42, the notification unit 43, and the deletion unit 44 are examples of electronic circuits included in the processor, examples of processes executed by the processor, and the like.

  The reception unit 41 is a processing unit that receives a task entry request or a task cancellation request from the clip 10 received by the wireless unit 31. Specifically, the receiving unit 41 receives various requests described in the format shown in FIG. Then, when “Hold” is registered in the gripping state of the received request, the receiving unit 41 determines that it is an entry request, and outputs the received information to the registration unit 42. Further, when “Release” is registered in the gripping state of the received request, the receiving unit 41 determines the release request and outputs the received information to the deleting unit 44.

  As another example, when the identifier included in the received request is not registered in the task DB 35, the reception unit 41 determines that the request is an entry and outputs the received information to the registration unit 42. Further, when the identifier included in the received request is registered in the task DB 35, the receiving unit 41 determines that the request is a cancellation request and outputs the received information to the deleting unit 44.

  The registration unit 42 is a processing unit that registers a task in the task DB 35. Specifically, when the receiving unit 41 receives the entry request, the registration unit 42 stores various information included in the entry request in the task DB 35 as a task. For example, when the entry request “identifier = ID001, gripping state = Hold” is received, the registration unit 42 stores the reception time and the identifier “ID001” in the task DB 35 in association with each other. After that, the registration unit 42 accepts the setting of the “task execution time” and the “task name” via the display unit 32 and the input unit 33, and stores the accepted information in the task DB 35.

  As another example, when the entry request “identifier = ID001, task execution time = 9: 00, task name = business trip settlement, grip state = Hold” is received, the registration unit 42 receives the reception time, the identifier, and the task name. And the task execution time are associated with each other and stored in the task DB 35. In this way, the registration unit 42 can register the received information as a task and allow the user to register the information that is insufficient as the task.

  If the task name or the like is not input, the registration unit 42 can temporarily register arbitrary information such as “task with ID001” or “task XX” until the task name is input. The registration unit 42 can also register in the task DB 35 in the order in which the entry requests are received, and can also sort in the order of task execution time. The registration unit 42 also extracts information used for BT communication from the information received by the reception unit 41, and stores the information in association with each task.

  The notification unit 43 is a processing unit that notifies the user of the task to be executed. Specifically, the notification unit 43 refers to the task DB 35, and when a task that has reached the task execution time is detected, the notification unit 43 transmits a vibration instruction to the clip 10 having the identifier associated with the task. By doing so, even if the user forgets the task start time or the location of the document 1 sandwiched between the clips, it is possible to suppress forgetting to execute the task.

  Further, when the deleting unit 44 deletes a task from the task DB 35, the notification unit 43 refers to the task DB 35 and determines whether or not there is a task to be executed next. Then, when there is a task to be executed next, the notification unit 43 transmits the lighting instruction to the clip 10 having the identifier associated with the task. By doing so, the notification unit 43 can notify the user of the existence of an unprocessed task.

  The deletion unit 44 is a processing unit that deletes a processed task from the task list. Specifically, the deletion unit 44 deletes the corresponding task from the task DB 35 when the cancellation request is received by the reception unit 41. Then, the deletion unit 44 notifies the notification unit 43 that the task has been deleted.

  For example, when the cancellation request “identifier = ID001, gripping state = Release” is received, or when the identifier “ID001” is received from the reception unit 41, the deletion unit 44 performs the task corresponding to the identifier “ID001”. Delete from DB35.

[Explanation of task registration]
FIG. 5 is a diagram illustrating a transition example of screen display in task registration. As illustrated in FIG. 5, when the clip 10 detects that the document 1 is sandwiched, the clip 10 transmits the identifier “ID001” to the smartphone 30 (S1). Upon receiving the identifier, the smartphone 30 causes the display unit 32 to display the received identifier (S2).

  Subsequently, the smartphone 30 registers the task corresponding to the received identifier in the task DB 35 and displays the registered task list on the display unit 32 (S3). Here, an example in which the identifier “ID001” is displayed as the task name because the task name is not set is illustrated.

  After that, when the smartphone 30 receives the change of the task name of the task corresponding to the identifier "ID001" from the user, the smartphone 30 updates the task DB 35 with the received task name "business trip settlement" (S4). Subsequently, the smartphone 30 displays a list of tasks registered in the task DB 35 (S5).

[Description of task cancellation]
FIG. 6 is a diagram for explaining task deletion from task notification. In FIG. 6, an example will be described in which each of two clips, clip 10 and clip 10a, registers a task. The clip 10a also has the same functional configuration as the clip 10.

  As shown in FIG. 6, the smartphone 30 stores a task list. Specifically, the smartphone 30 displays "1.90, bank documents, ..." as "item number, task execution time, task name, ..." and "2, 10:00, business trip settlement, ... "is memorized.

  In such a state, when the time becomes 9:00, the smartphone 30 determines that it is the start time of the task “bank document” of item No. 1 (S10). Then, the smartphone 30 transmits the vibration instruction to the clip 10 associated with the identifier of the task "bank document", and the clip 10 activates the vibe according to the vibration instruction (S11).

  After that, when the clip 10 detects that the document 1 is removed, the clip 10 transmits the identifier to the smartphone 30 (S12). The smartphone 30 that has received the identifier deletes the task “1.9: 00, bank documents, ...” that is stored in association with the received identifier, and adds the task “Business trip settlement” of item No. 2 to the item number. Promote to 1 (S13).

  Subsequently, the smartphone 30 specifies the task to be executed next from the task DB 35 because there is an unprocessed task (S14). Then, the smartphone 30 transmits a lighting instruction to the clip 10a corresponding to the identifier of the task to be executed next (S15). Upon receiving this instruction, the clip 10a lights a light emitting unit such as an LED.

[Process flow]
FIG. 7 is a sequence diagram illustrating the flow of processing according to the first embodiment. In FIG. 7, as in FIG. 6, an example in which each of two clips, clip 10 and clip 10a, registers a task will be described. Further, since the clip 10 and the clip 10a have the same functional configuration, the same symbols are used for the processing units. The clip 10 holds an identifier (ID001), and the clip 10a holds an identifier (ID002).

  As shown in FIG. 7, when the determination unit 21 of the clip 10 detects the gripping state of the gripping unit 14 (S101), the notification unit 22 of the clip 10 sends an entry request including the identifier (ID001) to the smartphone 30. (S102 and S103).

  Then, when the receiving unit 41 of the smartphone 30 receives the entry request including the identifier from the clip 10 (S104), the registration unit 42 registers the task corresponding to the received identifier in the task DB 35 (S105). The task registered here is a task (ID001).

  The registration unit 42 also performs pairing with the clip 10 for which the task registration is performed, as necessary (S106 to S108). The execution timing of pairing is not limited to that shown in the figure, and it can be executed at any time between task registration and task start time.

  Similarly, when the determination unit 21 of the clip 10a detects the holding state of the holding unit 14 (S109), the notification unit 22 of the clip 10a transmits an entry request including the identifier (ID002) to the smartphone 30 (S110 and S111). ).

  Then, when the receiving unit 41 of the smartphone 30 receives the entry request including the identifier from the clip 10a (S112), the registration unit 42 registers the task corresponding to the received identifier in the task DB 35 (S113). Note that the task registered here is a task (ID002).

  Further, the registration unit 42 executes pairing with the clip 10 for which the task registration is performed, if necessary (S114 to S116). The execution timing of pairing is not limited to that shown in the figure, and it can be executed at any time between task registration and task start time.

  After that, when the notification unit 43 of the smartphone 30 detects the start time of the task (ID001) (S117), the notification unit 43 executes notification of a vibration instruction or the like to the clip 10 associated with the task (ID001) (S118 and S119). ).

  When the vibration unit 13 of the clip 10 receives the vibration instruction from the smartphone 30, the vibration unit 13 activates the vibe (S120). After that, when the task is executed and the document or the like is detached from the clip 10, the determination unit 21 of the clip 10 detects the non-grasping state (S121). Then, the notification unit 22 of the clip 10 transmits a deletion request including the identifier (ID001) to the smartphone 30 (S122 and S123).

  Then, the deletion unit 44 of the smartphone 30 deletes the corresponding task (ID001) from the task DB 35 by receiving the release request from the clip 10 (S124). After that, the deletion unit 44 cancels the pairing with the clip 10 (S125).

  Subsequently, the notification unit 43 of the smartphone 30 specifies that the task (ID002) is registered as the next task (S126). Then, the notification unit 43 executes advance notification such as a lighting instruction to the clip 10a associated with the task (ID002) (S127 and S128). The light emitting unit 12 of the clip 10a that has received this notification turns on the LED (S129).

[effect]
In this way, the user can easily register a task in the smartphone 30 by inserting an object such as a document in each clip, and by removing the object from the clip, the user can easily delete the task from the smartphone 30. You can In this way, the user can easily manage the physical object that is the target of the task and the information of the task in association with each other. In addition, the user can manage tasks by organizing the physical objects that are the targets of tasks without performing difficult operations, so task management can be performed as an extension of daily activities, and tasks can be easily performed. Can be managed.

  Further, since the user can manage the task with the smartphone 30, the task can be easily edited and managed. When the task is completed, the smartphone 30 can turn on the LED of the clip corresponding to the next task, so that the user can be prevented from forgetting the task.

  By the way, although the example in which the task is managed by one smartphone 30 has been described in the first embodiment, the invention is not limited to this, and the task can be managed by using a plurality of smartphones. Therefore, in a second embodiment, an example of task management using a plurality of smartphones will be described.

[overall structure]
FIG. 8 is a diagram illustrating an example of the overall configuration of the system according to the second embodiment. As shown in FIG. 8, this system includes a clip 10, a smartphone 30, a smartphone 50, and a management server 70. The clip 10 and each smartphone are connected using wireless communication such as BT. Each smartphone and the management server 70 are connected via a network. As such a network, any type of communication network such as the Internet (LAN), a LAN (Local Area Network), a VPN (Virtual Private Network), and the like can be adopted regardless of wired or wireless.

  Similar to the first embodiment, the clip 10 retains a unique identifier and is an example of a device that detects that a physical association with an object or a physical association between an object is released. Is. The smartphone 30 and the smartphone 50 are an example of a task management device having a display, a touch panel, or the like, or a first computer, as in the first embodiment. The management server 70 is a server device that assigns a task to each smartphone, and is an example of a second computer.

  In such a state, for example, when the clip 10 detects that the clip 10 is physically associated with an object such as a document, the clip 10 transmits the identifier of the device itself to the smartphone 30 located at a position where short-distance communication is possible. When the smartphone 30 receives the identifier from the clip 10 located at the position where short-distance communication is possible, the smartphone 30 transmits the received identifier of the clip 10 and the identifier of the own device to the management server 70. The management server 70 receives the identifier of the clip 10 and the identifier of the smartphone 30. Then, when the received identifier of the clip 10 is not stored, the management server 70 stores the identifier of the clip 10 and the identifier of the smartphone 30 in association with each other. On the other hand, when the received identifier of the clip 10 has been stored, the management server 70 updates the identifier of the other smartphone stored in association with the identifier of the clip 10 with the received identifier of the smartphone 30.

  That is, when an object is sandwiched between the clips 10, the smartphone 50 located at a position where BT communication with the clip 10 is possible transmits the identifier of the clip 10 to the management server 70. Then, when the identifier of the clip 10 is not registered as a task, the management server 70 assigns it as a new task of the smartphone 50. On the other hand, when the identifier of the clip 10 is already registered as a task, the management server 70 changes the assignment destination of the task to the smartphone 50.

  As described above, since tasks can be managed by a plurality of smartphones, for example, one task can be shared within a company, and task management for a plurality of people can be easily executed.

[Function configuration]
FIG. 9 is a functional block diagram of a functional configuration example of the system according to the second embodiment. Since the clip 10 has the same function as that of the first embodiment, detailed description thereof will be omitted here. For example, when the grip state changes, the clip 10 searches for a smartphone capable of short-range communication, and transmits the state (Hold or Release) of the grip portion 14 and the identifier to the searched smartphone. Further, when a new smartphone capable of short-distance communication is searched for, the clip 10 transmits the state of the gripping unit 14 and the identifier to the searched smartphone when a new smartphone capable of short-distance communication is searched for.

  Further, since the smartphone 30 and the smartphone 50 have the same configuration, the smartphone 50 will be described here as an example. In the following description, the processing unit of the smartphone 30 will also be described using the same reference numerals as those of the smartphone 50.

(Functional configuration of smartphone 50)
As shown in FIG. 9, the smartphone 50 includes a communication unit 51, a display unit 52, an input unit 53, a storage unit 54, and a control unit 60.

  The communication unit 51 is a processing unit that performs short-range wireless communication with the clip 10 using BT and transmits / receives data to / from the management server 70 via various networks. For example, the communication unit 51 receives from the clip 10 a task entry request or a deletion request including the identifier of the clip 10. The communication unit 51 also transmits a vibration instruction, a lighting instruction, a light-off instruction, and the like to the clip 10.

  The communication unit 51 also transmits the identifier of each clip 10 and the identifier of the smartphone 50 to the management server 70. The communication unit 51 receives a task registration instruction and a task deletion instruction from the management server 70.

  The display unit 52 is a processing unit that displays various kinds of information, and is, for example, a touch panel. For example, the display unit 52 displays information about registered tasks. The input unit 53 is a processing unit that receives input of various kinds of information from the user, and is, for example, a software keyboard. For example, the input unit 53 receives an input such as registration or change of a task name and outputs it to the control unit 60.

  The storage unit 54 is a storage device that stores programs executed by the control unit 60 and various data, and is, for example, a hard disk or a memory. This storage unit 54 stores a task DB 55. The task DB 55 is a database that stores information about registered tasks. The information stored in the task DB 55 is the same as that in the first embodiment, and detailed description thereof will be omitted.

  The storage unit 54 also stores “SMP002” as an identifier assigned to the smartphone 50. The storage unit 54 of the smartphone 30 stores “SMP001” as an identifier assigned to the smartphone 30.

  The control unit 60 is a processing unit that controls the overall processing of the smartphone 50, and is, for example, a processor. The control unit 60 includes a reception unit 61, a transmission unit 62, a registration unit 63, a notification unit 64, and a deletion unit 65. The reception unit 61, the transmission unit 62, the registration unit 63, the notification unit 64, and the deletion unit 65 are an example of an electronic circuit included in the processor and an example of a process executed by the processor.

  The receiving unit 61 is a processing unit that receives various types of information from the clip 10 and the management server 70. Specifically, the reception unit 61 receives a task entry request, a task cancellation request, and the like, which are transmitted by the clip 10 in accordance with a change in the grip state. Then, the receiving unit 61 outputs the received information to the transmitting unit 62. The information to be received is the same as that in the first embodiment, and detailed description thereof will be omitted.

  Further, the receiving unit 61 receives the combination of the state of the gripping unit 14 and the identifier, which the clip 10 has transmitted with the detection of a new BT connection destination. That is, the receiving unit 61 receives information transmitted from the clip 10 due to a change in the storage location of the clip 10. For example, the receiving unit 61 receives the state “Hold” of the grip unit 14 and the identifier (ID001), and outputs it to the transmitting unit 62.

  Further, the receiving unit 61 receives a task registration instruction and a task deletion instruction from the management server 70. For example, the receiving unit 61 receives, as the task registration instruction, the task registration instruction and the identifier of the corresponding clip 10 from the management server 70. Then, the reception unit 61 outputs the received task registration instruction to the registration unit 63. Further, the receiving unit 61 receives, as the task deletion instruction, the task deletion instruction and the identifier of the corresponding clip 10 from the management server 70. Then, the receiving unit 61 outputs the received task deletion instruction to the deleting unit 65. Further, the receiving unit 61 may measure the received radio field intensity when receiving the entry request from the clip 10.

  The transmission unit 62 is a processing unit that transmits the information received from the clip 10 to the management server 70. Specifically, the transmission unit 62 transmits the entry request and the deletion request received from the clip 10 to the management server 70, and requests the management server 70 for task allocation and task deletion.

  For example, when the transmission unit 62 receives the entry request “identifier (ID001), time (6:00), gripping state (Hold)” shown in FIG. 3 from the clip 10, the transmission unit 62 sends its own identifier (SMP002) to this entry request. Is added and transmitted to the management server 70. Similarly, when the transmission unit 62 receives the deletion request “identifier (ID001), time (9:00), gripping state (Release)” from the clip 10, the transmission unit 62 adds its own identifier (SMP002) to the deletion request. And sends it to the management server 70.

  Further, when the transmitting unit 62 receives the combination of the state “Hold” of the gripping unit 14 and the identifier (ID001) from the receiving unit 61, it adds its own identifier (SMP002) to this combination and transmits it to the management server 70. To do.

  The registration unit 63 is a processing unit that registers a task in the task DB 55 according to an instruction from the management server 70. Specifically, when the receiving unit 61 receives the task registration instruction and the identifier of the corresponding clip 10, the registration unit 63 registers the task corresponding to the received identifier of the clip 10 in the task DB 55. Since the information to be registered is the same as that in the first embodiment, detailed description will be omitted.

  The notification unit 64 is a processing unit that notifies the user of the task to be executed. Since the notification unit 64 executes the same processing as the notification unit 43 described in the first embodiment, detailed description will be omitted.

  The deletion unit 65 is a processing unit that deletes a processed task from the task list. Specifically, when the receiving unit 61 receives the task deletion instruction and the identifier of the corresponding clip 10, the deleting unit 65 deletes the task corresponding to the received identifier of the clip 10 from the task DB 55.

(Functional configuration of the management server 70)
As shown in FIG. 9, the management server 70 has a communication unit 71, a storage unit 72, and a control unit 80.

  The communication unit 71 is a processing unit that transmits and receives data to and from each smartphone via various networks. For example, the communication unit 71 receives from the smartphone 50 various information such as a task entry request and a deletion request including the identifier of the clip 10 and the identifier of the smartphone 50. The communication unit 51 also transmits a task registration instruction, a task deletion instruction, or the like to the smartphone 50 or the like.

  The storage unit 72 is a storage device that stores programs executed by the control unit 80 and various data, and is, for example, a hard disk or a memory. This storage unit 72 stores a task allocation DB 73.

  The task assignment DB 73 is a database that stores assignment information of tasks specified by the clip 10. Specifically, the task assignment DB 73 is a database that manages which smartphone a task is assigned to.

  FIG. 10 is a diagram showing an example of information stored in the task allocation DB 73. As illustrated in FIG. 10, the task allocation DB 73 stores “reception time, identifier, allocation destination, radio wave intensity” in association with each other. The “reception time” is the time when the task entry request is received. The “identifier” is an identifier of a clip registered as a task. The “assignment destination” is the identifier of the smartphone to which the task is assigned. The “radio field strength” is the received field strength when the smartphone receives the task entry request from the clip. As will be described later, in the process executed by the smartphone and the management server 70, when the information on the radio wave intensity is not used, the information on the radio wave intensity need not be stored in the task allocation DB 37. Further, in the processing, when the information on the radio field intensity is not used, the radio field intensity may not be measured by the receiving unit 61 of the smartphone 50.

  The example of FIG. 10 is an example of the entry request transmitted from the clip 10 having the identifier “ID001”. The management server 70 receives this entry request at time “6:01” via the smartphone 50, and the radio field intensity measured when the smartphone 50 receives the entry request from the clip 10 is “XXX”. Show. It also indicates that a task has been assigned to the smartphone 50 having the identifier “SMP002” in response to this entry request. Each information stored here is stored by the determination unit 82 described later.

  The control unit 80 is a processing unit that controls the overall processing of the management server 70, and is, for example, a processor. The control unit 80 includes a receiving unit 81, a determining unit 82, and a transmitting unit 83. The receiving unit 81, the determining unit 82, and the transmitting unit 83 are an example of an electronic circuit included in the processor and an example of a process executed by the processor.

  The reception unit 81 is a processing unit that receives various information such as a task entry request and a deletion request from each smartphone. For example, the receiving unit 81 receives the entry request “holding state (Hold), clip identifier, smartphone identifier” transmitted by the clip 10. Further, the receiving unit 81 receives the deletion request “grasping state (Release), clip identifier, smartphone identifier” transmitted by the clip 10. Further, the receiving unit 81 receives the information in which the smartphone identifier is added to the combination of the “grasping state and the clip identifier” transmitted by the clip 10 when the new BT connection destination is detected.

  That is, the receiving unit 81 receives the gripped state of the clip 10 and the identifier of the clip 10 in accordance with the state change of the clip 10 and the change of the BT connection destination. Further, the receiving unit 81 receives the received field strength when the smartphone receives the entry request from the clip, together with these pieces of information. Then, the receiving unit 81 outputs the received information to the determining unit 82.

  The determination unit 82 is a processing unit that determines a task allocation destination and allocates the task. Specifically, when the grip state of the received clip 10 is (Hold) and the identifier of the clip 10 is not registered, the determination unit 82 executes task assignment. Further, when the received identifier of the clip 10 has been registered and the received grip state is “Release”, the determination unit 82 executes task de-allocation. Further, when the received identifier of the clip 10 has been registered and the received gripping state is “Hold”, the determination unit 82 executes task assignment determination based on radio field intensity.

  For example, when the grip state of the clip 10 received from the smartphone 50 is (Hold) and the identifier (ID001) of the clip 10 is not registered in the task assignment DB 73, the determination unit 82 assigns the task to the smartphone 50. In this case, the determination unit 82 associates the reception time, the identifier (ID001) of the clip 10, the identifier (SMP002) of the allocation-destination smartphone 50, and the measured radio field intensity (XXX), and associates them with the task allocation DB 73. To store. Then, the determination unit 82 requests the transmission unit 83 to transmit the task registration instruction to the corresponding smartphone 50.

  Further, when the grip state of the clip 10 received from the smartphone 50 is (Release) and the identifier (ID001) of the clip 10 is registered in the task allocation DB 73, the determination unit 82 releases the task of the smartphone 50. In this case, the determination unit 82 refers to the task allocation DB 73 and identifies the allocation destination (SMP002) associated with the identifier (ID001) of the clip 10. Then, the determination unit 82 requests the transmission unit 83 to transmit the task deletion instruction to the smartphone 50 associated with the corresponding allocation destination (SMP002).

  Further, when the gripping state of the clip 10 received from the smartphone 50 is (Hold) and the identifier (ID001) of the clip 10 is registered in the task allocation DB 73, the determination unit 82 determines whether the task allocation destination needs to be changed. To judge. For example, consider a case where, when the clip 10 broadcasts an entry request, a plurality of smartphones happen to exist near the clip 10 and each smartphone receives the entry request from the clip 10. In this case, both the smartphone A and the smartphone B that have received the entry request transmit the identifier of their own device and the identifier of the clip 10 to the management server 70. Then, the management server 70 sends both the entry request A including the identifier of the clip 10 and the identifier of the smartphone A and the entry request B including the identifier of the clip 10 and the identifier of the smartphone B during the predetermined time interval. You will receive it. If the smartphone to which the clip 10 should be associated is a smartphone that is located closer to the clip 10, it determines the radio field strength when communication is performed between the clip 10 and each smartphone. Available for For example, it is assumed that the management server 70 first receives the entry request from the smartphone A and then receives the entry request from the smartphone B. The determination unit 82 compares the radio field intensity information included in the entry request for the identifier (ID001) of the current clip 10 with the radio field intensity registered in the task allocation DB 73. Then, the determination unit 82 assigns the task to the one having the higher radio field intensity.

  For example, in the determination unit 82, the registered smartphone A has a stronger radio field intensity of the wireless communication performed with the clip 10 (that is, the smartphone A is closer to the clip 10 than the smartphone B is). In this case, it is determined that the task assignment of the smartphone B received later does not need to be changed, and the processes such as DB update and notification are not executed. On the other hand, when the newly received smartphone B has a stronger radio field intensity (that is, the smartphone B is closer to the clip 10 than the clip A is), the determination unit 82 changes the task assignment. Specifically, the determination unit 82 updates the task allocation DB 73 with the information regarding the identifier and the radio field intensity of the smartphone 50 that has already been registered with the identifier and the radio field intensity of the newly received smartphone 30. Then, the determination unit 82 requests the transmission unit 83 to transmit the task registration instruction to the smartphone 30 to which the task is newly assigned and the task deletion instruction to the smartphone 50 that has completed the task assignment.

  Note that, here, when the management server 70 receives an entry request including the same clip identifier from a plurality of smartphones within a predetermined time interval, the determination as to which smartphone to associate with is used by the radio field intensity. Although the example of making the determination has been described, the present invention is not limited to this. For example, they can be simply assigned in the order of reception. That is, the determination unit 82 can also change the task assignment by giving priority to the smartphone 30 that has newly transmitted the identifier or the like over the registered smartphone 50, regardless of the radio field intensity.

  Also, when the smartphone user transmits the identifier of the clip 10 to the management server 70, it is possible to set which smartphone the task is to be assigned to. When the smartphone identifier is set as the “task assignment destination” in the information received from the smartphone, the determination unit 82 of the management server 70 assigns the task to the set smartphone.

  The transmission unit 83 is a processing unit that transmits a task allocation instruction and a task deletion instruction to a corresponding smartphone. Specifically, the transmission unit 83 transmits various instructions according to the request received from the determination unit 82. For example, the transmission unit 83 transmits a task registration instruction including the “identifier (ID001) of the clip 10 and the gripping state (Hold)” to the smartphone 50 to which the task is assigned.

  Further, the transmission unit 83 transmits a task deletion instruction including the “identifier (ID001) of the clip 10 and the grip state (Release)” to the smartphone 50 associated with the completed task.

  In addition, the transmission unit 83 transmits a task deletion instruction including the “identifier (ID001) of the clip 10” to the smartphone 50 that has been released from the task assignment due to the task assignment change. Further, the transmission unit 83 transmits a task registration instruction including the “identifier (ID001) of the clip 10” to the smartphone 30 to which the task has been newly assigned, along with the task assignment change.

[Explanation of task assignment]
Next, task assignment according to the second embodiment will be described. FIG. 11 is a diagram illustrating task assignment according to the second embodiment. As shown in FIG. 11, the clip 10 transmits the identifier of the clip 10 to the smartphone 50 via wireless communication. For example, when the clip 10 detects that the document 1 is sandwiched, the clip 10 searches for a terminal capable of short-distance communication, and transmits the identifier “ID001” of the clip 10 to the searched smartphone 50 (S20).

  Subsequently, when the smartphone 50 receives the identifier of the clip 10, the smartphone 50 transmits the identifier “ID001” of the clip 10 and its own identifier “SMP002” to the management server 70 (S21).

  Then, when the management server 70 receives the identifier “ID001” of the clip 10 and the identifier “SMP002” of the smartphone 50, since the “ID001” has not been registered, the assignment destination of the task is determined to be the smartphone 50 (S22). .. After that, the management server 70 notifies the smartphone 50 of the task (S23). As a result, the smartphone 50 receives the task name to be displayed in association with the task by the user operation, for example, and registers the task “1, bank document” associated with the clip 10.

[Explanation of task assignment change]
Next, an example of changing the task assignment according to the second embodiment will be described. FIG. 12 is a diagram illustrating an example of changing task assignment according to the second embodiment.

  As shown in FIG. 12, when the clip 10 detects that the document 1 is sandwiched, it searches for a terminal capable of short-distance communication, and transmits the identifier “ID001” of the clip 10 to the searched smartphone 50. (S30). After that, here, it is assumed that the same process as in FIG. 11 is executed and the task “1, bank documents” associated with the clip 10 is already registered in the smartphone 50.

  In such a state, it is assumed that the storage location of the clip 10 is changed, and the smartphone 10 is detected as the terminal capable of short-distance communication with the clip 10 (S31). For example, when the document 1 sandwiched by the clips 10 is passed from the user who carries the smartphone 50 to the user who carries the smartphone 30, such a state occurs. Then, the clip 10 transmits its own identifier “ID001” to the newly detected smartphone 30 (S32).

  Subsequently, when the smartphone 30 receives the identifier of the clip 10, the smartphone 30 transmits the identifier “ID001” of the clip 10 and its own identifier “SMP001” to the management server 70 (S33).

  Then, when the management server 70 receives the identifier “ID001” of the clip 10 and the identifier “SMP001” of the smartphone 30, since the “ID001” is already registered in association with the “SMP002” of the smartphone 50, the task allocation is performed. Preliminary determination is executed (S34). Here, the management server 70 receives the identifier of the clip 10 that the smartphone 30 receives from the smartphone 30 based on the radio field intensity when the smartphone 50 receives the identifier of the clip 10 that is received from the smartphone 50 as described above. Since the radio field strength at the time of doing is stronger, the assignment destination of the task is changed to the smartphone 30.

  As a result, the management server 70 notifies the smartphone 30 of task assignment (S35), and notifies the smartphone 50 of task deletion (S36). In this way, the task corresponding to the clip 10 moves from the smartphone 50 to the smartphone 30 as the clip 10 or the smartphone 50 moves.

[Process flow]
FIG. 13 is a sequence diagram illustrating a flow of processing according to the second embodiment. As illustrated in FIG. 13, when the determination unit 21 of the clip 10 detects the gripping state of the gripping unit 14 (S201), the notification unit 22 transmits an entry request including the identifier (ID001) to the smartphone 50 (S202 and S202). S203).

  Then, the receiving unit 61 of the smartphone 50 receives the entry request including the identifier from the clip 10 (S204). Then, the transmission unit 62 of the smartphone 50 transmits the received identifier "ID001" and its own identifier "SMP002" to the management server 70 (S205 and S206).

  Subsequently, the determination unit 82 of the management server 70 determines the smartphone 50 as the allocation destination because the identifier “ID001” of the clip 10 received from the smartphone 50 is not registered in the task allocation DB 73 (S207). At this time, the determination unit 82 stores, in the task allocation DB 73, the radio field intensity received from the smartphone 50 when the smartphone 50 receives the identifier of the clip 10. Then, the transmission unit 83 of the management server 70 notifies the smartphone 50 of the task (S208 and S209).

  Upon receiving this notification, the registration unit 63 of the smartphone 50 registers the task for the identifier “ID001” of the clip 10 in the task DB 55 (S210). The task registered here is a task (ID001).

  In addition, the registration unit 63 of the smartphone 50 executes pairing with the clip 10 for which the task registration is performed, as necessary (S211 to S213). The execution timing of pairing is not limited to that shown in the figure, and it can be executed at any time between task registration and task start time.

  After that, when the notification unit 22 of the clip 10 detects the smartphone 30 that is a new connection destination due to the movement or the like (S214), the notification unit 22 transmits the identifier “ID001” of itself to the smartphone 30 (S215 and S216).

  Then, the receiving unit 61 of the smartphone 30 receives the identifier “ID001” from the clip 10 (S217). Then, the transmission unit 62 of the smartphone 30 transmits the identifier “ID001” of the clip 10 and its own identifier “SMP001” to the management server 70 (S218 and S219).

  After that, since the identifier “ID001” of the clip 10 received from the smartphone 30 is already registered as a task, the determination unit 82 of the management server 70 executes the determination of the allocation destination (S220). Then, the determination unit 82 determines the smartphone 30 as the allocation destination based on the radio field intensity and the like (S221).

  As a result, the transmission unit 82 of the management server 70 transmits a task cancellation notification corresponding to the clip 10 to the smartphone 50 (S222 and S223). Then, the deletion unit 65 of the smartphone 50 deletes the corresponding task from the task DB 55 (S224) and cancels the pairing with the clip 10 (S225 and S226).

  On the other hand, the transmission unit 82 of the management server 70 transmits the registration notification of the task corresponding to the clip 10 to the smartphone 30 (S227 and S228). Then, the registration unit 63 of the smartphone 30 registers the relevant task in the task DB 55 (S229), and performs pairing with the clip 10 as needed (S230 to S232). The execution timing of pairing is not limited to that shown in the figure, and it can be executed at any time between task registration and task start time. Also, the order of the cancellation notice and the registration notice can be arbitrarily changed.

[effect]
In this way, the task can be easily registered in the smartphone using the clip 10, and when the clip 10 or the smartphone in which the task is registered moves, the task can be moved to another smartphone. Therefore, tasks can be shared by a plurality of people, and group tasks and the like can be managed. For example, you can automatically send the task to the boss's smartphone when you generate the payment task yourself, register it on your smartphone, and then hand over the documents related to the task to your boss. Is improved, and user convenience is improved.

  Also, because the assignment destination of the task can be changed according to the radio field strength, for urgent tasks etc., the person who is nearby, not the person who registered the task, can execute it instead, so forget to execute the task etc. Human error can be suppressed.

  Although the embodiments of the present invention have been described so far, the present invention may be implemented in various different forms other than the embodiments described above.

[Broadcast]
For example, when there are multiple tasks, the order of execution and the storage location of clips may be forgotten. In such a case, the smartphone 30 can transmit a vibration instruction or a lighting instruction to each clip corresponding to each registered task.

  FIG. 14 is a diagram illustrating an example of simultaneous notification to clips. As shown in FIG. 14, the notification unit 43 of the smartphone 30 superimposes and displays the clip button 30a on the task list screen. Then, when the clip button 30a is selected by the user 2, the notification unit 43 executes the notification process for each clip corresponding to each task.

  For example, the notification unit 43 transmits the vibration instruction to the clip 10 corresponding to the first task, and then transmits the vibration instruction to the clip 10a corresponding to the second task. Subsequently, the notification unit 43 transmits the vibration instruction to the clip 10b corresponding to the third task, and then transmits the vibration instruction to the clip 10c corresponding to the fourth task.

  By doing so, the user can confirm the position and number of tasks. Although the vibration instruction has been described as an example here, it may be a lighting instruction or a combination of both. Also, the order of transmitting the instructions can be arbitrarily changed. Further, in the above-described embodiment, vibration and lighting are exemplified as the notification example, but the notification is not limited to this. For example, when the clip has a speaker, sound can be output in response to an instruction from the smartphone.

[Alert screen]
For example, the notification unit 43 of the smartphone 30 transmits a vibration instruction or the like to the clip corresponding to the task that has reached the start time, but the clip may not be in a communicable position. In this case, the notification unit 43 of the smartphone 30 can display an alert screen on the display unit 32 to alert the user.

  FIG. 15 is a diagram showing an example of an alert screen when a clip is not nearby. As shown in FIG. 15, the notification unit 43 of the smartphone 30 displays an alert screen in which “the task is deadline of XX” is described when the clip corresponding to the task that has reached the start time is not nearby. Further, the notification unit 43 allows the user to select whether to re-notify after 15 minutes, re-notify after 1 hour, or re-notify when a clip is detected, that is, when wireless communication with the clip becomes possible. Re-notification is executed according to the selected content. The screen message and the like can be arbitrarily changed.

[Pre-register to clip]
For example, in the above embodiment, an example in which the smartphone or the management server associates the task with the clip has been described, but the invention is not limited to this. For example, information about a task can be registered in advance in the internal memory of each clip. That is, the task name can be registered in each clip. For example, a clip used for the task "overtime calculation" performed at the end of the month, a clip used for the task "morning meeting material" performed every Monday, and the like are generated in advance. In this way, by determining the clips to be used for the periodic task in advance, it is possible to suppress human error such as inserting wrong material in the clips even when the number of clips becomes large. .

  Also, a plurality of clips can be associated with one material. An example of using a plurality of clips is a task that is executed weekly, but the day of the week that is executed changes every week. In this case, the relevant material is sandwiched between the weekly clip and the clip for the execution target day. By doing so, it is possible to associate two tasks for each week with the relevant material.

[Determination of gripping state]
In the above embodiment, an example in which the energization sensor 14a is used to determine the gripped state has been described, but the present invention is not limited to this. For example, an angle sensor that detects the angle at which the two grips 14 are open or a pressure sensor that detects the pressure of the two grips 14 can be used. Furthermore, a resistance value or the like can also be adopted, and any sensor can be adopted as long as it is a sensor that can detect an operation such as opening of the grip 14 or closing of the grip 14.

  For example, if it is detected by the angle sensor that the angle has expanded after the task registration, it may be determined that a new document has been additionally inserted, and the task may be determined to be changed. Similarly, after the task registration, when the angle sensor detects that the angle has become narrow, it can be determined that the document has been extracted and that the task has been changed. When such a task change occurs, the smartphone displays the changed task information on the screen. The smartphone can also execute the same process as the above-described task registration to re-register the task.

[Information sent from clip]
In the above-described embodiment, the example in which the identifier and the grip state are transmitted from the clip 10 has been described, but the present invention is not limited to this, and various information can be transmitted. For example, the clip 10 can also transmit predetermined time length information that specifies notification timing and the like to the smartphone. The clip 10 can also transmit time length information designating a task start time or the like to the smartphone.

[Notification by clip]
In the above embodiment, the clip 10 activates the vibe and lights the LED when the vibration instruction or the like is received from the smartphone, but the invention is not limited to this. For example, the clip 10 can autonomously perform vibe activation or LED lighting by storing the task start time or the like in an internal memory or the like.

[Examples other than clips]
For example, in addition to the clip, by adding a small electronic circuit to an envelope or a file in which an object is put, the same processing as in the above embodiment can be executed.

[system]
In addition, each component of each unit illustrated does not necessarily have to be physically configured as illustrated. That is, the specific form of distribution / integration of each part is not limited to the one shown in the figure, and all or part of the part may be functionally or physically distributed / integrated in arbitrary units according to various loads and usage conditions. Can be configured. Further, various processing functions performed by each device may be executed entirely or in part on a CPU (Central Processing Unit). Further, it goes without saying that various processing functions may be executed in whole or in an arbitrary part on a program analyzed and executed by the CPU or on hardware by a wired logic.

  Further, of the processes described in the present embodiment, all or part of the processes described as being automatically performed may be manually performed. Alternatively, all or part of the processing described as being manually performed can be automatically performed by a known method. In addition, the processing procedures, control procedures, specific names, and information including various data and parameters shown in the above-mentioned documents and drawings can be arbitrarily changed unless otherwise specified.

[hardware]
Each of the above devices can be implemented by, for example, a computer 100 having the following hardware configuration. FIG. 16 is a diagram illustrating a hardware configuration example. As shown in FIG. 16, the computer 100 includes a communication interface 100a, an HDD (Hard Disk Drive) 100b, a memory 100c, and a processor 100d.

  Examples of the processor 100d include a CPU, a DSP (Digital Signal Processor), an FPGA (Field Programmable Gate Array), and a PLD (Programmable Logic Device). Further, examples of the memory 100c include a RAM (Random Access Memory) such as an SDRAM (Synchronous Dynamic Random Access Memory), a ROM (Read Only Memory), and a flash memory.

  The clip 10 also operates as an information processing device that executes the notification method by reading and executing the program. That is, the clip 10 executes a program that executes the same functions as the determination unit 21 and the notification unit 22. As a result, the clip 10 can execute a process that performs the same function as the determination unit 21 and the notification unit 22. The programs referred to in the other embodiments are not limited to being executed by the clip 10. For example, the present invention can be similarly applied to the case where another computer or server executes the program, or when these computers cooperate to execute the program.

  This program can be distributed via a network such as the Internet. In addition, this program is recorded on a computer-readable recording medium such as a hard disk, a flexible disk (FD), a CD-ROM, an MO (Magneto-Optical disk), a DVD (Digital Versatile Disc), and the like. It can be executed by being read. Although the clip 10 is described as an example here, each smartphone and the management server 70 can be processed in the same manner.

10 clip 11 wireless unit 12 light emitting unit 13 vibrating unit 14 gripping unit 14a energization sensor 15 storage unit 20 control unit 21 determination unit 22 notification unit 30 smartphone 31 wireless unit 32 display unit 33 input unit 34 storage unit 40 control unit 41 reception unit 42 Registration unit 43 Notification unit 44 Deletion unit 70 Management server 71 Communication unit 72 Storage unit 73 Task allocation DB
80 control unit 81 reception unit 82 determination unit 83 transmission unit

Claims (10)

The user is physically associated with an object used to execute a task that indicates a unit to be registered in the schedule list to be executed, and / or the physical association with the object is released. A detection unit for detecting
Wherein the detection unit, when detecting that you associated with the object, the task management device for managing a schedule list of the user, and transmits an entry registration request for the task, including the identifier of the own device, the When the generation of the association between an object and the task is requested, or when it is detected that the association with the object is released, the task management device deletes the entry of the task including the identifier of the own device. An object management apparatus , comprising: a transmission unit that transmits a request and requests deletion of association between the object and the task . The object according to claim 1, wherein the detection unit detects that the object management device has been physically associated with the object when detecting that the object is sandwiched. Management device. When the detection unit detects that the management device for the object has changed from the state in which the object is sandwiched to the state in which the object is not sandwiched, it detects that the association with the object has been released. The object management apparatus according to claim 1, wherein: In an object management system including an object management device and a first computer that manages a schedule list scheduled to be executed by a user,
The management device for the object is
A detection unit that detects that the user is physically associated with an object used to execute a task indicating a unit to be registered in the schedule list ;
Wherein when the detection unit detects, before Symbol first computer, possess a transmitting section for transmitting an entry registration request for the task, including the identifier of the own device,
The first computer is
Transmitted from the transmitting unit of the management device of the product, a receiving unit that receives the entry registration request including an identifier of the management device of the product,
An identifier management apparatus said received object, to display information about the identifier of the management device of the product stored in the storage unit and a storage unit that stores, displays a registration screen including a registration execution time for at least the task Display section ,
An object management system, comprising: a registration unit that generates a task in which the execution time received on the registration screen is associated with an identifier of the object management apparatus and registers the task in the schedule list . The first computer, the identifier of the management device of the product received by the, if the identifier of unrecorded, an identifier of a management device of the product stored in the storage unit, if the identifier of the recorded the management system of things according to claim 4, characterized in that to remove the identifier of the management device of the product from the storage unit. The first computer includes a transmission unit that transmits an operation instruction to the object management device specified by the identifier of the object management device stored in the storage unit when a predetermined condition is satisfied. Have,
The object management device, a receiving unit for receiving the operation instruction,
The object management system according to claim 4, further comprising a notification unit that executes a predetermined operation when the operation instruction is received. A receiving unit of the first computer receives an identifier from each of the plurality of object management devices;
The storage unit of the first computer stores the received identifiers in the order in which they are received, and satisfying the predetermined condition is based on information received from the first object management apparatus. The fact that the object management device has detected that the association with the object that has been associated with the object has been released, and the transmitter is stored next to the first object management device in the stored order. The object management system according to claim 6, wherein the operation instruction is transmitted to a second object management device that is operating. When a notification indicating that the execution time has come is received from the task management device, the vibration device included in the object management device is executed, and the task management device sends a notification that specifies a target to be executed next. The object management apparatus according to claim 1, further comprising a control unit that lights up a light emitting device included in the object management apparatus when received. The first computer is
  A monitoring unit that monitors the execution time of each task registered as the schedule list,
  When a task at the execution time has occurred, the storage unit is referenced to identify an identifier associated with the task, and the management apparatus for the object corresponding to the identified identifier starts execution of the task. It has a notification part to notify,
  The management device for the object is
  And a control unit which, when receiving a notification of the start of execution of the task from the first computer, executes a vibration of a vibrating device of the management device of the object or a light emission of a light emitting device of the management device of the object. The article management system according to claim 4, wherein: The display unit of the first computer transmits a vibration instruction or a light emission instruction to the object management apparatus associated with the task that has reached the start time, but cannot communicate because the object management apparatus cannot be detected. The object management system according to claim 4, wherein information indicating that the task is due is started in this case.

Images