TEXT MESSAGING CONVERSATION USER INTERFACE FUNCTIONALITY

• US 20090047983A1
• Filed: 10/22/2008
• Published: 02/19/2009
• Est. Priority Date: 12/13/2004
• Status: Active Grant

• Current Assignee: Google Technology Holdings LLC (Alphabet Inc.)
• Original Assignee: Blackberry Limited
• Inventors: Kuhl, Lawrence Edward, Klassen, Gerhard Dietrich, Wisebourt, Shaul S.
• Granted Patent: US 7,558,586 B2
• Time in Patent Office: Days
• US Class Current: 455/466
• CPC Class Codes: G06F 3/0482 Interaction with lists of selectable items, e.g. menus
• CPC Class Codes: G06F 3/0485 Scrolling or panning
• CPC Class Codes: G06F 3/0488 using a touch-screen or digitiser, e.g. input of commands through traced gestures
• CPC Class Codes: H04L 51/216 Handling conversation history, e.g. grouping of messages in sessions or threads
• CPC Class Codes: H04M 1/72436 for text messaging, e.g. short messaging services [SMS] or e-mails

Abstract

A computer readable medium, method and user device for a user interface functionality for SMS and SMS-like message conversations is provided. A group of individual SMS messages is treated as a single entity by the SMS conversation UI, the SMS conversation history UI saves space by including the SMS editor within the conversation history panel, and displays a pop-up display with useful information regarding the SMS message being edited.

Claims

1. A method for execution by a wireless user device to process SMS (Short Message Service) messages, the method comprising:

for each SMS message sent or received by the wireless user device, grouping the SMS message into one of a plurality of threads based on;

an address of a sender of the SMS message for each SMS message received by the wireless user device; and

an address of a receiver of the SMS message for each SMS message sent by the wireless user device;

for each thread;

displaying a respective UI (User Interface) display element representing the thread;

setting a focus on the thread in response to user selection of the UI display element representing the thread; and

while the focus is on the thread, performing a function upon each of the individual SMS messages of the thread in response to a user input.

2. The method of claim 1, wherein the user input comprises a user selection of a UI display item representing a thread function.

3. The method of claim 1 further comprising:

saving individual SMS messages as saved individual SMS messages in response to user input;

grouping saved individual SMS messages that do not belong to one of the plurality of threads; and

in response to a user input, displaying the saved individual SMS messages to/from a selected address in a display list.

4. The method of claim 2 wherein available thread functions comprise at least one of:

a thread delete function, and performing the individual function respectively upon each of the individual SMS messages comprises deleting each individual SMS message of the thread;

a thread save function, and performing the individual function respectively upon each of the individual SMS messages comprises saving each individual SMS message of the thread; and

a thread open function, and performing the individual function respectively upon each of the individual SMS messages comprises displaying each of the individual SMS messages of the thread in a conversation history display.

5. The method of claim 4 wherein the conversation history display comprises an indication of a current radio signal strength and an indication of a number of unread SMS messages.

6. The method of claim 4 wherein the conversation history display comprises a status for each SMS message displayed.

7. The method of claim 6 further comprising:

in response to a user input, displaying a display element in association with a particular text SMS message in the conversation history display, the display element providing an indication of an elapsed time since a status of the particular text SMS message last changed.

8. The method of claim 4 further comprising:

displaying a message editor as part of the conversation history display.

9. The method of claim 8 further comprising:

displaying a display element indicating a number of allowed characters remaining for a SMS message being edited.

10. The method of claim 8 further comprising:

automatically splitting a SMS message being composed into multiple SMS messages if the SMS message being composed is to long for a single SMS message;

while the SMS message is being composed, displaying a number of single SMS messages that will be sent.

11. The method of claim 4 wherein the SMS text messages in the conversation history display for a given thread are arranged vertically in chronological order thereby displaying a history of the thread.

12. The method of claim 4 wherein for a given thread, a title bar is displayed at the top of the conversation history display comprising an indication of an identity of the sender of an SMS text message received in the thread.

13. The method of claim 1 wherein the grouping and displaying are performed for messages for multiple different text messaging services to produce threads that are message threads of multiple different text messaging services.

14. The method of claim 1 wherein for each thread the respective UI element is a particular SMS text message that represents the thread.

15. The method of claim 1 wherein grouping comprises:

starting a new thread upon receipt of an SMS message from an address for which no thread has been started or upon transmission of an SMS message to an address for which no thread has been started;

adding each subsequent sent or received SMS message to an appropriate thread for the SMS message.

16. The method of claim 1 further comprising:

grouping at least one other individual SMS text message that does not belong to a thread; and

displaying the at least one other individual SMS text message in a display list.

17. The method of claim 4 wherein the display of each SMS text message in the conversation history display comprises a status selected from the group of being composed, saved as draft, sent successfully, not sent successfully, received, and opened.

18. The method of claim 17 further comprising:

for the conversation history display;

setting a focus on an individual SMS text message of the thread in response to a user selection of a US display item representing the individual SMS text message; and

displaying a message hint pop-up for the individual SMS text message with further information regarding the status displayed for the individual SMS text message, the hint pop-up comprising an indication of an elapsed time since the status of the focussed SMS text message last changed.

19. A computer readable medium having computer executable instructions stored thereon for execution on a processor so as to implement the method of claim 1.

20. A wireless device comprising:

a display screen;

an input panel; and

an SMS (Short Message Service) processing function operable to;

for each SMS message received or sent by the wireless device, group the SMS message into one of a plurality of threads based on;

an address of a sender of the SMS message for each SMS message received by the wireless device; and

an address of a receiver of the SMS message for each SMS message sent by the wireless device; and

for each thread;

display a respective UI (User Interface) display element representing the thread on the display screen;

set a focus on the thread in response to user selection of the UI display element representing the thread; and

while the focus is on the thread, perform a function upon each of the individual SMS messages of the thread in response to a user input.