IP Library Granted Patent US 12,150,025
Granted Patent B2
US 12,150,025 · App. 18/312,261 · Granted Nov 19, 2024

System, method, apparatus, and computer program product for providing mobile device support services

Inventors: Cameron Hurst (Asheville, NC); Stuart Saunders (Lakewood, OH)
Assignee: Assurant, Inc.
H04W4/50G06F11/0742G06F11/0748G06F11/0793G06F11/2294G06F21/577H04L67/303H04W4/60G06F2221/2143H04W84/12
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,150,025
App. No.
18/312,261
Granted
Nov 19, 2024
Kind
B2
Abstract

A method is provided for providing mobile device support services. The method may include monitoring a mobile device status. The method may additionally include performing device diagnostics based at least in part on captured device status data to identify potential faults that may affect mobile device functionality. A corresponding system, apparatus, and computer program product are also provided.

Claims (47)

1. A method comprising:

receiving device status data from one or more mobile devices;

causing rendering of a portal interface on a screen of a user device, wherein the portal interface comprises information associated with a fault predicted for the one or more mobile devices, the fault comprising a fault with (i) at least one application installed on the one or more mobile devices or (ii) at least one hardware component of the one or more mobile devices;

receiving, via the portal interface, an indication of a selection by a user; and

transmitting computer executable instructions configured to automatically modify, via the portal interface and based on the selection, at least one configuration associated with the one or more mobile devices, wherein modifying the at least one configuration is configured to resolve the fault predicted for the one or more mobile devices.

2. The method according to claim 1 , further comprising:

maintaining a log of device events experienced by the one or more mobile devices; and

causing rendering of a user interface comprising of the log of device events.

3. The method according to claim 1 , further comprising:

causing rendering of a user interface comprising (i) the at least one application installed on the one or more mobile devices and (ii) a status message associated with each of the at least one application rendered via the user interface.

4. The method according to claim 1 , further comprising:

detecting data identifying at least a particular device of the one or more mobile devices; and

causing rendering of a support user interface comprising viewable content associated with at least the particular device.

5. The method according to claim 1 , further comprising:

causing rendering of a user interface comprising a text input form that enables input of text messages utilized to identify text instructions corresponding to a solution based at least in part on the text messages.

6. The method according to claim 1 , further comprising:

causing rendering of at least one alert associated with the one or more mobile devices, the at least one alert associated with (i) the at least one application installed on the one or more mobile devices or (ii) the at least one hardware component of the one or more mobile devices.

7. The method according to claim 6 , wherein the at least one alert comprises a list of high risk applications installed on the one or more mobile devices.

8. The method according to claim 6 , wherein the at least one alert comprises a list of incompatible applications installed to the one or more mobile devices.

9. The method according to claim 6 , wherein the at least one alert comprises a list of hardware faults associated with the at least one hardware component of the one or more mobile devices.

10. The method according to claim 6 , further comprising:

causing the one or more mobile devices to run at least one diagnostic process; and

receiving the device status data in response to the at least one diagnostic process,

wherein the at least one alert is generated based at least in part on the device status data.

11. A system comprising at least one processor and at least one non-transitory memory having computer-coded instructions stored thereon that, in execution with the at least one processor, causes the system to:

receive device status data from one or more mobile devices;

cause rendering of a portal interface on a screen of a user device, wherein the portal interface comprises information associated with a fault predicted for the one or more mobile devices, the fault comprising a fault with (i) at least one application installed on the one or more mobile devices or (ii) at least one hardware component of the one or more mobile devices;

receive, via the portal interface, an indication of a selection by a user; and

transmit computer executable instructions configured to automatically modify, via the portal interface and based on the selection, at least one configuration associated with the one or more mobile devices, wherein modifying the at least one configuration is configured to resolve the fault predicted for the one or more mobile devices.

12. The system according to claim 11 , further caused to:

maintain a log of device events experienced by the one or more mobile devices; and

cause rendering of a user interface comprising of the log of device events.

13. The system according to claim 11 , further caused to:

cause rendering of a user interface comprising (i) the at least one application installed on the one or more mobile devices and (ii) a status message associated with each of the at least one application rendered via the user interface.

14. The system according to claim 11 , further caused to:

detect data identifying at least a particular device of the one or more mobile devices; and

cause rendering of a support user interface comprising viewable content associated with at least the particular device.

15. The system according to claim 11 , further caused to:

cause rendering of a user interface comprising a text input form that enables input of text messages utilized to identify text instructions corresponding to a solution based at least in part on the text messages.

16. The system according to claim 11 , further caused to:

cause rendering of at least one alert associated with the one or more mobile devices, the at least one alert associated with (i) the at least one application installed on the one or more mobile devices or (ii) the at least one hardware component of the one or more mobile devices.

17. The system according to claim 16 , wherein the at least one alert comprises a list of high risk applications installed on the one or more mobile devices.

18. The system according to claim 16 , wherein the at least one alert comprises a list of incompatible applications installed to the one or more mobile devices.

19. The system according to claim 16 , wherein the at least one alert comprises a list of hardware faults associated with the at least one hardware component of the one or more mobile devices.

20. The system according to claim 16 , further caused to:

cause the one or more mobile devices to run at least one diagnostic process; and

receive the device status data in response to the at least one diagnostic process, wherein the at least one alert is generated based at least in part on the device status data.

Assignments (4)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 5, 2023
From: HURST, CAMERON
To: ASSURANT, INC.
Reel/Frame 063546/0420 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 5, 2023
From: SAUNDERS, STUART
To: MOBILE DEFENSE, INC.
Reel/Frame 063546/0457 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 5, 2023
From: MOBILE DEFENSE, INC.
To: TS HOLDINGS, INC.
Reel/Frame 063546/0529 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 5, 2023
From: TS HOLDINGS, INC.
To: ASSURANT, INC.
Reel/Frame 063546/0565 →
Continuity (6)
Continuation 17248337 · Jan 21, 2021
Continuation 16448583 · Jun 21, 2019
Continuation 15272261 · Sep 21, 2016
Continuation 13841306 · Mar 15, 2013
Provisional Application 61620795 · Apr 5, 2012
Related Publication 20230319532A1 · Oct 5, 2023