Targeted crash fixing on a client device

• US 10,198,304 B2
• Filed: 11/04/2014
• Issued: 02/05/2019
• Est. Priority Date: 11/04/2014
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Oath Inc. (Verizon Communications Inc.)
• Inventors: Rossbacher, Andreas, Coe, Brian, Herron, Jon, Hanuska, Alex
• Primary Examiner(s): Mehrmanesh, Elmira
• Application Number:
  US14/532,450
• Publication Number:
  US 20160124799A1
• Time in Patent Office: 1,554 Days
• Field of Search: 714 3814
• CPC Class Codes: G06F 11/0709 in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
• CPC Class Codes: G06F 11/0742 in a data processing system embedded in a mobile device, e.g. mobile phones, handheld devices
• CPC Class Codes: G06F 11/0793 Remedial or corrective actions recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

Client devices having deployed an application may experience a crash of the application. For example, a first client device may experience a first crash having a first crash signature of the application. After experiencing the first crash, a first device identification of the first client device may be assigned to a first bucket designating one or more device identifications of client devices having experienced the first crash. Client devices having device identifications in the first bucket are provided with a first crash fix for the first crash, while a second client device is not provide with the first crash fix, where the application is deployed on the second client device and the second client device was not assigned to the first bucket.

Claims

1. A method of targeted crash fixing, comprising:

identifying a group of users that have deployed an application on client devices, the group of users comprising a first user having a first client device and a second user having a second client device;

receiving a first device identification from the first client device, the first device identification comprising a first crash signature indicating that the application experienced a first crash on the first client device;

assigning the first device identification to a first bucket designating one or more device identifications of client devices having experienced the first crash;

responsive to determining that an updated version of the application and a first crash fix for the first crash are both available, determining whether the first crash fix is integrated into the updated version of the application;

responsive to determining that the first crash fix is not integrated into the updated version of the application, providing at a first time the first crash fix but not the updated version of the application to client devices identified by the one or more device identifications of the first bucket but not to client devices, upon which the application is deployed, that are not identified by the one or more device identifications of the first bucket, the first crash fix provided to the first client device but not the second client device;

receiving, via a network connection, a crash confirmation fix from the first client device;

responsive to determining that the crash confirmation fix indicates that the first crash fix resolved the first crash on the first client device, removing the first device identification, associated with the first client device, from the first bucket;

receiving a third device identification from a third client device, the third device identification comprising a third crash signature indicating that a third application experienced a third crash on the third client device;

assigning the third device identification to a third bucket designating one or more device identifications of client devices having experienced the third crash;

responsive to determining that an updated version of the third application and a third crash fix for the third crash are both available, determining whether the third crash fix is integrated into the updated version of the third application; and

responsive to determining that the third crash fix is integrated into the updated version of the third application, providing the updated version of the third application but not the third crash fix to client devices identified by the one or more device identifications of the third bucket but not to client devices, upon which the third application is deployed, that are not identified by the one or more device identifications of the third bucket, the third crash fix provided to the third client device.

2. The method of claim 1, wherein the application is different than the third application.

3. The method of claim 1, comprising:

providing the first crash fix to a fourth client device identified by a fourth device identification of the first bucket; and

responsive to the first crash fix not resolving the first crash for the fourth client device;

retaining the assignment of the fourth third device identification to the first bucket;

generating a second crash fix to address the first crash; and

providing the second crash fix to the fourth client device.

4. The method of claim 1, comprising:

providing the first crash fix to a fourth client device identified by a fourth device identification of the first bucket; and

responsive to the first crash fix not being received by the fourth client device;

retaining the assignment of the fourth device identification to the first bucket; and

providing the first crash fix to the fourth client device.

5. The method of claim 1, comprising:

receiving a third crash confirmation fix from the client device; and

responsive to determining that the third crash confirmation fix indicates that the updated version of the third application resolved the third crash on the client device, removing the device identification, associated with the first client device, from the third bucket.

