# US 2018/0176158 A1 · Messaging System Apparatuses Circuits and Methods of Operation Thereof

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2018/0176158 A1
- Document ID: US20180176158A1
- Status: Published application
- Kind: A1
- Application number: 15/899,162
- Filed: 2018-02-19
- Published: 2018-06-21
- Earliest claimed: 2010-02-16
- Assignees: TigerText, Inc.
- Applicants: TigerText, Inc.
- Inventors: Jeffrey Evans; Brad Brooks
- Web page: https://patentgrep.com/patent/US20180176158A1

## CPC

- H04L 51/04: Real-time or near real-time messaging, e.g. instant messaging [IM]
- 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]}
- G06Q 10/107: Computer-aided management of electronic mailing [e-mailing]
- H04L 51/06: Message adaptation to terminal or network requirements
- H04L 51/08: Annexed information, e.g. attachments
- H04L 51/214: using selective forwarding
- H04L 51/222: using geographical location information, e.g. messages transmitted or received in proximity of a certain spot or area
- H04L 51/224: providing notification on incoming messages, e.g. pushed notifications of received messages
- H04L 51/23: Reliability checks, e.g. acknowledgments or fault reporting
- H04L 51/56: Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 63/102: {Entity profiles}
- H04W 4/12: Messaging; Mailboxes; Announcements
- G06F 2221/2111: Location-sensitive, e.g. geographical location, GPS
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A messaging system configured to receive a message from a first mobile messaging client device, transmit to a second mobile messaging client device a notification of the presence of the message, receive a message attribute comprising an instruction to limit a functionality of the message, apply the message attribute to the message based on a message characteristic and update any existing corresponding message attribute, and transmit the message and the message attribute to the second mobile messaging client device where the message and the message attribute are stored in non-volatile memory at least until the second mobile messaging client device manages the message in accordance with the message attribute, wherein managing the message comprises limiting functionality of the message based on the message attribute, wherein the message attribute comprises a predetermined message viewing time after which the message content cannot be accessed at the second mobile messaging client device.

## Claims

### Claim at position 1

1-28. (canceled)

### Claim 29

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 where the message and the message attribute are stored in non-volatile memory at least until the second mobile messaging client device 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.

### Claim 30 (depends on 29)

The system of claim 29, 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.

### Claim 31 (depends on 30)

The system of claim 30, wherein the messaging server is further configured to: prior to g), validate the second mobile messaging client device based on the client authentication data.

### Claim 32 (depends on 29)

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

### Claim 33 (depends on 29)

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

### Claim 34 (depends on 29)

The system of claim 29, 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.

### Claim 35 (depends on 29)

The system of claim 29, 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.

### Claim 36 (depends on 29)

The system of claim 29, 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.

### Claim 37 (depends on 29)

The system of claim 29, wherein the messaging server is further configured to: transmit to the second mobile messaging client device additional message attributes for the message.

### Claim 38 (depends on 29)

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

### Claim 39 (depends on 38)

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

### Claim 40 (depends on 29)

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

### Claim 41 (depends on 29)

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

### Claim 42 (depends on 29)

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

### Claim 43 (depends on 29)

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

### Claim 44 (depends on 29)

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

### Claim 45 (depends on 29)

The system of claim 29, wherein the messaging server is further configured to: h) manage the message in accordance with the message attribute.

### Claim 46 (depends on 29)

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

### Claim 47 (depends on 29, 46)

The system of claim 29 or 46, wherein the messaging server edits the message attribute of the message.

### Claim 48 (depends on 29, 47)

The system of claim 29 or 47, wherein the messaging server adds one or more additional message attributes to the message.

### Claim 49 (depends on 29)

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

### Claim 50 (depends on 29, 49)

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

### Claim 51 (depends on 29, 49)

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

### Claim 52

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.

### Claim 53 (depends on 52)

The method of claim 52, wherein d) further comprises: receiving from the second mobile messaging client device a request to retrieve the message, the request comprising client authentication data.

### Claim 54 (depends on 53)

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

### Claim 55 (depends on 52)

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

### Claim 56 (depends on 52)

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

### Claim 57 (depends on 52)

The method of claim 52, 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.

### Claim 58 (depends on 52)

The method of claim 52, 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.

### Claim 59 (depends on 52)

The method of claim 52, 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.

### Claim 60 (depends on 52)

The method of claim 52, further comprising: h) transmitting to the second mobile messaging client device additional message attributes for the message.

### Claim 61 (depends on 52)

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

### Claim 62 (depends on 61)

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

### Claim 63 (depends on 52)

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

### Claim 64 (depends on 52)

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

### Claim 65 (depends on 52)

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

### Claim 66 (depends on 52)

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

### Claim 67 (depends on 52)

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

### Claim 68 (depends on 52)

The method of claim 52, further comprising: h) managing the message in accordance with the message attribute.

### Claim 69 (depends on 52)

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

### Claim 70 (depends on 52, 69)

The method of claim 52 or 69, further comprising: editing the message attribute of the message.

### Claim 71 (depends on 52, 70)

The method of claim 52 or 70, further comprising: adding one or more additional message attributes to the message.

### Claim 72 (depends on 52)

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

### Claim 73 (depends on 52, 72)

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

### Claim 74 (depends on 52, 72)

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