Rules interface for implementing message rules on a mobile computing device

• US 7,599,991 B2
• Filed: 03/10/2004
• Issued: 10/06/2009
• Est. Priority Date: 03/10/2004
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Burgess, Gregory M., Giles, Tadd H., Cover, Steven A., Vargas, Garrett R., Elmer, Robert C.
• Primary Examiner(s): Vaughn, Jr.; William C
• Assistant Examiner(s): Ibrahim; Mohamed
• Application Number:
  US10/798,743
• Publication Number:
  US 20050204003A1
• Time in Patent Office: 2,036 Days
• Field of Search: 709/205, 709/206, 709/207, 719/315
• US Class Current: 709/205
• CPC Class Codes: G06Q 10/00 Administration; Management

Abstract

Described is a system and method for filtering messages received by a message-handling program, that leverage the existing message-handling architecture of computer devices to trigger events and perform other actions instead of (or in addition to) displaying the messages to users. One or more rule clients, e.g., COM objects, register for processing messages. When an appropriate message is received, the message-handling mechanism passes the message to a rule client. Depending on how that rule client responds, the message-handling mechanism determines what to do with the message, e.g., discontinue the message. Messages that are not discontinued are passed to another rule client, if any, or displayed in the user interface, if not. Rule clients may be read only, or may have write access, to modify messages. Messages may be hidden from a user by a rule client, modified before being display to a user, or left intact.

Claims

1. In a mobile computing device, a method for filtering messages received by an inbox program to route selected messages to applications rather than directly to a message inbox, the method comprising:

receiving a message at an inbox program that is configured to present message data to users, the inbox program including a message storing component, the inbox program being installed on the mobile computing device;

upon detecting that the message should be sent to a plurality of rule clients, flagging the message at the inbox program, indicating that the message should be sent to the plurality of rule clients that have registered to receive messages that have been flagged, wherein the plurality of rule clients includes at least one rule client that requests read only access to received messages and at least one rule client that requests write access to received messages, and wherein the plurality of rule clients registers by registering a dynamic-link library in a system registry as a component object model object such that each rule client is loaded when the inbox program receives the message, each rule client being loaded in the inbox program'"'"'s process space;

calling a create message function and passing the flagged message to the message storing component;

upon the message storing component detecting the flag, the message storing component calling a first rule client of the plurality of rule clients and providing a copy of the message to the first rule client rather than storing the message in the message inbox, wherein the first rule client is registered to receive read only access to the message;

the first rule client processing the copy of the message such that the first rule client extracts information from the copy of the message and passes the information to an application program that is distinct from the inbox program;

upon detecting that the first rule client is finished processing the copy of the message, discarding the copy of the message;

after the first rule client has processed the copy of the message, providing the message to a second rule client that is registered to receive write access to the message; and

receiving data from the second rule client, the data indicating whether the inbox program may provide the message to the next rule client in the plurality of rule clients or discard the message.

2. The method of claim 1 wherein receiving a message comprises receiving a message in an SMS format.

3. The method of claim 1 wherein receiving a message comprises receiving a message formatted according to a protocol, the protocol belonging to a set containing IMAP4, POP3, ActiveSync, Instant Messaging and MMS.

4. The method of claim 1 wherein calling the first rule client and providing the copy of the message comprises calling the first rule client on a defined interface.

5. The method of claim 1 further comprising, upon determining that the data received from the second rule client indicates that the message should be discarded, the inbox program deleting the message.

6. The method of claim 1 further comprising, upon determining that the data received from the second rule client indicates that the message may be provided to the next rule client, determining whether there is a next rule client in the plurality of rule clients, and if so providing the message to the next rule client.

7. The method of claim 6 further comprising, upon determining that there is no next rule client in the plurality of rule clients, storing the message for display in a user interface corresponding to the inbox program.

8. The method of claim 6 wherein the data received from the second rule client indicating that the inbox program may provide the message to the next rule client comprises information indicating that the second rule client was not interested in processing the message.

9. The method of claim 6 wherein the data received from the second rule client indicating that the inbox program may provide the message to the next rule client comprises information indicating that the second rule client processed the message.

10. Memory having stored thereon computer-executable instructions which when executed perform the method of claim 1.

11. The method of claim 1 further comprising, the second rule client modifying the message.

12. The method of claim 1 wherein each of the rule clients of the plurality of rule clients is ordered such that rule clients requesting read-only access to messages are called prior to rule clients requesting write access to the messages.

13. In a computing device, a system for filtering messages received by an inbox program to route selected messages to applications rather than directly to a message inbox, the system comprising:

a processor; and

memory storing instructions which when executed by the processor perform a method comprising;

receiving a message at an inbox program that is configured to present message data to users, the inbox program including a message storing component, the message being received over a Short Message Service (SMS) transport;

upon receiving the message, searching a system registry for rule clients that have registered to receive messages that are received over the SMS transport, wherein each rule client registers in the system registry by adding a name of a dynamic-link library (DLL) which defines the rule client to an entry corresponding to the SMS transport in the system registry;

upon detecting that a plurality of rule clients are registered to receive messages that are received over the SMS transport, flagging the message at the inbox program, indicating that the message should be sent to the plurality of rule clients, wherein the plurality of rule clients includes at least one rule client that requests read only access to received messages and at least one rule client that requests write access to received messages,

calling a create message function and passing the flagged message to the message storing component;

upon the message storing component detecting the flag, the message storing component calling a first rule client of the plurality of rule clients and providing a copy of the message to the first rule client rather than storing the message in the message inbox, wherein the first rule client is registered to receive read only access to the message;

the first rule client processing the copy of the message such that the first rule client extracts information from the copy of the message and passes the information to an application program that is distinct from the inbox program;

upon detecting that the first rule client is finished processing the copy of the message, discarding the copy of the message;

after the first rule client has processed the copy of the message, providing the message to a second rule client that is registered to receive write access to the message; and

receiving data from the second rule client, the data indicating whether the inbox program may provide the message to the next rule client in the plurality of rule clients or discard the message.

14. The system of claim 13 further comprising, upon receiving the data from the second rule client indicating that the inbox program may provide the message to the next rule client, the inbox program storing the message in a message inbox.

15. The system of claim 13 wherein the data returned from the second rule client indicates that the second rule client was not interested in handling the message.