Event heap: a coordination infrastructure for dynamic heterogeneous application interactions in ubiquitous computing environments

• US 7,702,729 B2
• Filed: 04/08/2004
• Issued: 04/20/2010
• Est. Priority Date: 04/08/2003
• Status: Active Grant

• Current Assignee: Tidebreak, Inc.
• Original Assignee: Armando Fox, Bradley E. Johanson, Patrick M. Hanrahan, Terry A. Winograd
• Inventors: Winograd, Terry A., Johanson, Bradley E., Fox, Armando, Hanrahan, Patrick M.
• Primary Examiner(s): Phillips; Hassan
• Assistant Examiner(s): Tiv; Backhean
• Application Number:
  US10/821,756
• Publication Number:
  US 20040243663A1
• Time in Patent Office: 2,203 Days
• Field of Search: 709205-207
• US Class Current: 709/205
• CPC Class Codes: G06F 2209/544 Remote
• CPC Class Codes: G06F 2209/546 Xcast
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

An efficient and adaptive middleware infrastructure called the Event Heap system dynamically coordinates application interactions and communications in a ubiquitous computing environment, e.g., an interactive workspace, having heterogeneous software applications running on various machines and devices across different platforms. Applications exchange events via the Event Heap. Each event is characterized by a set of unordered, named fields. Events are routed by matching certain attributes in the fields. The source and target versions of each field are automatically set when an event is posted or used as a template. The Event Heap system implements a unique combination of features, both intrinsic to tuplespaces and specific to the Event Heap, including content based addressing, support for routing patterns, standard routing fields, limited data persistence, query persistence/registration, transparent communication, self-description, flexible typing, logical/physical centralization, portable client API, at most once per source first-in-first-out ordering, and modular restartability.

Claims

1. A computer system for exchanging events in an interactive workspace, comprising:

(a) a plurality of heterogeneous software applications, called clients, wherein said clients are run by a plurality of heterogeneous machines of said interactive workspace;

(b) a server for coordinating exchanges of a plurality of events between said clients, wherein each of said events comprises a set of unordered named fields and wherein each of said unordered named fields of each of said events comprises a post value and a template value;

(c) a network for connecting said server and said plurality of clients;

(d) a post function for allowing each of said clients to assign one or more of said post values to said unordered named fields of one of said events and to post said events, wherein said posted event is posted on said server; and

(e) a retrieve function for allowing each of said clients to retrieve said posted event from said server, wherein said retrieve function allows each of said clients to assign one or more of said template values to said unordered named fields of one of said events, referred to as a template event, wherein said template value of one of said unordered named fields of said template event specifies a matching requirement on said post values of the same of said unordered named fields of said posted events, wherein said posted event is retrieved based on matching said one or more post values of said unordered named fields of said posted event with said one or more template values of said unordered named fields of said template event, and wherein said matching ignores a field order of some or all of said unordered named fields of said posted event and said template event;

wherein said set of unordered named fields of each of said events comprises multiple standard source fields, wherein said set of unordered named fields further comprises a target field corresponding to each of said multiple standard source fields, wherein said standard source fields are associated with said clients posting said events, wherein said target fields are associated with said clients retrieving said events, and wherein said standard source fields and said corresponding target field are used for routing said events between said clients.

2. The system as set forth in claim 1, wherein said standard source fields include an application instance, an application name, a device name, a person, and a group, wherein said standard source fields are set to wildcards by default for said template events for retrieving said posted event, and wherein said target fields are set to wildcards by default for said posted events.

3. The system as set forth in claim 1, wherein said set of unordered named fields of each of said events includes multiple standard fields, wherein said standard fields comprise an EventType, a SequenceID, a TimeToLive, and a TimeStamp.

4. The system as set forth in claim 1, wherein said post and said template values of said unordered named fields can be marked as a formal value or a virtual value, wherein each of said unordered named fields marked as said formal value matches any value in said matching of said posted event with said template event, and wherein each of said unordered named fields marked as said virtual value is ignored in said matching of said posted event with said template event.

5. The system as set forth in claim 1, wherein said retrieve function retrieves one of said posted events at most once, and wherein said retrieve function retrieves the same of said posted events based on a first-in-first-out per source ordering.

6. The system as set forth in claim 1, further comprising a restart function for automatically reconnecting one or more of said clients to said server.

7. The system as set forth in claim 1, wherein said set of unordered named fields of said posted event comprises an expiration field for determining an expiration time of said posted event.

