IP Library Granted Patent US 9,686,220
Granted Patent B2
US 9,686,220 · App. 14/697,756 · Granted Jun 20, 2017

Debug and verify execution modes for computing systems calculating automation degree of implementation metrics

Inventors: James R Malnati (Stillwater, MN); John Troini (Gilroy, CA); Robert Jamieson (Kuala Lumpur, MY)
Assignee: Unisys Corporation
H04L51/18H04L41/0627H04L41/0681H04L41/0876H04L41/0886H04L51/06H04L51/14H04L51/16
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 9,686,220
App. No.
14/697,756
Granted
Jun 20, 2017
Kind
B2
Abstract

Non-automated read-and-reply console messages may be automated. These messages may be classified into impact groups in which the messages may be removed from the database or sent to an automation analyzer for analysis. As more messages become automated, a debugging mode may be enabled to allow an operator to respond to a message with a proposed action. If the proposed action is aligned with an action predetermined in response to the automation analysis, the operator may be allowed to respond to future actions.

Claims (28)

1. A method, comprising:

selecting, by the message system, a first message execution mode for messages received by the message system, wherein the first message execution mode is selected from a group consisting of a first message execution mode and a second message execution mode;

receiving, by a message system, a first plurality of messages relating to events occurring on a host system;

processing, by the message system, the first plurality of messages in accordance with the selected first message execution mode, wherein processing in accordance with the first message execution mode comprises executing actions invoked by execution of a first portion of the first plurality of messages and logging, but not executing, actions invoked by execution of a second portion of the first plurality of messages; and

determining an automation degree of implementation metric indicative of the degree of automation implemented in the massage system, wherein the automation degree of implementation metric comprises a percentage or an absolute number of messages automated in the message system.

2. The method of claim 1 , further comprising:

selecting the second message execution mode;

receiving a second plurality of messages relating to events occurring on the host system; and

processing the second plurality of messages in accordance with the selected second message execution mode, wherein processing in accordance with the second message execution mode comprises logging, but not executing, all actions invoked by execution of the second plurality of messages.

3. The method of claim 2 , wherein selection of the second message execution mode overrides selection of the first message execution mode.

4. The method of claim 2 , wherein selection of one of the first message execution mode and second message execution mode is based, at least in part, on user input.

5. The method of claim 2 , further comprising comparing one or more logged actions with one or more user actions invoked in response to execution of one or more messages similar to the messages that invoked the one or more actions that were logged, but not executed.

6. The method of claim 5 , further comprising determining a level of confidence in the execution of the one or more messages based, at least in part, on the comparison, wherein the level of confidence comprises a confidence percentage.

7. An apparatus, comprising:

a processor; and

a memory coupled to the processor, where the processor is configured to perform the steps of:

selecting a first message execution mode for messages received by the message system, wherein the first message execution mode is selected from a group consisting of a first message execution mode and a second message execution mode;

receiving a first plurality of messages relating to events occurring on a host system;

processing the first plurality of messages in accordance with the selected first message execution mode, wherein processing in accordance with the first message execution mode comprises executing actions invoked by execution of a first portion of the first plurality of messages and logging, but not executing, actions invoked by execution of a second portion of the first plurality of messages; and

wherein the processor is further configured to perform the step of determining an automation degree of implementation metric indicative of the degree of automation implemented in the message system, wherein the automation degree of implementation metric comprises a percentage or an absolute number of messages automated in the message system.

8. The apparatus of claim 7 , wherein the processor is further configured to perform the steps of:

selecting the second message execution mode;

receiving a second plurality of messages relating to events occurring on the host system; and

processing the second plurality of messages in accordance with the selected second message execution mode, wherein processing in accordance with the second message execution mode comprises logging, but not executing, all actions invoked by execution of the second plurality of messages.

9. The apparatus of claim 8 , wherein selection of the second message execution mode overrides selection of the first message execution mode.

10. The apparatus of claim 8 , wherein selection of one of the first message execution mode and second message execution mode is based, at least in part, on user input.

11. The apparatus of claim 8 , wherein the processor is further configured to perform a step of comparing one or more logged actions with one or more user actions invoked in response to execution of one or more messages similar to the messages that invoked the one or more actions that were logged, but not executed.

12. The apparatus of claim 11 , wherein the processor is further configured to perform a step of determining a level of confidence in the execution of the one or more messages based, at least in part, on the comparison, wherein the level of confidence comprises a confidence percentage.

Assignments (8)
AMENDED AND RESTATED PATENT SECURITY AGREEMENT Recorded Jun 27, 2025
From: UNISYS CORPORATION; UNISYS HOLDING CORPORATION; UNISYS NPL, INC.; UNISYS AP INVESTMENT COMPANY I
To: COMPUTERSHARE TRUST COMPANY, N.A., AS COLLATERAL TRUSTEE
Reel/Frame 071759/0527 →
RELEASE OF SECURITY INTEREST Recorded Oct 28, 2020
From: WELLS FARGO BANK, NATIONAL ASSOCIATION
To: UNISYS CORPORATION
Reel/Frame 054231/0496 →
RELEASE OF SECURITY INTEREST Recorded Nov 9, 2017
From: WELLS FARGO BANK, NATIONAL ASSOCIATION
To: UNISYS CORPORATION
Reel/Frame 044416/0114 →
SECURITY INTEREST Recorded Oct 12, 2017
From: UNISYS CORPORATION
To: WELLS FARGO BANK NA
Reel/Frame 043852/0145 →
SECURITY INTEREST Recorded Oct 6, 2017
From: UNISYS CORPORATION
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 044144/0081 →
SECURITY INTEREST Recorded Sep 12, 2017
From: UNISYS CORPORATION
To: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS AGENT
Reel/Frame 043558/0245 →
PATENT SECURITY AGREEMENT Recorded Apr 27, 2017
From: UNISYS CORPORATION
To: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL TRUSTEE
Reel/Frame 042354/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 6, 2015
From: MALNATI, JAMES R; JAMIESON, ROBERT; TROINI, JOHN
To: UNISYS CORPORATION
Reel/Frame 036060/0910 →
Continuity (1)
Related Publication 20160323209A1 · Nov 3, 2016