Method And System For Mapping Domain Prefixes To Qualified URLs

• US 20130067115A1
• Filed: 09/12/2012
• Published: 03/14/2013
• Est. Priority Date: 09/12/2011
• Status: Abandoned Application

• Current Assignee: Isaac Omar Lapanc
• Original Assignee: Isaac Omar Lapanc
• Inventors: Lapanc, Isaac Omar
• Application Number:
  US13/612,818
• Publication Number:
  US 20130067115A1
• Time in Patent Office: Days
• US Class Current: 709/245
• CPC Class Codes: G06F 16/9566 URL specific, e.g. using aliases, detecting broken or misspelled links
• CPC Class Codes: H04L 2101/33 containing protocol addresses or telephone numbers
• CPC Class Codes: H04L 2101/345 containing wildcard characters
• CPC Class Codes: H04L 61/106 across networks, e.g. mapping telephone numbers to data network addresses
• CPC Class Codes: H04L 61/302 Administrative registration, e.g. for domain names at internet corporation for assigned names and numbers [ICANN]
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications

Abstract

A centralized host server domain can be setup to process all the A (Address) wildcard DNS records of matching non-existent domain names. The left-most label of the non-existent domain will be identified as the “DOMAIN PREFIX” and it will be extracted from the non-existent domain name of the Universal Resource Locator (URL) HTTP Request that is sent by a client. The host server will use the extracted “DOMAIN PREFIX” and perform a search against a centralized database where Domains'"'"' output URLs are defined and mapped to “DOMAIN PREFIX” values. The search result, which can be a single URL or multiple URLs, of the same or different protocol, will be sent back to the client as the Response. Domain Prefixes values and their associated keywords that are stored in the centralized database and mapped to output URLs will be accessed and utilized by new and existing internet resources search engines.

Claims

1. A URL service system providing domains configured for utilizing non-existent domain names resulting by the wild card “

*”

setting of the A (Address) host record for the purpose of using the left-most value of the non-existent domain name to search a plurality of values that are stored in a central database and are mapped to a plurality of defined output re-direct URL links, the URL service system comprising;

a central database for storing registered qualified domains;

a central database for registering and storing phone numbers for the purpose of having them prefixed to qualified domains and non-existent domain names for the purpose of communication and establishing communication and linking channels;

a centralized host server exposing its IP address for other domains to use as the host IP address to point to when setting up their wild card “

*”

A (Address) record;

a service domain to handle and process phone numbers for the purpose of associating a phone number to a qualified domain and locating related internet URL information, wherein the general format is;

phone number.urlisp.com.

2. A method of prefixing qualified domains to retrieve specific internal and external URL internet resources as defined by the qualified domain operators, comprising:

storing a plurality of prefixes and associated keywords defined by users in a centralized database; and

searching the internet for the prefix values to locate specific internet resources.

3. The method of claim 2, wherein the prefix values are telephone numbers.

4. The method of claim 2, further comprising:

receiving and accepting a request from a service domain to join in servicing the phone number prefix by introducing a SERVICE JOIN Type.

5. The method of claim 4, further comprising extending contact software applications to display internet URL resources by consuming a plurality of defined Application Programming Interface methods that are associated with handling a processing procedures which are associated with the handling of non-existent domain names.

6. The method of claim 5, wherein the non-existent domain names comprise a phone number value.

7. A method of prefixing qualified domains to retrieve specific internal and external URL internet resources as defined by the qualified domain operators, comprising:

receiving an HTTP request URL having a qualified domain and at least one domain prefix;

determining whether the HTTP request contains a fully qualified URL;

if the HTTP request does not contain a fully qualified URL, then searching a database of for a qualified domain name that matches the qualified domain name in the received URL;

if a match is found in the database, determining the value of the domain prefix;

retrieving records associated with the domain prefix, wherein the records contain a second URL;

rendering the second URL.

8. The method of prefixing qualified domains of claim 7, further comprising determining whether the prefix value is a phone number.

9. The method of prefixing qualified domains of claim 8, wherein if the prefix value is a phone number, determining whether the phone number has been authorized via an approval process.

10. The method of prefixing qualified domains of claim 7, wherein the records associated with a domain prefix comprise a plurality of second URLs