IP Library Granted Patent US 10,417,084
Granted Patent B2
US 10,417,084 · App. 15/460,086 · Granted Sep 17, 2019

Method and apparatus for managing device failure

Inventors: Vincent Yin Liu (Chengdu, CN); Patrick Minggang Lu (Shanghai, CN); Charlie Chao Chen (Shanghai, CN)
Assignee: EMC IP Holding Company LLC
G06F11/0793G06F11/079G06F11/0709H04L41/00H04L41/069H04L41/0636H04L41/0681
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,417,084
App. No.
15/460,086
Granted
Sep 17, 2019
Kind
B2
Abstract

Embodiments of the present disclosure relate to a method and apparatus for managing a failure of a device. The method comprises detecting whether a failure occurs in a device, and generating a failure report for the failure in response to the failure occurring in the device. The method further comprises querying a device object repository with the failure report, and the object device repository stores historical failure information associated with the device and a fix solution corresponding to the historical failure information. The method further comprises obtaining the fix solution from the device object repository based on a comparison between the failure report and the historical failure information. Embodiments of the present disclosure can manage the failure of the device more effectively.

Claims (62)

1. A method for managing a failure of a device, comprising:

detecting whether a failure occurs in the device including:

periodically detecting whether the failure occurs in the device; and

in response to the failure occurring in the device, generating a new task in a task management module, the task management module being used to manage status of the device;

in response to the failure occurring in the device, generating a failure report for the failure;

querying a device object repository with the failure report, the device object repository storing historical failure information associated with the device and a fix solution corresponding to the historical failure information;

obtaining the fix solution from the device object repository based on a comparison between the failure report and the historical failure information;

in response to obtaining the fix solution from the device object repository, fixing the failure according to the fix solution;

re-detecting whether the failure occurs in the device; and

in response to no failure occurring in the device, automatically closing the new task.

2. The method according to claim 1 , wherein the detecting whether a failure occurs in a device comprises:

in response to generating a new task in a task management module, detecting whether the failure occurs in the device, the task management module being used to manage status of the device.

3. The method according to claim 1 , wherein the detecting whether a failure occurs in a device further comprises:

obtaining operating status information of the device; and

determining whether the failure occurs in the device based on the operating status information.

4. The method according to claim 1 , wherein the generating the failure report of the failure comprises:

performing, for the failure, a correlation analysis between the device and another device; and

determining a root cause of the failure based on a result of the correlation analysis.

5. The method according to claim 4 , wherein the failure report includes at least one of the following:

a failure code of the failure, a log of the failure, an identifier of the device, a type of the device, a vendor of the device and a location of the device.

6. The method according to claim 1 , wherein the obtaining the fix solution from the device object repository comprises:

determining a matching degree between failure information in the failure report and the historical failure information; and

in response to the matching degree being above a predetermined threshold, obtaining the fix solution from the device object repository.

7. The method according to claim 6 , wherein the matching degree includes a plurality of sub-matching degrees, the plurality of sub-matching degrees including at least two of the following: a first matching degree related to a type, a second matching degree related to a vendor, a third matching degree related to a failure code, and a fourth matching degree related to a failure log.

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

obtaining operating status information of a plurality of devices from the task management module for display, the device being included in the plurality of devices.

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

analyzing the historical failure information in the device object repository; and

predicting a potential failure based on a result of the analysis.

10. A system, comprising:

a data storage system; and

computer-executable program logic encoded in memory of one or more computers enabled to manage a failure of a device, wherein the computer-executable program logic is configured for the execution of:

detecting whether a failure occurs in the device including:

periodically detecting whether the failure occurs in the device; and

in response to the failure occurring in the device, generating a new task in a task management module, the task management module being used to manage status of the device;

in response to the failure occurring in the device, generating a failure report for the failure;

querying a device object repository with the failure report, the device object repository storing historical failure information associated with the device and a fix solution corresponding to the historical failure information;

obtaining the fix solution from the device object repository based on a comparison between the failure report and the historical failure information;

in response to obtaining the fix solution from the device object repository, fixing the failure according to the fix solution;

re-detecting whether the failure occurs in the device; and

in response to no failure occurring in the device, automatically closing the new task.

11. The system of claim 10 , wherein the detecting whether a failure occurs in a device comprises:

in response to generating a new task in a task management module, detecting whether the failure occurs in the device, the task management module being used to manage status of the device.

12. The system of claim 10 , wherein the detecting whether a failure occurs in a device further comprises:

obtaining operating status information of the device; and

determining whether the failure occurs in the device based on the operating status information.

13. A computer program product for managing a failure of a device, the computer program product comprising:

a non-transitory computer readable medium encoded with computer-executable code, the code configured to enable the execution of:

detecting whether a failure occurs in a device including:

periodically detecting whether the failure occurs in the device; and

in response to the failure occurring in the device, generating a new task in a task management module, the task management module being used to manage status of the device;

in response to the failure occurring in the device, generating a failure report for the failure;

querying a device object repository with the failure report, the device object repository storing historical failure information associated with the device and a fix solution corresponding to the historical failure information;

obtaining the fix solution from the device object repository based on a comparison between the failure report and the historical failure information;

in response to obtaining the fix solution from the device object repository, fixing the failure according to the fix solution;

re-detecting whether the failure occurs in the device; and

in response to no failure occurring in the device, automatically closing the new task.

14. The computer program product of claim 13 , wherein the detecting whether a failure occurs in a device comprises:

in response to generating a new task in a task management module, detecting whether the failure occurs in the device, the task management module being used to manage status of the device.

15. The computer program product of claim 13 , wherein the detecting whether a failure occurs in a device further comprises:

obtaining operating status information of the device; and

determining whether the failure occurs in the device based on the operating status information.

Assignments (8)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053546/0001) Recorded Jun 23, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC IP HOLDING COMPANY LLC
Reel/Frame 071642/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (042769/0001) Recorded Apr 26, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MOZY, INC.); DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO WYSE TECHNOLOGY L.L.C.)
Reel/Frame 059803/0802 →
RELEASE OF SECURITY INTEREST AT REEL 042768 FRAME 0585 Recorded Nov 2, 2021
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; MOZY, INC.; WYSE TECHNOLOGY L.L.C.
Reel/Frame 058297/0536 →
SECURITY AGREEMENT Recorded Apr 22, 2020
From: CREDANT TECHNOLOGIES INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 053546/0001 →
SECURITY AGREEMENT Recorded Mar 21, 2019
From: CREDANT TECHNOLOGIES, INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 049452/0223 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 21, 2017
From: LIU, VINCENT YIN; LU, PATRICK MINGGANG; CHEN, CHARLIE CHAO
To: EMC IP HOLDING COMPANY, LLC
Reel/Frame 044457/0224 →
PATENT SECURITY INTEREST (CREDIT) Recorded Jun 12, 2017
From: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; MOZY, INC.; WYSE TECHNOLOGY L.L.C.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 042768/0585 →
PATENT SECURITY INTEREST (NOTES) Recorded Jun 12, 2017
From: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; MOZY, INC.; WYSE TECHNOLOGY L.L.C.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 042769/0001 →
Priority Claims (1)
CN 2016 1 0148027 · Mar 15, 2016 · national
Continuity (1)
Related Publication 20170269983A1 · Sep 21, 2017