IP Library Granted Patent US 12,198,103
Granted Patent B2
US 12,198,103 · App. 18/045,370 · Granted Jan 14, 2025

System and method for displaying message history when composing a message

Inventors: Leonid Vymenets (Toronto, CA); Francis Thomas Riddle (Portsmouth, NH); Henry Yao-Tsu Chen (Redmond, WA)
Assignee: Malikie Innovations Limited
G06Q10/107G06F3/0484G06F40/10
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 12,198,103
App. No.
18/045,370
Granted
Jan 14, 2025
Kind
B2
Abstract

A system and a method are provided for displaying message history while composing a message. The method includes displaying a message composition application comprising a first recipient field, a message history display area, and a message composition field; detecting an input into the first recipient field for specifying a recipient; and upon detecting that the recipient has been specified: displaying a second recipient field; navigating application focus from the first recipient field to the second recipient field; and displaying a message history associated with the recipient in the message history display area.

Claims (65)

1. A method of operating a mobile device comprising:

displaying a message composition application comprising a user interface, the user interface comprising:

a first recipient field;

a message history display area separate from the first recipient field; and

a message composition field separate from the message history display area and the first recipient field;

receiving first text input via the first recipient field;

displaying, in a first recipient dropdown list, candidate recipient addresses having names containing at least some letters that match the first text input in the first recipient field;

selecting, from the first recipient dropdown list, a first one of the candidate recipient addresses as a first recipient;

displaying, in the message history display area, a first message history comprising messages exchanged between the first recipient and a user of the mobile device in response to selecting the first recipient;

displaying, in response to selecting the first recipient, a second recipient field, wherein the first recipient field is separate from the second recipient field;

receiving second text input via the second recipient field;

displaying, in a second recipient dropdown list, candidate recipient addresses having names containing at least some letters that match the second text input in the second recipient field;

selecting, from the second recipient dropdown list, a second one of the candidate recipient addresses as a second recipient; and

replacing, in the message history display area and in response to selecting the second recipient, the first message history with a second message history comprising group messages exchanged between each of the first recipient, the second recipient, and the user of the mobile device.

2. The method of claim 1 , further comprising:

receiving input into the message composition field before receiving the first text input via the first recipient field, wherein the message composition field maintains the input after receiving the first text input via the first recipient field and after receiving the second text input via the second recipient field.

3. The method of claim 1 , further comprising:

receiving input into the message composition field before receiving the first text input via the first recipient field; and

sending, when the first recipient and the second recipient are not associated with a same recipient, a text message comprising the input in the message composition field to the first recipient and the second recipient.

4. The method of claim 1 , further comprising navigating, in response to displaying the second recipient field, an application focus from the first recipient field to the second recipient field.

5. The method of claim 4 , further comprising continuing to display the first recipient field and the second recipient field when the application focus has moved from the second recipient field to the message composition field.

6. A non-transitory computer readable medium comprising computer executable instructions that, when executed by a processor, cause a mobile device to:

display a message composition application comprising a user interface, the user interface comprising:

a first recipient field;

a message history display area separate from the first recipient field; and

a message composition field separate from the message history display area and the first recipient field;

receive first text input via the first recipient field;

display, in a first recipient dropdown list, candidate recipient addresses having names containing at least some letters that match the first text input in the first recipient field;

select, from the first recipient dropdown list, a first one of the candidate recipient addresses as a first recipient;

display, in the message history display area, a first message history comprising messages exchanged between the first recipient and a user of the mobile device in response to selecting the first recipient;

display, in response to selecting the first recipient, a second recipient field, wherein the first recipient field is separate from the second recipient field;

receive second text input via the second recipient field;

display, in a second recipient dropdown list, candidate recipient addresses having names containing at least some letters that match the second text input in the second recipient field;

select, from the second recipient dropdown list, a second one of the candidate recipient addresses as a second recipient; and

replace, in the message history display area and in response to selecting the second recipient, the first message history a second message history comprising group messages exchanged between each of the first recipient, the second recipient, and the user of the mobile device.

