Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method for mapping and routing web URL requests from a web browser into a mobile application when installed on a computing device, without access to the computing device operating system's registry of installed applications, comprising the steps of: generating a hosted URL address for mapping and routing, wherein the hosted URL address includes a domain name and a path name; preparing and storing in a database, routing instructions for the hosted URL based on the path name, including specifying at least one preferred destination URL and at least one alternate URL for each of a specified target operating system; receiving a header request from a computing device to access the hosted URL via a web browser resident on the requesting computing device, wherein the header request includes the hosted URL address and an identifying user-agent string of the web browser; analyzing the header request to identify the path name of the hosted URL address and the requesting operating system as provided in the identifying user-agent string; searching the database of routing instructions to identify the at least one preferred destination URL and the at least one alternate URL associated with the path name and the operating system provided in the header request; retrieving from the database the identified at least one preferred destination URL and the at least one alternate URL providing an instruction to the computing device to redirect the web browser to the retrieved at least one preferred destination URL, wherein the instruction includes a web browser status request; receiving the requested web browser status from the computing device indicating if the browser is in an active or inactive state; and if the web browser status is inactive, then providing an instruction to the computing device to redirect the web browser to the retrieved at least one alternate destination URL.
A system maps web URL requests to mobile apps without accessing the operating system's app registry. It generates a unique, trackable web address (URL) with a domain and a specific path. Routing instructions are stored in a database, linking the URL path to a "preferred" destination (ideally the mobile app) and an "alternate" destination (like a mobile webpage) for each operating system. When a user clicks the URL, the system detects the URL path and operating system from the browser request. It retrieves the preferred and alternate URLs from the database. The system then checks if the user's browser is active or inactive (likely indicating the app's presence). If inactive, the system redirects the browser to the alternate URL, otherwise the preferred URL is used.
2. The method of claim 1 , wherein the database is an application server.
The URL mapping and routing system described previously where web URL requests are mapped to mobile apps without accessing the operating system's app registry and routing instructions are stored in a database, the database is specifically an application server. This means the routing logic and URL-to-destination mappings are handled by a dedicated server application, centralizing the routing management and potentially allowing for easier scaling and updates to the URL routing rules. The application server handles receiving the web URL requests, querying the routing rules, and instructing the user's browser on where to redirect.
3. The method of claim 1 , wherein the preferred destination URL is present in a mobile application.
The URL mapping and routing system described previously where web URL requests are mapped to mobile apps without accessing the operating system's app registry, and a system detects the URL path and operating system from the browser request and then retrieves the preferred and alternate URLs from the database, the preferred destination URL is designed to directly open and navigate within a mobile application installed on the user's device. This means that if the system detects the mobile application is present (browser active), the user will be seamlessly directed into the app, enhancing the user experience by bypassing the mobile website.
4. The method of claim 3 , wherein the alternate landing page is a mobile version of a webpage and is displayed on the web browser of the computing device.
The URL mapping and routing system, which redirects web requests to mobile apps if available, uses an alternate landing page when the app isn't active, that alternate landing page is a mobile-optimized version of a webpage. This mobile webpage is displayed directly within the user's web browser on their device. This ensures that users always have a usable destination, even if the preferred mobile app destination isn't available, and the mobile webpage is tailored to the device's screen size for optimal viewing.
5. The method of claim 1 , wherein at least one of the at least one preferred destination URL and the at least one alternate destination URL is chosen based on at least one of geographical location of the computing device and the time of day the header request is received from the computing device.
The URL mapping and routing system described previously, where web URL requests are mapped to mobile apps and a system detects the URL path and operating system from the browser request and then retrieves the preferred and alternate URLs from the database, the choice between the preferred mobile app destination and the alternate webpage destination is influenced by the user's geographical location or the time of day the request is received. This enables location-based routing to different app sections or time-sensitive promotions on the webpage. For example, users in a specific region could be directed to a localized version of the app or webpage or during specific hours.
6. The method of claim 1 further including, receiving the at least one preferred destination URL and the at least one alternate destination URL from a form in communication with the database.
The URL mapping and routing system described previously, where web URL requests are mapped to mobile apps, and preferred and alternate URLs are retrieved from a database, includes a method for receiving the preferred mobile app destination and alternate webpage URL information through a form that directly interacts with the routing database. This enables administrators or marketing teams to easily manage and update the URL routing rules without needing direct access to the database, providing a user-friendly interface for configuring the system. This input mechanism simplifies the process of specifying which URLs should direct to specific app locations or mobile web pages.
7. The method of claim 1 further including a computer having a processor and memory in communication with the database, for generating the hosted URL address, and preparing, and storing in the database, the routing instructions for the hosted URL.
The URL mapping and routing system described previously, where web URL requests are mapped to mobile apps, includes a computer system with a processor and memory that communicates with the database to handle key functions: generating the initial trackable web address (URL), preparing the routing instructions that link the URL to mobile app and webpage destinations, and storing those routing instructions within the database. This computer system is the central control point for managing the URL mapping and routing logic, and the processor executes the code responsible for generating URLs and managing routing data.
8. The method of claim 1 , wherein the computer includes a URL management interface for receiving the at least one preferred destination URL from a data entry form.
The URL mapping and routing system that redirects web requests to mobile apps if available, includes a URL management interface on a computer. This interface allows administrators to input the preferred mobile app destination URL using a data entry form. The system provides a user-friendly method for specifying which app destination should be associated with a given tracked URL, simplifying the configuration and maintenance of the app redirection rules. This helps non-technical personnel manage the app redirection destinations, by abstracting away the complexities of the underlying database.
Unknown
August 22, 2017
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.