6. The method of claim 1, comprising:

responsive to a second device identification of the second client device not being assigned to the first bucket, marking the first crash fix as not being applicable to the second client device.

7. The method of claim 1, comprising:

receiving a fourth device identification from a fourth client device, the fourth device identification comprising a fourth crash signature indicating that a fourth application experienced a fourth crash on the fourth client device;

assigning the fourth device identification to a fourth bucket designating one or more device identifications of client devices having experienced the fourth crash;

responsive to determining that an updated version of the fourth application and a fourth crash fix for the fourth crash are both available, determining whether the fourth crash fix is integrated into the updated version of the fourth application; and

responsive to determining that the fourth crash fix is not integrated into the updated version of the fourth application, providing the fourth crash fix to client devices identified by the one or more device identifications of the fourth bucket but not to client devices, upon which the fourth application is deployed, that are not identified by the one or more device identifications of the fourth bucket, the fourth crash fix provided to the fourth client device.

8. The method of claim 1, comprising:

receiving the first device identification from the first client device, the first device identification comprising a second crash signature indicating that the application experienced a second crash on the first client device; and

assigning the first device identification to a second bucket designating one or more device identifications of client devices having experienced the second crash.

9. The method of claim 8, comprising:

receiving a second device identification from the second client device, the second device identification comprising the second crash signature indicating that the application experienced the second crash on the second client device; and

assigning the second device identification to the second bucket.

10. The method of claim 9, comprising:

creating a second crash fix to address the second crash;

sending the second crash fix to the first client device and to the second client device; and

removing the first device identification and the second device identification from the second bucket.

11. A system for targeted crash fixing, comprising:

a processor; and

memory comprising processor-executable instructions that when executed by the processor cause implementation of a crash management component configured to;

receive a first device identification from a first user having a first client device, the first device identification comprising a first crash signature indicating that an application experienced a first crash on the first client device;

assign the first device identification to a first bucket designating one or more device identifications of client devices having experienced the first crash;

responsive to determining that an updated version of the application and a first crash fix for the first crash are both available, determine whether the first crash fix is integrated into the updated version of the application;

responsive to determining that the first crash fix is not integrated into the updated version of the application, provide the first crash fix to client devices assigned to the first bucket but not to client devices, upon which the application is deployed, that are not assigned to the first bucket, the first crash fix provided to the first client device but not a second client device, where the application is deployed on the second client device and the second client device was not assigned to the first bucket;

receive, via a network connection, a crash confirmation fix from the first client device;

responsive to determining that the crash confirmation fix indicates that the first crash fix resolved the first crash on the first client device, remove the first device identification, associated with the first client device, from the first bucket;

receive a device identification from a client device, the device identification comprising a third crash signature indicating that a third application experienced a third crash on the client device;

assign the device identification to a third bucket designating one or more device identifications of client devices having experienced the third crash;

responsive to determining that an updated version of the third application and a third crash fix for the third crash are both available, determine whether the third crash fix is integrated into the updated version of the third application; and

responsive to determining that the third crash fix is integrated into the updated version of the third application, provide the updated version of the third application to client devices identified by the one or more device identifications of the third bucket but not to client devices, upon which the third application is deployed, that are not identified by the one or more device identifications of the third bucket, the third crash fix provided to the client device.

12. The system of claim 11, the crash management component configured to:

provide the first crash fix to a fourth client device identified by a fourth device identification of the first bucket; and

responsive to the first crash fix not resolving the first crash for the fourth client device;

retain the assignment of the fourth device identification to the first bucket;

generate a second crash fix to address the first crash; and

provide the second crash fix to the fourth client device.

13. The system of claim 11, the crash management component configured to:

receive a third crash confirmation fix from the client device; and

responsive to determining that the third crash confirmation fix indicates that the updated version of the third application resolved the third crash on the client device, remove the device identification, associated with the first client device, from the third bucket.

