Event-Controlled Mobile OS Logging for Reduced Computational Burden

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The increasing complexity of mobile device operations has made parsing log data computationally prohibitive, requiring more efficient mechanisms for managing and analyzing log data in mobile operating systems.

Innovation Solution

Implementing event-controlled continuous logging in mobile operating environments, where log data collection is initiated and terminated based on predetermined events, with index codes for categorization and multiple triggers for flexible data management, allowing for selective and efficient logging of relevant data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If continuous logging of all mobile OS data is implemented, then diagnostic capabilities are improved, but computational burden and complexity increase

Engineering Contradiction:
Improvediagnostic capabilitiesVSAvoidcomputational burden
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments log data collection by creating multiple independent trigger mechanisms (start triggers and stop triggers) that can be activated based on specific events. Each trigger operates independently and can be associated with index codes to filter data collection scope. This segmentation allows the system to collect only relevant log data during specific time windows rather than continuously collecting all data, thereby reducing computational burden while maintaining diagnostic capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements periodic logging by using paired start and stop triggers that define specific time windows for data collection. Logging is activated periodically when start triggers are met and deactivated when corresponding stop triggers are met. This periodic action replaces continuous logging, significantly reducing the computational burden while still capturing diagnostic information at relevant intervals.

Inventive Principle:
Principle #19Periodic action

2Adaptability or versatility

If event-controlled logging with multiple triggers is implemented, then data management flexibility is improved, but system complexity increases

Engineering Contradiction:
Improvedata management flexibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal trigger mechanism that can handle multiple functions through a common framework. The same trigger structure supports both start and stop functions, can be associated with multiple index codes, and can operate independently or in combination with other triggers. This multi-functionality provides data management flexibility without proportionally increasing system complexity, as the underlying mechanism remains consistent across different use cases.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The trigger mechanisms are designed to be self-configuring through association with index codes and events. When a start trigger is activated, it automatically defines the scope of data collection based on its associated index codes. Corresponding stop triggers automatically terminate collection when their conditions are met. This self-service capability allows flexible data management without requiring complex external control logic.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS7890299B2Providing event-controlled continuous logging for a mobile operating environment
Publication Date: 2011.02.15 QUALCOMM INC
  • US7890299B2 patent drawing
  • US7890299B2 patent drawing
  • US7890299B2 patent drawing

AI summary

Providing for event-controlled continuous logging for a mobile operating environment is described herein. For instance, collection of mobile device operating system (OS) log data can be initiated and terminated as a result of one or more predetermined events. The events can both trigger collection as well as terminate collection of the log data. Further, limiting collection/termination of log data to particular log index codes is also described herein, enabling logging of data pertinent to one or more determinable events. As described, the subject specification discloses mechanisms to initiate and to terminate continuous logging of mobile OS log codes as a result of occurrence of one or more determinable events.