Messaging system apparatuses circuits and methods of operation thereof

• US 9,489,661 B2
• Filed: 03/14/2011
• Issued: 11/08/2016
• Est. Priority Date: 02/16/2010
• Status: Active Grant

• Current Assignee: Tigerconnect Inc.
• Original Assignee: TigerText
• Inventors: Evans, Jeffrey, Brooks, Brad
• Primary Examiner(s): Nguyen, Dustin
• Application Number:
  US13/046,862
• Publication Number:
  US 20110202598A1
• Time in Patent Office: 2,066 Days
• Field of Search: 709/206, 709/238, 709/203, 709/207, 705/2, 713/166, 713/176, 455/466, 455/412.2, 707/100, 715/752, 726/1, 726/28
• US Class Current: 1/1
• 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 may include a messaging client device that may be configured to output web browser renderable code comprising a text message and further configured to manage the web browser renderable code in accordance with a message management policy associated with the text message. The messaging system may further include a messaging server that is configured to validate said messaging client device as complying with the message management policy prior to sending a link to the web browser renderable code. The messaging system may include a second messaging client device configured to validate a first messaging client device as complying with the message management policy prior to authorizing transmission of the message to the first messaging client device.

Claims

1. A messaging system comprising:

a messaging server configured to;

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

b) store the message in a database;

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

d) receive from the second mobile messaging client device a request to retrieve the message;

e) receive a message attribute comprising an instruction to limit a functionality of the message;

f) apply the message attribute to the message based on a message characteristic and update any existing corresponding message attribute; and

g) transmit the message and the message attribute to the second mobile messaging client device that manages the message in accordance with the message attribute, wherein managing the message comprises limiting the functionality of the message based on the message attribute.

2. The system of claim 1, wherein in d) the messaging server is further configured to:

receive from the second mobile messaging client device a request to retrieve the message, the request comprising client authentication data.

3. The system of claim 2, wherein the messaging server is further configured to:

prior to g), validate the second mobile messaging client device based on the client authentication data.

4. The system of claim 1, wherein the message characteristic comprises content of the message.

5. The system of claim 1, wherein the message characteristic comprises a recipient of the message.

6. The system of claim 1, wherein the messaging server is further configured to:

h) receive an updated message attribute comprising an instruction to limit a functionality of the message;

i) apply the updated message attribute to the message and update any existing corresponding message attribute; and

j) transmit at least the updated message attribute to the second mobile messaging client device.

7. The system of claim 1, wherein the messaging server is further configured to:

h) receive from the second mobile messaging client device an automatic notification that the second mobile messaging client device has managed the message in accordance with the message attribute.

8. The system of claim 1, wherein in a), the messaging server is further configured to:

receive a message and a message attribute from a first mobile messaging client device executing a messaging application and associated with a first authorized user.

9. The system of claim 1, wherein the messaging server is further configured to:

transmit to the second mobile messaging client device additional message attributes for the message.

10. The system of claim 1, wherein the message attribute is a predetermined message deletion time.

11. The system of claim 10, wherein the predetermined message deletion time is based on a time the second mobile messaging client device first displays the message.

12. The system of claim 1, wherein the message attribute is an amount of time during which the message may be accessed at the second mobile messaging client device.

13. The system of claim 1, wherein the message attribute is a number of times the message may be accessed at the second mobile messaging client device.

14. The system of claim 1, wherein the message attribute designates a geographic location of the second mobile messaging client device in which the message may be accessed.

15. The system of claim 1, wherein the message attribute comprises one or more of an ability to print, save, and forward the message.

16. The system of claim 1, wherein the message content includes at least one of text and an attachment.

17. The system of claim 1, wherein the messaging server is further configured to:

h) manage the message in accordance with the message attribute.

18. The system of claim 1, wherein the first authorized user defines the message attribute of the message.

19. The system of claim 1 or 18, wherein the messaging server edits the message attribute of the message.

20. The system of claim 1 or 19, wherein the messaging server adds one or more additional message attributes to the message.

21. The system of claim 1, wherein the messaging server is configured to allow a user having an administrator privilege to define the message attribute of the message.

22. The system of claim 1 or 21, wherein the message has an identified recipient group and the attribute of the message is based on the identified recipient group of the message.

23. The system of claim 1 or 21, wherein the message has an identified recipient position and the attribute of the message is based on the identified recipient position of the message.

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

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

b) storing the message in a database;

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

d) receiving from the second mobile messaging client device a request to retrieve the message;

e) receiving a message attribute comprising an instruction to limit a functionality of the message;

f) applying the message attribute to the message based on a message characteristic and updating any existing corresponding message attribute; and

g) transmitting the message and the message attribute to the second mobile messaging client device that manages the message in accordance with the message attribute, wherein managing the message comprises limiting the functionality of the message based on the message attribute.

25. The method of claim 24, wherein d) further comprises:

receiving from the second mobile messaging client device a request to retrieve the message, the request comprising client authentication data.

26. The method of claim 25, further comprising the step of, prior to g), validating the second mobile messaging client device based on the client authentication data.

27. The method of claim 24, wherein the message characteristic comprises content of the message.

28. The method of claim 24, wherein the message characteristic comprises a recipient of the message.

29. The method of claim 24, further comprising the steps of:

h) receiving an updated message attribute comprising an instruction to limit a functionality of the message;

i) applying the updated message attribute to the message and updating any existing corresponding message attribute; and

j) transmitting at least the updated message attribute to the second mobile messaging client device.

30. The method of claim 24, further comprising:

h) receiving from the second mobile messaging client device an automatic notification that the second mobile messaging client device has managed the message in accordance with the message attribute.

31. The method of claim 24, wherein step a) further comprises:

receiving a message and a message attribute from a first mobile messaging client device executing a messaging application and associated with a first authorized user.

32. The method of claim 24, further comprising:

h) transmitting to the second mobile messaging client device additional message attributes for the message.

33. The method of claim 24, wherein the message attribute is a predetermined message deletion time.

34. The method of claim 33, wherein the predetermined message deletion time is based on a time the second mobile messaging client device first displays the message.

35. The method of claim 24, wherein the message attribute is an amount of time during which the message may be accessed at the second mobile messaging client device.

36. The method of claim 24, wherein the message attribute is a number of times the message may be accessed at the second mobile messaging client device.

37. The method of claim 24, wherein the message attribute designates a geographic location of the second mobile messaging client device in which the message may be accessed.

38. The method of claim 24, wherein the message attribute comprises one or more of an ability to print, save, and forward the message.

39. The method of claim 24, wherein the message content includes at least one of text and an attachment.

40. The method of claim 24, further comprising:

h) managing the message in accordance with the message attribute.

41. The method of claim 24, wherein the first authorized user defines the message attribute of the message.

42. The method of claim 24 or 41, further comprising:

editing the message attribute of the message.

43. The method of claim 24 or 42, further comprising:

adding one or more additional message attributes to the message.

44. The method of claim 24, wherein the message attribute is defined by a user having an administrator privilege.

45. The method of claim 24 or 44, wherein the message has an identified recipient group and the attribute of the message is based on the identified recipient group of the message.

46. The method of claim 24 or 44, wherein the message has an identified recipient position and the attribute of the message is based on the identified recipient position of the message.