14. The system of claim 11, wherein the application is different than the third application.

15. The system of claim 11, the crash management component configured to:

receive the first device identification from the first client device, the first device identification comprising a second crash signature indicating that the application experienced a second crash on the first client device; and

assign the first device identification to a second bucket designating one or more device identifications of devices having experienced the second crash.

16. The system of claim 15, the crash management component configured to:

receive a second device identification from the second client device, the second device identification comprising the second crash signature indicating that the application experienced the second crash on the second client device; and

assign the second device identification to the second bucket.

17. The system of claim 16, the crash management component configured to:

create a second crash fix to address the second crash.

18. The system of claim 17, the crash management component configured to:

send the second crash fix to the first client device and to the second client device; and

remove the first device identification and the second device identification from the second bucket.

19. A non-transitory computer readable medium comprising computer executable instructions that when executed by a processor perform a method for maintaining buckets for targeted crash fixing, comprising:

maintaining a first bucket for a first crash of an application, the first crash having a first crash signature;

maintaining a second bucket for a second crash of the application, the second crash having a second crash signature;

responsive to receiving a first crash notification, corresponding to the first crash, from a first client device, assigning a first device identification of the first client device to the first bucket;

responsive to receiving a second crash notification, corresponding to the second crash, from a second client device, assigning a second device identification of the second client device to the second bucket;

responsive to determining that an updated version of the application and a first crash fix for client devices assigned to the first bucket are both available, determining whether the first crash fix is integrated into the updated version of the application;

generating second crash fix for client devices assigned to the second bucket;

responsive to determining that the first crash fix is integrated into the updated version of the application, providing the updated version of the application but not the first crash fix to the first client device based upon the first client device being assigned to the first bucket but not to client devices, upon which the application is deployed, that are not assigned to the first bucket;

providing the second crash fix to the second client device based upon the second client device being assigned to the second bucket but not to client devices, upon which the application is deployed, that are not assigned to the second bucket;

receiving, via a network connection, a crash confirmation fix from the first client device;

responsive to determining that the crash confirmation fix indicates that the updated version of the application resolved the first crash on the first client device, removing the first device identification, associated with the first client device, from the first bucket;

receiving, via a second network connection, a second crash confirmation fix from the second client device;

responsive to determining that the second crash confirmation fix indicates that the second crash fix resolved the second crash on the second client device, removing the second device identification, associated with the second client device, from the second bucket;

receiving a third device identification from a third client device, the third device identification comprising a third crash signature indicating that a third application experienced a third crash on the third client device;

assigning the third device identification to a third bucket designating one or more device identifications of client devices having experienced the third crash;

responsive to determining that an updated version of the third application and a third crash fix for the third crash are both available, determining whether the third crash fix is integrated into the updated version of the third application; and

responsive to determining that the third crash fix is not integrated into the updated version of the third application, providing the third crash fix to client devices identified by the one or more device identifications of the third bucket but not to client devices, upon which the third application is deployed, that are not identified by the one or more device identifications of the third bucket, the third crash fix provided to the third client device.

20. The computer readable medium of claim 19, comprising:

receiving a fourth device identification from a fourth client device, the fourth device identification comprising a fourth crash signature indicating that a fourth application experienced a fourth crash on the fourth client device;

assigning the fourth device identification to a fourth bucket designating one or more device identifications of client devices having experienced the fourth crash;

responsive to determining that an updated version of the fourth application and a fourth crash fix for the fourth crash are both available, determining whether the fourth crash fix is integrated into the updated version of the fourth application; and

responsive to determining that the fourth crash fix is integrated into the updated version of the fourth application, providing the updated version of the fourth application to client devices identified by the one or more device identifications of the fourth bucket but not to client devices, upon which the fourth application is deployed, that are not identified by the one or more device identifications of the fourth bucket, the fourth crash fix provided to the fourth client device.