Messaging system apparatuses circuits and methods of operation thereof

• US 10,257,125 B2
• Filed: 07/29/2016
• Issued: 04/09/2019
• Est. Priority Date: 02/16/2010
• Status: Active Grant

• Current Assignee: Tigerconnect Inc.
• Original Assignee: Tigerconnect Inc.
• Inventors: Brooks, Andrew, Brooks, Brad, Bhatia, Sumeet, Evans, Jeffrey
• Primary Examiner(s): Nguyen, Dustin
• Application Number:
  US15/224,472
• Publication Number:
  US 20160337280A1
• Time in Patent Office: 984 Days
• CPC Class Codes: G06F 21/10 Protecting distributed programs or content, e.g. vending or licensing of copyrighted material protection in video systems or pay television H04N7/16 ; Digital rights management [DRM]
• CPC Class Codes: G06F 2221/2111 Location-sensitive, e.g. geographical location, GPS
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/06 Message adaptation to terminal or network requirements
• CPC Class Codes: H04L 51/08 Annexed information, e.g. attachments
• CPC Class Codes: H04L 51/214 using selective forwarding
• CPC Class Codes: H04L 51/222 using geographical location information, e.g. messages transmitted or received in proximity of a certain spot or area
• CPC Class Codes: H04L 51/224 providing notification on incoming messages, e.g. pushed notifications of received messages
• CPC Class Codes: H04L 51/23 Reliability checks, e.g. acknowledgments or fault reporting
• CPC Class Codes: H04L 51/56 Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements

Abstract

A messaging system including a server configured to receive a message from a second messaging device, transmit to a first messaging device a notification of the presence of the message at the server, transmit the message and a message attribute to the first messaging device, where the message and the message attribute are stored in non-volatile memory in the first messaging device at least until the message is managed by the first messaging device in accordance with the message attribute, and wherein the message attribute comprises a predetermined message viewing time after which at least a portion of the message cannot be displayed at the first messaging device, and receive from the first messaging device a message management notification generated by the first messaging device in connection with managing the message in accordance with the message attribute at the first messaging device.

Claims

1. A messaging system comprising:

a first mobile messaging client device executing a messaging application and associated with a first authorized user, the first mobile messaging client device having a processor configured to;

a) receive from a messaging server a notification of the presence of a message at the messaging server, where the message is addressed to the first authorized user;

b) send to the messaging server a request to retrieve the message, the request including client authentication data, where the first mobile messaging client device sends the request automatically in response to receipt of the notification;

c) receive the message, the message having message content;

d) manage the message in accordance with a message attribute, wherein managing the message comprises limiting a functionality of the message based on the message attribute, where the message and the message attribute are stored in non-volatile memory in the first mobile messaging client device at least until the message is managed by the first mobile messaging client device in accordance with the message attribute, and wherein the message attribute comprises a predetermined message viewing time after which at least a portion of the message content cannot be displayed at the first mobile messaging client device; and

e) send to the messaging server a message management notification;

the messaging server having a processor configured to;

a) receive the message addressed to the first authorized user from the second mobile messaging client device executing the messaging application and associated with a second authorized user;

b) store the message in a database;

c) transmit to the first mobile messaging client device the notification of the presence of the message at the messaging server;

d) receive from the first mobile messaging client device the request to retrieve the message, the request including client authentication data;

e) validate the first mobile messaging client device based on the client authentication data;

f) transmit the message to the first mobile messaging client device; and

g) receive from the first mobile messaging client device the message management notification.

2. The system of claim 1, wherein the message management notification is sent from the first mobile messaging client device after the first mobile messaging client device manages the message and indicates the first mobile messaging client device managed the message in accordance with the message attribute.

3. The system of claim 1, wherein the message attribute is set by the second authorized user at the second mobile messaging client device and is transmitted from the second mobile messaging device to the first mobile messaging client device via the messaging server.

4. The system of claim 1, wherein the message management notification is sent from the first mobile messaging client device before the first mobile messaging client device manages the message.

5. The system of claim 1, wherein the message attribute further comprises a predetermined message deletion time, and the predetermined message deletion time is based on a time the second mobile messaging client device sends the message.

6. The system of claim 1, wherein the predetermined message viewing time is based on a time a second mobile messaging client device sends the message.

