IP Library Granted Patent US 9,443,227
Granted Patent B2
US 9,443,227 · App. 13/063,763 · Granted Sep 13, 2016

Messaging system apparatuses circuits and methods of operation thereof

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,443,227
App. No.
13/063,763
Granted
Sep 13, 2016
Kind
B2
Abstract

A messaging system may include a messaging client device that may be configured to receive an impermanent text message and may be further configured to manage the impermanent text message in accordance with a message management policy associated with the impermanent text message. The messaging system may further include an impermanent messaging server configured to validate the messaging client device as complying with the message management policy prior to authorizing a transmission of the impermanent text message to the messaging client device. The messaging system may include a distributed network gateway server configured to validate the messaging client device as complying with a message management policy prior to authorizing transmission of the impermanent text message to the messaging client device.

Claims (53)

1. A messaging system comprising:

a first mobile messaging client device executing a messaging application and associated with a first authorized user, the 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 device in accordance with the message attribute; 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 a 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 first mobile messaging client device first displays the message.

6. The system of claim 1 , 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 device, and the predetermined message viewing time is based on a time the first mobile messaging client device first displays 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

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 message attribute comprises a predetermined message viewing time after which at least a portion of a content of the message cannot be displayed at the first mobile messaging device, and the predetermined message viewing time is based on a time the first mobile messaging client device first displays the message.

11. 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.

12. 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.

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

14. 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 first mobile messaging client device first displays 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;

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 attribute comprises a predetermined message viewing time after which at least a portion of a content of the message cannot be displayed at the first mobile messaging device, and the predetermined message viewing time is based on a time the first mobile messaging client device first displays the message.

19. 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.

20. 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.

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

22. 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 first mobile messaging client device first displays 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.

Assignments (10)
RELEASE OF SECURITY INTEREST IN INTELLECTUAL PROPERTY AT REEL/FRAME NO. 41987/0885 Recorded Feb 16, 2022
From: CANADIAN IMPERIAL BANK OF COMMERCE (AS SUCCESSOR IN INTEREST TO WF FUND V LIMITED PARTNERSHIP)
To: TIGERCONNECT, INC. (FORMERLY KNOWN AS TIGERTEXT, INC.)
Reel/Frame 059165/0978 →
CHANGE OF NAME Recorded Dec 14, 2018
From: TIGERTEXT, INC.
To: TIGERCONNECT INC.
Reel/Frame 047911/0880 →
RELEASE OF SECURITY INTEREST Recorded Aug 17, 2018
From: SILICON VALLEY BANK
To: TIGERCONNECT, INC. (F/K/A TIGERTEXT, INC.)
Reel/Frame 046848/0785 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 12, 2018
From: BHATIA, SUMEET
To: TIGERCONNECT, INC.
Reel/Frame 046052/0125 →
ASSIGNMENT AND ASSUMPTION OF SECURITY INTERESTS Recorded Jan 9, 2018
From: WF FUND V LIMITED PARTNERSHIP, C/O/B/ AS WELLINGTON FINANCIAL LP AND WELLINGTON FINANCIAL FUND V
To: CANADIAN IMPERIAL BANK OF COMMERCE
Reel/Frame 045028/0880 →
RELEASE OF SECURITY INTEREST Recorded Apr 13, 2017
From: FIFTH STREET FINANCE CORP.
To: TIGERTEXT, INC.
Reel/Frame 042005/0423 →
SECURITY INTEREST Recorded Apr 12, 2017
From: TIGERTEXT, INC.
To: WF FUND V LIMITED PARTNERSHIP
Reel/Frame 041987/0885 →
SECURITY INTEREST Recorded Aug 6, 2015
From: TIGERTEXT, INC.
To: SILICON VALLEY BANK
Reel/Frame 036263/0307 →
SECURITY INTEREST Recorded Dec 10, 2014
From: TIGERTEXT, INC.
To: FIFTH STREET FINANCE CORPORATION
Reel/Frame 034456/0045 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 20, 2012
From: EVANS, JEFFREY; BROOKS, BRAD
To: TIGERTEXT, INC.
Reel/Frame 028994/0011 →