Mobile Device Driving Behavior Tracking via OS Activity Services
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for understanding user interactions with mobile devices are limited, as they primarily focus on active actions, neglecting the vast amount of passive time when users are simply carrying their phones, which is not well understood or utilized in the industry.
Innovation Solution
A system and method for passively capturing and monitoring device behaviors using a mobile device's OS services and sensors to track movements and orientations, allowing for the inference of activities such as driving habits without the need for external OBD devices, and recording travel data efficiently to analyze driving behaviors.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If the system continuously monitors device behaviors using sensors and OS services, then measurement precision of driving habits is improved, but use of energy by the device increases
Solution Approach 1:
The system implements periodic monitoring by setting timers that activate sensor data collection only during specific intervals when driving activity is detected. Instead of continuous monitoring, the system checks for driving conditions periodically using OS activity services, and only then activates sensor recording, thereby reducing battery consumption while maintaining tracking accuracy during relevant periods
Solution Approach 2:
The system extracts and processes only the necessary sensor data (acceleration, orientation, location) when driving activity is detected, rather than continuously collecting all possible device data. By filtering and selecting only relevant sensor inputs based on OS activity reports, the system reduces energy consumption while maintaining measurement precision for driving habit analysis
2Device complexity
If the system uses OS services and sensors to track device behaviors, then device complexity is reduced by eliminating external OBD devices, but difficulty of detecting and measuring driving behaviors increases
Solution Approach 1:
The system uses the OS activity service as an intermediary that bridges the gap between simple sensor data and driving behavior detection. The OS service processes raw sensor inputs and provides standardized activity identifiers that indicate driving conditions, making it easier to detect driving behaviors without complex external hardware while maintaining detection accuracy through the operating system's built-in activity recognition capabilities
Solution Approach 2:
The system leverages the multi-functionality of existing OS services that handle various device activities (walking, running, driving, cycling) through a single unified interface. By using the universal activity recognition framework already present in the operating system, the system avoids the need for activity-specific sensors or processors, simplifying device complexity while maintaining comprehensive behavior detection capabilities
3Quantity of substance
If the system records sensor data continuously during detected driving activities, then quantity of useful information increases, but loss of time for data processing increases
Solution Approach 1:
The system performs preliminary filtering by using OS activity services to pre-identify driving conditions before activating full sensor recording. This preliminary detection action ensures that only data collected during actual driving activities is recorded, reducing the total volume of data that requires processing while maintaining comprehensive coverage of relevant driving behaviors
Solution Approach 2:
The system skips non-relevant data collection periods by using timer-based gating that prevents sensor recording during non-driving activities. By skipping data collection during irrelevant time periods, the system reduces both the quantity of data to process and the time required for data processing, while still capturing all necessary driving behavior information during active driving periods
Data Source
AI summary
A determination is made that a mobile device is associated with a reference activity of a user based on motion, orientation, rotational, magnetic field, and/or location data provided by sensors of the device. Activity data associated with the reference activity is obtained from the sensor-provided data. The activity data is recorded on the device for a configured period of time after which it is determined that the device is no longer performing the reference activity. The retained activity data for the reference activity is sent from the device to a network-based behavior analyzer when a network connection is available from the device. The network-based behavior analyzer derives user behaviors for the reference activity based on the activity data.