Triggering actions with mobile messages

• US 9,942,732 B2
• Filed: 07/09/2016
• Issued: 04/10/2018
• Est. Priority Date: 07/09/2016
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Rubinstein, Mark
• Primary Examiner(s): Gelin, Jean
• Application Number:
  US15/206,221
• Publication Number:
  US 20180014167A1
• Time in Patent Office: 640 Days
• Field of Search: 4554121, 4554122, 455413, 4554141, 4554142, 455417, 455445, 455466
• CPC Class Codes: H04M 1/724 User interfaces specially adapted for cordless or mobile telephones
• CPC Class Codes: H04M 1/72436 for text messaging, e.g. short messaging services [SMS] or e-mails
• CPC Class Codes: H04M 1/72445 for supporting Internet browser applications
• CPC Class Codes: H04M 11/007 with remote control systems remote control in general G08C
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 68/005 Transmission of information for alerting of incoming communication

Abstract

A mobile device may create a message rule to establish a causal relationship between a messaging activity and a device activity or vice versa. A message rule user interface displayed on the mobile device may receive from a user a message parameter, describing at least one of a message format and a message content of a hypothetical received mobile message. The message rule user interface also may receive a response action directive describing a device action to be performed by the mobile device in response to receiving an incoming mobile message corresponding to the message parameter. The mobile device may store a message target rule associating the message parameter with the response action directive. The mobile device may receive the incoming mobile message corresponding to the message parameter and execute the device action according to the response action directive.

Claims

1. A mobile message device, comprising:

an output device configured to present a message rule user interface to the user to establish a message rule;

an input device configured to receive from a user via the message rule user interface a message parameter describing at least one of a message format and a message content of a hypothetical mobile message received in a mobile messaging module and a response action directive describing a device action selected from a plurality of device actions to be performed by the mobile message device in response to receiving an incoming mobile message matching the message parameter;

memory configured to store a message target rule associating the message parameter with the response action directive;

a communication interface configured to receive the incoming mobile message matching the message parameter; and

a processing core having at least one processor configured to execute the device action in response to the incoming mobile message according to the response action directive.

2. The mobile message device of claim 1, wherein the processing core is further configured to implement a smart assistant module to present a message rule user interface.

3. The mobile message device of claim 1, wherein the input device is further configured to receive from the user at least one of an active period parameter describing a time period when the message parameter is applied and an active location parameter describing a region where the message parameter is applied.

4. The mobile message device of claim 1, wherein the output device is further configured to present an address list to the user to allow selection of a source address.

5. The mobile message device of claim 1, wherein the processing core is further configured to identify a source that sent the incoming mobile message.

6. The mobile message device of claim 1, wherein the processing core is further configured to select an application module to execute the device action based on the response action directive.

7. The mobile message device of claim 1, wherein the output device is further configured to present a message parameter checklist to receive the message parameter.

8. The mobile message device of claim 1, wherein the input device is further configured to receive a text string from the user describing at least one of a text and a text fragment of the incoming mobile message.

9. The mobile message device of claim 1, wherein the output device is further configured to provide a text string to the user describing at least one of a text and a text fragment for selection as the message content.

10. The mobile message device of claim 1, wherein the output device is further configured to present an action directive checklist to receive the response action directive describing at least one of identifying a device location, causing the mobile message device to ring, forwarding the incoming mobile message, scheduling a meeting with the user, interacting with a smart assistant module, and activating an extension module added to the action directive checklist by the user.

11. The mobile message device of claim 1, wherein the input device is further configured to receive an accompanying text to be sent in conjunction with the device action.

12. The mobile message device of claim 1, wherein the input device is further configured to receive from the user via the message rule user interface a trigger parameter from a user describing a hypothetical meta device event occurring internal to the mobile message device and a message directive describing an outgoing mobile message to be sent upon an occurrence of a meta device event matching the trigger parameter.

13. A computing device, having a memory to store a series of instructions that are executed by at least one processor to implement a smart assistant module, the computing device configured to present a message rule user interface to the user with the smart assistant module to establish a message source rule;

receive from a user via the message rule user interface a trigger parameter describing a hypothetical meta device event occurring internal to the computing device;

receive from the user via the message rule user interface a message directive describing an outgoing mobile message selected from a plurality of outgoing mobile messages to be sent upon an occurrence of a meta device event matching the trigger parameter;

store a message source rule associating the trigger parameter with the message directive;

identify the occurrence of the meta device event matching the trigger parameter; and

send the outgoing mobile message upon the occurrence of the meta device event according to the message directive.

14. The computing device of claim 13, wherein the computing device is further configured to

present an address list to the user to allow selection of a target address.

15. The computing device of claim 13, wherein the computing device is further configured to

receive from the user at least one of a time trigger parameter describing a time, a timer trigger parameter describing an expiration of a timer, a location trigger parameter describing a location, a proximity trigger parameter describing a proximity to a different mobile message device as the trigger parameter, and an extension trigger parameter describing a custom trigger event entered by the user.

16. The computing device of claim 13, wherein the computing device is further configured to

select an application module to identify the meta device event.

17. The computing device of claim 13, wherein the computing device is further configured to

receive a text string from the user describing at least one of a text and a text fragment to include in the outgoing mobile message.

18. The computing device of claim 13, wherein the computing device is further configured to

incorporate a data output from at least one of a clock module, a calendar module, a location service module, an address book module, and an extension module into the outgoing mobile message.

19. A machine-implemented method, comprising:

presenting a message rule user interface with a smart assistant module to the user to establish a message target rule;

receiving in a mobile message device from a user via the message rule user interface a message parameter describing at least one of a message format and a message content of a hypothetical mobile message received in a mobile messaging module;

receiving from the user via the message rule user interface a response action directive describing a device action selected from a plurality of device actions to be performed by the mobile message device in response to receiving an incoming mobile message matching the message parameter;

store a message target rule associating the message parameter with the response action directive;

receiving an incoming mobile message matching the message parameter; and

executing the device action in response to the incoming mobile message according to the response action directive.

20. The method of claim 19, further comprising:

presenting an action directive checklist to receive the response action directive describing at least one of identifying a device location, causing the mobile message device to ring, forwarding the incoming mobile message, scheduling a meeting with the user, interacting with a smart assistant module, and activating an extension module added to the action directive checklist by the user.