IP Library Granted Patent US 8,874,967
Granted Patent B2
US 8,874,967 · App. 13/436,298 · Granted Oct 28, 2014

Managing code-tracing data

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 8,874,967
App. No.
13/436,298
Granted
Oct 28, 2014
Kind
B2
Abstract

A method of managing code-tracing data is described. The method comprises the steps of: analyzing a log of code-tracing data to identify a module in which an error occurred; activating code-tracing at a high detail level in that module; identifying modules associated with that module; and activating code-tracing at a high detail level in those identified modules.

Claims (37)

1. A method of managing code-tracing data, the method comprising the steps of:

analyzing a log of code-tracing data to identify a module in which an error occurred based on a category associated with the error, the category identifying data types in the code-tracing data;

activating code-tracing at a high detail level in that module;

identifying modules associated with that module;

activating code-tracing at a high detail level in those identified modules; and

sending a message to a remote management center when the error occurred within a predefined set period of time since a last error.

2. A method according to claim 1 , wherein the module in which an error occurred comprises a service in a control application.

3. A method according to claim 2 , wherein the identified modules comprise service providers associated with the service.

4. A method according to claim 3 , wherein the service providers comprise CEN XFS modules.

5. A method according to claim 1 , wherein the method includes the further steps of:

creating a code-tracing profile to include high detail level code-tracing for the module in which the error occurred; and

associating a defect type with this profile.

6. A method according to claim 1 , wherein the method comprises the further steps of:

detecting a pattern of errors over a period of time; and

applying a code-tracing profile appropriate for the detected pattern.

7. A method according to claim 1 , wherein the method comprises the further steps of:

detecting the absence of an error over a defined time period; and

reducing the code-tracing detail level.

8. A system for managing code-tracing data, the system comprising:

a trace manager arranged to

(i) analyze a log of code-tracing data to identify a module in which an error occurred based on a category associated with the error, the category identifying data types in the code-tracing data;

(ii) activate code-tracing at a high detail level in that module;

(iii) identify modules associated with that module;

(iv) activate code-tracing at a high detail level in those identified modules; and

(v) send a message to a remote management center when the error occurred within a predefined set period of time since a last error.

9. A system according to claim 8 , wherein the trace manager comprises a software component.

10. A system according to claim 9 , wherein the trace manager is further arranged to:

create a code-tracing profile to include high detail level code-tracing for the module in which the error occurred; and

associate a defect type with this profile.

11. A system according to claim 9 , wherein the trace manager is further arranged to:

detect a pattern of errors over a period of time; and

apply a code-tracing profile appropriate for the detected pattern.

12. A system according to claim 9 , wherein the trace manager is further arranged to:

detect the absence of an error over a defined time period; and

reduce the code-tracing detail level.

13. A system according to claim 9 , wherein the system includes a self-service terminal.

14. A system according to claim 13 , wherein the self-service terminal includes a cash dispenser.

Assignments (10)
CORRECTIVE ASSIGNMENT TO CORRECT THE THE PROPERTIES SECTION BY INCLUDING IT WITH TEN PREVIOUSLY OMITTED PROPERTY NUMBERS PREVIOUSLY RECORDED ON REEL 65346 FRAME 367. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY INTEREST. Recorded Aug 13, 2025
From: NCR ATLEOS CORPORATION; CARDTRONICS USA, LLC
To: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 072445/0072 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 30, 2024
From: NCR VOYIX CORPORATION
To: NCR ATLEOS CORPORATION
Reel/Frame 067590/0109 →
CHANGE OF NAME Recorded May 30, 2024
From: NCR CORPORATION
To: NCR VOYIX CORPORATION
Reel/Frame 067578/0417 →
CORRECTIVE ASSIGNMENT TO CORRECT THE DOCUMENT DATE AND REMOVE THE OATH/DECLARATION (37 CFR 1.63) PREVIOUSLY RECORDED AT REEL: 065331 FRAME: 0297. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY INTEREST. Recorded Oct 31, 2023
From: NCR ATLEOS CORPORATION
To: CITIBANK, N.A.
Reel/Frame 065627/0332 →
SECURITY INTEREST Recorded Oct 25, 2023
From: NCR ATLEOS CORPORATION; CARDTRONICS USA, LLC
To: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 065346/0367 →
RELEASE OF PATENT SECURITY INTEREST Recorded Oct 25, 2023
From: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
To: NCR VOYIX CORPORATION
Reel/Frame 065346/0531 →
SECURITY INTEREST Recorded Oct 24, 2023
From: NCR ATLEOS CORPORATION
To: CITIBANK, N.A.
Reel/Frame 065331/0297 →
SECURITY AGREEMENT Recorded Apr 18, 2016
From: NCR CORPORATION; NCR INTERNATIONAL, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 038646/0001 →
SECURITY AGREEMENT Recorded Jan 15, 2014
From: NCR CORPORATION; NCR INTERNATIONAL, INC.
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 032034/0010 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 30, 2012
From: SPAFFORD, MICHAEL; VESELY, JAN
To: NCR CORPORATION
Reel/Frame 027966/0732 →