IP Library Granted Patent US 11,310,289
Granted Patent B2
US 11,310,289 · App. 16/011,246 · Granted Apr 19, 2022

Systems and methods for generating a shortcut associated with a rich communication services messaging session

Inventors: Lodema M. Steinbach (Clayton, CA); Sethumadhav Bendi (Walnut Creek, CA)
Assignee: Verizon Patent and Licensing Inc.
H04L65/1066G06F40/134H04L65/1006H04L69/24H04L67/02
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 11,310,289
App. No.
16/011,246
Granted
Apr 19, 2022
Kind
B2
Abstract

A user device may receive an instruction to generate a shortcut associated with a rich communication services (RCS) messaging session that is associated with a RCS application. The user device may generate, based on receiving the instruction, a snapshot of the RCS messaging session, and may transmit, based on generating the snapshot of the RCS messaging session, the snapshot of the RCS messaging session to an application server. The user device may generate, based on transmitting the snapshot of the RCS messaging session to the application server, the shortcut associated with the RCS messaging session, where the shortcut associated with the RCS messaging session is linked to the snapshot of the RCS messaging session. The user device may display, on a display of the device, the shortcut associated with the RCS messaging session.

Claims (144)

1. A device, comprising:

one or more memories; and

one or more processors, communicatively coupled to the one or more memories, to:

receive, at the device, an instruction to generate a shortcut associated with a rich communication services (RCS) messaging session,

wherein the RCS messaging session is associated with a RCS application;

generate, at the device, based on receiving the instruction, a snapshot of the RCS messaging session,

wherein the snapshot is associated with a position within the RCS messaging session at a point in time;

transmit, by the device, based on generating the snapshot of the RCS messaging session, the snapshot of the RCS messaging session to an application server;

receive, after generating the snapshot of the RCS messaging session, additional information associated with the RCS messaging session;

transmit, to the application server and based on receiving the additional information, the additional information and an instruction to store the additional information in the snapshot of the RCS messaging session;

generate, at the device, based on transmitting the snapshot of the RCS messaging session to the application server, the shortcut associated with the RCS messaging session,

wherein the shortcut associated with the RCS messaging session is linked to the snapshot of the RCS messaging session, and

wherein the shortcut associated with the RCS messaging session allows access to the snapshot of the RCS messaging session to resume the RCS messaging session from the snapshot of the RCS messaging session, and

wherein resuming the RCS messaging session from the snapshot of the RCS messaging session comprises:

 launching the RCS application, and

 displaying, in the RCS messaging session, information included in the snapshot of the RCS messaging session when the snapshot of the RCS messaging session was generated at the position within the RCS messaging session at the point in time prior to subsequent information being displayed in the RCS messaging session; and

display, on a home screen or lock screen of a display of the device, the shortcut associated with the RCS messaging session.

2. The device of claim 1 , wherein the snapshot of the RCS messaging session includes at least one of:

information identifying one or more messages included in the RCS messaging session,

information identifying a time stamp associated with the one or more messages, or

information identifying one or more attachments included in the RCS messaging session.

3. The device of claim 1 , wherein the shortcut associated with the RCS messaging session includes at least one of:

a notification displayed on the device,

an icon displayed on the device, or

a hyperlink displayed on the device.

4. The device of claim 1 , wherein the one or more processors are further to:

receive an input associated with a user interaction with the shortcut associated with the RCS messaging session;

obtain, based on receiving the input, the snapshot of the RCS messaging session from the application server; and

display the snapshot of the RCS messaging session in the RCS application on the device.

5. The device of claim 1 , wherein the additional information associated with the RCS messaging session includes at least one of:

information identifying one or more messages that were transmitted in the RCS messaging session after the snapshot of the RCS messaging session was generated,

information identifying a time stamp associated with the one or more messages that were transmitted in the RCS messaging session after the snapshot of the RCS messaging session was generated, or

information identifying one or more additional attachments that were transmitted in the RCS messaging session after the snapshot of the RCS messaging session was generated.

6. The device of claim 1 , wherein the one or more processors are further to:

receive other additional information associated with the RCS messaging session;

receive another instruction to generate another shortcut associated with the RCS messaging session;

generate, based on receiving the other instruction, an updated snapshot of the RCS messaging session,

wherein the updated snapshot of the RCS messaging session includes:

information included in the snapshot of the RCS messaging session, and

the other additional information associated with the RCS messaging session;

