MESSAGING COMMUNICATION APPLICATION

• US 20120114108A1
• Filed: 09/26/2011
• Published: 05/10/2012
• Est. Priority Date: 09/27/2010
• Status: Abandoned Application

• Current Assignee: Voxer IP LLC (Voxer, Inc.)
• Original Assignee: Voxer IP LLC (Voxer, Inc.)
• Inventors: Katis, Thomas E., Panttaja, James T., Panttaja, Mary G., Ranney, Matthew J.
• Application Number:
  US13/245,690
• Publication Number:
  US 20120114108A1
• Time in Patent Office: Days
• US Class Current: 379/88.13
• CPC Class Codes: H04L 51/224 providing notification on incoming messages, e.g. pushed notifications of received messages
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04M 2203/65 related to applications where calls are combined with other types of communication
• CPC Class Codes: H04M 7/006 Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements

Abstract

A messaging application that includes a transmit module configured to progressively transmit time-based media of a message to a recipient as the media is created. The transmit module transmits the message in either a messaging mode where the time-based media of the message is transmitted before a delivery route to the recipient is completely discovered or a call mode where the transmission occurs after providing a notification requesting synchronous communication and receiving a confirmation that the recipient would like to engage in synchronous communication. In response to the notification, the recipient has the option of rendering the incoming message in either a real-time mode as the time-based media of the message is received or a time-shifted mode by rendering the time-based media of the message at an arbitrary later time after it was received.

Claims

1. A messaging application embedded in a computer readable medium, the messaging application including:

a notification module configured to receive a notification that provides a notification that a sender of a message containing time-based media would like to engage in synchronous communication; and

a rendering module configured to enable a recipient of the message to render the message in either;

(a) a real-time mode as the time-based media of the message is received;

or

(b) a time-shifted mode by rendering the time-based media of the message at an arbitrary later time after it was received; and

(c) one or more rendering options to seamlessly transition the rendering of the time-based media of the message between the two modes (a) and (b).

2. The messaging application of claim 1, further comprising a join module that enables the recipient to engage in synchronous communication with the sender in response to the notification.

3. The messaging application of claim 1, further comprising a screening module configured to enable the recipient of the incoming message to screen the message by rendering the time-based media of the incoming message as it is received, but without engaging in synchronous communication with the sender.

4. The messaging application of claim 1, further comprising an ignore feature that enables the recipient to ignore the message as the message is received.

5. The messaging application of claim 1, further comprising a storage module configured to progressively store in persistent storage the time-based media of the message as the time-based media of the incoming message is received.

6. The messaging application of claim 5, wherein the rendering module is configured to render the time-based media of the message in the time-shifted mode by retrieving and rendering the time-based media from persistent storage.

7. The messaging application of claim 1, wherein the rendering module provides one or more of the following rendering options:

play, pause, replay, play faster, play slower, jump backward, jump forward, catch up to the most recently received media, Catch up to Live (CTL), or jump to the most recently received media.

8. The messaging application of claim 1, further comprising a transmit module configured to transmit an outgoing message to the sender of the incoming message.

9. The messaging application of claim 8, wherein the transmit module is further configured to transmit the outgoing message synchronously with respect to the incoming message.

10. The messaging application of claim 8, wherein the transmit module is further configured to transmit the outgoing message asynchronously with respect to the incoming message.

11. The messaging application of claim 8, wherein the outgoing message contains time-based media.

12. The messaging application of claim 8, wherein the outgoing message contains text media.

13. The messaging application of claim 1, wherein the incoming message is transmitted as a progressive email, the progressive email including:

a header containing an identifier associated with the recipient; and

a body which progressively streams the time-based media within the body of the progressive email as the time based media is progressively transmitted by the sender.

14. The messaging application of claim 1, wherein the incoming message is transmitted as an HTTP message, the HTTP message including:

a header containing an identifier associated with the recipient; and

