URL Request Parsing for Direct Application Initialization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile devices often redirect URL requests to WAP browsers instead of launching relevant applications, forcing users to navigate through irrelevant website information, especially when accessing specific mobile applications like Sprint TV or airline check-in services.
Innovation Solution
Implementing a system that parses URL requests to identify application associations and initializes the corresponding destination application directly, even if the application is uninstalled, by using an association table that can be dynamically updated.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the mobile device redirects all URL requests to WAP browsers, then the device maintains a simple URL handling mechanism, but users experience irrelevant website information and cannot directly access specific mobile applications
Solution Approach 1:
The URL handling system is segmented into multiple components: a URL parser that extracts application identification portions, an association table that maps URLs to applications, and a decision logic that routes requests appropriately. This segmentation allows the system to differentiate between general web browsing and specific application launches, resolving the contradiction between simplicity and direct application access.
Solution Approach 2:
An association table acts as an intermediary between URL requests and mobile applications. This intermediary component stores mappings between URL patterns and target applications, enabling the system to translate generic URL requests into specific application launches without requiring complex direct routing logic, thus maintaining system simplicity while enabling direct access.
2Productivity
If the system parses every URL request to identify application associations, then users can directly access relevant applications, but the processing time and computational resources increase
Solution Approach 1:
The association table is pre-populated with URL-to-application mappings during system initialization or application installation. This preliminary action allows the system to quickly lookup and resolve URL requests without performing complex parsing and analysis for each individual request, thereby maintaining high application launch efficiency while minimizing processing time.
Solution Approach 2:
The system changes the parameter of URL handling from deep content analysis to pattern matching against pre-defined associations. By transforming the problem from interpreting full URL semantics to comparing against stored patterns, the system achieves fast processing while still enabling direct application access.
3Adaptability or versatility
If the system only initializes installed applications from URL requests, then the system maintains simple application management, but users cannot access or download new applications through URL links
Solution Approach 1:
The association table and URL parsing system serve multiple functions: they identify installed applications for direct launching, detect uninstalled applications, and trigger appropriate actions (launch or download). This multi-functionality allows the system to handle both installed and uninstalled applications through the same mechanism, increasing adaptability without proportionally increasing complexity.
Solution Approach 2:
The system dynamically determines the appropriate action based on application installation status. When a URL request is received, the system checks whether the associated application is installed and adapts its response accordingly—either launching the application or initiating a download. This dynamic behavior enables versatile application handling while maintaining a relatively simple core system.
Data Source
AI summary
Computer-readable media, systems, and methods for initializing a destination application on a mobile device based upon a received uniform resource locator (“URL”) request that is associated with the destination application. In embodiments, a URL request is received from a background application on a mobile device and the URL request indicates an address of a website that the user requests the mobile device be redirected to. Further, in embodiments, the URL request is parsed to obtain an application identification portion that is at least part of the URL request. In embodiments, it is determined that there is an association between the application identification portion and the destination application where the destination application is registered on the mobile device and is associated with the application identification portion of the URL request. Still further, in embodiments, the destination application is initialized.