Exploiting entity relationships in proximity-based scheduling applications

• US 20060288347A1
• Filed: 06/20/2005
• Published: 12/21/2006
• Est. Priority Date: 06/20/2005
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Jemiolo, Daniel Everett, Subramanian, Balan
• Application Number:
  US11/156,783
• Publication Number:
  US 20060288347A1
• Time in Patent Office: Days
• US Class Current: 718/102
• CPC Class Codes: G06Q 10/109 Time management, e.g. calendars, reminders, meetings or time accounting

Abstract

Entity relationships are created, discovered, and applied in proximity-based scheduling applications. When a signal is received from an entity in proximity to a user of a data processing system, the signal is compared against previously recorded signals. If a signal match is found, the entity generating the signal is identified using the entity definition associated with the previously recorded signal. Entities associated with the entity generating the signal are also identified. A reminder is provided to the user to perform tasks associated with the entity and tasks associated with the others entities while the user is in proximity to the entity. If a signal match is not found, and if the user has performed a task with an unassociated entity, a relationship may be created between the entity associated with the performed task and the unassociated entity, either automatically or upon prompting the user.

Claims

1. A method for using entity relationships to schedule execution of tasks in a data processing system, the method comprising

receiving a signal from an entity in proximity to a user of the data processing system;

comparing the signal against a plurality of previously recorded signals;

identifying the entity that generated the signal from an entity definition associated with a previously recorded signal in response to the signal matching a previously recorded signal in the plurality of previously recorded signals;

identifying other entities associated with the entity; and

providing a reminder to perform tasks associated with the entity and tasks associated with the other entities while the user is in proximity to the entity.

2. The method of claim 1, further comprising:

determining whether a task has been performed with an unassociated entity in response to the signal not matching a previously recorded signal in the plurality of previously recorded signals; and

suggesting to the user that an entity relationship between the entity associated with the performed task and the unassociated entity be created in response to determining that a task has been performed with an unassociated entity.

3. The method of claim 1, further comprising:

determining whether a task has been performed with an unassociated entity in response to the signal not matching a previously recorded signal in the plurality of previously recorded signals; and

automatically creating a relationship between the entity associated with the performed task and the unassociated entity in response to determining that a task has been performed with an unassociated entity.

4. The method of claim 1, wherein the entity is identified by querying an entity database, wherein the entity database comprises a private entity collection and a global database of public entities.

5. The method of claim 4, wherein entity relationships in the global database of public entities are synchronized with entity relationships created by different users based on a threshold.

6. The method of claim 5, wherein the threshold comprises a number of users who have created a same entity relationship and a number of tasks for which the users discovered a same entity-task relationship.

7. The method of claim 1, wherein other entities associated with the entity are identified by querying an entity-relationship database, and wherein the entity-relationship database comprises a set of equality and inclusion relationships between known entities.

8. The method of claim 1, wherein tasks associated with the entity are identified by querying an entity-task database, wherein the task-entity database comprises a set of tasks and associated entities.

9. The method of claim 1, wherein the signal is received using sense-and-respond technology.

10. The method of claim 9, wherein the sense-and-respond technology is radio frequency identification.

11. The method of claim 1, wherein the signal is received in response to polling an area surrounding the data processing system.

12. The method of claim 1, wherein the signal is received in response to monitoring an area surrounding the data processing system.

13. The method of claim 1, wherein the entity is one of a person, place, or an object.

14. A data processing system for using entity relationships to schedule execution of tasks, the data processing system comprising:

a plurality of entities, wherein the entities comprise transmission units for transmitting signals; and

a portable computing device, wherein the portable computing device comprises a receiving unit for receiving signals from the transmission units when the portable computing device is in proximity to the entities, and wherein the portable computing device comprises computer usable program code for identifying an entity transmitting a signal through a comparison of the signal to previously recorded signals, identifying other entities associated with the entity, and providing a reminder to perform tasks associated with the entity and tasks associated with the other entities while a user of the portable computing device is in proximity to the entity.

15. A computer program product comprising:

a computer usable medium having computer usable program code for using entity relationships to schedule execution of tasks, said computer program product comprising;

computer usable program code for receiving a signal from an entity in proximity to a user of the data processing system;

computer usable program code for comparing the signal against a plurality of previously recorded signals;

computer usable program code for identifying the entity that generated the incoming signal from an entity definition associated with the previously recorded signal if the signal matches a previously recorded signal in the plurality of previously recorded signals;

computer usable program code for identifying other entities associated with the entity; and

computer usable program code for providing a reminder to perform tasks associated with the entity and tasks associated with the other entities while the user is in proximity to the entity.

16. The computer program product of claim 15, further comprising:

computer usable program code for determining whether a task has been performed with an unassociated entity in response to the signal not matching a previously recorded signal in the plurality of previously recorded signals; and

computer usable program code for suggesting to the user that an entity relationship between the entity associated with the performed task and the unassociated entity be created in response to determining that a task has been performed with an unassociated entity.

17. The computer program product of claim 15, further comprising:

computer usable program code for determining whether a task has been performed with an unassociated entity in response to the signal not matching a previously recorded signal in the plurality of previously recorded signals; and

computer usable program code for automatically creating a relationship between the entity associated with the performed task and the unassociated entity in response to determining that a task has been performed with an unassociated entity.

18. The computer program product of claim 15, wherein the entity is identified by querying an entity database, wherein the entity database comprises a private entity collection and a global database of public entities.

19. The computer program product of claim 18, wherein entity relationships in the global database of public entities are synchronized with entity relationships created by different users based on a threshold, wherein the threshold comprises a number of users who have created a same entity relationship and a number of tasks for which the users discovered a same entity-task relationship.

20. The computer program product of claim 18, wherein other entities associated with the entity are identified by querying an entity-relationship database, wherein the entity-relationship database comprises a set of equality and inclusion relationships between known entities, wherein tasks associated with the entity are identified by querying an entity-task database, and wherein the task-entity database comprises a set of tasks and associated entities.