8. The system as set forth in claim 1, further comprising a query function for allowing each of said clients to register a query template event onto said server and to assign one or more values to said unordered named fields of said query template event, wherein said posted event is returned to said client that registered said query template event based on matching said one or more values of said unordered named fields of said posted event and said one or more values of said unordered named fields of said query template event, and wherein said posted event is returned to said client that registered said query template event only if said posted event is posted after said query template event is registered.

9. The system as set forth in claim 8, wherein said query function allows each of said clients to unregister said query template event, wherein said query template event is removed from said server when said query template event is unregistered.

10. The system as set forth in claim 1, wherein one of said clients posting one of said posted events does not directly communicate with said client retrieving the same of said posted events.

11. The system as set forth in claim 1, wherein said interactive workspace of said plurality of heterogeneous machines is in a bounded physical environment.

12. A method for exchanging events in an interactive workspace, comprising:

(a) having a plurality of heterogeneous software applications, called clients, wherein said clients are run by a plurality of heterogeneous machines of said interactive workspace;

(b) having a server for coordinating exchanges of a plurality of events between said clients, wherein each of said events comprises a set of unordered named fields, and wherein each of said unordered named fields of each of said events comprises a post value and a template value;

(c) connecting said server and said plurality of clients through a network;

(d) providing a post function for allowing each of said clients to assign one or more of said post values to said unordered named fields of one of said events and to post said events, wherein said posted event is posted on said server; and

(e) providing a retrieve function for allowing each of said clients to retrieve said posted event from said server, wherein said retrieve function allows each of said clients to assign one or more of said template values to said unordered named fields of one of said events, referred to as a template event, wherein said template value of one of said unordered named fields of said template event specifies a matching requirement on said post values of the same of said unordered named fields of said posted events, wherein said posted event is retrieved based on matching said one or more post values of said unordered named fields of said posted event with said one or more template values of said unordered named fields of said template event, and wherein said matching ignores a field order of some or all of said unordered named fields of said posted event and said template event;

wherein said set of unordered named fields of each of said events comprises multiple standard source fields, wherein said set of unordered named fields further comprises a target field corresponding to each of said multiple standard source fields, wherein said standard source fields are associated with said clients posting said events, wherein said target fields are associated with said clients retrieving said events, and wherein said standard source fields and said corresponding target field are used for routing said events between said clients.

13. The method as set forth in claim 12, wherein said set of unordered named fields of said posted event comprises an expiration field for determining an expiration time of said posted event.

14. The method as set forth in claim 12, further comprising providing a query function for allowing each of said clients to register a query template event onto said server and to assign one or more values to said unordered named fields of said query template event, wherein said posted event is returned to said client that registered said query template event based on matching said one or more values of said unordered named fields of said posted event and said one or more values of said unordered named fields of said query template event, and wherein said posted event is returned to said client that registered said query template event only if said posted event is posted after said query template event is registered.

15. The method as set forth in claim 14, wherein said query function allows each of said clients to unregister said query template event, wherein said query template event is removed from said server when said query template event is unregistered.

16. The method as set forth in claim 12, wherein said standard source fields include an application instance, an application name, a device name, a person, and a group, wherein said standard source fields are set to wildcards by default for said template events for retrieving said posted events, and wherein said target fields are set to wildcards by default for said posted events.

17. The method as set forth in claim 12, wherein said set of unordered named fields of each of said events comprises multiple standard fields, wherein said standard fields comprise an EventType, a SequenceID, a TimeToLive, and a TimeStamp.

18. The method as set forth in claim 12, wherein said post and said template values of said unordered named fields can be marked as a formal value or a virtual value, wherein each of said unordered named fields marked as said formal value matches any value in said matching of said posted event with said template event, and wherein each of said unordered named fields marked as said virtual value is ignored in said matching of said posted event with said template event.

19. The method as set forth in claim 12, wherein said retrieve function retrieves one of said posted events at most once, and wherein said retrieve function retrieves the same of said posted events based on a first-in-first-out per source ordering.

20. The method as set forth in claim 12, further comprising automatically reconnecting one of said clients to said server if the same of said client disconnects from said network.

21. The method as set forth in claim 12, wherein one of said clients posting one of said posted events does not directly communicate with said client retrieving the same of said posted events.

22. The method as set forth in claim 12, wherein said interactive workspace of said plurality of heterogeneous machines is in a bounded physical environment.