transmit, based on generating the updated snapshot of the RCS messaging session, the updated snapshot of the RCS messaging session to the application server associated with the RCS application; and

link, based on transmitting the snapshot of the RCS messaging session to the application server, the shortcut associated with the RCS messaging session to the updated snapshot of the RCS messaging session.

7. The device of claim 1 , wherein the one or more processors are further to:

receive another instruction to generate another shortcut associated with the RCS messaging session; and

generate, based on receiving the other instruction, an updated snapshot of the RCS messaging session,

wherein the updated snapshot of the RCS messaging session includes:

information included in the snapshot of the RCS messaging session, and

the additional information associated with the RCS messaging session.

8. A non-transitory computer-readable medium storing instructions, the instructions comprising:

one or more instructions that, when executed by one or more processors of a device, cause the one or more processors to:

receive, at the device, an instruction to generate a shortcut associated with a rich communication services (RCS) messaging session,

wherein the RCS messaging session is associated with a RCS application, and

wherein the RCS messaging session is associated with a user and a chatbot;

generate, at the device and based on receiving the instruction, a snapshot of the RCS messaging session,

wherein the snapshot is associated with a position within the RCS messaging session at a point in time;

transmit, by the device and based on generating the snapshot of the RCS messaging session, the snapshot of the RCS messaging session to an application server;

receive, after generating the snapshot of the RCS messaging session, additional information associated with the RCS messaging session;

transmit, to the application server and based on receiving the additional information, the additional information and an instruction to store the additional information in the snapshot of the RCS messaging session;

generate, at the device and based on transmitting the snapshot of the RCS messaging session to the application server, the shortcut associated with the RCS messaging session,

wherein the shortcut associated with the RCS messaging session is linked to the snapshot of the RCS messaging session, and

wherein the shortcut associated with the RCS messaging session allows access to the snapshot of the RCS messaging session to resume the RCS messaging session from the snapshot of the RCS messaging session, and

wherein the one or more processors, when resuming the RCS messaging session from the snapshot of the RCS messaging session, are to:

 launch the RCS application, and

 display, in the RCS messaging session, information included in the snapshot of the RCS messaging session when the snapshot of the RCS messaging session was generated at the position within the RCS messaging session at the point in time prior to subsequent information being displayed in the RCS messaging session; and

display, on a home screen or lock screen of a display of the device, the shortcut associated with the RCS messaging session.

9. The non-transitory computer-readable medium of claim 8 , wherein the snapshot of the RCS messaging session includes at least one of:

information identifying a message included in the RCS messaging session,

information identifying a time stamp associated with the message,

information identifying an attachment included in the RCS messaging session, or

information identifying an image included in the RCS messaging session.

10. The non-transitory computer-readable medium of claim 8 , wherein the shortcut associated with the RCS messaging session includes at least one of:

an icon displayed on the home screen of the device, or

a hyperlink displayed on the home screen of the device.

11. The non-transitory computer-readable medium of claim 8 , wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:

receive, after generating the snapshot of the RCS messaging session, other additional information associated with the RCS messaging session,

wherein the other additional information associated with the RCS messaging session is received while the RCS messaging session is idle; and

based on receiving the other additional information:

transmit, to the application server, the other additional information and an instruction to store the other additional information in the snapshot of the RCS messaging session.

12. The non-transitory computer-readable medium of claim 8 , wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:

receive an input associated with a user interaction with the shortcut associated with the RCS messaging session;

obtain, based on receiving the input, the snapshot of the RCS messaging session from the application server; and

display, on the display of the device, the snapshot of the RCS messaging session in the RCS application.

13. The non-transitory computer-readable medium of claim 8 , wherein the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:

receive other additional information associated with the RCS messaging session;

receive another instruction to generate another shortcut associated with the RCS messaging session;

generate, based on receiving the other instruction, an updated snapshot of the RCS messaging session,

wherein the updated snapshot of the RCS messaging session includes:

information included in the snapshot of the RCS messaging session, and

the other additional information associated with the RCS messaging session;

transmit, based on generating the updated snapshot of the RCS messaging session, the updated snapshot of the RCS messaging session to the application server associated with the RCS application; and

link, based on transmitting the snapshot of the RCS messaging session to the application server, the shortcut associated with the RCS messaging session to the updated snapshot of the RCS messaging session.

14. The non-transitory computer-readable medium of claim 13 , wherein the other additional information associated with the RCS messaging session includes at least one of:

