Mobile Call Content Preloading for Caller Credibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile device users frequently receive unwanted calls from unknown or suspicious sources, lacking effective tools to identify their credibility in real-time, leading to high rates of unanswered calls.
Innovation Solution
A system and method for call content management that includes identifying calls destined for mobile devices, accessing a call content API, assigning IP addresses and user identifiers, establishing communication channels, and routing calls with pre-loaded content to enhance user decision-making.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If caller ID or basic data services are used to display call sources, then users can identify some call information, but users lack sufficient content to verify caller credibility and distinguish spam/scam calls from legitimate calls
Solution Approach 1:
The system performs preliminary actions by pre-loading call content data (company information, logos, product details, testimonials) onto the mobile device before the actual call occurs. This allows the device to quickly retrieve and display relevant credibility information during the call without needing to query external servers in real-time, thus providing comprehensive verification content while maintaining system efficiency
Solution Approach 2:
The patent introduces an intermediary mechanism (content delivery network and API system) that bridges the gap between enterprise devices and mobile devices. This intermediary pre-processes and delivers call content data, enabling mobile devices to display comprehensive caller credibility information without requiring complex real-time verification systems on the user's end
2Reliability
If comprehensive call verification content is provided to help users identify legitimate calls, then users can make more informed decisions, but the system requires complex infrastructure including content delivery devices, APIs, and communication channels
Solution Approach 1:
The system segments the call verification functionality into distinct modular components: enterprise device (call initiation and content storage), content delivery device (data transmission and management), and mobile device (content display and user interaction). This segmentation allows each component to perform its specific function efficiently, improving overall system reliability while managing complexity through clear separation of concerns
Solution Approach 2:
The content delivery device acts as an intermediary that manages the complex infrastructure tasks of transmitting and managing call content data between the enterprise device and mobile device. This intermediary layer handles the complexity of data delivery, authentication, and synchronization, allowing the enterprise and mobile devices to focus on their core functions while maintaining high call identification accuracy
3Loss of information
If call content data is delivered in real-time during calls, then users can verify caller credibility, but the call setup time and data transmission delay increase
Solution Approach 1:
The system performs preliminary action by delivering and caching call content data on the mobile device before the call is initiated. The content delivery device transmits company information, logos, and other verification data in advance, allowing the mobile device to store this information locally. When the call occurs, the pre-loaded content is immediately displayed without requiring real-time data transmission, thus providing comprehensive caller information while minimizing call setup time
Solution Approach 2:
The patent merges the call setup process with the content delivery process by integrating these functions into a unified workflow. The content delivery device simultaneously handles call routing and content transmission, combining multiple operations into a single coordinated process that reduces overall setup time while ensuring complete caller verification data is delivered to the mobile device
Data Source
AI summary
One example method of operation may include identifying a call to a mobile device, determining whether the call includes call content data intended for the mobile device, initiating an active session and a time to live (TTL) associated with the call content data, forwarding the call content data to the mobile device when the call includes call content data associated with the caller, and receiving a content confirmation from the mobile device that the call content data was received.