Method and apparatus for implementing a real-time event management platform

• US 7,454,459 B1
• Filed: 09/04/2002
• Issued: 11/18/2008
• Est. Priority Date: 09/04/2001
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Jarna Inc.
• Inventors: Kapoor, Sanjay, Toy, Andrew
• Primary Examiner(s): Flynn; Nathan J.
• Assistant Examiner(s): Shin; Kyung H
• Application Number:
  US10/236,003
• Time in Patent Office: 2,267 Days
• Field of Search: 709/202, 709/203, 709/206, 709/207, 709/245, 707/203
• US Class Current: 709/203
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 12/189 in combination with wireless systems selective distribution or broadcast in wireless communication networks H04W4/06
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

A method and apparatus for implementing a real-time enterprise event management system is disclosed. The enterprise event management (EEM) system couples together various “event aware” computing resources that publish and subscribe to “events” that provide information about the state computing resources. All of the events are represented as eXtensible Mark-up Language (XML) documents. Chains of related events are known as “event streams”. In the real-time event management platform, the event streams are available to all other event-aware computing resources operating in the shared event driven environment. The three main components are a real-time messaging system or handing event messages, a rules engine for allowing specific event message handing rules to be created, and a enterprise directory schema for providing a comprehensive directory of all the available resources and the means in which the resources may be accessed.

Claims

1. A mobile device comprising:

a device specific agent of the mobile device configured to process event messages specific to the mobile device, forward said event messages to a plurality of applications located on the mobile device, and receive said event messages from the plurality of applications, said device specific agent including

a transport module configured to receive said specific event messages from a network source or a second mobile device originating said specific event messages,

a message router configured to route said received specific event messages within said mobile device; and

a first application from the plurality of applications configured to receive said specific event messages from said message router, wherein

when the device specific agent receives said specific event messages originating from the network source or the second mobile device, the device specific agent is configured to verify whether the specific event messages originate from a second application, and whether the second application is included in the plurality of applications on the mobile device by consulting a database directory, and in a case the second application is not included, the device specific agent selects said first application and directs said specific event messages to a module that translates said specific event messages to a format corresponding to the first application.

2. The mobile device as claimed in claim 1, wherein said device specific agent forwards a message not addressed to said device specific agent to a native application.

3. The mobile device as claimed in claim 1, wherein said transport module decrypts incoming specific event messages.

4. The mobile device as claimed in claim 1, wherein said transport module decompresses received specific event messages.

5. The mobile device as claimed in claim 1, further comprising:

a native application connector configured to translate said specific event messages received from said message router into commands for an application programming interface for a native application.

6. The mobile device as claimed in claim 1, wherein said transport module communicates across an SMTP connection.

7. The mobile device as claimed in claim 6, wherein said device specific agent intercepts emails sent to said mobile device.

8. The mobile device as claimed in claim 1, wherein said specific event messages comprise XML formatted messages.

9. The mobile device as claimed in claim 1, further comprising:

a client management module configured to receive client management event messages and change encryption keys.

10. The mobile device as claimed in claim 1, further comprising:

a client management module configured to receive client management event messages and destroy data on said mobile device.

18. The mobile device according to claim 1, wherein the message router further includes:

a rules engine configured to define rules for routing the event specific messages and generate responses to the event specific messages,

wherein the rules are defined based on information of the database directory.

11. An application system that is configured to be in communication with a mobile device, the system comprising:

a real-time messaging system configured to forward to the mobile device event messages specific to the mobile device and originating from a network source or a second mobile device, the mobile device including a device specific agent of the mobile device and configured to process said event messages, forward said event messages to a plurality of applications located on the mobile device, and receive said event messages originating from the plurality of applications;

a rules engine configured to process said specific event messages forwarded by said real-time messaging system;

a universal database directory configured to store information about a plurality of computing resources available to said application platform; and

at least one web services application configured to receive said specific event messages from said real-time messaging system, wherein,

when the application system receives a specific event message originating from a first application located on the network source or the second mobile device, and the application system consults the universal database on a presence of the first application among the plurality of applications on the mobile device, and the universal database directory includes information that the first application is not included in the plurality of applications on the mobile device, the application system translates the specific event message to a format corresponding to a second application and directs the specific event message to the second application.

12. The system as claimed in claim 11, further comprising:

a presence management module configured to determine the presence of client devices.

13. The system as claimed in claim 11, further comprising:

an SMTP transport module configured to deliver said specific event messages in SMTP email messages.

14. The system as claimed in claim 11, further comprising:

an HTTP transport module configured to deliver said specific event messages across an HTTP connection.

15. The system as claimed in claim 11, further comprising:

a legacy application translator configured to translate events generated by a legacy application into said specific event messages for said application platform.

16. The system as claimed in claim 11, further comprising:

a legacy application connector configured to poll a legacy application and generating events for said application platform upon detection of changes.

17. The system as claimed in claim 11, wherein said specific event messages comprise XML formatted messages.

19. The application system according to claim 11, wherein the rules engine is further configured to define rules for routing the event specific messages and generate responses to the event specific messages,

wherein the rules are defined based on information of the universal database directory.