Fault Data Logging for Wireless Mobile Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile communication devices face challenges in diagnosing and isolating latent bugs due to resource constraints and complex technology integration, leading to increased call volumes, troubleshooting difficulties, and revenue loss from device recalls.

Innovation Solution

A communication system that selectively collects and analyzes fault data by logging information at each vertical software layer, enabling efficient diagnosis of responsible components and reducing the burden on wireless data communication networks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If comprehensive fault data collection is implemented across all devices, then diagnostic accuracy is improved, but network bandwidth consumption increases

Engineering Contradiction:
Improvediagnostic accuracyVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
Measurement precisionVSLoss of energy

Solution Approach 1:

The system implements selective fault data collection by configuring different fault logging parameters for different device groups or individual devices. The network server can set specific fault types, severity levels, or data collection intervals tailored to each device's operational context, ensuring that only relevant fault information is transmitted, thus improving diagnostic accuracy for critical issues while minimizing unnecessary network bandwidth consumption.

Inventive Principle:
Principle #3Local quality

2Measurement precision

If detailed fault logging is enabled continuously, then fault diagnosis capability is improved, but device processing overhead increases

Engineering Contradiction:
Improvefault diagnosis capabilityVSAvoiddevice processing overhead
Core Design Contradiction:
Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The system implements periodic or event-triggered fault data collection instead of continuous logging. The fault data collection can be activated at specific intervals or triggered by particular events such as detected anomalies, system state changes, or user requests. This approach enables sufficient fault diagnosis capability when needed while significantly reducing the continuous processing overhead and energy consumption on resource-constrained mobile devices.

Inventive Principle:
Principle #19Periodic action

3Productivity

If extensive fault information is collected, then bug isolation speed is improved, but data management complexity increases

Engineering Contradiction:
Improvebug isolation speedVSAvoiddata management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system extracts and transmits only the essential fault information needed for rapid bug isolation to the network server for centralized analysis. By filtering and selecting only the most relevant fault data characteristics and sending them to the server, the system achieves fast bug isolation capability while keeping the data management complexity on individual devices minimal. The server handles the complex analysis of aggregated fault information from multiple devices.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS8886179B2Fielded device failure tracking and response
Publication Date: 2014.11.11 QUALCOMM INC
  • US8886179B2 patent drawing
  • US8886179B2 patent drawing
  • US8886179B2 patent drawing

AI summary

A fault remediation system for fielded wireless mobile devices addresses field failure data collection, consolidation of field failure data, and an information services platform so that the players in a wireless/mobile broadcast/broadband application/service value chain to respond to field failure problems in a consistent and automated manner from wireless/mobile devices over wireless multicast and or wireless broadband networks. An elegant and extremely flexible mechanism enables the failure data collection from a targeted set of wireless/mobile devices. In addition, sophisticated mechanisms identify targeted set of devices that should participate in field failure data collection based on user specified operational requirements (e.g., selected OEM, device configuration type, subscribers to a specific wireless broadband serve, failure occurrence certain time limits, etc.). The fault data logging on the mobile device is vertically integrated to allow diagnosis and assignment to a responsible party for fixing, testing, and release with subsequent certification and deployment.