7. The system of claim 1, wherein the message attribute further comprises a number of times the message may be accessed at the first mobile messaging client device.

8. A messaging system comprising a messaging server having a processor configured to:

a) receive a message from a second mobile messaging client device executing a messaging application and associated with a second authorized user;

b) store the message in a database;

c) transmit to a first mobile messaging client device executing the messaging application and associated with a first authorized user, a notification of the presence of the message at the messaging server, where the message is addressed to the first authorized user;

d) receive from the first mobile messaging client device a request to retrieve the message, the request including client authentication data;

e) validate the first mobile messaging client device based on the client authentication data;

f) transmit the message and a message attribute to the first mobile messaging client device, where the message and the message attribute are stored in non-volatile memory in the first mobile messaging client device at least until the message is managed by the first mobile messaging device in accordance with the message attribute, and wherein the message attribute comprises a predetermined message viewing time after which at least a portion of the message cannot be displayed at the first mobile messaging device; and

g) receive from the first mobile messaging client device a message management notification generated by the first mobile messaging client device in connection with managing the message in accordance with the message attribute at the first mobile messaging client device.

9. The system of claim 8, wherein the message management notification is sent from the first mobile messaging client device after the first mobile messaging client device manages the message and indicates the first mobile messaging client device managed the message in accordance with the message attribute.

10. The system of claim 8, wherein the messaging server is further configured to:

prior to f), receive the message attribute from the second authorized user at the second mobile messaging client device.

11. The system of claim 8, wherein the messaging server is further configured to:

h) manage the message at the messaging server in accordance with the message attribute.

12. The system of claim 11, wherein in h) the messaging server deletes the message from the database.

13. The system of claim 8, wherein the message attribute comprises a predetermined message deletion time, and the predetermined message deletion time is based on a time the second mobile messaging client device sends the message.

14. The system of claim 8, wherein the predetermined message viewing time is based on a time the second mobile messaging client sends the message.

15. The system of claim 8, wherein the message management notification is sent from the first mobile messaging client device before the first mobile messaging client device manages the message.

16. The system of claim 8, wherein the message attribute further comprises a number of times the message may be accessed at the first mobile messaging client device.

17. A method for managing a messaging system comprising the steps of:

a) receiving at a messaging server a message addressed to a first authorized user from a second mobile messaging client device executing a messaging application and associated with a second authorized user;

b) storing the message in a database;

c) transmitting from the messaging server to a first mobile messaging client device executing the messaging application and associated with a first authorized user, a notification of the presence of the message at the messaging server;

d) receiving at the messaging server from the first mobile messaging client device a request to retrieve the message, the request including client authentication data;

e) validating the first mobile messaging client device at the messaging server based on the client authentication data;

f) transmitting the message and a message attribute from the messaging server to the first mobile messaging client device, where the message and the message attribute are stored in non-volatile memory in the first mobile messaging client device at least until the message is managed by the first mobile messaging device in accordance with the message attribute, and wherein the message attribute comprises a predetermined message viewing time after which at least a portion of the message cannot be displayed at the first mobile messaging device;

g) managing the message in accordance with the message attribute at the messaging server; and

h) receiving at the messaging server from the first mobile messaging client device a message management notification generated by the first mobile messaging client device in connection with managing the message in accordance with the message attribute at the first mobile messaging client device.

18. The method of claim 17, wherein the message notification is sent from the first mobile messaging client device after the first mobile messaging client device manages the message and indicates the first mobile messaging client device managed the message in accordance with the message attribute.

19. The method of claim 17, further comprising:

prior to f), receiving the message attribute from the second authorized user at the second mobile messaging client device.

20. The method of claim 17, wherein in step g) the messaging server deletes the message from the database.

21. The method of claim 17, wherein the message attribute comprises a predetermined message deletion time, and the predetermined message deletion time is based on a time the second mobile messaging client device sends the message.

22. The method of claim 17, wherein the predetermined message viewing time is based on a time the second mobile messaging client sends the message.

23. The method of claim 17, wherein the message management notification is sent from the first mobile messaging client device before the first mobile messaging client device manages the message.

24. The method of claim 17, wherein the message attribute comprises a number of times the message may be accessed at the first mobile messaging client device.