Cellular Phone Offline Function Recommendation via Local History Database
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing cellular phone customization methods require online server cooperation, are limited to specific communication operations, and have deep menu hierarchies making it difficult to access frequently used functions.
Innovation Solution
A cellular phone with a rule database associating events with process data, a history database storing function and situation data, and a system that extracts and executes process data to recommend functions based on user history and situation, allowing offline use and easy access to frequently used functions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If a cellular phone operates in cooperation with a server for customization, then recommendation accuracy is improved, but the system cannot be used when the cellular phone is off-line
Solution Approach 1:
The patent segments the customization system into two parts: a server-based component for initial data collection and analysis, and a local component (rule database and history database) stored in the cellular phone for offline operation. This segmentation allows the system to maintain recommendation accuracy while enabling offline usability, as the local databases can operate independently once populated.
Solution Approach 2:
The system performs preliminary actions by collecting user data and generating rule information and history information during online periods, storing these in local databases before offline operation is needed. This preliminary data collection and processing enables the system to provide accurate recommendations even when the cellular phone is off-line, as all necessary information is pre-loaded.
2Productivity
If recommendation information is provided only for communication operations, then communication efficiency is improved, but the system cannot be employed when another operation is performed
Solution Approach 1:
The patent implements universality by designing the recommendation system to handle multiple types of operations beyond just communication. The rule database and history database are structured to capture and analyze various user activities, enabling the system to provide context-appropriate recommendations for different operations performed on the cellular phone, not limited to communication functions.
3Ease of manufacture
If a deep menu hierarchy is used for selecting functions, then function organization is improved, but it is difficult to reach a desired function even when frequently used
Solution Approach 1:
The patent applies self-service by enabling the system to automatically analyze user behavior patterns and generate contextual recommendations without requiring users to manually navigate through deep menu hierarchies. The history use part automatically extracts relevant information and presents recommended functions based on the current situation, allowing the system to serve itself in optimizing user access to functions.
Solution Approach 2:
The system performs preliminary analysis of user behavior and pre-prepares recommended functions based on historical data and current context. Instead of requiring users to search through organized but deep menus at the moment of need, the system has already identified and prepared relevant functions in advance, presenting them when needed based on the situation.
Data Source
AI summary
Every time a prescribe function is executed, a history use part 112 stores operation history information in an operation history DB 122. When an event occurs, an action control part 111 searches a rule DB 121, extracts an “action” corresponding to the event having occurred, and outputs the extracted action together with information indicating a situation of the occurrence of the event to the history use part 112. The history use part 112 searches he operation history DB 122 on the basis of the information indicating the situation of the occurrence of the event and extracts a corresponding “function”. The history use part 112 executes an action on the basis of the “action” input from the action control part 111 and the extracted “function”.