# US 8,788,605 B2 · System and method for handling electronic messages

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

- Number: US 8,788,605 B2
- Document ID: US8788605B2
- Status: Granted
- Kind: B2
- Application number: 13/534,691
- Filed: 2012-06-27
- Published: 2012-10-25
- Granted: 2014-07-22
- Earliest claimed: 2004-06-21
- Assignees: BlackBerry Limited
- Applicants: Neil Patrick Adams; Ian Robertson; David Victor MacFarlane; Herbert Anthony Little
- Inventors: Neil Patrick Adams; Ian Robertson; David Victor MacFarlane; Herbert Anthony Little
- Web page: https://patentgrep.com/patent/US8788605B2

## CPC

- H04L 51/212: using filtering or selective blocking
- G06Q 10/107: Computer-aided management of electronic mailing [e-mailing]
- H04M 1/72436: for text messaging, e.g. short messaging services [SMS] or e-mails
- H04L 51/58: Message adaptation for wireless communication
- H04M 1/72451: according to schedules, e.g. using calendar applications
- H04W 4/12: Messaging; Mailboxes; Announcements
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- 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
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Systems and methods for handling messages on a mobile device. A system and method could be configured to receive at a mobile device a message that is associated with a message expiry indicator. If a message expiry indicator is determined to be associated with the received message, then the received message is removed from the mobile device.

## Claims

### Claim 1

A server comprising:
a processor configured to:
receive a message;
re-envelope the message as a secure message;
determine whether a message expiry attribute is associated with the message;
automatically set a message expiry attribute for the message based on re-enveloping the message as a secure message when there is not a message expiry attribute already associated with the message;
not setting a message expiry attribute on re-enveloping the message if there is a message expiry attribute already associated with the message; and
forward the message.

### Claim 2 (depends on 1)

The server of claim 1, wherein the message is an e-mail message.

### Claim 3 (depends on 2)

The server of claim 2, wherein information contained in the message expiry attribute is encoded in a signed attribute of the e-mail message.

### Claim 4 (depends on 1)

The server of claim 1, wherein the message contains a timeout notification expiry attribute.

### Claim 5 (depends on 1)

The server of claim 1, wherein the message expiry attribute specifies a period of time.

### Claim 6 (depends on 1)

The server of claim 1, wherein the message comprises a PGP message or an S/MIME message.

### Claim 7

A mobile device comprising:
a processor configured to:
generate a message; and
subsequent to creating the message, request an input at a user interface to select whether a message expiry attribute should be associated with the message;
receive the input;
if the message expiry attribute is to be associated with the message, automatically associate a predetermined type of message expiry attribute based upon contents of the message; and
send the message with the message expiry attribute.

### Claim 8 (depends on 7)

The mobile device of claim 7, wherein information contained in the message expiry attribute is encoded in a signed attribute of the message.

### Claim 9 (depends on 7)

The mobile device of claim 7, wherein the removal criterion is based upon whether the message has been accessed by a user.

### Claim 10 (depends on 7)

The mobile device of claim 7, wherein the removal criterion is based upon whether a receiving mobile device has received complete contents of the message and whether the complete contents of the message have been displayed on the receiving mobile device.

### Claim 11 (depends on 7)

The mobile device of claim 7, wherein the removal criterion is time-based.

### Claim 12 (depends on 11)

The mobile device of claim 11, wherein the message contains a timeout notification expiry attribute;
wherein a timer is set for the timeout period specified in the timeout notification expiry attribute;
wherein when the timer expires, the message is automatically removed from the mobile device.

### Claim 13 (depends on 12)

The mobile device of claim 12, wherein the timer is started after the message is closed at a receiving mobile device or when the message is received at the receiving mobile device.

### Claim 14

A mobile device comprising a processor configured to:
generate a message comprising a message expiry attribute;
present, at a user interface, an option of setting the message expiry attribute; and
determine, by the processor, that the option of setting the message expiry attribute is not elected at the user interface; and
automatically set the message expiry attribute based upon the determination and based upon contents of the message.

### Claim 15 (depends on 14)

The mobile device of claim 14, wherein the message contents comprise a classification marking.

### Claim 16 (depends on 14)

The mobile device of claim 14, wherein the removal criterion is based on one of:
whether the message has been read;
an amount of time after the message has been received; and
an amount of time after the message has been closed.