a body which progressively streams the time-based media within the body of the HTTP message as the time based media is progressively transmitted by the sender.

15. The messaging application of claim 1, wherein the incoming message includes a message header and a message body containing the time-based media of the message.

16. The messaging application of claim 15, wherein the message header is received ahead of and separate from the message body.

17. The messaging application of claim 15, wherein the message header contains one or more of the following:

(i) a first identifier identifying the recipient of the message;

(ii) a second identifier identifying the sender;

(iii) presence status of the sender; and

/or

(iv) meta data associated with the incoming message.

18. The messaging application of claim 1, further comprising a conversation module configured to string one or more transmitted and/or received messages into a conversation.

19. The messaging application of claim 18, further comprising a display module configured to display the one or more transmitted and/or received messages of the conversation in time-indexed order.

20. The messaging application of claim 19, wherein the rendering module is further configured to render the media of a selected message among the one or more transmitted and/or received messages of the conversation by selecting the selected message when displayed by the display module and then rendering the media of the selected message from storage.

21. The messaging application of claim 18, wherein the conversation module strings the transmitted and/or received messages into the conversation based on a common attribute, the common attribute comprising one of the following:

(i) a conversation name;

(ii) a name of a participant of the conversation;

(iii) a name of a user group;

or

(iv) a conversation topic.

22. A messaging application embedded in a computer readable medium, the messaging application including:

a message module configured to generate a message containing time based media;

a transmit module configured to progressively transmit the time-based media of the message to a recipient as the media is created in either;

(i) a messaging mode where the time-based media of the message is transmitted before a delivery route to the recipient is completely discovered;

or

(ii) a call mode after providing a notification requesting synchronous communication and receiving a confirmation that the recipient would like to engage in synchronous communication.

23. The messaging application of claim 22, wherein the messaging mode is implementing with a start message and an end message function.

24. The messaging application of claim 23, wherein the start message function and the end message function are implemented by one of the following:

(i) asserting a messaging function for the duration of the message;

or

(ii) asserting start and stop functions.

25. The messaging application of claim 22, wherein the notification comprises an audio notification, a visual notification, or both audio and visual notifications.

26. The messaging application of claim 22, wherein the messaging module is further configured to generate a text message and the transmit module is further configured to transmit the text message to the recipient.

27. The messaging application of claim 22, wherein the message generated by the message module comprises a message header and a message body.

28. The messaging application of claim 27, wherein the message body is configured to dynamically increase in size as the time-based media of the message is progressively created and added to the message.

29. The messaging application of claim 27, wherein the message header contains one or more of the following:

(i) a first identifier identifying the recipient of the message;

(ii) a second identifier identifying the sender;

(iii) information indicative of the presence status of the sender; and

/or

(iv) meta data associated with the incoming message.

30. The messaging application of claim 28, wherein the transmit module is further configured to transmit the message header ahead of and separate from the message body.

31. The messaging application of claim 27, wherein the message is a progressive email including the message header and the message body, wherein the message body progressively streams the time-based media of the message as the time based media is created and progressively transmitted by the transmit module.

32. The messaging application of claim 27, wherein the message is an HTTP message including the message header and the message body, wherein the message body progressively streams the time-based media of the message as the time based media is progressively transmitted by the transmit module.

33. The messaging application of claim 30, wherein the transmit module is further configured to progressively transmit the time-based media of the message as the media is created along a delivery route discovered using an identifier associated with the recipient and contained in the message header.

34. The messaging application of claim 30, wherein the transmit module is further configured to progressively transmit the time-based media of the message along the delivery route before the message is complete.

35. The messaging application of claim 22, further comprising a storage module configured to progressively store the time-based media of the message in persistent storage as the media is created.

36. The messaging application of claim 35, wherein the transmission module is further configured to transmit the time-based media from persistent storage after a communication device executing the communication applications connects to a communication network after being disconnected from the network when the time-based media of the message was created.