IP Library › Granted Patent US 10,733,040
Granted Patent B2
US 10,733,040 · App. 15/886,214 · Granted Aug 4, 2020

Individual bug fixed messages for software users

Inventor: Daniel Flohr (Stuttgart, DE)
Assignee: FARO TECHNOLOGIES, INC.
G06F11/079G06F8/65G06F11/0709G06F11/0766G06F11/0778G06F11/0787G06F11/366G06F11/0793
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 10,733,040
App. No.
15/886,214
Granted
Aug 4, 2020
Kind
B2
Abstract

Individual bug fixed messages for software users that includes determining an occurrence of an error in software executing on a user processor. A unique error report identifier is stored in a memory accessible by the user processor and the error is reported. The reporting includes transmitting the unique error report identifier and error data that describes the error to a developer server. The error data is analyzed to determine a fix to correct the error. A message regarding the fix to correct the error is stored in a fixed error database. The software is launched and it is determined that the error was previously reported. The fixed error database is queried by the software with the unique error report identifier to locate the message. Based on locating the message, the message is downloaded and displayed by the user processor.

Claims (34)

1. A method for reporting errors in software, the method comprising:

determining an occurrence of an error in software executing on a user processor;

storing, in a memory accessible by the user processor, a unique error report identifier;

reporting the error, the reporting comprising transmitting the unique error report identifier and error data that describes the error to a developer server, wherein the unique error report identifier is a session identifier of a session between the user processor and the developer server at the time that the error occurred;

analyzing the error data to determine a fix to correct the error;

storing a message regarding the fix to correct the error and the unique error report identifier in a fixed error database;

launching the software and determining that the error was previously reported;

querying, by the software, the fixed error database with the unique error report identifier to locate the message; and

based on locating the message, downloading and displaying the message on the user processor, the downloading and displaying performed by the user processor.

2. The method of claim 1 , wherein the error data is anonymized to remove data that identifies a user reporting the error.

3. The method of claim 1 , wherein the fix is a software update and the method further comprises, based on locating the message, downloading and installing the software update at the user processor.

4. The method of claim 1 , wherein the determining that the error was previously reported comprises locating the unique error report identifier in the memory accessible by the user processor.

5. The method of claim 1 , wherein the error data includes a recorded state of the working memory of the user processor at the time that the error occurred.

6. The method of claim 1 , wherein the software is scan processing software and the user processor is located on a laser scanner.

7. A method for reporting errors in software, the method comprising:

determining an occurrence of an error in software executing on a user processor;

storing, in a memory accessible by the user processor, a unique error report identifier;

reporting the error, the reporting comprising transmitting the unique error report identifier and error data that describes the error to a developer server, wherein the error data is anonymized to remove data that identifies a user reporting the error;

launching the software and determining that the error was previously reported;

querying, by the software, a fixed error database with the unique error report identifier to locate a message regarding a fix to correct the error; and

based on locating the message, downloading and displaying the message on the user processor, the downloading and displaying performed by the user processor.

8. The method of claim 7 , wherein the unique error report identifier is a session identifier of a session between the user processor and the developer server at the time that the error occurred.

9. The method of claim 7 , wherein the fix is a software update and the method further comprises, based on locating the message, downloading and installing the software update at the user processor.

10. The method of claim 7 , wherein the determining that the error was previously reported comprises locating the unique error report identifier in the memory accessible by the user processor.

11. The method of claim 7 , wherein the error data includes a recorded state of the working memory of the user processor at the time that the error occurred.

12. The method of claim 7 , wherein the software is scan processing software and the user processor is located on a laser scanner.

13. A method for reporting errors in software, the method comprising:

receiving an error report at a developer server, the receiving from a user processor executing software, the error report comprising a unique error report identifier and error data that describes an error in the software;

analyzing the error data to determine a fix to correct the error; and

storing a message regarding the fix to correct the error and the unique error report identifier in a fixed error database, the message accessible by the user processor in response to a query from the user processor that specifies the unique error report identifier, wherein the fix is a software update and the message describes how to download and install the software update at the user processor.

14. The method of claim 13 , wherein the unique error report identifier is a session identifier of a session between the user processor and the developer server at the time that the error occurred.

15. The method of claim 13 , wherein the error data is anonymized to remove data that identifies a user reporting the error.

16. The method of claim 13 , wherein the error data includes a recorded state of the working memory of the user processor at the time that the error occurred.

17. The method of claim 13 , wherein the software is scan processing software and the user processor is located on a laser scanner.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 1, 2018
From: FLOHR, DANIEL
To: FARO TECHNOLOGIES, INC.
Reel/Frame 044801/0094 →
Continuity (1)
Related Publication 20190235942A1 · Aug 1, 2019