System and method for identifying problems via a monitoring application that repetitively records multiple separate consecutive files listing launched or installed applications

• US 8,996,916 B2
• Filed: 08/16/2012
• Issued: 03/31/2015
• Est. Priority Date: 08/16/2011
• Status: Active Grant

• Current Assignee: Future Dial Inc
• Original Assignee: Future Dial Inc
• Inventors: Huang, George C.
• Primary Examiner(s): SCHELL, JOSEPH O
• Application Number:
  US13/587,855
• Publication Number:
  US 20130047038A1
• Time in Patent Office: 957 Days
• Field of Search: 714/25, 714/26, 714/27, 714/37, 714/38.1, 714/40, 717/127, 717/168, 717/174
• US Class Current: 714/27
• 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/0721 within a central processing unit [CPU]
• CPC Class Codes: G06F 11/0748 in a remote unit communicating with a single-box computer node experiencing an error/fault remote testing G06F11/2294
• CPC Class Codes: G06F 11/0751 Error or fault detection not based on redundancy power supply failures G06F1/30; network fault management H04L41/06
• CPC Class Codes: G06F 11/0787 Storage of error reports, e.g. persistent data storage, storage using memory protection
• CPC Class Codes: G06F 11/079 Root cause analysis, i.e. error or fault diagnosis in a hardware test environment G06F11/22; in a software test environment G06F11/36
• CPC Class Codes: G06F 11/1448 Management of the data involved in backup or backup restore
• CPC Class Codes: G06F 11/1456 Hardware arrangements for backup
• CPC Class Codes: G06F 11/2294 by remote test
• CPC Class Codes: G06F 11/3051 Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs verification or detection of system hardware configuration G06F11/2247
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 13/124 where hardware is a sequential transfer control unit, e.g. microprocessor, peripheral processor or state-machine
• CPC Class Codes: G06F 13/385 for adaptation of a particular data processing system to different peripheral devices
• CPC Class Codes: G06F 13/4022 using switching circuits, e.g. switching matrix, connection or expansion network G06F13/4009 takes precedence
• CPC Class Codes: G06F 13/4027 using bus bridges G06F13/4022 takes precedence
• CPC Class Codes: G06F 13/4282 on a serial bus, e.g. I2C bus, SPI bus on daisy chain buses G06F13/4247
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data
• CPC Class Codes: G06F 3/0619 in relation to data integrity, e.g. data losses, bit errors
• CPC Class Codes: G06F 3/065 Replication mechanisms
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: H04L 41/0869 : Validating the configuration within one network element
• CPC Class Codes: H04M 1/72406 : by software upgrading or downloading
• CPC Class Codes: H04W 8/205 : Transfer to or from user equipment or user record carrier
• CPC Class Codes: H04W 8/24 : Transfer of terminal data
• CPC Class Codes: H04W 88/02 : Terminal devices

Abstract

A system and method for discovering fault conditions such as conflicts between applications and an operating system, driver, hardware, or a combination thereof, installed in mobile computing devices uses a mobile device running a diagnostic application. A list of applications that were launched or installed during a time period prior to an operational disruption is retrieved. A data table of combinations of incompatible programs and drivers is used to analyze the list of the applications that were launched or installed to create a list of potential fault-causing interactions due to software incompatibilities of software installed in the mobile computing device. A knowledge database is updated with data identifying at least one of the potential fault-causing interactions. Further disclosed is a computer program that identifies hardware-created or software-created problems and operational disruptions in mobile computing devices by collecting data on incompatibilities in particular mobile computing devices on the internet.

Claims

1. A method, comprising:

retrieving, via a computing device, from a mobile computing device having a wireless data connection, a list of applications that were launched or installed on the mobile computing device during a time period prior to an operational disruption, the list of applications generated via a monitoring application running on the mobile computing device, wherein the monitoring application repetitively records multiple separate consecutive files listing applications that have been launched or installed within the time period;

using, via the computing device, a data table of combinations of incompatible programs and drivers to analyze said list of the applications that were launched or installed, to create a list of potential fault-causing interactions due to software incompatibilities of hardware or of software installed in said mobile computing device; and

updating, via the computing device, a knowledge database with data identifying at least one of said potential fault-causing interactions.

2. The method of claim 1, wherein said potential fault-causing interactions comprise problems between applications and one or more of:

an operating system, a driver, hardware or another application.

3. The method of claim 1, wherein said monitoring application repetitively records three separate consecutive files by repetitively writing three files in a process wherein:

a first file is opened, data is written to the first file, and the first file is closed;

a second file is opened, data is written to the second file, and the second file is closed; and

,

a third file is opened, data is written to the third file, and the third file is closed.

4. The method of claim 1, wherein said monitoring application is configured to selectively upload said files to a central data repository only when a Wi-Fi connection is available to the mobile computing device.

5. The method of claim 1, further comprising generating a notification to a user of at least one software incompatibility or at least one recommended modification of said mobile computing device.

6. The method of claim 1, further comprising updating firmware in said mobile computing device after a data backup on said mobile computing device and restoring data to said mobile computing device from said data backup after said step of updating said firmware.

7. The method according to claim 1, wherein the computing device reads said list of applications and performs analysis on said list of applications to obtain statistical or heuristic patterns pinpointing a program creating said problems.

8. The method according to claim 1, further comprising creating a database that lists harmful combinations of model IDs, operating system versions, and other device characteristics that in conjunction with one or more programs negatively impact user experience.

9. A tangible non-transitory computer readable storage medium storing instructions, which when executed by a computing device instruct said computing device to perform a method comprising:

retrieving from a mobile computing device having a wireless data connection, a list of applications that were launched or installed on the mobile computing device during a time period prior to an operational disruption, the list of applications generated via a monitoring application running on the mobile computing device, wherein the monitoring application repetitively records multiple separate consecutive files listing applications that have been launched or installed within the time period;

using a data table of combinations of incompatible programs and drivers to analyze said list of the applications that were launched or installed, to create a list of potential fault-causing interactions due to software incompatibilities of hardware or of software installed in said mobile computing device; and

updating a knowledge database with data identifying at least one of said potential fault-causing interactions.

10. A system, comprising:

a processor;

a memory storing a set of instructions, which when executed instruct the processor to;

retrieve from a mobile computing device having a wireless data connection, a list of applications that were launched or installed on the mobile computing device during a time period prior to an operational disruption, the list of applications generated via a monitoring application running on the mobile computing device, wherein the monitoring application repetitively records multiple separate consecutive files listing applications that have been launched or installed within the time period;

use a data table of combinations of incompatible programs and drivers to analyze said list of the applications that were launched or installed, to create a list of potential fault-causing interactions due to software incompatibilities of hardware or of software installed in said mobile computing device; and

update a knowledge database with data identifying at least one of said potential fault-causing interactions.