7. The non-transitory computer readable medium of claim 6 , wherein the computer executable instructions, when executed by the processor, further cause the mobile device to:

receive input into the message composition field before receiving the first text input via the first recipient field, wherein the message composition field maintains the input after receiving the first text input via the first recipient field and after receiving the second text input via the second recipient field.

8. The non-transitory computer readable medium of claim 6 , wherein the computer executable instructions, when executed by the processor, further cause the mobile device to:

receive input into the message composition field before receiving the first text input via the first recipient field; and

send, when the first recipient and the second recipient are not associated with a same recipient, a text message comprising the input in the message composition field to the first recipient and the second recipient.

9. The non-transitory computer readable medium of claim 6 , wherein the computer executable instructions, when executed by the processor, further cause the mobile device to navigate, in response to displaying the second recipient field, an application focus from the first recipient field to the second recipient field.

10. The non-transitory computer readable medium of claim 9 , wherein the computer executable instructions, when executed by the processor, further cause the mobile device to continue to display the first recipient field and the second recipient field when the application focus has moved from the second recipient field to the message composition field.

11. A mobile device comprising:

a memory configured to store computer executable instructions; and

a processor coupled to memory and configured to execute the computer executable instructions to cause the mobile device to:

display a message composition application comprising a user interface, the user interface comprising:

a first recipient field;

a message history display area separate from the first recipient field; and

a message composition field separate from the message history display area and the first recipient field;

receive first text input, input via the first recipient field;

display, in a first recipient dropdown list, candidate recipient addresses having names containing at least some letters that match the first text input in the first recipient field;

select, from the first recipient dropdown list, a first one of the candidate recipient addresses as a first recipient;

display, in the message history display area, a first message history comprising messages exchanged between the first recipient and a user of the mobile device in response to selecting the first recipient;

display, in response to selecting the first recipient, a second recipient field, wherein the first recipient field is separate from the second recipient field;

receive second text input via the second recipient field;

display, in a second recipient dropdown list, candidate recipient addresses having names containing at least some letters that match the second text input in the second recipient field;

select, from the second recipient dropdown list, a second one of the candidate recipient addresses as a second recipient; and

replace, in the message history display area and in response to selecting the second recipient, the first message history with a second message history comprising group messages exchanged between each of the first recipient, the second recipient, and the user of the mobile device.

12. The mobile device of claim 11 , wherein the processor is further configured to execute the computer executable instructions to cause the mobile device to:

receive input into the message composition field before receiving the first text input via the first recipient field, wherein the message composition field maintains the input after receiving the first text input via the first recipient field and after receiving the second text input via the second recipient field.

13. The mobile device of claim 11 , wherein the processor is further configured to execute the computer executable instructions to cause the mobile device to:

receive input into the message composition field before receiving the first text input via the first recipient field; and

send, when the first recipient and the second recipient are not associated with a same recipient, a text message comprising the input in the message composition field to the first recipient and the second recipient.

14. The mobile device of claim 11 , wherein the processor is further configured to execute the computer executable instructions to cause the mobile device to navigate, in response to displaying the second recipient field, an application focus from the first recipient field to the second recipient field.

15. The mobile device of claim 14 , wherein the processor is further configured to execute the computer executable instructions to cause the mobile device to continue to display the first recipient field and the second recipient field when the application focus has moved from the second recipient field to the message composition field.