information identifying an additional message that transmitted in the RCS messaging session after the snapshot of the RCS messaging session was generated,

information identifying an additional time stamp associated with the additional message,

information identifying an additional attachment that transmitted in the RCS messaging session after the snapshot of the RCS messaging session was generated, or

information identifying an additional image that transmitted in the RCS messaging session after the snapshot of the RCS messaging session was generated.

15. A method, comprising:

receiving, at a device, an instruction to generate a shortcut associated with a rich communication services (RCS) messaging session,

wherein the RCS messaging session is associated with a RCS application,

wherein the RCS messaging session is further associated with another application included on the device, and

wherein the RCS messaging session is associated with a user and a chatbot;

generating, by the device and based on receiving the instruction, a snapshot of the RCS messaging session,

wherein the snapshot is associated with a position within the RCS messaging session at a point in time;

transmitting, by the device and based on generating the snapshot of the RCS messaging session, the snapshot of the RCS messaging session to an application server;

receiving, by the device and after generating the snapshot of the RCS messaging session, additional information associated with the RCS messaging session;

transmit, by the device, to the application server, and based on receiving the additional information, the additional information and an instruction to store the additional information in the snapshot of the RCS messaging session;

generating, by the device and based on transmitting the snapshot of the RCS messaging session to the application server, the shortcut associated with the RCS messaging session,

wherein the shortcut associated with the RCS messaging session is linked to the snapshot of the RCS messaging session, and

wherein the shortcut associated with the RCS messaging session allows access to the snapshot of the RCS messaging session to resume the RCS messaging session from the snapshot of the RCS messaging session, and

wherein the instructions, that cause the one or more processors to resume the RCS messaging session from the snapshot of the RCS messaging session, cause the one or more processors to:

launch the RCS application, and

display, in the RCS messaging session, information included in the snapshot of the RCS messaging session when the snapshot of the RCS messaging session was generated at the position within the RCS messaging session at the point in time prior to subsequent information being displayed in the RCS messaging session; and

displaying, on a home screen or lock screen of a display of the device, the shortcut associated with the RCS messaging session.

16. The method of claim 15 , wherein the snapshot of the RCS messaging session includes at least one of:

information identifying a message included in the RCS messaging session,

information identifying a time stamp associated with the message,

information identifying an attachment included in the RCS messaging session,

information identifying an image included in the RCS messaging session,

information identifying the user,

information identifying the chatbot, or

information identifying the other application included on the device.

17. The method of claim 15 , wherein the shortcut associated with the RCS messaging session includes at least one of:

an icon displayed on the home screen of the device,

a hyperlink displayed on the home screen of the device, or

a notification displayed on the lock screen of the device.

18. The method of claim 15 , further comprising:

receiving, after generating the snapshot of the RCS messaging session, other additional information associated with the RCS messaging session,

wherein the other additional information associated with the RCS messaging session is received while the RCS messaging session is idle; and

based on receiving the additional information:

transmitting, to the application server, the other additional information and an instruction to store the other additional information in the snapshot of the RCS messaging session, and

displaying, on the display of the device, a notification associated with the other additional information.

19. The method of claim 15 , further comprising:

receiving an input associated with a user interaction with the shortcut associated with the RCS messaging session;

obtaining, based on receiving the input, the snapshot of the RCS messaging session from the application server; and

displaying, on the display of the device, the snapshot of the RCS messaging session in the RCS application.

20. The method of claim 15 , further comprising:

receiving, while the RCS messaging session is active, other additional information associated with the RCS messaging session;

receiving another instruction to generate another shortcut associated with the RCS messaging session,

generating, based on receiving the other instruction, an updated snapshot of the RCS messaging session,

wherein the updated snapshot of the RCS messaging session includes:

information included in the snapshot of the RCS messaging session, and

the other additional information associated with the RCS messaging session;

transmitting, based on generating the updated snapshot of the RCS messaging session, the updated snapshot of the RCS messaging session to the application server associated with the RCS application; and

linking, based on transmitting the snapshot of the RCS messaging session to the application server, the shortcut associated with the RCS messaging session to the updated snapshot of the RCS messaging session.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 18, 2018
From: STEINBACH, LODEMA M.; BENDI, SETHUMADHAV
To: VERIZON PATENT AND LICENSING INC.
Reel/Frame 046122/0242 →
Continuity (1)
Related Publication 20190387031A1 · Dec 19, 2019
Cited By (1)
US 12,470,612