Assignments (5)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 16, 2023
From: BLACKBERRY LIMITED
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064104/0103 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 10, 2023
From: RIDDLE, FRANCIS THOMAS
To: RESEARCH IN MOTION CORPORATION
Reel/Frame 062325/0506 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 10, 2023
From: VYMENETS, LEONID; CHEN, HENRY YAO-TSU
To: RESEARCH IN MOTION LIMITED
Reel/Frame 062325/0549 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 10, 2023
From: RESEARCH IN MOTION CORPORATION
To: RESEARCH IN MOTION LIMITED
Reel/Frame 062325/0602 →
CHANGE OF NAME Recorded Jan 10, 2023
From: RESEARCH IN MOTION LIMITED
To: BLACKBERRY LIMITED
Reel/Frame 062338/0806 →
Continuity (2)
Continuation 13295404 · Nov 14, 2011
Related Publication 20230110143A1 · Apr 13, 2023
References Cited (78)
US 7328242B1 · McCarthy et al. · 2008 [cited by applicant]
US 8001181B2 · Wilson et al. · 2011 [cited by applicant]
US 8754572B2 · Behforooz et al. · 2014 [cited by applicant]
US 20020023128A1 · Matsumoto et al. · 2002 [cited by applicant]
US 20030146939A1 · Petropoulos et al. · 2003 [cited by applicant]
US 20040015548A1 · Lee · 2004 [cited by applicant]
US 20040015553A1 · Griffin et al. · 2004 [cited by applicant]
US 20040137884A1 · Engstrom et al. · 2004 [cited by applicant]
US 20050091612A1 · Stabb et al. · 2005 [cited by applicant]
US 20050166154A1 · Wilson et al. · 2005 [cited by applicant]
US 20050203929A1 · Hazarika et al. · 2005 [cited by applicant]
US 20060116164A1 · Kang · 2006 [cited by applicant]
US 20060128404A1 · Klassen et al. · 2006 [cited by applicant]
US 20060197753A1 · Hotelling · 2006 [cited by applicant]
US 20060217965A1 · Babu · 2006 [cited by applicant]
US 20060221957A1 · Ozawa et al. · 2006 [cited by applicant]
US 20060288298A1 · Haitani et al. · 2006 [cited by applicant]
US 20070005715A1 · LeVasseur et al. · 2007 [cited by applicant]
US 20070198474A1 · Davidson et al. · 2007 [cited by applicant]
US 20070242061A1 · Rhoten et al. · 2007 [cited by applicant]
US 20070245006A1 · Lehikoinen et al. · 2007 [cited by applicant]
US 20070280179A1 · Van Belle · 2007 [cited by examiner]
US 20070283044A1 · Van Bell et al. · 2007 [cited by applicant]
US 20080040437A1 · Agarwal et al. · 2008 [cited by applicant]
US 20080153459A1 · Kansal et al. · 2008 [cited by applicant]
US 20080222118A1 · Scian et al. · 2008 [cited by applicant]
US 20080250107A1 · Holzer et al. · 2008 [cited by applicant]
US 20080307322A1 · Stochosky et al. · 2008 [cited by applicant]
US 20090005011A1 · Christie et al. · 2009 [cited by applicant]
US 20090007012A1 · Mandic et al. · 2009 [cited by applicant]
US 20090037413A1 · Castell et al. · 2009 [cited by applicant]
US 20090061825A1 · Neelakantan et al. · 2009 [cited by applicant]
US 20090177617A1 · Lee · 2009 [cited by applicant]
US 20090177981A1 · Christie et al. · 2009 [cited by applicant]
US 20100100852A1 · Buchanan · 2010 [cited by applicant]
US 20100162133A1 · Pascal et al. · 2010 [cited by applicant]
US 20100217808A1 · Benninger · 2010 [cited by applicant]
US 20100217809A1 · Vymenets et al. · 2010 [cited by applicant]
US 20100223547A1 · Wilson et al. · 2010 [cited by applicant]
US 20100235523A1 · Garcia et al. · 2010 [cited by applicant]
US 20100267369A1 · Lim et al. · 2010 [cited by applicant]
US 20110087970A1 · Swink et al. · 2011 [cited by applicant]
US 20110179126A1 · Wetherell · 2011 [cited by examiner]
US 20110230178A1 · Jones et al. · 2011 [cited by applicant]
US 20110252317A1 · Keranen et al. · 2011 [cited by applicant]
US 20120077469A1 · Bhogal et al. · 2012 [cited by applicant]
US 20120331405A1 · Eidelson et al. · 2012 [cited by applicant]
US 20130055111A1 · Peyton et al. · 2013 [cited by applicant]
US 20130125019A1 · Vymenets et al. · 2013 [cited by applicant]
EP 1271286A2 · 2003 [cited by applicant]
EP 2381402A1 · 2011 [cited by applicant]
EP 2385689A1 · 2011 [cited by applicant]
WO 2006043977A1 · 2006 [cited by applicant]
Lee, Rob; “Group Messaging—iPhone iOS4 Does—Android 2.1 Doesn't”; retrieved from https://www.youtube.com/watch?v=pXbPTjOXjE8; Jul. 19, 2010; 6 pages. [cited by applicant]
Office Action dated Nov. 7, 2014; U.S. Appl. No. 13/295,404, filed Nov. 14, 2011; 23 pages. [cited by applicant]
Final Office Action dated Jun. 22, 2015; U.S. Appl. No. 13/295,404, filed Nov. 14, 2011; 26 pages. [cited by applicant]
Advisory Action dated Sep. 18, 2015; U.S. Appl. No. 13/295,404, filed Nov. 14, 2011; 4 pages. [cited by applicant]
Office Action dated Nov. 17, 2015; U.S. Appl. No. 13/295,404, filed Nov. 14, 2011; 23 pages. [cited by applicant]
Final Office Action dated Jun. 20, 2016; U.S. Appl. No. 13/295,404, filed Nov. 14, 2011; 18 pages. [cited by applicant]
Advisory Action dated Sep. 19, 2016; U.S. Appl. No. 13/295,404, filed Nov. 14, 2011; 4 pages. [cited by applicant]
Office Action dated Oct. 21, 2016; U.S. Appl. No. 13/295,404, filed Nov. 14, 2011; 16 pages. [cited by applicant]
Final Office Action dated May 18, 2017; U.S. Appl. No. 13/295,404, filed Nov. 14, 2011; 16 pages. [cited by applicant]
Advisory Action dated Aug. 10, 2017; U.S. Appl. No. 13/295,404, filed Nov. 14, 2011; 5 pages. [cited by applicant]
Office Action dated Dec. 21, 2017; U.S. Appl. No. 13/295,404, filed Nov. 14, 2011; 16 pages. [cited by applicant]
Final Office Action dated Jul. 13, 2018; U.S. Appl. No. 13/295,404, filed Nov. 14, 2011; 19 pages. [cited by applicant]
Advisory Action dated Oct. 2, 2018; U.S. Appl. No. 13/295,404, filed Nov. 14, 2011; 4 pages. [cited by applicant]
Office Action dated Dec. 13, 2018; U.S. Appl. No. 13/295,404, filed Nov. 14, 2011; 18 pages. [cited by applicant]
Office Action dated Jun. 17, 2019; U.S. Appl. No. 13/295,404, filed Nov. 14, 2011; 18 pages. [cited by applicant]
Final Office Action dated Dec. 30, 2019; U.S. Appl. No. 13/295,404, filed Nov. 14, 2011; 23 pages. [cited by applicant]
European Extended Search Report; Application No. 11189060.4; Apr. 11, 2012; 7 pages. [cited by applicant]
PCT International Search Report & Written Opinion of the International Searching Authority; PCT/CA2011/050702; Aug. 3, 2012; 6 pages. [cited by applicant]
European Extended Search Report; Application No. 12156348.0; Jul. 20, 2012; 9 pages. [cited by applicant]
European Examination Report; Application No. 12156348.0; Jan. 26, 2016; 6 pages. [cited by applicant]
European Examination Report; Application No. 12156348.0; Aug. 23, 2017; 8 pages. [cited by applicant]
Canadian Office Action; Application No. 2,806,906; Sep. 4, 2014; 5 pages. [cited by applicant]
Canadian Office Action; Application No. 2,806,906; Jan. 12, 2016; 7 pages. [cited by applicant]
Canadian Office Action; Application No. 2,806,906; Jan. 6, 2017; 8 pages. [cited by applicant]
Canadian Office Action; Application No. 2,806,906; Feb. 9, 2018; 11 pages. [cited by applicant]